From 65b5515cc11d64e312a25e380ed8d1d31d68d14a Mon Sep 17 00:00:00 2001
From: fire <fire@users.noreply.github.com>
Date: Sat, 2 Nov 2024 14:54:50 +0000
Subject: [PATCH] =?UTF-8?q?Deploying=20to=20gh-pages=20from=20=20@=2098cbb?=
 =?UTF-8?q?53c085c0cf6eb1fc47d246e37298e40d9a7=20=F0=9F=9A=80?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/authors.html                             |     2 +-
 docs/changelog.html                           |    80 +-
 docs/changelog.xml                            |    42 +-
 docs/changelog/2021/20210401-changelog.html   |     2 +-
 docs/changelog/2021/20210501-changelog.html   |     2 +-
 docs/changelog/2021/20210601-changelog.html   |     2 +-
 docs/changelog/2021/20210701-changelog.html   |     2 +-
 docs/changelog/2021/20210801-changelog.html   |     2 +-
 docs/changelog/2021/20210901-changelog.html   |     2 +-
 docs/changelog/2021/20211001-changelog.html   |     2 +-
 docs/changelog/2021/20211101-changelog.html   |     2 +-
 docs/changelog/2022/20220101-changelog.html   |     2 +-
 docs/changelog/2022/20220201-changelog.html   |     2 +-
 docs/changelog/2022/20220301-changelog.html   |     2 +-
 docs/changelog/2022/20220401-changelog.html   |     2 +-
 docs/changelog/2022/20220501-changelog.html   |     2 +-
 docs/changelog/2022/20220601-changelog.html   |     2 +-
 docs/changelog/2022/20220801-changelog.html   |     2 +-
 docs/changelog/2022/20220901-changelog.html   |     2 +-
 docs/changelog/2022/20221001-changelog.html   |     2 +-
 docs/changelog/2022/20221101-changelog.html   |     2 +-
 docs/changelog/2022/20221201-changelog.html   |     2 +-
 docs/changelog/2023/20230101-changelog.html   |     2 +-
 docs/changelog/2023/20230201-changelog.html   |     2 +-
 docs/changelog/2023/20230301-changelog.html   |     2 +-
 docs/changelog/2023/20230501-changelog.html   |     2 +-
 docs/changelog/2023/20230601-changelog.html   |     2 +-
 docs/changelog/2023/20230701-changelog.html   |     2 +-
 docs/changelog/2023/20230801-changelog.html   |     2 +-
 docs/changelog/2023/20230901-changelog.html   |     2 +-
 docs/changelog/2023/20231001-changelog.html   |     2 +-
 docs/changelog/2023/20231109-changelog.html   |     2 +-
 docs/changelog/2023/20231207-changelog.html   |     2 +-
 docs/changelog/2024/20240101-changelog.html   |     2 +-
 docs/changelog/2024/20240202-changelog.html   |     2 +-
 docs/changelog/2024/20240330-changelog.html   |     2 +-
 docs/changelog/2024/20240505-changelog.html   |     2 +-
 docs/changelog/2024/20240603-changelog.html   |     2 +-
 docs/changelog/2024/20240625-changelog.html   |     2 +-
 docs/changelog/2024/20240701-changelog.html   |     2 +-
 docs/changelog/2024/20240901-changelog.html   |     2 +-
 docs/changelog/2024/20241003-changelog.html   |     2 +-
 docs/decisions.html                           |   922 +-
 docs/decisions.xml                            |    42 +-
 .../20200602-manage-backend-with-k3s.html     |     2 +-
 docs/decisions/20200608-vsekai-charter.html   |     2 +-
 .../decisions/20200729-entity-networking.html |     2 +-
 .../20210212-add-build-notifications.html     |     2 +-
 ...212-use-log4brains-to-manage-the-adrs.html |     2 +-
 ...rkdown-architectural-decision-records.html |     2 +-
 .../20210523-basis-universal-import.html      |     2 +-
 ...t-and-export-pipeline-in-godot-engine.html |     2 +-
 ...istribute-trusted-clients-with-notary.html |     2 +-
 ...3-retarget-motion-for-vrm-type-models.html |     2 +-
 ...lfy-meshes-and-lods-better-with-quads.html |     2 +-
 ...ial-install-of-gravity-for-kubernetes.html |     2 +-
 .../20210529-performance-profiling.html       |     2 +-
 ...ntation-and-book-content-via-lottie-2.html |     2 +-
 .../20210612-flow-avatar-asset-pipeline.html  |     2 +-
 ...20210622-shadermotion-to-godot-engine.html |     2 +-
 ...7-transfer-animations-by-baking-reset.html |     2 +-
 .../20210710-verify-pr-workflow.html          |     2 +-
 .../20210715-Material-Addon-Blender.html      |     2 +-
 .../20210715-portable-world-content.html      |     2 +-
 ...0210724-Spreadsheet-animation-preview.html |     2 +-
 .../decisions/20210811-disconnected-ipfs.html |     2 +-
 .../20210811-game-workflow-membrane.html      |     2 +-
 docs/decisions/20210811-glb-in-video.html     |     2 +-
 .../20210811-godot-transparency.html          |     2 +-
 docs/decisions/20210811-min-spec-v-sekai.html |     2 +-
 docs/decisions/20210811-minecraft-voxel.html  |     2 +-
 .../20210811-neural-blend-shape-rigging.html  |     2 +-
 docs/decisions/20210811-omi-glb.html          |     2 +-
 docs/decisions/20210811-soiree-party.html     |     2 +-
 docs/decisions/20210811-spoke-to-v-sekai.html |     2 +-
 .../20211005-bridge-music-to-xr.html          |     2 +-
 ...create-add-spring-bones-to-vrm-models.html |     2 +-
 .../20211005-create-sop-for-vrm-creation.html |     2 +-
 ...esults-by-subdivision-in-godot-engine.html |     2 +-
 ...ap-by-connecting-mediapipe-to-blender.html |     2 +-
 .../20211005-test-google-mediapipe.html       |     2 +-
 ...our-amd-apu-test-computer-via-barrier.html |     2 +-
 ...5-use-materialx-for-asset-interchange.html |     2 +-
 ...riends-and-acquaintances-via-presence.html |     2 +-
 ...e-cluster-for-the-same-web-and-native.html |     2 +-
 ...rams-at-production-quality-of-service.html |     2 +-
 .../20211031-1000-player-servers.html         |     2 +-
 docs/decisions/20211031-arc-radial-menu.html  |     2 +-
 ...nto-a-custom-godot-standardmaterial3d.html |     2 +-
 ...ake-blend-shape-to-skeleton-animation.html |     2 +-
 ...20211031-benchmark-animation-playback.html |     2 +-
 .../20211031-character-workshop.html          |     2 +-
 .../20211031-cicd-export-v-sekai.html         |     2 +-
 docs/decisions/20211031-client-and-mast.html  |     2 +-
 .../20211031-construct-the-virtual-world.html |     2 +-
 ...20211031-create-a-demo-viewer-gallery.html |     2 +-
 ...g-via-robot-framework-and-swiftshader.html |     2 +-
 ...1031-extract-proposals-into-proposals.html |     2 +-
 ...ion-tracking-requires-standard-shapes.html |     2 +-
 ...tion-players-to-the-closest-root-node.html |     2 +-
 ...1-godot-database-viewer-for-proposals.html |     2 +-
 ...have-better-user-developer-experience.html |     2 +-
 docs/decisions/20211031-have-wires-in-3d.html |     2 +-
 ...031-how-to-make-a-v-sekaigodot-update.html |     2 +-
 docs/decisions/20211031-keep-a-changelog.html |     2 +-
 .../20211031-make-a-place-to-record.html      |     2 +-
 docs/decisions/20211031-meeting-area.html     |     2 +-
 ...31-membrane-framework-streaming-mixer.html |     2 +-
 .../20211031-openvr-for-godot-engine.html     |     2 +-
 ...out-groups-terminology-for-vskdefault.html |     2 +-
 .../20211031-plausable-npc-behaviour.html     |     2 +-
 ...processed-animations-on-any-vrm-model.html |     2 +-
 ...-from-windows-in-unix-mode-with-msys2.html |     2 +-
 .../20211031-script-as-a-binary.html          |     2 +-
 .../20211031-standard-backup-procedures.html  |     2 +-
 .../20211031-stream-shader-motion.html        |     2 +-
 ...1-streaming-godot-to-opensoundcontrol.html |     2 +-
 docs/decisions/20211031-thorvg.html           |     2 +-
 .../20211031-tire-model-car-sim.html          |     2 +-
 .../20211031-update-uro-for-godot-4.html      |     2 +-
 ...1-use-bpr-to-rank-skeleton-bone-names.html |     2 +-
 .../20211031-use-our-custom-fullbody-ik.html  |     2 +-
 .../20211031-verification-tools.html          |     2 +-
 ...0211031-vmd-on-vrm-animationtree-node.html |     2 +-
 docs/decisions/20211031-voip.html             |     2 +-
 ...latform-called-vfx-reference-platform.html |     2 +-
 ...104-research-mesh-tooling-with-kaolin.html |     2 +-
 ...1104-research-mesh-tooling-with-nglod.html |     2 +-
 ...1105-have-an-webxr-version-of-v-sekai.html |     2 +-
 ...-on-wasgo-prototype-by-using-godot-34.html |     2 +-
 ...points-to-triangulate-in-godot-engine.html |     2 +-
 ...r-in-godot-engine-to-prototype-cassie.html |     2 +-
 ...aterials-on-the-web-in-godot-engine-2.html |     2 +-
 .../20211108-integrate-with-blender.html      |     2 +-
 ...es-appear-via-the-use-of-the-exporter.html |     2 +-
 ...-experimenting-with-written-workflows.html |     2 +-
 ...g-model-to-work-in-2d-and-with-webrtc.html |     2 +-
 ...r-virtual-worlds-using-ssh-signatures.html |     2 +-
 ...le-v-sekai-using-bots-and-multipliers.html |     2 +-
 ...ry-browser-to-use-alternative-sources.html |     2 +-
 ...-updates-by-delaying-to-2-week-cycles.html |     2 +-
 ...store-service-on-elixir-and-on-sqlite.html |     2 +-
 ...eaking-by-following-quality-checklist.html |     2 +-
 ...-by-creating-an-upstream-pull-request.html |     2 +-
 ...gine-changes-use-a-decision-flowchart.html |     2 +-
 ...deck-hardware-proxy-by-fedora-kinoite.html |     2 +-
 ...k-hardware-proxy-by-fedora-silverblue.html |     2 +-
 ...-open-metaverse-by-working-on-v-sekai.html |     2 +-
 ...1220-network-the-ubisoft-mixer-server.html |     2 +-
 ...211229-run-meetings-using-lean-coffee.html |     2 +-
 ...ter-from-a-webcam-to-the-vmc-protocol.html |     2 +-
 ...d-shapes-to-skeletons-for-performance.html |     2 +-
 .../20220113-change-transform-by-crdt.html    |     2 +-
 .../20220118-convert-gltf-to-a-scene.html     |     2 +-
 ...-to-upload-maps-and-avatars-templates.html |     2 +-
 docs/decisions/20220130-optimize-cicd.html    |     2 +-
 ...-to-record-decisions-write-a-proposal.html |     2 +-
 .../20220131-elixir-desktop-uro.html          |     2 +-
 .../20220131-github-actions-support.html      |     2 +-
 .../20220131-run-own-infrastructure.html      |     2 +-
 ...-gltf-extensions-for-interoperability.html |     2 +-
 ...20220203-create-default-animation-set.html |     2 +-
 ...o-pass by-fixing-spatial-audio-branch.html |     2 +-
 ...06-logging-notifications-from-discord.html |     2 +-
 docs/decisions/20220207-virtual-pets.html     |     2 +-
 .../20220215-uro-deployment-process.html      |     2 +-
 .../decisions/20220217-omi-chan-oni-chan.html |     2 +-
 ...-where-we-re-going-by-planning-vsekai.html |     2 +-
 ...0222-rank-bone-names-with-transformer.html |     2 +-
 ...0222-rank-bone-skeletons-with-xgboost.html |     2 +-
 ...ank-skeleton-bone-names-with-catboost.html |     2 +-
 ...23-store-source-VSK_map-files-via-DVC.html |     2 +-
 .../20220224-v-sekai-version-two-plan.html    |     2 +-
 .../20220228-v-sekai-version-three-plan.html  |     2 +-
 .../20220317-baserow.io-truenas.html          |     2 +-
 ...20317-protect-minumum-spec-steam-deck.html |     2 +-
 .../20220317-use-spec-rough-metal.html        |     2 +-
 .../20220318-merge-retargeting-pr.html        |     2 +-
 .../20220515-profile-using-perf.html          |     2 +-
 docs/decisions/20220531-elixir-uro-dev.html   |     2 +-
 docs/decisions/20220531-truenas-scale.html    |     2 +-
 .../20220601-lightweight-quality-avatars.html |     2 +-
 .../20220605-gocd-pipeline-reset.html         |     2 +-
 .../20220605-host-internal-baserow.html       |     2 +-
 .../20220624-webcam-to-posed-characters.html  |     2 +-
 ...0220820-bake alembic-anim-via-blender.html |     2 +-
 docs/decisions/20220820-cloth-sim.html        |     2 +-
 .../20220820-market-booth-tutorial.html       |     2 +-
 .../20220830-godot-pdf-workflow.html          |     2 +-
 ...-mirror-extend-asset-library-packages.html |     2 +-
 ...16-too-many-branches-on-v-sekai-godot.html |     2 +-
 docs/decisions/20221006-rename-to-main.html   |     2 +-
 .../20221006-unidot-is-optional.html          |     2 +-
 ...20221014-networking-overhaul-proposal.html |     2 +-
 .../20221016-v-sekai-view-replication.html    |     2 +-
 ...0221018-v-sekai-game-update-procedure.html |     2 +-
 ...replication-sync-for-100-000-entities.html |     2 +-
 ...-networking-100000-entities-ownership.html |     2 +-
 ...21019-replicate-sync-100-000-entities.html |     2 +-
 ...-make-it-easier-propose-and-post-bugs.html |     2 +-
 ...rger-worlds-by-server-state-migration.html |     2 +-
 .../20221203-block-direct-pushes-to-main.html |     2 +-
 .../20221203-target-10-minutes-cicd.html      |     2 +-
 .../20221205-debug-linux-export.html          |     2 +-
 ...05-moving-fast-philosophy-development.html |     2 +-
 .../20221205-port-renik-to-many-bone-ik.html  |     2 +-
 ...export-godot-vrm-to-the-asset-library.html |     2 +-
 .../20221212-world-and-character-tools.html   |     2 +-
 ...wershell-autocomplete-use-right-arrow.html |     2 +-
 .../20230106-walking-controller-renik.html    |     2 +-
 .../20230107-elixir-uro-dev-sqlite.html       |     2 +-
 ...230108-bolster-creating-the-metaverse.html |     2 +-
 .../20230108-wmf-video-playback.html          |     2 +-
 .../20230123-face-helmet-capture.html         |     2 +-
 ...lender-with-gltf-extensions-and-godot.html |     2 +-
 .../20230123-no-traversal-loading-screen.html |     2 +-
 docs/decisions/20230123-player-scripting.html |     2 +-
 .../20230123-publish-godot-vrm-4.html         |     2 +-
 .../20230123-ready-the-net-demo.html          |     2 +-
 .../20230123-recording-demo-checklist.html    |     2 +-
 ...123-use-easy-charts-for-observability.html |     2 +-
 ...5-cover-80-95-percent-of-the-userbase.html |     2 +-
 ...game-tablet-interface-we-can-activate.html |     2 +-
 ...community-with-a-reactive-discord-bot.html |     2 +-
 docs/decisions/20230125-possible-futures.html |     2 +-
 ...to-match-compatibile-maps-and-avatars.html |     2 +-
 .../20230125-two-groups-battle-demo.html      |     2 +-
 ...erated-scripting-with-libsql-and-wasm.html |     2 +-
 ...z-we-cannot-compare-the-interpolation.html |     2 +-
 ...pt-best-product-development-practices.html |     2 +-
 .../decisions/20230131-default-test-plan.html |     2 +-
 .../20230131-meeting-at-gdc-2023.html         |     2 +-
 ...end-for-machine-learning-computations.html |     2 +-
 .../20230310-don't-merge-incomplete-work.html |     2 +-
 docs/decisions/20230310-xml-based-tests.html  |     2 +-
 docs/decisions/20230408-v-sekai-launcher.html |     2 +-
 docs/decisions/20230415-load-collaborate.html |     2 +-
 ...cedural-variations-props-envs-avatars.html |     2 +-
 .../20230415-rgbaf-to-store-integers.html     |     2 +-
 .../20230419-limited-tracker-placement.html   |     2 +-
 .../20230419-package-godot-for-pkgin.html     |     2 +-
 .../20230429-git-subrepo-challenges.html      |     2 +-
 docs/decisions/20230429-improve-collab.html   |     2 +-
 docs/decisions/20230429-v-sekai-roadmap.html  |     2 +-
 ...odot-engine-for-image-superresolution.html |     2 +-
 ...0505-automated-avatar-garment-rigging.html |     2 +-
 .../20230505-consistent-v-sekai-naming.html   |     2 +-
 ...5-cross-platform-artwork-distribution.html |     2 +-
 ...05-polygon-mesh-based-sculpting-tools.html |     2 +-
 .../20230505-v-sekai-ai-completion.html       |     2 +-
 ...vatar-publishing-workflow-portability.html |     2 +-
 docs/decisions/20230507-distributed-sim.html  |     2 +-
 docs/decisions/20230507-supabase.html         |     2 +-
 docs/decisions/20230508-novel-3d-views.html   |     2 +-
 .../20230509-wasm-data-exchange.html          |     2 +-
 .../20230516-additional-3d-import.html        |     2 +-
 ...um-nightclub-booth-for-virtual-market.html |     2 +-
 docs/decisions/20230516-v-sekai-roadmap.html  |     2 +-
 ...dd-vrm-omi-personality-gltf-extension.html |     2 +-
 docs/decisions/20230519-v-sekai-roadmap.html  |     2 +-
 .../20230521-audio-jitter-buffer-voip.html    |     2 +-
 .../20230522-JOKE-fictional-blood-combat.html |     2 +-
 docs/decisions/20230523-marketing-cycle.html  |     2 +-
 .../decisions/20230525-animation-ik-node.html |     2 +-
 docs/decisions/20230527-godot-test-game.html  |     2 +-
 docs/decisions/20230527-organization.html     |     2 +-
 .../20230527-server-cdn-session-url.html      |     2 +-
 .../20230527-server-performance-test.html     |     2 +-
 ...230527-server-side-content-validation.html |     2 +-
 docs/decisions/20230527-server-sidecar.html   |     2 +-
 docs/decisions/20230527-v-sekai-roadmap.html  |     2 +-
 .../decisions/20230531-godot-engine-ipad.html |     2 +-
 .../20230531-godot-engine-learning.html       |     2 +-
 .../20230602-limited-tracker-placement.html   |     2 +-
 .../20230602-pmx-module-integration.html      |     2 +-
 docs/decisions/20230602-v-sekai-roadmap.html  |     2 +-
 docs/decisions/20230608-v-sekai-roadmap.html  |     2 +-
 docs/decisions/20230611-wasm-in-v-sekai.html  |     2 +-
 docs/decisions/20230614-llm-statechart.html   |     2 +-
 docs/decisions/20230616-pmx-to-vrm.html       |     2 +-
 docs/decisions/20230618-v-sekai-roadmap.html  |     2 +-
 ...embrane-framework-for-mesh-processing.html |     2 +-
 ...20230619-move-cockroachdb-to-yugabyte.html |     2 +-
 docs/decisions/20230620-doi-github.html       |     2 +-
 .../20230620-t5-jsonformer-xstate.html        |     2 +-
 .../20230623-fdn-reverb-solution.html         |     2 +-
 docs/decisions/20230624-v-sekai-roadmap.html  |     2 +-
 docs/decisions/20230626-godot-vrm1-addon.html |     2 +-
 .../20230630-vsekai-goal-meeting.html         |     2 +-
 .../20230701-vsekai-broken-down-goals.html    |     2 +-
 ...ng-avatar-creation-process-01-regular.html |     2 +-
 ...g-avatar-creation-process-02-advanced.html |     2 +-
 ...719-dual-databases-cockroachdb-khepri.html |     2 +-
 ...30719-pose-kusudama-constraints-in-vr.html |     2 +-
 ...nik-directly-rather-than-many-bone-ik.html |     2 +-
 docs/decisions/20230803-idle-rpg-home.html    |     2 +-
 .../20230803-jolt-gextension-to-module.html   |     2 +-
 .../20230803-publish-vrm-to-assetlibrary.html |     2 +-
 .../20230803-subrepo-addon-management.html    |     2 +-
 docs/decisions/20230804-dokku.html            |     2 +-
 docs/decisions/20230806-music-gen.html        |     2 +-
 ...v-sekai-ipad-projection-compatibility.html |     2 +-
 .../decisions/20230811-punchline-reports.html |     2 +-
 .../20230812-constraint-all-bones.html        |     2 +-
 docs/decisions/20230812-gocd-agent-setup.html |     2 +-
 ...-and-merge-procedure-source-code-tree.html |     2 +-
 .../20230812-vsekai-update-process.html       |     2 +-
 ...lender-runner-into-membrane-framework.html |     2 +-
 ...adcaster-into-membrane-framework copy.html |     2 +-
 docs/decisions/20230819-train-game.html       |     2 +-
 .../20230823-speech-to-blendshapes.html       |     2 +-
 docs/decisions/20230824-subdiv-for-lods.html  |     2 +-
 docs/decisions/20230829-omifest-2023.html     |     2 +-
 .../20230830-better-backend-services.html     |     2 +-
 .../20230830-better-object-pick.html          |     2 +-
 .../20230830-generating-v-sekai-worlds.html   |     2 +-
 docs/decisions/20230831-fixing-menus.html     |     2 +-
 .../20230831-fixing-upload-limits.html        |     2 +-
 .../20230903-replicate-vrm-transform.html     |     2 +-
 ...able-screen-generative-assistant-ggml.html |     2 +-
 ...11-can-poly-green-coords-extend-to-3d.html |     2 +-
 docs/decisions/20230911-first-alpha-tag.html  |     2 +-
 docs/decisions/20230911-xpr.exs.html          |     2 +-
 .../20230911-xr-grid-with-drawing.html        |     2 +-
 ...230912-target-most-popular-resolution.html |     2 +-
 docs/decisions/20230913-V-Sekai-bugs.html     |     2 +-
 .../20230920-godot-project-search.html        |     2 +-
 ...20230922-spacetime-shadow-shards-sync.html |     2 +-
 ...0231019-quest3-mocap-steam-lighthouse.html |     2 +-
 .../20231020-llama-cpp-mistral-npc.html       |     2 +-
 .../20231022-hover-to-ocean-game.html         |     2 +-
 .../20231024-finetuning-workflow.html         |     2 +-
 .../20231024-training-simulators.html         |     2 +-
 .../20231026-blender-steam-beta-version.html  |     2 +-
 .../20231027-apartment-building-vr.html       |     2 +-
 .../20231027-drawing-concept-to-blockout.html |     2 +-
 .../20231027-dreamcraft3d-workflow.html       |     2 +-
 ...-write-a-list-of-github-pull-requests.html |     2 +-
 .../20231104-flatbuffer_packed_scenes.html    |     2 +-
 .../20231105-pdf-embed-raster-svg-vr.html     |     2 +-
 ...31108-ansible-new-server-provisioning.html |     2 +-
 ...231108-munich-godot-engine-conference.html |     2 +-
 .../20231108-neon-1-gb-scene-storage.html     |     2 +-
 docs/decisions/20231108-neon-postgresql.html  |     2 +-
 ...108-neon-vercel-functions-toy-problem.html |     2 +-
 ...0231108-nier-automata-world-expansion.html |     2 +-
 ...20231108-postgres-bytea-optimizations.html |     2 +-
 docs/decisions/20231108-v-sekai-chat-bot.html |     2 +-
 .../20231109-discord-polygonjs-generator.html |     2 +-
 .../20231110-ai-based-outlier-detection.html  |     2 +-
 .../20231110-better-pipeline-tools.html       |     2 +-
 .../20231110-blender-manual-t-pose.html       |     2 +-
 .../20231110-efficient-llm-training.html      |     2 +-
 .../20231110-v-sekai-dependencies.html        |     2 +-
 docs/decisions/20231111-ayon-evaluation.html  |     2 +-
 docs/decisions/20231112-archive-projects.html |     2 +-
 .../20231112-validation-service.html          |     2 +-
 ...1114-elixir-definition-of-godot-types.html |     2 +-
 .../20231114-maintain-svgcleaner.html         |     2 +-
 ...pload-creative-commons-fbx-test-files.html |     2 +-
 docs/decisions/20231125-v-sekai-report.html   |     2 +-
 docs/decisions/20231126-v-sekai-report.html   |     2 +-
 docs/decisions/20231127-performance-test.html |     2 +-
 .../20231201-headless-launcher-backend.html   |     2 +-
 .../20231201-xr-hands-animation-node.html     |     2 +-
 ...231203-graphsage-embedding-generation.html |     2 +-
 .../20231203-mesh-rwkv-test-metrics.html      |     2 +-
 docs/decisions/20231203-mesh-rwkv.html        |     2 +-
 .../20231209-appium-testing-fbx-to-gltf.html  |     2 +-
 .../20231209-appium-testing-win11.html        |     2 +-
 docs/decisions/20231218-mtlx-try-two.html     |     2 +-
 .../20231225-mesh-transformer-clothing.html   |     2 +-
 ...1225-mesh-transformer-facial-features.html |     2 +-
 .../20231226-furniture-vs-organic.html        |     2 +-
 .../20231227-blue-green-shadows.html          |     2 +-
 .../decisions/20231227-punchline-reports.html |     2 +-
 docs/decisions/20231228-v-sekai-slogan.html   |     2 +-
 docs/decisions/20231229-byobu.html            |     2 +-
 docs/decisions/20231229-mRemoteNG.html        |     2 +-
 .../20231230-spatiallabs-openvr.html          |     2 +-
 .../20240105-1-meter-128-quantize.html        |     2 +-
 .../20240110-magical-girls-college-novel.html |     2 +-
 ...it-clothing-on-humans-without-tearing.html |     2 +-
 docs/decisions/20240111-fspy.html             |     2 +-
 docs/decisions/20240117-pivot-painting.html   |     2 +-
 .../20240120-vr-armature-system.html          |     2 +-
 ...0240121-easy-diffusion-fedora-install.html |     2 +-
 .../decisions/20240121-install-tailscale.html |     2 +-
 .../20240121-livebook-fedora-install.html     |     2 +-
 docs/decisions/20240121-mac-setup.html        |     2 +-
 ...240127-urban-explorer-gdc-2024-sample.html |     2 +-
 ...tomization-with-ai-facial-expressions.html |     2 +-
 docs/decisions/20240217-container-2-wasm.html |     2 +-
 .../20240217-documentation-guidelines.html    |     2 +-
 ...17-essential-typle-normalization-form.html |     2 +-
 .../20240217-intended-effort-versioning.html  |     2 +-
 .../20240217-workload-benchmarking.html       |     2 +-
 docs/decisions/20240218-blender-to-godot.html |     2 +-
 .../20240218-vrm-acronym-correction.html      |     2 +-
 .../20240218-vrm-substance-editor.html        |     2 +-
 docs/decisions/20240305-v-sekai-launcher.html |     2 +-
 docs/decisions/20240307-rabbitmq-ra.html      |     2 +-
 docs/decisions/20240314-live-collab.html      |     2 +-
 docs/decisions/20240324-v-sekai-as-slc.html   |     2 +-
 .../20240325-fdb-sqlite-blender-godot.html    |     2 +-
 .../20240325-table-avatar-embedded-xmp.html   |     2 +-
 docs/decisions/20240326-heartstrings-vr.html  |     2 +-
 ...240326-verifying-and-finetuning-plans.html |     2 +-
 .../20240329-ready-to-go-kit-windows-11.html  |     2 +-
 ...20240330-bitnami-rancher-helm-catalog.html |     2 +-
 docs/decisions/20240330-cicd-gitlab.html      |     2 +-
 docs/decisions/20240330-gitlab-helm.html      |     2 +-
 .../20240330-hyperv-harvester-test.html       |     2 +-
 .../decisions/20240330-k8s-harvester-hci.html |     2 +-
 .../20240331-vrc-vrm-compatibility.html       |     2 +-
 docs/decisions/20240401-shader-graphic.html   |     2 +-
 .../20240406-itch-github-actions.html         |     2 +-
 .../decisions/20240406-web-based-explore.html |     2 +-
 .../20240407-pcvr-vs-standalone.html          |     2 +-
 docs/decisions/20240409-crud-godot-tiles.html |     2 +-
 .../20240409-elixir-raft-vs-sqlite-fdb.html   |     2 +-
 .../20240410-data-storage-elixir.html         |     2 +-
 .../20240411-elixir-libgodot-bundlex.html     |     2 +-
 .../20240411-elixir-libgodot-zig.html         |     2 +-
 ...player-movement-with-parented-obejcts.html |     2 +-
 ...0413-calling-opensource-llm-with-aria.html |     2 +-
 ...ing-quad-based-meshgpt-with-40gb-vram.html |     2 +-
 ...20240416-previewer-upload-gltf-to-glb.html |     2 +-
 docs/decisions/20240418-college-quest.html    |     2 +-
 ...building-metaverse-with-glue-mechanic.html |     2 +-
 .../20240424-reset-steamvr-controllers.html   |     2 +-
 .../20240425-proposal-prompt-system.html      |     2 +-
 docs/decisions/20240425-recharge-cycle.html   |     2 +-
 .../decisions/20240502-gltf-fbx-tscn-vrm.html |     2 +-
 ...02-install-windows-on-older-computers.html |     2 +-
 ...0502-membrane-framework-identity-post.html |     2 +-
 .../20240502-mesh-object-sync-benchmark.html  |     2 +-
 docs/decisions/20240502-mvsqlite-launchd.html |     2 +-
 .../20240502-where-can-I-use-gltf.html        |     2 +-
 docs/decisions/20240511-review-80-vr.html     |     2 +-
 .../20240511-wasm-cache-incident.html         |     2 +-
 docs/decisions/20240522-discord-bot.html      |     2 +-
 .../20240522-discord-inworld-portal.html      |     2 +-
 .../20240522-shader-motion-to-bvh.html        |     2 +-
 .../decisions/20240522-webrtc-relay-test.html |     2 +-
 ...20240528-pipeline-godot-wasm-importer.html |     2 +-
 ...240529-improve-godot-import-ecosystem.html |     2 +-
 ...anagement-for-godot-engine-in-v-sekai.html |     2 +-
 ...eton-mirroring-use-the-godot-humanoid.html |     2 +-
 ...8-skin-weight-transfer-skeleton-merge.html |     2 +-
 .../20240611-lower-learning-rate.html         |     2 +-
 docs/decisions/20240611-test-1x-and-4x.html   |     2 +-
 docs/decisions/20240613-1k-quad-limit.html    |     2 +-
 ...ifying-the-mesh-transformer-for-quads.html |     2 +-
 ...13-training-dataset-creation-with-csg.html |     2 +-
 docs/decisions/20240613-training-dataset.html |     2 +-
 .../20240615-what-is-mesh-transformers.html   |     2 +-
 ...0240616-request-for-quad-mesh-dataset.html |     2 +-
 .../20240618-4-player-test-vsekai.html        |     2 +-
 .../20240618-schedule-as-binary-tree.html     |     2 +-
 .../20240621-caption-photos-for-cicd.html     |     2 +-
 .../20240621-proposal-template copy.html      |     2 +-
 .../20240622-build-for-many-platforms.html    |     2 +-
 ...240622-gocd-agent-docker-image-update.html |     2 +-
 .../20240622-process-for-testing-vsekai.html  |     2 +-
 .../20240623-do-cdn-for-launcher.html         |     2 +-
 .../20240623-only-save-tools-in-our-cdn.html  |     2 +-
 .../20240623-talk-length-prototypes.html      |     2 +-
 .../20240623-what-is-uro-backend.html         |     2 +-
 ...40626-update-python3-macos-certicates.html |     2 +-
 .../20240627-every-commit-push-pass-cicd.html |     2 +-
 .../20240627-gdextension-as-libriscv.html     |     2 +-
 ...se-motion-transformers-for-prediction.html |     2 +-
 docs/decisions/20240705-rpg_town.html         |     2 +-
 ...0706-motion-capture-bill-of-materials.html |     2 +-
 .../20240708-vsekai-my-life-as-a-queen.html   |     2 +-
 ...20240709-anwave-set-nvidia-watt-limit.html |     2 +-
 docs/decisions/20240709-wired-first.html      |     2 +-
 .../20240710-art-direction-in-vsekai.html     |     2 +-
 ...-cc0-base-mesh-to-godot-engine-t-pose.html |     2 +-
 ...240710-platform-focus-on-pcvr-and-web.html |     2 +-
 ...0240710-use-godot-engine-web-threaded.html |     2 +-
 ...20240710-use-webrtc-to-native-interop.html |     2 +-
 .../20240710-web-and-pcvr-networking.html     |     2 +-
 ...se-shrinkwrap-blender-modiifer-to-fit.html |     2 +-
 ...240715-vrchat-networking-mental-model.html |     2 +-
 .../20240717-core-vsekai-scripting.html       |     2 +-
 .../20240810-steamvr-dongles-separate.html    |     2 +-
 .../20240824-ffmpeg-wav-mic-speaker-play.html |     2 +-
 ...e-lane-depletion-thunderbolt-4-issues.html |     2 +-
 ...0240830-use-dokku-to-host-vsk-backend.html |     2 +-
 ...tracker-configuration-and-constraints.html |     2 +-
 ...odot-engine-xr-elite-conference-setup.html |     2 +-
 docs/decisions/20241001-small-game-tools.html |     2 +-
 ...6-restore-onedrive-shortcut-overrides.html |     2 +-
 ...41011-recovering-makehuman-parameters.html |     2 +-
 docs/decisions/20241014-app-updater.html      |     2 +-
 .../20241014-basic-realtime-interaction.html  |     2 +-
 .../20241014-xr-interface-for-rigging.html    |     2 +-
 ...0241016-instantiating-v-sekai-content.html |     2 +-
 ...ence-between-capsules-and-mesh-volume.html |     2 +-
 ...use-data-tables-for-godot-constraints.html |     2 +-
 .../ai-assisted-proposal-style-guide.html     |     2 +-
 .../attachments/pitch_apple_vision_01.html    |     2 +-
 .../attachments/pitch_general_02.html         |     2 +-
 .../decisions/attachments/project_mirage.html |     2 +-
 .../thunderbolt_install_windows.html          |     2 +-
 .../attachments/virtual_pets/LICENSE.html     |     2 +-
 docs/decisions/present-proposal-template.html |     2 +-
 docs/index.html                               |     2 +-
 docs/{plan.html => plans.html}                |     6 +-
 docs/search.json                              | 33148 ++++++++--------
 docs/sitemap.xml                              |  2030 +-
 513 files changed, 18641 insertions(+), 18641 deletions(-)
 rename docs/{plan.html => plans.html} (99%)

diff --git a/docs/authors.html b/docs/authors.html
index 83bd5a2a27..30ba5e4d2a 100644
--- a/docs/authors.html
+++ b/docs/authors.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="./plans.qmd"> 
+    <a class="nav-link" href="./plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/changelog.html b/docs/changelog.html
index ae97665b80..2db1c1d5f3 100644
--- a/docs/changelog.html
+++ b/docs/changelog.html
@@ -162,7 +162,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="./plans.qmd"> 
+    <a class="nav-link" href="./plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
@@ -240,197 +240,197 @@ <h1 class="title">Changes to V-Sekai</h1>
 </tr>
 </thead>
 <tbody class="list">
-<tr data-index="0" data-listing-file-modified-sort="1730535490014" data-listing-reading-time-sort="2" data-listing-word-count-sort="293" data-listing-title-sort="V-Sekai Changelog - October 2024" data-listing-filename-sort="20241003-changelog.md">
+<tr data-index="0" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="2" data-listing-word-count-sort="293" data-listing-title-sort="V-Sekai Changelog - October 2024" data-listing-filename-sort="20241003-changelog.md">
 <td>
 <a href="./changelog/2024/20241003-changelog.html" class="title listing-title">V-Sekai Changelog - October 2024</a>
 </td>
 </tr>
-<tr data-index="1" data-listing-file-modified-sort="1730535490014" data-listing-reading-time-sort="2" data-listing-word-count-sort="212" data-listing-title-sort="V-Sekai Changelog - September 2024" data-listing-filename-sort="20240901-changelog.md">
+<tr data-index="1" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="2" data-listing-word-count-sort="212" data-listing-title-sort="V-Sekai Changelog - September 2024" data-listing-filename-sort="20240901-changelog.md">
 <td>
 <a href="./changelog/2024/20240901-changelog.html" class="title listing-title">V-Sekai Changelog - September 2024</a>
 </td>
 </tr>
-<tr data-index="2" data-listing-file-modified-sort="1730535490014" data-listing-reading-time-sort="2" data-listing-word-count-sort="274" data-listing-title-sort="V-Sekai Changelog - July 2024" data-listing-filename-sort="20240701-changelog.md">
+<tr data-index="2" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="2" data-listing-word-count-sort="274" data-listing-title-sort="V-Sekai Changelog - July 2024" data-listing-filename-sort="20240701-changelog.md">
 <td>
 <a href="./changelog/2024/20240701-changelog.html" class="title listing-title">V-Sekai Changelog - July 2024</a>
 </td>
 </tr>
-<tr data-index="3" data-listing-file-modified-sort="1730535490014" data-listing-reading-time-sort="2" data-listing-word-count-sort="290" data-listing-title-sort="Special Notice: V-Sekai 2023-2024" data-listing-filename-sort="20240625-changelog.md">
+<tr data-index="3" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="2" data-listing-word-count-sort="290" data-listing-title-sort="Special Notice: V-Sekai 2023-2024" data-listing-filename-sort="20240625-changelog.md">
 <td>
 <a href="./changelog/2024/20240625-changelog.html" class="title listing-title">Special Notice: V-Sekai 2023-2024</a>
 </td>
 </tr>
-<tr data-index="4" data-listing-file-modified-sort="1730535490014" data-listing-reading-time-sort="2" data-listing-word-count-sort="212" data-listing-title-sort="V-Sekai Changelog - June 2024" data-listing-filename-sort="20240603-changelog.md">
+<tr data-index="4" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="2" data-listing-word-count-sort="212" data-listing-title-sort="V-Sekai Changelog - June 2024" data-listing-filename-sort="20240603-changelog.md">
 <td>
 <a href="./changelog/2024/20240603-changelog.html" class="title listing-title">V-Sekai Changelog - June 2024</a>
 </td>
 </tr>
-<tr data-index="5" data-listing-file-modified-sort="1730535490014" data-listing-reading-time-sort="1" data-listing-word-count-sort="84" data-listing-title-sort="V-Sekai Changelog - May 2024" data-listing-filename-sort="20240505-changelog.md">
+<tr data-index="5" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="1" data-listing-word-count-sort="84" data-listing-title-sort="V-Sekai Changelog - May 2024" data-listing-filename-sort="20240505-changelog.md">
 <td>
 <a href="./changelog/2024/20240505-changelog.html" class="title listing-title">V-Sekai Changelog - May 2024</a>
 </td>
 </tr>
-<tr data-index="6" data-listing-file-modified-sort="1730535490014" data-listing-reading-time-sort="1" data-listing-word-count-sort="82" data-listing-title-sort="V-Sekai Changelog - March 2024" data-listing-filename-sort="20240330-changelog.md">
+<tr data-index="6" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="1" data-listing-word-count-sort="82" data-listing-title-sort="V-Sekai Changelog - March 2024" data-listing-filename-sort="20240330-changelog.md">
 <td>
 <a href="./changelog/2024/20240330-changelog.html" class="title listing-title">V-Sekai Changelog - March 2024</a>
 </td>
 </tr>
-<tr data-index="7" data-listing-file-modified-sort="1730535490014" data-listing-reading-time-sort="2" data-listing-word-count-sort="344" data-listing-title-sort="V-Sekai Changelog - February 2024" data-listing-filename-sort="20240202-changelog.md">
+<tr data-index="7" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="2" data-listing-word-count-sort="344" data-listing-title-sort="V-Sekai Changelog - February 2024" data-listing-filename-sort="20240202-changelog.md">
 <td>
 <a href="./changelog/2024/20240202-changelog.html" class="title listing-title">V-Sekai Changelog - February 2024</a>
 </td>
 </tr>
-<tr data-index="8" data-listing-file-modified-sort="1730535490014" data-listing-reading-time-sort="1" data-listing-word-count-sort="71" data-listing-title-sort="V-Sekai Changelog - January 2024" data-listing-filename-sort="20240101-changelog.md">
+<tr data-index="8" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="1" data-listing-word-count-sort="71" data-listing-title-sort="V-Sekai Changelog - January 2024" data-listing-filename-sort="20240101-changelog.md">
 <td>
 <a href="./changelog/2024/20240101-changelog.html" class="title listing-title">V-Sekai Changelog - January 2024</a>
 </td>
 </tr>
-<tr data-index="9" data-listing-file-modified-sort="1730535490014" data-listing-reading-time-sort="1" data-listing-word-count-sort="198" data-listing-title-sort="V-Sekai Changelog - December 2023" data-listing-filename-sort="20231207-changelog.md">
+<tr data-index="9" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="1" data-listing-word-count-sort="198" data-listing-title-sort="V-Sekai Changelog - December 2023" data-listing-filename-sort="20231207-changelog.md">
 <td>
 <a href="./changelog/2023/20231207-changelog.html" class="title listing-title">V-Sekai Changelog - December 2023</a>
 </td>
 </tr>
-<tr data-index="10" data-listing-file-modified-sort="1730535490014" data-listing-reading-time-sort="3" data-listing-word-count-sort="494" data-listing-title-sort="V-Sekai Changelog - November 2023" data-listing-filename-sort="20231109-changelog.md">
+<tr data-index="10" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="3" data-listing-word-count-sort="494" data-listing-title-sort="V-Sekai Changelog - November 2023" data-listing-filename-sort="20231109-changelog.md">
 <td>
 <a href="./changelog/2023/20231109-changelog.html" class="title listing-title">V-Sekai Changelog - November 2023</a>
 </td>
 </tr>
-<tr data-index="11" data-listing-file-modified-sort="1730535490014" data-listing-reading-time-sort="2" data-listing-word-count-sort="260" data-listing-title-sort="V-Sekai Changelog - October 2023" data-listing-filename-sort="20231001-changelog.md">
+<tr data-index="11" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="2" data-listing-word-count-sort="260" data-listing-title-sort="V-Sekai Changelog - October 2023" data-listing-filename-sort="20231001-changelog.md">
 <td>
 <a href="./changelog/2023/20231001-changelog.html" class="title listing-title">V-Sekai Changelog - October 2023</a>
 </td>
 </tr>
-<tr data-index="12" data-listing-file-modified-sort="1730535490014" data-listing-reading-time-sort="2" data-listing-word-count-sort="305" data-listing-title-sort="V-Sekai Changelog - September 2023" data-listing-filename-sort="20230901-changelog.md">
+<tr data-index="12" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="2" data-listing-word-count-sort="305" data-listing-title-sort="V-Sekai Changelog - September 2023" data-listing-filename-sort="20230901-changelog.md">
 <td>
 <a href="./changelog/2023/20230901-changelog.html" class="title listing-title">V-Sekai Changelog - September 2023</a>
 </td>
 </tr>
-<tr data-index="13" data-listing-file-modified-sort="1730535490014" data-listing-reading-time-sort="3" data-listing-word-count-sort="476" data-listing-title-sort="V-Sekai Changelog - August 2023" data-listing-filename-sort="20230801-changelog.md">
+<tr data-index="13" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="3" data-listing-word-count-sort="476" data-listing-title-sort="V-Sekai Changelog - August 2023" data-listing-filename-sort="20230801-changelog.md">
 <td>
 <a href="./changelog/2023/20230801-changelog.html" class="title listing-title">V-Sekai Changelog - August 2023</a>
 </td>
 </tr>
-<tr data-index="14" data-listing-file-modified-sort="1730535490014" data-listing-reading-time-sort="1" data-listing-word-count-sort="173" data-listing-title-sort="V-Sekai Changelog - July 2023" data-listing-filename-sort="20230701-changelog.md">
+<tr data-index="14" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="1" data-listing-word-count-sort="173" data-listing-title-sort="V-Sekai Changelog - July 2023" data-listing-filename-sort="20230701-changelog.md">
 <td>
 <a href="./changelog/2023/20230701-changelog.html" class="title listing-title">V-Sekai Changelog - July 2023</a>
 </td>
 </tr>
-<tr data-index="15" data-listing-file-modified-sort="1730535490014" data-listing-reading-time-sort="4" data-listing-word-count-sort="629" data-listing-title-sort="V-Sekai Changelog - 2023-06" data-listing-filename-sort="20230601-changelog.md">
+<tr data-index="15" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="4" data-listing-word-count-sort="629" data-listing-title-sort="V-Sekai Changelog - 2023-06" data-listing-filename-sort="20230601-changelog.md">
 <td>
 <a href="./changelog/2023/20230601-changelog.html" class="title listing-title">V-Sekai Changelog - 2023-06</a>
 </td>
 </tr>
-<tr data-index="16" data-listing-file-modified-sort="1730535490014" data-listing-reading-time-sort="2" data-listing-word-count-sort="300" data-listing-title-sort="V-Sekai Changelog - 2023-05" data-listing-filename-sort="20230501-changelog.md">
+<tr data-index="16" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="2" data-listing-word-count-sort="300" data-listing-title-sort="V-Sekai Changelog - 2023-05" data-listing-filename-sort="20230501-changelog.md">
 <td>
 <a href="./changelog/2023/20230501-changelog.html" class="title listing-title">V-Sekai Changelog - 2023-05</a>
 </td>
 </tr>
-<tr data-index="17" data-listing-file-modified-sort="1730535490014" data-listing-reading-time-sort="7" data-listing-word-count-sort="1376" data-listing-title-sort="V-Sekai Changelog - 2023-03" data-listing-filename-sort="20230301-changelog.md">
+<tr data-index="17" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="7" data-listing-word-count-sort="1376" data-listing-title-sort="V-Sekai Changelog - 2023-03" data-listing-filename-sort="20230301-changelog.md">
 <td>
 <a href="./changelog/2023/20230301-changelog.html" class="title listing-title">V-Sekai Changelog - 2023-03</a>
 </td>
 </tr>
-<tr data-index="18" data-listing-file-modified-sort="1730535490014" data-listing-reading-time-sort="1" data-listing-word-count-sort="134" data-listing-title-sort="V-Sekai Changelog - 2023-02" data-listing-filename-sort="20230201-changelog.md">
+<tr data-index="18" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="1" data-listing-word-count-sort="134" data-listing-title-sort="V-Sekai Changelog - 2023-02" data-listing-filename-sort="20230201-changelog.md">
 <td>
 <a href="./changelog/2023/20230201-changelog.html" class="title listing-title">V-Sekai Changelog - 2023-02</a>
 </td>
 </tr>
-<tr data-index="19" data-listing-file-modified-sort="1730535490014" data-listing-reading-time-sort="1" data-listing-word-count-sort="7" data-listing-title-sort="V-Sekai Changelog - 2023-01" data-listing-filename-sort="20230101-changelog.md">
+<tr data-index="19" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="1" data-listing-word-count-sort="7" data-listing-title-sort="V-Sekai Changelog - 2023-01" data-listing-filename-sort="20230101-changelog.md">
 <td>
 <a href="./changelog/2023/20230101-changelog.html" class="title listing-title">V-Sekai Changelog - 2023-01</a>
 </td>
 </tr>
-<tr data-index="20" data-listing-file-modified-sort="1730535490014" data-listing-reading-time-sort="2" data-listing-word-count-sort="230" data-listing-title-sort="V-Sekai Changelog - 2022-12" data-listing-filename-sort="20221201-changelog.md">
+<tr data-index="20" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="2" data-listing-word-count-sort="230" data-listing-title-sort="V-Sekai Changelog - 2022-12" data-listing-filename-sort="20221201-changelog.md">
 <td>
 <a href="./changelog/2022/20221201-changelog.html" class="title listing-title">V-Sekai Changelog - 2022-12</a>
 </td>
 </tr>
-<tr data-index="21" data-listing-file-modified-sort="1730535490014" data-listing-reading-time-sort="2" data-listing-word-count-sort="267" data-listing-title-sort="V-Sekai Changelog - 2022-11" data-listing-filename-sort="20221101-changelog.md">
+<tr data-index="21" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="2" data-listing-word-count-sort="267" data-listing-title-sort="V-Sekai Changelog - 2022-11" data-listing-filename-sort="20221101-changelog.md">
 <td>
 <a href="./changelog/2022/20221101-changelog.html" class="title listing-title">V-Sekai Changelog - 2022-11</a>
 </td>
 </tr>
-<tr data-index="22" data-listing-file-modified-sort="1730535490014" data-listing-reading-time-sort="8" data-listing-word-count-sort="1452" data-listing-title-sort="V-Sekai Changelog - 2022-10" data-listing-filename-sort="20221001-changelog.md">
+<tr data-index="22" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="8" data-listing-word-count-sort="1452" data-listing-title-sort="V-Sekai Changelog - 2022-10" data-listing-filename-sort="20221001-changelog.md">
 <td>
 <a href="./changelog/2022/20221001-changelog.html" class="title listing-title">V-Sekai Changelog - 2022-10</a>
 </td>
 </tr>
-<tr data-index="23" data-listing-file-modified-sort="1730535490014" data-listing-reading-time-sort="1" data-listing-word-count-sort="162" data-listing-title-sort="V-Sekai Changelog - 2022-09" data-listing-filename-sort="20220901-changelog.md">
+<tr data-index="23" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="1" data-listing-word-count-sort="162" data-listing-title-sort="V-Sekai Changelog - 2022-09" data-listing-filename-sort="20220901-changelog.md">
 <td>
 <a href="./changelog/2022/20220901-changelog.html" class="title listing-title">V-Sekai Changelog - 2022-09</a>
 </td>
 </tr>
-<tr data-index="24" data-listing-file-modified-sort="1730535490014" data-listing-reading-time-sort="1" data-listing-word-count-sort="77" data-listing-title-sort="V-Sekai Changelog - 2022-08" data-listing-filename-sort="20220801-changelog.md">
+<tr data-index="24" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="1" data-listing-word-count-sort="77" data-listing-title-sort="V-Sekai Changelog - 2022-08" data-listing-filename-sort="20220801-changelog.md">
 <td>
 <a href="./changelog/2022/20220801-changelog.html" class="title listing-title">V-Sekai Changelog - 2022-08</a>
 </td>
 </tr>
-<tr data-index="25" data-listing-file-modified-sort="1730535490014" data-listing-reading-time-sort="3" data-listing-word-count-sort="427" data-listing-title-sort="V-Sekai Changelog - 2022-06" data-listing-filename-sort="20220601-changelog.md">
+<tr data-index="25" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="3" data-listing-word-count-sort="427" data-listing-title-sort="V-Sekai Changelog - 2022-06" data-listing-filename-sort="20220601-changelog.md">
 <td>
 <a href="./changelog/2022/20220601-changelog.html" class="title listing-title">V-Sekai Changelog - 2022-06</a>
 </td>
 </tr>
-<tr data-index="26" data-listing-file-modified-sort="1730535490014" data-listing-reading-time-sort="1" data-listing-word-count-sort="115" data-listing-title-sort="V-Sekai Changelog - 2022-05" data-listing-filename-sort="20220501-changelog.md">
+<tr data-index="26" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="1" data-listing-word-count-sort="115" data-listing-title-sort="V-Sekai Changelog - 2022-05" data-listing-filename-sort="20220501-changelog.md">
 <td>
 <a href="./changelog/2022/20220501-changelog.html" class="title listing-title">V-Sekai Changelog - 2022-05</a>
 </td>
 </tr>
-<tr data-index="27" data-listing-file-modified-sort="1730535490014" data-listing-reading-time-sort="3" data-listing-word-count-sort="459" data-listing-title-sort="V-Sekai Changelog - 2022-04" data-listing-filename-sort="20220401-changelog.md">
+<tr data-index="27" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="3" data-listing-word-count-sort="459" data-listing-title-sort="V-Sekai Changelog - 2022-04" data-listing-filename-sort="20220401-changelog.md">
 <td>
 <a href="./changelog/2022/20220401-changelog.html" class="title listing-title">V-Sekai Changelog - 2022-04</a>
 </td>
 </tr>
-<tr data-index="28" data-listing-file-modified-sort="1730535490014" data-listing-reading-time-sort="2" data-listing-word-count-sort="227" data-listing-title-sort="V-Sekai Changelog - 2022-03" data-listing-filename-sort="20220301-changelog.md">
+<tr data-index="28" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="2" data-listing-word-count-sort="227" data-listing-title-sort="V-Sekai Changelog - 2022-03" data-listing-filename-sort="20220301-changelog.md">
 <td>
 <a href="./changelog/2022/20220301-changelog.html" class="title listing-title">V-Sekai Changelog - 2022-03</a>
 </td>
 </tr>
-<tr data-index="29" data-listing-file-modified-sort="1730535490014" data-listing-reading-time-sort="1" data-listing-word-count-sort="152" data-listing-title-sort="V-Sekai Changelog - 2022-02" data-listing-filename-sort="20220201-changelog.md">
+<tr data-index="29" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="1" data-listing-word-count-sort="152" data-listing-title-sort="V-Sekai Changelog - 2022-02" data-listing-filename-sort="20220201-changelog.md">
 <td>
 <a href="./changelog/2022/20220201-changelog.html" class="title listing-title">V-Sekai Changelog - 2022-02</a>
 </td>
 </tr>
-<tr data-index="30" data-listing-file-modified-sort="1730535490014" data-listing-reading-time-sort="1" data-listing-word-count-sort="79" data-listing-title-sort="V-Sekai Changelog - 2022-01" data-listing-filename-sort="20220101-changelog.md">
+<tr data-index="30" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="1" data-listing-word-count-sort="79" data-listing-title-sort="V-Sekai Changelog - 2022-01" data-listing-filename-sort="20220101-changelog.md">
 <td>
 <a href="./changelog/2022/20220101-changelog.html" class="title listing-title">V-Sekai Changelog - 2022-01</a>
 </td>
 </tr>
-<tr data-index="31" data-listing-file-modified-sort="1730535490014" data-listing-reading-time-sort="2" data-listing-word-count-sort="354" data-listing-title-sort="V-Sekai Changelog - 2021-11" data-listing-filename-sort="20211101-changelog.md">
+<tr data-index="31" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="2" data-listing-word-count-sort="354" data-listing-title-sort="V-Sekai Changelog - 2021-11" data-listing-filename-sort="20211101-changelog.md">
 <td>
 <a href="./changelog/2021/20211101-changelog.html" class="title listing-title">V-Sekai Changelog - 2021-11</a>
 </td>
 </tr>
-<tr data-index="32" data-listing-file-modified-sort="1730535490014" data-listing-reading-time-sort="8" data-listing-word-count-sort="1453" data-listing-title-sort="V-Sekai Changelog - 2021-10" data-listing-filename-sort="20211001-changelog.md">
+<tr data-index="32" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="8" data-listing-word-count-sort="1453" data-listing-title-sort="V-Sekai Changelog - 2021-10" data-listing-filename-sort="20211001-changelog.md">
 <td>
 <a href="./changelog/2021/20211001-changelog.html" class="title listing-title">V-Sekai Changelog - 2021-10</a>
 </td>
 </tr>
-<tr data-index="33" data-listing-file-modified-sort="1730535490014" data-listing-reading-time-sort="10" data-listing-word-count-sort="1895" data-listing-title-sort="V-Sekai Changelog - 2021-09" data-listing-filename-sort="20210901-changelog.md">
+<tr data-index="33" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="10" data-listing-word-count-sort="1895" data-listing-title-sort="V-Sekai Changelog - 2021-09" data-listing-filename-sort="20210901-changelog.md">
 <td>
 <a href="./changelog/2021/20210901-changelog.html" class="title listing-title">V-Sekai Changelog - 2021-09</a>
 </td>
 </tr>
-<tr data-index="34" data-listing-file-modified-sort="1730535490014" data-listing-reading-time-sort="5" data-listing-word-count-sort="911" data-listing-title-sort="V-Sekai Changelog - 2021-08" data-listing-filename-sort="20210801-changelog.md">
+<tr data-index="34" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="5" data-listing-word-count-sort="911" data-listing-title-sort="V-Sekai Changelog - 2021-08" data-listing-filename-sort="20210801-changelog.md">
 <td>
 <a href="./changelog/2021/20210801-changelog.html" class="title listing-title">V-Sekai Changelog - 2021-08</a>
 </td>
 </tr>
-<tr data-index="35" data-listing-file-modified-sort="1730535490014" data-listing-reading-time-sort="6" data-listing-word-count-sort="1026" data-listing-title-sort="V-Sekai Changelog - 2021-07" data-listing-filename-sort="20210701-changelog.md">
+<tr data-index="35" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="6" data-listing-word-count-sort="1026" data-listing-title-sort="V-Sekai Changelog - 2021-07" data-listing-filename-sort="20210701-changelog.md">
 <td>
 <a href="./changelog/2021/20210701-changelog.html" class="title listing-title">V-Sekai Changelog - 2021-07</a>
 </td>
 </tr>
-<tr data-index="36" data-listing-file-modified-sort="1730535490014" data-listing-reading-time-sort="10" data-listing-word-count-sort="1961" data-listing-title-sort="V-Sekai Changelog - 2021-06" data-listing-filename-sort="20210601-changelog.md">
+<tr data-index="36" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="10" data-listing-word-count-sort="1961" data-listing-title-sort="V-Sekai Changelog - 2021-06" data-listing-filename-sort="20210601-changelog.md">
 <td>
 <a href="./changelog/2021/20210601-changelog.html" class="title listing-title">V-Sekai Changelog - 2021-06</a>
 </td>
 </tr>
-<tr data-index="37" data-listing-file-modified-sort="1730535490014" data-listing-reading-time-sort="18" data-listing-word-count-sort="3494" data-listing-title-sort="V-Sekai Changelog - 2021-05" data-listing-filename-sort="20210501-changelog.md">
+<tr data-index="37" data-listing-file-modified-sort="1730559023662" data-listing-reading-time-sort="18" data-listing-word-count-sort="3494" data-listing-title-sort="V-Sekai Changelog - 2021-05" data-listing-filename-sort="20210501-changelog.md">
 <td>
 <a href="./changelog/2021/20210501-changelog.html" class="title listing-title">V-Sekai Changelog - 2021-05</a>
 </td>
 </tr>
-<tr data-index="38" data-listing-file-modified-sort="1730535490014" data-listing-reading-time-sort="2" data-listing-word-count-sort="357" data-listing-title-sort="V-Sekai Changelog - 2021-04" data-listing-filename-sort="20210401-changelog.md">
+<tr data-index="38" data-listing-file-modified-sort="1730559023662" data-listing-reading-time-sort="2" data-listing-word-count-sort="357" data-listing-title-sort="V-Sekai Changelog - 2021-04" data-listing-filename-sort="20210401-changelog.md">
 <td>
 <a href="./changelog/2021/20210401-changelog.html" class="title listing-title">V-Sekai Changelog - 2021-04</a>
 </td>
diff --git a/docs/changelog.xml b/docs/changelog.xml
index cb27ea00f0..c8465f860f 100644
--- a/docs/changelog.xml
+++ b/docs/changelog.xml
@@ -10,7 +10,7 @@
 <atom:link href="https://v-sekai.github.io/manuals/changelog.xml" rel="self" type="application/rss+xml"/>
 <description></description>
 <generator>quarto-1.5.57</generator>
-<lastBuildDate>Sat, 02 Nov 2024 08:18:42 GMT</lastBuildDate>
+<lastBuildDate>Sat, 02 Nov 2024 14:50:38 GMT</lastBuildDate>
 <item>
   <title></title>
   <link>https://v-sekai.github.io/manuals/changelog/2024/20241003-changelog.html</link>
@@ -91,7 +91,7 @@
 
  ]]></description>
   <guid>https://v-sekai.github.io/manuals/changelog/2024/20241003-changelog.html</guid>
-  <pubDate>Sat, 02 Nov 2024 08:18:42 GMT</pubDate>
+  <pubDate>Sat, 02 Nov 2024 14:50:38 GMT</pubDate>
 </item>
 <item>
   <title></title>
@@ -164,7 +164,7 @@
 
  ]]></description>
   <guid>https://v-sekai.github.io/manuals/changelog/2024/20240901-changelog.html</guid>
-  <pubDate>Sat, 02 Nov 2024 08:18:42 GMT</pubDate>
+  <pubDate>Sat, 02 Nov 2024 14:50:38 GMT</pubDate>
 </item>
 <item>
   <title></title>
@@ -264,7 +264,7 @@
 
  ]]></description>
   <guid>https://v-sekai.github.io/manuals/changelog/2024/20240701-changelog.html</guid>
-  <pubDate>Sat, 02 Nov 2024 08:18:42 GMT</pubDate>
+  <pubDate>Sat, 02 Nov 2024 14:50:38 GMT</pubDate>
 </item>
 <item>
   <title></title>
@@ -334,7 +334,7 @@
 
  ]]></description>
   <guid>https://v-sekai.github.io/manuals/changelog/2024/20240625-changelog.html</guid>
-  <pubDate>Sat, 02 Nov 2024 08:18:42 GMT</pubDate>
+  <pubDate>Sat, 02 Nov 2024 14:50:38 GMT</pubDate>
 </item>
 <item>
   <title></title>
@@ -410,7 +410,7 @@
 
  ]]></description>
   <guid>https://v-sekai.github.io/manuals/changelog/2024/20240603-changelog.html</guid>
-  <pubDate>Sat, 02 Nov 2024 08:18:42 GMT</pubDate>
+  <pubDate>Sat, 02 Nov 2024 14:50:38 GMT</pubDate>
 </item>
 <item>
   <title></title>
@@ -485,7 +485,7 @@
 
  ]]></description>
   <guid>https://v-sekai.github.io/manuals/changelog/2024/20240505-changelog.html</guid>
-  <pubDate>Sat, 02 Nov 2024 08:18:42 GMT</pubDate>
+  <pubDate>Sat, 02 Nov 2024 14:50:38 GMT</pubDate>
 </item>
 <item>
   <title></title>
@@ -558,7 +558,7 @@
 
  ]]></description>
   <guid>https://v-sekai.github.io/manuals/changelog/2024/20240330-changelog.html</guid>
-  <pubDate>Sat, 02 Nov 2024 08:18:42 GMT</pubDate>
+  <pubDate>Sat, 02 Nov 2024 14:50:38 GMT</pubDate>
 </item>
 <item>
   <title></title>
@@ -634,7 +634,7 @@
 
  ]]></description>
   <guid>https://v-sekai.github.io/manuals/changelog/2024/20240202-changelog.html</guid>
-  <pubDate>Sat, 02 Nov 2024 08:18:42 GMT</pubDate>
+  <pubDate>Sat, 02 Nov 2024 14:50:38 GMT</pubDate>
 </item>
 <item>
   <title></title>
@@ -707,7 +707,7 @@
 
  ]]></description>
   <guid>https://v-sekai.github.io/manuals/changelog/2024/20240101-changelog.html</guid>
-  <pubDate>Sat, 02 Nov 2024 08:18:42 GMT</pubDate>
+  <pubDate>Sat, 02 Nov 2024 14:50:38 GMT</pubDate>
 </item>
 <item>
   <title></title>
@@ -782,7 +782,7 @@
 
  ]]></description>
   <guid>https://v-sekai.github.io/manuals/changelog/2023/20231207-changelog.html</guid>
-  <pubDate>Sat, 02 Nov 2024 08:18:42 GMT</pubDate>
+  <pubDate>Sat, 02 Nov 2024 14:50:38 GMT</pubDate>
 </item>
 <item>
   <title></title>
@@ -887,7 +887,7 @@
 
  ]]></description>
   <guid>https://v-sekai.github.io/manuals/changelog/2023/20231109-changelog.html</guid>
-  <pubDate>Sat, 02 Nov 2024 08:18:42 GMT</pubDate>
+  <pubDate>Sat, 02 Nov 2024 14:50:38 GMT</pubDate>
 </item>
 <item>
   <title></title>
@@ -978,7 +978,7 @@ font-style: inherit;">./extract.sh</span></span></code></pre></div>
 
  ]]></description>
   <guid>https://v-sekai.github.io/manuals/changelog/2023/20231001-changelog.html</guid>
-  <pubDate>Sat, 02 Nov 2024 08:18:42 GMT</pubDate>
+  <pubDate>Sat, 02 Nov 2024 14:50:38 GMT</pubDate>
 </item>
 <item>
   <title></title>
@@ -1053,7 +1053,7 @@ font-style: inherit;">./extract.sh</span></span></code></pre></div>
 
  ]]></description>
   <guid>https://v-sekai.github.io/manuals/changelog/2023/20230901-changelog.html</guid>
-  <pubDate>Sat, 02 Nov 2024 08:18:42 GMT</pubDate>
+  <pubDate>Sat, 02 Nov 2024 14:50:38 GMT</pubDate>
 </item>
 <item>
   <title></title>
@@ -1151,7 +1151,7 @@ font-style: inherit;">./extract.sh</span></span></code></pre></div>
 
  ]]></description>
   <guid>https://v-sekai.github.io/manuals/changelog/2023/20230801-changelog.html</guid>
-  <pubDate>Sat, 02 Nov 2024 08:18:42 GMT</pubDate>
+  <pubDate>Sat, 02 Nov 2024 14:50:38 GMT</pubDate>
 </item>
 <item>
   <title></title>
@@ -1221,7 +1221,7 @@ font-style: inherit;">./extract.sh</span></span></code></pre></div>
 
  ]]></description>
   <guid>https://v-sekai.github.io/manuals/changelog/2023/20230701-changelog.html</guid>
-  <pubDate>Sat, 02 Nov 2024 08:18:42 GMT</pubDate>
+  <pubDate>Sat, 02 Nov 2024 14:50:38 GMT</pubDate>
 </item>
 <item>
   <title></title>
@@ -1287,7 +1287,7 @@ font-style: inherit;">./extract.sh</span></span></code></pre></div>
 
  ]]></description>
   <guid>https://v-sekai.github.io/manuals/changelog/2023/20230601-changelog.html</guid>
-  <pubDate>Sat, 02 Nov 2024 08:18:42 GMT</pubDate>
+  <pubDate>Sat, 02 Nov 2024 14:50:38 GMT</pubDate>
 </item>
 <item>
   <title></title>
@@ -1323,7 +1323,7 @@ font-style: inherit;">./extract.sh</span></span></code></pre></div>
 
  ]]></description>
   <guid>https://v-sekai.github.io/manuals/changelog/2023/20230501-changelog.html</guid>
-  <pubDate>Sat, 02 Nov 2024 08:18:42 GMT</pubDate>
+  <pubDate>Sat, 02 Nov 2024 14:50:38 GMT</pubDate>
 </item>
 <item>
   <title></title>
@@ -1483,7 +1483,7 @@ font-style: inherit;">./extract.sh</span></span></code></pre></div>
 
  ]]></description>
   <guid>https://v-sekai.github.io/manuals/changelog/2023/20230301-changelog.html</guid>
-  <pubDate>Sat, 02 Nov 2024 08:18:42 GMT</pubDate>
+  <pubDate>Sat, 02 Nov 2024 14:50:38 GMT</pubDate>
 </item>
 <item>
   <title></title>
@@ -1519,7 +1519,7 @@ font-style: inherit;">./extract.sh</span></span></code></pre></div>
 
  ]]></description>
   <guid>https://v-sekai.github.io/manuals/changelog/2023/20230201-changelog.html</guid>
-  <pubDate>Sat, 02 Nov 2024 08:18:42 GMT</pubDate>
+  <pubDate>Sat, 02 Nov 2024 14:50:38 GMT</pubDate>
 </item>
 <item>
   <title></title>
@@ -1538,7 +1538,7 @@ font-style: inherit;">./extract.sh</span></span></code></pre></div>
 
  ]]></description>
   <guid>https://v-sekai.github.io/manuals/changelog/2023/20230101-changelog.html</guid>
-  <pubDate>Sat, 02 Nov 2024 08:18:42 GMT</pubDate>
+  <pubDate>Sat, 02 Nov 2024 14:50:38 GMT</pubDate>
 </item>
 </channel>
 </rss>
diff --git a/docs/changelog/2021/20210401-changelog.html b/docs/changelog/2021/20210401-changelog.html
index c3d26e1e6b..2a99930882 100644
--- a/docs/changelog/2021/20210401-changelog.html
+++ b/docs/changelog/2021/20210401-changelog.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/changelog/2021/20210501-changelog.html b/docs/changelog/2021/20210501-changelog.html
index 918a9937af..083748d12c 100644
--- a/docs/changelog/2021/20210501-changelog.html
+++ b/docs/changelog/2021/20210501-changelog.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/changelog/2021/20210601-changelog.html b/docs/changelog/2021/20210601-changelog.html
index ab0137bb7f..bd8a25f5a1 100644
--- a/docs/changelog/2021/20210601-changelog.html
+++ b/docs/changelog/2021/20210601-changelog.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/changelog/2021/20210701-changelog.html b/docs/changelog/2021/20210701-changelog.html
index ce28746c28..7de151b28c 100644
--- a/docs/changelog/2021/20210701-changelog.html
+++ b/docs/changelog/2021/20210701-changelog.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/changelog/2021/20210801-changelog.html b/docs/changelog/2021/20210801-changelog.html
index c3932af7c9..9a01a20d67 100644
--- a/docs/changelog/2021/20210801-changelog.html
+++ b/docs/changelog/2021/20210801-changelog.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/changelog/2021/20210901-changelog.html b/docs/changelog/2021/20210901-changelog.html
index 395fed0c4b..5a807e8fd8 100644
--- a/docs/changelog/2021/20210901-changelog.html
+++ b/docs/changelog/2021/20210901-changelog.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/changelog/2021/20211001-changelog.html b/docs/changelog/2021/20211001-changelog.html
index 4098a9d523..28d0d653d8 100644
--- a/docs/changelog/2021/20211001-changelog.html
+++ b/docs/changelog/2021/20211001-changelog.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/changelog/2021/20211101-changelog.html b/docs/changelog/2021/20211101-changelog.html
index a67791d418..c51e3f00c0 100644
--- a/docs/changelog/2021/20211101-changelog.html
+++ b/docs/changelog/2021/20211101-changelog.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/changelog/2022/20220101-changelog.html b/docs/changelog/2022/20220101-changelog.html
index 54e3ff3ab1..ef80135469 100644
--- a/docs/changelog/2022/20220101-changelog.html
+++ b/docs/changelog/2022/20220101-changelog.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/changelog/2022/20220201-changelog.html b/docs/changelog/2022/20220201-changelog.html
index 365565a270..b580289ada 100644
--- a/docs/changelog/2022/20220201-changelog.html
+++ b/docs/changelog/2022/20220201-changelog.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/changelog/2022/20220301-changelog.html b/docs/changelog/2022/20220301-changelog.html
index 65763205bd..69f99d2104 100644
--- a/docs/changelog/2022/20220301-changelog.html
+++ b/docs/changelog/2022/20220301-changelog.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/changelog/2022/20220401-changelog.html b/docs/changelog/2022/20220401-changelog.html
index 7aa6d0534f..5a41e6006c 100644
--- a/docs/changelog/2022/20220401-changelog.html
+++ b/docs/changelog/2022/20220401-changelog.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/changelog/2022/20220501-changelog.html b/docs/changelog/2022/20220501-changelog.html
index 0a0913a8cb..447e28c3ac 100644
--- a/docs/changelog/2022/20220501-changelog.html
+++ b/docs/changelog/2022/20220501-changelog.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/changelog/2022/20220601-changelog.html b/docs/changelog/2022/20220601-changelog.html
index 1dc4c5497f..5440fb8eb9 100644
--- a/docs/changelog/2022/20220601-changelog.html
+++ b/docs/changelog/2022/20220601-changelog.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/changelog/2022/20220801-changelog.html b/docs/changelog/2022/20220801-changelog.html
index 8e148edab3..ba0eea7dba 100644
--- a/docs/changelog/2022/20220801-changelog.html
+++ b/docs/changelog/2022/20220801-changelog.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/changelog/2022/20220901-changelog.html b/docs/changelog/2022/20220901-changelog.html
index dfea53f529..a21e54dd1d 100644
--- a/docs/changelog/2022/20220901-changelog.html
+++ b/docs/changelog/2022/20220901-changelog.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/changelog/2022/20221001-changelog.html b/docs/changelog/2022/20221001-changelog.html
index e07b1194ea..8ab8b8bf5e 100644
--- a/docs/changelog/2022/20221001-changelog.html
+++ b/docs/changelog/2022/20221001-changelog.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/changelog/2022/20221101-changelog.html b/docs/changelog/2022/20221101-changelog.html
index 2ac92545ff..26b4142a55 100644
--- a/docs/changelog/2022/20221101-changelog.html
+++ b/docs/changelog/2022/20221101-changelog.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/changelog/2022/20221201-changelog.html b/docs/changelog/2022/20221201-changelog.html
index e12ef25ed5..c76b330ecd 100644
--- a/docs/changelog/2022/20221201-changelog.html
+++ b/docs/changelog/2022/20221201-changelog.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/changelog/2023/20230101-changelog.html b/docs/changelog/2023/20230101-changelog.html
index 15ced4507c..455fd70af6 100644
--- a/docs/changelog/2023/20230101-changelog.html
+++ b/docs/changelog/2023/20230101-changelog.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/changelog/2023/20230201-changelog.html b/docs/changelog/2023/20230201-changelog.html
index aa059d2b42..e234c07f7a 100644
--- a/docs/changelog/2023/20230201-changelog.html
+++ b/docs/changelog/2023/20230201-changelog.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/changelog/2023/20230301-changelog.html b/docs/changelog/2023/20230301-changelog.html
index e225c843e0..c888ab1117 100644
--- a/docs/changelog/2023/20230301-changelog.html
+++ b/docs/changelog/2023/20230301-changelog.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/changelog/2023/20230501-changelog.html b/docs/changelog/2023/20230501-changelog.html
index 79b32754d7..891e061722 100644
--- a/docs/changelog/2023/20230501-changelog.html
+++ b/docs/changelog/2023/20230501-changelog.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/changelog/2023/20230601-changelog.html b/docs/changelog/2023/20230601-changelog.html
index a727cd729c..eb91ebefef 100644
--- a/docs/changelog/2023/20230601-changelog.html
+++ b/docs/changelog/2023/20230601-changelog.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/changelog/2023/20230701-changelog.html b/docs/changelog/2023/20230701-changelog.html
index 07e44982f6..59b3f61ddb 100644
--- a/docs/changelog/2023/20230701-changelog.html
+++ b/docs/changelog/2023/20230701-changelog.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/changelog/2023/20230801-changelog.html b/docs/changelog/2023/20230801-changelog.html
index 499e9106c4..158ec49579 100644
--- a/docs/changelog/2023/20230801-changelog.html
+++ b/docs/changelog/2023/20230801-changelog.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/changelog/2023/20230901-changelog.html b/docs/changelog/2023/20230901-changelog.html
index e1a464a6fa..d29316a542 100644
--- a/docs/changelog/2023/20230901-changelog.html
+++ b/docs/changelog/2023/20230901-changelog.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/changelog/2023/20231001-changelog.html b/docs/changelog/2023/20231001-changelog.html
index 7d38f9aab8..d3cc905cd9 100644
--- a/docs/changelog/2023/20231001-changelog.html
+++ b/docs/changelog/2023/20231001-changelog.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/changelog/2023/20231109-changelog.html b/docs/changelog/2023/20231109-changelog.html
index bf8092aa24..32f8192030 100644
--- a/docs/changelog/2023/20231109-changelog.html
+++ b/docs/changelog/2023/20231109-changelog.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/changelog/2023/20231207-changelog.html b/docs/changelog/2023/20231207-changelog.html
index feb0745445..7c06f2ebc2 100644
--- a/docs/changelog/2023/20231207-changelog.html
+++ b/docs/changelog/2023/20231207-changelog.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/changelog/2024/20240101-changelog.html b/docs/changelog/2024/20240101-changelog.html
index 2d120f52e1..1b7da34714 100644
--- a/docs/changelog/2024/20240101-changelog.html
+++ b/docs/changelog/2024/20240101-changelog.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/changelog/2024/20240202-changelog.html b/docs/changelog/2024/20240202-changelog.html
index 1c65392290..08e3d71120 100644
--- a/docs/changelog/2024/20240202-changelog.html
+++ b/docs/changelog/2024/20240202-changelog.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/changelog/2024/20240330-changelog.html b/docs/changelog/2024/20240330-changelog.html
index bdac5b1e1f..b746a6e1b9 100644
--- a/docs/changelog/2024/20240330-changelog.html
+++ b/docs/changelog/2024/20240330-changelog.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/changelog/2024/20240505-changelog.html b/docs/changelog/2024/20240505-changelog.html
index ecf82ad7b5..cee6ec39d6 100644
--- a/docs/changelog/2024/20240505-changelog.html
+++ b/docs/changelog/2024/20240505-changelog.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/changelog/2024/20240603-changelog.html b/docs/changelog/2024/20240603-changelog.html
index ef5a2d16fc..35f4146948 100644
--- a/docs/changelog/2024/20240603-changelog.html
+++ b/docs/changelog/2024/20240603-changelog.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/changelog/2024/20240625-changelog.html b/docs/changelog/2024/20240625-changelog.html
index 8935a6123a..09c0f0dc83 100644
--- a/docs/changelog/2024/20240625-changelog.html
+++ b/docs/changelog/2024/20240625-changelog.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/changelog/2024/20240701-changelog.html b/docs/changelog/2024/20240701-changelog.html
index f2a08eb8cb..fb28daa25c 100644
--- a/docs/changelog/2024/20240701-changelog.html
+++ b/docs/changelog/2024/20240701-changelog.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/changelog/2024/20240901-changelog.html b/docs/changelog/2024/20240901-changelog.html
index bfbb9e86d3..967e79da49 100644
--- a/docs/changelog/2024/20240901-changelog.html
+++ b/docs/changelog/2024/20240901-changelog.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/changelog/2024/20241003-changelog.html b/docs/changelog/2024/20241003-changelog.html
index 23dfd7de9b..3e4f7b99e2 100644
--- a/docs/changelog/2024/20241003-changelog.html
+++ b/docs/changelog/2024/20241003-changelog.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions.html b/docs/decisions.html
index 152544e39f..3477cccddc 100644
--- a/docs/decisions.html
+++ b/docs/decisions.html
@@ -162,7 +162,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="./plans.qmd"> 
+    <a class="nav-link" href="./plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
@@ -234,7 +234,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 </tr>
 </thead>
 <tbody class="list">
-<tr data-index="0" data-listing-file-modified-sort="1730535490238" data-listing-reading-time-sort="1" data-listing-word-count-sort="107" data-listing-title-sort="Proposed: Template" data-listing-filename-sort="present-proposal-template.md">
+<tr data-index="0" data-listing-file-modified-sort="1730559023878" data-listing-reading-time-sort="1" data-listing-word-count-sort="107" data-listing-title-sort="Proposed: Template" data-listing-filename-sort="present-proposal-template.md">
 <td>
 <a href="./decisions/present-proposal-template.html" class="title listing-title">Proposed: Template</a>
 </td>
@@ -245,7 +245,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/present-proposal-template.html" class="filename listing-filename">present-proposal-template.md</a>
 </td>
 </tr>
-<tr data-index="1" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="2" data-listing-word-count-sort="341" data-listing-title-sort="Accepted: AI Assisted Style Guide" data-listing-filename-sort="ai-assisted-proposal-style-guide.md">
+<tr data-index="1" data-listing-file-modified-sort="1730559023690" data-listing-reading-time-sort="2" data-listing-word-count-sort="341" data-listing-title-sort="Accepted: AI Assisted Style Guide" data-listing-filename-sort="ai-assisted-proposal-style-guide.md">
 <td>
 <a href="./decisions/ai-assisted-proposal-style-guide.html" class="title listing-title">Accepted: AI Assisted Style Guide</a>
 </td>
@@ -256,7 +256,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/ai-assisted-proposal-style-guide.html" class="filename listing-filename">ai-assisted-proposal-style-guide.md</a>
 </td>
 </tr>
-<tr data-index="2" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="2" data-listing-word-count-sort="326" data-listing-title-sort="Proposal: Use Data Tables for Godot Constraints" data-listing-filename-sort="20241028-use-data-tables-for-godot-constraints.md">
+<tr data-index="2" data-listing-file-modified-sort="1730559023690" data-listing-reading-time-sort="2" data-listing-word-count-sort="326" data-listing-title-sort="Proposal: Use Data Tables for Godot Constraints" data-listing-filename-sort="20241028-use-data-tables-for-godot-constraints.md">
 <td>
 <a href="./decisions/20241028-use-data-tables-for-godot-constraints.html" class="title listing-title">Proposal: Use Data Tables for Godot Constraints</a>
 </td>
@@ -267,7 +267,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20241028-use-data-tables-for-godot-constraints.html" class="filename listing-filename">20241028-use-data-tables-for-godot-constraints.md</a>
 </td>
 </tr>
-<tr data-index="3" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="2" data-listing-word-count-sort="387" data-listing-title-sort="Proposed: Reduce Size Difference Between Capsules and Mesh Volume" data-listing-filename-sort="20241019-reduce-size-difference-between-capsules-and-mesh-volume.md">
+<tr data-index="3" data-listing-file-modified-sort="1730559023690" data-listing-reading-time-sort="2" data-listing-word-count-sort="387" data-listing-title-sort="Proposed: Reduce Size Difference Between Capsules and Mesh Volume" data-listing-filename-sort="20241019-reduce-size-difference-between-capsules-and-mesh-volume.md">
 <td>
 <a href="./decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html" class="title listing-title">Proposed: Reduce Size Difference Between Capsules and Mesh Volume</a>
 </td>
@@ -278,7 +278,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html" class="filename listing-filename">20241019-reduce-size-difference-between-capsules-and-mesh-volume.md</a>
 </td>
 </tr>
-<tr data-index="4" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="3" data-listing-word-count-sort="500" data-listing-title-sort="Proposed: Evaluate three proposals for V-Sekai content distribution" data-listing-filename-sort="20241016-instantiating-v-sekai-content.md">
+<tr data-index="4" data-listing-file-modified-sort="1730559023690" data-listing-reading-time-sort="3" data-listing-word-count-sort="500" data-listing-title-sort="Proposed: Evaluate three proposals for V-Sekai content distribution" data-listing-filename-sort="20241016-instantiating-v-sekai-content.md">
 <td>
 <a href="./decisions/20241016-instantiating-v-sekai-content.html" class="title listing-title">Proposed: Evaluate three proposals for V-Sekai content distribution</a>
 </td>
@@ -289,7 +289,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20241016-instantiating-v-sekai-content.html" class="filename listing-filename">20241016-instantiating-v-sekai-content.md</a>
 </td>
 </tr>
-<tr data-index="5" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="8" data-listing-word-count-sort="1452" data-listing-title-sort="Proposed: Editing Character Body Bone Constraints in Immersive Mode" data-listing-filename-sort="20241014-xr-interface-for-rigging.md">
+<tr data-index="5" data-listing-file-modified-sort="1730559023690" data-listing-reading-time-sort="8" data-listing-word-count-sort="1452" data-listing-title-sort="Proposed: Editing Character Body Bone Constraints in Immersive Mode" data-listing-filename-sort="20241014-xr-interface-for-rigging.md">
 <td>
 <a href="./decisions/20241014-xr-interface-for-rigging.html" class="title listing-title">Proposed: Editing Character Body Bone Constraints in Immersive Mode</a>
 </td>
@@ -300,7 +300,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20241014-xr-interface-for-rigging.html" class="filename listing-filename">20241014-xr-interface-for-rigging.md</a>
 </td>
 </tr>
-<tr data-index="6" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="5" data-listing-word-count-sort="992" data-listing-title-sort="Proposed: Basic Real-Time Interaction for Character and World Scenes" data-listing-filename-sort="20241014-basic-realtime-interaction.md">
+<tr data-index="6" data-listing-file-modified-sort="1730559023690" data-listing-reading-time-sort="5" data-listing-word-count-sort="992" data-listing-title-sort="Proposed: Basic Real-Time Interaction for Character and World Scenes" data-listing-filename-sort="20241014-basic-realtime-interaction.md">
 <td>
 <a href="./decisions/20241014-basic-realtime-interaction.html" class="title listing-title">Proposed: Basic Real-Time Interaction for Character and World Scenes</a>
 </td>
@@ -311,7 +311,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20241014-basic-realtime-interaction.html" class="filename listing-filename">20241014-basic-realtime-interaction.md</a>
 </td>
 </tr>
-<tr data-index="7" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="2" data-listing-word-count-sort="243" data-listing-title-sort="Proposed: Updater No-Op Implementation Using Velopack" data-listing-filename-sort="20241014-app-updater.md">
+<tr data-index="7" data-listing-file-modified-sort="1730559023690" data-listing-reading-time-sort="2" data-listing-word-count-sort="243" data-listing-title-sort="Proposed: Updater No-Op Implementation Using Velopack" data-listing-filename-sort="20241014-app-updater.md">
 <td>
 <a href="./decisions/20241014-app-updater.html" class="title listing-title">Proposed: Updater No-Op Implementation Using Velopack</a>
 </td>
@@ -322,7 +322,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20241014-app-updater.html" class="filename listing-filename">20241014-app-updater.md</a>
 </td>
 </tr>
-<tr data-index="8" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="3" data-listing-word-count-sort="598" data-listing-title-sort="Proposed: Recovering MakeHuman Parameters Using Depth Map Comparison with Godot Engine" data-listing-filename-sort="20241011-recovering-makehuman-parameters.md">
+<tr data-index="8" data-listing-file-modified-sort="1730559023690" data-listing-reading-time-sort="3" data-listing-word-count-sort="598" data-listing-title-sort="Proposed: Recovering MakeHuman Parameters Using Depth Map Comparison with Godot Engine" data-listing-filename-sort="20241011-recovering-makehuman-parameters.md">
 <td>
 <a href="./decisions/20241011-recovering-makehuman-parameters.html" class="title listing-title">Proposed: Recovering MakeHuman Parameters Using Depth Map Comparison with Godot Engine</a>
 </td>
@@ -333,7 +333,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20241011-recovering-makehuman-parameters.html" class="filename listing-filename">20241011-recovering-makehuman-parameters.md</a>
 </td>
 </tr>
-<tr data-index="9" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="2" data-listing-word-count-sort="296" data-listing-title-sort="Accepted: Restoring Default User Directory Structure in Windows 11" data-listing-filename-sort="20241006-restore-onedrive-shortcut-overrides.md">
+<tr data-index="9" data-listing-file-modified-sort="1730559023690" data-listing-reading-time-sort="2" data-listing-word-count-sort="296" data-listing-title-sort="Accepted: Restoring Default User Directory Structure in Windows 11" data-listing-filename-sort="20241006-restore-onedrive-shortcut-overrides.md">
 <td>
 <a href="./decisions/20241006-restore-onedrive-shortcut-overrides.html" class="title listing-title">Accepted: Restoring Default User Directory Structure in Windows 11</a>
 </td>
@@ -344,7 +344,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20241006-restore-onedrive-shortcut-overrides.html" class="filename listing-filename">20241006-restore-onedrive-shortcut-overrides.md</a>
 </td>
 </tr>
-<tr data-index="10" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="2" data-listing-word-count-sort="385" data-listing-title-sort="Proposed: Small V-Sekai Creation Tools" data-listing-filename-sort="20241001-small-game-tools.md">
+<tr data-index="10" data-listing-file-modified-sort="1730559023690" data-listing-reading-time-sort="2" data-listing-word-count-sort="385" data-listing-title-sort="Proposed: Small V-Sekai Creation Tools" data-listing-filename-sort="20241001-small-game-tools.md">
 <td>
 <a href="./decisions/20241001-small-game-tools.html" class="title listing-title">Proposed: Small V-Sekai Creation Tools</a>
 </td>
@@ -355,7 +355,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20241001-small-game-tools.html" class="filename listing-filename">20241001-small-game-tools.md</a>
 </td>
 </tr>
-<tr data-index="11" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="3" data-listing-word-count-sort="467" data-listing-title-sort="Accepted: Godot Engine XR Elite HMD Conference Setup" data-listing-filename-sort="20240914-godot-engine-xr-elite-conference-setup.md">
+<tr data-index="11" data-listing-file-modified-sort="1730559023690" data-listing-reading-time-sort="3" data-listing-word-count-sort="467" data-listing-title-sort="Accepted: Godot Engine XR Elite HMD Conference Setup" data-listing-filename-sort="20240914-godot-engine-xr-elite-conference-setup.md">
 <td>
 <a href="./decisions/20240914-godot-engine-xr-elite-conference-setup.html" class="title listing-title">Accepted: Godot Engine XR Elite HMD Conference Setup</a>
 </td>
@@ -366,7 +366,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240914-godot-engine-xr-elite-conference-setup.html" class="filename listing-filename">20240914-godot-engine-xr-elite-conference-setup.md</a>
 </td>
 </tr>
-<tr data-index="12" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="3" data-listing-word-count-sort="527" data-listing-title-sort="Proposed: Revised Tracker Configuration and Constraints for HTC VIVE XR Elite" data-listing-filename-sort="20240905-revised-tracker-configuration-and-constraints.md">
+<tr data-index="12" data-listing-file-modified-sort="1730559023690" data-listing-reading-time-sort="3" data-listing-word-count-sort="527" data-listing-title-sort="Proposed: Revised Tracker Configuration and Constraints for HTC VIVE XR Elite" data-listing-filename-sort="20240905-revised-tracker-configuration-and-constraints.md">
 <td>
 <a href="./decisions/20240905-revised-tracker-configuration-and-constraints.html" class="title listing-title">Proposed: Revised Tracker Configuration and Constraints for HTC VIVE XR Elite</a>
 </td>
@@ -377,7 +377,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240905-revised-tracker-configuration-and-constraints.html" class="filename listing-filename">20240905-revised-tracker-configuration-and-constraints.md</a>
 </td>
 </tr>
-<tr data-index="13" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="2" data-listing-word-count-sort="330" data-listing-title-sort="Proposed: Transition to Dokku from Kubernetes Proposal" data-listing-filename-sort="20240830-use-dokku-to-host-vsk-backend.md">
+<tr data-index="13" data-listing-file-modified-sort="1730559023690" data-listing-reading-time-sort="2" data-listing-word-count-sort="330" data-listing-title-sort="Proposed: Transition to Dokku from Kubernetes Proposal" data-listing-filename-sort="20240830-use-dokku-to-host-vsk-backend.md">
 <td>
 <a href="./decisions/20240830-use-dokku-to-host-vsk-backend.html" class="title listing-title">Proposed: Transition to Dokku from Kubernetes Proposal</a>
 </td>
@@ -388,7 +388,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240830-use-dokku-to-host-vsk-backend.html" class="filename listing-filename">20240830-use-dokku-to-host-vsk-backend.md</a>
 </td>
 </tr>
-<tr data-index="14" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="3" data-listing-word-count-sort="552" data-listing-title-sort="Accepted: PCI-E Lane Depletion and Thunderbolt 4 Issues" data-listing-filename-sort="20240830-pcie-lane-depletion-thunderbolt-4-issues.md">
+<tr data-index="14" data-listing-file-modified-sort="1730559023690" data-listing-reading-time-sort="3" data-listing-word-count-sort="552" data-listing-title-sort="Accepted: PCI-E Lane Depletion and Thunderbolt 4 Issues" data-listing-filename-sort="20240830-pcie-lane-depletion-thunderbolt-4-issues.md">
 <td>
 <a href="./decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html" class="title listing-title">Accepted: PCI-E Lane Depletion and Thunderbolt 4 Issues</a>
 </td>
@@ -399,7 +399,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html" class="filename listing-filename">20240830-pcie-lane-depletion-thunderbolt-4-issues.md</a>
 </td>
 </tr>
-<tr data-index="15" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="5" data-listing-word-count-sort="860" data-listing-title-sort="Proposed: FFMPEG Wave/Mic and Speaker/Play" data-listing-filename-sort="20240824-ffmpeg-wav-mic-speaker-play.md">
+<tr data-index="15" data-listing-file-modified-sort="1730559023690" data-listing-reading-time-sort="5" data-listing-word-count-sort="860" data-listing-title-sort="Proposed: FFMPEG Wave/Mic and Speaker/Play" data-listing-filename-sort="20240824-ffmpeg-wav-mic-speaker-play.md">
 <td>
 <a href="./decisions/20240824-ffmpeg-wav-mic-speaker-play.html" class="title listing-title">Proposed: FFMPEG Wave/Mic and Speaker/Play</a>
 </td>
@@ -410,7 +410,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240824-ffmpeg-wav-mic-speaker-play.html" class="filename listing-filename">20240824-ffmpeg-wav-mic-speaker-play.md</a>
 </td>
 </tr>
-<tr data-index="16" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="2" data-listing-word-count-sort="293" data-listing-title-sort="Proposed: Improving Connectivity for Valve StreamVR Light House Dongles" data-listing-filename-sort="20240810-steamvr-dongles-separate.md">
+<tr data-index="16" data-listing-file-modified-sort="1730559023690" data-listing-reading-time-sort="2" data-listing-word-count-sort="293" data-listing-title-sort="Proposed: Improving Connectivity for Valve StreamVR Light House Dongles" data-listing-filename-sort="20240810-steamvr-dongles-separate.md">
 <td>
 <a href="./decisions/20240810-steamvr-dongles-separate.html" class="title listing-title">Proposed: Improving Connectivity for Valve StreamVR Light House Dongles</a>
 </td>
@@ -421,7 +421,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240810-steamvr-dongles-separate.html" class="filename listing-filename">20240810-steamvr-dongles-separate.md</a>
 </td>
 </tr>
-<tr data-index="17" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="4" data-listing-word-count-sort="608" data-listing-title-sort="Proposal: Core V-Sekai Scripting with Wasm" data-listing-filename-sort="20240717-core-vsekai-scripting.md">
+<tr data-index="17" data-listing-file-modified-sort="1730559023690" data-listing-reading-time-sort="4" data-listing-word-count-sort="608" data-listing-title-sort="Proposal: Core V-Sekai Scripting with Wasm" data-listing-filename-sort="20240717-core-vsekai-scripting.md">
 <td>
 <a href="./decisions/20240717-core-vsekai-scripting.html" class="title listing-title">Proposal: Core V-Sekai Scripting with Wasm</a>
 </td>
@@ -432,7 +432,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240717-core-vsekai-scripting.html" class="filename listing-filename">20240717-core-vsekai-scripting.md</a>
 </td>
 </tr>
-<tr data-index="18" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="47" data-listing-word-count-sort="9387" data-listing-title-sort="Proposed: Create a Conceptual Model of VRChat Networking" data-listing-filename-sort="20240715-vrchat-networking-mental-model.md">
+<tr data-index="18" data-listing-file-modified-sort="1730559023690" data-listing-reading-time-sort="47" data-listing-word-count-sort="9387" data-listing-title-sort="Proposed: Create a Conceptual Model of VRChat Networking" data-listing-filename-sort="20240715-vrchat-networking-mental-model.md">
 <td>
 <a href="./decisions/20240715-vrchat-networking-mental-model.html" class="title listing-title">Proposed: Create a Conceptual Model of VRChat Networking</a>
 </td>
@@ -443,7 +443,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240715-vrchat-networking-mental-model.html" class="filename listing-filename">20240715-vrchat-networking-mental-model.md</a>
 </td>
 </tr>
-<tr data-index="19" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="2" data-listing-word-count-sort="246" data-listing-title-sort="Proposed: Use shrink wrap blender modifier to fit" data-listing-filename-sort="20240712-use-shrinkwrap-blender-modiifer-to-fit.md">
+<tr data-index="19" data-listing-file-modified-sort="1730559023690" data-listing-reading-time-sort="2" data-listing-word-count-sort="246" data-listing-title-sort="Proposed: Use shrink wrap blender modifier to fit" data-listing-filename-sort="20240712-use-shrinkwrap-blender-modiifer-to-fit.md">
 <td>
 <a href="./decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html" class="title listing-title">Proposed: Use shrink wrap blender modifier to fit</a>
 </td>
@@ -454,7 +454,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html" class="filename listing-filename">20240712-use-shrinkwrap-blender-modiifer-to-fit.md</a>
 </td>
 </tr>
-<tr data-index="20" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="3" data-listing-word-count-sort="514" data-listing-title-sort="Proposed: Networking PCVR with the Web" data-listing-filename-sort="20240710-web-and-pcvr-networking.md">
+<tr data-index="20" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="3" data-listing-word-count-sort="514" data-listing-title-sort="Proposed: Networking PCVR with the Web" data-listing-filename-sort="20240710-web-and-pcvr-networking.md">
 <td>
 <a href="./decisions/20240710-web-and-pcvr-networking.html" class="title listing-title">Proposed: Networking PCVR with the Web</a>
 </td>
@@ -465,7 +465,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240710-web-and-pcvr-networking.html" class="filename listing-filename">20240710-web-and-pcvr-networking.md</a>
 </td>
 </tr>
-<tr data-index="21" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="2" data-listing-word-count-sort="325" data-listing-title-sort="Proposed: Use WebRTC to Native to Interop with Godot Engine" data-listing-filename-sort="20240710-use-webrtc-to-native-interop.md">
+<tr data-index="21" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="325" data-listing-title-sort="Proposed: Use WebRTC to Native to Interop with Godot Engine" data-listing-filename-sort="20240710-use-webrtc-to-native-interop.md">
 <td>
 <a href="./decisions/20240710-use-webrtc-to-native-interop.html" class="title listing-title">Proposed: Use WebRTC to Native to Interop with Godot Engine</a>
 </td>
@@ -476,7 +476,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240710-use-webrtc-to-native-interop.html" class="filename listing-filename">20240710-use-webrtc-to-native-interop.md</a>
 </td>
 </tr>
-<tr data-index="22" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="3" data-listing-word-count-sort="591" data-listing-title-sort="Proposed: Use Godot Engine Web Threaded" data-listing-filename-sort="20240710-use-godot-engine-web-threaded.md">
+<tr data-index="22" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="3" data-listing-word-count-sort="591" data-listing-title-sort="Proposed: Use Godot Engine Web Threaded" data-listing-filename-sort="20240710-use-godot-engine-web-threaded.md">
 <td>
 <a href="./decisions/20240710-use-godot-engine-web-threaded.html" class="title listing-title">Proposed: Use Godot Engine Web Threaded</a>
 </td>
@@ -487,7 +487,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240710-use-godot-engine-web-threaded.html" class="filename listing-filename">20240710-use-godot-engine-web-threaded.md</a>
 </td>
 </tr>
-<tr data-index="23" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="2" data-listing-word-count-sort="387" data-listing-title-sort="Proposed: Focus on PCVR and the Web" data-listing-filename-sort="20240710-platform-focus-on-pcvr-and-web.md">
+<tr data-index="23" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="387" data-listing-title-sort="Proposed: Focus on PCVR and the Web" data-listing-filename-sort="20240710-platform-focus-on-pcvr-and-web.md">
 <td>
 <a href="./decisions/20240710-platform-focus-on-pcvr-and-web.html" class="title listing-title">Proposed: Focus on PCVR and the Web</a>
 </td>
@@ -498,7 +498,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240710-platform-focus-on-pcvr-and-web.html" class="filename listing-filename">20240710-platform-focus-on-pcvr-and-web.md</a>
 </td>
 </tr>
-<tr data-index="24" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="4" data-listing-word-count-sort="690" data-listing-title-sort="Proposed: Convert Blender CC0 Base Mesh to Godot Engine T-Pose" data-listing-filename-sort="20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.md">
+<tr data-index="24" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="4" data-listing-word-count-sort="690" data-listing-title-sort="Proposed: Convert Blender CC0 Base Mesh to Godot Engine T-Pose" data-listing-filename-sort="20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.md">
 <td>
 <a href="./decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html" class="title listing-title">Proposed: Convert Blender CC0 Base Mesh to Godot Engine T-Pose</a>
 </td>
@@ -509,7 +509,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html" class="filename listing-filename">20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.md</a>
 </td>
 </tr>
-<tr data-index="25" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="2" data-listing-word-count-sort="362" data-listing-title-sort="Proposed: Art Direction in V-Sekai Process" data-listing-filename-sort="20240710-art-direction-in-vsekai.md">
+<tr data-index="25" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="362" data-listing-title-sort="Proposed: Art Direction in V-Sekai Process" data-listing-filename-sort="20240710-art-direction-in-vsekai.md">
 <td>
 <a href="./decisions/20240710-art-direction-in-vsekai.html" class="title listing-title">Proposed: Art Direction in V-Sekai Process</a>
 </td>
@@ -520,7 +520,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240710-art-direction-in-vsekai.html" class="filename listing-filename">20240710-art-direction-in-vsekai.md</a>
 </td>
 </tr>
-<tr data-index="26" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="2" data-listing-word-count-sort="271" data-listing-title-sort="Proposed: A Wired-First Strategy for PCVR" data-listing-filename-sort="20240709-wired-first.md">
+<tr data-index="26" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="271" data-listing-title-sort="Proposed: A Wired-First Strategy for PCVR" data-listing-filename-sort="20240709-wired-first.md">
 <td>
 <a href="./decisions/20240709-wired-first.html" class="title listing-title">Proposed: A Wired-First Strategy for PCVR</a>
 </td>
@@ -531,7 +531,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240709-wired-first.html" class="filename listing-filename">20240709-wired-first.md</a>
 </td>
 </tr>
-<tr data-index="27" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="2" data-listing-word-count-sort="356" data-listing-title-sort="Proposed: Set Nvidia Watt Limit with Anwave" data-listing-filename-sort="20240709-anwave-set-nvidia-watt-limit.md">
+<tr data-index="27" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="356" data-listing-title-sort="Proposed: Set Nvidia Watt Limit with Anwave" data-listing-filename-sort="20240709-anwave-set-nvidia-watt-limit.md">
 <td>
 <a href="./decisions/20240709-anwave-set-nvidia-watt-limit.html" class="title listing-title">Proposed: Set Nvidia Watt Limit with Anwave</a>
 </td>
@@ -542,7 +542,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240709-anwave-set-nvidia-watt-limit.html" class="filename listing-filename">20240709-anwave-set-nvidia-watt-limit.md</a>
 </td>
 </tr>
-<tr data-index="28" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="5" data-listing-word-count-sort="872" data-listing-title-sort="Proposed: V-Sekai: My Life as a Princess" data-listing-filename-sort="20240708-vsekai-my-life-as-a-queen.md">
+<tr data-index="28" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="5" data-listing-word-count-sort="872" data-listing-title-sort="Proposed: V-Sekai: My Life as a Princess" data-listing-filename-sort="20240708-vsekai-my-life-as-a-queen.md">
 <td>
 <a href="./decisions/20240708-vsekai-my-life-as-a-queen.html" class="title listing-title">Proposed: V-Sekai: My Life as a Princess</a>
 </td>
@@ -553,7 +553,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240708-vsekai-my-life-as-a-queen.html" class="filename listing-filename">20240708-vsekai-my-life-as-a-queen.md</a>
 </td>
 </tr>
-<tr data-index="29" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="8" data-listing-word-count-sort="1487" data-listing-title-sort="Proposed: Maximum Streaming Bill of Materials Setup for Motion Capture" data-listing-filename-sort="20240706-motion-capture-bill-of-materials.md">
+<tr data-index="29" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="8" data-listing-word-count-sort="1487" data-listing-title-sort="Proposed: Maximum Streaming Bill of Materials Setup for Motion Capture" data-listing-filename-sort="20240706-motion-capture-bill-of-materials.md">
 <td>
 <a href="./decisions/20240706-motion-capture-bill-of-materials.html" class="title listing-title">Proposed: Maximum Streaming Bill of Materials Setup for Motion Capture</a>
 </td>
@@ -564,7 +564,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240706-motion-capture-bill-of-materials.html" class="filename listing-filename">20240706-motion-capture-bill-of-materials.md</a>
 </td>
 </tr>
-<tr data-index="30" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="3" data-listing-word-count-sort="463" data-listing-title-sort="Proposal: RPG Town in V-Sekai" data-listing-filename-sort="20240705-rpg_town.md">
+<tr data-index="30" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="3" data-listing-word-count-sort="463" data-listing-title-sort="Proposal: RPG Town in V-Sekai" data-listing-filename-sort="20240705-rpg_town.md">
 <td>
 <a href="./decisions/20240705-rpg_town.html" class="title listing-title">Proposal: RPG Town in V-Sekai</a>
 </td>
@@ -575,7 +575,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240705-rpg_town.html" class="filename listing-filename">20240705-rpg_town.md</a>
 </td>
 </tr>
-<tr data-index="31" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="2" data-listing-word-count-sort="340" data-listing-title-sort="Proposed: Use motion transformers for motion prediction" data-listing-filename-sort="20240630-use-motion-transformers-for-prediction.md">
+<tr data-index="31" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="340" data-listing-title-sort="Proposed: Use motion transformers for motion prediction" data-listing-filename-sort="20240630-use-motion-transformers-for-prediction.md">
 <td>
 <a href="./decisions/20240630-use-motion-transformers-for-prediction.html" class="title listing-title">Proposed: Use motion transformers for motion prediction</a>
 </td>
@@ -586,7 +586,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240630-use-motion-transformers-for-prediction.html" class="filename listing-filename">20240630-use-motion-transformers-for-prediction.md</a>
 </td>
 </tr>
-<tr data-index="32" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="3" data-listing-word-count-sort="447" data-listing-title-sort="Superceded: RISCV Binaries as Shared Libraries" data-listing-filename-sort="20240627-gdextension-as-libriscv.md">
+<tr data-index="32" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="3" data-listing-word-count-sort="447" data-listing-title-sort="Superceded: RISCV Binaries as Shared Libraries" data-listing-filename-sort="20240627-gdextension-as-libriscv.md">
 <td>
 <a href="./decisions/20240627-gdextension-as-libriscv.html" class="title listing-title">Superceded: RISCV Binaries as Shared Libraries</a>
 </td>
@@ -597,7 +597,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240627-gdextension-as-libriscv.html" class="filename listing-filename">20240627-gdextension-as-libriscv.md</a>
 </td>
 </tr>
-<tr data-index="33" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="2" data-listing-word-count-sort="372" data-listing-title-sort="Proposed: Every Commit Push Pass Cicd" data-listing-filename-sort="20240627-every-commit-push-pass-cicd.md">
+<tr data-index="33" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="372" data-listing-title-sort="Proposed: Every Commit Push Pass Cicd" data-listing-filename-sort="20240627-every-commit-push-pass-cicd.md">
 <td>
 <a href="./decisions/20240627-every-commit-push-pass-cicd.html" class="title listing-title">Proposed: Every Commit Push Pass Cicd</a>
 </td>
@@ -608,7 +608,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240627-every-commit-push-pass-cicd.html" class="filename listing-filename">20240627-every-commit-push-pass-cicd.md</a>
 </td>
 </tr>
-<tr data-index="34" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="3" data-listing-word-count-sort="525" data-listing-title-sort="Proposed: Update python3 macOS Certificates" data-listing-filename-sort="20240626-update-python3-macos-certicates.md">
+<tr data-index="34" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="3" data-listing-word-count-sort="525" data-listing-title-sort="Proposed: Update python3 macOS Certificates" data-listing-filename-sort="20240626-update-python3-macos-certicates.md">
 <td>
 <a href="./decisions/20240626-update-python3-macos-certicates.html" class="title listing-title">Proposed: Update python3 macOS Certificates</a>
 </td>
@@ -619,7 +619,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240626-update-python3-macos-certicates.html" class="filename listing-filename">20240626-update-python3-macos-certicates.md</a>
 </td>
 </tr>
-<tr data-index="35" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="3" data-listing-word-count-sort="507" data-listing-title-sort="Proposed: Why did we build &quot;Uro&quot;?" data-listing-filename-sort="20240623-what-is-uro-backend.md">
+<tr data-index="35" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="3" data-listing-word-count-sort="507" data-listing-title-sort="Proposed: Why did we build &quot;Uro&quot;?" data-listing-filename-sort="20240623-what-is-uro-backend.md">
 <td>
 <a href="./decisions/20240623-what-is-uro-backend.html" class="title listing-title">Proposed: Why did we build “Uro”?</a>
 </td>
@@ -630,7 +630,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240623-what-is-uro-backend.html" class="filename listing-filename">20240623-what-is-uro-backend.md</a>
 </td>
 </tr>
-<tr data-index="36" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="2" data-listing-word-count-sort="349" data-listing-title-sort="Proposed: Talk Length Game Prototypes" data-listing-filename-sort="20240623-talk-length-prototypes.md">
+<tr data-index="36" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="349" data-listing-title-sort="Proposed: Talk Length Game Prototypes" data-listing-filename-sort="20240623-talk-length-prototypes.md">
 <td>
 <a href="./decisions/20240623-talk-length-prototypes.html" class="title listing-title">Proposed: Talk Length Game Prototypes</a>
 </td>
@@ -641,7 +641,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240623-talk-length-prototypes.html" class="filename listing-filename">20240623-talk-length-prototypes.md</a>
 </td>
 </tr>
-<tr data-index="37" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="2" data-listing-word-count-sort="306" data-listing-title-sort="Proposal: Only Save Tools in Our CDN" data-listing-filename-sort="20240623-only-save-tools-in-our-cdn.md">
+<tr data-index="37" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="306" data-listing-title-sort="Proposal: Only Save Tools in Our CDN" data-listing-filename-sort="20240623-only-save-tools-in-our-cdn.md">
 <td>
 <a href="./decisions/20240623-only-save-tools-in-our-cdn.html" class="title listing-title">Proposal: Only Save Tools in Our CDN</a>
 </td>
@@ -652,7 +652,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240623-only-save-tools-in-our-cdn.html" class="filename listing-filename">20240623-only-save-tools-in-our-cdn.md</a>
 </td>
 </tr>
-<tr data-index="38" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="2" data-listing-word-count-sort="280" data-listing-title-sort="Proposed: Use GitHub Actions and Digital Ocean Spaces for a V-Sekai Launcher" data-listing-filename-sort="20240623-do-cdn-for-launcher.md">
+<tr data-index="38" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="280" data-listing-title-sort="Proposed: Use GitHub Actions and Digital Ocean Spaces for a V-Sekai Launcher" data-listing-filename-sort="20240623-do-cdn-for-launcher.md">
 <td>
 <a href="./decisions/20240623-do-cdn-for-launcher.html" class="title listing-title">Proposed: Use GitHub Actions and Digital Ocean Spaces for a V-Sekai Launcher</a>
 </td>
@@ -663,7 +663,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240623-do-cdn-for-launcher.html" class="filename listing-filename">20240623-do-cdn-for-launcher.md</a>
 </td>
 </tr>
-<tr data-index="39" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="2" data-listing-word-count-sort="256" data-listing-title-sort="Proposed: Create a process for testing V-Sekai." data-listing-filename-sort="20240622-process-for-testing-vsekai.md">
+<tr data-index="39" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="256" data-listing-title-sort="Proposed: Create a process for testing V-Sekai." data-listing-filename-sort="20240622-process-for-testing-vsekai.md">
 <td>
 <a href="./decisions/20240622-process-for-testing-vsekai.html" class="title listing-title">Proposed: Create a process for testing V-Sekai.</a>
 </td>
@@ -674,7 +674,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240622-process-for-testing-vsekai.html" class="filename listing-filename">20240622-process-for-testing-vsekai.md</a>
 </td>
 </tr>
-<tr data-index="40" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="2" data-listing-word-count-sort="316" data-listing-title-sort="Accepted: GoCD Agent Docker Image Update" data-listing-filename-sort="20240622-gocd-agent-docker-image-update.md">
+<tr data-index="40" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="316" data-listing-title-sort="Accepted: GoCD Agent Docker Image Update" data-listing-filename-sort="20240622-gocd-agent-docker-image-update.md">
 <td>
 <a href="./decisions/20240622-gocd-agent-docker-image-update.html" class="title listing-title">Accepted: GoCD Agent Docker Image Update</a>
 </td>
@@ -685,7 +685,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240622-gocd-agent-docker-image-update.html" class="filename listing-filename">20240622-gocd-agent-docker-image-update.md</a>
 </td>
 </tr>
-<tr data-index="41" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="2" data-listing-word-count-sort="398" data-listing-title-sort="Proposed: Build V-Sekai editor for many platforms" data-listing-filename-sort="20240622-build-for-many-platforms.md">
+<tr data-index="41" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="398" data-listing-title-sort="Proposed: Build V-Sekai editor for many platforms" data-listing-filename-sort="20240622-build-for-many-platforms.md">
 <td>
 <a href="./decisions/20240622-build-for-many-platforms.html" class="title listing-title">Proposed: Build V-Sekai editor for many platforms</a>
 </td>
@@ -696,7 +696,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240622-build-for-many-platforms.html" class="filename listing-filename">20240622-build-for-many-platforms.md</a>
 </td>
 </tr>
-<tr data-index="42" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="1" data-listing-word-count-sort="107" data-listing-title-sort="Proposed: Command Traces with Server Backend" data-listing-filename-sort="20240621-proposal-template copy.md">
+<tr data-index="42" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="1" data-listing-word-count-sort="107" data-listing-title-sort="Proposed: Command Traces with Server Backend" data-listing-filename-sort="20240621-proposal-template copy.md">
 <td>
 <a href="./decisions/20240621-proposal-template copy.html" class="title listing-title">Proposed: Command Traces with Server Backend</a>
 </td>
@@ -707,7 +707,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240621-proposal-template copy.html" class="filename listing-filename">20240621-proposal-template copy.md</a>
 </td>
 </tr>
-<tr data-index="43" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="2" data-listing-word-count-sort="346" data-listing-title-sort="Proposed: Image Captioning Tool" data-listing-filename-sort="20240621-caption-photos-for-cicd.md">
+<tr data-index="43" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="346" data-listing-title-sort="Proposed: Image Captioning Tool" data-listing-filename-sort="20240621-caption-photos-for-cicd.md">
 <td>
 <a href="./decisions/20240621-caption-photos-for-cicd.html" class="title listing-title">Proposed: Image Captioning Tool</a>
 </td>
@@ -718,7 +718,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240621-caption-photos-for-cicd.html" class="filename listing-filename">20240621-caption-photos-for-cicd.md</a>
 </td>
 </tr>
-<tr data-index="44" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="3" data-listing-word-count-sort="446" data-listing-title-sort="Proposed: Transforming Schedule DAG into a Left-child Right-sibling Binary Tree" data-listing-filename-sort="20240618-schedule-as-binary-tree.md">
+<tr data-index="44" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="3" data-listing-word-count-sort="446" data-listing-title-sort="Proposed: Transforming Schedule DAG into a Left-child Right-sibling Binary Tree" data-listing-filename-sort="20240618-schedule-as-binary-tree.md">
 <td>
 <a href="./decisions/20240618-schedule-as-binary-tree.html" class="title listing-title">Proposed: Transforming Schedule DAG into a Left-child Right-sibling Binary Tree</a>
 </td>
@@ -729,7 +729,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240618-schedule-as-binary-tree.html" class="filename listing-filename">20240618-schedule-as-binary-tree.md</a>
 </td>
 </tr>
-<tr data-index="45" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="2" data-listing-word-count-sort="266" data-listing-title-sort="Proposed: 4 Player Test V-Sekai" data-listing-filename-sort="20240618-4-player-test-vsekai.md">
+<tr data-index="45" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="266" data-listing-title-sort="Proposed: 4 Player Test V-Sekai" data-listing-filename-sort="20240618-4-player-test-vsekai.md">
 <td>
 <a href="./decisions/20240618-4-player-test-vsekai.html" class="title listing-title">Proposed: 4 Player Test V-Sekai</a>
 </td>
@@ -740,7 +740,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240618-4-player-test-vsekai.html" class="filename listing-filename">20240618-4-player-test-vsekai.md</a>
 </td>
 </tr>
-<tr data-index="46" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="2" data-listing-word-count-sort="330" data-listing-title-sort="Proposed: Triangle to Quad Mesh Dataset Creation" data-listing-filename-sort="20240616-request-for-quad-mesh-dataset.md">
+<tr data-index="46" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="330" data-listing-title-sort="Proposed: Triangle to Quad Mesh Dataset Creation" data-listing-filename-sort="20240616-request-for-quad-mesh-dataset.md">
 <td>
 <a href="./decisions/20240616-request-for-quad-mesh-dataset.html" class="title listing-title">Proposed: Triangle to Quad Mesh Dataset Creation</a>
 </td>
@@ -751,7 +751,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240616-request-for-quad-mesh-dataset.html" class="filename listing-filename">20240616-request-for-quad-mesh-dataset.md</a>
 </td>
 </tr>
-<tr data-index="47" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="2" data-listing-word-count-sort="363" data-listing-title-sort="Proposed: Explain the concept of Mesh Transformers" data-listing-filename-sort="20240615-what-is-mesh-transformers.md">
+<tr data-index="47" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="363" data-listing-title-sort="Proposed: Explain the concept of Mesh Transformers" data-listing-filename-sort="20240615-what-is-mesh-transformers.md">
 <td>
 <a href="./decisions/20240615-what-is-mesh-transformers.html" class="title listing-title">Proposed: Explain the concept of Mesh Transformers</a>
 </td>
@@ -762,7 +762,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240615-what-is-mesh-transformers.html" class="filename listing-filename">20240615-what-is-mesh-transformers.md</a>
 </td>
 </tr>
-<tr data-index="48" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="2" data-listing-word-count-sort="361" data-listing-title-sort="Proposed: Dataset Scaling for Training Mesh Transformer" data-listing-filename-sort="20240613-training-dataset.md">
+<tr data-index="48" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="361" data-listing-title-sort="Proposed: Dataset Scaling for Training Mesh Transformer" data-listing-filename-sort="20240613-training-dataset.md">
 <td>
 <a href="./decisions/20240613-training-dataset.html" class="title listing-title">Proposed: Dataset Scaling for Training Mesh Transformer</a>
 </td>
@@ -773,7 +773,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240613-training-dataset.html" class="filename listing-filename">20240613-training-dataset.md</a>
 </td>
 </tr>
-<tr data-index="49" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="3" data-listing-word-count-sort="411" data-listing-title-sort="Proposed: Dataset Creation with CSG" data-listing-filename-sort="20240613-training-dataset-creation-with-csg.md">
+<tr data-index="49" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="3" data-listing-word-count-sort="411" data-listing-title-sort="Proposed: Dataset Creation with CSG" data-listing-filename-sort="20240613-training-dataset-creation-with-csg.md">
 <td>
 <a href="./decisions/20240613-training-dataset-creation-with-csg.html" class="title listing-title">Proposed: Dataset Creation with CSG</a>
 </td>
@@ -784,7 +784,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240613-training-dataset-creation-with-csg.html" class="filename listing-filename">20240613-training-dataset-creation-with-csg.md</a>
 </td>
 </tr>
-<tr data-index="50" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="2" data-listing-word-count-sort="296" data-listing-title-sort="Proposed: Modify the Mesh Transformer for Quads" data-listing-filename-sort="20240613-modifying-the-mesh-transformer-for-quads.md">
+<tr data-index="50" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="296" data-listing-title-sort="Proposed: Modify the Mesh Transformer for Quads" data-listing-filename-sort="20240613-modifying-the-mesh-transformer-for-quads.md">
 <td>
 <a href="./decisions/20240613-modifying-the-mesh-transformer-for-quads.html" class="title listing-title">Proposed: Modify the Mesh Transformer for Quads</a>
 </td>
@@ -795,7 +795,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240613-modifying-the-mesh-transformer-for-quads.html" class="filename listing-filename">20240613-modifying-the-mesh-transformer-for-quads.md</a>
 </td>
 </tr>
-<tr data-index="51" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="3" data-listing-word-count-sort="411" data-listing-title-sort="Proposed: Training Mesh Transformer for 3D Avatar Creation" data-listing-filename-sort="20240613-1k-quad-limit.md">
+<tr data-index="51" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="3" data-listing-word-count-sort="411" data-listing-title-sort="Proposed: Training Mesh Transformer for 3D Avatar Creation" data-listing-filename-sort="20240613-1k-quad-limit.md">
 <td>
 <a href="./decisions/20240613-1k-quad-limit.html" class="title listing-title">Proposed: Training Mesh Transformer for 3D Avatar Creation</a>
 </td>
@@ -806,7 +806,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240613-1k-quad-limit.html" class="filename listing-filename">20240613-1k-quad-limit.md</a>
 </td>
 </tr>
-<tr data-index="52" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="2" data-listing-word-count-sort="298" data-listing-title-sort="Proposed: Managing Multiple Training Runs in Separate Pods" data-listing-filename-sort="20240611-test-1x-and-4x.md">
+<tr data-index="52" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="298" data-listing-title-sort="Proposed: Managing Multiple Training Runs in Separate Pods" data-listing-filename-sort="20240611-test-1x-and-4x.md">
 <td>
 <a href="./decisions/20240611-test-1x-and-4x.html" class="title listing-title">Proposed: Managing Multiple Training Runs in Separate Pods</a>
 </td>
@@ -817,7 +817,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240611-test-1x-and-4x.html" class="filename listing-filename">20240611-test-1x-and-4x.md</a>
 </td>
 </tr>
-<tr data-index="53" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="2" data-listing-word-count-sort="264" data-listing-title-sort="Proposed: Switch learning rate to be lower." data-listing-filename-sort="20240611-lower-learning-rate.md">
+<tr data-index="53" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="264" data-listing-title-sort="Proposed: Switch learning rate to be lower." data-listing-filename-sort="20240611-lower-learning-rate.md">
 <td>
 <a href="./decisions/20240611-lower-learning-rate.html" class="title listing-title">Proposed: Switch learning rate to be lower.</a>
 </td>
@@ -828,7 +828,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240611-lower-learning-rate.html" class="filename listing-filename">20240611-lower-learning-rate.md</a>
 </td>
 </tr>
-<tr data-index="54" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="6" data-listing-word-count-sort="1009" data-listing-title-sort="Accepted: Better Skeleton Merge with Robust Skin Weight Transfer" data-listing-filename-sort="20240608-skin-weight-transfer-skeleton-merge.md">
+<tr data-index="54" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="6" data-listing-word-count-sort="1009" data-listing-title-sort="Accepted: Better Skeleton Merge with Robust Skin Weight Transfer" data-listing-filename-sort="20240608-skin-weight-transfer-skeleton-merge.md">
 <td>
 <a href="./decisions/20240608-skin-weight-transfer-skeleton-merge.html" class="title listing-title">Accepted: Better Skeleton Merge with Robust Skin Weight Transfer</a>
 </td>
@@ -839,7 +839,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240608-skin-weight-transfer-skeleton-merge.html" class="filename listing-filename">20240608-skin-weight-transfer-skeleton-merge.md</a>
 </td>
 </tr>
-<tr data-index="55" data-listing-file-modified-sort="1730535490042" data-listing-reading-time-sort="5" data-listing-word-count-sort="973" data-listing-title-sort="Accepted: Use the Humanoid Profile for Character Motion Mirroring" data-listing-filename-sort="20240608-for-skeleton-mirroring-use-the-godot-humanoid.md">
+<tr data-index="55" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="5" data-listing-word-count-sort="973" data-listing-title-sort="Accepted: Use the Humanoid Profile for Character Motion Mirroring" data-listing-filename-sort="20240608-for-skeleton-mirroring-use-the-godot-humanoid.md">
 <td>
 <a href="./decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html" class="title listing-title">Accepted: Use the Humanoid Profile for Character Motion Mirroring</a>
 </td>
@@ -850,7 +850,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html" class="filename listing-filename">20240608-for-skeleton-mirroring-use-the-godot-humanoid.md</a>
 </td>
 </tr>
-<tr data-index="56" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="3" data-listing-word-count-sort="440" data-listing-title-sort="Proposal: Sustainable Version Management for Godot Engine in V-Sekai" data-listing-filename-sort="20240605-sustainable-version-management-for-godot-engine-in-v-sekai.md">
+<tr data-index="56" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="3" data-listing-word-count-sort="440" data-listing-title-sort="Proposal: Sustainable Version Management for Godot Engine in V-Sekai" data-listing-filename-sort="20240605-sustainable-version-management-for-godot-engine-in-v-sekai.md">
 <td>
 <a href="./decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html" class="title listing-title">Proposal: Sustainable Version Management for Godot Engine in V-Sekai</a>
 </td>
@@ -861,7 +861,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html" class="filename listing-filename">20240605-sustainable-version-management-for-godot-engine-in-v-sekai.md</a>
 </td>
 </tr>
-<tr data-index="57" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="3" data-listing-word-count-sort="489" data-listing-title-sort="Proposed: Improve the Godot Ecosystem" data-listing-filename-sort="20240529-improve-godot-import-ecosystem.md">
+<tr data-index="57" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="3" data-listing-word-count-sort="489" data-listing-title-sort="Proposed: Improve the Godot Ecosystem" data-listing-filename-sort="20240529-improve-godot-import-ecosystem.md">
 <td>
 <a href="./decisions/20240529-improve-godot-import-ecosystem.html" class="title listing-title">Proposed: Improve the Godot Ecosystem</a>
 </td>
@@ -872,7 +872,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240529-improve-godot-import-ecosystem.html" class="filename listing-filename">20240529-improve-godot-import-ecosystem.md</a>
 </td>
 </tr>
-<tr data-index="58" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="274" data-listing-title-sort="Proposed: Godot Engine as Wasm Importer" data-listing-filename-sort="20240528-pipeline-godot-wasm-importer.md">
+<tr data-index="58" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="274" data-listing-title-sort="Proposed: Godot Engine as Wasm Importer" data-listing-filename-sort="20240528-pipeline-godot-wasm-importer.md">
 <td>
 <a href="./decisions/20240528-pipeline-godot-wasm-importer.html" class="title listing-title">Proposed: Godot Engine as Wasm Importer</a>
 </td>
@@ -883,7 +883,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240528-pipeline-godot-wasm-importer.html" class="filename listing-filename">20240528-pipeline-godot-wasm-importer.md</a>
 </td>
 </tr>
-<tr data-index="59" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="1" data-listing-word-count-sort="107" data-listing-title-sort="Proposed: Draft WebRTC Relay Test" data-listing-filename-sort="20240522-webrtc-relay-test.md">
+<tr data-index="59" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="1" data-listing-word-count-sort="107" data-listing-title-sort="Proposed: Draft WebRTC Relay Test" data-listing-filename-sort="20240522-webrtc-relay-test.md">
 <td>
 <a href="./decisions/20240522-webrtc-relay-test.html" class="title listing-title">Proposed: Draft WebRTC Relay Test</a>
 </td>
@@ -894,7 +894,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240522-webrtc-relay-test.html" class="filename listing-filename">20240522-webrtc-relay-test.md</a>
 </td>
 </tr>
-<tr data-index="60" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="346" data-listing-title-sort="Draft: shadermotion to BVH" data-listing-filename-sort="20240522-shader-motion-to-bvh.md">
+<tr data-index="60" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="346" data-listing-title-sort="Draft: shadermotion to BVH" data-listing-filename-sort="20240522-shader-motion-to-bvh.md">
 <td>
 <a href="./decisions/20240522-shader-motion-to-bvh.html" class="title listing-title">Draft: shadermotion to BVH</a>
 </td>
@@ -905,7 +905,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240522-shader-motion-to-bvh.html" class="filename listing-filename">20240522-shader-motion-to-bvh.md</a>
 </td>
 </tr>
-<tr data-index="61" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="343" data-listing-title-sort="Draft: View the worlds and interact with people in VR without being in VR via a Discord Inward Portal" data-listing-filename-sort="20240522-discord-inworld-portal.md">
+<tr data-index="61" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="343" data-listing-title-sort="Draft: View the worlds and interact with people in VR without being in VR via a Discord Inward Portal" data-listing-filename-sort="20240522-discord-inworld-portal.md">
 <td>
 <a href="./decisions/20240522-discord-inworld-portal.html" class="title listing-title">Draft: View the worlds and interact with people in VR without being in VR via a Discord Inward Portal</a>
 </td>
@@ -916,7 +916,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240522-discord-inworld-portal.html" class="filename listing-filename">20240522-discord-inworld-portal.md</a>
 </td>
 </tr>
-<tr data-index="62" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="3" data-listing-word-count-sort="407" data-listing-title-sort="Draft: Notify community members and users about activity and updates via a Discord bot" data-listing-filename-sort="20240522-discord-bot.md">
+<tr data-index="62" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="3" data-listing-word-count-sort="407" data-listing-title-sort="Draft: Notify community members and users about activity and updates via a Discord bot" data-listing-filename-sort="20240522-discord-bot.md">
 <td>
 <a href="./decisions/20240522-discord-bot.html" class="title listing-title">Draft: Notify community members and users about activity and updates via a Discord bot</a>
 </td>
@@ -927,7 +927,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240522-discord-bot.html" class="filename listing-filename">20240522-discord-bot.md</a>
 </td>
 </tr>
-<tr data-index="63" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="367" data-listing-title-sort="Accepted: Wasm Cache Incident Report" data-listing-filename-sort="20240511-wasm-cache-incident.md">
+<tr data-index="63" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="367" data-listing-title-sort="Accepted: Wasm Cache Incident Report" data-listing-filename-sort="20240511-wasm-cache-incident.md">
 <td>
 <a href="./decisions/20240511-wasm-cache-incident.html" class="title listing-title">Accepted: Wasm Cache Incident Report</a>
 </td>
@@ -938,7 +938,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240511-wasm-cache-incident.html" class="filename listing-filename">20240511-wasm-cache-incident.md</a>
 </td>
 </tr>
-<tr data-index="64" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="351" data-listing-title-sort="Rejected: VR Game with 80 Players and One World Server" data-listing-filename-sort="20240511-review-80-vr.md">
+<tr data-index="64" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="351" data-listing-title-sort="Rejected: VR Game with 80 Players and One World Server" data-listing-filename-sort="20240511-review-80-vr.md">
 <td>
 <a href="./decisions/20240511-review-80-vr.html" class="title listing-title">Rejected: VR Game with 80 Players and One World Server</a>
 </td>
@@ -949,7 +949,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240511-review-80-vr.html" class="filename listing-filename">20240511-review-80-vr.md</a>
 </td>
 </tr>
-<tr data-index="65" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="319" data-listing-title-sort="Proposed: Can I use V-Sekai for 3d assets &amp; 3d extensions?" data-listing-filename-sort="20240502-where-can-I-use-gltf.md">
+<tr data-index="65" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="319" data-listing-title-sort="Proposed: Can I use V-Sekai for 3d assets &amp; 3d extensions?" data-listing-filename-sort="20240502-where-can-I-use-gltf.md">
 <td>
 <a href="./decisions/20240502-where-can-I-use-gltf.html" class="title listing-title">Proposed: Can I use V-Sekai for 3d assets &amp; 3d extensions?</a>
 </td>
@@ -960,7 +960,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240502-where-can-I-use-gltf.html" class="filename listing-filename">20240502-where-can-I-use-gltf.md</a>
 </td>
 </tr>
-<tr data-index="66" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="4" data-listing-word-count-sort="622" data-listing-title-sort="Proposed: Launching the mvsqlite rdbms server" data-listing-filename-sort="20240502-mvsqlite-launchd.md">
+<tr data-index="66" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="4" data-listing-word-count-sort="622" data-listing-title-sort="Proposed: Launching the mvsqlite rdbms server" data-listing-filename-sort="20240502-mvsqlite-launchd.md">
 <td>
 <a href="./decisions/20240502-mvsqlite-launchd.html" class="title listing-title">Proposed: Launching the mvsqlite rdbms server</a>
 </td>
@@ -971,7 +971,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240502-mvsqlite-launchd.html" class="filename listing-filename">20240502-mvsqlite-launchd.md</a>
 </td>
 </tr>
-<tr data-index="67" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="3" data-listing-word-count-sort="437" data-listing-title-sort="Proposed: Stress Testing Godot Engine's Networking System" data-listing-filename-sort="20240502-mesh-object-sync-benchmark.md">
+<tr data-index="67" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="3" data-listing-word-count-sort="437" data-listing-title-sort="Proposed: Stress Testing Godot Engine's Networking System" data-listing-filename-sort="20240502-mesh-object-sync-benchmark.md">
 <td>
 <a href="./decisions/20240502-mesh-object-sync-benchmark.html" class="title listing-title">Proposed: Stress Testing Godot Engine’s Networking System</a>
 </td>
@@ -982,7 +982,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240502-mesh-object-sync-benchmark.html" class="filename listing-filename">20240502-mesh-object-sync-benchmark.md</a>
 </td>
 </tr>
-<tr data-index="68" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="369" data-listing-title-sort="Proposed: Process the glTF2 input file and return it as is" data-listing-filename-sort="20240502-membrane-framework-identity-post.md">
+<tr data-index="68" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="369" data-listing-title-sort="Proposed: Process the glTF2 input file and return it as is" data-listing-filename-sort="20240502-membrane-framework-identity-post.md">
 <td>
 <a href="./decisions/20240502-membrane-framework-identity-post.html" class="title listing-title">Proposed: Process the glTF2 input file and return it as is</a>
 </td>
@@ -993,7 +993,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240502-membrane-framework-identity-post.html" class="filename listing-filename">20240502-membrane-framework-identity-post.md</a>
 </td>
 </tr>
-<tr data-index="69" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="259" data-listing-title-sort="Proposed: Enable Windows 11 Installation on Older Computers" data-listing-filename-sort="20240502-install-windows-on-older-computers.md">
+<tr data-index="69" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="259" data-listing-title-sort="Proposed: Enable Windows 11 Installation on Older Computers" data-listing-filename-sort="20240502-install-windows-on-older-computers.md">
 <td>
 <a href="./decisions/20240502-install-windows-on-older-computers.html" class="title listing-title">Proposed: Enable Windows 11 Installation on Older Computers</a>
 </td>
@@ -1004,7 +1004,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240502-install-windows-on-older-computers.html" class="filename listing-filename">20240502-install-windows-on-older-computers.md</a>
 </td>
 </tr>
-<tr data-index="70" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="3" data-listing-word-count-sort="429" data-listing-title-sort="Proposed: Workflows for 3D Model Conversion" data-listing-filename-sort="20240502-gltf-fbx-tscn-vrm.md">
+<tr data-index="70" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="3" data-listing-word-count-sort="429" data-listing-title-sort="Proposed: Workflows for 3D Model Conversion" data-listing-filename-sort="20240502-gltf-fbx-tscn-vrm.md">
 <td>
 <a href="./decisions/20240502-gltf-fbx-tscn-vrm.html" class="title listing-title">Proposed: Workflows for 3D Model Conversion</a>
 </td>
@@ -1015,7 +1015,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240502-gltf-fbx-tscn-vrm.html" class="filename listing-filename">20240502-gltf-fbx-tscn-vrm.md</a>
 </td>
 </tr>
-<tr data-index="71" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="345" data-listing-title-sort="Proposed: Stuck / Recharge Cycle" data-listing-filename-sort="20240425-recharge-cycle.md">
+<tr data-index="71" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="345" data-listing-title-sort="Proposed: Stuck / Recharge Cycle" data-listing-filename-sort="20240425-recharge-cycle.md">
 <td>
 <a href="./decisions/20240425-recharge-cycle.html" class="title listing-title">Proposed: Stuck / Recharge Cycle</a>
 </td>
@@ -1026,7 +1026,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240425-recharge-cycle.html" class="filename listing-filename">20240425-recharge-cycle.md</a>
 </td>
 </tr>
-<tr data-index="72" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="305" data-listing-title-sort="Proposed: ChatGPT-4 Based Proposal Prompt System" data-listing-filename-sort="20240425-proposal-prompt-system.md">
+<tr data-index="72" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="305" data-listing-title-sort="Proposed: ChatGPT-4 Based Proposal Prompt System" data-listing-filename-sort="20240425-proposal-prompt-system.md">
 <td>
 <a href="./decisions/20240425-proposal-prompt-system.html" class="title listing-title">Proposed: ChatGPT-4 Based Proposal Prompt System</a>
 </td>
@@ -1037,7 +1037,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240425-proposal-prompt-system.html" class="filename listing-filename">20240425-proposal-prompt-system.md</a>
 </td>
 </tr>
-<tr data-index="73" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="239" data-listing-title-sort="Accepted: Prioritizing Valve Controllers Over Meta Quest 3 Controllers" data-listing-filename-sort="20240424-reset-steamvr-controllers.md">
+<tr data-index="73" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="239" data-listing-title-sort="Accepted: Prioritizing Valve Controllers Over Meta Quest 3 Controllers" data-listing-filename-sort="20240424-reset-steamvr-controllers.md">
 <td>
 <a href="./decisions/20240424-reset-steamvr-controllers.html" class="title listing-title">Accepted: Prioritizing Valve Controllers Over Meta Quest 3 Controllers</a>
 </td>
@@ -1048,7 +1048,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240424-reset-steamvr-controllers.html" class="filename listing-filename">20240424-reset-steamvr-controllers.md</a>
 </td>
 </tr>
-<tr data-index="74" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="360" data-listing-title-sort="Accepted: Building a Metaverse with Glue Mechanic in V-Sekai" data-listing-filename-sort="20240423-building-metaverse-with-glue-mechanic.md">
+<tr data-index="74" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="360" data-listing-title-sort="Accepted: Building a Metaverse with Glue Mechanic in V-Sekai" data-listing-filename-sort="20240423-building-metaverse-with-glue-mechanic.md">
 <td>
 <a href="./decisions/20240423-building-metaverse-with-glue-mechanic.html" class="title listing-title">Accepted: Building a Metaverse with Glue Mechanic in V-Sekai</a>
 </td>
@@ -1059,7 +1059,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240423-building-metaverse-with-glue-mechanic.html" class="filename listing-filename">20240423-building-metaverse-with-glue-mechanic.md</a>
 </td>
 </tr>
-<tr data-index="75" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="3" data-listing-word-count-sort="423" data-listing-title-sort="Proposed: Town Courier" data-listing-filename-sort="20240418-college-quest.md">
+<tr data-index="75" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="3" data-listing-word-count-sort="423" data-listing-title-sort="Proposed: Town Courier" data-listing-filename-sort="20240418-college-quest.md">
 <td>
 <a href="./decisions/20240418-college-quest.html" class="title listing-title">Proposed: Town Courier</a>
 </td>
@@ -1070,7 +1070,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240418-college-quest.html" class="filename listing-filename">20240418-college-quest.md</a>
 </td>
 </tr>
-<tr data-index="76" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="337" data-listing-title-sort="Proposed: Implementing a 3D Previewer for GLTF with XMP Metadata" data-listing-filename-sort="20240416-previewer-upload-gltf-to-glb.md">
+<tr data-index="76" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="337" data-listing-title-sort="Proposed: Implementing a 3D Previewer for GLTF with XMP Metadata" data-listing-filename-sort="20240416-previewer-upload-gltf-to-glb.md">
 <td>
 <a href="./decisions/20240416-previewer-upload-gltf-to-glb.html" class="title listing-title">Proposed: Implementing a 3D Previewer for GLTF with XMP Metadata</a>
 </td>
@@ -1081,7 +1081,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240416-previewer-upload-gltf-to-glb.html" class="filename listing-filename">20240416-previewer-upload-gltf-to-glb.md</a>
 </td>
 </tr>
-<tr data-index="77" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="3" data-listing-word-count-sort="591" data-listing-title-sort="Proposed: Train quad-based Meshgpt within constraints" data-listing-filename-sort="20240413-training-quad-based-meshgpt-with-40gb-vram.md">
+<tr data-index="77" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="3" data-listing-word-count-sort="591" data-listing-title-sort="Proposed: Train quad-based Meshgpt within constraints" data-listing-filename-sort="20240413-training-quad-based-meshgpt-with-40gb-vram.md">
 <td>
 <a href="./decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html" class="title listing-title">Proposed: Train quad-based Meshgpt within constraints</a>
 </td>
@@ -1092,7 +1092,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html" class="filename listing-filename">20240413-training-quad-based-meshgpt-with-40gb-vram.md</a>
 </td>
 </tr>
-<tr data-index="78" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="363" data-listing-title-sort="Proposed: Calling Open Source LLM with Aria" data-listing-filename-sort="20240413-calling-opensource-llm-with-aria.md">
+<tr data-index="78" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="363" data-listing-title-sort="Proposed: Calling Open Source LLM with Aria" data-listing-filename-sort="20240413-calling-opensource-llm-with-aria.md">
 <td>
 <a href="./decisions/20240413-calling-opensource-llm-with-aria.html" class="title listing-title">Proposed: Calling Open Source LLM with Aria</a>
 </td>
@@ -1103,7 +1103,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240413-calling-opensource-llm-with-aria.html" class="filename listing-filename">20240413-calling-opensource-llm-with-aria.md</a>
 </td>
 </tr>
-<tr data-index="79" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="3" data-listing-word-count-sort="460" data-listing-title-sort="Proposed: Implementing a 3D Multiplayer Movement System with Parented Objects and Inventory Management" data-listing-filename-sort="20240411-multiplayer-movement-with-parented-obejcts.md">
+<tr data-index="79" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="3" data-listing-word-count-sort="460" data-listing-title-sort="Proposed: Implementing a 3D Multiplayer Movement System with Parented Objects and Inventory Management" data-listing-filename-sort="20240411-multiplayer-movement-with-parented-obejcts.md">
 <td>
 <a href="./decisions/20240411-multiplayer-movement-with-parented-obejcts.html" class="title listing-title">Proposed: Implementing a 3D Multiplayer Movement System with Parented Objects and Inventory Management</a>
 </td>
@@ -1114,7 +1114,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240411-multiplayer-movement-with-parented-obejcts.html" class="filename listing-filename">20240411-multiplayer-movement-with-parented-obejcts.md</a>
 </td>
 </tr>
-<tr data-index="80" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="279" data-listing-title-sort="Rejected: Binding GDExtension to a C-like Language for Libgodot to Implement a Distributed Simulation" data-listing-filename-sort="20240411-elixir-libgodot-zig.md">
+<tr data-index="80" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="279" data-listing-title-sort="Rejected: Binding GDExtension to a C-like Language for Libgodot to Implement a Distributed Simulation" data-listing-filename-sort="20240411-elixir-libgodot-zig.md">
 <td>
 <a href="./decisions/20240411-elixir-libgodot-zig.html" class="title listing-title">Rejected: Binding GDExtension to a C-like Language for Libgodot to Implement a Distributed Simulation</a>
 </td>
@@ -1125,7 +1125,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240411-elixir-libgodot-zig.html" class="filename listing-filename">20240411-elixir-libgodot-zig.md</a>
 </td>
 </tr>
-<tr data-index="81" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="314" data-listing-title-sort="Proposed: Use Bundlex for Binding GDExtension to Elixir for Libgodot to Implement a Distributed Simulation" data-listing-filename-sort="20240411-elixir-libgodot-bundlex.md">
+<tr data-index="81" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="314" data-listing-title-sort="Proposed: Use Bundlex for Binding GDExtension to Elixir for Libgodot to Implement a Distributed Simulation" data-listing-filename-sort="20240411-elixir-libgodot-bundlex.md">
 <td>
 <a href="./decisions/20240411-elixir-libgodot-bundlex.html" class="title listing-title">Proposed: Use Bundlex for Binding GDExtension to Elixir for Libgodot to Implement a Distributed Simulation</a>
 </td>
@@ -1136,7 +1136,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240411-elixir-libgodot-bundlex.html" class="filename listing-filename">20240411-elixir-libgodot-bundlex.md</a>
 </td>
 </tr>
-<tr data-index="82" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="3" data-listing-word-count-sort="472" data-listing-title-sort="Proposed: Implementing Elixir Data Models for Memory, Local, Bulk, and Global Storage" data-listing-filename-sort="20240410-data-storage-elixir.md">
+<tr data-index="82" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="3" data-listing-word-count-sort="472" data-listing-title-sort="Proposed: Implementing Elixir Data Models for Memory, Local, Bulk, and Global Storage" data-listing-filename-sort="20240410-data-storage-elixir.md">
 <td>
 <a href="./decisions/20240410-data-storage-elixir.html" class="title listing-title">Proposed: Implementing Elixir Data Models for Memory, Local, Bulk, and Global Storage</a>
 </td>
@@ -1147,7 +1147,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240410-data-storage-elixir.html" class="filename listing-filename">20240410-data-storage-elixir.md</a>
 </td>
 </tr>
-<tr data-index="83" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="3" data-listing-word-count-sort="424" data-listing-title-sort="Rejected: RabbitMQ RA vs SQLite on FoundationDB vs CockroachDB" data-listing-filename-sort="20240409-elixir-raft-vs-sqlite-fdb.md">
+<tr data-index="83" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="3" data-listing-word-count-sort="424" data-listing-title-sort="Rejected: RabbitMQ RA vs SQLite on FoundationDB vs CockroachDB" data-listing-filename-sort="20240409-elixir-raft-vs-sqlite-fdb.md">
 <td>
 <a href="./decisions/20240409-elixir-raft-vs-sqlite-fdb.html" class="title listing-title">Rejected: RabbitMQ RA vs SQLite on FoundationDB vs CockroachDB</a>
 </td>
@@ -1158,7 +1158,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240409-elixir-raft-vs-sqlite-fdb.html" class="filename listing-filename">20240409-elixir-raft-vs-sqlite-fdb.md</a>
 </td>
 </tr>
-<tr data-index="84" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="387" data-listing-title-sort="Accepted: &quot;Sunny Park&quot; Test Case for 3D Tile Sync" data-listing-filename-sort="20240409-crud-godot-tiles.md">
+<tr data-index="84" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="387" data-listing-title-sort="Accepted: &quot;Sunny Park&quot; Test Case for 3D Tile Sync" data-listing-filename-sort="20240409-crud-godot-tiles.md">
 <td>
 <a href="./decisions/20240409-crud-godot-tiles.html" class="title listing-title">Accepted: “Sunny Park” Test Case for 3D Tile Sync</a>
 </td>
@@ -1169,7 +1169,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240409-crud-godot-tiles.html" class="filename listing-filename">20240409-crud-godot-tiles.md</a>
 </td>
 </tr>
-<tr data-index="85" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="366" data-listing-title-sort="Accepted: Focusing on PCVR vs Android Build vs Web Build" data-listing-filename-sort="20240407-pcvr-vs-standalone.md">
+<tr data-index="85" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="366" data-listing-title-sort="Accepted: Focusing on PCVR vs Android Build vs Web Build" data-listing-filename-sort="20240407-pcvr-vs-standalone.md">
 <td>
 <a href="./decisions/20240407-pcvr-vs-standalone.html" class="title listing-title">Accepted: Focusing on PCVR vs Android Build vs Web Build</a>
 </td>
@@ -1180,7 +1180,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240407-pcvr-vs-standalone.html" class="filename listing-filename">20240407-pcvr-vs-standalone.md</a>
 </td>
 </tr>
-<tr data-index="86" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="270" data-listing-title-sort="Proposed: Web-Based Exploration of V-Sekai" data-listing-filename-sort="20240406-web-based-explore.md">
+<tr data-index="86" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="270" data-listing-title-sort="Proposed: Web-Based Exploration of V-Sekai" data-listing-filename-sort="20240406-web-based-explore.md">
 <td>
 <a href="./decisions/20240406-web-based-explore.html" class="title listing-title">Proposed: Web-Based Exploration of V-Sekai</a>
 </td>
@@ -1191,7 +1191,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240406-web-based-explore.html" class="filename listing-filename">20240406-web-based-explore.md</a>
 </td>
 </tr>
-<tr data-index="87" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="265" data-listing-title-sort="Proposed: Provide a V-Sekai Starter Kit" data-listing-filename-sort="20240406-itch-github-actions.md">
+<tr data-index="87" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="265" data-listing-title-sort="Proposed: Provide a V-Sekai Starter Kit" data-listing-filename-sort="20240406-itch-github-actions.md">
 <td>
 <a href="./decisions/20240406-itch-github-actions.html" class="title listing-title">Proposed: Provide a V-Sekai Starter Kit</a>
 </td>
@@ -1202,7 +1202,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240406-itch-github-actions.html" class="filename listing-filename">20240406-itch-github-actions.md</a>
 </td>
 </tr>
-<tr data-index="88" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="3" data-listing-word-count-sort="474" data-listing-title-sort="Proposed: Material Shader Graphic Shirt with Sharp Edges" data-listing-filename-sort="20240401-shader-graphic.md">
+<tr data-index="88" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="3" data-listing-word-count-sort="474" data-listing-title-sort="Proposed: Material Shader Graphic Shirt with Sharp Edges" data-listing-filename-sort="20240401-shader-graphic.md">
 <td>
 <a href="./decisions/20240401-shader-graphic.html" class="title listing-title">Proposed: Material Shader Graphic Shirt with Sharp Edges</a>
 </td>
@@ -1213,7 +1213,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240401-shader-graphic.html" class="filename listing-filename">20240401-shader-graphic.md</a>
 </td>
 </tr>
-<tr data-index="89" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="4" data-listing-word-count-sort="623" data-listing-title-sort="Proposed: VRC and VRM compatibility" data-listing-filename-sort="20240331-vrc-vrm-compatibility.md">
+<tr data-index="89" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="4" data-listing-word-count-sort="623" data-listing-title-sort="Proposed: VRC and VRM compatibility" data-listing-filename-sort="20240331-vrc-vrm-compatibility.md">
 <td>
 <a href="./decisions/20240331-vrc-vrm-compatibility.html" class="title listing-title">Proposed: VRC and VRM compatibility</a>
 </td>
@@ -1224,7 +1224,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240331-vrc-vrm-compatibility.html" class="filename listing-filename">20240331-vrc-vrm-compatibility.md</a>
 </td>
 </tr>
-<tr data-index="90" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="4" data-listing-word-count-sort="602" data-listing-title-sort="Accepted: k8s on harvester hci" data-listing-filename-sort="20240330-k8s-harvester-hci.md">
+<tr data-index="90" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="4" data-listing-word-count-sort="602" data-listing-title-sort="Accepted: k8s on harvester hci" data-listing-filename-sort="20240330-k8s-harvester-hci.md">
 <td>
 <a href="./decisions/20240330-k8s-harvester-hci.html" class="title listing-title">Accepted: k8s on harvester hci</a>
 </td>
@@ -1235,7 +1235,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240330-k8s-harvester-hci.html" class="filename listing-filename">20240330-k8s-harvester-hci.md</a>
 </td>
 </tr>
-<tr data-index="91" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="338" data-listing-title-sort="Proposed: Hyperv windows Harvester Test" data-listing-filename-sort="20240330-hyperv-harvester-test.md">
+<tr data-index="91" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="338" data-listing-title-sort="Proposed: Hyperv windows Harvester Test" data-listing-filename-sort="20240330-hyperv-harvester-test.md">
 <td>
 <a href="./decisions/20240330-hyperv-harvester-test.html" class="title listing-title">Proposed: Hyperv windows Harvester Test</a>
 </td>
@@ -1246,7 +1246,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240330-hyperv-harvester-test.html" class="filename listing-filename">20240330-hyperv-harvester-test.md</a>
 </td>
 </tr>
-<tr data-index="92" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="4" data-listing-word-count-sort="765" data-listing-title-sort="Proposed: Integrating Helm for Kubernetes Runner Installation with S3 Cache" data-listing-filename-sort="20240330-gitlab-helm.md">
+<tr data-index="92" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="4" data-listing-word-count-sort="765" data-listing-title-sort="Proposed: Integrating Helm for Kubernetes Runner Installation with S3 Cache" data-listing-filename-sort="20240330-gitlab-helm.md">
 <td>
 <a href="./decisions/20240330-gitlab-helm.html" class="title listing-title">Proposed: Integrating Helm for Kubernetes Runner Installation with S3 Cache</a>
 </td>
@@ -1257,7 +1257,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240330-gitlab-helm.html" class="filename listing-filename">20240330-gitlab-helm.md</a>
 </td>
 </tr>
-<tr data-index="93" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="3" data-listing-word-count-sort="466" data-listing-title-sort="Proposed: CI/CD Setup with Docker and Other Platforms" data-listing-filename-sort="20240330-cicd-gitlab.md">
+<tr data-index="93" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="3" data-listing-word-count-sort="466" data-listing-title-sort="Proposed: CI/CD Setup with Docker and Other Platforms" data-listing-filename-sort="20240330-cicd-gitlab.md">
 <td>
 <a href="./decisions/20240330-cicd-gitlab.html" class="title listing-title">Proposed: CI/CD Setup with Docker and Other Platforms</a>
 </td>
@@ -1268,7 +1268,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240330-cicd-gitlab.html" class="filename listing-filename">20240330-cicd-gitlab.md</a>
 </td>
 </tr>
-<tr data-index="94" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="355" data-listing-title-sort="Proposed: Installing Helm Chart from a Git Repository using Rancher" data-listing-filename-sort="20240330-bitnami-rancher-helm-catalog.md">
+<tr data-index="94" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="355" data-listing-title-sort="Proposed: Installing Helm Chart from a Git Repository using Rancher" data-listing-filename-sort="20240330-bitnami-rancher-helm-catalog.md">
 <td>
 <a href="./decisions/20240330-bitnami-rancher-helm-catalog.html" class="title listing-title">Proposed: Installing Helm Chart from a Git Repository using Rancher</a>
 </td>
@@ -1279,7 +1279,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240330-bitnami-rancher-helm-catalog.html" class="filename listing-filename">20240330-bitnami-rancher-helm-catalog.md</a>
 </td>
 </tr>
-<tr data-index="95" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="284" data-listing-title-sort="Proposed: V-Sekai Setup as a Ready-to-Go Kit" data-listing-filename-sort="20240329-ready-to-go-kit-windows-11.md">
+<tr data-index="95" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="284" data-listing-title-sort="Proposed: V-Sekai Setup as a Ready-to-Go Kit" data-listing-filename-sort="20240329-ready-to-go-kit-windows-11.md">
 <td>
 <a href="./decisions/20240329-ready-to-go-kit-windows-11.html" class="title listing-title">Proposed: V-Sekai Setup as a Ready-to-Go Kit</a>
 </td>
@@ -1290,7 +1290,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240329-ready-to-go-kit-windows-11.html" class="filename listing-filename">20240329-ready-to-go-kit-windows-11.md</a>
 </td>
 </tr>
-<tr data-index="96" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="301" data-listing-title-sort="Proposed: Teaching Large Language Models (LLMs) with Goal-Task Planners" data-listing-filename-sort="20240326-verifying-and-finetuning-plans.md">
+<tr data-index="96" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="301" data-listing-title-sort="Proposed: Teaching Large Language Models (LLMs) with Goal-Task Planners" data-listing-filename-sort="20240326-verifying-and-finetuning-plans.md">
 <td>
 <a href="./decisions/20240326-verifying-and-finetuning-plans.html" class="title listing-title">Proposed: Teaching Large Language Models (LLMs) with Goal-Task Planners</a>
 </td>
@@ -1301,7 +1301,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240326-verifying-and-finetuning-plans.html" class="filename listing-filename">20240326-verifying-and-finetuning-plans.md</a>
 </td>
 </tr>
-<tr data-index="97" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="3" data-listing-word-count-sort="498" data-listing-title-sort="Proposed: &quot;Cafe Serenade&quot; - A VR Dating Sim Experience" data-listing-filename-sort="20240326-heartstrings-vr.md">
+<tr data-index="97" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="3" data-listing-word-count-sort="498" data-listing-title-sort="Proposed: &quot;Cafe Serenade&quot; - A VR Dating Sim Experience" data-listing-filename-sort="20240326-heartstrings-vr.md">
 <td>
 <a href="./decisions/20240326-heartstrings-vr.html" class="title listing-title">Proposed: “Cafe Serenade” - A VR Dating Sim Experience</a>
 </td>
@@ -1312,7 +1312,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240326-heartstrings-vr.html" class="filename listing-filename">20240326-heartstrings-vr.md</a>
 </td>
 </tr>
-<tr data-index="98" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="374" data-listing-title-sort="Proposed: for 3d Asset Schema Design and Database Backend Selection" data-listing-filename-sort="20240325-table-avatar-embedded-xmp.md">
+<tr data-index="98" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="374" data-listing-title-sort="Proposed: for 3d Asset Schema Design and Database Backend Selection" data-listing-filename-sort="20240325-table-avatar-embedded-xmp.md">
 <td>
 <a href="./decisions/20240325-table-avatar-embedded-xmp.html" class="title listing-title">Proposed: for 3d Asset Schema Design and Database Backend Selection</a>
 </td>
@@ -1323,7 +1323,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240325-table-avatar-embedded-xmp.html" class="filename listing-filename">20240325-table-avatar-embedded-xmp.md</a>
 </td>
 </tr>
-<tr data-index="99" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="371" data-listing-title-sort="Proposed: Synchronizing Blender and FDB-SQLite for Proxy Movement" data-listing-filename-sort="20240325-fdb-sqlite-blender-godot.md">
+<tr data-index="99" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="371" data-listing-title-sort="Proposed: Synchronizing Blender and FDB-SQLite for Proxy Movement" data-listing-filename-sort="20240325-fdb-sqlite-blender-godot.md">
 <td>
 <a href="./decisions/20240325-fdb-sqlite-blender-godot.html" class="title listing-title">Proposed: Synchronizing Blender and FDB-SQLite for Proxy Movement</a>
 </td>
@@ -1334,7 +1334,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240325-fdb-sqlite-blender-godot.html" class="filename listing-filename">20240325-fdb-sqlite-blender-godot.md</a>
 </td>
 </tr>
-<tr data-index="100" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="232" data-listing-title-sort="Proposed: V-Sekai Implementation Using SLC Framework" data-listing-filename-sort="20240324-v-sekai-as-slc.md">
+<tr data-index="100" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="232" data-listing-title-sort="Proposed: V-Sekai Implementation Using SLC Framework" data-listing-filename-sort="20240324-v-sekai-as-slc.md">
 <td>
 <a href="./decisions/20240324-v-sekai-as-slc.html" class="title listing-title">Proposed: V-Sekai Implementation Using SLC Framework</a>
 </td>
@@ -1345,7 +1345,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240324-v-sekai-as-slc.html" class="filename listing-filename">20240324-v-sekai-as-slc.md</a>
 </td>
 </tr>
-<tr data-index="101" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="292" data-listing-title-sort="Proposed: Real-Time Motion Capture and Animation Synchronization" data-listing-filename-sort="20240314-live-collab.md">
+<tr data-index="101" data-listing-file-modified-sort="1730559023686" data-listing-reading-time-sort="2" data-listing-word-count-sort="292" data-listing-title-sort="Proposed: Real-Time Motion Capture and Animation Synchronization" data-listing-filename-sort="20240314-live-collab.md">
 <td>
 <a href="./decisions/20240314-live-collab.html" class="title listing-title">Proposed: Real-Time Motion Capture and Animation Synchronization</a>
 </td>
@@ -1356,7 +1356,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240314-live-collab.html" class="filename listing-filename">20240314-live-collab.md</a>
 </td>
 </tr>
-<tr data-index="102" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="1" data-listing-word-count-sort="168" data-listing-title-sort="Proposed: Implement Ra in V-Sekai" data-listing-filename-sort="20240307-rabbitmq-ra.md">
+<tr data-index="102" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="1" data-listing-word-count-sort="168" data-listing-title-sort="Proposed: Implement Ra in V-Sekai" data-listing-filename-sort="20240307-rabbitmq-ra.md">
 <td>
 <a href="./decisions/20240307-rabbitmq-ra.html" class="title listing-title">Proposed: Implement Ra in V-Sekai</a>
 </td>
@@ -1367,7 +1367,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240307-rabbitmq-ra.html" class="filename listing-filename">20240307-rabbitmq-ra.md</a>
 </td>
 </tr>
-<tr data-index="103" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="3" data-listing-word-count-sort="435" data-listing-title-sort="Proposed: V-Sekai Game Launcher" data-listing-filename-sort="20240305-v-sekai-launcher.md">
+<tr data-index="103" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="3" data-listing-word-count-sort="435" data-listing-title-sort="Proposed: V-Sekai Game Launcher" data-listing-filename-sort="20240305-v-sekai-launcher.md">
 <td>
 <a href="./decisions/20240305-v-sekai-launcher.html" class="title listing-title">Proposed: V-Sekai Game Launcher</a>
 </td>
@@ -1378,7 +1378,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240305-v-sekai-launcher.html" class="filename listing-filename">20240305-v-sekai-launcher.md</a>
 </td>
 </tr>
-<tr data-index="104" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="32" data-listing-word-count-sort="6389" data-listing-title-sort="Proposed VRM mtoon in Substance Designer" data-listing-filename-sort="20240218-vrm-substance-editor.md">
+<tr data-index="104" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="32" data-listing-word-count-sort="6389" data-listing-title-sort="Proposed VRM mtoon in Substance Designer" data-listing-filename-sort="20240218-vrm-substance-editor.md">
 <td>
 <a href="./decisions/20240218-vrm-substance-editor.html" class="title listing-title">Proposed VRM mtoon in Substance Designer</a>
 </td>
@@ -1389,7 +1389,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240218-vrm-substance-editor.html" class="filename listing-filename">20240218-vrm-substance-editor.md</a>
 </td>
 </tr>
-<tr data-index="105" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="1" data-listing-word-count-sort="196" data-listing-title-sort="Accepted: VRM Acronym Correction" data-listing-filename-sort="20240218-vrm-acronym-correction.md">
+<tr data-index="105" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="1" data-listing-word-count-sort="196" data-listing-title-sort="Accepted: VRM Acronym Correction" data-listing-filename-sort="20240218-vrm-acronym-correction.md">
 <td>
 <a href="./decisions/20240218-vrm-acronym-correction.html" class="title listing-title">Accepted: VRM Acronym Correction</a>
 </td>
@@ -1400,7 +1400,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240218-vrm-acronym-correction.html" class="filename listing-filename">20240218-vrm-acronym-correction.md</a>
 </td>
 </tr>
-<tr data-index="106" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="309" data-listing-title-sort="Proposed: Blender to Godot API Conversion" data-listing-filename-sort="20240218-blender-to-godot.md">
+<tr data-index="106" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="309" data-listing-title-sort="Proposed: Blender to Godot API Conversion" data-listing-filename-sort="20240218-blender-to-godot.md">
 <td>
 <a href="./decisions/20240218-blender-to-godot.html" class="title listing-title">Proposed: Blender to Godot API Conversion</a>
 </td>
@@ -1411,7 +1411,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240218-blender-to-godot.html" class="filename listing-filename">20240218-blender-to-godot.md</a>
 </td>
 </tr>
-<tr data-index="107" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="359" data-listing-title-sort="Proposed: for using workloads to emulate the usage patterns" data-listing-filename-sort="20240217-workload-benchmarking.md">
+<tr data-index="107" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="359" data-listing-title-sort="Proposed: for using workloads to emulate the usage patterns" data-listing-filename-sort="20240217-workload-benchmarking.md">
 <td>
 <a href="./decisions/20240217-workload-benchmarking.html" class="title listing-title">Proposed: for using workloads to emulate the usage patterns</a>
 </td>
@@ -1422,7 +1422,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240217-workload-benchmarking.html" class="filename listing-filename">20240217-workload-benchmarking.md</a>
 </td>
 </tr>
-<tr data-index="108" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="384" data-listing-title-sort="Proposed: Adoption of Intended Effort Versioning (EffVer) in V-Sekai" data-listing-filename-sort="20240217-intended-effort-versioning.md">
+<tr data-index="108" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="384" data-listing-title-sort="Proposed: Adoption of Intended Effort Versioning (EffVer) in V-Sekai" data-listing-filename-sort="20240217-intended-effort-versioning.md">
 <td>
 <a href="./decisions/20240217-intended-effort-versioning.html" class="title listing-title">Proposed: Adoption of Intended Effort Versioning (EffVer) in V-Sekai</a>
 </td>
@@ -1433,7 +1433,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240217-intended-effort-versioning.html" class="filename listing-filename">20240217-intended-effort-versioning.md</a>
 </td>
 </tr>
-<tr data-index="109" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="7" data-listing-word-count-sort="1223" data-listing-title-sort="Proposed: Implementation of Essential Tuple Normalization Form (ETNF) for relational databases (rdbms, sql)" data-listing-filename-sort="20240217-essential-typle-normalization-form.md">
+<tr data-index="109" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="7" data-listing-word-count-sort="1223" data-listing-title-sort="Proposed: Implementation of Essential Tuple Normalization Form (ETNF) for relational databases (rdbms, sql)" data-listing-filename-sort="20240217-essential-typle-normalization-form.md">
 <td>
 <a href="./decisions/20240217-essential-typle-normalization-form.html" class="title listing-title">Proposed: Implementation of Essential Tuple Normalization Form (ETNF) for relational databases (rdbms, sql)</a>
 </td>
@@ -1444,7 +1444,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240217-essential-typle-normalization-form.html" class="filename listing-filename">20240217-essential-typle-normalization-form.md</a>
 </td>
 </tr>
-<tr data-index="110" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="278" data-listing-title-sort="Proposed: Comprehensive Documentation for V-Sekai" data-listing-filename-sort="20240217-documentation-guidelines.md">
+<tr data-index="110" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="278" data-listing-title-sort="Proposed: Comprehensive Documentation for V-Sekai" data-listing-filename-sort="20240217-documentation-guidelines.md">
 <td>
 <a href="./decisions/20240217-documentation-guidelines.html" class="title listing-title">Proposed: Comprehensive Documentation for V-Sekai</a>
 </td>
@@ -1455,7 +1455,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240217-documentation-guidelines.html" class="filename listing-filename">20240217-documentation-guidelines.md</a>
 </td>
 </tr>
-<tr data-index="111" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="301" data-listing-title-sort="Proposed: Container2Wasm Integration in V-Sekai" data-listing-filename-sort="20240217-container-2-wasm.md">
+<tr data-index="111" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="301" data-listing-title-sort="Proposed: Container2Wasm Integration in V-Sekai" data-listing-filename-sort="20240217-container-2-wasm.md">
 <td>
 <a href="./decisions/20240217-container-2-wasm.html" class="title listing-title">Proposed: Container2Wasm Integration in V-Sekai</a>
 </td>
@@ -1466,7 +1466,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240217-container-2-wasm.html" class="filename listing-filename">20240217-container-2-wasm.md</a>
 </td>
 </tr>
-<tr data-index="112" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="298" data-listing-title-sort="Proposed: Enhancing Avatar Expressiveness with AI-Generated Blend Shapes" data-listing-filename-sort="20240215-avatar-customization-with-ai-facial-expressions.md">
+<tr data-index="112" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="298" data-listing-title-sort="Proposed: Enhancing Avatar Expressiveness with AI-Generated Blend Shapes" data-listing-filename-sort="20240215-avatar-customization-with-ai-facial-expressions.md">
 <td>
 <a href="./decisions/20240215-avatar-customization-with-ai-facial-expressions.html" class="title listing-title">Proposed: Enhancing Avatar Expressiveness with AI-Generated Blend Shapes</a>
 </td>
@@ -1477,7 +1477,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240215-avatar-customization-with-ai-facial-expressions.html" class="filename listing-filename">20240215-avatar-customization-with-ai-facial-expressions.md</a>
 </td>
 </tr>
-<tr data-index="113" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="328" data-listing-title-sort="Proposed: Urban Navigator: The City Unveiled" data-listing-filename-sort="20240127-urban-explorer-gdc-2024-sample.md">
+<tr data-index="113" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="328" data-listing-title-sort="Proposed: Urban Navigator: The City Unveiled" data-listing-filename-sort="20240127-urban-explorer-gdc-2024-sample.md">
 <td>
 <a href="./decisions/20240127-urban-explorer-gdc-2024-sample.html" class="title listing-title">Proposed: Urban Navigator: The City Unveiled</a>
 </td>
@@ -1488,7 +1488,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240127-urban-explorer-gdc-2024-sample.html" class="filename listing-filename">20240127-urban-explorer-gdc-2024-sample.md</a>
 </td>
 </tr>
-<tr data-index="114" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="4" data-listing-word-count-sort="663" data-listing-title-sort="Proposed: Macos cicd setup." data-listing-filename-sort="20240121-mac-setup.md">
+<tr data-index="114" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="4" data-listing-word-count-sort="663" data-listing-title-sort="Proposed: Macos cicd setup." data-listing-filename-sort="20240121-mac-setup.md">
 <td>
 <a href="./decisions/20240121-mac-setup.html" class="title listing-title">Proposed: Macos cicd setup.</a>
 </td>
@@ -1499,7 +1499,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240121-mac-setup.html" class="filename listing-filename">20240121-mac-setup.md</a>
 </td>
 </tr>
-<tr data-index="115" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="3" data-listing-word-count-sort="519" data-listing-title-sort="Proposed: Elixir Livebook on Fedora 39" data-listing-filename-sort="20240121-livebook-fedora-install.md">
+<tr data-index="115" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="3" data-listing-word-count-sort="519" data-listing-title-sort="Proposed: Elixir Livebook on Fedora 39" data-listing-filename-sort="20240121-livebook-fedora-install.md">
 <td>
 <a href="./decisions/20240121-livebook-fedora-install.html" class="title listing-title">Proposed: Elixir Livebook on Fedora 39</a>
 </td>
@@ -1510,7 +1510,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240121-livebook-fedora-install.html" class="filename listing-filename">20240121-livebook-fedora-install.md</a>
 </td>
 </tr>
-<tr data-index="116" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="326" data-listing-title-sort="Proposed: Installing Tailscale on Linux Fedora 39" data-listing-filename-sort="20240121-install-tailscale.md">
+<tr data-index="116" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="326" data-listing-title-sort="Proposed: Installing Tailscale on Linux Fedora 39" data-listing-filename-sort="20240121-install-tailscale.md">
 <td>
 <a href="./decisions/20240121-install-tailscale.html" class="title listing-title">Proposed: Installing Tailscale on Linux Fedora 39</a>
 </td>
@@ -1521,7 +1521,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240121-install-tailscale.html" class="filename listing-filename">20240121-install-tailscale.md</a>
 </td>
 </tr>
-<tr data-index="117" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="390" data-listing-title-sort="Proposed: Easy Diffusion AI Setup on Linux Systems" data-listing-filename-sort="20240121-easy-diffusion-fedora-install.md">
+<tr data-index="117" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="390" data-listing-title-sort="Proposed: Easy Diffusion AI Setup on Linux Systems" data-listing-filename-sort="20240121-easy-diffusion-fedora-install.md">
 <td>
 <a href="./decisions/20240121-easy-diffusion-fedora-install.html" class="title listing-title">Proposed: Easy Diffusion AI Setup on Linux Systems</a>
 </td>
@@ -1532,7 +1532,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240121-easy-diffusion-fedora-install.html" class="filename listing-filename">20240121-easy-diffusion-fedora-install.md</a>
 </td>
 </tr>
-<tr data-index="118" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="361" data-listing-title-sort="Proposed: Advanced VR Armature System for V-Sekai" data-listing-filename-sort="20240120-vr-armature-system.md">
+<tr data-index="118" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="361" data-listing-title-sort="Proposed: Advanced VR Armature System for V-Sekai" data-listing-filename-sort="20240120-vr-armature-system.md">
 <td>
 <a href="./decisions/20240120-vr-armature-system.html" class="title listing-title">Proposed: Advanced VR Armature System for V-Sekai</a>
 </td>
@@ -1543,7 +1543,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240120-vr-armature-system.html" class="filename listing-filename">20240120-vr-armature-system.md</a>
 </td>
 </tr>
-<tr data-index="119" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="1" data-listing-word-count-sort="146" data-listing-title-sort="Proposed: Provide Pivot Painting Resources" data-listing-filename-sort="20240117-pivot-painting.md">
+<tr data-index="119" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="1" data-listing-word-count-sort="146" data-listing-title-sort="Proposed: Provide Pivot Painting Resources" data-listing-filename-sort="20240117-pivot-painting.md">
 <td>
 <a href="./decisions/20240117-pivot-painting.html" class="title listing-title">Proposed: Provide Pivot Painting Resources</a>
 </td>
@@ -1554,7 +1554,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240117-pivot-painting.html" class="filename listing-filename">20240117-pivot-painting.md</a>
 </td>
 </tr>
-<tr data-index="120" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="328" data-listing-title-sort="Proposed: Camera matching with fSpy." data-listing-filename-sort="20240111-fspy.md">
+<tr data-index="120" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="328" data-listing-title-sort="Proposed: Camera matching with fSpy." data-listing-filename-sort="20240111-fspy.md">
 <td>
 <a href="./decisions/20240111-fspy.html" class="title listing-title">Proposed: Camera matching with fSpy.</a>
 </td>
@@ -1565,7 +1565,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240111-fspy.html" class="filename listing-filename">20240111-fspy.md</a>
 </td>
 </tr>
-<tr data-index="121" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="356" data-listing-title-sort="Draft: Fit Clothing on Humans Without Tearing" data-listing-filename-sort="20240111-fit-clothing-on-humans-without-tearing.md">
+<tr data-index="121" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="356" data-listing-title-sort="Draft: Fit Clothing on Humans Without Tearing" data-listing-filename-sort="20240111-fit-clothing-on-humans-without-tearing.md">
 <td>
 <a href="./decisions/20240111-fit-clothing-on-humans-without-tearing.html" class="title listing-title">Draft: Fit Clothing on Humans Without Tearing</a>
 </td>
@@ -1576,7 +1576,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240111-fit-clothing-on-humans-without-tearing.html" class="filename listing-filename">20240111-fit-clothing-on-humans-without-tearing.md</a>
 </td>
 </tr>
-<tr data-index="122" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="3" data-listing-word-count-sort="554" data-listing-title-sort="Proposed: Magical Girls College Manager Simulator" data-listing-filename-sort="20240110-magical-girls-college-novel.md">
+<tr data-index="122" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="3" data-listing-word-count-sort="554" data-listing-title-sort="Proposed: Magical Girls College Manager Simulator" data-listing-filename-sort="20240110-magical-girls-college-novel.md">
 <td>
 <a href="./decisions/20240110-magical-girls-college-novel.html" class="title listing-title">Proposed: Magical Girls College Manager Simulator</a>
 </td>
@@ -1587,7 +1587,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240110-magical-girls-college-novel.html" class="filename listing-filename">20240110-magical-girls-college-novel.md</a>
 </td>
 </tr>
-<tr data-index="123" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="351" data-listing-title-sort="Proposed: 1 Meter Cubed 128 Quantized" data-listing-filename-sort="20240105-1-meter-128-quantize.md">
+<tr data-index="123" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="351" data-listing-title-sort="Proposed: 1 Meter Cubed 128 Quantized" data-listing-filename-sort="20240105-1-meter-128-quantize.md">
 <td>
 <a href="./decisions/20240105-1-meter-128-quantize.html" class="title listing-title">Proposed: 1 Meter Cubed 128 Quantized</a>
 </td>
@@ -1598,7 +1598,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20240105-1-meter-128-quantize.html" class="filename listing-filename">20240105-1-meter-128-quantize.md</a>
 </td>
 </tr>
-<tr data-index="124" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="219" data-listing-title-sort="Deprecated: Valid configuration of Spatiallabs and Openxr" data-listing-filename-sort="20231230-spatiallabs-openvr.md">
+<tr data-index="124" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="219" data-listing-title-sort="Deprecated: Valid configuration of Spatiallabs and Openxr" data-listing-filename-sort="20231230-spatiallabs-openvr.md">
 <td>
 <a href="./decisions/20231230-spatiallabs-openvr.html" class="title listing-title">Deprecated: Valid configuration of Spatiallabs and Openxr</a>
 </td>
@@ -1609,7 +1609,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231230-spatiallabs-openvr.html" class="filename listing-filename">20231230-spatiallabs-openvr.md</a>
 </td>
 </tr>
-<tr data-index="125" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="320" data-listing-title-sort="Proposed: Choosing a terminal emulator for Windows" data-listing-filename-sort="20231229-mRemoteNG.md">
+<tr data-index="125" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="320" data-listing-title-sort="Proposed: Choosing a terminal emulator for Windows" data-listing-filename-sort="20231229-mRemoteNG.md">
 <td>
 <a href="./decisions/20231229-mRemoteNG.html" class="title listing-title">Proposed: Choosing a terminal emulator for Windows</a>
 </td>
@@ -1620,7 +1620,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231229-mRemoteNG.html" class="filename listing-filename">20231229-mRemoteNG.md</a>
 </td>
 </tr>
-<tr data-index="126" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="271" data-listing-title-sort="Proposed: Byobu terminal multiplexer" data-listing-filename-sort="20231229-byobu.md">
+<tr data-index="126" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="271" data-listing-title-sort="Proposed: Byobu terminal multiplexer" data-listing-filename-sort="20231229-byobu.md">
 <td>
 <a href="./decisions/20231229-byobu.html" class="title listing-title">Proposed: Byobu terminal multiplexer</a>
 </td>
@@ -1631,7 +1631,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231229-byobu.html" class="filename listing-filename">20231229-byobu.md</a>
 </td>
 </tr>
-<tr data-index="127" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="246" data-listing-title-sort="Proposed: V-Sekai: Gateways to Virtual Worlds" data-listing-filename-sort="20231228-v-sekai-slogan.md">
+<tr data-index="127" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="246" data-listing-title-sort="Proposed: V-Sekai: Gateways to Virtual Worlds" data-listing-filename-sort="20231228-v-sekai-slogan.md">
 <td>
 <a href="./decisions/20231228-v-sekai-slogan.html" class="title listing-title">Proposed: V-Sekai: Gateways to Virtual Worlds</a>
 </td>
@@ -1642,7 +1642,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231228-v-sekai-slogan.html" class="filename listing-filename">20231228-v-sekai-slogan.md</a>
 </td>
 </tr>
-<tr data-index="128" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="260" data-listing-title-sort="Proposed: Use the &quot;Punchline Reports&quot; Method" data-listing-filename-sort="20231227-punchline-reports.md">
+<tr data-index="128" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="260" data-listing-title-sort="Proposed: Use the &quot;Punchline Reports&quot; Method" data-listing-filename-sort="20231227-punchline-reports.md">
 <td>
 <a href="./decisions/20231227-punchline-reports.html" class="title listing-title">Proposed: Use the “Punchline Reports” Method</a>
 </td>
@@ -1653,7 +1653,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231227-punchline-reports.html" class="filename listing-filename">20231227-punchline-reports.md</a>
 </td>
 </tr>
-<tr data-index="129" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="338" data-listing-title-sort="Proposed: Blue Green new shadows for new avatars" data-listing-filename-sort="20231227-blue-green-shadows.md">
+<tr data-index="129" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="338" data-listing-title-sort="Proposed: Blue Green new shadows for new avatars" data-listing-filename-sort="20231227-blue-green-shadows.md">
 <td>
 <a href="./decisions/20231227-blue-green-shadows.html" class="title listing-title">Proposed: Blue Green new shadows for new avatars</a>
 </td>
@@ -1664,7 +1664,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231227-blue-green-shadows.html" class="filename listing-filename">20231227-blue-green-shadows.md</a>
 </td>
 </tr>
-<tr data-index="130" data-listing-file-modified-sort="1730535490038" data-listing-reading-time-sort="2" data-listing-word-count-sort="272" data-listing-title-sort="Proposed: Hardsurface vs Organic" data-listing-filename-sort="20231226-furniture-vs-organic.md">
+<tr data-index="130" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="272" data-listing-title-sort="Proposed: Hardsurface vs Organic" data-listing-filename-sort="20231226-furniture-vs-organic.md">
 <td>
 <a href="./decisions/20231226-furniture-vs-organic.html" class="title listing-title">Proposed: Hardsurface vs Organic</a>
 </td>
@@ -1675,7 +1675,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231226-furniture-vs-organic.html" class="filename listing-filename">20231226-furniture-vs-organic.md</a>
 </td>
 </tr>
-<tr data-index="131" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="311" data-listing-title-sort="Proposed: Mesh Transformer Expressive Facial Features" data-listing-filename-sort="20231225-mesh-transformer-facial-features.md">
+<tr data-index="131" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="311" data-listing-title-sort="Proposed: Mesh Transformer Expressive Facial Features" data-listing-filename-sort="20231225-mesh-transformer-facial-features.md">
 <td>
 <a href="./decisions/20231225-mesh-transformer-facial-features.html" class="title listing-title">Proposed: Mesh Transformer Expressive Facial Features</a>
 </td>
@@ -1686,7 +1686,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231225-mesh-transformer-facial-features.html" class="filename listing-filename">20231225-mesh-transformer-facial-features.md</a>
 </td>
 </tr>
-<tr data-index="132" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="307" data-listing-title-sort="Proposed: Mesh Transformer Clothing" data-listing-filename-sort="20231225-mesh-transformer-clothing.md">
+<tr data-index="132" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="307" data-listing-title-sort="Proposed: Mesh Transformer Clothing" data-listing-filename-sort="20231225-mesh-transformer-clothing.md">
 <td>
 <a href="./decisions/20231225-mesh-transformer-clothing.html" class="title listing-title">Proposed: Mesh Transformer Clothing</a>
 </td>
@@ -1697,7 +1697,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231225-mesh-transformer-clothing.html" class="filename listing-filename">20231225-mesh-transformer-clothing.md</a>
 </td>
 </tr>
-<tr data-index="133" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="287" data-listing-title-sort="Proposed: MaterialX try two." data-listing-filename-sort="20231218-mtlx-try-two.md">
+<tr data-index="133" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="287" data-listing-title-sort="Proposed: MaterialX try two." data-listing-filename-sort="20231218-mtlx-try-two.md">
 <td>
 <a href="./decisions/20231218-mtlx-try-two.html" class="title listing-title">Proposed: MaterialX try two.</a>
 </td>
@@ -1708,7 +1708,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231218-mtlx-try-two.html" class="filename listing-filename">20231218-mtlx-try-two.md</a>
 </td>
 </tr>
-<tr data-index="134" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="3" data-listing-word-count-sort="408" data-listing-title-sort="Proposed: Automating Game Testing Process Using Appium 2" data-listing-filename-sort="20231209-appium-testing-win11.md">
+<tr data-index="134" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="3" data-listing-word-count-sort="408" data-listing-title-sort="Proposed: Automating Game Testing Process Using Appium 2" data-listing-filename-sort="20231209-appium-testing-win11.md">
 <td>
 <a href="./decisions/20231209-appium-testing-win11.html" class="title listing-title">Proposed: Automating Game Testing Process Using Appium 2</a>
 </td>
@@ -1719,7 +1719,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231209-appium-testing-win11.html" class="filename listing-filename">20231209-appium-testing-win11.md</a>
 </td>
 </tr>
-<tr data-index="135" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="242" data-listing-title-sort="Proposed: Appium Testing for Windows 11" data-listing-filename-sort="20231209-appium-testing-fbx-to-gltf.md">
+<tr data-index="135" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="242" data-listing-title-sort="Proposed: Appium Testing for Windows 11" data-listing-filename-sort="20231209-appium-testing-fbx-to-gltf.md">
 <td>
 <a href="./decisions/20231209-appium-testing-fbx-to-gltf.html" class="title listing-title">Proposed: Appium Testing for Windows 11</a>
 </td>
@@ -1730,7 +1730,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231209-appium-testing-fbx-to-gltf.html" class="filename listing-filename">20231209-appium-testing-fbx-to-gltf.md</a>
 </td>
 </tr>
-<tr data-index="136" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="5" data-listing-word-count-sort="838" data-listing-title-sort="Proposed: Triangle Meshes Inferencing with MeshRWKV" data-listing-filename-sort="20231203-mesh-rwkv.md">
+<tr data-index="136" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="5" data-listing-word-count-sort="838" data-listing-title-sort="Proposed: Triangle Meshes Inferencing with MeshRWKV" data-listing-filename-sort="20231203-mesh-rwkv.md">
 <td>
 <a href="./decisions/20231203-mesh-rwkv.html" class="title listing-title">Proposed: Triangle Meshes Inferencing with MeshRWKV</a>
 </td>
@@ -1741,7 +1741,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231203-mesh-rwkv.html" class="filename listing-filename">20231203-mesh-rwkv.md</a>
 </td>
 </tr>
-<tr data-index="137" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="302" data-listing-title-sort="Draft: Initial Training of the MeshRWVK Model" data-listing-filename-sort="20231203-mesh-rwkv-test-metrics.md">
+<tr data-index="137" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="302" data-listing-title-sort="Draft: Initial Training of the MeshRWVK Model" data-listing-filename-sort="20231203-mesh-rwkv-test-metrics.md">
 <td>
 <a href="./decisions/20231203-mesh-rwkv-test-metrics.html" class="title listing-title">Draft: Initial Training of the MeshRWVK Model</a>
 </td>
@@ -1752,7 +1752,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231203-mesh-rwkv-test-metrics.html" class="filename listing-filename">20231203-mesh-rwkv-test-metrics.md</a>
 </td>
 </tr>
-<tr data-index="138" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="4" data-listing-word-count-sort="768" data-listing-title-sort="Draft: GraphSAGE Embedding Algorithm Explanation" data-listing-filename-sort="20231203-graphsage-embedding-generation.md">
+<tr data-index="138" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="4" data-listing-word-count-sort="768" data-listing-title-sort="Draft: GraphSAGE Embedding Algorithm Explanation" data-listing-filename-sort="20231203-graphsage-embedding-generation.md">
 <td>
 <a href="./decisions/20231203-graphsage-embedding-generation.html" class="title listing-title">Draft: GraphSAGE Embedding Algorithm Explanation</a>
 </td>
@@ -1763,7 +1763,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231203-graphsage-embedding-generation.html" class="filename listing-filename">20231203-graphsage-embedding-generation.md</a>
 </td>
 </tr>
-<tr data-index="139" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="3" data-listing-word-count-sort="509" data-listing-title-sort="Proposed: Seamless Integration of XR Tracking in Godot Engine" data-listing-filename-sort="20231201-xr-hands-animation-node.md">
+<tr data-index="139" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="3" data-listing-word-count-sort="509" data-listing-title-sort="Proposed: Seamless Integration of XR Tracking in Godot Engine" data-listing-filename-sort="20231201-xr-hands-animation-node.md">
 <td>
 <a href="./decisions/20231201-xr-hands-animation-node.html" class="title listing-title">Proposed: Seamless Integration of XR Tracking in Godot Engine</a>
 </td>
@@ -1774,7 +1774,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231201-xr-hands-animation-node.html" class="filename listing-filename">20231201-xr-hands-animation-node.md</a>
 </td>
 </tr>
-<tr data-index="140" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="7" data-listing-word-count-sort="1372" data-listing-title-sort="Proposed: Headless Launcher Backend with Elixir and Server-Side CockroachDB" data-listing-filename-sort="20231201-headless-launcher-backend.md">
+<tr data-index="140" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="7" data-listing-word-count-sort="1372" data-listing-title-sort="Proposed: Headless Launcher Backend with Elixir and Server-Side CockroachDB" data-listing-filename-sort="20231201-headless-launcher-backend.md">
 <td>
 <a href="./decisions/20231201-headless-launcher-backend.html" class="title listing-title">Proposed: Headless Launcher Backend with Elixir and Server-Side CockroachDB</a>
 </td>
@@ -1785,7 +1785,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231201-headless-launcher-backend.html" class="filename listing-filename">20231201-headless-launcher-backend.md</a>
 </td>
 </tr>
-<tr data-index="141" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="3" data-listing-word-count-sort="434" data-listing-title-sort="Accepted: Benchmarking Network Performance for Scalable Multiplayer in Godot" data-listing-filename-sort="20231127-performance-test.md">
+<tr data-index="141" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="3" data-listing-word-count-sort="434" data-listing-title-sort="Accepted: Benchmarking Network Performance for Scalable Multiplayer in Godot" data-listing-filename-sort="20231127-performance-test.md">
 <td>
 <a href="./decisions/20231127-performance-test.html" class="title listing-title">Accepted: Benchmarking Network Performance for Scalable Multiplayer in Godot</a>
 </td>
@@ -1796,7 +1796,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231127-performance-test.html" class="filename listing-filename">20231127-performance-test.md</a>
 </td>
 </tr>
-<tr data-index="142" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="3" data-listing-word-count-sort="422" data-listing-title-sort="Accepted: V-Sekai 2023-11-26 Report" data-listing-filename-sort="20231126-v-sekai-report.md">
+<tr data-index="142" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="3" data-listing-word-count-sort="422" data-listing-title-sort="Accepted: V-Sekai 2023-11-26 Report" data-listing-filename-sort="20231126-v-sekai-report.md">
 <td>
 <a href="./decisions/20231126-v-sekai-report.html" class="title listing-title">Accepted: V-Sekai 2023-11-26 Report</a>
 </td>
@@ -1807,7 +1807,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231126-v-sekai-report.html" class="filename listing-filename">20231126-v-sekai-report.md</a>
 </td>
 </tr>
-<tr data-index="143" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="4" data-listing-word-count-sort="680" data-listing-title-sort="Superseded: V-Sekai 2023-11-25 Report" data-listing-filename-sort="20231125-v-sekai-report.md">
+<tr data-index="143" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="4" data-listing-word-count-sort="680" data-listing-title-sort="Superseded: V-Sekai 2023-11-25 Report" data-listing-filename-sort="20231125-v-sekai-report.md">
 <td>
 <a href="./decisions/20231125-v-sekai-report.html" class="title listing-title">Superseded: V-Sekai 2023-11-25 Report</a>
 </td>
@@ -1818,7 +1818,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231125-v-sekai-report.html" class="filename listing-filename">20231125-v-sekai-report.md</a>
 </td>
 </tr>
-<tr data-index="144" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="319" data-listing-title-sort="Proposed: Upload Creative Commons FBX Test Files for Enhanced LOD Optimization in V-Sekai" data-listing-filename-sort="20231114-upload-creative-commons-fbx-test-files.md">
+<tr data-index="144" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="319" data-listing-title-sort="Proposed: Upload Creative Commons FBX Test Files for Enhanced LOD Optimization in V-Sekai" data-listing-filename-sort="20231114-upload-creative-commons-fbx-test-files.md">
 <td>
 <a href="./decisions/20231114-upload-creative-commons-fbx-test-files.html" class="title listing-title">Proposed: Upload Creative Commons FBX Test Files for Enhanced LOD Optimization in V-Sekai</a>
 </td>
@@ -1829,7 +1829,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231114-upload-creative-commons-fbx-test-files.html" class="filename listing-filename">20231114-upload-creative-commons-fbx-test-files.md</a>
 </td>
 </tr>
-<tr data-index="145" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="283" data-listing-title-sort="Proposed: Enhancing VR Book Reading through SVG Optimization" data-listing-filename-sort="20231114-maintain-svgcleaner.md">
+<tr data-index="145" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="283" data-listing-title-sort="Proposed: Enhancing VR Book Reading through SVG Optimization" data-listing-filename-sort="20231114-maintain-svgcleaner.md">
 <td>
 <a href="./decisions/20231114-maintain-svgcleaner.html" class="title listing-title">Proposed: Enhancing VR Book Reading through SVG Optimization</a>
 </td>
@@ -1840,7 +1840,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231114-maintain-svgcleaner.html" class="filename listing-filename">20231114-maintain-svgcleaner.md</a>
 </td>
 </tr>
-<tr data-index="146" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="350" data-listing-title-sort="Proposed: Defining the List of Godot Types in Elixir Godot Parsers" data-listing-filename-sort="20231114-elixir-definition-of-godot-types.md">
+<tr data-index="146" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="350" data-listing-title-sort="Proposed: Defining the List of Godot Types in Elixir Godot Parsers" data-listing-filename-sort="20231114-elixir-definition-of-godot-types.md">
 <td>
 <a href="./decisions/20231114-elixir-definition-of-godot-types.html" class="title listing-title">Proposed: Defining the List of Godot Types in Elixir Godot Parsers</a>
 </td>
@@ -1851,7 +1851,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231114-elixir-definition-of-godot-types.html" class="filename listing-filename">20231114-elixir-definition-of-godot-types.md</a>
 </td>
 </tr>
-<tr data-index="147" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="357" data-listing-title-sort="Proposed: Validator Service for V-Sekai" data-listing-filename-sort="20231112-validation-service.md">
+<tr data-index="147" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="357" data-listing-title-sort="Proposed: Validator Service for V-Sekai" data-listing-filename-sort="20231112-validation-service.md">
 <td>
 <a href="./decisions/20231112-validation-service.html" class="title listing-title">Proposed: Validator Service for V-Sekai</a>
 </td>
@@ -1862,7 +1862,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231112-validation-service.html" class="filename listing-filename">20231112-validation-service.md</a>
 </td>
 </tr>
-<tr data-index="148" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="3" data-listing-word-count-sort="527" data-listing-title-sort="Proposed: Effective V-Sekai project archival strategy" data-listing-filename-sort="20231112-archive-projects.md">
+<tr data-index="148" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="3" data-listing-word-count-sort="527" data-listing-title-sort="Proposed: Effective V-Sekai project archival strategy" data-listing-filename-sort="20231112-archive-projects.md">
 <td>
 <a href="./decisions/20231112-archive-projects.html" class="title listing-title">Proposed: Effective V-Sekai project archival strategy</a>
 </td>
@@ -1873,7 +1873,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231112-archive-projects.html" class="filename listing-filename">20231112-archive-projects.md</a>
 </td>
 </tr>
-<tr data-index="149" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="3" data-listing-word-count-sort="586" data-listing-title-sort="Proposed: Evaluate AYON pipeline platform on hosted cloud services" data-listing-filename-sort="20231111-ayon-evaluation.md">
+<tr data-index="149" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="3" data-listing-word-count-sort="586" data-listing-title-sort="Proposed: Evaluate AYON pipeline platform on hosted cloud services" data-listing-filename-sort="20231111-ayon-evaluation.md">
 <td>
 <a href="./decisions/20231111-ayon-evaluation.html" class="title listing-title">Proposed: Evaluate AYON pipeline platform on hosted cloud services</a>
 </td>
@@ -1884,7 +1884,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231111-ayon-evaluation.html" class="filename listing-filename">20231111-ayon-evaluation.md</a>
 </td>
 </tr>
-<tr data-index="150" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="3" data-listing-word-count-sort="416" data-listing-title-sort="Accepted: V-Sekai dependencies" data-listing-filename-sort="20231110-v-sekai-dependencies.md">
+<tr data-index="150" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="3" data-listing-word-count-sort="416" data-listing-title-sort="Accepted: V-Sekai dependencies" data-listing-filename-sort="20231110-v-sekai-dependencies.md">
 <td>
 <a href="./decisions/20231110-v-sekai-dependencies.html" class="title listing-title">Accepted: V-Sekai dependencies</a>
 </td>
@@ -1895,7 +1895,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231110-v-sekai-dependencies.html" class="filename listing-filename">20231110-v-sekai-dependencies.md</a>
 </td>
 </tr>
-<tr data-index="151" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="247" data-listing-title-sort="Proposed: Efficient Training of LLMs in V-Sekai" data-listing-filename-sort="20231110-efficient-llm-training.md">
+<tr data-index="151" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="247" data-listing-title-sort="Proposed: Efficient Training of LLMs in V-Sekai" data-listing-filename-sort="20231110-efficient-llm-training.md">
 <td>
 <a href="./decisions/20231110-efficient-llm-training.html" class="title listing-title">Proposed: Efficient Training of LLMs in V-Sekai</a>
 </td>
@@ -1906,7 +1906,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231110-efficient-llm-training.html" class="filename listing-filename">20231110-efficient-llm-training.md</a>
 </td>
 </tr>
-<tr data-index="152" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="265" data-listing-title-sort="Accepted: Overcoming the Blender T-Pose Limitation with Documentation" data-listing-filename-sort="20231110-blender-manual-t-pose.md">
+<tr data-index="152" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="265" data-listing-title-sort="Accepted: Overcoming the Blender T-Pose Limitation with Documentation" data-listing-filename-sort="20231110-blender-manual-t-pose.md">
 <td>
 <a href="./decisions/20231110-blender-manual-t-pose.html" class="title listing-title">Accepted: Overcoming the Blender T-Pose Limitation with Documentation</a>
 </td>
@@ -1917,7 +1917,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231110-blender-manual-t-pose.html" class="filename listing-filename">20231110-blender-manual-t-pose.md</a>
 </td>
 </tr>
-<tr data-index="153" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="328" data-listing-title-sort="Proposed: Enhancing V-Sekai x Godot Engine x AYON for a Superior Workflow" data-listing-filename-sort="20231110-better-pipeline-tools.md">
+<tr data-index="153" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="328" data-listing-title-sort="Proposed: Enhancing V-Sekai x Godot Engine x AYON for a Superior Workflow" data-listing-filename-sort="20231110-better-pipeline-tools.md">
 <td>
 <a href="./decisions/20231110-better-pipeline-tools.html" class="title listing-title">Proposed: Enhancing V-Sekai x Godot Engine x AYON for a Superior Workflow</a>
 </td>
@@ -1928,7 +1928,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231110-better-pipeline-tools.html" class="filename listing-filename">20231110-better-pipeline-tools.md</a>
 </td>
 </tr>
-<tr data-index="154" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="332" data-listing-title-sort="Proposed: Streamlining Game Development with AI-Based Aria's Guidance" data-listing-filename-sort="20231110-ai-based-outlier-detection.md">
+<tr data-index="154" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="332" data-listing-title-sort="Proposed: Streamlining Game Development with AI-Based Aria's Guidance" data-listing-filename-sort="20231110-ai-based-outlier-detection.md">
 <td>
 <a href="./decisions/20231110-ai-based-outlier-detection.html" class="title listing-title">Proposed: Streamlining Game Development with AI-Based Aria’s Guidance</a>
 </td>
@@ -1939,7 +1939,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231110-ai-based-outlier-detection.html" class="filename listing-filename">20231110-ai-based-outlier-detection.md</a>
 </td>
 </tr>
-<tr data-index="155" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="4" data-listing-word-count-sort="640" data-listing-title-sort="Proposed: Character Customization Discord Bot PoC for V-Sekai" data-listing-filename-sort="20231109-discord-polygonjs-generator.md">
+<tr data-index="155" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="4" data-listing-word-count-sort="640" data-listing-title-sort="Proposed: Character Customization Discord Bot PoC for V-Sekai" data-listing-filename-sort="20231109-discord-polygonjs-generator.md">
 <td>
 <a href="./decisions/20231109-discord-polygonjs-generator.html" class="title listing-title">Proposed: Character Customization Discord Bot PoC for V-Sekai</a>
 </td>
@@ -1950,7 +1950,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231109-discord-polygonjs-generator.html" class="filename listing-filename">20231109-discord-polygonjs-generator.md</a>
 </td>
 </tr>
-<tr data-index="156" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="277" data-listing-title-sort="Proposed: Creation of an 'Ask V-Sekai' Chatbot Using Vercel, OpenAI, and Neon PostgreSQL" data-listing-filename-sort="20231108-v-sekai-chat-bot.md">
+<tr data-index="156" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="277" data-listing-title-sort="Proposed: Creation of an 'Ask V-Sekai' Chatbot Using Vercel, OpenAI, and Neon PostgreSQL" data-listing-filename-sort="20231108-v-sekai-chat-bot.md">
 <td>
 <a href="./decisions/20231108-v-sekai-chat-bot.html" class="title listing-title">Proposed: Creation of an ‘Ask V-Sekai’ Chatbot Using Vercel, OpenAI, and Neon PostgreSQL</a>
 </td>
@@ -1961,7 +1961,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231108-v-sekai-chat-bot.html" class="filename listing-filename">20231108-v-sekai-chat-bot.md</a>
 </td>
 </tr>
-<tr data-index="157" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="211" data-listing-title-sort="Proposed: PostgreSQL `bytea` Storage Optimization for V-Sekai's Edge CDN" data-listing-filename-sort="20231108-postgres-bytea-optimizations.md">
+<tr data-index="157" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="211" data-listing-title-sort="Proposed: PostgreSQL `bytea` Storage Optimization for V-Sekai's Edge CDN" data-listing-filename-sort="20231108-postgres-bytea-optimizations.md">
 <td>
 <a href="./decisions/20231108-postgres-bytea-optimizations.html" class="title listing-title">Proposed: PostgreSQL <code>bytea</code> Storage Optimization for V-Sekai’s Edge CDN</a>
 </td>
@@ -1972,7 +1972,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231108-postgres-bytea-optimizations.html" class="filename listing-filename">20231108-postgres-bytea-optimizations.md</a>
 </td>
 </tr>
-<tr data-index="158" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="3" data-listing-word-count-sort="411" data-listing-title-sort="Proposed: &quot;Freedom is in a future that you did not have in the past&quot; - A Game Development Philosophy from NieR:Automata" data-listing-filename-sort="20231108-nier-automata-world-expansion.md">
+<tr data-index="158" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="3" data-listing-word-count-sort="411" data-listing-title-sort="Proposed: &quot;Freedom is in a future that you did not have in the past&quot; - A Game Development Philosophy from NieR:Automata" data-listing-filename-sort="20231108-nier-automata-world-expansion.md">
 <td>
 <a href="./decisions/20231108-nier-automata-world-expansion.html" class="title listing-title">Proposed: “Freedom is in a future that you did not have in the past” - A Game Development Philosophy from NieR:Automata</a>
 </td>
@@ -1983,7 +1983,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231108-nier-automata-world-expansion.html" class="filename listing-filename">20231108-nier-automata-world-expansion.md</a>
 </td>
 </tr>
-<tr data-index="159" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="287" data-listing-title-sort="Proposed: Development of a Community Polling Discord Bot Using Vercel and Neon PostgreSQL" data-listing-filename-sort="20231108-neon-vercel-functions-toy-problem.md">
+<tr data-index="159" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="287" data-listing-title-sort="Proposed: Development of a Community Polling Discord Bot Using Vercel and Neon PostgreSQL" data-listing-filename-sort="20231108-neon-vercel-functions-toy-problem.md">
 <td>
 <a href="./decisions/20231108-neon-vercel-functions-toy-problem.html" class="title listing-title">Proposed: Development of a Community Polling Discord Bot Using Vercel and Neon PostgreSQL</a>
 </td>
@@ -1994,7 +1994,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231108-neon-vercel-functions-toy-problem.html" class="filename listing-filename">20231108-neon-vercel-functions-toy-problem.md</a>
 </td>
 </tr>
-<tr data-index="160" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="1" data-listing-word-count-sort="192" data-listing-title-sort="Proposed: Adopting Neon for a More Manageable Backend at V-Sekai" data-listing-filename-sort="20231108-neon-postgresql.md">
+<tr data-index="160" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="1" data-listing-word-count-sort="192" data-listing-title-sort="Proposed: Adopting Neon for a More Manageable Backend at V-Sekai" data-listing-filename-sort="20231108-neon-postgresql.md">
 <td>
 <a href="./decisions/20231108-neon-postgresql.html" class="title listing-title">Proposed: Adopting Neon for a More Manageable Backend at V-Sekai</a>
 </td>
@@ -2005,7 +2005,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231108-neon-postgresql.html" class="filename listing-filename">20231108-neon-postgresql.md</a>
 </td>
 </tr>
-<tr data-index="161" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="262" data-listing-title-sort="Proposed: Adopting Neon's Bottomless Storage with S3-Compatible Object Store for Edge CDN Data Management" data-listing-filename-sort="20231108-neon-1-gb-scene-storage.md">
+<tr data-index="161" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="262" data-listing-title-sort="Proposed: Adopting Neon's Bottomless Storage with S3-Compatible Object Store for Edge CDN Data Management" data-listing-filename-sort="20231108-neon-1-gb-scene-storage.md">
 <td>
 <a href="./decisions/20231108-neon-1-gb-scene-storage.html" class="title listing-title">Proposed: Adopting Neon’s Bottomless Storage with S3-Compatible Object Store for Edge CDN Data Management</a>
 </td>
@@ -2016,7 +2016,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231108-neon-1-gb-scene-storage.html" class="filename listing-filename">20231108-neon-1-gb-scene-storage.md</a>
 </td>
 </tr>
-<tr data-index="162" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="274" data-listing-title-sort="Proposed: Enhancing V-Sekai Through Effective Documentation" data-listing-filename-sort="20231108-munich-godot-engine-conference.md">
+<tr data-index="162" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="274" data-listing-title-sort="Proposed: Enhancing V-Sekai Through Effective Documentation" data-listing-filename-sort="20231108-munich-godot-engine-conference.md">
 <td>
 <a href="./decisions/20231108-munich-godot-engine-conference.html" class="title listing-title">Proposed: Enhancing V-Sekai Through Effective Documentation</a>
 </td>
@@ -2027,7 +2027,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231108-munich-godot-engine-conference.html" class="filename listing-filename">20231108-munich-godot-engine-conference.md</a>
 </td>
 </tr>
-<tr data-index="163" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="308" data-listing-title-sort="Proposed: Ansible Server Provisioning" data-listing-filename-sort="20231108-ansible-new-server-provisioning.md">
+<tr data-index="163" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="308" data-listing-title-sort="Proposed: Ansible Server Provisioning" data-listing-filename-sort="20231108-ansible-new-server-provisioning.md">
 <td>
 <a href="./decisions/20231108-ansible-new-server-provisioning.html" class="title listing-title">Proposed: Ansible Server Provisioning</a>
 </td>
@@ -2038,7 +2038,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231108-ansible-new-server-provisioning.html" class="filename listing-filename">20231108-ansible-new-server-provisioning.md</a>
 </td>
 </tr>
-<tr data-index="164" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="287" data-listing-title-sort="Proposed: PDF to SVG Conversion for VR Books" data-listing-filename-sort="20231105-pdf-embed-raster-svg-vr.md">
+<tr data-index="164" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="287" data-listing-title-sort="Proposed: PDF to SVG Conversion for VR Books" data-listing-filename-sort="20231105-pdf-embed-raster-svg-vr.md">
 <td>
 <a href="./decisions/20231105-pdf-embed-raster-svg-vr.html" class="title listing-title">Proposed: PDF to SVG Conversion for VR Books</a>
 </td>
@@ -2049,7 +2049,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231105-pdf-embed-raster-svg-vr.html" class="filename listing-filename">20231105-pdf-embed-raster-svg-vr.md</a>
 </td>
 </tr>
-<tr data-index="165" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="390" data-listing-title-sort="Rejected: Merge Scene Tool for Godot Editor with FlatBuffer-based JSON Serialization" data-listing-filename-sort="20231104-flatbuffer_packed_scenes.md">
+<tr data-index="165" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="390" data-listing-title-sort="Rejected: Merge Scene Tool for Godot Editor with FlatBuffer-based JSON Serialization" data-listing-filename-sort="20231104-flatbuffer_packed_scenes.md">
 <td>
 <a href="./decisions/20231104-flatbuffer_packed_scenes.html" class="title listing-title">Rejected: Merge Scene Tool for Godot Editor with FlatBuffer-based JSON Serialization</a>
 </td>
@@ -2060,7 +2060,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231104-flatbuffer_packed_scenes.html" class="filename listing-filename">20231104-flatbuffer_packed_scenes.md</a>
 </td>
 </tr>
-<tr data-index="166" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="6" data-listing-word-count-sort="1092" data-listing-title-sort="Accepted: Write List of Github Pull Requests for Review" data-listing-filename-sort="20231027-write-a-list-of-github-pull-requests.md">
+<tr data-index="166" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="6" data-listing-word-count-sort="1092" data-listing-title-sort="Accepted: Write List of Github Pull Requests for Review" data-listing-filename-sort="20231027-write-a-list-of-github-pull-requests.md">
 <td>
 <a href="./decisions/20231027-write-a-list-of-github-pull-requests.html" class="title listing-title">Accepted: Write List of Github Pull Requests for Review</a>
 </td>
@@ -2071,7 +2071,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231027-write-a-list-of-github-pull-requests.html" class="filename listing-filename">20231027-write-a-list-of-github-pull-requests.md</a>
 </td>
 </tr>
-<tr data-index="167" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="292" data-listing-title-sort="Proposed: DreamCraft3D - A Hierarchical 3D Content Generation Method" data-listing-filename-sort="20231027-dreamcraft3d-workflow.md">
+<tr data-index="167" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="292" data-listing-title-sort="Proposed: DreamCraft3D - A Hierarchical 3D Content Generation Method" data-listing-filename-sort="20231027-dreamcraft3d-workflow.md">
 <td>
 <a href="./decisions/20231027-dreamcraft3d-workflow.html" class="title listing-title">Proposed: DreamCraft3D - A Hierarchical 3D Content Generation Method</a>
 </td>
@@ -2082,7 +2082,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231027-dreamcraft3d-workflow.html" class="filename listing-filename">20231027-dreamcraft3d-workflow.md</a>
 </td>
 </tr>
-<tr data-index="168" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="246" data-listing-title-sort="Proposed: Drawing Concept to Blockout" data-listing-filename-sort="20231027-drawing-concept-to-blockout.md">
+<tr data-index="168" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="246" data-listing-title-sort="Proposed: Drawing Concept to Blockout" data-listing-filename-sort="20231027-drawing-concept-to-blockout.md">
 <td>
 <a href="./decisions/20231027-drawing-concept-to-blockout.html" class="title listing-title">Proposed: Drawing Concept to Blockout</a>
 </td>
@@ -2093,7 +2093,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231027-drawing-concept-to-blockout.html" class="filename listing-filename">20231027-drawing-concept-to-blockout.md</a>
 </td>
 </tr>
-<tr data-index="169" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="325" data-listing-title-sort="Proposed: Build a Cozy Apartment in VR for V-Sekai" data-listing-filename-sort="20231027-apartment-building-vr.md">
+<tr data-index="169" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="325" data-listing-title-sort="Proposed: Build a Cozy Apartment in VR for V-Sekai" data-listing-filename-sort="20231027-apartment-building-vr.md">
 <td>
 <a href="./decisions/20231027-apartment-building-vr.html" class="title listing-title">Proposed: Build a Cozy Apartment in VR for V-Sekai</a>
 </td>
@@ -2104,7 +2104,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231027-apartment-building-vr.html" class="filename listing-filename">20231027-apartment-building-vr.md</a>
 </td>
 </tr>
-<tr data-index="170" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="1" data-listing-word-count-sort="111" data-listing-title-sort="Proposed: Solve Blender versions by locking LTS versions on Blender (3.6)" data-listing-filename-sort="20231026-blender-steam-beta-version.md">
+<tr data-index="170" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="1" data-listing-word-count-sort="111" data-listing-title-sort="Proposed: Solve Blender versions by locking LTS versions on Blender (3.6)" data-listing-filename-sort="20231026-blender-steam-beta-version.md">
 <td>
 <a href="./decisions/20231026-blender-steam-beta-version.html" class="title listing-title">Proposed: Solve Blender versions by locking LTS versions on Blender (3.6)</a>
 </td>
@@ -2115,7 +2115,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231026-blender-steam-beta-version.html" class="filename listing-filename">20231026-blender-steam-beta-version.md</a>
 </td>
 </tr>
-<tr data-index="171" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="290" data-listing-title-sort="Proposed: Implementing Advanced Training Simulators in V-Sekai" data-listing-filename-sort="20231024-training-simulators.md">
+<tr data-index="171" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="290" data-listing-title-sort="Proposed: Implementing Advanced Training Simulators in V-Sekai" data-listing-filename-sort="20231024-training-simulators.md">
 <td>
 <a href="./decisions/20231024-training-simulators.html" class="title listing-title">Proposed: Implementing Advanced Training Simulators in V-Sekai</a>
 </td>
@@ -2126,7 +2126,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231024-training-simulators.html" class="filename listing-filename">20231024-training-simulators.md</a>
 </td>
 </tr>
-<tr data-index="172" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="303" data-listing-title-sort="Proposed: Enhancing Task-Specific Model Performance through Fine-Tuning with Axolotl" data-listing-filename-sort="20231024-finetuning-workflow.md">
+<tr data-index="172" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="303" data-listing-title-sort="Proposed: Enhancing Task-Specific Model Performance through Fine-Tuning with Axolotl" data-listing-filename-sort="20231024-finetuning-workflow.md">
 <td>
 <a href="./decisions/20231024-finetuning-workflow.html" class="title listing-title">Proposed: Enhancing Task-Specific Model Performance through Fine-Tuning with Axolotl</a>
 </td>
@@ -2137,7 +2137,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231024-finetuning-workflow.html" class="filename listing-filename">20231024-finetuning-workflow.md</a>
 </td>
 </tr>
-<tr data-index="173" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="274" data-listing-title-sort="Proposed: Navigating New Horizons: A Proposal for Expanding Exploration in V-Sekai" data-listing-filename-sort="20231022-hover-to-ocean-game.md">
+<tr data-index="173" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="274" data-listing-title-sort="Proposed: Navigating New Horizons: A Proposal for Expanding Exploration in V-Sekai" data-listing-filename-sort="20231022-hover-to-ocean-game.md">
 <td>
 <a href="./decisions/20231022-hover-to-ocean-game.html" class="title listing-title">Proposed: Navigating New Horizons: A Proposal for Expanding Exploration in V-Sekai</a>
 </td>
@@ -2148,7 +2148,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231022-hover-to-ocean-game.html" class="filename listing-filename">20231022-hover-to-ocean-game.md</a>
 </td>
 </tr>
-<tr data-index="174" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="294" data-listing-title-sort="Proposed: Llama CPP AI Model NPC" data-listing-filename-sort="20231020-llama-cpp-mistral-npc.md">
+<tr data-index="174" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="294" data-listing-title-sort="Proposed: Llama CPP AI Model NPC" data-listing-filename-sort="20231020-llama-cpp-mistral-npc.md">
 <td>
 <a href="./decisions/20231020-llama-cpp-mistral-npc.html" class="title listing-title">Proposed: Llama CPP AI Model NPC</a>
 </td>
@@ -2159,7 +2159,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231020-llama-cpp-mistral-npc.html" class="filename listing-filename">20231020-llama-cpp-mistral-npc.md</a>
 </td>
 </tr>
-<tr data-index="175" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="392" data-listing-title-sort="Proposed: Valve VR Ecosystem with Quest 3" data-listing-filename-sort="20231019-quest3-mocap-steam-lighthouse.md">
+<tr data-index="175" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="392" data-listing-title-sort="Proposed: Valve VR Ecosystem with Quest 3" data-listing-filename-sort="20231019-quest3-mocap-steam-lighthouse.md">
 <td>
 <a href="./decisions/20231019-quest3-mocap-steam-lighthouse.html" class="title listing-title">Proposed: Valve VR Ecosystem with Quest 3</a>
 </td>
@@ -2170,7 +2170,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20231019-quest3-mocap-steam-lighthouse.html" class="filename listing-filename">20231019-quest3-mocap-steam-lighthouse.md</a>
 </td>
 </tr>
-<tr data-index="176" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="371" data-listing-title-sort="Proposed: Streamlining V-Sekai Performance" data-listing-filename-sort="20230922-spacetime-shadow-shards-sync.md">
+<tr data-index="176" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="371" data-listing-title-sort="Proposed: Streamlining V-Sekai Performance" data-listing-filename-sort="20230922-spacetime-shadow-shards-sync.md">
 <td>
 <a href="./decisions/20230922-spacetime-shadow-shards-sync.html" class="title listing-title">Proposed: Streamlining V-Sekai Performance</a>
 </td>
@@ -2181,7 +2181,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230922-spacetime-shadow-shards-sync.html" class="filename listing-filename">20230922-spacetime-shadow-shards-sync.md</a>
 </td>
 </tr>
-<tr data-index="177" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="380" data-listing-title-sort="Proposed: Use embedding search with Godot Engine projects" data-listing-filename-sort="20230920-godot-project-search.md">
+<tr data-index="177" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="380" data-listing-title-sort="Proposed: Use embedding search with Godot Engine projects" data-listing-filename-sort="20230920-godot-project-search.md">
 <td>
 <a href="./decisions/20230920-godot-project-search.html" class="title listing-title">Proposed: Use embedding search with Godot Engine projects</a>
 </td>
@@ -2192,7 +2192,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230920-godot-project-search.html" class="filename listing-filename">20230920-godot-project-search.md</a>
 </td>
 </tr>
-<tr data-index="178" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="375" data-listing-title-sort="Proposed: Challenges that need to be addressed in V-Sekai" data-listing-filename-sort="20230913-V-Sekai-bugs.md">
+<tr data-index="178" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="375" data-listing-title-sort="Proposed: Challenges that need to be addressed in V-Sekai" data-listing-filename-sort="20230913-V-Sekai-bugs.md">
 <td>
 <a href="./decisions/20230913-V-Sekai-bugs.html" class="title listing-title">Proposed: Challenges that need to be addressed in V-Sekai</a>
 </td>
@@ -2203,7 +2203,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230913-V-Sekai-bugs.html" class="filename listing-filename">20230913-V-Sekai-bugs.md</a>
 </td>
 </tr>
-<tr data-index="179" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="1" data-listing-word-count-sort="181" data-listing-title-sort="Proposed: Address Screen Resolution Compatibility Issues" data-listing-filename-sort="20230912-target-most-popular-resolution.md">
+<tr data-index="179" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="1" data-listing-word-count-sort="181" data-listing-title-sort="Proposed: Address Screen Resolution Compatibility Issues" data-listing-filename-sort="20230912-target-most-popular-resolution.md">
 <td>
 <a href="./decisions/20230912-target-most-popular-resolution.html" class="title listing-title">Proposed: Address Screen Resolution Compatibility Issues</a>
 </td>
@@ -2214,7 +2214,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230912-target-most-popular-resolution.html" class="filename listing-filename">20230912-target-most-popular-resolution.md</a>
 </td>
 </tr>
-<tr data-index="180" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="1" data-listing-word-count-sort="199" data-listing-title-sort="Proposed: Improving xr grid with new enhancements" data-listing-filename-sort="20230911-xr-grid-with-drawing.md">
+<tr data-index="180" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="1" data-listing-word-count-sort="199" data-listing-title-sort="Proposed: Improving xr grid with new enhancements" data-listing-filename-sort="20230911-xr-grid-with-drawing.md">
 <td>
 <a href="./decisions/20230911-xr-grid-with-drawing.html" class="title listing-title">Proposed: Improving xr grid with new enhancements</a>
 </td>
@@ -2225,7 +2225,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230911-xr-grid-with-drawing.html" class="filename listing-filename">20230911-xr-grid-with-drawing.md</a>
 </td>
 </tr>
-<tr data-index="181" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="3" data-listing-word-count-sort="597" data-listing-title-sort="Draft: XPR in Elixir" data-listing-filename-sort="20230911-xpr.exs.md">
+<tr data-index="181" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="3" data-listing-word-count-sort="597" data-listing-title-sort="Draft: XPR in Elixir" data-listing-filename-sort="20230911-xpr.exs.md">
 <td>
 <a href="./decisions/20230911-xpr.exs.html" class="title listing-title">Draft: XPR in Elixir</a>
 </td>
@@ -2236,7 +2236,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230911-xpr.exs.html" class="filename listing-filename">20230911-xpr.exs.md</a>
 </td>
 </tr>
-<tr data-index="182" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="316" data-listing-title-sort="Proposed: Implementing Semantic Versioning for Alpha Releases in V-Sekai" data-listing-filename-sort="20230911-first-alpha-tag.md">
+<tr data-index="182" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="2" data-listing-word-count-sort="316" data-listing-title-sort="Proposed: Implementing Semantic Versioning for Alpha Releases in V-Sekai" data-listing-filename-sort="20230911-first-alpha-tag.md">
 <td>
 <a href="./decisions/20230911-first-alpha-tag.html" class="title listing-title">Proposed: Implementing Semantic Versioning for Alpha Releases in V-Sekai</a>
 </td>
@@ -2247,7 +2247,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230911-first-alpha-tag.html" class="filename listing-filename">20230911-first-alpha-tag.md</a>
 </td>
 </tr>
-<tr data-index="183" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="1" data-listing-word-count-sort="73" data-listing-title-sort="Draft: Can Poly Green Coords extend to 3d?" data-listing-filename-sort="20230911-can-poly-green-coords-extend-to-3d.md">
+<tr data-index="183" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="1" data-listing-word-count-sort="73" data-listing-title-sort="Draft: Can Poly Green Coords extend to 3d?" data-listing-filename-sort="20230911-can-poly-green-coords-extend-to-3d.md">
 <td>
 <a href="./decisions/20230911-can-poly-green-coords-extend-to-3d.html" class="title listing-title">Draft: Can Poly Green Coords extend to 3d?</a>
 </td>
@@ -2258,7 +2258,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230911-can-poly-green-coords-extend-to-3d.html" class="filename listing-filename">20230911-can-poly-green-coords-extend-to-3d.md</a>
 </td>
 </tr>
-<tr data-index="184" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="3" data-listing-word-count-sort="558" data-listing-title-sort="Draft: Translation/Transcription Badge with GGML's Whisper" data-listing-filename-sort="20230908-bendable-screen-generative-assistant-ggml.md">
+<tr data-index="184" data-listing-file-modified-sort="1730559023682" data-listing-reading-time-sort="3" data-listing-word-count-sort="558" data-listing-title-sort="Draft: Translation/Transcription Badge with GGML's Whisper" data-listing-filename-sort="20230908-bendable-screen-generative-assistant-ggml.md">
 <td>
 <a href="./decisions/20230908-bendable-screen-generative-assistant-ggml.html" class="title listing-title">Draft: Translation/Transcription Badge with GGML’s Whisper</a>
 </td>
@@ -2269,7 +2269,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230908-bendable-screen-generative-assistant-ggml.html" class="filename listing-filename">20230908-bendable-screen-generative-assistant-ggml.md</a>
 </td>
 </tr>
-<tr data-index="185" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="3" data-listing-word-count-sort="543" data-listing-title-sort="Rejected: Enabling VRM to Blender Conversion with Cloud GPUs and replicate.com" data-listing-filename-sort="20230903-replicate-vrm-transform.md">
+<tr data-index="185" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="3" data-listing-word-count-sort="543" data-listing-title-sort="Rejected: Enabling VRM to Blender Conversion with Cloud GPUs and replicate.com" data-listing-filename-sort="20230903-replicate-vrm-transform.md">
 <td>
 <a href="./decisions/20230903-replicate-vrm-transform.html" class="title listing-title">Rejected: Enabling VRM to Blender Conversion with Cloud GPUs and replicate.com</a>
 </td>
@@ -2280,7 +2280,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230903-replicate-vrm-transform.html" class="filename listing-filename">20230903-replicate-vrm-transform.md</a>
 </td>
 </tr>
-<tr data-index="186" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="239" data-listing-title-sort="Accepted: Enhancing Map Uploads" data-listing-filename-sort="20230831-fixing-upload-limits.md">
+<tr data-index="186" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="2" data-listing-word-count-sort="239" data-listing-title-sort="Accepted: Enhancing Map Uploads" data-listing-filename-sort="20230831-fixing-upload-limits.md">
 <td>
 <a href="./decisions/20230831-fixing-upload-limits.html" class="title listing-title">Accepted: Enhancing Map Uploads</a>
 </td>
@@ -2291,7 +2291,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230831-fixing-upload-limits.html" class="filename listing-filename">20230831-fixing-upload-limits.md</a>
 </td>
 </tr>
-<tr data-index="187" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="1" data-listing-word-count-sort="193" data-listing-title-sort="Accepted: Fix menus in-game" data-listing-filename-sort="20230831-fixing-menus.md">
+<tr data-index="187" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="1" data-listing-word-count-sort="193" data-listing-title-sort="Accepted: Fix menus in-game" data-listing-filename-sort="20230831-fixing-menus.md">
 <td>
 <a href="./decisions/20230831-fixing-menus.html" class="title listing-title">Accepted: Fix menus in-game</a>
 </td>
@@ -2302,7 +2302,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230831-fixing-menus.html" class="filename listing-filename">20230831-fixing-menus.md</a>
 </td>
 </tr>
-<tr data-index="188" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="4" data-listing-word-count-sort="660" data-listing-title-sort="Proposed: Expanding Worlds" data-listing-filename-sort="20230830-generating-v-sekai-worlds.md">
+<tr data-index="188" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="4" data-listing-word-count-sort="660" data-listing-title-sort="Proposed: Expanding Worlds" data-listing-filename-sort="20230830-generating-v-sekai-worlds.md">
 <td>
 <a href="./decisions/20230830-generating-v-sekai-worlds.html" class="title listing-title">Proposed: Expanding Worlds</a>
 </td>
@@ -2313,7 +2313,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230830-generating-v-sekai-worlds.html" class="filename listing-filename">20230830-generating-v-sekai-worlds.md</a>
 </td>
 </tr>
-<tr data-index="189" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="376" data-listing-title-sort="Proposed: Improving VR Experience" data-listing-filename-sort="20230830-better-object-pick.md">
+<tr data-index="189" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="2" data-listing-word-count-sort="376" data-listing-title-sort="Proposed: Improving VR Experience" data-listing-filename-sort="20230830-better-object-pick.md">
 <td>
 <a href="./decisions/20230830-better-object-pick.html" class="title listing-title">Proposed: Improving VR Experience</a>
 </td>
@@ -2324,7 +2324,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230830-better-object-pick.html" class="filename listing-filename">20230830-better-object-pick.md</a>
 </td>
 </tr>
-<tr data-index="190" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="339" data-listing-title-sort="Proposed: Integrating Backend Services" data-listing-filename-sort="20230830-better-backend-services.md">
+<tr data-index="190" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="2" data-listing-word-count-sort="339" data-listing-title-sort="Proposed: Integrating Backend Services" data-listing-filename-sort="20230830-better-backend-services.md">
 <td>
 <a href="./decisions/20230830-better-backend-services.html" class="title listing-title">Proposed: Integrating Backend Services</a>
 </td>
@@ -2335,7 +2335,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230830-better-backend-services.html" class="filename listing-filename">20230830-better-backend-services.md</a>
 </td>
 </tr>
-<tr data-index="191" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="5" data-listing-word-count-sort="821" data-listing-title-sort="Proposed: OMIFest 2023 - The Call" data-listing-filename-sort="20230829-omifest-2023.md">
+<tr data-index="191" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="5" data-listing-word-count-sort="821" data-listing-title-sort="Proposed: OMIFest 2023 - The Call" data-listing-filename-sort="20230829-omifest-2023.md">
 <td>
 <a href="./decisions/20230829-omifest-2023.html" class="title listing-title">Proposed: OMIFest 2023 - The Call</a>
 </td>
@@ -2346,7 +2346,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230829-omifest-2023.html" class="filename listing-filename">20230829-omifest-2023.md</a>
 </td>
 </tr>
-<tr data-index="192" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="214" data-listing-title-sort="Accepted: Use opensubdiv for level of detail" data-listing-filename-sort="20230824-subdiv-for-lods.md">
+<tr data-index="192" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="2" data-listing-word-count-sort="214" data-listing-title-sort="Accepted: Use opensubdiv for level of detail" data-listing-filename-sort="20230824-subdiv-for-lods.md">
 <td>
 <a href="./decisions/20230824-subdiv-for-lods.html" class="title listing-title">Accepted: Use opensubdiv for level of detail</a>
 </td>
@@ -2357,7 +2357,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230824-subdiv-for-lods.html" class="filename listing-filename">20230824-subdiv-for-lods.md</a>
 </td>
 </tr>
-<tr data-index="193" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="4" data-listing-word-count-sort="724" data-listing-title-sort="Proposed: Developing a Unified Model for Speech-to-Facial Shape Generation Using Outlines 〰 Library" data-listing-filename-sort="20230823-speech-to-blendshapes.md">
+<tr data-index="193" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="4" data-listing-word-count-sort="724" data-listing-title-sort="Proposed: Developing a Unified Model for Speech-to-Facial Shape Generation Using Outlines 〰 Library" data-listing-filename-sort="20230823-speech-to-blendshapes.md">
 <td>
 <a href="./decisions/20230823-speech-to-blendshapes.html" class="title listing-title">Proposed: Developing a Unified Model for Speech-to-Facial Shape Generation Using Outlines 〰 Library</a>
 </td>
@@ -2368,7 +2368,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230823-speech-to-blendshapes.html" class="filename listing-filename">20230823-speech-to-blendshapes.md</a>
 </td>
 </tr>
-<tr data-index="194" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="368" data-listing-title-sort="Proposed: Following Tracks: Enhancing VR Train Station Simulation in V-Sekai using Godot Engine" data-listing-filename-sort="20230819-train-game.md">
+<tr data-index="194" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="2" data-listing-word-count-sort="368" data-listing-title-sort="Proposed: Following Tracks: Enhancing VR Train Station Simulation in V-Sekai using Godot Engine" data-listing-filename-sort="20230819-train-game.md">
 <td>
 <a href="./decisions/20230819-train-game.html" class="title listing-title">Proposed: Following Tracks: Enhancing VR Train Station Simulation in V-Sekai using Godot Engine</a>
 </td>
@@ -2379,7 +2379,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230819-train-game.html" class="filename listing-filename">20230819-train-game.md</a>
 </td>
 </tr>
-<tr data-index="195" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="3" data-listing-word-count-sort="540" data-listing-title-sort="Rejected: Rewriting Mixer Broadcaster Into Membrane Framework Pipelines" data-listing-filename-sort="20230813-mixer-broadcaster-into-membrane-framework copy.md">
+<tr data-index="195" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="3" data-listing-word-count-sort="540" data-listing-title-sort="Rejected: Rewriting Mixer Broadcaster Into Membrane Framework Pipelines" data-listing-filename-sort="20230813-mixer-broadcaster-into-membrane-framework copy.md">
 <td>
 <a href="./decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html" class="title listing-title">Rejected: Rewriting Mixer Broadcaster Into Membrane Framework Pipelines</a>
 </td>
@@ -2390,7 +2390,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html" class="filename listing-filename">20230813-mixer-broadcaster-into-membrane-framework copy.md</a>
 </td>
 </tr>
-<tr data-index="196" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="5" data-listing-word-count-sort="919" data-listing-title-sort="Proposed: Transitioning to Membrane Framework Pipelines with JSON-RPC Blender Runner" data-listing-filename-sort="20230813-blender-runner-into-membrane-framework.md">
+<tr data-index="196" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="5" data-listing-word-count-sort="919" data-listing-title-sort="Proposed: Transitioning to Membrane Framework Pipelines with JSON-RPC Blender Runner" data-listing-filename-sort="20230813-blender-runner-into-membrane-framework.md">
 <td>
 <a href="./decisions/20230813-blender-runner-into-membrane-framework.html" class="title listing-title">Proposed: Transitioning to Membrane Framework Pipelines with JSON-RPC Blender Runner</a>
 </td>
@@ -2401,7 +2401,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230813-blender-runner-into-membrane-framework.html" class="filename listing-filename">20230813-blender-runner-into-membrane-framework.md</a>
 </td>
 </tr>
-<tr data-index="197" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="239" data-listing-title-sort="Proposed: Update V-Sekai game engine procedure" data-listing-filename-sort="20230812-vsekai-update-process.md">
+<tr data-index="197" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="2" data-listing-word-count-sort="239" data-listing-title-sort="Proposed: Update V-Sekai game engine procedure" data-listing-filename-sort="20230812-vsekai-update-process.md">
 <td>
 <a href="./decisions/20230812-vsekai-update-process.html" class="title listing-title">Proposed: Update V-Sekai game engine procedure</a>
 </td>
@@ -2412,7 +2412,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230812-vsekai-update-process.html" class="filename listing-filename">20230812-vsekai-update-process.md</a>
 </td>
 </tr>
-<tr data-index="198" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="284" data-listing-title-sort="Proposed: Procedure to unmerge and then merge solves a V-Sekai source code broken tree" data-listing-filename-sort="20230812-unmerge-and-merge-procedure-source-code-tree.md">
+<tr data-index="198" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="2" data-listing-word-count-sort="284" data-listing-title-sort="Proposed: Procedure to unmerge and then merge solves a V-Sekai source code broken tree" data-listing-filename-sort="20230812-unmerge-and-merge-procedure-source-code-tree.md">
 <td>
 <a href="./decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html" class="title listing-title">Proposed: Procedure to unmerge and then merge solves a V-Sekai source code broken tree</a>
 </td>
@@ -2423,7 +2423,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html" class="filename listing-filename">20230812-unmerge-and-merge-procedure-source-code-tree.md</a>
 </td>
 </tr>
-<tr data-index="199" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="3" data-listing-word-count-sort="433" data-listing-title-sort="Proposed: Configuring GoCD Agents in V-Sekai" data-listing-filename-sort="20230812-gocd-agent-setup.md">
+<tr data-index="199" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="3" data-listing-word-count-sort="433" data-listing-title-sort="Proposed: Configuring GoCD Agents in V-Sekai" data-listing-filename-sort="20230812-gocd-agent-setup.md">
 <td>
 <a href="./decisions/20230812-gocd-agent-setup.html" class="title listing-title">Proposed: Configuring GoCD Agents in V-Sekai</a>
 </td>
@@ -2434,7 +2434,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230812-gocd-agent-setup.html" class="filename listing-filename">20230812-gocd-agent-setup.md</a>
 </td>
 </tr>
-<tr data-index="200" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="278" data-listing-title-sort="Proposed: Constrain the entire Godot Humanoid Skeleton" data-listing-filename-sort="20230812-constraint-all-bones.md">
+<tr data-index="200" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="2" data-listing-word-count-sort="278" data-listing-title-sort="Proposed: Constrain the entire Godot Humanoid Skeleton" data-listing-filename-sort="20230812-constraint-all-bones.md">
 <td>
 <a href="./decisions/20230812-constraint-all-bones.html" class="title listing-title">Proposed: Constrain the entire Godot Humanoid Skeleton</a>
 </td>
@@ -2445,7 +2445,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230812-constraint-all-bones.html" class="filename listing-filename">20230812-constraint-all-bones.md</a>
 </td>
 </tr>
-<tr data-index="201" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="3" data-listing-word-count-sort="422" data-listing-title-sort="Accepted: Punchline based reports" data-listing-filename-sort="20230811-punchline-reports.md">
+<tr data-index="201" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="3" data-listing-word-count-sort="422" data-listing-title-sort="Accepted: Punchline based reports" data-listing-filename-sort="20230811-punchline-reports.md">
 <td>
 <a href="./decisions/20230811-punchline-reports.html" class="title listing-title">Accepted: Punchline based reports</a>
 </td>
@@ -2456,7 +2456,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230811-punchline-reports.html" class="filename listing-filename">20230811-punchline-reports.md</a>
 </td>
 </tr>
-<tr data-index="202" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="320" data-listing-title-sort="Proposed: V-Sekai Navigation Compatibility with VR" data-listing-filename-sort="20230806-v-sekai-ipad-projection-compatibility.md">
+<tr data-index="202" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="2" data-listing-word-count-sort="320" data-listing-title-sort="Proposed: V-Sekai Navigation Compatibility with VR" data-listing-filename-sort="20230806-v-sekai-ipad-projection-compatibility.md">
 <td>
 <a href="./decisions/20230806-v-sekai-ipad-projection-compatibility.html" class="title listing-title">Proposed: V-Sekai Navigation Compatibility with VR</a>
 </td>
@@ -2467,7 +2467,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230806-v-sekai-ipad-projection-compatibility.html" class="filename listing-filename">20230806-v-sekai-ipad-projection-compatibility.md</a>
 </td>
 </tr>
-<tr data-index="203" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="3" data-listing-word-count-sort="474" data-listing-title-sort="Proposed: Sonic Symphony: Crafting Melodies with Machine Intelligence" data-listing-filename-sort="20230806-music-gen.md">
+<tr data-index="203" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="3" data-listing-word-count-sort="474" data-listing-title-sort="Proposed: Sonic Symphony: Crafting Melodies with Machine Intelligence" data-listing-filename-sort="20230806-music-gen.md">
 <td>
 <a href="./decisions/20230806-music-gen.html" class="title listing-title">Proposed: Sonic Symphony: Crafting Melodies with Machine Intelligence</a>
 </td>
@@ -2478,7 +2478,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230806-music-gen.html" class="filename listing-filename">20230806-music-gen.md</a>
 </td>
 </tr>
-<tr data-index="204" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="340" data-listing-title-sort="Proposed: Dokku for V-Sekai URO Backend Services Hosting and Development" data-listing-filename-sort="20230804-dokku.md">
+<tr data-index="204" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="2" data-listing-word-count-sort="340" data-listing-title-sort="Proposed: Dokku for V-Sekai URO Backend Services Hosting and Development" data-listing-filename-sort="20230804-dokku.md">
 <td>
 <a href="./decisions/20230804-dokku.html" class="title listing-title">Proposed: Dokku for V-Sekai URO Backend Services Hosting and Development</a>
 </td>
@@ -2489,7 +2489,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230804-dokku.html" class="filename listing-filename">20230804-dokku.md</a>
 </td>
 </tr>
-<tr data-index="205" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="293" data-listing-title-sort="Accepted: Git Subrepo Addon Management" data-listing-filename-sort="20230803-subrepo-addon-management.md">
+<tr data-index="205" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="2" data-listing-word-count-sort="293" data-listing-title-sort="Accepted: Git Subrepo Addon Management" data-listing-filename-sort="20230803-subrepo-addon-management.md">
 <td>
 <a href="./decisions/20230803-subrepo-addon-management.html" class="title listing-title">Accepted: Git Subrepo Addon Management</a>
 </td>
@@ -2500,7 +2500,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230803-subrepo-addon-management.html" class="filename listing-filename">20230803-subrepo-addon-management.md</a>
 </td>
 </tr>
-<tr data-index="206" data-listing-file-modified-sort="1730535490034" data-listing-reading-time-sort="2" data-listing-word-count-sort="359" data-listing-title-sort="Accepted: Completing VRM 1.0 Support and Publishing to Godot Engine Asset Library" data-listing-filename-sort="20230803-publish-vrm-to-assetlibrary.md">
+<tr data-index="206" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="2" data-listing-word-count-sort="359" data-listing-title-sort="Accepted: Completing VRM 1.0 Support and Publishing to Godot Engine Asset Library" data-listing-filename-sort="20230803-publish-vrm-to-assetlibrary.md">
 <td>
 <a href="./decisions/20230803-publish-vrm-to-assetlibrary.html" class="title listing-title">Accepted: Completing VRM 1.0 Support and Publishing to Godot Engine Asset Library</a>
 </td>
@@ -2511,7 +2511,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230803-publish-vrm-to-assetlibrary.html" class="filename listing-filename">20230803-publish-vrm-to-assetlibrary.md</a>
 </td>
 </tr>
-<tr data-index="207" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="2" data-listing-word-count-sort="270" data-listing-title-sort="Proposed: Port Godot Jolt from GDExtension to C++ Module" data-listing-filename-sort="20230803-jolt-gextension-to-module.md">
+<tr data-index="207" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="2" data-listing-word-count-sort="270" data-listing-title-sort="Proposed: Port Godot Jolt from GDExtension to C++ Module" data-listing-filename-sort="20230803-jolt-gextension-to-module.md">
 <td>
 <a href="./decisions/20230803-jolt-gextension-to-module.html" class="title listing-title">Proposed: Port Godot Jolt from GDExtension to C++ Module</a>
 </td>
@@ -2522,7 +2522,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230803-jolt-gextension-to-module.html" class="filename listing-filename">20230803-jolt-gextension-to-module.md</a>
 </td>
 </tr>
-<tr data-index="208" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="2" data-listing-word-count-sort="362" data-listing-title-sort="Proposed: Social RPG World Proposal" data-listing-filename-sort="20230803-idle-rpg-home.md">
+<tr data-index="208" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="2" data-listing-word-count-sort="362" data-listing-title-sort="Proposed: Social RPG World Proposal" data-listing-filename-sort="20230803-idle-rpg-home.md">
 <td>
 <a href="./decisions/20230803-idle-rpg-home.html" class="title listing-title">Proposed: Social RPG World Proposal</a>
 </td>
@@ -2533,7 +2533,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230803-idle-rpg-home.html" class="filename listing-filename">20230803-idle-rpg-home.md</a>
 </td>
 </tr>
-<tr data-index="209" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="2" data-listing-word-count-sort="238" data-listing-title-sort="Proposed: Solve Renik directly rather than through many bone ik" data-listing-filename-sort="20230726-solve-renik-directly-rather-than-many-bone-ik.md">
+<tr data-index="209" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="2" data-listing-word-count-sort="238" data-listing-title-sort="Proposed: Solve Renik directly rather than through many bone ik" data-listing-filename-sort="20230726-solve-renik-directly-rather-than-many-bone-ik.md">
 <td>
 <a href="./decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html" class="title listing-title">Proposed: Solve Renik directly rather than through many bone ik</a>
 </td>
@@ -2544,7 +2544,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html" class="filename listing-filename">20230726-solve-renik-directly-rather-than-many-bone-ik.md</a>
 </td>
 </tr>
-<tr data-index="210" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="3" data-listing-word-count-sort="564" data-listing-title-sort="Proposed: Enhancing the Many Bone IK Configuration" data-listing-filename-sort="20230719-pose-kusudama-constraints-in-vr.md">
+<tr data-index="210" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="3" data-listing-word-count-sort="564" data-listing-title-sort="Proposed: Enhancing the Many Bone IK Configuration" data-listing-filename-sort="20230719-pose-kusudama-constraints-in-vr.md">
 <td>
 <a href="./decisions/20230719-pose-kusudama-constraints-in-vr.html" class="title listing-title">Proposed: Enhancing the Many Bone IK Configuration</a>
 </td>
@@ -2555,7 +2555,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230719-pose-kusudama-constraints-in-vr.html" class="filename listing-filename">20230719-pose-kusudama-constraints-in-vr.md</a>
 </td>
 </tr>
-<tr data-index="211" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="2" data-listing-word-count-sort="394" data-listing-title-sort="Proposed: Game simulation server sidekick process" data-listing-filename-sort="20230719-dual-databases-cockroachdb-khepri.md">
+<tr data-index="211" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="2" data-listing-word-count-sort="394" data-listing-title-sort="Proposed: Game simulation server sidekick process" data-listing-filename-sort="20230719-dual-databases-cockroachdb-khepri.md">
 <td>
 <a href="./decisions/20230719-dual-databases-cockroachdb-khepri.html" class="title listing-title">Proposed: Game simulation server sidekick process</a>
 </td>
@@ -2566,7 +2566,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230719-dual-databases-cockroachdb-khepri.html" class="filename listing-filename">20230719-dual-databases-cockroachdb-khepri.md</a>
 </td>
 </tr>
-<tr data-index="212" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="4" data-listing-word-count-sort="738" data-listing-title-sort="Proposed: Enhancing Avatar Creation Process in V-Sekai Advanced" data-listing-filename-sort="20230716-enhancing-avatar-creation-process-02-advanced.md">
+<tr data-index="212" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="4" data-listing-word-count-sort="738" data-listing-title-sort="Proposed: Enhancing Avatar Creation Process in V-Sekai Advanced" data-listing-filename-sort="20230716-enhancing-avatar-creation-process-02-advanced.md">
 <td>
 <a href="./decisions/20230716-enhancing-avatar-creation-process-02-advanced.html" class="title listing-title">Proposed: Enhancing Avatar Creation Process in V-Sekai Advanced</a>
 </td>
@@ -2577,7 +2577,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230716-enhancing-avatar-creation-process-02-advanced.html" class="filename listing-filename">20230716-enhancing-avatar-creation-process-02-advanced.md</a>
 </td>
 </tr>
-<tr data-index="213" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="5" data-listing-word-count-sort="854" data-listing-title-sort="Proposed: Enhancing Avatar Creation Process in V-Sekai Regular" data-listing-filename-sort="20230716-enhancing-avatar-creation-process-01-regular.md">
+<tr data-index="213" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="5" data-listing-word-count-sort="854" data-listing-title-sort="Proposed: Enhancing Avatar Creation Process in V-Sekai Regular" data-listing-filename-sort="20230716-enhancing-avatar-creation-process-01-regular.md">
 <td>
 <a href="./decisions/20230716-enhancing-avatar-creation-process-01-regular.html" class="title listing-title">Proposed: Enhancing Avatar Creation Process in V-Sekai Regular</a>
 </td>
@@ -2588,7 +2588,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230716-enhancing-avatar-creation-process-01-regular.html" class="filename listing-filename">20230716-enhancing-avatar-creation-process-01-regular.md</a>
 </td>
 </tr>
-<tr data-index="214" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="6" data-listing-word-count-sort="1108" data-listing-title-sort="Proposed: V-Sekai Feature Enhancement Proposal" data-listing-filename-sort="20230701-vsekai-broken-down-goals.md">
+<tr data-index="214" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="6" data-listing-word-count-sort="1108" data-listing-title-sort="Proposed: V-Sekai Feature Enhancement Proposal" data-listing-filename-sort="20230701-vsekai-broken-down-goals.md">
 <td>
 <a href="./decisions/20230701-vsekai-broken-down-goals.html" class="title listing-title">Proposed: V-Sekai Feature Enhancement Proposal</a>
 </td>
@@ -2599,7 +2599,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230701-vsekai-broken-down-goals.html" class="filename listing-filename">20230701-vsekai-broken-down-goals.md</a>
 </td>
 </tr>
-<tr data-index="215" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="2" data-listing-word-count-sort="287" data-listing-title-sort="Accepted: V-Sekai Meeting - Friday, June 30, 2023" data-listing-filename-sort="20230630-vsekai-goal-meeting.md">
+<tr data-index="215" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="2" data-listing-word-count-sort="287" data-listing-title-sort="Accepted: V-Sekai Meeting - Friday, June 30, 2023" data-listing-filename-sort="20230630-vsekai-goal-meeting.md">
 <td>
 <a href="./decisions/20230630-vsekai-goal-meeting.html" class="title listing-title">Accepted: V-Sekai Meeting - Friday, June 30, 2023</a>
 </td>
@@ -2610,7 +2610,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230630-vsekai-goal-meeting.html" class="filename listing-filename">20230630-vsekai-goal-meeting.md</a>
 </td>
 </tr>
-<tr data-index="216" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="3" data-listing-word-count-sort="466" data-listing-title-sort="Proposed: Ship Godot Engine VRM1 to solve portable humanoid avatars" data-listing-filename-sort="20230626-godot-vrm1-addon.md">
+<tr data-index="216" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="3" data-listing-word-count-sort="466" data-listing-title-sort="Proposed: Ship Godot Engine VRM1 to solve portable humanoid avatars" data-listing-filename-sort="20230626-godot-vrm1-addon.md">
 <td>
 <a href="./decisions/20230626-godot-vrm1-addon.html" class="title listing-title">Proposed: Ship Godot Engine VRM1 to solve portable humanoid avatars</a>
 </td>
@@ -2621,7 +2621,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230626-godot-vrm1-addon.html" class="filename listing-filename">20230626-godot-vrm1-addon.md</a>
 </td>
 </tr>
-<tr data-index="217" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="2" data-listing-word-count-sort="230" data-listing-title-sort="Accepted: V-Sekai Roadmap and Goals 2023-06-24" data-listing-filename-sort="20230624-v-sekai-roadmap.md">
+<tr data-index="217" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="2" data-listing-word-count-sort="230" data-listing-title-sort="Accepted: V-Sekai Roadmap and Goals 2023-06-24" data-listing-filename-sort="20230624-v-sekai-roadmap.md">
 <td>
 <a href="./decisions/20230624-v-sekai-roadmap.html" class="title listing-title">Accepted: V-Sekai Roadmap and Goals 2023-06-24</a>
 </td>
@@ -2632,7 +2632,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230624-v-sekai-roadmap.html" class="filename listing-filename">20230624-v-sekai-roadmap.md</a>
 </td>
 </tr>
-<tr data-index="218" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="8" data-listing-word-count-sort="1423" data-listing-title-sort="Proposed: Implementing Feedback Delay Networks for Enhanced Audio Reverb Simulation in V-Sekai" data-listing-filename-sort="20230623-fdn-reverb-solution.md">
+<tr data-index="218" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="8" data-listing-word-count-sort="1423" data-listing-title-sort="Proposed: Implementing Feedback Delay Networks for Enhanced Audio Reverb Simulation in V-Sekai" data-listing-filename-sort="20230623-fdn-reverb-solution.md">
 <td>
 <a href="./decisions/20230623-fdn-reverb-solution.html" class="title listing-title">Proposed: Implementing Feedback Delay Networks for Enhanced Audio Reverb Simulation in V-Sekai</a>
 </td>
@@ -2643,7 +2643,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230623-fdn-reverb-solution.html" class="filename listing-filename">20230623-fdn-reverb-solution.md</a>
 </td>
 </tr>
-<tr data-index="219" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="5" data-listing-word-count-sort="820" data-listing-title-sort="Proposed: Large language model t5 generating xstate json reliabily for digital beings" data-listing-filename-sort="20230620-t5-jsonformer-xstate.md">
+<tr data-index="219" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="5" data-listing-word-count-sort="820" data-listing-title-sort="Proposed: Large language model t5 generating xstate json reliabily for digital beings" data-listing-filename-sort="20230620-t5-jsonformer-xstate.md">
 <td>
 <a href="./decisions/20230620-t5-jsonformer-xstate.html" class="title listing-title">Proposed: Large language model t5 generating xstate json reliabily for digital beings</a>
 </td>
@@ -2654,7 +2654,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230620-t5-jsonformer-xstate.html" class="filename listing-filename">20230620-t5-jsonformer-xstate.md</a>
 </td>
 </tr>
-<tr data-index="220" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="2" data-listing-word-count-sort="324" data-listing-title-sort="Proposed: A Potential Solution for V-Sekai's Identifier Assignment Challenge" data-listing-filename-sort="20230620-doi-github.md">
+<tr data-index="220" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="2" data-listing-word-count-sort="324" data-listing-title-sort="Proposed: A Potential Solution for V-Sekai's Identifier Assignment Challenge" data-listing-filename-sort="20230620-doi-github.md">
 <td>
 <a href="./decisions/20230620-doi-github.html" class="title listing-title">Proposed: A Potential Solution for V-Sekai’s Identifier Assignment Challenge</a>
 </td>
@@ -2665,7 +2665,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230620-doi-github.html" class="filename listing-filename">20230620-doi-github.md</a>
 </td>
 </tr>
-<tr data-index="221" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="2" data-listing-word-count-sort="395" data-listing-title-sort="Rejected: V-Sekai Database Solution for 50,000 Concurrent Online Users" data-listing-filename-sort="20230619-move-cockroachdb-to-yugabyte.md">
+<tr data-index="221" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="2" data-listing-word-count-sort="395" data-listing-title-sort="Rejected: V-Sekai Database Solution for 50,000 Concurrent Online Users" data-listing-filename-sort="20230619-move-cockroachdb-to-yugabyte.md">
 <td>
 <a href="./decisions/20230619-move-cockroachdb-to-yugabyte.html" class="title listing-title">Rejected: V-Sekai Database Solution for 50,000 Concurrent Online Users</a>
 </td>
@@ -2676,7 +2676,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230619-move-cockroachdb-to-yugabyte.html" class="filename listing-filename">20230619-move-cockroachdb-to-yugabyte.md</a>
 </td>
 </tr>
-<tr data-index="222" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="3" data-listing-word-count-sort="551" data-listing-title-sort="Proposed: Networked Procedural Generation as a Sidecar to the Godot Engine Server" data-listing-filename-sort="20230619-membrane-framework-for-mesh-processing.md">
+<tr data-index="222" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="3" data-listing-word-count-sort="551" data-listing-title-sort="Proposed: Networked Procedural Generation as a Sidecar to the Godot Engine Server" data-listing-filename-sort="20230619-membrane-framework-for-mesh-processing.md">
 <td>
 <a href="./decisions/20230619-membrane-framework-for-mesh-processing.html" class="title listing-title">Proposed: Networked Procedural Generation as a Sidecar to the Godot Engine Server</a>
 </td>
@@ -2687,7 +2687,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230619-membrane-framework-for-mesh-processing.html" class="filename listing-filename">20230619-membrane-framework-for-mesh-processing.md</a>
 </td>
 </tr>
-<tr data-index="223" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="3" data-listing-word-count-sort="581" data-listing-title-sort="Accepted: V-Sekai Roadmap and Goals 2023-06-18" data-listing-filename-sort="20230618-v-sekai-roadmap.md">
+<tr data-index="223" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="3" data-listing-word-count-sort="581" data-listing-title-sort="Accepted: V-Sekai Roadmap and Goals 2023-06-18" data-listing-filename-sort="20230618-v-sekai-roadmap.md">
 <td>
 <a href="./decisions/20230618-v-sekai-roadmap.html" class="title listing-title">Accepted: V-Sekai Roadmap and Goals 2023-06-18</a>
 </td>
@@ -2698,7 +2698,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230618-v-sekai-roadmap.html" class="filename listing-filename">20230618-v-sekai-roadmap.md</a>
 </td>
 </tr>
-<tr data-index="224" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="2" data-listing-word-count-sort="223" data-listing-title-sort="Proposed: V-Sekai Bone Hierarchy Conversion" data-listing-filename-sort="20230616-pmx-to-vrm.md">
+<tr data-index="224" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="2" data-listing-word-count-sort="223" data-listing-title-sort="Proposed: V-Sekai Bone Hierarchy Conversion" data-listing-filename-sort="20230616-pmx-to-vrm.md">
 <td>
 <a href="./decisions/20230616-pmx-to-vrm.html" class="title listing-title">Proposed: V-Sekai Bone Hierarchy Conversion</a>
 </td>
@@ -2709,7 +2709,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230616-pmx-to-vrm.html" class="filename listing-filename">20230616-pmx-to-vrm.md</a>
 </td>
 </tr>
-<tr data-index="225" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="2" data-listing-word-count-sort="258" data-listing-title-sort="Proposed: Increase variety and quality with generated animation trees" data-listing-filename-sort="20230614-llm-statechart.md">
+<tr data-index="225" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="2" data-listing-word-count-sort="258" data-listing-title-sort="Proposed: Increase variety and quality with generated animation trees" data-listing-filename-sort="20230614-llm-statechart.md">
 <td>
 <a href="./decisions/20230614-llm-statechart.html" class="title listing-title">Proposed: Increase variety and quality with generated animation trees</a>
 </td>
@@ -2720,7 +2720,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230614-llm-statechart.html" class="filename listing-filename">20230614-llm-statechart.md</a>
 </td>
 </tr>
-<tr data-index="226" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="5" data-listing-word-count-sort="812" data-listing-title-sort="Proposed: Wasm in V-Sekai Proposal" data-listing-filename-sort="20230611-wasm-in-v-sekai.md">
+<tr data-index="226" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="5" data-listing-word-count-sort="812" data-listing-title-sort="Proposed: Wasm in V-Sekai Proposal" data-listing-filename-sort="20230611-wasm-in-v-sekai.md">
 <td>
 <a href="./decisions/20230611-wasm-in-v-sekai.html" class="title listing-title">Proposed: Wasm in V-Sekai Proposal</a>
 </td>
@@ -2731,7 +2731,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230611-wasm-in-v-sekai.html" class="filename listing-filename">20230611-wasm-in-v-sekai.md</a>
 </td>
 </tr>
-<tr data-index="227" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="2" data-listing-word-count-sort="255" data-listing-title-sort="Superseded: V-Sekai Roadmap and Goals 2023-06-08" data-listing-filename-sort="20230608-v-sekai-roadmap.md">
+<tr data-index="227" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="2" data-listing-word-count-sort="255" data-listing-title-sort="Superseded: V-Sekai Roadmap and Goals 2023-06-08" data-listing-filename-sort="20230608-v-sekai-roadmap.md">
 <td>
 <a href="./decisions/20230608-v-sekai-roadmap.html" class="title listing-title">Superseded: V-Sekai Roadmap and Goals 2023-06-08</a>
 </td>
@@ -2742,7 +2742,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230608-v-sekai-roadmap.html" class="filename listing-filename">20230608-v-sekai-roadmap.md</a>
 </td>
 </tr>
-<tr data-index="228" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="2" data-listing-word-count-sort="211" data-listing-title-sort="Superseded: V-Sekai Roadmap and Goals 2023-06-02" data-listing-filename-sort="20230602-v-sekai-roadmap.md">
+<tr data-index="228" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="2" data-listing-word-count-sort="211" data-listing-title-sort="Superseded: V-Sekai Roadmap and Goals 2023-06-02" data-listing-filename-sort="20230602-v-sekai-roadmap.md">
 <td>
 <a href="./decisions/20230602-v-sekai-roadmap.html" class="title listing-title">Superseded: V-Sekai Roadmap and Goals 2023-06-02</a>
 </td>
@@ -2753,7 +2753,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230602-v-sekai-roadmap.html" class="filename listing-filename">20230602-v-sekai-roadmap.md</a>
 </td>
 </tr>
-<tr data-index="229" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="3" data-listing-word-count-sort="415" data-listing-title-sort="Proposed: Pmx module integration" data-listing-filename-sort="20230602-pmx-module-integration.md">
+<tr data-index="229" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="3" data-listing-word-count-sort="415" data-listing-title-sort="Proposed: Pmx module integration" data-listing-filename-sort="20230602-pmx-module-integration.md">
 <td>
 <a href="./decisions/20230602-pmx-module-integration.html" class="title listing-title">Proposed: Pmx module integration</a>
 </td>
@@ -2764,7 +2764,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230602-pmx-module-integration.html" class="filename listing-filename">20230602-pmx-module-integration.md</a>
 </td>
 </tr>
-<tr data-index="230" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="4" data-listing-word-count-sort="645" data-listing-title-sort="Proposed: Capturing accurate body movements with limited tracker placement" data-listing-filename-sort="20230602-limited-tracker-placement.md">
+<tr data-index="230" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="4" data-listing-word-count-sort="645" data-listing-title-sort="Proposed: Capturing accurate body movements with limited tracker placement" data-listing-filename-sort="20230602-limited-tracker-placement.md">
 <td>
 <a href="./decisions/20230602-limited-tracker-placement.html" class="title listing-title">Proposed: Capturing accurate body movements with limited tracker placement</a>
 </td>
@@ -2775,7 +2775,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230602-limited-tracker-placement.html" class="filename listing-filename">20230602-limited-tracker-placement.md</a>
 </td>
 </tr>
-<tr data-index="231" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="2" data-listing-word-count-sort="242" data-listing-title-sort="Proposed: Propose a solution to improve V-Sekai contributors' design skills for navigating 3D environments" data-listing-filename-sort="20230531-godot-engine-learning.md">
+<tr data-index="231" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="2" data-listing-word-count-sort="242" data-listing-title-sort="Proposed: Propose a solution to improve V-Sekai contributors' design skills for navigating 3D environments" data-listing-filename-sort="20230531-godot-engine-learning.md">
 <td>
 <a href="./decisions/20230531-godot-engine-learning.html" class="title listing-title">Proposed: Propose a solution to improve V-Sekai contributors’ design skills for navigating 3D environments</a>
 </td>
@@ -2786,7 +2786,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230531-godot-engine-learning.html" class="filename listing-filename">20230531-godot-engine-learning.md</a>
 </td>
 </tr>
-<tr data-index="232" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="3" data-listing-word-count-sort="401" data-listing-title-sort="Proposed: Build a Single-Instance MacOS Editor for the iPad" data-listing-filename-sort="20230531-godot-engine-ipad.md">
+<tr data-index="232" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="3" data-listing-word-count-sort="401" data-listing-title-sort="Proposed: Build a Single-Instance MacOS Editor for the iPad" data-listing-filename-sort="20230531-godot-engine-ipad.md">
 <td>
 <a href="./decisions/20230531-godot-engine-ipad.html" class="title listing-title">Proposed: Build a Single-Instance MacOS Editor for the iPad</a>
 </td>
@@ -2797,7 +2797,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230531-godot-engine-ipad.html" class="filename listing-filename">20230531-godot-engine-ipad.md</a>
 </td>
 </tr>
-<tr data-index="233" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="2" data-listing-word-count-sort="224" data-listing-title-sort="Superseded: V-Sekai Roadmap and Goals 2023-05-19" data-listing-filename-sort="20230527-v-sekai-roadmap.md">
+<tr data-index="233" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="2" data-listing-word-count-sort="224" data-listing-title-sort="Superseded: V-Sekai Roadmap and Goals 2023-05-19" data-listing-filename-sort="20230527-v-sekai-roadmap.md">
 <td>
 <a href="./decisions/20230527-v-sekai-roadmap.html" class="title listing-title">Superseded: V-Sekai Roadmap and Goals 2023-05-19</a>
 </td>
@@ -2808,7 +2808,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230527-v-sekai-roadmap.html" class="filename listing-filename">20230527-v-sekai-roadmap.md</a>
 </td>
 </tr>
-<tr data-index="234" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="3" data-listing-word-count-sort="497" data-listing-title-sort="Proposed: Efficiently managing and synchronizing game data with a server sidecar" data-listing-filename-sort="20230527-server-sidecar.md">
+<tr data-index="234" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="3" data-listing-word-count-sort="497" data-listing-title-sort="Proposed: Efficiently managing and synchronizing game data with a server sidecar" data-listing-filename-sort="20230527-server-sidecar.md">
 <td>
 <a href="./decisions/20230527-server-sidecar.html" class="title listing-title">Proposed: Efficiently managing and synchronizing game data with a server sidecar</a>
 </td>
@@ -2819,7 +2819,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230527-server-sidecar.html" class="filename listing-filename">20230527-server-sidecar.md</a>
 </td>
 </tr>
-<tr data-index="235" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="2" data-listing-word-count-sort="330" data-listing-title-sort="Proposed: Implement server-side content validation export followed by a sanitization service and CDN support" data-listing-filename-sort="20230527-server-side-content-validation.md">
+<tr data-index="235" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="2" data-listing-word-count-sort="330" data-listing-title-sort="Proposed: Implement server-side content validation export followed by a sanitization service and CDN support" data-listing-filename-sort="20230527-server-side-content-validation.md">
 <td>
 <a href="./decisions/20230527-server-side-content-validation.html" class="title listing-title">Proposed: Implement server-side content validation export followed by a sanitization service and CDN support</a>
 </td>
@@ -2830,7 +2830,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230527-server-side-content-validation.html" class="filename listing-filename">20230527-server-side-content-validation.md</a>
 </td>
 </tr>
-<tr data-index="236" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="3" data-listing-word-count-sort="518" data-listing-title-sort="Proposed: Generating Random Text Data for testing V-Sekai systems" data-listing-filename-sort="20230527-server-performance-test.md">
+<tr data-index="236" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="3" data-listing-word-count-sort="518" data-listing-title-sort="Proposed: Generating Random Text Data for testing V-Sekai systems" data-listing-filename-sort="20230527-server-performance-test.md">
 <td>
 <a href="./decisions/20230527-server-performance-test.html" class="title listing-title">Proposed: Generating Random Text Data for testing V-Sekai systems</a>
 </td>
@@ -2841,7 +2841,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230527-server-performance-test.html" class="filename listing-filename">20230527-server-performance-test.md</a>
 </td>
 </tr>
-<tr data-index="237" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="2" data-listing-word-count-sort="284" data-listing-title-sort="Proposed: Handling access to session based game data" data-listing-filename-sort="20230527-server-cdn-session-url.md">
+<tr data-index="237" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="2" data-listing-word-count-sort="284" data-listing-title-sort="Proposed: Handling access to session based game data" data-listing-filename-sort="20230527-server-cdn-session-url.md">
 <td>
 <a href="./decisions/20230527-server-cdn-session-url.html" class="title listing-title">Proposed: Handling access to session based game data</a>
 </td>
@@ -2852,7 +2852,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230527-server-cdn-session-url.html" class="filename listing-filename">20230527-server-cdn-session-url.md</a>
 </td>
 </tr>
-<tr data-index="238" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="2" data-listing-word-count-sort="347" data-listing-title-sort="Draft: Finding ways to attract users, developers, and creators sustaining V-Sekai" data-listing-filename-sort="20230527-organization.md">
+<tr data-index="238" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="2" data-listing-word-count-sort="347" data-listing-title-sort="Draft: Finding ways to attract users, developers, and creators sustaining V-Sekai" data-listing-filename-sort="20230527-organization.md">
 <td>
 <a href="./decisions/20230527-organization.html" class="title listing-title">Draft: Finding ways to attract users, developers, and creators sustaining V-Sekai</a>
 </td>
@@ -2863,7 +2863,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230527-organization.html" class="filename listing-filename">20230527-organization.md</a>
 </td>
 </tr>
-<tr data-index="239" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="1" data-listing-word-count-sort="144" data-listing-title-sort="Proposed: Create a 12x12 meter 3D demo map with 2-meter-high obstacles and walls" data-listing-filename-sort="20230527-godot-test-game.md">
+<tr data-index="239" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="1" data-listing-word-count-sort="144" data-listing-title-sort="Proposed: Create a 12x12 meter 3D demo map with 2-meter-high obstacles and walls" data-listing-filename-sort="20230527-godot-test-game.md">
 <td>
 <a href="./decisions/20230527-godot-test-game.html" class="title listing-title">Proposed: Create a 12x12 meter 3D demo map with 2-meter-high obstacles and walls</a>
 </td>
@@ -2874,7 +2874,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230527-godot-test-game.html" class="filename listing-filename">20230527-godot-test-game.md</a>
 </td>
 </tr>
-<tr data-index="240" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="3" data-listing-word-count-sort="512" data-listing-title-sort="Proposed: Convert IK solvers to be using the AnimationTree" data-listing-filename-sort="20230525-animation-ik-node.md">
+<tr data-index="240" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="3" data-listing-word-count-sort="512" data-listing-title-sort="Proposed: Convert IK solvers to be using the AnimationTree" data-listing-filename-sort="20230525-animation-ik-node.md">
 <td>
 <a href="./decisions/20230525-animation-ik-node.html" class="title listing-title">Proposed: Convert IK solvers to be using the AnimationTree</a>
 </td>
@@ -2885,7 +2885,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230525-animation-ik-node.html" class="filename listing-filename">20230525-animation-ik-node.md</a>
 </td>
 </tr>
-<tr data-index="241" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="2" data-listing-word-count-sort="369" data-listing-title-sort="Draft: Improve V-Sekai marketing" data-listing-filename-sort="20230523-marketing-cycle.md">
+<tr data-index="241" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="2" data-listing-word-count-sort="369" data-listing-title-sort="Draft: Improve V-Sekai marketing" data-listing-filename-sort="20230523-marketing-cycle.md">
 <td>
 <a href="./decisions/20230523-marketing-cycle.html" class="title listing-title">Draft: Improve V-Sekai marketing</a>
 </td>
@@ -2896,7 +2896,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230523-marketing-cycle.html" class="filename listing-filename">20230523-marketing-cycle.md</a>
 </td>
 </tr>
-<tr data-index="242" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="1" data-listing-word-count-sort="158" data-listing-title-sort="Rejected: Defeating your fictional enemies in their blood" data-listing-filename-sort="20230522-JOKE-fictional-blood-combat.md">
+<tr data-index="242" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="1" data-listing-word-count-sort="158" data-listing-title-sort="Rejected: Defeating your fictional enemies in their blood" data-listing-filename-sort="20230522-JOKE-fictional-blood-combat.md">
 <td>
 <a href="./decisions/20230522-JOKE-fictional-blood-combat.html" class="title listing-title">Rejected: Defeating your fictional enemies in their blood</a>
 </td>
@@ -2907,7 +2907,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230522-JOKE-fictional-blood-combat.html" class="filename listing-filename">20230522-JOKE-fictional-blood-combat.md</a>
 </td>
 </tr>
-<tr data-index="243" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="2" data-listing-word-count-sort="294" data-listing-title-sort="Proposed: Improving Jitter-Buffer Implementation for Voice Chat in V-Sekai Projects" data-listing-filename-sort="20230521-audio-jitter-buffer-voip.md">
+<tr data-index="243" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="2" data-listing-word-count-sort="294" data-listing-title-sort="Proposed: Improving Jitter-Buffer Implementation for Voice Chat in V-Sekai Projects" data-listing-filename-sort="20230521-audio-jitter-buffer-voip.md">
 <td>
 <a href="./decisions/20230521-audio-jitter-buffer-voip.html" class="title listing-title">Proposed: Improving Jitter-Buffer Implementation for Voice Chat in V-Sekai Projects</a>
 </td>
@@ -2918,7 +2918,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230521-audio-jitter-buffer-voip.html" class="filename listing-filename">20230521-audio-jitter-buffer-voip.md</a>
 </td>
 </tr>
-<tr data-index="244" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="2" data-listing-word-count-sort="250" data-listing-title-sort="Superseded: V-Sekai Roadmap and Goals 2023-05-19" data-listing-filename-sort="20230519-v-sekai-roadmap.md">
+<tr data-index="244" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="2" data-listing-word-count-sort="250" data-listing-title-sort="Superseded: V-Sekai Roadmap and Goals 2023-05-19" data-listing-filename-sort="20230519-v-sekai-roadmap.md">
 <td>
 <a href="./decisions/20230519-v-sekai-roadmap.html" class="title listing-title">Superseded: V-Sekai Roadmap and Goals 2023-05-19</a>
 </td>
@@ -2929,7 +2929,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230519-v-sekai-roadmap.html" class="filename listing-filename">20230519-v-sekai-roadmap.md</a>
 </td>
 </tr>
-<tr data-index="245" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="3" data-listing-word-count-sort="425" data-listing-title-sort="Proposed: Add VRM portable avatars and OMI_personality to the GLTF Transform tool" data-listing-filename-sort="20230519-add-vrm-omi-personality-gltf-extension.md">
+<tr data-index="245" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="3" data-listing-word-count-sort="425" data-listing-title-sort="Proposed: Add VRM portable avatars and OMI_personality to the GLTF Transform tool" data-listing-filename-sort="20230519-add-vrm-omi-personality-gltf-extension.md">
 <td>
 <a href="./decisions/20230519-add-vrm-omi-personality-gltf-extension.html" class="title listing-title">Proposed: Add VRM portable avatars and OMI_personality to the GLTF Transform tool</a>
 </td>
@@ -2940,7 +2940,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230519-add-vrm-omi-personality-gltf-extension.html" class="filename listing-filename">20230519-add-vrm-omi-personality-gltf-extension.md</a>
 </td>
 </tr>
-<tr data-index="246" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="2" data-listing-word-count-sort="268" data-listing-title-sort="Superseded: V-Sekai Roadmap and Goals 2023-05-16" data-listing-filename-sort="20230516-v-sekai-roadmap.md">
+<tr data-index="246" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="2" data-listing-word-count-sort="268" data-listing-title-sort="Superseded: V-Sekai Roadmap and Goals 2023-05-16" data-listing-filename-sort="20230516-v-sekai-roadmap.md">
 <td>
 <a href="./decisions/20230516-v-sekai-roadmap.html" class="title listing-title">Superseded: V-Sekai Roadmap and Goals 2023-05-16</a>
 </td>
@@ -2951,7 +2951,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230516-v-sekai-roadmap.html" class="filename listing-filename">20230516-v-sekai-roadmap.md</a>
 </td>
 </tr>
-<tr data-index="247" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="2" data-listing-word-count-sort="294" data-listing-title-sort="Accepted: Aquarium Nightclub Booth for Virtual Market Exhibition" data-listing-filename-sort="20230516-create-an-aquarium-nightclub-booth-for-virtual-market.md">
+<tr data-index="247" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="2" data-listing-word-count-sort="294" data-listing-title-sort="Accepted: Aquarium Nightclub Booth for Virtual Market Exhibition" data-listing-filename-sort="20230516-create-an-aquarium-nightclub-booth-for-virtual-market.md">
 <td>
 <a href="./decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html" class="title listing-title">Accepted: Aquarium Nightclub Booth for Virtual Market Exhibition</a>
 </td>
@@ -2962,7 +2962,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html" class="filename listing-filename">20230516-create-an-aquarium-nightclub-booth-for-virtual-market.md</a>
 </td>
 </tr>
-<tr data-index="248" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="3" data-listing-word-count-sort="447" data-listing-title-sort="Rejected: Additional 3D Import Functionality" data-listing-filename-sort="20230516-additional-3d-import.md">
+<tr data-index="248" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="3" data-listing-word-count-sort="447" data-listing-title-sort="Rejected: Additional 3D Import Functionality" data-listing-filename-sort="20230516-additional-3d-import.md">
 <td>
 <a href="./decisions/20230516-additional-3d-import.html" class="title listing-title">Rejected: Additional 3D Import Functionality</a>
 </td>
@@ -2973,7 +2973,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230516-additional-3d-import.html" class="filename listing-filename">20230516-additional-3d-import.md</a>
 </td>
 </tr>
-<tr data-index="249" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="2" data-listing-word-count-sort="261" data-listing-title-sort="Draft: Exchange data between Godot Engine and WASM using handles" data-listing-filename-sort="20230509-wasm-data-exchange.md">
+<tr data-index="249" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="2" data-listing-word-count-sort="261" data-listing-title-sort="Draft: Exchange data between Godot Engine and WASM using handles" data-listing-filename-sort="20230509-wasm-data-exchange.md">
 <td>
 <a href="./decisions/20230509-wasm-data-exchange.html" class="title listing-title">Draft: Exchange data between Godot Engine and WASM using handles</a>
 </td>
@@ -2984,7 +2984,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230509-wasm-data-exchange.html" class="filename listing-filename">20230509-wasm-data-exchange.md</a>
 </td>
 </tr>
-<tr data-index="250" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="2" data-listing-word-count-sort="347" data-listing-title-sort="Draft: Convert segmented front facing 3D Garment images to novel 3d views for 3d modeling" data-listing-filename-sort="20230508-novel-3d-views.md">
+<tr data-index="250" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="2" data-listing-word-count-sort="347" data-listing-title-sort="Draft: Convert segmented front facing 3D Garment images to novel 3d views for 3d modeling" data-listing-filename-sort="20230508-novel-3d-views.md">
 <td>
 <a href="./decisions/20230508-novel-3d-views.html" class="title listing-title">Draft: Convert segmented front facing 3D Garment images to novel 3d views for 3d modeling</a>
 </td>
@@ -2995,7 +2995,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230508-novel-3d-views.html" class="filename listing-filename">20230508-novel-3d-views.md</a>
 </td>
 </tr>
-<tr data-index="251" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="2" data-listing-word-count-sort="330" data-listing-title-sort="Rejected: Using Deno to handle the conversion of GLB files to Godot Engine packed scenes" data-listing-filename-sort="20230507-supabase.md">
+<tr data-index="251" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="2" data-listing-word-count-sort="330" data-listing-title-sort="Rejected: Using Deno to handle the conversion of GLB files to Godot Engine packed scenes" data-listing-filename-sort="20230507-supabase.md">
 <td>
 <a href="./decisions/20230507-supabase.html" class="title listing-title">Rejected: Using Deno to handle the conversion of GLB files to Godot Engine packed scenes</a>
 </td>
@@ -3006,7 +3006,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230507-supabase.html" class="filename listing-filename">20230507-supabase.md</a>
 </td>
 </tr>
-<tr data-index="252" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="17" data-listing-word-count-sort="3248" data-listing-title-sort="Rejected: Distributed simulation" data-listing-filename-sort="20230507-distributed-sim.md">
+<tr data-index="252" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="17" data-listing-word-count-sort="3248" data-listing-title-sort="Rejected: Distributed simulation" data-listing-filename-sort="20230507-distributed-sim.md">
 <td>
 <a href="./decisions/20230507-distributed-sim.html" class="title listing-title">Rejected: Distributed simulation</a>
 </td>
@@ -3017,7 +3017,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230507-distributed-sim.html" class="filename listing-filename">20230507-distributed-sim.md</a>
 </td>
 </tr>
-<tr data-index="253" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="2" data-listing-word-count-sort="388" data-listing-title-sort="Draft: Describe a avatar publishing workflow for portability" data-listing-filename-sort="20230507-avatar-publishing-workflow-portability.md">
+<tr data-index="253" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="2" data-listing-word-count-sort="388" data-listing-title-sort="Draft: Describe a avatar publishing workflow for portability" data-listing-filename-sort="20230507-avatar-publishing-workflow-portability.md">
 <td>
 <a href="./decisions/20230507-avatar-publishing-workflow-portability.html" class="title listing-title">Draft: Describe a avatar publishing workflow for portability</a>
 </td>
@@ -3028,7 +3028,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230507-avatar-publishing-workflow-portability.html" class="filename listing-filename">20230507-avatar-publishing-workflow-portability.md</a>
 </td>
 </tr>
-<tr data-index="254" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="3" data-listing-word-count-sort="448" data-listing-title-sort="Superseded: Solve V-Sekai limitations using ChatGPT-4 AI completion." data-listing-filename-sort="20230505-v-sekai-ai-completion.md">
+<tr data-index="254" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="3" data-listing-word-count-sort="448" data-listing-title-sort="Superseded: Solve V-Sekai limitations using ChatGPT-4 AI completion." data-listing-filename-sort="20230505-v-sekai-ai-completion.md">
 <td>
 <a href="./decisions/20230505-v-sekai-ai-completion.html" class="title listing-title">Superseded: Solve V-Sekai limitations using ChatGPT-4 AI completion.</a>
 </td>
@@ -3039,7 +3039,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230505-v-sekai-ai-completion.html" class="filename listing-filename">20230505-v-sekai-ai-completion.md</a>
 </td>
 </tr>
-<tr data-index="255" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="2" data-listing-word-count-sort="382" data-listing-title-sort="Proposed: VR design application for V-Sekai" data-listing-filename-sort="20230505-polygon-mesh-based-sculpting-tools.md">
+<tr data-index="255" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="2" data-listing-word-count-sort="382" data-listing-title-sort="Proposed: VR design application for V-Sekai" data-listing-filename-sort="20230505-polygon-mesh-based-sculpting-tools.md">
 <td>
 <a href="./decisions/20230505-polygon-mesh-based-sculpting-tools.html" class="title listing-title">Proposed: VR design application for V-Sekai</a>
 </td>
@@ -3050,7 +3050,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230505-polygon-mesh-based-sculpting-tools.html" class="filename listing-filename">20230505-polygon-mesh-based-sculpting-tools.md</a>
 </td>
 </tr>
-<tr data-index="256" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="2" data-listing-word-count-sort="256" data-listing-title-sort="Proposed: Enhancing Cross-Platform Compatibility and User Experience for V-Sekai VR Social Players" data-listing-filename-sort="20230505-cross-platform-artwork-distribution.md">
+<tr data-index="256" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="2" data-listing-word-count-sort="256" data-listing-title-sort="Proposed: Enhancing Cross-Platform Compatibility and User Experience for V-Sekai VR Social Players" data-listing-filename-sort="20230505-cross-platform-artwork-distribution.md">
 <td>
 <a href="./decisions/20230505-cross-platform-artwork-distribution.html" class="title listing-title">Proposed: Enhancing Cross-Platform Compatibility and User Experience for V-Sekai VR Social Players</a>
 </td>
@@ -3061,7 +3061,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230505-cross-platform-artwork-distribution.html" class="filename listing-filename">20230505-cross-platform-artwork-distribution.md</a>
 </td>
 </tr>
-<tr data-index="257" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="3" data-listing-word-count-sort="445" data-listing-title-sort="Proposed: Solve a V-Sekai naming convention limitation." data-listing-filename-sort="20230505-consistent-v-sekai-naming.md">
+<tr data-index="257" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="3" data-listing-word-count-sort="445" data-listing-title-sort="Proposed: Solve a V-Sekai naming convention limitation." data-listing-filename-sort="20230505-consistent-v-sekai-naming.md">
 <td>
 <a href="./decisions/20230505-consistent-v-sekai-naming.html" class="title listing-title">Proposed: Solve a V-Sekai naming convention limitation.</a>
 </td>
@@ -3072,7 +3072,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230505-consistent-v-sekai-naming.html" class="filename listing-filename">20230505-consistent-v-sekai-naming.md</a>
 </td>
 </tr>
-<tr data-index="258" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="4" data-listing-word-count-sort="635" data-listing-title-sort="Proposed: Automated avatar garment rigging" data-listing-filename-sort="20230505-automated-avatar-garment-rigging.md">
+<tr data-index="258" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="4" data-listing-word-count-sort="635" data-listing-title-sort="Proposed: Automated avatar garment rigging" data-listing-filename-sort="20230505-automated-avatar-garment-rigging.md">
 <td>
 <a href="./decisions/20230505-automated-avatar-garment-rigging.html" class="title listing-title">Proposed: Automated avatar garment rigging</a>
 </td>
@@ -3083,7 +3083,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230505-automated-avatar-garment-rigging.html" class="filename listing-filename">20230505-automated-avatar-garment-rigging.md</a>
 </td>
 </tr>
-<tr data-index="259" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="3" data-listing-word-count-sort="431" data-listing-title-sort="Accepted: Adding IREE to Godot Engine for Image Superresolution" data-listing-filename-sort="20230502-add-iree-to-godot-engine-for-image-superresolution.md">
+<tr data-index="259" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="3" data-listing-word-count-sort="431" data-listing-title-sort="Accepted: Adding IREE to Godot Engine for Image Superresolution" data-listing-filename-sort="20230502-add-iree-to-godot-engine-for-image-superresolution.md">
 <td>
 <a href="./decisions/20230502-add-iree-to-godot-engine-for-image-superresolution.html" class="title listing-title">Accepted: Adding IREE to Godot Engine for Image Superresolution</a>
 </td>
@@ -3094,7 +3094,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230502-add-iree-to-godot-engine-for-image-superresolution.html" class="filename listing-filename">20230502-add-iree-to-godot-engine-for-image-superresolution.md</a>
 </td>
 </tr>
-<tr data-index="260" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="3" data-listing-word-count-sort="594" data-listing-title-sort="Superseded: V-Sekai Roadmap and Goals 2023-04-20" data-listing-filename-sort="20230429-v-sekai-roadmap.md">
+<tr data-index="260" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="3" data-listing-word-count-sort="594" data-listing-title-sort="Superseded: V-Sekai Roadmap and Goals 2023-04-20" data-listing-filename-sort="20230429-v-sekai-roadmap.md">
 <td>
 <a href="./decisions/20230429-v-sekai-roadmap.html" class="title listing-title">Superseded: V-Sekai Roadmap and Goals 2023-04-20</a>
 </td>
@@ -3105,7 +3105,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230429-v-sekai-roadmap.html" class="filename listing-filename">20230429-v-sekai-roadmap.md</a>
 </td>
 </tr>
-<tr data-index="261" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="3" data-listing-word-count-sort="590" data-listing-title-sort="Proposed: Improve the collaboration process and attract more contributors to work on the project" data-listing-filename-sort="20230429-improve-collab.md">
+<tr data-index="261" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="3" data-listing-word-count-sort="590" data-listing-title-sort="Proposed: Improve the collaboration process and attract more contributors to work on the project" data-listing-filename-sort="20230429-improve-collab.md">
 <td>
 <a href="./decisions/20230429-improve-collab.html" class="title listing-title">Proposed: Improve the collaboration process and attract more contributors to work on the project</a>
 </td>
@@ -3116,7 +3116,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230429-improve-collab.html" class="filename listing-filename">20230429-improve-collab.md</a>
 </td>
 </tr>
-<tr data-index="262" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="2" data-listing-word-count-sort="277" data-listing-title-sort="Accepted: Challenges in managing and synchronizing multiple assets and libraries across different git repositories" data-listing-filename-sort="20230429-git-subrepo-challenges.md">
+<tr data-index="262" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="2" data-listing-word-count-sort="277" data-listing-title-sort="Accepted: Challenges in managing and synchronizing multiple assets and libraries across different git repositories" data-listing-filename-sort="20230429-git-subrepo-challenges.md">
 <td>
 <a href="./decisions/20230429-git-subrepo-challenges.html" class="title listing-title">Accepted: Challenges in managing and synchronizing multiple assets and libraries across different git repositories</a>
 </td>
@@ -3127,7 +3127,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230429-git-subrepo-challenges.html" class="filename listing-filename">20230429-git-subrepo-challenges.md</a>
 </td>
 </tr>
-<tr data-index="263" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="5" data-listing-word-count-sort="985" data-listing-title-sort="Rejected: Package Godot for pkgin" data-listing-filename-sort="20230419-package-godot-for-pkgin.md">
+<tr data-index="263" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="5" data-listing-word-count-sort="985" data-listing-title-sort="Rejected: Package Godot for pkgin" data-listing-filename-sort="20230419-package-godot-for-pkgin.md">
 <td>
 <a href="./decisions/20230419-package-godot-for-pkgin.html" class="title listing-title">Rejected: Package Godot for pkgin</a>
 </td>
@@ -3138,7 +3138,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230419-package-godot-for-pkgin.html" class="filename listing-filename">20230419-package-godot-for-pkgin.md</a>
 </td>
 </tr>
-<tr data-index="264" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="4" data-listing-word-count-sort="676" data-listing-title-sort="Proposed: Capturing accurate body movements with limited tracker placement" data-listing-filename-sort="20230419-limited-tracker-placement.md">
+<tr data-index="264" data-listing-file-modified-sort="1730559023678" data-listing-reading-time-sort="4" data-listing-word-count-sort="676" data-listing-title-sort="Proposed: Capturing accurate body movements with limited tracker placement" data-listing-filename-sort="20230419-limited-tracker-placement.md">
 <td>
 <a href="./decisions/20230419-limited-tracker-placement.html" class="title listing-title">Proposed: Capturing accurate body movements with limited tracker placement</a>
 </td>
@@ -3149,7 +3149,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230419-limited-tracker-placement.html" class="filename listing-filename">20230419-limited-tracker-placement.md</a>
 </td>
 </tr>
-<tr data-index="265" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="3" data-listing-word-count-sort="463" data-listing-title-sort="Proposed: Use godot rgbaf textures to store integers" data-listing-filename-sort="20230415-rgbaf-to-store-integers.md">
+<tr data-index="265" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="3" data-listing-word-count-sort="463" data-listing-title-sort="Proposed: Use godot rgbaf textures to store integers" data-listing-filename-sort="20230415-rgbaf-to-store-integers.md">
 <td>
 <a href="./decisions/20230415-rgbaf-to-store-integers.html" class="title listing-title">Proposed: Use godot rgbaf textures to store integers</a>
 </td>
@@ -3160,7 +3160,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230415-rgbaf-to-store-integers.html" class="filename listing-filename">20230415-rgbaf-to-store-integers.md</a>
 </td>
 </tr>
-<tr data-index="266" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="3" data-listing-word-count-sort="489" data-listing-title-sort="Proposed: Procedurally create variations for our props, environments and avatars" data-listing-filename-sort="20230415-procedural-variations-props-envs-avatars.md">
+<tr data-index="266" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="3" data-listing-word-count-sort="489" data-listing-title-sort="Proposed: Procedurally create variations for our props, environments and avatars" data-listing-filename-sort="20230415-procedural-variations-props-envs-avatars.md">
 <td>
 <a href="./decisions/20230415-procedural-variations-props-envs-avatars.html" class="title listing-title">Proposed: Procedurally create variations for our props, environments and avatars</a>
 </td>
@@ -3171,7 +3171,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230415-procedural-variations-props-envs-avatars.html" class="filename listing-filename">20230415-procedural-variations-props-envs-avatars.md</a>
 </td>
 </tr>
-<tr data-index="267" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="2" data-listing-word-count-sort="317" data-listing-title-sort="Proposed: Hit a collaborate button to load up into V-Sekai" data-listing-filename-sort="20230415-load-collaborate.md">
+<tr data-index="267" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="317" data-listing-title-sort="Proposed: Hit a collaborate button to load up into V-Sekai" data-listing-filename-sort="20230415-load-collaborate.md">
 <td>
 <a href="./decisions/20230415-load-collaborate.html" class="title listing-title">Proposed: Hit a collaborate button to load up into V-Sekai</a>
 </td>
@@ -3182,7 +3182,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230415-load-collaborate.html" class="filename listing-filename">20230415-load-collaborate.md</a>
 </td>
 </tr>
-<tr data-index="268" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="1" data-listing-word-count-sort="174" data-listing-title-sort="Proposed: Provide v-sekai-game in a launcher to make it easier to use v-sekai" data-listing-filename-sort="20230408-v-sekai-launcher.md">
+<tr data-index="268" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="1" data-listing-word-count-sort="174" data-listing-title-sort="Proposed: Provide v-sekai-game in a launcher to make it easier to use v-sekai" data-listing-filename-sort="20230408-v-sekai-launcher.md">
 <td>
 <a href="./decisions/20230408-v-sekai-launcher.html" class="title listing-title">Proposed: Provide v-sekai-game in a launcher to make it easier to use v-sekai</a>
 </td>
@@ -3193,7 +3193,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230408-v-sekai-launcher.html" class="filename listing-filename">20230408-v-sekai-launcher.md</a>
 </td>
 </tr>
-<tr data-index="269" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="1" data-listing-word-count-sort="199" data-listing-title-sort="Proposed: Use junit xml based tests in github" data-listing-filename-sort="20230310-xml-based-tests.md">
+<tr data-index="269" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="1" data-listing-word-count-sort="199" data-listing-title-sort="Proposed: Use junit xml based tests in github" data-listing-filename-sort="20230310-xml-based-tests.md">
 <td>
 <a href="./decisions/20230310-xml-based-tests.html" class="title listing-title">Proposed: Use junit xml based tests in github</a>
 </td>
@@ -3204,7 +3204,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230310-xml-based-tests.html" class="filename listing-filename">20230310-xml-based-tests.md</a>
 </td>
 </tr>
-<tr data-index="270" data-listing-file-modified-sort="1730535490030" data-listing-reading-time-sort="1" data-listing-word-count-sort="37" data-listing-title-sort="Proposed: Don't merge incomplete work." data-listing-filename-sort="20230310-don't-merge-incomplete-work.md">
+<tr data-index="270" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="1" data-listing-word-count-sort="37" data-listing-title-sort="Proposed: Don't merge incomplete work." data-listing-filename-sort="20230310-don't-merge-incomplete-work.md">
 <td>
 <a href="./decisions/20230310-don't-merge-incomplete-work.html" class="title listing-title">Proposed: Don’t merge incomplete work.</a>
 </td>
@@ -3215,7 +3215,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230310-don't-merge-incomplete-work.html" class="filename listing-filename">20230310-don’t-merge-incomplete-work.md</a>
 </td>
 </tr>
-<tr data-index="271" data-listing-file-modified-sort="1730535490026" data-listing-reading-time-sort="2" data-listing-word-count-sort="338" data-listing-title-sort="Superseded: Creating a Godot Engine C++ module with IREE backend for machine learning computations using Vulkan and CUDA" data-listing-filename-sort="20230310-IREE-backend-for-machine-learning-computations.md">
+<tr data-index="271" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="338" data-listing-title-sort="Superseded: Creating a Godot Engine C++ module with IREE backend for machine learning computations using Vulkan and CUDA" data-listing-filename-sort="20230310-IREE-backend-for-machine-learning-computations.md">
 <td>
 <a href="./decisions/20230310-IREE-backend-for-machine-learning-computations.html" class="title listing-title">Superseded: Creating a Godot Engine C++ module with IREE backend for machine learning computations using Vulkan and CUDA</a>
 </td>
@@ -3226,7 +3226,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230310-IREE-backend-for-machine-learning-computations.html" class="filename listing-filename">20230310-IREE-backend-for-machine-learning-computations.md</a>
 </td>
 </tr>
-<tr data-index="272" data-listing-file-modified-sort="1730535490026" data-listing-reading-time-sort="2" data-listing-word-count-sort="285" data-listing-title-sort="Accepted: Meet at GDC SF 2023" data-listing-filename-sort="20230131-meeting-at-gdc-2023.md">
+<tr data-index="272" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="285" data-listing-title-sort="Accepted: Meet at GDC SF 2023" data-listing-filename-sort="20230131-meeting-at-gdc-2023.md">
 <td>
 <a href="./decisions/20230131-meeting-at-gdc-2023.html" class="title listing-title">Accepted: Meet at GDC SF 2023</a>
 </td>
@@ -3237,7 +3237,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230131-meeting-at-gdc-2023.html" class="filename listing-filename">20230131-meeting-at-gdc-2023.md</a>
 </td>
 </tr>
-<tr data-index="273" data-listing-file-modified-sort="1730535490026" data-listing-reading-time-sort="2" data-listing-word-count-sort="374" data-listing-title-sort="Accepted: Default test plan for testing V-Sekai engine upgrades." data-listing-filename-sort="20230131-default-test-plan.md">
+<tr data-index="273" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="374" data-listing-title-sort="Accepted: Default test plan for testing V-Sekai engine upgrades." data-listing-filename-sort="20230131-default-test-plan.md">
 <td>
 <a href="./decisions/20230131-default-test-plan.html" class="title listing-title">Accepted: Default test plan for testing V-Sekai engine upgrades.</a>
 </td>
@@ -3248,7 +3248,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230131-default-test-plan.html" class="filename listing-filename">20230131-default-test-plan.md</a>
 </td>
 </tr>
-<tr data-index="274" data-listing-file-modified-sort="1730535490026" data-listing-reading-time-sort="2" data-listing-word-count-sort="297" data-listing-title-sort="Proposed: Adopt best practices for product development" data-listing-filename-sort="20230131-adopt-best-product-development-practices.md">
+<tr data-index="274" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="297" data-listing-title-sort="Proposed: Adopt best practices for product development" data-listing-filename-sort="20230131-adopt-best-product-development-practices.md">
 <td>
 <a href="./decisions/20230131-adopt-best-product-development-practices.html" class="title listing-title">Proposed: Adopt best practices for product development</a>
 </td>
@@ -3259,7 +3259,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230131-adopt-best-product-development-practices.html" class="filename listing-filename">20230131-adopt-best-product-development-practices.md</a>
 </td>
 </tr>
-<tr data-index="275" data-listing-file-modified-sort="1730535490026" data-listing-reading-time-sort="2" data-listing-word-count-sort="340" data-listing-title-sort="Proposed: Without visualization, we cannot easily compare the interpolation states" data-listing-filename-sort="20230125-without-viz-we-cannot-compare-the-interpolation.md">
+<tr data-index="275" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="340" data-listing-title-sort="Proposed: Without visualization, we cannot easily compare the interpolation states" data-listing-filename-sort="20230125-without-viz-we-cannot-compare-the-interpolation.md">
 <td>
 <a href="./decisions/20230125-without-viz-we-cannot-compare-the-interpolation.html" class="title listing-title">Proposed: Without visualization, we cannot easily compare the interpolation states</a>
 </td>
@@ -3270,7 +3270,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230125-without-viz-we-cannot-compare-the-interpolation.html" class="filename listing-filename">20230125-without-viz-we-cannot-compare-the-interpolation.md</a>
 </td>
 </tr>
-<tr data-index="276" data-listing-file-modified-sort="1730535490026" data-listing-reading-time-sort="2" data-listing-word-count-sort="276" data-listing-title-sort="Proposed: Provide user generated scripting with libsql and wasm" data-listing-filename-sort="20230125-user-generated-scripting-with-libsql-and-wasm.md">
+<tr data-index="276" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="276" data-listing-title-sort="Proposed: Provide user generated scripting with libsql and wasm" data-listing-filename-sort="20230125-user-generated-scripting-with-libsql-and-wasm.md">
 <td>
 <a href="./decisions/20230125-user-generated-scripting-with-libsql-and-wasm.html" class="title listing-title">Proposed: Provide user generated scripting with libsql and wasm</a>
 </td>
@@ -3281,7 +3281,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230125-user-generated-scripting-with-libsql-and-wasm.html" class="filename listing-filename">20230125-user-generated-scripting-with-libsql-and-wasm.md</a>
 </td>
 </tr>
-<tr data-index="277" data-listing-file-modified-sort="1730535490026" data-listing-reading-time-sort="2" data-listing-word-count-sort="216" data-listing-title-sort="Proposed: Have two groups move towards each other battle demo" data-listing-filename-sort="20230125-two-groups-battle-demo.md">
+<tr data-index="277" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="216" data-listing-title-sort="Proposed: Have two groups move towards each other battle demo" data-listing-filename-sort="20230125-two-groups-battle-demo.md">
 <td>
 <a href="./decisions/20230125-two-groups-battle-demo.html" class="title listing-title">Proposed: Have two groups move towards each other battle demo</a>
 </td>
@@ -3292,7 +3292,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230125-two-groups-battle-demo.html" class="filename listing-filename">20230125-two-groups-battle-demo.md</a>
 </td>
 </tr>
-<tr data-index="278" data-listing-file-modified-sort="1730535490026" data-listing-reading-time-sort="1" data-listing-word-count-sort="193" data-listing-title-sort="Proposed: Provide metadata to pre-check if maps and avatars are compatible to load" data-listing-filename-sort="20230125-provide-metadata-to-match-compatibile-maps-and-avatars.md">
+<tr data-index="278" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="1" data-listing-word-count-sort="193" data-listing-title-sort="Proposed: Provide metadata to pre-check if maps and avatars are compatible to load" data-listing-filename-sort="20230125-provide-metadata-to-match-compatibile-maps-and-avatars.md">
 <td>
 <a href="./decisions/20230125-provide-metadata-to-match-compatibile-maps-and-avatars.html" class="title listing-title">Proposed: Provide metadata to pre-check if maps and avatars are compatible to load</a>
 </td>
@@ -3303,7 +3303,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230125-provide-metadata-to-match-compatibile-maps-and-avatars.html" class="filename listing-filename">20230125-provide-metadata-to-match-compatibile-maps-and-avatars.md</a>
 </td>
 </tr>
-<tr data-index="279" data-listing-file-modified-sort="1730535490026" data-listing-reading-time-sort="2" data-listing-word-count-sort="322" data-listing-title-sort="Proposed: Possible futures" data-listing-filename-sort="20230125-possible-futures.md">
+<tr data-index="279" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="322" data-listing-title-sort="Proposed: Possible futures" data-listing-filename-sort="20230125-possible-futures.md">
 <td>
 <a href="./decisions/20230125-possible-futures.html" class="title listing-title">Proposed: Possible futures</a>
 </td>
@@ -3314,7 +3314,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230125-possible-futures.html" class="filename listing-filename">20230125-possible-futures.md</a>
 </td>
 </tr>
-<tr data-index="280" data-listing-file-modified-sort="1730535490026" data-listing-reading-time-sort="2" data-listing-word-count-sort="218" data-listing-title-sort="Proposed: Grow the community with a reactive Discord bot." data-listing-filename-sort="20230125-grow-the-community-with-a-reactive-discord-bot.md">
+<tr data-index="280" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="218" data-listing-title-sort="Proposed: Grow the community with a reactive Discord bot." data-listing-filename-sort="20230125-grow-the-community-with-a-reactive-discord-bot.md">
 <td>
 <a href="./decisions/20230125-grow-the-community-with-a-reactive-discord-bot.html" class="title listing-title">Proposed: Grow the community with a reactive Discord bot.</a>
 </td>
@@ -3325,7 +3325,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230125-grow-the-community-with-a-reactive-discord-bot.html" class="filename listing-filename">20230125-grow-the-community-with-a-reactive-discord-bot.md</a>
 </td>
 </tr>
-<tr data-index="281" data-listing-file-modified-sort="1730535490026" data-listing-reading-time-sort="1" data-listing-word-count-sort="183" data-listing-title-sort="Proposed: Create an in-game tablet interface we can activate" data-listing-filename-sort="20230125-create-an-in-game-tablet-interface-we-can-activate.md">
+<tr data-index="281" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="1" data-listing-word-count-sort="183" data-listing-title-sort="Proposed: Create an in-game tablet interface we can activate" data-listing-filename-sort="20230125-create-an-in-game-tablet-interface-we-can-activate.md">
 <td>
 <a href="./decisions/20230125-create-an-in-game-tablet-interface-we-can-activate.html" class="title listing-title">Proposed: Create an in-game tablet interface we can activate</a>
 </td>
@@ -3336,7 +3336,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230125-create-an-in-game-tablet-interface-we-can-activate.html" class="filename listing-filename">20230125-create-an-in-game-tablet-interface-we-can-activate.md</a>
 </td>
 </tr>
-<tr data-index="282" data-listing-file-modified-sort="1730535490026" data-listing-reading-time-sort="1" data-listing-word-count-sort="180" data-listing-title-sort="Proposed: Cover 80% to 95% of the player base." data-listing-filename-sort="20230125-cover-80-95-percent-of-the-userbase.md">
+<tr data-index="282" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="1" data-listing-word-count-sort="180" data-listing-title-sort="Proposed: Cover 80% to 95% of the player base." data-listing-filename-sort="20230125-cover-80-95-percent-of-the-userbase.md">
 <td>
 <a href="./decisions/20230125-cover-80-95-percent-of-the-userbase.html" class="title listing-title">Proposed: Cover 80% to 95% of the player base.</a>
 </td>
@@ -3347,7 +3347,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230125-cover-80-95-percent-of-the-userbase.html" class="filename listing-filename">20230125-cover-80-95-percent-of-the-userbase.md</a>
 </td>
 </tr>
-<tr data-index="283" data-listing-file-modified-sort="1730535490026" data-listing-reading-time-sort="1" data-listing-word-count-sort="177" data-listing-title-sort="Proposed: Use Easy Charts for observability" data-listing-filename-sort="20230123-use-easy-charts-for-observability.md">
+<tr data-index="283" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="1" data-listing-word-count-sort="177" data-listing-title-sort="Proposed: Use Easy Charts for observability" data-listing-filename-sort="20230123-use-easy-charts-for-observability.md">
 <td>
 <a href="./decisions/20230123-use-easy-charts-for-observability.html" class="title listing-title">Proposed: Use Easy Charts for observability</a>
 </td>
@@ -3358,7 +3358,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230123-use-easy-charts-for-observability.html" class="filename listing-filename">20230123-use-easy-charts-for-observability.md</a>
 </td>
 </tr>
-<tr data-index="284" data-listing-file-modified-sort="1730535490026" data-listing-reading-time-sort="2" data-listing-word-count-sort="323" data-listing-title-sort="Proposed: Recording demo checklist" data-listing-filename-sort="20230123-recording-demo-checklist.md">
+<tr data-index="284" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="323" data-listing-title-sort="Proposed: Recording demo checklist" data-listing-filename-sort="20230123-recording-demo-checklist.md">
 <td>
 <a href="./decisions/20230123-recording-demo-checklist.html" class="title listing-title">Proposed: Recording demo checklist</a>
 </td>
@@ -3369,7 +3369,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230123-recording-demo-checklist.html" class="filename listing-filename">20230123-recording-demo-checklist.md</a>
 </td>
 </tr>
-<tr data-index="285" data-listing-file-modified-sort="1730535490026" data-listing-reading-time-sort="2" data-listing-word-count-sort="299" data-listing-title-sort="Proposed: Ready net demo" data-listing-filename-sort="20230123-ready-the-net-demo.md">
+<tr data-index="285" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="299" data-listing-title-sort="Proposed: Ready net demo" data-listing-filename-sort="20230123-ready-the-net-demo.md">
 <td>
 <a href="./decisions/20230123-ready-the-net-demo.html" class="title listing-title">Proposed: Ready net demo</a>
 </td>
@@ -3380,7 +3380,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230123-ready-the-net-demo.html" class="filename listing-filename">20230123-ready-the-net-demo.md</a>
 </td>
 </tr>
-<tr data-index="286" data-listing-file-modified-sort="1730535490026" data-listing-reading-time-sort="2" data-listing-word-count-sort="379" data-listing-title-sort="Proposed: Publish Godot VRM for Godot 4 for production use" data-listing-filename-sort="20230123-publish-godot-vrm-4.md">
+<tr data-index="286" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="379" data-listing-title-sort="Proposed: Publish Godot VRM for Godot 4 for production use" data-listing-filename-sort="20230123-publish-godot-vrm-4.md">
 <td>
 <a href="./decisions/20230123-publish-godot-vrm-4.html" class="title listing-title">Proposed: Publish Godot VRM for Godot 4 for production use</a>
 </td>
@@ -3391,7 +3391,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230123-publish-godot-vrm-4.html" class="filename listing-filename">20230123-publish-godot-vrm-4.md</a>
 </td>
 </tr>
-<tr data-index="287" data-listing-file-modified-sort="1730535490026" data-listing-reading-time-sort="2" data-listing-word-count-sort="344" data-listing-title-sort="Proposed: Provide user generated scripting using WasGO" data-listing-filename-sort="20230123-player-scripting.md">
+<tr data-index="287" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="344" data-listing-title-sort="Proposed: Provide user generated scripting using WasGO" data-listing-filename-sort="20230123-player-scripting.md">
 <td>
 <a href="./decisions/20230123-player-scripting.html" class="title listing-title">Proposed: Provide user generated scripting using WasGO</a>
 </td>
@@ -3402,7 +3402,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230123-player-scripting.html" class="filename listing-filename">20230123-player-scripting.md</a>
 </td>
 </tr>
-<tr data-index="288" data-listing-file-modified-sort="1730535490026" data-listing-reading-time-sort="4" data-listing-word-count-sort="610" data-listing-title-sort="Proposed: No traversal loading screen" data-listing-filename-sort="20230123-no-traversal-loading-screen.md">
+<tr data-index="288" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="4" data-listing-word-count-sort="610" data-listing-title-sort="Proposed: No traversal loading screen" data-listing-filename-sort="20230123-no-traversal-loading-screen.md">
 <td>
 <a href="./decisions/20230123-no-traversal-loading-screen.html" class="title listing-title">Proposed: No traversal loading screen</a>
 </td>
@@ -3413,7 +3413,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230123-no-traversal-loading-screen.html" class="filename listing-filename">20230123-no-traversal-loading-screen.md</a>
 </td>
 </tr>
-<tr data-index="289" data-listing-file-modified-sort="1730535490026" data-listing-reading-time-sort="2" data-listing-word-count-sort="318" data-listing-title-sort="Proposed: Better Godot Engine integration with Blender with gltf extensions" data-listing-filename-sort="20230123-integrate-blender-with-gltf-extensions-and-godot.md">
+<tr data-index="289" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="318" data-listing-title-sort="Proposed: Better Godot Engine integration with Blender with gltf extensions" data-listing-filename-sort="20230123-integrate-blender-with-gltf-extensions-and-godot.md">
 <td>
 <a href="./decisions/20230123-integrate-blender-with-gltf-extensions-and-godot.html" class="title listing-title">Proposed: Better Godot Engine integration with Blender with gltf extensions</a>
 </td>
@@ -3424,7 +3424,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230123-integrate-blender-with-gltf-extensions-and-godot.html" class="filename listing-filename">20230123-integrate-blender-with-gltf-extensions-and-godot.md</a>
 </td>
 </tr>
-<tr data-index="290" data-listing-file-modified-sort="1730535490026" data-listing-reading-time-sort="2" data-listing-word-count-sort="301" data-listing-title-sort="Proposed: Face helmet capture" data-listing-filename-sort="20230123-face-helmet-capture.md">
+<tr data-index="290" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="301" data-listing-title-sort="Proposed: Face helmet capture" data-listing-filename-sort="20230123-face-helmet-capture.md">
 <td>
 <a href="./decisions/20230123-face-helmet-capture.html" class="title listing-title">Proposed: Face helmet capture</a>
 </td>
@@ -3435,7 +3435,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230123-face-helmet-capture.html" class="filename listing-filename">20230123-face-helmet-capture.md</a>
 </td>
 </tr>
-<tr data-index="291" data-listing-file-modified-sort="1730535490026" data-listing-reading-time-sort="2" data-listing-word-count-sort="277" data-listing-title-sort="Proposed: Add WMF for windows media playback" data-listing-filename-sort="20230108-wmf-video-playback.md">
+<tr data-index="291" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="277" data-listing-title-sort="Proposed: Add WMF for windows media playback" data-listing-filename-sort="20230108-wmf-video-playback.md">
 <td>
 <a href="./decisions/20230108-wmf-video-playback.html" class="title listing-title">Proposed: Add WMF for windows media playback</a>
 </td>
@@ -3446,7 +3446,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230108-wmf-video-playback.html" class="filename listing-filename">20230108-wmf-video-playback.md</a>
 </td>
 </tr>
-<tr data-index="292" data-listing-file-modified-sort="1730535490026" data-listing-reading-time-sort="3" data-listing-word-count-sort="490" data-listing-title-sort="Accepted: Bolster creating the metaverse" data-listing-filename-sort="20230108-bolster-creating-the-metaverse.md">
+<tr data-index="292" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="3" data-listing-word-count-sort="490" data-listing-title-sort="Accepted: Bolster creating the metaverse" data-listing-filename-sort="20230108-bolster-creating-the-metaverse.md">
 <td>
 <a href="./decisions/20230108-bolster-creating-the-metaverse.html" class="title listing-title">Accepted: Bolster creating the metaverse</a>
 </td>
@@ -3457,7 +3457,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230108-bolster-creating-the-metaverse.html" class="filename listing-filename">20230108-bolster-creating-the-metaverse.md</a>
 </td>
 </tr>
-<tr data-index="293" data-listing-file-modified-sort="1730535490026" data-listing-reading-time-sort="3" data-listing-word-count-sort="520" data-listing-title-sort="Accepted: How to start a EXPERIMENTAL environment for sqlite and elixir?" data-listing-filename-sort="20230107-elixir-uro-dev-sqlite.md">
+<tr data-index="293" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="3" data-listing-word-count-sort="520" data-listing-title-sort="Accepted: How to start a EXPERIMENTAL environment for sqlite and elixir?" data-listing-filename-sort="20230107-elixir-uro-dev-sqlite.md">
 <td>
 <a href="./decisions/20230107-elixir-uro-dev-sqlite.html" class="title listing-title">Accepted: How to start a EXPERIMENTAL environment for sqlite and elixir?</a>
 </td>
@@ -3468,7 +3468,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230107-elixir-uro-dev-sqlite.html" class="filename listing-filename">20230107-elixir-uro-dev-sqlite.md</a>
 </td>
 </tr>
-<tr data-index="294" data-listing-file-modified-sort="1730535490026" data-listing-reading-time-sort="2" data-listing-word-count-sort="361" data-listing-title-sort="Accepted: Separate walking controller from RenIK for ManyBoneIK" data-listing-filename-sort="20230106-walking-controller-renik.md">
+<tr data-index="294" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="361" data-listing-title-sort="Accepted: Separate walking controller from RenIK for ManyBoneIK" data-listing-filename-sort="20230106-walking-controller-renik.md">
 <td>
 <a href="./decisions/20230106-walking-controller-renik.html" class="title listing-title">Accepted: Separate walking controller from RenIK for ManyBoneIK</a>
 </td>
@@ -3479,7 +3479,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20230106-walking-controller-renik.html" class="filename listing-filename">20230106-walking-controller-renik.md</a>
 </td>
 </tr>
-<tr data-index="295" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="348" data-listing-title-sort="Proposed: Powershell autocomplete uses right arrow" data-listing-filename-sort="20221214-powershell-autocomplete-use-right-arrow.md">
+<tr data-index="295" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="348" data-listing-title-sort="Proposed: Powershell autocomplete uses right arrow" data-listing-filename-sort="20221214-powershell-autocomplete-use-right-arrow.md">
 <td>
 <a href="./decisions/20221214-powershell-autocomplete-use-right-arrow.html" class="title listing-title">Proposed: Powershell autocomplete uses right arrow</a>
 </td>
@@ -3490,7 +3490,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20221214-powershell-autocomplete-use-right-arrow.html" class="filename listing-filename">20221214-powershell-autocomplete-use-right-arrow.md</a>
 </td>
 </tr>
-<tr data-index="296" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="3" data-listing-word-count-sort="417" data-listing-title-sort="Proposed: Tools helpful for creating Avatars and Worlds" data-listing-filename-sort="20221212-world-and-character-tools.md">
+<tr data-index="296" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="3" data-listing-word-count-sort="417" data-listing-title-sort="Proposed: Tools helpful for creating Avatars and Worlds" data-listing-filename-sort="20221212-world-and-character-tools.md">
 <td>
 <a href="./decisions/20221212-world-and-character-tools.html" class="title listing-title">Proposed: Tools helpful for creating Avatars and Worlds</a>
 </td>
@@ -3501,7 +3501,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20221212-world-and-character-tools.html" class="filename listing-filename">20221212-world-and-character-tools.md</a>
 </td>
 </tr>
-<tr data-index="297" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="4" data-listing-word-count-sort="631" data-listing-title-sort="Proposed: Prepare godot-vrm for asset library publishing" data-listing-filename-sort="20221206-export-godot-vrm-to-the-asset-library.md">
+<tr data-index="297" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="4" data-listing-word-count-sort="631" data-listing-title-sort="Proposed: Prepare godot-vrm for asset library publishing" data-listing-filename-sort="20221206-export-godot-vrm-to-the-asset-library.md">
 <td>
 <a href="./decisions/20221206-export-godot-vrm-to-the-asset-library.html" class="title listing-title">Proposed: Prepare godot-vrm for asset library publishing</a>
 </td>
@@ -3512,7 +3512,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20221206-export-godot-vrm-to-the-asset-library.html" class="filename listing-filename">20221206-export-godot-vrm-to-the-asset-library.md</a>
 </td>
 </tr>
-<tr data-index="298" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="374" data-listing-title-sort="Proposed: Port RENIK to Many Bone IK for better quality" data-listing-filename-sort="20221205-port-renik-to-many-bone-ik.md">
+<tr data-index="298" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="374" data-listing-title-sort="Proposed: Port RENIK to Many Bone IK for better quality" data-listing-filename-sort="20221205-port-renik-to-many-bone-ik.md">
 <td>
 <a href="./decisions/20221205-port-renik-to-many-bone-ik.html" class="title listing-title">Proposed: Port RENIK to Many Bone IK for better quality</a>
 </td>
@@ -3523,7 +3523,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20221205-port-renik-to-many-bone-ik.html" class="filename listing-filename">20221205-port-renik-to-many-bone-ik.md</a>
 </td>
 </tr>
-<tr data-index="299" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="363" data-listing-title-sort="Proposed: Move fast without breaking things for V-Sekai" data-listing-filename-sort="20221205-moving-fast-philosophy-development.md">
+<tr data-index="299" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="363" data-listing-title-sort="Proposed: Move fast without breaking things for V-Sekai" data-listing-filename-sort="20221205-moving-fast-philosophy-development.md">
 <td>
 <a href="./decisions/20221205-moving-fast-philosophy-development.html" class="title listing-title">Proposed: Move fast without breaking things for V-Sekai</a>
 </td>
@@ -3534,7 +3534,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20221205-moving-fast-philosophy-development.html" class="filename listing-filename">20221205-moving-fast-philosophy-development.md</a>
 </td>
 </tr>
-<tr data-index="300" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="3" data-listing-word-count-sort="438" data-listing-title-sort="Proposed: Debug Linux Export" data-listing-filename-sort="20221205-debug-linux-export.md">
+<tr data-index="300" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="3" data-listing-word-count-sort="438" data-listing-title-sort="Proposed: Debug Linux Export" data-listing-filename-sort="20221205-debug-linux-export.md">
 <td>
 <a href="./decisions/20221205-debug-linux-export.html" class="title listing-title">Proposed: Debug Linux Export</a>
 </td>
@@ -3545,7 +3545,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20221205-debug-linux-export.html" class="filename listing-filename">20221205-debug-linux-export.md</a>
 </td>
 </tr>
-<tr data-index="301" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="362" data-listing-title-sort="Proposed: Target 10 minutes cicd builds to improve our iterations" data-listing-filename-sort="20221203-target-10-minutes-cicd.md">
+<tr data-index="301" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="362" data-listing-title-sort="Proposed: Target 10 minutes cicd builds to improve our iterations" data-listing-filename-sort="20221203-target-10-minutes-cicd.md">
 <td>
 <a href="./decisions/20221203-target-10-minutes-cicd.html" class="title listing-title">Proposed: Target 10 minutes cicd builds to improve our iterations</a>
 </td>
@@ -3556,7 +3556,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20221203-target-10-minutes-cicd.html" class="filename listing-filename">20221203-target-10-minutes-cicd.md</a>
 </td>
 </tr>
-<tr data-index="302" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="381" data-listing-title-sort="Rejected: Blocking direct push to MAIN to avoid build breakage" data-listing-filename-sort="20221203-block-direct-pushes-to-main.md">
+<tr data-index="302" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="381" data-listing-title-sort="Rejected: Blocking direct push to MAIN to avoid build breakage" data-listing-filename-sort="20221203-block-direct-pushes-to-main.md">
 <td>
 <a href="./decisions/20221203-block-direct-pushes-to-main.html" class="title listing-title">Rejected: Blocking direct push to MAIN to avoid build breakage</a>
 </td>
@@ -3567,7 +3567,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20221203-block-direct-pushes-to-main.html" class="filename listing-filename">20221203-block-direct-pushes-to-main.md</a>
 </td>
 </tr>
-<tr data-index="303" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="5" data-listing-word-count-sort="959" data-listing-title-sort="Draft: Simulate larger 3d multiplayer worlds using &quot;brickworlds partition layout&quot;" data-listing-filename-sort="20221022-have-larger-worlds-by-server-state-migration.md">
+<tr data-index="303" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="5" data-listing-word-count-sort="959" data-listing-title-sort="Draft: Simulate larger 3d multiplayer worlds using &quot;brickworlds partition layout&quot;" data-listing-filename-sort="20221022-have-larger-worlds-by-server-state-migration.md">
 <td>
 <a href="./decisions/20221022-have-larger-worlds-by-server-state-migration.html" class="title listing-title">Draft: Simulate larger 3d multiplayer worlds using “brickworlds partition layout”</a>
 </td>
@@ -3578,7 +3578,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20221022-have-larger-worlds-by-server-state-migration.html" class="filename listing-filename">20221022-have-larger-worlds-by-server-state-migration.md</a>
 </td>
 </tr>
-<tr data-index="304" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="3" data-listing-word-count-sort="457" data-listing-title-sort="Proposed: Make it easier to propose and file bugs by simplifying the templates" data-listing-filename-sort="20221021-make-it-easier-propose-and-post-bugs.md">
+<tr data-index="304" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="3" data-listing-word-count-sort="457" data-listing-title-sort="Proposed: Make it easier to propose and file bugs by simplifying the templates" data-listing-filename-sort="20221021-make-it-easier-propose-and-post-bugs.md">
 <td>
 <a href="./decisions/20221021-make-it-easier-propose-and-post-bugs.html" class="title listing-title">Proposed: Make it easier to propose and file bugs by simplifying the templates</a>
 </td>
@@ -3589,7 +3589,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20221021-make-it-easier-propose-and-post-bugs.html" class="filename listing-filename">20221021-make-it-easier-propose-and-post-bugs.md</a>
 </td>
 </tr>
-<tr data-index="305" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="378" data-listing-title-sort="Proposed: Replicate sync 100'000 entities using a solution (Revision 1)" data-listing-filename-sort="20221019-replicate-sync-100-000-entities.md">
+<tr data-index="305" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="378" data-listing-title-sort="Proposed: Replicate sync 100'000 entities using a solution (Revision 1)" data-listing-filename-sort="20221019-replicate-sync-100-000-entities.md">
 <td>
 <a href="./decisions/20221019-replicate-sync-100-000-entities.html" class="title listing-title">Proposed: Replicate sync 100’000 entities using a solution (Revision 1)</a>
 </td>
@@ -3600,7 +3600,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20221019-replicate-sync-100-000-entities.html" class="filename listing-filename">20221019-replicate-sync-100-000-entities.md</a>
 </td>
 </tr>
-<tr data-index="306" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="4" data-listing-word-count-sort="715" data-listing-title-sort="Proposed: Networking with 100000 Entities and Ownership (Revision 2)" data-listing-filename-sort="20221019-networking-100000-entities-ownership.md">
+<tr data-index="306" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="4" data-listing-word-count-sort="715" data-listing-title-sort="Proposed: Networking with 100000 Entities and Ownership (Revision 2)" data-listing-filename-sort="20221019-networking-100000-entities-ownership.md">
 <td>
 <a href="./decisions/20221019-networking-100000-entities-ownership.html" class="title listing-title">Proposed: Networking with 100000 Entities and Ownership (Revision 2)</a>
 </td>
@@ -3611,7 +3611,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20221019-networking-100000-entities-ownership.html" class="filename listing-filename">20221019-networking-100000-entities-ownership.md</a>
 </td>
 </tr>
-<tr data-index="307" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="3" data-listing-word-count-sort="569" data-listing-title-sort="Proposed: Replicate sync 100'000 entities using Godot Engine, mvsqlite and Foundationdb" data-listing-filename-sort="20221019-develop-a-replication-sync-for-100-000-entities.md">
+<tr data-index="307" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="3" data-listing-word-count-sort="569" data-listing-title-sort="Proposed: Replicate sync 100'000 entities using Godot Engine, mvsqlite and Foundationdb" data-listing-filename-sort="20221019-develop-a-replication-sync-for-100-000-entities.md">
 <td>
 <a href="./decisions/20221019-develop-a-replication-sync-for-100-000-entities.html" class="title listing-title">Proposed: Replicate sync 100’000 entities using Godot Engine, mvsqlite and Foundationdb</a>
 </td>
@@ -3622,7 +3622,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20221019-develop-a-replication-sync-for-100-000-entities.html" class="filename listing-filename">20221019-develop-a-replication-sync-for-100-000-entities.md</a>
 </td>
 </tr>
-<tr data-index="308" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="3" data-listing-word-count-sort="486" data-listing-title-sort="Proposed: To remember how to update the engine and game write a procedure" data-listing-filename-sort="20221018-v-sekai-game-update-procedure.md">
+<tr data-index="308" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="3" data-listing-word-count-sort="486" data-listing-title-sort="Proposed: To remember how to update the engine and game write a procedure" data-listing-filename-sort="20221018-v-sekai-game-update-procedure.md">
 <td>
 <a href="./decisions/20221018-v-sekai-game-update-procedure.html" class="title listing-title">Proposed: To remember how to update the engine and game write a procedure</a>
 </td>
@@ -3633,7 +3633,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20221018-v-sekai-game-update-procedure.html" class="filename listing-filename">20221018-v-sekai-game-update-procedure.md</a>
 </td>
 </tr>
-<tr data-index="309" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="9" data-listing-word-count-sort="1633" data-listing-title-sort="Rejected: Use view replication algorithm for multiplayer multirelay sync" data-listing-filename-sort="20221016-v-sekai-view-replication.md">
+<tr data-index="309" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="9" data-listing-word-count-sort="1633" data-listing-title-sort="Rejected: Use view replication algorithm for multiplayer multirelay sync" data-listing-filename-sort="20221016-v-sekai-view-replication.md">
 <td>
 <a href="./decisions/20221016-v-sekai-view-replication.html" class="title listing-title">Rejected: Use view replication algorithm for multiplayer multirelay sync</a>
 </td>
@@ -3644,7 +3644,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20221016-v-sekai-view-replication.html" class="filename listing-filename">20221016-v-sekai-view-replication.md</a>
 </td>
 </tr>
-<tr data-index="310" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="5" data-listing-word-count-sort="936" data-listing-title-sort="Draft: Networking Overhaul" data-listing-filename-sort="20221014-networking-overhaul-proposal.md">
+<tr data-index="310" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="5" data-listing-word-count-sort="936" data-listing-title-sort="Draft: Networking Overhaul" data-listing-filename-sort="20221014-networking-overhaul-proposal.md">
 <td>
 <a href="./decisions/20221014-networking-overhaul-proposal.html" class="title listing-title">Draft: Networking Overhaul</a>
 </td>
@@ -3655,7 +3655,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20221014-networking-overhaul-proposal.html" class="filename listing-filename">20221014-networking-overhaul-proposal.md</a>
 </td>
 </tr>
-<tr data-index="311" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="317" data-listing-title-sort="Proposed: Unidot is optional" data-listing-filename-sort="20221006-unidot-is-optional.md">
+<tr data-index="311" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="317" data-listing-title-sort="Proposed: Unidot is optional" data-listing-filename-sort="20221006-unidot-is-optional.md">
 <td>
 <a href="./decisions/20221006-unidot-is-optional.html" class="title listing-title">Proposed: Unidot is optional</a>
 </td>
@@ -3666,7 +3666,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20221006-unidot-is-optional.html" class="filename listing-filename">20221006-unidot-is-optional.md</a>
 </td>
 </tr>
-<tr data-index="312" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="317" data-listing-title-sort="Proposed: Rename master to godot3 and main to godot4" data-listing-filename-sort="20221006-rename-to-main.md">
+<tr data-index="312" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="317" data-listing-title-sort="Proposed: Rename master to godot3 and main to godot4" data-listing-filename-sort="20221006-rename-to-main.md">
 <td>
 <a href="./decisions/20221006-rename-to-main.html" class="title listing-title">Proposed: Rename master to godot3 and main to godot4</a>
 </td>
@@ -3677,7 +3677,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20221006-rename-to-main.html" class="filename listing-filename">20221006-rename-to-main.md</a>
 </td>
 </tr>
-<tr data-index="313" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="325" data-listing-title-sort="Proposed: We have too many branches on V-Sekai/godot." data-listing-filename-sort="20220916-too-many-branches-on-v-sekai-godot.md">
+<tr data-index="313" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="325" data-listing-title-sort="Proposed: We have too many branches on V-Sekai/godot." data-listing-filename-sort="20220916-too-many-branches-on-v-sekai-godot.md">
 <td>
 <a href="./decisions/20220916-too-many-branches-on-v-sekai-godot.html" class="title listing-title">Proposed: We have too many branches on V-Sekai/godot.</a>
 </td>
@@ -3688,7 +3688,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20220916-too-many-branches-on-v-sekai-godot.html" class="filename listing-filename">20220916-too-many-branches-on-v-sekai-godot.md</a>
 </td>
 </tr>
-<tr data-index="314" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="304" data-listing-title-sort="Proposed: Extended asset library packages in addition to the upstream asset library" data-listing-filename-sort="20220901-mirror-extend-asset-library-packages.md">
+<tr data-index="314" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="304" data-listing-title-sort="Proposed: Extended asset library packages in addition to the upstream asset library" data-listing-filename-sort="20220901-mirror-extend-asset-library-packages.md">
 <td>
 <a href="./decisions/20220901-mirror-extend-asset-library-packages.html" class="title listing-title">Proposed: Extended asset library packages in addition to the upstream asset library</a>
 </td>
@@ -3699,7 +3699,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20220901-mirror-extend-asset-library-packages.html" class="filename listing-filename">20220901-mirror-extend-asset-library-packages.md</a>
 </td>
 </tr>
-<tr data-index="315" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="293" data-listing-title-sort="Proposed: Provide pdf reading" data-listing-filename-sort="20220830-godot-pdf-workflow.md">
+<tr data-index="315" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="293" data-listing-title-sort="Proposed: Provide pdf reading" data-listing-filename-sort="20220830-godot-pdf-workflow.md">
 <td>
 <a href="./decisions/20220830-godot-pdf-workflow.html" class="title listing-title">Proposed: Provide pdf reading</a>
 </td>
@@ -3710,7 +3710,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20220830-godot-pdf-workflow.html" class="filename listing-filename">20220830-godot-pdf-workflow.md</a>
 </td>
 </tr>
-<tr data-index="316" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="344" data-listing-title-sort="Proposed: Make a market booth creation tutorial." data-listing-filename-sort="20220820-market-booth-tutorial.md">
+<tr data-index="316" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="344" data-listing-title-sort="Proposed: Make a market booth creation tutorial." data-listing-filename-sort="20220820-market-booth-tutorial.md">
 <td>
 <a href="./decisions/20220820-market-booth-tutorial.html" class="title listing-title">Proposed: Make a market booth creation tutorial.</a>
 </td>
@@ -3721,7 +3721,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20220820-market-booth-tutorial.html" class="filename listing-filename">20220820-market-booth-tutorial.md</a>
 </td>
 </tr>
-<tr data-index="317" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="266" data-listing-title-sort="Proposed: Simulate cloth on characters" data-listing-filename-sort="20220820-cloth-sim.md">
+<tr data-index="317" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="266" data-listing-title-sort="Proposed: Simulate cloth on characters" data-listing-filename-sort="20220820-cloth-sim.md">
 <td>
 <a href="./decisions/20220820-cloth-sim.html" class="title listing-title">Proposed: Simulate cloth on characters</a>
 </td>
@@ -3732,7 +3732,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20220820-cloth-sim.html" class="filename listing-filename">20220820-cloth-sim.md</a>
 </td>
 </tr>
-<tr data-index="318" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="3" data-listing-word-count-sort="574" data-listing-title-sort="Proposed: Bake alembic imports by running blender script." data-listing-filename-sort="20220820-bake alembic-anim-via-blender.md">
+<tr data-index="318" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="3" data-listing-word-count-sort="574" data-listing-title-sort="Proposed: Bake alembic imports by running blender script." data-listing-filename-sort="20220820-bake alembic-anim-via-blender.md">
 <td>
 <a href="./decisions/20220820-bake alembic-anim-via-blender.html" class="title listing-title">Proposed: Bake alembic imports by running blender script.</a>
 </td>
@@ -3743,7 +3743,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20220820-bake alembic-anim-via-blender.html" class="filename listing-filename">20220820-bake alembic-anim-via-blender.md</a>
 </td>
 </tr>
-<tr data-index="319" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="3" data-listing-word-count-sort="444" data-listing-title-sort="Proposed: Connect Mediapipe to Blender" data-listing-filename-sort="20220624-webcam-to-posed-characters.md">
+<tr data-index="319" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="3" data-listing-word-count-sort="444" data-listing-title-sort="Proposed: Connect Mediapipe to Blender" data-listing-filename-sort="20220624-webcam-to-posed-characters.md">
 <td>
 <a href="./decisions/20220624-webcam-to-posed-characters.html" class="title listing-title">Proposed: Connect Mediapipe to Blender</a>
 </td>
@@ -3754,7 +3754,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20220624-webcam-to-posed-characters.html" class="filename listing-filename">20220624-webcam-to-posed-characters.md</a>
 </td>
 </tr>
-<tr data-index="320" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="3" data-listing-word-count-sort="534" data-listing-title-sort="Proposed: Host a baserow application for internal use." data-listing-filename-sort="20220605-host-internal-baserow.md">
+<tr data-index="320" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="3" data-listing-word-count-sort="534" data-listing-title-sort="Proposed: Host a baserow application for internal use." data-listing-filename-sort="20220605-host-internal-baserow.md">
 <td>
 <a href="./decisions/20220605-host-internal-baserow.html" class="title listing-title">Proposed: Host a baserow application for internal use.</a>
 </td>
@@ -3765,7 +3765,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20220605-host-internal-baserow.html" class="filename listing-filename">20220605-host-internal-baserow.md</a>
 </td>
 </tr>
-<tr data-index="321" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="316" data-listing-title-sort="Accepted: To avoid git submodule but recreate the gocd pipelines" data-listing-filename-sort="20220605-gocd-pipeline-reset.md">
+<tr data-index="321" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="316" data-listing-title-sort="Accepted: To avoid git submodule but recreate the gocd pipelines" data-listing-filename-sort="20220605-gocd-pipeline-reset.md">
 <td>
 <a href="./decisions/20220605-gocd-pipeline-reset.html" class="title listing-title">Accepted: To avoid git submodule but recreate the gocd pipelines</a>
 </td>
@@ -3776,7 +3776,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20220605-gocd-pipeline-reset.html" class="filename listing-filename">20220605-gocd-pipeline-reset.md</a>
 </td>
 </tr>
-<tr data-index="322" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="3" data-listing-word-count-sort="456" data-listing-title-sort="Proposed: Lightweight quality avatars" data-listing-filename-sort="20220601-lightweight-quality-avatars.md">
+<tr data-index="322" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="3" data-listing-word-count-sort="456" data-listing-title-sort="Proposed: Lightweight quality avatars" data-listing-filename-sort="20220601-lightweight-quality-avatars.md">
 <td>
 <a href="./decisions/20220601-lightweight-quality-avatars.html" class="title listing-title">Proposed: Lightweight quality avatars</a>
 </td>
@@ -3787,7 +3787,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20220601-lightweight-quality-avatars.html" class="filename listing-filename">20220601-lightweight-quality-avatars.md</a>
 </td>
 </tr>
-<tr data-index="323" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="370" data-listing-title-sort="Rejected: To create a deployment kit use truescale to host gocd agents for cicd." data-listing-filename-sort="20220531-truenas-scale.md">
+<tr data-index="323" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="370" data-listing-title-sort="Rejected: To create a deployment kit use truescale to host gocd agents for cicd." data-listing-filename-sort="20220531-truenas-scale.md">
 <td>
 <a href="./decisions/20220531-truenas-scale.html" class="title listing-title">Rejected: To create a deployment kit use truescale to host gocd agents for cicd.</a>
 </td>
@@ -3798,7 +3798,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20220531-truenas-scale.html" class="filename listing-filename">20220531-truenas-scale.md</a>
 </td>
 </tr>
-<tr data-index="324" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="3" data-listing-word-count-sort="510" data-listing-title-sort="Accepted: How to start a development environment for cockroach and elixir?" data-listing-filename-sort="20220531-elixir-uro-dev.md">
+<tr data-index="324" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="3" data-listing-word-count-sort="510" data-listing-title-sort="Accepted: How to start a development environment for cockroach and elixir?" data-listing-filename-sort="20220531-elixir-uro-dev.md">
 <td>
 <a href="./decisions/20220531-elixir-uro-dev.html" class="title listing-title">Accepted: How to start a development environment for cockroach and elixir?</a>
 </td>
@@ -3809,7 +3809,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20220531-elixir-uro-dev.html" class="filename listing-filename">20220531-elixir-uro-dev.md</a>
 </td>
 </tr>
-<tr data-index="325" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="319" data-listing-title-sort="Proposed: Profile using perf" data-listing-filename-sort="20220515-profile-using-perf.md">
+<tr data-index="325" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="319" data-listing-title-sort="Proposed: Profile using perf" data-listing-filename-sort="20220515-profile-using-perf.md">
 <td>
 <a href="./decisions/20220515-profile-using-perf.html" class="title listing-title">Proposed: Profile using perf</a>
 </td>
@@ -3820,7 +3820,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20220515-profile-using-perf.html" class="filename listing-filename">20220515-profile-using-perf.md</a>
 </td>
 </tr>
-<tr data-index="326" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="4" data-listing-word-count-sort="672" data-listing-title-sort="Proposed: Merge retargeting feature into Godot Engine master" data-listing-filename-sort="20220318-merge-retargeting-pr.md">
+<tr data-index="326" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="4" data-listing-word-count-sort="672" data-listing-title-sort="Proposed: Merge retargeting feature into Godot Engine master" data-listing-filename-sort="20220318-merge-retargeting-pr.md">
 <td>
 <a href="./decisions/20220318-merge-retargeting-pr.html" class="title listing-title">Proposed: Merge retargeting feature into Godot Engine master</a>
 </td>
@@ -3831,7 +3831,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20220318-merge-retargeting-pr.html" class="filename listing-filename">20220318-merge-retargeting-pr.md</a>
 </td>
 </tr>
-<tr data-index="327" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="324" data-listing-title-sort="Proposed: Use specular vec3 from gltf to show multicoloured metals" data-listing-filename-sort="20220317-use-spec-rough-metal.md">
+<tr data-index="327" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="324" data-listing-title-sort="Proposed: Use specular vec3 from gltf to show multicoloured metals" data-listing-filename-sort="20220317-use-spec-rough-metal.md">
 <td>
 <a href="./decisions/20220317-use-spec-rough-metal.html" class="title listing-title">Proposed: Use specular vec3 from gltf to show multicoloured metals</a>
 </td>
@@ -3842,7 +3842,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20220317-use-spec-rough-metal.html" class="filename listing-filename">20220317-use-spec-rough-metal.md</a>
 </td>
 </tr>
-<tr data-index="328" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="324" data-listing-title-sort="Proposed: To protect the minimum spec maintain steam deck version of flatmode V-Sekai" data-listing-filename-sort="20220317-protect-minumum-spec-steam-deck.md">
+<tr data-index="328" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="324" data-listing-title-sort="Proposed: To protect the minimum spec maintain steam deck version of flatmode V-Sekai" data-listing-filename-sort="20220317-protect-minumum-spec-steam-deck.md">
 <td>
 <a href="./decisions/20220317-protect-minumum-spec-steam-deck.html" class="title listing-title">Proposed: To protect the minimum spec maintain steam deck version of flatmode V-Sekai</a>
 </td>
@@ -3853,7 +3853,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20220317-protect-minumum-spec-steam-deck.html" class="filename listing-filename">20220317-protect-minumum-spec-steam-deck.md</a>
 </td>
 </tr>
-<tr data-index="329" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="315" data-listing-title-sort="Draft: To provide an asset library prototype use baserow" data-listing-filename-sort="20220317-baserow.io-truenas.md">
+<tr data-index="329" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="315" data-listing-title-sort="Draft: To provide an asset library prototype use baserow" data-listing-filename-sort="20220317-baserow.io-truenas.md">
 <td>
 <a href="./decisions/20220317-baserow.io-truenas.html" class="title listing-title">Draft: To provide an asset library prototype use baserow</a>
 </td>
@@ -3864,7 +3864,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20220317-baserow.io-truenas.html" class="filename listing-filename">20220317-baserow.io-truenas.md</a>
 </td>
 </tr>
-<tr data-index="330" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="3" data-listing-word-count-sort="411" data-listing-title-sort="Accepted: Planning V-Sekai Version 3 on 2022-02-28" data-listing-filename-sort="20220228-v-sekai-version-three-plan.md">
+<tr data-index="330" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="3" data-listing-word-count-sort="411" data-listing-title-sort="Accepted: Planning V-Sekai Version 3 on 2022-02-28" data-listing-filename-sort="20220228-v-sekai-version-three-plan.md">
 <td>
 <a href="./decisions/20220228-v-sekai-version-three-plan.html" class="title listing-title">Accepted: Planning V-Sekai Version 3 on 2022-02-28</a>
 </td>
@@ -3875,7 +3875,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20220228-v-sekai-version-three-plan.html" class="filename listing-filename">20220228-v-sekai-version-three-plan.md</a>
 </td>
 </tr>
-<tr data-index="331" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="4" data-listing-word-count-sort="652" data-listing-title-sort="Superseded: Planning V-Sekai Version 2 on 2022-02-24" data-listing-filename-sort="20220224-v-sekai-version-two-plan.md">
+<tr data-index="331" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="4" data-listing-word-count-sort="652" data-listing-title-sort="Superseded: Planning V-Sekai Version 2 on 2022-02-24" data-listing-filename-sort="20220224-v-sekai-version-two-plan.md">
 <td>
 <a href="./decisions/20220224-v-sekai-version-two-plan.html" class="title listing-title">Superseded: Planning V-Sekai Version 2 on 2022-02-24</a>
 </td>
@@ -3886,7 +3886,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20220224-v-sekai-version-two-plan.html" class="filename listing-filename">20220224-v-sekai-version-two-plan.md</a>
 </td>
 </tr>
-<tr data-index="332" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="3" data-listing-word-count-sort="532" data-listing-title-sort="Rejected: Storing raw VSK_map files via DVC to avoid limitations" data-listing-filename-sort="20220223-store-source-VSK_map-files-via-DVC.md">
+<tr data-index="332" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="3" data-listing-word-count-sort="532" data-listing-title-sort="Rejected: Storing raw VSK_map files via DVC to avoid limitations" data-listing-filename-sort="20220223-store-source-VSK_map-files-via-DVC.md">
 <td>
 <a href="./decisions/20220223-store-source-VSK_map-files-via-DVC.html" class="title listing-title">Rejected: Storing raw VSK_map files via DVC to avoid limitations</a>
 </td>
@@ -3897,7 +3897,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20220223-store-source-VSK_map-files-via-DVC.html" class="filename listing-filename">20220223-store-source-VSK_map-files-via-DVC.md</a>
 </td>
 </tr>
-<tr data-index="333" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="4" data-listing-word-count-sort="773" data-listing-title-sort="Accepted: Rank skeleton #bone names with catboost" data-listing-filename-sort="20220222-rank-skeleton-bone-names-with-catboost.md">
+<tr data-index="333" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="4" data-listing-word-count-sort="773" data-listing-title-sort="Accepted: Rank skeleton #bone names with catboost" data-listing-filename-sort="20220222-rank-skeleton-bone-names-with-catboost.md">
 <td>
 <a href="./decisions/20220222-rank-skeleton-bone-names-with-catboost.html" class="title listing-title">Accepted: Rank skeleton #bone names with catboost</a>
 </td>
@@ -3908,7 +3908,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20220222-rank-skeleton-bone-names-with-catboost.html" class="filename listing-filename">20220222-rank-skeleton-bone-names-with-catboost.md</a>
 </td>
 </tr>
-<tr data-index="334" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="3" data-listing-word-count-sort="456" data-listing-title-sort="Accepted: Rank skeleton #bone names with xgboost" data-listing-filename-sort="20220222-rank-bone-skeletons-with-xgboost.md">
+<tr data-index="334" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="3" data-listing-word-count-sort="456" data-listing-title-sort="Accepted: Rank skeleton #bone names with xgboost" data-listing-filename-sort="20220222-rank-bone-skeletons-with-xgboost.md">
 <td>
 <a href="./decisions/20220222-rank-bone-skeletons-with-xgboost.html" class="title listing-title">Accepted: Rank skeleton #bone names with xgboost</a>
 </td>
@@ -3919,7 +3919,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20220222-rank-bone-skeletons-with-xgboost.html" class="filename listing-filename">20220222-rank-bone-skeletons-with-xgboost.md</a>
 </td>
 </tr>
-<tr data-index="335" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="3" data-listing-word-count-sort="457" data-listing-title-sort="Accepted: Rank skeleton #bone names with transformer4rec" data-listing-filename-sort="20220222-rank-bone-names-with-transformer.md">
+<tr data-index="335" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="3" data-listing-word-count-sort="457" data-listing-title-sort="Accepted: Rank skeleton #bone names with transformer4rec" data-listing-filename-sort="20220222-rank-bone-names-with-transformer.md">
 <td>
 <a href="./decisions/20220222-rank-bone-names-with-transformer.html" class="title listing-title">Accepted: Rank skeleton #bone names with transformer4rec</a>
 </td>
@@ -3930,7 +3930,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20220222-rank-bone-names-with-transformer.html" class="filename listing-filename">20220222-rank-bone-names-with-transformer.md</a>
 </td>
 </tr>
-<tr data-index="336" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="4" data-listing-word-count-sort="653" data-listing-title-sort="Superseded: Planning V-Sekai on 2022-02-21 Superseded" data-listing-filename-sort="20220222-know-where-we-re-going-by-planning-vsekai.md">
+<tr data-index="336" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="4" data-listing-word-count-sort="653" data-listing-title-sort="Superseded: Planning V-Sekai on 2022-02-21 Superseded" data-listing-filename-sort="20220222-know-where-we-re-going-by-planning-vsekai.md">
 <td>
 <a href="./decisions/20220222-know-where-we-re-going-by-planning-vsekai.html" class="title listing-title">Superseded: Planning V-Sekai on 2022-02-21 Superseded</a>
 </td>
@@ -3941,7 +3941,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20220222-know-where-we-re-going-by-planning-vsekai.html" class="filename listing-filename">20220222-know-where-we-re-going-by-planning-vsekai.md</a>
 </td>
 </tr>
-<tr data-index="337" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="3" data-listing-word-count-sort="423" data-listing-title-sort="Accepted: To create omi chan rig a \#256FES" data-listing-filename-sort="20220217-omi-chan-oni-chan.md">
+<tr data-index="337" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="3" data-listing-word-count-sort="423" data-listing-title-sort="Accepted: To create omi chan rig a \#256FES" data-listing-filename-sort="20220217-omi-chan-oni-chan.md">
 <td>
 <a href="./decisions/20220217-omi-chan-oni-chan.html" class="title listing-title">Accepted: To create omi chan rig a #256FES</a>
 </td>
@@ -3952,7 +3952,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20220217-omi-chan-oni-chan.html" class="filename listing-filename">20220217-omi-chan-oni-chan.md</a>
 </td>
 </tr>
-<tr data-index="338" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="3" data-listing-word-count-sort="457" data-listing-title-sort="Proposed: To deploy backend services like Uro safely use a defined process" data-listing-filename-sort="20220215-uro-deployment-process.md">
+<tr data-index="338" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="3" data-listing-word-count-sort="457" data-listing-title-sort="Proposed: To deploy backend services like Uro safely use a defined process" data-listing-filename-sort="20220215-uro-deployment-process.md">
 <td>
 <a href="./decisions/20220215-uro-deployment-process.html" class="title listing-title">Proposed: To deploy backend services like Uro safely use a defined process</a>
 </td>
@@ -3963,7 +3963,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20220215-uro-deployment-process.html" class="filename listing-filename">20220215-uro-deployment-process.md</a>
 </td>
 </tr>
-<tr data-index="339" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="358" data-listing-title-sort="Accepted: To make a virtual pet game given Jeana's designs" data-listing-filename-sort="20220207-virtual-pets.md">
+<tr data-index="339" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="358" data-listing-title-sort="Accepted: To make a virtual pet game given Jeana's designs" data-listing-filename-sort="20220207-virtual-pets.md">
 <td>
 <a href="./decisions/20220207-virtual-pets.html" class="title listing-title">Accepted: To make a virtual pet game given Jeana’s designs</a>
 </td>
@@ -3974,7 +3974,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20220207-virtual-pets.html" class="filename listing-filename">20220207-virtual-pets.md</a>
 </td>
 </tr>
-<tr data-index="340" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="342" data-listing-title-sort="Proposed: Log change notifications using DiscordChatExporter" data-listing-filename-sort="20220206-logging-notifications-from-discord.md">
+<tr data-index="340" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="342" data-listing-title-sort="Proposed: Log change notifications using DiscordChatExporter" data-listing-filename-sort="20220206-logging-notifications-from-discord.md">
 <td>
 <a href="./decisions/20220206-logging-notifications-from-discord.html" class="title listing-title">Proposed: Log change notifications using DiscordChatExporter</a>
 </td>
@@ -3985,7 +3985,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20220206-logging-notifications-from-discord.html" class="filename listing-filename">20220206-logging-notifications-from-discord.md</a>
 </td>
 </tr>
-<tr data-index="341" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="310" data-listing-title-sort="Accepted: Allow cicd to pass by fixing spatial audio branch" data-listing-filename-sort="20220205-cicd-to-pass by-fixing-spatial-audio-branch.md">
+<tr data-index="341" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="310" data-listing-title-sort="Accepted: Allow cicd to pass by fixing spatial audio branch" data-listing-filename-sort="20220205-cicd-to-pass by-fixing-spatial-audio-branch.md">
 <td>
 <a href="./decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html" class="title listing-title">Accepted: Allow cicd to pass by fixing spatial audio branch</a>
 </td>
@@ -3996,7 +3996,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html" class="filename listing-filename">20220205-cicd-to-pass by-fixing-spatial-audio-branch.md</a>
 </td>
 </tr>
-<tr data-index="342" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="3" data-listing-word-count-sort="440" data-listing-title-sort="Draft: To have a default set of motions on a 3d character by creating a default animation set" data-listing-filename-sort="20220203-create-default-animation-set.md">
+<tr data-index="342" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="3" data-listing-word-count-sort="440" data-listing-title-sort="Draft: To have a default set of motions on a 3d character by creating a default animation set" data-listing-filename-sort="20220203-create-default-animation-set.md">
 <td>
 <a href="./decisions/20220203-create-default-animation-set.html" class="title listing-title">Draft: To have a default set of motions on a 3d character by creating a default animation set</a>
 </td>
@@ -4007,7 +4007,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20220203-create-default-animation-set.html" class="filename listing-filename">20220203-create-default-animation-set.md</a>
 </td>
 </tr>
-<tr data-index="343" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="4" data-listing-word-count-sort="612" data-listing-title-sort="Accepted: Interoperability between platforms using gltf extensions" data-listing-filename-sort="20220202-gltf-extensions-for-interoperability.md">
+<tr data-index="343" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="4" data-listing-word-count-sort="612" data-listing-title-sort="Accepted: Interoperability between platforms using gltf extensions" data-listing-filename-sort="20220202-gltf-extensions-for-interoperability.md">
 <td>
 <a href="./decisions/20220202-gltf-extensions-for-interoperability.html" class="title listing-title">Accepted: Interoperability between platforms using gltf extensions</a>
 </td>
@@ -4018,7 +4018,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20220202-gltf-extensions-for-interoperability.html" class="filename listing-filename">20220202-gltf-extensions-for-interoperability.md</a>
 </td>
 </tr>
-<tr data-index="344" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="4" data-listing-word-count-sort="622" data-listing-title-sort="Rejected: To allow independent deployment run our own infrastructure" data-listing-filename-sort="20220131-run-own-infrastructure.md">
+<tr data-index="344" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="4" data-listing-word-count-sort="622" data-listing-title-sort="Rejected: To allow independent deployment run our own infrastructure" data-listing-filename-sort="20220131-run-own-infrastructure.md">
 <td>
 <a href="./decisions/20220131-run-own-infrastructure.html" class="title listing-title">Rejected: To allow independent deployment run our own infrastructure</a>
 </td>
@@ -4029,7 +4029,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20220131-run-own-infrastructure.html" class="filename listing-filename">20220131-run-own-infrastructure.md</a>
 </td>
 </tr>
-<tr data-index="345" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="3" data-listing-word-count-sort="456" data-listing-title-sort="Accepted: To have an alternative CICD use Github Actions." data-listing-filename-sort="20220131-github-actions-support.md">
+<tr data-index="345" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="3" data-listing-word-count-sort="456" data-listing-title-sort="Accepted: To have an alternative CICD use Github Actions." data-listing-filename-sort="20220131-github-actions-support.md">
 <td>
 <a href="./decisions/20220131-github-actions-support.html" class="title listing-title">Accepted: To have an alternative CICD use Github Actions.</a>
 </td>
@@ -4040,7 +4040,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20220131-github-actions-support.html" class="filename listing-filename">20220131-github-actions-support.md</a>
 </td>
 </tr>
-<tr data-index="346" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="325" data-listing-title-sort="Proposed: Make a desktop version of Uro for ease of development." data-listing-filename-sort="20220131-elixir-desktop-uro.md">
+<tr data-index="346" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="325" data-listing-title-sort="Proposed: Make a desktop version of Uro for ease of development." data-listing-filename-sort="20220131-elixir-desktop-uro.md">
 <td>
 <a href="./decisions/20220131-elixir-desktop-uro.html" class="title listing-title">Proposed: Make a desktop version of Uro for ease of development.</a>
 </td>
@@ -4051,7 +4051,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20220131-elixir-desktop-uro.html" class="filename listing-filename">20220131-elixir-desktop-uro.md</a>
 </td>
 </tr>
-<tr data-index="347" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="4" data-listing-word-count-sort="711" data-listing-title-sort="Accepted: To record decisions write a proposal." data-listing-filename-sort="20220130-to-record-decisions-write-a-proposal.md">
+<tr data-index="347" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="4" data-listing-word-count-sort="711" data-listing-title-sort="Accepted: To record decisions write a proposal." data-listing-filename-sort="20220130-to-record-decisions-write-a-proposal.md">
 <td>
 <a href="./decisions/20220130-to-record-decisions-write-a-proposal.html" class="title listing-title">Accepted: To record decisions write a proposal.</a>
 </td>
@@ -4062,7 +4062,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20220130-to-record-decisions-write-a-proposal.html" class="filename listing-filename">20220130-to-record-decisions-write-a-proposal.md</a>
 </td>
 </tr>
-<tr data-index="348" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="330" data-listing-title-sort="Proposal: Optimize cicd for costs because it's limited" data-listing-filename-sort="20220130-optimize-cicd.md">
+<tr data-index="348" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="330" data-listing-title-sort="Proposal: Optimize cicd for costs because it's limited" data-listing-filename-sort="20220130-optimize-cicd.md">
 <td>
 <a href="./decisions/20220130-optimize-cicd.html" class="title listing-title">Proposal: Optimize cicd for costs because it’s limited</a>
 </td>
@@ -4073,7 +4073,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20220130-optimize-cicd.html" class="filename listing-filename">20220130-optimize-cicd.md</a>
 </td>
 </tr>
-<tr data-index="349" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="325" data-listing-title-sort="Accepted: To make it easier to upload V-Sekai maps and Avatars use Godot Engine 4 script templates." data-listing-filename-sort="20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.md">
+<tr data-index="349" data-listing-file-modified-sort="1730559023674" data-listing-reading-time-sort="2" data-listing-word-count-sort="325" data-listing-title-sort="Accepted: To make it easier to upload V-Sekai maps and Avatars use Godot Engine 4 script templates." data-listing-filename-sort="20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.md">
 <td>
 <a href="./decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html" class="title listing-title">Accepted: To make it easier to upload V-Sekai maps and Avatars use Godot Engine 4 script templates.</a>
 </td>
@@ -4084,7 +4084,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html" class="filename listing-filename">20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.md</a>
 </td>
 </tr>
-<tr data-index="350" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="338" data-listing-title-sort="Accepted: Convert gltf to a scene with AudioStreamPlayer3D, convert AudiostreamPlayer3D to gltf and expose usability." data-listing-filename-sort="20220118-convert-gltf-to-a-scene.md">
+<tr data-index="350" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="338" data-listing-title-sort="Accepted: Convert gltf to a scene with AudioStreamPlayer3D, convert AudiostreamPlayer3D to gltf and expose usability." data-listing-filename-sort="20220118-convert-gltf-to-a-scene.md">
 <td>
 <a href="./decisions/20220118-convert-gltf-to-a-scene.html" class="title listing-title">Accepted: Convert gltf to a scene with AudioStreamPlayer3D, convert AudiostreamPlayer3D to gltf and expose usability.</a>
 </td>
@@ -4095,7 +4095,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20220118-convert-gltf-to-a-scene.html" class="filename listing-filename">20220118-convert-gltf-to-a-scene.md</a>
 </td>
 </tr>
-<tr data-index="351" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="279" data-listing-title-sort="Proposal: Change transform by CRDT." data-listing-filename-sort="20220113-change-transform-by-crdt.md">
+<tr data-index="351" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="279" data-listing-title-sort="Proposal: Change transform by CRDT." data-listing-filename-sort="20220113-change-transform-by-crdt.md">
 <td>
 <a href="./decisions/20220113-change-transform-by-crdt.html" class="title listing-title">Proposal: Change transform by CRDT.</a>
 </td>
@@ -4106,7 +4106,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20220113-change-transform-by-crdt.html" class="filename listing-filename">20220113-change-transform-by-crdt.md</a>
 </td>
 </tr>
-<tr data-index="352" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="3" data-listing-word-count-sort="570" data-listing-title-sort="Proposal: Bake blend shapes to skeletons for performance" data-listing-filename-sort="20220108-bake-blend-shapes-to-skeletons-for-performance.md">
+<tr data-index="352" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="3" data-listing-word-count-sort="570" data-listing-title-sort="Proposal: Bake blend shapes to skeletons for performance" data-listing-filename-sort="20220108-bake-blend-shapes-to-skeletons-for-performance.md">
 <td>
 <a href="./decisions/20220108-bake-blend-shapes-to-skeletons-for-performance.html" class="title listing-title">Proposal: Bake blend shapes to skeletons for performance</a>
 </td>
@@ -4117,7 +4117,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20220108-bake-blend-shapes-to-skeletons-for-performance.html" class="filename listing-filename">20220108-bake-blend-shapes-to-skeletons-for-performance.md</a>
 </td>
 </tr>
-<tr data-index="353" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="345" data-listing-title-sort="Proposal: Stream a character from a webcam to the vmc protocol" data-listing-filename-sort="20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.md">
+<tr data-index="353" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="345" data-listing-title-sort="Proposal: Stream a character from a webcam to the vmc protocol" data-listing-filename-sort="20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.md">
 <td>
 <a href="./decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html" class="title listing-title">Proposal: Stream a character from a webcam to the vmc protocol</a>
 </td>
@@ -4128,7 +4128,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html" class="filename listing-filename">20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.md</a>
 </td>
 </tr>
-<tr data-index="354" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="3" data-listing-word-count-sort="447" data-listing-title-sort="Accepted: Run meetings using Lean Coffee" data-listing-filename-sort="20211229-run-meetings-using-lean-coffee.md">
+<tr data-index="354" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="3" data-listing-word-count-sort="447" data-listing-title-sort="Accepted: Run meetings using Lean Coffee" data-listing-filename-sort="20211229-run-meetings-using-lean-coffee.md">
 <td>
 <a href="./decisions/20211229-run-meetings-using-lean-coffee.html" class="title listing-title">Accepted: Run meetings using Lean Coffee</a>
 </td>
@@ -4139,7 +4139,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211229-run-meetings-using-lean-coffee.html" class="filename listing-filename">20211229-run-meetings-using-lean-coffee.md</a>
 </td>
 </tr>
-<tr data-index="355" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="381" data-listing-title-sort="Rejected: Network the Ubisoft Mixer server" data-listing-filename-sort="20211220-network-the-ubisoft-mixer-server.md">
+<tr data-index="355" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="381" data-listing-title-sort="Rejected: Network the Ubisoft Mixer server" data-listing-filename-sort="20211220-network-the-ubisoft-mixer-server.md">
 <td>
 <a href="./decisions/20211220-network-the-ubisoft-mixer-server.html" class="title listing-title">Rejected: Network the Ubisoft Mixer server</a>
 </td>
@@ -4150,7 +4150,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211220-network-the-ubisoft-mixer-server.html" class="filename listing-filename">20211220-network-the-ubisoft-mixer-server.md</a>
 </td>
 </tr>
-<tr data-index="356" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="4" data-listing-word-count-sort="736" data-listing-title-sort="Accepted: Create an open metaverse by working on V-Sekai" data-listing-filename-sort="20211214-create-an-open-metaverse-by-working-on-v-sekai.md">
+<tr data-index="356" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="4" data-listing-word-count-sort="736" data-listing-title-sort="Accepted: Create an open metaverse by working on V-Sekai" data-listing-filename-sort="20211214-create-an-open-metaverse-by-working-on-v-sekai.md">
 <td>
 <a href="./decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html" class="title listing-title">Accepted: Create an open metaverse by working on V-Sekai</a>
 </td>
@@ -4161,7 +4161,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html" class="filename listing-filename">20211214-create-an-open-metaverse-by-working-on-v-sekai.md</a>
 </td>
 </tr>
-<tr data-index="357" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="345" data-listing-title-sort="Rejected: Create Steamdeck hardware proxy by installing Fedora Silverblue and #steam" data-listing-filename-sort="20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.md">
+<tr data-index="357" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="345" data-listing-title-sort="Rejected: Create Steamdeck hardware proxy by installing Fedora Silverblue and #steam" data-listing-filename-sort="20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.md">
 <td>
 <a href="./decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html" class="title listing-title">Rejected: Create Steamdeck hardware proxy by installing Fedora Silverblue and #steam</a>
 </td>
@@ -4172,7 +4172,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html" class="filename listing-filename">20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.md</a>
 </td>
 </tr>
-<tr data-index="358" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="336" data-listing-title-sort="Rejected: Create Steamdeck hardware proxy by installing Fedora Kinoite and #steam" data-listing-filename-sort="20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.md">
+<tr data-index="358" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="336" data-listing-title-sort="Rejected: Create Steamdeck hardware proxy by installing Fedora Kinoite and #steam" data-listing-filename-sort="20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.md">
 <td>
 <a href="./decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html" class="title listing-title">Rejected: Create Steamdeck hardware proxy by installing Fedora Kinoite and #steam</a>
 </td>
@@ -4183,7 +4183,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html" class="filename listing-filename">20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.md</a>
 </td>
 </tr>
-<tr data-index="359" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="3" data-listing-word-count-sort="457" data-listing-title-sort="Accepted: For Godot Engine changes use a decision flowchart" data-listing-filename-sort="20211207-for-godot-engine-changes-use-a-decision-flowchart.md">
+<tr data-index="359" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="3" data-listing-word-count-sort="457" data-listing-title-sort="Accepted: For Godot Engine changes use a decision flowchart" data-listing-filename-sort="20211207-for-godot-engine-changes-use-a-decision-flowchart.md">
 <td>
 <a href="./decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html" class="title listing-title">Accepted: For Godot Engine changes use a decision flowchart</a>
 </td>
@@ -4194,7 +4194,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html" class="filename listing-filename">20211207-for-godot-engine-changes-use-a-decision-flowchart.md</a>
 </td>
 </tr>
-<tr data-index="360" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="389" data-listing-title-sort="Accepted: Create an upstream pull request for all non-V-Sekai related patches" data-listing-filename-sort="20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.md">
+<tr data-index="360" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="389" data-listing-title-sort="Accepted: Create an upstream pull request for all non-V-Sekai related patches" data-listing-filename-sort="20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.md">
 <td>
 <a href="./decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html" class="title listing-title">Accepted: Create an upstream pull request for all non-V-Sekai related patches</a>
 </td>
@@ -4205,7 +4205,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html" class="filename listing-filename">20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.md</a>
 </td>
 </tr>
-<tr data-index="361" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="3" data-listing-word-count-sort="476" data-listing-title-sort="Accepted: Avoid avatar breaking by following quality checklist" data-listing-filename-sort="20211130-avoid-avatar-breaking-by-following-quality-checklist.md">
+<tr data-index="361" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="3" data-listing-word-count-sort="476" data-listing-title-sort="Accepted: Avoid avatar breaking by following quality checklist" data-listing-filename-sort="20211130-avoid-avatar-breaking-by-following-quality-checklist.md">
 <td>
 <a href="./decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html" class="title listing-title">Accepted: Avoid avatar breaking by following quality checklist</a>
 </td>
@@ -4216,7 +4216,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html" class="filename listing-filename">20211130-avoid-avatar-breaking-by-following-quality-checklist.md</a>
 </td>
 </tr>
-<tr data-index="362" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="3" data-listing-word-count-sort="414" data-listing-title-sort="Accepted: Create a Godot Engine asset store service on elixir and on sqlite." data-listing-filename-sort="20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.md">
+<tr data-index="362" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="3" data-listing-word-count-sort="414" data-listing-title-sort="Accepted: Create a Godot Engine asset store service on elixir and on sqlite." data-listing-filename-sort="20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.md">
 <td>
 <a href="./decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html" class="title listing-title">Accepted: Create a Godot Engine asset store service on elixir and on sqlite.</a>
 </td>
@@ -4227,7 +4227,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html" class="filename listing-filename">20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.md</a>
 </td>
 </tr>
-<tr data-index="363" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="338" data-listing-title-sort="Accepted: Stabilize Godot Engine updates by delaying to 2 week cycles" data-listing-filename-sort="20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.md">
+<tr data-index="363" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="338" data-listing-title-sort="Accepted: Stabilize Godot Engine updates by delaying to 2 week cycles" data-listing-filename-sort="20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.md">
 <td>
 <a href="./decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html" class="title listing-title">Accepted: Stabilize Godot Engine updates by delaying to 2 week cycles</a>
 </td>
@@ -4238,7 +4238,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html" class="filename listing-filename">20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.md</a>
 </td>
 </tr>
-<tr data-index="364" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="377" data-listing-title-sort="Proposed: Allow Godot Asset Library browser to use alternative sources" data-listing-filename-sort="20211117-allow-godot-asset-library-browser-to-use-alternative-sources.md">
+<tr data-index="364" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="377" data-listing-title-sort="Proposed: Allow Godot Asset Library browser to use alternative sources" data-listing-filename-sort="20211117-allow-godot-asset-library-browser-to-use-alternative-sources.md">
 <td>
 <a href="./decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html" class="title listing-title">Proposed: Allow Godot Asset Library browser to use alternative sources</a>
 </td>
@@ -4249,7 +4249,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html" class="filename listing-filename">20211117-allow-godot-asset-library-browser-to-use-alternative-sources.md</a>
 </td>
 </tr>
-<tr data-index="365" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="331" data-listing-title-sort="Proposed: Learn how to scale V-Sekai using bots and multipliers" data-listing-filename-sort="20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.md">
+<tr data-index="365" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="331" data-listing-title-sort="Proposed: Learn how to scale V-Sekai using bots and multipliers" data-listing-filename-sort="20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.md">
 <td>
 <a href="./decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html" class="title listing-title">Proposed: Learn how to scale V-Sekai using bots and multipliers</a>
 </td>
@@ -4260,7 +4260,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html" class="filename listing-filename">20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.md</a>
 </td>
 </tr>
-<tr data-index="366" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="3" data-listing-word-count-sort="560" data-listing-title-sort="Rejected: File or attestation for virtual worlds using ssh signatures" data-listing-filename-sort="20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.md">
+<tr data-index="366" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="3" data-listing-word-count-sort="560" data-listing-title-sort="Rejected: File or attestation for virtual worlds using ssh signatures" data-listing-filename-sort="20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.md">
 <td>
 <a href="./decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html" class="title listing-title">Rejected: File or attestation for virtual worlds using ssh signatures</a>
 </td>
@@ -4271,7 +4271,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html" class="filename listing-filename">20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.md</a>
 </td>
 </tr>
-<tr data-index="367" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="390" data-listing-title-sort="Accepted: Degrade V-Sekai's networking model to work in 2d and with webrtc." data-listing-filename-sort="20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.md">
+<tr data-index="367" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="390" data-listing-title-sort="Accepted: Degrade V-Sekai's networking model to work in 2d and with webrtc." data-listing-filename-sort="20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.md">
 <td>
 <a href="./decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html" class="title listing-title">Accepted: Degrade V-Sekai’s networking model to work in 2d and with webrtc.</a>
 </td>
@@ -4282,7 +4282,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html" class="filename listing-filename">20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.md</a>
 </td>
 </tr>
-<tr data-index="368" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="348" data-listing-title-sort="Draft: Create a VRM character by experimenting with written workflows." data-listing-filename-sort="20211109-create-a-vrm-character-by-experimenting-with-written-workflows.md">
+<tr data-index="368" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="348" data-listing-title-sort="Draft: Create a VRM character by experimenting with written workflows." data-listing-filename-sort="20211109-create-a-vrm-character-by-experimenting-with-written-workflows.md">
 <td>
 <a href="./decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html" class="title listing-title">Draft: Create a VRM character by experimenting with written workflows.</a>
 </td>
@@ -4293,7 +4293,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html" class="filename listing-filename">20211109-create-a-vrm-character-by-experimenting-with-written-workflows.md</a>
 </td>
 </tr>
-<tr data-index="369" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="339" data-listing-title-sort="Proposed: Polish demo of V-Sekai by making invisible meshes appear via the use of the exporter." data-listing-filename-sort="20211108-invisible-meshes-appear-via-the-use-of-the-exporter.md">
+<tr data-index="369" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="339" data-listing-title-sort="Proposed: Polish demo of V-Sekai by making invisible meshes appear via the use of the exporter." data-listing-filename-sort="20211108-invisible-meshes-appear-via-the-use-of-the-exporter.md">
 <td>
 <a href="./decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html" class="title listing-title">Proposed: Polish demo of V-Sekai by making invisible meshes appear via the use of the exporter.</a>
 </td>
@@ -4304,7 +4304,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html" class="filename listing-filename">20211108-invisible-meshes-appear-via-the-use-of-the-exporter.md</a>
 </td>
 </tr>
-<tr data-index="370" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="375" data-listing-title-sort="Proposed: Integrate with blender" data-listing-filename-sort="20211108-integrate-with-blender.md">
+<tr data-index="370" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="375" data-listing-title-sort="Proposed: Integrate with blender" data-listing-filename-sort="20211108-integrate-with-blender.md">
 <td>
 <a href="./decisions/20211108-integrate-with-blender.html" class="title listing-title">Proposed: Integrate with blender</a>
 </td>
@@ -4315,7 +4315,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211108-integrate-with-blender.html" class="filename listing-filename">20211108-integrate-with-blender.md</a>
 </td>
 </tr>
-<tr data-index="371" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="336" data-listing-title-sort="Draft: Preview #materialx materials on the Web in Godot Engine" data-listing-filename-sort="20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.md">
+<tr data-index="371" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="336" data-listing-title-sort="Draft: Preview #materialx materials on the Web in Godot Engine" data-listing-filename-sort="20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.md">
 <td>
 <a href="./decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html" class="title listing-title">Draft: Preview #materialx materials on the Web in Godot Engine</a>
 </td>
@@ -4326,7 +4326,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html" class="filename listing-filename">20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.md</a>
 </td>
 </tr>
-<tr data-index="372" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="329" data-listing-title-sort="Draft: Use single player WebXR in Godot Engine to prototype CASSIE." data-listing-filename-sort="20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.md">
+<tr data-index="372" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="329" data-listing-title-sort="Draft: Use single player WebXR in Godot Engine to prototype CASSIE." data-listing-filename-sort="20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.md">
 <td>
 <a href="./decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html" class="title listing-title">Draft: Use single player WebXR in Godot Engine to prototype CASSIE.</a>
 </td>
@@ -4337,7 +4337,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html" class="filename listing-filename">20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.md</a>
 </td>
 </tr>
-<tr data-index="373" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="3" data-listing-word-count-sort="508" data-listing-title-sort="Accepted: Take a list of 3D points that form a vaguely closed boundary in space and triangulate in Godot Engine" data-listing-filename-sort="20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.md">
+<tr data-index="373" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="3" data-listing-word-count-sort="508" data-listing-title-sort="Accepted: Take a list of 3D points that form a vaguely closed boundary in space and triangulate in Godot Engine" data-listing-filename-sort="20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.md">
 <td>
 <a href="./decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html" class="title listing-title">Accepted: Take a list of 3D points that form a vaguely closed boundary in space and triangulate in Godot Engine</a>
 </td>
@@ -4348,7 +4348,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html" class="filename listing-filename">20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.md</a>
 </td>
 </tr>
-<tr data-index="374" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="357" data-listing-title-sort="Rejected: Iterate faster on WasGo prototype by using Godot 3.4" data-listing-filename-sort="20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.md">
+<tr data-index="374" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="357" data-listing-title-sort="Rejected: Iterate faster on WasGo prototype by using Godot 3.4" data-listing-filename-sort="20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.md">
 <td>
 <a href="./decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html" class="title listing-title">Rejected: Iterate faster on WasGo prototype by using Godot 3.4</a>
 </td>
@@ -4359,7 +4359,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html" class="filename listing-filename">20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.md</a>
 </td>
 </tr>
-<tr data-index="375" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="335" data-listing-title-sort="Rejected: Have an WebXR version of V-Sekai that is more accessible" data-listing-filename-sort="20211105-have-an-webxr-version-of-v-sekai.md">
+<tr data-index="375" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="335" data-listing-title-sort="Rejected: Have an WebXR version of V-Sekai that is more accessible" data-listing-filename-sort="20211105-have-an-webxr-version-of-v-sekai.md">
 <td>
 <a href="./decisions/20211105-have-an-webxr-version-of-v-sekai.html" class="title listing-title">Rejected: Have an WebXR version of V-Sekai that is more accessible</a>
 </td>
@@ -4370,7 +4370,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211105-have-an-webxr-version-of-v-sekai.html" class="filename listing-filename">20211105-have-an-webxr-version-of-v-sekai.md</a>
 </td>
 </tr>
-<tr data-index="376" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="2" data-listing-word-count-sort="364" data-listing-title-sort="Draft: Research mesh tooling with nglod" data-listing-filename-sort="20211104-research-mesh-tooling-with-nglod.md">
+<tr data-index="376" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="364" data-listing-title-sort="Draft: Research mesh tooling with nglod" data-listing-filename-sort="20211104-research-mesh-tooling-with-nglod.md">
 <td>
 <a href="./decisions/20211104-research-mesh-tooling-with-nglod.html" class="title listing-title">Draft: Research mesh tooling with nglod</a>
 </td>
@@ -4381,7 +4381,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211104-research-mesh-tooling-with-nglod.html" class="filename listing-filename">20211104-research-mesh-tooling-with-nglod.md</a>
 </td>
 </tr>
-<tr data-index="377" data-listing-file-modified-sort="1730535490022" data-listing-reading-time-sort="3" data-listing-word-count-sort="482" data-listing-title-sort="Draft: Research mesh tooling with kaolin" data-listing-filename-sort="20211104-research-mesh-tooling-with-kaolin.md">
+<tr data-index="377" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="3" data-listing-word-count-sort="482" data-listing-title-sort="Draft: Research mesh tooling with kaolin" data-listing-filename-sort="20211104-research-mesh-tooling-with-kaolin.md">
 <td>
 <a href="./decisions/20211104-research-mesh-tooling-with-kaolin.html" class="title listing-title">Draft: Research mesh tooling with kaolin</a>
 </td>
@@ -4392,7 +4392,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211104-research-mesh-tooling-with-kaolin.html" class="filename listing-filename">20211104-research-mesh-tooling-with-kaolin.md</a>
 </td>
 </tr>
-<tr data-index="378" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="3" data-listing-word-count-sort="456" data-listing-title-sort="Draft: Use a standard reference platform called VFX Reference platform" data-listing-filename-sort="20211103-use-platform-called-vfx-reference-platform.md">
+<tr data-index="378" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="3" data-listing-word-count-sort="456" data-listing-title-sort="Draft: Use a standard reference platform called VFX Reference platform" data-listing-filename-sort="20211103-use-platform-called-vfx-reference-platform.md">
 <td>
 <a href="./decisions/20211103-use-platform-called-vfx-reference-platform.html" class="title listing-title">Draft: Use a standard reference platform called VFX Reference platform</a>
 </td>
@@ -4403,7 +4403,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211103-use-platform-called-vfx-reference-platform.html" class="filename listing-filename">20211103-use-platform-called-vfx-reference-platform.md</a>
 </td>
 </tr>
-<tr data-index="379" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="258" data-listing-title-sort="Accepted: VOIP" data-listing-filename-sort="20211031-voip.md">
+<tr data-index="379" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="258" data-listing-title-sort="Accepted: VOIP" data-listing-filename-sort="20211031-voip.md">
 <td>
 <a href="./decisions/20211031-voip.html" class="title listing-title">Accepted: VOIP</a>
 </td>
@@ -4414,7 +4414,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211031-voip.html" class="filename listing-filename">20211031-voip.md</a>
 </td>
 </tr>
-<tr data-index="380" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="3" data-listing-word-count-sort="445" data-listing-title-sort="Draft: VMD on VRM AnimationTree Node" data-listing-filename-sort="20211031-vmd-on-vrm-animationtree-node.md">
+<tr data-index="380" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="3" data-listing-word-count-sort="445" data-listing-title-sort="Draft: VMD on VRM AnimationTree Node" data-listing-filename-sort="20211031-vmd-on-vrm-animationtree-node.md">
 <td>
 <a href="./decisions/20211031-vmd-on-vrm-animationtree-node.html" class="title listing-title">Draft: VMD on VRM AnimationTree Node</a>
 </td>
@@ -4425,7 +4425,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211031-vmd-on-vrm-animationtree-node.html" class="filename listing-filename">20211031-vmd-on-vrm-animationtree-node.md</a>
 </td>
 </tr>
-<tr data-index="381" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="261" data-listing-title-sort="Draft: Verification tools" data-listing-filename-sort="20211031-verification-tools.md">
+<tr data-index="381" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="261" data-listing-title-sort="Draft: Verification tools" data-listing-filename-sort="20211031-verification-tools.md">
 <td>
 <a href="./decisions/20211031-verification-tools.html" class="title listing-title">Draft: Verification tools</a>
 </td>
@@ -4436,7 +4436,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211031-verification-tools.html" class="filename listing-filename">20211031-verification-tools.md</a>
 </td>
 </tr>
-<tr data-index="382" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="247" data-listing-title-sort="Accepted: Use our custom fullbody IK" data-listing-filename-sort="20211031-use-our-custom-fullbody-ik.md">
+<tr data-index="382" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="247" data-listing-title-sort="Accepted: Use our custom fullbody IK" data-listing-filename-sort="20211031-use-our-custom-fullbody-ik.md">
 <td>
 <a href="./decisions/20211031-use-our-custom-fullbody-ik.html" class="title listing-title">Accepted: Use our custom fullbody IK</a>
 </td>
@@ -4447,7 +4447,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211031-use-our-custom-fullbody-ik.html" class="filename listing-filename">20211031-use-our-custom-fullbody-ik.md</a>
 </td>
 </tr>
-<tr data-index="383" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="250" data-listing-title-sort="Proposed: Rank skeleton bone names by using BPR" data-listing-filename-sort="20211031-use-bpr-to-rank-skeleton-bone-names.md">
+<tr data-index="383" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="250" data-listing-title-sort="Proposed: Rank skeleton bone names by using BPR" data-listing-filename-sort="20211031-use-bpr-to-rank-skeleton-bone-names.md">
 <td>
 <a href="./decisions/20211031-use-bpr-to-rank-skeleton-bone-names.html" class="title listing-title">Proposed: Rank skeleton bone names by using BPR</a>
 </td>
@@ -4458,7 +4458,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211031-use-bpr-to-rank-skeleton-bone-names.html" class="filename listing-filename">20211031-use-bpr-to-rank-skeleton-bone-names.md</a>
 </td>
 </tr>
-<tr data-index="384" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="242" data-listing-title-sort="Proposed: Update URO for Godot 4" data-listing-filename-sort="20211031-update-uro-for-godot-4.md">
+<tr data-index="384" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="242" data-listing-title-sort="Proposed: Update URO for Godot 4" data-listing-filename-sort="20211031-update-uro-for-godot-4.md">
 <td>
 <a href="./decisions/20211031-update-uro-for-godot-4.html" class="title listing-title">Proposed: Update URO for Godot 4</a>
 </td>
@@ -4469,7 +4469,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211031-update-uro-for-godot-4.html" class="filename listing-filename">20211031-update-uro-for-godot-4.md</a>
 </td>
 </tr>
-<tr data-index="385" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="322" data-listing-title-sort="Proposed: Tire model car sim" data-listing-filename-sort="20211031-tire-model-car-sim.md">
+<tr data-index="385" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="322" data-listing-title-sort="Proposed: Tire model car sim" data-listing-filename-sort="20211031-tire-model-car-sim.md">
 <td>
 <a href="./decisions/20211031-tire-model-car-sim.html" class="title listing-title">Proposed: Tire model car sim</a>
 </td>
@@ -4480,7 +4480,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211031-tire-model-car-sim.html" class="filename listing-filename">20211031-tire-model-car-sim.md</a>
 </td>
 </tr>
-<tr data-index="386" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="253" data-listing-title-sort="Accepted: ThorVG" data-listing-filename-sort="20211031-thorvg.md">
+<tr data-index="386" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="253" data-listing-title-sort="Accepted: ThorVG" data-listing-filename-sort="20211031-thorvg.md">
 <td>
 <a href="./decisions/20211031-thorvg.html" class="title listing-title">Accepted: ThorVG</a>
 </td>
@@ -4491,7 +4491,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211031-thorvg.html" class="filename listing-filename">20211031-thorvg.md</a>
 </td>
 </tr>
-<tr data-index="387" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="276" data-listing-title-sort="Proposed: Take a streaming godot game and streaming the VRM to OpenSoundControl" data-listing-filename-sort="20211031-streaming-godot-to-opensoundcontrol.md">
+<tr data-index="387" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="276" data-listing-title-sort="Proposed: Take a streaming godot game and streaming the VRM to OpenSoundControl" data-listing-filename-sort="20211031-streaming-godot-to-opensoundcontrol.md">
 <td>
 <a href="./decisions/20211031-streaming-godot-to-opensoundcontrol.html" class="title listing-title">Proposed: Take a streaming godot game and streaming the VRM to OpenSoundControl</a>
 </td>
@@ -4502,7 +4502,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211031-streaming-godot-to-opensoundcontrol.html" class="filename listing-filename">20211031-streaming-godot-to-opensoundcontrol.md</a>
 </td>
 </tr>
-<tr data-index="388" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="254" data-listing-title-sort="Proposed: Stream shader motion" data-listing-filename-sort="20211031-stream-shader-motion.md">
+<tr data-index="388" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="254" data-listing-title-sort="Proposed: Stream shader motion" data-listing-filename-sort="20211031-stream-shader-motion.md">
 <td>
 <a href="./decisions/20211031-stream-shader-motion.html" class="title listing-title">Proposed: Stream shader motion</a>
 </td>
@@ -4513,7 +4513,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211031-stream-shader-motion.html" class="filename listing-filename">20211031-stream-shader-motion.md</a>
 </td>
 </tr>
-<tr data-index="389" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="318" data-listing-title-sort="Proposed: Standard backup procedures" data-listing-filename-sort="20211031-standard-backup-procedures.md">
+<tr data-index="389" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="318" data-listing-title-sort="Proposed: Standard backup procedures" data-listing-filename-sort="20211031-standard-backup-procedures.md">
 <td>
 <a href="./decisions/20211031-standard-backup-procedures.html" class="title listing-title">Proposed: Standard backup procedures</a>
 </td>
@@ -4524,7 +4524,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211031-standard-backup-procedures.html" class="filename listing-filename">20211031-standard-backup-procedures.md</a>
 </td>
 </tr>
-<tr data-index="390" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="251" data-listing-title-sort="Proposed: To provide a performance and portable script use WasGo" data-listing-filename-sort="20211031-script-as-a-binary.md">
+<tr data-index="390" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="251" data-listing-title-sort="Proposed: To provide a performance and portable script use WasGo" data-listing-filename-sort="20211031-script-as-a-binary.md">
 <td>
 <a href="./decisions/20211031-script-as-a-binary.html" class="title listing-title">Proposed: To provide a performance and portable script use WasGo</a>
 </td>
@@ -4535,7 +4535,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211031-script-as-a-binary.html" class="filename listing-filename">20211031-script-as-a-binary.md</a>
 </td>
 </tr>
-<tr data-index="391" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="381" data-listing-title-sort="Proposed: Run the maintenance scripts from Windows in Unix mode with msys2" data-listing-filename-sort="20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.md">
+<tr data-index="391" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="381" data-listing-title-sort="Proposed: Run the maintenance scripts from Windows in Unix mode with msys2" data-listing-filename-sort="20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.md">
 <td>
 <a href="./decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html" class="title listing-title">Proposed: Run the maintenance scripts from Windows in Unix mode with msys2</a>
 </td>
@@ -4546,7 +4546,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html" class="filename listing-filename">20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.md</a>
 </td>
 </tr>
-<tr data-index="392" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="324" data-listing-title-sort="Superseded: Play preprocessed #animation on any VRM model" data-listing-filename-sort="20211031-play-preprocessed-animations-on-any-vrm-model.md">
+<tr data-index="392" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="324" data-listing-title-sort="Superseded: Play preprocessed #animation on any VRM model" data-listing-filename-sort="20211031-play-preprocessed-animations-on-any-vrm-model.md">
 <td>
 <a href="./decisions/20211031-play-preprocessed-animations-on-any-vrm-model.html" class="title listing-title">Superseded: Play preprocessed #animation on any VRM model</a>
 </td>
@@ -4557,7 +4557,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211031-play-preprocessed-animations-on-any-vrm-model.html" class="filename listing-filename">20211031-play-preprocessed-animations-on-any-vrm-model.md</a>
 </td>
 </tr>
-<tr data-index="393" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="247" data-listing-title-sort="Proposed: Plausible npc behavior" data-listing-filename-sort="20211031-plausable-npc-behaviour.md">
+<tr data-index="393" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="247" data-listing-title-sort="Proposed: Plausible npc behavior" data-listing-filename-sort="20211031-plausable-npc-behaviour.md">
 <td>
 <a href="./decisions/20211031-plausable-npc-behaviour.html" class="title listing-title">Proposed: Plausible npc behavior</a>
 </td>
@@ -4568,7 +4568,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211031-plausable-npc-behaviour.html" class="filename listing-filename">20211031-plausable-npc-behaviour.md</a>
 </td>
 </tr>
-<tr data-index="394" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="354" data-listing-title-sort="Proposed: Phase out groups in the branding to make it more recognizable" data-listing-filename-sort="20211031-phase-out-groups-terminology-for-vskdefault.md">
+<tr data-index="394" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="354" data-listing-title-sort="Proposed: Phase out groups in the branding to make it more recognizable" data-listing-filename-sort="20211031-phase-out-groups-terminology-for-vskdefault.md">
 <td>
 <a href="./decisions/20211031-phase-out-groups-terminology-for-vskdefault.html" class="title listing-title">Proposed: Phase out groups in the branding to make it more recognizable</a>
 </td>
@@ -4579,7 +4579,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211031-phase-out-groups-terminology-for-vskdefault.html" class="filename listing-filename">20211031-phase-out-groups-terminology-for-vskdefault.md</a>
 </td>
 </tr>
-<tr data-index="395" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="241" data-listing-title-sort="Rejected: OpenVR for Godot Engine" data-listing-filename-sort="20211031-openvr-for-godot-engine.md">
+<tr data-index="395" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="241" data-listing-title-sort="Rejected: OpenVR for Godot Engine" data-listing-filename-sort="20211031-openvr-for-godot-engine.md">
 <td>
 <a href="./decisions/20211031-openvr-for-godot-engine.html" class="title listing-title">Rejected: OpenVR for Godot Engine</a>
 </td>
@@ -4590,7 +4590,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211031-openvr-for-godot-engine.html" class="filename listing-filename">20211031-openvr-for-godot-engine.md</a>
 </td>
 </tr>
-<tr data-index="396" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="285" data-listing-title-sort="Proposed: Membrane Framework streaming Mixer" data-listing-filename-sort="20211031-membrane-framework-streaming-mixer.md">
+<tr data-index="396" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="285" data-listing-title-sort="Proposed: Membrane Framework streaming Mixer" data-listing-filename-sort="20211031-membrane-framework-streaming-mixer.md">
 <td>
 <a href="./decisions/20211031-membrane-framework-streaming-mixer.html" class="title listing-title">Proposed: Membrane Framework streaming Mixer</a>
 </td>
@@ -4601,7 +4601,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211031-membrane-framework-streaming-mixer.html" class="filename listing-filename">20211031-membrane-framework-streaming-mixer.md</a>
 </td>
 </tr>
-<tr data-index="397" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="251" data-listing-title-sort="Proposed: Meeting area" data-listing-filename-sort="20211031-meeting-area.md">
+<tr data-index="397" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="251" data-listing-title-sort="Proposed: Meeting area" data-listing-filename-sort="20211031-meeting-area.md">
 <td>
 <a href="./decisions/20211031-meeting-area.html" class="title listing-title">Proposed: Meeting area</a>
 </td>
@@ -4612,7 +4612,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211031-meeting-area.html" class="filename listing-filename">20211031-meeting-area.md</a>
 </td>
 </tr>
-<tr data-index="398" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="244" data-listing-title-sort="Proposed: Make a place to record" data-listing-filename-sort="20211031-make-a-place-to-record.md">
+<tr data-index="398" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="244" data-listing-title-sort="Proposed: Make a place to record" data-listing-filename-sort="20211031-make-a-place-to-record.md">
 <td>
 <a href="./decisions/20211031-make-a-place-to-record.html" class="title listing-title">Proposed: Make a place to record</a>
 </td>
@@ -4623,7 +4623,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211031-make-a-place-to-record.html" class="filename listing-filename">20211031-make-a-place-to-record.md</a>
 </td>
 </tr>
-<tr data-index="399" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="352" data-listing-title-sort="Accepted: Keep a changelog" data-listing-filename-sort="20211031-keep-a-changelog.md">
+<tr data-index="399" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="352" data-listing-title-sort="Accepted: Keep a changelog" data-listing-filename-sort="20211031-keep-a-changelog.md">
 <td>
 <a href="./decisions/20211031-keep-a-changelog.html" class="title listing-title">Accepted: Keep a changelog</a>
 </td>
@@ -4634,7 +4634,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211031-keep-a-changelog.html" class="filename listing-filename">20211031-keep-a-changelog.md</a>
 </td>
 </tr>
-<tr data-index="400" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="284" data-listing-title-sort="Proposed: How to make a V-Sekai/godot update?" data-listing-filename-sort="20211031-how-to-make-a-v-sekaigodot-update.md">
+<tr data-index="400" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="284" data-listing-title-sort="Proposed: How to make a V-Sekai/godot update?" data-listing-filename-sort="20211031-how-to-make-a-v-sekaigodot-update.md">
 <td>
 <a href="./decisions/20211031-how-to-make-a-v-sekaigodot-update.html" class="title listing-title">Proposed: How to make a V-Sekai/godot update?</a>
 </td>
@@ -4645,7 +4645,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211031-how-to-make-a-v-sekaigodot-update.html" class="filename listing-filename">20211031-how-to-make-a-v-sekaigodot-update.md</a>
 </td>
 </tr>
-<tr data-index="401" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="246" data-listing-title-sort="Proposed: Have wires in 3d" data-listing-filename-sort="20211031-have-wires-in-3d.md">
+<tr data-index="401" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="246" data-listing-title-sort="Proposed: Have wires in 3d" data-listing-filename-sort="20211031-have-wires-in-3d.md">
 <td>
 <a href="./decisions/20211031-have-wires-in-3d.html" class="title listing-title">Proposed: Have wires in 3d</a>
 </td>
@@ -4656,7 +4656,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211031-have-wires-in-3d.html" class="filename listing-filename">20211031-have-wires-in-3d.md</a>
 </td>
 </tr>
-<tr data-index="402" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="250" data-listing-title-sort="Proposed: Have better user developer experience" data-listing-filename-sort="20211031-have-better-user-developer-experience.md">
+<tr data-index="402" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="250" data-listing-title-sort="Proposed: Have better user developer experience" data-listing-filename-sort="20211031-have-better-user-developer-experience.md">
 <td>
 <a href="./decisions/20211031-have-better-user-developer-experience.html" class="title listing-title">Proposed: Have better user developer experience</a>
 </td>
@@ -4667,7 +4667,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211031-have-better-user-developer-experience.html" class="filename listing-filename">20211031-have-better-user-developer-experience.md</a>
 </td>
 </tr>
-<tr data-index="403" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="3" data-listing-word-count-sort="405" data-listing-title-sort="Proposed: Godot Database viewer for proposals" data-listing-filename-sort="20211031-godot-database-viewer-for-proposals.md">
+<tr data-index="403" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="3" data-listing-word-count-sort="405" data-listing-title-sort="Proposed: Godot Database viewer for proposals" data-listing-filename-sort="20211031-godot-database-viewer-for-proposals.md">
 <td>
 <a href="./decisions/20211031-godot-database-viewer-for-proposals.html" class="title listing-title">Proposed: Godot Database viewer for proposals</a>
 </td>
@@ -4678,7 +4678,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211031-godot-database-viewer-for-proposals.html" class="filename listing-filename">20211031-godot-database-viewer-for-proposals.md</a>
 </td>
 </tr>
-<tr data-index="404" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="254" data-listing-title-sort="Proposed: glTF - importer should bind animation players to the closest root node" data-listing-filename-sort="20211031-gltf-importer-should-bind-animation-players-to-the-closest-root-node.md">
+<tr data-index="404" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="254" data-listing-title-sort="Proposed: glTF - importer should bind animation players to the closest root node" data-listing-filename-sort="20211031-gltf-importer-should-bind-animation-players-to-the-closest-root-node.md">
 <td>
 <a href="./decisions/20211031-gltf-importer-should-bind-animation-players-to-the-closest-root-node.html" class="title listing-title">Proposed: glTF - importer should bind animation players to the closest root node</a>
 </td>
@@ -4689,7 +4689,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211031-gltf-importer-should-bind-animation-players-to-the-closest-root-node.html" class="filename listing-filename">20211031-gltf-importer-should-bind-animation-players-to-the-closest-root-node.md</a>
 </td>
 </tr>
-<tr data-index="405" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="249" data-listing-title-sort="Proposed: Face motion tracking requires standard shapes" data-listing-filename-sort="20211031-face-motion-tracking-requires-standard-shapes.md">
+<tr data-index="405" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="249" data-listing-title-sort="Proposed: Face motion tracking requires standard shapes" data-listing-filename-sort="20211031-face-motion-tracking-requires-standard-shapes.md">
 <td>
 <a href="./decisions/20211031-face-motion-tracking-requires-standard-shapes.html" class="title listing-title">Proposed: Face motion tracking requires standard shapes</a>
 </td>
@@ -4700,7 +4700,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211031-face-motion-tracking-requires-standard-shapes.html" class="filename listing-filename">20211031-face-motion-tracking-requires-standard-shapes.md</a>
 </td>
 </tr>
-<tr data-index="406" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="23" data-listing-word-count-sort="4597" data-listing-title-sort="Proposed: Extract proposals into proposals" data-listing-filename-sort="20211031-extract-proposals-into-proposals.md">
+<tr data-index="406" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="23" data-listing-word-count-sort="4597" data-listing-title-sort="Proposed: Extract proposals into proposals" data-listing-filename-sort="20211031-extract-proposals-into-proposals.md">
 <td>
 <a href="./decisions/20211031-extract-proposals-into-proposals.html" class="title listing-title">Proposed: Extract proposals into proposals</a>
 </td>
@@ -4711,7 +4711,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211031-extract-proposals-into-proposals.html" class="filename listing-filename">20211031-extract-proposals-into-proposals.md</a>
 </td>
 </tr>
-<tr data-index="407" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="247" data-listing-title-sort="Proposed: Export / Import testing via robot-framework and swiftshader" data-listing-filename-sort="20211031-export-import-testing-via-robot-framework-and-swiftshader.md">
+<tr data-index="407" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="247" data-listing-title-sort="Proposed: Export / Import testing via robot-framework and swiftshader" data-listing-filename-sort="20211031-export-import-testing-via-robot-framework-and-swiftshader.md">
 <td>
 <a href="./decisions/20211031-export-import-testing-via-robot-framework-and-swiftshader.html" class="title listing-title">Proposed: Export / Import testing via robot-framework and swiftshader</a>
 </td>
@@ -4722,7 +4722,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211031-export-import-testing-via-robot-framework-and-swiftshader.html" class="filename listing-filename">20211031-export-import-testing-via-robot-framework-and-swiftshader.md</a>
 </td>
 </tr>
-<tr data-index="408" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="3" data-listing-word-count-sort="405" data-listing-title-sort="Proposed: Create a demo viewer gallery" data-listing-filename-sort="20211031-create-a-demo-viewer-gallery.md">
+<tr data-index="408" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="3" data-listing-word-count-sort="405" data-listing-title-sort="Proposed: Create a demo viewer gallery" data-listing-filename-sort="20211031-create-a-demo-viewer-gallery.md">
 <td>
 <a href="./decisions/20211031-create-a-demo-viewer-gallery.html" class="title listing-title">Proposed: Create a demo viewer gallery</a>
 </td>
@@ -4733,7 +4733,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211031-create-a-demo-viewer-gallery.html" class="filename listing-filename">20211031-create-a-demo-viewer-gallery.md</a>
 </td>
 </tr>
-<tr data-index="409" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="252" data-listing-title-sort="Proposed: Construct the virtual #world" data-listing-filename-sort="20211031-construct-the-virtual-world.md">
+<tr data-index="409" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="252" data-listing-title-sort="Proposed: Construct the virtual #world" data-listing-filename-sort="20211031-construct-the-virtual-world.md">
 <td>
 <a href="./decisions/20211031-construct-the-virtual-world.html" class="title listing-title">Proposed: Construct the virtual #world</a>
 </td>
@@ -4744,7 +4744,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211031-construct-the-virtual-world.html" class="filename listing-filename">20211031-construct-the-virtual-world.md</a>
 </td>
 </tr>
-<tr data-index="410" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="254" data-listing-title-sort="Proposed: Client and Mast" data-listing-filename-sort="20211031-client-and-mast.md">
+<tr data-index="410" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="254" data-listing-title-sort="Proposed: Client and Mast" data-listing-filename-sort="20211031-client-and-mast.md">
 <td>
 <a href="./decisions/20211031-client-and-mast.html" class="title listing-title">Proposed: Client and Mast</a>
 </td>
@@ -4755,7 +4755,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211031-client-and-mast.html" class="filename listing-filename">20211031-client-and-mast.md</a>
 </td>
 </tr>
-<tr data-index="411" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="243" data-listing-title-sort="Proposed: CICD Export V-Sekai" data-listing-filename-sort="20211031-cicd-export-v-sekai.md">
+<tr data-index="411" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="243" data-listing-title-sort="Proposed: CICD Export V-Sekai" data-listing-filename-sort="20211031-cicd-export-v-sekai.md">
 <td>
 <a href="./decisions/20211031-cicd-export-v-sekai.html" class="title listing-title">Proposed: CICD Export V-Sekai</a>
 </td>
@@ -4766,7 +4766,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211031-cicd-export-v-sekai.html" class="filename listing-filename">20211031-cicd-export-v-sekai.md</a>
 </td>
 </tr>
-<tr data-index="412" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="245" data-listing-title-sort="Proposed: Character workshop" data-listing-filename-sort="20211031-character-workshop.md">
+<tr data-index="412" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="245" data-listing-title-sort="Proposed: Character workshop" data-listing-filename-sort="20211031-character-workshop.md">
 <td>
 <a href="./decisions/20211031-character-workshop.html" class="title listing-title">Proposed: Character workshop</a>
 </td>
@@ -4777,7 +4777,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211031-character-workshop.html" class="filename listing-filename">20211031-character-workshop.md</a>
 </td>
 </tr>
-<tr data-index="413" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="319" data-listing-title-sort="Proposed: Benchmark #animation playback" data-listing-filename-sort="20211031-benchmark-animation-playback.md">
+<tr data-index="413" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="319" data-listing-title-sort="Proposed: Benchmark #animation playback" data-listing-filename-sort="20211031-benchmark-animation-playback.md">
 <td>
 <a href="./decisions/20211031-benchmark-animation-playback.html" class="title listing-title">Proposed: Benchmark #animation playback</a>
 </td>
@@ -4788,7 +4788,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211031-benchmark-animation-playback.html" class="filename listing-filename">20211031-benchmark-animation-playback.md</a>
 </td>
 </tr>
-<tr data-index="414" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="291" data-listing-title-sort="Proposed: Bake blend shape to skeleton animation" data-listing-filename-sort="20211031-bake-blend-shape-to-skeleton-animation.md">
+<tr data-index="414" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="291" data-listing-title-sort="Proposed: Bake blend shape to skeleton animation" data-listing-filename-sort="20211031-bake-blend-shape-to-skeleton-animation.md">
 <td>
 <a href="./decisions/20211031-bake-blend-shape-to-skeleton-animation.html" class="title listing-title">Proposed: Bake blend shape to skeleton animation</a>
 </td>
@@ -4799,7 +4799,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211031-bake-blend-shape-to-skeleton-animation.html" class="filename listing-filename">20211031-bake-blend-shape-to-skeleton-animation.md</a>
 </td>
 </tr>
-<tr data-index="415" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="326" data-listing-title-sort="Proposed: Bake a #materialx into a custom Godot StandardMaterial3D" data-listing-filename-sort="20211031-bake-a-materialx-into-a-custom-godot-standardmaterial3d.md">
+<tr data-index="415" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="326" data-listing-title-sort="Proposed: Bake a #materialx into a custom Godot StandardMaterial3D" data-listing-filename-sort="20211031-bake-a-materialx-into-a-custom-godot-standardmaterial3d.md">
 <td>
 <a href="./decisions/20211031-bake-a-materialx-into-a-custom-godot-standardmaterial3d.html" class="title listing-title">Proposed: Bake a #materialx into a custom Godot StandardMaterial3D</a>
 </td>
@@ -4810,7 +4810,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211031-bake-a-materialx-into-a-custom-godot-standardmaterial3d.html" class="filename listing-filename">20211031-bake-a-materialx-into-a-custom-godot-standardmaterial3d.md</a>
 </td>
 </tr>
-<tr data-index="416" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="244" data-listing-title-sort="Proposed: ARC radial menu" data-listing-filename-sort="20211031-arc-radial-menu.md">
+<tr data-index="416" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="244" data-listing-title-sort="Proposed: ARC radial menu" data-listing-filename-sort="20211031-arc-radial-menu.md">
 <td>
 <a href="./decisions/20211031-arc-radial-menu.html" class="title listing-title">Proposed: ARC radial menu</a>
 </td>
@@ -4821,7 +4821,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211031-arc-radial-menu.html" class="filename listing-filename">20211031-arc-radial-menu.md</a>
 </td>
 </tr>
-<tr data-index="417" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="243" data-listing-title-sort="Proposed: 1000 player servers" data-listing-filename-sort="20211031-1000-player-servers.md">
+<tr data-index="417" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="243" data-listing-title-sort="Proposed: 1000 player servers" data-listing-filename-sort="20211031-1000-player-servers.md">
 <td>
 <a href="./decisions/20211031-1000-player-servers.html" class="title listing-title">Proposed: 1000 player servers</a>
 </td>
@@ -4832,7 +4832,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211031-1000-player-servers.html" class="filename listing-filename">20211031-1000-player-servers.md</a>
 </td>
 </tr>
-<tr data-index="418" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="312" data-listing-title-sort="Proposed: We want to proxy udp datagrams at production quality of service." data-listing-filename-sort="20211005-we-want-to-proxy-udp-datagrams-at-production-quality-of-service.md">
+<tr data-index="418" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="312" data-listing-title-sort="Proposed: We want to proxy udp datagrams at production quality of service." data-listing-filename-sort="20211005-we-want-to-proxy-udp-datagrams-at-production-quality-of-service.md">
 <td>
 <a href="./decisions/20211005-we-want-to-proxy-udp-datagrams-at-production-quality-of-service.html" class="title listing-title">Proposed: We want to proxy udp datagrams at production quality of service.</a>
 </td>
@@ -4843,7 +4843,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211005-we-want-to-proxy-udp-datagrams-at-production-quality-of-service.html" class="filename listing-filename">20211005-we-want-to-proxy-udp-datagrams-at-production-quality-of-service.md</a>
 </td>
 </tr>
-<tr data-index="419" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="3" data-listing-word-count-sort="422" data-listing-title-sort="Proposed: Want to use the same cluster for the same web and native." data-listing-filename-sort="20211005-want-to-use-the-same-cluster-for-the-same-web-and-native.md">
+<tr data-index="419" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="3" data-listing-word-count-sort="422" data-listing-title-sort="Proposed: Want to use the same cluster for the same web and native." data-listing-filename-sort="20211005-want-to-use-the-same-cluster-for-the-same-web-and-native.md">
 <td>
 <a href="./decisions/20211005-want-to-use-the-same-cluster-for-the-same-web-and-native.html" class="title listing-title">Proposed: Want to use the same cluster for the same web and native.</a>
 </td>
@@ -4854,7 +4854,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211005-want-to-use-the-same-cluster-for-the-same-web-and-native.html" class="filename listing-filename">20211005-want-to-use-the-same-cluster-for-the-same-web-and-native.md</a>
 </td>
 </tr>
-<tr data-index="420" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="319" data-listing-title-sort="Proposed: Summon #friend and acquaintances via presence to the current world." data-listing-filename-sort="20211005-want-to-summon-friends-and-acquaintances-via-presence.md">
+<tr data-index="420" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="319" data-listing-title-sort="Proposed: Summon #friend and acquaintances via presence to the current world." data-listing-filename-sort="20211005-want-to-summon-friends-and-acquaintances-via-presence.md">
 <td>
 <a href="./decisions/20211005-want-to-summon-friends-and-acquaintances-via-presence.html" class="title listing-title">Proposed: Summon #friend and acquaintances via presence to the current world.</a>
 </td>
@@ -4865,7 +4865,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211005-want-to-summon-friends-and-acquaintances-via-presence.html" class="filename listing-filename">20211005-want-to-summon-friends-and-acquaintances-via-presence.md</a>
 </td>
 </tr>
-<tr data-index="421" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="260" data-listing-title-sort="Proposed: Use materialx for asset interchange" data-listing-filename-sort="20211005-use-materialx-for-asset-interchange.md">
+<tr data-index="421" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="260" data-listing-title-sort="Proposed: Use materialx for asset interchange" data-listing-filename-sort="20211005-use-materialx-for-asset-interchange.md">
 <td>
 <a href="./decisions/20211005-use-materialx-for-asset-interchange.html" class="title listing-title">Proposed: Use materialx for asset interchange</a>
 </td>
@@ -4876,7 +4876,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211005-use-materialx-for-asset-interchange.html" class="filename listing-filename">20211005-use-materialx-for-asset-interchange.md</a>
 </td>
 </tr>
-<tr data-index="422" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="270" data-listing-title-sort="Proposed: Use KVM to test our AMD APU test computer via Barrier." data-listing-filename-sort="20211005-use-kvm-to-test-our-amd-apu-test-computer-via-barrier.md">
+<tr data-index="422" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="270" data-listing-title-sort="Proposed: Use KVM to test our AMD APU test computer via Barrier." data-listing-filename-sort="20211005-use-kvm-to-test-our-amd-apu-test-computer-via-barrier.md">
 <td>
 <a href="./decisions/20211005-use-kvm-to-test-our-amd-apu-test-computer-via-barrier.html" class="title listing-title">Proposed: Use KVM to test our AMD APU test computer via Barrier.</a>
 </td>
@@ -4887,7 +4887,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211005-use-kvm-to-test-our-amd-apu-test-computer-via-barrier.html" class="filename listing-filename">20211005-use-kvm-to-test-our-amd-apu-test-computer-via-barrier.md</a>
 </td>
 </tr>
-<tr data-index="423" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="3" data-listing-word-count-sort="462" data-listing-title-sort="Proposed: Test Google Mediapipe" data-listing-filename-sort="20211005-test-google-mediapipe.md">
+<tr data-index="423" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="3" data-listing-word-count-sort="462" data-listing-title-sort="Proposed: Test Google Mediapipe" data-listing-filename-sort="20211005-test-google-mediapipe.md">
 <td>
 <a href="./decisions/20211005-test-google-mediapipe.html" class="title listing-title">Proposed: Test Google Mediapipe</a>
 </td>
@@ -4898,7 +4898,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211005-test-google-mediapipe.html" class="filename listing-filename">20211005-test-google-mediapipe.md</a>
 </td>
 </tr>
-<tr data-index="424" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="309" data-listing-title-sort="Proposed: Solve Mocap By Connecting Mediapipe to Blender" data-listing-filename-sort="20211005-solve-mocap-by-connecting-mediapipe-to-blender.md">
+<tr data-index="424" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="309" data-listing-title-sort="Proposed: Solve Mocap By Connecting Mediapipe to Blender" data-listing-filename-sort="20211005-solve-mocap-by-connecting-mediapipe-to-blender.md">
 <td>
 <a href="./decisions/20211005-solve-mocap-by-connecting-mediapipe-to-blender.html" class="title listing-title">Proposed: Solve Mocap By Connecting Mediapipe to Blender</a>
 </td>
@@ -4909,7 +4909,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211005-solve-mocap-by-connecting-mediapipe-to-blender.html" class="filename listing-filename">20211005-solve-mocap-by-connecting-mediapipe-to-blender.md</a>
 </td>
 </tr>
-<tr data-index="425" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="260" data-listing-title-sort="Proposed: Improve Meshing Results by Subdivision in Godot Engine" data-listing-filename-sort="20211005-improve-meshing-results-by-subdivision-in-godot-engine.md">
+<tr data-index="425" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="260" data-listing-title-sort="Proposed: Improve Meshing Results by Subdivision in Godot Engine" data-listing-filename-sort="20211005-improve-meshing-results-by-subdivision-in-godot-engine.md">
 <td>
 <a href="./decisions/20211005-improve-meshing-results-by-subdivision-in-godot-engine.html" class="title listing-title">Proposed: Improve Meshing Results by Subdivision in Godot Engine</a>
 </td>
@@ -4920,7 +4920,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211005-improve-meshing-results-by-subdivision-in-godot-engine.html" class="filename listing-filename">20211005-improve-meshing-results-by-subdivision-in-godot-engine.md</a>
 </td>
 </tr>
-<tr data-index="426" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="288" data-listing-title-sort="Proposed: Create SOP for VRM #creation" data-listing-filename-sort="20211005-create-sop-for-vrm-creation.md">
+<tr data-index="426" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="288" data-listing-title-sort="Proposed: Create SOP for VRM #creation" data-listing-filename-sort="20211005-create-sop-for-vrm-creation.md">
 <td>
 <a href="./decisions/20211005-create-sop-for-vrm-creation.html" class="title listing-title">Proposed: Create SOP for VRM #creation</a>
 </td>
@@ -4931,7 +4931,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211005-create-sop-for-vrm-creation.html" class="filename listing-filename">20211005-create-sop-for-vrm-creation.md</a>
 </td>
 </tr>
-<tr data-index="427" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="315" data-listing-title-sort="Proposed: Create a standard procedure from adding spring bones to VRM models." data-listing-filename-sort="20211005-create-add-spring-bones-to-vrm-models.md">
+<tr data-index="427" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="315" data-listing-title-sort="Proposed: Create a standard procedure from adding spring bones to VRM models." data-listing-filename-sort="20211005-create-add-spring-bones-to-vrm-models.md">
 <td>
 <a href="./decisions/20211005-create-add-spring-bones-to-vrm-models.html" class="title listing-title">Proposed: Create a standard procedure from adding spring bones to VRM models.</a>
 </td>
@@ -4942,7 +4942,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211005-create-add-spring-bones-to-vrm-models.html" class="filename listing-filename">20211005-create-add-spring-bones-to-vrm-models.md</a>
 </td>
 </tr>
-<tr data-index="428" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="256" data-listing-title-sort="Proposed: Music is important to human experience and should be bridged to XR" data-listing-filename-sort="20211005-bridge-music-to-xr.md">
+<tr data-index="428" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="256" data-listing-title-sort="Proposed: Music is important to human experience and should be bridged to XR" data-listing-filename-sort="20211005-bridge-music-to-xr.md">
 <td>
 <a href="./decisions/20211005-bridge-music-to-xr.html" class="title listing-title">Proposed: Music is important to human experience and should be bridged to XR</a>
 </td>
@@ -4953,7 +4953,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20211005-bridge-music-to-xr.html" class="filename listing-filename">20211005-bridge-music-to-xr.md</a>
 </td>
 </tr>
-<tr data-index="429" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="308" data-listing-title-sort="Proposed: Spoke to V-Sekai" data-listing-filename-sort="20210811-spoke-to-v-sekai.md">
+<tr data-index="429" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="308" data-listing-title-sort="Proposed: Spoke to V-Sekai" data-listing-filename-sort="20210811-spoke-to-v-sekai.md">
 <td>
 <a href="./decisions/20210811-spoke-to-v-sekai.html" class="title listing-title">Proposed: Spoke to V-Sekai</a>
 </td>
@@ -4964,7 +4964,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20210811-spoke-to-v-sekai.html" class="filename listing-filename">20210811-spoke-to-v-sekai.md</a>
 </td>
 </tr>
-<tr data-index="430" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="3" data-listing-word-count-sort="543" data-listing-title-sort="Proposed: Soiree party mode" data-listing-filename-sort="20210811-soiree-party.md">
+<tr data-index="430" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="3" data-listing-word-count-sort="543" data-listing-title-sort="Proposed: Soiree party mode" data-listing-filename-sort="20210811-soiree-party.md">
 <td>
 <a href="./decisions/20210811-soiree-party.html" class="title listing-title">Proposed: Soiree party mode</a>
 </td>
@@ -4975,7 +4975,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20210811-soiree-party.html" class="filename listing-filename">20210811-soiree-party.md</a>
 </td>
 </tr>
-<tr data-index="431" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="308" data-listing-title-sort="Proposed: OMI Glb Portable Content" data-listing-filename-sort="20210811-omi-glb.md">
+<tr data-index="431" data-listing-file-modified-sort="1730559023670" data-listing-reading-time-sort="2" data-listing-word-count-sort="308" data-listing-title-sort="Proposed: OMI Glb Portable Content" data-listing-filename-sort="20210811-omi-glb.md">
 <td>
 <a href="./decisions/20210811-omi-glb.html" class="title listing-title">Proposed: OMI Glb Portable Content</a>
 </td>
@@ -4986,7 +4986,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20210811-omi-glb.html" class="filename listing-filename">20210811-omi-glb.md</a>
 </td>
 </tr>
-<tr data-index="432" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="3" data-listing-word-count-sort="429" data-listing-title-sort="Proposed: Neural Blend Shape Rigging" data-listing-filename-sort="20210811-neural-blend-shape-rigging.md">
+<tr data-index="432" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="3" data-listing-word-count-sort="429" data-listing-title-sort="Proposed: Neural Blend Shape Rigging" data-listing-filename-sort="20210811-neural-blend-shape-rigging.md">
 <td>
 <a href="./decisions/20210811-neural-blend-shape-rigging.html" class="title listing-title">Proposed: Neural Blend Shape Rigging</a>
 </td>
@@ -4997,7 +4997,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20210811-neural-blend-shape-rigging.html" class="filename listing-filename">20210811-neural-blend-shape-rigging.md</a>
 </td>
 </tr>
-<tr data-index="433" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="291" data-listing-title-sort="Proposed: Import Minecraft worlds to Godot Engine" data-listing-filename-sort="20210811-minecraft-voxel.md">
+<tr data-index="433" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="2" data-listing-word-count-sort="291" data-listing-title-sort="Proposed: Import Minecraft worlds to Godot Engine" data-listing-filename-sort="20210811-minecraft-voxel.md">
 <td>
 <a href="./decisions/20210811-minecraft-voxel.html" class="title listing-title">Proposed: Import Minecraft worlds to Godot Engine</a>
 </td>
@@ -5008,7 +5008,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20210811-minecraft-voxel.html" class="filename listing-filename">20210811-minecraft-voxel.md</a>
 </td>
 </tr>
-<tr data-index="434" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="3" data-listing-word-count-sort="522" data-listing-title-sort="Proposed: Minimum Specification V-Sekai Hardware" data-listing-filename-sort="20210811-min-spec-v-sekai.md">
+<tr data-index="434" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="3" data-listing-word-count-sort="522" data-listing-title-sort="Proposed: Minimum Specification V-Sekai Hardware" data-listing-filename-sort="20210811-min-spec-v-sekai.md">
 <td>
 <a href="./decisions/20210811-min-spec-v-sekai.html" class="title listing-title">Proposed: Minimum Specification V-Sekai Hardware</a>
 </td>
@@ -5019,7 +5019,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20210811-min-spec-v-sekai.html" class="filename listing-filename">20210811-min-spec-v-sekai.md</a>
 </td>
 </tr>
-<tr data-index="435" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="345" data-listing-title-sort="Accepted: OIT in Godot Engine" data-listing-filename-sort="20210811-godot-transparency.md">
+<tr data-index="435" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="2" data-listing-word-count-sort="345" data-listing-title-sort="Accepted: OIT in Godot Engine" data-listing-filename-sort="20210811-godot-transparency.md">
 <td>
 <a href="./decisions/20210811-godot-transparency.html" class="title listing-title">Accepted: OIT in Godot Engine</a>
 </td>
@@ -5030,7 +5030,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20210811-godot-transparency.html" class="filename listing-filename">20210811-godot-transparency.md</a>
 </td>
 </tr>
-<tr data-index="436" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="290" data-listing-title-sort="Proposed: GLB data in a Movie" data-listing-filename-sort="20210811-glb-in-video.md">
+<tr data-index="436" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="2" data-listing-word-count-sort="290" data-listing-title-sort="Proposed: GLB data in a Movie" data-listing-filename-sort="20210811-glb-in-video.md">
 <td>
 <a href="./decisions/20210811-glb-in-video.html" class="title listing-title">Proposed: GLB data in a Movie</a>
 </td>
@@ -5041,7 +5041,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20210811-glb-in-video.html" class="filename listing-filename">20210811-glb-in-video.md</a>
 </td>
 </tr>
-<tr data-index="437" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="277" data-listing-title-sort="Proposed: Membrane Framework to Process Game Workflows" data-listing-filename-sort="20210811-game-workflow-membrane.md">
+<tr data-index="437" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="2" data-listing-word-count-sort="277" data-listing-title-sort="Proposed: Membrane Framework to Process Game Workflows" data-listing-filename-sort="20210811-game-workflow-membrane.md">
 <td>
 <a href="./decisions/20210811-game-workflow-membrane.html" class="title listing-title">Proposed: Membrane Framework to Process Game Workflows</a>
 </td>
@@ -5052,7 +5052,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20210811-game-workflow-membrane.html" class="filename listing-filename">20210811-game-workflow-membrane.md</a>
 </td>
 </tr>
-<tr data-index="438" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="256" data-listing-title-sort="Proposed: Godot Engine implementation of disconnected IPFS" data-listing-filename-sort="20210811-disconnected-ipfs.md">
+<tr data-index="438" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="2" data-listing-word-count-sort="256" data-listing-title-sort="Proposed: Godot Engine implementation of disconnected IPFS" data-listing-filename-sort="20210811-disconnected-ipfs.md">
 <td>
 <a href="./decisions/20210811-disconnected-ipfs.html" class="title listing-title">Proposed: Godot Engine implementation of disconnected IPFS</a>
 </td>
@@ -5063,7 +5063,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20210811-disconnected-ipfs.html" class="filename listing-filename">20210811-disconnected-ipfs.md</a>
 </td>
 </tr>
-<tr data-index="439" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="4" data-listing-word-count-sort="663" data-listing-title-sort="Proposed: Spreadsheet Animation Preview" data-listing-filename-sort="20210724-Spreadsheet-animation-preview.md">
+<tr data-index="439" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="4" data-listing-word-count-sort="663" data-listing-title-sort="Proposed: Spreadsheet Animation Preview" data-listing-filename-sort="20210724-Spreadsheet-animation-preview.md">
 <td>
 <a href="./decisions/20210724-Spreadsheet-animation-preview.html" class="title listing-title">Proposed: Spreadsheet Animation Preview</a>
 </td>
@@ -5074,7 +5074,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20210724-Spreadsheet-animation-preview.html" class="filename listing-filename">20210724-Spreadsheet-animation-preview.md</a>
 </td>
 </tr>
-<tr data-index="440" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="317" data-listing-title-sort="Proposed: Portable #world Content" data-listing-filename-sort="20210715-portable-world-content.md">
+<tr data-index="440" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="2" data-listing-word-count-sort="317" data-listing-title-sort="Proposed: Portable #world Content" data-listing-filename-sort="20210715-portable-world-content.md">
 <td>
 <a href="./decisions/20210715-portable-world-content.html" class="title listing-title">Proposed: Portable #world Content</a>
 </td>
@@ -5085,7 +5085,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20210715-portable-world-content.html" class="filename listing-filename">20210715-portable-world-content.md</a>
 </td>
 </tr>
-<tr data-index="441" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="273" data-listing-title-sort="Proposed: Material Addon Blender" data-listing-filename-sort="20210715-Material-Addon-Blender.md">
+<tr data-index="441" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="2" data-listing-word-count-sort="273" data-listing-title-sort="Proposed: Material Addon Blender" data-listing-filename-sort="20210715-Material-Addon-Blender.md">
 <td>
 <a href="./decisions/20210715-Material-Addon-Blender.html" class="title listing-title">Proposed: Material Addon Blender</a>
 </td>
@@ -5096,7 +5096,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20210715-Material-Addon-Blender.html" class="filename listing-filename">20210715-Material-Addon-Blender.md</a>
 </td>
 </tr>
-<tr data-index="442" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="290" data-listing-title-sort="Proposed: Describe a Godot Engine pr verification workflow" data-listing-filename-sort="20210710-verify-pr-workflow.md">
+<tr data-index="442" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="2" data-listing-word-count-sort="290" data-listing-title-sort="Proposed: Describe a Godot Engine pr verification workflow" data-listing-filename-sort="20210710-verify-pr-workflow.md">
 <td>
 <a href="./decisions/20210710-verify-pr-workflow.html" class="title listing-title">Proposed: Describe a Godot Engine pr verification workflow</a>
 </td>
@@ -5107,7 +5107,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20210710-verify-pr-workflow.html" class="filename listing-filename">20210710-verify-pr-workflow.md</a>
 </td>
 </tr>
-<tr data-index="443" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="3" data-listing-word-count-sort="538" data-listing-title-sort="Proposed: Transfer animation by baking reset" data-listing-filename-sort="20210707-transfer-animations-by-baking-reset.md">
+<tr data-index="443" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="3" data-listing-word-count-sort="538" data-listing-title-sort="Proposed: Transfer animation by baking reset" data-listing-filename-sort="20210707-transfer-animations-by-baking-reset.md">
 <td>
 <a href="./decisions/20210707-transfer-animations-by-baking-reset.html" class="title listing-title">Proposed: Transfer animation by baking reset</a>
 </td>
@@ -5118,7 +5118,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20210707-transfer-animations-by-baking-reset.html" class="filename listing-filename">20210707-transfer-animations-by-baking-reset.md</a>
 </td>
 </tr>
-<tr data-index="444" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="386" data-listing-title-sort="Proposed: Convert #shadermotion to be played in Godot Engine" data-listing-filename-sort="20210622-shadermotion-to-godot-engine.md">
+<tr data-index="444" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="2" data-listing-word-count-sort="386" data-listing-title-sort="Proposed: Convert #shadermotion to be played in Godot Engine" data-listing-filename-sort="20210622-shadermotion-to-godot-engine.md">
 <td>
 <a href="./decisions/20210622-shadermotion-to-godot-engine.html" class="title listing-title">Proposed: Convert #shadermotion to be played in Godot Engine</a>
 </td>
@@ -5129,7 +5129,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20210622-shadermotion-to-godot-engine.html" class="filename listing-filename">20210622-shadermotion-to-godot-engine.md</a>
 </td>
 </tr>
-<tr data-index="445" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="351" data-listing-title-sort="Proposed: Convert FBX and glTF2 to VRM via flow-avatar-asset-pipeline" data-listing-filename-sort="20210612-flow-avatar-asset-pipeline.md">
+<tr data-index="445" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="2" data-listing-word-count-sort="351" data-listing-title-sort="Proposed: Convert FBX and glTF2 to VRM via flow-avatar-asset-pipeline" data-listing-filename-sort="20210612-flow-avatar-asset-pipeline.md">
 <td>
 <a href="./decisions/20210612-flow-avatar-asset-pipeline.html" class="title listing-title">Proposed: Convert FBX and glTF2 to VRM via flow-avatar-asset-pipeline</a>
 </td>
@@ -5140,7 +5140,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20210612-flow-avatar-asset-pipeline.html" class="filename listing-filename">20210612-flow-avatar-asset-pipeline.md</a>
 </td>
 </tr>
-<tr data-index="446" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="3" data-listing-word-count-sort="513" data-listing-title-sort="Proposed: Store presentation and book content via Lottie" data-listing-filename-sort="20210601-store-presentation-and-book-content-via-lottie-2.md">
+<tr data-index="446" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="3" data-listing-word-count-sort="513" data-listing-title-sort="Proposed: Store presentation and book content via Lottie" data-listing-filename-sort="20210601-store-presentation-and-book-content-via-lottie-2.md">
 <td>
 <a href="./decisions/20210601-store-presentation-and-book-content-via-lottie-2.html" class="title listing-title">Proposed: Store presentation and book content via Lottie</a>
 </td>
@@ -5151,7 +5151,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20210601-store-presentation-and-book-content-via-lottie-2.html" class="filename listing-filename">20210601-store-presentation-and-book-content-via-lottie-2.md</a>
 </td>
 </tr>
-<tr data-index="447" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="348" data-listing-title-sort="Proposed: Performance profile the game with AMDuProf" data-listing-filename-sort="20210529-performance-profiling.md">
+<tr data-index="447" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="2" data-listing-word-count-sort="348" data-listing-title-sort="Proposed: Performance profile the game with AMDuProf" data-listing-filename-sort="20210529-performance-profiling.md">
 <td>
 <a href="./decisions/20210529-performance-profiling.html" class="title listing-title">Proposed: Performance profile the game with AMDuProf</a>
 </td>
@@ -5162,7 +5162,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20210529-performance-profiling.html" class="filename listing-filename">20210529-performance-profiling.md</a>
 </td>
 </tr>
-<tr data-index="448" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="328" data-listing-title-sort="Proposed: Trial install of Gravity for Kubernetes" data-listing-filename-sort="20210528-trial-install-of-gravity-for-kubernetes.md">
+<tr data-index="448" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="2" data-listing-word-count-sort="328" data-listing-title-sort="Proposed: Trial install of Gravity for Kubernetes" data-listing-filename-sort="20210528-trial-install-of-gravity-for-kubernetes.md">
 <td>
 <a href="./decisions/20210528-trial-install-of-gravity-for-kubernetes.html" class="title listing-title">Proposed: Trial install of Gravity for Kubernetes</a>
 </td>
@@ -5173,7 +5173,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20210528-trial-install-of-gravity-for-kubernetes.html" class="filename listing-filename">20210528-trial-install-of-gravity-for-kubernetes.md</a>
 </td>
 </tr>
-<tr data-index="449" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="328" data-listing-title-sort="Proposed: Simplify Meshes and LODs better with Quads" data-listing-filename-sort="20210523-simplfy-meshes-and-lods-better-with-quads.md">
+<tr data-index="449" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="2" data-listing-word-count-sort="328" data-listing-title-sort="Proposed: Simplify Meshes and LODs better with Quads" data-listing-filename-sort="20210523-simplfy-meshes-and-lods-better-with-quads.md">
 <td>
 <a href="./decisions/20210523-simplfy-meshes-and-lods-better-with-quads.html" class="title listing-title">Proposed: Simplify Meshes and LODs better with Quads</a>
 </td>
@@ -5184,7 +5184,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20210523-simplfy-meshes-and-lods-better-with-quads.html" class="filename listing-filename">20210523-simplfy-meshes-and-lods-better-with-quads.md</a>
 </td>
 </tr>
-<tr data-index="450" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="4" data-listing-word-count-sort="662" data-listing-title-sort="Proposed: Retarget VRM Motion Blender Workflow" data-listing-filename-sort="20210523-retarget-motion-for-vrm-type-models.md">
+<tr data-index="450" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="4" data-listing-word-count-sort="662" data-listing-title-sort="Proposed: Retarget VRM Motion Blender Workflow" data-listing-filename-sort="20210523-retarget-motion-for-vrm-type-models.md">
 <td>
 <a href="./decisions/20210523-retarget-motion-for-vrm-type-models.html" class="title listing-title">Proposed: Retarget VRM Motion Blender Workflow</a>
 </td>
@@ -5195,7 +5195,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20210523-retarget-motion-for-vrm-type-models.html" class="filename listing-filename">20210523-retarget-motion-for-vrm-type-models.md</a>
 </td>
 </tr>
-<tr data-index="451" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="3" data-listing-word-count-sort="407" data-listing-title-sort="Proposed: Distribute trusted clients with notary" data-listing-filename-sort="20210523-distribute-trusted-clients-with-notary.md">
+<tr data-index="451" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="3" data-listing-word-count-sort="407" data-listing-title-sort="Proposed: Distribute trusted clients with notary" data-listing-filename-sort="20210523-distribute-trusted-clients-with-notary.md">
 <td>
 <a href="./decisions/20210523-distribute-trusted-clients-with-notary.html" class="title listing-title">Proposed: Distribute trusted clients with notary</a>
 </td>
@@ -5206,7 +5206,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20210523-distribute-trusted-clients-with-notary.html" class="filename listing-filename">20210523-distribute-trusted-clients-with-notary.md</a>
 </td>
 </tr>
-<tr data-index="452" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="320" data-listing-title-sort="Accepted: Complete glTF2 / VRM import and export pipeline in Godot Engine" data-listing-filename-sort="20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.md">
+<tr data-index="452" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="2" data-listing-word-count-sort="320" data-listing-title-sort="Accepted: Complete glTF2 / VRM import and export pipeline in Godot Engine" data-listing-filename-sort="20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.md">
 <td>
 <a href="./decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html" class="title listing-title">Accepted: Complete glTF2 / VRM import and export pipeline in Godot Engine</a>
 </td>
@@ -5217,7 +5217,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html" class="filename listing-filename">20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.md</a>
 </td>
 </tr>
-<tr data-index="453" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="251" data-listing-title-sort="Accepted: Support more flexible texture import via Basis Universal in Godot Engine" data-listing-filename-sort="20210523-basis-universal-import.md">
+<tr data-index="453" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="2" data-listing-word-count-sort="251" data-listing-title-sort="Accepted: Support more flexible texture import via Basis Universal in Godot Engine" data-listing-filename-sort="20210523-basis-universal-import.md">
 <td>
 <a href="./decisions/20210523-basis-universal-import.html" class="title listing-title">Accepted: Support more flexible texture import via Basis Universal in Godot Engine</a>
 </td>
@@ -5228,7 +5228,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20210523-basis-universal-import.html" class="filename listing-filename">20210523-basis-universal-import.md</a>
 </td>
 </tr>
-<tr data-index="454" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="358" data-listing-title-sort="Accepted: Use Markdown Architectural Decision Records" data-listing-filename-sort="20210212-use-markdown-architectural-decision-records.md">
+<tr data-index="454" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="2" data-listing-word-count-sort="358" data-listing-title-sort="Accepted: Use Markdown Architectural Decision Records" data-listing-filename-sort="20210212-use-markdown-architectural-decision-records.md">
 <td>
 <a href="./decisions/20210212-use-markdown-architectural-decision-records.html" class="title listing-title">Accepted: Use Markdown Architectural Decision Records</a>
 </td>
@@ -5239,7 +5239,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20210212-use-markdown-architectural-decision-records.html" class="filename listing-filename">20210212-use-markdown-architectural-decision-records.md</a>
 </td>
 </tr>
-<tr data-index="455" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="235" data-listing-title-sort="Superseded: Use Log4brains to manage the ADRs" data-listing-filename-sort="20210212-use-log4brains-to-manage-the-adrs.md">
+<tr data-index="455" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="2" data-listing-word-count-sort="235" data-listing-title-sort="Superseded: Use Log4brains to manage the ADRs" data-listing-filename-sort="20210212-use-log4brains-to-manage-the-adrs.md">
 <td>
 <a href="./decisions/20210212-use-log4brains-to-manage-the-adrs.html" class="title listing-title">Superseded: Use Log4brains to manage the ADRs</a>
 </td>
@@ -5250,7 +5250,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20210212-use-log4brains-to-manage-the-adrs.html" class="filename listing-filename">20210212-use-log4brains-to-manage-the-adrs.md</a>
 </td>
 </tr>
-<tr data-index="456" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="2" data-listing-word-count-sort="266" data-listing-title-sort="Proposed: Add build notifications" data-listing-filename-sort="20210212-add-build-notifications.md">
+<tr data-index="456" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="2" data-listing-word-count-sort="266" data-listing-title-sort="Proposed: Add build notifications" data-listing-filename-sort="20210212-add-build-notifications.md">
 <td>
 <a href="./decisions/20210212-add-build-notifications.html" class="title listing-title">Proposed: Add build notifications</a>
 </td>
@@ -5261,7 +5261,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20210212-add-build-notifications.html" class="filename listing-filename">20210212-add-build-notifications.md</a>
 </td>
 </tr>
-<tr data-index="457" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="7" data-listing-word-count-sort="1359" data-listing-title-sort="Accepted: Adding Entity Networking to Groups" data-listing-filename-sort="20200729-entity-networking.md">
+<tr data-index="457" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="7" data-listing-word-count-sort="1359" data-listing-title-sort="Accepted: Adding Entity Networking to Groups" data-listing-filename-sort="20200729-entity-networking.md">
 <td>
 <a href="./decisions/20200729-entity-networking.html" class="title listing-title">Accepted: Adding Entity Networking to Groups</a>
 </td>
@@ -5272,7 +5272,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20200729-entity-networking.html" class="filename listing-filename">20200729-entity-networking.md</a>
 </td>
 </tr>
-<tr data-index="458" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="12" data-listing-word-count-sort="2279" data-listing-title-sort="Mozilla Builders Summer MVP Lab (SUBMITTED ON JUNE 8 2020)" data-listing-filename-sort="20200608-vsekai-charter.md">
+<tr data-index="458" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="12" data-listing-word-count-sort="2279" data-listing-title-sort="Mozilla Builders Summer MVP Lab (SUBMITTED ON JUNE 8 2020)" data-listing-filename-sort="20200608-vsekai-charter.md">
 <td>
 <a href="./decisions/20200608-vsekai-charter.html" class="title listing-title">Mozilla Builders Summer MVP Lab (SUBMITTED ON JUNE 8 2020)</a>
 </td>
@@ -5283,7 +5283,7 @@ <h1 class="title">Decisions of V-Sekai</h1>
 <a href="./decisions/20200608-vsekai-charter.html" class="filename listing-filename">20200608-vsekai-charter.md</a>
 </td>
 </tr>
-<tr data-index="459" data-listing-file-modified-sort="1730535490018" data-listing-reading-time-sort="26" data-listing-word-count-sort="5049" data-listing-title-sort="Accepted: Manage backend resources on one or more physical machines with K3S" data-listing-filename-sort="20200602-manage-backend-with-k3s.md">
+<tr data-index="459" data-listing-file-modified-sort="1730559023666" data-listing-reading-time-sort="26" data-listing-word-count-sort="5049" data-listing-title-sort="Accepted: Manage backend resources on one or more physical machines with K3S" data-listing-filename-sort="20200602-manage-backend-with-k3s.md">
 <td>
 <a href="./decisions/20200602-manage-backend-with-k3s.html" class="title listing-title">Accepted: Manage backend resources on one or more physical machines with K3S</a>
 </td>
diff --git a/docs/decisions.xml b/docs/decisions.xml
index e7031c9d85..fff2076238 100644
--- a/docs/decisions.xml
+++ b/docs/decisions.xml
@@ -10,7 +10,7 @@
 <atom:link href="https://v-sekai.github.io/manuals/decisions.xml" rel="self" type="application/rss+xml"/>
 <description></description>
 <generator>quarto-1.5.57</generator>
-<lastBuildDate>Sat, 02 Nov 2024 08:18:48 GMT</lastBuildDate>
+<lastBuildDate>Sat, 02 Nov 2024 14:50:43 GMT</lastBuildDate>
 <item>
   <title></title>
   <link>https://v-sekai.github.io/manuals/decisions/present-proposal-template.html</link>
@@ -75,7 +75,7 @@
 
  ]]></description>
   <guid>https://v-sekai.github.io/manuals/decisions/present-proposal-template.html</guid>
-  <pubDate>Sat, 02 Nov 2024 08:18:48 GMT</pubDate>
+  <pubDate>Sat, 02 Nov 2024 14:50:43 GMT</pubDate>
 </item>
 <item>
   <title></title>
@@ -161,7 +161,7 @@
 
  ]]></description>
   <guid>https://v-sekai.github.io/manuals/decisions/ai-assisted-proposal-style-guide.html</guid>
-  <pubDate>Sat, 02 Nov 2024 08:18:48 GMT</pubDate>
+  <pubDate>Sat, 02 Nov 2024 14:50:43 GMT</pubDate>
 </item>
 <item>
   <title></title>
@@ -242,7 +242,7 @@
 
  ]]></description>
   <guid>https://v-sekai.github.io/manuals/decisions/20241028-use-data-tables-for-godot-constraints.html</guid>
-  <pubDate>Sat, 02 Nov 2024 08:18:48 GMT</pubDate>
+  <pubDate>Sat, 02 Nov 2024 14:50:43 GMT</pubDate>
 </item>
 <item>
   <title></title>
@@ -345,7 +345,7 @@
 
  ]]></description>
   <guid>https://v-sekai.github.io/manuals/decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html</guid>
-  <pubDate>Sat, 02 Nov 2024 08:18:48 GMT</pubDate>
+  <pubDate>Sat, 02 Nov 2024 14:50:43 GMT</pubDate>
 </item>
 <item>
   <title></title>
@@ -439,7 +439,7 @@
 
  ]]></description>
   <guid>https://v-sekai.github.io/manuals/decisions/20241016-instantiating-v-sekai-content.html</guid>
-  <pubDate>Sat, 02 Nov 2024 08:18:48 GMT</pubDate>
+  <pubDate>Sat, 02 Nov 2024 14:50:43 GMT</pubDate>
 </item>
 <item>
   <title></title>
@@ -590,7 +590,7 @@
 
  ]]></description>
   <guid>https://v-sekai.github.io/manuals/decisions/20241014-xr-interface-for-rigging.html</guid>
-  <pubDate>Sat, 02 Nov 2024 08:18:48 GMT</pubDate>
+  <pubDate>Sat, 02 Nov 2024 14:50:43 GMT</pubDate>
 </item>
 <item>
   <title></title>
@@ -691,7 +691,7 @@
 
  ]]></description>
   <guid>https://v-sekai.github.io/manuals/decisions/20241014-basic-realtime-interaction.html</guid>
-  <pubDate>Sat, 02 Nov 2024 08:18:48 GMT</pubDate>
+  <pubDate>Sat, 02 Nov 2024 14:50:43 GMT</pubDate>
 </item>
 <item>
   <title></title>
@@ -794,7 +794,7 @@ func notify(message):
 
  ]]></description>
   <guid>https://v-sekai.github.io/manuals/decisions/20241014-app-updater.html</guid>
-  <pubDate>Sat, 02 Nov 2024 08:18:48 GMT</pubDate>
+  <pubDate>Sat, 02 Nov 2024 14:50:43 GMT</pubDate>
 </item>
 <item>
   <title></title>
@@ -924,7 +924,7 @@ func notify(message):
 
  ]]></description>
   <guid>https://v-sekai.github.io/manuals/decisions/20241011-recovering-makehuman-parameters.html</guid>
-  <pubDate>Sat, 02 Nov 2024 08:18:48 GMT</pubDate>
+  <pubDate>Sat, 02 Nov 2024 14:50:43 GMT</pubDate>
 </item>
 <item>
   <title></title>
@@ -1010,7 +1010,7 @@ func notify(message):
 
  ]]></description>
   <guid>https://v-sekai.github.io/manuals/decisions/20241006-restore-onedrive-shortcut-overrides.html</guid>
-  <pubDate>Sat, 02 Nov 2024 08:18:48 GMT</pubDate>
+  <pubDate>Sat, 02 Nov 2024 14:50:43 GMT</pubDate>
 </item>
 <item>
   <title></title>
@@ -1093,7 +1093,7 @@ func notify(message):
 
  ]]></description>
   <guid>https://v-sekai.github.io/manuals/decisions/20241001-small-game-tools.html</guid>
-  <pubDate>Sat, 02 Nov 2024 08:18:48 GMT</pubDate>
+  <pubDate>Sat, 02 Nov 2024 14:50:43 GMT</pubDate>
 </item>
 <item>
   <title></title>
@@ -1196,7 +1196,7 @@ func notify(message):
 
  ]]></description>
   <guid>https://v-sekai.github.io/manuals/decisions/20240914-godot-engine-xr-elite-conference-setup.html</guid>
-  <pubDate>Sat, 02 Nov 2024 08:18:48 GMT</pubDate>
+  <pubDate>Sat, 02 Nov 2024 14:50:43 GMT</pubDate>
 </item>
 <item>
   <title></title>
@@ -1321,7 +1321,7 @@ func notify(message):
 
  ]]></description>
   <guid>https://v-sekai.github.io/manuals/decisions/20240905-revised-tracker-configuration-and-constraints.html</guid>
-  <pubDate>Sat, 02 Nov 2024 08:18:48 GMT</pubDate>
+  <pubDate>Sat, 02 Nov 2024 14:50:43 GMT</pubDate>
 </item>
 <item>
   <title></title>
@@ -1463,7 +1463,7 @@ font-style: inherit;"># Follow the specific instructions from the Signoz guide</
 
  ]]></description>
   <guid>https://v-sekai.github.io/manuals/decisions/20240830-use-dokku-to-host-vsk-backend.html</guid>
-  <pubDate>Sat, 02 Nov 2024 08:18:48 GMT</pubDate>
+  <pubDate>Sat, 02 Nov 2024 14:50:43 GMT</pubDate>
 </item>
 <item>
   <title></title>
@@ -1561,7 +1561,7 @@ font-style: inherit;"># Follow the specific instructions from the Signoz guide</
 
  ]]></description>
   <guid>https://v-sekai.github.io/manuals/decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html</guid>
-  <pubDate>Sat, 02 Nov 2024 08:18:48 GMT</pubDate>
+  <pubDate>Sat, 02 Nov 2024 14:50:43 GMT</pubDate>
 </item>
 <item>
   <title></title>
@@ -2046,7 +2046,7 @@ font-style: inherit;">-i</span> dummy</span></code></pre></div>
 
  ]]></description>
   <guid>https://v-sekai.github.io/manuals/decisions/20240824-ffmpeg-wav-mic-speaker-play.html</guid>
-  <pubDate>Sat, 02 Nov 2024 08:18:48 GMT</pubDate>
+  <pubDate>Sat, 02 Nov 2024 14:50:43 GMT</pubDate>
 </item>
 <item>
   <title></title>
@@ -2135,7 +2135,7 @@ font-style: inherit;">-i</span> dummy</span></code></pre></div>
 
  ]]></description>
   <guid>https://v-sekai.github.io/manuals/decisions/20240810-steamvr-dongles-separate.html</guid>
-  <pubDate>Sat, 02 Nov 2024 08:18:48 GMT</pubDate>
+  <pubDate>Sat, 02 Nov 2024 14:50:43 GMT</pubDate>
 </item>
 <item>
   <title></title>
@@ -2234,7 +2234,7 @@ font-style: inherit;">-i</span> dummy</span></code></pre></div>
 
  ]]></description>
   <guid>https://v-sekai.github.io/manuals/decisions/20240717-core-vsekai-scripting.html</guid>
-  <pubDate>Sat, 02 Nov 2024 08:18:48 GMT</pubDate>
+  <pubDate>Sat, 02 Nov 2024 14:50:43 GMT</pubDate>
 </item>
 <item>
   <title></title>
@@ -2866,7 +2866,7 @@ font-style: inherit;">}</span></span></code></pre></div>
 
  ]]></description>
   <guid>https://v-sekai.github.io/manuals/decisions/20240715-vrchat-networking-mental-model.html</guid>
-  <pubDate>Sat, 02 Nov 2024 08:18:48 GMT</pubDate>
+  <pubDate>Sat, 02 Nov 2024 14:50:43 GMT</pubDate>
 </item>
 <item>
   <title></title>
@@ -2953,7 +2953,7 @@ font-style: inherit;">}</span></span></code></pre></div>
 
  ]]></description>
   <guid>https://v-sekai.github.io/manuals/decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html</guid>
-  <pubDate>Sat, 02 Nov 2024 08:18:48 GMT</pubDate>
+  <pubDate>Sat, 02 Nov 2024 14:50:43 GMT</pubDate>
 </item>
 </channel>
 </rss>
diff --git a/docs/decisions/20200602-manage-backend-with-k3s.html b/docs/decisions/20200602-manage-backend-with-k3s.html
index ea84937010..506bdff2fe 100644
--- a/docs/decisions/20200602-manage-backend-with-k3s.html
+++ b/docs/decisions/20200602-manage-backend-with-k3s.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20200608-vsekai-charter.html b/docs/decisions/20200608-vsekai-charter.html
index 2fdad84d08..cce326cf84 100644
--- a/docs/decisions/20200608-vsekai-charter.html
+++ b/docs/decisions/20200608-vsekai-charter.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20200729-entity-networking.html b/docs/decisions/20200729-entity-networking.html
index fce2a629b3..4604fe8746 100644
--- a/docs/decisions/20200729-entity-networking.html
+++ b/docs/decisions/20200729-entity-networking.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20210212-add-build-notifications.html b/docs/decisions/20210212-add-build-notifications.html
index 9846f486d3..e2ea079138 100644
--- a/docs/decisions/20210212-add-build-notifications.html
+++ b/docs/decisions/20210212-add-build-notifications.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20210212-use-log4brains-to-manage-the-adrs.html b/docs/decisions/20210212-use-log4brains-to-manage-the-adrs.html
index 1b63ba80b5..0e348aab36 100644
--- a/docs/decisions/20210212-use-log4brains-to-manage-the-adrs.html
+++ b/docs/decisions/20210212-use-log4brains-to-manage-the-adrs.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20210212-use-markdown-architectural-decision-records.html b/docs/decisions/20210212-use-markdown-architectural-decision-records.html
index 16442d481c..baea8babce 100644
--- a/docs/decisions/20210212-use-markdown-architectural-decision-records.html
+++ b/docs/decisions/20210212-use-markdown-architectural-decision-records.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20210523-basis-universal-import.html b/docs/decisions/20210523-basis-universal-import.html
index 59527b60f2..515d7e548e 100644
--- a/docs/decisions/20210523-basis-universal-import.html
+++ b/docs/decisions/20210523-basis-universal-import.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html b/docs/decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html
index 89e90122a8..e7c7f27462 100644
--- a/docs/decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html
+++ b/docs/decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20210523-distribute-trusted-clients-with-notary.html b/docs/decisions/20210523-distribute-trusted-clients-with-notary.html
index ea9d2301d3..9c0cfc610f 100644
--- a/docs/decisions/20210523-distribute-trusted-clients-with-notary.html
+++ b/docs/decisions/20210523-distribute-trusted-clients-with-notary.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20210523-retarget-motion-for-vrm-type-models.html b/docs/decisions/20210523-retarget-motion-for-vrm-type-models.html
index 8dfce8199f..0dd28719bd 100644
--- a/docs/decisions/20210523-retarget-motion-for-vrm-type-models.html
+++ b/docs/decisions/20210523-retarget-motion-for-vrm-type-models.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20210523-simplfy-meshes-and-lods-better-with-quads.html b/docs/decisions/20210523-simplfy-meshes-and-lods-better-with-quads.html
index 13f3829104..f48e0e805d 100644
--- a/docs/decisions/20210523-simplfy-meshes-and-lods-better-with-quads.html
+++ b/docs/decisions/20210523-simplfy-meshes-and-lods-better-with-quads.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20210528-trial-install-of-gravity-for-kubernetes.html b/docs/decisions/20210528-trial-install-of-gravity-for-kubernetes.html
index b788afbaf0..a6442cdfe2 100644
--- a/docs/decisions/20210528-trial-install-of-gravity-for-kubernetes.html
+++ b/docs/decisions/20210528-trial-install-of-gravity-for-kubernetes.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20210529-performance-profiling.html b/docs/decisions/20210529-performance-profiling.html
index 891cd5ac65..b471bfd425 100644
--- a/docs/decisions/20210529-performance-profiling.html
+++ b/docs/decisions/20210529-performance-profiling.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20210601-store-presentation-and-book-content-via-lottie-2.html b/docs/decisions/20210601-store-presentation-and-book-content-via-lottie-2.html
index 5cda814f3c..e5a746e4f2 100644
--- a/docs/decisions/20210601-store-presentation-and-book-content-via-lottie-2.html
+++ b/docs/decisions/20210601-store-presentation-and-book-content-via-lottie-2.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20210612-flow-avatar-asset-pipeline.html b/docs/decisions/20210612-flow-avatar-asset-pipeline.html
index 8fe6a5ac6e..b56484c9ee 100644
--- a/docs/decisions/20210612-flow-avatar-asset-pipeline.html
+++ b/docs/decisions/20210612-flow-avatar-asset-pipeline.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20210622-shadermotion-to-godot-engine.html b/docs/decisions/20210622-shadermotion-to-godot-engine.html
index 470e346476..190c56a09b 100644
--- a/docs/decisions/20210622-shadermotion-to-godot-engine.html
+++ b/docs/decisions/20210622-shadermotion-to-godot-engine.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20210707-transfer-animations-by-baking-reset.html b/docs/decisions/20210707-transfer-animations-by-baking-reset.html
index 55828a135f..3c3ca9bb4a 100644
--- a/docs/decisions/20210707-transfer-animations-by-baking-reset.html
+++ b/docs/decisions/20210707-transfer-animations-by-baking-reset.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20210710-verify-pr-workflow.html b/docs/decisions/20210710-verify-pr-workflow.html
index 9dc4b2634d..d0f274f483 100644
--- a/docs/decisions/20210710-verify-pr-workflow.html
+++ b/docs/decisions/20210710-verify-pr-workflow.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20210715-Material-Addon-Blender.html b/docs/decisions/20210715-Material-Addon-Blender.html
index 8861747de7..303a8312c3 100644
--- a/docs/decisions/20210715-Material-Addon-Blender.html
+++ b/docs/decisions/20210715-Material-Addon-Blender.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20210715-portable-world-content.html b/docs/decisions/20210715-portable-world-content.html
index f2d94d6a99..a1b2eae3b9 100644
--- a/docs/decisions/20210715-portable-world-content.html
+++ b/docs/decisions/20210715-portable-world-content.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20210724-Spreadsheet-animation-preview.html b/docs/decisions/20210724-Spreadsheet-animation-preview.html
index 14e20561d5..c52e5c712a 100644
--- a/docs/decisions/20210724-Spreadsheet-animation-preview.html
+++ b/docs/decisions/20210724-Spreadsheet-animation-preview.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20210811-disconnected-ipfs.html b/docs/decisions/20210811-disconnected-ipfs.html
index 2a32fdc7b3..802f0d6b89 100644
--- a/docs/decisions/20210811-disconnected-ipfs.html
+++ b/docs/decisions/20210811-disconnected-ipfs.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20210811-game-workflow-membrane.html b/docs/decisions/20210811-game-workflow-membrane.html
index 381150dff6..01f7f1ac7d 100644
--- a/docs/decisions/20210811-game-workflow-membrane.html
+++ b/docs/decisions/20210811-game-workflow-membrane.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20210811-glb-in-video.html b/docs/decisions/20210811-glb-in-video.html
index c89abb26db..e7ec3da5d8 100644
--- a/docs/decisions/20210811-glb-in-video.html
+++ b/docs/decisions/20210811-glb-in-video.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20210811-godot-transparency.html b/docs/decisions/20210811-godot-transparency.html
index 388c13e067..c3bc12faf4 100644
--- a/docs/decisions/20210811-godot-transparency.html
+++ b/docs/decisions/20210811-godot-transparency.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20210811-min-spec-v-sekai.html b/docs/decisions/20210811-min-spec-v-sekai.html
index 8c9c0e6c70..573e65171c 100644
--- a/docs/decisions/20210811-min-spec-v-sekai.html
+++ b/docs/decisions/20210811-min-spec-v-sekai.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20210811-minecraft-voxel.html b/docs/decisions/20210811-minecraft-voxel.html
index 6e0506acb1..342676cd7c 100644
--- a/docs/decisions/20210811-minecraft-voxel.html
+++ b/docs/decisions/20210811-minecraft-voxel.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20210811-neural-blend-shape-rigging.html b/docs/decisions/20210811-neural-blend-shape-rigging.html
index 376aa0d0b8..df2afcb1da 100644
--- a/docs/decisions/20210811-neural-blend-shape-rigging.html
+++ b/docs/decisions/20210811-neural-blend-shape-rigging.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20210811-omi-glb.html b/docs/decisions/20210811-omi-glb.html
index a3033b6278..ec952724ed 100644
--- a/docs/decisions/20210811-omi-glb.html
+++ b/docs/decisions/20210811-omi-glb.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20210811-soiree-party.html b/docs/decisions/20210811-soiree-party.html
index 10cc0d9f37..2d3c40fbe8 100644
--- a/docs/decisions/20210811-soiree-party.html
+++ b/docs/decisions/20210811-soiree-party.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20210811-spoke-to-v-sekai.html b/docs/decisions/20210811-spoke-to-v-sekai.html
index 434bdf4bbc..a1889689b1 100644
--- a/docs/decisions/20210811-spoke-to-v-sekai.html
+++ b/docs/decisions/20210811-spoke-to-v-sekai.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211005-bridge-music-to-xr.html b/docs/decisions/20211005-bridge-music-to-xr.html
index 5202b1f76b..3105664d8d 100644
--- a/docs/decisions/20211005-bridge-music-to-xr.html
+++ b/docs/decisions/20211005-bridge-music-to-xr.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211005-create-add-spring-bones-to-vrm-models.html b/docs/decisions/20211005-create-add-spring-bones-to-vrm-models.html
index 3ecebf4930..a6672fcf9d 100644
--- a/docs/decisions/20211005-create-add-spring-bones-to-vrm-models.html
+++ b/docs/decisions/20211005-create-add-spring-bones-to-vrm-models.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211005-create-sop-for-vrm-creation.html b/docs/decisions/20211005-create-sop-for-vrm-creation.html
index e2c0d429a9..cae7c8471f 100644
--- a/docs/decisions/20211005-create-sop-for-vrm-creation.html
+++ b/docs/decisions/20211005-create-sop-for-vrm-creation.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211005-improve-meshing-results-by-subdivision-in-godot-engine.html b/docs/decisions/20211005-improve-meshing-results-by-subdivision-in-godot-engine.html
index 93913006e5..7b89e03fb2 100644
--- a/docs/decisions/20211005-improve-meshing-results-by-subdivision-in-godot-engine.html
+++ b/docs/decisions/20211005-improve-meshing-results-by-subdivision-in-godot-engine.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211005-solve-mocap-by-connecting-mediapipe-to-blender.html b/docs/decisions/20211005-solve-mocap-by-connecting-mediapipe-to-blender.html
index 9ad3f5b9df..d12a578a2b 100644
--- a/docs/decisions/20211005-solve-mocap-by-connecting-mediapipe-to-blender.html
+++ b/docs/decisions/20211005-solve-mocap-by-connecting-mediapipe-to-blender.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211005-test-google-mediapipe.html b/docs/decisions/20211005-test-google-mediapipe.html
index 0087753441..e71482f33e 100644
--- a/docs/decisions/20211005-test-google-mediapipe.html
+++ b/docs/decisions/20211005-test-google-mediapipe.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211005-use-kvm-to-test-our-amd-apu-test-computer-via-barrier.html b/docs/decisions/20211005-use-kvm-to-test-our-amd-apu-test-computer-via-barrier.html
index 83f5f37a93..7ee02e08d6 100644
--- a/docs/decisions/20211005-use-kvm-to-test-our-amd-apu-test-computer-via-barrier.html
+++ b/docs/decisions/20211005-use-kvm-to-test-our-amd-apu-test-computer-via-barrier.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211005-use-materialx-for-asset-interchange.html b/docs/decisions/20211005-use-materialx-for-asset-interchange.html
index 80fccc9b86..44afe22461 100644
--- a/docs/decisions/20211005-use-materialx-for-asset-interchange.html
+++ b/docs/decisions/20211005-use-materialx-for-asset-interchange.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211005-want-to-summon-friends-and-acquaintances-via-presence.html b/docs/decisions/20211005-want-to-summon-friends-and-acquaintances-via-presence.html
index 65b717a8d8..374f26b488 100644
--- a/docs/decisions/20211005-want-to-summon-friends-and-acquaintances-via-presence.html
+++ b/docs/decisions/20211005-want-to-summon-friends-and-acquaintances-via-presence.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211005-want-to-use-the-same-cluster-for-the-same-web-and-native.html b/docs/decisions/20211005-want-to-use-the-same-cluster-for-the-same-web-and-native.html
index b7b636ea1d..01b7976340 100644
--- a/docs/decisions/20211005-want-to-use-the-same-cluster-for-the-same-web-and-native.html
+++ b/docs/decisions/20211005-want-to-use-the-same-cluster-for-the-same-web-and-native.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211005-we-want-to-proxy-udp-datagrams-at-production-quality-of-service.html b/docs/decisions/20211005-we-want-to-proxy-udp-datagrams-at-production-quality-of-service.html
index 5b895fa1f2..ccfb88fc8c 100644
--- a/docs/decisions/20211005-we-want-to-proxy-udp-datagrams-at-production-quality-of-service.html
+++ b/docs/decisions/20211005-we-want-to-proxy-udp-datagrams-at-production-quality-of-service.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211031-1000-player-servers.html b/docs/decisions/20211031-1000-player-servers.html
index 1427650875..89aea01100 100644
--- a/docs/decisions/20211031-1000-player-servers.html
+++ b/docs/decisions/20211031-1000-player-servers.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211031-arc-radial-menu.html b/docs/decisions/20211031-arc-radial-menu.html
index 003908b016..592b9e2634 100644
--- a/docs/decisions/20211031-arc-radial-menu.html
+++ b/docs/decisions/20211031-arc-radial-menu.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211031-bake-a-materialx-into-a-custom-godot-standardmaterial3d.html b/docs/decisions/20211031-bake-a-materialx-into-a-custom-godot-standardmaterial3d.html
index 14deef5120..6a3033b68b 100644
--- a/docs/decisions/20211031-bake-a-materialx-into-a-custom-godot-standardmaterial3d.html
+++ b/docs/decisions/20211031-bake-a-materialx-into-a-custom-godot-standardmaterial3d.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211031-bake-blend-shape-to-skeleton-animation.html b/docs/decisions/20211031-bake-blend-shape-to-skeleton-animation.html
index fbb9decaac..e49af31d7f 100644
--- a/docs/decisions/20211031-bake-blend-shape-to-skeleton-animation.html
+++ b/docs/decisions/20211031-bake-blend-shape-to-skeleton-animation.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211031-benchmark-animation-playback.html b/docs/decisions/20211031-benchmark-animation-playback.html
index 5b0b2835d8..c046f36439 100644
--- a/docs/decisions/20211031-benchmark-animation-playback.html
+++ b/docs/decisions/20211031-benchmark-animation-playback.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211031-character-workshop.html b/docs/decisions/20211031-character-workshop.html
index 12bbff7a74..15112bfac7 100644
--- a/docs/decisions/20211031-character-workshop.html
+++ b/docs/decisions/20211031-character-workshop.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211031-cicd-export-v-sekai.html b/docs/decisions/20211031-cicd-export-v-sekai.html
index cf66877d28..0652a7387a 100644
--- a/docs/decisions/20211031-cicd-export-v-sekai.html
+++ b/docs/decisions/20211031-cicd-export-v-sekai.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211031-client-and-mast.html b/docs/decisions/20211031-client-and-mast.html
index 7c75c3d63c..96406d93f8 100644
--- a/docs/decisions/20211031-client-and-mast.html
+++ b/docs/decisions/20211031-client-and-mast.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211031-construct-the-virtual-world.html b/docs/decisions/20211031-construct-the-virtual-world.html
index 20a39220fb..48e0576a6a 100644
--- a/docs/decisions/20211031-construct-the-virtual-world.html
+++ b/docs/decisions/20211031-construct-the-virtual-world.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211031-create-a-demo-viewer-gallery.html b/docs/decisions/20211031-create-a-demo-viewer-gallery.html
index 48c301cc57..ab70d5f74d 100644
--- a/docs/decisions/20211031-create-a-demo-viewer-gallery.html
+++ b/docs/decisions/20211031-create-a-demo-viewer-gallery.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211031-export-import-testing-via-robot-framework-and-swiftshader.html b/docs/decisions/20211031-export-import-testing-via-robot-framework-and-swiftshader.html
index 18aa58e258..5fa2c9d8e1 100644
--- a/docs/decisions/20211031-export-import-testing-via-robot-framework-and-swiftshader.html
+++ b/docs/decisions/20211031-export-import-testing-via-robot-framework-and-swiftshader.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211031-extract-proposals-into-proposals.html b/docs/decisions/20211031-extract-proposals-into-proposals.html
index 87ea181af2..652471c1f1 100644
--- a/docs/decisions/20211031-extract-proposals-into-proposals.html
+++ b/docs/decisions/20211031-extract-proposals-into-proposals.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211031-face-motion-tracking-requires-standard-shapes.html b/docs/decisions/20211031-face-motion-tracking-requires-standard-shapes.html
index 650d709450..8cec73aedb 100644
--- a/docs/decisions/20211031-face-motion-tracking-requires-standard-shapes.html
+++ b/docs/decisions/20211031-face-motion-tracking-requires-standard-shapes.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211031-gltf-importer-should-bind-animation-players-to-the-closest-root-node.html b/docs/decisions/20211031-gltf-importer-should-bind-animation-players-to-the-closest-root-node.html
index 737da8ffd1..afcf7f6a92 100644
--- a/docs/decisions/20211031-gltf-importer-should-bind-animation-players-to-the-closest-root-node.html
+++ b/docs/decisions/20211031-gltf-importer-should-bind-animation-players-to-the-closest-root-node.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211031-godot-database-viewer-for-proposals.html b/docs/decisions/20211031-godot-database-viewer-for-proposals.html
index b7c72c50b5..674719c243 100644
--- a/docs/decisions/20211031-godot-database-viewer-for-proposals.html
+++ b/docs/decisions/20211031-godot-database-viewer-for-proposals.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211031-have-better-user-developer-experience.html b/docs/decisions/20211031-have-better-user-developer-experience.html
index 6c049f0763..edddf937d4 100644
--- a/docs/decisions/20211031-have-better-user-developer-experience.html
+++ b/docs/decisions/20211031-have-better-user-developer-experience.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211031-have-wires-in-3d.html b/docs/decisions/20211031-have-wires-in-3d.html
index 2fb22d17cc..949546e989 100644
--- a/docs/decisions/20211031-have-wires-in-3d.html
+++ b/docs/decisions/20211031-have-wires-in-3d.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211031-how-to-make-a-v-sekaigodot-update.html b/docs/decisions/20211031-how-to-make-a-v-sekaigodot-update.html
index f5edbdf812..9fba81ec03 100644
--- a/docs/decisions/20211031-how-to-make-a-v-sekaigodot-update.html
+++ b/docs/decisions/20211031-how-to-make-a-v-sekaigodot-update.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211031-keep-a-changelog.html b/docs/decisions/20211031-keep-a-changelog.html
index caec08ddad..7829de0a38 100644
--- a/docs/decisions/20211031-keep-a-changelog.html
+++ b/docs/decisions/20211031-keep-a-changelog.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211031-make-a-place-to-record.html b/docs/decisions/20211031-make-a-place-to-record.html
index 4aa6299daf..8bd360f836 100644
--- a/docs/decisions/20211031-make-a-place-to-record.html
+++ b/docs/decisions/20211031-make-a-place-to-record.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211031-meeting-area.html b/docs/decisions/20211031-meeting-area.html
index 0eee90318f..9d1a7409a0 100644
--- a/docs/decisions/20211031-meeting-area.html
+++ b/docs/decisions/20211031-meeting-area.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211031-membrane-framework-streaming-mixer.html b/docs/decisions/20211031-membrane-framework-streaming-mixer.html
index a928c600fa..812704bc29 100644
--- a/docs/decisions/20211031-membrane-framework-streaming-mixer.html
+++ b/docs/decisions/20211031-membrane-framework-streaming-mixer.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211031-openvr-for-godot-engine.html b/docs/decisions/20211031-openvr-for-godot-engine.html
index 552b426309..2fd2e48ffc 100644
--- a/docs/decisions/20211031-openvr-for-godot-engine.html
+++ b/docs/decisions/20211031-openvr-for-godot-engine.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211031-phase-out-groups-terminology-for-vskdefault.html b/docs/decisions/20211031-phase-out-groups-terminology-for-vskdefault.html
index 2f1540eab7..782abe459f 100644
--- a/docs/decisions/20211031-phase-out-groups-terminology-for-vskdefault.html
+++ b/docs/decisions/20211031-phase-out-groups-terminology-for-vskdefault.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211031-plausable-npc-behaviour.html b/docs/decisions/20211031-plausable-npc-behaviour.html
index 69520fa69e..a3d22dfb6d 100644
--- a/docs/decisions/20211031-plausable-npc-behaviour.html
+++ b/docs/decisions/20211031-plausable-npc-behaviour.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211031-play-preprocessed-animations-on-any-vrm-model.html b/docs/decisions/20211031-play-preprocessed-animations-on-any-vrm-model.html
index 154be09993..8f1bd88f60 100644
--- a/docs/decisions/20211031-play-preprocessed-animations-on-any-vrm-model.html
+++ b/docs/decisions/20211031-play-preprocessed-animations-on-any-vrm-model.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html b/docs/decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html
index 235be68b43..7961ddf7a6 100644
--- a/docs/decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html
+++ b/docs/decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211031-script-as-a-binary.html b/docs/decisions/20211031-script-as-a-binary.html
index 1726904a14..28a53cdc0f 100644
--- a/docs/decisions/20211031-script-as-a-binary.html
+++ b/docs/decisions/20211031-script-as-a-binary.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211031-standard-backup-procedures.html b/docs/decisions/20211031-standard-backup-procedures.html
index b84a8210f9..d7e9c4aeeb 100644
--- a/docs/decisions/20211031-standard-backup-procedures.html
+++ b/docs/decisions/20211031-standard-backup-procedures.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211031-stream-shader-motion.html b/docs/decisions/20211031-stream-shader-motion.html
index e900ebf2f2..925666c3bf 100644
--- a/docs/decisions/20211031-stream-shader-motion.html
+++ b/docs/decisions/20211031-stream-shader-motion.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211031-streaming-godot-to-opensoundcontrol.html b/docs/decisions/20211031-streaming-godot-to-opensoundcontrol.html
index ce8346848f..e8d9d35abd 100644
--- a/docs/decisions/20211031-streaming-godot-to-opensoundcontrol.html
+++ b/docs/decisions/20211031-streaming-godot-to-opensoundcontrol.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211031-thorvg.html b/docs/decisions/20211031-thorvg.html
index c52ce42e64..9a46176196 100644
--- a/docs/decisions/20211031-thorvg.html
+++ b/docs/decisions/20211031-thorvg.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211031-tire-model-car-sim.html b/docs/decisions/20211031-tire-model-car-sim.html
index f2e56b3a6d..7ed760be28 100644
--- a/docs/decisions/20211031-tire-model-car-sim.html
+++ b/docs/decisions/20211031-tire-model-car-sim.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211031-update-uro-for-godot-4.html b/docs/decisions/20211031-update-uro-for-godot-4.html
index 767461da5f..0c069c4a09 100644
--- a/docs/decisions/20211031-update-uro-for-godot-4.html
+++ b/docs/decisions/20211031-update-uro-for-godot-4.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211031-use-bpr-to-rank-skeleton-bone-names.html b/docs/decisions/20211031-use-bpr-to-rank-skeleton-bone-names.html
index 3926770767..05cac4b7f7 100644
--- a/docs/decisions/20211031-use-bpr-to-rank-skeleton-bone-names.html
+++ b/docs/decisions/20211031-use-bpr-to-rank-skeleton-bone-names.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211031-use-our-custom-fullbody-ik.html b/docs/decisions/20211031-use-our-custom-fullbody-ik.html
index 6b87d95ac4..70209ac1ea 100644
--- a/docs/decisions/20211031-use-our-custom-fullbody-ik.html
+++ b/docs/decisions/20211031-use-our-custom-fullbody-ik.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211031-verification-tools.html b/docs/decisions/20211031-verification-tools.html
index f5df04fb47..aced29340e 100644
--- a/docs/decisions/20211031-verification-tools.html
+++ b/docs/decisions/20211031-verification-tools.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211031-vmd-on-vrm-animationtree-node.html b/docs/decisions/20211031-vmd-on-vrm-animationtree-node.html
index 9598c897d1..682b8455a7 100644
--- a/docs/decisions/20211031-vmd-on-vrm-animationtree-node.html
+++ b/docs/decisions/20211031-vmd-on-vrm-animationtree-node.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211031-voip.html b/docs/decisions/20211031-voip.html
index a921994bc1..8ac022f919 100644
--- a/docs/decisions/20211031-voip.html
+++ b/docs/decisions/20211031-voip.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211103-use-platform-called-vfx-reference-platform.html b/docs/decisions/20211103-use-platform-called-vfx-reference-platform.html
index 3a43fc1342..e39bc1086e 100644
--- a/docs/decisions/20211103-use-platform-called-vfx-reference-platform.html
+++ b/docs/decisions/20211103-use-platform-called-vfx-reference-platform.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211104-research-mesh-tooling-with-kaolin.html b/docs/decisions/20211104-research-mesh-tooling-with-kaolin.html
index 5540331459..7ef2107d65 100644
--- a/docs/decisions/20211104-research-mesh-tooling-with-kaolin.html
+++ b/docs/decisions/20211104-research-mesh-tooling-with-kaolin.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211104-research-mesh-tooling-with-nglod.html b/docs/decisions/20211104-research-mesh-tooling-with-nglod.html
index eefdc6b2fa..9ab06e40e7 100644
--- a/docs/decisions/20211104-research-mesh-tooling-with-nglod.html
+++ b/docs/decisions/20211104-research-mesh-tooling-with-nglod.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211105-have-an-webxr-version-of-v-sekai.html b/docs/decisions/20211105-have-an-webxr-version-of-v-sekai.html
index 6dd86e3a53..b54ce9ce36 100644
--- a/docs/decisions/20211105-have-an-webxr-version-of-v-sekai.html
+++ b/docs/decisions/20211105-have-an-webxr-version-of-v-sekai.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html b/docs/decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html
index 50114ade5d..e205c302ad 100644
--- a/docs/decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html
+++ b/docs/decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html b/docs/decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html
index 983c1b6327..8c0ceb2578 100644
--- a/docs/decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html
+++ b/docs/decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html b/docs/decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html
index f44d86458d..0e27881c3c 100644
--- a/docs/decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html
+++ b/docs/decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html b/docs/decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html
index f325d9127e..ac57a61d7c 100644
--- a/docs/decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html
+++ b/docs/decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211108-integrate-with-blender.html b/docs/decisions/20211108-integrate-with-blender.html
index 4ea77eb1c7..72202351b8 100644
--- a/docs/decisions/20211108-integrate-with-blender.html
+++ b/docs/decisions/20211108-integrate-with-blender.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html b/docs/decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html
index 970fc3d3d4..46329755d9 100644
--- a/docs/decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html
+++ b/docs/decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html b/docs/decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html
index ead4641895..60a2b5909e 100644
--- a/docs/decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html
+++ b/docs/decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html b/docs/decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html
index f102a879e1..66f629c3a7 100644
--- a/docs/decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html
+++ b/docs/decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html b/docs/decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html
index faee18a2aa..1416edccf3 100644
--- a/docs/decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html
+++ b/docs/decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html b/docs/decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html
index 52b3f78d8b..690f68c4ed 100644
--- a/docs/decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html
+++ b/docs/decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html b/docs/decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html
index 10fa28f60e..5518243b6d 100644
--- a/docs/decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html
+++ b/docs/decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html b/docs/decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html
index c97dfed142..a177607cce 100644
--- a/docs/decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html
+++ b/docs/decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html b/docs/decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html
index c0c611b8fc..3a2afdf3bc 100644
--- a/docs/decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html
+++ b/docs/decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html b/docs/decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html
index 30ea46a485..329c23d368 100644
--- a/docs/decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html
+++ b/docs/decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html b/docs/decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html
index 123e70ecbd..639d95789e 100644
--- a/docs/decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html
+++ b/docs/decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html b/docs/decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html
index f401e4bf71..59f583a6d2 100644
--- a/docs/decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html
+++ b/docs/decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html b/docs/decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html
index acb19fb568..c7ced28a11 100644
--- a/docs/decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html
+++ b/docs/decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html b/docs/decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html
index 9407e17435..58ee87832f 100644
--- a/docs/decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html
+++ b/docs/decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html b/docs/decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html
index f71f646ecf..fc04564111 100644
--- a/docs/decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html
+++ b/docs/decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211220-network-the-ubisoft-mixer-server.html b/docs/decisions/20211220-network-the-ubisoft-mixer-server.html
index a9508fe759..497062b701 100644
--- a/docs/decisions/20211220-network-the-ubisoft-mixer-server.html
+++ b/docs/decisions/20211220-network-the-ubisoft-mixer-server.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211229-run-meetings-using-lean-coffee.html b/docs/decisions/20211229-run-meetings-using-lean-coffee.html
index 51e0817d3b..c20b03e87b 100644
--- a/docs/decisions/20211229-run-meetings-using-lean-coffee.html
+++ b/docs/decisions/20211229-run-meetings-using-lean-coffee.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html b/docs/decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html
index c8810f80de..0a08e6968f 100644
--- a/docs/decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html
+++ b/docs/decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20220108-bake-blend-shapes-to-skeletons-for-performance.html b/docs/decisions/20220108-bake-blend-shapes-to-skeletons-for-performance.html
index 401e6aabfd..ff65bc67b8 100644
--- a/docs/decisions/20220108-bake-blend-shapes-to-skeletons-for-performance.html
+++ b/docs/decisions/20220108-bake-blend-shapes-to-skeletons-for-performance.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20220113-change-transform-by-crdt.html b/docs/decisions/20220113-change-transform-by-crdt.html
index 8981ef2c9b..e68a6aa692 100644
--- a/docs/decisions/20220113-change-transform-by-crdt.html
+++ b/docs/decisions/20220113-change-transform-by-crdt.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20220118-convert-gltf-to-a-scene.html b/docs/decisions/20220118-convert-gltf-to-a-scene.html
index f36833c531..f957567a91 100644
--- a/docs/decisions/20220118-convert-gltf-to-a-scene.html
+++ b/docs/decisions/20220118-convert-gltf-to-a-scene.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html b/docs/decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html
index 07eb13e8ef..8ab31fa6d5 100644
--- a/docs/decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html
+++ b/docs/decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20220130-optimize-cicd.html b/docs/decisions/20220130-optimize-cicd.html
index 9238f9c72d..b930beff38 100644
--- a/docs/decisions/20220130-optimize-cicd.html
+++ b/docs/decisions/20220130-optimize-cicd.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20220130-to-record-decisions-write-a-proposal.html b/docs/decisions/20220130-to-record-decisions-write-a-proposal.html
index 0a347e3917..ed5bfa2b41 100644
--- a/docs/decisions/20220130-to-record-decisions-write-a-proposal.html
+++ b/docs/decisions/20220130-to-record-decisions-write-a-proposal.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20220131-elixir-desktop-uro.html b/docs/decisions/20220131-elixir-desktop-uro.html
index a0edf33d71..824c92cdd2 100644
--- a/docs/decisions/20220131-elixir-desktop-uro.html
+++ b/docs/decisions/20220131-elixir-desktop-uro.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20220131-github-actions-support.html b/docs/decisions/20220131-github-actions-support.html
index 570ce146a9..536834d59d 100644
--- a/docs/decisions/20220131-github-actions-support.html
+++ b/docs/decisions/20220131-github-actions-support.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20220131-run-own-infrastructure.html b/docs/decisions/20220131-run-own-infrastructure.html
index 109fecf750..8e41465bdc 100644
--- a/docs/decisions/20220131-run-own-infrastructure.html
+++ b/docs/decisions/20220131-run-own-infrastructure.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20220202-gltf-extensions-for-interoperability.html b/docs/decisions/20220202-gltf-extensions-for-interoperability.html
index 2114885e66..ed5a33e10c 100644
--- a/docs/decisions/20220202-gltf-extensions-for-interoperability.html
+++ b/docs/decisions/20220202-gltf-extensions-for-interoperability.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20220203-create-default-animation-set.html b/docs/decisions/20220203-create-default-animation-set.html
index da8e7e08e2..335eb45ee0 100644
--- a/docs/decisions/20220203-create-default-animation-set.html
+++ b/docs/decisions/20220203-create-default-animation-set.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html b/docs/decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html
index 9b4ff10dd5..e9016687d3 100644
--- a/docs/decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html	
+++ b/docs/decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html	
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20220206-logging-notifications-from-discord.html b/docs/decisions/20220206-logging-notifications-from-discord.html
index e9063444b9..340fc19b8a 100644
--- a/docs/decisions/20220206-logging-notifications-from-discord.html
+++ b/docs/decisions/20220206-logging-notifications-from-discord.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20220207-virtual-pets.html b/docs/decisions/20220207-virtual-pets.html
index 03bc88d50e..4c4efcc222 100644
--- a/docs/decisions/20220207-virtual-pets.html
+++ b/docs/decisions/20220207-virtual-pets.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20220215-uro-deployment-process.html b/docs/decisions/20220215-uro-deployment-process.html
index 4b2827a27f..472e2974d7 100644
--- a/docs/decisions/20220215-uro-deployment-process.html
+++ b/docs/decisions/20220215-uro-deployment-process.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20220217-omi-chan-oni-chan.html b/docs/decisions/20220217-omi-chan-oni-chan.html
index 6bce630cef..ab473c098b 100644
--- a/docs/decisions/20220217-omi-chan-oni-chan.html
+++ b/docs/decisions/20220217-omi-chan-oni-chan.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20220222-know-where-we-re-going-by-planning-vsekai.html b/docs/decisions/20220222-know-where-we-re-going-by-planning-vsekai.html
index e3425b1c50..55b35a2220 100644
--- a/docs/decisions/20220222-know-where-we-re-going-by-planning-vsekai.html
+++ b/docs/decisions/20220222-know-where-we-re-going-by-planning-vsekai.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20220222-rank-bone-names-with-transformer.html b/docs/decisions/20220222-rank-bone-names-with-transformer.html
index d2fd8cb42f..4e684db350 100644
--- a/docs/decisions/20220222-rank-bone-names-with-transformer.html
+++ b/docs/decisions/20220222-rank-bone-names-with-transformer.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20220222-rank-bone-skeletons-with-xgboost.html b/docs/decisions/20220222-rank-bone-skeletons-with-xgboost.html
index a509da438c..61379ed616 100644
--- a/docs/decisions/20220222-rank-bone-skeletons-with-xgboost.html
+++ b/docs/decisions/20220222-rank-bone-skeletons-with-xgboost.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20220222-rank-skeleton-bone-names-with-catboost.html b/docs/decisions/20220222-rank-skeleton-bone-names-with-catboost.html
index d24507da4e..d362205558 100644
--- a/docs/decisions/20220222-rank-skeleton-bone-names-with-catboost.html
+++ b/docs/decisions/20220222-rank-skeleton-bone-names-with-catboost.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20220223-store-source-VSK_map-files-via-DVC.html b/docs/decisions/20220223-store-source-VSK_map-files-via-DVC.html
index 44b77f4bec..89397054ae 100644
--- a/docs/decisions/20220223-store-source-VSK_map-files-via-DVC.html
+++ b/docs/decisions/20220223-store-source-VSK_map-files-via-DVC.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20220224-v-sekai-version-two-plan.html b/docs/decisions/20220224-v-sekai-version-two-plan.html
index 03dd8ddccd..41f4923941 100644
--- a/docs/decisions/20220224-v-sekai-version-two-plan.html
+++ b/docs/decisions/20220224-v-sekai-version-two-plan.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20220228-v-sekai-version-three-plan.html b/docs/decisions/20220228-v-sekai-version-three-plan.html
index c06c80481a..23a01ce923 100644
--- a/docs/decisions/20220228-v-sekai-version-three-plan.html
+++ b/docs/decisions/20220228-v-sekai-version-three-plan.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20220317-baserow.io-truenas.html b/docs/decisions/20220317-baserow.io-truenas.html
index 820580be45..94de5fb50b 100644
--- a/docs/decisions/20220317-baserow.io-truenas.html
+++ b/docs/decisions/20220317-baserow.io-truenas.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20220317-protect-minumum-spec-steam-deck.html b/docs/decisions/20220317-protect-minumum-spec-steam-deck.html
index a529c957bd..f8b63fe0e7 100644
--- a/docs/decisions/20220317-protect-minumum-spec-steam-deck.html
+++ b/docs/decisions/20220317-protect-minumum-spec-steam-deck.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20220317-use-spec-rough-metal.html b/docs/decisions/20220317-use-spec-rough-metal.html
index 618db87cd3..56460b6c51 100644
--- a/docs/decisions/20220317-use-spec-rough-metal.html
+++ b/docs/decisions/20220317-use-spec-rough-metal.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20220318-merge-retargeting-pr.html b/docs/decisions/20220318-merge-retargeting-pr.html
index 1daae03956..38a1df923c 100644
--- a/docs/decisions/20220318-merge-retargeting-pr.html
+++ b/docs/decisions/20220318-merge-retargeting-pr.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20220515-profile-using-perf.html b/docs/decisions/20220515-profile-using-perf.html
index f088f4fdab..b9b3a2d7f4 100644
--- a/docs/decisions/20220515-profile-using-perf.html
+++ b/docs/decisions/20220515-profile-using-perf.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20220531-elixir-uro-dev.html b/docs/decisions/20220531-elixir-uro-dev.html
index 733950670b..de984120ae 100644
--- a/docs/decisions/20220531-elixir-uro-dev.html
+++ b/docs/decisions/20220531-elixir-uro-dev.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20220531-truenas-scale.html b/docs/decisions/20220531-truenas-scale.html
index c451962542..86fad33bc5 100644
--- a/docs/decisions/20220531-truenas-scale.html
+++ b/docs/decisions/20220531-truenas-scale.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20220601-lightweight-quality-avatars.html b/docs/decisions/20220601-lightweight-quality-avatars.html
index c9cfd8ef9c..5be65728c1 100644
--- a/docs/decisions/20220601-lightweight-quality-avatars.html
+++ b/docs/decisions/20220601-lightweight-quality-avatars.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20220605-gocd-pipeline-reset.html b/docs/decisions/20220605-gocd-pipeline-reset.html
index cb0d147313..334ff298ee 100644
--- a/docs/decisions/20220605-gocd-pipeline-reset.html
+++ b/docs/decisions/20220605-gocd-pipeline-reset.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20220605-host-internal-baserow.html b/docs/decisions/20220605-host-internal-baserow.html
index b31182ce5f..1716dd8b87 100644
--- a/docs/decisions/20220605-host-internal-baserow.html
+++ b/docs/decisions/20220605-host-internal-baserow.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20220624-webcam-to-posed-characters.html b/docs/decisions/20220624-webcam-to-posed-characters.html
index 989bd0ff67..fb4acae08d 100644
--- a/docs/decisions/20220624-webcam-to-posed-characters.html
+++ b/docs/decisions/20220624-webcam-to-posed-characters.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20220820-bake alembic-anim-via-blender.html b/docs/decisions/20220820-bake alembic-anim-via-blender.html
index a9fba89ecb..d30db3e89b 100644
--- a/docs/decisions/20220820-bake alembic-anim-via-blender.html	
+++ b/docs/decisions/20220820-bake alembic-anim-via-blender.html	
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20220820-cloth-sim.html b/docs/decisions/20220820-cloth-sim.html
index 5e83e21f40..1698524da5 100644
--- a/docs/decisions/20220820-cloth-sim.html
+++ b/docs/decisions/20220820-cloth-sim.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20220820-market-booth-tutorial.html b/docs/decisions/20220820-market-booth-tutorial.html
index 3880c3be30..e77fe131fe 100644
--- a/docs/decisions/20220820-market-booth-tutorial.html
+++ b/docs/decisions/20220820-market-booth-tutorial.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20220830-godot-pdf-workflow.html b/docs/decisions/20220830-godot-pdf-workflow.html
index 07bfeebfe1..64a8fe43e7 100644
--- a/docs/decisions/20220830-godot-pdf-workflow.html
+++ b/docs/decisions/20220830-godot-pdf-workflow.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20220901-mirror-extend-asset-library-packages.html b/docs/decisions/20220901-mirror-extend-asset-library-packages.html
index 9cf5c9e8c9..2735b4a5af 100644
--- a/docs/decisions/20220901-mirror-extend-asset-library-packages.html
+++ b/docs/decisions/20220901-mirror-extend-asset-library-packages.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20220916-too-many-branches-on-v-sekai-godot.html b/docs/decisions/20220916-too-many-branches-on-v-sekai-godot.html
index 353900225f..f1df539ef5 100644
--- a/docs/decisions/20220916-too-many-branches-on-v-sekai-godot.html
+++ b/docs/decisions/20220916-too-many-branches-on-v-sekai-godot.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20221006-rename-to-main.html b/docs/decisions/20221006-rename-to-main.html
index b3a31d2fbf..ac91b11474 100644
--- a/docs/decisions/20221006-rename-to-main.html
+++ b/docs/decisions/20221006-rename-to-main.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20221006-unidot-is-optional.html b/docs/decisions/20221006-unidot-is-optional.html
index eb2872295c..74ac92a678 100644
--- a/docs/decisions/20221006-unidot-is-optional.html
+++ b/docs/decisions/20221006-unidot-is-optional.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20221014-networking-overhaul-proposal.html b/docs/decisions/20221014-networking-overhaul-proposal.html
index b8a717b09f..2ba3e03256 100644
--- a/docs/decisions/20221014-networking-overhaul-proposal.html
+++ b/docs/decisions/20221014-networking-overhaul-proposal.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20221016-v-sekai-view-replication.html b/docs/decisions/20221016-v-sekai-view-replication.html
index 9056a5965f..9598047522 100644
--- a/docs/decisions/20221016-v-sekai-view-replication.html
+++ b/docs/decisions/20221016-v-sekai-view-replication.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20221018-v-sekai-game-update-procedure.html b/docs/decisions/20221018-v-sekai-game-update-procedure.html
index 6dc102dbd6..906557f3fa 100644
--- a/docs/decisions/20221018-v-sekai-game-update-procedure.html
+++ b/docs/decisions/20221018-v-sekai-game-update-procedure.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20221019-develop-a-replication-sync-for-100-000-entities.html b/docs/decisions/20221019-develop-a-replication-sync-for-100-000-entities.html
index 1baae2600d..39671a642c 100644
--- a/docs/decisions/20221019-develop-a-replication-sync-for-100-000-entities.html
+++ b/docs/decisions/20221019-develop-a-replication-sync-for-100-000-entities.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20221019-networking-100000-entities-ownership.html b/docs/decisions/20221019-networking-100000-entities-ownership.html
index 80ac1c0534..29507a2c74 100644
--- a/docs/decisions/20221019-networking-100000-entities-ownership.html
+++ b/docs/decisions/20221019-networking-100000-entities-ownership.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20221019-replicate-sync-100-000-entities.html b/docs/decisions/20221019-replicate-sync-100-000-entities.html
index 936567865d..4ce6a47872 100644
--- a/docs/decisions/20221019-replicate-sync-100-000-entities.html
+++ b/docs/decisions/20221019-replicate-sync-100-000-entities.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20221021-make-it-easier-propose-and-post-bugs.html b/docs/decisions/20221021-make-it-easier-propose-and-post-bugs.html
index 4f656a94c5..59fe6ca03f 100644
--- a/docs/decisions/20221021-make-it-easier-propose-and-post-bugs.html
+++ b/docs/decisions/20221021-make-it-easier-propose-and-post-bugs.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20221022-have-larger-worlds-by-server-state-migration.html b/docs/decisions/20221022-have-larger-worlds-by-server-state-migration.html
index 8f0bec7844..24d83258fd 100644
--- a/docs/decisions/20221022-have-larger-worlds-by-server-state-migration.html
+++ b/docs/decisions/20221022-have-larger-worlds-by-server-state-migration.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20221203-block-direct-pushes-to-main.html b/docs/decisions/20221203-block-direct-pushes-to-main.html
index c2f8f1dd92..306aa43fb6 100644
--- a/docs/decisions/20221203-block-direct-pushes-to-main.html
+++ b/docs/decisions/20221203-block-direct-pushes-to-main.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20221203-target-10-minutes-cicd.html b/docs/decisions/20221203-target-10-minutes-cicd.html
index 7936f3a2d5..d72b23be90 100644
--- a/docs/decisions/20221203-target-10-minutes-cicd.html
+++ b/docs/decisions/20221203-target-10-minutes-cicd.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20221205-debug-linux-export.html b/docs/decisions/20221205-debug-linux-export.html
index 6ea6bc5b9a..44498d93ba 100644
--- a/docs/decisions/20221205-debug-linux-export.html
+++ b/docs/decisions/20221205-debug-linux-export.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20221205-moving-fast-philosophy-development.html b/docs/decisions/20221205-moving-fast-philosophy-development.html
index 59c8c260f0..9daa6a0901 100644
--- a/docs/decisions/20221205-moving-fast-philosophy-development.html
+++ b/docs/decisions/20221205-moving-fast-philosophy-development.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20221205-port-renik-to-many-bone-ik.html b/docs/decisions/20221205-port-renik-to-many-bone-ik.html
index 4a85a6abae..e5224b1ce1 100644
--- a/docs/decisions/20221205-port-renik-to-many-bone-ik.html
+++ b/docs/decisions/20221205-port-renik-to-many-bone-ik.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20221206-export-godot-vrm-to-the-asset-library.html b/docs/decisions/20221206-export-godot-vrm-to-the-asset-library.html
index 225cff6837..539d97348b 100644
--- a/docs/decisions/20221206-export-godot-vrm-to-the-asset-library.html
+++ b/docs/decisions/20221206-export-godot-vrm-to-the-asset-library.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20221212-world-and-character-tools.html b/docs/decisions/20221212-world-and-character-tools.html
index 48964ce49d..7b8274c949 100644
--- a/docs/decisions/20221212-world-and-character-tools.html
+++ b/docs/decisions/20221212-world-and-character-tools.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20221214-powershell-autocomplete-use-right-arrow.html b/docs/decisions/20221214-powershell-autocomplete-use-right-arrow.html
index 29bd5b55ca..210adf56a3 100644
--- a/docs/decisions/20221214-powershell-autocomplete-use-right-arrow.html
+++ b/docs/decisions/20221214-powershell-autocomplete-use-right-arrow.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230106-walking-controller-renik.html b/docs/decisions/20230106-walking-controller-renik.html
index 2d3075d8b8..d38005cfc0 100644
--- a/docs/decisions/20230106-walking-controller-renik.html
+++ b/docs/decisions/20230106-walking-controller-renik.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230107-elixir-uro-dev-sqlite.html b/docs/decisions/20230107-elixir-uro-dev-sqlite.html
index 3d8a7c2c6d..0273894a02 100644
--- a/docs/decisions/20230107-elixir-uro-dev-sqlite.html
+++ b/docs/decisions/20230107-elixir-uro-dev-sqlite.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230108-bolster-creating-the-metaverse.html b/docs/decisions/20230108-bolster-creating-the-metaverse.html
index f5d80470c1..5b38a969d6 100644
--- a/docs/decisions/20230108-bolster-creating-the-metaverse.html
+++ b/docs/decisions/20230108-bolster-creating-the-metaverse.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230108-wmf-video-playback.html b/docs/decisions/20230108-wmf-video-playback.html
index 0c8743beba..74715ac093 100644
--- a/docs/decisions/20230108-wmf-video-playback.html
+++ b/docs/decisions/20230108-wmf-video-playback.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230123-face-helmet-capture.html b/docs/decisions/20230123-face-helmet-capture.html
index c1685d3072..9c496a1100 100644
--- a/docs/decisions/20230123-face-helmet-capture.html
+++ b/docs/decisions/20230123-face-helmet-capture.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230123-integrate-blender-with-gltf-extensions-and-godot.html b/docs/decisions/20230123-integrate-blender-with-gltf-extensions-and-godot.html
index 0214d461ac..8e58d7fc32 100644
--- a/docs/decisions/20230123-integrate-blender-with-gltf-extensions-and-godot.html
+++ b/docs/decisions/20230123-integrate-blender-with-gltf-extensions-and-godot.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230123-no-traversal-loading-screen.html b/docs/decisions/20230123-no-traversal-loading-screen.html
index 48dfbfa8bb..04ae11df03 100644
--- a/docs/decisions/20230123-no-traversal-loading-screen.html
+++ b/docs/decisions/20230123-no-traversal-loading-screen.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230123-player-scripting.html b/docs/decisions/20230123-player-scripting.html
index 71e06c32d3..188f105627 100644
--- a/docs/decisions/20230123-player-scripting.html
+++ b/docs/decisions/20230123-player-scripting.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230123-publish-godot-vrm-4.html b/docs/decisions/20230123-publish-godot-vrm-4.html
index e10943ae80..0000cc2d7f 100644
--- a/docs/decisions/20230123-publish-godot-vrm-4.html
+++ b/docs/decisions/20230123-publish-godot-vrm-4.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230123-ready-the-net-demo.html b/docs/decisions/20230123-ready-the-net-demo.html
index 164a19745b..da6ebc7cce 100644
--- a/docs/decisions/20230123-ready-the-net-demo.html
+++ b/docs/decisions/20230123-ready-the-net-demo.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230123-recording-demo-checklist.html b/docs/decisions/20230123-recording-demo-checklist.html
index ff6938ff56..00584f1375 100644
--- a/docs/decisions/20230123-recording-demo-checklist.html
+++ b/docs/decisions/20230123-recording-demo-checklist.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230123-use-easy-charts-for-observability.html b/docs/decisions/20230123-use-easy-charts-for-observability.html
index 3e55eb9520..9bc97fc000 100644
--- a/docs/decisions/20230123-use-easy-charts-for-observability.html
+++ b/docs/decisions/20230123-use-easy-charts-for-observability.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230125-cover-80-95-percent-of-the-userbase.html b/docs/decisions/20230125-cover-80-95-percent-of-the-userbase.html
index 91aee1984a..31c319487f 100644
--- a/docs/decisions/20230125-cover-80-95-percent-of-the-userbase.html
+++ b/docs/decisions/20230125-cover-80-95-percent-of-the-userbase.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230125-create-an-in-game-tablet-interface-we-can-activate.html b/docs/decisions/20230125-create-an-in-game-tablet-interface-we-can-activate.html
index 2da1af9f99..0fc15cf522 100644
--- a/docs/decisions/20230125-create-an-in-game-tablet-interface-we-can-activate.html
+++ b/docs/decisions/20230125-create-an-in-game-tablet-interface-we-can-activate.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230125-grow-the-community-with-a-reactive-discord-bot.html b/docs/decisions/20230125-grow-the-community-with-a-reactive-discord-bot.html
index a3e9c8ab03..4a957a9652 100644
--- a/docs/decisions/20230125-grow-the-community-with-a-reactive-discord-bot.html
+++ b/docs/decisions/20230125-grow-the-community-with-a-reactive-discord-bot.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230125-possible-futures.html b/docs/decisions/20230125-possible-futures.html
index f822b9f4a2..36b30b61ae 100644
--- a/docs/decisions/20230125-possible-futures.html
+++ b/docs/decisions/20230125-possible-futures.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230125-provide-metadata-to-match-compatibile-maps-and-avatars.html b/docs/decisions/20230125-provide-metadata-to-match-compatibile-maps-and-avatars.html
index 30710c4e08..64ce80528b 100644
--- a/docs/decisions/20230125-provide-metadata-to-match-compatibile-maps-and-avatars.html
+++ b/docs/decisions/20230125-provide-metadata-to-match-compatibile-maps-and-avatars.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230125-two-groups-battle-demo.html b/docs/decisions/20230125-two-groups-battle-demo.html
index e06cb192b0..156a82822a 100644
--- a/docs/decisions/20230125-two-groups-battle-demo.html
+++ b/docs/decisions/20230125-two-groups-battle-demo.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230125-user-generated-scripting-with-libsql-and-wasm.html b/docs/decisions/20230125-user-generated-scripting-with-libsql-and-wasm.html
index 1b20ebb126..0dba725ba2 100644
--- a/docs/decisions/20230125-user-generated-scripting-with-libsql-and-wasm.html
+++ b/docs/decisions/20230125-user-generated-scripting-with-libsql-and-wasm.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230125-without-viz-we-cannot-compare-the-interpolation.html b/docs/decisions/20230125-without-viz-we-cannot-compare-the-interpolation.html
index a67a922581..c53d185c38 100644
--- a/docs/decisions/20230125-without-viz-we-cannot-compare-the-interpolation.html
+++ b/docs/decisions/20230125-without-viz-we-cannot-compare-the-interpolation.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230131-adopt-best-product-development-practices.html b/docs/decisions/20230131-adopt-best-product-development-practices.html
index d91f32f04a..84272e2f02 100644
--- a/docs/decisions/20230131-adopt-best-product-development-practices.html
+++ b/docs/decisions/20230131-adopt-best-product-development-practices.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230131-default-test-plan.html b/docs/decisions/20230131-default-test-plan.html
index 598baae7ca..f83447d899 100644
--- a/docs/decisions/20230131-default-test-plan.html
+++ b/docs/decisions/20230131-default-test-plan.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230131-meeting-at-gdc-2023.html b/docs/decisions/20230131-meeting-at-gdc-2023.html
index 1bcb34c683..978cb4592f 100644
--- a/docs/decisions/20230131-meeting-at-gdc-2023.html
+++ b/docs/decisions/20230131-meeting-at-gdc-2023.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230310-IREE-backend-for-machine-learning-computations.html b/docs/decisions/20230310-IREE-backend-for-machine-learning-computations.html
index 468b286a71..62c622450a 100644
--- a/docs/decisions/20230310-IREE-backend-for-machine-learning-computations.html
+++ b/docs/decisions/20230310-IREE-backend-for-machine-learning-computations.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230310-don't-merge-incomplete-work.html b/docs/decisions/20230310-don't-merge-incomplete-work.html
index 691fad0a5b..36be916174 100644
--- a/docs/decisions/20230310-don't-merge-incomplete-work.html
+++ b/docs/decisions/20230310-don't-merge-incomplete-work.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230310-xml-based-tests.html b/docs/decisions/20230310-xml-based-tests.html
index c085cd1f6a..8309b44775 100644
--- a/docs/decisions/20230310-xml-based-tests.html
+++ b/docs/decisions/20230310-xml-based-tests.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230408-v-sekai-launcher.html b/docs/decisions/20230408-v-sekai-launcher.html
index 31d6b3d0bb..138188c8fb 100644
--- a/docs/decisions/20230408-v-sekai-launcher.html
+++ b/docs/decisions/20230408-v-sekai-launcher.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230415-load-collaborate.html b/docs/decisions/20230415-load-collaborate.html
index 4cc660747d..d1510a5547 100644
--- a/docs/decisions/20230415-load-collaborate.html
+++ b/docs/decisions/20230415-load-collaborate.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230415-procedural-variations-props-envs-avatars.html b/docs/decisions/20230415-procedural-variations-props-envs-avatars.html
index 2aa5ef1aed..699eb2eddb 100644
--- a/docs/decisions/20230415-procedural-variations-props-envs-avatars.html
+++ b/docs/decisions/20230415-procedural-variations-props-envs-avatars.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230415-rgbaf-to-store-integers.html b/docs/decisions/20230415-rgbaf-to-store-integers.html
index ec39d0fe08..063f1e7ca6 100644
--- a/docs/decisions/20230415-rgbaf-to-store-integers.html
+++ b/docs/decisions/20230415-rgbaf-to-store-integers.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230419-limited-tracker-placement.html b/docs/decisions/20230419-limited-tracker-placement.html
index 0bcebc15f6..64a323c00b 100644
--- a/docs/decisions/20230419-limited-tracker-placement.html
+++ b/docs/decisions/20230419-limited-tracker-placement.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230419-package-godot-for-pkgin.html b/docs/decisions/20230419-package-godot-for-pkgin.html
index 2b66584fa9..2482a9f11e 100644
--- a/docs/decisions/20230419-package-godot-for-pkgin.html
+++ b/docs/decisions/20230419-package-godot-for-pkgin.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230429-git-subrepo-challenges.html b/docs/decisions/20230429-git-subrepo-challenges.html
index 14d1417bb4..7bfd5e2b4f 100644
--- a/docs/decisions/20230429-git-subrepo-challenges.html
+++ b/docs/decisions/20230429-git-subrepo-challenges.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230429-improve-collab.html b/docs/decisions/20230429-improve-collab.html
index 164a566920..37f66694ef 100644
--- a/docs/decisions/20230429-improve-collab.html
+++ b/docs/decisions/20230429-improve-collab.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230429-v-sekai-roadmap.html b/docs/decisions/20230429-v-sekai-roadmap.html
index c31322ebee..94ba13711f 100644
--- a/docs/decisions/20230429-v-sekai-roadmap.html
+++ b/docs/decisions/20230429-v-sekai-roadmap.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230502-add-iree-to-godot-engine-for-image-superresolution.html b/docs/decisions/20230502-add-iree-to-godot-engine-for-image-superresolution.html
index f31887dd73..295c7b771a 100644
--- a/docs/decisions/20230502-add-iree-to-godot-engine-for-image-superresolution.html
+++ b/docs/decisions/20230502-add-iree-to-godot-engine-for-image-superresolution.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230505-automated-avatar-garment-rigging.html b/docs/decisions/20230505-automated-avatar-garment-rigging.html
index a153083137..1f5dc16b4e 100644
--- a/docs/decisions/20230505-automated-avatar-garment-rigging.html
+++ b/docs/decisions/20230505-automated-avatar-garment-rigging.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230505-consistent-v-sekai-naming.html b/docs/decisions/20230505-consistent-v-sekai-naming.html
index 26d58bfa36..49bbb6b00d 100644
--- a/docs/decisions/20230505-consistent-v-sekai-naming.html
+++ b/docs/decisions/20230505-consistent-v-sekai-naming.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230505-cross-platform-artwork-distribution.html b/docs/decisions/20230505-cross-platform-artwork-distribution.html
index f71bcae44b..2c997cced8 100644
--- a/docs/decisions/20230505-cross-platform-artwork-distribution.html
+++ b/docs/decisions/20230505-cross-platform-artwork-distribution.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230505-polygon-mesh-based-sculpting-tools.html b/docs/decisions/20230505-polygon-mesh-based-sculpting-tools.html
index 9887b52dd3..98f897b7cf 100644
--- a/docs/decisions/20230505-polygon-mesh-based-sculpting-tools.html
+++ b/docs/decisions/20230505-polygon-mesh-based-sculpting-tools.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230505-v-sekai-ai-completion.html b/docs/decisions/20230505-v-sekai-ai-completion.html
index b34438fd86..89cc342031 100644
--- a/docs/decisions/20230505-v-sekai-ai-completion.html
+++ b/docs/decisions/20230505-v-sekai-ai-completion.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230507-avatar-publishing-workflow-portability.html b/docs/decisions/20230507-avatar-publishing-workflow-portability.html
index 47c6715139..e51cdb2536 100644
--- a/docs/decisions/20230507-avatar-publishing-workflow-portability.html
+++ b/docs/decisions/20230507-avatar-publishing-workflow-portability.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230507-distributed-sim.html b/docs/decisions/20230507-distributed-sim.html
index 850fcf00c0..2573ff4a9a 100644
--- a/docs/decisions/20230507-distributed-sim.html
+++ b/docs/decisions/20230507-distributed-sim.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230507-supabase.html b/docs/decisions/20230507-supabase.html
index 7602be1710..c5bfbf8e0a 100644
--- a/docs/decisions/20230507-supabase.html
+++ b/docs/decisions/20230507-supabase.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230508-novel-3d-views.html b/docs/decisions/20230508-novel-3d-views.html
index 0d7c3f3baf..dedff387ed 100644
--- a/docs/decisions/20230508-novel-3d-views.html
+++ b/docs/decisions/20230508-novel-3d-views.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230509-wasm-data-exchange.html b/docs/decisions/20230509-wasm-data-exchange.html
index 62b28eae96..3526407ff0 100644
--- a/docs/decisions/20230509-wasm-data-exchange.html
+++ b/docs/decisions/20230509-wasm-data-exchange.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230516-additional-3d-import.html b/docs/decisions/20230516-additional-3d-import.html
index a717eee54b..afec4e314b 100644
--- a/docs/decisions/20230516-additional-3d-import.html
+++ b/docs/decisions/20230516-additional-3d-import.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html b/docs/decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html
index 0cbf3a8cf0..83f5737528 100644
--- a/docs/decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html
+++ b/docs/decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230516-v-sekai-roadmap.html b/docs/decisions/20230516-v-sekai-roadmap.html
index 510f9a2107..274778183b 100644
--- a/docs/decisions/20230516-v-sekai-roadmap.html
+++ b/docs/decisions/20230516-v-sekai-roadmap.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230519-add-vrm-omi-personality-gltf-extension.html b/docs/decisions/20230519-add-vrm-omi-personality-gltf-extension.html
index aee4c0eca1..7c4f08607b 100644
--- a/docs/decisions/20230519-add-vrm-omi-personality-gltf-extension.html
+++ b/docs/decisions/20230519-add-vrm-omi-personality-gltf-extension.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230519-v-sekai-roadmap.html b/docs/decisions/20230519-v-sekai-roadmap.html
index b2fc4133ce..f018425e11 100644
--- a/docs/decisions/20230519-v-sekai-roadmap.html
+++ b/docs/decisions/20230519-v-sekai-roadmap.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230521-audio-jitter-buffer-voip.html b/docs/decisions/20230521-audio-jitter-buffer-voip.html
index 28b15da1b6..4cc8cba70f 100644
--- a/docs/decisions/20230521-audio-jitter-buffer-voip.html
+++ b/docs/decisions/20230521-audio-jitter-buffer-voip.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230522-JOKE-fictional-blood-combat.html b/docs/decisions/20230522-JOKE-fictional-blood-combat.html
index 979f3a9d10..597fb35474 100644
--- a/docs/decisions/20230522-JOKE-fictional-blood-combat.html
+++ b/docs/decisions/20230522-JOKE-fictional-blood-combat.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230523-marketing-cycle.html b/docs/decisions/20230523-marketing-cycle.html
index 0dae53c7fb..72bac833d2 100644
--- a/docs/decisions/20230523-marketing-cycle.html
+++ b/docs/decisions/20230523-marketing-cycle.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230525-animation-ik-node.html b/docs/decisions/20230525-animation-ik-node.html
index e19933234e..cbe4bb72c8 100644
--- a/docs/decisions/20230525-animation-ik-node.html
+++ b/docs/decisions/20230525-animation-ik-node.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230527-godot-test-game.html b/docs/decisions/20230527-godot-test-game.html
index 6a1cac2d4a..0dd67c89fb 100644
--- a/docs/decisions/20230527-godot-test-game.html
+++ b/docs/decisions/20230527-godot-test-game.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230527-organization.html b/docs/decisions/20230527-organization.html
index 3f960dc8cf..4de62f0fbf 100644
--- a/docs/decisions/20230527-organization.html
+++ b/docs/decisions/20230527-organization.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230527-server-cdn-session-url.html b/docs/decisions/20230527-server-cdn-session-url.html
index add9df0f84..4bb57f6a2a 100644
--- a/docs/decisions/20230527-server-cdn-session-url.html
+++ b/docs/decisions/20230527-server-cdn-session-url.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230527-server-performance-test.html b/docs/decisions/20230527-server-performance-test.html
index 3607d9bb46..871e5608e1 100644
--- a/docs/decisions/20230527-server-performance-test.html
+++ b/docs/decisions/20230527-server-performance-test.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230527-server-side-content-validation.html b/docs/decisions/20230527-server-side-content-validation.html
index 572992b436..c93e038f95 100644
--- a/docs/decisions/20230527-server-side-content-validation.html
+++ b/docs/decisions/20230527-server-side-content-validation.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230527-server-sidecar.html b/docs/decisions/20230527-server-sidecar.html
index 5078f99823..1cc47366d9 100644
--- a/docs/decisions/20230527-server-sidecar.html
+++ b/docs/decisions/20230527-server-sidecar.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230527-v-sekai-roadmap.html b/docs/decisions/20230527-v-sekai-roadmap.html
index c02ce9952c..b4eda8b2e0 100644
--- a/docs/decisions/20230527-v-sekai-roadmap.html
+++ b/docs/decisions/20230527-v-sekai-roadmap.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230531-godot-engine-ipad.html b/docs/decisions/20230531-godot-engine-ipad.html
index 3ae29a8f11..6b8eb5a375 100644
--- a/docs/decisions/20230531-godot-engine-ipad.html
+++ b/docs/decisions/20230531-godot-engine-ipad.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230531-godot-engine-learning.html b/docs/decisions/20230531-godot-engine-learning.html
index da7c290dc4..8ea0cc98df 100644
--- a/docs/decisions/20230531-godot-engine-learning.html
+++ b/docs/decisions/20230531-godot-engine-learning.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230602-limited-tracker-placement.html b/docs/decisions/20230602-limited-tracker-placement.html
index 7ec7aeb1ad..cc664a9aa5 100644
--- a/docs/decisions/20230602-limited-tracker-placement.html
+++ b/docs/decisions/20230602-limited-tracker-placement.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230602-pmx-module-integration.html b/docs/decisions/20230602-pmx-module-integration.html
index aa2a3d9f6f..d8bfc42ad3 100644
--- a/docs/decisions/20230602-pmx-module-integration.html
+++ b/docs/decisions/20230602-pmx-module-integration.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230602-v-sekai-roadmap.html b/docs/decisions/20230602-v-sekai-roadmap.html
index e10f85aea7..57e6c95378 100644
--- a/docs/decisions/20230602-v-sekai-roadmap.html
+++ b/docs/decisions/20230602-v-sekai-roadmap.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230608-v-sekai-roadmap.html b/docs/decisions/20230608-v-sekai-roadmap.html
index 94fab73dc6..a13b37a45a 100644
--- a/docs/decisions/20230608-v-sekai-roadmap.html
+++ b/docs/decisions/20230608-v-sekai-roadmap.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230611-wasm-in-v-sekai.html b/docs/decisions/20230611-wasm-in-v-sekai.html
index b49d1a9c50..451dc93105 100644
--- a/docs/decisions/20230611-wasm-in-v-sekai.html
+++ b/docs/decisions/20230611-wasm-in-v-sekai.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230614-llm-statechart.html b/docs/decisions/20230614-llm-statechart.html
index e1fb872b2f..053fd801ef 100644
--- a/docs/decisions/20230614-llm-statechart.html
+++ b/docs/decisions/20230614-llm-statechart.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230616-pmx-to-vrm.html b/docs/decisions/20230616-pmx-to-vrm.html
index 6ae2413d50..844cbd56f4 100644
--- a/docs/decisions/20230616-pmx-to-vrm.html
+++ b/docs/decisions/20230616-pmx-to-vrm.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230618-v-sekai-roadmap.html b/docs/decisions/20230618-v-sekai-roadmap.html
index 1482f2b4b2..81cf9ff2fa 100644
--- a/docs/decisions/20230618-v-sekai-roadmap.html
+++ b/docs/decisions/20230618-v-sekai-roadmap.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230619-membrane-framework-for-mesh-processing.html b/docs/decisions/20230619-membrane-framework-for-mesh-processing.html
index 47652a31d8..f154d2d76a 100644
--- a/docs/decisions/20230619-membrane-framework-for-mesh-processing.html
+++ b/docs/decisions/20230619-membrane-framework-for-mesh-processing.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230619-move-cockroachdb-to-yugabyte.html b/docs/decisions/20230619-move-cockroachdb-to-yugabyte.html
index 43ee28a598..479167fc4a 100644
--- a/docs/decisions/20230619-move-cockroachdb-to-yugabyte.html
+++ b/docs/decisions/20230619-move-cockroachdb-to-yugabyte.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230620-doi-github.html b/docs/decisions/20230620-doi-github.html
index 34af4d3b35..86b99dfd2f 100644
--- a/docs/decisions/20230620-doi-github.html
+++ b/docs/decisions/20230620-doi-github.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230620-t5-jsonformer-xstate.html b/docs/decisions/20230620-t5-jsonformer-xstate.html
index acdef8e820..75c3299523 100644
--- a/docs/decisions/20230620-t5-jsonformer-xstate.html
+++ b/docs/decisions/20230620-t5-jsonformer-xstate.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230623-fdn-reverb-solution.html b/docs/decisions/20230623-fdn-reverb-solution.html
index 49e0127db3..b6291291db 100644
--- a/docs/decisions/20230623-fdn-reverb-solution.html
+++ b/docs/decisions/20230623-fdn-reverb-solution.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230624-v-sekai-roadmap.html b/docs/decisions/20230624-v-sekai-roadmap.html
index e05cca682e..4c080c5ef2 100644
--- a/docs/decisions/20230624-v-sekai-roadmap.html
+++ b/docs/decisions/20230624-v-sekai-roadmap.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230626-godot-vrm1-addon.html b/docs/decisions/20230626-godot-vrm1-addon.html
index 5758c40df4..c56942b416 100644
--- a/docs/decisions/20230626-godot-vrm1-addon.html
+++ b/docs/decisions/20230626-godot-vrm1-addon.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230630-vsekai-goal-meeting.html b/docs/decisions/20230630-vsekai-goal-meeting.html
index e98cd71f94..113cc31389 100644
--- a/docs/decisions/20230630-vsekai-goal-meeting.html
+++ b/docs/decisions/20230630-vsekai-goal-meeting.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230701-vsekai-broken-down-goals.html b/docs/decisions/20230701-vsekai-broken-down-goals.html
index 8d086a25c4..4a07438f33 100644
--- a/docs/decisions/20230701-vsekai-broken-down-goals.html
+++ b/docs/decisions/20230701-vsekai-broken-down-goals.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230716-enhancing-avatar-creation-process-01-regular.html b/docs/decisions/20230716-enhancing-avatar-creation-process-01-regular.html
index 488898f1cb..7a7eb5e8f7 100644
--- a/docs/decisions/20230716-enhancing-avatar-creation-process-01-regular.html
+++ b/docs/decisions/20230716-enhancing-avatar-creation-process-01-regular.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230716-enhancing-avatar-creation-process-02-advanced.html b/docs/decisions/20230716-enhancing-avatar-creation-process-02-advanced.html
index e4ea30c7a2..be250cb4ae 100644
--- a/docs/decisions/20230716-enhancing-avatar-creation-process-02-advanced.html
+++ b/docs/decisions/20230716-enhancing-avatar-creation-process-02-advanced.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230719-dual-databases-cockroachdb-khepri.html b/docs/decisions/20230719-dual-databases-cockroachdb-khepri.html
index a8cccd83c2..452e281a0b 100644
--- a/docs/decisions/20230719-dual-databases-cockroachdb-khepri.html
+++ b/docs/decisions/20230719-dual-databases-cockroachdb-khepri.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230719-pose-kusudama-constraints-in-vr.html b/docs/decisions/20230719-pose-kusudama-constraints-in-vr.html
index 9033a54891..e3dd3a2516 100644
--- a/docs/decisions/20230719-pose-kusudama-constraints-in-vr.html
+++ b/docs/decisions/20230719-pose-kusudama-constraints-in-vr.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html b/docs/decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html
index 981cc0b145..20f9216861 100644
--- a/docs/decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html
+++ b/docs/decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230803-idle-rpg-home.html b/docs/decisions/20230803-idle-rpg-home.html
index d528b20765..74023929ce 100644
--- a/docs/decisions/20230803-idle-rpg-home.html
+++ b/docs/decisions/20230803-idle-rpg-home.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230803-jolt-gextension-to-module.html b/docs/decisions/20230803-jolt-gextension-to-module.html
index 8532b2bce0..df080303df 100644
--- a/docs/decisions/20230803-jolt-gextension-to-module.html
+++ b/docs/decisions/20230803-jolt-gextension-to-module.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230803-publish-vrm-to-assetlibrary.html b/docs/decisions/20230803-publish-vrm-to-assetlibrary.html
index c0a1ace60d..f43c9dfa49 100644
--- a/docs/decisions/20230803-publish-vrm-to-assetlibrary.html
+++ b/docs/decisions/20230803-publish-vrm-to-assetlibrary.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230803-subrepo-addon-management.html b/docs/decisions/20230803-subrepo-addon-management.html
index fe63355e91..d070e6e8f6 100644
--- a/docs/decisions/20230803-subrepo-addon-management.html
+++ b/docs/decisions/20230803-subrepo-addon-management.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230804-dokku.html b/docs/decisions/20230804-dokku.html
index f7cad3ba9e..26db9e67cb 100644
--- a/docs/decisions/20230804-dokku.html
+++ b/docs/decisions/20230804-dokku.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230806-music-gen.html b/docs/decisions/20230806-music-gen.html
index 7a491d665b..f1ce26ef53 100644
--- a/docs/decisions/20230806-music-gen.html
+++ b/docs/decisions/20230806-music-gen.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230806-v-sekai-ipad-projection-compatibility.html b/docs/decisions/20230806-v-sekai-ipad-projection-compatibility.html
index 3bbe36678b..d545bed6b7 100644
--- a/docs/decisions/20230806-v-sekai-ipad-projection-compatibility.html
+++ b/docs/decisions/20230806-v-sekai-ipad-projection-compatibility.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230811-punchline-reports.html b/docs/decisions/20230811-punchline-reports.html
index f763b28d2e..9e57babfc8 100644
--- a/docs/decisions/20230811-punchline-reports.html
+++ b/docs/decisions/20230811-punchline-reports.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230812-constraint-all-bones.html b/docs/decisions/20230812-constraint-all-bones.html
index f00d882a53..846e99017b 100644
--- a/docs/decisions/20230812-constraint-all-bones.html
+++ b/docs/decisions/20230812-constraint-all-bones.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230812-gocd-agent-setup.html b/docs/decisions/20230812-gocd-agent-setup.html
index faa6b05f2a..dbfa1a0579 100644
--- a/docs/decisions/20230812-gocd-agent-setup.html
+++ b/docs/decisions/20230812-gocd-agent-setup.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html b/docs/decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html
index cac68c93c2..c75d737ce0 100644
--- a/docs/decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html
+++ b/docs/decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230812-vsekai-update-process.html b/docs/decisions/20230812-vsekai-update-process.html
index def4404e7a..ab0ac099f3 100644
--- a/docs/decisions/20230812-vsekai-update-process.html
+++ b/docs/decisions/20230812-vsekai-update-process.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230813-blender-runner-into-membrane-framework.html b/docs/decisions/20230813-blender-runner-into-membrane-framework.html
index e0cfd57966..5ca8447eef 100644
--- a/docs/decisions/20230813-blender-runner-into-membrane-framework.html
+++ b/docs/decisions/20230813-blender-runner-into-membrane-framework.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html b/docs/decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html
index 7a2bb23279..0f3666b2b9 100644
--- a/docs/decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html	
+++ b/docs/decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html	
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230819-train-game.html b/docs/decisions/20230819-train-game.html
index f29bb72cc9..41eb9e38ca 100644
--- a/docs/decisions/20230819-train-game.html
+++ b/docs/decisions/20230819-train-game.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230823-speech-to-blendshapes.html b/docs/decisions/20230823-speech-to-blendshapes.html
index cf235c3339..c6a5388e41 100644
--- a/docs/decisions/20230823-speech-to-blendshapes.html
+++ b/docs/decisions/20230823-speech-to-blendshapes.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230824-subdiv-for-lods.html b/docs/decisions/20230824-subdiv-for-lods.html
index 0c58cd0c95..18211d3266 100644
--- a/docs/decisions/20230824-subdiv-for-lods.html
+++ b/docs/decisions/20230824-subdiv-for-lods.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230829-omifest-2023.html b/docs/decisions/20230829-omifest-2023.html
index 15a63aee3c..bd7361ccd0 100644
--- a/docs/decisions/20230829-omifest-2023.html
+++ b/docs/decisions/20230829-omifest-2023.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230830-better-backend-services.html b/docs/decisions/20230830-better-backend-services.html
index 5246a43bd2..60462cbd45 100644
--- a/docs/decisions/20230830-better-backend-services.html
+++ b/docs/decisions/20230830-better-backend-services.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230830-better-object-pick.html b/docs/decisions/20230830-better-object-pick.html
index e69dd72e75..2ef1f464cc 100644
--- a/docs/decisions/20230830-better-object-pick.html
+++ b/docs/decisions/20230830-better-object-pick.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230830-generating-v-sekai-worlds.html b/docs/decisions/20230830-generating-v-sekai-worlds.html
index a0de12b10f..b4285000a7 100644
--- a/docs/decisions/20230830-generating-v-sekai-worlds.html
+++ b/docs/decisions/20230830-generating-v-sekai-worlds.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230831-fixing-menus.html b/docs/decisions/20230831-fixing-menus.html
index 3901a83544..ad78e57af8 100644
--- a/docs/decisions/20230831-fixing-menus.html
+++ b/docs/decisions/20230831-fixing-menus.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230831-fixing-upload-limits.html b/docs/decisions/20230831-fixing-upload-limits.html
index ce04226120..6740aafaf1 100644
--- a/docs/decisions/20230831-fixing-upload-limits.html
+++ b/docs/decisions/20230831-fixing-upload-limits.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230903-replicate-vrm-transform.html b/docs/decisions/20230903-replicate-vrm-transform.html
index 9810a3f299..677877b10e 100644
--- a/docs/decisions/20230903-replicate-vrm-transform.html
+++ b/docs/decisions/20230903-replicate-vrm-transform.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230908-bendable-screen-generative-assistant-ggml.html b/docs/decisions/20230908-bendable-screen-generative-assistant-ggml.html
index e3229415e7..356859f49d 100644
--- a/docs/decisions/20230908-bendable-screen-generative-assistant-ggml.html
+++ b/docs/decisions/20230908-bendable-screen-generative-assistant-ggml.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230911-can-poly-green-coords-extend-to-3d.html b/docs/decisions/20230911-can-poly-green-coords-extend-to-3d.html
index 3106327225..2697443e6c 100644
--- a/docs/decisions/20230911-can-poly-green-coords-extend-to-3d.html
+++ b/docs/decisions/20230911-can-poly-green-coords-extend-to-3d.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230911-first-alpha-tag.html b/docs/decisions/20230911-first-alpha-tag.html
index 2ecfc10fb5..9d0e6b5c13 100644
--- a/docs/decisions/20230911-first-alpha-tag.html
+++ b/docs/decisions/20230911-first-alpha-tag.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230911-xpr.exs.html b/docs/decisions/20230911-xpr.exs.html
index cda115ce6d..407e0fea0d 100644
--- a/docs/decisions/20230911-xpr.exs.html
+++ b/docs/decisions/20230911-xpr.exs.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230911-xr-grid-with-drawing.html b/docs/decisions/20230911-xr-grid-with-drawing.html
index 3eb322bc8a..9b2167f4f1 100644
--- a/docs/decisions/20230911-xr-grid-with-drawing.html
+++ b/docs/decisions/20230911-xr-grid-with-drawing.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230912-target-most-popular-resolution.html b/docs/decisions/20230912-target-most-popular-resolution.html
index 95c9c05534..9920f63aea 100644
--- a/docs/decisions/20230912-target-most-popular-resolution.html
+++ b/docs/decisions/20230912-target-most-popular-resolution.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230913-V-Sekai-bugs.html b/docs/decisions/20230913-V-Sekai-bugs.html
index 1c3f9abe0e..f1d342e15b 100644
--- a/docs/decisions/20230913-V-Sekai-bugs.html
+++ b/docs/decisions/20230913-V-Sekai-bugs.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230920-godot-project-search.html b/docs/decisions/20230920-godot-project-search.html
index 657f78f302..f4c7b06d36 100644
--- a/docs/decisions/20230920-godot-project-search.html
+++ b/docs/decisions/20230920-godot-project-search.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20230922-spacetime-shadow-shards-sync.html b/docs/decisions/20230922-spacetime-shadow-shards-sync.html
index 24c7854622..16fe6ccb5d 100644
--- a/docs/decisions/20230922-spacetime-shadow-shards-sync.html
+++ b/docs/decisions/20230922-spacetime-shadow-shards-sync.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231019-quest3-mocap-steam-lighthouse.html b/docs/decisions/20231019-quest3-mocap-steam-lighthouse.html
index 0c7dad1644..6c4f65d082 100644
--- a/docs/decisions/20231019-quest3-mocap-steam-lighthouse.html
+++ b/docs/decisions/20231019-quest3-mocap-steam-lighthouse.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231020-llama-cpp-mistral-npc.html b/docs/decisions/20231020-llama-cpp-mistral-npc.html
index 873b889896..31ea55c50a 100644
--- a/docs/decisions/20231020-llama-cpp-mistral-npc.html
+++ b/docs/decisions/20231020-llama-cpp-mistral-npc.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231022-hover-to-ocean-game.html b/docs/decisions/20231022-hover-to-ocean-game.html
index dbda934b06..53dade4bd0 100644
--- a/docs/decisions/20231022-hover-to-ocean-game.html
+++ b/docs/decisions/20231022-hover-to-ocean-game.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231024-finetuning-workflow.html b/docs/decisions/20231024-finetuning-workflow.html
index eda4565956..9b2a4f60e7 100644
--- a/docs/decisions/20231024-finetuning-workflow.html
+++ b/docs/decisions/20231024-finetuning-workflow.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231024-training-simulators.html b/docs/decisions/20231024-training-simulators.html
index d0091263ec..a601b40b1c 100644
--- a/docs/decisions/20231024-training-simulators.html
+++ b/docs/decisions/20231024-training-simulators.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231026-blender-steam-beta-version.html b/docs/decisions/20231026-blender-steam-beta-version.html
index 6d480c9599..b40cc2ffae 100644
--- a/docs/decisions/20231026-blender-steam-beta-version.html
+++ b/docs/decisions/20231026-blender-steam-beta-version.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231027-apartment-building-vr.html b/docs/decisions/20231027-apartment-building-vr.html
index b892d3f219..d0454228a3 100644
--- a/docs/decisions/20231027-apartment-building-vr.html
+++ b/docs/decisions/20231027-apartment-building-vr.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231027-drawing-concept-to-blockout.html b/docs/decisions/20231027-drawing-concept-to-blockout.html
index e8b2c80659..3dc8db37eb 100644
--- a/docs/decisions/20231027-drawing-concept-to-blockout.html
+++ b/docs/decisions/20231027-drawing-concept-to-blockout.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231027-dreamcraft3d-workflow.html b/docs/decisions/20231027-dreamcraft3d-workflow.html
index 55596fdd75..308c88ac75 100644
--- a/docs/decisions/20231027-dreamcraft3d-workflow.html
+++ b/docs/decisions/20231027-dreamcraft3d-workflow.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231027-write-a-list-of-github-pull-requests.html b/docs/decisions/20231027-write-a-list-of-github-pull-requests.html
index 0acfac181e..d601fa5368 100644
--- a/docs/decisions/20231027-write-a-list-of-github-pull-requests.html
+++ b/docs/decisions/20231027-write-a-list-of-github-pull-requests.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231104-flatbuffer_packed_scenes.html b/docs/decisions/20231104-flatbuffer_packed_scenes.html
index 8c5b522585..793838afb3 100644
--- a/docs/decisions/20231104-flatbuffer_packed_scenes.html
+++ b/docs/decisions/20231104-flatbuffer_packed_scenes.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231105-pdf-embed-raster-svg-vr.html b/docs/decisions/20231105-pdf-embed-raster-svg-vr.html
index 680af20119..5f329f4c92 100644
--- a/docs/decisions/20231105-pdf-embed-raster-svg-vr.html
+++ b/docs/decisions/20231105-pdf-embed-raster-svg-vr.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231108-ansible-new-server-provisioning.html b/docs/decisions/20231108-ansible-new-server-provisioning.html
index 3312be0694..559fd76da1 100644
--- a/docs/decisions/20231108-ansible-new-server-provisioning.html
+++ b/docs/decisions/20231108-ansible-new-server-provisioning.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231108-munich-godot-engine-conference.html b/docs/decisions/20231108-munich-godot-engine-conference.html
index ee3201b23c..38564383ee 100644
--- a/docs/decisions/20231108-munich-godot-engine-conference.html
+++ b/docs/decisions/20231108-munich-godot-engine-conference.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231108-neon-1-gb-scene-storage.html b/docs/decisions/20231108-neon-1-gb-scene-storage.html
index ebe0b32cca..a9e9eb700d 100644
--- a/docs/decisions/20231108-neon-1-gb-scene-storage.html
+++ b/docs/decisions/20231108-neon-1-gb-scene-storage.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231108-neon-postgresql.html b/docs/decisions/20231108-neon-postgresql.html
index 3c010abf73..5f6f91687e 100644
--- a/docs/decisions/20231108-neon-postgresql.html
+++ b/docs/decisions/20231108-neon-postgresql.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231108-neon-vercel-functions-toy-problem.html b/docs/decisions/20231108-neon-vercel-functions-toy-problem.html
index cc308a1abe..179b5ed55e 100644
--- a/docs/decisions/20231108-neon-vercel-functions-toy-problem.html
+++ b/docs/decisions/20231108-neon-vercel-functions-toy-problem.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231108-nier-automata-world-expansion.html b/docs/decisions/20231108-nier-automata-world-expansion.html
index e227412e0a..0df4999d24 100644
--- a/docs/decisions/20231108-nier-automata-world-expansion.html
+++ b/docs/decisions/20231108-nier-automata-world-expansion.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231108-postgres-bytea-optimizations.html b/docs/decisions/20231108-postgres-bytea-optimizations.html
index e74b7293e2..45d2e317e8 100644
--- a/docs/decisions/20231108-postgres-bytea-optimizations.html
+++ b/docs/decisions/20231108-postgres-bytea-optimizations.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231108-v-sekai-chat-bot.html b/docs/decisions/20231108-v-sekai-chat-bot.html
index 3d382bc477..108dbe91ba 100644
--- a/docs/decisions/20231108-v-sekai-chat-bot.html
+++ b/docs/decisions/20231108-v-sekai-chat-bot.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231109-discord-polygonjs-generator.html b/docs/decisions/20231109-discord-polygonjs-generator.html
index 74a7e879e9..7dfa5f219d 100644
--- a/docs/decisions/20231109-discord-polygonjs-generator.html
+++ b/docs/decisions/20231109-discord-polygonjs-generator.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231110-ai-based-outlier-detection.html b/docs/decisions/20231110-ai-based-outlier-detection.html
index b150cbbb72..a00342ca0c 100644
--- a/docs/decisions/20231110-ai-based-outlier-detection.html
+++ b/docs/decisions/20231110-ai-based-outlier-detection.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231110-better-pipeline-tools.html b/docs/decisions/20231110-better-pipeline-tools.html
index a52f12eec8..c514844300 100644
--- a/docs/decisions/20231110-better-pipeline-tools.html
+++ b/docs/decisions/20231110-better-pipeline-tools.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231110-blender-manual-t-pose.html b/docs/decisions/20231110-blender-manual-t-pose.html
index aa69de5730..64cb0eb950 100644
--- a/docs/decisions/20231110-blender-manual-t-pose.html
+++ b/docs/decisions/20231110-blender-manual-t-pose.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231110-efficient-llm-training.html b/docs/decisions/20231110-efficient-llm-training.html
index 10dd600075..b962619dc3 100644
--- a/docs/decisions/20231110-efficient-llm-training.html
+++ b/docs/decisions/20231110-efficient-llm-training.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231110-v-sekai-dependencies.html b/docs/decisions/20231110-v-sekai-dependencies.html
index 99c7450618..3b4bfd85a1 100644
--- a/docs/decisions/20231110-v-sekai-dependencies.html
+++ b/docs/decisions/20231110-v-sekai-dependencies.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231111-ayon-evaluation.html b/docs/decisions/20231111-ayon-evaluation.html
index 3cdd70af93..49b60ba1ef 100644
--- a/docs/decisions/20231111-ayon-evaluation.html
+++ b/docs/decisions/20231111-ayon-evaluation.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231112-archive-projects.html b/docs/decisions/20231112-archive-projects.html
index d57a253669..d76af81f8b 100644
--- a/docs/decisions/20231112-archive-projects.html
+++ b/docs/decisions/20231112-archive-projects.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231112-validation-service.html b/docs/decisions/20231112-validation-service.html
index d6993b8d44..b05d129cec 100644
--- a/docs/decisions/20231112-validation-service.html
+++ b/docs/decisions/20231112-validation-service.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231114-elixir-definition-of-godot-types.html b/docs/decisions/20231114-elixir-definition-of-godot-types.html
index 332c18d6f2..2a3c8840a3 100644
--- a/docs/decisions/20231114-elixir-definition-of-godot-types.html
+++ b/docs/decisions/20231114-elixir-definition-of-godot-types.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231114-maintain-svgcleaner.html b/docs/decisions/20231114-maintain-svgcleaner.html
index 0dcaaed7b4..00af3b00a1 100644
--- a/docs/decisions/20231114-maintain-svgcleaner.html
+++ b/docs/decisions/20231114-maintain-svgcleaner.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231114-upload-creative-commons-fbx-test-files.html b/docs/decisions/20231114-upload-creative-commons-fbx-test-files.html
index 3878e19dc8..944da3b930 100644
--- a/docs/decisions/20231114-upload-creative-commons-fbx-test-files.html
+++ b/docs/decisions/20231114-upload-creative-commons-fbx-test-files.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231125-v-sekai-report.html b/docs/decisions/20231125-v-sekai-report.html
index 4b44427569..054945e5b8 100644
--- a/docs/decisions/20231125-v-sekai-report.html
+++ b/docs/decisions/20231125-v-sekai-report.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231126-v-sekai-report.html b/docs/decisions/20231126-v-sekai-report.html
index 2499de9514..2aac8577d8 100644
--- a/docs/decisions/20231126-v-sekai-report.html
+++ b/docs/decisions/20231126-v-sekai-report.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231127-performance-test.html b/docs/decisions/20231127-performance-test.html
index 7cccebd687..0a78e0922a 100644
--- a/docs/decisions/20231127-performance-test.html
+++ b/docs/decisions/20231127-performance-test.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231201-headless-launcher-backend.html b/docs/decisions/20231201-headless-launcher-backend.html
index 757e98a0ec..33c96677dc 100644
--- a/docs/decisions/20231201-headless-launcher-backend.html
+++ b/docs/decisions/20231201-headless-launcher-backend.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231201-xr-hands-animation-node.html b/docs/decisions/20231201-xr-hands-animation-node.html
index 63d6320071..3b013d3c39 100644
--- a/docs/decisions/20231201-xr-hands-animation-node.html
+++ b/docs/decisions/20231201-xr-hands-animation-node.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231203-graphsage-embedding-generation.html b/docs/decisions/20231203-graphsage-embedding-generation.html
index af2a72ac86..277272b759 100644
--- a/docs/decisions/20231203-graphsage-embedding-generation.html
+++ b/docs/decisions/20231203-graphsage-embedding-generation.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231203-mesh-rwkv-test-metrics.html b/docs/decisions/20231203-mesh-rwkv-test-metrics.html
index fd303cc64d..319582a93b 100644
--- a/docs/decisions/20231203-mesh-rwkv-test-metrics.html
+++ b/docs/decisions/20231203-mesh-rwkv-test-metrics.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231203-mesh-rwkv.html b/docs/decisions/20231203-mesh-rwkv.html
index 2c8628c0c2..13fded315b 100644
--- a/docs/decisions/20231203-mesh-rwkv.html
+++ b/docs/decisions/20231203-mesh-rwkv.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231209-appium-testing-fbx-to-gltf.html b/docs/decisions/20231209-appium-testing-fbx-to-gltf.html
index 1593bf41de..569d4a2522 100644
--- a/docs/decisions/20231209-appium-testing-fbx-to-gltf.html
+++ b/docs/decisions/20231209-appium-testing-fbx-to-gltf.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231209-appium-testing-win11.html b/docs/decisions/20231209-appium-testing-win11.html
index c5a0ced4d0..03a9c70b7f 100644
--- a/docs/decisions/20231209-appium-testing-win11.html
+++ b/docs/decisions/20231209-appium-testing-win11.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231218-mtlx-try-two.html b/docs/decisions/20231218-mtlx-try-two.html
index 86383cd0da..b57525a291 100644
--- a/docs/decisions/20231218-mtlx-try-two.html
+++ b/docs/decisions/20231218-mtlx-try-two.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231225-mesh-transformer-clothing.html b/docs/decisions/20231225-mesh-transformer-clothing.html
index a45fd68776..9a9b67a700 100644
--- a/docs/decisions/20231225-mesh-transformer-clothing.html
+++ b/docs/decisions/20231225-mesh-transformer-clothing.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231225-mesh-transformer-facial-features.html b/docs/decisions/20231225-mesh-transformer-facial-features.html
index c9a9357756..c13692a364 100644
--- a/docs/decisions/20231225-mesh-transformer-facial-features.html
+++ b/docs/decisions/20231225-mesh-transformer-facial-features.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231226-furniture-vs-organic.html b/docs/decisions/20231226-furniture-vs-organic.html
index b67b60fa08..80c00f3824 100644
--- a/docs/decisions/20231226-furniture-vs-organic.html
+++ b/docs/decisions/20231226-furniture-vs-organic.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231227-blue-green-shadows.html b/docs/decisions/20231227-blue-green-shadows.html
index eff4bee366..87987e2934 100644
--- a/docs/decisions/20231227-blue-green-shadows.html
+++ b/docs/decisions/20231227-blue-green-shadows.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231227-punchline-reports.html b/docs/decisions/20231227-punchline-reports.html
index 30b20f96b9..c5d745b566 100644
--- a/docs/decisions/20231227-punchline-reports.html
+++ b/docs/decisions/20231227-punchline-reports.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231228-v-sekai-slogan.html b/docs/decisions/20231228-v-sekai-slogan.html
index 8b47e5e8b4..bd1cef0d1f 100644
--- a/docs/decisions/20231228-v-sekai-slogan.html
+++ b/docs/decisions/20231228-v-sekai-slogan.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231229-byobu.html b/docs/decisions/20231229-byobu.html
index 05684719e8..6f08e24fce 100644
--- a/docs/decisions/20231229-byobu.html
+++ b/docs/decisions/20231229-byobu.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231229-mRemoteNG.html b/docs/decisions/20231229-mRemoteNG.html
index 47f33fb75e..a3686fedae 100644
--- a/docs/decisions/20231229-mRemoteNG.html
+++ b/docs/decisions/20231229-mRemoteNG.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20231230-spatiallabs-openvr.html b/docs/decisions/20231230-spatiallabs-openvr.html
index 1a159dd060..cb3acfcdcb 100644
--- a/docs/decisions/20231230-spatiallabs-openvr.html
+++ b/docs/decisions/20231230-spatiallabs-openvr.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240105-1-meter-128-quantize.html b/docs/decisions/20240105-1-meter-128-quantize.html
index f3d21da65e..9c4b0fd0b2 100644
--- a/docs/decisions/20240105-1-meter-128-quantize.html
+++ b/docs/decisions/20240105-1-meter-128-quantize.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240110-magical-girls-college-novel.html b/docs/decisions/20240110-magical-girls-college-novel.html
index 8503910915..5a65f7480a 100644
--- a/docs/decisions/20240110-magical-girls-college-novel.html
+++ b/docs/decisions/20240110-magical-girls-college-novel.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240111-fit-clothing-on-humans-without-tearing.html b/docs/decisions/20240111-fit-clothing-on-humans-without-tearing.html
index d25fabb582..79a26c2117 100644
--- a/docs/decisions/20240111-fit-clothing-on-humans-without-tearing.html
+++ b/docs/decisions/20240111-fit-clothing-on-humans-without-tearing.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240111-fspy.html b/docs/decisions/20240111-fspy.html
index 79e77a6436..a900752dcd 100644
--- a/docs/decisions/20240111-fspy.html
+++ b/docs/decisions/20240111-fspy.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240117-pivot-painting.html b/docs/decisions/20240117-pivot-painting.html
index 6e98b0f06c..d0c7c77b47 100644
--- a/docs/decisions/20240117-pivot-painting.html
+++ b/docs/decisions/20240117-pivot-painting.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240120-vr-armature-system.html b/docs/decisions/20240120-vr-armature-system.html
index 686243cf45..3b52d63df7 100644
--- a/docs/decisions/20240120-vr-armature-system.html
+++ b/docs/decisions/20240120-vr-armature-system.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240121-easy-diffusion-fedora-install.html b/docs/decisions/20240121-easy-diffusion-fedora-install.html
index 0adbbb856c..31cf5840ae 100644
--- a/docs/decisions/20240121-easy-diffusion-fedora-install.html
+++ b/docs/decisions/20240121-easy-diffusion-fedora-install.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240121-install-tailscale.html b/docs/decisions/20240121-install-tailscale.html
index 03f9636102..d2f4fdf01b 100644
--- a/docs/decisions/20240121-install-tailscale.html
+++ b/docs/decisions/20240121-install-tailscale.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240121-livebook-fedora-install.html b/docs/decisions/20240121-livebook-fedora-install.html
index 11ed58b66d..b2d208a4d1 100644
--- a/docs/decisions/20240121-livebook-fedora-install.html
+++ b/docs/decisions/20240121-livebook-fedora-install.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240121-mac-setup.html b/docs/decisions/20240121-mac-setup.html
index 43a6c33b0c..e2e102b513 100644
--- a/docs/decisions/20240121-mac-setup.html
+++ b/docs/decisions/20240121-mac-setup.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240127-urban-explorer-gdc-2024-sample.html b/docs/decisions/20240127-urban-explorer-gdc-2024-sample.html
index 25f658321a..b933a3fb72 100644
--- a/docs/decisions/20240127-urban-explorer-gdc-2024-sample.html
+++ b/docs/decisions/20240127-urban-explorer-gdc-2024-sample.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240215-avatar-customization-with-ai-facial-expressions.html b/docs/decisions/20240215-avatar-customization-with-ai-facial-expressions.html
index 93f87b63b3..6e49d5d692 100644
--- a/docs/decisions/20240215-avatar-customization-with-ai-facial-expressions.html
+++ b/docs/decisions/20240215-avatar-customization-with-ai-facial-expressions.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240217-container-2-wasm.html b/docs/decisions/20240217-container-2-wasm.html
index bcf0a658af..a2b942ecfd 100644
--- a/docs/decisions/20240217-container-2-wasm.html
+++ b/docs/decisions/20240217-container-2-wasm.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240217-documentation-guidelines.html b/docs/decisions/20240217-documentation-guidelines.html
index 0ece1775a1..bf22fd9adb 100644
--- a/docs/decisions/20240217-documentation-guidelines.html
+++ b/docs/decisions/20240217-documentation-guidelines.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240217-essential-typle-normalization-form.html b/docs/decisions/20240217-essential-typle-normalization-form.html
index a85a624e36..0720dda121 100644
--- a/docs/decisions/20240217-essential-typle-normalization-form.html
+++ b/docs/decisions/20240217-essential-typle-normalization-form.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240217-intended-effort-versioning.html b/docs/decisions/20240217-intended-effort-versioning.html
index ebb2839ed8..d2d8696492 100644
--- a/docs/decisions/20240217-intended-effort-versioning.html
+++ b/docs/decisions/20240217-intended-effort-versioning.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240217-workload-benchmarking.html b/docs/decisions/20240217-workload-benchmarking.html
index 8c20dcd90b..25650565f8 100644
--- a/docs/decisions/20240217-workload-benchmarking.html
+++ b/docs/decisions/20240217-workload-benchmarking.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240218-blender-to-godot.html b/docs/decisions/20240218-blender-to-godot.html
index b72ced934e..ffdfa73636 100644
--- a/docs/decisions/20240218-blender-to-godot.html
+++ b/docs/decisions/20240218-blender-to-godot.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240218-vrm-acronym-correction.html b/docs/decisions/20240218-vrm-acronym-correction.html
index 6e12d076f7..a3a953ad6e 100644
--- a/docs/decisions/20240218-vrm-acronym-correction.html
+++ b/docs/decisions/20240218-vrm-acronym-correction.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240218-vrm-substance-editor.html b/docs/decisions/20240218-vrm-substance-editor.html
index c3dda57c2e..b8a16b88aa 100644
--- a/docs/decisions/20240218-vrm-substance-editor.html
+++ b/docs/decisions/20240218-vrm-substance-editor.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240305-v-sekai-launcher.html b/docs/decisions/20240305-v-sekai-launcher.html
index 1db8f7f8d7..a0c145b4b9 100644
--- a/docs/decisions/20240305-v-sekai-launcher.html
+++ b/docs/decisions/20240305-v-sekai-launcher.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240307-rabbitmq-ra.html b/docs/decisions/20240307-rabbitmq-ra.html
index d8420355e3..dcce15f85d 100644
--- a/docs/decisions/20240307-rabbitmq-ra.html
+++ b/docs/decisions/20240307-rabbitmq-ra.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240314-live-collab.html b/docs/decisions/20240314-live-collab.html
index 870fb51843..27c42e871c 100644
--- a/docs/decisions/20240314-live-collab.html
+++ b/docs/decisions/20240314-live-collab.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240324-v-sekai-as-slc.html b/docs/decisions/20240324-v-sekai-as-slc.html
index 3a4af4e5d8..809fecc70b 100644
--- a/docs/decisions/20240324-v-sekai-as-slc.html
+++ b/docs/decisions/20240324-v-sekai-as-slc.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240325-fdb-sqlite-blender-godot.html b/docs/decisions/20240325-fdb-sqlite-blender-godot.html
index 9e78fd009b..a005ff5b99 100644
--- a/docs/decisions/20240325-fdb-sqlite-blender-godot.html
+++ b/docs/decisions/20240325-fdb-sqlite-blender-godot.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240325-table-avatar-embedded-xmp.html b/docs/decisions/20240325-table-avatar-embedded-xmp.html
index fc9271a488..1bc165ca83 100644
--- a/docs/decisions/20240325-table-avatar-embedded-xmp.html
+++ b/docs/decisions/20240325-table-avatar-embedded-xmp.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240326-heartstrings-vr.html b/docs/decisions/20240326-heartstrings-vr.html
index ae6c693263..4b9d72fcd2 100644
--- a/docs/decisions/20240326-heartstrings-vr.html
+++ b/docs/decisions/20240326-heartstrings-vr.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240326-verifying-and-finetuning-plans.html b/docs/decisions/20240326-verifying-and-finetuning-plans.html
index 28ce8b4617..c3ce0d20ee 100644
--- a/docs/decisions/20240326-verifying-and-finetuning-plans.html
+++ b/docs/decisions/20240326-verifying-and-finetuning-plans.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240329-ready-to-go-kit-windows-11.html b/docs/decisions/20240329-ready-to-go-kit-windows-11.html
index be6b964570..3eac3366a7 100644
--- a/docs/decisions/20240329-ready-to-go-kit-windows-11.html
+++ b/docs/decisions/20240329-ready-to-go-kit-windows-11.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240330-bitnami-rancher-helm-catalog.html b/docs/decisions/20240330-bitnami-rancher-helm-catalog.html
index a4bed2e89c..a0cec67b0b 100644
--- a/docs/decisions/20240330-bitnami-rancher-helm-catalog.html
+++ b/docs/decisions/20240330-bitnami-rancher-helm-catalog.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240330-cicd-gitlab.html b/docs/decisions/20240330-cicd-gitlab.html
index fecce219a0..25005566db 100644
--- a/docs/decisions/20240330-cicd-gitlab.html
+++ b/docs/decisions/20240330-cicd-gitlab.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240330-gitlab-helm.html b/docs/decisions/20240330-gitlab-helm.html
index c9ef7a8ea5..9da43bef2a 100644
--- a/docs/decisions/20240330-gitlab-helm.html
+++ b/docs/decisions/20240330-gitlab-helm.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240330-hyperv-harvester-test.html b/docs/decisions/20240330-hyperv-harvester-test.html
index b108021c82..c30914534e 100644
--- a/docs/decisions/20240330-hyperv-harvester-test.html
+++ b/docs/decisions/20240330-hyperv-harvester-test.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240330-k8s-harvester-hci.html b/docs/decisions/20240330-k8s-harvester-hci.html
index f3c59fa686..c3d91bfdd9 100644
--- a/docs/decisions/20240330-k8s-harvester-hci.html
+++ b/docs/decisions/20240330-k8s-harvester-hci.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240331-vrc-vrm-compatibility.html b/docs/decisions/20240331-vrc-vrm-compatibility.html
index cce2344cc8..d98c2b9d7b 100644
--- a/docs/decisions/20240331-vrc-vrm-compatibility.html
+++ b/docs/decisions/20240331-vrc-vrm-compatibility.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240401-shader-graphic.html b/docs/decisions/20240401-shader-graphic.html
index 4337ab41c5..f519516df1 100644
--- a/docs/decisions/20240401-shader-graphic.html
+++ b/docs/decisions/20240401-shader-graphic.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240406-itch-github-actions.html b/docs/decisions/20240406-itch-github-actions.html
index c5d4563fa3..f6ca8283af 100644
--- a/docs/decisions/20240406-itch-github-actions.html
+++ b/docs/decisions/20240406-itch-github-actions.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240406-web-based-explore.html b/docs/decisions/20240406-web-based-explore.html
index 4960ea5778..80aef5384c 100644
--- a/docs/decisions/20240406-web-based-explore.html
+++ b/docs/decisions/20240406-web-based-explore.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240407-pcvr-vs-standalone.html b/docs/decisions/20240407-pcvr-vs-standalone.html
index 5826e8bc2e..879536c62e 100644
--- a/docs/decisions/20240407-pcvr-vs-standalone.html
+++ b/docs/decisions/20240407-pcvr-vs-standalone.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240409-crud-godot-tiles.html b/docs/decisions/20240409-crud-godot-tiles.html
index 2e494b89c5..fb8293d357 100644
--- a/docs/decisions/20240409-crud-godot-tiles.html
+++ b/docs/decisions/20240409-crud-godot-tiles.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240409-elixir-raft-vs-sqlite-fdb.html b/docs/decisions/20240409-elixir-raft-vs-sqlite-fdb.html
index dd341f8f9d..84a1f59a2a 100644
--- a/docs/decisions/20240409-elixir-raft-vs-sqlite-fdb.html
+++ b/docs/decisions/20240409-elixir-raft-vs-sqlite-fdb.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240410-data-storage-elixir.html b/docs/decisions/20240410-data-storage-elixir.html
index fa8846fa81..719fef9bcc 100644
--- a/docs/decisions/20240410-data-storage-elixir.html
+++ b/docs/decisions/20240410-data-storage-elixir.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240411-elixir-libgodot-bundlex.html b/docs/decisions/20240411-elixir-libgodot-bundlex.html
index 2d23a2f9f9..4aa79278fa 100644
--- a/docs/decisions/20240411-elixir-libgodot-bundlex.html
+++ b/docs/decisions/20240411-elixir-libgodot-bundlex.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240411-elixir-libgodot-zig.html b/docs/decisions/20240411-elixir-libgodot-zig.html
index c09e0b01d0..1989a7c50b 100644
--- a/docs/decisions/20240411-elixir-libgodot-zig.html
+++ b/docs/decisions/20240411-elixir-libgodot-zig.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240411-multiplayer-movement-with-parented-obejcts.html b/docs/decisions/20240411-multiplayer-movement-with-parented-obejcts.html
index 77e1d33128..3620d65db4 100644
--- a/docs/decisions/20240411-multiplayer-movement-with-parented-obejcts.html
+++ b/docs/decisions/20240411-multiplayer-movement-with-parented-obejcts.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240413-calling-opensource-llm-with-aria.html b/docs/decisions/20240413-calling-opensource-llm-with-aria.html
index a4d241e190..9970459a3c 100644
--- a/docs/decisions/20240413-calling-opensource-llm-with-aria.html
+++ b/docs/decisions/20240413-calling-opensource-llm-with-aria.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html b/docs/decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html
index e3a4613c44..bb747f17dc 100644
--- a/docs/decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html
+++ b/docs/decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240416-previewer-upload-gltf-to-glb.html b/docs/decisions/20240416-previewer-upload-gltf-to-glb.html
index 11163e3c30..e8fc3e74a5 100644
--- a/docs/decisions/20240416-previewer-upload-gltf-to-glb.html
+++ b/docs/decisions/20240416-previewer-upload-gltf-to-glb.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240418-college-quest.html b/docs/decisions/20240418-college-quest.html
index 3e4e6da85d..3a4f972cab 100644
--- a/docs/decisions/20240418-college-quest.html
+++ b/docs/decisions/20240418-college-quest.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240423-building-metaverse-with-glue-mechanic.html b/docs/decisions/20240423-building-metaverse-with-glue-mechanic.html
index e66f130f48..a70b1b3217 100644
--- a/docs/decisions/20240423-building-metaverse-with-glue-mechanic.html
+++ b/docs/decisions/20240423-building-metaverse-with-glue-mechanic.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240424-reset-steamvr-controllers.html b/docs/decisions/20240424-reset-steamvr-controllers.html
index 9c54447bc1..5c09bda65a 100644
--- a/docs/decisions/20240424-reset-steamvr-controllers.html
+++ b/docs/decisions/20240424-reset-steamvr-controllers.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240425-proposal-prompt-system.html b/docs/decisions/20240425-proposal-prompt-system.html
index 7333e78e3a..413fadaa50 100644
--- a/docs/decisions/20240425-proposal-prompt-system.html
+++ b/docs/decisions/20240425-proposal-prompt-system.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240425-recharge-cycle.html b/docs/decisions/20240425-recharge-cycle.html
index 6e3635ea8c..d9f1827998 100644
--- a/docs/decisions/20240425-recharge-cycle.html
+++ b/docs/decisions/20240425-recharge-cycle.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240502-gltf-fbx-tscn-vrm.html b/docs/decisions/20240502-gltf-fbx-tscn-vrm.html
index 925b7bb5d2..89fe775972 100644
--- a/docs/decisions/20240502-gltf-fbx-tscn-vrm.html
+++ b/docs/decisions/20240502-gltf-fbx-tscn-vrm.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240502-install-windows-on-older-computers.html b/docs/decisions/20240502-install-windows-on-older-computers.html
index fb3d11d197..1fe66fac17 100644
--- a/docs/decisions/20240502-install-windows-on-older-computers.html
+++ b/docs/decisions/20240502-install-windows-on-older-computers.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240502-membrane-framework-identity-post.html b/docs/decisions/20240502-membrane-framework-identity-post.html
index 0eb002a63d..21ff3f1724 100644
--- a/docs/decisions/20240502-membrane-framework-identity-post.html
+++ b/docs/decisions/20240502-membrane-framework-identity-post.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240502-mesh-object-sync-benchmark.html b/docs/decisions/20240502-mesh-object-sync-benchmark.html
index 67fe31816e..bc1e1a8fdf 100644
--- a/docs/decisions/20240502-mesh-object-sync-benchmark.html
+++ b/docs/decisions/20240502-mesh-object-sync-benchmark.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240502-mvsqlite-launchd.html b/docs/decisions/20240502-mvsqlite-launchd.html
index a3e1ce1c57..8da9bffb13 100644
--- a/docs/decisions/20240502-mvsqlite-launchd.html
+++ b/docs/decisions/20240502-mvsqlite-launchd.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240502-where-can-I-use-gltf.html b/docs/decisions/20240502-where-can-I-use-gltf.html
index e9b8564a3a..4c8bb2a723 100644
--- a/docs/decisions/20240502-where-can-I-use-gltf.html
+++ b/docs/decisions/20240502-where-can-I-use-gltf.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240511-review-80-vr.html b/docs/decisions/20240511-review-80-vr.html
index b1e0fda8bc..9146a2ac3f 100644
--- a/docs/decisions/20240511-review-80-vr.html
+++ b/docs/decisions/20240511-review-80-vr.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240511-wasm-cache-incident.html b/docs/decisions/20240511-wasm-cache-incident.html
index d69e8e8948..b423a221ff 100644
--- a/docs/decisions/20240511-wasm-cache-incident.html
+++ b/docs/decisions/20240511-wasm-cache-incident.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240522-discord-bot.html b/docs/decisions/20240522-discord-bot.html
index 1fb9052162..7ef7c7928d 100644
--- a/docs/decisions/20240522-discord-bot.html
+++ b/docs/decisions/20240522-discord-bot.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240522-discord-inworld-portal.html b/docs/decisions/20240522-discord-inworld-portal.html
index 13c1554873..1f753477a2 100644
--- a/docs/decisions/20240522-discord-inworld-portal.html
+++ b/docs/decisions/20240522-discord-inworld-portal.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240522-shader-motion-to-bvh.html b/docs/decisions/20240522-shader-motion-to-bvh.html
index 28f40ef2a0..e2d0343c0c 100644
--- a/docs/decisions/20240522-shader-motion-to-bvh.html
+++ b/docs/decisions/20240522-shader-motion-to-bvh.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240522-webrtc-relay-test.html b/docs/decisions/20240522-webrtc-relay-test.html
index d3ea39aa68..9b2fb9137a 100644
--- a/docs/decisions/20240522-webrtc-relay-test.html
+++ b/docs/decisions/20240522-webrtc-relay-test.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240528-pipeline-godot-wasm-importer.html b/docs/decisions/20240528-pipeline-godot-wasm-importer.html
index c120914b66..c3bdf2e93c 100644
--- a/docs/decisions/20240528-pipeline-godot-wasm-importer.html
+++ b/docs/decisions/20240528-pipeline-godot-wasm-importer.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240529-improve-godot-import-ecosystem.html b/docs/decisions/20240529-improve-godot-import-ecosystem.html
index 66c5c73924..5e93302720 100644
--- a/docs/decisions/20240529-improve-godot-import-ecosystem.html
+++ b/docs/decisions/20240529-improve-godot-import-ecosystem.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html b/docs/decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html
index 988651beba..bca2d412eb 100644
--- a/docs/decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html
+++ b/docs/decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html b/docs/decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html
index f6fe60c8f9..5bca6d9675 100644
--- a/docs/decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html
+++ b/docs/decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240608-skin-weight-transfer-skeleton-merge.html b/docs/decisions/20240608-skin-weight-transfer-skeleton-merge.html
index cbdb4e94b1..93171fb417 100644
--- a/docs/decisions/20240608-skin-weight-transfer-skeleton-merge.html
+++ b/docs/decisions/20240608-skin-weight-transfer-skeleton-merge.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240611-lower-learning-rate.html b/docs/decisions/20240611-lower-learning-rate.html
index 1d016ac331..bd83a090ab 100644
--- a/docs/decisions/20240611-lower-learning-rate.html
+++ b/docs/decisions/20240611-lower-learning-rate.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240611-test-1x-and-4x.html b/docs/decisions/20240611-test-1x-and-4x.html
index 0082f1f6c1..02d7ee278a 100644
--- a/docs/decisions/20240611-test-1x-and-4x.html
+++ b/docs/decisions/20240611-test-1x-and-4x.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240613-1k-quad-limit.html b/docs/decisions/20240613-1k-quad-limit.html
index dbce581d22..03242856c9 100644
--- a/docs/decisions/20240613-1k-quad-limit.html
+++ b/docs/decisions/20240613-1k-quad-limit.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240613-modifying-the-mesh-transformer-for-quads.html b/docs/decisions/20240613-modifying-the-mesh-transformer-for-quads.html
index 78bcf04d29..84c89ae216 100644
--- a/docs/decisions/20240613-modifying-the-mesh-transformer-for-quads.html
+++ b/docs/decisions/20240613-modifying-the-mesh-transformer-for-quads.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240613-training-dataset-creation-with-csg.html b/docs/decisions/20240613-training-dataset-creation-with-csg.html
index 446c64ba76..1dd7ef2a2b 100644
--- a/docs/decisions/20240613-training-dataset-creation-with-csg.html
+++ b/docs/decisions/20240613-training-dataset-creation-with-csg.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240613-training-dataset.html b/docs/decisions/20240613-training-dataset.html
index 2f951f748e..d88603fb2d 100644
--- a/docs/decisions/20240613-training-dataset.html
+++ b/docs/decisions/20240613-training-dataset.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240615-what-is-mesh-transformers.html b/docs/decisions/20240615-what-is-mesh-transformers.html
index a3115113dd..f333ee6a63 100644
--- a/docs/decisions/20240615-what-is-mesh-transformers.html
+++ b/docs/decisions/20240615-what-is-mesh-transformers.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240616-request-for-quad-mesh-dataset.html b/docs/decisions/20240616-request-for-quad-mesh-dataset.html
index ac2aa2f5e3..c6a76a3361 100644
--- a/docs/decisions/20240616-request-for-quad-mesh-dataset.html
+++ b/docs/decisions/20240616-request-for-quad-mesh-dataset.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240618-4-player-test-vsekai.html b/docs/decisions/20240618-4-player-test-vsekai.html
index 1cd1a2116e..8a69208450 100644
--- a/docs/decisions/20240618-4-player-test-vsekai.html
+++ b/docs/decisions/20240618-4-player-test-vsekai.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240618-schedule-as-binary-tree.html b/docs/decisions/20240618-schedule-as-binary-tree.html
index 8192af6b17..f40d4a5d6d 100644
--- a/docs/decisions/20240618-schedule-as-binary-tree.html
+++ b/docs/decisions/20240618-schedule-as-binary-tree.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240621-caption-photos-for-cicd.html b/docs/decisions/20240621-caption-photos-for-cicd.html
index 9ebce5e8d1..1c160a8c46 100644
--- a/docs/decisions/20240621-caption-photos-for-cicd.html
+++ b/docs/decisions/20240621-caption-photos-for-cicd.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240621-proposal-template copy.html b/docs/decisions/20240621-proposal-template copy.html
index 5b0d33f2be..27126abad1 100644
--- a/docs/decisions/20240621-proposal-template copy.html	
+++ b/docs/decisions/20240621-proposal-template copy.html	
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240622-build-for-many-platforms.html b/docs/decisions/20240622-build-for-many-platforms.html
index d6f244a549..28ebc4fb5c 100644
--- a/docs/decisions/20240622-build-for-many-platforms.html
+++ b/docs/decisions/20240622-build-for-many-platforms.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240622-gocd-agent-docker-image-update.html b/docs/decisions/20240622-gocd-agent-docker-image-update.html
index fc212f860d..67af8e24f4 100644
--- a/docs/decisions/20240622-gocd-agent-docker-image-update.html
+++ b/docs/decisions/20240622-gocd-agent-docker-image-update.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240622-process-for-testing-vsekai.html b/docs/decisions/20240622-process-for-testing-vsekai.html
index a1567685c6..c3e7edc66f 100644
--- a/docs/decisions/20240622-process-for-testing-vsekai.html
+++ b/docs/decisions/20240622-process-for-testing-vsekai.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240623-do-cdn-for-launcher.html b/docs/decisions/20240623-do-cdn-for-launcher.html
index 4dd43d1b1b..2b0d1c21e9 100644
--- a/docs/decisions/20240623-do-cdn-for-launcher.html
+++ b/docs/decisions/20240623-do-cdn-for-launcher.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240623-only-save-tools-in-our-cdn.html b/docs/decisions/20240623-only-save-tools-in-our-cdn.html
index f7254b925f..517e6f9887 100644
--- a/docs/decisions/20240623-only-save-tools-in-our-cdn.html
+++ b/docs/decisions/20240623-only-save-tools-in-our-cdn.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240623-talk-length-prototypes.html b/docs/decisions/20240623-talk-length-prototypes.html
index 68ac17d98c..0f7542cdb8 100644
--- a/docs/decisions/20240623-talk-length-prototypes.html
+++ b/docs/decisions/20240623-talk-length-prototypes.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240623-what-is-uro-backend.html b/docs/decisions/20240623-what-is-uro-backend.html
index 14dff52d35..ef9148bd15 100644
--- a/docs/decisions/20240623-what-is-uro-backend.html
+++ b/docs/decisions/20240623-what-is-uro-backend.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240626-update-python3-macos-certicates.html b/docs/decisions/20240626-update-python3-macos-certicates.html
index e1d3388cf0..dea9901a9c 100644
--- a/docs/decisions/20240626-update-python3-macos-certicates.html
+++ b/docs/decisions/20240626-update-python3-macos-certicates.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240627-every-commit-push-pass-cicd.html b/docs/decisions/20240627-every-commit-push-pass-cicd.html
index 2bdef22c80..d37166225b 100644
--- a/docs/decisions/20240627-every-commit-push-pass-cicd.html
+++ b/docs/decisions/20240627-every-commit-push-pass-cicd.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240627-gdextension-as-libriscv.html b/docs/decisions/20240627-gdextension-as-libriscv.html
index a5a1ca6d53..35862d9ed1 100644
--- a/docs/decisions/20240627-gdextension-as-libriscv.html
+++ b/docs/decisions/20240627-gdextension-as-libriscv.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240630-use-motion-transformers-for-prediction.html b/docs/decisions/20240630-use-motion-transformers-for-prediction.html
index d850a9a20c..5fc2e9f22f 100644
--- a/docs/decisions/20240630-use-motion-transformers-for-prediction.html
+++ b/docs/decisions/20240630-use-motion-transformers-for-prediction.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240705-rpg_town.html b/docs/decisions/20240705-rpg_town.html
index 47146c94ec..f5192eb980 100644
--- a/docs/decisions/20240705-rpg_town.html
+++ b/docs/decisions/20240705-rpg_town.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240706-motion-capture-bill-of-materials.html b/docs/decisions/20240706-motion-capture-bill-of-materials.html
index d97998a928..0bab3563ab 100644
--- a/docs/decisions/20240706-motion-capture-bill-of-materials.html
+++ b/docs/decisions/20240706-motion-capture-bill-of-materials.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240708-vsekai-my-life-as-a-queen.html b/docs/decisions/20240708-vsekai-my-life-as-a-queen.html
index ca2bdd3572..d92d840f12 100644
--- a/docs/decisions/20240708-vsekai-my-life-as-a-queen.html
+++ b/docs/decisions/20240708-vsekai-my-life-as-a-queen.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240709-anwave-set-nvidia-watt-limit.html b/docs/decisions/20240709-anwave-set-nvidia-watt-limit.html
index 2ba2a9dc97..7bee55594b 100644
--- a/docs/decisions/20240709-anwave-set-nvidia-watt-limit.html
+++ b/docs/decisions/20240709-anwave-set-nvidia-watt-limit.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240709-wired-first.html b/docs/decisions/20240709-wired-first.html
index 59f0f1f592..01d8ef66ae 100644
--- a/docs/decisions/20240709-wired-first.html
+++ b/docs/decisions/20240709-wired-first.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240710-art-direction-in-vsekai.html b/docs/decisions/20240710-art-direction-in-vsekai.html
index fac9c71543..a38f332c0d 100644
--- a/docs/decisions/20240710-art-direction-in-vsekai.html
+++ b/docs/decisions/20240710-art-direction-in-vsekai.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html b/docs/decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html
index f9644da6fe..b22c094fbd 100644
--- a/docs/decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html
+++ b/docs/decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240710-platform-focus-on-pcvr-and-web.html b/docs/decisions/20240710-platform-focus-on-pcvr-and-web.html
index ee35eeaa54..5210a60b0b 100644
--- a/docs/decisions/20240710-platform-focus-on-pcvr-and-web.html
+++ b/docs/decisions/20240710-platform-focus-on-pcvr-and-web.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240710-use-godot-engine-web-threaded.html b/docs/decisions/20240710-use-godot-engine-web-threaded.html
index ce1d408076..a47a4b992c 100644
--- a/docs/decisions/20240710-use-godot-engine-web-threaded.html
+++ b/docs/decisions/20240710-use-godot-engine-web-threaded.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240710-use-webrtc-to-native-interop.html b/docs/decisions/20240710-use-webrtc-to-native-interop.html
index a1bf9c432c..75ee89fc3c 100644
--- a/docs/decisions/20240710-use-webrtc-to-native-interop.html
+++ b/docs/decisions/20240710-use-webrtc-to-native-interop.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240710-web-and-pcvr-networking.html b/docs/decisions/20240710-web-and-pcvr-networking.html
index 76446f80ad..e76b1f6a0d 100644
--- a/docs/decisions/20240710-web-and-pcvr-networking.html
+++ b/docs/decisions/20240710-web-and-pcvr-networking.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html b/docs/decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html
index 953ad9ff56..9936d56c7f 100644
--- a/docs/decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html
+++ b/docs/decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240715-vrchat-networking-mental-model.html b/docs/decisions/20240715-vrchat-networking-mental-model.html
index 6244bb1695..0ba80d7a1c 100644
--- a/docs/decisions/20240715-vrchat-networking-mental-model.html
+++ b/docs/decisions/20240715-vrchat-networking-mental-model.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240717-core-vsekai-scripting.html b/docs/decisions/20240717-core-vsekai-scripting.html
index 9bf4da1b9a..26cebaad03 100644
--- a/docs/decisions/20240717-core-vsekai-scripting.html
+++ b/docs/decisions/20240717-core-vsekai-scripting.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240810-steamvr-dongles-separate.html b/docs/decisions/20240810-steamvr-dongles-separate.html
index 273dd21a9f..4734a78928 100644
--- a/docs/decisions/20240810-steamvr-dongles-separate.html
+++ b/docs/decisions/20240810-steamvr-dongles-separate.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240824-ffmpeg-wav-mic-speaker-play.html b/docs/decisions/20240824-ffmpeg-wav-mic-speaker-play.html
index 0416422c9a..99a910e90b 100644
--- a/docs/decisions/20240824-ffmpeg-wav-mic-speaker-play.html
+++ b/docs/decisions/20240824-ffmpeg-wav-mic-speaker-play.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html b/docs/decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html
index e5b5686644..da62c4414b 100644
--- a/docs/decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html
+++ b/docs/decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240830-use-dokku-to-host-vsk-backend.html b/docs/decisions/20240830-use-dokku-to-host-vsk-backend.html
index e8f2e8d15e..ef9ff213ed 100644
--- a/docs/decisions/20240830-use-dokku-to-host-vsk-backend.html
+++ b/docs/decisions/20240830-use-dokku-to-host-vsk-backend.html
@@ -135,7 +135,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240905-revised-tracker-configuration-and-constraints.html b/docs/decisions/20240905-revised-tracker-configuration-and-constraints.html
index 8c3451ae5e..681bb2c9e1 100644
--- a/docs/decisions/20240905-revised-tracker-configuration-and-constraints.html
+++ b/docs/decisions/20240905-revised-tracker-configuration-and-constraints.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20240914-godot-engine-xr-elite-conference-setup.html b/docs/decisions/20240914-godot-engine-xr-elite-conference-setup.html
index dcaef7b25a..d7f5370fcf 100644
--- a/docs/decisions/20240914-godot-engine-xr-elite-conference-setup.html
+++ b/docs/decisions/20240914-godot-engine-xr-elite-conference-setup.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20241001-small-game-tools.html b/docs/decisions/20241001-small-game-tools.html
index 2d29b519fb..e99864d6be 100644
--- a/docs/decisions/20241001-small-game-tools.html
+++ b/docs/decisions/20241001-small-game-tools.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20241006-restore-onedrive-shortcut-overrides.html b/docs/decisions/20241006-restore-onedrive-shortcut-overrides.html
index ea51cef29c..ca69bb735e 100644
--- a/docs/decisions/20241006-restore-onedrive-shortcut-overrides.html
+++ b/docs/decisions/20241006-restore-onedrive-shortcut-overrides.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20241011-recovering-makehuman-parameters.html b/docs/decisions/20241011-recovering-makehuman-parameters.html
index f46220566f..a6e40a610b 100644
--- a/docs/decisions/20241011-recovering-makehuman-parameters.html
+++ b/docs/decisions/20241011-recovering-makehuman-parameters.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20241014-app-updater.html b/docs/decisions/20241014-app-updater.html
index 5f1c9164d1..4ae3dc9e33 100644
--- a/docs/decisions/20241014-app-updater.html
+++ b/docs/decisions/20241014-app-updater.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20241014-basic-realtime-interaction.html b/docs/decisions/20241014-basic-realtime-interaction.html
index f7dcd157dd..682f584e54 100644
--- a/docs/decisions/20241014-basic-realtime-interaction.html
+++ b/docs/decisions/20241014-basic-realtime-interaction.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20241014-xr-interface-for-rigging.html b/docs/decisions/20241014-xr-interface-for-rigging.html
index 5629adb4b7..288e273133 100644
--- a/docs/decisions/20241014-xr-interface-for-rigging.html
+++ b/docs/decisions/20241014-xr-interface-for-rigging.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20241016-instantiating-v-sekai-content.html b/docs/decisions/20241016-instantiating-v-sekai-content.html
index 9aa7f83442..9155b3570f 100644
--- a/docs/decisions/20241016-instantiating-v-sekai-content.html
+++ b/docs/decisions/20241016-instantiating-v-sekai-content.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html b/docs/decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html
index f302e2f7ef..1b5e3fb9bb 100644
--- a/docs/decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html
+++ b/docs/decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/20241028-use-data-tables-for-godot-constraints.html b/docs/decisions/20241028-use-data-tables-for-godot-constraints.html
index 61a5fa409c..b40d8a46be 100644
--- a/docs/decisions/20241028-use-data-tables-for-godot-constraints.html
+++ b/docs/decisions/20241028-use-data-tables-for-godot-constraints.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/ai-assisted-proposal-style-guide.html b/docs/decisions/ai-assisted-proposal-style-guide.html
index f8992b21c2..69d2fdeae3 100644
--- a/docs/decisions/ai-assisted-proposal-style-guide.html
+++ b/docs/decisions/ai-assisted-proposal-style-guide.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/attachments/pitch_apple_vision_01.html b/docs/decisions/attachments/pitch_apple_vision_01.html
index 0b78aece3c..b97318e31a 100644
--- a/docs/decisions/attachments/pitch_apple_vision_01.html
+++ b/docs/decisions/attachments/pitch_apple_vision_01.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/attachments/pitch_general_02.html b/docs/decisions/attachments/pitch_general_02.html
index 53afb17ec0..8e2a101232 100644
--- a/docs/decisions/attachments/pitch_general_02.html
+++ b/docs/decisions/attachments/pitch_general_02.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/attachments/project_mirage.html b/docs/decisions/attachments/project_mirage.html
index be5c95bac6..e06698ff36 100644
--- a/docs/decisions/attachments/project_mirage.html
+++ b/docs/decisions/attachments/project_mirage.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/attachments/thunderbolt_install_windows.html b/docs/decisions/attachments/thunderbolt_install_windows.html
index 342bd2055c..f71ebb1b69 100644
--- a/docs/decisions/attachments/thunderbolt_install_windows.html
+++ b/docs/decisions/attachments/thunderbolt_install_windows.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../plans.qmd"> 
+    <a class="nav-link" href="../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/attachments/virtual_pets/LICENSE.html b/docs/decisions/attachments/virtual_pets/LICENSE.html
index bd768a8ac8..61186255c1 100644
--- a/docs/decisions/attachments/virtual_pets/LICENSE.html
+++ b/docs/decisions/attachments/virtual_pets/LICENSE.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../../../plans.qmd"> 
+    <a class="nav-link" href="../../../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/decisions/present-proposal-template.html b/docs/decisions/present-proposal-template.html
index 1727e122c4..d401252578 100644
--- a/docs/decisions/present-proposal-template.html
+++ b/docs/decisions/present-proposal-template.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="../plans.qmd"> 
+    <a class="nav-link" href="../plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/index.html b/docs/index.html
index 93d1f68cb7..955c956124 100644
--- a/docs/index.html
+++ b/docs/index.html
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="./plans.qmd"> 
+    <a class="nav-link" href="./plans.html"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
diff --git a/docs/plan.html b/docs/plans.html
similarity index 99%
rename from docs/plan.html
rename to docs/plans.html
index 2a507cc79d..10c1adc2fc 100644
--- a/docs/plan.html
+++ b/docs/plans.html
@@ -7,7 +7,7 @@
 <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes">
 
 
-<title>plan – V-Sekai - Manuals</title>
+<title>plans – V-Sekai - Manuals</title>
 <style>
 code{white-space: pre-wrap;}
 span.smallcaps{font-variant: small-caps;}
@@ -101,7 +101,7 @@
 <span class="menu-text">Decisions</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="./plans.qmd"> 
+    <a class="nav-link active" href="./plans.html" aria-current="page"> 
 <span class="menu-text">Plans</span></a>
   </li>  
 </ul>
@@ -724,7 +724,7 @@
     </div>   
     <div class="nav-footer-center">
       &nbsp;
-    <div class="toc-actions"><ul><li><a href="https://github.com/V-Sekai/manuals/edit/main/plan.qmd" class="toc-action"><i class="bi bi-github"></i>Edit this page</a></li></ul></div></div>
+    <div class="toc-actions"><ul><li><a href="https://github.com/V-Sekai/manuals/edit/main/plans.qmd" class="toc-action"><i class="bi bi-github"></i>Edit this page</a></li></ul></div></div>
     <div class="nav-footer-right">
       <ul class="footer-items list-unstyled">
     <li class="nav-item compact">
diff --git a/docs/search.json b/docs/search.json
index fc09d30ec9..9b8e2252f4 100644
--- a/docs/search.json
+++ b/docs/search.json
@@ -1,14486 +1,14402 @@
 [
   {
-    "objectID": "plan.html",
-    "href": "plan.html",
-    "title": "V-Sekai - Manuals",
+    "objectID": "changelog/2023/20230601-changelog.html",
+    "href": "changelog/2023/20230601-changelog.html",
+    "title": "V-Sekai Changelog - 2023-06",
     "section": "",
-    "text": "%% V-Sekai Social Virtual Reality Project\n\ngraph TD\n    %% Define tasks and dependencies based on your project\n\n    A[Restore old V-Sekai]\n    B[Game Telemetry System]\n    C[Integrate Motion Matching Techniques]\n    D[Implement Crash Reporting System and Performance Metrics]\n    E[Optimize Engine for Smooth Framerates]\n    F[Recruit Artist for Default Home Map]\n    G[Implement Account System, TOS, Privacy Policy]\n    H[Integration of Video Playback & Streaming]\n\n    A --&gt; C\n    C --&gt; D\n    D --&gt; E\n    A --&gt; F\n    A --&gt; G\n    A --&gt; H\n\n    %% Task styling\n    classDef taskInfo fill:#f9f,stroke:#333,stroke-width:2px;"
+    "text": "In June 2023, various developments and discussions took place in the Godot community, particularly within the V-Sekai project. Key highlights include updates to the godot-vrm repository, security improvements in the v-sekai-game repository, and progress on animation retargeting and PMX character structure. Additionally, a fix was implemented for Skeleton3D’s rest_dirty reset issue.\n\nFork created: aaronfranke/godot-vrm (01/06/2023)\nNew commits in V-Sekai/godot-vrm repository, including updates to load_at_runtime_scene for 4.x and adding files_dropped functionality (02/06/2023)\nPR 130 closed, bumping github/codeql-action from 2.3.5 to 2.3.6 in V-Sekai/v-sekai-game (02/06/2023)\nPR 129 closed, bumping actions/setup-dotnet from 3.1.0 to 3.2.0 in V-Sekai/v-sekai-game (02/06/2023)\nStepSecurity bot opened PR 131 to apply security best practices in V-Sekai/v-sekai-game (02/06/2023)\nNew commit in v-sekai-game:main to avoid the empty avatar crash (02/06/2023)\nNew commits in v-sekai-game:main, including changes to assert and early return print _error (02/06/2023)\nNew tag created in V-Sekai/godot: groups-4.x.2023-06-03T034215Z (02/06/2023)\nPR 131 closed, applying security best practices in V-Sekai/v-sekai-game (02/06/2023)\nNew commit in v-sekai-game:main to make joining a server less crashy (02/06/2023)\nNew commit in v-sekai-game:main to remove debug points (02/06/2023)\nNew branch created in V-Sekai/v-sekai-game: codeql (02/06/2023)\nPR 132 opened, creating codeql.yml in V-Sekai/v-sekai-game (02/06/2023)\nNew comment on issue #25 in V-Sekai/godot-vrm discussing how to make a VRM model pose using GDScript (02/06/2023)\nNew commits in v-sekai-game:main, including changes to assert and early return print _error part 3, avoiding runtime errors, and removing gut (02/06/2023 - 03/06/2023)\nPR 132 closed, creating codeql.yml in V-Sekai/v-sekai-game (03/06/2023)\nPR 133 opened, hardening GitHub Actions in V-Sekai/v-sekai-game (03/06/2023)\nNew comments on issue #25 in V-Sekai/godot-vrm discussing animation retargeting and PMX character structure (03/06/2023)\nNew commits in v-sekai-game:main, including removing hardcoded gravity and gravity direction, inverting state machine condition, and setting up work in progress state chart (03/06/2023)\nNew branch created in V-Sekai/v-sekai-game: state-chart (03/06/2023)\nSkeleton3D now correctly resets rest_dirty only after all bone transforms have been updated (PR 78025 by lyuma). This also resolves the SkeletonGizmo display issue when there is more than one bone root.\n\n\n\nThe team has introduced a feature that allows for easy setup with just a single click. Additionally, they’re now utilizing an advanced system known as the Many Bones’ solver.\n\n\n\nThere were some concerns about how much time the GPU was spending on processing the shader - think of the shader like a set of instructions telling the GPU how to draw each pixel. The frame times, or the speed at which frames are processed, seemed to be slower than expected. However, it was clarified that these tests were being run in a mode designed for finding errors (debug mode), not for optimal performance.\n\n\n\nThe team discussed how their system’s performance stacks up against other virtual reality social platforms. They used different types of hardware for these comparisons, similar to comparing the performance of different cars using various types of roads and conditions.\n\n\n\nThe team also talked about how to best optimize their system for different devices. This is akin to tuning a car’s engine differently depending on whether it’s going to be driven in the city or on a racetrack.\n\n\n\nThere were discussions about the challenges of rendering avatars, especially when there are multiple avatars on the screen at once. It’s like trying to paint multiple portraits at the same time - the more you have, the harder it gets. The team discussed the need for guidelines to help avatar creators optimize their designs for less powerful hardware.\n\n\n\nLooking ahead, the team plans to conduct more tests, particularly focusing on how well their system handles complex 3D models on Android devices. They also aim to create a benchmark scenario where they expect good performance across most platforms, much like setting a standard track to test different cars’ performances."
   },
   {
-    "objectID": "changelog/2023/20231001-changelog.html",
-    "href": "changelog/2023/20231001-changelog.html",
-    "title": "V-Sekai Changelog - October 2023",
+    "objectID": "changelog/2023/20230601-changelog.html#simplified-setup-and-advanced-solver-system",
+    "href": "changelog/2023/20230601-changelog.html#simplified-setup-and-advanced-solver-system",
+    "title": "V-Sekai Changelog - 2023-06",
     "section": "",
-    "text": "Lyuma has pushed support to GodotEngine Unidot-Importer for humanoid unity .anim import including lox9973’s center of mass correction for hips. #gamedev\nHumanoid anim support is complete, including arm/leg twist! Import of standalone Avatar assets is now functional (such as converted VRM files).\nUnpacked avatar prefabs are now extracted into their own scenes.\n\n\n\n\n\nUpdated casync for v-sekai-game. This is still using the old version binaries.\n\ngit clone https://github.com/V-Sekai/casync-v-sekai-game.git\ncd casync-v-sekai-game\n./extract.sh\n\n\n\n\nFixed an issue with GLTF images being referenced directly instead of going through the GLTFState.textures mapping. This was causing texture mis-matches on some VRMs when loaded. The fix involved passing the GLTF state into a few more functions, replacing the image list, so we could also access the textures mapping directly alongside them. (#82)\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\nThis project does not adhere to Semantic Versioning.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nConvinced PolygonJS to change their license to the MIT license.\nReviewed a character generator with OMI and JIN\nDiscussed svg in gltf at OMI\nProposed feature request to add an extractor to save 3d assets, gltf files, CAD files, shapefiles, STLs, etc to ArchiveBox. Issue #668\nDiscovered a method of json document sync. JsonJoy\n\n\n\n\n\n“The term logbook originated with the ship’s log, a maritime record of important events in the management, operation, and navigation of a ship. The captain was responsible for keeping a log, as a minimum, of navigational wind, speed, direction and position.” - Wikipedia"
+    "text": "The team has introduced a feature that allows for easy setup with just a single click. Additionally, they’re now utilizing an advanced system known as the Many Bones’ solver."
   },
   {
-    "objectID": "changelog/2023/20231001-changelog.html#unreleased",
-    "href": "changelog/2023/20231001-changelog.html#unreleased",
-    "title": "V-Sekai Changelog - October 2023",
+    "objectID": "changelog/2023/20230601-changelog.html#graphics-processing-unit-gpu-performance",
+    "href": "changelog/2023/20230601-changelog.html#graphics-processing-unit-gpu-performance",
+    "title": "V-Sekai Changelog - 2023-06",
     "section": "",
-    "text": "Lyuma has pushed support to GodotEngine Unidot-Importer for humanoid unity .anim import including lox9973’s center of mass correction for hips. #gamedev\nHumanoid anim support is complete, including arm/leg twist! Import of standalone Avatar assets is now functional (such as converted VRM files).\nUnpacked avatar prefabs are now extracted into their own scenes.\n\n\n\n\n\nUpdated casync for v-sekai-game. This is still using the old version binaries.\n\ngit clone https://github.com/V-Sekai/casync-v-sekai-game.git\ncd casync-v-sekai-game\n./extract.sh\n\n\n\n\nFixed an issue with GLTF images being referenced directly instead of going through the GLTFState.textures mapping. This was causing texture mis-matches on some VRMs when loaded. The fix involved passing the GLTF state into a few more functions, replacing the image list, so we could also access the textures mapping directly alongside them. (#82)\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\nThis project does not adhere to Semantic Versioning."
+    "text": "There were some concerns about how much time the GPU was spending on processing the shader - think of the shader like a set of instructions telling the GPU how to draw each pixel. The frame times, or the speed at which frames are processed, seemed to be slower than expected. However, it was clarified that these tests were being run in a mode designed for finding errors (debug mode), not for optimal performance."
   },
   {
-    "objectID": "changelog/2023/20231001-changelog.html#previous-releases",
-    "href": "changelog/2023/20231001-changelog.html#previous-releases",
-    "title": "V-Sekai Changelog - October 2023",
+    "objectID": "changelog/2023/20230601-changelog.html#comparing-performance-across-platforms",
+    "href": "changelog/2023/20230601-changelog.html#comparing-performance-across-platforms",
+    "title": "V-Sekai Changelog - 2023-06",
     "section": "",
-    "text": "Not applicable for this month."
+    "text": "The team discussed how their system’s performance stacks up against other virtual reality social platforms. They used different types of hardware for these comparisons, similar to comparing the performance of different cars using various types of roads and conditions."
   },
   {
-    "objectID": "changelog/2023/20231001-changelog.html#misc",
-    "href": "changelog/2023/20231001-changelog.html#misc",
-    "title": "V-Sekai Changelog - October 2023",
+    "objectID": "changelog/2023/20230601-changelog.html#tailoring-performance-for-different-devices",
+    "href": "changelog/2023/20230601-changelog.html#tailoring-performance-for-different-devices",
+    "title": "V-Sekai Changelog - 2023-06",
     "section": "",
-    "text": "Convinced PolygonJS to change their license to the MIT license.\nReviewed a character generator with OMI and JIN\nDiscussed svg in gltf at OMI\nProposed feature request to add an extractor to save 3d assets, gltf files, CAD files, shapefiles, STLs, etc to ArchiveBox. Issue #668\nDiscovered a method of json document sync. JsonJoy"
+    "text": "The team also talked about how to best optimize their system for different devices. This is akin to tuning a car’s engine differently depending on whether it’s going to be driven in the city or on a racetrack."
   },
   {
-    "objectID": "changelog/2023/20231001-changelog.html#quotes-of-the-month",
-    "href": "changelog/2023/20231001-changelog.html#quotes-of-the-month",
-    "title": "V-Sekai Changelog - October 2023",
+    "objectID": "changelog/2023/20230601-changelog.html#rendering-avatars",
+    "href": "changelog/2023/20230601-changelog.html#rendering-avatars",
+    "title": "V-Sekai Changelog - 2023-06",
     "section": "",
-    "text": "“The term logbook originated with the ship’s log, a maritime record of important events in the management, operation, and navigation of a ship. The captain was responsible for keeping a log, as a minimum, of navigational wind, speed, direction and position.” - Wikipedia"
+    "text": "There were discussions about the challenges of rendering avatars, especially when there are multiple avatars on the screen at once. It’s like trying to paint multiple portraits at the same time - the more you have, the harder it gets. The team discussed the need for guidelines to help avatar creators optimize their designs for less powerful hardware."
   },
   {
-    "objectID": "changelog/2023/20230201-changelog.html",
-    "href": "changelog/2023/20230201-changelog.html",
-    "title": "V-Sekai Changelog - 2023-02",
+    "objectID": "changelog/2023/20230601-changelog.html#future-plans",
+    "href": "changelog/2023/20230601-changelog.html#future-plans",
+    "title": "V-Sekai Changelog - 2023-06",
     "section": "",
-    "text": "This is the changelog for February 2023.\nThe sdk has the entire v-sekai-game project, all the builds and git .\nThe game builds can be smaller but they currently have the shared_library, the executable and the gdextension interface files. It also can launch v-sekai with openxr.\nThe builds are ranging to 10 minutes for a partially cached build on average. Engine builds take longer.\nhttps://nightly.link/V-Sekai/v-sekai-game/workflows/vsk_linux_builds/main\n\n\n\nSomeone wanted me to help out on voip so I assisted\nA v-tuber, expiredpopsicle, is using godot-vrm! and contributed.\nFaolan is a Godot contributor. Fire gifted libgodot code to him and now he’s able to run his vr platform on the Meta Quest with dotnet.\n\n\n\n\nI reduced iteration times on the V-Sekai cicd from 1.5 hours to 2-10 minutes.\nI also stopped merging incomplete work. Every merge commit should stand on its own."
+    "text": "Looking ahead, the team plans to conduct more tests, particularly focusing on how well their system handles complex 3D models on Android devices. They also aim to create a benchmark scenario where they expect good performance across most platforms, much like setting a standard track to test different cars’ performances."
   },
   {
-    "objectID": "changelog/2023/20230201-changelog.html#people",
-    "href": "changelog/2023/20230201-changelog.html#people",
-    "title": "V-Sekai Changelog - 2023-02",
+    "objectID": "changelog/2023/20230701-changelog.html",
+    "href": "changelog/2023/20230701-changelog.html",
+    "title": "V-Sekai Changelog - July 2023",
     "section": "",
-    "text": "Someone wanted me to help out on voip so I assisted\nA v-tuber, expiredpopsicle, is using godot-vrm! and contributed.\nFaolan is a Godot contributor. Fire gifted libgodot code to him and now he’s able to run his vr platform on the Meta Quest with dotnet."
+    "text": "VRM 1.0 export work by Lyuma.\nImplemented VRM 1 spring bones in the vrm1-wip branch by Lyuma.\nRefactored XML class definitions in all external vsk-modules by iFire.\nAdded “painfulness” to the many bone IK solver by iFire.\n\n\n\n\n\nPushed a bunch of the code for VRM 1 to godot-vrm by Lyuma.\nMore changes to vrm1-wip specifically changing how head hiding works by Lyuma.\nRestoring editor upload of avatars and worlds by iFire.\n\n\n\n\n\nPosted a fix for the magenta viewport copy of xr bug by iFire.\n\n\n\n\n\nVRM 0 models are upgraded to VRM 1 format during import, so only VRM 1 can be exported, and it will use VRM 1 style naming for everything by Lyuma.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\nThis project does not adheres to Semantic Versioning.\n\n\n\n\n\nNot applicable for this month.\n\nNote: This changelog has been compiled based on the updates provided. For more detailed information, please refer to the specific issues or pull requests in the respective repositories."
   },
   {
-    "objectID": "changelog/2023/20230201-changelog.html#fire",
-    "href": "changelog/2023/20230201-changelog.html#fire",
-    "title": "V-Sekai Changelog - 2023-02",
+    "objectID": "changelog/2023/20230701-changelog.html#unreleased",
+    "href": "changelog/2023/20230701-changelog.html#unreleased",
+    "title": "V-Sekai Changelog - July 2023",
     "section": "",
-    "text": "I reduced iteration times on the V-Sekai cicd from 1.5 hours to 2-10 minutes.\nI also stopped merging incomplete work. Every merge commit should stand on its own."
+    "text": "VRM 1.0 export work by Lyuma.\nImplemented VRM 1 spring bones in the vrm1-wip branch by Lyuma.\nRefactored XML class definitions in all external vsk-modules by iFire.\nAdded “painfulness” to the many bone IK solver by iFire.\n\n\n\n\n\nPushed a bunch of the code for VRM 1 to godot-vrm by Lyuma.\nMore changes to vrm1-wip specifically changing how head hiding works by Lyuma.\nRestoring editor upload of avatars and worlds by iFire.\n\n\n\n\n\nPosted a fix for the magenta viewport copy of xr bug by iFire.\n\n\n\n\n\nVRM 0 models are upgraded to VRM 1 format during import, so only VRM 1 can be exported, and it will use VRM 1 style naming for everything by Lyuma.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\nThis project does not adheres to Semantic Versioning."
   },
   {
-    "objectID": "changelog/2023/20230101-changelog.html",
-    "href": "changelog/2023/20230101-changelog.html",
-    "title": "V-Sekai Changelog - 2023-01",
+    "objectID": "changelog/2023/20230701-changelog.html#previous-releases",
+    "href": "changelog/2023/20230701-changelog.html#previous-releases",
+    "title": "V-Sekai Changelog - July 2023",
     "section": "",
-    "text": "V-Sekai Changelog - 2023-01\nThis is the changelog for January 2023."
+    "text": "Not applicable for this month.\n\nNote: This changelog has been compiled based on the updates provided. For more detailed information, please refer to the specific issues or pull requests in the respective repositories."
   },
   {
-    "objectID": "changelog/2023/20230501-changelog.html",
-    "href": "changelog/2023/20230501-changelog.html",
-    "title": "V-Sekai Changelog - 2023-05",
+    "objectID": "changelog/2023/20230301-changelog.html",
+    "href": "changelog/2023/20230301-changelog.html",
+    "title": "V-Sekai Changelog - 2023-03",
     "section": "",
-    "text": "In May 2023, significant progress was made in the Godot community and V-Sekai project. Key developments include the implementation of WebAssembly modules for Godot Engine 4, improvements to the V-Sekai Godot Engine fork, and advancements in Unidot’s FBX humanoid support. Additionally, there were updates to the manual site, suggestions for Blender VRM drag-and-drop support, and bug fixes related to LODs.\n\nhttps://github.com/ashtonmeuser/godot-wasm/tree/godot-4 Implements wasm modules for Godot Engine 4.\nFire has chatgpt4 api access.\nMerged godot-wasm into V-Sekai Godot Engine fork for experimenting with user generated scripting and optimization of computation.\nvsk_speech branch of V-Sekai Godot Engine passes cicd again!!\nRevised and optimized the manual site.\nSuggested that .VRM drag and drop support is added to Blender. https://github.com/mika-f/blender-drag-and-drop/issues/34#issuecomment-1539429579\nUse a better representation of feminine and masculine avatars\nFixing bugs with lods\n\n\n\nLyuma has been working on implementing imported humanoid FBX support in Unidot, including bone guessing. The current implementation supports FBX source models and performs bone name guessing when humanDescription is empty. However, it does not yet support humanoid .anim clips, and there are known issues applying Animator components to already-imported models.\nAfter fixing a typo in Fix Silhouette, Lyuma reported that FBX humanoid animation import in Unidot seems much closer. They also implemented support for “Copy from other Avatar” to handle conversion of Maya FBX files with the first frame posed like the animation. This allows using the T-pose of another model as the rest pose.\nLyuma shared their progress on Twitter, showcasing the effectiveness of Unidot-Importer by VSekaiOfficial and Godot 4.0’s new humanoid retargeter system. The Godot Engine community also discovered the team’s GLTF work, as seen in a tweet by Bramwell.\nGamefromscratch covered Godot -&gt; Unity migration in a YouTube video, highlighting the use of barcoderdev’s version of FBX2glTF with Unidot, which might solve the pivot issue encountered earlier."
+    "text": "This is the changelog for March 2023.\nGodot Engine 4.0 launched on March 1st. 🎉\n\n\nUpgrade the documentation to point to github actions.\nPosted changes to https://github.com/godotengine/tps-demo/pull/167 to improve Github Actions export\nWorking on https://github.com/V-Sekai/blender-art-blue-tin-fox-models to get a list of prototype models.\nTuned the vr vingette usability feature to be more black.\nCreate an Awesome V-sekai page https://github.com/V-Sekai/awesome-v-sekai.\nMigrate the manual page to https://v-sekai.github.io/manuals\nInvestigated SHARK and IREE. Provides vulkan for machine learning.\nWrote a proposal for libfbx. https://github.com/godotengine/godot-proposals/issues/6453\nDid some removal of non essential code towards being in vr, loading maps and being in an avatar.\nRestore the brightness defaults in physical lighting.\nTrial variable rate shading.\nUpdate VSK_model_explorer to stable Godot Engine 4.0.\nHelped HungryProton add an automated build system for his ProtonGraph application. https://github.com/protongraph/protongraph\nTrying to get Godot Engine V-Sekai builds to pass. There was a breaking change in Scons.\nLibgodot doesn’t pass unit testing.\nUpdated https://github.com/V-Sekai/godot-task-goal-planner ’s gut addon and remove vsk versioning.\nReleased embedding search example with Marqo. https://github.com/fire/soriee-search\n\n\n\n\n\n\n\n\n\nSequence\nPose\n\n\n\n\n0\nT-pose\n\n\n1\nA-Pose\n\n\n2\nHands beside the upper leg, palms inwards at “At Ease”.\n\n\n3\nLift left leg\n\n\n4\nPut hands next to the face in a claw position palms facing outwards\n\n\n5\nHands at “At Ease”\n\n\n6\nLift left arm from “At Ease” to pointing straight upwards\n\n\n7\nLift left arm from “At Ease” to pointing upwards and wave off to a side\n\n\n8\nPoint left index finger\n\n\n9\nHands at “At Ease”\n\n\n10\nBicycle pose\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nOrganization\nDescription\ndate\n\n\n\n\nGodot Engine Foundation & V-Sekai\nCSG Fire Chatted about CSG with reduz First Meeting\n2023-03-30 00:00:00\n\n\nV-Sekai\nPhysics Colliders Fire CoACD https://github.com/SarahWeiii/CoACD/issues/9\n2023-03-30 00:00:00\n\n\nV-Sekai & Thorvg\nFire Fire Review thorvg PR https://github.com/godotengine/godot/pull/75508\n2023-03-30 00:00:00\n\n\nV-Sekai\nFire Fire Play a horror game First Meeting\n2023-03-30 00:00:00\n\n\nV-Sekai & Zylann\nFire Fire Asked zylann to review double precision pr\n2023-03-30 00:00:00\n\n\nV-Sekai\nFire Fire Restore github cicd First Meeting\n2023-03-30 00:00:00\n\n\nV-Sekai\nFire Fire Animation iks as node first draft posted. First draft\n2023-03-30 00:00:00\n\n\nV-Sekai\nFire Fire Propose a animation node pr First Meeting\n2023-03-30 00:00:00"
   },
   {
-    "objectID": "changelog/2023/20230501-changelog.html#unidot-update-summary",
-    "href": "changelog/2023/20230501-changelog.html#unidot-update-summary",
-    "title": "V-Sekai Changelog - 2023-05",
+    "objectID": "changelog/2023/20230301-changelog.html#fire",
+    "href": "changelog/2023/20230301-changelog.html#fire",
+    "title": "V-Sekai Changelog - 2023-03",
     "section": "",
-    "text": "Lyuma has been working on implementing imported humanoid FBX support in Unidot, including bone guessing. The current implementation supports FBX source models and performs bone name guessing when humanDescription is empty. However, it does not yet support humanoid .anim clips, and there are known issues applying Animator components to already-imported models.\nAfter fixing a typo in Fix Silhouette, Lyuma reported that FBX humanoid animation import in Unidot seems much closer. They also implemented support for “Copy from other Avatar” to handle conversion of Maya FBX files with the first frame posed like the animation. This allows using the T-pose of another model as the rest pose.\nLyuma shared their progress on Twitter, showcasing the effectiveness of Unidot-Importer by VSekaiOfficial and Godot 4.0’s new humanoid retargeter system. The Godot Engine community also discovered the team’s GLTF work, as seen in a tweet by Bramwell.\nGamefromscratch covered Godot -&gt; Unity migration in a YouTube video, highlighting the use of barcoderdev’s version of FBX2glTF with Unidot, which might solve the pivot issue encountered earlier."
+    "text": "Upgrade the documentation to point to github actions.\nPosted changes to https://github.com/godotengine/tps-demo/pull/167 to improve Github Actions export\nWorking on https://github.com/V-Sekai/blender-art-blue-tin-fox-models to get a list of prototype models.\nTuned the vr vingette usability feature to be more black.\nCreate an Awesome V-sekai page https://github.com/V-Sekai/awesome-v-sekai.\nMigrate the manual page to https://v-sekai.github.io/manuals\nInvestigated SHARK and IREE. Provides vulkan for machine learning.\nWrote a proposal for libfbx. https://github.com/godotengine/godot-proposals/issues/6453\nDid some removal of non essential code towards being in vr, loading maps and being in an avatar.\nRestore the brightness defaults in physical lighting.\nTrial variable rate shading.\nUpdate VSK_model_explorer to stable Godot Engine 4.0.\nHelped HungryProton add an automated build system for his ProtonGraph application. https://github.com/protongraph/protongraph\nTrying to get Godot Engine V-Sekai builds to pass. There was a breaking change in Scons.\nLibgodot doesn’t pass unit testing.\nUpdated https://github.com/V-Sekai/godot-task-goal-planner ’s gut addon and remove vsk versioning.\nReleased embedding search example with Marqo. https://github.com/fire/soriee-search\n\n\n\n\n\n\n\n\n\nSequence\nPose\n\n\n\n\n0\nT-pose\n\n\n1\nA-Pose\n\n\n2\nHands beside the upper leg, palms inwards at “At Ease”.\n\n\n3\nLift left leg\n\n\n4\nPut hands next to the face in a claw position palms facing outwards\n\n\n5\nHands at “At Ease”\n\n\n6\nLift left arm from “At Ease” to pointing straight upwards\n\n\n7\nLift left arm from “At Ease” to pointing upwards and wave off to a side\n\n\n8\nPoint left index finger\n\n\n9\nHands at “At Ease”\n\n\n10\nBicycle pose\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nOrganization\nDescription\ndate\n\n\n\n\nGodot Engine Foundation & V-Sekai\nCSG Fire Chatted about CSG with reduz First Meeting\n2023-03-30 00:00:00\n\n\nV-Sekai\nPhysics Colliders Fire CoACD https://github.com/SarahWeiii/CoACD/issues/9\n2023-03-30 00:00:00\n\n\nV-Sekai & Thorvg\nFire Fire Review thorvg PR https://github.com/godotengine/godot/pull/75508\n2023-03-30 00:00:00\n\n\nV-Sekai\nFire Fire Play a horror game First Meeting\n2023-03-30 00:00:00\n\n\nV-Sekai & Zylann\nFire Fire Asked zylann to review double precision pr\n2023-03-30 00:00:00\n\n\nV-Sekai\nFire Fire Restore github cicd First Meeting\n2023-03-30 00:00:00\n\n\nV-Sekai\nFire Fire Animation iks as node first draft posted. First draft\n2023-03-30 00:00:00\n\n\nV-Sekai\nFire Fire Propose a animation node pr First Meeting\n2023-03-30 00:00:00"
   },
   {
-    "objectID": "changelog/2023/20231109-changelog.html",
-    "href": "changelog/2023/20231109-changelog.html",
-    "title": "V-Sekai Changelog - November 2023",
+    "objectID": "changelog/2023/20231207-changelog.html",
+    "href": "changelog/2023/20231207-changelog.html",
+    "title": "V-Sekai Changelog - December 2023",
     "section": "",
-    "text": "V-Sekai.xr-grid is a VR interaction tool.\n\nFirst release\nRelease Version: 0.1.0-rc1\nChanges: The game name environment variable has been updated in the build workflow. A new commit was also made to set the draft flag to false for the release.\nRelease Link\n\n\n\n\nV-Sekai Model Explorer is a 3D model viewer built with Godot 4. It supports various model formats like VRM and glTF 2.0. With this tool, you can dive deep into the components of a 3D model - inspecting meshes, materials, textures, and animations.\n\nFirst release\nRelease Version: v0.2.0-rc2\nChanges: The GAMENAME environment variable value has been changed to “vsekai_model_explorer”. The macos_editor_macos_deploy job from builds.yml has been removed. A README.md for GitHub actions has been added and the warning has been moved to the top of the file.\nRelease Link\n\n\n\n\n\n\n\n\nMacOS Editor Builds: MacOS editor builds have been added to the project. (Commit: df041f0)\nExport Mac Game: The game can now be exported for Mac. Pending code-signing and App support.\nGolang Installation: Golang has been installed in the project. (Commit: c25456b)\nUnidot Dependency Removal: The dependency on the post-import script by Unidot has been removed after conversion is complete. This means the converted assets will work standalone without the Unidot importer, with one exception*.\nSupported Asset Types: Supported asset types are listed in the readme. It should support many types of meshes, animations, Standard shader materials, scenes/prefabs and physics objects.\nOptimization for Generating Tangents in Mikktspace: An optimization has been added for generating tangents in mikktspace. (Pull Request #83648)\n\n\n\n\n\nGame Name Variable: A game name variable has been implemented on Github Actions. (Commit: 08d87db)\nGodot Engine Repository Update: The Godot engine repository and reference in build workflows have been updated. (Commit: f7f609d)\nImports Update: Imports in the project have been updated. (Commit: 896cb7c)\nUnidot Beta Release: Unidot is now in a beta / early RC for the first release.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nSecurity Best Practices: Applied security best practices as recommended by StepSecurity. (Commit: d641001)\n\nThis project does not adhere to Semantic Versioning.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nLyuma, a member of the V-Sekai team, recently attended the Godot Engine Munich 2023 conference.\nShaders or MonoBehaviors/scripts are not currently supported. This will not be part of the initial release. The goal for now is scene / character / animation conversion.\nAnimationTree uses the standalone runtime/anim_tree.gd script as a blackboard system to simulate unity parameters. This file should remain.\nUnidot Importer Github Link\nA wild spooky dev snapshot appears! 👻 🎃 Contributors are making great progress on solving regressions in Godot 4.2! This new 4.2 beta 4 should be significantly more stable and reliable to upgrade 4.1 projects (not perfect yet though!). Godot Engine Dev snapshot: Godot 4.2 beta 4 We continue iterating quickly on beta snapshots for Godot 4.2 to ensure that we can solve regressions before the stable release."
+    "text": "2023-12-11 20:10: Unidot Importer | Unidot Importer. Unidot is a .unitypackage asset interoperability tool to bring assets designed for other engines into Godot Engine. Check it out here.\n2023-12-12 04:19: Unidot was submitted to the asset library! We have a separate discord server for Unidot Importer: Join us on Discord. It’s kind of a companion for V-Sekai, but I expect a lot of general game developers joining who have little interest in VR or social virtual worlds, so I think it’s good to have a separate community.\n\n\n\n\nInitial commit on TOOL_game_start:main branch.\nNew commits to godot:master adding various features and fixes.\nUnify tangents in obj on godot:unify-tangents-obj branch.\nUpdates to manuals:main branch.\nAddition of mtlx on godot:godot-mtlx-4.2 branch.\nUpdates to godot-usd:main branch\nUpdated https://saracenone.itch.io/groups-4x on godot engine master (4.3). DX12 is not enabled.\n\n\n\n\n\nForce-pushed changes to various branches in the godot repository.\nMerged pull requests on V-Sekai.xr-grid:main branch.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nRemoval of git submodules on godot-mtlx:godot-rebase branch.\n\n\n\n\n\nSecurity Best Practices: Applied security best practices as recommended by StepSecurity.\n\nThis project does not adhere to Semantic Versioning.\n\n\n\n\n\nNot applicable for this month."
   },
   {
-    "objectID": "changelog/2023/20231109-changelog.html#released",
-    "href": "changelog/2023/20231109-changelog.html#released",
-    "title": "V-Sekai Changelog - November 2023",
+    "objectID": "changelog/2023/20231207-changelog.html#released",
+    "href": "changelog/2023/20231207-changelog.html#released",
+    "title": "V-Sekai Changelog - December 2023",
     "section": "",
-    "text": "V-Sekai.xr-grid is a VR interaction tool.\n\nFirst release\nRelease Version: 0.1.0-rc1\nChanges: The game name environment variable has been updated in the build workflow. A new commit was also made to set the draft flag to false for the release.\nRelease Link\n\n\n\n\nV-Sekai Model Explorer is a 3D model viewer built with Godot 4. It supports various model formats like VRM and glTF 2.0. With this tool, you can dive deep into the components of a 3D model - inspecting meshes, materials, textures, and animations.\n\nFirst release\nRelease Version: v0.2.0-rc2\nChanges: The GAMENAME environment variable value has been changed to “vsekai_model_explorer”. The macos_editor_macos_deploy job from builds.yml has been removed. A README.md for GitHub actions has been added and the warning has been moved to the top of the file.\nRelease Link"
+    "text": "2023-12-11 20:10: Unidot Importer | Unidot Importer. Unidot is a .unitypackage asset interoperability tool to bring assets designed for other engines into Godot Engine. Check it out here.\n2023-12-12 04:19: Unidot was submitted to the asset library! We have a separate discord server for Unidot Importer: Join us on Discord. It’s kind of a companion for V-Sekai, but I expect a lot of general game developers joining who have little interest in VR or social virtual worlds, so I think it’s good to have a separate community.\n\n\n\n\nInitial commit on TOOL_game_start:main branch.\nNew commits to godot:master adding various features and fixes.\nUnify tangents in obj on godot:unify-tangents-obj branch.\nUpdates to manuals:main branch.\nAddition of mtlx on godot:godot-mtlx-4.2 branch.\nUpdates to godot-usd:main branch\nUpdated https://saracenone.itch.io/groups-4x on godot engine master (4.3). DX12 is not enabled.\n\n\n\n\n\nForce-pushed changes to various branches in the godot repository.\nMerged pull requests on V-Sekai.xr-grid:main branch.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nRemoval of git submodules on godot-mtlx:godot-rebase branch.\n\n\n\n\n\nSecurity Best Practices: Applied security best practices as recommended by StepSecurity.\n\nThis project does not adhere to Semantic Versioning."
   },
   {
-    "objectID": "changelog/2023/20231109-changelog.html#unreleased",
-    "href": "changelog/2023/20231109-changelog.html#unreleased",
-    "title": "V-Sekai Changelog - November 2023",
+    "objectID": "changelog/2023/20231207-changelog.html#previous-releases",
+    "href": "changelog/2023/20231207-changelog.html#previous-releases",
+    "title": "V-Sekai Changelog - December 2023",
     "section": "",
-    "text": "MacOS Editor Builds: MacOS editor builds have been added to the project. (Commit: df041f0)\nExport Mac Game: The game can now be exported for Mac. Pending code-signing and App support.\nGolang Installation: Golang has been installed in the project. (Commit: c25456b)\nUnidot Dependency Removal: The dependency on the post-import script by Unidot has been removed after conversion is complete. This means the converted assets will work standalone without the Unidot importer, with one exception*.\nSupported Asset Types: Supported asset types are listed in the readme. It should support many types of meshes, animations, Standard shader materials, scenes/prefabs and physics objects.\nOptimization for Generating Tangents in Mikktspace: An optimization has been added for generating tangents in mikktspace. (Pull Request #83648)\n\n\n\n\n\nGame Name Variable: A game name variable has been implemented on Github Actions. (Commit: 08d87db)\nGodot Engine Repository Update: The Godot engine repository and reference in build workflows have been updated. (Commit: f7f609d)\nImports Update: Imports in the project have been updated. (Commit: 896cb7c)\nUnidot Beta Release: Unidot is now in a beta / early RC for the first release.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nSecurity Best Practices: Applied security best practices as recommended by StepSecurity. (Commit: d641001)\n\nThis project does not adhere to Semantic Versioning."
+    "text": "Not applicable for this month."
   },
   {
-    "objectID": "changelog/2023/20231109-changelog.html#previous-releases",
-    "href": "changelog/2023/20231109-changelog.html#previous-releases",
-    "title": "V-Sekai Changelog - November 2023",
+    "objectID": "changelog/2023/20230801-changelog.html",
+    "href": "changelog/2023/20230801-changelog.html",
+    "title": "V-Sekai Changelog - August 2023",
     "section": "",
-    "text": "Not applicable for this month."
+    "text": "Basisu (ktx2) for gltf was merged to allow compressing the textures to KTX2, which is GPU compatible and has a very small size. Our project also deals with hundreds and thousands of models placed in one scene, making the file size of each model crucial.\nRechieKho Integrated the iree.gd library with Godot game engine and allows Godot projects to leverage IREE for machine learning workflows.\n\nAddition of Godot image &lt;-&gt; IREE buffer view conversion utilities\nExposure of IREE workflow\nAddition of Godot demos showing IREE integration\n\nRecreated Architext demo for testing apartment blueprint generation.\nGodot VRM has been submitted to the asset library for 4.x by Lyuma on 2023-08-03. It’s now usable and most bugs have been fixed. One known issue is that node constraints have some issues on models which were retargeted (needed bone rotation). If anyone wants to play with godot-vrm, feel free to clone it from github: it’s the same as the version that will be available in the Godot Asset Library. Readme is updated. Feel free to check it out and give feedback. Github Link\nNew commits to godot_uro:main by Lyuma and Fire.\nNew commits to v-sekai-game:main by Lyuma and Fire.\nNew commits to godot:groups-staging-4.2 by Fire.\nNew commits to godot:vsk-many-bone-ik-4.2 by Fire.\nNew commits to v-sekai-game:update-translations by Fire.\nNew commits to v-sekai-game:update-godot by Fire.\nNew commits to godot-vrm:only-addon by Lyuma.\nNew commits to godot-vrm:master by Lyuma.\nNew commits to godot:vsk-flac-4.2 by Fire.\nNew commits to godot:vsk-subdiv-4-0 branch.\nForce-pushed updates to godot branches: vsk-subdiv-4-0, groups-staging-4.2, scene-import-fixes, faster-generate-lod.\nDeletion of branches in V-Sekai/v-sekai-game: migrate-authors, all-contributors/add-lyuma, all-contributors/add-EnthWyrr.\nCreation of new branches in V-Sekai/v-sekai-game: gh-readonly-queue/main/pr-213-d5fbc97d5854516d4305eb94fb6a81307256c978, all-contributors/- add-s-ilent, gh-readonly-queue/main/pr-215-e72f9297674c4c2f82dcc59ba8af18a03fd86fcc, gh-readonly-queue/main/pr-215-d5fbc97d5854516d4305eb94fb6a81307256c978, gh-readonly-queue/main/pr-213-2a174801a0b88ccdfc9c3671230911f6978477bd.\nNew commits to godot:groups-staging-4.2 branch.\nCreation of new branches in V-Sekai/godot: groups-staging-lbfgs, vsk-lbfgs-4.2.\nBump of github/codeql-action from 2.21.4 to 2.21.5 in V-Sekai/v-sekai-game.\nCreation of new branch in V-Sekai/v-sekai-game: dependabot/github_actions/github/codeql-action-2.21.5.\nPull requests #213 and #215 in V-Sekai/v-sekai-game.\nPull request #216 (Bump github/codeql-action from 2.21.4 to 2.21.5) in V-Sekai/v-sekai-game.\n\n\n\n\n\nUpdated localization files for VR manager and menu strings by Fire.\nUpdated the ref value for the v-sekai-game repository to groups-4.2.2023-08-01T161313Z by Fire.\nUpdated godot-deps action.yml by Fire.\nUpdated icons path in FLAC config module by Fire.\nUpdates to README.md and .all-contributorsrc in V-Sekai/v-sekai-game.\nRefactoring and updates in godot:groups-staging-4.2 and godot:vsk-lbfgs-4.2 branches.\n\n\n\n\n\nFix theme of export dialog by Lyuma.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nMany Bone IK has been removed temporarily to ensure the engine builds and passes tests.\nDeletion of branches in V-Sekai/v-sekai-game: gh-readonly-queue/main/pr-213-d5fbc97d5854516d4305eb94fb6a81307256c978, gh-readonly-queue/main/pr-215-e72f9297674c4c2f82dcc59ba8af18a03fd86fcc, gh-readonly-queue/main/pr-215-d5fbc97d5854516d4305eb94fb6a81307256c978, gh-readonly-queue/main/pr-213-2a174801a0b88ccdfc9c3671230911f6978477bd, groups-4.2-latest, dependabot/github_actions/github/codeql-action-2.21.5. MMD PMX scene importer in godot:groups-staging-4.2 branch.\n\n\n\n\n\nNot applicable for this month.\n\nThis project does not adhere to Semantic Versioning.\n\n\n\n\n\nNot applicable for this month.\n\nNote: This changelog has been compiled based on the updates provided. For more detailed information, please refer to the specific issues or pull requests in the respective repositories."
   },
   {
-    "objectID": "changelog/2023/20231109-changelog.html#misc",
-    "href": "changelog/2023/20231109-changelog.html#misc",
-    "title": "V-Sekai Changelog - November 2023",
+    "objectID": "changelog/2023/20230801-changelog.html#unreleased",
+    "href": "changelog/2023/20230801-changelog.html#unreleased",
+    "title": "V-Sekai Changelog - August 2023",
     "section": "",
-    "text": "Lyuma, a member of the V-Sekai team, recently attended the Godot Engine Munich 2023 conference.\nShaders or MonoBehaviors/scripts are not currently supported. This will not be part of the initial release. The goal for now is scene / character / animation conversion.\nAnimationTree uses the standalone runtime/anim_tree.gd script as a blackboard system to simulate unity parameters. This file should remain.\nUnidot Importer Github Link\nA wild spooky dev snapshot appears! 👻 🎃 Contributors are making great progress on solving regressions in Godot 4.2! This new 4.2 beta 4 should be significantly more stable and reliable to upgrade 4.1 projects (not perfect yet though!). Godot Engine Dev snapshot: Godot 4.2 beta 4 We continue iterating quickly on beta snapshots for Godot 4.2 to ensure that we can solve regressions before the stable release."
+    "text": "Basisu (ktx2) for gltf was merged to allow compressing the textures to KTX2, which is GPU compatible and has a very small size. Our project also deals with hundreds and thousands of models placed in one scene, making the file size of each model crucial.\nRechieKho Integrated the iree.gd library with Godot game engine and allows Godot projects to leverage IREE for machine learning workflows.\n\nAddition of Godot image &lt;-&gt; IREE buffer view conversion utilities\nExposure of IREE workflow\nAddition of Godot demos showing IREE integration\n\nRecreated Architext demo for testing apartment blueprint generation.\nGodot VRM has been submitted to the asset library for 4.x by Lyuma on 2023-08-03. It’s now usable and most bugs have been fixed. One known issue is that node constraints have some issues on models which were retargeted (needed bone rotation). If anyone wants to play with godot-vrm, feel free to clone it from github: it’s the same as the version that will be available in the Godot Asset Library. Readme is updated. Feel free to check it out and give feedback. Github Link\nNew commits to godot_uro:main by Lyuma and Fire.\nNew commits to v-sekai-game:main by Lyuma and Fire.\nNew commits to godot:groups-staging-4.2 by Fire.\nNew commits to godot:vsk-many-bone-ik-4.2 by Fire.\nNew commits to v-sekai-game:update-translations by Fire.\nNew commits to v-sekai-game:update-godot by Fire.\nNew commits to godot-vrm:only-addon by Lyuma.\nNew commits to godot-vrm:master by Lyuma.\nNew commits to godot:vsk-flac-4.2 by Fire.\nNew commits to godot:vsk-subdiv-4-0 branch.\nForce-pushed updates to godot branches: vsk-subdiv-4-0, groups-staging-4.2, scene-import-fixes, faster-generate-lod.\nDeletion of branches in V-Sekai/v-sekai-game: migrate-authors, all-contributors/add-lyuma, all-contributors/add-EnthWyrr.\nCreation of new branches in V-Sekai/v-sekai-game: gh-readonly-queue/main/pr-213-d5fbc97d5854516d4305eb94fb6a81307256c978, all-contributors/- add-s-ilent, gh-readonly-queue/main/pr-215-e72f9297674c4c2f82dcc59ba8af18a03fd86fcc, gh-readonly-queue/main/pr-215-d5fbc97d5854516d4305eb94fb6a81307256c978, gh-readonly-queue/main/pr-213-2a174801a0b88ccdfc9c3671230911f6978477bd.\nNew commits to godot:groups-staging-4.2 branch.\nCreation of new branches in V-Sekai/godot: groups-staging-lbfgs, vsk-lbfgs-4.2.\nBump of github/codeql-action from 2.21.4 to 2.21.5 in V-Sekai/v-sekai-game.\nCreation of new branch in V-Sekai/v-sekai-game: dependabot/github_actions/github/codeql-action-2.21.5.\nPull requests #213 and #215 in V-Sekai/v-sekai-game.\nPull request #216 (Bump github/codeql-action from 2.21.4 to 2.21.5) in V-Sekai/v-sekai-game.\n\n\n\n\n\nUpdated localization files for VR manager and menu strings by Fire.\nUpdated the ref value for the v-sekai-game repository to groups-4.2.2023-08-01T161313Z by Fire.\nUpdated godot-deps action.yml by Fire.\nUpdated icons path in FLAC config module by Fire.\nUpdates to README.md and .all-contributorsrc in V-Sekai/v-sekai-game.\nRefactoring and updates in godot:groups-staging-4.2 and godot:vsk-lbfgs-4.2 branches.\n\n\n\n\n\nFix theme of export dialog by Lyuma.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nMany Bone IK has been removed temporarily to ensure the engine builds and passes tests.\nDeletion of branches in V-Sekai/v-sekai-game: gh-readonly-queue/main/pr-213-d5fbc97d5854516d4305eb94fb6a81307256c978, gh-readonly-queue/main/pr-215-e72f9297674c4c2f82dcc59ba8af18a03fd86fcc, gh-readonly-queue/main/pr-215-d5fbc97d5854516d4305eb94fb6a81307256c978, gh-readonly-queue/main/pr-213-2a174801a0b88ccdfc9c3671230911f6978477bd, groups-4.2-latest, dependabot/github_actions/github/codeql-action-2.21.5. MMD PMX scene importer in godot:groups-staging-4.2 branch.\n\n\n\n\n\nNot applicable for this month.\n\nThis project does not adhere to Semantic Versioning."
   },
   {
-    "objectID": "changelog/2022/20220401-changelog.html",
-    "href": "changelog/2022/20220401-changelog.html",
-    "title": "V-Sekai Changelog - 2022-04",
+    "objectID": "changelog/2023/20230801-changelog.html#previous-releases",
+    "href": "changelog/2023/20230801-changelog.html#previous-releases",
+    "title": "V-Sekai Changelog - August 2023",
     "section": "",
-    "text": "Moved issues into the tracker.\n\n\nWorked with manifold csg library author and was able to remove the boost dependency. https://github.com/elalish/manifold/pull/92\nAlso published a first draft on a Godot Engine master branch. See the issue for details.\n\n\n\nLyuma\nMade a lot of progress towards animation import in Unidot. Godot’s node system means that some paths become different: for example, meshes have to be reparented to skeletons; or extra levels in the hierarchy to keep track of physics bodies.\nTo this end, it is now keeping a lookup dictionary from path and component to fileID (which can be mapped to Godot node) which means animation support should be close.\n(Also, they made a major change to the import system in 2019 which affects id numbering. Still working on it)\nPushed a major update to Unidot, mostly in the post_import script. It should now generate paths much more accurately to the original file, and implemented the hashing algorithm used by Unity 2019 for file ID generation, for example generating ids like 919132149155446097 for the root object.\nThis has fixed some assets exported from Unity 2019 like below, which used to fail to resolve the fileIDs for meshes! @iFire\nMade some progress with terrain import in Unidot. It will import textures, normalmaps and splatmaps (creating an appropriate ShaderMaterial). My plan is to implement trees and grass using MultimeshInstance objects. With this I also now support texture assets. Texture Arrays seem to fail internally. Hard to tell if I did something wrong or something isn’t implemented on Godot’s end, but we’ll get there…\nperformance-wise, I think it’s now acceptable to just pipe all 2+ million polygons (for 1025x1025 terrain) to the GPU. I’m using tristrips so it’s mostly just 1 index per triangle. It might be better to use a more dedicated terrain system for this, so this is just a stopgap while Godot 4 is in development since the terrain systems in the asset library are not keeping up with the rapid pace of development. (if you’re interested in this subject, feel free to start a thread or reply on godot-general)\nTerrain trees, splatmaps and materials are implemented in Unidot, converting to a single conventional terrain mesh + multimesh. I have not implemented holes yet, but if someone has an example and there is demand, I could work on it.\nI also chose not to implement detail (grasses), because I don’t understand how detail patches are implemented, and they tend to not look that great in VR, so I’d rather work on something else.\n\n\n\n\nRestore fix-save-as-binary so we can export projects\nRestore elixir shared branch so we can run godot in elixir\nPoked ludwig about diffusion net for machine learning training.\n\n\n\n\nFBX2GLTF and Blender importers are merged.\n\n\n\niFire\n\nMade a bug report for Blender exported animation to gltf with @RockyMadio https://github.com/KhronosGroup/glTF-Blender-IO/issues/1613 GitHub"
+    "text": "Not applicable for this month.\n\nNote: This changelog has been compiled based on the updates provided. For more detailed information, please refer to the specific issues or pull requests in the respective repositories."
   },
   {
-    "objectID": "changelog/2022/20220401-changelog.html#section",
-    "href": "changelog/2022/20220401-changelog.html#section",
-    "title": "V-Sekai Changelog - 2022-04",
+    "objectID": "changelog/2023/20230901-changelog.html",
+    "href": "changelog/2023/20230901-changelog.html",
+    "title": "V-Sekai Changelog - September 2023",
     "section": "",
-    "text": "Worked with manifold csg library author and was able to remove the boost dependency. https://github.com/elalish/manifold/pull/92\nAlso published a first draft on a Godot Engine master branch. See the issue for details."
+    "text": "Ported RenIK to GDScript, providing a reference implementation and allowing for separation of RenIKPlacement from RenIK as two distinct nodes. This change enables reuse of the foot placement implementation on any other IK system or swapping out the foot placement system for another animation system and then running the IK algorithm independently. The port was challenging due to differences in the Basis APIs between C++ and GDScript. The GDScript code is available at https://github.com/V-Sekai/renik/tree/gdscript and can be used instead of the original C++ version at https://github.com/V-Sekai/renik. It includes a test scene for use in projects.\n\n\n\n\n\n\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\n\n\n\nNot applicable for this month.\n\nThis project does not adhere to Semantic Versioning.\n\n\n\n\n\nNot applicable for this month.\n\nNote: This changelog has been compiled based on the updates provided. For more detailed information, please refer to the specific issues or pull requests in the respective repositories.\n\n\n\ncommit dc4754b - (main) Merge pull request #242 from V-Sekai/move-utility Move the utility folder.\ncommit f854698 - (main) Merge pull request #241 from V-Sekai/better-svgs Improve the logos.\ncommit 5928dee - (main) Merge pull request #239 from V-Sekai/remove-unused-01 Remove unnecessary files and configurations for Mac development in vs code.\ncommit 8c34654 - (remove-unused-math-utils) Remove unused math utils.\ncommit 9860967 - (main) Merge pull request #245 from V-Sekai/xr-on Make xr mode on.\ncommit 6147202 - (xr-on) Make xr mode on.\ncommit dc4754b - (main) Merge pull request #242 from V-Sekai/move-utility Move the utility folder.\ncommit 83b4490 - (move-utility) Move the utility folder.\ncommit f854698 - (main) Merge pull request #241 from V-Sekai/better-svgs Improve the logos.\ncommit 6519cce - (better-svgs) Improve the logos.\nWrite a constraint minimizer https://github.com/V-Sekai/v-sekai-game/blob/constraint-minimizer/new_script.gd\nWrite a github action for godot engine so I can push releases\nUpdate github actions for tagged release. Use the 0.1.0-alpha1 tag.\nInvestigate https://about.signpath.io/product/open-source for part 2\nLauncher https://gist.github.com/fire/e5a16d3e738e8575b8ce7f527c245d27\nPeople are asking about 3d ik so I need to increase the code quality of https://github.com/V-Sekai/renik"
   },
   {
-    "objectID": "changelog/2022/20220401-changelog.html#section-1",
-    "href": "changelog/2022/20220401-changelog.html#section-1",
-    "title": "V-Sekai Changelog - 2022-04",
+    "objectID": "changelog/2023/20230901-changelog.html#unreleased",
+    "href": "changelog/2023/20230901-changelog.html#unreleased",
+    "title": "V-Sekai Changelog - September 2023",
     "section": "",
-    "text": "Lyuma\nMade a lot of progress towards animation import in Unidot. Godot’s node system means that some paths become different: for example, meshes have to be reparented to skeletons; or extra levels in the hierarchy to keep track of physics bodies.\nTo this end, it is now keeping a lookup dictionary from path and component to fileID (which can be mapped to Godot node) which means animation support should be close.\n(Also, they made a major change to the import system in 2019 which affects id numbering. Still working on it)\nPushed a major update to Unidot, mostly in the post_import script. It should now generate paths much more accurately to the original file, and implemented the hashing algorithm used by Unity 2019 for file ID generation, for example generating ids like 919132149155446097 for the root object.\nThis has fixed some assets exported from Unity 2019 like below, which used to fail to resolve the fileIDs for meshes! @iFire\nMade some progress with terrain import in Unidot. It will import textures, normalmaps and splatmaps (creating an appropriate ShaderMaterial). My plan is to implement trees and grass using MultimeshInstance objects. With this I also now support texture assets. Texture Arrays seem to fail internally. Hard to tell if I did something wrong or something isn’t implemented on Godot’s end, but we’ll get there…\nperformance-wise, I think it’s now acceptable to just pipe all 2+ million polygons (for 1025x1025 terrain) to the GPU. I’m using tristrips so it’s mostly just 1 index per triangle. It might be better to use a more dedicated terrain system for this, so this is just a stopgap while Godot 4 is in development since the terrain systems in the asset library are not keeping up with the rapid pace of development. (if you’re interested in this subject, feel free to start a thread or reply on godot-general)\nTerrain trees, splatmaps and materials are implemented in Unidot, converting to a single conventional terrain mesh + multimesh. I have not implemented holes yet, but if someone has an example and there is demand, I could work on it.\nI also chose not to implement detail (grasses), because I don’t understand how detail patches are implemented, and they tend to not look that great in VR, so I’d rather work on something else."
+    "text": "Ported RenIK to GDScript, providing a reference implementation and allowing for separation of RenIKPlacement from RenIK as two distinct nodes. This change enables reuse of the foot placement implementation on any other IK system or swapping out the foot placement system for another animation system and then running the IK algorithm independently. The port was challenging due to differences in the Basis APIs between C++ and GDScript. The GDScript code is available at https://github.com/V-Sekai/renik/tree/gdscript and can be used instead of the original C++ version at https://github.com/V-Sekai/renik. It includes a test scene for use in projects."
   },
   {
-    "objectID": "changelog/2022/20220401-changelog.html#section-2",
-    "href": "changelog/2022/20220401-changelog.html#section-2",
-    "title": "V-Sekai Changelog - 2022-04",
+    "objectID": "changelog/2023/20230901-changelog.html#changed",
+    "href": "changelog/2023/20230901-changelog.html#changed",
+    "title": "V-Sekai Changelog - September 2023",
     "section": "",
-    "text": "Restore fix-save-as-binary so we can export projects\nRestore elixir shared branch so we can run godot in elixir\nPoked ludwig about diffusion net for machine learning training."
+    "text": "Not applicable for this month.\n\n\n\n\n\n\n\n\nNot applicable for this month.\n\nThis project does not adhere to Semantic Versioning."
   },
   {
-    "objectID": "changelog/2022/20220401-changelog.html#section-3",
-    "href": "changelog/2022/20220401-changelog.html#section-3",
-    "title": "V-Sekai Changelog - 2022-04",
+    "objectID": "changelog/2023/20230901-changelog.html#previous-releases",
+    "href": "changelog/2023/20230901-changelog.html#previous-releases",
+    "title": "V-Sekai Changelog - September 2023",
     "section": "",
-    "text": "FBX2GLTF and Blender importers are merged."
+    "text": "Not applicable for this month.\n\nNote: This changelog has been compiled based on the updates provided. For more detailed information, please refer to the specific issues or pull requests in the respective repositories."
   },
   {
-    "objectID": "changelog/2022/20220401-changelog.html#section-4",
-    "href": "changelog/2022/20220401-changelog.html#section-4",
-    "title": "V-Sekai Changelog - 2022-04",
+    "objectID": "changelog/2023/20230901-changelog.html#work-in-progress",
+    "href": "changelog/2023/20230901-changelog.html#work-in-progress",
+    "title": "V-Sekai Changelog - September 2023",
     "section": "",
-    "text": "iFire\n\nMade a bug report for Blender exported animation to gltf with @RockyMadio https://github.com/KhronosGroup/glTF-Blender-IO/issues/1613 GitHub"
+    "text": "commit dc4754b - (main) Merge pull request #242 from V-Sekai/move-utility Move the utility folder.\ncommit f854698 - (main) Merge pull request #241 from V-Sekai/better-svgs Improve the logos.\ncommit 5928dee - (main) Merge pull request #239 from V-Sekai/remove-unused-01 Remove unnecessary files and configurations for Mac development in vs code.\ncommit 8c34654 - (remove-unused-math-utils) Remove unused math utils.\ncommit 9860967 - (main) Merge pull request #245 from V-Sekai/xr-on Make xr mode on.\ncommit 6147202 - (xr-on) Make xr mode on.\ncommit dc4754b - (main) Merge pull request #242 from V-Sekai/move-utility Move the utility folder.\ncommit 83b4490 - (move-utility) Move the utility folder.\ncommit f854698 - (main) Merge pull request #241 from V-Sekai/better-svgs Improve the logos.\ncommit 6519cce - (better-svgs) Improve the logos.\nWrite a constraint minimizer https://github.com/V-Sekai/v-sekai-game/blob/constraint-minimizer/new_script.gd\nWrite a github action for godot engine so I can push releases\nUpdate github actions for tagged release. Use the 0.1.0-alpha1 tag.\nInvestigate https://about.signpath.io/product/open-source for part 2\nLauncher https://gist.github.com/fire/e5a16d3e738e8575b8ce7f527c245d27\nPeople are asking about 3d ik so I need to increase the code quality of https://github.com/V-Sekai/renik"
   },
   {
-    "objectID": "changelog/2022/20220101-changelog.html",
-    "href": "changelog/2022/20220101-changelog.html",
-    "title": "V-Sekai Changelog - 2022-01",
+    "objectID": "changelog/2022/20221001-changelog.html",
+    "href": "changelog/2022/20221001-changelog.html",
+    "title": "V-Sekai Changelog - 2022-10",
     "section": "",
-    "text": "iFire wrote with Lyuma some proposals:\n\nCICD as a TrueNas Scale system\nProposal for Github CICD actions.\n\nBastiaanOlij updated the OpenXR pull request so it now uses OpenXR 1.0.22 and it has that DISABLE_STD_FILESYSTEM switch in there.\n\n\nSwitch proposal website to use https://quarto.org/.\nUpdated nomnoml diagrams.\n\n\n\n&lt;Lyuma&gt; Merged VR support (including OpenXR and the ability to create OpenVR as a plugin) into our godot engine build.\n\n\n\nMaterial Maker was patched so that OpenEXR export don’t shift color channels in generated EXR file."
+    "text": "Lyuma — 01/10/2022 I have pushed internal and external resource whitelisting at the ResrouceLoader (ResourceFormatLoaderBinary) level as a Godot engine patch.\n\nHere’s an example of what gets printed when the above script with OS.alert() attempts to be loaded\nERROR: user://asset_cache/81dd12d03686\n0a08faba06a1b47a3a29.scn:Resource of unrecognized type in file: GDScript.\n   at: load (core/io/resource_format_binary.cpp:789)\nERROR: Failed loading resource: user://asset_cache/81dd12d036860a08faba06a1b47a3a29.scn. Make sure resources have been imported by opening the project in the editor at least once.\nNote that I was forced to rebase to the latest build which includes the new build system (target=editor) most of the code I changed is in the private gitlab repo. once things stabilize and we get the build system up and running again, next step is to publish the remainder of the code on github\n\ngroups-4.x (and staging) were updated to latest. I attempted to update GoCD, but it’s a bit of a yolo merge, since a few pieces all had to be updated at once due to new scons target=editor argument we need to follow https://ci.v-sekai.cloud/ (log in as guest) and test the release builds\n\n\nexport builds are being created again with the new scons naming scheme. They seem to work on linux (steam deck) at least. Don’t have access to a windows machine right now\n\n\n\n\nhttps://github.com/v-sekai/v-sekai-game is released as fully opensource.\n\n\n\n\niFire (he, him) — Today at 16:33 https://github.com/V-Sekai/v-sekai-game/pull/5 added caching to reduce doing nothing builds from 2 hours to 10 minutes ish\n\nNew contributors this week:\n@Malek Awesome for being around 🐱. Contributed to designs and cheering us when we succeed. Fixed the issue with the ci/cd with the recurse submodules. Too much to list!\n@gamethecupdog Helped us figured out some problems with AMD vr and V-sekai. We debugged the AMD VR launch issues and talked about fixing the vignette settings in the ui https://github.com/V-Sekai/V-Sekai.github.io/issues/378\n@meowses For supporting us and watching our presentation.\n@Kosyne For starting a topic about onboarding and our short term and long term planning.\n@! [P1-D3] Samuel Martin @Mr_Squarepeg Thanks for hanging out on Sunday, we chatted about V-Sekai and played a bit of ZeroK.\n\n\n\niFire (he, him) — Today at 12:34 Turned off the mesh mirror mode for avatars because of playtesting confusion.\nLyuma — Today at 13:04 makes sense. at some point we can add a mirror, and we need a map aligned at the right place, or a script added to maps which define where the ““mirrors”” are (there can be more than one since it’s just duplicating meshes which is cool)\niFire (he, him) — Today at 14:47 I added https://github.com/TokageItLab/realtime_retarget to V-Sekai’s godot engine c++ modules. Please test, @トカゲ is looking for feedback.\ntefusion’s gdextension addon https://github.com/tefusion/godot-subdiv is now published. https://godotengine.org/asset-library/asset/1488\niFire reorganized the development documentation site.\niFire is working on a bullet train kinetic novel https://github.com/V-Sekai-fire/INK_bullet_train world.\n\n\n\nUpdated this website to remove the left sidebar. Added headers to decisions and the changelog.\n\n\n\nGodot Engine proposal meeting rejected setting float=64 as default. However official 64 bit builds have interest.\n\n\n\nEarly morning discussion with guillefix, lyuma and fire.\nFeature requests from the community:\n\ndesktop capture\navatar ik\nquest support\n3d node graph system\nin-game content creation\nwasm for game scripting\n\n\n\n\nMeeting between betalars, fire, lyuma, jeana and others about usability in 3d games, convention application and V-Sekai.\n\n\n\n\n\n\nbetalars is working on making Chaos Computer Club more accessible.\nThere has been development to create an online-platform for Chaos Communication Congress using Godot\nIt is planned to be deployed in browser, limiting it to Godot 3 for now\nRealistically, the Congress Experience software will not be production-ready before Godot4, so starting with Godot 3 only sets us up for tech-debt and also makes cooperation with V-sekai impossible, so it was the wrong decision originally and is now being reverted.\nBased on limited contributors and also limited time, a Prototype in Godot 3 has been scrapped and betalars reached out to the V-Sekai team for some collaboration and humble contributions\n\n\n\n\n\nMilas needs to write a masters thesis on accessibility-driven Game-Development\nAt the end of December of each year, CCC holds a big conference, this year it is going to be a decentralized bunch of small-scale events due to the pandemic\niFire wants to be able to present meaningful progress by march 2023\n\n\n\n\n\nPretty much all goals align …\n\nMake it FOSS\nAllow for player interaction and expression in an online space\nMake 3D-level building accessible for players\nUse Godot Engine\nEncourage for tinkering and hacking (of the white-hat variety of course)\n\n… except for the fact, that online-chaos was developed for desktop browsers and not VR-Devices\nV-Sekai is engineering-driven and lacks in UX and Design, which betalars has more knowledge in, so there is potential for synergy\nIf this collaboration is successful, it would introduce the project into a big community of developers, some of which will be happy to contribute further code\n\n\n\n\n\nGetting distracted by shiny things\nThere’s currently limited interest in the chaos community at large and Betalars is still pretty junior in experience despite leading the effort of building an online-world\n\n\n\n\n\nAccessibility\n\nV-Sekai is interested in this subject, there’s an argument to be had, that XR has great potential for people with disabilities\n\nNot having to leave their flat for social interaction is a plus\nBeing able to choose to be stealth with a bodily disability\nMore intuitive controls with tracking\nHand tracking can be used for signing.\n\nEven for for visually impaired people, there are options to interact\nButtons\n\nRumble\nSound Feedback\nThere’s a lot of potential for work and research here, that would also benefit the godot-community by add-on development\n\n… and maybe by politely asking for some vital accessibility features to be pushed upstream\nConcrete Projects are:\n\nSubtitles\nIntroducing a Layer for alternate text / screen-reader Label3D\n\n\nLevel Generation\n\nCurrently there is a lot of interest in the community on this subject, as NeosVR, a project with great level-building UX, has been frozen\nGodot has a solid 3D-Level generator, that can be used by “power-users” to create 3D-Scenes\nExpanding its feature set could benefit the Godot Engine Community at large\nThere’s the need for intuitive tools for the average user to create cool stuff in 3D\n\nVoxel-Editors are a great first step, as they are an intuitive tool for blocking out 3D-shapes\nVoxel Editors can be extended with\n“Smart Voxel objects”, that can generate stuff like staircases, roofs, fences etc, that are a pain to block out within the voxel grid (and expanding the voxel grid)\n\n3D-Generators, that based on the existing mesh can build plants for instance\nConvenient Prop-Placement\n\n\n\nLevel Generation References\n\nEverQuest Next Landmark - Detail building tools\nCloud Gardens, a relaxing level building game\nDreams\ncrocotile3d.com\nMinecraft\n\nAI-Assisted Level Generation will probably also be a thing soon\nDesigning fun player-interaction Concepts\n\nBetalars would like to work on it, but it is hard\n\nMaking pretty Characters\n\nBetalars has been working on a sims-style character generator\nCurrent state can be found on gitlab\n\nHopefully will also benefit Godot Engine community\n\n\nDeveloping a Tablet-Mode for V-Sekai\n\nThere has been effort put into creating a Non-VR interaction mode\nCurrently it is pretty janky and not thought through\nBetalars would like to improve this\n\nFire’s V-Sekai priorities:\n\na better setting to be in\ncommunications between at least two people\nbetter character motion via constraints, spring bones, and animations\nbetter character models (betalars has a character creation system that they already developed as possible collaboration points)\n\n\n\n\n\ngithub.com/omigroup/ux-research\nThis is the new repo for the recently formed UX Research group in OMI. Check back weekly for updates on this repo and how to get involved. - GitHub - omigroup/ux-research: This is a new working group for OMIGroup\n\n\n\n\nMmmaellon’s work requires him to build an XR app using AWS Services. He wants to use that opportunity to make something that allows players to build maps collaboratively.\n\n\n\nASTC work for mobile gpu textures work."
   },
   {
-    "objectID": "changelog/2022/20220101-changelog.html#section",
-    "href": "changelog/2022/20220101-changelog.html#section",
-    "title": "V-Sekai Changelog - 2022-01",
+    "objectID": "changelog/2022/20221001-changelog.html#section",
+    "href": "changelog/2022/20221001-changelog.html#section",
+    "title": "V-Sekai Changelog - 2022-10",
     "section": "",
-    "text": "Switch proposal website to use https://quarto.org/.\nUpdated nomnoml diagrams."
+    "text": "Lyuma — 01/10/2022 I have pushed internal and external resource whitelisting at the ResrouceLoader (ResourceFormatLoaderBinary) level as a Godot engine patch.\n\nHere’s an example of what gets printed when the above script with OS.alert() attempts to be loaded\nERROR: user://asset_cache/81dd12d03686\n0a08faba06a1b47a3a29.scn:Resource of unrecognized type in file: GDScript.\n   at: load (core/io/resource_format_binary.cpp:789)\nERROR: Failed loading resource: user://asset_cache/81dd12d036860a08faba06a1b47a3a29.scn. Make sure resources have been imported by opening the project in the editor at least once.\nNote that I was forced to rebase to the latest build which includes the new build system (target=editor) most of the code I changed is in the private gitlab repo. once things stabilize and we get the build system up and running again, next step is to publish the remainder of the code on github\n\ngroups-4.x (and staging) were updated to latest. I attempted to update GoCD, but it’s a bit of a yolo merge, since a few pieces all had to be updated at once due to new scons target=editor argument we need to follow https://ci.v-sekai.cloud/ (log in as guest) and test the release builds\n\n\nexport builds are being created again with the new scons naming scheme. They seem to work on linux (steam deck) at least. Don’t have access to a windows machine right now"
   },
   {
-    "objectID": "changelog/2022/20220101-changelog.html#section-1",
-    "href": "changelog/2022/20220101-changelog.html#section-1",
-    "title": "V-Sekai Changelog - 2022-01",
+    "objectID": "changelog/2022/20221001-changelog.html#section-1",
+    "href": "changelog/2022/20221001-changelog.html#section-1",
+    "title": "V-Sekai Changelog - 2022-10",
     "section": "",
-    "text": "&lt;Lyuma&gt; Merged VR support (including OpenXR and the ability to create OpenVR as a plugin) into our godot engine build."
+    "text": "https://github.com/v-sekai/v-sekai-game is released as fully opensource."
   },
   {
-    "objectID": "changelog/2022/20220101-changelog.html#section-2",
-    "href": "changelog/2022/20220101-changelog.html#section-2",
-    "title": "V-Sekai Changelog - 2022-01",
+    "objectID": "changelog/2022/20221001-changelog.html#section-2",
+    "href": "changelog/2022/20221001-changelog.html#section-2",
+    "title": "V-Sekai Changelog - 2022-10",
     "section": "",
-    "text": "Material Maker was patched so that OpenEXR export don’t shift color channels in generated EXR file."
+    "text": "iFire (he, him) — Today at 16:33 https://github.com/V-Sekai/v-sekai-game/pull/5 added caching to reduce doing nothing builds from 2 hours to 10 minutes ish\n\nNew contributors this week:\n@Malek Awesome for being around 🐱. Contributed to designs and cheering us when we succeed. Fixed the issue with the ci/cd with the recurse submodules. Too much to list!\n@gamethecupdog Helped us figured out some problems with AMD vr and V-sekai. We debugged the AMD VR launch issues and talked about fixing the vignette settings in the ui https://github.com/V-Sekai/V-Sekai.github.io/issues/378\n@meowses For supporting us and watching our presentation.\n@Kosyne For starting a topic about onboarding and our short term and long term planning.\n@! [P1-D3] Samuel Martin @Mr_Squarepeg Thanks for hanging out on Sunday, we chatted about V-Sekai and played a bit of ZeroK."
   },
   {
-    "objectID": "changelog/2022/20221201-changelog.html",
-    "href": "changelog/2022/20221201-changelog.html",
-    "title": "V-Sekai Changelog - 2022-12",
+    "objectID": "changelog/2022/20221001-changelog.html#section-3",
+    "href": "changelog/2022/20221001-changelog.html#section-3",
+    "title": "V-Sekai Changelog - 2022-10",
     "section": "",
-    "text": "V-Sekai Changelog - 2022-12\nThis is the changelog for December 2022.\n\n\n2022-12-05\nRestored AEC3 to speech for echo cancellation.\n\n\n2022-12-06\nSome reorganization of the the V-Sekai-game issues and the proposal repository to move bugs to V-Sekai-game and enhancements to the proposal repository. Organized the issues and put some videos for some of them. The Japanese tokyo world bug with the 30 second lag between load was funny.\nMoved enhancements to https://github.com/V-Sekai/V-Sekai.github.io and bugs to https://github.com/V-Sekai/v-sekai-game/issues.\nGodot Speech now includes echo cancellation using WebRTC AEC3. Thanks iFire for adding it and getting it building. (some of the builds had issues but they should be resolved) .\n\n\n2022-12-12\nMMMaellon updated the V-Sekai game fov to 70.\nLyuma — Today at 00:34\nWe had an animation meeting with people in the Godot rocketchat.\nWe went through the issues in this list: https://docs.google.com/spreadsheets/d/16Al_PUHAUJE0S3XXtBpmA6MQIA_9sx57BXEisW1EAB0/edit#gid=0 Google Docs (Saracen / Lyuma / Fire / Tokage) A list of open issues/bugs/PRs th…\nPretty excited about some of these changes if they can get merged, especially the ability to extend and override AnimationNode classes, such as from a GDExtension plugin\nWe agreed to punt SkeletonModificationStack3D until 4.1. I think we will remove it from 4.0 because it is very buggy in its present state and there is not enough time to develop a good system for IK\n\n\n2022-12-15\n\n\n\noblique clipping plane for screenspace mirrors\n\n\n&lt;Lyuma&gt; Engine patch: https://github.com/V-Sekai/godot/tree/override_projection VR Demo branch based on Saracen’s code: https://github.com/V-Sekai/avatar_vr_demo/tree/screenspace_mirror It’s missing some of the newer changes but anyway that’s what I have."
+    "text": "iFire (he, him) — Today at 12:34 Turned off the mesh mirror mode for avatars because of playtesting confusion.\nLyuma — Today at 13:04 makes sense. at some point we can add a mirror, and we need a map aligned at the right place, or a script added to maps which define where the ““mirrors”” are (there can be more than one since it’s just duplicating meshes which is cool)\niFire (he, him) — Today at 14:47 I added https://github.com/TokageItLab/realtime_retarget to V-Sekai’s godot engine c++ modules. Please test, @トカゲ is looking for feedback.\ntefusion’s gdextension addon https://github.com/tefusion/godot-subdiv is now published. https://godotengine.org/asset-library/asset/1488\niFire reorganized the development documentation site.\niFire is working on a bullet train kinetic novel https://github.com/V-Sekai-fire/INK_bullet_train world."
   },
   {
-    "objectID": "changelog/2022/20220901-changelog.html",
-    "href": "changelog/2022/20220901-changelog.html",
-    "title": "V-Sekai Changelog - 2022-09",
+    "objectID": "changelog/2022/20221001-changelog.html#section-4",
+    "href": "changelog/2022/20221001-changelog.html#section-4",
+    "title": "V-Sekai Changelog - 2022-10",
     "section": "",
-    "text": "V-Sekai Changelog - 2022-09\n\n\n2022-09-05\ntefusion took iFire’s previous Godot Engine 3 branch and forward ported quad subdivision to an gdextension addon https://github.com/tefusion/godot-subdiv\nWe discuss with Reduz, Calinou and Lyuma about astc and limiting astc block size to 4x4, 8x8, and 12x12 block sizes. 4x4 was agreed on. Others have not yet.\n\n\n2022-09-06\nRestored Lillybyte’s https://github.com/godotengine/godot/pull/59675 Show the 3D transform gizmo in the center when otherwise offscreen work.\nGodot Engine astc block size agreed to be 4x4 and 8x8.\nSaracen’s Make auto-advance flag a requirement for conditional/expression evaluation with design amendments approved. https://github.com/godotengine/godot/pull/65312\nhttps://twitter.com/KenneyNL made a V-Sekai logo for us. https://twitter.com/KenneyNL/status/1567077172866596868?s=20&t=RIGyiux3A_KNX_HCLCVKvg\n\n\n2022-09-09\nhttps://github.com/Geequlim/ECMAScript/issues/131#issuecomment-1241570998 Javascript update.\nhttps://github.com/fire/ewbik Collaborated with Eron and Lyuma. Worked on the design of EWBIK bone weights and bone priority. Worked on the different bone rolls vs silhouette problem in regular 3d formats versus VRM which has a identity bone roll. (Use the original bone and then parent the change to be in ewbik bone roll.) Made the EWBIK solve less jello. Also discussion using kusudama constraints in Godot Engine core."
+    "text": "Updated this website to remove the left sidebar. Added headers to decisions and the changelog."
   },
   {
-    "objectID": "changelog/2022/20220301-changelog.html",
-    "href": "changelog/2022/20220301-changelog.html",
-    "title": "V-Sekai Changelog - 2022-03",
+    "objectID": "changelog/2022/20221001-changelog.html#section-5",
+    "href": "changelog/2022/20221001-changelog.html#section-5",
+    "title": "V-Sekai Changelog - 2022-10",
     "section": "",
-    "text": "Steamdeck test with V-Sekai.\nRestored image grid in V-Sekai content picking.\nWorking with the animation team to approve the skeleton animation retargeter.\nhttps://github.com/fire/geodesiac-path-on-mesh https://mindsdb.com/ https://github.com/godotengine/godot/pull/56902 https://github.com/KhronosGroup/glTF-Blender-IO/pull/1582.\nRestored wasd in V-Sekai build.\nAlso the last line also reduced the warning from 700 to around 8-30\nLast week improved openxr support but not yet locomotion.\nHand actions and triggers still bugged\nCollaboration with Khronos and Lucasfilm has added gltf principled pbr to materialx\nA static materialx baking importer has been added to a Godot Engine c++ master module\nAbandoned the work on webview because it required too much mingw hacking of windows calls. Should have worked in msvc still https://github.com/AcademySoftwareFoundation/MaterialX/issues/874\nWant to propose gltf specular and gltf volumetric to the godot engine rendering team\nWorked on an idea with Krsytof https://github.com/godotengine/godot-proposals/discussions/4226 to pin inspectors.\nFire collaborated with Tokage and Lyuma on the UIUX of a skeletal retargeting importer\nStarted a discussion on a train station stress test. https://github.com/godotengine/godot-proposals/discussions/4233\n\n\nOpenXR mode works!!!\nMade a skeleton retargeting demo.\n\n\n\n\n\nAdded a new audio effect to down-mix stereo audio to mono progressively. https://github.com/godotengine/godot/pull/58823\n\n\n\n\nAllow automatic lod when importing 3D scenes with Static Lightmaps https://github.com/godotengine/godot/pull/58548\nproductionize a clothing band / bracelet maker on 3d manifold-only meshes https://github.com/fire/geodesiac-path-on-mesh\nplay with a auto-ml thing that guesses floats, guesses classes and forecasts https://mindsdb.com/\nworking with the animation team to approve the skeleton animation retargeter. https://github.com/godotengine/godot/pull/56902\nconvinced the gltf blender maintainer it’s super easy to export pure 3d animations as gltf. https://github.com/KhronosGroup/glTF-Blender-IO/pull/1582"
+    "text": "Godot Engine proposal meeting rejected setting float=64 as default. However official 64 bit builds have interest."
   },
   {
-    "objectID": "changelog/2022/20220301-changelog.html#section",
-    "href": "changelog/2022/20220301-changelog.html#section",
-    "title": "V-Sekai Changelog - 2022-03",
+    "objectID": "changelog/2022/20221001-changelog.html#section-6",
+    "href": "changelog/2022/20221001-changelog.html#section-6",
+    "title": "V-Sekai Changelog - 2022-10",
     "section": "",
-    "text": "OpenXR mode works!!!\nMade a skeleton retargeting demo."
+    "text": "Early morning discussion with guillefix, lyuma and fire.\nFeature requests from the community:\n\ndesktop capture\navatar ik\nquest support\n3d node graph system\nin-game content creation\nwasm for game scripting"
   },
   {
-    "objectID": "changelog/2022/20220301-changelog.html#section-1",
-    "href": "changelog/2022/20220301-changelog.html#section-1",
-    "title": "V-Sekai Changelog - 2022-03",
+    "objectID": "changelog/2022/20221001-changelog.html#section-7",
+    "href": "changelog/2022/20221001-changelog.html#section-7",
+    "title": "V-Sekai Changelog - 2022-10",
     "section": "",
-    "text": "Added a new audio effect to down-mix stereo audio to mono progressively. https://github.com/godotengine/godot/pull/58823\n\n\n\n\nAllow automatic lod when importing 3D scenes with Static Lightmaps https://github.com/godotengine/godot/pull/58548\nproductionize a clothing band / bracelet maker on 3d manifold-only meshes https://github.com/fire/geodesiac-path-on-mesh\nplay with a auto-ml thing that guesses floats, guesses classes and forecasts https://mindsdb.com/\nworking with the animation team to approve the skeleton animation retargeter. https://github.com/godotengine/godot/pull/56902\nconvinced the gltf blender maintainer it’s super easy to export pure 3d animations as gltf. https://github.com/KhronosGroup/glTF-Blender-IO/pull/1582"
+    "text": "Meeting between betalars, fire, lyuma, jeana and others about usability in 3d games, convention application and V-Sekai."
   },
   {
-    "objectID": "changelog/2022/20220601-changelog.html",
-    "href": "changelog/2022/20220601-changelog.html",
-    "title": "V-Sekai Changelog - 2022-06",
+    "objectID": "changelog/2022/20221001-changelog.html#humble-contributions-and-places-to-start",
+    "href": "changelog/2022/20221001-changelog.html#humble-contributions-and-places-to-start",
+    "title": "V-Sekai Changelog - 2022-10",
     "section": "",
-    "text": "Updated this v-sekai.github.io website.\n\n\n\n\nHad a meeting with Lyuma, Fire, Sarcen, Silent and MMMaellon about the V-Sekai project.\nResolved apply style patches to 3d-audio.\nMake V-Sekai film tests with the new Godot Engine movie maker feature.\n\n\n\n\n\n\nFire collaborated on godot-snappy for object snapping https://github.com/jgillich/godot-snappy\nTry to integrate manifold again.\n\n\n\n\nhttps://gitlab.com/bramw/baserow/-/issues/998 Spent some documenting the baserow io system on Digital Ocean used to store in-progress art assets, data from research and 3d galleries.\nDonated research on avatar generation to the MIT-licensed project at https://github.com/AtlasFoundation/OpenCharacterCreator As part of: lightweight-quality-avatars\n\n\n\n\nLyuma uncommented some code in vsk_avatar/ik_space.gd to create IK tracking points on the server, to enable IK sync via server. TL;DR (Other peers can see other peers while connected to a server.)\nServer sync issue removed from todo list.\n\n\n\n\n\n\n\n\n\n\nid\nName\nNotes\nActive\n\n\n\n\n24\nVR smooth locomotion.\n\nTrue\n\n\n24\nVR smooth locomotion with blackout.\n\nTrue\n\n\n5\nGrab an object.\n\nTrue\n\n\n17\nSupport large uploads to the content distribution network.\n\nTrue\n\n\n19\nMake a video of entering the world and grabbing objects.\n\nTrue\n\n\n\nTrialing a fix for issue of SDFGI on VR. Was poor. Had to backout branch."
+    "text": "betalars is working on making Chaos Computer Club more accessible.\nThere has been development to create an online-platform for Chaos Communication Congress using Godot\nIt is planned to be deployed in browser, limiting it to Godot 3 for now\nRealistically, the Congress Experience software will not be production-ready before Godot4, so starting with Godot 3 only sets us up for tech-debt and also makes cooperation with V-sekai impossible, so it was the wrong decision originally and is now being reverted.\nBased on limited contributors and also limited time, a Prototype in Godot 3 has been scrapped and betalars reached out to the V-Sekai team for some collaboration and humble contributions\n\n\n\n\n\nMilas needs to write a masters thesis on accessibility-driven Game-Development\nAt the end of December of each year, CCC holds a big conference, this year it is going to be a decentralized bunch of small-scale events due to the pandemic\niFire wants to be able to present meaningful progress by march 2023\n\n\n\n\n\nPretty much all goals align …\n\nMake it FOSS\nAllow for player interaction and expression in an online space\nMake 3D-level building accessible for players\nUse Godot Engine\nEncourage for tinkering and hacking (of the white-hat variety of course)\n\n… except for the fact, that online-chaos was developed for desktop browsers and not VR-Devices\nV-Sekai is engineering-driven and lacks in UX and Design, which betalars has more knowledge in, so there is potential for synergy\nIf this collaboration is successful, it would introduce the project into a big community of developers, some of which will be happy to contribute further code\n\n\n\n\n\nGetting distracted by shiny things\nThere’s currently limited interest in the chaos community at large and Betalars is still pretty junior in experience despite leading the effort of building an online-world\n\n\n\n\n\nAccessibility\n\nV-Sekai is interested in this subject, there’s an argument to be had, that XR has great potential for people with disabilities\n\nNot having to leave their flat for social interaction is a plus\nBeing able to choose to be stealth with a bodily disability\nMore intuitive controls with tracking\nHand tracking can be used for signing.\n\nEven for for visually impaired people, there are options to interact\nButtons\n\nRumble\nSound Feedback\nThere’s a lot of potential for work and research here, that would also benefit the godot-community by add-on development\n\n… and maybe by politely asking for some vital accessibility features to be pushed upstream\nConcrete Projects are:\n\nSubtitles\nIntroducing a Layer for alternate text / screen-reader Label3D\n\n\nLevel Generation\n\nCurrently there is a lot of interest in the community on this subject, as NeosVR, a project with great level-building UX, has been frozen\nGodot has a solid 3D-Level generator, that can be used by “power-users” to create 3D-Scenes\nExpanding its feature set could benefit the Godot Engine Community at large\nThere’s the need for intuitive tools for the average user to create cool stuff in 3D\n\nVoxel-Editors are a great first step, as they are an intuitive tool for blocking out 3D-shapes\nVoxel Editors can be extended with\n“Smart Voxel objects”, that can generate stuff like staircases, roofs, fences etc, that are a pain to block out within the voxel grid (and expanding the voxel grid)\n\n3D-Generators, that based on the existing mesh can build plants for instance\nConvenient Prop-Placement\n\n\n\nLevel Generation References\n\nEverQuest Next Landmark - Detail building tools\nCloud Gardens, a relaxing level building game\nDreams\ncrocotile3d.com\nMinecraft\n\nAI-Assisted Level Generation will probably also be a thing soon\nDesigning fun player-interaction Concepts\n\nBetalars would like to work on it, but it is hard\n\nMaking pretty Characters\n\nBetalars has been working on a sims-style character generator\nCurrent state can be found on gitlab\n\nHopefully will also benefit Godot Engine community\n\n\nDeveloping a Tablet-Mode for V-Sekai\n\nThere has been effort put into creating a Non-VR interaction mode\nCurrently it is pretty janky and not thought through\nBetalars would like to improve this\n\nFire’s V-Sekai priorities:\n\na better setting to be in\ncommunications between at least two people\nbetter character motion via constraints, spring bones, and animations\nbetter character models (betalars has a character creation system that they already developed as possible collaboration points)\n\n\n\n\n\ngithub.com/omigroup/ux-research\nThis is the new repo for the recently formed UX Research group in OMI. Check back weekly for updates on this repo and how to get involved. - GitHub - omigroup/ux-research: This is a new working group for OMIGroup"
   },
   {
-    "objectID": "changelog/2022/20220601-changelog.html#section",
-    "href": "changelog/2022/20220601-changelog.html#section",
-    "title": "V-Sekai Changelog - 2022-06",
+    "objectID": "changelog/2022/20221001-changelog.html#section-8",
+    "href": "changelog/2022/20221001-changelog.html#section-8",
+    "title": "V-Sekai Changelog - 2022-10",
     "section": "",
-    "text": "Updated this v-sekai.github.io website.\n\n\n\n\nHad a meeting with Lyuma, Fire, Sarcen, Silent and MMMaellon about the V-Sekai project.\nResolved apply style patches to 3d-audio.\nMake V-Sekai film tests with the new Godot Engine movie maker feature."
+    "text": "Mmmaellon’s work requires him to build an XR app using AWS Services. He wants to use that opportunity to make something that allows players to build maps collaboratively."
   },
   {
-    "objectID": "changelog/2022/20220601-changelog.html#section-1",
-    "href": "changelog/2022/20220601-changelog.html#section-1",
-    "title": "V-Sekai Changelog - 2022-06",
+    "objectID": "changelog/2022/20221001-changelog.html#section-9",
+    "href": "changelog/2022/20221001-changelog.html#section-9",
+    "title": "V-Sekai Changelog - 2022-10",
     "section": "",
-    "text": "Fire collaborated on godot-snappy for object snapping https://github.com/jgillich/godot-snappy\nTry to integrate manifold again."
+    "text": "ASTC work for mobile gpu textures work."
   },
   {
-    "objectID": "changelog/2022/20220601-changelog.html#section-2",
-    "href": "changelog/2022/20220601-changelog.html#section-2",
-    "title": "V-Sekai Changelog - 2022-06",
+    "objectID": "changelog/2022/20220801-changelog.html",
+    "href": "changelog/2022/20220801-changelog.html",
+    "title": "V-Sekai Changelog - 2022-08",
     "section": "",
-    "text": "https://gitlab.com/bramw/baserow/-/issues/998 Spent some documenting the baserow io system on Digital Ocean used to store in-progress art assets, data from research and 3d galleries.\nDonated research on avatar generation to the MIT-licensed project at https://github.com/AtlasFoundation/OpenCharacterCreator As part of: lightweight-quality-avatars"
+    "text": "Migrated vsk_avatar and vsk_vrm_avatar_tool to import retargeter. There is still pending work to apply the 180 degree rotation during VRM import but we’re pretty close. Newly uploaded avatars should work, but after we fix the z-forward issue we may want to upload again.\n\n\n\nNothing to see here, got godot 4 engine updated to the latest master.\n\n\n\nMany changes to the Godot Engine 4 master retargeting and animation system were added."
   },
   {
-    "objectID": "changelog/2022/20220601-changelog.html#section-3",
-    "href": "changelog/2022/20220601-changelog.html#section-3",
-    "title": "V-Sekai Changelog - 2022-06",
+    "objectID": "changelog/2022/20220801-changelog.html#lyuma-04082022",
+    "href": "changelog/2022/20220801-changelog.html#lyuma-04082022",
+    "title": "V-Sekai Changelog - 2022-08",
     "section": "",
-    "text": "Lyuma uncommented some code in vsk_avatar/ik_space.gd to create IK tracking points on the server, to enable IK sync via server. TL;DR (Other peers can see other peers while connected to a server.)\nServer sync issue removed from todo list.\n\n\n\n\n\n\n\n\n\n\nid\nName\nNotes\nActive\n\n\n\n\n24\nVR smooth locomotion.\n\nTrue\n\n\n24\nVR smooth locomotion with blackout.\n\nTrue\n\n\n5\nGrab an object.\n\nTrue\n\n\n17\nSupport large uploads to the content distribution network.\n\nTrue\n\n\n19\nMake a video of entering the world and grabbing objects.\n\nTrue\n\n\n\nTrialing a fix for issue of SDFGI on VR. Was poor. Had to backout branch."
+    "text": "Migrated vsk_avatar and vsk_vrm_avatar_tool to import retargeter. There is still pending work to apply the 180 degree rotation during VRM import but we’re pretty close. Newly uploaded avatars should work, but after we fix the z-forward issue we may want to upload again."
   },
   {
-    "objectID": "changelog/2021/20210701-changelog.html",
-    "href": "changelog/2021/20210701-changelog.html",
-    "title": "V-Sekai Changelog - 2021-07",
+    "objectID": "changelog/2022/20220801-changelog.html#ifire-he-him-26082022",
+    "href": "changelog/2022/20220801-changelog.html#ifire-he-him-26082022",
+    "title": "V-Sekai Changelog - 2022-08",
     "section": "",
-    "text": "V-Sekai Changelog - 2021-07\n\n2021-07-30 23:27:44Z fire: Update https://github.com/V-Sekai/FBX2glTF/releases/tag/v2021-06-20T0053%2B0000 with a godot 4 project\n2021-07-30 23:27:32Z fire: Merged 3/5 prs related to gltf, colliders and RESET animation\n2021-07-28 23:15:15Z fire: https://github.com/godotengine/godot/pull/50964 Libcurl work from the net team\n2021-07-27 15:10:18Z fire: / https://cdn.discordapp.com/attachments/836651615532482611/869597574481449001/unknown.png\n2021-07-27 14:15:21Z fire: Working on CICD for https://github.com/V-Sekai/godot-hop-spin-dance as a preview for v-sekai 4\n2021-07-26 00:39:45Z fire: https://tenor.com/view/fun-lies-imlovingit-portal-itwouldbefuntheysaid-gif-4842907\n2021-07-26 00:22:35Z lyuma: ugly, but we do what we must\n2021-07-26 00:22:31Z lyuma: I was able to resolve autoload cycles by passing references by loading them in the right order, and passing in the out-of-order (cyclic) references as constructor arguments, referencing them with a prefix instead of the autoload name\n2021-07-26 00:21:40Z lyuma: There are still quite a few addons left, and then comes debugging\n2021-07-26 00:21:32Z lyuma: Made good progress on porting GDScript. I have most VSK* and sar1_ classes ported: https://cdn.discordapp.com/attachments/836651615532482611/869011521290764298/unknown.png\n2021-07-25 20:06:18Z fire: Worked with OMI to add OMI https://github.com/M3-org/awesome-metaverse/pull/4 to the list.\n2021-07-25 18:05:02Z Saracen: Nice!\n2021-07-25 18:00:45Z fire: Saracen Bugfix for _File. I’m able to open vrms again\n2021-07-23 20:10:25Z fire: https://cdn.discordapp.com/attachments/836651615532482611/868223549469511740/unknown.png\n2021-07-23 16:56:54Z fire: https://cdn.discordapp.com/attachments/836651615532482611/868174850005561374/unknown.png\n2021-07-23 16:56:33Z fire: https://twitter.com/MampelSkyliner Lyuma Trying to connect.\n2021-07-22 19:59:57Z fire: https://youtu.be/WBGkyqYEdTU From Mark Mandel\n2021-07-22 19:28:43Z fire: &gt; gizmo improvements are (finally) up for review 🙂 #50748\n2021-07-22 18:17:32Z fire: Did some research on ai planners. https://gist.github.com/fire/e5fd4fd3a943b76f3f1e4e76c305af0b\n2021-07-22 16:51:42Z fire: started moz hubs importer in godot engine master\n2021-07-22 16:42:11Z fire: collaborated with jonb on libcurl in Godot\n2021-07-22 00:05:41Z fire: OMI Meeting today. Debates are ongoing. No consensus.\n2021-07-20 18:29:32Z fire: Reduz wants to merge the real_t is double PRs soon. 🎆 🎆\n2021-07-20 00:01:16Z fire: Connected with https://twitter.com/lorenc_dan\n2021-07-19 23:21:35Z fire: https://github.com/KhronosGroup/glTF/pull/1955\n2021-07-19 23:01:08Z MMMaellon#2053 Have you guys messed with this engine before? Heard about it at work because Amazon made it https://o3de.org/ 👀 (1)\n2021-07-19 19:23:28Z fire: “&gt; iFire and I broke the ice, but feel this would be best served as a series of workshops together. We created this issue in the omigroup/gltf-extensions repo to track progress. https://github.com/omigroup/gltf-extensions/issues/3”\n2021-07-18 19:45:09Z Saracen: Put the Vket6 repo on GitLab. Right now, it’s just a straight port of the original, mostly making it work with Udon scripting, but I will explore changes which could be made for VKet6. https://gitlab.com/SaracenOne/vket6-vsk-booth/\n2021-07-16 17:41:08Z fire: Godot Networking meeting Saracen\n2021-07-15 23:45:34Z fire: Worked on glTF2 OMI_audio_emitter with humbletim\n2021-07-15 06:47:10Z Saracen: https://github.com/godotengine/godot/issues/50471\n2021-07-15 06:47:09Z Saracen: Logged this issue. Considering this one pretty crucial for V-Sekai’s 4.x port since the codebase heavily relies on dependent singletons\n2021-07-14 19:22:42Z fire: W3C - OMI GLTF extension working group created\n2021-07-14 19:22:23Z fire: https://cdn.discordapp.com/attachments/823417508417110026/864919725301432360/unknown.png\n2021-07-14 19:21:56Z fire: materialx pr merged\n2021-07-14 05:46:19Z fire: / /o/  ❤️ ❤️ ❤️ https://cdn.discordapp.com/attachments/836651615532482611/864744601017516042/unknown.png\n2021-07-14 03:32:32Z fire: https://cdn.discordapp.com/attachments/836651615532482611/864710936211750942/unknown.png\n2021-07-14 03:32:20Z fire: Saracen Lyuma We will be at this roundtable? https://cdn.discordapp.com/attachments/836651615532482611/864710886093619240/unknown.png\n2021-07-14 00:40:41Z fire: https://github.com/omigroup/OMI/issues/64 gltf2 proposal\n2021-07-13 21:05:10Z fire: Proposal for a materialx bsdf that works for gltf bsdf https://github.com/materialx/MaterialX/issues/653#issuecomment-879321877\n2021-07-13 12:18:26Z lyuma: Beware: autoload cycles are a problem: two files cannot reference each other without breaking the cycle in some way. Currently, I have about 7 references to EntityManager commented out from the network_manager addon, or else Godot hard crashes when loading the project.\n2021-07-13 12:16:42Z lyuma: “Pushed https://github.com/V-Sekai/godot-hop-spin-dance groups_test_project branch. The following addons now compile:\n\nentity_manager\ngd_util\ninput_manager\nmath_util\nmesh_combiner\nmodel_format\nnetwork_manager\nquentincaffeino-console\nsar1_log_manager\nstate_machine\nstatic_baker\nvsk_avatar (50% commented, must redo later)\nvsk_vrm_avatar_tool” ✨ (1)\n\n2021-07-13 02:01:04Z fire: Got static!\n2021-07-13 01:39:09Z fire: Can’t connect yet, but there’s less errors running\n2021-07-13 01:38:21Z fire: Worked on https://github.com/V-Sekai/godot_voip_experimental\n2021-07-11 21:54:33Z fire: https://github.com/V-Sekai/v-sekai-proposals/issues/34 Lyuma Wrote how to evaluate neural blendshapes\n2021-07-10 20:31:09Z fire: For next week I’m going to get a build of groupx-4.x to cicd and then start iterating on “Two person floating name tags in a networked Groups 4.x with the ability to pass beachballs”. I asked my friend gameplay programmer and we determined that waiting for all the things to port to Godot Engine 4 has a high latency. I’m trying a new approach of growing the code base feature by feature as it was done originally for 3.x.\n2021-07-10 20:22:34Z fire: Polishing https://github.com/godotengine/godot/pull/49645 for merge\n2021-07-09 21:04:20Z fire: Morning Meeting done with Reduz, Catania and Lyuma about Pose in 3d\n2021-07-07 18:40:06Z fire: Updated https://hackmd.io/C0oIi_vlRs6V8qa9ZCjxaw with the guessing “Blender edit” https://github.com/KhronosGroup/glTF-Blender-IO/pull/941\n2021-07-07 18:39:23Z fire: We talked about how “godot pose matcher” is an ok name for the tool\n2021-07-07 18:38:51Z Saracen: I’m going to try and build a test case for another bug in GodotPhysics and also start refactoring the avatar bone fixer from vsk_avatar into its own standalone addon with minimal dependencies.\n2021-07-07 18:38:31Z fire: Worked with tokage on bone rolls https://docs.google.com/spreadsheets/d/1j6Sq7-Iy_P3esTILySrqVQ91Hlq4MsEiI35X_R-NaiI/edit#gid=0\n2021-07-07 06:21:14Z fire: Merge pull request #50229 from reduz/fix-textures-not-updating Saracen Lyuma 👏 (2),pink (2)\n2021-07-07 06:01:10Z fire: https://cdn.discordapp.com/attachments/836651615532482611/862211623782711306/unknown.png\n2021-07-07 06:00:30Z fire: https://cdn.discordapp.com/attachments/598003845657788438/862209880990547968/fox_default_run.glb Fox is holding a leg.\n2021-07-07 05:59:29Z fire: https://github.com/godot-extended-libraries/godot-fire/tree/feature/bake-reset-anim Lyuma Saracen QA testing the RESET pose baker\n2021-07-06 18:11:18Z fire: Saracen was interested in my Hydro module.\n2021-07-06 18:11:02Z fire: Saracen and I were interested in GridMate interest management techniques\n2021-07-06 18:10:34Z fire: Evaluated o3de 1. GridMate as a college class !!!! 2. OIT (Transparency) 3. TressFX ??? 4. animation sync 5. behavior tree\n2021-07-05 21:07:53Z fire: “Did some work on physics collision bugs but didn’t complete. Sent to saracen. https://github.com/V-Sekai/godot/commit/99a9f79e25f7760cb5a0990e67545d78e9dd0423”\n2021-07-05 15:29:30Z fire: “I figured out the bug with the ewbik ui. need to separate the concept of the stored”“serialisable”” data vs the internal runtime data because the serialisable data can’t access the skeleton.”\n2021-07-03 23:41:32Z fire: worked with eron and also separately got the ik to not reset every solve on ewbik\n2021-07-02 07:14:33Z fire: https://github.com/materialx/MaterialX/pull/651 Standalone material baker\n2021-07-01 19:13:21Z fire: Vket6 booth summoning of discord here?!\n2021-07-01 15:35:11Z fire: Poked https://github.com/SigNoz/signoz/issues/193\n2021-07-01 14:48:52Z fire: Discussed with HumbleTim the concept of a source glb we run again as many individual solvers for the input data, if the input is solved and it passes QA, that is one that is the outputted.\n2021-07-01 14:22:16Z fire: https://github.com/materialx/MaterialX/issues/650#issuecomment-871921261\n2021-07-01 14:21:54Z fire: ThorVG now supports images! in svg"
+    "text": "Nothing to see here, got godot 4 engine updated to the latest master."
   },
   {
-    "objectID": "changelog/2021/20211101-changelog.html",
-    "href": "changelog/2021/20211101-changelog.html",
-    "title": "V-Sekai Changelog - 2021-11",
+    "objectID": "changelog/2022/20220801-changelog.html#トカゲ",
+    "href": "changelog/2022/20220801-changelog.html#トカゲ",
+    "title": "V-Sekai Changelog - 2022-08",
     "section": "",
-    "text": "iFire: Added https://github.com/V-Sekai/v-sekai-proposals/blob/master/CHANGELOG.md\niFire: Update FBX2glTF to create packaged release tags.\niFire: Wild goose chased godot 3.4 webxr. the goose flew away this time.\niFire: Evaluating Godot 4 for the web. 2D only. Builds in a bit from itch and cicd\niFire: I’ll be arranging the OMI gltf2 group meeting tomorrow. It’s currently wednesday. Need figure out what people are doing and reflect that.\niFire: https://github.com/godotengine/godot/pull/54886 Lyuma pr for blend i/o. Pending pr proposal. Discussed with the Godot Discord community and with Reduz.\nLyuma: the above is in reference to the .blend, .bvh (via bleneer) and .usdz (via blender) importers for Godor 4 and 3.3+\niFire: Ported and split the blender assisted addons into 6 branches and 3 repos\ntheoway: Visual script updates. https://github.com/godotengine/godot-proposals/issues/3548\niFire: Ventured into MaterialX slack channel and asked for answers. Answers were found.\nLyuma: Wrote a simple .bvh importer for Godot using @iFire [He/Him]’s blender importer as a base (importing using blender).\niFire: Onboarded a few people onto Godot 4 Groups from older versions\niFire: Finishing touches on blend import for Godot Engine\nLyuma: reworked scene export\n\n\n\niFire: Builds of fbx2gltf from github cicd are now at https://github.com/V-Sekai/FBX2glTF/releases\niFire: Updated the godot branch. There was some some difficult with the blend-io branch so I merged it with other branch import something\nMMMaellon: Didn’t we use to have an IK channel? Anyway here’s some of my ideas on how I plan to revamp RenIK. I’m still hoping that EWBIK takes over RENIK’s IK solving one day, so I’m focusing on improving the walk cycle and leaving IK solving alone https://mmmaellon.notion.site/Semi-Deterministic-Walk-Cycles-dbe1dcaa307e4fb9b85dd6ee920de20c\niFire — 07/11/2021: Groups update to the latest Godot. 1. intersect rays api changed. 2. misc crash if precondition fails return Oops forgot to upload a few branches.\niFire — 08/11/2021: https://github.com/V-Sekai/godot-blender Now works on my Linux. Need some testing for Windows and Mac. Save a blend file into the godot project and it’ll be openable as scene through tricks.\niFire — 08/11/2021: Will be around in voice call for an 30m to 1 hour.\niFire — 09/11/2021: Cleared some godot engine github backlog. Wheeee\niFire: Mixer bug fixes have been merged https://github.com/ubisoft/mixer\n\n\n\n\n\n\nAdded a change log\n2021-11-03 21:01:24Z fire: iFire Reviewed Visual Script work prs https://github.com/godotengine/godot/pull/54564 https://github.com/godotengine/godot/pull/52218"
+    "text": "Many changes to the Godot Engine 4 master retargeting and animation system were added."
   },
   {
-    "objectID": "changelog/2021/20211101-changelog.html#z",
-    "href": "changelog/2021/20211101-changelog.html#z",
-    "title": "V-Sekai Changelog - 2021-11",
+    "objectID": "changelog/2022/20221101-changelog.html",
+    "href": "changelog/2022/20221101-changelog.html",
+    "title": "V-Sekai Changelog - 2022-11",
     "section": "",
-    "text": "Added a change log\n2021-11-03 21:01:24Z fire: iFire Reviewed Visual Script work prs https://github.com/godotengine/godot/pull/54564 https://github.com/godotengine/godot/pull/52218"
+    "text": "v-sekai-game-bug\n\n\n\n\n\nopenxr_showing\n\n\nRestored V-Sekai-Game home.\nWorked on EWBIK as a git branch.\n\n\n\nGame releases are working again.\n\n\n\nV-Sekai-game Player spawning should be working again (see their name tag at least). There’s an issue with the default sky_celebration map caused by “TestEntity” which has scene_file_path==“” and that breaks the validation logic, preventing the player from spawning, and most default maps don’t work. You need to use Mobile Dragon Shop (very dark) or Tokyo Map\nNote that avatars are currently not working. I think I’m getting closer to identifying where the validation is causing trouble.\n\n\nWe are working on a v2 of the network architecture based on Godot’s network spawn & sync system, so a lot of the code I’m editing right now is kind of legacy at this point. The new network implementation should drastically simplify the code and eliminate dozens of complex GDScript files from being needed. I still want to get this demo stable, since we will still be using the player controller and avatar loader from it\n\n\n\nVSK Tokyo Map\n\n\nThe new v2 network demo can be found at https://github.com/V-Sekai/net_demo if you’re curious. There’s no VR support planned for net_demo, but it should serve as a strong foundation going forward.\nAvatars should show up again. There was some code mistake that triggered only when the default “mirror” was disabled and caused avatars not to instantiate, but I didn’t notice because I had turned it on in my checkout\nI also fixed the default sky celebration map\nAvatar bone rotations are currently broken with this setup. Seems like the head always faces a certain direction:\n\n\n\nAvatar bone rotations are broken"
   },
   {
-    "objectID": "changelog/2021/20210801-changelog.html",
-    "href": "changelog/2021/20210801-changelog.html",
-    "title": "V-Sekai Changelog - 2021-08",
+    "objectID": "changelog/2022/20221101-changelog.html#section",
+    "href": "changelog/2022/20221101-changelog.html#section",
+    "title": "V-Sekai Changelog - 2022-11",
     "section": "",
-    "text": "V-Sekai Changelog - 2021-08\n\n2021-08-31 23:04:24Z fire: Did a few hours of work learning Blender with Cleam last night. Did some testing of Tokage’s skeleton gizmo.\n2021-08-30 17:09:35Z MMMaellon#2053 nice\n2021-08-30 16:13:28Z Saracen: Got MMMaellon’s RenIK system compiling for 4.x now. It’s also worth noting that the new SkeletonModifierStack is now mainlined in 4.0, so my next task with this will be to port RenIK to using this system. The final step will be porting it to the new GDExtension system as that becomes more viable\n2021-08-30 02:31:12Z fire: updated our engine + AUTHORITY changes + libcurl\n2021-08-28 22:01:33Z fire: Left is blend shape / right is bones. https://cdn.discordapp.com/attachments/836651615532482611/881297479033827388/2021-08-28_15-00-45.mp4\n2021-08-28 21:52:02Z fire: I got dembones working. ./DemBones -i=\"Face_Geom.fbx\" -a=\"Face_Anim.abc\" --bindUpdate=2 -o=\"Decomposition_20_grouped_face.fbx\" --nnz=8 -b=256 Note that the corresponding fbx is 0.01 scale while the alembic is in meters. The RMSE = 0.00433256 must be this low. Especially do not pass DemBones if the RMSE is like 3.5. Next thing is to integrate an existing 3d skeleton.\n2021-08-28 21:28:03Z fire: Jonbonazza said he resolved the ipv6 dns problem and the last remaining steps are to get to build for all platforms. Details for a future iFire.\n2021-08-28 06:24:28Z fire: https://twitter.com/mux213/status/1431474082885734403?s=20 🥽 (2)\n2021-08-27 23:20:23Z fire: troubles\n2021-08-27 23:20:17Z fire: Restoring spatial audio after ellenhp’s pr\n2021-08-27 14:15:31Z fire: https://cdn.discordapp.com/attachments/836651615532482611/880817809737805824/image0.jpg\n2021-08-27 09:17:32Z fire: https://cdn.discordapp.com/attachments/836651615532482611/880742820812562432/unknown.png\n2021-08-27 09:10:49Z fire: https://github.com/godotengine/godot/pull/51985\n2021-08-27 08:26:02Z lyuma: hosting seems to kind of work but plays constant physics sounds, so it’s likely that scenes are loading, but I can’t see anything.\n2021-08-27 08:23:56Z lyuma: Made some further progress: https://cdn.discordapp.com/attachments/836651615532482611/880729330035077120/unknown.png pink (2)\n2021-08-27 05:35:53Z lyuma: we do things because they are crazy\n2021-08-27 05:35:15Z fire: https://pbs.twimg.com/media/E3OC-r7WQAUvy5l.jpg ⬆️ (1)\n2021-08-27 05:26:19Z lyuma: https://cdn.discordapp.com/attachments/836651615532482611/880684632553705482/unknown.png\n2021-08-27 01:43:10Z fire: https://github.com/ValveSoftware/openvr/tree/master/samples/helloworldoverlay steam overlay\n2021-08-26 20:20:03Z fire: https://thume.ca/2017/06/17/tree-diffing/ useful comparing two visual script trees or two godot engine scenes or maybe skeletons!?s\n2021-08-26 19:21:48Z lyuma: Quilkin thread\n2021-08-26 16:01:57Z fire: https://medium.com/embarkstudios/say-hi-to-quilkin-an-open-source-udp-proxy-88577c795204\n2021-08-26 14:36:54Z fire: https://cdn.discordapp.com/attachments/836651615532482611/880460804351205386/image0.jpg\n2021-08-26 11:44:22Z lyuma: With the Autoload ordering fix applied, groups client now gets to the loading bar and is able to fade out after loading some plugins, but ends up at a black screen without showing the menu screen.\n2021-08-26 10:07:46Z lyuma: “Write PR to fix Autoload sort order (e.g. at runtime) https://github.com/godotengine/godot/pull/52122”\n2021-08-26 01:30:05Z fire: Got together with CLEAM and got a schedule to work on Blender artwork. First thing is teach ourselves how to make a Virtual Market quality character. https://cdn.discordapp.com/attachments/836651615532482611/880262796661624912/Artboard-11.png 👍🏿 (2)\n2021-08-24 16:56:46Z Saracen: https://github.com/godotengine/godot/pull/52071 gddab (3)\n2021-08-24 16:56:45Z Saracen: GDScript 2.0 bug fixes\n2021-08-24 16:10:48Z fire: https://cdn.discordapp.com/attachments/836651615532482611/879759658393403402/unknown.png\n2021-08-24 16:07:44Z fire: MaterialX gltf2 bake with https://github.com/fire/MaterialX/tree/standalone-gltf https://cdn.discordapp.com/attachments/836651615532482611/879758889032253501/unknown.png\n2021-08-24 15:47:33Z fire: draft of materialx spec written https://github.com/fire/glTF/tree/materialx and draft of stand alone baker https://github.com/fire/MaterialX/tree/standalone\n2021-08-23 16:44:55Z fire: Spent some time trying to bake the animations of the face going from 0 to 1 for Angry face on three_girl vrm and dem bones could not work. Bake blend shapes to skeletal animation. Did not succeed.\n2021-08-22 07:59:23Z fire: remotes/bruvzg/msdf_fonts2\n2021-08-20 19:09:33Z fire: https://github.com/godotengine/godot/pull/44399\n2021-08-20 19:08:25Z fire: https://github.com/vnen/godot-cpp/tree/gdnative-extensions\n2021-08-20 08:30:17Z fire: https://github.com/godotengine/godot/pull/51908 new MSDF Branch\n2021-08-19 15:58:27Z fire: https://cdn.discordapp.com/attachments/836651615532482611/877944612508008468/2021-08-19_08-57-17.mp4\n2021-08-19 15:37:58Z fire: https://user-images.githubusercontent.com/7645683/109620721-debe3f00-7b42-11eb-870b-c2207812a03f.mov\n2021-08-19 15:33:20Z fire: Testing MSDF branch 2 https://github.com/bruvzg/godot/tree/msdf_fonts2.\n2021-08-16 15:03:26Z fire: Nikumaru font: https://cdn.discordapp.com/attachments/836651615532482611/876843603413069884/unknown.png\n2021-08-16 14:36:27Z lyuma: Including 3d modifier?? ⭐ (2),gdbee (2),🍦 (2),🔥 (2)\n2021-08-16 14:04:39Z fire: ik 3d is merged!!!!!\n2021-08-14 00:04:31Z fire: Updated https://github.com/fire/looking-glass/ Godot Engine demo. The fix was making the app fullscreen\n2021-08-14 00:00:04Z fire: Connected with Emili Yu https://ns.inria.fr/d3/CASSIE/\n2021-08-13 23:59:33Z fire: Connected with FreeMocap https://twitter.com/JonMatthis\n2021-08-13 06:07:51Z lyuma: “&gt; It’s coming! The Virtual Market 6 will commence in 18 hours! &gt; The opening ceremony will be held on JST 9:30 am, UTC 0:30 am, Eastern 8:30 pm. &gt; https://www.youtube.com/watch?v=XrTj_-Yg7AA”\n2021-08-13 04:21:30Z fire: https://twitter.com/Lyuma2d/status/1426005291573813249?s=20\n2021-08-11 22:48:18Z fire: https://twitch.tv/freemocap Jon’s gonna stream tomorrow, Thursday from roughly 4-6pm (Eastern US time)\n2021-08-11 15:37:36Z fire: For cloud and edge computing, made an iso that’ll automatically install k3s with proper keying if we reboot once manually to remove the iso. https://github.com/V-Sekai/k3s-auto-start-gitops\n2021-08-10 22:56:35Z Saracen: Looking into this right now (https://github.com/godotengine/godot/issues/47885), discussion will be on RocketChat #scripting\n2021-08-10 19:47:41Z lyuma: Congrats!!\n2021-08-10 19:47:30Z fire: https://github.com/godotengine/godot/pull/49343/files merged 👏 (2)\n2021-08-05 06:51:43Z MMMaellon#2053 that’s very exciting hype (3),gdhollidays (2)\n2021-08-05 06:31:39Z lyuma: but this is a huge milestone for us: we can now open the project cleanly and fix stuff\n2021-08-05 06:31:02Z lyuma: Groups project now opens on Godot 4 without errors! We’re still getting a few script errors here and there while exporting, and we see some issues related to loading openvr; and a godot bug related to extending a “res://” url might be affecting exports\n2021-08-05 02:16:43Z lyuma: We’re still missing ports of GDNative code: godot speech and open?r\n2021-08-05 02:16:04Z lyuma: Finished with the majority of the port of 430 gdscript files. We have builds running, though godot4 has bugs in export builds with preload() of tscn files so I’ll try changing those to regular load()\n2021-08-05 01:14:44Z lyuma: V-Sekai in godot 4 is getting my avatars! https://cdn.discordapp.com/attachments/836651615532482611/872648788672647208/unknown.png vrcExclaim (1)\n2021-08-04 18:52:42Z fire: Wasm emulation of fedora 33 via RISCV64. Related to Stellar Mesh discussion. https://cdn.discordapp.com/attachments/836651615532482611/872552648182751252/unknown.png\n2021-08-04 13:19:32Z fire: Trialing new github actions for all of our modules\n2021-08-02 22:17:37Z fire: Next year Siggraph is in Vancouver 🇨🇦\n2021-08-02 20:45:24Z fire: https://cdn.discordapp.com/attachments/836651615532482611/871856235098562621/unknown.png\n2021-08-02 20:14:08Z lyuma: Siggraph 2021 is the week of August 9 - August 13\n2021-08-02 19:48:01Z fire: Siggraph 2021! invited to discord\n2021-08-02 05:49:11Z fire: Worked on gltf2 export in Godot Engine master\n2021-08-02 05:48:57Z fire: Worked with Nikitalita on visual regression testing of vulkan"
+    "text": "v-sekai-game-bug\n\n\n\n\n\nopenxr_showing\n\n\nRestored V-Sekai-Game home.\nWorked on EWBIK as a git branch."
   },
   {
-    "objectID": "changelog/2021/20211001-changelog.html",
-    "href": "changelog/2021/20211001-changelog.html",
-    "title": "V-Sekai Changelog - 2021-10",
+    "objectID": "changelog/2022/20221101-changelog.html#section-1",
+    "href": "changelog/2022/20221101-changelog.html#section-1",
+    "title": "V-Sekai Changelog - 2022-11",
     "section": "",
-    "text": "V-Sekai Changelog - 2021-10\n\n2021-10-31 19:30:30Z fire: https://twitter.com/reduzio/status/1454867881771024391?s=20\n2021-10-31 17:12:51Z fire: Instruction unclear. Hair stuck in gentle breeze. https://github.com/fire/TressFX-OpenGL See releases for a zip. https://cdn.discordapp.com/attachments/836651615532482611/904417650510295060/2021-10-31_10-09-56.mp4\n2021-10-31 04:08:23Z fire: Confirmed fixed my screenshots system.\n2021-10-30 18:18:28Z fire: :danceblob:\n2021-10-30 18:17:58Z fire: aha. yes. https://github.com/godotengine/godot/pull/54427\n2021-10-30 17:59:04Z fire: Restored theme generator for groups. [reverted to editor theme] Needs time to debug.\n2021-10-30 06:03:59Z fire: Early builds are testable\n2021-10-30 02:20:34Z lyuma: “The VRM avatar converter has been updated at https://github.com/V-Sekai/vsk_vrm_avatar_tool and made to work with the new rotation/scale/blend_shape tracks. (generated scenes duplicate all resources, so make sure to not save as”“.tscn”“)” https://cdn.discordapp.com/attachments/836651615532482611/903830713009311754/unknown.png\n2021-10-29 23:28:11Z fire: Character translation movement now works. [WASD]\n2021-10-29 20:59:18Z fire:  HungryProton pushed the beginning of the 4.0 port to the refactoring-4.0 branch\n2021-10-29 16:02:35Z fire: From Mux and related to Godot XR This is so much fun: https://youtu.be/UxZj8OOCgY4\n2021-10-29 01:42:32Z lyuma: Here’s a video showing multiple players moving around over the network! and made it right side up by not calling set_vflip(true)! https://cdn.discordapp.com/attachments/836651615532482611/903458754262089728/vsekaimultiplayer_2021-10-28.mp4 🎉 (1)\n2021-10-29 01:26:17Z lyuma: “We might all be in error avatars, and the world might be upside down….. But. We have networking!!! (This is the first time we’ve successfully made a multiplayer connection on Godot 4 pre-alpha with Vulkan!)” https://cdn.discordapp.com/attachments/836651615532482611/903454660243894352/unknown.png\n2021-10-28 09:40:10Z lyuma: https://media.discordapp.net/attachments/659137056991346708/903093451560714280/unknown.png\n2021-10-27 19:54:44Z fire: Checked material settings Lyuma. Pushed the updates.\n2021-10-27 18:22:01Z fire: Lyuma ninja and ccache oh my. https://github.com/V-Sekai/godot/tree/ninja-ccache Based on work by dmoody256\n2021-10-27 16:31:59Z fire: Great work humbletim https://github.com/omigroup/omi-blender-gltf/pull/1\n2021-10-27 01:47:49Z fire: I un-archived HungryProton’s work, made a build and duplicated some trash cans. https://cdn.discordapp.com/attachments/836651615532482611/902735304228737094/unknown.png\n2021-10-25 19:59:28Z fire: Rotation mode pr merged. https://github.com/godotengine/godot/pull/54222 Lod added 🦎 (1)\n2021-10-25 12:23:37Z fire: Openvr update from mux\n2021-10-25 06:39:34Z lyuma: Updated some more scripts to work with the latest engine. the groups demo is still pink with looping physics sounds, though moving the mouse appears to pan the audio, so there’s something moving somewhere\n2021-10-24 01:37:02Z fire: “followed up on a design for duplicated blendshapes Lyuma korewaChino EIREXE https://github.com/godotengine/godot/issues/54062”\n2021-10-24 01:21:56Z fire: Tested animation compress. was a bit slow\n2021-10-24 01:12:26Z fire: Moved key-frame reduce to 4.0 but it still has fiddly test cases. Don’t want to debug, but leaving it here. https://github.com/V-Sekai/godot/commits/keyframe-reduce Dropping it.\n2021-10-23 15:25:29Z fire: https://twitter.com/smallseasonsbot/status/1451929853565890563?s=20\n2021-10-23 08:08:18Z fire: https://cdn.discordapp.com/attachments/836651615532482611/901381505526415360/unknown.png\n2021-10-23 06:18:32Z fire: sync with samsung thorvg team need pr review about paint replacement through iteration for color replacement\n2021-10-23 01:48:51Z fire: Got godot speech C++ module to compile. At some point in the future need to try uncompressed audio after the api changes. There’s a test project. 🗣️ (2)\n2021-10-23 00:36:32Z fire: Extracting godot-speech into a C++ module\n2021-10-23 00:25:44Z fire: Lyuma told me about this tool. So cleaned it a bit https://github.com/V-Sekai/V-Sekai-Blender-tools/tree/main/addons/ApplyModifierForObjectWithShapeKeys\n2021-10-21 03:27:13Z lyuma: fire made a lot of progress debugging the frame lag and random hangs. we have mitigations for some issues, but might not be fully correct\n2021-10-20 07:26:46Z fire: VERY POOR 1 FRAME STUTTER Got the sample working with our own build of the openvr gdextension. https://github.com/V-Sekai/v-sekai-openvr-sample/releases/tag/v0.2 Includes the godot 4 editor.\n2021-10-18 16:33:47Z fire: https://deepmind.com/blog/announcements/mujoco\n2021-10-18 13:59:41Z fire: mux offers to send his working openvr as an archive. He found some bugs with exporting gdextensions\n2021-10-18 05:26:43Z fire: cyberpunkmermaid#6171 interested in clothing for avatars at omigroup\n2021-10-17 01:02:32Z fire: https://github.com/ubisoft/mixer/pull/27\n2021-10-17 01:01:54Z fire: Debugged why mixer crashes on 2.93 did not fix but worked around\n2021-10-16 02:52:17Z fire: I am satisfied. Found the bug. https://github.com/godotengine/godot/pull/53865\n2021-10-16 00:33:27Z fire: What can we do to speed up our processes? https://scattered-thoughts.net/writing/speed-matters/\n2021-10-16 00:22:51Z lyuma: Updated Unidot Importer to work with latest master. Godot has gotten quite a lot faster it feels like\n2021-10-15 23:05:50Z fire: https://github.com/godotengine/godot/pull/53821#issuecomment-944785300\n2021-10-15 22:29:11Z fire: “https://github.com/V-Sekai/godot-4-animation-vrm-sample\n\nCurrently the root motion is on the hips and not on the root bone so it’s a bit funny”\n\n2021-10-15 22:22:01Z lyuma: “Rumors of a Godot 4 alpha are beginning to emerge. From Akien: &gt; New 4.0 build which is not alpha yet hohoho https://downloads.tuxfamily.org/godotengine/testing/4.0/4.0-dev.20211015/\n\nSome hints that it could be ““a few days more to mature”” beyond ““this week”” so there’s a chance of next week even!”\n\n2021-10-15 14:10:43Z fire: https://github.com/godotengine/godot/pull/53833 📽️ (1),🎞️ (1),🧹 (1)\n2021-10-15 01:33:14Z fire: https://github.com/godotengine/godot/issues/53823 Saracen PREVIEWS ARE FIXED 🔥 👍 (2)\n2021-10-14 15:08:32Z fire: Watching https://vive.com event.\n2021-10-14 14:12:59Z fire: Typed a plan for EWBIK work https://github.com/godot-extended-libraries/ewbik/issues/6\n2021-10-13 11:49:07Z fire: Worked on トカゲ VRM-like rotational rest pose baking https://github.com/V-Sekai/godot/tree/bake-rests\n2021-10-13 11:03:55Z fire: Skeleton split transform 3d merged from reduz\n2021-10-13 09:20:44Z fire: Updated Lyuma https://github.com/V-Sekai/godot/tree/groups-4.x-remove-separate-gltf-bake\n2021-10-13 04:57:28Z fire: Updated https://github.com/V-Sekai/godot/tree/rot-interpolate\n2021-10-12 10:54:44Z fire: Akien mentioned libacktrace\n2021-10-11 18:46:53Z lyuma: “Spent all day researching nonunknown’s negative scale issue: https://github.com/godotengine/godot/pull/53642#issuecomment-940357171 I think I have a pretty good understanding of why it breaks in Godot (except cull_back meshes) and what solutions are possible/feasible.”\n2021-10-11 15:57:30Z fire: https://cdn.discordapp.com/attachments/836651615532482611/897150929911021619/unknown.png\n2021-10-11 15:03:44Z fire: Updated blockmesh models https://github.com/V-Sekai/art-blue-tin-fox-models/releases/tag/latest. Edited: Incorrect export. Exported again.\n2021-10-11 13:24:24Z fire: Restored compilation of lasso.\n2021-10-11 12:56:20Z fire: Today’s Godot Engine build tag https://github.com/V-Sekai/godot/releases/tag/groups-4.x.2021-10-11T123723Z\n2021-10-10 22:50:47Z fire: https://cdn.discordapp.com/attachments/836651615532482611/896892548528889896/unknown.png\n2021-10-10 22:48:25Z fire: Trialing windows 11 and WSL for CUDA on windows. It works\n2021-10-10 22:48:09Z fire: Silent Sure, at least the permission to use them and if it’s not too much effort.\n2021-10-10 10:18:21Z Silent#0264 Do you want the source text?\n2021-10-09 23:24:05Z fire: Lyuma EIREXE https://www.kickstarter.com/projects/lookingglass/looking-glass-portrait with https://github.com/CaptainProton42/GodotHoloPlay https://cdn.discordapp.com/attachments/836651615532482611/896538541402783774/unknown.png\n2021-10-09 18:21:42Z fire: Silent Trying to create your list of CC0, CC-BY avatars https://cdn.discordapp.com/attachments/836651615532482611/896462441221877790/unknown.png\n2021-10-09 18:20:55Z fire: Creating a list of VRM checking conditions. https://cdn.discordapp.com/attachments/836651615532482611/896462244378996756/unknown.png\n2021-10-08 17:31:13Z fire: https://twitter.com/smallseasonsbot/status/1446491101490081802?s=20\n2021-10-08 17:01:37Z fire: Does not support blend shapes in bake, but does in player.\n2021-10-08 17:00:47Z fire: See addons/miku_motion_bake/readme.md for instructions\n2021-10-08 17:00:26Z fire: Been working on baking from VMD to VRM. Promising. https://github.com/V-Sekai/MikuMotionVSekai\n2021-10-07 07:42:12Z fire: “youwin — Yesterday at 21:03 started work on an obs &lt;-&gt; godot integration using obs-websocket. Might be useful for tutorial makers or recording short demo clips of your game without requiring too much editing https://github.com/you-win/obs-websocket-gd” 👀 (3),👍 (1)\n2021-10-06 20:26:41Z fire: Notes from GDC - Genshin Impact: Building a Scalable AI System humbletim https://hackmd.io/SPqekctOQYS5vQ7w7glJ5A\n2021-10-06 20:10:50Z fire: https://github.com/godotengine/godot-proposals/issues/3394 reduz wrote a proposal for ellenhp\n2021-10-06 20:07:47Z fire: Decreasing GLB (probably VRM) sizes https://forum.playcanvas.com/t/tricks-to-decrease-morph-target-sizes/18628/9?u=chris\n2021-10-06 19:51:03Z fire: Trialing https://v-sekai.budibase.app Lyuma\n2021-10-06 19:34:12Z fire: Discussed with Ob5vr about blend shape baking. TODO: Get some GDC courses from The Last of Us Part 2 on SSD techniques.\n2021-10-06 19:21:20Z トカゲ: “Marged Skeleton Gizmo 🎉 https://github.com/godotengine/godot/pull/45699” gdhearteyes (1),PartyParrot (2),mikuleek (1),SkellyDance (1)\n2021-10-06 19:17:15Z fire: https://github.com/godotengine/godot/pull/53298\n2021-10-06 19:05:46Z fire: Also to bake blend shapes.\n2021-10-06 19:05:37Z fire: The goal is to remove the dem bones repo is remove FBX and ABC dependencies\n2021-10-06 19:04:50Z fire: https://github.com/V-Sekai/godot-dem-bones/tree/godot working on it for a few hours\n2021-10-06 19:01:30Z fire: Still working on a summary of UIUX proposals. https://hackmd.io/26BUnwWOSYuMFIvvpoLa5Q\n2021-10-06 13:18:17Z fire: https://github.com/godotengine/godot/pull/53473 Lyuma トカゲ 🆗 (1)\n2021-10-05 07:01:01Z fire: https://cdn.discordapp.com/attachments/836651615532482611/894841592505069599/unknown.png pog (2),😍 (2)\n2021-10-05 06:50:22Z lyuma: we can chat more about this in #server-backend\n2021-10-05 06:44:14Z fire: https://twitter.com/JenMsft/status/1445065715698962442?s=20\n2021-10-05 04:55:21Z fire: Donmcurdy chat about materialx in omigroup’s gltf extensions discord for a few hours ❤️ (2),👏 (2)\n2021-10-04 17:03:45Z fire: GLTF2 Document merged.\n2021-10-04 08:21:47Z lyuma: トカゲ let’s move this to #animation … but basically there are three different proposals from Reduz.\n2021-10-04 08:21:42Z トカゲ: So it should not support A pose -&gt; T pose\n2021-10-04 08:21:02Z トカゲ: If I understand correctly from my discussion with reduz, this implementation is pretty similar to the global transform in MMD\n2021-10-04 08:18:08Z lyuma: I believe this proposal is sort of a generalization of the retargeting system you might find in Unity, without going into specifics on the implementation of the retargeting: what Reduz calls a “Retargeter” is what you would call an “Avatar” in Unity.\n2021-10-04 08:15:31Z lyuma: “Reduz made a new proposal related to Animations: https://github.com/godotengine/godot-proposals/issues/3379”\n2021-10-04 05:35:48Z fire: https://github.com/godotengine/godot/pull/50964 Updated libcurl. Ready for merging.\n2021-10-04 01:59:46Z fire: Branch created https://github.com/V-Sekai/godot/tree/remove-skeleton-ik-3d\n2021-10-03 19:51:15Z fire: https://www.campaign.viveport.com/step-into-catart\n2021-10-03 19:49:11Z fire: https://autodesk-forks.github.io/MaterialX/ materialx web viewer\n2021-10-03 19:48:47Z fire: https://cdn.discordapp.com/attachments/836651615532482611/894310029715464262/unknown.png\n2021-10-03 05:35:20Z lyuma: This isn’t really a discussion channel so I’ll continue in #server-backend\n2021-10-03 04:37:57Z fire: v-sekai.org’s ssl cert will expire in 2 days\n2021-10-02 19:26:59Z fire: https://github.com/godotengine/godot/pull/53337 merged\n2021-10-02 16:51:51Z fire: Need to a tech limits design. The Last of Us Part II Abby has a total joint count of 1075 Animated - 520 (includes face) and 555 procedural.\n2021-10-02 16:34:45Z fire: “Everything is back to working. Yesterday everything broke ref: meshes disappeared and crash with skeleton because minimum verts. Fixes from Lyuma. Also tested occlusion culling”\n2021-10-02 14:35:34Z fire: Lyuma The platform creator of Tokyo Game Show 2021 liked my post. https://cdn.discordapp.com/attachments/836651615532482611/893868818038915132/unknown.png\n2021-10-02 12:52:57Z Saracen: Cool, I’ll read through it later today\n2021-10-02 12:48:43Z lyuma: “Saracen fire New proposal by reduz for animation import without bone rest pose: https://github.com/godotengine/godot-proposals/issues/3377”\n2021-10-02 02:32:49Z fire: https://github.com/godotengine/godot-proposals/issues/3375\n2021-10-01 07:54:55Z Saracen: Neat!"
+    "text": "Game releases are working again."
   },
   {
-    "objectID": "changelog/2024/20240901-changelog.html",
-    "href": "changelog/2024/20240901-changelog.html",
-    "title": "V-Sekai Changelog - September 2024",
+    "objectID": "changelog/2022/20221101-changelog.html#lyuma",
+    "href": "changelog/2022/20221101-changelog.html#lyuma",
+    "title": "V-Sekai Changelog - 2022-11",
     "section": "",
-    "text": "Experimental (🧪): This stage is for features that are still being tested and may not be stable.\nFeature complete (🎯): This stage is for features that have all planned functionality implemented.\nBeta (🚧): This stage is for features that are largely complete but may still have bugs.\nGeneral release (🚀): This stage is for features that have been fully tested and are now released.\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\n\n\nWork in progress with humanoid muscle encoding to/from quaternion. We can use this in the future for more efficient network serialization (similar to ShaderMotion’s format, or networked IK)\nSome progress on CDN code to make it a bit more reliable and engineered. It supports both gltf and godot scene format.\nfire and fwsGonzo have been working hard on godot-sandbox, a scripting system which allows you to write C++ code which acts like GDScript, via a sandboxed risc-v VM\nIn terms of engine features, typed dictionaries are in! https://godotengine.org/article/dev-snapshot-godot-4-4-dev-2/ That said, code which uses typed dictionaries will be incompatible with Godot 4.3 and earlier.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nSecurity Best Practices:\n\nThis project does not adhere to Semantic Versioning.\n\n\n\n\n\nNot applicable for this month."
+    "text": "V-Sekai-game Player spawning should be working again (see their name tag at least). There’s an issue with the default sky_celebration map caused by “TestEntity” which has scene_file_path==“” and that breaks the validation logic, preventing the player from spawning, and most default maps don’t work. You need to use Mobile Dragon Shop (very dark) or Tokyo Map\nNote that avatars are currently not working. I think I’m getting closer to identifying where the validation is causing trouble.\n\n\nWe are working on a v2 of the network architecture based on Godot’s network spawn & sync system, so a lot of the code I’m editing right now is kind of legacy at this point. The new network implementation should drastically simplify the code and eliminate dozens of complex GDScript files from being needed. I still want to get this demo stable, since we will still be using the player controller and avatar loader from it\n\n\n\nVSK Tokyo Map\n\n\nThe new v2 network demo can be found at https://github.com/V-Sekai/net_demo if you’re curious. There’s no VR support planned for net_demo, but it should serve as a strong foundation going forward.\nAvatars should show up again. There was some code mistake that triggered only when the default “mirror” was disabled and caused avatars not to instantiate, but I didn’t notice because I had turned it on in my checkout\nI also fixed the default sky celebration map\nAvatar bone rotations are currently broken with this setup. Seems like the head always faces a certain direction:\n\n\n\nAvatar bone rotations are broken"
   },
   {
-    "objectID": "changelog/2024/20240901-changelog.html#released",
-    "href": "changelog/2024/20240901-changelog.html#released",
-    "title": "V-Sekai Changelog - September 2024",
+    "objectID": "changelog/2022/20220501-changelog.html",
+    "href": "changelog/2022/20220501-changelog.html",
+    "title": "V-Sekai Changelog - 2022-05",
     "section": "",
-    "text": "Not applicable for this month."
+    "text": "https://github.com/V-Sekai/godot-seurat is dependent on being able to fetch 16 bit float buffers https://github.com/godotengine/godot/issues/54122#issuecomment-1140414946.\n\n\n\n\nInvestigated technical art via breaking apart the cafe\nInvestigated DagAmendment for brush based refinement of csg shapes.\n\n\n\n\n\nCharacters now load but the pose is incorrect.\nMaps load from a new sdk uploader.\nThe content picker is bad and ugly but usable to pick maps to host and choose avatars.\nThe server sees all clients but the clients only see the server and not each other.\nThe vr pose is incorrect but you can see the error so it hasn’t catastrophically exploded.\n\n\n\n\nimage\n\n\n\n\n\nCompleted a first stage EWBIK inverse kinematics solver to the stage one which solves but doesn’t have constraints."
   },
   {
-    "objectID": "changelog/2024/20240901-changelog.html#unreleased",
-    "href": "changelog/2024/20240901-changelog.html#unreleased",
-    "title": "V-Sekai Changelog - September 2024",
+    "objectID": "changelog/2022/20220501-changelog.html#section",
+    "href": "changelog/2022/20220501-changelog.html#section",
+    "title": "V-Sekai Changelog - 2022-05",
     "section": "",
-    "text": "Work in progress with humanoid muscle encoding to/from quaternion. We can use this in the future for more efficient network serialization (similar to ShaderMotion’s format, or networked IK)\nSome progress on CDN code to make it a bit more reliable and engineered. It supports both gltf and godot scene format.\nfire and fwsGonzo have been working hard on godot-sandbox, a scripting system which allows you to write C++ code which acts like GDScript, via a sandboxed risc-v VM\nIn terms of engine features, typed dictionaries are in! https://godotengine.org/article/dev-snapshot-godot-4-4-dev-2/ That said, code which uses typed dictionaries will be incompatible with Godot 4.3 and earlier.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nSecurity Best Practices:\n\nThis project does not adhere to Semantic Versioning."
+    "text": "https://github.com/V-Sekai/godot-seurat is dependent on being able to fetch 16 bit float buffers https://github.com/godotengine/godot/issues/54122#issuecomment-1140414946."
   },
   {
-    "objectID": "changelog/2024/20240901-changelog.html#previous-releases",
-    "href": "changelog/2024/20240901-changelog.html#previous-releases",
-    "title": "V-Sekai Changelog - September 2024",
+    "objectID": "changelog/2022/20220501-changelog.html#section-1",
+    "href": "changelog/2022/20220501-changelog.html#section-1",
+    "title": "V-Sekai Changelog - 2022-05",
     "section": "",
-    "text": "Not applicable for this month."
+    "text": "Investigated technical art via breaking apart the cafe\nInvestigated DagAmendment for brush based refinement of csg shapes."
   },
   {
-    "objectID": "changelog/2024/20240101-changelog.html",
-    "href": "changelog/2024/20240101-changelog.html",
-    "title": "V-Sekai Changelog - January 2024",
+    "objectID": "changelog/2022/20220501-changelog.html#section-2",
+    "href": "changelog/2022/20220501-changelog.html#section-2",
+    "title": "V-Sekai Changelog - 2022-05",
     "section": "",
-    "text": "Not applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nSecurity Best Practices: Applied security best practices as recommended by StepSecurity. (Commit: d641001)\n\nThis project does not adhere to Semantic Versioning.\n\n\n\n\n\nNot applicable for this month."
+    "text": "Characters now load but the pose is incorrect.\nMaps load from a new sdk uploader.\nThe content picker is bad and ugly but usable to pick maps to host and choose avatars.\nThe server sees all clients but the clients only see the server and not each other.\nThe vr pose is incorrect but you can see the error so it hasn’t catastrophically exploded.\n\n\n\n\nimage"
   },
   {
-    "objectID": "changelog/2024/20240101-changelog.html#released",
-    "href": "changelog/2024/20240101-changelog.html#released",
-    "title": "V-Sekai Changelog - January 2024",
+    "objectID": "changelog/2022/20220501-changelog.html#section-3",
+    "href": "changelog/2022/20220501-changelog.html#section-3",
+    "title": "V-Sekai Changelog - 2022-05",
     "section": "",
-    "text": "Not applicable for this month."
+    "text": "Completed a first stage EWBIK inverse kinematics solver to the stage one which solves but doesn’t have constraints."
   },
   {
-    "objectID": "changelog/2024/20240101-changelog.html#unreleased",
-    "href": "changelog/2024/20240101-changelog.html#unreleased",
-    "title": "V-Sekai Changelog - January 2024",
+    "objectID": "changelog/2022/20220201-changelog.html",
+    "href": "changelog/2022/20220201-changelog.html",
+    "title": "V-Sekai Changelog - 2022-02",
     "section": "",
-    "text": "Not applicable for this month.\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nSecurity Best Practices: Applied security best practices as recommended by StepSecurity. (Commit: d641001)\n\nThis project does not adhere to Semantic Versioning."
+    "text": "iFire — Today at 07:38 Openxr is merged into Godot Engine master!\nLyuma — Today at 16:13\nOVR Advanced Settings 5.4.0 is released with OpenXR playspace moving support (for devices connected via SteamVR):\nhttps://user-images.githubusercontent.com/32321/155451982-8d21ca07-0178-4314-a4f2-8de56c275fa3.png\n\n\n\nトカゲ — 10:28 We discussed with reduz implementation of retargeting for about 8 hours\nLyuma — 14:02 if anyone’s interested, you can read RocketChat from a browser: https://chat.godotengine.org/channel/animation?msg=JYqzF7xviTbh5zbmm\n\n\n\nFire moved multiple projects issues to https://github.com/V-Sekai/V-Sekai/issues.\n\n\n\nLyuma changed RenIK to use set_bone_local_pose_override, and “hacked” skeleton’s transform to keep it centered on the hips, fixing the avatar disappearing when far from origin.\n\n\n\nWe made a lot of progress yesterday: getting closer to OpenXR integration; fixed some issues with avatar uploading; and progress with WasGo, including the ability to create a Godot Callable which directly represents a WASM function\n\n\n\nMoved fire’s project notes to V-Sekai/V-sekai issues.\nCurl has been postponed.\nCvtt bc6, bc7 texture compression speedup by reducing quality has been merged. Updating groups.\n\n\n\nWasgo go! Restored wasgo wasm execution."
   },
   {
-    "objectID": "changelog/2024/20240101-changelog.html#previous-releases",
-    "href": "changelog/2024/20240101-changelog.html#previous-releases",
-    "title": "V-Sekai Changelog - January 2024",
+    "objectID": "changelog/2022/20220201-changelog.html#section",
+    "href": "changelog/2022/20220201-changelog.html#section",
+    "title": "V-Sekai Changelog - 2022-02",
     "section": "",
-    "text": "Not applicable for this month."
+    "text": "iFire — Today at 07:38 Openxr is merged into Godot Engine master!\nLyuma — Today at 16:13\nOVR Advanced Settings 5.4.0 is released with OpenXR playspace moving support (for devices connected via SteamVR):\nhttps://user-images.githubusercontent.com/32321/155451982-8d21ca07-0178-4314-a4f2-8de56c275fa3.png"
   },
   {
-    "objectID": "changelog/2024/20240625-changelog.html",
-    "href": "changelog/2024/20240625-changelog.html",
-    "title": "Special Notice: V-Sekai 2023-2024",
+    "objectID": "changelog/2022/20220201-changelog.html#section-1",
+    "href": "changelog/2022/20220201-changelog.html#section-1",
+    "title": "V-Sekai Changelog - 2022-02",
     "section": "",
-    "text": "Focused on Unidot and VRM (import pipeline).\nGodot 4.0 bugfixes and animation. Lots of engine dev.\nJuly–Aug spent time working on new CDN downloader and starting to rethink avatar controller.\n\n\n\n\n\nNew networking system committed to v-sekai-game and to a demo repository. It is missing basic features like support for pickup items so we haven’t enabled it yet.\n\n\n\n\n\nJan–Mar focused on FBX support and GDC.\nApr–May focused on updating Unidot to support FBX.\n\n\n\n\n\n\nSince early June, Lyuma started to revisit the incomplete code from 10 months ago. Lyuma is currently working on tracker binding / skeleton calibration (e.g. full body).\n4.3 release was delayed. Lyuma wants to release 4.3-compatible updates to Unidot and VRM.\nLyuma had some difficulties with API integration.\nSome Godot 4.3 bugs are still on Lyuma’s plate.\n\n\n\n\n\nNew in-game UI update. A draft was committed a couple weeks ago but saracen has been away on vacation.\nSaracen has also been working some more on physics sync.\nAPI/backend redesign.\n\n\n\n\n\nIntegration of UI code into game.\nNetwork syncing support of props/objects using the new system.\nIntegration of other game features between avatar_vr_demo (player controller) and v-sekai-game (legacy codebase).\nNew backend so we can reenable registration.\nSome OpenAPI wrapper so we can talk to the new backend.\n\nLyuma thinks we should put more focus on getting something lightweight we can run and play levels in. Lyuma is of half a mind to put more focus into making avatar demo runnable with custom content rather than fully integrating network syncing just so we can get off the ground more easily with content creation."
+    "text": "トカゲ — 10:28 We discussed with reduz implementation of retargeting for about 8 hours\nLyuma — 14:02 if anyone’s interested, you can read RocketChat from a browser: https://chat.godotengine.org/channel/animation?msg=JYqzF7xviTbh5zbmm"
   },
   {
-    "objectID": "changelog/2024/20240625-changelog.html#stuff-we-did-over-the-past-year",
-    "href": "changelog/2024/20240625-changelog.html#stuff-we-did-over-the-past-year",
-    "title": "Special Notice: V-Sekai 2023-2024",
+    "objectID": "changelog/2022/20220201-changelog.html#section-2",
+    "href": "changelog/2022/20220201-changelog.html#section-2",
+    "title": "V-Sekai Changelog - 2022-02",
     "section": "",
-    "text": "Focused on Unidot and VRM (import pipeline).\nGodot 4.0 bugfixes and animation. Lots of engine dev.\nJuly–Aug spent time working on new CDN downloader and starting to rethink avatar controller.\n\n\n\n\n\nNew networking system committed to v-sekai-game and to a demo repository. It is missing basic features like support for pickup items so we haven’t enabled it yet.\n\n\n\n\n\nJan–Mar focused on FBX support and GDC.\nApr–May focused on updating Unidot to support FBX."
+    "text": "Fire moved multiple projects issues to https://github.com/V-Sekai/V-Sekai/issues."
   },
   {
-    "objectID": "changelog/2024/20240625-changelog.html#current-work",
-    "href": "changelog/2024/20240625-changelog.html#current-work",
-    "title": "Special Notice: V-Sekai 2023-2024",
+    "objectID": "changelog/2022/20220201-changelog.html#section-3",
+    "href": "changelog/2022/20220201-changelog.html#section-3",
+    "title": "V-Sekai Changelog - 2022-02",
     "section": "",
-    "text": "Since early June, Lyuma started to revisit the incomplete code from 10 months ago. Lyuma is currently working on tracker binding / skeleton calibration (e.g. full body).\n4.3 release was delayed. Lyuma wants to release 4.3-compatible updates to Unidot and VRM.\nLyuma had some difficulties with API integration.\nSome Godot 4.3 bugs are still on Lyuma’s plate."
+    "text": "Lyuma changed RenIK to use set_bone_local_pose_override, and “hacked” skeleton’s transform to keep it centered on the hips, fixing the avatar disappearing when far from origin."
   },
   {
-    "objectID": "changelog/2024/20240625-changelog.html#other-projects-in-progress",
-    "href": "changelog/2024/20240625-changelog.html#other-projects-in-progress",
-    "title": "Special Notice: V-Sekai 2023-2024",
+    "objectID": "changelog/2022/20220201-changelog.html#section-4",
+    "href": "changelog/2022/20220201-changelog.html#section-4",
+    "title": "V-Sekai Changelog - 2022-02",
     "section": "",
-    "text": "New in-game UI update. A draft was committed a couple weeks ago but saracen has been away on vacation.\nSaracen has also been working some more on physics sync.\nAPI/backend redesign."
+    "text": "We made a lot of progress yesterday: getting closer to OpenXR integration; fixed some issues with avatar uploading; and progress with WasGo, including the ability to create a Godot Callable which directly represents a WASM function"
   },
   {
-    "objectID": "changelog/2024/20240625-changelog.html#wtfawry-what-do-we-need-to-get-v-sekai-game-working-with-the-new-architecture",
-    "href": "changelog/2024/20240625-changelog.html#wtfawry-what-do-we-need-to-get-v-sekai-game-working-with-the-new-architecture",
-    "title": "Special Notice: V-Sekai 2023-2024",
+    "objectID": "changelog/2022/20220201-changelog.html#section-5",
+    "href": "changelog/2022/20220201-changelog.html#section-5",
+    "title": "V-Sekai Changelog - 2022-02",
     "section": "",
-    "text": "Integration of UI code into game.\nNetwork syncing support of props/objects using the new system.\nIntegration of other game features between avatar_vr_demo (player controller) and v-sekai-game (legacy codebase).\nNew backend so we can reenable registration.\nSome OpenAPI wrapper so we can talk to the new backend.\n\nLyuma thinks we should put more focus on getting something lightweight we can run and play levels in. Lyuma is of half a mind to put more focus into making avatar demo runnable with custom content rather than fully integrating network syncing just so we can get off the ground more easily with content creation."
+    "text": "Moved fire’s project notes to V-Sekai/V-sekai issues.\nCurl has been postponed.\nCvtt bc6, bc7 texture compression speedup by reducing quality has been merged. Updating groups."
   },
   {
-    "objectID": "changelog/2024/20240701-changelog.html",
-    "href": "changelog/2024/20240701-changelog.html",
-    "title": "V-Sekai Changelog - July 2024",
+    "objectID": "changelog/2022/20220201-changelog.html#section-6",
+    "href": "changelog/2022/20220201-changelog.html#section-6",
+    "title": "V-Sekai Changelog - 2022-02",
     "section": "",
-    "text": "Experimental (🧪): This stage is for features that are still being tested and may not be stable.\nFeature complete (🎯): This stage is for features that have all planned functionality implemented.\nBeta (🚧): This stage is for features that are largely complete but may still have bugs.\nGeneral release (🚀): This stage is for features that have been fully tested and are now released.\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nReplaced fabrik ik solver in renik ik character controler with qcp ik solver.\nManifold for Godot Engine CSG ready for review\nWorked on Wasgo for WASM32-CPUs for tooling and runtime user generated code.\nWorked on libriscv loading and executing a hello world function call with a shared object.\nWorked on godot-llama trying to get the new PHI-3 model working. https://github.com/V-Sekai/godot-llama\nWorked on ServerBackend🚫\nWorked on TrollVsGoatTrafficSimulator\nWorked on elaish/manifold for Constructive Solid Geometry\nWorked on Vahera/godot-orchestrator for riscv and a merge for node formatting\nWorked with fwsGonzo/libriscv for riscv. V8 now works.\nWorked on 3D Mesh\n\nTokenized into Sequence of Tokens\nInputted into Transformer Model\nGenerates New Meshes\nModifies Existing Meshes\n\nExperimental Mirrors: Engine Patch 🧪\nExperimental Mirrors: Screenspace 🧪\nMaintained Resource Whitelister 🎯\nMaintained VRM 🎯\nRobust Weight Painting (Experimental 🧪) (iFire)\n\nRelies on Lyuma’s Skeleton Merging Tool\n\nUpdate to Godot Engien 4.3-beta3\n\n\n\n\nUnified Godot Humanoid Skeleton 🚀\nUnidot Unity Package Importer\nFBX 🚧\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nSecurity Best Practices:\n\nThis project does not adhere to Semantic Versioning.\n\n\n\n\n\nNot applicable for this month."
+    "text": "Wasgo go! Restored wasgo wasm execution."
   },
   {
-    "objectID": "changelog/2024/20240701-changelog.html#released",
-    "href": "changelog/2024/20240701-changelog.html#released",
-    "title": "V-Sekai Changelog - July 2024",
+    "objectID": "changelog/2021/20210401-changelog.html",
+    "href": "changelog/2021/20210401-changelog.html",
+    "title": "V-Sekai Changelog - 2021-04",
     "section": "",
-    "text": "Not applicable for this month."
+    "text": "V-Sekai Changelog - 2021-04\nIn April 2021, various developments and discussions took place in the Godot community. Key highlights include proposal designs for MaterialX integration, audio system improvements, and updates to the TPS demo for Godot 4.0. Additionally, there were investigations into edcurve support, normal seam problems, and soft body creation usability.\n\n2021-04-30\n\nProposal design of MaterialX Principled BSDF to Blender Principled BSDF to Blender surface.\nLyuma — MaterialX in glTF would allow for a generalization of “KHR_materials_variants” extension.\nMade a proposal for GLTF2 to include MaterialX in three stages.\nMade a prototype that exposes HTC Facial tracker to Godot Engine as a GDNative plugin for 3.x. Link\n\n\n\n2021-04-29\n\nDesign Approved; Needs Proposal from Juan: Play scheduled notes/metronome Link\nPostponed Discussion: Modular audio system (like JACK) godot#35613\nInterest: Integrate interactive music PR godot#32769\nInterest: Discuss audio stream graph\nApproved: Onboarding for newcomers to the audio side of Godot development\nInterest: Godot Audio Graph\n\n\n\n2021-04-28\n\nArguing in OMI about materialx, usdz and wasm\nFiled issue Link\nInvestigate Link for edcurve support now\nFiled issue Link\nFire filed issue Link about the rendering server custom format issue with a reproduction project.\nReduz is personally updating the TPS demo for 4.0\nGodot Engine developers’ next Live Q&A on YouTube this Thursday, 29 April 2021 at 18:00 UTC. Link\nLyuma Topics: Normal seam problem\nLyuma Topics: Create a proposals for better usability of soft body creation.\nLyuma Topics: Using n-gon encoding for glTF / VRM.\n\n\n\n2021-04-27\n\nMade a small video and ported the Godot IPFS demo to Windows. Link\nUpdated Scheduled play branch and the demo. Link and Link\nWaiting for a 3d print of Link so I can try the HTC Facial tracker with Link.\nMade a decision yesterday to close GIF / APNG import in Godot due to consensus. Link\nReviewing WebP as the default lossless compression algo for the core Godot Engine. Link\nReceived an update to the Holo display delivery. It’ll be in May - https://www.kickstarter.com/projects/lookingglass/looking-glass-portrait/posts\nReviewing Play Scheduled proposal - Link\nUse the IPFS Go language binary to make Godot an IPFS server Link\nWorked on debugging SVG import for the UI made for the hop spin dance display. Link"
   },
   {
-    "objectID": "changelog/2024/20240701-changelog.html#unreleased",
-    "href": "changelog/2024/20240701-changelog.html#unreleased",
-    "title": "V-Sekai Changelog - July 2024",
+    "objectID": "changelog/2021/20210501-changelog.html",
+    "href": "changelog/2021/20210501-changelog.html",
+    "title": "V-Sekai Changelog - 2021-05",
     "section": "",
-    "text": "Replaced fabrik ik solver in renik ik character controler with qcp ik solver.\nManifold for Godot Engine CSG ready for review\nWorked on Wasgo for WASM32-CPUs for tooling and runtime user generated code.\nWorked on libriscv loading and executing a hello world function call with a shared object.\nWorked on godot-llama trying to get the new PHI-3 model working. https://github.com/V-Sekai/godot-llama\nWorked on ServerBackend🚫\nWorked on TrollVsGoatTrafficSimulator\nWorked on elaish/manifold for Constructive Solid Geometry\nWorked on Vahera/godot-orchestrator for riscv and a merge for node formatting\nWorked with fwsGonzo/libriscv for riscv. V8 now works.\nWorked on 3D Mesh\n\nTokenized into Sequence of Tokens\nInputted into Transformer Model\nGenerates New Meshes\nModifies Existing Meshes\n\nExperimental Mirrors: Engine Patch 🧪\nExperimental Mirrors: Screenspace 🧪\nMaintained Resource Whitelister 🎯\nMaintained VRM 🎯\nRobust Weight Painting (Experimental 🧪) (iFire)\n\nRelies on Lyuma’s Skeleton Merging Tool\n\nUpdate to Godot Engien 4.3-beta3\n\n\n\n\nUnified Godot Humanoid Skeleton 🚀\nUnidot Unity Package Importer\nFBX 🚧\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nSecurity Best Practices:\n\nThis project does not adhere to Semantic Versioning."
+    "text": "V-Sekai Changelog - 2021-05\n\n\nChangelog\n\n2021-05-31\n\n21:30:03Z fire: Godot4OVRTest and godot-fire\n21:29:42Z fire: Context. Porting OpenXR to run on Godot Engine 4\n21:29:29Z fire: haagch’s input on VkPhysicalDevices and VkInstances\n21:28:46Z fire: haagch’s suggestion for handling VkInstance in OpenXR plugin and engine\n21:25:54Z lyuma: Yayay\n21:11:03Z fire: 🎆 🎆 🎆\n21:10:49Z fire: 🎉\n21:10:45Z fire: Lyuma Merged PR #49120 👏 (2)\n\n\n\n2021-05-30\n\n12:58:28Z fire: V-Sekai VRM addon release\n10:58:12Z lyuma: “Submitted the asset”“VRM Importer and MToon Shader”” - it will be at asset/3693 once approved.\n\nIssue comment\nVideo demo\n\n00:57:51Z fire: Merged LOD fix PR #49197\n\n\n\n2021-05-29\n\n22:08:49Z fire: Found a bug in LOD on integer locations. Asked someone to handle it for me.\n17:52:04Z fire: Lyuma May need an ubuntu version too. Not sure how the test matrix works. I want fedora and ubuntu LTS (the oldest one)\n17:13:00Z lyuma: Progress on godot-cpp, Godette-Chan model port to VRM, and other updates\n17:09:27Z lyuma: Debugging an issue causing the outlines to look too bright in MixedLight mode, then I’ll demonstrate exporting a default character from vroid studio as well.\n\n\n\n2021-05-29\n\n17:06:50Z lyuma: Godette-Chan model in VRM format\n16:59:06Z lyuma: Godette-Chan model port result 👏 (1)\n\n\n\n2021-05-28\n\n22:45:48Z fire: Spent the afternoon on organizing work on the CMValley Godot Demo\n21:53:32Z lyuma: Updated godot-cpp; fixed SConstruct lines and resolved errors with clang and the gltf GDNative plugin\n21:15:35Z fire: Investigating the Godot Engine open content map “CMValley_to_Godot_Demo” (Ask me for the doc if you want it)\n20:46:13Z fire: Given .net assemblies 1. visualize 2. given pdbs associate symbols 3. graph!\n20:45:48Z fire: Lyuma Synergiance SourcetrailDotnetIndexer\n06:24:04Z fire: Code review gltf the entire afternoon\n\n\n\n2021-05-27\n\n18:45:25Z fire: Spent time summoning peers about making a realistically lit 3d game level environment in Godot Engine. Official Godot Engine business. -_-\n\n\n\n2021-05-26\n\n21:43:14Z lyuma: Filed bugs and pull requests\n21:17:25Z fire: Tokage improved the Skeleton Gizmos with better color choices and bugfix for a shadow problem with depth\n17:43:36Z fire: We contributed to the drafting of them.\n17:43:22Z fire: Values from OMI\n10:38:49Z lyuma: Twitter post\n\n\n\n2021-05-26\n\n09:26:03Z lyuma: For now anyway, the VRM module is only for import.\n09:25:40Z lyuma: there’s a lot of untested code related to export, since there are still bugs, but I expect to be able to incorporate any bugfixes made to export\n09:25:09Z lyuma: After finishing the backport of the Fire’s latest gltf module to 3.x as a module / draft PR, I had success in porting the gltf module to GDNative: The VRM module now runs in Godot 3.3-stable: Screenshot\n\n\n\n2021-05-24\n\n18:13:44Z fire: Evaluating curve fitter from Maya2glTF. Reducer-fire branch Screenshot\n18:08:49Z Saracen: Progress on asset validation layer and remaining issues\n15:37:50Z fire: (blender)\n15:37:37Z fire: Screenshot 👍 (2)\n15:37:09Z fire: Worked with hutty to transfer gltf export tech to his voxel drawing tool\n00:56:09Z fire: Also, pitching usdz after 4.0\n00:55:22Z fire: “Trying to pitch a list of features for funding. - Full glTF2 / VRM import and export pipeline in Godot Engine\nGeneral purpose retargeting system for VRM type models + encoding in BVH (3d pose format)\nGodot Engine support for basis universal in glTF2\nQuads in glTF2\nAfter quads in glTF2, better mesh simplification and LODs that work on quads”\n\n\n\n2021-05-22\n\n16:23:18Z fire: PR #47764 Lod Merge! 👏 (4)\n03:41:06Z lyuma: is it GLES2 or GLES3?\n03:12:33Z fire: humbletim Screenshot\n02:30:08Z fire: Investigating V-Sekai compiled for javascript\n\n\n\n2021-05-21\n\n23:38:30Z fire: Screenshot\n23:32:27Z fire: What do I do, Victoria Day on Monday. How is the Queen!?\n23:31:24Z fire: Discussed 15 frames encoding into a QR / DataMatrix code ShaderMotion Writing a obs script in python to read data.\n\n\n\n2021-05-21\n\n15:37:50Z fire: (blender)\n15:37:37Z fire: Screenshot 👍 (2)\n15:37:09Z fire: Worked with hutty to transfer gltf export tech to his voxel drawing tool\n00:56:09Z fire: Also, pitching usdz after 4.0\n00:55:22Z fire: “Trying to pitch a list of features for funding. - Full glTF2 / VRM import and export pipeline in Godot Engine\nGeneral purpose retargeting system for VRM type models + encoding in BVH (3d pose format)\nGodot Engine support for basis universal in glTF2\nQuads in glTF2\nAfter quads in glTF2, better mesh simplification and LODs that work on quads”\n2021-05-21 22:51:16Z lyuma: “I worked with fire on debugging glTF. I think we’re going to possibly need two different approaches for solving glTF skeletons.\n\nRadical change to glTF parser to treat all subtree nodes as part of a single skeleton recursively. (What we were just testing) I believe this would be unacceptable in 3.x because it is almost guaranteed to break compatibility with all content, but it may be desirable in 4.x.\nAdd BoneAttachments to skeletons directly parented to skeletons. (We tried this). This may be required in 3.x.\nWhile in _determine_skeletons, detect the specific case in which two skeletons would be directly parented and add them to the disjoint set in this case (look at the parent objects at the end). Do not actually add the parent bone to the disjoint set: only do it if this would hit the problem case. Issue: this may require doing another iteration of the _determine_skeletons code? Is this possible without causing more bugs? This could be a compromise if it is possible.\n\nBugs:\n\nAnimations must not animate SkinnedMesh objects\nWe ran into weird issues with fake_joints. Can these issues be reproduced without the radical change above? I think they can by making a single gltf file which has a skin also referencing a mesh. This issue leads animation targeting mesh-bones to fail to create a bone track correctly.\nMeshSkinnedToItselfAndOthersV3 is missing a whole mesh node after import. It shows up in the popup but not in the final scene. Owner issue?? Is it related to the fake_joints? The glb here should have a spinning diamond and two spinning skinned cubes:” https://cdn.discordapp.com/attachments/836651615532482611/845433592888557568/MeshSkinnedToItselfAndOthersV3.glb\n\n2021-05-21 22:29:43Z fire: We also gain the ability to post more twitter tweets.\n2021-05-21 22:29:23Z fire: Had a discussion with Lyuma and Saracen about V-Sekai for wider testing and how it was blocked by scene validation feature.\n2021-05-21 15:27:33Z fire: Multiple PRs from fire and Lyuma were merged for gltf problems\n2021-05-20 15:28:19Z fire: トカゲ https://github.com/godot-extended-libraries/godot-fire/commits/features/skeleton-gizmos I did some cleanup, rebased on the modification stack and changed the color for selected bones to be a darker orange\n2021-05-20 15:26:43Z fire: Lyuma IK and Modification stack are now a stacked branch.\n2021-05-20 04:21:06Z fire: Work with Lyuma on 3 glTF bug fixes. 1. instead of failing all the meshes only fail once 2. the skins duplication removal code has a bug and it needs to check skin bind bone, skin bind name and pose transform. 3. the skin bind code was removed 4. gltf 4.0 modules was backported to 3.2\n2021-05-19 19:20:41Z fire: Lyuma and I summarized our concerns about the ease of implementation and the inability to use off the shelf code.\n2021-05-19 19:20:00Z fire: OMI Week 3. Stayed for the talk at 9am and then stayed with Robert Long to talk about OMI Identity and misc things like there is no opensource OpenXR mobile client. https://github.com/omigroup/OMI/issues/36#issuecomment-844392614\n2021-05-19 14:37:19Z fire: After sleeping on the Linux RPM database problem, I was able to get WSL working again. Lyuma I needed to switch WSL to version 2.\n2021-05-18 18:32:58Z fire:\n\ngroups-4.x branch in the Groups Godot Engine Repo\n\n1. VRM patches required\n2. Importing patches for the editor\n3. Gltf and other UV1-8 channel requirements\n4. (stacked branch) bone modification + bone gizmos\n5. fix normals being broken in mesh optimizer\nPush on merge extended-fire-master remotes/fire/cubic-interpolation\nPush on merge extended-fire-master remotes/fire/gltf-bone-skinning-normalization\n6. remotes/bruvzg/msdf_fonts\n7. push gltf export (fire)\n8. feature/spatial-audio\n9. rewrite compressed audio for voip\nPush on SIMDE for avx support\nPunt crash / reliability problem on Godot Engine crashing\n\nmerge-script-4.x is the branch name for the groups_merge_script Repo\n\n2021-05-18 17:41:55Z fire: “Coordination problems:\nname of the ““merge script”” for v-sekai 4.x\nname of the V-Sekai/godot branch for v-sekai 4.x\nwhich branches should be in the initial set of patches applied to godotengine master branch”\n2021-05-18 14:46:44Z fire: GSOC 2021 started on Monday. Will be mentoring Theoway and on the topic of Visual Script node visual organization\n2021-05-18 14:43:56Z fire: Posted my last revision of runtime export https://github.com/godot-extended-libraries/godot-fire/tree/extended-fire-master-runtime-gltf\n2021-05-18 14:01:58Z fire: Lyuma Please see xr channel in godot about runtime gltf. May be too politically diffficult to get merged, so will fix gltf export bugs\n2021-05-18 03:48:49Z fire: “Worked with Lyuma and Tim on MotionShader to glTF2 https://hackmd.io/@tI5OkracQhuas5Kjh-kG0g/S1uzKIgt_/edit”\n2021-05-17 00:07:58Z Saracen: A few more fixes to the XR switching + you can now alter your real-world height at runtime heart (2)\n2021-05-16 23:01:38Z fire: I have as animation as I want 😮 https://cdn.discordapp.com/attachments/836651615532482611/843624264958738462/2021-05-16_15-59-25.mp4 👍 (2)\n2021-05-16 23:01:17Z fire: https://cdn.discordapp.com/attachments/835369558541467668/843623340965888040/godot_girl_stealth_JohnnyRouddro_mit_lic_No_Logic_David_cc_by.glb\n2021-05-16 22:58:19Z Saracen: Added further bug fixes to runtime switching of VR mode and flat mode. Fixes the few minor remaining issues with the avatar poses getting messed up, and the VR controllers being stuck on screen. With that, I’m satisfied with marking this feature as done in the tracker.\n2021-05-16 22:22:05Z fire: Work around found. Import into godot and then export it as glb again.\n2021-05-16 22:17:37Z fire: Submitted a blender gltf bug report. https://github.com/KhronosGroup/glTF-Blender-IO/issues/1392 😮 (1)\n2021-05-16 21:19:32Z fire: We are a go for big frame counts. I’m able to get a massive dataset thanks to lox9973 https://cdn.discordapp.com/attachments/836651615532482611/843598569851846707/unknown.png\n2021-05-16 21:15:45Z lyuma: “I hope the code I wrote will help others as a template for making nice-looking inspectors.\n\nI am considering submitting Godot-MToon-Shader to the asset library, separately from VRM.”\n\n2021-05-16 21:15:12Z lyuma: Using much the same cursed techniques that many Unity inspectors use, I was able to create bold headings, and “single-line” texture+image property pickers.\n2021-05-16 21:13:39Z lyuma: In some ways, it’s a bit more clunky than the get_property_list(), and a bit less versatile in terms of what you can do… but I decided to think outside the VBoxContainer a little bit, and I came up with a reasonable inspector, I think.\n2021-05-16 21:11:54Z lyuma: Spent most of the day learning how to make a custom shader inspector using EditorInspectorPlugin. I’m pretty happy with how it turned out https://cdn.discordapp.com/attachments/836651615532482611/843596648855896084/mtoon_shader_inspector.png\n2021-05-16 16:15:16Z fire: Thanks lox9973 for linking me to enough training data for my pose motion transfer tests. https://www.youtube.com/playlist?list=PLmwqDOin_Zt4WCMWqoK6SdHlg0C_WeCP6 (cc-by)\n2021-05-16 15:11:34Z fire: Brainstorming an intermediate format that isn’t exact per bone joint orientation but general across characters\n2021-05-16 05:53:14Z fire: Investigating ShaderMotion. Now that I can go from some anims to Unity Mechanism / UE4 / VRM skeletons, I want to investigate writing a shader motion player.\n2021-05-16 01:16:04Z lyuma: https://github.com/V-Sekai/godot-vrm godot3 branch (Godot 3.3): Runtime support requires no patches. Editor requires gltf module. master branch: Runtime support requires no patches. Editor requires two small engine fixes.\n2021-05-16 01:13:55Z lyuma: Getting very close to a releasable fully featured (Import-only) VRM addon for Godot. Let me know what you think in #pipeline https://cdn.discordapp.com/attachments/836651615532482611/843295167603015700/godot_vrm_1.0.0_beta.mp4\n2021-05-15 23:15:29Z fire: VRM from jin. Motion from Perfume dance webgl demo from 2013 in bvh format\n2021-05-15 23:15:13Z fire: Testing animation retargeting software from the Blender ecosystem. https://cdn.discordapp.com/attachments/842452265296986134/843264562430214164/2021-05-15_16-10-49.mp4\n2021-05-15 14:36:56Z lyuma: wiping history on V-Sekai/godot-vrm will be necessary because some large binary files were pushed in the past, and I want to ensure this addon is lightweight and easy to clone.\n2021-05-15 14:33:39Z lyuma: “Pushed an update to Godot-VRM for godot 3.x: https://github.com/V-Sekai/godot-vrm/tree/gd3 It’s not finalized yet and I will do a bit more testing and bugfixing before rebasing/wiping all of history pushing it to godot3, its final resting place.”\n2021-05-14 15:00:58Z Saracen: Fixed some bugs to improve support for switching between VR and flat modes at runtime. Very ugly hack to fix one of the bugs though, strange issue. Some slight remaining avatar issues, but it’s mostly working now it seems.\n2021-05-14 02:17:44Z fire: Added three pictures and a video.\n2021-05-14 01:33:44Z fire: VOX to VRM fun. (Autorigging investigation for any static humanoid mesh!)\n2021-05-13 21:38:00Z lyuma: but yeah! It’s really exciting to get this much imported with just a couple clicks and about 30 seconds of waiting\n2021-05-13 21:37:01Z lyuma: it’s a bit of random chance that it looks so similar: the skydome and some objects like flowers have completely custom shaders, so those will have to be ported manually\n2021-05-13 21:36:32Z Saracen: This is actually starting to look like the original now\n2021-05-13 21:36:27Z Saracen: Woah!\n2021-05-13 21:36:04Z lyuma: Unidot Importer: Got lighting and basic environment settings importing. In squiddingme’s Traveler’s Rift, I’m now able to bake lighting immediately after importing. (You can see the probes are baking as black, so there are still some issues to be worked out.) - Also added support for audio, cameras and reflection probes: https://cdn.discordapp.com/attachments/836651615532482611/842515566413873172/unknown.png\n2021-05-13 18:14:28Z fire: https://github.com/V-Sekai/vox-to-vrm\n2021-05-13 18:12:49Z lyuma: Oh, jin is re-rigging it\n2021-05-13 18:12:28Z lyuma: Jin’s proposal does not make sense\n2021-05-13 18:12:21Z lyuma: Vrm is an avatar format which requires a rigged humanoid model. Obj does not support rigging\n2021-05-13 17:48:43Z fire: Lyuma https://cdn.discordapp.com/attachments/836651615532482611/842458354202181642/unknown.png\n2021-05-13 06:35:51Z Saracen: Tweaked the way wristspan is calculated since it came out wrong on some avatars where the arms weren’t perfectly aligned. Should result in more accurate VR proportions.\n2021-05-13 04:26:05Z fire: Rebased my godot 4.0 stack so I can go back to my vrm viewer thing\n2021-05-13 03:14:34Z Saracen: One more patch just to allow direct assignment of upper and lower bones by ID, but it seems to be working now. Good job! It’s now possible to use avatars with in-between bones.\n2021-05-13 03:00:37Z Saracen: Basically, the new code to automatically assign the next bone in the chain assumed the skeleton was assigned, even though it can be null.\n2021-05-13 02:55:04Z MMMaellon#2053 whoa wait why was it crashing\n2021-05-13 02:47:41Z Saracen: Fixed RenIK crashing.\n2021-05-13 00:48:18Z fire: Reviewed https://github.com/godotengine/godot/pull/46568. Basis universal version update.\n2021-05-12 23:34:42Z fire: OMI meeting today. OKR Review. Progress was difficult.\n2021-05-11 15:38:53Z fire: Vive con starts in 20 minutes Voice Notifications. Any interesting talks?\n2021-05-11 15:38:00Z fire: Anything from Vive Con?\n2021-05-11 13:49:22Z lyuma: Fixed an issue in EWBIK that was bothering me – namely, that the result of the algorithm appeared to depend on the root bone having an identity transform. It seems that all that was needed was to transform the “tip” and “target” headings of an IKBoneChain by the inverse transform of the root. https://cdn.discordapp.com/attachments/836651615532482611/841673340740829234/unknown.png 🌅 (1)\n2021-05-11 03:32:10Z fire: Whoo debugged EWBIK the entire day, and removed the hacks to reveal the broken core to be rebuilt! Thanks Eron!\n2021-05-10 17:21:03Z fire: Evaluated EWBIK with Motion Retargeting. Suggestions included adding a position indication (with scale) as a child of the correction node that is a child of the bone attachment and olving only one frame at a time. No conclusions yet, because ewbik is too broken.\n2021-05-10 02:48:21Z fire: Working with Eron on ewbik. Next meeting at 9am or later.\n2021-05-09 22:31:35Z fire: Working out a system where we create targets from the other skeletal animation using bone attachments and then a corresponding correction node underneath it. The ik solver then uses those correction node targets as the target.\n2021-05-09 17:22:13Z Saracen: Support for ordered grid super sampling and camera position-based bill-boarding added thanks to help from Silent and Lyuma\n2021-05-09 16:08:30Z fire: Many patches from トカゲ were merged today /. Thanks\n2021-05-09 14:34:42Z fire: Saracen / Lyuma suggested a hint_string where a skeleton bone attachment gets a filtering tree popup for selecting bones\n2021-05-08 15:47:13Z Saracen: https://github.com/SaracenOne/godot/tree/collada_semantic_fix_4_0\n2021-05-08 15:46:07Z Saracen: https://github.com/SaracenOne/godot/tree/collada_semantics_fix_3\n2021-05-08 15:45:11Z Saracen: Fixed some bugs with the Collada importer\n2021-05-08 15:44:33Z Saracen: https://cdn.discordapp.com/attachments/836651615532482611/840615163937816585/screenshot_2021_05_08_164031.png\n2021-05-08 10:48:29Z lyuma: Just to see how close I could get, I manually added a WorldEnvironment and did a few tweaks to light attenuation curves: https://cdn.discordapp.com/attachments/836651615532482611/840540658241634304/unknown.png\n2021-05-08 10:43:35Z lyuma: (Though, I also have not yet implemented world environment. Also, you can see it fails to port custom shaders like the skybox.)\n2021-05-08 10:42:42Z lyuma: squiddingme helped provide me with source files to their beautiful Traveler’s Rift, and I am finally able to import it using Unidot. This part was all automated, and includes collision meshes for all of the separate pickup objects, as well as light sources. https://cdn.discordapp.com/attachments/836651615532482611/840539201987936306/TravelersRift.jpg 👍 (1)\n2021-05-08 06:55:06Z fire: Chatted with humbletim about importing an existing armature into EWBIK Java\n2021-05-08 06:30:40Z MMMaellon#2053 You were talking about it the other day, but all that I got was that it was difficult to set up. idk what it actually did\n2021-05-08 06:30:13Z MMMaellon#2053 what does matrix server giv us?\n2021-05-08 06:28:45Z lyuma: “1. We set up a matrix server in 5 hours (a few hours wasted due to firewall).\n\n\nWe set up federation to the matrix server in an SRV record Next steps?\nTry godot-matrix to see if we can use the matrix server for interop. (Are there similar bindings for other languages?)\nSee if we can boil everything down to be easy to set up.\nWhat is matrix actually useful for? Identity? Establishing E2E messages? Sending invites? How does federation help?”\n\n\n2021-05-07 13:51:55Z fire: EWBIK bone dampening is implemented.\n2021-05-07 11:09:14Z fire: &gt; You won’t need stabilization before you’ve implemented constraints.\n2021-05-07 11:08:49Z fire: “Ewbik todo. dampening is about getting a natural pose, stabilization is about preventing wobbling when a lot of constraints are being violated.”\n2021-05-06 15:45:06Z fire: Got a reply from glitchtip. Require use cases generation.\n2021-05-05 21:29:14Z fire: Added better ui for creating the effectors (targets and pins) in ewbik\n2021-05-05 18:28:53Z fire: Lyuma When you’re around, wanted to show you the EWBIK changes. It’s working for some small cases.\n2021-05-05 12:53:56Z lyuma: anyway aside from this PR and one other two-line workaround to the @export gdscript bug, Godot VRM master branch is now up-to-date and works on godot master (4.x). Currently working on getting the reins on 3.x and backporting some of the bugfixes\n2021-05-05 12:52:45Z lyuma: Akien uses a stupid reason to argue against https://github.com/godotengine/godot/pull/48014\n2021-05-04 22:02:14Z fire: Oops stupid, I didn’t enable parent to child for EWBIK\n2021-05-04 16:34:46Z fire: The idea is to run scripts on the os using ebpf to probe an active system. EBpf is similar to Sun DTrace and made by the same people.\n2021-05-04 16:34:15Z fire: Discovered: https://pixielabs.ai/ Apache 2 CNCF project. Access metrics, events, traces and logs in seconds without changing code via dynamic eBPF probes and ingestors.\n2021-05-04 16:15:03Z fire: Debugged with Eron EWBIK. No conclusions.\n2021-05-04 14:52:02Z fire: “Next steps on EWBIK: The stiffness constraint of a bone determines how much the IK solver should prefer to avoid rotating it if it can. The kusudama constraint limits rotation and twist.”\n2021-05-04 13:01:11Z fire: https://github.com/godotengine/godot/pull/47389#issuecomment-830588813 Saracen Please respond to wave importer review\n2021-05-04 12:59:10Z fire: “Still working on getting tokage’s prs merged (ping pong) https://github.com/godotengine/godot/pull/48332 (discrete carry) https://github.com/godotengine/godot/pull/48375”\n2021-05-04 12:55:38Z fire: Porting https://github.com/fire/godot/tree/2d-ik but need to ask pouley something\n2021-05-04 05:30:19Z lyuma: music?\n2021-05-04 05:28:37Z fire: V-Sekai music discussion.\n2021-05-04 01:29:11Z fire: rafallus EWBIK meeting time. Meeting done. Discussed the instability when the target is close and with multiple targets. Investigated future implementation of Kusudama constraints. Described a way to turn off ewbik constraints in the Java demo.\n2021-05-03 21:25:19Z fire: Godot Vulkan now runs a software renderer (for now SwiftShader) on cicd. Thanks qarmin.\n2021-05-03 21:24:38Z fire: https://github.com/godotengine/godot/pull/48410\n2021-05-03 21:23:55Z fire: PSA - We run godot –doctool in the Linux build, so if you modify the public API but fail to update the documentation, it will throw an error: So remember to run –doctool.\n2021-05-03 21:20:13Z fire: Fetching 2d IK PR for tomorrow.\n2021-05-03 21:19:37Z fire: Updated lottie to use zstd packedscene compression because vram compression is bad.\n2021-05-03 20:28:02Z fire: Trying to see if power of two resize will solve a crash on etcpak compressing for Lottie. It does.\n2021-05-03 20:19:20Z fire: Updated lottie https://github.com/godot-extended-libraries/lottie/tree/next to use texture compression (1GB to 10MB) and change skipping frames which was cursed to a interpolation scheme where the input is frame rate and not skipped frames.\n2021-05-03 19:10:40Z fire: Discussed with Lyuma about so many Godot Engine bugs to fix. gdparty (1)\n2021-05-03 16:06:57Z lyuma: Implemented support for unity binary asset format into Unidot Importer (such as LightingData.asset) - note that the actual data in this file isn’t used yet, but now we can parse these files.\n2021-05-03 12:09:06Z fire: Scheduled a meeting with rafallus about ewibik and working on gltf2 normalization pr.\n2021-05-02 21:09:57Z fire: &gt; wasm2c: Convert wasm files to C source and header\n2021-05-02 21:01:10Z fire: There’s an discussion about OMI and WASM again.\n2021-05-02 21:00:18Z fire: Discussed with Tylo#4997 in the OMI server, apparently we’re GLTF2 buddies. He worked on glTF2 furniture arrangements with 3d product models.\n2021-05-02 19:48:53Z fire: Reviewed https://github.com/godotengine/godot/issues/41028 with tokage “Blendspace2D BLEND_MODE_DISCRETE_CARRY freezes or doesn’t carry #41028”\n2021-05-02 15:10:07Z fire: https://github.com/fire/godot/tree/bc7enc_rdo and https://github.com/simd-everywhere/simde Godot Simd proposal\n2021-05-02 01:35:12Z fire: Working on nested bone attachments that also have a skeleton\n2021-05-02 01:27:57Z fire: Lyuma We got bone attachments! 🍖 (1)\n2021-05-01 22:34:48Z fire: Add a pr. Needs review\n2021-05-01 18:59:03Z fire: Trying to deal with the case where the weights is [2, 2, 2, 2] [0.7, 0.3, 0.0, 0.0] &gt;.&lt;\n2021-05-01 16:42:28Z fire: Clamping Nans, -Inf, +Inf in gltf exporter in Godot Engine."
   },
   {
-    "objectID": "changelog/2024/20240701-changelog.html#previous-releases",
-    "href": "changelog/2024/20240701-changelog.html#previous-releases",
-    "title": "V-Sekai Changelog - July 2024",
+    "objectID": "changelog/2021/20210601-changelog.html",
+    "href": "changelog/2021/20210601-changelog.html",
+    "title": "V-Sekai Changelog - 2021-06",
     "section": "",
-    "text": "Not applicable for this month."
+    "text": "V-Sekai Changelog - 2021-06\n\n2021-06-30 17:31:02Z lyuma: Updated the GDScript migration script: https://github.com/V-Sekai/gd3to4/commit/bad3998a69273ba3b1172cead10363b7fda706cd\n2021-06-30 17:29:12Z lyuma: “Posted the MToon shader on the Godot Shaders page: https://godotshaders.com/shader/mtoon-shader-for-godot/”\n2021-06-30 09:27:28Z fire: Shaved some yaks to get the point of gltf2 export. Made 5 prs.\n2021-06-29 15:13:05Z fire: “Today I will work on:\nExpedite the SVG PR https://github.com/godotengine/godot/pull/49645\nInvestigate gltf2 export https://github.com/godotengine/godot/pull/48947 and https://github.com/fire/godot/tree/gltf-export-02\nInvestigate VOIP in Godot Engine outside of Godot Engine org tree”\n2021-06-28 03:02:32Z fire: Sent saracen an animation test\n2021-06-27 20:35:13Z fire: I wrote a 20 step instruction on how to save any pose as the rest pose. https://github.com/V-Sekai/blue-tin-fox-models/blob/master/characters/blender-save-pose-as-rest-pose.md\n2021-06-27 04:34:09Z fire: Invited a few new people this week. Say hi to LillyByte from Godot Engine Discord and mrmetaverse from OMI Group\n2021-06-24 22:57:41Z fire: https://hubs.mozilla.com/spoke/projects/new?sceneId=Rpt8DJS\n2021-06-24 22:40:50Z fire: https://github.com/MozillaReality/hubs-blender-exporter https://github.com/KhronosGroup/glTF/pull/1400 Lyuma\n2021-06-24 21:34:56Z fire: Talked with Robert from OMI about the useful of a spatial audio emitter extension. There’s also a microsoft and a mozilla hub implementation for spatial audio node in wav?, mp3? or ogg? . He had unfinished business with the extension namespace of hubs and wanted to split it.\n2021-06-23 00:19:33Z lyuma: “https://github.com/V-Sekai-godot-hop-spin-dance Don’t get your hopes up quite yet: A lot of the lower level dependencies for scene packing and t-posing are not converted yet, but the tool scripts work now, so it’s a start :-p” 🔥 (1)\n2021-06-23 00:19:07Z lyuma: Worked with fire to get the avatar conversion tool updated, using the high level vsk_avatar vsk_vrm_avatar_tool modules: https://cdn.discordapp.com/attachments/836651615532482611/857052116593803284/unknown.png\n2021-06-22 23:48:06Z lyuma: mux says they also keep hitting this issue. they also made the connection to set_name() interestingly\n2021-06-22 23:47:51Z lyuma: after a day of debugging, Saracen got a reproduction project here: https://github.com/godotengine/godot/issues/49843\n2021-06-22 23:22:17Z fire: Another day. Implement vrm quaternion format from lox9973 from ShaderMotion to move godot VRMs\n2021-06-22 21:00:23Z fire: We ported the avatar T-Poser to the point the menu popup shows and checkpointed, then concluded for lunch. Multiple modules were ported.\n2021-06-22 20:56:35Z fire: https://github.com/godotengine/godot-proposals/issues/2903 Lyuma wrote a proposal\n2021-06-22 17:33:46Z fire: “Did a 5 minute design for libcurl in Godot Engine. Use https://github.com/OpenAPITools/openapi-generator/tree/master/modules/openapi-generator/src/main/resources/C-libcurl as a template.”\n2021-06-22 17:22:01Z fire: Defined a mantra for groups: Presence with custom avatars and custom worlds.\n2021-06-22 15:55:37Z fire: Updated https://github.com/godotengine/godot/pull/49645 CICD Passes https://cdn.discordapp.com/attachments/836651615532482611/856925406166515722/unknown.png\n2021-06-21 13:24:31Z fire: Did I do this wrong? A vs B cs C https://imgsli.com/NTgzMDk/1/2\n2021-06-21 12:40:26Z fire: Good news, the gd_util, math_util and vsk_avatar plugin enables. Now to test it.\n2021-06-21 03:30:21Z fire: Updated godot-vrm to latest master. https://github.com/V-Sekai/godot-vrm/tree/master 👍 (1)\n2021-06-20 23:44:26Z Saracen: More fixes to be compatible with the latest master branch. Also making more bug reports for serious issues I encounter 🐛 (1),👍 (1)\n2021-06-20 20:29:37Z fire: It’s pretty slow like 7 seconds\n2021-06-20 20:29:23Z fire: &gt; RGBA Max error: 77 RMSE: 1.55 PSNR 44.34 dB\n2021-06-20 20:29:22Z fire: # bc7_enc_rdo\n2021-06-20 20:29:01Z Saracen: Wow, the existing one is already pretty fast. Good job!\n2021-06-20 20:28:33Z fire: “# Current (1 thread) RGBA Max error: 57 RMSE: 0.85 PSNR 49.57 dB CVTT 1024x1024 total time: 1.55 secs # Previous (1 thread) RGBA Max error: 28 RMSE: 0.43 PSNR 55.53 dB CVTT 1024x1024 total time: 35.68 secs”\n2021-06-20 20:28:32Z fire: https://github.com/fire/godot/tree/faster-cvtt Lyuma Saracen Faster BPTC compression.\n2021-06-19 22:42:58Z Saracen: I think I managed to fix the performance issue. It was a badly ported coroutine calling a heavy function continually. Still some issues with pathfinding and abilities not executing, but it’s at least actually functioning now.\n2021-06-19 19:22:18Z Saracen: Further fixes, there’s workarounds now for the tool I wrote to extract root motion. Two of the notable bugs I’ve discovered are ConfigFile.load returning random values and the fact that there doesn’t seem to be implicit casting between String and StringName. Want to create some example projects for this. It’s also worth noting that while Amethyst is close to being functional now, it’s running OBSCENELY slow at the moment. 🦥 (1)\n2021-06-19 18:01:49Z Saracen: Some more progress on the Amethyst port\n2021-06-19 07:45:39Z fire: Can now export blends to gltf2 and save as an artifact. Also installs vrm plugin.\n2021-06-19 07:45:30Z fire: https://github.com/V-Sekai/blue-tin-fox-models\n2021-06-19 00:16:57Z fire: Discussed with Saracen and Acquaintances to add a female mannequin to add colored characters.\n2021-06-18 21:01:16Z fire: https://github.com/godotengine/godot/pull/49717\n2021-06-18 20:15:22Z lyuma: That’s a bug with shadow mesh actually\n2021-06-18 20:14:42Z fire: https://github.com/godotengine/godot/issues/49706\n2021-06-18 10:29:49Z lyuma: https://cdn.discordapp.com/attachments/836651615532482611/855393862876790804/avp_living.jpg\n2021-06-18 10:28:07Z lyuma: There are still things missing, of course: for example, some materials like the walls use a custom shader with nonstandard property names… but the overall scene structure does get imported! 👏 (3)\n2021-06-18 10:27:51Z lyuma: I’m proud to announce that Unidot Importer was finally able to import the “Vol. 6” AirBnB House without any major errors! https://cdn.discordapp.com/attachments/836651615532482611/855393367545085983/unknown.png\n2021-06-17 22:53:22Z fire: 2 visual script godot engine prs merged\n2021-06-17 17:01:09Z fire: !!!\n2021-06-17 16:59:42Z Saracen: I pushed an experimental branch of Amethyst designed to work in 4.0 upstream to a new branch. The behavior tree is still broken though.\n2021-06-16 23:24:26Z fire: https://github.com/fire/godot/tree/bc7enc_rdo Updated\n2021-06-16 23:23:49Z fire: https://github.com/godotengine/godot/pull/49669 Lyuma not sure if it’s the crash\n2021-06-16 17:55:57Z fire: OMI meeting notes.\n2021-06-16 17:54:58Z fire: https://cdn.discordapp.com/attachments/836651615532482611/854781112055234561/June_16th_2021_OMI_Meeting.pdf\n2021-06-16 17:52:52Z fire: ThorVG made bugfixes to my failure code.\n2021-06-16 07:18:45Z fire: Got very sidetracked. Also implemented ThorVG to compare.\n2021-06-14 16:30:44Z fire: Code review from Blender for faster baking performance\n2021-06-14 16:30:09Z fire: https://github.com/godotengine/godot/pull/49601 PR for SVG module.\n2021-06-13 02:50:12Z fire: Woke up with a dream. openseeface as a body tracker. https://github.com/you-win/openseeface-gd/issues/16\n2021-06-13 02:44:32Z fire: Related to the comic book reader idea for vr\n2021-06-13 02:39:39Z fire: I wrote a SVG module for godot engine https://github.com/sammycage/lunasvg/issues/47\n2021-06-12 22:26:57Z fire: I think I’m breaking lyuma’s server\n2021-06-12 22:26:21Z fire: Godot Engine 4 and Groups 4.x builds have been flowing for the last day or so on itchio\n2021-06-12 22:16:36Z fire: Chatted with youwin with Lyuma and did work on gdopenseeface, gltf and godot-vrm\n2021-06-12 22:16:09Z fire: Chatted with https://twitter.com/CaptainProton42 and joined a few repositories\n2021-06-11 22:07:17Z fire: https://github.com/Tom94/tev !\n2021-06-11 03:46:06Z lyuma: Updated the @export fix for a third time. It’s amazing how many different ways there are to fix bit operations on a single line of code\n2021-06-11 03:45:26Z lyuma: Updated shader_improvements_meta_3.x branch for latest 3.x godot so someone could try SCSS (I want to keep it for historical purposes). I’m not going to update 4.x because it’s in flux and too much churn with renames to keep anything working\n2021-06-11 03:44:54Z lyuma: Found a bug in MToon, related to a line of code that flips the normal if it’s pointing backwards from the view direction (you can see this if you look at an MToon face with custom normals from a sharp direction).\n2021-06-10 22:56:30Z fire: Restoring the CICD builds for godot 4. I did the changes, but currently verifying that it builds on Groups 4.x and then I’ll try github.com/godotengine@master\n2021-06-10 03:11:20Z fire: https://cdn.discordapp.com/attachments/845777129605300255/852383622606094346/unknown.png https://cdn.discordapp.com/attachments/845777129605300255/852383560882323487/unknown.png I tested compute graphs earlier. This is is the important part. I can now start a github action, start a kubernetes server, start a argo server, start an alpine linux image, have a whale message a hello world and then save it as a file and have it be download as a github artifact\n2021-06-09 20:50:29Z lyuma: “I tried baking lighting in the”“AirBNB”” and ran into this error: &gt; WARNING: Inconsistency found in triangulation while building BSP, probe interpolation quality may degrade a bit. &gt; at: LightmapGI::_compute_bsp_tree (scene\\3d_gi.cpp:460) &gt; &gt; Jfons informed me it is an issue with separating tetrahedrons. The scene has 2641 light probes so there’s probably something suspect there. I’ll have to look into it further. I think I have an idea: we have to make sure there are probes above and below to form a complete tetrahedron”\n2021-06-09 20:49:09Z lyuma: “Summary about lightmap UV problem: Mesh scale & import scale matters when dealing with lightmaps. There were bugs reading the scale, but now that is fixed and the issue with losing polygons will only happen on triangles with 1e-7 edge length in world space.\n\nThe issue with removing mesh edges still exists, in theory, but in practice it seems unlikely so let’s wait and see if it shows up in the wild and then we can take another look”\n\n2021-06-09 18:09:18Z lyuma: https://cdn.discordapp.com/attachments/836651615532482611/852248004215570432/unknown.png\n2021-06-09 18:07:18Z lyuma: Due to a glitch in Godot’s etcpak implementation, I had to use BPTC texture compression. It took 3-4 hours to compress all the textures :-p (I can’t use uncompressed textures because VRAM isn’t free and I don’t own a 3090) godette (1)\n2021-06-09 18:06:25Z lyuma: so it’s bound to improve further. it’s pretty fun seeing this place come together\n2021-06-09 18:06:04Z lyuma: A lot of objects are missing material assignments due to naming rules (for example ” - ” or ” #” in filenames\n2021-06-09 18:05:39Z lyuma: I know it’s not the v-sekai 4.x port but I took a break from it to work a bit more on fixing import issues: https://cdn.discordapp.com/attachments/836651615532482611/852247085931298896/unknown.png\n2021-06-09 13:44:28Z fire: https://github.com/godotengine/godot/pull/49458#event-4864988341 Lyuma\n2021-06-08 16:57:57Z fire: Blank screen\n2021-06-08 16:57:53Z fire:\n\nOpenVR: initializing OpenVR context Application in scene (normal) mode. Main OpenVR interface has been initialized Main render models interface has been initialized. Exec path: C:/Users/XXXX/Desktop/groups-4.x/godot/bin\n\n2021-06-08 16:04:42Z fire: Fell asleep doing Quat and Transform3D renames\n2021-06-08 12:25:39Z fire: “Need to build godot, then copy the generated files for GDNative. --gdnative-generate-json-api api.json --gdnative-generate-json-builtin-api builtin_api.json”\n2021-06-08 10:22:22Z fire: Lyuma Openvr godot 4\n2021-06-08 10:21:49Z fire: fire build godot using:\n\ngodot#49301\nThen build the plugin with:\ngodot_openvr#123\nMake sure to use vnens godot-cpp and copy all the gdnative headers and stuff into place from your godot build”\n\n2021-06-08 02:36:48Z fire: Lyuma Saracen MMMaellon https://cdn.discordapp.com/attachments/836651615532482611/851650948467916810/unknown.png 👍 (1),VRDude (2)\n2021-06-07 19:44:27Z fire: https://github.com/godotengine/godot/pull/49401 PR\n2021-06-07 07:02:52Z fire: Made a release of FBX2glTF https://github.com/V-Sekai/FBX2glTF/releases/tag/v2021-06-07T06_5500_00\n2021-06-06 16:20:36Z fire: ✨ Silent’s Birthday Party. Cake, Shrine and 15 fps. Someone mentioned there was a guest list of a hundred.\n2021-06-04 14:59:40Z fire: My first Blender pr. ✨ https://developer.blender.org/D11502/new/ 👍 (1)\n2021-06-03 22:27:31Z fire: Lyuma lots of things changed today. Including Transform -&gt; Transform3D\n2021-06-03 14:55:15Z fire: Meeting done.\n2021-06-03 12:59:57Z fire: “Lyuma Saracen MMMaellon PR review meeting on https://meet.jit.si/godot-pr-review in 5 min, everyone welcome. We’ll bikeshed about”“breaks compat”” PRs for 4.0 (mostly renaming stuff in the API, etc.)”\n2021-06-03 04:47:29Z fire: ”\ndiff --git a/source/blender/io/collada/AnimationExporter.cpp b/source/blender/io/collada/AnimationExporter.cpp\nindex 73952b06bc9..3679dd090b4 100644\n--- a/source/blender/io/collada/AnimationExporter.cpp\n+++ b/source/blender/io/collada/AnimationExporter.cpp\n@@ -100,6 +100,10 @@ bool AnimationExporter::exportAnimations()\n    openLibrary();\n\n    BCObjectSet::iterator it;\n+\n+#ifdef WITH_OMP\n+#pragma omp parallel for\n+#endif\n    for (it = animated_subset.begin(); it != animated_subset.end(); ++it) {\n        Object *ob = *it;\n        exportAnimation(ob, animation_sampler);``` 15 minutes to 5 minutes gltf2 anim export.\n2021-06-02 20:39:33Z fire: Lyuma Any thoughts on making Mousse a VRM? I’m stuck. Meshes are not exporting from Blender. Compiling Blender 2.93 (LTS) for debugging.\n2021-06-02 20:19:18Z fire: Wasm GDNative and Godot Engine will be evaluated in future releases https://twitter.com/nonunknown3/status/1400090487005011970?s=20\n2021-06-02 20:14:14Z fire: / Blender 2.93 is out https://www.blender.org/download/releases/2-93/ https://twitter.com/i/status/1373384489146142720\n2021-06-02 19:03:14Z fire: Worked with Lyuma with posting a comment about small and bigger than [-1, 1] weights on blend shapes. Will send it off to the rendering team and we’re punting it.\n2021-06-02 15:08:21Z fire: Spent an hour debugging gltf2 blend shapes. 💤 Conclusion, blender export bug in 2.91 (stable is 2.92)\n2021-06-01 15:03:23Z fire: lottie -&gt; zstd compressed packaged scene (online)\n2021-06-01 15:03:08Z fire: inkscape -&gt; lottie -&gt; saved in an ordered list container with zstd (all offline). .cb7l\n2021-06-01 14:41:05Z fire: Investigating a path where we do pdf -&gt; svg (vectors and raster images) -&gt; lottie (vectors and raster images)\n2021-06-01 13:43:29Z fire: Finding libraries that does pdf https://github.com/reMarkable/pdfium-binaries https://pdfium.googlesource.com/pdfium/+/HEAD/docs/getting-started.md pdfium page as_image\n2021-06-01 06:25:26Z lyuma: https://twitter.com/VSekaiOfficial/status/1399608449101484032"
   },
   {
-    "objectID": "decisions/20231229-byobu.html",
-    "href": "decisions/20231229-byobu.html",
-    "title": "Proposed: Byobu terminal multiplexer",
+    "objectID": "changelog/2021/20210901-changelog.html",
+    "href": "changelog/2021/20210901-changelog.html",
+    "title": "V-Sekai Changelog - 2021-09",
     "section": "",
-    "text": "Status: Proposed \nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nIn the world of software development, having a robust and user-friendly terminal environment is crucial. Developers often need to manage multiple terminal sessions at once, which can be challenging without the right tools.\n\n\n\nThe challenge is to find a usable terminal multiplexer that can handle multiple terminal sessions efficiently and effectively.\n\n\n\nOur strategy is to use Byobu, a GPLv3 open source text-based window manager and terminal multiplexer. It was chosen for its ease of use and robust feature set.\n\n\n\nBy using Byobu, developers can easily manage multiple terminal sessions from a single interface. This can greatly improve productivity and efficiency.\n\n\n\nAs with any tool, there may be a learning curve associated with Byobu. However, its benefits far outweigh this minor inconvenience.\n\n\n\nOther options like Screen and tmux were considered but found not as user friendly. Tmux, in particular, didn’t correctly scroll and did not advertise the option to start on terminal.\n\n\n\nWhile Byobu is an excellent tool for managing multiple terminal sessions, it may not be necessary for developers who only occasionally need to work with multiple terminals.\n\n\n\nThis decision to use Byobu is part of our core strategy to provide the best tools and environment for our developers.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
+    "text": "V-Sekai Changelog - 2021-09\n\n2021-09-30 18:33:19Z fire: Saracen https://github.com/godotengine/godot/pull/52210 https://cdn.discordapp.com/attachments/836651615532482611/893203877367779408/unknown.png\n2021-09-30 01:28:33Z fire: https://www.youtube.com/watch?v=Dp42lQYVzwo&t=47s\n2021-09-29 22:12:20Z fire: Holoplay initial commit https://github.com/CaptainProton42/GodotHoloPlayExtension\n2021-09-29 22:08:01Z fire: “Fales 12:31 PM Okay peeps, I got the WebRTC plugin for 4.0 to build on all platforms (and most architectures): https://github.com/Faless/webrtc-native/actions/runs/1288153747 .” 👍 (1)\n2021-09-29 21:39:33Z fire: Closed 6 bugs related to 53114\n2021-09-29 21:03:56Z fire: https://github.com/godotengine/godot/pull/53114 Merged\n2021-09-29 20:23:20Z lyuma: “Posted the glTF export bugfix for review. Fixes blend shapes, skeletons and nested bone attachment hierarchies: https://github.com/godotengine/godot/pull/53114”\n2021-09-29 10:10:12Z lyuma: Successfully exported a glTF model with multiple surfaces and blend shapes: https://cdn.discordapp.com/attachments/836651615532482611/892714872012406794/unknown.png kickass (2)\n2021-09-28 22:34:20Z fire:  has entered the discussion\n2021-09-28 22:33:40Z fire: Spent some time at OMIGROUP discussing OMI-WASM-ECS\n2021-09-28 16:33:48Z fire: https://twitter.com/mux213/status/1442820373322420224?s=20 😎 (2)\n2021-09-28 16:25:34Z fire: Updated https://github.com/V-Sekai/godot/tree/export_skin_fixes to master\n2021-09-27 21:24:18Z fire: &gt; From reduz all would you be up for an animation meeting tomorrow?\n2021-09-27 19:30:01Z fire: point to child and point to global as a skeleton modifier. just dreamed this. Per frame 😱\n2021-09-27 17:03:16Z fire: https://github.com/GodotVR/godot_xr_reference\n2021-09-27 15:31:37Z lyuma: “Nice blog post by Mux about GDExtension! A good read: https://godotengine.org/article/introducing-gd-extensions Maybe we can try making one of these for VRM springbone” 👍 (2)\n2021-09-27 14:32:29Z fire: Wrote down a bake miku miku motion workflow. With a rebased 3.x (not 3.3) we can export the baked scene with a manual step to delete the face / blendshapes. Remember to copy both the reset and the transferred anim. Then in 4.0 import and put it on the original vrm. Enable RESET bake.\n2021-09-27 14:26:53Z fire: Reviewed godot-tests pr and had some comments. Added a comment to fix export of skeletons and skins. Tested the export more. Noted a weird issue where if the blend was animated it would cause the blend shape to be exported wrong. Like a shape mouth blend set to 1.0 and looking in blender\n2021-09-27 14:25:36Z fire: Approved gltf2 making light activate again. Discussed IK with Eron and on VRM rests.\n2021-09-27 12:51:50Z fire: I exported the scene from your pr. Testing it with joy set to 1. https://cdn.discordapp.com/attachments/836651615532482611/892030776210780210/unknown.png\n2021-09-27 07:18:36Z fire: godot-tests? ✅ (1)\n2021-09-27 07:18:31Z fire: Lyuma want to add cursed hat to the models repo?\n2021-09-27 07:01:50Z lyuma: Pushed pull request https://github.com/godotengine/godot/pull/53114 to address gltf skin and skeleton objects being generated at the wrong time during the export process. Still in draft state because it needs more testing.\n2021-09-26 11:28:12Z Saracen: https://github.com/godotengine/godot/pull/53086 🐱 (2)\n2021-09-24 18:21:54Z fire: Ellenhp discussion about HRTF audio in the audio channel in chat.godotengine.org.\n2021-09-24 14:59:37Z fire: Good news everyone. https://twitter.com/yunayuna64/status/1441288908659048453\n2021-09-23 22:43:33Z lyuma: “Just resolved yet another server downtime. It was down overnight because I was unavailable to investigate due to an appointment. Cause for failure: Fedora (without NetworkManager?) defaults to non-daemonized dhclient and allowed the dhcp lease to expire.\n\nTo prevent future disruption, I have implemented both mitigations outlined in this helpful ServerFault answer! https://serverfault.com/a/291202 regrets_for_not_using_ubuntu++;”\n\n2021-09-23 21:28:31Z fire: https://github.com/V-Sekai/godot-vrm/issues/23 👍 (1)\n2021-09-23 09:02:30Z lyuma: in terms of ui, is VisualScript good?\n2021-09-23 09:02:13Z lyuma: “co-opting this channel to discuss the AnimationTree draft proposal &gt; https://docs.google.com/document/d/1mkGjnj8VzCJmZS2x6l6qMVvemylGR2OPYq4hF-sTPRI/edit?usp=sharing\n\nI think the overall design is great. we are wondering how to configure the variables”\n\n2021-09-22 19:42:40Z fire: VMD to VRM Dance https://cdn.discordapp.com/attachments/836651615532482611/890322222042976286/2021-09-22_12-03-13.mp4 👍 (3)\n2021-09-21 01:25:13Z fire: First draft of new updated extensions api. https://github.com/godotengine/godot/pull/52802 Lyuma\n2021-09-20 23:21:50Z lyuma: Cool\n2021-09-20 23:19:13Z fire: Chatted with Robert. Proposed design to do the import_node and import_scene APIs as a first pass for the OMI_audio_emitter extension. Can fallback to post hook.\n2021-09-20 22:44:46Z lyuma: ImporterMeshInstance3D. Nice that is moving out of the Editor namespace, and less typing\n2021-09-20 22:44:11Z fire: https://cdn.discordapp.com/attachments/836651615532482611/889643129525907546/unknown.png\n2021-09-20 19:50:39Z fire: gltfdocument extensions works I think. next steps 1) review 2) merge 3) update godot-vrm. for now. khajit needs food\n2021-09-20 19:31:58Z fire: false success &gt;.&gt;\n2021-09-20 16:57:12Z fire: &gt; reduz: it should only check whether its the same for vertex, normal and tangent\n2021-09-20 12:26:23Z fire: openvr\n2021-09-20 12:26:06Z fire: and after you compile it make sure you create a new extensions_api.json and copy the gdnative_extensions.h file into the godot-cpp of the plugin\n2021-09-20 12:25:53Z fire: https://github.com/BastiaanOlij/godot/tree/xr_extension_return_buffers\n2021-09-19 04:43:53Z fire: Contacted moody he wanted to get scons ninja and scons shared libraries done. there are new prs needing review\n2021-09-19 04:33:10Z fire: Lots of headless crash bugs\n2021-09-19 04:13:07Z fire: https://cdn.discordapp.com/attachments/836651615532482611/889001129877340160/unknown.png 😩 (1)\n2021-09-19 03:23:59Z fire: Next up. rebuild GDExtension Openvr\n2021-09-19 03:18:41Z fire: Spending some time checking CICD still works. Updated misc. See logs on pipeline https://github.com/V-Sekai/groups-gocd-pipelines/\n2021-09-18 19:32:11Z lyuma: “Updated cluster install directions to account for the recent changes seeing remote ip; cockroachdb not from helm; and disabling eviction: https://github.com/V-Sekai/v-sekai-proposals/blob/master/docs/decisions/20200602-manage-backend-with-k3s.md”\n2021-09-18 18:48:46Z lyuma: “Our server was down for 4 hours due to a kubernetes misconfiguration (one of the options was reverted to default by mistake when changing the network metallb options):\n\nTo correct, I edited /etc/systemd/system/k3s.service and changed the ExecStart lines to:\nExecStart=/usr/local/bin/k3s \\\n    server \\\n        '-o' \\\n        '/root/.kube/config' \\\n        '--default-local-storage-path' \\\n        '/kube/pvc' \\\n        '--disable=traefik' \\\n        '--disable=servicelb' \\\n        '--disable=flannel' \\\n        '--disable=cni' \\\n        '--kubelet-arg=eviction-soft=memory.available&lt;0%,imagefs.available&lt;0%,nodefs.available&lt;0%' \\\n        '--kubelet-arg=eviction-hard=memory.available&lt;0%,imagefs.available&lt;0%,nodefs.available&lt;0%' \\\n\n2021-09-18 12:41:48Z fire: “&gt; WOW…. workarounds galore and its not pretty, and it crashes badly when you exit Godot, but OpenVR is breathing life and renders to the headset now. That means that the system at its core is working and we’re now at a stage of fixing bugs (well I still need to finish the changes to controllers).\n\n\nFor OpenXR there is far more work to do because there currently isn’t any support for rendering to texture chains supplied by the plugin and I’m only about halfway through converting all the code. I plan to do more on that conversion tomorrow as I wait for things to be fixed in Godot before I can take the next steps with OpenVR.”\n\n\n2021-09-18 12:41:23Z fire: &gt; mux\n2021-09-18 03:58:34Z fire: https://github.com/godotengine/godot/pull/52802\n2021-09-18 01:04:23Z fire: https://cdn.discordapp.com/attachments/836651615532482611/888591247835541584/unknown.png\n2021-09-18 01:04:19Z fire: first draft design of GLT2DocumentExtensionEditor\n2021-09-17 07:07:15Z fire: https://twitter.com/VR_Rosie/status/1438600868245426180?s=20\n2021-09-16 16:24:13Z fire: Added https://github.com/godotengine/godot-proposals/issues/3305 and updated https://github.com/godotengine/godot-proposals/issues/3273\n2021-09-16 06:28:45Z fire: “Lyuma Saracen When I wake up tomorrow I’m going to be hyped and implement https://hackmd.io/37S0FGw7TruwjiLIspl8vQ. I think the proposal is ready to go. Please read and comment.”\n2021-09-15 15:58:29Z fire: https://twitter.com/bjornornorn/status/1435607551031357443?s=20 🆗 (1)\n2021-09-15 15:57:26Z fire: “Having fun with shaders, but gotta go do errands. Trying to make the circle fit the box. Might need some help https://github.com/V-Sekai/godot/tree/ok_color”\n2021-09-15 15:57:09Z fire: https://cdn.discordapp.com/attachments/836651615532482611/887728757702537247/unknown.png\n2021-09-15 00:43:01Z fire: Devise a workflow for https://github.com/godotengine/godot/pull/49775#issuecomment-919608377\n2021-09-14 18:23:20Z fire: https://hackmd.io/37S0FGw7TruwjiLIspl8vQ\n2021-09-14 17:18:20Z fire: &gt; Discussion this morning with Reduz to unify the Ref&lt;GLTFDocument&gt; api. &gt; &gt; - load_file(), load_buffer() that just generates the internal state, and save_file and save_buffer functions that save back the files. &gt; - parse_scene(Node*) generates the internal state from a Node* scene. And Node* write_scene() writes it out &gt; &gt; Expose a Vector&lt;Ref&lt;GLTFDocumentExtension&gt;&gt;”\n2021-09-14 17:17:39Z fire: https://github.com/godotengine/godot/pull/52541#issuecomment-919353368 Lyuma, Saracen, MMMaellon, Silent. Feedback requested on GLTFDocument api.\n2021-09-14 07:23:22Z fire: Four Godot 4 prs on my list – 1) libcurl complete the pr and not be at 98% 2) core based gltf i/o 3) svg 4) cvtt\n2021-09-13 22:44:02Z fire: https://cdn.discordapp.com/attachments/836651615532482611/887106377716224000/2021-09-13_15-42-22.mp4 👏 (4)\n2021-09-13 22:33:29Z fire: https://github.com/TwistedTwigleg/Godot_GSOC_2020_Project/tree/IK_Modification_Fix Updated Skeleton Modifier example code Saracen\n2021-09-13 19:07:30Z fire: Put https://github.com/godotengine/godot/pull/52541 for review again.\n2021-09-13 19:07:11Z fire: Godot Meson updates https://github.com/godotengine/godot/pull/52311#issuecomment-918474496\n2021-09-13 11:08:54Z fire: “Contacted Eron and sent demo materials. https://ifiregames.itch.io/chibifire-godot-4-custom-engine https://github.com/V-Sekai/godot-ik-tests”\n2021-09-13 11:08:14Z fire: Can’t sleep so updated the skeleton modification demo https://github.com/godotengine/godot-demo-projects/issues/649\n2021-09-11 17:59:00Z fire: Eron was interested in ewbik on sunday\n2021-09-11 16:37:08Z fire: https://github.com/V-Sekai/godot-vrm/issues/22\n2021-09-11 16:32:05Z fire: Lyuma I updated godot engine to remove PackedSceneGLTF. The changes will be posted in a bit for godot-vrm\n2021-09-09 17:50:45Z fire: 👀 https://www.vrfocus.com/2021/09/ray-ban-stories-is-facebooks-299-entry-into-the-smart-glasses-market/\n2021-09-08 17:24:52Z fire: Lyuma Saracen from reduz &gt; fire it looks good. We got quite a lot of demand to make the GLTF importer part of core, given it is needed for VR and other stuff, so I have the feeling we should optimize it for performance (which we should do anyway) and have an option to load actual meshes instead of EditorImporterMesh.. so that means we would need to provide a function to parse the mesh node into a scene node and the editor supplies, otherwise it uses Mesh as a default\n2021-09-07 18:32:54Z fire: Miku Base Textures https://cdn.discordapp.com/attachments/836651615532482611/884868837978288178/unknown.png\n2021-09-07 18:02:00Z fire: Miku Miku Dance now split into materials. https://cdn.discordapp.com/attachments/836651615532482611/884861074648760380/unknown.png 👍 (2)\n2021-09-07 16:39:33Z トカゲ: “fixed skinning https://github.com/godotengine/godot/pull/52462”\n2021-09-07 05:53:14Z fire: https://cdn.discordapp.com/attachments/836651615532482611/884677671563460639/unknown.png\n2021-09-07 02:10:09Z fire: Trying to write down steps to make a V-Sekai/godot update\n2021-09-06 00:25:10Z fire: https://cdn.discordapp.com/attachments/836651615532482611/884232728839606284/kaitai_mmd_pmx.zip\n2021-09-06 00:24:45Z fire: https://github.com/kaitai-io/kaitai_struct_formats/pull/446 Lyuma Thanks to Hakanai I can now generate mmd_pmx c++/stl via & 'C:\\Program Files (x86)\\kaitai-struct-compiler\\bin\\kaitai-struct-compiler.bat' --cpp-standard=11 --target=cpp_stl .\\3d\\mmd_pmx.ksy -I=. --cpp-namespace kaitai_mmd_pmx Also glb binary has a parser for read and write too. Can also do fbx!?!!!! Also tscn, scn, tres and res mikuleek (3)\n2021-09-06 00:09:07Z トカゲ: “Child class of EditorProperty’s read_only property has been implemented correctly https://github.com/godotengine/godot/pull/51722” https://cdn.discordapp.com/attachments/836651615532482611/884228687992594482/2021-09-06_9.07.35-1.mov 👍 (2)\n2021-09-04 02:10:44Z fire: GLTF Skeletons\n2021-09-04 01:30:12Z lyuma: We found an infinite recursion bug in the godot gltf exporter caused by the construction of gltf node objects from skeletons and skins. I believe the issue is treating skeletons as special objects, and if we expand skeleton bones to nodes initially that should simplify things greatly and prevent this type of bug.\n2021-09-03 22:23:17Z fire: use vnen’s fix to replace saracen’s auto load fix\n2021-09-03 15:36:00Z fire: If you were crashing Godot Engine when opening vrms, it’s a Nvidia driver bug. Please update.\n2021-09-03 08:10:01Z lyuma: This was all imported using Unidot on godot 4.x (with progress bar patch :-p)\n2021-09-03 08:09:11Z lyuma: https://cdn.discordapp.com/attachments/836651615532482611/883262336243216424/rin_himeji_lineup.png FeaturingDanteFromTheDevilMayCry (1)\n2021-09-03 08:09:06Z lyuma: Fixed material searching logic for legacy materials. There are some issues with material ordering, but most scenes now import with the correct materials! https://cdn.discordapp.com/attachments/836651615532482611/883262312969011250/rin_himeji_diorama2.png\n2021-09-03 08:08:15Z lyuma: https://cdn.discordapp.com/attachments/836651615532482611/883262098942079026/archery_sample.png\n2021-09-02 03:56:26Z lyuma: “Progress on Unidot Importer: I made some major fixes on binary asset deserialization: I finally figured out how padding works (short answer: flag 0x4000 adds padding after a byte or short), and fixed a crash by implementing support for Unity 4.x and earlier assets, since you never know where they will show up.\n\nNext up is parsing the texture filename mapping from FBX files to assist in material discovery, since Unity legacy materials default to lookup by texture filename rather than material name or texture name. Since Godot has no means for preserving the original filename on import when the files are not present, doing a fix to the FBX2glTF tool won’t quite cover my necessary usecase, so I think extracting the map in the tooling is easiest. Will probably revisit this decision later.” 👍 (4)\n\n2021-09-02 01:27:40Z fire: https://twitter.com/babylonjs/status/1433216048036122629?s=20 webgpu\n2021-09-01 21:26:59Z fire: \n2021-09-01 15:39:17Z fire: Tried to get additional screenshots to work https://github.com/godotengine/godot/pull/52316\n2021-09-01 14:53:33Z fire: Worked with ellenhp on a proposal on import, to extract all the vorbis packets and just decode vorbis so the imported file gets rid of the ogg container. This is to remove stb_vorbis because of its documented crashing nature. Has preapproval from reduz."
   },
   {
-    "objectID": "decisions/20231229-byobu.html#metadata",
-    "href": "decisions/20231229-byobu.html#metadata",
-    "title": "Proposed: Byobu terminal multiplexer",
+    "objectID": "changelog/2024/20241003-changelog.html",
+    "href": "changelog/2024/20241003-changelog.html",
+    "title": "V-Sekai Changelog - October 2024",
     "section": "",
-    "text": "Status: Proposed \nDeciders: V-Sekai\nTags: V-Sekai"
+    "text": "Experimental (🧪): This stage is for features that are still being tested and may not be stable.\nFeature complete (🎯): This stage is for features that have all planned functionality implemented.\nBeta (🚧): This stage is for features that are largely complete but may still have bugs.\nGeneral release (🚀): This stage is for features that have been fully tested and are now released.\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\n\n\n🎯 https://gonzerelli.itch.io/demo - fwsgonzo decided to embed LuaJIT to Godot Sandbox as a proof-of-concept. Touching the first coin will open up a Lua “console” which redirects print() to a TextEdit\n🎯 https://gonzerelli.itch.io/demo - We enabled binary translation for LuaJIT on Godot Sandbox.\n🚀 Installed Discord on the Meta Quest 3 and was able to stream Godot Engine and ecosystem applications.\n🎯 Added a double build of steam audio\n🎯 Steam Audio now works without a custom Godot Engine fork.\n🧪 The VRM Consortium, Inc., the creator and advocate of the VRM 3D avatar file format, which is based on the glTF™ 2.0 open standard, has announced a collaboration with The Khronos Group, the developer of glTF, to advance the international standardization of VRM.\n🚀 Submitted IREE.gd to Awesome-Godot-Scientific\n🧪 Collaboration with GuilhermeGSousa/godot-motion-matching\n🚀 Found opensource animation assets. Useful bases for retargeting and also stylizing motions. O3DE MotionMatching Animation Assets\n🧪 Collaboration with maiself/godot-python-extension\n🧪 Split V-Sekai world into world_editor and world_game\n\n\n\n\n\n🚧 Try to release iree-gd for godot engine 4.3 stable. https://github.com/iree-gd/iree.gd/pull/87\n🧪 Cleanup 3d cage for porting to python. https://github.com/V-Sekai-fire/godot_cage_deformer\n🚧 Updated manifold to remove GLM - https://github.com/godotengine/godot/pull/94321\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nSecurity Best Practices:\n\nThis project does not adhere to Semantic Versioning.\n\n\n\n\n\nNot applicable for this month."
   },
   {
-    "objectID": "decisions/20231229-byobu.html#the-backdrop",
-    "href": "decisions/20231229-byobu.html#the-backdrop",
-    "title": "Proposed: Byobu terminal multiplexer",
+    "objectID": "changelog/2024/20241003-changelog.html#released",
+    "href": "changelog/2024/20241003-changelog.html#released",
+    "title": "V-Sekai Changelog - October 2024",
     "section": "",
-    "text": "In the world of software development, having a robust and user-friendly terminal environment is crucial. Developers often need to manage multiple terminal sessions at once, which can be challenging without the right tools."
+    "text": "Not applicable for this month."
   },
   {
-    "objectID": "decisions/20231229-byobu.html#the-challenge",
-    "href": "decisions/20231229-byobu.html#the-challenge",
-    "title": "Proposed: Byobu terminal multiplexer",
+    "objectID": "changelog/2024/20241003-changelog.html#unreleased",
+    "href": "changelog/2024/20241003-changelog.html#unreleased",
+    "title": "V-Sekai Changelog - October 2024",
     "section": "",
-    "text": "The challenge is to find a usable terminal multiplexer that can handle multiple terminal sessions efficiently and effectively."
+    "text": "🎯 https://gonzerelli.itch.io/demo - fwsgonzo decided to embed LuaJIT to Godot Sandbox as a proof-of-concept. Touching the first coin will open up a Lua “console” which redirects print() to a TextEdit\n🎯 https://gonzerelli.itch.io/demo - We enabled binary translation for LuaJIT on Godot Sandbox.\n🚀 Installed Discord on the Meta Quest 3 and was able to stream Godot Engine and ecosystem applications.\n🎯 Added a double build of steam audio\n🎯 Steam Audio now works without a custom Godot Engine fork.\n🧪 The VRM Consortium, Inc., the creator and advocate of the VRM 3D avatar file format, which is based on the glTF™ 2.0 open standard, has announced a collaboration with The Khronos Group, the developer of glTF, to advance the international standardization of VRM.\n🚀 Submitted IREE.gd to Awesome-Godot-Scientific\n🧪 Collaboration with GuilhermeGSousa/godot-motion-matching\n🚀 Found opensource animation assets. Useful bases for retargeting and also stylizing motions. O3DE MotionMatching Animation Assets\n🧪 Collaboration with maiself/godot-python-extension\n🧪 Split V-Sekai world into world_editor and world_game\n\n\n\n\n\n🚧 Try to release iree-gd for godot engine 4.3 stable. https://github.com/iree-gd/iree.gd/pull/87\n🧪 Cleanup 3d cage for porting to python. https://github.com/V-Sekai-fire/godot_cage_deformer\n🚧 Updated manifold to remove GLM - https://github.com/godotengine/godot/pull/94321\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nSecurity Best Practices:\n\nThis project does not adhere to Semantic Versioning."
   },
   {
-    "objectID": "decisions/20231229-byobu.html#the-strategy",
-    "href": "decisions/20231229-byobu.html#the-strategy",
-    "title": "Proposed: Byobu terminal multiplexer",
+    "objectID": "changelog/2024/20241003-changelog.html#previous-releases",
+    "href": "changelog/2024/20241003-changelog.html#previous-releases",
+    "title": "V-Sekai Changelog - October 2024",
     "section": "",
-    "text": "Our strategy is to use Byobu, a GPLv3 open source text-based window manager and terminal multiplexer. It was chosen for its ease of use and robust feature set."
+    "text": "Not applicable for this month."
   },
   {
-    "objectID": "decisions/20231229-byobu.html#the-upside",
-    "href": "decisions/20231229-byobu.html#the-upside",
-    "title": "Proposed: Byobu terminal multiplexer",
+    "objectID": "changelog/2024/20240202-changelog.html",
+    "href": "changelog/2024/20240202-changelog.html",
+    "title": "V-Sekai Changelog - February 2024",
     "section": "",
-    "text": "By using Byobu, developers can easily manage multiple terminal sessions from a single interface. This can greatly improve productivity and efficiency."
+    "text": "Not applicable for this month.\n\n\n\n\n\n\n\nUFBX Importer: Merged into Godot Engine master for version 4.3.\nUnidot Spring Bones: Spring bones now import with Unidot Importer! It’s compatible with various popular formats and supports all features of the vrm spring bone script. Currently no advanced features like axis locks or inside colliders. While the vrm script supports curves, Unity curve sampling has not been implemented yet, so each bone in the chain imports with a constant value.\ngodot-vrm: An update to godot-vrm on git has been pushed to make it easier and more straightforward to edit spring bones in the inspector.\nUnidot: A lot of bugfixes have been made to the VRM import/export, unidot import pipeline, and springbone support. It’s becoming a lot easier to import a set of assets from unitypackage including booth outfits, attach them, and then export a VRM with functional spring bones!\nGodot FBX Importer: ArchVizPro volume 6 imported with ufbx. The importer is exceptionally good, and during testing it appears to perfectly replicate the result obtained in the autodesk SDK. This means Unidot in Godot 4.3 will be able to import directly to fbx out of the box without having to go through gltf!\ngodot-whisper: Added support for real-time audio transcription within the Godot Engine, which includes enhanced compatibility for the Metal API on Apple devices and improved threading performance. (Commit: 2d85a0e update)\ngodot-steamaudio: Updated the Steam Audio integration by refactoring the build configuration and audio stream handling process. (Commit: 8f15de1 Refactor build configuration)\n\n\n\n\n\nRemove a V-Sekai-game github release and point to https://saracenone.itch.io/groups-4x\n\n\n\n\n\n2024-02-07: There was a nasty bug involving the springbone gizmo, a node rename, and a Godot bug that would corrupt the node if replace_by was called on an internal node (such as a gizmo) that was leading random meshes to disappear in godot vrm during import. Should be fixed now!\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nSecurity Best Practices:\nThis project does not adhere to Semantic Versioning.\n\n\n\n\n\n\nNot applicable for this month."
   },
   {
-    "objectID": "decisions/20231229-byobu.html#the-downside",
-    "href": "decisions/20231229-byobu.html#the-downside",
-    "title": "Proposed: Byobu terminal multiplexer",
+    "objectID": "changelog/2024/20240202-changelog.html#released",
+    "href": "changelog/2024/20240202-changelog.html#released",
+    "title": "V-Sekai Changelog - February 2024",
     "section": "",
-    "text": "As with any tool, there may be a learning curve associated with Byobu. However, its benefits far outweigh this minor inconvenience."
+    "text": "Not applicable for this month."
   },
   {
-    "objectID": "decisions/20231229-byobu.html#the-road-not-taken",
-    "href": "decisions/20231229-byobu.html#the-road-not-taken",
-    "title": "Proposed: Byobu terminal multiplexer",
+    "objectID": "changelog/2024/20240202-changelog.html#unreleased",
+    "href": "changelog/2024/20240202-changelog.html#unreleased",
+    "title": "V-Sekai Changelog - February 2024",
     "section": "",
-    "text": "Other options like Screen and tmux were considered but found not as user friendly. Tmux, in particular, didn’t correctly scroll and did not advertise the option to start on terminal."
+    "text": "UFBX Importer: Merged into Godot Engine master for version 4.3.\nUnidot Spring Bones: Spring bones now import with Unidot Importer! It’s compatible with various popular formats and supports all features of the vrm spring bone script. Currently no advanced features like axis locks or inside colliders. While the vrm script supports curves, Unity curve sampling has not been implemented yet, so each bone in the chain imports with a constant value.\ngodot-vrm: An update to godot-vrm on git has been pushed to make it easier and more straightforward to edit spring bones in the inspector.\nUnidot: A lot of bugfixes have been made to the VRM import/export, unidot import pipeline, and springbone support. It’s becoming a lot easier to import a set of assets from unitypackage including booth outfits, attach them, and then export a VRM with functional spring bones!\nGodot FBX Importer: ArchVizPro volume 6 imported with ufbx. The importer is exceptionally good, and during testing it appears to perfectly replicate the result obtained in the autodesk SDK. This means Unidot in Godot 4.3 will be able to import directly to fbx out of the box without having to go through gltf!\ngodot-whisper: Added support for real-time audio transcription within the Godot Engine, which includes enhanced compatibility for the Metal API on Apple devices and improved threading performance. (Commit: 2d85a0e update)\ngodot-steamaudio: Updated the Steam Audio integration by refactoring the build configuration and audio stream handling process. (Commit: 8f15de1 Refactor build configuration)\n\n\n\n\n\nRemove a V-Sekai-game github release and point to https://saracenone.itch.io/groups-4x\n\n\n\n\n\n2024-02-07: There was a nasty bug involving the springbone gizmo, a node rename, and a Godot bug that would corrupt the node if replace_by was called on an internal node (such as a gizmo) that was leading random meshes to disappear in godot vrm during import. Should be fixed now!\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nSecurity Best Practices:\nThis project does not adhere to Semantic Versioning."
   },
   {
-    "objectID": "decisions/20231229-byobu.html#the-infrequent-use-case",
-    "href": "decisions/20231229-byobu.html#the-infrequent-use-case",
-    "title": "Proposed: Byobu terminal multiplexer",
+    "objectID": "changelog/2024/20240202-changelog.html#previous-releases",
+    "href": "changelog/2024/20240202-changelog.html#previous-releases",
+    "title": "V-Sekai Changelog - February 2024",
     "section": "",
-    "text": "While Byobu is an excellent tool for managing multiple terminal sessions, it may not be necessary for developers who only occasionally need to work with multiple terminals."
+    "text": "Not applicable for this month."
   },
   {
-    "objectID": "decisions/20231229-byobu.html#in-core-and-done-by-us",
-    "href": "decisions/20231229-byobu.html#in-core-and-done-by-us",
-    "title": "Proposed: Byobu terminal multiplexer",
+    "objectID": "changelog/2024/20240330-changelog.html",
+    "href": "changelog/2024/20240330-changelog.html",
+    "title": "V-Sekai Changelog - March 2024",
     "section": "",
-    "text": "This decision to use Byobu is part of our core strategy to provide the best tools and environment for our developers."
+    "text": "Not applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\nGDC Demo: We attended the Game Developers Conference (GDC) in San Francisco, California, USA. We demonstrated the capabilities of the Godot Engine on an Android tablet.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nSecurity Best Practices:\n\nThis project does not adhere to Semantic Versioning.\n\n\n\n\n\nNot applicable for this month."
   },
   {
-    "objectID": "decisions/20231229-byobu.html#further-reading",
-    "href": "decisions/20231229-byobu.html#further-reading",
-    "title": "Proposed: Byobu terminal multiplexer",
+    "objectID": "changelog/2024/20240330-changelog.html#released",
+    "href": "changelog/2024/20240330-changelog.html#released",
+    "title": "V-Sekai Changelog - March 2024",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
+    "text": "Not applicable for this month."
   },
   {
-    "objectID": "decisions/20240330-cicd-gitlab.html",
-    "href": "decisions/20240330-cicd-gitlab.html",
-    "title": "Proposed: CI/CD Setup with Docker and Other Platforms",
+    "objectID": "changelog/2024/20240330-changelog.html#unreleased",
+    "href": "changelog/2024/20240330-changelog.html#unreleased",
+    "title": "V-Sekai Changelog - March 2024",
     "section": "",
-    "text": "The V-Sekai project is focused on enhancing the Godot Engine by introducing social VR capabilities. To ensure a seamless development process across various environments, we need a robust CI/CD setup. This setup should cater to the diverse platforms our developers and contributors use, including Linux, macOS, Windows, Docker, and Kubernetes clusters.\n\n\n\nOur current CI/CD setup does not efficiently cover all operating systems and environments our developers use. This leads to inconsistent build and test results across different platforms. This inconsistency hinders our ability to rapidly develop and deploy features for the V-Sekai project.\n\n\n\nTo address this, we propose registering GitLab Runners for Linux, macOS, Windows, Docker, and Kubernetes. Each runner will be configured to handle builds and tests specific to its platform. Here’s a simplified view of how each runner would be set up:\nFor Linux, macOS, and Windows Runners:\n\nInstall GitLab Runner on the respective OS.\nUse the gitlab-runner register command with the platform-specific registration token.\nConfigure the runner to use an executor appropriate for the OS (e.g., shell for Linux/macOS, PowerShell for Windows).\n\nFor Docker Runner:\n\nInstall Docker on the host machine.\nPull the GitLab Runner Docker image.\nRun the GitLab Runner container with the Docker executor.\n\nFor Kubernetes Runner:\n\nDeploy the GitLab Runner Helm chart to the Kubernetes cluster.\nConfigure the runner to use the Kubernetes executor.\nUse a registration token from the GitLab instance to link the Kubernetes runner.\n\n\n\n\n\nConsistency Across Platforms: Ensures builds and tests are consistent across all supported platforms.\nIncreased Development Speed: Faster feedback loops for developers working on different platforms.\nScalability: Kubernetes runners can dynamically scale to handle increased loads, improving CI/CD pipeline performance.\n\n\n\n\n\nMaintenance Overhead: Requires initial setup and ongoing maintenance of runners across multiple platforms.\nComplexity: Adds complexity to the CI/CD setup, especially managing different executors and environments.\n\n\n\n\n\nRelying solely on cloud-based CI/CD services. While simpler, this would not provide the level of control and customization needed for our specific development needs.\n\n\n\n\n\nHandling builds or tests that require very specific environment configurations not commonly used by the development team. These cases might still need bespoke solutions outside the standard CI/CD pipeline.\n\n\n\n\nThis initiative is core to our mission of enhancing the Godot Engine with social VR capabilities. It will be executed by the V-Sekai development team, ensuring alignment with our project’s goals and technical standards.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAssisted by Aria, your AI assistant."
+    "text": "Not applicable for this month.\n\n\n\n\nGDC Demo: We attended the Game Developers Conference (GDC) in San Francisco, California, USA. We demonstrated the capabilities of the Godot Engine on an Android tablet.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nSecurity Best Practices:\n\nThis project does not adhere to Semantic Versioning."
   },
   {
-    "objectID": "decisions/20240330-cicd-gitlab.html#context",
-    "href": "decisions/20240330-cicd-gitlab.html#context",
-    "title": "Proposed: CI/CD Setup with Docker and Other Platforms",
+    "objectID": "changelog/2024/20240330-changelog.html#previous-releases",
+    "href": "changelog/2024/20240330-changelog.html#previous-releases",
+    "title": "V-Sekai Changelog - March 2024",
     "section": "",
-    "text": "The V-Sekai project is focused on enhancing the Godot Engine by introducing social VR capabilities. To ensure a seamless development process across various environments, we need a robust CI/CD setup. This setup should cater to the diverse platforms our developers and contributors use, including Linux, macOS, Windows, Docker, and Kubernetes clusters."
+    "text": "Not applicable for this month."
   },
   {
-    "objectID": "decisions/20240330-cicd-gitlab.html#problem-statement",
-    "href": "decisions/20240330-cicd-gitlab.html#problem-statement",
-    "title": "Proposed: CI/CD Setup with Docker and Other Platforms",
+    "objectID": "changelog/2024/20240505-changelog.html",
+    "href": "changelog/2024/20240505-changelog.html",
+    "title": "V-Sekai Changelog - May 2024",
     "section": "",
-    "text": "Our current CI/CD setup does not efficiently cover all operating systems and environments our developers use. This leads to inconsistent build and test results across different platforms. This inconsistency hinders our ability to rapidly develop and deploy features for the V-Sekai project."
+    "text": "Not applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\nWebRTC: Worked on browser and native webrtc interop. https://ifiregames.itch.io/webrtc-native-web-interoperability\nlibgodot: Worked on embedding libgodot to where it doesn’t belong.\ncsg: Update csg in Godot Engine to use Manifold.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nSecurity Best Practices:\n\nThis project does not adhere to Semantic Versioning.\n\n\n\n\n\nNot applicable for this month."
   },
   {
-    "objectID": "decisions/20240330-cicd-gitlab.html#proposed-solution",
-    "href": "decisions/20240330-cicd-gitlab.html#proposed-solution",
-    "title": "Proposed: CI/CD Setup with Docker and Other Platforms",
+    "objectID": "changelog/2024/20240505-changelog.html#released",
+    "href": "changelog/2024/20240505-changelog.html#released",
+    "title": "V-Sekai Changelog - May 2024",
     "section": "",
-    "text": "To address this, we propose registering GitLab Runners for Linux, macOS, Windows, Docker, and Kubernetes. Each runner will be configured to handle builds and tests specific to its platform. Here’s a simplified view of how each runner would be set up:\nFor Linux, macOS, and Windows Runners:\n\nInstall GitLab Runner on the respective OS.\nUse the gitlab-runner register command with the platform-specific registration token.\nConfigure the runner to use an executor appropriate for the OS (e.g., shell for Linux/macOS, PowerShell for Windows).\n\nFor Docker Runner:\n\nInstall Docker on the host machine.\nPull the GitLab Runner Docker image.\nRun the GitLab Runner container with the Docker executor.\n\nFor Kubernetes Runner:\n\nDeploy the GitLab Runner Helm chart to the Kubernetes cluster.\nConfigure the runner to use the Kubernetes executor.\nUse a registration token from the GitLab instance to link the Kubernetes runner."
+    "text": "Not applicable for this month."
   },
   {
-    "objectID": "decisions/20240330-cicd-gitlab.html#benefits",
-    "href": "decisions/20240330-cicd-gitlab.html#benefits",
-    "title": "Proposed: CI/CD Setup with Docker and Other Platforms",
+    "objectID": "changelog/2024/20240505-changelog.html#unreleased",
+    "href": "changelog/2024/20240505-changelog.html#unreleased",
+    "title": "V-Sekai Changelog - May 2024",
     "section": "",
-    "text": "Consistency Across Platforms: Ensures builds and tests are consistent across all supported platforms.\nIncreased Development Speed: Faster feedback loops for developers working on different platforms.\nScalability: Kubernetes runners can dynamically scale to handle increased loads, improving CI/CD pipeline performance."
+    "text": "Not applicable for this month.\n\n\n\n\nWebRTC: Worked on browser and native webrtc interop. https://ifiregames.itch.io/webrtc-native-web-interoperability\nlibgodot: Worked on embedding libgodot to where it doesn’t belong.\ncsg: Update csg in Godot Engine to use Manifold.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nSecurity Best Practices:\n\nThis project does not adhere to Semantic Versioning."
   },
   {
-    "objectID": "decisions/20240330-cicd-gitlab.html#downsides",
-    "href": "decisions/20240330-cicd-gitlab.html#downsides",
-    "title": "Proposed: CI/CD Setup with Docker and Other Platforms",
+    "objectID": "changelog/2024/20240505-changelog.html#previous-releases",
+    "href": "changelog/2024/20240505-changelog.html#previous-releases",
+    "title": "V-Sekai Changelog - May 2024",
     "section": "",
-    "text": "Maintenance Overhead: Requires initial setup and ongoing maintenance of runners across multiple platforms.\nComplexity: Adds complexity to the CI/CD setup, especially managing different executors and environments."
+    "text": "Not applicable for this month."
   },
   {
-    "objectID": "decisions/20240330-cicd-gitlab.html#alternatives-not-chosen",
-    "href": "decisions/20240330-cicd-gitlab.html#alternatives-not-chosen",
-    "title": "Proposed: CI/CD Setup with Docker and Other Platforms",
+    "objectID": "changelog/2024/20240603-changelog.html",
+    "href": "changelog/2024/20240603-changelog.html",
+    "title": "V-Sekai Changelog - June 2024",
     "section": "",
-    "text": "Relying solely on cloud-based CI/CD services. While simpler, this would not provide the level of control and customization needed for our specific development needs."
+    "text": "Not applicable for this month.\n\n\n\n\n\n\n\nWorked on a pull request for motion blur, which included:\n\nPushing updates to the vsk-motion-blur-4.3-beta1 branch in the Godot repository.\n\nInitiated and updated a paint mixer spectral.js project in the world:main branch\nPushed an update to the mirror script at V-Sekai/avatar_vr_demo so it works in desktop mode as well as XR, and works at arbitrary aspect ratios. Thanks iFire for rubber duckying and encouraging me. Note that if you want square pixels and wish to use the screenspace mode, you need this commit V-Sekai/godot. However, it also supports using Godot’s builtin Frustum camera in non-screenspace mode where the pixels will be aligned along the plane of the mirror. See if you can spot the differences. (the skybox shader doesn’t fully support frustum mode)\nIntegrated OpenTelemetry into the codebase for enhanced debugging capabilities. This will allow developers to trace and monitor application performance in real-time, helping to identify and resolve issues more efficiently.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nBumped github/codeql-action from 3.25.6 to 3.25.7 for security best practices.\n\nThis project does not adhere to Semantic Versioning.\n\n\n\n\n\nNot applicable for this month."
   },
   {
-    "objectID": "decisions/20240330-cicd-gitlab.html#infrequent-use-case",
-    "href": "decisions/20240330-cicd-gitlab.html#infrequent-use-case",
-    "title": "Proposed: CI/CD Setup with Docker and Other Platforms",
+    "objectID": "changelog/2024/20240603-changelog.html#released",
+    "href": "changelog/2024/20240603-changelog.html#released",
+    "title": "V-Sekai Changelog - June 2024",
     "section": "",
-    "text": "Handling builds or tests that require very specific environment configurations not commonly used by the development team. These cases might still need bespoke solutions outside the standard CI/CD pipeline."
+    "text": "Not applicable for this month."
   },
   {
-    "objectID": "decisions/20240330-cicd-gitlab.html#in-core-and-done-by-us",
-    "href": "decisions/20240330-cicd-gitlab.html#in-core-and-done-by-us",
-    "title": "Proposed: CI/CD Setup with Docker and Other Platforms",
+    "objectID": "changelog/2024/20240603-changelog.html#unreleased",
+    "href": "changelog/2024/20240603-changelog.html#unreleased",
+    "title": "V-Sekai Changelog - June 2024",
     "section": "",
-    "text": "This initiative is core to our mission of enhancing the Godot Engine with social VR capabilities. It will be executed by the V-Sekai development team, ensuring alignment with our project’s goals and technical standards."
+    "text": "Worked on a pull request for motion blur, which included:\n\nPushing updates to the vsk-motion-blur-4.3-beta1 branch in the Godot repository.\n\nInitiated and updated a paint mixer spectral.js project in the world:main branch\nPushed an update to the mirror script at V-Sekai/avatar_vr_demo so it works in desktop mode as well as XR, and works at arbitrary aspect ratios. Thanks iFire for rubber duckying and encouraging me. Note that if you want square pixels and wish to use the screenspace mode, you need this commit V-Sekai/godot. However, it also supports using Godot’s builtin Frustum camera in non-screenspace mode where the pixels will be aligned along the plane of the mirror. See if you can spot the differences. (the skybox shader doesn’t fully support frustum mode)\nIntegrated OpenTelemetry into the codebase for enhanced debugging capabilities. This will allow developers to trace and monitor application performance in real-time, helping to identify and resolve issues more efficiently.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nBumped github/codeql-action from 3.25.6 to 3.25.7 for security best practices.\n\nThis project does not adhere to Semantic Versioning."
   },
   {
-    "objectID": "decisions/20240330-cicd-gitlab.html#status",
-    "href": "decisions/20240330-cicd-gitlab.html#status",
-    "title": "Proposed: CI/CD Setup with Docker and Other Platforms",
+    "objectID": "changelog/2024/20240603-changelog.html#previous-releases",
+    "href": "changelog/2024/20240603-changelog.html#previous-releases",
+    "title": "V-Sekai Changelog - June 2024",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "Not applicable for this month."
   },
   {
-    "objectID": "decisions/20240330-cicd-gitlab.html#decision-makers",
-    "href": "decisions/20240330-cicd-gitlab.html#decision-makers",
-    "title": "Proposed: CI/CD Setup with Docker and Other Platforms",
+    "objectID": "decisions/20221016-v-sekai-view-replication.html",
+    "href": "decisions/20221016-v-sekai-view-replication.html",
+    "title": "Rejected: Use view replication algorithm for multiplayer multirelay sync",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "Status: rejected\nDeciders: V-Sekai,fire,\nTags: V-Sekai,sync,view replication,\n\n\n\nSee replicate sync 100’000 entities using a solution.\n\n\n\nV-Sekai could use viewstamp replication in the context of game entity interpolation of past and current state.\nThe key insight is everything is a keyframed animation that is nearest, linear or cubic interpolated.\n\n\n\nWe assume we’re using Godot Engine 4 with float is doubles.\n\nReplicate pending property changes safely to a quorum of distributed replicas, then\ninterpolate property changes to the in-memory state.\n\nIgnore p_time too far in the future or the past as the viewstamp limit.\nT Animation::_interpolate(const Vector&lt;TKey&lt;T&gt;&gt; &p_keys, double p_time, InterpolationType p_interp, bool p_loop_wrap, bool *p_ok, bool p_backward) const\n\nACK to the client.\n\nSee also Linux io_uring (replacement for epoll).\nEverything is an interpolation event or a property state. Want to fit datastructures into 128 bytes (2 CPU cache lines).\nWe reuse the create_property data structure as the state.\n\n\nReferencing https://github.com/tigerbeetledb/tigerbeetle/blob/main/docs/DESIGN.md#data-structures.\nSee Variant bytes_to_var_with_objects (PackedByteArray bytes) and PackedByteArray var_to_bytes_with_objects (Variant variable).\n\n\ncreate_property_interpolate {\n           id: 16 bytes (128-bit)\n   past_entity_id: 16 bytes (128-bit)\ncurrent_entity_id: 16 bytes (128-bit) [to allow interpolation between different entities]\n    user_data: 16 bytes (128-bit) [optional, e.g. opaque third-party identifier to link\n        this transfer (many-to-one) to an external entity]\n     reserved: 16 bytes (128-bit) [reserved, for accounting policy primitives]\n       pending_id: 16 bytes (128-bit) [optional, required to post or void an existing but pending transfer]\n      timeout:  8 bytes (64-bit) [optional, required only for a pending transfer, a quantity of time,\n        i.e. an offset in nanoseconds from timestamp]\n        shard:  4 bytes (32-bit) [required, to enforce isolation by ensuring that all transfers\n        are between entities of the same shard]\n         code:  2 bytes (16-bit) [required, an opaque entity code describing the type\n        of the interpolation, e.g. player, map, prop]\n        flags:  2 bytes (16-bit) [optional, to modify the usage of the reserved field and for future feature expansion.]\n        value:  n bytes (n-bit) [required, variant of the past property and current property,\n        which must be the same for both properties. Uses var_to_bytes_with_objects.]\n    timestamp:  8 bytes (64-bit) [reserved, assigned by the leader before journaling]\n} = n bytes (n CPU cache lines)\n\n\n\n   create_property {\n          id: 16 bytes (128-bit)\n       user_data: 16 bytes (128-bit) [optional, opaque third-party identifier to link this account\n        (many-to-one) to an external entity]\n    reserved: 48 bytes (384-bit) [reserved for future accounting policy primitives]\n       shard:  4 bytes (32-bit) [required, to enforce isolation by ensuring that all transfers\n        are between accounts of the same ledger]\n        code:  2 bytes (16-bit) [required, an opaque entity code describing the type\n        of the interpolation, e.g. player, map, prop]\n       flags:  2 bytes (16-bit) [optional, net balance limits:\n        e.g. debits_must_not_exceed_credits or credits_must_not_exceed_debits]\n     past_interpolations_pending: n bytes (n-bit variant. Uses var_to_bytes_with_objects.)\n      past_interpolations_posted: n bytes (n-bit variant. Uses var_to_bytes_with_objects.)\n  current_interpolations_pending: n bytes (n-bit variant. Uses var_to_bytes_with_objects.)\n   current_interpolations_posted: n bytes (n-bit variant. Uses var_to_bytes_with_objects.)\n               timestamp: 8 bytes ( 64-bit) [reserved]\n} = n bytes (n CPU cache lines)\n\n\n\n\n\n\nThe code is based on robust view replication consensus algorithm theory.\nThe playback of the state machine is deterministic.\n\n\n\n\n\nMinimum of three relays.\n\n\n\n\n\nOption: Current V-Sekai replication\nRejection Reason: Can’t link servers\n\n\n\n\nEntity replication is not trivial.\n\n\n\nWe’re doing the networking layer.\n\n\n\n\nAdd a multiplayer interface and visual nodes for SceneTree replication\nLMAX Exchange Architecture\n\nLMAX (quote):\n\n\njournal incoming events safely to disk, and\nreplicate to backup nodes, then\napply these events to the in-memory state, then\nACK to the client\n\n\n\nTigerbeetle design\n\nTigerbeetle uses viewstamp replication in the context of bank ledger credit and debit.\nTigerbeetle (quote):\n\n\nreplicate incoming events safely to a quorum of distributed replicas, then\napply these events to the in-memory state, then\nACK to the client\n\n\n\nviewstamped-replication-made-famous\nvr-revisited.pdf\nTigerBeetle Discord server\nCubic interpolation\n\n\n\n\nNote that this handles both nearest interpolation and cubic (with time) interpolation.\ntemplate &lt;class T&gt;\nT Animation::_interpolate(const Vector&lt;TKey&lt;T&gt;&gt; &p_keys, double p_time, InterpolationType p_interp, bool p_loop_wrap, bool *p_ok, bool p_backward) const {\n    int len = _find(p_keys, length) + 1; // try to find last key (there may be more past the end)\n\n    if (len &lt;= 0) {\n        // (-1 or -2 returned originally) (plus one above)\n        // meaning no keys, or only key time is larger than length\n        if (p_ok) {\n            *p_ok = false;\n        }\n        return T();\n    } else if (len == 1) { // one key found (0+1), return it\n\n        if (p_ok) {\n            *p_ok = true;\n        }\n        return p_keys[0].value;\n    }\n\n    int idx = _find(p_keys, p_time, p_backward);\n\n    ERR_FAIL_COND_V(idx == -2, T());\n\n    bool result = true;\n    int next = 0;\n    real_t c = 0.0;\n    // prepare for all cases of interpolation\n\n    if (loop_mode == LOOP_LINEAR && p_loop_wrap) {\n        // loop\n        if (!p_backward) {\n            // no backward\n            if (idx &gt;= 0) {\n                if (idx &lt; len - 1) {\n                    next = idx + 1;\n                    real_t delta = p_keys[next].time - p_keys[idx].time;\n                    real_t from = p_time - p_keys[idx].time;\n\n                    if (Math::is_zero_approx(delta)) {\n                        c = 0;\n                    } else {\n                        c = from / delta;\n                    }\n                } else {\n                    next = 0;\n                    real_t delta = (length - p_keys[idx].time) + p_keys[next].time;\n                    real_t from = p_time - p_keys[idx].time;\n\n                    if (Math::is_zero_approx(delta)) {\n                        c = 0;\n                    } else {\n                        c = from / delta;\n                    }\n                }\n            } else {\n                // on loop, behind first key\n                idx = len - 1;\n                next = 0;\n                real_t endtime = (length - p_keys[idx].time);\n                if (endtime &lt; 0) { // may be keys past the end\n                    endtime = 0;\n                }\n                real_t delta = endtime + p_keys[next].time;\n                real_t from = endtime + p_time;\n\n                if (Math::is_zero_approx(delta)) {\n                    c = 0;\n                } else {\n                    c = from / delta;\n                }\n            }\n        } else {\n            // backward\n            if (idx &lt;= len - 1) {\n                if (idx &gt; 0) {\n                    next = idx - 1;\n                    real_t delta = (length - p_keys[next].time) - (length - p_keys[idx].time);\n                    real_t from = (length - p_time) - (length - p_keys[idx].time);\n\n                    if (Math::is_zero_approx(delta)) {\n                        c = 0;\n                    } else {\n                        c = from / delta;\n                    }\n                } else {\n                    next = len - 1;\n                    real_t delta = p_keys[idx].time + (length - p_keys[next].time);\n                    real_t from = (length - p_time) - (length - p_keys[idx].time);\n\n                    if (Math::is_zero_approx(delta)) {\n                        c = 0;\n                    } else {\n                        c = from / delta;\n                    }\n                }\n            } else {\n                // on loop, in front of last key\n                idx = 0;\n                next = len - 1;\n                real_t endtime = p_keys[idx].time;\n                if (endtime &gt; length) { // may be keys past the end\n                    endtime = length;\n                }\n                real_t delta = p_keys[next].time - endtime;\n                real_t from = p_time - endtime;\n\n                if (Math::is_zero_approx(delta)) {\n                    c = 0;\n                } else {\n                    c = from / delta;\n                }\n            }\n        }\n    } else { // no loop\n        if (!p_backward) {\n            if (idx &gt;= 0) {\n                if (idx &lt; len - 1) {\n                    next = idx + 1;\n                    real_t delta = p_keys[next].time - p_keys[idx].time;\n                    real_t from = p_time - p_keys[idx].time;\n\n                    if (Math::is_zero_approx(delta)) {\n                        c = 0;\n                    } else {\n                        c = from / delta;\n                    }\n                } else {\n                    next = idx;\n                }\n            } else {\n                idx = next = 0;\n            }\n        } else {\n            if (idx &lt;= len - 1) {\n                if (idx &gt; 0) {\n                    next = idx - 1;\n                    real_t delta = (length - p_keys[next].time) - (length - p_keys[idx].time);\n                    real_t from = (length - p_time) - (length - p_keys[idx].time);\n\n                    if (Math::is_zero_approx(delta)) {\n                        c = 0;\n                    } else {\n                        c = from / delta;\n                    }\n\n                } else {\n                    next = idx;\n                }\n            } else {\n                idx = next = len - 1;\n            }\n        }\n    }\n\n    if (p_ok) {\n        *p_ok = result;\n    }\n    if (!result) {\n        return T();\n    }\n\n    real_t tr = p_keys[idx].transition;\n\n    if (tr == 0 || idx == next) {\n        // don't interpolate if not needed\n        return p_keys[idx].value;\n    }\n\n    if (tr != 1.0) {\n        c = Math::ease(c, tr);\n    }\n\n    switch (p_interp) {\n        case INTERPOLATION_NEAREST: {\n            return p_keys[idx].value;\n        } break;\n        case INTERPOLATION_LINEAR: {\n            return _interpolate(p_keys[idx].value, p_keys[next].value, c);\n        } break;\n        case INTERPOLATION_LINEAR_ANGLE: {\n            return _interpolate_angle(p_keys[idx].value, p_keys[next].value, c);\n        } break;\n        case INTERPOLATION_CUBIC:\n        case INTERPOLATION_CUBIC_ANGLE: {\n            int pre = 0;\n            int post = 0;\n            if (!p_backward) {\n                pre = idx - 1;\n                if (pre &lt; 0) {\n                    if (loop_mode == LOOP_LINEAR && p_loop_wrap) {\n                        pre = len - 1;\n                    } else {\n                        pre = 0;\n                    }\n                }\n                post = next + 1;\n                if (post &gt;= len) {\n                    if (loop_mode == LOOP_LINEAR && p_loop_wrap) {\n                        post = 0;\n                    } else {\n                        post = next;\n                    }\n                }\n            } else {\n                pre = idx + 1;\n                if (pre &gt;= len) {\n                    if (loop_mode == LOOP_LINEAR && p_loop_wrap) {\n                        pre = 0;\n                    } else {\n                        pre = idx;\n                    }\n                }\n                post = next - 1;\n                if (post &lt; 0) {\n                    if (loop_mode == LOOP_LINEAR && p_loop_wrap) {\n                        post = len - 1;\n                    } else {\n                        post = 0;\n                    }\n                }\n            }\n\n            real_t pre_t = 0.0;\n            real_t to_t = 0.0;\n            real_t post_t = 0.0;\n            if (loop_mode == LOOP_LINEAR && p_loop_wrap) {\n                pre_t = pre &gt; idx ? -length + p_keys[pre].time - p_keys[idx].time : p_keys[pre].time - p_keys[idx].time;\n                to_t = next &lt; idx ? length + p_keys[next].time - p_keys[idx].time : p_keys[next].time - p_keys[idx].time;\n                post_t = next &lt; idx || post &lt;= idx ? length + p_keys[post].time - p_keys[idx].time : p_keys[post].time - p_keys[idx].time;\n            } else {\n                pre_t = p_keys[pre].time - p_keys[idx].time;\n                to_t = p_keys[next].time - p_keys[idx].time;\n                post_t = p_keys[post].time - p_keys[idx].time;\n            }\n\n            if (p_interp == INTERPOLATION_CUBIC_ANGLE) {\n                return _cubic_interpolate_angle_in_time(\n                        p_keys[pre].value, p_keys[idx].value, p_keys[next].value, p_keys[post].value, c,\n                        pre_t, to_t, post_t);\n            }\n            return _cubic_interpolate_in_time(\n                    p_keys[pre].value, p_keys[idx].value, p_keys[next].value, p_keys[post].value, c,\n                    pre_t, to_t, post_t);\n        } break;\n        default:\n            return p_keys[idx].value;\n    }\n\n    // do a barrel roll\n}\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240330-cicd-gitlab.html#tags",
-    "href": "decisions/20240330-cicd-gitlab.html#tags",
-    "title": "Proposed: CI/CD Setup with Docker and Other Platforms",
+    "objectID": "decisions/20221016-v-sekai-view-replication.html#context-and-problem-statement",
+    "href": "decisions/20221016-v-sekai-view-replication.html#context-and-problem-statement",
+    "title": "Rejected: Use view replication algorithm for multiplayer multirelay sync",
     "section": "",
-    "text": "V-Sekai"
+    "text": "See replicate sync 100’000 entities using a solution."
   },
   {
-    "objectID": "decisions/20240330-cicd-gitlab.html#further-reading",
-    "href": "decisions/20240330-cicd-gitlab.html#further-reading",
-    "title": "Proposed: CI/CD Setup with Docker and Other Platforms",
+    "objectID": "decisions/20221016-v-sekai-view-replication.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20221016-v-sekai-view-replication.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Rejected: Use view replication algorithm for multiplayer multirelay sync",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAssisted by Aria, your AI assistant."
+    "text": "V-Sekai could use viewstamp replication in the context of game entity interpolation of past and current state.\nThe key insight is everything is a keyframed animation that is nearest, linear or cubic interpolated."
   },
   {
-    "objectID": "decisions/20230310-IREE-backend-for-machine-learning-computations.html",
-    "href": "decisions/20230310-IREE-backend-for-machine-learning-computations.html",
-    "title": "Superseded: Creating a Godot Engine C++ module with IREE backend for machine learning computations using Vulkan and CUDA",
+    "objectID": "decisions/20221016-v-sekai-view-replication.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20221016-v-sekai-view-replication.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Rejected: Use view replication algorithm for multiplayer multirelay sync",
     "section": "",
-    "text": "Superseded: Creating a Godot Engine C++ module with IREE backend for machine learning computations using Vulkan and CUDA\n\nMetadata\n\nStatus: superseded by 20230502-add-iree-to-godot-engine-for-image-superresolution \nDeciders: V-Sekai,fire,\nTags: V-Sekai, IREE, Godot Engine, Image Superresolution, Vulkan Backend,chatgpt 4,Google,\n\n\n\nContext and Problem Statement\nI want to have a starting place for testing ai algorithms.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nCreate a Godot Engine C++ module with a machine learning computation backend.\nFind a interesting test case.\nWant to run the machine learning technology on the player’s computer, the cpu-only server that hosts the game, and the gpu cloud.\nTo summarize, if you’re looking for a sample that demonstrates loading a model at runtime for CPU, Vulkan, and CUDA in C++, you can check out the IREE samples. In particular, the dynamic_shapes and simple_embedding samples showcase how to run on your choice of target. The input program may have a signature in the stablehlo dialect, and you can use IREE or XLA depending on your preferred tech stack or runtime requirements. The Vulkan stack in IREE is relatively stable and offers good performance, with nod.ai’s SHARK offering extra tuning and APIs on top. However, there may be differences in optimization depending on the workload and potential driver bugs and pitfalls.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nProvide IREE to godot engine.\nUses the Vulkan back end.\n\ninput_count\ninput/0/data (TypedArray)\noutput_count\noutput/0/data (TypedArray)\n\n\n\nPositive Consequences\nHave a playground for testing.\n\n\nNegative Consequences\nNo response\n\n\nOption graveyard\nDon’t use onnx because it doesn’t have vulkan support which limits reach.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot a small number of gdscript lines.\n\n\nIs there a reason why this should be core and done by us?\nI know how, and no one else is doing it.\n\n\nReferences\n\nV-Sekai\nSHARK\nIREE in-tree samples: https://github.com/openxla/iree/tree/main/samples\nIREE extra/more complex samples: https://github.com/iree-org/iree-samples\nIREE dynamic shapes sample: https://github.com/openxla/iree/tree/main/samples/dynamic_shapes\nIREE CPU/Vulkan/CUDA sample: https://github.com/openxla/iree/tree/main/samples/simple_embedding\nXLA axpy example: https://github.com/openxla/xla/tree/main/xla/examples/axpy\nnod.ai SHARK: https://github.com/nod-ai/SHARK\nnod.ai SHARK results on AMD GPUs using Vulkan: https://nod.ai/sd-rdna3-ces2023/"
+    "text": "We assume we’re using Godot Engine 4 with float is doubles.\n\nReplicate pending property changes safely to a quorum of distributed replicas, then\ninterpolate property changes to the in-memory state.\n\nIgnore p_time too far in the future or the past as the viewstamp limit.\nT Animation::_interpolate(const Vector&lt;TKey&lt;T&gt;&gt; &p_keys, double p_time, InterpolationType p_interp, bool p_loop_wrap, bool *p_ok, bool p_backward) const\n\nACK to the client.\n\nSee also Linux io_uring (replacement for epoll).\nEverything is an interpolation event or a property state. Want to fit datastructures into 128 bytes (2 CPU cache lines).\nWe reuse the create_property data structure as the state.\n\n\nReferencing https://github.com/tigerbeetledb/tigerbeetle/blob/main/docs/DESIGN.md#data-structures.\nSee Variant bytes_to_var_with_objects (PackedByteArray bytes) and PackedByteArray var_to_bytes_with_objects (Variant variable).\n\n\ncreate_property_interpolate {\n           id: 16 bytes (128-bit)\n   past_entity_id: 16 bytes (128-bit)\ncurrent_entity_id: 16 bytes (128-bit) [to allow interpolation between different entities]\n    user_data: 16 bytes (128-bit) [optional, e.g. opaque third-party identifier to link\n        this transfer (many-to-one) to an external entity]\n     reserved: 16 bytes (128-bit) [reserved, for accounting policy primitives]\n       pending_id: 16 bytes (128-bit) [optional, required to post or void an existing but pending transfer]\n      timeout:  8 bytes (64-bit) [optional, required only for a pending transfer, a quantity of time,\n        i.e. an offset in nanoseconds from timestamp]\n        shard:  4 bytes (32-bit) [required, to enforce isolation by ensuring that all transfers\n        are between entities of the same shard]\n         code:  2 bytes (16-bit) [required, an opaque entity code describing the type\n        of the interpolation, e.g. player, map, prop]\n        flags:  2 bytes (16-bit) [optional, to modify the usage of the reserved field and for future feature expansion.]\n        value:  n bytes (n-bit) [required, variant of the past property and current property,\n        which must be the same for both properties. Uses var_to_bytes_with_objects.]\n    timestamp:  8 bytes (64-bit) [reserved, assigned by the leader before journaling]\n} = n bytes (n CPU cache lines)\n\n\n\n   create_property {\n          id: 16 bytes (128-bit)\n       user_data: 16 bytes (128-bit) [optional, opaque third-party identifier to link this account\n        (many-to-one) to an external entity]\n    reserved: 48 bytes (384-bit) [reserved for future accounting policy primitives]\n       shard:  4 bytes (32-bit) [required, to enforce isolation by ensuring that all transfers\n        are between accounts of the same ledger]\n        code:  2 bytes (16-bit) [required, an opaque entity code describing the type\n        of the interpolation, e.g. player, map, prop]\n       flags:  2 bytes (16-bit) [optional, net balance limits:\n        e.g. debits_must_not_exceed_credits or credits_must_not_exceed_debits]\n     past_interpolations_pending: n bytes (n-bit variant. Uses var_to_bytes_with_objects.)\n      past_interpolations_posted: n bytes (n-bit variant. Uses var_to_bytes_with_objects.)\n  current_interpolations_pending: n bytes (n-bit variant. Uses var_to_bytes_with_objects.)\n   current_interpolations_posted: n bytes (n-bit variant. Uses var_to_bytes_with_objects.)\n               timestamp: 8 bytes ( 64-bit) [reserved]\n} = n bytes (n CPU cache lines)"
   },
   {
-    "objectID": "decisions/20230922-spacetime-shadow-shards-sync.html",
-    "href": "decisions/20230922-spacetime-shadow-shards-sync.html",
-    "title": "Proposed: Streamlining V-Sekai Performance",
+    "objectID": "decisions/20221016-v-sekai-view-replication.html#positive-consequences",
+    "href": "decisions/20221016-v-sekai-view-replication.html#positive-consequences",
+    "title": "Rejected: Use view replication algorithm for multiplayer multirelay sync",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, Godot, Networking\n\n\n\n\nV-Sekai, leveraging the Godot client-server model, aspires to support 1000-2000 clients. The objective is to deliver uninterrupted gameplay and a comprehensive gaming experience.\n\n\n\nKey challenges encompass managing single-shard overload, administering shadow shards, and implementing state synchronization and game state transitions. These tasks necessitate precise planning, execution, and monitoring for peak performance.\n\n\n\nA simple gameplay session will be initiated where an art seller can upload artwork. The game environment will be a flat surface with a boundary, allowing mathematical movement calculations without a navigation mesh.\nThe number of clients connecting to the server will gradually increase, starting small and eventually reaching 2,000. This will test the server’s capacity to handle multiple connections. During testing, system resources will be monitored to estimate the cost and resources required to support 2000 players. Gameplay sessions will be recorded for the trade show, and load testing will be conducted to ensure our server can manage the maximum number of players without crashing or significant slowdowns.\n\nServer Configuration: Set up a Godot server that listens on a designated port.\nClient Development: Build a Godot client that connects to our server using High-Level Networking.\nShadow Shard Administration: Generate shadow copies of the original shard, serialize them for network transmission, and synchronize their state periodically.\nState Synchronization: Develop Ref&lt;Animation&gt; data structures symbolizing different parts of the model and outline their interactions.\nGame State Transitions: Preserve, the current game state, pinpoint the target state, transition to it, and validate the transition using an orphan AnimationTree.\n\n\n\n\nThis strategy allows us to accommodate numerous clients simultaneously without sacrificing performance or user experience. It also provides a systematic method to monitor and enhance gaming sessions.\n\n\n\nThis approach requires substantial resources and expertise in server configuration, networking, and game development. Unexpected challenges may surface during implementation and testing.\n\n\n\nA potential alternative could have been adopting a different game engine or networking model. However, this would demand a complete revamp of our existing setup, possibly compromising performance and flexibility.\n\n\n\nControversial plans are essential to minimize gameplay disruption in unexpected traffic surges or server outages.\n\n\n\nAll tasks outlined are integral to our operations and will be undertaken by us.\n\n\n\n\n[V-Sekai]\nAI assists this article."
+    "text": "The code is based on robust view replication consensus algorithm theory.\nThe playback of the state machine is deterministic."
   },
   {
-    "objectID": "decisions/20230922-spacetime-shadow-shards-sync.html#metadata",
-    "href": "decisions/20230922-spacetime-shadow-shards-sync.html#metadata",
-    "title": "Proposed: Streamlining V-Sekai Performance",
+    "objectID": "decisions/20221016-v-sekai-view-replication.html#negative-consequences",
+    "href": "decisions/20221016-v-sekai-view-replication.html#negative-consequences",
+    "title": "Rejected: Use view replication algorithm for multiplayer multirelay sync",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, Godot, Networking"
+    "text": "Minimum of three relays."
   },
   {
-    "objectID": "decisions/20230922-spacetime-shadow-shards-sync.html#background",
-    "href": "decisions/20230922-spacetime-shadow-shards-sync.html#background",
-    "title": "Proposed: Streamlining V-Sekai Performance",
+    "objectID": "decisions/20221016-v-sekai-view-replication.html#option-graveyard",
+    "href": "decisions/20221016-v-sekai-view-replication.html#option-graveyard",
+    "title": "Rejected: Use view replication algorithm for multiplayer multirelay sync",
     "section": "",
-    "text": "V-Sekai, leveraging the Godot client-server model, aspires to support 1000-2000 clients. The objective is to deliver uninterrupted gameplay and a comprehensive gaming experience."
+    "text": "Option: Current V-Sekai replication\nRejection Reason: Can’t link servers"
   },
   {
-    "objectID": "decisions/20230922-spacetime-shadow-shards-sync.html#challenges",
-    "href": "decisions/20230922-spacetime-shadow-shards-sync.html#challenges",
-    "title": "Proposed: Streamlining V-Sekai Performance",
+    "objectID": "decisions/20221016-v-sekai-view-replication.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20221016-v-sekai-view-replication.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Rejected: Use view replication algorithm for multiplayer multirelay sync",
     "section": "",
-    "text": "Key challenges encompass managing single-shard overload, administering shadow shards, and implementing state synchronization and game state transitions. These tasks necessitate precise planning, execution, and monitoring for peak performance."
+    "text": "Entity replication is not trivial."
   },
   {
-    "objectID": "decisions/20230922-spacetime-shadow-shards-sync.html#approach",
-    "href": "decisions/20230922-spacetime-shadow-shards-sync.html#approach",
-    "title": "Proposed: Streamlining V-Sekai Performance",
+    "objectID": "decisions/20221016-v-sekai-view-replication.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20221016-v-sekai-view-replication.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Rejected: Use view replication algorithm for multiplayer multirelay sync",
     "section": "",
-    "text": "A simple gameplay session will be initiated where an art seller can upload artwork. The game environment will be a flat surface with a boundary, allowing mathematical movement calculations without a navigation mesh.\nThe number of clients connecting to the server will gradually increase, starting small and eventually reaching 2,000. This will test the server’s capacity to handle multiple connections. During testing, system resources will be monitored to estimate the cost and resources required to support 2000 players. Gameplay sessions will be recorded for the trade show, and load testing will be conducted to ensure our server can manage the maximum number of players without crashing or significant slowdowns.\n\nServer Configuration: Set up a Godot server that listens on a designated port.\nClient Development: Build a Godot client that connects to our server using High-Level Networking.\nShadow Shard Administration: Generate shadow copies of the original shard, serialize them for network transmission, and synchronize their state periodically.\nState Synchronization: Develop Ref&lt;Animation&gt; data structures symbolizing different parts of the model and outline their interactions.\nGame State Transitions: Preserve, the current game state, pinpoint the target state, transition to it, and validate the transition using an orphan AnimationTree."
+    "text": "We’re doing the networking layer."
   },
   {
-    "objectID": "decisions/20230922-spacetime-shadow-shards-sync.html#advantages",
-    "href": "decisions/20230922-spacetime-shadow-shards-sync.html#advantages",
-    "title": "Proposed: Streamlining V-Sekai Performance",
+    "objectID": "decisions/20221016-v-sekai-view-replication.html#references",
+    "href": "decisions/20221016-v-sekai-view-replication.html#references",
+    "title": "Rejected: Use view replication algorithm for multiplayer multirelay sync",
     "section": "",
-    "text": "This strategy allows us to accommodate numerous clients simultaneously without sacrificing performance or user experience. It also provides a systematic method to monitor and enhance gaming sessions."
+    "text": "Add a multiplayer interface and visual nodes for SceneTree replication\nLMAX Exchange Architecture\n\nLMAX (quote):\n\n\njournal incoming events safely to disk, and\nreplicate to backup nodes, then\napply these events to the in-memory state, then\nACK to the client\n\n\n\nTigerbeetle design\n\nTigerbeetle uses viewstamp replication in the context of bank ledger credit and debit.\nTigerbeetle (quote):\n\n\nreplicate incoming events safely to a quorum of distributed replicas, then\napply these events to the in-memory state, then\nACK to the client\n\n\n\nviewstamped-replication-made-famous\nvr-revisited.pdf\nTigerBeetle Discord server\nCubic interpolation"
   },
   {
-    "objectID": "decisions/20230922-spacetime-shadow-shards-sync.html#limitations",
-    "href": "decisions/20230922-spacetime-shadow-shards-sync.html#limitations",
-    "title": "Proposed: Streamlining V-Sekai Performance",
+    "objectID": "decisions/20221016-v-sekai-view-replication.html#interpolation-function-from-godot-engine-4",
+    "href": "decisions/20221016-v-sekai-view-replication.html#interpolation-function-from-godot-engine-4",
+    "title": "Rejected: Use view replication algorithm for multiplayer multirelay sync",
     "section": "",
-    "text": "This approach requires substantial resources and expertise in server configuration, networking, and game development. Unexpected challenges may surface during implementation and testing."
+    "text": "Note that this handles both nearest interpolation and cubic (with time) interpolation.\ntemplate &lt;class T&gt;\nT Animation::_interpolate(const Vector&lt;TKey&lt;T&gt;&gt; &p_keys, double p_time, InterpolationType p_interp, bool p_loop_wrap, bool *p_ok, bool p_backward) const {\n    int len = _find(p_keys, length) + 1; // try to find last key (there may be more past the end)\n\n    if (len &lt;= 0) {\n        // (-1 or -2 returned originally) (plus one above)\n        // meaning no keys, or only key time is larger than length\n        if (p_ok) {\n            *p_ok = false;\n        }\n        return T();\n    } else if (len == 1) { // one key found (0+1), return it\n\n        if (p_ok) {\n            *p_ok = true;\n        }\n        return p_keys[0].value;\n    }\n\n    int idx = _find(p_keys, p_time, p_backward);\n\n    ERR_FAIL_COND_V(idx == -2, T());\n\n    bool result = true;\n    int next = 0;\n    real_t c = 0.0;\n    // prepare for all cases of interpolation\n\n    if (loop_mode == LOOP_LINEAR && p_loop_wrap) {\n        // loop\n        if (!p_backward) {\n            // no backward\n            if (idx &gt;= 0) {\n                if (idx &lt; len - 1) {\n                    next = idx + 1;\n                    real_t delta = p_keys[next].time - p_keys[idx].time;\n                    real_t from = p_time - p_keys[idx].time;\n\n                    if (Math::is_zero_approx(delta)) {\n                        c = 0;\n                    } else {\n                        c = from / delta;\n                    }\n                } else {\n                    next = 0;\n                    real_t delta = (length - p_keys[idx].time) + p_keys[next].time;\n                    real_t from = p_time - p_keys[idx].time;\n\n                    if (Math::is_zero_approx(delta)) {\n                        c = 0;\n                    } else {\n                        c = from / delta;\n                    }\n                }\n            } else {\n                // on loop, behind first key\n                idx = len - 1;\n                next = 0;\n                real_t endtime = (length - p_keys[idx].time);\n                if (endtime &lt; 0) { // may be keys past the end\n                    endtime = 0;\n                }\n                real_t delta = endtime + p_keys[next].time;\n                real_t from = endtime + p_time;\n\n                if (Math::is_zero_approx(delta)) {\n                    c = 0;\n                } else {\n                    c = from / delta;\n                }\n            }\n        } else {\n            // backward\n            if (idx &lt;= len - 1) {\n                if (idx &gt; 0) {\n                    next = idx - 1;\n                    real_t delta = (length - p_keys[next].time) - (length - p_keys[idx].time);\n                    real_t from = (length - p_time) - (length - p_keys[idx].time);\n\n                    if (Math::is_zero_approx(delta)) {\n                        c = 0;\n                    } else {\n                        c = from / delta;\n                    }\n                } else {\n                    next = len - 1;\n                    real_t delta = p_keys[idx].time + (length - p_keys[next].time);\n                    real_t from = (length - p_time) - (length - p_keys[idx].time);\n\n                    if (Math::is_zero_approx(delta)) {\n                        c = 0;\n                    } else {\n                        c = from / delta;\n                    }\n                }\n            } else {\n                // on loop, in front of last key\n                idx = 0;\n                next = len - 1;\n                real_t endtime = p_keys[idx].time;\n                if (endtime &gt; length) { // may be keys past the end\n                    endtime = length;\n                }\n                real_t delta = p_keys[next].time - endtime;\n                real_t from = p_time - endtime;\n\n                if (Math::is_zero_approx(delta)) {\n                    c = 0;\n                } else {\n                    c = from / delta;\n                }\n            }\n        }\n    } else { // no loop\n        if (!p_backward) {\n            if (idx &gt;= 0) {\n                if (idx &lt; len - 1) {\n                    next = idx + 1;\n                    real_t delta = p_keys[next].time - p_keys[idx].time;\n                    real_t from = p_time - p_keys[idx].time;\n\n                    if (Math::is_zero_approx(delta)) {\n                        c = 0;\n                    } else {\n                        c = from / delta;\n                    }\n                } else {\n                    next = idx;\n                }\n            } else {\n                idx = next = 0;\n            }\n        } else {\n            if (idx &lt;= len - 1) {\n                if (idx &gt; 0) {\n                    next = idx - 1;\n                    real_t delta = (length - p_keys[next].time) - (length - p_keys[idx].time);\n                    real_t from = (length - p_time) - (length - p_keys[idx].time);\n\n                    if (Math::is_zero_approx(delta)) {\n                        c = 0;\n                    } else {\n                        c = from / delta;\n                    }\n\n                } else {\n                    next = idx;\n                }\n            } else {\n                idx = next = len - 1;\n            }\n        }\n    }\n\n    if (p_ok) {\n        *p_ok = result;\n    }\n    if (!result) {\n        return T();\n    }\n\n    real_t tr = p_keys[idx].transition;\n\n    if (tr == 0 || idx == next) {\n        // don't interpolate if not needed\n        return p_keys[idx].value;\n    }\n\n    if (tr != 1.0) {\n        c = Math::ease(c, tr);\n    }\n\n    switch (p_interp) {\n        case INTERPOLATION_NEAREST: {\n            return p_keys[idx].value;\n        } break;\n        case INTERPOLATION_LINEAR: {\n            return _interpolate(p_keys[idx].value, p_keys[next].value, c);\n        } break;\n        case INTERPOLATION_LINEAR_ANGLE: {\n            return _interpolate_angle(p_keys[idx].value, p_keys[next].value, c);\n        } break;\n        case INTERPOLATION_CUBIC:\n        case INTERPOLATION_CUBIC_ANGLE: {\n            int pre = 0;\n            int post = 0;\n            if (!p_backward) {\n                pre = idx - 1;\n                if (pre &lt; 0) {\n                    if (loop_mode == LOOP_LINEAR && p_loop_wrap) {\n                        pre = len - 1;\n                    } else {\n                        pre = 0;\n                    }\n                }\n                post = next + 1;\n                if (post &gt;= len) {\n                    if (loop_mode == LOOP_LINEAR && p_loop_wrap) {\n                        post = 0;\n                    } else {\n                        post = next;\n                    }\n                }\n            } else {\n                pre = idx + 1;\n                if (pre &gt;= len) {\n                    if (loop_mode == LOOP_LINEAR && p_loop_wrap) {\n                        pre = 0;\n                    } else {\n                        pre = idx;\n                    }\n                }\n                post = next - 1;\n                if (post &lt; 0) {\n                    if (loop_mode == LOOP_LINEAR && p_loop_wrap) {\n                        post = len - 1;\n                    } else {\n                        post = 0;\n                    }\n                }\n            }\n\n            real_t pre_t = 0.0;\n            real_t to_t = 0.0;\n            real_t post_t = 0.0;\n            if (loop_mode == LOOP_LINEAR && p_loop_wrap) {\n                pre_t = pre &gt; idx ? -length + p_keys[pre].time - p_keys[idx].time : p_keys[pre].time - p_keys[idx].time;\n                to_t = next &lt; idx ? length + p_keys[next].time - p_keys[idx].time : p_keys[next].time - p_keys[idx].time;\n                post_t = next &lt; idx || post &lt;= idx ? length + p_keys[post].time - p_keys[idx].time : p_keys[post].time - p_keys[idx].time;\n            } else {\n                pre_t = p_keys[pre].time - p_keys[idx].time;\n                to_t = p_keys[next].time - p_keys[idx].time;\n                post_t = p_keys[post].time - p_keys[idx].time;\n            }\n\n            if (p_interp == INTERPOLATION_CUBIC_ANGLE) {\n                return _cubic_interpolate_angle_in_time(\n                        p_keys[pre].value, p_keys[idx].value, p_keys[next].value, p_keys[post].value, c,\n                        pre_t, to_t, post_t);\n            }\n            return _cubic_interpolate_in_time(\n                    p_keys[pre].value, p_keys[idx].value, p_keys[next].value, p_keys[post].value, c,\n                    pre_t, to_t, post_t);\n        } break;\n        default:\n            return p_keys[idx].value;\n    }\n\n    // do a barrel roll\n}"
   },
   {
-    "objectID": "decisions/20230922-spacetime-shadow-shards-sync.html#alternatives",
-    "href": "decisions/20230922-spacetime-shadow-shards-sync.html#alternatives",
-    "title": "Proposed: Streamlining V-Sekai Performance",
+    "objectID": "decisions/20221016-v-sekai-view-replication.html#derivative-license",
+    "href": "decisions/20221016-v-sekai-view-replication.html#derivative-license",
+    "title": "Rejected: Use view replication algorithm for multiplayer multirelay sync",
     "section": "",
-    "text": "A potential alternative could have been adopting a different game engine or networking model. However, this would demand a complete revamp of our existing setup, possibly compromising performance and flexibility."
+    "text": "Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230922-spacetime-shadow-shards-sync.html#exceptional-scenarios",
-    "href": "decisions/20230922-spacetime-shadow-shards-sync.html#exceptional-scenarios",
-    "title": "Proposed: Streamlining V-Sekai Performance",
+    "objectID": "decisions/20211229-run-meetings-using-lean-coffee.html",
+    "href": "decisions/20211229-run-meetings-using-lean-coffee.html",
+    "title": "Accepted: Run meetings using Lean Coffee",
     "section": "",
-    "text": "Controversial plans are essential to minimize gameplay disruption in unexpected traffic surges or server outages."
+    "text": "Status: accepted \nDeciders: V-Sekai,Mr. Metaverse,fire,\nTags: V-Sekai,\n\n\n\nMeetings need to be ran better than randomly.\n\n\n\nLean coffee can improve on meetings.\n\n\n\nThree column kanban board. To discuss, discussing, and discussed.\nHave everyone add cards for topics they want to discuss. It may take 2-3 min for people to get into the Trello board. Once in take 2-3 min to add topics to the left column.\nThen have everyone vote, each person gets 2-3 votes. To vote, they should click the card of a topic to discuss and in the comments type “+”. Be sure nobody else adds any other comments until we begin discussing the cards.\nLast, sort the cards by number of comments (most amount of + go to top) and then one by one drag in the top card to “discussing”. Set a timer for 5 minutes. After 5 minutes the group votes to keep discussing or to move on. While discussing the group can add comments or links to the card while discussing.\n\n\n\n\nOrganized meetings are better\n\n\n\n\n\nCan be strange to use because it’s not common.\n\n\n\n\n\nOption: Gather for one hour randomly.\nRejection Reason: We can do better.\n\n\n\n\nNot code.\n\n\n\nWe need to run better meetings.\n\n\n\n\nhttps://leanchange.org/resources/leancoffee\n\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230922-spacetime-shadow-shards-sync.html#responsibility",
-    "href": "decisions/20230922-spacetime-shadow-shards-sync.html#responsibility",
-    "title": "Proposed: Streamlining V-Sekai Performance",
+    "objectID": "decisions/20211229-run-meetings-using-lean-coffee.html#context-and-problem-statement",
+    "href": "decisions/20211229-run-meetings-using-lean-coffee.html#context-and-problem-statement",
+    "title": "Accepted: Run meetings using Lean Coffee",
     "section": "",
-    "text": "All tasks outlined are integral to our operations and will be undertaken by us."
+    "text": "Meetings need to be ran better than randomly."
   },
   {
-    "objectID": "decisions/20230922-spacetime-shadow-shards-sync.html#additional-resources",
-    "href": "decisions/20230922-spacetime-shadow-shards-sync.html#additional-resources",
-    "title": "Proposed: Streamlining V-Sekai Performance",
+    "objectID": "decisions/20211229-run-meetings-using-lean-coffee.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20211229-run-meetings-using-lean-coffee.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Accepted: Run meetings using Lean Coffee",
     "section": "",
-    "text": "[V-Sekai]\nAI assists this article."
+    "text": "Lean coffee can improve on meetings."
   },
   {
-    "objectID": "decisions/20230831-fixing-upload-limits.html",
-    "href": "decisions/20230831-fixing-upload-limits.html",
-    "title": "Accepted: Enhancing Map Uploads",
+    "objectID": "decisions/20211229-run-meetings-using-lean-coffee.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20211229-run-meetings-using-lean-coffee.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Accepted: Run meetings using Lean Coffee",
     "section": "",
-    "text": "Status: accepted\nDeciders: V-Sekai, fire, Scipi\nTags: V-Sekai\n\n\n\n\nV-Sekai is facing limitations in its Elixir uro backend when uploading maps, specifically related to the Godot Engine scenes. These limitations are believed to be caused by a restriction in the Waffles library.\n\n\n\nThe challenge at hand is to address the arbitrary limitations imposed by the Waffles library on the Godot Engine scenes during map uploads in the Elixir uro backend of V-Sekai.\n\n\n\nTo overcome this challenge, we propose patching the Waffles library in collaboration with our new contributor.\n\n\n\nBy patching the Waffles library, we can effectively remove the limitations on the Godot Engine scenes and improve the functionality of map uploads in V-Sekai.\n\n\n\nIt is important to consider any potential downsides or risks associated with patching the Waffles library. Further analysis and testing may be required to ensure compatibility and stability.\n\n\n\nAlternative solutions to address the limitations have been explored, but patching the Waffles library appears to be the most viable option.\n\n\n\nThis limitation impacts the specific use case of map uploads in the Elixir uro backend, and may not affect other functionalities in V-Sekai.\n\n\n\nAs a core functionality of V-Sekai, addressing the limitations in the Godot Engine scenes during map uploads is a task that should be done by our team.\n\n\n\n\nV-Sekai\nThis article is assisted by AI.\nhttps://github.com/V-Sekai/v-sekai-game/issues/68"
+    "text": "Three column kanban board. To discuss, discussing, and discussed.\nHave everyone add cards for topics they want to discuss. It may take 2-3 min for people to get into the Trello board. Once in take 2-3 min to add topics to the left column.\nThen have everyone vote, each person gets 2-3 votes. To vote, they should click the card of a topic to discuss and in the comments type “+”. Be sure nobody else adds any other comments until we begin discussing the cards.\nLast, sort the cards by number of comments (most amount of + go to top) and then one by one drag in the top card to “discussing”. Set a timer for 5 minutes. After 5 minutes the group votes to keep discussing or to move on. While discussing the group can add comments or links to the card while discussing."
   },
   {
-    "objectID": "decisions/20230831-fixing-upload-limits.html#metadata",
-    "href": "decisions/20230831-fixing-upload-limits.html#metadata",
-    "title": "Accepted: Enhancing Map Uploads",
+    "objectID": "decisions/20211229-run-meetings-using-lean-coffee.html#positive-consequences",
+    "href": "decisions/20211229-run-meetings-using-lean-coffee.html#positive-consequences",
+    "title": "Accepted: Run meetings using Lean Coffee",
     "section": "",
-    "text": "Status: accepted\nDeciders: V-Sekai, fire, Scipi\nTags: V-Sekai"
+    "text": "Organized meetings are better"
   },
   {
-    "objectID": "decisions/20230831-fixing-upload-limits.html#the-backdrop",
-    "href": "decisions/20230831-fixing-upload-limits.html#the-backdrop",
-    "title": "Accepted: Enhancing Map Uploads",
+    "objectID": "decisions/20211229-run-meetings-using-lean-coffee.html#negative-consequences",
+    "href": "decisions/20211229-run-meetings-using-lean-coffee.html#negative-consequences",
+    "title": "Accepted: Run meetings using Lean Coffee",
     "section": "",
-    "text": "V-Sekai is facing limitations in its Elixir uro backend when uploading maps, specifically related to the Godot Engine scenes. These limitations are believed to be caused by a restriction in the Waffles library."
+    "text": "Can be strange to use because it’s not common."
   },
   {
-    "objectID": "decisions/20230831-fixing-upload-limits.html#the-challenge",
-    "href": "decisions/20230831-fixing-upload-limits.html#the-challenge",
-    "title": "Accepted: Enhancing Map Uploads",
+    "objectID": "decisions/20211229-run-meetings-using-lean-coffee.html#option-graveyard",
+    "href": "decisions/20211229-run-meetings-using-lean-coffee.html#option-graveyard",
+    "title": "Accepted: Run meetings using Lean Coffee",
     "section": "",
-    "text": "The challenge at hand is to address the arbitrary limitations imposed by the Waffles library on the Godot Engine scenes during map uploads in the Elixir uro backend of V-Sekai."
+    "text": "Option: Gather for one hour randomly.\nRejection Reason: We can do better."
   },
   {
-    "objectID": "decisions/20230831-fixing-upload-limits.html#the-strategy",
-    "href": "decisions/20230831-fixing-upload-limits.html#the-strategy",
-    "title": "Accepted: Enhancing Map Uploads",
+    "objectID": "decisions/20211229-run-meetings-using-lean-coffee.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20211229-run-meetings-using-lean-coffee.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Accepted: Run meetings using Lean Coffee",
     "section": "",
-    "text": "To overcome this challenge, we propose patching the Waffles library in collaboration with our new contributor."
+    "text": "Not code."
   },
   {
-    "objectID": "decisions/20230831-fixing-upload-limits.html#the-upside",
-    "href": "decisions/20230831-fixing-upload-limits.html#the-upside",
-    "title": "Accepted: Enhancing Map Uploads",
+    "objectID": "decisions/20211229-run-meetings-using-lean-coffee.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20211229-run-meetings-using-lean-coffee.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Accepted: Run meetings using Lean Coffee",
     "section": "",
-    "text": "By patching the Waffles library, we can effectively remove the limitations on the Godot Engine scenes and improve the functionality of map uploads in V-Sekai."
+    "text": "We need to run better meetings."
   },
   {
-    "objectID": "decisions/20230831-fixing-upload-limits.html#the-downside",
-    "href": "decisions/20230831-fixing-upload-limits.html#the-downside",
-    "title": "Accepted: Enhancing Map Uploads",
+    "objectID": "decisions/20211229-run-meetings-using-lean-coffee.html#references",
+    "href": "decisions/20211229-run-meetings-using-lean-coffee.html#references",
+    "title": "Accepted: Run meetings using Lean Coffee",
     "section": "",
-    "text": "It is important to consider any potential downsides or risks associated with patching the Waffles library. Further analysis and testing may be required to ensure compatibility and stability."
+    "text": "https://leanchange.org/resources/leancoffee"
   },
   {
-    "objectID": "decisions/20230831-fixing-upload-limits.html#the-road-not-taken",
-    "href": "decisions/20230831-fixing-upload-limits.html#the-road-not-taken",
-    "title": "Accepted: Enhancing Map Uploads",
+    "objectID": "decisions/20211229-run-meetings-using-lean-coffee.html#derivative-license",
+    "href": "decisions/20211229-run-meetings-using-lean-coffee.html#derivative-license",
+    "title": "Accepted: Run meetings using Lean Coffee",
     "section": "",
-    "text": "Alternative solutions to address the limitations have been explored, but patching the Waffles library appears to be the most viable option."
+    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230831-fixing-upload-limits.html#the-infrequent-use-case",
-    "href": "decisions/20230831-fixing-upload-limits.html#the-infrequent-use-case",
-    "title": "Accepted: Enhancing Map Uploads",
+    "objectID": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html",
+    "href": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html",
+    "title": "Accepted: Use the Humanoid Profile for Character Motion Mirroring",
     "section": "",
-    "text": "This limitation impacts the specific use case of map uploads in the Elixir uro backend, and may not affect other functionalities in V-Sekai."
+    "text": "Daniel Snd was looking for a simple way to mirror right-sided walking keyframes on a character avatar motion.\n\n\n\nDaniel Snd did not utilize the Godot Engine humanoid profile.\n\n\n\nThe solution is to use the Godot Engine humanoid profile.\n\n\nIn Godot Engine, the animation humanoid profile is essential for managing bone rolls in incoming humanoid skeletons. This is because these skeletons often have arbitrary bone rolls that need to be standardized for consistent animation behavior.\n\n\nBone roll refers to the rotation around the bone’s longitudinal axis. In 3D modeling and animation, it’s important to correctly set up bone rolls as they determine the axes of rotation for the bones during animation.\n\n\n\nThe SkeletonProfileHumanoid in Godot 4.0 adopts a practical rule for managing bone rolls:\n\nThe +Y axis should point from the parent joint to the child joint. This is considered as the roll axis.\nThe +X rotation should bend the joints towards the body’s inside (almost the direction of muscle contraction).\n\n\n\n\nIf you mirror animations, the bone rolls and names may need to be corrected. This is because the orientation of the bones can get flipped during the mirroring process. The Godot Humanoid Profile applies a Bone Rule to the bone rolls.\n\n\n\nThe Godot Humanoid Profile standardizes the bone names consistently, it allows one to reuse animations across different characters. For example, if one has a walking animation for one character and one wants to apply it to another character, having the same bone names will allow one to do this without any additional work.\n\n\n\nIn 3D animation, the T-Pose is a standard pose where the character stands upright with their arms extended straight out to the sides. This pose is often used as the default pose for rigging and animating characters because it provides a clear view of all parts of the character. However, not all models are initially in a T-Pose. If you have a model in any other pose (let’s say it’s an A-Pose), you might need to convert it to a T-Pose before you can use it effectively in Godot.\n\n\n\n\nThe engine can ensure that all humanoid animations behave consistently, regardless of the original orientation or roll of the bones in the imported skeleton by following the Bone Rule. This makes it easier to create and manage humanoid animations, especially when working with different humanoids that may have been rigged differently.\n\n\n\n\nUsing the Godot Humanoid Profile will allow for consistent behavior across all humanoid animations, making it easier to create and manage these animations. It also allows for reusability of animations across different characters, saving time and effort in animation creation.\n\n\n\nThere may be a learning curve associated with understanding and implementing the Godot Humanoid Profile. Additionally, this solution assumes that all incoming humanoid skeletons will be compatible with the Godot Humanoid Profile, which may not always be the case.\n\n\n\nAn alternative could have been to manually adjust the bone rolls and names for each individual animation. However, this would be a time-consuming process and would not guarantee consistent results across different animations.\n\n\n\nThis proposal may not be beneficial for non-humanoid animations or for projects that do not require motion mirroring.\n\n\n\nThis proposal involves using an existing feature of the Godot Engine the V-Sekai team implemented in Godot Engine 4.0, so no additional development work would be required from our team.\n\n\n\nStatus: Accepted\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nGodot Engine\nHumanoid Profile\nAnimation Mirroring\nBone Rolls\nCharacter Avatar Motion\n3D Modeling\nT-Pose Conversion\nAnimation Reusability\nV-Sekai\nVR Animation\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nFire\n\nAI assistant Aria assisted with this article.\n\n\n\n## SPDX-License-Identifier: CC0-1.0\n##\n## Author: Daniel Snd\n\n@export var left_name:String = \"Left\"\n@export var right_name:String = \"Right\"\n\nfunc do_mirror():\n    var parenteless_ids :PackedInt32Array = get_parentless_bones()\n    for p in get_parentless_bones():\n        attempt_mirror_recursive(p)\n\nfunc attempt_mirror_recursive(bone_id:int):\n    for i in get_bone_children(bone_id):\n        var bone_name = get_bone_name(i)\n        if bone_name.contains(right_name):\n            mirror_pose(bone_name)\n        elif bone_name.contains(left_name):\n            pass\n        else:\n            mirror_single_bone(i)\n        attempt_mirror_recursive(i)\n\nfunc mirror_single_bone(bone_idx):\n    var mirrored_rot = get_bone_pose(bone_idx).basis.get_rotation_quaternion()\n    mirrored_rot.x *= -1\n    mirrored_rot.w *= -1\n    set_bone_pose_rotation(bone_idx, mirrored_rot)\n\n# Function to mirror pose\nfunc mirror_pose(bone_name):\n    var bone_idx = find_bone(bone_name)\n    if bone_idx == -1:\n        print(\"Bone does not exist in Skeleton\")\n        return\n\n    var mirrored_bone_idx = find_bone(bone_name.replace(right_name, left_name) if bone_name.contains(right_name) else bone_name.replace(left_name, right_name))\n    if mirrored_bone_idx == -1:\n        print(\"Mirrored bone does not exist in Skeleton\")\n        return\n\n    var tr :Transform3D = get_bone_pose(bone_idx)\n    var opposite_tr :Transform3D = get_bone_pose(mirrored_bone_idx)\n    var mirrored_rot = tr.basis.get_rotation_quaternion()\n    mirrored_rot.x *= -1\n    mirrored_rot.w *= -1\n\n    var opposite_mirrored_rot = opposite_tr.basis.get_rotation_quaternion()\n    opposite_mirrored_rot.x *= -1\n    opposite_mirrored_rot.w *= -1\n\n    set_bone_pose_rotation(mirrored_bone_idx, mirrored_rot)\n    set_bone_pose_rotation(bone_idx, opposite_mirrored_rot)"
   },
   {
-    "objectID": "decisions/20230831-fixing-upload-limits.html#in-core-and-done-by-us",
-    "href": "decisions/20230831-fixing-upload-limits.html#in-core-and-done-by-us",
-    "title": "Accepted: Enhancing Map Uploads",
+    "objectID": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#context",
+    "href": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#context",
+    "title": "Accepted: Use the Humanoid Profile for Character Motion Mirroring",
     "section": "",
-    "text": "As a core functionality of V-Sekai, addressing the limitations in the Godot Engine scenes during map uploads is a task that should be done by our team."
+    "text": "Daniel Snd was looking for a simple way to mirror right-sided walking keyframes on a character avatar motion."
   },
   {
-    "objectID": "decisions/20230831-fixing-upload-limits.html#further-reading",
-    "href": "decisions/20230831-fixing-upload-limits.html#further-reading",
-    "title": "Accepted: Enhancing Map Uploads",
+    "objectID": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#problem-statement",
+    "href": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#problem-statement",
+    "title": "Accepted: Use the Humanoid Profile for Character Motion Mirroring",
     "section": "",
-    "text": "V-Sekai\nThis article is assisted by AI.\nhttps://github.com/V-Sekai/v-sekai-game/issues/68"
+    "text": "Daniel Snd did not utilize the Godot Engine humanoid profile."
   },
   {
-    "objectID": "decisions/20230408-v-sekai-launcher.html",
-    "href": "decisions/20230408-v-sekai-launcher.html",
-    "title": "Proposed: Provide v-sekai-game in a launcher to make it easier to use v-sekai",
+    "objectID": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#solution-description",
+    "href": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#solution-description",
+    "title": "Accepted: Use the Humanoid Profile for Character Motion Mirroring",
     "section": "",
-    "text": "Proposed: Provide v-sekai-game in a launcher to make it easier to use v-sekai\n\nMetadata\n\nStatus: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nContext and Problem Statement\nProvide v-sekai-game in a launcher.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nMake a graphical launcher that runs scoop.\nRun scoop bucket add v-sekai-central https://github.com/v-sekai/v-sekai-central.\nTo install, do scoop install v-sekai-game.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\n\nCreate a scoop bucket at https://github.com/V-Sekai/v-sekai-central\nStore game builds in git repos using desync to put separate the files into chunks.\nIn the manifest decompress the desync files.\n\n\n\nPositive Consequences\nWe are able to use V-Sekai easier.\n\n\nNegative Consequences\nWe cannot get other features in.\n\n\nOption graveyard\nDo nothing.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nThis is a json manifest which is a bit more than a few lines of script.\n\n\nIs there a reason why this should be core and done by us?\nWant to make it easier to use v-sekai.\n\n\nReferences\n\nV-Sekai"
+    "text": "The solution is to use the Godot Engine humanoid profile.\n\n\nIn Godot Engine, the animation humanoid profile is essential for managing bone rolls in incoming humanoid skeletons. This is because these skeletons often have arbitrary bone rolls that need to be standardized for consistent animation behavior.\n\n\nBone roll refers to the rotation around the bone’s longitudinal axis. In 3D modeling and animation, it’s important to correctly set up bone rolls as they determine the axes of rotation for the bones during animation.\n\n\n\nThe SkeletonProfileHumanoid in Godot 4.0 adopts a practical rule for managing bone rolls:\n\nThe +Y axis should point from the parent joint to the child joint. This is considered as the roll axis.\nThe +X rotation should bend the joints towards the body’s inside (almost the direction of muscle contraction).\n\n\n\n\nIf you mirror animations, the bone rolls and names may need to be corrected. This is because the orientation of the bones can get flipped during the mirroring process. The Godot Humanoid Profile applies a Bone Rule to the bone rolls.\n\n\n\nThe Godot Humanoid Profile standardizes the bone names consistently, it allows one to reuse animations across different characters. For example, if one has a walking animation for one character and one wants to apply it to another character, having the same bone names will allow one to do this without any additional work.\n\n\n\nIn 3D animation, the T-Pose is a standard pose where the character stands upright with their arms extended straight out to the sides. This pose is often used as the default pose for rigging and animating characters because it provides a clear view of all parts of the character. However, not all models are initially in a T-Pose. If you have a model in any other pose (let’s say it’s an A-Pose), you might need to convert it to a T-Pose before you can use it effectively in Godot.\n\n\n\n\nThe engine can ensure that all humanoid animations behave consistently, regardless of the original orientation or roll of the bones in the imported skeleton by following the Bone Rule. This makes it easier to create and manage humanoid animations, especially when working with different humanoids that may have been rigged differently."
   },
   {
-    "objectID": "decisions/20240710-art-direction-in-vsekai.html",
-    "href": "decisions/20240710-art-direction-in-vsekai.html",
-    "title": "Proposed: Art Direction in V-Sekai Process",
+    "objectID": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#benefits",
+    "href": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#benefits",
+    "title": "Accepted: Use the Humanoid Profile for Character Motion Mirroring",
     "section": "",
-    "text": "We visited a VRChat world for “Zenless Zone Zero” and discussed how cool the urban maze was created. Lyuma mentioned that he prefers wild open places. We also noted how Mihoyo has three distinct settings:\n\nMedieval (Genshin Impact)\nUrban Asia (Zenless Zone Zero)\nInterstellar (Star Rail)\n\n\n\n\nWe need an art direction in V-Sekai for our work. Without a defined art direction, we risk inconsistency and lack of cohesion in our visual presentation.\n\n\n\n\nConcept Art Creation: Develop initial concept art to explore different themes and styles.\nCommunity Feedback: Share concept art with the community for feedback and suggestions.\nStyle Guide Development: Create a comprehensive style guide based on the chosen art direction.\nImplementation: Apply the style guide across all assets and environments within V-Sekai.\n\n\n\n\n\nVisual Cohesion: A unified art direction ensures a consistent and professional appearance.\nEnhanced User Experience: A well-defined aesthetic can make the virtual environment more immersive and enjoyable.\nBrand Identity: Establishing a unique visual style helps in building a recognizable brand.\n\n\n\n\n\nLimited Creativity: Strict adherence to a specific art direction may limit creative expression.\nInitial Setup Time: Developing and implementing an art direction requires an initial investment of time and resources.\n\n\n\n\nAlternative approaches such as allowing individual artists complete freedom or using multiple art styles were considered but ultimately deemed less effective for maintaining visual consistency.\n\n\n\nIn scenarios where highly specialized or technical visual elements are required, additional oversight may be necessary to ensure they align with the overall art direction.\n\n\n\nThis proposal aligns with our core values of efficiency and professionalism and will be implemented by our team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "Using the Godot Humanoid Profile will allow for consistent behavior across all humanoid animations, making it easier to create and manage these animations. It also allows for reusability of animations across different characters, saving time and effort in animation creation."
   },
   {
-    "objectID": "decisions/20240710-art-direction-in-vsekai.html#the-context",
-    "href": "decisions/20240710-art-direction-in-vsekai.html#the-context",
-    "title": "Proposed: Art Direction in V-Sekai Process",
+    "objectID": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#downsides",
+    "href": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#downsides",
+    "title": "Accepted: Use the Humanoid Profile for Character Motion Mirroring",
     "section": "",
-    "text": "We visited a VRChat world for “Zenless Zone Zero” and discussed how cool the urban maze was created. Lyuma mentioned that he prefers wild open places. We also noted how Mihoyo has three distinct settings:\n\nMedieval (Genshin Impact)\nUrban Asia (Zenless Zone Zero)\nInterstellar (Star Rail)"
+    "text": "There may be a learning curve associated with understanding and implementing the Godot Humanoid Profile. Additionally, this solution assumes that all incoming humanoid skeletons will be compatible with the Godot Humanoid Profile, which may not always be the case."
   },
   {
-    "objectID": "decisions/20240710-art-direction-in-vsekai.html#the-problem-statement",
-    "href": "decisions/20240710-art-direction-in-vsekai.html#the-problem-statement",
-    "title": "Proposed: Art Direction in V-Sekai Process",
+    "objectID": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#the-road-not-taken",
+    "href": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#the-road-not-taken",
+    "title": "Accepted: Use the Humanoid Profile for Character Motion Mirroring",
     "section": "",
-    "text": "We need an art direction in V-Sekai for our work. Without a defined art direction, we risk inconsistency and lack of cohesion in our visual presentation."
+    "text": "An alternative could have been to manually adjust the bone rolls and names for each individual animation. However, this would be a time-consuming process and would not guarantee consistent results across different animations."
   },
   {
-    "objectID": "decisions/20240710-art-direction-in-vsekai.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240710-art-direction-in-vsekai.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Art Direction in V-Sekai Process",
+    "objectID": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#the-infrequent-use-case",
+    "href": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#the-infrequent-use-case",
+    "title": "Accepted: Use the Humanoid Profile for Character Motion Mirroring",
     "section": "",
-    "text": "Concept Art Creation: Develop initial concept art to explore different themes and styles.\nCommunity Feedback: Share concept art with the community for feedback and suggestions.\nStyle Guide Development: Create a comprehensive style guide based on the chosen art direction.\nImplementation: Apply the style guide across all assets and environments within V-Sekai."
+    "text": "This proposal may not be beneficial for non-humanoid animations or for projects that do not require motion mirroring."
   },
   {
-    "objectID": "decisions/20240710-art-direction-in-vsekai.html#the-benefits",
-    "href": "decisions/20240710-art-direction-in-vsekai.html#the-benefits",
-    "title": "Proposed: Art Direction in V-Sekai Process",
+    "objectID": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#in-core-and-done-by-us",
+    "href": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#in-core-and-done-by-us",
+    "title": "Accepted: Use the Humanoid Profile for Character Motion Mirroring",
     "section": "",
-    "text": "Visual Cohesion: A unified art direction ensures a consistent and professional appearance.\nEnhanced User Experience: A well-defined aesthetic can make the virtual environment more immersive and enjoyable.\nBrand Identity: Establishing a unique visual style helps in building a recognizable brand."
+    "text": "This proposal involves using an existing feature of the Godot Engine the V-Sekai team implemented in Godot Engine 4.0, so no additional development work would be required from our team."
   },
   {
-    "objectID": "decisions/20240710-art-direction-in-vsekai.html#the-downsides",
-    "href": "decisions/20240710-art-direction-in-vsekai.html#the-downsides",
-    "title": "Proposed: Art Direction in V-Sekai Process",
+    "objectID": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#status",
+    "href": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#status",
+    "title": "Accepted: Use the Humanoid Profile for Character Motion Mirroring",
     "section": "",
-    "text": "Limited Creativity: Strict adherence to a specific art direction may limit creative expression.\nInitial Setup Time: Developing and implementing an art direction requires an initial investment of time and resources."
+    "text": "Status: Accepted"
   },
   {
-    "objectID": "decisions/20240710-art-direction-in-vsekai.html#the-road-not-taken",
-    "href": "decisions/20240710-art-direction-in-vsekai.html#the-road-not-taken",
-    "title": "Proposed: Art Direction in V-Sekai Process",
+    "objectID": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#decision-makers",
+    "href": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#decision-makers",
+    "title": "Accepted: Use the Humanoid Profile for Character Motion Mirroring",
     "section": "",
-    "text": "Alternative approaches such as allowing individual artists complete freedom or using multiple art styles were considered but ultimately deemed less effective for maintaining visual consistency."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20240710-art-direction-in-vsekai.html#the-infrequent-use-case",
-    "href": "decisions/20240710-art-direction-in-vsekai.html#the-infrequent-use-case",
-    "title": "Proposed: Art Direction in V-Sekai Process",
+    "objectID": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#tags",
+    "href": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#tags",
+    "title": "Accepted: Use the Humanoid Profile for Character Motion Mirroring",
     "section": "",
-    "text": "In scenarios where highly specialized or technical visual elements are required, additional oversight may be necessary to ensure they align with the overall art direction."
+    "text": "Godot Engine\nHumanoid Profile\nAnimation Mirroring\nBone Rolls\nCharacter Avatar Motion\n3D Modeling\nT-Pose Conversion\nAnimation Reusability\nV-Sekai\nVR Animation"
   },
   {
-    "objectID": "decisions/20240710-art-direction-in-vsekai.html#in-core-and-done-by-us",
-    "href": "decisions/20240710-art-direction-in-vsekai.html#in-core-and-done-by-us",
-    "title": "Proposed: Art Direction in V-Sekai Process",
+    "objectID": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#further-reading",
+    "href": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#further-reading",
+    "title": "Accepted: Use the Humanoid Profile for Character Motion Mirroring",
     "section": "",
-    "text": "This proposal aligns with our core values of efficiency and professionalism and will be implemented by our team."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nFire\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240710-art-direction-in-vsekai.html#status",
-    "href": "decisions/20240710-art-direction-in-vsekai.html#status",
-    "title": "Proposed: Art Direction in V-Sekai Process",
+    "objectID": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#mirroring-script",
+    "href": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#mirroring-script",
+    "title": "Accepted: Use the Humanoid Profile for Character Motion Mirroring",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "## SPDX-License-Identifier: CC0-1.0\n##\n## Author: Daniel Snd\n\n@export var left_name:String = \"Left\"\n@export var right_name:String = \"Right\"\n\nfunc do_mirror():\n    var parenteless_ids :PackedInt32Array = get_parentless_bones()\n    for p in get_parentless_bones():\n        attempt_mirror_recursive(p)\n\nfunc attempt_mirror_recursive(bone_id:int):\n    for i in get_bone_children(bone_id):\n        var bone_name = get_bone_name(i)\n        if bone_name.contains(right_name):\n            mirror_pose(bone_name)\n        elif bone_name.contains(left_name):\n            pass\n        else:\n            mirror_single_bone(i)\n        attempt_mirror_recursive(i)\n\nfunc mirror_single_bone(bone_idx):\n    var mirrored_rot = get_bone_pose(bone_idx).basis.get_rotation_quaternion()\n    mirrored_rot.x *= -1\n    mirrored_rot.w *= -1\n    set_bone_pose_rotation(bone_idx, mirrored_rot)\n\n# Function to mirror pose\nfunc mirror_pose(bone_name):\n    var bone_idx = find_bone(bone_name)\n    if bone_idx == -1:\n        print(\"Bone does not exist in Skeleton\")\n        return\n\n    var mirrored_bone_idx = find_bone(bone_name.replace(right_name, left_name) if bone_name.contains(right_name) else bone_name.replace(left_name, right_name))\n    if mirrored_bone_idx == -1:\n        print(\"Mirrored bone does not exist in Skeleton\")\n        return\n\n    var tr :Transform3D = get_bone_pose(bone_idx)\n    var opposite_tr :Transform3D = get_bone_pose(mirrored_bone_idx)\n    var mirrored_rot = tr.basis.get_rotation_quaternion()\n    mirrored_rot.x *= -1\n    mirrored_rot.w *= -1\n\n    var opposite_mirrored_rot = opposite_tr.basis.get_rotation_quaternion()\n    opposite_mirrored_rot.x *= -1\n    opposite_mirrored_rot.w *= -1\n\n    set_bone_pose_rotation(mirrored_bone_idx, mirrored_rot)\n    set_bone_pose_rotation(bone_idx, opposite_mirrored_rot)"
   },
   {
-    "objectID": "decisions/20240710-art-direction-in-vsekai.html#decision-makers",
-    "href": "decisions/20240710-art-direction-in-vsekai.html#decision-makers",
-    "title": "Proposed: Art Direction in V-Sekai Process",
+    "objectID": "decisions/20211031-gltf-importer-should-bind-animation-players-to-the-closest-root-node.html",
+    "href": "decisions/20211031-gltf-importer-should-bind-animation-players-to-the-closest-root-node.html",
+    "title": "Proposed: glTF - importer should bind animation players to the closest root node",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "Proposed: glTF - importer should bind animation players to the closest root node\n\nContext and Problem Statement\nGodot currently creates one massive animation per scene. It is hard to organize.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nSplit the monolithic animation player.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nMove the animations on to different subbranches.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nCan be an addon\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nDoesn’t need to be done.\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240710-art-direction-in-vsekai.html#tags",
-    "href": "decisions/20240710-art-direction-in-vsekai.html#tags",
-    "title": "Proposed: Art Direction in V-Sekai Process",
+    "objectID": "decisions/20230123-publish-godot-vrm-4.html",
+    "href": "decisions/20230123-publish-godot-vrm-4.html",
+    "title": "Proposed: Publish Godot VRM for Godot 4 for production use",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Status: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nI want to be able to download the godot vrm addon from the asset library in 4.\n\n\n\nBy publishing we will have reviewed the bugs and decide it is ready to be use.\n\n\n\nSubmit godot vrm to the godot 4 asset library lyuma\nStarted because of discussion with https://twitter.com/AlfredBaudisch/status/1586999148171198465?s=20&t=nUHLXskgrxnTbPFN9WzZxQ about mtoon outlines\n\n\n\nWe’ll prepare for release.\n\n\n\nOld bugs might not be fixed.\n\n\n\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\n\nGodot VRM is a few gdscripts.\n\n\n\nGodot VRM is a core feature.\n\n\n\n\nV-Sekai\n\n\n\n\nMIT License\n\nCopyright (c) 2018-present SaracenOne\nCopyright (c) 2019-present K. S. Ernest (iFire) Lee (fire)\nCopyright (c) 2020-present Lyuma\nCopyright (c) 2020-present MMMaellon\nCopyright (c) 2022-present V-Sekai Contributors\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
   },
   {
-    "objectID": "decisions/20240710-art-direction-in-vsekai.html#further-reading",
-    "href": "decisions/20240710-art-direction-in-vsekai.html#further-reading",
-    "title": "Proposed: Art Direction in V-Sekai Process",
+    "objectID": "decisions/20230123-publish-godot-vrm-4.html#context-and-problem-statement",
+    "href": "decisions/20230123-publish-godot-vrm-4.html#context-and-problem-statement",
+    "title": "Proposed: Publish Godot VRM for Godot 4 for production use",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "I want to be able to download the godot vrm addon from the asset library in 4."
   },
   {
-    "objectID": "decisions/20240710-use-webrtc-to-native-interop.html",
-    "href": "decisions/20240710-use-webrtc-to-native-interop.html",
-    "title": "Proposed: Use WebRTC to Native to Interop with Godot Engine",
+    "objectID": "decisions/20230123-publish-godot-vrm-4.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20230123-publish-godot-vrm-4.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: Publish Godot VRM for Godot 4 for production use",
     "section": "",
-    "text": "In the realm of game development, particularly with the Godot Engine, enabling seamless communication between native clients and web clients is crucial. This proposal aims to address this need by leveraging WebRTC for interoperability.\n\n\n\nWe cannot connect between native clients and web clients for our Godot Engine game. This limitation hinders the user experience and restricts the game’s accessibility across different platforms.\n\n\n\nImplement WebRTC in both native and web clients to facilitate real-time communication.\nSet up a signaling server to manage the initial connection setup between clients.\nUtilize WebRTC data channels for efficient data transfer between clients.\nIntegrate WebRTC functionalities within the Godot Engine to ensure smooth operation.\n\n\n\n\nImproved Connectivity: Enables seamless communication between native and web clients.\nEnhanced User Experience: Provides a consistent gaming experience across different platforms.\nScalability: Facilitates the addition of new features that require real-time communication.\n\n\n\n\n\nComplexity: Implementing WebRTC can be complex and may require significant development effort.\nPerformance Overhead: Real-time communication may introduce performance overhead, especially on lower-end devices.\n\n\n\n\nAlternative approaches such as using traditional client-server models or other communication protocols were considered but ultimately deemed less efficient or effective for real-time communication needs.\n\n\n\nIn scenarios where highly specialized or technical language is required, additional human oversight may be necessary to ensure accuracy and appropriateness.\n\n\n\nThis proposal aligns with our core values of efficiency and professionalism and will be implemented by our team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "By publishing we will have reviewed the bugs and decide it is ready to be use."
   },
   {
-    "objectID": "decisions/20240710-use-webrtc-to-native-interop.html#the-context",
-    "href": "decisions/20240710-use-webrtc-to-native-interop.html#the-context",
-    "title": "Proposed: Use WebRTC to Native to Interop with Godot Engine",
+    "objectID": "decisions/20230123-publish-godot-vrm-4.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20230123-publish-godot-vrm-4.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Publish Godot VRM for Godot 4 for production use",
     "section": "",
-    "text": "In the realm of game development, particularly with the Godot Engine, enabling seamless communication between native clients and web clients is crucial. This proposal aims to address this need by leveraging WebRTC for interoperability."
+    "text": "Submit godot vrm to the godot 4 asset library lyuma\nStarted because of discussion with https://twitter.com/AlfredBaudisch/status/1586999148171198465?s=20&t=nUHLXskgrxnTbPFN9WzZxQ about mtoon outlines"
   },
   {
-    "objectID": "decisions/20240710-use-webrtc-to-native-interop.html#the-problem-statement",
-    "href": "decisions/20240710-use-webrtc-to-native-interop.html#the-problem-statement",
-    "title": "Proposed: Use WebRTC to Native to Interop with Godot Engine",
+    "objectID": "decisions/20230123-publish-godot-vrm-4.html#positive-consequences",
+    "href": "decisions/20230123-publish-godot-vrm-4.html#positive-consequences",
+    "title": "Proposed: Publish Godot VRM for Godot 4 for production use",
     "section": "",
-    "text": "We cannot connect between native clients and web clients for our Godot Engine game. This limitation hinders the user experience and restricts the game’s accessibility across different platforms."
+    "text": "We’ll prepare for release."
   },
   {
-    "objectID": "decisions/20240710-use-webrtc-to-native-interop.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240710-use-webrtc-to-native-interop.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Use WebRTC to Native to Interop with Godot Engine",
+    "objectID": "decisions/20230123-publish-godot-vrm-4.html#negative-consequences",
+    "href": "decisions/20230123-publish-godot-vrm-4.html#negative-consequences",
+    "title": "Proposed: Publish Godot VRM for Godot 4 for production use",
     "section": "",
-    "text": "Implement WebRTC in both native and web clients to facilitate real-time communication.\nSet up a signaling server to manage the initial connection setup between clients.\nUtilize WebRTC data channels for efficient data transfer between clients.\nIntegrate WebRTC functionalities within the Godot Engine to ensure smooth operation."
+    "text": "Old bugs might not be fixed."
   },
   {
-    "objectID": "decisions/20240710-use-webrtc-to-native-interop.html#the-benefits",
-    "href": "decisions/20240710-use-webrtc-to-native-interop.html#the-benefits",
-    "title": "Proposed: Use WebRTC to Native to Interop with Godot Engine",
+    "objectID": "decisions/20230123-publish-godot-vrm-4.html#option-graveyard",
+    "href": "decisions/20230123-publish-godot-vrm-4.html#option-graveyard",
+    "title": "Proposed: Publish Godot VRM for Godot 4 for production use",
     "section": "",
-    "text": "Improved Connectivity: Enables seamless communication between native and web clients.\nEnhanced User Experience: Provides a consistent gaming experience across different platforms.\nScalability: Facilitates the addition of new features that require real-time communication."
+    "text": "Option: The status quo. \nRejection Reason: This solves nothing."
   },
   {
-    "objectID": "decisions/20240710-use-webrtc-to-native-interop.html#the-downsides",
-    "href": "decisions/20240710-use-webrtc-to-native-interop.html#the-downsides",
-    "title": "Proposed: Use WebRTC to Native to Interop with Godot Engine",
+    "objectID": "decisions/20230123-publish-godot-vrm-4.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230123-publish-godot-vrm-4.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Publish Godot VRM for Godot 4 for production use",
     "section": "",
-    "text": "Complexity: Implementing WebRTC can be complex and may require significant development effort.\nPerformance Overhead: Real-time communication may introduce performance overhead, especially on lower-end devices."
+    "text": "Godot VRM is a few gdscripts."
   },
   {
-    "objectID": "decisions/20240710-use-webrtc-to-native-interop.html#the-road-not-taken",
-    "href": "decisions/20240710-use-webrtc-to-native-interop.html#the-road-not-taken",
-    "title": "Proposed: Use WebRTC to Native to Interop with Godot Engine",
+    "objectID": "decisions/20230123-publish-godot-vrm-4.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230123-publish-godot-vrm-4.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Publish Godot VRM for Godot 4 for production use",
     "section": "",
-    "text": "Alternative approaches such as using traditional client-server models or other communication protocols were considered but ultimately deemed less efficient or effective for real-time communication needs."
+    "text": "Godot VRM is a core feature."
   },
   {
-    "objectID": "decisions/20240710-use-webrtc-to-native-interop.html#the-infrequent-use-case",
-    "href": "decisions/20240710-use-webrtc-to-native-interop.html#the-infrequent-use-case",
-    "title": "Proposed: Use WebRTC to Native to Interop with Godot Engine",
+    "objectID": "decisions/20230123-publish-godot-vrm-4.html#references",
+    "href": "decisions/20230123-publish-godot-vrm-4.html#references",
+    "title": "Proposed: Publish Godot VRM for Godot 4 for production use",
     "section": "",
-    "text": "In scenarios where highly specialized or technical language is required, additional human oversight may be necessary to ensure accuracy and appropriateness."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20240710-use-webrtc-to-native-interop.html#in-core-and-done-by-us",
-    "href": "decisions/20240710-use-webrtc-to-native-interop.html#in-core-and-done-by-us",
-    "title": "Proposed: Use WebRTC to Native to Interop with Godot Engine",
+    "objectID": "decisions/20230123-publish-godot-vrm-4.html#license-of-the-contribution",
+    "href": "decisions/20230123-publish-godot-vrm-4.html#license-of-the-contribution",
+    "title": "Proposed: Publish Godot VRM for Godot 4 for production use",
     "section": "",
-    "text": "This proposal aligns with our core values of efficiency and professionalism and will be implemented by our team."
+    "text": "MIT License\n\nCopyright (c) 2018-present SaracenOne\nCopyright (c) 2019-present K. S. Ernest (iFire) Lee (fire)\nCopyright (c) 2020-present Lyuma\nCopyright (c) 2020-present MMMaellon\nCopyright (c) 2022-present V-Sekai Contributors\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
   },
   {
-    "objectID": "decisions/20240710-use-webrtc-to-native-interop.html#status",
-    "href": "decisions/20240710-use-webrtc-to-native-interop.html#status",
-    "title": "Proposed: Use WebRTC to Native to Interop with Godot Engine",
+    "objectID": "decisions/20240425-recharge-cycle.html",
+    "href": "decisions/20240425-recharge-cycle.html",
+    "title": "Proposed: Stuck / Recharge Cycle",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "In the realm of software development, it’s common for developers to hit a wall or get “stuck” on a particular problem. This can lead to frustration and decreased productivity.\n\n\n\nDevelopers often find themselves stuck on a problem, unable to make progress. This can be due to a variety of reasons such as lack of understanding, complexity of the problem, or simply mental fatigue.\n\n\n\nThe proposed solution is a “Stuck/Recharge” cycle. When a developer finds themselves stuck on a problem, they switch to working on someone else’s problem. This change in perspective can help recharge their mental energy and when they return to their original problem, they may find that they are able to approach it with a fresh mindset.\nif (developer.isStuck()) {\n    developer.switchTask();\n    developer.recharge();\n    developer.returnToOriginalTask();\n}\n\n\n\nThis approach can help prevent burnout and increase overall productivity. It also promotes collaboration and knowledge sharing among the team.\n\n\n\nThere could be potential downsides such as context switching overhead and disruption of flow. However, these can be mitigated with proper task management and communication within the team.\n\n\n\nAn alternative approach could be to have dedicated “unsticking” sessions where developers come together to brainstorm solutions for stuck problems. However, this requires coordination and may not be as flexible as the proposed solution.\n\n\n\nThis proposal may not be beneficial for simple tasks or for developers who rarely get stuck.\n\n\n\nThis proposal is applicable to our core development process and can be implemented by us.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240710-use-webrtc-to-native-interop.html#decision-makers",
-    "href": "decisions/20240710-use-webrtc-to-native-interop.html#decision-makers",
-    "title": "Proposed: Use WebRTC to Native to Interop with Godot Engine",
+    "objectID": "decisions/20240425-recharge-cycle.html#the-context",
+    "href": "decisions/20240425-recharge-cycle.html#the-context",
+    "title": "Proposed: Stuck / Recharge Cycle",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "In the realm of software development, it’s common for developers to hit a wall or get “stuck” on a particular problem. This can lead to frustration and decreased productivity."
   },
   {
-    "objectID": "decisions/20240710-use-webrtc-to-native-interop.html#tags",
-    "href": "decisions/20240710-use-webrtc-to-native-interop.html#tags",
-    "title": "Proposed: Use WebRTC to Native to Interop with Godot Engine",
+    "objectID": "decisions/20240425-recharge-cycle.html#the-problem-statement",
+    "href": "decisions/20240425-recharge-cycle.html#the-problem-statement",
+    "title": "Proposed: Stuck / Recharge Cycle",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Developers often find themselves stuck on a problem, unable to make progress. This can be due to a variety of reasons such as lack of understanding, complexity of the problem, or simply mental fatigue."
   },
   {
-    "objectID": "decisions/20240710-use-webrtc-to-native-interop.html#further-reading",
-    "href": "decisions/20240710-use-webrtc-to-native-interop.html#further-reading",
-    "title": "Proposed: Use WebRTC to Native to Interop with Godot Engine",
+    "objectID": "decisions/20240425-recharge-cycle.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240425-recharge-cycle.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Stuck / Recharge Cycle",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "The proposed solution is a “Stuck/Recharge” cycle. When a developer finds themselves stuck on a problem, they switch to working on someone else’s problem. This change in perspective can help recharge their mental energy and when they return to their original problem, they may find that they are able to approach it with a fresh mindset.\nif (developer.isStuck()) {\n    developer.switchTask();\n    developer.recharge();\n    developer.returnToOriginalTask();\n}"
   },
   {
-    "objectID": "decisions/20230620-t5-jsonformer-xstate.html",
-    "href": "decisions/20230620-t5-jsonformer-xstate.html",
-    "title": "Proposed: Large language model t5 generating xstate json reliabily for digital beings",
+    "objectID": "decisions/20240425-recharge-cycle.html#the-benefits",
+    "href": "decisions/20240425-recharge-cycle.html#the-benefits",
+    "title": "Proposed: Stuck / Recharge Cycle",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nV-Sekai is facing a limitation that requires a solution to convert natural language text into XState JSON format for executing behavior statecharts for digital beings. This can be achieved by using the T5 (Text-to-Text Transfer Transformer) model with JSON-former for XState in Godot Engine 4.0.\n\n\n\nThe proposed solution involves using the T5 model to generate text based on input text and then converting the generated text into XState JSON format, all within the Godot Engine 4.0 environment.\n\n\n\nTo use T5 (Text-to-Text Transfer Transformer) with JSON-former for XState in Godot Engine 4.0, you’ll need to follow these steps:\n\nLoad the necessary libraries\n\nvar transformers = preload(\"res://path/to/transformers.gd\")\nvar torch = preload(\"res://path/to/torch.gd\")\n\nLoad the T5 model and tokenizer\n\nvar model_name = \"t5-small\"\nvar tokenizer = transformers.load_T5Tokenizer(model_name)\nvar model = transformers.load_T5ForConditionalGeneration(model_name)\n\nCreate a function to generate text using T5\n\nfunc generate_text(input_text: String) -&gt; String:\n    var input_ids = tokenizer.encode(input_text)\n    var outputs = model.generate(input_ids)\n    var generated_text = tokenizer.decode(outputs[0])\n    return generated_text\n\nCreate a function to replace placeholders in T5 output\n\nfunc replace_placeholders(text: String) -&gt; String:\n    var formatted_text = text.replace(\"&lt;extra_id_0&gt;\", \"event\").replace(\"&lt;extra_id_1&gt;\", \"state\")\n    return formatted_text\n\nCreate a function to parse JSON from formatted text\n\nfunc parse_JSON(formatted_text: String) -&gt; Dictionary:\n    var json_object = JSON.parse(formatted_text).result\n    return json_object\n\nCreate a function to convert T5 output to XState JSON format\n\nfunc t5_to_jsonformer_xstate(text: String) -&gt; Dictionary:\n    var formatted_text = replace_placeholders(text)\n    var json_object = parse_JSON(formatted_text)\n    return json_object\n\nUse the functions to generate XState JSON\n\nfunc _ready():\n    var input_text = \"your input text here\"\n    var t5_output = generate_text(input_text)\n    var xstate_json = t5_to_jsonformer_xstate(t5_output)\n    print(xstate_json)\nThis will give you the XState JSON format for the given input text. Note that the T5 model might need to be fine-tuned on a dataset specific to your use case to generate accurate XState JSON representations.\n\n\n\n\nAutomates the process of converting natural language text into XState JSON format within the Godot Engine 4.0 environment.\nReduces manual effort and potential errors in creating XState JSON representations.\n\n\n\n\n\nThe T5 model may require fine-tuning on a specific dataset to generate accurate XState JSON representations.\nThere might be limitations in understanding complex or ambiguous input text.\n\n\n\n\nHere are some option graveyard items for the proposal:\n\nUsing rule-based natural language processing (NLP) techniques\n\nPros:\n\nEasier to implement and understand.\nNo need for training data or fine-tuning.\n\nCons:\n\nLimited in handling complex or ambiguous input text.\nRequires manual updates to rules as new use cases emerge.\n\n\nUsing other pre-trained NLP models (e.g., GPT-3, BERT)\n\nPros:\n\nCan leverage existing state-of-the-art NLP models.\nMay provide better performance on certain tasks.\n\nCons:\n\nMay require additional fine-tuning or adaptation for the specific task.\nSome models may have higher computational requirements or costs.\n\n\nCreating a custom NLP model from scratch\n\nPros:\n\nTailored specifically for the task of converting natural language text into XState JSON format.\nPotential for better performance if designed well.\n\nCons:\n\nRequires significant time and effort to develop, train, and maintain.\nMay not perform as well as existing state-of-the-art models.\n\n\nUsing an external API or service for natural language understanding\n\nPros:\n\nOffloads the complexity of NLP to an external service.\nCan potentially leverage more advanced NLP techniques.\n\nCons:\n\nIntroduces dependency on an external service.\nMay incur additional costs or usage limitations.\n\n\n\nThese options were considered but ultimately discarded in favor of using the T5 model with JSON-former for XState in Godot Engine 4.0 due to its balance of performance, ease of implementation, and adaptability to the specific task.\n\n\n\nThe proposed solution requires more than a few lines of script and involves using a pre-trained model (T5) to generate the desired output within the Godot Engine 4.0 environment.\n\n\n\nImplementing this solution as part of the core functionality can help V-Sekai users automate the process of generating XState JSON representations from natural language text within the Godot Engine 4.0 environment, improving efficiency and reducing manual effort.\n\n\n\n\nV-Sekai\nGodot Engine\nGDScript documentation\nT5 (Text-to-Text Transfer Transformer)\nTransformers library\nXState documentation"
+    "text": "This approach can help prevent burnout and increase overall productivity. It also promotes collaboration and knowledge sharing among the team."
   },
   {
-    "objectID": "decisions/20230620-t5-jsonformer-xstate.html#metadata",
-    "href": "decisions/20230620-t5-jsonformer-xstate.html#metadata",
-    "title": "Proposed: Large language model t5 generating xstate json reliabily for digital beings",
+    "objectID": "decisions/20240425-recharge-cycle.html#the-downsides",
+    "href": "decisions/20240425-recharge-cycle.html#the-downsides",
+    "title": "Proposed: Stuck / Recharge Cycle",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai"
+    "text": "There could be potential downsides such as context switching overhead and disruption of flow. However, these can be mitigated with proper task management and communication within the team."
   },
   {
-    "objectID": "decisions/20230620-t5-jsonformer-xstate.html#context-and-problem-statement",
-    "href": "decisions/20230620-t5-jsonformer-xstate.html#context-and-problem-statement",
-    "title": "Proposed: Large language model t5 generating xstate json reliabily for digital beings",
+    "objectID": "decisions/20240425-recharge-cycle.html#the-road-not-taken",
+    "href": "decisions/20240425-recharge-cycle.html#the-road-not-taken",
+    "title": "Proposed: Stuck / Recharge Cycle",
     "section": "",
-    "text": "V-Sekai is facing a limitation that requires a solution to convert natural language text into XState JSON format for executing behavior statecharts for digital beings. This can be achieved by using the T5 (Text-to-Text Transfer Transformer) model with JSON-former for XState in Godot Engine 4.0."
+    "text": "An alternative approach could be to have dedicated “unsticking” sessions where developers come together to brainstorm solutions for stuck problems. However, this requires coordination and may not be as flexible as the proposed solution."
   },
   {
-    "objectID": "decisions/20230620-t5-jsonformer-xstate.html#proposed-solution",
-    "href": "decisions/20230620-t5-jsonformer-xstate.html#proposed-solution",
-    "title": "Proposed: Large language model t5 generating xstate json reliabily for digital beings",
+    "objectID": "decisions/20240425-recharge-cycle.html#the-infrequent-use-case",
+    "href": "decisions/20240425-recharge-cycle.html#the-infrequent-use-case",
+    "title": "Proposed: Stuck / Recharge Cycle",
     "section": "",
-    "text": "The proposed solution involves using the T5 model to generate text based on input text and then converting the generated text into XState JSON format, all within the Godot Engine 4.0 environment."
+    "text": "This proposal may not be beneficial for simple tasks or for developers who rarely get stuck."
   },
   {
-    "objectID": "decisions/20230620-t5-jsonformer-xstate.html#implementation",
-    "href": "decisions/20230620-t5-jsonformer-xstate.html#implementation",
-    "title": "Proposed: Large language model t5 generating xstate json reliabily for digital beings",
+    "objectID": "decisions/20240425-recharge-cycle.html#in-core-and-done-by-us",
+    "href": "decisions/20240425-recharge-cycle.html#in-core-and-done-by-us",
+    "title": "Proposed: Stuck / Recharge Cycle",
     "section": "",
-    "text": "To use T5 (Text-to-Text Transfer Transformer) with JSON-former for XState in Godot Engine 4.0, you’ll need to follow these steps:\n\nLoad the necessary libraries\n\nvar transformers = preload(\"res://path/to/transformers.gd\")\nvar torch = preload(\"res://path/to/torch.gd\")\n\nLoad the T5 model and tokenizer\n\nvar model_name = \"t5-small\"\nvar tokenizer = transformers.load_T5Tokenizer(model_name)\nvar model = transformers.load_T5ForConditionalGeneration(model_name)\n\nCreate a function to generate text using T5\n\nfunc generate_text(input_text: String) -&gt; String:\n    var input_ids = tokenizer.encode(input_text)\n    var outputs = model.generate(input_ids)\n    var generated_text = tokenizer.decode(outputs[0])\n    return generated_text\n\nCreate a function to replace placeholders in T5 output\n\nfunc replace_placeholders(text: String) -&gt; String:\n    var formatted_text = text.replace(\"&lt;extra_id_0&gt;\", \"event\").replace(\"&lt;extra_id_1&gt;\", \"state\")\n    return formatted_text\n\nCreate a function to parse JSON from formatted text\n\nfunc parse_JSON(formatted_text: String) -&gt; Dictionary:\n    var json_object = JSON.parse(formatted_text).result\n    return json_object\n\nCreate a function to convert T5 output to XState JSON format\n\nfunc t5_to_jsonformer_xstate(text: String) -&gt; Dictionary:\n    var formatted_text = replace_placeholders(text)\n    var json_object = parse_JSON(formatted_text)\n    return json_object\n\nUse the functions to generate XState JSON\n\nfunc _ready():\n    var input_text = \"your input text here\"\n    var t5_output = generate_text(input_text)\n    var xstate_json = t5_to_jsonformer_xstate(t5_output)\n    print(xstate_json)\nThis will give you the XState JSON format for the given input text. Note that the T5 model might need to be fine-tuned on a dataset specific to your use case to generate accurate XState JSON representations."
+    "text": "This proposal is applicable to our core development process and can be implemented by us."
   },
   {
-    "objectID": "decisions/20230620-t5-jsonformer-xstate.html#positive-consequences",
-    "href": "decisions/20230620-t5-jsonformer-xstate.html#positive-consequences",
-    "title": "Proposed: Large language model t5 generating xstate json reliabily for digital beings",
+    "objectID": "decisions/20240425-recharge-cycle.html#status",
+    "href": "decisions/20240425-recharge-cycle.html#status",
+    "title": "Proposed: Stuck / Recharge Cycle",
     "section": "",
-    "text": "Automates the process of converting natural language text into XState JSON format within the Godot Engine 4.0 environment.\nReduces manual effort and potential errors in creating XState JSON representations."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20230620-t5-jsonformer-xstate.html#negative-consequences",
-    "href": "decisions/20230620-t5-jsonformer-xstate.html#negative-consequences",
-    "title": "Proposed: Large language model t5 generating xstate json reliabily for digital beings",
+    "objectID": "decisions/20240425-recharge-cycle.html#decision-makers",
+    "href": "decisions/20240425-recharge-cycle.html#decision-makers",
+    "title": "Proposed: Stuck / Recharge Cycle",
     "section": "",
-    "text": "The T5 model may require fine-tuning on a specific dataset to generate accurate XState JSON representations.\nThere might be limitations in understanding complex or ambiguous input text."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20230620-t5-jsonformer-xstate.html#option-graveyard",
-    "href": "decisions/20230620-t5-jsonformer-xstate.html#option-graveyard",
-    "title": "Proposed: Large language model t5 generating xstate json reliabily for digital beings",
+    "objectID": "decisions/20240425-recharge-cycle.html#tags",
+    "href": "decisions/20240425-recharge-cycle.html#tags",
+    "title": "Proposed: Stuck / Recharge Cycle",
     "section": "",
-    "text": "Here are some option graveyard items for the proposal:\n\nUsing rule-based natural language processing (NLP) techniques\n\nPros:\n\nEasier to implement and understand.\nNo need for training data or fine-tuning.\n\nCons:\n\nLimited in handling complex or ambiguous input text.\nRequires manual updates to rules as new use cases emerge.\n\n\nUsing other pre-trained NLP models (e.g., GPT-3, BERT)\n\nPros:\n\nCan leverage existing state-of-the-art NLP models.\nMay provide better performance on certain tasks.\n\nCons:\n\nMay require additional fine-tuning or adaptation for the specific task.\nSome models may have higher computational requirements or costs.\n\n\nCreating a custom NLP model from scratch\n\nPros:\n\nTailored specifically for the task of converting natural language text into XState JSON format.\nPotential for better performance if designed well.\n\nCons:\n\nRequires significant time and effort to develop, train, and maintain.\nMay not perform as well as existing state-of-the-art models.\n\n\nUsing an external API or service for natural language understanding\n\nPros:\n\nOffloads the complexity of NLP to an external service.\nCan potentially leverage more advanced NLP techniques.\n\nCons:\n\nIntroduces dependency on an external service.\nMay incur additional costs or usage limitations.\n\n\n\nThese options were considered but ultimately discarded in favor of using the T5 model with JSON-former for XState in Godot Engine 4.0 due to its balance of performance, ease of implementation, and adaptability to the specific task."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20230620-t5-jsonformer-xstate.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230620-t5-jsonformer-xstate.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Large language model t5 generating xstate json reliabily for digital beings",
+    "objectID": "decisions/20240425-recharge-cycle.html#further-reading",
+    "href": "decisions/20240425-recharge-cycle.html#further-reading",
+    "title": "Proposed: Stuck / Recharge Cycle",
     "section": "",
-    "text": "The proposed solution requires more than a few lines of script and involves using a pre-trained model (T5) to generate the desired output within the Godot Engine 4.0 environment."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20230620-t5-jsonformer-xstate.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230620-t5-jsonformer-xstate.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Large language model t5 generating xstate json reliabily for digital beings",
+    "objectID": "decisions/20210523-basis-universal-import.html",
+    "href": "decisions/20210523-basis-universal-import.html",
+    "title": "Accepted: Support more flexible texture import via Basis Universal in Godot Engine",
     "section": "",
-    "text": "Implementing this solution as part of the core functionality can help V-Sekai users automate the process of generating XState JSON representations from natural language text within the Godot Engine 4.0 environment, improving efficiency and reducing manual effort."
+    "text": "Support more flexible texture import via Basis Universal in Godot Engine. Adding Basis Universal allows more flexibility in the import. –&gt;\n\n\n\n\nBasis Universal\n\n\n\n\nChosen option: Basis Universal\n\n\n\nMore flexibility between mobile and desktop\n\n\n\n\n\nDramatically slower import\nTexture limits?\n\n\n\n\n\n\n\nAdd basis universal to Godot Engine via glTF\n\nGood, because Basis Universal isn’t fully supported in the import pipeline\nGood, because it bridges Web, Desktop and Mobile\nBad, because makes importing slower\n\n\n\n\n\n\nhttps://github.com/KhronosGroup/glTF/blob/master/extensions/2.0/Khronos/KHR_texture_basisu/README.md\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230620-t5-jsonformer-xstate.html#references",
-    "href": "decisions/20230620-t5-jsonformer-xstate.html#references",
-    "title": "Proposed: Large language model t5 generating xstate json reliabily for digital beings",
+    "objectID": "decisions/20210523-basis-universal-import.html#context-and-problem-statement",
+    "href": "decisions/20210523-basis-universal-import.html#context-and-problem-statement",
+    "title": "Accepted: Support more flexible texture import via Basis Universal in Godot Engine",
     "section": "",
-    "text": "V-Sekai\nGodot Engine\nGDScript documentation\nT5 (Text-to-Text Transfer Transformer)\nTransformers library\nXState documentation"
+    "text": "Support more flexible texture import via Basis Universal in Godot Engine. Adding Basis Universal allows more flexibility in the import. –&gt;"
   },
   {
-    "objectID": "decisions/20210811-godot-transparency.html",
-    "href": "decisions/20210811-godot-transparency.html",
-    "title": "Accepted: OIT in Godot Engine",
+    "objectID": "decisions/20210523-basis-universal-import.html#considered-options",
+    "href": "decisions/20210523-basis-universal-import.html#considered-options",
+    "title": "Accepted: Support more flexible texture import via Basis Universal in Godot Engine",
     "section": "",
-    "text": "Accepted: OIT in Godot Engine\n\nContext and Problem Statement\nRender hair well.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nUse “Shortcut” or “PPLL” to render OIT transparency.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n\nShortcut takes 4 passes but is faster.\n\nTressFX technology uses order independent transparency.\n\n(OIT). There are two variants. One uses a per-pixel linked list (PPLL), and the other uses a multi-pass method referred to as Shortcut.\n\n\nThe main decision to make is whether to use per-pixel linked lists or Shortcut. The Shortcut method can be generally faster, with an easier memory bound, but at the expense of some quality. The TressFX 4.1/Unreal 4.22 Engine integration uses Shortcut (although the shader for PPLL may still be present in the branch, it was/is unmodified/untested/unused). TressFX 4.1/Cauldron uses both Shortcut and PPLL.\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nAvatars are a strength of V-Sekai.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nCode complexity.\n\n\nIs there a reason why this should be core and done by us?\nReduz isn’t interested in OIT.\n\n\nReferences\n\nhttps://raw.githubusercontent.com/GPUOpen-Effects/TressFX/master/doc/TressFX4xDeveloperGuide.pdf\nhttps://github.com/GPUOpen-Effects/TressFX/blob/master/src/Shaders/TressFXPPLL.hlsl\nhttps://github.com/GPUOpen-Effects/TressFX/blob/master/src/Shaders/TressFXShortCut.hlsl\nhttps://blog.icare3d.org/2010/07/opengl-40-abuffer-v20-linked-lists-of.html\nhttps://github.com/SaschaWillems/Vulkan/blob/master/examples/oit/oit.cpp\n\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Basis Universal"
   },
   {
-    "objectID": "decisions/20230619-membrane-framework-for-mesh-processing.html",
-    "href": "decisions/20230619-membrane-framework-for-mesh-processing.html",
-    "title": "Proposed: Networked Procedural Generation as a Sidecar to the Godot Engine Server",
+    "objectID": "decisions/20210523-basis-universal-import.html#decision-outcome",
+    "href": "decisions/20210523-basis-universal-import.html#decision-outcome",
+    "title": "Accepted: Support more flexible texture import via Basis Universal in Godot Engine",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai, fire\nTags: V-Sekai, Chatbot GPT4 assistance\n\n\n\n\nEnable creation of more dynamic and engaging environments within V-Sekai.\n\n\n\nV-Sekai, an open-source virtual reality platform, aims to deliver a user-friendly experience for the VR community. To boost its functionality and compatibility with other tools, we propose integrating networked procedural generation as a sidecar to the Godot engine server, allowing for more dynamic and immersive environments in V-Sekai.\nTo further address V-Sekai’s limitations, we suggest incorporating the Membrane Framework along with other relevant technologies such as Godot Engine, OpenMfx Support, Elixir Phoenix, and Elixir Nx. This comprehensive integration will not only enhance V-Sekai’s capabilities but also increase its versatility across various use cases.\nThe implementation involves connecting V-Sekai with the components mentioned in the Membrane Framework diagram below:\nsequenceDiagram\n  participant MembraneFramework\n  participant WebAndGodotEngineAndBlenderClient\n  participant ElixirNx\n  participant AIMLFramework\n  participant Yugabyte\n\n  rect rgb(240, 248, 255)\n    note over MembraneFramework, Yugabyte: Toggle Actions\n    MembraneFramework-&gt;&gt;WebAndGodotEngineAndBlenderClient: TOGGLE_GAME_ENGINE_AND_CLIENTS\n    MembraneFramework-&gt;&gt;ElixirNx: ACCELERATE_MEMBRANE_FRAMEWORK\n    MembraneFramework-&gt;&gt;AIMLFramework: TOGGLE_AIML_FRAMEWORK\n    MembraneFramework-&gt;&gt;Yugabyte: TOGGLE_YUGABYTE\n  end\n\n  box \"Source\" #CCFFCC\n    participant MembraneFramework\n    participant WebAndGodotEngineAndBlenderClient\n  end\n\n  box \"Filter\" #FFFFCC\n    participant ElixirNx\n    participant AIMLFramework\n  end\n\n  box \"Sink & Source of Data\" #FFCCCC\n    participant Yugabyte\n  end\n\n\nWe propose using read replicas for applications needing single-zone writes and multi-region reads. Benefits include:\n\nResilience: Zone-level resilience with primary cluster nodes across multiple zones.\nConsistency: Timeline consistency in replica clusters, better than eventual consistency.\nLatency: Quick reads from primary and replica clusters; write latency depends on client-primary cluster distance.\n\n\n\n\n\n\nImproved functionality and versatility of V-Sekai\nEnhanced compatibility with other tools and platforms\nGreater potential for collaboration and community involvement\n\n\n\n\n\nIncreased complexity in implementation and maintenance\nPotential performance overhead due to integration of multiple components\n\n\n\n\n\nStandalone procedural generation: Implementing procedural generation as a standalone feature without integrating it with the Godot Engine server. This option was discarded because it would not provide the same level of compatibility and versatility as the proposed solution.\nUsing pre-built assets: Relying on pre-built assets for creating environments instead of implementing networked procedural generation. This option was discarded due to the limited flexibility and potential for repetitive content, which could negatively impact user engagement.\nThird-party procedural generation tools: Integrating third-party procedural generation tools instead of developing a custom solution. This option was discarded because it may not offer the same level of control and customization required for V-Sekai’s specific needs.\nStatic environment design: Focusing on static environment design rather than dynamic, procedurally generated content. This option was discarded because it would not provide the desired level of immersion and interactivity for V-Sekai users.\n\n\n\n\nNo, the proposed solution involves integrating multiple technologies and cannot be achieved with a simple script workaround.\n\n\n\nYes, addressing the limitations of V-Sekai is crucial for its success and adoption within the VR community. By integrating the proposed technologies, we can ensure that V-Sekai remains competitive and relevant in the rapidly evolving VR landscape.\n\n\n\n\nV-Sekai"
+    "text": "Chosen option: Basis Universal\n\n\n\nMore flexibility between mobile and desktop\n\n\n\n\n\nDramatically slower import\nTexture limits?"
   },
   {
-    "objectID": "decisions/20230619-membrane-framework-for-mesh-processing.html#metadata",
-    "href": "decisions/20230619-membrane-framework-for-mesh-processing.html#metadata",
-    "title": "Proposed: Networked Procedural Generation as a Sidecar to the Godot Engine Server",
+    "objectID": "decisions/20210523-basis-universal-import.html#pros-and-cons-of-the-options",
+    "href": "decisions/20210523-basis-universal-import.html#pros-and-cons-of-the-options",
+    "title": "Accepted: Support more flexible texture import via Basis Universal in Godot Engine",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai, fire\nTags: V-Sekai, Chatbot GPT4 assistance"
+    "text": "Add basis universal to Godot Engine via glTF\n\nGood, because Basis Universal isn’t fully supported in the import pipeline\nGood, because it bridges Web, Desktop and Mobile\nBad, because makes importing slower"
   },
   {
-    "objectID": "decisions/20230619-membrane-framework-for-mesh-processing.html#context-and-problem-statement",
-    "href": "decisions/20230619-membrane-framework-for-mesh-processing.html#context-and-problem-statement",
-    "title": "Proposed: Networked Procedural Generation as a Sidecar to the Godot Engine Server",
+    "objectID": "decisions/20210523-basis-universal-import.html#references",
+    "href": "decisions/20210523-basis-universal-import.html#references",
+    "title": "Accepted: Support more flexible texture import via Basis Universal in Godot Engine",
     "section": "",
-    "text": "Enable creation of more dynamic and engaging environments within V-Sekai."
+    "text": "https://github.com/KhronosGroup/glTF/blob/master/extensions/2.0/Khronos/KHR_texture_basisu/README.md"
   },
   {
-    "objectID": "decisions/20230619-membrane-framework-for-mesh-processing.html#proposed-solution",
-    "href": "decisions/20230619-membrane-framework-for-mesh-processing.html#proposed-solution",
-    "title": "Proposed: Networked Procedural Generation as a Sidecar to the Godot Engine Server",
+    "objectID": "decisions/20210523-basis-universal-import.html#derivative-license",
+    "href": "decisions/20210523-basis-universal-import.html#derivative-license",
+    "title": "Accepted: Support more flexible texture import via Basis Universal in Godot Engine",
     "section": "",
-    "text": "V-Sekai, an open-source virtual reality platform, aims to deliver a user-friendly experience for the VR community. To boost its functionality and compatibility with other tools, we propose integrating networked procedural generation as a sidecar to the Godot engine server, allowing for more dynamic and immersive environments in V-Sekai.\nTo further address V-Sekai’s limitations, we suggest incorporating the Membrane Framework along with other relevant technologies such as Godot Engine, OpenMfx Support, Elixir Phoenix, and Elixir Nx. This comprehensive integration will not only enhance V-Sekai’s capabilities but also increase its versatility across various use cases.\nThe implementation involves connecting V-Sekai with the components mentioned in the Membrane Framework diagram below:\nsequenceDiagram\n  participant MembraneFramework\n  participant WebAndGodotEngineAndBlenderClient\n  participant ElixirNx\n  participant AIMLFramework\n  participant Yugabyte\n\n  rect rgb(240, 248, 255)\n    note over MembraneFramework, Yugabyte: Toggle Actions\n    MembraneFramework-&gt;&gt;WebAndGodotEngineAndBlenderClient: TOGGLE_GAME_ENGINE_AND_CLIENTS\n    MembraneFramework-&gt;&gt;ElixirNx: ACCELERATE_MEMBRANE_FRAMEWORK\n    MembraneFramework-&gt;&gt;AIMLFramework: TOGGLE_AIML_FRAMEWORK\n    MembraneFramework-&gt;&gt;Yugabyte: TOGGLE_YUGABYTE\n  end\n\n  box \"Source\" #CCFFCC\n    participant MembraneFramework\n    participant WebAndGodotEngineAndBlenderClient\n  end\n\n  box \"Filter\" #FFFFCC\n    participant ElixirNx\n    participant AIMLFramework\n  end\n\n  box \"Sink & Source of Data\" #FFCCCC\n    participant Yugabyte\n  end\n\n\nWe propose using read replicas for applications needing single-zone writes and multi-region reads. Benefits include:\n\nResilience: Zone-level resilience with primary cluster nodes across multiple zones.\nConsistency: Timeline consistency in replica clusters, better than eventual consistency.\nLatency: Quick reads from primary and replica clusters; write latency depends on client-primary cluster distance."
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230619-membrane-framework-for-mesh-processing.html#positive-consequences",
-    "href": "decisions/20230619-membrane-framework-for-mesh-processing.html#positive-consequences",
-    "title": "Proposed: Networked Procedural Generation as a Sidecar to the Godot Engine Server",
+    "objectID": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html",
+    "href": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html",
+    "title": "Accepted: Take a list of 3D points that form a vaguely closed boundary in space and triangulate in Godot Engine",
     "section": "",
-    "text": "Improved functionality and versatility of V-Sekai\nEnhanced compatibility with other tools and platforms\nGreater potential for collaboration and community involvement"
+    "text": "Status: accepted \nDeciders: V-Sekai,fire,em-yu\nTags: V-Sekai,\n\n\n\nCASSIE is a method for Curve And Surface Sketching in Immersive Environments.\nA core part of the CASSIE algorithm is to take a list of 3D points that form a vaguely closed boundary in space and triangulate.\n\n\n\nThis CASSIE triangulate operation needs to be done in Godot Engine so it can be use in V-Sekai.\n\n\n\n\nImplement “An Algorithm for Triangulating Multiple 3D Polygons”\nUse Godot’s delaunay tetrahedralize https://github.com/godotengine/godot/blob/96d7bc62af25b85b8b9cc091eeea1e7a784ba624/core/math/delaunay_3d.h#L145 static Vector&lt;OutputSimplex&gt; tetrahedralize(const Vector&lt;Vector3&gt; &p_points)\nEmilie Yu described a method for smoothing meshes.\n\nLibigl should be best for smoothing while pinning the boundaries. I see they have a solver that can take fixed boundary constraints https://libigl.github.io/tutorial/#quadratic-energy-minimization so that could allow you to pin the boundaries. So instead of this line it would be something like\nigl::min_quad_with_fixed_data mqwf;\nigl::min_quad_with_fixed_precompute(S, [flat vector of indices of boundary vertices size=(3 * N_boundary)], [zero matrix], true, mqwf);\nigl::min_quad_with_fixed_solve(mqwf, M * U, [flat vector of boundary vertices positions size=(3 * N_boundary)], [zero vector], Z);\nand the vector Z is a (3 * N) flat vector of the solution vertices (equivalent to the “U” of the other example).\n\n??? Add remeshing.\nExpose a function to Godot Engine called triangulate boundaries.\n\n\n\n\n\nJeana demonstrated the feel of CASSIE on 2021-11-05 to draw a cat.\n\n\n\n\n20211105 CASSIE Jeana\n\n\n\n\n\n\nAdding complexity and maybe time space explosions because of mesh processing.\nMay cause stuttering in VR.\n\n\n\n\n\nOption: Integrate drawing like OpenBrush. https://github.com/icosa-gallery/open-brush\nRejection Reason: The feel is not the same.\n\n\n\n\nNot a trivial gdscript and has performance gaps.\n\n\n\nIt is cool and I know how to approach implementing CASSIE in Godot Engine.\n\n\n\n\nhttps://www.cse.wustl.edu/~taoju/zoum/projects/TriMultPoly\nhttps://em-yu.github.io/\nhttps://ns.inria.fr/d3/CASSIE\nhttps://libigl.github.io/\nhttps://github.com/godotengine/\nhttps://www.blender.org/\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230619-membrane-framework-for-mesh-processing.html#negative-consequences",
-    "href": "decisions/20230619-membrane-framework-for-mesh-processing.html#negative-consequences",
-    "title": "Proposed: Networked Procedural Generation as a Sidecar to the Godot Engine Server",
+    "objectID": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html#context-and-problem-statement",
+    "href": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html#context-and-problem-statement",
+    "title": "Accepted: Take a list of 3D points that form a vaguely closed boundary in space and triangulate in Godot Engine",
     "section": "",
-    "text": "Increased complexity in implementation and maintenance\nPotential performance overhead due to integration of multiple components"
+    "text": "CASSIE is a method for Curve And Surface Sketching in Immersive Environments.\nA core part of the CASSIE algorithm is to take a list of 3D points that form a vaguely closed boundary in space and triangulate."
   },
   {
-    "objectID": "decisions/20230619-membrane-framework-for-mesh-processing.html#option-graveyard",
-    "href": "decisions/20230619-membrane-framework-for-mesh-processing.html#option-graveyard",
-    "title": "Proposed: Networked Procedural Generation as a Sidecar to the Godot Engine Server",
+    "objectID": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Accepted: Take a list of 3D points that form a vaguely closed boundary in space and triangulate in Godot Engine",
     "section": "",
-    "text": "Standalone procedural generation: Implementing procedural generation as a standalone feature without integrating it with the Godot Engine server. This option was discarded because it would not provide the same level of compatibility and versatility as the proposed solution.\nUsing pre-built assets: Relying on pre-built assets for creating environments instead of implementing networked procedural generation. This option was discarded due to the limited flexibility and potential for repetitive content, which could negatively impact user engagement.\nThird-party procedural generation tools: Integrating third-party procedural generation tools instead of developing a custom solution. This option was discarded because it may not offer the same level of control and customization required for V-Sekai’s specific needs.\nStatic environment design: Focusing on static environment design rather than dynamic, procedurally generated content. This option was discarded because it would not provide the desired level of immersion and interactivity for V-Sekai users."
+    "text": "This CASSIE triangulate operation needs to be done in Godot Engine so it can be use in V-Sekai."
   },
   {
-    "objectID": "decisions/20230619-membrane-framework-for-mesh-processing.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230619-membrane-framework-for-mesh-processing.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Networked Procedural Generation as a Sidecar to the Godot Engine Server",
+    "objectID": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Accepted: Take a list of 3D points that form a vaguely closed boundary in space and triangulate in Godot Engine",
     "section": "",
-    "text": "No, the proposed solution involves integrating multiple technologies and cannot be achieved with a simple script workaround."
+    "text": "Implement “An Algorithm for Triangulating Multiple 3D Polygons”\nUse Godot’s delaunay tetrahedralize https://github.com/godotengine/godot/blob/96d7bc62af25b85b8b9cc091eeea1e7a784ba624/core/math/delaunay_3d.h#L145 static Vector&lt;OutputSimplex&gt; tetrahedralize(const Vector&lt;Vector3&gt; &p_points)\nEmilie Yu described a method for smoothing meshes.\n\nLibigl should be best for smoothing while pinning the boundaries. I see they have a solver that can take fixed boundary constraints https://libigl.github.io/tutorial/#quadratic-energy-minimization so that could allow you to pin the boundaries. So instead of this line it would be something like\nigl::min_quad_with_fixed_data mqwf;\nigl::min_quad_with_fixed_precompute(S, [flat vector of indices of boundary vertices size=(3 * N_boundary)], [zero matrix], true, mqwf);\nigl::min_quad_with_fixed_solve(mqwf, M * U, [flat vector of boundary vertices positions size=(3 * N_boundary)], [zero vector], Z);\nand the vector Z is a (3 * N) flat vector of the solution vertices (equivalent to the “U” of the other example).\n\n??? Add remeshing.\nExpose a function to Godot Engine called triangulate boundaries."
   },
   {
-    "objectID": "decisions/20230619-membrane-framework-for-mesh-processing.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230619-membrane-framework-for-mesh-processing.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Networked Procedural Generation as a Sidecar to the Godot Engine Server",
+    "objectID": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html#positive-consequences",
+    "href": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html#positive-consequences",
+    "title": "Accepted: Take a list of 3D points that form a vaguely closed boundary in space and triangulate in Godot Engine",
     "section": "",
-    "text": "Yes, addressing the limitations of V-Sekai is crucial for its success and adoption within the VR community. By integrating the proposed technologies, we can ensure that V-Sekai remains competitive and relevant in the rapidly evolving VR landscape."
+    "text": "Jeana demonstrated the feel of CASSIE on 2021-11-05 to draw a cat.\n\n\n\n\n20211105 CASSIE Jeana"
   },
   {
-    "objectID": "decisions/20230619-membrane-framework-for-mesh-processing.html#references",
-    "href": "decisions/20230619-membrane-framework-for-mesh-processing.html#references",
-    "title": "Proposed: Networked Procedural Generation as a Sidecar to the Godot Engine Server",
+    "objectID": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html#negative-consequences",
+    "href": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html#negative-consequences",
+    "title": "Accepted: Take a list of 3D points that form a vaguely closed boundary in space and triangulate in Godot Engine",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Adding complexity and maybe time space explosions because of mesh processing.\nMay cause stuttering in VR."
   },
   {
-    "objectID": "decisions/20200602-manage-backend-with-k3s.html",
-    "href": "decisions/20200602-manage-backend-with-k3s.html",
-    "title": "Accepted: Manage backend resources on one or more physical machines with K3S",
+    "objectID": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html#option-graveyard",
+    "href": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html#option-graveyard",
+    "title": "Accepted: Take a list of 3D points that form a vaguely closed boundary in space and triangulate in Godot Engine",
     "section": "",
-    "text": "We want a way to manage backend resources on one or more physical machines.\n\n\n\nWe are using a lightweight Kubernetes implementation, k3s, to provide management of backend resources\n\n\n\n\n\nInstall Fedora 34 with a user account set as administrator.\nAdd authorized keys into ~/.ssh/authorized_keys\nOPTIONAL: customize SSH port: Set Port 2345 in /etc/ssh/sshd_config.\nsudo semanage port -a -t ssh_port_t -p tcp 2345\nsudo firewall-cmd --add-port=2345/tcp\nREQUIRED: set PasswordAuthentication no in /etc/ssh/sshd_config.\nOPTIONAL: Configure default DNS server:\n\n\n[main]\ndns=none\n[ipv4]\nmethod=auto\ndns=8.8.8.8;4.2.2.2;\nignore-auto-dns=true\n\n\n\nsearch localhost\nnameserver 1.0.0.1\nnameserver 1.1.1.1\n\n\n\nsudo service sshd restart\nsudo firewall-cmd --add-masquerade --permanent\nsudo systemctl restart firewalld\nsudo yum install redhat-lsb-core container-selinux selinux-policy-base podman\nsudo rpm -i https://github.com/rancher/k3s-selinux/releases/download/v0.1.1-rc1/k3s-selinux-0.1.1-rc1.el7.noarch.rpm\n# Validate that ssh logins work, then run:\nsudo service NetworkManager stop; sudo service NetworkManager start\nsudo grubby --update-kernel=ALL --args=\"systemd.unified_cgroup_hierarchy=0\"\nNow, reboot the system.\nFirst, create a new LVM Logical Volume named kubepvc XFS 100GB mounted at /kube. Add the following to /etc/fstab:\n\n\n\n# If created manually, run `sudo blkid` and add:\n# UUID=aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee /kube   auto  defaults   0 0\n/kube/rancher /var/lib/rancher    none bind 0 0`\n\n\n\nNow, setup the partition:\nsudo mkdir -p /kube\nsudo mount /kube\nsudo mkdir -p /kube/pvc /kube/rancher /var/lib/rancher /root/.kube\nsudo chcon -R -t container_file_t /kube/pvc\nsudo mount /var/lib/rancher\n\n\n\n\nIf your system uses SELinux, add the following SELinux module to allow dev-shm access. This will be necessary for python multiprocessing in containers, specifically usage of shm_lock, which is used by Emscripten.\n\n\nmodule dev-shm 1.0;\n\nrequire {\n        type container_runtime_tmpfs_t;\n        type container_t;\n        class dir { getattr relabelto unlink ioctl execute append read setattr write lock create rename link search rmdir remove_name reparent add_name open };\n        class file { map getattr relabelto unlink ioctl execute append read setattr write lock create rename relabelfrom link execute_no_trans entrypoint execmod open };\n        class shm { write destroy unix_write getattr create read setattr unix_read associate lock };\n        class sock_file { getattr relabelto unlink ioctl execute append read setattr write lock create rename relabelfrom link open };\n        class fifo_file { getattr relabelto unlink ioctl execute append read setattr write lock create rename relabelfrom link open };\n        class lnk_file { getattr relabelto unlink ioctl execute append read setattr write lock create rename relabelfrom link };\n}\n#============= container_t ==============\nallow container_t container_runtime_tmpfs_t:dir { getattr relabelto unlink ioctl execute append read setattr write lock create rename link search rmdir remove_name reparent add_name open };\n# domain_can_mmap_files\nallow container_t container_runtime_tmpfs_t:file { map getattr relabelto unlink ioctl execute append read setattr write lock create rename relabelfrom link execute_no_trans entrypoint execmod open };\nallow container_t container_runtime_tmpfs_t:shm { write destroy unix_write getattr create read setattr unix_read associate lock };\nallow container_t container_runtime_tmpfs_t:sock_file { getattr relabelto unlink ioctl execute append read setattr write lock create rename relabelfrom link open };\nallow container_t container_runtime_tmpfs_t:fifo_file { getattr relabelto unlink ioctl execute append read setattr write lock create rename relabelfrom link open };\nallow container_t container_runtime_tmpfs_t:lnk_file { getattr relabelto unlink ioctl execute append read setattr write lock create rename relabelfrom link };\nNow, install it with:\ncheckmodule -M -m dev-shm.te -o dev-shm.mod\nsemodule_package -m dev-shm.mod -o dev-shm.pp\nsudo semodule -i dev-shm.pp\n\n\n\n\ncurl -sfL https://raw.githubusercontent.com/rancher/k3s/master/install.sh | sh -s - server -o /root/.kube/config --default-local-storage-path /kube/pvc --disable=traefik --disable=servicelb --disable=flannel --disable=cni '--kubelet-arg=eviction-soft=memory.available&lt;0%,imagefs.available&lt;0%,nodefs.available&lt;0%' '--kubelet-arg=eviction-hard=memory.available&lt;0%,imagefs.available&lt;0%,nodefs.available&lt;0%'\nNow you will need to obtain the DNS IAM credentials. In this example, we are working with these Route53 hosted domains: vsekai.org,vsekai.net,vsekai.com,vsekai.cloud,v-sekai.org,v-sekai.net,v-sekai.com,v-sekai.cloud,vsek.ai,v-sek.ai\nInstall Helm services:\nACCESSKEY=AKIAABCDEFGHIJKLMNOP\nSECRETKEY=XXXXXXXXXXXXXXXXXXXX\n\nsudo helm repo add gocd https://gocd.github.io/helm-chart\nsudo helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx\nsudo helm repo add bitnami https://charts.bitnami.com/bitnami\nsudo helm repo add jetstack https://charts.jetstack.io\nsudo helm repo update\n\n# We are still using 3.2.3 - I have not figured out the upgrade process yet for external-dns\n\nsudo helm install external-dns --set provider=aws --set aws.zoneType=public --set registry=noop --set aws.credentials.accessKey=\"$ACCESSKEY\" --set domainFilters='{vsekai.org,vsekai.net,vsekai.com,vsekai.cloud,v-sekai.org,v-sekai.net,v-sekai.com,v-sekai.cloud,vsek.ai,v-sek.ai}' --set aws.credentials.secretKey=\"$SECRETKEY\"  bitnami/external-dns\n\n\n# NOTE: Some of these commands may be outdated:\n# They seem to refer to nginx-nginx-ingress but now it is nginx-ingress-nginx.\n# Take the following with a grain of salt:\n\nsudo kubectl create namespace ingress-nginx\nsudo helm install --namespace ingress-nginx nginx ingress-nginx/ingress-nginx --set controller.replicaCount=2\nsudo kubectl patch svc/nginx-nginx-ingress-controller -n kube-system --patch '{\"spec\":{\"externalTrafficPolicy\":\"Local\"}}'\nsudo kubectl patch deployments/nginx-nginx-ingress-controller --patch '{\"spec\":{\"template\":{\"spec\":{\"hostNetwork\":true}}}}' -n kube-system\n\nsudo kubectl get replicasets -n kube-system\n# Find the oldest nginx-nginx-ingress-controller one and delete with\nsudo kubectl delete replicasets -nginx-ingress-controller-abcdefg-whatever -n kube-system\n\n\n# Some weird stuff we changed. I don't think any of it is needed other than the above\n# externalTrafficPolicy and hostNetwork configuration changes.\n\ncat &gt; ingress-svc-edit.yaml\napiVersion: v1\nkind: Service\nmetadata:\n  annotations:\n    meta.helm.sh/release-name: nginx\n    meta.helm.sh/release-namespace: ingress-nginx\n    metallb.universe.tf/address-pool: default\n  creationTimestamp: \"2021-04-30T02:33:02Z\"\n  finalizers:\n  - service.kubernetes.io/load-balancer-cleanup\n  labels:\n    app.kubernetes.io/component: controller\n    app.kubernetes.io/instance: nginx\n    app.kubernetes.io/managed-by: Helm\n    app.kubernetes.io/name: ingress-nginx\n    app.kubernetes.io/version: 0.45.0\n    helm.sh/chart: ingress-nginx-3.29.0\n  name: nginx-ingress-nginx-controller\n  namespace: ingress-nginx\nspec:\n  clusterIP: 10.43.219.102\n  clusterIPs:\n  - 10.43.219.102\n  externalTrafficPolicy: Local\n  healthCheckNodePort: 32689\n  ipFamilies:\n  - IPv4\n  ipFamilyPolicy: SingleStack\n  ports:\n  - name: http\n    nodePort: 32595\n    port: 80\n    protocol: TCP\n    targetPort: http\n  - name: https\n    nodePort: 31937\n    port: 443\n    protocol: TCP\n    targetPort: https\n  selector:\n    app.kubernetes.io/component: controller\n    app.kubernetes.io/instance: nginx\n    app.kubernetes.io/name: ingress-nginx\n  sessionAffinity: None\n  type: LoadBalancer\nstatus:\n  loadBalancer:\n    ingress:\n    - ip: 999.999.999.999\n\nCtrl-D to save\n\nsudo kubectl apply -f ingress-svc-edit.yaml\n\nsudo kubectl patch -n ingress-nginx services/nginx-ingress-nginx-controller --patch '{\"metadata\":{\"annotations\":{\"metallb.universe.tf/address-pool\":\"default\"}},\"spec\":{\"externalTrafficPolicy\":\"Local\"}}\nsudo kubectl patch deployments/nginx-ingress-nginx-controller --patch '{\"spec\":{\"template\":{\"spec\":{\"hostNetwork\":true}}}}' -n ingress-nginx\n\n\n\n\n\nsudo kubectl create namespace cert-manager\n# Used --version v0.15.1 before; now v1.3.1\nsudo helm install cert-manager jetstack/cert-manager --namespace cert-manager --version v1.3.1 --set installCRDs=true\nsudo kubectl --namespace cert-manager create secret generic prod-route53-credentials-secret --from-literal=secret-access-key=\"$SECRETKEY\"\n\n\napiVersion: cert-manager.io/v1alpha2\nkind: ClusterIssuer\nmetadata:\n  name: letsencrypt-prod\n  namespace: cert-manager\nspec:\n  acme:\n    # The ACME server URL\n    server: https://acme-v02.api.letsencrypt.org/directory\n    # Email address used for ACME registration\n    email: example@example.com\n    # Name of a secret used to store the ACME account private key\n    privateKeySecretRef:\n      name: letsencrypt-prod\n    # Enable the HTTP-01 challenge provider\n    solvers:\n      - http01:\n          ingress:\n            class: nginx\n    #solvers:\n    #- dns01:\n    #   route53:\n    #     region: us-east-1\n    #     accessKeyID: AKIAABCDEFGHIJKLMNOP\n    #     secretAccessKeySecretRef:\n    #       name: prod-route53-credentials-secret\n    #       key: secret-access-key\n---\napiVersion: extensions/v1beta1\nkind: Ingress\nmetadata:\n  name: core-ingress\n  annotations:\n    kubernetes.io/ingress.class: \"nginx\"\n    cert-manager.io/cluster-issuer: \"letsencrypt-prod\"\n    nginx.ingress.kubernetes.io/hsts: \"false\"\n    # nginx.ingress.kubernetes.io/add-base-url: \"true\"\n    nginx.ingress.kubernetes.io/ssl-redirect: \"true\"\n    nginx.ingress.kubernetes.io/configuration-snippet: |\n      if ($host ~ ^(?!(ci))) {\n        more_clear_headers \"Strict-Transport-Security\";\n      }\n      if ($host ~ ^(.*\\.?)vsekai\\.([a-z]*)$ ) {\n          set $subd $1;\n          set $tld $2;\n          set $newdomain v-sekai.$tld;\n          rewrite ^/(.*)$ https://$subd$newdomain/$1;\n      }\nspec:\n  tls:\n    - hosts:\n        - vsekai.cloud\n        - v-sekai.cloud\n        - uro.vsekai.cloud\n        - uro.v-sekai.cloud\n        - radiance.v-sekai.cloud\n        - ci.radiance.v-sekai.cloud\n        - ci.v-sekai.cloud\n        - radiance.vsekai.cloud\n        - ci.radiance.vsekai.cloud\n        - ci.vsekai.cloud\n        - hls.vsek.ai\n      secretName: radiance-cert-secret1\n  rules:\n    - host: vsekai.cloud\n    - host: v-sekai.cloud\n    - host: uro.vsekai.cloud\n    - host: uro.v-sekai.cloud\n      http:\n        paths:\n          - path: /\n            backend:\n              serviceName: uro\n              servicePort: 4000\n    - host: hls.vsek.ai\n      http:\n        paths:\n          - path: /\n            backend:\n              serviceName: nginx-rtmp-service\n              servicePort: 80\n    - host: radiance.vsekai.cloud\n    - host: radiance.v-sekai.cloud\n      http:\n        paths:\n          - path: /debug_headers\n            backend:\n              serviceName: echo-service\n              servicePort: 8099\n          - path: /\n            backend:\n              serviceName: echo1\n              servicePort: 80\n    - host: ci.vsekai.cloud\n    - host: ci.v-sekai.cloud\n      http:\n        paths:\n          - path: /\n            backend:\n              serviceName: gocd-server\n              servicePort: 8153\n    - host: ci.radiance.vsekai.cloud\n    - host: ci.radiance.v-sekai.cloud\n      http:\n        paths:\n          - path: /\n            backend:\n              serviceName: gocd-server\n              servicePort: 8153\nThen:\nsudo kubectl apply -f ingress.yaml\n\n\n\n\n\n\napiVersion: v1\nkind: ConfigMap\nmetadata:\n  namespace: metallb-system\n  name: config\ndata:\n  config: |\n    address-pools:\n    - name: default\n      protocol: layer2\n      addresses:\n      - 108.85.109.49/32 # &lt;--- this is the external. HOST IP\nsudo kubectl create namespace metallb-system\nsudo kubectl create secret generic -n metallb-system memberlist --from-literal=secretkey=\"$(openssl rand -base64 128)\"\nsudo kubectl apply -f metalconfig.yml\nsudo kubectl apply -f https://raw.githubusercontent.com/metallb/metallb/v0.9.3/manifests/metallb.yaml\n\n\n\n\n(Optional in theory, but you have to remove enabled platforms in gocd):\nStart by grabbing a legitimate copy of MacOSX10.15.sdk.tar.xz from your local MacBook or Mac Mini.\nThen do the following to build:\ncd /opt\nsudo chown `whoami` .\ngit clone https://github.com/tpoechtrager/osxcross.git /opt/osxcross\nsudo chown root .\ncd /opt/osxcross\nmv MacOSX10.15.sdk.tar.xz /opt/osxcross/tarballs\nUNATTENDED=1 ./build.sh\n\n# In case host OS is newer than guest OS:\ncp -p /lib64/libstdc++.so.6 /opt/osxcross/target/bin/\nOn SELinux systems, you may need to give containers read permissions:\nsudo chcon -R unconfined_u:object_r:container_share_t:s0  /opt/osxcross\n\n\n\n\n\nagent:\n  image:\n    # agent.image.repository is the GoCD Agent image name\n    repository: \"groupsinfra/gocd-agent-centos-8-groups\" # agent.image.tag is the GoCD Agent image's tag\n    tag: v20.7.0-groups-0.5.3\n    # agent.image.pullPolicy is the GoCD Agent image's pull policy\n\n    pullPolicy: \"IfNotPresent\" # agent.replicaCount is the GoCD Agent replicas Count. Specify the number of GoCD agents to run\n  replicaCount: 6\n  security:\n    ssh:\n      enabled: true\n      secretName: gocd-ssh\nserver:\n  shouldPreconfigure: false\n  security:\n    ssh:\n      enabled: true\n      secretName: gocd-ssh\n  env:\n    extraEnvVars:\n      - name: GOCD_PLUGIN_INSTALL_gitlab-oauth-authorization-plugin\n        value: https://github.com/gocd-contrib/gitlab-oauth-authorization-plugin/releases/download/v2.0.1-52-exp/gitlab-oauth-authorization-plugin-2.0.1-52.jar\n\n\nssh-keygen -t rsa -b 4096 -C \"gocd-ssh-key\" -f gocd-ssh -P ''\n( ssh-keyscan gitlab.com ; ssh-keyscan github.com ) &gt; gocd_known_hosts\nsudo kubectl create secret generic gocd-ssh --from-file=id_rsa=gocd-ssh --from-file=id_rsa.pub=gocd-ssh.pub --from-file=known_hosts=gocd_known_hosts\n\n# Chart version 1.37.0 is gocd v21.2.0\nsudo helm install -f gocd_values.yaml gocd gocd/gocd --version 1.37.0\nsudo chcon -R -t container_file_t /kube/pvc\n# Installs a trash service on port 80 by default. Let's delete it:\nsudo kubectl delete ingress gocd-server\n# Instead of using \"kubectl scale\", scale agents by editing gocd_values.yaml\n# and do \"sudo helm upgrade -f ....\"\nsudo helm install -f gocd_values.yaml gocd gocd/gocd --version 1.37.0\n# Make sure to enable the agents in the web UI, and assign them to Resources and Environments.\n\n\n\n\n# Disable and Delete all agents in the AGENTS tab of gocd.\nEdit gocd_values.yaml and set agent version to latest (e.g. v21.2.0-groups-0.5.8)\nsudo helm upgrade -f gocd_values.yaml gocd gocd/gocd --version 1.37.0\nsudo kubectl delete ingress gocd-server\n# Upgrade gocd-agent-dind:\nsudo kubectl patch deployments/gocd-agent-dind --patch '{\"spec\":{\"template\":{\"spec\":{\"containers\":[{\"name\":\"gocd-agent-dind\",\"image\":\"gocd/gocd-agent-docker-dind:v21.2.0\"}]}}}}'\n# You can also use patch to upgrade gocd-agent and gocd-server instead of upgrading via helm chart. I sometimes do it that way.\n# Delete the old Agents on the web interface. Wait for the new agents to come up, and enable them and assign them as appropriate.\n\n\n\nCreate DockerHub permissions: Create an account if you do not have one. Visit https://hub.docker.com/settings/security and create an Access Token. Copy the token.\nsudo  kubectl create secret docker-registry regcred --docker-server=https://index.docker.io/v1/ --docker-username=dockerhubuser --docker-password=XXXX --docker-email=your.dockerhub.email@example.com\n\n\n\nFor osxcross (OSX cross compiling), make sure the OSX compiler SDK you created on mac os located at /opt/osxcross.\nIf you do not have osxcross (no access to Apple hardware), then you must create an empty directory at /opt/osxcross or remove the relevant volume mounts (and remove from enabled build targets in the gocd pipelines).\nNow create Docker-in-Docker, and apply this file with kubectl create -f dind.yaml or kubectl apply -f dind.yaml\n\n\n\napiVersion: apps/v1\nkind: Deployment\nmetadata:\n  labels:\n    app: gocd\n    component: agent-dind\n  name: gocd-agent-dind\n  namespace: default\nspec:\n  progressDeadlineSeconds: 600\n  replicas: 2\n  revisionHistoryLimit: 10\n  selector:\n    matchLabels:\n      app: gocd\n      component: agent-dind\n      release: gocd\n  strategy:\n    rollingUpdate:\n      maxSurge: 25%\n      maxUnavailable: 25%\n    type: RollingUpdate\n  template:\n    metadata:\n      creationTimestamp: null\n      labels:\n        app: gocd\n        component: agent-dind\n        release: gocd\n    spec:\n      containers:\n        - env:\n            - name: GO_SERVER_URL\n              value: http://gocd-server:8153/go\n          image: gocd/gocd-agent-docker-dind:v21.2.0\n          imagePullPolicy: IfNotPresent\n          name: gocd-agent-dind\n          resources: {}\n          securityContext:\n            privileged: true\n          terminationMessagePath: /dev/termination-log\n          terminationMessagePolicy: File\n          volumeMounts:\n            - mountPath: /root/.ssh\n              name: ssh-secrets\n              readOnly: true\n            - mountPath: /root/.docker\n              name: kaniko-secret\n            - mountPath: /opt/osxcross\n              name: opt-osxcross-volume\n              readOnly: true\n      dnsPolicy: ClusterFirst\n      restartPolicy: Always\n      schedulerName: default-scheduler\n      securityContext:\n        fsGroup: 0\n        runAsGroup: 0\n        runAsUser: 0\n      serviceAccount: default\n      serviceAccountName: default\n      terminationGracePeriodSeconds: 30\n      volumes:\n        - name: ssh-secrets\n          secret:\n            defaultMode: 256\n            secretName: gocd-ssh\n        - name: kaniko-secret\n          secret:\n            secretName: regcred\n            items:\n              - key: .dockerconfigjson\n                path: config.json\n        - name: opt-osxcross-volume\n          hostPath:\n            path: /opt/osxcross\n            type: Directory\n\n\n\n\nTo add osxcross support to the main agents, create the following patch:\ngocd-agent-patch.yaml\napiVersion: apps/v1\nkind: Deployment\nmetadata:\n  name: gocd-agent\nspec:\n  template:\n    spec:\n      containers:\n        - name: gocd-agent\n          volumeMounts:\n            - mountPath: /opt/osxcross\n              name: opt-osxcross-volume\n              readOnly: true\n      volumes:\n        - name: opt-osxcross-volume\n          hostPath:\n            path: /opt/osxcross\n            type: Directory\nand apply with:\nsudo kubectl patch deployments/gocd-agent -p \"$(cat gocd-agent-patch.yaml)\"\nMake sure to enable the Agents when they come up on the GoCD Dashboard. Add every server to the “development” environment. Also, assign linux servers to “mingw” and “linux”. Assign the dind agents to “dind”.\nFor GitLab, go to https://ci.v-sekai.cloud/go/admin/security/auth_configs and select Create new authorization configuration -&gt; gitlab-auth-config / GitLab Authentication plugin / follow documentation here: https://github.com/gocd-contrib/gitlab-oauth-authorization-plugin/blob/master/INSTALL.md - Do not check Allow only known users to login yet. If this works, you can skip the text auth step and corresponding passwd commands.\nCreate Guest login:\n\nGo to auth_configs, Create new authorization configuration -&gt; guest-login / Guest Login Plugin / Fill out Go server URL / Username view / Display name Guest.\nNow, go to Roles Management. Create role guest. Add Deny for all types and Resources * as desired.\nIn an Incognito window, visit the CI system and login as Guest. Close the incognito window.\nNow, go to Users Management. Select view / Guest and select Roles -&gt; guest\nAdmin -&gt; Pipelines. Select Pipeline Group beta, click + on the top right of the whole group, go to Roles, add guest, and only check View. Save this.\n\nAt this point, Guest should have permission to view pipelines, see logs, download artifacts but nothing else.\nFor text auth, go to https://ci.v-sekai.cloud/go/admin/security/auth_configs and select Create new authorization configuration -&gt; file-auth-config / Password File Authentication plugin / /godata/config/password.properties\nsudo kubectl exec gocd-server-6d77846995-5l244 -- touch /godata/config/password.properties\nsudo yum install httpd-tools\nhtpasswd -c -B passwd admin\ncat passwd | sudo kubectl exec gocd-server-6d77846995-5l244 -- sudo tee /kubepvc/pvc/*/godata/config/password.properties\nNow go to users page, edit your user and enable Global Admin.\nNow go to file-auth-config, edit configuration, enable Allow only known users to login\n\n\n\nGo to Admin -&gt; Config Repositories\n\nConfig #repository Name: groups-gocd-pipelines\nPlugin ID: JSON Configuration Plugin\nMaterial Type: Git\nURL: git@gitlab.com:godot-groups/groups-gocd-pipelines\nBranch: master\nGoCD pipeline files pattern: *.gopipeline.json\nGoCD environment files pattern: *.goenvironment.json\n\nRules\n\nAllow: Pipeline Group: beta\nAllow: Environment: development\n\n\n\n\ncurl -L https://github.com/fluxcd/flux2/releases/download/v0.24.1/flux_0.24.1_linux_amd64.tar.gz | tar -zxf - flux\nsudo cp flux /usr/local/bin/flux\nsudo chmod +x /usr/local/bin/flux\nsudo kubectl apply -f https://github.com/fluxcd/flux2/releases/download/v0.24.1/install.yaml\nFork the flux-config #repository from here https://github.com/V-Sekai/flux-config into your own github account, and set GHUSER=your github account.\nNow, in your fork of flux-config, go to project Settings -&gt; Deploy Keys and add the result of the above identity command. Make sure to check Allow write access.\nOnce you have done this, you can continue with the flux setup using your newly forked repository.\nexport GHUSER=\"xxxxxxxxx\"\nsudo flux install\nsudo flux create source git gitrepo --url=https://github.com/$GHUSER/flux-config  --branch=flux2\nsudo flux create kustomization workloads --source=GitRepository/gitrepo --path=\"./workloads/\"\nsudo flux get all\nFOR DEBUGGING ONLY: sudo setenforce permissive - this appears to have no effect, so there is a different problem.\n\n\n\n\n\nstatefulset:\n  resources:\n    limits:\n      memory: \"8Gi\"\n    requests:\n      memory: \"8Gi\"\nconf:\n  cache: \"2Gi\"\n  max-sql-memory: \"2Gi\"\ntls:\n  enabled: true\n\n\n\n\n# Helm version MAY be deprecated. We will switch to operator below.\n\n#sudo helm install cockroachdb --values cockroachdb.values.yaml cockroachdb/cockroachdb\n#sudo kubectl certificate approve default.node.cockroachdb-0\n#sudo kubectl certificate approve default.node.cockroachdb-1\n#sudo kubectl certificate approve default.node.cockroachdb-2\n#sudo kubectl certificate approve default.client.root\n\nwget https://raw.githubusercontent.com/cockroachdb/cockroach-operator/master/manifests/operator.yaml -O cockroach-operator.yaml\nsudo kubectl apply -f cockroach-operator.yaml\n\nwget https://raw.githubusercontent.com/cockroachdb/cockroach-operator/master/config/crd/bases/crdb.cockroachlabs.com_crdbclusters.yaml\nsudo kubectl apply -f crdb.yaml\n\ncat &gt; cockroachdb_extra_resource_certgen.yaml\napiVersion: v1\nkind: ServiceAccount\nmetadata:\n  name: cockroachdb\n  labels:\n    app: cockroachdb\n---\napiVersion: rbac.authorization.k8s.io/v1\nkind: Role\nmetadata:\n  name: cockroachdb\n  labels:\n    app: cockroachdb\nrules:\n- apiGroups:\n  - \"\"\n  resources:\n  - secrets\n  verbs:\n  - create\n  - get\n---\napiVersion: rbac.authorization.k8s.io/v1\nkind: ClusterRole\nmetadata:\n  name: cockroachdb\n  labels:\n    app: cockroachdb\nrules:\n- apiGroups:\n  - certificates.k8s.io\n  resources:\n  - certificatesigningrequests\n  verbs:\n  - create\n  - get\n  - watch\n---\napiVersion: rbac.authorization.k8s.io/v1\nkind: RoleBinding\nmetadata:\n  name: cockroachdb\n  labels:\n    app: cockroachdb\nroleRef:\n  apiGroup: rbac.authorization.k8s.io\n  kind: Role\n  name: cockroachdb\nsubjects:\n- kind: ServiceAccount\n  name: cockroachdb\n  namespace: default\n---\napiVersion: rbac.authorization.k8s.io/v1\nkind: ClusterRoleBinding\nmetadata:\n  name: cockroachdb\n  labels:\n    app: cockroachdb\nroleRef:\n  apiGroup: rbac.authorization.k8s.io\n  kind: ClusterRole\n  name: cockroachdb\nsubjects:\n- kind: ServiceAccount\n  name: cockroachdb\n  namespace: default\n\nCtrl-D\n\n\n# Note: may need to set up physicalVolume and physicalVolumeClaim objects for each cockraoch node.\n\n# The permissions may be set wrong if you are upgrading. Fix them with:\nsudo chown -R 1000581000 /kube/pvc/pvc-aaaaaaaaaaaaaaaaaa /kube/pvc/pvc-bbbbbbbbbbbbbbb /kube/pvc/pvc-cccccccccccccccccccccccccccccccc\n\n# OLD curl -o client-secure.yaml https://raw.githubusercontent.com/cockroachdb/cockroach/master/cloud/kubernetes/client-secure.yaml\n# OLD sudo kubectl apply -f client-secure.yaml\n\nwget https://raw.githubusercontent.com/cockroachdb/cockroach-operator/master/examples/client-secure-operator.yaml\nsudo kubectl apply -f client-secure-operator.yaml\n\nsudo kubectl certificate approve default.client.uro-prod\n\nsudo kubectl exec -it cockroachdb-client-secure -- ./cockroach sql --certs-dir=/cockroach-certs --host=cockroachdb-public\nIn SQL, write:\nCREATE DATABASE uro_prod;\nCREATE USER 'uro-prod' WITH PASSWORD 'blablablablaSOMEDATABASEPASSWORD';\nGRANT ALL ON DATABASE uro_prod to \"uro-prod\";\nTo make backups:\nsudo kubectl exec -it cockroachdb-client-secure -- ./cockroach dump --certs-dir=/cockroach-certs --host=cockroachdb-public uro_prod &gt; uro_prod_backup.txt\nApply secrets:\n(On dev machine) MIX_ENV=prod mix phx.gen.secret\n# Copy the output of above, and copy the database password from above:\nsudo kubectl create secret generic uro-prod --from-literal=secret-key-base='GENERATED_WITH_ABOVE_COMMAND' --from-literal=pass='blablablablaSOMEDATABASEPASSWORD'\n\nsudo kubectl apply -f https://raw.githubusercontent.com/V-Sekai/uro/master/kubernetes.yaml\n\n\n\n\n\n\nk3s set the default client cert for root to expire after a year or so. This leads to a problem where you can’t administer your own cluster because your root account’s cert is expired. So I had to figure out how to fix this.\nFor the most part, the process I came up with matches this more concise post here: https://github.com/k3s-io/k3s/issues/2342#issuecomment-713016341\nFirst approach, how to rotate kube client certificates: Because we need to modify /root/.kube/config, I ran sudo -i to login as a root shell.\n\nmkdir tls and create tls/config.txt with the following lines:\n\n# --------------------- tls/config.txt -----------\n[ req ]\ndistinguished_name                           = req_distinguished_name\nreq_extensions                                   = v3_req\nprompt = no\n[ req_distinguished_name ]\norganizationName       = system:masters\ncommonName             = system:admin\n[ v3_req ]\nbasicConstraints                                 = CA:FALSE\nkeyUsage                                           = critical, digitalSignature, keyEncipherment\nextendedKeyUsage                            = clientAuth\n# -------------------------------------------------\n\ncp /kube/rancher/k3s/server/tls/client-ca.crt tls/client-ca.crt\nopenssl ecparam -name prime256v1 -genkey -noout -out tls/new-key.pem\nopenssl req -new -key tls/new-key.pem -sha256 -nodes -out tls/new-req.csr -config tls/config.txt\nopenssl x509 -req -days 3000 -in tls/new-req.csr -CA tls/client-ca.crt -CAkey /kube/rancher/k3s/server/tls/client-ca.key -set_serial 4294742997922865905 -extensions v3_req -extfile tls/config.txt -out tls/new-client.crt\ncat tls/new-client.crt tls/client-ca.crt | base64 -w0; echo\ncat tls/new-key.pem | base64 -w0; echo\nedit .kube/config and update client-certificate-data: and client-key-data: respectively.\n\nHow to upgrade the rest of the certs.\nfind /var/lib/rancher/k3s/server/tls -name '*.crt' | while read fn; do echo $fn ===========; openssl x509 -text -in $fn | grep Not\\ After | grep '202[012]'; done\nHere is the script I ran:\n#!/bin/bash\nset -\nset -x\n[ -e \"$1.csr\" ] || openssl x509 -x509toreq -in \"$1.crt\" -out \"$1.csr\" -signkey \"$1.key\"\nmv -i \"$1.crt\" \"$1.crt.bak.$(date +%s)\"\nopenssl x509 -req -in \"$1.csr\" -CA \"client-ca.crt\" -CAkey \"client-ca.key\" -CAcreateserial -days 3650 -out \"$1.crt\"\ncat \"client-ca.crt\" &gt;&gt; \"$1.crt\"\nyou can use this process to update the client cert for /root/.kube/config\nNote that etcd/client.crt actually uses its own server-ca.key instead of client-ca within the etcd folder, so you need a slight modification of the script for this one. I don’t know what any of these certs do so I just did all of them\nFinally, client-k3s-controller.crt and client-kube-proxy.crt must be copied from /var/lib/rancher/k3s/server/tls to /var/lib/rancher/k3s/agent\n\n\n\nStart the upgrade process with:\nsudo dnf upgrade --refresh\nsudo dnf install dnf-plugin-system-upgrade\nsudo dnf system-upgrade download --releasever=34\nAnswer y to all prompts confirming list of packages and new GPG keys, if any. Once successful, it displays:\nDownload complete! Use 'dnf system-upgrade reboot' to start the upgrade.\nTo remove cached metadata and transaction use 'dnf system-upgrade clean'\nThe downloaded packages were saved in cache until the next successful transaction.\nYou can remove cached packages by executing 'dnf clean packages'.\nComplete the upgrade with:\nsudo dnf system-upgrade reboot\nThis will bring the system down for about an hour.\n\n\n\nsudo helm repo update\n# If the stable/nginx-ingress chart is still installed, make sure to helm uninstall nginx first.\nsudo helm upgrade --namespace ingress-nginx nginx ingress-nginx/ingress-nginx --set controller.replicaCount=2\nsudo helm upgrade cert-manager jetstack/cert-manager --namespace cert-manager --set installCRDs=true\n### I was not able to get external-dns to upgrade, but it is not user-facing so we keep running the old version.\n# sudo helm upgrade external-dns --reuse-values bitnami/external-dns\n\n\n\ncurl -sfL https://raw.githubusercontent.com/rancher/k3s/master/install.sh | sh -s - server -o /root/.kube/config --default-local-storage-path /kube/pvc --no-deploy=servicelb --disable=traefik --disable=servicelb\n\n\n\nRun the shell:\nsudo kubectl exec -it cockroachdb-client-secure -- ./cockroach sql --certs-dir=/cockroach-certs --host=cockroachdb-public\nAt the top of the shell prompt, it will say something like this. Copy the first two numbers from the CockroachDB CCL line. In this case, 20.2\n#\n# Welcome to the CockroachDB SQL shell.\n# All statements must be terminated by a semicolon.\n# To exit, type: \\q.\n#\n# Server version: CockroachDB CCL v20.2.2 (x86_64-unknown-linux-gnu\nReplace some.version in the following command with the value we found above:\nSET CLUSTER SETTING cluster.preserve_downgrade_option = 'some.version';\nFinally, perform the upgrade:\nsudo kubectl delete job cockroachdb-init\nsudo helm upgrade cockroachdb cockroachdb/cockroachdb --values cockroachdb.values.yaml\ncurl -o client-secure.yaml https://raw.githubusercontent.com/cockroachdb/cockroach/master/cloud/kubernetes/client-secure.yaml\nsudo kubectl delete pods/cockroachdb-client-secure\nsudo kubectl create -f client-secure.yaml\n\n\n\n\n\n\nKnowledge gains about service creation\nOperation experience\n\n\n\n\n\nConstant maintenance\n\n\n\n\n\nOption: Dedicated Servers\nOption: Virtual Machines\n\n\n\n\nYes, it is possible to deploy this system using docker or in the root system.\n\n\n\nHaving experience with kubernetes and maintaining discipline will make scaling or service upgrades smoother in the future.\n\n\n\n\nhttps://k3s.io/\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Option: Integrate drawing like OpenBrush. https://github.com/icosa-gallery/open-brush\nRejection Reason: The feel is not the same."
   },
   {
-    "objectID": "decisions/20200602-manage-backend-with-k3s.html#context-and-problem-statement",
-    "href": "decisions/20200602-manage-backend-with-k3s.html#context-and-problem-statement",
-    "title": "Accepted: Manage backend resources on one or more physical machines with K3S",
+    "objectID": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Accepted: Take a list of 3D points that form a vaguely closed boundary in space and triangulate in Godot Engine",
     "section": "",
-    "text": "We want a way to manage backend resources on one or more physical machines."
+    "text": "Not a trivial gdscript and has performance gaps."
   },
   {
-    "objectID": "decisions/20200602-manage-backend-with-k3s.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20200602-manage-backend-with-k3s.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Accepted: Manage backend resources on one or more physical machines with K3S",
+    "objectID": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Accepted: Take a list of 3D points that form a vaguely closed boundary in space and triangulate in Godot Engine",
     "section": "",
-    "text": "We are using a lightweight Kubernetes implementation, k3s, to provide management of backend resources"
+    "text": "It is cool and I know how to approach implementing CASSIE in Godot Engine."
   },
   {
-    "objectID": "decisions/20200602-manage-backend-with-k3s.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20200602-manage-backend-with-k3s.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Accepted: Manage backend resources on one or more physical machines with K3S",
+    "objectID": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html#references",
+    "href": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html#references",
+    "title": "Accepted: Take a list of 3D points that form a vaguely closed boundary in space and triangulate in Godot Engine",
     "section": "",
-    "text": "Install Fedora 34 with a user account set as administrator.\nAdd authorized keys into ~/.ssh/authorized_keys\nOPTIONAL: customize SSH port: Set Port 2345 in /etc/ssh/sshd_config.\nsudo semanage port -a -t ssh_port_t -p tcp 2345\nsudo firewall-cmd --add-port=2345/tcp\nREQUIRED: set PasswordAuthentication no in /etc/ssh/sshd_config.\nOPTIONAL: Configure default DNS server:\n\n\n[main]\ndns=none\n[ipv4]\nmethod=auto\ndns=8.8.8.8;4.2.2.2;\nignore-auto-dns=true\n\n\n\nsearch localhost\nnameserver 1.0.0.1\nnameserver 1.1.1.1\n\n\n\nsudo service sshd restart\nsudo firewall-cmd --add-masquerade --permanent\nsudo systemctl restart firewalld\nsudo yum install redhat-lsb-core container-selinux selinux-policy-base podman\nsudo rpm -i https://github.com/rancher/k3s-selinux/releases/download/v0.1.1-rc1/k3s-selinux-0.1.1-rc1.el7.noarch.rpm\n# Validate that ssh logins work, then run:\nsudo service NetworkManager stop; sudo service NetworkManager start\nsudo grubby --update-kernel=ALL --args=\"systemd.unified_cgroup_hierarchy=0\"\nNow, reboot the system.\nFirst, create a new LVM Logical Volume named kubepvc XFS 100GB mounted at /kube. Add the following to /etc/fstab:\n\n\n\n# If created manually, run `sudo blkid` and add:\n# UUID=aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee /kube   auto  defaults   0 0\n/kube/rancher /var/lib/rancher    none bind 0 0`\n\n\n\nNow, setup the partition:\nsudo mkdir -p /kube\nsudo mount /kube\nsudo mkdir -p /kube/pvc /kube/rancher /var/lib/rancher /root/.kube\nsudo chcon -R -t container_file_t /kube/pvc\nsudo mount /var/lib/rancher\n\n\n\n\nIf your system uses SELinux, add the following SELinux module to allow dev-shm access. This will be necessary for python multiprocessing in containers, specifically usage of shm_lock, which is used by Emscripten.\n\n\nmodule dev-shm 1.0;\n\nrequire {\n        type container_runtime_tmpfs_t;\n        type container_t;\n        class dir { getattr relabelto unlink ioctl execute append read setattr write lock create rename link search rmdir remove_name reparent add_name open };\n        class file { map getattr relabelto unlink ioctl execute append read setattr write lock create rename relabelfrom link execute_no_trans entrypoint execmod open };\n        class shm { write destroy unix_write getattr create read setattr unix_read associate lock };\n        class sock_file { getattr relabelto unlink ioctl execute append read setattr write lock create rename relabelfrom link open };\n        class fifo_file { getattr relabelto unlink ioctl execute append read setattr write lock create rename relabelfrom link open };\n        class lnk_file { getattr relabelto unlink ioctl execute append read setattr write lock create rename relabelfrom link };\n}\n#============= container_t ==============\nallow container_t container_runtime_tmpfs_t:dir { getattr relabelto unlink ioctl execute append read setattr write lock create rename link search rmdir remove_name reparent add_name open };\n# domain_can_mmap_files\nallow container_t container_runtime_tmpfs_t:file { map getattr relabelto unlink ioctl execute append read setattr write lock create rename relabelfrom link execute_no_trans entrypoint execmod open };\nallow container_t container_runtime_tmpfs_t:shm { write destroy unix_write getattr create read setattr unix_read associate lock };\nallow container_t container_runtime_tmpfs_t:sock_file { getattr relabelto unlink ioctl execute append read setattr write lock create rename relabelfrom link open };\nallow container_t container_runtime_tmpfs_t:fifo_file { getattr relabelto unlink ioctl execute append read setattr write lock create rename relabelfrom link open };\nallow container_t container_runtime_tmpfs_t:lnk_file { getattr relabelto unlink ioctl execute append read setattr write lock create rename relabelfrom link };\nNow, install it with:\ncheckmodule -M -m dev-shm.te -o dev-shm.mod\nsemodule_package -m dev-shm.mod -o dev-shm.pp\nsudo semodule -i dev-shm.pp\n\n\n\n\ncurl -sfL https://raw.githubusercontent.com/rancher/k3s/master/install.sh | sh -s - server -o /root/.kube/config --default-local-storage-path /kube/pvc --disable=traefik --disable=servicelb --disable=flannel --disable=cni '--kubelet-arg=eviction-soft=memory.available&lt;0%,imagefs.available&lt;0%,nodefs.available&lt;0%' '--kubelet-arg=eviction-hard=memory.available&lt;0%,imagefs.available&lt;0%,nodefs.available&lt;0%'\nNow you will need to obtain the DNS IAM credentials. In this example, we are working with these Route53 hosted domains: vsekai.org,vsekai.net,vsekai.com,vsekai.cloud,v-sekai.org,v-sekai.net,v-sekai.com,v-sekai.cloud,vsek.ai,v-sek.ai\nInstall Helm services:\nACCESSKEY=AKIAABCDEFGHIJKLMNOP\nSECRETKEY=XXXXXXXXXXXXXXXXXXXX\n\nsudo helm repo add gocd https://gocd.github.io/helm-chart\nsudo helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx\nsudo helm repo add bitnami https://charts.bitnami.com/bitnami\nsudo helm repo add jetstack https://charts.jetstack.io\nsudo helm repo update\n\n# We are still using 3.2.3 - I have not figured out the upgrade process yet for external-dns\n\nsudo helm install external-dns --set provider=aws --set aws.zoneType=public --set registry=noop --set aws.credentials.accessKey=\"$ACCESSKEY\" --set domainFilters='{vsekai.org,vsekai.net,vsekai.com,vsekai.cloud,v-sekai.org,v-sekai.net,v-sekai.com,v-sekai.cloud,vsek.ai,v-sek.ai}' --set aws.credentials.secretKey=\"$SECRETKEY\"  bitnami/external-dns\n\n\n# NOTE: Some of these commands may be outdated:\n# They seem to refer to nginx-nginx-ingress but now it is nginx-ingress-nginx.\n# Take the following with a grain of salt:\n\nsudo kubectl create namespace ingress-nginx\nsudo helm install --namespace ingress-nginx nginx ingress-nginx/ingress-nginx --set controller.replicaCount=2\nsudo kubectl patch svc/nginx-nginx-ingress-controller -n kube-system --patch '{\"spec\":{\"externalTrafficPolicy\":\"Local\"}}'\nsudo kubectl patch deployments/nginx-nginx-ingress-controller --patch '{\"spec\":{\"template\":{\"spec\":{\"hostNetwork\":true}}}}' -n kube-system\n\nsudo kubectl get replicasets -n kube-system\n# Find the oldest nginx-nginx-ingress-controller one and delete with\nsudo kubectl delete replicasets -nginx-ingress-controller-abcdefg-whatever -n kube-system\n\n\n# Some weird stuff we changed. I don't think any of it is needed other than the above\n# externalTrafficPolicy and hostNetwork configuration changes.\n\ncat &gt; ingress-svc-edit.yaml\napiVersion: v1\nkind: Service\nmetadata:\n  annotations:\n    meta.helm.sh/release-name: nginx\n    meta.helm.sh/release-namespace: ingress-nginx\n    metallb.universe.tf/address-pool: default\n  creationTimestamp: \"2021-04-30T02:33:02Z\"\n  finalizers:\n  - service.kubernetes.io/load-balancer-cleanup\n  labels:\n    app.kubernetes.io/component: controller\n    app.kubernetes.io/instance: nginx\n    app.kubernetes.io/managed-by: Helm\n    app.kubernetes.io/name: ingress-nginx\n    app.kubernetes.io/version: 0.45.0\n    helm.sh/chart: ingress-nginx-3.29.0\n  name: nginx-ingress-nginx-controller\n  namespace: ingress-nginx\nspec:\n  clusterIP: 10.43.219.102\n  clusterIPs:\n  - 10.43.219.102\n  externalTrafficPolicy: Local\n  healthCheckNodePort: 32689\n  ipFamilies:\n  - IPv4\n  ipFamilyPolicy: SingleStack\n  ports:\n  - name: http\n    nodePort: 32595\n    port: 80\n    protocol: TCP\n    targetPort: http\n  - name: https\n    nodePort: 31937\n    port: 443\n    protocol: TCP\n    targetPort: https\n  selector:\n    app.kubernetes.io/component: controller\n    app.kubernetes.io/instance: nginx\n    app.kubernetes.io/name: ingress-nginx\n  sessionAffinity: None\n  type: LoadBalancer\nstatus:\n  loadBalancer:\n    ingress:\n    - ip: 999.999.999.999\n\nCtrl-D to save\n\nsudo kubectl apply -f ingress-svc-edit.yaml\n\nsudo kubectl patch -n ingress-nginx services/nginx-ingress-nginx-controller --patch '{\"metadata\":{\"annotations\":{\"metallb.universe.tf/address-pool\":\"default\"}},\"spec\":{\"externalTrafficPolicy\":\"Local\"}}\nsudo kubectl patch deployments/nginx-ingress-nginx-controller --patch '{\"spec\":{\"template\":{\"spec\":{\"hostNetwork\":true}}}}' -n ingress-nginx\n\n\n\n\n\nsudo kubectl create namespace cert-manager\n# Used --version v0.15.1 before; now v1.3.1\nsudo helm install cert-manager jetstack/cert-manager --namespace cert-manager --version v1.3.1 --set installCRDs=true\nsudo kubectl --namespace cert-manager create secret generic prod-route53-credentials-secret --from-literal=secret-access-key=\"$SECRETKEY\"\n\n\napiVersion: cert-manager.io/v1alpha2\nkind: ClusterIssuer\nmetadata:\n  name: letsencrypt-prod\n  namespace: cert-manager\nspec:\n  acme:\n    # The ACME server URL\n    server: https://acme-v02.api.letsencrypt.org/directory\n    # Email address used for ACME registration\n    email: example@example.com\n    # Name of a secret used to store the ACME account private key\n    privateKeySecretRef:\n      name: letsencrypt-prod\n    # Enable the HTTP-01 challenge provider\n    solvers:\n      - http01:\n          ingress:\n            class: nginx\n    #solvers:\n    #- dns01:\n    #   route53:\n    #     region: us-east-1\n    #     accessKeyID: AKIAABCDEFGHIJKLMNOP\n    #     secretAccessKeySecretRef:\n    #       name: prod-route53-credentials-secret\n    #       key: secret-access-key\n---\napiVersion: extensions/v1beta1\nkind: Ingress\nmetadata:\n  name: core-ingress\n  annotations:\n    kubernetes.io/ingress.class: \"nginx\"\n    cert-manager.io/cluster-issuer: \"letsencrypt-prod\"\n    nginx.ingress.kubernetes.io/hsts: \"false\"\n    # nginx.ingress.kubernetes.io/add-base-url: \"true\"\n    nginx.ingress.kubernetes.io/ssl-redirect: \"true\"\n    nginx.ingress.kubernetes.io/configuration-snippet: |\n      if ($host ~ ^(?!(ci))) {\n        more_clear_headers \"Strict-Transport-Security\";\n      }\n      if ($host ~ ^(.*\\.?)vsekai\\.([a-z]*)$ ) {\n          set $subd $1;\n          set $tld $2;\n          set $newdomain v-sekai.$tld;\n          rewrite ^/(.*)$ https://$subd$newdomain/$1;\n      }\nspec:\n  tls:\n    - hosts:\n        - vsekai.cloud\n        - v-sekai.cloud\n        - uro.vsekai.cloud\n        - uro.v-sekai.cloud\n        - radiance.v-sekai.cloud\n        - ci.radiance.v-sekai.cloud\n        - ci.v-sekai.cloud\n        - radiance.vsekai.cloud\n        - ci.radiance.vsekai.cloud\n        - ci.vsekai.cloud\n        - hls.vsek.ai\n      secretName: radiance-cert-secret1\n  rules:\n    - host: vsekai.cloud\n    - host: v-sekai.cloud\n    - host: uro.vsekai.cloud\n    - host: uro.v-sekai.cloud\n      http:\n        paths:\n          - path: /\n            backend:\n              serviceName: uro\n              servicePort: 4000\n    - host: hls.vsek.ai\n      http:\n        paths:\n          - path: /\n            backend:\n              serviceName: nginx-rtmp-service\n              servicePort: 80\n    - host: radiance.vsekai.cloud\n    - host: radiance.v-sekai.cloud\n      http:\n        paths:\n          - path: /debug_headers\n            backend:\n              serviceName: echo-service\n              servicePort: 8099\n          - path: /\n            backend:\n              serviceName: echo1\n              servicePort: 80\n    - host: ci.vsekai.cloud\n    - host: ci.v-sekai.cloud\n      http:\n        paths:\n          - path: /\n            backend:\n              serviceName: gocd-server\n              servicePort: 8153\n    - host: ci.radiance.vsekai.cloud\n    - host: ci.radiance.v-sekai.cloud\n      http:\n        paths:\n          - path: /\n            backend:\n              serviceName: gocd-server\n              servicePort: 8153\nThen:\nsudo kubectl apply -f ingress.yaml\n\n\n\n\n\n\napiVersion: v1\nkind: ConfigMap\nmetadata:\n  namespace: metallb-system\n  name: config\ndata:\n  config: |\n    address-pools:\n    - name: default\n      protocol: layer2\n      addresses:\n      - 108.85.109.49/32 # &lt;--- this is the external. HOST IP\nsudo kubectl create namespace metallb-system\nsudo kubectl create secret generic -n metallb-system memberlist --from-literal=secretkey=\"$(openssl rand -base64 128)\"\nsudo kubectl apply -f metalconfig.yml\nsudo kubectl apply -f https://raw.githubusercontent.com/metallb/metallb/v0.9.3/manifests/metallb.yaml\n\n\n\n\n(Optional in theory, but you have to remove enabled platforms in gocd):\nStart by grabbing a legitimate copy of MacOSX10.15.sdk.tar.xz from your local MacBook or Mac Mini.\nThen do the following to build:\ncd /opt\nsudo chown `whoami` .\ngit clone https://github.com/tpoechtrager/osxcross.git /opt/osxcross\nsudo chown root .\ncd /opt/osxcross\nmv MacOSX10.15.sdk.tar.xz /opt/osxcross/tarballs\nUNATTENDED=1 ./build.sh\n\n# In case host OS is newer than guest OS:\ncp -p /lib64/libstdc++.so.6 /opt/osxcross/target/bin/\nOn SELinux systems, you may need to give containers read permissions:\nsudo chcon -R unconfined_u:object_r:container_share_t:s0  /opt/osxcross\n\n\n\n\n\nagent:\n  image:\n    # agent.image.repository is the GoCD Agent image name\n    repository: \"groupsinfra/gocd-agent-centos-8-groups\" # agent.image.tag is the GoCD Agent image's tag\n    tag: v20.7.0-groups-0.5.3\n    # agent.image.pullPolicy is the GoCD Agent image's pull policy\n\n    pullPolicy: \"IfNotPresent\" # agent.replicaCount is the GoCD Agent replicas Count. Specify the number of GoCD agents to run\n  replicaCount: 6\n  security:\n    ssh:\n      enabled: true\n      secretName: gocd-ssh\nserver:\n  shouldPreconfigure: false\n  security:\n    ssh:\n      enabled: true\n      secretName: gocd-ssh\n  env:\n    extraEnvVars:\n      - name: GOCD_PLUGIN_INSTALL_gitlab-oauth-authorization-plugin\n        value: https://github.com/gocd-contrib/gitlab-oauth-authorization-plugin/releases/download/v2.0.1-52-exp/gitlab-oauth-authorization-plugin-2.0.1-52.jar\n\n\nssh-keygen -t rsa -b 4096 -C \"gocd-ssh-key\" -f gocd-ssh -P ''\n( ssh-keyscan gitlab.com ; ssh-keyscan github.com ) &gt; gocd_known_hosts\nsudo kubectl create secret generic gocd-ssh --from-file=id_rsa=gocd-ssh --from-file=id_rsa.pub=gocd-ssh.pub --from-file=known_hosts=gocd_known_hosts\n\n# Chart version 1.37.0 is gocd v21.2.0\nsudo helm install -f gocd_values.yaml gocd gocd/gocd --version 1.37.0\nsudo chcon -R -t container_file_t /kube/pvc\n# Installs a trash service on port 80 by default. Let's delete it:\nsudo kubectl delete ingress gocd-server\n# Instead of using \"kubectl scale\", scale agents by editing gocd_values.yaml\n# and do \"sudo helm upgrade -f ....\"\nsudo helm install -f gocd_values.yaml gocd gocd/gocd --version 1.37.0\n# Make sure to enable the agents in the web UI, and assign them to Resources and Environments.\n\n\n\n\n# Disable and Delete all agents in the AGENTS tab of gocd.\nEdit gocd_values.yaml and set agent version to latest (e.g. v21.2.0-groups-0.5.8)\nsudo helm upgrade -f gocd_values.yaml gocd gocd/gocd --version 1.37.0\nsudo kubectl delete ingress gocd-server\n# Upgrade gocd-agent-dind:\nsudo kubectl patch deployments/gocd-agent-dind --patch '{\"spec\":{\"template\":{\"spec\":{\"containers\":[{\"name\":\"gocd-agent-dind\",\"image\":\"gocd/gocd-agent-docker-dind:v21.2.0\"}]}}}}'\n# You can also use patch to upgrade gocd-agent and gocd-server instead of upgrading via helm chart. I sometimes do it that way.\n# Delete the old Agents on the web interface. Wait for the new agents to come up, and enable them and assign them as appropriate.\n\n\n\nCreate DockerHub permissions: Create an account if you do not have one. Visit https://hub.docker.com/settings/security and create an Access Token. Copy the token.\nsudo  kubectl create secret docker-registry regcred --docker-server=https://index.docker.io/v1/ --docker-username=dockerhubuser --docker-password=XXXX --docker-email=your.dockerhub.email@example.com\n\n\n\nFor osxcross (OSX cross compiling), make sure the OSX compiler SDK you created on mac os located at /opt/osxcross.\nIf you do not have osxcross (no access to Apple hardware), then you must create an empty directory at /opt/osxcross or remove the relevant volume mounts (and remove from enabled build targets in the gocd pipelines).\nNow create Docker-in-Docker, and apply this file with kubectl create -f dind.yaml or kubectl apply -f dind.yaml\n\n\n\napiVersion: apps/v1\nkind: Deployment\nmetadata:\n  labels:\n    app: gocd\n    component: agent-dind\n  name: gocd-agent-dind\n  namespace: default\nspec:\n  progressDeadlineSeconds: 600\n  replicas: 2\n  revisionHistoryLimit: 10\n  selector:\n    matchLabels:\n      app: gocd\n      component: agent-dind\n      release: gocd\n  strategy:\n    rollingUpdate:\n      maxSurge: 25%\n      maxUnavailable: 25%\n    type: RollingUpdate\n  template:\n    metadata:\n      creationTimestamp: null\n      labels:\n        app: gocd\n        component: agent-dind\n        release: gocd\n    spec:\n      containers:\n        - env:\n            - name: GO_SERVER_URL\n              value: http://gocd-server:8153/go\n          image: gocd/gocd-agent-docker-dind:v21.2.0\n          imagePullPolicy: IfNotPresent\n          name: gocd-agent-dind\n          resources: {}\n          securityContext:\n            privileged: true\n          terminationMessagePath: /dev/termination-log\n          terminationMessagePolicy: File\n          volumeMounts:\n            - mountPath: /root/.ssh\n              name: ssh-secrets\n              readOnly: true\n            - mountPath: /root/.docker\n              name: kaniko-secret\n            - mountPath: /opt/osxcross\n              name: opt-osxcross-volume\n              readOnly: true\n      dnsPolicy: ClusterFirst\n      restartPolicy: Always\n      schedulerName: default-scheduler\n      securityContext:\n        fsGroup: 0\n        runAsGroup: 0\n        runAsUser: 0\n      serviceAccount: default\n      serviceAccountName: default\n      terminationGracePeriodSeconds: 30\n      volumes:\n        - name: ssh-secrets\n          secret:\n            defaultMode: 256\n            secretName: gocd-ssh\n        - name: kaniko-secret\n          secret:\n            secretName: regcred\n            items:\n              - key: .dockerconfigjson\n                path: config.json\n        - name: opt-osxcross-volume\n          hostPath:\n            path: /opt/osxcross\n            type: Directory\n\n\n\n\nTo add osxcross support to the main agents, create the following patch:\ngocd-agent-patch.yaml\napiVersion: apps/v1\nkind: Deployment\nmetadata:\n  name: gocd-agent\nspec:\n  template:\n    spec:\n      containers:\n        - name: gocd-agent\n          volumeMounts:\n            - mountPath: /opt/osxcross\n              name: opt-osxcross-volume\n              readOnly: true\n      volumes:\n        - name: opt-osxcross-volume\n          hostPath:\n            path: /opt/osxcross\n            type: Directory\nand apply with:\nsudo kubectl patch deployments/gocd-agent -p \"$(cat gocd-agent-patch.yaml)\"\nMake sure to enable the Agents when they come up on the GoCD Dashboard. Add every server to the “development” environment. Also, assign linux servers to “mingw” and “linux”. Assign the dind agents to “dind”.\nFor GitLab, go to https://ci.v-sekai.cloud/go/admin/security/auth_configs and select Create new authorization configuration -&gt; gitlab-auth-config / GitLab Authentication plugin / follow documentation here: https://github.com/gocd-contrib/gitlab-oauth-authorization-plugin/blob/master/INSTALL.md - Do not check Allow only known users to login yet. If this works, you can skip the text auth step and corresponding passwd commands.\nCreate Guest login:\n\nGo to auth_configs, Create new authorization configuration -&gt; guest-login / Guest Login Plugin / Fill out Go server URL / Username view / Display name Guest.\nNow, go to Roles Management. Create role guest. Add Deny for all types and Resources * as desired.\nIn an Incognito window, visit the CI system and login as Guest. Close the incognito window.\nNow, go to Users Management. Select view / Guest and select Roles -&gt; guest\nAdmin -&gt; Pipelines. Select Pipeline Group beta, click + on the top right of the whole group, go to Roles, add guest, and only check View. Save this.\n\nAt this point, Guest should have permission to view pipelines, see logs, download artifacts but nothing else.\nFor text auth, go to https://ci.v-sekai.cloud/go/admin/security/auth_configs and select Create new authorization configuration -&gt; file-auth-config / Password File Authentication plugin / /godata/config/password.properties\nsudo kubectl exec gocd-server-6d77846995-5l244 -- touch /godata/config/password.properties\nsudo yum install httpd-tools\nhtpasswd -c -B passwd admin\ncat passwd | sudo kubectl exec gocd-server-6d77846995-5l244 -- sudo tee /kubepvc/pvc/*/godata/config/password.properties\nNow go to users page, edit your user and enable Global Admin.\nNow go to file-auth-config, edit configuration, enable Allow only known users to login\n\n\n\nGo to Admin -&gt; Config Repositories\n\nConfig #repository Name: groups-gocd-pipelines\nPlugin ID: JSON Configuration Plugin\nMaterial Type: Git\nURL: git@gitlab.com:godot-groups/groups-gocd-pipelines\nBranch: master\nGoCD pipeline files pattern: *.gopipeline.json\nGoCD environment files pattern: *.goenvironment.json\n\nRules\n\nAllow: Pipeline Group: beta\nAllow: Environment: development\n\n\n\n\ncurl -L https://github.com/fluxcd/flux2/releases/download/v0.24.1/flux_0.24.1_linux_amd64.tar.gz | tar -zxf - flux\nsudo cp flux /usr/local/bin/flux\nsudo chmod +x /usr/local/bin/flux\nsudo kubectl apply -f https://github.com/fluxcd/flux2/releases/download/v0.24.1/install.yaml\nFork the flux-config #repository from here https://github.com/V-Sekai/flux-config into your own github account, and set GHUSER=your github account.\nNow, in your fork of flux-config, go to project Settings -&gt; Deploy Keys and add the result of the above identity command. Make sure to check Allow write access.\nOnce you have done this, you can continue with the flux setup using your newly forked repository.\nexport GHUSER=\"xxxxxxxxx\"\nsudo flux install\nsudo flux create source git gitrepo --url=https://github.com/$GHUSER/flux-config  --branch=flux2\nsudo flux create kustomization workloads --source=GitRepository/gitrepo --path=\"./workloads/\"\nsudo flux get all\nFOR DEBUGGING ONLY: sudo setenforce permissive - this appears to have no effect, so there is a different problem.\n\n\n\n\n\nstatefulset:\n  resources:\n    limits:\n      memory: \"8Gi\"\n    requests:\n      memory: \"8Gi\"\nconf:\n  cache: \"2Gi\"\n  max-sql-memory: \"2Gi\"\ntls:\n  enabled: true\n\n\n\n\n# Helm version MAY be deprecated. We will switch to operator below.\n\n#sudo helm install cockroachdb --values cockroachdb.values.yaml cockroachdb/cockroachdb\n#sudo kubectl certificate approve default.node.cockroachdb-0\n#sudo kubectl certificate approve default.node.cockroachdb-1\n#sudo kubectl certificate approve default.node.cockroachdb-2\n#sudo kubectl certificate approve default.client.root\n\nwget https://raw.githubusercontent.com/cockroachdb/cockroach-operator/master/manifests/operator.yaml -O cockroach-operator.yaml\nsudo kubectl apply -f cockroach-operator.yaml\n\nwget https://raw.githubusercontent.com/cockroachdb/cockroach-operator/master/config/crd/bases/crdb.cockroachlabs.com_crdbclusters.yaml\nsudo kubectl apply -f crdb.yaml\n\ncat &gt; cockroachdb_extra_resource_certgen.yaml\napiVersion: v1\nkind: ServiceAccount\nmetadata:\n  name: cockroachdb\n  labels:\n    app: cockroachdb\n---\napiVersion: rbac.authorization.k8s.io/v1\nkind: Role\nmetadata:\n  name: cockroachdb\n  labels:\n    app: cockroachdb\nrules:\n- apiGroups:\n  - \"\"\n  resources:\n  - secrets\n  verbs:\n  - create\n  - get\n---\napiVersion: rbac.authorization.k8s.io/v1\nkind: ClusterRole\nmetadata:\n  name: cockroachdb\n  labels:\n    app: cockroachdb\nrules:\n- apiGroups:\n  - certificates.k8s.io\n  resources:\n  - certificatesigningrequests\n  verbs:\n  - create\n  - get\n  - watch\n---\napiVersion: rbac.authorization.k8s.io/v1\nkind: RoleBinding\nmetadata:\n  name: cockroachdb\n  labels:\n    app: cockroachdb\nroleRef:\n  apiGroup: rbac.authorization.k8s.io\n  kind: Role\n  name: cockroachdb\nsubjects:\n- kind: ServiceAccount\n  name: cockroachdb\n  namespace: default\n---\napiVersion: rbac.authorization.k8s.io/v1\nkind: ClusterRoleBinding\nmetadata:\n  name: cockroachdb\n  labels:\n    app: cockroachdb\nroleRef:\n  apiGroup: rbac.authorization.k8s.io\n  kind: ClusterRole\n  name: cockroachdb\nsubjects:\n- kind: ServiceAccount\n  name: cockroachdb\n  namespace: default\n\nCtrl-D\n\n\n# Note: may need to set up physicalVolume and physicalVolumeClaim objects for each cockraoch node.\n\n# The permissions may be set wrong if you are upgrading. Fix them with:\nsudo chown -R 1000581000 /kube/pvc/pvc-aaaaaaaaaaaaaaaaaa /kube/pvc/pvc-bbbbbbbbbbbbbbb /kube/pvc/pvc-cccccccccccccccccccccccccccccccc\n\n# OLD curl -o client-secure.yaml https://raw.githubusercontent.com/cockroachdb/cockroach/master/cloud/kubernetes/client-secure.yaml\n# OLD sudo kubectl apply -f client-secure.yaml\n\nwget https://raw.githubusercontent.com/cockroachdb/cockroach-operator/master/examples/client-secure-operator.yaml\nsudo kubectl apply -f client-secure-operator.yaml\n\nsudo kubectl certificate approve default.client.uro-prod\n\nsudo kubectl exec -it cockroachdb-client-secure -- ./cockroach sql --certs-dir=/cockroach-certs --host=cockroachdb-public\nIn SQL, write:\nCREATE DATABASE uro_prod;\nCREATE USER 'uro-prod' WITH PASSWORD 'blablablablaSOMEDATABASEPASSWORD';\nGRANT ALL ON DATABASE uro_prod to \"uro-prod\";\nTo make backups:\nsudo kubectl exec -it cockroachdb-client-secure -- ./cockroach dump --certs-dir=/cockroach-certs --host=cockroachdb-public uro_prod &gt; uro_prod_backup.txt\nApply secrets:\n(On dev machine) MIX_ENV=prod mix phx.gen.secret\n# Copy the output of above, and copy the database password from above:\nsudo kubectl create secret generic uro-prod --from-literal=secret-key-base='GENERATED_WITH_ABOVE_COMMAND' --from-literal=pass='blablablablaSOMEDATABASEPASSWORD'\n\nsudo kubectl apply -f https://raw.githubusercontent.com/V-Sekai/uro/master/kubernetes.yaml\n\n\n\n\n\n\nk3s set the default client cert for root to expire after a year or so. This leads to a problem where you can’t administer your own cluster because your root account’s cert is expired. So I had to figure out how to fix this.\nFor the most part, the process I came up with matches this more concise post here: https://github.com/k3s-io/k3s/issues/2342#issuecomment-713016341\nFirst approach, how to rotate kube client certificates: Because we need to modify /root/.kube/config, I ran sudo -i to login as a root shell.\n\nmkdir tls and create tls/config.txt with the following lines:\n\n# --------------------- tls/config.txt -----------\n[ req ]\ndistinguished_name                           = req_distinguished_name\nreq_extensions                                   = v3_req\nprompt = no\n[ req_distinguished_name ]\norganizationName       = system:masters\ncommonName             = system:admin\n[ v3_req ]\nbasicConstraints                                 = CA:FALSE\nkeyUsage                                           = critical, digitalSignature, keyEncipherment\nextendedKeyUsage                            = clientAuth\n# -------------------------------------------------\n\ncp /kube/rancher/k3s/server/tls/client-ca.crt tls/client-ca.crt\nopenssl ecparam -name prime256v1 -genkey -noout -out tls/new-key.pem\nopenssl req -new -key tls/new-key.pem -sha256 -nodes -out tls/new-req.csr -config tls/config.txt\nopenssl x509 -req -days 3000 -in tls/new-req.csr -CA tls/client-ca.crt -CAkey /kube/rancher/k3s/server/tls/client-ca.key -set_serial 4294742997922865905 -extensions v3_req -extfile tls/config.txt -out tls/new-client.crt\ncat tls/new-client.crt tls/client-ca.crt | base64 -w0; echo\ncat tls/new-key.pem | base64 -w0; echo\nedit .kube/config and update client-certificate-data: and client-key-data: respectively.\n\nHow to upgrade the rest of the certs.\nfind /var/lib/rancher/k3s/server/tls -name '*.crt' | while read fn; do echo $fn ===========; openssl x509 -text -in $fn | grep Not\\ After | grep '202[012]'; done\nHere is the script I ran:\n#!/bin/bash\nset -\nset -x\n[ -e \"$1.csr\" ] || openssl x509 -x509toreq -in \"$1.crt\" -out \"$1.csr\" -signkey \"$1.key\"\nmv -i \"$1.crt\" \"$1.crt.bak.$(date +%s)\"\nopenssl x509 -req -in \"$1.csr\" -CA \"client-ca.crt\" -CAkey \"client-ca.key\" -CAcreateserial -days 3650 -out \"$1.crt\"\ncat \"client-ca.crt\" &gt;&gt; \"$1.crt\"\nyou can use this process to update the client cert for /root/.kube/config\nNote that etcd/client.crt actually uses its own server-ca.key instead of client-ca within the etcd folder, so you need a slight modification of the script for this one. I don’t know what any of these certs do so I just did all of them\nFinally, client-k3s-controller.crt and client-kube-proxy.crt must be copied from /var/lib/rancher/k3s/server/tls to /var/lib/rancher/k3s/agent\n\n\n\nStart the upgrade process with:\nsudo dnf upgrade --refresh\nsudo dnf install dnf-plugin-system-upgrade\nsudo dnf system-upgrade download --releasever=34\nAnswer y to all prompts confirming list of packages and new GPG keys, if any. Once successful, it displays:\nDownload complete! Use 'dnf system-upgrade reboot' to start the upgrade.\nTo remove cached metadata and transaction use 'dnf system-upgrade clean'\nThe downloaded packages were saved in cache until the next successful transaction.\nYou can remove cached packages by executing 'dnf clean packages'.\nComplete the upgrade with:\nsudo dnf system-upgrade reboot\nThis will bring the system down for about an hour.\n\n\n\nsudo helm repo update\n# If the stable/nginx-ingress chart is still installed, make sure to helm uninstall nginx first.\nsudo helm upgrade --namespace ingress-nginx nginx ingress-nginx/ingress-nginx --set controller.replicaCount=2\nsudo helm upgrade cert-manager jetstack/cert-manager --namespace cert-manager --set installCRDs=true\n### I was not able to get external-dns to upgrade, but it is not user-facing so we keep running the old version.\n# sudo helm upgrade external-dns --reuse-values bitnami/external-dns\n\n\n\ncurl -sfL https://raw.githubusercontent.com/rancher/k3s/master/install.sh | sh -s - server -o /root/.kube/config --default-local-storage-path /kube/pvc --no-deploy=servicelb --disable=traefik --disable=servicelb\n\n\n\nRun the shell:\nsudo kubectl exec -it cockroachdb-client-secure -- ./cockroach sql --certs-dir=/cockroach-certs --host=cockroachdb-public\nAt the top of the shell prompt, it will say something like this. Copy the first two numbers from the CockroachDB CCL line. In this case, 20.2\n#\n# Welcome to the CockroachDB SQL shell.\n# All statements must be terminated by a semicolon.\n# To exit, type: \\q.\n#\n# Server version: CockroachDB CCL v20.2.2 (x86_64-unknown-linux-gnu\nReplace some.version in the following command with the value we found above:\nSET CLUSTER SETTING cluster.preserve_downgrade_option = 'some.version';\nFinally, perform the upgrade:\nsudo kubectl delete job cockroachdb-init\nsudo helm upgrade cockroachdb cockroachdb/cockroachdb --values cockroachdb.values.yaml\ncurl -o client-secure.yaml https://raw.githubusercontent.com/cockroachdb/cockroach/master/cloud/kubernetes/client-secure.yaml\nsudo kubectl delete pods/cockroachdb-client-secure\nsudo kubectl create -f client-secure.yaml"
+    "text": "https://www.cse.wustl.edu/~taoju/zoum/projects/TriMultPoly\nhttps://em-yu.github.io/\nhttps://ns.inria.fr/d3/CASSIE\nhttps://libigl.github.io/\nhttps://github.com/godotengine/\nhttps://www.blender.org/"
   },
   {
-    "objectID": "decisions/20200602-manage-backend-with-k3s.html#positive-consequences",
-    "href": "decisions/20200602-manage-backend-with-k3s.html#positive-consequences",
-    "title": "Accepted: Manage backend resources on one or more physical machines with K3S",
+    "objectID": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html#derivative-license",
+    "href": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html#derivative-license",
+    "title": "Accepted: Take a list of 3D points that form a vaguely closed boundary in space and triangulate in Godot Engine",
     "section": "",
-    "text": "Knowledge gains about service creation\nOperation experience"
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20200602-manage-backend-with-k3s.html#negative-consequences",
-    "href": "decisions/20200602-manage-backend-with-k3s.html#negative-consequences",
-    "title": "Accepted: Manage backend resources on one or more physical machines with K3S",
+    "objectID": "decisions/20230716-enhancing-avatar-creation-process-01-regular.html",
+    "href": "decisions/20230716-enhancing-avatar-creation-process-01-regular.html",
+    "title": "Proposed: Enhancing Avatar Creation Process in V-Sekai Regular",
     "section": "",
-    "text": "Constant maintenance"
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nV-Sekai currently has limitations when it comes to creating avatars with specific features and customizations. This can be a hindrance for users who want to have more control over the appearance of their avatars. To address this, we propose an enhancement that introduces various tools and techniques to overcome these limitations and provide a more comprehensive avatar creation process.\n\n\n\nHere is a list of raw processes to be broken down.\n\n\nTo implement the requested changes, here are the modified instructions:\n\nCreating the avatar face: Utilizes digital drawing techniques to design and create the facial features of the avatar.\n\nInput mime type: None\nOutput mime type: Digital drawing/image file (e.g., PNG, SVG)\n\nChanging colors: Utilizes a digital paintbrush tool like Penpot to modify and customize the colors of the avatar.\n\nInput mime type: Digital drawing/image file (e.g., PNG, SVG)\nOutput mime type: Digital drawing/image file (e.g., PNG, SVG)\n\nSelecting the best-looking avatars: Evaluates and chooses the most visually appealing avatars from a pool of options.\n\nInput mime type: Digital drawing/image file (e.g., PNG, SVG)\nOutput mime type: Digital drawing/image file (e.g., PNG, SVG)\n\nRemoving the background image: Removes the background image to make rework easier. May provide worse results with edge details.\n\nInput mime type: Digital drawing/image file (e.g., PNG, SVG)\nOutput mime type: Digital drawing/image file (e.g., PNG, SVG)\n\nAdding a body: Incorporates a body to the avatar using Blender’s CC0 base mesh or a similar tool.\n\nInput mime type: Digital drawing/image file (e.g., PNG, SVG)\nOutput mime type: Digital drawing/image file (e.g., PNG, SVG)\n\nCreating a 3D model of the back of the avatar: If feasible, attempts to create a 3D model of the back of the avatar for a more comprehensive representation.\n\nInput mime type: Digital drawing/image file (e.g., PNG, SVG)\nOutput mime type: Digital drawing/image file (e.g., PNG, SVG)\n\nSimplifying images: Uses a tool to simplify and refine the entire avatar image as a whole, removing any unnecessary image details or complexities.\n\nInput mime type: Digital drawing/image file (e.g., PNG, SVG)\nOutput mime type: Digital drawing/image file (e.g., PNG, SVG)\n\nAdding clothing and accessories: Enhances the avatar by adding clothing and accessories using tools like Vroid Hub.\n\nInput mime type: Digital drawing/image file (e.g., PNG, SVG)\nOutput mime type: Digital drawing/image file (e.g., PNG, SVG)\n\nPlacing the 2D image as a reference: Positions the 2D reference image in front of the 3D model to serve as a visual guide during customization.\n\nInput mime type: Digital drawing/image file (e.g., PNG, SVG), 3D model file (e.g., GLTF)\nOutput mime type: 3D model file (e.g., GLTF), Digital image file (e.g., PNG, SVG)\n\nCapturing and enhancing images: Captures images from various angles using a camera and enhances them to improve the overall quality.\n\n\nInput mime type: Digital drawing/image file (e.g., PNG, SVG)\nOutput mime type: Digital image file (e.g., PNG, SVG)\n\n\nGenerating text captions: Creates descriptive text captions for the captured images to provide additional context or information.\n\n\nInput mime type: Digital image file (e.g., PNG, SVG)\nOutput mime type: Text file (e.g., TXT)\n\n\nUsing a 2D reference image in Blender: Uses a 2D reference image within Blender to guide the customization process.\n\n\nInput mime type: Digital drawing/image file (e.g., PNG, SVG)\nOutput mime type: 3D model file (e.g., GLTF), Digital image file (e.g., PNG, SVG)\n\n\n\n\n\n\nUsers will be able to create highly customizable avatars with specific features.\nThe avatar creation process will be enhanced with a variety of tools and techniques.\nDetailed customization of colors, clothing, accessories, and facial expressions will be possible.\nMotion capture capabilities can be integrated for more realistic animations.\n\n\n\n\n\nThe implementation process is complex and may require advanced technical skills from users.\nSome steps, like creating a 3D model of the back of the avatar, may not always be successful.\nPainting errors and other imperfections may remain in the final avatar.\n\n\n\n\n\nExcessive complexity or technical requirements: We want the avatar creation process to be user-friendly and accessible to a wide range of users, so any options that require advanced technical skills or have excessively complex customization controls will not be included.\n\n\n\n\nNo, the proposed enhancement involves a multi-step process that cannot be easily replicated with just a few lines of script.\n\n\n\nThe proposed enhancement addresses the limitations in V-Sekai’s avatar creation process, providing users with a comprehensive solution for creating highly customizable avatars. By implementing these tools and techniques within the platform, V-Sekai can offer a more robust and user-friendly experience for its community.\n\n\n\n\nV-Sekai\nDetail Tweaker\nInstructBLIP: Towards General-purpose Vision-Language Models with Instruction Tuning\nPetals"
   },
   {
-    "objectID": "decisions/20200602-manage-backend-with-k3s.html#option-graveyard",
-    "href": "decisions/20200602-manage-backend-with-k3s.html#option-graveyard",
-    "title": "Accepted: Manage backend resources on one or more physical machines with K3S",
+    "objectID": "decisions/20230716-enhancing-avatar-creation-process-01-regular.html#metadata",
+    "href": "decisions/20230716-enhancing-avatar-creation-process-01-regular.html#metadata",
+    "title": "Proposed: Enhancing Avatar Creation Process in V-Sekai Regular",
     "section": "",
-    "text": "Option: Dedicated Servers\nOption: Virtual Machines"
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20200602-manage-backend-with-k3s.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20200602-manage-backend-with-k3s.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Accepted: Manage backend resources on one or more physical machines with K3S",
+    "objectID": "decisions/20230716-enhancing-avatar-creation-process-01-regular.html#context-and-problem-statement",
+    "href": "decisions/20230716-enhancing-avatar-creation-process-01-regular.html#context-and-problem-statement",
+    "title": "Proposed: Enhancing Avatar Creation Process in V-Sekai Regular",
     "section": "",
-    "text": "Yes, it is possible to deploy this system using docker or in the root system."
+    "text": "V-Sekai currently has limitations when it comes to creating avatars with specific features and customizations. This can be a hindrance for users who want to have more control over the appearance of their avatars. To address this, we propose an enhancement that introduces various tools and techniques to overcome these limitations and provide a more comprehensive avatar creation process."
   },
   {
-    "objectID": "decisions/20200602-manage-backend-with-k3s.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20200602-manage-backend-with-k3s.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Accepted: Manage backend resources on one or more physical machines with K3S",
+    "objectID": "decisions/20230716-enhancing-avatar-creation-process-01-regular.html#proposed-solution",
+    "href": "decisions/20230716-enhancing-avatar-creation-process-01-regular.html#proposed-solution",
+    "title": "Proposed: Enhancing Avatar Creation Process in V-Sekai Regular",
     "section": "",
-    "text": "Having experience with kubernetes and maintaining discipline will make scaling or service upgrades smoother in the future."
+    "text": "Here is a list of raw processes to be broken down.\n\n\nTo implement the requested changes, here are the modified instructions:\n\nCreating the avatar face: Utilizes digital drawing techniques to design and create the facial features of the avatar.\n\nInput mime type: None\nOutput mime type: Digital drawing/image file (e.g., PNG, SVG)\n\nChanging colors: Utilizes a digital paintbrush tool like Penpot to modify and customize the colors of the avatar.\n\nInput mime type: Digital drawing/image file (e.g., PNG, SVG)\nOutput mime type: Digital drawing/image file (e.g., PNG, SVG)\n\nSelecting the best-looking avatars: Evaluates and chooses the most visually appealing avatars from a pool of options.\n\nInput mime type: Digital drawing/image file (e.g., PNG, SVG)\nOutput mime type: Digital drawing/image file (e.g., PNG, SVG)\n\nRemoving the background image: Removes the background image to make rework easier. May provide worse results with edge details.\n\nInput mime type: Digital drawing/image file (e.g., PNG, SVG)\nOutput mime type: Digital drawing/image file (e.g., PNG, SVG)\n\nAdding a body: Incorporates a body to the avatar using Blender’s CC0 base mesh or a similar tool.\n\nInput mime type: Digital drawing/image file (e.g., PNG, SVG)\nOutput mime type: Digital drawing/image file (e.g., PNG, SVG)\n\nCreating a 3D model of the back of the avatar: If feasible, attempts to create a 3D model of the back of the avatar for a more comprehensive representation.\n\nInput mime type: Digital drawing/image file (e.g., PNG, SVG)\nOutput mime type: Digital drawing/image file (e.g., PNG, SVG)\n\nSimplifying images: Uses a tool to simplify and refine the entire avatar image as a whole, removing any unnecessary image details or complexities.\n\nInput mime type: Digital drawing/image file (e.g., PNG, SVG)\nOutput mime type: Digital drawing/image file (e.g., PNG, SVG)\n\nAdding clothing and accessories: Enhances the avatar by adding clothing and accessories using tools like Vroid Hub.\n\nInput mime type: Digital drawing/image file (e.g., PNG, SVG)\nOutput mime type: Digital drawing/image file (e.g., PNG, SVG)\n\nPlacing the 2D image as a reference: Positions the 2D reference image in front of the 3D model to serve as a visual guide during customization.\n\nInput mime type: Digital drawing/image file (e.g., PNG, SVG), 3D model file (e.g., GLTF)\nOutput mime type: 3D model file (e.g., GLTF), Digital image file (e.g., PNG, SVG)\n\nCapturing and enhancing images: Captures images from various angles using a camera and enhances them to improve the overall quality.\n\n\nInput mime type: Digital drawing/image file (e.g., PNG, SVG)\nOutput mime type: Digital image file (e.g., PNG, SVG)\n\n\nGenerating text captions: Creates descriptive text captions for the captured images to provide additional context or information.\n\n\nInput mime type: Digital image file (e.g., PNG, SVG)\nOutput mime type: Text file (e.g., TXT)\n\n\nUsing a 2D reference image in Blender: Uses a 2D reference image within Blender to guide the customization process.\n\n\nInput mime type: Digital drawing/image file (e.g., PNG, SVG)\nOutput mime type: 3D model file (e.g., GLTF), Digital image file (e.g., PNG, SVG)"
   },
   {
-    "objectID": "decisions/20200602-manage-backend-with-k3s.html#references",
-    "href": "decisions/20200602-manage-backend-with-k3s.html#references",
-    "title": "Accepted: Manage backend resources on one or more physical machines with K3S",
+    "objectID": "decisions/20230716-enhancing-avatar-creation-process-01-regular.html#positive-consequences",
+    "href": "decisions/20230716-enhancing-avatar-creation-process-01-regular.html#positive-consequences",
+    "title": "Proposed: Enhancing Avatar Creation Process in V-Sekai Regular",
     "section": "",
-    "text": "https://k3s.io/"
+    "text": "Users will be able to create highly customizable avatars with specific features.\nThe avatar creation process will be enhanced with a variety of tools and techniques.\nDetailed customization of colors, clothing, accessories, and facial expressions will be possible.\nMotion capture capabilities can be integrated for more realistic animations."
   },
   {
-    "objectID": "decisions/20200602-manage-backend-with-k3s.html#derivative-license",
-    "href": "decisions/20200602-manage-backend-with-k3s.html#derivative-license",
-    "title": "Accepted: Manage backend resources on one or more physical machines with K3S",
+    "objectID": "decisions/20230716-enhancing-avatar-creation-process-01-regular.html#negative-consequences",
+    "href": "decisions/20230716-enhancing-avatar-creation-process-01-regular.html#negative-consequences",
+    "title": "Proposed: Enhancing Avatar Creation Process in V-Sekai Regular",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "The implementation process is complex and may require advanced technical skills from users.\nSome steps, like creating a 3D model of the back of the avatar, may not always be successful.\nPainting errors and other imperfections may remain in the final avatar."
   },
   {
-    "objectID": "decisions/20240708-vsekai-my-life-as-a-queen.html",
-    "href": "decisions/20240708-vsekai-my-life-as-a-queen.html",
-    "title": "Proposed: V-Sekai: My Life as a Princess",
+    "objectID": "decisions/20230716-enhancing-avatar-creation-process-01-regular.html#option-graveyard",
+    "href": "decisions/20230716-enhancing-avatar-creation-process-01-regular.html#option-graveyard",
+    "title": "Proposed: Enhancing Avatar Creation Process in V-Sekai Regular",
     "section": "",
-    "text": "The second Godot XR Game Jam is organized by the Godot XR Community and is occurring on July 8th, 2024. The jam theme is: Relaxation!\n\n\n\nCreate an Android XR game using the theme of “Relaxation” and utilizing Godot Engine 4.3 with our module for goal hierarchical task network planner and our portable avatar import format (VRM).\n\n\n\nIn “V-Sekai: My Life as a Princess,” players assume the role of a princess tasked with rebuilding and managing a kingdom. The game focuses on relaxation through planning, resource management, VR interactions, and adventurer tasking.\n\n\n\nLateral Thinking with Weathered Technology\nDesigned so both planning and people can do the same things\n\n\n\n\nvar memories: Dictionary = {\n    \"is_at\": {\"player\": \"cabin\"},\n    \"is_outside_of\": {\"cave entrance\": \"cabin\"},\n    \"contains\": {\"first_room\": \"treasure\"}\n}\n\nvar todo_list: Array = [\n    \"Explore the cabin\",\n    \"Find the cave entrance\",\n    \"Enter the cave\",\n    \"Reach the treasure room\"\n]\nYou start in a little cabin in the woods. You have a cave you can venture into, and at the end is treasure. This initial prototype serves as a simple introduction to the game’s mechanics and environment.\n\n\n\nvar princess_strategic_memories: Dictionary = {\n    \"is_at\": {\"princess\": \"royal cabin\"},\n    \"has_goal\": {\"princess\": \"retrieve treasure from the cave\"},\n    \"preparation_status\": {\"princess\": \"not_started\"}\n}\n\nvar princess_strategic_plan: Array = [\n    \"Set goal to retrieve treasure from the cave\",\n    \"Prepare for the journey\"\n]\n\nvar princess_tactical_memories: Dictionary = {\n    \"is_at\": {\"princess\": \"royal cabin\"},\n    \"knows_location\": {\"princess\": [\"royal cabin\", \"cave entrance\"]},\n    \"route_planned\": {\"princess\": false}\n}\n\nvar princess_tactical_plan: Array = [\n    \"Move to the royal cabin\",\n    \"Locate the cave entrance\",\n    \"Plan route through the cave to the treasure room\"\n]\n\nvar princess_operational_memories: Dictionary = {\n    \"is_at\": {\"princess\": \"royal cabin\"},\n    \"visited\": {\"princess\": []},\n    \"contains\": {\"first_room\": \"treasure\"}\n}\n\nvar princess_operational_plan: Array = [\n    \"Gather supplies for the journey\",\n    \"Travel to the cave entrance\",\n    \"Wait for the adventurer\",\n    \"Provide support from outside the cave\",\n    \"Receive the treasure from the adventurer\"\n]\n\nvar adventurer_tactical_memories: Dictionary = {\n    \"is_at\": {\"adventurer\": \"adventurer's cabin\"},\n    \"knows_location\": {\"adventurer\": [\"adventurer's cabin\", \"cave entrance\"]},\n    \"route_planned\": {\"adventurer\": false}\n}\n\nvar adventurer_tactical_plan: Array = [\n    \"Move to the adventurer's cabin\",\n    \"Locate the cave entrance\",\n    \"Plan route through the cave to the treasure room\"\n]\n\nvar adventurer_operational_memories: Dictionary = {\n    \"is_at\": {\"adventurer\": \"adventurer's cabin\"},\n    \"visited\": {\"adventurer\": []},\n    \"contains\": {\"first_room\": \"treasure\"}\n}\n\nvar adventurer_operational_plan: Array = [\n    \"Walk to the adventurer's cabin\",\n    \"Search for the cave entrance\",\n    \"Enter the cave\",\n    \"Navigate to the first room\",\n    \"Collect the treasure\",\n    \"Return to the cave entrance and hand over the treasure to the princess\"\n]\nIn the initial prototype, you explore the cave yourself. In “V-Sekai: My Life as a Princess,” you will reverse this concept by taking on the role of the princess who supplies adventurers with instructions to explore the cave and retrieve treasures. This shift from direct exploration to strategic management aligns with the relaxation theme.\n\n\n\n\n\nRelaxing Gameplay: Focuses on non-combat activities like building, gardening, organizing events, and sending adventurers on quests.\nImmersive Experience: Utilizes VRM technology for customizable avatars and Godot’s XR capabilities for an engaging experience.\nDynamic Task Management: The HTN planner ensures that tasks are generated based on player actions, providing a unique experience each time.\n\n\n\n\n\nLearning Curve: Players unfamiliar with resource management games may find it challenging initially.\nHardware Requirements: Requires a VR-capable device, which may limit accessibility.\n\n\n\n\n\nCombat Mechanics: Instead of focusing on relaxation, we could have included combat elements, but this would detract from the theme of relaxation.\nLinear Storyline: A fixed storyline could have been implemented, but dynamic task generation offers more replayability.\n\n\n\n\n\nSeasonal Events: While the game includes various activities, seasonal events such as festivals or special quests tied to real-world holidays are not included. These could add variety but would require additional development time and resources.\n\n\n\n\n\nCore Development: The V-Sekai development team will handle all core aspects of the game, including coding, art, and design.\nCommunity Contributions: Open to contributions from the Godot XR community for additional content and features.\n\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\niFire\nBrune\n\n\n\n\n\nV-Sekai\nGodot XR\nRelaxation\nVRM\nHTN Planner\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nFinal Fantasy Crystal Chronicles: My Life as a King - A Lost WiiWare Classic [REFFOID]\nGodot XR Game Jam July 2024\nGridmap usage in Cassette Beasts\n\nAI assistant Aria assisted with this article."
+    "text": "Excessive complexity or technical requirements: We want the avatar creation process to be user-friendly and accessible to a wide range of users, so any options that require advanced technical skills or have excessively complex customization controls will not be included."
   },
   {
-    "objectID": "decisions/20240708-vsekai-my-life-as-a-queen.html#the-context",
-    "href": "decisions/20240708-vsekai-my-life-as-a-queen.html#the-context",
-    "title": "Proposed: V-Sekai: My Life as a Princess",
+    "objectID": "decisions/20230716-enhancing-avatar-creation-process-01-regular.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230716-enhancing-avatar-creation-process-01-regular.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Enhancing Avatar Creation Process in V-Sekai Regular",
     "section": "",
-    "text": "The second Godot XR Game Jam is organized by the Godot XR Community and is occurring on July 8th, 2024. The jam theme is: Relaxation!"
+    "text": "No, the proposed enhancement involves a multi-step process that cannot be easily replicated with just a few lines of script."
   },
   {
-    "objectID": "decisions/20240708-vsekai-my-life-as-a-queen.html#the-problem-statement",
-    "href": "decisions/20240708-vsekai-my-life-as-a-queen.html#the-problem-statement",
-    "title": "Proposed: V-Sekai: My Life as a Princess",
+    "objectID": "decisions/20230716-enhancing-avatar-creation-process-01-regular.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230716-enhancing-avatar-creation-process-01-regular.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Enhancing Avatar Creation Process in V-Sekai Regular",
     "section": "",
-    "text": "Create an Android XR game using the theme of “Relaxation” and utilizing Godot Engine 4.3 with our module for goal hierarchical task network planner and our portable avatar import format (VRM)."
+    "text": "The proposed enhancement addresses the limitations in V-Sekai’s avatar creation process, providing users with a comprehensive solution for creating highly customizable avatars. By implementing these tools and techniques within the platform, V-Sekai can offer a more robust and user-friendly experience for its community."
   },
   {
-    "objectID": "decisions/20240708-vsekai-my-life-as-a-queen.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240708-vsekai-my-life-as-a-queen.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: V-Sekai: My Life as a Princess",
+    "objectID": "decisions/20230716-enhancing-avatar-creation-process-01-regular.html#references",
+    "href": "decisions/20230716-enhancing-avatar-creation-process-01-regular.html#references",
+    "title": "Proposed: Enhancing Avatar Creation Process in V-Sekai Regular",
     "section": "",
-    "text": "In “V-Sekai: My Life as a Princess,” players assume the role of a princess tasked with rebuilding and managing a kingdom. The game focuses on relaxation through planning, resource management, VR interactions, and adventurer tasking.\n\n\n\nLateral Thinking with Weathered Technology\nDesigned so both planning and people can do the same things\n\n\n\n\nvar memories: Dictionary = {\n    \"is_at\": {\"player\": \"cabin\"},\n    \"is_outside_of\": {\"cave entrance\": \"cabin\"},\n    \"contains\": {\"first_room\": \"treasure\"}\n}\n\nvar todo_list: Array = [\n    \"Explore the cabin\",\n    \"Find the cave entrance\",\n    \"Enter the cave\",\n    \"Reach the treasure room\"\n]\nYou start in a little cabin in the woods. You have a cave you can venture into, and at the end is treasure. This initial prototype serves as a simple introduction to the game’s mechanics and environment.\n\n\n\nvar princess_strategic_memories: Dictionary = {\n    \"is_at\": {\"princess\": \"royal cabin\"},\n    \"has_goal\": {\"princess\": \"retrieve treasure from the cave\"},\n    \"preparation_status\": {\"princess\": \"not_started\"}\n}\n\nvar princess_strategic_plan: Array = [\n    \"Set goal to retrieve treasure from the cave\",\n    \"Prepare for the journey\"\n]\n\nvar princess_tactical_memories: Dictionary = {\n    \"is_at\": {\"princess\": \"royal cabin\"},\n    \"knows_location\": {\"princess\": [\"royal cabin\", \"cave entrance\"]},\n    \"route_planned\": {\"princess\": false}\n}\n\nvar princess_tactical_plan: Array = [\n    \"Move to the royal cabin\",\n    \"Locate the cave entrance\",\n    \"Plan route through the cave to the treasure room\"\n]\n\nvar princess_operational_memories: Dictionary = {\n    \"is_at\": {\"princess\": \"royal cabin\"},\n    \"visited\": {\"princess\": []},\n    \"contains\": {\"first_room\": \"treasure\"}\n}\n\nvar princess_operational_plan: Array = [\n    \"Gather supplies for the journey\",\n    \"Travel to the cave entrance\",\n    \"Wait for the adventurer\",\n    \"Provide support from outside the cave\",\n    \"Receive the treasure from the adventurer\"\n]\n\nvar adventurer_tactical_memories: Dictionary = {\n    \"is_at\": {\"adventurer\": \"adventurer's cabin\"},\n    \"knows_location\": {\"adventurer\": [\"adventurer's cabin\", \"cave entrance\"]},\n    \"route_planned\": {\"adventurer\": false}\n}\n\nvar adventurer_tactical_plan: Array = [\n    \"Move to the adventurer's cabin\",\n    \"Locate the cave entrance\",\n    \"Plan route through the cave to the treasure room\"\n]\n\nvar adventurer_operational_memories: Dictionary = {\n    \"is_at\": {\"adventurer\": \"adventurer's cabin\"},\n    \"visited\": {\"adventurer\": []},\n    \"contains\": {\"first_room\": \"treasure\"}\n}\n\nvar adventurer_operational_plan: Array = [\n    \"Walk to the adventurer's cabin\",\n    \"Search for the cave entrance\",\n    \"Enter the cave\",\n    \"Navigate to the first room\",\n    \"Collect the treasure\",\n    \"Return to the cave entrance and hand over the treasure to the princess\"\n]\nIn the initial prototype, you explore the cave yourself. In “V-Sekai: My Life as a Princess,” you will reverse this concept by taking on the role of the princess who supplies adventurers with instructions to explore the cave and retrieve treasures. This shift from direct exploration to strategic management aligns with the relaxation theme."
+    "text": "V-Sekai\nDetail Tweaker\nInstructBLIP: Towards General-purpose Vision-Language Models with Instruction Tuning\nPetals"
   },
   {
-    "objectID": "decisions/20240708-vsekai-my-life-as-a-queen.html#the-benefits",
-    "href": "decisions/20240708-vsekai-my-life-as-a-queen.html#the-benefits",
-    "title": "Proposed: V-Sekai: My Life as a Princess",
+    "objectID": "decisions/20231108-neon-vercel-functions-toy-problem.html",
+    "href": "decisions/20231108-neon-vercel-functions-toy-problem.html",
+    "title": "Proposed: Development of a Community Polling Discord Bot Using Vercel and Neon PostgreSQL",
     "section": "",
-    "text": "Relaxing Gameplay: Focuses on non-combat activities like building, gardening, organizing events, and sending adventurers on quests.\nImmersive Experience: Utilizes VRM technology for customizable avatars and Godot’s XR capabilities for an engaging experience.\nDynamic Task Management: The HTN planner ensures that tasks are generated based on player actions, providing a unique experience each time."
+    "text": "Status: Proposed\nDeciders: V-Sekai Technical Team\nTags: Discord, Polling, Vercel, Serverless, PostgreSQL, Neon, Reactions, Community Engagement\n\n\n\n\nV-Sekai is aiming to boost community engagement by implementing interactive polling through Discord. The objective is to create a polling system where users can vote via reactions, and the results are managed in real-time.\n\n\n\nHow can V-Sekai develop a Discord bot that facilitates community polls using message reactions and records the results in a Neon-managed PostgreSQL database in a serverless environment?\n\n\n\n\nConstruct a Discord bot deployed on Vercel that can post poll messages with emoji reactions for voting.\nMonitor reaction additions and removals on these messages to count votes.\nIntegrate with Neon’s PostgreSQL database to store and update poll data, ensuring one vote per user.\nProvide real-time feedback and results tallying through the Discord bot.\n\n\n\n\n\nEngages the community in decision-making processes with interactive polls.\nGathers real-time data on community preferences and opinions.\nDemonstrates the real-time data handling capabilities of serverless functions and PostgreSQL databases.\n\n\n\n\n\nAdditional complexity in reaction event handling and vote deduplication.\nEnsuring database performance under high concurrency during active polls.\n\n\n\n\n\nUsing traditional polling methods without leveraging Discord’s interactive capabilities.\nReliance on external polling services that may not integrate seamlessly with Discord or offer real-time updates.\n\n\n\n\n\nDetailed analysis of voting patterns over time, which may require complex database queries.\n\n\n\n\n\nYes, the implementation of the Community Polling Discord bot using Neon’s PostgreSQL service will be developed and maintained internally as part of V-Sekai’s commitment to interactive community engagement.\n\n\n\n\n\nDiscord Bots: An Introduction\nVercel Serverless Functions\nNeon’s PostgreSQL Edge Capabilities\n\nThis strategy was formulated with AI assistance."
   },
   {
-    "objectID": "decisions/20240708-vsekai-my-life-as-a-queen.html#the-downsides",
-    "href": "decisions/20240708-vsekai-my-life-as-a-queen.html#the-downsides",
-    "title": "Proposed: V-Sekai: My Life as a Princess",
+    "objectID": "decisions/20231108-neon-vercel-functions-toy-problem.html#metadata",
+    "href": "decisions/20231108-neon-vercel-functions-toy-problem.html#metadata",
+    "title": "Proposed: Development of a Community Polling Discord Bot Using Vercel and Neon PostgreSQL",
     "section": "",
-    "text": "Learning Curve: Players unfamiliar with resource management games may find it challenging initially.\nHardware Requirements: Requires a VR-capable device, which may limit accessibility."
+    "text": "Status: Proposed\nDeciders: V-Sekai Technical Team\nTags: Discord, Polling, Vercel, Serverless, PostgreSQL, Neon, Reactions, Community Engagement"
   },
   {
-    "objectID": "decisions/20240708-vsekai-my-life-as-a-queen.html#the-road-not-taken",
-    "href": "decisions/20240708-vsekai-my-life-as-a-queen.html#the-road-not-taken",
-    "title": "Proposed: V-Sekai: My Life as a Princess",
+    "objectID": "decisions/20231108-neon-vercel-functions-toy-problem.html#the-backdrop",
+    "href": "decisions/20231108-neon-vercel-functions-toy-problem.html#the-backdrop",
+    "title": "Proposed: Development of a Community Polling Discord Bot Using Vercel and Neon PostgreSQL",
     "section": "",
-    "text": "Combat Mechanics: Instead of focusing on relaxation, we could have included combat elements, but this would detract from the theme of relaxation.\nLinear Storyline: A fixed storyline could have been implemented, but dynamic task generation offers more replayability."
+    "text": "V-Sekai is aiming to boost community engagement by implementing interactive polling through Discord. The objective is to create a polling system where users can vote via reactions, and the results are managed in real-time."
   },
   {
-    "objectID": "decisions/20240708-vsekai-my-life-as-a-queen.html#the-infrequent-use-case",
-    "href": "decisions/20240708-vsekai-my-life-as-a-queen.html#the-infrequent-use-case",
-    "title": "Proposed: V-Sekai: My Life as a Princess",
+    "objectID": "decisions/20231108-neon-vercel-functions-toy-problem.html#the-challenge",
+    "href": "decisions/20231108-neon-vercel-functions-toy-problem.html#the-challenge",
+    "title": "Proposed: Development of a Community Polling Discord Bot Using Vercel and Neon PostgreSQL",
     "section": "",
-    "text": "Seasonal Events: While the game includes various activities, seasonal events such as festivals or special quests tied to real-world holidays are not included. These could add variety but would require additional development time and resources."
+    "text": "How can V-Sekai develop a Discord bot that facilitates community polls using message reactions and records the results in a Neon-managed PostgreSQL database in a serverless environment?"
   },
   {
-    "objectID": "decisions/20240708-vsekai-my-life-as-a-queen.html#in-core-and-done-by-us",
-    "href": "decisions/20240708-vsekai-my-life-as-a-queen.html#in-core-and-done-by-us",
-    "title": "Proposed: V-Sekai: My Life as a Princess",
+    "objectID": "decisions/20231108-neon-vercel-functions-toy-problem.html#the-strategy",
+    "href": "decisions/20231108-neon-vercel-functions-toy-problem.html#the-strategy",
+    "title": "Proposed: Development of a Community Polling Discord Bot Using Vercel and Neon PostgreSQL",
     "section": "",
-    "text": "Core Development: The V-Sekai development team will handle all core aspects of the game, including coding, art, and design.\nCommunity Contributions: Open to contributions from the Godot XR community for additional content and features."
+    "text": "Construct a Discord bot deployed on Vercel that can post poll messages with emoji reactions for voting.\nMonitor reaction additions and removals on these messages to count votes.\nIntegrate with Neon’s PostgreSQL database to store and update poll data, ensuring one vote per user.\nProvide real-time feedback and results tallying through the Discord bot."
   },
   {
-    "objectID": "decisions/20240708-vsekai-my-life-as-a-queen.html#status",
-    "href": "decisions/20240708-vsekai-my-life-as-a-queen.html#status",
-    "title": "Proposed: V-Sekai: My Life as a Princess",
+    "objectID": "decisions/20231108-neon-vercel-functions-toy-problem.html#the-upside",
+    "href": "decisions/20231108-neon-vercel-functions-toy-problem.html#the-upside",
+    "title": "Proposed: Development of a Community Polling Discord Bot Using Vercel and Neon PostgreSQL",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "Engages the community in decision-making processes with interactive polls.\nGathers real-time data on community preferences and opinions.\nDemonstrates the real-time data handling capabilities of serverless functions and PostgreSQL databases."
   },
   {
-    "objectID": "decisions/20240708-vsekai-my-life-as-a-queen.html#decision-makers",
-    "href": "decisions/20240708-vsekai-my-life-as-a-queen.html#decision-makers",
-    "title": "Proposed: V-Sekai: My Life as a Princess",
+    "objectID": "decisions/20231108-neon-vercel-functions-toy-problem.html#the-downside",
+    "href": "decisions/20231108-neon-vercel-functions-toy-problem.html#the-downside",
+    "title": "Proposed: Development of a Community Polling Discord Bot Using Vercel and Neon PostgreSQL",
     "section": "",
-    "text": "V-Sekai development team\niFire\nBrune"
+    "text": "Additional complexity in reaction event handling and vote deduplication.\nEnsuring database performance under high concurrency during active polls."
   },
   {
-    "objectID": "decisions/20240708-vsekai-my-life-as-a-queen.html#tags",
-    "href": "decisions/20240708-vsekai-my-life-as-a-queen.html#tags",
-    "title": "Proposed: V-Sekai: My Life as a Princess",
+    "objectID": "decisions/20231108-neon-vercel-functions-toy-problem.html#the-road-not-taken",
+    "href": "decisions/20231108-neon-vercel-functions-toy-problem.html#the-road-not-taken",
+    "title": "Proposed: Development of a Community Polling Discord Bot Using Vercel and Neon PostgreSQL",
     "section": "",
-    "text": "V-Sekai\nGodot XR\nRelaxation\nVRM\nHTN Planner"
+    "text": "Using traditional polling methods without leveraging Discord’s interactive capabilities.\nReliance on external polling services that may not integrate seamlessly with Discord or offer real-time updates."
   },
   {
-    "objectID": "decisions/20240708-vsekai-my-life-as-a-queen.html#further-reading",
-    "href": "decisions/20240708-vsekai-my-life-as-a-queen.html#further-reading",
-    "title": "Proposed: V-Sekai: My Life as a Princess",
+    "objectID": "decisions/20231108-neon-vercel-functions-toy-problem.html#the-infrequent-use-case",
+    "href": "decisions/20231108-neon-vercel-functions-toy-problem.html#the-infrequent-use-case",
+    "title": "Proposed: Development of a Community Polling Discord Bot Using Vercel and Neon PostgreSQL",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nFinal Fantasy Crystal Chronicles: My Life as a King - A Lost WiiWare Classic [REFFOID]\nGodot XR Game Jam July 2024\nGridmap usage in Cassette Beasts\n\nAI assistant Aria assisted with this article."
+    "text": "Detailed analysis of voting patterns over time, which may require complex database queries."
   },
   {
-    "objectID": "decisions/20211031-meeting-area.html",
-    "href": "decisions/20211031-meeting-area.html",
-    "title": "Proposed: Meeting area",
+    "objectID": "decisions/20231108-neon-vercel-functions-toy-problem.html#in-core-and-done-by-us",
+    "href": "decisions/20231108-neon-vercel-functions-toy-problem.html#in-core-and-done-by-us",
+    "title": "Proposed: Development of a Community Polling Discord Bot Using Vercel and Neon PostgreSQL",
     "section": "",
-    "text": "Proposed: Meeting area\n\nContext and Problem Statement\nNeed a virtual world to meet.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nNeed to be in VR more.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nHub world with a glass whiteboard to do meetings with some private alcoves.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nCore\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nI know how this worlds\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Yes, the implementation of the Community Polling Discord bot using Neon’s PostgreSQL service will be developed and maintained internally as part of V-Sekai’s commitment to interactive community engagement."
   },
   {
-    "objectID": "decisions/20231201-headless-launcher-backend.html",
-    "href": "decisions/20231201-headless-launcher-backend.html",
-    "title": "Proposed: Headless Launcher Backend with Elixir and Server-Side CockroachDB",
+    "objectID": "decisions/20231108-neon-vercel-functions-toy-problem.html#further-reading",
+    "href": "decisions/20231108-neon-vercel-functions-toy-problem.html#further-reading",
+    "title": "Proposed: Development of a Community Polling Discord Bot Using Vercel and Neon PostgreSQL",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai Team\nTags: headless, backend, launcher, updater\n\n\n\n\nIntroduce a headless backend launcher to automate game updates for enhanced gaming experience.\n\n\n\nBuild an updater that is simple yet robust, handling automated game updates in the background.\n\n\n\nThe strategy for this proposal is to develop a headless backend launcher using Elixir and CockroachDB. The main components of the system will be:\nThe Headless CLI will implement desync for data synchronization and provide commands for displaying help information, version information, switching modes, checking current mode, listing all available modes, and updating according to semantic versioning.\nThe Updater Online Service will be a lightweight service that uses Elixir for handling web requests and CockroachDB for persistence. It will integrate the desync protocol and include error handling strategies for failed updates or data synchronization issues.\nThe GUI Launcher will be designed using the Godot Engine and will also integrate the desync protocol. It will feature a basic visual setup with V-Sekai branding.\nThe Game Sample will involve developing a basic visual sample with V-Sekai branding, planning for testing each component to ensure functionality, addressing security concerns including user data protection and secure updates, and discussing scalability potential with increasing users or larger game updates.\nEach table will have its own schema module representing different aspects of the application such as modes, versions, and update processes.\n\n\n\nThis system promotes seamless gaming with high performance and reliability from Elixir and CockroachDB.\n\n\n\nTechnology integration may lead to complex issues and compatibility challenges.\n\n\n\nExternal updaters and manual patches were dismissed for their demanding nature.\n\n\n\nDesign will allow manual update initiation for situations like limited bandwidth.\n\n\n\nThe V-Sekai team will develop and maintain this launcher backend. A detailed maintenance plan will be provided.\n\n\n\nA comprehensive documentation will be created for understanding the system and onboarding new team members.\n\n\n\n\nV-Sekai GitHub - Our efforts in VR using Godot Engine.\nV-Sekai Game Repo - Our open-source VR and social experiences project.\nDesync - Alternative casync implementation.\n\n\n\n\nstateDiagram-v2\n    [*] --&gt; Idle\n    Idle --&gt; CheckForUpdates : Update Triggered\n    CheckForUpdates --&gt; Updating\n    Updating --&gt; Idle : Update Successful\n\n    state CheckForUpdates {\n        [*] --&gt; Checking\n        Checking --&gt; NoUpdateFound\n        NoUpdateFound --&gt; [*]\n\n        Checking --&gt; UpdateAvailable\n        UpdateAvailable --&gt; PreparingUpdate\n        PreparingUpdate --&gt; DownloadingUpdate\n        DownloadingUpdate --&gt; ApplyingUpdate\n        ApplyingUpdate --&gt; FinalizingUpdate\n        FinalizingUpdate --&gt; UpdateSuccessful\n        UpdateSuccessful --&gt; [*]\n    }\n\n    Updating: Update in progress\n    Idle: Waiting for update trigger\nUse Elixir for concurrent services and CockroachDB on the server for data management:\n\nHeadless CLI\n\nImplement desync for data synchronization.\nDetail how desync will be integrated into the service and GUI.\n\n\n# Display help information\nvsekai --help\n\n# Display version information\nvsekai --version\n\n# Switch to a different mode. Modes allow different operations for the software.\nvsekai mode switch --mode_name stable\n\n# Check the current mode.\nvsekai mode current\n\n# List all available modes.\nvsekai mode list\n\n# Always updates according to semantic versioning to the mode.\n./headless-vsekai-v0.1.0.exe --update C:/v-sekai/launcher\n./headless-vsekai-v0.1.1.exe --update C:/v-sekai/launcher\n./headless-vsekai-v0.2.0.exe --update C:/v-sekai/launcher\n\n# Pseudo code for update process\ncheck_launcher_folder()\nvalidate_manifest_file_and_version()\nensure_correct_files_for_update()\ndownload_to_temp()\ndelete_old_and_move_over()\nsetup_registry_values()\n\nUpdater Online Service:\n\nCreate a lightweight updater service.\nUse Elixir for web requests handling.\nUtilize server-side CockroachDB for persistence.\nIntegrate desync protocol in the Service.\nInclude error handling strategy for failed updates or data synchronization issues.\n\nGUI Launcher Creation:\n\nDesign an intuitive Godot Engine GUI launcher.\nIntegrate desync protocol in the GUI.\nDetail the basic visual setup with V-Sekai branding.\n\nGame Setup Efforts:\n\nDevelop a basic visual setup with V-Sekai branding.\nInclude a plan for testing each component to ensure functionality.\nAddress security concerns, including user data protection and secure updates.\nDiscuss scalability potential with increasing users or larger game updates.\n\n\n\n\n\n\ndefmodule VSekaiNebula.Mode do\n  @moduledoc \"\"\"\n  This module represents the `modes` table in the application's database.\n\n  ## Fields\n\n  - `:name`: The name of the mode.\n  - `:is_active`: A boolean indicating whether the mode is active or not.\n  - `:update_to`: Updates to a different mode.\n  - `:id`: A unique identifier for each mode. It is autogenerated and serves as the primary key.\n  \"\"\"\n\n  use Ecto.Schema\n\n  schema \"modes\" do\n    field :name, :string\n    field :is_active, :bool\n    field :update_to, Ecto.UUID\n    field :id, Ecto.UUID, autogenerate: true, primary_key: true\n\n    timestamps()\n  end\n\n  # TODO changeset/2\nend\n\n\n\ndefmodule VSekaiNebula.Version do\n  @moduledoc \"\"\"\n  This module represents the `versions` table in the application's database.\n\n  ## Fields\n\n  - `:version`: The version number.\n  - `:skip_update`: A boolean indicating whether to skip the update or not.\n  - `:manifest_file_uri`: The URI of the manifest file. This is generated server-side to ensure integrity,\n    especially during CI/CD processes. It helps prevent issues such as network errors, mid-process failures,\n    or programming errors causing incorrect checksums or file locations.\n  - `:id`: A unique identifier for each version. It is autogenerated and serves as the primary key.\n\n  ## Associations\n\n  - belongs_to :mode, VSekaiNebula.Mode: Each version is associated with a mode.\n  \"\"\"\n\n  use Ecto.Schema\n\n  schema \"versions\" do\n    field :version, :string\n    field :skip_update, :bool\n    field :manifest_file_uri, :string\n    field :id, Ecto.UUID, autogenerate: true, primary_key: true\n\n    belongs_to :mode, VSekaiNebula.Mode\n\n    timestamps()\n  end\n\n  # TODO changeset/2\nend\n\n\n\ndefmodule VSekaiNebula.Files do\n  @moduledoc \"\"\"\n  This module represents the `files` table in the application's database.\n\n  ## Fields\n\n  - `:file_name`: The name of the file.\n  - `:file_uri`: The URI of the file.\n  - `:file_checksum_hash`: The checksum hash of the file.\n  - `:id`: A unique identifier for each file. It is autogenerated and serves as the primary key.\n\n  ## Associations\n\n  - belongs_to :version, VSekaiNebula.Version: Each file is associated with a version.\n\n  ## Reasoning\n\n  - Timestamps are removed as they are not necessary for this table. The files are static and do not change over time.\n  \"\"\"\n\n  use Ecto.Schema\n\n  schema \"files\" do\n    field :file_name, :string\n    field :file_uri, :string\n    field :file_checksum_hash, :string\n    field :id, Ecto.UUID, autogenerate: true, primary_key: true\n\n    belongs_to :version, VSekaiNebula.Version\n  end\n\n  # TODO changeset/2\nend\n\n\n\n\ndefmodule VSekaiNebula.CDN do\n  @moduledoc \"\"\"\n  This module represents the `cdn` table in the application's database.\n\n  ## Fields\n\n  - `:uid`: The unique identifier of the CDN.\n  - `:name`: The name of the CDN.\n  - `:uri`: The URI of the CDN.\n  - `:last_checked_on`: The date and time when the CDN was last checked. This field is necessary as the CDN details are checked regularly and we need to keep track of when they were last checked.\n  - `:region`: The region where the CDN is located.\n  - `:id`: A unique identifier for each CDN. It is autogenerated and serves as the primary key.\n\n  ## Reasoning\n\n  - Traditional timestamps (created_at, updated_at) are removed as they are not necessary for this table. The CDN details are static and do not change over time, except for the `:last_checked_on` field which is updated regularly.\n  \"\"\"\n\n  use Ecto.Schema\n\n  import Ecto.Changeset\n\n  schema \"cdn\" do\n    field :uid, :string\n    field :name, :string\n    field :uri, :string\n    field :last_checked_on, :utc_datetime\n    field :region, :string\n    field :id, Ecto.UUID, autogenerate: true, primary_key: true\n  end\n\n  # TODO changeset/2\nend"
+    "text": "Discord Bots: An Introduction\nVercel Serverless Functions\nNeon’s PostgreSQL Edge Capabilities\n\nThis strategy was formulated with AI assistance."
   },
   {
-    "objectID": "decisions/20231201-headless-launcher-backend.html#metadata",
-    "href": "decisions/20231201-headless-launcher-backend.html#metadata",
-    "title": "Proposed: Headless Launcher Backend with Elixir and Server-Side CockroachDB",
+    "objectID": "decisions/20230719-dual-databases-cockroachdb-khepri.html",
+    "href": "decisions/20230719-dual-databases-cockroachdb-khepri.html",
+    "title": "Proposed: Game simulation server sidekick process",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai Team\nTags: headless, backend, launcher, updater"
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, Godot Engine, khepri, elixir\n\n\n\n\nWe want to provide each game server a sidekick process that restarts Godot Engine on crash and acts as a local processor before upload to the source of truth backend database. This will ensure continuous gameplay and data integrity.\n\n\n\nWe propose to use khepri for sidekick server data with an elixir frontend.\nKhepri provides robustness and reliability while Elixir offers scalability and fault-tolerance.\n\n\n\n\nDevelop a sidekick process using khepri that monitors the Godot Engine.\nIn case of a crash, the sidekick process should be able to restart the Godot Engine.\nThe sidekick process should also act as a local processor for game data before it’s uploaded to the backend database.\nImplement an Elixir frontend to interact with the sidekick process.\n\n\n\n\n\nImproved game server stability.\nContinuous gameplay even in the event of a crash.\nEnsured data integrity before upload to the backend database.\n\n\n\n\n\nAdditional development time and resources required.\nPotential complexity in managing the sidekick process.\n\n\n\n\n\nUsing a simple watchdog script: A simple script that monitors the Godot Engine and restarts it in case of a crash. This was rejected due to its inability to act as a local processor for game data before upload.\nRelying on third-party services: There are several third-party services that offer process monitoring and automatic restarts. However, these were rejected due to potential issues with customization, cost, and data privacy.\nBuilding a custom solution from scratch: While this would give us the most control, it was deemed too resource-intensive and unnecessary given the existence of suitable tools like khepri and Elixir.\nDo nothing: The option to maintain the status quo was considered but ultimately rejected due to the negative impact on user experience and data integrity.\n\n\n\n\nNo, this enhancement is fundamental to the stability of the game servers and cannot be achieved with a simple script workaround.\n\n\n\nYes, as this directly impacts the user experience and the integrity of our game data, it is crucial that we have full control over its implementation and maintenance.\n\n\n\n\nV-Sekai"
   },
   {
-    "objectID": "decisions/20231201-headless-launcher-backend.html#backdrop",
-    "href": "decisions/20231201-headless-launcher-backend.html#backdrop",
-    "title": "Proposed: Headless Launcher Backend with Elixir and Server-Side CockroachDB",
+    "objectID": "decisions/20230719-dual-databases-cockroachdb-khepri.html#metadata",
+    "href": "decisions/20230719-dual-databases-cockroachdb-khepri.html#metadata",
+    "title": "Proposed: Game simulation server sidekick process",
     "section": "",
-    "text": "Introduce a headless backend launcher to automate game updates for enhanced gaming experience."
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, Godot Engine, khepri, elixir"
   },
   {
-    "objectID": "decisions/20231201-headless-launcher-backend.html#challenge",
-    "href": "decisions/20231201-headless-launcher-backend.html#challenge",
-    "title": "Proposed: Headless Launcher Backend with Elixir and Server-Side CockroachDB",
+    "objectID": "decisions/20230719-dual-databases-cockroachdb-khepri.html#context-and-problem-statement",
+    "href": "decisions/20230719-dual-databases-cockroachdb-khepri.html#context-and-problem-statement",
+    "title": "Proposed: Game simulation server sidekick process",
     "section": "",
-    "text": "Build an updater that is simple yet robust, handling automated game updates in the background."
+    "text": "We want to provide each game server a sidekick process that restarts Godot Engine on crash and acts as a local processor before upload to the source of truth backend database. This will ensure continuous gameplay and data integrity."
   },
   {
-    "objectID": "decisions/20231201-headless-launcher-backend.html#strategy",
-    "href": "decisions/20231201-headless-launcher-backend.html#strategy",
-    "title": "Proposed: Headless Launcher Backend with Elixir and Server-Side CockroachDB",
+    "objectID": "decisions/20230719-dual-databases-cockroachdb-khepri.html#proposed-solution",
+    "href": "decisions/20230719-dual-databases-cockroachdb-khepri.html#proposed-solution",
+    "title": "Proposed: Game simulation server sidekick process",
     "section": "",
-    "text": "The strategy for this proposal is to develop a headless backend launcher using Elixir and CockroachDB. The main components of the system will be:\nThe Headless CLI will implement desync for data synchronization and provide commands for displaying help information, version information, switching modes, checking current mode, listing all available modes, and updating according to semantic versioning.\nThe Updater Online Service will be a lightweight service that uses Elixir for handling web requests and CockroachDB for persistence. It will integrate the desync protocol and include error handling strategies for failed updates or data synchronization issues.\nThe GUI Launcher will be designed using the Godot Engine and will also integrate the desync protocol. It will feature a basic visual setup with V-Sekai branding.\nThe Game Sample will involve developing a basic visual sample with V-Sekai branding, planning for testing each component to ensure functionality, addressing security concerns including user data protection and secure updates, and discussing scalability potential with increasing users or larger game updates.\nEach table will have its own schema module representing different aspects of the application such as modes, versions, and update processes."
+    "text": "We propose to use khepri for sidekick server data with an elixir frontend.\nKhepri provides robustness and reliability while Elixir offers scalability and fault-tolerance."
   },
   {
-    "objectID": "decisions/20231201-headless-launcher-backend.html#upside",
-    "href": "decisions/20231201-headless-launcher-backend.html#upside",
-    "title": "Proposed: Headless Launcher Backend with Elixir and Server-Side CockroachDB",
+    "objectID": "decisions/20230719-dual-databases-cockroachdb-khepri.html#implementation",
+    "href": "decisions/20230719-dual-databases-cockroachdb-khepri.html#implementation",
+    "title": "Proposed: Game simulation server sidekick process",
     "section": "",
-    "text": "This system promotes seamless gaming with high performance and reliability from Elixir and CockroachDB."
+    "text": "Develop a sidekick process using khepri that monitors the Godot Engine.\nIn case of a crash, the sidekick process should be able to restart the Godot Engine.\nThe sidekick process should also act as a local processor for game data before it’s uploaded to the backend database.\nImplement an Elixir frontend to interact with the sidekick process."
   },
   {
-    "objectID": "decisions/20231201-headless-launcher-backend.html#downside",
-    "href": "decisions/20231201-headless-launcher-backend.html#downside",
-    "title": "Proposed: Headless Launcher Backend with Elixir and Server-Side CockroachDB",
+    "objectID": "decisions/20230719-dual-databases-cockroachdb-khepri.html#positive-consequences",
+    "href": "decisions/20230719-dual-databases-cockroachdb-khepri.html#positive-consequences",
+    "title": "Proposed: Game simulation server sidekick process",
     "section": "",
-    "text": "Technology integration may lead to complex issues and compatibility challenges."
+    "text": "Improved game server stability.\nContinuous gameplay even in the event of a crash.\nEnsured data integrity before upload to the backend database."
   },
   {
-    "objectID": "decisions/20231201-headless-launcher-backend.html#road-not-taken",
-    "href": "decisions/20231201-headless-launcher-backend.html#road-not-taken",
-    "title": "Proposed: Headless Launcher Backend with Elixir and Server-Side CockroachDB",
+    "objectID": "decisions/20230719-dual-databases-cockroachdb-khepri.html#negative-consequences",
+    "href": "decisions/20230719-dual-databases-cockroachdb-khepri.html#negative-consequences",
+    "title": "Proposed: Game simulation server sidekick process",
     "section": "",
-    "text": "External updaters and manual patches were dismissed for their demanding nature."
+    "text": "Additional development time and resources required.\nPotential complexity in managing the sidekick process."
   },
   {
-    "objectID": "decisions/20231201-headless-launcher-backend.html#infrequent-use-case",
-    "href": "decisions/20231201-headless-launcher-backend.html#infrequent-use-case",
-    "title": "Proposed: Headless Launcher Backend with Elixir and Server-Side CockroachDB",
+    "objectID": "decisions/20230719-dual-databases-cockroachdb-khepri.html#option-graveyard",
+    "href": "decisions/20230719-dual-databases-cockroachdb-khepri.html#option-graveyard",
+    "title": "Proposed: Game simulation server sidekick process",
     "section": "",
-    "text": "Design will allow manual update initiation for situations like limited bandwidth."
+    "text": "Using a simple watchdog script: A simple script that monitors the Godot Engine and restarts it in case of a crash. This was rejected due to its inability to act as a local processor for game data before upload.\nRelying on third-party services: There are several third-party services that offer process monitoring and automatic restarts. However, these were rejected due to potential issues with customization, cost, and data privacy.\nBuilding a custom solution from scratch: While this would give us the most control, it was deemed too resource-intensive and unnecessary given the existence of suitable tools like khepri and Elixir.\nDo nothing: The option to maintain the status quo was considered but ultimately rejected due to the negative impact on user experience and data integrity."
   },
   {
-    "objectID": "decisions/20231201-headless-launcher-backend.html#core-and-done-by-us",
-    "href": "decisions/20231201-headless-launcher-backend.html#core-and-done-by-us",
-    "title": "Proposed: Headless Launcher Backend with Elixir and Server-Side CockroachDB",
+    "objectID": "decisions/20230719-dual-databases-cockroachdb-khepri.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230719-dual-databases-cockroachdb-khepri.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Game simulation server sidekick process",
     "section": "",
-    "text": "The V-Sekai team will develop and maintain this launcher backend. A detailed maintenance plan will be provided."
+    "text": "No, this enhancement is fundamental to the stability of the game servers and cannot be achieved with a simple script workaround."
   },
   {
-    "objectID": "decisions/20231201-headless-launcher-backend.html#documentation",
-    "href": "decisions/20231201-headless-launcher-backend.html#documentation",
-    "title": "Proposed: Headless Launcher Backend with Elixir and Server-Side CockroachDB",
+    "objectID": "decisions/20230719-dual-databases-cockroachdb-khepri.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230719-dual-databases-cockroachdb-khepri.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Game simulation server sidekick process",
     "section": "",
-    "text": "A comprehensive documentation will be created for understanding the system and onboarding new team members."
+    "text": "Yes, as this directly impacts the user experience and the integrity of our game data, it is crucial that we have full control over its implementation and maintenance."
   },
   {
-    "objectID": "decisions/20231201-headless-launcher-backend.html#further-reading",
-    "href": "decisions/20231201-headless-launcher-backend.html#further-reading",
-    "title": "Proposed: Headless Launcher Backend with Elixir and Server-Side CockroachDB",
+    "objectID": "decisions/20230719-dual-databases-cockroachdb-khepri.html#references",
+    "href": "decisions/20230719-dual-databases-cockroachdb-khepri.html#references",
+    "title": "Proposed: Game simulation server sidekick process",
     "section": "",
-    "text": "V-Sekai GitHub - Our efforts in VR using Godot Engine.\nV-Sekai Game Repo - Our open-source VR and social experiences project.\nDesync - Alternative casync implementation."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20231201-headless-launcher-backend.html#code-snippets",
-    "href": "decisions/20231201-headless-launcher-backend.html#code-snippets",
-    "title": "Proposed: Headless Launcher Backend with Elixir and Server-Side CockroachDB",
-    "section": "",
-    "text": "stateDiagram-v2\n    [*] --&gt; Idle\n    Idle --&gt; CheckForUpdates : Update Triggered\n    CheckForUpdates --&gt; Updating\n    Updating --&gt; Idle : Update Successful\n\n    state CheckForUpdates {\n        [*] --&gt; Checking\n        Checking --&gt; NoUpdateFound\n        NoUpdateFound --&gt; [*]\n\n        Checking --&gt; UpdateAvailable\n        UpdateAvailable --&gt; PreparingUpdate\n        PreparingUpdate --&gt; DownloadingUpdate\n        DownloadingUpdate --&gt; ApplyingUpdate\n        ApplyingUpdate --&gt; FinalizingUpdate\n        FinalizingUpdate --&gt; UpdateSuccessful\n        UpdateSuccessful --&gt; [*]\n    }\n\n    Updating: Update in progress\n    Idle: Waiting for update trigger\nUse Elixir for concurrent services and CockroachDB on the server for data management:\n\nHeadless CLI\n\nImplement desync for data synchronization.\nDetail how desync will be integrated into the service and GUI.\n\n\n# Display help information\nvsekai --help\n\n# Display version information\nvsekai --version\n\n# Switch to a different mode. Modes allow different operations for the software.\nvsekai mode switch --mode_name stable\n\n# Check the current mode.\nvsekai mode current\n\n# List all available modes.\nvsekai mode list\n\n# Always updates according to semantic versioning to the mode.\n./headless-vsekai-v0.1.0.exe --update C:/v-sekai/launcher\n./headless-vsekai-v0.1.1.exe --update C:/v-sekai/launcher\n./headless-vsekai-v0.2.0.exe --update C:/v-sekai/launcher\n\n# Pseudo code for update process\ncheck_launcher_folder()\nvalidate_manifest_file_and_version()\nensure_correct_files_for_update()\ndownload_to_temp()\ndelete_old_and_move_over()\nsetup_registry_values()\n\nUpdater Online Service:\n\nCreate a lightweight updater service.\nUse Elixir for web requests handling.\nUtilize server-side CockroachDB for persistence.\nIntegrate desync protocol in the Service.\nInclude error handling strategy for failed updates or data synchronization issues.\n\nGUI Launcher Creation:\n\nDesign an intuitive Godot Engine GUI launcher.\nIntegrate desync protocol in the GUI.\nDetail the basic visual setup with V-Sekai branding.\n\nGame Setup Efforts:\n\nDevelop a basic visual setup with V-Sekai branding.\nInclude a plan for testing each component to ensure functionality.\nAddress security concerns, including user data protection and secure updates.\nDiscuss scalability potential with increasing users or larger game updates.\n\n\n\n\n\n\ndefmodule VSekaiNebula.Mode do\n  @moduledoc \"\"\"\n  This module represents the `modes` table in the application's database.\n\n  ## Fields\n\n  - `:name`: The name of the mode.\n  - `:is_active`: A boolean indicating whether the mode is active or not.\n  - `:update_to`: Updates to a different mode.\n  - `:id`: A unique identifier for each mode. It is autogenerated and serves as the primary key.\n  \"\"\"\n\n  use Ecto.Schema\n\n  schema \"modes\" do\n    field :name, :string\n    field :is_active, :bool\n    field :update_to, Ecto.UUID\n    field :id, Ecto.UUID, autogenerate: true, primary_key: true\n\n    timestamps()\n  end\n\n  # TODO changeset/2\nend\n\n\n\ndefmodule VSekaiNebula.Version do\n  @moduledoc \"\"\"\n  This module represents the `versions` table in the application's database.\n\n  ## Fields\n\n  - `:version`: The version number.\n  - `:skip_update`: A boolean indicating whether to skip the update or not.\n  - `:manifest_file_uri`: The URI of the manifest file. This is generated server-side to ensure integrity,\n    especially during CI/CD processes. It helps prevent issues such as network errors, mid-process failures,\n    or programming errors causing incorrect checksums or file locations.\n  - `:id`: A unique identifier for each version. It is autogenerated and serves as the primary key.\n\n  ## Associations\n\n  - belongs_to :mode, VSekaiNebula.Mode: Each version is associated with a mode.\n  \"\"\"\n\n  use Ecto.Schema\n\n  schema \"versions\" do\n    field :version, :string\n    field :skip_update, :bool\n    field :manifest_file_uri, :string\n    field :id, Ecto.UUID, autogenerate: true, primary_key: true\n\n    belongs_to :mode, VSekaiNebula.Mode\n\n    timestamps()\n  end\n\n  # TODO changeset/2\nend\n\n\n\ndefmodule VSekaiNebula.Files do\n  @moduledoc \"\"\"\n  This module represents the `files` table in the application's database.\n\n  ## Fields\n\n  - `:file_name`: The name of the file.\n  - `:file_uri`: The URI of the file.\n  - `:file_checksum_hash`: The checksum hash of the file.\n  - `:id`: A unique identifier for each file. It is autogenerated and serves as the primary key.\n\n  ## Associations\n\n  - belongs_to :version, VSekaiNebula.Version: Each file is associated with a version.\n\n  ## Reasoning\n\n  - Timestamps are removed as they are not necessary for this table. The files are static and do not change over time.\n  \"\"\"\n\n  use Ecto.Schema\n\n  schema \"files\" do\n    field :file_name, :string\n    field :file_uri, :string\n    field :file_checksum_hash, :string\n    field :id, Ecto.UUID, autogenerate: true, primary_key: true\n\n    belongs_to :version, VSekaiNebula.Version\n  end\n\n  # TODO changeset/2\nend\n\n\n\n\ndefmodule VSekaiNebula.CDN do\n  @moduledoc \"\"\"\n  This module represents the `cdn` table in the application's database.\n\n  ## Fields\n\n  - `:uid`: The unique identifier of the CDN.\n  - `:name`: The name of the CDN.\n  - `:uri`: The URI of the CDN.\n  - `:last_checked_on`: The date and time when the CDN was last checked. This field is necessary as the CDN details are checked regularly and we need to keep track of when they were last checked.\n  - `:region`: The region where the CDN is located.\n  - `:id`: A unique identifier for each CDN. It is autogenerated and serves as the primary key.\n\n  ## Reasoning\n\n  - Traditional timestamps (created_at, updated_at) are removed as they are not necessary for this table. The CDN details are static and do not change over time, except for the `:last_checked_on` field which is updated regularly.\n  \"\"\"\n\n  use Ecto.Schema\n\n  import Ecto.Changeset\n\n  schema \"cdn\" do\n    field :uid, :string\n    field :name, :string\n    field :uri, :string\n    field :last_checked_on, :utc_datetime\n    field :region, :string\n    field :id, Ecto.UUID, autogenerate: true, primary_key: true\n  end\n\n  # TODO changeset/2\nend"
-  },
-  {
-    "objectID": "decisions/20240217-documentation-guidelines.html",
-    "href": "decisions/20240217-documentation-guidelines.html",
-    "title": "Proposed: Comprehensive Documentation for V-Sekai",
+    "objectID": "decisions/20240611-test-1x-and-4x.html",
+    "href": "decisions/20240611-test-1x-and-4x.html",
+    "title": "Proposed: Managing Multiple Training Runs in Separate Pods",
     "section": "",
-    "text": "V-Sekai is a project that brings social VR/VRSNS/metaverse components to the Godot Engine. It has numerous features and topics that need comprehensive documentation for both developers and users.\n\n\n\nThe current documentation lacks detailed information about significant features and topics, making it difficult for users and developers to understand and utilize V-Sekai’s full potential.\n\n\n\nWe propose creating dedicated pages for each feature with descriptive titles and bullet lists of essential points. For instance:\n\n\n\nExplanation of XR and Godot\nHow XR works in Godot and how V-Sekai utilizes it\nAchievements possible with this feature/knowledge\nLimitations of the technology affecting our product\n\nFor step-by-step instructions, we will use straightforward language and consistent verbs and phrasing. For example:\n\n\n\n\nOpen the Project -&gt; Project Settings… menu.\nNavigate to Display -&gt; Window in the left column.\nScroll down to the resolution setting.\nClick the numbers to change the resolution (values are in pixels).\n\n\n\n\n\nThis proposal will make it easier for users and developers to understand and use V-Sekai. It will also provide a foundation for further development and improvements.\n\n\n\nCreating comprehensive documentation requires time and resources. However, the benefits outweigh the costs.\n\n\n\nWithout comprehensive documentation, users and developers may struggle to understand and use V-Sekai effectively.\n\n\n\nEven infrequent or advanced features should be documented to ensure all users can fully utilize V-Sekai.\n\n\n\nThis proposal will be implemented by the V-Sekai development team and community stakeholders.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team, community stakeholders, GDQuest, Fire\n\n\n\n\n\nV-Sekai, Avatar Customization, AI, Facial Expressions\n\n\n\n\n\nV-Sekai · GitHub\nV-Sekai/v-sekai-game\n\nAI assistant Aria assisted with this proposal."
+    "text": "We are working on training a model using multiple GPUs. We have encountered issues when trying to run two training runs in the same pod.\n\n\n\nThe problem is that we cannot run multiple GPU training runs in the same pod. This limits our ability to parallelize our training and make full use of our resources.\n\n\n\nBased on the discussion, the proposal is to manage the training runs in separate pods. Specifically:\n\nStart a pod with a single X1 4090 for stable training.\nStart another new pod with 4x 4090 to test the theory that you can only run the multi-GPU once per session.\n\n\n\n\n\nThis approach allows us to run multiple training runs simultaneously, making full use of our resources.\nIt also enables us to isolate the training runs, reducing the risk of one affecting the other.\n\n\n\n\n\nManaging multiple pods might be more complex than managing a single one.\nThere may be additional overhead associated with running multiple pods.\n\n\n\n\n\nWe could have continued trying to run multiple training runs in the same pod, but this was causing issues.\n\n\n\n\n\nThis approach may not be necessary if we only need to run a single training run at a time.\n\n\n\n\n\nThe decision on how to manage the pods and the training runs will be made by us, using our acquired resources and expertise.\n\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240217-documentation-guidelines.html#context",
-    "href": "decisions/20240217-documentation-guidelines.html#context",
-    "title": "Proposed: Comprehensive Documentation for V-Sekai",
+    "objectID": "decisions/20240611-test-1x-and-4x.html#the-context",
+    "href": "decisions/20240611-test-1x-and-4x.html#the-context",
+    "title": "Proposed: Managing Multiple Training Runs in Separate Pods",
     "section": "",
-    "text": "V-Sekai is a project that brings social VR/VRSNS/metaverse components to the Godot Engine. It has numerous features and topics that need comprehensive documentation for both developers and users."
+    "text": "We are working on training a model using multiple GPUs. We have encountered issues when trying to run two training runs in the same pod."
   },
   {
-    "objectID": "decisions/20240217-documentation-guidelines.html#problem-statement",
-    "href": "decisions/20240217-documentation-guidelines.html#problem-statement",
-    "title": "Proposed: Comprehensive Documentation for V-Sekai",
+    "objectID": "decisions/20240611-test-1x-and-4x.html#the-problem-statement",
+    "href": "decisions/20240611-test-1x-and-4x.html#the-problem-statement",
+    "title": "Proposed: Managing Multiple Training Runs in Separate Pods",
     "section": "",
-    "text": "The current documentation lacks detailed information about significant features and topics, making it difficult for users and developers to understand and utilize V-Sekai’s full potential."
+    "text": "The problem is that we cannot run multiple GPU training runs in the same pod. This limits our ability to parallelize our training and make full use of our resources."
   },
   {
-    "objectID": "decisions/20240217-documentation-guidelines.html#proposed-solution",
-    "href": "decisions/20240217-documentation-guidelines.html#proposed-solution",
-    "title": "Proposed: Comprehensive Documentation for V-Sekai",
+    "objectID": "decisions/20240611-test-1x-and-4x.html#proposal",
+    "href": "decisions/20240611-test-1x-and-4x.html#proposal",
+    "title": "Proposed: Managing Multiple Training Runs in Separate Pods",
     "section": "",
-    "text": "We propose creating dedicated pages for each feature with descriptive titles and bullet lists of essential points. For instance:\n\n\n\nExplanation of XR and Godot\nHow XR works in Godot and how V-Sekai utilizes it\nAchievements possible with this feature/knowledge\nLimitations of the technology affecting our product\n\nFor step-by-step instructions, we will use straightforward language and consistent verbs and phrasing. For example:\n\n\n\n\nOpen the Project -&gt; Project Settings… menu.\nNavigate to Display -&gt; Window in the left column.\nScroll down to the resolution setting.\nClick the numbers to change the resolution (values are in pixels)."
+    "text": "Based on the discussion, the proposal is to manage the training runs in separate pods. Specifically:\n\nStart a pod with a single X1 4090 for stable training.\nStart another new pod with 4x 4090 to test the theory that you can only run the multi-GPU once per session."
   },
   {
-    "objectID": "decisions/20240217-documentation-guidelines.html#benefits",
-    "href": "decisions/20240217-documentation-guidelines.html#benefits",
-    "title": "Proposed: Comprehensive Documentation for V-Sekai",
+    "objectID": "decisions/20240611-test-1x-and-4x.html#the-benefits",
+    "href": "decisions/20240611-test-1x-and-4x.html#the-benefits",
+    "title": "Proposed: Managing Multiple Training Runs in Separate Pods",
     "section": "",
-    "text": "This proposal will make it easier for users and developers to understand and use V-Sekai. It will also provide a foundation for further development and improvements."
+    "text": "This approach allows us to run multiple training runs simultaneously, making full use of our resources.\nIt also enables us to isolate the training runs, reducing the risk of one affecting the other."
   },
   {
-    "objectID": "decisions/20240217-documentation-guidelines.html#downsides",
-    "href": "decisions/20240217-documentation-guidelines.html#downsides",
-    "title": "Proposed: Comprehensive Documentation for V-Sekai",
+    "objectID": "decisions/20240611-test-1x-and-4x.html#the-downsides",
+    "href": "decisions/20240611-test-1x-and-4x.html#the-downsides",
+    "title": "Proposed: Managing Multiple Training Runs in Separate Pods",
     "section": "",
-    "text": "Creating comprehensive documentation requires time and resources. However, the benefits outweigh the costs."
+    "text": "Managing multiple pods might be more complex than managing a single one.\nThere may be additional overhead associated with running multiple pods."
   },
   {
-    "objectID": "decisions/20240217-documentation-guidelines.html#the-road-not-taken",
-    "href": "decisions/20240217-documentation-guidelines.html#the-road-not-taken",
-    "title": "Proposed: Comprehensive Documentation for V-Sekai",
+    "objectID": "decisions/20240611-test-1x-and-4x.html#the-road-not-taken",
+    "href": "decisions/20240611-test-1x-and-4x.html#the-road-not-taken",
+    "title": "Proposed: Managing Multiple Training Runs in Separate Pods",
     "section": "",
-    "text": "Without comprehensive documentation, users and developers may struggle to understand and use V-Sekai effectively."
+    "text": "We could have continued trying to run multiple training runs in the same pod, but this was causing issues."
   },
   {
-    "objectID": "decisions/20240217-documentation-guidelines.html#the-infrequent-use-case",
-    "href": "decisions/20240217-documentation-guidelines.html#the-infrequent-use-case",
-    "title": "Proposed: Comprehensive Documentation for V-Sekai",
+    "objectID": "decisions/20240611-test-1x-and-4x.html#the-infrequent-use-case",
+    "href": "decisions/20240611-test-1x-and-4x.html#the-infrequent-use-case",
+    "title": "Proposed: Managing Multiple Training Runs in Separate Pods",
     "section": "",
-    "text": "Even infrequent or advanced features should be documented to ensure all users can fully utilize V-Sekai."
+    "text": "This approach may not be necessary if we only need to run a single training run at a time."
   },
   {
-    "objectID": "decisions/20240217-documentation-guidelines.html#in-core-and-done-by-us",
-    "href": "decisions/20240217-documentation-guidelines.html#in-core-and-done-by-us",
-    "title": "Proposed: Comprehensive Documentation for V-Sekai",
+    "objectID": "decisions/20240611-test-1x-and-4x.html#in-core-and-done-by-us",
+    "href": "decisions/20240611-test-1x-and-4x.html#in-core-and-done-by-us",
+    "title": "Proposed: Managing Multiple Training Runs in Separate Pods",
     "section": "",
-    "text": "This proposal will be implemented by the V-Sekai development team and community stakeholders."
+    "text": "The decision on how to manage the pods and the training runs will be made by us, using our acquired resources and expertise."
   },
   {
-    "objectID": "decisions/20240217-documentation-guidelines.html#status",
-    "href": "decisions/20240217-documentation-guidelines.html#status",
-    "title": "Proposed: Comprehensive Documentation for V-Sekai",
+    "objectID": "decisions/20240611-test-1x-and-4x.html#status",
+    "href": "decisions/20240611-test-1x-and-4x.html#status",
+    "title": "Proposed: Managing Multiple Training Runs in Separate Pods",
     "section": "",
     "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20240217-documentation-guidelines.html#decision-makers",
-    "href": "decisions/20240217-documentation-guidelines.html#decision-makers",
-    "title": "Proposed: Comprehensive Documentation for V-Sekai",
+    "objectID": "decisions/20240611-test-1x-and-4x.html#decision-makers",
+    "href": "decisions/20240611-test-1x-and-4x.html#decision-makers",
+    "title": "Proposed: Managing Multiple Training Runs in Separate Pods",
     "section": "",
-    "text": "V-Sekai development team, community stakeholders, GDQuest, Fire"
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20240217-documentation-guidelines.html#tags",
-    "href": "decisions/20240217-documentation-guidelines.html#tags",
-    "title": "Proposed: Comprehensive Documentation for V-Sekai",
+    "objectID": "decisions/20240611-test-1x-and-4x.html#tags",
+    "href": "decisions/20240611-test-1x-and-4x.html#tags",
+    "title": "Proposed: Managing Multiple Training Runs in Separate Pods",
     "section": "",
-    "text": "V-Sekai, Avatar Customization, AI, Facial Expressions"
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20240217-documentation-guidelines.html#further-reading",
-    "href": "decisions/20240217-documentation-guidelines.html#further-reading",
-    "title": "Proposed: Comprehensive Documentation for V-Sekai",
+    "objectID": "decisions/20240611-test-1x-and-4x.html#further-reading",
+    "href": "decisions/20240611-test-1x-and-4x.html#further-reading",
+    "title": "Proposed: Managing Multiple Training Runs in Separate Pods",
     "section": "",
-    "text": "V-Sekai · GitHub\nV-Sekai/v-sekai-game\n\nAI assistant Aria assisted with this proposal."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20230819-train-game.html",
-    "href": "decisions/20230819-train-game.html",
-    "title": "Proposed: Following Tracks: Enhancing VR Train Station Simulation in V-Sekai using Godot Engine",
+    "objectID": "decisions/20240626-update-python3-macos-certicates.html",
+    "href": "decisions/20240626-update-python3-macos-certicates.html",
+    "title": "Proposed: Update python3 macOS Certificates",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, Godot Engine, VR Development\n\n\n\n\nV-Sekai is a platform that specializes in VR development with the Godot engine. It’s currently facing challenges because there isn’t a test game available. The goal is to develop a minimal viable product for a train station simulator. This simulator will focus on avatar rendering, networking simulation, and parented objects in the train.\n\n\n\nThe main problems are the need for precise controls in VR and the ability to render and network large groups of people in VR. This also includes extensive NPC tests with skeletal animation in the Godot engine for VR.\n\n\n\nThe strategy involves adding new features to V-Sekai to address these challenges:\n\nNetworking Avatar Crowds: The aim here is to develop efficient methods for networking large groups of avatars in VR. This will involve creating a system that can handle the high data traffic required for real-time interaction between numerous avatars, while maintaining performance and stability. This could be achieved by implementing advanced networking protocols and optimization techniques to ensure smooth communication between avatars without overloading the network.\n\n\n\n\nIf this strategy is implemented successfully, it could enhance the user experience in VR games developed using the Godot engine. It could also enable the creation of more diverse and complex VR environments.\n\n\n\nThis process may require significant resources and time, and there might be technical limitations.\n\n\n\nAn alternative could have been to use a different game engine that already supports these features. However, this wouldn’t contribute to the improvement of the Godot engine.\n\n\n\nThese improvements might not benefit all types of games or developers. Their relevance depends on the specific needs and goals of each project.\n\n\n\nV-Sekai’s expertise in VR development and understanding of its challenges make it well-suited to lead these improvements. By doing so, V-Sekai can align with developer needs, contribute to the open-source Godot engine, and help build a stronger community around it.\nDespite requiring effort and resources, the potential benefits for both V-Sekai and the wider Godot engine community make it a worthwhile investment.\n\n\n\n\nV-Sekai\nGodot Engine Proposal Discussion\n\nThis article is assisted by AI."
+    "text": "In the current scenario, all Python network certificates are not functioning as expected. This is causing a significant hindrance in the smooth execution of network-related tasks and operations.\n\n\n\nAll python network certificates don’t work on the Macos.\n\n\n\nHere is a Python script that installs or updates a set of default Root Certificates for the SSL module using the certificates provided by the certifi package:\n# Install_Certificates.command\n# install_certifi.py\n#\n# sample script to install or update a set of default Root Certificates\n# for the ssl module.  Uses the certificates provided by the certifi package:\n#       https://pypi.python.org/pypi/certifi\n\nimport os\nimport os.path\nimport ssl\nimport stat\nimport subprocess\nimport sys\n\nSTAT_0o775 = ( stat.S_IRUSR | stat.S_IWUSR | stat.S_IXUSR\n             | stat.S_IRGRP | stat.S_IWGRP | stat.S_IXGRP\n             | stat.S_IROTH |                stat.S_IXOTH )\n\n\ndef main():\n    openssl_dir, openssl_cafile = os.path.split(\n        ssl.get_default_verify_paths().openssl_cafile)\n\n    print(\" -- pip install --upgrade certifi\")\n    subprocess.check_call([sys.executable,\n        \"-E\", \"-s\", \"-m\", \"pip\", \"install\", \"--upgrade\", \"certifi\"])\n\n    import certifi\n\n    # change working directory to the default SSL directory\n    os.chdir(openssl_dir)\n    relpath_to_certifi_cafile = os.path.relpath(certifi.where())\n    print(\" -- removing any existing file or link\")\n    try:\n        os.remove(openssl_cafile)\n    except FileNotFoundError:\n        pass\n    print(\" -- creating symlink to certifi certificate bundle\")\n    os.symlink(relpath_to_certifi_cafile, openssl_cafile)\n    print(\" -- setting permissions\")\n    os.chmod(openssl_cafile, STAT_0o775)\n    print(\" -- update complete\")\n\nif __name__ == '__main__':\n    main()\n\n\n\nThe proposed solution will ensure that the Python network certificates are updated and functioning correctly. This will facilitate smooth network operations and tasks.\n\n\n\nThere might be some initial downtime during the update process. Also, any issues with the certifi package could potentially affect the certificate update process.\n\n\n\nAn alternative approach could have been to manually update each certificate. However, this would have been a time-consuming and error-prone process.\n\n\n\nThis solution may not be applicable for systems that do not use Python or where network certificates are managed differently.\n\n\n\nThe proposed solution is core to our operations as it directly impacts the functionality of our network operations. The implementation will be done by us, the V-Sekai development team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20230819-train-game.html#metadata",
-    "href": "decisions/20230819-train-game.html#metadata",
-    "title": "Proposed: Following Tracks: Enhancing VR Train Station Simulation in V-Sekai using Godot Engine",
+    "objectID": "decisions/20240626-update-python3-macos-certicates.html#the-context",
+    "href": "decisions/20240626-update-python3-macos-certicates.html#the-context",
+    "title": "Proposed: Update python3 macOS Certificates",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, Godot Engine, VR Development"
+    "text": "In the current scenario, all Python network certificates are not functioning as expected. This is causing a significant hindrance in the smooth execution of network-related tasks and operations."
   },
   {
-    "objectID": "decisions/20230819-train-game.html#the-backdrop",
-    "href": "decisions/20230819-train-game.html#the-backdrop",
-    "title": "Proposed: Following Tracks: Enhancing VR Train Station Simulation in V-Sekai using Godot Engine",
+    "objectID": "decisions/20240626-update-python3-macos-certicates.html#the-problem-statement",
+    "href": "decisions/20240626-update-python3-macos-certicates.html#the-problem-statement",
+    "title": "Proposed: Update python3 macOS Certificates",
     "section": "",
-    "text": "V-Sekai is a platform that specializes in VR development with the Godot engine. It’s currently facing challenges because there isn’t a test game available. The goal is to develop a minimal viable product for a train station simulator. This simulator will focus on avatar rendering, networking simulation, and parented objects in the train."
+    "text": "All python network certificates don’t work on the Macos."
   },
   {
-    "objectID": "decisions/20230819-train-game.html#the-challenge",
-    "href": "decisions/20230819-train-game.html#the-challenge",
-    "title": "Proposed: Following Tracks: Enhancing VR Train Station Simulation in V-Sekai using Godot Engine",
+    "objectID": "decisions/20240626-update-python3-macos-certicates.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240626-update-python3-macos-certicates.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Update python3 macOS Certificates",
     "section": "",
-    "text": "The main problems are the need for precise controls in VR and the ability to render and network large groups of people in VR. This also includes extensive NPC tests with skeletal animation in the Godot engine for VR."
+    "text": "Here is a Python script that installs or updates a set of default Root Certificates for the SSL module using the certificates provided by the certifi package:\n# Install_Certificates.command\n# install_certifi.py\n#\n# sample script to install or update a set of default Root Certificates\n# for the ssl module.  Uses the certificates provided by the certifi package:\n#       https://pypi.python.org/pypi/certifi\n\nimport os\nimport os.path\nimport ssl\nimport stat\nimport subprocess\nimport sys\n\nSTAT_0o775 = ( stat.S_IRUSR | stat.S_IWUSR | stat.S_IXUSR\n             | stat.S_IRGRP | stat.S_IWGRP | stat.S_IXGRP\n             | stat.S_IROTH |                stat.S_IXOTH )\n\n\ndef main():\n    openssl_dir, openssl_cafile = os.path.split(\n        ssl.get_default_verify_paths().openssl_cafile)\n\n    print(\" -- pip install --upgrade certifi\")\n    subprocess.check_call([sys.executable,\n        \"-E\", \"-s\", \"-m\", \"pip\", \"install\", \"--upgrade\", \"certifi\"])\n\n    import certifi\n\n    # change working directory to the default SSL directory\n    os.chdir(openssl_dir)\n    relpath_to_certifi_cafile = os.path.relpath(certifi.where())\n    print(\" -- removing any existing file or link\")\n    try:\n        os.remove(openssl_cafile)\n    except FileNotFoundError:\n        pass\n    print(\" -- creating symlink to certifi certificate bundle\")\n    os.symlink(relpath_to_certifi_cafile, openssl_cafile)\n    print(\" -- setting permissions\")\n    os.chmod(openssl_cafile, STAT_0o775)\n    print(\" -- update complete\")\n\nif __name__ == '__main__':\n    main()"
   },
   {
-    "objectID": "decisions/20230819-train-game.html#the-strategy",
-    "href": "decisions/20230819-train-game.html#the-strategy",
-    "title": "Proposed: Following Tracks: Enhancing VR Train Station Simulation in V-Sekai using Godot Engine",
+    "objectID": "decisions/20240626-update-python3-macos-certicates.html#the-benefits",
+    "href": "decisions/20240626-update-python3-macos-certicates.html#the-benefits",
+    "title": "Proposed: Update python3 macOS Certificates",
     "section": "",
-    "text": "The strategy involves adding new features to V-Sekai to address these challenges:\n\nNetworking Avatar Crowds: The aim here is to develop efficient methods for networking large groups of avatars in VR. This will involve creating a system that can handle the high data traffic required for real-time interaction between numerous avatars, while maintaining performance and stability. This could be achieved by implementing advanced networking protocols and optimization techniques to ensure smooth communication between avatars without overloading the network."
+    "text": "The proposed solution will ensure that the Python network certificates are updated and functioning correctly. This will facilitate smooth network operations and tasks."
   },
   {
-    "objectID": "decisions/20230819-train-game.html#the-upside",
-    "href": "decisions/20230819-train-game.html#the-upside",
-    "title": "Proposed: Following Tracks: Enhancing VR Train Station Simulation in V-Sekai using Godot Engine",
+    "objectID": "decisions/20240626-update-python3-macos-certicates.html#the-downsides",
+    "href": "decisions/20240626-update-python3-macos-certicates.html#the-downsides",
+    "title": "Proposed: Update python3 macOS Certificates",
     "section": "",
-    "text": "If this strategy is implemented successfully, it could enhance the user experience in VR games developed using the Godot engine. It could also enable the creation of more diverse and complex VR environments."
+    "text": "There might be some initial downtime during the update process. Also, any issues with the certifi package could potentially affect the certificate update process."
   },
   {
-    "objectID": "decisions/20230819-train-game.html#the-downside",
-    "href": "decisions/20230819-train-game.html#the-downside",
-    "title": "Proposed: Following Tracks: Enhancing VR Train Station Simulation in V-Sekai using Godot Engine",
+    "objectID": "decisions/20240626-update-python3-macos-certicates.html#the-road-not-taken",
+    "href": "decisions/20240626-update-python3-macos-certicates.html#the-road-not-taken",
+    "title": "Proposed: Update python3 macOS Certificates",
     "section": "",
-    "text": "This process may require significant resources and time, and there might be technical limitations."
+    "text": "An alternative approach could have been to manually update each certificate. However, this would have been a time-consuming and error-prone process."
   },
   {
-    "objectID": "decisions/20230819-train-game.html#the-road-not-taken",
-    "href": "decisions/20230819-train-game.html#the-road-not-taken",
-    "title": "Proposed: Following Tracks: Enhancing VR Train Station Simulation in V-Sekai using Godot Engine",
+    "objectID": "decisions/20240626-update-python3-macos-certicates.html#the-infrequent-use-case",
+    "href": "decisions/20240626-update-python3-macos-certicates.html#the-infrequent-use-case",
+    "title": "Proposed: Update python3 macOS Certificates",
     "section": "",
-    "text": "An alternative could have been to use a different game engine that already supports these features. However, this wouldn’t contribute to the improvement of the Godot engine."
+    "text": "This solution may not be applicable for systems that do not use Python or where network certificates are managed differently."
   },
   {
-    "objectID": "decisions/20230819-train-game.html#the-infrequent-use-case",
-    "href": "decisions/20230819-train-game.html#the-infrequent-use-case",
-    "title": "Proposed: Following Tracks: Enhancing VR Train Station Simulation in V-Sekai using Godot Engine",
+    "objectID": "decisions/20240626-update-python3-macos-certicates.html#in-core-and-done-by-us",
+    "href": "decisions/20240626-update-python3-macos-certicates.html#in-core-and-done-by-us",
+    "title": "Proposed: Update python3 macOS Certificates",
     "section": "",
-    "text": "These improvements might not benefit all types of games or developers. Their relevance depends on the specific needs and goals of each project."
+    "text": "The proposed solution is core to our operations as it directly impacts the functionality of our network operations. The implementation will be done by us, the V-Sekai development team."
   },
   {
-    "objectID": "decisions/20230819-train-game.html#in-core-and-done-by-us",
-    "href": "decisions/20230819-train-game.html#in-core-and-done-by-us",
-    "title": "Proposed: Following Tracks: Enhancing VR Train Station Simulation in V-Sekai using Godot Engine",
+    "objectID": "decisions/20240626-update-python3-macos-certicates.html#status",
+    "href": "decisions/20240626-update-python3-macos-certicates.html#status",
+    "title": "Proposed: Update python3 macOS Certificates",
     "section": "",
-    "text": "V-Sekai’s expertise in VR development and understanding of its challenges make it well-suited to lead these improvements. By doing so, V-Sekai can align with developer needs, contribute to the open-source Godot engine, and help build a stronger community around it.\nDespite requiring effort and resources, the potential benefits for both V-Sekai and the wider Godot engine community make it a worthwhile investment."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20230819-train-game.html#further-reading",
-    "href": "decisions/20230819-train-game.html#further-reading",
-    "title": "Proposed: Following Tracks: Enhancing VR Train Station Simulation in V-Sekai using Godot Engine",
+    "objectID": "decisions/20240626-update-python3-macos-certicates.html#decision-makers",
+    "href": "decisions/20240626-update-python3-macos-certicates.html#decision-makers",
+    "title": "Proposed: Update python3 macOS Certificates",
     "section": "",
-    "text": "V-Sekai\nGodot Engine Proposal Discussion\n\nThis article is assisted by AI."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20240717-core-vsekai-scripting.html",
-    "href": "decisions/20240717-core-vsekai-scripting.html",
-    "title": "Proposal: Core V-Sekai Scripting with Wasm",
+    "objectID": "decisions/20240626-update-python3-macos-certicates.html#tags",
+    "href": "decisions/20240626-update-python3-macos-certicates.html#tags",
+    "title": "Proposed: Update python3 macOS Certificates",
     "section": "",
-    "text": "The V-Sekai project aims to enhance the Godot Engine with social VR functionality. Currently, the project uses a forked version of the Godot Engine, which complicates development and maintenance due to frequent updates from the main Godot repository.\n\n\n\nThe V-Sekai team faces challenges with maintaining a forked version of the Godot Engine. Some team members prefer using the stock Godot Engine to avoid long compilation times and complex build processes. Additionally, there is a need for faster and more secure scripting capabilities than what GDScript offers.\n\n\n\nIf we move all core scripts to Wasm, we’ll need to make only one GDExtension, and then it will never change. So it will be one build that we can all share. We will only need to update when we want a new update from the main Godot Engine repository.\nIt might be hard, but encapsulating complex types is a bridge we’re going to have to cross no matter what.\nMMMaellon originally thought the reason why we want to move to Wasm is because the team doesn’t want to edit the C++ code. Perfectly matching the old API sounds really, really hard. But if we’re allowed to take shortcuts and figure out workarounds, MMMaellon thinks making a Wasm layer that allows us to do enough is doable. As long as the bar isn’t that it has to be an exact perfect replica of the old API.\nWe propose separating the core scripts into WebAssembly (Wasm) modules. This approach allows us to use the stock Godot Engine while leveraging the performance benefits of Wasm.\nThe core scripts will be loaded as Wasm modules, and a single GDExtension will handle the integration between Godot and the Wasm runtime.\n\n\n\nCore Scripts in Wasm: Move all core scripts to Wasm modules. These scripts will handle essential functionalities like security checks and editor tools.\nGDExtension for Wasm Integration: Develop a GDExtension that loads and executes the Wasm modules. This extension will act as a bridge between Godot and the Wasm runtime.\nSingle Binary Distribution: By using Wasm, we can distribute a single binary executable that includes the GDExtension and Wasm modules, simplifying the deployment process.\n\n\n\n\n\n\nPerformance: Wasm provides near-native performance, making it faster than GDScript.\nSecurity: Wasm’s sandboxed environment enhances security by isolating the execution of scripts.\nMaintainability: Using the stock Godot Engine reduces the burden of maintaining a forked version and simplifies updates.\nFlexibility: Developers can write core scripts in languages that compile to Wasm, such as C++ or Rust.\n\n\n\n\n\nComplexity: Developing and integrating Wasm modules adds complexity to the project.\nLearning Curve: Team members may need to learn new technologies and tools related to Wasm.\n\n\n\n\n\nSticking with Forked Godot: Continuing to use a forked version of Godot would require ongoing maintenance and could deter contributors.\nUsing Only GDExtension: While GDExtension provides native performance, it requires code signing and can be cumbersome to manage across multiple modules.\n\n\n\n\nIn scenarios where the performance and security benefits of Wasm are not critical, simpler scripting solutions like GDScript or native GDExtensions might suffice.\n\n\n\nThis proposal involves significant changes to the core architecture of the V-Sekai project. The development team will be responsible for implementing and maintaining the Wasm integration and GDExtension.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\nFire\nMMMaellon\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20240717-core-vsekai-scripting.html#the-context",
-    "href": "decisions/20240717-core-vsekai-scripting.html#the-context",
-    "title": "Proposal: Core V-Sekai Scripting with Wasm",
+    "objectID": "decisions/20240626-update-python3-macos-certicates.html#further-reading",
+    "href": "decisions/20240626-update-python3-macos-certicates.html#further-reading",
+    "title": "Proposed: Update python3 macOS Certificates",
     "section": "",
-    "text": "The V-Sekai project aims to enhance the Godot Engine with social VR functionality. Currently, the project uses a forked version of the Godot Engine, which complicates development and maintenance due to frequent updates from the main Godot repository."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240717-core-vsekai-scripting.html#the-problem-statement",
-    "href": "decisions/20240717-core-vsekai-scripting.html#the-problem-statement",
-    "title": "Proposal: Core V-Sekai Scripting with Wasm",
+    "objectID": "decisions/20231104-flatbuffer_packed_scenes.html",
+    "href": "decisions/20231104-flatbuffer_packed_scenes.html",
+    "title": "Rejected: Merge Scene Tool for Godot Editor with FlatBuffer-based JSON Serialization",
     "section": "",
-    "text": "The V-Sekai team faces challenges with maintaining a forked version of the Godot Engine. Some team members prefer using the stock Godot Engine to avoid long compilation times and complex build processes. Additionally, there is a need for faster and more secure scripting capabilities than what GDScript offers."
+    "text": "In collaborative projects, team members may edit the same scene in different ways. Version control systems (VCS) like Git can help manage these modifications through merging. However, merging scenes (TSCN format) can be challenging due to their complex semantics and potential for corruption.\n\n\n\nTo prevent scene corruption after merging, the Godot Editor should provide a merge scene window that allows users to merge TSCN files. This tool should:\n\nDetect Git merge conflict placeholders (&lt;&lt;&lt;&lt;&lt;&lt;&lt;, =======, &gt;&gt;&gt;&gt;&gt;&gt;&gt;)\nReconstruct local and remote scenes\nDisplay a merged scene tree with actions to accept or discard changes, or choose between local and remote versions\n\nThe merge tool should be intelligent enough to detect node movements, renaming, and other complex scene semantics. It should also allow users to edit the merged scene before saving it.\n\n\nTo ensure efficient serialization of the internal state of the merge tool at the start, in between, and at the end, FlatBuffer-based JSON should be used. This will allow for faster processing and better performance while maintaining human-readability.\n\n\n\n\nWhile this feature could be implemented as an add-on, a merge tool is a common feature in modern IDEs and should be fully integrated into the Godot Editor for a seamless user experience."
   },
   {
-    "objectID": "decisions/20240717-core-vsekai-scripting.html#proposed-solution",
-    "href": "decisions/20240717-core-vsekai-scripting.html#proposed-solution",
-    "title": "Proposal: Core V-Sekai Scripting with Wasm",
+    "objectID": "decisions/20231104-flatbuffer_packed_scenes.html#problem-merging-scenes-in-collaborative-projects",
+    "href": "decisions/20231104-flatbuffer_packed_scenes.html#problem-merging-scenes-in-collaborative-projects",
+    "title": "Rejected: Merge Scene Tool for Godot Editor with FlatBuffer-based JSON Serialization",
     "section": "",
-    "text": "If we move all core scripts to Wasm, we’ll need to make only one GDExtension, and then it will never change. So it will be one build that we can all share. We will only need to update when we want a new update from the main Godot Engine repository.\nIt might be hard, but encapsulating complex types is a bridge we’re going to have to cross no matter what.\nMMMaellon originally thought the reason why we want to move to Wasm is because the team doesn’t want to edit the C++ code. Perfectly matching the old API sounds really, really hard. But if we’re allowed to take shortcuts and figure out workarounds, MMMaellon thinks making a Wasm layer that allows us to do enough is doable. As long as the bar isn’t that it has to be an exact perfect replica of the old API.\nWe propose separating the core scripts into WebAssembly (Wasm) modules. This approach allows us to use the stock Godot Engine while leveraging the performance benefits of Wasm.\nThe core scripts will be loaded as Wasm modules, and a single GDExtension will handle the integration between Godot and the Wasm runtime.\n\n\n\nCore Scripts in Wasm: Move all core scripts to Wasm modules. These scripts will handle essential functionalities like security checks and editor tools.\nGDExtension for Wasm Integration: Develop a GDExtension that loads and executes the Wasm modules. This extension will act as a bridge between Godot and the Wasm runtime.\nSingle Binary Distribution: By using Wasm, we can distribute a single binary executable that includes the GDExtension and Wasm modules, simplifying the deployment process."
+    "text": "In collaborative projects, team members may edit the same scene in different ways. Version control systems (VCS) like Git can help manage these modifications through merging. However, merging scenes (TSCN format) can be challenging due to their complex semantics and potential for corruption."
   },
   {
-    "objectID": "decisions/20240717-core-vsekai-scripting.html#the-benefits",
-    "href": "decisions/20240717-core-vsekai-scripting.html#the-benefits",
-    "title": "Proposal: Core V-Sekai Scripting with Wasm",
+    "objectID": "decisions/20231104-flatbuffer_packed_scenes.html#solution-integrate-a-merge-scene-tool-in-godot-editor",
+    "href": "decisions/20231104-flatbuffer_packed_scenes.html#solution-integrate-a-merge-scene-tool-in-godot-editor",
+    "title": "Rejected: Merge Scene Tool for Godot Editor with FlatBuffer-based JSON Serialization",
     "section": "",
-    "text": "Performance: Wasm provides near-native performance, making it faster than GDScript.\nSecurity: Wasm’s sandboxed environment enhances security by isolating the execution of scripts.\nMaintainability: Using the stock Godot Engine reduces the burden of maintaining a forked version and simplifies updates.\nFlexibility: Developers can write core scripts in languages that compile to Wasm, such as C++ or Rust."
+    "text": "To prevent scene corruption after merging, the Godot Editor should provide a merge scene window that allows users to merge TSCN files. This tool should:\n\nDetect Git merge conflict placeholders (&lt;&lt;&lt;&lt;&lt;&lt;&lt;, =======, &gt;&gt;&gt;&gt;&gt;&gt;&gt;)\nReconstruct local and remote scenes\nDisplay a merged scene tree with actions to accept or discard changes, or choose between local and remote versions\n\nThe merge tool should be intelligent enough to detect node movements, renaming, and other complex scene semantics. It should also allow users to edit the merged scene before saving it.\n\n\nTo ensure efficient serialization of the internal state of the merge tool at the start, in between, and at the end, FlatBuffer-based JSON should be used. This will allow for faster processing and better performance while maintaining human-readability."
   },
   {
-    "objectID": "decisions/20240717-core-vsekai-scripting.html#the-downsides",
-    "href": "decisions/20240717-core-vsekai-scripting.html#the-downsides",
-    "title": "Proposal: Core V-Sekai Scripting with Wasm",
+    "objectID": "decisions/20231104-flatbuffer_packed_scenes.html#reason-for-core-integration",
+    "href": "decisions/20231104-flatbuffer_packed_scenes.html#reason-for-core-integration",
+    "title": "Rejected: Merge Scene Tool for Godot Editor with FlatBuffer-based JSON Serialization",
     "section": "",
-    "text": "Complexity: Developing and integrating Wasm modules adds complexity to the project.\nLearning Curve: Team members may need to learn new technologies and tools related to Wasm."
+    "text": "While this feature could be implemented as an add-on, a merge tool is a common feature in modern IDEs and should be fully integrated into the Godot Editor for a seamless user experience."
   },
   {
-    "objectID": "decisions/20240717-core-vsekai-scripting.html#the-road-not-taken",
-    "href": "decisions/20240717-core-vsekai-scripting.html#the-road-not-taken",
-    "title": "Proposal: Core V-Sekai Scripting with Wasm",
-    "section": "",
-    "text": "Sticking with Forked Godot: Continuing to use a forked version of Godot would require ongoing maintenance and could deter contributors.\nUsing Only GDExtension: While GDExtension provides native performance, it requires code signing and can be cumbersome to manage across multiple modules."
+    "objectID": "decisions/20231104-flatbuffer_packed_scenes.html#problem-limited-scene-file-format-options",
+    "href": "decisions/20231104-flatbuffer_packed_scenes.html#problem-limited-scene-file-format-options",
+    "title": "Rejected: Merge Scene Tool for Godot Editor with FlatBuffer-based JSON Serialization",
+    "section": "Problem: Limited Scene File Format Options",
+    "text": "Problem: Limited Scene File Format Options\nWhen working on a project related to Godot, such as game development or add-ons, you may encounter limitations with the current scene file formats:\n\nescn: For scenes created by external tools (e.g., importing from Blender)\nscn: Binary format, small but not very useful when collaborating on a project\ntscn: Textual format, INI/TOML-like syntax, human-readable, and encouraged for use\n\nThe TSCN format is proprietary and not widely used, leading to issues such as difficulty editing scenes outside of the Godot Editor and a lack of supporting tools like linters or syntax checkers."
   },
   {
-    "objectID": "decisions/20240717-core-vsekai-scripting.html#the-infrequent-use-case",
-    "href": "decisions/20240717-core-vsekai-scripting.html#the-infrequent-use-case",
-    "title": "Proposal: Core V-Sekai Scripting with Wasm",
-    "section": "",
-    "text": "In scenarios where the performance and security benefits of Wasm are not critical, simpler scripting solutions like GDScript or native GDExtensions might suffice."
+    "objectID": "decisions/20231104-flatbuffer_packed_scenes.html#solution-support-flatbuffer-based-json-as-an-alternative-human-readable-file-format",
+    "href": "decisions/20231104-flatbuffer_packed_scenes.html#solution-support-flatbuffer-based-json-as-an-alternative-human-readable-file-format",
+    "title": "Rejected: Merge Scene Tool for Godot Editor with FlatBuffer-based JSON Serialization",
+    "section": "Solution: Support FlatBuffer-based JSON as an Alternative Human-Readable File Format",
+    "text": "Solution: Support FlatBuffer-based JSON as an Alternative Human-Readable File Format\nTo overcome these limitations, it would be beneficial for Godot to support alternative human-readable file formats, such as FlatBuffer-based JSON. FlatBuffers provide a more efficient way to serialize and deserialize data compared to standard JSON while still being human-readable.\nThis feature should be part of the core engine to ensure official support and seamless integration.\nUse the extension FBJSCN."
   },
   {
-    "objectID": "decisions/20240717-core-vsekai-scripting.html#in-core-and-done-by-us",
-    "href": "decisions/20240717-core-vsekai-scripting.html#in-core-and-done-by-us",
-    "title": "Proposal: Core V-Sekai Scripting with Wasm",
+    "objectID": "decisions/20230125-provide-metadata-to-match-compatibile-maps-and-avatars.html",
+    "href": "decisions/20230125-provide-metadata-to-match-compatibile-maps-and-avatars.html",
+    "title": "Proposed: Provide metadata to pre-check if maps and avatars are compatible to load",
     "section": "",
-    "text": "This proposal involves significant changes to the core architecture of the V-Sekai project. The development team will be responsible for implementing and maintaining the Wasm integration and GDExtension."
+    "text": "Proposed: Provide metadata to pre-check if maps and avatars are compatible to load\n\nMetadata\n\nStatus: proposed \nDeciders: V-Sekai,fire,lyuma\nTags: V-Sekai,\n\n\n\nContext and Problem Statement\nWe don’t know which are maps and avatars are compatible to load.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\n\nAdd date and version number to maps list\n\nCan also be add xmp metadata packets to each packed scene.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nWhen the user presses launches the game, there should be no unnecessary steps.\n\n\nPositive Consequences\nIt is easier to pick content that is loadable.\n\n\nNegative Consequences\nWe cannot get other features in.\n\n\nOption graveyard\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\n\nthis requires a server change\nthis requires a godot engine change\n\n\n\nIs there a reason why this should be core and done by us?\nUsability is a core feature.\n\n\nReferences\n\nV-Sekai\nKHR_xmp_json_ld"
   },
   {
-    "objectID": "decisions/20240717-core-vsekai-scripting.html#status",
-    "href": "decisions/20240717-core-vsekai-scripting.html#status",
-    "title": "Proposal: Core V-Sekai Scripting with Wasm",
+    "objectID": "decisions/20211005-create-add-spring-bones-to-vrm-models.html",
+    "href": "decisions/20211005-create-add-spring-bones-to-vrm-models.html",
+    "title": "Proposed: Create a standard procedure from adding spring bones to VRM models.",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "Create a standard operating procedure from adding spring bones to VRM models.\n\n\n\nBy adding spring bones the body doesn’t clip through clothing or hair.\n\n\n\nSecondary is a node under the root.\nUse VRM Spring Bone Collider Group to stop spring bones from clipping with the skeleton.\nAdd the root bones of the armature you want to animate.\nIs it possible to generate a humanoid collider groups?\n\n\n\nInstructions are needed, automation is work.\n\n\n\nNo response\n\n\n\nNo response\n\n\n\nI don’t know and it’s in my area so I need to know.\n\n\n\n\nLyuma has an upside down spring bone arrangement to avoid flipping.\nhttps://gist.github.com/emilianavt/51d8399987d67544fdebfe2ebd9a5149\nhttps://sator-imaging.booth.pm/items/2254383\nhttps://github.com/yuzu-unity/HumanoidCollider/raw/master/HumanoidCollider.unitypackage\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240717-core-vsekai-scripting.html#decision-makers",
-    "href": "decisions/20240717-core-vsekai-scripting.html#decision-makers",
-    "title": "Proposal: Core V-Sekai Scripting with Wasm",
+    "objectID": "decisions/20211005-create-add-spring-bones-to-vrm-models.html#context-and-problem-statement",
+    "href": "decisions/20211005-create-add-spring-bones-to-vrm-models.html#context-and-problem-statement",
+    "title": "Proposed: Create a standard procedure from adding spring bones to VRM models.",
     "section": "",
-    "text": "V-Sekai development team\nFire\nMMMaellon"
+    "text": "Create a standard operating procedure from adding spring bones to VRM models."
   },
   {
-    "objectID": "decisions/20240717-core-vsekai-scripting.html#tags",
-    "href": "decisions/20240717-core-vsekai-scripting.html#tags",
-    "title": "Proposal: Core V-Sekai Scripting with Wasm",
+    "objectID": "decisions/20211005-create-add-spring-bones-to-vrm-models.html#describe-the-feature-enhancement-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20211005-create-add-spring-bones-to-vrm-models.html#describe-the-feature-enhancement-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: Create a standard procedure from adding spring bones to VRM models.",
     "section": "",
-    "text": "V-Sekai"
+    "text": "By adding spring bones the body doesn’t clip through clothing or hair."
   },
   {
-    "objectID": "decisions/20240717-core-vsekai-scripting.html#further-reading",
-    "href": "decisions/20240717-core-vsekai-scripting.html#further-reading",
-    "title": "Proposal: Core V-Sekai Scripting with Wasm",
+    "objectID": "decisions/20211005-create-add-spring-bones-to-vrm-models.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-andor-diagrams",
+    "href": "decisions/20211005-create-add-spring-bones-to-vrm-models.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-andor-diagrams",
+    "title": "Proposed: Create a standard procedure from adding spring bones to VRM models.",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "Secondary is a node under the root.\nUse VRM Spring Bone Collider Group to stop spring bones from clipping with the skeleton.\nAdd the root bones of the armature you want to animate.\nIs it possible to generate a humanoid collider groups?"
   },
   {
-    "objectID": "decisions/20221006-rename-to-main.html",
-    "href": "decisions/20221006-rename-to-main.html",
-    "title": "Proposed: Rename master to godot3 and main to godot4",
+    "objectID": "decisions/20211005-create-add-spring-bones-to-vrm-models.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20211005-create-add-spring-bones-to-vrm-models.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Create a standard procedure from adding spring bones to VRM models.",
     "section": "",
-    "text": "Status: proposed \nDeciders: V-Sekai,lyuma,fire\nTags: V-Sekai,\n\n\n\nNot all the branches are released and are currently named godot4. They should be renamed to main.\n\n\n\nRename all godot4 branches to be main for v-sekai-game.\n\n\n\niFire (he, him) — Today at 16:11\nneed some consensus. I think that given v-sekai-game has only one branch it should be named\nLyuma — Today at 16:11\nI agree provided we do the same with the submodules\n\n\n\n\ncohersion\n\n\n\n\n\nchange\n\n\n\n\n\nDo nothing.\n\n\n\n\nCode organization.\n\n\n\nWe own the repos.\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Instructions are needed, automation is work."
   },
   {
-    "objectID": "decisions/20221006-rename-to-main.html#context-and-problem-statement",
-    "href": "decisions/20221006-rename-to-main.html#context-and-problem-statement",
-    "title": "Proposed: Rename master to godot3 and main to godot4",
+    "objectID": "decisions/20211005-create-add-spring-bones-to-vrm-models.html#positive-consequences",
+    "href": "decisions/20211005-create-add-spring-bones-to-vrm-models.html#positive-consequences",
+    "title": "Proposed: Create a standard procedure from adding spring bones to VRM models.",
     "section": "",
-    "text": "Not all the branches are released and are currently named godot4. They should be renamed to main."
+    "text": "No response"
   },
   {
-    "objectID": "decisions/20221006-rename-to-main.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20221006-rename-to-main.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: Rename master to godot3 and main to godot4",
+    "objectID": "decisions/20211005-create-add-spring-bones-to-vrm-models.html#negative-consequences",
+    "href": "decisions/20211005-create-add-spring-bones-to-vrm-models.html#negative-consequences",
+    "title": "Proposed: Create a standard procedure from adding spring bones to VRM models.",
     "section": "",
-    "text": "Rename all godot4 branches to be main for v-sekai-game."
+    "text": "No response"
   },
   {
-    "objectID": "decisions/20221006-rename-to-main.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20221006-rename-to-main.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Rename master to godot3 and main to godot4",
+    "objectID": "decisions/20211005-create-add-spring-bones-to-vrm-models.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20211005-create-add-spring-bones-to-vrm-models.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Create a standard procedure from adding spring bones to VRM models.",
     "section": "",
-    "text": "iFire (he, him) — Today at 16:11\nneed some consensus. I think that given v-sekai-game has only one branch it should be named\nLyuma — Today at 16:11\nI agree provided we do the same with the submodules"
+    "text": "I don’t know and it’s in my area so I need to know."
   },
   {
-    "objectID": "decisions/20221006-rename-to-main.html#positive-consequences",
-    "href": "decisions/20221006-rename-to-main.html#positive-consequences",
-    "title": "Proposed: Rename master to godot3 and main to godot4",
+    "objectID": "decisions/20211005-create-add-spring-bones-to-vrm-models.html#references",
+    "href": "decisions/20211005-create-add-spring-bones-to-vrm-models.html#references",
+    "title": "Proposed: Create a standard procedure from adding spring bones to VRM models.",
     "section": "",
-    "text": "cohersion"
+    "text": "Lyuma has an upside down spring bone arrangement to avoid flipping.\nhttps://gist.github.com/emilianavt/51d8399987d67544fdebfe2ebd9a5149\nhttps://sator-imaging.booth.pm/items/2254383\nhttps://github.com/yuzu-unity/HumanoidCollider/raw/master/HumanoidCollider.unitypackage"
   },
   {
-    "objectID": "decisions/20221006-rename-to-main.html#negative-consequences",
-    "href": "decisions/20221006-rename-to-main.html#negative-consequences",
-    "title": "Proposed: Rename master to godot3 and main to godot4",
+    "objectID": "decisions/20211005-create-add-spring-bones-to-vrm-models.html#derivative-license",
+    "href": "decisions/20211005-create-add-spring-bones-to-vrm-models.html#derivative-license",
+    "title": "Proposed: Create a standard procedure from adding spring bones to VRM models.",
     "section": "",
-    "text": "change"
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20221006-rename-to-main.html#option-graveyard",
-    "href": "decisions/20221006-rename-to-main.html#option-graveyard",
-    "title": "Proposed: Rename master to godot3 and main to godot4",
+    "objectID": "decisions/20230527-organization.html",
+    "href": "decisions/20230527-organization.html",
+    "title": "Draft: Finding ways to attract users, developers, and creators sustaining V-Sekai",
     "section": "",
-    "text": "Do nothing."
+    "text": "Status: draft\nDeciders: V-Sekai, Bioblaze Payne, fire\nTags: V-Sekai, GPT-4\n\n\n\n\nV-Sekai is a project aimed at creating an open-source, federated virtual world platform. The main challenge faced by the V-Sekai project is to compete with established platforms like Roblox, which has a massive user base and a market valuation of $41 billion. The problem lies in finding ways to attract users, developers, and creators while maintaining a sustainable economic model.\n\n\n\nTo address the limitations of V-Sekai and make it competitive with platforms like Roblox, the following solutions are proposed:\n\nImplement a V-Sekai currency system: Convert fiat currency into in-game currency.\nCharge a fee for adding money into the system: This will help generate revenue for the platform and maintain its sustainability.\nCreators are paid directly for their content from V-Sekai.\nPrevent abuse and ensure fair distribution of resources.\n\n\n\n\n\nIntegrate a payment gateway to charge fees for adding money into the system.\nImplement usage limits for players and creators to ensure fair resource allocation.\nOffer creators a reward for their work.\n\n\n\n\n\nAttracting more creators and users to the platform\nGenerating revenue to sustain the platform’s growth\nEnsuring fair distribution of resources among users and creators\nEncouraging creators to have a fair share in the platform.\n\n\n\n\n\nPotential backlash from users due to fees and usage limits\nLegal complexities in treating creators fairly.\nBalancing the currency system to prevent inflation or deflation\n\n\n\n\nImplementing a single currency system: This option was discarded due to the potential for abuse and difficulty in balancing the economy.\n\n\n\nNo, the proposed solution requires significant changes to the platform’s core architecture and cannot be achieved through simple scripting.\n\n\n\nYes, the proposed solution addresses fundamental limitations of the V-Sekai project and is essential for its success. It requires deep integration with the platform’s core systems and should be implemented by the core development team.\n\n\n\n\nV-Sekai"
   },
   {
-    "objectID": "decisions/20221006-rename-to-main.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20221006-rename-to-main.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Rename master to godot3 and main to godot4",
+    "objectID": "decisions/20230527-organization.html#metadata",
+    "href": "decisions/20230527-organization.html#metadata",
+    "title": "Draft: Finding ways to attract users, developers, and creators sustaining V-Sekai",
     "section": "",
-    "text": "Code organization."
+    "text": "Status: draft\nDeciders: V-Sekai, Bioblaze Payne, fire\nTags: V-Sekai, GPT-4"
   },
   {
-    "objectID": "decisions/20221006-rename-to-main.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20221006-rename-to-main.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Rename master to godot3 and main to godot4",
+    "objectID": "decisions/20230527-organization.html#context-and-problem-statement",
+    "href": "decisions/20230527-organization.html#context-and-problem-statement",
+    "title": "Draft: Finding ways to attract users, developers, and creators sustaining V-Sekai",
     "section": "",
-    "text": "We own the repos."
+    "text": "V-Sekai is a project aimed at creating an open-source, federated virtual world platform. The main challenge faced by the V-Sekai project is to compete with established platforms like Roblox, which has a massive user base and a market valuation of $41 billion. The problem lies in finding ways to attract users, developers, and creators while maintaining a sustainable economic model."
   },
   {
-    "objectID": "decisions/20221006-rename-to-main.html#derivative-license",
-    "href": "decisions/20221006-rename-to-main.html#derivative-license",
-    "title": "Proposed: Rename master to godot3 and main to godot4",
+    "objectID": "decisions/20230527-organization.html#proposed-solution",
+    "href": "decisions/20230527-organization.html#proposed-solution",
+    "title": "Draft: Finding ways to attract users, developers, and creators sustaining V-Sekai",
     "section": "",
-    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "To address the limitations of V-Sekai and make it competitive with platforms like Roblox, the following solutions are proposed:\n\nImplement a V-Sekai currency system: Convert fiat currency into in-game currency.\nCharge a fee for adding money into the system: This will help generate revenue for the platform and maintain its sustainability.\nCreators are paid directly for their content from V-Sekai.\nPrevent abuse and ensure fair distribution of resources."
   },
   {
-    "objectID": "decisions/20230429-git-subrepo-challenges.html",
-    "href": "decisions/20230429-git-subrepo-challenges.html",
-    "title": "Accepted: Challenges in managing and synchronizing multiple assets and libraries across different git repositories",
+    "objectID": "decisions/20230527-organization.html#implementation",
+    "href": "decisions/20230527-organization.html#implementation",
+    "title": "Draft: Finding ways to attract users, developers, and creators sustaining V-Sekai",
     "section": "",
-    "text": "Accepted: Challenges in managing and synchronizing multiple assets and libraries across different git repositories\n\nMetadata\n\nStatus: accepted \nDeciders: V-Sekai,fire\nTags: V-Sekai,chatgpt4 summary,\n\n\n\nContext and Problem Statement\nV-Sekai projects currently face challenges in managing and synchronizing multiple assets and libraries across different branches. How can we improve the workflow to better maintain the project’s organization and compatibility?\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nImplement a Git subrepo management system to separate assets and libraries, enabling easier tracking and synchronization between branches. This solution streamlines the development process\n\n\nDescribe how your proposal will work with code, pseudo-code, mock-ups, or diagrams\nConfigure the Git subrepo to automatically update and synchronize with the main project.\nUse the Git subrepo in each branch to maintain consistent asset and library versions.\nAvoid storing godot and modules inside of the v-sekai-game.\n\n\nPositive Consequences\n\nImproved organization and compatibility of assets and libraries across branches.\nSimplified workflow for project updates and synchronization.\n\n\n\nNegative Consequences\n\nPotential learning curve for developers unfamiliar with Git subrepo management.\nPossible limitations in implementing other features.\n\n\n\nOption graveyard\nWorkarounds using scripts may be possible, but they are likely to be less efficient and more prone to errors compared to a Git subrepo management system.\n\n\nIf this enhancement will be used infrequently, can it be worked around with a few lines of script?\nNot a few lines of code. It is also devops.\n\n\nIs there a reason why this should be core and done by us?\nIntegrating a Git subrepo management system as a core feature ensures consistency and maintainability across the entire V-Sekai project. It promotes better collaboration among team members and streamlines the development process.\n\n\nReferences\n\nV-Sekai\nGit Subrepo Documentation"
+    "text": "Integrate a payment gateway to charge fees for adding money into the system.\nImplement usage limits for players and creators to ensure fair resource allocation.\nOffer creators a reward for their work."
   },
   {
-    "objectID": "decisions/20231108-postgres-bytea-optimizations.html",
-    "href": "decisions/20231108-postgres-bytea-optimizations.html",
-    "title": "Proposed: PostgreSQL bytea Storage Optimization for V-Sekai’s Edge CDN",
+    "objectID": "decisions/20230527-organization.html#positive-consequences",
+    "href": "decisions/20230527-organization.html#positive-consequences",
+    "title": "Draft: Finding ways to attract users, developers, and creators sustaining V-Sekai",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai, Fire\nTags: V-Sekai, PostgreSQL, Edge Hosting, CDN, bytea, TOAST, Optimization\n\n\n\n\nV-Sekai maintains an open-source CDN platform and seeks database optimizations for better performance and scalability.\n\n\n\nHow can V-Sekai enhance binary data storage and access by leveraging PostgreSQL’s bytea type with EXTERNAL storage, independent of Neon’s bottomless feature?\n\n\n\nOptimize the PostgreSQL database schema for CDN data by setting bytea columns to use EXTERNAL storage. This facilitates out-of-line and uncompressed storage of binary data, improving read performance and enabling streaming capabilities.\n\n\n\n\nReduced CPU usage by bypassing compression for binary data.\nEfficient access to specific data segments without loading entire objects, beneficial for streaming content.\n\n\n\n\n\nComplexity in managing custom TOAST configurations.\nNeed for precise database management to ensure performance gains.\n\n\n\n\nDefaulting to the EXTENDED storage type, which compresses bytea data but may not be as efficient for V-Sekai’s use case.\n\n\n\nScenarios requiring compressed storage for binary data, where the EXTENDED storage type might be more appropriate.\n\n\n\nThe PostgreSQL optimization will be implemented by V-Sekai’s team as a crucial part of our infrastructure enhancements.\n\n\n\n\nV-Sekai on GitHub\nBinary Data Performance in PostgreSQL - CYBERTEC​【oaicite:0】​\n\nThis article was assisted by AI."
+    "text": "Attracting more creators and users to the platform\nGenerating revenue to sustain the platform’s growth\nEnsuring fair distribution of resources among users and creators\nEncouraging creators to have a fair share in the platform."
   },
   {
-    "objectID": "decisions/20231108-postgres-bytea-optimizations.html#metadata",
-    "href": "decisions/20231108-postgres-bytea-optimizations.html#metadata",
-    "title": "Proposed: PostgreSQL bytea Storage Optimization for V-Sekai’s Edge CDN",
+    "objectID": "decisions/20230527-organization.html#negative-consequences",
+    "href": "decisions/20230527-organization.html#negative-consequences",
+    "title": "Draft: Finding ways to attract users, developers, and creators sustaining V-Sekai",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai, Fire\nTags: V-Sekai, PostgreSQL, Edge Hosting, CDN, bytea, TOAST, Optimization"
+    "text": "Potential backlash from users due to fees and usage limits\nLegal complexities in treating creators fairly.\nBalancing the currency system to prevent inflation or deflation"
   },
   {
-    "objectID": "decisions/20231108-postgres-bytea-optimizations.html#the-backdrop",
-    "href": "decisions/20231108-postgres-bytea-optimizations.html#the-backdrop",
-    "title": "Proposed: PostgreSQL bytea Storage Optimization for V-Sekai’s Edge CDN",
+    "objectID": "decisions/20230527-organization.html#option-graveyard",
+    "href": "decisions/20230527-organization.html#option-graveyard",
+    "title": "Draft: Finding ways to attract users, developers, and creators sustaining V-Sekai",
     "section": "",
-    "text": "V-Sekai maintains an open-source CDN platform and seeks database optimizations for better performance and scalability."
+    "text": "Implementing a single currency system: This option was discarded due to the potential for abuse and difficulty in balancing the economy."
   },
   {
-    "objectID": "decisions/20231108-postgres-bytea-optimizations.html#the-challenge",
-    "href": "decisions/20231108-postgres-bytea-optimizations.html#the-challenge",
-    "title": "Proposed: PostgreSQL bytea Storage Optimization for V-Sekai’s Edge CDN",
+    "objectID": "decisions/20230527-organization.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230527-organization.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Draft: Finding ways to attract users, developers, and creators sustaining V-Sekai",
     "section": "",
-    "text": "How can V-Sekai enhance binary data storage and access by leveraging PostgreSQL’s bytea type with EXTERNAL storage, independent of Neon’s bottomless feature?"
+    "text": "No, the proposed solution requires significant changes to the platform’s core architecture and cannot be achieved through simple scripting."
   },
   {
-    "objectID": "decisions/20231108-postgres-bytea-optimizations.html#the-strategy",
-    "href": "decisions/20231108-postgres-bytea-optimizations.html#the-strategy",
-    "title": "Proposed: PostgreSQL bytea Storage Optimization for V-Sekai’s Edge CDN",
+    "objectID": "decisions/20230527-organization.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230527-organization.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Draft: Finding ways to attract users, developers, and creators sustaining V-Sekai",
     "section": "",
-    "text": "Optimize the PostgreSQL database schema for CDN data by setting bytea columns to use EXTERNAL storage. This facilitates out-of-line and uncompressed storage of binary data, improving read performance and enabling streaming capabilities."
+    "text": "Yes, the proposed solution addresses fundamental limitations of the V-Sekai project and is essential for its success. It requires deep integration with the platform’s core systems and should be implemented by the core development team."
   },
   {
-    "objectID": "decisions/20231108-postgres-bytea-optimizations.html#the-upside",
-    "href": "decisions/20231108-postgres-bytea-optimizations.html#the-upside",
-    "title": "Proposed: PostgreSQL bytea Storage Optimization for V-Sekai’s Edge CDN",
+    "objectID": "decisions/20230527-organization.html#references",
+    "href": "decisions/20230527-organization.html#references",
+    "title": "Draft: Finding ways to attract users, developers, and creators sustaining V-Sekai",
     "section": "",
-    "text": "Reduced CPU usage by bypassing compression for binary data.\nEfficient access to specific data segments without loading entire objects, beneficial for streaming content."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20231108-postgres-bytea-optimizations.html#the-downside",
-    "href": "decisions/20231108-postgres-bytea-optimizations.html#the-downside",
-    "title": "Proposed: PostgreSQL bytea Storage Optimization for V-Sekai’s Edge CDN",
+    "objectID": "decisions/20230509-wasm-data-exchange.html",
+    "href": "decisions/20230509-wasm-data-exchange.html",
+    "title": "Draft: Exchange data between Godot Engine and WASM using handles",
     "section": "",
-    "text": "Complexity in managing custom TOAST configurations.\nNeed for precise database management to ensure performance gains."
+    "text": "Status: draft \nDeciders: V-Sekai, fire, lyuma, ashtonmeuser\nTags: V-Sekai, ChatGPT-4\n\n\n\n\nV-Sekai faces a limitation in sending complex data types between the Godot Engine and WebAssembly (WASM) modules. Simple Variant types can be marshaled or copied onto the stack, but arrays, dictionaries, and Object types require a more efficient approach.\n\n\n\nImplement a handle-based approach for managing complex data types. Allocate handles, possibly reference counted, allowing the WASM guest to pass integers around to all the Godot APIs. This will enable efficient communication between the host side and the WASM guest.\n\n\n\n\nDesign a handle-based system for managing complex data types.\nImplement reference counting for allocated handles.\nAdd Godot APIs to accept integer handles instead of direct object references.\nTest the new implementation with various data types and scenarios.\n\n\n\n\n\nEfficient communication between the host side and the WASM guest.\nImproved performance when dealing with complex data types.\nSimplified API usage for developers.\n\n\n\n\n\nAdditional complexity in the implementation.\nPotential overhead due to reference counting.\n\n\n\n\nN/A\n\n\n\nNo, this enhancement addresses a core limitation and requires changes to the underlying system.\n\n\n\nYes, this enhancement improves the efficiency and usability of the V-Sekai platform, making it more attractive to developers and users.\n\n\n\n\nV-Sekai\nGodot Engine StreamPeer\nGodot Engine Wasm\nGodot Engine WasGo"
   },
   {
-    "objectID": "decisions/20231108-postgres-bytea-optimizations.html#the-road-not-taken",
-    "href": "decisions/20231108-postgres-bytea-optimizations.html#the-road-not-taken",
-    "title": "Proposed: PostgreSQL bytea Storage Optimization for V-Sekai’s Edge CDN",
+    "objectID": "decisions/20230509-wasm-data-exchange.html#metadata",
+    "href": "decisions/20230509-wasm-data-exchange.html#metadata",
+    "title": "Draft: Exchange data between Godot Engine and WASM using handles",
     "section": "",
-    "text": "Defaulting to the EXTENDED storage type, which compresses bytea data but may not be as efficient for V-Sekai’s use case."
+    "text": "Status: draft \nDeciders: V-Sekai, fire, lyuma, ashtonmeuser\nTags: V-Sekai, ChatGPT-4"
   },
   {
-    "objectID": "decisions/20231108-postgres-bytea-optimizations.html#the-infrequent-use-case",
-    "href": "decisions/20231108-postgres-bytea-optimizations.html#the-infrequent-use-case",
-    "title": "Proposed: PostgreSQL bytea Storage Optimization for V-Sekai’s Edge CDN",
+    "objectID": "decisions/20230509-wasm-data-exchange.html#context-and-problem-statement",
+    "href": "decisions/20230509-wasm-data-exchange.html#context-and-problem-statement",
+    "title": "Draft: Exchange data between Godot Engine and WASM using handles",
     "section": "",
-    "text": "Scenarios requiring compressed storage for binary data, where the EXTENDED storage type might be more appropriate."
+    "text": "V-Sekai faces a limitation in sending complex data types between the Godot Engine and WebAssembly (WASM) modules. Simple Variant types can be marshaled or copied onto the stack, but arrays, dictionaries, and Object types require a more efficient approach."
   },
   {
-    "objectID": "decisions/20231108-postgres-bytea-optimizations.html#in-core-and-done-by-us",
-    "href": "decisions/20231108-postgres-bytea-optimizations.html#in-core-and-done-by-us",
-    "title": "Proposed: PostgreSQL bytea Storage Optimization for V-Sekai’s Edge CDN",
+    "objectID": "decisions/20230509-wasm-data-exchange.html#proposed-solution",
+    "href": "decisions/20230509-wasm-data-exchange.html#proposed-solution",
+    "title": "Draft: Exchange data between Godot Engine and WASM using handles",
     "section": "",
-    "text": "The PostgreSQL optimization will be implemented by V-Sekai’s team as a crucial part of our infrastructure enhancements."
+    "text": "Implement a handle-based approach for managing complex data types. Allocate handles, possibly reference counted, allowing the WASM guest to pass integers around to all the Godot APIs. This will enable efficient communication between the host side and the WASM guest."
   },
   {
-    "objectID": "decisions/20231108-postgres-bytea-optimizations.html#further-reading",
-    "href": "decisions/20231108-postgres-bytea-optimizations.html#further-reading",
-    "title": "Proposed: PostgreSQL bytea Storage Optimization for V-Sekai’s Edge CDN",
+    "objectID": "decisions/20230509-wasm-data-exchange.html#implementation",
+    "href": "decisions/20230509-wasm-data-exchange.html#implementation",
+    "title": "Draft: Exchange data between Godot Engine and WASM using handles",
     "section": "",
-    "text": "V-Sekai on GitHub\nBinary Data Performance in PostgreSQL - CYBERTEC​【oaicite:0】​\n\nThis article was assisted by AI."
+    "text": "Design a handle-based system for managing complex data types.\nImplement reference counting for allocated handles.\nAdd Godot APIs to accept integer handles instead of direct object references.\nTest the new implementation with various data types and scenarios."
   },
   {
-    "objectID": "decisions/20241011-recovering-makehuman-parameters.html",
-    "href": "decisions/20241011-recovering-makehuman-parameters.html",
-    "title": "Proposed: Recovering MakeHuman Parameters Using Depth Map Comparison with Godot Engine",
+    "objectID": "decisions/20230509-wasm-data-exchange.html#positive-consequences",
+    "href": "decisions/20230509-wasm-data-exchange.html#positive-consequences",
+    "title": "Draft: Exchange data between Godot Engine and WASM using handles",
     "section": "",
-    "text": "In the realm of digital animation and character modeling, fitting an avatar to a specific image can enhance personalization and realism in various applications such as gaming and virtual reality.\n\n\n\nThe challenge lies in accurately estimating the parameters of a MakeHuman model from a given anime-style image to ensure the avatar closely resembles the original character.\n\n\n\n\n\nWe propose a system that utilizes depth map comparisons between rendered images from the Godot Engine and depth maps generated from anime images using Apple’s ML-Depth-Pro. This approach aims to optimize the MakeHuman parameters to recreate accurate 3D models of anime characters.\n\n\n\nDepth Map Generation: Generate depth maps from both anime images and Godot-rendered characters.\nOptimization: Employ machine learning techniques to minimize the differences between these depth maps, facilitating accurate parameter recovery.\nCost Efficiency: Leverage open-source tools to maintain budget-friendliness.\n\n\n\n\n\nInput Data: Anime images with manually labeled MakeHuman parameters for initial calibration.\nDepth Comparison: Analyze the discrepancies between the depth maps produced by Godot and those derived from anime images.\nOptimization Process: Utilize a search algorithm (e.g., genetic algorithm or bayesian optimization) to iteratively adjust and determine optimal MakeHuman parameters.\n\n\n\n\n\nData Collection:\n\nTask: Manually label a small set of images with MakeHuman parameters.\nOutcome: Create a baseline dataset for initial optimization efforts.\n\nGodot Integration:\n\nTask: Develop a script within Godot to render depth maps from configured MakeHuman models.\nOutcome: Prepare depth maps for subsequent comparison.\n\nOptimization Algorithm:\n\nTask: Implement a cost-effective optimization algorithm using a suitable loss function (e.g., L2, Chamfer distance).\nOutcome: Establish a mechanism to identify the best matching MakeHuman parameters.\n\nTesting and Refinement:\n\nTask: Systematically compare generated depth maps and refine the algorithm to improve accuracy.\nTimeline:\n\nData Collection: 1 week\nGodot Integration: 2 weeks\nOptimization Model: 3 weeks\nTesting & Refinement: 1 week\nTotal Duration: 7 weeks\n\n\n\n\n\n\n\n\nThis streamlined, budget-conscious methodology promises significant enhancements in personalization and realism in digital character modeling, making it ideal for applications in gaming and virtual reality where character authenticity is crucial.\n\n\n\n\nLimited Creativity: Strict adherence to replicating existing images may limit creative modifications.\nTechnical Complexity: The integration of multiple advanced technologies (depth sensing, machine learning, and 3D rendering) requires high technical expertise.\n\n\n\n\nAlternative methods such as direct 3D scanning of physical models or manual tweaking of parameters were considered but deemed less efficient and scalable compared to our proposed automated depth comparison method.\n\n\n\nIn cases where extremely high fidelity is required, such as in professional film production, additional manual adjustments by expert artists might still be necessary.\n\n\n\nThis project aligns with our core mission of enhancing digital interaction experiences and will be developed and maintained by our team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nDepthPro Demo with 3D Visualization\nHyper_parameter_optimization like bayensian optimization\n\nAI assistant Aria assisted with this article."
+    "text": "Efficient communication between the host side and the WASM guest.\nImproved performance when dealing with complex data types.\nSimplified API usage for developers."
   },
   {
-    "objectID": "decisions/20241011-recovering-makehuman-parameters.html#the-context",
-    "href": "decisions/20241011-recovering-makehuman-parameters.html#the-context",
-    "title": "Proposed: Recovering MakeHuman Parameters Using Depth Map Comparison with Godot Engine",
+    "objectID": "decisions/20230509-wasm-data-exchange.html#negative-consequences",
+    "href": "decisions/20230509-wasm-data-exchange.html#negative-consequences",
+    "title": "Draft: Exchange data between Godot Engine and WASM using handles",
     "section": "",
-    "text": "In the realm of digital animation and character modeling, fitting an avatar to a specific image can enhance personalization and realism in various applications such as gaming and virtual reality."
+    "text": "Additional complexity in the implementation.\nPotential overhead due to reference counting."
   },
   {
-    "objectID": "decisions/20241011-recovering-makehuman-parameters.html#the-problem-statement",
-    "href": "decisions/20241011-recovering-makehuman-parameters.html#the-problem-statement",
-    "title": "Proposed: Recovering MakeHuman Parameters Using Depth Map Comparison with Godot Engine",
+    "objectID": "decisions/20230509-wasm-data-exchange.html#option-graveyard",
+    "href": "decisions/20230509-wasm-data-exchange.html#option-graveyard",
+    "title": "Draft: Exchange data between Godot Engine and WASM using handles",
     "section": "",
-    "text": "The challenge lies in accurately estimating the parameters of a MakeHuman model from a given anime-style image to ensure the avatar closely resembles the original character."
+    "text": "N/A"
   },
   {
-    "objectID": "decisions/20241011-recovering-makehuman-parameters.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20241011-recovering-makehuman-parameters.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Recovering MakeHuman Parameters Using Depth Map Comparison with Godot Engine",
+    "objectID": "decisions/20230509-wasm-data-exchange.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230509-wasm-data-exchange.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Draft: Exchange data between Godot Engine and WASM using handles",
     "section": "",
-    "text": "We propose a system that utilizes depth map comparisons between rendered images from the Godot Engine and depth maps generated from anime images using Apple’s ML-Depth-Pro. This approach aims to optimize the MakeHuman parameters to recreate accurate 3D models of anime characters.\n\n\n\nDepth Map Generation: Generate depth maps from both anime images and Godot-rendered characters.\nOptimization: Employ machine learning techniques to minimize the differences between these depth maps, facilitating accurate parameter recovery.\nCost Efficiency: Leverage open-source tools to maintain budget-friendliness.\n\n\n\n\n\nInput Data: Anime images with manually labeled MakeHuman parameters for initial calibration.\nDepth Comparison: Analyze the discrepancies between the depth maps produced by Godot and those derived from anime images.\nOptimization Process: Utilize a search algorithm (e.g., genetic algorithm or bayesian optimization) to iteratively adjust and determine optimal MakeHuman parameters.\n\n\n\n\n\nData Collection:\n\nTask: Manually label a small set of images with MakeHuman parameters.\nOutcome: Create a baseline dataset for initial optimization efforts.\n\nGodot Integration:\n\nTask: Develop a script within Godot to render depth maps from configured MakeHuman models.\nOutcome: Prepare depth maps for subsequent comparison.\n\nOptimization Algorithm:\n\nTask: Implement a cost-effective optimization algorithm using a suitable loss function (e.g., L2, Chamfer distance).\nOutcome: Establish a mechanism to identify the best matching MakeHuman parameters.\n\nTesting and Refinement:\n\nTask: Systematically compare generated depth maps and refine the algorithm to improve accuracy.\nTimeline:\n\nData Collection: 1 week\nGodot Integration: 2 weeks\nOptimization Model: 3 weeks\nTesting & Refinement: 1 week\nTotal Duration: 7 weeks"
+    "text": "No, this enhancement addresses a core limitation and requires changes to the underlying system."
   },
   {
-    "objectID": "decisions/20241011-recovering-makehuman-parameters.html#the-benefits",
-    "href": "decisions/20241011-recovering-makehuman-parameters.html#the-benefits",
-    "title": "Proposed: Recovering MakeHuman Parameters Using Depth Map Comparison with Godot Engine",
+    "objectID": "decisions/20230509-wasm-data-exchange.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230509-wasm-data-exchange.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Draft: Exchange data between Godot Engine and WASM using handles",
     "section": "",
-    "text": "This streamlined, budget-conscious methodology promises significant enhancements in personalization and realism in digital character modeling, making it ideal for applications in gaming and virtual reality where character authenticity is crucial."
+    "text": "Yes, this enhancement improves the efficiency and usability of the V-Sekai platform, making it more attractive to developers and users."
   },
   {
-    "objectID": "decisions/20241011-recovering-makehuman-parameters.html#the-downsides",
-    "href": "decisions/20241011-recovering-makehuman-parameters.html#the-downsides",
-    "title": "Proposed: Recovering MakeHuman Parameters Using Depth Map Comparison with Godot Engine",
+    "objectID": "decisions/20230509-wasm-data-exchange.html#references",
+    "href": "decisions/20230509-wasm-data-exchange.html#references",
+    "title": "Draft: Exchange data between Godot Engine and WASM using handles",
     "section": "",
-    "text": "Limited Creativity: Strict adherence to replicating existing images may limit creative modifications.\nTechnical Complexity: The integration of multiple advanced technologies (depth sensing, machine learning, and 3D rendering) requires high technical expertise."
+    "text": "V-Sekai\nGodot Engine StreamPeer\nGodot Engine Wasm\nGodot Engine WasGo"
   },
   {
-    "objectID": "decisions/20241011-recovering-makehuman-parameters.html#the-road-not-taken",
-    "href": "decisions/20241011-recovering-makehuman-parameters.html#the-road-not-taken",
-    "title": "Proposed: Recovering MakeHuman Parameters Using Depth Map Comparison with Godot Engine",
+    "objectID": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html",
+    "href": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html",
+    "title": "Accepted: Create an open metaverse by working on V-Sekai",
     "section": "",
-    "text": "Alternative methods such as direct 3D scanning of physical models or manual tweaking of parameters were considered but deemed less efficient and scalable compared to our proposed automated depth comparison method."
+    "text": "Status: accepted \nDeciders: V-Sekai,lyuma,fire,MrMetaverse,\nTags: V-Sekai,\n\n\n\nV-Sekai is a VR virtual world platform.\n\n\n\nBuild V-Sekai.\n\nSpatialized audio and VOIP support\nA custom networking stack\nA security-focused sandboxed scripting environment backed by WASM\nCustomizable servers with their own individual game rules\nDependable for important presentations\n\nAs a 3d world builder, I want to upload a world to invite my friends to experience (Voice Communication, Reliability, Networked) with me.\n\nUninstalled: give a URL with a copy of the game.\nInstalled: url to uro that sends an url\n\nv-sekai://v-sekai.org/lyuma/home?key=asjdfhgdtg#68.4,1.4,0.34\nRegister windows protocol handler\n\n\nAs an explorer, I want to browse a selection of places to visit.\nAs a user, I want to pick up objects to hand them to my friend.\nAs a user, I want to bring my identity (my avatar) to interact with in V-Sekai.\nAs a developer, I need V-Sekai to understand my needs to have an excellent developer-user experience.\nAs a creative, I want to edit my V-Sekai virtual environment to better suit my requirements and preferences.\nAs a user developer, I want to remix V-Sekai to better suit my requirements and preferences.\nAs a person, I want to work with a group that shares my values.\nAs a person, I want to survive long enough to build V-Sekai.\n\n\n\nRegister protocol.\ndef register_protocol(proto, command):\n    import winreg\n    key = winreg.CreateKey(winreg.HKEY_CLASSES_ROOT, rf\"{proto}\")\n    winreg.SetValueEx(key, \"\", 0, winreg.REG_SZ, f\"URL:{proto} protocol\")\n    winreg.SetValueEx(key, \"URL Protocol\", 0, winreg.REG_SZ, \"\")\n    key = winreg.CreateKey(winreg.HKEY_CLASSES_ROOT, rf\"{proto}\\shell\\open\\command\")\n    winreg.SetValueEx(key, \"\", 0, winreg.REG_SZ, command)\n\n\n\n\nIt matters that we are here to create V-Sekai. I imagine a future where all the virtual world platforms are closed, with no space to create and remix.\nWe are making V-Sekai to serve people who want to create and be in the metaverse.\n\n\n\n\n\nWe are promoting Native VRM support so arbitrary 3d models aren’t on the golden path as of 2021-12-16.\nWe choose native code on the devices, so we can’t use the interoperability of the web as of 2021-12-16.\nWe choose Godot Engine which is an open source game engine to own our dependencies, so it is hard to use off the shelf commercial technologies.\nWe prefer de-facto or open standards for the most reach, so we may not be able to get the exact solution we want without effort.\n\n\n\n\n\nOption: Use dominant VR platforms.\nRejection Reason: At this moment. there is an opportunity to have a coalition of open metaverse.\n\n\n\n\nV-Sekai needs a strategy and not code.\n\n\n\nWe are V-Sekai and only we can be who we want to be.\n\n\n\n\nhttps://www.fortressofdoors.com/so-you-want-to-compete-with-roblox/\n\n\n\n\nYou should consider the following as mere table stakes: High-quality multiplayer support for user #creation out of the box High-performance servers with excellent reliability Powerful, user-friendly, and joyful creation tools\n\n\n\n\nhttps://martinfowler.com/bliki/MonolithFirst.html\nhttps://en.wikipedia.org/wiki/John_Gall_(author)\nhttps://github.com/ubisoft/mixer Has Blender and Unity Support 2021-12-14. It needs to be debugged for Blender 3.0.\n\n\n\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20241011-recovering-makehuman-parameters.html#the-infrequent-use-case",
-    "href": "decisions/20241011-recovering-makehuman-parameters.html#the-infrequent-use-case",
-    "title": "Proposed: Recovering MakeHuman Parameters Using Depth Map Comparison with Godot Engine",
+    "objectID": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html#context-and-problem-statement",
+    "href": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html#context-and-problem-statement",
+    "title": "Accepted: Create an open metaverse by working on V-Sekai",
     "section": "",
-    "text": "In cases where extremely high fidelity is required, such as in professional film production, additional manual adjustments by expert artists might still be necessary."
+    "text": "V-Sekai is a VR virtual world platform."
   },
   {
-    "objectID": "decisions/20241011-recovering-makehuman-parameters.html#in-core-and-done-by-us",
-    "href": "decisions/20241011-recovering-makehuman-parameters.html#in-core-and-done-by-us",
-    "title": "Proposed: Recovering MakeHuman Parameters Using Depth Map Comparison with Godot Engine",
+    "objectID": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Accepted: Create an open metaverse by working on V-Sekai",
     "section": "",
-    "text": "This project aligns with our core mission of enhancing digital interaction experiences and will be developed and maintained by our team."
+    "text": "Build V-Sekai.\n\nSpatialized audio and VOIP support\nA custom networking stack\nA security-focused sandboxed scripting environment backed by WASM\nCustomizable servers with their own individual game rules\nDependable for important presentations\n\nAs a 3d world builder, I want to upload a world to invite my friends to experience (Voice Communication, Reliability, Networked) with me.\n\nUninstalled: give a URL with a copy of the game.\nInstalled: url to uro that sends an url\n\nv-sekai://v-sekai.org/lyuma/home?key=asjdfhgdtg#68.4,1.4,0.34\nRegister windows protocol handler\n\n\nAs an explorer, I want to browse a selection of places to visit.\nAs a user, I want to pick up objects to hand them to my friend.\nAs a user, I want to bring my identity (my avatar) to interact with in V-Sekai.\nAs a developer, I need V-Sekai to understand my needs to have an excellent developer-user experience.\nAs a creative, I want to edit my V-Sekai virtual environment to better suit my requirements and preferences.\nAs a user developer, I want to remix V-Sekai to better suit my requirements and preferences.\nAs a person, I want to work with a group that shares my values.\nAs a person, I want to survive long enough to build V-Sekai."
   },
   {
-    "objectID": "decisions/20241011-recovering-makehuman-parameters.html#status",
-    "href": "decisions/20241011-recovering-makehuman-parameters.html#status",
-    "title": "Proposed: Recovering MakeHuman Parameters Using Depth Map Comparison with Godot Engine",
+    "objectID": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Accepted: Create an open metaverse by working on V-Sekai",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "Register protocol.\ndef register_protocol(proto, command):\n    import winreg\n    key = winreg.CreateKey(winreg.HKEY_CLASSES_ROOT, rf\"{proto}\")\n    winreg.SetValueEx(key, \"\", 0, winreg.REG_SZ, f\"URL:{proto} protocol\")\n    winreg.SetValueEx(key, \"URL Protocol\", 0, winreg.REG_SZ, \"\")\n    key = winreg.CreateKey(winreg.HKEY_CLASSES_ROOT, rf\"{proto}\\shell\\open\\command\")\n    winreg.SetValueEx(key, \"\", 0, winreg.REG_SZ, command)"
   },
   {
-    "objectID": "decisions/20241011-recovering-makehuman-parameters.html#decision-makers",
-    "href": "decisions/20241011-recovering-makehuman-parameters.html#decision-makers",
-    "title": "Proposed: Recovering MakeHuman Parameters Using Depth Map Comparison with Godot Engine",
+    "objectID": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html#positive-consequences",
+    "href": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html#positive-consequences",
+    "title": "Accepted: Create an open metaverse by working on V-Sekai",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "It matters that we are here to create V-Sekai. I imagine a future where all the virtual world platforms are closed, with no space to create and remix.\nWe are making V-Sekai to serve people who want to create and be in the metaverse."
   },
   {
-    "objectID": "decisions/20241011-recovering-makehuman-parameters.html#tags",
-    "href": "decisions/20241011-recovering-makehuman-parameters.html#tags",
-    "title": "Proposed: Recovering MakeHuman Parameters Using Depth Map Comparison with Godot Engine",
+    "objectID": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html#negative-consequences",
+    "href": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html#negative-consequences",
+    "title": "Accepted: Create an open metaverse by working on V-Sekai",
     "section": "",
-    "text": "V-Sekai"
+    "text": "We are promoting Native VRM support so arbitrary 3d models aren’t on the golden path as of 2021-12-16.\nWe choose native code on the devices, so we can’t use the interoperability of the web as of 2021-12-16.\nWe choose Godot Engine which is an open source game engine to own our dependencies, so it is hard to use off the shelf commercial technologies.\nWe prefer de-facto or open standards for the most reach, so we may not be able to get the exact solution we want without effort."
   },
   {
-    "objectID": "decisions/20241011-recovering-makehuman-parameters.html#further-reading",
-    "href": "decisions/20241011-recovering-makehuman-parameters.html#further-reading",
-    "title": "Proposed: Recovering MakeHuman Parameters Using Depth Map Comparison with Godot Engine",
+    "objectID": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html#option-graveyard",
+    "href": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html#option-graveyard",
+    "title": "Accepted: Create an open metaverse by working on V-Sekai",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nDepthPro Demo with 3D Visualization\nHyper_parameter_optimization like bayensian optimization\n\nAI assistant Aria assisted with this article."
+    "text": "Option: Use dominant VR platforms.\nRejection Reason: At this moment. there is an opportunity to have a coalition of open metaverse."
   },
   {
-    "objectID": "decisions/20230507-distributed-sim.html",
-    "href": "decisions/20230507-distributed-sim.html",
-    "title": "Rejected: Distributed simulation",
+    "objectID": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Accepted: Create an open metaverse by working on V-Sekai",
     "section": "",
-    "text": "Status: rejected \nDeciders: V-Sekai,fire,\nTags: V-Sekai,networking,\n\n\n\n\nOur project involves a distributed simulation system where maintaining strong consistency and efficient workload distribution are important requirements. We are currently facing the challenge of how to handle authority transfer and state updates between simulation servers without incurring high network hop counts and latency.\nSomeone invited me to a popular VR platform and gave me a 20-minute tour, just enough to learn how to in desktop mode create a world, import an object, and inspector-edit it. So I imported our celebration map, and the map loaded in 20 seconds. I was able to change its transform. I’m still thinking about that experience.\n\n\n\nWe propose to use a metadata system with Khepri instances and Raft consensus algorithm to manage ownership and mastership information for game entity nodes. Homeservers will manage metadata using their own Khepri instances within a Raft cluster, while simulation servers, including player simulation servers, will maintain game entity nodes they have authority over using their own Khepri instances.\nAuthority transfer will be initiated through the metadata Raft cluster when players interact with game entities governed by different simulation servers. The homeserver Khepri’s nested path-to-value structure will be updated based on the ownership and mastership rules set by the Master. State updates will be exchanged between old and new authority simulation servers or synchronized using a separate mechanism during authority transfer.\nBy monitoring the load on homeservers and simulation servers, we can balance the system and ensure fault tolerance using Raft’s mechanisms. As the number of game entity nodes and players grows, adding more homeservers to the metadata Raft cluster and more simulation servers will ensure efficient workload distribution and enhance the overall gaming experience.\nWe believe that this approach will provide strong consistency guarantees, access control, and scalability while minimizing network hop counts and latency for authority transfer and state updates between simulation servers.\n\n\n\n\n\n\nHomeserver: A server responsible for managing metadata, including ownership and mastership information for game entity nodes.\nSimulation server: A server responsible for containing game entity nodes it has authority over, including player simulation servers.\nKhepri: A tree-like replicated on-disk database library for Erlang and Elixir, used for maintaining a nested path-to-value store.\nRaft cluster: A cluster of servers implementing the Raft consensus algorithm to ensure strong consistency and fault tolerance.\nOwnership: The player who has control over a game entity and can change its state.\nMastership: The authority that can change ownership rules and default ownership settings.\nAsk, Deny, Allow: Rules set by the Master for ownership transfer.\n\n\n\n\n\nEach type of server can only be Khepri members of the same type.\nEach server can only allow be Khepri members of the same logical instance.\nRaft is only active inside of each logical instance.\nHomeserver servers are REST + JSON and the cheap pattern.\nSimulation servers are using the nasty state transfer pattern\n\n\n\n\n\n\n\n\n\n\n\nStep\nAction\n\n\n\n\n1\nPlayer A’s simulation server sends a request to the home server to fetch the public key of Player B.\n\n\n2\nThe home server retrieves Player B’s public key from its database and sends it back to Player A’s simulation server.\n\n\n3\nPlayer A’s simulation server uses Player B’s public key to encrypt a message or binary data.\n\n\n4\nPlayer A’s simulation server signs the encrypted message or binary data using its own private key.\n\n\n5\nPlayer A’s simulation server sends the encrypted message or binary data along with the digital signature to Player B’s simulation server using the membrane_udp_plugin.\n\n\n6\nPlayer B’s simulation server receives the message and verifies the digital signature using Player A’s public key, which it retrieves from the home server.\n\n\n7\nIf the signature is valid, Player B’s simulation server uses its own private key to decrypt the message and obtain the original data sent by Player A’s simulation server.\n\n\n8\nIf the message is confidential, Player B’s simulation server may want to send a response back to Player A’s simulation server using a similar protocol, with Player A’s public key retrieved from the home server.\n\n\n\nThis table outlines the steps of the communication protocol between Player A and Player B’s simulation servers, which involves retrieving public keys from the home server’s database, encrypting and signing messages, and verifying digital signatures to ensure the authenticity of the messages. This protocol ensures secure and confidential communication between the two simulation servers, allowing for safe and reliable data exchange.\n# EC examples\nalice_private_jwk = JOSE.JWK.from_pem_file(\"ec-secp256r1-alice.pem\")\nalice_public_jwk  = JOSE.JWK.to_public(alice_private_jwk)\nbob_private_jwk   = JOSE.JWK.from_pem_file(\"ec-secp256r1-bob.pem\")\nbob_public_jwk    = JOSE.JWK.to_public(bob_private_jwk)\n\n## Encrypt and Decrypt (defaults to ECDH-ES with A128GCM)\n### Alice sends Bob a secret message using Bob's public key and Alice's private key\nalice_to_bob = \"For Bob's eyes only.\"\nencrypted = JOSE.JWK.box_encrypt(alice_to_bob, bob_public_jwk, alice_private_jwk)\n### Only Bob can decrypt the message using his private key (Alice's public key is embedded in the JWE header)\n{^alice_to_bob, _} = JOSE.JWK.box_decrypt(encrypted, bob_private_jwk)\n\n\n\nIn a distributed simulation system, maintaining separate roles for homeservers and simulation servers and using a metadata system with strong consistency guarantees is crucial. Homeservers are responsible for managing metadata, including ownership and mastership information for game entity nodes, using a Khepri instance within a Raft cluster. Simulation servers, including player simulation servers, maintain game entity nodes they have authority over using their own Khepri instances.\nAuthority transfer is initiated through the metadata Raft cluster when players interact with game entities governed by different simulation servers. The homeserver Khepri’s nested path-to-value structure is updated based on the ownership and mastership rules set by the Master. State updates are exchanged between old and new authority simulation servers or synchronized using a separate mechanism during authority transfer.\nMonitoring the load on homeservers and simulation servers allows for balancing the system and ensuring fault tolerance using Raft’s mechanisms. As the number of game entity nodes and players grows, adding more homeservers to the metadata Raft cluster and more simulation servers ensures efficient workload distribution and enhances the overall gaming experience.\n\n\n\n\nCase 1: Authority transfer from Player A to Player B on a different home server\n\n\n\n\n\n\n\n\nStep\nDescription\nHop Count\n\n\n\n\n1\nPlayer A’s simulation server sends a request to its homeserver (1 hop).\n1\n\n\n2\nPlayer A’s homeserver sends an authority request to Player B’s homeserver (H hops).\nH\n\n\n3\nPlayer B’s homeserver sends a response to Player A’s homeserver (H hops).\nH\n\n\n4\nPlayer A’s homeserver sends an authority response to Player A’s simulation server (1 hop).\n1\n\n\n5\nPlayer A’s simulation server sends an acknowledgment to Player B’s simulation server (1 hop).\n1\n\n\n\nSending an acknowledgment from Player A’s homeserver to Player A’s simulation server may not be necessary, as the authority request can be sent directly to Player B’s homeserver without waiting for confirmation.\nTotal hops: 3 + 2 * H\nCase 2: Authority transfer if Player A’s and Player B’s homeservers are exactly the same\n\n\n\n\n\n\n\n\nStep\nDescription\nHop Count\n\n\n\n\n1\nPlayer A’s simulation server sends a request to its homeserver (1 hop).\n1\n\n\n2\nPlayer A’s homeserver sends a response directly to Player B’s simulation server (1 hop).\n1\n\n\n3\nPlayer B’s simulation server sends an acknowledgment to Player A’s simulation server (1 hop).\n1\n\n\n\nTotal hops: 3\nIn this optimized process, we have removed sending an acknowledgment from Player A’s homeserver to Player A’s simulation server. This acknowledgment may not be necessary, as the response can be sent directly to Player B’s simulation server without waiting for confirmation. By removing this step, we reduce the total hop count by 1, potentially improving the efficiency of the authority transfer process when both players are on the same home server.\nCase 3: Direct communication between Player A and Player B’s simulation servers on the same home server.\n\n\n\n\n\n\n\n\nStep\nDescription\nHop Count\n\n\n\n\n1\nPlayer A’s simulation server sends an update directly to Player B’s simulation server using a hand-optimized binary layout and an asynchronous communication model.\n1\n\n\n2\nPlayer B’s simulation server sends an acknowledgment to Player A’s simulation server using credit-based flow control or another asynchronous technique.\n1\n\n\n\nIn this modified version of Case 3, both the update and acknowledgment steps employ the high-performance communication system’s features. This includes using hand-optimized binary layouts for data transfer and asynchronous communication techniques to minimize latency and maximize throughput. The total hop count remains the same at 2 hops.\n\n\n\nStrong consistency guarantees\nAccess control over Khepri instances\nScalability\nMinimized network hop counts and latency for authority transfer and state updates\n\n\n\n\n\nComplexity: The proposed system involves multiple components, such as homeservers, simulation servers, Khepri instances, and Raft clusters. Managing and maintaining these components can be complex and may require significant development effort.\nPerformance: The use of Raft consensus algorithm ensures strong consistency but may introduce performance overhead due to the need for communication between nodes in the cluster. This could impact the overall performance of the distributed simulation system.\nScalability: While the proposal aims to provide scalability, it is not clear how well the system will scale as the number of game entity nodes and players grows. Adding more homeservers and simulation servers might help, but there could still be bottlenecks or limitations that need to be addressed.\nSecurity: The proposed state transfer protocol relies on public key cryptography for secure communication between simulation servers. However, the security of the system depends on proper key management and protection against potential attacks, such as man-in-the-middle attacks or replay attacks.\nFault tolerance: Although the Raft consensus algorithm provides fault tolerance, the system’s resilience to failures (e.g., server crashes, network issues) needs to be carefully considered and tested to ensure smooth operation under various conditions.\nSynchronization: The proposal mentions that state updates are exchanged between old and new authority simulation servers or synchronized using a separate mechanism during authority transfer. However, it does not provide details on how this synchronization process works, which could be a critical aspect of the system’s functionality.\nLoad balancing: Monitoring the load on homeservers and simulation servers is essential for balancing the system. However, the proposal does not provide specific details on how load balancing will be achieved or what metrics will be used to determine when to add or remove servers from the system.\n\n\n\n\nWe considered using a client-server model for the distributed simulation system but found that it would not provide the strong consistency guarantees and access control we require, and it would also be more difficult to scale as the number of game entity nodes and players grows.\n\n\n\nThis is not a few lines of script.\n\n\n\nI am exploring alternatives for the current implementation of the client-server model.\n\n\n\n\nV-Sekai: https://v-sekai.org/\nKhepri documentation: https://github.com/rabbitmq/khepri\nRaft consensus algorithm: https://raft.github.io/\nNetworked Physics in Virtual Reality: https://gafferongames.com/post/networked_physics_in_virtual_reality/\nChapter 7 - Advanced Architecture using ZeroMQ: https://zguide.zeromq.org/docs/chapter7/"
+    "text": "V-Sekai needs a strategy and not code."
   },
   {
-    "objectID": "decisions/20230507-distributed-sim.html#distributed-simulation-architecture",
-    "href": "decisions/20230507-distributed-sim.html#distributed-simulation-architecture",
-    "title": "Rejected: Distributed simulation",
+    "objectID": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Accepted: Create an open metaverse by working on V-Sekai",
     "section": "",
-    "text": "Case 1: Authority transfer from Player A to Player B on a different home server\n\n\n\n\n\n\n\n\nStep\nDescription\nHop Count\n\n\n\n\n1\nPlayer A’s simulation server sends a request to its homeserver (1 hop).\n1\n\n\n2\nPlayer A’s homeserver sends an authority request to Player B’s homeserver (H hops).\nH\n\n\n3\nPlayer B’s homeserver sends a response to Player A’s homeserver (H hops).\nH\n\n\n4\nPlayer A’s homeserver sends an authority response to Player A’s simulation server (1 hop).\n1\n\n\n5\nPlayer A’s simulation server sends an acknowledgment to Player B’s simulation server (1 hop).\n1\n\n\n\nSending an acknowledgment from Player A’s homeserver to Player A’s simulation server may not be necessary, as the authority request can be sent directly to Player B’s homeserver without waiting for confirmation.\nTotal hops: 3 + 2 * H\nCase 2: Authority transfer if Player A’s and Player B’s homeservers are exactly the same\n\n\n\n\n\n\n\n\nStep\nDescription\nHop Count\n\n\n\n\n1\nPlayer A’s simulation server sends a request to its homeserver (1 hop).\n1\n\n\n2\nPlayer A’s homeserver sends a response directly to Player B’s simulation server (1 hop).\n1\n\n\n3\nPlayer B’s simulation server sends an acknowledgment to Player A’s simulation server (1 hop).\n1\n\n\n\nTotal hops: 3\nIn this optimized process, we have removed sending an acknowledgment from Player A’s homeserver to Player A’s simulation server. This acknowledgment may not be necessary, as the response can be sent directly to Player B’s simulation server without waiting for confirmation. By removing this step, we reduce the total hop count by 1, potentially improving the efficiency of the authority transfer process when both players are on the same home server.\nCase 3: Direct communication between Player A and Player B’s simulation servers on the same home server.\n\n\n\n\n\n\n\n\nStep\nDescription\nHop Count\n\n\n\n\n1\nPlayer A’s simulation server sends an update directly to Player B’s simulation server using a hand-optimized binary layout and an asynchronous communication model.\n1\n\n\n2\nPlayer B’s simulation server sends an acknowledgment to Player A’s simulation server using credit-based flow control or another asynchronous technique.\n1\n\n\n\nIn this modified version of Case 3, both the update and acknowledgment steps employ the high-performance communication system’s features. This includes using hand-optimized binary layouts for data transfer and asynchronous communication techniques to minimize latency and maximize throughput. The total hop count remains the same at 2 hops.\n\n\n\nStrong consistency guarantees\nAccess control over Khepri instances\nScalability\nMinimized network hop counts and latency for authority transfer and state updates\n\n\n\n\n\nComplexity: The proposed system involves multiple components, such as homeservers, simulation servers, Khepri instances, and Raft clusters. Managing and maintaining these components can be complex and may require significant development effort.\nPerformance: The use of Raft consensus algorithm ensures strong consistency but may introduce performance overhead due to the need for communication between nodes in the cluster. This could impact the overall performance of the distributed simulation system.\nScalability: While the proposal aims to provide scalability, it is not clear how well the system will scale as the number of game entity nodes and players grows. Adding more homeservers and simulation servers might help, but there could still be bottlenecks or limitations that need to be addressed.\nSecurity: The proposed state transfer protocol relies on public key cryptography for secure communication between simulation servers. However, the security of the system depends on proper key management and protection against potential attacks, such as man-in-the-middle attacks or replay attacks.\nFault tolerance: Although the Raft consensus algorithm provides fault tolerance, the system’s resilience to failures (e.g., server crashes, network issues) needs to be carefully considered and tested to ensure smooth operation under various conditions.\nSynchronization: The proposal mentions that state updates are exchanged between old and new authority simulation servers or synchronized using a separate mechanism during authority transfer. However, it does not provide details on how this synchronization process works, which could be a critical aspect of the system’s functionality.\nLoad balancing: Monitoring the load on homeservers and simulation servers is essential for balancing the system. However, the proposal does not provide specific details on how load balancing will be achieved or what metrics will be used to determine when to add or remove servers from the system.\n\n\n\n\nWe considered using a client-server model for the distributed simulation system but found that it would not provide the strong consistency guarantees and access control we require, and it would also be more difficult to scale as the number of game entity nodes and players grows.\n\n\n\nThis is not a few lines of script.\n\n\n\nI am exploring alternatives for the current implementation of the client-server model.\n\n\n\n\nV-Sekai: https://v-sekai.org/\nKhepri documentation: https://github.com/rabbitmq/khepri\nRaft consensus algorithm: https://raft.github.io/\nNetworked Physics in Virtual Reality: https://gafferongames.com/post/networked_physics_in_virtual_reality/\nChapter 7 - Advanced Architecture using ZeroMQ: https://zguide.zeromq.org/docs/chapter7/"
+    "text": "We are V-Sekai and only we can be who we want to be."
   },
   {
-    "objectID": "decisions/20230602-pmx-module-integration.html",
-    "href": "decisions/20230602-pmx-module-integration.html",
-    "title": "Proposed: Pmx module integration",
+    "objectID": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html#references",
+    "href": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html#references",
+    "title": "Accepted: Create an open metaverse by working on V-Sekai",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, GPT-4\n\n\n\n\nState process for importing a godot engine module work and publish.\n\n\n\nIntegrate the Godot PMX module into the V-Sekai project by following the implementation steps below.\n\n\n\n\nGo to https://github.com/V-Sekai/godot\nMake sure the 4.0 branch is synced with https://github.com/godotengine/godot\nCreate a branch.\n\nLet’s use an example like vsk-pmx.\n\nSwitch to the branch.\nRun git subrepo clone https://github.com/V-Sekai/godot-pmx modules/pmx in the terminal or command prompt.\nCode the module.\nRun git subrepo pull modules/pmx in the terminal or command prompt to merge with upstream repo.\nCode the module.\nRun git subrepo push modules/pmx in the terminal or command prompt to publish.\nMake sure GitHub CI/CD tests pass.\n\n\n\n\n\nSeamless integration of the PMX module into the V-Sekai project\nImproved functionality and features for users\nEasier maintenance and updates for the module\n\n\n\n\n\nPotential increase in complexity and dependencies\nPossible performance impact if not optimized properly\n\n\n\n\n\nManual integration of the PMX module: Instead of using git subrepo, manually copy and integrate the PMX module into the V-Sekai project. This option is less efficient and harder to maintain, as it requires manual updates and synchronization with the original PMX repository.\nUsing Git Submodules: Use git submodule to include the PMX module in the V-Sekai project. While this approach allows for easier updates and maintenance, it can be more complex to set up and manage compared to git subrepo.\nCreating a separate plugin: Develop the PMX module as a standalone plugin that users can install and enable in their projects. This option reduces the complexity of the core V-Sekai project but may result in less seamless integration and increased setup effort for users.\nForking the Godot Engine: Fork the entire Godot Engine and directly modify its source code to include the PMX module. This option is not recommended, as it would make it difficult to keep the fork updated with upstream changes and could lead to compatibility issues.\n\n\n\n\nThis enhancement cannot be easily worked around with a few lines of script, as it involves integrating a new module into the core project.\n\n\n\nIntegrating the PMX module into the core project ensures that it is maintained and updated alongside the main project, providing a consistent and reliable experience for users.\n\n\n\n\nV-Sekai"
+    "text": "https://www.fortressofdoors.com/so-you-want-to-compete-with-roblox/\n\n\n\n\nYou should consider the following as mere table stakes: High-quality multiplayer support for user #creation out of the box High-performance servers with excellent reliability Powerful, user-friendly, and joyful creation tools\n\n\n\n\nhttps://martinfowler.com/bliki/MonolithFirst.html\nhttps://en.wikipedia.org/wiki/John_Gall_(author)\nhttps://github.com/ubisoft/mixer Has Blender and Unity Support 2021-12-14. It needs to be debugged for Blender 3.0."
   },
   {
-    "objectID": "decisions/20230602-pmx-module-integration.html#metadata",
-    "href": "decisions/20230602-pmx-module-integration.html#metadata",
-    "title": "Proposed: Pmx module integration",
+    "objectID": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html#derivative-license",
+    "href": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html#derivative-license",
+    "title": "Accepted: Create an open metaverse by working on V-Sekai",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, GPT-4"
+    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230602-pmx-module-integration.html#context-and-problem-statement",
-    "href": "decisions/20230602-pmx-module-integration.html#context-and-problem-statement",
-    "title": "Proposed: Pmx module integration",
+    "objectID": "decisions/20231108-neon-1-gb-scene-storage.html",
+    "href": "decisions/20231108-neon-1-gb-scene-storage.html",
+    "title": "Proposed: Adopting Neon’s Bottomless Storage with S3-Compatible Object Store for Edge CDN Data Management",
     "section": "",
-    "text": "State process for importing a godot engine module work and publish."
+    "text": "Status: Proposed\nDeciders: V-Sekai, Fire\nTags: V-Sekai, Neon, Edge Hosting, Bottomless Storage, S3 Compatible, CDN, PostgreSQL, bytea\n\n\n\n\nV-Sekai operates an open-source platform and is in need of a scalable, high-performance solution for storing and managing CDN data for avatars and worlds at the edge.\n\n\n\nHow can V-Sekai effectively use Neon’s bottomless storage, which leverages PostgreSQL’s capabilities and an S3-compatible object store, for edge-hosted CDN data management?\n\n\n\nImplement an edge computing architecture with Neon’s PostgreSQL services, employing the bytea data type for binary data storage and Neon’s bottomless storage system for flushing PostgreSQL pages to an S3-compatible object store.\n\n\n\n\nEdge-hosted architecture for optimal performance and data sovereignty.\nS3-compatible storage enables cost-effective scaling and redundancy.\nThe use of PostgreSQL’s bytea accommodates efficient binary data management without special maintenance.\n\n\n\n\n\nbytea data type has a 1GB size limit and requires loading full data into memory for operations, which might affect performance with large objects.\nDependence on the reliability of S3-compatible services at the edge.\n\n\n\n\nCentralized or non-S3-compatible storage solutions that may not provide the latency and scalability benefits of an edge-hosted environment.\n\n\n\nCases where binary data exceeds the bytea size limit, necessitating additional strategies for data segmentation or alternative storage methods.\n\n\n\nYes, the edge-hosted Neon infrastructure with an S3-compatible object store is planned to be developed and maintained in-house as a core component of V-Sekai’s backend.\n\n\n\n\nV-Sekai on GitHub\nNeon’s Architecture and Bottomless Storage Details\nPostgreSQL bytea Performance Considerations\n\nThis article was assisted by AI."
   },
   {
-    "objectID": "decisions/20230602-pmx-module-integration.html#proposed-solution",
-    "href": "decisions/20230602-pmx-module-integration.html#proposed-solution",
-    "title": "Proposed: Pmx module integration",
+    "objectID": "decisions/20231108-neon-1-gb-scene-storage.html#metadata",
+    "href": "decisions/20231108-neon-1-gb-scene-storage.html#metadata",
+    "title": "Proposed: Adopting Neon’s Bottomless Storage with S3-Compatible Object Store for Edge CDN Data Management",
     "section": "",
-    "text": "Integrate the Godot PMX module into the V-Sekai project by following the implementation steps below."
+    "text": "Status: Proposed\nDeciders: V-Sekai, Fire\nTags: V-Sekai, Neon, Edge Hosting, Bottomless Storage, S3 Compatible, CDN, PostgreSQL, bytea"
   },
   {
-    "objectID": "decisions/20230602-pmx-module-integration.html#implementation",
-    "href": "decisions/20230602-pmx-module-integration.html#implementation",
-    "title": "Proposed: Pmx module integration",
+    "objectID": "decisions/20231108-neon-1-gb-scene-storage.html#the-backdrop",
+    "href": "decisions/20231108-neon-1-gb-scene-storage.html#the-backdrop",
+    "title": "Proposed: Adopting Neon’s Bottomless Storage with S3-Compatible Object Store for Edge CDN Data Management",
     "section": "",
-    "text": "Go to https://github.com/V-Sekai/godot\nMake sure the 4.0 branch is synced with https://github.com/godotengine/godot\nCreate a branch.\n\nLet’s use an example like vsk-pmx.\n\nSwitch to the branch.\nRun git subrepo clone https://github.com/V-Sekai/godot-pmx modules/pmx in the terminal or command prompt.\nCode the module.\nRun git subrepo pull modules/pmx in the terminal or command prompt to merge with upstream repo.\nCode the module.\nRun git subrepo push modules/pmx in the terminal or command prompt to publish.\nMake sure GitHub CI/CD tests pass."
+    "text": "V-Sekai operates an open-source platform and is in need of a scalable, high-performance solution for storing and managing CDN data for avatars and worlds at the edge."
   },
   {
-    "objectID": "decisions/20230602-pmx-module-integration.html#positive-consequences",
-    "href": "decisions/20230602-pmx-module-integration.html#positive-consequences",
-    "title": "Proposed: Pmx module integration",
+    "objectID": "decisions/20231108-neon-1-gb-scene-storage.html#the-challenge",
+    "href": "decisions/20231108-neon-1-gb-scene-storage.html#the-challenge",
+    "title": "Proposed: Adopting Neon’s Bottomless Storage with S3-Compatible Object Store for Edge CDN Data Management",
     "section": "",
-    "text": "Seamless integration of the PMX module into the V-Sekai project\nImproved functionality and features for users\nEasier maintenance and updates for the module"
+    "text": "How can V-Sekai effectively use Neon’s bottomless storage, which leverages PostgreSQL’s capabilities and an S3-compatible object store, for edge-hosted CDN data management?"
   },
   {
-    "objectID": "decisions/20230602-pmx-module-integration.html#negative-consequences",
-    "href": "decisions/20230602-pmx-module-integration.html#negative-consequences",
-    "title": "Proposed: Pmx module integration",
+    "objectID": "decisions/20231108-neon-1-gb-scene-storage.html#the-strategy",
+    "href": "decisions/20231108-neon-1-gb-scene-storage.html#the-strategy",
+    "title": "Proposed: Adopting Neon’s Bottomless Storage with S3-Compatible Object Store for Edge CDN Data Management",
     "section": "",
-    "text": "Potential increase in complexity and dependencies\nPossible performance impact if not optimized properly"
+    "text": "Implement an edge computing architecture with Neon’s PostgreSQL services, employing the bytea data type for binary data storage and Neon’s bottomless storage system for flushing PostgreSQL pages to an S3-compatible object store."
   },
   {
-    "objectID": "decisions/20230602-pmx-module-integration.html#option-graveyard",
-    "href": "decisions/20230602-pmx-module-integration.html#option-graveyard",
-    "title": "Proposed: Pmx module integration",
+    "objectID": "decisions/20231108-neon-1-gb-scene-storage.html#the-upside",
+    "href": "decisions/20231108-neon-1-gb-scene-storage.html#the-upside",
+    "title": "Proposed: Adopting Neon’s Bottomless Storage with S3-Compatible Object Store for Edge CDN Data Management",
     "section": "",
-    "text": "Manual integration of the PMX module: Instead of using git subrepo, manually copy and integrate the PMX module into the V-Sekai project. This option is less efficient and harder to maintain, as it requires manual updates and synchronization with the original PMX repository.\nUsing Git Submodules: Use git submodule to include the PMX module in the V-Sekai project. While this approach allows for easier updates and maintenance, it can be more complex to set up and manage compared to git subrepo.\nCreating a separate plugin: Develop the PMX module as a standalone plugin that users can install and enable in their projects. This option reduces the complexity of the core V-Sekai project but may result in less seamless integration and increased setup effort for users.\nForking the Godot Engine: Fork the entire Godot Engine and directly modify its source code to include the PMX module. This option is not recommended, as it would make it difficult to keep the fork updated with upstream changes and could lead to compatibility issues."
+    "text": "Edge-hosted architecture for optimal performance and data sovereignty.\nS3-compatible storage enables cost-effective scaling and redundancy.\nThe use of PostgreSQL’s bytea accommodates efficient binary data management without special maintenance."
   },
   {
-    "objectID": "decisions/20230602-pmx-module-integration.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230602-pmx-module-integration.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Pmx module integration",
+    "objectID": "decisions/20231108-neon-1-gb-scene-storage.html#the-downside",
+    "href": "decisions/20231108-neon-1-gb-scene-storage.html#the-downside",
+    "title": "Proposed: Adopting Neon’s Bottomless Storage with S3-Compatible Object Store for Edge CDN Data Management",
     "section": "",
-    "text": "This enhancement cannot be easily worked around with a few lines of script, as it involves integrating a new module into the core project."
+    "text": "bytea data type has a 1GB size limit and requires loading full data into memory for operations, which might affect performance with large objects.\nDependence on the reliability of S3-compatible services at the edge."
   },
   {
-    "objectID": "decisions/20230602-pmx-module-integration.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230602-pmx-module-integration.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Pmx module integration",
+    "objectID": "decisions/20231108-neon-1-gb-scene-storage.html#the-road-not-taken",
+    "href": "decisions/20231108-neon-1-gb-scene-storage.html#the-road-not-taken",
+    "title": "Proposed: Adopting Neon’s Bottomless Storage with S3-Compatible Object Store for Edge CDN Data Management",
     "section": "",
-    "text": "Integrating the PMX module into the core project ensures that it is maintained and updated alongside the main project, providing a consistent and reliable experience for users."
+    "text": "Centralized or non-S3-compatible storage solutions that may not provide the latency and scalability benefits of an edge-hosted environment."
   },
   {
-    "objectID": "decisions/20230602-pmx-module-integration.html#references",
-    "href": "decisions/20230602-pmx-module-integration.html#references",
-    "title": "Proposed: Pmx module integration",
+    "objectID": "decisions/20231108-neon-1-gb-scene-storage.html#the-infrequent-use-case",
+    "href": "decisions/20231108-neon-1-gb-scene-storage.html#the-infrequent-use-case",
+    "title": "Proposed: Adopting Neon’s Bottomless Storage with S3-Compatible Object Store for Edge CDN Data Management",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Cases where binary data exceeds the bytea size limit, necessitating additional strategies for data segmentation or alternative storage methods."
   },
   {
-    "objectID": "decisions/20241014-app-updater.html",
-    "href": "decisions/20241014-app-updater.html",
-    "title": "Proposed: Updater No-Op Implementation Using Velopack",
+    "objectID": "decisions/20231108-neon-1-gb-scene-storage.html#in-core-and-done-by-us",
+    "href": "decisions/20231108-neon-1-gb-scene-storage.html#in-core-and-done-by-us",
+    "title": "Proposed: Adopting Neon’s Bottomless Storage with S3-Compatible Object Store for Edge CDN Data Management",
     "section": "",
-    "text": "V-Sekai needs frequent updates to improve and expand its VR features.\n\n\n\nIt’s essential to keep users informed during updates without distracting them with complex visuals.\n\n\n\n\n\nfunc update_application():\n    show_text(\"Updating V-Sekai... Please wait.\")\n    if Velopack.check_for_updates():\n        Velopack.perform_update()\n    hide_text()\n    notify(\"Update complete!\")\n\nfunc show_text(text):\n    var label = Label.new()\n    label.text = text\n    add_child(label)\n\nfunc hide_text():\n    get_node(\"Label\").queue_free()\n\nfunc notify(message):\n    show_message(message)\n\n\n\n\n\nSimplicity: Straightforward user communication.\nClarity: Clear update status messages.\nPerformance: Efficient use of resources through Velopack’s optimized update mechanisms.\n\n\n\n\n\nLack of Visual Appeal: Simple text might seem less professional.\nDependency on External Tool: Reliance on Velopack for update management.\n\n\n\n\nA full graphical interface was considered but deemed too distracting for this phase.\n\n\n\nUsers who rarely update might prefer more detailed visuals.\n\n\n\nHandled internally to ensure seamless integration with Velopack.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\nUpdater\nVelopack\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub repository.\nV-Sekai/v-sekai-game - Project page on GitHub.\nVelopack Documentation - Learn more about how Velopack manages application updates.\n\nAI assistant Aria assisted with this article."
+    "text": "Yes, the edge-hosted Neon infrastructure with an S3-compatible object store is planned to be developed and maintained in-house as a core component of V-Sekai’s backend."
   },
   {
-    "objectID": "decisions/20241014-app-updater.html#the-context",
-    "href": "decisions/20241014-app-updater.html#the-context",
-    "title": "Proposed: Updater No-Op Implementation Using Velopack",
+    "objectID": "decisions/20231108-neon-1-gb-scene-storage.html#further-reading",
+    "href": "decisions/20231108-neon-1-gb-scene-storage.html#further-reading",
+    "title": "Proposed: Adopting Neon’s Bottomless Storage with S3-Compatible Object Store for Edge CDN Data Management",
     "section": "",
-    "text": "V-Sekai needs frequent updates to improve and expand its VR features."
+    "text": "V-Sekai on GitHub\nNeon’s Architecture and Bottomless Storage Details\nPostgreSQL bytea Performance Considerations\n\nThis article was assisted by AI."
   },
   {
-    "objectID": "decisions/20241014-app-updater.html#the-problem-statement",
-    "href": "decisions/20241014-app-updater.html#the-problem-statement",
-    "title": "Proposed: Updater No-Op Implementation Using Velopack",
+    "objectID": "decisions/20211031-script-as-a-binary.html",
+    "href": "decisions/20211031-script-as-a-binary.html",
+    "title": "Proposed: To provide a performance and portable script use WasGo",
     "section": "",
-    "text": "It’s essential to keep users informed during updates without distracting them with complex visuals."
+    "text": "Proposed: To provide a performance and portable script use WasGo\n\nContext and Problem Statement\nNeed a performant and portable script\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nUse wasgo for godot 4\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n\nport wasgo to 4\ndownload as binaries\n???\ngame\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNeed to collaborate with mmae\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nWe know how this works.\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20241014-app-updater.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20241014-app-updater.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Updater No-Op Implementation Using Velopack",
+    "objectID": "decisions/20240623-talk-length-prototypes.html",
+    "href": "decisions/20240623-talk-length-prototypes.html",
+    "title": "Proposed: Talk Length Game Prototypes",
     "section": "",
-    "text": "func update_application():\n    show_text(\"Updating V-Sekai... Please wait.\")\n    if Velopack.check_for_updates():\n        Velopack.perform_update()\n    hide_text()\n    notify(\"Update complete!\")\n\nfunc show_text(text):\n    var label = Label.new()\n    label.text = text\n    add_child(label)\n\nfunc hide_text():\n    get_node(\"Label\").queue_free()\n\nfunc notify(message):\n    show_message(message)"
+    "text": "V-Sekai is a Virtual Reality Social Network Service (VRSNS).\n\n\n\nWhat length should a game demo be?\n\n\n\nOne suggestion is to make the game demo the length of a TED talk. A TED Talk is typically 18 minutes long. This duration is considered optimal for maintaining audience attention and conveying a powerful message, which is exactly what we aim to achieve with our game demo.\n\n\n\n\nAttention Span: An 18-minute demo aligns well with the average person’s attention span. It’s long enough to immerse the player in the game world and showcase its features, but not so long that it risks losing the player’s interest.\nDepth of Experience: This length allows us to provide a substantial preview of the game without overwhelming the player. We can introduce the main gameplay mechanics, narrative elements, and unique features within this timeframe.\nUnique Selling Point: Having a TED talk-length game demo could serve as a unique selling point, distinguishing V-Sekai from other VRSNS.\n\n\n\n\n\nNot One-Size-Fits-All: The length of a TED talk may not be suitable for all types of games. Some games might require longer playtimes to fully appreciate their depth and complexity.\nPlayer Preferences: Some players might prefer shorter or longer demos. We would need to ensure that our target audience is comfortable with this length.\n\n\n\n\nAlternative lengths for the game demo could be considered, such as the length of a typical movie or TV episode.\n\n\n\nThis proposal may not apply to games that are designed to be played in short bursts.\n\n\n\nThis proposal would be implemented by the V-Sekai development team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - The GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis proposal was assisted by AI assistant Aria."
   },
   {
-    "objectID": "decisions/20241014-app-updater.html#the-benefits",
-    "href": "decisions/20241014-app-updater.html#the-benefits",
-    "title": "Proposed: Updater No-Op Implementation Using Velopack",
+    "objectID": "decisions/20240623-talk-length-prototypes.html#the-context",
+    "href": "decisions/20240623-talk-length-prototypes.html#the-context",
+    "title": "Proposed: Talk Length Game Prototypes",
     "section": "",
-    "text": "Simplicity: Straightforward user communication.\nClarity: Clear update status messages.\nPerformance: Efficient use of resources through Velopack’s optimized update mechanisms."
+    "text": "V-Sekai is a Virtual Reality Social Network Service (VRSNS)."
   },
   {
-    "objectID": "decisions/20241014-app-updater.html#the-downsides",
-    "href": "decisions/20241014-app-updater.html#the-downsides",
-    "title": "Proposed: Updater No-Op Implementation Using Velopack",
+    "objectID": "decisions/20240623-talk-length-prototypes.html#the-problem-statement",
+    "href": "decisions/20240623-talk-length-prototypes.html#the-problem-statement",
+    "title": "Proposed: Talk Length Game Prototypes",
     "section": "",
-    "text": "Lack of Visual Appeal: Simple text might seem less professional.\nDependency on External Tool: Reliance on Velopack for update management."
+    "text": "What length should a game demo be?"
   },
   {
-    "objectID": "decisions/20241014-app-updater.html#the-road-not-taken",
-    "href": "decisions/20241014-app-updater.html#the-road-not-taken",
-    "title": "Proposed: Updater No-Op Implementation Using Velopack",
+    "objectID": "decisions/20240623-talk-length-prototypes.html#proposal",
+    "href": "decisions/20240623-talk-length-prototypes.html#proposal",
+    "title": "Proposed: Talk Length Game Prototypes",
     "section": "",
-    "text": "A full graphical interface was considered but deemed too distracting for this phase."
+    "text": "One suggestion is to make the game demo the length of a TED talk. A TED Talk is typically 18 minutes long. This duration is considered optimal for maintaining audience attention and conveying a powerful message, which is exactly what we aim to achieve with our game demo."
   },
   {
-    "objectID": "decisions/20241014-app-updater.html#the-infrequent-use-case",
-    "href": "decisions/20241014-app-updater.html#the-infrequent-use-case",
-    "title": "Proposed: Updater No-Op Implementation Using Velopack",
+    "objectID": "decisions/20240623-talk-length-prototypes.html#the-benefits",
+    "href": "decisions/20240623-talk-length-prototypes.html#the-benefits",
+    "title": "Proposed: Talk Length Game Prototypes",
     "section": "",
-    "text": "Users who rarely update might prefer more detailed visuals."
+    "text": "Attention Span: An 18-minute demo aligns well with the average person’s attention span. It’s long enough to immerse the player in the game world and showcase its features, but not so long that it risks losing the player’s interest.\nDepth of Experience: This length allows us to provide a substantial preview of the game without overwhelming the player. We can introduce the main gameplay mechanics, narrative elements, and unique features within this timeframe.\nUnique Selling Point: Having a TED talk-length game demo could serve as a unique selling point, distinguishing V-Sekai from other VRSNS."
   },
   {
-    "objectID": "decisions/20241014-app-updater.html#in-core-and-done-by-us",
-    "href": "decisions/20241014-app-updater.html#in-core-and-done-by-us",
-    "title": "Proposed: Updater No-Op Implementation Using Velopack",
+    "objectID": "decisions/20240623-talk-length-prototypes.html#the-downsides",
+    "href": "decisions/20240623-talk-length-prototypes.html#the-downsides",
+    "title": "Proposed: Talk Length Game Prototypes",
     "section": "",
-    "text": "Handled internally to ensure seamless integration with Velopack."
+    "text": "Not One-Size-Fits-All: The length of a TED talk may not be suitable for all types of games. Some games might require longer playtimes to fully appreciate their depth and complexity.\nPlayer Preferences: Some players might prefer shorter or longer demos. We would need to ensure that our target audience is comfortable with this length."
   },
   {
-    "objectID": "decisions/20241014-app-updater.html#status",
-    "href": "decisions/20241014-app-updater.html#status",
-    "title": "Proposed: Updater No-Op Implementation Using Velopack",
+    "objectID": "decisions/20240623-talk-length-prototypes.html#the-road-not-taken",
+    "href": "decisions/20240623-talk-length-prototypes.html#the-road-not-taken",
+    "title": "Proposed: Talk Length Game Prototypes",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "Alternative lengths for the game demo could be considered, such as the length of a typical movie or TV episode."
   },
   {
-    "objectID": "decisions/20241014-app-updater.html#decision-makers",
-    "href": "decisions/20241014-app-updater.html#decision-makers",
-    "title": "Proposed: Updater No-Op Implementation Using Velopack",
+    "objectID": "decisions/20240623-talk-length-prototypes.html#the-infrequent-use-case",
+    "href": "decisions/20240623-talk-length-prototypes.html#the-infrequent-use-case",
+    "title": "Proposed: Talk Length Game Prototypes",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "This proposal may not apply to games that are designed to be played in short bursts."
   },
   {
-    "objectID": "decisions/20241014-app-updater.html#tags",
-    "href": "decisions/20241014-app-updater.html#tags",
-    "title": "Proposed: Updater No-Op Implementation Using Velopack",
+    "objectID": "decisions/20240623-talk-length-prototypes.html#in-core-and-done-by-us",
+    "href": "decisions/20240623-talk-length-prototypes.html#in-core-and-done-by-us",
+    "title": "Proposed: Talk Length Game Prototypes",
     "section": "",
-    "text": "V-Sekai\nUpdater\nVelopack"
+    "text": "This proposal would be implemented by the V-Sekai development team."
   },
   {
-    "objectID": "decisions/20241014-app-updater.html#further-reading",
-    "href": "decisions/20241014-app-updater.html#further-reading",
-    "title": "Proposed: Updater No-Op Implementation Using Velopack",
+    "objectID": "decisions/20240623-talk-length-prototypes.html#status",
+    "href": "decisions/20240623-talk-length-prototypes.html#status",
+    "title": "Proposed: Talk Length Game Prototypes",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub repository.\nV-Sekai/v-sekai-game - Project page on GitHub.\nVelopack Documentation - Learn more about how Velopack manages application updates.\n\nAI assistant Aria assisted with this article."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20210622-shadermotion-to-godot-engine.html",
-    "href": "decisions/20210622-shadermotion-to-godot-engine.html",
-    "title": "Proposed: Convert #shadermotion to be played in Godot Engine",
+    "objectID": "decisions/20240623-talk-length-prototypes.html#decision-makers",
+    "href": "decisions/20240623-talk-length-prototypes.html#decision-makers",
+    "title": "Proposed: Talk Length Game Prototypes",
     "section": "",
-    "text": "We want a better way of importing animations to Godot Engine. Unfortunately, there is no standard way to exchange motion from other places to Godot and work interchangeably on different characters.\n\n\n\n#shadermotion files in video format provide an excellent way to record motion. However, we want the ability to play it back in Godot Engine onto a VRM character.\n\n\n\nInstall youtube-dl and ffmpeg with scoop\nscoop install youtube-dl ffmpeg\nConvert #shadermotion videos into WebM VP9.\nyoutube-dl https://www.youtube.com/playlist?list=PLmwqDOin_Zt4WCMWqoK6SdHlg0C_WeCP6 --audio-format wav --format webm --recode-video webm\nCrop the preview frame of the video for the left and the right side.\nffmpeg -i \"NNNN.webm\" \"-filter:v\" \"crop=in_w*(1-0.925):ih:0:0,fps=60,scale=24x180:flags=lanczos+full_chroma_inp\" shader_motion_character_00.webm\nffmpeg -i \"NNNN.webm\" \"-filter:v\" \"crop=in_w*(1-0.925):in_h:in_w:in_h,fps=60,scale=24x180:flags=lanczos+full_chroma_inp\" shader_motion_character_0\n\n\n\nBuild godot-cpp\ngodot.windows.opt.tools.64.exe --gdnative-generate-json-api api.json\ngodot.windows.opt.tools.64.exe --gdnative-generate-json-builtin-api builtin_api.json\n# copy to godot-cpp\n# compile godot-cpp\n# Use instructions for 4\n# https://github.com/GodotVR/godot_openvr/pull/123#issue-658898644\nscons p=windows target=release -j16 target=release generate_bindings=yes\n# compile gdnative-video-decoder\nscons platform=win64 target=release -j16\n\n\n\n\nCan interchange motions\n\n\n\n\n\nComplexity\n\n\n\n\nNot trivial.\n\n\n\nThe ability to give motion to 3d characters or NPCS is important.\nThe ability to interchange pose is important.\n\n\n\n\nhttps://motion.chibifire.com\nhttps://github.com/ytdl-org/youtube-dl\nhttps://github.com/FFmpeg/FFmpeg\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20210622-shadermotion-to-godot-engine.html#context-and-problem-statement",
-    "href": "decisions/20210622-shadermotion-to-godot-engine.html#context-and-problem-statement",
-    "title": "Proposed: Convert #shadermotion to be played in Godot Engine",
+    "objectID": "decisions/20240623-talk-length-prototypes.html#tags",
+    "href": "decisions/20240623-talk-length-prototypes.html#tags",
+    "title": "Proposed: Talk Length Game Prototypes",
     "section": "",
-    "text": "We want a better way of importing animations to Godot Engine. Unfortunately, there is no standard way to exchange motion from other places to Godot and work interchangeably on different characters."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20210622-shadermotion-to-godot-engine.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20210622-shadermotion-to-godot-engine.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: Convert #shadermotion to be played in Godot Engine",
+    "objectID": "decisions/20240623-talk-length-prototypes.html#further-reading",
+    "href": "decisions/20240623-talk-length-prototypes.html#further-reading",
+    "title": "Proposed: Talk Length Game Prototypes",
     "section": "",
-    "text": "#shadermotion files in video format provide an excellent way to record motion. However, we want the ability to play it back in Godot Engine onto a VRM character."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - The GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis proposal was assisted by AI assistant Aria."
   },
   {
-    "objectID": "decisions/20210622-shadermotion-to-godot-engine.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20210622-shadermotion-to-godot-engine.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Convert #shadermotion to be played in Godot Engine",
+    "objectID": "decisions/20240325-table-avatar-embedded-xmp.html",
+    "href": "decisions/20240325-table-avatar-embedded-xmp.html",
+    "title": "Proposed: for 3d Asset Schema Design and Database Backend Selection",
     "section": "",
-    "text": "Install youtube-dl and ffmpeg with scoop\nscoop install youtube-dl ffmpeg\nConvert #shadermotion videos into WebM VP9.\nyoutube-dl https://www.youtube.com/playlist?list=PLmwqDOin_Zt4WCMWqoK6SdHlg0C_WeCP6 --audio-format wav --format webm --recode-video webm\nCrop the preview frame of the video for the left and the right side.\nffmpeg -i \"NNNN.webm\" \"-filter:v\" \"crop=in_w*(1-0.925):ih:0:0,fps=60,scale=24x180:flags=lanczos+full_chroma_inp\" shader_motion_character_00.webm\nffmpeg -i \"NNNN.webm\" \"-filter:v\" \"crop=in_w*(1-0.925):in_h:in_w:in_h,fps=60,scale=24x180:flags=lanczos+full_chroma_inp\" shader_motion_character_0"
+    "text": "The current project involves creating a schema for storing VRM license data, GLTF 3d assets, and other metadata. The data will be stored in a public.cbf_avatar table with fields such as created_at, gltf_embedded, id, and xmp.\n\n\n\nThe main challenge is deciding on the appropriate database backend and determining whether storing large files in a relational database is a good practice.\n\n\n\nCREATE TABLE public.cbf_avatar (\n    created_at timestamptz DEFAULT now() NOT NULL,\n    gltf_embedded jsonb DEFAULT '{}'::jsonb NOT NULL,\n    id uuid DEFAULT gen_random_uuid() NOT NULL,\n    xmp jsonb DEFAULT '{}'::jsonb NOT NULL,\n    CONSTRAINT cbf_avatar_pkey PRIMARY KEY (id)\n);\nThe proposed solution involves using either Supabase PostgreSQL or FoundationDB with SQLite as the database backend. The gltf_embedded field will store GLTF 3d asset data as JSON binary, while the xmp field will store VRM license data and other metadata.\n\n\n\n\nThe use of JSON binary allows for efficient storage and retrieval of GLTF 3d assets.\nThe chosen database backends are robust and reliable, ensuring data integrity and consistency.\n\n\n\n\n\nStoring large files in a relational database could potentially lead to disk thrashing and other performance issues.\nFields in databases generally have a size limit, which could pose problems if the data exceeds this limit.\n\n\n\n\nAn alternative approach would be to store the large files in a separate file system and only keep references to these files in the database. However, this might complicate the data management process.\n\n\n\nThis schema design and database backend selection may not be suitable for applications that require extremely high performance or have strict limitations on data size.\n\n\n\nThe schema design and database backend selection will be implemented by the V-Sekai development team.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nPostgres Storing Large Text - A 2020 article suggesting that larger file storage in a relational database is okay.\n\nThis proposal was assisted by Aria, an AI assistant."
   },
   {
-    "objectID": "decisions/20210622-shadermotion-to-godot-engine.html#how-to-build-godot-video-decoder",
-    "href": "decisions/20210622-shadermotion-to-godot-engine.html#how-to-build-godot-video-decoder",
-    "title": "Proposed: Convert #shadermotion to be played in Godot Engine",
+    "objectID": "decisions/20240325-table-avatar-embedded-xmp.html#context",
+    "href": "decisions/20240325-table-avatar-embedded-xmp.html#context",
+    "title": "Proposed: for 3d Asset Schema Design and Database Backend Selection",
     "section": "",
-    "text": "Build godot-cpp\ngodot.windows.opt.tools.64.exe --gdnative-generate-json-api api.json\ngodot.windows.opt.tools.64.exe --gdnative-generate-json-builtin-api builtin_api.json\n# copy to godot-cpp\n# compile godot-cpp\n# Use instructions for 4\n# https://github.com/GodotVR/godot_openvr/pull/123#issue-658898644\nscons p=windows target=release -j16 target=release generate_bindings=yes\n# compile gdnative-video-decoder\nscons platform=win64 target=release -j16"
+    "text": "The current project involves creating a schema for storing VRM license data, GLTF 3d assets, and other metadata. The data will be stored in a public.cbf_avatar table with fields such as created_at, gltf_embedded, id, and xmp."
   },
   {
-    "objectID": "decisions/20210622-shadermotion-to-godot-engine.html#positive-consequences",
-    "href": "decisions/20210622-shadermotion-to-godot-engine.html#positive-consequences",
-    "title": "Proposed: Convert #shadermotion to be played in Godot Engine",
+    "objectID": "decisions/20240325-table-avatar-embedded-xmp.html#problem-statement",
+    "href": "decisions/20240325-table-avatar-embedded-xmp.html#problem-statement",
+    "title": "Proposed: for 3d Asset Schema Design and Database Backend Selection",
     "section": "",
-    "text": "Can interchange motions"
+    "text": "The main challenge is deciding on the appropriate database backend and determining whether storing large files in a relational database is a good practice."
   },
   {
-    "objectID": "decisions/20210622-shadermotion-to-godot-engine.html#negative-consequences",
-    "href": "decisions/20210622-shadermotion-to-godot-engine.html#negative-consequences",
-    "title": "Proposed: Convert #shadermotion to be played in Godot Engine",
+    "objectID": "decisions/20240325-table-avatar-embedded-xmp.html#proposed-solution",
+    "href": "decisions/20240325-table-avatar-embedded-xmp.html#proposed-solution",
+    "title": "Proposed: for 3d Asset Schema Design and Database Backend Selection",
     "section": "",
-    "text": "Complexity"
+    "text": "CREATE TABLE public.cbf_avatar (\n    created_at timestamptz DEFAULT now() NOT NULL,\n    gltf_embedded jsonb DEFAULT '{}'::jsonb NOT NULL,\n    id uuid DEFAULT gen_random_uuid() NOT NULL,\n    xmp jsonb DEFAULT '{}'::jsonb NOT NULL,\n    CONSTRAINT cbf_avatar_pkey PRIMARY KEY (id)\n);\nThe proposed solution involves using either Supabase PostgreSQL or FoundationDB with SQLite as the database backend. The gltf_embedded field will store GLTF 3d asset data as JSON binary, while the xmp field will store VRM license data and other metadata."
   },
   {
-    "objectID": "decisions/20210622-shadermotion-to-godot-engine.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20210622-shadermotion-to-godot-engine.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Convert #shadermotion to be played in Godot Engine",
+    "objectID": "decisions/20240325-table-avatar-embedded-xmp.html#benefits",
+    "href": "decisions/20240325-table-avatar-embedded-xmp.html#benefits",
+    "title": "Proposed: for 3d Asset Schema Design and Database Backend Selection",
     "section": "",
-    "text": "Not trivial."
+    "text": "The use of JSON binary allows for efficient storage and retrieval of GLTF 3d assets.\nThe chosen database backends are robust and reliable, ensuring data integrity and consistency."
   },
   {
-    "objectID": "decisions/20210622-shadermotion-to-godot-engine.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20210622-shadermotion-to-godot-engine.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Convert #shadermotion to be played in Godot Engine",
+    "objectID": "decisions/20240325-table-avatar-embedded-xmp.html#downsides",
+    "href": "decisions/20240325-table-avatar-embedded-xmp.html#downsides",
+    "title": "Proposed: for 3d Asset Schema Design and Database Backend Selection",
     "section": "",
-    "text": "The ability to give motion to 3d characters or NPCS is important.\nThe ability to interchange pose is important."
+    "text": "Storing large files in a relational database could potentially lead to disk thrashing and other performance issues.\nFields in databases generally have a size limit, which could pose problems if the data exceeds this limit."
   },
   {
-    "objectID": "decisions/20210622-shadermotion-to-godot-engine.html#references",
-    "href": "decisions/20210622-shadermotion-to-godot-engine.html#references",
-    "title": "Proposed: Convert #shadermotion to be played in Godot Engine",
+    "objectID": "decisions/20240325-table-avatar-embedded-xmp.html#the-road-not-taken",
+    "href": "decisions/20240325-table-avatar-embedded-xmp.html#the-road-not-taken",
+    "title": "Proposed: for 3d Asset Schema Design and Database Backend Selection",
     "section": "",
-    "text": "https://motion.chibifire.com\nhttps://github.com/ytdl-org/youtube-dl\nhttps://github.com/FFmpeg/FFmpeg"
+    "text": "An alternative approach would be to store the large files in a separate file system and only keep references to these files in the database. However, this might complicate the data management process."
   },
   {
-    "objectID": "decisions/20210622-shadermotion-to-godot-engine.html#derivative-license",
-    "href": "decisions/20210622-shadermotion-to-godot-engine.html#derivative-license",
-    "title": "Proposed: Convert #shadermotion to be played in Godot Engine",
+    "objectID": "decisions/20240325-table-avatar-embedded-xmp.html#infrequent-use-case",
+    "href": "decisions/20240325-table-avatar-embedded-xmp.html#infrequent-use-case",
+    "title": "Proposed: for 3d Asset Schema Design and Database Backend Selection",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "This schema design and database backend selection may not be suitable for applications that require extremely high performance or have strict limitations on data size."
   },
   {
-    "objectID": "decisions/20230803-subrepo-addon-management.html",
-    "href": "decisions/20230803-subrepo-addon-management.html",
-    "title": "Accepted: Git Subrepo Addon Management",
+    "objectID": "decisions/20240325-table-avatar-embedded-xmp.html#in-core-and-done-by-us",
+    "href": "decisions/20240325-table-avatar-embedded-xmp.html#in-core-and-done-by-us",
+    "title": "Proposed: for 3d Asset Schema Design and Database Backend Selection",
     "section": "",
-    "text": "We are currently managing separate repositories for each addon in the V-Sekai game. This has led to difficulties in synchronizing updates and maintaining consistency across different components of the project.\n\n\n\nWe propose to continue maintaining separate repositories for each addon, but use Git subrepo to merge them into the main V-Sekai game repository. This would result in the following structure:\nv-sekai-game\n│\n└───addons\n    │\n    ├───vrm (from godot-vrm/only-addon)\n    │\n    └───Godot-MToon-Shader (from Godot-MToon-Shader)\nThis way, all addons will be part of the main game repository but can still be managed independently.\n\n\n\nThe implementation will involve the following steps:\n\nChanges are made in the respective addon repositories.\nThese changes are then merged into the main V-Sekai game repository using Git subrepo.\n\nThis ensures that the addons remain up-to-date with their respective repositories.\n\n\n\n\nStreamlined workflow for managing addons.\nEasier synchronization of updates across different components of the project.\nReduced complexity in project management.\n\n\n\n\n\nInitial setup may require some time and effort.\nDevelopers will need to adapt to the new workflow.\n\n\n\n\nPreviously, we considered maintaining separate repositories for each addon without using Git subrepo. However, this approach was discarded due to the difficulties in synchronizing updates and maintaining consistency across different components of the project.\n\n\n\nNo, this enhancement is fundamental to the project structure and cannot be worked around with a few lines of script.\n\n\n\nYes, this change affects the core structure of our project and should therefore be implemented by us to ensure consistency and control over the project.\n\n\n\n\nV-Sekai"
+    "text": "The schema design and database backend selection will be implemented by the V-Sekai development team."
   },
   {
-    "objectID": "decisions/20230803-subrepo-addon-management.html#context-and-problem-statement",
-    "href": "decisions/20230803-subrepo-addon-management.html#context-and-problem-statement",
-    "title": "Accepted: Git Subrepo Addon Management",
+    "objectID": "decisions/20240325-table-avatar-embedded-xmp.html#status",
+    "href": "decisions/20240325-table-avatar-embedded-xmp.html#status",
+    "title": "Proposed: for 3d Asset Schema Design and Database Backend Selection",
     "section": "",
-    "text": "We are currently managing separate repositories for each addon in the V-Sekai game. This has led to difficulties in synchronizing updates and maintaining consistency across different components of the project."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20230803-subrepo-addon-management.html#proposed-solution",
-    "href": "decisions/20230803-subrepo-addon-management.html#proposed-solution",
-    "title": "Accepted: Git Subrepo Addon Management",
+    "objectID": "decisions/20240325-table-avatar-embedded-xmp.html#decision-makers",
+    "href": "decisions/20240325-table-avatar-embedded-xmp.html#decision-makers",
+    "title": "Proposed: for 3d Asset Schema Design and Database Backend Selection",
     "section": "",
-    "text": "We propose to continue maintaining separate repositories for each addon, but use Git subrepo to merge them into the main V-Sekai game repository. This would result in the following structure:\nv-sekai-game\n│\n└───addons\n    │\n    ├───vrm (from godot-vrm/only-addon)\n    │\n    └───Godot-MToon-Shader (from Godot-MToon-Shader)\nThis way, all addons will be part of the main game repository but can still be managed independently."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20230803-subrepo-addon-management.html#implementation",
-    "href": "decisions/20230803-subrepo-addon-management.html#implementation",
-    "title": "Accepted: Git Subrepo Addon Management",
+    "objectID": "decisions/20240325-table-avatar-embedded-xmp.html#tags",
+    "href": "decisions/20240325-table-avatar-embedded-xmp.html#tags",
+    "title": "Proposed: for 3d Asset Schema Design and Database Backend Selection",
     "section": "",
-    "text": "The implementation will involve the following steps:\n\nChanges are made in the respective addon repositories.\nThese changes are then merged into the main V-Sekai game repository using Git subrepo.\n\nThis ensures that the addons remain up-to-date with their respective repositories."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20230803-subrepo-addon-management.html#positive-consequences",
-    "href": "decisions/20230803-subrepo-addon-management.html#positive-consequences",
-    "title": "Accepted: Git Subrepo Addon Management",
+    "objectID": "decisions/20240325-table-avatar-embedded-xmp.html#further-reading",
+    "href": "decisions/20240325-table-avatar-embedded-xmp.html#further-reading",
+    "title": "Proposed: for 3d Asset Schema Design and Database Backend Selection",
     "section": "",
-    "text": "Streamlined workflow for managing addons.\nEasier synchronization of updates across different components of the project.\nReduced complexity in project management."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nPostgres Storing Large Text - A 2020 article suggesting that larger file storage in a relational database is okay.\n\nThis proposal was assisted by Aria, an AI assistant."
   },
   {
-    "objectID": "decisions/20230803-subrepo-addon-management.html#negative-consequences",
-    "href": "decisions/20230803-subrepo-addon-management.html#negative-consequences",
-    "title": "Accepted: Git Subrepo Addon Management",
+    "objectID": "decisions/20240406-web-based-explore.html",
+    "href": "decisions/20240406-web-based-explore.html",
+    "title": "Proposed: Web-Based Exploration of V-Sekai",
     "section": "",
-    "text": "Initial setup may require some time and effort.\nDevelopers will need to adapt to the new workflow."
+    "text": "Recently, a discussion arose regarding the potential for creating a web version of V-Sekai. The concept involves utilizing WebAssembly (wasm) for this endeavor. Additionally, there is interest in integrating WebRTC with both native and web platforms.\n\n\n\nThe current iteration of V-Sekai lacks web accessibility, limiting its reach and usability. Furthermore, challenges exist concerning shared array buffer accessibility on Safari and access to ad networks, both of which are vital for online games.\n\n\n\nWe propose to construct a web version of V-Sekai using wasm. This process will necessitate overcoming the shared array buffer accessibility issue on Safari and ensuring access to ad networks.\n\n\n\n\nEnhanced accessibility and reach for V-Sekai.\nImproved user experience by allowing access from any device equipped with a web browser.\nPotential revenue increase through ad networks.\n\n\n\n\n\nPotential performance issues due to operation on a web platform.\nPossible compatibility issues across different browsers.\n\n\n\n\nAn alternative approach would be maintaining an exclusive focus on the native platform. However, this would restrict V-Sekai’s reach and potential for growth.\n\n\n\nThis proposal will significantly benefit users who prefer or only have access to the web platform.\n\n\n\nThe V-Sekai development team will undertake this project.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20230803-subrepo-addon-management.html#option-graveyard",
-    "href": "decisions/20230803-subrepo-addon-management.html#option-graveyard",
-    "title": "Accepted: Git Subrepo Addon Management",
+    "objectID": "decisions/20240406-web-based-explore.html#context",
+    "href": "decisions/20240406-web-based-explore.html#context",
+    "title": "Proposed: Web-Based Exploration of V-Sekai",
     "section": "",
-    "text": "Previously, we considered maintaining separate repositories for each addon without using Git subrepo. However, this approach was discarded due to the difficulties in synchronizing updates and maintaining consistency across different components of the project."
+    "text": "Recently, a discussion arose regarding the potential for creating a web version of V-Sekai. The concept involves utilizing WebAssembly (wasm) for this endeavor. Additionally, there is interest in integrating WebRTC with both native and web platforms."
   },
   {
-    "objectID": "decisions/20230803-subrepo-addon-management.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230803-subrepo-addon-management.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Accepted: Git Subrepo Addon Management",
+    "objectID": "decisions/20240406-web-based-explore.html#problem-statement",
+    "href": "decisions/20240406-web-based-explore.html#problem-statement",
+    "title": "Proposed: Web-Based Exploration of V-Sekai",
     "section": "",
-    "text": "No, this enhancement is fundamental to the project structure and cannot be worked around with a few lines of script."
+    "text": "The current iteration of V-Sekai lacks web accessibility, limiting its reach and usability. Furthermore, challenges exist concerning shared array buffer accessibility on Safari and access to ad networks, both of which are vital for online games."
   },
   {
-    "objectID": "decisions/20230803-subrepo-addon-management.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230803-subrepo-addon-management.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Accepted: Git Subrepo Addon Management",
+    "objectID": "decisions/20240406-web-based-explore.html#proposal",
+    "href": "decisions/20240406-web-based-explore.html#proposal",
+    "title": "Proposed: Web-Based Exploration of V-Sekai",
     "section": "",
-    "text": "Yes, this change affects the core structure of our project and should therefore be implemented by us to ensure consistency and control over the project."
+    "text": "We propose to construct a web version of V-Sekai using wasm. This process will necessitate overcoming the shared array buffer accessibility issue on Safari and ensuring access to ad networks."
   },
   {
-    "objectID": "decisions/20230803-subrepo-addon-management.html#references",
-    "href": "decisions/20230803-subrepo-addon-management.html#references",
-    "title": "Accepted: Git Subrepo Addon Management",
+    "objectID": "decisions/20240406-web-based-explore.html#benefits",
+    "href": "decisions/20240406-web-based-explore.html#benefits",
+    "title": "Proposed: Web-Based Exploration of V-Sekai",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Enhanced accessibility and reach for V-Sekai.\nImproved user experience by allowing access from any device equipped with a web browser.\nPotential revenue increase through ad networks."
   },
   {
-    "objectID": "decisions/20230505-polygon-mesh-based-sculpting-tools.html",
-    "href": "decisions/20230505-polygon-mesh-based-sculpting-tools.html",
-    "title": "Proposed: VR design application for V-Sekai",
+    "objectID": "decisions/20240406-web-based-explore.html#downsides",
+    "href": "decisions/20240406-web-based-explore.html#downsides",
+    "title": "Proposed: Web-Based Exploration of V-Sekai",
     "section": "",
-    "text": "Status: proposed \nDeciders: V-Sekai,fire,\nTags: V-Sekai,ChatGPT-4,\n\n\n\n\nFind or create a VR design application offering a variety of powerful polygon mesh-based sculpting tools, suitable for both aspiring creatives and experienced 3D artists.\n\n\n\nCurrently, V-Sekai lacks a comprehensive VR design application that provides polygon mesh-based sculpting tools for users with varying levels of experience. How can we integrate such a tool to enhance the creative capabilities of our users?\n\n\n\nIntegrate a powerful VR design application, such as Gravity Sketch, which offers a wide range of polygon mesh-based sculpting tools. This will cater to both beginners and experienced 3D artists, allowing them to create intricate designs within the V-Sekai environment.\n\n\n\n\nResearch available VR design applications that meet the requirements.\nEvaluate the compatibility of the chosen application with V-Sekai.\nDevelop an integration plan, including necessary API calls and user interface adjustments.\nImplement the integration, ensuring seamless functionality within V-Sekai.\nTest the integrated application with various user profiles to ensure usability and performance.\n\n\n\n\n\nEnhanced creative capabilities for V-Sekai users.\nAttraction of a wider user base, including experienced 3D artists.\nImproved user satisfaction and engagement.\n\n\n\n\n\nPotential increase in system requirements for V-Sekai.\nAdditional development time and resources required for integration.\n\n\n\n\n\nDeveloping a custom VR design application from scratch (time-consuming and resource-intensive).\n\n\n\n\nNo, as the enhancement involves integrating a complex VR design application that cannot be achieved through a simple script workaround.\n\n\n\nYes, integrating a powerful VR design application will significantly enhance the creative capabilities of V-Sekai users, making it a core feature that directly impacts user experience and satisfaction.\n\n\n\n\nV-Sekai\nCassie on Github: https://github.com/V-Sekai/cassie\nShapelab by Leopoly on Steam\nGravity Sketch on Steam\nSubstance 3D Modeler 2023 on Steam: https://store.steampowered.com/app/1745780/Substance_3D_Modeler_2023/"
+    "text": "Potential performance issues due to operation on a web platform.\nPossible compatibility issues across different browsers."
   },
   {
-    "objectID": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#metadata",
-    "href": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#metadata",
-    "title": "Proposed: VR design application for V-Sekai",
+    "objectID": "decisions/20240406-web-based-explore.html#alternative-path",
+    "href": "decisions/20240406-web-based-explore.html#alternative-path",
+    "title": "Proposed: Web-Based Exploration of V-Sekai",
     "section": "",
-    "text": "Status: proposed \nDeciders: V-Sekai,fire,\nTags: V-Sekai,ChatGPT-4,"
+    "text": "An alternative approach would be maintaining an exclusive focus on the native platform. However, this would restrict V-Sekai’s reach and potential for growth."
   },
   {
-    "objectID": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#context-and-problem-statement",
-    "href": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#context-and-problem-statement",
-    "title": "Proposed: VR design application for V-Sekai",
+    "objectID": "decisions/20240406-web-based-explore.html#infrequent-use-case",
+    "href": "decisions/20240406-web-based-explore.html#infrequent-use-case",
+    "title": "Proposed: Web-Based Exploration of V-Sekai",
     "section": "",
-    "text": "Find or create a VR design application offering a variety of powerful polygon mesh-based sculpting tools, suitable for both aspiring creatives and experienced 3D artists."
+    "text": "This proposal will significantly benefit users who prefer or only have access to the web platform."
   },
   {
-    "objectID": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#describe-the-problem-or-limitation-you-have-in-your-project-e.g.-in-free-form-using-two-to-three-sentences.-consider-articulating-the-case-in-the-form-of-a-question.",
-    "href": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#describe-the-problem-or-limitation-you-have-in-your-project-e.g.-in-free-form-using-two-to-three-sentences.-consider-articulating-the-case-in-the-form-of-a-question.",
-    "title": "Proposed: VR design application for V-Sekai",
+    "objectID": "decisions/20240406-web-based-explore.html#core-implementation-by-us",
+    "href": "decisions/20240406-web-based-explore.html#core-implementation-by-us",
+    "title": "Proposed: Web-Based Exploration of V-Sekai",
     "section": "",
-    "text": "Currently, V-Sekai lacks a comprehensive VR design application that provides polygon mesh-based sculpting tools for users with varying levels of experience. How can we integrate such a tool to enhance the creative capabilities of our users?"
+    "text": "The V-Sekai development team will undertake this project."
   },
   {
-    "objectID": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: VR design application for V-Sekai",
+    "objectID": "decisions/20240406-web-based-explore.html#status",
+    "href": "decisions/20240406-web-based-explore.html#status",
+    "title": "Proposed: Web-Based Exploration of V-Sekai",
     "section": "",
-    "text": "Integrate a powerful VR design application, such as Gravity Sketch, which offers a wide range of polygon mesh-based sculpting tools. This will cater to both beginners and experienced 3D artists, allowing them to create intricate designs within the V-Sekai environment."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: VR design application for V-Sekai",
+    "objectID": "decisions/20240406-web-based-explore.html#decision-makers",
+    "href": "decisions/20240406-web-based-explore.html#decision-makers",
+    "title": "Proposed: Web-Based Exploration of V-Sekai",
     "section": "",
-    "text": "Research available VR design applications that meet the requirements.\nEvaluate the compatibility of the chosen application with V-Sekai.\nDevelop an integration plan, including necessary API calls and user interface adjustments.\nImplement the integration, ensuring seamless functionality within V-Sekai.\nTest the integrated application with various user profiles to ensure usability and performance."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#positive-consequences",
-    "href": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#positive-consequences",
-    "title": "Proposed: VR design application for V-Sekai",
+    "objectID": "decisions/20240406-web-based-explore.html#tags",
+    "href": "decisions/20240406-web-based-explore.html#tags",
+    "title": "Proposed: Web-Based Exploration of V-Sekai",
     "section": "",
-    "text": "Enhanced creative capabilities for V-Sekai users.\nAttraction of a wider user base, including experienced 3D artists.\nImproved user satisfaction and engagement."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#negative-consequences",
-    "href": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#negative-consequences",
-    "title": "Proposed: VR design application for V-Sekai",
+    "objectID": "decisions/20240406-web-based-explore.html#further-reading",
+    "href": "decisions/20240406-web-based-explore.html#further-reading",
+    "title": "Proposed: Web-Based Exploration of V-Sekai",
     "section": "",
-    "text": "Potential increase in system requirements for V-Sekai.\nAdditional development time and resources required for integration."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#option-graveyard",
-    "href": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#option-graveyard",
-    "title": "Proposed: VR design application for V-Sekai",
-    "section": "",
-    "text": "Developing a custom VR design application from scratch (time-consuming and resource-intensive)."
-  },
-  {
-    "objectID": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: VR design application for V-Sekai",
-    "section": "",
-    "text": "No, as the enhancement involves integrating a complex VR design application that cannot be achieved through a simple script workaround."
-  },
-  {
-    "objectID": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: VR design application for V-Sekai",
-    "section": "",
-    "text": "Yes, integrating a powerful VR design application will significantly enhance the creative capabilities of V-Sekai users, making it a core feature that directly impacts user experience and satisfaction."
-  },
-  {
-    "objectID": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#references",
-    "href": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#references",
-    "title": "Proposed: VR design application for V-Sekai",
-    "section": "",
-    "text": "V-Sekai\nCassie on Github: https://github.com/V-Sekai/cassie\nShapelab by Leopoly on Steam\nGravity Sketch on Steam\nSubstance 3D Modeler 2023 on Steam: https://store.steampowered.com/app/1745780/Substance_3D_Modeler_2023/"
-  },
-  {
-    "objectID": "decisions/20220531-truenas-scale.html",
-    "href": "decisions/20220531-truenas-scale.html",
-    "title": "Rejected: To create a deployment kit use truescale to host gocd agents for cicd.",
-    "section": "",
-    "text": "proposed\ndraft\nrejected\naccepted\ndeprecated\nsuperseded by\n\n\n\n\nV-Sekai,fire,\n\n\n\nV-Sekai,\n\n\n\nI want to run docker containers in a semi production way.\n\n\n\nUse truenas scale to host gocd agents for cicd.\n\n\n\nAdd a new storage node from hosts.\n\n\n\n\ninstall truenas scale\ninstall truenas charts\nLaunch docker image\nimage: groupsinfra/gocd-agent-centos-8-groups\ntag: v20.7.0-groups-0.5.3\nAdd environment variables\nGO_SERVER_URL=“https://ci.v-sekai.cloud/go/”\nAdd host volumes for\n/go\n/mnt/homego # On truenas\n\n\n\n\n\n??? Enable the agent\n??? Add the environment to the agent\n??? Add the agent to the environment.\n\n\n\nCan deploy this setup to digital ocean.\n\n\n\nNo response\n\n\n\nNo response\n\n\n\nNot a few lines script.\n\n\n\nI know how to do this and I don’t want to pay for it.\n\n\n\n\nV-Sekai\nagent_auto_register\n\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
-  },
-  {
-    "objectID": "decisions/20220531-truenas-scale.html#truenas-scale",
-    "href": "decisions/20220531-truenas-scale.html#truenas-scale",
-    "title": "Rejected: To create a deployment kit use truescale to host gocd agents for cicd.",
-    "section": "",
-    "text": "install truenas scale\ninstall truenas charts\nLaunch docker image\nimage: groupsinfra/gocd-agent-centos-8-groups\ntag: v20.7.0-groups-0.5.3\nAdd environment variables\nGO_SERVER_URL=“https://ci.v-sekai.cloud/go/”\nAdd host volumes for\n/go\n/mnt/homego # On truenas"
-  },
-  {
-    "objectID": "decisions/20220531-truenas-scale.html#gocd-config",
-    "href": "decisions/20220531-truenas-scale.html#gocd-config",
-    "title": "Rejected: To create a deployment kit use truescale to host gocd agents for cicd.",
-    "section": "",
-    "text": "??? Enable the agent\n??? Add the environment to the agent\n??? Add the agent to the environment.\n\n\n\nCan deploy this setup to digital ocean.\n\n\n\nNo response\n\n\n\nNo response\n\n\n\nNot a few lines script.\n\n\n\nI know how to do this and I don’t want to pay for it.\n\n\n\n\nV-Sekai\nagent_auto_register\n\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
-  },
-  {
-    "objectID": "decisions/20240502-gltf-fbx-tscn-vrm.html",
-    "href": "decisions/20240502-gltf-fbx-tscn-vrm.html",
-    "title": "Proposed: Workflows for 3D Model Conversion",
+    "objectID": "decisions/20240705-rpg_town.html",
+    "href": "decisions/20240705-rpg_town.html",
+    "title": "Proposal: RPG Town in V-Sekai",
     "section": "",
-    "text": "In the realm of 3D modeling and animation, there are numerous file formats each with their own unique features and capabilities. However, not all software can support every format, leading to a need for conversion tools.\n\n\n\nThe challenge lies in creating a tool that can convert between different 3D model formats, specifically from glTF to FBX, while maintaining the integrity of the original model.\n\n\n\nWe propose to develop a workflow for 3D model conversion using the Elixir Membrane Framework.\nThe primary function of this tool would be to take a glTF file as input and export it as an FBX file. This tool could also potentially support other formats such as USD, Godot Engine tscn, and VRM.\nAdditionally, we propose a feature where the tool can take a post and return a result. This could be useful for batch processing or automated tasks.\nTo make these services accessible, we plan to expose them via a Tailscale funnel.\nFor many of the flows, we can use USD to glTF, then glTF to Godot Engine, and finally Godot Engine to VRM and back. This approach allows us to leverage existing conversion libraries and tools, reducing the amount of custom code we need to write.\ngraph LR\n    A[USD] --&gt; B[glTF]\n    B --&gt; C[Godot Engine]\n    C --&gt; D[VRM]\n    D --&gt; B\n\n\n\nThis tool would greatly simplify the process of converting 3D models between different formats, saving time and reducing potential errors.\n\n\n\nThere may be some loss of data or quality during the conversion process, depending on the complexity of the model and the capabilities of the target format.\n\n\n\nAlternative solutions could involve using existing conversion tools or plugins, but these may not offer the same level of control or flexibility as a custom-built tool.\n\n\n\nWhile the primary use case is for converting glTF to FBX, the tool could also be used for other less common conversions.\n\n\n\nThis tool would be developed in-house by the V-Sekai development team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "Researchers have been studying emergent AI behaviors in sandbox environments inspired by games like The Sims. This proposal aims to leverage these insights to enhance the V-Sekai game, which features 25 NPCs running goal-task hierarchical task network (GT-HTN).\n\n\n\nThe challenge is to create a dynamic and engaging environment where NPCs exhibit complex behaviors that can be streamed 24/7. The goal is to make the game interesting enough for Twitch streaming while ensuring the NPCs’ actions are meaningful and not just random clicks.\n\n\n\nFor HTN implementation, we will study the GOAP framework from Vinicius Gerevini’s GitHub and define tasks and goals for NPCs using predicate, subject-object triplet variables, or method calls. Networking and traffic simulation will involve implementing network traffic tests to ensure smooth operation and using tools like Microsoft’s GraphRAG for generating predicate and subject objects. For LLM integration, we will integrate Large Language Models (LLMs) to set goals for NPCs based on Twitch chat summaries, using LLMs to help plan but not directly control NPC actions.\n\n\nNPC Interaction Flow:\ngraph TD;\n    A[Start] --&gt; B[Define Goals];\n    B --&gt; C[Assign Tasks];\n    C --&gt; D[Execute Actions];\n    D --&gt; E[Monitor and Adjust];\n    E --&gt; F[Stream to Twitch];\nSystem Architecture:\ngraph LR;\n    A[User Input] --&gt; B[LLM];\n    B --&gt; C[Goal Setting];\n    C --&gt; D[GTHTN Engine];\n    D --&gt; E[NPC Actions];\n    E --&gt; F[Twitch Stream];\n\n\n\n\nCreating an interactive and dynamic environment suitable for Twitch streaming will result in engaging content. It allows for complex and unpredictable NPC interactions, fostering emergent behaviors. Additionally, it engages the community by summarizing Twitch chat to set NPC goals.\n\n\n\nImplementing and maintaining such a system can be challenging due to its complexity. It also requires significant computational resources for real-time processing and streaming.\n\n\n\nManually setting NPC goals and actions would be less dynamic and engaging. Using simpler AI models may not exhibit complex behaviors.\n\n\n\nRunning the game without Twitch integration, focusing solely on NPC interactions, represents an infrequent use case.\n\n\n\nWe will implement the GOAP framework within the V-Sekai game and integrate LLMs for goal setting based on community input.\n\n\n\nStatus: Proposed \n\n\n\nThe decision makers for this proposal are the V-Sekai development team.\n\n\n\nV-Sekai\n\n\n\nFor more information, you can visit the V-Sekai GitHub account, which focuses on social VR functionality for the Godot Engine. You can also check out the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240502-gltf-fbx-tscn-vrm.html#the-context",
-    "href": "decisions/20240502-gltf-fbx-tscn-vrm.html#the-context",
-    "title": "Proposed: Workflows for 3D Model Conversion",
+    "objectID": "decisions/20240705-rpg_town.html#the-context",
+    "href": "decisions/20240705-rpg_town.html#the-context",
+    "title": "Proposal: RPG Town in V-Sekai",
     "section": "",
-    "text": "In the realm of 3D modeling and animation, there are numerous file formats each with their own unique features and capabilities. However, not all software can support every format, leading to a need for conversion tools."
+    "text": "Researchers have been studying emergent AI behaviors in sandbox environments inspired by games like The Sims. This proposal aims to leverage these insights to enhance the V-Sekai game, which features 25 NPCs running goal-task hierarchical task network (GT-HTN)."
   },
   {
-    "objectID": "decisions/20240502-gltf-fbx-tscn-vrm.html#the-problem-statement",
-    "href": "decisions/20240502-gltf-fbx-tscn-vrm.html#the-problem-statement",
-    "title": "Proposed: Workflows for 3D Model Conversion",
+    "objectID": "decisions/20240705-rpg_town.html#the-problem-statement",
+    "href": "decisions/20240705-rpg_town.html#the-problem-statement",
+    "title": "Proposal: RPG Town in V-Sekai",
     "section": "",
-    "text": "The challenge lies in creating a tool that can convert between different 3D model formats, specifically from glTF to FBX, while maintaining the integrity of the original model."
+    "text": "The challenge is to create a dynamic and engaging environment where NPCs exhibit complex behaviors that can be streamed 24/7. The goal is to make the game interesting enough for Twitch streaming while ensuring the NPCs’ actions are meaningful and not just random clicks."
   },
   {
-    "objectID": "decisions/20240502-gltf-fbx-tscn-vrm.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240502-gltf-fbx-tscn-vrm.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Workflows for 3D Model Conversion",
+    "objectID": "decisions/20240705-rpg_town.html#describe-how-your-proposal-will-work",
+    "href": "decisions/20240705-rpg_town.html#describe-how-your-proposal-will-work",
+    "title": "Proposal: RPG Town in V-Sekai",
     "section": "",
-    "text": "We propose to develop a workflow for 3D model conversion using the Elixir Membrane Framework.\nThe primary function of this tool would be to take a glTF file as input and export it as an FBX file. This tool could also potentially support other formats such as USD, Godot Engine tscn, and VRM.\nAdditionally, we propose a feature where the tool can take a post and return a result. This could be useful for batch processing or automated tasks.\nTo make these services accessible, we plan to expose them via a Tailscale funnel.\nFor many of the flows, we can use USD to glTF, then glTF to Godot Engine, and finally Godot Engine to VRM and back. This approach allows us to leverage existing conversion libraries and tools, reducing the amount of custom code we need to write.\ngraph LR\n    A[USD] --&gt; B[glTF]\n    B --&gt; C[Godot Engine]\n    C --&gt; D[VRM]\n    D --&gt; B"
+    "text": "For HTN implementation, we will study the GOAP framework from Vinicius Gerevini’s GitHub and define tasks and goals for NPCs using predicate, subject-object triplet variables, or method calls. Networking and traffic simulation will involve implementing network traffic tests to ensure smooth operation and using tools like Microsoft’s GraphRAG for generating predicate and subject objects. For LLM integration, we will integrate Large Language Models (LLMs) to set goals for NPCs based on Twitch chat summaries, using LLMs to help plan but not directly control NPC actions.\n\n\nNPC Interaction Flow:\ngraph TD;\n    A[Start] --&gt; B[Define Goals];\n    B --&gt; C[Assign Tasks];\n    C --&gt; D[Execute Actions];\n    D --&gt; E[Monitor and Adjust];\n    E --&gt; F[Stream to Twitch];\nSystem Architecture:\ngraph LR;\n    A[User Input] --&gt; B[LLM];\n    B --&gt; C[Goal Setting];\n    C --&gt; D[GTHTN Engine];\n    D --&gt; E[NPC Actions];\n    E --&gt; F[Twitch Stream];"
   },
   {
-    "objectID": "decisions/20240502-gltf-fbx-tscn-vrm.html#the-benefits",
-    "href": "decisions/20240502-gltf-fbx-tscn-vrm.html#the-benefits",
-    "title": "Proposed: Workflows for 3D Model Conversion",
+    "objectID": "decisions/20240705-rpg_town.html#the-benefits",
+    "href": "decisions/20240705-rpg_town.html#the-benefits",
+    "title": "Proposal: RPG Town in V-Sekai",
     "section": "",
-    "text": "This tool would greatly simplify the process of converting 3D models between different formats, saving time and reducing potential errors."
+    "text": "Creating an interactive and dynamic environment suitable for Twitch streaming will result in engaging content. It allows for complex and unpredictable NPC interactions, fostering emergent behaviors. Additionally, it engages the community by summarizing Twitch chat to set NPC goals."
   },
   {
-    "objectID": "decisions/20240502-gltf-fbx-tscn-vrm.html#the-downsides",
-    "href": "decisions/20240502-gltf-fbx-tscn-vrm.html#the-downsides",
-    "title": "Proposed: Workflows for 3D Model Conversion",
+    "objectID": "decisions/20240705-rpg_town.html#the-downsides",
+    "href": "decisions/20240705-rpg_town.html#the-downsides",
+    "title": "Proposal: RPG Town in V-Sekai",
     "section": "",
-    "text": "There may be some loss of data or quality during the conversion process, depending on the complexity of the model and the capabilities of the target format."
+    "text": "Implementing and maintaining such a system can be challenging due to its complexity. It also requires significant computational resources for real-time processing and streaming."
   },
   {
-    "objectID": "decisions/20240502-gltf-fbx-tscn-vrm.html#the-road-not-taken",
-    "href": "decisions/20240502-gltf-fbx-tscn-vrm.html#the-road-not-taken",
-    "title": "Proposed: Workflows for 3D Model Conversion",
+    "objectID": "decisions/20240705-rpg_town.html#the-road-not-taken",
+    "href": "decisions/20240705-rpg_town.html#the-road-not-taken",
+    "title": "Proposal: RPG Town in V-Sekai",
     "section": "",
-    "text": "Alternative solutions could involve using existing conversion tools or plugins, but these may not offer the same level of control or flexibility as a custom-built tool."
+    "text": "Manually setting NPC goals and actions would be less dynamic and engaging. Using simpler AI models may not exhibit complex behaviors."
   },
   {
-    "objectID": "decisions/20240502-gltf-fbx-tscn-vrm.html#the-infrequent-use-case",
-    "href": "decisions/20240502-gltf-fbx-tscn-vrm.html#the-infrequent-use-case",
-    "title": "Proposed: Workflows for 3D Model Conversion",
+    "objectID": "decisions/20240705-rpg_town.html#the-infrequent-use-case",
+    "href": "decisions/20240705-rpg_town.html#the-infrequent-use-case",
+    "title": "Proposal: RPG Town in V-Sekai",
     "section": "",
-    "text": "While the primary use case is for converting glTF to FBX, the tool could also be used for other less common conversions."
+    "text": "Running the game without Twitch integration, focusing solely on NPC interactions, represents an infrequent use case."
   },
   {
-    "objectID": "decisions/20240502-gltf-fbx-tscn-vrm.html#in-core-and-done-by-us",
-    "href": "decisions/20240502-gltf-fbx-tscn-vrm.html#in-core-and-done-by-us",
-    "title": "Proposed: Workflows for 3D Model Conversion",
+    "objectID": "decisions/20240705-rpg_town.html#in-core-and-done-by-us",
+    "href": "decisions/20240705-rpg_town.html#in-core-and-done-by-us",
+    "title": "Proposal: RPG Town in V-Sekai",
     "section": "",
-    "text": "This tool would be developed in-house by the V-Sekai development team."
+    "text": "We will implement the GOAP framework within the V-Sekai game and integrate LLMs for goal setting based on community input."
   },
   {
-    "objectID": "decisions/20240502-gltf-fbx-tscn-vrm.html#status",
-    "href": "decisions/20240502-gltf-fbx-tscn-vrm.html#status",
-    "title": "Proposed: Workflows for 3D Model Conversion",
+    "objectID": "decisions/20240705-rpg_town.html#status",
+    "href": "decisions/20240705-rpg_town.html#status",
+    "title": "Proposal: RPG Town in V-Sekai",
     "section": "",
     "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20240502-gltf-fbx-tscn-vrm.html#decision-makers",
-    "href": "decisions/20240502-gltf-fbx-tscn-vrm.html#decision-makers",
-    "title": "Proposed: Workflows for 3D Model Conversion",
+    "objectID": "decisions/20240705-rpg_town.html#decision-makers",
+    "href": "decisions/20240705-rpg_town.html#decision-makers",
+    "title": "Proposal: RPG Town in V-Sekai",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "The decision makers for this proposal are the V-Sekai development team."
   },
   {
-    "objectID": "decisions/20240502-gltf-fbx-tscn-vrm.html#tags",
-    "href": "decisions/20240502-gltf-fbx-tscn-vrm.html#tags",
-    "title": "Proposed: Workflows for 3D Model Conversion",
+    "objectID": "decisions/20240705-rpg_town.html#tags",
+    "href": "decisions/20240705-rpg_town.html#tags",
+    "title": "Proposal: RPG Town in V-Sekai",
     "section": "",
     "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20240502-gltf-fbx-tscn-vrm.html#further-reading",
-    "href": "decisions/20240502-gltf-fbx-tscn-vrm.html#further-reading",
-    "title": "Proposed: Workflows for 3D Model Conversion",
-    "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
-  },
-  {
-    "objectID": "decisions/20211031-have-wires-in-3d.html",
-    "href": "decisions/20211031-have-wires-in-3d.html",
-    "title": "Proposed: Have wires in 3d",
-    "section": "",
-    "text": "Proposed: Have wires in 3d\n\nContext and Problem Statement\nHave wires in 3d to simulate connections\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nVertlet Rope wires\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nVertlet Rope wires project\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nIs a few hundred lines of gdscript\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nporting is easy by me\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
-  },
-  {
-    "objectID": "decisions/20230429-improve-collab.html",
-    "href": "decisions/20230429-improve-collab.html",
-    "title": "Proposed: Improve the collaboration process and attract more contributors to work on the project",
+    "objectID": "decisions/20240705-rpg_town.html#further-reading",
+    "href": "decisions/20240705-rpg_town.html#further-reading",
+    "title": "Proposal: RPG Town in V-Sekai",
     "section": "",
-    "text": "Proposed: Improve the collaboration process and attract more contributors to work on the project\n\nMetadata\n\nStatus: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,Roadmap,Collaboration,chatgpt4 summary,\n\n\n\nContext and Problem Statement\nThe V-Sekai project has an extensive roadmap with short-term, mid-term, and long-term goals, but it lacks a project manager and struggles to find collaborators who share the vision and can dedicate enough time to contribute. How can we improve the collaboration process and attract more contributors to work on the project more effectively?\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nThe proposed option to overcome the limitation of attracting more contributors and improving collaboration is to develop clear and concise project documentation, including a visual roadmap using mermaid.js, and establish a transparent contribution process. This will provide a structured environment for new and existing contributors to collaborate and understand the project’s goals and priorities.\n\nHow it helps to overcome the problem or limitation\n\nA well-organized project documentation and visual roadmap will help potential contributors understand the project’s scope and vision, allowing them to make informed decisions about contributing.\nA transparent contribution process will facilitate collaboration by providing guidelines, resources, and communication channels for contributors.\nOnboarding new contributors with tutorials and mentorship will help them quickly become productive and dedicated team members.\nRegular meetings and progress updates will keep the team motivated and focused on achieving milestones.\nRecognizing and rewarding contributors will foster a sense of community and commitment, making it more likely that they continue contributing to the project.\n\nWith these measures in place, the V-Sekai project will overcome its current limitations, making it easier for the team to work together and attract new contributors.\n\n\n\nDescribe how your proposal will work with code, pseudo-code, mock-ups, or diagrams\nDevelop a clear and concise project documentation that outlines the project’s goals, requirements, and milestones. Establish a transparent and structured contribution process, including:\n\nCreate a centralized repository for documentation, code, and assets, with clear guidelines for contributing.\nDevelop a project roadmap with prioritized tasks, deadlines, and assigned responsibilities.\nImplement an onboarding process for new contributors, including tutorials, resources, and mentorship.\nOrganize regular meetings and communication channels for updates, progress reports, and collaboration.\nRecognize and reward contributors for their work, fostering a sense of community and commitment.\n\n\n\nPositive Consequences\n\nImproved collaboration and communication among the team\nAttracting more contributors with diverse skill sets\nFaster progress towards project milestones\nClear understanding of project goals and priorities\n\n\n\nNegative Consequences\n\nIncreased management and coordination overhead\nPotential for disagreements on priorities and approaches\n\n\n\nOption graveyard\n\nRelying on informal communication and ad-hoc collaboration\nContinuing with the current approach without a structured process\n\n\n\nIf this enhancement will be used infrequently, can it be worked around with a few lines of script?\nWhile it may be possible to work around some aspects of the problem with a few lines of script, it would not address the underlying issues of attracting and retaining contributors or improving collaboration. The proposed solution aims to create a more sustainable and efficient environment for the V-Sekai project, which cannot be achieved with a temporary workaround or a simple script.\n\n\nIs there a reason why this should be core and done by us?\nAs the primary developers of the project, the V-Sekai team has the best understanding of the project’s goals, objectives, and priorities. Implementing this feature in-house will ensure that the solution aligns well with the project’s vision and addresses the specific needs of the project.\n\n\nReferences\n\nV-Sekai\nV-Sekai Roadmap and Goals\nV-Sekai Team Discussions and Updates\nMermaid.js"
+    "text": "For more information, you can visit the V-Sekai GitHub account, which focuses on social VR functionality for the Godot Engine. You can also check out the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240127-urban-explorer-gdc-2024-sample.html",
-    "href": "decisions/20240127-urban-explorer-gdc-2024-sample.html",
-    "title": "Proposed: Urban Navigator: The City Unveiled",
+    "objectID": "decisions/20240409-crud-godot-tiles.html",
+    "href": "decisions/20240409-crud-godot-tiles.html",
+    "title": "Accepted: “Sunny Park” Test Case for 3D Tile Sync",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nThe aim is to present a demo at the Game Developer Conference 2024 that will showcase the capabilities of the Godot Engine animation and Godot Engine 3D pipelines.\n\n\n\nThe task at hand is to create a Godot Engine demo within a span of one week.\n\n\n\nThe proposed idea is “Urban Navigator: The City Unveiled”. Embark on an exploratory journey through the heart of a city. Unravel the secrets of a sprawling metropolis where every street corner has a story to tell. With the help of advanced motion matching technology, your gamepad inputs are transformed into lifelike movements, enabling seamless interaction with the city.\n\n\n\nThe project will demonstrate the power and flexibility of the Godot Engine, potentially attracting more developers to use it. It also provides an opportunity to innovate in the field of urban exploration games.\n\n\n\nThe tight timeline could lead to compromises in quality or scope. There’s also a risk that the final product may not fully meet the expectations set by the proposal.\n\n\n\nAn alternative approach could have been to focus on a different genre or type of game that might be less complex but still showcases the capabilities of the Godot Engine.\n\n\n\nWhile the primary use case is for the Game Developer Conference demo, the developed game could also be used as a benchmarking tool for testing hardware performance with the Godot Engine.\n\n\n\nYes, this project is core to our mission of showcasing the capabilities of the Godot Engine and can be done by our team.\n\n\n\n\nV-Sekai · GitHub - This is the official GitHub account for the V-Sekai development community which focuses on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - This is the GitHub page for the V-Sekai open-source project that brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis article was assisted by AI assistant Aria."
+    "text": "This test case aims to utilize a specific database technology, sqlite-fdb, to assess the efficiency and accuracy of syncing 3D tiles between Blender and Godot. The test will involve basic CRUD operations on a set of 3D tiles representing a park.\n\n\n\n\n3D Tiles: These include Grass, Pathway, Bench, Tree, Pond.\nTools: The tools used in this process are Blender (for creation/editing), Godot Engine (for scene assembly), and Database (for syncing).\n\n\n\n\n\nCreate (Blender): Design 5 different 3D park tiles and store their data in the database.\nRead (Godot): Import the tiles from the database into Godot and assemble the “Sunny Park.”\nUpdate (Blender): Modify a tile (e.g., change the color of the bench), update the database, and verify the update in Godot.\nDelete (Blender): Remove a tile (e.g., pond), delete it from the database, and confirm its removal in Godot.\n\n\n\n\n\nSynchronization Accuracy: Ensure that changes made in Blender are accurately reflected in Godot.\nPerformance: Measure the time taken for sync operations.\nEase of Use: Evaluate the complexity of the sync steps.\nError Handling: Check how the system responds to errors such as missing data."
   },
   {
-    "objectID": "decisions/20240127-urban-explorer-gdc-2024-sample.html#metadata",
-    "href": "decisions/20240127-urban-explorer-gdc-2024-sample.html#metadata",
-    "title": "Proposed: Urban Navigator: The City Unveiled",
+    "objectID": "decisions/20240409-crud-godot-tiles.html#objective",
+    "href": "decisions/20240409-crud-godot-tiles.html#objective",
+    "title": "Accepted: “Sunny Park” Test Case for 3D Tile Sync",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai"
+    "text": "This test case aims to utilize a specific database technology, sqlite-fdb, to assess the efficiency and accuracy of syncing 3D tiles between Blender and Godot. The test will involve basic CRUD operations on a set of 3D tiles representing a park."
   },
   {
-    "objectID": "decisions/20240127-urban-explorer-gdc-2024-sample.html#the-backdrop",
-    "href": "decisions/20240127-urban-explorer-gdc-2024-sample.html#the-backdrop",
-    "title": "Proposed: Urban Navigator: The City Unveiled",
+    "objectID": "decisions/20240409-crud-godot-tiles.html#components",
+    "href": "decisions/20240409-crud-godot-tiles.html#components",
+    "title": "Accepted: “Sunny Park” Test Case for 3D Tile Sync",
     "section": "",
-    "text": "The aim is to present a demo at the Game Developer Conference 2024 that will showcase the capabilities of the Godot Engine animation and Godot Engine 3D pipelines."
+    "text": "3D Tiles: These include Grass, Pathway, Bench, Tree, Pond.\nTools: The tools used in this process are Blender (for creation/editing), Godot Engine (for scene assembly), and Database (for syncing)."
   },
   {
-    "objectID": "decisions/20240127-urban-explorer-gdc-2024-sample.html#the-challenge",
-    "href": "decisions/20240127-urban-explorer-gdc-2024-sample.html#the-challenge",
-    "title": "Proposed: Urban Navigator: The City Unveiled",
+    "objectID": "decisions/20240409-crud-godot-tiles.html#steps",
+    "href": "decisions/20240409-crud-godot-tiles.html#steps",
+    "title": "Accepted: “Sunny Park” Test Case for 3D Tile Sync",
     "section": "",
-    "text": "The task at hand is to create a Godot Engine demo within a span of one week."
+    "text": "Create (Blender): Design 5 different 3D park tiles and store their data in the database.\nRead (Godot): Import the tiles from the database into Godot and assemble the “Sunny Park.”\nUpdate (Blender): Modify a tile (e.g., change the color of the bench), update the database, and verify the update in Godot.\nDelete (Blender): Remove a tile (e.g., pond), delete it from the database, and confirm its removal in Godot."
   },
   {
-    "objectID": "decisions/20240127-urban-explorer-gdc-2024-sample.html#the-strategy",
-    "href": "decisions/20240127-urban-explorer-gdc-2024-sample.html#the-strategy",
-    "title": "Proposed: Urban Navigator: The City Unveiled",
+    "objectID": "decisions/20240409-crud-godot-tiles.html#evaluation-criteria",
+    "href": "decisions/20240409-crud-godot-tiles.html#evaluation-criteria",
+    "title": "Accepted: “Sunny Park” Test Case for 3D Tile Sync",
     "section": "",
-    "text": "The proposed idea is “Urban Navigator: The City Unveiled”. Embark on an exploratory journey through the heart of a city. Unravel the secrets of a sprawling metropolis where every street corner has a story to tell. With the help of advanced motion matching technology, your gamepad inputs are transformed into lifelike movements, enabling seamless interaction with the city."
+    "text": "Synchronization Accuracy: Ensure that changes made in Blender are accurately reflected in Godot.\nPerformance: Measure the time taken for sync operations.\nEase of Use: Evaluate the complexity of the sync steps.\nError Handling: Check how the system responds to errors such as missing data."
   },
   {
-    "objectID": "decisions/20240127-urban-explorer-gdc-2024-sample.html#the-upside",
-    "href": "decisions/20240127-urban-explorer-gdc-2024-sample.html#the-upside",
-    "title": "Proposed: Urban Navigator: The City Unveiled",
-    "section": "",
-    "text": "The project will demonstrate the power and flexibility of the Godot Engine, potentially attracting more developers to use it. It also provides an opportunity to innovate in the field of urban exploration games."
+    "objectID": "decisions/20240409-crud-godot-tiles.html#context",
+    "href": "decisions/20240409-crud-godot-tiles.html#context",
+    "title": "Accepted: “Sunny Park” Test Case for 3D Tile Sync",
+    "section": "Context",
+    "text": "Context\nThis proposal arises from the need for an efficient and accurate synchronization of 3D tiles between Blender and Godot Engine."
   },
   {
-    "objectID": "decisions/20240127-urban-explorer-gdc-2024-sample.html#the-downside",
-    "href": "decisions/20240127-urban-explorer-gdc-2024-sample.html#the-downside",
-    "title": "Proposed: Urban Navigator: The City Unveiled",
-    "section": "",
-    "text": "The tight timeline could lead to compromises in quality or scope. There’s also a risk that the final product may not fully meet the expectations set by the proposal."
+    "objectID": "decisions/20240409-crud-godot-tiles.html#problem-statement",
+    "href": "decisions/20240409-crud-godot-tiles.html#problem-statement",
+    "title": "Accepted: “Sunny Park” Test Case for 3D Tile Sync",
+    "section": "Problem Statement",
+    "text": "Problem Statement\nThe problem is determining whether SQLite-fdb would be faster for syncing 3D tiles from Blender to Godot engine compared to multi raft or cockroachdb."
   },
   {
-    "objectID": "decisions/20240127-urban-explorer-gdc-2024-sample.html#the-road-not-taken",
-    "href": "decisions/20240127-urban-explorer-gdc-2024-sample.html#the-road-not-taken",
-    "title": "Proposed: Urban Navigator: The City Unveiled",
-    "section": "",
-    "text": "An alternative approach could have been to focus on a different genre or type of game that might be less complex but still showcases the capabilities of the Godot Engine."
+    "objectID": "decisions/20240409-crud-godot-tiles.html#benefits",
+    "href": "decisions/20240409-crud-godot-tiles.html#benefits",
+    "title": "Accepted: “Sunny Park” Test Case for 3D Tile Sync",
+    "section": "Benefits",
+    "text": "Benefits\nThe benefits of this proposal include improved performance, ease of use, and error handling in the synchronization process."
   },
   {
-    "objectID": "decisions/20240127-urban-explorer-gdc-2024-sample.html#the-infrequent-use-case",
-    "href": "decisions/20240127-urban-explorer-gdc-2024-sample.html#the-infrequent-use-case",
-    "title": "Proposed: Urban Navigator: The City Unveiled",
-    "section": "",
-    "text": "While the primary use case is for the Game Developer Conference demo, the developed game could also be used as a benchmarking tool for testing hardware performance with the Godot Engine."
+    "objectID": "decisions/20240409-crud-godot-tiles.html#downsides",
+    "href": "decisions/20240409-crud-godot-tiles.html#downsides",
+    "title": "Accepted: “Sunny Park” Test Case for 3D Tile Sync",
+    "section": "Downsides",
+    "text": "Downsides\nPotential downsides may include increased complexity and potential for errors during synchronization."
   },
   {
-    "objectID": "decisions/20240127-urban-explorer-gdc-2024-sample.html#in-core-and-done-by-us",
-    "href": "decisions/20240127-urban-explorer-gdc-2024-sample.html#in-core-and-done-by-us",
-    "title": "Proposed: Urban Navigator: The City Unveiled",
-    "section": "",
-    "text": "Yes, this project is core to our mission of showcasing the capabilities of the Godot Engine and can be done by our team."
+    "objectID": "decisions/20240409-crud-godot-tiles.html#road-not-taken",
+    "href": "decisions/20240409-crud-godot-tiles.html#road-not-taken",
+    "title": "Accepted: “Sunny Park” Test Case for 3D Tile Sync",
+    "section": "Road Not Taken",
+    "text": "Road Not Taken\nThis proposal did not consider other database technologies that could be used for synchronization."
   },
   {
-    "objectID": "decisions/20240127-urban-explorer-gdc-2024-sample.html#further-reading",
-    "href": "decisions/20240127-urban-explorer-gdc-2024-sample.html#further-reading",
-    "title": "Proposed: Urban Navigator: The City Unveiled",
-    "section": "",
-    "text": "V-Sekai · GitHub - This is the official GitHub account for the V-Sekai development community which focuses on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - This is the GitHub page for the V-Sekai open-source project that brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis article was assisted by AI assistant Aria."
+    "objectID": "decisions/20240409-crud-godot-tiles.html#infrequent-use-case",
+    "href": "decisions/20240409-crud-godot-tiles.html#infrequent-use-case",
+    "title": "Accepted: “Sunny Park” Test Case for 3D Tile Sync",
+    "section": "Infrequent Use Case",
+    "text": "Infrequent Use Case\nThis proposal may not apply to projects that do not require frequent synchronization of 3D tiles between Blender and Godot Engine."
   },
   {
-    "objectID": "decisions/20211031-arc-radial-menu.html",
-    "href": "decisions/20211031-arc-radial-menu.html",
-    "title": "Proposed: ARC radial menu",
-    "section": "",
-    "text": "Proposed: ARC radial menu\n\nContext and Problem Statement\nNeed to make user experience easy to use\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nMake an arc menu.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nTo be mocked up.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nSure. can be script.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nUIUX is our business.\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "objectID": "decisions/20240409-crud-godot-tiles.html#in-core-and-done-by-us",
+    "href": "decisions/20240409-crud-godot-tiles.html#in-core-and-done-by-us",
+    "title": "Accepted: “Sunny Park” Test Case for 3D Tile Sync",
+    "section": "In Core and Done by Us",
+    "text": "In Core and Done by Us\nThe V-Sekai development team will be responsible for implementing this proposal."
   },
   {
-    "objectID": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html",
-    "href": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html",
-    "title": "Rejected: Rewriting Mixer Broadcaster Into Membrane Framework Pipelines",
-    "section": "",
-    "text": "Status: Rejected\nDeciders: V-Sekai\nTags: V-Sekai, Elixir, Membrane Framework, Multiplayer Blender\n\n\n\n\nUbisoft’s mixer broadcaster code has been the only available solution for handling multiplayer Blender. However, it has its limitations when it comes to scalability and real-time performance. This proposal aims to rewrite the code using Elixir and the Membrane Framework.\n\n\n\nThe main challenge is to translate the existing code into Elixir while maintaining the functionality and improving upon the limitations of the current system. This includes ensuring that the new code can handle larger volumes of users and provide real-time updates without lag or delay.\n\n\n\ngraph LR\n  A[Ubisoft's Mixer Broadcaster Code] --&gt; B[Elixir & Membrane Framework Code]\n  C[No Authentication] --&gt; D[GitHub OAuth 2.0 Login]\n  E[No Database] --&gt; F[Khepri Database Library]\nThis strategy leverages Elixir and the Membrane Framework’s unique features, uses the Khepri database library for data management, and implements GitHub login using OAuth 2.0 protocol for single sign-on.\nHere are the key steps:\n\nCodebase: Transition from Ubisoft’s Mixer Broadcaster Code to Elixir & Membrane Framework Code, tracked in a version control system.\nDependencies: Declare and isolate dependencies explicitly, avoiding reliance on system-wide packages.\nConfig: Store configuration (including GitHub OAuth 2.0 Login credentials) in the environment, not in the code.\nBacking Services: Replace in-memory data persistence with Khepri Database Library, attached as a backing service.\nBuild, Release, Run: Strictly separate these stages, facilitated by the Elixir & Membrane Framework Code.\nProcesses: Execute application as one or more stateless processes, storing needed state in the Khepri database.\nPort Binding: Export services via port binding, making the application self-contained.\nConcurrency: Scale out the application via the process model, allowing for handling increased load.\nDisposability: Aim for fast startup and graceful shutdown to maximize robustness.\nDev/Prod Parity: Keep development, staging, and production environments as similar as possible.\nLogs: Treat logs as event streams, handled by the executing environment.\nAdmin Processes: Run any needed one-off administrative tasks in an identical environment as the regular long-running processes of the app.\n\n\n\n\nBy rewriting the code in Elixir, using the Membrane Framework, and implementing the Khepri database library, we can expect improved scalability and real-time performance. This will allow for more users to use the system simultaneously without experiencing delays or lags. Additionally, the fault-tolerance feature of Elixir will ensure that the system remains operational even when errors occur.\n\n\n\nRewriting the code will require time and resources. There may also be a learning curve for developers who are not familiar with Elixir, the Membrane Framework, and the Khepri database library.\n\n\n\nAn alternative approach would have been to optimize the existing code instead of rewriting it. However, this would not have addressed the inherent limitations of the current system.\n\n\n\nIn cases where the number of users is low and real-time updates are not critical, the current system may still be sufficient. However, as the user base grows and the demand for real-time updates increases, the need for a more scalable and efficient system becomes apparent.\n\n\n\nYes, the rewriting of the code will indeed be done by us as we also maintain the uro backend services.\n\n\n\n\nV-Sekai\nElixir\nMembrane Framework\nKhepri Database Library\n\nThis article is assisted by AI."
+    "objectID": "decisions/20240409-crud-godot-tiles.html#status",
+    "href": "decisions/20240409-crud-godot-tiles.html#status",
+    "title": "Accepted: “Sunny Park” Test Case for 3D Tile Sync",
+    "section": "Status",
+    "text": "Status\nStatus: Accepted"
   },
   {
-    "objectID": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html#metadata",
-    "href": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html#metadata",
-    "title": "Rejected: Rewriting Mixer Broadcaster Into Membrane Framework Pipelines",
-    "section": "",
-    "text": "Status: Rejected\nDeciders: V-Sekai\nTags: V-Sekai, Elixir, Membrane Framework, Multiplayer Blender"
+    "objectID": "decisions/20240409-crud-godot-tiles.html#decision-makers",
+    "href": "decisions/20240409-crud-godot-tiles.html#decision-makers",
+    "title": "Accepted: “Sunny Park” Test Case for 3D Tile Sync",
+    "section": "Decision Makers",
+    "text": "Decision Makers\n\nV-Sekai development team"
   },
   {
-    "objectID": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html#the-backdrop",
-    "href": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html#the-backdrop",
-    "title": "Rejected: Rewriting Mixer Broadcaster Into Membrane Framework Pipelines",
-    "section": "",
-    "text": "Ubisoft’s mixer broadcaster code has been the only available solution for handling multiplayer Blender. However, it has its limitations when it comes to scalability and real-time performance. This proposal aims to rewrite the code using Elixir and the Membrane Framework."
+    "objectID": "decisions/20240409-crud-godot-tiles.html#tags",
+    "href": "decisions/20240409-crud-godot-tiles.html#tags",
+    "title": "Accepted: “Sunny Park” Test Case for 3D Tile Sync",
+    "section": "Tags",
+    "text": "Tags\n\nV-Sekai"
   },
   {
-    "objectID": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html#the-challenge",
-    "href": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html#the-challenge",
-    "title": "Rejected: Rewriting Mixer Broadcaster Into Membrane Framework Pipelines",
-    "section": "",
-    "text": "The main challenge is to translate the existing code into Elixir while maintaining the functionality and improving upon the limitations of the current system. This includes ensuring that the new code can handle larger volumes of users and provide real-time updates without lag or delay."
+    "objectID": "decisions/20240409-crud-godot-tiles.html#further-reading",
+    "href": "decisions/20240409-crud-godot-tiles.html#further-reading",
+    "title": "Accepted: “Sunny Park” Test Case for 3D Tile Sync",
+    "section": "Further Reading",
+    "text": "Further Reading\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nEfficient_Methods_for_Improving_Scalability_and_Playability_of_Massively_Multiplayer_Online_Game_MMOG by Prasetya, Kusno\nlawnjelly’s spergler algorithm for splitting meshes\nlibgodot.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html#strategy",
-    "href": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html#strategy",
-    "title": "Rejected: Rewriting Mixer Broadcaster Into Membrane Framework Pipelines",
+    "objectID": "decisions/20230310-xml-based-tests.html",
+    "href": "decisions/20230310-xml-based-tests.html",
+    "title": "Proposed: Use junit xml based tests in github",
     "section": "",
-    "text": "graph LR\n  A[Ubisoft's Mixer Broadcaster Code] --&gt; B[Elixir & Membrane Framework Code]\n  C[No Authentication] --&gt; D[GitHub OAuth 2.0 Login]\n  E[No Database] --&gt; F[Khepri Database Library]\nThis strategy leverages Elixir and the Membrane Framework’s unique features, uses the Khepri database library for data management, and implements GitHub login using OAuth 2.0 protocol for single sign-on.\nHere are the key steps:\n\nCodebase: Transition from Ubisoft’s Mixer Broadcaster Code to Elixir & Membrane Framework Code, tracked in a version control system.\nDependencies: Declare and isolate dependencies explicitly, avoiding reliance on system-wide packages.\nConfig: Store configuration (including GitHub OAuth 2.0 Login credentials) in the environment, not in the code.\nBacking Services: Replace in-memory data persistence with Khepri Database Library, attached as a backing service.\nBuild, Release, Run: Strictly separate these stages, facilitated by the Elixir & Membrane Framework Code.\nProcesses: Execute application as one or more stateless processes, storing needed state in the Khepri database.\nPort Binding: Export services via port binding, making the application self-contained.\nConcurrency: Scale out the application via the process model, allowing for handling increased load.\nDisposability: Aim for fast startup and graceful shutdown to maximize robustness.\nDev/Prod Parity: Keep development, staging, and production environments as similar as possible.\nLogs: Treat logs as event streams, handled by the executing environment.\nAdmin Processes: Run any needed one-off administrative tasks in an identical environment as the regular long-running processes of the app."
+    "text": "Proposed: Use junit xml based tests in github\n\nMetadata\n\nStatus: proposed \nDeciders: V-Sekai,fire,\nTags: V-Sekai,\n\n\n\nContext and Problem Statement\nV-Sekai is not robust.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nI want to make V-Sekai more robust using best practices like unit tests.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nWhen CICD runs it will run gut and parse the junit xml that is outputted.\nWe will also need to use pending head git workflow techniques.\n\n\nPositive Consequences\nWe will be able to use unit tests for gdscript, not just for C++ to make v-sekai more robust.\n\n\nNegative Consequences\nWe cannot get other features in.\n\n\nOption graveyard\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nThis is a cicd change and is able scripting the github actions.\n\n\nIs there a reason why this should be core and done by us?\nWe manage cicd.\n\n\nReferences\n\nV-Sekai\nhttps://martinfowler.com/bliki/PendingHead.html"
   },
   {
-    "objectID": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html#the-upside",
-    "href": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html#the-upside",
-    "title": "Rejected: Rewriting Mixer Broadcaster Into Membrane Framework Pipelines",
+    "objectID": "decisions/20220207-virtual-pets.html",
+    "href": "decisions/20220207-virtual-pets.html",
+    "title": "Accepted: To make a virtual pet game given Jeana’s designs",
     "section": "",
-    "text": "By rewriting the code in Elixir, using the Membrane Framework, and implementing the Khepri database library, we can expect improved scalability and real-time performance. This will allow for more users to use the system simultaneously without experiencing delays or lags. Additionally, the fault-tolerance feature of Elixir will ensure that the system remains operational even when errors occur."
+    "text": "Status: accepted\nDeciders: V-Sekai,ifire,Jeana,lyuma,\nTags: V-Sekai,\n\n\n\nWe were chatting late night and the idea of a virtual pet game was challenged.\n\n\n\n\n\n\nVRM with spring bones\nreverse bone direction\nSimulate virtual pet behaviors\n\n\n\n\n\nspringbone/constraint/follower (will clip through geom)\nphysics\nnavmesh (bake at runtime?)\nraycast\n\n\n\n\n\nWanted to create a virtual reality pet game where the pet was a character that was beside you in game and networked. The virtual pet would be with you in the game.\n\n\n\n\nAble to backtrack ideas.\n\n\n\n\n\nWork\n\n\n\n\n\nOption: Forgetting decisions.\nRejection Reason: We won’t remember the original reasons why we did things.\n\n\n\n\nNot a small amount of scripting.\n\n\n\nWe are running the project.\n\n\n\n\nhttps://twitter.com/jordy_j_s/status/1489644934743396356?s=20&t=WWesEW8ksELrkJa__3mUIg\nhttps://github.com/V-Sekai/godot-tfd\nhttps://twitter.com/VSekaiOfficial\nhttps://itch.io/jam/virtual-pet-jam\n\n\n\n\n\n\nJeana virtual pet concept\n\n\n\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html#the-downside",
-    "href": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html#the-downside",
-    "title": "Rejected: Rewriting Mixer Broadcaster Into Membrane Framework Pipelines",
+    "objectID": "decisions/20220207-virtual-pets.html#context-and-problem-statement",
+    "href": "decisions/20220207-virtual-pets.html#context-and-problem-statement",
+    "title": "Accepted: To make a virtual pet game given Jeana’s designs",
     "section": "",
-    "text": "Rewriting the code will require time and resources. There may also be a learning curve for developers who are not familiar with Elixir, the Membrane Framework, and the Khepri database library."
+    "text": "We were chatting late night and the idea of a virtual pet game was challenged."
   },
   {
-    "objectID": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html#the-road-not-taken",
-    "href": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html#the-road-not-taken",
-    "title": "Rejected: Rewriting Mixer Broadcaster Into Membrane Framework Pipelines",
+    "objectID": "decisions/20220207-virtual-pets.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20220207-virtual-pets.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Accepted: To make a virtual pet game given Jeana’s designs",
     "section": "",
-    "text": "An alternative approach would have been to optimize the existing code instead of rewriting it. However, this would not have addressed the inherent limitations of the current system."
+    "text": "VRM with spring bones\nreverse bone direction\nSimulate virtual pet behaviors\n\n\n\n\n\nspringbone/constraint/follower (will clip through geom)\nphysics\nnavmesh (bake at runtime?)\nraycast"
   },
   {
-    "objectID": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html#the-infrequent-use-case",
-    "href": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html#the-infrequent-use-case",
-    "title": "Rejected: Rewriting Mixer Broadcaster Into Membrane Framework Pipelines",
+    "objectID": "decisions/20220207-virtual-pets.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20220207-virtual-pets.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Accepted: To make a virtual pet game given Jeana’s designs",
     "section": "",
-    "text": "In cases where the number of users is low and real-time updates are not critical, the current system may still be sufficient. However, as the user base grows and the demand for real-time updates increases, the need for a more scalable and efficient system becomes apparent."
+    "text": "Wanted to create a virtual reality pet game where the pet was a character that was beside you in game and networked. The virtual pet would be with you in the game."
   },
   {
-    "objectID": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html#in-core-and-done-by-us",
-    "href": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html#in-core-and-done-by-us",
-    "title": "Rejected: Rewriting Mixer Broadcaster Into Membrane Framework Pipelines",
+    "objectID": "decisions/20220207-virtual-pets.html#positive-consequences",
+    "href": "decisions/20220207-virtual-pets.html#positive-consequences",
+    "title": "Accepted: To make a virtual pet game given Jeana’s designs",
     "section": "",
-    "text": "Yes, the rewriting of the code will indeed be done by us as we also maintain the uro backend services."
+    "text": "Able to backtrack ideas."
   },
   {
-    "objectID": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html#further-reading",
-    "href": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html#further-reading",
-    "title": "Rejected: Rewriting Mixer Broadcaster Into Membrane Framework Pipelines",
+    "objectID": "decisions/20220207-virtual-pets.html#negative-consequences",
+    "href": "decisions/20220207-virtual-pets.html#negative-consequences",
+    "title": "Accepted: To make a virtual pet game given Jeana’s designs",
     "section": "",
-    "text": "V-Sekai\nElixir\nMembrane Framework\nKhepri Database Library\n\nThis article is assisted by AI."
+    "text": "Work"
   },
   {
-    "objectID": "decisions/20230525-animation-ik-node.html",
-    "href": "decisions/20230525-animation-ik-node.html",
-    "title": "Proposed: Convert IK solvers to be using the AnimationTree",
+    "objectID": "decisions/20220207-virtual-pets.html#option-graveyard",
+    "href": "decisions/20220207-virtual-pets.html#option-graveyard",
+    "title": "Accepted: To make a virtual pet game given Jeana’s designs",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai, fire,\nTags: V-Sekai, GPT-4\n\n\n\n\nAs part of the V-Sekai project we’re working on virtual worlds and avatars usable for all.\n\n\n\nThere is no robust, and production quality inverse kinematic solver for full body tracking virtual reality tracking and other inverse kinematic uses like foot planting and hand grabbing.\nIn addition to the limitations of the current IK system due to its implementation as a SkeletonIK3D node, the IK system can be improved by reimplementing it as an animation node. This can address these limitations and improve the overall functionality.\n\n\n\n\nReimplement the IK system as an animation node to gain better control over the processing order, ensure accurate pose states.\nReuse the track filtering code that exists in the AnimationTree system to enhance the new IK system’s capabilities.\n\n\n\n\nIn order to improve the Inverse Kinematics (IK) system, we will replace SkeletonIK3D with a new custom AnimationNode called IKAnimationNode. This new node will ensure accurate pose states and provide precise control over the IK system.\nTo enhance the blending between animations and handle IK more efficiently, we will reuse track filtering code from the existing AnimationTree. This will allow for smoother transitions and better performance.\nNext, we will implement the IK solver within the new IKAnimationNode. This solver will be responsible for calculating target positions and rotations for each bone in the skeleton.\nAfter implementing the IK solver, we will update the AnimationTree to use the new IKAnimationNode. This will involve adding an empty track, reading from the transform’s position, and blending between different animations to create seamless motion.\nAs we develop this new IK system, it is crucial to address potential issues such as filter usability, duplicate subtrees versus multiple outputs, and designing a reasonable full body setup. This includes handling jumping and foot IK interactions with the ground.\nFinally, we will test and optimize the new IK system to ensure correct functionality and optimal performance. This will result in a more robust and efficient IK solution for our animation needs.\n\n\n\n\nImproved control over the processing order of the IK system.\nAccurate pose states for better animation quality.\nPotential performance improvements by executing the animation tree outside of the main thread.\nEnhanced capabilities of the new IK system by reusing the track filtering code.\n\n\n\n\n\nIncreased complexity in the animation system.\nPossible compatibility issues with existing projects.\n\n\n\n\n\nKeeping the current SkeletonIK3D node and trying to improve its functionality.\nImplementing a custom IK solver without reusing the track filtering code from the AnimationTree system.\nUsing third-party IK solvers instead of developing an in-house solution.\n\n\n\n\nNo, the enhancement involves a significant change in the IK system’s implementation and cannot be easily worked around with a script.\n\n\n\nYes, addressing the limitations of the current IK system is crucial for improving V-Sekai’s functionality and providing a better experience for users.\n\n\n\n\nV-Sekai\nManyBoneIK3D (mentioned for reference purposes only)"
+    "text": "Option: Forgetting decisions.\nRejection Reason: We won’t remember the original reasons why we did things."
   },
   {
-    "objectID": "decisions/20230525-animation-ik-node.html#metadata",
-    "href": "decisions/20230525-animation-ik-node.html#metadata",
-    "title": "Proposed: Convert IK solvers to be using the AnimationTree",
+    "objectID": "decisions/20220207-virtual-pets.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20220207-virtual-pets.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Accepted: To make a virtual pet game given Jeana’s designs",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai, fire,\nTags: V-Sekai, GPT-4"
+    "text": "Not a small amount of scripting."
   },
   {
-    "objectID": "decisions/20230525-animation-ik-node.html#project",
-    "href": "decisions/20230525-animation-ik-node.html#project",
-    "title": "Proposed: Convert IK solvers to be using the AnimationTree",
+    "objectID": "decisions/20220207-virtual-pets.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20220207-virtual-pets.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Accepted: To make a virtual pet game given Jeana’s designs",
     "section": "",
-    "text": "As part of the V-Sekai project we’re working on virtual worlds and avatars usable for all."
+    "text": "We are running the project."
   },
   {
-    "objectID": "decisions/20230525-animation-ik-node.html#context-and-problem-statement",
-    "href": "decisions/20230525-animation-ik-node.html#context-and-problem-statement",
-    "title": "Proposed: Convert IK solvers to be using the AnimationTree",
+    "objectID": "decisions/20220207-virtual-pets.html#references",
+    "href": "decisions/20220207-virtual-pets.html#references",
+    "title": "Accepted: To make a virtual pet game given Jeana’s designs",
     "section": "",
-    "text": "There is no robust, and production quality inverse kinematic solver for full body tracking virtual reality tracking and other inverse kinematic uses like foot planting and hand grabbing.\nIn addition to the limitations of the current IK system due to its implementation as a SkeletonIK3D node, the IK system can be improved by reimplementing it as an animation node. This can address these limitations and improve the overall functionality."
+    "text": "https://twitter.com/jordy_j_s/status/1489644934743396356?s=20&t=WWesEW8ksELrkJa__3mUIg\nhttps://github.com/V-Sekai/godot-tfd\nhttps://twitter.com/VSekaiOfficial\nhttps://itch.io/jam/virtual-pet-jam\n\n\n\n\n\n\nJeana virtual pet concept"
   },
   {
-    "objectID": "decisions/20230525-animation-ik-node.html#proposed-solution",
-    "href": "decisions/20230525-animation-ik-node.html#proposed-solution",
-    "title": "Proposed: Convert IK solvers to be using the AnimationTree",
+    "objectID": "decisions/20220207-virtual-pets.html#derivative-license",
+    "href": "decisions/20220207-virtual-pets.html#derivative-license",
+    "title": "Accepted: To make a virtual pet game given Jeana’s designs",
     "section": "",
-    "text": "Reimplement the IK system as an animation node to gain better control over the processing order, ensure accurate pose states.\nReuse the track filtering code that exists in the AnimationTree system to enhance the new IK system’s capabilities."
+    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230525-animation-ik-node.html#implementation",
-    "href": "decisions/20230525-animation-ik-node.html#implementation",
-    "title": "Proposed: Convert IK solvers to be using the AnimationTree",
+    "objectID": "decisions/20211031-streaming-godot-to-opensoundcontrol.html",
+    "href": "decisions/20211031-streaming-godot-to-opensoundcontrol.html",
+    "title": "Proposed: Take a streaming godot game and streaming the VRM to OpenSoundControl",
     "section": "",
-    "text": "In order to improve the Inverse Kinematics (IK) system, we will replace SkeletonIK3D with a new custom AnimationNode called IKAnimationNode. This new node will ensure accurate pose states and provide precise control over the IK system.\nTo enhance the blending between animations and handle IK more efficiently, we will reuse track filtering code from the existing AnimationTree. This will allow for smoother transitions and better performance.\nNext, we will implement the IK solver within the new IKAnimationNode. This solver will be responsible for calculating target positions and rotations for each bone in the skeleton.\nAfter implementing the IK solver, we will update the AnimationTree to use the new IKAnimationNode. This will involve adding an empty track, reading from the transform’s position, and blending between different animations to create seamless motion.\nAs we develop this new IK system, it is crucial to address potential issues such as filter usability, duplicate subtrees versus multiple outputs, and designing a reasonable full body setup. This includes handling jumping and foot IK interactions with the ground.\nFinally, we will test and optimize the new IK system to ensure correct functionality and optimal performance. This will result in a more robust and efficient IK solution for our animation needs."
+    "text": "Proposed: Take a streaming godot game and streaming the VRM to OpenSoundControl\n\nContext and Problem Statement\nStreaming to Godot OSC to jsons.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nStream the animation player because we have no way to stream Godot as a autonomous program.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n\nTake animation player\nPut it in a animation tree\nAnimation node streams motions to osc\nTake osc to node.js\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot trivial\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nIt’s rare to know how to dothis.\n\n\nReferences\n\nto node js https://github.com/colinbdclark/osc.js js\nhttps://github.com/infosia/vmc2bvh\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230525-animation-ik-node.html#positive-consequences",
-    "href": "decisions/20230525-animation-ik-node.html#positive-consequences",
-    "title": "Proposed: Convert IK solvers to be using the AnimationTree",
+    "objectID": "decisions/20211031-have-better-user-developer-experience.html",
+    "href": "decisions/20211031-have-better-user-developer-experience.html",
+    "title": "Proposed: Have better user developer experience",
     "section": "",
-    "text": "Improved control over the processing order of the IK system.\nAccurate pose states for better animation quality.\nPotential performance improvements by executing the animation tree outside of the main thread.\nEnhanced capabilities of the new IK system by reusing the track filtering code."
+    "text": "Proposed: Have better user developer experience\n\nContext and Problem Statement\nV-Sekai can aim to better at user developer experience.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nWe can measure and improve our experience.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n\nMeasure\nImprove\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot a few lines of code.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nWe need to do it.\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230525-animation-ik-node.html#negative-consequences",
-    "href": "decisions/20230525-animation-ik-node.html#negative-consequences",
-    "title": "Proposed: Convert IK solvers to be using the AnimationTree",
+    "objectID": "decisions/20221203-target-10-minutes-cicd.html",
+    "href": "decisions/20221203-target-10-minutes-cicd.html",
+    "title": "Proposed: Target 10 minutes cicd builds to improve our iterations",
     "section": "",
-    "text": "Increased complexity in the animation system.\nPossible compatibility issues with existing projects."
+    "text": "Status: proposed \nDeciders: V-Sekai,fire,\nTags: V-Sekai,\n\n\n\nCICD builds take too long to do.\n\n\n\nTry to aim for 10 minute builds and reduce stress.\n\n\n\nTry to aim for the godot cicd builds to finish in 10 minute.\n\n\n\nWe can see the results of our work.\n\n\n\nMight need to do special tricks.\n\n\n\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\n\nThis is a dev ops change.\n\n\n\nWe own the github repositories.\n\n\n\n\nV-Sekai\n\n\n\n\nCopyright (c) 2022 K. S. Ernest (iFire) Lee Copyright (c) 2022 V-Sekai contributors\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230525-animation-ik-node.html#option-graveyard",
-    "href": "decisions/20230525-animation-ik-node.html#option-graveyard",
-    "title": "Proposed: Convert IK solvers to be using the AnimationTree",
+    "objectID": "decisions/20221203-target-10-minutes-cicd.html#context-and-problem-statement",
+    "href": "decisions/20221203-target-10-minutes-cicd.html#context-and-problem-statement",
+    "title": "Proposed: Target 10 minutes cicd builds to improve our iterations",
     "section": "",
-    "text": "Keeping the current SkeletonIK3D node and trying to improve its functionality.\nImplementing a custom IK solver without reusing the track filtering code from the AnimationTree system.\nUsing third-party IK solvers instead of developing an in-house solution."
+    "text": "CICD builds take too long to do."
   },
   {
-    "objectID": "decisions/20230525-animation-ik-node.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230525-animation-ik-node.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Convert IK solvers to be using the AnimationTree",
+    "objectID": "decisions/20221203-target-10-minutes-cicd.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20221203-target-10-minutes-cicd.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: Target 10 minutes cicd builds to improve our iterations",
     "section": "",
-    "text": "No, the enhancement involves a significant change in the IK system’s implementation and cannot be easily worked around with a script."
+    "text": "Try to aim for 10 minute builds and reduce stress."
   },
   {
-    "objectID": "decisions/20230525-animation-ik-node.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230525-animation-ik-node.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Convert IK solvers to be using the AnimationTree",
+    "objectID": "decisions/20221203-target-10-minutes-cicd.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20221203-target-10-minutes-cicd.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Target 10 minutes cicd builds to improve our iterations",
     "section": "",
-    "text": "Yes, addressing the limitations of the current IK system is crucial for improving V-Sekai’s functionality and providing a better experience for users."
+    "text": "Try to aim for the godot cicd builds to finish in 10 minute."
   },
   {
-    "objectID": "decisions/20230525-animation-ik-node.html#references",
-    "href": "decisions/20230525-animation-ik-node.html#references",
-    "title": "Proposed: Convert IK solvers to be using the AnimationTree",
+    "objectID": "decisions/20221203-target-10-minutes-cicd.html#positive-consequences",
+    "href": "decisions/20221203-target-10-minutes-cicd.html#positive-consequences",
+    "title": "Proposed: Target 10 minutes cicd builds to improve our iterations",
     "section": "",
-    "text": "V-Sekai\nManyBoneIK3D (mentioned for reference purposes only)"
+    "text": "We can see the results of our work."
   },
   {
-    "objectID": "decisions/20210523-simplfy-meshes-and-lods-better-with-quads.html",
-    "href": "decisions/20210523-simplfy-meshes-and-lods-better-with-quads.html",
-    "title": "Proposed: Simplify Meshes and LODs better with Quads",
+    "objectID": "decisions/20221203-target-10-minutes-cicd.html#negative-consequences",
+    "href": "decisions/20221203-target-10-minutes-cicd.html#negative-consequences",
+    "title": "Proposed: Target 10 minutes cicd builds to improve our iterations",
     "section": "",
-    "text": "Better mesh simplification and LODs that work on quads.\nCharacters that use subdivision look much better and be a difference between 18,000 quads and millions of quads.\n\n\n\nResearch a way to do subdivsion and decimation on quads.\n\n\nTo be determined.\n\n\n\n\nVisual Quality\nMaintainability\n\n\n\n\n\nTechnical complexity\n\n(this section can be repeated for each option, if more than one option is open for consideration\n\n\n\n\nList the proposed options no longer open for consideration.\nList the reasons for the rejection: (the Bad traits)\n\n\n\nNot trivial to do.\n\n\n\nWe want the source art to be in quads so we can post process it in the game.\n\n\n\n\nhttps://gdcvault.com/play/1026752/Quad-Mesh-Simplification-in\nhttps://github.com/godotengine/godot-proposals/issues/3861\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Might need to do special tricks."
   },
   {
-    "objectID": "decisions/20210523-simplfy-meshes-and-lods-better-with-quads.html#context-and-problem-statement",
-    "href": "decisions/20210523-simplfy-meshes-and-lods-better-with-quads.html#context-and-problem-statement",
-    "title": "Proposed: Simplify Meshes and LODs better with Quads",
+    "objectID": "decisions/20221203-target-10-minutes-cicd.html#option-graveyard",
+    "href": "decisions/20221203-target-10-minutes-cicd.html#option-graveyard",
+    "title": "Proposed: Target 10 minutes cicd builds to improve our iterations",
     "section": "",
-    "text": "Better mesh simplification and LODs that work on quads.\nCharacters that use subdivision look much better and be a difference between 18,000 quads and millions of quads."
+    "text": "Option: The status quo. \nRejection Reason: This solves nothing."
   },
   {
-    "objectID": "decisions/20210523-simplfy-meshes-and-lods-better-with-quads.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20210523-simplfy-meshes-and-lods-better-with-quads.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: Simplify Meshes and LODs better with Quads",
+    "objectID": "decisions/20221203-target-10-minutes-cicd.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20221203-target-10-minutes-cicd.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Target 10 minutes cicd builds to improve our iterations",
     "section": "",
-    "text": "Research a way to do subdivsion and decimation on quads.\n\n\nTo be determined.\n\n\n\n\nVisual Quality\nMaintainability\n\n\n\n\n\nTechnical complexity\n\n(this section can be repeated for each option, if more than one option is open for consideration"
+    "text": "This is a dev ops change."
   },
   {
-    "objectID": "decisions/20210523-simplfy-meshes-and-lods-better-with-quads.html#option-graveyard-tris",
-    "href": "decisions/20210523-simplfy-meshes-and-lods-better-with-quads.html#option-graveyard-tris",
-    "title": "Proposed: Simplify Meshes and LODs better with Quads",
+    "objectID": "decisions/20221203-target-10-minutes-cicd.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20221203-target-10-minutes-cicd.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Target 10 minutes cicd builds to improve our iterations",
     "section": "",
-    "text": "List the proposed options no longer open for consideration.\nList the reasons for the rejection: (the Bad traits)"
+    "text": "We own the github repositories."
   },
   {
-    "objectID": "decisions/20210523-simplfy-meshes-and-lods-better-with-quads.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20210523-simplfy-meshes-and-lods-better-with-quads.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Simplify Meshes and LODs better with Quads",
+    "objectID": "decisions/20221203-target-10-minutes-cicd.html#references",
+    "href": "decisions/20221203-target-10-minutes-cicd.html#references",
+    "title": "Proposed: Target 10 minutes cicd builds to improve our iterations",
     "section": "",
-    "text": "Not trivial to do."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20210523-simplfy-meshes-and-lods-better-with-quads.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20210523-simplfy-meshes-and-lods-better-with-quads.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Simplify Meshes and LODs better with Quads",
+    "objectID": "decisions/20221203-target-10-minutes-cicd.html#license-of-the-contribution",
+    "href": "decisions/20221203-target-10-minutes-cicd.html#license-of-the-contribution",
+    "title": "Proposed: Target 10 minutes cicd builds to improve our iterations",
     "section": "",
-    "text": "We want the source art to be in quads so we can post process it in the game."
+    "text": "Copyright (c) 2022 K. S. Ernest (iFire) Lee Copyright (c) 2022 V-Sekai contributors\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20210523-simplfy-meshes-and-lods-better-with-quads.html#references",
-    "href": "decisions/20210523-simplfy-meshes-and-lods-better-with-quads.html#references",
-    "title": "Proposed: Simplify Meshes and LODs better with Quads",
+    "objectID": "decisions/20220131-github-actions-support.html",
+    "href": "decisions/20220131-github-actions-support.html",
+    "title": "Accepted: To have an alternative CICD use Github Actions.",
     "section": "",
-    "text": "https://gdcvault.com/play/1026752/Quad-Mesh-Simplification-in\nhttps://github.com/godotengine/godot-proposals/issues/3861"
+    "text": "Status: accepted \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nGitHub actions is free and does not require running your own hardware for CI/CD. We understand some users may desire to use this route to build our system.\nHowever, we also want our system to be fully self hosted, so as a compromise, we may wish to offer first-party support for both types of continuous integration.\n\n\n\nWe will offer github actions files in our official Godot fork as well as our V-Sekai project.\n\n\n\nWe will generate github actions templates using the same jsonnet we use for GoCD.\n\n\n\n\nThe social network of GitHub is more accessible to most people.\nOffers more options for building our infrastructure and ways to get into Godot development, which is good.\nGitHub’s donated compute time may free up valuable compute resources for more critical operations.\n\n\n\n\n\nMaintaining more scripts requires our developer time\nMore codepaths means more QA or pieces that can break.\n\n\n\n\n\nOption: Keep the status quo, which is using GoCD or building manually on the command line.\nRejection Reason: Building manually on the command line is slow on Windows and not reproducible;\nRejection Reason: GoCD is inaccessible to most developers.\n\n\n\n\nIt can.\n\n\n\nWe want to maintain it to encourage developers and as the publisher of the platform it is our responsibility.\n\n\n\n\nhttps://jsonnet.org/\nhttps://docs.github.com/en/billing/managing-billing-for-github-actions/about-billing-for-github-actions\n\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20210523-simplfy-meshes-and-lods-better-with-quads.html#derivative-license",
-    "href": "decisions/20210523-simplfy-meshes-and-lods-better-with-quads.html#derivative-license",
-    "title": "Proposed: Simplify Meshes and LODs better with Quads",
+    "objectID": "decisions/20220131-github-actions-support.html#context-and-problem-statement",
+    "href": "decisions/20220131-github-actions-support.html#context-and-problem-statement",
+    "title": "Accepted: To have an alternative CICD use Github Actions.",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "GitHub actions is free and does not require running your own hardware for CI/CD. We understand some users may desire to use this route to build our system.\nHowever, we also want our system to be fully self hosted, so as a compromise, we may wish to offer first-party support for both types of continuous integration."
   },
   {
-    "objectID": "decisions/attachments/pitch_apple_vision_01.html",
-    "href": "decisions/attachments/pitch_apple_vision_01.html",
-    "title": "V-Sekai offer immersive experiences in various virtual environments.",
+    "objectID": "decisions/20220131-github-actions-support.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20220131-github-actions-support.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Accepted: To have an alternative CICD use Github Actions.",
     "section": "",
-    "text": "V-Sekai, a proposed VR app for Apple Vision Pro, aims to offer immersive experiences in various virtual environments.\n\n\n\nSpatial Awareness: For interactive VR environments and enhancing 3D doodling and Virtual Avatar Performance.\nHigh Resolution Display: Utilizes Apple Vision Pro’s display for detailed VR rendering.\nVoice Communication: Allows user communication via voice chat.\n\n\n\n\n\nEye Tracking: Facilitates navigation and selection within the VR world.\nHand Gesture Recognition: Enables interaction with VR objects.\nProposed Machine Learning Technologies: Implements proposed speech-to-text and text-to-speech capabilities for real-time transcription and voice synthesis.\n\n\n\n\nV-Sekai offers exploration of pre-designed worlds or creation of custom ones. Users can manipulate VR objects, navigate menus with eye-tracking, and communicate via voice chat. Machine learning technologies enhance accessibility and interactivity. Spatial awareness adds depth to 3D doodling and Virtual Avatar Performance."
+    "text": "We will offer github actions files in our official Godot fork as well as our V-Sekai project."
   },
   {
-    "objectID": "decisions/attachments/pitch_apple_vision_01.html#key-features",
-    "href": "decisions/attachments/pitch_apple_vision_01.html#key-features",
-    "title": "V-Sekai offer immersive experiences in various virtual environments.",
+    "objectID": "decisions/20220131-github-actions-support.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20220131-github-actions-support.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Accepted: To have an alternative CICD use Github Actions.",
     "section": "",
-    "text": "Spatial Awareness: For interactive VR environments and enhancing 3D doodling and Virtual Avatar Performance.\nHigh Resolution Display: Utilizes Apple Vision Pro’s display for detailed VR rendering.\nVoice Communication: Allows user communication via voice chat."
+    "text": "We will generate github actions templates using the same jsonnet we use for GoCD."
   },
   {
-    "objectID": "decisions/attachments/pitch_apple_vision_01.html#proposed-features",
-    "href": "decisions/attachments/pitch_apple_vision_01.html#proposed-features",
-    "title": "V-Sekai offer immersive experiences in various virtual environments.",
+    "objectID": "decisions/20220131-github-actions-support.html#positive-consequences",
+    "href": "decisions/20220131-github-actions-support.html#positive-consequences",
+    "title": "Accepted: To have an alternative CICD use Github Actions.",
     "section": "",
-    "text": "Eye Tracking: Facilitates navigation and selection within the VR world.\nHand Gesture Recognition: Enables interaction with VR objects.\nProposed Machine Learning Technologies: Implements proposed speech-to-text and text-to-speech capabilities for real-time transcription and voice synthesis."
+    "text": "The social network of GitHub is more accessible to most people.\nOffers more options for building our infrastructure and ways to get into Godot development, which is good.\nGitHub’s donated compute time may free up valuable compute resources for more critical operations."
   },
   {
-    "objectID": "decisions/attachments/pitch_apple_vision_01.html#user-experience",
-    "href": "decisions/attachments/pitch_apple_vision_01.html#user-experience",
-    "title": "V-Sekai offer immersive experiences in various virtual environments.",
+    "objectID": "decisions/20220131-github-actions-support.html#negative-consequences",
+    "href": "decisions/20220131-github-actions-support.html#negative-consequences",
+    "title": "Accepted: To have an alternative CICD use Github Actions.",
     "section": "",
-    "text": "V-Sekai offers exploration of pre-designed worlds or creation of custom ones. Users can manipulate VR objects, navigate menus with eye-tracking, and communicate via voice chat. Machine learning technologies enhance accessibility and interactivity. Spatial awareness adds depth to 3D doodling and Virtual Avatar Performance."
+    "text": "Maintaining more scripts requires our developer time\nMore codepaths means more QA or pieces that can break."
   },
   {
-    "objectID": "decisions/attachments/thunderbolt_install_windows.html",
-    "href": "decisions/attachments/thunderbolt_install_windows.html",
-    "title": "Thunderbolt Driver Issue Solution",
+    "objectID": "decisions/20220131-github-actions-support.html#option-graveyard",
+    "href": "decisions/20220131-github-actions-support.html#option-graveyard",
+    "title": "Accepted: To have an alternative CICD use Github Actions.",
     "section": "",
-    "text": "Thunderbolt Driver Issue Solution\nTo all who end up in this thread, as I did. Welcome\nAnother user in this thread had a solution that worked for me, so I will repeat it with a more detailed explanation.\nCredit to “Johnatan” on page 3\nThe issue is that the new Thunderbolt drivers fail to remove and overwrite the old drivers. The problem can be resolved through the device manager.\nRight-click on “Start” (the Windows icon at the corner of your taskbar) and select “Device Manager.”\nWithin the device manager, open the category “System Devices.”\nScroll down to Thunderbolt(TM) Controller - (model number here)\n*Right-click on it, select “Uninstall Device,” and check the box “Delete the driver software for this device.”\nOnce removed, rerun the Thunderbolt installer or the update through the Dell Command Updater.\n*If you are worried about uninstalling the driver in the device manager, fret not. The driver will reinstall itself on reboot if you have an internet connection."
+    "text": "Option: Keep the status quo, which is using GoCD or building manually on the command line.\nRejection Reason: Building manually on the command line is slow on Windows and not reproducible;\nRejection Reason: GoCD is inaccessible to most developers."
   },
   {
-    "objectID": "decisions/attachments/project_mirage.html",
-    "href": "decisions/attachments/project_mirage.html",
-    "title": "Project Mirage",
+    "objectID": "decisions/20220131-github-actions-support.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20220131-github-actions-support.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Accepted: To have an alternative CICD use Github Actions.",
     "section": "",
-    "text": "Project Mirage\n\n\n\n\n\n\n\n\nStep\nDescription\nDependency\n\n\n\n\n1\nAn avatar’s face is created in a digital format, similar to drawing a portrait on a computer.\nNone\n\n\n2\nThe colors of the avatar are changed using Penpot, like using a digital paintbrush to change the color of a painting.\nCreated digital avatar\n\n\n3\nThe best looking avatars are chosen from a large group, like picking the best apples from a tree.\nChanged colors of the avatar\n\n\n4\nA body is added to the avatar using Blender’s CC0 base mesh, like adding a body to a mannequin head.\nChosen best looking avatars\n\n\n5\nAn attempt is made to create a 3D model of the back of the avatar (this wasn’t successful), like trying to sculpt the back of a statue but not getting it right.\nAdded body to the avatar\n\n\n6\nA tool is used to simplify any image, like using an eraser to remove details from a sketch.\nUnsuccessful attempt to create a 3D model of the back of the avatar\n\n\n7\nClothing and accessories are added to the avatar for Vroid Hub, like dressing up a doll.\nSimplified image\n\n\n8\nA 2D reference image is used in Blender, like using a photograph to help draw a picture.\nAdded clothing and accessories to the avatar\n\n\n9\nThe 2D image is placed in front of the 3D model, like placing a picture in front of a sculpture to use as a reference.\nUsed 2D reference image in Blender\n\n\n10\nAn image is captured from the camera’s point of view and sharpened, like taking a photo and then enhancing its clarity.\nPlaced 2D image in front of the 3D model\n\n\n11\nA tool is used that takes any image and generates a text caption, like writing a description for a photograph.\nCaptured and sharpened image from the camera’s point of view\n\n\n12\nThe color of the clothing is corrected and the pleated folds are ignored for the first try, like adjusting the colors in a painting and ignoring the small details for now.\nGenerated text caption from image\n\n\n13\nA complex structure involving sculpting and rigging is created, like building a skeleton for a clay model.\nCorrected color of the clothing\n\n\n14\nThe avatar is imported into Godot Engine and “Project Mirage”, like moving a digital file from one folder to another.\nCreated complex structure involving sculpting and rigging\n\n\n15\nThe imported avatar is refined in “Project Mirage”, like polishing a newly built machine.\nImported avatar into Godot Engine and “Project Mirage”\n\n\n16\nSpring bone “jiggle bones” are converted to phys bones and colliders, like changing the springs in a toy to make it more realistic.\nRefined the imported avatar in “Project Mirage”\n\n\n17\nPainting errors such as shirt seams and mesh clipping problems with the spine bone remain, like leaving some imperfections in a painting.\nConverted spring bone “jiggle bones” to phys bones and colliders\n\n\n18\nA choice is made between using the existing VRM MToon material in “Project Mirage” or using a friend’s custom SCSS shader, like choosing between two different types of paint for a painting.\nLeft painting errors unfixed\n\n\n19\nIssues with “Project Mirage”’s material counts and bones are dealt with, like solving problems in a complex puzzle.\nMade a choice between using the existing VRM MToon material in “Project Mirage” or using a friend’s custom SCSS shader\n\n\n20\nA process is established for moving files between “Project Mirage” and Godot Engine, like setting up a conveyor belt between two factories.\nDealt with issues with “Project Mirage”’s material counts and bones\n\n\n21\nVroid Hub’s hair painter and mesh generator are used, like using a special tool to add hair to a doll.\nEstablished process for moving files between “Project Mirage” and Godot Engine\n\n\n22\n“Perfect sync”, which are facial expressions for motion capture, is added, like giving a puppet the ability to show emotions.\nUsed Vroid Hub’s hair painter and mesh generator\n\n\n23\nMotion capture is set up using the Steam VR Lighthouse system, overcoming significant difficulties, like setting up a complex tracking system to record movements.\nAdded “perfect sync” facial expressions for motion capture"
+    "text": "It can."
   },
   {
-    "objectID": "decisions/20230516-additional-3d-import.html",
-    "href": "decisions/20230516-additional-3d-import.html",
-    "title": "Rejected: Additional 3D Import Functionality",
+    "objectID": "decisions/20220131-github-actions-support.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20220131-github-actions-support.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Accepted: To have an alternative CICD use Github Actions.",
     "section": "",
-    "text": "Status: rejected \nDeciders: V-Sekai,fire,\nTags: V-Sekai,ChatGPT-4,AI_assistance\n\n\n\n\nImprove the 3D import functionality in Godot Engine for V-Sekai by enhancing the existing import process and adding support for more file formats.\nThis proposal is rejected because it doesn’t improve the 3D import functionality compared to its effort\n\n\n\n\nStatus: proposed\nDeciders: V-Sekai\nTags: V-Sekai, GPT-4\n\n\n\n\nV-Sekai has implemented .fbx and .gltf 3D import, and .obj is already part of Godot Engine. However, there is still room for improvement in the import process and support for additional file formats. The current Blender importer for Godot Engine 4.0 requires an additional installation and injects a Python script into Blender.\n\n\n\n\nDevelop an addon that can simultaneously export colliders, occluders, and LOD variants for a given mesh without requiring an additional Blender importer.\nEnhance the existing import process by providing better error handling, reporting, and automatic fixes for common issues.\nImprove the performance of the import process, especially for large and complex 3D models.\n\n\n\n\n\nCreate an addon that automatically searches for and sets Geometry Nodes input constants with relevant names (e.g., is_occluder, is_collider, and LOD) while exporting, giving modelers maximum flexibility on how different versions of a mesh should be exported. This addon should not require an additional Blender importer or Python script injection.\nUpdate the import pipeline to handle errors gracefully and provide helpful feedback to users.\nOptimize the import process by implementing caching, parallel processing, and other performance improvements.\n\n\n\n\n\nUsers will have more control over the export process, allowing them to easily manage colliders, occluders, and LOD variants without needing an additional Blender importer.\nThe improved import process will reduce the time spent on fixing import-related issues.\nFaster import times will lead to a smoother development experience.\n\n\n\n\n\nDeveloping an addon may require additional resources and maintenance.\nThere might be potential licensing issues with integrating third-party libraries.\n\n\n\n\n\nRelying solely on community plugins for additional import functionality.\nLimiting support to only a few popular file formats.\n\n\n\n\nNo, this enhancement addresses a core limitation in the engine and requires significant changes to the import pipeline.\n\n\n\nYes, improving the 3D import functionality is essential for providing a better user experience and supporting a wider range of 3D modeling tools. It also ensures that V-Sekai remains competitive with other game engines.\n\n\n\n\nV-Sekai"
+    "text": "We want to maintain it to encourage developers and as the publisher of the platform it is our responsibility."
   },
   {
-    "objectID": "decisions/20230516-additional-3d-import.html#metadata",
-    "href": "decisions/20230516-additional-3d-import.html#metadata",
-    "title": "Rejected: Additional 3D Import Functionality",
+    "objectID": "decisions/20220131-github-actions-support.html#references",
+    "href": "decisions/20220131-github-actions-support.html#references",
+    "title": "Accepted: To have an alternative CICD use Github Actions.",
     "section": "",
-    "text": "Status: rejected \nDeciders: V-Sekai,fire,\nTags: V-Sekai,ChatGPT-4,AI_assistance"
+    "text": "https://jsonnet.org/\nhttps://docs.github.com/en/billing/managing-billing-for-github-actions/about-billing-for-github-actions"
   },
   {
-    "objectID": "decisions/20230516-additional-3d-import.html#propose-a-possible-solution-to-solve-a-v-sekai-limitation.-if-this-doesnt-look-right-choose-a-different-type.",
-    "href": "decisions/20230516-additional-3d-import.html#propose-a-possible-solution-to-solve-a-v-sekai-limitation.-if-this-doesnt-look-right-choose-a-different-type.",
-    "title": "Rejected: Additional 3D Import Functionality",
+    "objectID": "decisions/20220131-github-actions-support.html#derivative-license",
+    "href": "decisions/20220131-github-actions-support.html#derivative-license",
+    "title": "Accepted: To have an alternative CICD use Github Actions.",
     "section": "",
-    "text": "Improve the 3D import functionality in Godot Engine for V-Sekai by enhancing the existing import process and adding support for more file formats.\nThis proposal is rejected because it doesn’t improve the 3D import functionality compared to its effort"
+    "text": "Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230516-additional-3d-import.html#metadata-1",
-    "href": "decisions/20230516-additional-3d-import.html#metadata-1",
-    "title": "Rejected: Additional 3D Import Functionality",
+    "objectID": "decisions/20211005-create-sop-for-vrm-creation.html",
+    "href": "decisions/20211005-create-sop-for-vrm-creation.html",
+    "title": "Proposed: Create SOP for VRM #creation",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, GPT-4"
+    "text": "Proposed: Create SOP for VRM #creation\n\nContext and Problem Statement\nCreate SOP for VRM #creation\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nHard to Get character #creation correct.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nList checkable prescriptions.\n\nSeparate Head from the body?\nMake sure every other mesh than the head mesh has no Head bone weights.\nDisable automatic mesh merging\nVertex weighting vs masking vs vrm spring bones\nSeparate leg weighting from each other with putting the character into the spread pose.\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nIs a workflow.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nNo one else is doing it.\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230516-additional-3d-import.html#context-and-problem-statement",
-    "href": "decisions/20230516-additional-3d-import.html#context-and-problem-statement",
-    "title": "Rejected: Additional 3D Import Functionality",
+    "objectID": "decisions/20221205-debug-linux-export.html",
+    "href": "decisions/20221205-debug-linux-export.html",
+    "title": "Proposed: Debug Linux Export",
     "section": "",
-    "text": "V-Sekai has implemented .fbx and .gltf 3D import, and .obj is already part of Godot Engine. However, there is still room for improvement in the import process and support for additional file formats. The current Blender importer for Godot Engine 4.0 requires an additional installation and injects a Python script into Blender."
+    "text": "Status: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nIt is hard to debug exports on Linux without using Linux as a desktop environment. There is a crash on export.\n\n\n\nPropose a workflow for debugging linux exports.\n\n\n\nUse wsl or a virtual machine.\n\nDownload the exact version of the editor that crashes on export.\nDownload the game templates.\nRun the export in a debugger\nFind the bug.\n\n\n\n\n\nWe can export again\nWriting down the workflow makes use be able to reuse processes.\n\n\n\n\nWe need to download the binaries manually for now.\n\n\n\n\nOption: The status quo. \nRejection Reason: This solves nothing. \nOption: Compile the package manually \nRejection Reason: This solves nothing because it is all manually and undocumented \n\n\n\n\nThis is a workflow document.\n\n\n\nWe have to build V-Sekai.\n\n\n\n\nV-Sekai\n\n\n\n\nMIT License\n\nCopyright (c) 2018-2022 SaracenOne\nCopyright (c) 2019-2022 K. S. Ernest (iFire) Lee (fire)\nCopyright (c) 2020-2022 Lyuma\nCopyright (c) 2020-2022 MMMaellon\nCopyright (c) 2022 V-Sekai Contributors\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
   },
   {
-    "objectID": "decisions/20230516-additional-3d-import.html#proposed-solution",
-    "href": "decisions/20230516-additional-3d-import.html#proposed-solution",
-    "title": "Rejected: Additional 3D Import Functionality",
+    "objectID": "decisions/20221205-debug-linux-export.html#context-and-problem-statement",
+    "href": "decisions/20221205-debug-linux-export.html#context-and-problem-statement",
+    "title": "Proposed: Debug Linux Export",
     "section": "",
-    "text": "Develop an addon that can simultaneously export colliders, occluders, and LOD variants for a given mesh without requiring an additional Blender importer.\nEnhance the existing import process by providing better error handling, reporting, and automatic fixes for common issues.\nImprove the performance of the import process, especially for large and complex 3D models."
+    "text": "It is hard to debug exports on Linux without using Linux as a desktop environment. There is a crash on export."
   },
   {
-    "objectID": "decisions/20230516-additional-3d-import.html#implementation",
-    "href": "decisions/20230516-additional-3d-import.html#implementation",
-    "title": "Rejected: Additional 3D Import Functionality",
+    "objectID": "decisions/20221205-debug-linux-export.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20221205-debug-linux-export.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: Debug Linux Export",
     "section": "",
-    "text": "Create an addon that automatically searches for and sets Geometry Nodes input constants with relevant names (e.g., is_occluder, is_collider, and LOD) while exporting, giving modelers maximum flexibility on how different versions of a mesh should be exported. This addon should not require an additional Blender importer or Python script injection.\nUpdate the import pipeline to handle errors gracefully and provide helpful feedback to users.\nOptimize the import process by implementing caching, parallel processing, and other performance improvements."
+    "text": "Propose a workflow for debugging linux exports."
   },
   {
-    "objectID": "decisions/20230516-additional-3d-import.html#positive-consequences",
-    "href": "decisions/20230516-additional-3d-import.html#positive-consequences",
-    "title": "Rejected: Additional 3D Import Functionality",
+    "objectID": "decisions/20221205-debug-linux-export.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20221205-debug-linux-export.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Debug Linux Export",
     "section": "",
-    "text": "Users will have more control over the export process, allowing them to easily manage colliders, occluders, and LOD variants without needing an additional Blender importer.\nThe improved import process will reduce the time spent on fixing import-related issues.\nFaster import times will lead to a smoother development experience."
+    "text": "Use wsl or a virtual machine.\n\nDownload the exact version of the editor that crashes on export.\nDownload the game templates.\nRun the export in a debugger\nFind the bug."
   },
   {
-    "objectID": "decisions/20230516-additional-3d-import.html#negative-consequences",
-    "href": "decisions/20230516-additional-3d-import.html#negative-consequences",
-    "title": "Rejected: Additional 3D Import Functionality",
+    "objectID": "decisions/20221205-debug-linux-export.html#positive-consequences",
+    "href": "decisions/20221205-debug-linux-export.html#positive-consequences",
+    "title": "Proposed: Debug Linux Export",
     "section": "",
-    "text": "Developing an addon may require additional resources and maintenance.\nThere might be potential licensing issues with integrating third-party libraries."
+    "text": "We can export again\nWriting down the workflow makes use be able to reuse processes."
   },
   {
-    "objectID": "decisions/20230516-additional-3d-import.html#option-graveyard",
-    "href": "decisions/20230516-additional-3d-import.html#option-graveyard",
-    "title": "Rejected: Additional 3D Import Functionality",
+    "objectID": "decisions/20221205-debug-linux-export.html#negative-consequences",
+    "href": "decisions/20221205-debug-linux-export.html#negative-consequences",
+    "title": "Proposed: Debug Linux Export",
     "section": "",
-    "text": "Relying solely on community plugins for additional import functionality.\nLimiting support to only a few popular file formats."
+    "text": "We need to download the binaries manually for now."
   },
   {
-    "objectID": "decisions/20230516-additional-3d-import.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230516-additional-3d-import.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Rejected: Additional 3D Import Functionality",
+    "objectID": "decisions/20221205-debug-linux-export.html#option-graveyard",
+    "href": "decisions/20221205-debug-linux-export.html#option-graveyard",
+    "title": "Proposed: Debug Linux Export",
     "section": "",
-    "text": "No, this enhancement addresses a core limitation in the engine and requires significant changes to the import pipeline."
+    "text": "Option: The status quo. \nRejection Reason: This solves nothing. \nOption: Compile the package manually \nRejection Reason: This solves nothing because it is all manually and undocumented"
   },
   {
-    "objectID": "decisions/20230516-additional-3d-import.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230516-additional-3d-import.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Rejected: Additional 3D Import Functionality",
+    "objectID": "decisions/20221205-debug-linux-export.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20221205-debug-linux-export.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Debug Linux Export",
     "section": "",
-    "text": "Yes, improving the 3D import functionality is essential for providing a better user experience and supporting a wider range of 3D modeling tools. It also ensures that V-Sekai remains competitive with other game engines."
+    "text": "This is a workflow document."
   },
   {
-    "objectID": "decisions/20230516-additional-3d-import.html#references",
-    "href": "decisions/20230516-additional-3d-import.html#references",
-    "title": "Rejected: Additional 3D Import Functionality",
+    "objectID": "decisions/20221205-debug-linux-export.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20221205-debug-linux-export.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Debug Linux Export",
     "section": "",
-    "text": "V-Sekai"
+    "text": "We have to build V-Sekai."
   },
   {
-    "objectID": "decisions/20231108-nier-automata-world-expansion.html",
-    "href": "decisions/20231108-nier-automata-world-expansion.html",
-    "title": "Proposed: “Freedom is in a future that you did not have in the past” - A Game Development Philosophy from NieR:Automata",
+    "objectID": "decisions/20221205-debug-linux-export.html#references",
+    "href": "decisions/20221205-debug-linux-export.html#references",
+    "title": "Proposed: Debug Linux Export",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, Game Development, Open-world, Rich Content\n\n\n\n\nDuring GDC 2018, Yoko Taro and Takahisa Taura, key figures behind the creation of ‘NieR:Automata’, shared their insights on game development. Their panel was among the most attended, shedding light on the philosophy of game development and the intricacies of crafting an immersive world.\n\n\n\nThe primary challenge in game development lies in striking a balance between open-world freedom and rich content. While gamers often equate ultimate freedom with open-world games, many such titles lack depth. The goal should be to design the right gameplay mechanics while ensuring high player immersion.\n\n\n\n\n“Freedom is in a future that you did not have in the past” - Yoko Taro (40:40)\n\nYoko Taro emphasized the importance of incorporating freedom in a game while maintaining a balance between an open-world and rich content. He drew inspiration from The Legend of Zelda: Ocarina of Time when building the world of NieR. This strategy involves creating easy-to-learn gameplay without hindering the flow of the experience.\n\n\n\nThis approach fosters a more immersive gaming experience. By concentrating on the appropriate gameplay mechanics and balancing open-world freedom with rich content, developers can produce games that are both engaging and meaningful.\n\n\n\nThe downside to this approach is that it may necessitate more time and resources for development. Achieving a balance between open-world freedom and rich content can be a complex task, demanding meticulous planning and execution.\n\n\n\nAn alternative strategy could involve focusing exclusively on either open-world freedom or rich content. However, this could lead to a game that lacks depth or fails to fully captivate players.\n\n\n\nThis approach may not be suitable for all types of games. For instance, games that are heavily story-driven may not benefit from an open-world format.\n\n\n\nThis strategy is in line with our core philosophy of game development. We believe in crafting immersive experiences that balance freedom with rich content.\n\n\n\nFor more insights on this topic, consider the following resources:\n\nV-Sekai: The official GitHub page of V-Sekai, featuring various projects and initiatives related to game development.\nGDC 2018: A Fun Time in Which Some No-Good Game Developers May Discuss How We Made ‘NieR:Automata’: A comprehensive report on the GDC 2018 panel featuring Yoko Taro and Takahisa Taura discussing the creation process of ‘NieR:Automata’.\nGDC 2018 Video: A Fun Time in Which Some No-Good Game Developers May Discuss How We Made ‘NieR:Automata’\n\nThis article was assisted by AI."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20231108-nier-automata-world-expansion.html#metadata",
-    "href": "decisions/20231108-nier-automata-world-expansion.html#metadata",
-    "title": "Proposed: “Freedom is in a future that you did not have in the past” - A Game Development Philosophy from NieR:Automata",
+    "objectID": "decisions/20221205-debug-linux-export.html#license-of-the-contribution",
+    "href": "decisions/20221205-debug-linux-export.html#license-of-the-contribution",
+    "title": "Proposed: Debug Linux Export",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, Game Development, Open-world, Rich Content"
+    "text": "MIT License\n\nCopyright (c) 2018-2022 SaracenOne\nCopyright (c) 2019-2022 K. S. Ernest (iFire) Lee (fire)\nCopyright (c) 2020-2022 Lyuma\nCopyright (c) 2020-2022 MMMaellon\nCopyright (c) 2022 V-Sekai Contributors\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
   },
   {
-    "objectID": "decisions/20231108-nier-automata-world-expansion.html#context",
-    "href": "decisions/20231108-nier-automata-world-expansion.html#context",
-    "title": "Proposed: “Freedom is in a future that you did not have in the past” - A Game Development Philosophy from NieR:Automata",
+    "objectID": "decisions/20211031-benchmark-animation-playback.html",
+    "href": "decisions/20211031-benchmark-animation-playback.html",
+    "title": "Proposed: Benchmark #animation playback",
     "section": "",
-    "text": "During GDC 2018, Yoko Taro and Takahisa Taura, key figures behind the creation of ‘NieR:Automata’, shared their insights on game development. Their panel was among the most attended, shedding light on the philosophy of game development and the intricacies of crafting an immersive world."
+    "text": "Proposed: Benchmark #animation playback\n\nContext and Problem Statement\nHow slow is #animation playback in a simulated player situation.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nNeed to see where we’re at.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n100, 500, 1’000, 50’000 avatars animating with 30fps and #animation compression on vs off.\nRandomize clips: idle, run, jump, walk (left, right, back, front)\nPut them into a 2d blend space and feed a random velocity.\nStart the #animation at different random offsets.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nCore code.\n\n\nPositive Consequences\n\nCan investigate compressed #animation player as a compute shader. The current architecture of the skinning and blend shapes #animation is like vertex #animation fed by buffers, but the keyframe playback is also problematic\n\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nI care about this more than other core contributors.\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20231108-nier-automata-world-expansion.html#problem",
-    "href": "decisions/20231108-nier-automata-world-expansion.html#problem",
-    "title": "Proposed: “Freedom is in a future that you did not have in the past” - A Game Development Philosophy from NieR:Automata",
+    "objectID": "decisions/20230131-default-test-plan.html",
+    "href": "decisions/20230131-default-test-plan.html",
+    "title": "Accepted: Default test plan for testing V-Sekai engine upgrades.",
     "section": "",
-    "text": "The primary challenge in game development lies in striking a balance between open-world freedom and rich content. While gamers often equate ultimate freedom with open-world games, many such titles lack depth. The goal should be to design the right gameplay mechanics while ensuring high player immersion."
+    "text": "Status: accepted \nDeciders: V-Sekai,fire,\nTags: V-Sekai,\n\n\n\nWant to write down the default test plan for V-sekai on engine upgrades.\n\n\n\nWrite the default test plans.\n\n\n\n\nCheck if OpenXR godot works by joining a server.\nOn pancake desktop mode, check if two clients connect to a 1 server and see each other’s movements.\nCheck if you can export a map.\nWIP Check audio io\n\n\n\n\nThese are the default things that should work.\n\n\n\nWork.\n\n\n\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\n\nThis is a standard procedure.\n\n\n\nWe need to test our work.\n\n\n\n\nV-Sekai\n\n\n\n\nMIT License\n\nCopyright (c) 2019-2022 K. S. Ernest (iFire) Lee (fire)\nCopyright (c) 2022 V-Sekai Contributors\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
   },
   {
-    "objectID": "decisions/20231108-nier-automata-world-expansion.html#strategy",
-    "href": "decisions/20231108-nier-automata-world-expansion.html#strategy",
-    "title": "Proposed: “Freedom is in a future that you did not have in the past” - A Game Development Philosophy from NieR:Automata",
+    "objectID": "decisions/20230131-default-test-plan.html#context-and-problem-statement",
+    "href": "decisions/20230131-default-test-plan.html#context-and-problem-statement",
+    "title": "Accepted: Default test plan for testing V-Sekai engine upgrades.",
     "section": "",
-    "text": "“Freedom is in a future that you did not have in the past” - Yoko Taro (40:40)\n\nYoko Taro emphasized the importance of incorporating freedom in a game while maintaining a balance between an open-world and rich content. He drew inspiration from The Legend of Zelda: Ocarina of Time when building the world of NieR. This strategy involves creating easy-to-learn gameplay without hindering the flow of the experience."
+    "text": "Want to write down the default test plan for V-sekai on engine upgrades."
   },
   {
-    "objectID": "decisions/20231108-nier-automata-world-expansion.html#pros",
-    "href": "decisions/20231108-nier-automata-world-expansion.html#pros",
-    "title": "Proposed: “Freedom is in a future that you did not have in the past” - A Game Development Philosophy from NieR:Automata",
+    "objectID": "decisions/20230131-default-test-plan.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20230131-default-test-plan.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Accepted: Default test plan for testing V-Sekai engine upgrades.",
     "section": "",
-    "text": "This approach fosters a more immersive gaming experience. By concentrating on the appropriate gameplay mechanics and balancing open-world freedom with rich content, developers can produce games that are both engaging and meaningful."
+    "text": "Write the default test plans."
   },
   {
-    "objectID": "decisions/20231108-nier-automata-world-expansion.html#cons",
-    "href": "decisions/20231108-nier-automata-world-expansion.html#cons",
-    "title": "Proposed: “Freedom is in a future that you did not have in the past” - A Game Development Philosophy from NieR:Automata",
+    "objectID": "decisions/20230131-default-test-plan.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20230131-default-test-plan.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Accepted: Default test plan for testing V-Sekai engine upgrades.",
     "section": "",
-    "text": "The downside to this approach is that it may necessitate more time and resources for development. Achieving a balance between open-world freedom and rich content can be a complex task, demanding meticulous planning and execution."
+    "text": "Check if OpenXR godot works by joining a server.\nOn pancake desktop mode, check if two clients connect to a 1 server and see each other’s movements.\nCheck if you can export a map.\nWIP Check audio io"
   },
   {
-    "objectID": "decisions/20231108-nier-automata-world-expansion.html#alternative-approach",
-    "href": "decisions/20231108-nier-automata-world-expansion.html#alternative-approach",
-    "title": "Proposed: “Freedom is in a future that you did not have in the past” - A Game Development Philosophy from NieR:Automata",
+    "objectID": "decisions/20230131-default-test-plan.html#positive-consequences",
+    "href": "decisions/20230131-default-test-plan.html#positive-consequences",
+    "title": "Accepted: Default test plan for testing V-Sekai engine upgrades.",
     "section": "",
-    "text": "An alternative strategy could involve focusing exclusively on either open-world freedom or rich content. However, this could lead to a game that lacks depth or fails to fully captivate players."
+    "text": "These are the default things that should work."
   },
   {
-    "objectID": "decisions/20231108-nier-automata-world-expansion.html#limited-use-case",
-    "href": "decisions/20231108-nier-automata-world-expansion.html#limited-use-case",
-    "title": "Proposed: “Freedom is in a future that you did not have in the past” - A Game Development Philosophy from NieR:Automata",
+    "objectID": "decisions/20230131-default-test-plan.html#negative-consequences",
+    "href": "decisions/20230131-default-test-plan.html#negative-consequences",
+    "title": "Accepted: Default test plan for testing V-Sekai engine upgrades.",
     "section": "",
-    "text": "This approach may not be suitable for all types of games. For instance, games that are heavily story-driven may not benefit from an open-world format."
+    "text": "Work."
   },
   {
-    "objectID": "decisions/20231108-nier-automata-world-expansion.html#alignment-with-our-core-philosophy",
-    "href": "decisions/20231108-nier-automata-world-expansion.html#alignment-with-our-core-philosophy",
-    "title": "Proposed: “Freedom is in a future that you did not have in the past” - A Game Development Philosophy from NieR:Automata",
+    "objectID": "decisions/20230131-default-test-plan.html#option-graveyard",
+    "href": "decisions/20230131-default-test-plan.html#option-graveyard",
+    "title": "Accepted: Default test plan for testing V-Sekai engine upgrades.",
     "section": "",
-    "text": "This strategy is in line with our core philosophy of game development. We believe in crafting immersive experiences that balance freedom with rich content."
+    "text": "Option: The status quo. \nRejection Reason: This solves nothing."
   },
   {
-    "objectID": "decisions/20231108-nier-automata-world-expansion.html#additional-resources",
-    "href": "decisions/20231108-nier-automata-world-expansion.html#additional-resources",
-    "title": "Proposed: “Freedom is in a future that you did not have in the past” - A Game Development Philosophy from NieR:Automata",
+    "objectID": "decisions/20230131-default-test-plan.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230131-default-test-plan.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Accepted: Default test plan for testing V-Sekai engine upgrades.",
     "section": "",
-    "text": "For more insights on this topic, consider the following resources:\n\nV-Sekai: The official GitHub page of V-Sekai, featuring various projects and initiatives related to game development.\nGDC 2018: A Fun Time in Which Some No-Good Game Developers May Discuss How We Made ‘NieR:Automata’: A comprehensive report on the GDC 2018 panel featuring Yoko Taro and Takahisa Taura discussing the creation process of ‘NieR:Automata’.\nGDC 2018 Video: A Fun Time in Which Some No-Good Game Developers May Discuss How We Made ‘NieR:Automata’\n\nThis article was assisted by AI."
+    "text": "This is a standard procedure."
   },
   {
-    "objectID": "decisions/20231027-drawing-concept-to-blockout.html",
-    "href": "decisions/20231027-drawing-concept-to-blockout.html",
-    "title": "Proposed: Drawing Concept to Blockout",
+    "objectID": "decisions/20230131-default-test-plan.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230131-default-test-plan.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Accepted: Default test plan for testing V-Sekai engine upgrades.",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai, fire\nTags: V-Sekai\n\n\n\n\nThe goal is to add more finished vrms to V-Sekai.\n\n\n\nThe task at hand is to create some concept art for an existing VRoid character model.\n\n\n\nHere’s the proposed strategy:\n\nStart with grayscale outlines to focus on shapes rather than color.\nUse a off-white background, an outline color, a shadow color and a solid color.\nFocus on the overall shapes and silhouette first before adding details.\n\n\n\n\nThis process will help nail down the overall look and feel before getting distracted by details and color. Starting with outlines and simple shapes will make it easier to iterate quickly.\n\n\n\nThe downside could be that focusing too much on the overall shape might lead to neglecting the finer details which are also important in character design. Also, this approach may not work as effectively for complex designs.\n\n\n\nAn alternative approach could have been to start with detailed sketches instead of broad shapes. This would allow for more detail early on but could potentially slow down the iteration process.\n\n\n\nThis method might not be suitable if the character design is already well established and does not require significant changes to its overall shape and structure.\n\n\n\nYes, this is a core part of our design process and is done by us.\n\n\n\nFor more information, you can visit the following links:\n\nV-Sekai\nAI assists this article."
+    "text": "We need to test our work."
   },
   {
-    "objectID": "decisions/20231027-drawing-concept-to-blockout.html#metadata",
-    "href": "decisions/20231027-drawing-concept-to-blockout.html#metadata",
-    "title": "Proposed: Drawing Concept to Blockout",
+    "objectID": "decisions/20230131-default-test-plan.html#references",
+    "href": "decisions/20230131-default-test-plan.html#references",
+    "title": "Accepted: Default test plan for testing V-Sekai engine upgrades.",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai, fire\nTags: V-Sekai"
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20231027-drawing-concept-to-blockout.html#the-backdrop",
-    "href": "decisions/20231027-drawing-concept-to-blockout.html#the-backdrop",
-    "title": "Proposed: Drawing Concept to Blockout",
+    "objectID": "decisions/20230131-default-test-plan.html#license-of-the-contribution",
+    "href": "decisions/20230131-default-test-plan.html#license-of-the-contribution",
+    "title": "Accepted: Default test plan for testing V-Sekai engine upgrades.",
     "section": "",
-    "text": "The goal is to add more finished vrms to V-Sekai."
+    "text": "MIT License\n\nCopyright (c) 2019-2022 K. S. Ernest (iFire) Lee (fire)\nCopyright (c) 2022 V-Sekai Contributors\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
   },
   {
-    "objectID": "decisions/20231027-drawing-concept-to-blockout.html#the-challenge",
-    "href": "decisions/20231027-drawing-concept-to-blockout.html#the-challenge",
-    "title": "Proposed: Drawing Concept to Blockout",
+    "objectID": "decisions/20230507-avatar-publishing-workflow-portability.html",
+    "href": "decisions/20230507-avatar-publishing-workflow-portability.html",
+    "title": "Draft: Describe a avatar publishing workflow for portability",
     "section": "",
-    "text": "The task at hand is to create some concept art for an existing VRoid character model."
+    "text": "Status: draft \nDeciders: V-Sekai, fire\nTags: V-Sekai, ChatGPT-4, Avatar Publishing, Workflow, Portability, VRM Format, Silent’s Shader, Platform Compatibility, Sketchfab, Booth.pm\n\n\n\n\nWe want to create a workflow for publishing avatars in a portable format that can be easily used across different platforms. The goal is to streamline the process of converting and exporting avatars while maintaining compatibility with various platforms.\n\n\n\nThe proposed solution involves using the VRM portable avatar format, Silent’s shader, and platform-specific package bundles to create a seamless workflow for avatar publishing.\n\n\n\n\nImport avatar in VRM0 portable avatar format.\nInstall Silent’s shader 1.11.\nConvert VRM to compatible platform’s internal format.\n\nAvoid “Combine Mesh” option.\nThe Cutout Rendering Mode matches VRM’s usual transparency usage.\nUNRESOLVED: VRM Colliders cause greatly increased count of simulated physics objects\n\n\nTry switching to inside bounds instead of bone as spheres\n\nSwap the mtoon material for Silent’s shader’s crosstone material. Fire doesn’t use the light-ramp shader.\nMany bones need to be the first child for IK to work.\nFire prefers solid colour backgrounds for avatar photos\nExport as a compatible platform package bundle.\nBundle VRM and compatible platform package bundle and publish on Sketchfab and/or Booth.pm.\nThe compatible platform should display the avatar as poor rated.\n\n\n\n\n\nStreamlined avatar publishing process.\nIncreased portability and compatibility with different platforms.\nEasier sharing and distribution of avatars.\n\n\n\n\n\nPotential loss of some features or quality during conversion.\nMay require additional work to ensure compatibility with all desired platforms.\n\n\n\n\nN/A\n\n\n\nNo, this enhancement aims to create a comprehensive workflow for avatar publishing, which cannot be achieved with just a few lines of script.\n\n\n\nYes, creating a standardized workflow for avatar publishing ensures consistency and compatibility across platforms, making it easier for users to share and distribute their avatars.\n\n\n\n\nV-Sekai: V-Sekai\nSilent Cel Shading Shader: SCSS\nSilent Cel Shading Shader v1.11: Silent Cel Shading Shader v1.11\nBooth.pm: Booth.pm\nSketchfab: Sketchfab\nVRM converter for compatible platform: VRM converter\n\nAutomatically installs Univrm: Univrm"
   },
   {
-    "objectID": "decisions/20231027-drawing-concept-to-blockout.html#the-strategy",
-    "href": "decisions/20231027-drawing-concept-to-blockout.html#the-strategy",
-    "title": "Proposed: Drawing Concept to Blockout",
+    "objectID": "decisions/20230507-avatar-publishing-workflow-portability.html#metadata",
+    "href": "decisions/20230507-avatar-publishing-workflow-portability.html#metadata",
+    "title": "Draft: Describe a avatar publishing workflow for portability",
     "section": "",
-    "text": "Here’s the proposed strategy:\n\nStart with grayscale outlines to focus on shapes rather than color.\nUse a off-white background, an outline color, a shadow color and a solid color.\nFocus on the overall shapes and silhouette first before adding details."
+    "text": "Status: draft \nDeciders: V-Sekai, fire\nTags: V-Sekai, ChatGPT-4, Avatar Publishing, Workflow, Portability, VRM Format, Silent’s Shader, Platform Compatibility, Sketchfab, Booth.pm"
   },
   {
-    "objectID": "decisions/20231027-drawing-concept-to-blockout.html#the-upside",
-    "href": "decisions/20231027-drawing-concept-to-blockout.html#the-upside",
-    "title": "Proposed: Drawing Concept to Blockout",
+    "objectID": "decisions/20230507-avatar-publishing-workflow-portability.html#context-and-problem-statement",
+    "href": "decisions/20230507-avatar-publishing-workflow-portability.html#context-and-problem-statement",
+    "title": "Draft: Describe a avatar publishing workflow for portability",
     "section": "",
-    "text": "This process will help nail down the overall look and feel before getting distracted by details and color. Starting with outlines and simple shapes will make it easier to iterate quickly."
+    "text": "We want to create a workflow for publishing avatars in a portable format that can be easily used across different platforms. The goal is to streamline the process of converting and exporting avatars while maintaining compatibility with various platforms."
   },
   {
-    "objectID": "decisions/20231027-drawing-concept-to-blockout.html#the-downside",
-    "href": "decisions/20231027-drawing-concept-to-blockout.html#the-downside",
-    "title": "Proposed: Drawing Concept to Blockout",
+    "objectID": "decisions/20230507-avatar-publishing-workflow-portability.html#proposed-solution",
+    "href": "decisions/20230507-avatar-publishing-workflow-portability.html#proposed-solution",
+    "title": "Draft: Describe a avatar publishing workflow for portability",
     "section": "",
-    "text": "The downside could be that focusing too much on the overall shape might lead to neglecting the finer details which are also important in character design. Also, this approach may not work as effectively for complex designs."
+    "text": "The proposed solution involves using the VRM portable avatar format, Silent’s shader, and platform-specific package bundles to create a seamless workflow for avatar publishing."
   },
   {
-    "objectID": "decisions/20231027-drawing-concept-to-blockout.html#the-road-not-taken",
-    "href": "decisions/20231027-drawing-concept-to-blockout.html#the-road-not-taken",
-    "title": "Proposed: Drawing Concept to Blockout",
+    "objectID": "decisions/20230507-avatar-publishing-workflow-portability.html#implementation",
+    "href": "decisions/20230507-avatar-publishing-workflow-portability.html#implementation",
+    "title": "Draft: Describe a avatar publishing workflow for portability",
     "section": "",
-    "text": "An alternative approach could have been to start with detailed sketches instead of broad shapes. This would allow for more detail early on but could potentially slow down the iteration process."
+    "text": "Import avatar in VRM0 portable avatar format.\nInstall Silent’s shader 1.11.\nConvert VRM to compatible platform’s internal format.\n\nAvoid “Combine Mesh” option.\nThe Cutout Rendering Mode matches VRM’s usual transparency usage.\nUNRESOLVED: VRM Colliders cause greatly increased count of simulated physics objects\n\n\nTry switching to inside bounds instead of bone as spheres\n\nSwap the mtoon material for Silent’s shader’s crosstone material. Fire doesn’t use the light-ramp shader.\nMany bones need to be the first child for IK to work.\nFire prefers solid colour backgrounds for avatar photos\nExport as a compatible platform package bundle.\nBundle VRM and compatible platform package bundle and publish on Sketchfab and/or Booth.pm.\nThe compatible platform should display the avatar as poor rated."
   },
   {
-    "objectID": "decisions/20231027-drawing-concept-to-blockout.html#the-infrequent-use-case",
-    "href": "decisions/20231027-drawing-concept-to-blockout.html#the-infrequent-use-case",
-    "title": "Proposed: Drawing Concept to Blockout",
+    "objectID": "decisions/20230507-avatar-publishing-workflow-portability.html#positive-consequences",
+    "href": "decisions/20230507-avatar-publishing-workflow-portability.html#positive-consequences",
+    "title": "Draft: Describe a avatar publishing workflow for portability",
     "section": "",
-    "text": "This method might not be suitable if the character design is already well established and does not require significant changes to its overall shape and structure."
+    "text": "Streamlined avatar publishing process.\nIncreased portability and compatibility with different platforms.\nEasier sharing and distribution of avatars."
   },
   {
-    "objectID": "decisions/20231027-drawing-concept-to-blockout.html#in-core-and-done-by-us",
-    "href": "decisions/20231027-drawing-concept-to-blockout.html#in-core-and-done-by-us",
-    "title": "Proposed: Drawing Concept to Blockout",
+    "objectID": "decisions/20230507-avatar-publishing-workflow-portability.html#negative-consequences",
+    "href": "decisions/20230507-avatar-publishing-workflow-portability.html#negative-consequences",
+    "title": "Draft: Describe a avatar publishing workflow for portability",
     "section": "",
-    "text": "Yes, this is a core part of our design process and is done by us."
+    "text": "Potential loss of some features or quality during conversion.\nMay require additional work to ensure compatibility with all desired platforms."
   },
   {
-    "objectID": "decisions/20231027-drawing-concept-to-blockout.html#further-reading",
-    "href": "decisions/20231027-drawing-concept-to-blockout.html#further-reading",
-    "title": "Proposed: Drawing Concept to Blockout",
+    "objectID": "decisions/20230507-avatar-publishing-workflow-portability.html#option-graveyard",
+    "href": "decisions/20230507-avatar-publishing-workflow-portability.html#option-graveyard",
+    "title": "Draft: Describe a avatar publishing workflow for portability",
     "section": "",
-    "text": "For more information, you can visit the following links:\n\nV-Sekai\nAI assists this article."
+    "text": "N/A"
   },
   {
-    "objectID": "decisions/20230719-pose-kusudama-constraints-in-vr.html",
-    "href": "decisions/20230719-pose-kusudama-constraints-in-vr.html",
-    "title": "Proposed: Enhancing the Many Bone IK Configuration",
+    "objectID": "decisions/20230507-avatar-publishing-workflow-portability.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230507-avatar-publishing-workflow-portability.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Draft: Describe a avatar publishing workflow for portability",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, VR, Game Development\n\n\n\n\nWe have identified a limitation in the V-Sekai platform where there are too many variables to pose the kusudama constraints on the desktop. We propose to overcome this limitation by introducing a VR mode.\n\n\n\nOur solution involves creating a VR mode specifically for posing Many Bone IK kusudama constraints. The steps for implementation are as follows:\n\nTake an off the shelf VR controller.\nTake an off the shelf multiplayer functionality.\nDevelop a tool selection ui. Collaborate with guillefix.\nAdjust the kusudama constraint attributes to match posing.\nSave attributes.\n\n\n\nImagine you have a ball. There are two ways you can move it:\n\nTwist: Like spinning a globe on its stand.\nSwing: Like moving your finger from one spot to another on the ball.\n\nThink of a Kusudama (a type of origami that forms a sphere) as an example for the swing movement. The pieces of paper move just like your finger would on the ball.\n\n\n\n\n\nInvestigate Saracen’s VR networking prototype.\nRebuild character posing without tracking the physical sensors\nApply Many Bone IK tracking\nRotation swing (10x Vector4)\nRotation twist (From and range)\nAdjust for quality\nComplete configuration\n\nAssigning physical sensors to IK points is non-goal.\n\n\n\n\nDesktop Mode Enhancement: Initially, we considered enhancing the desktop mode to handle the kusudama constraints better. However, this option was discarded due to the inherent limitations of the desktop interface for such complex interactions.\nUse of External Tools: Another option was to use external tools or plugins specifically designed for handling Many Bone IK kusudama constraints. This option was rejected because it would require users to learn and manage additional software, which could lead to a fragmented user experience.\nSimplified Kusudama Constraints: We also thought about simplifying the kusudama constraints to make them more manageable on the desktop. But this option was discarded as it would limit the capabilities and flexibility that our platform currently offers.\nAutomated Posing: An automated system for posing the kusudama constraints was also considered. However, this option was rejected because it would take away control from the users, potentially leading to less satisfactory results.\nTutorials and Guides: Providing extensive tutorials and guides to help users navigate the complexity of posing kusudama constraints on the desktop was another option. This was discarded because it doesn’t address the core issue - the difficulty of managing these constraints on a desktop interface.\n\n\n\n\n\nIncreased complexity in game development.\nPotential need for more resources (time, manpower, etc.) for implementation and testing.\n\n\n\n\nThis section is reserved for options considered but rejected.\n\n\n\nPosing the avatar is the first interaction a user has when entering our virtual world, V-Sekai. This underlines the necessity of investing in this enhancement to ensure a seamless and engaging user experience right from their first interaction with our platform.\n\n\n\nPose quality is crucial to us. As the creators of V-Sekai, we have an unparalleled understanding of our platform’s limitations and potential improvements. This insight puts us in a unique position to enhance the pose quality in a way that aligns with our users’ needs and expectations. Therefore, it is essential that we undertake this enhancement.\n\n\n\n\nV-Sekai"
+    "text": "No, this enhancement aims to create a comprehensive workflow for avatar publishing, which cannot be achieved with just a few lines of script."
   },
   {
-    "objectID": "decisions/20230719-pose-kusudama-constraints-in-vr.html#metadata",
-    "href": "decisions/20230719-pose-kusudama-constraints-in-vr.html#metadata",
-    "title": "Proposed: Enhancing the Many Bone IK Configuration",
+    "objectID": "decisions/20230507-avatar-publishing-workflow-portability.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230507-avatar-publishing-workflow-portability.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Draft: Describe a avatar publishing workflow for portability",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, VR, Game Development"
+    "text": "Yes, creating a standardized workflow for avatar publishing ensures consistency and compatibility across platforms, making it easier for users to share and distribute their avatars."
   },
   {
-    "objectID": "decisions/20230719-pose-kusudama-constraints-in-vr.html#context-and-problem-statement",
-    "href": "decisions/20230719-pose-kusudama-constraints-in-vr.html#context-and-problem-statement",
-    "title": "Proposed: Enhancing the Many Bone IK Configuration",
+    "objectID": "decisions/20230507-avatar-publishing-workflow-portability.html#references",
+    "href": "decisions/20230507-avatar-publishing-workflow-portability.html#references",
+    "title": "Draft: Describe a avatar publishing workflow for portability",
     "section": "",
-    "text": "We have identified a limitation in the V-Sekai platform where there are too many variables to pose the kusudama constraints on the desktop. We propose to overcome this limitation by introducing a VR mode."
+    "text": "V-Sekai: V-Sekai\nSilent Cel Shading Shader: SCSS\nSilent Cel Shading Shader v1.11: Silent Cel Shading Shader v1.11\nBooth.pm: Booth.pm\nSketchfab: Sketchfab\nVRM converter for compatible platform: VRM converter\n\nAutomatically installs Univrm: Univrm"
   },
   {
-    "objectID": "decisions/20230719-pose-kusudama-constraints-in-vr.html#proposed-solution",
-    "href": "decisions/20230719-pose-kusudama-constraints-in-vr.html#proposed-solution",
-    "title": "Proposed: Enhancing the Many Bone IK Configuration",
+    "objectID": "decisions/attachments/virtual_pets/LICENSE.html",
+    "href": "decisions/attachments/virtual_pets/LICENSE.html",
+    "title": "V-Sekai - Manuals",
     "section": "",
-    "text": "Our solution involves creating a VR mode specifically for posing Many Bone IK kusudama constraints. The steps for implementation are as follows:\n\nTake an off the shelf VR controller.\nTake an off the shelf multiplayer functionality.\nDevelop a tool selection ui. Collaborate with guillefix.\nAdjust the kusudama constraint attributes to match posing.\nSave attributes.\n\n\n\nImagine you have a ball. There are two ways you can move it:\n\nTwist: Like spinning a globe on its stand.\nSwing: Like moving your finger from one spot to another on the ball.\n\nThink of a Kusudama (a type of origami that forms a sphere) as an example for the swing movement. The pieces of paper move just like your finger would on the ball."
+    "text": "CC0 1.0 Universal\nStatement of Purpose\nThe laws of most jurisdictions throughout the world automatically confer exclusive Copyright and Related Rights (defined below) upon the creator and subsequent owner(s) (each and all, an “owner”) of an original work of authorship and/or a database (each, a “Work”).\nCertain owners wish to permanently relinquish those rights to a Work for the purpose of contributing to a commons of creative, cultural and scientific works (“Commons”) that the public can reliably and without fear of later claims of infringement build upon, modify, incorporate in other works, reuse and redistribute as freely as possible in any form whatsoever and for any purposes, including without limitation commercial purposes. These owners may contribute to the Commons to promote the ideal of a free culture and the further production of creative, cultural and scientific works, or to gain reputation or greater distribution for their Work in part through the use and efforts of others.\nFor these and/or other purposes and motivations, and without any expectation of additional consideration or compensation, the person associating CC0 with a Work (the “Affirmer”), to the extent that he or she is an owner of Copyright and Related Rights in the Work, voluntarily elects to apply CC0 to the Work and publicly distribute the Work under its terms, with knowledge of his or her Copyright and Related Rights in the Work and the meaning and intended legal effect of CC0 on those rights.\n\nCopyright and Related Rights. A Work made available under CC0 may be protected by copyright and related or neighboring rights (“Copyright and Related Rights”). Copyright and Related Rights include, but are not limited to, the following:\n\n\nthe right to reproduce, adapt, distribute, perform, display, communicate, and translate a Work;\nmoral rights retained by the original author(s) and/or performer(s);\npublicity and privacy rights pertaining to a person’s image or likeness depicted in a Work;\nrights protecting against unfair competition in regards to a Work, subject to the limitations in paragraph 4(a), below;\nrights protecting the extraction, dissemination, use and reuse of data in a Work;\ndatabase rights (such as those arising under Directive 96/9/EC of the European Parliament and of the Council of 11 March 1996 on the legal protection of databases, and under any national implementation thereof, including any amended or successor version of such directive); and\nother similar, equivalent or corresponding rights throughout the world based on applicable law or treaty, and any national implementations thereof.\n\n\nWaiver. To the greatest extent permitted by, but not in contravention of, applicable law, Affirmer hereby overtly, fully, permanently, irrevocably and unconditionally waives, abandons, and surrenders all of Affirmer’s Copyright and Related Rights and associated claims and causes of action, whether now known or unknown (including existing as well as future claims and causes of action), in the Work (i) in all territories worldwide, (ii) for the maximum duration provided by applicable law or treaty (including future time extensions), (iii) in any current or future medium and for any number of copies, and (iv) for any purpose whatsoever, including without limitation commercial, advertising or promotional purposes (the “Waiver”). Affirmer makes the Waiver for the benefit of each member of the public at large and to the detriment of Affirmer’s heirs and successors, fully intending that such Waiver shall not be subject to revocation, rescission, cancellation, termination, or any other legal or equitable action to disrupt the quiet enjoyment of the Work by the public as contemplated by Affirmer’s express Statement of Purpose.\nPublic License Fallback. Should any part of the Waiver for any reason be judged legally invalid or ineffective under applicable law, then the Waiver shall be preserved to the maximum extent permitted taking into account Affirmer’s express Statement of Purpose. In addition, to the extent the Waiver is so judged Affirmer hereby grants to each affected person a royalty-free, non transferable, non sublicensable, non exclusive, irrevocable and unconditional license to exercise Affirmer’s Copyright and Related Rights in the Work (i) in all territories worldwide, (ii) for the maximum duration provided by applicable law or treaty (including future time extensions), (iii) in any current or future medium and for any number of copies, and (iv) for any purpose whatsoever, including without limitation commercial, advertising or promotional purposes (the “License”). The License shall be deemed effective as of the date CC0 was applied by Affirmer to the Work. Should any part of the License for any reason be judged legally invalid or ineffective under applicable law, such partial invalidity or ineffectiveness shall not invalidate the remainder of the License, and in such case Affirmer hereby affirms that he or she will not (i) exercise any of his or her remaining Copyright and Related Rights in the Work or (ii) assert any associated claims and causes of action with respect to the Work, in either case contrary to Affirmer’s express Statement of Purpose.\nLimitations and Disclaimers.\n\n\nNo trademark or patent rights held by Affirmer are waived, abandoned, surrendered, licensed or otherwise affected by this document.\nAffirmer offers the Work as-is and makes no representations or warranties of any kind concerning the Work, express, implied, statutory or otherwise, including without limitation warranties of title, merchantability, fitness for a particular purpose, non infringement, or the absence of latent or other defects, accuracy, or the present or absence of errors, whether or not discoverable, all to the greatest extent permissible under applicable law.\nAffirmer disclaims responsibility for clearing rights of other persons that may apply to the Work or any use thereof, including without limitation any person’s Copyright and Related Rights in the Work. Further, Affirmer disclaims responsibility for obtaining any necessary consents, permissions or other rights required for any use of the Work.\nAffirmer understands and acknowledges that Creative Commons is not a party to this document and has no duty or obligation with respect to this CC0 or use of the Work.\n\nFor more information, please see http://creativecommons.org/publicdomain/zero/1.0/"
   },
   {
-    "objectID": "decisions/20230719-pose-kusudama-constraints-in-vr.html#implementation",
-    "href": "decisions/20230719-pose-kusudama-constraints-in-vr.html#implementation",
-    "title": "Proposed: Enhancing the Many Bone IK Configuration",
+    "objectID": "decisions/attachments/pitch_general_02.html",
+    "href": "decisions/attachments/pitch_general_02.html",
+    "title": "V-Sekai’s main goals and features:",
     "section": "",
-    "text": "Investigate Saracen’s VR networking prototype.\nRebuild character posing without tracking the physical sensors\nApply Many Bone IK tracking\nRotation swing (10x Vector4)\nRotation twist (From and range)\nAdjust for quality\nComplete configuration\n\nAssigning physical sensors to IK points is non-goal."
+    "text": "V-Sekai’s main goals and features:\nV-Sekai wants to make virtual collaboration easy for everyone by focusing on bringing people together and enabling creation.\nWith open voice and text chat, you can hang out and talk to others freely. Customize your VRM 1.0 avatar to represent yourself and feel like you’re among friends no matter where they are.\nOur simple spaces provide locations for any activity. You can discuss ideas in a casual lounge, brainstorm on interactive whiteboards, design together in a 3D workshop, or build fully customized environments.\nIn V-Sekai, you can express yourself by sharing and creating things together. You can doodle and prototype on the digital whiteboard or with 3D modeling tools. Bring in images, videos, web content, anything - then combine them into new inventions. You can create alone or with friends to keep improving each other’s work.\nWe know that new platforms need good tutorials. That’s why we make collaborating in V-Sekai simple, with friendly walkthroughs and a helpful community. We built this platform for you, and we listen and update regularly based on what the community wants to create.\nAt V-Sekai, we believe in open access. We are developing ways for outside creators to build new tools, spaces, and features that expand V-Sekai’s potential. We follow our values of empowering users, spreading joy, and helping shape this open world!\nV-Sekai provides space, freedom, and fertile ground for relationships to flourish. The essentials for hanging out with friends in a virtual world are simple enough for everyone yet open for spontaneous interaction and creating together. We build the foundation, and you provide the imagination. Join us in building the future of social VR!\nTo summarize, V-Sekai’s main objectives are:\n• Enabling open communication through voice/text chat and VRM 1.0 avatars\n• Providing simple, flexible spaces for any activity or collaboration\n• Sharing media, tools, and abilities to create together\n• Educating and supporting the community\n• Providing open access for user and creator contributions\n• Fostering human relationships and co-creation in virtual reality\n• Keeping the platform accessible to all while being open-ended enough for creativity\n• Building a foundation for connection focused on user experience\n• Developing an ecosystem where people power imagination and potential."
   },
   {
-    "objectID": "decisions/20230719-pose-kusudama-constraints-in-vr.html#option-graveyard",
-    "href": "decisions/20230719-pose-kusudama-constraints-in-vr.html#option-graveyard",
-    "title": "Proposed: Enhancing the Many Bone IK Configuration",
+    "objectID": "decisions/20220202-gltf-extensions-for-interoperability.html",
+    "href": "decisions/20220202-gltf-extensions-for-interoperability.html",
+    "title": "Accepted: Interoperability between platforms using gltf extensions",
     "section": "",
-    "text": "Desktop Mode Enhancement: Initially, we considered enhancing the desktop mode to handle the kusudama constraints better. However, this option was discarded due to the inherent limitations of the desktop interface for such complex interactions.\nUse of External Tools: Another option was to use external tools or plugins specifically designed for handling Many Bone IK kusudama constraints. This option was rejected because it would require users to learn and manage additional software, which could lead to a fragmented user experience.\nSimplified Kusudama Constraints: We also thought about simplifying the kusudama constraints to make them more manageable on the desktop. But this option was discarded as it would limit the capabilities and flexibility that our platform currently offers.\nAutomated Posing: An automated system for posing the kusudama constraints was also considered. However, this option was rejected because it would take away control from the users, potentially leading to less satisfactory results.\nTutorials and Guides: Providing extensive tutorials and guides to help users navigate the complexity of posing kusudama constraints on the desktop was another option. This was discarded because it doesn’t address the core issue - the difficulty of managing these constraints on a desktop interface."
+    "text": "Status: accepted\nDeciders: V-Sekai,fire,lyuma,humbletim,codefloof,\nTags: V-Sekai,\n\n\n\nBuild Gltf extensions. Why build incomplete Gltf extensions with limited usefulness without the complete package? We should be making for creators, not ourselves.\n\n\n\nhumbletim, codefloof, iFire and lyuma debated the meaningfulness of building Gltf extensions.\niFire constructed an argument we are making a Gltf container for the metaverse. A metaverse container where each part is separated because of limited engineering bandwidth. We brought up the point Gltf isn’t unknown and is unknown.\nLyuma can’t entirely agree that Gltf extensions are “separated.” Gltf extensions are independent extensions that are good from an engineering perspective.\nLyuma reaffirmed his suspicions that OMI standards are not so valuable in isolation. Humbletim raised valid concerns that the Unity work had not progressed, and Mozilla Hubs had not merged the OMI audio emitter code. We may need Unity platforms and Mozilla Hubs to bootstrap the ecosystem, but tools like Gltf transform could sidestep it.\niFire also constructed a strawman of how operating inside a platform is seamless, and transferring between platforms is like pulling teeth. Still, a strawman isn’t something that helped facilitate the discussion so Lyuma may have misunderstood that part. iFire described the unity package vs others. Lyuma agrees that this is valid; other formats could be deemed “interoperable,” more expressive than Gltf.\nIn Lyuma’s mind, it’s a fair X point that already exists. So why work on Y? Why does Gltf 3d format if we have Fbx 3d format etc.?\nLyuma doesn’t think we need to assume that there must be only one standard.\nWe’re trying to see if we can do better by working together than taking some existing closed format and using it verbatim.\nOMI work is valid even if a unity package standard exists. We don’t need to be the only standard.\niFire didn’t exhaust all the details of the point, but we can make a Gltf transform for as many standards we can catalog.\n\n\n\nWe will generate github actions templates using the same jsonnet we use for GoCD.\n\n\n\n\nInteroperating between platforms.\n\n\n\n\n\nEasy to ignore users.\n\n\n\n\n\nOption: Keep the status quo, which is having separate platforms.\nRejection Reason: We want interoperability at OMI.\n\n\n\n\nIt is not only a few lines of code.\n\n\n\nWe want to maintain it to encourage developers and as the publisher of the platform it is our responsibility.\n\n\n\n\nhttps://omigroup.org/\n\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230719-pose-kusudama-constraints-in-vr.html#negative-consequences",
-    "href": "decisions/20230719-pose-kusudama-constraints-in-vr.html#negative-consequences",
-    "title": "Proposed: Enhancing the Many Bone IK Configuration",
+    "objectID": "decisions/20220202-gltf-extensions-for-interoperability.html#context-and-problem-statement",
+    "href": "decisions/20220202-gltf-extensions-for-interoperability.html#context-and-problem-statement",
+    "title": "Accepted: Interoperability between platforms using gltf extensions",
     "section": "",
-    "text": "Increased complexity in game development.\nPotential need for more resources (time, manpower, etc.) for implementation and testing."
+    "text": "Build Gltf extensions. Why build incomplete Gltf extensions with limited usefulness without the complete package? We should be making for creators, not ourselves."
   },
   {
-    "objectID": "decisions/20230719-pose-kusudama-constraints-in-vr.html#option-graveyard-1",
-    "href": "decisions/20230719-pose-kusudama-constraints-in-vr.html#option-graveyard-1",
-    "title": "Proposed: Enhancing the Many Bone IK Configuration",
+    "objectID": "decisions/20220202-gltf-extensions-for-interoperability.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20220202-gltf-extensions-for-interoperability.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Accepted: Interoperability between platforms using gltf extensions",
     "section": "",
-    "text": "This section is reserved for options considered but rejected."
+    "text": "humbletim, codefloof, iFire and lyuma debated the meaningfulness of building Gltf extensions.\niFire constructed an argument we are making a Gltf container for the metaverse. A metaverse container where each part is separated because of limited engineering bandwidth. We brought up the point Gltf isn’t unknown and is unknown.\nLyuma can’t entirely agree that Gltf extensions are “separated.” Gltf extensions are independent extensions that are good from an engineering perspective.\nLyuma reaffirmed his suspicions that OMI standards are not so valuable in isolation. Humbletim raised valid concerns that the Unity work had not progressed, and Mozilla Hubs had not merged the OMI audio emitter code. We may need Unity platforms and Mozilla Hubs to bootstrap the ecosystem, but tools like Gltf transform could sidestep it.\niFire also constructed a strawman of how operating inside a platform is seamless, and transferring between platforms is like pulling teeth. Still, a strawman isn’t something that helped facilitate the discussion so Lyuma may have misunderstood that part. iFire described the unity package vs others. Lyuma agrees that this is valid; other formats could be deemed “interoperable,” more expressive than Gltf.\nIn Lyuma’s mind, it’s a fair X point that already exists. So why work on Y? Why does Gltf 3d format if we have Fbx 3d format etc.?\nLyuma doesn’t think we need to assume that there must be only one standard.\nWe’re trying to see if we can do better by working together than taking some existing closed format and using it verbatim.\nOMI work is valid even if a unity package standard exists. We don’t need to be the only standard.\niFire didn’t exhaust all the details of the point, but we can make a Gltf transform for as many standards we can catalog."
   },
   {
-    "objectID": "decisions/20230719-pose-kusudama-constraints-in-vr.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230719-pose-kusudama-constraints-in-vr.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Enhancing the Many Bone IK Configuration",
+    "objectID": "decisions/20220202-gltf-extensions-for-interoperability.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20220202-gltf-extensions-for-interoperability.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Accepted: Interoperability between platforms using gltf extensions",
     "section": "",
-    "text": "Posing the avatar is the first interaction a user has when entering our virtual world, V-Sekai. This underlines the necessity of investing in this enhancement to ensure a seamless and engaging user experience right from their first interaction with our platform."
+    "text": "We will generate github actions templates using the same jsonnet we use for GoCD."
   },
   {
-    "objectID": "decisions/20230719-pose-kusudama-constraints-in-vr.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230719-pose-kusudama-constraints-in-vr.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Enhancing the Many Bone IK Configuration",
+    "objectID": "decisions/20220202-gltf-extensions-for-interoperability.html#positive-consequences",
+    "href": "decisions/20220202-gltf-extensions-for-interoperability.html#positive-consequences",
+    "title": "Accepted: Interoperability between platforms using gltf extensions",
     "section": "",
-    "text": "Pose quality is crucial to us. As the creators of V-Sekai, we have an unparalleled understanding of our platform’s limitations and potential improvements. This insight puts us in a unique position to enhance the pose quality in a way that aligns with our users’ needs and expectations. Therefore, it is essential that we undertake this enhancement."
+    "text": "Interoperating between platforms."
   },
   {
-    "objectID": "decisions/20230719-pose-kusudama-constraints-in-vr.html#references",
-    "href": "decisions/20230719-pose-kusudama-constraints-in-vr.html#references",
-    "title": "Proposed: Enhancing the Many Bone IK Configuration",
+    "objectID": "decisions/20220202-gltf-extensions-for-interoperability.html#negative-consequences",
+    "href": "decisions/20220202-gltf-extensions-for-interoperability.html#negative-consequences",
+    "title": "Accepted: Interoperability between platforms using gltf extensions",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Easy to ignore users."
   },
   {
-    "objectID": "decisions/20240424-reset-steamvr-controllers.html",
-    "href": "decisions/20240424-reset-steamvr-controllers.html",
-    "title": "Accepted: Prioritizing Valve Controllers Over Meta Quest 3 Controllers",
+    "objectID": "decisions/20220202-gltf-extensions-for-interoperability.html#option-graveyard",
+    "href": "decisions/20220202-gltf-extensions-for-interoperability.html#option-graveyard",
+    "title": "Accepted: Interoperability between platforms using gltf extensions",
     "section": "",
-    "text": "We are considering the use of Quest 3 and Lighthouse tracked Valve Index controllers for our project when using playspace calibration.\n\n\n\nThe issue we face is that when a Meta Quest 3 is used, it takes over the controller priority. So we’re unable to open the steamvr menu.\n\n\n\nTo address this problem, we propose turning the SteamVR Index controller on and off. This action will prioritize the Valve controller over the Meta controller.\n\n\n\n\nEnsures optimal functionality of the Valve controller.\nPrevents interference from the Meta controller.\n\n\n\n\n\nMay need to be adjusted for different hardware configurations.\n\n\n\n\nWe could have chosen to let the Meta controller take priority, but this would not have been ideal for our specific needs.\n\n\n\nThis solution may not be necessary for users who do not use a Meta Quest 3.\n\n\n\nThis proposal has been developed and will be implemented by the V-Sekai development team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - The GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis proposal was assisted by AI assistant, Aria."
+    "text": "Option: Keep the status quo, which is having separate platforms.\nRejection Reason: We want interoperability at OMI."
   },
   {
-    "objectID": "decisions/20240424-reset-steamvr-controllers.html#the-context",
-    "href": "decisions/20240424-reset-steamvr-controllers.html#the-context",
-    "title": "Accepted: Prioritizing Valve Controllers Over Meta Quest 3 Controllers",
+    "objectID": "decisions/20220202-gltf-extensions-for-interoperability.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20220202-gltf-extensions-for-interoperability.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Accepted: Interoperability between platforms using gltf extensions",
     "section": "",
-    "text": "We are considering the use of Quest 3 and Lighthouse tracked Valve Index controllers for our project when using playspace calibration."
+    "text": "It is not only a few lines of code."
   },
   {
-    "objectID": "decisions/20240424-reset-steamvr-controllers.html#the-problem-statement",
-    "href": "decisions/20240424-reset-steamvr-controllers.html#the-problem-statement",
-    "title": "Accepted: Prioritizing Valve Controllers Over Meta Quest 3 Controllers",
+    "objectID": "decisions/20220202-gltf-extensions-for-interoperability.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20220202-gltf-extensions-for-interoperability.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Accepted: Interoperability between platforms using gltf extensions",
     "section": "",
-    "text": "The issue we face is that when a Meta Quest 3 is used, it takes over the controller priority. So we’re unable to open the steamvr menu."
+    "text": "We want to maintain it to encourage developers and as the publisher of the platform it is our responsibility."
   },
   {
-    "objectID": "decisions/20240424-reset-steamvr-controllers.html#solution-proposal",
-    "href": "decisions/20240424-reset-steamvr-controllers.html#solution-proposal",
-    "title": "Accepted: Prioritizing Valve Controllers Over Meta Quest 3 Controllers",
+    "objectID": "decisions/20220202-gltf-extensions-for-interoperability.html#references",
+    "href": "decisions/20220202-gltf-extensions-for-interoperability.html#references",
+    "title": "Accepted: Interoperability between platforms using gltf extensions",
     "section": "",
-    "text": "To address this problem, we propose turning the SteamVR Index controller on and off. This action will prioritize the Valve controller over the Meta controller."
+    "text": "https://omigroup.org/"
   },
   {
-    "objectID": "decisions/20240424-reset-steamvr-controllers.html#the-benefits",
-    "href": "decisions/20240424-reset-steamvr-controllers.html#the-benefits",
-    "title": "Accepted: Prioritizing Valve Controllers Over Meta Quest 3 Controllers",
+    "objectID": "decisions/20220202-gltf-extensions-for-interoperability.html#derivative-license",
+    "href": "decisions/20220202-gltf-extensions-for-interoperability.html#derivative-license",
+    "title": "Accepted: Interoperability between platforms using gltf extensions",
     "section": "",
-    "text": "Ensures optimal functionality of the Valve controller.\nPrevents interference from the Meta controller."
+    "text": "Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240424-reset-steamvr-controllers.html#the-downsides",
-    "href": "decisions/20240424-reset-steamvr-controllers.html#the-downsides",
-    "title": "Accepted: Prioritizing Valve Controllers Over Meta Quest 3 Controllers",
+    "objectID": "decisions/20230521-audio-jitter-buffer-voip.html",
+    "href": "decisions/20230521-audio-jitter-buffer-voip.html",
+    "title": "Proposed: Improving Jitter-Buffer Implementation for Voice Chat in V-Sekai Projects",
     "section": "",
-    "text": "May need to be adjusted for different hardware configurations."
+    "text": "Status: proposed\nDeciders: V-Sekai, lyuma, Dreadpon,\nTags: V-Sekai, GPT-4, jitter-buffer, voice-chat, godot-speech, audio-quality, adaptive-jitter-buffer, Speex\n\n\n\n\nDreadpon is working on a voice chat solution inside Godot 3.5.2 and found the jitter-buffer implementation in godot-speech to be rudimentary. They are looking for an ideal jitter-buffer implementation that can handle both slowing down and speeding up played audio.\n\n\n\nUse the adaptive jitter buffer from the Speex source code as a starting point, with modifications to address its limitations:\n\nCapture packets as they are being dropped from the jitter buffer.\nEnsure all captured packets are played.\nImplement a playback buffer to speed up the audio when necessary.\n\n\n\n\n\nIntegrate the adaptive jitter buffer from the Speex source code into the godot-speech project.\nModify the jitter buffer to capture dropped packets and store them in a separate buffer.\nImplement a playback buffer that accelerates audio playback when more audio packets are available.\nTest the new implementation to ensure it handles jitter compensation effectively.\n\n\n\n\n\nImproved jitter compensation in the voice chat solution.\nBetter handling of packet drops and audio acceleration.\nEnhanced overall audio quality in the voice chat system.\n\n\n\n\n\nAdditional complexity in the godot-speech codebase.\nPotential performance impact due to the added buffering mechanism.\n\n\n\n\n\nContinue using the current rudimentary jitter-buffer implementation in godot-speech.\n\n\n\n\nNo, this enhancement is essential for a high-quality voice chat solution and cannot be easily worked around with a few lines of script.\n\n\n\nYes, improving the jitter-buffer implementation is crucial for providing a reliable and high-quality voice chat experience in V-Sekai projects.\n\n\n\n\nV-Sekai\ngodot-speech\nSpeex"
   },
   {
-    "objectID": "decisions/20240424-reset-steamvr-controllers.html#the-road-not-taken",
-    "href": "decisions/20240424-reset-steamvr-controllers.html#the-road-not-taken",
-    "title": "Accepted: Prioritizing Valve Controllers Over Meta Quest 3 Controllers",
+    "objectID": "decisions/20230521-audio-jitter-buffer-voip.html#metadata",
+    "href": "decisions/20230521-audio-jitter-buffer-voip.html#metadata",
+    "title": "Proposed: Improving Jitter-Buffer Implementation for Voice Chat in V-Sekai Projects",
     "section": "",
-    "text": "We could have chosen to let the Meta controller take priority, but this would not have been ideal for our specific needs."
+    "text": "Status: proposed\nDeciders: V-Sekai, lyuma, Dreadpon,\nTags: V-Sekai, GPT-4, jitter-buffer, voice-chat, godot-speech, audio-quality, adaptive-jitter-buffer, Speex"
   },
   {
-    "objectID": "decisions/20240424-reset-steamvr-controllers.html#the-infrequent-use-case",
-    "href": "decisions/20240424-reset-steamvr-controllers.html#the-infrequent-use-case",
-    "title": "Accepted: Prioritizing Valve Controllers Over Meta Quest 3 Controllers",
+    "objectID": "decisions/20230521-audio-jitter-buffer-voip.html#context-and-problem-statement",
+    "href": "decisions/20230521-audio-jitter-buffer-voip.html#context-and-problem-statement",
+    "title": "Proposed: Improving Jitter-Buffer Implementation for Voice Chat in V-Sekai Projects",
     "section": "",
-    "text": "This solution may not be necessary for users who do not use a Meta Quest 3."
+    "text": "Dreadpon is working on a voice chat solution inside Godot 3.5.2 and found the jitter-buffer implementation in godot-speech to be rudimentary. They are looking for an ideal jitter-buffer implementation that can handle both slowing down and speeding up played audio."
   },
   {
-    "objectID": "decisions/20240424-reset-steamvr-controllers.html#in-core-and-done-by-us",
-    "href": "decisions/20240424-reset-steamvr-controllers.html#in-core-and-done-by-us",
-    "title": "Accepted: Prioritizing Valve Controllers Over Meta Quest 3 Controllers",
+    "objectID": "decisions/20230521-audio-jitter-buffer-voip.html#proposed-solution",
+    "href": "decisions/20230521-audio-jitter-buffer-voip.html#proposed-solution",
+    "title": "Proposed: Improving Jitter-Buffer Implementation for Voice Chat in V-Sekai Projects",
     "section": "",
-    "text": "This proposal has been developed and will be implemented by the V-Sekai development team."
+    "text": "Use the adaptive jitter buffer from the Speex source code as a starting point, with modifications to address its limitations:\n\nCapture packets as they are being dropped from the jitter buffer.\nEnsure all captured packets are played.\nImplement a playback buffer to speed up the audio when necessary."
   },
   {
-    "objectID": "decisions/20240424-reset-steamvr-controllers.html#status",
-    "href": "decisions/20240424-reset-steamvr-controllers.html#status",
-    "title": "Accepted: Prioritizing Valve Controllers Over Meta Quest 3 Controllers",
+    "objectID": "decisions/20230521-audio-jitter-buffer-voip.html#implementation",
+    "href": "decisions/20230521-audio-jitter-buffer-voip.html#implementation",
+    "title": "Proposed: Improving Jitter-Buffer Implementation for Voice Chat in V-Sekai Projects",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "Integrate the adaptive jitter buffer from the Speex source code into the godot-speech project.\nModify the jitter buffer to capture dropped packets and store them in a separate buffer.\nImplement a playback buffer that accelerates audio playback when more audio packets are available.\nTest the new implementation to ensure it handles jitter compensation effectively."
   },
   {
-    "objectID": "decisions/20240424-reset-steamvr-controllers.html#decision-makers",
-    "href": "decisions/20240424-reset-steamvr-controllers.html#decision-makers",
-    "title": "Accepted: Prioritizing Valve Controllers Over Meta Quest 3 Controllers",
+    "objectID": "decisions/20230521-audio-jitter-buffer-voip.html#positive-consequences",
+    "href": "decisions/20230521-audio-jitter-buffer-voip.html#positive-consequences",
+    "title": "Proposed: Improving Jitter-Buffer Implementation for Voice Chat in V-Sekai Projects",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "Improved jitter compensation in the voice chat solution.\nBetter handling of packet drops and audio acceleration.\nEnhanced overall audio quality in the voice chat system."
   },
   {
-    "objectID": "decisions/20240424-reset-steamvr-controllers.html#tags",
-    "href": "decisions/20240424-reset-steamvr-controllers.html#tags",
-    "title": "Accepted: Prioritizing Valve Controllers Over Meta Quest 3 Controllers",
+    "objectID": "decisions/20230521-audio-jitter-buffer-voip.html#negative-consequences",
+    "href": "decisions/20230521-audio-jitter-buffer-voip.html#negative-consequences",
+    "title": "Proposed: Improving Jitter-Buffer Implementation for Voice Chat in V-Sekai Projects",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Additional complexity in the godot-speech codebase.\nPotential performance impact due to the added buffering mechanism."
   },
   {
-    "objectID": "decisions/20240424-reset-steamvr-controllers.html#further-reading",
-    "href": "decisions/20240424-reset-steamvr-controllers.html#further-reading",
-    "title": "Accepted: Prioritizing Valve Controllers Over Meta Quest 3 Controllers",
+    "objectID": "decisions/20230521-audio-jitter-buffer-voip.html#option-graveyard",
+    "href": "decisions/20230521-audio-jitter-buffer-voip.html#option-graveyard",
+    "title": "Proposed: Improving Jitter-Buffer Implementation for Voice Chat in V-Sekai Projects",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - The GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis proposal was assisted by AI assistant, Aria."
+    "text": "Continue using the current rudimentary jitter-buffer implementation in godot-speech."
   },
   {
-    "objectID": "decisions/20230630-vsekai-goal-meeting.html",
-    "href": "decisions/20230630-vsekai-goal-meeting.html",
-    "title": "Accepted: V-Sekai Meeting - Friday, June 30, 2023",
+    "objectID": "decisions/20230521-audio-jitter-buffer-voip.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230521-audio-jitter-buffer-voip.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Improving Jitter-Buffer Implementation for Voice Chat in V-Sekai Projects",
     "section": "",
-    "text": "Original pad (90 day expiration): https://pad.sfconservancy.org/p/v-sekai-goals-meet-2023-06-30.md /timeslider#937\n\n\nMeeting goal: determine what we can feasibly build and what we can enable others to build.\n\n\n\n\nOptimally piggybacking on systems others have built / are maintaining.\nBuild things we would want to use\n\n\n\n\n\n\n\nScene loading support\nWorld hosting (network protocol)\nInstancing: Holepunching (users host?) and relay system and Multi-instance server system?\n\n\n\n\n\nAvatar support\nAvatar animation system\nVoIP (voice communication)\nIK synchronization and other player / avatar synchronization\nObject parenting support (chairs)\n\n\n\n\n\nInteractive elements\nGrabbable objects\nButtons\nPhysics\n\n\n\n\n\nDoodling (with a builtin script to save to a file)\nCameras (take a picture - screenshot?)\nMirrors + camera\nVideo player (static + playback of videos without a duration aka live) libvlc or ffmpeg\nLocal API (http OR jsonrpc OR local pipe OR OSC etc.) for Extending the Platform\n\nAllow users to write scripts and plugins for V-Sekai\nOr allow a local user to write custom GDScript into V-Sekai\nAPI to create an object.\nDetermine RPCs or functions to expose)\n\n\n\n\n\n\n\nNeeds API or scripting language.\n\n\n\n\n\nVRM import (avatars)\nGodot editor\nWorld creation\nUploading / sharing content items to an inventory.\n\n\n\n\n\nScreen sharing (OBS)\nModeling and 3D Creation (Blender)\n\n\n\n\n\nText chat\nCollaboration features / meeting spaces\n\nDoodling\n3D doodling/modeling tools sketch\nSaving and loading of content at runtime\n\nSupport for proprietary video hosting websites\n\n\n\n\n\nV-Sekai"
+    "text": "No, this enhancement is essential for a high-quality voice chat solution and cannot be easily worked around with a few lines of script."
   },
   {
-    "objectID": "decisions/20230630-vsekai-goal-meeting.html#context-and-problem-statement",
-    "href": "decisions/20230630-vsekai-goal-meeting.html#context-and-problem-statement",
-    "title": "Accepted: V-Sekai Meeting - Friday, June 30, 2023",
+    "objectID": "decisions/20230521-audio-jitter-buffer-voip.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230521-audio-jitter-buffer-voip.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Improving Jitter-Buffer Implementation for Voice Chat in V-Sekai Projects",
     "section": "",
-    "text": "Meeting goal: determine what we can feasibly build and what we can enable others to build."
+    "text": "Yes, improving the jitter-buffer implementation is crucial for providing a reliable and high-quality voice chat experience in V-Sekai projects."
   },
   {
-    "objectID": "decisions/20230630-vsekai-goal-meeting.html#principles",
-    "href": "decisions/20230630-vsekai-goal-meeting.html#principles",
-    "title": "Accepted: V-Sekai Meeting - Friday, June 30, 2023",
+    "objectID": "decisions/20230521-audio-jitter-buffer-voip.html#references",
+    "href": "decisions/20230521-audio-jitter-buffer-voip.html#references",
+    "title": "Proposed: Improving Jitter-Buffer Implementation for Voice Chat in V-Sekai Projects",
     "section": "",
-    "text": "Optimally piggybacking on systems others have built / are maintaining.\nBuild things we would want to use"
+    "text": "V-Sekai\ngodot-speech\nSpeex"
   },
   {
-    "objectID": "decisions/20230630-vsekai-goal-meeting.html#foundational-runtime-features-provided-by-the-platform",
-    "href": "decisions/20230630-vsekai-goal-meeting.html#foundational-runtime-features-provided-by-the-platform",
-    "title": "Accepted: V-Sekai Meeting - Friday, June 30, 2023",
+    "objectID": "decisions/20231020-llama-cpp-mistral-npc.html",
+    "href": "decisions/20231020-llama-cpp-mistral-npc.html",
+    "title": "Proposed: Llama CPP AI Model NPC",
     "section": "",
-    "text": "Scene loading support\nWorld hosting (network protocol)\nInstancing: Holepunching (users host?) and relay system and Multi-instance server system?\n\n\n\n\n\nAvatar support\nAvatar animation system\nVoIP (voice communication)\nIK synchronization and other player / avatar synchronization\nObject parenting support (chairs)\n\n\n\n\n\nInteractive elements\nGrabbable objects\nButtons\nPhysics\n\n\n\n\n\nDoodling (with a builtin script to save to a file)\nCameras (take a picture - screenshot?)\nMirrors + camera\nVideo player (static + playback of videos without a duration aka live) libvlc or ffmpeg\nLocal API (http OR jsonrpc OR local pipe OR OSC etc.) for Extending the Platform\n\nAllow users to write scripts and plugins for V-Sekai\nOr allow a local user to write custom GDScript into V-Sekai\nAPI to create an object.\nDetermine RPCs or functions to expose)"
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, AI, NPC, Godot 4\n\n\n\n\nIn the realm of game development, creating engaging and dynamic Non-Player Characters (NPCs) is a challenging task. With advancements in AI, there’s an opportunity to leverage these technologies to enhance NPC interactions.\n\n\n\nThe challenge lies in effectively using various AI models to create the “brain” of an AI NPC in Godot 4. This involves generating realistic and contextually appropriate dialogs for the NPCs.\n\n\n\nThe strategy involves using a local GPT4All model for generating AI-based NPC dialog. The script includes several exported variables that can be set in the Godot editor, such as npc_background_directions, sample_npc_question_prompt, and sample_npc_prompt_response. These variables are used to configure the behavior of the AI dialog generation.\nKey functions include:\n\ncall_model(prompt): Calls the local model with a given prompt.\nset_model(new_model_name : String): Sets the model name.\n\n\n\n\nLeveraging AI for NPC dialog generation can lead to more dynamic and engaging gameplay. It allows for a wide range of responses and can adapt to different player inputs.\n\n\n\nAI models require significant computational resources and may not be suitable for all platforms. Additionally, ensuring the appropriateness and quality of generated dialogs can be challenging.\n\n\n\nTraditional methods of NPC dialog generation involve pre-scripted dialogs or simple decision trees. While these methods are less resource-intensive, they lack the dynamism and adaptability of AI-generated dialogs.\n\n\n\nIn games with minimal NPC interactions or where dialog is not a significant aspect of gameplay, the use of AI for dialog generation may not be necessary.\n\n\n\nYes, the implementation of this strategy is done by us in the core of our game development process.\n\n\n\n\nV-Sekai GitHub\nAI assists this article.\nAxolotl Mistral Example"
   },
   {
-    "objectID": "decisions/20230630-vsekai-goal-meeting.html#web-requests-http-or-websocket-to-servers",
-    "href": "decisions/20230630-vsekai-goal-meeting.html#web-requests-http-or-websocket-to-servers",
-    "title": "Accepted: V-Sekai Meeting - Friday, June 30, 2023",
+    "objectID": "decisions/20231020-llama-cpp-mistral-npc.html#metadata",
+    "href": "decisions/20231020-llama-cpp-mistral-npc.html#metadata",
+    "title": "Proposed: Llama CPP AI Model NPC",
     "section": "",
-    "text": "Needs API or scripting language."
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, AI, NPC, Godot 4"
   },
   {
-    "objectID": "decisions/20230630-vsekai-goal-meeting.html#foundational-static-content-creationsdk-features-in-the-editor",
-    "href": "decisions/20230630-vsekai-goal-meeting.html#foundational-static-content-creationsdk-features-in-the-editor",
-    "title": "Accepted: V-Sekai Meeting - Friday, June 30, 2023",
+    "objectID": "decisions/20231020-llama-cpp-mistral-npc.html#the-backdrop",
+    "href": "decisions/20231020-llama-cpp-mistral-npc.html#the-backdrop",
+    "title": "Proposed: Llama CPP AI Model NPC",
     "section": "",
-    "text": "VRM import (avatars)\nGodot editor\nWorld creation\nUploading / sharing content items to an inventory."
+    "text": "In the realm of game development, creating engaging and dynamic Non-Player Characters (NPCs) is a challenging task. With advancements in AI, there’s an opportunity to leverage these technologies to enhance NPC interactions."
   },
   {
-    "objectID": "decisions/20230630-vsekai-goal-meeting.html#features-that-we-can-interface-with-third-parties",
-    "href": "decisions/20230630-vsekai-goal-meeting.html#features-that-we-can-interface-with-third-parties",
-    "title": "Accepted: V-Sekai Meeting - Friday, June 30, 2023",
+    "objectID": "decisions/20231020-llama-cpp-mistral-npc.html#the-challenge",
+    "href": "decisions/20231020-llama-cpp-mistral-npc.html#the-challenge",
+    "title": "Proposed: Llama CPP AI Model NPC",
     "section": "",
-    "text": "Screen sharing (OBS)\nModeling and 3D Creation (Blender)"
+    "text": "The challenge lies in effectively using various AI models to create the “brain” of an AI NPC in Godot 4. This involves generating realistic and contextually appropriate dialogs for the NPCs."
   },
   {
-    "objectID": "decisions/20230630-vsekai-goal-meeting.html#features-that-we-can-enable-platform-developers-to-build",
-    "href": "decisions/20230630-vsekai-goal-meeting.html#features-that-we-can-enable-platform-developers-to-build",
-    "title": "Accepted: V-Sekai Meeting - Friday, June 30, 2023",
+    "objectID": "decisions/20231020-llama-cpp-mistral-npc.html#the-strategy",
+    "href": "decisions/20231020-llama-cpp-mistral-npc.html#the-strategy",
+    "title": "Proposed: Llama CPP AI Model NPC",
     "section": "",
-    "text": "Text chat\nCollaboration features / meeting spaces\n\nDoodling\n3D doodling/modeling tools sketch\nSaving and loading of content at runtime\n\nSupport for proprietary video hosting websites"
+    "text": "The strategy involves using a local GPT4All model for generating AI-based NPC dialog. The script includes several exported variables that can be set in the Godot editor, such as npc_background_directions, sample_npc_question_prompt, and sample_npc_prompt_response. These variables are used to configure the behavior of the AI dialog generation.\nKey functions include:\n\ncall_model(prompt): Calls the local model with a given prompt.\nset_model(new_model_name : String): Sets the model name."
   },
   {
-    "objectID": "decisions/20230630-vsekai-goal-meeting.html#references",
-    "href": "decisions/20230630-vsekai-goal-meeting.html#references",
-    "title": "Accepted: V-Sekai Meeting - Friday, June 30, 2023",
+    "objectID": "decisions/20231020-llama-cpp-mistral-npc.html#the-upside",
+    "href": "decisions/20231020-llama-cpp-mistral-npc.html#the-upside",
+    "title": "Proposed: Llama CPP AI Model NPC",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Leveraging AI for NPC dialog generation can lead to more dynamic and engaging gameplay. It allows for a wide range of responses and can adapt to different player inputs."
   },
   {
-    "objectID": "decisions/20231112-archive-projects.html",
-    "href": "decisions/20231112-archive-projects.html",
-    "title": "Proposed: Effective V-Sekai project archival strategy",
+    "objectID": "decisions/20231020-llama-cpp-mistral-npc.html#the-downside",
+    "href": "decisions/20231020-llama-cpp-mistral-npc.html#the-downside",
+    "title": "Proposed: Llama CPP AI Model NPC",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai, fire, arne\nTags: V-Sekai, Documentation, Project Archiving\n\n\n\n\nThe need for an effective project archival strategy has been highlighted by the experience of going through old projects without any structure or crucial data. This proposal aims to overcome this challenge in the context of V-Sekai projects.\n\n\n\nThe main challenge is to create a structured and comprehensive archive of V-Sekai projects that will allow easy access and understanding of each project even years after its completion.\n\n\n\nThe proposed strategy includes:\n\nMaintaining online projects: If a project is hosted online, doesn’t necessitate upkeep and isn’t financially burdensome, it’s best to keep it live for easy future reference.\nStructuring offline projects: For those projects that aren’t feasible to keep online, store them in your local file system. Establish a main folder with yearly subfolders for systematic organization.\nCapturing screenshots: Screenshots serve as a quick visual reference of your project without the need to set it up again.\nCreating screen recordings: For a more comprehensive record, consider creating a screen recording of your project—this not only captures the visual aspect but also records any audio commentary you might provide.\nIncorporating a README: Include a README file that outlines the purpose of the project, its creation and abandonment dates, contributors, and instructions to get it up and running again. This provides essential information about the project at a glance.\nSecuring the database: In cases where projects lack a database dump, all the actual content could be lost. Execute a sqldump or use the export functionality your database offers to create a backup alongside your files. This ensures data preservation.\nRetaining generated assets: When utilizing static site generators, include the directory containing the compiled HTML, CSS & JS in the archive. This allows you to easily browse the complete website by simply running a static file server.\nArchiving on the Internet Archive: If the platform hosting your content isn’t owned by you (for instance, you’re publishing to Discord or Github), consider saving your data to the Archive.org. This adds an extra level of security for preserving your projects.\n\n\n\n\nThis strategy will ensure that all V-Sekai projects are well-documented and easily accessible in the future. It will also help in preserving the history and evolution of V-Sekai projects over time.\n\n\n\nThe process might be time-consuming and require regular updates and maintenance.\n\n\n\nAn alternative could be to use a cloud-based storage service for archiving projects. However, this might not provide the same level of organization and accessibility as the proposed strategy.\n\n\n\nIn cases where a project was short-lived or did not have significant impact, it might be decided to not include it in the archive.\n\n\n\nYes, this strategy should be implemented by the V-Sekai team as it directly affects the organization and preservation of their projects.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\narne.me/articles/archive-your-old-projects\n\nThis article was assisted by AI assistant Aria."
+    "text": "AI models require significant computational resources and may not be suitable for all platforms. Additionally, ensuring the appropriateness and quality of generated dialogs can be challenging."
   },
   {
-    "objectID": "decisions/20231112-archive-projects.html#metadata",
-    "href": "decisions/20231112-archive-projects.html#metadata",
-    "title": "Proposed: Effective V-Sekai project archival strategy",
+    "objectID": "decisions/20231020-llama-cpp-mistral-npc.html#the-road-not-taken",
+    "href": "decisions/20231020-llama-cpp-mistral-npc.html#the-road-not-taken",
+    "title": "Proposed: Llama CPP AI Model NPC",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai, fire, arne\nTags: V-Sekai, Documentation, Project Archiving"
+    "text": "Traditional methods of NPC dialog generation involve pre-scripted dialogs or simple decision trees. While these methods are less resource-intensive, they lack the dynamism and adaptability of AI-generated dialogs."
   },
   {
-    "objectID": "decisions/20231112-archive-projects.html#the-backdrop",
-    "href": "decisions/20231112-archive-projects.html#the-backdrop",
-    "title": "Proposed: Effective V-Sekai project archival strategy",
+    "objectID": "decisions/20231020-llama-cpp-mistral-npc.html#the-infrequent-use-case",
+    "href": "decisions/20231020-llama-cpp-mistral-npc.html#the-infrequent-use-case",
+    "title": "Proposed: Llama CPP AI Model NPC",
     "section": "",
-    "text": "The need for an effective project archival strategy has been highlighted by the experience of going through old projects without any structure or crucial data. This proposal aims to overcome this challenge in the context of V-Sekai projects."
+    "text": "In games with minimal NPC interactions or where dialog is not a significant aspect of gameplay, the use of AI for dialog generation may not be necessary."
   },
   {
-    "objectID": "decisions/20231112-archive-projects.html#the-challenge",
-    "href": "decisions/20231112-archive-projects.html#the-challenge",
-    "title": "Proposed: Effective V-Sekai project archival strategy",
+    "objectID": "decisions/20231020-llama-cpp-mistral-npc.html#in-core-and-done-by-us",
+    "href": "decisions/20231020-llama-cpp-mistral-npc.html#in-core-and-done-by-us",
+    "title": "Proposed: Llama CPP AI Model NPC",
     "section": "",
-    "text": "The main challenge is to create a structured and comprehensive archive of V-Sekai projects that will allow easy access and understanding of each project even years after its completion."
+    "text": "Yes, the implementation of this strategy is done by us in the core of our game development process."
   },
   {
-    "objectID": "decisions/20231112-archive-projects.html#the-strategy",
-    "href": "decisions/20231112-archive-projects.html#the-strategy",
-    "title": "Proposed: Effective V-Sekai project archival strategy",
+    "objectID": "decisions/20231020-llama-cpp-mistral-npc.html#further-reading",
+    "href": "decisions/20231020-llama-cpp-mistral-npc.html#further-reading",
+    "title": "Proposed: Llama CPP AI Model NPC",
     "section": "",
-    "text": "The proposed strategy includes:\n\nMaintaining online projects: If a project is hosted online, doesn’t necessitate upkeep and isn’t financially burdensome, it’s best to keep it live for easy future reference.\nStructuring offline projects: For those projects that aren’t feasible to keep online, store them in your local file system. Establish a main folder with yearly subfolders for systematic organization.\nCapturing screenshots: Screenshots serve as a quick visual reference of your project without the need to set it up again.\nCreating screen recordings: For a more comprehensive record, consider creating a screen recording of your project—this not only captures the visual aspect but also records any audio commentary you might provide.\nIncorporating a README: Include a README file that outlines the purpose of the project, its creation and abandonment dates, contributors, and instructions to get it up and running again. This provides essential information about the project at a glance.\nSecuring the database: In cases where projects lack a database dump, all the actual content could be lost. Execute a sqldump or use the export functionality your database offers to create a backup alongside your files. This ensures data preservation.\nRetaining generated assets: When utilizing static site generators, include the directory containing the compiled HTML, CSS & JS in the archive. This allows you to easily browse the complete website by simply running a static file server.\nArchiving on the Internet Archive: If the platform hosting your content isn’t owned by you (for instance, you’re publishing to Discord or Github), consider saving your data to the Archive.org. This adds an extra level of security for preserving your projects."
+    "text": "V-Sekai GitHub\nAI assists this article.\nAxolotl Mistral Example"
   },
   {
-    "objectID": "decisions/20231112-archive-projects.html#the-upside",
-    "href": "decisions/20231112-archive-projects.html#the-upside",
-    "title": "Proposed: Effective V-Sekai project archival strategy",
+    "objectID": "decisions/20220118-convert-gltf-to-a-scene.html",
+    "href": "decisions/20220118-convert-gltf-to-a-scene.html",
+    "title": "Accepted: Convert gltf to a scene with AudioStreamPlayer3D, convert AudiostreamPlayer3D to gltf and expose usability.",
     "section": "",
-    "text": "This strategy will ensure that all V-Sekai projects are well-documented and easily accessible in the future. It will also help in preserving the history and evolution of V-Sekai projects over time."
+    "text": "Status: accepted \nDeciders: V-Sekai,fire,lyuma,\nTags: V-Sekai,\n\n\n\nWe want to import gltf audio emitters in Godot Engine.\n\n\n\nWe designed a gltf audio emitter extension with OMI.\n\n\n\n\nConvert gltf to a scene with AudioStreamPlayer3D\nconvert AudiostreamPlayer3D to gltf\nPublish to the Godot Engine 4.0 asset library\n\n\n\n\n\nAudio emitters.\n\n\n\n\n\nWork needs to be done to implement omi audio.\n\n\n\n\n\nOption: The current status.\nRejection Reason: Unable to load audio from artwork.\n\n\n\n\nNot a few lines of code.\n\n\n\nI proposed the idea and people at OMI are starting to move on.\n\n\n\n\nhttps://github.com/omigroup/gltf-extensions/pull/1\n\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20231112-archive-projects.html#the-downside",
-    "href": "decisions/20231112-archive-projects.html#the-downside",
-    "title": "Proposed: Effective V-Sekai project archival strategy",
+    "objectID": "decisions/20220118-convert-gltf-to-a-scene.html#context-and-problem-statement",
+    "href": "decisions/20220118-convert-gltf-to-a-scene.html#context-and-problem-statement",
+    "title": "Accepted: Convert gltf to a scene with AudioStreamPlayer3D, convert AudiostreamPlayer3D to gltf and expose usability.",
     "section": "",
-    "text": "The process might be time-consuming and require regular updates and maintenance."
+    "text": "We want to import gltf audio emitters in Godot Engine."
   },
   {
-    "objectID": "decisions/20231112-archive-projects.html#the-road-not-taken",
-    "href": "decisions/20231112-archive-projects.html#the-road-not-taken",
-    "title": "Proposed: Effective V-Sekai project archival strategy",
+    "objectID": "decisions/20220118-convert-gltf-to-a-scene.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20220118-convert-gltf-to-a-scene.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Accepted: Convert gltf to a scene with AudioStreamPlayer3D, convert AudiostreamPlayer3D to gltf and expose usability.",
     "section": "",
-    "text": "An alternative could be to use a cloud-based storage service for archiving projects. However, this might not provide the same level of organization and accessibility as the proposed strategy."
+    "text": "We designed a gltf audio emitter extension with OMI."
   },
   {
-    "objectID": "decisions/20231112-archive-projects.html#the-infrequent-use-case",
-    "href": "decisions/20231112-archive-projects.html#the-infrequent-use-case",
-    "title": "Proposed: Effective V-Sekai project archival strategy",
+    "objectID": "decisions/20220118-convert-gltf-to-a-scene.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20220118-convert-gltf-to-a-scene.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Accepted: Convert gltf to a scene with AudioStreamPlayer3D, convert AudiostreamPlayer3D to gltf and expose usability.",
     "section": "",
-    "text": "In cases where a project was short-lived or did not have significant impact, it might be decided to not include it in the archive."
+    "text": "Convert gltf to a scene with AudioStreamPlayer3D\nconvert AudiostreamPlayer3D to gltf\nPublish to the Godot Engine 4.0 asset library"
   },
   {
-    "objectID": "decisions/20231112-archive-projects.html#in-core-and-done-by-us",
-    "href": "decisions/20231112-archive-projects.html#in-core-and-done-by-us",
-    "title": "Proposed: Effective V-Sekai project archival strategy",
+    "objectID": "decisions/20220118-convert-gltf-to-a-scene.html#positive-consequences",
+    "href": "decisions/20220118-convert-gltf-to-a-scene.html#positive-consequences",
+    "title": "Accepted: Convert gltf to a scene with AudioStreamPlayer3D, convert AudiostreamPlayer3D to gltf and expose usability.",
     "section": "",
-    "text": "Yes, this strategy should be implemented by the V-Sekai team as it directly affects the organization and preservation of their projects."
+    "text": "Audio emitters."
   },
   {
-    "objectID": "decisions/20231112-archive-projects.html#further-reading",
-    "href": "decisions/20231112-archive-projects.html#further-reading",
-    "title": "Proposed: Effective V-Sekai project archival strategy",
+    "objectID": "decisions/20220118-convert-gltf-to-a-scene.html#negative-consequences",
+    "href": "decisions/20220118-convert-gltf-to-a-scene.html#negative-consequences",
+    "title": "Accepted: Convert gltf to a scene with AudioStreamPlayer3D, convert AudiostreamPlayer3D to gltf and expose usability.",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\narne.me/articles/archive-your-old-projects\n\nThis article was assisted by AI assistant Aria."
+    "text": "Work needs to be done to implement omi audio."
   },
   {
-    "objectID": "decisions/20220624-webcam-to-posed-characters.html",
-    "href": "decisions/20220624-webcam-to-posed-characters.html",
-    "title": "Proposed: Connect Mediapipe to Blender",
+    "objectID": "decisions/20220118-convert-gltf-to-a-scene.html#option-graveyard",
+    "href": "decisions/20220118-convert-gltf-to-a-scene.html#option-graveyard",
+    "title": "Accepted: Convert gltf to a scene with AudioStreamPlayer3D, convert AudiostreamPlayer3D to gltf and expose usability.",
     "section": "",
-    "text": "Proposed: Connect Mediapipe to Blender\n\nContext and Problem Statement\nWant to animate a blender file with mediapipe\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nBy writing a c++ executable on Linux, we can connect Mediapipe to Blender.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n\nCreate a wrapper for https://github.com/infosia/vmc2bvh/tree/master/osc\nInstall Blender addon https://github.com/maybites/blender.NodeOSC\nConvert python script to c++\nMake c++ buildable by bazel\nBuild executables on Github Actions\n\n\nDesign loop\n\nhttps://github.com/CLIUtils/CLI11 for command line parsing\nhttps://github.com/infosia/vmc2bvh/blob/master/code/Vmc2Bvh.cpp for example code\nFor each process send osc to node osc (Blender).\nCreate a structure for the messages\n\n\n\nNotes from Lox\nI looked at your mediapipe code.\nI can write pseudocode but since i don’t have a cpp toolchain, i can’t guarantee it’ll work\nYou might take a look at my code\nhttps://gitlab.com/-/snippets/2349711#LC70\nThe idea is quite simple:\ncompute hips and chest 3d position by averaging left+right hips and left+right shoulders 3d landmark.\ncompute hips and chest 2d position similarly using 2d landmark.\ncompute the spine length as the hips-chest distance for both 3d and 2d.\nthe 2d-to-3d scale factor is then the ratio of the two distances.\nhips world position will be hips 2d position scaled by the factor, with z=0\nhow do I get the 3d landmarks\nthat’s provided by API https://google.github.io/mediapipe/solutions/pose#pose_world_landmarks\nlox9973 — Today at 01:26\n2d landmarks: output.pose_landmarks\n3d landmarks: output.pose_world_landmarks\nthey are both 4d vectors\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nML and armature work is hard\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nIt’s needed for face tracking to work well.\n\n\nReferences\nFrom Kendrick\n\nmedia_pipe_demo.zip\nhttps://github.com/V-Sekai/game-tools-V-Sekai\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Option: The current status.\nRejection Reason: Unable to load audio from artwork."
   },
   {
-    "objectID": "decisions/20240110-magical-girls-college-novel.html",
-    "href": "decisions/20240110-magical-girls-college-novel.html",
-    "title": "Proposed: Magical Girls College Manager Simulator",
+    "objectID": "decisions/20220118-convert-gltf-to-a-scene.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20220118-convert-gltf-to-a-scene.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Accepted: Convert gltf to a scene with AudioStreamPlayer3D, convert AudiostreamPlayer3D to gltf and expose usability.",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai, Cthulhoo, fire\nTags: V-Sekai\n\n\n\n\nA new game concept where players manage a college for magical girls has been proposed. Inspired by “Shadows of Doubt,” the game will focus on time management, relationship building, and academic success in a magical setting.\n\n\nShadows of Doubt on Steam\nA sandbox stealth game set in an alternate 1980s universe, blending detective work with gathering intelligence and solving cases.\n\n\n\n\nDevelop engaging planner scenarios for the player to navigate over the course of a week.\n\n\n\nUtilize VRM 3D chibis for character representation; initially limiting characters to five core members:\n\nThe Protagonist\nFour love interests\n\n\n\n\n\nStudents can earn study points by:\n\nAttending lectures\nCompleting homework\nStudying in the library\nEngaging in practical exercises\n\n\n\n\nCharacters can build relationships through activities:\n\nEating at the mess hall (easy, small benefit)\nGrabbing coffee together (small benefit)\nWatching movies at the cinema (moderate difficulty and benefit)\nHanging out at the pool (moderately challenging, moderate benefit)\nPicnicking in the park (challenging, moderate benefit)\nBeach trips (most challenging, high benefit)\n\n\n\n\nTo prevent burnout, students can:\n\nRead books\nPartake in hobbies\nParticipate in club activities\nEngage in chaste handholding\n\nSpecial considerations are given to individual preferences affecting decision outcomes, such as preferred or disliked activities impacting the willingness to participate.\n\n\n\n\n\n\nBurnout Management: A single meter may represent stamina and morale, balancing academic and social demands.\nPlanning Interface: Players plan weekly activities that unfold in real-time, adapting to emergent scenarios and random events.\nDuration: Each playthrough is one week long, split into weekdays and weekends, offering a chance to assess and strategize for the coming weeks.\n\n\n\n\nThis simulator offers a unique blend of time management, relationship simulation, and supernatural elements that appeal to various gaming audiences.\n\n\n\nComplex AI planning and character interaction mechanics could pose development challenges.\n\n\n\nThe decision to exclude a Pokemon-style battle system indicates a conscious move away from combat-oriented gameplay in favor of a simulation that emphasizes time management and social interactions within an academic setting. This choice differentiates the game from typical fantasy or RPG genres, focusing instead on daily life and relationship dynamics amongst magical girls.\nAlternative paths that were not taken might include:\n\nComplex combat systems with magical abilities.\nAn overarching narrative driven by external conflicts or villains.\nExpansion of the school’s supernatural elements beyond academic settings into broader world-saving quests.\n\nBy not pursuing these elements, the game remains intimate, allowing players to deeply explore the nuances of daily decisions and their impacts on personal growth and friendships.\n\n\n\nThough primary focus lies on managing relationships and academics within the college, rare use cases might involve:\n\nHandling exceptional magical crises that disrupt the normal flow of school life, requiring strategic changes to weekly planning.\nSpecial events such as magical tournaments or festivals, where characters must balance celebration with responsibilities.\nUnique narrative branches that only occur under specific conditions, adding replayability and depth to the character arcs.\n\nAddressing infrequent use cases can add layers of complexity and engagement for players, offering surprises and challenges that disrupt the routine management aspects of the game.\n\n\n\nThe V-Sekai team will decide core features and their implementation internally.\n\n\n\n\nV-Sekai GitHub Account\nV-Sekai Game Repository\n\nAI assistant Aria contributed to this proposal."
+    "text": "Not a few lines of code."
   },
   {
-    "objectID": "decisions/20240110-magical-girls-college-novel.html#metadata",
-    "href": "decisions/20240110-magical-girls-college-novel.html#metadata",
-    "title": "Proposed: Magical Girls College Manager Simulator",
+    "objectID": "decisions/20220118-convert-gltf-to-a-scene.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20220118-convert-gltf-to-a-scene.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Accepted: Convert gltf to a scene with AudioStreamPlayer3D, convert AudiostreamPlayer3D to gltf and expose usability.",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai, Cthulhoo, fire\nTags: V-Sekai"
+    "text": "I proposed the idea and people at OMI are starting to move on."
   },
   {
-    "objectID": "decisions/20240110-magical-girls-college-novel.html#the-backdrop",
-    "href": "decisions/20240110-magical-girls-college-novel.html#the-backdrop",
-    "title": "Proposed: Magical Girls College Manager Simulator",
+    "objectID": "decisions/20220118-convert-gltf-to-a-scene.html#references",
+    "href": "decisions/20220118-convert-gltf-to-a-scene.html#references",
+    "title": "Accepted: Convert gltf to a scene with AudioStreamPlayer3D, convert AudiostreamPlayer3D to gltf and expose usability.",
     "section": "",
-    "text": "A new game concept where players manage a college for magical girls has been proposed. Inspired by “Shadows of Doubt,” the game will focus on time management, relationship building, and academic success in a magical setting.\n\n\nShadows of Doubt on Steam\nA sandbox stealth game set in an alternate 1980s universe, blending detective work with gathering intelligence and solving cases."
+    "text": "https://github.com/omigroup/gltf-extensions/pull/1"
   },
   {
-    "objectID": "decisions/20240110-magical-girls-college-novel.html#the-challenge",
-    "href": "decisions/20240110-magical-girls-college-novel.html#the-challenge",
-    "title": "Proposed: Magical Girls College Manager Simulator",
+    "objectID": "decisions/20220118-convert-gltf-to-a-scene.html#derivative-license",
+    "href": "decisions/20220118-convert-gltf-to-a-scene.html#derivative-license",
+    "title": "Accepted: Convert gltf to a scene with AudioStreamPlayer3D, convert AudiostreamPlayer3D to gltf and expose usability.",
     "section": "",
-    "text": "Develop engaging planner scenarios for the player to navigate over the course of a week."
+    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240110-magical-girls-college-novel.html#the-strategy",
-    "href": "decisions/20240110-magical-girls-college-novel.html#the-strategy",
-    "title": "Proposed: Magical Girls College Manager Simulator",
+    "objectID": "decisions/20231218-mtlx-try-two.html",
+    "href": "decisions/20231218-mtlx-try-two.html",
+    "title": "Proposed: MaterialX try two.",
     "section": "",
-    "text": "Utilize VRM 3D chibis for character representation; initially limiting characters to five core members:\n\nThe Protagonist\nFour love interests\n\n\n\n\n\nStudents can earn study points by:\n\nAttending lectures\nCompleting homework\nStudying in the library\nEngaging in practical exercises\n\n\n\n\nCharacters can build relationships through activities:\n\nEating at the mess hall (easy, small benefit)\nGrabbing coffee together (small benefit)\nWatching movies at the cinema (moderate difficulty and benefit)\nHanging out at the pool (moderately challenging, moderate benefit)\nPicnicking in the park (challenging, moderate benefit)\nBeach trips (most challenging, high benefit)\n\n\n\n\nTo prevent burnout, students can:\n\nRead books\nPartake in hobbies\nParticipate in club activities\nEngage in chaste handholding\n\nSpecial considerations are given to individual preferences affecting decision outcomes, such as preferred or disliked activities impacting the willingness to participate."
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nThe conversation revolves around the implementation of MaterialX in Blender nodes and its extension to glTF. The goal is to have an official KHR extension for MaterialX in glTF, which Blender should also support.\n\n\n\nThis proposal discusses implementing MaterialX in Blender nodes and extending it to glTF. The aim is to support an official KHR extension for MaterialX in glTF.\n\n\n\nThe plan is to first implement MaterialX in Blender nodes, then extend it to glTF. Once a KHR extension exists for MaterialX in glTF, Blender should add that.\n\n\n\nIf successful, this will allow for more efficient and effective use of MaterialX in Blender and its extensions. It will also pave the way for further developments and improvements in this area.\n\n\n\nThe downside is that this is a complex task that requires deep understanding and expertise in both Blender and MaterialX. There may also be unforeseen challenges and issues that could arise during the implementation process.\n\n\n\nSuccess will enhance MaterialX use in Blender and its extensions. However, this complex task requires deep expertise in both Blender and MaterialX and may face unforeseen challenges.\n\n\n\nAn alternative could be focusing on MaterialX’s functionality with OpenGL before its implementation in Blender nodes and glTF. Or using Material maker or Substance Designer.\n\n\n\nThis core proposal will be executed by the V-Sekai team.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240110-magical-girls-college-novel.html#gameplay-mechanics",
-    "href": "decisions/20240110-magical-girls-college-novel.html#gameplay-mechanics",
-    "title": "Proposed: Magical Girls College Manager Simulator",
+    "objectID": "decisions/20231218-mtlx-try-two.html#metadata",
+    "href": "decisions/20231218-mtlx-try-two.html#metadata",
+    "title": "Proposed: MaterialX try two.",
     "section": "",
-    "text": "Burnout Management: A single meter may represent stamina and morale, balancing academic and social demands.\nPlanning Interface: Players plan weekly activities that unfold in real-time, adapting to emergent scenarios and random events.\nDuration: Each playthrough is one week long, split into weekdays and weekends, offering a chance to assess and strategize for the coming weeks."
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20240110-magical-girls-college-novel.html#the-upside",
-    "href": "decisions/20240110-magical-girls-college-novel.html#the-upside",
-    "title": "Proposed: Magical Girls College Manager Simulator",
+    "objectID": "decisions/20231218-mtlx-try-two.html#the-backdrop",
+    "href": "decisions/20231218-mtlx-try-two.html#the-backdrop",
+    "title": "Proposed: MaterialX try two.",
     "section": "",
-    "text": "This simulator offers a unique blend of time management, relationship simulation, and supernatural elements that appeal to various gaming audiences."
+    "text": "The conversation revolves around the implementation of MaterialX in Blender nodes and its extension to glTF. The goal is to have an official KHR extension for MaterialX in glTF, which Blender should also support."
   },
   {
-    "objectID": "decisions/20240110-magical-girls-college-novel.html#the-downside",
-    "href": "decisions/20240110-magical-girls-college-novel.html#the-downside",
-    "title": "Proposed: Magical Girls College Manager Simulator",
+    "objectID": "decisions/20231218-mtlx-try-two.html#the-challenge",
+    "href": "decisions/20231218-mtlx-try-two.html#the-challenge",
+    "title": "Proposed: MaterialX try two.",
     "section": "",
-    "text": "Complex AI planning and character interaction mechanics could pose development challenges."
+    "text": "This proposal discusses implementing MaterialX in Blender nodes and extending it to glTF. The aim is to support an official KHR extension for MaterialX in glTF."
   },
   {
-    "objectID": "decisions/20240110-magical-girls-college-novel.html#the-road-not-taken",
-    "href": "decisions/20240110-magical-girls-college-novel.html#the-road-not-taken",
-    "title": "Proposed: Magical Girls College Manager Simulator",
+    "objectID": "decisions/20231218-mtlx-try-two.html#the-strategy",
+    "href": "decisions/20231218-mtlx-try-two.html#the-strategy",
+    "title": "Proposed: MaterialX try two.",
     "section": "",
-    "text": "The decision to exclude a Pokemon-style battle system indicates a conscious move away from combat-oriented gameplay in favor of a simulation that emphasizes time management and social interactions within an academic setting. This choice differentiates the game from typical fantasy or RPG genres, focusing instead on daily life and relationship dynamics amongst magical girls.\nAlternative paths that were not taken might include:\n\nComplex combat systems with magical abilities.\nAn overarching narrative driven by external conflicts or villains.\nExpansion of the school’s supernatural elements beyond academic settings into broader world-saving quests.\n\nBy not pursuing these elements, the game remains intimate, allowing players to deeply explore the nuances of daily decisions and their impacts on personal growth and friendships."
+    "text": "The plan is to first implement MaterialX in Blender nodes, then extend it to glTF. Once a KHR extension exists for MaterialX in glTF, Blender should add that."
   },
   {
-    "objectID": "decisions/20240110-magical-girls-college-novel.html#the-infrequent-use-case",
-    "href": "decisions/20240110-magical-girls-college-novel.html#the-infrequent-use-case",
-    "title": "Proposed: Magical Girls College Manager Simulator",
+    "objectID": "decisions/20231218-mtlx-try-two.html#the-upside",
+    "href": "decisions/20231218-mtlx-try-two.html#the-upside",
+    "title": "Proposed: MaterialX try two.",
     "section": "",
-    "text": "Though primary focus lies on managing relationships and academics within the college, rare use cases might involve:\n\nHandling exceptional magical crises that disrupt the normal flow of school life, requiring strategic changes to weekly planning.\nSpecial events such as magical tournaments or festivals, where characters must balance celebration with responsibilities.\nUnique narrative branches that only occur under specific conditions, adding replayability and depth to the character arcs.\n\nAddressing infrequent use cases can add layers of complexity and engagement for players, offering surprises and challenges that disrupt the routine management aspects of the game."
+    "text": "If successful, this will allow for more efficient and effective use of MaterialX in Blender and its extensions. It will also pave the way for further developments and improvements in this area."
   },
   {
-    "objectID": "decisions/20240110-magical-girls-college-novel.html#in-core-and-done-by-us",
-    "href": "decisions/20240110-magical-girls-college-novel.html#in-core-and-done-by-us",
-    "title": "Proposed: Magical Girls College Manager Simulator",
+    "objectID": "decisions/20231218-mtlx-try-two.html#the-downside",
+    "href": "decisions/20231218-mtlx-try-two.html#the-downside",
+    "title": "Proposed: MaterialX try two.",
     "section": "",
-    "text": "The V-Sekai team will decide core features and their implementation internally."
+    "text": "The downside is that this is a complex task that requires deep understanding and expertise in both Blender and MaterialX. There may also be unforeseen challenges and issues that could arise during the implementation process."
   },
   {
-    "objectID": "decisions/20240110-magical-girls-college-novel.html#further-reading",
-    "href": "decisions/20240110-magical-girls-college-novel.html#further-reading",
-    "title": "Proposed: Magical Girls College Manager Simulator",
+    "objectID": "decisions/20231218-mtlx-try-two.html#the-road-not-taken",
+    "href": "decisions/20231218-mtlx-try-two.html#the-road-not-taken",
+    "title": "Proposed: MaterialX try two.",
     "section": "",
-    "text": "V-Sekai GitHub Account\nV-Sekai Game Repository\n\nAI assistant Aria contributed to this proposal."
+    "text": "Success will enhance MaterialX use in Blender and its extensions. However, this complex task requires deep expertise in both Blender and MaterialX and may face unforeseen challenges."
   },
   {
-    "objectID": "decisions/20220318-merge-retargeting-pr.html",
-    "href": "decisions/20220318-merge-retargeting-pr.html",
-    "title": "Proposed: Merge retargeting feature into Godot Engine master",
+    "objectID": "decisions/20231218-mtlx-try-two.html#the-infrequent-use-case",
+    "href": "decisions/20231218-mtlx-try-two.html#the-infrequent-use-case",
+    "title": "Proposed: MaterialX try two.",
     "section": "",
-    "text": "Proposed: Merge retargeting feature into Godot Engine master\n\nDescribe the status of the issue.\nSuperseded by the https://github.com/V-Sekai/V-Sekai.github.io/issues/229 proposal.\n\n\nList the deciders of the issue.\nV-Sekai,tokage,fire,lyuma\n\n\nDescribe the tags of the issue.\nV-Sekai,animation,retargeting,\n\n\nContext and Problem Statement\nWe want to share animations among different skeletons.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nUse tokage’s animation retargeting.\n\nLyuma’s explanations\nFirst of all, Local (rest) and Absolute modes are not good enough for most of the common retargeting cases. As a test,. I transferred a local animation from one character to an Xbot model, and the animation was broken. See here: left is Global (GLO) which works well. Right is Local (LOC) which has arms and body backwards (image below).\nSo the question is: when is Global not good enough? Well, it is not well suited for finger bones. By its very nature, it does not know how finger bones work, since it is working on the “silhouette” of the model.\nThis means none of these retargeting modes are good enough on their own. So what can we do about it?\nPerhaps it is possible to create an importer which twists fingers in the Bone Rest matrix into a configuration suitable for Global retargeting? I can’t say whether or not this is possible, but if this could be solved, then maybe we can use Global mode for everything?\nIt could be declared that finger bones shall be local, and all other bones shall be global, and everyone making assets should agree on finger rotations. This might not always be possible, but this is my interpretation of reduz’s idea of storing the PlaybackMode in Node B in Tokage’s diagram.\nOr it could be left up to each animation artist / importer which to use, and then you’re going to have a mixture of modes. If so, I see two ways to deal with it:\nThe animations are stored in global along with skeleton and converted using the source skeleton. This sounds ok in principle if some conversion tool could be made, but I would be afraid to deal with converting animations on the fly at runtime.\nThe animations must point to the RetargetOption they were generated with (or a per-track retarget mode), so that these differently sourced animations can be mixed.\nfrom what I can understand, “2” is what Tokage is proposing. I don’t see many other solutions to this. Fundamentally, if it is the case that animations made from different models are needed to be mixed, I don’t see a viable solution other than the last one.\n\n\n\n158130997-7582d581-2b3c-45f5-b28f-deb26f2f6ffd\n\n\n\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\n\nSee pull request.\n\n\n\nPositive Consequences\n\nSharing animations will make Godot Engine better.\n\n\n\nNegative Consequences\n\nThe feature is hard to do.\n\n\n\nOption graveyard\n\nUse Blender and other types of retargeting\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\n\nNOT A FEW LINES OF SCRIPT!!!\n\n\n\nIs there a reason why this should be core and done by us?\n\nThis should be a core feature of Godot Engine.\n\n\n\nReferences\n\nV-Sekai\nhttps://github.com/godotengine/godot/pull/56902\n\n\n\nLicense of the contribution\nCopyright (c) 2022 V-Sekai contributors. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "An alternative could be focusing on MaterialX’s functionality with OpenGL before its implementation in Blender nodes and glTF. Or using Material maker or Substance Designer."
   },
   {
-    "objectID": "decisions/20211031-bake-blend-shape-to-skeleton-animation.html",
-    "href": "decisions/20211031-bake-blend-shape-to-skeleton-animation.html",
-    "title": "Proposed: Bake blend shape to skeleton animation",
+    "objectID": "decisions/20231218-mtlx-try-two.html#in-core-and-done-by-us",
+    "href": "decisions/20231218-mtlx-try-two.html#in-core-and-done-by-us",
+    "title": "Proposed: MaterialX try two.",
     "section": "",
-    "text": "Proposed: Bake blend shape to skeleton animation\n\nContext and Problem Statement\nBlend shapes are expensive and hard to interpolate\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nWant to bake blend shapes to animations.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n./DemBones -i=\"Face_Geom.fbx\" -a=\"Face_Anim.abc\" --bindUpdate=2 -o=\"Decomposition_20_grouped_face.fbx\" --nnz=8 -b=256\nNote that the corresponding fbx is 0.01 scale while the alembic is in meters.\nThe RMSE = 0.00433256 must be this low.\nDo not pass #dembones if the RMSE is like 3.5.\nNext step is to integrate an existing 3d skeleton.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot a few lines of script.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nWe control the default skeleton controller.\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "This core proposal will be executed by the V-Sekai team."
   },
   {
-    "objectID": "decisions/20230806-music-gen.html",
-    "href": "decisions/20230806-music-gen.html",
-    "title": "Proposed: Sonic Symphony: Crafting Melodies with Machine Intelligence",
+    "objectID": "decisions/20231218-mtlx-try-two.html#further-reading",
+    "href": "decisions/20231218-mtlx-try-two.html#further-reading",
+    "title": "Proposed: MaterialX try two.",
     "section": "",
-    "text": "Status: proposed\nMasterminds: V-Sekai, fire\nKeywords: Music, AI, GPT-3, Python, Generation\n\n\n\n\nAs we navigate the 21st century, technology has become an inseparable part of our existence. It’s been making waves in the realm of music too. One such wave is the use of artificial intelligence (AI) to craft melodies. This blueprint proposes a method for creating music using computer algorithms.\n\n\n\nThe mission is to create music using computer programs.\n\n\n\nOne promising strategy is to employ .ABC files. These files have proven effective in generating outputs with AI models like GPT-3. The .ABC files carry data in the header section, such as the key signature, tempo, and time signature, which can be incorporated into the prompt.\nAlternatively, we could leverage AI models to script for us. For instance, we could ask for a Python script that composes the chromatic 7th intervals from C to B in eighth notes. The output format could be something user-friendly like Lilypond or MusicXML.\nHere’s a sneak peek at a Python script:\ndef generate_chromatic_seventh_intervals():\n    notes = ['C', 'C#', 'D', 'D#', 'E', 'F', 'F#', 'G', 'G#', 'A', 'A#', 'B']\n    intervals = []\n\n    for i in range(len(notes)):\n        seventh_interval = (i + 10) % len(notes)\n        intervals.append((notes[i], notes[seventh_interval]))\n\n    return intervals\n\nprint(generate_chromatic_seventh_intervals())\nAnother feasible strategy might be to use AI models to generate Lilypond syntax. Lilypond is a robust and adaptable tool for engraving tasks of all kinds, including sheet music, complex notation, vocal music, etc. Here is an example of a simple Lilypond syntax:\n\\relative c' {\n  c4 d e f |\n  g a b c |\n}\nThis code will compose a sequence of eighth notes from C to C.\n\n\n\nDuring the journey to find a solution, several paths were explored and abandoned for various reasons:\n\nUsing MIDI files: While MIDI files are a common choice for music creation, they were left behind due to their complexity and the challenge in crafting them programmatically.\nUsing MusicXML: Despite MusicXML being a comprehensive and widely supported format, it was abandoned due to its lengthy and intricate structure, which makes it tough to craft programmatically.\nUsing other music notation software: Other music notation software like Finale and Sibelius were considered but left behind due to their proprietary nature and lack of support for the programmatic generation of music.\n\n\n\n\n\nThis approach will pave the way for easier music creation.\nIt will sidestep the limitations posed by the intricate structure of MusicXML.\n\n\n\n\n\nThere may be some hurdles when using AI models to generate Lilypond syntax.\nTraining small transformers to output syntactically correct .ABC files might pose a challenge.\n\n\n\n\n\nSample .ABC files\nLilypond Notation Reference\nAsk HN: AI that produces sheet music for practice?"
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20230806-music-gen.html#the-blueprint",
-    "href": "decisions/20230806-music-gen.html#the-blueprint",
-    "title": "Proposed: Sonic Symphony: Crafting Melodies with Machine Intelligence",
+    "objectID": "decisions/20230911-can-poly-green-coords-extend-to-3d.html",
+    "href": "decisions/20230911-can-poly-green-coords-extend-to-3d.html",
+    "title": "Draft: Can Poly Green Coords extend to 3d?",
     "section": "",
-    "text": "Status: proposed\nMasterminds: V-Sekai, fire\nKeywords: Music, AI, GPT-3, Python, Generation"
+    "text": "Draft: Can Poly Green Coords extend to 3d?\nReminded by works by pixar: https://graphics.pixar.com/library/ProfileMover/\nHow applicable is this to 3d polygonal cages?\nYou may be interested by *[Green Coordinates for Triquad Cages in 3D](https://research.adobe.com/publication/green-coordinates-for-triquad-cages-in-3d/)* by Thiery and Boubekeur (SIGGRAPH Asia 2022). It is only for straight polygons though, the deformed cage cannot have Bézier arcs like this 2D version has, that's future work. ;) Profile curves are definitely a very nice and related work!\nOriginally posted by @eliemichel in https://github.com/eliemichel/PolyGreenCoords/issues/1#issuecomment-1683045650"
   },
   {
-    "objectID": "decisions/20230806-music-gen.html#the-backdrop",
-    "href": "decisions/20230806-music-gen.html#the-backdrop",
-    "title": "Proposed: Sonic Symphony: Crafting Melodies with Machine Intelligence",
+    "objectID": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html",
+    "href": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html",
+    "title": "Proposal: Stream a character from a webcam to the vmc protocol",
     "section": "",
-    "text": "As we navigate the 21st century, technology has become an inseparable part of our existence. It’s been making waves in the realm of music too. One such wave is the use of artificial intelligence (AI) to craft melodies. This blueprint proposes a method for creating music using computer algorithms."
+    "text": "Status: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nStream a character from a webcam to the vmc protocol so it can be played in any VMC receiver.\n\n\n\nKalidokit packages mediapipe, opengl acceleration and tensorflow.\n\n\n\nUse kalidokit and have it output the vmc protocol using osc.js.\n\n\n\n\nOutput OSC.js which Godot Engine can use.\n\n\n\n\n\nUses the nodejs runtimes which is added complexity.\n\n\n\n\n\nOption: \nRejection Reason: \n\n\n\n\nNot a few lines of script.\n\n\n\nI joined the dots.\n\n\n\n\nhttps://github.com/infosia/vmc2bvh\nhttps://github.com/colinbdclark/osc.js/\n\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230806-music-gen.html#the-challenge",
-    "href": "decisions/20230806-music-gen.html#the-challenge",
-    "title": "Proposed: Sonic Symphony: Crafting Melodies with Machine Intelligence",
+    "objectID": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html#context-and-problem-statement",
+    "href": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html#context-and-problem-statement",
+    "title": "Proposal: Stream a character from a webcam to the vmc protocol",
     "section": "",
-    "text": "The mission is to create music using computer programs."
+    "text": "Stream a character from a webcam to the vmc protocol so it can be played in any VMC receiver."
   },
   {
-    "objectID": "decisions/20230806-music-gen.html#the-strategy",
-    "href": "decisions/20230806-music-gen.html#the-strategy",
-    "title": "Proposed: Sonic Symphony: Crafting Melodies with Machine Intelligence",
+    "objectID": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposal: Stream a character from a webcam to the vmc protocol",
     "section": "",
-    "text": "One promising strategy is to employ .ABC files. These files have proven effective in generating outputs with AI models like GPT-3. The .ABC files carry data in the header section, such as the key signature, tempo, and time signature, which can be incorporated into the prompt.\nAlternatively, we could leverage AI models to script for us. For instance, we could ask for a Python script that composes the chromatic 7th intervals from C to B in eighth notes. The output format could be something user-friendly like Lilypond or MusicXML.\nHere’s a sneak peek at a Python script:\ndef generate_chromatic_seventh_intervals():\n    notes = ['C', 'C#', 'D', 'D#', 'E', 'F', 'F#', 'G', 'G#', 'A', 'A#', 'B']\n    intervals = []\n\n    for i in range(len(notes)):\n        seventh_interval = (i + 10) % len(notes)\n        intervals.append((notes[i], notes[seventh_interval]))\n\n    return intervals\n\nprint(generate_chromatic_seventh_intervals())\nAnother feasible strategy might be to use AI models to generate Lilypond syntax. Lilypond is a robust and adaptable tool for engraving tasks of all kinds, including sheet music, complex notation, vocal music, etc. Here is an example of a simple Lilypond syntax:\n\\relative c' {\n  c4 d e f |\n  g a b c |\n}\nThis code will compose a sequence of eighth notes from C to C."
+    "text": "Kalidokit packages mediapipe, opengl acceleration and tensorflow."
   },
   {
-    "objectID": "decisions/20230806-music-gen.html#the-road-not-taken",
-    "href": "decisions/20230806-music-gen.html#the-road-not-taken",
-    "title": "Proposed: Sonic Symphony: Crafting Melodies with Machine Intelligence",
+    "objectID": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposal: Stream a character from a webcam to the vmc protocol",
     "section": "",
-    "text": "During the journey to find a solution, several paths were explored and abandoned for various reasons:\n\nUsing MIDI files: While MIDI files are a common choice for music creation, they were left behind due to their complexity and the challenge in crafting them programmatically.\nUsing MusicXML: Despite MusicXML being a comprehensive and widely supported format, it was abandoned due to its lengthy and intricate structure, which makes it tough to craft programmatically.\nUsing other music notation software: Other music notation software like Finale and Sibelius were considered but left behind due to their proprietary nature and lack of support for the programmatic generation of music."
+    "text": "Use kalidokit and have it output the vmc protocol using osc.js."
   },
   {
-    "objectID": "decisions/20230806-music-gen.html#the-upside",
-    "href": "decisions/20230806-music-gen.html#the-upside",
-    "title": "Proposed: Sonic Symphony: Crafting Melodies with Machine Intelligence",
+    "objectID": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html#positive-consequences",
+    "href": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html#positive-consequences",
+    "title": "Proposal: Stream a character from a webcam to the vmc protocol",
     "section": "",
-    "text": "This approach will pave the way for easier music creation.\nIt will sidestep the limitations posed by the intricate structure of MusicXML."
+    "text": "Output OSC.js which Godot Engine can use."
   },
   {
-    "objectID": "decisions/20230806-music-gen.html#the-downside",
-    "href": "decisions/20230806-music-gen.html#the-downside",
-    "title": "Proposed: Sonic Symphony: Crafting Melodies with Machine Intelligence",
+    "objectID": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html#negative-consequences",
+    "href": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html#negative-consequences",
+    "title": "Proposal: Stream a character from a webcam to the vmc protocol",
     "section": "",
-    "text": "There may be some hurdles when using AI models to generate Lilypond syntax.\nTraining small transformers to output syntactically correct .ABC files might pose a challenge."
+    "text": "Uses the nodejs runtimes which is added complexity."
   },
   {
-    "objectID": "decisions/20230806-music-gen.html#further-reading",
-    "href": "decisions/20230806-music-gen.html#further-reading",
-    "title": "Proposed: Sonic Symphony: Crafting Melodies with Machine Intelligence",
+    "objectID": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html#option-graveyard",
+    "href": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html#option-graveyard",
+    "title": "Proposal: Stream a character from a webcam to the vmc protocol",
     "section": "",
-    "text": "Sample .ABC files\nLilypond Notation Reference\nAsk HN: AI that produces sheet music for practice?"
+    "text": "Option: \nRejection Reason:"
   },
   {
-    "objectID": "decisions/20231203-graphsage-embedding-generation.html",
-    "href": "decisions/20231203-graphsage-embedding-generation.html",
-    "title": "Draft: GraphSAGE Embedding Algorithm Explanation",
+    "objectID": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposal: Stream a character from a webcam to the vmc protocol",
     "section": "",
-    "text": "Status: Draft\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nIn the world of graph-based machine learning, the GraphSAGE algorithm has emerged as a powerful tool for generating node embeddings. It’s an inductive method that learns to generate embeddings by leveraging node feature information and the graph structure.\n\n\n\nUnderstanding the GraphSAGE algorithm can be challenging due to its complex nature and the use of various mathematical concepts. This proposal aims to break down the algorithm into understandable components and explain how it works in a clear and concise manner.\n\n\n\n\n\n\nThe algorithm incrementally aggregates and updates the representations of each node by considering the information from its local neighbors at each depth.\nAs the depth K increases, nodes incorporate information from a wider neighborhood.\nThe choice of aggregator functions can vary and has a significant impact on the performance and the type of information aggregated.\n\n\n\n\n\nGraph G(V,E)G(V,E): The input graph with nodes VV and edges EE.\nInput Features {xv∀v∈V}{xv​∀v∈V}: The features for each node in the graph.\nDepth KK: The depth of the search or the number of iterations.\nWeight Matrices Wk∀k∈{1…K}Wk​∀k∈{1…K}: The weight matrices used for each depth kk.\nNon-linearity σσ: A non-linear activation function.\nAggregator Functions AGGREGATEk∀k∈{1…K}AGGREGATEk​∀k∈{1…K}: Functions that aggregate information from the node’s neighbors.\nNeighborhood Function NN: A function that returns the set of neighbors for a given node.\n\n\n\n\n\nVector Representations zv∀v∈Vzv​∀v∈V: The resulting vector representations for all nodes in the graph.\n\n\n\n\n\nInitialization: Each node’s feature vector xvxv​ is used as the initial representation hv0hv0​.\nIteration for Depth KK: For each depth level from 1 to KK:\n\nFor each node vv in the graph:\n\nAggregate the representations of the nodes in its neighborhood N(v)N(v) using the aggregator function AGGREGATEkAGGREGATEk​ for that depth. This results in a new vector hN(v)khN(v)k​.\nConcatenate this aggregated vector with the node’s current representation hvk−1hvk−1​, and apply the weight matrix WkWk​ followed by the non-linearity σσ. This results in the updated representation hvkhvk​.\nNormalize the updated representation.\n\n\nFinal Representations: After the final iteration KK, the output for each node vv, zvzv​, is set as its last representation hvKhvK​.\n\n\n\n\n\nThe algorithm incrementally aggregates and updates the representations of each node by considering the information from its local neighbors at each depth.\nAs the depth KK increases, nodes incorporate information from a wider neighborhood.\nThe choice of aggregator functions can vary and has a significant impact on the performance and the type of information aggregated.\n\n\n\n\n\nInductive Learning: Unlike traditional methods that require retraining for new nodes, this algorithm can generate embeddings for unseen nodes.\nFlexibility: The algorithm can be adapted to different types of graphs and feature sets.\nScalability: It’s designed to work efficiently on large graphs.\n\nUnderstanding this algorithm helps in applying it to real-world graph problems, such as social network analysis, recommendation systems, and more, where the structure and features of the graph can be leveraged to learn informative node embeddings.\n\n\n\n\nThe GraphSAGE algorithm provides a flexible and scalable solution for generating node embeddings in large graphs. It allows for inductive learning, which means it can handle unseen nodes without requiring retraining. This makes it particularly useful for dynamic graphs where nodes may be added or removed over time.\n\n\n\nThe algorithm’s performance heavily depends on the choice of aggregator functions and the quality of node features. Poorly chosen functions or low-quality features can lead to suboptimal embeddings. Additionally, the algorithm may not perform well on graphs with complex structures or those that lack sufficient node feature information.\n\n\n\nAlternative methods for generating node embeddings, such as transductive learning algorithms, could be considered. However, these methods typically require retraining when new nodes are added, making them less suitable for dynamic graphs.\n\n\n\nWhile GraphSAGE is highly effective for many graph-based machine learning tasks, it may not be the best choice for all scenarios. For instance, in cases where the graph structure is less important than node features, other methods like feature-based machine learning models might be more appropriate.\n\n\n\nYes, this explanation of the GraphSAGE algorithm has been developed by us, with assistance from AI assistant Aria.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nInductive Representation Learning on Large Graphs"
+    "text": "Not a few lines of script."
   },
   {
-    "objectID": "decisions/20231203-graphsage-embedding-generation.html#metadata",
-    "href": "decisions/20231203-graphsage-embedding-generation.html#metadata",
-    "title": "Draft: GraphSAGE Embedding Algorithm Explanation",
+    "objectID": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposal: Stream a character from a webcam to the vmc protocol",
     "section": "",
-    "text": "Status: Draft\nDeciders: V-Sekai\nTags: V-Sekai"
+    "text": "I joined the dots."
   },
   {
-    "objectID": "decisions/20231203-graphsage-embedding-generation.html#the-backdrop",
-    "href": "decisions/20231203-graphsage-embedding-generation.html#the-backdrop",
-    "title": "Draft: GraphSAGE Embedding Algorithm Explanation",
+    "objectID": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html#references",
+    "href": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html#references",
+    "title": "Proposal: Stream a character from a webcam to the vmc protocol",
     "section": "",
-    "text": "In the world of graph-based machine learning, the GraphSAGE algorithm has emerged as a powerful tool for generating node embeddings. It’s an inductive method that learns to generate embeddings by leveraging node feature information and the graph structure."
+    "text": "https://github.com/infosia/vmc2bvh\nhttps://github.com/colinbdclark/osc.js/"
   },
   {
-    "objectID": "decisions/20231203-graphsage-embedding-generation.html#the-challenge",
-    "href": "decisions/20231203-graphsage-embedding-generation.html#the-challenge",
-    "title": "Draft: GraphSAGE Embedding Algorithm Explanation",
+    "objectID": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html#derivative-license",
+    "href": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html#derivative-license",
+    "title": "Proposal: Stream a character from a webcam to the vmc protocol",
     "section": "",
-    "text": "Understanding the GraphSAGE algorithm can be challenging due to its complex nature and the use of various mathematical concepts. This proposal aims to break down the algorithm into understandable components and explain how it works in a clear and concise manner."
+    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20231203-graphsage-embedding-generation.html#the-strategy",
-    "href": "decisions/20231203-graphsage-embedding-generation.html#the-strategy",
-    "title": "Draft: GraphSAGE Embedding Algorithm Explanation",
+    "objectID": "decisions/20231201-xr-hands-animation-node.html",
+    "href": "decisions/20231201-xr-hands-animation-node.html",
+    "title": "Proposed: Seamless Integration of XR Tracking in Godot Engine",
     "section": "",
-    "text": "The algorithm incrementally aggregates and updates the representations of each node by considering the information from its local neighbors at each depth.\nAs the depth K increases, nodes incorporate information from a wider neighborhood.\nThe choice of aggregator functions can vary and has a significant impact on the performance and the type of information aggregated.\n\n\n\n\n\nGraph G(V,E)G(V,E): The input graph with nodes VV and edges EE.\nInput Features {xv∀v∈V}{xv​∀v∈V}: The features for each node in the graph.\nDepth KK: The depth of the search or the number of iterations.\nWeight Matrices Wk∀k∈{1…K}Wk​∀k∈{1…K}: The weight matrices used for each depth kk.\nNon-linearity σσ: A non-linear activation function.\nAggregator Functions AGGREGATEk∀k∈{1…K}AGGREGATEk​∀k∈{1…K}: Functions that aggregate information from the node’s neighbors.\nNeighborhood Function NN: A function that returns the set of neighbors for a given node.\n\n\n\n\n\nVector Representations zv∀v∈Vzv​∀v∈V: The resulting vector representations for all nodes in the graph.\n\n\n\n\n\nInitialization: Each node’s feature vector xvxv​ is used as the initial representation hv0hv0​.\nIteration for Depth KK: For each depth level from 1 to KK:\n\nFor each node vv in the graph:\n\nAggregate the representations of the nodes in its neighborhood N(v)N(v) using the aggregator function AGGREGATEkAGGREGATEk​ for that depth. This results in a new vector hN(v)khN(v)k​.\nConcatenate this aggregated vector with the node’s current representation hvk−1hvk−1​, and apply the weight matrix WkWk​ followed by the non-linearity σσ. This results in the updated representation hvkhvk​.\nNormalize the updated representation.\n\n\nFinal Representations: After the final iteration KK, the output for each node vv, zvzv​, is set as its last representation hvKhvK​.\n\n\n\n\n\nThe algorithm incrementally aggregates and updates the representations of each node by considering the information from its local neighbors at each depth.\nAs the depth KK increases, nodes incorporate information from a wider neighborhood.\nThe choice of aggregator functions can vary and has a significant impact on the performance and the type of information aggregated.\n\n\n\n\n\nInductive Learning: Unlike traditional methods that require retraining for new nodes, this algorithm can generate embeddings for unseen nodes.\nFlexibility: The algorithm can be adapted to different types of graphs and feature sets.\nScalability: It’s designed to work efficiently on large graphs.\n\nUnderstanding this algorithm helps in applying it to real-world graph problems, such as social network analysis, recommendation systems, and more, where the structure and features of the graph can be leveraged to learn informative node embeddings."
+    "text": "Status: Proposed\nDeciders: V-Sekai Project Maintainers\nTags: XR, Hand Tracking, Full Body Tracking, OpenXR, Godot Engine, Animation Retargeting\n\n\n\n\nThe document outlines the need for supporting hand and full body tracking in extended reality (XR) applications. As virtual and augmented reality technologies improve, developers seek methods to integrate external skeleton data, such as OpenXR hand tracking or “full body tracking” skeletons, with existing imported and skinned meshes within the Godot Engine.\n\n\n\nThe current implementation of OpenXR provides a bone structure model for hand tracking data, which is incorporated into the Godot Engine through an OpenXRHand helper node. This node transforms global position and orientation data into local space. However, this approach has compatibility issues due to the requirement that mesh structures strictly adhere to the OpenXR standard. Additionally, there’s a growing need to support solutions for vendor APIs offering “full body tracking” skeletons.\n\n\n\nTo address these limitations, we propose the introduction of an OpenXRSkeleton3D node. This new node will:\n\nConform to the OpenXR standard for consistency.\nInclude hardcoded rest poses based on open hands recorded using OpenXR to simplify development.\nApply tracked OpenXR data dynamically to generate pose animations.\n\nThis strategy enables advanced retargeting scenarios and improves the integration of partial tracking data to hand meshes, humanoid skeletons, and blending of tracked poses with static ones for specific interactions like object manipulation.\n\n\n\n\nIn AR, deforming the mesh to match the player’s actual hands and fingers can significantly enhance realism.\n\n\n\nIn VR, this strategy enables the representation of fixed-size avatar hands that do not vary with the player’s real hand size, similar to games like “Half-Life Alyx.”\n\n\n\n\n\nThe proposed solution will improve interoperability with other systems and standards, such as:\n\nApple’s Vision Pro: By implementing an AppleSkeleton3D node to accommodate format and skeleton definitions differences.\nWebXR: Potentially aligning with the OpenXR system.\nGodot Engine: Including additional metacarpal bones in the engine’s humanoid skeleton for accurate retargeting.\n\n\n\n\nThe system could also be beneficial for non-XR applications such as:\n\nAdjusting leg movement to avoid ground collision.\nSupporting procedural foot-planting techniques for realistic animation.\nTracking arms for dynamic motion capture.\nAllowing inverse kinematics setups similar to classic shooters like Doom (2016).\nProviding active ragdolls for lifelike physics responses, exemplified in Godot Engine Active Ragdolls.\n\n\n\n\n\nXR-Specific Node: This component extracts and refines hand-tracking data into a specialized Skeleton3D node.\nAnimation BlendTree Node: This node handles the complex task of retargeting data across different skeletons, enabling a mix-and-match approach to animation and physical interactions.\n\n\n\n\nA typical use case may involve two hand skeletons from different tracking sources being retargeted onto a third skeleton dedicated to visual representation within the Godot Engine environment or for physics-based interactions.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20231203-graphsage-embedding-generation.html#the-upside",
-    "href": "decisions/20231203-graphsage-embedding-generation.html#the-upside",
-    "title": "Draft: GraphSAGE Embedding Algorithm Explanation",
+    "objectID": "decisions/20231201-xr-hands-animation-node.html#metadata",
+    "href": "decisions/20231201-xr-hands-animation-node.html#metadata",
+    "title": "Proposed: Seamless Integration of XR Tracking in Godot Engine",
     "section": "",
-    "text": "The GraphSAGE algorithm provides a flexible and scalable solution for generating node embeddings in large graphs. It allows for inductive learning, which means it can handle unseen nodes without requiring retraining. This makes it particularly useful for dynamic graphs where nodes may be added or removed over time."
+    "text": "Status: Proposed\nDeciders: V-Sekai Project Maintainers\nTags: XR, Hand Tracking, Full Body Tracking, OpenXR, Godot Engine, Animation Retargeting"
   },
   {
-    "objectID": "decisions/20231203-graphsage-embedding-generation.html#the-downside",
-    "href": "decisions/20231203-graphsage-embedding-generation.html#the-downside",
-    "title": "Draft: GraphSAGE Embedding Algorithm Explanation",
+    "objectID": "decisions/20231201-xr-hands-animation-node.html#the-backdrop",
+    "href": "decisions/20231201-xr-hands-animation-node.html#the-backdrop",
+    "title": "Proposed: Seamless Integration of XR Tracking in Godot Engine",
     "section": "",
-    "text": "The algorithm’s performance heavily depends on the choice of aggregator functions and the quality of node features. Poorly chosen functions or low-quality features can lead to suboptimal embeddings. Additionally, the algorithm may not perform well on graphs with complex structures or those that lack sufficient node feature information."
+    "text": "The document outlines the need for supporting hand and full body tracking in extended reality (XR) applications. As virtual and augmented reality technologies improve, developers seek methods to integrate external skeleton data, such as OpenXR hand tracking or “full body tracking” skeletons, with existing imported and skinned meshes within the Godot Engine."
   },
   {
-    "objectID": "decisions/20231203-graphsage-embedding-generation.html#the-road-not-taken",
-    "href": "decisions/20231203-graphsage-embedding-generation.html#the-road-not-taken",
-    "title": "Draft: GraphSAGE Embedding Algorithm Explanation",
+    "objectID": "decisions/20231201-xr-hands-animation-node.html#the-challenge",
+    "href": "decisions/20231201-xr-hands-animation-node.html#the-challenge",
+    "title": "Proposed: Seamless Integration of XR Tracking in Godot Engine",
     "section": "",
-    "text": "Alternative methods for generating node embeddings, such as transductive learning algorithms, could be considered. However, these methods typically require retraining when new nodes are added, making them less suitable for dynamic graphs."
+    "text": "The current implementation of OpenXR provides a bone structure model for hand tracking data, which is incorporated into the Godot Engine through an OpenXRHand helper node. This node transforms global position and orientation data into local space. However, this approach has compatibility issues due to the requirement that mesh structures strictly adhere to the OpenXR standard. Additionally, there’s a growing need to support solutions for vendor APIs offering “full body tracking” skeletons."
   },
   {
-    "objectID": "decisions/20231203-graphsage-embedding-generation.html#the-infrequent-use-case",
-    "href": "decisions/20231203-graphsage-embedding-generation.html#the-infrequent-use-case",
-    "title": "Draft: GraphSAGE Embedding Algorithm Explanation",
+    "objectID": "decisions/20231201-xr-hands-animation-node.html#the-strategy",
+    "href": "decisions/20231201-xr-hands-animation-node.html#the-strategy",
+    "title": "Proposed: Seamless Integration of XR Tracking in Godot Engine",
     "section": "",
-    "text": "While GraphSAGE is highly effective for many graph-based machine learning tasks, it may not be the best choice for all scenarios. For instance, in cases where the graph structure is less important than node features, other methods like feature-based machine learning models might be more appropriate."
+    "text": "To address these limitations, we propose the introduction of an OpenXRSkeleton3D node. This new node will:\n\nConform to the OpenXR standard for consistency.\nInclude hardcoded rest poses based on open hands recorded using OpenXR to simplify development.\nApply tracked OpenXR data dynamically to generate pose animations.\n\nThis strategy enables advanced retargeting scenarios and improves the integration of partial tracking data to hand meshes, humanoid skeletons, and blending of tracked poses with static ones for specific interactions like object manipulation.\n\n\n\n\nIn AR, deforming the mesh to match the player’s actual hands and fingers can significantly enhance realism.\n\n\n\nIn VR, this strategy enables the representation of fixed-size avatar hands that do not vary with the player’s real hand size, similar to games like “Half-Life Alyx.”"
   },
   {
-    "objectID": "decisions/20231203-graphsage-embedding-generation.html#in-core-and-done-by-us",
-    "href": "decisions/20231203-graphsage-embedding-generation.html#in-core-and-done-by-us",
-    "title": "Draft: GraphSAGE Embedding Algorithm Explanation",
+    "objectID": "decisions/20231201-xr-hands-animation-node.html#compatibility-with-other-systems",
+    "href": "decisions/20231201-xr-hands-animation-node.html#compatibility-with-other-systems",
+    "title": "Proposed: Seamless Integration of XR Tracking in Godot Engine",
     "section": "",
-    "text": "Yes, this explanation of the GraphSAGE algorithm has been developed by us, with assistance from AI assistant Aria."
+    "text": "The proposed solution will improve interoperability with other systems and standards, such as:\n\nApple’s Vision Pro: By implementing an AppleSkeleton3D node to accommodate format and skeleton definitions differences.\nWebXR: Potentially aligning with the OpenXR system.\nGodot Engine: Including additional metacarpal bones in the engine’s humanoid skeleton for accurate retargeting."
   },
   {
-    "objectID": "decisions/20231203-graphsage-embedding-generation.html#further-reading",
-    "href": "decisions/20231203-graphsage-embedding-generation.html#further-reading",
-    "title": "Draft: GraphSAGE Embedding Algorithm Explanation",
+    "objectID": "decisions/20231201-xr-hands-animation-node.html#non-xr-use-cases-showcasing-broader-utility",
+    "href": "decisions/20231201-xr-hands-animation-node.html#non-xr-use-cases-showcasing-broader-utility",
+    "title": "Proposed: Seamless Integration of XR Tracking in Godot Engine",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nInductive Representation Learning on Large Graphs"
+    "text": "The system could also be beneficial for non-XR applications such as:\n\nAdjusting leg movement to avoid ground collision.\nSupporting procedural foot-planting techniques for realistic animation.\nTracking arms for dynamic motion capture.\nAllowing inverse kinematics setups similar to classic shooters like Doom (2016).\nProviding active ragdolls for lifelike physics responses, exemplified in Godot Engine Active Ragdolls."
   },
   {
-    "objectID": "decisions/20240307-rabbitmq-ra.html",
-    "href": "decisions/20240307-rabbitmq-ra.html",
-    "title": "Proposed: Implement Ra in V-Sekai",
+    "objectID": "decisions/20231201-xr-hands-animation-node.html#core-components",
+    "href": "decisions/20231201-xr-hands-animation-node.html#core-components",
+    "title": "Proposed: Seamless Integration of XR Tracking in Godot Engine",
     "section": "",
-    "text": "V-Sekai, a VR social network, needs reliable state machines for data persistence. Current system may struggle with data consistency and failure recovery.\n\n\n\nUser experience can be disrupted due to potential data inconsistencies and loss, leading to issues like lost interactions and inconsistent virtual states.\n\n\n\nImplement Ra, a Raft implementation by Team RabbitMQ, in any Erlang or Elixir project. Ra enables persistent, fault-tolerant, replicated state machines.\n\n\n\n\nFault Tolerance: Ra ensures data consistency via leader election and log replication.\nEfficiency: Supports log compaction and snapshot installation.\nScalability: Suitable for large-scale applications like V-Sekai.\n\n\n\n\n\nLearning Curve: Developers need to learn Ra and the Raft consensus algorithm.\nDependency: Ra could increase project complexity.\n\n\n\n\nOther solutions like CRDTs were considered but have major shortcomings.\n\n\n\nIn small distributed systems with rare failures, Ra’s benefits may not be fully realized.\n\n\n\nThe V-Sekai team will implement Ra.\n\n\n\nProposed\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\nRa\nErlang\nElixir\nDistributed Systems\n\n\n\n\n\nV-Sekai · GitHub\nV-Sekai/v-sekai-game\n\nAssisted by Aria, an AI assistant."
+    "text": "XR-Specific Node: This component extracts and refines hand-tracking data into a specialized Skeleton3D node.\nAnimation BlendTree Node: This node handles the complex task of retargeting data across different skeletons, enabling a mix-and-match approach to animation and physical interactions."
   },
   {
-    "objectID": "decisions/20240307-rabbitmq-ra.html#context",
-    "href": "decisions/20240307-rabbitmq-ra.html#context",
-    "title": "Proposed: Implement Ra in V-Sekai",
+    "objectID": "decisions/20231201-xr-hands-animation-node.html#application-scenarios",
+    "href": "decisions/20231201-xr-hands-animation-node.html#application-scenarios",
+    "title": "Proposed: Seamless Integration of XR Tracking in Godot Engine",
     "section": "",
-    "text": "V-Sekai, a VR social network, needs reliable state machines for data persistence. Current system may struggle with data consistency and failure recovery."
+    "text": "A typical use case may involve two hand skeletons from different tracking sources being retargeted onto a third skeleton dedicated to visual representation within the Godot Engine environment or for physics-based interactions."
   },
   {
-    "objectID": "decisions/20240307-rabbitmq-ra.html#problem",
-    "href": "decisions/20240307-rabbitmq-ra.html#problem",
-    "title": "Proposed: Implement Ra in V-Sekai",
+    "objectID": "decisions/20231201-xr-hands-animation-node.html#further-reading",
+    "href": "decisions/20231201-xr-hands-animation-node.html#further-reading",
+    "title": "Proposed: Seamless Integration of XR Tracking in Godot Engine",
     "section": "",
-    "text": "User experience can be disrupted due to potential data inconsistencies and loss, leading to issues like lost interactions and inconsistent virtual states."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240307-rabbitmq-ra.html#solution",
-    "href": "decisions/20240307-rabbitmq-ra.html#solution",
-    "title": "Proposed: Implement Ra in V-Sekai",
+    "objectID": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html",
+    "href": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html",
+    "title": "Proposed: Solve Renik directly rather than through many bone ik",
     "section": "",
-    "text": "Implement Ra, a Raft implementation by Team RabbitMQ, in any Erlang or Elixir project. Ra enables persistent, fault-tolerant, replicated state machines."
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nWe want a robust character controller through V-Sekai renik, but we’re working on an abstract many bone ik and there wasn’t visible progress. The current approach is not yielding the desired results and is proving to be inefficient.\n\n\n\nPause many bone ik and update renik to use many bone ik technologies. This would involve refactoring the existing codebase to integrate the many bone ik technologies directly into the renik solution.\n\n\n\nTo be determined.\n\n\n\n\nMore efficient and direct solution for character control.\nBetter utilization of many bone ik technologies.\nPotential for improved performance and responsiveness in the final product.\n\n\n\n\n\nRequires significant refactoring of the existing codebase.\nPotential for introducing new bugs during the integration process.\nMay require additional resources and time to implement correctly.\n\n\n\n\nThis section is reserved for documenting past decisions and their outcomes.\n\n\n\nNo, this enhancement involves a fundamental change in how the character controller is implemented and cannot be achieved with a simple script workaround.\n\n\n\nYes, as the creators of the system, we have the best understanding of its architecture and potential improvements. Outsourcing or relying on external contributions may not align with our vision for the project.\n\n\n\n\nV-Sekai"
   },
   {
-    "objectID": "decisions/20240307-rabbitmq-ra.html#benefits",
-    "href": "decisions/20240307-rabbitmq-ra.html#benefits",
-    "title": "Proposed: Implement Ra in V-Sekai",
+    "objectID": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html#metadata",
+    "href": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html#metadata",
+    "title": "Proposed: Solve Renik directly rather than through many bone ik",
     "section": "",
-    "text": "Fault Tolerance: Ra ensures data consistency via leader election and log replication.\nEfficiency: Supports log compaction and snapshot installation.\nScalability: Suitable for large-scale applications like V-Sekai."
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20240307-rabbitmq-ra.html#downsides",
-    "href": "decisions/20240307-rabbitmq-ra.html#downsides",
-    "title": "Proposed: Implement Ra in V-Sekai",
+    "objectID": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html#context-and-problem-statement",
+    "href": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html#context-and-problem-statement",
+    "title": "Proposed: Solve Renik directly rather than through many bone ik",
     "section": "",
-    "text": "Learning Curve: Developers need to learn Ra and the Raft consensus algorithm.\nDependency: Ra could increase project complexity."
+    "text": "We want a robust character controller through V-Sekai renik, but we’re working on an abstract many bone ik and there wasn’t visible progress. The current approach is not yielding the desired results and is proving to be inefficient."
   },
   {
-    "objectID": "decisions/20240307-rabbitmq-ra.html#alternatives",
-    "href": "decisions/20240307-rabbitmq-ra.html#alternatives",
-    "title": "Proposed: Implement Ra in V-Sekai",
+    "objectID": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html#proposed-solution",
+    "href": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html#proposed-solution",
+    "title": "Proposed: Solve Renik directly rather than through many bone ik",
     "section": "",
-    "text": "Other solutions like CRDTs were considered but have major shortcomings."
+    "text": "Pause many bone ik and update renik to use many bone ik technologies. This would involve refactoring the existing codebase to integrate the many bone ik technologies directly into the renik solution."
   },
   {
-    "objectID": "decisions/20240307-rabbitmq-ra.html#infrequent-use-case",
-    "href": "decisions/20240307-rabbitmq-ra.html#infrequent-use-case",
-    "title": "Proposed: Implement Ra in V-Sekai",
+    "objectID": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html#implementation",
+    "href": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html#implementation",
+    "title": "Proposed: Solve Renik directly rather than through many bone ik",
     "section": "",
-    "text": "In small distributed systems with rare failures, Ra’s benefits may not be fully realized."
+    "text": "To be determined."
   },
   {
-    "objectID": "decisions/20240307-rabbitmq-ra.html#implementation",
-    "href": "decisions/20240307-rabbitmq-ra.html#implementation",
-    "title": "Proposed: Implement Ra in V-Sekai",
+    "objectID": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html#positive-consequences",
+    "href": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html#positive-consequences",
+    "title": "Proposed: Solve Renik directly rather than through many bone ik",
     "section": "",
-    "text": "The V-Sekai team will implement Ra."
+    "text": "More efficient and direct solution for character control.\nBetter utilization of many bone ik technologies.\nPotential for improved performance and responsiveness in the final product."
   },
   {
-    "objectID": "decisions/20240307-rabbitmq-ra.html#status",
-    "href": "decisions/20240307-rabbitmq-ra.html#status",
-    "title": "Proposed: Implement Ra in V-Sekai",
+    "objectID": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html#negative-consequences",
+    "href": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html#negative-consequences",
+    "title": "Proposed: Solve Renik directly rather than through many bone ik",
     "section": "",
-    "text": "Proposed"
+    "text": "Requires significant refactoring of the existing codebase.\nPotential for introducing new bugs during the integration process.\nMay require additional resources and time to implement correctly."
   },
   {
-    "objectID": "decisions/20240307-rabbitmq-ra.html#decision-makers",
-    "href": "decisions/20240307-rabbitmq-ra.html#decision-makers",
-    "title": "Proposed: Implement Ra in V-Sekai",
+    "objectID": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html#option-graveyard",
+    "href": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html#option-graveyard",
+    "title": "Proposed: Solve Renik directly rather than through many bone ik",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "This section is reserved for documenting past decisions and their outcomes."
   },
   {
-    "objectID": "decisions/20240307-rabbitmq-ra.html#tags",
-    "href": "decisions/20240307-rabbitmq-ra.html#tags",
-    "title": "Proposed: Implement Ra in V-Sekai",
+    "objectID": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Solve Renik directly rather than through many bone ik",
     "section": "",
-    "text": "V-Sekai\nRa\nErlang\nElixir\nDistributed Systems"
+    "text": "No, this enhancement involves a fundamental change in how the character controller is implemented and cannot be achieved with a simple script workaround."
   },
   {
-    "objectID": "decisions/20240307-rabbitmq-ra.html#further-reading",
-    "href": "decisions/20240307-rabbitmq-ra.html#further-reading",
-    "title": "Proposed: Implement Ra in V-Sekai",
+    "objectID": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Solve Renik directly rather than through many bone ik",
     "section": "",
-    "text": "V-Sekai · GitHub\nV-Sekai/v-sekai-game\n\nAssisted by Aria, an AI assistant."
+    "text": "Yes, as the creators of the system, we have the best understanding of its architecture and potential improvements. Outsourcing or relying on external contributions may not align with our vision for the project."
   },
   {
-    "objectID": "decisions/20240710-platform-focus-on-pcvr-and-web.html",
-    "href": "decisions/20240710-platform-focus-on-pcvr-and-web.html",
-    "title": "Proposed: Focus on PCVR and the Web",
+    "objectID": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html#references",
+    "href": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html#references",
+    "title": "Proposed: Solve Renik directly rather than through many bone ik",
     "section": "",
-    "text": "In the development of virtual reality (VR) applications, focusing on both PC-based VR (PCVR) and web platforms can provide a broader reach and enhanced user experience.\nNote: When referring to “web” in this document, it specifically means web desktop platforms and not WebXR.\n\n\n\nBalancing the development efforts between PCVR and web platforms presents challenges in terms of resource allocation and maintaining consistent performance across different environments.\n\n\n\n\nUnified Codebase: Develop a unified codebase that supports both PCVR and web platforms to ensure consistency and reduce maintenance overhead.\nUnified Networking: A PCVR client can communicate with a web client.\nPlatform-Specific Optimizations: Implement platform-specific optimizations to leverage the strengths of each environment.\nResponsive Design: Ensure the user interface is responsive and adapts seamlessly to different devices and screen sizes.\nPerformance Monitoring: Continuously monitor performance metrics to identify and address any platform-specific issues promptly.\nMultithreaded Web: Opt for a multithreaded web approach instead of a single-threaded one to enhance performance and responsiveness on web platforms.\n\n\n\n\n\nBroader Reach: Supporting both PCVR and web platforms allows us to cater to a wider audience.\nEnhanced User Experience: Platform-specific optimizations ensure users have the best possible experience regardless of their device.\nConsistency: A unified codebase ensures consistent functionality and appearance across platforms.\n\n\n\n\n\nResource Allocation: Balancing development efforts between two platforms may require additional resources.\nComplexity: Managing a unified codebase with platform-specific optimizations can introduce complexity.\n\n\n\n\nFocusing exclusively on either PCVR or web platforms was considered but ultimately deemed less effective in reaching a broader audience.\n\n\n\nIn scenarios where the application is highly specialized for either PCVR or web, focusing on one platform might be more efficient.\n\n\n\nThis proposal aligns with our core values of inclusivity and innovation and will be implemented by our team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\nFire\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20240710-platform-focus-on-pcvr-and-web.html#the-context",
-    "href": "decisions/20240710-platform-focus-on-pcvr-and-web.html#the-context",
-    "title": "Proposed: Focus on PCVR and the Web",
+    "objectID": "decisions/20231226-furniture-vs-organic.html",
+    "href": "decisions/20231226-furniture-vs-organic.html",
+    "title": "Proposed: Hardsurface vs Organic",
     "section": "",
-    "text": "In the development of virtual reality (VR) applications, focusing on both PC-based VR (PCVR) and web platforms can provide a broader reach and enhanced user experience.\nNote: When referring to “web” in this document, it specifically means web desktop platforms and not WebXR."
+    "text": "Status: Proposed\nDeciders: V-Sekai, fire, msstabby\nTags: V-Sekai, VR, Godot Engine, 3D Modeling, Performance Optimization\n\n\n\n\nV-Sekai is a vibrant platform for social VR experiences built on the Godot Engine. Its success hinges on the seamless integration of visually appealing 3D environments and characters that perform optimally across various VR hardware.\n\n\n\nThe challenge lies in striking a balance between hardsurface (static objects) and organic (characters) modeling within V-Sekai. The goal is to optimize both types of models, reducing geometric complexity without compromising on visual richness or functional requirements of rigging and animation.\n\n\n\nAdopt different strategies for hardsurface and organic modeling. For hardsurface models, focus on reducing the number of triangles, especially for non-moving geometry like furniture. For organic models, ensure even distribution of triangles to meet the unique requirements of rigging and deformation during animation.\n\n\n\nSuch optimization can lead to improved performance, reduced latency, and a more immersive VR experience for users.\n\n\n\nIt may require rethinking and overhauling existing modeling workflows, which could be resource-intensive.\n\n\n\nIgnoring the optimization could result in suboptimal performance, impacting the user experience and the scalability of V-Sekai projects.\n\n\n\nRare or unique objects and characters that require a departure from standard optimization practices to maintain their distinctiveness or functionality.\n\n\n\nThe proposal recommends integrating these optimization practices into the core development workflow of V-Sekai, handled by the internal team.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis proposal was assisted by Aria, an AI assistant."
   },
   {
-    "objectID": "decisions/20240710-platform-focus-on-pcvr-and-web.html#the-problem-statement",
-    "href": "decisions/20240710-platform-focus-on-pcvr-and-web.html#the-problem-statement",
-    "title": "Proposed: Focus on PCVR and the Web",
+    "objectID": "decisions/20231226-furniture-vs-organic.html#metadata",
+    "href": "decisions/20231226-furniture-vs-organic.html#metadata",
+    "title": "Proposed: Hardsurface vs Organic",
     "section": "",
-    "text": "Balancing the development efforts between PCVR and web platforms presents challenges in terms of resource allocation and maintaining consistent performance across different environments."
+    "text": "Status: Proposed\nDeciders: V-Sekai, fire, msstabby\nTags: V-Sekai, VR, Godot Engine, 3D Modeling, Performance Optimization"
   },
   {
-    "objectID": "decisions/20240710-platform-focus-on-pcvr-and-web.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240710-platform-focus-on-pcvr-and-web.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Focus on PCVR and the Web",
+    "objectID": "decisions/20231226-furniture-vs-organic.html#context",
+    "href": "decisions/20231226-furniture-vs-organic.html#context",
+    "title": "Proposed: Hardsurface vs Organic",
     "section": "",
-    "text": "Unified Codebase: Develop a unified codebase that supports both PCVR and web platforms to ensure consistency and reduce maintenance overhead.\nUnified Networking: A PCVR client can communicate with a web client.\nPlatform-Specific Optimizations: Implement platform-specific optimizations to leverage the strengths of each environment.\nResponsive Design: Ensure the user interface is responsive and adapts seamlessly to different devices and screen sizes.\nPerformance Monitoring: Continuously monitor performance metrics to identify and address any platform-specific issues promptly.\nMultithreaded Web: Opt for a multithreaded web approach instead of a single-threaded one to enhance performance and responsiveness on web platforms."
+    "text": "V-Sekai is a vibrant platform for social VR experiences built on the Godot Engine. Its success hinges on the seamless integration of visually appealing 3D environments and characters that perform optimally across various VR hardware."
   },
   {
-    "objectID": "decisions/20240710-platform-focus-on-pcvr-and-web.html#the-benefits",
-    "href": "decisions/20240710-platform-focus-on-pcvr-and-web.html#the-benefits",
-    "title": "Proposed: Focus on PCVR and the Web",
+    "objectID": "decisions/20231226-furniture-vs-organic.html#problem",
+    "href": "decisions/20231226-furniture-vs-organic.html#problem",
+    "title": "Proposed: Hardsurface vs Organic",
     "section": "",
-    "text": "Broader Reach: Supporting both PCVR and web platforms allows us to cater to a wider audience.\nEnhanced User Experience: Platform-specific optimizations ensure users have the best possible experience regardless of their device.\nConsistency: A unified codebase ensures consistent functionality and appearance across platforms."
+    "text": "The challenge lies in striking a balance between hardsurface (static objects) and organic (characters) modeling within V-Sekai. The goal is to optimize both types of models, reducing geometric complexity without compromising on visual richness or functional requirements of rigging and animation."
   },
   {
-    "objectID": "decisions/20240710-platform-focus-on-pcvr-and-web.html#the-downsides",
-    "href": "decisions/20240710-platform-focus-on-pcvr-and-web.html#the-downsides",
-    "title": "Proposed: Focus on PCVR and the Web",
+    "objectID": "decisions/20231226-furniture-vs-organic.html#possible-solution",
+    "href": "decisions/20231226-furniture-vs-organic.html#possible-solution",
+    "title": "Proposed: Hardsurface vs Organic",
     "section": "",
-    "text": "Resource Allocation: Balancing development efforts between two platforms may require additional resources.\nComplexity: Managing a unified codebase with platform-specific optimizations can introduce complexity."
+    "text": "Adopt different strategies for hardsurface and organic modeling. For hardsurface models, focus on reducing the number of triangles, especially for non-moving geometry like furniture. For organic models, ensure even distribution of triangles to meet the unique requirements of rigging and deformation during animation."
   },
   {
-    "objectID": "decisions/20240710-platform-focus-on-pcvr-and-web.html#the-road-not-taken",
-    "href": "decisions/20240710-platform-focus-on-pcvr-and-web.html#the-road-not-taken",
-    "title": "Proposed: Focus on PCVR and the Web",
+    "objectID": "decisions/20231226-furniture-vs-organic.html#pros",
+    "href": "decisions/20231226-furniture-vs-organic.html#pros",
+    "title": "Proposed: Hardsurface vs Organic",
     "section": "",
-    "text": "Focusing exclusively on either PCVR or web platforms was considered but ultimately deemed less effective in reaching a broader audience."
+    "text": "Such optimization can lead to improved performance, reduced latency, and a more immersive VR experience for users."
   },
   {
-    "objectID": "decisions/20240710-platform-focus-on-pcvr-and-web.html#the-infrequent-use-case",
-    "href": "decisions/20240710-platform-focus-on-pcvr-and-web.html#the-infrequent-use-case",
-    "title": "Proposed: Focus on PCVR and the Web",
+    "objectID": "decisions/20231226-furniture-vs-organic.html#cons",
+    "href": "decisions/20231226-furniture-vs-organic.html#cons",
+    "title": "Proposed: Hardsurface vs Organic",
     "section": "",
-    "text": "In scenarios where the application is highly specialized for either PCVR or web, focusing on one platform might be more efficient."
+    "text": "It may require rethinking and overhauling existing modeling workflows, which could be resource-intensive."
   },
   {
-    "objectID": "decisions/20240710-platform-focus-on-pcvr-and-web.html#in-core-and-done-by-us",
-    "href": "decisions/20240710-platform-focus-on-pcvr-and-web.html#in-core-and-done-by-us",
-    "title": "Proposed: Focus on PCVR and the Web",
+    "objectID": "decisions/20231226-furniture-vs-organic.html#alternatives",
+    "href": "decisions/20231226-furniture-vs-organic.html#alternatives",
+    "title": "Proposed: Hardsurface vs Organic",
     "section": "",
-    "text": "This proposal aligns with our core values of inclusivity and innovation and will be implemented by our team."
+    "text": "Ignoring the optimization could result in suboptimal performance, impacting the user experience and the scalability of V-Sekai projects."
   },
   {
-    "objectID": "decisions/20240710-platform-focus-on-pcvr-and-web.html#status",
-    "href": "decisions/20240710-platform-focus-on-pcvr-and-web.html#status",
-    "title": "Proposed: Focus on PCVR and the Web",
+    "objectID": "decisions/20231226-furniture-vs-organic.html#special-considerations",
+    "href": "decisions/20231226-furniture-vs-organic.html#special-considerations",
+    "title": "Proposed: Hardsurface vs Organic",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "Rare or unique objects and characters that require a departure from standard optimization practices to maintain their distinctiveness or functionality."
   },
   {
-    "objectID": "decisions/20240710-platform-focus-on-pcvr-and-web.html#decision-makers",
-    "href": "decisions/20240710-platform-focus-on-pcvr-and-web.html#decision-makers",
-    "title": "Proposed: Focus on PCVR and the Web",
+    "objectID": "decisions/20231226-furniture-vs-organic.html#implementation",
+    "href": "decisions/20231226-furniture-vs-organic.html#implementation",
+    "title": "Proposed: Hardsurface vs Organic",
     "section": "",
-    "text": "V-Sekai development team\nFire"
+    "text": "The proposal recommends integrating these optimization practices into the core development workflow of V-Sekai, handled by the internal team."
   },
   {
-    "objectID": "decisions/20240710-platform-focus-on-pcvr-and-web.html#tags",
-    "href": "decisions/20240710-platform-focus-on-pcvr-and-web.html#tags",
-    "title": "Proposed: Focus on PCVR and the Web",
+    "objectID": "decisions/20231226-furniture-vs-organic.html#references",
+    "href": "decisions/20231226-furniture-vs-organic.html#references",
+    "title": "Proposed: Hardsurface vs Organic",
     "section": "",
-    "text": "V-Sekai"
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis proposal was assisted by Aria, an AI assistant."
   },
   {
-    "objectID": "decisions/20240710-platform-focus-on-pcvr-and-web.html#further-reading",
-    "href": "decisions/20240710-platform-focus-on-pcvr-and-web.html#further-reading",
-    "title": "Proposed: Focus on PCVR and the Web",
+    "objectID": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html",
+    "href": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html",
+    "title": "Accepted: Create an upstream pull request for all non-V-Sekai related patches",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "Status: accepted \nDeciders: V-Sekai,fire,lyuma,\nTags: V-Sekai,\n\n\n\nWe use a gitassembler script, but the list may diverge from Godot Engine master.\nThese critical changes need to be synced with Godot Engine organization.\n\n\n\nNon-V-Sekai related and upstreamable godot patches should be filed as upstream PRs.\nThis makes Godot Engine core and V-Sekai better because changes are synchronized.\n\n\n\nHere is an example .gitassembly:\nstage groups-web-4.x remotes/v-sekai-godot/master\nmerge groups-web-4.x remotes/lyuma/gltf_shapes_8bones\nmerge groups-web-4.x remotes/v-sekai-godot/ninja-ccache\nNeed to check every line in the list using a comparison link:\n\nhttps://github.com/godotengine/godot/compare/master…lyuma:gltf_shapes_8bones\nhttps://github.com/godotengine/godot/compare/master…v-sekai-godot:ninja-ccache\n\nMake a corresponding pull request on https://github.com/godotengine/godot/pulls if there isn’t one.\nIf not possible, or non-upstreamable (for example, V-Sekai related), leave a comment in the .gitassembly why one cannot create a Godot Engine organization pull request.\n\n\n\n\nsynced\neasier maintenance\n\n\n\n\n\nneed to pay cost of bureaucracy\n\n\n\n\n\nOption: do nothing\nRejection Reason: V-Sekai and Godot Engine organization diverge\n\n\n\n\nNot a few lines of code.\n\n\n\nGodot Engine code is core.\n\n\n\n\nhttps://github.com/godotengine/godot\nhttps://github.com/v-sekai/godot\nhttps://www.thregr.org/~wavexx/software/git-assembler/\n\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240121-mac-setup.html",
-    "href": "decisions/20240121-mac-setup.html",
-    "title": "Proposed: Macos cicd setup.",
+    "objectID": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html#context-and-problem-statement",
+    "href": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html#context-and-problem-statement",
+    "title": "Accepted: Create an upstream pull request for all non-V-Sekai related patches",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai Core Team\nTags: Documentation, Automation, GoCD, Continuous Integration\n\n\n\n\nV-Sekai, a community-driven project aimed at developing social VR functionality for the Godot Engine, is experiencing growing pains due to increased contributions and complexity. There’s an apparent need to streamline development processes and ensure reliable automation in build and deployment workflows.\n\n\n\nThe current manual setup of development environments, especially continuous integration (CI) agents, is time-consuming and error-prone. The process lacks documentation, which creates barriers for new contributors and limits the scalability of the existing CI infrastructure.\n\n\n\nTo address these challenges, we propose to document the process thoroughly and automate the setup of GoCD agents, particularly for macOS environments, to facilitate smoother onboarding and reduce setup discrepancies.\n\n\nHere’s a step-by-step guide to setting up a GoCD agent service and configuring it to automatically start up on boot on a Mac.\n\n\n\nBoot your freshly reset or newly bought Mac.\nProceed with the initial setup, creating a user account as prompted by the macOS setup wizard.\n\n\n\n\ncd go-agent-20.5.0\nsudo xattr -d -r com.apple.quarantine .\n\n\n\n\nHandle Single Sign-On (SSO) if necessary.\n\n\n\n\n\nLog in with your Apple ID and download Xcode from the App Store.\n\n\n\n\n\nInstall Homebrew and the command line developer tools.\n/bin/bash -c \"$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh)\"\n\n\n\n\n\nInstall the GoCD agent via Homebrew or download from the GoCD website.\n\n\n\n\n\nEdit wrapper-properties.conf to configure your GoCD server URL and additional preferences.\n\n\n\n\n\nUpdate the server URL to https://ci.v-sekai.cloud/go.\n\n\n\n\n\nCreate a launch daemon for automatic startup on boot using the following commands:\nsudo tee /Library/LaunchDaemons/com.gocd.agent.plist &lt;&lt;EOF\n&lt;?xml version=\"1.0\" encoding=\"UTF-8\"?&gt;\n&lt;!DOCTYPE plist PUBLIC \"-//Apple//DTD PLIST 1.0//EN\" \"http://www.apple.com/DTDs/PropertyList-1.0.dtd\"&gt;\n&lt;plist version=\"1.0\"&gt;\n&lt;dict&gt;\n    &lt;key&gt;Label&lt;/key&gt;\n    &lt;string&gt;com.gocd.agent&lt;/string&gt;\n    &lt;key&gt;ProgramArguments&lt;/key&gt;\n    &lt;array&gt;\n        &lt;string&gt;/Users/fire/go-agent-23.5.0/bin/go-agent&lt;/string&gt;\n        &lt;string&gt;start&lt;/string&gt;\n    &lt;/array&gt;\n    &lt;key&gt;RunAtLoad&lt;/key&gt;\n    &lt;true/&gt;\n    &lt;key&gt;KeepAlive&lt;/key&gt;\n    &lt;true/&gt;\n&lt;/dict&gt;\n&lt;/plist&gt;\nEOF\nsudo launchctl load /Library/LaunchDaemons/com.gocd.agent.plist\nsudo launchctl list | grep com.gocd.agent\nReplace /Users/fire/go-agent-23.5.0 with the actual path where the binary resides.\nVerify that the agent starts upon boot.\n\nYour GoCD agent should now automatically start up whenever your Mac boots up.\n\n\n\n\n\nAutomating the setup of the GoCD agents substantially minimizes the potential for human error during configuration. It also speeds up the onboarding process for new developers and maintains consistency across multiple setups.\n\n\n\nThe main downside is the initial investment in time and resources required to document and test the automation scripts. Additionally, there is a reliance on macOS-specific services, which could alienate potential contributors who do not have access to a Mac.\n\n\n\nAlternatively, we considered using different CI services, like GitHub Actions or GitLab CI, but decided against it due to GoCD’s robustness and flexibility fitting V-Sekai’s needs more closely.\n\n\n\nWe recognize that not all contributors will require a local GoCD agent setup. However, for those involved in CI pipeline management or requiring a mirrored development environment, this will be invaluable.\n\n\n\nThis proposal suggests that the task be managed internally by the core V-Sekai team to maintain control over critical infrastructure components.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community.\nV-Sekai/v-sekai-game - GitHub repository for the V-Sekai game.\n\nAI assistant Aria assisted with this article."
+    "text": "We use a gitassembler script, but the list may diverge from Godot Engine master.\nThese critical changes need to be synced with Godot Engine organization."
   },
   {
-    "objectID": "decisions/20240121-mac-setup.html#metadata",
-    "href": "decisions/20240121-mac-setup.html#metadata",
-    "title": "Proposed: Macos cicd setup.",
+    "objectID": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Accepted: Create an upstream pull request for all non-V-Sekai related patches",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai Core Team\nTags: Documentation, Automation, GoCD, Continuous Integration"
+    "text": "Non-V-Sekai related and upstreamable godot patches should be filed as upstream PRs.\nThis makes Godot Engine core and V-Sekai better because changes are synchronized."
   },
   {
-    "objectID": "decisions/20240121-mac-setup.html#the-backdrop",
-    "href": "decisions/20240121-mac-setup.html#the-backdrop",
-    "title": "Proposed: Macos cicd setup.",
+    "objectID": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Accepted: Create an upstream pull request for all non-V-Sekai related patches",
     "section": "",
-    "text": "V-Sekai, a community-driven project aimed at developing social VR functionality for the Godot Engine, is experiencing growing pains due to increased contributions and complexity. There’s an apparent need to streamline development processes and ensure reliable automation in build and deployment workflows."
+    "text": "Here is an example .gitassembly:\nstage groups-web-4.x remotes/v-sekai-godot/master\nmerge groups-web-4.x remotes/lyuma/gltf_shapes_8bones\nmerge groups-web-4.x remotes/v-sekai-godot/ninja-ccache\nNeed to check every line in the list using a comparison link:\n\nhttps://github.com/godotengine/godot/compare/master…lyuma:gltf_shapes_8bones\nhttps://github.com/godotengine/godot/compare/master…v-sekai-godot:ninja-ccache\n\nMake a corresponding pull request on https://github.com/godotengine/godot/pulls if there isn’t one.\nIf not possible, or non-upstreamable (for example, V-Sekai related), leave a comment in the .gitassembly why one cannot create a Godot Engine organization pull request."
   },
   {
-    "objectID": "decisions/20240121-mac-setup.html#the-challenge",
-    "href": "decisions/20240121-mac-setup.html#the-challenge",
-    "title": "Proposed: Macos cicd setup.",
+    "objectID": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html#positive-consequences",
+    "href": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html#positive-consequences",
+    "title": "Accepted: Create an upstream pull request for all non-V-Sekai related patches",
     "section": "",
-    "text": "The current manual setup of development environments, especially continuous integration (CI) agents, is time-consuming and error-prone. The process lacks documentation, which creates barriers for new contributors and limits the scalability of the existing CI infrastructure."
+    "text": "synced\neasier maintenance"
   },
   {
-    "objectID": "decisions/20240121-mac-setup.html#the-strategy",
-    "href": "decisions/20240121-mac-setup.html#the-strategy",
-    "title": "Proposed: Macos cicd setup.",
+    "objectID": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html#negative-consequences",
+    "href": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html#negative-consequences",
+    "title": "Accepted: Create an upstream pull request for all non-V-Sekai related patches",
     "section": "",
-    "text": "To address these challenges, we propose to document the process thoroughly and automate the setup of GoCD agents, particularly for macOS environments, to facilitate smoother onboarding and reduce setup discrepancies.\n\n\nHere’s a step-by-step guide to setting up a GoCD agent service and configuring it to automatically start up on boot on a Mac.\n\n\n\nBoot your freshly reset or newly bought Mac.\nProceed with the initial setup, creating a user account as prompted by the macOS setup wizard.\n\n\n\n\ncd go-agent-20.5.0\nsudo xattr -d -r com.apple.quarantine .\n\n\n\n\nHandle Single Sign-On (SSO) if necessary.\n\n\n\n\n\nLog in with your Apple ID and download Xcode from the App Store.\n\n\n\n\n\nInstall Homebrew and the command line developer tools.\n/bin/bash -c \"$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh)\"\n\n\n\n\n\nInstall the GoCD agent via Homebrew or download from the GoCD website.\n\n\n\n\n\nEdit wrapper-properties.conf to configure your GoCD server URL and additional preferences.\n\n\n\n\n\nUpdate the server URL to https://ci.v-sekai.cloud/go.\n\n\n\n\n\nCreate a launch daemon for automatic startup on boot using the following commands:\nsudo tee /Library/LaunchDaemons/com.gocd.agent.plist &lt;&lt;EOF\n&lt;?xml version=\"1.0\" encoding=\"UTF-8\"?&gt;\n&lt;!DOCTYPE plist PUBLIC \"-//Apple//DTD PLIST 1.0//EN\" \"http://www.apple.com/DTDs/PropertyList-1.0.dtd\"&gt;\n&lt;plist version=\"1.0\"&gt;\n&lt;dict&gt;\n    &lt;key&gt;Label&lt;/key&gt;\n    &lt;string&gt;com.gocd.agent&lt;/string&gt;\n    &lt;key&gt;ProgramArguments&lt;/key&gt;\n    &lt;array&gt;\n        &lt;string&gt;/Users/fire/go-agent-23.5.0/bin/go-agent&lt;/string&gt;\n        &lt;string&gt;start&lt;/string&gt;\n    &lt;/array&gt;\n    &lt;key&gt;RunAtLoad&lt;/key&gt;\n    &lt;true/&gt;\n    &lt;key&gt;KeepAlive&lt;/key&gt;\n    &lt;true/&gt;\n&lt;/dict&gt;\n&lt;/plist&gt;\nEOF\nsudo launchctl load /Library/LaunchDaemons/com.gocd.agent.plist\nsudo launchctl list | grep com.gocd.agent\nReplace /Users/fire/go-agent-23.5.0 with the actual path where the binary resides.\nVerify that the agent starts upon boot.\n\nYour GoCD agent should now automatically start up whenever your Mac boots up."
+    "text": "need to pay cost of bureaucracy"
   },
   {
-    "objectID": "decisions/20240121-mac-setup.html#the-upside",
-    "href": "decisions/20240121-mac-setup.html#the-upside",
-    "title": "Proposed: Macos cicd setup.",
+    "objectID": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html#option-graveyard",
+    "href": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html#option-graveyard",
+    "title": "Accepted: Create an upstream pull request for all non-V-Sekai related patches",
     "section": "",
-    "text": "Automating the setup of the GoCD agents substantially minimizes the potential for human error during configuration. It also speeds up the onboarding process for new developers and maintains consistency across multiple setups."
+    "text": "Option: do nothing\nRejection Reason: V-Sekai and Godot Engine organization diverge"
   },
   {
-    "objectID": "decisions/20240121-mac-setup.html#the-downside",
-    "href": "decisions/20240121-mac-setup.html#the-downside",
-    "title": "Proposed: Macos cicd setup.",
+    "objectID": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Accepted: Create an upstream pull request for all non-V-Sekai related patches",
     "section": "",
-    "text": "The main downside is the initial investment in time and resources required to document and test the automation scripts. Additionally, there is a reliance on macOS-specific services, which could alienate potential contributors who do not have access to a Mac."
+    "text": "Not a few lines of code."
   },
   {
-    "objectID": "decisions/20240121-mac-setup.html#the-road-not-taken",
-    "href": "decisions/20240121-mac-setup.html#the-road-not-taken",
-    "title": "Proposed: Macos cicd setup.",
+    "objectID": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Accepted: Create an upstream pull request for all non-V-Sekai related patches",
     "section": "",
-    "text": "Alternatively, we considered using different CI services, like GitHub Actions or GitLab CI, but decided against it due to GoCD’s robustness and flexibility fitting V-Sekai’s needs more closely."
+    "text": "Godot Engine code is core."
   },
   {
-    "objectID": "decisions/20240121-mac-setup.html#the-infrequent-use-case",
-    "href": "decisions/20240121-mac-setup.html#the-infrequent-use-case",
-    "title": "Proposed: Macos cicd setup.",
+    "objectID": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html#references",
+    "href": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html#references",
+    "title": "Accepted: Create an upstream pull request for all non-V-Sekai related patches",
     "section": "",
-    "text": "We recognize that not all contributors will require a local GoCD agent setup. However, for those involved in CI pipeline management or requiring a mirrored development environment, this will be invaluable."
+    "text": "https://github.com/godotengine/godot\nhttps://github.com/v-sekai/godot\nhttps://www.thregr.org/~wavexx/software/git-assembler/"
   },
   {
-    "objectID": "decisions/20240121-mac-setup.html#in-core-and-done-by-us",
-    "href": "decisions/20240121-mac-setup.html#in-core-and-done-by-us",
-    "title": "Proposed: Macos cicd setup.",
+    "objectID": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html#derivative-license",
+    "href": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html#derivative-license",
+    "title": "Accepted: Create an upstream pull request for all non-V-Sekai related patches",
     "section": "",
-    "text": "This proposal suggests that the task be managed internally by the core V-Sekai team to maintain control over critical infrastructure components."
+    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240121-mac-setup.html#further-reading",
-    "href": "decisions/20240121-mac-setup.html#further-reading",
-    "title": "Proposed: Macos cicd setup.",
+    "objectID": "decisions/20240528-pipeline-godot-wasm-importer.html",
+    "href": "decisions/20240528-pipeline-godot-wasm-importer.html",
+    "title": "Proposed: Godot Engine as Wasm Importer",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community.\nV-Sekai/v-sekai-game - GitHub repository for the V-Sekai game.\n\nAI assistant Aria assisted with this article."
+    "text": "There are concerns regarding the security of gltf and fbx document code in Godot Engine.\n\n\n\nThe current implementation of gltf and fbx document code in Godot Engine may pose potential security risks.\n\n\n\nThe proposal is to compile Godot Engine as wasm and run the wasm workers in batch on the incoming files. This can be achieved without the need for node, using Rustler + wasmtime.\n1. Compile Godot Engine as wasm\n2. Run wasm workers on incoming files\n\n\n\n\nEnhanced security for gltf and fbx document code.\nEfficient handling of incoming files.\n\n\n\n\n\nPotential increase in complexity due to the introduction of wasm.\nPossible performance overhead from running wasm workers.\n\n\n\n\nAn additional layer of Godot Engine text scene and text resource to JSON could be implemented to avoid parsing errors.\n\n\n\nThis solution might not be beneficial for smaller projects or those that do not use gltf and fbx document code extensively.\n\n\n\nThis proposal involves core changes to the Godot Engine and will be implemented by the V-Sekai development team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team, Fire, Benbot\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nElixi Nodejs\norb-runtime to run wasm\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20211103-use-platform-called-vfx-reference-platform.html",
-    "href": "decisions/20211103-use-platform-called-vfx-reference-platform.html",
-    "title": "Draft: Use a standard reference platform called VFX Reference platform",
+    "objectID": "decisions/20240528-pipeline-godot-wasm-importer.html#the-context",
+    "href": "decisions/20240528-pipeline-godot-wasm-importer.html#the-context",
+    "title": "Proposed: Godot Engine as Wasm Importer",
     "section": "",
-    "text": "Status: draft \nDeciders: V-Sekai,fire,\nTags: V-Sekai,\n\n\n\n\n[A standard reference platform’s purpose is to] minimize incompatibilities between different software packages, ease the support burden for Linux-based pipelines and encourage further adoption of Linux by software vendors.\n\nHere are some problems:\n\nWe want to keep a consistent server configuration setup.\nWe want creators to have a consistent work environment.\n\n\n\n\n\nThe VFX Reference #platform is a set of tool and library versions to be used as a common target #platform for building software for the VFX industry. Its purpose is to minimize incompatibilities between different software packages, ease the support burden for Linux-based pipelines and encourage further adoption of Linux by software vendors. The Reference #platform is updated annually by a group of software vendors in collaboration with the Visual Effects Society Technology Committee.\n\n\n\n\n\nFind candidate centos-like platforms.\nA candidate is Rocky Linux.\n\n\n\n\n\nThe problems with #platform are informed by decisions of others in the industry.\n\n\n\n\n\nGoing outside the #platform is risky.\n\n\n\n\n\nOption: Use Rocky Linux directly\nRejection Reason: No collaboration\nOption: Use Fedora 35 directly\nRejection Reason: Unclear support lifetime.\n\n\n\n\nThis is a devops proposal, not a coding proposal.\n\n\n\nWe do have to choose a reference #platform even if we don’t think about it to upload to docker.\n\n\n\n\nhttps://vfxplatform.com/\nhttps://hub.docker.com/u/aswf\nhttps://hub.docker.com/r/aswf/ci-base\nhttps://github.com/AcademySoftwareFoundation/aswf-docker/tree/master/ci-base\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "There are concerns regarding the security of gltf and fbx document code in Godot Engine."
   },
   {
-    "objectID": "decisions/20211103-use-platform-called-vfx-reference-platform.html#context-and-problem-statement",
-    "href": "decisions/20211103-use-platform-called-vfx-reference-platform.html#context-and-problem-statement",
-    "title": "Draft: Use a standard reference platform called VFX Reference platform",
+    "objectID": "decisions/20240528-pipeline-godot-wasm-importer.html#the-problem-statement",
+    "href": "decisions/20240528-pipeline-godot-wasm-importer.html#the-problem-statement",
+    "title": "Proposed: Godot Engine as Wasm Importer",
     "section": "",
-    "text": "[A standard reference platform’s purpose is to] minimize incompatibilities between different software packages, ease the support burden for Linux-based pipelines and encourage further adoption of Linux by software vendors.\n\nHere are some problems:\n\nWe want to keep a consistent server configuration setup.\nWe want creators to have a consistent work environment."
+    "text": "The current implementation of gltf and fbx document code in Godot Engine may pose potential security risks."
   },
   {
-    "objectID": "decisions/20211103-use-platform-called-vfx-reference-platform.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20211103-use-platform-called-vfx-reference-platform.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Draft: Use a standard reference platform called VFX Reference platform",
+    "objectID": "decisions/20240528-pipeline-godot-wasm-importer.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240528-pipeline-godot-wasm-importer.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Godot Engine as Wasm Importer",
     "section": "",
-    "text": "The VFX Reference #platform is a set of tool and library versions to be used as a common target #platform for building software for the VFX industry. Its purpose is to minimize incompatibilities between different software packages, ease the support burden for Linux-based pipelines and encourage further adoption of Linux by software vendors. The Reference #platform is updated annually by a group of software vendors in collaboration with the Visual Effects Society Technology Committee."
+    "text": "The proposal is to compile Godot Engine as wasm and run the wasm workers in batch on the incoming files. This can be achieved without the need for node, using Rustler + wasmtime.\n1. Compile Godot Engine as wasm\n2. Run wasm workers on incoming files"
   },
   {
-    "objectID": "decisions/20211103-use-platform-called-vfx-reference-platform.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20211103-use-platform-called-vfx-reference-platform.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Draft: Use a standard reference platform called VFX Reference platform",
+    "objectID": "decisions/20240528-pipeline-godot-wasm-importer.html#the-benefits",
+    "href": "decisions/20240528-pipeline-godot-wasm-importer.html#the-benefits",
+    "title": "Proposed: Godot Engine as Wasm Importer",
     "section": "",
-    "text": "Find candidate centos-like platforms.\nA candidate is Rocky Linux."
+    "text": "Enhanced security for gltf and fbx document code.\nEfficient handling of incoming files."
   },
   {
-    "objectID": "decisions/20211103-use-platform-called-vfx-reference-platform.html#positive-consequences",
-    "href": "decisions/20211103-use-platform-called-vfx-reference-platform.html#positive-consequences",
-    "title": "Draft: Use a standard reference platform called VFX Reference platform",
+    "objectID": "decisions/20240528-pipeline-godot-wasm-importer.html#the-downsides",
+    "href": "decisions/20240528-pipeline-godot-wasm-importer.html#the-downsides",
+    "title": "Proposed: Godot Engine as Wasm Importer",
     "section": "",
-    "text": "The problems with #platform are informed by decisions of others in the industry."
+    "text": "Potential increase in complexity due to the introduction of wasm.\nPossible performance overhead from running wasm workers."
   },
   {
-    "objectID": "decisions/20211103-use-platform-called-vfx-reference-platform.html#negative-consequences",
-    "href": "decisions/20211103-use-platform-called-vfx-reference-platform.html#negative-consequences",
-    "title": "Draft: Use a standard reference platform called VFX Reference platform",
+    "objectID": "decisions/20240528-pipeline-godot-wasm-importer.html#the-road-not-taken",
+    "href": "decisions/20240528-pipeline-godot-wasm-importer.html#the-road-not-taken",
+    "title": "Proposed: Godot Engine as Wasm Importer",
     "section": "",
-    "text": "Going outside the #platform is risky."
+    "text": "An additional layer of Godot Engine text scene and text resource to JSON could be implemented to avoid parsing errors."
   },
   {
-    "objectID": "decisions/20211103-use-platform-called-vfx-reference-platform.html#option-graveyard",
-    "href": "decisions/20211103-use-platform-called-vfx-reference-platform.html#option-graveyard",
-    "title": "Draft: Use a standard reference platform called VFX Reference platform",
+    "objectID": "decisions/20240528-pipeline-godot-wasm-importer.html#the-infrequent-use-case",
+    "href": "decisions/20240528-pipeline-godot-wasm-importer.html#the-infrequent-use-case",
+    "title": "Proposed: Godot Engine as Wasm Importer",
     "section": "",
-    "text": "Option: Use Rocky Linux directly\nRejection Reason: No collaboration\nOption: Use Fedora 35 directly\nRejection Reason: Unclear support lifetime."
+    "text": "This solution might not be beneficial for smaller projects or those that do not use gltf and fbx document code extensively."
   },
   {
-    "objectID": "decisions/20211103-use-platform-called-vfx-reference-platform.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20211103-use-platform-called-vfx-reference-platform.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Draft: Use a standard reference platform called VFX Reference platform",
+    "objectID": "decisions/20240528-pipeline-godot-wasm-importer.html#in-core-and-done-by-us",
+    "href": "decisions/20240528-pipeline-godot-wasm-importer.html#in-core-and-done-by-us",
+    "title": "Proposed: Godot Engine as Wasm Importer",
     "section": "",
-    "text": "This is a devops proposal, not a coding proposal."
+    "text": "This proposal involves core changes to the Godot Engine and will be implemented by the V-Sekai development team."
   },
   {
-    "objectID": "decisions/20211103-use-platform-called-vfx-reference-platform.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20211103-use-platform-called-vfx-reference-platform.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Draft: Use a standard reference platform called VFX Reference platform",
+    "objectID": "decisions/20240528-pipeline-godot-wasm-importer.html#status",
+    "href": "decisions/20240528-pipeline-godot-wasm-importer.html#status",
+    "title": "Proposed: Godot Engine as Wasm Importer",
     "section": "",
-    "text": "We do have to choose a reference #platform even if we don’t think about it to upload to docker."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20211103-use-platform-called-vfx-reference-platform.html#references",
-    "href": "decisions/20211103-use-platform-called-vfx-reference-platform.html#references",
-    "title": "Draft: Use a standard reference platform called VFX Reference platform",
+    "objectID": "decisions/20240528-pipeline-godot-wasm-importer.html#decision-makers",
+    "href": "decisions/20240528-pipeline-godot-wasm-importer.html#decision-makers",
+    "title": "Proposed: Godot Engine as Wasm Importer",
     "section": "",
-    "text": "https://vfxplatform.com/\nhttps://hub.docker.com/u/aswf\nhttps://hub.docker.com/r/aswf/ci-base\nhttps://github.com/AcademySoftwareFoundation/aswf-docker/tree/master/ci-base"
+    "text": "V-Sekai development team, Fire, Benbot"
   },
   {
-    "objectID": "decisions/20211103-use-platform-called-vfx-reference-platform.html#derivative-license",
-    "href": "decisions/20211103-use-platform-called-vfx-reference-platform.html#derivative-license",
-    "title": "Draft: Use a standard reference platform called VFX Reference platform",
+    "objectID": "decisions/20240528-pipeline-godot-wasm-importer.html#tags",
+    "href": "decisions/20240528-pipeline-godot-wasm-importer.html#tags",
+    "title": "Proposed: Godot Engine as Wasm Importer",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html",
-    "href": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html",
-    "title": "Accepted: To make it easier to upload V-Sekai maps and Avatars use Godot Engine 4 script templates.",
+    "objectID": "decisions/20240528-pipeline-godot-wasm-importer.html#further-reading",
+    "href": "decisions/20240528-pipeline-godot-wasm-importer.html#further-reading",
+    "title": "Proposed: Godot Engine as Wasm Importer",
     "section": "",
-    "text": "Status: accepted \nDeciders: V-Sekai,fire,saracen\nTags: V-Sekai,\n\n\n\nUploading V-Sekai maps and Avatars is complicated.\n\n\n\nUse the new Godot Engine feature of script templates to make it easier to upload.\n\n\n\n\nCreate a template for Avatars\nCreate a template for maps\n\n\n\n\n\nLess steps to upload.\n\n\n\n\n\nLoss of knowledge of how the tools work.\n\n\n\n\n\nOption: Status quo.\nRejection Reason: Too many steps are currently needed.\n\n\n\n\nNot a few lines of script.\n\n\n\nWe control the core application flow.\n\n\n\n\nhttps://github.com/godotengine/godot/pull/53957\n\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nElixi Nodejs\norb-runtime to run wasm\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html#context-and-problem-statement",
-    "href": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html#context-and-problem-statement",
-    "title": "Accepted: To make it easier to upload V-Sekai maps and Avatars use Godot Engine 4 script templates.",
+    "objectID": "decisions/20230911-xpr.exs.html",
+    "href": "decisions/20230911-xpr.exs.html",
+    "title": "Draft: XPR in Elixir",
     "section": "",
-    "text": "Uploading V-Sekai maps and Avatars is complicated."
+    "text": "Draft: XPR in Elixir\ndefmodule AveragableLerpable do\n  @callback average(a :: any(), b :: any(), t :: number()) :: any()\n  @callback lerp(a :: any(), b :: any(), t :: number()) :: any()\n  @callback spherical_interpolate(a :: any(), b :: any(), t :: number()) :: any()\n  @callback spherical_cubic_interpolate(a :: any(), b :: any(), c :: any(), d :: any(), t1 :: number(), t2 :: number(), t3 :: number(), t4 :: number()) :: any()\n  @callback cubic_interpolate(a :: any(), b :: any(), c :: any(), d :: any(), t1 :: number(), t2 :: number(), t3 :: number(), t4 :: number()) :: any()\nend\n\ndefmodule Rotation6D do\n  @behavior AveragableLerpable\n\n  defstruct [:x1, :y1, :z1, :x2, :y2, :z2]\n\n  # Implement the required methods here\nend\n\ndefmodule Position3D do\n  @behavior AveragableLerpable\n\n  defstruct [:x, :y, :z]\n\n  # Implement the required methods here\nend\n\ndefmodule LightCone do\n  @type t :: %{\n          count: [AveragableLerpable.t()],\n          accumulate: [function()],\n          array: [AveragableLerpable.t()],\n          set: MapSet.t(any())\n        }\nend\n\n@type event ::\n        {:expand}\n        | {:superposition}\n        | {:spacetime_bubble}\n        | {:light_cone}\n        | {:collapse}\n        | {:avg_lerp}\n        | {:plus}\n        | {:union}\n\ndefmodule PropagateFilter do\n  use Membrane.Filter\n\n  @impl true\n  def handle_init(_) do\n    {:ok, %{}}\n  end\n\n  @impl true\n  def handle_demand(:output, size, :buffers, _ctx) do\n    {{:ok, demand: {:input, size}}, %{}}\n  end\n\n  @impl true\n  def handle_process(:input, buffer, _ctx) do\n    # Process the input data and generate the output data\n    output_data = process(buffer.payload)\n\n    # Create a new buffer with the output data\n    output_buffer = %Membrane.Buffer{payload: output_data}\n\n    {{:ok, buffer: {:output, output_buffer}}, %{}}\n  end\n\n  defp process(input_data) do\n    # Implement your processing logic here\n    # For example, if input_data is a list of numbers, you can calculate their sum:\n    Enum.reduce(input_data, 0, &(&1 + &2))\n  end\nend\n\n\ndefmodule XprPipeline do\n  use Membrane.Pipeline\n\n  alias Membrane.Element.Tee.Master\n  alias Membrane.Element.Funnel\n  alias Membrane.Element.Clock\n\n  @impl true\n  def handle_init(_) do\n    children = [\n      clock: Clock,\n      light_cone: LightConeElement,\n      expanding: ExpandingElement,\n      collapsing: CollapsingElement,\n      reduce: ReduceElement,\n      update: UpdateElement,\n      tee: Master,\n      funnel: Funnel,\n      propagate: PropagateFilter\n    ]\n\n    links = [\n      link(:clock)\n      |&gt; via_out(:tick, options: [interval: 1000]) # Adjust the interval as needed\n      |&gt; to(:tee)\n      |&gt; to(:expanding)\n      |&gt; to(:light_cone)\n      |&gt; to(:collapsing)\n      |&gt; to(:reduce)\n      |&gt; to(:propagate)\n      |&gt; to(:funnel)\n      |&gt; to(:update)\n    ]\n\n    {{:ok, %ParentSpec{children: children, links: links}}, %{}}\n  end\nend"
   },
   {
-    "objectID": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Accepted: To make it easier to upload V-Sekai maps and Avatars use Godot Engine 4 script templates.",
+    "objectID": "decisions/20211031-construct-the-virtual-world.html",
+    "href": "decisions/20211031-construct-the-virtual-world.html",
+    "title": "Proposed: Construct the virtual #world",
     "section": "",
-    "text": "Use the new Godot Engine feature of script templates to make it easier to upload."
+    "text": "Proposed: Construct the virtual #world\n\nContext and Problem Statement\nIt’s hard to create the virtual world.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nUse a way to create 3d in a virtual world.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n\npacked scenes\nblockmesh\ncassie\nSpark joy.\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot trivial.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nI know how to do this.\n\n\nReferences\n\nCASSIE\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Accepted: To make it easier to upload V-Sekai maps and Avatars use Godot Engine 4 script templates.",
+    "objectID": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html",
+    "href": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html",
+    "title": "Accepted: Avoid avatar breaking by following quality checklist",
     "section": "",
-    "text": "Create a template for Avatars\nCreate a template for maps"
+    "text": "Status: accepted \nDeciders: V-Sekai,fire,\nTags: V-Sekai,\n\n\n\nAvoid avatar breaking which harmful to the person using the avatar.\n\n\n\nCreate a checklist to ensure quality.\n\n\n\nThis is defined for a VRM character.\n\nAdd a root bone\nAge height normalization to 1.59m for an Asian adult female.\nAuto generate spring bones via https://fujisunflower.booth.pm/items/2087178\nCheck eyes\nCheck Jaws\nAdjust spring bones limits\nCheck transparent glasses etc.\nRun mesh mush at 80 degrees twist on all vertices\nCheck culling locations\nMatch shade and base color in MTOON1\nThe relative angle between the Hips and the Thigh should something that works for inverse kinematics.\nCheck manifolds for skin breaking\n\nMove the feet to the origin of the scene\n\nCursor to world origin\nChange to origin\nMove to below feet\nMove object origin to origin\n\nCheck if environment lighting breaks the avatar\n\nChange sky temperature to the brightest\ntest 0.00001 light intensity\ntest 16 light intensity\n\nHow to make a Portrait of the head photo?\n\nE96E66 background color\n16 light intensity and camera set to realistic focal length for a portrait makes the photo look good.\n\n\n\n\n\nLess avatar breaking.\n\n\n\n\n\nWork\n\n\n\n\n\nOption: Do nothing.\nRejection Reason: This is unacceptable to the people who use the avatars.\n\n\n\n\nThis can be automated in the future.\n\n\n\nThis is a guideline and we are in the area.\n\n\n\n\nVRM - 3D Avatar File Format for VR \n\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html#positive-consequences",
-    "href": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html#positive-consequences",
-    "title": "Accepted: To make it easier to upload V-Sekai maps and Avatars use Godot Engine 4 script templates.",
+    "objectID": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html#context-and-problem-statement",
+    "href": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html#context-and-problem-statement",
+    "title": "Accepted: Avoid avatar breaking by following quality checklist",
     "section": "",
-    "text": "Less steps to upload."
+    "text": "Avoid avatar breaking which harmful to the person using the avatar."
   },
   {
-    "objectID": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html#negative-consequences",
-    "href": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html#negative-consequences",
-    "title": "Accepted: To make it easier to upload V-Sekai maps and Avatars use Godot Engine 4 script templates.",
+    "objectID": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Accepted: Avoid avatar breaking by following quality checklist",
     "section": "",
-    "text": "Loss of knowledge of how the tools work."
+    "text": "Create a checklist to ensure quality."
   },
   {
-    "objectID": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html#option-graveyard",
-    "href": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html#option-graveyard",
-    "title": "Accepted: To make it easier to upload V-Sekai maps and Avatars use Godot Engine 4 script templates.",
+    "objectID": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Accepted: Avoid avatar breaking by following quality checklist",
     "section": "",
-    "text": "Option: Status quo.\nRejection Reason: Too many steps are currently needed."
+    "text": "This is defined for a VRM character.\n\nAdd a root bone\nAge height normalization to 1.59m for an Asian adult female.\nAuto generate spring bones via https://fujisunflower.booth.pm/items/2087178\nCheck eyes\nCheck Jaws\nAdjust spring bones limits\nCheck transparent glasses etc.\nRun mesh mush at 80 degrees twist on all vertices\nCheck culling locations\nMatch shade and base color in MTOON1\nThe relative angle between the Hips and the Thigh should something that works for inverse kinematics.\nCheck manifolds for skin breaking\n\nMove the feet to the origin of the scene\n\nCursor to world origin\nChange to origin\nMove to below feet\nMove object origin to origin\n\nCheck if environment lighting breaks the avatar\n\nChange sky temperature to the brightest\ntest 0.00001 light intensity\ntest 16 light intensity\n\nHow to make a Portrait of the head photo?\n\nE96E66 background color\n16 light intensity and camera set to realistic focal length for a portrait makes the photo look good."
   },
   {
-    "objectID": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Accepted: To make it easier to upload V-Sekai maps and Avatars use Godot Engine 4 script templates.",
+    "objectID": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html#positive-consequences",
+    "href": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html#positive-consequences",
+    "title": "Accepted: Avoid avatar breaking by following quality checklist",
     "section": "",
-    "text": "Not a few lines of script."
+    "text": "Less avatar breaking."
   },
   {
-    "objectID": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Accepted: To make it easier to upload V-Sekai maps and Avatars use Godot Engine 4 script templates.",
+    "objectID": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html#negative-consequences",
+    "href": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html#negative-consequences",
+    "title": "Accepted: Avoid avatar breaking by following quality checklist",
     "section": "",
-    "text": "We control the core application flow."
+    "text": "Work"
   },
   {
-    "objectID": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html#references",
-    "href": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html#references",
-    "title": "Accepted: To make it easier to upload V-Sekai maps and Avatars use Godot Engine 4 script templates.",
+    "objectID": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html#option-graveyard",
+    "href": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html#option-graveyard",
+    "title": "Accepted: Avoid avatar breaking by following quality checklist",
     "section": "",
-    "text": "https://github.com/godotengine/godot/pull/53957"
+    "text": "Option: Do nothing.\nRejection Reason: This is unacceptable to the people who use the avatars."
   },
   {
-    "objectID": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html#derivative-license",
-    "href": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html#derivative-license",
-    "title": "Accepted: To make it easier to upload V-Sekai maps and Avatars use Godot Engine 4 script templates.",
+    "objectID": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Accepted: Avoid avatar breaking by following quality checklist",
     "section": "",
-    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "This can be automated in the future."
   },
   {
-    "objectID": "decisions/20230429-v-sekai-roadmap.html",
-    "href": "decisions/20230429-v-sekai-roadmap.html",
-    "title": "Superseded: V-Sekai Roadmap and Goals 2023-04-20",
+    "objectID": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Accepted: Avoid avatar breaking by following quality checklist",
     "section": "",
-    "text": "Superseded: V-Sekai Roadmap and Goals 2023-04-20\n\nMetadata\n\nStatus: superseded by 20230516-v-sekai-roadmap.md \nDeciders: V-Sekai,fire,lyuma,\nTags: V-Sekai,chatgpt4 summary,\n\n\n\nContext and Problem Statement\nWhat is the V-Sekai Roadmap and Goals?\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nThe roadmap presented here is divided into three stages: short-term, mid-term, and long-term goals. Each stage builds upon the previous one, gradually expanding the project’s scope and capabilities.\n\n\nDescribe how your proposal will work with code, pseudo-code, mock-ups, or diagrams\ngraph LR\n\n  subgraph Short Term\n    A[Avatar Loading] --&gt; B1[Simple Demo with VRM Avatar]\n    A --&gt; B2[VRM & Unity Import - Maintain and Improve]\n    A --&gt; B3[Network Code Reconciliation - Godot Network System]\n    A --&gt; B4[Jitter in Network Interpolation]\n    A --&gt; B5[Implement jitter and playback buffer for Voice]\n  end\n\n  subgraph Mid Term\n    B4 --&gt; C[Network]\n    C --&gt; D1[Entity System & Background Loading]\n    C --&gt; D2[Background Loading - Re-evaluate with Multithreaded Scene Tree]\n    C --&gt; D3[UI Work - Fix VR UI & Improve Interaction]\n    C --&gt; D4[Lightweight Relay Instance Server - Single Process, Multiple Instances]\n  end\n\n  subgraph Long Term\n    D4 --&gt; E[Scalable Instances]\n    E --&gt; F1[Network Topology Implementation]\n    E --&gt; F2[Streamlined Content Creation - Better Workflow]\n    E --&gt; F3[Zero Stutter when Loading Content - Address Bottlenecks]\n    E --&gt; F4[Social and Upload Features - Enhance User Experience]\n    E --&gt; F5[Video and Audio Work - Streaming Integration]\n    E --&gt; F6[Scripting Integrations - WASM-based Scripts]\n    E --&gt; F7[UX Work for Non-Technical Users - Accessible UI]\n    E --&gt; F8[Loading VRM Avatars - Streamlined Process]\n    E --&gt; F9[In-Editor Content Building UX - Non-Technical Users]\n  end\nThe discussion involves the development of V-Sekai, a project with short-term, mid-term, and long-term goals. In the short term, the focus is on avatar loading, simple demos, VRM & Unity import, network code reconciliation, adding network interpolation, and voice jitter buffer. Mid-term goals include working on the network, entity system, background loading, UI improvements, and developing a lightweight relay instance server. Finally, long-term goals involve scalable instances, network topology implementation, streamlined content creation, zero stutter loading, enhancing social and upload features, video and music playback and live streaming, scripting integrations, UX work for non-technical users, and in-editor content building UX.\nOne challenge the project faces is maintaining and improving the existing codebase, which includes outdated workarounds from Godot 3. Another setback was the change from OpenVR to OpenXR. Content is another hurdle: transferring a world from other platforms to V-Sekai is currently best accomplished by exporting source assets such as glTF or FBX. The project aims to cater to non-technical users, making it more accessible than other platforms. WASM-based scripting is being considered, but there are concerns about implementation challenges and security.\nIn addition, the V-Sekai project needs a project manager, and the team struggles to find collaborators who share their vision and can dedicate enough time to contribute significantly. Nevertheless, despite the long list of features needed for basic functionality, the team believes that V-Sekai is essential for the future of the Metaverse space, and that will draw collaborators to assist on our common vision.\nIt’s important that our roadmap and goals continue to be discussed and iterated on. Nothing should be seen as final, since technology changes so rapidly and consensus is important.\n\n\nPositive Consequences\nWe can create V-Sekai easier.\n\n\nNegative Consequences\nOverhead might be hard.\n\n\nOption graveyard\n\nRelying on informal communication and ad-hoc collaboration\nContinuing with the current approach without a structured process\n\n\n\nIf this enhancement will be used infrequently, can it be worked around with a few lines of script?\nNo. This is a process.\n\n\nIs there a reason why this should be core and done by us?\nThis is a core process for V-Sekai.\n\n\nReferences\n\nV-Sekai"
+    "text": "This is a guideline and we are in the area."
   },
   {
-    "objectID": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html",
-    "href": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html",
-    "title": "Proposed: Train quad-based Meshgpt within constraints",
+    "objectID": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html#references",
+    "href": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html#references",
+    "title": "Accepted: Avoid avatar breaking by following quality checklist",
     "section": "",
-    "text": "The goal is to train a MeshGPT model for quad-based geometry with limited resources of one day using fixed Nvidia GPU hardware to evaluate its performance.\n\n\n\nDescribe a workflow for training Meshgpt with quad-based meshes to create a set of LODs (Level of Detail) within the given constraints.\n\n\n\n\nData Preparation: Collect a diverse dataset of quad-based meshes suitable for generating LODs. This involves cleaning and normalizing the data to ensure consistency and remove inconsistencies or errors. Categorizing the data based on complexity and size allows for targeted training and model performance evaluation across different mesh types. A requirement is to attribute every available source 3d model. Gather a dataset of quad-based meshes representing various objects within the distance range of interest.\nModel Architecture Selection: Choose an appropriate language model architecture to handle geometric data effectively. MeshGPT could be a good starting point due to its success in handling 3D mesh generation tasks.\nBatch Processing Technique: Implement a batch processing technique to optimize the use of GPU resources.\nHyperparameter Tuning: Fine-tune the hyperparameters, such as learning rate, batch size, and number of layers, to achieve optimal performance within the given time constraint. This may involve experimentation with different values and configurations to find the best setup for the chosen model architecture and dataset.\nTraining Process: Train the MeshGPT model using the prepared dataset with the chosen architecture, optimized batch processing technique, and fine-tuned hyperparameters for over one day. This involves monitoring the training process and making necessary adjustments to ensure optimal performance within the given timeframe.\nEvaluation: Evaluate the trained model’s performance by generating LODs for a diverse quad-based mesh and comparing them to ground truth data or existing LOD generation methods.\nResults Analysis: Analyze the results obtained from the evaluation stage, focusing on metrics such as accuracy, speed, and resource usage.\n\n\n\n\n\nEfficient utilization of Video RAM in training large language models for mesh generation tasks.\nAbility to train the MeshGPT model within a one-day timeframe.\nImproved LOD generation capabilities for quad-based meshes.\n\n\n\n\n\nLimited flexibility due to the constraint of Video RAM.\nTraining large language models can be computationally intensive and require significant processing power, potentially impacting system performance.\nRequires careful hyperparameter tuning for optimal results within the given timeframe.\n\n\n\n\n\nUsing less powerful hardware or smaller video RAM would result in longer training times or lower model capacity.\nOpting for a more complex model architecture without optimizations could lead to overfitting and poor performance on the LOD generation task.\n\n\n\n\nIn cases where more advanced GPU hardware is available, this workflow may not be necessary as it would allow for larger models or longer training times, potentially resulting in better performance. However, the proposed workflow can be a starting point for those with limited resources or time constraints.\n\n\n\n\nWorkflow design specifically tailored to train MeshGPT on quad-based meshes within one day using a fixed sized video RAM.\nHyperparameter tuning and optimization techniques are implemented to maximize performance under the given constraints.\n\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nRunpod\nMeshGPT with Quads\n\nAI assistant Aria assisted with this article."
+    "text": "VRM - 3D Avatar File Format for VR"
   },
   {
-    "objectID": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#the-context",
-    "href": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#the-context",
-    "title": "Proposed: Train quad-based Meshgpt within constraints",
+    "objectID": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html#derivative-license",
+    "href": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html#derivative-license",
+    "title": "Accepted: Avoid avatar breaking by following quality checklist",
     "section": "",
-    "text": "The goal is to train a MeshGPT model for quad-based geometry with limited resources of one day using fixed Nvidia GPU hardware to evaluate its performance."
+    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#the-problem-statement",
-    "href": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#the-problem-statement",
-    "title": "Proposed: Train quad-based Meshgpt within constraints",
+    "objectID": "decisions/20240502-mesh-object-sync-benchmark.html",
+    "href": "decisions/20240502-mesh-object-sync-benchmark.html",
+    "title": "Proposed: Stress Testing Godot Engine’s Networking System",
     "section": "",
-    "text": "Describe a workflow for training Meshgpt with quad-based meshes to create a set of LODs (Level of Detail) within the given constraints."
+    "text": "The V-Sekai development team is working on a project that involves avatar, world, and prop collaboration workflow in the Godot engine. The team plans to use FoundationDB with SQLite to enhance the performance of this workflow.\n\n\n\nWe need to ensure that the networking system of the Godot engine can handle the increased load and perform optimally under stress.\n\n\n\nCreate in three stages:\n\nlocal client to local server\nlocal client to remote server\nremote client to remote server\n\nDoes not test infrastructure implementation.\nWe propose to conduct stress testing on the Godot engine’s networking system.\nThis will involve creating multiple virtual users and simulating high traffic scenarios to evaluate how the system performs under heavy load.\n# This is a single node example.\n# Assuming we have a list of props and a World instance\nvar props = [prop1, prop2, prop3]\nvar world = World.new()\n\nfor i in range(10): # Simulate 10 users\n    var user = User.new() # Create a new user\n    var selected_props = [] # List to store selected props\n\n    for _ in range(randi()%props.size()+1): # Randomly select props\n        var prop = props[randi()%props.size()]\n        selected_props.append(prop)\n\n    user.glue_props(selected_props) # Glue selected props together\n    world.merge(user.get_changed_world()) # Merge the changed world into the main world\n\n# Now, let's read back the changed world\nprint(world.get_state())\n# To be determined realistic multclient version.\nTest personal computer and digital ocean.\n\n\n\n\nIdentify potential bottlenecks in the system.\nEnsure the system can handle high traffic without compromising performance.\nImprove overall system reliability and user experience.\n\n\n\n\n\nRequires time and resources to set up and conduct the tests.\nPotential for false positives or negatives due to the simulated nature of the test.\n\n\n\n\nAn alternative would be to skip stress testing and directly implement the system. However, this could lead to unforeseen issues in a live environment, potentially affecting user experience.\n\n\n\nIn cases where the traffic is consistently low, stress testing may not provide significant benefits. However, it’s still important to prepare for potential spikes in usage.\n\n\n\nThe proposed stress testing will be conducted by the V-Sekai development team.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nStress testing Unity’s LLAPI, what are the limits?\nCrappy Contraption\n\nThis proposal was assisted by Aria, an AI assistant."
   },
   {
-    "objectID": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#proposed-workflow-with-data-selection-section",
-    "href": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#proposed-workflow-with-data-selection-section",
-    "title": "Proposed: Train quad-based Meshgpt within constraints",
+    "objectID": "decisions/20240502-mesh-object-sync-benchmark.html#context",
+    "href": "decisions/20240502-mesh-object-sync-benchmark.html#context",
+    "title": "Proposed: Stress Testing Godot Engine’s Networking System",
     "section": "",
-    "text": "Data Preparation: Collect a diverse dataset of quad-based meshes suitable for generating LODs. This involves cleaning and normalizing the data to ensure consistency and remove inconsistencies or errors. Categorizing the data based on complexity and size allows for targeted training and model performance evaluation across different mesh types. A requirement is to attribute every available source 3d model. Gather a dataset of quad-based meshes representing various objects within the distance range of interest.\nModel Architecture Selection: Choose an appropriate language model architecture to handle geometric data effectively. MeshGPT could be a good starting point due to its success in handling 3D mesh generation tasks.\nBatch Processing Technique: Implement a batch processing technique to optimize the use of GPU resources.\nHyperparameter Tuning: Fine-tune the hyperparameters, such as learning rate, batch size, and number of layers, to achieve optimal performance within the given time constraint. This may involve experimentation with different values and configurations to find the best setup for the chosen model architecture and dataset.\nTraining Process: Train the MeshGPT model using the prepared dataset with the chosen architecture, optimized batch processing technique, and fine-tuned hyperparameters for over one day. This involves monitoring the training process and making necessary adjustments to ensure optimal performance within the given timeframe.\nEvaluation: Evaluate the trained model’s performance by generating LODs for a diverse quad-based mesh and comparing them to ground truth data or existing LOD generation methods.\nResults Analysis: Analyze the results obtained from the evaluation stage, focusing on metrics such as accuracy, speed, and resource usage."
+    "text": "The V-Sekai development team is working on a project that involves avatar, world, and prop collaboration workflow in the Godot engine. The team plans to use FoundationDB with SQLite to enhance the performance of this workflow."
   },
   {
-    "objectID": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#the-benefits",
-    "href": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#the-benefits",
-    "title": "Proposed: Train quad-based Meshgpt within constraints",
+    "objectID": "decisions/20240502-mesh-object-sync-benchmark.html#problem-statement",
+    "href": "decisions/20240502-mesh-object-sync-benchmark.html#problem-statement",
+    "title": "Proposed: Stress Testing Godot Engine’s Networking System",
     "section": "",
-    "text": "Efficient utilization of Video RAM in training large language models for mesh generation tasks.\nAbility to train the MeshGPT model within a one-day timeframe.\nImproved LOD generation capabilities for quad-based meshes."
+    "text": "We need to ensure that the networking system of the Godot engine can handle the increased load and perform optimally under stress."
   },
   {
-    "objectID": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#the-downsides",
-    "href": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#the-downsides",
-    "title": "Proposed: Train quad-based Meshgpt within constraints",
+    "objectID": "decisions/20240502-mesh-object-sync-benchmark.html#solution",
+    "href": "decisions/20240502-mesh-object-sync-benchmark.html#solution",
+    "title": "Proposed: Stress Testing Godot Engine’s Networking System",
     "section": "",
-    "text": "Limited flexibility due to the constraint of Video RAM.\nTraining large language models can be computationally intensive and require significant processing power, potentially impacting system performance.\nRequires careful hyperparameter tuning for optimal results within the given timeframe."
+    "text": "Create in three stages:\n\nlocal client to local server\nlocal client to remote server\nremote client to remote server\n\nDoes not test infrastructure implementation.\nWe propose to conduct stress testing on the Godot engine’s networking system.\nThis will involve creating multiple virtual users and simulating high traffic scenarios to evaluate how the system performs under heavy load.\n# This is a single node example.\n# Assuming we have a list of props and a World instance\nvar props = [prop1, prop2, prop3]\nvar world = World.new()\n\nfor i in range(10): # Simulate 10 users\n    var user = User.new() # Create a new user\n    var selected_props = [] # List to store selected props\n\n    for _ in range(randi()%props.size()+1): # Randomly select props\n        var prop = props[randi()%props.size()]\n        selected_props.append(prop)\n\n    user.glue_props(selected_props) # Glue selected props together\n    world.merge(user.get_changed_world()) # Merge the changed world into the main world\n\n# Now, let's read back the changed world\nprint(world.get_state())\n# To be determined realistic multclient version.\nTest personal computer and digital ocean."
   },
   {
-    "objectID": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#the-road-not-taken",
-    "href": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#the-road-not-taken",
-    "title": "Proposed: Train quad-based Meshgpt within constraints",
+    "objectID": "decisions/20240502-mesh-object-sync-benchmark.html#benefits",
+    "href": "decisions/20240502-mesh-object-sync-benchmark.html#benefits",
+    "title": "Proposed: Stress Testing Godot Engine’s Networking System",
     "section": "",
-    "text": "Using less powerful hardware or smaller video RAM would result in longer training times or lower model capacity.\nOpting for a more complex model architecture without optimizations could lead to overfitting and poor performance on the LOD generation task."
+    "text": "Identify potential bottlenecks in the system.\nEnsure the system can handle high traffic without compromising performance.\nImprove overall system reliability and user experience."
   },
   {
-    "objectID": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#the-infrequent-use-case",
-    "href": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#the-infrequent-use-case",
-    "title": "Proposed: Train quad-based Meshgpt within constraints",
+    "objectID": "decisions/20240502-mesh-object-sync-benchmark.html#downsides",
+    "href": "decisions/20240502-mesh-object-sync-benchmark.html#downsides",
+    "title": "Proposed: Stress Testing Godot Engine’s Networking System",
     "section": "",
-    "text": "In cases where more advanced GPU hardware is available, this workflow may not be necessary as it would allow for larger models or longer training times, potentially resulting in better performance. However, the proposed workflow can be a starting point for those with limited resources or time constraints."
+    "text": "Requires time and resources to set up and conduct the tests.\nPotential for false positives or negatives due to the simulated nature of the test."
   },
   {
-    "objectID": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#in-core-and-done-by-us",
-    "href": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#in-core-and-done-by-us",
-    "title": "Proposed: Train quad-based Meshgpt within constraints",
+    "objectID": "decisions/20240502-mesh-object-sync-benchmark.html#the-road-not-taken",
+    "href": "decisions/20240502-mesh-object-sync-benchmark.html#the-road-not-taken",
+    "title": "Proposed: Stress Testing Godot Engine’s Networking System",
     "section": "",
-    "text": "Workflow design specifically tailored to train MeshGPT on quad-based meshes within one day using a fixed sized video RAM.\nHyperparameter tuning and optimization techniques are implemented to maximize performance under the given constraints."
+    "text": "An alternative would be to skip stress testing and directly implement the system. However, this could lead to unforeseen issues in a live environment, potentially affecting user experience."
   },
   {
-    "objectID": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#status",
-    "href": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#status",
-    "title": "Proposed: Train quad-based Meshgpt within constraints",
+    "objectID": "decisions/20240502-mesh-object-sync-benchmark.html#the-infrequent-use-case",
+    "href": "decisions/20240502-mesh-object-sync-benchmark.html#the-infrequent-use-case",
+    "title": "Proposed: Stress Testing Godot Engine’s Networking System",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "In cases where the traffic is consistently low, stress testing may not provide significant benefits. However, it’s still important to prepare for potential spikes in usage."
   },
   {
-    "objectID": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#decision-makers",
-    "href": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#decision-makers",
-    "title": "Proposed: Train quad-based Meshgpt within constraints",
+    "objectID": "decisions/20240502-mesh-object-sync-benchmark.html#in-core-and-done-by-us",
+    "href": "decisions/20240502-mesh-object-sync-benchmark.html#in-core-and-done-by-us",
+    "title": "Proposed: Stress Testing Godot Engine’s Networking System",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "The proposed stress testing will be conducted by the V-Sekai development team."
   },
   {
-    "objectID": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#tags",
-    "href": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#tags",
-    "title": "Proposed: Train quad-based Meshgpt within constraints",
+    "objectID": "decisions/20240502-mesh-object-sync-benchmark.html#status",
+    "href": "decisions/20240502-mesh-object-sync-benchmark.html#status",
+    "title": "Proposed: Stress Testing Godot Engine’s Networking System",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#further-reading",
-    "href": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#further-reading",
-    "title": "Proposed: Train quad-based Meshgpt within constraints",
+    "objectID": "decisions/20240502-mesh-object-sync-benchmark.html#decision-makers",
+    "href": "decisions/20240502-mesh-object-sync-benchmark.html#decision-makers",
+    "title": "Proposed: Stress Testing Godot Engine’s Networking System",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nRunpod\nMeshGPT with Quads\n\nAI assistant Aria assisted with this article."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20230614-llm-statechart.html",
-    "href": "decisions/20230614-llm-statechart.html",
-    "title": "Proposed: Increase variety and quality with generated animation trees",
+    "objectID": "decisions/20240502-mesh-object-sync-benchmark.html#tags",
+    "href": "decisions/20240502-mesh-object-sync-benchmark.html#tags",
+    "title": "Proposed: Stress Testing Godot Engine’s Networking System",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, ai assisted\n\n\n\n\nGenerate an AnimationTrees with blend trees and nested state machines as a startchart json.\n\n\n\nCreate a script that generates a JSON file representing the AnimationTrees structure, including blend trees and nested state machines. This JSON file can then be used to create the corresponding AnimationTrees in the V-Sekai engine.\n\n\n\n\nDefine the JSON schema for the AnimationTrees structure.\nCreate a script that reads the existing AnimationTrees data and converts it into the defined JSON format.\nImplement a function in the V-Sekai engine that reads the generated JSON file and creates the corresponding AnimationTrees.\n\n\n\n\n\nEasier management and sharing of AnimationTrees structures.\nSimplified collaboration between developers working on the same project.\nPotential for automation and procedural generation of AnimationTrees.\n\n\n\n\n\nAdditional development time required to implement the JSON conversion script and the corresponding function in the V-Sekai engine.\nPossible performance overhead when reading and parsing the JSON file.\n\n\n\n\n\nManually creating and managing AnimationTrees structures without using a JSON representation.\n\n\n\n\nNo, this enhancement aims to simplify the management and sharing of complex AnimationTrees structures, which cannot be easily achieved with just a few lines of script.\n\n\n\nYes, implementing this feature as part of the core V-Sekai engine ensures consistency and compatibility across different projects and developers using the engine.\n\n\n\n\nV-Sekai\njsonformer\nintegrations/jsonformer_experimental"
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20230614-llm-statechart.html#metadata",
-    "href": "decisions/20230614-llm-statechart.html#metadata",
-    "title": "Proposed: Increase variety and quality with generated animation trees",
+    "objectID": "decisions/20240502-mesh-object-sync-benchmark.html#further-reading",
+    "href": "decisions/20240502-mesh-object-sync-benchmark.html#further-reading",
+    "title": "Proposed: Stress Testing Godot Engine’s Networking System",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, ai assisted"
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nStress testing Unity’s LLAPI, what are the limits?\nCrappy Contraption\n\nThis proposal was assisted by Aria, an AI assistant."
   },
   {
-    "objectID": "decisions/20230614-llm-statechart.html#context-and-problem-statement",
-    "href": "decisions/20230614-llm-statechart.html#context-and-problem-statement",
-    "title": "Proposed: Increase variety and quality with generated animation trees",
+    "objectID": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html",
+    "href": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html",
+    "title": "Proposed: Phase out groups in the branding to make it more recognizable",
     "section": "",
-    "text": "Generate an AnimationTrees with blend trees and nested state machines as a startchart json."
+    "text": "Need to find recognizable brands.\n\n\n\nPhase out the ‘groups’ terminology as much as possible because it was too generic and can easily get mixed up with other things.\n\n\n\nReplace vsk_default for the groups in the Godot project.\n\n\n\n\n[e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]\n[…]\n\n\n\n\n\n[e.g., compromising quality attribute, follow-up decisions required, …]\n[…]\n\n[this section can be repeated for each option if more than one option is open for consideration]\n\n\n\n\nOption: \nRejection Reason: \n\n\n\n\nNot a script.\n\n\n\nWe use the groups branding.\n\n\n\n\nLink type \n… \n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230614-llm-statechart.html#proposed-solution",
-    "href": "decisions/20230614-llm-statechart.html#proposed-solution",
-    "title": "Proposed: Increase variety and quality with generated animation trees",
+    "objectID": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html#context-and-problem-statement",
+    "href": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html#context-and-problem-statement",
+    "title": "Proposed: Phase out groups in the branding to make it more recognizable",
     "section": "",
-    "text": "Create a script that generates a JSON file representing the AnimationTrees structure, including blend trees and nested state machines. This JSON file can then be used to create the corresponding AnimationTrees in the V-Sekai engine."
+    "text": "Need to find recognizable brands."
   },
   {
-    "objectID": "decisions/20230614-llm-statechart.html#implementation",
-    "href": "decisions/20230614-llm-statechart.html#implementation",
-    "title": "Proposed: Increase variety and quality with generated animation trees",
+    "objectID": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: Phase out groups in the branding to make it more recognizable",
     "section": "",
-    "text": "Define the JSON schema for the AnimationTrees structure.\nCreate a script that reads the existing AnimationTrees data and converts it into the defined JSON format.\nImplement a function in the V-Sekai engine that reads the generated JSON file and creates the corresponding AnimationTrees."
+    "text": "Phase out the ‘groups’ terminology as much as possible because it was too generic and can easily get mixed up with other things."
   },
   {
-    "objectID": "decisions/20230614-llm-statechart.html#positive-consequences",
-    "href": "decisions/20230614-llm-statechart.html#positive-consequences",
-    "title": "Proposed: Increase variety and quality with generated animation trees",
+    "objectID": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Phase out groups in the branding to make it more recognizable",
     "section": "",
-    "text": "Easier management and sharing of AnimationTrees structures.\nSimplified collaboration between developers working on the same project.\nPotential for automation and procedural generation of AnimationTrees."
+    "text": "Replace vsk_default for the groups in the Godot project."
   },
   {
-    "objectID": "decisions/20230614-llm-statechart.html#negative-consequences",
-    "href": "decisions/20230614-llm-statechart.html#negative-consequences",
-    "title": "Proposed: Increase variety and quality with generated animation trees",
+    "objectID": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html#positive-consequences",
+    "href": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html#positive-consequences",
+    "title": "Proposed: Phase out groups in the branding to make it more recognizable",
     "section": "",
-    "text": "Additional development time required to implement the JSON conversion script and the corresponding function in the V-Sekai engine.\nPossible performance overhead when reading and parsing the JSON file."
+    "text": "[e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]\n[…]"
   },
   {
-    "objectID": "decisions/20230614-llm-statechart.html#option-graveyard",
-    "href": "decisions/20230614-llm-statechart.html#option-graveyard",
-    "title": "Proposed: Increase variety and quality with generated animation trees",
+    "objectID": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html#negative-consequences",
+    "href": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html#negative-consequences",
+    "title": "Proposed: Phase out groups in the branding to make it more recognizable",
     "section": "",
-    "text": "Manually creating and managing AnimationTrees structures without using a JSON representation."
+    "text": "[e.g., compromising quality attribute, follow-up decisions required, …]\n[…]\n\n[this section can be repeated for each option if more than one option is open for consideration]"
   },
   {
-    "objectID": "decisions/20230614-llm-statechart.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230614-llm-statechart.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Increase variety and quality with generated animation trees",
+    "objectID": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html#option-graveyard",
+    "href": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html#option-graveyard",
+    "title": "Proposed: Phase out groups in the branding to make it more recognizable",
     "section": "",
-    "text": "No, this enhancement aims to simplify the management and sharing of complex AnimationTrees structures, which cannot be easily achieved with just a few lines of script."
+    "text": "Option: \nRejection Reason:"
   },
   {
-    "objectID": "decisions/20230614-llm-statechart.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230614-llm-statechart.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Increase variety and quality with generated animation trees",
+    "objectID": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Phase out groups in the branding to make it more recognizable",
     "section": "",
-    "text": "Yes, implementing this feature as part of the core V-Sekai engine ensures consistency and compatibility across different projects and developers using the engine."
+    "text": "Not a script."
   },
   {
-    "objectID": "decisions/20230614-llm-statechart.html#references",
-    "href": "decisions/20230614-llm-statechart.html#references",
-    "title": "Proposed: Increase variety and quality with generated animation trees",
+    "objectID": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Phase out groups in the branding to make it more recognizable",
     "section": "",
-    "text": "V-Sekai\njsonformer\nintegrations/jsonformer_experimental"
+    "text": "We use the groups branding."
   },
   {
-    "objectID": "decisions/20240217-intended-effort-versioning.html",
-    "href": "decisions/20240217-intended-effort-versioning.html",
-    "title": "Proposed: Adoption of Intended Effort Versioning (EffVer) in V-Sekai",
+    "objectID": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html#references",
+    "href": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html#references",
+    "title": "Proposed: Phase out groups in the branding to make it more recognizable",
     "section": "",
-    "text": "V-Sekai currently does not adhere to any specific versioning scheme. This can lead to confusion and inefficiency when users try to adopt new versions of the software.\n\n\n\nWithout a clear versioning system, users may struggle to understand the effort required to adopt new versions of V-Sekai. This can result in wasted time and resources, and potentially deter users from updating to newer versions.\n\n\n\nWe propose adopting EffVer, short for Intended Effort Versioning. This versioning scheme categorizes version increments into Macro, Meso, and Micro, based on the effort needed for adoption—large, some, and little to no effort, respectively.\n# Example of EffVer in action\nversion = \"1.0.0\"  # Initial release\n\n# A micro update requiring little to no effort to adopt\nversion = \"1.0.1\"\n\n# A meso update requiring some effort to adopt\nversion = \"1.1.0\"\n\n# A macro update requiring large effort to adopt\nversion = \"2.0.0\"\n\n\n\nAdopting EffVer would provide clear communication to users about the expected effort required to adopt new versions of V-Sekai. This respects users’ time by quantifying and communicating the adoption effort upfront.\n\n\n\nThe main downside is that it requires the development team to accurately estimate the effort required for each update, which could be subjective and vary between users.\n\n\n\nAlternatives such as Semantic Versioning (SemVer) and Calendar Versioning (CalVer) were considered. However, these focus on technical orthogonality or time of release, rather than the intended impact of changes.\n\n\n\nEffVer may not be as effective for infrequent users who are less familiar with the software and may require more effort to adopt new versions regardless of the changes made.\n\n\n\nThe implementation of EffVer would be done by the V-Sekai development team and integrated into the core project.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team and community stakeholders.\n\n\n\n\n\nV-Sekai, Avatar Customization, AI, Facial Expressions\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nIntended Effort Versioning (EffVer)\n\nAI assistant Aria assisted with this article."
+    "text": "Link type \n…"
   },
   {
-    "objectID": "decisions/20240217-intended-effort-versioning.html#the-context",
-    "href": "decisions/20240217-intended-effort-versioning.html#the-context",
-    "title": "Proposed: Adoption of Intended Effort Versioning (EffVer) in V-Sekai",
+    "objectID": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html#derivative-license",
+    "href": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html#derivative-license",
+    "title": "Proposed: Phase out groups in the branding to make it more recognizable",
     "section": "",
-    "text": "V-Sekai currently does not adhere to any specific versioning scheme. This can lead to confusion and inefficiency when users try to adopt new versions of the software."
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240217-intended-effort-versioning.html#the-problem-statement",
-    "href": "decisions/20240217-intended-effort-versioning.html#the-problem-statement",
-    "title": "Proposed: Adoption of Intended Effort Versioning (EffVer) in V-Sekai",
+    "objectID": "decisions/20230123-use-easy-charts-for-observability.html",
+    "href": "decisions/20230123-use-easy-charts-for-observability.html",
+    "title": "Proposed: Use Easy Charts for observability",
     "section": "",
-    "text": "Without a clear versioning system, users may struggle to understand the effort required to adopt new versions of V-Sekai. This can result in wasted time and resources, and potentially deter users from updating to newer versions."
+    "text": "Proposed: Use Easy Charts for observability\n\nMetadata\n\nStatus: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nContext and Problem Statement\nWe would like to visualize metrics in-game.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nPort https://github.com/fenix-hub/godot-engine.easy-charts to v-sekai\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\n\nCreate a project in 4\nAdd easy charts as a addon\nUse the auto migrate in 4\nFix missing\n\n\n\nPositive Consequences\nWe are able to use V-Sekai easier to debug.\n\n\nNegative Consequences\nWe cannot get other features in.\n\n\nOption graveyard\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nEasy charts is not a few lines of script.\n\n\nIs there a reason why this should be core and done by us?\nToo low performance impacts usability.\n\n\nReferences\n\nV-Sekai\nhttps://github.com/fenix-hub/godot-engine.easy-charts"
   },
   {
-    "objectID": "decisions/20240217-intended-effort-versioning.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240217-intended-effort-versioning.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Adoption of Intended Effort Versioning (EffVer) in V-Sekai",
+    "objectID": "decisions/20231203-mesh-rwkv.html",
+    "href": "decisions/20231203-mesh-rwkv.html",
+    "title": "Proposed: Triangle Meshes Inferencing with MeshRWKV",
     "section": "",
-    "text": "We propose adopting EffVer, short for Intended Effort Versioning. This versioning scheme categorizes version increments into Macro, Meso, and Micro, based on the effort needed for adoption—large, some, and little to no effort, respectively.\n# Example of EffVer in action\nversion = \"1.0.0\"  # Initial release\n\n# A micro update requiring little to no effort to adopt\nversion = \"1.0.1\"\n\n# A meso update requiring some effort to adopt\nversion = \"1.1.0\"\n\n# A macro update requiring large effort to adopt\nversion = \"2.0.0\""
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nMeshGPT uses a transformer model trained on geometric vocabulary to generate triangle meshes, resulting in clean, coherent, and compact meshes.\n\n\n\nAdapting GPT-like generative models for the 3D domain is a challenge. Automated triangle mesh generation needs a robust solution.\n\n\n\nThe MeshRWKV model employs a sequence-based approach that autoregressively generates triangle meshes as sequences of triangles. The conversion process to RWKV4 can be broken down into two primary steps:\n\n\nThe initial step involves learning a vocabulary that can accurately represent triangle meshes from a large collection of 3D object meshes. This enables the encoding and decoding of triangles from this embedding.\nA graph convolution encoder, specifically a series of SAGE-Conv graph convolution layers, is utilized in this process. This encoder processes the mesh in the form of a face graph. For each graph node, input features include the positionally encoded 9 coordinates of the face triangle, its area, the angles between its edges, and the normal of the face.\nThese geometrically rich features capture the intricate details of 3D shapes and are quantized as embeddings of a codebook using residual quantization. This effectively reduces the sequence lengths of the mesh representation.\nThese embeddings are then sequenced and decoded by a 1D ResNet-34 network, which interprets the face features as a 1D sequence. It outputs logits corresponding to the 9 discrete coordinates of each face triangle. The size of the codebook C and the discretization space are determined based on the specific requirements and constraints of the model.\n\n\n\nThe next step is to train RWKV4, which leverages these quantized geometric embeddings. Given a sequence of geometric embeddings extracted from the triangles of a mesh, the transformer is trained to predict the codebook index of the next embedding in the sequence.\nOnce trained, the transformer can be auto-regressively sampled to predict sequences of embeddings. These embeddings can then be decoded to generate novel and diverse mesh structures that display efficient, irregular triangulations similar to human-crafted meshes.\n\n\n\nMeshGPT has made significant strides in the field of direct mesh generation, but it is not without its limitations. The autoregressive nature of the model results in slower sampling performance, with mesh generation times ranging from 30 to 90 seconds. The MeshGPT team’s learned tokenization approach has been successful in reducing sequence lengths for single object generation, but it may not be as effective when applied to scene-scale generation. This presents an opportunity for future enhancement.\nFurthermore, MeshGPT’s current computational resources restrict it to using the GPT2-medium transformer, which is less sophisticated than models like Llama2. Given that larger language models tend to benefit from increased data and computational power, expanding these resources could significantly enhance MeshGPT’s performance and capabilities.\nIt’s important to note that the RWKV (Receptance Weighted Key Value) model’s context size is significantly larger than that of GPT2. In machine learning, context size refers to the amount of information from previous steps that a model can consider while making predictions for the next step. It essentially determines how much ‘memory’ the model has about past data.\nThe larger context size of RWKV means that it can remember and utilize more past information while generating outputs. This feature potentially enables it to handle larger and more complex tasks, provided there are sufficient computational resources.\nHowever, a larger context size also implies higher computational demands. More processing power and memory are required to store and manage such large amounts of data. This could pose challenges in terms of hardware requirements and efficiency, particularly when dealing with very large datasets or complex tasks.\n\n\n\n\nOur approach produces compact meshes with sharp geometric details. It can suggest multiple shape completions for incomplete shapes.\n\n\n\nGiven that the MeshGPT model has already developed a process for converting mesh data into logits, this simplifies the task of applying the MeshRWKV model to skeletal animation.\nThe fundamental concept would involve representing a sequence of animation frames (from frame0 to frameN) as meshes. The recursive nature of RWKV could potentially offer significant advantages in this scenario. It might facilitate efficient encoding and decoding of sequential frames, which could lead to the generation of smooth and coherent animations.\nWith the mesh-to-logits conversion challenge addressed by MeshGPT, the primary focus can be on developing new training methodologies and loss functions tailored for animation data. This approach could significantly broaden the applicability of the MeshRWKV model, opening up exciting possibilities for future research and development in the field of 3D animation.\n\n\n\nTraining the model may require significant computational resources. Learning a vocabulary for triangle meshes could be complex.\n\n\n\nOther methods like neural field-based approaches exist but often miss geometric details or produce over-triangulated meshes.\n\n\n\nGenerating complex 3D shapes for niche applications might need additional model training or fine-tuning.\n\n\n\nYes, this proposal is core to our work at V-Sekai and will be implemented by us.\n\n\n\n\nV-Sekai · GitHub\nV-Sekai/v-sekai-game\nMeshGPT\nObjaverse-XL\nNous-Hermes-2-Vision\nMachine Learning in Elixir\nPyTorch Geometric SAGEConv\nInductive Representation Learning on Large Graphs\n\nAssisted by AI assistant Aria."
   },
   {
-    "objectID": "decisions/20240217-intended-effort-versioning.html#the-benefits",
-    "href": "decisions/20240217-intended-effort-versioning.html#the-benefits",
-    "title": "Proposed: Adoption of Intended Effort Versioning (EffVer) in V-Sekai",
+    "objectID": "decisions/20231203-mesh-rwkv.html#metadata",
+    "href": "decisions/20231203-mesh-rwkv.html#metadata",
+    "title": "Proposed: Triangle Meshes Inferencing with MeshRWKV",
     "section": "",
-    "text": "Adopting EffVer would provide clear communication to users about the expected effort required to adopt new versions of V-Sekai. This respects users’ time by quantifying and communicating the adoption effort upfront."
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20240217-intended-effort-versioning.html#the-downsides",
-    "href": "decisions/20240217-intended-effort-versioning.html#the-downsides",
-    "title": "Proposed: Adoption of Intended Effort Versioning (EffVer) in V-Sekai",
+    "objectID": "decisions/20231203-mesh-rwkv.html#background",
+    "href": "decisions/20231203-mesh-rwkv.html#background",
+    "title": "Proposed: Triangle Meshes Inferencing with MeshRWKV",
     "section": "",
-    "text": "The main downside is that it requires the development team to accurately estimate the effort required for each update, which could be subjective and vary between users."
+    "text": "MeshGPT uses a transformer model trained on geometric vocabulary to generate triangle meshes, resulting in clean, coherent, and compact meshes."
   },
   {
-    "objectID": "decisions/20240217-intended-effort-versioning.html#the-road-not-taken",
-    "href": "decisions/20240217-intended-effort-versioning.html#the-road-not-taken",
-    "title": "Proposed: Adoption of Intended Effort Versioning (EffVer) in V-Sekai",
+    "objectID": "decisions/20231203-mesh-rwkv.html#problem",
+    "href": "decisions/20231203-mesh-rwkv.html#problem",
+    "title": "Proposed: Triangle Meshes Inferencing with MeshRWKV",
     "section": "",
-    "text": "Alternatives such as Semantic Versioning (SemVer) and Calendar Versioning (CalVer) were considered. However, these focus on technical orthogonality or time of release, rather than the intended impact of changes."
+    "text": "Adapting GPT-like generative models for the 3D domain is a challenge. Automated triangle mesh generation needs a robust solution."
   },
   {
-    "objectID": "decisions/20240217-intended-effort-versioning.html#the-infrequent-use-case",
-    "href": "decisions/20240217-intended-effort-versioning.html#the-infrequent-use-case",
-    "title": "Proposed: Adoption of Intended Effort Versioning (EffVer) in V-Sekai",
+    "objectID": "decisions/20231203-mesh-rwkv.html#strategy",
+    "href": "decisions/20231203-mesh-rwkv.html#strategy",
+    "title": "Proposed: Triangle Meshes Inferencing with MeshRWKV",
     "section": "",
-    "text": "EffVer may not be as effective for infrequent users who are less familiar with the software and may require more effort to adopt new versions regardless of the changes made."
+    "text": "The MeshRWKV model employs a sequence-based approach that autoregressively generates triangle meshes as sequences of triangles. The conversion process to RWKV4 can be broken down into two primary steps:\n\n\nThe initial step involves learning a vocabulary that can accurately represent triangle meshes from a large collection of 3D object meshes. This enables the encoding and decoding of triangles from this embedding.\nA graph convolution encoder, specifically a series of SAGE-Conv graph convolution layers, is utilized in this process. This encoder processes the mesh in the form of a face graph. For each graph node, input features include the positionally encoded 9 coordinates of the face triangle, its area, the angles between its edges, and the normal of the face.\nThese geometrically rich features capture the intricate details of 3D shapes and are quantized as embeddings of a codebook using residual quantization. This effectively reduces the sequence lengths of the mesh representation.\nThese embeddings are then sequenced and decoded by a 1D ResNet-34 network, which interprets the face features as a 1D sequence. It outputs logits corresponding to the 9 discrete coordinates of each face triangle. The size of the codebook C and the discretization space are determined based on the specific requirements and constraints of the model.\n\n\n\nThe next step is to train RWKV4, which leverages these quantized geometric embeddings. Given a sequence of geometric embeddings extracted from the triangles of a mesh, the transformer is trained to predict the codebook index of the next embedding in the sequence.\nOnce trained, the transformer can be auto-regressively sampled to predict sequences of embeddings. These embeddings can then be decoded to generate novel and diverse mesh structures that display efficient, irregular triangulations similar to human-crafted meshes.\n\n\n\nMeshGPT has made significant strides in the field of direct mesh generation, but it is not without its limitations. The autoregressive nature of the model results in slower sampling performance, with mesh generation times ranging from 30 to 90 seconds. The MeshGPT team’s learned tokenization approach has been successful in reducing sequence lengths for single object generation, but it may not be as effective when applied to scene-scale generation. This presents an opportunity for future enhancement.\nFurthermore, MeshGPT’s current computational resources restrict it to using the GPT2-medium transformer, which is less sophisticated than models like Llama2. Given that larger language models tend to benefit from increased data and computational power, expanding these resources could significantly enhance MeshGPT’s performance and capabilities.\nIt’s important to note that the RWKV (Receptance Weighted Key Value) model’s context size is significantly larger than that of GPT2. In machine learning, context size refers to the amount of information from previous steps that a model can consider while making predictions for the next step. It essentially determines how much ‘memory’ the model has about past data.\nThe larger context size of RWKV means that it can remember and utilize more past information while generating outputs. This feature potentially enables it to handle larger and more complex tasks, provided there are sufficient computational resources.\nHowever, a larger context size also implies higher computational demands. More processing power and memory are required to store and manage such large amounts of data. This could pose challenges in terms of hardware requirements and efficiency, particularly when dealing with very large datasets or complex tasks."
   },
   {
-    "objectID": "decisions/20240217-intended-effort-versioning.html#in-core-and-done-by-us",
-    "href": "decisions/20240217-intended-effort-versioning.html#in-core-and-done-by-us",
-    "title": "Proposed: Adoption of Intended Effort Versioning (EffVer) in V-Sekai",
+    "objectID": "decisions/20231203-mesh-rwkv.html#benefits",
+    "href": "decisions/20231203-mesh-rwkv.html#benefits",
+    "title": "Proposed: Triangle Meshes Inferencing with MeshRWKV",
     "section": "",
-    "text": "The implementation of EffVer would be done by the V-Sekai development team and integrated into the core project."
+    "text": "Our approach produces compact meshes with sharp geometric details. It can suggest multiple shape completions for incomplete shapes."
   },
   {
-    "objectID": "decisions/20240217-intended-effort-versioning.html#status",
-    "href": "decisions/20240217-intended-effort-versioning.html#status",
-    "title": "Proposed: Adoption of Intended Effort Versioning (EffVer) in V-Sekai",
+    "objectID": "decisions/20231203-mesh-rwkv.html#future-work",
+    "href": "decisions/20231203-mesh-rwkv.html#future-work",
+    "title": "Proposed: Triangle Meshes Inferencing with MeshRWKV",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "Given that the MeshGPT model has already developed a process for converting mesh data into logits, this simplifies the task of applying the MeshRWKV model to skeletal animation.\nThe fundamental concept would involve representing a sequence of animation frames (from frame0 to frameN) as meshes. The recursive nature of RWKV could potentially offer significant advantages in this scenario. It might facilitate efficient encoding and decoding of sequential frames, which could lead to the generation of smooth and coherent animations.\nWith the mesh-to-logits conversion challenge addressed by MeshGPT, the primary focus can be on developing new training methodologies and loss functions tailored for animation data. This approach could significantly broaden the applicability of the MeshRWKV model, opening up exciting possibilities for future research and development in the field of 3D animation."
   },
   {
-    "objectID": "decisions/20240217-intended-effort-versioning.html#decision-makers",
-    "href": "decisions/20240217-intended-effort-versioning.html#decision-makers",
-    "title": "Proposed: Adoption of Intended Effort Versioning (EffVer) in V-Sekai",
+    "objectID": "decisions/20231203-mesh-rwkv.html#drawbacks",
+    "href": "decisions/20231203-mesh-rwkv.html#drawbacks",
+    "title": "Proposed: Triangle Meshes Inferencing with MeshRWKV",
     "section": "",
-    "text": "V-Sekai development team and community stakeholders."
+    "text": "Training the model may require significant computational resources. Learning a vocabulary for triangle meshes could be complex."
   },
   {
-    "objectID": "decisions/20240217-intended-effort-versioning.html#tags",
-    "href": "decisions/20240217-intended-effort-versioning.html#tags",
-    "title": "Proposed: Adoption of Intended Effort Versioning (EffVer) in V-Sekai",
+    "objectID": "decisions/20231203-mesh-rwkv.html#alternatives",
+    "href": "decisions/20231203-mesh-rwkv.html#alternatives",
+    "title": "Proposed: Triangle Meshes Inferencing with MeshRWKV",
     "section": "",
-    "text": "V-Sekai, Avatar Customization, AI, Facial Expressions"
+    "text": "Other methods like neural field-based approaches exist but often miss geometric details or produce over-triangulated meshes."
   },
   {
-    "objectID": "decisions/20240217-intended-effort-versioning.html#further-reading",
-    "href": "decisions/20240217-intended-effort-versioning.html#further-reading",
-    "title": "Proposed: Adoption of Intended Effort Versioning (EffVer) in V-Sekai",
+    "objectID": "decisions/20231203-mesh-rwkv.html#special-use-case",
+    "href": "decisions/20231203-mesh-rwkv.html#special-use-case",
+    "title": "Proposed: Triangle Meshes Inferencing with MeshRWKV",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nIntended Effort Versioning (EffVer)\n\nAI assistant Aria assisted with this article."
+    "text": "Generating complex 3D shapes for niche applications might need additional model training or fine-tuning."
   },
   {
-    "objectID": "decisions/20231110-better-pipeline-tools.html",
-    "href": "decisions/20231110-better-pipeline-tools.html",
-    "title": "Proposed: Enhancing V-Sekai x Godot Engine x AYON for a Superior Workflow",
+    "objectID": "decisions/20231203-mesh-rwkv.html#core-implemented-by-us",
+    "href": "decisions/20231203-mesh-rwkv.html#core-implemented-by-us",
+    "title": "Proposed: Triangle Meshes Inferencing with MeshRWKV",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai, fire\nTags: V-Sekai, Godot Engine, Virtual Reality\n\n\n\n\nThe V-Sekai Project is an open-source initiative that aims to bring social VR/VRSNS/metaverse components to the Godot Engine.\n\n\n\nOne of the market leaders in VRSNS, the OMEGA project, is tied to a specific game engine and faces two key challenges in bundling their game engine:\n\nThe size of the bundle would be quite large.\nThey are separate entities that require commercial terms to bundle together.\nComponents are not commercial-friendly opensource.\n\nWe have the opportunity to enhance AYON to create a superior launcher for the Godot Engine and the Project, something many of our competitors cannot do due to similar constraints.\n\n\n\nOur strategy is to outperform OMEGA’s workflow by enhancing AYON through tooling and comprehensive documentation. By providing clear instructions and efficient tools for developers, we aim to streamline the development process and improve efficiency.\n\n\n\nThis approach could potentially lead to a more diverse range of social VR experiences and help grow the Godot Engine community.\n\n\n\nEnhancing AYON and creating comprehensive documentation is a time-consuming process and requires ongoing maintenance.\n\n\n\nAn alternative option would be to develop an individual plugin or extension. However, this requires significant resources and may not be feasible for an open-source project.\n\n\n\nWhile developing a plugin or extension provides out-of-the-box functionality, it may not cover all use cases and could limit the diversity of social VR experiences.\n\n\n\nBy focusing on enhancing AYON and creating comprehensive documentation, we are empowering developers to implement these features in their own unique ways.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nAYON - The platform hosting our tools and editor\n\n\nThis article was assisted by Aria, an AI assistant."
+    "text": "Yes, this proposal is core to our work at V-Sekai and will be implemented by us."
   },
   {
-    "objectID": "decisions/20231110-better-pipeline-tools.html#metadata",
-    "href": "decisions/20231110-better-pipeline-tools.html#metadata",
-    "title": "Proposed: Enhancing V-Sekai x Godot Engine x AYON for a Superior Workflow",
+    "objectID": "decisions/20231203-mesh-rwkv.html#references",
+    "href": "decisions/20231203-mesh-rwkv.html#references",
+    "title": "Proposed: Triangle Meshes Inferencing with MeshRWKV",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai, fire\nTags: V-Sekai, Godot Engine, Virtual Reality"
+    "text": "V-Sekai · GitHub\nV-Sekai/v-sekai-game\nMeshGPT\nObjaverse-XL\nNous-Hermes-2-Vision\nMachine Learning in Elixir\nPyTorch Geometric SAGEConv\nInductive Representation Learning on Large Graphs\n\nAssisted by AI assistant Aria."
   },
   {
-    "objectID": "decisions/20231110-better-pipeline-tools.html#the-backdrop",
-    "href": "decisions/20231110-better-pipeline-tools.html#the-backdrop",
-    "title": "Proposed: Enhancing V-Sekai x Godot Engine x AYON for a Superior Workflow",
+    "objectID": "decisions/20220531-elixir-uro-dev.html",
+    "href": "decisions/20220531-elixir-uro-dev.html",
+    "title": "Accepted: How to start a development environment for cockroach and elixir?",
     "section": "",
-    "text": "The V-Sekai Project is an open-source initiative that aims to bring social VR/VRSNS/metaverse components to the Godot Engine."
+    "text": "Accepted: How to start a development environment for cockroach and elixir?\n\nDescribe the status of the issue.\n\nproposed\ndraft\nrejected\naccepted\ndeprecated\nsuperseded by\n\n\n\nList the deciders of the issue.\nV-Sekai,lyuma,fire,\n\n\nDescribe the tags of the issue.\nV-Sekai,\n\n\nContext and Problem Statement\nHow do we start our uro backend?\nSee also 20230107-elixir-uro-dev-sqlite.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nWrite documentation how to update elixir.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nDownload the cockroach distribution and run this:\n./cockroach.exe start-single-node  --insecure --store=node1 --listen-addr=localhost:26257 --http-addr=localhost:8080\nYou can add --background to run in the background.\nNext, compile uro. You will need Elixir installed.\nI recommend getting the latest, but for these steps, I am using Elixir v1.13.3.\nDownload Uro from https://github.com/V-Sekai/uro\nWe are using the dev environment. It is the default, but you can also set MIX_ENV=dev.\nTo compile HTML/CSS webpack:\ncd assets\nnpm install\nnpm run deploy\ncd ..\nIf the compile gives issues, you can run it multiple times. To compile dependencies:\nmix do compile, phx.digest\nIf one of them gives an error due to nmake or not having a compiler, you can fix it by opening a x64 Native Tools command prompt from visual studio and run mix deps.compile bcrypt_elixir\nFinally, create and migrate the database and start the development server:\nmix ecto.create\nmix ecto.migrate\nmix phx.server\nThis will start uro at http://localhost:4000/\nGitHub - V-Sekai/uro: Server backend for V-Sekai written in Elixir …\nThe docker image docker-uro is compiled using GoCD, so after pushing, check that the pipeline ran.\nThen, go to DockerHub at https://hub.docker.com/r/groupsinfra/uro/tags and check the most recently pushed tag (it will not be the latest one, but instead a specific version).\nNow, edit the flux config at https://github.com/V-Sekai/flux-config/blob/flux2/workloads/uro-deployment.yaml and replace the uro image version with the tag from above.\nCheck that uro-deployment was updated.\n\n\nPositive Consequences\nWe’re able to update uro!\n\n\nNegative Consequences\nNo response\n\n\nOption graveyard\nNo response\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nIt’s arguably a few lines of script, but it’s our script!\n\n\nIs there a reason why this should be core and done by us?\nWe maintain the website.\n\n\nReferences\n\nV-Sekai\nUro\nhttps://github.com/V-Sekai/uro/issues/52\n\n\n\nLicense of the contribution\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20231110-better-pipeline-tools.html#the-challenge",
-    "href": "decisions/20231110-better-pipeline-tools.html#the-challenge",
-    "title": "Proposed: Enhancing V-Sekai x Godot Engine x AYON for a Superior Workflow",
+    "objectID": "decisions/20240623-what-is-uro-backend.html",
+    "href": "decisions/20240623-what-is-uro-backend.html",
+    "title": "Proposed: Why did we build “Uro”?",
     "section": "",
-    "text": "One of the market leaders in VRSNS, the OMEGA project, is tied to a specific game engine and faces two key challenges in bundling their game engine:\n\nThe size of the bundle would be quite large.\nThey are separate entities that require commercial terms to bundle together.\nComponents are not commercial-friendly opensource.\n\nWe have the opportunity to enhance AYON to create a superior launcher for the Godot Engine and the Project, something many of our competitors cannot do due to similar constraints."
+    "text": "V-Sekai is an open-source project that brings social VR/VRSNS/metaverse components to the Godot Engine. It has a complex architecture involving multiple components, including a game client, a backend called “Uro”, and game servers.\n\n\n\nThere is a need to explain the architecture of V-Sekai, specifically the roles and interactions of the game client, the Uro backend, and the game servers.\n\n\n\nThe game client is the application that users interact with. It connects to both Uro, our backend service, and directly to game servers.\nThe game editor is a separate tool used by game designers. They use it to create and upload new worlds, props, and avatars to the Uro backend.\nUro is the backend service for our game. It handles requests from both the game client and game editor. It stores and serves game assets like worlds, props, and avatars.\nGame servers are responsible for running the game logic in real-time. They communicate with the game clients to keep the game state synchronized between all players.\n\n\n\nUnderstanding the architecture of V-Sekai can help developers contribute more effectively to the project. It can also help users troubleshoot issues and understand the capabilities and limitations of the system.\n\n\n\nThe complexity of the architecture may be daunting for some, and there may be a learning curve involved in understanding it.\n\n\n\n\nAn alternative approach could have been to implement a Peer-to-Peer (P2P) architecture. In this setup, each game client also acts as a mini-server, communicating directly with other clients.\nAnother alternative would be to use cloud-based game backends such as Microsoft’s PlayFab. These services can automatically scale up or down based on demand, ensuring that there’s always enough capacity for all players.\nNakama is an open-source distributed social and realtime server for games and apps. It has a rich feature set including user accounts, chat, social, matchmaker, realtime multiplayer, and much more.\n\n\n\n\nThe primary use case for the Uro server is to facilitate interactions between the game client and the game servers, there may be infrequent use cases where its functionality could be extended or used in different ways. For example, it is can be used to implement additional features such as leaderboards, achievements, or social networking features within the game. These use cases, while not common, should still be considered when designing and implementing the Uro server.\n\n\n\nThis proposal is core to the V-Sekai project and will be implemented by the V-Sekai development team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\nFire\nAries\n\n\n\n\n\nV-Sekai\nUro Backend\nGame Architecture\nOpen-source Project\nGodot Engine\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20231110-better-pipeline-tools.html#the-strategy",
-    "href": "decisions/20231110-better-pipeline-tools.html#the-strategy",
-    "title": "Proposed: Enhancing V-Sekai x Godot Engine x AYON for a Superior Workflow",
+    "objectID": "decisions/20240623-what-is-uro-backend.html#the-context",
+    "href": "decisions/20240623-what-is-uro-backend.html#the-context",
+    "title": "Proposed: Why did we build “Uro”?",
     "section": "",
-    "text": "Our strategy is to outperform OMEGA’s workflow by enhancing AYON through tooling and comprehensive documentation. By providing clear instructions and efficient tools for developers, we aim to streamline the development process and improve efficiency."
+    "text": "V-Sekai is an open-source project that brings social VR/VRSNS/metaverse components to the Godot Engine. It has a complex architecture involving multiple components, including a game client, a backend called “Uro”, and game servers."
   },
   {
-    "objectID": "decisions/20231110-better-pipeline-tools.html#the-upside",
-    "href": "decisions/20231110-better-pipeline-tools.html#the-upside",
-    "title": "Proposed: Enhancing V-Sekai x Godot Engine x AYON for a Superior Workflow",
+    "objectID": "decisions/20240623-what-is-uro-backend.html#the-problem-statement",
+    "href": "decisions/20240623-what-is-uro-backend.html#the-problem-statement",
+    "title": "Proposed: Why did we build “Uro”?",
     "section": "",
-    "text": "This approach could potentially lead to a more diverse range of social VR experiences and help grow the Godot Engine community."
+    "text": "There is a need to explain the architecture of V-Sekai, specifically the roles and interactions of the game client, the Uro backend, and the game servers."
   },
   {
-    "objectID": "decisions/20231110-better-pipeline-tools.html#the-downside",
-    "href": "decisions/20231110-better-pipeline-tools.html#the-downside",
-    "title": "Proposed: Enhancing V-Sekai x Godot Engine x AYON for a Superior Workflow",
+    "objectID": "decisions/20240623-what-is-uro-backend.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240623-what-is-uro-backend.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Why did we build “Uro”?",
     "section": "",
-    "text": "Enhancing AYON and creating comprehensive documentation is a time-consuming process and requires ongoing maintenance."
+    "text": "The game client is the application that users interact with. It connects to both Uro, our backend service, and directly to game servers.\nThe game editor is a separate tool used by game designers. They use it to create and upload new worlds, props, and avatars to the Uro backend.\nUro is the backend service for our game. It handles requests from both the game client and game editor. It stores and serves game assets like worlds, props, and avatars.\nGame servers are responsible for running the game logic in real-time. They communicate with the game clients to keep the game state synchronized between all players."
   },
   {
-    "objectID": "decisions/20231110-better-pipeline-tools.html#the-road-not-taken",
-    "href": "decisions/20231110-better-pipeline-tools.html#the-road-not-taken",
-    "title": "Proposed: Enhancing V-Sekai x Godot Engine x AYON for a Superior Workflow",
+    "objectID": "decisions/20240623-what-is-uro-backend.html#the-benefits",
+    "href": "decisions/20240623-what-is-uro-backend.html#the-benefits",
+    "title": "Proposed: Why did we build “Uro”?",
     "section": "",
-    "text": "An alternative option would be to develop an individual plugin or extension. However, this requires significant resources and may not be feasible for an open-source project."
+    "text": "Understanding the architecture of V-Sekai can help developers contribute more effectively to the project. It can also help users troubleshoot issues and understand the capabilities and limitations of the system."
   },
   {
-    "objectID": "decisions/20231110-better-pipeline-tools.html#the-infrequent-use-case",
-    "href": "decisions/20231110-better-pipeline-tools.html#the-infrequent-use-case",
-    "title": "Proposed: Enhancing V-Sekai x Godot Engine x AYON for a Superior Workflow",
+    "objectID": "decisions/20240623-what-is-uro-backend.html#the-downsides",
+    "href": "decisions/20240623-what-is-uro-backend.html#the-downsides",
+    "title": "Proposed: Why did we build “Uro”?",
     "section": "",
-    "text": "While developing a plugin or extension provides out-of-the-box functionality, it may not cover all use cases and could limit the diversity of social VR experiences."
+    "text": "The complexity of the architecture may be daunting for some, and there may be a learning curve involved in understanding it."
   },
   {
-    "objectID": "decisions/20231110-better-pipeline-tools.html#in-core-and-done-by-us",
-    "href": "decisions/20231110-better-pipeline-tools.html#in-core-and-done-by-us",
-    "title": "Proposed: Enhancing V-Sekai x Godot Engine x AYON for a Superior Workflow",
+    "objectID": "decisions/20240623-what-is-uro-backend.html#the-road-not-taken",
+    "href": "decisions/20240623-what-is-uro-backend.html#the-road-not-taken",
+    "title": "Proposed: Why did we build “Uro”?",
     "section": "",
-    "text": "By focusing on enhancing AYON and creating comprehensive documentation, we are empowering developers to implement these features in their own unique ways."
+    "text": "An alternative approach could have been to implement a Peer-to-Peer (P2P) architecture. In this setup, each game client also acts as a mini-server, communicating directly with other clients.\nAnother alternative would be to use cloud-based game backends such as Microsoft’s PlayFab. These services can automatically scale up or down based on demand, ensuring that there’s always enough capacity for all players.\nNakama is an open-source distributed social and realtime server for games and apps. It has a rich feature set including user accounts, chat, social, matchmaker, realtime multiplayer, and much more."
   },
   {
-    "objectID": "decisions/20231110-better-pipeline-tools.html#further-reading",
-    "href": "decisions/20231110-better-pipeline-tools.html#further-reading",
-    "title": "Proposed: Enhancing V-Sekai x Godot Engine x AYON for a Superior Workflow",
+    "objectID": "decisions/20240623-what-is-uro-backend.html#the-infrequent-use-case",
+    "href": "decisions/20240623-what-is-uro-backend.html#the-infrequent-use-case",
+    "title": "Proposed: Why did we build “Uro”?",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nAYON - The platform hosting our tools and editor\n\n\nThis article was assisted by Aria, an AI assistant."
+    "text": "The primary use case for the Uro server is to facilitate interactions between the game client and the game servers, there may be infrequent use cases where its functionality could be extended or used in different ways. For example, it is can be used to implement additional features such as leaderboards, achievements, or social networking features within the game. These use cases, while not common, should still be considered when designing and implementing the Uro server."
   },
   {
-    "objectID": "decisions/20221018-v-sekai-game-update-procedure.html",
-    "href": "decisions/20221018-v-sekai-game-update-procedure.html",
-    "title": "Proposed: To remember how to update the engine and game write a procedure",
+    "objectID": "decisions/20240623-what-is-uro-backend.html#in-core-and-done-by-us",
+    "href": "decisions/20240623-what-is-uro-backend.html#in-core-and-done-by-us",
+    "title": "Proposed: Why did we build “Uro”?",
     "section": "",
-    "text": "Status: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\n\nGodot Engine and V-Sekai are fast moving projects.\n\n\n\nWrite down how to update the engine and the game.\n\n\n\n\nFirst step: change the update_vsekai_godot script to push to a staging branch.\nNext step (lazy and simple): it is your responsibility to build the engine, run groups project and make sure it works.\nOptionally: you should perform an export build and make sure that works too.\nNext step (less lazy): we add another set of CI pipelines for staging godot -&gt; staging templates -&gt; staging groups and then we test that\nMost issues aren’t export related, so I think engine build + open project and run project is probably sufficient for most things and we need a script to push staging -&gt; groups-4.x\nWhich means everyone gets the upgraded engine\n\n\n\n\nCreating a standard procedure means people know what to do.\n\n\n\nIt’s complicated.\n\n\n\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\n\nThis is a procedure and not code.\n\n\n\nWe know how to do this and others don’t.\n\n\n\n\nV-Sekai\n\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "This proposal is core to the V-Sekai project and will be implemented by the V-Sekai development team."
   },
   {
-    "objectID": "decisions/20221018-v-sekai-game-update-procedure.html#context-and-problem-statement",
-    "href": "decisions/20221018-v-sekai-game-update-procedure.html#context-and-problem-statement",
-    "title": "Proposed: To remember how to update the engine and game write a procedure",
+    "objectID": "decisions/20240623-what-is-uro-backend.html#status",
+    "href": "decisions/20240623-what-is-uro-backend.html#status",
+    "title": "Proposed: Why did we build “Uro”?",
     "section": "",
-    "text": "Godot Engine and V-Sekai are fast moving projects."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20221018-v-sekai-game-update-procedure.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20221018-v-sekai-game-update-procedure.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: To remember how to update the engine and game write a procedure",
+    "objectID": "decisions/20240623-what-is-uro-backend.html#decision-makers",
+    "href": "decisions/20240623-what-is-uro-backend.html#decision-makers",
+    "title": "Proposed: Why did we build “Uro”?",
     "section": "",
-    "text": "Write down how to update the engine and the game."
+    "text": "V-Sekai development team\nFire\nAries"
   },
   {
-    "objectID": "decisions/20221018-v-sekai-game-update-procedure.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20221018-v-sekai-game-update-procedure.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: To remember how to update the engine and game write a procedure",
+    "objectID": "decisions/20240623-what-is-uro-backend.html#tags",
+    "href": "decisions/20240623-what-is-uro-backend.html#tags",
+    "title": "Proposed: Why did we build “Uro”?",
     "section": "",
-    "text": "First step: change the update_vsekai_godot script to push to a staging branch.\nNext step (lazy and simple): it is your responsibility to build the engine, run groups project and make sure it works.\nOptionally: you should perform an export build and make sure that works too.\nNext step (less lazy): we add another set of CI pipelines for staging godot -&gt; staging templates -&gt; staging groups and then we test that\nMost issues aren’t export related, so I think engine build + open project and run project is probably sufficient for most things and we need a script to push staging -&gt; groups-4.x\nWhich means everyone gets the upgraded engine"
+    "text": "V-Sekai\nUro Backend\nGame Architecture\nOpen-source Project\nGodot Engine"
   },
   {
-    "objectID": "decisions/20221018-v-sekai-game-update-procedure.html#positive-consequences",
-    "href": "decisions/20221018-v-sekai-game-update-procedure.html#positive-consequences",
-    "title": "Proposed: To remember how to update the engine and game write a procedure",
+    "objectID": "decisions/20240623-what-is-uro-backend.html#further-reading",
+    "href": "decisions/20240623-what-is-uro-backend.html#further-reading",
+    "title": "Proposed: Why did we build “Uro”?",
     "section": "",
-    "text": "Creating a standard procedure means people know what to do."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20221018-v-sekai-game-update-procedure.html#negative-consequences",
-    "href": "decisions/20221018-v-sekai-game-update-procedure.html#negative-consequences",
-    "title": "Proposed: To remember how to update the engine and game write a procedure",
+    "objectID": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html",
+    "href": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html",
+    "title": "Proposed: Replicate sync 100’000 entities using Godot Engine, mvsqlite and Foundationdb",
     "section": "",
-    "text": "It’s complicated."
+    "text": "Status: proposed\nDeciders: V-Sekai,fire,\nTags: V-Sekai,sync,view replication,\n\n\n\nSee replicate sync 100’000 entities using a solution.\n\n\n\nI propose we have groups of servers handling entities. Each server is synchronized with mvsqlite.\n\n\n\nWe assume we’re using Godot Engine 4 with float is doubles.\nThe servers do not share (independently access) the same memory or storage.\nWe can track the entity’s visibility and have a packed byte array per frame.\nUse mvsqlite in STRICT sql mode.\nUse the SQLite generated columns option STORED to optimize for reading and VIRTUAL to optimize for writing.\nCreate ECS style mvsqlite database for streaming and events (movement, health, avatar path and others).\nFor movement update the table once and only once per frame.\nFor avatar paths that change batch notify once per frame.\n\n\n\nimage\n\n\n\n\n\n\nThe code is using foundationdb’s share nothing architecture.\n\n\n\n\n\nWorried that latency will be above 20 milliseconds. It was shown in the graphs. May be a bug in mvsqlite with sequential key retries. Does the ownership / mastership of entities change often?\n\n\n\n\n\nOption: Current V-Sekai replication\nRejection Reason: Can’t link servers\n\n\n\n\nEntity replication is not trivial.\n\n\n\nWe’re doing the networking layer.\n\n\n\n\nfault-tolerance\ngodot-sqlite with mvsqlite\nnovus core\n\n\n\n\n[godot client alice] -&gt; [godot server alpha with mvsqlite |  [godot server alpha with mvsqlite| owns groups entities per tick\n  | have a way to track entities\n  | create, update and delete entity groups]]\n[godot client bob] -&gt; [godot server beta with mvsqlite |  [godot server beta with mvsqlite| owns groups entities per tick\n  | have a way to track entities\n  | create, update and delete entity groups]]\n[godot client carol] -&gt; [godot server gamma with mvsqlite |  [godot server gamma with mvsqlite| owns groups entities per tick\n  | have a way to track entities\n  | create, update and delete entity groups]]\n  [godot server alpha with mvsqlite] - [godot server beta with mvsqlite]\n  [godot server alpha with mvsqlite] - [godot server gamma with mvsqlite]\n  [godot server beta with mvsqlite] - [godot server gamma with mvsqlite]\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20221018-v-sekai-game-update-procedure.html#option-graveyard",
-    "href": "decisions/20221018-v-sekai-game-update-procedure.html#option-graveyard",
-    "title": "Proposed: To remember how to update the engine and game write a procedure",
+    "objectID": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#context-and-problem-statement",
+    "href": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#context-and-problem-statement",
+    "title": "Proposed: Replicate sync 100’000 entities using Godot Engine, mvsqlite and Foundationdb",
     "section": "",
-    "text": "Option: The status quo. \nRejection Reason: This solves nothing."
+    "text": "See replicate sync 100’000 entities using a solution."
   },
   {
-    "objectID": "decisions/20221018-v-sekai-game-update-procedure.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20221018-v-sekai-game-update-procedure.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: To remember how to update the engine and game write a procedure",
+    "objectID": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: Replicate sync 100’000 entities using Godot Engine, mvsqlite and Foundationdb",
     "section": "",
-    "text": "This is a procedure and not code."
+    "text": "I propose we have groups of servers handling entities. Each server is synchronized with mvsqlite."
   },
   {
-    "objectID": "decisions/20221018-v-sekai-game-update-procedure.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20221018-v-sekai-game-update-procedure.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: To remember how to update the engine and game write a procedure",
+    "objectID": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Replicate sync 100’000 entities using Godot Engine, mvsqlite and Foundationdb",
     "section": "",
-    "text": "We know how to do this and others don’t."
+    "text": "We assume we’re using Godot Engine 4 with float is doubles.\nThe servers do not share (independently access) the same memory or storage.\nWe can track the entity’s visibility and have a packed byte array per frame.\nUse mvsqlite in STRICT sql mode.\nUse the SQLite generated columns option STORED to optimize for reading and VIRTUAL to optimize for writing.\nCreate ECS style mvsqlite database for streaming and events (movement, health, avatar path and others).\nFor movement update the table once and only once per frame.\nFor avatar paths that change batch notify once per frame.\n\n\n\nimage"
   },
   {
-    "objectID": "decisions/20221018-v-sekai-game-update-procedure.html#references",
-    "href": "decisions/20221018-v-sekai-game-update-procedure.html#references",
-    "title": "Proposed: To remember how to update the engine and game write a procedure",
+    "objectID": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#positive-consequences",
+    "href": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#positive-consequences",
+    "title": "Proposed: Replicate sync 100’000 entities using Godot Engine, mvsqlite and Foundationdb",
     "section": "",
-    "text": "V-Sekai"
+    "text": "The code is using foundationdb’s share nothing architecture."
   },
   {
-    "objectID": "decisions/20221018-v-sekai-game-update-procedure.html#license-of-the-contribution",
-    "href": "decisions/20221018-v-sekai-game-update-procedure.html#license-of-the-contribution",
-    "title": "Proposed: To remember how to update the engine and game write a procedure",
+    "objectID": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#negative-consequences",
+    "href": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#negative-consequences",
+    "title": "Proposed: Replicate sync 100’000 entities using Godot Engine, mvsqlite and Foundationdb",
     "section": "",
-    "text": "Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Worried that latency will be above 20 milliseconds. It was shown in the graphs. May be a bug in mvsqlite with sequential key retries. Does the ownership / mastership of entities change often?"
   },
   {
-    "objectID": "decisions/20230913-V-Sekai-bugs.html",
-    "href": "decisions/20230913-V-Sekai-bugs.html",
-    "title": "Proposed: Challenges that need to be addressed in V-Sekai",
+    "objectID": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#option-graveyard",
+    "href": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#option-graveyard",
+    "title": "Proposed: Replicate sync 100’000 entities using Godot Engine, mvsqlite and Foundationdb",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nIn our quest to expand our community, we are faced with several challenges that need to be addressed.\n\n\n\nOur game has been QA Engineered by Facade, which was a great help. However, there are still issues that need to be resolved.\n\n\n\nWe have identified several areas of concern and have charted them in the following flow diagram:\ngraph TD\n    Crash[\"V-Sekai crash on start on RADV, Ubuntu 22.04.2 LTS (Jammy Jellyfish) #115\"]\n    VR[\"VR doesn't work #228\"]\n    Avatar[\"Restore avatar upload #243\"]\n    Uploads[\"Restore world uploads #244\"]\n    Mirror[\"Restore mirror in the preview server #249\"]\n    Freeze[\"Pressing escape button while ingame freezes client #250\"]\n    Escape[\"Escape button in menu should go back, instead does nothing #251\"]\n    Text[\"UI dropdown text is invisible until hovered #252\"]\n    Sensitivity[\"Increase default mouse sensitivity #253\"]\n    Gestures[\"Restore gestures #254\"]\n    VOIP[\"Restore VOIP #255\"]\n    IK[\"IK errors ingame #256\"]\n\n    Crash--&gt;VR\n    VR--&gt;Avatar\n    Avatar--&gt;Uploads\n    Uploads--&gt;Mirror\n    Mirror--&gt;Freeze\n    Freeze--&gt;Escape\n    Escape--&gt;Text\n    Text--&gt;Sensitivity\n    Sensitivity--&gt;Gestures\n    Gestures--&gt;VOIP\n    VOIP--&gt;IK\n\n\n\nAddressing these issues will significantly improve the user experience, making our game more enjoyable and accessible. This could lead to an increase in our user base and community engagement.\n\n\n\nThe process of resolving these issues may require significant time and resources. It might also involve some trial and error, which could potentially introduce new bugs or problems.\n\n\n\nIgnoring these issues is not an option as it would negatively impact the user experience and could hinder the growth of our community.\n\n\n\nWhile some of these issues might only affect a small number of users or occur under specific circumstances, it’s important to address them to ensure a smooth and enjoyable experience for all users.\n\n\n\nYes, these issues are core to the functionality of our game and should be addressed by our team.\n\n\n\n\nV-Sekai\nThis article is assisted by AI."
+    "text": "Option: Current V-Sekai replication\nRejection Reason: Can’t link servers"
   },
   {
-    "objectID": "decisions/20230913-V-Sekai-bugs.html#metadata",
-    "href": "decisions/20230913-V-Sekai-bugs.html#metadata",
-    "title": "Proposed: Challenges that need to be addressed in V-Sekai",
+    "objectID": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Replicate sync 100’000 entities using Godot Engine, mvsqlite and Foundationdb",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai"
+    "text": "Entity replication is not trivial."
   },
   {
-    "objectID": "decisions/20230913-V-Sekai-bugs.html#the-backdrop",
-    "href": "decisions/20230913-V-Sekai-bugs.html#the-backdrop",
-    "title": "Proposed: Challenges that need to be addressed in V-Sekai",
+    "objectID": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Replicate sync 100’000 entities using Godot Engine, mvsqlite and Foundationdb",
     "section": "",
-    "text": "In our quest to expand our community, we are faced with several challenges that need to be addressed."
+    "text": "We’re doing the networking layer."
   },
   {
-    "objectID": "decisions/20230913-V-Sekai-bugs.html#the-challenge",
-    "href": "decisions/20230913-V-Sekai-bugs.html#the-challenge",
-    "title": "Proposed: Challenges that need to be addressed in V-Sekai",
+    "objectID": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#references",
+    "href": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#references",
+    "title": "Proposed: Replicate sync 100’000 entities using Godot Engine, mvsqlite and Foundationdb",
     "section": "",
-    "text": "Our game has been QA Engineered by Facade, which was a great help. However, there are still issues that need to be resolved."
+    "text": "fault-tolerance\ngodot-sqlite with mvsqlite\nnovus core"
   },
   {
-    "objectID": "decisions/20230913-V-Sekai-bugs.html#the-strategy",
-    "href": "decisions/20230913-V-Sekai-bugs.html#the-strategy",
-    "title": "Proposed: Challenges that need to be addressed in V-Sekai",
+    "objectID": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#diagram-source",
+    "href": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#diagram-source",
+    "title": "Proposed: Replicate sync 100’000 entities using Godot Engine, mvsqlite and Foundationdb",
     "section": "",
-    "text": "We have identified several areas of concern and have charted them in the following flow diagram:\ngraph TD\n    Crash[\"V-Sekai crash on start on RADV, Ubuntu 22.04.2 LTS (Jammy Jellyfish) #115\"]\n    VR[\"VR doesn't work #228\"]\n    Avatar[\"Restore avatar upload #243\"]\n    Uploads[\"Restore world uploads #244\"]\n    Mirror[\"Restore mirror in the preview server #249\"]\n    Freeze[\"Pressing escape button while ingame freezes client #250\"]\n    Escape[\"Escape button in menu should go back, instead does nothing #251\"]\n    Text[\"UI dropdown text is invisible until hovered #252\"]\n    Sensitivity[\"Increase default mouse sensitivity #253\"]\n    Gestures[\"Restore gestures #254\"]\n    VOIP[\"Restore VOIP #255\"]\n    IK[\"IK errors ingame #256\"]\n\n    Crash--&gt;VR\n    VR--&gt;Avatar\n    Avatar--&gt;Uploads\n    Uploads--&gt;Mirror\n    Mirror--&gt;Freeze\n    Freeze--&gt;Escape\n    Escape--&gt;Text\n    Text--&gt;Sensitivity\n    Sensitivity--&gt;Gestures\n    Gestures--&gt;VOIP\n    VOIP--&gt;IK"
+    "text": "[godot client alice] -&gt; [godot server alpha with mvsqlite |  [godot server alpha with mvsqlite| owns groups entities per tick\n  | have a way to track entities\n  | create, update and delete entity groups]]\n[godot client bob] -&gt; [godot server beta with mvsqlite |  [godot server beta with mvsqlite| owns groups entities per tick\n  | have a way to track entities\n  | create, update and delete entity groups]]\n[godot client carol] -&gt; [godot server gamma with mvsqlite |  [godot server gamma with mvsqlite| owns groups entities per tick\n  | have a way to track entities\n  | create, update and delete entity groups]]\n  [godot server alpha with mvsqlite] - [godot server beta with mvsqlite]\n  [godot server alpha with mvsqlite] - [godot server gamma with mvsqlite]\n  [godot server beta with mvsqlite] - [godot server gamma with mvsqlite]"
   },
   {
-    "objectID": "decisions/20230913-V-Sekai-bugs.html#the-upside",
-    "href": "decisions/20230913-V-Sekai-bugs.html#the-upside",
-    "title": "Proposed: Challenges that need to be addressed in V-Sekai",
+    "objectID": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#derivative-license",
+    "href": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#derivative-license",
+    "title": "Proposed: Replicate sync 100’000 entities using Godot Engine, mvsqlite and Foundationdb",
     "section": "",
-    "text": "Addressing these issues will significantly improve the user experience, making our game more enjoyable and accessible. This could lead to an increase in our user base and community engagement."
+    "text": "Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230913-V-Sekai-bugs.html#the-downside",
-    "href": "decisions/20230913-V-Sekai-bugs.html#the-downside",
-    "title": "Proposed: Challenges that need to be addressed in V-Sekai",
+    "objectID": "decisions/20230531-godot-engine-ipad.html",
+    "href": "decisions/20230531-godot-engine-ipad.html",
+    "title": "Proposed: Build a Single-Instance MacOS Editor for the iPad",
     "section": "",
-    "text": "The process of resolving these issues may require significant time and resources. It might also involve some trial and error, which could potentially introduce new bugs or problems."
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, GPT-4, MacOS, iPad\n\n\n\n\nWe have successfully tested a MacOS editor on the iPhone in February 2023. Now, we want to build a similar editor for the iPad so that people can upload game worlds and avatars from a tablet. However, due to iOS limitations, it’s impossible to run multiple instances of the app or restart the app on non-jailbroken devices. Therefore, we need to adapt the existing codebase to work within these constraints.\n\n\n\n\nAdapt the existing MacOS editor codebase for the iPad without relying on multi-process architecture.\nTest the application on various iPad models to ensure compatibility and performance.\n\n\n\n\n\nClone the existing iPhone Godot Engine editor repository.\nCreate a new branch for the iPad version.\nModify the codebase to avoid using multi-process architecture:\n\nChange almost all global states (probably except UIApplication and view controller) to thread-local.\nRun multiple Godot instances in threads instead of processes.\n\nImplement the editor, import project folder, and export PCK to the filesystem. Our project requires SCN uploads to a web CDN.\nTest the application on different iPad models and fix any issues found during testing.\n\nInstall Xcode.\nGenerate certificates.\nUpload the Godot Engine iPad build to the iPad.\n\nMerge the iPad branch back into the main branch once the application is stable and fully functional.\n\n\n\n\n\nExpanding the availability of the MacOS editor to iPad users.\nReusing the existing codebase, reducing development time and effort.\n\n\n\n\n\nAdditional development and testing efforts required to support another platform.\nPotential maintenance overhead due to supporting multiple platforms.\n\n\n\n\n\nDeveloping a separate iPad-only application from scratch.\nUsing web-based editor solutions instead of a native app.\nImplementing a remote desktop solution to access a MacOS editor on a different device.\nPorting the MacOS editor to a cross-platform framework, potentially sacrificing performance and native features.\n\n\n\n\nNo, this enhancement requires significant changes to the existing codebase to properly support the iPad.\n\n\n\nYes, as the maintainers of Godot Engine, we have the expertise and knowledge of the codebase to efficiently adapt it for the iPad.\n\n\n\n\nV-Sekai\niPad fork of of Godot Engine"
   },
   {
-    "objectID": "decisions/20230913-V-Sekai-bugs.html#the-road-not-taken",
-    "href": "decisions/20230913-V-Sekai-bugs.html#the-road-not-taken",
-    "title": "Proposed: Challenges that need to be addressed in V-Sekai",
+    "objectID": "decisions/20230531-godot-engine-ipad.html#metadata",
+    "href": "decisions/20230531-godot-engine-ipad.html#metadata",
+    "title": "Proposed: Build a Single-Instance MacOS Editor for the iPad",
     "section": "",
-    "text": "Ignoring these issues is not an option as it would negatively impact the user experience and could hinder the growth of our community."
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, GPT-4, MacOS, iPad"
   },
   {
-    "objectID": "decisions/20230913-V-Sekai-bugs.html#the-infrequent-use-case",
-    "href": "decisions/20230913-V-Sekai-bugs.html#the-infrequent-use-case",
-    "title": "Proposed: Challenges that need to be addressed in V-Sekai",
+    "objectID": "decisions/20230531-godot-engine-ipad.html#context-and-problem-statement",
+    "href": "decisions/20230531-godot-engine-ipad.html#context-and-problem-statement",
+    "title": "Proposed: Build a Single-Instance MacOS Editor for the iPad",
     "section": "",
-    "text": "While some of these issues might only affect a small number of users or occur under specific circumstances, it’s important to address them to ensure a smooth and enjoyable experience for all users."
+    "text": "We have successfully tested a MacOS editor on the iPhone in February 2023. Now, we want to build a similar editor for the iPad so that people can upload game worlds and avatars from a tablet. However, due to iOS limitations, it’s impossible to run multiple instances of the app or restart the app on non-jailbroken devices. Therefore, we need to adapt the existing codebase to work within these constraints."
   },
   {
-    "objectID": "decisions/20230913-V-Sekai-bugs.html#in-core-and-done-by-us",
-    "href": "decisions/20230913-V-Sekai-bugs.html#in-core-and-done-by-us",
-    "title": "Proposed: Challenges that need to be addressed in V-Sekai",
+    "objectID": "decisions/20230531-godot-engine-ipad.html#proposed-solution",
+    "href": "decisions/20230531-godot-engine-ipad.html#proposed-solution",
+    "title": "Proposed: Build a Single-Instance MacOS Editor for the iPad",
     "section": "",
-    "text": "Yes, these issues are core to the functionality of our game and should be addressed by our team."
+    "text": "Adapt the existing MacOS editor codebase for the iPad without relying on multi-process architecture.\nTest the application on various iPad models to ensure compatibility and performance."
   },
   {
-    "objectID": "decisions/20230913-V-Sekai-bugs.html#further-reading",
-    "href": "decisions/20230913-V-Sekai-bugs.html#further-reading",
-    "title": "Proposed: Challenges that need to be addressed in V-Sekai",
+    "objectID": "decisions/20230531-godot-engine-ipad.html#implementation",
+    "href": "decisions/20230531-godot-engine-ipad.html#implementation",
+    "title": "Proposed: Build a Single-Instance MacOS Editor for the iPad",
     "section": "",
-    "text": "V-Sekai\nThis article is assisted by AI."
+    "text": "Clone the existing iPhone Godot Engine editor repository.\nCreate a new branch for the iPad version.\nModify the codebase to avoid using multi-process architecture:\n\nChange almost all global states (probably except UIApplication and view controller) to thread-local.\nRun multiple Godot instances in threads instead of processes.\n\nImplement the editor, import project folder, and export PCK to the filesystem. Our project requires SCN uploads to a web CDN.\nTest the application on different iPad models and fix any issues found during testing.\n\nInstall Xcode.\nGenerate certificates.\nUpload the Godot Engine iPad build to the iPad.\n\nMerge the iPad branch back into the main branch once the application is stable and fully functional."
   },
   {
-    "objectID": "decisions/20211031-use-our-custom-fullbody-ik.html",
-    "href": "decisions/20211031-use-our-custom-fullbody-ik.html",
-    "title": "Accepted: Use our custom fullbody IK",
+    "objectID": "decisions/20230531-godot-engine-ipad.html#positive-consequences",
+    "href": "decisions/20230531-godot-engine-ipad.html#positive-consequences",
+    "title": "Proposed: Build a Single-Instance MacOS Editor for the iPad",
     "section": "",
-    "text": "Accepted: Use our custom fullbody IK\n\nContext and Problem Statement\nWe need to animater our characters in game using full body ik.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nEWBIK is a full body ik.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nEWBIK\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nCode is already complicated.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nI and Eron know.\n\n\nReferences\n\nEWBIK\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Expanding the availability of the MacOS editor to iPad users.\nReusing the existing codebase, reducing development time and effort."
   },
   {
-    "objectID": "decisions/20231114-maintain-svgcleaner.html",
-    "href": "decisions/20231114-maintain-svgcleaner.html",
-    "title": "Proposed: Enhancing VR Book Reading through SVG Optimization",
+    "objectID": "decisions/20230531-godot-engine-ipad.html#negative-consequences",
+    "href": "decisions/20230531-godot-engine-ipad.html#negative-consequences",
+    "title": "Proposed: Build a Single-Instance MacOS Editor for the iPad",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: SVG Optimization, VR Book Reading, V-Sekai\n\n\n\n\nV-Sekai is dedicated to advancing the immersive experience in social VR. We can enhance VR book reading, a feature that demands high-quality visuals with efficient resource usage.\n\n\n\nIntegrating readable, high-quality SVG-based books into the VR environment presents a dual challenge of maintaining visual clarity while optimizing performance.\n\n\n\nUtilize the svgcleaner tool, particularly its Rust implementation, to optimize SVG files for VR book reading. This involves cleaning up SVG files from unnecessary data, thereby reducing file size without compromising visual integrity.\n\n\n\nOptimized SVGs lead to faster load times, smoother performance, and an overall enhanced user experience in VR book reading. This aligns with V-Sekai’s goal of creating a seamless and engaging VR environment.\n\n\n\nThe svgcleaner tool, particularly its Rust version, is currently archived and read-only, indicating a need for refresh or redevelopment.\n\n\n\nAlternative SVG optimization methods or tools might exist but could lack the specific features or efficiency provided by svgcleaner.\n\n\n\nWhile primarily aimed at VR book reading, this optimization could benefit other areas of V-Sekai where SVGs are used.\n\n\n\nThe task involves integrating an external tool (svgcleaner) into the core V-Sekai development process, possibly requiring custom adaptation for the specific VR context.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\nsvgcleaner on GitHub - The GitHub repository for svgcleaner, a tool to optimize SVG files.\n\nThis article was assisted by AI assistant Aria."
+    "text": "Additional development and testing efforts required to support another platform.\nPotential maintenance overhead due to supporting multiple platforms."
   },
   {
-    "objectID": "decisions/20231114-maintain-svgcleaner.html#metadata",
-    "href": "decisions/20231114-maintain-svgcleaner.html#metadata",
-    "title": "Proposed: Enhancing VR Book Reading through SVG Optimization",
+    "objectID": "decisions/20230531-godot-engine-ipad.html#option-graveyard",
+    "href": "decisions/20230531-godot-engine-ipad.html#option-graveyard",
+    "title": "Proposed: Build a Single-Instance MacOS Editor for the iPad",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: SVG Optimization, VR Book Reading, V-Sekai"
+    "text": "Developing a separate iPad-only application from scratch.\nUsing web-based editor solutions instead of a native app.\nImplementing a remote desktop solution to access a MacOS editor on a different device.\nPorting the MacOS editor to a cross-platform framework, potentially sacrificing performance and native features."
   },
   {
-    "objectID": "decisions/20231114-maintain-svgcleaner.html#the-backdrop",
-    "href": "decisions/20231114-maintain-svgcleaner.html#the-backdrop",
-    "title": "Proposed: Enhancing VR Book Reading through SVG Optimization",
+    "objectID": "decisions/20230531-godot-engine-ipad.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230531-godot-engine-ipad.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Build a Single-Instance MacOS Editor for the iPad",
     "section": "",
-    "text": "V-Sekai is dedicated to advancing the immersive experience in social VR. We can enhance VR book reading, a feature that demands high-quality visuals with efficient resource usage."
+    "text": "No, this enhancement requires significant changes to the existing codebase to properly support the iPad."
   },
   {
-    "objectID": "decisions/20231114-maintain-svgcleaner.html#the-challenge",
-    "href": "decisions/20231114-maintain-svgcleaner.html#the-challenge",
-    "title": "Proposed: Enhancing VR Book Reading through SVG Optimization",
+    "objectID": "decisions/20230531-godot-engine-ipad.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230531-godot-engine-ipad.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Build a Single-Instance MacOS Editor for the iPad",
     "section": "",
-    "text": "Integrating readable, high-quality SVG-based books into the VR environment presents a dual challenge of maintaining visual clarity while optimizing performance."
+    "text": "Yes, as the maintainers of Godot Engine, we have the expertise and knowledge of the codebase to efficiently adapt it for the iPad."
   },
   {
-    "objectID": "decisions/20231114-maintain-svgcleaner.html#the-strategy",
-    "href": "decisions/20231114-maintain-svgcleaner.html#the-strategy",
-    "title": "Proposed: Enhancing VR Book Reading through SVG Optimization",
+    "objectID": "decisions/20230531-godot-engine-ipad.html#references",
+    "href": "decisions/20230531-godot-engine-ipad.html#references",
+    "title": "Proposed: Build a Single-Instance MacOS Editor for the iPad",
     "section": "",
-    "text": "Utilize the svgcleaner tool, particularly its Rust implementation, to optimize SVG files for VR book reading. This involves cleaning up SVG files from unnecessary data, thereby reducing file size without compromising visual integrity."
+    "text": "V-Sekai\niPad fork of of Godot Engine"
   },
   {
-    "objectID": "decisions/20231114-maintain-svgcleaner.html#the-upside",
-    "href": "decisions/20231114-maintain-svgcleaner.html#the-upside",
-    "title": "Proposed: Enhancing VR Book Reading through SVG Optimization",
+    "objectID": "decisions/20240914-godot-engine-xr-elite-conference-setup.html",
+    "href": "decisions/20240914-godot-engine-xr-elite-conference-setup.html",
+    "title": "Accepted: Godot Engine XR Elite HMD Conference Setup",
     "section": "",
-    "text": "Optimized SVGs lead to faster load times, smoother performance, and an overall enhanced user experience in VR book reading. This aligns with V-Sekai’s goal of creating a seamless and engaging VR environment."
+    "text": "Fire, an independent developer previously contracted with the Godot Foundation, plans to demonstrate the capabilities of the Godot Engine XR Team’s work on the VIVE headset at an upcoming conference. This setup is crucial for showcasing advanced VR features using the XR Elite Headset.\n\n\n\nSetting up a reliable and efficient demonstration environment for the XR Elite Headset at a conference can be challenging due to potential network issues and hardware integration complexities.\n\n\n\nThe proposed setup involves several components to ensure a stable and high-performance demonstration:\n\nHardware Connection:\n\nConnect the XR Elite Headset to a USB-C hub.\nAttach the Vive Ultimate Tracker dongle and a Belkin USB-C to Gigabit Ethernet Adapter to the hub.\n\nNetwork Configuration:\n\nUse a wired ethernet connection to avoid Wi-Fi instability common in conference venues.\nSet a fixed IP address for the VIVE Business Streaming server using the VBSIpSetting.exe tool.\n\nSoftware Setup:\n\nEnsure the business streaming server has a physical display connected to prevent the SteamVR overlay issue.\nRun SteamVR for VR demonstrations.\n\nAdditional Stability Measures:\n\nDisable Wi-Fi on the XR Elite Headset to rely solely on the wired connection.\nConsider using a gigabit travel router/switch to manage and shorten routing internally at the venue.\n\n\n\n\n\n\nReliability: Wired connections reduce the risk of connectivity issues during live demonstrations.\nPerformance: Direct network connections and optimized settings ensure smooth operation of VR applications.\nProfessional Presentation: A stable setup reflects well on the Godot Engine project and its capabilities in VR.\n\n\n\n\n\nComplexity: The setup requires careful configuration and might be daunting for less technical users.\nEquipment Dependency: Relies on specific hardware and software that may not be readily available at all venues.\n\n\n\n\nAlternative simpler setups were considered but rejected due to their reliance on less stable wireless connections which could compromise the demonstration’s effectiveness.\n\n\n\nIn cases where a direct internet connection is unavailable, additional configurations like mobile routers or other networking equipment might be necessary.\n\n\n\nThis proposal aligns with our core mission to showcase the best of Godot Engine’s VR capabilities and will be implemented by fire with support from the V-Sekai development team.\n\n\n\nStatus: Accepted \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20231114-maintain-svgcleaner.html#the-downside",
-    "href": "decisions/20231114-maintain-svgcleaner.html#the-downside",
-    "title": "Proposed: Enhancing VR Book Reading through SVG Optimization",
+    "objectID": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#the-context",
+    "href": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#the-context",
+    "title": "Accepted: Godot Engine XR Elite HMD Conference Setup",
     "section": "",
-    "text": "The svgcleaner tool, particularly its Rust version, is currently archived and read-only, indicating a need for refresh or redevelopment."
+    "text": "Fire, an independent developer previously contracted with the Godot Foundation, plans to demonstrate the capabilities of the Godot Engine XR Team’s work on the VIVE headset at an upcoming conference. This setup is crucial for showcasing advanced VR features using the XR Elite Headset."
   },
   {
-    "objectID": "decisions/20231114-maintain-svgcleaner.html#the-road-not-taken",
-    "href": "decisions/20231114-maintain-svgcleaner.html#the-road-not-taken",
-    "title": "Proposed: Enhancing VR Book Reading through SVG Optimization",
+    "objectID": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#the-problem-statement",
+    "href": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#the-problem-statement",
+    "title": "Accepted: Godot Engine XR Elite HMD Conference Setup",
     "section": "",
-    "text": "Alternative SVG optimization methods or tools might exist but could lack the specific features or efficiency provided by svgcleaner."
+    "text": "Setting up a reliable and efficient demonstration environment for the XR Elite Headset at a conference can be challenging due to potential network issues and hardware integration complexities."
   },
   {
-    "objectID": "decisions/20231114-maintain-svgcleaner.html#the-infrequent-use-case",
-    "href": "decisions/20231114-maintain-svgcleaner.html#the-infrequent-use-case",
-    "title": "Proposed: Enhancing VR Book Reading through SVG Optimization",
+    "objectID": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Accepted: Godot Engine XR Elite HMD Conference Setup",
     "section": "",
-    "text": "While primarily aimed at VR book reading, this optimization could benefit other areas of V-Sekai where SVGs are used."
+    "text": "The proposed setup involves several components to ensure a stable and high-performance demonstration:\n\nHardware Connection:\n\nConnect the XR Elite Headset to a USB-C hub.\nAttach the Vive Ultimate Tracker dongle and a Belkin USB-C to Gigabit Ethernet Adapter to the hub.\n\nNetwork Configuration:\n\nUse a wired ethernet connection to avoid Wi-Fi instability common in conference venues.\nSet a fixed IP address for the VIVE Business Streaming server using the VBSIpSetting.exe tool.\n\nSoftware Setup:\n\nEnsure the business streaming server has a physical display connected to prevent the SteamVR overlay issue.\nRun SteamVR for VR demonstrations.\n\nAdditional Stability Measures:\n\nDisable Wi-Fi on the XR Elite Headset to rely solely on the wired connection.\nConsider using a gigabit travel router/switch to manage and shorten routing internally at the venue."
   },
   {
-    "objectID": "decisions/20231114-maintain-svgcleaner.html#in-core-and-done-by-us",
-    "href": "decisions/20231114-maintain-svgcleaner.html#in-core-and-done-by-us",
-    "title": "Proposed: Enhancing VR Book Reading through SVG Optimization",
+    "objectID": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#the-benefits",
+    "href": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#the-benefits",
+    "title": "Accepted: Godot Engine XR Elite HMD Conference Setup",
     "section": "",
-    "text": "The task involves integrating an external tool (svgcleaner) into the core V-Sekai development process, possibly requiring custom adaptation for the specific VR context."
+    "text": "Reliability: Wired connections reduce the risk of connectivity issues during live demonstrations.\nPerformance: Direct network connections and optimized settings ensure smooth operation of VR applications.\nProfessional Presentation: A stable setup reflects well on the Godot Engine project and its capabilities in VR."
   },
   {
-    "objectID": "decisions/20231114-maintain-svgcleaner.html#further-reading",
-    "href": "decisions/20231114-maintain-svgcleaner.html#further-reading",
-    "title": "Proposed: Enhancing VR Book Reading through SVG Optimization",
+    "objectID": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#the-downsides",
+    "href": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#the-downsides",
+    "title": "Accepted: Godot Engine XR Elite HMD Conference Setup",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\nsvgcleaner on GitHub - The GitHub repository for svgcleaner, a tool to optimize SVG files.\n\nThis article was assisted by AI assistant Aria."
+    "text": "Complexity: The setup requires careful configuration and might be daunting for less technical users.\nEquipment Dependency: Relies on specific hardware and software that may not be readily available at all venues."
   },
   {
-    "objectID": "decisions/20231108-munich-godot-engine-conference.html",
-    "href": "decisions/20231108-munich-godot-engine-conference.html",
-    "title": "Proposed: Enhancing V-Sekai Through Effective Documentation",
+    "objectID": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#the-road-not-taken",
+    "href": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#the-road-not-taken",
+    "title": "Accepted: Godot Engine XR Elite HMD Conference Setup",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nLyuma, a member of the V-Sekai team, recently attended the Godot Engine Munich 2023 conference. Three key takeaways from the event were the importance of friendship, Gemütlichkeit (a German term for a state of warmth, friendliness, and good cheer), and the critical role of documentation.\n\n\n\nOne of the challenges faced by V-Sekai is ensuring that all processes and systems are well-documented. This is crucial for maintaining consistency, facilitating knowledge transfer, and enabling efficient problem-solving.\n\n\n\nTo overcome this challenge, the strategy is to prioritize documentation in all projects. This involves creating comprehensive guides, manuals, and references that detail how different systems work and how to use them effectively.\n\n\n\nThe upside of this approach is that it can significantly improve the efficiency and effectiveness of the team. With proper documentation, team members can quickly understand and navigate different systems, reducing the time spent on troubleshooting and problem-solving.\n\n\n\nThe downside is that creating and maintaining documentation can be time-consuming. However, the benefits of having well-documented systems far outweigh the costs.\n\n\n\nAn alternative approach could have been to rely on informal knowledge transfer methods, such as one-on-one training or mentoring. However, this approach lacks the consistency and scalability of formal documentation.\n\n\n\nIn cases where systems or processes are rarely used or subject to frequent changes, maintaining up-to-date documentation might be challenging. In such scenarios, a combination of documentation and hands-on training might be more effective.\n\n\n\nThe decision to prioritize documentation is proposed by V-Sekai.\n\n\n\n\nV-Sekai\n\nThis article was assisted by Aria, an AI."
+    "text": "Alternative simpler setups were considered but rejected due to their reliance on less stable wireless connections which could compromise the demonstration’s effectiveness."
   },
   {
-    "objectID": "decisions/20231108-munich-godot-engine-conference.html#metadata",
-    "href": "decisions/20231108-munich-godot-engine-conference.html#metadata",
-    "title": "Proposed: Enhancing V-Sekai Through Effective Documentation",
+    "objectID": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#the-infrequent-use-case",
+    "href": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#the-infrequent-use-case",
+    "title": "Accepted: Godot Engine XR Elite HMD Conference Setup",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai"
+    "text": "In cases where a direct internet connection is unavailable, additional configurations like mobile routers or other networking equipment might be necessary."
   },
   {
-    "objectID": "decisions/20231108-munich-godot-engine-conference.html#the-backdrop",
-    "href": "decisions/20231108-munich-godot-engine-conference.html#the-backdrop",
-    "title": "Proposed: Enhancing V-Sekai Through Effective Documentation",
+    "objectID": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#in-core-and-done-by-us",
+    "href": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#in-core-and-done-by-us",
+    "title": "Accepted: Godot Engine XR Elite HMD Conference Setup",
     "section": "",
-    "text": "Lyuma, a member of the V-Sekai team, recently attended the Godot Engine Munich 2023 conference. Three key takeaways from the event were the importance of friendship, Gemütlichkeit (a German term for a state of warmth, friendliness, and good cheer), and the critical role of documentation."
+    "text": "This proposal aligns with our core mission to showcase the best of Godot Engine’s VR capabilities and will be implemented by fire with support from the V-Sekai development team."
   },
   {
-    "objectID": "decisions/20231108-munich-godot-engine-conference.html#the-challenge",
-    "href": "decisions/20231108-munich-godot-engine-conference.html#the-challenge",
-    "title": "Proposed: Enhancing V-Sekai Through Effective Documentation",
+    "objectID": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#status",
+    "href": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#status",
+    "title": "Accepted: Godot Engine XR Elite HMD Conference Setup",
     "section": "",
-    "text": "One of the challenges faced by V-Sekai is ensuring that all processes and systems are well-documented. This is crucial for maintaining consistency, facilitating knowledge transfer, and enabling efficient problem-solving."
+    "text": "Status: Accepted"
   },
   {
-    "objectID": "decisions/20231108-munich-godot-engine-conference.html#the-strategy",
-    "href": "decisions/20231108-munich-godot-engine-conference.html#the-strategy",
-    "title": "Proposed: Enhancing V-Sekai Through Effective Documentation",
+    "objectID": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#decision-makers",
+    "href": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#decision-makers",
+    "title": "Accepted: Godot Engine XR Elite HMD Conference Setup",
     "section": "",
-    "text": "To overcome this challenge, the strategy is to prioritize documentation in all projects. This involves creating comprehensive guides, manuals, and references that detail how different systems work and how to use them effectively."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20231108-munich-godot-engine-conference.html#the-upside",
-    "href": "decisions/20231108-munich-godot-engine-conference.html#the-upside",
-    "title": "Proposed: Enhancing V-Sekai Through Effective Documentation",
+    "objectID": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#tags",
+    "href": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#tags",
+    "title": "Accepted: Godot Engine XR Elite HMD Conference Setup",
     "section": "",
-    "text": "The upside of this approach is that it can significantly improve the efficiency and effectiveness of the team. With proper documentation, team members can quickly understand and navigate different systems, reducing the time spent on troubleshooting and problem-solving."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20231108-munich-godot-engine-conference.html#the-downside",
-    "href": "decisions/20231108-munich-godot-engine-conference.html#the-downside",
-    "title": "Proposed: Enhancing V-Sekai Through Effective Documentation",
+    "objectID": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#further-reading",
+    "href": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#further-reading",
+    "title": "Accepted: Godot Engine XR Elite HMD Conference Setup",
     "section": "",
-    "text": "The downside is that creating and maintaining documentation can be time-consuming. However, the benefits of having well-documented systems far outweigh the costs."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20231108-munich-godot-engine-conference.html#the-road-not-taken",
-    "href": "decisions/20231108-munich-godot-engine-conference.html#the-road-not-taken",
-    "title": "Proposed: Enhancing V-Sekai Through Effective Documentation",
+    "objectID": "decisions/20231114-elixir-definition-of-godot-types.html",
+    "href": "decisions/20231114-elixir-definition-of-godot-types.html",
+    "title": "Proposed: Defining the List of Godot Types in Elixir Godot Parsers",
     "section": "",
-    "text": "An alternative approach could have been to rely on informal knowledge transfer methods, such as one-on-one training or mentoring. However, this approach lacks the consistency and scalability of formal documentation."
+    "text": "Status: Proposed\nDeciders: V-Sekai Development Team\nTags: Godot Engine, Elixir, Type Definitions, V-Sekai\n\n\n\n\nThe elixir_godot_parsers project under V-Sekai aims to enhance the integration and parsing capabilities between the Elixir programming language and the Godot Engine. A key component of this is understanding and effectively parsing various data types used in Godot.\n\n\n\nCurrently, there may be ambiguities or a lack of clear definition for all Godot types within the elixir_godot_parsers project. This can lead to inconsistencies in parsing and handling data, potentially affecting the efficiency and reliability of the integration.\n\n\n\nPropose the creation of a comprehensive, well-documented list of all Godot types. This list should be detailed and include specifications for each type, ensuring clarity and consistency in how Elixir handles and parses these types.\n\n\n\nDefining a clear list of Godot types will enhance the reliability and functionality of the Elixir-Godot integration. This will make the development process smoother, reduce bugs, and improve the overall efficiency of projects using both Elixir and Godot.\n\n\n\nCompiling and maintaining this list could be time-consuming. It may also require regular updates to stay in sync with any changes or updates in the Godot Engine.\n\n\n\nAn alternative approach could be to continue without a defined list, relying on ad-hoc solutions for each type as needed. However, this could lead to increased development time and potential errors.\n\n\n\nWhile this proposal primarily targets the Elixir-Godot integration, having a well-defined list of types could also be beneficial for other projects or integrations involving the Godot Engine.\n\n\n\nThis task involves direct contributions to the core functionality of the elixir_godot_parsers project under V-Sekai, aiming to enhance its core capabilities in terms of data handling and parsing.\n\n\n\n\nV-Sekai GitHub Repository - The official GitHub account for the V-Sekai development community, focusing on social VR functionality for the Godot Engine.\nElixir Godot Parsers Repository - The GitHub page for the elixir_godot_parsers project, part of V-Sekai’s efforts to integrate Elixir with the Godot Engine.\n\nThis proposal was created with the assistance of AI assistant Aria."
   },
   {
-    "objectID": "decisions/20231108-munich-godot-engine-conference.html#the-infrequent-use-case",
-    "href": "decisions/20231108-munich-godot-engine-conference.html#the-infrequent-use-case",
-    "title": "Proposed: Enhancing V-Sekai Through Effective Documentation",
+    "objectID": "decisions/20231114-elixir-definition-of-godot-types.html#metadata",
+    "href": "decisions/20231114-elixir-definition-of-godot-types.html#metadata",
+    "title": "Proposed: Defining the List of Godot Types in Elixir Godot Parsers",
     "section": "",
-    "text": "In cases where systems or processes are rarely used or subject to frequent changes, maintaining up-to-date documentation might be challenging. In such scenarios, a combination of documentation and hands-on training might be more effective."
+    "text": "Status: Proposed\nDeciders: V-Sekai Development Team\nTags: Godot Engine, Elixir, Type Definitions, V-Sekai"
   },
   {
-    "objectID": "decisions/20231108-munich-godot-engine-conference.html#in-core-and-done-by-us",
-    "href": "decisions/20231108-munich-godot-engine-conference.html#in-core-and-done-by-us",
-    "title": "Proposed: Enhancing V-Sekai Through Effective Documentation",
+    "objectID": "decisions/20231114-elixir-definition-of-godot-types.html#the-backdrop",
+    "href": "decisions/20231114-elixir-definition-of-godot-types.html#the-backdrop",
+    "title": "Proposed: Defining the List of Godot Types in Elixir Godot Parsers",
     "section": "",
-    "text": "The decision to prioritize documentation is proposed by V-Sekai."
+    "text": "The elixir_godot_parsers project under V-Sekai aims to enhance the integration and parsing capabilities between the Elixir programming language and the Godot Engine. A key component of this is understanding and effectively parsing various data types used in Godot."
   },
   {
-    "objectID": "decisions/20231108-munich-godot-engine-conference.html#further-reading",
-    "href": "decisions/20231108-munich-godot-engine-conference.html#further-reading",
-    "title": "Proposed: Enhancing V-Sekai Through Effective Documentation",
+    "objectID": "decisions/20231114-elixir-definition-of-godot-types.html#the-challenge",
+    "href": "decisions/20231114-elixir-definition-of-godot-types.html#the-challenge",
+    "title": "Proposed: Defining the List of Godot Types in Elixir Godot Parsers",
     "section": "",
-    "text": "V-Sekai\n\nThis article was assisted by Aria, an AI."
+    "text": "Currently, there may be ambiguities or a lack of clear definition for all Godot types within the elixir_godot_parsers project. This can lead to inconsistencies in parsing and handling data, potentially affecting the efficiency and reliability of the integration."
   },
   {
-    "objectID": "decisions/20211031-character-workshop.html",
-    "href": "decisions/20211031-character-workshop.html",
-    "title": "Proposed: Character workshop",
+    "objectID": "decisions/20231114-elixir-definition-of-godot-types.html#the-strategy",
+    "href": "decisions/20231114-elixir-definition-of-godot-types.html#the-strategy",
+    "title": "Proposed: Defining the List of Godot Types in Elixir Godot Parsers",
     "section": "",
-    "text": "Proposed: Character workshop\n\nContext and Problem Statement\nCharacters are hard. Make it easier.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nMake a workshop for working with 3d characters.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nAuto rig a 3d obj.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNo idea.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nI can do this!\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Propose the creation of a comprehensive, well-documented list of all Godot types. This list should be detailed and include specifications for each type, ensuring clarity and consistency in how Elixir handles and parses these types."
   },
   {
-    "objectID": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html",
-    "href": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html",
-    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Silverblue and #steam",
+    "objectID": "decisions/20231114-elixir-definition-of-godot-types.html#the-upside",
+    "href": "decisions/20231114-elixir-definition-of-godot-types.html#the-upside",
+    "title": "Proposed: Defining the List of Godot Types in Elixir Godot Parsers",
     "section": "",
-    "text": "Status: rejected \nDeciders: V-Sekai,fire,\nTags: V-Sekai,\n\n\n\nI don’t have a #steam Deck since it was delayed til February 2022 to test V-Sekai.\n\n\n\nInstall Fedora Kinoite and Steam.\n\n\n\n\nInstall Ventoy on a USB Stick\nInstall iso of Fedora Silverblue onto the drive on Ventoy\nInstall Fedora Silverblue onto hardware proxy defined in another proposal.\nInstall #steam via RPMFusion\n\n\n\n\n\nAble to test builds from Windows?\n\n\n\n\n\nUnknown\n\n\n\n\n\nOption: Use Arch Manjaro\nRejection Reason: Unfamiliar with OS.\nOption: Use Arch Manjaro\nRejection Reason: Unfamiliar with OS.\n\n\n\n\nNot lines of code.\n\n\n\nQA testing needs to be inhouse.\n\n\n\n\nhttps://en.wikipedia.org/wiki/Steam_Deck\nhttps://download.fedoraproject.org/pub/fedora/linux/releases/35/Kinoite/x86_64/iso/Fedora-Kinoite-ostree-x86_64-35-1.2.iso\n\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Defining a clear list of Godot types will enhance the reliability and functionality of the Elixir-Godot integration. This will make the development process smoother, reduce bugs, and improve the overall efficiency of projects using both Elixir and Godot."
   },
   {
-    "objectID": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html#context-and-problem-statement",
-    "href": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html#context-and-problem-statement",
-    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Silverblue and #steam",
+    "objectID": "decisions/20231114-elixir-definition-of-godot-types.html#the-downside",
+    "href": "decisions/20231114-elixir-definition-of-godot-types.html#the-downside",
+    "title": "Proposed: Defining the List of Godot Types in Elixir Godot Parsers",
     "section": "",
-    "text": "I don’t have a #steam Deck since it was delayed til February 2022 to test V-Sekai."
+    "text": "Compiling and maintaining this list could be time-consuming. It may also require regular updates to stay in sync with any changes or updates in the Godot Engine."
   },
   {
-    "objectID": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Silverblue and #steam",
+    "objectID": "decisions/20231114-elixir-definition-of-godot-types.html#the-road-not-taken",
+    "href": "decisions/20231114-elixir-definition-of-godot-types.html#the-road-not-taken",
+    "title": "Proposed: Defining the List of Godot Types in Elixir Godot Parsers",
     "section": "",
-    "text": "Install Fedora Kinoite and Steam."
+    "text": "An alternative approach could be to continue without a defined list, relying on ad-hoc solutions for each type as needed. However, this could lead to increased development time and potential errors."
   },
   {
-    "objectID": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Silverblue and #steam",
+    "objectID": "decisions/20231114-elixir-definition-of-godot-types.html#the-infrequent-use-case",
+    "href": "decisions/20231114-elixir-definition-of-godot-types.html#the-infrequent-use-case",
+    "title": "Proposed: Defining the List of Godot Types in Elixir Godot Parsers",
     "section": "",
-    "text": "Install Ventoy on a USB Stick\nInstall iso of Fedora Silverblue onto the drive on Ventoy\nInstall Fedora Silverblue onto hardware proxy defined in another proposal.\nInstall #steam via RPMFusion"
+    "text": "While this proposal primarily targets the Elixir-Godot integration, having a well-defined list of types could also be beneficial for other projects or integrations involving the Godot Engine."
   },
   {
-    "objectID": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html#positive-consequences",
-    "href": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html#positive-consequences",
-    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Silverblue and #steam",
+    "objectID": "decisions/20231114-elixir-definition-of-godot-types.html#in-core-and-done-by-us",
+    "href": "decisions/20231114-elixir-definition-of-godot-types.html#in-core-and-done-by-us",
+    "title": "Proposed: Defining the List of Godot Types in Elixir Godot Parsers",
     "section": "",
-    "text": "Able to test builds from Windows?"
+    "text": "This task involves direct contributions to the core functionality of the elixir_godot_parsers project under V-Sekai, aiming to enhance its core capabilities in terms of data handling and parsing."
   },
   {
-    "objectID": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html#negative-consequences",
-    "href": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html#negative-consequences",
-    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Silverblue and #steam",
+    "objectID": "decisions/20231114-elixir-definition-of-godot-types.html#further-reading",
+    "href": "decisions/20231114-elixir-definition-of-godot-types.html#further-reading",
+    "title": "Proposed: Defining the List of Godot Types in Elixir Godot Parsers",
     "section": "",
-    "text": "Unknown"
+    "text": "V-Sekai GitHub Repository - The official GitHub account for the V-Sekai development community, focusing on social VR functionality for the Godot Engine.\nElixir Godot Parsers Repository - The GitHub page for the elixir_godot_parsers project, part of V-Sekai’s efforts to integrate Elixir with the Godot Engine.\n\nThis proposal was created with the assistance of AI assistant Aria."
   },
   {
-    "objectID": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html#option-graveyard",
-    "href": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html#option-graveyard",
-    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Silverblue and #steam",
+    "objectID": "decisions/20231105-pdf-embed-raster-svg-vr.html",
+    "href": "decisions/20231105-pdf-embed-raster-svg-vr.html",
+    "title": "Proposed: PDF to SVG Conversion for VR Books",
     "section": "",
-    "text": "Option: Use Arch Manjaro\nRejection Reason: Unfamiliar with OS.\nOption: Use Arch Manjaro\nRejection Reason: Unfamiliar with OS."
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nThe idea of converting PDFs to SVGs with raster image embeds for use in a VR book reader is an exciting project. However, dealing with PDF conversion can be challenging, especially when it comes to more complex tasks.\n\n\n\nThe main challenge lies in the conversion process from PDF to SVG while maintaining the quality and integrity of the original content. This includes handling raster embeds and ensuring they are correctly displayed in the Godot engine.\n\n\n\nThe proposed workflow involves taking a PDF page with potential raster embeds, running it through svgcleaner, and then using it in the Godot engine. The goal is to create a CBZ where the images are SVGs.\n\n\n\nThis approach allows for the creation of high-quality, interactive VR books. It also leverages the capabilities of the Godot engine, which supports SVG, PNG, and JPG embeds.\n\n\n\nThe complexity of the conversion process may present some challenges. Additionally, the quality of the final product will heavily depend on the quality of the original PDF and its embedded raster images.\n\n\n\nAn alternative approach could involve converting the PDF to another format that might be easier to work with. However, this would likely result in a loss of quality and may not support the desired interactivity.\n\n\n\nThis workflow may not be suitable for all types of PDFs, particularly those with complex layouts or numerous embedded images.\n\n\n\nThe implementation of this workflow would require a deep understanding of both the PDF and SVG formats, as well as the Godot engine. It would likely be a significant undertaking.\n\n\n\n\nV-Sekai\n\nThis article was assisted by AI."
   },
   {
-    "objectID": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Silverblue and #steam",
+    "objectID": "decisions/20231105-pdf-embed-raster-svg-vr.html#metadata",
+    "href": "decisions/20231105-pdf-embed-raster-svg-vr.html#metadata",
+    "title": "Proposed: PDF to SVG Conversion for VR Books",
     "section": "",
-    "text": "Not lines of code."
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Silverblue and #steam",
+    "objectID": "decisions/20231105-pdf-embed-raster-svg-vr.html#the-backdrop",
+    "href": "decisions/20231105-pdf-embed-raster-svg-vr.html#the-backdrop",
+    "title": "Proposed: PDF to SVG Conversion for VR Books",
     "section": "",
-    "text": "QA testing needs to be inhouse."
+    "text": "The idea of converting PDFs to SVGs with raster image embeds for use in a VR book reader is an exciting project. However, dealing with PDF conversion can be challenging, especially when it comes to more complex tasks."
   },
   {
-    "objectID": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html#references",
-    "href": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html#references",
-    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Silverblue and #steam",
+    "objectID": "decisions/20231105-pdf-embed-raster-svg-vr.html#the-challenge",
+    "href": "decisions/20231105-pdf-embed-raster-svg-vr.html#the-challenge",
+    "title": "Proposed: PDF to SVG Conversion for VR Books",
     "section": "",
-    "text": "https://en.wikipedia.org/wiki/Steam_Deck\nhttps://download.fedoraproject.org/pub/fedora/linux/releases/35/Kinoite/x86_64/iso/Fedora-Kinoite-ostree-x86_64-35-1.2.iso"
+    "text": "The main challenge lies in the conversion process from PDF to SVG while maintaining the quality and integrity of the original content. This includes handling raster embeds and ensuring they are correctly displayed in the Godot engine."
   },
   {
-    "objectID": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html#derivative-license",
-    "href": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html#derivative-license",
-    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Silverblue and #steam",
+    "objectID": "decisions/20231105-pdf-embed-raster-svg-vr.html#the-strategy",
+    "href": "decisions/20231105-pdf-embed-raster-svg-vr.html#the-strategy",
+    "title": "Proposed: PDF to SVG Conversion for VR Books",
     "section": "",
-    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "The proposed workflow involves taking a PDF page with potential raster embeds, running it through svgcleaner, and then using it in the Godot engine. The goal is to create a CBZ where the images are SVGs."
   },
   {
-    "objectID": "decisions/20211031-godot-database-viewer-for-proposals.html",
-    "href": "decisions/20211031-godot-database-viewer-for-proposals.html",
-    "title": "Proposed: Godot Database viewer for proposals",
+    "objectID": "decisions/20231105-pdf-embed-raster-svg-vr.html#the-upside",
+    "href": "decisions/20231105-pdf-embed-raster-svg-vr.html#the-upside",
+    "title": "Proposed: PDF to SVG Conversion for VR Books",
     "section": "",
-    "text": "[Describe the problem or limitation you are having in your project]\n[Describe the context and problem statement, e.g., in free form using two to three sentences. You may want to articulate the problem in the form of a question.]\n\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\n\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\n\n\n\n\n[e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]\n[…]\n\n\n\n\n\n[e.g., compromising quality attribute, follow-up decisions required, …]\n[…]\n\n[this section can be repeated for each option if more than one option is open for consideration]\n\n\n\n\nOption: \nRejection Reason: \n\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\n\n\n\nIs there a reason why this should be core and done by us?\n\n\n\n\nLink type \n… \n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "This approach allows for the creation of high-quality, interactive VR books. It also leverages the capabilities of the Godot engine, which supports SVG, PNG, and JPG embeds."
   },
   {
-    "objectID": "decisions/20211031-godot-database-viewer-for-proposals.html#context-and-problem-statement",
-    "href": "decisions/20211031-godot-database-viewer-for-proposals.html#context-and-problem-statement",
-    "title": "Proposed: Godot Database viewer for proposals",
+    "objectID": "decisions/20231105-pdf-embed-raster-svg-vr.html#the-downside",
+    "href": "decisions/20231105-pdf-embed-raster-svg-vr.html#the-downside",
+    "title": "Proposed: PDF to SVG Conversion for VR Books",
     "section": "",
-    "text": "[Describe the problem or limitation you are having in your project]\n[Describe the context and problem statement, e.g., in free form using two to three sentences. You may want to articulate the problem in the form of a question.]"
+    "text": "The complexity of the conversion process may present some challenges. Additionally, the quality of the final product will heavily depend on the quality of the original PDF and its embedded raster images."
   },
   {
-    "objectID": "decisions/20211031-godot-database-viewer-for-proposals.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20211031-godot-database-viewer-for-proposals.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: Godot Database viewer for proposals",
+    "objectID": "decisions/20231105-pdf-embed-raster-svg-vr.html#the-road-not-taken",
+    "href": "decisions/20231105-pdf-embed-raster-svg-vr.html#the-road-not-taken",
+    "title": "Proposed: PDF to SVG Conversion for VR Books",
     "section": "",
-    "text": "Describe the proposed option and how it helps to overcome the problem or limitation"
+    "text": "An alternative approach could involve converting the PDF to another format that might be easier to work with. However, this would likely result in a loss of quality and may not support the desired interactivity."
   },
   {
-    "objectID": "decisions/20211031-godot-database-viewer-for-proposals.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20211031-godot-database-viewer-for-proposals.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Godot Database viewer for proposals",
+    "objectID": "decisions/20231105-pdf-embed-raster-svg-vr.html#the-infrequent-use-case",
+    "href": "decisions/20231105-pdf-embed-raster-svg-vr.html#the-infrequent-use-case",
+    "title": "Proposed: PDF to SVG Conversion for VR Books",
     "section": "",
-    "text": "Describe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams"
+    "text": "This workflow may not be suitable for all types of PDFs, particularly those with complex layouts or numerous embedded images."
   },
   {
-    "objectID": "decisions/20211031-godot-database-viewer-for-proposals.html#positive-consequences",
-    "href": "decisions/20211031-godot-database-viewer-for-proposals.html#positive-consequences",
-    "title": "Proposed: Godot Database viewer for proposals",
+    "objectID": "decisions/20231105-pdf-embed-raster-svg-vr.html#in-core-and-done-by-us",
+    "href": "decisions/20231105-pdf-embed-raster-svg-vr.html#in-core-and-done-by-us",
+    "title": "Proposed: PDF to SVG Conversion for VR Books",
     "section": "",
-    "text": "[e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]\n[…]"
+    "text": "The implementation of this workflow would require a deep understanding of both the PDF and SVG formats, as well as the Godot engine. It would likely be a significant undertaking."
   },
   {
-    "objectID": "decisions/20211031-godot-database-viewer-for-proposals.html#negative-consequences",
-    "href": "decisions/20211031-godot-database-viewer-for-proposals.html#negative-consequences",
-    "title": "Proposed: Godot Database viewer for proposals",
+    "objectID": "decisions/20231105-pdf-embed-raster-svg-vr.html#further-reading",
+    "href": "decisions/20231105-pdf-embed-raster-svg-vr.html#further-reading",
+    "title": "Proposed: PDF to SVG Conversion for VR Books",
     "section": "",
-    "text": "[e.g., compromising quality attribute, follow-up decisions required, …]\n[…]\n\n[this section can be repeated for each option if more than one option is open for consideration]"
+    "text": "V-Sekai\n\nThis article was assisted by AI."
   },
   {
-    "objectID": "decisions/20211031-godot-database-viewer-for-proposals.html#option-graveyard",
-    "href": "decisions/20211031-godot-database-viewer-for-proposals.html#option-graveyard",
-    "title": "Proposed: Godot Database viewer for proposals",
+    "objectID": "decisions/20240218-vrm-substance-editor.html",
+    "href": "decisions/20240218-vrm-substance-editor.html",
+    "title": "Proposed VRM mtoon in Substance Designer",
     "section": "",
-    "text": "Option: \nRejection Reason:"
+    "text": "VRM is a file format for handling 3D humanoid avatars in VR applications. It’s designed to be a versatile and exchangeable format across various systems. mtoon is a toon shader used with VRM models to give them a distinct, stylized look that emulates 2D animation within a 3D space.\nSubstance Designer is a powerful node-based texturing tool essential for creating realistic textures for 3D models. By implementing mtoon support in Substance Designer, we can bridge the gap between high-quality texture design and VRM character customization.\n\n\n\nThe current workflow for applying toon shading to VRM models is disconnected from the process of designing textures, often requiring multiple tools and manual adjustments. We aim to simplify the workflow by integrating mtoon support directly into Substance Designer, allowing for a more cohesive and efficient design process.\n\n\n\nThe implementation would involve developing a custom Substance Designer node set or a template that encapsulates mtoon’s parameters and replicates its shading model within the Substance Designer environment. This would allow artists to preview and tweak the toon shader settings in real-time while crafting the textures.\nA mock-up interface would present these parameters within Substance Designer, where each one directly corresponds to a property in the VRM mtoon shader.\n\n\n\n\nStreamlined Workflow: Artists can create and adjust VRM textures and toon shaders all within Substance Designer.\nReal-time Previews: Immediate feedback on how changes to textures and shader parameters impact the final appearance.\nConsistency: Reduces discrepancies between the design phase and the final rendering in VR applications.\n\n\n\n\n\nDevelopment Time: Significant time investment required to develop and maintain the custom node set/template.\nComplexity: Adds an additional layer of complexity within Substance Designer, which could be overwhelming for new users.\nNiche Audience: The feature might only cater to a relatively small audience of VRM content creators.\n\n\n\n\nWe could have chosen to maintain the status quo, requiring VRM creators to switch between multiple tools to finalize their avatar’s appearance. However, this would prolong the existing inefficiencies in the production pipeline.\n\n\n\nWhile most VRM mtoon use cases involve common elements like lit colors and normal maps, less frequent use cases could involve highly custom properties such as UV animations or unique rim lighting effects.\n\n\n\nThe development of this feature would be in-house, ensuring deep integration with existing Substance Designer systems and full control over the implementation and updates.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team and community stakeholders.\n\n\n\n\n\nV-Sekai, Avatar Customization, AI, Facial Expressions\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article.\nBelow is a table of parameters for the proposed VRM mtoon Substance Designer node set/template:\n\n\n\n\n\n\n\n\n\n\n\nRank\nParameter\nType\nDescription\nImpact Level\nRange\n\n\n\n\n1\n_Color\nvec4\nLit Color, Alpha (Lit RGB, Alpha A)\nHigh\n[0, 1]\n\n\n2\n_MainTex\ntexture\nMain Texture (RGB)\nHigh\n[0, 1]\n\n\n3\n_ShadeColor\nvec4\nShade Color (Shade RGB)\nHigh\n[0, 1]\n\n\n4\n_ShadeTexture\ntexture\nShade Texture (RGB)\nHigh\n[0, 1]\n\n\n5\n_ShadeToony\nfloat\nShading Toony (0.0 is Lambert. Higher value get toony shading.)\nHigh\n[0.0, 1.0]\n\n\n6\n_RimColor\nvec4\nRim Color (RGB)\nHigh\n[0, 1]\n\n\n7\n_RimTexture\ntexture\nRim Texture (RGB)\nHigh\n[0, 1]\n\n\n8\n_EmissionColor\nvec4\nEmission Color (RGB)\nHigh\n[0, 1]\n\n\n9\n_EmissionMap\ntexture\nEmission Map (RGB)\nHigh\n[0, 1]\n\n\n10\n_Cutoff\nfloat\nAlpha Cutoff (Discard pixels below this value in Cutout mode)\nHigh\n[0.0, 1.0]\n\n\n11\n_AlphaCutoutEnable\nint\nRendering Type (TransparentWithZWrite mode can cause problems with rendering.)\nHigh\n{0, 1}\n\n\n12\n_MainTex_ST\nvec4\nUV Offset (UV Scale X,Y, UV Offset X,Y)\nHigh\n[0, 1]\n\n\n13\n_BumpScale\nvec2\nNormal Map and Multiplier for normals in tangent space\nHigh\n[0.0, 1.0]\n\n\n14\n_BumpMap\ntexture\nNormal Map (RGB)\nHigh\n[0, 1]\n\n\n15\n_OutlineWidth\nfloat\nWidth (Outline Width)\nHigh\n[0.01, ∞)\n\n\n16\n_OutlineWidthTexture\ntexture\nOutline Width Texture (R)\nHigh\n[0, 1]\n\n\n17\n_OutlineColor\nvec4\nOutline Color (RGB)\nHigh\n[0, 1]\n\n\n18\n_SphereAdd\ntexture\nMatCap Texture (RGB)\nSubtle\n[0, 1]\n\n\n19\n_ShadeShift\nfloat\nShading Shift (Zero is Default. Negative value increase lit area. Positive value increase shade area.)\nModerate\n[-1.0, ∞)\n\n\n20\n_ReceiveShadowRate\nfloat\nShadow Receive (Texture R * Rate. White is Default. Black attenuates shadows.)\nModerate\n[0.0, 1.0]\n\n\n21\n_ReceiveShadowTexture\ntexture\nReceive Shadow Texture (R)\nModerate\n[0, 1]\n\n\n22\n_ShadingGradeRate\nfloat\nShading Grade (Lit & Shade Mixing Multiplier: Texture R * Rate. Compatible with UTS2 ShadingGradeMap. White is Default. Black amplifies shade.)\nModerate\n[0.0, 1.0]\n\n\n23\n_ShadingGradeTexture\ntexture\nShading Grade Texture (R)\nModerate\n[0, 1]\n\n\n24\n_LightColorAttenuation\nfloat\nLight Color Attenuation\nModerate\n[0.0, ∞)\n\n\n25\n_IndirectLightIntensity\nfloat\nGI Intensity (Indirect Light Intensity)\nModerate\n[0.0, ∞)\n\n\n26\n_MatcapColor\nvec4\nMatCap Color (Color multiplied with Additive Sphere map / MatCap Texture RGB)\nSubtle\n[0, 1]\n\n\n27\n_RimLightingMix\nfloat\nRim Lighting Mix\nSubtle\n[0.0, 1.0]\n\n\n28\n_RimFresnelPower\nfloat\nFresnel Power (If you increase this value, you get sharper rim light.)\nSubtle\n[0.0, 100.0]\n\n\n29\n_RimLift\nfloat\nRim Lift (If you increase this value, you can lift rim light.)\nSubtle\n[0.0, ∞)\n\n\n30\n_OutlineWidthMode\nint\nMode (None = outline pass disabled; World = outline in world coordinates; Screen = screen pixel thickness)\nOutline-Specific\n{0, 1, 2}\n\n\n31\n_OutlineScaledMaxDistance\nfloat\nOutline Scaled Distance (Width Scaled Max Distance)\nOutline-Specific\n[1.0, 10.0]\n\n\n32\n_OutlineColorMode\nint\nColor Mode (FixedColor = unshaded; MixedLighting = match environment light (recommended))\nOutline-Specific\n{0, 1}\n\n\n33\n_OutlineLightingMix\nfloat\nOutline Mix (Outline Lighting Mix)\nOutline-Specific\n[0.0, 1.0]\n\n\n34\n_UvAnimMaskTexture\ntexture\nAuto Animation Mask Texture (R)\nUV Animation\n[0, 1]\n\n\n35\n_UvAnimScrollX\nfloat\nUV Scroll X (per second)\nUV Animation\n[-100.0, 100.0]\n\n\n36\n_UvAnimScrollY\nfloat\nUV Scroll Y (per second)\nUV Animation\n[-100.0, 100.0]\n\n\n37\n_UvAnimRotation\nfloat\nUV Rotation (per second)\nUV Animation\n[-100.0, 100.0]\n\n\n38\n_DebugMode\nint\nVisualize (Debugging Visualization: Normal or Lighting)\nDebugging\n{0, 1, 2}"
   },
   {
-    "objectID": "decisions/20211031-godot-database-viewer-for-proposals.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20211031-godot-database-viewer-for-proposals.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Godot Database viewer for proposals",
+    "objectID": "decisions/20240218-vrm-substance-editor.html#the-context",
+    "href": "decisions/20240218-vrm-substance-editor.html#the-context",
+    "title": "Proposed VRM mtoon in Substance Designer",
     "section": "",
-    "text": "If this enhancement will not be used often, can it be worked around with a few lines of script?"
+    "text": "VRM is a file format for handling 3D humanoid avatars in VR applications. It’s designed to be a versatile and exchangeable format across various systems. mtoon is a toon shader used with VRM models to give them a distinct, stylized look that emulates 2D animation within a 3D space.\nSubstance Designer is a powerful node-based texturing tool essential for creating realistic textures for 3D models. By implementing mtoon support in Substance Designer, we can bridge the gap between high-quality texture design and VRM character customization."
   },
   {
-    "objectID": "decisions/20211031-godot-database-viewer-for-proposals.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20211031-godot-database-viewer-for-proposals.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Godot Database viewer for proposals",
+    "objectID": "decisions/20240218-vrm-substance-editor.html#the-problem-statement",
+    "href": "decisions/20240218-vrm-substance-editor.html#the-problem-statement",
+    "title": "Proposed VRM mtoon in Substance Designer",
     "section": "",
-    "text": "Is there a reason why this should be core and done by us?"
+    "text": "The current workflow for applying toon shading to VRM models is disconnected from the process of designing textures, often requiring multiple tools and manual adjustments. We aim to simplify the workflow by integrating mtoon support directly into Substance Designer, allowing for a more cohesive and efficient design process."
   },
   {
-    "objectID": "decisions/20211031-godot-database-viewer-for-proposals.html#references",
-    "href": "decisions/20211031-godot-database-viewer-for-proposals.html#references",
-    "title": "Proposed: Godot Database viewer for proposals",
+    "objectID": "decisions/20240218-vrm-substance-editor.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240218-vrm-substance-editor.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed VRM mtoon in Substance Designer",
     "section": "",
-    "text": "Link type \n…"
+    "text": "The implementation would involve developing a custom Substance Designer node set or a template that encapsulates mtoon’s parameters and replicates its shading model within the Substance Designer environment. This would allow artists to preview and tweak the toon shader settings in real-time while crafting the textures.\nA mock-up interface would present these parameters within Substance Designer, where each one directly corresponds to a property in the VRM mtoon shader."
   },
   {
-    "objectID": "decisions/20211031-godot-database-viewer-for-proposals.html#derivative-license",
-    "href": "decisions/20211031-godot-database-viewer-for-proposals.html#derivative-license",
-    "title": "Proposed: Godot Database viewer for proposals",
+    "objectID": "decisions/20240218-vrm-substance-editor.html#the-benefits",
+    "href": "decisions/20240218-vrm-substance-editor.html#the-benefits",
+    "title": "Proposed VRM mtoon in Substance Designer",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Streamlined Workflow: Artists can create and adjust VRM textures and toon shaders all within Substance Designer.\nReal-time Previews: Immediate feedback on how changes to textures and shader parameters impact the final appearance.\nConsistency: Reduces discrepancies between the design phase and the final rendering in VR applications."
   },
   {
-    "objectID": "decisions/20230508-novel-3d-views.html",
-    "href": "decisions/20230508-novel-3d-views.html",
-    "title": "Draft: Convert segmented front facing 3D Garment images to novel 3d views for 3d modeling",
+    "objectID": "decisions/20240218-vrm-substance-editor.html#the-downsides",
+    "href": "decisions/20240218-vrm-substance-editor.html#the-downsides",
+    "title": "Proposed VRM mtoon in Substance Designer",
     "section": "",
-    "text": "Status: draft \nDeciders: V-Sekai, fire,\nTags: V-Sekai, ChatGPT-4\n\n\n\n\nWe want to create 3D models from a front-shot of the garment.\n\n\n\nUse Meta’s image segmentation model and zero123’s 3D reconstruction algorithm to generate novel 3D views of garments from a single front-shot image.\n\n\n\n\nPreprocess the input image: Resize and normalize the input image to meet the requirements of Meta’s image segmentation model.\nExtract the garment using Meta’s image segmentation model:\n\nLoad the pre-trained Meta’s image segmentation model.\nPass the preprocessed input image through the model to obtain the segmented garment image.\n\nPrepare the segmented garment for 3D reconstruction:\n\nLoad segmented garment image into zero123’s 3D novel view algorithm.\n\nApply zero123’s 3D reconstruction algorithm:\n\nLoad the pre-trained zero123’s 3D reconstruction model.\nPass the prepared segmented garment image through the model to generate novel 3d views of the garment.\n\nGenerate novel 3D views of the garment:\n\nRotate the 3D camera at intervals of 20 degrees around the garment to capture multiple 3D views.\n\nManually model the garment using views:\n\nUse a 3d design tool like Blender to create a mesh.\n\n\n\n\n\n\nEnhanced user experience with realistic 3D garment previews.\nImproved understanding of garment fit and style.\nIncreased creator satisfaction.\n\n\n\n\n\nPotential increase in computational resources required for processing.\nPossible limitations in accuracy and quality of generated 3D models.\n\n\n\n\n\nUsing multiple images for 3D reconstruction (discarded due to not enough aligned input images for 3D construction).\n\n\n\n\nNo, this enhancement requires integration of advanced image segmentation and 3D reconstruction algorithms, which cannot be achieved with a simple script.\n\n\n\nYes, implementing this feature as part of our core project will improve our opensource community of creators.\n\n\n\n\nV-Sekai"
+    "text": "Development Time: Significant time investment required to develop and maintain the custom node set/template.\nComplexity: Adds an additional layer of complexity within Substance Designer, which could be overwhelming for new users.\nNiche Audience: The feature might only cater to a relatively small audience of VRM content creators."
   },
   {
-    "objectID": "decisions/20230508-novel-3d-views.html#metadata",
-    "href": "decisions/20230508-novel-3d-views.html#metadata",
-    "title": "Draft: Convert segmented front facing 3D Garment images to novel 3d views for 3d modeling",
+    "objectID": "decisions/20240218-vrm-substance-editor.html#the-road-not-taken",
+    "href": "decisions/20240218-vrm-substance-editor.html#the-road-not-taken",
+    "title": "Proposed VRM mtoon in Substance Designer",
     "section": "",
-    "text": "Status: draft \nDeciders: V-Sekai, fire,\nTags: V-Sekai, ChatGPT-4"
+    "text": "We could have chosen to maintain the status quo, requiring VRM creators to switch between multiple tools to finalize their avatar’s appearance. However, this would prolong the existing inefficiencies in the production pipeline."
   },
   {
-    "objectID": "decisions/20230508-novel-3d-views.html#context-and-problem-statement",
-    "href": "decisions/20230508-novel-3d-views.html#context-and-problem-statement",
-    "title": "Draft: Convert segmented front facing 3D Garment images to novel 3d views for 3d modeling",
+    "objectID": "decisions/20240218-vrm-substance-editor.html#the-infrequent-use-case",
+    "href": "decisions/20240218-vrm-substance-editor.html#the-infrequent-use-case",
+    "title": "Proposed VRM mtoon in Substance Designer",
     "section": "",
-    "text": "We want to create 3D models from a front-shot of the garment."
+    "text": "While most VRM mtoon use cases involve common elements like lit colors and normal maps, less frequent use cases could involve highly custom properties such as UV animations or unique rim lighting effects."
   },
   {
-    "objectID": "decisions/20230508-novel-3d-views.html#proposed-solution",
-    "href": "decisions/20230508-novel-3d-views.html#proposed-solution",
-    "title": "Draft: Convert segmented front facing 3D Garment images to novel 3d views for 3d modeling",
+    "objectID": "decisions/20240218-vrm-substance-editor.html#in-core-and-done-by-us",
+    "href": "decisions/20240218-vrm-substance-editor.html#in-core-and-done-by-us",
+    "title": "Proposed VRM mtoon in Substance Designer",
     "section": "",
-    "text": "Use Meta’s image segmentation model and zero123’s 3D reconstruction algorithm to generate novel 3D views of garments from a single front-shot image."
+    "text": "The development of this feature would be in-house, ensuring deep integration with existing Substance Designer systems and full control over the implementation and updates."
   },
   {
-    "objectID": "decisions/20230508-novel-3d-views.html#implementation",
-    "href": "decisions/20230508-novel-3d-views.html#implementation",
-    "title": "Draft: Convert segmented front facing 3D Garment images to novel 3d views for 3d modeling",
+    "objectID": "decisions/20240218-vrm-substance-editor.html#status",
+    "href": "decisions/20240218-vrm-substance-editor.html#status",
+    "title": "Proposed VRM mtoon in Substance Designer",
     "section": "",
-    "text": "Preprocess the input image: Resize and normalize the input image to meet the requirements of Meta’s image segmentation model.\nExtract the garment using Meta’s image segmentation model:\n\nLoad the pre-trained Meta’s image segmentation model.\nPass the preprocessed input image through the model to obtain the segmented garment image.\n\nPrepare the segmented garment for 3D reconstruction:\n\nLoad segmented garment image into zero123’s 3D novel view algorithm.\n\nApply zero123’s 3D reconstruction algorithm:\n\nLoad the pre-trained zero123’s 3D reconstruction model.\nPass the prepared segmented garment image through the model to generate novel 3d views of the garment.\n\nGenerate novel 3D views of the garment:\n\nRotate the 3D camera at intervals of 20 degrees around the garment to capture multiple 3D views.\n\nManually model the garment using views:\n\nUse a 3d design tool like Blender to create a mesh."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20230508-novel-3d-views.html#positive-consequences",
-    "href": "decisions/20230508-novel-3d-views.html#positive-consequences",
-    "title": "Draft: Convert segmented front facing 3D Garment images to novel 3d views for 3d modeling",
+    "objectID": "decisions/20240218-vrm-substance-editor.html#decision-makers",
+    "href": "decisions/20240218-vrm-substance-editor.html#decision-makers",
+    "title": "Proposed VRM mtoon in Substance Designer",
     "section": "",
-    "text": "Enhanced user experience with realistic 3D garment previews.\nImproved understanding of garment fit and style.\nIncreased creator satisfaction."
+    "text": "V-Sekai development team and community stakeholders."
   },
   {
-    "objectID": "decisions/20230508-novel-3d-views.html#negative-consequences",
-    "href": "decisions/20230508-novel-3d-views.html#negative-consequences",
-    "title": "Draft: Convert segmented front facing 3D Garment images to novel 3d views for 3d modeling",
+    "objectID": "decisions/20240218-vrm-substance-editor.html#tags",
+    "href": "decisions/20240218-vrm-substance-editor.html#tags",
+    "title": "Proposed VRM mtoon in Substance Designer",
     "section": "",
-    "text": "Potential increase in computational resources required for processing.\nPossible limitations in accuracy and quality of generated 3D models."
+    "text": "V-Sekai, Avatar Customization, AI, Facial Expressions"
   },
   {
-    "objectID": "decisions/20230508-novel-3d-views.html#option-graveyard",
-    "href": "decisions/20230508-novel-3d-views.html#option-graveyard",
-    "title": "Draft: Convert segmented front facing 3D Garment images to novel 3d views for 3d modeling",
+    "objectID": "decisions/20240218-vrm-substance-editor.html#further-reading",
+    "href": "decisions/20240218-vrm-substance-editor.html#further-reading",
+    "title": "Proposed VRM mtoon in Substance Designer",
     "section": "",
-    "text": "Using multiple images for 3D reconstruction (discarded due to not enough aligned input images for 3D construction)."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article.\nBelow is a table of parameters for the proposed VRM mtoon Substance Designer node set/template:\n\n\n\n\n\n\n\n\n\n\n\nRank\nParameter\nType\nDescription\nImpact Level\nRange\n\n\n\n\n1\n_Color\nvec4\nLit Color, Alpha (Lit RGB, Alpha A)\nHigh\n[0, 1]\n\n\n2\n_MainTex\ntexture\nMain Texture (RGB)\nHigh\n[0, 1]\n\n\n3\n_ShadeColor\nvec4\nShade Color (Shade RGB)\nHigh\n[0, 1]\n\n\n4\n_ShadeTexture\ntexture\nShade Texture (RGB)\nHigh\n[0, 1]\n\n\n5\n_ShadeToony\nfloat\nShading Toony (0.0 is Lambert. Higher value get toony shading.)\nHigh\n[0.0, 1.0]\n\n\n6\n_RimColor\nvec4\nRim Color (RGB)\nHigh\n[0, 1]\n\n\n7\n_RimTexture\ntexture\nRim Texture (RGB)\nHigh\n[0, 1]\n\n\n8\n_EmissionColor\nvec4\nEmission Color (RGB)\nHigh\n[0, 1]\n\n\n9\n_EmissionMap\ntexture\nEmission Map (RGB)\nHigh\n[0, 1]\n\n\n10\n_Cutoff\nfloat\nAlpha Cutoff (Discard pixels below this value in Cutout mode)\nHigh\n[0.0, 1.0]\n\n\n11\n_AlphaCutoutEnable\nint\nRendering Type (TransparentWithZWrite mode can cause problems with rendering.)\nHigh\n{0, 1}\n\n\n12\n_MainTex_ST\nvec4\nUV Offset (UV Scale X,Y, UV Offset X,Y)\nHigh\n[0, 1]\n\n\n13\n_BumpScale\nvec2\nNormal Map and Multiplier for normals in tangent space\nHigh\n[0.0, 1.0]\n\n\n14\n_BumpMap\ntexture\nNormal Map (RGB)\nHigh\n[0, 1]\n\n\n15\n_OutlineWidth\nfloat\nWidth (Outline Width)\nHigh\n[0.01, ∞)\n\n\n16\n_OutlineWidthTexture\ntexture\nOutline Width Texture (R)\nHigh\n[0, 1]\n\n\n17\n_OutlineColor\nvec4\nOutline Color (RGB)\nHigh\n[0, 1]\n\n\n18\n_SphereAdd\ntexture\nMatCap Texture (RGB)\nSubtle\n[0, 1]\n\n\n19\n_ShadeShift\nfloat\nShading Shift (Zero is Default. Negative value increase lit area. Positive value increase shade area.)\nModerate\n[-1.0, ∞)\n\n\n20\n_ReceiveShadowRate\nfloat\nShadow Receive (Texture R * Rate. White is Default. Black attenuates shadows.)\nModerate\n[0.0, 1.0]\n\n\n21\n_ReceiveShadowTexture\ntexture\nReceive Shadow Texture (R)\nModerate\n[0, 1]\n\n\n22\n_ShadingGradeRate\nfloat\nShading Grade (Lit & Shade Mixing Multiplier: Texture R * Rate. Compatible with UTS2 ShadingGradeMap. White is Default. Black amplifies shade.)\nModerate\n[0.0, 1.0]\n\n\n23\n_ShadingGradeTexture\ntexture\nShading Grade Texture (R)\nModerate\n[0, 1]\n\n\n24\n_LightColorAttenuation\nfloat\nLight Color Attenuation\nModerate\n[0.0, ∞)\n\n\n25\n_IndirectLightIntensity\nfloat\nGI Intensity (Indirect Light Intensity)\nModerate\n[0.0, ∞)\n\n\n26\n_MatcapColor\nvec4\nMatCap Color (Color multiplied with Additive Sphere map / MatCap Texture RGB)\nSubtle\n[0, 1]\n\n\n27\n_RimLightingMix\nfloat\nRim Lighting Mix\nSubtle\n[0.0, 1.0]\n\n\n28\n_RimFresnelPower\nfloat\nFresnel Power (If you increase this value, you get sharper rim light.)\nSubtle\n[0.0, 100.0]\n\n\n29\n_RimLift\nfloat\nRim Lift (If you increase this value, you can lift rim light.)\nSubtle\n[0.0, ∞)\n\n\n30\n_OutlineWidthMode\nint\nMode (None = outline pass disabled; World = outline in world coordinates; Screen = screen pixel thickness)\nOutline-Specific\n{0, 1, 2}\n\n\n31\n_OutlineScaledMaxDistance\nfloat\nOutline Scaled Distance (Width Scaled Max Distance)\nOutline-Specific\n[1.0, 10.0]\n\n\n32\n_OutlineColorMode\nint\nColor Mode (FixedColor = unshaded; MixedLighting = match environment light (recommended))\nOutline-Specific\n{0, 1}\n\n\n33\n_OutlineLightingMix\nfloat\nOutline Mix (Outline Lighting Mix)\nOutline-Specific\n[0.0, 1.0]\n\n\n34\n_UvAnimMaskTexture\ntexture\nAuto Animation Mask Texture (R)\nUV Animation\n[0, 1]\n\n\n35\n_UvAnimScrollX\nfloat\nUV Scroll X (per second)\nUV Animation\n[-100.0, 100.0]\n\n\n36\n_UvAnimScrollY\nfloat\nUV Scroll Y (per second)\nUV Animation\n[-100.0, 100.0]\n\n\n37\n_UvAnimRotation\nfloat\nUV Rotation (per second)\nUV Animation\n[-100.0, 100.0]\n\n\n38\n_DebugMode\nint\nVisualize (Debugging Visualization: Normal or Lighting)\nDebugging\n{0, 1, 2}"
   },
   {
-    "objectID": "decisions/20230508-novel-3d-views.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230508-novel-3d-views.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Draft: Convert segmented front facing 3D Garment images to novel 3d views for 3d modeling",
+    "objectID": "decisions/20211005-improve-meshing-results-by-subdivision-in-godot-engine.html",
+    "href": "decisions/20211005-improve-meshing-results-by-subdivision-in-godot-engine.html",
+    "title": "Proposed: Improve Meshing Results by Subdivision in Godot Engine",
     "section": "",
-    "text": "No, this enhancement requires integration of advanced image segmentation and 3D reconstruction algorithms, which cannot be achieved with a simple script."
+    "text": "For characters subdivision surfaces allow the ability to conserve authoring while also scaling polygons.\n\n\n\nUsing subdivision surfaces in Godot is useful.\n\n\n\n\nImplement subdivision\nIs the UI based on LOD multiples?\n\n\n\n\nNot a few lines of code.\n\n\n\nCan be done by other people.\n\n\n\n\nhttps://github.com/V-Sekai/godot/tree/subdivision\nhttps://github.com/godotengine/godot-proposals/issues/784\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230508-novel-3d-views.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230508-novel-3d-views.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Draft: Convert segmented front facing 3D Garment images to novel 3d views for 3d modeling",
+    "objectID": "decisions/20211005-improve-meshing-results-by-subdivision-in-godot-engine.html#context-and-problem-statement",
+    "href": "decisions/20211005-improve-meshing-results-by-subdivision-in-godot-engine.html#context-and-problem-statement",
+    "title": "Proposed: Improve Meshing Results by Subdivision in Godot Engine",
     "section": "",
-    "text": "Yes, implementing this feature as part of our core project will improve our opensource community of creators."
+    "text": "For characters subdivision surfaces allow the ability to conserve authoring while also scaling polygons."
   },
   {
-    "objectID": "decisions/20230508-novel-3d-views.html#references",
-    "href": "decisions/20230508-novel-3d-views.html#references",
-    "title": "Draft: Convert segmented front facing 3D Garment images to novel 3d views for 3d modeling",
+    "objectID": "decisions/20211005-improve-meshing-results-by-subdivision-in-godot-engine.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20211005-improve-meshing-results-by-subdivision-in-godot-engine.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: Improve Meshing Results by Subdivision in Godot Engine",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Using subdivision surfaces in Godot is useful."
   },
   {
-    "objectID": "decisions/20230131-meeting-at-gdc-2023.html",
-    "href": "decisions/20230131-meeting-at-gdc-2023.html",
-    "title": "Accepted: Meet at GDC SF 2023",
+    "objectID": "decisions/20211005-improve-meshing-results-by-subdivision-in-godot-engine.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20211005-improve-meshing-results-by-subdivision-in-godot-engine.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Improve Meshing Results by Subdivision in Godot Engine",
     "section": "",
-    "text": "Accepted: Meet at GDC SF 2023\nCompleted.\n\nContext and Problem Statement\nWe would like to meet at the Gdeveloper conference San Francisco.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nWould like meet and try to ask for assistance.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\n\nPropose a meeting spot\nFly and ensure lodging\n\n\n\nPositive Consequences\nMeet and greet. &lt;3\n\n\nNegative Consequences\nAt what cost!\n\n\nOption graveyard\nNo response\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot coding related.\n\n\nIs there a reason why this should be core and done by us?\nWe would like to do this.\n\n\nReferences\n\nV-Sekai\n\n\n\nLicense of the contribution\nCopyright (c) 2022 K. S. Ernest (iFire) Lee contributors. Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Implement subdivision\nIs the UI based on LOD multiples?"
   },
   {
-    "objectID": "decisions/20230123-ready-the-net-demo.html",
-    "href": "decisions/20230123-ready-the-net-demo.html",
-    "title": "Proposed: Ready net demo",
+    "objectID": "decisions/20211005-improve-meshing-results-by-subdivision-in-godot-engine.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20211005-improve-meshing-results-by-subdivision-in-godot-engine.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Improve Meshing Results by Subdivision in Godot Engine",
     "section": "",
-    "text": "Proposed: Ready net demo\n\nContext and Problem Statement\nGet the net demo ready for merge into V-Sekai\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nI want to get the net demo ready for presentation.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\n\njitter buffer window of 100ms\nbit packing with the godot engine core animation compression\nperfect prediction using ballistic trajectory https://github.com/fbsamples/oculus-networked-physics-sample/blob/f4242f317fc1c81348308bdd69774c637c3c0f91/Networked%20Physics/Assets/Scripts/Prediction.cs#L48\n\n\n\nPositive Consequences\nWe’ll have lag free VR network sync.\n\n\nNegative Consequences\nMay have cheating with this type of replication.\n\n\nOption graveyard\nOption: The status quo. Rejection Reason: This solves nothing.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot trivial.\n\n\nIs there a reason why this should be core and done by us?\nWe are doing this.\n\n\nReferences\n\nV-Sekai\n\n\n\nLicense of the contribution\nCopyright (c) 2019-latest V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Not a few lines of code."
   },
   {
-    "objectID": "decisions/20231225-mesh-transformer-clothing.html",
-    "href": "decisions/20231225-mesh-transformer-clothing.html",
-    "title": "Proposed: Mesh Transformer Clothing",
+    "objectID": "decisions/20211005-improve-meshing-results-by-subdivision-in-godot-engine.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20211005-improve-meshing-results-by-subdivision-in-godot-engine.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Improve Meshing Results by Subdivision in Godot Engine",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, second rank\n\n\n\n\nIn the realm of Virtual Reality (VR), personalization and style expression play a significant role in enhancing user experience. One way to achieve this is through customizable clothing for avatars, which can be made possible with the use of Mesh Transformers.\n\n\n\nThe challenge lies in enabling personalization and style expression in virtual environments by designing a wide array of clothing items optimized for VR. This involves generating meshes for different garments like jackets, shirts, pants, dresses, and more.\n\n\n\nThe strategy is to use Mesh Transformers to generate these clothing items. The goal is to create clothing that is visually appealing, stylistically diverse, and adaptable to different avatar bodies, while maintaining a low polygon count for optimal VR performance.\n\n\n\nThe upside is the creation of more immersive and engaging virtual environments, with avatars that can express their individuality and style through their clothing.\n\n\n\nThe downside could be the potential increase in complexity and computational requirements due to the addition of more detailed and diverse clothing items.\n\n\n\nAn alternative approach could have been to use simpler, less diverse clothing designs. However, this would limit the range of personal expression possible in VR environments.\n\n\n\nIn cases where VR environments are used for simple tasks or interactions, the need for highly diverse and customizable clothing may not be as high.\n\n\n\nYes, this proposal is core to our mission of enhancing VR experiences and will be implemented by our team.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
+    "text": "Can be done by other people."
   },
   {
-    "objectID": "decisions/20231225-mesh-transformer-clothing.html#metadata",
-    "href": "decisions/20231225-mesh-transformer-clothing.html#metadata",
-    "title": "Proposed: Mesh Transformer Clothing",
+    "objectID": "decisions/20211005-improve-meshing-results-by-subdivision-in-godot-engine.html#references",
+    "href": "decisions/20211005-improve-meshing-results-by-subdivision-in-godot-engine.html#references",
+    "title": "Proposed: Improve Meshing Results by Subdivision in Godot Engine",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, second rank"
+    "text": "https://github.com/V-Sekai/godot/tree/subdivision\nhttps://github.com/godotengine/godot-proposals/issues/784"
   },
   {
-    "objectID": "decisions/20231225-mesh-transformer-clothing.html#the-backdrop",
-    "href": "decisions/20231225-mesh-transformer-clothing.html#the-backdrop",
-    "title": "Proposed: Mesh Transformer Clothing",
+    "objectID": "decisions/20211005-improve-meshing-results-by-subdivision-in-godot-engine.html#derivative-license",
+    "href": "decisions/20211005-improve-meshing-results-by-subdivision-in-godot-engine.html#derivative-license",
+    "title": "Proposed: Improve Meshing Results by Subdivision in Godot Engine",
     "section": "",
-    "text": "In the realm of Virtual Reality (VR), personalization and style expression play a significant role in enhancing user experience. One way to achieve this is through customizable clothing for avatars, which can be made possible with the use of Mesh Transformers."
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20231225-mesh-transformer-clothing.html#the-challenge",
-    "href": "decisions/20231225-mesh-transformer-clothing.html#the-challenge",
-    "title": "Proposed: Mesh Transformer Clothing",
+    "objectID": "decisions/20220820-bake alembic-anim-via-blender.html",
+    "href": "decisions/20220820-bake alembic-anim-via-blender.html",
+    "title": "Proposed: Bake alembic imports by running blender script.",
     "section": "",
-    "text": "The challenge lies in enabling personalization and style expression in virtual environments by designing a wide array of clothing items optimized for VR. This involves generating meshes for different garments like jackets, shirts, pants, dresses, and more."
+    "text": "Proposed: Bake alembic imports by running blender script.\n\nContext and Problem Statement\nWant to bake alembic imports to gltf blend shapes.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nWe run a python script in Blender to bake alembic inputs to gltf2.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\n# MIT LICENSE\n# Authored by iFire#6518 and alexfreyre#1663\n# This code ONLY apply to a mesh and simulations with ONLY the same vertex number\n\nimport bpy\n\n#Converts a MeshCache or Cloth modifiers to ShapeKeys\nframe = bpy.context.scene.frame_start\nfor frame in range(bpy.context.scene.frame_end + 1):\n    bpy.context.scene.frame_current = frame\n\n    # For alembic files converted to MDD and loaded as MeshCache.\n    bpy.ops.object.modifier_apply_as_shapekey(keep_modifier=True, modifier=\"MeshCache\")\n\n    # For cloth simulations inside blender using a Cloth modifier.\n    #bpy.ops.object.modifier_apply_as_shapekey(keep_modifier=True, modifier=\"Cloth\")\n\n# Loop through shapekeys and add as keyframe per frame.\n# https://blender.stackexchange.com/q/149045/87258\nframe = bpy.context.scene.frame_start\nfor frame in range(bpy.context.scene.frame_end + 1):\n    bpy.context.scene.frame_current = frame\n\n    for shapekey in bpy.data.shape_keys:\n        for i, keyblock in enumerate(shapekey.key_blocks):\n            if keyblock.name != \"Basis\":\n                curr = i - 1\n                if curr != frame:\n                    keyblock.value = 0\n                    keyblock.keyframe_insert(\"value\", frame=frame)\n                else:\n                    keyblock.value = 1\n                    keyblock.keyframe_insert(\"value\", frame=frame)\n\n# bpy.ops.object.modifier_remove(modifier=\"MeshCache\")\n# bpy.ops.object.modifier_remove(modifier=\"Cloth\")\nDo not use the pc2 vertex cache format because of mesh accuracy loss.\n\n\nPositive Consequences\nCan convert alembic to gltf2 for better interoperability.\n\n\nNegative Consequences\nBlend shapes are big.\n\n\nOption graveyard\nOption: Don’t convert.\nThis loses the animation.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot a few lines of script.\n\n\nIs there a reason why this should be core and done by us?\nWe already made a solution.\n\n\nReferences\n\nV-Sekai\n\n\n\nLicense of the contribution\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20231225-mesh-transformer-clothing.html#the-strategy",
-    "href": "decisions/20231225-mesh-transformer-clothing.html#the-strategy",
-    "title": "Proposed: Mesh Transformer Clothing",
+    "objectID": "decisions/20211105-have-an-webxr-version-of-v-sekai.html",
+    "href": "decisions/20211105-have-an-webxr-version-of-v-sekai.html",
+    "title": "Rejected: Have an WebXR version of V-Sekai that is more accessible",
     "section": "",
-    "text": "The strategy is to use Mesh Transformers to generate these clothing items. The goal is to create clothing that is visually appealing, stylistically diverse, and adaptable to different avatar bodies, while maintaining a low polygon count for optimal VR performance."
+    "text": "Status: rejected \nDeciders: V-Sekai,fire,\nTags: V-Sekai,\n\n\n\nIt’s hard to get access to V-Sekai.\n\n\n\nLet’s strip down our V-Sekai prototype and make it work for WebXR.\n\n\n\n\nUpgrade to 3.4 Godot Engine\n\n\n\n\n\n[e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]\n\n\n\n\n\nTook too much effort to verify.\n\n\n\n\n\nOption: \nRejection Reason: \n\n\n\n\nThis is not a few lines of code and is a V-Sekai core topic.\n\n\n\nWe maintain core V-Sekai.\n\n\n\n\nhttps://github.com/V-Sekai/groups-workspace-fire\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20231225-mesh-transformer-clothing.html#the-upside",
-    "href": "decisions/20231225-mesh-transformer-clothing.html#the-upside",
-    "title": "Proposed: Mesh Transformer Clothing",
+    "objectID": "decisions/20211105-have-an-webxr-version-of-v-sekai.html#context-and-problem-statement",
+    "href": "decisions/20211105-have-an-webxr-version-of-v-sekai.html#context-and-problem-statement",
+    "title": "Rejected: Have an WebXR version of V-Sekai that is more accessible",
     "section": "",
-    "text": "The upside is the creation of more immersive and engaging virtual environments, with avatars that can express their individuality and style through their clothing."
+    "text": "It’s hard to get access to V-Sekai."
   },
   {
-    "objectID": "decisions/20231225-mesh-transformer-clothing.html#the-downside",
-    "href": "decisions/20231225-mesh-transformer-clothing.html#the-downside",
-    "title": "Proposed: Mesh Transformer Clothing",
+    "objectID": "decisions/20211105-have-an-webxr-version-of-v-sekai.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20211105-have-an-webxr-version-of-v-sekai.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Rejected: Have an WebXR version of V-Sekai that is more accessible",
     "section": "",
-    "text": "The downside could be the potential increase in complexity and computational requirements due to the addition of more detailed and diverse clothing items."
+    "text": "Let’s strip down our V-Sekai prototype and make it work for WebXR."
   },
   {
-    "objectID": "decisions/20231225-mesh-transformer-clothing.html#the-road-not-taken",
-    "href": "decisions/20231225-mesh-transformer-clothing.html#the-road-not-taken",
-    "title": "Proposed: Mesh Transformer Clothing",
+    "objectID": "decisions/20211105-have-an-webxr-version-of-v-sekai.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20211105-have-an-webxr-version-of-v-sekai.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Rejected: Have an WebXR version of V-Sekai that is more accessible",
     "section": "",
-    "text": "An alternative approach could have been to use simpler, less diverse clothing designs. However, this would limit the range of personal expression possible in VR environments."
+    "text": "Upgrade to 3.4 Godot Engine"
   },
   {
-    "objectID": "decisions/20231225-mesh-transformer-clothing.html#the-infrequent-use-case",
-    "href": "decisions/20231225-mesh-transformer-clothing.html#the-infrequent-use-case",
-    "title": "Proposed: Mesh Transformer Clothing",
+    "objectID": "decisions/20211105-have-an-webxr-version-of-v-sekai.html#positive-consequences",
+    "href": "decisions/20211105-have-an-webxr-version-of-v-sekai.html#positive-consequences",
+    "title": "Rejected: Have an WebXR version of V-Sekai that is more accessible",
     "section": "",
-    "text": "In cases where VR environments are used for simple tasks or interactions, the need for highly diverse and customizable clothing may not be as high."
+    "text": "[e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]"
   },
   {
-    "objectID": "decisions/20231225-mesh-transformer-clothing.html#in-core-and-done-by-us",
-    "href": "decisions/20231225-mesh-transformer-clothing.html#in-core-and-done-by-us",
-    "title": "Proposed: Mesh Transformer Clothing",
+    "objectID": "decisions/20211105-have-an-webxr-version-of-v-sekai.html#negative-consequences",
+    "href": "decisions/20211105-have-an-webxr-version-of-v-sekai.html#negative-consequences",
+    "title": "Rejected: Have an WebXR version of V-Sekai that is more accessible",
     "section": "",
-    "text": "Yes, this proposal is core to our mission of enhancing VR experiences and will be implemented by our team."
+    "text": "Took too much effort to verify."
   },
   {
-    "objectID": "decisions/20231225-mesh-transformer-clothing.html#further-reading",
-    "href": "decisions/20231225-mesh-transformer-clothing.html#further-reading",
-    "title": "Proposed: Mesh Transformer Clothing",
+    "objectID": "decisions/20211105-have-an-webxr-version-of-v-sekai.html#option-graveyard",
+    "href": "decisions/20211105-have-an-webxr-version-of-v-sekai.html#option-graveyard",
+    "title": "Rejected: Have an WebXR version of V-Sekai that is more accessible",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
+    "text": "Option: \nRejection Reason:"
   },
   {
-    "objectID": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html",
-    "href": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html",
-    "title": "Proposed: Convert Blender CC0 Base Mesh to Godot Engine T-Pose",
+    "objectID": "decisions/20211105-have-an-webxr-version-of-v-sekai.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20211105-have-an-webxr-version-of-v-sekai.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Rejected: Have an WebXR version of V-Sekai that is more accessible",
     "section": "",
-    "text": "We would like to have several base meshes for testing and for skeleton merge clothing tests.\n\n\n\nThe current process of converting Blender CC0 base meshes to a format compatible with the Godot Engine is cumbersome and lacks a standardized approach. This proposal aims to streamline the conversion process, ensuring consistency and efficiency.\n\n\n\n\nInstall Blender 4.1.1\nDownload “Human Base Meshes bundle by Blender Studio CC0 Licensed”\nTest Auto Rig Pro version 3.70.38\nPick a category:\n\nA. Stylized\nB. Realistic\nC. Stylized Parts\nD. Realistic Parts\n\nWe’re picking realistic.\nPick feminine or masculine: We’re picking feminine.\nSelect all the meshes\nUse Auto-Rig Pro Smart: “Get Selected Objects”\nAdd armature: Human\n\nSet biped\nAdd additional: Twist\n\nClick on the body parts:\n\nNeck (This is the base of the neck)\nChin (This is the tip of the chin)\nShoulder (It’s in between the arm.)\nSpine root (Crotch area.)\nAnkles (Above the foot.)\n\nSet skeleton type to “UE5 Manny-Quinn”\nAdd facial\nRemember to set eyes (required)\nSet pelvis up to be enabled\nClick on the facial areas:\n\nEyebrows\nEyes\nMouth\n\nSet character name (it’s an option in misc tab) to body_feminine_realistic\nClick match to rig\nSelect all meshes, and the rig. Then go to the Skin tab\nSelect scale fix\nDo not enable preserve volume\nThen hit bind (Ensure the engine is heat map, voxel skinning gives poor results around the shoulder blades on base meshes.)\nGo to Rig\nDo not set pose to T-Pose. It is not reversible.\nSet the pose to “UE5 Manny-Quinn”\nTODO: Create a new animation action and name it “A-POSE”\nConfigure FBX exporter:\n\nUnity humanoid\nClick fix rig (again)\nSelect advanced\nFull facial\nExport root bone c_traj\nSet root motion\n\nEnsure that the multi-mesh GEO-body_female_realistic is set to render disabled\nExport as GLB\nOpen GLB in Godot Engine\nTODO: Instructions on the bone map\nTODO: Instructions on silhouette fixer:\n\nDisable list:\n\nLeftFoot\nRightFoot\nNeck\nHead\nUpperChest\n\n\n\n\n\n\n\nImproved Efficiency: Streamlining the conversion process saves time and reduces manual effort.\nConsistency: Standardizing the approach ensures uniformity across different base meshes.\nEnhanced Compatibility: Ensures that the converted meshes are fully compatible with the Godot Engine.\n\n\n\n\n\nInitial Learning Curve: Team members may need time to familiarize themselves with the new process.\nTool Dependency: Reliance on specific tools like Auto Rig Pro may limit flexibility.\n\n\n\n\nAlternative approaches such as manual rigging or using different software were considered but ultimately deemed less efficient or effective.\n\n\n\nIn rare cases where highly specialized or technical requirements arise, additional human oversight may be necessary to ensure accuracy and appropriateness.\n\n\n\nThis proposal aligns with our core values of efficiency and professionalism and will be implemented by our team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nHuman Base Meshes bundle by Blender Studio CC0 Licensed - Human Base Meshes bundle by Blender Studio includes 17 separate meshes, including complete male and female figures, plus individual body parts like feet, hands, heads, jaws, and eyeballs.\nAuto Rig Pro\n\nAI assistant Aria assisted with this article."
+    "text": "This is not a few lines of code and is a V-Sekai core topic."
   },
   {
-    "objectID": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#the-context",
-    "href": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#the-context",
-    "title": "Proposed: Convert Blender CC0 Base Mesh to Godot Engine T-Pose",
+    "objectID": "decisions/20211105-have-an-webxr-version-of-v-sekai.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20211105-have-an-webxr-version-of-v-sekai.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Rejected: Have an WebXR version of V-Sekai that is more accessible",
     "section": "",
-    "text": "We would like to have several base meshes for testing and for skeleton merge clothing tests."
+    "text": "We maintain core V-Sekai."
   },
   {
-    "objectID": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#the-problem-statement",
-    "href": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#the-problem-statement",
-    "title": "Proposed: Convert Blender CC0 Base Mesh to Godot Engine T-Pose",
+    "objectID": "decisions/20211105-have-an-webxr-version-of-v-sekai.html#references",
+    "href": "decisions/20211105-have-an-webxr-version-of-v-sekai.html#references",
+    "title": "Rejected: Have an WebXR version of V-Sekai that is more accessible",
     "section": "",
-    "text": "The current process of converting Blender CC0 base meshes to a format compatible with the Godot Engine is cumbersome and lacks a standardized approach. This proposal aims to streamline the conversion process, ensuring consistency and efficiency."
+    "text": "https://github.com/V-Sekai/groups-workspace-fire"
   },
   {
-    "objectID": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Convert Blender CC0 Base Mesh to Godot Engine T-Pose",
+    "objectID": "decisions/20211105-have-an-webxr-version-of-v-sekai.html#derivative-license",
+    "href": "decisions/20211105-have-an-webxr-version-of-v-sekai.html#derivative-license",
+    "title": "Rejected: Have an WebXR version of V-Sekai that is more accessible",
     "section": "",
-    "text": "Install Blender 4.1.1\nDownload “Human Base Meshes bundle by Blender Studio CC0 Licensed”\nTest Auto Rig Pro version 3.70.38\nPick a category:\n\nA. Stylized\nB. Realistic\nC. Stylized Parts\nD. Realistic Parts\n\nWe’re picking realistic.\nPick feminine or masculine: We’re picking feminine.\nSelect all the meshes\nUse Auto-Rig Pro Smart: “Get Selected Objects”\nAdd armature: Human\n\nSet biped\nAdd additional: Twist\n\nClick on the body parts:\n\nNeck (This is the base of the neck)\nChin (This is the tip of the chin)\nShoulder (It’s in between the arm.)\nSpine root (Crotch area.)\nAnkles (Above the foot.)\n\nSet skeleton type to “UE5 Manny-Quinn”\nAdd facial\nRemember to set eyes (required)\nSet pelvis up to be enabled\nClick on the facial areas:\n\nEyebrows\nEyes\nMouth\n\nSet character name (it’s an option in misc tab) to body_feminine_realistic\nClick match to rig\nSelect all meshes, and the rig. Then go to the Skin tab\nSelect scale fix\nDo not enable preserve volume\nThen hit bind (Ensure the engine is heat map, voxel skinning gives poor results around the shoulder blades on base meshes.)\nGo to Rig\nDo not set pose to T-Pose. It is not reversible.\nSet the pose to “UE5 Manny-Quinn”\nTODO: Create a new animation action and name it “A-POSE”\nConfigure FBX exporter:\n\nUnity humanoid\nClick fix rig (again)\nSelect advanced\nFull facial\nExport root bone c_traj\nSet root motion\n\nEnsure that the multi-mesh GEO-body_female_realistic is set to render disabled\nExport as GLB\nOpen GLB in Godot Engine\nTODO: Instructions on the bone map\nTODO: Instructions on silhouette fixer:\n\nDisable list:\n\nLeftFoot\nRightFoot\nNeck\nHead\nUpperChest"
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#the-benefits",
-    "href": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#the-benefits",
-    "title": "Proposed: Convert Blender CC0 Base Mesh to Godot Engine T-Pose",
+    "objectID": "decisions/20230804-dokku.html",
+    "href": "decisions/20230804-dokku.html",
+    "title": "Proposed: Dokku for V-Sekai URO Backend Services Hosting and Development",
     "section": "",
-    "text": "Improved Efficiency: Streamlining the conversion process saves time and reduces manual effort.\nConsistency: Standardizing the approach ensures uniformity across different base meshes.\nEnhanced Compatibility: Ensures that the converted meshes are fully compatible with the Godot Engine."
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, Dokku, Backend, Hosting, Development\n\n\n\n\nV-Sekai is exploring options to improve its backend services hosting and development. The goal is to find a system that can offer scalability, ease of deployment, and efficient resource management.\n\n\n\nOne potential solution could be Dokku, a Docker-powered mini-Heroku. Dokku provides a platform that could potentially meet our needs for building, deploying and managing applications effectively.\n\n\n\nIf Dokku were chosen, the implementation would involve setting up a Dokku server, migrating existing services, and training the team on how to use Dokku for development and deployment.\n# Install Dokku\nwget https://raw.githubusercontent.com/dokku/dokku/v0.21.4/bootstrap.sh;\nsudo DOKKU_TAG=v0.21.4 bash bootstrap.sh\n\n\n\n\nScalability: Dokku has features that could allow us to scale our applications based on demand.\nEase of Deployment: Dokku’s git-based deployment system might simplify the process of deploying new versions of our applications.\nResource Management: Dokku’s use of Docker containers could lead to more efficient use of system resources.\n\n\n\n\n\nThere might be a learning curve for the team members who are not familiar with Dokku or Docker.\nMigration of existing services to a new platform could require significant time and resources.\n\n\n\n\nOther options considered include traditional VM-based hosting and other PaaS solutions like Heroku or AWS Elastic Beanstalk. These options have their own sets of advantages and disadvantages that need to be weighed against those of Dokku.\n\n\n\nThis depends on the specific requirements of our backend services. If the enhancement is fundamental to the hosting and development of our backend services, it may not be possible to work around it with a few lines of script.\n\n\n\nThe choice of hosting and development environment is crucial for the efficiency and effectiveness of our operations. Whether Dokku or another solution is chosen, it will be important for us to maintain control over this aspect of our infrastructure.\n\n\n\n\nV-Sekai\nDokku Documentation"
   },
   {
-    "objectID": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#the-downsides",
-    "href": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#the-downsides",
-    "title": "Proposed: Convert Blender CC0 Base Mesh to Godot Engine T-Pose",
+    "objectID": "decisions/20230804-dokku.html#metadata",
+    "href": "decisions/20230804-dokku.html#metadata",
+    "title": "Proposed: Dokku for V-Sekai URO Backend Services Hosting and Development",
     "section": "",
-    "text": "Initial Learning Curve: Team members may need time to familiarize themselves with the new process.\nTool Dependency: Reliance on specific tools like Auto Rig Pro may limit flexibility."
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, Dokku, Backend, Hosting, Development"
   },
   {
-    "objectID": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#the-road-not-taken",
-    "href": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#the-road-not-taken",
-    "title": "Proposed: Convert Blender CC0 Base Mesh to Godot Engine T-Pose",
+    "objectID": "decisions/20230804-dokku.html#context-and-problem-statement",
+    "href": "decisions/20230804-dokku.html#context-and-problem-statement",
+    "title": "Proposed: Dokku for V-Sekai URO Backend Services Hosting and Development",
     "section": "",
-    "text": "Alternative approaches such as manual rigging or using different software were considered but ultimately deemed less efficient or effective."
+    "text": "V-Sekai is exploring options to improve its backend services hosting and development. The goal is to find a system that can offer scalability, ease of deployment, and efficient resource management."
   },
   {
-    "objectID": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#the-infrequent-use-case",
-    "href": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#the-infrequent-use-case",
-    "title": "Proposed: Convert Blender CC0 Base Mesh to Godot Engine T-Pose",
+    "objectID": "decisions/20230804-dokku.html#proposed-solution",
+    "href": "decisions/20230804-dokku.html#proposed-solution",
+    "title": "Proposed: Dokku for V-Sekai URO Backend Services Hosting and Development",
     "section": "",
-    "text": "In rare cases where highly specialized or technical requirements arise, additional human oversight may be necessary to ensure accuracy and appropriateness."
+    "text": "One potential solution could be Dokku, a Docker-powered mini-Heroku. Dokku provides a platform that could potentially meet our needs for building, deploying and managing applications effectively."
   },
   {
-    "objectID": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#in-core-and-done-by-us",
-    "href": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#in-core-and-done-by-us",
-    "title": "Proposed: Convert Blender CC0 Base Mesh to Godot Engine T-Pose",
+    "objectID": "decisions/20230804-dokku.html#implementation",
+    "href": "decisions/20230804-dokku.html#implementation",
+    "title": "Proposed: Dokku for V-Sekai URO Backend Services Hosting and Development",
     "section": "",
-    "text": "This proposal aligns with our core values of efficiency and professionalism and will be implemented by our team."
+    "text": "If Dokku were chosen, the implementation would involve setting up a Dokku server, migrating existing services, and training the team on how to use Dokku for development and deployment.\n# Install Dokku\nwget https://raw.githubusercontent.com/dokku/dokku/v0.21.4/bootstrap.sh;\nsudo DOKKU_TAG=v0.21.4 bash bootstrap.sh"
   },
   {
-    "objectID": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#status",
-    "href": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#status",
-    "title": "Proposed: Convert Blender CC0 Base Mesh to Godot Engine T-Pose",
+    "objectID": "decisions/20230804-dokku.html#potential-benefits",
+    "href": "decisions/20230804-dokku.html#potential-benefits",
+    "title": "Proposed: Dokku for V-Sekai URO Backend Services Hosting and Development",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "Scalability: Dokku has features that could allow us to scale our applications based on demand.\nEase of Deployment: Dokku’s git-based deployment system might simplify the process of deploying new versions of our applications.\nResource Management: Dokku’s use of Docker containers could lead to more efficient use of system resources."
   },
   {
-    "objectID": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#decision-makers",
-    "href": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#decision-makers",
-    "title": "Proposed: Convert Blender CC0 Base Mesh to Godot Engine T-Pose",
+    "objectID": "decisions/20230804-dokku.html#potential-drawbacks",
+    "href": "decisions/20230804-dokku.html#potential-drawbacks",
+    "title": "Proposed: Dokku for V-Sekai URO Backend Services Hosting and Development",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "There might be a learning curve for the team members who are not familiar with Dokku or Docker.\nMigration of existing services to a new platform could require significant time and resources."
   },
   {
-    "objectID": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#tags",
-    "href": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#tags",
-    "title": "Proposed: Convert Blender CC0 Base Mesh to Godot Engine T-Pose",
+    "objectID": "decisions/20230804-dokku.html#option-graveyard",
+    "href": "decisions/20230804-dokku.html#option-graveyard",
+    "title": "Proposed: Dokku for V-Sekai URO Backend Services Hosting and Development",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Other options considered include traditional VM-based hosting and other PaaS solutions like Heroku or AWS Elastic Beanstalk. These options have their own sets of advantages and disadvantages that need to be weighed against those of Dokku."
   },
   {
-    "objectID": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#further-reading",
-    "href": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#further-reading",
-    "title": "Proposed: Convert Blender CC0 Base Mesh to Godot Engine T-Pose",
+    "objectID": "decisions/20230804-dokku.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230804-dokku.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Dokku for V-Sekai URO Backend Services Hosting and Development",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nHuman Base Meshes bundle by Blender Studio CC0 Licensed - Human Base Meshes bundle by Blender Studio includes 17 separate meshes, including complete male and female figures, plus individual body parts like feet, hands, heads, jaws, and eyeballs.\nAuto Rig Pro\n\nAI assistant Aria assisted with this article."
+    "text": "This depends on the specific requirements of our backend services. If the enhancement is fundamental to the hosting and development of our backend services, it may not be possible to work around it with a few lines of script."
   },
   {
-    "objectID": "decisions/20221006-unidot-is-optional.html",
-    "href": "decisions/20221006-unidot-is-optional.html",
-    "title": "Proposed: Unidot is optional",
+    "objectID": "decisions/20230804-dokku.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230804-dokku.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Dokku for V-Sekai URO Backend Services Hosting and Development",
     "section": "",
-    "text": "Status: proposed \nDeciders: V-Sekai,fire,MalekiRe\nTags: V-Sekai,\n\n\n\nIs this error of concerning building Godot Engine with V-Sekai game?\n\n\n\nUnidot addon error\n\n\n\n\n\nLet MalekiRe know that the Unidot addon is not critical to V-Sekai game.\n\n\n\nLeft this document here.\n\n\n\n\nIt’s not essential.\n\n\n\n\n\nProbably should fix the unidot addon.\n\n[this section can be repeated for each option if more than one option is open for consideration]\n\n\n\n\nOption: Do something.\nRejection Reason: It’s not essential.\n\n\n\n\nThis is a broken addon.\n\n\n\nWe maintain V-Sekai.\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "The choice of hosting and development environment is crucial for the efficiency and effectiveness of our operations. Whether Dokku or another solution is chosen, it will be important for us to maintain control over this aspect of our infrastructure."
   },
   {
-    "objectID": "decisions/20221006-unidot-is-optional.html#context-and-problem-statement",
-    "href": "decisions/20221006-unidot-is-optional.html#context-and-problem-statement",
-    "title": "Proposed: Unidot is optional",
+    "objectID": "decisions/20230804-dokku.html#references",
+    "href": "decisions/20230804-dokku.html#references",
+    "title": "Proposed: Dokku for V-Sekai URO Backend Services Hosting and Development",
     "section": "",
-    "text": "Is this error of concerning building Godot Engine with V-Sekai game?\n\n\n\nUnidot addon error"
+    "text": "V-Sekai\nDokku Documentation"
   },
   {
-    "objectID": "decisions/20221006-unidot-is-optional.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20221006-unidot-is-optional.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: Unidot is optional",
+    "objectID": "decisions/20240329-ready-to-go-kit-windows-11.html",
+    "href": "decisions/20240329-ready-to-go-kit-windows-11.html",
+    "title": "Proposed: V-Sekai Setup as a Ready-to-Go Kit",
     "section": "",
-    "text": "Let MalekiRe know that the Unidot addon is not critical to V-Sekai game."
+    "text": "V-Sekai is an open-source project that focuses on bringing social VR functionality to the Godot Engine. It aims to create a metaverse where users can interact and engage in various activities.\n\n\n\nThe current setup process for V-Sekai is complex and time-consuming, which may deter potential users and developers. We need to simplify this process by creating a ready-to-go kit.\n\n\n\nThe ready-to-go kit will be a pre-configured package containing all necessary files and dependencies for running V-Sekai. Users will simply need to download and extract the package to get started.\n\nDownload V-Sekai Kit\nExtract Files\nRun V-Sekai\n\n\n\n\n\nSimplified setup process\nIncreased accessibility for non-technical users\nPotential increase in user base and community contributions\n\n\n\n\n\nMaintenance of the kit could become resource-intensive if not automated\nPotential security risks if not properly managed\n\n\n\n\nWe could have continued with the existing setup process, but this would likely limit the growth and accessibility of V-Sekai.\n\n\n\nUsers who wish to customize their V-Sekai experience extensively may find the ready-to-go kit limiting. However, they still have the option to manually set up V-Sekai.\n\n\n\nThis proposal will be implemented by the V-Sekai development team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20221006-unidot-is-optional.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20221006-unidot-is-optional.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Unidot is optional",
+    "objectID": "decisions/20240329-ready-to-go-kit-windows-11.html#the-context",
+    "href": "decisions/20240329-ready-to-go-kit-windows-11.html#the-context",
+    "title": "Proposed: V-Sekai Setup as a Ready-to-Go Kit",
     "section": "",
-    "text": "Left this document here."
+    "text": "V-Sekai is an open-source project that focuses on bringing social VR functionality to the Godot Engine. It aims to create a metaverse where users can interact and engage in various activities."
   },
   {
-    "objectID": "decisions/20221006-unidot-is-optional.html#positive-consequences",
-    "href": "decisions/20221006-unidot-is-optional.html#positive-consequences",
-    "title": "Proposed: Unidot is optional",
+    "objectID": "decisions/20240329-ready-to-go-kit-windows-11.html#the-problem-statement",
+    "href": "decisions/20240329-ready-to-go-kit-windows-11.html#the-problem-statement",
+    "title": "Proposed: V-Sekai Setup as a Ready-to-Go Kit",
     "section": "",
-    "text": "It’s not essential."
+    "text": "The current setup process for V-Sekai is complex and time-consuming, which may deter potential users and developers. We need to simplify this process by creating a ready-to-go kit."
   },
   {
-    "objectID": "decisions/20221006-unidot-is-optional.html#negative-consequences",
-    "href": "decisions/20221006-unidot-is-optional.html#negative-consequences",
-    "title": "Proposed: Unidot is optional",
+    "objectID": "decisions/20240329-ready-to-go-kit-windows-11.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240329-ready-to-go-kit-windows-11.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: V-Sekai Setup as a Ready-to-Go Kit",
     "section": "",
-    "text": "Probably should fix the unidot addon.\n\n[this section can be repeated for each option if more than one option is open for consideration]"
+    "text": "The ready-to-go kit will be a pre-configured package containing all necessary files and dependencies for running V-Sekai. Users will simply need to download and extract the package to get started.\n\nDownload V-Sekai Kit\nExtract Files\nRun V-Sekai"
   },
   {
-    "objectID": "decisions/20221006-unidot-is-optional.html#option-graveyard",
-    "href": "decisions/20221006-unidot-is-optional.html#option-graveyard",
-    "title": "Proposed: Unidot is optional",
+    "objectID": "decisions/20240329-ready-to-go-kit-windows-11.html#the-benefits",
+    "href": "decisions/20240329-ready-to-go-kit-windows-11.html#the-benefits",
+    "title": "Proposed: V-Sekai Setup as a Ready-to-Go Kit",
     "section": "",
-    "text": "Option: Do something.\nRejection Reason: It’s not essential."
+    "text": "Simplified setup process\nIncreased accessibility for non-technical users\nPotential increase in user base and community contributions"
   },
   {
-    "objectID": "decisions/20221006-unidot-is-optional.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20221006-unidot-is-optional.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Unidot is optional",
+    "objectID": "decisions/20240329-ready-to-go-kit-windows-11.html#the-downsides",
+    "href": "decisions/20240329-ready-to-go-kit-windows-11.html#the-downsides",
+    "title": "Proposed: V-Sekai Setup as a Ready-to-Go Kit",
     "section": "",
-    "text": "This is a broken addon."
+    "text": "Maintenance of the kit could become resource-intensive if not automated\nPotential security risks if not properly managed"
   },
   {
-    "objectID": "decisions/20221006-unidot-is-optional.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20221006-unidot-is-optional.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Unidot is optional",
+    "objectID": "decisions/20240329-ready-to-go-kit-windows-11.html#the-road-not-taken",
+    "href": "decisions/20240329-ready-to-go-kit-windows-11.html#the-road-not-taken",
+    "title": "Proposed: V-Sekai Setup as a Ready-to-Go Kit",
     "section": "",
-    "text": "We maintain V-Sekai."
+    "text": "We could have continued with the existing setup process, but this would likely limit the growth and accessibility of V-Sekai."
   },
   {
-    "objectID": "decisions/20221006-unidot-is-optional.html#derivative-license",
-    "href": "decisions/20221006-unidot-is-optional.html#derivative-license",
-    "title": "Proposed: Unidot is optional",
+    "objectID": "decisions/20240329-ready-to-go-kit-windows-11.html#the-infrequent-use-case",
+    "href": "decisions/20240329-ready-to-go-kit-windows-11.html#the-infrequent-use-case",
+    "title": "Proposed: V-Sekai Setup as a Ready-to-Go Kit",
     "section": "",
-    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Users who wish to customize their V-Sekai experience extensively may find the ready-to-go kit limiting. However, they still have the option to manually set up V-Sekai."
   },
   {
-    "objectID": "decisions/20220130-to-record-decisions-write-a-proposal.html",
-    "href": "decisions/20220130-to-record-decisions-write-a-proposal.html",
-    "title": "Accepted: To record decisions write a proposal.",
+    "objectID": "decisions/20240329-ready-to-go-kit-windows-11.html#in-core-and-done-by-us",
+    "href": "decisions/20240329-ready-to-go-kit-windows-11.html#in-core-and-done-by-us",
+    "title": "Proposed: V-Sekai Setup as a Ready-to-Go Kit",
     "section": "",
-    "text": "Status: accepted\nDeciders: V-Sekai,ifire,\nTags: V-Sekai,\n\n\n\nWe need to record our decisions.\n\n\n\nUse the decision record format.\n\n\n\n# [short title of solved problem and solution]\n\n- Status: proposed &lt;!-- draft | rejected | accepted | deprecated | superseded by --&gt;\n- Deciders: V-Sekai,\n- Tags: V-Sekai,\n\n## Context and Problem Statement\n\n[Describe the problem or limitation you are having in your project]\n\n[Describe the context and problem statement, e.g., in free form using two to three sentences. You may want to articulate the problem in the form of a question.]\n\n## Describe the proposed option and how it helps to overcome the problem or limitation\n\n[Describe the proposed option and how it helps to overcome the problem or limitation]\n\n## Describe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\n\n[Describe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams]\n\n## Positive Consequences &lt;!-- optional --&gt;\n\n- [e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]\n\n## Negative Consequences &lt;!-- optional --&gt;\n\n- [e.g., compromising quality attribute, follow-up decisions required, …]\n\n[this section can be repeated for each option if more than one option is open for consideration]\n\n## Option graveyard: &lt;!-- same as above --&gt;\n\n- Option: &lt;!-- [List the proposed options no longer open for consideration.] --&gt;\n- Rejection Reason: &lt;!-- [List the reasons for the rejection: (the Bad traits)] --&gt;\n\n## If this enhancement will not be used often, can it be worked around with a few lines of script?\n\n[If this enhancement will not be used often, can it be worked around with a few lines of script?]\n\n## Is there a reason why this should be core and done by us?\n\n[Is there a reason why this should be core and done by us?]\n\n## References &lt;!-- optional and numbers of links can vary --&gt;\n\n- [Link type](link to decision) &lt;!-- example: Refined by [xxx](yyyymmdd-xxx.md) --&gt;\n\n## Derivative License\n\nCopyright (c) 2021 V-Sekai contributors.\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE.\n\n\n\n\nAble to backtrack ideas.\n\n\n\n\n\nWork\n\n\n\n\n\nOption: Forgetting decisions.\nRejection Reason: We won’t remember the original reasons why we did things.\n\n\n\n\nNot code.\n\n\n\nWe are running the project.\n\n\n\n\nhttps://adr.github.io/\n\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "This proposal will be implemented by the V-Sekai development team."
   },
   {
-    "objectID": "decisions/20220130-to-record-decisions-write-a-proposal.html#context-and-problem-statement",
-    "href": "decisions/20220130-to-record-decisions-write-a-proposal.html#context-and-problem-statement",
-    "title": "Accepted: To record decisions write a proposal.",
+    "objectID": "decisions/20240329-ready-to-go-kit-windows-11.html#status",
+    "href": "decisions/20240329-ready-to-go-kit-windows-11.html#status",
+    "title": "Proposed: V-Sekai Setup as a Ready-to-Go Kit",
     "section": "",
-    "text": "We need to record our decisions."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20220130-to-record-decisions-write-a-proposal.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20220130-to-record-decisions-write-a-proposal.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Accepted: To record decisions write a proposal.",
+    "objectID": "decisions/20240329-ready-to-go-kit-windows-11.html#decision-makers",
+    "href": "decisions/20240329-ready-to-go-kit-windows-11.html#decision-makers",
+    "title": "Proposed: V-Sekai Setup as a Ready-to-Go Kit",
     "section": "",
-    "text": "Use the decision record format."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20220130-to-record-decisions-write-a-proposal.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20220130-to-record-decisions-write-a-proposal.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Accepted: To record decisions write a proposal.",
+    "objectID": "decisions/20240329-ready-to-go-kit-windows-11.html#tags",
+    "href": "decisions/20240329-ready-to-go-kit-windows-11.html#tags",
+    "title": "Proposed: V-Sekai Setup as a Ready-to-Go Kit",
     "section": "",
-    "text": "# [short title of solved problem and solution]\n\n- Status: proposed &lt;!-- draft | rejected | accepted | deprecated | superseded by --&gt;\n- Deciders: V-Sekai,\n- Tags: V-Sekai,\n\n## Context and Problem Statement\n\n[Describe the problem or limitation you are having in your project]\n\n[Describe the context and problem statement, e.g., in free form using two to three sentences. You may want to articulate the problem in the form of a question.]\n\n## Describe the proposed option and how it helps to overcome the problem or limitation\n\n[Describe the proposed option and how it helps to overcome the problem or limitation]\n\n## Describe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\n\n[Describe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams]\n\n## Positive Consequences &lt;!-- optional --&gt;\n\n- [e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]\n\n## Negative Consequences &lt;!-- optional --&gt;\n\n- [e.g., compromising quality attribute, follow-up decisions required, …]\n\n[this section can be repeated for each option if more than one option is open for consideration]\n\n## Option graveyard: &lt;!-- same as above --&gt;\n\n- Option: &lt;!-- [List the proposed options no longer open for consideration.] --&gt;\n- Rejection Reason: &lt;!-- [List the reasons for the rejection: (the Bad traits)] --&gt;\n\n## If this enhancement will not be used often, can it be worked around with a few lines of script?\n\n[If this enhancement will not be used often, can it be worked around with a few lines of script?]\n\n## Is there a reason why this should be core and done by us?\n\n[Is there a reason why this should be core and done by us?]\n\n## References &lt;!-- optional and numbers of links can vary --&gt;\n\n- [Link type](link to decision) &lt;!-- example: Refined by [xxx](yyyymmdd-xxx.md) --&gt;\n\n## Derivative License\n\nCopyright (c) 2021 V-Sekai contributors.\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20220130-to-record-decisions-write-a-proposal.html#positive-consequences",
-    "href": "decisions/20220130-to-record-decisions-write-a-proposal.html#positive-consequences",
-    "title": "Accepted: To record decisions write a proposal.",
+    "objectID": "decisions/20240329-ready-to-go-kit-windows-11.html#further-reading",
+    "href": "decisions/20240329-ready-to-go-kit-windows-11.html#further-reading",
+    "title": "Proposed: V-Sekai Setup as a Ready-to-Go Kit",
     "section": "",
-    "text": "Able to backtrack ideas."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20220130-to-record-decisions-write-a-proposal.html#negative-consequences",
-    "href": "decisions/20220130-to-record-decisions-write-a-proposal.html#negative-consequences",
-    "title": "Accepted: To record decisions write a proposal.",
+    "objectID": "decisions/20230125-without-viz-we-cannot-compare-the-interpolation.html",
+    "href": "decisions/20230125-without-viz-we-cannot-compare-the-interpolation.html",
+    "title": "Proposed: Without visualization, we cannot easily compare the interpolation states",
     "section": "",
-    "text": "Work"
+    "text": "Proposed: Without visualization, we cannot easily compare the interpolation states\n\nMetadata\n\nStatus: proposed \nDeciders: V-Sekai,fire,\nTags: V-Sekai,\n\n\n\nContext and Problem Statement\nV-Sekai interpolation is poor.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nProvide visualization for interpolation.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nTo optimize end to end interpolation, you can use line graphs and scatter plots. A line graph shows the progress of an animation over time, while a scatter plot shows the data points that were used to create an animation.\nA line graph can help you debug physics interpolation issues. If your object’s position is not moving smoothly, you can look at how it moved over time and see if there are any sudden changes or jumps in its motion that might be causing problems. This will help you determine whether you need to adjust your physics simulation or tweak some other aspect of your game design.\nSecond, you can use scatter plots to visualize how different variables interact with each other. For example, if you have an object that’s supposed to move along a straight line but instead moves in a curved path, then it might be helpful for you to see whether there are any correlations between its position and its velocity. This will help you isolate which variables are causing this behavior so that you can optimize them individually or together.\n\n\nPositive Consequences\nWe are able to use V-Sekai easier.\n\n\nNegative Consequences\nWe cannot get other features in.\n\n\nOption graveyard\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nEasy chart is a gdscript addon but it is not trivial to reimplement.\n\n\nIs there a reason why this should be core and done by us?\nMotion posing is a core feature.\n\n\nReferences\n\nV-Sekai\nEasy Charts"
   },
   {
-    "objectID": "decisions/20220130-to-record-decisions-write-a-proposal.html#option-graveyard",
-    "href": "decisions/20220130-to-record-decisions-write-a-proposal.html#option-graveyard",
-    "title": "Accepted: To record decisions write a proposal.",
+    "objectID": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html",
+    "href": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html",
+    "title": "Proposed: Add VRM portable avatars and OMI_personality to the GLTF Transform tool",
     "section": "",
-    "text": "Option: Forgetting decisions.\nRejection Reason: We won’t remember the original reasons why we did things."
+    "text": "Status: proposed \nDeciders: V-Sekai\nTags: V-Sekai, GPT-4\n\n\n\n\nWe want to use OMI_personality, but it needs to be injected into a VRM file by tooling like GLTF Transform and GLTF Transform needs to know completely the VRM0 and VRM1 specification.\n\n\n\n\nStudy and understand the VRM0 and VRM1 specifications.\nImplement support for VRM portable avatars in GLTF Transform.\nAdd functionality to add OMI_personality into VRM files using GLTF Transform.\n\n\n\n\n\n\n\nReview the official VRM documentation and specifications.\nIdentify key components and features required for supporting VRM portable avatars in GLTF Transform.\n\n\n\n\n\nDesign and implement a new extension for GLTF Transform that can handle VRM portable avatars.\n\nEnable “.vrm” io reads\nWrite a plugin that increases the VRM version by one.\n\nEnsure compatibility with existing GLTF Transform features and extensions.\n\n\n\n\n\nModify the CLI configuration to accept OMI_personality data as input.\nImplement functionality to add OMI_personality data into VRM files using the new extension.\n\n\n\n\n\nCreate test cases with different VRM files and OMI_personality configurations.\nVerify the correct injection of OMI_personality data into VRM files.\nEnsure compatibility with other GLTF Transform features and extensions.\n\n\n\n\n\n\nSupport for VRM portable avatars in GLTF Transform.\nAbility to inject OMI_personality into VRM files.\nIncreased adoption of GLTF Transform for VRM-related projects.\n\n\n\n\n\nAdditional development and maintenance effort required for the new extension.\n\n\n\n\nN/A\n\n\n\nNo, this enhancement requires a deeper integration with GLTF Transform and understanding of the VRM specifications.\n\n\n\nYes, implementing this feature will provide a valuable addition to the GLTF Transform tool and cater to the growing VRM community.\n\n\n\n\nV-Sekai\nFor an example similar to KHR_lights_punctual, refer to this implementation.\nNo known design for VRM glTF_transform. However, there are two npm packages by quantumcraft that deal with VRM data, but they’re not open source.\nThe glTF Transform CLI allows specifying a config file, which can register additional glTF extensions and CLI functionality. Check out the CLI configuration documentation. Needle Tools has been trying this approach for NEEDLE_* extensions.\nOMI_personality"
   },
   {
-    "objectID": "decisions/20220130-to-record-decisions-write-a-proposal.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20220130-to-record-decisions-write-a-proposal.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Accepted: To record decisions write a proposal.",
+    "objectID": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html#metadata",
+    "href": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html#metadata",
+    "title": "Proposed: Add VRM portable avatars and OMI_personality to the GLTF Transform tool",
     "section": "",
-    "text": "Not code."
+    "text": "Status: proposed \nDeciders: V-Sekai\nTags: V-Sekai, GPT-4"
   },
   {
-    "objectID": "decisions/20220130-to-record-decisions-write-a-proposal.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20220130-to-record-decisions-write-a-proposal.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Accepted: To record decisions write a proposal.",
+    "objectID": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html#context-and-problem-statement",
+    "href": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html#context-and-problem-statement",
+    "title": "Proposed: Add VRM portable avatars and OMI_personality to the GLTF Transform tool",
     "section": "",
-    "text": "We are running the project."
+    "text": "We want to use OMI_personality, but it needs to be injected into a VRM file by tooling like GLTF Transform and GLTF Transform needs to know completely the VRM0 and VRM1 specification."
   },
   {
-    "objectID": "decisions/20220130-to-record-decisions-write-a-proposal.html#references",
-    "href": "decisions/20220130-to-record-decisions-write-a-proposal.html#references",
-    "title": "Accepted: To record decisions write a proposal.",
+    "objectID": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html#proposed-solution",
+    "href": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html#proposed-solution",
+    "title": "Proposed: Add VRM portable avatars and OMI_personality to the GLTF Transform tool",
     "section": "",
-    "text": "https://adr.github.io/"
+    "text": "Study and understand the VRM0 and VRM1 specifications.\nImplement support for VRM portable avatars in GLTF Transform.\nAdd functionality to add OMI_personality into VRM files using GLTF Transform."
   },
   {
-    "objectID": "decisions/20220130-to-record-decisions-write-a-proposal.html#derivative-license",
-    "href": "decisions/20220130-to-record-decisions-write-a-proposal.html#derivative-license",
-    "title": "Accepted: To record decisions write a proposal.",
+    "objectID": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html#implementation",
+    "href": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html#implementation",
+    "title": "Proposed: Add VRM portable avatars and OMI_personality to the GLTF Transform tool",
     "section": "",
-    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Review the official VRM documentation and specifications.\nIdentify key components and features required for supporting VRM portable avatars in GLTF Transform.\n\n\n\n\n\nDesign and implement a new extension for GLTF Transform that can handle VRM portable avatars.\n\nEnable “.vrm” io reads\nWrite a plugin that increases the VRM version by one.\n\nEnsure compatibility with existing GLTF Transform features and extensions.\n\n\n\n\n\nModify the CLI configuration to accept OMI_personality data as input.\nImplement functionality to add OMI_personality data into VRM files using the new extension.\n\n\n\n\n\nCreate test cases with different VRM files and OMI_personality configurations.\nVerify the correct injection of OMI_personality data into VRM files.\nEnsure compatibility with other GLTF Transform features and extensions."
   },
   {
-    "objectID": "decisions/20240411-elixir-libgodot-zig.html",
-    "href": "decisions/20240411-elixir-libgodot-zig.html",
-    "title": "Rejected: Binding GDExtension to a C-like Language for Libgodot to Implement a Distributed Simulation",
+    "objectID": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html#positive-consequences",
+    "href": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html#positive-consequences",
+    "title": "Proposed: Add VRM portable avatars and OMI_personality to the GLTF Transform tool",
     "section": "",
-    "text": "The V-Sekai development team is working on enhancing the simulation experience in our VR game. We aim to create a more immersive and interactive environment for our players.\n\n\n\nWe can bind GDExtension to a C-like language for libgodot to implement a distributed simulation.\n\n\n\nWe propose to use godot-zig to bind GDExtension to Elixir. This will allow us to leverage the power of Elixir’s concurrency and fault-tolerance features, which are ideal for creating distributed simulations.\n\n\n\n\nEnhanced simulation performance due to Elixir’s efficient handling of concurrent processes.\nImproved fault tolerance, as Elixir’s supervisor trees can automatically recover from errors.\nIncreased developer productivity, as Elixir’s syntax is concise and expressive.\n\n\n\n\n\nRequires learning a new programming language (Elixir), which may increase the development time initially.\nPotential compatibility issues between Elixir and existing parts of the system.\n\n\n\n\nWe considered using other languages like Rust or Go, but they did not offer the same level of concurrency and fault-tolerance features as Elixir.\n\n\n\nThis proposal may not be suitable for smaller projects that do not require complex distributed simulations.\n\n\n\nThe V-Sekai development team will implement this proposal.\n\n\n\nStatus: Rejected \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\ngodot-zig\nzigler\n\nAssisted by Aria."
+    "text": "Support for VRM portable avatars in GLTF Transform.\nAbility to inject OMI_personality into VRM files.\nIncreased adoption of GLTF Transform for VRM-related projects."
   },
   {
-    "objectID": "decisions/20240411-elixir-libgodot-zig.html#the-context",
-    "href": "decisions/20240411-elixir-libgodot-zig.html#the-context",
-    "title": "Rejected: Binding GDExtension to a C-like Language for Libgodot to Implement a Distributed Simulation",
+    "objectID": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html#negative-consequences",
+    "href": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html#negative-consequences",
+    "title": "Proposed: Add VRM portable avatars and OMI_personality to the GLTF Transform tool",
     "section": "",
-    "text": "The V-Sekai development team is working on enhancing the simulation experience in our VR game. We aim to create a more immersive and interactive environment for our players."
+    "text": "Additional development and maintenance effort required for the new extension."
   },
   {
-    "objectID": "decisions/20240411-elixir-libgodot-zig.html#the-problem-statement",
-    "href": "decisions/20240411-elixir-libgodot-zig.html#the-problem-statement",
-    "title": "Rejected: Binding GDExtension to a C-like Language for Libgodot to Implement a Distributed Simulation",
+    "objectID": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html#option-graveyard",
+    "href": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html#option-graveyard",
+    "title": "Proposed: Add VRM portable avatars and OMI_personality to the GLTF Transform tool",
     "section": "",
-    "text": "We can bind GDExtension to a C-like language for libgodot to implement a distributed simulation."
+    "text": "N/A"
   },
   {
-    "objectID": "decisions/20240411-elixir-libgodot-zig.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240411-elixir-libgodot-zig.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Rejected: Binding GDExtension to a C-like Language for Libgodot to Implement a Distributed Simulation",
+    "objectID": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Add VRM portable avatars and OMI_personality to the GLTF Transform tool",
     "section": "",
-    "text": "We propose to use godot-zig to bind GDExtension to Elixir. This will allow us to leverage the power of Elixir’s concurrency and fault-tolerance features, which are ideal for creating distributed simulations."
+    "text": "No, this enhancement requires a deeper integration with GLTF Transform and understanding of the VRM specifications."
   },
   {
-    "objectID": "decisions/20240411-elixir-libgodot-zig.html#the-benefits",
-    "href": "decisions/20240411-elixir-libgodot-zig.html#the-benefits",
-    "title": "Rejected: Binding GDExtension to a C-like Language for Libgodot to Implement a Distributed Simulation",
+    "objectID": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Add VRM portable avatars and OMI_personality to the GLTF Transform tool",
     "section": "",
-    "text": "Enhanced simulation performance due to Elixir’s efficient handling of concurrent processes.\nImproved fault tolerance, as Elixir’s supervisor trees can automatically recover from errors.\nIncreased developer productivity, as Elixir’s syntax is concise and expressive."
+    "text": "Yes, implementing this feature will provide a valuable addition to the GLTF Transform tool and cater to the growing VRM community."
   },
   {
-    "objectID": "decisions/20240411-elixir-libgodot-zig.html#the-downsides",
-    "href": "decisions/20240411-elixir-libgodot-zig.html#the-downsides",
-    "title": "Rejected: Binding GDExtension to a C-like Language for Libgodot to Implement a Distributed Simulation",
+    "objectID": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html#references",
+    "href": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html#references",
+    "title": "Proposed: Add VRM portable avatars and OMI_personality to the GLTF Transform tool",
     "section": "",
-    "text": "Requires learning a new programming language (Elixir), which may increase the development time initially.\nPotential compatibility issues between Elixir and existing parts of the system."
+    "text": "V-Sekai\nFor an example similar to KHR_lights_punctual, refer to this implementation.\nNo known design for VRM glTF_transform. However, there are two npm packages by quantumcraft that deal with VRM data, but they’re not open source.\nThe glTF Transform CLI allows specifying a config file, which can register additional glTF extensions and CLI functionality. Check out the CLI configuration documentation. Needle Tools has been trying this approach for NEEDLE_* extensions.\nOMI_personality"
   },
   {
-    "objectID": "decisions/20240411-elixir-libgodot-zig.html#the-road-not-taken",
-    "href": "decisions/20240411-elixir-libgodot-zig.html#the-road-not-taken",
-    "title": "Rejected: Binding GDExtension to a C-like Language for Libgodot to Implement a Distributed Simulation",
+    "objectID": "decisions/20230519-v-sekai-roadmap.html",
+    "href": "decisions/20230519-v-sekai-roadmap.html",
+    "title": "Superseded: V-Sekai Roadmap and Goals 2023-05-19",
     "section": "",
-    "text": "We considered using other languages like Rust or Go, but they did not offer the same level of concurrency and fault-tolerance features as Elixir."
+    "text": "Superseded: V-Sekai Roadmap and Goals 2023-05-19\n\nMetadata\n\nStatus: superseded by 20230527-v-sekai-roadmap.md \nDeciders: V-Sekai,fire,lyuma,\nTags: V-Sekai,chatgpt4 summary,\n\n\n\nContext and Problem Statement\nWhat is the V-Sekai Roadmap and Goals?\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nThe roadmap presented here is short-term.\n\n\nDescribe how your proposal will work with code, pseudo-code, mock-ups, or diagrams\ngraph LR\n  subgraph Short Term\n    A[May 16th, 2023] --&gt; C[Assist Tokageit with Godot Engine 4.1 features before May 30th feature freeze]\n    B --&gt; D[Assist Godot Engine 4.1 features before May 30th feature freeze]\n    C --&gt; E\n    D --&gt; E[Vrm upload to the asset library after May 30th, 2023]\n    E --&gt; F[Unidot fix import bugs that blocked assets import]\n    F --&gt; G[Unidot Unity Import upload to the asset library after May 30th, 2023]\n    G --&gt; H[Implement onevoip]\n  end\n\n\nPositive Consequences\nWe can create V-Sekai easier.\n\n\nNegative Consequences\nOverhead might be hard.\n\n\nOption graveyard\n\nImplementing a custom voice chat solution instead of using onevoip\nWaiting for Godot Engine 4.2 instead of assisting with 4.1 features\nIgnoring SkeletonIK3D issues and focusing on other aspects\n\n\n\nIf this enhancement will be used infrequently, can it be worked around with a few lines of script?\nNo. This is a process.\n\n\nIs there a reason why this should be core and done by us?\nThis is a core process for V-Sekai.\n\n\nReferences\n\nV-Sekai"
   },
   {
-    "objectID": "decisions/20240411-elixir-libgodot-zig.html#the-infrequent-use-case",
-    "href": "decisions/20240411-elixir-libgodot-zig.html#the-infrequent-use-case",
-    "title": "Rejected: Binding GDExtension to a C-like Language for Libgodot to Implement a Distributed Simulation",
+    "objectID": "decisions/20231229-mRemoteNG.html",
+    "href": "decisions/20231229-mRemoteNG.html",
+    "title": "Proposed: Choosing a terminal emulator for Windows",
     "section": "",
-    "text": "This proposal may not be suitable for smaller projects that do not require complex distributed simulations."
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nA need for efficient and effective remote access to multiple devices. As the world becomes more interconnected, the ability to manage and control various devices remotely has become crucial.\n\n\n\nSoftware that can log into multiple devices, providing users with the ability to perform tasks on those devices without physical access.\n\n\n\nAccording to AlternativeTo, mRemoteNG is a popular open-source alternative to MobaXterm. It’s a fork of mRemote, an open source, tabbed, multi-protocol, remote connections manager.\nKey points:\n\nmRemoteNG is the most popular Windows alternative to MobaXterm.\nmRemoteNG is the most popular Open Source & free alternative to MobaXterm.\n\n\n\n\nThe upside of using mRemoteNG is its versatility and cost-effectiveness. Being an open-source tool, it allows for customization and improvements from the user community. It also supports multiple protocols for managing remote connections.\n\n\n\nThe downside could be the potential learning curve associated with using a new tool. Additionally, as it is open-source, support might not be as readily available or comprehensive as with commercial software.\n\n\n\nThe road not taken would be sticking with traditional, possibly proprietary, terminal emulators. While these may offer robust features and dedicated support, they often come at a significant cost and lack the flexibility of open-source solutions.\n\n\n\nAn infrequent use case might be using mRemoteNG for managing a small number of devices or connections. In such cases, the full potential of the tool may not be utilized.\n\n\n\nThis strategy is not in core and done by us. It involves leveraging an existing open-source solution to address our needs.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240411-elixir-libgodot-zig.html#in-core-and-done-by-us",
-    "href": "decisions/20240411-elixir-libgodot-zig.html#in-core-and-done-by-us",
-    "title": "Rejected: Binding GDExtension to a C-like Language for Libgodot to Implement a Distributed Simulation",
+    "objectID": "decisions/20231229-mRemoteNG.html#metadata",
+    "href": "decisions/20231229-mRemoteNG.html#metadata",
+    "title": "Proposed: Choosing a terminal emulator for Windows",
     "section": "",
-    "text": "The V-Sekai development team will implement this proposal."
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20240411-elixir-libgodot-zig.html#status",
-    "href": "decisions/20240411-elixir-libgodot-zig.html#status",
-    "title": "Rejected: Binding GDExtension to a C-like Language for Libgodot to Implement a Distributed Simulation",
+    "objectID": "decisions/20231229-mRemoteNG.html#the-backdrop",
+    "href": "decisions/20231229-mRemoteNG.html#the-backdrop",
+    "title": "Proposed: Choosing a terminal emulator for Windows",
     "section": "",
-    "text": "Status: Rejected"
+    "text": "A need for efficient and effective remote access to multiple devices. As the world becomes more interconnected, the ability to manage and control various devices remotely has become crucial."
   },
   {
-    "objectID": "decisions/20240411-elixir-libgodot-zig.html#decision-makers",
-    "href": "decisions/20240411-elixir-libgodot-zig.html#decision-makers",
-    "title": "Rejected: Binding GDExtension to a C-like Language for Libgodot to Implement a Distributed Simulation",
+    "objectID": "decisions/20231229-mRemoteNG.html#the-challenge",
+    "href": "decisions/20231229-mRemoteNG.html#the-challenge",
+    "title": "Proposed: Choosing a terminal emulator for Windows",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "Software that can log into multiple devices, providing users with the ability to perform tasks on those devices without physical access."
   },
   {
-    "objectID": "decisions/20240411-elixir-libgodot-zig.html#tags",
-    "href": "decisions/20240411-elixir-libgodot-zig.html#tags",
-    "title": "Rejected: Binding GDExtension to a C-like Language for Libgodot to Implement a Distributed Simulation",
+    "objectID": "decisions/20231229-mRemoteNG.html#the-strategy",
+    "href": "decisions/20231229-mRemoteNG.html#the-strategy",
+    "title": "Proposed: Choosing a terminal emulator for Windows",
     "section": "",
-    "text": "V-Sekai"
+    "text": "According to AlternativeTo, mRemoteNG is a popular open-source alternative to MobaXterm. It’s a fork of mRemote, an open source, tabbed, multi-protocol, remote connections manager.\nKey points:\n\nmRemoteNG is the most popular Windows alternative to MobaXterm.\nmRemoteNG is the most popular Open Source & free alternative to MobaXterm."
   },
   {
-    "objectID": "decisions/20240411-elixir-libgodot-zig.html#further-reading",
-    "href": "decisions/20240411-elixir-libgodot-zig.html#further-reading",
-    "title": "Rejected: Binding GDExtension to a C-like Language for Libgodot to Implement a Distributed Simulation",
+    "objectID": "decisions/20231229-mRemoteNG.html#the-upside",
+    "href": "decisions/20231229-mRemoteNG.html#the-upside",
+    "title": "Proposed: Choosing a terminal emulator for Windows",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\ngodot-zig\nzigler\n\nAssisted by Aria."
+    "text": "The upside of using mRemoteNG is its versatility and cost-effectiveness. Being an open-source tool, it allows for customization and improvements from the user community. It also supports multiple protocols for managing remote connections."
   },
   {
-    "objectID": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html",
-    "href": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html",
-    "title": "Draft: Preview #materialx materials on the Web in Godot Engine",
+    "objectID": "decisions/20231229-mRemoteNG.html#the-downside",
+    "href": "decisions/20231229-mRemoteNG.html#the-downside",
+    "title": "Proposed: Choosing a terminal emulator for Windows",
     "section": "",
-    "text": "Status: draft \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nThere is no process for previewing #materialx on the web.\n\n\n\nPropose using Godot Engine 4.0 as a WebGL2 previewer for MaterialX.\n\n\n\n\nCompile Godot Engine 4.0 for WebGL2\nMake a 2D app\nExport to the Itch.io web store.\n\n\n\n\n\nCan use the same code base as the rest\n\n\n\n\n\nGodot monopolizing yet another platform.\n\n\n\n\n\nOption: \nRejection Reason: \n\n\n\n\nThis requires devops.\n\n\n\nCan be outside of core.\n\n\n\n\nhttps://github.com/godotengine/godot\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "The downside could be the potential learning curve associated with using a new tool. Additionally, as it is open-source, support might not be as readily available or comprehensive as with commercial software."
   },
   {
-    "objectID": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html#context-and-problem-statement",
-    "href": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html#context-and-problem-statement",
-    "title": "Draft: Preview #materialx materials on the Web in Godot Engine",
+    "objectID": "decisions/20231229-mRemoteNG.html#the-road-not-taken",
+    "href": "decisions/20231229-mRemoteNG.html#the-road-not-taken",
+    "title": "Proposed: Choosing a terminal emulator for Windows",
     "section": "",
-    "text": "There is no process for previewing #materialx on the web."
+    "text": "The road not taken would be sticking with traditional, possibly proprietary, terminal emulators. While these may offer robust features and dedicated support, they often come at a significant cost and lack the flexibility of open-source solutions."
   },
   {
-    "objectID": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Draft: Preview #materialx materials on the Web in Godot Engine",
+    "objectID": "decisions/20231229-mRemoteNG.html#the-infrequent-use-case",
+    "href": "decisions/20231229-mRemoteNG.html#the-infrequent-use-case",
+    "title": "Proposed: Choosing a terminal emulator for Windows",
     "section": "",
-    "text": "Propose using Godot Engine 4.0 as a WebGL2 previewer for MaterialX."
+    "text": "An infrequent use case might be using mRemoteNG for managing a small number of devices or connections. In such cases, the full potential of the tool may not be utilized."
   },
   {
-    "objectID": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Draft: Preview #materialx materials on the Web in Godot Engine",
+    "objectID": "decisions/20231229-mRemoteNG.html#in-core-and-done-by-us",
+    "href": "decisions/20231229-mRemoteNG.html#in-core-and-done-by-us",
+    "title": "Proposed: Choosing a terminal emulator for Windows",
     "section": "",
-    "text": "Compile Godot Engine 4.0 for WebGL2\nMake a 2D app\nExport to the Itch.io web store."
+    "text": "This strategy is not in core and done by us. It involves leveraging an existing open-source solution to address our needs."
   },
   {
-    "objectID": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html#positive-consequences",
-    "href": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html#positive-consequences",
-    "title": "Draft: Preview #materialx materials on the Web in Godot Engine",
+    "objectID": "decisions/20231229-mRemoteNG.html#further-reading",
+    "href": "decisions/20231229-mRemoteNG.html#further-reading",
+    "title": "Proposed: Choosing a terminal emulator for Windows",
     "section": "",
-    "text": "Can use the same code base as the rest"
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html#negative-consequences",
-    "href": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html#negative-consequences",
-    "title": "Draft: Preview #materialx materials on the Web in Godot Engine",
+    "objectID": "decisions/20210811-omi-glb.html",
+    "href": "decisions/20210811-omi-glb.html",
+    "title": "Proposed: OMI Glb Portable Content",
     "section": "",
-    "text": "Godot monopolizing yet another platform."
+    "text": "Proposed: OMI Glb Portable Content\n\nContext and Problem Statement\nWe desire portable content.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nCreate an art workflow.\n[Blender] -&gt; [OMI.glb]\n[OMI.glb] -&gt; [Godot Engine Packed Scene]\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nCreate an OMI Blender addon under W3C license.\nCreate glTF2 extension pull request for Godot Engine.\nFlow:\n\nOMI importer to Blender\nExporter of extended blender with OMI extensions to extended gltf\nSupport for OMI extended gltf in godot with definition of in-memory format for OMI extensions in Godot Engine for bidirectionality.\n\nExpected output:\n\nExport/Import as OMI format in Blender\nSupport OMI GLB in Godot\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nInterlapping projects are complicated.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nCan collaborate with Mozilla hubs team and OMI.\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html#option-graveyard",
-    "href": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html#option-graveyard",
-    "title": "Draft: Preview #materialx materials on the Web in Godot Engine",
+    "objectID": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html",
+    "href": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html",
+    "title": "Draft: Create a VRM character by experimenting with written workflows.",
     "section": "",
-    "text": "Option: \nRejection Reason:"
+    "text": "Status: draft \nDeciders: V-Sekai,fire,\nTags: V-Sekai,\n\n\n\nWant to experiment with character creation workflows.\n\n\n\nWant to document VRM character creation workflows.\n\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\n\n\n\n\nChecks can be automated for use in a workshop.\n\n\n\n\n\n[e.g., compromising quality attribute, follow-up decisions required, …]\n\n[this section can be repeated for each option if more than one option is open for consideration]\n\n\n\n\nOption: \nRejection Reason: \n\n\n\n\nThis is educational material and not code.\n\n\n\nI know how to do this.\n\n\n\n\nhttps://github.com/vrm-c\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Draft: Preview #materialx materials on the Web in Godot Engine",
+    "objectID": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html#context-and-problem-statement",
+    "href": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html#context-and-problem-statement",
+    "title": "Draft: Create a VRM character by experimenting with written workflows.",
     "section": "",
-    "text": "This requires devops."
+    "text": "Want to experiment with character creation workflows."
   },
   {
-    "objectID": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Draft: Preview #materialx materials on the Web in Godot Engine",
+    "objectID": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Draft: Create a VRM character by experimenting with written workflows.",
     "section": "",
-    "text": "Can be outside of core."
+    "text": "Want to document VRM character creation workflows."
   },
   {
-    "objectID": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html#references",
-    "href": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html#references",
-    "title": "Draft: Preview #materialx materials on the Web in Godot Engine",
+    "objectID": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Draft: Create a VRM character by experimenting with written workflows.",
     "section": "",
-    "text": "https://github.com/godotengine/godot"
+    "text": "Describe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams"
   },
   {
-    "objectID": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html#derivative-license",
-    "href": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html#derivative-license",
-    "title": "Draft: Preview #materialx materials on the Web in Godot Engine",
+    "objectID": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html#positive-consequences",
+    "href": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html#positive-consequences",
+    "title": "Draft: Create a VRM character by experimenting with written workflows.",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Checks can be automated for use in a workshop."
   },
   {
-    "objectID": "decisions/20230831-fixing-menus.html",
-    "href": "decisions/20230831-fixing-menus.html",
-    "title": "Accepted: Fix menus in-game",
+    "objectID": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html#negative-consequences",
+    "href": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html#negative-consequences",
+    "title": "Draft: Create a VRM character by experimenting with written workflows.",
     "section": "",
-    "text": "Status: accepted\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\n\n\n\nThe menus in-game are unable to capture events from the VR controllers.\n\n\n\nDebug the on_pointer_pressed function as it is not working correctly due to an issue with Transform3D.xform_inv. The current implementation mimics mouse input, but it fails to translate global positions correctly. Review the global_to_viewport function and ensure it returns the correct value for local_at.\n\n\n\nFixing the menus will enable players to interact with them using VR controllers, enhancing the user experience.\n\n\n\nFixing the menus may require significant code changes, introducing potential bugs or conflicts that need proper testing to ensure stability.\n\n\n\nExploring alternative input systems specifically designed for VR controllers could be considered, but it may involve rewriting a large portion of the menu code and potentially introducing new dependencies.\n\n\n\nThis fix targets players using VR controllers to interact with the menus. Players without VR controllers will not be affected.\n\n\n\nYes, this issue falls within our core development responsibilities, and we will take ownership of fixing the menus.\n\n\n\n\nV-Sekai\nThis article is assisted by AI."
+    "text": "[e.g., compromising quality attribute, follow-up decisions required, …]\n\n[this section can be repeated for each option if more than one option is open for consideration]"
   },
   {
-    "objectID": "decisions/20230831-fixing-menus.html#metadata",
-    "href": "decisions/20230831-fixing-menus.html#metadata",
-    "title": "Accepted: Fix menus in-game",
+    "objectID": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html#option-graveyard",
+    "href": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html#option-graveyard",
+    "title": "Draft: Create a VRM character by experimenting with written workflows.",
     "section": "",
-    "text": "Status: accepted\nDeciders: V-Sekai\nTags: V-Sekai"
+    "text": "Option: \nRejection Reason:"
   },
   {
-    "objectID": "decisions/20230831-fixing-menus.html#the-challenge",
-    "href": "decisions/20230831-fixing-menus.html#the-challenge",
-    "title": "Accepted: Fix menus in-game",
+    "objectID": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Draft: Create a VRM character by experimenting with written workflows.",
     "section": "",
-    "text": "The menus in-game are unable to capture events from the VR controllers."
+    "text": "This is educational material and not code."
   },
   {
-    "objectID": "decisions/20230831-fixing-menus.html#the-strategy",
-    "href": "decisions/20230831-fixing-menus.html#the-strategy",
-    "title": "Accepted: Fix menus in-game",
+    "objectID": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Draft: Create a VRM character by experimenting with written workflows.",
     "section": "",
-    "text": "Debug the on_pointer_pressed function as it is not working correctly due to an issue with Transform3D.xform_inv. The current implementation mimics mouse input, but it fails to translate global positions correctly. Review the global_to_viewport function and ensure it returns the correct value for local_at."
+    "text": "I know how to do this."
   },
   {
-    "objectID": "decisions/20230831-fixing-menus.html#the-upside",
-    "href": "decisions/20230831-fixing-menus.html#the-upside",
-    "title": "Accepted: Fix menus in-game",
+    "objectID": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html#references",
+    "href": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html#references",
+    "title": "Draft: Create a VRM character by experimenting with written workflows.",
     "section": "",
-    "text": "Fixing the menus will enable players to interact with them using VR controllers, enhancing the user experience."
+    "text": "https://github.com/vrm-c"
   },
   {
-    "objectID": "decisions/20230831-fixing-menus.html#the-downside",
-    "href": "decisions/20230831-fixing-menus.html#the-downside",
-    "title": "Accepted: Fix menus in-game",
+    "objectID": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html#derivative-license",
+    "href": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html#derivative-license",
+    "title": "Draft: Create a VRM character by experimenting with written workflows.",
     "section": "",
-    "text": "Fixing the menus may require significant code changes, introducing potential bugs or conflicts that need proper testing to ensure stability."
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230831-fixing-menus.html#the-road-not-taken",
-    "href": "decisions/20230831-fixing-menus.html#the-road-not-taken",
-    "title": "Accepted: Fix menus in-game",
+    "objectID": "decisions/20231227-blue-green-shadows.html",
+    "href": "decisions/20231227-blue-green-shadows.html",
+    "title": "Proposed: Blue Green new shadows for new avatars",
     "section": "",
-    "text": "Exploring alternative input systems specifically designed for VR controllers could be considered, but it may involve rewriting a large portion of the menu code and potentially introducing new dependencies."
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nThe default avatar format in V-Sekai, vrm0, has a shadow color that is too pink (F7CFDB). This has been a point of contention among users and developers alike.\n\n\n\nThe challenge lies in changing the default shadow color for new models to something more universally appealing. Two colors have been suggested as alternatives:\n\n\n\nColor Description\nASCII Hex Code\n\n\n\n\nSage Green\n#8F9779\n\n\nSoft Sky Blue\n#B4C8E5\n\n\n\n\n\n\nThe strategy would involve modifying the default settings in the vrm0 avatar format for new models to use one of the proposed colors instead of the current pink shade.\n\n\n\nChanging the default shadow color for new models could lead to a more visually pleasing user experience. It could also potentially increase user satisfaction and engagement.\n\n\n\nSome users may prefer the current pink shadow color. Changing it for new models could lead to dissatisfaction among this group of users.\n\n\n\nAn alternative approach could be to allow users to customize the shadow color themselves. However, this could potentially complicate the user interface and make the platform more difficult to use for beginners.\n\n\n\nIn some cases, the pink shadow color might actually be preferred. For example, in certain lighting conditions or for certain types of avatars, the pink color might look better than the proposed alternatives.\n\n\n\nThis change would need to be implemented by the V-Sekai development team. It would likely require modifications to the core code of the platform.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nThis article was assisted by Aria, your AI assistant."
   },
   {
-    "objectID": "decisions/20230831-fixing-menus.html#the-infrequent-use-case",
-    "href": "decisions/20230831-fixing-menus.html#the-infrequent-use-case",
-    "title": "Accepted: Fix menus in-game",
+    "objectID": "decisions/20231227-blue-green-shadows.html#metadata",
+    "href": "decisions/20231227-blue-green-shadows.html#metadata",
+    "title": "Proposed: Blue Green new shadows for new avatars",
     "section": "",
-    "text": "This fix targets players using VR controllers to interact with the menus. Players without VR controllers will not be affected."
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20230831-fixing-menus.html#in-core-and-done-by-us",
-    "href": "decisions/20230831-fixing-menus.html#in-core-and-done-by-us",
-    "title": "Accepted: Fix menus in-game",
+    "objectID": "decisions/20231227-blue-green-shadows.html#the-backdrop",
+    "href": "decisions/20231227-blue-green-shadows.html#the-backdrop",
+    "title": "Proposed: Blue Green new shadows for new avatars",
     "section": "",
-    "text": "Yes, this issue falls within our core development responsibilities, and we will take ownership of fixing the menus."
+    "text": "The default avatar format in V-Sekai, vrm0, has a shadow color that is too pink (F7CFDB). This has been a point of contention among users and developers alike."
   },
   {
-    "objectID": "decisions/20230831-fixing-menus.html#further-reading",
-    "href": "decisions/20230831-fixing-menus.html#further-reading",
-    "title": "Accepted: Fix menus in-game",
+    "objectID": "decisions/20231227-blue-green-shadows.html#the-challenge",
+    "href": "decisions/20231227-blue-green-shadows.html#the-challenge",
+    "title": "Proposed: Blue Green new shadows for new avatars",
     "section": "",
-    "text": "V-Sekai\nThis article is assisted by AI."
+    "text": "The challenge lies in changing the default shadow color for new models to something more universally appealing. Two colors have been suggested as alternatives:\n\n\n\nColor Description\nASCII Hex Code\n\n\n\n\nSage Green\n#8F9779\n\n\nSoft Sky Blue\n#B4C8E5"
   },
   {
-    "objectID": "decisions/20240407-pcvr-vs-standalone.html",
-    "href": "decisions/20240407-pcvr-vs-standalone.html",
-    "title": "Accepted: Focusing on PCVR vs Android Build vs Web Build",
+    "objectID": "decisions/20231227-blue-green-shadows.html#the-strategy",
+    "href": "decisions/20231227-blue-green-shadows.html#the-strategy",
+    "title": "Proposed: Blue Green new shadows for new avatars",
     "section": "",
-    "text": "V-Sekai is a project that aims to bring social VR functionality to the Godot Engine. The current dilemma is whether to focus on an Android/Web build, potentially moving away from PCVR as the primary platform, or continue focusing on PCVR.\n\n\n\nThe team lacks a high-powered enterprise sales team for enterprise PCVR. The mobile Vulkan is considered due to its ability to use compute shaders to skeleton skin meshes for large avatar counts. However, Meta dominates the standalone VR software market, and matching their offerings requires a superior product.\nMeta dominates the standalone VR software market but they are limited by the laws of physics.\n\n\n\nGiven the current market situation and V-Sekai’s capabilities, it is suggested to focus on PCVR. This platform can offer high-quality AAA games with lots of content, which standalone games cannot currently provide.\n\n\n\n\nAbility to offer high-quality AAA games with lots of content.\nLess crowded market compared to the standalone VR software market.\nWe can make more experiences.\nWe can make better experiences.\nThe PCVR hardware is more capable (vulkan, shader functions, less need to optimize), so the same experiences are easier to create.\nPCVR is easier to develop and test.\nPCVR is more open to collaboration.\n\n\n\n\n\nRequires a significant investment in PCVR development.\nThe market for PCVR is growing but lacks spotlight.\n\n\n\n\nFocusing on an Android build would mean entering a highly competitive market dominated by established players like Meta. It would also require aggressively pursuing game developers for exclusive content, which could be a challenging strategy.\n\n\n\nIf Meta decides to shift focus towards the consumer AR market, leaving the gaming market, there could be an opportunity for V-Sekai to fill the gap.\n\n\n\nThe decision to focus on PCVR will be a core strategy for V-Sekai, implemented by the development team.\n\n\n\nAccepted\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\nPCVR\nVR Development\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis article was assisted by AI assistant Aria."
+    "text": "The strategy would involve modifying the default settings in the vrm0 avatar format for new models to use one of the proposed colors instead of the current pink shade."
   },
   {
-    "objectID": "decisions/20240407-pcvr-vs-standalone.html#context",
-    "href": "decisions/20240407-pcvr-vs-standalone.html#context",
-    "title": "Accepted: Focusing on PCVR vs Android Build vs Web Build",
+    "objectID": "decisions/20231227-blue-green-shadows.html#the-upside",
+    "href": "decisions/20231227-blue-green-shadows.html#the-upside",
+    "title": "Proposed: Blue Green new shadows for new avatars",
     "section": "",
-    "text": "V-Sekai is a project that aims to bring social VR functionality to the Godot Engine. The current dilemma is whether to focus on an Android/Web build, potentially moving away from PCVR as the primary platform, or continue focusing on PCVR."
+    "text": "Changing the default shadow color for new models could lead to a more visually pleasing user experience. It could also potentially increase user satisfaction and engagement."
   },
   {
-    "objectID": "decisions/20240407-pcvr-vs-standalone.html#problem-statement",
-    "href": "decisions/20240407-pcvr-vs-standalone.html#problem-statement",
-    "title": "Accepted: Focusing on PCVR vs Android Build vs Web Build",
+    "objectID": "decisions/20231227-blue-green-shadows.html#the-downside",
+    "href": "decisions/20231227-blue-green-shadows.html#the-downside",
+    "title": "Proposed: Blue Green new shadows for new avatars",
     "section": "",
-    "text": "The team lacks a high-powered enterprise sales team for enterprise PCVR. The mobile Vulkan is considered due to its ability to use compute shaders to skeleton skin meshes for large avatar counts. However, Meta dominates the standalone VR software market, and matching their offerings requires a superior product.\nMeta dominates the standalone VR software market but they are limited by the laws of physics."
+    "text": "Some users may prefer the current pink shadow color. Changing it for new models could lead to dissatisfaction among this group of users."
   },
   {
-    "objectID": "decisions/20240407-pcvr-vs-standalone.html#proposal",
-    "href": "decisions/20240407-pcvr-vs-standalone.html#proposal",
-    "title": "Accepted: Focusing on PCVR vs Android Build vs Web Build",
+    "objectID": "decisions/20231227-blue-green-shadows.html#the-road-not-taken",
+    "href": "decisions/20231227-blue-green-shadows.html#the-road-not-taken",
+    "title": "Proposed: Blue Green new shadows for new avatars",
     "section": "",
-    "text": "Given the current market situation and V-Sekai’s capabilities, it is suggested to focus on PCVR. This platform can offer high-quality AAA games with lots of content, which standalone games cannot currently provide."
+    "text": "An alternative approach could be to allow users to customize the shadow color themselves. However, this could potentially complicate the user interface and make the platform more difficult to use for beginners."
   },
   {
-    "objectID": "decisions/20240407-pcvr-vs-standalone.html#benefits",
-    "href": "decisions/20240407-pcvr-vs-standalone.html#benefits",
-    "title": "Accepted: Focusing on PCVR vs Android Build vs Web Build",
+    "objectID": "decisions/20231227-blue-green-shadows.html#the-infrequent-use-case",
+    "href": "decisions/20231227-blue-green-shadows.html#the-infrequent-use-case",
+    "title": "Proposed: Blue Green new shadows for new avatars",
     "section": "",
-    "text": "Ability to offer high-quality AAA games with lots of content.\nLess crowded market compared to the standalone VR software market.\nWe can make more experiences.\nWe can make better experiences.\nThe PCVR hardware is more capable (vulkan, shader functions, less need to optimize), so the same experiences are easier to create.\nPCVR is easier to develop and test.\nPCVR is more open to collaboration."
+    "text": "In some cases, the pink shadow color might actually be preferred. For example, in certain lighting conditions or for certain types of avatars, the pink color might look better than the proposed alternatives."
   },
   {
-    "objectID": "decisions/20240407-pcvr-vs-standalone.html#downsides",
-    "href": "decisions/20240407-pcvr-vs-standalone.html#downsides",
-    "title": "Accepted: Focusing on PCVR vs Android Build vs Web Build",
+    "objectID": "decisions/20231227-blue-green-shadows.html#in-core-and-done-by-us",
+    "href": "decisions/20231227-blue-green-shadows.html#in-core-and-done-by-us",
+    "title": "Proposed: Blue Green new shadows for new avatars",
     "section": "",
-    "text": "Requires a significant investment in PCVR development.\nThe market for PCVR is growing but lacks spotlight."
+    "text": "This change would need to be implemented by the V-Sekai development team. It would likely require modifications to the core code of the platform."
   },
   {
-    "objectID": "decisions/20240407-pcvr-vs-standalone.html#the-road-not-taken",
-    "href": "decisions/20240407-pcvr-vs-standalone.html#the-road-not-taken",
-    "title": "Accepted: Focusing on PCVR vs Android Build vs Web Build",
+    "objectID": "decisions/20231227-blue-green-shadows.html#further-reading",
+    "href": "decisions/20231227-blue-green-shadows.html#further-reading",
+    "title": "Proposed: Blue Green new shadows for new avatars",
     "section": "",
-    "text": "Focusing on an Android build would mean entering a highly competitive market dominated by established players like Meta. It would also require aggressively pursuing game developers for exclusive content, which could be a challenging strategy."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nThis article was assisted by Aria, your AI assistant."
   },
   {
-    "objectID": "decisions/20240407-pcvr-vs-standalone.html#infrequent-use-case",
-    "href": "decisions/20240407-pcvr-vs-standalone.html#infrequent-use-case",
-    "title": "Accepted: Focusing on PCVR vs Android Build vs Web Build",
+    "objectID": "decisions/20230824-subdiv-for-lods.html",
+    "href": "decisions/20230824-subdiv-for-lods.html",
+    "title": "Accepted: Use opensubdiv for level of detail",
     "section": "",
-    "text": "If Meta decides to shift focus towards the consumer AR market, leaving the gaming market, there could be an opportunity for V-Sekai to fill the gap."
+    "text": "Status: accepted \nDeciders: V-Sekai, fire\nTags: V-Sekai\n\n\n\n\nCreators want more. Players want more. The platform can only support a limited amount of content.\n\n\n\nThe challenge lies in optimizing the content to fit within the platform’s limitations without compromising on the quality and detail.\n\n\n\nUse OpenSubdiv to increase detail, which can then be reduced through Godot Engine’s LOD (Level of Detail) scheme. This allows for high-quality models that are optimized for performance.\n\n\n\nThe upside is that this approach allows for more detailed models while still maintaining good performance.\n\n\n\nThe downside is that it requires additional processing to create the LOD models, which could potentially slow down the development process.\n\n\n\nAn alternative approach would have been to manually create lower detail models for use in less demanding scenarios. However, this would require significantly more work from the creators.\n\n\n\nThis strategy might not be beneficial for very simple models or scenes where the level of detail is not a significant factor.\n\n\n\nYes, this strategy is implemented in the core of our platform and maintained by us.\n\n\n\n\nV-Sekai\nThis article is assisted by AI."
   },
   {
-    "objectID": "decisions/20240407-pcvr-vs-standalone.html#in-core-and-done-by-us",
-    "href": "decisions/20240407-pcvr-vs-standalone.html#in-core-and-done-by-us",
-    "title": "Accepted: Focusing on PCVR vs Android Build vs Web Build",
+    "objectID": "decisions/20230824-subdiv-for-lods.html#metadata",
+    "href": "decisions/20230824-subdiv-for-lods.html#metadata",
+    "title": "Accepted: Use opensubdiv for level of detail",
     "section": "",
-    "text": "The decision to focus on PCVR will be a core strategy for V-Sekai, implemented by the development team."
+    "text": "Status: accepted \nDeciders: V-Sekai, fire\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20240407-pcvr-vs-standalone.html#status",
-    "href": "decisions/20240407-pcvr-vs-standalone.html#status",
-    "title": "Accepted: Focusing on PCVR vs Android Build vs Web Build",
+    "objectID": "decisions/20230824-subdiv-for-lods.html#the-backdrop",
+    "href": "decisions/20230824-subdiv-for-lods.html#the-backdrop",
+    "title": "Accepted: Use opensubdiv for level of detail",
     "section": "",
-    "text": "Accepted"
+    "text": "Creators want more. Players want more. The platform can only support a limited amount of content."
   },
   {
-    "objectID": "decisions/20240407-pcvr-vs-standalone.html#decision-makers",
-    "href": "decisions/20240407-pcvr-vs-standalone.html#decision-makers",
-    "title": "Accepted: Focusing on PCVR vs Android Build vs Web Build",
+    "objectID": "decisions/20230824-subdiv-for-lods.html#the-challenge",
+    "href": "decisions/20230824-subdiv-for-lods.html#the-challenge",
+    "title": "Accepted: Use opensubdiv for level of detail",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "The challenge lies in optimizing the content to fit within the platform’s limitations without compromising on the quality and detail."
   },
   {
-    "objectID": "decisions/20240407-pcvr-vs-standalone.html#tags",
-    "href": "decisions/20240407-pcvr-vs-standalone.html#tags",
-    "title": "Accepted: Focusing on PCVR vs Android Build vs Web Build",
+    "objectID": "decisions/20230824-subdiv-for-lods.html#the-strategy",
+    "href": "decisions/20230824-subdiv-for-lods.html#the-strategy",
+    "title": "Accepted: Use opensubdiv for level of detail",
     "section": "",
-    "text": "V-Sekai\nPCVR\nVR Development"
+    "text": "Use OpenSubdiv to increase detail, which can then be reduced through Godot Engine’s LOD (Level of Detail) scheme. This allows for high-quality models that are optimized for performance."
   },
   {
-    "objectID": "decisions/20240407-pcvr-vs-standalone.html#further-reading",
-    "href": "decisions/20240407-pcvr-vs-standalone.html#further-reading",
-    "title": "Accepted: Focusing on PCVR vs Android Build vs Web Build",
+    "objectID": "decisions/20230824-subdiv-for-lods.html#the-upside",
+    "href": "decisions/20230824-subdiv-for-lods.html#the-upside",
+    "title": "Accepted: Use opensubdiv for level of detail",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis article was assisted by AI assistant Aria."
+    "text": "The upside is that this approach allows for more detailed models while still maintaining good performance."
   },
   {
-    "objectID": "decisions/20230803-idle-rpg-home.html",
-    "href": "decisions/20230803-idle-rpg-home.html",
-    "title": "Proposed: Social RPG World Proposal",
+    "objectID": "decisions/20230824-subdiv-for-lods.html#the-downside",
+    "href": "decisions/20230824-subdiv-for-lods.html#the-downside",
+    "title": "Accepted: Use opensubdiv for level of detail",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nWe aim to engage users in the V-Sekai world. A social RPG game could be the solution, offering continuous gameplay that encourages interaction.\n\n\n\n\n\nOur game is set in a “Comfortable Cyberprep” realm. It merges sci-fi with ease, where tech and humans coexist. Players explore a future city where technology is part of life. The city glows with neon lights, holographic interfaces, and advanced AI, yet retains homeliness.\n\nStatic couch collider: A fixed location for player interaction.\nNon-functional Static bed without collider: A rejuvenation spot for characters.\nNon-functional Mirror that is off: A decorative element with potential uses.\nNon-functional Video player screen that is off: A feature for entertainment or information.\n\n\n\n\n\nChill and hang with friends: The game provides a relaxed environment for socializing.\nPlay a game: Beyond socializing, players can engage in an RPG game.\n\n\n\n\n\nRPG game with level rewards: Players improve through play.\nCombat System: Players choose between different types of weapons or defensive items.\nStationary Target Combat System: A mechanism where players engage in combat with fixed-position targets.\n\n\n\n\n\nSettings are not persisted past server restart.\nLimited number of weapon choices: To maintain balance.\nCooldown period for using healing items: To prevent spamming.\n\n\n\n\n\nImplementation details will be decided upon proposal acceptance.\n\n\n\n\nIncreased user engagement\nProlonged interaction within the V-Sekai world\nEnhanced socialization among players\n\n\n\n\n\nPotential increase in development time and resources\nRisk of unbalanced gameplay if the RPG system is not properly designed\n\n\n\n\nOptions considered but discarded:\n\nIdle RPG Mechanic: Removed due to potential decrease in active engagement from players.\n\n\n\n\nThe frequency of use depends on the players’ engagement level. However, given the complexity of an RPG system, it cannot be simply worked around with a few lines of script.\n\n\n\nCreating an RPG system as a feature of V-Sekai will enhance the overall user experience and engagement, which aligns with our goal of providing a compelling virtual world.\n\n\n\n\nV-Sekai"
+    "text": "The downside is that it requires additional processing to create the LOD models, which could potentially slow down the development process."
   },
   {
-    "objectID": "decisions/20230803-idle-rpg-home.html#metadata",
-    "href": "decisions/20230803-idle-rpg-home.html#metadata",
-    "title": "Proposed: Social RPG World Proposal",
+    "objectID": "decisions/20230824-subdiv-for-lods.html#the-road-not-taken",
+    "href": "decisions/20230824-subdiv-for-lods.html#the-road-not-taken",
+    "title": "Accepted: Use opensubdiv for level of detail",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai"
+    "text": "An alternative approach would have been to manually create lower detail models for use in less demanding scenarios. However, this would require significantly more work from the creators."
   },
   {
-    "objectID": "decisions/20230803-idle-rpg-home.html#context-and-problem-statement",
-    "href": "decisions/20230803-idle-rpg-home.html#context-and-problem-statement",
-    "title": "Proposed: Social RPG World Proposal",
+    "objectID": "decisions/20230824-subdiv-for-lods.html#the-infrequent-use-case",
+    "href": "decisions/20230824-subdiv-for-lods.html#the-infrequent-use-case",
+    "title": "Accepted: Use opensubdiv for level of detail",
     "section": "",
-    "text": "We aim to engage users in the V-Sekai world. A social RPG game could be the solution, offering continuous gameplay that encourages interaction."
+    "text": "This strategy might not be beneficial for very simple models or scenes where the level of detail is not a significant factor."
   },
   {
-    "objectID": "decisions/20230803-idle-rpg-home.html#proposed-solution",
-    "href": "decisions/20230803-idle-rpg-home.html#proposed-solution",
-    "title": "Proposed: Social RPG World Proposal",
+    "objectID": "decisions/20230824-subdiv-for-lods.html#in-core-and-done-by-us",
+    "href": "decisions/20230824-subdiv-for-lods.html#in-core-and-done-by-us",
+    "title": "Accepted: Use opensubdiv for level of detail",
     "section": "",
-    "text": "Our game is set in a “Comfortable Cyberprep” realm. It merges sci-fi with ease, where tech and humans coexist. Players explore a future city where technology is part of life. The city glows with neon lights, holographic interfaces, and advanced AI, yet retains homeliness.\n\nStatic couch collider: A fixed location for player interaction.\nNon-functional Static bed without collider: A rejuvenation spot for characters.\nNon-functional Mirror that is off: A decorative element with potential uses.\nNon-functional Video player screen that is off: A feature for entertainment or information.\n\n\n\n\n\nChill and hang with friends: The game provides a relaxed environment for socializing.\nPlay a game: Beyond socializing, players can engage in an RPG game.\n\n\n\n\n\nRPG game with level rewards: Players improve through play.\nCombat System: Players choose between different types of weapons or defensive items.\nStationary Target Combat System: A mechanism where players engage in combat with fixed-position targets.\n\n\n\n\n\nSettings are not persisted past server restart.\nLimited number of weapon choices: To maintain balance.\nCooldown period for using healing items: To prevent spamming."
+    "text": "Yes, this strategy is implemented in the core of our platform and maintained by us."
   },
   {
-    "objectID": "decisions/20230803-idle-rpg-home.html#implementation",
-    "href": "decisions/20230803-idle-rpg-home.html#implementation",
-    "title": "Proposed: Social RPG World Proposal",
+    "objectID": "decisions/20230824-subdiv-for-lods.html#further-reading",
+    "href": "decisions/20230824-subdiv-for-lods.html#further-reading",
+    "title": "Accepted: Use opensubdiv for level of detail",
     "section": "",
-    "text": "Implementation details will be decided upon proposal acceptance."
+    "text": "V-Sekai\nThis article is assisted by AI."
   },
   {
-    "objectID": "decisions/20230803-idle-rpg-home.html#positive-consequences",
-    "href": "decisions/20230803-idle-rpg-home.html#positive-consequences",
-    "title": "Proposed: Social RPG World Proposal",
+    "objectID": "decisions/20240217-container-2-wasm.html",
+    "href": "decisions/20240217-container-2-wasm.html",
+    "title": "Proposed: Container2Wasm Integration in V-Sekai",
     "section": "",
-    "text": "Increased user engagement\nProlonged interaction within the V-Sekai world\nEnhanced socialization among players"
+    "text": "V-Sekai is a project focused on social VR functionality for the Godot Engine. It aims to bring social VR/VRSNS/metaverse components to the Godot Engine, enhancing avatar customization and AI-driven facial expressions.\n\n\n\nIntegrating complex backend services directly within a browser or lightweight client environments can be challenging. This integration is crucial for enhancing avatar customization and AI-driven facial expressions by leveraging containerized services.\n\n\n\nWe propose to use container2wasm, a tool that converts container images to WebAssembly (WASM) format. This will enable these containers to run on WASM with emulation support for x86_64 and riscv64 containers. The tool works with various WASI runtimes like wasmtime, wamr, wasmer, wasmedge, and wazero, and it can also run in the browser.\n\nConvert container image to WASM using container2wasm\nDeploy the WASM module in the desired environment\nRun the WASM module using a suitable WASI runtime\n\n\n\n\n\nEnables running of containerized services directly in the browser or lightweight client environments.\nEnhances avatar customization and AI-driven facial expressions in V-Sekai.\nLeverages the power of WASM for efficient, safe, and portable execution.\n\n\n\n\n\nRequires understanding and maintenance of WASM modules.\nPotential compatibility issues with certain containerized services.\n\n\n\n\nAn alternative would be to run the backend services on dedicated servers and communicate with them via APIs. However, this could introduce latency and require more resources.\n\n\n\nIn scenarios where the backend service is not frequently used, converting it to WASM might not provide significant benefits.\n\n\n\nThe integration of container2wasm will be done by the V-Sekai development team with support from the community stakeholders.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team and community stakeholders.\n\n\n\n\n\nV-Sekai, Avatar Customization, AI, Facial Expressions\n\n\n\n\n\nV-Sekai · GitHub\nV-Sekai/v-sekai-game\nContainer2Wasm · GitHub\n\nThis proposal was assisted by Aria, an AI assistant."
   },
   {
-    "objectID": "decisions/20230803-idle-rpg-home.html#negative-consequences",
-    "href": "decisions/20230803-idle-rpg-home.html#negative-consequences",
-    "title": "Proposed: Social RPG World Proposal",
+    "objectID": "decisions/20240217-container-2-wasm.html#context",
+    "href": "decisions/20240217-container-2-wasm.html#context",
+    "title": "Proposed: Container2Wasm Integration in V-Sekai",
     "section": "",
-    "text": "Potential increase in development time and resources\nRisk of unbalanced gameplay if the RPG system is not properly designed"
+    "text": "V-Sekai is a project focused on social VR functionality for the Godot Engine. It aims to bring social VR/VRSNS/metaverse components to the Godot Engine, enhancing avatar customization and AI-driven facial expressions."
   },
   {
-    "objectID": "decisions/20230803-idle-rpg-home.html#option-graveyard",
-    "href": "decisions/20230803-idle-rpg-home.html#option-graveyard",
-    "title": "Proposed: Social RPG World Proposal",
+    "objectID": "decisions/20240217-container-2-wasm.html#problem-statement",
+    "href": "decisions/20240217-container-2-wasm.html#problem-statement",
+    "title": "Proposed: Container2Wasm Integration in V-Sekai",
     "section": "",
-    "text": "Options considered but discarded:\n\nIdle RPG Mechanic: Removed due to potential decrease in active engagement from players."
+    "text": "Integrating complex backend services directly within a browser or lightweight client environments can be challenging. This integration is crucial for enhancing avatar customization and AI-driven facial expressions by leveraging containerized services."
   },
   {
-    "objectID": "decisions/20230803-idle-rpg-home.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230803-idle-rpg-home.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Social RPG World Proposal",
+    "objectID": "decisions/20240217-container-2-wasm.html#proposed-solution",
+    "href": "decisions/20240217-container-2-wasm.html#proposed-solution",
+    "title": "Proposed: Container2Wasm Integration in V-Sekai",
     "section": "",
-    "text": "The frequency of use depends on the players’ engagement level. However, given the complexity of an RPG system, it cannot be simply worked around with a few lines of script."
+    "text": "We propose to use container2wasm, a tool that converts container images to WebAssembly (WASM) format. This will enable these containers to run on WASM with emulation support for x86_64 and riscv64 containers. The tool works with various WASI runtimes like wasmtime, wamr, wasmer, wasmedge, and wazero, and it can also run in the browser.\n\nConvert container image to WASM using container2wasm\nDeploy the WASM module in the desired environment\nRun the WASM module using a suitable WASI runtime"
   },
   {
-    "objectID": "decisions/20230803-idle-rpg-home.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230803-idle-rpg-home.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Social RPG World Proposal",
+    "objectID": "decisions/20240217-container-2-wasm.html#benefits",
+    "href": "decisions/20240217-container-2-wasm.html#benefits",
+    "title": "Proposed: Container2Wasm Integration in V-Sekai",
     "section": "",
-    "text": "Creating an RPG system as a feature of V-Sekai will enhance the overall user experience and engagement, which aligns with our goal of providing a compelling virtual world."
+    "text": "Enables running of containerized services directly in the browser or lightweight client environments.\nEnhances avatar customization and AI-driven facial expressions in V-Sekai.\nLeverages the power of WASM for efficient, safe, and portable execution."
   },
   {
-    "objectID": "decisions/20230803-idle-rpg-home.html#references",
-    "href": "decisions/20230803-idle-rpg-home.html#references",
-    "title": "Proposed: Social RPG World Proposal",
+    "objectID": "decisions/20240217-container-2-wasm.html#downsides",
+    "href": "decisions/20240217-container-2-wasm.html#downsides",
+    "title": "Proposed: Container2Wasm Integration in V-Sekai",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Requires understanding and maintenance of WASM modules.\nPotential compatibility issues with certain containerized services."
   },
   {
-    "objectID": "decisions/20230620-doi-github.html",
-    "href": "decisions/20230620-doi-github.html",
-    "title": "Proposed: A Potential Solution for V-Sekai’s Identifier Assignment Challenge",
+    "objectID": "decisions/20240217-container-2-wasm.html#the-road-not-taken",
+    "href": "decisions/20240217-container-2-wasm.html#the-road-not-taken",
+    "title": "Proposed: Container2Wasm Integration in V-Sekai",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai, fire\nTags: V-Sekai, AI-augmented\n\n\n\n\nV-Sekai requires a method to assign permanent Digital Object Identifiers (DOIs) to their digital artifacts.\n\n\n\nLeverage Github and Zenodo to create a permanent DOI for V-Sekai’s data and code.\n\n\n\nFollow these steps in the guide below:\n\nSet up a Github Repository\nConnect Github to Zenodo\nActivate Github Repository in Zenodo\nGenerate a Release in Github\nObtain Your DOI from Zenodo\nShowcase DOI Badge in Github README (optional)\n\n\n\n\n\nPersistent DOIs for data and code\nEffortless referencing of repositories across browsers\nEnhanced visibility and accessibility of V-Sekai’s digital artifacts\n\n\n\n\n\nNecessitates managing multiple platforms (Github and Zenodo)\nPossible learning curve for users unfamiliar with Github and Zenodo\n\n\n\n\n\nUtilizing Figshare: Figshare is an alternative platform that enables assigning DOIs to digital artifacts. However, its integration with Github may not be as smooth as Zenodo’s.\nManual DOI registration: Manually registering a DOI through agencies like DataCite or CrossRef. This option can be labor-intensive and might involve additional fees.\nDepending on publisher-assigned DOIs: Some publishers allocate DOIs to supplementary materials during article publication. However, this option relies on the publisher’s policies and may not encompass all digital artifacts.\nEmploying institutional repositories: Certain institutions provide their own repositories for hosting digital artifacts and assigning DOIs. This option could be constrained by institutional policies and access limitations.\nNo DOI: Opting not to assign a DOI to V-Sekai’s digital artifacts, which would complicate referencing and long-term accessibility.\n\n\n\n\nNo, this solution demands integration between Github and Zenodo to produce a permanent DOI.\n\n\n\nYes, allocating a permanent DOI to V-Sekai’s digital artifacts guarantees long-term accessibility and accurate referencing in publications or other materials.\n\n\n\n\nV-Sekai\nGithub\nZenodo\nhttps://github.com/GlobalEcologyFlinders/assignDOI"
+    "text": "An alternative would be to run the backend services on dedicated servers and communicate with them via APIs. However, this could introduce latency and require more resources."
   },
   {
-    "objectID": "decisions/20230620-doi-github.html#metadata",
-    "href": "decisions/20230620-doi-github.html#metadata",
-    "title": "Proposed: A Potential Solution for V-Sekai’s Identifier Assignment Challenge",
+    "objectID": "decisions/20240217-container-2-wasm.html#the-infrequent-use-case",
+    "href": "decisions/20240217-container-2-wasm.html#the-infrequent-use-case",
+    "title": "Proposed: Container2Wasm Integration in V-Sekai",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai, fire\nTags: V-Sekai, AI-augmented"
+    "text": "In scenarios where the backend service is not frequently used, converting it to WASM might not provide significant benefits."
   },
   {
-    "objectID": "decisions/20230620-doi-github.html#context-and-problem-statement",
-    "href": "decisions/20230620-doi-github.html#context-and-problem-statement",
-    "title": "Proposed: A Potential Solution for V-Sekai’s Identifier Assignment Challenge",
+    "objectID": "decisions/20240217-container-2-wasm.html#in-core-and-done-by-us",
+    "href": "decisions/20240217-container-2-wasm.html#in-core-and-done-by-us",
+    "title": "Proposed: Container2Wasm Integration in V-Sekai",
     "section": "",
-    "text": "V-Sekai requires a method to assign permanent Digital Object Identifiers (DOIs) to their digital artifacts."
+    "text": "The integration of container2wasm will be done by the V-Sekai development team with support from the community stakeholders."
   },
   {
-    "objectID": "decisions/20230620-doi-github.html#suggested-solution",
-    "href": "decisions/20230620-doi-github.html#suggested-solution",
-    "title": "Proposed: A Potential Solution for V-Sekai’s Identifier Assignment Challenge",
+    "objectID": "decisions/20240217-container-2-wasm.html#status",
+    "href": "decisions/20240217-container-2-wasm.html#status",
+    "title": "Proposed: Container2Wasm Integration in V-Sekai",
     "section": "",
-    "text": "Leverage Github and Zenodo to create a permanent DOI for V-Sekai’s data and code."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20230620-doi-github.html#implementation",
-    "href": "decisions/20230620-doi-github.html#implementation",
-    "title": "Proposed: A Potential Solution for V-Sekai’s Identifier Assignment Challenge",
+    "objectID": "decisions/20240217-container-2-wasm.html#decision-makers",
+    "href": "decisions/20240217-container-2-wasm.html#decision-makers",
+    "title": "Proposed: Container2Wasm Integration in V-Sekai",
     "section": "",
-    "text": "Follow these steps in the guide below:\n\nSet up a Github Repository\nConnect Github to Zenodo\nActivate Github Repository in Zenodo\nGenerate a Release in Github\nObtain Your DOI from Zenodo\nShowcase DOI Badge in Github README (optional)"
+    "text": "V-Sekai development team and community stakeholders."
   },
   {
-    "objectID": "decisions/20230620-doi-github.html#positive-consequences",
-    "href": "decisions/20230620-doi-github.html#positive-consequences",
-    "title": "Proposed: A Potential Solution for V-Sekai’s Identifier Assignment Challenge",
+    "objectID": "decisions/20240217-container-2-wasm.html#tags",
+    "href": "decisions/20240217-container-2-wasm.html#tags",
+    "title": "Proposed: Container2Wasm Integration in V-Sekai",
     "section": "",
-    "text": "Persistent DOIs for data and code\nEffortless referencing of repositories across browsers\nEnhanced visibility and accessibility of V-Sekai’s digital artifacts"
+    "text": "V-Sekai, Avatar Customization, AI, Facial Expressions"
   },
   {
-    "objectID": "decisions/20230620-doi-github.html#negative-consequences",
-    "href": "decisions/20230620-doi-github.html#negative-consequences",
-    "title": "Proposed: A Potential Solution for V-Sekai’s Identifier Assignment Challenge",
+    "objectID": "decisions/20240217-container-2-wasm.html#further-reading",
+    "href": "decisions/20240217-container-2-wasm.html#further-reading",
+    "title": "Proposed: Container2Wasm Integration in V-Sekai",
     "section": "",
-    "text": "Necessitates managing multiple platforms (Github and Zenodo)\nPossible learning curve for users unfamiliar with Github and Zenodo"
+    "text": "V-Sekai · GitHub\nV-Sekai/v-sekai-game\nContainer2Wasm · GitHub\n\nThis proposal was assisted by Aria, an AI assistant."
   },
   {
-    "objectID": "decisions/20230620-doi-github.html#alternative-options",
-    "href": "decisions/20230620-doi-github.html#alternative-options",
-    "title": "Proposed: A Potential Solution for V-Sekai’s Identifier Assignment Challenge",
+    "objectID": "decisions/20230626-godot-vrm1-addon.html",
+    "href": "decisions/20230626-godot-vrm1-addon.html",
+    "title": "Proposed: Ship Godot Engine VRM1 to solve portable humanoid avatars",
     "section": "",
-    "text": "Utilizing Figshare: Figshare is an alternative platform that enables assigning DOIs to digital artifacts. However, its integration with Github may not be as smooth as Zenodo’s.\nManual DOI registration: Manually registering a DOI through agencies like DataCite or CrossRef. This option can be labor-intensive and might involve additional fees.\nDepending on publisher-assigned DOIs: Some publishers allocate DOIs to supplementary materials during article publication. However, this option relies on the publisher’s policies and may not encompass all digital artifacts.\nEmploying institutional repositories: Certain institutions provide their own repositories for hosting digital artifacts and assigning DOIs. This option could be constrained by institutional policies and access limitations.\nNo DOI: Opting not to assign a DOI to V-Sekai’s digital artifacts, which would complicate referencing and long-term accessibility."
+    "text": "Status: proposed \nDeciders: V-Sekai, fire, lyuma\nTags: V-Sekai, ai copilot\n\n\n\n\nHave portable humanoid avatars.\n\n\n\nShip Godot Engine VRM1 to Godot Engine asset Library.\n\n\n\n\nImplement basic humanoid avatar functionality such as rigging, animation, and basic physics through VRM1 spring bones.\nImplement support for both MToon1 and MToon0 materials, which provide a physically-based rendering approach for anime-style graphics.\nImplement support for the glTF PBR material type, which provides a more physically-based rendering approach for realistic graphics.\nImplement facial expressions, eye tracking, and lip syncing for a more immersive experience.\nImplement export by copying the import code in reverse, and refine it over time.\nUse the VRM spec’s suggested algorithm for implementing first-person view, which eliminates the need for head scaling.\nPrioritize necessary features and say no to suggestions that are not necessary to avoid feature bloat.\nDo not implement AnimationTree for this proposal.\n\n\n\n\n\nPortable humanoid avatars can be easily created and used in Godot Engine projects.\nThe addition of MToon1 material support provides a physically-based rendering approach for anime-style graphics.\nFacial expressions, eye tracking, and lip syncing enhance the immersive experience for users.\nExport functionality allows for easy sharing of avatars between projects and with other users.\nThe use of the VRM spec’s suggested algorithm for implementing first-person view simplifies the implementation process.\n\n\n\n\n\nThe implementation of these features may require additional development time and resources.\nThe addition of new features may increase the complexity of the codebase and require additional maintenance.\nThe use of the MToon1 material may require additional GPU resources and may not be suitable for low-end hardware.\nThe implementation of facial expressions, eye tracking, and lip syncing may require additional hardware or software support.\n\n\n\n\nWe are not implementing support for other material types beyond MToon0, MToon1 and gltf PBR, which could limit the range of visual styles that can be achieved with Godot Engine.\n\n\n\nIt is unlikely that these enhancements can be easily worked around with a few lines of script, as they require significant development effort and integration with the Godot Engine codebase.\n\n\n\n\nPortable humanoid avatars are a key feature for many Godot Engine projects, and the ability to easily create and use them is important for the success of the engine.\nThe addition of MToon1 material support and other enhancements will improve the quality and visual fidelity of Godot Engine projects.\nBy implementing these features in-house, we can ensure that they are well-integrated with the Godot Engine codebase and meet our quality standards.\n\n\n\n\n\nV-Sekai\nhttps://github.com/vrm-c/vrm-specification\nhttps://github.com/vrm-c/vrm-specification/blob/master/specification/VRMC_vrm-1.0/firstPerson.md#meshannotationauto-algorithm"
   },
   {
-    "objectID": "decisions/20230620-doi-github.html#can-this-enhancement-be-worked-around-with-a-few-lines-of-script-if-used-infrequently",
-    "href": "decisions/20230620-doi-github.html#can-this-enhancement-be-worked-around-with-a-few-lines-of-script-if-used-infrequently",
-    "title": "Proposed: A Potential Solution for V-Sekai’s Identifier Assignment Challenge",
+    "objectID": "decisions/20230626-godot-vrm1-addon.html#metadata",
+    "href": "decisions/20230626-godot-vrm1-addon.html#metadata",
+    "title": "Proposed: Ship Godot Engine VRM1 to solve portable humanoid avatars",
     "section": "",
-    "text": "No, this solution demands integration between Github and Zenodo to produce a permanent DOI."
+    "text": "Status: proposed \nDeciders: V-Sekai, fire, lyuma\nTags: V-Sekai, ai copilot"
   },
   {
-    "objectID": "decisions/20230620-doi-github.html#is-there-a-reason-why-this-should-be-core-and-implemented-by-us",
-    "href": "decisions/20230620-doi-github.html#is-there-a-reason-why-this-should-be-core-and-implemented-by-us",
-    "title": "Proposed: A Potential Solution for V-Sekai’s Identifier Assignment Challenge",
+    "objectID": "decisions/20230626-godot-vrm1-addon.html#context-and-problem-statement",
+    "href": "decisions/20230626-godot-vrm1-addon.html#context-and-problem-statement",
+    "title": "Proposed: Ship Godot Engine VRM1 to solve portable humanoid avatars",
     "section": "",
-    "text": "Yes, allocating a permanent DOI to V-Sekai’s digital artifacts guarantees long-term accessibility and accurate referencing in publications or other materials."
+    "text": "Have portable humanoid avatars."
   },
   {
-    "objectID": "decisions/20230620-doi-github.html#references",
-    "href": "decisions/20230620-doi-github.html#references",
-    "title": "Proposed: A Potential Solution for V-Sekai’s Identifier Assignment Challenge",
+    "objectID": "decisions/20230626-godot-vrm1-addon.html#proposed-solution",
+    "href": "decisions/20230626-godot-vrm1-addon.html#proposed-solution",
+    "title": "Proposed: Ship Godot Engine VRM1 to solve portable humanoid avatars",
     "section": "",
-    "text": "V-Sekai\nGithub\nZenodo\nhttps://github.com/GlobalEcologyFlinders/assignDOI"
+    "text": "Ship Godot Engine VRM1 to Godot Engine asset Library."
   },
   {
-    "objectID": "decisions/20240709-anwave-set-nvidia-watt-limit.html",
-    "href": "decisions/20240709-anwave-set-nvidia-watt-limit.html",
-    "title": "Proposed: Set Nvidia Watt Limit with Anwave",
+    "objectID": "decisions/20230626-godot-vrm1-addon.html#implementation",
+    "href": "decisions/20230626-godot-vrm1-addon.html#implementation",
+    "title": "Proposed: Ship Godot Engine VRM1 to solve portable humanoid avatars",
     "section": "",
-    "text": "Users have reported issues with their PCs overheating, particularly during the summer months. This problem is exacerbated for those using high-performance GPUs on Windows 11 and using PC virtual reality apps like VRChat.\n\n\n\nOn Windows 11, my PC was overheating in the summer heat.\n\n\n\nTo mitigate the overheating issue, we propose using Anwave to power limit the GPU to 140 watts. This can be achieved by configuring the power management settings of the GPU.\n\nOpen Anwave application.\nNavigate to the power management section.\nSet the power limit of the GPU to 140 watts.\nApply the changes and monitor the GPU temperature.\n\n\n\n\n\nReduced Overheating: By limiting the power consumption of the GPU, the overall heat generated will be reduced.\nImproved Stability: Lower temperatures can lead to more stable system performance.\nExtended Hardware Lifespan: Reducing thermal stress can prolong the life of the GPU and other components.\n\n\n\n\n\nPerformance Impact: Limiting the power may reduce the performance of the GPU, affecting tasks that require high computational power.\nComplexity: Users need to be familiar with tools like Anwave and comfortable making changes to power settings.\n\n\n\n\nAlternative solutions such as improving cooling systems (e.g., adding more fans or using liquid cooling) were considered but deemed more costly and complex compared to software-based power management.\n\n\n\nThis solution might not be necessary for users in cooler climates or those who do not push their GPUs to high performance levels.\n\n\n\nThe implementation of this proposal will be handled internally by the V-Sekai development team, ensuring compatibility and stability with our existing systems.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nnvidia-power-management-power-control\n\nAI assistant Aria assisted with this article."
+    "text": "Implement basic humanoid avatar functionality such as rigging, animation, and basic physics through VRM1 spring bones.\nImplement support for both MToon1 and MToon0 materials, which provide a physically-based rendering approach for anime-style graphics.\nImplement support for the glTF PBR material type, which provides a more physically-based rendering approach for realistic graphics.\nImplement facial expressions, eye tracking, and lip syncing for a more immersive experience.\nImplement export by copying the import code in reverse, and refine it over time.\nUse the VRM spec’s suggested algorithm for implementing first-person view, which eliminates the need for head scaling.\nPrioritize necessary features and say no to suggestions that are not necessary to avoid feature bloat.\nDo not implement AnimationTree for this proposal."
   },
   {
-    "objectID": "decisions/20240709-anwave-set-nvidia-watt-limit.html#the-context",
-    "href": "decisions/20240709-anwave-set-nvidia-watt-limit.html#the-context",
-    "title": "Proposed: Set Nvidia Watt Limit with Anwave",
+    "objectID": "decisions/20230626-godot-vrm1-addon.html#positive-consequences",
+    "href": "decisions/20230626-godot-vrm1-addon.html#positive-consequences",
+    "title": "Proposed: Ship Godot Engine VRM1 to solve portable humanoid avatars",
     "section": "",
-    "text": "Users have reported issues with their PCs overheating, particularly during the summer months. This problem is exacerbated for those using high-performance GPUs on Windows 11 and using PC virtual reality apps like VRChat."
+    "text": "Portable humanoid avatars can be easily created and used in Godot Engine projects.\nThe addition of MToon1 material support provides a physically-based rendering approach for anime-style graphics.\nFacial expressions, eye tracking, and lip syncing enhance the immersive experience for users.\nExport functionality allows for easy sharing of avatars between projects and with other users.\nThe use of the VRM spec’s suggested algorithm for implementing first-person view simplifies the implementation process."
   },
   {
-    "objectID": "decisions/20240709-anwave-set-nvidia-watt-limit.html#the-problem-statement",
-    "href": "decisions/20240709-anwave-set-nvidia-watt-limit.html#the-problem-statement",
-    "title": "Proposed: Set Nvidia Watt Limit with Anwave",
+    "objectID": "decisions/20230626-godot-vrm1-addon.html#negative-consequences",
+    "href": "decisions/20230626-godot-vrm1-addon.html#negative-consequences",
+    "title": "Proposed: Ship Godot Engine VRM1 to solve portable humanoid avatars",
     "section": "",
-    "text": "On Windows 11, my PC was overheating in the summer heat."
+    "text": "The implementation of these features may require additional development time and resources.\nThe addition of new features may increase the complexity of the codebase and require additional maintenance.\nThe use of the MToon1 material may require additional GPU resources and may not be suitable for low-end hardware.\nThe implementation of facial expressions, eye tracking, and lip syncing may require additional hardware or software support."
   },
   {
-    "objectID": "decisions/20240709-anwave-set-nvidia-watt-limit.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240709-anwave-set-nvidia-watt-limit.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Set Nvidia Watt Limit with Anwave",
+    "objectID": "decisions/20230626-godot-vrm1-addon.html#option-graveyard",
+    "href": "decisions/20230626-godot-vrm1-addon.html#option-graveyard",
+    "title": "Proposed: Ship Godot Engine VRM1 to solve portable humanoid avatars",
     "section": "",
-    "text": "To mitigate the overheating issue, we propose using Anwave to power limit the GPU to 140 watts. This can be achieved by configuring the power management settings of the GPU.\n\nOpen Anwave application.\nNavigate to the power management section.\nSet the power limit of the GPU to 140 watts.\nApply the changes and monitor the GPU temperature."
+    "text": "We are not implementing support for other material types beyond MToon0, MToon1 and gltf PBR, which could limit the range of visual styles that can be achieved with Godot Engine."
   },
   {
-    "objectID": "decisions/20240709-anwave-set-nvidia-watt-limit.html#the-benefits",
-    "href": "decisions/20240709-anwave-set-nvidia-watt-limit.html#the-benefits",
-    "title": "Proposed: Set Nvidia Watt Limit with Anwave",
+    "objectID": "decisions/20230626-godot-vrm1-addon.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230626-godot-vrm1-addon.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Ship Godot Engine VRM1 to solve portable humanoid avatars",
     "section": "",
-    "text": "Reduced Overheating: By limiting the power consumption of the GPU, the overall heat generated will be reduced.\nImproved Stability: Lower temperatures can lead to more stable system performance.\nExtended Hardware Lifespan: Reducing thermal stress can prolong the life of the GPU and other components."
+    "text": "It is unlikely that these enhancements can be easily worked around with a few lines of script, as they require significant development effort and integration with the Godot Engine codebase."
   },
   {
-    "objectID": "decisions/20240709-anwave-set-nvidia-watt-limit.html#the-downsides",
-    "href": "decisions/20240709-anwave-set-nvidia-watt-limit.html#the-downsides",
-    "title": "Proposed: Set Nvidia Watt Limit with Anwave",
+    "objectID": "decisions/20230626-godot-vrm1-addon.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230626-godot-vrm1-addon.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Ship Godot Engine VRM1 to solve portable humanoid avatars",
     "section": "",
-    "text": "Performance Impact: Limiting the power may reduce the performance of the GPU, affecting tasks that require high computational power.\nComplexity: Users need to be familiar with tools like Anwave and comfortable making changes to power settings."
+    "text": "Portable humanoid avatars are a key feature for many Godot Engine projects, and the ability to easily create and use them is important for the success of the engine.\nThe addition of MToon1 material support and other enhancements will improve the quality and visual fidelity of Godot Engine projects.\nBy implementing these features in-house, we can ensure that they are well-integrated with the Godot Engine codebase and meet our quality standards."
   },
   {
-    "objectID": "decisions/20240709-anwave-set-nvidia-watt-limit.html#the-road-not-taken",
-    "href": "decisions/20240709-anwave-set-nvidia-watt-limit.html#the-road-not-taken",
-    "title": "Proposed: Set Nvidia Watt Limit with Anwave",
+    "objectID": "decisions/20230626-godot-vrm1-addon.html#references",
+    "href": "decisions/20230626-godot-vrm1-addon.html#references",
+    "title": "Proposed: Ship Godot Engine VRM1 to solve portable humanoid avatars",
     "section": "",
-    "text": "Alternative solutions such as improving cooling systems (e.g., adding more fans or using liquid cooling) were considered but deemed more costly and complex compared to software-based power management."
+    "text": "V-Sekai\nhttps://github.com/vrm-c/vrm-specification\nhttps://github.com/vrm-c/vrm-specification/blob/master/specification/VRMC_vrm-1.0/firstPerson.md#meshannotationauto-algorithm"
   },
   {
-    "objectID": "decisions/20240709-anwave-set-nvidia-watt-limit.html#the-infrequent-use-case",
-    "href": "decisions/20240709-anwave-set-nvidia-watt-limit.html#the-infrequent-use-case",
-    "title": "Proposed: Set Nvidia Watt Limit with Anwave",
+    "objectID": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html",
+    "href": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html",
+    "title": "Accepted: Rank skeleton #bone names with catboost",
     "section": "",
-    "text": "This solution might not be necessary for users in cooler climates or those who do not push their GPUs to high performance levels."
+    "text": "Status: accepted \n\n\n\nImprove automatic #bone selection\n\n\n\nUse catboost to rank bones.\n\nCompile catboost as a library\nya make -r catboost/libs/model_interface/static\n\n\n\n\n\nInstall catboost\nGenerate training data.\nMapping to #bone names, attributes and categories.\nUse a training app create test data.\nGenerate train and test datasets for T-Posed character surfaces\nExample: CSV.\nLabel,Feature: #bone X global location in meters,Feature: #bone Y global location in meters,Feature: #bone Z global location in meters,Feature: #bone truncated normalized basis axis x 0,Feature: #bone truncated normalized basis axis x 1,Feature: #bone truncated normalized basis axis x 2,Feature: #bone truncated normalized basis axis y 0,Feature: #bone truncated normalized basis axis y 1,Feature: #bone truncated normalized basis axis y 2,Feature: #bone X global scale in meters,Feature: #bone Y global scale in meters,Feature: #bone Z global scale in meters,Feature: #bone Parent X global location in meters,Feature: #bone Parent Y global location in meters,Feature: #bone Parent Z global location in meters,Feature: #bone Parent truncated normalized basis axis x 0,Feature: #bone Parent truncated normalized basis axis x 1,Feature: #bone Parent truncated normalized basis axis x 2,Feature: #bone Parent truncated normalized basis axis y 0,Feature: #bone Parent truncated normalized basis axis y 1,Feature: #bone Parent truncated normalized basis axis y 2,Feature: #bone Parent X global scale in meters,Feature: #bone Parent Y global scale in meters,Feature: #bone Parent Z global scale in meters,Feature: Masculine (-1.0) and feminine (1.0),Feature: Body mass in kilograms,Feature: Head circumference in meters,Feature: Neckline circumference in meters,Feature: Left Shoulder circumference in meters,Feature: Right Shoulder circumference in meters,Feature: Left Elbow circumference in meters,Feature: Right Elbow circumference in meters,Feature: Left wrist circumference in meters,Feature: Right wrist circumference in meters,Feature: Waist circumference in meters,Feature: Left thigh circumference in meters,Feature: Right thigh circumference in meters,Feature: Left ankle circumference in meters,Feature: Right ankle circumference in meters,Feature: Animation Time,Category: Corresponding VRM Bone,Category: Title,Category: Author,Category: Specification Version,Category: Animation 1,0,0,0,1,0,0,0,1,0,1,1,1,0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,,AvatarSample_A,VRoid,,T-Pose\nA missing value means the field is empty.\nTrain.\nTest.\nUse on cpu and in Godot Engine.\nProbability of a click.\n\n\n\n\n\nWe can guess the proper name.\nUseful for the facial mapping problem?\nUseful for the character generator slider recommendation problem?\nGenerate test data by moving the character\nInference requires only single pose inputs.\n\n\n\n\n\nStarring at the abyss.\nNeeds to be have a smaller library size. Not almost 200 mb.\n\n\n\n\n\nOption:\n\nbpr from Quora\n\nRejection Reason:\n\nBpr from Quora is not used in production.\n\nOption:\n\ndlrm from facebook\n\nRejection Reason:\n\nToo difficult to run\n\n\n\n\n\nNot a few lines of code.\n\n\n\nWe need this to make the quality of life of creators better.\n\n\n\n\nhttps://github.com/facebookresearch/dlrm\nhttps://medium.com/@marthawhite_81346/learning-with-the-criteo-tb-dataset-e3ec12d9d77e\nhttps://www.kaggle.com/c/criteo-display-ad-challenge/data\nSkeleton pool operator from neural blend shapes.\nhttps://tailor.fandom.com/wiki/Types_of_measurement\nhttps://knarkowicz.wordpress.com/2014/04/16/octahedron-normal-vector-encoding/\nhttps://www.kaggle.com/egordm/deep-learning-recommendation-model-dlrm\n\n    @article{li2021learning,\n    author = {Li, Peizhuo and Aberman, Kfir and Hanocka, Rana and Liu, Libin and Sorkine-Hornung, Olga and Chen, Baoquan},\n    title = {Learning Skeletal Articulations with Neural Blend Shapes},\n    journal = {ACM Transactions on Graphics (TOG)},\n    volume = {40},\n    number = {4},\n    pages = {1},\n    year = {2021},\n    publisher = {ACM}\n    }\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.\n\n\n\n\nSupersedes 20211031-use-bpr-to-rank-skeleton-bone-names"
   },
   {
-    "objectID": "decisions/20240709-anwave-set-nvidia-watt-limit.html#in-core-and-done-by-us",
-    "href": "decisions/20240709-anwave-set-nvidia-watt-limit.html#in-core-and-done-by-us",
-    "title": "Proposed: Set Nvidia Watt Limit with Anwave",
+    "objectID": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#context-and-problem-statement",
+    "href": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#context-and-problem-statement",
+    "title": "Accepted: Rank skeleton #bone names with catboost",
     "section": "",
-    "text": "The implementation of this proposal will be handled internally by the V-Sekai development team, ensuring compatibility and stability with our existing systems."
+    "text": "Improve automatic #bone selection"
   },
   {
-    "objectID": "decisions/20240709-anwave-set-nvidia-watt-limit.html#status",
-    "href": "decisions/20240709-anwave-set-nvidia-watt-limit.html#status",
-    "title": "Proposed: Set Nvidia Watt Limit with Anwave",
+    "objectID": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Accepted: Rank skeleton #bone names with catboost",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "Use catboost to rank bones.\n\nCompile catboost as a library\nya make -r catboost/libs/model_interface/static"
   },
   {
-    "objectID": "decisions/20240709-anwave-set-nvidia-watt-limit.html#decision-makers",
-    "href": "decisions/20240709-anwave-set-nvidia-watt-limit.html#decision-makers",
-    "title": "Proposed: Set Nvidia Watt Limit with Anwave",
+    "objectID": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Accepted: Rank skeleton #bone names with catboost",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "Install catboost\nGenerate training data.\nMapping to #bone names, attributes and categories.\nUse a training app create test data.\nGenerate train and test datasets for T-Posed character surfaces\nExample: CSV.\nLabel,Feature: #bone X global location in meters,Feature: #bone Y global location in meters,Feature: #bone Z global location in meters,Feature: #bone truncated normalized basis axis x 0,Feature: #bone truncated normalized basis axis x 1,Feature: #bone truncated normalized basis axis x 2,Feature: #bone truncated normalized basis axis y 0,Feature: #bone truncated normalized basis axis y 1,Feature: #bone truncated normalized basis axis y 2,Feature: #bone X global scale in meters,Feature: #bone Y global scale in meters,Feature: #bone Z global scale in meters,Feature: #bone Parent X global location in meters,Feature: #bone Parent Y global location in meters,Feature: #bone Parent Z global location in meters,Feature: #bone Parent truncated normalized basis axis x 0,Feature: #bone Parent truncated normalized basis axis x 1,Feature: #bone Parent truncated normalized basis axis x 2,Feature: #bone Parent truncated normalized basis axis y 0,Feature: #bone Parent truncated normalized basis axis y 1,Feature: #bone Parent truncated normalized basis axis y 2,Feature: #bone Parent X global scale in meters,Feature: #bone Parent Y global scale in meters,Feature: #bone Parent Z global scale in meters,Feature: Masculine (-1.0) and feminine (1.0),Feature: Body mass in kilograms,Feature: Head circumference in meters,Feature: Neckline circumference in meters,Feature: Left Shoulder circumference in meters,Feature: Right Shoulder circumference in meters,Feature: Left Elbow circumference in meters,Feature: Right Elbow circumference in meters,Feature: Left wrist circumference in meters,Feature: Right wrist circumference in meters,Feature: Waist circumference in meters,Feature: Left thigh circumference in meters,Feature: Right thigh circumference in meters,Feature: Left ankle circumference in meters,Feature: Right ankle circumference in meters,Feature: Animation Time,Category: Corresponding VRM Bone,Category: Title,Category: Author,Category: Specification Version,Category: Animation 1,0,0,0,1,0,0,0,1,0,1,1,1,0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,,AvatarSample_A,VRoid,,T-Pose\nA missing value means the field is empty.\nTrain.\nTest.\nUse on cpu and in Godot Engine.\nProbability of a click."
   },
   {
-    "objectID": "decisions/20240709-anwave-set-nvidia-watt-limit.html#tags",
-    "href": "decisions/20240709-anwave-set-nvidia-watt-limit.html#tags",
-    "title": "Proposed: Set Nvidia Watt Limit with Anwave",
+    "objectID": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#positive-consequences",
+    "href": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#positive-consequences",
+    "title": "Accepted: Rank skeleton #bone names with catboost",
     "section": "",
-    "text": "V-Sekai"
+    "text": "We can guess the proper name.\nUseful for the facial mapping problem?\nUseful for the character generator slider recommendation problem?\nGenerate test data by moving the character\nInference requires only single pose inputs."
   },
   {
-    "objectID": "decisions/20240709-anwave-set-nvidia-watt-limit.html#further-reading",
-    "href": "decisions/20240709-anwave-set-nvidia-watt-limit.html#further-reading",
-    "title": "Proposed: Set Nvidia Watt Limit with Anwave",
+    "objectID": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#negative-consequences",
+    "href": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#negative-consequences",
+    "title": "Accepted: Rank skeleton #bone names with catboost",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nnvidia-power-management-power-control\n\nAI assistant Aria assisted with this article."
+    "text": "Starring at the abyss.\nNeeds to be have a smaller library size. Not almost 200 mb."
   },
   {
-    "objectID": "decisions/20230123-face-helmet-capture.html",
-    "href": "decisions/20230123-face-helmet-capture.html",
-    "title": "Proposed: Face helmet capture",
+    "objectID": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#option-graveyard",
+    "href": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#option-graveyard",
+    "title": "Accepted: Rank skeleton #bone names with catboost",
     "section": "",
-    "text": "Proposed: Face helmet capture\n\nContext and Problem Statement\nWith a face helmet we can capture the face movement reliably.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nWe don’t have a way to talk to v-sekai for capture.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\n\nRun the v-sekai app\nExport either VMC or Godot Networking protocol for facial tracking\nOpen question on how to have tracking.\n\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nOption graveyard\nNo response\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot a few lines of script.\n\n\nIs there a reason why this should be core and done by us?\nI have the raw materials to do this.\n\n\nReferences\n\nV-Sekai\n\n\n\nLicense of the contribution\nCopyright (c) 2022 K. S. Ernest (iFire) Lee Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Option:\n\nbpr from Quora\n\nRejection Reason:\n\nBpr from Quora is not used in production.\n\nOption:\n\ndlrm from facebook\n\nRejection Reason:\n\nToo difficult to run"
   },
   {
-    "objectID": "decisions/20231027-dreamcraft3d-workflow.html",
-    "href": "decisions/20231027-dreamcraft3d-workflow.html",
-    "title": "Proposed: DreamCraft3D - A Hierarchical 3D Content Generation Method",
+    "objectID": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Accepted: Rank skeleton #bone names with catboost",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai, fire, Joseph Cat\nTags: V-Sekai, VRM, Rigging, 3D Modeling, DreamCraft3D\n\n\n\n\nDreamCraft3D is a hierarchical 3D content generation method that produces high-fidelity and coherent 3D objects. It uses a 2D reference image to guide the stages of geometry sculpting and texture boosting.\n\n\n\nThe main challenge lies in addressing the consistency issue that existing works encounter. To sculpt geometries that render coherently, DreamCraft3D performs score distillation sampling via a view-dependent diffusion model.\n\n\n\nThe strategy for implementing DreamCraft3D involves several steps:\n\nUse DreamCraft3D to generate high-fidelity and coherent 3D objects from 2D concept art.\nUtilize existing projects like Mixamo or AccuRig for rigging models.\nIf the topology isn’t suitable for animation, employ tools such as Quadwild BIMDF or Exoside’s Quad Remesher to enhance it.\nCorrect bad rigs using delta mush with the help of the Corrective Smooth Baker addon for Blender.\nDevelop software to perform clothing simulation differentially, referring to V-Sekai’s Cloth Dynamics as a guide.\n\n\n\n\nDreamCraft3D, with its tailored 3D priors throughout the hierarchical generation, can generate coherent 3D objects with photorealistic renderings. This advances the state-of-the-art in 3D content generation.\n\n\n\nThe process of converting 2D concept art into a rigged 3D model can be complex and time-consuming. It also requires expertise in 3D modeling and rigging.\n\n\n\nAn alternative approach could have been to manually create and rig the 3D models. However, this would be even more time-consuming and require even more expertise.\n\n\n\nIf the feature is used infrequently, it may not justify the time and resources spent on developing it.\n\n\n\nThis project aligns with our core expertise in VR technologies and 3D modeling. Therefore, it can be done by us.\n\n\n\nFor further reading, please refer to:\n\nV-Sekai GitHub Repository\nDreamCraft3D Code\nAI assists this article."
+    "text": "Not a few lines of code."
   },
   {
-    "objectID": "decisions/20231027-dreamcraft3d-workflow.html#metadata",
-    "href": "decisions/20231027-dreamcraft3d-workflow.html#metadata",
-    "title": "Proposed: DreamCraft3D - A Hierarchical 3D Content Generation Method",
+    "objectID": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Accepted: Rank skeleton #bone names with catboost",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai, fire, Joseph Cat\nTags: V-Sekai, VRM, Rigging, 3D Modeling, DreamCraft3D"
+    "text": "We need this to make the quality of life of creators better."
   },
   {
-    "objectID": "decisions/20231027-dreamcraft3d-workflow.html#context",
-    "href": "decisions/20231027-dreamcraft3d-workflow.html#context",
-    "title": "Proposed: DreamCraft3D - A Hierarchical 3D Content Generation Method",
+    "objectID": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#references",
+    "href": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#references",
+    "title": "Accepted: Rank skeleton #bone names with catboost",
     "section": "",
-    "text": "DreamCraft3D is a hierarchical 3D content generation method that produces high-fidelity and coherent 3D objects. It uses a 2D reference image to guide the stages of geometry sculpting and texture boosting."
+    "text": "https://github.com/facebookresearch/dlrm\nhttps://medium.com/@marthawhite_81346/learning-with-the-criteo-tb-dataset-e3ec12d9d77e\nhttps://www.kaggle.com/c/criteo-display-ad-challenge/data\nSkeleton pool operator from neural blend shapes.\nhttps://tailor.fandom.com/wiki/Types_of_measurement\nhttps://knarkowicz.wordpress.com/2014/04/16/octahedron-normal-vector-encoding/\nhttps://www.kaggle.com/egordm/deep-learning-recommendation-model-dlrm\n\n    @article{li2021learning,\n    author = {Li, Peizhuo and Aberman, Kfir and Hanocka, Rana and Liu, Libin and Sorkine-Hornung, Olga and Chen, Baoquan},\n    title = {Learning Skeletal Articulations with Neural Blend Shapes},\n    journal = {ACM Transactions on Graphics (TOG)},\n    volume = {40},\n    number = {4},\n    pages = {1},\n    year = {2021},\n    publisher = {ACM}\n    }"
   },
   {
-    "objectID": "decisions/20231027-dreamcraft3d-workflow.html#problem",
-    "href": "decisions/20231027-dreamcraft3d-workflow.html#problem",
-    "title": "Proposed: DreamCraft3D - A Hierarchical 3D Content Generation Method",
+    "objectID": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#derivative-license",
+    "href": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#derivative-license",
+    "title": "Accepted: Rank skeleton #bone names with catboost",
     "section": "",
-    "text": "The main challenge lies in addressing the consistency issue that existing works encounter. To sculpt geometries that render coherently, DreamCraft3D performs score distillation sampling via a view-dependent diffusion model."
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20231027-dreamcraft3d-workflow.html#solution",
-    "href": "decisions/20231027-dreamcraft3d-workflow.html#solution",
-    "title": "Proposed: DreamCraft3D - A Hierarchical 3D Content Generation Method",
+    "objectID": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#links",
+    "href": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#links",
+    "title": "Accepted: Rank skeleton #bone names with catboost",
     "section": "",
-    "text": "The strategy for implementing DreamCraft3D involves several steps:\n\nUse DreamCraft3D to generate high-fidelity and coherent 3D objects from 2D concept art.\nUtilize existing projects like Mixamo or AccuRig for rigging models.\nIf the topology isn’t suitable for animation, employ tools such as Quadwild BIMDF or Exoside’s Quad Remesher to enhance it.\nCorrect bad rigs using delta mush with the help of the Corrective Smooth Baker addon for Blender.\nDevelop software to perform clothing simulation differentially, referring to V-Sekai’s Cloth Dynamics as a guide."
+    "text": "Supersedes 20211031-use-bpr-to-rank-skeleton-bone-names"
   },
   {
-    "objectID": "decisions/20231027-dreamcraft3d-workflow.html#pros",
-    "href": "decisions/20231027-dreamcraft3d-workflow.html#pros",
-    "title": "Proposed: DreamCraft3D - A Hierarchical 3D Content Generation Method",
+    "objectID": "decisions/20231108-v-sekai-chat-bot.html",
+    "href": "decisions/20231108-v-sekai-chat-bot.html",
+    "title": "Proposed: Creation of an ‘Ask V-Sekai’ Chatbot Using Vercel, OpenAI, and Neon PostgreSQL",
     "section": "",
-    "text": "DreamCraft3D, with its tailored 3D priors throughout the hierarchical generation, can generate coherent 3D objects with photorealistic renderings. This advances the state-of-the-art in 3D content generation."
+    "text": "Status: Proposed\nDeciders: V-Sekai Development Team\nTags: V-Sekai, Chatbot, Vercel, OpenAI, Neon, PostgreSQL, AI, Serverless\n\n\n\n\nV-Sekai aims to provide immediate, AI-driven answers to community queries using a chatbot integrated with Discord.\n\n\n\nHow to develop an ‘Ask V-Sekai’ chatbot that utilizes Vercel serverless functions for interaction, OpenAI for natural language understanding, and Neon PostgreSQL for storing and retrieving knowledge?\n\n\n\n\nDesign and deploy a serverless function on Vercel that interfaces with Discord to receive questions.\nUse OpenAI’s API to process natural language queries and generate responses.\nStore and retrieve chatbot training and interaction data using Neon’s PostgreSQL service, leveraging the pgvector extension for efficient similarity analysis.\nContinuously improve the chatbot’s accuracy and response quality through data analytics and model fine-tuning.\n\n\n\n\n\nQuick, accurate responses to user inquiries, enhancing the V-Sekai community experience.\nLeverage cutting-edge AI and serverless technologies for a scalable, low-overhead solution.\nGather valuable interaction data to refine the chatbot and community support strategies.\n\n\n\n\n\nInitial complexity in setting up the integration between Vercel, OpenAI, and Neon PostgreSQL.\nOngoing maintenance and potential costs associated with OpenAI API usage.\n\n\n\n\n\nTraditional FAQ systems that do not offer real-time, AI-driven interaction and learning capabilities.\n\n\n\n\n\nComplex queries that require human intervention and are not yet within the scope of the AI’s training.\n\n\n\n\n\nThe development, deployment, and maintenance of the ‘Ask V-Sekai’ chatbot will be managed internally as a strategic tool for community engagement.\n\n\n\n\n\nVercel Serverless Functions Documentation\nOpenAI API Documentation\nNeon Tech Blog on Building an AI ChatBot\nAsk Neon This strategy was formulated with AI assistance."
   },
   {
-    "objectID": "decisions/20231027-dreamcraft3d-workflow.html#cons",
-    "href": "decisions/20231027-dreamcraft3d-workflow.html#cons",
-    "title": "Proposed: DreamCraft3D - A Hierarchical 3D Content Generation Method",
+    "objectID": "decisions/20231108-v-sekai-chat-bot.html#metadata",
+    "href": "decisions/20231108-v-sekai-chat-bot.html#metadata",
+    "title": "Proposed: Creation of an ‘Ask V-Sekai’ Chatbot Using Vercel, OpenAI, and Neon PostgreSQL",
     "section": "",
-    "text": "The process of converting 2D concept art into a rigged 3D model can be complex and time-consuming. It also requires expertise in 3D modeling and rigging."
+    "text": "Status: Proposed\nDeciders: V-Sekai Development Team\nTags: V-Sekai, Chatbot, Vercel, OpenAI, Neon, PostgreSQL, AI, Serverless"
   },
   {
-    "objectID": "decisions/20231027-dreamcraft3d-workflow.html#alternatives",
-    "href": "decisions/20231027-dreamcraft3d-workflow.html#alternatives",
-    "title": "Proposed: DreamCraft3D - A Hierarchical 3D Content Generation Method",
+    "objectID": "decisions/20231108-v-sekai-chat-bot.html#the-backdrop",
+    "href": "decisions/20231108-v-sekai-chat-bot.html#the-backdrop",
+    "title": "Proposed: Creation of an ‘Ask V-Sekai’ Chatbot Using Vercel, OpenAI, and Neon PostgreSQL",
     "section": "",
-    "text": "An alternative approach could have been to manually create and rig the 3D models. However, this would be even more time-consuming and require even more expertise."
+    "text": "V-Sekai aims to provide immediate, AI-driven answers to community queries using a chatbot integrated with Discord."
   },
   {
-    "objectID": "decisions/20231027-dreamcraft3d-workflow.html#infrequent-use-case",
-    "href": "decisions/20231027-dreamcraft3d-workflow.html#infrequent-use-case",
-    "title": "Proposed: DreamCraft3D - A Hierarchical 3D Content Generation Method",
+    "objectID": "decisions/20231108-v-sekai-chat-bot.html#the-challenge",
+    "href": "decisions/20231108-v-sekai-chat-bot.html#the-challenge",
+    "title": "Proposed: Creation of an ‘Ask V-Sekai’ Chatbot Using Vercel, OpenAI, and Neon PostgreSQL",
     "section": "",
-    "text": "If the feature is used infrequently, it may not justify the time and resources spent on developing it."
+    "text": "How to develop an ‘Ask V-Sekai’ chatbot that utilizes Vercel serverless functions for interaction, OpenAI for natural language understanding, and Neon PostgreSQL for storing and retrieving knowledge?"
   },
   {
-    "objectID": "decisions/20231027-dreamcraft3d-workflow.html#ownership",
-    "href": "decisions/20231027-dreamcraft3d-workflow.html#ownership",
-    "title": "Proposed: DreamCraft3D - A Hierarchical 3D Content Generation Method",
+    "objectID": "decisions/20231108-v-sekai-chat-bot.html#the-strategy",
+    "href": "decisions/20231108-v-sekai-chat-bot.html#the-strategy",
+    "title": "Proposed: Creation of an ‘Ask V-Sekai’ Chatbot Using Vercel, OpenAI, and Neon PostgreSQL",
     "section": "",
-    "text": "This project aligns with our core expertise in VR technologies and 3D modeling. Therefore, it can be done by us."
+    "text": "Design and deploy a serverless function on Vercel that interfaces with Discord to receive questions.\nUse OpenAI’s API to process natural language queries and generate responses.\nStore and retrieve chatbot training and interaction data using Neon’s PostgreSQL service, leveraging the pgvector extension for efficient similarity analysis.\nContinuously improve the chatbot’s accuracy and response quality through data analytics and model fine-tuning."
   },
   {
-    "objectID": "decisions/20231027-dreamcraft3d-workflow.html#references",
-    "href": "decisions/20231027-dreamcraft3d-workflow.html#references",
-    "title": "Proposed: DreamCraft3D - A Hierarchical 3D Content Generation Method",
+    "objectID": "decisions/20231108-v-sekai-chat-bot.html#the-upside",
+    "href": "decisions/20231108-v-sekai-chat-bot.html#the-upside",
+    "title": "Proposed: Creation of an ‘Ask V-Sekai’ Chatbot Using Vercel, OpenAI, and Neon PostgreSQL",
     "section": "",
-    "text": "For further reading, please refer to:\n\nV-Sekai GitHub Repository\nDreamCraft3D Code\nAI assists this article."
+    "text": "Quick, accurate responses to user inquiries, enhancing the V-Sekai community experience.\nLeverage cutting-edge AI and serverless technologies for a scalable, low-overhead solution.\nGather valuable interaction data to refine the chatbot and community support strategies."
   },
   {
-    "objectID": "decisions/20230106-walking-controller-renik.html",
-    "href": "decisions/20230106-walking-controller-renik.html",
-    "title": "Accepted: Separate walking controller from RenIK for ManyBoneIK",
+    "objectID": "decisions/20231108-v-sekai-chat-bot.html#the-downside",
+    "href": "decisions/20231108-v-sekai-chat-bot.html#the-downside",
+    "title": "Proposed: Creation of an ‘Ask V-Sekai’ Chatbot Using Vercel, OpenAI, and Neon PostgreSQL",
     "section": "",
-    "text": "Status: accepted \nDeciders: V-Sekai,fire,lyuma,\nTags: V-Sekai,\n\n\n\nTo be able to implement ManyBoneIk we need to extract the walking controller from RenIK.\n\n\n\nExtract the walking controller into like a gdscript.\n\n\n\nSplit the tracker IKPoints from the controller.\n\n\n\nWe can migrate to many bone ik.\n\n\n\nConversion to gdscript may be slower.\n\n\n\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\n\nIt is a few lines of script.\n\n\n\nWe manage the avatar experience.\n\n\n\n\nV-Sekai\n\n\n\n\nMIT License\n\nCopyright (c) 2018-2022 SaracenOne\nCopyright (c) 2019-2022 K. S. Ernest (iFire) Lee (fire)\nCopyright (c) 2020-2022 Lyuma\nCopyright (c) 2020-2022 MMMaellon\nCopyright (c) 2022 V-Sekai Contributors\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
+    "text": "Initial complexity in setting up the integration between Vercel, OpenAI, and Neon PostgreSQL.\nOngoing maintenance and potential costs associated with OpenAI API usage."
   },
   {
-    "objectID": "decisions/20230106-walking-controller-renik.html#context-and-problem-statement",
-    "href": "decisions/20230106-walking-controller-renik.html#context-and-problem-statement",
-    "title": "Accepted: Separate walking controller from RenIK for ManyBoneIK",
+    "objectID": "decisions/20231108-v-sekai-chat-bot.html#the-road-not-taken",
+    "href": "decisions/20231108-v-sekai-chat-bot.html#the-road-not-taken",
+    "title": "Proposed: Creation of an ‘Ask V-Sekai’ Chatbot Using Vercel, OpenAI, and Neon PostgreSQL",
     "section": "",
-    "text": "To be able to implement ManyBoneIk we need to extract the walking controller from RenIK."
+    "text": "Traditional FAQ systems that do not offer real-time, AI-driven interaction and learning capabilities."
   },
   {
-    "objectID": "decisions/20230106-walking-controller-renik.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20230106-walking-controller-renik.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Accepted: Separate walking controller from RenIK for ManyBoneIK",
+    "objectID": "decisions/20231108-v-sekai-chat-bot.html#the-infrequent-use-case",
+    "href": "decisions/20231108-v-sekai-chat-bot.html#the-infrequent-use-case",
+    "title": "Proposed: Creation of an ‘Ask V-Sekai’ Chatbot Using Vercel, OpenAI, and Neon PostgreSQL",
     "section": "",
-    "text": "Extract the walking controller into like a gdscript."
+    "text": "Complex queries that require human intervention and are not yet within the scope of the AI’s training."
   },
   {
-    "objectID": "decisions/20230106-walking-controller-renik.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20230106-walking-controller-renik.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Accepted: Separate walking controller from RenIK for ManyBoneIK",
+    "objectID": "decisions/20231108-v-sekai-chat-bot.html#in-core-and-done-by-us",
+    "href": "decisions/20231108-v-sekai-chat-bot.html#in-core-and-done-by-us",
+    "title": "Proposed: Creation of an ‘Ask V-Sekai’ Chatbot Using Vercel, OpenAI, and Neon PostgreSQL",
     "section": "",
-    "text": "Split the tracker IKPoints from the controller."
+    "text": "The development, deployment, and maintenance of the ‘Ask V-Sekai’ chatbot will be managed internally as a strategic tool for community engagement."
   },
   {
-    "objectID": "decisions/20230106-walking-controller-renik.html#positive-consequences",
-    "href": "decisions/20230106-walking-controller-renik.html#positive-consequences",
-    "title": "Accepted: Separate walking controller from RenIK for ManyBoneIK",
+    "objectID": "decisions/20231108-v-sekai-chat-bot.html#further-reading",
+    "href": "decisions/20231108-v-sekai-chat-bot.html#further-reading",
+    "title": "Proposed: Creation of an ‘Ask V-Sekai’ Chatbot Using Vercel, OpenAI, and Neon PostgreSQL",
     "section": "",
-    "text": "We can migrate to many bone ik."
+    "text": "Vercel Serverless Functions Documentation\nOpenAI API Documentation\nNeon Tech Blog on Building an AI ChatBot\nAsk Neon This strategy was formulated with AI assistance."
   },
   {
-    "objectID": "decisions/20230106-walking-controller-renik.html#negative-consequences",
-    "href": "decisions/20230106-walking-controller-renik.html#negative-consequences",
-    "title": "Accepted: Separate walking controller from RenIK for ManyBoneIK",
+    "objectID": "decisions/20211104-research-mesh-tooling-with-kaolin.html",
+    "href": "decisions/20211104-research-mesh-tooling-with-kaolin.html",
+    "title": "Draft: Research mesh tooling with kaolin",
     "section": "",
-    "text": "Conversion to gdscript may be slower."
+    "text": "Status: draft \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nNeed geometric tools for many things in the V-Sekai.\n[Describe the context and problem statement, e.g., in free form using two to three sentences. You may want to articulate the problem in the form of a question.]\n\n\n\nUse kaolin for some of the tools.\n\n\n\n\ngit clone https://github.com/NVIDIAGameWorks/kaolin.git\nInstall https://github.com/conda-forge/miniforge#mambaforge\nconda create --name kaolin python=3.9\nconda activate kaolin\nconda install pytorch torchvision torchaudio cudatoolkit=11.3 -c pytorch\npython setup.py develop\nTest the install. python -c \"import kaolin; print(kaolin.__version__)\"\n\n\n\nHi fire , thanks for your interest in Kaolin. Currently probably the best way to learn Kaolin is to take a look through the documentation and look for relevant functions. We hope to make more demos which will make learning Kaolin smoother in the future.\nThe functions which will be useful to you would be:\nkaolin.io.obj.import_mesh to import a mesh.\ntorch.meshgrid to generate a bunch of 3D coordinates of a voxel grid.\nkaolin.metrics.trianglemesh.point_to_mesh_distance to get the distance function for those points.\nkaolin.ops.mesh.check_sign to get the sign of the points to multiply with the distance.\nkaolin.ops.conversions.voxelgrids_to_trianglemeshes to convert the SDF grid to a mesh.\n\n\n\n\n\n[e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]\n\n\n\n\n\nMight require the GPU.\nInferencing may be difficult at interactive rates.\n\n\n\n\n\nOption: \nRejection Reason: \n\n\n\n\nCUDA, PyTorch and c++ are significant works.\n\n\n\nI have an approach!\n\n\n\n\nhttps://kaolin.readthedocs.io/en/latest/notes/installation.html\nhttps://www.alecjacobson.com/weblog/?tag=qslim\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230106-walking-controller-renik.html#option-graveyard",
-    "href": "decisions/20230106-walking-controller-renik.html#option-graveyard",
-    "title": "Accepted: Separate walking controller from RenIK for ManyBoneIK",
+    "objectID": "decisions/20211104-research-mesh-tooling-with-kaolin.html#context-and-problem-statement",
+    "href": "decisions/20211104-research-mesh-tooling-with-kaolin.html#context-and-problem-statement",
+    "title": "Draft: Research mesh tooling with kaolin",
     "section": "",
-    "text": "Option: The status quo. \nRejection Reason: This solves nothing."
+    "text": "Need geometric tools for many things in the V-Sekai.\n[Describe the context and problem statement, e.g., in free form using two to three sentences. You may want to articulate the problem in the form of a question.]"
   },
   {
-    "objectID": "decisions/20230106-walking-controller-renik.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230106-walking-controller-renik.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Accepted: Separate walking controller from RenIK for ManyBoneIK",
+    "objectID": "decisions/20211104-research-mesh-tooling-with-kaolin.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20211104-research-mesh-tooling-with-kaolin.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Draft: Research mesh tooling with kaolin",
     "section": "",
-    "text": "It is a few lines of script."
+    "text": "Use kaolin for some of the tools."
   },
   {
-    "objectID": "decisions/20230106-walking-controller-renik.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230106-walking-controller-renik.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Accepted: Separate walking controller from RenIK for ManyBoneIK",
+    "objectID": "decisions/20211104-research-mesh-tooling-with-kaolin.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20211104-research-mesh-tooling-with-kaolin.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Draft: Research mesh tooling with kaolin",
     "section": "",
-    "text": "We manage the avatar experience."
+    "text": "git clone https://github.com/NVIDIAGameWorks/kaolin.git\nInstall https://github.com/conda-forge/miniforge#mambaforge\nconda create --name kaolin python=3.9\nconda activate kaolin\nconda install pytorch torchvision torchaudio cudatoolkit=11.3 -c pytorch\npython setup.py develop\nTest the install. python -c \"import kaolin; print(kaolin.__version__)\"\n\n\n\nHi fire , thanks for your interest in Kaolin. Currently probably the best way to learn Kaolin is to take a look through the documentation and look for relevant functions. We hope to make more demos which will make learning Kaolin smoother in the future.\nThe functions which will be useful to you would be:\nkaolin.io.obj.import_mesh to import a mesh.\ntorch.meshgrid to generate a bunch of 3D coordinates of a voxel grid.\nkaolin.metrics.trianglemesh.point_to_mesh_distance to get the distance function for those points.\nkaolin.ops.mesh.check_sign to get the sign of the points to multiply with the distance.\nkaolin.ops.conversions.voxelgrids_to_trianglemeshes to convert the SDF grid to a mesh."
   },
   {
-    "objectID": "decisions/20230106-walking-controller-renik.html#references",
-    "href": "decisions/20230106-walking-controller-renik.html#references",
-    "title": "Accepted: Separate walking controller from RenIK for ManyBoneIK",
+    "objectID": "decisions/20211104-research-mesh-tooling-with-kaolin.html#positive-consequences",
+    "href": "decisions/20211104-research-mesh-tooling-with-kaolin.html#positive-consequences",
+    "title": "Draft: Research mesh tooling with kaolin",
     "section": "",
-    "text": "V-Sekai"
+    "text": "[e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]"
   },
   {
-    "objectID": "decisions/20230106-walking-controller-renik.html#license-of-the-contribution",
-    "href": "decisions/20230106-walking-controller-renik.html#license-of-the-contribution",
-    "title": "Accepted: Separate walking controller from RenIK for ManyBoneIK",
+    "objectID": "decisions/20211104-research-mesh-tooling-with-kaolin.html#negative-consequences",
+    "href": "decisions/20211104-research-mesh-tooling-with-kaolin.html#negative-consequences",
+    "title": "Draft: Research mesh tooling with kaolin",
     "section": "",
-    "text": "MIT License\n\nCopyright (c) 2018-2022 SaracenOne\nCopyright (c) 2019-2022 K. S. Ernest (iFire) Lee (fire)\nCopyright (c) 2020-2022 Lyuma\nCopyright (c) 2020-2022 MMMaellon\nCopyright (c) 2022 V-Sekai Contributors\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
+    "text": "Might require the GPU.\nInferencing may be difficult at interactive rates."
   },
   {
-    "objectID": "decisions/20230415-load-collaborate.html",
-    "href": "decisions/20230415-load-collaborate.html",
-    "title": "Proposed: Hit a collaborate button to load up into V-Sekai",
+    "objectID": "decisions/20211104-research-mesh-tooling-with-kaolin.html#option-graveyard",
+    "href": "decisions/20211104-research-mesh-tooling-with-kaolin.html#option-graveyard",
+    "title": "Draft: Research mesh tooling with kaolin",
     "section": "",
-    "text": "Proposed: Hit a collaborate button to load up into V-Sekai\n\nContext and Problem Statement\nLoad up into V-Sekai as a server and then they hit a collaborate button\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\n\nThe host player invites friends to their world\nThe friends’ clients will automatically connect to the caching solution\nThe host player has a valid V-Sekai map project on their computer that they load up into V-Sekai as a server\n\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nAdd mvsqlite+godot script to collaboration.\n\n\nPositive Consequences\nSummoning new friends and collaborators.\n\n\nNegative Consequences\nNo response\n\n\nOption graveyard\nNo response\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nThis is more of a user experience thing.\n\n\nIs there a reason why this should be core and done by us?\nWe are driving this.\n\n\nReferences\n\nV-Sekai\n\n\n\nLicense of the contribution\nCopyright (c) 2022 K. S. Ernest (iFire) Lee Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Option: \nRejection Reason:"
   },
   {
-    "objectID": "decisions/20230123-integrate-blender-with-gltf-extensions-and-godot.html",
-    "href": "decisions/20230123-integrate-blender-with-gltf-extensions-and-godot.html",
-    "title": "Proposed: Better Godot Engine integration with Blender with gltf extensions",
+    "objectID": "decisions/20211104-research-mesh-tooling-with-kaolin.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20211104-research-mesh-tooling-with-kaolin.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Draft: Research mesh tooling with kaolin",
     "section": "",
-    "text": "Proposed: Better Godot Engine integration with Blender with gltf extensions\n\nContext and Problem Statement\nIntegration between blender and Godot Engine could be better.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nThe import of Godot Shaders to Godot Engine can help developers and developer artists workflows.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nWrite a design for embed the Godot shader and material information in the exported GLTF as an extension, then parse it in the Godot importer\n\n\nPositive Consequences\nEasier to use Godot Engine\n\n\nNegative Consequences\nThe Godot Engine shader definition may change\n\n\nOption graveyard\nStatus quo.\nCan we do nothing?\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nThis is probably a folder of python scripts.\n\n\nIs there a reason why this should be core and done by us?\nWe manage the Godot Engine import experience.\n\n\nReferences\n\nV-Sekai\n\n\n\nLicense of the contribution\nCopyright (c) 2022-present K. S. Ernest (iFire) Lee Copyright (c) 2022-present V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "CUDA, PyTorch and c++ are significant works."
   },
   {
-    "objectID": "decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html",
-    "href": "decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html",
-    "title": "Accepted: For Godot Engine changes use a decision flowchart",
+    "objectID": "decisions/20211104-research-mesh-tooling-with-kaolin.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20211104-research-mesh-tooling-with-kaolin.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Draft: Research mesh tooling with kaolin",
     "section": "",
-    "text": "Status: accepted \nDeciders: V-Sekai,fire,lyuma,\nTags: V-Sekai,\n\n\n\nWe have conflicts on how to merge Godot. We need to organize our strategies.\n\n\n\nWe will write a decision flow chart on what to do.\n\n\n\nIs it upstreamable?\nIf upstreamable, commit to your own godot fork, and submit a Godot PR.\nThen, add this commit into the .gitassembly\nIf not upstreamable, and intended as a V-Sekai specific feature, make the commit in the V-Sekai godot fork, don’t submit a godot PR, and add to the .gitassembly.\nIf two upstreamable commits conflict, that is a godot problem because it implies the upstream open PRs would be broken if they both merged. There are two options:\nFirst, if the resolution to this merge conflict is itself something which must be upstreamed, a new PR should be opened or communication needs to happen between the PR maintainers.\nTemporarily, a new V-Sekai branch could be created which resolves this conflict while waiting for the upstream Godot maintainers to resolve the build issues.\nWorkflow for updating merge script.\n\nMake a local commit to merge-script-master\nRun the merge script\nIf successful, push (might happen automatically)\n\n\n\n\n\nEasier to remember solutions.\n\n\n\n\n\nLoss of flexibility.\n\n\n\n\n\nOption: Do adhoc decisions.\nRejection Reason: Not a better strategy.\n\n\n\n\nThis is a workflow design.\n\n\n\nOnly we care about our own policies.\n\n\n\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "I have an approach!"
   },
   {
-    "objectID": "decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html#context-and-problem-statement",
-    "href": "decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html#context-and-problem-statement",
-    "title": "Accepted: For Godot Engine changes use a decision flowchart",
+    "objectID": "decisions/20211104-research-mesh-tooling-with-kaolin.html#references",
+    "href": "decisions/20211104-research-mesh-tooling-with-kaolin.html#references",
+    "title": "Draft: Research mesh tooling with kaolin",
     "section": "",
-    "text": "We have conflicts on how to merge Godot. We need to organize our strategies."
+    "text": "https://kaolin.readthedocs.io/en/latest/notes/installation.html\nhttps://www.alecjacobson.com/weblog/?tag=qslim"
   },
   {
-    "objectID": "decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Accepted: For Godot Engine changes use a decision flowchart",
+    "objectID": "decisions/20211104-research-mesh-tooling-with-kaolin.html#derivative-license",
+    "href": "decisions/20211104-research-mesh-tooling-with-kaolin.html#derivative-license",
+    "title": "Draft: Research mesh tooling with kaolin",
     "section": "",
-    "text": "We will write a decision flow chart on what to do."
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Accepted: For Godot Engine changes use a decision flowchart",
+    "objectID": "decisions/20220916-too-many-branches-on-v-sekai-godot.html",
+    "href": "decisions/20220916-too-many-branches-on-v-sekai-godot.html",
+    "title": "Proposed: We have too many branches on V-Sekai/godot.",
     "section": "",
-    "text": "Is it upstreamable?\nIf upstreamable, commit to your own godot fork, and submit a Godot PR.\nThen, add this commit into the .gitassembly\nIf not upstreamable, and intended as a V-Sekai specific feature, make the commit in the V-Sekai godot fork, don’t submit a godot PR, and add to the .gitassembly.\nIf two upstreamable commits conflict, that is a godot problem because it implies the upstream open PRs would be broken if they both merged. There are two options:\nFirst, if the resolution to this merge conflict is itself something which must be upstreamed, a new PR should be opened or communication needs to happen between the PR maintainers.\nTemporarily, a new V-Sekai branch could be created which resolves this conflict while waiting for the upstream Godot maintainers to resolve the build issues.\nWorkflow for updating merge script.\n\nMake a local commit to merge-script-master\nRun the merge script\nIf successful, push (might happen automatically)"
+    "text": "Proposed: We have too many branches on V-Sekai/godot.\n\nContext and Problem Statement\nWe have too many branches on V-Sekai/godot.\nA lot of branches are already merged, some are godot 3.x, some were for old alphas.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nCreate a procedure for deleting branches.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nWe should be able to delete merged branches after we remove it from merge script or move the branches to an archive repo with all the PRs.\n&lt;lyuma&gt; It’s definitely ok to delete when godot merges . you can still get the commit hash by git log | grep v-sekai/branchname in godotengine/godot.\n\n\nPositive Consequences\nLess confusion.\n\n\nNegative Consequences\nAccidentally deleting a used branch.\n\n\nOption graveyard\nDo nothing.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot applicable.\n\n\nIs there a reason why this should be core and done by us?\nWe own the V-Sekai/godot repository.\n\n\nReferences\n\nV-Sekai\n\n\n\nLicense of the contribution\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html#positive-consequences",
-    "href": "decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html#positive-consequences",
-    "title": "Accepted: For Godot Engine changes use a decision flowchart",
+    "objectID": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html",
+    "href": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html",
+    "title": "Accepted: Create a Godot Engine asset store service on elixir and on sqlite.",
     "section": "",
-    "text": "Easier to remember solutions."
+    "text": "Status: accepted \nDeciders: V-Sekai,fire,\nTags: V-Sekai,\n\n\n\nGodot Engine lacks an asset store service.\n\n\n\nWrite an elixir service that stores data in a database.\n\n\n\nUse elixir.\nUse ecto with sqlite.\n\nUpgrade elixir-sqlite/exqlite to 3.37.0\nUpgrade elixir-sqlite/ecto_sqlite3 to support strict mode.\nPunt using elixir-sqlite/ecto_sqlite3\n\nUse ecto with cockroachdb.\n\nMake distribution of OSS cockroachdb for windows.\n\nConvert godot asset store api to an openapi schema.\n\nhttps://mermade.github.io/openapi-gui/\n\nProvide a phoenix web server.\nWorks on Windows.\nDesign a sqlite dataabase schema.\nInvestigate membrane framework.\n\n\n\n\nAble to publish v-sekai addons.\nOverlay existing asset library\nAble to in a future feature post process packed scenes exported by V-Selai\n\n\n\n\n\n[e.g., compromising quality attribute, follow-up decisions required, …]\n\n[this section can be repeated for each option if more than one option is open for consideration]\n\n\n\n\nOption: Use the existing asset library backend\nRejection Reason: Does not use a modern tech stack.\n\n\n\n\nDon’t need a line of script.\n\n\n\nThis is a V-Sekai service and I know of an approach.\n\n\n\n\nhttps://github.com/godotengine/godot-asset-library/blob/master/API.md\nhttps://godotengine.org/\nhttps://www.sqlite.org/draft/stricttables.html\nhttps://github.com/elixir-sqlite/ecto_sqlite3/issues\nhttps://www.phoenixframework.org/\nhttps://github.com/elixir-sqlite/exqlite/issues/175 Upgrade to Sqlite 3.37\n\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html#negative-consequences",
-    "href": "decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html#negative-consequences",
-    "title": "Accepted: For Godot Engine changes use a decision flowchart",
+    "objectID": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html#context-and-problem-statement",
+    "href": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html#context-and-problem-statement",
+    "title": "Accepted: Create a Godot Engine asset store service on elixir and on sqlite.",
     "section": "",
-    "text": "Loss of flexibility."
+    "text": "Godot Engine lacks an asset store service."
   },
   {
-    "objectID": "decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html#option-graveyard",
-    "href": "decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html#option-graveyard",
-    "title": "Accepted: For Godot Engine changes use a decision flowchart",
+    "objectID": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Accepted: Create a Godot Engine asset store service on elixir and on sqlite.",
     "section": "",
-    "text": "Option: Do adhoc decisions.\nRejection Reason: Not a better strategy."
+    "text": "Write an elixir service that stores data in a database."
   },
   {
-    "objectID": "decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Accepted: For Godot Engine changes use a decision flowchart",
+    "objectID": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Accepted: Create a Godot Engine asset store service on elixir and on sqlite.",
     "section": "",
-    "text": "This is a workflow design."
+    "text": "Use elixir.\nUse ecto with sqlite.\n\nUpgrade elixir-sqlite/exqlite to 3.37.0\nUpgrade elixir-sqlite/ecto_sqlite3 to support strict mode.\nPunt using elixir-sqlite/ecto_sqlite3\n\nUse ecto with cockroachdb.\n\nMake distribution of OSS cockroachdb for windows.\n\nConvert godot asset store api to an openapi schema.\n\nhttps://mermade.github.io/openapi-gui/\n\nProvide a phoenix web server.\nWorks on Windows.\nDesign a sqlite dataabase schema.\nInvestigate membrane framework."
   },
   {
-    "objectID": "decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Accepted: For Godot Engine changes use a decision flowchart",
+    "objectID": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html#positive-consequences",
+    "href": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html#positive-consequences",
+    "title": "Accepted: Create a Godot Engine asset store service on elixir and on sqlite.",
     "section": "",
-    "text": "Only we care about our own policies."
+    "text": "Able to publish v-sekai addons.\nOverlay existing asset library\nAble to in a future feature post process packed scenes exported by V-Selai"
   },
   {
-    "objectID": "decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html#derivative-license",
-    "href": "decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html#derivative-license",
-    "title": "Accepted: For Godot Engine changes use a decision flowchart",
+    "objectID": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html#negative-consequences",
+    "href": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html#negative-consequences",
+    "title": "Accepted: Create a Godot Engine asset store service on elixir and on sqlite.",
     "section": "",
-    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "[e.g., compromising quality attribute, follow-up decisions required, …]\n\n[this section can be repeated for each option if more than one option is open for consideration]"
   },
   {
-    "objectID": "decisions/20231027-write-a-list-of-github-pull-requests.html",
-    "href": "decisions/20231027-write-a-list-of-github-pull-requests.html",
-    "title": "Accepted: Write List of Github Pull Requests for Review",
+    "objectID": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html#option-graveyard",
+    "href": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html#option-graveyard",
+    "title": "Accepted: Create a Godot Engine asset store service on elixir and on sqlite.",
     "section": "",
-    "text": "Status: Accepted\nDeciders: V-Sekai, fire\nTags: V-Sekai, Elixir, GitHub API, Pull Requests\n\n\n\n\nThe objective is to fetch and compile a list of open pull requests from the Godot Engine repository on GitHub using Elixir.\n\n\n\nThe challenge lies in utilizing the GitHub GraphQL API to retrieve data about open pull requests in a specific milestone of the Godot Engine repository. This data should then be written to a text file for subsequent review.\n\n\n\nHere’s the proposed solution:\n\nUtilize the HTTPoison library to send a POST request to the GitHub GraphQL API.\nParse the response with the Jason library.\nWrite the relevant data to a text file using Elixir’s built-in File module.\n\n\n\n\nThis method allows us to fetch and store data about open pull requests in a structured and automated manner. It also facilitates offline review of this data or sharing it with others.\n\n\n\nWhile the script is designed to handle pagination and fetch all open pull requests, it may still encounter issues if the number of requests exceeds the rate limit set by GitHub’s API. In such cases, some data might not be fetched until the rate limit resets. Additionally, as the script fetches data in batches of 50, it could take a significant amount of time to fetch all data if there are hundreds or thousands of open pull requests.\n\n\n\nAn alternative approach could have been to use the GitHub REST API instead of the GraphQL API. However, the GraphQL API allows for more flexible and efficient data fetching.\n\n\n\nThis script might not be suitable if you need to fetch data about closed pull requests or pull requests in other repositories or milestones.\n\n\n\nYes, this is a core part of our development process and is done by us.\n\n\n\nFor more information, you can visit the following links:\n\nV-Sekai\nGitHub GraphQL API\nElixir HTTPoison Library\nElixir Jason Library\nAllourideas Wiki Survey\n\nThis article was assisted by AI."
+    "text": "Option: Use the existing asset library backend\nRejection Reason: Does not use a modern tech stack."
   },
   {
-    "objectID": "decisions/20231027-write-a-list-of-github-pull-requests.html#metadata",
-    "href": "decisions/20231027-write-a-list-of-github-pull-requests.html#metadata",
-    "title": "Accepted: Write List of Github Pull Requests for Review",
+    "objectID": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Accepted: Create a Godot Engine asset store service on elixir and on sqlite.",
     "section": "",
-    "text": "Status: Accepted\nDeciders: V-Sekai, fire\nTags: V-Sekai, Elixir, GitHub API, Pull Requests"
+    "text": "Don’t need a line of script."
   },
   {
-    "objectID": "decisions/20231027-write-a-list-of-github-pull-requests.html#context",
-    "href": "decisions/20231027-write-a-list-of-github-pull-requests.html#context",
-    "title": "Accepted: Write List of Github Pull Requests for Review",
+    "objectID": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Accepted: Create a Godot Engine asset store service on elixir and on sqlite.",
     "section": "",
-    "text": "The objective is to fetch and compile a list of open pull requests from the Godot Engine repository on GitHub using Elixir."
+    "text": "This is a V-Sekai service and I know of an approach."
   },
   {
-    "objectID": "decisions/20231027-write-a-list-of-github-pull-requests.html#problem",
-    "href": "decisions/20231027-write-a-list-of-github-pull-requests.html#problem",
-    "title": "Accepted: Write List of Github Pull Requests for Review",
+    "objectID": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html#references",
+    "href": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html#references",
+    "title": "Accepted: Create a Godot Engine asset store service on elixir and on sqlite.",
     "section": "",
-    "text": "The challenge lies in utilizing the GitHub GraphQL API to retrieve data about open pull requests in a specific milestone of the Godot Engine repository. This data should then be written to a text file for subsequent review."
+    "text": "https://github.com/godotengine/godot-asset-library/blob/master/API.md\nhttps://godotengine.org/\nhttps://www.sqlite.org/draft/stricttables.html\nhttps://github.com/elixir-sqlite/ecto_sqlite3/issues\nhttps://www.phoenixframework.org/\nhttps://github.com/elixir-sqlite/exqlite/issues/175 Upgrade to Sqlite 3.37"
   },
   {
-    "objectID": "decisions/20231027-write-a-list-of-github-pull-requests.html#solution",
-    "href": "decisions/20231027-write-a-list-of-github-pull-requests.html#solution",
-    "title": "Accepted: Write List of Github Pull Requests for Review",
+    "objectID": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html#derivative-license",
+    "href": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html#derivative-license",
+    "title": "Accepted: Create a Godot Engine asset store service on elixir and on sqlite.",
     "section": "",
-    "text": "Here’s the proposed solution:\n\nUtilize the HTTPoison library to send a POST request to the GitHub GraphQL API.\nParse the response with the Jason library.\nWrite the relevant data to a text file using Elixir’s built-in File module."
+    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20231027-write-a-list-of-github-pull-requests.html#advantages",
-    "href": "decisions/20231027-write-a-list-of-github-pull-requests.html#advantages",
-    "title": "Accepted: Write List of Github Pull Requests for Review",
+    "objectID": "decisions/20240613-1k-quad-limit.html",
+    "href": "decisions/20240613-1k-quad-limit.html",
+    "title": "Proposed: Training Mesh Transformer for 3D Avatar Creation",
     "section": "",
-    "text": "This method allows us to fetch and store data about open pull requests in a structured and automated manner. It also facilitates offline review of this data or sharing it with others."
+    "text": "We are working with mesh transformer large language models.\n\n\n\nThe goal is to train the mesh transformer to create 3D avatar characters. The challenge lies in managing the complexity of the model and the computational resources required for training.\n\n\n\nOur approach involves using quad support for the avatars, which allows us to cut the avatar into smaller objects as part of the body. This method is more manageable and efficient than trying to train the model on larger body parts or the entire avatar.\nHowever, it’s important to note that we cannot use triangles and quads at the same time. Also, having a context length of 32k or more will require a bigger model, which might not be feasible unless we have a substantial GPU budget for computation.\nFor our training data, we aim to keep the triangle count below 5k triangles. We also need to consider the shape of the training data and the type of quad data we need to provide.\nIn terms of numbers, we’re looking at around 1500 triangles, which would result in 6k to 9k tokens. If these triangles are converted to quads and there is a reduction, we could aim for around MAX 8k tokens. In this case, 1 triangle equals 6 tokens, and 1 quad equals 8 tokens.\nThis means that 8,000 tokens would equate to 1,000 quads.\n\n\n\n\nTraining the mesh transformer on smaller body parts will make it more manageable and efficient.\nUsing quads instead of triangles could potentially reduce the complexity of the model.\n\n\n\n\n\nThe process requires a significant amount of GPU compute power, which could be expensive.\nThe model might not be able to handle large context lengths effectively.\n\n\n\n\n\nWe could have chosen to train the model on larger body parts or the entire avatar, but this would require significantly more computational resources.\n\n\n\n\n\nThis approach may not be suitable for avatars with complex structures or high polygon counts.\n\n\n\n\n\nThe training of the mesh transformer will be done by us, using our acquired resources and expertise.\n\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\niFire\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20231027-write-a-list-of-github-pull-requests.html#disadvantages",
-    "href": "decisions/20231027-write-a-list-of-github-pull-requests.html#disadvantages",
-    "title": "Accepted: Write List of Github Pull Requests for Review",
+    "objectID": "decisions/20240613-1k-quad-limit.html#the-context",
+    "href": "decisions/20240613-1k-quad-limit.html#the-context",
+    "title": "Proposed: Training Mesh Transformer for 3D Avatar Creation",
     "section": "",
-    "text": "While the script is designed to handle pagination and fetch all open pull requests, it may still encounter issues if the number of requests exceeds the rate limit set by GitHub’s API. In such cases, some data might not be fetched until the rate limit resets. Additionally, as the script fetches data in batches of 50, it could take a significant amount of time to fetch all data if there are hundreds or thousands of open pull requests."
+    "text": "We are working with mesh transformer large language models."
   },
   {
-    "objectID": "decisions/20231027-write-a-list-of-github-pull-requests.html#alternatives",
-    "href": "decisions/20231027-write-a-list-of-github-pull-requests.html#alternatives",
-    "title": "Accepted: Write List of Github Pull Requests for Review",
+    "objectID": "decisions/20240613-1k-quad-limit.html#the-problem-statement",
+    "href": "decisions/20240613-1k-quad-limit.html#the-problem-statement",
+    "title": "Proposed: Training Mesh Transformer for 3D Avatar Creation",
     "section": "",
-    "text": "An alternative approach could have been to use the GitHub REST API instead of the GraphQL API. However, the GraphQL API allows for more flexible and efficient data fetching."
+    "text": "The goal is to train the mesh transformer to create 3D avatar characters. The challenge lies in managing the complexity of the model and the computational resources required for training."
   },
   {
-    "objectID": "decisions/20231027-write-a-list-of-github-pull-requests.html#limitations",
-    "href": "decisions/20231027-write-a-list-of-github-pull-requests.html#limitations",
-    "title": "Accepted: Write List of Github Pull Requests for Review",
+    "objectID": "decisions/20240613-1k-quad-limit.html#proposal",
+    "href": "decisions/20240613-1k-quad-limit.html#proposal",
+    "title": "Proposed: Training Mesh Transformer for 3D Avatar Creation",
     "section": "",
-    "text": "This script might not be suitable if you need to fetch data about closed pull requests or pull requests in other repositories or milestones."
+    "text": "Our approach involves using quad support for the avatars, which allows us to cut the avatar into smaller objects as part of the body. This method is more manageable and efficient than trying to train the model on larger body parts or the entire avatar.\nHowever, it’s important to note that we cannot use triangles and quads at the same time. Also, having a context length of 32k or more will require a bigger model, which might not be feasible unless we have a substantial GPU budget for computation.\nFor our training data, we aim to keep the triangle count below 5k triangles. We also need to consider the shape of the training data and the type of quad data we need to provide.\nIn terms of numbers, we’re looking at around 1500 triangles, which would result in 6k to 9k tokens. If these triangles are converted to quads and there is a reduction, we could aim for around MAX 8k tokens. In this case, 1 triangle equals 6 tokens, and 1 quad equals 8 tokens.\nThis means that 8,000 tokens would equate to 1,000 quads."
   },
   {
-    "objectID": "decisions/20231027-write-a-list-of-github-pull-requests.html#ownership",
-    "href": "decisions/20231027-write-a-list-of-github-pull-requests.html#ownership",
-    "title": "Accepted: Write List of Github Pull Requests for Review",
+    "objectID": "decisions/20240613-1k-quad-limit.html#the-benefits",
+    "href": "decisions/20240613-1k-quad-limit.html#the-benefits",
+    "title": "Proposed: Training Mesh Transformer for 3D Avatar Creation",
     "section": "",
-    "text": "Yes, this is a core part of our development process and is done by us."
+    "text": "Training the mesh transformer on smaller body parts will make it more manageable and efficient.\nUsing quads instead of triangles could potentially reduce the complexity of the model."
   },
   {
-    "objectID": "decisions/20231027-write-a-list-of-github-pull-requests.html#references",
-    "href": "decisions/20231027-write-a-list-of-github-pull-requests.html#references",
-    "title": "Accepted: Write List of Github Pull Requests for Review",
+    "objectID": "decisions/20240613-1k-quad-limit.html#the-downsides",
+    "href": "decisions/20240613-1k-quad-limit.html#the-downsides",
+    "title": "Proposed: Training Mesh Transformer for 3D Avatar Creation",
     "section": "",
-    "text": "For more information, you can visit the following links:\n\nV-Sekai\nGitHub GraphQL API\nElixir HTTPoison Library\nElixir Jason Library\nAllourideas Wiki Survey\n\nThis article was assisted by AI."
+    "text": "The process requires a significant amount of GPU compute power, which could be expensive.\nThe model might not be able to handle large context lengths effectively."
   },
   {
-    "objectID": "decisions/20231027-write-a-list-of-github-pull-requests.html#section",
-    "href": "decisions/20231027-write-a-list-of-github-pull-requests.html#section",
-    "title": "Accepted: Write List of Github Pull Requests for Review",
-    "section": "Section",
-    "text": "Section\ndefmodule PullRequestFetcher do\n  @query \"\"\"\n  {\n    repository(owner: \"godotengine\", name: \"godot\") {\n      milestone(number: 18) {\n        title\n        pullRequests(states: OPEN, first: 50) {\n          pageInfo {\n            endCursor\n            hasNextPage\n          }\n          nodes {\n            number\n            title\n            labels(first: 10) {\n              nodes {\n                name\n              }\n            }\n          }\n        }\n      }\n    }\n  }\n  \"\"\"\n\n  def fetch_and_write_pull_requests(query \\\\ @query, file \\\\ nil) do\n    file = if file, do: file, else: File.open!(\"pull_requests.txt\", [:write, :utf8])\n\n    {:ok, response} =\n      HTTPoison.post(\n        \"https://api.github.com/graphql\",\n        Jason.encode!(%{query: query}),\n        [\n          {\"Authorization\", \"Bearer #{System.fetch_env!(\"LB_GITHUB_TOKEN\")}\"},\n          {\"Content-Type\", \"application/json\"}\n        ],\n        timeout: 500_000,\n        reciv_timeout: 500_000\n      )\n\n    data = Jason.decode!(response.body)\n    pull_requests = data[\"data\"][\"repository\"][\"milestone\"][\"pullRequests\"]\n\n    for pull_request &lt;- pull_requests[\"nodes\"] do\n      labels = pull_request[\"labels\"][\"nodes\"] |&gt; Enum.map(& &1[\"name\"]) |&gt; Enum.join(\", \")\n      row = \"#{pull_request[\"title\"]} (##{pull_request[\"number\"]}) - Labels: [#{labels}]\"\n      IO.write(file, row &lt;&gt; \"\\n\")\n    end\n\n    if pull_requests[\"pageInfo\"][\"hasNextPage\"] do\n      next_query = \"\"\"\n      {\n        repository(owner: \"godotengine\", name: \"godot\") {\n          milestone(number: 18) {\n            title\n            pullRequests(states: OPEN, first: 50, after: \"#{pull_requests[\"pageInfo\"][\"endCursor\"]}\") {\n              pageInfo {\n                endCursor\n                hasNextPage\n              }\n              nodes {\n                number\n                title\n                labels(first: 10) {\n                  nodes {\n                    name\n                  }\n                }\n              }\n            }\n          }\n        }\n      }\n      \"\"\"\n\n      fetch_and_write_pull_requests(next_query, file)\n    else\n      :ok = File.close(file)\n    end\n  end\nend\n\nPullRequestFetcher.fetch_and_write_pull_requests()\n\n:ok"
+    "objectID": "decisions/20240613-1k-quad-limit.html#the-road-not-taken",
+    "href": "decisions/20240613-1k-quad-limit.html#the-road-not-taken",
+    "title": "Proposed: Training Mesh Transformer for 3D Avatar Creation",
+    "section": "",
+    "text": "We could have chosen to train the model on larger body parts or the entire avatar, but this would require significantly more computational resources."
   },
   {
-    "objectID": "decisions/20231027-apartment-building-vr.html",
-    "href": "decisions/20231027-apartment-building-vr.html",
-    "title": "Proposed: Build a Cozy Apartment in VR for V-Sekai",
+    "objectID": "decisions/20240613-1k-quad-limit.html#the-infrequent-use-case",
+    "href": "decisions/20240613-1k-quad-limit.html#the-infrequent-use-case",
+    "title": "Proposed: Training Mesh Transformer for 3D Avatar Creation",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai, fire\nTags: V-Sekai, VR, 3D Modeling, Virtual Reality\n\n\n\n\nVirtual Reality (VR) is a rapidly growing technology with applications in various fields. One such application is the creation of virtual environments, such as apartments. This proposal aims to outline a strategy for building a cozy apartment in VR as a default environment for V-Sekai.\n\n\n\nThe main challenge is to create a realistic and immersive virtual environment that accurately represents a cozy apartment. This includes creating detailed 3D models of the apartment’s interior and exterior, as well as implementing realistic lighting and textures.\n\n\n\n\nMake a rough SVG sketch of the floor plan from the top for each of the topographical levels.\nConvert SVG to geometry using a suitable software tool.\nUse basic shapes to extrude the walls, floors, and ceilings of the apartment.\nCheck human dimensions to ensure the scale of the apartment is accurate and realistic.\nRevise and refine the model in virtual reality.\n\n\n\n\nBuilding a cozy apartment in VR can provide a unique and immersive experience for users. It can also be used for various purposes such as virtual tours, real estate marketing, and interior design planning.\n\n\n\nThe process of building a detailed and realistic VR apartment can be time-consuming and requires expertise in 3D modeling and VR technologies. Additionally, users will need VR equipment to fully experience the virtual apartment.\n\n\n\nAn alternative approach could have been to use pre-made 3D models of apartments. However, this would limit the customization options and may not provide the same level of detail and realism.\n\n\n\nIn cases where the VR apartment is used infrequently, it may not justify the time and resources spent on building it.\n\n\n\nThis project aligns with our core expertise in VR technologies and 3D modeling. Therefore, it can be done by us.\n\n\n\n\nV-Sekai GitHub Repository\nAI assists this article."
+    "text": "This approach may not be suitable for avatars with complex structures or high polygon counts."
   },
   {
-    "objectID": "decisions/20231027-apartment-building-vr.html#metadata",
-    "href": "decisions/20231027-apartment-building-vr.html#metadata",
-    "title": "Proposed: Build a Cozy Apartment in VR for V-Sekai",
+    "objectID": "decisions/20240613-1k-quad-limit.html#in-core-and-done-by-us",
+    "href": "decisions/20240613-1k-quad-limit.html#in-core-and-done-by-us",
+    "title": "Proposed: Training Mesh Transformer for 3D Avatar Creation",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai, fire\nTags: V-Sekai, VR, 3D Modeling, Virtual Reality"
+    "text": "The training of the mesh transformer will be done by us, using our acquired resources and expertise."
   },
   {
-    "objectID": "decisions/20231027-apartment-building-vr.html#the-backdrop",
-    "href": "decisions/20231027-apartment-building-vr.html#the-backdrop",
-    "title": "Proposed: Build a Cozy Apartment in VR for V-Sekai",
+    "objectID": "decisions/20240613-1k-quad-limit.html#status",
+    "href": "decisions/20240613-1k-quad-limit.html#status",
+    "title": "Proposed: Training Mesh Transformer for 3D Avatar Creation",
     "section": "",
-    "text": "Virtual Reality (VR) is a rapidly growing technology with applications in various fields. One such application is the creation of virtual environments, such as apartments. This proposal aims to outline a strategy for building a cozy apartment in VR as a default environment for V-Sekai."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20231027-apartment-building-vr.html#the-challenge",
-    "href": "decisions/20231027-apartment-building-vr.html#the-challenge",
-    "title": "Proposed: Build a Cozy Apartment in VR for V-Sekai",
+    "objectID": "decisions/20240613-1k-quad-limit.html#decision-makers",
+    "href": "decisions/20240613-1k-quad-limit.html#decision-makers",
+    "title": "Proposed: Training Mesh Transformer for 3D Avatar Creation",
     "section": "",
-    "text": "The main challenge is to create a realistic and immersive virtual environment that accurately represents a cozy apartment. This includes creating detailed 3D models of the apartment’s interior and exterior, as well as implementing realistic lighting and textures."
+    "text": "V-Sekai development team\niFire"
   },
   {
-    "objectID": "decisions/20231027-apartment-building-vr.html#the-strategy",
-    "href": "decisions/20231027-apartment-building-vr.html#the-strategy",
-    "title": "Proposed: Build a Cozy Apartment in VR for V-Sekai",
+    "objectID": "decisions/20240613-1k-quad-limit.html#tags",
+    "href": "decisions/20240613-1k-quad-limit.html#tags",
+    "title": "Proposed: Training Mesh Transformer for 3D Avatar Creation",
     "section": "",
-    "text": "Make a rough SVG sketch of the floor plan from the top for each of the topographical levels.\nConvert SVG to geometry using a suitable software tool.\nUse basic shapes to extrude the walls, floors, and ceilings of the apartment.\nCheck human dimensions to ensure the scale of the apartment is accurate and realistic.\nRevise and refine the model in virtual reality."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20231027-apartment-building-vr.html#the-upside",
-    "href": "decisions/20231027-apartment-building-vr.html#the-upside",
-    "title": "Proposed: Build a Cozy Apartment in VR for V-Sekai",
+    "objectID": "decisions/20240613-1k-quad-limit.html#further-reading",
+    "href": "decisions/20240613-1k-quad-limit.html#further-reading",
+    "title": "Proposed: Training Mesh Transformer for 3D Avatar Creation",
     "section": "",
-    "text": "Building a cozy apartment in VR can provide a unique and immersive experience for users. It can also be used for various purposes such as virtual tours, real estate marketing, and interior design planning."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20231027-apartment-building-vr.html#the-downside",
-    "href": "decisions/20231027-apartment-building-vr.html#the-downside",
-    "title": "Proposed: Build a Cozy Apartment in VR for V-Sekai",
+    "objectID": "decisions/20230527-v-sekai-roadmap.html",
+    "href": "decisions/20230527-v-sekai-roadmap.html",
+    "title": "Superseded: V-Sekai Roadmap and Goals 2023-05-19",
     "section": "",
-    "text": "The process of building a detailed and realistic VR apartment can be time-consuming and requires expertise in 3D modeling and VR technologies. Additionally, users will need VR equipment to fully experience the virtual apartment."
+    "text": "Superseded: V-Sekai Roadmap and Goals 2023-05-19\n\nMetadata\n\nStatus: superseded by 20230602-v-sekai-roadmap.md \nDeciders: V-Sekai,fire,lyuma,\nTags: V-Sekai,chatgpt4 summary,\n\n\n\nContext and Problem Statement\nWhat is the V-Sekai Roadmap and Goals?\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nThe roadmap presented here is short-term.\n\n\nDescribe how your proposal will work with code, pseudo-code, mock-ups, or diagrams\ngraph LR\n  subgraph Short Term\n    A[May 27th, 2023] --&gt; D[Assist Godot Engine 4.1 features before May 30th feature freeze]\n    D --&gt; E[Vrm upload to the asset library after May 30th, 2023]\n    F --&gt; G[Unidot Unity Import upload to the asset library after May 30th, 2023]\n    G --&gt; H[Add jitter buffer to godot_speech]\n    H --&gt; I[Implement onevoip]\n  end\n\n\nPositive Consequences\nWe can create V-Sekai easier.\n\n\nNegative Consequences\nOverhead might be hard.\n\n\nOption graveyard\n\nImplementing a custom voice chat solution instead of using onevoip\nWaiting for Godot Engine 4.2 instead of assisting with 4.1 features\nIgnoring SkeletonIK3D issues and focusing on other aspects\n\n\n\nIf this enhancement will be used infrequently, can it be worked around with a few lines of script?\nNo. This is a process.\n\n\nIs there a reason why this should be core and done by us?\nThis is a core process for V-Sekai.\n\n\nReferences\n\nV-Sekai"
   },
   {
-    "objectID": "decisions/20231027-apartment-building-vr.html#the-road-not-taken",
-    "href": "decisions/20231027-apartment-building-vr.html#the-road-not-taken",
-    "title": "Proposed: Build a Cozy Apartment in VR for V-Sekai",
+    "objectID": "decisions/20240621-proposal-template copy.html",
+    "href": "decisions/20240621-proposal-template copy.html",
+    "title": "Proposed: Command Traces with Server Backend",
     "section": "",
-    "text": "An alternative approach could have been to use pre-made 3D models of apartments. However, this would limit the customization options and may not provide the same level of detail and realism."
+    "text": "Status: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20231027-apartment-building-vr.html#the-infrequent-use-case",
-    "href": "decisions/20231027-apartment-building-vr.html#the-infrequent-use-case",
-    "title": "Proposed: Build a Cozy Apartment in VR for V-Sekai",
+    "objectID": "decisions/20240621-proposal-template copy.html#status",
+    "href": "decisions/20240621-proposal-template copy.html#status",
+    "title": "Proposed: Command Traces with Server Backend",
     "section": "",
-    "text": "In cases where the VR apartment is used infrequently, it may not justify the time and resources spent on building it."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20231027-apartment-building-vr.html#in-core-and-done-by-us",
-    "href": "decisions/20231027-apartment-building-vr.html#in-core-and-done-by-us",
-    "title": "Proposed: Build a Cozy Apartment in VR for V-Sekai",
+    "objectID": "decisions/20240621-proposal-template copy.html#decision-makers",
+    "href": "decisions/20240621-proposal-template copy.html#decision-makers",
+    "title": "Proposed: Command Traces with Server Backend",
     "section": "",
-    "text": "This project aligns with our core expertise in VR technologies and 3D modeling. Therefore, it can be done by us."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20231027-apartment-building-vr.html#further-reading",
-    "href": "decisions/20231027-apartment-building-vr.html#further-reading",
-    "title": "Proposed: Build a Cozy Apartment in VR for V-Sekai",
+    "objectID": "decisions/20240621-proposal-template copy.html#tags",
+    "href": "decisions/20240621-proposal-template copy.html#tags",
+    "title": "Proposed: Command Traces with Server Backend",
     "section": "",
-    "text": "V-Sekai GitHub Repository\nAI assists this article."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20211031-create-a-demo-viewer-gallery.html",
-    "href": "decisions/20211031-create-a-demo-viewer-gallery.html",
-    "title": "Proposed: Create a demo viewer gallery",
+    "objectID": "decisions/20240621-proposal-template copy.html#further-reading",
+    "href": "decisions/20240621-proposal-template copy.html#further-reading",
+    "title": "Proposed: Command Traces with Server Backend",
     "section": "",
-    "text": "[Describe the problem or limitation you are having in your project]\n[Describe the context and problem statement, e.g., in free form using two to three sentences. You may want to articulate the problem in the form of a question.]\n\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\n\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\n\n\n\n\n[e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]\n[…]\n\n\n\n\n\n[e.g., compromising quality attribute, follow-up decisions required, …]\n[…]\n\n[this section can be repeated for each option if more than one option is open for consideration]\n\n\n\n\nOption: \nRejection Reason: \n\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\n\n\n\nIs there a reason why this should be core and done by us?\n\n\n\n\nLink type \n… \n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20211031-create-a-demo-viewer-gallery.html#context-and-problem-statement",
-    "href": "decisions/20211031-create-a-demo-viewer-gallery.html#context-and-problem-statement",
-    "title": "Proposed: Create a demo viewer gallery",
+    "objectID": "decisions/20230616-pmx-to-vrm.html",
+    "href": "decisions/20230616-pmx-to-vrm.html",
+    "title": "Proposed: V-Sekai Bone Hierarchy Conversion",
     "section": "",
-    "text": "[Describe the problem or limitation you are having in your project]\n[Describe the context and problem statement, e.g., in free form using two to three sentences. You may want to articulate the problem in the form of a question.]"
+    "text": "Status: proposed \nDeciders: V-Sekai, fire\nTags: V-Sekai, AI Assisted\n\n\n\n\nV-Sekai has a problem with its bone hierarchy conversion. This causes issues with Alicia’s hips-spine angle.\n\n\n\nWe suggest a new conversion method. It keeps the original bone hierarchy and translates bone names from Japanese to English. This avoids problems caused by changing the hierarchy.\n\n\n\n\nOriginal hierarchy (Japanese names):\nCenter (センター)\n├ UpperBody (上半身)\n└ LowerBody (下半身)\nNew method, same hierarchy, translated names:\nCenter (Hips)\n├ UpperBody (Spine)\n└ LowerBody (Legs)\nAfter the second conversion, the hierarchy changes:\nHips (LowerBody)\n└ Spine (UpperBody)\n\nThis solution keeps the right hips-spine angle for Alicia.\n\n\n\n\nKeeps the original bone hierarchy, avoiding animation issues.\nTranslates bone names to English, helping non-Japanese speakers.\n\n\n\n\n\nMight need more time to create the new method.\n\n\n\n\n\nChanging the hierarchy during conversion caused the problem.\n\n\n\n\nNo, this needs a new method in the bone hierarchy conversion process.\n\n\n\nYes, it affects character animations and user experience with V-Sekai models.\n\n\n\n\nV-Sekai"
   },
   {
-    "objectID": "decisions/20211031-create-a-demo-viewer-gallery.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20211031-create-a-demo-viewer-gallery.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: Create a demo viewer gallery",
+    "objectID": "decisions/20230616-pmx-to-vrm.html#metadata",
+    "href": "decisions/20230616-pmx-to-vrm.html#metadata",
+    "title": "Proposed: V-Sekai Bone Hierarchy Conversion",
     "section": "",
-    "text": "Describe the proposed option and how it helps to overcome the problem or limitation"
+    "text": "Status: proposed \nDeciders: V-Sekai, fire\nTags: V-Sekai, AI Assisted"
   },
   {
-    "objectID": "decisions/20211031-create-a-demo-viewer-gallery.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20211031-create-a-demo-viewer-gallery.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Create a demo viewer gallery",
+    "objectID": "decisions/20230616-pmx-to-vrm.html#problem",
+    "href": "decisions/20230616-pmx-to-vrm.html#problem",
+    "title": "Proposed: V-Sekai Bone Hierarchy Conversion",
     "section": "",
-    "text": "Describe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams"
+    "text": "V-Sekai has a problem with its bone hierarchy conversion. This causes issues with Alicia’s hips-spine angle."
   },
   {
-    "objectID": "decisions/20211031-create-a-demo-viewer-gallery.html#positive-consequences",
-    "href": "decisions/20211031-create-a-demo-viewer-gallery.html#positive-consequences",
-    "title": "Proposed: Create a demo viewer gallery",
+    "objectID": "decisions/20230616-pmx-to-vrm.html#solution",
+    "href": "decisions/20230616-pmx-to-vrm.html#solution",
+    "title": "Proposed: V-Sekai Bone Hierarchy Conversion",
     "section": "",
-    "text": "[e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]\n[…]"
+    "text": "We suggest a new conversion method. It keeps the original bone hierarchy and translates bone names from Japanese to English. This avoids problems caused by changing the hierarchy."
   },
   {
-    "objectID": "decisions/20211031-create-a-demo-viewer-gallery.html#negative-consequences",
-    "href": "decisions/20211031-create-a-demo-viewer-gallery.html#negative-consequences",
-    "title": "Proposed: Create a demo viewer gallery",
+    "objectID": "decisions/20230616-pmx-to-vrm.html#changes",
+    "href": "decisions/20230616-pmx-to-vrm.html#changes",
+    "title": "Proposed: V-Sekai Bone Hierarchy Conversion",
     "section": "",
-    "text": "[e.g., compromising quality attribute, follow-up decisions required, …]\n[…]\n\n[this section can be repeated for each option if more than one option is open for consideration]"
+    "text": "Original hierarchy (Japanese names):\nCenter (センター)\n├ UpperBody (上半身)\n└ LowerBody (下半身)\nNew method, same hierarchy, translated names:\nCenter (Hips)\n├ UpperBody (Spine)\n└ LowerBody (Legs)\nAfter the second conversion, the hierarchy changes:\nHips (LowerBody)\n└ Spine (UpperBody)\n\nThis solution keeps the right hips-spine angle for Alicia."
   },
   {
-    "objectID": "decisions/20211031-create-a-demo-viewer-gallery.html#option-graveyard",
-    "href": "decisions/20211031-create-a-demo-viewer-gallery.html#option-graveyard",
-    "title": "Proposed: Create a demo viewer gallery",
+    "objectID": "decisions/20230616-pmx-to-vrm.html#good-outcomes",
+    "href": "decisions/20230616-pmx-to-vrm.html#good-outcomes",
+    "title": "Proposed: V-Sekai Bone Hierarchy Conversion",
     "section": "",
-    "text": "Option: \nRejection Reason:"
+    "text": "Keeps the original bone hierarchy, avoiding animation issues.\nTranslates bone names to English, helping non-Japanese speakers."
   },
   {
-    "objectID": "decisions/20211031-create-a-demo-viewer-gallery.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20211031-create-a-demo-viewer-gallery.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Create a demo viewer gallery",
+    "objectID": "decisions/20230616-pmx-to-vrm.html#bad-outcomes",
+    "href": "decisions/20230616-pmx-to-vrm.html#bad-outcomes",
+    "title": "Proposed: V-Sekai Bone Hierarchy Conversion",
     "section": "",
-    "text": "If this enhancement will not be used often, can it be worked around with a few lines of script?"
+    "text": "Might need more time to create the new method."
   },
   {
-    "objectID": "decisions/20211031-create-a-demo-viewer-gallery.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20211031-create-a-demo-viewer-gallery.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Create a demo viewer gallery",
+    "objectID": "decisions/20230616-pmx-to-vrm.html#other-options",
+    "href": "decisions/20230616-pmx-to-vrm.html#other-options",
+    "title": "Proposed: V-Sekai Bone Hierarchy Conversion",
     "section": "",
-    "text": "Is there a reason why this should be core and done by us?"
+    "text": "Changing the hierarchy during conversion caused the problem."
   },
   {
-    "objectID": "decisions/20211031-create-a-demo-viewer-gallery.html#references",
-    "href": "decisions/20211031-create-a-demo-viewer-gallery.html#references",
-    "title": "Proposed: Create a demo viewer gallery",
+    "objectID": "decisions/20230616-pmx-to-vrm.html#can-it-be-fixed-with-a-script",
+    "href": "decisions/20230616-pmx-to-vrm.html#can-it-be-fixed-with-a-script",
+    "title": "Proposed: V-Sekai Bone Hierarchy Conversion",
     "section": "",
-    "text": "Link type \n…"
+    "text": "No, this needs a new method in the bone hierarchy conversion process."
   },
   {
-    "objectID": "decisions/20211031-create-a-demo-viewer-gallery.html#derivative-license",
-    "href": "decisions/20211031-create-a-demo-viewer-gallery.html#derivative-license",
-    "title": "Proposed: Create a demo viewer gallery",
+    "objectID": "decisions/20230616-pmx-to-vrm.html#should-we-do-it",
+    "href": "decisions/20230616-pmx-to-vrm.html#should-we-do-it",
+    "title": "Proposed: V-Sekai Bone Hierarchy Conversion",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Yes, it affects character animations and user experience with V-Sekai models."
   },
   {
-    "objectID": "decisions/20240618-4-player-test-vsekai.html",
-    "href": "decisions/20240618-4-player-test-vsekai.html",
-    "title": "Proposed: 4 Player Test V-Sekai",
+    "objectID": "decisions/20230616-pmx-to-vrm.html#references",
+    "href": "decisions/20230616-pmx-to-vrm.html#references",
+    "title": "Proposed: V-Sekai Bone Hierarchy Conversion",
     "section": "",
-    "text": "V-Sekai is a social VR functionality for the Godot Engine. It’s an open-source project that brings social VR/VRSNS/metaverse components to the Godot Engine.\n\n\n\nWe want to host a 4 player test tonight.\n\n\n\nHere is a step-by-step guide on how we can achieve this:\n\nImport a map into V-Sekai: We will use a map with a CC-BY or CC0 license for the world upload.\nStart a server: We will set up and start a server where the test will be hosted.\nInvite people: We will then invite the players to join the test.\n\n\n\n\nHosting a 4 player test will allow us to:\n\nUnderstand the performance of our application with multiple users.\nIdentify any bugs or issues that may arise in a multi-player environment.\n\n\n\n\nPotential downsides could include:\n\nServer issues due to multiple connections.\nUnidentified bugs causing disruptions during the test.\n\n\n\n\nAlternative solutions could have been to conduct individual tests with each player, but this would not give us insights into the multi-player experience.\n\n\n\nThis proposal does not cover scenarios where more than 4 players are needed for testing.\n\n\n\nThe entire process from importing the map to inviting the players will be done by the V-Sekai development team.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20240618-4-player-test-vsekai.html#context",
-    "href": "decisions/20240618-4-player-test-vsekai.html#context",
-    "title": "Proposed: 4 Player Test V-Sekai",
+    "objectID": "decisions/20240616-request-for-quad-mesh-dataset.html",
+    "href": "decisions/20240616-request-for-quad-mesh-dataset.html",
+    "title": "Proposed: Triangle to Quad Mesh Dataset Creation",
     "section": "",
-    "text": "V-Sekai is a social VR functionality for the Godot Engine. It’s an open-source project that brings social VR/VRSNS/metaverse components to the Godot Engine."
+    "text": "Mesh Transformers, which consist of a construction worker (auto encoder) and an architect (transformer), aim to simplify the process of generating 3D models. Users can generate a 3D model using a prompt, eliminating the need to search through numerous 3D libraries.\n\n\n\nThe task at hand is to create a triangle mesh to quad mesh dataset that’s suitable for machine learning training. The meshes should be converted from triangles to quads, have captions, contain a maximum of 1k quads, and include at least 100 objects, should be 100_000 objects.\nNote that triangulating a quad mesh is not the same task.\n\n\n\nWe propose using remeshing tools convert triangle meshes to quad meshes.\nThe first dataset will focus on items an avatar would wear. This includes clothing, accessories, and other wearable items.\n\n\n\ncaption\ntype annotation\nmaterial annotation\n\n\n\n\n\nThis proposal simplifies the process of creating 3D models. It allows users to quickly receive a 3D model that fits their needs.\n\n\n\nThe proposal may require significant computational resources. Additionally, there may be some loss of detail during the conversion process.\n\n\n\nAn alternative approach would involve manually converting each quad mesh to a triangle mesh and adding captions. However, this method would be time-consuming and not feasible for large datasets.\n\n\n\nThe proposal may not benefit users who only need a small number of 3D models or those with very specific requirements.\n\n\n\nThe V-Sekai development team will be responsible for creating and converting the meshes.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\nFire\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - The GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nobjaverse_annotations\nV-Sekai.blue-tin-fox-models\n[https://github.com/maria-korosteleva/garment-pattern-generator]\n[https://cmp.felk.cvut.cz/t-less/index.html]\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240618-4-player-test-vsekai.html#problem-statement",
-    "href": "decisions/20240618-4-player-test-vsekai.html#problem-statement",
-    "title": "Proposed: 4 Player Test V-Sekai",
+    "objectID": "decisions/20240616-request-for-quad-mesh-dataset.html#the-context",
+    "href": "decisions/20240616-request-for-quad-mesh-dataset.html#the-context",
+    "title": "Proposed: Triangle to Quad Mesh Dataset Creation",
     "section": "",
-    "text": "We want to host a 4 player test tonight."
+    "text": "Mesh Transformers, which consist of a construction worker (auto encoder) and an architect (transformer), aim to simplify the process of generating 3D models. Users can generate a 3D model using a prompt, eliminating the need to search through numerous 3D libraries."
   },
   {
-    "objectID": "decisions/20240618-4-player-test-vsekai.html#solution",
-    "href": "decisions/20240618-4-player-test-vsekai.html#solution",
-    "title": "Proposed: 4 Player Test V-Sekai",
+    "objectID": "decisions/20240616-request-for-quad-mesh-dataset.html#the-problem-statement",
+    "href": "decisions/20240616-request-for-quad-mesh-dataset.html#the-problem-statement",
+    "title": "Proposed: Triangle to Quad Mesh Dataset Creation",
     "section": "",
-    "text": "Here is a step-by-step guide on how we can achieve this:\n\nImport a map into V-Sekai: We will use a map with a CC-BY or CC0 license for the world upload.\nStart a server: We will set up and start a server where the test will be hosted.\nInvite people: We will then invite the players to join the test."
+    "text": "The task at hand is to create a triangle mesh to quad mesh dataset that’s suitable for machine learning training. The meshes should be converted from triangles to quads, have captions, contain a maximum of 1k quads, and include at least 100 objects, should be 100_000 objects.\nNote that triangulating a quad mesh is not the same task."
   },
   {
-    "objectID": "decisions/20240618-4-player-test-vsekai.html#benefits",
-    "href": "decisions/20240618-4-player-test-vsekai.html#benefits",
-    "title": "Proposed: 4 Player Test V-Sekai",
+    "objectID": "decisions/20240616-request-for-quad-mesh-dataset.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240616-request-for-quad-mesh-dataset.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Triangle to Quad Mesh Dataset Creation",
     "section": "",
-    "text": "Hosting a 4 player test will allow us to:\n\nUnderstand the performance of our application with multiple users.\nIdentify any bugs or issues that may arise in a multi-player environment."
+    "text": "We propose using remeshing tools convert triangle meshes to quad meshes.\nThe first dataset will focus on items an avatar would wear. This includes clothing, accessories, and other wearable items.\n\n\n\ncaption\ntype annotation\nmaterial annotation"
   },
   {
-    "objectID": "decisions/20240618-4-player-test-vsekai.html#downsides",
-    "href": "decisions/20240618-4-player-test-vsekai.html#downsides",
-    "title": "Proposed: 4 Player Test V-Sekai",
+    "objectID": "decisions/20240616-request-for-quad-mesh-dataset.html#the-benefits",
+    "href": "decisions/20240616-request-for-quad-mesh-dataset.html#the-benefits",
+    "title": "Proposed: Triangle to Quad Mesh Dataset Creation",
     "section": "",
-    "text": "Potential downsides could include:\n\nServer issues due to multiple connections.\nUnidentified bugs causing disruptions during the test."
+    "text": "This proposal simplifies the process of creating 3D models. It allows users to quickly receive a 3D model that fits their needs."
   },
   {
-    "objectID": "decisions/20240618-4-player-test-vsekai.html#the-road-not-taken",
-    "href": "decisions/20240618-4-player-test-vsekai.html#the-road-not-taken",
-    "title": "Proposed: 4 Player Test V-Sekai",
+    "objectID": "decisions/20240616-request-for-quad-mesh-dataset.html#the-downsides",
+    "href": "decisions/20240616-request-for-quad-mesh-dataset.html#the-downsides",
+    "title": "Proposed: Triangle to Quad Mesh Dataset Creation",
     "section": "",
-    "text": "Alternative solutions could have been to conduct individual tests with each player, but this would not give us insights into the multi-player experience."
+    "text": "The proposal may require significant computational resources. Additionally, there may be some loss of detail during the conversion process."
   },
   {
-    "objectID": "decisions/20240618-4-player-test-vsekai.html#the-infrequent-use-case",
-    "href": "decisions/20240618-4-player-test-vsekai.html#the-infrequent-use-case",
-    "title": "Proposed: 4 Player Test V-Sekai",
+    "objectID": "decisions/20240616-request-for-quad-mesh-dataset.html#the-road-not-taken",
+    "href": "decisions/20240616-request-for-quad-mesh-dataset.html#the-road-not-taken",
+    "title": "Proposed: Triangle to Quad Mesh Dataset Creation",
     "section": "",
-    "text": "This proposal does not cover scenarios where more than 4 players are needed for testing."
+    "text": "An alternative approach would involve manually converting each quad mesh to a triangle mesh and adding captions. However, this method would be time-consuming and not feasible for large datasets."
   },
   {
-    "objectID": "decisions/20240618-4-player-test-vsekai.html#in-core-and-done-by-us",
-    "href": "decisions/20240618-4-player-test-vsekai.html#in-core-and-done-by-us",
-    "title": "Proposed: 4 Player Test V-Sekai",
+    "objectID": "decisions/20240616-request-for-quad-mesh-dataset.html#the-infrequent-use-case",
+    "href": "decisions/20240616-request-for-quad-mesh-dataset.html#the-infrequent-use-case",
+    "title": "Proposed: Triangle to Quad Mesh Dataset Creation",
     "section": "",
-    "text": "The entire process from importing the map to inviting the players will be done by the V-Sekai development team."
+    "text": "The proposal may not benefit users who only need a small number of 3D models or those with very specific requirements."
   },
   {
-    "objectID": "decisions/20240618-4-player-test-vsekai.html#status",
-    "href": "decisions/20240618-4-player-test-vsekai.html#status",
-    "title": "Proposed: 4 Player Test V-Sekai",
+    "objectID": "decisions/20240616-request-for-quad-mesh-dataset.html#in-core-and-done-by-us",
+    "href": "decisions/20240616-request-for-quad-mesh-dataset.html#in-core-and-done-by-us",
+    "title": "Proposed: Triangle to Quad Mesh Dataset Creation",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "The V-Sekai development team will be responsible for creating and converting the meshes."
   },
   {
-    "objectID": "decisions/20240618-4-player-test-vsekai.html#decision-makers",
-    "href": "decisions/20240618-4-player-test-vsekai.html#decision-makers",
-    "title": "Proposed: 4 Player Test V-Sekai",
+    "objectID": "decisions/20240616-request-for-quad-mesh-dataset.html#status",
+    "href": "decisions/20240616-request-for-quad-mesh-dataset.html#status",
+    "title": "Proposed: Triangle to Quad Mesh Dataset Creation",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20240618-4-player-test-vsekai.html#tags",
-    "href": "decisions/20240618-4-player-test-vsekai.html#tags",
-    "title": "Proposed: 4 Player Test V-Sekai",
+    "objectID": "decisions/20240616-request-for-quad-mesh-dataset.html#decision-makers",
+    "href": "decisions/20240616-request-for-quad-mesh-dataset.html#decision-makers",
+    "title": "Proposed: Triangle to Quad Mesh Dataset Creation",
     "section": "",
-    "text": "V-Sekai"
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20240618-4-player-test-vsekai.html#further-reading",
-    "href": "decisions/20240618-4-player-test-vsekai.html#further-reading",
-    "title": "Proposed: 4 Player Test V-Sekai",
+    "objectID": "decisions/20240616-request-for-quad-mesh-dataset.html#tags",
+    "href": "decisions/20240616-request-for-quad-mesh-dataset.html#tags",
+    "title": "Proposed: Triangle to Quad Mesh Dataset Creation",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "V-Sekai\nFire"
   },
   {
-    "objectID": "decisions/20240715-vrchat-networking-mental-model.html",
-    "href": "decisions/20240715-vrchat-networking-mental-model.html",
-    "title": "Proposed: Create a Conceptual Model of VRChat Networking",
+    "objectID": "decisions/20240616-request-for-quad-mesh-dataset.html#further-reading",
+    "href": "decisions/20240616-request-for-quad-mesh-dataset.html#further-reading",
+    "title": "Proposed: Triangle to Quad Mesh Dataset Creation",
     "section": "",
-    "text": "In the realm of virtual reality, particularly within VRChat, understanding the networking model is crucial for developers. This proposal aims to create a comprehensive conceptual model of VRChat’s networking system.\n\n\n\nDevelopers often struggle with the intricacies of VRChat’s networking, leading to inefficient code and suboptimal user experiences. A clear and concise guide is needed to demystify the process.\n\n\n\n\n\nThere are two primary methods to send data in VRChat:\n\nUdonsynced Variables:\n\nMark variables as [UdonSynced].\nCall RequestSerialization() in the script to send a copy of the synced variables to all other clients.\nOnly the owner can call RequestSerialization(), so ensure you call Networking.SetOwner() first.\nAn event called OnDeserialization is triggered when a network packet is received.\n\nNetwork Events:\n\nUse SendCustomNetworkEvent() to send an event.\nSpecify a string that matches the name of a function taking no arguments; this function will run upon receiving the event.\nChoose to send the event either to the owner or all clients.\n\n\n// Example of Udonsynced variable\n[UdonBehaviourSyncMode(BehaviourSyncMode.Manual)]\npublic class SyncExample : UdonSharpBehaviour\n{\n    [UdonSynced] private int syncedVariable;\n\n    public void UpdateVariable(int newValue)\n    {\n        if (Networking.IsOwner(gameObject))\n        {\n            syncedVariable = newValue;\n            RequestSerialization();\n        }\n    }\n\n    public override void OnDeserialization()\n    {\n        // Handle deserialized data\n    }\n}\n\n// Example of Network Event\npublic class EventExample : UdonSharpBehaviour\n{\n    public void TriggerEvent()\n    {\n        SendCustomNetworkEvent(VRC.Udon.Common.Interfaces.NetworkEventTarget.All, \"HandleEvent\");\n    }\n\n    public void HandleEvent()\n    {\n        // Handle the event\n    }\n}\n\n\n\n\n\nImproved Readability: Clear guidelines enhance the readability of networking code.\nConsistency: Ensures uniformity in how networking tasks are handled across different projects.\nEfficiency: Streamlined processes make it easier for developers to implement networking features quickly.\n\n\n\n\n\nInitial Setup Time: Establishing and fine-tuning the mental model requires an initial investment of time and resources.\nLimited Flexibility: Strict adherence to the model may limit creative solutions to unique problems.\n\n\n\n\nAlternative approaches such as manual editing or using different networking models were considered but ultimately impossible as we don’t run VRChat.\n\n\n\nIn scenarios where highly specialized or technical networking solutions are required, additional human oversight may be necessary to ensure accuracy and appropriateness.\n\n\n\nWe need to understand how networking models work.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\nFire\nMMMaellon\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article.\n\n\nCentauri2442 recorded the byte count(s) of every synced variable type in udon\n\n\n\n\n\n\n\n\n\n\nSystem Type\nmaxByte\nminByte\nvariableType\nNotes\n\n\n\n\nSystem.Boolean\n2\n2\nBool\n\n\n\nSystem.Char\n2\n2\nChar\n\n\n\nSystem.Byte\n2\n2\nByte\n\n\n\nSystem.SByte\n2\n2\nSByte\n\n\n\nSystem.Int16\n4\n2\nShort\nSwaps every other\n\n\nSystem.UInt16\n4\n2\nUShort\nSwaps every other\n\n\nSystem.Int32\n8\n4\nInt\nSwaps every other\n\n\nSystem.UInt32\n8\n4\nUInt\nSwaps every other\n\n\nSystem.Int64\n12\n8\nLong\nSwaps every other\n\n\nSystem.UInt64\n12\n8\nULong\nSwaps every other\n\n\nSystem.Single\n8\n4\nFloat\nSwaps every other\n\n\nSystem.Double\n12\n8\nDouble\nSwaps every other\n\n\nUnityEngine.Vector2\n8\n8\nVector2\n\n\n\nUnityEngine.Vector3\n12\n12\nVector3\n\n\n\nUnityEngine.Vector4\n16\n16\nVector4\n\n\n\nUnityEngine.Quaternion\n16\n16\nQuaternion\n\n\n\nSystem.String\n84\n1\nString\nNull: No serialization | 84 + 1 byte per character, byte size allocated per for (84, 88, 92, etc)\n\n\nRVCUInt\n8\n8\nRVCUInt\n\n\n\nUnityEngine.Color\n8\n8\nColor\n\n\n\nUnityEngine.Color32\n8\n8\nColor32\n\n\n\nSystem.BooleanArray\n80\n80\nBooleanArray\n80 + array size in increments of 4 as buffer (80, 84, 88, etc) | Will increase every 4 values (5, 9, 13, etc)\n\n\nSystem.CharArray\n80\n80\nCharArray\n80 + array size in increments of 4 as buffer (80, 84, 88, etc) | Will increase every 4 values (5, 9, 13, etc)\n\n\nSystem.ByteArray\n80\n80\nByteArray\n80 + array size in increments of 4 as buffer (80, 84, 88, etc) | Will increase every 4 values (5, 9, 13, etc)\n\n\nSystem.SByteArray\n80\n80\nSByteArray\n80 + array size in increments of 4 as buffer (80, 84, 88, etc) | Will increase every 4 values (5, 9, 13, etc)\n\n\nSystem.Int16Array\n80\n80\nShortArray\n80 + array size in increments of 4 as buffer (80, 84, 88, etc) | Will increase every 2 values (3, 5, 7, etc)\n\n\nSystem.UInt16Array\n80\n80\nUShortArray\n80 + array size in increments of 4 as buffer (80, 84, 88, etc) | Will increase every 2 values (3, 5, 7, etc)\n\n\nSystem.Int32Array\n80\n80\nIntArray\n80 + array size * 4\n\n\nSystem.UInt32Array\n80\n80\nUIntArray\n80 + array size * 4\n\n\nSystem.Int64Array\n80\n80\nLongArray\n80 + array size * 8\n\n\nSystem.UInt64Array\n80\n80\nULongArray\n80 + array size * 8\n\n\nSystem.SingleArray\n80\n80\nFloatArray\n80 + array size * 4\n\n\nSystem.DoubleArray\n80\n80\nDoubleArray\n80 + array size * 8\n\n\nUnityEngine.Vector2Array\n80\n80\nVector2Array\n80 + array size * 8\n\n\nUnityEngine.Vector3Array\n80\n80\nVector3Array\n80 + array size * 12\n\n\nUnityEngine.Vector4Array\n80\n80\nVector4Array\n80 + array size * 16\n\n\nUnityEngine.QuaternionArray\n80\n80\nQuaternionArray\n80 + array size * 16\n\n\nSystem.StringArray\n80\n80\nStringArray\n84 + (2, 4, or 8 bytes per character). Size of 0: 84 bytes. Size greater than 0 but with any null values: 0 bytes. Size greater than 0 with all valid strings: 84 + (2, 4, or 8 bytes per character)\n\n\nRVCUStringArray\n80\n80\nRVCUStringArray\n84 + (2, 4, or 8 bytes per character). Size of 0: 84 bytes. Size greater than 0 but with any null values: 0 bytes. Size greater than 0 with all valid strings: 84 + (2, 4, or 8 bytes per character)\n\n\nUnityEngine.ColorArray\n80\n80\nColorArray\n80 + array size * 16\n\n\nUnityEngine.Color32Array\n80\n80\nColor32Array\n80 + array size * 4\n\n\n\n\n\n\nAnswer: In VRChat, which uses UdonSharp for scripting, there isn’t a hard limit on the number of UdonSharpBehaviour instances a world (or server instance) can have. However, practical limits are imposed by performance considerations. Each UdonSharpBehaviour consumes memory and processing power, so the total number you can effectively use will depend on the complexity of your scripts and the capabilities of the hardware running the world. It’s essential to optimize your scripts and manage resources efficiently to ensure smooth performance.\n\n\n\nAnswer: Yes, UdonSharpBehaviour instances can communicate with each other. Here are some ways they can interact:\n\nCustom Network Events: You can send custom network events (with zero parameters) to trigger actions in other UdonSharpBehaviour instances. The receiver won’t know who the sender is, and the action will be performed locally on the UdonSharpBehaviour’s current frame.\nSynced Variables: If you need to send data, it’s better to use synced variables rather than mixing them with network events. When these variables get updated, the OnDeserialization() method will be called. This is a function in UdonSharpBehaviour that you can override to handle any work needed with the updated variables.\n\n\n\n\nAnswer: You typically don’t mix network events with synced variables. If you need to send data, just use synced variables. When the variables get updated, OnDeserialization() will be called. That’s a function in UdonSharpBehaviour that you can override. Do all the work needed with the variables in OnDeserialization.\n\n\n\nAnswer: There’s an advanced feature called FieldChangeCallbacks that allows for code simplification. Basically, create a C# property with a getter and a setter and specify it as the field change callback. The setter will be called in addition to OnDeserialization when network updates come in. This helps combine the code for local and remote clients in the setter. This is an advanced code-writing optimization for making your code cleaner. No, it does not affect performance in terms of space and time. FieldChangeCallbacks reduces code repetition, thereby simplifying the codebase and making it more maintainable.\n\n\n\nAnswer: Assume we calculate the state of the world independently for each frame, without depending on previous frames. This means that while the exact values of the three variables are crucial for determining the current state, the order of changes within the same frame does not affect the final state interpretation at that frame."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - The GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nobjaverse_annotations\nV-Sekai.blue-tin-fox-models\n[https://github.com/maria-korosteleva/garment-pattern-generator]\n[https://cmp.felk.cvut.cz/t-less/index.html]\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240715-vrchat-networking-mental-model.html#the-context",
-    "href": "decisions/20240715-vrchat-networking-mental-model.html#the-context",
-    "title": "Proposed: Create a Conceptual Model of VRChat Networking",
+    "objectID": "decisions/20230602-v-sekai-roadmap.html",
+    "href": "decisions/20230602-v-sekai-roadmap.html",
+    "title": "Superseded: V-Sekai Roadmap and Goals 2023-06-02",
     "section": "",
-    "text": "In the realm of virtual reality, particularly within VRChat, understanding the networking model is crucial for developers. This proposal aims to create a comprehensive conceptual model of VRChat’s networking system."
+    "text": "Superseded: V-Sekai Roadmap and Goals 2023-06-02\n\nMetadata\n\nStatus: superseded by 20230608-v-sekai-roadmap.md \nDeciders: V-Sekai, fire, lyuma\nTags: V-Sekai,gpt4 summary\n\n\n\nContext and Problem Statement\nWhat is the V-Sekai Roadmap and Goals?\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nThe roadmap presented here is short-term.\n\n\nDescribe how your proposal will work with code, pseudo-code, mock-ups, or diagrams\ngraph LR\n  subgraph Short Term\n    A[June 02th, 2023] --&gt; E[VRM 1 import and export]\n    E --&gt; F[VRM 1 and OMI_personality]\n    F --&gt; G[Nightclub aquarium booth 4mx4mx5m]\n    G --&gt; H[Add jitter buffer to godot_speech]\n    H --&gt; I[Assist with onevoip]\n    I --&gt; K[What is stretchsense?]\n    K --&gt; L[How can we get more artwork?]\n    L --&gt; M[Collective work and other matters?]\n  end\n\n\nPositive Consequences\nWe can create V-Sekai easier.\n\n\nNegative Consequences\nOverhead might be hard.\n\n\nOption graveyard\nWe can avoid planning.\n\n\nIf this enhancement will be used infrequently, can it be worked around with a few lines of script?\nNo. This is a process.\n\n\nIs there a reason why this should be core and done by us?\nThis is a core process for V-Sekai.\n\n\nReferences\n\nV-Sekai"
   },
   {
-    "objectID": "decisions/20240715-vrchat-networking-mental-model.html#the-problem-statement",
-    "href": "decisions/20240715-vrchat-networking-mental-model.html#the-problem-statement",
-    "title": "Proposed: Create a Conceptual Model of VRChat Networking",
+    "objectID": "decisions/20230812-gocd-agent-setup.html",
+    "href": "decisions/20230812-gocd-agent-setup.html",
+    "title": "Proposed: Configuring GoCD Agents in V-Sekai",
     "section": "",
-    "text": "Developers often struggle with the intricacies of VRChat’s networking, leading to inefficient code and suboptimal user experiences. A clear and concise guide is needed to demystify the process."
+    "text": "Status: proposed \nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nV-Sekai is a platform that requires regular configuration of GoCD agents. This process can be time-consuming and prone to errors if not done correctly.\n\n\n\nThe challenge is to configure the GoCD agents after a restart of the host machine. This involves accessing the GoCD server, navigating to the Agents page, enabling new agents, configuring agent resources, assigning environments, and saving changes.\n\n\n\nThe strategy is to follow a step-by-step guide to ensure that all the necessary configurations are made correctly. This includes:\n\nAccessing the GoCD Server\nNavigating to the Agents Page\nEnabling New Agents\nConfiguring Agent Resources\nAssigning Environments\nSaving Changes\n\n\n\n\nBy following this guide, users can ensure that their GoCD agents are configured correctly and ready to run jobs. This can save time and reduce the risk of errors.\n\n\n\nThe downside is that this process needs to be repeated every time the host machine is restarted. However, this is a necessary step to ensure that the GoCD agents function correctly.\n\n\n\nAn alternative approach could be to automate this process using scripts or other automation tools. However, this would require additional technical expertise and may not be feasible for all users.\n\n\n\nIn some cases, users may need to configure additional settings or use different resources and environments. These cases will require additional steps and may not be covered by this guide.\n\n\n\nYes, this guide was created by us and is part of our core documentation.\n\n\n\n\nV-Sekai\nThis article is assisted by AI.\n\n\n\n\n\n\n\n\n\n\n\n\nAgent Type\nResources\nEnvironments\n\n\n\n\ngocd-agent-59dbf9989-vp4d66\nlinux, mingw5\ndevelopment, itch-fire\n\n\ngocd-agent-dind-96575468d4-s29l2\ndind\ndevelopment, itch-fire\n\n\ngocd-agent-59dbf9989-cczqj\nlinux, mingw5\ndevelopment, itch-fire\n\n\ngocd-agent-59dbf9989-p6vs5\nlinux, mingw5\ndevelopment, itch-fire\n\n\ngocd-agent-59dbf9989-t4ckd\nlinux, mingw5\ndevelopment, itch-fire\n\n\ngocd-agent-dind-96575468d4-b6gq9\ndind\ndevelopment, itch-fire\n\n\n\nPlease note that the actual resources and environments will vary based on your specific setup."
   },
   {
-    "objectID": "decisions/20240715-vrchat-networking-mental-model.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240715-vrchat-networking-mental-model.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Create a Conceptual Model of VRChat Networking",
+    "objectID": "decisions/20230812-gocd-agent-setup.html#metadata",
+    "href": "decisions/20230812-gocd-agent-setup.html#metadata",
+    "title": "Proposed: Configuring GoCD Agents in V-Sekai",
     "section": "",
-    "text": "There are two primary methods to send data in VRChat:\n\nUdonsynced Variables:\n\nMark variables as [UdonSynced].\nCall RequestSerialization() in the script to send a copy of the synced variables to all other clients.\nOnly the owner can call RequestSerialization(), so ensure you call Networking.SetOwner() first.\nAn event called OnDeserialization is triggered when a network packet is received.\n\nNetwork Events:\n\nUse SendCustomNetworkEvent() to send an event.\nSpecify a string that matches the name of a function taking no arguments; this function will run upon receiving the event.\nChoose to send the event either to the owner or all clients.\n\n\n// Example of Udonsynced variable\n[UdonBehaviourSyncMode(BehaviourSyncMode.Manual)]\npublic class SyncExample : UdonSharpBehaviour\n{\n    [UdonSynced] private int syncedVariable;\n\n    public void UpdateVariable(int newValue)\n    {\n        if (Networking.IsOwner(gameObject))\n        {\n            syncedVariable = newValue;\n            RequestSerialization();\n        }\n    }\n\n    public override void OnDeserialization()\n    {\n        // Handle deserialized data\n    }\n}\n\n// Example of Network Event\npublic class EventExample : UdonSharpBehaviour\n{\n    public void TriggerEvent()\n    {\n        SendCustomNetworkEvent(VRC.Udon.Common.Interfaces.NetworkEventTarget.All, \"HandleEvent\");\n    }\n\n    public void HandleEvent()\n    {\n        // Handle the event\n    }\n}"
+    "text": "Status: proposed \nDeciders: V-Sekai\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20240715-vrchat-networking-mental-model.html#the-benefits",
-    "href": "decisions/20240715-vrchat-networking-mental-model.html#the-benefits",
-    "title": "Proposed: Create a Conceptual Model of VRChat Networking",
+    "objectID": "decisions/20230812-gocd-agent-setup.html#the-backdrop",
+    "href": "decisions/20230812-gocd-agent-setup.html#the-backdrop",
+    "title": "Proposed: Configuring GoCD Agents in V-Sekai",
     "section": "",
-    "text": "Improved Readability: Clear guidelines enhance the readability of networking code.\nConsistency: Ensures uniformity in how networking tasks are handled across different projects.\nEfficiency: Streamlined processes make it easier for developers to implement networking features quickly."
+    "text": "V-Sekai is a platform that requires regular configuration of GoCD agents. This process can be time-consuming and prone to errors if not done correctly."
   },
   {
-    "objectID": "decisions/20240715-vrchat-networking-mental-model.html#the-downsides",
-    "href": "decisions/20240715-vrchat-networking-mental-model.html#the-downsides",
-    "title": "Proposed: Create a Conceptual Model of VRChat Networking",
+    "objectID": "decisions/20230812-gocd-agent-setup.html#the-challenge",
+    "href": "decisions/20230812-gocd-agent-setup.html#the-challenge",
+    "title": "Proposed: Configuring GoCD Agents in V-Sekai",
     "section": "",
-    "text": "Initial Setup Time: Establishing and fine-tuning the mental model requires an initial investment of time and resources.\nLimited Flexibility: Strict adherence to the model may limit creative solutions to unique problems."
+    "text": "The challenge is to configure the GoCD agents after a restart of the host machine. This involves accessing the GoCD server, navigating to the Agents page, enabling new agents, configuring agent resources, assigning environments, and saving changes."
   },
   {
-    "objectID": "decisions/20240715-vrchat-networking-mental-model.html#the-road-not-taken",
-    "href": "decisions/20240715-vrchat-networking-mental-model.html#the-road-not-taken",
-    "title": "Proposed: Create a Conceptual Model of VRChat Networking",
+    "objectID": "decisions/20230812-gocd-agent-setup.html#the-strategy",
+    "href": "decisions/20230812-gocd-agent-setup.html#the-strategy",
+    "title": "Proposed: Configuring GoCD Agents in V-Sekai",
     "section": "",
-    "text": "Alternative approaches such as manual editing or using different networking models were considered but ultimately impossible as we don’t run VRChat."
+    "text": "The strategy is to follow a step-by-step guide to ensure that all the necessary configurations are made correctly. This includes:\n\nAccessing the GoCD Server\nNavigating to the Agents Page\nEnabling New Agents\nConfiguring Agent Resources\nAssigning Environments\nSaving Changes"
   },
   {
-    "objectID": "decisions/20240715-vrchat-networking-mental-model.html#the-infrequent-use-case",
-    "href": "decisions/20240715-vrchat-networking-mental-model.html#the-infrequent-use-case",
-    "title": "Proposed: Create a Conceptual Model of VRChat Networking",
+    "objectID": "decisions/20230812-gocd-agent-setup.html#the-upside",
+    "href": "decisions/20230812-gocd-agent-setup.html#the-upside",
+    "title": "Proposed: Configuring GoCD Agents in V-Sekai",
     "section": "",
-    "text": "In scenarios where highly specialized or technical networking solutions are required, additional human oversight may be necessary to ensure accuracy and appropriateness."
+    "text": "By following this guide, users can ensure that their GoCD agents are configured correctly and ready to run jobs. This can save time and reduce the risk of errors."
   },
   {
-    "objectID": "decisions/20240715-vrchat-networking-mental-model.html#in-core-and-done-by-us",
-    "href": "decisions/20240715-vrchat-networking-mental-model.html#in-core-and-done-by-us",
-    "title": "Proposed: Create a Conceptual Model of VRChat Networking",
+    "objectID": "decisions/20230812-gocd-agent-setup.html#the-downside",
+    "href": "decisions/20230812-gocd-agent-setup.html#the-downside",
+    "title": "Proposed: Configuring GoCD Agents in V-Sekai",
     "section": "",
-    "text": "We need to understand how networking models work."
+    "text": "The downside is that this process needs to be repeated every time the host machine is restarted. However, this is a necessary step to ensure that the GoCD agents function correctly."
   },
   {
-    "objectID": "decisions/20240715-vrchat-networking-mental-model.html#status",
-    "href": "decisions/20240715-vrchat-networking-mental-model.html#status",
-    "title": "Proposed: Create a Conceptual Model of VRChat Networking",
+    "objectID": "decisions/20230812-gocd-agent-setup.html#the-road-not-taken",
+    "href": "decisions/20230812-gocd-agent-setup.html#the-road-not-taken",
+    "title": "Proposed: Configuring GoCD Agents in V-Sekai",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "An alternative approach could be to automate this process using scripts or other automation tools. However, this would require additional technical expertise and may not be feasible for all users."
   },
   {
-    "objectID": "decisions/20240715-vrchat-networking-mental-model.html#decision-makers",
-    "href": "decisions/20240715-vrchat-networking-mental-model.html#decision-makers",
-    "title": "Proposed: Create a Conceptual Model of VRChat Networking",
+    "objectID": "decisions/20230812-gocd-agent-setup.html#the-infrequent-use-case",
+    "href": "decisions/20230812-gocd-agent-setup.html#the-infrequent-use-case",
+    "title": "Proposed: Configuring GoCD Agents in V-Sekai",
     "section": "",
-    "text": "V-Sekai development team\nFire\nMMMaellon"
+    "text": "In some cases, users may need to configure additional settings or use different resources and environments. These cases will require additional steps and may not be covered by this guide."
   },
   {
-    "objectID": "decisions/20240715-vrchat-networking-mental-model.html#tags",
-    "href": "decisions/20240715-vrchat-networking-mental-model.html#tags",
-    "title": "Proposed: Create a Conceptual Model of VRChat Networking",
+    "objectID": "decisions/20230812-gocd-agent-setup.html#in-core-and-done-by-us",
+    "href": "decisions/20230812-gocd-agent-setup.html#in-core-and-done-by-us",
+    "title": "Proposed: Configuring GoCD Agents in V-Sekai",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Yes, this guide was created by us and is part of our core documentation."
   },
   {
-    "objectID": "decisions/20240715-vrchat-networking-mental-model.html#further-reading",
-    "href": "decisions/20240715-vrchat-networking-mental-model.html#further-reading",
-    "title": "Proposed: Create a Conceptual Model of VRChat Networking",
+    "objectID": "decisions/20230812-gocd-agent-setup.html#further-reading",
+    "href": "decisions/20230812-gocd-agent-setup.html#further-reading",
+    "title": "Proposed: Configuring GoCD Agents in V-Sekai",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article.\n\n\nCentauri2442 recorded the byte count(s) of every synced variable type in udon\n\n\n\n\n\n\n\n\n\n\nSystem Type\nmaxByte\nminByte\nvariableType\nNotes\n\n\n\n\nSystem.Boolean\n2\n2\nBool\n\n\n\nSystem.Char\n2\n2\nChar\n\n\n\nSystem.Byte\n2\n2\nByte\n\n\n\nSystem.SByte\n2\n2\nSByte\n\n\n\nSystem.Int16\n4\n2\nShort\nSwaps every other\n\n\nSystem.UInt16\n4\n2\nUShort\nSwaps every other\n\n\nSystem.Int32\n8\n4\nInt\nSwaps every other\n\n\nSystem.UInt32\n8\n4\nUInt\nSwaps every other\n\n\nSystem.Int64\n12\n8\nLong\nSwaps every other\n\n\nSystem.UInt64\n12\n8\nULong\nSwaps every other\n\n\nSystem.Single\n8\n4\nFloat\nSwaps every other\n\n\nSystem.Double\n12\n8\nDouble\nSwaps every other\n\n\nUnityEngine.Vector2\n8\n8\nVector2\n\n\n\nUnityEngine.Vector3\n12\n12\nVector3\n\n\n\nUnityEngine.Vector4\n16\n16\nVector4\n\n\n\nUnityEngine.Quaternion\n16\n16\nQuaternion\n\n\n\nSystem.String\n84\n1\nString\nNull: No serialization | 84 + 1 byte per character, byte size allocated per for (84, 88, 92, etc)\n\n\nRVCUInt\n8\n8\nRVCUInt\n\n\n\nUnityEngine.Color\n8\n8\nColor\n\n\n\nUnityEngine.Color32\n8\n8\nColor32\n\n\n\nSystem.BooleanArray\n80\n80\nBooleanArray\n80 + array size in increments of 4 as buffer (80, 84, 88, etc) | Will increase every 4 values (5, 9, 13, etc)\n\n\nSystem.CharArray\n80\n80\nCharArray\n80 + array size in increments of 4 as buffer (80, 84, 88, etc) | Will increase every 4 values (5, 9, 13, etc)\n\n\nSystem.ByteArray\n80\n80\nByteArray\n80 + array size in increments of 4 as buffer (80, 84, 88, etc) | Will increase every 4 values (5, 9, 13, etc)\n\n\nSystem.SByteArray\n80\n80\nSByteArray\n80 + array size in increments of 4 as buffer (80, 84, 88, etc) | Will increase every 4 values (5, 9, 13, etc)\n\n\nSystem.Int16Array\n80\n80\nShortArray\n80 + array size in increments of 4 as buffer (80, 84, 88, etc) | Will increase every 2 values (3, 5, 7, etc)\n\n\nSystem.UInt16Array\n80\n80\nUShortArray\n80 + array size in increments of 4 as buffer (80, 84, 88, etc) | Will increase every 2 values (3, 5, 7, etc)\n\n\nSystem.Int32Array\n80\n80\nIntArray\n80 + array size * 4\n\n\nSystem.UInt32Array\n80\n80\nUIntArray\n80 + array size * 4\n\n\nSystem.Int64Array\n80\n80\nLongArray\n80 + array size * 8\n\n\nSystem.UInt64Array\n80\n80\nULongArray\n80 + array size * 8\n\n\nSystem.SingleArray\n80\n80\nFloatArray\n80 + array size * 4\n\n\nSystem.DoubleArray\n80\n80\nDoubleArray\n80 + array size * 8\n\n\nUnityEngine.Vector2Array\n80\n80\nVector2Array\n80 + array size * 8\n\n\nUnityEngine.Vector3Array\n80\n80\nVector3Array\n80 + array size * 12\n\n\nUnityEngine.Vector4Array\n80\n80\nVector4Array\n80 + array size * 16\n\n\nUnityEngine.QuaternionArray\n80\n80\nQuaternionArray\n80 + array size * 16\n\n\nSystem.StringArray\n80\n80\nStringArray\n84 + (2, 4, or 8 bytes per character). Size of 0: 84 bytes. Size greater than 0 but with any null values: 0 bytes. Size greater than 0 with all valid strings: 84 + (2, 4, or 8 bytes per character)\n\n\nRVCUStringArray\n80\n80\nRVCUStringArray\n84 + (2, 4, or 8 bytes per character). Size of 0: 84 bytes. Size greater than 0 but with any null values: 0 bytes. Size greater than 0 with all valid strings: 84 + (2, 4, or 8 bytes per character)\n\n\nUnityEngine.ColorArray\n80\n80\nColorArray\n80 + array size * 16\n\n\nUnityEngine.Color32Array\n80\n80\nColor32Array\n80 + array size * 4\n\n\n\n\n\n\nAnswer: In VRChat, which uses UdonSharp for scripting, there isn’t a hard limit on the number of UdonSharpBehaviour instances a world (or server instance) can have. However, practical limits are imposed by performance considerations. Each UdonSharpBehaviour consumes memory and processing power, so the total number you can effectively use will depend on the complexity of your scripts and the capabilities of the hardware running the world. It’s essential to optimize your scripts and manage resources efficiently to ensure smooth performance.\n\n\n\nAnswer: Yes, UdonSharpBehaviour instances can communicate with each other. Here are some ways they can interact:\n\nCustom Network Events: You can send custom network events (with zero parameters) to trigger actions in other UdonSharpBehaviour instances. The receiver won’t know who the sender is, and the action will be performed locally on the UdonSharpBehaviour’s current frame.\nSynced Variables: If you need to send data, it’s better to use synced variables rather than mixing them with network events. When these variables get updated, the OnDeserialization() method will be called. This is a function in UdonSharpBehaviour that you can override to handle any work needed with the updated variables.\n\n\n\n\nAnswer: You typically don’t mix network events with synced variables. If you need to send data, just use synced variables. When the variables get updated, OnDeserialization() will be called. That’s a function in UdonSharpBehaviour that you can override. Do all the work needed with the variables in OnDeserialization.\n\n\n\nAnswer: There’s an advanced feature called FieldChangeCallbacks that allows for code simplification. Basically, create a C# property with a getter and a setter and specify it as the field change callback. The setter will be called in addition to OnDeserialization when network updates come in. This helps combine the code for local and remote clients in the setter. This is an advanced code-writing optimization for making your code cleaner. No, it does not affect performance in terms of space and time. FieldChangeCallbacks reduces code repetition, thereby simplifying the codebase and making it more maintainable.\n\n\n\nAnswer: Assume we calculate the state of the world independently for each frame, without depending on previous frames. This means that while the exact values of the three variables are crucial for determining the current state, the order of changes within the same frame does not affect the final state interpretation at that frame."
+    "text": "V-Sekai\nThis article is assisted by AI."
   },
   {
-    "objectID": "decisions/20230701-vsekai-broken-down-goals.html",
-    "href": "decisions/20230701-vsekai-broken-down-goals.html",
-    "title": "Proposed: V-Sekai Feature Enhancement Proposal",
+    "objectID": "decisions/20230812-gocd-agent-setup.html#example-configuration",
+    "href": "decisions/20230812-gocd-agent-setup.html#example-configuration",
+    "title": "Proposed: Configuring GoCD Agents in V-Sekai",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, ai summarized\n\n\n\n\nWe are developing a virtual reality platform, V-Sekai. To ensure the platform meets user needs and expectations, we have identified several features that need to be implemented. These features have been categorized based on their priority and necessity for the initial release.\n\n\n\nThe features have been organized into three categories: Must-Have, Nice-to-Have, and Out of Scope Initially. The priority within each category reflects the relative importance of the features for an initial release.\n\n\n\n\n\n\n\n\n\n\nPriority\nFeature\nDependencies\n\n\n\n\n1\nEnvironment (scene loading, world hosting, instancing)\nNone\n\n\n2\nWeb requests to servers (HTTP/WebSocket API)\nEnvironment\n\n\n3\nPerson to person interaction (avatars, animation, synchronization)\nEnvironment\n\n\n4\nInteraction with the world (interactive elements, physics)\nEnvironment\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nPriority\nFeature\nDependencies\n\n\n\n\n5\nCollaboration features (doodling, modeling, content loading)\nEnvironment, Person to person interaction\n\n\n6\nStatic content creation in editor (import avatars, create worlds)\nEnvironment\n\n\n7\nShareable content (inventory)\nEnvironment, Static content creation in editor\n\n\n8\nLocal API for extending platform\nEnvironment, Web requests to servers\n\n\n9\nVideo playback\nEnvironment\n\n\n10\nSupport for proprietary video hosting\nVideo playback\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nPriority\nFeature\nDependencies\n\n\n\n\n11\nText chat\nEnvironment, Person to person interaction\n\n\n12\nScreen sharing (OBS)\nEnvironment, Person to person interaction\n\n\n13\nModeling and 3D Creation (Blender)\nEnvironment, Static content creation in editor\n\n\n\n\n\n\n\nThe implementation details will be determined once the proposal is accepted and the features are finalized.\n\n\n\n\nA well-structured and prioritized feature list will guide development efforts.\nClear categorization helps manage stakeholder expectations about what will be included in the initial release.\n\n\n\n\n\nSome features may require more time and resources than initially estimated.\nStakeholders may have different opinions on the priority of certain features.\n\n\n\n\nThis section will include any options considered but ultimately rejected during the decision-making process.\n\n\n\nThis question will be addressed during the implementation phase for each feature.\n\n\n\nAs these features form the core functionality of the V-Sekai platform, they should be developed by our team to ensure quality and consistency.\n\n\n\n\nV-Sekai"
+    "text": "Agent Type\nResources\nEnvironments\n\n\n\n\ngocd-agent-59dbf9989-vp4d66\nlinux, mingw5\ndevelopment, itch-fire\n\n\ngocd-agent-dind-96575468d4-s29l2\ndind\ndevelopment, itch-fire\n\n\ngocd-agent-59dbf9989-cczqj\nlinux, mingw5\ndevelopment, itch-fire\n\n\ngocd-agent-59dbf9989-p6vs5\nlinux, mingw5\ndevelopment, itch-fire\n\n\ngocd-agent-59dbf9989-t4ckd\nlinux, mingw5\ndevelopment, itch-fire\n\n\ngocd-agent-dind-96575468d4-b6gq9\ndind\ndevelopment, itch-fire\n\n\n\nPlease note that the actual resources and environments will vary based on your specific setup."
   },
   {
-    "objectID": "decisions/20230701-vsekai-broken-down-goals.html#metadata",
-    "href": "decisions/20230701-vsekai-broken-down-goals.html#metadata",
-    "title": "Proposed: V-Sekai Feature Enhancement Proposal",
+    "objectID": "decisions/20230419-package-godot-for-pkgin.html",
+    "href": "decisions/20230419-package-godot-for-pkgin.html",
+    "title": "Rejected: Package Godot for pkgin",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, ai summarized"
+    "text": "Rejected: Package Godot for pkgin\n\nMetadata\n\nStatus: rejected \nDeciders: V-Sekai,fire,\nTags: V-Sekai,chatgpt4,\n\n\n\nContext and Problem Statement\nAccording to Netflix, the BSD-type operating systems are competitive, and supporting pkgsrc is an excellent way to start.\n\npkgsrc is a framework for managing third-party software on UNIX-like systems containing over 26,000 packages. It is the default package manager of NetBSD and SmartOS and can be used to enable freely available software to be built quickly on a large number of other UNIX-like platforms.\n\n\nV-Sekai is developing a free, open-source virtual reality platform. We work to make it user-friendly and fulfill a need in the VR community.\n\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\n\nEffortless installation and updates: Packaging Godot Engine for pkgin makes it easier to install and update the software on macOS, Linux, and NetBSD, offering a smooth experience for users at all expertise levels.\nWider platform support: By embracing pkgsrc and packaging Godot Engine for pkgin, compatibility with an array of UNIX-like systems is ensured, broadening the user base and fostering adoption across different platforms.\nPromoting cooperation: V-Sekai’s support for pkgsrc and packaging of the Godot Engine for pkgin enables collaboration through the vast third-party software ecosystem available for UNIX-like systems, stimulating the exchange of ideas and resources.\nReinforcing open-source ideals: V-Sekai’s decision to package the Godot Engine for pkgin strengthens its commitment to open-source values like accessibility, transparency, and community-driven development, enhancing growth within the VR community.\n\n\n\nDescribe how your proposal will work with code, pseudo-code, mock-ups, or diagrams\ngraph LR\nA[Godot Engine Source Code] --&gt; B[Build and Package]\nB --&gt; C[Godot Engine pkgin Package]\nC --&gt; D{Platform Compatibility}\nD --&gt; E[macOS]\nD --&gt; F[Linux]\nD --&gt; G[NetBSD]\nC --&gt; H[Package Repository]\nI[User] --&gt; J[pkgin command]\nJ --&gt; H\nH --&gt; K[Install/Update Godot Engine]\nK --&gt; I\n\n\nPositive Consequences\n\nEasy installation and updates: Pkgin support simplifies installing and updating the Godot Engine on UNIX-like systems, such as macOS, Linux, and NetBSD, providing a hassle-free experience for users.\nWide platform support: Pkgin compatibility ensures that the Godot Engine works seamlessly with multiple UNIX-like systems, expanding the user base and promoting adoption across various platforms.\nEfficient dependency handling: Pkgin automatically manages dependencies, streamlining the installation process and minimizing conflicts or issues due to unmet requirements.\nUniform software environment: Pkgin helps maintain consistency in software versions and configurations, which is crucial for collaboration and reducing the need for troubleshooting.\nConnection to the pkgsrc ecosystem: Supporting pkgin allows users to tap into the extensive third-party software ecosystem for UNIX-like systems, fostering the exchange of ideas and resources within the open-source community.\nResource and time savings: By offering pkgin support, developers can concentrate on enhancing the Godot Engine and V-Sekai’s VR platform features rather than manually managing software installations and updates.\nEmphasizing open-source principles: By endorsing pkgin, both V-Sekai and the Godot Engine reaffirm their commitment to open-source values, such as accessibility, transparency, and community-driven development, fostering growth and collaboration within the VR community.\n\n\n\nNegative Consequences\nThere are some potential downsides to packaging the Godot Engine for pkgin, which include:\nAdditional maintenance work: Supporting pkgin may necessitate regular package updates to ensure compatibility with different systems and to keep up with new Godot Engine versions and features. This could require extra time and resources from the development team.\nIncomplete platform support: Pkgin is designed for UNIX-like systems, but it doesn’t directly cater to users on other platforms, such as Windows. Supporting alternative package managers for non-UNIX platforms may demand extra efforts.\nUser learning curve: Users unfamiliar with pkgin or pkgsrc might need to invest time in learning to use the package manager effectively, which could pose a barrier for some users, particularly those new to UNIX-like systems or with limited package management experience.\nPotential compatibility challenges: While pkgin aims to provide compatibility across various UNIX-like systems, certain configurations or system setups may still pose difficulties. Addressing these issues might require more development and troubleshooting efforts.\nUnnecessary overhead for small projects: For smaller projects or users with minimal requirements, the added features and capabilities provided by pkgin support might be excessive. In such cases, the effort needed to maintain and use a pkgin package could outweigh its benefits.\nDespite these potential downsides, offering pkgin support can bring significant advantages, such as streamlining installation and updates, ensuring compatibility with UNIX-like systems, and promoting collaboration within the open-source community.\n\n\nOption graveyard\nAlternative package managers: While other package managers like apt or yum might have been considered, they may need to provide different compatibility with BSD-type systems than pkgsrc. Pkgin, designed for pkgsrc, is the default package manager for systems like NetBSD and SmartOS, making it the ideal choice.\nManual installation: Requiring users to compile and install Godot Engine manually would complicate the process and be less user-friendly, particularly for novices. This approach could also result in software version inconsistencies and configuration issues, affecting user experience.\nCustom package manager: Developing a custom package manager specifically for V-Sekai’s platform is resource-intensive and duplicates existing package managers’ efforts, such as pkgin, which already offers compatibility with BSD-type systems.\nExclusively focusing on other platforms: By targeting only Linux, macOS, or Windows, V-Sekai would limit its potential user base and overlook the advantages of supporting UNIX-like systems like NetBSD and SmartOS. So instead, packaging Godot Engine for pkgin enables V-Sekai to reach a wider audience using BSD-type operating systems.\n\n\nIf this enhancement will be used infrequently, can it be worked around with a few lines of script?\nUsing a script for Godot Engine may have drawbacks, such as being less user-friendly, requiring more maintenance, having limited compatibility with BSD-type systems, and potentially impacting integration with the pkgsrc ecosystem.\n\n\nIs there a reason why this should be core and done by us?\nPackaging the Godot Engine for pkgin as a core task our team handles ensures quality control, streamlined support, customization, alignment with your platform’s vision, and trust-building with users. These factors contribute to the overall success and adoption of your open-source virtual reality platform.\n\n\nReferences\n\nV-Sekai\nhttps://pkgsrc.joyent.com/"
   },
   {
-    "objectID": "decisions/20230701-vsekai-broken-down-goals.html#context-and-problem-statement",
-    "href": "decisions/20230701-vsekai-broken-down-goals.html#context-and-problem-statement",
-    "title": "Proposed: V-Sekai Feature Enhancement Proposal",
+    "objectID": "decisions/20211005-bridge-music-to-xr.html",
+    "href": "decisions/20211005-bridge-music-to-xr.html",
+    "title": "Proposed: Music is important to human experience and should be bridged to XR",
     "section": "",
-    "text": "We are developing a virtual reality platform, V-Sekai. To ensure the platform meets user needs and expectations, we have identified several features that need to be implemented. These features have been categorized based on their priority and necessity for the initial release."
+    "text": "Proposed: Music is important to human experience and should be bridged to XR\n\nContext and Problem Statement\nMusic is important to human experience\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nBridge membrane given a video file play to on a website.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nNo idea\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nRTSP -&gt; #website\n\n\nPositive Consequences\n\nCreate know how for video rooms\n\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nUseful to bridge into other things.\n\n\nReferences\n\nhttps://github.com/ROZ-MOFUMOFU-ME/TopazBot\nhttps://github.com/membraneframework/membrane_rtc_engine\nhttps://github.com/membraneframework/membrane_rtsp\nhttps://github.com/membraneframework/membrane_rtp_plugin\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230701-vsekai-broken-down-goals.html#proposed-solution",
-    "href": "decisions/20230701-vsekai-broken-down-goals.html#proposed-solution",
-    "title": "Proposed: V-Sekai Feature Enhancement Proposal",
+    "objectID": "decisions/20230310-don't-merge-incomplete-work.html",
+    "href": "decisions/20230310-don't-merge-incomplete-work.html",
+    "title": "Proposed: Don’t merge incomplete work.",
     "section": "",
-    "text": "The features have been organized into three categories: Must-Have, Nice-to-Have, and Out of Scope Initially. The priority within each category reflects the relative importance of the features for an initial release.\n\n\n\n\n\n\n\n\n\n\nPriority\nFeature\nDependencies\n\n\n\n\n1\nEnvironment (scene loading, world hosting, instancing)\nNone\n\n\n2\nWeb requests to servers (HTTP/WebSocket API)\nEnvironment\n\n\n3\nPerson to person interaction (avatars, animation, synchronization)\nEnvironment\n\n\n4\nInteraction with the world (interactive elements, physics)\nEnvironment\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nPriority\nFeature\nDependencies\n\n\n\n\n5\nCollaboration features (doodling, modeling, content loading)\nEnvironment, Person to person interaction\n\n\n6\nStatic content creation in editor (import avatars, create worlds)\nEnvironment\n\n\n7\nShareable content (inventory)\nEnvironment, Static content creation in editor\n\n\n8\nLocal API for extending platform\nEnvironment, Web requests to servers\n\n\n9\nVideo playback\nEnvironment\n\n\n10\nSupport for proprietary video hosting\nVideo playback\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nPriority\nFeature\nDependencies\n\n\n\n\n11\nText chat\nEnvironment, Person to person interaction\n\n\n12\nScreen sharing (OBS)\nEnvironment, Person to person interaction\n\n\n13\nModeling and 3D Creation (Blender)\nEnvironment, Static content creation in editor"
+    "text": "Proposed: Don’t merge incomplete work.\n\nV-Sekai version\nlatest on 2022-06-05\n\n\nSystem information\nWin 11, Vulkan, Nvidia 3000\n\n\nIssue description\nDon’t merge changes when the tests or the compile fails.\n\n\nSteps to reproduce\n\nPush a build\nIt fails\nBuild is broken\n\n\n\nMinimal reproduction project\nV-Sekai project."
   },
   {
-    "objectID": "decisions/20230701-vsekai-broken-down-goals.html#implementation",
-    "href": "decisions/20230701-vsekai-broken-down-goals.html#implementation",
-    "title": "Proposed: V-Sekai Feature Enhancement Proposal",
+    "objectID": "decisions/20220605-gocd-pipeline-reset.html",
+    "href": "decisions/20220605-gocd-pipeline-reset.html",
+    "title": "Accepted: To avoid git submodule but recreate the gocd pipelines",
     "section": "",
-    "text": "The implementation details will be determined once the proposal is accepted and the features are finalized."
+    "text": "Accepted: To avoid git submodule but recreate the gocd pipelines\n\nDescribe the status of the issue.\n\nproposed\ndraft\nrejected\naccepted\ndeprecated\nsuperseded by\n\n\n\nList the deciders of the issue.\nV-Sekai,fire,\n\n\nDescribe the tags of the issue.\nV-Sekai,gocd,\n\n\nContext and Problem Statement\nGocd git submodule failed to load.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nReset the gocd pipeline by renaming the initial pipeline name.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\n\nclone https://github.com/V-Sekai/groups-gocd-pipelines\nModify https://github.com/V-Sekai/groups-gocd-pipelines/blob/master/src/godot_4_x.jsonnet\ngodot_template_groups_editor to have increment the revision number.\n./bin/generate\ncommit to git\n\n\n\nPositive Consequences\nAble to build again.\n\n\nNegative Consequences\nIncreases cache size.\n\n\nOption graveyard\nNo response\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nIt is a few lines of script.\n\n\nIs there a reason why this should be core and done by us?\nIt’s our release process.\n\n\nReferences\n\nV-Sekai\n\n\n\nLicense of the contribution\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230701-vsekai-broken-down-goals.html#positive-consequences",
-    "href": "decisions/20230701-vsekai-broken-down-goals.html#positive-consequences",
-    "title": "Proposed: V-Sekai Feature Enhancement Proposal",
+    "objectID": "decisions/20221014-networking-overhaul-proposal.html",
+    "href": "decisions/20221014-networking-overhaul-proposal.html",
+    "title": "Draft: Networking Overhaul",
     "section": "",
-    "text": "A well-structured and prioritized feature list will guide development efforts.\nClear categorization helps manage stakeholder expectations about what will be included in the initial release."
+    "text": "Status: draft\nDeciders: V-Sekai, Malek, Lyuma, SaracenOne, Fire,\nTags: Networking,\n\n\n\nWe seek to solve these issues:\n\n(A) Use godot 4.0’s networking tools.\n(B) Use a relay server that doesn’t run any game code, rather than a headless V-Sekai server.\n(C) Make the costs of hosting V-Sekai as small as possible.\n(D) Write the server in Rust, for the speed and safety guarantees.\n(E) Make networking highly scalable for a single server.\n(F) Allow a client to connect to multiple servers simultaneously without issues, for seamless travel and portals.\n(G) Synchronize state between clients\n\nNote: This proposal does not cover Permissions, and is based in part on the previous Entity Networking proposal.\n\n\n\nBy using the technologies described below, we will cover A-G.\n\n\n\n\n\nTo reduce complexity, latency, and processing power, we have created a simple Mastership/Ownership model.\nClients are defined as individuals connecting to a Server, they have their own v-sekai game instance running.\nThe Relay Server, as of now, does not contain information about the state of the world, the only information the Relay Server contains is on Mastership/Ownership rules.\nP1 connects to the Server.\n\nP2 connects to the Server.\n\nP3 connects to the Server.\n\nP1 spawns in a Ball.\n\nServer marks that P1 has both Mastership and Ownership of Ball.\n\nServer synchronizes with P1 and sends the state of the Ball to P2, its location, rotation, the very fact of its existence, and its owner, master, and rule.\n\nServer State\n\n\n\nObjects\nMaster\nOwner\nRule\n\n\n\n\nBall\nP1\nP1\nAsk\n\n\n\nWhat does this mean?\n\n\nSince P1 is the Owner of the Ball, this means that P1 is the only one who can change the state of the ball. When Server synchronizes, if P2 were to have the ball in a different location then P1, the Server would tell P2 that the Ball is in the location P1 has it, and would do the same for P3. It can be thought of as a mutex on the state of the Ball. Whoever holds the Mutex is the one who can modify the state therein. This also means that all calculations for game state are split up among all the players, every player only has to run code modifying what they own, which in large scale player events would otherwise increase exponentially with custom scripts for each player’s props or avatars.\n\n\n\nThis presents a problem however, how could P2 take the Ball from P1? The solution is Mastership. Whoever is the Master can change who is the Owner at any time. The Master also can change whatever the default Rule is, which is what the Server, and Client references when looking to change Ownership to itself (or someone else?).\n\nAsk: Take a round trip to the Master and back to the Server so the Master can decide based on external factors whether or not to allow ownership transfer or deny it. This could be used for example, if someone only wants a gun to be grabbable if they are a “shooter” and not if they are a “civilian”\nDeny: You cannot ask for ownership transfer, good for things like Avatar’s transform node, you don’t wanna be involuntarily moved around, or for the root of the world map.\nAllow: You can ask for ownership any time, and it is automatically granted.\n\n\n\n\n\nWe can change the rate of synchronization based on the closest clients owned model, and other things like that, there are a lot of areas for optimization when it comes to using this.\n\n\n\n\n\nLow Latency for Competitive/Real-Time interactions\nLow processing power on both the server and client side\nBroad enough to be easily modifiable for optimizations in the future without changing the model\n\n\n\n\n\nComplexity, we will have to code this all from scratch basically\nMulti-user interactions become impossible on a single object, at least to do simply, some smart coding could get around it but it isn’t easy to do.\nResolutions for the allow rule could lead to inconsistencies, such as two different people picking up a gun and firing it, and two resulting bullets being spawned from the same gun before it gets removed from one individual.\n\n\n\n\nAbsolutely, this is the foundation of basically everything content wise in V-sekai.\n\n\n\nhttps://github.com/V-Sekai/V-Sekai.github.io/blob/master/decisions/2020/20200729-entity-networking.md\nMalek’s forum post on networking in the Discord server.\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230701-vsekai-broken-down-goals.html#negative-consequences",
-    "href": "decisions/20230701-vsekai-broken-down-goals.html#negative-consequences",
-    "title": "Proposed: V-Sekai Feature Enhancement Proposal",
+    "objectID": "decisions/20221014-networking-overhaul-proposal.html#context-and-problem-statement",
+    "href": "decisions/20221014-networking-overhaul-proposal.html#context-and-problem-statement",
+    "title": "Draft: Networking Overhaul",
     "section": "",
-    "text": "Some features may require more time and resources than initially estimated.\nStakeholders may have different opinions on the priority of certain features."
+    "text": "We seek to solve these issues:\n\n(A) Use godot 4.0’s networking tools.\n(B) Use a relay server that doesn’t run any game code, rather than a headless V-Sekai server.\n(C) Make the costs of hosting V-Sekai as small as possible.\n(D) Write the server in Rust, for the speed and safety guarantees.\n(E) Make networking highly scalable for a single server.\n(F) Allow a client to connect to multiple servers simultaneously without issues, for seamless travel and portals.\n(G) Synchronize state between clients\n\nNote: This proposal does not cover Permissions, and is based in part on the previous Entity Networking proposal."
   },
   {
-    "objectID": "decisions/20230701-vsekai-broken-down-goals.html#option-graveyard",
-    "href": "decisions/20230701-vsekai-broken-down-goals.html#option-graveyard",
-    "title": "Proposed: V-Sekai Feature Enhancement Proposal",
+    "objectID": "decisions/20221014-networking-overhaul-proposal.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20221014-networking-overhaul-proposal.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Draft: Networking Overhaul",
     "section": "",
-    "text": "This section will include any options considered but ultimately rejected during the decision-making process."
+    "text": "By using the technologies described below, we will cover A-G."
   },
   {
-    "objectID": "decisions/20230701-vsekai-broken-down-goals.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230701-vsekai-broken-down-goals.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: V-Sekai Feature Enhancement Proposal",
+    "objectID": "decisions/20221014-networking-overhaul-proposal.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-andor-diagrams",
+    "href": "decisions/20221014-networking-overhaul-proposal.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-andor-diagrams",
+    "title": "Draft: Networking Overhaul",
     "section": "",
-    "text": "This question will be addressed during the implementation phase for each feature."
+    "text": "To reduce complexity, latency, and processing power, we have created a simple Mastership/Ownership model.\nClients are defined as individuals connecting to a Server, they have their own v-sekai game instance running.\nThe Relay Server, as of now, does not contain information about the state of the world, the only information the Relay Server contains is on Mastership/Ownership rules.\nP1 connects to the Server.\n\nP2 connects to the Server.\n\nP3 connects to the Server.\n\nP1 spawns in a Ball.\n\nServer marks that P1 has both Mastership and Ownership of Ball.\n\nServer synchronizes with P1 and sends the state of the Ball to P2, its location, rotation, the very fact of its existence, and its owner, master, and rule.\n\nServer State\n\n\n\nObjects\nMaster\nOwner\nRule\n\n\n\n\nBall\nP1\nP1\nAsk\n\n\n\nWhat does this mean?\n\n\nSince P1 is the Owner of the Ball, this means that P1 is the only one who can change the state of the ball. When Server synchronizes, if P2 were to have the ball in a different location then P1, the Server would tell P2 that the Ball is in the location P1 has it, and would do the same for P3. It can be thought of as a mutex on the state of the Ball. Whoever holds the Mutex is the one who can modify the state therein. This also means that all calculations for game state are split up among all the players, every player only has to run code modifying what they own, which in large scale player events would otherwise increase exponentially with custom scripts for each player’s props or avatars.\n\n\n\nThis presents a problem however, how could P2 take the Ball from P1? The solution is Mastership. Whoever is the Master can change who is the Owner at any time. The Master also can change whatever the default Rule is, which is what the Server, and Client references when looking to change Ownership to itself (or someone else?).\n\nAsk: Take a round trip to the Master and back to the Server so the Master can decide based on external factors whether or not to allow ownership transfer or deny it. This could be used for example, if someone only wants a gun to be grabbable if they are a “shooter” and not if they are a “civilian”\nDeny: You cannot ask for ownership transfer, good for things like Avatar’s transform node, you don’t wanna be involuntarily moved around, or for the root of the world map.\nAllow: You can ask for ownership any time, and it is automatically granted.\n\n\n\n\n\nWe can change the rate of synchronization based on the closest clients owned model, and other things like that, there are a lot of areas for optimization when it comes to using this."
   },
   {
-    "objectID": "decisions/20230701-vsekai-broken-down-goals.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230701-vsekai-broken-down-goals.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: V-Sekai Feature Enhancement Proposal",
+    "objectID": "decisions/20221014-networking-overhaul-proposal.html#positive-consequences-list",
+    "href": "decisions/20221014-networking-overhaul-proposal.html#positive-consequences-list",
+    "title": "Draft: Networking Overhaul",
     "section": "",
-    "text": "As these features form the core functionality of the V-Sekai platform, they should be developed by our team to ensure quality and consistency."
+    "text": "Low Latency for Competitive/Real-Time interactions\nLow processing power on both the server and client side\nBroad enough to be easily modifiable for optimizations in the future without changing the model"
   },
   {
-    "objectID": "decisions/20230701-vsekai-broken-down-goals.html#references",
-    "href": "decisions/20230701-vsekai-broken-down-goals.html#references",
-    "title": "Proposed: V-Sekai Feature Enhancement Proposal",
+    "objectID": "decisions/20221014-networking-overhaul-proposal.html#negative-consequences-list",
+    "href": "decisions/20221014-networking-overhaul-proposal.html#negative-consequences-list",
+    "title": "Draft: Networking Overhaul",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Complexity, we will have to code this all from scratch basically\nMulti-user interactions become impossible on a single object, at least to do simply, some smart coding could get around it but it isn’t easy to do.\nResolutions for the allow rule could lead to inconsistencies, such as two different people picking up a gun and firing it, and two resulting bullets being spawned from the same gun before it gets removed from one individual."
   },
   {
-    "objectID": "decisions/20210811-game-workflow-membrane.html",
-    "href": "decisions/20210811-game-workflow-membrane.html",
-    "title": "Proposed: Membrane Framework to Process Game Workflows",
+    "objectID": "decisions/20221014-networking-overhaul-proposal.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20221014-networking-overhaul-proposal.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Draft: Networking Overhaul",
     "section": "",
-    "text": "Proposed: Membrane Framework to Process Game Workflows\n\nContext and Problem Statement\nUse a workflow tool to process game things.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nMembrane is a workflow tool and can be used to orchestrate Blender.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nModify Blender input\nStretch goal. Push from Blender Mixer to Godot Engine.\n\nAutomatic correct skeleton mesh skinning for VRMs.\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot a few lines of code because it orchestrates multiple tools.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nNeeded to be done by us.\n\n\nReferences\n\nhttps://www.membraneframework.org/\nhttps://github.com/Pyrlang/Pyrlang\nhttp://www.wings3d.com/\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Absolutely, this is the foundation of basically everything content wise in V-sekai."
   },
   {
-    "objectID": "decisions/20211031-face-motion-tracking-requires-standard-shapes.html",
-    "href": "decisions/20211031-face-motion-tracking-requires-standard-shapes.html",
-    "title": "Proposed: Face motion tracking requires standard shapes",
+    "objectID": "decisions/20221014-networking-overhaul-proposal.html#references",
+    "href": "decisions/20221014-networking-overhaul-proposal.html#references",
+    "title": "Draft: Networking Overhaul",
     "section": "",
-    "text": "Proposed: Face motion tracking requires standard shapes\n\nContext and Problem Statement\nMake VRM faces sync with Perfectsync, SRanipal or Mediapipe faces.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nPeople use many standard types of face definitions.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n???\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot trivial.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nIt is a dependency of doing VR avatars.\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "https://github.com/V-Sekai/V-Sekai.github.io/blob/master/decisions/2020/20200729-entity-networking.md\nMalek’s forum post on networking in the Discord server."
   },
   {
-    "objectID": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html",
-    "href": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html",
-    "title": "Accepted: Stabilize Godot Engine updates by delaying to 2 week cycles",
+    "objectID": "decisions/20221014-networking-overhaul-proposal.html#derivative-license",
+    "href": "decisions/20221014-networking-overhaul-proposal.html#derivative-license",
+    "title": "Draft: Networking Overhaul",
     "section": "",
-    "text": "Status: accepted \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nStabilize Godot Engine updates because the update broke Groups broke once.\n\n\n\nWe use multiple ways to harden Godot Engine.\n\n\n\n\nDelay to around 2 week cycles\nMove V-Sekai godot to use a branch that is not tracked with Godot Engine master.\n\n\n\n\n\nMore stability\n\n\n\n\n\nLosing the pulse of Godot Engine development.\n\n\n\n\n\nOption: \nRejection Reason: \n\n\n\n\nNot a few lines of script in core.\n\n\n\nWe maintain the engine.\n\n\n\n\nhttps://godotengine.org\n\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html#context-and-problem-statement",
-    "href": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html#context-and-problem-statement",
-    "title": "Accepted: Stabilize Godot Engine updates by delaying to 2 week cycles",
+    "objectID": "decisions/20240622-process-for-testing-vsekai.html",
+    "href": "decisions/20240622-process-for-testing-vsekai.html",
+    "title": "Proposed: Create a process for testing V-Sekai.",
     "section": "",
-    "text": "Stabilize Godot Engine updates because the update broke Groups broke once."
+    "text": "We’re making V-Sekai, an immersive VR game that brings social VR/VRSNS/metaverse components to the Godot Engine.\n\n\n\nSometimes our flow doesn’t work and we can’t play the game because we broke the script.\nWe want to introduce automated testing to make it easier to debug.\n\n\n\nWe propose to use a test-driven development (TDD) approach.\n\n\n\n\nReduced time spent on debugging.\nIncreased confidence in the stability of the game.\nFaster development cycle as bugs are caught early.\n\n\n\n\n\nInitial setup of automated testing can be time-consuming.\nTests need to be maintained and updated as the game evolves.\n\n\n\n\nWe could continue without automated testing, but this could lead to more time spent on debugging and less time on developing new features.\n\n\n\nIn cases where new features are added infrequently, the overhead of maintaining tests might outweigh the benefits.\n\n\n\nThe testing framework would be part of the core game engine and maintained by us, the V-Sekai development team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\nAutomated Testing\nGame Development\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Accepted: Stabilize Godot Engine updates by delaying to 2 week cycles",
+    "objectID": "decisions/20240622-process-for-testing-vsekai.html#the-context",
+    "href": "decisions/20240622-process-for-testing-vsekai.html#the-context",
+    "title": "Proposed: Create a process for testing V-Sekai.",
     "section": "",
-    "text": "We use multiple ways to harden Godot Engine."
+    "text": "We’re making V-Sekai, an immersive VR game that brings social VR/VRSNS/metaverse components to the Godot Engine."
   },
   {
-    "objectID": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Accepted: Stabilize Godot Engine updates by delaying to 2 week cycles",
+    "objectID": "decisions/20240622-process-for-testing-vsekai.html#the-problem-statement",
+    "href": "decisions/20240622-process-for-testing-vsekai.html#the-problem-statement",
+    "title": "Proposed: Create a process for testing V-Sekai.",
     "section": "",
-    "text": "Delay to around 2 week cycles\nMove V-Sekai godot to use a branch that is not tracked with Godot Engine master."
+    "text": "Sometimes our flow doesn’t work and we can’t play the game because we broke the script.\nWe want to introduce automated testing to make it easier to debug."
   },
   {
-    "objectID": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html#positive-consequences",
-    "href": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html#positive-consequences",
-    "title": "Accepted: Stabilize Godot Engine updates by delaying to 2 week cycles",
+    "objectID": "decisions/20240622-process-for-testing-vsekai.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240622-process-for-testing-vsekai.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Create a process for testing V-Sekai.",
     "section": "",
-    "text": "More stability"
+    "text": "We propose to use a test-driven development (TDD) approach."
   },
   {
-    "objectID": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html#negative-consequences",
-    "href": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html#negative-consequences",
-    "title": "Accepted: Stabilize Godot Engine updates by delaying to 2 week cycles",
+    "objectID": "decisions/20240622-process-for-testing-vsekai.html#the-benefits",
+    "href": "decisions/20240622-process-for-testing-vsekai.html#the-benefits",
+    "title": "Proposed: Create a process for testing V-Sekai.",
     "section": "",
-    "text": "Losing the pulse of Godot Engine development."
+    "text": "Reduced time spent on debugging.\nIncreased confidence in the stability of the game.\nFaster development cycle as bugs are caught early."
   },
   {
-    "objectID": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html#option-graveyard",
-    "href": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html#option-graveyard",
-    "title": "Accepted: Stabilize Godot Engine updates by delaying to 2 week cycles",
+    "objectID": "decisions/20240622-process-for-testing-vsekai.html#the-downsides",
+    "href": "decisions/20240622-process-for-testing-vsekai.html#the-downsides",
+    "title": "Proposed: Create a process for testing V-Sekai.",
     "section": "",
-    "text": "Option: \nRejection Reason:"
+    "text": "Initial setup of automated testing can be time-consuming.\nTests need to be maintained and updated as the game evolves."
   },
   {
-    "objectID": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Accepted: Stabilize Godot Engine updates by delaying to 2 week cycles",
+    "objectID": "decisions/20240622-process-for-testing-vsekai.html#the-road-not-taken",
+    "href": "decisions/20240622-process-for-testing-vsekai.html#the-road-not-taken",
+    "title": "Proposed: Create a process for testing V-Sekai.",
     "section": "",
-    "text": "Not a few lines of script in core."
+    "text": "We could continue without automated testing, but this could lead to more time spent on debugging and less time on developing new features."
   },
   {
-    "objectID": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Accepted: Stabilize Godot Engine updates by delaying to 2 week cycles",
+    "objectID": "decisions/20240622-process-for-testing-vsekai.html#the-infrequent-use-case",
+    "href": "decisions/20240622-process-for-testing-vsekai.html#the-infrequent-use-case",
+    "title": "Proposed: Create a process for testing V-Sekai.",
     "section": "",
-    "text": "We maintain the engine."
+    "text": "In cases where new features are added infrequently, the overhead of maintaining tests might outweigh the benefits."
   },
   {
-    "objectID": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html#references",
-    "href": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html#references",
-    "title": "Accepted: Stabilize Godot Engine updates by delaying to 2 week cycles",
+    "objectID": "decisions/20240622-process-for-testing-vsekai.html#in-core-and-done-by-us",
+    "href": "decisions/20240622-process-for-testing-vsekai.html#in-core-and-done-by-us",
+    "title": "Proposed: Create a process for testing V-Sekai.",
     "section": "",
-    "text": "https://godotengine.org"
+    "text": "The testing framework would be part of the core game engine and maintained by us, the V-Sekai development team."
   },
   {
-    "objectID": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html#derivative-license",
-    "href": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html#derivative-license",
-    "title": "Accepted: Stabilize Godot Engine updates by delaying to 2 week cycles",
+    "objectID": "decisions/20240622-process-for-testing-vsekai.html#status",
+    "href": "decisions/20240622-process-for-testing-vsekai.html#status",
+    "title": "Proposed: Create a process for testing V-Sekai.",
     "section": "",
-    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20230527-server-performance-test.html",
-    "href": "decisions/20230527-server-performance-test.html",
-    "title": "Proposed: Generating Random Text Data for testing V-Sekai systems",
+    "objectID": "decisions/20240622-process-for-testing-vsekai.html#decision-makers",
+    "href": "decisions/20240622-process-for-testing-vsekai.html#decision-makers",
+    "title": "Proposed: Create a process for testing V-Sekai.",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai, Bioblaze Payne, fire\nTags: V-Sekai, GPT-4\n\n\n\n\nV-Sekai is a project that aims to provide an immersive virtual world experience for users. As the project grows in complexity, it becomes increasingly important to ensure that the system is thoroughly tested and can handle various scenarios. One of the challenges faced by the V-Sekai team is the lack of diverse and realistic data for testing purposes. This limitation hinders the ability to identify potential issues and optimize the system’s performance.\n\n\n\nTo address the limitations in testing the V-Sekai system due to the lack of diverse and realistic data, this proposal suggests generating random text data for testing purposes.\n\n\nWe will use a tool like Chance.js library to generate random text data for testing purposes and use the database.\n\n\nFor generating random sentences, we will use something like the following method:\nchance.sentence();\nReference: Chance.js Sentence\n\n\n\nFor generating random user names, we will use something like the following method:\nchance.name();\nReference: Chance.js Name\n\n\n\nWe will perform the following SQL operations on the user and chat tables:\n\nSELECT All Data in Table\nSELECT LIKE Data based on %NA%\nSELECT Specific Row Data\nINSERT\nUPDATE\nDELETE\n\n\n\nTable user\nid | username | password | updated_on | created_on |\nTable chat\nid | user_id | name | text | updated_on | deleted_on | created_on |\n\n\n\n\nWe will create a SQL function to check if the username/password match and return ‘OK’. We will also check if the query returned is ‘OK’ and add false information randomly in the nodes to signify a user doing invalid calls for production testing.\nThe implementation will generate 90 days of data, generating 100,000 text data entries for testing purposes.\n\n\n\n\n\n\nImproved testing capabilities with diverse and realistic data\nEnhanced system reliability due to thorough testing\nIdentification of potential issues before they impact users\n\n\n\n\n\nAdditional development time required to implement the solution\nPotential increase in storage requirements for generated data\n\n\n\n\n\nUsing static test data: This option was considered for simplicity, but it would not provide the diverse and realistic data needed for thorough testing.\nManual data generation: This option involved manually creating test data, but it was deemed time-consuming and inefficient compared to using a library like Chance.js.\nThird-party data generation services: While there are external services that can generate random text data, using them would introduce dependencies and potential costs. Implementing our a solution similar to Chance.js allows for better control over the process.\nCrowdsourcing test data: This option involved gathering test data from users or volunteers. However, it raised concerns about data privacy, consistency, and quality.\n\n\n\n\nNo, this enhancement is essential for thorough testing and cannot be easily worked around with a few lines of script.\n\n\n\nYes, addressing the V-Sekai limitation is crucial for ensuring the system’s reliability and performance. Implementing this solution internally allows for better control over the testing process and data generation.\n\n\n\n\nV-Sekai"
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20230527-server-performance-test.html#metadata",
-    "href": "decisions/20230527-server-performance-test.html#metadata",
-    "title": "Proposed: Generating Random Text Data for testing V-Sekai systems",
+    "objectID": "decisions/20240622-process-for-testing-vsekai.html#tags",
+    "href": "decisions/20240622-process-for-testing-vsekai.html#tags",
+    "title": "Proposed: Create a process for testing V-Sekai.",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai, Bioblaze Payne, fire\nTags: V-Sekai, GPT-4"
+    "text": "V-Sekai\nAutomated Testing\nGame Development"
   },
   {
-    "objectID": "decisions/20230527-server-performance-test.html#context-and-problem-statement",
-    "href": "decisions/20230527-server-performance-test.html#context-and-problem-statement",
-    "title": "Proposed: Generating Random Text Data for testing V-Sekai systems",
+    "objectID": "decisions/20240622-process-for-testing-vsekai.html#further-reading",
+    "href": "decisions/20240622-process-for-testing-vsekai.html#further-reading",
+    "title": "Proposed: Create a process for testing V-Sekai.",
     "section": "",
-    "text": "V-Sekai is a project that aims to provide an immersive virtual world experience for users. As the project grows in complexity, it becomes increasingly important to ensure that the system is thoroughly tested and can handle various scenarios. One of the challenges faced by the V-Sekai team is the lack of diverse and realistic data for testing purposes. This limitation hinders the ability to identify potential issues and optimize the system’s performance."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20230527-server-performance-test.html#proposed-solution",
-    "href": "decisions/20230527-server-performance-test.html#proposed-solution",
-    "title": "Proposed: Generating Random Text Data for testing V-Sekai systems",
+    "objectID": "decisions/20230912-target-most-popular-resolution.html",
+    "href": "decisions/20230912-target-most-popular-resolution.html",
+    "title": "Proposed: Address Screen Resolution Compatibility Issues",
     "section": "",
-    "text": "To address the limitations in testing the V-Sekai system due to the lack of diverse and realistic data, this proposal suggests generating random text data for testing purposes.\n\n\nWe will use a tool like Chance.js library to generate random text data for testing purposes and use the database.\n\n\nFor generating random sentences, we will use something like the following method:\nchance.sentence();\nReference: Chance.js Sentence\n\n\n\nFor generating random user names, we will use something like the following method:\nchance.name();\nReference: Chance.js Name\n\n\n\nWe will perform the following SQL operations on the user and chat tables:\n\nSELECT All Data in Table\nSELECT LIKE Data based on %NA%\nSELECT Specific Row Data\nINSERT\nUPDATE\nDELETE\n\n\n\nTable user\nid | username | password | updated_on | created_on |\nTable chat\nid | user_id | name | text | updated_on | deleted_on | created_on |\n\n\n\n\nWe will create a SQL function to check if the username/password match and return ‘OK’. We will also check if the query returned is ‘OK’ and add false information randomly in the nodes to signify a user doing invalid calls for production testing.\nThe implementation will generate 90 days of data, generating 100,000 text data entries for testing purposes."
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nSeveral users, including Lyuma, have reported that their monitors are not compatible with the V-Sekai menu system. This issue is causing a significant hindrance in the user experience.\n\n\n\n\nUser satisfaction\nCompatibility with various screen resolutions\n\n\n\n\n\nLeave as is\nSet V-Sekai’s screen resolution to fit the default resolution of the Valve hardware survey’s most popular resolution.\n\n\n\n\nChosen option: “Set V-Sekai’s screen resolution to fit the default resolution of the Valve hardware survey’s most popular resolution.”, because it will increase compatibility and improve user experience.\n\n\n\n\n\n\nGood, because it increases compatibility with the majority of users’ monitors.\nBad, because it may not cover all possible monitor resolutions, leaving some users still facing issues.\n\n\n\n\n\nGood, because it requires no additional work or changes.\nBad, because it does not solve the problem and leaves users frustrated.\n\n\n\n\n\n\nV-Sekai\nThis article is assisted by AI."
   },
   {
-    "objectID": "decisions/20230527-server-performance-test.html#positive-consequences",
-    "href": "decisions/20230527-server-performance-test.html#positive-consequences",
-    "title": "Proposed: Generating Random Text Data for testing V-Sekai systems",
+    "objectID": "decisions/20230912-target-most-popular-resolution.html#metadata",
+    "href": "decisions/20230912-target-most-popular-resolution.html#metadata",
+    "title": "Proposed: Address Screen Resolution Compatibility Issues",
     "section": "",
-    "text": "Improved testing capabilities with diverse and realistic data\nEnhanced system reliability due to thorough testing\nIdentification of potential issues before they impact users"
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20230527-server-performance-test.html#negative-consequences",
-    "href": "decisions/20230527-server-performance-test.html#negative-consequences",
-    "title": "Proposed: Generating Random Text Data for testing V-Sekai systems",
+    "objectID": "decisions/20230912-target-most-popular-resolution.html#context-and-problem-statement",
+    "href": "decisions/20230912-target-most-popular-resolution.html#context-and-problem-statement",
+    "title": "Proposed: Address Screen Resolution Compatibility Issues",
     "section": "",
-    "text": "Additional development time required to implement the solution\nPotential increase in storage requirements for generated data"
+    "text": "Several users, including Lyuma, have reported that their monitors are not compatible with the V-Sekai menu system. This issue is causing a significant hindrance in the user experience."
   },
   {
-    "objectID": "decisions/20230527-server-performance-test.html#option-graveyard",
-    "href": "decisions/20230527-server-performance-test.html#option-graveyard",
-    "title": "Proposed: Generating Random Text Data for testing V-Sekai systems",
+    "objectID": "decisions/20230912-target-most-popular-resolution.html#decision-drivers",
+    "href": "decisions/20230912-target-most-popular-resolution.html#decision-drivers",
+    "title": "Proposed: Address Screen Resolution Compatibility Issues",
     "section": "",
-    "text": "Using static test data: This option was considered for simplicity, but it would not provide the diverse and realistic data needed for thorough testing.\nManual data generation: This option involved manually creating test data, but it was deemed time-consuming and inefficient compared to using a library like Chance.js.\nThird-party data generation services: While there are external services that can generate random text data, using them would introduce dependencies and potential costs. Implementing our a solution similar to Chance.js allows for better control over the process.\nCrowdsourcing test data: This option involved gathering test data from users or volunteers. However, it raised concerns about data privacy, consistency, and quality."
+    "text": "User satisfaction\nCompatibility with various screen resolutions"
   },
   {
-    "objectID": "decisions/20230527-server-performance-test.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230527-server-performance-test.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Generating Random Text Data for testing V-Sekai systems",
+    "objectID": "decisions/20230912-target-most-popular-resolution.html#considered-options",
+    "href": "decisions/20230912-target-most-popular-resolution.html#considered-options",
+    "title": "Proposed: Address Screen Resolution Compatibility Issues",
     "section": "",
-    "text": "No, this enhancement is essential for thorough testing and cannot be easily worked around with a few lines of script."
+    "text": "Leave as is\nSet V-Sekai’s screen resolution to fit the default resolution of the Valve hardware survey’s most popular resolution."
   },
   {
-    "objectID": "decisions/20230527-server-performance-test.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230527-server-performance-test.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Generating Random Text Data for testing V-Sekai systems",
+    "objectID": "decisions/20230912-target-most-popular-resolution.html#decision-outcome",
+    "href": "decisions/20230912-target-most-popular-resolution.html#decision-outcome",
+    "title": "Proposed: Address Screen Resolution Compatibility Issues",
     "section": "",
-    "text": "Yes, addressing the V-Sekai limitation is crucial for ensuring the system’s reliability and performance. Implementing this solution internally allows for better control over the testing process and data generation."
+    "text": "Chosen option: “Set V-Sekai’s screen resolution to fit the default resolution of the Valve hardware survey’s most popular resolution.”, because it will increase compatibility and improve user experience."
   },
   {
-    "objectID": "decisions/20230527-server-performance-test.html#references",
-    "href": "decisions/20230527-server-performance-test.html#references",
-    "title": "Proposed: Generating Random Text Data for testing V-Sekai systems",
+    "objectID": "decisions/20230912-target-most-popular-resolution.html#pros-and-cons-of-the-options",
+    "href": "decisions/20230912-target-most-popular-resolution.html#pros-and-cons-of-the-options",
+    "title": "Proposed: Address Screen Resolution Compatibility Issues",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Good, because it increases compatibility with the majority of users’ monitors.\nBad, because it may not cover all possible monitor resolutions, leaving some users still facing issues.\n\n\n\n\n\nGood, because it requires no additional work or changes.\nBad, because it does not solve the problem and leaves users frustrated."
   },
   {
-    "objectID": "decisions/20210212-use-markdown-architectural-decision-records.html",
-    "href": "decisions/20210212-use-markdown-architectural-decision-records.html",
-    "title": "Accepted: Use Markdown Architectural Decision Records",
+    "objectID": "decisions/20230912-target-most-popular-resolution.html#links",
+    "href": "decisions/20230912-target-most-popular-resolution.html#links",
+    "title": "Proposed: Address Screen Resolution Compatibility Issues",
     "section": "",
-    "text": "Status: accepted\nDate: 2021-02-11\nTags: doc\n\n\n\nWe want to record architectural decisions made in this project. Which format and structure should these records follow?\n\n\n\n\nMADR 2.1.2 with Log4brains patch\nMADR 2.1.2 – The original Markdown Architectural Decision Records\nMichael Nygard’s template – The first incarnation of the term “ADR”\nSustainable Architectural Decisions – The Y-Statements\nOther templates listed at https://github.com/joelparkerhenderson/architecture_decision_record\nFormless – No conventions for file format and structure\n\n\n\n\nChosen option: “MADR 2.1.2 with Log4brains patch”, because\n\nImplicit assumptions should be made explicit. Design documentation is important to enable people understanding the decisions later on. See also A rational design process: How and why to fake it.\nThe MADR format is lean and fits our development style.\nThe MADR structure is comprehensible and facilitates usage & maintenance.\nThe MADR project is vivid.\nVersion 2.1.2 is the latest one available when starting to document ADRs.\nThe Log4brains patch adds more features, like tags.\n\nThe “Log4brains patch” performs the following modifications to the original template:\n\nChange the ADR filenames format (NNN-adr-name becomes YYYYMMDD-adr-name), to avoid conflicts during Git merges.\nAdd a draft status, to enable collaborative writing.\nAdd a Tags field.\n\n\n\n\n\nRelates to Use Log4brains to manage the ADRs\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "V-Sekai\nThis article is assisted by AI."
   },
   {
-    "objectID": "decisions/20210212-use-markdown-architectural-decision-records.html#context-and-problem-statement",
-    "href": "decisions/20210212-use-markdown-architectural-decision-records.html#context-and-problem-statement",
-    "title": "Accepted: Use Markdown Architectural Decision Records",
+    "objectID": "decisions/20221206-export-godot-vrm-to-the-asset-library.html",
+    "href": "decisions/20221206-export-godot-vrm-to-the-asset-library.html",
+    "title": "Proposed: Prepare godot-vrm for asset library publishing",
     "section": "",
-    "text": "We want to record architectural decisions made in this project. Which format and structure should these records follow?"
+    "text": "Status: accepted \nDeciders: V-Sekai,lyuma,fire,\nTags: V-Sekai,\n\n\n\n\nWe want to prepare godot-vrm for asset library publishing, but the format for publishing is incompatible with development.\n\n\n\nWe convert godot-vrm into a format suitable for development and then write a converter to a format ready for the asset library.\n\n\n\nHow to migrate to Godot-VRM to submodule format?\nThe thing Lyuma got blocked on is that VRM contains two addons: VRM and Godot-MToon-Shader\nRevive the Godot-MToon-Shader repository which Lyuma previously archived.\nBut Lyuma will change it so it’s only the submodule (contents of the addons folder) and then Lyuma will make the Godot VRM addon (submodule) a branch in the godot-vrm repository\nThen we’ll make a script to sync the changes to/from the godot-vrm example project which we submit to asset lib\nWriting this up for Fire, since we talked about the issue with addons/vrm being duplicated in multiple projects since Godot Asset Library doesn’t allow submodules / raw addons folders.\nDid some unarchiving and renames so that https://github.com/V-Sekai/Godot-MToon-Shader gets the top google slot\n\nMake sure the godot-vrm code is synced up with other repositories where it was duplicated.\nMake a mtoon addon repository with a copy of the Godot-MToon-Shader code.\nMake a branch in godot-vrm with ONLY the 4.0 vrm addon, usable as a submodule.\nChange v-sekai-game and other similar projects to use Godot-MToon-Shader and vrm as a submodules\nWrite a script to sync up repository contents from one to the other.\n\n\n\nIs there a functional difference between if not stringvar.is_empty(): vs if stringvar != \"\": x != “” is a bit shorter and easier to type, but I noticed some recommendation to use is_empty().\n\n\n\n\nWe don’t have duplicate godot-vrm copies and the copies stay in sync.\n\n\n\nAsset library copy is different than development.\n\n\n\n\nOption: The status quo. \nRejection Reason: This solves nothing. We have duplicate development versions. \n\n\n\n\nThis is a repository layout and not code.\n\n\n\nWe own the godot-vrm and the mtoon repositories.\n\n\n\n\nV-Sekai\n\n\n\n\nMIT License\n\nCopyright (c) 2018-2022 SaracenOne\nCopyright (c) 2019-2022 K. S. Ernest (iFire) Lee (fire)\nCopyright (c) 2020-2022 Lyuma\nCopyright (c) 2020-2022 MMMaellon\nCopyright (c) 2022 V-Sekai Contributors\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
   },
   {
-    "objectID": "decisions/20210212-use-markdown-architectural-decision-records.html#considered-options",
-    "href": "decisions/20210212-use-markdown-architectural-decision-records.html#considered-options",
-    "title": "Accepted: Use Markdown Architectural Decision Records",
+    "objectID": "decisions/20221206-export-godot-vrm-to-the-asset-library.html#context-and-problem-statement",
+    "href": "decisions/20221206-export-godot-vrm-to-the-asset-library.html#context-and-problem-statement",
+    "title": "Proposed: Prepare godot-vrm for asset library publishing",
     "section": "",
-    "text": "MADR 2.1.2 with Log4brains patch\nMADR 2.1.2 – The original Markdown Architectural Decision Records\nMichael Nygard’s template – The first incarnation of the term “ADR”\nSustainable Architectural Decisions – The Y-Statements\nOther templates listed at https://github.com/joelparkerhenderson/architecture_decision_record\nFormless – No conventions for file format and structure"
+    "text": "We want to prepare godot-vrm for asset library publishing, but the format for publishing is incompatible with development."
   },
   {
-    "objectID": "decisions/20210212-use-markdown-architectural-decision-records.html#decision-outcome",
-    "href": "decisions/20210212-use-markdown-architectural-decision-records.html#decision-outcome",
-    "title": "Accepted: Use Markdown Architectural Decision Records",
+    "objectID": "decisions/20221206-export-godot-vrm-to-the-asset-library.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20221206-export-godot-vrm-to-the-asset-library.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: Prepare godot-vrm for asset library publishing",
     "section": "",
-    "text": "Chosen option: “MADR 2.1.2 with Log4brains patch”, because\n\nImplicit assumptions should be made explicit. Design documentation is important to enable people understanding the decisions later on. See also A rational design process: How and why to fake it.\nThe MADR format is lean and fits our development style.\nThe MADR structure is comprehensible and facilitates usage & maintenance.\nThe MADR project is vivid.\nVersion 2.1.2 is the latest one available when starting to document ADRs.\nThe Log4brains patch adds more features, like tags.\n\nThe “Log4brains patch” performs the following modifications to the original template:\n\nChange the ADR filenames format (NNN-adr-name becomes YYYYMMDD-adr-name), to avoid conflicts during Git merges.\nAdd a draft status, to enable collaborative writing.\nAdd a Tags field."
+    "text": "We convert godot-vrm into a format suitable for development and then write a converter to a format ready for the asset library."
   },
   {
-    "objectID": "decisions/20210212-use-markdown-architectural-decision-records.html#references",
-    "href": "decisions/20210212-use-markdown-architectural-decision-records.html#references",
-    "title": "Accepted: Use Markdown Architectural Decision Records",
+    "objectID": "decisions/20221206-export-godot-vrm-to-the-asset-library.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20221206-export-godot-vrm-to-the-asset-library.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Prepare godot-vrm for asset library publishing",
     "section": "",
-    "text": "Relates to Use Log4brains to manage the ADRs"
+    "text": "How to migrate to Godot-VRM to submodule format?\nThe thing Lyuma got blocked on is that VRM contains two addons: VRM and Godot-MToon-Shader\nRevive the Godot-MToon-Shader repository which Lyuma previously archived.\nBut Lyuma will change it so it’s only the submodule (contents of the addons folder) and then Lyuma will make the Godot VRM addon (submodule) a branch in the godot-vrm repository\nThen we’ll make a script to sync the changes to/from the godot-vrm example project which we submit to asset lib\nWriting this up for Fire, since we talked about the issue with addons/vrm being duplicated in multiple projects since Godot Asset Library doesn’t allow submodules / raw addons folders.\nDid some unarchiving and renames so that https://github.com/V-Sekai/Godot-MToon-Shader gets the top google slot\n\nMake sure the godot-vrm code is synced up with other repositories where it was duplicated.\nMake a mtoon addon repository with a copy of the Godot-MToon-Shader code.\nMake a branch in godot-vrm with ONLY the 4.0 vrm addon, usable as a submodule.\nChange v-sekai-game and other similar projects to use Godot-MToon-Shader and vrm as a submodules\nWrite a script to sync up repository contents from one to the other.\n\n\n\nIs there a functional difference between if not stringvar.is_empty(): vs if stringvar != \"\": x != “” is a bit shorter and easier to type, but I noticed some recommendation to use is_empty()."
   },
   {
-    "objectID": "decisions/20210212-use-markdown-architectural-decision-records.html#derivative-license",
-    "href": "decisions/20210212-use-markdown-architectural-decision-records.html#derivative-license",
-    "title": "Accepted: Use Markdown Architectural Decision Records",
+    "objectID": "decisions/20221206-export-godot-vrm-to-the-asset-library.html#positive-consequences",
+    "href": "decisions/20221206-export-godot-vrm-to-the-asset-library.html#positive-consequences",
+    "title": "Proposed: Prepare godot-vrm for asset library publishing",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "We don’t have duplicate godot-vrm copies and the copies stay in sync."
   },
   {
-    "objectID": "decisions/20210715-portable-world-content.html",
-    "href": "decisions/20210715-portable-world-content.html",
-    "title": "Proposed: Portable #world Content",
+    "objectID": "decisions/20221206-export-godot-vrm-to-the-asset-library.html#negative-consequences",
+    "href": "decisions/20221206-export-godot-vrm-to-the-asset-library.html#negative-consequences",
+    "title": "Proposed: Prepare godot-vrm for asset library publishing",
     "section": "",
-    "text": "Proposed: Portable #world Content\n\nContext and Problem Statement\nIndependent meta-verses (virtual worlds) lack content because their communities are too small to fund much content work.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nCollaborate with Mozilla Hub’s Spoke Editor and OMI Group’s glTF2 extensions to have portable #world content.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nProvide basic glTF2 extensions. Here is an initial list.\n\nURI scene linking\nArchive binary format\nAudio emitters\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nThere are many moving parts and a web client, which is not a few lines of code.\n\n\nPositive Consequences\n\nEasier creation of new virtual worlds.\nEncourage remixing content\nKeeping old content portable to new virtual #world\n\n\n\nNegative Consequences\n\nHave to find different monetization means for independent virtual #world\n\n\n\nIs there a reason why this should be core and done by us?\nNo one is doing it.\n\n\nReferences\n\nhttps://github.com/ubisoft/mixer/issues/19\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Asset library copy is different than development."
   },
   {
-    "objectID": "decisions/20240121-livebook-fedora-install.html",
-    "href": "decisions/20240121-livebook-fedora-install.html",
-    "title": "Proposed: Elixir Livebook on Fedora 39",
+    "objectID": "decisions/20221206-export-godot-vrm-to-the-asset-library.html#option-graveyard",
+    "href": "decisions/20221206-export-godot-vrm-to-the-asset-library.html#option-graveyard",
+    "title": "Proposed: Prepare godot-vrm for asset library publishing",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai Team\nTags: Elixir, Livebook, Fedora 39\n\n\n\n\nThe goal is to utilize Elixir NX for data science and numerical computing applications relevant to V-Sekai.\n\n\n\nThe challenge lies in ensuring a successful installation and configuration of Elixir Livebook on Fedora 39, which will serve as a development platform.\n\n\n\n\nAssess compatibility between Elixir Livebook and Fedora 39.\nIdentify all dependencies required for Elixir Livebook.\nDevelop comprehensive guidelines for the installation process.\nConduct a test run of the install procedure on a Fedora 39 system.\n\nCreate a dedicated user for running Livebook and determine an appropriate location for the installation, such as /opt/livebook.\nsudo yum groupinstall -y 'Development Tools' 'C Development Tools and Libraries'\nsudo dnf install -y \\\n  autoconf \\\n  ncurses-devel \\\n  wxGTK3-devel \\\n  wxBase3 \\\n  openssl-devel \\\n  java-1.8.0-openjdk-devel \\\n  libiodbc \\\n  unixODBC-devel.x86_64 \\\n  erlang-odbc.x86_64 \\\n  libxslt \\\n  fop \\\n  automake \\\n  readline-devel \\\n  git \\\n  gcc \\\n  unzip \\\n  curl\nsudo dnf copr enable vbatts/bazel -y && dnf install bazel5 -y\nsudo dnf install akmod-nvidia xorg-x11-drv-nvidia-cuda -y\n\n# As root or using sudo\nuseradd --system --create-home --home-dir /opt/livebook livebook\nchown -R livebook: /opt/livebook\nsu - livebook\ncd /opt/livebook\ngit clone https://github.com/asdf-vm/asdf.git ~/.asdf\necho -e '\\n. $HOME/.asdf/asdf.sh' &gt;&gt; ~/.bashrc\necho -e '\\n. $HOME/.asdf/completions/asdf.bash' &gt;&gt; ~/.bashrc\nsource ~/.bashrc\nasdf plugin-add erlang https://github.com/asdf-vm/asdf-erlang.git\nasdf install erlang 26.2.1\nasdf global erlang 26.2.1\nasdf plugin-add elixir https://github.com/asdf-vm/asdf-elixir.git\nasdf install elixir 1.16-otp-26\nasdf global elixir 1.16-otp-26\nerl -version\nelixir -v\nmix do local.rebar --force, local.hex --force\nmix escript.install hex livebook --force\nTo insert or overwrite the existing systemd service configuration for Elixir Livebook directly from the shell, you can use the following commands:\nFirst, open your terminal and use cat combined with a here-document to overwrite the file with the new configuration:\nsudo cat &gt; /etc/systemd/system/livebook.service &lt;&lt;EOF\n[Unit]\nDescription=Elixir Livebook server\nAfter=network.target\n\n[Service]\nUser=livebook\nWorkingDirectory=/opt/livebook\nExecStart=/bin/bash -c '. /opt/livebook/.asdf/asdf.sh && exec /opt/livebook/.asdf/installs/elixir/1.16-otp-26/.mix/escripts/livebook server'\nEnvironment=MIX_ENV=prod\nEnvironment=LIVEBOOK_PORT=8080\nEnvironment=LIVEBOOK_IP=0.0.0.0\nEnvironment=LIVEBOOK_HOME=/opt/livebook\nRestart=on-failure\n\n[Install]\nWantedBy=multi-user.target\nEOF\nEnsure that you have the necessary permissions to write to /etc/systemd/system/.\nAfter saving the file, reload systemd to apply the changes:\nsudo systemctl daemon-reload\nsudo systemctl enable livebook.service\nsudo systemctl restart livebook.service\nVerify that the service is running correctly with:\nsudo systemctl status livebook.service # Check this for the authentication token.\nDebug the service with journalctl.\nsudo journalctl -u livebook.service\nRemember to adjust the path specified in the ExecStart directive if required and set any additional environment variables as needed.\n\n\n\n\nProvides a real-time collaborative tool for Elixir development.\nHelps in verifying Elixir NX’s capabilities through visualization.\nStreamlines the code development cycle with instant feedback.\n\n\n\n\n\nTime allocation needed for the seamless functioning of Livebook on Fedora 39.\nDependencies might add a layer of complexity in ongoing maintenance.\nThe initial setup could pose challenges for non-expert users.\n\n\n\n\nOther tools and languages were assessed but did not fulfill V-Sekai’s requirements as effectively as Elixir Livebook.\n\n\n\nEvaluating occasional usage to justify the demand for an efficient installation approach.\n\n\n\nDetermining if this integration should be centralized within V-Sekai’s primary offerings and whether internal resources can achieve this implementation.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account of V-Sekai’s developer community.\nV-Sekai/v-sekai-game - Repository dedicated to V-Sekai’s project for merging social VR and metaverse elements with Godot Engine.\n\nAria, an AI assistant, contributed to the drafting of this proposal."
+    "text": "Option: The status quo. \nRejection Reason: This solves nothing. We have duplicate development versions."
   },
   {
-    "objectID": "decisions/20240121-livebook-fedora-install.html#metadata",
-    "href": "decisions/20240121-livebook-fedora-install.html#metadata",
-    "title": "Proposed: Elixir Livebook on Fedora 39",
+    "objectID": "decisions/20221206-export-godot-vrm-to-the-asset-library.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20221206-export-godot-vrm-to-the-asset-library.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Prepare godot-vrm for asset library publishing",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai Team\nTags: Elixir, Livebook, Fedora 39"
+    "text": "This is a repository layout and not code."
   },
   {
-    "objectID": "decisions/20240121-livebook-fedora-install.html#backdrop",
-    "href": "decisions/20240121-livebook-fedora-install.html#backdrop",
-    "title": "Proposed: Elixir Livebook on Fedora 39",
+    "objectID": "decisions/20221206-export-godot-vrm-to-the-asset-library.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20221206-export-godot-vrm-to-the-asset-library.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Prepare godot-vrm for asset library publishing",
     "section": "",
-    "text": "The goal is to utilize Elixir NX for data science and numerical computing applications relevant to V-Sekai."
+    "text": "We own the godot-vrm and the mtoon repositories."
   },
   {
-    "objectID": "decisions/20240121-livebook-fedora-install.html#challenge",
-    "href": "decisions/20240121-livebook-fedora-install.html#challenge",
-    "title": "Proposed: Elixir Livebook on Fedora 39",
+    "objectID": "decisions/20221206-export-godot-vrm-to-the-asset-library.html#references",
+    "href": "decisions/20221206-export-godot-vrm-to-the-asset-library.html#references",
+    "title": "Proposed: Prepare godot-vrm for asset library publishing",
     "section": "",
-    "text": "The challenge lies in ensuring a successful installation and configuration of Elixir Livebook on Fedora 39, which will serve as a development platform."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20240121-livebook-fedora-install.html#strategy",
-    "href": "decisions/20240121-livebook-fedora-install.html#strategy",
-    "title": "Proposed: Elixir Livebook on Fedora 39",
+    "objectID": "decisions/20221206-export-godot-vrm-to-the-asset-library.html#license-of-the-contribution",
+    "href": "decisions/20221206-export-godot-vrm-to-the-asset-library.html#license-of-the-contribution",
+    "title": "Proposed: Prepare godot-vrm for asset library publishing",
     "section": "",
-    "text": "Assess compatibility between Elixir Livebook and Fedora 39.\nIdentify all dependencies required for Elixir Livebook.\nDevelop comprehensive guidelines for the installation process.\nConduct a test run of the install procedure on a Fedora 39 system.\n\nCreate a dedicated user for running Livebook and determine an appropriate location for the installation, such as /opt/livebook.\nsudo yum groupinstall -y 'Development Tools' 'C Development Tools and Libraries'\nsudo dnf install -y \\\n  autoconf \\\n  ncurses-devel \\\n  wxGTK3-devel \\\n  wxBase3 \\\n  openssl-devel \\\n  java-1.8.0-openjdk-devel \\\n  libiodbc \\\n  unixODBC-devel.x86_64 \\\n  erlang-odbc.x86_64 \\\n  libxslt \\\n  fop \\\n  automake \\\n  readline-devel \\\n  git \\\n  gcc \\\n  unzip \\\n  curl\nsudo dnf copr enable vbatts/bazel -y && dnf install bazel5 -y\nsudo dnf install akmod-nvidia xorg-x11-drv-nvidia-cuda -y\n\n# As root or using sudo\nuseradd --system --create-home --home-dir /opt/livebook livebook\nchown -R livebook: /opt/livebook\nsu - livebook\ncd /opt/livebook\ngit clone https://github.com/asdf-vm/asdf.git ~/.asdf\necho -e '\\n. $HOME/.asdf/asdf.sh' &gt;&gt; ~/.bashrc\necho -e '\\n. $HOME/.asdf/completions/asdf.bash' &gt;&gt; ~/.bashrc\nsource ~/.bashrc\nasdf plugin-add erlang https://github.com/asdf-vm/asdf-erlang.git\nasdf install erlang 26.2.1\nasdf global erlang 26.2.1\nasdf plugin-add elixir https://github.com/asdf-vm/asdf-elixir.git\nasdf install elixir 1.16-otp-26\nasdf global elixir 1.16-otp-26\nerl -version\nelixir -v\nmix do local.rebar --force, local.hex --force\nmix escript.install hex livebook --force\nTo insert or overwrite the existing systemd service configuration for Elixir Livebook directly from the shell, you can use the following commands:\nFirst, open your terminal and use cat combined with a here-document to overwrite the file with the new configuration:\nsudo cat &gt; /etc/systemd/system/livebook.service &lt;&lt;EOF\n[Unit]\nDescription=Elixir Livebook server\nAfter=network.target\n\n[Service]\nUser=livebook\nWorkingDirectory=/opt/livebook\nExecStart=/bin/bash -c '. /opt/livebook/.asdf/asdf.sh && exec /opt/livebook/.asdf/installs/elixir/1.16-otp-26/.mix/escripts/livebook server'\nEnvironment=MIX_ENV=prod\nEnvironment=LIVEBOOK_PORT=8080\nEnvironment=LIVEBOOK_IP=0.0.0.0\nEnvironment=LIVEBOOK_HOME=/opt/livebook\nRestart=on-failure\n\n[Install]\nWantedBy=multi-user.target\nEOF\nEnsure that you have the necessary permissions to write to /etc/systemd/system/.\nAfter saving the file, reload systemd to apply the changes:\nsudo systemctl daemon-reload\nsudo systemctl enable livebook.service\nsudo systemctl restart livebook.service\nVerify that the service is running correctly with:\nsudo systemctl status livebook.service # Check this for the authentication token.\nDebug the service with journalctl.\nsudo journalctl -u livebook.service\nRemember to adjust the path specified in the ExecStart directive if required and set any additional environment variables as needed."
+    "text": "MIT License\n\nCopyright (c) 2018-2022 SaracenOne\nCopyright (c) 2019-2022 K. S. Ernest (iFire) Lee (fire)\nCopyright (c) 2020-2022 Lyuma\nCopyright (c) 2020-2022 MMMaellon\nCopyright (c) 2022 V-Sekai Contributors\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
   },
   {
-    "objectID": "decisions/20240121-livebook-fedora-install.html#upside",
-    "href": "decisions/20240121-livebook-fedora-install.html#upside",
-    "title": "Proposed: Elixir Livebook on Fedora 39",
+    "objectID": "decisions/20211031-extract-proposals-into-proposals.html",
+    "href": "decisions/20211031-extract-proposals-into-proposals.html",
+    "title": "Proposed: Extract proposals into proposals",
     "section": "",
-    "text": "Provides a real-time collaborative tool for Elixir development.\nHelps in verifying Elixir NX’s capabilities through visualization.\nStreamlines the code development cycle with instant feedback."
+    "text": "Proposed: Extract proposals into proposals\n\nContext and Problem Statement\nDecision trees are hard to use\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nConvert items in a decision tree into proposals\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n\n\n\n\n\n\n\n\nName\nDescription\nTask Stage\n\n\n\n\nGLTF #materialx\n\nidea\n\n\nGodot CASSIE\n\nidea\n\n\nElixir membrane gltf processor\n\nidea\n\n\nGodot Dem Bones\nConvert blend shapes to skeletal animation\nidea\n\n\nrobust-voip\nvoip or audio problems?\nidea\n\n\nCVTT\nAllow the use of BC6 and BC7 instead of DXT5.\nidea\n\n\nSpiceDB\nAuthorization\nidea\n\n\nLibcurl\nLibcurl for Godot Engine\nevaluate\n\n\nGodot OSC\nhttps://github.com/infosia/vmc2bvh\nclosed abandoned\n\n\nGLTF wasm\n\nidea\n\n\nGodot AI Planner\n\nidea\n\n\nProfile Picture taker\nBetter VRM full profile and portrait taker\nidea\n\n\nGLTF omi-audio-emitter\n\nidea\n\n\nRobust Networking\nnetworking problems: max room capacity? other unknown bandwidth limits? server hosting problems: dedicated server support? self hosting / upnp / holepunching?\nidea\n\n\nGLTF animation tree\n\nidea\n\n\n#materialx Godot Plugin\nGLTF2 #materialx BSDF\nidea\n\n\n#materialx Grid Texture Generator\n\nidea\n\n\nAvatar Customization\nhow to import avatars from various places: Only VRM? Use Blender to convert GLTF?\nidea\n\n\nV-Sekai homeroom\n\nidea\n\n\nEWBIK Json debug\nPrint EWBIK json debug\nidea\n\n\nAnimation Tree\nAnimation tree\nidea\n\n\nDecimate character to 60’000 polygons\nUse for VRCHAT https://sketchfab.com/3d-models/haveto-blue-mage-ray-tachie-dialog-5e15ae6513d74f63b7bdf5ec4ba884e6\nidea\n\n\nFlat Avatar Animation\nHow do I get an animation set to play on my V-Sekai avatar (T-Pose with correct bone rotations) Native Blender FBX? Unity? Others?\nidea\n\n\nEventful Activities\nactivities: mirrors? physics interactables? games? video players? Custom cameras? Selfie cameras?\nidea\n\n\nUDIM bake to textures\n\nidea\n\n\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot code, but ideas.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nOnly we know.\n\n\nReferences\n\nplan-V-Sekai.txt\nplan-cassie.txt\nplan_lyuma\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240121-livebook-fedora-install.html#downside",
-    "href": "decisions/20240121-livebook-fedora-install.html#downside",
-    "title": "Proposed: Elixir Livebook on Fedora 39",
+    "objectID": "decisions/20230823-speech-to-blendshapes.html",
+    "href": "decisions/20230823-speech-to-blendshapes.html",
+    "title": "Proposed: Developing a Unified Model for Speech-to-Facial Shape Generation Using Outlines 〰 Library",
     "section": "",
-    "text": "Time allocation needed for the seamless functioning of Livebook on Fedora 39.\nDependencies might add a layer of complexity in ongoing maintenance.\nThe initial setup could pose challenges for non-expert users."
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nV-Sekai is embarking on a project that translates speech into corresponding facial shapes for virtual reality applications. This process eliminates the need for a face camera and leverages the SpeechEncoderDecoderModel from Hugging Face’s Transformers library for comprehensive speech recognition.\nThe SpeakingFaces dataset, a collection from 142 diverse subjects, will be utilized for this project. The dataset is accessible via the server of the Institute for Smart Systems and Artificial Intelligence (ISSAI) under the Creative Commons Attribution 4.0 International License.\nOutlines 〰, a neural text generation library, will also play a crucial role in this project. It offers robust prompting primitives, separates the prompting from the execution logic, and is compatible with all models. It interfaces with models through the next-token logits and can be used with API-based models as well.\n\n\n\nThe primary challenge lies in developing a model capable of generating text and blendshapes simultaneously from the same input speech using the Outlines 〰 library.\n\n\n\nThe proposed strategy involves creating a custom model that accepts speech as input and outputs both text and blendshapes. This unified model would incorporate a shared encoder to process the speech input, and a single decoder to generate the text and blendshape outputs. The Outlines 〰 library will be used to conform the output to the desired format.\nfrom outlines import Outline\nfrom transformers import SpeechEncoderDecoderModel, Speech2Text2Processor, Wav2Vec2Model\nimport json\n\n# Initialize the processor and encoder\nprocessor = Speech2Text2Processor.from_pretrained(\"facebook/s2t-small-librispeech-asr\")\nencoder = Wav2Vec2Model.from_pretrained(\"facebook/wav2vec2-base-960h\")\n\n# Initialize the decoder\ndecoder = Speech2Text2Model.from_pretrained(\"facebook/s2t-small-librispeech-asr\")\n\n# Initialize the unified model\nmodel = UnifiedSpeechEncoderDecoderModel(encoder=encoder, decoder=decoder)\n\n# Define an outline for the model\noutline = Outline(model).to(device)\n\n# Generate text and blendshapes\ngenerated_text, generated_blendshapes = outline.generate(input_speech)\n\n# Conform to JSON schemaßß\nblendshapes_keys = [\"BrowInnerUp\", \"BrowDownLeft\", \"BrowDownRight\", \"BrowOuterUpLeft\", \"BrowOuterUpRight\",\n                    \"EyeLookUpLeft\", \"EyeLookUpRight\", \"EyeLookDownLeft\", \"EyeLookDownRight\", \"EyeLookInLeft\",\n                    \"EyeLookInRight\", \"EyeLookOutLeft\", \"EyeLookOutRight\", \"EyeBlinkLeft\", \"EyeBlinkRight\",\n                    \"EyeSquintRight\", \"EyeSquintLeft\", \"EyeWideLeft\", \"EyeWideRight\", \"CheekPuff\",\n                    \"CheekSquintLeft\", \"CheekSquintRight\", \"NoseSneerLeft\", \"NoseSneerRight\", \"JawOpen\",\n                    \"JawForward\", \"JawLeft\", \"JawRight\", \"MouthFunnel\", \"MouthPucker\", \"MouthLeft\",\n                    \"MouthRight\", \"MouthRollUpper\", \"MouthRollLower\", \"MouthShrugUpper\", \"MouthShrugLower\",\n                    \"MouthClose\", \"MouthSmileLeft\", \"MouthSmileRight\", \"MouthFrownLeft\", \"MouthFrownRight\",\n                    \"MouthDimpleLeft\", \"MouthDimpleRight\", \"MouthUpperUpLeft\", \"MouthUpperUpRight\",\n                    \"MouthLowerDownLeft\", \"MouthLowerDownRight\", \"MouthPressLeft\", \"MouthPressRight\",\n                    \"MouthStretchLeft\", \"MouthStretchRight\", \"TongueOut\"]\n\noutput = {\n    \"text\": generated_text,\n    \"blendshapes\": dict(zip(blendshapes_keys, generated_blendshapes))\n}\n\njson_output = json.dumps(output)\n\n\n\nDeveloping our own unified model for generating both text and blendshapes from speech using the Outlines 〰 library is a strategic move that provides us with greater control and customization to meet our specific needs. It not only deepens our understanding of the model, aiding in troubleshooting and improvements, but also allows us to optimize it for better performance and efficiency.\n\n\n\nThe limitation of this approach is that the UnifiedSpeechEncoderDecoderModel, and Outline are placeholders for your actual unified model classes, and outline respectively. You would need to implement these classes yourself, or find pre-trained models that suit your needs.\n\n\n\nBeing self-reliant in maintaining and updating our model eliminates dependence on third parties, providing flexibility to make changes as needed. Moreover, it ensures seamless integration with other parts of our system.\n\n\n\nWhile this approach requires more initial effort, the potential for improvement and fine-tuning with our unique data sets makes it worthwhile, leading to superior results in the long run.\n\n\n\nYes, the development and maintenance of the unified model will be done by us.\n\n\n\n\nV-Sekai\nThis article is assisted by AI."
   },
   {
-    "objectID": "decisions/20240121-livebook-fedora-install.html#road-not-taken",
-    "href": "decisions/20240121-livebook-fedora-install.html#road-not-taken",
-    "title": "Proposed: Elixir Livebook on Fedora 39",
+    "objectID": "decisions/20230823-speech-to-blendshapes.html#metadata",
+    "href": "decisions/20230823-speech-to-blendshapes.html#metadata",
+    "title": "Proposed: Developing a Unified Model for Speech-to-Facial Shape Generation Using Outlines 〰 Library",
     "section": "",
-    "text": "Other tools and languages were assessed but did not fulfill V-Sekai’s requirements as effectively as Elixir Livebook."
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20240121-livebook-fedora-install.html#infrequent-use-case",
-    "href": "decisions/20240121-livebook-fedora-install.html#infrequent-use-case",
-    "title": "Proposed: Elixir Livebook on Fedora 39",
+    "objectID": "decisions/20230823-speech-to-blendshapes.html#the-backdrop",
+    "href": "decisions/20230823-speech-to-blendshapes.html#the-backdrop",
+    "title": "Proposed: Developing a Unified Model for Speech-to-Facial Shape Generation Using Outlines 〰 Library",
     "section": "",
-    "text": "Evaluating occasional usage to justify the demand for an efficient installation approach."
+    "text": "V-Sekai is embarking on a project that translates speech into corresponding facial shapes for virtual reality applications. This process eliminates the need for a face camera and leverages the SpeechEncoderDecoderModel from Hugging Face’s Transformers library for comprehensive speech recognition.\nThe SpeakingFaces dataset, a collection from 142 diverse subjects, will be utilized for this project. The dataset is accessible via the server of the Institute for Smart Systems and Artificial Intelligence (ISSAI) under the Creative Commons Attribution 4.0 International License.\nOutlines 〰, a neural text generation library, will also play a crucial role in this project. It offers robust prompting primitives, separates the prompting from the execution logic, and is compatible with all models. It interfaces with models through the next-token logits and can be used with API-based models as well."
   },
   {
-    "objectID": "decisions/20240121-livebook-fedora-install.html#in-core-and-done-by-us",
-    "href": "decisions/20240121-livebook-fedora-install.html#in-core-and-done-by-us",
-    "title": "Proposed: Elixir Livebook on Fedora 39",
+    "objectID": "decisions/20230823-speech-to-blendshapes.html#the-challenge",
+    "href": "decisions/20230823-speech-to-blendshapes.html#the-challenge",
+    "title": "Proposed: Developing a Unified Model for Speech-to-Facial Shape Generation Using Outlines 〰 Library",
     "section": "",
-    "text": "Determining if this integration should be centralized within V-Sekai’s primary offerings and whether internal resources can achieve this implementation."
+    "text": "The primary challenge lies in developing a model capable of generating text and blendshapes simultaneously from the same input speech using the Outlines 〰 library."
   },
   {
-    "objectID": "decisions/20240121-livebook-fedora-install.html#further-reading",
-    "href": "decisions/20240121-livebook-fedora-install.html#further-reading",
-    "title": "Proposed: Elixir Livebook on Fedora 39",
+    "objectID": "decisions/20230823-speech-to-blendshapes.html#the-strategy",
+    "href": "decisions/20230823-speech-to-blendshapes.html#the-strategy",
+    "title": "Proposed: Developing a Unified Model for Speech-to-Facial Shape Generation Using Outlines 〰 Library",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account of V-Sekai’s developer community.\nV-Sekai/v-sekai-game - Repository dedicated to V-Sekai’s project for merging social VR and metaverse elements with Godot Engine.\n\nAria, an AI assistant, contributed to the drafting of this proposal."
+    "text": "The proposed strategy involves creating a custom model that accepts speech as input and outputs both text and blendshapes. This unified model would incorporate a shared encoder to process the speech input, and a single decoder to generate the text and blendshape outputs. The Outlines 〰 library will be used to conform the output to the desired format.\nfrom outlines import Outline\nfrom transformers import SpeechEncoderDecoderModel, Speech2Text2Processor, Wav2Vec2Model\nimport json\n\n# Initialize the processor and encoder\nprocessor = Speech2Text2Processor.from_pretrained(\"facebook/s2t-small-librispeech-asr\")\nencoder = Wav2Vec2Model.from_pretrained(\"facebook/wav2vec2-base-960h\")\n\n# Initialize the decoder\ndecoder = Speech2Text2Model.from_pretrained(\"facebook/s2t-small-librispeech-asr\")\n\n# Initialize the unified model\nmodel = UnifiedSpeechEncoderDecoderModel(encoder=encoder, decoder=decoder)\n\n# Define an outline for the model\noutline = Outline(model).to(device)\n\n# Generate text and blendshapes\ngenerated_text, generated_blendshapes = outline.generate(input_speech)\n\n# Conform to JSON schemaßß\nblendshapes_keys = [\"BrowInnerUp\", \"BrowDownLeft\", \"BrowDownRight\", \"BrowOuterUpLeft\", \"BrowOuterUpRight\",\n                    \"EyeLookUpLeft\", \"EyeLookUpRight\", \"EyeLookDownLeft\", \"EyeLookDownRight\", \"EyeLookInLeft\",\n                    \"EyeLookInRight\", \"EyeLookOutLeft\", \"EyeLookOutRight\", \"EyeBlinkLeft\", \"EyeBlinkRight\",\n                    \"EyeSquintRight\", \"EyeSquintLeft\", \"EyeWideLeft\", \"EyeWideRight\", \"CheekPuff\",\n                    \"CheekSquintLeft\", \"CheekSquintRight\", \"NoseSneerLeft\", \"NoseSneerRight\", \"JawOpen\",\n                    \"JawForward\", \"JawLeft\", \"JawRight\", \"MouthFunnel\", \"MouthPucker\", \"MouthLeft\",\n                    \"MouthRight\", \"MouthRollUpper\", \"MouthRollLower\", \"MouthShrugUpper\", \"MouthShrugLower\",\n                    \"MouthClose\", \"MouthSmileLeft\", \"MouthSmileRight\", \"MouthFrownLeft\", \"MouthFrownRight\",\n                    \"MouthDimpleLeft\", \"MouthDimpleRight\", \"MouthUpperUpLeft\", \"MouthUpperUpRight\",\n                    \"MouthLowerDownLeft\", \"MouthLowerDownRight\", \"MouthPressLeft\", \"MouthPressRight\",\n                    \"MouthStretchLeft\", \"MouthStretchRight\", \"TongueOut\"]\n\noutput = {\n    \"text\": generated_text,\n    \"blendshapes\": dict(zip(blendshapes_keys, generated_blendshapes))\n}\n\njson_output = json.dumps(output)"
   },
   {
-    "objectID": "decisions/20220901-mirror-extend-asset-library-packages.html",
-    "href": "decisions/20220901-mirror-extend-asset-library-packages.html",
-    "title": "Proposed: Extended asset library packages in addition to the upstream asset library",
+    "objectID": "decisions/20230823-speech-to-blendshapes.html#the-upside",
+    "href": "decisions/20230823-speech-to-blendshapes.html#the-upside",
+    "title": "Proposed: Developing a Unified Model for Speech-to-Facial Shape Generation Using Outlines 〰 Library",
     "section": "",
-    "text": "Proposed: Extended asset library packages in addition to the upstream asset library\n\nContext and Problem Statement\nHave a way to deploy custom asset libs via the godot engine asset library ui\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nWe propose to use the V-Sekai uro server to provide an asset library url to Godot Engine.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nImplement\n\nrest passthrough https://github.com/godotengine/godot-asset-library/blob/master/API.md\naccount based package bundles (does not include the original package, only the metadata)\n\n\n\nPositive Consequences\nWe can have our own asset archives.\n\n\nNegative Consequences\nMay compromise security.\n\n\nOption graveyard\nUpload to the asset library directly.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot a few lines of script.\n\n\nIs there a reason why this should be core and done by us?\nWe maintain uro.\n\n\nReferences\n\nV-Sekai\n\n\n\nLicense of the contribution\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Developing our own unified model for generating both text and blendshapes from speech using the Outlines 〰 library is a strategic move that provides us with greater control and customization to meet our specific needs. It not only deepens our understanding of the model, aiding in troubleshooting and improvements, but also allows us to optimize it for better performance and efficiency."
   },
   {
-    "objectID": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html",
-    "href": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html",
-    "title": "Draft: Use single player WebXR in Godot Engine to prototype CASSIE.",
+    "objectID": "decisions/20230823-speech-to-blendshapes.html#the-downside",
+    "href": "decisions/20230823-speech-to-blendshapes.html#the-downside",
+    "title": "Proposed: Developing a Unified Model for Speech-to-Facial Shape Generation Using Outlines 〰 Library",
     "section": "",
-    "text": "Status: draft \nDeciders: V-Sekai,fire\nTags: V-Sekai,\n\n\n\nWant to prototype a drawing environment in vr for the web.\nUnable to commit much resources.\n\n\n\nUse a fork of Godot 3.4 for WebXR that includes delauney tetrahedralization processing.\nPostponed until Godot Engine master has WebXR\n\n\n\n\nExtract geometry class from Godot Engine 4.0 to 3.4.\n\n\n\n\n\nStable\n\n\n\n\n\nSlower than Godot Engine master\n\n\n\n\n\nOption: Godot master as of 2021-11-05\nRejection Reason: Godot Master doesn’t have WebXR on this date.\n\n\n\n\nThis is a project proposal.\n\n\n\nI found an approach to do it.\n\n\n\n\nhttps://godotengine.org/news\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "The limitation of this approach is that the UnifiedSpeechEncoderDecoderModel, and Outline are placeholders for your actual unified model classes, and outline respectively. You would need to implement these classes yourself, or find pre-trained models that suit your needs."
   },
   {
-    "objectID": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html#context-and-problem-statement",
-    "href": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html#context-and-problem-statement",
-    "title": "Draft: Use single player WebXR in Godot Engine to prototype CASSIE.",
+    "objectID": "decisions/20230823-speech-to-blendshapes.html#the-road-not-taken",
+    "href": "decisions/20230823-speech-to-blendshapes.html#the-road-not-taken",
+    "title": "Proposed: Developing a Unified Model for Speech-to-Facial Shape Generation Using Outlines 〰 Library",
     "section": "",
-    "text": "Want to prototype a drawing environment in vr for the web.\nUnable to commit much resources."
+    "text": "Being self-reliant in maintaining and updating our model eliminates dependence on third parties, providing flexibility to make changes as needed. Moreover, it ensures seamless integration with other parts of our system."
   },
   {
-    "objectID": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Draft: Use single player WebXR in Godot Engine to prototype CASSIE.",
+    "objectID": "decisions/20230823-speech-to-blendshapes.html#the-infrequent-use-case",
+    "href": "decisions/20230823-speech-to-blendshapes.html#the-infrequent-use-case",
+    "title": "Proposed: Developing a Unified Model for Speech-to-Facial Shape Generation Using Outlines 〰 Library",
     "section": "",
-    "text": "Use a fork of Godot 3.4 for WebXR that includes delauney tetrahedralization processing.\nPostponed until Godot Engine master has WebXR"
+    "text": "While this approach requires more initial effort, the potential for improvement and fine-tuning with our unique data sets makes it worthwhile, leading to superior results in the long run."
   },
   {
-    "objectID": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Draft: Use single player WebXR in Godot Engine to prototype CASSIE.",
+    "objectID": "decisions/20230823-speech-to-blendshapes.html#in-core-and-done-by-us",
+    "href": "decisions/20230823-speech-to-blendshapes.html#in-core-and-done-by-us",
+    "title": "Proposed: Developing a Unified Model for Speech-to-Facial Shape Generation Using Outlines 〰 Library",
     "section": "",
-    "text": "Extract geometry class from Godot Engine 4.0 to 3.4."
+    "text": "Yes, the development and maintenance of the unified model will be done by us."
   },
   {
-    "objectID": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html#positive-consequences",
-    "href": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html#positive-consequences",
-    "title": "Draft: Use single player WebXR in Godot Engine to prototype CASSIE.",
+    "objectID": "decisions/20230823-speech-to-blendshapes.html#further-reading",
+    "href": "decisions/20230823-speech-to-blendshapes.html#further-reading",
+    "title": "Proposed: Developing a Unified Model for Speech-to-Facial Shape Generation Using Outlines 〰 Library",
     "section": "",
-    "text": "Stable"
+    "text": "V-Sekai\nThis article is assisted by AI."
   },
   {
-    "objectID": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html#negative-consequences",
-    "href": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html#negative-consequences",
-    "title": "Draft: Use single player WebXR in Godot Engine to prototype CASSIE.",
+    "objectID": "decisions/20240613-training-dataset.html",
+    "href": "decisions/20240613-training-dataset.html",
+    "title": "Proposed: Dataset Scaling for Training Mesh Transformer",
     "section": "",
-    "text": "Slower than Godot Engine master"
+    "text": "We are working on training a mesh transformer to create 3D avatar characters. The avatars are represented using quads, and we aim to keep the quad count to 1024 or less.\n\n\n\nThe question at hand is determining the size of the dataset needed for training the model effectively.\n\n\n\nThe size of the dataset required for training a model effectively depends on the desired type of outputs from the model.\n\nGeneric Outputs: If the goal is to have the model generate outputs that it has already seen during training, a smaller dataset is sufficient. In this case, a dataset size in the range of 2,000 to 10,000 would be appropriate.\nNovel Outputs: On the other hand, if the aim is for the model to generate novel or never-seen-before outputs, a larger dataset is necessary. Here, a dataset size between 10,000 and 100,000 would be more suitable.\n\n\n\n\n\nA smaller dataset is easier to manage and requires less computational resources for training.\nA larger dataset allows the model to generate novel outputs, enhancing its creativity and versatility.\n\n\n\n\n\nA smaller dataset might limit the model’s ability to generate novel outputs.\nA larger dataset requires more computational resources for training and may lead to longer training times.\n\n\n\n\n\nWe could have chosen to use a fixed dataset size without considering the type of outputs we want from the model.\n\n\n\n\n\nThis approach may not be suitable if we want the model to generate both generic and novel outputs equally well.\n\n\n\n\n\nThe decision on the dataset size and the training of the mesh transformer will be done by us, using our acquired resources and expertise.\n\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\niFire\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html#option-graveyard",
-    "href": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html#option-graveyard",
-    "title": "Draft: Use single player WebXR in Godot Engine to prototype CASSIE.",
+    "objectID": "decisions/20240613-training-dataset.html#the-context",
+    "href": "decisions/20240613-training-dataset.html#the-context",
+    "title": "Proposed: Dataset Scaling for Training Mesh Transformer",
     "section": "",
-    "text": "Option: Godot master as of 2021-11-05\nRejection Reason: Godot Master doesn’t have WebXR on this date."
+    "text": "We are working on training a mesh transformer to create 3D avatar characters. The avatars are represented using quads, and we aim to keep the quad count to 1024 or less."
   },
   {
-    "objectID": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Draft: Use single player WebXR in Godot Engine to prototype CASSIE.",
+    "objectID": "decisions/20240613-training-dataset.html#the-problem-statement",
+    "href": "decisions/20240613-training-dataset.html#the-problem-statement",
+    "title": "Proposed: Dataset Scaling for Training Mesh Transformer",
     "section": "",
-    "text": "This is a project proposal."
+    "text": "The question at hand is determining the size of the dataset needed for training the model effectively."
   },
   {
-    "objectID": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Draft: Use single player WebXR in Godot Engine to prototype CASSIE.",
+    "objectID": "decisions/20240613-training-dataset.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240613-training-dataset.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Dataset Scaling for Training Mesh Transformer",
     "section": "",
-    "text": "I found an approach to do it."
+    "text": "The size of the dataset required for training a model effectively depends on the desired type of outputs from the model.\n\nGeneric Outputs: If the goal is to have the model generate outputs that it has already seen during training, a smaller dataset is sufficient. In this case, a dataset size in the range of 2,000 to 10,000 would be appropriate.\nNovel Outputs: On the other hand, if the aim is for the model to generate novel or never-seen-before outputs, a larger dataset is necessary. Here, a dataset size between 10,000 and 100,000 would be more suitable."
   },
   {
-    "objectID": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html#references",
-    "href": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html#references",
-    "title": "Draft: Use single player WebXR in Godot Engine to prototype CASSIE.",
+    "objectID": "decisions/20240613-training-dataset.html#the-benefits",
+    "href": "decisions/20240613-training-dataset.html#the-benefits",
+    "title": "Proposed: Dataset Scaling for Training Mesh Transformer",
     "section": "",
-    "text": "https://godotengine.org/news"
+    "text": "A smaller dataset is easier to manage and requires less computational resources for training.\nA larger dataset allows the model to generate novel outputs, enhancing its creativity and versatility."
   },
   {
-    "objectID": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html#derivative-license",
-    "href": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html#derivative-license",
-    "title": "Draft: Use single player WebXR in Godot Engine to prototype CASSIE.",
+    "objectID": "decisions/20240613-training-dataset.html#the-downsides",
+    "href": "decisions/20240613-training-dataset.html#the-downsides",
+    "title": "Proposed: Dataset Scaling for Training Mesh Transformer",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "A smaller dataset might limit the model’s ability to generate novel outputs.\nA larger dataset requires more computational resources for training and may lead to longer training times."
   },
   {
-    "objectID": "decisions/20231112-validation-service.html",
-    "href": "decisions/20231112-validation-service.html",
-    "title": "Proposed: Validator Service for V-Sekai",
+    "objectID": "decisions/20240613-training-dataset.html#the-road-not-taken",
+    "href": "decisions/20240613-training-dataset.html#the-road-not-taken",
+    "title": "Proposed: Dataset Scaling for Training Mesh Transformer",
     "section": "",
-    "text": "Status: Proposed\nDeciders: iFire, Bioblaze Payne, V-Sekai Team\nTags: V-Sekai, Validator Service, Godot Engine, GLTF, Websockets, API\n\n\n\n\nV-Sekai is an open-source project that brings social VR/VRSNS/metaverse components to the Godot Engine. The team is considering implementing a validator service to enhance the functionality and reliability of their projects.\n\n\n\nThe current backend system lacks a mechanism to validate scenes, count triangles, convert GLTF to Godot scene, and strip bad code from Godot scenes. This can lead to errors and inefficiencies in the development process.\n\n\n\nThe proposed solution is to create a validator service that conforms to a specific specification. This service would:\n\nConvert GLTF to Godot scene.\nGo over the scene and print the number of triangles.\nIf necessary, run LOD on the scene.\nRun a validation that strips the bad code from the Godot scene.\nUse websockets and an API for communication and function calls.\n\nThe front-end for this service could be a CLI that calls the function locally. The asset service would call the validator service, which would then notify the websocket service via its API call.\n\n\n\nImplementing this validator service would provide several benefits:\n\nImproved accuracy and efficiency in the development process.\nEnhanced error detection and prevention.\nStreamlined communication between different parts of the system.\n\n\n\n\nPotential challenges or downsides could include:\n\nComplexity in setting up and maintaining the validator service.\nNeed for thorough testing to ensure the validator service works as expected.\n\n\n\n\nAn alternative approach could be to use gdscript + webrtc instead of websockets + API for communication and function calls. However, this would need to be evaluated for feasibility and efficiency.\n\n\n\nThe next steps would be to:\n\nFinalize the specification for the validator service.\nDevelop the validator service according to the agreed-upon specification.\nTest the validator service thoroughly to ensure it works as expected.\nImplement the validator service in the V-Sekai system.\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nThis proposal was assisted by AI assistant Aria."
+    "text": "We could have chosen to use a fixed dataset size without considering the type of outputs we want from the model."
   },
   {
-    "objectID": "decisions/20231112-validation-service.html#metadata",
-    "href": "decisions/20231112-validation-service.html#metadata",
-    "title": "Proposed: Validator Service for V-Sekai",
+    "objectID": "decisions/20240613-training-dataset.html#the-infrequent-use-case",
+    "href": "decisions/20240613-training-dataset.html#the-infrequent-use-case",
+    "title": "Proposed: Dataset Scaling for Training Mesh Transformer",
     "section": "",
-    "text": "Status: Proposed\nDeciders: iFire, Bioblaze Payne, V-Sekai Team\nTags: V-Sekai, Validator Service, Godot Engine, GLTF, Websockets, API"
+    "text": "This approach may not be suitable if we want the model to generate both generic and novel outputs equally well."
   },
   {
-    "objectID": "decisions/20231112-validation-service.html#context",
-    "href": "decisions/20231112-validation-service.html#context",
-    "title": "Proposed: Validator Service for V-Sekai",
+    "objectID": "decisions/20240613-training-dataset.html#in-core-and-done-by-us",
+    "href": "decisions/20240613-training-dataset.html#in-core-and-done-by-us",
+    "title": "Proposed: Dataset Scaling for Training Mesh Transformer",
     "section": "",
-    "text": "V-Sekai is an open-source project that brings social VR/VRSNS/metaverse components to the Godot Engine. The team is considering implementing a validator service to enhance the functionality and reliability of their projects."
+    "text": "The decision on the dataset size and the training of the mesh transformer will be done by us, using our acquired resources and expertise."
   },
   {
-    "objectID": "decisions/20231112-validation-service.html#problem",
-    "href": "decisions/20231112-validation-service.html#problem",
-    "title": "Proposed: Validator Service for V-Sekai",
+    "objectID": "decisions/20240613-training-dataset.html#status",
+    "href": "decisions/20240613-training-dataset.html#status",
+    "title": "Proposed: Dataset Scaling for Training Mesh Transformer",
     "section": "",
-    "text": "The current backend system lacks a mechanism to validate scenes, count triangles, convert GLTF to Godot scene, and strip bad code from Godot scenes. This can lead to errors and inefficiencies in the development process."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20231112-validation-service.html#proposed-solution",
-    "href": "decisions/20231112-validation-service.html#proposed-solution",
-    "title": "Proposed: Validator Service for V-Sekai",
+    "objectID": "decisions/20240613-training-dataset.html#decision-makers",
+    "href": "decisions/20240613-training-dataset.html#decision-makers",
+    "title": "Proposed: Dataset Scaling for Training Mesh Transformer",
     "section": "",
-    "text": "The proposed solution is to create a validator service that conforms to a specific specification. This service would:\n\nConvert GLTF to Godot scene.\nGo over the scene and print the number of triangles.\nIf necessary, run LOD on the scene.\nRun a validation that strips the bad code from the Godot scene.\nUse websockets and an API for communication and function calls.\n\nThe front-end for this service could be a CLI that calls the function locally. The asset service would call the validator service, which would then notify the websocket service via its API call."
+    "text": "V-Sekai development team\niFire"
   },
   {
-    "objectID": "decisions/20231112-validation-service.html#benefits",
-    "href": "decisions/20231112-validation-service.html#benefits",
-    "title": "Proposed: Validator Service for V-Sekai",
+    "objectID": "decisions/20240613-training-dataset.html#tags",
+    "href": "decisions/20240613-training-dataset.html#tags",
+    "title": "Proposed: Dataset Scaling for Training Mesh Transformer",
     "section": "",
-    "text": "Implementing this validator service would provide several benefits:\n\nImproved accuracy and efficiency in the development process.\nEnhanced error detection and prevention.\nStreamlined communication between different parts of the system."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20231112-validation-service.html#potential-downsides",
-    "href": "decisions/20231112-validation-service.html#potential-downsides",
-    "title": "Proposed: Validator Service for V-Sekai",
+    "objectID": "decisions/20240613-training-dataset.html#further-reading",
+    "href": "decisions/20240613-training-dataset.html#further-reading",
+    "title": "Proposed: Dataset Scaling for Training Mesh Transformer",
     "section": "",
-    "text": "Potential challenges or downsides could include:\n\nComplexity in setting up and maintaining the validator service.\nNeed for thorough testing to ensure the validator service works as expected."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20231112-validation-service.html#alternatives-considered",
-    "href": "decisions/20231112-validation-service.html#alternatives-considered",
-    "title": "Proposed: Validator Service for V-Sekai",
+    "objectID": "decisions/20240305-v-sekai-launcher.html",
+    "href": "decisions/20240305-v-sekai-launcher.html",
+    "title": "Proposed: V-Sekai Game Launcher",
     "section": "",
-    "text": "An alternative approach could be to use gdscript + webrtc instead of websockets + API for communication and function calls. However, this would need to be evaluated for feasibility and efficiency."
+    "text": "The game project’s current distribution and dependency management is a challenge. The existing setup, which involves a Godot project with multiple add-ons, is complex and challenging to manage and distribute.\n\n\n\n\nThe editor plugin is deeply intertwined with the gameplay elements, making it hard to develop.\nWe aim to make the editor plugin lightweight and easy to distribute so that users can easily incorporate it into their regular projects to convert their existing Godot content into V-Sekai-compatible content.\nThere is a code duplication problem between vsk_game and vsk_editor/sdk.\nWe must consider what changes we can make to the plugin’s design to make it more user-friendly.\nThe lack of a package manager and universal plugins or a dependency graph for plugins is a significant issue, potentially overlapping with a core problem in Godot.\n\nThe priority question is how to transform this into an SDK with the cleanest possible distribution method.\n\n\n\nTo address these issues, we propose the creation of a V-Sekai Game Launcher. This launcher will be built using Godot and will replace the regular Godot project manager. It will handle all package-related tasks, ensuring smooth distribution and dependency management.\n\n\n\n\nSimplified distribution: The launcher will handle the distribution of the game, making it easier for users to access and install the game.\nImproved dependency management: The launcher will also manage the game’s dependencies, resolving the current issues faced due to the lack of a package manager.\nEnhanced user experience: With the launcher handling package and project management, users can focus on creating content or playing the game.\n\n\n\n\n\nDevelopment time: Building a new launcher will require additional development time and resources.\nUser adoption: Users may need time to adapt to the new launcher and its functionalities.\n\n\n\n\nAn alternative solution considered was to use the Godot Asset Store for distribution. However, it does not solve the dependency management problem and is not ready yet for such a task.\n\n\n\nIn cases where users want to manage their packages manually or prefer using the regular Godot project manager, they may find the launcher unnecessary or intrusive.\n\n\n\nThe V-Sekai development team will develop the V-Sekai Game Launcher.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team and community stakeholders.\n\n\n\n\n\nV-Sekai, Avatar Customization, AI, Facial Expressions, Game Launcher\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this proposal."
   },
   {
-    "objectID": "decisions/20231112-validation-service.html#next-steps",
-    "href": "decisions/20231112-validation-service.html#next-steps",
-    "title": "Proposed: Validator Service for V-Sekai",
+    "objectID": "decisions/20240305-v-sekai-launcher.html#the-context",
+    "href": "decisions/20240305-v-sekai-launcher.html#the-context",
+    "title": "Proposed: V-Sekai Game Launcher",
     "section": "",
-    "text": "The next steps would be to:\n\nFinalize the specification for the validator service.\nDevelop the validator service according to the agreed-upon specification.\nTest the validator service thoroughly to ensure it works as expected.\nImplement the validator service in the V-Sekai system."
+    "text": "The game project’s current distribution and dependency management is a challenge. The existing setup, which involves a Godot project with multiple add-ons, is complex and challenging to manage and distribute."
   },
   {
-    "objectID": "decisions/20231112-validation-service.html#references",
-    "href": "decisions/20231112-validation-service.html#references",
-    "title": "Proposed: Validator Service for V-Sekai",
+    "objectID": "decisions/20240305-v-sekai-launcher.html#the-problem-statement",
+    "href": "decisions/20240305-v-sekai-launcher.html#the-problem-statement",
+    "title": "Proposed: V-Sekai Game Launcher",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nThis proposal was assisted by AI assistant Aria."
+    "text": "The editor plugin is deeply intertwined with the gameplay elements, making it hard to develop.\nWe aim to make the editor plugin lightweight and easy to distribute so that users can easily incorporate it into their regular projects to convert their existing Godot content into V-Sekai-compatible content.\nThere is a code duplication problem between vsk_game and vsk_editor/sdk.\nWe must consider what changes we can make to the plugin’s design to make it more user-friendly.\nThe lack of a package manager and universal plugins or a dependency graph for plugins is a significant issue, potentially overlapping with a core problem in Godot.\n\nThe priority question is how to transform this into an SDK with the cleanest possible distribution method."
   },
   {
-    "objectID": "decisions/20240121-install-tailscale.html",
-    "href": "decisions/20240121-install-tailscale.html",
-    "title": "Proposed: Installing Tailscale on Linux Fedora 39",
+    "objectID": "decisions/20240305-v-sekai-launcher.html#proposed-solution",
+    "href": "decisions/20240305-v-sekai-launcher.html#proposed-solution",
+    "title": "Proposed: V-Sekai Game Launcher",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nIn the current digital age, secure and efficient networking is a necessity. Tailscale provides a secure network connection between devices, regardless of location. This proposal aims to guide the installation of Tailscale on Linux Fedora 39.\n\n\n\nThe challenge lies in setting up Tailscale on Linux Fedora 39. The process involves adding the Tailscale repository, installing the software, enabling the service, and connecting to the Tailscale network.\n\n\n\nHere’s a concise step-by-step guide:\n# Add the Tailscale repository\nsudo dnf config-manager --add-repo https://pkgs.tailscale.com/stable/rhel/8/tailscale.repo\n\n# Install Tailscale\nsudo dnf install tailscale -y\n\n# Enable and start the service\nsudo systemctl enable --now tailscaled\n\n# Connect to your Tailscale network and authenticate in your browser\nsudo tailscale up\n\n# Find your Tailscale IPv4 address\ntailscale ip -4\n\n# Disable key expiry\n\n\n\n\nSecure: Tailscale uses end-to-end encryption for all traffic.\nEasy to set up: The process is straightforward and can be done quickly.\nScalable: Tailscale can handle connections between a large number of devices.\n\n\n\n\n\nRequires internet access: Tailscale requires an active internet connection to establish the network.\nCompatibility issues: There may be compatibility issues with certain applications or systems.\n\n\n\n\n\nOpenVPN: A well-established VPN solution, but it requires more complex setup and maintenance.\nWireGuard: Another VPN solution that is simpler and faster but less mature.\n\n\n\n\nThis solution is particularly useful for remote teams who need to access shared resources securely, or for individuals who want to connect their devices in a private network.\n\n\n\nIn-house development of a similar solution would require significant resources and expertise in networking and security. It is more cost-effective and efficient to use an existing solution like Tailscale.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis proposal was assisted by Aria, the AI assistant."
+    "text": "To address these issues, we propose the creation of a V-Sekai Game Launcher. This launcher will be built using Godot and will replace the regular Godot project manager. It will handle all package-related tasks, ensuring smooth distribution and dependency management."
   },
   {
-    "objectID": "decisions/20240121-install-tailscale.html#metadata",
-    "href": "decisions/20240121-install-tailscale.html#metadata",
-    "title": "Proposed: Installing Tailscale on Linux Fedora 39",
+    "objectID": "decisions/20240305-v-sekai-launcher.html#the-benefits",
+    "href": "decisions/20240305-v-sekai-launcher.html#the-benefits",
+    "title": "Proposed: V-Sekai Game Launcher",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai"
+    "text": "Simplified distribution: The launcher will handle the distribution of the game, making it easier for users to access and install the game.\nImproved dependency management: The launcher will also manage the game’s dependencies, resolving the current issues faced due to the lack of a package manager.\nEnhanced user experience: With the launcher handling package and project management, users can focus on creating content or playing the game."
   },
   {
-    "objectID": "decisions/20240121-install-tailscale.html#context",
-    "href": "decisions/20240121-install-tailscale.html#context",
-    "title": "Proposed: Installing Tailscale on Linux Fedora 39",
+    "objectID": "decisions/20240305-v-sekai-launcher.html#the-downsides",
+    "href": "decisions/20240305-v-sekai-launcher.html#the-downsides",
+    "title": "Proposed: V-Sekai Game Launcher",
     "section": "",
-    "text": "In the current digital age, secure and efficient networking is a necessity. Tailscale provides a secure network connection between devices, regardless of location. This proposal aims to guide the installation of Tailscale on Linux Fedora 39."
+    "text": "Development time: Building a new launcher will require additional development time and resources.\nUser adoption: Users may need time to adapt to the new launcher and its functionalities."
   },
   {
-    "objectID": "decisions/20240121-install-tailscale.html#problem",
-    "href": "decisions/20240121-install-tailscale.html#problem",
-    "title": "Proposed: Installing Tailscale on Linux Fedora 39",
+    "objectID": "decisions/20240305-v-sekai-launcher.html#the-road-not-taken",
+    "href": "decisions/20240305-v-sekai-launcher.html#the-road-not-taken",
+    "title": "Proposed: V-Sekai Game Launcher",
     "section": "",
-    "text": "The challenge lies in setting up Tailscale on Linux Fedora 39. The process involves adding the Tailscale repository, installing the software, enabling the service, and connecting to the Tailscale network."
+    "text": "An alternative solution considered was to use the Godot Asset Store for distribution. However, it does not solve the dependency management problem and is not ready yet for such a task."
   },
   {
-    "objectID": "decisions/20240121-install-tailscale.html#solution",
-    "href": "decisions/20240121-install-tailscale.html#solution",
-    "title": "Proposed: Installing Tailscale on Linux Fedora 39",
+    "objectID": "decisions/20240305-v-sekai-launcher.html#the-infrequent-use-case",
+    "href": "decisions/20240305-v-sekai-launcher.html#the-infrequent-use-case",
+    "title": "Proposed: V-Sekai Game Launcher",
     "section": "",
-    "text": "Here’s a concise step-by-step guide:\n# Add the Tailscale repository\nsudo dnf config-manager --add-repo https://pkgs.tailscale.com/stable/rhel/8/tailscale.repo\n\n# Install Tailscale\nsudo dnf install tailscale -y\n\n# Enable and start the service\nsudo systemctl enable --now tailscaled\n\n# Connect to your Tailscale network and authenticate in your browser\nsudo tailscale up\n\n# Find your Tailscale IPv4 address\ntailscale ip -4\n\n# Disable key expiry"
+    "text": "In cases where users want to manage their packages manually or prefer using the regular Godot project manager, they may find the launcher unnecessary or intrusive."
   },
   {
-    "objectID": "decisions/20240121-install-tailscale.html#pros",
-    "href": "decisions/20240121-install-tailscale.html#pros",
-    "title": "Proposed: Installing Tailscale on Linux Fedora 39",
+    "objectID": "decisions/20240305-v-sekai-launcher.html#in-core-and-done-by-us",
+    "href": "decisions/20240305-v-sekai-launcher.html#in-core-and-done-by-us",
+    "title": "Proposed: V-Sekai Game Launcher",
     "section": "",
-    "text": "Secure: Tailscale uses end-to-end encryption for all traffic.\nEasy to set up: The process is straightforward and can be done quickly.\nScalable: Tailscale can handle connections between a large number of devices."
+    "text": "The V-Sekai development team will develop the V-Sekai Game Launcher."
   },
   {
-    "objectID": "decisions/20240121-install-tailscale.html#cons",
-    "href": "decisions/20240121-install-tailscale.html#cons",
-    "title": "Proposed: Installing Tailscale on Linux Fedora 39",
+    "objectID": "decisions/20240305-v-sekai-launcher.html#status",
+    "href": "decisions/20240305-v-sekai-launcher.html#status",
+    "title": "Proposed: V-Sekai Game Launcher",
     "section": "",
-    "text": "Requires internet access: Tailscale requires an active internet connection to establish the network.\nCompatibility issues: There may be compatibility issues with certain applications or systems."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20240121-install-tailscale.html#alternatives-considered",
-    "href": "decisions/20240121-install-tailscale.html#alternatives-considered",
-    "title": "Proposed: Installing Tailscale on Linux Fedora 39",
+    "objectID": "decisions/20240305-v-sekai-launcher.html#decision-makers",
+    "href": "decisions/20240305-v-sekai-launcher.html#decision-makers",
+    "title": "Proposed: V-Sekai Game Launcher",
     "section": "",
-    "text": "OpenVPN: A well-established VPN solution, but it requires more complex setup and maintenance.\nWireGuard: Another VPN solution that is simpler and faster but less mature."
+    "text": "V-Sekai development team and community stakeholders."
   },
   {
-    "objectID": "decisions/20240121-install-tailscale.html#rare-use-case",
-    "href": "decisions/20240121-install-tailscale.html#rare-use-case",
-    "title": "Proposed: Installing Tailscale on Linux Fedora 39",
+    "objectID": "decisions/20240305-v-sekai-launcher.html#tags",
+    "href": "decisions/20240305-v-sekai-launcher.html#tags",
+    "title": "Proposed: V-Sekai Game Launcher",
     "section": "",
-    "text": "This solution is particularly useful for remote teams who need to access shared resources securely, or for individuals who want to connect their devices in a private network."
+    "text": "V-Sekai, Avatar Customization, AI, Facial Expressions, Game Launcher"
   },
   {
-    "objectID": "decisions/20240121-install-tailscale.html#in-house-development",
-    "href": "decisions/20240121-install-tailscale.html#in-house-development",
-    "title": "Proposed: Installing Tailscale on Linux Fedora 39",
+    "objectID": "decisions/20240305-v-sekai-launcher.html#further-reading",
+    "href": "decisions/20240305-v-sekai-launcher.html#further-reading",
+    "title": "Proposed: V-Sekai Game Launcher",
     "section": "",
-    "text": "In-house development of a similar solution would require significant resources and expertise in networking and security. It is more cost-effective and efficient to use an existing solution like Tailscale."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this proposal."
   },
   {
-    "objectID": "decisions/20240121-install-tailscale.html#references",
-    "href": "decisions/20240121-install-tailscale.html#references",
-    "title": "Proposed: Installing Tailscale on Linux Fedora 39",
+    "objectID": "decisions/20240627-every-commit-push-pass-cicd.html",
+    "href": "decisions/20240627-every-commit-push-pass-cicd.html",
+    "title": "Proposed: Every Commit Push Pass Cicd",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis proposal was assisted by Aria, the AI assistant."
+    "text": "We are working on V-Sekai, a virtual reality social network. Our development workflow involves multiple developers making frequent changes to the codebase.\n\n\n\nWe have trouble understanding the logical flow of work. This is causing delays in development and making it difficult to track changes and debug issues. Currently, our commits are checked after they are merged into the main branch, which can lead to problems if the commit does not pass the checks.\n\n\n\nThe proposal is to implement a system where every commit and push operation passes through our CI/CD pipeline as a logical unit before being checked into the main branch. This means that each commit will trigger a build and test process, ensuring that all changes are validated before they are merged.\nOn every commit:\n  Trigger CI/CD pipeline\n    Build application\n    Run tests\nIf tests pass:\n  Allow check-in to main branch\nElse:\n  Return error and prevent check-in\n\n\n\n\nImproved traceability of changes\nFaster identification and resolution of issues\nMore efficient development workflow\nPrevention of problematic commits entering the main branch\n\n\n\n\n\nPotential increase in build times\nRequires investment in robust testing infrastructure\n\n\n\n\nAn alternative approach could be to only run the CI/CD pipeline on specific branches or at specific times. However, this would not provide the same level of validation and could lead to issues being missed.\n\n\n\nIn cases where commits are made infrequently, this approach may result in longer periods between builds. However, the benefits of improved traceability and issue resolution outweigh this potential downside.\n\n\n\nThis change will be implemented by the V-Sekai development team and will become a core part of our development workflow.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240522-discord-bot.html",
-    "href": "decisions/20240522-discord-bot.html",
-    "title": "Draft: Notify community members and users about activity and updates via a Discord bot",
+    "objectID": "decisions/20240627-every-commit-push-pass-cicd.html#the-context",
+    "href": "decisions/20240627-every-commit-push-pass-cicd.html#the-context",
+    "title": "Proposed: Every Commit Push Pass Cicd",
     "section": "",
-    "text": "Status: draft\n\n\n\nWe want a way to notify community members and users about activity and updates.\n\n\n\nA discord bot would be able to inform users via Discord about updates and changes.\n\n\n\nWe would connect to Discord API from Elixir using one of several integration libraries.\nWe can report #information such as server player count by editing a message; or updating the bot status.\nI would also like to poll #information such as CI/CD builds and deployments. We could make an API where someone or something can post a message displayed in Discord using curl or some command, though we would have to make sure this is locked behind a secret key. Unclear.\n\n\n\n\nGrow the community\nHelp us manage the project\n\n\n\n\n\nMaintenance costs of having a service fed"
+    "text": "We are working on V-Sekai, a virtual reality social network. Our development workflow involves multiple developers making frequent changes to the codebase."
   },
   {
-    "objectID": "decisions/20240522-discord-bot.html#context-and-problem-statement",
-    "href": "decisions/20240522-discord-bot.html#context-and-problem-statement",
-    "title": "Draft: Notify community members and users about activity and updates via a Discord bot",
+    "objectID": "decisions/20240627-every-commit-push-pass-cicd.html#the-problem-statement",
+    "href": "decisions/20240627-every-commit-push-pass-cicd.html#the-problem-statement",
+    "title": "Proposed: Every Commit Push Pass Cicd",
     "section": "",
-    "text": "We want a way to notify community members and users about activity and updates."
+    "text": "We have trouble understanding the logical flow of work. This is causing delays in development and making it difficult to track changes and debug issues. Currently, our commits are checked after they are merged into the main branch, which can lead to problems if the commit does not pass the checks."
   },
   {
-    "objectID": "decisions/20240522-discord-bot.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20240522-discord-bot.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Draft: Notify community members and users about activity and updates via a Discord bot",
+    "objectID": "decisions/20240627-every-commit-push-pass-cicd.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240627-every-commit-push-pass-cicd.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Every Commit Push Pass Cicd",
     "section": "",
-    "text": "A discord bot would be able to inform users via Discord about updates and changes."
+    "text": "The proposal is to implement a system where every commit and push operation passes through our CI/CD pipeline as a logical unit before being checked into the main branch. This means that each commit will trigger a build and test process, ensuring that all changes are validated before they are merged.\nOn every commit:\n  Trigger CI/CD pipeline\n    Build application\n    Run tests\nIf tests pass:\n  Allow check-in to main branch\nElse:\n  Return error and prevent check-in"
   },
   {
-    "objectID": "decisions/20240522-discord-bot.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240522-discord-bot.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Draft: Notify community members and users about activity and updates via a Discord bot",
+    "objectID": "decisions/20240627-every-commit-push-pass-cicd.html#the-benefits",
+    "href": "decisions/20240627-every-commit-push-pass-cicd.html#the-benefits",
+    "title": "Proposed: Every Commit Push Pass Cicd",
     "section": "",
-    "text": "We would connect to Discord API from Elixir using one of several integration libraries.\nWe can report #information such as server player count by editing a message; or updating the bot status.\nI would also like to poll #information such as CI/CD builds and deployments. We could make an API where someone or something can post a message displayed in Discord using curl or some command, though we would have to make sure this is locked behind a secret key. Unclear."
+    "text": "Improved traceability of changes\nFaster identification and resolution of issues\nMore efficient development workflow\nPrevention of problematic commits entering the main branch"
   },
   {
-    "objectID": "decisions/20240522-discord-bot.html#positive-consequences",
-    "href": "decisions/20240522-discord-bot.html#positive-consequences",
-    "title": "Draft: Notify community members and users about activity and updates via a Discord bot",
+    "objectID": "decisions/20240627-every-commit-push-pass-cicd.html#the-downsides",
+    "href": "decisions/20240627-every-commit-push-pass-cicd.html#the-downsides",
+    "title": "Proposed: Every Commit Push Pass Cicd",
     "section": "",
-    "text": "Grow the community\nHelp us manage the project"
+    "text": "Potential increase in build times\nRequires investment in robust testing infrastructure"
   },
   {
-    "objectID": "decisions/20240522-discord-bot.html#negative-consequences",
-    "href": "decisions/20240522-discord-bot.html#negative-consequences",
-    "title": "Draft: Notify community members and users about activity and updates via a Discord bot",
+    "objectID": "decisions/20240627-every-commit-push-pass-cicd.html#the-road-not-taken",
+    "href": "decisions/20240627-every-commit-push-pass-cicd.html#the-road-not-taken",
+    "title": "Proposed: Every Commit Push Pass Cicd",
     "section": "",
-    "text": "Maintenance costs of having a service fed"
-  },
-  {
-    "objectID": "decisions/20240522-discord-bot.html#positive-consequences-1",
-    "href": "decisions/20240522-discord-bot.html#positive-consequences-1",
-    "title": "Draft: Notify community members and users about activity and updates via a Discord bot",
-    "section": "Positive Consequences",
-    "text": "Positive Consequences\n\nLower maintenance burden"
+    "text": "An alternative approach could be to only run the CI/CD pipeline on specific branches or at specific times. However, this would not provide the same level of validation and could lead to issues being missed."
   },
   {
-    "objectID": "decisions/20240522-discord-bot.html#negative-consequences-1",
-    "href": "decisions/20240522-discord-bot.html#negative-consequences-1",
-    "title": "Draft: Notify community members and users about activity and updates via a Discord bot",
-    "section": "Negative Consequences",
-    "text": "Negative Consequences\n\nNo access to commands or statuses. Only capable of posting messages."
+    "objectID": "decisions/20240627-every-commit-push-pass-cicd.html#the-infrequent-use-case",
+    "href": "decisions/20240627-every-commit-push-pass-cicd.html#the-infrequent-use-case",
+    "title": "Proposed: Every Commit Push Pass Cicd",
+    "section": "",
+    "text": "In cases where commits are made infrequently, this approach may result in longer periods between builds. However, the benefits of improved traceability and issue resolution outweigh this potential downside."
   },
   {
-    "objectID": "decisions/20240522-discord-bot.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20240522-discord-bot.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Draft: Notify community members and users about activity and updates via a Discord bot",
-    "section": "If this enhancement will not be used often, can it be worked around with a few lines of script?",
-    "text": "If this enhancement will not be used often, can it be worked around with a few lines of script?\nYes, it is possible to script querying the itch.io or Uro shards API. This proposal aims to make this #information more accessible to those who would not script it."
+    "objectID": "decisions/20240627-every-commit-push-pass-cicd.html#in-core-and-done-by-us",
+    "href": "decisions/20240627-every-commit-push-pass-cicd.html#in-core-and-done-by-us",
+    "title": "Proposed: Every Commit Push Pass Cicd",
+    "section": "",
+    "text": "This change will be implemented by the V-Sekai development team and will become a core part of our development workflow."
   },
   {
-    "objectID": "decisions/20240522-discord-bot.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20240522-discord-bot.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Draft: Notify community members and users about activity and updates via a Discord bot",
-    "section": "Is there a reason why this should be core and done by us?",
-    "text": "Is there a reason why this should be core and done by us?\nWe need this to grow the community."
+    "objectID": "decisions/20240627-every-commit-push-pass-cicd.html#status",
+    "href": "decisions/20240627-every-commit-push-pass-cicd.html#status",
+    "title": "Proposed: Every Commit Push Pass Cicd",
+    "section": "",
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20240522-discord-bot.html#derivative-license",
-    "href": "decisions/20240522-discord-bot.html#derivative-license",
-    "title": "Draft: Notify community members and users about activity and updates via a Discord bot",
-    "section": "Derivative License",
-    "text": "Derivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "objectID": "decisions/20240627-every-commit-push-pass-cicd.html#decision-makers",
+    "href": "decisions/20240627-every-commit-push-pass-cicd.html#decision-makers",
+    "title": "Proposed: Every Commit Push Pass Cicd",
+    "section": "",
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20211220-network-the-ubisoft-mixer-server.html",
-    "href": "decisions/20211220-network-the-ubisoft-mixer-server.html",
-    "title": "Rejected: Network the Ubisoft Mixer server",
+    "objectID": "decisions/20240627-every-commit-push-pass-cicd.html#tags",
+    "href": "decisions/20240627-every-commit-push-pass-cicd.html#tags",
+    "title": "Proposed: Every Commit Push Pass Cicd",
     "section": "",
-    "text": "Status: rejected \nDeciders: V-Sekai,fire,\nTags: V-Sekai,\n\n\n\nWe want to use the Ubisoft Mixer project more easily.\nThe Ubisoft mixer project is also a good way to share Godot Engine scenes.\nThe problem is the mixer project is in Python and doesn’t have file sync.\n\n\n\nMy proposed solution is to write a elixir server that syncs the Blender file and the file share.\n\n\n\n\nExtract Mixer broadcaster code\nWrite an Elixir udp based broadcaster with webrtc\nWrite an Elixir file sync (SECURITY WARNING)\n\n\n\n\n\nEasier to host mixer.\n\n\n\n\n\nThe software may be a vector for security attacks.\n\n\n\n\n\nOption: Use V-Sekai as a networking sync.\nRejection Reason: Not ready yet and someone is working on it.\n\n\n\n\nNot a few lines of script.\n\n\n\nI know how to do this and no one else is doing it.\n\n\n\n\nhttps://github.com/ubisoft/mixer/issues\n\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20211220-network-the-ubisoft-mixer-server.html#context-and-problem-statement",
-    "href": "decisions/20211220-network-the-ubisoft-mixer-server.html#context-and-problem-statement",
-    "title": "Rejected: Network the Ubisoft Mixer server",
+    "objectID": "decisions/20240627-every-commit-push-pass-cicd.html#further-reading",
+    "href": "decisions/20240627-every-commit-push-pass-cicd.html#further-reading",
+    "title": "Proposed: Every Commit Push Pass Cicd",
     "section": "",
-    "text": "We want to use the Ubisoft Mixer project more easily.\nThe Ubisoft mixer project is also a good way to share Godot Engine scenes.\nThe problem is the mixer project is in Python and doesn’t have file sync."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20211220-network-the-ubisoft-mixer-server.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20211220-network-the-ubisoft-mixer-server.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Rejected: Network the Ubisoft Mixer server",
+    "objectID": "decisions/20240314-live-collab.html",
+    "href": "decisions/20240314-live-collab.html",
+    "title": "Proposed: Real-Time Motion Capture and Animation Synchronization",
     "section": "",
-    "text": "My proposed solution is to write a elixir server that syncs the Blender file and the file share."
+    "text": "In the context of V-Sekai, a VR social network, we are looking to enhance the user experience by introducing real-time motion capture and animation synchronization features. This would allow users to interact with each other in real-time within the Godot engine.\n\n\n\nCurrently, there’s no mechanism for real-time synchronization of skeleton motion capture (mocap), blend shape animations, and skeleton animations between different users. This limits the interactive capabilities of the platform and hinders the creation of a truly immersive virtual environment.\n\n\n\nWe propose to extend the live collaboration feature to include real-time synchronization of mocap and animations. This will enable users to see each other’s movements and expressions in real-time, further enhancing the interactivity of the platform.\n\n\n\n\nReal-Time Interaction: Users can see each other’s movements and expressions in real-time, creating a more immersive and interactive experience.\nAnimation Synchronization: Changes made to the animations by one user are instantly visible to others.\nEnhanced User Experience: The ability to interact with each other in a more realistic manner greatly enhances the overall user experience.\n\n\n\n\n\nIncreased Complexity: The addition of mocap and animation synchronization could increase the complexity of the project.\nPerformance Impact: Real-time synchronization of animations could have an impact on performance, especially for users with slower internet connections.\n\n\n\n\nThe minimum viable product would include the ability to move a model around on one machine and have those positions updated on another, as well as the ability to perform basic animations that are visible to other users. Given the simplicity of the Godot scene format, this should be achievable.\n\n\n\nThe V-Sekai team will implement this feature.\n\n\n\nProposed\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\nGodot\nLive Collaboration\nMotion Capture\nAnimation Synchronization\n\n\n\n\n\nV-Sekai · GitHub\nV-Sekai/v-sekai-game\n\nAssisted by Aria, an AI assistant."
   },
   {
-    "objectID": "decisions/20211220-network-the-ubisoft-mixer-server.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20211220-network-the-ubisoft-mixer-server.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Rejected: Network the Ubisoft Mixer server",
+    "objectID": "decisions/20240314-live-collab.html#context",
+    "href": "decisions/20240314-live-collab.html#context",
+    "title": "Proposed: Real-Time Motion Capture and Animation Synchronization",
     "section": "",
-    "text": "Extract Mixer broadcaster code\nWrite an Elixir udp based broadcaster with webrtc\nWrite an Elixir file sync (SECURITY WARNING)"
+    "text": "In the context of V-Sekai, a VR social network, we are looking to enhance the user experience by introducing real-time motion capture and animation synchronization features. This would allow users to interact with each other in real-time within the Godot engine."
   },
   {
-    "objectID": "decisions/20211220-network-the-ubisoft-mixer-server.html#positive-consequences",
-    "href": "decisions/20211220-network-the-ubisoft-mixer-server.html#positive-consequences",
-    "title": "Rejected: Network the Ubisoft Mixer server",
+    "objectID": "decisions/20240314-live-collab.html#problem",
+    "href": "decisions/20240314-live-collab.html#problem",
+    "title": "Proposed: Real-Time Motion Capture and Animation Synchronization",
     "section": "",
-    "text": "Easier to host mixer."
+    "text": "Currently, there’s no mechanism for real-time synchronization of skeleton motion capture (mocap), blend shape animations, and skeleton animations between different users. This limits the interactive capabilities of the platform and hinders the creation of a truly immersive virtual environment."
   },
   {
-    "objectID": "decisions/20211220-network-the-ubisoft-mixer-server.html#negative-consequences",
-    "href": "decisions/20211220-network-the-ubisoft-mixer-server.html#negative-consequences",
-    "title": "Rejected: Network the Ubisoft Mixer server",
+    "objectID": "decisions/20240314-live-collab.html#solution",
+    "href": "decisions/20240314-live-collab.html#solution",
+    "title": "Proposed: Real-Time Motion Capture and Animation Synchronization",
     "section": "",
-    "text": "The software may be a vector for security attacks."
+    "text": "We propose to extend the live collaboration feature to include real-time synchronization of mocap and animations. This will enable users to see each other’s movements and expressions in real-time, further enhancing the interactivity of the platform."
   },
   {
-    "objectID": "decisions/20211220-network-the-ubisoft-mixer-server.html#option-graveyard",
-    "href": "decisions/20211220-network-the-ubisoft-mixer-server.html#option-graveyard",
-    "title": "Rejected: Network the Ubisoft Mixer server",
+    "objectID": "decisions/20240314-live-collab.html#benefits",
+    "href": "decisions/20240314-live-collab.html#benefits",
+    "title": "Proposed: Real-Time Motion Capture and Animation Synchronization",
     "section": "",
-    "text": "Option: Use V-Sekai as a networking sync.\nRejection Reason: Not ready yet and someone is working on it."
+    "text": "Real-Time Interaction: Users can see each other’s movements and expressions in real-time, creating a more immersive and interactive experience.\nAnimation Synchronization: Changes made to the animations by one user are instantly visible to others.\nEnhanced User Experience: The ability to interact with each other in a more realistic manner greatly enhances the overall user experience."
   },
   {
-    "objectID": "decisions/20211220-network-the-ubisoft-mixer-server.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20211220-network-the-ubisoft-mixer-server.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Rejected: Network the Ubisoft Mixer server",
+    "objectID": "decisions/20240314-live-collab.html#downsides",
+    "href": "decisions/20240314-live-collab.html#downsides",
+    "title": "Proposed: Real-Time Motion Capture and Animation Synchronization",
     "section": "",
-    "text": "Not a few lines of script."
+    "text": "Increased Complexity: The addition of mocap and animation synchronization could increase the complexity of the project.\nPerformance Impact: Real-time synchronization of animations could have an impact on performance, especially for users with slower internet connections."
   },
   {
-    "objectID": "decisions/20211220-network-the-ubisoft-mixer-server.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20211220-network-the-ubisoft-mixer-server.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Rejected: Network the Ubisoft Mixer server",
+    "objectID": "decisions/20240314-live-collab.html#mvp",
+    "href": "decisions/20240314-live-collab.html#mvp",
+    "title": "Proposed: Real-Time Motion Capture and Animation Synchronization",
     "section": "",
-    "text": "I know how to do this and no one else is doing it."
+    "text": "The minimum viable product would include the ability to move a model around on one machine and have those positions updated on another, as well as the ability to perform basic animations that are visible to other users. Given the simplicity of the Godot scene format, this should be achievable."
   },
   {
-    "objectID": "decisions/20211220-network-the-ubisoft-mixer-server.html#references",
-    "href": "decisions/20211220-network-the-ubisoft-mixer-server.html#references",
-    "title": "Rejected: Network the Ubisoft Mixer server",
+    "objectID": "decisions/20240314-live-collab.html#implementation",
+    "href": "decisions/20240314-live-collab.html#implementation",
+    "title": "Proposed: Real-Time Motion Capture and Animation Synchronization",
     "section": "",
-    "text": "https://github.com/ubisoft/mixer/issues"
+    "text": "The V-Sekai team will implement this feature."
   },
   {
-    "objectID": "decisions/20211220-network-the-ubisoft-mixer-server.html#derivative-license",
-    "href": "decisions/20211220-network-the-ubisoft-mixer-server.html#derivative-license",
-    "title": "Rejected: Network the Ubisoft Mixer server",
+    "objectID": "decisions/20240314-live-collab.html#status",
+    "href": "decisions/20240314-live-collab.html#status",
+    "title": "Proposed: Real-Time Motion Capture and Animation Synchronization",
     "section": "",
-    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Proposed"
   },
   {
-    "objectID": "decisions/20211031-verification-tools.html",
-    "href": "decisions/20211031-verification-tools.html",
-    "title": "Draft: Verification tools",
+    "objectID": "decisions/20240314-live-collab.html#decision-makers",
+    "href": "decisions/20240314-live-collab.html#decision-makers",
+    "title": "Proposed: Real-Time Motion Capture and Animation Synchronization",
     "section": "",
-    "text": "Draft: Verification tools\n\nContext and Problem Statement\nNeed to verify color, motion and scale\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nProduce a reference for color, motion and scene scales.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n\nColor using industry standard reference chart\nRange of motion animations\nMeter scale tests\n100 avatar bottleneck test\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNo.\n\n\nPositive Consequences\nNeed to standardize\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nOnly we can set standards\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20241014-basic-realtime-interaction.html",
-    "href": "decisions/20241014-basic-realtime-interaction.html",
-    "title": "Proposed: Basic Real-Time Interaction for Character and World Scenes",
+    "objectID": "decisions/20240314-live-collab.html#tags",
+    "href": "decisions/20240314-live-collab.html#tags",
+    "title": "Proposed: Real-Time Motion Capture and Animation Synchronization",
     "section": "",
-    "text": "The project will enable users to interact in real-time by manipulating objects within a shared virtual environment, enhancing the user experience.\n\n\n\nI want to extend V-Sekai’s functionality to support real-time interaction with uploaded character and world scenes. This includes the ability for users to manipulate objects within the scene and have those changes reflected in real-time for other users connected to the same session. Additionally, seamless integration of new elements into the environment is crucial.\nHere’s a detailed breakdown of the features we plan to implement:\n\nReal-time Interaction: Users can move and rotate objects in the scene. Changes appear instantly, providing immediate visual feedback.\nNetworked Synchronization: When one user modifies something, the change is immediately visible to all other users in the same session.\nObject Persistence: Users can save their current scene setup to continue working on it later or retrieve it in another session.\nDynamic Environment Integration: Facilitate the introduction of new interactive elements during live sessions.\nMediator Role: A special user, called a mediator, can manage permissions like who can move what, start or end the session, and oversee interactions between users.\nLimited Scope: Initially, this feature will support multiple users interacting in one scene without additional complexities like handling multiple scenes or advanced physics.\n\nThis upgrade leverages the existing functionality of V-Sekai for uploading and rendering game engine assets. It assumes the utilization of V-Sekai’s current game engine and networking capabilities, or the integration of clearly specified, readily available libraries or services to achieve the desired real-time interaction and synchronization.\n\n\n\n\n\n[Scene Interaction Mock-up]\n+------------------------------------------------+\n|                                                |\n|  [User1]                                       |\n|    * (Object1) &lt;-- [Moving]                    |\n|                                                |\n|  [Tool Switcher Pie Menu]                      |\n|    - Move Tool                                 |\n|    - Rotate Tool                               |\n|    - Close                                     |\n|                                                |\n|  [User2]                                       |\n|    * (Object2)                                 |\n|                                                |\n+------------------------------------------------+\n\n\n\n\nEnhanced user engagement allows users to interact dynamically with objects, increasing the sense of presence. Establishing basic functionalities lays the foundation for future features that can include more complex interactions. Immediate feedback is crucial for collaborative environments, and intuitive tool selection through the Tool Switcher Pie Menu enhances workflow efficiency.\n\n\n\nThe initial features are limited to basic manipulations, which might not meet all user expectations. As the user base grows, the current simple synchronization mechanism may need significant enhancements.\n\n\n\nA full-scale interaction suite was initially considered, including scaling and advanced physics, but it was decided against due to complexity and resource constraints.\n\n\n\nWhile the system is designed for multiple users, it will also support single-user sessions, although this is not the primary focus.\n\n\n\nThis feature is core to the project’s mission of enhancing interactive capabilities and will be developed internally to ensure seamless integration and maintain control over quality.\n\n\n\nStatus: Proposed \n\n\n\n\nProject development team\nFire\nHumble Tim\n\n\n\n\nReal-time interaction, basic object manipulation, networked synchronization, user engagement, virtual collaboration, intuitive tool switching\n\n\n\n\nProject GitHub - Official GitHub account for the project development community focusing on enhancing virtual interaction capabilities.\nProject Documentation - Comprehensive documentation on the project’s features and development guidelines.\n\nAI assistant Aria assisted with this article."
+    "text": "V-Sekai\nGodot\nLive Collaboration\nMotion Capture\nAnimation Synchronization"
   },
   {
-    "objectID": "decisions/20241014-basic-realtime-interaction.html#the-context",
-    "href": "decisions/20241014-basic-realtime-interaction.html#the-context",
-    "title": "Proposed: Basic Real-Time Interaction for Character and World Scenes",
+    "objectID": "decisions/20240314-live-collab.html#further-reading",
+    "href": "decisions/20240314-live-collab.html#further-reading",
+    "title": "Proposed: Real-Time Motion Capture and Animation Synchronization",
     "section": "",
-    "text": "The project will enable users to interact in real-time by manipulating objects within a shared virtual environment, enhancing the user experience."
+    "text": "V-Sekai · GitHub\nV-Sekai/v-sekai-game\n\nAssisted by Aria, an AI assistant."
   },
   {
-    "objectID": "decisions/20241014-basic-realtime-interaction.html#the-problem-statement",
-    "href": "decisions/20241014-basic-realtime-interaction.html#the-problem-statement",
-    "title": "Proposed: Basic Real-Time Interaction for Character and World Scenes",
+    "objectID": "decisions/20240331-vrc-vrm-compatibility.html",
+    "href": "decisions/20240331-vrc-vrm-compatibility.html",
+    "title": "Proposed: VRC and VRM compatibility",
     "section": "",
-    "text": "I want to extend V-Sekai’s functionality to support real-time interaction with uploaded character and world scenes. This includes the ability for users to manipulate objects within the scene and have those changes reflected in real-time for other users connected to the same session. Additionally, seamless integration of new elements into the environment is crucial.\nHere’s a detailed breakdown of the features we plan to implement:\n\nReal-time Interaction: Users can move and rotate objects in the scene. Changes appear instantly, providing immediate visual feedback.\nNetworked Synchronization: When one user modifies something, the change is immediately visible to all other users in the same session.\nObject Persistence: Users can save their current scene setup to continue working on it later or retrieve it in another session.\nDynamic Environment Integration: Facilitate the introduction of new interactive elements during live sessions.\nMediator Role: A special user, called a mediator, can manage permissions like who can move what, start or end the session, and oversee interactions between users.\nLimited Scope: Initially, this feature will support multiple users interacting in one scene without additional complexities like handling multiple scenes or advanced physics.\n\nThis upgrade leverages the existing functionality of V-Sekai for uploading and rendering game engine assets. It assumes the utilization of V-Sekai’s current game engine and networking capabilities, or the integration of clearly specified, readily available libraries or services to achieve the desired real-time interaction and synchronization."
+    "text": "VRChat (VRC) and Virtual Reality Model (VRM) are two popular things used in the creation of virtual reality content. However, they are not inherently compatible with each other, which can cause issues for developers trying to use both in their projects.\n\n\n\nThe lack of compatibility between VRC and VRM can lead to inefficiencies and limitations in the development process. This proposal aims to address this issue by providing a solution that allows for seamless integration of these two groups.\n\n\n\nThe proposed solution involves a series of steps outlined in the README below:\n\nDO NOT remove transparent triangles for [hair, face, body]\nMake sure the Body has all blend shapes deleted.\nAdd face shapes with hana tool\nSplit the skin from the clothing using separate by material.\nOn all the clothing delete vertex groups.\nUse Robust Weight Transfer for Blender to rig clothing\nUnpack the prefab.\nConvert to vrchat. Combine meshes, remove upper chest\nDelete skirt bones that are not used.\nAdd vrcfury direct tree\nAdd vrcfury fix write defaults\nAdd vrcfury anchor override fix\nAdd vrcfury jerry’s templates\nAdd vrcfury unlimited parameters\nMake sure the Body has the perfect sync blend shapes.\nRemember that VRM Mouth Joy is similar to jawOpen.\nRemember that brown down and eye blink can be buggy.\nChoose either the MPEG4 blendshapes or Perfect sync. Delete one or the other.\nRemove empty vrc parameters\nRemove Physbones with missing transforms from secondary.\nConvert bone clusters in sphere colliders to capsule colliders to go from VERY POOR to POOR.\nContinue converting capsules until satisfied “POOR”.\nThe FX controller must match the name and not be temporary.\nUse Auto VRMColliders.\nMake sure all pipeline IDs are detached.\nRemember to delete the upper chest from the humanoid.\nEye look is behind the nose bridge\nMake sure the breast bones are parented as the same bone as the clothing chest bones correspond to.\nCross eyed fix in vrcfury breaks eye tracking.\nUpload. (Pick a new slot. DO NOT REUSE A SLOT.)\n\n\n\n\nvrc sdk base\nvrc sdk avatar\nvrcfury\nvrcft - jerry’s templates\n\n\n\n\n\nin liltoon turn saturation to 2.\n\n\n\n\n\nTry in blender to merge by distance\n\n\n\n\n\n0.0125 m for distance\n15 degrees for angle match\n\n\n\n\n\nCore movement\nEars :3\n\n\n\n\n\nVRCFury blink controller\nVRCFury blend shape optimizer\nVRCFury direct tree optimizer\nVRCFury fix write defaults\nVRCFury unlimited parameters\nVRCFury anchor override fix\nVRCFury GoGo\n\n\n\n\n\nThe proposed solution will allow developers to use VRC and VRM together in their projects, leading to increased flexibility and efficiency.\n\n\n\nThe process may be complex and time-consuming, especially for those unfamiliar with these formats.\n\n\n\nAn alternative approach could involve developing a new format that combines the features of both VRC and VRM. However, this would likely require significant resources and may not be feasible for all developers.\n\n\n\nThis proposal may not be beneficial for developers who only use one of these formats in their projects.\n\n\n\nThe proposed solution has been developed by us and is integrated into our core system.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nvrc-get gui\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n[https://vcc.vrcfury.com]\n[https://Adjerry91.github.io/VRCFaceTracking-Templates/index.json]\n[https://esperecyan.github.io/VRMConverterForVRChat/registry.json]\n[https://vpm.nadena.dev/vpm.json]\n[https://lilxyzw.github.io/vpm-repos/vpm.json]\n[https://fujisunflower.booth.pm/items/2087178]\nVRM Downgrader\nGoGo Loco\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20241014-basic-realtime-interaction.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20241014-basic-realtime-interaction.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Basic Real-Time Interaction for Character and World Scenes",
+    "objectID": "decisions/20240331-vrc-vrm-compatibility.html#the-context",
+    "href": "decisions/20240331-vrc-vrm-compatibility.html#the-context",
+    "title": "Proposed: VRC and VRM compatibility",
     "section": "",
-    "text": "[Scene Interaction Mock-up]\n+------------------------------------------------+\n|                                                |\n|  [User1]                                       |\n|    * (Object1) &lt;-- [Moving]                    |\n|                                                |\n|  [Tool Switcher Pie Menu]                      |\n|    - Move Tool                                 |\n|    - Rotate Tool                               |\n|    - Close                                     |\n|                                                |\n|  [User2]                                       |\n|    * (Object2)                                 |\n|                                                |\n+------------------------------------------------+"
+    "text": "VRChat (VRC) and Virtual Reality Model (VRM) are two popular things used in the creation of virtual reality content. However, they are not inherently compatible with each other, which can cause issues for developers trying to use both in their projects."
   },
   {
-    "objectID": "decisions/20241014-basic-realtime-interaction.html#the-benefits",
-    "href": "decisions/20241014-basic-realtime-interaction.html#the-benefits",
-    "title": "Proposed: Basic Real-Time Interaction for Character and World Scenes",
+    "objectID": "decisions/20240331-vrc-vrm-compatibility.html#the-problem-statement",
+    "href": "decisions/20240331-vrc-vrm-compatibility.html#the-problem-statement",
+    "title": "Proposed: VRC and VRM compatibility",
     "section": "",
-    "text": "Enhanced user engagement allows users to interact dynamically with objects, increasing the sense of presence. Establishing basic functionalities lays the foundation for future features that can include more complex interactions. Immediate feedback is crucial for collaborative environments, and intuitive tool selection through the Tool Switcher Pie Menu enhances workflow efficiency."
+    "text": "The lack of compatibility between VRC and VRM can lead to inefficiencies and limitations in the development process. This proposal aims to address this issue by providing a solution that allows for seamless integration of these two groups."
   },
   {
-    "objectID": "decisions/20241014-basic-realtime-interaction.html#the-downsides",
-    "href": "decisions/20241014-basic-realtime-interaction.html#the-downsides",
-    "title": "Proposed: Basic Real-Time Interaction for Character and World Scenes",
+    "objectID": "decisions/20240331-vrc-vrm-compatibility.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240331-vrc-vrm-compatibility.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: VRC and VRM compatibility",
     "section": "",
-    "text": "The initial features are limited to basic manipulations, which might not meet all user expectations. As the user base grows, the current simple synchronization mechanism may need significant enhancements."
+    "text": "The proposed solution involves a series of steps outlined in the README below:\n\nDO NOT remove transparent triangles for [hair, face, body]\nMake sure the Body has all blend shapes deleted.\nAdd face shapes with hana tool\nSplit the skin from the clothing using separate by material.\nOn all the clothing delete vertex groups.\nUse Robust Weight Transfer for Blender to rig clothing\nUnpack the prefab.\nConvert to vrchat. Combine meshes, remove upper chest\nDelete skirt bones that are not used.\nAdd vrcfury direct tree\nAdd vrcfury fix write defaults\nAdd vrcfury anchor override fix\nAdd vrcfury jerry’s templates\nAdd vrcfury unlimited parameters\nMake sure the Body has the perfect sync blend shapes.\nRemember that VRM Mouth Joy is similar to jawOpen.\nRemember that brown down and eye blink can be buggy.\nChoose either the MPEG4 blendshapes or Perfect sync. Delete one or the other.\nRemove empty vrc parameters\nRemove Physbones with missing transforms from secondary.\nConvert bone clusters in sphere colliders to capsule colliders to go from VERY POOR to POOR.\nContinue converting capsules until satisfied “POOR”.\nThe FX controller must match the name and not be temporary.\nUse Auto VRMColliders.\nMake sure all pipeline IDs are detached.\nRemember to delete the upper chest from the humanoid.\nEye look is behind the nose bridge\nMake sure the breast bones are parented as the same bone as the clothing chest bones correspond to.\nCross eyed fix in vrcfury breaks eye tracking.\nUpload. (Pick a new slot. DO NOT REUSE A SLOT.)\n\n\n\n\nvrc sdk base\nvrc sdk avatar\nvrcfury\nvrcft - jerry’s templates\n\n\n\n\n\nin liltoon turn saturation to 2.\n\n\n\n\n\nTry in blender to merge by distance\n\n\n\n\n\n0.0125 m for distance\n15 degrees for angle match\n\n\n\n\n\nCore movement\nEars :3\n\n\n\n\n\nVRCFury blink controller\nVRCFury blend shape optimizer\nVRCFury direct tree optimizer\nVRCFury fix write defaults\nVRCFury unlimited parameters\nVRCFury anchor override fix\nVRCFury GoGo"
   },
   {
-    "objectID": "decisions/20241014-basic-realtime-interaction.html#the-road-not-taken",
-    "href": "decisions/20241014-basic-realtime-interaction.html#the-road-not-taken",
-    "title": "Proposed: Basic Real-Time Interaction for Character and World Scenes",
+    "objectID": "decisions/20240331-vrc-vrm-compatibility.html#the-benefits",
+    "href": "decisions/20240331-vrc-vrm-compatibility.html#the-benefits",
+    "title": "Proposed: VRC and VRM compatibility",
     "section": "",
-    "text": "A full-scale interaction suite was initially considered, including scaling and advanced physics, but it was decided against due to complexity and resource constraints."
+    "text": "The proposed solution will allow developers to use VRC and VRM together in their projects, leading to increased flexibility and efficiency."
   },
   {
-    "objectID": "decisions/20241014-basic-realtime-interaction.html#the-infrequent-use-case",
-    "href": "decisions/20241014-basic-realtime-interaction.html#the-infrequent-use-case",
-    "title": "Proposed: Basic Real-Time Interaction for Character and World Scenes",
+    "objectID": "decisions/20240331-vrc-vrm-compatibility.html#the-downsides",
+    "href": "decisions/20240331-vrc-vrm-compatibility.html#the-downsides",
+    "title": "Proposed: VRC and VRM compatibility",
     "section": "",
-    "text": "While the system is designed for multiple users, it will also support single-user sessions, although this is not the primary focus."
+    "text": "The process may be complex and time-consuming, especially for those unfamiliar with these formats."
   },
   {
-    "objectID": "decisions/20241014-basic-realtime-interaction.html#in-core-and-done-by-us",
-    "href": "decisions/20241014-basic-realtime-interaction.html#in-core-and-done-by-us",
-    "title": "Proposed: Basic Real-Time Interaction for Character and World Scenes",
+    "objectID": "decisions/20240331-vrc-vrm-compatibility.html#the-road-not-taken",
+    "href": "decisions/20240331-vrc-vrm-compatibility.html#the-road-not-taken",
+    "title": "Proposed: VRC and VRM compatibility",
     "section": "",
-    "text": "This feature is core to the project’s mission of enhancing interactive capabilities and will be developed internally to ensure seamless integration and maintain control over quality."
+    "text": "An alternative approach could involve developing a new format that combines the features of both VRC and VRM. However, this would likely require significant resources and may not be feasible for all developers."
   },
   {
-    "objectID": "decisions/20241014-basic-realtime-interaction.html#status",
-    "href": "decisions/20241014-basic-realtime-interaction.html#status",
-    "title": "Proposed: Basic Real-Time Interaction for Character and World Scenes",
+    "objectID": "decisions/20240331-vrc-vrm-compatibility.html#the-infrequent-use-case",
+    "href": "decisions/20240331-vrc-vrm-compatibility.html#the-infrequent-use-case",
+    "title": "Proposed: VRC and VRM compatibility",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "This proposal may not be beneficial for developers who only use one of these formats in their projects."
   },
   {
-    "objectID": "decisions/20241014-basic-realtime-interaction.html#decision-makers",
-    "href": "decisions/20241014-basic-realtime-interaction.html#decision-makers",
-    "title": "Proposed: Basic Real-Time Interaction for Character and World Scenes",
+    "objectID": "decisions/20240331-vrc-vrm-compatibility.html#in-core-and-done-by-us",
+    "href": "decisions/20240331-vrc-vrm-compatibility.html#in-core-and-done-by-us",
+    "title": "Proposed: VRC and VRM compatibility",
     "section": "",
-    "text": "Project development team\nFire\nHumble Tim"
+    "text": "The proposed solution has been developed by us and is integrated into our core system."
   },
   {
-    "objectID": "decisions/20241014-basic-realtime-interaction.html#tags",
-    "href": "decisions/20241014-basic-realtime-interaction.html#tags",
-    "title": "Proposed: Basic Real-Time Interaction for Character and World Scenes",
+    "objectID": "decisions/20240331-vrc-vrm-compatibility.html#status",
+    "href": "decisions/20240331-vrc-vrm-compatibility.html#status",
+    "title": "Proposed: VRC and VRM compatibility",
     "section": "",
-    "text": "Real-time interaction, basic object manipulation, networked synchronization, user engagement, virtual collaboration, intuitive tool switching"
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20241014-basic-realtime-interaction.html#further-reading",
-    "href": "decisions/20241014-basic-realtime-interaction.html#further-reading",
-    "title": "Proposed: Basic Real-Time Interaction for Character and World Scenes",
+    "objectID": "decisions/20240331-vrc-vrm-compatibility.html#decision-makers",
+    "href": "decisions/20240331-vrc-vrm-compatibility.html#decision-makers",
+    "title": "Proposed: VRC and VRM compatibility",
     "section": "",
-    "text": "Project GitHub - Official GitHub account for the project development community focusing on enhancing virtual interaction capabilities.\nProject Documentation - Comprehensive documentation on the project’s features and development guidelines.\n\nAI assistant Aria assisted with this article."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20211031-update-uro-for-godot-4.html",
-    "href": "decisions/20211031-update-uro-for-godot-4.html",
-    "title": "Proposed: Update URO for Godot 4",
+    "objectID": "decisions/20240331-vrc-vrm-compatibility.html#tags",
+    "href": "decisions/20240331-vrc-vrm-compatibility.html#tags",
+    "title": "Proposed: VRC and VRM compatibility",
     "section": "",
-    "text": "Proposed: Update URO for Godot 4\n\nContext and Problem Statement\nNeed a lobby server\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nUpdate URO for Godot 4.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nTo be determined.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot a few lines of script.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nWe can do it!\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20230903-replicate-vrm-transform.html",
-    "href": "decisions/20230903-replicate-vrm-transform.html",
-    "title": "Rejected: Enabling VRM to Blender Conversion with Cloud GPUs and replicate.com",
+    "objectID": "decisions/20240331-vrc-vrm-compatibility.html#further-reading",
+    "href": "decisions/20240331-vrc-vrm-compatibility.html#further-reading",
+    "title": "Proposed: VRC and VRM compatibility",
     "section": "",
-    "text": "Status: rejected\nDeciders: V-Sekai, fire, antpb\nTags: V-Sekai\n\n\n\n\nThe VRM format is becoming increasingly popular in the field of 3D modeling and animation. It allows for easy sharing and transfer of humanoid 3D models with skeletal animations between different software applications. One such application is the Godot Engine, a popular open-source game engine.\n\n\n\nCurrently, developers working with VRM files in Godot Engine face difficulties when trying to convert these files to Blender format for further editing or manipulation. Manual conversion processes can be time-consuming and error-prone.\n\n\n\nThe proposed strategy for enabling VRM to Blender conversion involves leveraging the computational power of cloud GPUs provided by replicate.com. By running a GPU-accelerated Blender instance, developers can perform an identity operation on the VRM input, converting it to Blender format. This simplifies the process of converting VRM files to Blender format.\nTo convert VRM files to Blender format, developers can follow these steps:\n\nInstall the necessary libraries or plugins in Blender that support the VRM format.\nLeverage replicate.com’s infrastructure to spin up a GPU-accelerated Blender instance.\nDevelop a script or tool that takes the VRM file as input and sends it to the GPU-accelerated Blender instance via a REST interface.\nIn the GPU-accelerated Blender instance, use the installed libraries or plugins to perform the conversion from VRM to Blender format.\nAlso use Blender to perform the conversion from Blender to VRM/GLTF format.\n\nThis strategy streamlines the workflow for developers, saving time and improving collaboration between designers and developers. The use of cloud GPUs and replicate.com’s infrastructure ensures fast and efficient conversion processes.\nAdditionally, this strategy can also be extended to other software applications or websites that can utilize a REST interface, allowing developers working with VRM files to convert them to Blender format seamlessly, regardless of the software they are using.\n\n\n\n\nStreamlined workflow: Developers can easily convert VRM files to Blender format, opening up a wide range of editing and manipulation possibilities.\nTime-saving: The use of cloud GPUs and replicate.com’s infrastructure ensures fast and efficient conversion processes.\nImproved collaboration: The ability to work with VRM models in both Godot Engine and Blender facilitates collaboration between designers and developers.\n\n\n\n\n\nDevelopment effort and expertise: Creating the necessary library or plugin may require significant technical knowledge in both the Godot Engine and VRM format.\nCompatibility issues: Different versions of FBX or GLB files may introduce compatibility challenges during the conversion process.\nMaintenance challenges: Keeping up with future updates to the Godot Engine and VRM specifications may require ongoing effort.\n\n\n\n\nWe considered developing a web application, but it was deemed to have heavy engineering costs.\n\n\n\nWhile the proposed solution focuses on streamlining VRM to Blender conversion for the Godot Engine ecosystem, the same concept can be extended to other software applications or websites that can utilize a REST interface. This allows developers working with VRM files to convert them to Blender format seamlessly, regardless of the software they are using. The use of cloud GPUs and replicate.com’s infrastructure still ensures fast and efficient conversion processes.\n\n\n\nFire knows the way.\n\n\n\n\nV-Sekai\nVRM Animation Specification\nReplicate - Cloud GPU Toy\n\nThis article is assisted by AI.\nIs there anything else I can assist you with?"
+    "text": "vrc-get gui\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n[https://vcc.vrcfury.com]\n[https://Adjerry91.github.io/VRCFaceTracking-Templates/index.json]\n[https://esperecyan.github.io/VRMConverterForVRChat/registry.json]\n[https://vpm.nadena.dev/vpm.json]\n[https://lilxyzw.github.io/vpm-repos/vpm.json]\n[https://fujisunflower.booth.pm/items/2087178]\nVRM Downgrader\nGoGo Loco\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20230903-replicate-vrm-transform.html#metadata",
-    "href": "decisions/20230903-replicate-vrm-transform.html#metadata",
-    "title": "Rejected: Enabling VRM to Blender Conversion with Cloud GPUs and replicate.com",
+    "objectID": "decisions/20240611-lower-learning-rate.html",
+    "href": "decisions/20240611-lower-learning-rate.html",
+    "title": "Proposed: Switch learning rate to be lower.",
     "section": "",
-    "text": "Status: rejected\nDeciders: V-Sekai, fire, antpb\nTags: V-Sekai"
+    "text": "We are currently training a mesh transformer’s auto encoder.\n\n\n\nThe current learning rate might not be optimal for our training process. We need to find a way to adjust it dynamically based on the progress of the training.\n\n\n\nWe propose to monitor the reconstruction loss after each epoch. If the loss decreases by less than 0.004 per epoch, we switch the learning rate to 1e-4.\nNote: Don’t forget to change the load method that the model uses to load the model.\n\n\n\nBy adjusting the learning rate based on the progress of the training, we can potentially achieve better results and prevent overfitting.\n\n\n\nThis approach requires careful monitoring of the training process and might require additional computational resources.\n\n\n\nAn alternative could be to use a fixed learning rate throughout the training process. However, this might not yield optimal results.\n\n\n\nThis approach might not be suitable for all types of models or datasets.\n\n\n\nThis proposal is made by the V-Sekai development team and will be implemented by us.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20230903-replicate-vrm-transform.html#the-backdrop",
-    "href": "decisions/20230903-replicate-vrm-transform.html#the-backdrop",
-    "title": "Rejected: Enabling VRM to Blender Conversion with Cloud GPUs and replicate.com",
+    "objectID": "decisions/20240611-lower-learning-rate.html#the-context",
+    "href": "decisions/20240611-lower-learning-rate.html#the-context",
+    "title": "Proposed: Switch learning rate to be lower.",
     "section": "",
-    "text": "The VRM format is becoming increasingly popular in the field of 3D modeling and animation. It allows for easy sharing and transfer of humanoid 3D models with skeletal animations between different software applications. One such application is the Godot Engine, a popular open-source game engine."
+    "text": "We are currently training a mesh transformer’s auto encoder."
   },
   {
-    "objectID": "decisions/20230903-replicate-vrm-transform.html#the-challenge",
-    "href": "decisions/20230903-replicate-vrm-transform.html#the-challenge",
-    "title": "Rejected: Enabling VRM to Blender Conversion with Cloud GPUs and replicate.com",
+    "objectID": "decisions/20240611-lower-learning-rate.html#the-problem-statement",
+    "href": "decisions/20240611-lower-learning-rate.html#the-problem-statement",
+    "title": "Proposed: Switch learning rate to be lower.",
     "section": "",
-    "text": "Currently, developers working with VRM files in Godot Engine face difficulties when trying to convert these files to Blender format for further editing or manipulation. Manual conversion processes can be time-consuming and error-prone."
+    "text": "The current learning rate might not be optimal for our training process. We need to find a way to adjust it dynamically based on the progress of the training."
   },
   {
-    "objectID": "decisions/20230903-replicate-vrm-transform.html#the-strategy",
-    "href": "decisions/20230903-replicate-vrm-transform.html#the-strategy",
-    "title": "Rejected: Enabling VRM to Blender Conversion with Cloud GPUs and replicate.com",
+    "objectID": "decisions/20240611-lower-learning-rate.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240611-lower-learning-rate.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Switch learning rate to be lower.",
     "section": "",
-    "text": "The proposed strategy for enabling VRM to Blender conversion involves leveraging the computational power of cloud GPUs provided by replicate.com. By running a GPU-accelerated Blender instance, developers can perform an identity operation on the VRM input, converting it to Blender format. This simplifies the process of converting VRM files to Blender format.\nTo convert VRM files to Blender format, developers can follow these steps:\n\nInstall the necessary libraries or plugins in Blender that support the VRM format.\nLeverage replicate.com’s infrastructure to spin up a GPU-accelerated Blender instance.\nDevelop a script or tool that takes the VRM file as input and sends it to the GPU-accelerated Blender instance via a REST interface.\nIn the GPU-accelerated Blender instance, use the installed libraries or plugins to perform the conversion from VRM to Blender format.\nAlso use Blender to perform the conversion from Blender to VRM/GLTF format.\n\nThis strategy streamlines the workflow for developers, saving time and improving collaboration between designers and developers. The use of cloud GPUs and replicate.com’s infrastructure ensures fast and efficient conversion processes.\nAdditionally, this strategy can also be extended to other software applications or websites that can utilize a REST interface, allowing developers working with VRM files to convert them to Blender format seamlessly, regardless of the software they are using."
+    "text": "We propose to monitor the reconstruction loss after each epoch. If the loss decreases by less than 0.004 per epoch, we switch the learning rate to 1e-4.\nNote: Don’t forget to change the load method that the model uses to load the model."
   },
   {
-    "objectID": "decisions/20230903-replicate-vrm-transform.html#the-upside",
-    "href": "decisions/20230903-replicate-vrm-transform.html#the-upside",
-    "title": "Rejected: Enabling VRM to Blender Conversion with Cloud GPUs and replicate.com",
+    "objectID": "decisions/20240611-lower-learning-rate.html#the-benefits",
+    "href": "decisions/20240611-lower-learning-rate.html#the-benefits",
+    "title": "Proposed: Switch learning rate to be lower.",
     "section": "",
-    "text": "Streamlined workflow: Developers can easily convert VRM files to Blender format, opening up a wide range of editing and manipulation possibilities.\nTime-saving: The use of cloud GPUs and replicate.com’s infrastructure ensures fast and efficient conversion processes.\nImproved collaboration: The ability to work with VRM models in both Godot Engine and Blender facilitates collaboration between designers and developers."
+    "text": "By adjusting the learning rate based on the progress of the training, we can potentially achieve better results and prevent overfitting."
   },
   {
-    "objectID": "decisions/20230903-replicate-vrm-transform.html#the-downside",
-    "href": "decisions/20230903-replicate-vrm-transform.html#the-downside",
-    "title": "Rejected: Enabling VRM to Blender Conversion with Cloud GPUs and replicate.com",
+    "objectID": "decisions/20240611-lower-learning-rate.html#the-downsides",
+    "href": "decisions/20240611-lower-learning-rate.html#the-downsides",
+    "title": "Proposed: Switch learning rate to be lower.",
     "section": "",
-    "text": "Development effort and expertise: Creating the necessary library or plugin may require significant technical knowledge in both the Godot Engine and VRM format.\nCompatibility issues: Different versions of FBX or GLB files may introduce compatibility challenges during the conversion process.\nMaintenance challenges: Keeping up with future updates to the Godot Engine and VRM specifications may require ongoing effort."
+    "text": "This approach requires careful monitoring of the training process and might require additional computational resources."
   },
   {
-    "objectID": "decisions/20230903-replicate-vrm-transform.html#the-road-not-taken",
-    "href": "decisions/20230903-replicate-vrm-transform.html#the-road-not-taken",
-    "title": "Rejected: Enabling VRM to Blender Conversion with Cloud GPUs and replicate.com",
+    "objectID": "decisions/20240611-lower-learning-rate.html#the-road-not-taken",
+    "href": "decisions/20240611-lower-learning-rate.html#the-road-not-taken",
+    "title": "Proposed: Switch learning rate to be lower.",
     "section": "",
-    "text": "We considered developing a web application, but it was deemed to have heavy engineering costs."
+    "text": "An alternative could be to use a fixed learning rate throughout the training process. However, this might not yield optimal results."
   },
   {
-    "objectID": "decisions/20230903-replicate-vrm-transform.html#the-infrequent-use-case",
-    "href": "decisions/20230903-replicate-vrm-transform.html#the-infrequent-use-case",
-    "title": "Rejected: Enabling VRM to Blender Conversion with Cloud GPUs and replicate.com",
+    "objectID": "decisions/20240611-lower-learning-rate.html#the-infrequent-use-case",
+    "href": "decisions/20240611-lower-learning-rate.html#the-infrequent-use-case",
+    "title": "Proposed: Switch learning rate to be lower.",
     "section": "",
-    "text": "While the proposed solution focuses on streamlining VRM to Blender conversion for the Godot Engine ecosystem, the same concept can be extended to other software applications or websites that can utilize a REST interface. This allows developers working with VRM files to convert them to Blender format seamlessly, regardless of the software they are using. The use of cloud GPUs and replicate.com’s infrastructure still ensures fast and efficient conversion processes."
+    "text": "This approach might not be suitable for all types of models or datasets."
   },
   {
-    "objectID": "decisions/20230903-replicate-vrm-transform.html#in-core-and-done-by-us",
-    "href": "decisions/20230903-replicate-vrm-transform.html#in-core-and-done-by-us",
-    "title": "Rejected: Enabling VRM to Blender Conversion with Cloud GPUs and replicate.com",
+    "objectID": "decisions/20240611-lower-learning-rate.html#in-core-and-done-by-us",
+    "href": "decisions/20240611-lower-learning-rate.html#in-core-and-done-by-us",
+    "title": "Proposed: Switch learning rate to be lower.",
     "section": "",
-    "text": "Fire knows the way."
+    "text": "This proposal is made by the V-Sekai development team and will be implemented by us."
   },
   {
-    "objectID": "decisions/20230903-replicate-vrm-transform.html#further-reading",
-    "href": "decisions/20230903-replicate-vrm-transform.html#further-reading",
-    "title": "Rejected: Enabling VRM to Blender Conversion with Cloud GPUs and replicate.com",
+    "objectID": "decisions/20240611-lower-learning-rate.html#status",
+    "href": "decisions/20240611-lower-learning-rate.html#status",
+    "title": "Proposed: Switch learning rate to be lower.",
     "section": "",
-    "text": "V-Sekai\nVRM Animation Specification\nReplicate - Cloud GPU Toy\n\nThis article is assisted by AI.\nIs there anything else I can assist you with?"
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20210529-performance-profiling.html",
-    "href": "decisions/20210529-performance-profiling.html",
-    "title": "Proposed: Performance profile the game with AMDuProf",
+    "objectID": "decisions/20240611-lower-learning-rate.html#decision-makers",
+    "href": "decisions/20240611-lower-learning-rate.html#decision-makers",
+    "title": "Proposed: Switch learning rate to be lower.",
     "section": "",
-    "text": "How do we profile the game?\nThe context is for example importing files are slow (they’re not the biggest bottleneck anymore). What tools and techniques can we use?\n\n\n\nUse AMDuProf\n\n\n\nAMDuProf shows the slower functions and there’s also a callgraph and flamegraph feature.\nA callgraph is similar to a stacktrace.\nA flamegraph is a way of visualizing performance. The first link is an ACM article describing the design.\nThe workflow is for each item start from the top and go down.\n\n\n\n\nWorks for both Intel and AMD\nWorks on Windows 10 and Linux\n\n\n\n\n\nLess usable than superluminal\nSlower than superluminal\n\n\n\n\n\nOption: superluminal\nRejection reason:\n\nNot free\n\n\n\n\n\nNot applicable.\n\n\n\nNot in code. This is documenting a technique.\n\n\n\n\nhttps://queue.acm.org/detail.cfm?id=2927301\nhttps://superluminal.eu/\nhttps://developer.amd.com/amd-uprof\nhttp://www.brendangregg.com/flamegraphs.html\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20210529-performance-profiling.html#context-and-problem-statement",
-    "href": "decisions/20210529-performance-profiling.html#context-and-problem-statement",
-    "title": "Proposed: Performance profile the game with AMDuProf",
+    "objectID": "decisions/20240611-lower-learning-rate.html#tags",
+    "href": "decisions/20240611-lower-learning-rate.html#tags",
+    "title": "Proposed: Switch learning rate to be lower.",
     "section": "",
-    "text": "How do we profile the game?\nThe context is for example importing files are slow (they’re not the biggest bottleneck anymore). What tools and techniques can we use?"
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20210529-performance-profiling.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20210529-performance-profiling.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: Performance profile the game with AMDuProf",
+    "objectID": "decisions/20240611-lower-learning-rate.html#further-reading",
+    "href": "decisions/20240611-lower-learning-rate.html#further-reading",
+    "title": "Proposed: Switch learning rate to be lower.",
     "section": "",
-    "text": "Use AMDuProf"
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20210529-performance-profiling.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-andor-diagrams",
-    "href": "decisions/20210529-performance-profiling.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-andor-diagrams",
-    "title": "Proposed: Performance profile the game with AMDuProf",
+    "objectID": "decisions/20231227-punchline-reports.html",
+    "href": "decisions/20231227-punchline-reports.html",
+    "title": "Proposed: Use the “Punchline Reports” Method",
     "section": "",
-    "text": "AMDuProf shows the slower functions and there’s also a callgraph and flamegraph feature.\nA callgraph is similar to a stacktrace.\nA flamegraph is a way of visualizing performance. The first link is an ACM article describing the design.\nThe workflow is for each item start from the top and go down."
+    "text": "Status: Proposed\nDeciders: V-Sekai, fire\nTags: V-Sekai\n\n\n\n\nThe article “I’m OK; The Bull Is Dead” from Computerworld discusses a method for reporting project status effectively. This method prioritizes delivering the most important information first, followed by supporting details.\n\n\n\nTraditional reporting styles often start with lengthy explanations which can delay the delivery of crucial information.\n\n\n\nImplement a four-step approach to reporting:\n\nStart with the punch line – the facts without adjectives or modifiers.\nDescribe the current status and how it affects the project.\nOutline the next steps or solutions.\nProvide an explanation or reason behind the punch line.\n\nThis approach is likened to the inverted pyramid style in journalism, where conclusions are presented first, followed by key facts, and then details.\n\n\n\n\nFaster delivery of crucial information.\nClearer understanding of the project status.\nMore effective communication within the team.\n\n\n\n\n\nMay require training or adjustment period for team members used to traditional reporting styles.\n\n\n\n\nContinuing with traditional reporting styles.\n\n\n\nThis method may not be suitable for projects where the context or background information is as important as the main facts.\n\n\n\nShould we decide to proceed, we will need to train our team on this new reporting method and adjust our project management tools accordingly.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\nI’m OK; The Bull Is Dead\n\nThis proposal was assisted by AI assistant, Aria."
   },
   {
-    "objectID": "decisions/20210529-performance-profiling.html#positive-consequences",
-    "href": "decisions/20210529-performance-profiling.html#positive-consequences",
-    "title": "Proposed: Performance profile the game with AMDuProf",
+    "objectID": "decisions/20231227-punchline-reports.html#metadata",
+    "href": "decisions/20231227-punchline-reports.html#metadata",
+    "title": "Proposed: Use the “Punchline Reports” Method",
     "section": "",
-    "text": "Works for both Intel and AMD\nWorks on Windows 10 and Linux"
+    "text": "Status: Proposed\nDeciders: V-Sekai, fire\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20210529-performance-profiling.html#negative-consequences",
-    "href": "decisions/20210529-performance-profiling.html#negative-consequences",
-    "title": "Proposed: Performance profile the game with AMDuProf",
+    "objectID": "decisions/20231227-punchline-reports.html#context",
+    "href": "decisions/20231227-punchline-reports.html#context",
+    "title": "Proposed: Use the “Punchline Reports” Method",
     "section": "",
-    "text": "Less usable than superluminal\nSlower than superluminal"
+    "text": "The article “I’m OK; The Bull Is Dead” from Computerworld discusses a method for reporting project status effectively. This method prioritizes delivering the most important information first, followed by supporting details."
   },
   {
-    "objectID": "decisions/20210529-performance-profiling.html#option-graveyard-same-as-above",
-    "href": "decisions/20210529-performance-profiling.html#option-graveyard-same-as-above",
-    "title": "Proposed: Performance profile the game with AMDuProf",
+    "objectID": "decisions/20231227-punchline-reports.html#problem",
+    "href": "decisions/20231227-punchline-reports.html#problem",
+    "title": "Proposed: Use the “Punchline Reports” Method",
     "section": "",
-    "text": "Option: superluminal\nRejection reason:\n\nNot free"
+    "text": "Traditional reporting styles often start with lengthy explanations which can delay the delivery of crucial information."
   },
   {
-    "objectID": "decisions/20210529-performance-profiling.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20210529-performance-profiling.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Performance profile the game with AMDuProf",
+    "objectID": "decisions/20231227-punchline-reports.html#solution",
+    "href": "decisions/20231227-punchline-reports.html#solution",
+    "title": "Proposed: Use the “Punchline Reports” Method",
     "section": "",
-    "text": "Not applicable."
+    "text": "Implement a four-step approach to reporting:\n\nStart with the punch line – the facts without adjectives or modifiers.\nDescribe the current status and how it affects the project.\nOutline the next steps or solutions.\nProvide an explanation or reason behind the punch line.\n\nThis approach is likened to the inverted pyramid style in journalism, where conclusions are presented first, followed by key facts, and then details."
   },
   {
-    "objectID": "decisions/20210529-performance-profiling.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20210529-performance-profiling.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Performance profile the game with AMDuProf",
+    "objectID": "decisions/20231227-punchline-reports.html#benefits",
+    "href": "decisions/20231227-punchline-reports.html#benefits",
+    "title": "Proposed: Use the “Punchline Reports” Method",
     "section": "",
-    "text": "Not in code. This is documenting a technique."
+    "text": "Faster delivery of crucial information.\nClearer understanding of the project status.\nMore effective communication within the team."
   },
   {
-    "objectID": "decisions/20210529-performance-profiling.html#references",
-    "href": "decisions/20210529-performance-profiling.html#references",
-    "title": "Proposed: Performance profile the game with AMDuProf",
+    "objectID": "decisions/20231227-punchline-reports.html#potential-drawbacks",
+    "href": "decisions/20231227-punchline-reports.html#potential-drawbacks",
+    "title": "Proposed: Use the “Punchline Reports” Method",
     "section": "",
-    "text": "https://queue.acm.org/detail.cfm?id=2927301\nhttps://superluminal.eu/\nhttps://developer.amd.com/amd-uprof\nhttp://www.brendangregg.com/flamegraphs.html"
+    "text": "May require training or adjustment period for team members used to traditional reporting styles."
   },
   {
-    "objectID": "decisions/20210529-performance-profiling.html#derivative-license",
-    "href": "decisions/20210529-performance-profiling.html#derivative-license",
-    "title": "Proposed: Performance profile the game with AMDuProf",
+    "objectID": "decisions/20231227-punchline-reports.html#alternatives-considered",
+    "href": "decisions/20231227-punchline-reports.html#alternatives-considered",
+    "title": "Proposed: Use the “Punchline Reports” Method",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Continuing with traditional reporting styles."
   },
   {
-    "objectID": "decisions/20230811-punchline-reports.html",
-    "href": "decisions/20230811-punchline-reports.html",
-    "title": "Accepted: Punchline based reports",
+    "objectID": "decisions/20231227-punchline-reports.html#rare-use-cases",
+    "href": "decisions/20231227-punchline-reports.html#rare-use-cases",
+    "title": "Proposed: Use the “Punchline Reports” Method",
     "section": "",
-    "text": "Status: proposed \nDeciders: V-Sekai, fire\nTags: V-Sekai\n\n\n\n\nCommunication and project management within your game development team can be better.\n\n\n\nUsing the reverse reporting style in game development, the project manager gets the most important information first, followed by supporting details.\n\n\n\n\n\nThis is where you present the facts related to the game development process. For example:\n\"The AI behavior for enemy characters wasn't completed on time, and we didn't start the level design for Stage 3 as planned.\"\nor\n\"Completed the character modeling as scheduled.\"\n\n\n\nIn this step, you explain how the punch line affects the game development project. For instance:\n\"Because of the incomplete AI behavior, the game testing has been delayed by a week.\"\n\n\n\nHere, you propose solutions to the problem if there are any. An example could be:\n\"I will be able to complete the AI behavior in the next four days but the level design for Stage 3 will still be behind schedule.\"\n\n\n\nFinally, you provide the reasons behind the punch line. This is where you can give a detailed account of why things happened the way they did. For example:\n\"Three days' delay in AI behavior is due to an unexpected bug in the pathfinding system, and the remaining delay is due to being called to assist the graphics team with texture optimization.\"\n\n\n\n\nThe upside of this strategy is that it allows for clear and concise communication within the team. It ensures that everyone is aware of the current status of the project and what needs to be done moving forward.\n\n\n\nThe downside is that it requires all team members to be diligent in their reporting. If someone fails to accurately report their progress or issues, it could lead to miscommunication and delays in the project.\n\n\n\nAn alternative approach could have been to use traditional reporting methods, where each team member provides a detailed report of their work. However, this method can often lead to information overload and important details may get lost in the process.\n\n\n\nThis strategy may not be as effective in smaller teams or projects where communication is more direct and less formal.\n\n\n\nYes, this strategy should be implemented by us as it aligns with our goal of improving communication and project management within the team.\n\n\n\n\nV-Sekai\nI’m OK; The Bull Is Dead\nThis article is assisted by AI."
+    "text": "This method may not be suitable for projects where the context or background information is as important as the main facts."
   },
   {
-    "objectID": "decisions/20230811-punchline-reports.html#metadata",
-    "href": "decisions/20230811-punchline-reports.html#metadata",
-    "title": "Accepted: Punchline based reports",
+    "objectID": "decisions/20231227-punchline-reports.html#implementation",
+    "href": "decisions/20231227-punchline-reports.html#implementation",
+    "title": "Proposed: Use the “Punchline Reports” Method",
     "section": "",
-    "text": "Status: proposed \nDeciders: V-Sekai, fire\nTags: V-Sekai"
+    "text": "Should we decide to proceed, we will need to train our team on this new reporting method and adjust our project management tools accordingly."
   },
   {
-    "objectID": "decisions/20230811-punchline-reports.html#the-backdrop",
-    "href": "decisions/20230811-punchline-reports.html#the-backdrop",
-    "title": "Accepted: Punchline based reports",
+    "objectID": "decisions/20231227-punchline-reports.html#references",
+    "href": "decisions/20231227-punchline-reports.html#references",
+    "title": "Proposed: Use the “Punchline Reports” Method",
     "section": "",
-    "text": "Communication and project management within your game development team can be better."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\nI’m OK; The Bull Is Dead\n\nThis proposal was assisted by AI assistant, Aria."
   },
   {
-    "objectID": "decisions/20230811-punchline-reports.html#the-challenge",
-    "href": "decisions/20230811-punchline-reports.html#the-challenge",
-    "title": "Accepted: Punchline based reports",
+    "objectID": "decisions/20240120-vr-armature-system.html",
+    "href": "decisions/20240120-vr-armature-system.html",
+    "title": "Proposed: Advanced VR Armature System for V-Sekai",
     "section": "",
-    "text": "Using the reverse reporting style in game development, the project manager gets the most important information first, followed by supporting details."
+    "text": "Status: Proposed\nDeciders: V-Sekai Core Team\nTags: Virtual Reality, Rigging, Animation, IK Systems, Development\n\n\n\n\nThe V-Sekai community needs better rigging and animation tools specifically tailored for VR. The goal is to move beyond the current limitations of traditional approaches.\n\n\n\nDevelop an intuitive inverse kinematics (IK) system for VR avatars that removes the need for numerical input, enhancing the user experience.\n\n\n\nThe proposed VR Armature System includes:\n\nHandles designed for VR interaction.\nVisual indicators for joint movement ranges.\nStraightforward adjustment methods without requiring numbers.\n\n\n\n\n\nHandle Control Design:\n\nCraft VR-appropriate ergonomic handles.\nTrack VR controller for handle interaction.\n\nVisual Indicator Development:\n\nVisualize joint limits.\nUpdate indicators with joint movement.\n\nIK Solver Integration:\n\nEmploy IK solver for joint positioning.\nValidate across different avatar models.\n\nInterface & Interaction:\n\nInterface design for easy joint manipulation.\nImplement feedback for joint limit reach.\n\nTesting & Debugging:\n\nUser testing for intuitive use.\nRefine system via user feedback.\n\nSystem Finalization:\n\nEstablish final iteration post-testing.\nOptimize for VR performance.\n\nDocumentation & Training:\n\nProduce user guides and tutorials.\nConduct capability and usage training sessions.\n\n\n\n\n\nImplementing this system aims to improve the creation process in VR and establish V-Sekai as a cutting-edge developer of VR tools.\n\n\n\nThe introduction of a new system may require substantial resources and time for users to become familiar with it.\n\n\n\nOther options, like enhancing existing numerical controls or looking into traditional motion capture technologies, were considered but didn’t meet our immersive needs.\n\n\n\nWhile focused on VR, this system could also benefit animators using more conventional methods by providing improved interfaces and easier rig manipulation.\n\n\n\nIt’s crucial for V-Sekai to maintain this project to ensure it meets our quality standards and integrates seamlessly with our core technologies.\n\n\n\nFor insights into V-Sekai’s contributions to social VR in Godot Engine and our open-source work, please see:\n\nV-Sekai GitHub Repository\nV-Sekai Game Repository\n\nThis proposal was refined with assistance from Aria."
   },
   {
-    "objectID": "decisions/20230811-punchline-reports.html#the-strategy",
-    "href": "decisions/20230811-punchline-reports.html#the-strategy",
-    "title": "Accepted: Punchline based reports",
+    "objectID": "decisions/20240120-vr-armature-system.html#metadata",
+    "href": "decisions/20240120-vr-armature-system.html#metadata",
+    "title": "Proposed: Advanced VR Armature System for V-Sekai",
     "section": "",
-    "text": "This is where you present the facts related to the game development process. For example:\n\"The AI behavior for enemy characters wasn't completed on time, and we didn't start the level design for Stage 3 as planned.\"\nor\n\"Completed the character modeling as scheduled.\"\n\n\n\nIn this step, you explain how the punch line affects the game development project. For instance:\n\"Because of the incomplete AI behavior, the game testing has been delayed by a week.\"\n\n\n\nHere, you propose solutions to the problem if there are any. An example could be:\n\"I will be able to complete the AI behavior in the next four days but the level design for Stage 3 will still be behind schedule.\"\n\n\n\nFinally, you provide the reasons behind the punch line. This is where you can give a detailed account of why things happened the way they did. For example:\n\"Three days' delay in AI behavior is due to an unexpected bug in the pathfinding system, and the remaining delay is due to being called to assist the graphics team with texture optimization.\""
+    "text": "Status: Proposed\nDeciders: V-Sekai Core Team\nTags: Virtual Reality, Rigging, Animation, IK Systems, Development"
   },
   {
-    "objectID": "decisions/20230811-punchline-reports.html#the-upside",
-    "href": "decisions/20230811-punchline-reports.html#the-upside",
-    "title": "Accepted: Punchline based reports",
+    "objectID": "decisions/20240120-vr-armature-system.html#introduction",
+    "href": "decisions/20240120-vr-armature-system.html#introduction",
+    "title": "Proposed: Advanced VR Armature System for V-Sekai",
     "section": "",
-    "text": "The upside of this strategy is that it allows for clear and concise communication within the team. It ensures that everyone is aware of the current status of the project and what needs to be done moving forward."
+    "text": "The V-Sekai community needs better rigging and animation tools specifically tailored for VR. The goal is to move beyond the current limitations of traditional approaches."
   },
   {
-    "objectID": "decisions/20230811-punchline-reports.html#the-downside",
-    "href": "decisions/20230811-punchline-reports.html#the-downside",
-    "title": "Accepted: Punchline based reports",
+    "objectID": "decisions/20240120-vr-armature-system.html#objective",
+    "href": "decisions/20240120-vr-armature-system.html#objective",
+    "title": "Proposed: Advanced VR Armature System for V-Sekai",
     "section": "",
-    "text": "The downside is that it requires all team members to be diligent in their reporting. If someone fails to accurately report their progress or issues, it could lead to miscommunication and delays in the project."
+    "text": "Develop an intuitive inverse kinematics (IK) system for VR avatars that removes the need for numerical input, enhancing the user experience."
   },
   {
-    "objectID": "decisions/20230811-punchline-reports.html#the-road-not-taken",
-    "href": "decisions/20230811-punchline-reports.html#the-road-not-taken",
-    "title": "Accepted: Punchline based reports",
+    "objectID": "decisions/20240120-vr-armature-system.html#proposed-solution",
+    "href": "decisions/20240120-vr-armature-system.html#proposed-solution",
+    "title": "Proposed: Advanced VR Armature System for V-Sekai",
     "section": "",
-    "text": "An alternative approach could have been to use traditional reporting methods, where each team member provides a detailed report of their work. However, this method can often lead to information overload and important details may get lost in the process."
+    "text": "The proposed VR Armature System includes:\n\nHandles designed for VR interaction.\nVisual indicators for joint movement ranges.\nStraightforward adjustment methods without requiring numbers."
   },
   {
-    "objectID": "decisions/20230811-punchline-reports.html#the-infrequent-use-case",
-    "href": "decisions/20230811-punchline-reports.html#the-infrequent-use-case",
-    "title": "Accepted: Punchline based reports",
+    "objectID": "decisions/20240120-vr-armature-system.html#technical-implementation-steps",
+    "href": "decisions/20240120-vr-armature-system.html#technical-implementation-steps",
+    "title": "Proposed: Advanced VR Armature System for V-Sekai",
     "section": "",
-    "text": "This strategy may not be as effective in smaller teams or projects where communication is more direct and less formal."
+    "text": "Handle Control Design:\n\nCraft VR-appropriate ergonomic handles.\nTrack VR controller for handle interaction.\n\nVisual Indicator Development:\n\nVisualize joint limits.\nUpdate indicators with joint movement.\n\nIK Solver Integration:\n\nEmploy IK solver for joint positioning.\nValidate across different avatar models.\n\nInterface & Interaction:\n\nInterface design for easy joint manipulation.\nImplement feedback for joint limit reach.\n\nTesting & Debugging:\n\nUser testing for intuitive use.\nRefine system via user feedback.\n\nSystem Finalization:\n\nEstablish final iteration post-testing.\nOptimize for VR performance.\n\nDocumentation & Training:\n\nProduce user guides and tutorials.\nConduct capability and usage training sessions."
   },
   {
-    "objectID": "decisions/20230811-punchline-reports.html#in-core-and-done-by-us",
-    "href": "decisions/20230811-punchline-reports.html#in-core-and-done-by-us",
-    "title": "Accepted: Punchline based reports",
+    "objectID": "decisions/20240120-vr-armature-system.html#benefits",
+    "href": "decisions/20240120-vr-armature-system.html#benefits",
+    "title": "Proposed: Advanced VR Armature System for V-Sekai",
     "section": "",
-    "text": "Yes, this strategy should be implemented by us as it aligns with our goal of improving communication and project management within the team."
+    "text": "Implementing this system aims to improve the creation process in VR and establish V-Sekai as a cutting-edge developer of VR tools."
   },
   {
-    "objectID": "decisions/20230811-punchline-reports.html#further-reading",
-    "href": "decisions/20230811-punchline-reports.html#further-reading",
-    "title": "Accepted: Punchline based reports",
+    "objectID": "decisions/20240120-vr-armature-system.html#considerations",
+    "href": "decisions/20240120-vr-armature-system.html#considerations",
+    "title": "Proposed: Advanced VR Armature System for V-Sekai",
     "section": "",
-    "text": "V-Sekai\nI’m OK; The Bull Is Dead\nThis article is assisted by AI."
+    "text": "The introduction of a new system may require substantial resources and time for users to become familiar with it."
   },
   {
-    "objectID": "decisions/20231225-mesh-transformer-facial-features.html",
-    "href": "decisions/20231225-mesh-transformer-facial-features.html",
-    "title": "Proposed: Mesh Transformer Expressive Facial Features",
+    "objectID": "decisions/20240120-vr-armature-system.html#alternatives-evaluated",
+    "href": "decisions/20240120-vr-armature-system.html#alternatives-evaluated",
+    "title": "Proposed: Advanced VR Armature System for V-Sekai",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, first rank\n\n\n\n\nVirtual Reality (VR) is a rapidly evolving field, with new technologies and techniques being developed constantly. One of the key areas of focus in VR development is creating realistic and expressive avatars. This is where Mesh Transformers comes into play.\n\n\n\nThe challenge lies in enhancing non-verbal communication in virtual reality by generating diverse facial structures and features that are expressive yet efficient in terms of polygon count. This includes creating a variety of facial shapes, eye configurations, nose shapes, and mouth designs.\n\n\n\nThe strategy is to employ Mesh Transformers to generate these facial features. The aim is to offer a range of facial features that can later be animated or rigged for various expressions, greatly enriching the social and emotional dynamics of VR experiences.\n\n\n\nThe upside is the creation of more immersive and engaging virtual environments, with avatars that can express a wide range of emotions and reactions.\n\n\n\nThe downside could be the potential increase in complexity and computational requirements due to the addition of more detailed and expressive facial features.\n\n\n\nAn alternative approach could have been to use simpler, less expressive avatar designs. However, this would limit the range of non-verbal communication possible in VR environments.\n\n\n\nIn cases where VR environments are used for simple tasks or interactions, the need for highly expressive avatars may not be as high.\n\n\n\nYes, this proposal is core to our mission of enhancing VR experiences and will be implemented by our team.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
+    "text": "Other options, like enhancing existing numerical controls or looking into traditional motion capture technologies, were considered but didn’t meet our immersive needs."
   },
   {
-    "objectID": "decisions/20231225-mesh-transformer-facial-features.html#metadata",
-    "href": "decisions/20231225-mesh-transformer-facial-features.html#metadata",
-    "title": "Proposed: Mesh Transformer Expressive Facial Features",
+    "objectID": "decisions/20240120-vr-armature-system.html#extended-applications",
+    "href": "decisions/20240120-vr-armature-system.html#extended-applications",
+    "title": "Proposed: Advanced VR Armature System for V-Sekai",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, first rank"
+    "text": "While focused on VR, this system could also benefit animators using more conventional methods by providing improved interfaces and easier rig manipulation."
   },
   {
-    "objectID": "decisions/20231225-mesh-transformer-facial-features.html#the-backdrop",
-    "href": "decisions/20231225-mesh-transformer-facial-features.html#the-backdrop",
-    "title": "Proposed: Mesh Transformer Expressive Facial Features",
+    "objectID": "decisions/20240120-vr-armature-system.html#alignment-with-v-sekai",
+    "href": "decisions/20240120-vr-armature-system.html#alignment-with-v-sekai",
+    "title": "Proposed: Advanced VR Armature System for V-Sekai",
     "section": "",
-    "text": "Virtual Reality (VR) is a rapidly evolving field, with new technologies and techniques being developed constantly. One of the key areas of focus in VR development is creating realistic and expressive avatars. This is where Mesh Transformers comes into play."
+    "text": "It’s crucial for V-Sekai to maintain this project to ensure it meets our quality standards and integrates seamlessly with our core technologies."
   },
   {
-    "objectID": "decisions/20231225-mesh-transformer-facial-features.html#the-challenge",
-    "href": "decisions/20231225-mesh-transformer-facial-features.html#the-challenge",
-    "title": "Proposed: Mesh Transformer Expressive Facial Features",
+    "objectID": "decisions/20240120-vr-armature-system.html#resources",
+    "href": "decisions/20240120-vr-armature-system.html#resources",
+    "title": "Proposed: Advanced VR Armature System for V-Sekai",
     "section": "",
-    "text": "The challenge lies in enhancing non-verbal communication in virtual reality by generating diverse facial structures and features that are expressive yet efficient in terms of polygon count. This includes creating a variety of facial shapes, eye configurations, nose shapes, and mouth designs."
+    "text": "For insights into V-Sekai’s contributions to social VR in Godot Engine and our open-source work, please see:\n\nV-Sekai GitHub Repository\nV-Sekai Game Repository\n\nThis proposal was refined with assistance from Aria."
   },
   {
-    "objectID": "decisions/20231225-mesh-transformer-facial-features.html#the-strategy",
-    "href": "decisions/20231225-mesh-transformer-facial-features.html#the-strategy",
-    "title": "Proposed: Mesh Transformer Expressive Facial Features",
+    "objectID": "decisions/20210707-transfer-animations-by-baking-reset.html",
+    "href": "decisions/20210707-transfer-animations-by-baking-reset.html",
+    "title": "Proposed: Transfer animation by baking reset",
     "section": "",
-    "text": "The strategy is to employ Mesh Transformers to generate these facial features. The aim is to offer a range of facial features that can later be animated or rigged for various expressions, greatly enriching the social and emotional dynamics of VR experiences."
+    "text": "Given two animations .glbs in gltf, you cannot transfer the animation between the same character in different files in some cases.\nFixes: https://github.com/godotengine/godot/issues/50212\nWe are NOT retargeting between different rigs in the RESET baker stage.\nWe are NOT defining how to generate the RESET #animation in this proposal.\n\n\nWe want to transfer #animation between exact scenes with the same matching RESET animation.\nWe can import unlimited motion capture #animation to use if we can enforce a certain T-POSE and ensure the rigs are corresponding.\nMultiple different specifications exist on bone rolls on specific bone names. If the skeleton matches one of them, we can use that set of rig animations.\n\n\n\n\nWe bake the RESET #animation and then set it to identity so that rigs with corresponding RESET #animation can have their #animation transferred.\n\n\n\n\n\n\nImport a new scene with animations.\nA RESET #animation from the imported scene will automatically be baked to the skeleton.\nKey all RESET #animation frames to identity.\n\n\n\n\n\nPick an #animation frame time and click\nFirst bake any existing RESET animation.\nBake the RESET #animation\nEnsure that a RESET #animation track exists and is set to identity transform\n\n\n\n\n\nMake a tool that can take a human character and make it T-pose (A-pose?) and then save it to the RESET animation.\nEnforce bone rolls on the rig and then save it to the RESET animation.\nRoot motion centering (move to the origin) tool and then save it as the RESET animation.\nFilter the RESET axes when baking per animation.\n\n\n\n\n\nThis is a confusing problem and hard to explain. So the code to solve it is non-obvious to propose and non-trivial to discover.\n\n\n\n#animation are a core feature of Godot Engine.\n\n\n\n\nBone roll parent to child baking. https://github.com/V-Sekai/godot/commit/99a9f79e25f7760cb5a0990e67545d78e9dd0423\nImplementation: https://github.com/godot-extended-libraries/godot-fire/tree/feature/bake-reset-anim\nReference bone roll spec. https://tokage.info/lab/?id=5\nUse the entire surface of the mesh to match to the SMPL rig. (Siggraph 2021) https://github.com/PeizhuoLi/neural-blend-shapes/issues\nGuessing “Blender edit” https://github.com/KhronosGroup/glTF-Blender-IO/pull/941\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20231225-mesh-transformer-facial-features.html#the-upside",
-    "href": "decisions/20231225-mesh-transformer-facial-features.html#the-upside",
-    "title": "Proposed: Mesh Transformer Expressive Facial Features",
+    "objectID": "decisions/20210707-transfer-animations-by-baking-reset.html#context-and-problem-statement",
+    "href": "decisions/20210707-transfer-animations-by-baking-reset.html#context-and-problem-statement",
+    "title": "Proposed: Transfer animation by baking reset",
     "section": "",
-    "text": "The upside is the creation of more immersive and engaging virtual environments, with avatars that can express a wide range of emotions and reactions."
+    "text": "Given two animations .glbs in gltf, you cannot transfer the animation between the same character in different files in some cases.\nFixes: https://github.com/godotengine/godot/issues/50212\nWe are NOT retargeting between different rigs in the RESET baker stage.\nWe are NOT defining how to generate the RESET #animation in this proposal.\n\n\nWe want to transfer #animation between exact scenes with the same matching RESET animation.\nWe can import unlimited motion capture #animation to use if we can enforce a certain T-POSE and ensure the rigs are corresponding.\nMultiple different specifications exist on bone rolls on specific bone names. If the skeleton matches one of them, we can use that set of rig animations."
   },
   {
-    "objectID": "decisions/20231225-mesh-transformer-facial-features.html#the-downside",
-    "href": "decisions/20231225-mesh-transformer-facial-features.html#the-downside",
-    "title": "Proposed: Mesh Transformer Expressive Facial Features",
+    "objectID": "decisions/20210707-transfer-animations-by-baking-reset.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20210707-transfer-animations-by-baking-reset.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: Transfer animation by baking reset",
     "section": "",
-    "text": "The downside could be the potential increase in complexity and computational requirements due to the addition of more detailed and expressive facial features."
+    "text": "We bake the RESET #animation and then set it to identity so that rigs with corresponding RESET #animation can have their #animation transferred."
   },
   {
-    "objectID": "decisions/20231225-mesh-transformer-facial-features.html#the-road-not-taken",
-    "href": "decisions/20231225-mesh-transformer-facial-features.html#the-road-not-taken",
-    "title": "Proposed: Mesh Transformer Expressive Facial Features",
+    "objectID": "decisions/20210707-transfer-animations-by-baking-reset.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20210707-transfer-animations-by-baking-reset.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Transfer animation by baking reset",
     "section": "",
-    "text": "An alternative approach could have been to use simpler, less expressive avatar designs. However, this would limit the range of non-verbal communication possible in VR environments."
+    "text": "Import a new scene with animations.\nA RESET #animation from the imported scene will automatically be baked to the skeleton.\nKey all RESET #animation frames to identity.\n\n\n\n\n\nPick an #animation frame time and click\nFirst bake any existing RESET animation.\nBake the RESET #animation\nEnsure that a RESET #animation track exists and is set to identity transform\n\n\n\n\n\nMake a tool that can take a human character and make it T-pose (A-pose?) and then save it to the RESET animation.\nEnforce bone rolls on the rig and then save it to the RESET animation.\nRoot motion centering (move to the origin) tool and then save it as the RESET animation.\nFilter the RESET axes when baking per animation."
   },
   {
-    "objectID": "decisions/20231225-mesh-transformer-facial-features.html#the-infrequent-use-case",
-    "href": "decisions/20231225-mesh-transformer-facial-features.html#the-infrequent-use-case",
-    "title": "Proposed: Mesh Transformer Expressive Facial Features",
+    "objectID": "decisions/20210707-transfer-animations-by-baking-reset.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20210707-transfer-animations-by-baking-reset.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Transfer animation by baking reset",
     "section": "",
-    "text": "In cases where VR environments are used for simple tasks or interactions, the need for highly expressive avatars may not be as high."
+    "text": "This is a confusing problem and hard to explain. So the code to solve it is non-obvious to propose and non-trivial to discover."
   },
   {
-    "objectID": "decisions/20231225-mesh-transformer-facial-features.html#in-core-and-done-by-us",
-    "href": "decisions/20231225-mesh-transformer-facial-features.html#in-core-and-done-by-us",
-    "title": "Proposed: Mesh Transformer Expressive Facial Features",
+    "objectID": "decisions/20210707-transfer-animations-by-baking-reset.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20210707-transfer-animations-by-baking-reset.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Transfer animation by baking reset",
     "section": "",
-    "text": "Yes, this proposal is core to our mission of enhancing VR experiences and will be implemented by our team."
+    "text": "#animation are a core feature of Godot Engine."
   },
   {
-    "objectID": "decisions/20231225-mesh-transformer-facial-features.html#further-reading",
-    "href": "decisions/20231225-mesh-transformer-facial-features.html#further-reading",
-    "title": "Proposed: Mesh Transformer Expressive Facial Features",
+    "objectID": "decisions/20210707-transfer-animations-by-baking-reset.html#references",
+    "href": "decisions/20210707-transfer-animations-by-baking-reset.html#references",
+    "title": "Proposed: Transfer animation by baking reset",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
+    "text": "Bone roll parent to child baking. https://github.com/V-Sekai/godot/commit/99a9f79e25f7760cb5a0990e67545d78e9dd0423\nImplementation: https://github.com/godot-extended-libraries/godot-fire/tree/feature/bake-reset-anim\nReference bone roll spec. https://tokage.info/lab/?id=5\nUse the entire surface of the mesh to match to the SMPL rig. (Siggraph 2021) https://github.com/PeizhuoLi/neural-blend-shapes/issues\nGuessing “Blender edit” https://github.com/KhronosGroup/glTF-Blender-IO/pull/941"
   },
   {
-    "objectID": "decisions/20240710-use-godot-engine-web-threaded.html",
-    "href": "decisions/20240710-use-godot-engine-web-threaded.html",
-    "title": "Proposed: Use Godot Engine Web Threaded",
+    "objectID": "decisions/20210707-transfer-animations-by-baking-reset.html#derivative-license",
+    "href": "decisions/20210707-transfer-animations-by-baking-reset.html#derivative-license",
+    "title": "Proposed: Transfer animation by baking reset",
     "section": "",
-    "text": "In the development of web-based applications using the Godot Engine, performance and responsiveness are critical. Leveraging multi-threading can significantly enhance these aspects.\n\n\n\nWhen developing web applications with Godot, we face challenges related to loading large resources and maintaining smooth audio playback. Single-threaded implementations often fall short in handling these tasks efficiently.\n\n\n\n\n\n\nFeature\nMulti-Threaded\nSingle-Threaded\n\n\n\n\nAudio Sampling\nx\nx\n\n\nNormal Audio Files\nx\n\n\n\nShared Array Buffer\nx\n\n\n\nLoad Large Maps in the Background\nx\n\n\n\nFull Browser Support\n\nx\n\n\nPotential Bugs\n\nx\n\n\n\n\n\n\n\nImproved Performance: Multi-threading allows for background resource loading, enhancing application responsiveness.\nBetter User Experience: Smooth audio playback and faster load times contribute to a more seamless user experience.\n\n\n\n\n\nComplexity: Implementing multi-threading can introduce complexity and potential bugs.\nBrowser Compatibility: Ensuring full browser support for multi-threaded features may require additional effort.\n\n\n\n\nAlternative approaches such as sticking with single-threaded implementations were considered but ultimately deemed less effective for handling large resources.\n\n\n\nIn cases where the application does not involve large resources or complex audio processing, single-threaded implementation might suffice.\n\n\n\nThis proposal aligns with our core values of efficiency and performance and will be implemented by our team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240710-use-godot-engine-web-threaded.html#the-context",
-    "href": "decisions/20240710-use-godot-engine-web-threaded.html#the-context",
-    "title": "Proposed: Use Godot Engine Web Threaded",
+    "objectID": "decisions/20221019-networking-100000-entities-ownership.html",
+    "href": "decisions/20221019-networking-100000-entities-ownership.html",
+    "title": "Proposed: Networking with 100000 Entities and Ownership (Revision 2)",
     "section": "",
-    "text": "In the development of web-based applications using the Godot Engine, performance and responsiveness are critical. Leveraging multi-threading can significantly enhance these aspects."
+    "text": "Status: proposed \nDeciders: V-Sekai,\nTags: V-Sekai, Networking\n\n\n\nIn short, replication of state while permitting object ownership to transfer, at scale.\n\n\n\nIf we go with a model in which objects have one of three policies:\n\nDeny\nAsk Master\nAllow always (synchronous replication)\n\nWe want to ensure various guarantees in each case.\n\nThere is no problem\nWe will delay sync by 1 round trip, so there is no problem because everything is synchronized against the master.\nWe will follow a “last-write wins” strategy from the perspective of the relay server responsible for mastership.\n\nOther relays only need to know which server owns each object (and possibly the ownership / mastership table), and where each entity is.\nHaving this constraint permits us to use a model where we do not need consistent and transactional global information about object ownership, which allows the system to be simpler.\nIdea of separation of presence queries (who is here, reliably, tricky to figure out who of 100000 clients is relevant?) from realtime networking sync, which can flow directly from relay to relay, degrading over distance.\n\n\n\nNone yet. We may try prototyping this type of system in multiple ways.\n\n\n\nThis keeps low latency but reduces the needed bandwidth to sync 100,000 entities.\nNapkin math:\n50 bytes per frame per object * 100,000 objects = 5MB per frame.\n5MB/frame * 20 fps = 100MB = 1Gbps\nIf we send updates of all objects to all objects, that requires 100Tb/s\n\n&gt; yea 100k users at once is impossible any way you put it. I think a realistic goal is 1k, as like, our max goal\n\nRight, so you would need to not send updates for far away objects\n\nOnly send 1000 closest objects: 1Tb/s\n\n+ Send faraway objects at 2Hz: 100Gb/s\n\n+ Heavy delta compression: 10Gb/s\n\nThis is for all players\n\nThie means, in a hypothetical universe where distant objects only need position sync, a server with 10Gb/s NIC could theoretically run 100,000 concurrent users, if optimizzed!\n\nAlso, therefore, per player bandwidth **of distant objects** would be 100Kbit/s of downstream data, which is pretty small.\n\nAgain I haven't accounted for IK synchronization, or for additional nearby objects, so it could be higher here.\nNearby objects is a smaller problem and easier to solve, and belongs in a separate proposal.\n\n\n\nWe may be overcomplicating a problem that doesn’t need to be solved yet. Pure interest management may be sufficient, and we do not currently have this many users.\n\n\n\n\n\n\n\n\n\n\n\n\nSource:\nDiscord VC with Malek and iFire\nDiscord channel forum-v-sekai “Networking with librg” thread: https://discord.com/channels/471446618156040210/1031379649776848900/1032401929587929208\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240710-use-godot-engine-web-threaded.html#the-problem-statement",
-    "href": "decisions/20240710-use-godot-engine-web-threaded.html#the-problem-statement",
-    "title": "Proposed: Use Godot Engine Web Threaded",
+    "objectID": "decisions/20221019-networking-100000-entities-ownership.html#context-and-problem-statement",
+    "href": "decisions/20221019-networking-100000-entities-ownership.html#context-and-problem-statement",
+    "title": "Proposed: Networking with 100000 Entities and Ownership (Revision 2)",
     "section": "",
-    "text": "When developing web applications with Godot, we face challenges related to loading large resources and maintaining smooth audio playback. Single-threaded implementations often fall short in handling these tasks efficiently."
+    "text": "In short, replication of state while permitting object ownership to transfer, at scale."
   },
   {
-    "objectID": "decisions/20240710-use-godot-engine-web-threaded.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240710-use-godot-engine-web-threaded.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Use Godot Engine Web Threaded",
+    "objectID": "decisions/20221019-networking-100000-entities-ownership.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20221019-networking-100000-entities-ownership.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: Networking with 100000 Entities and Ownership (Revision 2)",
     "section": "",
-    "text": "Feature\nMulti-Threaded\nSingle-Threaded\n\n\n\n\nAudio Sampling\nx\nx\n\n\nNormal Audio Files\nx\n\n\n\nShared Array Buffer\nx\n\n\n\nLoad Large Maps in the Background\nx\n\n\n\nFull Browser Support\n\nx\n\n\nPotential Bugs\n\nx"
+    "text": "If we go with a model in which objects have one of three policies:\n\nDeny\nAsk Master\nAllow always (synchronous replication)\n\nWe want to ensure various guarantees in each case.\n\nThere is no problem\nWe will delay sync by 1 round trip, so there is no problem because everything is synchronized against the master.\nWe will follow a “last-write wins” strategy from the perspective of the relay server responsible for mastership.\n\nOther relays only need to know which server owns each object (and possibly the ownership / mastership table), and where each entity is.\nHaving this constraint permits us to use a model where we do not need consistent and transactional global information about object ownership, which allows the system to be simpler.\nIdea of separation of presence queries (who is here, reliably, tricky to figure out who of 100000 clients is relevant?) from realtime networking sync, which can flow directly from relay to relay, degrading over distance."
   },
   {
-    "objectID": "decisions/20240710-use-godot-engine-web-threaded.html#the-benefits",
-    "href": "decisions/20240710-use-godot-engine-web-threaded.html#the-benefits",
-    "title": "Proposed: Use Godot Engine Web Threaded",
+    "objectID": "decisions/20221019-networking-100000-entities-ownership.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20221019-networking-100000-entities-ownership.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Networking with 100000 Entities and Ownership (Revision 2)",
     "section": "",
-    "text": "Improved Performance: Multi-threading allows for background resource loading, enhancing application responsiveness.\nBetter User Experience: Smooth audio playback and faster load times contribute to a more seamless user experience."
+    "text": "None yet. We may try prototyping this type of system in multiple ways."
   },
   {
-    "objectID": "decisions/20240710-use-godot-engine-web-threaded.html#the-downsides",
-    "href": "decisions/20240710-use-godot-engine-web-threaded.html#the-downsides",
-    "title": "Proposed: Use Godot Engine Web Threaded",
+    "objectID": "decisions/20221019-networking-100000-entities-ownership.html#positive-consequences",
+    "href": "decisions/20221019-networking-100000-entities-ownership.html#positive-consequences",
+    "title": "Proposed: Networking with 100000 Entities and Ownership (Revision 2)",
     "section": "",
-    "text": "Complexity: Implementing multi-threading can introduce complexity and potential bugs.\nBrowser Compatibility: Ensuring full browser support for multi-threaded features may require additional effort."
+    "text": "This keeps low latency but reduces the needed bandwidth to sync 100,000 entities.\nNapkin math:\n50 bytes per frame per object * 100,000 objects = 5MB per frame.\n5MB/frame * 20 fps = 100MB = 1Gbps\nIf we send updates of all objects to all objects, that requires 100Tb/s\n\n&gt; yea 100k users at once is impossible any way you put it. I think a realistic goal is 1k, as like, our max goal\n\nRight, so you would need to not send updates for far away objects\n\nOnly send 1000 closest objects: 1Tb/s\n\n+ Send faraway objects at 2Hz: 100Gb/s\n\n+ Heavy delta compression: 10Gb/s\n\nThis is for all players\n\nThie means, in a hypothetical universe where distant objects only need position sync, a server with 10Gb/s NIC could theoretically run 100,000 concurrent users, if optimizzed!\n\nAlso, therefore, per player bandwidth **of distant objects** would be 100Kbit/s of downstream data, which is pretty small.\n\nAgain I haven't accounted for IK synchronization, or for additional nearby objects, so it could be higher here.\nNearby objects is a smaller problem and easier to solve, and belongs in a separate proposal."
   },
   {
-    "objectID": "decisions/20240710-use-godot-engine-web-threaded.html#the-road-not-taken",
-    "href": "decisions/20240710-use-godot-engine-web-threaded.html#the-road-not-taken",
-    "title": "Proposed: Use Godot Engine Web Threaded",
+    "objectID": "decisions/20221019-networking-100000-entities-ownership.html#negative-consequences",
+    "href": "decisions/20221019-networking-100000-entities-ownership.html#negative-consequences",
+    "title": "Proposed: Networking with 100000 Entities and Ownership (Revision 2)",
     "section": "",
-    "text": "Alternative approaches such as sticking with single-threaded implementations were considered but ultimately deemed less effective for handling large resources."
+    "text": "We may be overcomplicating a problem that doesn’t need to be solved yet. Pure interest management may be sufficient, and we do not currently have this many users."
   },
   {
-    "objectID": "decisions/20240710-use-godot-engine-web-threaded.html#the-infrequent-use-case",
-    "href": "decisions/20240710-use-godot-engine-web-threaded.html#the-infrequent-use-case",
-    "title": "Proposed: Use Godot Engine Web Threaded",
+    "objectID": "decisions/20221019-networking-100000-entities-ownership.html#references",
+    "href": "decisions/20221019-networking-100000-entities-ownership.html#references",
+    "title": "Proposed: Networking with 100000 Entities and Ownership (Revision 2)",
     "section": "",
-    "text": "In cases where the application does not involve large resources or complex audio processing, single-threaded implementation might suffice."
+    "text": "Source:\nDiscord VC with Malek and iFire\nDiscord channel forum-v-sekai “Networking with librg” thread: https://discord.com/channels/471446618156040210/1031379649776848900/1032401929587929208"
   },
   {
-    "objectID": "decisions/20240710-use-godot-engine-web-threaded.html#in-core-and-done-by-us",
-    "href": "decisions/20240710-use-godot-engine-web-threaded.html#in-core-and-done-by-us",
-    "title": "Proposed: Use Godot Engine Web Threaded",
+    "objectID": "decisions/20221019-networking-100000-entities-ownership.html#license-of-the-contribution",
+    "href": "decisions/20221019-networking-100000-entities-ownership.html#license-of-the-contribution",
+    "title": "Proposed: Networking with 100000 Entities and Ownership (Revision 2)",
     "section": "",
-    "text": "This proposal aligns with our core values of efficiency and performance and will be implemented by our team."
+    "text": "Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240710-use-godot-engine-web-threaded.html#status",
-    "href": "decisions/20240710-use-godot-engine-web-threaded.html#status",
-    "title": "Proposed: Use Godot Engine Web Threaded",
+    "objectID": "decisions/20210811-min-spec-v-sekai.html",
+    "href": "decisions/20210811-min-spec-v-sekai.html",
+    "title": "Proposed: Minimum Specification V-Sekai Hardware",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "Proposed: Minimum Specification V-Sekai Hardware\n\nContext and Problem Statement\nTags: hardware proxy, minimum spec,\nWe want to create standardized performance numbers for V-Sekai.\nPerformance targets:\n\nAchieve 16.67 milliseconds (60 FPS) frame time on a 4k screen for V-Sekai in desktop flat mode.\nThe 16.67 milliseconds target should be achieved smoothly and not as the average.\nFrom the Steam Hardware Survey (July 2021) accessed on August 2021, there are 25% of gamers who have a maximum of 8 gigabytes of ram.\n\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nWe want to create a standard test platform for V-Sekai to get performance data.\n\nCanonical test/reference hardware by platform (desktop-flat, desktop-vr, mobile-vr)\nCanonical content by platform (avatar+map): both low end (Mozilla Hubs + static avatars) and mid-end and high-end\n\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nSpecify a minimum specification.\n\nSingle Board Computers UDOO BOLT GEAR - kit based on UDOOBOLT V8 with metallic case.\n\nThis is the computer we think is the most similar to a Valve Steamdeck.\n\nSolid State Drives - SSD 1 TB\nSolid State Drive - OS Drive (Size TBD)\nMemory Modules “NCNR” 260pin SODIMM ECC DDR4 2666 16GB1.2v 1Gx8(0-85) We use ECC to during testing avoid “Godbolts” from the universe.\nWindows 10 operating system Windows 10 is what typical PCVR uses.\nPopos! 20.04 operating system Popos! Linux is similar to the Arch Linux that Steam Deck uses.\n\nUse a scripted fly through demo.\n\nhttps://github.com/Calinou/godot-cmvalley\nhttps://github.com/TokageItLab/3d-platform-test-for-godot4\nAn animated camera can be exported from Blender.\nRecord performance data in .res format and also json.\nRecord OBS videos of the fly through with frametime and stats.\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot coding related.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\n\nOnly represent AMD APUs.\nHardware is fairly new. Only a few years old.\nSteam Deck uses quad-channel DDR5 instead of dual-channel DDR4, and also DLNA2 instead of Vega graphics\n\n\n\nIs there a reason why this should be core and done by us?\nAs a platform holder, it would be our responsibility to understand the limits of the platform.\n\n\nReferences\n\nUDOO Bolt datasheet_udoo_bolt_gear-1947342.pdf\nMouser Electronics Canada V-Sekai Platform.pdf\nhttps://developer.oculus.com/documentation/unity/unity-perf/\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240710-use-godot-engine-web-threaded.html#decision-makers",
-    "href": "decisions/20240710-use-godot-engine-web-threaded.html#decision-makers",
-    "title": "Proposed: Use Godot Engine Web Threaded",
+    "objectID": "decisions/20211005-we-want-to-proxy-udp-datagrams-at-production-quality-of-service.html",
+    "href": "decisions/20211005-we-want-to-proxy-udp-datagrams-at-production-quality-of-service.html",
+    "title": "Proposed: We want to proxy udp datagrams at production quality of service.",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "Proposed: We want to proxy udp datagrams at production quality of service.\n\nContext and Problem Statement\nWe want to proxy udp datagrams at production quality of service.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nThe ability to proxy V-Sekai game datagrams is an important part of the player experience.\nWe require that the proxy is able to handle both versions of DTLS inside of WebRTC and also with ENET.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nNo idea.\n\nWIP\n\nWireGuard in Cilium allows mesh kubernetes clustering\n\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNetworking and game networking are not a few lines of code. Game networking is game specific and the quality matters.\n\n\nPositive Consequences\n\nAllows greater access to potential users.\nWeb browser support requires webrtc.\n\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nWe own game networking.\n\n\nReferences\n\nhttps://github.com/yyyar/gobetween\nhttps://ebpf.io/\nhttps://cilium.io/\nhttps://docs.cilium.io/en/stable/gettingstarted/encryption-wireguard/\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240710-use-godot-engine-web-threaded.html#tags",
-    "href": "decisions/20240710-use-godot-engine-web-threaded.html#tags",
-    "title": "Proposed: Use Godot Engine Web Threaded",
+    "objectID": "decisions/20231109-discord-polygonjs-generator.html",
+    "href": "decisions/20231109-discord-polygonjs-generator.html",
+    "title": "Proposed: Character Customization Discord Bot PoC for V-Sekai",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Status: Proposed \nDeciders: V-Sekai, fire\nTags: V-Sekai, Character Customization, Discord Bot, PoC\n\n\n\n\nWithin the V-Sekai community, there is a desire to enhance user engagement through interactive tools that allow for creative expression. The community seeks to leverage Discord as a platform to introduce such tools.\n\n\n\nThe current challenge is to create an interactive Discord bot that allows for immersive character customization, aligning with V-Sekai’s vision of fostering a creative and engaged community.\n\n\n\nTo create a Discord bot as a Proof of Concept (PoC) that demonstrates the feasibility of character customization using trait-based input, we will execute the following steps:\n\nDefine Key Traits: We will select a set of fundamental character traits such as height, body shape, hair color, and clothing style. Each trait will be associated with a Unicode emoji for straightforward identification and interaction within the Discord interface.\nBot Development: A bot will be developed to parse textual commands linked to each trait. For example, a user might input !height 📏 to set the character’s height or !hair 🎨 to choose a hair color.\nImage Generation: The bot will map each trait to a specific set of 2D image assets. It will have the logic to composite these assets into a single image that represents the character based on the selected traits.\nUser Interaction: Reaction buttons for ‘like’ 👍, ‘dislike’ 👎, and ‘regenerate’ 🔄 will be implemented to allow users to interact with the generated character. This will provide immediate feedback mechanisms for the community.\nTesting and Iteration: The bot will be deployed in a controlled Discord environment and tested by real users. Their feedback will be crucial for refining the bot’s functionality and user experience.\nDocumentation: All development processes, user interactions, and iterations will be thoroughly documented. This documentation will be critical for understanding user needs and will inform future development cycles.\n\nThis PoC will serve to validate the core idea, engage the user community early in the development process, and provide critical insights for scaling the bot to handle more complex trait manipulation and 3D character rendering in future phases.\n\n\n\nImplementing this bot will potentially increase community engagement by providing a fun and interactive character creation tool. It will also lay the foundation for future developments in VR and character design within the V-Sekai ecosystem.\n\n\n\nThe initial development of the bot may require significant resources and there is a risk of low user adoption. Additionally, ensuring the bot’s scalability and handling user feedback for improvements could be challenging.\n\n\n\nAlternatives, such as outsourcing the tool or purchasing an existing solution, were considered but ultimately rejected in favor of in-house development to retain creative control and better integration with V-Sekai’s infrastructure.\n\n\n\nThere might be less frequent use cases for the bot, such as character customization for one-time events or non-regular users. The bot’s design will need to account for these to ensure it remains relevant and accessible.\n\n\n\nThe core functionality of the bot aligns with V-Sekai’s objectives and values. The development will be handled internally to ensure the tool’s compatibility with the community’s needs and expectations.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nV-Sekai Official Website - Community of enthusiasts building a next-generation social and gaming VR platform powered by the Godot Engine 4.0\nNousResearch Yarn Mistral 7b 128k - Hugging Face - A Hugging Face Space by realgenius\nIssue #68 · polygonjs/polygonjs - GitHub - Discussion on using polygon.js as a Discord webhook watcher to output messages and attachments\n\nThis article was assisted by AI."
   },
   {
-    "objectID": "decisions/20240710-use-godot-engine-web-threaded.html#further-reading",
-    "href": "decisions/20240710-use-godot-engine-web-threaded.html#further-reading",
-    "title": "Proposed: Use Godot Engine Web Threaded",
+    "objectID": "decisions/20231109-discord-polygonjs-generator.html#metadata",
+    "href": "decisions/20231109-discord-polygonjs-generator.html#metadata",
+    "title": "Proposed: Character Customization Discord Bot PoC for V-Sekai",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "Status: Proposed \nDeciders: V-Sekai, fire\nTags: V-Sekai, Character Customization, Discord Bot, PoC"
   },
   {
-    "objectID": "decisions/20230803-jolt-gextension-to-module.html",
-    "href": "decisions/20230803-jolt-gextension-to-module.html",
-    "title": "Proposed: Port Godot Jolt from GDExtension to C++ Module",
+    "objectID": "decisions/20231109-discord-polygonjs-generator.html#the-backdrop",
+    "href": "decisions/20231109-discord-polygonjs-generator.html#the-backdrop",
+    "title": "Proposed: Character Customization Discord Bot PoC for V-Sekai",
     "section": "",
-    "text": "Status: Proposed\nDeciders: v-sekai, fire\nTags: Godot, Jolt, GDExtension, C++ Module, SCons, CMake\n\n\n\n\nGodot Jolt is currently implemented as a GDExtension C++ extension. However, we want to use it as a C++ module, which requires porting from CMake to SCons. This change will also allow us to experiment with soft physics.\n\n\n\n\n\n\nAnalyze the current structure of Godot Jolt as a GDExtension.\nPlan the new structure as a C++ module.\nConvert the build system from CMake to SCons.\nTest the newly created C++ module in different scenarios.\nExperiment with soft physics once the module is stable.\n\n\n\n\n\nThe implementation details will be decided upon acceptance of this proposal.\n\n\n\n\nMore control over the engine’s core functionality.\nAbility to experiment with soft physics.\nBetter integration with Godot’s core systems.\nEnable double precision support\n\n\n\n\n\nRequires knowledge of both CMake and SCons.\nPotential increase in development time due to the complexity of porting.\n\n\n\n\nThis section will be filled as we explore different options and discard those that are not feasible or effective.\n\n\n\nGiven the complexity of porting a GDExtension to a C++ module, it cannot be simply worked around with a few lines of script.\n\n\n\nPorting Godot Jolt to a C++ module will provide more flexibility and control over its functionalities. It aligns with our goal of enhancing the capabilities of our game engine.\n\n\n\n\nGodot Engine\nSCons\nCMake"
+    "text": "Within the V-Sekai community, there is a desire to enhance user engagement through interactive tools that allow for creative expression. The community seeks to leverage Discord as a platform to introduce such tools."
   },
   {
-    "objectID": "decisions/20230803-jolt-gextension-to-module.html#metadata",
-    "href": "decisions/20230803-jolt-gextension-to-module.html#metadata",
-    "title": "Proposed: Port Godot Jolt from GDExtension to C++ Module",
+    "objectID": "decisions/20231109-discord-polygonjs-generator.html#the-challenge",
+    "href": "decisions/20231109-discord-polygonjs-generator.html#the-challenge",
+    "title": "Proposed: Character Customization Discord Bot PoC for V-Sekai",
     "section": "",
-    "text": "Status: Proposed\nDeciders: v-sekai, fire\nTags: Godot, Jolt, GDExtension, C++ Module, SCons, CMake"
+    "text": "The current challenge is to create an interactive Discord bot that allows for immersive character customization, aligning with V-Sekai’s vision of fostering a creative and engaged community."
   },
   {
-    "objectID": "decisions/20230803-jolt-gextension-to-module.html#context-and-problem-statement",
-    "href": "decisions/20230803-jolt-gextension-to-module.html#context-and-problem-statement",
-    "title": "Proposed: Port Godot Jolt from GDExtension to C++ Module",
+    "objectID": "decisions/20231109-discord-polygonjs-generator.html#the-strategy",
+    "href": "decisions/20231109-discord-polygonjs-generator.html#the-strategy",
+    "title": "Proposed: Character Customization Discord Bot PoC for V-Sekai",
     "section": "",
-    "text": "Godot Jolt is currently implemented as a GDExtension C++ extension. However, we want to use it as a C++ module, which requires porting from CMake to SCons. This change will also allow us to experiment with soft physics."
+    "text": "To create a Discord bot as a Proof of Concept (PoC) that demonstrates the feasibility of character customization using trait-based input, we will execute the following steps:\n\nDefine Key Traits: We will select a set of fundamental character traits such as height, body shape, hair color, and clothing style. Each trait will be associated with a Unicode emoji for straightforward identification and interaction within the Discord interface.\nBot Development: A bot will be developed to parse textual commands linked to each trait. For example, a user might input !height 📏 to set the character’s height or !hair 🎨 to choose a hair color.\nImage Generation: The bot will map each trait to a specific set of 2D image assets. It will have the logic to composite these assets into a single image that represents the character based on the selected traits.\nUser Interaction: Reaction buttons for ‘like’ 👍, ‘dislike’ 👎, and ‘regenerate’ 🔄 will be implemented to allow users to interact with the generated character. This will provide immediate feedback mechanisms for the community.\nTesting and Iteration: The bot will be deployed in a controlled Discord environment and tested by real users. Their feedback will be crucial for refining the bot’s functionality and user experience.\nDocumentation: All development processes, user interactions, and iterations will be thoroughly documented. This documentation will be critical for understanding user needs and will inform future development cycles.\n\nThis PoC will serve to validate the core idea, engage the user community early in the development process, and provide critical insights for scaling the bot to handle more complex trait manipulation and 3D character rendering in future phases."
   },
   {
-    "objectID": "decisions/20230803-jolt-gextension-to-module.html#proposed-solution",
-    "href": "decisions/20230803-jolt-gextension-to-module.html#proposed-solution",
-    "title": "Proposed: Port Godot Jolt from GDExtension to C++ Module",
+    "objectID": "decisions/20231109-discord-polygonjs-generator.html#the-upside",
+    "href": "decisions/20231109-discord-polygonjs-generator.html#the-upside",
+    "title": "Proposed: Character Customization Discord Bot PoC for V-Sekai",
     "section": "",
-    "text": "Analyze the current structure of Godot Jolt as a GDExtension.\nPlan the new structure as a C++ module.\nConvert the build system from CMake to SCons.\nTest the newly created C++ module in different scenarios.\nExperiment with soft physics once the module is stable."
+    "text": "Implementing this bot will potentially increase community engagement by providing a fun and interactive character creation tool. It will also lay the foundation for future developments in VR and character design within the V-Sekai ecosystem."
   },
   {
-    "objectID": "decisions/20230803-jolt-gextension-to-module.html#implementation",
-    "href": "decisions/20230803-jolt-gextension-to-module.html#implementation",
-    "title": "Proposed: Port Godot Jolt from GDExtension to C++ Module",
+    "objectID": "decisions/20231109-discord-polygonjs-generator.html#the-downside",
+    "href": "decisions/20231109-discord-polygonjs-generator.html#the-downside",
+    "title": "Proposed: Character Customization Discord Bot PoC for V-Sekai",
     "section": "",
-    "text": "The implementation details will be decided upon acceptance of this proposal."
+    "text": "The initial development of the bot may require significant resources and there is a risk of low user adoption. Additionally, ensuring the bot’s scalability and handling user feedback for improvements could be challenging."
   },
   {
-    "objectID": "decisions/20230803-jolt-gextension-to-module.html#positive-consequences",
-    "href": "decisions/20230803-jolt-gextension-to-module.html#positive-consequences",
-    "title": "Proposed: Port Godot Jolt from GDExtension to C++ Module",
+    "objectID": "decisions/20231109-discord-polygonjs-generator.html#the-road-not-taken",
+    "href": "decisions/20231109-discord-polygonjs-generator.html#the-road-not-taken",
+    "title": "Proposed: Character Customization Discord Bot PoC for V-Sekai",
     "section": "",
-    "text": "More control over the engine’s core functionality.\nAbility to experiment with soft physics.\nBetter integration with Godot’s core systems.\nEnable double precision support"
+    "text": "Alternatives, such as outsourcing the tool or purchasing an existing solution, were considered but ultimately rejected in favor of in-house development to retain creative control and better integration with V-Sekai’s infrastructure."
   },
   {
-    "objectID": "decisions/20230803-jolt-gextension-to-module.html#negative-consequences",
-    "href": "decisions/20230803-jolt-gextension-to-module.html#negative-consequences",
-    "title": "Proposed: Port Godot Jolt from GDExtension to C++ Module",
+    "objectID": "decisions/20231109-discord-polygonjs-generator.html#the-infrequent-use-case",
+    "href": "decisions/20231109-discord-polygonjs-generator.html#the-infrequent-use-case",
+    "title": "Proposed: Character Customization Discord Bot PoC for V-Sekai",
     "section": "",
-    "text": "Requires knowledge of both CMake and SCons.\nPotential increase in development time due to the complexity of porting."
+    "text": "There might be less frequent use cases for the bot, such as character customization for one-time events or non-regular users. The bot’s design will need to account for these to ensure it remains relevant and accessible."
   },
   {
-    "objectID": "decisions/20230803-jolt-gextension-to-module.html#option-graveyard",
-    "href": "decisions/20230803-jolt-gextension-to-module.html#option-graveyard",
-    "title": "Proposed: Port Godot Jolt from GDExtension to C++ Module",
+    "objectID": "decisions/20231109-discord-polygonjs-generator.html#in-core-and-done-by-us",
+    "href": "decisions/20231109-discord-polygonjs-generator.html#in-core-and-done-by-us",
+    "title": "Proposed: Character Customization Discord Bot PoC for V-Sekai",
     "section": "",
-    "text": "This section will be filled as we explore different options and discard those that are not feasible or effective."
+    "text": "The core functionality of the bot aligns with V-Sekai’s objectives and values. The development will be handled internally to ensure the tool’s compatibility with the community’s needs and expectations."
   },
   {
-    "objectID": "decisions/20230803-jolt-gextension-to-module.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230803-jolt-gextension-to-module.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Port Godot Jolt from GDExtension to C++ Module",
+    "objectID": "decisions/20231109-discord-polygonjs-generator.html#further-reading",
+    "href": "decisions/20231109-discord-polygonjs-generator.html#further-reading",
+    "title": "Proposed: Character Customization Discord Bot PoC for V-Sekai",
     "section": "",
-    "text": "Given the complexity of porting a GDExtension to a C++ module, it cannot be simply worked around with a few lines of script."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nV-Sekai Official Website - Community of enthusiasts building a next-generation social and gaming VR platform powered by the Godot Engine 4.0\nNousResearch Yarn Mistral 7b 128k - Hugging Face - A Hugging Face Space by realgenius\nIssue #68 · polygonjs/polygonjs - GitHub - Discussion on using polygon.js as a Discord webhook watcher to output messages and attachments\n\nThis article was assisted by AI."
   },
   {
-    "objectID": "decisions/20230803-jolt-gextension-to-module.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230803-jolt-gextension-to-module.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Port Godot Jolt from GDExtension to C++ Module",
+    "objectID": "decisions/20230830-generating-v-sekai-worlds.html",
+    "href": "decisions/20230830-generating-v-sekai-worlds.html",
+    "title": "Proposed: Expanding Worlds",
     "section": "",
-    "text": "Porting Godot Jolt to a C++ module will provide more flexibility and control over its functionalities. It aligns with our goal of enhancing the capabilities of our game engine."
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nV-Sekai is a virtual reality (VR) platform that offers users the opportunity to immerse themselves in virtual worlds. However, there are certain limitations that hinder the overall user experience. This proposal aims to address these limitations by proposing specific areas for improvement within V-Sekai.\n\n\n\nV-Sekai currently faces several limitations, including non-functional menus in VR mode and a limited number of available worlds. These challenges affect the usability and variety of experiences for the users. To overcome these challenges and enhance the V-Sekai user experience, we must prioritize and focus on one area for improvement.\n\n\nWe propose focusing on Generating More Worlds as the first step towards enhancing V-Sekai. By creating new VR worlds within V-Sekai, users will have a wider range of experiences to explore. This involves designing and implementing new environments to expand the options available. With more worlds to choose from, users will have increased engagement and longer sessions within the V-Sekai platform.\n\n\n\n\nTo generate more worlds for V-Sekai, we will follow a comprehensive strategy that includes the following steps:\n\nIdentify User Preferences: Understand the target audience and their preferences. Research popular VR themes, genres, and settings to get an idea of what users would enjoy.\nDesign New Environments: Use 3D modeling software like Blender or Unity to design new virtual environments for V-Sekai. Consider creating diverse worlds like fantasy realms, futuristic cities, natural landscapes, or historical settings.\nImplement Interactive Elements: Make the new worlds interactive by adding objects, characters, and elements that users can engage with. This can include non-playable characters (NPCs), puzzles, hidden items, or mini-games within each world.\nTest and Refine: Conduct thorough testing to ensure the new worlds are visually appealing, optimized for performance, and provide a seamless VR experience. Gather user feedback and make necessary improvements based on their suggestions.\nIntegrate with V-Sekai: Once the new worlds are ready, integrate them into the V-Sekai platform. Ensure they are easily accessible through the menus or navigation system within V-Sekai’s VR interface.\nRelease and Promote: Launch the updated version of V-Sekai with the newly generated worlds. Promote the release through various channels, such as social media, gaming forums, Virtual Reality communities, and V-Sekai’s official website.\n\nBy following this strategy, we will not only address the current limitations but also create an engaging and immersive VR experience for V-Sekai users.\n\n\n\n\nIncreased user engagement: The availability of more worlds will provide users with greater options to explore, leading to longer sessions and increased immersion in V-Sekai.\nExpanded user base: With a wider range of experiences, V-Sekai will attract new users who are looking for diverse VR environments.\nPositive word-of-mouth: Satisfied users will share their experiences with others, generating positive reviews and recommendations for V-Sekai.\n\n\n\n\n\nDevelopment complexity: Creating new worlds requires significant effort and resources, including 3D modeling, programming, and testing. This may lead to increased development time and costs.\nUpfront investment: Generating more worlds will require upfront investment in terms of design, implementation, and integration with V-Sekai.\nUser feedback and iteration: Continuous user feedback is crucial to refine and improve the new worlds. This iterative process may extend the development timeline.\n\n\n\n\nAn alternative solution that was considered was Integrating Backend Services. This would involve improving the backend infrastructure of V-Sekai to enhance scalability, performance, and reliability. However, after careful consideration, we prioritize generating more worlds as it directly addresses user experience limitations and provides tangible benefits in terms of user engagement and appeal.\n\n\n\nThe generation of more worlds is within the core capabilities of our team at V-Sekai. We have experienced 3D designers, developers, and testers who are skilled in creating immersive VR environments. Therefore, we are confident in our ability to execute this proposed solution effectively and efficiently.\n\n\n\n\nV-Sekai\nThis article is assisted by AI.\n\nIf you have any further questions or need clarification on any aspect of this proposal, please feel free to ask."
   },
   {
-    "objectID": "decisions/20230803-jolt-gextension-to-module.html#references",
-    "href": "decisions/20230803-jolt-gextension-to-module.html#references",
-    "title": "Proposed: Port Godot Jolt from GDExtension to C++ Module",
+    "objectID": "decisions/20230830-generating-v-sekai-worlds.html#metadata",
+    "href": "decisions/20230830-generating-v-sekai-worlds.html#metadata",
+    "title": "Proposed: Expanding Worlds",
     "section": "",
-    "text": "Godot Engine\nSCons\nCMake"
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20240121-easy-diffusion-fedora-install.html",
-    "href": "decisions/20240121-easy-diffusion-fedora-install.html",
-    "title": "Proposed: Easy Diffusion AI Setup on Linux Systems",
+    "objectID": "decisions/20230830-generating-v-sekai-worlds.html#introduction",
+    "href": "decisions/20230830-generating-v-sekai-worlds.html#introduction",
+    "title": "Proposed: Expanding Worlds",
     "section": "",
-    "text": "Status: Proposed\nDeciders: Development Team\nTags: AI, Easy Diffusion, Linux\n\n\n\n\nThe goal is to streamline the installation process of Easy Diffusion for creating AI-generated images on Linux systems.\n\n\n\nThe challenge lies in ensuring a simple and repeatable setup process for installing and configuring Easy Diffusion on various Linux distributions.\n\n\n\n\nAssess compatibility between Easy Diffusion and popular Linux distributions.\nIdentify dependencies and prerequisites required for Easy Diffusion.\nDevelop a script or instructions for a hassle-free setup experience.\nConduct test installations across different environments.\n\nFirst, download the latest release of Easy Diffusion for Linux. Then create a dedicated user for running Easy Diffusion and establish a standard location for the tool, like /opt/easy_diffusion.\n# As root or using sudo\ndnf install curl bzip2 -y\nuseradd --system --create-home --home-dir /opt/easy_diffusion easy_diffusion_user\nmkdir -p /opt/easy_diffusion\ncurl -L https://github.com/cmdr2/stable-diffusion-ui/releases/latest/download/Easy-Diffusion-Linux.zip -o /opt/easy_diffusion/Easy-Diffusion-Linux.zip\nunzip /opt/easy_diffusion/Easy-Diffusion-Linux.zip -d /opt/easy_diffusion/\n\nsudo bash -c 'cat &gt; /opt/easy_diffusion/easy-diffusion/config.yaml &lt;&lt;EOF\n# Configuration for Easy Diffusion\n# Change listen_port if port 9000 is already in use on your system.\n# Set listen_to_network to true to make Easy Diffusion accessible on your local network.\n\nnet:\n  listen_port: 9000\n  listen_to_network: true\n\n# Multi GPU setup\nrender_devices: auto\n\n# Set open_browser_on_start to false to disable opening a new browser tab on each restart.\nui:\n  open_browser_on_start: false\n\n# Set update_branch to main to use the stable version, or to beta to use the experimental\n# beta version.\nupdate_branch: beta\n\n# Set force_save_path to enforce an auto save path. Clients will not be able to change or\n# disable auto save when this option is set. Please adapt the path in the examples to your\n# needs.\n# Windows:\n# force_save_path: C:\\\\Easy Diffusion Images\\\\\n# Linux:\n# force_save_path: /data/easy_diffusion_images/\nforce_save_path: /opt/easy_diffusion/easy_diffusion_images/\nEOF'\nchown -R easy_diffusion_user: /opt/easy_diffusion\nchmod +x /opt/easy_diffusion/easy-diffusion/start.sh\nA systemd service configuration is used to manage the Easy Diffusion process:\nsudo bash -c 'cat &gt; /etc/systemd/system/easy-diffusion.service &lt;&lt;EOF\n[Unit]\nDescription=Easy Diffusion AI Image Generation Tool\nAfter=network.target\n\n[Service]\nUser=easy_diffusion_user\nWorkingDirectory=/opt/easy_diffusion/easy-diffusion\nExecStart=/bin/bash /opt/easy_diffusion/easy-diffusion/start.sh\nRestart=on-failure\n\n[Install]\nWantedBy=multi-user.target\nEOF'\nEnable and start the service as follows:\nsudo systemctl daemon-reload\nsudo systemctl enable easy-diffusion.service\nsudo systemctl start easy-diffusion.service\nCheck the status to confirm correct operation:\nsudo systemctl status easy-diffusion.service\nTo view detailed logs, use:\njournalctl -u easy-diffusion.service\n\n\n\n\nAutomates the setup process, minimizing user intervention.\nOffers consistency across different installations.\nSimplifies management with systemd integration.\n\n\n\n\n\nRequires thorough testing to ensure broad compatibility.\nSystemd is not universally adopted among all Linux distributions.\nAdditional effort is needed to maintain the service file and update paths as necessary when new versions are released.\n\n\n\n\n\nDownload for Linux: Official source code and documentation.\n\nAria, an AI assistant, provided support in formulating this proposal."
+    "text": "V-Sekai is a virtual reality (VR) platform that offers users the opportunity to immerse themselves in virtual worlds. However, there are certain limitations that hinder the overall user experience. This proposal aims to address these limitations by proposing specific areas for improvement within V-Sekai."
   },
   {
-    "objectID": "decisions/20240121-easy-diffusion-fedora-install.html#metadata",
-    "href": "decisions/20240121-easy-diffusion-fedora-install.html#metadata",
-    "title": "Proposed: Easy Diffusion AI Setup on Linux Systems",
+    "objectID": "decisions/20230830-generating-v-sekai-worlds.html#the-challenge",
+    "href": "decisions/20230830-generating-v-sekai-worlds.html#the-challenge",
+    "title": "Proposed: Expanding Worlds",
     "section": "",
-    "text": "Status: Proposed\nDeciders: Development Team\nTags: AI, Easy Diffusion, Linux"
+    "text": "V-Sekai currently faces several limitations, including non-functional menus in VR mode and a limited number of available worlds. These challenges affect the usability and variety of experiences for the users. To overcome these challenges and enhance the V-Sekai user experience, we must prioritize and focus on one area for improvement.\n\n\nWe propose focusing on Generating More Worlds as the first step towards enhancing V-Sekai. By creating new VR worlds within V-Sekai, users will have a wider range of experiences to explore. This involves designing and implementing new environments to expand the options available. With more worlds to choose from, users will have increased engagement and longer sessions within the V-Sekai platform."
   },
   {
-    "objectID": "decisions/20240121-easy-diffusion-fedora-install.html#backdrop",
-    "href": "decisions/20240121-easy-diffusion-fedora-install.html#backdrop",
-    "title": "Proposed: Easy Diffusion AI Setup on Linux Systems",
+    "objectID": "decisions/20230830-generating-v-sekai-worlds.html#the-strategy",
+    "href": "decisions/20230830-generating-v-sekai-worlds.html#the-strategy",
+    "title": "Proposed: Expanding Worlds",
     "section": "",
-    "text": "The goal is to streamline the installation process of Easy Diffusion for creating AI-generated images on Linux systems."
+    "text": "To generate more worlds for V-Sekai, we will follow a comprehensive strategy that includes the following steps:\n\nIdentify User Preferences: Understand the target audience and their preferences. Research popular VR themes, genres, and settings to get an idea of what users would enjoy.\nDesign New Environments: Use 3D modeling software like Blender or Unity to design new virtual environments for V-Sekai. Consider creating diverse worlds like fantasy realms, futuristic cities, natural landscapes, or historical settings.\nImplement Interactive Elements: Make the new worlds interactive by adding objects, characters, and elements that users can engage with. This can include non-playable characters (NPCs), puzzles, hidden items, or mini-games within each world.\nTest and Refine: Conduct thorough testing to ensure the new worlds are visually appealing, optimized for performance, and provide a seamless VR experience. Gather user feedback and make necessary improvements based on their suggestions.\nIntegrate with V-Sekai: Once the new worlds are ready, integrate them into the V-Sekai platform. Ensure they are easily accessible through the menus or navigation system within V-Sekai’s VR interface.\nRelease and Promote: Launch the updated version of V-Sekai with the newly generated worlds. Promote the release through various channels, such as social media, gaming forums, Virtual Reality communities, and V-Sekai’s official website.\n\nBy following this strategy, we will not only address the current limitations but also create an engaging and immersive VR experience for V-Sekai users."
   },
   {
-    "objectID": "decisions/20240121-easy-diffusion-fedora-install.html#challenge",
-    "href": "decisions/20240121-easy-diffusion-fedora-install.html#challenge",
-    "title": "Proposed: Easy Diffusion AI Setup on Linux Systems",
+    "objectID": "decisions/20230830-generating-v-sekai-worlds.html#upsides",
+    "href": "decisions/20230830-generating-v-sekai-worlds.html#upsides",
+    "title": "Proposed: Expanding Worlds",
     "section": "",
-    "text": "The challenge lies in ensuring a simple and repeatable setup process for installing and configuring Easy Diffusion on various Linux distributions."
+    "text": "Increased user engagement: The availability of more worlds will provide users with greater options to explore, leading to longer sessions and increased immersion in V-Sekai.\nExpanded user base: With a wider range of experiences, V-Sekai will attract new users who are looking for diverse VR environments.\nPositive word-of-mouth: Satisfied users will share their experiences with others, generating positive reviews and recommendations for V-Sekai."
   },
   {
-    "objectID": "decisions/20240121-easy-diffusion-fedora-install.html#strategy",
-    "href": "decisions/20240121-easy-diffusion-fedora-install.html#strategy",
-    "title": "Proposed: Easy Diffusion AI Setup on Linux Systems",
+    "objectID": "decisions/20230830-generating-v-sekai-worlds.html#downsides",
+    "href": "decisions/20230830-generating-v-sekai-worlds.html#downsides",
+    "title": "Proposed: Expanding Worlds",
     "section": "",
-    "text": "Assess compatibility between Easy Diffusion and popular Linux distributions.\nIdentify dependencies and prerequisites required for Easy Diffusion.\nDevelop a script or instructions for a hassle-free setup experience.\nConduct test installations across different environments.\n\nFirst, download the latest release of Easy Diffusion for Linux. Then create a dedicated user for running Easy Diffusion and establish a standard location for the tool, like /opt/easy_diffusion.\n# As root or using sudo\ndnf install curl bzip2 -y\nuseradd --system --create-home --home-dir /opt/easy_diffusion easy_diffusion_user\nmkdir -p /opt/easy_diffusion\ncurl -L https://github.com/cmdr2/stable-diffusion-ui/releases/latest/download/Easy-Diffusion-Linux.zip -o /opt/easy_diffusion/Easy-Diffusion-Linux.zip\nunzip /opt/easy_diffusion/Easy-Diffusion-Linux.zip -d /opt/easy_diffusion/\n\nsudo bash -c 'cat &gt; /opt/easy_diffusion/easy-diffusion/config.yaml &lt;&lt;EOF\n# Configuration for Easy Diffusion\n# Change listen_port if port 9000 is already in use on your system.\n# Set listen_to_network to true to make Easy Diffusion accessible on your local network.\n\nnet:\n  listen_port: 9000\n  listen_to_network: true\n\n# Multi GPU setup\nrender_devices: auto\n\n# Set open_browser_on_start to false to disable opening a new browser tab on each restart.\nui:\n  open_browser_on_start: false\n\n# Set update_branch to main to use the stable version, or to beta to use the experimental\n# beta version.\nupdate_branch: beta\n\n# Set force_save_path to enforce an auto save path. Clients will not be able to change or\n# disable auto save when this option is set. Please adapt the path in the examples to your\n# needs.\n# Windows:\n# force_save_path: C:\\\\Easy Diffusion Images\\\\\n# Linux:\n# force_save_path: /data/easy_diffusion_images/\nforce_save_path: /opt/easy_diffusion/easy_diffusion_images/\nEOF'\nchown -R easy_diffusion_user: /opt/easy_diffusion\nchmod +x /opt/easy_diffusion/easy-diffusion/start.sh\nA systemd service configuration is used to manage the Easy Diffusion process:\nsudo bash -c 'cat &gt; /etc/systemd/system/easy-diffusion.service &lt;&lt;EOF\n[Unit]\nDescription=Easy Diffusion AI Image Generation Tool\nAfter=network.target\n\n[Service]\nUser=easy_diffusion_user\nWorkingDirectory=/opt/easy_diffusion/easy-diffusion\nExecStart=/bin/bash /opt/easy_diffusion/easy-diffusion/start.sh\nRestart=on-failure\n\n[Install]\nWantedBy=multi-user.target\nEOF'\nEnable and start the service as follows:\nsudo systemctl daemon-reload\nsudo systemctl enable easy-diffusion.service\nsudo systemctl start easy-diffusion.service\nCheck the status to confirm correct operation:\nsudo systemctl status easy-diffusion.service\nTo view detailed logs, use:\njournalctl -u easy-diffusion.service"
+    "text": "Development complexity: Creating new worlds requires significant effort and resources, including 3D modeling, programming, and testing. This may lead to increased development time and costs.\nUpfront investment: Generating more worlds will require upfront investment in terms of design, implementation, and integration with V-Sekai.\nUser feedback and iteration: Continuous user feedback is crucial to refine and improve the new worlds. This iterative process may extend the development timeline."
   },
   {
-    "objectID": "decisions/20240121-easy-diffusion-fedora-install.html#upside",
-    "href": "decisions/20240121-easy-diffusion-fedora-install.html#upside",
-    "title": "Proposed: Easy Diffusion AI Setup on Linux Systems",
+    "objectID": "decisions/20230830-generating-v-sekai-worlds.html#the-road-not-taken",
+    "href": "decisions/20230830-generating-v-sekai-worlds.html#the-road-not-taken",
+    "title": "Proposed: Expanding Worlds",
     "section": "",
-    "text": "Automates the setup process, minimizing user intervention.\nOffers consistency across different installations.\nSimplifies management with systemd integration."
+    "text": "An alternative solution that was considered was Integrating Backend Services. This would involve improving the backend infrastructure of V-Sekai to enhance scalability, performance, and reliability. However, after careful consideration, we prioritize generating more worlds as it directly addresses user experience limitations and provides tangible benefits in terms of user engagement and appeal."
   },
   {
-    "objectID": "decisions/20240121-easy-diffusion-fedora-install.html#downside",
-    "href": "decisions/20240121-easy-diffusion-fedora-install.html#downside",
-    "title": "Proposed: Easy Diffusion AI Setup on Linux Systems",
+    "objectID": "decisions/20230830-generating-v-sekai-worlds.html#in-core-and-done-by-us",
+    "href": "decisions/20230830-generating-v-sekai-worlds.html#in-core-and-done-by-us",
+    "title": "Proposed: Expanding Worlds",
     "section": "",
-    "text": "Requires thorough testing to ensure broad compatibility.\nSystemd is not universally adopted among all Linux distributions.\nAdditional effort is needed to maintain the service file and update paths as necessary when new versions are released."
+    "text": "The generation of more worlds is within the core capabilities of our team at V-Sekai. We have experienced 3D designers, developers, and testers who are skilled in creating immersive VR environments. Therefore, we are confident in our ability to execute this proposed solution effectively and efficiently."
   },
   {
-    "objectID": "decisions/20240121-easy-diffusion-fedora-install.html#further-reading",
-    "href": "decisions/20240121-easy-diffusion-fedora-install.html#further-reading",
-    "title": "Proposed: Easy Diffusion AI Setup on Linux Systems",
+    "objectID": "decisions/20230830-generating-v-sekai-worlds.html#further-reading",
+    "href": "decisions/20230830-generating-v-sekai-worlds.html#further-reading",
+    "title": "Proposed: Expanding Worlds",
     "section": "",
-    "text": "Download for Linux: Official source code and documentation.\n\nAria, an AI assistant, provided support in formulating this proposal."
+    "text": "V-Sekai\nThis article is assisted by AI.\n\nIf you have any further questions or need clarification on any aspect of this proposal, please feel free to ask."
   },
   {
-    "objectID": "decisions/20240105-1-meter-128-quantize.html",
-    "href": "decisions/20240105-1-meter-128-quantize.html",
-    "title": "Proposed: 1 Meter Cubed 128 Quantized",
+    "objectID": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html",
+    "href": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html",
+    "title": "Proposed: Modify the Mesh Transformer for Quads",
     "section": "",
-    "text": "Status: Proposed \nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nMeshGPT’s “1 Meter Cubed 128 Quantized” format has emerged as a potential method to achieve standardized precision within virtual reality (VR) content creation, centring around polygonal modeling rather than voxel methods.\n\n\n\nThe key objective is to harness the potential of the “1 Meter Cubed 128 Quantized” format to enhance procedural generation processes within VR development.\n\n\n\n\nDevelop a comprehensive framework for environment generation that leverages the strengths of the polygonal quantized format.\nIntegrate adaptive algorithms tailored for this format to ensure dynamic responsiveness in VR spaces.\nEmbrace modular design paradigms that align with polygonal modeling to expedite the construction of VR environments.\n\n\n\n\n\nFosters a more intuitive AI-creator collaboration using a polygonal format conducive to AI tools.\nLowers barriers to entry for creators, leading to increased efficiency and innovation.\nStreamlines procedural generation to operate with enhanced speed and reduced resource consumption.\nProvides a scalable and flexible model to cater to diverse design requirements in VR environments.\n\n\n\n\n\nRequires considerable investment in research and development for effective technique integration.\nMay present a learning curve for developers not familiar with non-voxel formats.\n\n\n\n\n\nDependence on traditional voxel-based procedural generation technologies could be left behind in favor of the enhanced capabilities offered by the polygonal quantized format.\n\n\n\n\n\nSpecialized VR environments may demand generation methods that extend beyond the standard capacities of the “1 Meter Cubed 128 Quantized” format.\n\n\n\n\n\nThe enhancement of procedural generation via the adoption of the 1 Meter Cubed 128 Quantized polygonal format is an initiative headed by the V-Sekai team.\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nShadows of Doubt on Steam - A showcase of the advancements made possible through procedural generation in gaming.\n\nAssisted by AI Aria."
+    "text": "We’re working on a project that involves using an autoencoder/transformer for 3D models. The current setup does not have a setting for quads, which is a requirement for our project.\n\n\n\nThe challenge is to modify the autoencoder/transformer to include a setting for quads and achieve a loss around 0.35.\n\n\n\n\nModify the Autoencoder/Transformer: Update the existing code to include a quads=True parameter in the autoencoder/transformer.\nTest the Modification: Run tests to ensure that the modification works as expected and doesn’t break existing functionality.\nOptimize the Loss: Adjust the parameters and settings of the autoencoder/transformer to aim for a loss around 0.35 when processing quads.\n\n\n\n\n\nThis modification will allow us to process quads in our 3D models.\nAchieving a loss around 0.35 will improve the quality of our model transformations.\n\n\n\n\n\nModifying the existing code could introduce new bugs or issues.\nIt might be challenging to achieve the desired loss.\n\n\n\n\nAn alternative approach could be to convert quads into triangles before processing them with the autoencoder/transformer. However, this might result in loss of information or quality.\n\n\n\nThis modification might not be necessary if we are dealing with 3D models that do not contain quads.\n\n\n\nThe V-Sekai development team will handle the modification of the autoencoder/transformer and the optimization of the loss.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - The GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this proposal."
   },
   {
-    "objectID": "decisions/20240105-1-meter-128-quantize.html#metadata",
-    "href": "decisions/20240105-1-meter-128-quantize.html#metadata",
-    "title": "Proposed: 1 Meter Cubed 128 Quantized",
+    "objectID": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#the-context",
+    "href": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#the-context",
+    "title": "Proposed: Modify the Mesh Transformer for Quads",
     "section": "",
-    "text": "Status: Proposed \nDeciders: V-Sekai\nTags: V-Sekai"
+    "text": "We’re working on a project that involves using an autoencoder/transformer for 3D models. The current setup does not have a setting for quads, which is a requirement for our project."
   },
   {
-    "objectID": "decisions/20240105-1-meter-128-quantize.html#the-backdrop",
-    "href": "decisions/20240105-1-meter-128-quantize.html#the-backdrop",
-    "title": "Proposed: 1 Meter Cubed 128 Quantized",
+    "objectID": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#the-problem-statement",
+    "href": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#the-problem-statement",
+    "title": "Proposed: Modify the Mesh Transformer for Quads",
     "section": "",
-    "text": "MeshGPT’s “1 Meter Cubed 128 Quantized” format has emerged as a potential method to achieve standardized precision within virtual reality (VR) content creation, centring around polygonal modeling rather than voxel methods."
+    "text": "The challenge is to modify the autoencoder/transformer to include a setting for quads and achieve a loss around 0.35."
   },
   {
-    "objectID": "decisions/20240105-1-meter-128-quantize.html#the-challenge",
-    "href": "decisions/20240105-1-meter-128-quantize.html#the-challenge",
-    "title": "Proposed: 1 Meter Cubed 128 Quantized",
+    "objectID": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Modify the Mesh Transformer for Quads",
     "section": "",
-    "text": "The key objective is to harness the potential of the “1 Meter Cubed 128 Quantized” format to enhance procedural generation processes within VR development."
+    "text": "Modify the Autoencoder/Transformer: Update the existing code to include a quads=True parameter in the autoencoder/transformer.\nTest the Modification: Run tests to ensure that the modification works as expected and doesn’t break existing functionality.\nOptimize the Loss: Adjust the parameters and settings of the autoencoder/transformer to aim for a loss around 0.35 when processing quads."
   },
   {
-    "objectID": "decisions/20240105-1-meter-128-quantize.html#the-strategy",
-    "href": "decisions/20240105-1-meter-128-quantize.html#the-strategy",
-    "title": "Proposed: 1 Meter Cubed 128 Quantized",
+    "objectID": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#the-benefits",
+    "href": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#the-benefits",
+    "title": "Proposed: Modify the Mesh Transformer for Quads",
     "section": "",
-    "text": "Develop a comprehensive framework for environment generation that leverages the strengths of the polygonal quantized format.\nIntegrate adaptive algorithms tailored for this format to ensure dynamic responsiveness in VR spaces.\nEmbrace modular design paradigms that align with polygonal modeling to expedite the construction of VR environments."
+    "text": "This modification will allow us to process quads in our 3D models.\nAchieving a loss around 0.35 will improve the quality of our model transformations."
   },
   {
-    "objectID": "decisions/20240105-1-meter-128-quantize.html#the-upside",
-    "href": "decisions/20240105-1-meter-128-quantize.html#the-upside",
-    "title": "Proposed: 1 Meter Cubed 128 Quantized",
+    "objectID": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#the-downsides",
+    "href": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#the-downsides",
+    "title": "Proposed: Modify the Mesh Transformer for Quads",
     "section": "",
-    "text": "Fosters a more intuitive AI-creator collaboration using a polygonal format conducive to AI tools.\nLowers barriers to entry for creators, leading to increased efficiency and innovation.\nStreamlines procedural generation to operate with enhanced speed and reduced resource consumption.\nProvides a scalable and flexible model to cater to diverse design requirements in VR environments."
+    "text": "Modifying the existing code could introduce new bugs or issues.\nIt might be challenging to achieve the desired loss."
   },
   {
-    "objectID": "decisions/20240105-1-meter-128-quantize.html#the-downside",
-    "href": "decisions/20240105-1-meter-128-quantize.html#the-downside",
-    "title": "Proposed: 1 Meter Cubed 128 Quantized",
+    "objectID": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#the-road-not-taken",
+    "href": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#the-road-not-taken",
+    "title": "Proposed: Modify the Mesh Transformer for Quads",
     "section": "",
-    "text": "Requires considerable investment in research and development for effective technique integration.\nMay present a learning curve for developers not familiar with non-voxel formats."
+    "text": "An alternative approach could be to convert quads into triangles before processing them with the autoencoder/transformer. However, this might result in loss of information or quality."
   },
   {
-    "objectID": "decisions/20240105-1-meter-128-quantize.html#the-road-not-taken",
-    "href": "decisions/20240105-1-meter-128-quantize.html#the-road-not-taken",
-    "title": "Proposed: 1 Meter Cubed 128 Quantized",
+    "objectID": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#the-infrequent-use-case",
+    "href": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#the-infrequent-use-case",
+    "title": "Proposed: Modify the Mesh Transformer for Quads",
     "section": "",
-    "text": "Dependence on traditional voxel-based procedural generation technologies could be left behind in favor of the enhanced capabilities offered by the polygonal quantized format."
+    "text": "This modification might not be necessary if we are dealing with 3D models that do not contain quads."
   },
   {
-    "objectID": "decisions/20240105-1-meter-128-quantize.html#the-infrequent-use-case",
-    "href": "decisions/20240105-1-meter-128-quantize.html#the-infrequent-use-case",
-    "title": "Proposed: 1 Meter Cubed 128 Quantized",
+    "objectID": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#in-core-and-done-by-us",
+    "href": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#in-core-and-done-by-us",
+    "title": "Proposed: Modify the Mesh Transformer for Quads",
     "section": "",
-    "text": "Specialized VR environments may demand generation methods that extend beyond the standard capacities of the “1 Meter Cubed 128 Quantized” format."
+    "text": "The V-Sekai development team will handle the modification of the autoencoder/transformer and the optimization of the loss."
   },
   {
-    "objectID": "decisions/20240105-1-meter-128-quantize.html#in-core-and-done-by-us",
-    "href": "decisions/20240105-1-meter-128-quantize.html#in-core-and-done-by-us",
-    "title": "Proposed: 1 Meter Cubed 128 Quantized",
+    "objectID": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#status",
+    "href": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#status",
+    "title": "Proposed: Modify the Mesh Transformer for Quads",
     "section": "",
-    "text": "The enhancement of procedural generation via the adoption of the 1 Meter Cubed 128 Quantized polygonal format is an initiative headed by the V-Sekai team."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20240105-1-meter-128-quantize.html#further-reading",
-    "href": "decisions/20240105-1-meter-128-quantize.html#further-reading",
-    "title": "Proposed: 1 Meter Cubed 128 Quantized",
+    "objectID": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#decision-makers",
+    "href": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#decision-makers",
+    "title": "Proposed: Modify the Mesh Transformer for Quads",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nShadows of Doubt on Steam - A showcase of the advancements made possible through procedural generation in gaming.\n\nAssisted by AI Aria."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20240511-review-80-vr.html",
-    "href": "decisions/20240511-review-80-vr.html",
-    "title": "Rejected: VR Game with 80 Players and One World Server",
+    "objectID": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#tags",
+    "href": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#tags",
+    "title": "Proposed: Modify the Mesh Transformer for Quads",
     "section": "",
-    "text": "We aim to create a virtual reality (VR) game that can support eighty players simultaneously using a single world server.\n\n\n\nThe challenge lies in managing the load of player simulations, world server, and game state delivery.\nWe update the state of PLAYER_COUNT vsync times on a TBD CPU bare metal machine.\nIt takes 30ms to update the database on the prototype on VSK_godot/modules/mvsqlite/demo returning the list of all changed states.\nWe are going with the grid approach. Our world is a 1km by 1km area and each grid cell is 100m squared.\nA 1x1 grid of 100m squared requires 1 server.\nOur database is SQLite FoundationDB.\nThe game state delivery process involves the world server generating a stream of data containing the states of all players. This data is then sent to the client-side for rendering and interaction.\nThis list can then be used to generate the TBD gigabit/sec stream of packets that is sent from the world server.\nPlease note that the limiting factor here is due to the lack of multicast support over the internet.\n\n\n\n\nSupports a moderate number of players simultaneously\nProvides a rich, immersive gaming experience\nSimplified infrastructure with only one world server\n\n\n\n\n\nRequires significant resources and infrastructure\nBandwidth requirements may be high for some players\nLack of multicast support over the internet could limit game state delivery\n\n\n\n\nAn alternative would be to increase the number of players or world servers, but this would require more resources and infrastructure.\n\n\n\nIn cases where player traffic is consistently low, the infrastructure may be underutilized.\n\n\n\nThe proposed stress testing will be conducted by the V-Sekai development team.\n\n\n\nStatus: Rejected \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\ncreating-a-first-person-shooter-that-scales-to-millions-of-players\n\nAI assistant Aria assisted with this article."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20240511-review-80-vr.html#the-context",
-    "href": "decisions/20240511-review-80-vr.html#the-context",
-    "title": "Rejected: VR Game with 80 Players and One World Server",
+    "objectID": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#further-reading",
+    "href": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#further-reading",
+    "title": "Proposed: Modify the Mesh Transformer for Quads",
     "section": "",
-    "text": "We aim to create a virtual reality (VR) game that can support eighty players simultaneously using a single world server."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - The GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this proposal."
   },
   {
-    "objectID": "decisions/20240511-review-80-vr.html#the-problem-statement",
-    "href": "decisions/20240511-review-80-vr.html#the-problem-statement",
-    "title": "Rejected: VR Game with 80 Players and One World Server",
+    "objectID": "decisions/20210811-disconnected-ipfs.html",
+    "href": "decisions/20210811-disconnected-ipfs.html",
+    "title": "Proposed: Godot Engine implementation of disconnected IPFS",
     "section": "",
-    "text": "The challenge lies in managing the load of player simulations, world server, and game state delivery.\nWe update the state of PLAYER_COUNT vsync times on a TBD CPU bare metal machine.\nIt takes 30ms to update the database on the prototype on VSK_godot/modules/mvsqlite/demo returning the list of all changed states.\nWe are going with the grid approach. Our world is a 1km by 1km area and each grid cell is 100m squared.\nA 1x1 grid of 100m squared requires 1 server.\nOur database is SQLite FoundationDB.\nThe game state delivery process involves the world server generating a stream of data containing the states of all players. This data is then sent to the client-side for rendering and interaction.\nThis list can then be used to generate the TBD gigabit/sec stream of packets that is sent from the world server.\nPlease note that the limiting factor here is due to the lack of multicast support over the internet."
+    "text": "Proposed: Godot Engine implementation of disconnected IPFS\n\nContext and Problem Statement\nDisconnect IPFS from the internet\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nDisconnect IPFS so it can be standalone packages.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nImplement https://github.com/skogard/nebulus as a c++ library.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nMay be able to be done by others.\n\n\nPositive Consequences\n\nsend a offline package\n\n\n\nNegative Consequences\n\nin javascript\n\n\n\nIs there a reason why this should be core and done by us?\n\nMight be an extension\n\n\n\nReferences\n\nhttps://github.com/skogard/nebulus\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240511-review-80-vr.html#the-benefits",
-    "href": "decisions/20240511-review-80-vr.html#the-benefits",
-    "title": "Rejected: VR Game with 80 Players and One World Server",
+    "objectID": "decisions/20240522-shader-motion-to-bvh.html",
+    "href": "decisions/20240522-shader-motion-to-bvh.html",
+    "title": "Draft: shadermotion to BVH",
     "section": "",
-    "text": "Supports a moderate number of players simultaneously\nProvides a rich, immersive gaming experience\nSimplified infrastructure with only one world server"
+    "text": "Lacking characters motions to work with.\nTransferring motions across platforms via video.\n\n\n\n#shadermotion allows us to transfer motion for other VR platforms into a standard motion format.\n\n\n\nShaderMotion: “OBS” etc. motion captured video from VRChat.\n\n\n\nFloss.mp4\n\n\nExample: Floss.mp4\n(repo: lox9973/ShaderMotion)\nShaderMotion =&gt; BVH\n\ninput: mpeg4\noutput: bvh\n\n\n\n\n.mp4 #shadermotion video\nshadermotion-to-bvh by guillefix\n\ndownload shadermotion-to-bvh.zip from XXX github repo releases\nunpack to a folder\n\n\n\n\n\nRun shadermotion2.exe --video \"yourvideo.mp4\"\nKEEP THE WINDOW FOCUSED\nOnce completed, look for yourvideo.bvh\n\n\n\nThanks to humbletim for being the scribe\nThanks to lyuma for being test pilot flying these steps\n\n\n\n\n\nAble to have motion for characters\n\n\n\n\n\nMany steps\n\n\n\n\n#shadermotion is a novel solution to capturing motion from VRChat.\n\n\n\nThis document describes how to integrate #shadermotion with us.\n\n\n\n\nhttps://chibifire.com/shader_motion/\nhttps://hackmd.io/EmOAt375S8KFqaNdPDJCXQ\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240511-review-80-vr.html#the-downsides",
-    "href": "decisions/20240511-review-80-vr.html#the-downsides",
-    "title": "Rejected: VR Game with 80 Players and One World Server",
+    "objectID": "decisions/20240522-shader-motion-to-bvh.html#context-and-problem-statement",
+    "href": "decisions/20240522-shader-motion-to-bvh.html#context-and-problem-statement",
+    "title": "Draft: shadermotion to BVH",
     "section": "",
-    "text": "Requires significant resources and infrastructure\nBandwidth requirements may be high for some players\nLack of multicast support over the internet could limit game state delivery"
+    "text": "Lacking characters motions to work with.\nTransferring motions across platforms via video."
   },
   {
-    "objectID": "decisions/20240511-review-80-vr.html#the-road-not-taken",
-    "href": "decisions/20240511-review-80-vr.html#the-road-not-taken",
-    "title": "Rejected: VR Game with 80 Players and One World Server",
+    "objectID": "decisions/20240522-shader-motion-to-bvh.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20240522-shader-motion-to-bvh.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Draft: shadermotion to BVH",
     "section": "",
-    "text": "An alternative would be to increase the number of players or world servers, but this would require more resources and infrastructure."
+    "text": "#shadermotion allows us to transfer motion for other VR platforms into a standard motion format."
   },
   {
-    "objectID": "decisions/20240511-review-80-vr.html#the-infrequent-use-case",
-    "href": "decisions/20240511-review-80-vr.html#the-infrequent-use-case",
-    "title": "Rejected: VR Game with 80 Players and One World Server",
+    "objectID": "decisions/20240522-shader-motion-to-bvh.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-andor-diagrams",
+    "href": "decisions/20240522-shader-motion-to-bvh.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-andor-diagrams",
+    "title": "Draft: shadermotion to BVH",
     "section": "",
-    "text": "In cases where player traffic is consistently low, the infrastructure may be underutilized."
+    "text": "ShaderMotion: “OBS” etc. motion captured video from VRChat.\n\n\n\nFloss.mp4\n\n\nExample: Floss.mp4\n(repo: lox9973/ShaderMotion)\nShaderMotion =&gt; BVH\n\ninput: mpeg4\noutput: bvh\n\n\n\n\n.mp4 #shadermotion video\nshadermotion-to-bvh by guillefix\n\ndownload shadermotion-to-bvh.zip from XXX github repo releases\nunpack to a folder\n\n\n\n\n\nRun shadermotion2.exe --video \"yourvideo.mp4\"\nKEEP THE WINDOW FOCUSED\nOnce completed, look for yourvideo.bvh\n\n\n\nThanks to humbletim for being the scribe\nThanks to lyuma for being test pilot flying these steps"
   },
   {
-    "objectID": "decisions/20240511-review-80-vr.html#in-core-and-done-by-us",
-    "href": "decisions/20240511-review-80-vr.html#in-core-and-done-by-us",
-    "title": "Rejected: VR Game with 80 Players and One World Server",
+    "objectID": "decisions/20240522-shader-motion-to-bvh.html#positive-consequences",
+    "href": "decisions/20240522-shader-motion-to-bvh.html#positive-consequences",
+    "title": "Draft: shadermotion to BVH",
     "section": "",
-    "text": "The proposed stress testing will be conducted by the V-Sekai development team."
+    "text": "Able to have motion for characters"
   },
   {
-    "objectID": "decisions/20240511-review-80-vr.html#status",
-    "href": "decisions/20240511-review-80-vr.html#status",
-    "title": "Rejected: VR Game with 80 Players and One World Server",
+    "objectID": "decisions/20240522-shader-motion-to-bvh.html#negative-consequences",
+    "href": "decisions/20240522-shader-motion-to-bvh.html#negative-consequences",
+    "title": "Draft: shadermotion to BVH",
     "section": "",
-    "text": "Status: Rejected"
+    "text": "Many steps"
   },
   {
-    "objectID": "decisions/20240511-review-80-vr.html#decision-makers",
-    "href": "decisions/20240511-review-80-vr.html#decision-makers",
-    "title": "Rejected: VR Game with 80 Players and One World Server",
+    "objectID": "decisions/20240522-shader-motion-to-bvh.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20240522-shader-motion-to-bvh.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Draft: shadermotion to BVH",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "#shadermotion is a novel solution to capturing motion from VRChat."
   },
   {
-    "objectID": "decisions/20240511-review-80-vr.html#tags",
-    "href": "decisions/20240511-review-80-vr.html#tags",
-    "title": "Rejected: VR Game with 80 Players and One World Server",
+    "objectID": "decisions/20240522-shader-motion-to-bvh.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20240522-shader-motion-to-bvh.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Draft: shadermotion to BVH",
     "section": "",
-    "text": "V-Sekai"
+    "text": "This document describes how to integrate #shadermotion with us."
   },
   {
-    "objectID": "decisions/20240511-review-80-vr.html#further-reading",
-    "href": "decisions/20240511-review-80-vr.html#further-reading",
-    "title": "Rejected: VR Game with 80 Players and One World Server",
+    "objectID": "decisions/20240522-shader-motion-to-bvh.html#references",
+    "href": "decisions/20240522-shader-motion-to-bvh.html#references",
+    "title": "Draft: shadermotion to BVH",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\ncreating-a-first-person-shooter-that-scales-to-millions-of-players\n\nAI assistant Aria assisted with this article."
+    "text": "https://chibifire.com/shader_motion/\nhttps://hackmd.io/EmOAt375S8KFqaNdPDJCXQ"
   },
   {
-    "objectID": "decisions/20230415-rgbaf-to-store-integers.html",
-    "href": "decisions/20230415-rgbaf-to-store-integers.html",
-    "title": "Proposed: Use godot rgbaf textures to store integers",
+    "objectID": "decisions/20240522-shader-motion-to-bvh.html#derivative-license",
+    "href": "decisions/20240522-shader-motion-to-bvh.html#derivative-license",
+    "title": "Draft: shadermotion to BVH",
     "section": "",
-    "text": "Proposed: Use godot rgbaf textures to store integers\n\nMetadata\n\nStatus: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nContext and Problem Statement\nUse godot rgbaf textures to store integer.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nGodot Shader to extract the raw 16-bit integer in a FORMAT_RGBAH texture by Lyuma.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\n\nshader_type spatial;\nrender_mode unshaded;\nuniform usampler2D data_tex;\n\n/*\nUse with the following GDScript code:\n    var data_img = Image.new()\n    var data := PoolByteArray()\n    var indexin = 0x8400\n    data.append(indexin&0xff)\n    data.append((indexin&gt;&gt;8)&0xff)\n    data_img.create_from_data(1, 1, false, Image.FORMAT_RH, data)\n    var data_tex = ImageTexture.new()\n    data_tex.create_from_image(data_img, 0)\n    self.get_surface_material(0).set_shader_param(\"data_tex\", data_tex)\n*/\n\n// Extract the raw 16-bit integer assigned in a GL_RGBA16F or similar texture format\n// (in Godot, Image.FORMAT_RGBAH or Image.FORMAT_RH)\n\n// vectorized ?:\n// In GLSL, you are supposed to do this using a mix(uvec4, uvec4, bvec4)\n// However, in Godot, they forgot this overload existed, so we reimplement it.\n\nuvec4 godot_hack_mix(uvec4 a, uvec4 b, bvec4 c) {\n    return uvec4(c.x ? b.x : a.x, c.y ? b.y : a.y, c.z ? b.z : a.z, c.w ? b.w : a.w);\n}\n\nvoid fragment() {\n    // Fetch half precision texture using usampler2D.\n    // For some reason, it first converts to 32-bit float (but losslessly????)\n    // and so we have to convert the 32-bit float back to 16-bits.\n    uvec4 data = texelFetch(data_tex, ivec2(0,0), 0);\n\n    // Calculate bit shifted exponent\n    uvec4 exps = godot_hack_mix(\n        // Adjust floating point from 8-bit in float32 (127 bias) to 5-bit in half (15 bias)\n        uvec4((uvec4((ivec4((data & uvec4(0x7F800000)) &gt;&gt; uvec4(23)) - ivec4(127)) + ivec4(15)) & uvec4(0x1F)) &lt;&lt; uvec4(10)),\n        // Inf and NaN will remain Inf and Nan (maximum half exponent = 31)\n        uvec4(ivec4(31 &lt;&lt; 10)),\n        // Check for maximum float32 exponent = 255\n        equal((data) & uvec4(0x7F800000), uvec4(0x7F800000)));\n\n    // calculate final data.\n    data = godot_hack_mix(\n        // mantissa | exponent | signbit\n        ((data & uvec4(0x007FFFFF)) &gt;&gt; uvec4(13)) | exps | (((data &gt;&gt; uvec4(31)) & uvec4(1)) &lt;&lt; uvec4(15)),\n        // Denormalized case: exponent is all over the place, so instead we add the smallest non-denormalized half, then extract the mantessa bits.\n        // Finally, or the sign bit (and exponent = 0)\n        (((floatBitsToUint(uintBitsToFloat(data & uvec4(0x7FFFFFFF)) + 1.0/16384.0) & uvec4(0x007FFFFF)) &gt;&gt; uvec4(13))) | (((data &gt;&gt; uvec4(31)) & uvec4(1)) &lt;&lt; uvec4(15)),\n        // Denormalized case can be detected with half exponent &lt;= -15.\n        lessThanEqual((data) & uvec4(0x7F800000), uvec4(0x38000000)));\n\n    // Parse out individual bits if needed\n    ivec2 datar = ivec2((uvec2(data.r) &gt;&gt; uvec2(0,8)) & uvec2(0xFF));\n    ivec2 datag = ivec2((uvec2(data.g) &gt;&gt; uvec2(0,8)) & uvec2(0xFF));\n    ivec2 datab = ivec2((uvec2(data.b) &gt;&gt; uvec2(0,8)) & uvec2(0xFF));\n    ivec2 dataa = ivec2((uvec2(data.a) &gt;&gt; uvec2(0,8)) & uvec2(0xFF));\n\n    // Example code: check for precise 16-bit value that matches GDScript.\n    ALBEDO = vec3(0,0,0);\n    if (data.r == uint(0xFFFF)) {\n        ALBEDO = vec3(1,1,1);\n    }\n}\n\n\nPositive Consequences\nWe are able to use V-Sekai easier.\n\n\nNegative Consequences\nWe cannot get other features in.\n\n\nOption graveyard\nUse 8 bit colors.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nThis is a few lines of script.\n\n\nIs there a reason why this should be core and done by us?\nWanted to record this.\n\n\nReferences\n\nV-Sekai"
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230920-godot-project-search.html",
-    "href": "decisions/20230920-godot-project-search.html",
-    "title": "Proposed: Use embedding search with Godot Engine projects",
+    "objectID": "decisions/20240630-use-motion-transformers-for-prediction.html",
+    "href": "decisions/20240630-use-motion-transformers-for-prediction.html",
+    "title": "Proposed: Use motion transformers for motion prediction",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nThe Godot Engine is a powerful tool for creating games and other interactive content. However, finding specific pieces of code or resources within a large project can be challenging. This is where an embedding search engine like SeaGOAT can come in handy.\n\n\n\nThe challenge lies in integrating the SeaGOAT search engine with Godot Engine projects. Specifically, we need to ensure that it can effectively index and search .tscn, .tres, .gd, .cpp, .h, and .xml files, which are commonly used in Godot projects.\n\n\n\nTo use SeaGOAT with Godot Engine projects, you’ll need to add support for .tscn, .tres, .gd, .cpp, .h, and .xml files. You can do this by modifying the common.py file in the SeaGOAT repository. Specifically, you’ll want to add these extensions to the FILE_EXTENSIONS list:\nFILE_EXTENSIONS = [\n    # existing extensions...\n    \".tscn\",\n    \".tres\",\n    \".gd\",\n    \".cpp\",\n    \".h\",\n    \".xml\"\n]\nOnce you’ve done this, SeaGOAT should be able to index and search your Godot Engine projects.\n\n\n\nBy integrating SeaGOAT with your Godot Engine projects, you’ll be able to quickly and easily find specific pieces of code or resources. This can greatly speed up your development process and make it easier to manage large projects.\n\n\n\nThe downside is that this requires modifying the SeaGOAT source code, which may not be ideal if you’re not comfortable with Python or if you want to keep your SeaGOAT installation up-to-date with the official repository.\n\n\n\nAn alternative approach would be to use a different search engine that already supports .tscn, .tres, .gd, .cpp, .h, and .xml files. However, this may not provide the same level of functionality as SeaGOAT.\n\n\n\nThis strategy is most useful for large Godot Engine projects where finding specific pieces of code or resources can be challenging. For smaller projects, the built-in search functionality in Godot may be sufficient.\n\n\n\nThis modification would need to be done by us, as it involves changing the SeaGOAT source code. It’s not clear whether this change would be accepted into the core SeaGOAT project.\n\n\n\n\nV-Sekai\nSeaGOAT\nThis article is assisted by AI."
+    "text": "In virtual reality and gaming, predicting human motion is a critical aspect. It helps in creating more realistic characters and enhancing user interaction. Currently, we use traditional methods that are not very efficient and lack accuracy.\n\n\n\nThe main problem we are trying to solve is to predict the next tokens for motion. This will help us in creating more realistic movements for our characters in the game. Additionally, it can be used for generating new animations and for networking compression.\n\n\n\nWe propose to use MotionGPT, a transformer-based model that treats human motion as a foreign language. It learns the ‘grammar’ of human motion from data and uses it to generate new motions.\n# Pseudo-code for MotionGPT\ndef MotionGPT(data):\n    model = TransformerModel()\n    model.train(data)\n    return model.generate_motion()\n\n\n\n\nImproved accuracy in motion prediction.\nMore realistic character movements.\nEnhanced user experience.\nGeneration of new animations.\nNetworking compression.\n\n\n\n\n\nRequires large amounts of data for training.\nMight be computationally expensive.\n\n\n\n\nWe could have continued using traditional methods for motion prediction but they lack the efficiency and accuracy provided by transformer models.\n\n\n\nThis proposal might not be beneficial for games that do not require realistic human motion or where the computational resources are limited.\n\n\n\nThis proposal is core to our project as it directly impacts the realism and user experience of our game. It will be implemented by our development team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nMotionGPT: Human Motion\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20230920-godot-project-search.html#metadata",
-    "href": "decisions/20230920-godot-project-search.html#metadata",
-    "title": "Proposed: Use embedding search with Godot Engine projects",
+    "objectID": "decisions/20240630-use-motion-transformers-for-prediction.html#motiongpt-human-motion-as-foreign-language",
+    "href": "decisions/20240630-use-motion-transformers-for-prediction.html#motiongpt-human-motion-as-foreign-language",
+    "title": "Proposed: Use motion transformers for motion prediction",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai"
+    "text": "In virtual reality and gaming, predicting human motion is a critical aspect. It helps in creating more realistic characters and enhancing user interaction. Currently, we use traditional methods that are not very efficient and lack accuracy.\n\n\n\nThe main problem we are trying to solve is to predict the next tokens for motion. This will help us in creating more realistic movements for our characters in the game. Additionally, it can be used for generating new animations and for networking compression.\n\n\n\nWe propose to use MotionGPT, a transformer-based model that treats human motion as a foreign language. It learns the ‘grammar’ of human motion from data and uses it to generate new motions.\n# Pseudo-code for MotionGPT\ndef MotionGPT(data):\n    model = TransformerModel()\n    model.train(data)\n    return model.generate_motion()\n\n\n\n\nImproved accuracy in motion prediction.\nMore realistic character movements.\nEnhanced user experience.\nGeneration of new animations.\nNetworking compression.\n\n\n\n\n\nRequires large amounts of data for training.\nMight be computationally expensive.\n\n\n\n\nWe could have continued using traditional methods for motion prediction but they lack the efficiency and accuracy provided by transformer models.\n\n\n\nThis proposal might not be beneficial for games that do not require realistic human motion or where the computational resources are limited.\n\n\n\nThis proposal is core to our project as it directly impacts the realism and user experience of our game. It will be implemented by our development team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nMotionGPT: Human Motion\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20230920-godot-project-search.html#the-backdrop",
-    "href": "decisions/20230920-godot-project-search.html#the-backdrop",
-    "title": "Proposed: Use embedding search with Godot Engine projects",
+    "objectID": "decisions/20211031-openvr-for-godot-engine.html",
+    "href": "decisions/20211031-openvr-for-godot-engine.html",
+    "title": "Rejected: OpenVR for Godot Engine",
     "section": "",
-    "text": "The Godot Engine is a powerful tool for creating games and other interactive content. However, finding specific pieces of code or resources within a large project can be challenging. This is where an embedding search engine like SeaGOAT can come in handy."
+    "text": "Rejected: OpenVR for Godot Engine\n\nContext and Problem Statement\nOpenVR for Godot Engine\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nOpenVR for Godot Engine\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n\nCompile gdextension\nCompile openvr\nRun\nModify game code\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNo.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nThis is core.\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230920-godot-project-search.html#the-challenge",
-    "href": "decisions/20230920-godot-project-search.html#the-challenge",
-    "title": "Proposed: Use embedding search with Godot Engine projects",
+    "objectID": "decisions/20230125-cover-80-95-percent-of-the-userbase.html",
+    "href": "decisions/20230125-cover-80-95-percent-of-the-userbase.html",
+    "title": "Proposed: Cover 80% to 95% of the player base.",
     "section": "",
-    "text": "The challenge lies in integrating the SeaGOAT search engine with Godot Engine projects. Specifically, we need to ensure that it can effectively index and search .tscn, .tres, .gd, .cpp, .h, and .xml files, which are commonly used in Godot projects."
+    "text": "Proposed: Cover 80% to 95% of the player base.\n\nMetadata\n\nStatus: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nContext and Problem Statement\nPeople want to use V-Sekai, we need to provide coverage of their electronic equipment.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nCover 80% to 95% percent of the userbase’s equipment, so people can play V-Sekai.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nProvide coverage of:\n\nDesktop mode\nMeta Quest 2\nValve Index\nHTC Vive\n\n\n\nPositive Consequences\nWe are able to use V-Sekai easier.\n\n\nNegative Consequences\nWe cannot get other features in.\n\n\nOption graveyard\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nKnowing what to do is hard.\n\n\nIs there a reason why this should be core and done by us?\nUsability is a core feature.\n\n\nReferences\n\nV-Sekai"
   },
   {
-    "objectID": "decisions/20230920-godot-project-search.html#the-strategy",
-    "href": "decisions/20230920-godot-project-search.html#the-strategy",
-    "title": "Proposed: Use embedding search with Godot Engine projects",
+    "objectID": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html",
+    "href": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html",
+    "title": "Proposed: Allow Godot Asset Library browser to use alternative sources",
     "section": "",
-    "text": "To use SeaGOAT with Godot Engine projects, you’ll need to add support for .tscn, .tres, .gd, .cpp, .h, and .xml files. You can do this by modifying the common.py file in the SeaGOAT repository. Specifically, you’ll want to add these extensions to the FILE_EXTENSIONS list:\nFILE_EXTENSIONS = [\n    # existing extensions...\n    \".tscn\",\n    \".tres\",\n    \".gd\",\n    \".cpp\",\n    \".h\",\n    \".xml\"\n]\nOnce you’ve done this, SeaGOAT should be able to index and search your Godot Engine projects."
+    "text": "Status: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nGodot Engine has a great asset library browser.\nWhy can’t we reuse it for alternative Godot engine asset libraries?\n\n\n\nAdd an alternative server and document the current api as an openapi schema.\n\n\n\n\nOpenapi schema for the official asset library api.\nElixir server implementation\nPatch to Godot Engine to add arbitrary asset libraries\n\n\n\n\n\nMore freedom.\nXananax said he’ll use it. Xanax’s games are made 100% of addons with assets and glue code being the game.\n\n\n\n\n\nDifferent libraries\n\n\n\n\n\nOption: \nRejection Reason: \n\n\n\n\nCould be a few lines of script. Unsure of scope. The server can be a lot too.\n\n\n\nNot so core, but I can do it.\n\n\n\n\nhttps://github.com/godotengine/godot-asset-library/blob/master/API.md\n\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230920-godot-project-search.html#the-upside",
-    "href": "decisions/20230920-godot-project-search.html#the-upside",
-    "title": "Proposed: Use embedding search with Godot Engine projects",
+    "objectID": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html#context-and-problem-statement",
+    "href": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html#context-and-problem-statement",
+    "title": "Proposed: Allow Godot Asset Library browser to use alternative sources",
     "section": "",
-    "text": "By integrating SeaGOAT with your Godot Engine projects, you’ll be able to quickly and easily find specific pieces of code or resources. This can greatly speed up your development process and make it easier to manage large projects."
+    "text": "Godot Engine has a great asset library browser.\nWhy can’t we reuse it for alternative Godot engine asset libraries?"
   },
   {
-    "objectID": "decisions/20230920-godot-project-search.html#the-downside",
-    "href": "decisions/20230920-godot-project-search.html#the-downside",
-    "title": "Proposed: Use embedding search with Godot Engine projects",
+    "objectID": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: Allow Godot Asset Library browser to use alternative sources",
     "section": "",
-    "text": "The downside is that this requires modifying the SeaGOAT source code, which may not be ideal if you’re not comfortable with Python or if you want to keep your SeaGOAT installation up-to-date with the official repository."
+    "text": "Add an alternative server and document the current api as an openapi schema."
   },
   {
-    "objectID": "decisions/20230920-godot-project-search.html#the-road-not-taken",
-    "href": "decisions/20230920-godot-project-search.html#the-road-not-taken",
-    "title": "Proposed: Use embedding search with Godot Engine projects",
+    "objectID": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Allow Godot Asset Library browser to use alternative sources",
     "section": "",
-    "text": "An alternative approach would be to use a different search engine that already supports .tscn, .tres, .gd, .cpp, .h, and .xml files. However, this may not provide the same level of functionality as SeaGOAT."
+    "text": "Openapi schema for the official asset library api.\nElixir server implementation\nPatch to Godot Engine to add arbitrary asset libraries"
   },
   {
-    "objectID": "decisions/20230920-godot-project-search.html#the-infrequent-use-case",
-    "href": "decisions/20230920-godot-project-search.html#the-infrequent-use-case",
-    "title": "Proposed: Use embedding search with Godot Engine projects",
+    "objectID": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html#positive-consequences",
+    "href": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html#positive-consequences",
+    "title": "Proposed: Allow Godot Asset Library browser to use alternative sources",
     "section": "",
-    "text": "This strategy is most useful for large Godot Engine projects where finding specific pieces of code or resources can be challenging. For smaller projects, the built-in search functionality in Godot may be sufficient."
+    "text": "More freedom.\nXananax said he’ll use it. Xanax’s games are made 100% of addons with assets and glue code being the game."
   },
   {
-    "objectID": "decisions/20230920-godot-project-search.html#in-core-and-done-by-us",
-    "href": "decisions/20230920-godot-project-search.html#in-core-and-done-by-us",
-    "title": "Proposed: Use embedding search with Godot Engine projects",
+    "objectID": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html#negative-consequences",
+    "href": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html#negative-consequences",
+    "title": "Proposed: Allow Godot Asset Library browser to use alternative sources",
     "section": "",
-    "text": "This modification would need to be done by us, as it involves changing the SeaGOAT source code. It’s not clear whether this change would be accepted into the core SeaGOAT project."
+    "text": "Different libraries"
   },
   {
-    "objectID": "decisions/20230920-godot-project-search.html#further-reading",
-    "href": "decisions/20230920-godot-project-search.html#further-reading",
-    "title": "Proposed: Use embedding search with Godot Engine projects",
+    "objectID": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html#option-graveyard",
+    "href": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html#option-graveyard",
+    "title": "Proposed: Allow Godot Asset Library browser to use alternative sources",
     "section": "",
-    "text": "V-Sekai\nSeaGOAT\nThis article is assisted by AI."
+    "text": "Option: \nRejection Reason:"
   },
   {
-    "objectID": "decisions/20211031-use-bpr-to-rank-skeleton-bone-names.html",
-    "href": "decisions/20211031-use-bpr-to-rank-skeleton-bone-names.html",
-    "title": "Proposed: Rank skeleton bone names by using BPR",
+    "objectID": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Allow Godot Asset Library browser to use alternative sources",
     "section": "",
-    "text": "Proposed: Rank skeleton bone names by using BPR\n\nStatus: proposed\n\n\nContext and Problem Statement\nImprove automatic bone selection\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nUse brp to rank bones while storing in duckdb.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nUse duckdb and brp. Prototype concept then port to c++.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nTrying.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nI have the idea.\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Could be a few lines of script. Unsure of scope. The server can be a lot too."
   },
   {
-    "objectID": "decisions/20240416-previewer-upload-gltf-to-glb.html",
-    "href": "decisions/20240416-previewer-upload-gltf-to-glb.html",
-    "title": "Proposed: Implementing a 3D Previewer for GLTF with XMP Metadata",
+    "objectID": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Allow Godot Asset Library browser to use alternative sources",
     "section": "",
-    "text": "The current project involves the use of 3D models in GLTF format. These models also contain XMP metadata which needs to be previewed.\n\n\n\nThe challenge lies in creating a 3D previewer that handles GLTF files and their associated XMP metadata. The aim is to have one file per entry, making it easier to manage and organize the data.\n\n\n\nThe proposed solution involves loading a GLTF file and saving it as a GLB file. This process is lossless, meaning no data will be lost during the conversion. The GLB file will then preview the 3D model and its metadata.\nfunction convertToGLB(gltfFile) {\n    // Load the GLTF file\n    var gltf = loadGLTF(gltfFile);\n\n    // Convert the GLTF to GLB\n    var glb = gltf.toGLB();\n\n    // Save the GLB file\n    saveGLB(glb);\n}\n\n\n\n\nSimplifies the workflow by having only one file per entry.\nNo loss of data during the conversion from GLTF to GLB.\nMakes it easier to compress in Godot Engine’s workflow.\n\n\n\n\n\nRequires additional processing to convert GLTF files to GLB.\nMight increase the overall size of the project due to the conversion.\n\n\n\n\nAn alternative approach could be to keep the GLTF and XMP metadata separate and create a previewer that can handle multiple files. However, this would complicate the workflow and make it harder to manage the data.\n\n\n\nThis proposal might not be beneficial for projects that do not require a 3D previewer or do not use GLTF files.\n\n\n\nThe implementation of this proposal will be done by the V-Sekai development team.\n\n\n\nProposed\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis proposal was assisted by AI assistant Aria."
+    "text": "Not so core, but I can do it."
   },
   {
-    "objectID": "decisions/20240416-previewer-upload-gltf-to-glb.html#context",
-    "href": "decisions/20240416-previewer-upload-gltf-to-glb.html#context",
-    "title": "Proposed: Implementing a 3D Previewer for GLTF with XMP Metadata",
+    "objectID": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html#references",
+    "href": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html#references",
+    "title": "Proposed: Allow Godot Asset Library browser to use alternative sources",
     "section": "",
-    "text": "The current project involves the use of 3D models in GLTF format. These models also contain XMP metadata which needs to be previewed."
+    "text": "https://github.com/godotengine/godot-asset-library/blob/master/API.md"
   },
   {
-    "objectID": "decisions/20240416-previewer-upload-gltf-to-glb.html#problem-statement",
-    "href": "decisions/20240416-previewer-upload-gltf-to-glb.html#problem-statement",
-    "title": "Proposed: Implementing a 3D Previewer for GLTF with XMP Metadata",
+    "objectID": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html#derivative-license",
+    "href": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html#derivative-license",
+    "title": "Proposed: Allow Godot Asset Library browser to use alternative sources",
     "section": "",
-    "text": "The challenge lies in creating a 3D previewer that handles GLTF files and their associated XMP metadata. The aim is to have one file per entry, making it easier to manage and organize the data."
+    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240416-previewer-upload-gltf-to-glb.html#proposed-solution",
-    "href": "decisions/20240416-previewer-upload-gltf-to-glb.html#proposed-solution",
-    "title": "Proposed: Implementing a 3D Previewer for GLTF with XMP Metadata",
+    "objectID": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html",
+    "href": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html",
+    "title": "Proposed: Enhancing Avatar Expressiveness with AI-Generated Blend Shapes",
     "section": "",
-    "text": "The proposed solution involves loading a GLTF file and saving it as a GLB file. This process is lossless, meaning no data will be lost during the conversion. The GLB file will then preview the 3D model and its metadata.\nfunction convertToGLB(gltfFile) {\n    // Load the GLTF file\n    var gltf = loadGLTF(gltfFile);\n\n    // Convert the GLTF to GLB\n    var glb = gltf.toGLB();\n\n    // Save the GLB file\n    saveGLB(glb);\n}"
+    "text": "In the realm of virtual reality, expressiveness is paramount for a rich social experience. V-Sekai is dedicated to providing users with robust avatar customization options, particularly in the realm of facial expressions.\n\n\n\nThe current scope of facial expression customization in V-Sekai is limited. It lacks the depth necessary for users to craft avatars that can exhibit a comprehensive range of emotions, which detracts from the immersive experience and social interaction within the platform.\n\n\n\nTo be determined.\n\n\n\n\nEnhanced realism and emotional conveyance in avatars.\nGreater diversity in facial expressions enriches communication between users.\nSimplification of complex expression creation makes avatar personalization accessible to all skill levels.\n\n\n\n\n\nPotential performance impact due to real-time AI processing.\nThe requirement for ongoing dataset updates to improve and maintain AI model accuracy.\n\n\n\n\nAlternative options included manual blend shape sculpting by artists and community-driven expression templates, both of which were deemed to lack scalability and flexibility compared to an AI-based solution.\n\n\n\nFor users requiring highly specialized expressions seldom encountered in regular interactions, such as niche cultural facial gestures.\n\n\n\nThis initiative is core to V-Sekai’s mission of enhanced user interaction and must be developed in-house to ensure deep integration and alignment with existing systems.\n\n\n\nStatus: Proposed\n\n\n\n\n\nV-Sekai development team and community stakeholders.\n\n\n\n\n\nV-Sekai, Avatar Customization, AI, Facial Expressions\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nAssisted by Aria."
   },
   {
-    "objectID": "decisions/20240416-previewer-upload-gltf-to-glb.html#benefits",
-    "href": "decisions/20240416-previewer-upload-gltf-to-glb.html#benefits",
-    "title": "Proposed: Implementing a 3D Previewer for GLTF with XMP Metadata",
+    "objectID": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#the-context",
+    "href": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#the-context",
+    "title": "Proposed: Enhancing Avatar Expressiveness with AI-Generated Blend Shapes",
     "section": "",
-    "text": "Simplifies the workflow by having only one file per entry.\nNo loss of data during the conversion from GLTF to GLB.\nMakes it easier to compress in Godot Engine’s workflow."
+    "text": "In the realm of virtual reality, expressiveness is paramount for a rich social experience. V-Sekai is dedicated to providing users with robust avatar customization options, particularly in the realm of facial expressions."
   },
   {
-    "objectID": "decisions/20240416-previewer-upload-gltf-to-glb.html#downsides",
-    "href": "decisions/20240416-previewer-upload-gltf-to-glb.html#downsides",
-    "title": "Proposed: Implementing a 3D Previewer for GLTF with XMP Metadata",
+    "objectID": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#the-problem-statement",
+    "href": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#the-problem-statement",
+    "title": "Proposed: Enhancing Avatar Expressiveness with AI-Generated Blend Shapes",
     "section": "",
-    "text": "Requires additional processing to convert GLTF files to GLB.\nMight increase the overall size of the project due to the conversion."
+    "text": "The current scope of facial expression customization in V-Sekai is limited. It lacks the depth necessary for users to craft avatars that can exhibit a comprehensive range of emotions, which detracts from the immersive experience and social interaction within the platform."
   },
   {
-    "objectID": "decisions/20240416-previewer-upload-gltf-to-glb.html#the-road-not-taken",
-    "href": "decisions/20240416-previewer-upload-gltf-to-glb.html#the-road-not-taken",
-    "title": "Proposed: Implementing a 3D Previewer for GLTF with XMP Metadata",
+    "objectID": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Enhancing Avatar Expressiveness with AI-Generated Blend Shapes",
     "section": "",
-    "text": "An alternative approach could be to keep the GLTF and XMP metadata separate and create a previewer that can handle multiple files. However, this would complicate the workflow and make it harder to manage the data."
+    "text": "To be determined."
   },
   {
-    "objectID": "decisions/20240416-previewer-upload-gltf-to-glb.html#the-infrequent-use-case",
-    "href": "decisions/20240416-previewer-upload-gltf-to-glb.html#the-infrequent-use-case",
-    "title": "Proposed: Implementing a 3D Previewer for GLTF with XMP Metadata",
+    "objectID": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#the-benefits",
+    "href": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#the-benefits",
+    "title": "Proposed: Enhancing Avatar Expressiveness with AI-Generated Blend Shapes",
     "section": "",
-    "text": "This proposal might not be beneficial for projects that do not require a 3D previewer or do not use GLTF files."
+    "text": "Enhanced realism and emotional conveyance in avatars.\nGreater diversity in facial expressions enriches communication between users.\nSimplification of complex expression creation makes avatar personalization accessible to all skill levels."
   },
   {
-    "objectID": "decisions/20240416-previewer-upload-gltf-to-glb.html#in-core-and-done-by-us",
-    "href": "decisions/20240416-previewer-upload-gltf-to-glb.html#in-core-and-done-by-us",
-    "title": "Proposed: Implementing a 3D Previewer for GLTF with XMP Metadata",
+    "objectID": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#the-downsides",
+    "href": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#the-downsides",
+    "title": "Proposed: Enhancing Avatar Expressiveness with AI-Generated Blend Shapes",
     "section": "",
-    "text": "The implementation of this proposal will be done by the V-Sekai development team."
+    "text": "Potential performance impact due to real-time AI processing.\nThe requirement for ongoing dataset updates to improve and maintain AI model accuracy."
   },
   {
-    "objectID": "decisions/20240416-previewer-upload-gltf-to-glb.html#status",
-    "href": "decisions/20240416-previewer-upload-gltf-to-glb.html#status",
-    "title": "Proposed: Implementing a 3D Previewer for GLTF with XMP Metadata",
+    "objectID": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#the-road-not-taken",
+    "href": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#the-road-not-taken",
+    "title": "Proposed: Enhancing Avatar Expressiveness with AI-Generated Blend Shapes",
     "section": "",
-    "text": "Proposed"
+    "text": "Alternative options included manual blend shape sculpting by artists and community-driven expression templates, both of which were deemed to lack scalability and flexibility compared to an AI-based solution."
   },
   {
-    "objectID": "decisions/20240416-previewer-upload-gltf-to-glb.html#decision-makers",
-    "href": "decisions/20240416-previewer-upload-gltf-to-glb.html#decision-makers",
-    "title": "Proposed: Implementing a 3D Previewer for GLTF with XMP Metadata",
+    "objectID": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#the-infrequent-use-case",
+    "href": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#the-infrequent-use-case",
+    "title": "Proposed: Enhancing Avatar Expressiveness with AI-Generated Blend Shapes",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "For users requiring highly specialized expressions seldom encountered in regular interactions, such as niche cultural facial gestures."
   },
   {
-    "objectID": "decisions/20240416-previewer-upload-gltf-to-glb.html#tags",
-    "href": "decisions/20240416-previewer-upload-gltf-to-glb.html#tags",
-    "title": "Proposed: Implementing a 3D Previewer for GLTF with XMP Metadata",
+    "objectID": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#in-core-and-done-by-us",
+    "href": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#in-core-and-done-by-us",
+    "title": "Proposed: Enhancing Avatar Expressiveness with AI-Generated Blend Shapes",
     "section": "",
-    "text": "V-Sekai"
+    "text": "This initiative is core to V-Sekai’s mission of enhanced user interaction and must be developed in-house to ensure deep integration and alignment with existing systems."
   },
   {
-    "objectID": "decisions/20240416-previewer-upload-gltf-to-glb.html#further-reading",
-    "href": "decisions/20240416-previewer-upload-gltf-to-glb.html#further-reading",
-    "title": "Proposed: Implementing a 3D Previewer for GLTF with XMP Metadata",
+    "objectID": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#status",
+    "href": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#status",
+    "title": "Proposed: Enhancing Avatar Expressiveness with AI-Generated Blend Shapes",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis proposal was assisted by AI assistant Aria."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20220131-elixir-desktop-uro.html",
-    "href": "decisions/20220131-elixir-desktop-uro.html",
-    "title": "Proposed: Make a desktop version of Uro for ease of development.",
+    "objectID": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#decision-makers",
+    "href": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#decision-makers",
+    "title": "Proposed: Enhancing Avatar Expressiveness with AI-Generated Blend Shapes",
     "section": "",
-    "text": "Status: proposed \nDeciders: V-Sekai,fire,\nTags: V-Sekai,\n\n\n\nIt is hard to deploy URO.\n\n\n\nDeploy URO using Elixir Desktop.\n\n\n\n\nBuild of Elixir Desktop\nValidate both Windows and Linux builds.\nFocus on Linux first.\n\n\n\n\n\nAble to deploy Uro easier.\n\n\n\n\n\nIs this the most important thing to do with limited resources?\n\n\n\n\n\nOption: Current status.\nRejection Reason: Don’t have a platform for developing the backend.\n\n\n\n\nNot a few lines of code.\n\n\n\nWe are the maintainers of uro.\n\n\n\n\nhttps://github.com/elixir-desktop/desktop\nhttps://github.com/V-Sekai/uro\n\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "V-Sekai development team and community stakeholders."
   },
   {
-    "objectID": "decisions/20220131-elixir-desktop-uro.html#context-and-problem-statement",
-    "href": "decisions/20220131-elixir-desktop-uro.html#context-and-problem-statement",
-    "title": "Proposed: Make a desktop version of Uro for ease of development.",
+    "objectID": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#tags",
+    "href": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#tags",
+    "title": "Proposed: Enhancing Avatar Expressiveness with AI-Generated Blend Shapes",
     "section": "",
-    "text": "It is hard to deploy URO."
+    "text": "V-Sekai, Avatar Customization, AI, Facial Expressions"
   },
   {
-    "objectID": "decisions/20220131-elixir-desktop-uro.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20220131-elixir-desktop-uro.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: Make a desktop version of Uro for ease of development.",
+    "objectID": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#further-reading",
+    "href": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#further-reading",
+    "title": "Proposed: Enhancing Avatar Expressiveness with AI-Generated Blend Shapes",
     "section": "",
-    "text": "Deploy URO using Elixir Desktop."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nAssisted by Aria."
   },
   {
-    "objectID": "decisions/20220131-elixir-desktop-uro.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20220131-elixir-desktop-uro.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Make a desktop version of Uro for ease of development.",
+    "objectID": "decisions/20211031-tire-model-car-sim.html",
+    "href": "decisions/20211031-tire-model-car-sim.html",
+    "title": "Proposed: Tire model car sim",
     "section": "",
-    "text": "Build of Elixir Desktop\nValidate both Windows and Linux builds.\nFocus on Linux first."
+    "text": "Proposed: Tire model car sim\n\nContext and Problem Statement\nCreate a vehicle simulation\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nUse physx’s tire simulation. While citing their mit license.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nUse math model.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nOne does not simply make a vehicle sim.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nMaybe out of scope? But I have an approach.\n\n\nReferences\n\n\nTire Modeling #########################################\nThe default tire model employed by PhysX vehicles is discussed in Appendix H of the CarSimEd documentation:\nhttp://www.eggert.highpeakpress.com/ME485/Docs/CarSimEd.pdf\nPhysX vehicles allow any tire model to be simulated by specifying a tire shader, as discussed in :ref:Tire Shaders. A tire model commonly used in engineering simulation is the Pacejka tire model:\nhttp://phors.locost7.info/phors21.htm\n\nhttp://phors.locost7.info/phors22.htm\n\n\nhttps://github.com/NVIDIAGameWorks/PhysX/blob/ae80dede0546d652040ae6260a810e53e20a06fa/physx/documentation/PhysXGuide/_sources/Manual/Vehicles.txt#L2058\nhttps://web.archive.org/web/20180712141747/http://www.eggert.highpeakpress.com/ME485/Docs/CarSimEd.pdf\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20220131-elixir-desktop-uro.html#positive-consequences",
-    "href": "decisions/20220131-elixir-desktop-uro.html#positive-consequences",
-    "title": "Proposed: Make a desktop version of Uro for ease of development.",
+    "objectID": "decisions/20230624-v-sekai-roadmap.html",
+    "href": "decisions/20230624-v-sekai-roadmap.html",
+    "title": "Accepted: V-Sekai Roadmap and Goals 2023-06-24",
     "section": "",
-    "text": "Able to deploy Uro easier."
+    "text": "Accepted: V-Sekai Roadmap and Goals 2023-06-24\n\nMetadata\n\nStatus: accepted\nDeciders: V-Sekai, fire\nTags: V-Sekai, chatgpt4 summary,\n\n\n\nContext and Problem Statement\nWhat is the V-Sekai Roadmap and Goals?\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nThe roadmap presented here is short-term.\n\n\nDescribe how your proposal will work with code, pseudo-code, mock-ups, or diagrams\nBy avoiding work on User Generated Content (UGC) and world building, we can prioritize the three main states in the roadmap: “World / Avatar Performance” (WAP), “Networking” (NET), and “UI/UX”. This allows the team to focus on the core aspects of V-Sekai and achieve the goals more efficiently.\n\nMonitoring and Logging System Test:\n\nSetup logging framework\nConfigure monitoring system\nCreate a dashboard\n\nTest Environment with Simulated Data Test:\n\nCreate test scenarios\nGenerate simulated data\nConfigure test environment\nExecute test scenarios\nAnalyze test results\n\n\n\n\nPositive Consequences\n\nEasier creation of V-Sekai.\nFocused development on core aspects.\n\n\n\nNegative Consequences\n\nPotential overhead challenges.\n\n\n\nOption graveyard\n\nWaiting for Godot Engine 4.2 instead of assisting with 4.1 features.\n\n\n\nIf this enhancement will be used infrequently, can it be worked around with a few lines of script?\nNo. This is a process.\n\n\nIs there a reason why this should be core and done by us?\nThis is a core process for V-Sekai.\n\n\nReferences\n\nV-Sekai"
   },
   {
-    "objectID": "decisions/20220131-elixir-desktop-uro.html#negative-consequences",
-    "href": "decisions/20220131-elixir-desktop-uro.html#negative-consequences",
-    "title": "Proposed: Make a desktop version of Uro for ease of development.",
+    "objectID": "decisions/20230618-v-sekai-roadmap.html",
+    "href": "decisions/20230618-v-sekai-roadmap.html",
+    "title": "Accepted: V-Sekai Roadmap and Goals 2023-06-18",
     "section": "",
-    "text": "Is this the most important thing to do with limited resources?"
+    "text": "Accepted: V-Sekai Roadmap and Goals 2023-06-18\n\nMetadata\n\nStatus: superseded\nDeciders: V-Sekai, fire, guillefix\nTags: V-Sekai, chatgpt4 summary,\n\n\n\nContext and Problem Statement\nWhat is the V-Sekai Roadmap and Goals?\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nThe roadmap presented here is short-term.\n\n\nDescribe how your proposal will work with code, pseudo-code, mock-ups, or diagrams\nBy avoiding work on User Generated Content (UGC) and world building, we can prioritize the three main states in the roadmap: “World / Avatar Performance” (WAP), “Networking” (NET), and “UI/UX”. This allows the team to focus on the core aspects of V-Sekai and achieve the goals more efficiently.\n\n\nGoals\n\nWorld / Avatar Performance (WAP)\n\nTimeline: Q2-Q3\nImplement light assets and asynchronous loading to reduce load time by 30%\nUtilize modern rendering techniques and high-performance libraries to achieve 60 FPS on mid-range devices\nApply network optimization and low latency protocols for better performance, reducing latency by 50%\n\n\n\nNetworking (NET)\n\nTimeline: Q2-Q3\nUse efficient data formats and optimized compression algorithms to reduce file size by 40%\nEnsure accurate IK points are respected, achieving 95% accuracy\nExplore multiple technologies and alternative solutions for continuous improvement, evaluating 3 new technologies per quarter\n\n\n\nFirst Time User Experience (FTUX)\n\nTimeline: Q3-Q4\nOptimize first-time user experience by improving the loading process, increasing user retention by 20%\n\n\n\nDiagram\nsequenceDiagram\n    participant V-Sekai\n    participant Player\n    participant Creator\n    participant Lyuma as \"Lyuma (VRM1 - WAP)\"\n\n    Note over Lyuma: WAP: World / Avatar Performance\n    Note over Lyuma: Timeline: Q2-Q3\n\n    Creator-&gt;&gt;V-Sekai: Implement light assets and asynchronous loading (reduce load time by 30%)\n    V-Sekai-&gt;&gt;Player: Utilize modern rendering techniques and high-performance libraries (achieve 60 FPS on mid-range devices)\n    Player-&gt;&gt;Creator: Apply network optimization and low latency protocols for better performance (reduce latency by 50%)\n\n    Note over Player, Creator: NET: Network Optimization Techniques\n    Note over Player, Creator: Timeline: Q2-Q3\n\n    Creator-&gt;&gt;V-Sekai: Use efficient data formats and optimized compression algorithms (reduce file size by 40%)\n    V-Sekai-&gt;&gt;Player: Ensure accurate IK points are respected (achieve 95% accuracy)\n    V-Sekai-&gt;&gt;Player: Explore multiple technologies and alternative solutions for continuous improvement (evaluate 3 new technologies per quarter)\n\n    %% Metrics\n    Note over Player, Creator: Metrics:\n    Player-&gt;&gt;Player: File size reduction\n    Player-&gt;&gt;Player: IK accuracy\n    Player-&gt;&gt;Player: Technologies evaluated\n\nsequenceDiagram\n    participant Fire\n    participant Creator\n\n    Fire-&gt;&gt;Creator: Optimize first-time user experience by improving the loading process (increase user retention by 20%)\n\n    Note over Fire, Creator: FTUX: First Time User Experience\n    Note over Fire, Creator: Timeline: Q3-Q4\n\n    %% Metrics\n    Note over Fire, Creator: Metrics:\n    Fire-&gt;&gt;Fire: Load time reduction\n    Fire-&gt;&gt;Fire: Frame rate (FPS) for flat desktop\n    Fire-&gt;&gt;Fire: Frame rate (FPS) for VR desktop\n    Fire-&gt;&gt;Fire: Latency reduction\n    Fire-&gt;&gt;Fire: User retention rate\n\n\n\nPositive Consequences\n\nEasier creation of V-Sekai.\nFocused development on core aspects.\n\n\n\nNegative Consequences\n\nPotential overhead challenges.\n\n\n\nOption graveyard\n\nWaiting for Godot Engine 4.2 instead of assisting with 4.1 features.\n\n\n\nIf this enhancement will be used infrequently, can it be worked around with a few lines of script?\nNo. This is a process.\n\n\nIs there a reason why this should be core and done by us?\nThis is a core process for V-Sekai.\n\n\nReferences\n\nV-Sekai"
   },
   {
-    "objectID": "decisions/20220131-elixir-desktop-uro.html#option-graveyard",
-    "href": "decisions/20220131-elixir-desktop-uro.html#option-graveyard",
-    "title": "Proposed: Make a desktop version of Uro for ease of development.",
+    "objectID": "decisions/20210710-verify-pr-workflow.html",
+    "href": "decisions/20210710-verify-pr-workflow.html",
+    "title": "Proposed: Describe a Godot Engine pr verification workflow",
     "section": "",
-    "text": "Option: Current status.\nRejection Reason: Don’t have a platform for developing the backend."
+    "text": "Proposed: Describe a Godot Engine pr verification workflow\n\nContext and Problem Statement\nA Godot Engine pr needs to be verified for correctness and style.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nThis workflows describes how fire checks pull requests.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n\nStart Windows 10.\nInstall scoop\nscoop install visual-studio-code llvm-mingw\nInstall python and scons\ngit checkout https://github.com/V-Sekai/v-sekai-pr-template --recurse-submodules\nOpen repository in Visual Studio Code.\nSwitch godot engine branch\nPress launch in Visual Studio Code\nVerify fixes.\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nThis is a workflow.\n\n\nPositive Consequences\nMore robust techniques for doing prs.\n\n\nNegative Consequences\nPaperwork and complexity.\n\n\nIs there a reason why this should be core and done by us?\nThis is a core procedure.\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20220131-elixir-desktop-uro.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20220131-elixir-desktop-uro.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Make a desktop version of Uro for ease of development.",
+    "objectID": "decisions/20230123-recording-demo-checklist.html",
+    "href": "decisions/20230123-recording-demo-checklist.html",
+    "title": "Proposed: Recording demo checklist",
     "section": "",
-    "text": "Not a few lines of code."
+    "text": "Proposed: Recording demo checklist\n\nContext and Problem Statement\nHave a checklist of tasks needed for recording demos.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nI want to have consistency for the videos I record.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\n\nDo I have a keyboard to screen displayer?\nDoes the video have a V-Sekai logo?\nDoes the video have a work in progress disclaimer?\nDo I have a time code bar with V-Sekai Game prefix and a timezone suffix? https://obsproject.com/forum/resources/rtc-timecode-generator.1301/\nIs it under 4 megabytes?\n\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nOption graveyard\nNo response\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nThis is a script for filming.\n\n\nIs there a reason why this should be core and done by us?\nWanted to write down my preferences.\n\n\nReferences\n\nV-Sekai\n\n\n\nLicense of the contribution\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20220131-elixir-desktop-uro.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20220131-elixir-desktop-uro.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Make a desktop version of Uro for ease of development.",
+    "objectID": "decisions/20230619-move-cockroachdb-to-yugabyte.html",
+    "href": "decisions/20230619-move-cockroachdb-to-yugabyte.html",
+    "title": "Rejected: V-Sekai Database Solution for 50,000 Concurrent Online Users",
     "section": "",
-    "text": "We are the maintainers of uro."
+    "text": "Status: rejected\nDeciders: V-Sekai, fire\nTags: V-Sekai, llm summarization\n\n\n\n\nV-Sekai is currently facing a decision on which database solution to use for their project that can handle the load of 50,000 concurrent online users. The options being considered are PostgreSQL, CockroachDB, SQLite on FoundationDB, or YugabyteDB. Each option has its own set of advantages and disadvantages, and the team needs to determine which one best fits their requirements.\n\n\n\nBased on the discussion, it seems that YugabyteDB might be a suitable choice for V-Sekai’s needs. It offers a single-node setup with the potential for growth, supports a wide range of data types, and provides externally consistent transaction levels. Additionally, YugabyteDB appears to be more compatible with the existing schema compared to SQLite.\n\n\n\nTo implement YugabyteDB as the chosen database solution, the following steps should be taken:\n\nEvaluate YugabyteDB’s compatibility with the existing schema and identify any necessary adjustments.\nSet up a single-node YugabyteDB instance for initial development and testing.\nMigrate existing data from the current database solution to YugabyteDB.\nUpdate the application code to work with YugabyteDB.\nPerform thorough testing to ensure stability and performance meet expectations.\n\n\n\n\n\nSingle-node setup with the potential for growth\nCompatibility with the existing schema\nSupport for a wide range of data types\nExternally consistent transaction levels\n\n\n\n\n\nPotential new problems and challenges associated with adopting a new database solution\nPossible learning curve for the team in working with YugabyteDB\nCannot do online primary key upgrades.\n\n\n\n\n\nPostgreSQL: While a popular and powerful database solution, it may not offer the desired single-node setup with growth potential.\nCockroachDB: The current implementation has been problematic due to its 3-node distributed configuration in Kubernetes.\nSQLite on FoundationDB: Limited data types and compatibility issues with the existing schema make this option less desirable.\n\n\n\n\nNo, the choice of database solution is a core aspect of the project and cannot be easily worked around with a script.\n\n\n\nYes, selecting the appropriate database solution is crucial for the success and stability of V-Sekai. It directly impacts the performance, scalability, and maintainability of the platform.\n\n\n\n\nV-Sekai\nYugabyteDB Data Types\nCockroach Labs\nMVSQLite: Distributed MVCC SQLite that runs on FoundationDB\nPostgreSQL"
   },
   {
-    "objectID": "decisions/20220131-elixir-desktop-uro.html#references",
-    "href": "decisions/20220131-elixir-desktop-uro.html#references",
-    "title": "Proposed: Make a desktop version of Uro for ease of development.",
+    "objectID": "decisions/20230619-move-cockroachdb-to-yugabyte.html#metadata",
+    "href": "decisions/20230619-move-cockroachdb-to-yugabyte.html#metadata",
+    "title": "Rejected: V-Sekai Database Solution for 50,000 Concurrent Online Users",
     "section": "",
-    "text": "https://github.com/elixir-desktop/desktop\nhttps://github.com/V-Sekai/uro"
+    "text": "Status: rejected\nDeciders: V-Sekai, fire\nTags: V-Sekai, llm summarization"
   },
   {
-    "objectID": "decisions/20220131-elixir-desktop-uro.html#derivative-license",
-    "href": "decisions/20220131-elixir-desktop-uro.html#derivative-license",
-    "title": "Proposed: Make a desktop version of Uro for ease of development.",
+    "objectID": "decisions/20230619-move-cockroachdb-to-yugabyte.html#context-and-problem-statement",
+    "href": "decisions/20230619-move-cockroachdb-to-yugabyte.html#context-and-problem-statement",
+    "title": "Rejected: V-Sekai Database Solution for 50,000 Concurrent Online Users",
     "section": "",
-    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "V-Sekai is currently facing a decision on which database solution to use for their project that can handle the load of 50,000 concurrent online users. The options being considered are PostgreSQL, CockroachDB, SQLite on FoundationDB, or YugabyteDB. Each option has its own set of advantages and disadvantages, and the team needs to determine which one best fits their requirements."
   },
   {
-    "objectID": "decisions/20211031-1000-player-servers.html",
-    "href": "decisions/20211031-1000-player-servers.html",
-    "title": "Proposed: 1000 player servers",
+    "objectID": "decisions/20230619-move-cockroachdb-to-yugabyte.html#proposed-solution",
+    "href": "decisions/20230619-move-cockroachdb-to-yugabyte.html#proposed-solution",
+    "title": "Rejected: V-Sekai Database Solution for 50,000 Concurrent Online Users",
     "section": "",
-    "text": "Proposed: 1000 player servers\n\nContext and Problem Statement\nWant to support large groups of players\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nSmall crowds aren’t plausible.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n\nperformance testing\nrobots\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nRequires devops and scripting.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nI have an approach!\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Based on the discussion, it seems that YugabyteDB might be a suitable choice for V-Sekai’s needs. It offers a single-node setup with the potential for growth, supports a wide range of data types, and provides externally consistent transaction levels. Additionally, YugabyteDB appears to be more compatible with the existing schema compared to SQLite."
   },
   {
-    "objectID": "decisions/20230830-better-object-pick.html",
-    "href": "decisions/20230830-better-object-pick.html",
-    "title": "Proposed: Improving VR Experience",
+    "objectID": "decisions/20230619-move-cockroachdb-to-yugabyte.html#implementation",
+    "href": "decisions/20230619-move-cockroachdb-to-yugabyte.html#implementation",
+    "title": "Rejected: V-Sekai Database Solution for 50,000 Concurrent Online Users",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nV-Sekai is a virtual reality (VR) platform that offers users the opportunity to immerse themselves in virtual worlds. However, there are certain limitations that hinder the overall user experience. This documentation aims to address these limitations by proposing specific areas for improvement within V-Sekai.\n\n\n\nV-Sekai currently faces several limitations, including non-functional menus in VR mode and a limited number of available worlds. To overcome these challenges and enhance the user experience, we must prioritize and focus on one area for improvement.\n\n\nImproving Object Pickup and Menus: Enhancing object pickup mechanics and menus can make interactions within V-Sekai more intuitive and user-friendly. This may include refining controls, feedback mechanisms for object pickup, and finding alternative methods to access menus while in VR mode.\n\n\n\n\nTo ensure efficient use of time and resources, it is advisable to choose one area to focus on and strive to complete it within a two-week timeframe. This focused approach allows for significant progress in improving V-Sekai.\n\n\n\nBy addressing these limitations, V-Sekai can offer a more seamless and immersive VR experience. Improving object pickup and menus will enhance user interactions, making them more intuitive and user-friendly. This will ultimately result in a more engaging and enjoyable experience for V-Sekai users.\n\n\n\nGiven the limited timeframe, it may not be possible to address all the identified limitations simultaneously. Additionally, the complexity of refining object pickup mechanics and menus may present challenges in achieving substantial improvements within the two-week timeframe. It’s important to carefully assess the scope and feasibility of the proposed enhancements before committing to the timeframe.\n\n\n\nWhile focusing on improving object pickup and menus is recommended for the given timeframe, it’s important to acknowledge that there are other potential areas for improvement. Exploring options such as expanding the variety of worlds, integrating backend services, or optimizing performance can be considered in future iterations of V-Sekai.\n\n\n\nThe development team at V-Sekai should primarily handle the implementation and integration of the chosen improvement. However, collaborative efforts involving developers, designers, and user experience experts may be necessary to ensure the improvements align with the overall vision and goals of V-Sekai.\n\n\n\n\nV-Sekai\nThis article is assisted by AI."
+    "text": "To implement YugabyteDB as the chosen database solution, the following steps should be taken:\n\nEvaluate YugabyteDB’s compatibility with the existing schema and identify any necessary adjustments.\nSet up a single-node YugabyteDB instance for initial development and testing.\nMigrate existing data from the current database solution to YugabyteDB.\nUpdate the application code to work with YugabyteDB.\nPerform thorough testing to ensure stability and performance meet expectations."
   },
   {
-    "objectID": "decisions/20230830-better-object-pick.html#metadata",
-    "href": "decisions/20230830-better-object-pick.html#metadata",
-    "title": "Proposed: Improving VR Experience",
+    "objectID": "decisions/20230619-move-cockroachdb-to-yugabyte.html#positive-consequences",
+    "href": "decisions/20230619-move-cockroachdb-to-yugabyte.html#positive-consequences",
+    "title": "Rejected: V-Sekai Database Solution for 50,000 Concurrent Online Users",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai"
+    "text": "Single-node setup with the potential for growth\nCompatibility with the existing schema\nSupport for a wide range of data types\nExternally consistent transaction levels"
   },
   {
-    "objectID": "decisions/20230830-better-object-pick.html#introduction",
-    "href": "decisions/20230830-better-object-pick.html#introduction",
-    "title": "Proposed: Improving VR Experience",
+    "objectID": "decisions/20230619-move-cockroachdb-to-yugabyte.html#negative-consequences",
+    "href": "decisions/20230619-move-cockroachdb-to-yugabyte.html#negative-consequences",
+    "title": "Rejected: V-Sekai Database Solution for 50,000 Concurrent Online Users",
     "section": "",
-    "text": "V-Sekai is a virtual reality (VR) platform that offers users the opportunity to immerse themselves in virtual worlds. However, there are certain limitations that hinder the overall user experience. This documentation aims to address these limitations by proposing specific areas for improvement within V-Sekai."
+    "text": "Potential new problems and challenges associated with adopting a new database solution\nPossible learning curve for the team in working with YugabyteDB\nCannot do online primary key upgrades."
   },
   {
-    "objectID": "decisions/20230830-better-object-pick.html#the-challenge",
-    "href": "decisions/20230830-better-object-pick.html#the-challenge",
-    "title": "Proposed: Improving VR Experience",
+    "objectID": "decisions/20230619-move-cockroachdb-to-yugabyte.html#option-graveyard",
+    "href": "decisions/20230619-move-cockroachdb-to-yugabyte.html#option-graveyard",
+    "title": "Rejected: V-Sekai Database Solution for 50,000 Concurrent Online Users",
     "section": "",
-    "text": "V-Sekai currently faces several limitations, including non-functional menus in VR mode and a limited number of available worlds. To overcome these challenges and enhance the user experience, we must prioritize and focus on one area for improvement.\n\n\nImproving Object Pickup and Menus: Enhancing object pickup mechanics and menus can make interactions within V-Sekai more intuitive and user-friendly. This may include refining controls, feedback mechanisms for object pickup, and finding alternative methods to access menus while in VR mode."
+    "text": "PostgreSQL: While a popular and powerful database solution, it may not offer the desired single-node setup with growth potential.\nCockroachDB: The current implementation has been problematic due to its 3-node distributed configuration in Kubernetes.\nSQLite on FoundationDB: Limited data types and compatibility issues with the existing schema make this option less desirable."
   },
   {
-    "objectID": "decisions/20230830-better-object-pick.html#the-strategy",
-    "href": "decisions/20230830-better-object-pick.html#the-strategy",
-    "title": "Proposed: Improving VR Experience",
+    "objectID": "decisions/20230619-move-cockroachdb-to-yugabyte.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230619-move-cockroachdb-to-yugabyte.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Rejected: V-Sekai Database Solution for 50,000 Concurrent Online Users",
     "section": "",
-    "text": "To ensure efficient use of time and resources, it is advisable to choose one area to focus on and strive to complete it within a two-week timeframe. This focused approach allows for significant progress in improving V-Sekai."
+    "text": "No, the choice of database solution is a core aspect of the project and cannot be easily worked around with a script."
   },
   {
-    "objectID": "decisions/20230830-better-object-pick.html#upsides",
-    "href": "decisions/20230830-better-object-pick.html#upsides",
-    "title": "Proposed: Improving VR Experience",
+    "objectID": "decisions/20230619-move-cockroachdb-to-yugabyte.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230619-move-cockroachdb-to-yugabyte.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Rejected: V-Sekai Database Solution for 50,000 Concurrent Online Users",
     "section": "",
-    "text": "By addressing these limitations, V-Sekai can offer a more seamless and immersive VR experience. Improving object pickup and menus will enhance user interactions, making them more intuitive and user-friendly. This will ultimately result in a more engaging and enjoyable experience for V-Sekai users."
+    "text": "Yes, selecting the appropriate database solution is crucial for the success and stability of V-Sekai. It directly impacts the performance, scalability, and maintainability of the platform."
   },
   {
-    "objectID": "decisions/20230830-better-object-pick.html#downsides",
-    "href": "decisions/20230830-better-object-pick.html#downsides",
-    "title": "Proposed: Improving VR Experience",
+    "objectID": "decisions/20230619-move-cockroachdb-to-yugabyte.html#references",
+    "href": "decisions/20230619-move-cockroachdb-to-yugabyte.html#references",
+    "title": "Rejected: V-Sekai Database Solution for 50,000 Concurrent Online Users",
     "section": "",
-    "text": "Given the limited timeframe, it may not be possible to address all the identified limitations simultaneously. Additionally, the complexity of refining object pickup mechanics and menus may present challenges in achieving substantial improvements within the two-week timeframe. It’s important to carefully assess the scope and feasibility of the proposed enhancements before committing to the timeframe."
+    "text": "V-Sekai\nYugabyteDB Data Types\nCockroach Labs\nMVSQLite: Distributed MVCC SQLite that runs on FoundationDB\nPostgreSQL"
   },
   {
-    "objectID": "decisions/20230830-better-object-pick.html#the-road-not-taken",
-    "href": "decisions/20230830-better-object-pick.html#the-road-not-taken",
-    "title": "Proposed: Improving VR Experience",
+    "objectID": "decisions/20240111-fit-clothing-on-humans-without-tearing.html",
+    "href": "decisions/20240111-fit-clothing-on-humans-without-tearing.html",
+    "title": "Draft: Fit Clothing on Humans Without Tearing",
     "section": "",
-    "text": "While focusing on improving object pickup and menus is recommended for the given timeframe, it’s important to acknowledge that there are other potential areas for improvement. Exploring options such as expanding the variety of worlds, integrating backend services, or optimizing performance can be considered in future iterations of V-Sekai."
+    "text": "Status: Draft\nDeciders: V-Sekai, Fire, Joe Cat\nTags: V-Sekai\n\n\n\n\nThe challenge is to accurately fit clothing on a 3D human model without causing any tearing in the fabric. The proposed solution involves utilizing machine learning technology that ensures constraints are maintained for vertex faces during the fitting process."
   },
   {
-    "objectID": "decisions/20230830-better-object-pick.html#in-core-and-done-by-us",
-    "href": "decisions/20230830-better-object-pick.html#in-core-and-done-by-us",
-    "title": "Proposed: Improving VR Experience",
+    "objectID": "decisions/20240111-fit-clothing-on-humans-without-tearing.html#metadata",
+    "href": "decisions/20240111-fit-clothing-on-humans-without-tearing.html#metadata",
+    "title": "Draft: Fit Clothing on Humans Without Tearing",
     "section": "",
-    "text": "The development team at V-Sekai should primarily handle the implementation and integration of the chosen improvement. However, collaborative efforts involving developers, designers, and user experience experts may be necessary to ensure the improvements align with the overall vision and goals of V-Sekai."
+    "text": "Status: Draft\nDeciders: V-Sekai, Fire, Joe Cat\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20230830-better-object-pick.html#further-reading",
-    "href": "decisions/20230830-better-object-pick.html#further-reading",
-    "title": "Proposed: Improving VR Experience",
+    "objectID": "decisions/20240111-fit-clothing-on-humans-without-tearing.html#context",
+    "href": "decisions/20240111-fit-clothing-on-humans-without-tearing.html#context",
+    "title": "Draft: Fit Clothing on Humans Without Tearing",
     "section": "",
-    "text": "V-Sekai\nThis article is assisted by AI."
+    "text": "The challenge is to accurately fit clothing on a 3D human model without causing any tearing in the fabric. The proposed solution involves utilizing machine learning technology that ensures constraints are maintained for vertex faces during the fitting process."
   },
   {
-    "objectID": "decisions/20230527-server-side-content-validation.html",
-    "href": "decisions/20230527-server-side-content-validation.html",
-    "title": "Proposed: Implement server-side content validation export followed by a sanitization service and CDN support",
+    "objectID": "decisions/20211031-membrane-framework-streaming-mixer.html",
+    "href": "decisions/20211031-membrane-framework-streaming-mixer.html",
+    "title": "Proposed: Membrane Framework streaming Mixer",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai, Bioblaze Payne, fire\nTags: V-Sekai, GPT-4\n\n\n\n\nV-Sekai is a virtual world platform that allows users to create and share content. However, there are limitations in terms of content validation and distribution, which can lead to potential security risks and slow content delivery.\n\n\n\nImplement server-side validation export followed by a sanitization service and integrate with a Content Delivery Network (CDN) for efficient content distribution.\n\n\n\n\nServer-side validation: Develop a server-side validation system that checks the uploaded content for any malicious code or vulnerabilities.\nSanitization service: Implement a sanitization service that cleanses the content from any harmful elements before it’s distributed.\nCDN integration: Integrate the platform with a CDN to ensure fast and reliable content delivery to users worldwide.\n\n\n\n\n\nEnhanced security: Server-side validation and sanitization will help prevent malicious content from being distributed.\nImproved performance: CDN integration will speed up content delivery and provide a better user experience.\nScalability: The proposed solution will allow the platform to handle increased traffic and content uploads efficiently.\n\n\n\n\n\nIncreased development time: Implementing the proposed solution may require additional development time and resources.\nMaintenance: Ongoing maintenance of the server-side validation, sanitization service, and CDN integration will be required.\n\n\n\n\n\nClient-side validation only: This option was discarded due to its limited effectiveness in preventing malicious content distribution.\nNo CDN integration: This option was discarded as it would not address the issue of slow content delivery.\n\n\n\n\nNo, the proposed solution requires a more comprehensive approach to ensure secure and efficient content distribution.\n\n\n\nYes, implementing server-side validation, sanitization service, and CDN integration is essential for maintaining the platform’s security and providing a seamless user experience. These features should be part of the core functionality to ensure consistent performance and reliability.\n\n\n\n\nV-Sekai\nContent Delivery Network (CDN)"
+    "text": "Proposed: Membrane Framework streaming Mixer\n\nContext and Problem Statement\nI want to stream 3d content to godot engine live.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nCurrently having an import and export pipeline that isn’t live is frustrating.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n\nFind a stable version of Blender\nUse mixer plugin with that stable version\nMake Godot Engine sync plugin\n???\nMake a mixer sync server\nCreate python pickle packet\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot a few lines of code.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nI found this idea and its cool.\n\n\nReferences\n\nhttps://github.com/ubisoft/mixer\nhttps://github.com/ubisoft/vrtist\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230527-server-side-content-validation.html#metadata",
-    "href": "decisions/20230527-server-side-content-validation.html#metadata",
-    "title": "Proposed: Implement server-side content validation export followed by a sanitization service and CDN support",
+    "objectID": "decisions/20230608-v-sekai-roadmap.html",
+    "href": "decisions/20230608-v-sekai-roadmap.html",
+    "title": "Superseded: V-Sekai Roadmap and Goals 2023-06-08",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai, Bioblaze Payne, fire\nTags: V-Sekai, GPT-4"
+    "text": "Superseded: V-Sekai Roadmap and Goals 2023-06-08\n\nMetadata\n\nStatus: superseded by 20230618-v-sekai-roadmap.md \nDeciders: V-Sekai,fire,lyuma,\nTags: V-Sekai,chatgpt4 summary,\n\n\n\nContext and Problem Statement\nWhat is the V-Sekai Roadmap and Goals?\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nThe roadmap presented here is short-term.\n\n\nDescribe how your proposal will work with code, pseudo-code, mock-ups, or diagrams\ngraph LR\n  subgraph Short Term\n    A[June 08th, 2023] --&gt; D[IK Points for V-sekai]\n    D --&gt; E[Investigate ManyBoneIK & mediapipe to support Facial Mocap to ARKit 52 blendshape and audio to face]\n    E --&gt; F[Elixir mvsqlite Serversidecar]\n    F --&gt; I[Add jitter buffer to godot_speech]\n  end\n  subgraph Mid-term Term\n    D --&gt; E[Vrm upload to the asset library]\n    F --&gt; G[Unidot Unity Import upload to the asset library]\n    G --&gt; H[Add jitter buffer to godot_speech]\n    H --&gt; I[Implement onevoip]\n  end\n\n\nPositive Consequences\nWe can create V-Sekai easier.\n\n\nNegative Consequences\nOverhead might be hard.\n\n\nOption graveyard\n\nImplementing a custom voice chat solution instead of using onevoip\nWaiting for Godot Engine 4.2 instead of assisting with 4.1 features\nIgnoring SkeletonIK3D issues and focusing on other aspects\n\n\n\nIf this enhancement will be used infrequently, can it be worked around with a few lines of script?\nNo. This is a process.\n\n\nIs there a reason why this should be core and done by us?\nThis is a core process for V-Sekai.\n\n\nReferences\n\nV-Sekai"
   },
   {
-    "objectID": "decisions/20230527-server-side-content-validation.html#context-and-problem-statement",
-    "href": "decisions/20230527-server-side-content-validation.html#context-and-problem-statement",
-    "title": "Proposed: Implement server-side content validation export followed by a sanitization service and CDN support",
+    "objectID": "decisions/20210212-use-log4brains-to-manage-the-adrs.html",
+    "href": "decisions/20210212-use-log4brains-to-manage-the-adrs.html",
+    "title": "Superseded: Use Log4brains to manage the ADRs",
     "section": "",
-    "text": "V-Sekai is a virtual world platform that allows users to create and share content. However, there are limitations in terms of content validation and distribution, which can lead to potential security risks and slow content delivery."
+    "text": "Status: superseded\nDate: 2021-02-11\nTags: dev-tools, doc\n\n\n\nWe want to record architectural decisions made in this project. Which tool(s) should we use to manage these records?\n\n\n\n\nLog4brains: architecture knowledge base (command-line + static site generator)\nADR Tools: command-line to create ADRs\nADR Tools Python: command-line to create ADRs\nadr-viewer: static site generator\nadr-log: command-line to create a TOC of ADRs\n\n\n\n\nChosen option: “Log4brains”, because it includes the features of all the other tools, and even more.\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230527-server-side-content-validation.html#proposed-solution",
-    "href": "decisions/20230527-server-side-content-validation.html#proposed-solution",
-    "title": "Proposed: Implement server-side content validation export followed by a sanitization service and CDN support",
+    "objectID": "decisions/20210212-use-log4brains-to-manage-the-adrs.html#context-and-problem-statement",
+    "href": "decisions/20210212-use-log4brains-to-manage-the-adrs.html#context-and-problem-statement",
+    "title": "Superseded: Use Log4brains to manage the ADRs",
     "section": "",
-    "text": "Implement server-side validation export followed by a sanitization service and integrate with a Content Delivery Network (CDN) for efficient content distribution."
+    "text": "We want to record architectural decisions made in this project. Which tool(s) should we use to manage these records?"
   },
   {
-    "objectID": "decisions/20230527-server-side-content-validation.html#implementation",
-    "href": "decisions/20230527-server-side-content-validation.html#implementation",
-    "title": "Proposed: Implement server-side content validation export followed by a sanitization service and CDN support",
+    "objectID": "decisions/20210212-use-log4brains-to-manage-the-adrs.html#considered-options",
+    "href": "decisions/20210212-use-log4brains-to-manage-the-adrs.html#considered-options",
+    "title": "Superseded: Use Log4brains to manage the ADRs",
     "section": "",
-    "text": "Server-side validation: Develop a server-side validation system that checks the uploaded content for any malicious code or vulnerabilities.\nSanitization service: Implement a sanitization service that cleanses the content from any harmful elements before it’s distributed.\nCDN integration: Integrate the platform with a CDN to ensure fast and reliable content delivery to users worldwide."
+    "text": "Log4brains: architecture knowledge base (command-line + static site generator)\nADR Tools: command-line to create ADRs\nADR Tools Python: command-line to create ADRs\nadr-viewer: static site generator\nadr-log: command-line to create a TOC of ADRs"
   },
   {
-    "objectID": "decisions/20230527-server-side-content-validation.html#positive-consequences",
-    "href": "decisions/20230527-server-side-content-validation.html#positive-consequences",
-    "title": "Proposed: Implement server-side content validation export followed by a sanitization service and CDN support",
+    "objectID": "decisions/20210212-use-log4brains-to-manage-the-adrs.html#decision-outcome",
+    "href": "decisions/20210212-use-log4brains-to-manage-the-adrs.html#decision-outcome",
+    "title": "Superseded: Use Log4brains to manage the ADRs",
     "section": "",
-    "text": "Enhanced security: Server-side validation and sanitization will help prevent malicious content from being distributed.\nImproved performance: CDN integration will speed up content delivery and provide a better user experience.\nScalability: The proposed solution will allow the platform to handle increased traffic and content uploads efficiently."
+    "text": "Chosen option: “Log4brains”, because it includes the features of all the other tools, and even more."
   },
   {
-    "objectID": "decisions/20230527-server-side-content-validation.html#negative-consequences",
-    "href": "decisions/20230527-server-side-content-validation.html#negative-consequences",
-    "title": "Proposed: Implement server-side content validation export followed by a sanitization service and CDN support",
+    "objectID": "decisions/20210212-use-log4brains-to-manage-the-adrs.html#derivative-license",
+    "href": "decisions/20210212-use-log4brains-to-manage-the-adrs.html#derivative-license",
+    "title": "Superseded: Use Log4brains to manage the ADRs",
     "section": "",
-    "text": "Increased development time: Implementing the proposed solution may require additional development time and resources.\nMaintenance: Ongoing maintenance of the server-side validation, sanitization service, and CDN integration will be required."
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230527-server-side-content-validation.html#option-graveyard",
-    "href": "decisions/20230527-server-side-content-validation.html#option-graveyard",
-    "title": "Proposed: Implement server-side content validation export followed by a sanitization service and CDN support",
+    "objectID": "decisions/20240217-workload-benchmarking.html",
+    "href": "decisions/20240217-workload-benchmarking.html",
+    "title": "Proposed: for using workloads to emulate the usage patterns",
     "section": "",
-    "text": "Client-side validation only: This option was discarded due to its limited effectiveness in preventing malicious content distribution.\nNo CDN integration: This option was discarded as it would not address the issue of slow content delivery."
+    "text": "V-Sekai is a social virtual reality platform. Users interact with each other through avatars in different environments. The main operations include high read operations, moderate to high write operations, and latency sensitivity.\n\n\n\nTo ensure the best performance and user experience, we need to understand how the database system might perform under conditions similar to those experienced by V-Sekai. This includes balancing between high read operations for content delivery and write operations for dynamic user interactions, all while maintaining low latency.\n\n\n\nWe propose to use the Yahoo! Cloud Serving Benchmark (YCSB) workload to emulate the usage patterns of V-Sekai. This would involve a combination of workloads:\n\n\n\n50% read and 50% update operations.\nSimulates user interactions within V-Sekai, such as position updates, gestures, or environment interactions.\n\n\n\n\n\n95% read and 5% update operations.\nRepresents the frequent fetching of environment and avatar details.\n\n\n\n\n\nAdjusting the read and write ratios to reflect the real-time, interactive nature of V-Sekai.\nEmphasizing low latency in the benchmarking parameters.\n\n1. Set up YCSB with Workload A and B\n2. Customize the read/write ratio based on V-Sekai's usage patterns\n3. Emphasize low latency in the benchmarking parameters\n4. Run the benchmark and analyze the results\n\n\n\n\n\nProvides insights into how a database system might perform under V-Sekai-like conditions.\nHelps optimize the balance between read and write operations.\nEnsures low latency for a seamless user experience.\n\n\n\n\n\nRequires careful tuning and understanding of YCSB workloads.\nThe benchmark results might not perfectly reflect real-world usage due to the synthetic nature of benchmarks.\n\n\n\n\nAn alternative would be to use pre-defined YCSB workloads without customization. However, this might not accurately reflect V-Sekai’s specific usage patterns.\n\n\n\nIn scenarios where the usage patterns are not consistent or predictable, customizing the YCSB workload might not provide accurate insights.\n\n\n\nThe setup and customization of the YCSB benchmark will be done by the V-Sekai development team with support from the community stakeholders.\n\n\n\nStatus: Rejected\n\n\n\n\nV-Sekai development team and community stakeholders.\n\n\n\n\n\nV-Sekai, Performance Benchmarking, Database Optimization\n\n\n\n\n\nV-Sekai · GitHub\nV-Sekai/v-sekai-game\n\nThis proposal was assisted by Aria, an AI assistant."
   },
   {
-    "objectID": "decisions/20230527-server-side-content-validation.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230527-server-side-content-validation.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Implement server-side content validation export followed by a sanitization service and CDN support",
+    "objectID": "decisions/20240217-workload-benchmarking.html#context",
+    "href": "decisions/20240217-workload-benchmarking.html#context",
+    "title": "Proposed: for using workloads to emulate the usage patterns",
     "section": "",
-    "text": "No, the proposed solution requires a more comprehensive approach to ensure secure and efficient content distribution."
+    "text": "V-Sekai is a social virtual reality platform. Users interact with each other through avatars in different environments. The main operations include high read operations, moderate to high write operations, and latency sensitivity."
   },
   {
-    "objectID": "decisions/20230527-server-side-content-validation.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230527-server-side-content-validation.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Implement server-side content validation export followed by a sanitization service and CDN support",
+    "objectID": "decisions/20240217-workload-benchmarking.html#problem-statement",
+    "href": "decisions/20240217-workload-benchmarking.html#problem-statement",
+    "title": "Proposed: for using workloads to emulate the usage patterns",
     "section": "",
-    "text": "Yes, implementing server-side validation, sanitization service, and CDN integration is essential for maintaining the platform’s security and providing a seamless user experience. These features should be part of the core functionality to ensure consistent performance and reliability."
+    "text": "To ensure the best performance and user experience, we need to understand how the database system might perform under conditions similar to those experienced by V-Sekai. This includes balancing between high read operations for content delivery and write operations for dynamic user interactions, all while maintaining low latency."
   },
   {
-    "objectID": "decisions/20230527-server-side-content-validation.html#references",
-    "href": "decisions/20230527-server-side-content-validation.html#references",
-    "title": "Proposed: Implement server-side content validation export followed by a sanitization service and CDN support",
+    "objectID": "decisions/20240217-workload-benchmarking.html#proposed-solution",
+    "href": "decisions/20240217-workload-benchmarking.html#proposed-solution",
+    "title": "Proposed: for using workloads to emulate the usage patterns",
     "section": "",
-    "text": "V-Sekai\nContent Delivery Network (CDN)"
+    "text": "We propose to use the Yahoo! Cloud Serving Benchmark (YCSB) workload to emulate the usage patterns of V-Sekai. This would involve a combination of workloads:\n\n\n\n50% read and 50% update operations.\nSimulates user interactions within V-Sekai, such as position updates, gestures, or environment interactions.\n\n\n\n\n\n95% read and 5% update operations.\nRepresents the frequent fetching of environment and avatar details.\n\n\n\n\n\nAdjusting the read and write ratios to reflect the real-time, interactive nature of V-Sekai.\nEmphasizing low latency in the benchmarking parameters.\n\n1. Set up YCSB with Workload A and B\n2. Customize the read/write ratio based on V-Sekai's usage patterns\n3. Emphasize low latency in the benchmarking parameters\n4. Run the benchmark and analyze the results"
   },
   {
-    "objectID": "decisions/20220222-rank-bone-skeletons-with-xgboost.html",
-    "href": "decisions/20220222-rank-bone-skeletons-with-xgboost.html",
-    "title": "Accepted: Rank skeleton #bone names with xgboost",
+    "objectID": "decisions/20240217-workload-benchmarking.html#benefits",
+    "href": "decisions/20240217-workload-benchmarking.html#benefits",
+    "title": "Proposed: for using workloads to emulate the usage patterns",
     "section": "",
-    "text": "Status: accepted \n\n\n\nImprove automatic #bone selection\n\n\n\nUse xgboost to rank bones.\n\n\n\n\nInvestigate\n\n\n\n\n\nWe can guess the proper name.\nUseful for the facial mapping problem?\nUseful for the character generator slider recommendation problem?\nGenerate test data by moving the character\nInference requires only single pose inputs.\n\n\n\n\n\nStarring at the abyss.\n\n\n\n\n\nOption:\n\nbpr from Quora\n\nRejection Reason:\n\nBpr from Quora is not used in production.\n\nOption:\n\ndlrm from facebook\n\nRejection Reason:\n\nToo difficult to run\n\nOption:\n\ncatboost\n\nRejection Reason:\n\nToo difficult to run\n\n\n\n\n\nNot a few lines of code.\n\n\n\nWe need this to make the quality of life of creators better.\n\n\n\n\nhttps://github.com/BayesWitnesses/m2cgen\nhttps://stackoverflow.com/questions/36071672/using-xgboost-in-c\nhttps://github.com/facebookresearch/dlrm\nhttps://medium.com/@marthawhite_81346/learning-with-the-criteo-tb-dataset-e3ec12d9d77e\nhttps://www.kaggle.com/c/criteo-display-ad-challenge/data\nSkeleton pool operator from neural blend shapes.\nhttps://tailor.fandom.com/wiki/Types_of_measurement\nhttps://knarkowicz.wordpress.com/2014/04/16/octahedron-normal-vector-encoding/\nhttps://www.kaggle.com/egordm/deep-learning-recommendation-model-dlrm\n\n    @article{li2021learning,\n    author = {Li, Peizhuo and Aberman, Kfir and Hanocka, Rana and Liu, Libin and Sorkine-Hornung, Olga and Chen, Baoquan},\n    title = {Learning Skeletal Articulations with Neural Blend Shapes},\n    journal = {ACM Transactions on Graphics (TOG)},\n    volume = {40},\n    number = {4},\n    pages = {1},\n    year = {2021},\n    publisher = {ACM}\n    }\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.\n\n\n\n\nSupersedes 20211031-use-bpr-to-rank-skeleton-bone-names"
+    "text": "Provides insights into how a database system might perform under V-Sekai-like conditions.\nHelps optimize the balance between read and write operations.\nEnsures low latency for a seamless user experience."
   },
   {
-    "objectID": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#context-and-problem-statement",
-    "href": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#context-and-problem-statement",
-    "title": "Accepted: Rank skeleton #bone names with xgboost",
+    "objectID": "decisions/20240217-workload-benchmarking.html#downsides",
+    "href": "decisions/20240217-workload-benchmarking.html#downsides",
+    "title": "Proposed: for using workloads to emulate the usage patterns",
     "section": "",
-    "text": "Improve automatic #bone selection"
+    "text": "Requires careful tuning and understanding of YCSB workloads.\nThe benchmark results might not perfectly reflect real-world usage due to the synthetic nature of benchmarks."
   },
   {
-    "objectID": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Accepted: Rank skeleton #bone names with xgboost",
+    "objectID": "decisions/20240217-workload-benchmarking.html#the-road-not-taken",
+    "href": "decisions/20240217-workload-benchmarking.html#the-road-not-taken",
+    "title": "Proposed: for using workloads to emulate the usage patterns",
     "section": "",
-    "text": "Use xgboost to rank bones."
+    "text": "An alternative would be to use pre-defined YCSB workloads without customization. However, this might not accurately reflect V-Sekai’s specific usage patterns."
   },
   {
-    "objectID": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Accepted: Rank skeleton #bone names with xgboost",
+    "objectID": "decisions/20240217-workload-benchmarking.html#the-infrequent-use-case",
+    "href": "decisions/20240217-workload-benchmarking.html#the-infrequent-use-case",
+    "title": "Proposed: for using workloads to emulate the usage patterns",
     "section": "",
-    "text": "Investigate"
+    "text": "In scenarios where the usage patterns are not consistent or predictable, customizing the YCSB workload might not provide accurate insights."
   },
   {
-    "objectID": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#positive-consequences",
-    "href": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#positive-consequences",
-    "title": "Accepted: Rank skeleton #bone names with xgboost",
+    "objectID": "decisions/20240217-workload-benchmarking.html#in-core-and-done-by-us",
+    "href": "decisions/20240217-workload-benchmarking.html#in-core-and-done-by-us",
+    "title": "Proposed: for using workloads to emulate the usage patterns",
     "section": "",
-    "text": "We can guess the proper name.\nUseful for the facial mapping problem?\nUseful for the character generator slider recommendation problem?\nGenerate test data by moving the character\nInference requires only single pose inputs."
+    "text": "The setup and customization of the YCSB benchmark will be done by the V-Sekai development team with support from the community stakeholders."
   },
   {
-    "objectID": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#negative-consequences",
-    "href": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#negative-consequences",
-    "title": "Accepted: Rank skeleton #bone names with xgboost",
+    "objectID": "decisions/20240217-workload-benchmarking.html#status",
+    "href": "decisions/20240217-workload-benchmarking.html#status",
+    "title": "Proposed: for using workloads to emulate the usage patterns",
     "section": "",
-    "text": "Starring at the abyss."
+    "text": "Status: Rejected"
   },
   {
-    "objectID": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#option-graveyard",
-    "href": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#option-graveyard",
-    "title": "Accepted: Rank skeleton #bone names with xgboost",
+    "objectID": "decisions/20240217-workload-benchmarking.html#decision-makers",
+    "href": "decisions/20240217-workload-benchmarking.html#decision-makers",
+    "title": "Proposed: for using workloads to emulate the usage patterns",
     "section": "",
-    "text": "Option:\n\nbpr from Quora\n\nRejection Reason:\n\nBpr from Quora is not used in production.\n\nOption:\n\ndlrm from facebook\n\nRejection Reason:\n\nToo difficult to run\n\nOption:\n\ncatboost\n\nRejection Reason:\n\nToo difficult to run"
+    "text": "V-Sekai development team and community stakeholders."
   },
   {
-    "objectID": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Accepted: Rank skeleton #bone names with xgboost",
+    "objectID": "decisions/20240217-workload-benchmarking.html#tags",
+    "href": "decisions/20240217-workload-benchmarking.html#tags",
+    "title": "Proposed: for using workloads to emulate the usage patterns",
     "section": "",
-    "text": "Not a few lines of code."
+    "text": "V-Sekai, Performance Benchmarking, Database Optimization"
   },
   {
-    "objectID": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Accepted: Rank skeleton #bone names with xgboost",
+    "objectID": "decisions/20240217-workload-benchmarking.html#further-reading",
+    "href": "decisions/20240217-workload-benchmarking.html#further-reading",
+    "title": "Proposed: for using workloads to emulate the usage patterns",
     "section": "",
-    "text": "We need this to make the quality of life of creators better."
+    "text": "V-Sekai · GitHub\nV-Sekai/v-sekai-game\n\nThis proposal was assisted by Aria, an AI assistant."
   },
   {
-    "objectID": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#references",
-    "href": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#references",
-    "title": "Accepted: Rank skeleton #bone names with xgboost",
+    "objectID": "decisions/20230813-blender-runner-into-membrane-framework.html",
+    "href": "decisions/20230813-blender-runner-into-membrane-framework.html",
+    "title": "Proposed: Transitioning to Membrane Framework Pipelines with JSON-RPC Blender Runner",
     "section": "",
-    "text": "https://github.com/BayesWitnesses/m2cgen\nhttps://stackoverflow.com/questions/36071672/using-xgboost-in-c\nhttps://github.com/facebookresearch/dlrm\nhttps://medium.com/@marthawhite_81346/learning-with-the-criteo-tb-dataset-e3ec12d9d77e\nhttps://www.kaggle.com/c/criteo-display-ad-challenge/data\nSkeleton pool operator from neural blend shapes.\nhttps://tailor.fandom.com/wiki/Types_of_measurement\nhttps://knarkowicz.wordpress.com/2014/04/16/octahedron-normal-vector-encoding/\nhttps://www.kaggle.com/egordm/deep-learning-recommendation-model-dlrm\n\n    @article{li2021learning,\n    author = {Li, Peizhuo and Aberman, Kfir and Hanocka, Rana and Liu, Libin and Sorkine-Hornung, Olga and Chen, Baoquan},\n    title = {Learning Skeletal Articulations with Neural Blend Shapes},\n    journal = {ACM Transactions on Graphics (TOG)},\n    volume = {40},\n    number = {4},\n    pages = {1},\n    year = {2021},\n    publisher = {ACM}\n    }"
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, Elixir, Membrane Framework, Multiplayer Blender, JSON-RPC\n\n\n\n\nThe current solution for handling multiplayer Blender has its limitations when it comes to scalability and real-time performance. To address these issues, we propose a new approach that leverages Elixir and the Membrane Framework. This will involve rewriting the code and introducing a JSON-RPC Blender runner.\n\n\nIn this new approach, character posing will be handled in real-time and shared across multiple clients. This means that any changes made to a 3D model by one user will be immediately reflected on all other connected clients. This feature will enhance the collaborative experience and allow users to interact with the same 3D models simultaneously.\n\n\n\nThe state of the world, including objects, lighting, camera position, etc., will also be synchronized across all clients. This ensures that all users are experiencing the same environment, further enhancing the sense of immersion and collaboration.\n\n\n\nWe will introduce procedural generation techniques to create unique and dynamic environments. These generated worlds will be shared across all clients, ensuring that each user’s experience is not only immersive but also unique and engaging.\n\n\n\nAny drawings or annotations made using the Grease Pencil tool will be visible to all clients. This allows for collaborative sketching and planning, making it easier for teams to communicate their ideas visually.\n\n\n\nTo facilitate efficient communication with Blender, we’ll implement a JSON-RPC Blender runner. This will allow us to send commands to Blender and receive responses in a structured and standardized format. This feature will streamline the process of interacting with Blender, making it more efficient and user-friendly.\nBy implementing these features, we aim to improve the scalability and real-time performance of our multiplayer Blender solution. This will lead to a more immersive and collaborative experience for our users.\n\n\n\n\nThe main challenge is to translate the existing code into Elixir while maintaining the functionality and improving upon the limitations of the current system. This includes ensuring that the new code can handle larger volumes of users and provide real-time updates without lag or delay.\n\n\n\ngraph LR\n  A[Current Code] --&gt; B[Elixir & Membrane Framework Code]\n  C[No Authentication] --&gt; D[GitHub OAuth 2.0 Login]\n  E[No Database] --&gt; F[Khepri Database Library]\n  G[Blender Runner] --&gt; H[JSON-RPC Blender Runner]\n  I[Triangle Only] --&gt; J[Airlocks for Environment Translation]\nThis strategy leverages Elixir and the Membrane Framework’s unique features, uses the Khepri database library for data management, implements GitHub login using OAuth 2.0 protocol for single sign-on, introduces a JSON-RPC Blender runner for improved communication with Blender, and focuses on the use of triangles (a polygon with 3 vertices) and “Airlocks” for environment translation.\nHere are the key steps:\n\nCodebase: Transition from the current code to Elixir & Membrane Framework Code, tracked in a version control system.\nDependencies: Declare and isolate dependencies explicitly, avoiding reliance on system-wide packages.\nConfig: Store configuration (including GitHub OAuth 2.0 Login credentials) in the environment, not in the code.\nBacking Services: Replace in-memory data persistence with Khepri Database Library, attached as a backing service.\nBuild, Release, Run: Strictly separate these stages, facilitated by the Elixir & Membrane Framework Code.\nProcesses: Execute application as one or more stateless processes, storing needed state in the Khepri database.\nPort Binding: Export services via port binding, making the application self-contained.\nConcurrency: Scale out the application via the process model, allowing for handling increased load.\nDisposability: Aim for fast startup and graceful shutdown to maximize robustness.\nDev/Prod Parity: Keep development, staging, and production environments as similar as possible.\nLogs: Treat logs as event streams, handled by the executing environment.\nAdmin Processes: Run any needed one-off administrative tasks in an identical environment as the regular long-running processes of the app.\nBlender Runner: Implement a JSON-RPC Blender runner to facilitate efficient communication with Blender.\nTriangle Only: This principle ensures that only triangles (polygons with 3 vertices) are used in the graphical representation. This simplifies the rendering process and reduces computational complexity.\nAirlocks: Use airlocks to translate the remote environment to the local environment. This allows for seamless interaction between different parts of the system while maintaining isolation and security.\n\n\n\n\nBy rewriting the code in Elixir, using the Membrane Framework, implementing the Khepri database library, introducing a JSON-RPC Blender runner, focusing on the use of triangles, and employing the “Airlocks” principles, we can expect improved scalability and real-time performance. This will allow for more users to use the system simultaneously without experiencing delays or lags. Additionally, the fault-tolerance feature of Elixir will ensure that the system remains operational even when errors occur.\n\n\n\nRewriting the code will require time and resources. There may also be a learning curve for developers who are not familiar with Elixir, the Membrane Framework, the Khepri database library, JSON-RPC, the concept of using triangles in graphics, and “Airlocks”.\n\n\n\nAn alternative approach would have been to optimize the existing code instead of rewriting it. However, this would not have addressed the inherent limitations of the current system.\n\n\n\nIn cases where the number of users is low and real-time updates are not critical, the current system may still be sufficient. However, as the user base grows and the demand for real-time updates increases, the need for a more scalable and efficient system becomes apparent.\n\n\n\nYes, the rewriting of the code will indeed be done by us as we also maintain the backend services.\n\n\n\n\nV-Sekai\nElixir\nMembrane Framework\nKhepri Database Library\nJSON-RPC\n\nThis article is assisted by AI."
   },
   {
-    "objectID": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#derivative-license",
-    "href": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#derivative-license",
-    "title": "Accepted: Rank skeleton #bone names with xgboost",
+    "objectID": "decisions/20230813-blender-runner-into-membrane-framework.html#metadata",
+    "href": "decisions/20230813-blender-runner-into-membrane-framework.html#metadata",
+    "title": "Proposed: Transitioning to Membrane Framework Pipelines with JSON-RPC Blender Runner",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, Elixir, Membrane Framework, Multiplayer Blender, JSON-RPC"
   },
   {
-    "objectID": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#links",
-    "href": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#links",
-    "title": "Accepted: Rank skeleton #bone names with xgboost",
+    "objectID": "decisions/20230813-blender-runner-into-membrane-framework.html#backdrop",
+    "href": "decisions/20230813-blender-runner-into-membrane-framework.html#backdrop",
+    "title": "Proposed: Transitioning to Membrane Framework Pipelines with JSON-RPC Blender Runner",
     "section": "",
-    "text": "Supersedes 20211031-use-bpr-to-rank-skeleton-bone-names"
+    "text": "The current solution for handling multiplayer Blender has its limitations when it comes to scalability and real-time performance. To address these issues, we propose a new approach that leverages Elixir and the Membrane Framework. This will involve rewriting the code and introducing a JSON-RPC Blender runner.\n\n\nIn this new approach, character posing will be handled in real-time and shared across multiple clients. This means that any changes made to a 3D model by one user will be immediately reflected on all other connected clients. This feature will enhance the collaborative experience and allow users to interact with the same 3D models simultaneously.\n\n\n\nThe state of the world, including objects, lighting, camera position, etc., will also be synchronized across all clients. This ensures that all users are experiencing the same environment, further enhancing the sense of immersion and collaboration.\n\n\n\nWe will introduce procedural generation techniques to create unique and dynamic environments. These generated worlds will be shared across all clients, ensuring that each user’s experience is not only immersive but also unique and engaging.\n\n\n\nAny drawings or annotations made using the Grease Pencil tool will be visible to all clients. This allows for collaborative sketching and planning, making it easier for teams to communicate their ideas visually.\n\n\n\nTo facilitate efficient communication with Blender, we’ll implement a JSON-RPC Blender runner. This will allow us to send commands to Blender and receive responses in a structured and standardized format. This feature will streamline the process of interacting with Blender, making it more efficient and user-friendly.\nBy implementing these features, we aim to improve the scalability and real-time performance of our multiplayer Blender solution. This will lead to a more immersive and collaborative experience for our users."
   },
   {
-    "objectID": "decisions/20231026-blender-steam-beta-version.html",
-    "href": "decisions/20231026-blender-steam-beta-version.html",
-    "title": "Proposed: Solve Blender versions by locking LTS versions on Blender (3.6)",
+    "objectID": "decisions/20230813-blender-runner-into-membrane-framework.html#the-challenge",
+    "href": "decisions/20230813-blender-runner-into-membrane-framework.html#the-challenge",
+    "title": "Proposed: Transitioning to Membrane Framework Pipelines with JSON-RPC Blender Runner",
     "section": "",
-    "text": "Status: Proposed \nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nConstantly changing blender versions is a problem for blender import\n\n\n\nWe want to pin the blender version.\n\n\n\nPin the blender version to the steam version of LTS Blender – Blender (3.6)\n\n\n\nWe get the fast upgrades of steam and the pinning requirement satisfied.\n\n\n\nDependent on steam.\n\n\n\nDownload a version of Blender directly.\n\n\n\nAsk someone to use blender for you.\n\n\n\nThis is a staff note.\n\n\n\n\nV-Sekai\nAI assists this article.\nhttps://www.blender.org/\nhttps://store.steampowered.com/"
+    "text": "The main challenge is to translate the existing code into Elixir while maintaining the functionality and improving upon the limitations of the current system. This includes ensuring that the new code can handle larger volumes of users and provide real-time updates without lag or delay."
   },
   {
-    "objectID": "decisions/20231026-blender-steam-beta-version.html#metadata",
-    "href": "decisions/20231026-blender-steam-beta-version.html#metadata",
-    "title": "Proposed: Solve Blender versions by locking LTS versions on Blender (3.6)",
+    "objectID": "decisions/20230813-blender-runner-into-membrane-framework.html#strategy",
+    "href": "decisions/20230813-blender-runner-into-membrane-framework.html#strategy",
+    "title": "Proposed: Transitioning to Membrane Framework Pipelines with JSON-RPC Blender Runner",
     "section": "",
-    "text": "Status: Proposed \nDeciders: V-Sekai\nTags: V-Sekai"
+    "text": "graph LR\n  A[Current Code] --&gt; B[Elixir & Membrane Framework Code]\n  C[No Authentication] --&gt; D[GitHub OAuth 2.0 Login]\n  E[No Database] --&gt; F[Khepri Database Library]\n  G[Blender Runner] --&gt; H[JSON-RPC Blender Runner]\n  I[Triangle Only] --&gt; J[Airlocks for Environment Translation]\nThis strategy leverages Elixir and the Membrane Framework’s unique features, uses the Khepri database library for data management, implements GitHub login using OAuth 2.0 protocol for single sign-on, introduces a JSON-RPC Blender runner for improved communication with Blender, and focuses on the use of triangles (a polygon with 3 vertices) and “Airlocks” for environment translation.\nHere are the key steps:\n\nCodebase: Transition from the current code to Elixir & Membrane Framework Code, tracked in a version control system.\nDependencies: Declare and isolate dependencies explicitly, avoiding reliance on system-wide packages.\nConfig: Store configuration (including GitHub OAuth 2.0 Login credentials) in the environment, not in the code.\nBacking Services: Replace in-memory data persistence with Khepri Database Library, attached as a backing service.\nBuild, Release, Run: Strictly separate these stages, facilitated by the Elixir & Membrane Framework Code.\nProcesses: Execute application as one or more stateless processes, storing needed state in the Khepri database.\nPort Binding: Export services via port binding, making the application self-contained.\nConcurrency: Scale out the application via the process model, allowing for handling increased load.\nDisposability: Aim for fast startup and graceful shutdown to maximize robustness.\nDev/Prod Parity: Keep development, staging, and production environments as similar as possible.\nLogs: Treat logs as event streams, handled by the executing environment.\nAdmin Processes: Run any needed one-off administrative tasks in an identical environment as the regular long-running processes of the app.\nBlender Runner: Implement a JSON-RPC Blender runner to facilitate efficient communication with Blender.\nTriangle Only: This principle ensures that only triangles (polygons with 3 vertices) are used in the graphical representation. This simplifies the rendering process and reduces computational complexity.\nAirlocks: Use airlocks to translate the remote environment to the local environment. This allows for seamless interaction between different parts of the system while maintaining isolation and security."
   },
   {
-    "objectID": "decisions/20231026-blender-steam-beta-version.html#the-backdrop",
-    "href": "decisions/20231026-blender-steam-beta-version.html#the-backdrop",
-    "title": "Proposed: Solve Blender versions by locking LTS versions on Blender (3.6)",
+    "objectID": "decisions/20230813-blender-runner-into-membrane-framework.html#the-upside",
+    "href": "decisions/20230813-blender-runner-into-membrane-framework.html#the-upside",
+    "title": "Proposed: Transitioning to Membrane Framework Pipelines with JSON-RPC Blender Runner",
     "section": "",
-    "text": "Constantly changing blender versions is a problem for blender import"
+    "text": "By rewriting the code in Elixir, using the Membrane Framework, implementing the Khepri database library, introducing a JSON-RPC Blender runner, focusing on the use of triangles, and employing the “Airlocks” principles, we can expect improved scalability and real-time performance. This will allow for more users to use the system simultaneously without experiencing delays or lags. Additionally, the fault-tolerance feature of Elixir will ensure that the system remains operational even when errors occur."
   },
   {
-    "objectID": "decisions/20231026-blender-steam-beta-version.html#the-challenge",
-    "href": "decisions/20231026-blender-steam-beta-version.html#the-challenge",
-    "title": "Proposed: Solve Blender versions by locking LTS versions on Blender (3.6)",
+    "objectID": "decisions/20230813-blender-runner-into-membrane-framework.html#the-downside",
+    "href": "decisions/20230813-blender-runner-into-membrane-framework.html#the-downside",
+    "title": "Proposed: Transitioning to Membrane Framework Pipelines with JSON-RPC Blender Runner",
     "section": "",
-    "text": "We want to pin the blender version."
+    "text": "Rewriting the code will require time and resources. There may also be a learning curve for developers who are not familiar with Elixir, the Membrane Framework, the Khepri database library, JSON-RPC, the concept of using triangles in graphics, and “Airlocks”."
   },
   {
-    "objectID": "decisions/20231026-blender-steam-beta-version.html#the-strategy",
-    "href": "decisions/20231026-blender-steam-beta-version.html#the-strategy",
-    "title": "Proposed: Solve Blender versions by locking LTS versions on Blender (3.6)",
+    "objectID": "decisions/20230813-blender-runner-into-membrane-framework.html#the-road-not-taken",
+    "href": "decisions/20230813-blender-runner-into-membrane-framework.html#the-road-not-taken",
+    "title": "Proposed: Transitioning to Membrane Framework Pipelines with JSON-RPC Blender Runner",
     "section": "",
-    "text": "Pin the blender version to the steam version of LTS Blender – Blender (3.6)"
+    "text": "An alternative approach would have been to optimize the existing code instead of rewriting it. However, this would not have addressed the inherent limitations of the current system."
   },
   {
-    "objectID": "decisions/20231026-blender-steam-beta-version.html#the-upside",
-    "href": "decisions/20231026-blender-steam-beta-version.html#the-upside",
-    "title": "Proposed: Solve Blender versions by locking LTS versions on Blender (3.6)",
+    "objectID": "decisions/20230813-blender-runner-into-membrane-framework.html#the-infrequent-use-case",
+    "href": "decisions/20230813-blender-runner-into-membrane-framework.html#the-infrequent-use-case",
+    "title": "Proposed: Transitioning to Membrane Framework Pipelines with JSON-RPC Blender Runner",
     "section": "",
-    "text": "We get the fast upgrades of steam and the pinning requirement satisfied."
+    "text": "In cases where the number of users is low and real-time updates are not critical, the current system may still be sufficient. However, as the user base grows and the demand for real-time updates increases, the need for a more scalable and efficient system becomes apparent."
   },
   {
-    "objectID": "decisions/20231026-blender-steam-beta-version.html#the-downside",
-    "href": "decisions/20231026-blender-steam-beta-version.html#the-downside",
-    "title": "Proposed: Solve Blender versions by locking LTS versions on Blender (3.6)",
+    "objectID": "decisions/20230813-blender-runner-into-membrane-framework.html#in-core-and-done-by-us",
+    "href": "decisions/20230813-blender-runner-into-membrane-framework.html#in-core-and-done-by-us",
+    "title": "Proposed: Transitioning to Membrane Framework Pipelines with JSON-RPC Blender Runner",
     "section": "",
-    "text": "Dependent on steam."
+    "text": "Yes, the rewriting of the code will indeed be done by us as we also maintain the backend services."
   },
   {
-    "objectID": "decisions/20231026-blender-steam-beta-version.html#the-road-not-taken",
-    "href": "decisions/20231026-blender-steam-beta-version.html#the-road-not-taken",
-    "title": "Proposed: Solve Blender versions by locking LTS versions on Blender (3.6)",
+    "objectID": "decisions/20230813-blender-runner-into-membrane-framework.html#further-reading",
+    "href": "decisions/20230813-blender-runner-into-membrane-framework.html#further-reading",
+    "title": "Proposed: Transitioning to Membrane Framework Pipelines with JSON-RPC Blender Runner",
     "section": "",
-    "text": "Download a version of Blender directly."
+    "text": "V-Sekai\nElixir\nMembrane Framework\nKhepri Database Library\nJSON-RPC\n\nThis article is assisted by AI."
   },
   {
-    "objectID": "decisions/20231026-blender-steam-beta-version.html#the-infrequent-use-case",
-    "href": "decisions/20231026-blender-steam-beta-version.html#the-infrequent-use-case",
-    "title": "Proposed: Solve Blender versions by locking LTS versions on Blender (3.6)",
+    "objectID": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html",
+    "href": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html",
+    "title": "Accepted: Degrade V-Sekai’s networking model to work in 2d and with webrtc.",
     "section": "",
-    "text": "Ask someone to use blender for you."
+    "text": "Status: accepted \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nMake V-Sekai Godot work in 2D and on the web.\n\n\n\nDegrade the V-Sekai networking model.\n\n\n\n\nThe networking system exclusively uses the MultiplayerAPI, which by default is implemented via ENet, so one would have to swap that part with the WebRTC equivalent. Convert the ENet module to use WebRTC\n\n\n\n\n\nWorks in Opengl Godot 4\nWorks on the web with webrtc\nCan disable 3D for size.\n\n\n\n\n\n[e.g., compromising quality attribute, follow-up decisions required, …]\n\n[this section can be repeated for each option if more than one option is open for consideration]\n\n\n\n\nOption: \nRejection Reason: \n\n\n\n\nNot a few lines of gdscript.\n\n\n\nThis is core.\n\n\n\n\nLink type \n\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20231026-blender-steam-beta-version.html#in-core-and-done-by-us",
-    "href": "decisions/20231026-blender-steam-beta-version.html#in-core-and-done-by-us",
-    "title": "Proposed: Solve Blender versions by locking LTS versions on Blender (3.6)",
+    "objectID": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html#context-and-problem-statement",
+    "href": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html#context-and-problem-statement",
+    "title": "Accepted: Degrade V-Sekai’s networking model to work in 2d and with webrtc.",
     "section": "",
-    "text": "This is a staff note."
+    "text": "Make V-Sekai Godot work in 2D and on the web."
   },
   {
-    "objectID": "decisions/20231026-blender-steam-beta-version.html#further-reading",
-    "href": "decisions/20231026-blender-steam-beta-version.html#further-reading",
-    "title": "Proposed: Solve Blender versions by locking LTS versions on Blender (3.6)",
+    "objectID": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Accepted: Degrade V-Sekai’s networking model to work in 2d and with webrtc.",
     "section": "",
-    "text": "V-Sekai\nAI assists this article.\nhttps://www.blender.org/\nhttps://store.steampowered.com/"
+    "text": "Degrade the V-Sekai networking model."
   },
   {
-    "objectID": "decisions/20221205-moving-fast-philosophy-development.html",
-    "href": "decisions/20221205-moving-fast-philosophy-development.html",
-    "title": "Proposed: Move fast without breaking things for V-Sekai",
+    "objectID": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Accepted: Degrade V-Sekai’s networking model to work in 2d and with webrtc.",
     "section": "",
-    "text": "Status: proposed \nDeciders: V-Sekai,fire,\nTags: V-Sekai,\n\n\n\nWe want to discover ways to move faster.\n\n\n\nWe want to discover ways to move faster and last longer.\n\n\n\nPrototype quickly and be adaptive to change.\nWe use continuous integration and continuous deployment.\nWe record our decisions in documentation.\n\n\n\nWe improve our processes.\n\n\n\nProcesses become dead weight.\n\n\n\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\n\nThis is not code but a workflow document.\n\n\n\nWe work on V-Sekai.\n\n\n\n\nV-Sekai\n\n\n\n\nMIT License\n\nCopyright (c) 2018-2022 SaracenOne\nCopyright (c) 2019-2022 K. S. Ernest (iFire) Lee (fire)\nCopyright (c) 2020-2022 Lyuma\nCopyright (c) 2020-2022 MMMaellon\nCopyright (c) 2022 V-Sekai Contributors\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
+    "text": "The networking system exclusively uses the MultiplayerAPI, which by default is implemented via ENet, so one would have to swap that part with the WebRTC equivalent. Convert the ENet module to use WebRTC"
   },
   {
-    "objectID": "decisions/20221205-moving-fast-philosophy-development.html#context-and-problem-statement",
-    "href": "decisions/20221205-moving-fast-philosophy-development.html#context-and-problem-statement",
-    "title": "Proposed: Move fast without breaking things for V-Sekai",
+    "objectID": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html#positive-consequences",
+    "href": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html#positive-consequences",
+    "title": "Accepted: Degrade V-Sekai’s networking model to work in 2d and with webrtc.",
     "section": "",
-    "text": "We want to discover ways to move faster."
+    "text": "Works in Opengl Godot 4\nWorks on the web with webrtc\nCan disable 3D for size."
   },
   {
-    "objectID": "decisions/20221205-moving-fast-philosophy-development.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20221205-moving-fast-philosophy-development.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: Move fast without breaking things for V-Sekai",
+    "objectID": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html#negative-consequences",
+    "href": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html#negative-consequences",
+    "title": "Accepted: Degrade V-Sekai’s networking model to work in 2d and with webrtc.",
     "section": "",
-    "text": "We want to discover ways to move faster and last longer."
+    "text": "[e.g., compromising quality attribute, follow-up decisions required, …]\n\n[this section can be repeated for each option if more than one option is open for consideration]"
   },
   {
-    "objectID": "decisions/20221205-moving-fast-philosophy-development.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20221205-moving-fast-philosophy-development.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Move fast without breaking things for V-Sekai",
+    "objectID": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html#option-graveyard",
+    "href": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html#option-graveyard",
+    "title": "Accepted: Degrade V-Sekai’s networking model to work in 2d and with webrtc.",
     "section": "",
-    "text": "Prototype quickly and be adaptive to change.\nWe use continuous integration and continuous deployment.\nWe record our decisions in documentation."
+    "text": "Option: \nRejection Reason:"
   },
   {
-    "objectID": "decisions/20221205-moving-fast-philosophy-development.html#positive-consequences",
-    "href": "decisions/20221205-moving-fast-philosophy-development.html#positive-consequences",
-    "title": "Proposed: Move fast without breaking things for V-Sekai",
+    "objectID": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Accepted: Degrade V-Sekai’s networking model to work in 2d and with webrtc.",
     "section": "",
-    "text": "We improve our processes."
+    "text": "Not a few lines of gdscript."
   },
   {
-    "objectID": "decisions/20221205-moving-fast-philosophy-development.html#negative-consequences",
-    "href": "decisions/20221205-moving-fast-philosophy-development.html#negative-consequences",
-    "title": "Proposed: Move fast without breaking things for V-Sekai",
+    "objectID": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Accepted: Degrade V-Sekai’s networking model to work in 2d and with webrtc.",
     "section": "",
-    "text": "Processes become dead weight."
+    "text": "This is core."
   },
   {
-    "objectID": "decisions/20221205-moving-fast-philosophy-development.html#option-graveyard",
-    "href": "decisions/20221205-moving-fast-philosophy-development.html#option-graveyard",
-    "title": "Proposed: Move fast without breaking things for V-Sekai",
+    "objectID": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html#references",
+    "href": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html#references",
+    "title": "Accepted: Degrade V-Sekai’s networking model to work in 2d and with webrtc.",
     "section": "",
-    "text": "Option: The status quo. \nRejection Reason: This solves nothing."
+    "text": "Link type"
   },
   {
-    "objectID": "decisions/20221205-moving-fast-philosophy-development.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20221205-moving-fast-philosophy-development.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Move fast without breaking things for V-Sekai",
+    "objectID": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html#derivative-license",
+    "href": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html#derivative-license",
+    "title": "Accepted: Degrade V-Sekai’s networking model to work in 2d and with webrtc.",
     "section": "",
-    "text": "This is not code but a workflow document."
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20221205-moving-fast-philosophy-development.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20221205-moving-fast-philosophy-development.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Move fast without breaking things for V-Sekai",
+    "objectID": "decisions/20240111-fspy.html",
+    "href": "decisions/20240111-fspy.html",
+    "title": "Proposed: Camera matching with fSpy.",
     "section": "",
-    "text": "We work on V-Sekai."
+    "text": "Status: Proposed \nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nV-Sekai’s mission to be gateways to 3D environments needs camera matching, which is currently a bottleneck in our workflow.\n\n\n\nOur artists and developers need to align concept screenshots within the 3D spaces due to inconsistent camera parameter estimation.\n\n\n\nWe will adopt the fSpy tool that uses vanishing points to estimate camera parameters from images, facilitating a more precise camera match-moving process.\n\n\n\nFind parallel lines and use the longest lines you can.\nYou can move the axes to recenter.\n\n\n\n\n\nThe integration of fSpy into our workflow promises:\n\nA considerable reduction in time for setting up camera parameters.\nEnhanced accuracy and realism in matching 3D models with background images.\nStreamlined asset creation processes, thereby supporting quick iterations.\n\n\n\n\nSome challenges associated with this strategy include:\n\nAn initial learning phase required for effective use of the fSpy tool.\nPotential limitations in images that lack well-defined perspective lines or geometric structure.\nReliance on an external tool which may necessitate ongoing maintenance efforts.\n\n\n\n\nRather than using fSpy, we could continue manual estimation techniques or even develop a custom solution tailored to our specific requirements—both are valid but likely less efficient approaches.\n\n\n\nFor cases where fSpy struggles due to images with no clear vanishing points, alternative methods of camera estimation must be devised, potentially falling back on manual techniques or other specialized tools.\n\n\n\nfSpy integration should become central to our asset creation pipeline. We’ll need to invest in training and potentially develop complementary in-house tools to bridge the gap between fSpy outputs and our existing systems.\n\n\n\n\nV-Sekai GitHub Repository - Explore how V-Sekai leverages social VR functions within Godot Engine.\nV-Sekai Game Project - Delve into the collaborative effort of creating social VR/VRSNS/metaverse elements, all open-source and accessible.\n\nAI assistant Aria assisted with this proposal."
   },
   {
-    "objectID": "decisions/20221205-moving-fast-philosophy-development.html#references",
-    "href": "decisions/20221205-moving-fast-philosophy-development.html#references",
-    "title": "Proposed: Move fast without breaking things for V-Sekai",
+    "objectID": "decisions/20240111-fspy.html#metadata",
+    "href": "decisions/20240111-fspy.html#metadata",
+    "title": "Proposed: Camera matching with fSpy.",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Status: Proposed \nDeciders: V-Sekai\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20221205-moving-fast-philosophy-development.html#license-of-the-contribution",
-    "href": "decisions/20221205-moving-fast-philosophy-development.html#license-of-the-contribution",
-    "title": "Proposed: Move fast without breaking things for V-Sekai",
+    "objectID": "decisions/20240111-fspy.html#the-backdrop",
+    "href": "decisions/20240111-fspy.html#the-backdrop",
+    "title": "Proposed: Camera matching with fSpy.",
     "section": "",
-    "text": "MIT License\n\nCopyright (c) 2018-2022 SaracenOne\nCopyright (c) 2019-2022 K. S. Ernest (iFire) Lee (fire)\nCopyright (c) 2020-2022 Lyuma\nCopyright (c) 2020-2022 MMMaellon\nCopyright (c) 2022 V-Sekai Contributors\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
+    "text": "V-Sekai’s mission to be gateways to 3D environments needs camera matching, which is currently a bottleneck in our workflow."
   },
   {
-    "objectID": "decisions/20220830-godot-pdf-workflow.html",
-    "href": "decisions/20220830-godot-pdf-workflow.html",
-    "title": "Proposed: Provide pdf reading",
+    "objectID": "decisions/20240111-fspy.html#the-challenge",
+    "href": "decisions/20240111-fspy.html#the-challenge",
+    "title": "Proposed: Camera matching with fSpy.",
     "section": "",
-    "text": "Proposed: Provide pdf reading\n\nContext and Problem Statement\nProvide a workflow to read pdf documents.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nWe want to provide pdf reading without implementing a pdf reader.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\n\nConvert pdf into a series of svgs (raster + vector)\nPut svgs in a folder\nClean with https://github.com/RazrFalcon/svgcleaner\nUse godot engine 4’s thorvg\n\n\n\nPositive Consequences\nCan import artwork.\n\n\nNegative Consequences\nNot a real pdf viewer.\n\n\nOption graveyard\nDo nothing.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nA few lines of cli.\n\n\nIs there a reason why this should be core and done by us?\nWanted to write the workflow down.\n\n\nReferences\n\nV-Sekai\n\n\n\nLicense of the contribution\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Our artists and developers need to align concept screenshots within the 3D spaces due to inconsistent camera parameter estimation."
   },
   {
-    "objectID": "decisions/20231209-appium-testing-win11.html",
-    "href": "decisions/20231209-appium-testing-win11.html",
-    "title": "Proposed: Automating Game Testing Process Using Appium 2",
+    "objectID": "decisions/20240111-fspy.html#the-strategy",
+    "href": "decisions/20240111-fspy.html#the-strategy",
+    "title": "Proposed: Camera matching with fSpy.",
     "section": "",
-    "text": "Status: Draft\nDeciders: V-Sekai, fire\nTags: V-Sekai\n\n\n\n\nIn the field of game development, it’s crucial to provide a seamless user experience across various platforms. This requires the implementation of effective testing methodologies.\n\n\n\nOur primary challenge is automating the testing process using Appium. A significant part of this strategy involves converting FBX files, which are commonly used formats for 3D models and animations, into GLB format.\n\n\n\n\n\n\nInstall the Appium server on the Mac using sudo npm install -g appium. Make sure Node.js version 12 or higher is installed.\nLaunch the server using the appium command.\nUse appium driver list and appium driver update [driverName]. For iOS, install drivers with appium driver install xcuitest and install appium driver install xcuitest\nInstall plugins with appium plugin install [pluginName] and integrate them using appium --use-plugins=[appiumPlugin].\nInstall all the plugins\n\nappium plugin install execute-driver\nappium plugin install images\nappium plugin install universal-xml\nappium plugin install relaxed-caps\n\n\n\n\nInstall scoop npm.\n\nscoop install sudo\n# sudo scoop install tailscale # optional\nscoop install nodejs\n\nOn Windows, install the Appium client using Node Package Manager (NPM) with the command npm install -g appium.\nForce Install https://github.com/microsoft/WinAppDriver/releases/download/v1.2.1/WindowsApplicationDriver_1.2.1.msi\nUse appium driver list and appium driver update [driverName]. For Windows, install drivers with appium driver install --source=npm appium-windows-driver\nInstall all the plugins\n\nappium plugin install execute-driver\nappium plugin install images\nappium plugin install universal-xml\nappium plugin install relaxed-caps\n\nRun appium --use-plugins \"execute-driver,images,universal-xml,relaxed-caps\"\n\nEnsure that the network settings and firewall configurations on both the Windows client and the Mac server are compatible for seamless communication.\n\n\n\n\nThe proposed strategy will ensure a high-quality gaming experience by automating the testing process. It will also save time and resources by reducing manual testing efforts.\n\n\n\nThe implementation of this strategy may require substantial resources and could potentially present unforeseen challenges. Additionally, there might be compatibility issues between different versions of Appium and the operating systems.\n\n\n\nWe have considered other testing frameworks, but our proposed strategy with Appium offers the best balance between effectiveness and efficiency.\n\n\n\nOur strategy might not cover infrequent or edge cases in game development. However, these will be identified and addressed as they arise.\n\n\n\nYes, this strategy is core to our project and will be implemented by our team.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAssisted by Aria, an AI assistant."
+    "text": "We will adopt the fSpy tool that uses vanishing points to estimate camera parameters from images, facilitating a more precise camera match-moving process.\n\n\n\nFind parallel lines and use the longest lines you can.\nYou can move the axes to recenter."
   },
   {
-    "objectID": "decisions/20231209-appium-testing-win11.html#metadata",
-    "href": "decisions/20231209-appium-testing-win11.html#metadata",
-    "title": "Proposed: Automating Game Testing Process Using Appium 2",
+    "objectID": "decisions/20240111-fspy.html#the-upside",
+    "href": "decisions/20240111-fspy.html#the-upside",
+    "title": "Proposed: Camera matching with fSpy.",
     "section": "",
-    "text": "Status: Draft\nDeciders: V-Sekai, fire\nTags: V-Sekai"
+    "text": "The integration of fSpy into our workflow promises:\n\nA considerable reduction in time for setting up camera parameters.\nEnhanced accuracy and realism in matching 3D models with background images.\nStreamlined asset creation processes, thereby supporting quick iterations."
   },
   {
-    "objectID": "decisions/20231209-appium-testing-win11.html#context",
-    "href": "decisions/20231209-appium-testing-win11.html#context",
-    "title": "Proposed: Automating Game Testing Process Using Appium 2",
+    "objectID": "decisions/20240111-fspy.html#the-downside",
+    "href": "decisions/20240111-fspy.html#the-downside",
+    "title": "Proposed: Camera matching with fSpy.",
     "section": "",
-    "text": "In the field of game development, it’s crucial to provide a seamless user experience across various platforms. This requires the implementation of effective testing methodologies."
+    "text": "Some challenges associated with this strategy include:\n\nAn initial learning phase required for effective use of the fSpy tool.\nPotential limitations in images that lack well-defined perspective lines or geometric structure.\nReliance on an external tool which may necessitate ongoing maintenance efforts."
   },
   {
-    "objectID": "decisions/20231209-appium-testing-win11.html#problem",
-    "href": "decisions/20231209-appium-testing-win11.html#problem",
-    "title": "Proposed: Automating Game Testing Process Using Appium 2",
+    "objectID": "decisions/20240111-fspy.html#the-road-not-taken",
+    "href": "decisions/20240111-fspy.html#the-road-not-taken",
+    "title": "Proposed: Camera matching with fSpy.",
     "section": "",
-    "text": "Our primary challenge is automating the testing process using Appium. A significant part of this strategy involves converting FBX files, which are commonly used formats for 3D models and animations, into GLB format."
+    "text": "Rather than using fSpy, we could continue manual estimation techniques or even develop a custom solution tailored to our specific requirements—both are valid but likely less efficient approaches."
   },
   {
-    "objectID": "decisions/20231209-appium-testing-win11.html#solution",
-    "href": "decisions/20231209-appium-testing-win11.html#solution",
-    "title": "Proposed: Automating Game Testing Process Using Appium 2",
+    "objectID": "decisions/20240111-fspy.html#the-infrequent-use-case",
+    "href": "decisions/20240111-fspy.html#the-infrequent-use-case",
+    "title": "Proposed: Camera matching with fSpy.",
     "section": "",
-    "text": "Install the Appium server on the Mac using sudo npm install -g appium. Make sure Node.js version 12 or higher is installed.\nLaunch the server using the appium command.\nUse appium driver list and appium driver update [driverName]. For iOS, install drivers with appium driver install xcuitest and install appium driver install xcuitest\nInstall plugins with appium plugin install [pluginName] and integrate them using appium --use-plugins=[appiumPlugin].\nInstall all the plugins\n\nappium plugin install execute-driver\nappium plugin install images\nappium plugin install universal-xml\nappium plugin install relaxed-caps\n\n\n\n\nInstall scoop npm.\n\nscoop install sudo\n# sudo scoop install tailscale # optional\nscoop install nodejs\n\nOn Windows, install the Appium client using Node Package Manager (NPM) with the command npm install -g appium.\nForce Install https://github.com/microsoft/WinAppDriver/releases/download/v1.2.1/WindowsApplicationDriver_1.2.1.msi\nUse appium driver list and appium driver update [driverName]. For Windows, install drivers with appium driver install --source=npm appium-windows-driver\nInstall all the plugins\n\nappium plugin install execute-driver\nappium plugin install images\nappium plugin install universal-xml\nappium plugin install relaxed-caps\n\nRun appium --use-plugins \"execute-driver,images,universal-xml,relaxed-caps\"\n\nEnsure that the network settings and firewall configurations on both the Windows client and the Mac server are compatible for seamless communication."
+    "text": "For cases where fSpy struggles due to images with no clear vanishing points, alternative methods of camera estimation must be devised, potentially falling back on manual techniques or other specialized tools."
   },
   {
-    "objectID": "decisions/20231209-appium-testing-win11.html#benefits",
-    "href": "decisions/20231209-appium-testing-win11.html#benefits",
-    "title": "Proposed: Automating Game Testing Process Using Appium 2",
+    "objectID": "decisions/20240111-fspy.html#in-core-and-done-by-us",
+    "href": "decisions/20240111-fspy.html#in-core-and-done-by-us",
+    "title": "Proposed: Camera matching with fSpy.",
     "section": "",
-    "text": "The proposed strategy will ensure a high-quality gaming experience by automating the testing process. It will also save time and resources by reducing manual testing efforts."
+    "text": "fSpy integration should become central to our asset creation pipeline. We’ll need to invest in training and potentially develop complementary in-house tools to bridge the gap between fSpy outputs and our existing systems."
   },
   {
-    "objectID": "decisions/20231209-appium-testing-win11.html#risks",
-    "href": "decisions/20231209-appium-testing-win11.html#risks",
-    "title": "Proposed: Automating Game Testing Process Using Appium 2",
+    "objectID": "decisions/20240111-fspy.html#further-reading",
+    "href": "decisions/20240111-fspy.html#further-reading",
+    "title": "Proposed: Camera matching with fSpy.",
     "section": "",
-    "text": "The implementation of this strategy may require substantial resources and could potentially present unforeseen challenges. Additionally, there might be compatibility issues between different versions of Appium and the operating systems."
+    "text": "V-Sekai GitHub Repository - Explore how V-Sekai leverages social VR functions within Godot Engine.\nV-Sekai Game Project - Delve into the collaborative effort of creating social VR/VRSNS/metaverse elements, all open-source and accessible.\n\nAI assistant Aria assisted with this proposal."
   },
   {
-    "objectID": "decisions/20231209-appium-testing-win11.html#alternatives",
-    "href": "decisions/20231209-appium-testing-win11.html#alternatives",
-    "title": "Proposed: Automating Game Testing Process Using Appium 2",
+    "objectID": "decisions/20231125-v-sekai-report.html",
+    "href": "decisions/20231125-v-sekai-report.html",
+    "title": "Superseded: V-Sekai 2023-11-25 Report",
     "section": "",
-    "text": "We have considered other testing frameworks, but our proposed strategy with Appium offers the best balance between effectiveness and efficiency."
+    "text": "Status: Superseded by 20231126-v-sekai-report.md\nDeciders: V-Sekai, fire, PLYSHKA🐧, SaracenOne\nTags: V-Sekai, Linux, Bug Fix, Godot Engine, User Support\n\n\n\n\nV-Sekai, pronounced vee-say-kai, is a collective of developers passionate about creating open-source VR technology. We aim to contribute to social VR and provide alternatives to proprietary engines like Unity and Unreal.\nDespite challenges, we’ve grown into a global community committed to advancing open standards and open-source software for virtual worlds.\nOur strategy focuses on providing comprehensive documentation and support to help users understand the platform better. We’re also committed to investigating and resolving issues like the reported Linux build problem.\n\n\n\nOver the past month, our team has been deeply involved in the Godot Engine conference in Munich, Germany. Our primary responsibility during this period has been to prepare for the upcoming launch of Godot Engine 4.2, to which we are contributing as part of the animation and 3D pipeline teams.\nPLYSHKA🐧 asked on our Discord about the current state of V-Sekai:\n\nPLYSHKA🐧&gt; I’m fairly new to this platform overall, can someone explain in what state its currently in? What can it do and what can’t? I couldn’t launch Linux build properly (black screen), and when started from terminal it just opened Godot editor (it was game binary), so not sure what’s happening there, maybe I don’t understand something\n\n\n\n\nWhat state is V-Sekai in, and what can it do?\n\n\n\n\n\n\nDesktop Mode Loading: V-Sekai is currently unable to load in desktop mode.\nThe purple screen on the desktop: The black screen issue seems related to our current problem of Issue #341\nMultiplayer Voice Chat: The multiplayer voice chat feature in V-Sekai is broken.\n\n\n\n\n\nMenu Editing: In V-Sekai, menus can’t be edited in VR. They can only be edited on the desktop before entering a game.\nDefault Avatar: V-Sekai does not have a default avatar. This causes confusion as players load in with an error avatar.\nDefault Avatar IK: V-Sekai’s default ik is currently twisted incorrectly.\n\n\n\n\n\nAvatar Uploading and Downloading:** V-Sekai can upload from the editor and, download avatars, and load them into the game at runtime.\nWorld Uploading and Downloading:** V-Sekai can upload from the editor and, download worlds, and load them into the game at runtime.\nVR Mode Loading: V-Sekai can successfully load in VR mode.\n\n\n\n\n\nContributions: V-Sekai is actively looking for more contributions.\n\n\n\n\n\nFire is set to merge ufbx, freeing the industry-standard FBX file format from the Autodesk ecosystem for V-Sekai. However, due to limited funding, we won’t be able to implement the upcoming 3D format standard USDZ in next months.\n\n\n\n\n\n\n\nWeek Starting\nTask\n\n\n\n\nNovember 26th, 2023\nInvestigate and resolve “purple screen” bug in V-Sekai.\n\n\nDecember 3rd, 2023\nInitiate the merging of godot-ufbx in Godot Engine 4.3.\n\n\n\n\n\n\nPros:\nAddressing these challenges can enhance the user experience, boost platform adoption, and collect crucial feedback for subsequent development.\nCons:\nThere may be underlying issues causing the Linux build problem that could take significant time and resources to resolve.\n\n\n\nAn alternative approach could have been to ignore the user’s query and continue with the current development roadmap. However, this would not foster a supportive community or encourage user engagement.\n\n\n\nWhile most users may not encounter the same issue as PLYSHKA🐧, addressing even infrequent use cases is essential to ensure a robust and user-friendly platform.\n\n\n\nAddressing this issue falls within our core responsibilities as the V-Sekai development team.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20231209-appium-testing-win11.html#limitations",
-    "href": "decisions/20231209-appium-testing-win11.html#limitations",
-    "title": "Proposed: Automating Game Testing Process Using Appium 2",
+    "objectID": "decisions/20231125-v-sekai-report.html#metadata",
+    "href": "decisions/20231125-v-sekai-report.html#metadata",
+    "title": "Superseded: V-Sekai 2023-11-25 Report",
     "section": "",
-    "text": "Our strategy might not cover infrequent or edge cases in game development. However, these will be identified and addressed as they arise."
+    "text": "Status: Superseded by 20231126-v-sekai-report.md\nDeciders: V-Sekai, fire, PLYSHKA🐧, SaracenOne\nTags: V-Sekai, Linux, Bug Fix, Godot Engine, User Support"
   },
   {
-    "objectID": "decisions/20231209-appium-testing-win11.html#ownership",
-    "href": "decisions/20231209-appium-testing-win11.html#ownership",
-    "title": "Proposed: Automating Game Testing Process Using Appium 2",
+    "objectID": "decisions/20231125-v-sekai-report.html#what-is-v-sekai",
+    "href": "decisions/20231125-v-sekai-report.html#what-is-v-sekai",
+    "title": "Superseded: V-Sekai 2023-11-25 Report",
     "section": "",
-    "text": "Yes, this strategy is core to our project and will be implemented by our team."
+    "text": "V-Sekai, pronounced vee-say-kai, is a collective of developers passionate about creating open-source VR technology. We aim to contribute to social VR and provide alternatives to proprietary engines like Unity and Unreal.\nDespite challenges, we’ve grown into a global community committed to advancing open standards and open-source software for virtual worlds.\nOur strategy focuses on providing comprehensive documentation and support to help users understand the platform better. We’re also committed to investigating and resolving issues like the reported Linux build problem."
   },
   {
-    "objectID": "decisions/20231209-appium-testing-win11.html#references",
-    "href": "decisions/20231209-appium-testing-win11.html#references",
-    "title": "Proposed: Automating Game Testing Process Using Appium 2",
+    "objectID": "decisions/20231125-v-sekai-report.html#background",
+    "href": "decisions/20231125-v-sekai-report.html#background",
+    "title": "Superseded: V-Sekai 2023-11-25 Report",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAssisted by Aria, an AI assistant."
+    "text": "Over the past month, our team has been deeply involved in the Godot Engine conference in Munich, Germany. Our primary responsibility during this period has been to prepare for the upcoming launch of Godot Engine 4.2, to which we are contributing as part of the animation and 3D pipeline teams.\nPLYSHKA🐧 asked on our Discord about the current state of V-Sekai:\n\nPLYSHKA🐧&gt; I’m fairly new to this platform overall, can someone explain in what state its currently in? What can it do and what can’t? I couldn’t launch Linux build properly (black screen), and when started from terminal it just opened Godot editor (it was game binary), so not sure what’s happening there, maybe I don’t understand something"
   },
   {
-    "objectID": "decisions/20240406-itch-github-actions.html",
-    "href": "decisions/20240406-itch-github-actions.html",
-    "title": "Proposed: Provide a V-Sekai Starter Kit",
+    "objectID": "decisions/20231125-v-sekai-report.html#problem-statement",
+    "href": "decisions/20231125-v-sekai-report.html#problem-statement",
+    "title": "Superseded: V-Sekai 2023-11-25 Report",
     "section": "",
-    "text": "Provide a V-Sekai starter kit that is complete and usable.\n\n\n\nUse desync (casync) to generate catars. Then upload this to itchio.\n\n\n\nWe will use the casync tool to create .catar files from our project directory. This will be followed by uploading these files to Itch.io using their Butler CLI tool.\n# Generate .catar file\ncasync make myproject.catar myproject/\n\n# Upload to Itch.io\nbutler push myproject.catar user/game:channel\n\n\n\nSeed a cdn. This will allow us to distribute our SDK more efficiently and reliably.\n\n\n\nThe main downside is the additional complexity introduced by the use of casync and Butler. There may also be potential issues with compatibility or performance.\n\n\n\nAn alternative approach could have been to directly upload the SDK files to Itch.io without using casync. However, this would not provide the benefits of seeding a CDN.\n\n\n\nThis process might be less efficient for small updates, as it involves creating a new .catar file and uploading it each time.\n\n\n\nThis proposal is core to our project and will be implemented by the V-Sekai development team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
+    "text": "What state is V-Sekai in, and what can it do?"
   },
   {
-    "objectID": "decisions/20240406-itch-github-actions.html#the-context",
-    "href": "decisions/20240406-itch-github-actions.html#the-context",
-    "title": "Proposed: Provide a V-Sekai Starter Kit",
+    "objectID": "decisions/20231125-v-sekai-report.html#strategy",
+    "href": "decisions/20231125-v-sekai-report.html#strategy",
+    "title": "Superseded: V-Sekai 2023-11-25 Report",
     "section": "",
-    "text": "Provide a V-Sekai starter kit that is complete and usable."
+    "text": "Desktop Mode Loading: V-Sekai is currently unable to load in desktop mode.\nThe purple screen on the desktop: The black screen issue seems related to our current problem of Issue #341\nMultiplayer Voice Chat: The multiplayer voice chat feature in V-Sekai is broken.\n\n\n\n\n\nMenu Editing: In V-Sekai, menus can’t be edited in VR. They can only be edited on the desktop before entering a game.\nDefault Avatar: V-Sekai does not have a default avatar. This causes confusion as players load in with an error avatar.\nDefault Avatar IK: V-Sekai’s default ik is currently twisted incorrectly.\n\n\n\n\n\nAvatar Uploading and Downloading:** V-Sekai can upload from the editor and, download avatars, and load them into the game at runtime.\nWorld Uploading and Downloading:** V-Sekai can upload from the editor and, download worlds, and load them into the game at runtime.\nVR Mode Loading: V-Sekai can successfully load in VR mode.\n\n\n\n\n\nContributions: V-Sekai is actively looking for more contributions."
   },
   {
-    "objectID": "decisions/20240406-itch-github-actions.html#the-problem-statement",
-    "href": "decisions/20240406-itch-github-actions.html#the-problem-statement",
-    "title": "Proposed: Provide a V-Sekai Starter Kit",
+    "objectID": "decisions/20231125-v-sekai-report.html#timeline-for-the-next-weeks",
+    "href": "decisions/20231125-v-sekai-report.html#timeline-for-the-next-weeks",
+    "title": "Superseded: V-Sekai 2023-11-25 Report",
     "section": "",
-    "text": "Use desync (casync) to generate catars. Then upload this to itchio."
+    "text": "Fire is set to merge ufbx, freeing the industry-standard FBX file format from the Autodesk ecosystem for V-Sekai. However, due to limited funding, we won’t be able to implement the upcoming 3D format standard USDZ in next months.\n\n\n\n\n\n\n\nWeek Starting\nTask\n\n\n\n\nNovember 26th, 2023\nInvestigate and resolve “purple screen” bug in V-Sekai.\n\n\nDecember 3rd, 2023\nInitiate the merging of godot-ufbx in Godot Engine 4.3."
   },
   {
-    "objectID": "decisions/20240406-itch-github-actions.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240406-itch-github-actions.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Provide a V-Sekai Starter Kit",
+    "objectID": "decisions/20231125-v-sekai-report.html#pros-and-cons",
+    "href": "decisions/20231125-v-sekai-report.html#pros-and-cons",
+    "title": "Superseded: V-Sekai 2023-11-25 Report",
     "section": "",
-    "text": "We will use the casync tool to create .catar files from our project directory. This will be followed by uploading these files to Itch.io using their Butler CLI tool.\n# Generate .catar file\ncasync make myproject.catar myproject/\n\n# Upload to Itch.io\nbutler push myproject.catar user/game:channel"
+    "text": "Pros:\nAddressing these challenges can enhance the user experience, boost platform adoption, and collect crucial feedback for subsequent development.\nCons:\nThere may be underlying issues causing the Linux build problem that could take significant time and resources to resolve."
   },
   {
-    "objectID": "decisions/20240406-itch-github-actions.html#the-benefits",
-    "href": "decisions/20240406-itch-github-actions.html#the-benefits",
-    "title": "Proposed: Provide a V-Sekai Starter Kit",
+    "objectID": "decisions/20231125-v-sekai-report.html#alternative-approach",
+    "href": "decisions/20231125-v-sekai-report.html#alternative-approach",
+    "title": "Superseded: V-Sekai 2023-11-25 Report",
     "section": "",
-    "text": "Seed a cdn. This will allow us to distribute our SDK more efficiently and reliably."
+    "text": "An alternative approach could have been to ignore the user’s query and continue with the current development roadmap. However, this would not foster a supportive community or encourage user engagement."
   },
   {
-    "objectID": "decisions/20240406-itch-github-actions.html#the-downsides",
-    "href": "decisions/20240406-itch-github-actions.html#the-downsides",
-    "title": "Proposed: Provide a V-Sekai Starter Kit",
+    "objectID": "decisions/20231125-v-sekai-report.html#infrequent-use-case",
+    "href": "decisions/20231125-v-sekai-report.html#infrequent-use-case",
+    "title": "Superseded: V-Sekai 2023-11-25 Report",
     "section": "",
-    "text": "The main downside is the additional complexity introduced by the use of casync and Butler. There may also be potential issues with compatibility or performance."
+    "text": "While most users may not encounter the same issue as PLYSHKA🐧, addressing even infrequent use cases is essential to ensure a robust and user-friendly platform."
   },
   {
-    "objectID": "decisions/20240406-itch-github-actions.html#the-road-not-taken",
-    "href": "decisions/20240406-itch-github-actions.html#the-road-not-taken",
-    "title": "Proposed: Provide a V-Sekai Starter Kit",
+    "objectID": "decisions/20231125-v-sekai-report.html#responsibility",
+    "href": "decisions/20231125-v-sekai-report.html#responsibility",
+    "title": "Superseded: V-Sekai 2023-11-25 Report",
     "section": "",
-    "text": "An alternative approach could have been to directly upload the SDK files to Itch.io without using casync. However, this would not provide the benefits of seeding a CDN."
+    "text": "Addressing this issue falls within our core responsibilities as the V-Sekai development team."
   },
   {
-    "objectID": "decisions/20240406-itch-github-actions.html#the-infrequent-use-case",
-    "href": "decisions/20240406-itch-github-actions.html#the-infrequent-use-case",
-    "title": "Proposed: Provide a V-Sekai Starter Kit",
+    "objectID": "decisions/20231125-v-sekai-report.html#further-reading",
+    "href": "decisions/20231125-v-sekai-report.html#further-reading",
+    "title": "Superseded: V-Sekai 2023-11-25 Report",
     "section": "",
-    "text": "This process might be less efficient for small updates, as it involves creating a new .catar file and uploading it each time."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240406-itch-github-actions.html#in-core-and-done-by-us",
-    "href": "decisions/20240406-itch-github-actions.html#in-core-and-done-by-us",
-    "title": "Proposed: Provide a V-Sekai Starter Kit",
+    "objectID": "decisions/20241006-restore-onedrive-shortcut-overrides.html",
+    "href": "decisions/20241006-restore-onedrive-shortcut-overrides.html",
+    "title": "Accepted: Restoring Default User Directory Structure in Windows 11",
     "section": "",
-    "text": "This proposal is core to our project and will be implemented by the V-Sekai development team."
+    "text": "Using Windows 11.\n\n\n\nMicrosoft has configured OneDrive to automatically move key user folders such as Documents, Desktop, and others from the user directory into the OneDrive folder. This change can disrupt users’ familiar file organization and system workflows.\n\n\n\nThe solution involves two main steps:\n\nDisabling OneDrive Sync: Users need to pause or stop OneDrive from syncing these folders.\nRunning a Restore Default Paths Script: Execute a script that resets the default paths of user directories back to their original locations on the local drive.\n\n\n\n\n\nRestores traditional file paths for ease of access and familiarity.\nReduces dependency on cloud synchronization for essential folders.\nImproves system performance by reducing unnecessary sync operations.\n\n\n\n\n\nManual intervention required by users not comfortable with script execution.\nPotential data discrepancies if files are not fully synchronized before the change.\n\n\n\n\nAlternative solutions like using third-party tools or different cloud services were considered but dismissed due to increased complexity and potential security concerns.\n\n\n\nUsers who operate primarily offline or have strict data handling policies may find this change particularly beneficial.\n\n\n\nThis proposal is to be implemented internally within the V-Sekai development team’s systems before considering broader deployment.\n\n\n\nStatus: Accepted \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nWindows 10/11 User Shell Folders Restore Default Paths\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240406-itch-github-actions.html#status",
-    "href": "decisions/20240406-itch-github-actions.html#status",
-    "title": "Proposed: Provide a V-Sekai Starter Kit",
+    "objectID": "decisions/20241006-restore-onedrive-shortcut-overrides.html#the-context",
+    "href": "decisions/20241006-restore-onedrive-shortcut-overrides.html#the-context",
+    "title": "Accepted: Restoring Default User Directory Structure in Windows 11",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "Using Windows 11."
   },
   {
-    "objectID": "decisions/20240406-itch-github-actions.html#decision-makers",
-    "href": "decisions/20240406-itch-github-actions.html#decision-makers",
-    "title": "Proposed: Provide a V-Sekai Starter Kit",
+    "objectID": "decisions/20241006-restore-onedrive-shortcut-overrides.html#the-problem-statement",
+    "href": "decisions/20241006-restore-onedrive-shortcut-overrides.html#the-problem-statement",
+    "title": "Accepted: Restoring Default User Directory Structure in Windows 11",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "Microsoft has configured OneDrive to automatically move key user folders such as Documents, Desktop, and others from the user directory into the OneDrive folder. This change can disrupt users’ familiar file organization and system workflows."
   },
   {
-    "objectID": "decisions/20240406-itch-github-actions.html#tags",
-    "href": "decisions/20240406-itch-github-actions.html#tags",
-    "title": "Proposed: Provide a V-Sekai Starter Kit",
+    "objectID": "decisions/20241006-restore-onedrive-shortcut-overrides.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20241006-restore-onedrive-shortcut-overrides.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Accepted: Restoring Default User Directory Structure in Windows 11",
     "section": "",
-    "text": "V-Sekai"
+    "text": "The solution involves two main steps:\n\nDisabling OneDrive Sync: Users need to pause or stop OneDrive from syncing these folders.\nRunning a Restore Default Paths Script: Execute a script that resets the default paths of user directories back to their original locations on the local drive."
   },
   {
-    "objectID": "decisions/20240406-itch-github-actions.html#further-reading",
-    "href": "decisions/20240406-itch-github-actions.html#further-reading",
-    "title": "Proposed: Provide a V-Sekai Starter Kit",
+    "objectID": "decisions/20241006-restore-onedrive-shortcut-overrides.html#the-benefits",
+    "href": "decisions/20241006-restore-onedrive-shortcut-overrides.html#the-benefits",
+    "title": "Accepted: Restoring Default User Directory Structure in Windows 11",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
+    "text": "Restores traditional file paths for ease of access and familiarity.\nReduces dependency on cloud synchronization for essential folders.\nImproves system performance by reducing unnecessary sync operations."
   },
   {
-    "objectID": "decisions/20240622-build-for-many-platforms.html",
-    "href": "decisions/20240622-build-for-many-platforms.html",
-    "title": "Proposed: Build V-Sekai editor for many platforms",
+    "objectID": "decisions/20241006-restore-onedrive-shortcut-overrides.html#the-downsides",
+    "href": "decisions/20241006-restore-onedrive-shortcut-overrides.html#the-downsides",
+    "title": "Accepted: Restoring Default User Directory Structure in Windows 11",
     "section": "",
-    "text": "V-Sekai is a versatile tool that we utilize across various domains. Its adaptability and functionality make it an integral part of our operations.\n\n\n\nThe challenge at hand is to build the V-Sekai editor for multiple platforms, thereby enhancing its accessibility and usability.\n\n\n\nOur approach to this problem involves leveraging existing resources and tools:\n\nUtilize our existing gocd pipeline.\nEmploy osxcross for Mac builds.\nUse mingw for Windows builds.\nApply clang for Linux builds.\nImplement emscripten for web assembly.\nUtilize the android sdk on linux for Android builds.\n\nIn addition to these steps, we will also implement automated testing to ensure consistency across all systems. This will involve creating test scripts that can run on each platform, checking for any discrepancies or issues.\n\n\n\nOur goal is to showcase V-Sekai in October 2024. To achieve this, we need to prepare for various hardware targets. This multi-platform build will significantly enhance our reach and impact.\n\n\n\nThe primary downside is the potential complexity and challenges associated with managing and testing numerous build targets. Automated testing should help mitigate this issue, but it will still require careful management and oversight.\n\n\n\nWe could have chosen to focus on a single platform, but this would limit the reach and versatility of V-Sekai. By targeting multiple platforms, we can ensure that V-Sekai is accessible to a wider audience.\n\n\n\nWhile the main use case is for regular users, there may be infrequent use cases where developers or other tech-savvy individuals might want to customize or extend the functionality of V-Sekai. Our multi-platform approach caters to these users as well.\n\n\n\nThis project is core to our mission and will be executed by me. We believe that having control over the development process will allow us to maintain the high quality and consistency that we strive for.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\nFire\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - This is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis proposal was assisted by AI assistant Aria."
+    "text": "Manual intervention required by users not comfortable with script execution.\nPotential data discrepancies if files are not fully synchronized before the change."
   },
   {
-    "objectID": "decisions/20240622-build-for-many-platforms.html#the-context",
-    "href": "decisions/20240622-build-for-many-platforms.html#the-context",
-    "title": "Proposed: Build V-Sekai editor for many platforms",
+    "objectID": "decisions/20241006-restore-onedrive-shortcut-overrides.html#the-road-not-taken",
+    "href": "decisions/20241006-restore-onedrive-shortcut-overrides.html#the-road-not-taken",
+    "title": "Accepted: Restoring Default User Directory Structure in Windows 11",
     "section": "",
-    "text": "V-Sekai is a versatile tool that we utilize across various domains. Its adaptability and functionality make it an integral part of our operations."
+    "text": "Alternative solutions like using third-party tools or different cloud services were considered but dismissed due to increased complexity and potential security concerns."
   },
   {
-    "objectID": "decisions/20240622-build-for-many-platforms.html#the-problem-statement",
-    "href": "decisions/20240622-build-for-many-platforms.html#the-problem-statement",
-    "title": "Proposed: Build V-Sekai editor for many platforms",
+    "objectID": "decisions/20241006-restore-onedrive-shortcut-overrides.html#the-infrequent-use-case",
+    "href": "decisions/20241006-restore-onedrive-shortcut-overrides.html#the-infrequent-use-case",
+    "title": "Accepted: Restoring Default User Directory Structure in Windows 11",
     "section": "",
-    "text": "The challenge at hand is to build the V-Sekai editor for multiple platforms, thereby enhancing its accessibility and usability."
+    "text": "Users who operate primarily offline or have strict data handling policies may find this change particularly beneficial."
   },
   {
-    "objectID": "decisions/20240622-build-for-many-platforms.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240622-build-for-many-platforms.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Build V-Sekai editor for many platforms",
+    "objectID": "decisions/20241006-restore-onedrive-shortcut-overrides.html#in-core-and-done-by-us",
+    "href": "decisions/20241006-restore-onedrive-shortcut-overrides.html#in-core-and-done-by-us",
+    "title": "Accepted: Restoring Default User Directory Structure in Windows 11",
     "section": "",
-    "text": "Our approach to this problem involves leveraging existing resources and tools:\n\nUtilize our existing gocd pipeline.\nEmploy osxcross for Mac builds.\nUse mingw for Windows builds.\nApply clang for Linux builds.\nImplement emscripten for web assembly.\nUtilize the android sdk on linux for Android builds.\n\nIn addition to these steps, we will also implement automated testing to ensure consistency across all systems. This will involve creating test scripts that can run on each platform, checking for any discrepancies or issues."
+    "text": "This proposal is to be implemented internally within the V-Sekai development team’s systems before considering broader deployment."
   },
   {
-    "objectID": "decisions/20240622-build-for-many-platforms.html#the-benefits",
-    "href": "decisions/20240622-build-for-many-platforms.html#the-benefits",
-    "title": "Proposed: Build V-Sekai editor for many platforms",
+    "objectID": "decisions/20241006-restore-onedrive-shortcut-overrides.html#status",
+    "href": "decisions/20241006-restore-onedrive-shortcut-overrides.html#status",
+    "title": "Accepted: Restoring Default User Directory Structure in Windows 11",
     "section": "",
-    "text": "Our goal is to showcase V-Sekai in October 2024. To achieve this, we need to prepare for various hardware targets. This multi-platform build will significantly enhance our reach and impact."
+    "text": "Status: Accepted"
   },
   {
-    "objectID": "decisions/20240622-build-for-many-platforms.html#the-downsides",
-    "href": "decisions/20240622-build-for-many-platforms.html#the-downsides",
-    "title": "Proposed: Build V-Sekai editor for many platforms",
+    "objectID": "decisions/20241006-restore-onedrive-shortcut-overrides.html#decision-makers",
+    "href": "decisions/20241006-restore-onedrive-shortcut-overrides.html#decision-makers",
+    "title": "Accepted: Restoring Default User Directory Structure in Windows 11",
     "section": "",
-    "text": "The primary downside is the potential complexity and challenges associated with managing and testing numerous build targets. Automated testing should help mitigate this issue, but it will still require careful management and oversight."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20240622-build-for-many-platforms.html#the-road-not-taken",
-    "href": "decisions/20240622-build-for-many-platforms.html#the-road-not-taken",
-    "title": "Proposed: Build V-Sekai editor for many platforms",
+    "objectID": "decisions/20241006-restore-onedrive-shortcut-overrides.html#tags",
+    "href": "decisions/20241006-restore-onedrive-shortcut-overrides.html#tags",
+    "title": "Accepted: Restoring Default User Directory Structure in Windows 11",
     "section": "",
-    "text": "We could have chosen to focus on a single platform, but this would limit the reach and versatility of V-Sekai. By targeting multiple platforms, we can ensure that V-Sekai is accessible to a wider audience."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20240622-build-for-many-platforms.html#the-infrequent-use-case",
-    "href": "decisions/20240622-build-for-many-platforms.html#the-infrequent-use-case",
-    "title": "Proposed: Build V-Sekai editor for many platforms",
+    "objectID": "decisions/20241006-restore-onedrive-shortcut-overrides.html#further-reading",
+    "href": "decisions/20241006-restore-onedrive-shortcut-overrides.html#further-reading",
+    "title": "Accepted: Restoring Default User Directory Structure in Windows 11",
     "section": "",
-    "text": "While the main use case is for regular users, there may be infrequent use cases where developers or other tech-savvy individuals might want to customize or extend the functionality of V-Sekai. Our multi-platform approach caters to these users as well."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nWindows 10/11 User Shell Folders Restore Default Paths\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240622-build-for-many-platforms.html#in-core-and-done-by-us",
-    "href": "decisions/20240622-build-for-many-platforms.html#in-core-and-done-by-us",
-    "title": "Proposed: Build V-Sekai editor for many platforms",
+    "objectID": "decisions/20240425-proposal-prompt-system.html",
+    "href": "decisions/20240425-proposal-prompt-system.html",
+    "title": "Proposed: ChatGPT-4 Based Proposal Prompt System",
     "section": "",
-    "text": "This project is core to our mission and will be executed by me. We believe that having control over the development process will allow us to maintain the high quality and consistency that we strive for."
+    "text": "In the current scenario, creating proposals can be a time-consuming task. It requires a lot of brainstorming and writing which can sometimes lead to inefficiency and delay in work.\n\n\n\nThe problem lies in the manual creation of proposals. The process is slow and often lacks creativity due to human limitations. There is a need for an automated system that can generate proposals efficiently and creatively.\n\n\n\nWe propose a system that uses OpenAI’s ChatGPT-4 to generate proposals. The user will provide a prompt such as Create a proposal. Don't be purple. Be snappy. and the system will use this prompt to generate a proposal.\n\n\n\n\nEfficiency: This system will significantly reduce the time taken to create proposals.\nCreativity: With GPT-4’s advanced language model, the proposals generated will be creative and engaging.\nEase of Use: Users just need to provide a prompt and the system will take care of the rest.\n\n\n\n\nThe system may not always provide the best decision but only the most common wisdom. It might require human intervention to fine-tune the proposals.\n\n\n\nThere could be other AI models or methods to automate the proposal generation process. However, considering the performance and capabilities of GPT-4, it seems to be the most suitable choice.\n\n\n\nThis system might not be very useful for users who rarely need to create proposals.\n\n\n\nThe system will be developed and maintained by the V-Sekai development team.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\nProposal Generation\nGPT-4\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis proposal was assisted by AI assistant Aria."
   },
   {
-    "objectID": "decisions/20240622-build-for-many-platforms.html#status",
-    "href": "decisions/20240622-build-for-many-platforms.html#status",
-    "title": "Proposed: Build V-Sekai editor for many platforms",
+    "objectID": "decisions/20240425-proposal-prompt-system.html#context",
+    "href": "decisions/20240425-proposal-prompt-system.html#context",
+    "title": "Proposed: ChatGPT-4 Based Proposal Prompt System",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "In the current scenario, creating proposals can be a time-consuming task. It requires a lot of brainstorming and writing which can sometimes lead to inefficiency and delay in work."
   },
   {
-    "objectID": "decisions/20240622-build-for-many-platforms.html#decision-makers",
-    "href": "decisions/20240622-build-for-many-platforms.html#decision-makers",
-    "title": "Proposed: Build V-Sekai editor for many platforms",
+    "objectID": "decisions/20240425-proposal-prompt-system.html#problem-statement",
+    "href": "decisions/20240425-proposal-prompt-system.html#problem-statement",
+    "title": "Proposed: ChatGPT-4 Based Proposal Prompt System",
     "section": "",
-    "text": "V-Sekai development team\nFire"
+    "text": "The problem lies in the manual creation of proposals. The process is slow and often lacks creativity due to human limitations. There is a need for an automated system that can generate proposals efficiently and creatively."
   },
   {
-    "objectID": "decisions/20240622-build-for-many-platforms.html#tags",
-    "href": "decisions/20240622-build-for-many-platforms.html#tags",
-    "title": "Proposed: Build V-Sekai editor for many platforms",
+    "objectID": "decisions/20240425-proposal-prompt-system.html#proposed-solution",
+    "href": "decisions/20240425-proposal-prompt-system.html#proposed-solution",
+    "title": "Proposed: ChatGPT-4 Based Proposal Prompt System",
     "section": "",
-    "text": "V-Sekai"
+    "text": "We propose a system that uses OpenAI’s ChatGPT-4 to generate proposals. The user will provide a prompt such as Create a proposal. Don't be purple. Be snappy. and the system will use this prompt to generate a proposal."
   },
   {
-    "objectID": "decisions/20240622-build-for-many-platforms.html#further-reading",
-    "href": "decisions/20240622-build-for-many-platforms.html#further-reading",
-    "title": "Proposed: Build V-Sekai editor for many platforms",
+    "objectID": "decisions/20240425-proposal-prompt-system.html#benefits",
+    "href": "decisions/20240425-proposal-prompt-system.html#benefits",
+    "title": "Proposed: ChatGPT-4 Based Proposal Prompt System",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - This is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis proposal was assisted by AI assistant Aria."
+    "text": "Efficiency: This system will significantly reduce the time taken to create proposals.\nCreativity: With GPT-4’s advanced language model, the proposals generated will be creative and engaging.\nEase of Use: Users just need to provide a prompt and the system will take care of the rest."
   },
   {
-    "objectID": "decisions/20230125-possible-futures.html",
-    "href": "decisions/20230125-possible-futures.html",
-    "title": "Proposed: Possible futures",
+    "objectID": "decisions/20240425-proposal-prompt-system.html#downsides",
+    "href": "decisions/20240425-proposal-prompt-system.html#downsides",
+    "title": "Proposed: ChatGPT-4 Based Proposal Prompt System",
     "section": "",
-    "text": "Proposed: Possible futures\n\nMetadata\n\nStatus: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nContext and Problem Statement\nWe need to choose features to add to V-Sekai.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nTrim the steps needed to create the game.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nMain development:\n\nDevelop prototype of in-game tablet interface (L)\n\nImplement features to place objects (M)\nDebug color picker (S)\n\n\nFuture development:\n\nDebug joining separate worlds with different steps (L)\nRefine UI and user experience (L)\n\nTest and debug prototype (L)\n\nDebug backend upload support (L)\nDebug backend server lobby (L)\nDebug engine multiplayer (L)\nDefine architecture and create design document (S)\nImplement text input (S)\nAdjust objects with PLY (M)\nIntegrate the PLY addon for manifold meshes (L)\nImplement features to lock objects (M)\nDebug VOIP chat (M)\nMerge, subtract and intersect 3D models (XL)\nFocus a group of 3d models M)\nTools with sliders (M)\n\nAdjust constraints of the tool sliders with dag adjustment.\n\n\n\n\nPositive Consequences\nWe are able to use V-Sekai for fun and work.\n\n\nNegative Consequences\nWe cannot get other features in.\n\n\nOption graveyard\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nKnowing what to do is hard.\n\n\nIs there a reason why this should be core and done by us?\nThis is a list of core features.\n\n\nReferences\n\nV-Sekai"
+    "text": "The system may not always provide the best decision but only the most common wisdom. It might require human intervention to fine-tune the proposals."
   },
   {
-    "objectID": "decisions/20211031-how-to-make-a-v-sekaigodot-update.html",
-    "href": "decisions/20211031-how-to-make-a-v-sekaigodot-update.html",
-    "title": "Proposed: How to make a V-Sekai/godot update?",
+    "objectID": "decisions/20240425-proposal-prompt-system.html#the-road-not-taken",
+    "href": "decisions/20240425-proposal-prompt-system.html#the-road-not-taken",
+    "title": "Proposed: ChatGPT-4 Based Proposal Prompt System",
     "section": "",
-    "text": "Proposed: How to make a V-Sekai/godot update?\n\nContext and Problem Statement\nWrite down how we make branch updates.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nNeed to write down how to do updates.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nOn the Github UI, go to the mater branch and update from Godot Engine master.\ngit clone https://github.com/V-Sekai/groups_merge_script\ncd groups_merge_script\nsh update_repos.sh\ngit clone https://github.com/V-Sekai/groups-workspace-fire -b 4.x --single-branch --recurse-submodules\ncd groups-workspace-fire\n# open folder in visual studio code\n# use update repositories visual studio code command\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot code, but procedure.\n\n\nPositive Consequences\nLower bus factor.\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nThis a V-Sekai organization task.\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "There could be other AI models or methods to automate the proposal generation process. However, considering the performance and capabilities of GPT-4, it seems to be the most suitable choice."
   },
   {
-    "objectID": "decisions/20240502-membrane-framework-identity-post.html",
-    "href": "decisions/20240502-membrane-framework-identity-post.html",
-    "title": "Proposed: Process the glTF2 input file and return it as is",
+    "objectID": "decisions/20240425-proposal-prompt-system.html#the-infrequent-use-case",
+    "href": "decisions/20240425-proposal-prompt-system.html#the-infrequent-use-case",
+    "title": "Proposed: ChatGPT-4 Based Proposal Prompt System",
     "section": "",
-    "text": "We are working on a project that involves the use of the Elixir Membrane Framework. Our goal is to process glTF (GL Transmission Format) files, which are standard file formats for 3D scenes and models.\n\n\n\nWe need to create a job in the Membrane Framework that can take an input glTF file and return it as is. However, we are currently stuck and unable to proceed with this task.\n\n\n\ndefmodule MyPipeline do\n  use Membrane.Pipeline\n\n  @impl true\n  def handle_init(_) do\n    children = %{\n      source: %Membrane.File.Source{location: \"input.gltf\"},\n      sink: Membrane.File.Sink\n    }\n\n    links = [\n      link(:source)\n      |&gt; to(:sink)\n    ]\n\n    {{:ok, %ParentSpec{children: children, links: links}}, %{}}\n  end\nend\nThis is a basic pipeline that reads a file and writes it back out. It’s not doing any processing yet, but it’s a start.\n\n\n\nImplementing this feature will allow us to process glTF files within our application, opening up new possibilities for 3D model manipulation and visualization.\n\n\n\nThe main downside is the complexity involved in understanding and implementing the Membrane Framework. This could potentially slow down development time.\n\n\n\nAn alternative approach would have been to use a different framework or language that might be easier to implement but may not offer the same level of control and flexibility as the Membrane Framework.\n\n\n\nThis feature may not be used frequently if our application does not heavily rely on 3D model manipulation.\n\n\n\nThis feature will be implemented by the V-Sekai development team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "This system might not be very useful for users who rarely need to create proposals."
   },
   {
-    "objectID": "decisions/20240502-membrane-framework-identity-post.html#the-context",
-    "href": "decisions/20240502-membrane-framework-identity-post.html#the-context",
-    "title": "Proposed: Process the glTF2 input file and return it as is",
+    "objectID": "decisions/20240425-proposal-prompt-system.html#in-core-and-done-by-us",
+    "href": "decisions/20240425-proposal-prompt-system.html#in-core-and-done-by-us",
+    "title": "Proposed: ChatGPT-4 Based Proposal Prompt System",
     "section": "",
-    "text": "We are working on a project that involves the use of the Elixir Membrane Framework. Our goal is to process glTF (GL Transmission Format) files, which are standard file formats for 3D scenes and models."
+    "text": "The system will be developed and maintained by the V-Sekai development team."
   },
   {
-    "objectID": "decisions/20240502-membrane-framework-identity-post.html#the-problem-statement",
-    "href": "decisions/20240502-membrane-framework-identity-post.html#the-problem-statement",
-    "title": "Proposed: Process the glTF2 input file and return it as is",
+    "objectID": "decisions/20240425-proposal-prompt-system.html#status",
+    "href": "decisions/20240425-proposal-prompt-system.html#status",
+    "title": "Proposed: ChatGPT-4 Based Proposal Prompt System",
     "section": "",
-    "text": "We need to create a job in the Membrane Framework that can take an input glTF file and return it as is. However, we are currently stuck and unable to proceed with this task."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20240502-membrane-framework-identity-post.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240502-membrane-framework-identity-post.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Process the glTF2 input file and return it as is",
+    "objectID": "decisions/20240425-proposal-prompt-system.html#decision-makers",
+    "href": "decisions/20240425-proposal-prompt-system.html#decision-makers",
+    "title": "Proposed: ChatGPT-4 Based Proposal Prompt System",
     "section": "",
-    "text": "defmodule MyPipeline do\n  use Membrane.Pipeline\n\n  @impl true\n  def handle_init(_) do\n    children = %{\n      source: %Membrane.File.Source{location: \"input.gltf\"},\n      sink: Membrane.File.Sink\n    }\n\n    links = [\n      link(:source)\n      |&gt; to(:sink)\n    ]\n\n    {{:ok, %ParentSpec{children: children, links: links}}, %{}}\n  end\nend\nThis is a basic pipeline that reads a file and writes it back out. It’s not doing any processing yet, but it’s a start."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20240502-membrane-framework-identity-post.html#the-benefits",
-    "href": "decisions/20240502-membrane-framework-identity-post.html#the-benefits",
-    "title": "Proposed: Process the glTF2 input file and return it as is",
+    "objectID": "decisions/20240425-proposal-prompt-system.html#tags",
+    "href": "decisions/20240425-proposal-prompt-system.html#tags",
+    "title": "Proposed: ChatGPT-4 Based Proposal Prompt System",
     "section": "",
-    "text": "Implementing this feature will allow us to process glTF files within our application, opening up new possibilities for 3D model manipulation and visualization."
+    "text": "V-Sekai\nProposal Generation\nGPT-4"
   },
   {
-    "objectID": "decisions/20240502-membrane-framework-identity-post.html#the-downsides",
-    "href": "decisions/20240502-membrane-framework-identity-post.html#the-downsides",
-    "title": "Proposed: Process the glTF2 input file and return it as is",
+    "objectID": "decisions/20240425-proposal-prompt-system.html#further-reading",
+    "href": "decisions/20240425-proposal-prompt-system.html#further-reading",
+    "title": "Proposed: ChatGPT-4 Based Proposal Prompt System",
     "section": "",
-    "text": "The main downside is the complexity involved in understanding and implementing the Membrane Framework. This could potentially slow down development time."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis proposal was assisted by AI assistant Aria."
   },
   {
-    "objectID": "decisions/20240502-membrane-framework-identity-post.html#the-road-not-taken",
-    "href": "decisions/20240502-membrane-framework-identity-post.html#the-road-not-taken",
-    "title": "Proposed: Process the glTF2 input file and return it as is",
+    "objectID": "decisions/20211031-client-and-mast.html",
+    "href": "decisions/20211031-client-and-mast.html",
+    "title": "Proposed: Client and Mast",
     "section": "",
-    "text": "An alternative approach would have been to use a different framework or language that might be easier to implement but may not offer the same level of control and flexibility as the Membrane Framework."
+    "text": "Proposed: Client and Mast\n\nContext and Problem Statement\nClient and Mast\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nClient and Mast\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nClient and Mast.\nScripting / entity APIs: wasm / barebones messaging protocols + notification / scripted objects? entities?\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot a few lines of script.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nI know how this works.\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240502-membrane-framework-identity-post.html#the-infrequent-use-case",
-    "href": "decisions/20240502-membrane-framework-identity-post.html#the-infrequent-use-case",
-    "title": "Proposed: Process the glTF2 input file and return it as is",
+    "objectID": "decisions/20240905-revised-tracker-configuration-and-constraints.html",
+    "href": "decisions/20240905-revised-tracker-configuration-and-constraints.html",
+    "title": "Proposed: Revised Tracker Configuration and Constraints for HTC VIVE XR Elite",
     "section": "",
-    "text": "This feature may not be used frequently if our application does not heavily rely on 3D model manipulation."
+    "text": "In virtual reality (VR), precise motion tracking is import for immersive experiences. Effective tracker configuration is essential to enhance interaction within VR environments, specifically for the HTC VIVE XR Elite.\n\n\n\nTracker configurations distribution across available dongles, affects the setup of motion capture in VR applications, particularly with the HTC VIVE XR Elite.\n\n\n\n\n\n\nHips (1 tracker)\nFoot Right (1 tracker)\nFoot Left (1 tracker)\nElbow Left (1 tracker)\nElbow Right (1 tracker)\n\n\n\n\n\nKnee Right (1 tracker)\nKnee Left (1 tracker)\nChest (1 tracker)\nHips (1 tracker optional)\nChest (1 tracker optional)\n\n\n\n\nEach dongle supports a maximum of 5 trackers. This constraint is critical in determining how trackers are distributed between the two dongles to ensure optimal performance without exceeding the connectivity limit, specifically for the HTC VIVE XR Elite.\n\n\n\n\n\n\nEnhanced Lower Limb Tracking: By connecting both knee trackers to the HMD dongle, we ensure precise tracking of lower limb movements, which is essential for accurate motion capture in activities that involve significant leg movement.\nUpper Extremity Tracking: Including both elbow trackers on this dongle allows for detailed arm movement tracking, enhancing the realism and responsiveness of upper body interactions in VR.\n\n\n\n\n\nComprehensive Upper Body Tracking:\n\nChest and Hips Trackers: These trackers are crucial for capturing the core movements of the body, providing a stable base for upper body motion tracking.\nDual Foot Tracking: Placing the foot trackers on the PC-connected dongle ensures that foot movements are captured accurately, which is vital for walking, running, and other foot-based interactions in VR environments.\n\n\n\n\n\n\n\n\nImproved Accuracy: Optimized tracker placement enhances the precision of motion capture.\nEnhanced User Experience: More accurate tracking translates to a more immersive and responsive VR experience.\nScalability: This setup allows for easy adjustments and scalability as new trackers or technologies become available.\n\n\n\n\n\nComplex Setup: Initial configuration and calibration may be more complex and time-consuming.\nHardware Dependency: Performance is heavily dependent on the quality and capability of the hardware used.\n\n\n\n\nAlternative configurations that involved different distributions of trackers were considered but were not pursued due to potential compromises in tracking accuracy and performance.\n\n\n\nIn cases where extreme precision is not required, such as in less interactive VR applications, a simpler tracker setup might suffice.\n\n\n\nThis proposal aligns with our core mission to push the boundaries of VR technology and will be implemented by our internal development team, focusing on the HTC VIVE XR Elite.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\nHTC VIVE XR Elite\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240502-membrane-framework-identity-post.html#in-core-and-done-by-us",
-    "href": "decisions/20240502-membrane-framework-identity-post.html#in-core-and-done-by-us",
-    "title": "Proposed: Process the glTF2 input file and return it as is",
+    "objectID": "decisions/20240905-revised-tracker-configuration-and-constraints.html#the-context",
+    "href": "decisions/20240905-revised-tracker-configuration-and-constraints.html#the-context",
+    "title": "Proposed: Revised Tracker Configuration and Constraints for HTC VIVE XR Elite",
     "section": "",
-    "text": "This feature will be implemented by the V-Sekai development team."
+    "text": "In virtual reality (VR), precise motion tracking is import for immersive experiences. Effective tracker configuration is essential to enhance interaction within VR environments, specifically for the HTC VIVE XR Elite."
   },
   {
-    "objectID": "decisions/20240502-membrane-framework-identity-post.html#status",
-    "href": "decisions/20240502-membrane-framework-identity-post.html#status",
-    "title": "Proposed: Process the glTF2 input file and return it as is",
+    "objectID": "decisions/20240905-revised-tracker-configuration-and-constraints.html#the-problem-statement",
+    "href": "decisions/20240905-revised-tracker-configuration-and-constraints.html#the-problem-statement",
+    "title": "Proposed: Revised Tracker Configuration and Constraints for HTC VIVE XR Elite",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "Tracker configurations distribution across available dongles, affects the setup of motion capture in VR applications, particularly with the HTC VIVE XR Elite."
   },
   {
-    "objectID": "decisions/20240502-membrane-framework-identity-post.html#decision-makers",
-    "href": "decisions/20240502-membrane-framework-identity-post.html#decision-makers",
-    "title": "Proposed: Process the glTF2 input file and return it as is",
+    "objectID": "decisions/20240905-revised-tracker-configuration-and-constraints.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240905-revised-tracker-configuration-and-constraints.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Revised Tracker Configuration and Constraints for HTC VIVE XR Elite",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "Hips (1 tracker)\nFoot Right (1 tracker)\nFoot Left (1 tracker)\nElbow Left (1 tracker)\nElbow Right (1 tracker)\n\n\n\n\n\nKnee Right (1 tracker)\nKnee Left (1 tracker)\nChest (1 tracker)\nHips (1 tracker optional)\nChest (1 tracker optional)\n\n\n\n\nEach dongle supports a maximum of 5 trackers. This constraint is critical in determining how trackers are distributed between the two dongles to ensure optimal performance without exceeding the connectivity limit, specifically for the HTC VIVE XR Elite.\n\n\n\n\n\n\nEnhanced Lower Limb Tracking: By connecting both knee trackers to the HMD dongle, we ensure precise tracking of lower limb movements, which is essential for accurate motion capture in activities that involve significant leg movement.\nUpper Extremity Tracking: Including both elbow trackers on this dongle allows for detailed arm movement tracking, enhancing the realism and responsiveness of upper body interactions in VR.\n\n\n\n\n\nComprehensive Upper Body Tracking:\n\nChest and Hips Trackers: These trackers are crucial for capturing the core movements of the body, providing a stable base for upper body motion tracking.\nDual Foot Tracking: Placing the foot trackers on the PC-connected dongle ensures that foot movements are captured accurately, which is vital for walking, running, and other foot-based interactions in VR environments."
   },
   {
-    "objectID": "decisions/20240502-membrane-framework-identity-post.html#tags",
-    "href": "decisions/20240502-membrane-framework-identity-post.html#tags",
-    "title": "Proposed: Process the glTF2 input file and return it as is",
+    "objectID": "decisions/20240905-revised-tracker-configuration-and-constraints.html#the-benefits",
+    "href": "decisions/20240905-revised-tracker-configuration-and-constraints.html#the-benefits",
+    "title": "Proposed: Revised Tracker Configuration and Constraints for HTC VIVE XR Elite",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Improved Accuracy: Optimized tracker placement enhances the precision of motion capture.\nEnhanced User Experience: More accurate tracking translates to a more immersive and responsive VR experience.\nScalability: This setup allows for easy adjustments and scalability as new trackers or technologies become available."
   },
   {
-    "objectID": "decisions/20240502-membrane-framework-identity-post.html#further-reading",
-    "href": "decisions/20240502-membrane-framework-identity-post.html#further-reading",
-    "title": "Proposed: Process the glTF2 input file and return it as is",
+    "objectID": "decisions/20240905-revised-tracker-configuration-and-constraints.html#the-downsides",
+    "href": "decisions/20240905-revised-tracker-configuration-and-constraints.html#the-downsides",
+    "title": "Proposed: Revised Tracker Configuration and Constraints for HTC VIVE XR Elite",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "Complex Setup: Initial configuration and calibration may be more complex and time-consuming.\nHardware Dependency: Performance is heavily dependent on the quality and capability of the hardware used."
   },
   {
-    "objectID": "decisions/20211031-plausable-npc-behaviour.html",
-    "href": "decisions/20211031-plausable-npc-behaviour.html",
-    "title": "Proposed: Plausible npc behavior",
+    "objectID": "decisions/20240905-revised-tracker-configuration-and-constraints.html#the-road-not-taken",
+    "href": "decisions/20240905-revised-tracker-configuration-and-constraints.html#the-road-not-taken",
+    "title": "Proposed: Revised Tracker Configuration and Constraints for HTC VIVE XR Elite",
     "section": "",
-    "text": "Proposed: Plausible npc behavior\n\nContext and Problem Statement\nCreate plausible npc behavior\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nPlausible npc behavior using a htn planner\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nUpgrade my htn planner to a production state.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot a few lines.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nI have an approach!\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Alternative configurations that involved different distributions of trackers were considered but were not pursued due to potential compromises in tracking accuracy and performance."
   },
   {
-    "objectID": "decisions/20240413-calling-opensource-llm-with-aria.html",
-    "href": "decisions/20240413-calling-opensource-llm-with-aria.html",
-    "title": "Proposed: Calling Open Source LLM with Aria",
+    "objectID": "decisions/20240905-revised-tracker-configuration-and-constraints.html#the-infrequent-use-case",
+    "href": "decisions/20240905-revised-tracker-configuration-and-constraints.html#the-infrequent-use-case",
+    "title": "Proposed: Revised Tracker Configuration and Constraints for HTC VIVE XR Elite",
     "section": "",
-    "text": "Access to OpenAI’s ChatGPT-4 cannot last forever.\n\n\n\nUsing the assistant name Aria, I want to call an Apache2 licensed large language model (LLM) with open weights in my code editor, Visual Studio Code by Microsoft.\n\n\n\n\nInstall LM Studio: A tool for managing and deploying large language models.\nDownload a quantized version of Hermes-2-Pro-Mistral-7B: This model is available at Hugging Face Model Card.\nInstall Visual Studio Code: The popular code editor by Microsoft.\nInstall the Genie extension: This lets you interact with AI models directly in Visual Studio Code. ai-genie.chatgpt-vscode\nSet Genie to use the assistant name “Aria”: This will give the AI a unique identity within Visual Studio Code.\n{\n  \"genie.assistantName\": \"Aria\",\n  \"genie.apiUrl\": \"http://localhost:1234/v1/chat/completions\",\n  \"genie.model\": {\n    \"id\": \"nousresearch/hermes-2-pro-mistral-7b\",\n    \"tokenLimit\": 8192\n  }\n}\nStart using Aria in Visual Studio Code: With the above settings, you can now access and interact with the open source large language model (LLM) named Hermes-2-Pro-Mistral-7B through the Genie extension.\n\n\n\n\n\nAccess to an AI assistant large language model.\nAbility to develop and fine-tune your data models on open-source datasets.\n\n\n\n\n\nRequires a good understanding of natural language processing (NLP) and machine learning concepts.\nMay require additional hardware resources for running the LLM locally.\n\n\n\n\n\nUsing proprietary AI models that are not open-source or freely available, such as OpenAI’s ChatGPT-4.\nRelying on cloud-based services for AI interactions instead of local deployment.\n\n\n\n\n\nIn cases where real-time performance is critical, using an LLM might not be the optimal solution due to its computational requirements.\n\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\nFire\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
+    "text": "In cases where extreme precision is not required, such as in less interactive VR applications, a simpler tracker setup might suffice."
   },
   {
-    "objectID": "decisions/20240413-calling-opensource-llm-with-aria.html#further-reading",
-    "href": "decisions/20240413-calling-opensource-llm-with-aria.html#further-reading",
-    "title": "Proposed: Calling Open Source LLM with Aria",
+    "objectID": "decisions/20240905-revised-tracker-configuration-and-constraints.html#in-core-and-done-by-us",
+    "href": "decisions/20240905-revised-tracker-configuration-and-constraints.html#in-core-and-done-by-us",
+    "title": "Proposed: Revised Tracker Configuration and Constraints for HTC VIVE XR Elite",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
+    "text": "This proposal aligns with our core mission to push the boundaries of VR technology and will be implemented by our internal development team, focusing on the HTC VIVE XR Elite."
   },
   {
-    "objectID": "decisions/20240522-discord-inworld-portal.html",
-    "href": "decisions/20240522-discord-inworld-portal.html",
-    "title": "Draft: View the worlds and interact with people in VR without being in VR via a Discord Inward Portal",
+    "objectID": "decisions/20240905-revised-tracker-configuration-and-constraints.html#status",
+    "href": "decisions/20240905-revised-tracker-configuration-and-constraints.html#status",
+    "title": "Proposed: Revised Tracker Configuration and Constraints for HTC VIVE XR Elite",
     "section": "",
-    "text": "I want to see the worlds and interact with people in VR, without being in VR myself.\n\n\n\nA Discord voice/video call bot would allow players within the virtual world and outside to interact with each other.\n\n\n\nThis would be a bot client that connects to at least one server shard, and joins a Discord voice call, using WebRTC APIs to communicate voice and video data from Godot into discord.\n\n\n\n\nGrowing engagement with Groups\n\n\n\n\n\nRequires Discord\n\n\n\n\nPlayers can stream using OBS or discord screen sharing, but this requires players to do it, and only provides uni-directional communication.\n\n\n\nIt should be a standalone project based on Groups, but not core. The WebRTC dependency, if needed, would make integration difficult.\n\n\n\n\nhttps://discord.com/\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20240522-discord-inworld-portal.html#context-and-problem-statement",
-    "href": "decisions/20240522-discord-inworld-portal.html#context-and-problem-statement",
-    "title": "Draft: View the worlds and interact with people in VR without being in VR via a Discord Inward Portal",
+    "objectID": "decisions/20240905-revised-tracker-configuration-and-constraints.html#decision-makers",
+    "href": "decisions/20240905-revised-tracker-configuration-and-constraints.html#decision-makers",
+    "title": "Proposed: Revised Tracker Configuration and Constraints for HTC VIVE XR Elite",
     "section": "",
-    "text": "I want to see the worlds and interact with people in VR, without being in VR myself."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20240522-discord-inworld-portal.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20240522-discord-inworld-portal.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Draft: View the worlds and interact with people in VR without being in VR via a Discord Inward Portal",
+    "objectID": "decisions/20240905-revised-tracker-configuration-and-constraints.html#tags",
+    "href": "decisions/20240905-revised-tracker-configuration-and-constraints.html#tags",
+    "title": "Proposed: Revised Tracker Configuration and Constraints for HTC VIVE XR Elite",
     "section": "",
-    "text": "A Discord voice/video call bot would allow players within the virtual world and outside to interact with each other."
+    "text": "V-Sekai\nHTC VIVE XR Elite"
   },
   {
-    "objectID": "decisions/20240522-discord-inworld-portal.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240522-discord-inworld-portal.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Draft: View the worlds and interact with people in VR without being in VR via a Discord Inward Portal",
+    "objectID": "decisions/20240905-revised-tracker-configuration-and-constraints.html#further-reading",
+    "href": "decisions/20240905-revised-tracker-configuration-and-constraints.html#further-reading",
+    "title": "Proposed: Revised Tracker Configuration and Constraints for HTC VIVE XR Elite",
     "section": "",
-    "text": "This would be a bot client that connects to at least one server shard, and joins a Discord voice call, using WebRTC APIs to communicate voice and video data from Godot into discord."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240522-discord-inworld-portal.html#positive-consequences",
-    "href": "decisions/20240522-discord-inworld-portal.html#positive-consequences",
-    "title": "Draft: View the worlds and interact with people in VR without being in VR via a Discord Inward Portal",
+    "objectID": "decisions/20231024-finetuning-workflow.html",
+    "href": "decisions/20231024-finetuning-workflow.html",
+    "title": "Proposed: Enhancing Task-Specific Model Performance through Fine-Tuning with Axolotl",
     "section": "",
-    "text": "Growing engagement with Groups"
+    "text": "Status: Proposed\nDeciders: V-Sekai, fire\nTags: V-Sekai, Model Fine-tuning, Axolotl\n\n\n\n\nWe have multiple tasks each with a minimum of 100 samples and we want to fine-tune the latest models with our data. We are considering using the Axolotl library in a mode that batches the inputs.\n\n\n\nThe challenge is to effectively use these samples to fine-tune the model for each task without overfitting, while also ensuring that the model generalizes well to unseen data.\n\n\n\n\nData Preparation: First, we need to prepare our data for each task. This involves cleaning the data and splitting it into training and validation sets.\nModel Selection: Next, we select the latest models that we want to fine-tune. These could be models from Hugging Face’s model hub or any other source.\nFine-tuning with Axolotl: We will use the Axolotl library for fine-tuning. We can batch-mask our inputs to efficiently utilize our computational resources. This process will be repeated for each task.\nEvaluation: After fine-tuning, we evaluate the model on our validation set for each task to see how well it performs.\n\n\n\n\nBy fine-tuning the latest models on our specific tasks, we can potentially achieve better performance than using pre-trained models out-of-the-box. Also, Axolotl provides an easy-to-use interface for fine-tuning models.\n\n\n\nFine-tuning models requires computational resources and time. Also, with only 100 samples per task, there’s a risk of overfitting.\n\n\n\nAn alternative approach could be to use data augmentation techniques to increase the size of our dataset before fine-tuning.\n\n\n\nIf we have tasks that are infrequently performed, it might not be worth the effort to fine-tune a model specifically for these tasks.\n\n\n\nYes, this strategy involves us actively participating in the fine-tuning process.\n\n\n\n\nV-Sekai\nAxolotl\nAI assists this article."
   },
   {
-    "objectID": "decisions/20240522-discord-inworld-portal.html#negative-consequences",
-    "href": "decisions/20240522-discord-inworld-portal.html#negative-consequences",
-    "title": "Draft: View the worlds and interact with people in VR without being in VR via a Discord Inward Portal",
+    "objectID": "decisions/20231024-finetuning-workflow.html#metadata",
+    "href": "decisions/20231024-finetuning-workflow.html#metadata",
+    "title": "Proposed: Enhancing Task-Specific Model Performance through Fine-Tuning with Axolotl",
     "section": "",
-    "text": "Requires Discord"
+    "text": "Status: Proposed\nDeciders: V-Sekai, fire\nTags: V-Sekai, Model Fine-tuning, Axolotl"
   },
   {
-    "objectID": "decisions/20240522-discord-inworld-portal.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20240522-discord-inworld-portal.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Draft: View the worlds and interact with people in VR without being in VR via a Discord Inward Portal",
+    "objectID": "decisions/20231024-finetuning-workflow.html#the-backdrop",
+    "href": "decisions/20231024-finetuning-workflow.html#the-backdrop",
+    "title": "Proposed: Enhancing Task-Specific Model Performance through Fine-Tuning with Axolotl",
     "section": "",
-    "text": "Players can stream using OBS or discord screen sharing, but this requires players to do it, and only provides uni-directional communication."
+    "text": "We have multiple tasks each with a minimum of 100 samples and we want to fine-tune the latest models with our data. We are considering using the Axolotl library in a mode that batches the inputs."
   },
   {
-    "objectID": "decisions/20240522-discord-inworld-portal.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20240522-discord-inworld-portal.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Draft: View the worlds and interact with people in VR without being in VR via a Discord Inward Portal",
+    "objectID": "decisions/20231024-finetuning-workflow.html#the-challenge",
+    "href": "decisions/20231024-finetuning-workflow.html#the-challenge",
+    "title": "Proposed: Enhancing Task-Specific Model Performance through Fine-Tuning with Axolotl",
     "section": "",
-    "text": "It should be a standalone project based on Groups, but not core. The WebRTC dependency, if needed, would make integration difficult."
+    "text": "The challenge is to effectively use these samples to fine-tune the model for each task without overfitting, while also ensuring that the model generalizes well to unseen data."
   },
   {
-    "objectID": "decisions/20240522-discord-inworld-portal.html#references",
-    "href": "decisions/20240522-discord-inworld-portal.html#references",
-    "title": "Draft: View the worlds and interact with people in VR without being in VR via a Discord Inward Portal",
+    "objectID": "decisions/20231024-finetuning-workflow.html#the-strategy",
+    "href": "decisions/20231024-finetuning-workflow.html#the-strategy",
+    "title": "Proposed: Enhancing Task-Specific Model Performance through Fine-Tuning with Axolotl",
     "section": "",
-    "text": "https://discord.com/"
+    "text": "Data Preparation: First, we need to prepare our data for each task. This involves cleaning the data and splitting it into training and validation sets.\nModel Selection: Next, we select the latest models that we want to fine-tune. These could be models from Hugging Face’s model hub or any other source.\nFine-tuning with Axolotl: We will use the Axolotl library for fine-tuning. We can batch-mask our inputs to efficiently utilize our computational resources. This process will be repeated for each task.\nEvaluation: After fine-tuning, we evaluate the model on our validation set for each task to see how well it performs."
   },
   {
-    "objectID": "decisions/20240522-discord-inworld-portal.html#derivative-license",
-    "href": "decisions/20240522-discord-inworld-portal.html#derivative-license",
-    "title": "Draft: View the worlds and interact with people in VR without being in VR via a Discord Inward Portal",
+    "objectID": "decisions/20231024-finetuning-workflow.html#the-upside",
+    "href": "decisions/20231024-finetuning-workflow.html#the-upside",
+    "title": "Proposed: Enhancing Task-Specific Model Performance through Fine-Tuning with Axolotl",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "By fine-tuning the latest models on our specific tasks, we can potentially achieve better performance than using pre-trained models out-of-the-box. Also, Axolotl provides an easy-to-use interface for fine-tuning models."
   },
   {
-    "objectID": "decisions/20211031-stream-shader-motion.html",
-    "href": "decisions/20211031-stream-shader-motion.html",
-    "title": "Proposed: Stream shader motion",
+    "objectID": "decisions/20231024-finetuning-workflow.html#the-downside",
+    "href": "decisions/20231024-finetuning-workflow.html#the-downside",
+    "title": "Proposed: Enhancing Task-Specific Model Performance through Fine-Tuning with Axolotl",
     "section": "",
-    "text": "Proposed: Stream shader motion\n\nContext and Problem Statement\nWant to stream shader motion to multiple people.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nCreate a membrane Pipeline app for ShaderMotion and multiple people\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n\nfor each person send shader motion frames\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot trivial\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nI can move this forward.\n\n\nReferences\n\nMembrane framework\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Fine-tuning models requires computational resources and time. Also, with only 100 samples per task, there’s a risk of overfitting."
   },
   {
-    "objectID": "decisions/20211031-cicd-export-v-sekai.html",
-    "href": "decisions/20211031-cicd-export-v-sekai.html",
-    "title": "Proposed: CICD Export V-Sekai",
+    "objectID": "decisions/20231024-finetuning-workflow.html#the-road-not-taken",
+    "href": "decisions/20231024-finetuning-workflow.html#the-road-not-taken",
+    "title": "Proposed: Enhancing Task-Specific Model Performance through Fine-Tuning with Axolotl",
     "section": "",
-    "text": "Proposed: CICD Export V-Sekai\n\nContext and Problem Statement\nCICD Export V-Sekai\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nNeed to ship.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n\nGOCD\nDebug export bugs\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\n\nlots of devops work\n\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\n\nWe know how to do this.\n\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "An alternative approach could be to use data augmentation techniques to increase the size of our dataset before fine-tuning."
   },
   {
-    "objectID": "decisions/20230522-JOKE-fictional-blood-combat.html",
-    "href": "decisions/20230522-JOKE-fictional-blood-combat.html",
-    "title": "Rejected: Defeating your fictional enemies in their blood",
+    "objectID": "decisions/20231024-finetuning-workflow.html#the-infrequent-use-case",
+    "href": "decisions/20231024-finetuning-workflow.html#the-infrequent-use-case",
+    "title": "Proposed: Enhancing Task-Specific Model Performance through Fine-Tuning with Axolotl",
     "section": "",
-    "text": "Propose a solution to enhance realism in enemy defeat simulations.\n\n\n\nStatus: rejected \nDeciders: V-Sekai\nTags: V-Sekai, GPT-4, joke,\n\n\n\n\nGaming often involves defeating enemies, but current blood effects lack realism and immersion.\n\n\n\nImplement a realistic blood simulation system considering factors like enemy type, weapon, and environment.\n\n\n\n\nBlood simulation system: Develop a system generating realistic blood effects.\nIntegration: Ensure compatibility with existing game mechanics.\nOptimization: Minimize performance impact.\nTesting & refinement: Test extensively and refine based on feedback.\n\n\n\n\n\nEnhanced realism and immersion\nImproved visual effects\nIncreased player satisfaction\n\n\n\n\n\nIncreased development time and resources\nPotential performance issues\nUnsuitability for some games or audiences\n\n\n\n\n\nSimpler blood effect system\nPre-rendered blood effects only\n\n\n\n\nNo, significant development effort is required.\n\n\n\nEasier integration, optimization, control, and refinement as part of the core game engine.\n\n\n\n\nV-Sekai"
+    "text": "If we have tasks that are infrequently performed, it might not be worth the effort to fine-tune a model specifically for these tasks."
   },
   {
-    "objectID": "decisions/20230522-JOKE-fictional-blood-combat.html#metadata",
-    "href": "decisions/20230522-JOKE-fictional-blood-combat.html#metadata",
-    "title": "Rejected: Defeating your fictional enemies in their blood",
+    "objectID": "decisions/20231024-finetuning-workflow.html#in-core-and-done-by-us",
+    "href": "decisions/20231024-finetuning-workflow.html#in-core-and-done-by-us",
+    "title": "Proposed: Enhancing Task-Specific Model Performance through Fine-Tuning with Axolotl",
     "section": "",
-    "text": "Status: rejected \nDeciders: V-Sekai\nTags: V-Sekai, GPT-4, joke,"
+    "text": "Yes, this strategy involves us actively participating in the fine-tuning process."
   },
   {
-    "objectID": "decisions/20230522-JOKE-fictional-blood-combat.html#context-and-problem-statement",
-    "href": "decisions/20230522-JOKE-fictional-blood-combat.html#context-and-problem-statement",
-    "title": "Rejected: Defeating your fictional enemies in their blood",
+    "objectID": "decisions/20231024-finetuning-workflow.html#further-reading",
+    "href": "decisions/20231024-finetuning-workflow.html#further-reading",
+    "title": "Proposed: Enhancing Task-Specific Model Performance through Fine-Tuning with Axolotl",
     "section": "",
-    "text": "Gaming often involves defeating enemies, but current blood effects lack realism and immersion."
+    "text": "V-Sekai\nAxolotl\nAI assists this article."
   },
   {
-    "objectID": "decisions/20230522-JOKE-fictional-blood-combat.html#proposed-solution",
-    "href": "decisions/20230522-JOKE-fictional-blood-combat.html#proposed-solution",
-    "title": "Rejected: Defeating your fictional enemies in their blood",
+    "objectID": "decisions/20240330-gitlab-helm.html",
+    "href": "decisions/20240330-gitlab-helm.html",
+    "title": "Proposed: Integrating Helm for Kubernetes Runner Installation with S3 Cache",
     "section": "",
-    "text": "Implement a realistic blood simulation system considering factors like enemy type, weapon, and environment."
+    "text": "The V-Sekai project, focused on integrating social VR capabilities into the Godot Engine, necessitates a flexible and scalable CI/CD infrastructure to manage the development workflow across various environments effectively. Given the diversity of platforms our contributors use, including Linux, macOS, Windows, Docker, and Kubernetes, there is a critical need to standardize our CI/CD processes to ensure consistency and efficiency.\n\n\n\nThe current CI/CD setup at V-Sekai lacks a unified approach to deploying and managing runners in Kubernetes clusters, leading to potential inconsistencies in build and test environments. This fragmentation could slow down the development pipeline and impact the project’s ability to iterate rapidly on new features.\n\n\n\nWe propose to enhance our CI/CD pipeline by integrating Helm to streamline the installation and management of GitLab Runners in our Kubernetes clusters. Additionally, we will configure the runners to use S3 (Digital Ocean Spaces) as a cache, improving build times and reducing network traffic. Here’s how we plan to implement this solution:\n\n\nEnsure Helm is installed on your system. Helm will be used to deploy GitLab Runner instances as Helm charts, providing an easy and scalable way to manage runners within Kubernetes clusters.\ncurl https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3 | bash\n\n\n\nAdd the GitLab Runner Helm chart repository to your Helm setup. This repository contains the necessary templates for deploying GitLab Runners in a Kubernetes cluster.\nhelm repo add gitlab https://charts.gitlab.io/\nhelm repo update\n\n\n\nUpdate your values.yaml file with the following values to switch to the Ubuntu-based image and configure S3 as a cache:\n# Specify the Ubuntu image. Remember to set the version. You can also use the `ubuntu` or `latest` tags.\nimage: gitlab/gitlab-runner:v16.5.0\n\n# Update the security context values to the user ID in the ubuntu image\nsecurityContext:\n  fsGroup: 999\n  runAsUser: 999\n\n# Configure S3 as a cache\nrunners:\n  config: |\n    [[runners]]\n      [runners.kubernetes]\n        image = \"ubuntu:22.04\"\n      [runners.cache]\n        Type = \"s3\"\n        Path = \"runner\"\n        Shared = true\n        [runners.cache.s3]\n          ServerAddress = \"s3.amazonaws.com\"\n          BucketName = \"my_bucket_name\"\n          BucketLocation = \"eu-west-1\"\n          Insecure = false\n          AuthenticationType = \"access-key\"\n  cache:\n    secretName: s3access\n\n\n\nCreate an s3access Kubernetes secret that contains your access key and secret key:\nkubectl create secret generic s3access --from-literal=accesskey=\"YourAccessKey\" --from-literal=secretkey=\"YourSecretKey\"\n\n\n\nDeploy the GitLab Runner using Helm with the customized values.yaml file.\nhelm install gitlab-runner gitlab/gitlab-runner -f values.yaml\nEnsure to replace https://gitlab.example.com/ with your GitLab instance URL and \"REGISTRATION_TOKEN\" with your actual registration token.\n\n\n\n\n\nScalable and Efficient CI/CD: Leveraging Kubernetes for CI/CD runners allows for dynamic scaling based on the workload, improving resource efficiency.\nConsistency Across Environments: Using Helm charts for deployment ensures consistent environments for all CI/CD pipelines, reducing “it works on my machine” issues.\nImproved Build Times and Reduced Network Traffic: By using S3 as a cache, build times can be significantly reduced and network traffic minimized.\n\n\n\n\n\nComplexity: The initial setup and configuration may require a deep understanding of Kubernetes and Helm, posing a learning curve for some team members.\nMaintenance: Ongoing maintenance of Helm charts could increase operational overhead.\n\n\n\n\n\nManual Runner Installation: Avoided due to its lack of scalability and increased potential for configuration errors.\n\n\n\n\n\nTemporary or One-off CI/CD Tasks: For tasks that do not justify the overhead of Kubernetes runners, alternative, simpler CI/CD solutions might be temporarily employed.\n\n\n\n\nThis initiative aligns with our core mission of developing social VR capabilities within the Godot Engine. The V-Sekai development team will lead this project, ensuring it meets our technical standards and project goals.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai, CI/CD, Kubernetes, Helm, S3 Cache\n\n\n\n\n\nHelm Documentation\nGitLab Runner Helm Chart\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAssisted by Aria, your AI assistant."
   },
   {
-    "objectID": "decisions/20230522-JOKE-fictional-blood-combat.html#implementation",
-    "href": "decisions/20230522-JOKE-fictional-blood-combat.html#implementation",
-    "title": "Rejected: Defeating your fictional enemies in their blood",
+    "objectID": "decisions/20240330-gitlab-helm.html#context",
+    "href": "decisions/20240330-gitlab-helm.html#context",
+    "title": "Proposed: Integrating Helm for Kubernetes Runner Installation with S3 Cache",
     "section": "",
-    "text": "Blood simulation system: Develop a system generating realistic blood effects.\nIntegration: Ensure compatibility with existing game mechanics.\nOptimization: Minimize performance impact.\nTesting & refinement: Test extensively and refine based on feedback."
+    "text": "The V-Sekai project, focused on integrating social VR capabilities into the Godot Engine, necessitates a flexible and scalable CI/CD infrastructure to manage the development workflow across various environments effectively. Given the diversity of platforms our contributors use, including Linux, macOS, Windows, Docker, and Kubernetes, there is a critical need to standardize our CI/CD processes to ensure consistency and efficiency."
   },
   {
-    "objectID": "decisions/20230522-JOKE-fictional-blood-combat.html#positive-consequences",
-    "href": "decisions/20230522-JOKE-fictional-blood-combat.html#positive-consequences",
-    "title": "Rejected: Defeating your fictional enemies in their blood",
+    "objectID": "decisions/20240330-gitlab-helm.html#problem-statement",
+    "href": "decisions/20240330-gitlab-helm.html#problem-statement",
+    "title": "Proposed: Integrating Helm for Kubernetes Runner Installation with S3 Cache",
     "section": "",
-    "text": "Enhanced realism and immersion\nImproved visual effects\nIncreased player satisfaction"
+    "text": "The current CI/CD setup at V-Sekai lacks a unified approach to deploying and managing runners in Kubernetes clusters, leading to potential inconsistencies in build and test environments. This fragmentation could slow down the development pipeline and impact the project’s ability to iterate rapidly on new features."
   },
   {
-    "objectID": "decisions/20230522-JOKE-fictional-blood-combat.html#negative-consequences",
-    "href": "decisions/20230522-JOKE-fictional-blood-combat.html#negative-consequences",
-    "title": "Rejected: Defeating your fictional enemies in their blood",
+    "objectID": "decisions/20240330-gitlab-helm.html#proposed-solution",
+    "href": "decisions/20240330-gitlab-helm.html#proposed-solution",
+    "title": "Proposed: Integrating Helm for Kubernetes Runner Installation with S3 Cache",
     "section": "",
-    "text": "Increased development time and resources\nPotential performance issues\nUnsuitability for some games or audiences"
+    "text": "We propose to enhance our CI/CD pipeline by integrating Helm to streamline the installation and management of GitLab Runners in our Kubernetes clusters. Additionally, we will configure the runners to use S3 (Digital Ocean Spaces) as a cache, improving build times and reducing network traffic. Here’s how we plan to implement this solution:\n\n\nEnsure Helm is installed on your system. Helm will be used to deploy GitLab Runner instances as Helm charts, providing an easy and scalable way to manage runners within Kubernetes clusters.\ncurl https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3 | bash\n\n\n\nAdd the GitLab Runner Helm chart repository to your Helm setup. This repository contains the necessary templates for deploying GitLab Runners in a Kubernetes cluster.\nhelm repo add gitlab https://charts.gitlab.io/\nhelm repo update\n\n\n\nUpdate your values.yaml file with the following values to switch to the Ubuntu-based image and configure S3 as a cache:\n# Specify the Ubuntu image. Remember to set the version. You can also use the `ubuntu` or `latest` tags.\nimage: gitlab/gitlab-runner:v16.5.0\n\n# Update the security context values to the user ID in the ubuntu image\nsecurityContext:\n  fsGroup: 999\n  runAsUser: 999\n\n# Configure S3 as a cache\nrunners:\n  config: |\n    [[runners]]\n      [runners.kubernetes]\n        image = \"ubuntu:22.04\"\n      [runners.cache]\n        Type = \"s3\"\n        Path = \"runner\"\n        Shared = true\n        [runners.cache.s3]\n          ServerAddress = \"s3.amazonaws.com\"\n          BucketName = \"my_bucket_name\"\n          BucketLocation = \"eu-west-1\"\n          Insecure = false\n          AuthenticationType = \"access-key\"\n  cache:\n    secretName: s3access\n\n\n\nCreate an s3access Kubernetes secret that contains your access key and secret key:\nkubectl create secret generic s3access --from-literal=accesskey=\"YourAccessKey\" --from-literal=secretkey=\"YourSecretKey\"\n\n\n\nDeploy the GitLab Runner using Helm with the customized values.yaml file.\nhelm install gitlab-runner gitlab/gitlab-runner -f values.yaml\nEnsure to replace https://gitlab.example.com/ with your GitLab instance URL and \"REGISTRATION_TOKEN\" with your actual registration token."
   },
   {
-    "objectID": "decisions/20230522-JOKE-fictional-blood-combat.html#option-graveyard",
-    "href": "decisions/20230522-JOKE-fictional-blood-combat.html#option-graveyard",
-    "title": "Rejected: Defeating your fictional enemies in their blood",
+    "objectID": "decisions/20240330-gitlab-helm.html#benefits",
+    "href": "decisions/20240330-gitlab-helm.html#benefits",
+    "title": "Proposed: Integrating Helm for Kubernetes Runner Installation with S3 Cache",
     "section": "",
-    "text": "Simpler blood effect system\nPre-rendered blood effects only"
+    "text": "Scalable and Efficient CI/CD: Leveraging Kubernetes for CI/CD runners allows for dynamic scaling based on the workload, improving resource efficiency.\nConsistency Across Environments: Using Helm charts for deployment ensures consistent environments for all CI/CD pipelines, reducing “it works on my machine” issues.\nImproved Build Times and Reduced Network Traffic: By using S3 as a cache, build times can be significantly reduced and network traffic minimized."
   },
   {
-    "objectID": "decisions/20230522-JOKE-fictional-blood-combat.html#script-workaround",
-    "href": "decisions/20230522-JOKE-fictional-blood-combat.html#script-workaround",
-    "title": "Rejected: Defeating your fictional enemies in their blood",
+    "objectID": "decisions/20240330-gitlab-helm.html#downsides",
+    "href": "decisions/20240330-gitlab-helm.html#downsides",
+    "title": "Proposed: Integrating Helm for Kubernetes Runner Installation with S3 Cache",
     "section": "",
-    "text": "No, significant development effort is required."
+    "text": "Complexity: The initial setup and configuration may require a deep understanding of Kubernetes and Helm, posing a learning curve for some team members.\nMaintenance: Ongoing maintenance of Helm charts could increase operational overhead."
   },
   {
-    "objectID": "decisions/20230522-JOKE-fictional-blood-combat.html#core-implementation-rationale",
-    "href": "decisions/20230522-JOKE-fictional-blood-combat.html#core-implementation-rationale",
-    "title": "Rejected: Defeating your fictional enemies in their blood",
+    "objectID": "decisions/20240330-gitlab-helm.html#alternatives-not-chosen",
+    "href": "decisions/20240330-gitlab-helm.html#alternatives-not-chosen",
+    "title": "Proposed: Integrating Helm for Kubernetes Runner Installation with S3 Cache",
     "section": "",
-    "text": "Easier integration, optimization, control, and refinement as part of the core game engine."
+    "text": "Manual Runner Installation: Avoided due to its lack of scalability and increased potential for configuration errors."
   },
   {
-    "objectID": "decisions/20230522-JOKE-fictional-blood-combat.html#references",
-    "href": "decisions/20230522-JOKE-fictional-blood-combat.html#references",
-    "title": "Rejected: Defeating your fictional enemies in their blood",
+    "objectID": "decisions/20240330-gitlab-helm.html#infrequent-use-case",
+    "href": "decisions/20240330-gitlab-helm.html#infrequent-use-case",
+    "title": "Proposed: Integrating Helm for Kubernetes Runner Installation with S3 Cache",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Temporary or One-off CI/CD Tasks: For tasks that do not justify the overhead of Kubernetes runners, alternative, simpler CI/CD solutions might be temporarily employed."
   },
   {
-    "objectID": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html",
-    "href": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html",
-    "title": "Accepted: Aquarium Nightclub Booth for Virtual Market Exhibition",
+    "objectID": "decisions/20240330-gitlab-helm.html#in-core-and-done-by-us",
+    "href": "decisions/20240330-gitlab-helm.html#in-core-and-done-by-us",
+    "title": "Proposed: Integrating Helm for Kubernetes Runner Installation with S3 Cache",
     "section": "",
-    "text": "Status: accepted \nDeciders: V-Sekai, fire, etc, Aeris, cyberpunkmermaid,\nTags: V-Sekai, GPT-4, Virtual Reality, Cocoon Art Aquarium, VKET 2023 Summer, Voiceless,\n\n\n\n\nDesign a 4m x 4m x 5m Aquarium Nightclub themed booth.\n\n\n\nCreate an immersive environment combining aquarium and nightclub elements, including aquatic decorations, lighting, interactivity, a hostess, and ambient music.\n\n\n\nAquatic-themed decorations: Use 3D models of marine life, such as fish, corals, and seaweed, to create a colorful underwater environment.\nImplement the ambience of a nightclub.\nInteractive elements: Add interactive components, such as touch-sensitive screens or motion sensors, to allow visitors to interact with the marine life and control the lighting effects.\nJellyfish Hostess:\n\nJellyBell: Enchanting hostess engaging visitors in the booth experience.\nIridescent Gown: Amplifies her aquatic charm with sheer fabric and ribbons\n\nAmbient music: Include background music that complements the aquarium and nightclub themes.\n\n\n\n\n\n\nDesign and model 3D assets.\nImplement interactive elements.\nAdd hostess character.\nIntegrate ambient music.\n\n\n\n\n\nUnique and engaging theme attracts visitors.\nImmersive experience combines education and entertainment.\nEncourages interaction and exploration.\nHostess enhances visitor engagement.\n\n\n\n\n\nRequires significant development time and resources.\nBalancing two themes may be challenging.\nIntegrating dynamic lighting and shaders may require extra effort.\n\n\n\n\n\nStatic environment without interactivity.\nFocusing on one theme only.\n\n\n\n\nNo, requires significant design and development work.\n\n\n\nCreating a unique booth is essential for attracting visitors and showcasing VR development capabilities.\n\n\n\n\nV-Sekai\nVKET 2023 Summer\nSilent’s Cel Shading Shader"
+    "text": "This initiative aligns with our core mission of developing social VR capabilities within the Godot Engine. The V-Sekai development team will lead this project, ensuring it meets our technical standards and project goals."
   },
   {
-    "objectID": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html#metadata",
-    "href": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html#metadata",
-    "title": "Accepted: Aquarium Nightclub Booth for Virtual Market Exhibition",
+    "objectID": "decisions/20240330-gitlab-helm.html#status",
+    "href": "decisions/20240330-gitlab-helm.html#status",
+    "title": "Proposed: Integrating Helm for Kubernetes Runner Installation with S3 Cache",
     "section": "",
-    "text": "Status: accepted \nDeciders: V-Sekai, fire, etc, Aeris, cyberpunkmermaid,\nTags: V-Sekai, GPT-4, Virtual Reality, Cocoon Art Aquarium, VKET 2023 Summer, Voiceless,"
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html#context-and-problem-statement",
-    "href": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html#context-and-problem-statement",
-    "title": "Accepted: Aquarium Nightclub Booth for Virtual Market Exhibition",
+    "objectID": "decisions/20240330-gitlab-helm.html#decision-makers",
+    "href": "decisions/20240330-gitlab-helm.html#decision-makers",
+    "title": "Proposed: Integrating Helm for Kubernetes Runner Installation with S3 Cache",
     "section": "",
-    "text": "Design a 4m x 4m x 5m Aquarium Nightclub themed booth."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html#proposed-solution",
-    "href": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html#proposed-solution",
-    "title": "Accepted: Aquarium Nightclub Booth for Virtual Market Exhibition",
+    "objectID": "decisions/20240330-gitlab-helm.html#tags",
+    "href": "decisions/20240330-gitlab-helm.html#tags",
+    "title": "Proposed: Integrating Helm for Kubernetes Runner Installation with S3 Cache",
     "section": "",
-    "text": "Create an immersive environment combining aquarium and nightclub elements, including aquatic decorations, lighting, interactivity, a hostess, and ambient music.\n\n\n\nAquatic-themed decorations: Use 3D models of marine life, such as fish, corals, and seaweed, to create a colorful underwater environment.\nImplement the ambience of a nightclub.\nInteractive elements: Add interactive components, such as touch-sensitive screens or motion sensors, to allow visitors to interact with the marine life and control the lighting effects.\nJellyfish Hostess:\n\nJellyBell: Enchanting hostess engaging visitors in the booth experience.\nIridescent Gown: Amplifies her aquatic charm with sheer fabric and ribbons\n\nAmbient music: Include background music that complements the aquarium and nightclub themes."
+    "text": "V-Sekai, CI/CD, Kubernetes, Helm, S3 Cache"
   },
   {
-    "objectID": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html#implementation",
-    "href": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html#implementation",
-    "title": "Accepted: Aquarium Nightclub Booth for Virtual Market Exhibition",
+    "objectID": "decisions/20240330-gitlab-helm.html#further-reading",
+    "href": "decisions/20240330-gitlab-helm.html#further-reading",
+    "title": "Proposed: Integrating Helm for Kubernetes Runner Installation with S3 Cache",
     "section": "",
-    "text": "Design and model 3D assets.\nImplement interactive elements.\nAdd hostess character.\nIntegrate ambient music."
+    "text": "Helm Documentation\nGitLab Runner Helm Chart\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAssisted by Aria, your AI assistant."
   },
   {
-    "objectID": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html#positive-consequences",
-    "href": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html#positive-consequences",
-    "title": "Accepted: Aquarium Nightclub Booth for Virtual Market Exhibition",
+    "objectID": "decisions/20220113-change-transform-by-crdt.html",
+    "href": "decisions/20220113-change-transform-by-crdt.html",
+    "title": "Proposal: Change transform by CRDT.",
     "section": "",
-    "text": "Unique and engaging theme attracts visitors.\nImmersive experience combines education and entertainment.\nEncourages interaction and exploration.\nHostess enhances visitor engagement."
+    "text": "Status: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nChange transform and resolve conflict.\n\n\n\n???\n\n\n\n???\n\n\n\n\n???\n\n\n\n\n\n???\n\n\n\n\n\nOption: Status quo\nRejection Reason: ???\n\n\n\n\nNot small.\n\n\n\n\nResearch.\n\n\n\n\n\nhttps://github.com/gritzko/ron\nDescribed in Webaverse.\n\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html#negative-consequences",
-    "href": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html#negative-consequences",
-    "title": "Accepted: Aquarium Nightclub Booth for Virtual Market Exhibition",
+    "objectID": "decisions/20220113-change-transform-by-crdt.html#context-and-problem-statement",
+    "href": "decisions/20220113-change-transform-by-crdt.html#context-and-problem-statement",
+    "title": "Proposal: Change transform by CRDT.",
     "section": "",
-    "text": "Requires significant development time and resources.\nBalancing two themes may be challenging.\nIntegrating dynamic lighting and shaders may require extra effort."
+    "text": "Change transform and resolve conflict."
   },
   {
-    "objectID": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html#option-graveyard",
-    "href": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html#option-graveyard",
-    "title": "Accepted: Aquarium Nightclub Booth for Virtual Market Exhibition",
+    "objectID": "decisions/20220113-change-transform-by-crdt.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20220113-change-transform-by-crdt.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposal: Change transform by CRDT.",
     "section": "",
-    "text": "Static environment without interactivity.\nFocusing on one theme only."
+    "text": "???"
   },
   {
-    "objectID": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Accepted: Aquarium Nightclub Booth for Virtual Market Exhibition",
+    "objectID": "decisions/20220113-change-transform-by-crdt.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20220113-change-transform-by-crdt.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposal: Change transform by CRDT.",
     "section": "",
-    "text": "No, requires significant design and development work."
+    "text": "???"
   },
   {
-    "objectID": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Accepted: Aquarium Nightclub Booth for Virtual Market Exhibition",
+    "objectID": "decisions/20220113-change-transform-by-crdt.html#positive-consequences",
+    "href": "decisions/20220113-change-transform-by-crdt.html#positive-consequences",
+    "title": "Proposal: Change transform by CRDT.",
     "section": "",
-    "text": "Creating a unique booth is essential for attracting visitors and showcasing VR development capabilities."
+    "text": "???"
   },
   {
-    "objectID": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html#references",
-    "href": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html#references",
-    "title": "Accepted: Aquarium Nightclub Booth for Virtual Market Exhibition",
+    "objectID": "decisions/20220113-change-transform-by-crdt.html#negative-consequences",
+    "href": "decisions/20220113-change-transform-by-crdt.html#negative-consequences",
+    "title": "Proposal: Change transform by CRDT.",
     "section": "",
-    "text": "V-Sekai\nVKET 2023 Summer\nSilent’s Cel Shading Shader"
+    "text": "???"
   },
   {
-    "objectID": "decisions/20220222-rank-bone-names-with-transformer.html",
-    "href": "decisions/20220222-rank-bone-names-with-transformer.html",
-    "title": "Accepted: Rank skeleton #bone names with transformer4rec",
+    "objectID": "decisions/20220113-change-transform-by-crdt.html#option-graveyard",
+    "href": "decisions/20220113-change-transform-by-crdt.html#option-graveyard",
+    "title": "Proposal: Change transform by CRDT.",
     "section": "",
-    "text": "Status: accepted \n\n\n\nImprove automatic #bone selection\n\n\n\nUse transformer4rec to rank bones.\n\n\n\n\nInvestigate\nlibtorch?\n\n\n\n\n\nWe can guess the proper name.\nUseful for the facial mapping problem?\nUseful for the character generator slider recommendation problem?\nGenerate test data by moving the character\nInference requires only single pose inputs.\n\n\n\n\n\nStarring at the abyss.\n\n\n\n\n\nOption:\n\nbpr from Quora\n\nRejection Reason:\n\nBpr from Quora is not used in production.\n\nOption:\n\ndlrm from facebook\n\nRejection Reason:\n\nToo difficult to run\n\nOption:\n\ncatboost\n\nRejection Reason:\n\nToo difficult to run\n\n\n\n\n\nNot a few lines of code.\n\n\n\nWe need this to make the quality of life of creators better.\n\n\n\n\nhttps://github.com/BayesWitnesses/m2cgen\nhttps://stackoverflow.com/questions/36071672/using-xgboost-in-c\nhttps://github.com/facebookresearch/dlrm\nhttps://medium.com/@marthawhite_81346/learning-with-the-criteo-tb-dataset-e3ec12d9d77e\nhttps://www.kaggle.com/c/criteo-display-ad-challenge/data\nSkeleton pool operator from neural blend shapes.\nhttps://tailor.fandom.com/wiki/Types_of_measurement\nhttps://knarkowicz.wordpress.com/2014/04/16/octahedron-normal-vector-encoding/\nhttps://www.kaggle.com/egordm/deep-learning-recommendation-model-dlrm\n\n    @article{li2021learning,\n    author = {Li, Peizhuo and Aberman, Kfir and Hanocka, Rana and Liu, Libin and Sorkine-Hornung, Olga and Chen, Baoquan},\n    title = {Learning Skeletal Articulations with Neural Blend Shapes},\n    journal = {ACM Transactions on Graphics (TOG)},\n    volume = {40},\n    number = {4},\n    pages = {1},\n    year = {2021},\n    publisher = {ACM}\n    }\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.\n\n\n\n\nSupersedes 20211031-use-bpr-to-rank-skeleton-bone-names"
+    "text": "Option: Status quo\nRejection Reason: ???"
   },
   {
-    "objectID": "decisions/20220222-rank-bone-names-with-transformer.html#context-and-problem-statement",
-    "href": "decisions/20220222-rank-bone-names-with-transformer.html#context-and-problem-statement",
-    "title": "Accepted: Rank skeleton #bone names with transformer4rec",
+    "objectID": "decisions/20220113-change-transform-by-crdt.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20220113-change-transform-by-crdt.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposal: Change transform by CRDT.",
     "section": "",
-    "text": "Improve automatic #bone selection"
+    "text": "Not small."
   },
   {
-    "objectID": "decisions/20220222-rank-bone-names-with-transformer.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20220222-rank-bone-names-with-transformer.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Accepted: Rank skeleton #bone names with transformer4rec",
+    "objectID": "decisions/20220113-change-transform-by-crdt.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20220113-change-transform-by-crdt.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposal: Change transform by CRDT.",
     "section": "",
-    "text": "Use transformer4rec to rank bones."
+    "text": "Research."
   },
   {
-    "objectID": "decisions/20220222-rank-bone-names-with-transformer.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20220222-rank-bone-names-with-transformer.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Accepted: Rank skeleton #bone names with transformer4rec",
+    "objectID": "decisions/20220113-change-transform-by-crdt.html#references",
+    "href": "decisions/20220113-change-transform-by-crdt.html#references",
+    "title": "Proposal: Change transform by CRDT.",
     "section": "",
-    "text": "Investigate\nlibtorch?"
+    "text": "https://github.com/gritzko/ron\nDescribed in Webaverse."
   },
   {
-    "objectID": "decisions/20220222-rank-bone-names-with-transformer.html#positive-consequences",
-    "href": "decisions/20220222-rank-bone-names-with-transformer.html#positive-consequences",
-    "title": "Accepted: Rank skeleton #bone names with transformer4rec",
+    "objectID": "decisions/20220113-change-transform-by-crdt.html#derivative-license",
+    "href": "decisions/20220113-change-transform-by-crdt.html#derivative-license",
+    "title": "Proposal: Change transform by CRDT.",
     "section": "",
-    "text": "We can guess the proper name.\nUseful for the facial mapping problem?\nUseful for the character generator slider recommendation problem?\nGenerate test data by moving the character\nInference requires only single pose inputs."
+    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20220222-rank-bone-names-with-transformer.html#negative-consequences",
-    "href": "decisions/20220222-rank-bone-names-with-transformer.html#negative-consequences",
-    "title": "Accepted: Rank skeleton #bone names with transformer4rec",
+    "objectID": "decisions/20230125-grow-the-community-with-a-reactive-discord-bot.html",
+    "href": "decisions/20230125-grow-the-community-with-a-reactive-discord-bot.html",
+    "title": "Proposed: Grow the community with a reactive Discord bot.",
     "section": "",
-    "text": "Starring at the abyss."
+    "text": "Proposed: Grow the community with a reactive Discord bot.\n\nMetadata\n\nStatus: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nContext and Problem Statement\nV-Sekai discord is cumbersome to use.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nGrant the “Member” role to all members who click a reaction from the Discord bot.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nWe need to review the code and set up a runner in kubernetes.\n\n\nPositive Consequences\nWe are able to use the community easier.\n\n\nNegative Consequences\nWe cannot get other features in.\n\n\nOption graveyard\n\nOption: The status quo. \nRejection Reason: This solves nothing. \nOption: Use discord’s standard moderation tools with mass ban. \nRejection Reason: This is actually a good feature. Need to re-evaluate. \n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nKnowing what to do is hard.\n\n\nIs there a reason why this should be core and done by us?\nWe administrate the V-Sekai Discord.\n\n\nReferences\n\nV-Sekai\nVSona"
   },
   {
-    "objectID": "decisions/20220222-rank-bone-names-with-transformer.html#option-graveyard",
-    "href": "decisions/20220222-rank-bone-names-with-transformer.html#option-graveyard",
-    "title": "Accepted: Rank skeleton #bone names with transformer4rec",
+    "objectID": "decisions/20230125-two-groups-battle-demo.html",
+    "href": "decisions/20230125-two-groups-battle-demo.html",
+    "title": "Proposed: Have two groups move towards each other battle demo",
     "section": "",
-    "text": "Option:\n\nbpr from Quora\n\nRejection Reason:\n\nBpr from Quora is not used in production.\n\nOption:\n\ndlrm from facebook\n\nRejection Reason:\n\nToo difficult to run\n\nOption:\n\ncatboost\n\nRejection Reason:\n\nToo difficult to run"
+    "text": "Status: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\n\nWe need a demo of our work.\n\n\n\nMake a game out of having two groups attack each other.\n\n\n\n\nCreate two groups: mass A and mass B\nImplement pathfinding for both groups to find each other\nAdd avoidance behavior to prevent collisions between group members\nImplement attack functionality when groups are in range\n\nfunction createGroups() {\n  massA = createGroupA();\n  massB = createGroupB();\n}\n\nfunction update() {\n  pathfind(massA, massB);\n  pathfind(massB, massA);\n\n  avoidance(massA);\n  avoidance(massB);\n\n  attack(massA, massB);\n  attack(massB, massA);\n}\n\n\n\n\nCan use WebAssembly (WASM) scripting\nIn-game tablet drag to place objects\n\n\n\n\nWe are able to use V-Sekai easier.\n\n\n\n\n\nWe cannot get other features in.\n\n\n\n\n\nOption: The status quo.\nRejection Reason: This solves nothing.\n\n\n\n\nThis is an integration test.\n\n\n\nIt helps us focus.\n\n\n\n\nV-Sekai\nrenown"
   },
   {
-    "objectID": "decisions/20220222-rank-bone-names-with-transformer.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20220222-rank-bone-names-with-transformer.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Accepted: Rank skeleton #bone names with transformer4rec",
+    "objectID": "decisions/20230125-two-groups-battle-demo.html#additional-features-for-the-test",
+    "href": "decisions/20230125-two-groups-battle-demo.html#additional-features-for-the-test",
+    "title": "Proposed: Have two groups move towards each other battle demo",
     "section": "",
-    "text": "Not a few lines of code."
+    "text": "Can use WebAssembly (WASM) scripting\nIn-game tablet drag to place objects\n\n\n\n\nWe are able to use V-Sekai easier.\n\n\n\n\n\nWe cannot get other features in.\n\n\n\n\n\nOption: The status quo.\nRejection Reason: This solves nothing.\n\n\n\n\nThis is an integration test.\n\n\n\nIt helps us focus.\n\n\n\n\nV-Sekai\nrenown"
   },
   {
-    "objectID": "decisions/20220222-rank-bone-names-with-transformer.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20220222-rank-bone-names-with-transformer.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Accepted: Rank skeleton #bone names with transformer4rec",
+    "objectID": "decisions/20230415-procedural-variations-props-envs-avatars.html",
+    "href": "decisions/20230415-procedural-variations-props-envs-avatars.html",
+    "title": "Proposed: Procedurally create variations for our props, environments and avatars",
     "section": "",
-    "text": "We need this to make the quality of life of creators better."
+    "text": "Proposed: Procedurally create variations for our props, environments and avatars\n\nMetadata\n\nStatus: proposed \nDeciders: V-Sekai,fire,\nTags: V-Sekai,chatgp4,\n\n\n\nContext and Problem Statement\nLack of variety and customization in V-Sekai’s 3D props, environments, and avatars.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nIntroducing a procedural generator for 3D props, environments, and avatars in V-Sekai will significantly enhance user experience by offering a broad range of customizable options. Procedural generation is an algorithmic method of content creation that replaces manual design, resulting in a larger array of unique combinations.\nThe procedural generator can be developed using a mix of algorithms, libraries, and assets to produce a vast assortment of variations for props, environments, and avatars. Users’ input parameters, such as prop type, color, size, and material, will guide the generator in crafting distinctive content.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\ngraph TD\n  A[Prop Type] --&gt; B(Select Base Model)\n  A[Prop Type] --&gt; C(Apply Procedural Variations)\n  A[Prop Type] --&gt; D(Combine Variations)\n  B --&gt; E(Base Model)\n  C --&gt; F(Shape Variation)\n  C --&gt; G(Color Variation)\n  C --&gt; H(Texture Variation)\n  F --&gt; I(Combined Variations)\n  G --&gt; I(Combined Variations)\n  H --&gt; I(Combined Variations)\n  E --&gt; I(Combined Variations)\n  I --&gt; J(Final Output)\nThis flowchart demonstrates the procedural generation process using the following steps:\n\nUser Input Parameters: Users provide their preferences for prop type, color, size, and material.\nSelect Base Model: The generator selects a base model corresponding to the chosen prop type.\nApply Procedural Variations: The generator applies algorithmic variations to the base model, modifying its shape, color, and texture based on user input.\nCombine Variations: The generator combines these variations to create a unique prop with the specified properties.\nGenerate Unique Prop, Environment, or Avatar: The final output is a unique prop, environment, or avatar that meets the user’s preferences.\n\nThis approach increases the variety and customization options in V-Sekai, enhancing the platform’s appeal and offering a more engaging experience for users.\n\n\nPositive Consequences\n\nEnhanced variety: Procedural generation enables a wide array of unique content, delivering a diverse and constantly evolving experience for users.\nUser personalization: By incorporating user preferences, the generator can produce content that aligns with individual tastes and needs.\nEfficient resource utilization: Procedural content generation minimizes the need for manual design and asset creation, leading to a more cost-effective platform.\n\n\n\nNegative Consequences\n\nComplexity: Developing a procedural generator can be intricate, necessitating expertise in algorithms, 3D modeling, and other technical domains.\nPerformance impact: Real-time content generation might affect performance, particularly if algorithms are not optimized or if the platform experiences high user traffic.\n\n\n\nOption graveyard\nDo nothing.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nThis is a few lines of code.\n\n\nIs there a reason why this should be core and done by us?\nWe care about v-sekai more than others.\n\n\nReferences\n\nV-Sekai"
   },
   {
-    "objectID": "decisions/20220222-rank-bone-names-with-transformer.html#references",
-    "href": "decisions/20220222-rank-bone-names-with-transformer.html#references",
-    "title": "Accepted: Rank skeleton #bone names with transformer4rec",
+    "objectID": "decisions/20230502-add-iree-to-godot-engine-for-image-superresolution.html",
+    "href": "decisions/20230502-add-iree-to-godot-engine-for-image-superresolution.html",
+    "title": "Accepted: Adding IREE to Godot Engine for Image Superresolution",
     "section": "",
-    "text": "https://github.com/BayesWitnesses/m2cgen\nhttps://stackoverflow.com/questions/36071672/using-xgboost-in-c\nhttps://github.com/facebookresearch/dlrm\nhttps://medium.com/@marthawhite_81346/learning-with-the-criteo-tb-dataset-e3ec12d9d77e\nhttps://www.kaggle.com/c/criteo-display-ad-challenge/data\nSkeleton pool operator from neural blend shapes.\nhttps://tailor.fandom.com/wiki/Types_of_measurement\nhttps://knarkowicz.wordpress.com/2014/04/16/octahedron-normal-vector-encoding/\nhttps://www.kaggle.com/egordm/deep-learning-recommendation-model-dlrm\n\n    @article{li2021learning,\n    author = {Li, Peizhuo and Aberman, Kfir and Hanocka, Rana and Liu, Libin and Sorkine-Hornung, Olga and Chen, Baoquan},\n    title = {Learning Skeletal Articulations with Neural Blend Shapes},\n    journal = {ACM Transactions on Graphics (TOG)},\n    volume = {40},\n    number = {4},\n    pages = {1},\n    year = {2021},\n    publisher = {ACM}\n    }"
+    "text": "Accepted: Adding IREE to Godot Engine for Image Superresolution\n\nMetadata\n\nStatus: accepted \nDeciders: V-Sekai,fire,\nTags: V-Sekai, IREE, Godot Engine, Image Superresolution, Vulkan Backend,chatgpt 4,Google,\n\n\n\nContext and Problem Statement\nV-Sekai currently faces a limitation in the quality of upscaled images, particularly when the image needs to be magnified by a factor of 4x or more.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nIntegrate the Intermediate Representation Execution Environment (IREE) into the Godot Engine 4.0 as a C++ GDExtension. Utilize the Vulkan backend to run an image superresolution demo that generates 4x larger images. IREE is an MLIR-based end-to-end compiler and runtime that lowers Machine Learning (ML) models to a unified IR, allowing for better performance and scaling.\n\n\nDescribe how your proposal will work with code, pseudo-code, mock-ups, or diagrams\n\nCompile IREE as a C++ GDExtension for Godot Engine 4.0.\nUse the Vulkan backend to run the image superresolution demo.\nLoad and process ML models for image superresolution using IREE.\nIntegrate the resulting functionality into V-Sekai’s existing image processing pipeline.\n\n\n\nPositive Consequences\n\nAllow image superresolution in V-Sekai.\nEnhanced performance due to IREE’s efficient MLIR-based compiler and runtime.\nScalable solution that adapts to various hardware and software constraints. Not only NVIDIA, but ARM, Intel, AMD and Apple gpus.\nAllow using other machine learning models from PyTorch and Tensorflow\n\n\n\nNegative Consequences\n\nAdditional development time required for integration and optimization.\nPotential trade-offs in implementing other features.\n\n\n\nOption graveyard\n\nUse a custom script to work around the image superresolution issue.\n\nThis might not provide a scalable or high-performance solution.\n\nImplement a different image superresolution algorithm.\n\nThis could lead to suboptimal results compared to IREE’s capabilities.\n\n\n\n\nIf this enhancement will be used infrequently, can it be worked around with a few lines of script?\nA custom script could serve as a workaround for infrequent use of image superresolution, but it may have drawbacks in terms of efficiency, output quality, and maintenance efforts. If the feature aligns with V-Sekai’s goals and significantly improves user experience, integrating the IREE-based solution into the core might be more effective.\n\n\nIs there a reason why this should be core and done by us?\nIn summary, integrating the IREE-based image superresolution feature into V-Sekai’s core offers several benefits, including an enhanced user experience, performance optimization, alignment with open source values, and easier maintenance and support. These advantages contribute to a better, more immersive VR experience while staying true to V-Sekai’s project goals.\n\n\nReferences\n\nV-Sekai: https://v-sekai.org/\nIREE (Intermediate Representation Execution Environment): https://github.com/openxla/iree\nGodot Engine: https://godotengine.org\nVulkan Backend: https://www.khronos.org/vulkan/\nIREE.gd: https://github.com/RechieKho/IREE.gd"
   },
   {
-    "objectID": "decisions/20220222-rank-bone-names-with-transformer.html#derivative-license",
-    "href": "decisions/20220222-rank-bone-names-with-transformer.html#derivative-license",
-    "title": "Accepted: Rank skeleton #bone names with transformer4rec",
+    "objectID": "decisions/20211108-integrate-with-blender.html",
+    "href": "decisions/20211108-integrate-with-blender.html",
+    "title": "Proposed: Integrate with blender",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Status: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nBlend files are too difficult to write an importer for in Godot Engine.\n\n\n\nMake an addon that calls Blender directly and tell it to export to the proper place.\n\n\n\n\nEnable addon\nOpen blend\nSee the blend as a Godot Engine scene.\n\n\n\n\n\nIntegrates Blender into Godot Engine workflows.\nDownside of Blender version updates can be fixed by the use of the V-Sekai exporter tool.\n\n\n\n\n\nRequires blender to export cicd.\nChanges to the Blender version causes the project to desync.\n\n\n\n\n\nOption: \nRejection Reason: \n\n\n\n\n\nThis is a script but not a few lines.\n\n\n\n\nI know how to do this and others don’t.\n\n\n\n\nhttps://www.blender.org/\nhttps://github.com/V-Sekai/godot-blender\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20220222-rank-bone-names-with-transformer.html#links",
-    "href": "decisions/20220222-rank-bone-names-with-transformer.html#links",
-    "title": "Accepted: Rank skeleton #bone names with transformer4rec",
+    "objectID": "decisions/20211108-integrate-with-blender.html#context-and-problem-statement",
+    "href": "decisions/20211108-integrate-with-blender.html#context-and-problem-statement",
+    "title": "Proposed: Integrate with blender",
     "section": "",
-    "text": "Supersedes 20211031-use-bpr-to-rank-skeleton-bone-names"
+    "text": "Blend files are too difficult to write an importer for in Godot Engine."
   },
   {
-    "objectID": "decisions/20230908-bendable-screen-generative-assistant-ggml.html",
-    "href": "decisions/20230908-bendable-screen-generative-assistant-ggml.html",
-    "title": "Draft: Translation/Transcription Badge with GGML’s Whisper",
+    "objectID": "decisions/20211108-integrate-with-blender.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20211108-integrate-with-blender.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: Integrate with blender",
     "section": "",
-    "text": "The project aims to develop a translation/transcription badge using GGML’s Whisper, a part of the GGML library that provides access to large language models (LLMs). The primary focus is on voice interactions.\n\n\n\n\nVoice Interactions: The system will prioritize voice interactions, leveraging GGML’s Whisper capabilities to create a responsive AI. Python will not be used in this context.\nSpeech-to-Text Interface: A speech-to-text interface will be incorporated to process voice inputs effectively.\nDirect Connection to Compute Module: The display, set in portrait mode, will connect directly to the compute module, a standard Linux amd64 computer, eliminating the need for embedded software development.\nFlexible OLED Display: The system will utilize a 6-inch flexible OLED display from Wisecoco with a resolution of 2880*1440 at 60Hz refresh rate.\nNo Holograph Displays: The design will be streamlined and efficient, excluding holograph displays.\n\n\n\n\nThe project’s complexity and the expertise required in areas such as GGML, the Godot engine, and AI development pose significant challenges.\n\n\n\nWe have decided against integrating Python with GGML and using a pre-existing AI framework instead of developing one from scratch.\n\n\n\nThe project may not be suitable for individuals without familiarity with GGML or a background in AI development.\n\n\n\nThe project will be developed in-house, utilizing our expertise in AI and game development.\n\n\n\nFor more information, please refer to these resources:\n\nV-Sekai\nGGML on GitHub\nWhisper JAX on GitHub\nTwitter inspiration\nwisecoco 6 inch 2K Flexible OLED Display IPS 2880 * 1440 Flexible Screen Curved Bendable Screen\n\n\n\n\ngraph TD\nA[Edge Device: Compute Unit] --&gt;|Hosts| B[VRM1 Character Layer]\nC[Whisper for Speech-to-Text running on GGML] -- Audio Processing --&gt; B\nB --&gt; D[Wisecoco 6-inch Flexible OLED Display in Portrait Mode]\nE[Microphone] -- Audio Input --&gt; C\n\n\n\n\n\nThis unit is a standard Linux amd64 computer that hosts the VRM1 Character Layer (B).\n\n\n\nThis module, running on GGML, captures audio input from the Microphone (E) and converts it into text.\n\n\n\nThe processed data from the Whisper module animates a virtual character in this layer. The character can be in speaking or idle mode.\n\n\n\nThe resulting texts are displayed on this screen.\n\nNote: Currently, the system only supports speaking and idle states. Other modes are not available.\n\nThe choice of portrait mode for the display aligns with the specific needs and constraints of the project. As the project heavily relies on text-based interactions, specifically transcriptions, portrait mode allows more lines of text to be visible at once, thereby improving the user experience.\nThe system utilizes a 6-inch flexible OLED display from Wisecoco. Portrait mode is more space-efficient in such scenarios, taking up less horizontal space while still providing ample vertical space for text display.\nGiven that the primary focus of the project is voice interactions, the display mode should ideally support easy reading of transcriptions. Portrait mode, with its vertical orientation, is more suited to this task as it mimics the natural top-to-bottom reading flow.\nAccording to the system diagram, the processed data from the Whisper for Speech-to-Text module running on GGML is used to animate a virtual character and display the resulting texts. These texts are likely to be dialog or conversation-based, and portrait mode would allow for a more coherent and continuous display of these text blocks."
+    "text": "Make an addon that calls Blender directly and tell it to export to the proper place."
   },
   {
-    "objectID": "decisions/20230908-bendable-screen-generative-assistant-ggml.html#overview",
-    "href": "decisions/20230908-bendable-screen-generative-assistant-ggml.html#overview",
-    "title": "Draft: Translation/Transcription Badge with GGML’s Whisper",
+    "objectID": "decisions/20211108-integrate-with-blender.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20211108-integrate-with-blender.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Integrate with blender",
     "section": "",
-    "text": "The project aims to develop a translation/transcription badge using GGML’s Whisper, a part of the GGML library that provides access to large language models (LLMs). The primary focus is on voice interactions."
+    "text": "Enable addon\nOpen blend\nSee the blend as a Godot Engine scene."
   },
   {
-    "objectID": "decisions/20230908-bendable-screen-generative-assistant-ggml.html#key-features",
-    "href": "decisions/20230908-bendable-screen-generative-assistant-ggml.html#key-features",
-    "title": "Draft: Translation/Transcription Badge with GGML’s Whisper",
+    "objectID": "decisions/20211108-integrate-with-blender.html#positive-consequences",
+    "href": "decisions/20211108-integrate-with-blender.html#positive-consequences",
+    "title": "Proposed: Integrate with blender",
     "section": "",
-    "text": "Voice Interactions: The system will prioritize voice interactions, leveraging GGML’s Whisper capabilities to create a responsive AI. Python will not be used in this context.\nSpeech-to-Text Interface: A speech-to-text interface will be incorporated to process voice inputs effectively.\nDirect Connection to Compute Module: The display, set in portrait mode, will connect directly to the compute module, a standard Linux amd64 computer, eliminating the need for embedded software development.\nFlexible OLED Display: The system will utilize a 6-inch flexible OLED display from Wisecoco with a resolution of 2880*1440 at 60Hz refresh rate.\nNo Holograph Displays: The design will be streamlined and efficient, excluding holograph displays."
+    "text": "Integrates Blender into Godot Engine workflows.\nDownside of Blender version updates can be fixed by the use of the V-Sekai exporter tool."
   },
   {
-    "objectID": "decisions/20230908-bendable-screen-generative-assistant-ggml.html#potential-challenges",
-    "href": "decisions/20230908-bendable-screen-generative-assistant-ggml.html#potential-challenges",
-    "title": "Draft: Translation/Transcription Badge with GGML’s Whisper",
+    "objectID": "decisions/20211108-integrate-with-blender.html#negative-consequences",
+    "href": "decisions/20211108-integrate-with-blender.html#negative-consequences",
+    "title": "Proposed: Integrate with blender",
     "section": "",
-    "text": "The project’s complexity and the expertise required in areas such as GGML, the Godot engine, and AI development pose significant challenges."
+    "text": "Requires blender to export cicd.\nChanges to the Blender version causes the project to desync."
   },
   {
-    "objectID": "decisions/20230908-bendable-screen-generative-assistant-ggml.html#alternatives-not-considered",
-    "href": "decisions/20230908-bendable-screen-generative-assistant-ggml.html#alternatives-not-considered",
-    "title": "Draft: Translation/Transcription Badge with GGML’s Whisper",
+    "objectID": "decisions/20211108-integrate-with-blender.html#option-graveyard",
+    "href": "decisions/20211108-integrate-with-blender.html#option-graveyard",
+    "title": "Proposed: Integrate with blender",
     "section": "",
-    "text": "We have decided against integrating Python with GGML and using a pre-existing AI framework instead of developing one from scratch."
+    "text": "Option: \nRejection Reason:"
   },
   {
-    "objectID": "decisions/20230908-bendable-screen-generative-assistant-ggml.html#target-audience",
-    "href": "decisions/20230908-bendable-screen-generative-assistant-ggml.html#target-audience",
-    "title": "Draft: Translation/Transcription Badge with GGML’s Whisper",
+    "objectID": "decisions/20211108-integrate-with-blender.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20211108-integrate-with-blender.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Integrate with blender",
     "section": "",
-    "text": "The project may not be suitable for individuals without familiarity with GGML or a background in AI development."
+    "text": "This is a script but not a few lines."
   },
   {
-    "objectID": "decisions/20230908-bendable-screen-generative-assistant-ggml.html#development-strategy",
-    "href": "decisions/20230908-bendable-screen-generative-assistant-ggml.html#development-strategy",
-    "title": "Draft: Translation/Transcription Badge with GGML’s Whisper",
+    "objectID": "decisions/20211108-integrate-with-blender.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20211108-integrate-with-blender.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Integrate with blender",
     "section": "",
-    "text": "The project will be developed in-house, utilizing our expertise in AI and game development."
+    "text": "I know how to do this and others don’t."
   },
   {
-    "objectID": "decisions/20230908-bendable-screen-generative-assistant-ggml.html#further-reading",
-    "href": "decisions/20230908-bendable-screen-generative-assistant-ggml.html#further-reading",
-    "title": "Draft: Translation/Transcription Badge with GGML’s Whisper",
+    "objectID": "decisions/20211108-integrate-with-blender.html#references",
+    "href": "decisions/20211108-integrate-with-blender.html#references",
+    "title": "Proposed: Integrate with blender",
     "section": "",
-    "text": "For more information, please refer to these resources:\n\nV-Sekai\nGGML on GitHub\nWhisper JAX on GitHub\nTwitter inspiration\nwisecoco 6 inch 2K Flexible OLED Display IPS 2880 * 1440 Flexible Screen Curved Bendable Screen"
+    "text": "https://www.blender.org/\nhttps://github.com/V-Sekai/godot-blender"
   },
   {
-    "objectID": "decisions/20230908-bendable-screen-generative-assistant-ggml.html#system-diagram",
-    "href": "decisions/20230908-bendable-screen-generative-assistant-ggml.html#system-diagram",
-    "title": "Draft: Translation/Transcription Badge with GGML’s Whisper",
+    "objectID": "decisions/20211108-integrate-with-blender.html#derivative-license",
+    "href": "decisions/20211108-integrate-with-blender.html#derivative-license",
+    "title": "Proposed: Integrate with blender",
     "section": "",
-    "text": "graph TD\nA[Edge Device: Compute Unit] --&gt;|Hosts| B[VRM1 Character Layer]\nC[Whisper for Speech-to-Text running on GGML] -- Audio Processing --&gt; B\nB --&gt; D[Wisecoco 6-inch Flexible OLED Display in Portrait Mode]\nE[Microphone] -- Audio Input --&gt; C"
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230908-bendable-screen-generative-assistant-ggml.html#system-diagram-explanation",
-    "href": "decisions/20230908-bendable-screen-generative-assistant-ggml.html#system-diagram-explanation",
-    "title": "Draft: Translation/Transcription Badge with GGML’s Whisper",
+    "objectID": "decisions/20230108-wmf-video-playback.html",
+    "href": "decisions/20230108-wmf-video-playback.html",
+    "title": "Proposed: Add WMF for windows media playback",
     "section": "",
-    "text": "This unit is a standard Linux amd64 computer that hosts the VRM1 Character Layer (B).\n\n\n\nThis module, running on GGML, captures audio input from the Microphone (E) and converts it into text.\n\n\n\nThe processed data from the Whisper module animates a virtual character in this layer. The character can be in speaking or idle mode.\n\n\n\nThe resulting texts are displayed on this screen.\n\nNote: Currently, the system only supports speaking and idle states. Other modes are not available.\n\nThe choice of portrait mode for the display aligns with the specific needs and constraints of the project. As the project heavily relies on text-based interactions, specifically transcriptions, portrait mode allows more lines of text to be visible at once, thereby improving the user experience.\nThe system utilizes a 6-inch flexible OLED display from Wisecoco. Portrait mode is more space-efficient in such scenarios, taking up less horizontal space while still providing ample vertical space for text display.\nGiven that the primary focus of the project is voice interactions, the display mode should ideally support easy reading of transcriptions. Portrait mode, with its vertical orientation, is more suited to this task as it mimics the natural top-to-bottom reading flow.\nAccording to the system diagram, the processed data from the Whisper for Speech-to-Text module running on GGML is used to animate a virtual character and display the resulting texts. These texts are likely to be dialog or conversation-based, and portrait mode would allow for a more coherent and continuous display of these text blocks."
+    "text": "Proposed: Add WMF for windows media playback\n\nContext and Problem Statement\nWe don’t have any good ways of playing video and also large 4k videos.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nAdd WMF support to godot for the windows platform.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nSee https://github.com/V-Sekai/godot/tree/wmf\n\n\nPositive Consequences\nCan play videos.\nOS platform supported playback will be hardware accelerated.\n\n\nNegative Consequences\nNo response\n\n\nOption graveyard\nNo response\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nIt’s not a few lines.\n\n\nIs there a reason why this should be core and done by us?\nI found this!\n\n\nReferences\n\nV-Sekai\n\n\n\nLicense of the contribution\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20211031-vmd-on-vrm-animationtree-node.html",
-    "href": "decisions/20211031-vmd-on-vrm-animationtree-node.html",
-    "title": "Draft: VMD on VRM AnimationTree Node",
+    "objectID": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html",
+    "href": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html",
+    "title": "Rejected: Iterate faster on WasGo prototype by using Godot 3.4",
     "section": "",
-    "text": "Draft: VMD on VRM AnimationTree Node\n\nContext and Problem Statement\nEirexe made a VMD player based on Lox’s work.\nThis new ability means we now have a viable way to load VMD motions and use them as a VRM motion player.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nWe want to make an AnimationTree node to drive Miku Miku VMD motion and add other procedural animation features to blend motion on the VRM Avatar.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nHowever, we need to make some changes to the AnimationTree UI editor to make the changes possible. We want an expanded AnimationTree to customize nodes, mainly when Godot Engine adds procedural animation features.\nSaracen wants to make sure that the AnimationTree gets the features needed so any custom nodes can be quickly prototyped via scripted extensions if needed. Doing it in purely c++ can limit scripting.\niFire’s “hard coding” definition tests if the node is different from writing the node from a composition of existing nodes. A VMD animation tree node would be “hard coding.”\nThere are currently some limitations with the AnimationTree, which makes the animation tree somewhat challenging to extend with custom nodes via scripting. However, the good news is, we do not think it would take much to make a VMD AnimationTree node work. The AnimationTree work is primarily a UI limitation and a small one at that.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNOT A FEW LINES OF CODE!\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nWe currently know how to do this, if we don’t who else will?\n\n\nReferences\n\nhttps://github.com/EIRTeam/VMDMotionGD\nhttps://github.com/V-Sekai/godot-vrm\nhttps://en.wikipedia.org/wiki/MikuMikuDance\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Status: rejected \nDeciders: V-Sekai,fire,\nTags: V-Sekai,\n\n\n\nIterating on WasGo is too slow.\n\n\n\nPropose iterating on WasGo on Godot 3.4.\n\n\n\n\nBranch off Godot 3.4\nUse our version of wasgo\nRestore wasgo demos.\nImplement templated C++ code via mustashe for Wasgo\nPort to master\n\n\n\n\n\nSeparate the two axis of development. The first axis is Godot Engine master and the second axis is Wasgo development.\n\n\n\n\n\nMay or may not be more expensive.\nTook too much effort to verify.\n\n\n\n\n\nOption: \nRejection Reason: \n\n\n\n\nCoding strategy is not coding.\n\n\n\nThis is a V-Sekai strategy plan.\n\n\n\n\nhttps://github.com/V-Sekai/WasGo\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230829-omifest-2023.html",
-    "href": "decisions/20230829-omifest-2023.html",
-    "title": "Proposed: OMIFest 2023 - The Call",
+    "objectID": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html#context-and-problem-statement",
+    "href": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html#context-and-problem-statement",
+    "title": "Rejected: Iterate faster on WasGo prototype by using Godot 3.4",
     "section": "",
-    "text": "Status: Proposed\nDeciders: OMIGroup, Fire, Indiebio\nTags: OMIGroup, V-Sekai\n\n\n\n\n\n\nOMIFest 2023 is an online event set against the backdrop of a rapidly evolving digital landscape. As virtual reality and augmented reality technologies become more accessible, there’s an increasing need for platforms that allow artists, tinkerers, hackers, players, and professionals to showcase their talents and collaborate in a digital environment.\n\n\n\nThe challenge is to create an event that not only celebrates these individuals but also encourages conversation and collaboration within our community. We aim to build a webpage on the OMI website for more information and updates about this online event.\n\n\n\n\n\n\nOur strategy is to host a series of monthly events leading up to the main event in October 2024. Each month we will focus on different aspects of the event, such as building the vehicle, avatars, textures, scenery, and workshops on content creation.\n\n\n\nResearch: Held in conjunction with an academically minded in-person conference.\nAssets, protocols, and specification testing: Build assets and test protocols to ensure interoperability.\nCommunity Celebration: Celebrate with the global community in a digital setting.\n\n\n\n\nThis online event is open to everyone. Individuals, teams, corporate members, community groups, anyone and everyone can submit an entry. Registration will be required for our information, and some moderation may be required, but everyone is welcome.\n\n\n\n\nNotice boards for help needed, job board, find a team etc\nLimited poster advertising\nMusic\nBooths for nonprofit, education, community organizations\nMetaverse library/blockbuster to find how-to guides, videos, etc\nThrift shop for free stuff\nMarket for assets\nJunk yard for abandoned assets\nPortals to other worlds\nAssets that are created remain in the world\nScenery around the parade\nParade with floats\n\n\n\n\nIt is free to register and submit assets. The event will be free to attend. Some aspects and mini events may require payment.\n\n\n\nWe are open to sponsorships for this online event. More details will be provided soon.\n\n\n\nHere is a rough schedule of our monthly events:\n\n\n\nDate\nTopic\n\n\n\n\nAugust 2023\nContent sharing workshop\n\n\nSeptember 2023\nMaking a basic vehicle\n\n\nOctober 2023\nMaking an avatar\n\n\nNovember 2023\nMaking textures\n\n\nDecember 2023\nMaking scenery\n\n\nJanuary 2024\nMusic in the metaverse\n\n\nFebruary 2024\nAI\n\n\nMarch 2024\nCommunity, public spheres\n\n\nApril 2024\nPortals\n\n\nMay 2024\n(repeat the above?)\n\n\nJune 2024\nUse art to explore data\n\n\nJuly 2024\nReal world challenge\n\n\n\n\n\n\n\nThe upside of this online event is that it provides a platform for individuals from various backgrounds to showcase their talents, learn from each other, and collaborate on projects. It also helps in promoting the use of VR/AR technologies and encourages innovation in this field.\n\n\n\nThe downside could be the potential logistical challenges involved in organizing such a large-scale online event. There might also be issues related to ensuring fair participation and dealing with intellectual property rights.\n\n\n\nAn alternative approach could have been to organize smaller, more frequent online events throughout the year. However, we decided to go with a larger annual event to create more impact and allow participants enough time to prepare.\n\n\n\nWhile the event is designed to cater to a wide range of participants, there might be some who might not be able to participate due to lack of access to necessary technology or skills. We plan to address this by providing resources and learning materials to help them get started.\n\n\n\nYes, the event is being organized by us, OMIGroup, in collaboration with V-Sekai. We are responsible for planning, coordinating, and executing aspects of the event. The success of such a large-scale online event relies on the collective efforts of many individuals and organizations.\n\n\n\n\n\nOMIGroup\nV-Sekai\nMetaverse Float Parade\nThis article is assisted by AI."
+    "text": "Iterating on WasGo is too slow."
   },
   {
-    "objectID": "decisions/20230829-omifest-2023.html#metadata",
-    "href": "decisions/20230829-omifest-2023.html#metadata",
-    "title": "Proposed: OMIFest 2023 - The Call",
+    "objectID": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Rejected: Iterate faster on WasGo prototype by using Godot 3.4",
     "section": "",
-    "text": "Status: Proposed\nDeciders: OMIGroup, Fire, Indiebio\nTags: OMIGroup, V-Sekai"
+    "text": "Propose iterating on WasGo on Godot 3.4."
   },
   {
-    "objectID": "decisions/20230829-omifest-2023.html#context",
-    "href": "decisions/20230829-omifest-2023.html#context",
-    "title": "Proposed: OMIFest 2023 - The Call",
+    "objectID": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Rejected: Iterate faster on WasGo prototype by using Godot 3.4",
     "section": "",
-    "text": "OMIFest 2023 is an online event set against the backdrop of a rapidly evolving digital landscape. As virtual reality and augmented reality technologies become more accessible, there’s an increasing need for platforms that allow artists, tinkerers, hackers, players, and professionals to showcase their talents and collaborate in a digital environment.\n\n\n\nThe challenge is to create an event that not only celebrates these individuals but also encourages conversation and collaboration within our community. We aim to build a webpage on the OMI website for more information and updates about this online event."
+    "text": "Branch off Godot 3.4\nUse our version of wasgo\nRestore wasgo demos.\nImplement templated C++ code via mustashe for Wasgo\nPort to master"
   },
   {
-    "objectID": "decisions/20230829-omifest-2023.html#decision",
-    "href": "decisions/20230829-omifest-2023.html#decision",
-    "title": "Proposed: OMIFest 2023 - The Call",
+    "objectID": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html#positive-consequences",
+    "href": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html#positive-consequences",
+    "title": "Rejected: Iterate faster on WasGo prototype by using Godot 3.4",
     "section": "",
-    "text": "Our strategy is to host a series of monthly events leading up to the main event in October 2024. Each month we will focus on different aspects of the event, such as building the vehicle, avatars, textures, scenery, and workshops on content creation.\n\n\n\nResearch: Held in conjunction with an academically minded in-person conference.\nAssets, protocols, and specification testing: Build assets and test protocols to ensure interoperability.\nCommunity Celebration: Celebrate with the global community in a digital setting.\n\n\n\n\nThis online event is open to everyone. Individuals, teams, corporate members, community groups, anyone and everyone can submit an entry. Registration will be required for our information, and some moderation may be required, but everyone is welcome.\n\n\n\n\nNotice boards for help needed, job board, find a team etc\nLimited poster advertising\nMusic\nBooths for nonprofit, education, community organizations\nMetaverse library/blockbuster to find how-to guides, videos, etc\nThrift shop for free stuff\nMarket for assets\nJunk yard for abandoned assets\nPortals to other worlds\nAssets that are created remain in the world\nScenery around the parade\nParade with floats\n\n\n\n\nIt is free to register and submit assets. The event will be free to attend. Some aspects and mini events may require payment.\n\n\n\nWe are open to sponsorships for this online event. More details will be provided soon.\n\n\n\nHere is a rough schedule of our monthly events:\n\n\n\nDate\nTopic\n\n\n\n\nAugust 2023\nContent sharing workshop\n\n\nSeptember 2023\nMaking a basic vehicle\n\n\nOctober 2023\nMaking an avatar\n\n\nNovember 2023\nMaking textures\n\n\nDecember 2023\nMaking scenery\n\n\nJanuary 2024\nMusic in the metaverse\n\n\nFebruary 2024\nAI\n\n\nMarch 2024\nCommunity, public spheres\n\n\nApril 2024\nPortals\n\n\nMay 2024\n(repeat the above?)\n\n\nJune 2024\nUse art to explore data\n\n\nJuly 2024\nReal world challenge\n\n\n\n\n\n\n\nThe upside of this online event is that it provides a platform for individuals from various backgrounds to showcase their talents, learn from each other, and collaborate on projects. It also helps in promoting the use of VR/AR technologies and encourages innovation in this field.\n\n\n\nThe downside could be the potential logistical challenges involved in organizing such a large-scale online event. There might also be issues related to ensuring fair participation and dealing with intellectual property rights.\n\n\n\nAn alternative approach could have been to organize smaller, more frequent online events throughout the year. However, we decided to go with a larger annual event to create more impact and allow participants enough time to prepare.\n\n\n\nWhile the event is designed to cater to a wide range of participants, there might be some who might not be able to participate due to lack of access to necessary technology or skills. We plan to address this by providing resources and learning materials to help them get started.\n\n\n\nYes, the event is being organized by us, OMIGroup, in collaboration with V-Sekai. We are responsible for planning, coordinating, and executing aspects of the event. The success of such a large-scale online event relies on the collective efforts of many individuals and organizations."
+    "text": "Separate the two axis of development. The first axis is Godot Engine master and the second axis is Wasgo development."
   },
   {
-    "objectID": "decisions/20230829-omifest-2023.html#references",
-    "href": "decisions/20230829-omifest-2023.html#references",
-    "title": "Proposed: OMIFest 2023 - The Call",
+    "objectID": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html#negative-consequences",
+    "href": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html#negative-consequences",
+    "title": "Rejected: Iterate faster on WasGo prototype by using Godot 3.4",
     "section": "",
-    "text": "OMIGroup\nV-Sekai\nMetaverse Float Parade\nThis article is assisted by AI."
+    "text": "May or may not be more expensive.\nTook too much effort to verify."
   },
   {
-    "objectID": "decisions/20211031-bake-a-materialx-into-a-custom-godot-standardmaterial3d.html",
-    "href": "decisions/20211031-bake-a-materialx-into-a-custom-godot-standardmaterial3d.html",
-    "title": "Proposed: Bake a #materialx into a custom Godot StandardMaterial3D",
+    "objectID": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html#option-graveyard",
+    "href": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html#option-graveyard",
+    "title": "Rejected: Iterate faster on WasGo prototype by using Godot 3.4",
     "section": "",
-    "text": "Proposed: Bake a #materialx into a custom Godot StandardMaterial3D\n\nContext and Problem Statement\nThere is not many procedural material Makers.\nThe two the come to mind is Godot’s Material Maker and Adobe’s Substance Designer.\nMore options would be helpful.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nCreate a #materialx to Godot Standard Material tool.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nMake a GDscript tool that takes the #materialx bake tool I already made and bake it to a standard material 3D in Godot Engine.\nCraft a GDScript that uses the command line tool and converts mtlx to a standard material 3d.\n\napt install -y libglew-dev\n\n\ncmake -GNinja .. -DMATERIALX_BUILD_BAKER=ON\n\n\n.\\bin\\MaterialXBake.exe --material .\\resources\\Materials\\Examples\\glTFPBR\\gltf_pbr_boombox.mtlx --bakeFilename ../demo.mtlx --bakeWidth 8192 --bakeHeight 8192\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nEh. Not simple.\n\n\nPositive Consequences\nExpansion into a web tool.\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nI found an approach and it can be done.\n\n\nReferences\n\nhttps://github.com/fire/MaterialX/tree/gltf\nhttps://godotengine.org/showcase/material-maker\nhttps://en.wikipedia.org/wiki/Procedural_texture\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Option: \nRejection Reason:"
   },
   {
-    "objectID": "decisions/20220317-use-spec-rough-metal.html",
-    "href": "decisions/20220317-use-spec-rough-metal.html",
-    "title": "Proposed: Use specular vec3 from gltf to show multicoloured metals",
+    "objectID": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Rejected: Iterate faster on WasGo prototype by using Godot 3.4",
     "section": "",
-    "text": "Proposed: Use specular vec3 from gltf to show multicoloured metals\n\nDesc\nribe the status of the issue.\nrejected\n\n\nList the deciders of the issue.\nV-Sekai,fire,\n\n\nDescribe the tags of the issue.\nV-Sekai,\n\n\nContext and Problem Statement\nWe want to be able to use Specular from gltf and Specular from spec gloss, but previous solutions did not compose with the principled pbr roughness metallness model.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nImplement specular from gltf.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\n???\n\n\nPositive Consequences\nWe can import spec gloss for compatibility.\nDemos show multicolored transparency.\n\n\nNegative Consequences\n\nMore complexity\n\n\n\nOption graveyard\n\nOption: Add spec gloss extension\nDoes not compose with roughness metalness.\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot a few lines of code.\n\n\nIs there a reason why this should be core and done by us?\nChanging the standard material 3d is a core decision.\n\n\nReferences\n\nV-Sekai\n\n\n\nLicense of the contribution\nCopyright (c) 2022 V-Sekai contributors. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Coding strategy is not coding."
   },
   {
-    "objectID": "decisions/20200608-vsekai-charter.html",
-    "href": "decisions/20200608-vsekai-charter.html",
-    "title": "Mozilla Builders Summer MVP Lab (SUBMITTED ON JUNE 8 2020)",
+    "objectID": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Rejected: Iterate faster on WasGo prototype by using Godot 3.4",
     "section": "",
-    "text": "Mozilla Builders Summer MVP Lab (SUBMITTED ON JUNE 8 2020)\nDid you apply for our Spring MVP Lab program?\nCheck this if at least one team member applied.\nOne line summary of the MVP:\nA fully remixable and self-hosted collaborative VR environment based on Godot Engine.\nDescription of the product: What will the MVP be in 8 weeks?\nOur standalone Virtual Reality (VR) application will be usable from all SteamVR compatible PC headsets, as well as the mobile Oculus Quest VR platform. The MVP features a social hub with both 3D spatialized voice and realtime upper body tracking, with simple games, physics and social video viewing.\nCategory Category\n\nCollaboration & Society\nDecentralized Web : YES\nMessaging & Social Networking : YES\nSurveillance Capitalism\nMisinformation & Content\nArtificial Intelligence\nWeb Assembly\n\nCheck all that apply.\nOptional Video\nhttps://www.youtube.com/watch?v=j2PTDXG1Hc4\nWhy does your idea matter: How will it help deliver on the full promise of the internet, or make the internet more awesome? * The core principles of the Internet are openness and communication. We see VR as the basis for a new frontier of communication products, Social VR platforms. Hastened by the closure and general failings of the once-open source High Fidelity platform, we are now in desperate need of open source alternatives to the growing number of closed source VR-compatible walled gardens in development.\nWe are at the pinnacle of a new wave of VR and related tech, and with the impending maturity of open game engines, audio and video codecs, combined with faster internet connectivity capable of hosting services, and increasingly available VR hardware, the time is right to lead the development of an open platform.\nWe believe in putting power back in the hands of individuals, and thus we are strong believers in decentralized technology. Our initial goal will be to produce a polished, well-functioning service, but we also have plans to integrate decentralized authentication and encryption schemes, including GPG and web of trust based E2EE, as well as decentralized content distribution tech such as Bittorrent and IPFS.\nWho are your users or potential users?\nWe are building a product for all users of social VR, online collaboration or communication products. Social VR is a growing space, and its potential is only beginning to be realized, with a mass movement towards virtual collaboration.\nEven VR as a whole is still in very early stages, but it represents a large potential market, especially with the recent availability of affordable and easy to install headsets such as the Oculus Quest, which has seen rapid growth after its release one year ago.\nAn example of a leading VR platform with public numbers, VRChat has recently between 12000 and 15000 concurrent online users across VR and Desktop platforms, with roughly 4000 concurrent VR users using this platform (out of a reported 4 million registered users as of 2019).\nWhat is your personal connection to the service & the user group you are planning to reach with your product? *\nWe’re a passionate team of VR enthusiasts, some of us tinkering in our spare time with visual effects, level design, or graphics concepts still in research.\nIn an age where collaborating and connecting at distance is increasingly important, meeting in real life can often be a barrier to people. VR has the potential to bring people together and immerse them in a shared space, in a way that not even the best video collaboration can. I and another member of our group have participated in Virtual Market 4, the most recent iteration of a Japanese-run exponentially-growing marketplace of virtual content spanning multiple platforms.\nOther Social VR platforms have found ways to immerse me in a multitude of realities: for example, engaging in real time with people around the world at all times of day and night: attending live dance and music events, seeing performers breakdance and do pole acrobatics using VIVE full body trackers, forming friendships through exchanging personal stories around a campfire, programming environments defined by a math function and then experiencing them in VR, even solving a 1000 piece jigsaw puzzle with friends. It is my dream to enable these experiences and more in a setting that is sustainable, open and accessible.\nIf we do not fund this project, will your team still work on it? To what extent? *\nAn Injection of capital by Mozilla will speed up our development and let me take leave of my company to focus full time on the MVP. This could give us the opportunity to outrun these walled gardens in a very short time.\nIf not funded, we will be able to continue to advance it more slowly in our spare time, but other closed platforms are catching up, and time is of the essence. Our project will additionally drive development around open source VR support and 3D tools, and we can see lasting effects from our contributions in those areas.\nWhy did you pick this idea? Do you have domain expertise? How do you know people need what you’re building? *\nWe’re seeding the beginning of the VR frontier, and we already see a sizable fraction of the current VR population spending a substantial amount of time in Social VR walled gardens, such as VRChat.\nIt can be difficult or impossible to build atop walled garden platforms outside of their respective visions: we’ve run into such roadblocks in past projects. For example a combination of lack of the persistence, access to media/web requests, and general customizability has made other platforms unsuitable for building long games, and unsuitable for building complex collaboration tools. Meanwhile, our platform can be self hosted, allows private usage and can be modified.\nOur team includes significant backend and operations experience and several years of work on Godot Engine, all of which will be relevant to building this platform.\nWe suspect the need exists for an open alternative to other competing walled gardens. While many VR platforms are currently free-to-use and advertise a minimal set of privacy features, there is no guarantee that popular platforms will remain free or private forever: for example, a widely used product could be acquired by a corporation with different goals.\nAdditionally, we see potential for a customizable, open platform to be used within enterprises, as well as to build the foundation for games or other content which share needs with our platform, such as its VOIP or VR interaction features.\nAre you looking for any teammates? If so, please indicate what skills or roles you seek.\nNot at this time\nWe have created a Slack Channel and GitHub repository and issues list where you can post your project and look for teammates. You can also pivot or abandon your project as you connect with teammates:\nGitHub: https://github.com/fix-the-internet/spring-mvp-lab/issues\nSlack: https://join.slack.com/t/mozillabuilders/shared_invite/zt-czo6bp37-R9I5mKJVYPtCkTQFu1NLWw\nDescribe your work plan.\nTHIS IS A COPY OF OUR GANTT CHART. THIS WAS NOT SUBMITTED ~Lyuma\nWeek 1: Maintain continuous integration of Windows SteamVR and Oculus Quest, and Linux server builds running on a public server against which to test and dogfood the product. VOIP implementation: basic lipsync based on volume, integrate spatialization library. Improve Inverse Kinematics implementation and add non-VR support.\nWeek 2: Headless clients to extensively stress test the system. Implement crash reporting system, and reporting metrics including performance. Content: Use a basic scripting API to implement physics based games. Begin work on engine changes necessary to give smooth framerates even when during content loading.\nWeek 3: Networking interpolation: eliminate stuttering caused by networking. Godot OpenVR Plugin: fix bugs causing inconsistent framerate in VR. Pre-load content where needed to avoid stutters in the 3d environment.\nWeek 4: Content: Begin work on specific set of hardcoded avatars. Content: Recruit artist to begin work on create default home map. Physics: fix physics errors such as sliding down ramps. Test performance on regular vr hardware and optimization.\nWeek 5-6: Account system, TOS, Privacy Policy. Allow closed registration of users, starting with people who have already shown interest. Continue working on content. Fix bugs and issues as needed. Integration of video playback. Focus on stress testing.\nWeek 7-8 Fix bugs discovered during testing. Monitor performance metrics captured by users, keep fixing performance\nDescribe the approach the team will take to develop the Minimum Viable Product throughout the summer. This includes, but not limited to:\n\nWho are your competitors?\n\nVRChat, Facebook Horizon, RecRoom, AltSpace, EngageVR, Spatial (quest), Mozilla Hubs, VirtualCast, cluster, Sansar, HTC Vive Sync, OasisVR, ChilloutVR, Lavender, Roblox VR (We are not considering non-VR capable platforms or MMORPGs as competition)\n\nHow will you attract your first 1000 users? Your first 1,000,000?\n\nWe anticipate contacts from our immediate VR communities who have already shown interest in our project will seed the first 50 users.\nAt a minimum, we will provide the real time presence features available in other VR platforms: appearing in a room of people who you can hear and to break past 100 users, we will need to provide experiences which are not easily accessible on other platforms such as VRChat.\nTo move beyond thousands of users: being a neutral, open platform to host events: for example, Virtual Market had on the order of a million visitors ( https://www.youtube.com/watch?v=lLX7UNKV1fk ; https://v-market.work/ ), was hosted just as a collection of VRChat world instances, and still had to deal with several glitches as a result of instabilities of the underlying platform.\nAnother source of usage will be business meetings, and anything where privacy and self-hosting is a concern. Making sure that it is lightweight and remains very easy to compile will allow novel usages and customizations of the platform.\n\nFirst 2 week development milestone\n\nFirst two weeks:\n\nMaintain continuous integration of Windows SteamVR and Oculus Quest, and Linux server builds running on a public server against which to test and dogfood the product.\nVOIP implementation: basic lipsync based on volume, integrate spatialization library.\nImprove Inverse Kinematics implementation and add non-VR support.\nHeadless clients to extensively stress test the system.\nImplement crash reporting system, and reporting metrics including performance.\nContent: Use a basic scripting API to implement physics based games.\nBegin work on engine changes necessary to give smooth framerates even when during content loading.\nTech stack you plan to use (Cloud services, APIs, mobile platforms, languages, etc)\n\nGodot Engine, k3s, Elixir, OAuth, CockroachDB, nginx, Fedora, CentOS 8, Digital Ocean Spaces, Oculus Quest SDK on Android, Valve OpenVR on Windows.\n\nLink to simple sketches (can be as simple as paper and pencil) of your product or idea\n\nhttps://cdn.discordapp.com/attachments/659137056991346708/718332831687901224/vsekai-sketch.png\nLinks to mockups, prototypes, pitches.\nWhat challenges do you anticipate with this idea?\nWith the exception of Hubs, the now-defunct High Fidelity, and a handful of proprietary VR platforms, most Social VR applications are being developed in Unity. This leads to a design challenge in building around infrastructure and content that was created specifically with Unity in mind. For example, one of the leading open model sharing formats VRM only officially supports exporting from Unity.\nSocial platforms are strongly impacted by network effect, which puts a challenge towards acquisition. On top of this, VR applications tend to have extremely low retention compared with conventional applications. One possible reason is the restriction of only running one application at a time.\nWe are likely to encounter several unanticipated engineering challenges: VR platforms combine most of the hardest problems in all aspects of computing, from art, networking, social features to graphics optimization.\nTeam Member Locations by Country\nAdd location of all team members by country. COMMA SEPARATED.\nCanada, United States, United Kingdom\nTeam Details\nDescribe the background of ALL team members including finished projects, design skills, technologies, languages + frameworks you are familiar with or briefly describe any professional experience.\nMMMaellon: C++, Java, and Python. Familiar with the Android and iOS frameworks. Design skills come from working professionally as a motion graphics and VFX artist, and video editor. Used to work for a mobile app developer and in the process of getting a masters in computer science.\nSaracen: C++, C, C#, Java, Python, GDScript, Android. Worked several years professionally on mobile app development, self-taught experience working on game mods and game engine architecture including forks of the Id Software GPL releases, code contributions to the open source Godot Engine and to other VR platforms, tools development including Unity, Godot, and Blender plugins, and work on reimplementing legacy game engines for modern platforms.\nLyuma: C++, Java, Python, Javascript, C#, Android, iOS. Familiar with backend, operations, networking. Spent 9 years working in industry: led a team developing the VOIP and video implementation on an iOS and Android app reaching hundreds of millions of users, including the backend architecture, scaling, operations, and networking, as well as the stats and monitoring needed to optimize the design.\niFire: C++. Familiar with Godot Engine and Unreal Engine. Working professionally in game development. For Godot Engine, created a Blender to glTF2 pipeline and coordinating a FBX pipeline. Shipped Offworld Industries’ Squad (80 player War Simulator) as a programmer, devops, and IT for nearly two years. As a team, I implemented a Unreal Engine touch screen product demo for an aerospace company that was exhibited at the Las Vegas NBAA convention using HTML5 and Blueprints.\nWill all team members be committing their full-time energy to this project during the 8 weeks of the program? Not all successful MVP applicants will, but we do expect a major commitment to the MVP Lab. Please explain if you’re not able to commit fulltime to this & how we can be sure this will be a very serious commitment by you and your team\nMMMaellon is making individual contributions, including a VR character movement system, that have proved extremely valuable, as needed.\nSaracen will be working full time on the core client written for Godot.\nLyuma will be working full time on this project starting with the MVP Lab, focusing on dev ops, operations, backend and testing.\niFire is heavily engaged with the wider open source community surrounding Godot Engine, and takes on projects which help further Godot as an ecosystem, on top of spending part time dedicated to this MVP project.\nHow did you hear about the MVP Lab?\nWe heard about it from Hacker News: https://news.ycombinator.com/item?id=23194178\nAnything else we should know?\nAside from being passionate in the VR space, we are all committed to open source/decentralization, and we strive to bring value to the internet community as a whole."
+    "text": "This is a V-Sekai strategy plan."
   },
   {
-    "objectID": "decisions/20220108-bake-blend-shapes-to-skeletons-for-performance.html",
-    "href": "decisions/20220108-bake-blend-shapes-to-skeletons-for-performance.html",
-    "title": "Proposal: Bake blend shapes to skeletons for performance",
+    "objectID": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html#references",
+    "href": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html#references",
+    "title": "Rejected: Iterate faster on WasGo prototype by using Godot 3.4",
     "section": "",
-    "text": "Status: proposed \nDeciders: V-Sekai,fire,\nTags: V-Sekai,\n\n\n\nBlend shapes are slow to render.\n\n\n\nBake blend shapes to skeletal animation.\n\n\n\n\nI want to bake blendshapes\n\n52 face blendshape face movements\nVRM blend shapes\nThe blend shapes are interpolated between 0s and 1s.\nsingle animation track.\n\nI can send it to dem #bone and bake the blend shapes.\n\n\n\n\nRemove empties that are unused.\nExtract the blend shape from the mesh\nExport as alembic 1 meter is 1 unit. Flatten hierarchy.\nNote that all transforms on un-rigged meshes should be applied.\nRemove the skeleton and fbx export as 1 meter is 0.01 units.\nRun dem #bone (parameters to be determined)\n\n./dembones -i=\"a.fbx\" -a=\"a.abc\" -z=4 --bindUpdate=2 -b=200 -o=\"a_res.fbx\"\n# Note that RMSE should be in the same range as 0.01\nComputing Skinning Decomposition:\n    Iter #0: Updating trans..... Done! Updating weights... Done! RMSE = 0.0917716\n`\n\n11. Check the RMSE is less than 0.001.\n\n#### Options\n\nSkinning decomposition to generate bone transformations and skinning weights from input meshes sequence\n\n`call #dembones -i=\"Bone_Geom.fbx\" -a=\"Bone_Anim.abc\" -b=20 -o=\"Decomposition_20.fbx\"`\n\nJoint grouping\n\n`call #dembones -i=\"Bone_Geom.fbx\" -a=\"Bone_Anim.abc\" -b=20 --bindUpdate=2 -o=\"Decomposition_20_grouped.fbx\"`\n\nSolve skinning weights from input meshes sequence and input bone transformations\n\n`call #dembones -i=\"Bone_Trans.fbx\" -a=\"Bone_Anim.abc\" --nTransIters=0 -o=\"SolvedWeights.fbx\"`\n\nSolve bone transformations from input meshes sequence and input skinning weights\n\n`call #dembones -i=\"Bone_Skin.fbx\" -a=\"Bone_Anim.abc\" --nWeightsIters=0 -o=\"SolvedTransformations.fbx\"`\n\nOptimize given bone transformations and skinning weights from input meshes sequence\n\n`call #dembones -i=\"Bone_All.fbx\" -a=\"Bone_Anim.abc\" --bindUpdate=1 -o=\"Optimized.fbx\"`\n\nOnly solve helper #bone using demLock attribute of the joints\n\n`call #dembones -i=\"Bone_Helpers.fbx\" -a=\"Bone_Anim.abc\" --bindUpdate=1 -o=\"SolvedHelpers.fbx\"`\n\nPartially solve skinning weights using per-vertex color attribute of the mesh\n\n`call #dembones -i=\"Bone_PartiallySkinned.fbx\" -a=\"Bone_Anim.abc\" --nTransIters=0 -o=\"SolvedPartialWeights.fbx\"`\n\n### Open questions:\n\nI align each track to a second? one after the others?\n\nHow do I find the tracks again?\n\n## Positive Consequences &lt;!-- optional --&gt;\n\n- Better performance\n- Able to compose animations\n\n## Negative Consequences &lt;!-- optional --&gt;\n\n- More #bone\n\n## Option graveyard: &lt;!-- same as above --&gt;\n\n- Option: Status quo\n- Rejection Reason: Blend shapes are slow and uncomposable.\n\n## If this enhancement will not be used often, can it be worked around with a few lines of script?\n\nNot a few lines of code to do error bound matching and geometry processing.\n\n## Is there a reason why this should be core and done by us?\n\nI know how to do this!\n\n## References &lt;!-- optional and numbers of links can vary --&gt;\n\n- https://github.com/electronicarts/dem-bones\n\n## Derivative License\n\nCopyright (c) 2021 V-Sekai contributors.\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
+    "text": "https://github.com/V-Sekai/WasGo"
   },
   {
-    "objectID": "decisions/20220108-bake-blend-shapes-to-skeletons-for-performance.html#context-and-problem-statement",
-    "href": "decisions/20220108-bake-blend-shapes-to-skeletons-for-performance.html#context-and-problem-statement",
-    "title": "Proposal: Bake blend shapes to skeletons for performance",
+    "objectID": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html#derivative-license",
+    "href": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html#derivative-license",
+    "title": "Rejected: Iterate faster on WasGo prototype by using Godot 3.4",
     "section": "",
-    "text": "Blend shapes are slow to render."
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20220108-bake-blend-shapes-to-skeletons-for-performance.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20220108-bake-blend-shapes-to-skeletons-for-performance.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposal: Bake blend shapes to skeletons for performance",
+    "objectID": "decisions/20221021-make-it-easier-propose-and-post-bugs.html",
+    "href": "decisions/20221021-make-it-easier-propose-and-post-bugs.html",
+    "title": "Proposed: Make it easier to propose and file bugs by simplifying the templates",
     "section": "",
-    "text": "Bake blend shapes to skeletal animation."
+    "text": "Status: proposed \nDeciders: V-Sekai,lyuma\nTags: V-Sekai,\n\n\n\nAbout issue templates, I know Godot doesn’t permit plain feature requests in the main godot issue tracker. To propose something you have to have a fleshed out proposal.\nThat works well for Godot for two reasons: Godot has lots of users so there are already too many feature proposals; and the users of Godot are developers who can be asked to do research and write a whole implementation proposal\nThe users of V-Sekai are not technical in the same way; and furthermore we are not at the scale Godot was in 3.2 when they switched to requiring proposals.\nIf we ever do get big enough that feature requests propose a burden then we can consider making it harder to file them\n\n\n\nModify the V-Sekai-game issue templates to be easier to use.\n\n\n\nRemove required fields. Make them easier to use.\n\n\n\n\nMore bug filing\nMore proposals\n\n\n\n\n\nMore work on the devs to catalog\n\n\n\n\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\n\nNot a script.\n\n\n\nWe own the repos.\n\n\n\n\nV-Sekai\n\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20220108-bake-blend-shapes-to-skeletons-for-performance.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20220108-bake-blend-shapes-to-skeletons-for-performance.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposal: Bake blend shapes to skeletons for performance",
+    "objectID": "decisions/20221021-make-it-easier-propose-and-post-bugs.html#context-and-problem-statement",
+    "href": "decisions/20221021-make-it-easier-propose-and-post-bugs.html#context-and-problem-statement",
+    "title": "Proposed: Make it easier to propose and file bugs by simplifying the templates",
     "section": "",
-    "text": "I want to bake blendshapes\n\n52 face blendshape face movements\nVRM blend shapes\nThe blend shapes are interpolated between 0s and 1s.\nsingle animation track.\n\nI can send it to dem #bone and bake the blend shapes.\n\n\n\n\nRemove empties that are unused.\nExtract the blend shape from the mesh\nExport as alembic 1 meter is 1 unit. Flatten hierarchy.\nNote that all transforms on un-rigged meshes should be applied.\nRemove the skeleton and fbx export as 1 meter is 0.01 units.\nRun dem #bone (parameters to be determined)\n\n./dembones -i=\"a.fbx\" -a=\"a.abc\" -z=4 --bindUpdate=2 -b=200 -o=\"a_res.fbx\"\n# Note that RMSE should be in the same range as 0.01\nComputing Skinning Decomposition:\n    Iter #0: Updating trans..... Done! Updating weights... Done! RMSE = 0.0917716\n`\n\n11. Check the RMSE is less than 0.001.\n\n#### Options\n\nSkinning decomposition to generate bone transformations and skinning weights from input meshes sequence\n\n`call #dembones -i=\"Bone_Geom.fbx\" -a=\"Bone_Anim.abc\" -b=20 -o=\"Decomposition_20.fbx\"`\n\nJoint grouping\n\n`call #dembones -i=\"Bone_Geom.fbx\" -a=\"Bone_Anim.abc\" -b=20 --bindUpdate=2 -o=\"Decomposition_20_grouped.fbx\"`\n\nSolve skinning weights from input meshes sequence and input bone transformations\n\n`call #dembones -i=\"Bone_Trans.fbx\" -a=\"Bone_Anim.abc\" --nTransIters=0 -o=\"SolvedWeights.fbx\"`\n\nSolve bone transformations from input meshes sequence and input skinning weights\n\n`call #dembones -i=\"Bone_Skin.fbx\" -a=\"Bone_Anim.abc\" --nWeightsIters=0 -o=\"SolvedTransformations.fbx\"`\n\nOptimize given bone transformations and skinning weights from input meshes sequence\n\n`call #dembones -i=\"Bone_All.fbx\" -a=\"Bone_Anim.abc\" --bindUpdate=1 -o=\"Optimized.fbx\"`\n\nOnly solve helper #bone using demLock attribute of the joints\n\n`call #dembones -i=\"Bone_Helpers.fbx\" -a=\"Bone_Anim.abc\" --bindUpdate=1 -o=\"SolvedHelpers.fbx\"`\n\nPartially solve skinning weights using per-vertex color attribute of the mesh\n\n`call #dembones -i=\"Bone_PartiallySkinned.fbx\" -a=\"Bone_Anim.abc\" --nTransIters=0 -o=\"SolvedPartialWeights.fbx\"`\n\n### Open questions:\n\nI align each track to a second? one after the others?\n\nHow do I find the tracks again?\n\n## Positive Consequences &lt;!-- optional --&gt;\n\n- Better performance\n- Able to compose animations\n\n## Negative Consequences &lt;!-- optional --&gt;\n\n- More #bone\n\n## Option graveyard: &lt;!-- same as above --&gt;\n\n- Option: Status quo\n- Rejection Reason: Blend shapes are slow and uncomposable.\n\n## If this enhancement will not be used often, can it be worked around with a few lines of script?\n\nNot a few lines of code to do error bound matching and geometry processing.\n\n## Is there a reason why this should be core and done by us?\n\nI know how to do this!\n\n## References &lt;!-- optional and numbers of links can vary --&gt;\n\n- https://github.com/electronicarts/dem-bones\n\n## Derivative License\n\nCopyright (c) 2021 V-Sekai contributors.\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
+    "text": "About issue templates, I know Godot doesn’t permit plain feature requests in the main godot issue tracker. To propose something you have to have a fleshed out proposal.\nThat works well for Godot for two reasons: Godot has lots of users so there are already too many feature proposals; and the users of Godot are developers who can be asked to do research and write a whole implementation proposal\nThe users of V-Sekai are not technical in the same way; and furthermore we are not at the scale Godot was in 3.2 when they switched to requiring proposals.\nIf we ever do get big enough that feature requests propose a burden then we can consider making it harder to file them"
   },
   {
-    "objectID": "decisions/20211005-want-to-use-the-same-cluster-for-the-same-web-and-native.html",
-    "href": "decisions/20211005-want-to-use-the-same-cluster-for-the-same-web-and-native.html",
-    "title": "Proposed: Want to use the same cluster for the same web and native.",
+    "objectID": "decisions/20221021-make-it-easier-propose-and-post-bugs.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20221021-make-it-easier-propose-and-post-bugs.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: Make it easier to propose and file bugs by simplifying the templates",
     "section": "",
-    "text": "Proposed: Want to use the same cluster for the same web and native.\n\nContext and Problem Statement\nWant to use the same cluster for the same web and native.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nBy using webrtc only, we are able to reuse the same servers.\nAn alternative of a webserver that has both webrtc and enet is also possible.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nSuppose the server cluster sets up the infrastructure. In that case, it feels like WebRTC may jump past firewalls easier, and there’s existing turn-ice stuff.\nMy colleague noted that you could have one Godot engine server provide a proxy to another Godot server. The design was similar to cell phone vs cell phone tower vs tower to tower distribution of messages. It wasn’t clear that was possible, but he found something. Any thoughts about that?\n\n\nProblems\nWebRTC is much more complex to set up, so I don’t think it is a good alternative for ENet for indies.\nWebRTC needs infrastructure; ENet does not.\nDependency problems between ScriptInstance and PacketPeer. What do you mean?\nThe script_language.h includes packet_peer.h, so PacketPeer cannot use GDVIRTUAL because that needs script_language.h\n\nQuestions\nHow do modern games different games have different bandwidth minimums?\nCents per hour to host how many players?\nHole-punching for pure peer-to-peer games.\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nThis is compiled into the project and is work to change.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nNetworking is part of the project and can’t be changed by mods.\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Modify the V-Sekai-game issue templates to be easier to use."
   },
   {
-    "objectID": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html",
-    "href": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html",
-    "title": "Proposed: Procedure to unmerge and then merge solves a V-Sekai source code broken tree",
+    "objectID": "decisions/20221021-make-it-easier-propose-and-post-bugs.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20221021-make-it-easier-propose-and-post-bugs.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Make it easier to propose and file bugs by simplifying the templates",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nThe V-Sekai source code tree has been broken due to an unsuccessful merge. This has resulted in a halt in the development process, causing delays in project timelines.\n\n\n\nThe main challenge is to unmerge the broken tree and then successfully merge it again. This requires careful analysis of the code and understanding the root cause of the initial failed merge.\n\n\n\nWe use a tool called Git Assembly which makes reapplying branches on master easy. Here’s the strategy:\n\nIdentify the commit hash where the merge went wrong.\nRemove the item from the Git Assembler.\nAnalyze the code and identify the conflicts that caused the merge to fail.\nResolve the conflicts manually.\nFix the branch.\nReapply the branch on master using Git Assembly.\n\n\n\n\nBy following this strategy, we can potentially fix the broken source code tree without losing any significant work. This will allow us to resume the development process and meet our project deadlines.\n\n\n\nThe process of unmerging and merging can be time-consuming and complex. If not done correctly, it may lead to further issues in the codebase.\n\n\n\nAn alternative approach could have been to abandon the current branch and start a new one from the last known good state. However, this would mean losing all the changes made after the last good state.\n\n\n\nThis procedure is not commonly used as merges usually go smoothly. It’s only needed when a merge results in a broken source code tree.\n\n\n\nYes, this procedure is core to our operations and is performed by our team.\n\n\n\n\nV-Sekai\nThis article is assisted by AI."
+    "text": "Remove required fields. Make them easier to use."
   },
   {
-    "objectID": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html#metadata",
-    "href": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html#metadata",
-    "title": "Proposed: Procedure to unmerge and then merge solves a V-Sekai source code broken tree",
+    "objectID": "decisions/20221021-make-it-easier-propose-and-post-bugs.html#positive-consequences",
+    "href": "decisions/20221021-make-it-easier-propose-and-post-bugs.html#positive-consequences",
+    "title": "Proposed: Make it easier to propose and file bugs by simplifying the templates",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai"
+    "text": "More bug filing\nMore proposals"
   },
   {
-    "objectID": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html#the-backdrop",
-    "href": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html#the-backdrop",
-    "title": "Proposed: Procedure to unmerge and then merge solves a V-Sekai source code broken tree",
+    "objectID": "decisions/20221021-make-it-easier-propose-and-post-bugs.html#negative-consequences",
+    "href": "decisions/20221021-make-it-easier-propose-and-post-bugs.html#negative-consequences",
+    "title": "Proposed: Make it easier to propose and file bugs by simplifying the templates",
     "section": "",
-    "text": "The V-Sekai source code tree has been broken due to an unsuccessful merge. This has resulted in a halt in the development process, causing delays in project timelines."
+    "text": "More work on the devs to catalog"
   },
   {
-    "objectID": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html#the-challenge",
-    "href": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html#the-challenge",
-    "title": "Proposed: Procedure to unmerge and then merge solves a V-Sekai source code broken tree",
+    "objectID": "decisions/20221021-make-it-easier-propose-and-post-bugs.html#option-graveyard",
+    "href": "decisions/20221021-make-it-easier-propose-and-post-bugs.html#option-graveyard",
+    "title": "Proposed: Make it easier to propose and file bugs by simplifying the templates",
     "section": "",
-    "text": "The main challenge is to unmerge the broken tree and then successfully merge it again. This requires careful analysis of the code and understanding the root cause of the initial failed merge."
+    "text": "Option: The status quo. \nRejection Reason: This solves nothing."
   },
   {
-    "objectID": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html#the-strategy",
-    "href": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html#the-strategy",
-    "title": "Proposed: Procedure to unmerge and then merge solves a V-Sekai source code broken tree",
+    "objectID": "decisions/20221021-make-it-easier-propose-and-post-bugs.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20221021-make-it-easier-propose-and-post-bugs.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Make it easier to propose and file bugs by simplifying the templates",
     "section": "",
-    "text": "We use a tool called Git Assembly which makes reapplying branches on master easy. Here’s the strategy:\n\nIdentify the commit hash where the merge went wrong.\nRemove the item from the Git Assembler.\nAnalyze the code and identify the conflicts that caused the merge to fail.\nResolve the conflicts manually.\nFix the branch.\nReapply the branch on master using Git Assembly."
+    "text": "Not a script."
   },
   {
-    "objectID": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html#the-upside",
-    "href": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html#the-upside",
-    "title": "Proposed: Procedure to unmerge and then merge solves a V-Sekai source code broken tree",
+    "objectID": "decisions/20221021-make-it-easier-propose-and-post-bugs.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20221021-make-it-easier-propose-and-post-bugs.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Make it easier to propose and file bugs by simplifying the templates",
     "section": "",
-    "text": "By following this strategy, we can potentially fix the broken source code tree without losing any significant work. This will allow us to resume the development process and meet our project deadlines."
+    "text": "We own the repos."
   },
   {
-    "objectID": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html#the-downside",
-    "href": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html#the-downside",
-    "title": "Proposed: Procedure to unmerge and then merge solves a V-Sekai source code broken tree",
+    "objectID": "decisions/20221021-make-it-easier-propose-and-post-bugs.html#references",
+    "href": "decisions/20221021-make-it-easier-propose-and-post-bugs.html#references",
+    "title": "Proposed: Make it easier to propose and file bugs by simplifying the templates",
     "section": "",
-    "text": "The process of unmerging and merging can be time-consuming and complex. If not done correctly, it may lead to further issues in the codebase."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html#the-road-not-taken",
-    "href": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html#the-road-not-taken",
-    "title": "Proposed: Procedure to unmerge and then merge solves a V-Sekai source code broken tree",
+    "objectID": "decisions/20221021-make-it-easier-propose-and-post-bugs.html#license-of-the-contribution",
+    "href": "decisions/20221021-make-it-easier-propose-and-post-bugs.html#license-of-the-contribution",
+    "title": "Proposed: Make it easier to propose and file bugs by simplifying the templates",
     "section": "",
-    "text": "An alternative approach could have been to abandon the current branch and start a new one from the last known good state. However, this would mean losing all the changes made after the last good state."
+    "text": "Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html#the-infrequent-use-case",
-    "href": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html#the-infrequent-use-case",
-    "title": "Proposed: Procedure to unmerge and then merge solves a V-Sekai source code broken tree",
+    "objectID": "decisions/20210523-retarget-motion-for-vrm-type-models.html",
+    "href": "decisions/20210523-retarget-motion-for-vrm-type-models.html",
+    "title": "Proposed: Retarget VRM Motion Blender Workflow",
     "section": "",
-    "text": "This procedure is not commonly used as merges usually go smoothly. It’s only needed when a merge results in a broken source code tree."
+    "text": "We need to retarget motion for VRM type models.\nThis is a lengthy offline process to retarget other motions to VRM type models.\n\n\n\nUse Blender to retarget t-posed characters.\n\n\n\nInputs: bvh + t-pose avatar\nOutput: glb w/retargetted animation\n\n\n\n\nBlender v2.91 or v2.92 (may work with other versions)\nBlender Add-On: skeletal-motion-retarget-blender\n\nDownload .zip\nUse Blender Edit =&gt; Preferences, Add-ons, Install that zip\nCheck the box for the new install an add-on to activate\n\n(optional) if using a VRM avatar Blender Add-On: saturday06/VRM_Addon_for_Blender\n\nDownload .zip\nUse Blender Edit =&gt; Preferences, Add-ons, Install that zip\nCheck the box for the newly install an add-on to activate\n\n\n\n\n\n\n\nHave a rigged, T-Pose humanoid avatar\nStart a new scene?\n\nUnder the Scene Settings property panel, set Frame Rate to 30 fps\n(or you may want to match your .mp4 frame rate used during capture)\n\nImport your avatar model\n\nif using a VRM avatar, be sure to use Import VRM (otherwise, retargeting may not work!)\n\nImport the generated BVH. In the Animation section, enable the following options\n\nScale FPS\nScene Duration\n\nUse the Pose Transfer tab (vertical tab part of the “N” options panel?)\n\nSource: the imported BVH armature\nTarget: the imported avatar armature\nClick the Rebuild Bone List\n\nmanually map over any bones not automatically mapped\neg: LeftLowerArm =&gt; “Left elbow”\nnote: it is possible to save your mapping to .json and reuse\n\nClick Retarget Animation\n\nretargeting may take several minutes\n\n\nVerify retargeting by playing the animation via the Blender play button\nExport the scene as a .glb (using default settings)\n\n\n\n\nQ: Retargeted animation seems to have legs crossed / backwards\nA: This can happen if you import a VRM avatar as a .gltf (re-import using the VRM importer add-on)\nQ: Legs/arms bend unnaturally\nA: Check the armature bone name mappings\n\nat most, each target bone name should appear once\nleave BVH joints not present in your avatar blank\n\n\n\n\nThanks to humbletim for being the scribe\nThanks to lyuma for being test pilot flying these steps\n\n\n\n\nHave a generally robust process of retargeting motions to VRM-type models.\n\n\n\n\n\nOnly VRM\nMMD does not work.\n\n\n\n\n\nList the reasons for the rejection: (the Bad traits)\n\nProprietary Online Service\nBlackbox technology\n\n\n\n\nMotion retargeting is not trivial offline or online.\n\n\n\nWe need motions for our character controller without using an off-the-shelf black box solution.\n\n\n\n\nhttps://www.blender.org/\nhttps://hackmd.io/EmOAt375S8KFqaNdPDJCXQ\nhttps://github.com/V-Sekai/V-Sekai-Blender-tools/tree/main/addons/blender-skeletal-motion-animate\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html#in-core-and-done-by-us",
-    "href": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html#in-core-and-done-by-us",
-    "title": "Proposed: Procedure to unmerge and then merge solves a V-Sekai source code broken tree",
+    "objectID": "decisions/20210523-retarget-motion-for-vrm-type-models.html#context-and-problem-statement",
+    "href": "decisions/20210523-retarget-motion-for-vrm-type-models.html#context-and-problem-statement",
+    "title": "Proposed: Retarget VRM Motion Blender Workflow",
     "section": "",
-    "text": "Yes, this procedure is core to our operations and is performed by our team."
+    "text": "We need to retarget motion for VRM type models.\nThis is a lengthy offline process to retarget other motions to VRM type models."
   },
   {
-    "objectID": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html#further-reading",
-    "href": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html#further-reading",
-    "title": "Proposed: Procedure to unmerge and then merge solves a V-Sekai source code broken tree",
+    "objectID": "decisions/20210523-retarget-motion-for-vrm-type-models.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20210523-retarget-motion-for-vrm-type-models.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: Retarget VRM Motion Blender Workflow",
     "section": "",
-    "text": "V-Sekai\nThis article is assisted by AI."
+    "text": "Use Blender to retarget t-posed characters.\n\n\n\nInputs: bvh + t-pose avatar\nOutput: glb w/retargetted animation\n\n\n\n\nBlender v2.91 or v2.92 (may work with other versions)\nBlender Add-On: skeletal-motion-retarget-blender\n\nDownload .zip\nUse Blender Edit =&gt; Preferences, Add-ons, Install that zip\nCheck the box for the new install an add-on to activate\n\n(optional) if using a VRM avatar Blender Add-On: saturday06/VRM_Addon_for_Blender\n\nDownload .zip\nUse Blender Edit =&gt; Preferences, Add-ons, Install that zip\nCheck the box for the newly install an add-on to activate\n\n\n\n\n\n\n\nHave a rigged, T-Pose humanoid avatar\nStart a new scene?\n\nUnder the Scene Settings property panel, set Frame Rate to 30 fps\n(or you may want to match your .mp4 frame rate used during capture)\n\nImport your avatar model\n\nif using a VRM avatar, be sure to use Import VRM (otherwise, retargeting may not work!)\n\nImport the generated BVH. In the Animation section, enable the following options\n\nScale FPS\nScene Duration\n\nUse the Pose Transfer tab (vertical tab part of the “N” options panel?)\n\nSource: the imported BVH armature\nTarget: the imported avatar armature\nClick the Rebuild Bone List\n\nmanually map over any bones not automatically mapped\neg: LeftLowerArm =&gt; “Left elbow”\nnote: it is possible to save your mapping to .json and reuse\n\nClick Retarget Animation\n\nretargeting may take several minutes\n\n\nVerify retargeting by playing the animation via the Blender play button\nExport the scene as a .glb (using default settings)\n\n\n\n\nQ: Retargeted animation seems to have legs crossed / backwards\nA: This can happen if you import a VRM avatar as a .gltf (re-import using the VRM importer add-on)\nQ: Legs/arms bend unnaturally\nA: Check the armature bone name mappings\n\nat most, each target bone name should appear once\nleave BVH joints not present in your avatar blank\n\n\n\n\nThanks to humbletim for being the scribe\nThanks to lyuma for being test pilot flying these steps\n\n\n\n\nHave a generally robust process of retargeting motions to VRM-type models.\n\n\n\n\n\nOnly VRM\nMMD does not work."
   },
   {
-    "objectID": "decisions/20220224-v-sekai-version-two-plan.html",
-    "href": "decisions/20220224-v-sekai-version-two-plan.html",
-    "title": "Superseded: Planning V-Sekai Version 2 on 2022-02-24",
+    "objectID": "decisions/20210523-retarget-motion-for-vrm-type-models.html#option-graveyard-adobe-mixamo",
+    "href": "decisions/20210523-retarget-motion-for-vrm-type-models.html#option-graveyard-adobe-mixamo",
+    "title": "Proposed: Retarget VRM Motion Blender Workflow",
     "section": "",
-    "text": "Status: superseded by 20220228-v-sekai-version-three-plan.md \nDeciders: V-Sekai,ifire,lyuma,\nTags: V-Sekai,\n\n\n\nKnow where we’re going by describing what we want.\n\n\n\nProposed mission and a list of tasks.\n\n\n\n\n\n\nGodot Engine pull requests.\n\n\n\n\n\nOne gitlab repo with source assets? (sky celebration and sponza).\n\n\nThe ability to upload maps and avatars standalone via a SDK (set of submodules?) https://github.com/V-Sekai/vsk_sdk.\n\nBeing able to enter a vsk map ∀ maps (mvp = 1 map).\nEnter a vsk map with an entity in it (upload sky celebration OR upload sponza with one beachball).\n\nVSK_map source asset repositories\nLyuma will make a new github repo V-Sekai/vrm_submodule - we need a script for updating all submodules to the latest on a given branch.\nVSK_map source asset repositories\nI think vsk_sdk should only be submodules, no assets.\nWe can git rebase -i to remove the binary assets from it.\ngit merge to install the vsk_sdk into another project (such as gitlab). we need to look if git subtree supports .gitmodules and we can use it if it does.\nmake vsk_sdk the head for all of the sdk related submodules. do our development there and commit submodules regularly.\nIn groups project, pretend we delete all submodules in vsk_sdk. Then git merge vsk_sdk/main to bring in the submodules from that repo.\nEvery time we update vsk_sdk, do a git merge into groups and our source asset repo with sponza etc.\nVSK_map source asset repositories\n\nDon’t save .scn assets in git.\n\nno GLB.\nblend files ~10MB ok. &gt; 100MB let’s either use GitLab LFS or something else.\nEvaluate https://dvc.org/\n\n\n\n\nBeing able to have our group of people join and communicate. (godot speech).\n\n\nPorting C++ was discussed as a way forward to make it easier to debug\n\n\nVR support (openxr).\nInteracting with objects in desktop mode is important so that we can test easier.\nInteracting with objects in vr.\nScripting (wasgo).\nNetwork server to support 1000.\n\n\n\n\n\nGain clarity of mission.\n\n\n\n\nThe cost of overhead.\n\n\n\n\n\nOption: Status quo. \nRejection Reason: Complete the wrong thing. \n\n\n\n\nThis is a planning document.\n\n\n\nWe know what we want to do.\n\n\n\n\nNone\n\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "List the reasons for the rejection: (the Bad traits)\n\nProprietary Online Service\nBlackbox technology"
   },
   {
-    "objectID": "decisions/20220224-v-sekai-version-two-plan.html#context-and-problem-statement",
-    "href": "decisions/20220224-v-sekai-version-two-plan.html#context-and-problem-statement",
-    "title": "Superseded: Planning V-Sekai Version 2 on 2022-02-24",
+    "objectID": "decisions/20210523-retarget-motion-for-vrm-type-models.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20210523-retarget-motion-for-vrm-type-models.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Retarget VRM Motion Blender Workflow",
     "section": "",
-    "text": "Know where we’re going by describing what we want."
+    "text": "Motion retargeting is not trivial offline or online."
   },
   {
-    "objectID": "decisions/20220224-v-sekai-version-two-plan.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20220224-v-sekai-version-two-plan.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Superseded: Planning V-Sekai Version 2 on 2022-02-24",
+    "objectID": "decisions/20210523-retarget-motion-for-vrm-type-models.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20210523-retarget-motion-for-vrm-type-models.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Retarget VRM Motion Blender Workflow",
     "section": "",
-    "text": "Proposed mission and a list of tasks."
+    "text": "We need motions for our character controller without using an off-the-shelf black box solution."
   },
   {
-    "objectID": "decisions/20220224-v-sekai-version-two-plan.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20220224-v-sekai-version-two-plan.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Superseded: Planning V-Sekai Version 2 on 2022-02-24",
+    "objectID": "decisions/20210523-retarget-motion-for-vrm-type-models.html#references",
+    "href": "decisions/20210523-retarget-motion-for-vrm-type-models.html#references",
+    "title": "Proposed: Retarget VRM Motion Blender Workflow",
     "section": "",
-    "text": "Godot Engine pull requests.\n\n\n\n\n\nOne gitlab repo with source assets? (sky celebration and sponza).\n\n\nThe ability to upload maps and avatars standalone via a SDK (set of submodules?) https://github.com/V-Sekai/vsk_sdk.\n\nBeing able to enter a vsk map ∀ maps (mvp = 1 map).\nEnter a vsk map with an entity in it (upload sky celebration OR upload sponza with one beachball).\n\nVSK_map source asset repositories\nLyuma will make a new github repo V-Sekai/vrm_submodule - we need a script for updating all submodules to the latest on a given branch.\nVSK_map source asset repositories\nI think vsk_sdk should only be submodules, no assets.\nWe can git rebase -i to remove the binary assets from it.\ngit merge to install the vsk_sdk into another project (such as gitlab). we need to look if git subtree supports .gitmodules and we can use it if it does.\nmake vsk_sdk the head for all of the sdk related submodules. do our development there and commit submodules regularly.\nIn groups project, pretend we delete all submodules in vsk_sdk. Then git merge vsk_sdk/main to bring in the submodules from that repo.\nEvery time we update vsk_sdk, do a git merge into groups and our source asset repo with sponza etc.\nVSK_map source asset repositories\n\nDon’t save .scn assets in git.\n\nno GLB.\nblend files ~10MB ok. &gt; 100MB let’s either use GitLab LFS or something else.\nEvaluate https://dvc.org/\n\n\n\n\nBeing able to have our group of people join and communicate. (godot speech).\n\n\nPorting C++ was discussed as a way forward to make it easier to debug\n\n\nVR support (openxr).\nInteracting with objects in desktop mode is important so that we can test easier.\nInteracting with objects in vr.\nScripting (wasgo).\nNetwork server to support 1000."
+    "text": "https://www.blender.org/\nhttps://hackmd.io/EmOAt375S8KFqaNdPDJCXQ\nhttps://github.com/V-Sekai/V-Sekai-Blender-tools/tree/main/addons/blender-skeletal-motion-animate"
   },
   {
-    "objectID": "decisions/20220224-v-sekai-version-two-plan.html#positive-consequences",
-    "href": "decisions/20220224-v-sekai-version-two-plan.html#positive-consequences",
-    "title": "Superseded: Planning V-Sekai Version 2 on 2022-02-24",
+    "objectID": "decisions/20210523-retarget-motion-for-vrm-type-models.html#derivative-license",
+    "href": "decisions/20210523-retarget-motion-for-vrm-type-models.html#derivative-license",
+    "title": "Proposed: Retarget VRM Motion Blender Workflow",
     "section": "",
-    "text": "Gain clarity of mission."
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20220224-v-sekai-version-two-plan.html#negative-consequences",
-    "href": "decisions/20220224-v-sekai-version-two-plan.html#negative-consequences",
-    "title": "Superseded: Planning V-Sekai Version 2 on 2022-02-24",
+    "objectID": "decisions/20221214-powershell-autocomplete-use-right-arrow.html",
+    "href": "decisions/20221214-powershell-autocomplete-use-right-arrow.html",
+    "title": "Proposed: Powershell autocomplete uses right arrow",
     "section": "",
-    "text": "The cost of overhead."
+    "text": "Status: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nPowershell was updated and there is auto complete. However, the exact prediction command is unknown.\n\n\n\nDocument that powershell autocomplete uses the right arrow.\n\n\n\nWrite down that right arrow completes the prediction.\n\n\n\nCan auto complete.\n\n\n\nDocumentation is work.\n\n\n\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\n\nNone.\n\n\n\nI wanted to write this down and it’s not a core thing.\n\n\n\n\nV-Sekai\nhttps://mnaoumov.wordpress.com/2022/11/21/powershell-predictive-intellisense/\n\n\n\n\nMIT License\n\nCopyright (c) 2019-2022 K. S. Ernest (iFire) Lee (fire)\nCopyright (c) 2022 V-Sekai Contributors\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
   },
   {
-    "objectID": "decisions/20220224-v-sekai-version-two-plan.html#option-graveyard",
-    "href": "decisions/20220224-v-sekai-version-two-plan.html#option-graveyard",
-    "title": "Superseded: Planning V-Sekai Version 2 on 2022-02-24",
+    "objectID": "decisions/20221214-powershell-autocomplete-use-right-arrow.html#context-and-problem-statement",
+    "href": "decisions/20221214-powershell-autocomplete-use-right-arrow.html#context-and-problem-statement",
+    "title": "Proposed: Powershell autocomplete uses right arrow",
     "section": "",
-    "text": "Option: Status quo. \nRejection Reason: Complete the wrong thing."
+    "text": "Powershell was updated and there is auto complete. However, the exact prediction command is unknown."
   },
   {
-    "objectID": "decisions/20220224-v-sekai-version-two-plan.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20220224-v-sekai-version-two-plan.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Superseded: Planning V-Sekai Version 2 on 2022-02-24",
+    "objectID": "decisions/20221214-powershell-autocomplete-use-right-arrow.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20221214-powershell-autocomplete-use-right-arrow.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: Powershell autocomplete uses right arrow",
     "section": "",
-    "text": "This is a planning document."
+    "text": "Document that powershell autocomplete uses the right arrow."
   },
   {
-    "objectID": "decisions/20220224-v-sekai-version-two-plan.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20220224-v-sekai-version-two-plan.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Superseded: Planning V-Sekai Version 2 on 2022-02-24",
+    "objectID": "decisions/20221214-powershell-autocomplete-use-right-arrow.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20221214-powershell-autocomplete-use-right-arrow.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Powershell autocomplete uses right arrow",
     "section": "",
-    "text": "We know what we want to do."
+    "text": "Write down that right arrow completes the prediction."
   },
   {
-    "objectID": "decisions/20220224-v-sekai-version-two-plan.html#references",
-    "href": "decisions/20220224-v-sekai-version-two-plan.html#references",
-    "title": "Superseded: Planning V-Sekai Version 2 on 2022-02-24",
+    "objectID": "decisions/20221214-powershell-autocomplete-use-right-arrow.html#positive-consequences",
+    "href": "decisions/20221214-powershell-autocomplete-use-right-arrow.html#positive-consequences",
+    "title": "Proposed: Powershell autocomplete uses right arrow",
     "section": "",
-    "text": "None"
+    "text": "Can auto complete."
   },
   {
-    "objectID": "decisions/20220224-v-sekai-version-two-plan.html#derivative-license",
-    "href": "decisions/20220224-v-sekai-version-two-plan.html#derivative-license",
-    "title": "Superseded: Planning V-Sekai Version 2 on 2022-02-24",
+    "objectID": "decisions/20221214-powershell-autocomplete-use-right-arrow.html#negative-consequences",
+    "href": "decisions/20221214-powershell-autocomplete-use-right-arrow.html#negative-consequences",
+    "title": "Proposed: Powershell autocomplete uses right arrow",
     "section": "",
-    "text": "Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Documentation is work."
   },
   {
-    "objectID": "decisions/20231209-appium-testing-fbx-to-gltf.html",
-    "href": "decisions/20231209-appium-testing-fbx-to-gltf.html",
-    "title": "Proposed: Appium Testing for Windows 11",
+    "objectID": "decisions/20221214-powershell-autocomplete-use-right-arrow.html#option-graveyard",
+    "href": "decisions/20221214-powershell-autocomplete-use-right-arrow.html#option-graveyard",
+    "title": "Proposed: Powershell autocomplete uses right arrow",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nIn the realm of game development, providing a seamless user experience across various platforms is crucial. This necessitates the implementation of effective testing methodologies.\n\n\n\nThe primary challenge we face is the establishment of a robust testing framework that ensures cross-platform compatibility. Our focus is particularly on ensuring compatibility with the VR compatible desktop mode on Windows 11.\n\n\n\nTo address this problem, we propose the automation of the testing process using Appium. A significant part of this strategy involves the conversion of FBX files, which are commonly used formats for 3D models and animations, into GLB format.\n\n\n\nThis strategy promises to ensure a high-quality gaming experience.\n\n\n\nIt may require substantial resources and could potentially present unforeseen challenges.\n\n\n\nWe have considered other testing frameworks, but our proposed strategy with Appium offers the best balance between effectiveness and efficiency.\n\n\n\nOur strategy might not cover infrequent or edge cases in game development. However, these will be identified and addressed as they arise.\n\n\n\nYes, this strategy is core to our project and will be implemented by our team.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAssisted by Aria, an AI assistant."
+    "text": "Option: The status quo. \nRejection Reason: This solves nothing."
   },
   {
-    "objectID": "decisions/20231209-appium-testing-fbx-to-gltf.html#metadata",
-    "href": "decisions/20231209-appium-testing-fbx-to-gltf.html#metadata",
-    "title": "Proposed: Appium Testing for Windows 11",
+    "objectID": "decisions/20221214-powershell-autocomplete-use-right-arrow.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20221214-powershell-autocomplete-use-right-arrow.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Powershell autocomplete uses right arrow",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai"
+    "text": "None."
   },
   {
-    "objectID": "decisions/20231209-appium-testing-fbx-to-gltf.html#the-backdrop",
-    "href": "decisions/20231209-appium-testing-fbx-to-gltf.html#the-backdrop",
-    "title": "Proposed: Appium Testing for Windows 11",
+    "objectID": "decisions/20221214-powershell-autocomplete-use-right-arrow.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20221214-powershell-autocomplete-use-right-arrow.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Powershell autocomplete uses right arrow",
     "section": "",
-    "text": "In the realm of game development, providing a seamless user experience across various platforms is crucial. This necessitates the implementation of effective testing methodologies."
+    "text": "I wanted to write this down and it’s not a core thing."
   },
   {
-    "objectID": "decisions/20231209-appium-testing-fbx-to-gltf.html#the-challenge",
-    "href": "decisions/20231209-appium-testing-fbx-to-gltf.html#the-challenge",
-    "title": "Proposed: Appium Testing for Windows 11",
+    "objectID": "decisions/20221214-powershell-autocomplete-use-right-arrow.html#references",
+    "href": "decisions/20221214-powershell-autocomplete-use-right-arrow.html#references",
+    "title": "Proposed: Powershell autocomplete uses right arrow",
     "section": "",
-    "text": "The primary challenge we face is the establishment of a robust testing framework that ensures cross-platform compatibility. Our focus is particularly on ensuring compatibility with the VR compatible desktop mode on Windows 11."
+    "text": "V-Sekai\nhttps://mnaoumov.wordpress.com/2022/11/21/powershell-predictive-intellisense/"
   },
   {
-    "objectID": "decisions/20231209-appium-testing-fbx-to-gltf.html#the-strategy",
-    "href": "decisions/20231209-appium-testing-fbx-to-gltf.html#the-strategy",
-    "title": "Proposed: Appium Testing for Windows 11",
+    "objectID": "decisions/20221214-powershell-autocomplete-use-right-arrow.html#license-of-the-contribution",
+    "href": "decisions/20221214-powershell-autocomplete-use-right-arrow.html#license-of-the-contribution",
+    "title": "Proposed: Powershell autocomplete uses right arrow",
     "section": "",
-    "text": "To address this problem, we propose the automation of the testing process using Appium. A significant part of this strategy involves the conversion of FBX files, which are commonly used formats for 3D models and animations, into GLB format."
+    "text": "MIT License\n\nCopyright (c) 2019-2022 K. S. Ernest (iFire) Lee (fire)\nCopyright (c) 2022 V-Sekai Contributors\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
   },
   {
-    "objectID": "decisions/20231209-appium-testing-fbx-to-gltf.html#the-upside",
-    "href": "decisions/20231209-appium-testing-fbx-to-gltf.html#the-upside",
-    "title": "Proposed: Appium Testing for Windows 11",
+    "objectID": "decisions/20210528-trial-install-of-gravity-for-kubernetes.html",
+    "href": "decisions/20210528-trial-install-of-gravity-for-kubernetes.html",
+    "title": "Proposed: Trial install of Gravity for Kubernetes",
     "section": "",
-    "text": "This strategy promises to ensure a high-quality gaming experience."
+    "text": "Status: rejected\n\n\n\nGRAVITY IS EOL.\nWe have trouble installing Kubernetes.\nIt is difficult to use Kubernetes because of at least these reasons. Networking is hard, storage creation is hard and the number of steps is not split between config and install.\n\n\n\nGravity claims to be a easy to prepare system for preinstalled and airgapped Kubernetes systems.\n\n\n\nCreate a prototype for a toy problem.\nThe toy problem is serving the shader motion html/js static #website as a Kubernetes application.\nEvaluate the complexity.\n\n\n\n\nIncrease quality of life\nEasier distributon\n\n\n\n\n\nAnother layer of complexity\n\n\n\n\nKubernetes is a massive project.\n\n\n\nThis is an attempt to use off the shelf tooling.\n\n\n\n\nhttps://gravitational.com/\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20231209-appium-testing-fbx-to-gltf.html#the-downside",
-    "href": "decisions/20231209-appium-testing-fbx-to-gltf.html#the-downside",
-    "title": "Proposed: Appium Testing for Windows 11",
+    "objectID": "decisions/20210528-trial-install-of-gravity-for-kubernetes.html#context-and-problem-statement",
+    "href": "decisions/20210528-trial-install-of-gravity-for-kubernetes.html#context-and-problem-statement",
+    "title": "Proposed: Trial install of Gravity for Kubernetes",
     "section": "",
-    "text": "It may require substantial resources and could potentially present unforeseen challenges."
+    "text": "GRAVITY IS EOL.\nWe have trouble installing Kubernetes.\nIt is difficult to use Kubernetes because of at least these reasons. Networking is hard, storage creation is hard and the number of steps is not split between config and install."
   },
   {
-    "objectID": "decisions/20231209-appium-testing-fbx-to-gltf.html#the-road-not-taken",
-    "href": "decisions/20231209-appium-testing-fbx-to-gltf.html#the-road-not-taken",
-    "title": "Proposed: Appium Testing for Windows 11",
+    "objectID": "decisions/20210528-trial-install-of-gravity-for-kubernetes.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20210528-trial-install-of-gravity-for-kubernetes.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: Trial install of Gravity for Kubernetes",
     "section": "",
-    "text": "We have considered other testing frameworks, but our proposed strategy with Appium offers the best balance between effectiveness and efficiency."
+    "text": "Gravity claims to be a easy to prepare system for preinstalled and airgapped Kubernetes systems."
   },
   {
-    "objectID": "decisions/20231209-appium-testing-fbx-to-gltf.html#the-infrequent-use-case",
-    "href": "decisions/20231209-appium-testing-fbx-to-gltf.html#the-infrequent-use-case",
-    "title": "Proposed: Appium Testing for Windows 11",
+    "objectID": "decisions/20210528-trial-install-of-gravity-for-kubernetes.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-andor-diagrams",
+    "href": "decisions/20210528-trial-install-of-gravity-for-kubernetes.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-andor-diagrams",
+    "title": "Proposed: Trial install of Gravity for Kubernetes",
     "section": "",
-    "text": "Our strategy might not cover infrequent or edge cases in game development. However, these will be identified and addressed as they arise."
+    "text": "Create a prototype for a toy problem.\nThe toy problem is serving the shader motion html/js static #website as a Kubernetes application.\nEvaluate the complexity."
   },
   {
-    "objectID": "decisions/20231209-appium-testing-fbx-to-gltf.html#in-core-and-done-by-us",
-    "href": "decisions/20231209-appium-testing-fbx-to-gltf.html#in-core-and-done-by-us",
-    "title": "Proposed: Appium Testing for Windows 11",
+    "objectID": "decisions/20210528-trial-install-of-gravity-for-kubernetes.html#positive-consequences",
+    "href": "decisions/20210528-trial-install-of-gravity-for-kubernetes.html#positive-consequences",
+    "title": "Proposed: Trial install of Gravity for Kubernetes",
     "section": "",
-    "text": "Yes, this strategy is core to our project and will be implemented by our team."
+    "text": "Increase quality of life\nEasier distributon"
   },
   {
-    "objectID": "decisions/20231209-appium-testing-fbx-to-gltf.html#further-reading",
-    "href": "decisions/20231209-appium-testing-fbx-to-gltf.html#further-reading",
-    "title": "Proposed: Appium Testing for Windows 11",
+    "objectID": "decisions/20210528-trial-install-of-gravity-for-kubernetes.html#negative-consequences",
+    "href": "decisions/20210528-trial-install-of-gravity-for-kubernetes.html#negative-consequences",
+    "title": "Proposed: Trial install of Gravity for Kubernetes",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAssisted by Aria, an AI assistant."
+    "text": "Another layer of complexity"
   },
   {
-    "objectID": "decisions/20230505-consistent-v-sekai-naming.html",
-    "href": "decisions/20230505-consistent-v-sekai-naming.html",
-    "title": "Proposed: Solve a V-Sekai naming convention limitation.",
+    "objectID": "decisions/20210528-trial-install-of-gravity-for-kubernetes.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20210528-trial-install-of-gravity-for-kubernetes.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Trial install of Gravity for Kubernetes",
     "section": "",
-    "text": "Status: proposed \nDeciders: V-Sekai,fire,\nTags: V-Sekai,chatgpt4,naming conventions,standardization,code organization,documentation,project management,\n\n\n\n\nWe use different kinds of names for V-Sekai, such as v-sekai, V-Sekai, vsk, and v_sekai. It is confusing to find a scheme that fits the various naming conventions. Hyphens are banned in Godot Engine file systems, but allowed in GitHub branch names. We also use the godot_addon convention sometimes. How can we document and unify the naming conventions across different platforms and contexts?\n\n\n\nCreate a standardized naming convention guideline that defines the preferred format for all instances of V-Sekai’s name in code, documentation, and other materials, taking into account the specific requirements and limitations of each platform and context.\n\n\n\n\nDefine the preferred naming convention for V-Sekai in different contexts:\n\nGodot Engine file systems: vsk_default\nGitHub branch names: v-sekai-wasm\nAddon naming: addons/vsk_avatar\nGithub repository names must all be lowercase:\n\nGitHub is case-insensitive: this can result in users or devs inadvertently typing the wrong case in one case\nWindows is case-insensitive, so the above mistake can go unnoticed until the addon is used on a different OS\n\n\nCreate a guideline document outlining the naming convention rules for each context.\nUpdate existing code, documentation, and materials to follow the new naming conventions.\nEnforce the naming conventions in future development and contributions.\n\n# Example of following the naming convention in Godot Engine file system\nvsk_default/core/object.gd\n\n# Example of following the naming convention in GitHub branch names\nv-sekai-wasm\n\n# Example of following the naming convention for addons\naddons/vsk_avatar # in the file system\ngodot_vsk_avatar # on Github\n\n\n\n\nConsistent naming conventions across different platforms and contexts.\nReduced confusion among developers and users.\n\n\n\n\n\nTime and effort required to update existing code and materials to follow the new naming conventions.\n\n\n\n\nDoing nothing is a problem.\n\n\n\nNo, establishing consistent naming conventions requires updating all instances of V-Sekai’s name across the project and cannot be achieved with a simple script.\n\n\n\nYes, maintaining consistent naming conventions is essential for a professional and well-organized project. It will improve the overall quality of the codebase and documentation, making it easier for developers and users to understand and work with V-Sekai.\n\n\n\n\nV-Sekai\ngoblin.tools: https://goblin.tools/\nopenai: https://openai.com/"
+    "text": "Kubernetes is a massive project."
   },
   {
-    "objectID": "decisions/20230505-consistent-v-sekai-naming.html#metadata",
-    "href": "decisions/20230505-consistent-v-sekai-naming.html#metadata",
-    "title": "Proposed: Solve a V-Sekai naming convention limitation.",
+    "objectID": "decisions/20210528-trial-install-of-gravity-for-kubernetes.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20210528-trial-install-of-gravity-for-kubernetes.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Trial install of Gravity for Kubernetes",
     "section": "",
-    "text": "Status: proposed \nDeciders: V-Sekai,fire,\nTags: V-Sekai,chatgpt4,naming conventions,standardization,code organization,documentation,project management,"
+    "text": "This is an attempt to use off the shelf tooling."
   },
   {
-    "objectID": "decisions/20230505-consistent-v-sekai-naming.html#context-and-problem-statement",
-    "href": "decisions/20230505-consistent-v-sekai-naming.html#context-and-problem-statement",
-    "title": "Proposed: Solve a V-Sekai naming convention limitation.",
+    "objectID": "decisions/20210528-trial-install-of-gravity-for-kubernetes.html#references",
+    "href": "decisions/20210528-trial-install-of-gravity-for-kubernetes.html#references",
+    "title": "Proposed: Trial install of Gravity for Kubernetes",
     "section": "",
-    "text": "We use different kinds of names for V-Sekai, such as v-sekai, V-Sekai, vsk, and v_sekai. It is confusing to find a scheme that fits the various naming conventions. Hyphens are banned in Godot Engine file systems, but allowed in GitHub branch names. We also use the godot_addon convention sometimes. How can we document and unify the naming conventions across different platforms and contexts?"
+    "text": "https://gravitational.com/"
   },
   {
-    "objectID": "decisions/20230505-consistent-v-sekai-naming.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20230505-consistent-v-sekai-naming.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: Solve a V-Sekai naming convention limitation.",
+    "objectID": "decisions/20210528-trial-install-of-gravity-for-kubernetes.html#derivative-license",
+    "href": "decisions/20210528-trial-install-of-gravity-for-kubernetes.html#derivative-license",
+    "title": "Proposed: Trial install of Gravity for Kubernetes",
     "section": "",
-    "text": "Create a standardized naming convention guideline that defines the preferred format for all instances of V-Sekai’s name in code, documentation, and other materials, taking into account the specific requirements and limitations of each platform and context."
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230505-consistent-v-sekai-naming.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20230505-consistent-v-sekai-naming.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Solve a V-Sekai naming convention limitation.",
+    "objectID": "decisions/20230516-v-sekai-roadmap.html",
+    "href": "decisions/20230516-v-sekai-roadmap.html",
+    "title": "Superseded: V-Sekai Roadmap and Goals 2023-05-16",
     "section": "",
-    "text": "Define the preferred naming convention for V-Sekai in different contexts:\n\nGodot Engine file systems: vsk_default\nGitHub branch names: v-sekai-wasm\nAddon naming: addons/vsk_avatar\nGithub repository names must all be lowercase:\n\nGitHub is case-insensitive: this can result in users or devs inadvertently typing the wrong case in one case\nWindows is case-insensitive, so the above mistake can go unnoticed until the addon is used on a different OS\n\n\nCreate a guideline document outlining the naming convention rules for each context.\nUpdate existing code, documentation, and materials to follow the new naming conventions.\nEnforce the naming conventions in future development and contributions.\n\n# Example of following the naming convention in Godot Engine file system\nvsk_default/core/object.gd\n\n# Example of following the naming convention in GitHub branch names\nv-sekai-wasm\n\n# Example of following the naming convention for addons\naddons/vsk_avatar # in the file system\ngodot_vsk_avatar # on Github"
+    "text": "Superseded: V-Sekai Roadmap and Goals 2023-05-16\n\nMetadata\n\nStatus: superseded by 20230519-v-sekai-roadmap.md \nDeciders: V-Sekai,fire,lyuma,\nTags: V-Sekai,chatgpt4 summary,\n\n\n\nContext and Problem Statement\nWhat is the V-Sekai Roadmap and Goals?\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nThe roadmap presented here is short-term.\n\n\nDescribe how your proposal will work with code, pseudo-code, mock-ups, or diagrams\ngraph LR\n  subgraph Short Term\n    A[May 16th, 2023] --&gt; B[Solving SkeletonIK3D before May 30th. Will literally debug the two implementations in lockstep.]\n    B --&gt; C[Assist Tokageit with Godot Engine 4.1 features before May 30th feature freeze]\n    B --&gt; D[Assist Godot Engine 4.1 features before May 30th feature freeze]\n    C --&gt; E\n    D --&gt; E[Vrm upload to the asset library after May 30th, 2023]\n    E --&gt; F[Unidot fix import bugs that blocked assets import]\n    F --&gt; G[Unidot Unity Import upload to the asset library after May 30th, 2023]\n    G --&gt; H[Implement onevoip]\n  end\n\n\nPositive Consequences\nWe can create V-Sekai easier.\n\n\nNegative Consequences\nOverhead might be hard.\n\n\nOption graveyard\n\nImplementing a custom voice chat solution instead of using onevoip\nWaiting for Godot Engine 4.2 instead of assisting with 4.1 features\nIgnoring SkeletonIK3D issues and focusing on other aspects\n\n\n\nIf this enhancement will be used infrequently, can it be worked around with a few lines of script?\nNo. This is a process.\n\n\nIs there a reason why this should be core and done by us?\nThis is a core process for V-Sekai.\n\n\nReferences\n\nV-Sekai"
   },
   {
-    "objectID": "decisions/20230505-consistent-v-sekai-naming.html#positive-consequences",
-    "href": "decisions/20230505-consistent-v-sekai-naming.html#positive-consequences",
-    "title": "Proposed: Solve a V-Sekai naming convention limitation.",
+    "objectID": "decisions/20240401-shader-graphic.html",
+    "href": "decisions/20240401-shader-graphic.html",
+    "title": "Proposed: Material Shader Graphic Shirt with Sharp Edges",
     "section": "",
-    "text": "Consistent naming conventions across different platforms and contexts.\nReduced confusion among developers and users."
+    "text": "In the vibrant and ever-evolving realm of virtual reality, personal expression is paramount. Users crave the ability to showcase their unique style and personality through their avatars. One powerful avenue for this self-expression is through avatar apparel customization. In this scenario, we’re exploring the creation of a virtual shirt adorned with two distinct patterns. These patterns are applied using SVG files that are converted into a signed distance field mask, ensuring the edges remain crisp and sharp.\n\n\n\nAt present, there’s no straightforward method to design a shirt featuring two different patterns using SVG files in MaterialX, while also maintaining sharp pattern edges. This proposal seeks to address and resolve this issue.\n\n\n\nWe can harness the power of MaterialX’s shader graph system to craft a custom shader for our shirt. Here’s a rudimentary sketch of how it might be structured:\n# Import MaterialX library\nimport MaterialX as mx\n\n# Create a new document\ndoc = mx.createDocument()\n\n# Create a new shader graph\nshaderGraph = doc.addNode('shadergraph', 'myShaderGraph', 'surfaceshader')\n\n# Add two image nodes for our SVG patterns\npattern1 = shaderGraph.addInput('pattern1', 'filename')\npattern2 = shaderGraph.addInput('pattern2', 'filename')\n\n# Convert SVGs to signed distance fields for sharp edges\nsdfPattern1 = convertSVGToSDF(pattern1)\nsdfPattern2 = convertSVGToSDF(pattern2)\n\n# Add a mix node to blend the two patterns together\nmix = shaderGraph.addNode('mix', 'mix', 'color3')\nmix.setInputValue('fg', sdfPattern1)\nmix.setInputValue('bg', sdfPattern2)\n\n# Connect the mix node to the shader graph output\nshaderGraph.setOutputValue(mix)\nPlease note, this is a simplified example and may require adjustments based on your project’s specific needs.\n\n\n\nImplementing this feature will empower users with additional options for avatar customization. This could potentially boost user engagement and satisfaction. Moreover, by utilizing signed distance fields, we can guarantee sharp pattern edges, enhancing the visual appeal of the shirt.\n\n\n\nThe primary drawback is that this feature could potentially amplify the complexity of the codebase. It may also necessitate additional resources for implementation and ongoing maintenance.\n\n\n\nAn alternative approach might involve using a different library or tool that already supports this feature. However, this could potentially introduce other challenges such as compatibility issues or increased project complexity.\n\n\n\nThis feature might not see frequent use if the majority of users favor simpler designs for their avatars’ clothing. Nonetheless, it could still prove beneficial for those desiring more advanced customization options.\n\n\n\nThis feature will be developed by the V-Sekai development team and will form an integral part of our project’s core functionality.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20230505-consistent-v-sekai-naming.html#negative-consequences",
-    "href": "decisions/20230505-consistent-v-sekai-naming.html#negative-consequences",
-    "title": "Proposed: Solve a V-Sekai naming convention limitation.",
+    "objectID": "decisions/20240401-shader-graphic.html#the-context",
+    "href": "decisions/20240401-shader-graphic.html#the-context",
+    "title": "Proposed: Material Shader Graphic Shirt with Sharp Edges",
     "section": "",
-    "text": "Time and effort required to update existing code and materials to follow the new naming conventions."
+    "text": "In the vibrant and ever-evolving realm of virtual reality, personal expression is paramount. Users crave the ability to showcase their unique style and personality through their avatars. One powerful avenue for this self-expression is through avatar apparel customization. In this scenario, we’re exploring the creation of a virtual shirt adorned with two distinct patterns. These patterns are applied using SVG files that are converted into a signed distance field mask, ensuring the edges remain crisp and sharp."
   },
   {
-    "objectID": "decisions/20230505-consistent-v-sekai-naming.html#option-graveyard",
-    "href": "decisions/20230505-consistent-v-sekai-naming.html#option-graveyard",
-    "title": "Proposed: Solve a V-Sekai naming convention limitation.",
+    "objectID": "decisions/20240401-shader-graphic.html#the-problem-statement",
+    "href": "decisions/20240401-shader-graphic.html#the-problem-statement",
+    "title": "Proposed: Material Shader Graphic Shirt with Sharp Edges",
     "section": "",
-    "text": "Doing nothing is a problem."
+    "text": "At present, there’s no straightforward method to design a shirt featuring two different patterns using SVG files in MaterialX, while also maintaining sharp pattern edges. This proposal seeks to address and resolve this issue."
   },
   {
-    "objectID": "decisions/20230505-consistent-v-sekai-naming.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230505-consistent-v-sekai-naming.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Solve a V-Sekai naming convention limitation.",
+    "objectID": "decisions/20240401-shader-graphic.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240401-shader-graphic.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Material Shader Graphic Shirt with Sharp Edges",
     "section": "",
-    "text": "No, establishing consistent naming conventions requires updating all instances of V-Sekai’s name across the project and cannot be achieved with a simple script."
+    "text": "We can harness the power of MaterialX’s shader graph system to craft a custom shader for our shirt. Here’s a rudimentary sketch of how it might be structured:\n# Import MaterialX library\nimport MaterialX as mx\n\n# Create a new document\ndoc = mx.createDocument()\n\n# Create a new shader graph\nshaderGraph = doc.addNode('shadergraph', 'myShaderGraph', 'surfaceshader')\n\n# Add two image nodes for our SVG patterns\npattern1 = shaderGraph.addInput('pattern1', 'filename')\npattern2 = shaderGraph.addInput('pattern2', 'filename')\n\n# Convert SVGs to signed distance fields for sharp edges\nsdfPattern1 = convertSVGToSDF(pattern1)\nsdfPattern2 = convertSVGToSDF(pattern2)\n\n# Add a mix node to blend the two patterns together\nmix = shaderGraph.addNode('mix', 'mix', 'color3')\nmix.setInputValue('fg', sdfPattern1)\nmix.setInputValue('bg', sdfPattern2)\n\n# Connect the mix node to the shader graph output\nshaderGraph.setOutputValue(mix)\nPlease note, this is a simplified example and may require adjustments based on your project’s specific needs."
   },
   {
-    "objectID": "decisions/20230505-consistent-v-sekai-naming.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230505-consistent-v-sekai-naming.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Solve a V-Sekai naming convention limitation.",
+    "objectID": "decisions/20240401-shader-graphic.html#the-benefits",
+    "href": "decisions/20240401-shader-graphic.html#the-benefits",
+    "title": "Proposed: Material Shader Graphic Shirt with Sharp Edges",
     "section": "",
-    "text": "Yes, maintaining consistent naming conventions is essential for a professional and well-organized project. It will improve the overall quality of the codebase and documentation, making it easier for developers and users to understand and work with V-Sekai."
+    "text": "Implementing this feature will empower users with additional options for avatar customization. This could potentially boost user engagement and satisfaction. Moreover, by utilizing signed distance fields, we can guarantee sharp pattern edges, enhancing the visual appeal of the shirt."
   },
   {
-    "objectID": "decisions/20230505-consistent-v-sekai-naming.html#references",
-    "href": "decisions/20230505-consistent-v-sekai-naming.html#references",
-    "title": "Proposed: Solve a V-Sekai naming convention limitation.",
+    "objectID": "decisions/20240401-shader-graphic.html#the-downsides",
+    "href": "decisions/20240401-shader-graphic.html#the-downsides",
+    "title": "Proposed: Material Shader Graphic Shirt with Sharp Edges",
     "section": "",
-    "text": "V-Sekai\ngoblin.tools: https://goblin.tools/\nopenai: https://openai.com/"
+    "text": "The primary drawback is that this feature could potentially amplify the complexity of the codebase. It may also necessitate additional resources for implementation and ongoing maintenance."
   },
   {
-    "objectID": "decisions/20230812-constraint-all-bones.html",
-    "href": "decisions/20230812-constraint-all-bones.html",
-    "title": "Proposed: Constrain the entire Godot Humanoid Skeleton",
+    "objectID": "decisions/20240401-shader-graphic.html#the-road-not-taken",
+    "href": "decisions/20240401-shader-graphic.html#the-road-not-taken",
+    "title": "Proposed: Material Shader Graphic Shirt with Sharp Edges",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai, fire\nTags: V-Sekai\n\n\n\n\nThe current Godot humanoid skeleton system lacks proper constraints for all bones, specifically in terms of rotation swing and rotation twist limits. This has led to issues when trying to move parts of the skeleton such as the head or legs towards the torso.\n\n\n\nThe challenge lies in implementing these constraints without causing other issues within the system. Some bones are not solved and should not be constrained, adding complexity to the task.\n\n\n\nThe strategy is to carefully analyze each bone and determine the appropriate constraints. This will involve a combination of swing rotation and twist rotation constraints, depending on the specific bone.\n\n\n\nBy implementing these constraints, we can improve the functionality and reliability of the Godot humanoid skeleton system. This will allow for more realistic movements and prevent system errors when moving certain parts of the skeleton.\n\n\n\nThere may be potential challenges in implementing these constraints, particularly for the unsolved bones. It will require careful testing and adjustment to ensure that the new constraints do not introduce new issues.\n\n\n\nAn alternative would be to leave the system as it is, accepting its limitations. However, this would mean missing out on the potential improvements that could be achieved through this proposal.\n\n\n\nIn some rare cases, the lack of constraints might actually be beneficial, allowing for unusual or exaggerated movements. These cases will need to be considered and potentially addressed separately.\n\n\n\nYes, this change would be implemented in the core system by the V-Sekai team.\n\n\n\n\nV-Sekai\nThis article is assisted by AI."
+    "text": "An alternative approach might involve using a different library or tool that already supports this feature. However, this could potentially introduce other challenges such as compatibility issues or increased project complexity."
   },
   {
-    "objectID": "decisions/20230812-constraint-all-bones.html#metadata",
-    "href": "decisions/20230812-constraint-all-bones.html#metadata",
-    "title": "Proposed: Constrain the entire Godot Humanoid Skeleton",
+    "objectID": "decisions/20240401-shader-graphic.html#the-infrequent-use-case",
+    "href": "decisions/20240401-shader-graphic.html#the-infrequent-use-case",
+    "title": "Proposed: Material Shader Graphic Shirt with Sharp Edges",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai, fire\nTags: V-Sekai"
+    "text": "This feature might not see frequent use if the majority of users favor simpler designs for their avatars’ clothing. Nonetheless, it could still prove beneficial for those desiring more advanced customization options."
   },
   {
-    "objectID": "decisions/20230812-constraint-all-bones.html#the-backdrop",
-    "href": "decisions/20230812-constraint-all-bones.html#the-backdrop",
-    "title": "Proposed: Constrain the entire Godot Humanoid Skeleton",
+    "objectID": "decisions/20240401-shader-graphic.html#in-core-and-done-by-us",
+    "href": "decisions/20240401-shader-graphic.html#in-core-and-done-by-us",
+    "title": "Proposed: Material Shader Graphic Shirt with Sharp Edges",
     "section": "",
-    "text": "The current Godot humanoid skeleton system lacks proper constraints for all bones, specifically in terms of rotation swing and rotation twist limits. This has led to issues when trying to move parts of the skeleton such as the head or legs towards the torso."
+    "text": "This feature will be developed by the V-Sekai development team and will form an integral part of our project’s core functionality."
   },
   {
-    "objectID": "decisions/20230812-constraint-all-bones.html#the-challenge",
-    "href": "decisions/20230812-constraint-all-bones.html#the-challenge",
-    "title": "Proposed: Constrain the entire Godot Humanoid Skeleton",
+    "objectID": "decisions/20240401-shader-graphic.html#status",
+    "href": "decisions/20240401-shader-graphic.html#status",
+    "title": "Proposed: Material Shader Graphic Shirt with Sharp Edges",
     "section": "",
-    "text": "The challenge lies in implementing these constraints without causing other issues within the system. Some bones are not solved and should not be constrained, adding complexity to the task."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20230812-constraint-all-bones.html#the-strategy",
-    "href": "decisions/20230812-constraint-all-bones.html#the-strategy",
-    "title": "Proposed: Constrain the entire Godot Humanoid Skeleton",
+    "objectID": "decisions/20240401-shader-graphic.html#decision-makers",
+    "href": "decisions/20240401-shader-graphic.html#decision-makers",
+    "title": "Proposed: Material Shader Graphic Shirt with Sharp Edges",
     "section": "",
-    "text": "The strategy is to carefully analyze each bone and determine the appropriate constraints. This will involve a combination of swing rotation and twist rotation constraints, depending on the specific bone."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20230812-constraint-all-bones.html#the-upside",
-    "href": "decisions/20230812-constraint-all-bones.html#the-upside",
-    "title": "Proposed: Constrain the entire Godot Humanoid Skeleton",
+    "objectID": "decisions/20240401-shader-graphic.html#tags",
+    "href": "decisions/20240401-shader-graphic.html#tags",
+    "title": "Proposed: Material Shader Graphic Shirt with Sharp Edges",
     "section": "",
-    "text": "By implementing these constraints, we can improve the functionality and reliability of the Godot humanoid skeleton system. This will allow for more realistic movements and prevent system errors when moving certain parts of the skeleton."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20230812-constraint-all-bones.html#the-downside",
-    "href": "decisions/20230812-constraint-all-bones.html#the-downside",
-    "title": "Proposed: Constrain the entire Godot Humanoid Skeleton",
+    "objectID": "decisions/20240401-shader-graphic.html#further-reading",
+    "href": "decisions/20240401-shader-graphic.html#further-reading",
+    "title": "Proposed: Material Shader Graphic Shirt with Sharp Edges",
     "section": "",
-    "text": "There may be potential challenges in implementing these constraints, particularly for the unsolved bones. It will require careful testing and adjustment to ensure that the new constraints do not introduce new issues."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20230812-constraint-all-bones.html#the-road-not-taken",
-    "href": "decisions/20230812-constraint-all-bones.html#the-road-not-taken",
-    "title": "Proposed: Constrain the entire Godot Humanoid Skeleton",
+    "objectID": "decisions/20240217-essential-typle-normalization-form.html",
+    "href": "decisions/20240217-essential-typle-normalization-form.html",
+    "title": "Proposed: Implementation of Essential Tuple Normalization Form (ETNF) for relational databases (rdbms, sql)",
     "section": "",
-    "text": "An alternative would be to leave the system as it is, accepting its limitations. However, this would mean missing out on the potential improvements that could be achieved through this proposal."
+    "text": "V-Sekai is committed to enhancing data integrity, optimizing database performance, and standardizing data storage practices. To achieve these goals, we propose the adoption of the Essential Tuple Normalization Form (ETNF) across our database systems.\n\n\n\nCurrently, V-Sekai’s database systems lack a standardized approach to normalization. This leads to data redundancy, inconsistency, and inefficiencies in data management, which can hamper system performance and scalability.\n\n\n\nWe propose implementing ETNF, a normalization form that strikes an optimal balance between eliminating redundancy and maintaining manageable complexity in database schemas. Positioned between the fourth normal form (4NF) and the fifth normal form (5NF), ETNF provides a sophisticated yet practical approach to database normalization.\n\n\nA relation schema R is in Essential Tuple Normal Form (ETNF) if every tuple in every instance of R is essential. This means that no tuple in the database can be generated from other tuples, thus eliminating redundancy.\nIn mathematical terms, a relation R is in ETNF if and only if it is in Boyce-Codd Normal Form (BCNF) and some component of every explicit join dependency (JD) of R is a superkey. Specifically, for every nontrivial join dependency {R1, R2, …, Rn} that holds over R, the intersection of each pair of Ri and Rj is a superkey for at least one of Ri or Rj.\nThis concept is further illustrated by the theorem stating that if R is a relation schema specified only by functional dependencies (FDs) and join dependencies (JDs), then R is in ETNF if and only if it is in BCNF and some component of every explicit JD of R is a superkey.\nTherefore, ETNF is an effective normalization form that reduces data redundancy while maintaining manageable complexity in database schemas. It provides a balance between the elimination of unnecessary redundancy and the avoidance of extensive decomposition associated with higher normal forms like 5NF.\n\n\nConsider a V-Sekai database table storing information about parts, suppliers, and respective shipments. The table is not normalized and contains redundant data.\n\n\n\nSupplierID\nSupplierName\nPartID\nPartName\nShipmentQuantity\n\n\n\n\nS1\nAlice\nP1\nPart1\n100\n\n\nS1\nAlice\nP2\nPart2\n200\n\n\nS2\nBob\nP1\nPart1\n150\n\n\nS2\nBob\nP3\nPart3\n300\n\n\nS3\nCharlie\nP2\nPart2\n250\n\n\n\nIn this table, SupplierName and PartName are repeated for each SupplierID and PartID, respectively. This redundancy can lead to inconsistencies and anomalies.\n\n\n\nTo normalize the above table into ETNF, we would decompose it into three separate tables: Supplier, Part, and Shipment.\n\n\n\n\n\nSupplierID\nSupplierName\n\n\n\n\nS1\nAlice\n\n\nS2\nBob\n\n\nS3\nCharlie\n\n\n\n\n\n\n\n\n\nPartID\nPartName\n\n\n\n\nP1\nPart1\n\n\nP2\nPart2\n\n\nP3\nPart3\n\n\n\n\n\n\n\n\n\nSupplierID\nPartID\nShipmentQuantity\n\n\n\n\nS1\nP1\n100\n\n\nS1\nP2\n200\n\n\nS2\nP1\n150\n\n\nS2\nP3\n300\n\n\nS3\nP2\n250\n\n\n\nIn these normalized tables, each tuple is essential and there is no redundancy. The SupplierName is not repeated for each shipment from the same supplier, and similarly, the PartName is not repeated for each shipment of the same part. This design adheres to the principles of ETNF, enhancing data integrity and consistency.\n\n\n\n\n\n\nRedundancy Reduction: ETNF effectively reduces data redundancy by ensuring that all data stored in the database is essential and non-repetitive.\nData Integrity and Consistency: By minimizing redundancy, ETNF enhances the integrity and consistency of the database, making data more reliable and accurate.\nBalanced Complexity: ETNF offers a middle ground between 4NF and 5NF, reducing redundancy without the complexity of decomposing relations into smaller, more numerous relations as often required by 5NF.\n\n\n\n\n\nDependency Analysis: The first step involves a detailed analysis of all functional and join dependencies across the database to identify redundancy and determine the scope for normalization to ETNF.\nSchema Evaluation and Restructuring: Evaluate existing database schemas against ETNF criteria, identifying areas where restructuring is required to eliminate redundancy and enhance efficiency.\nPractical Application and Migration: Implement the ETNF principles through schema redesign and careful data migration, ensuring that the transition does not impact data integrity or system availability.\n\n\n\n\n\n\nEnhanced Data Integrity: Implementation of ETNF will significantly improve the integrity and reliability of V-Sekai’s data.\nOptimized Performance: By reducing redundancy, ETNF will streamline data storage and retrieval processes, enhancing overall system performance.\nStrategic Data Management: Adopting ETNF aligns with strategic initiatives for scalable, efficient, and consistent data management practices.\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nA normal form for preventing redundant tuples in relational databases\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20230812-constraint-all-bones.html#the-infrequent-use-case",
-    "href": "decisions/20230812-constraint-all-bones.html#the-infrequent-use-case",
-    "title": "Proposed: Constrain the entire Godot Humanoid Skeleton",
+    "objectID": "decisions/20240217-essential-typle-normalization-form.html#context",
+    "href": "decisions/20240217-essential-typle-normalization-form.html#context",
+    "title": "Proposed: Implementation of Essential Tuple Normalization Form (ETNF) for relational databases (rdbms, sql)",
     "section": "",
-    "text": "In some rare cases, the lack of constraints might actually be beneficial, allowing for unusual or exaggerated movements. These cases will need to be considered and potentially addressed separately."
+    "text": "V-Sekai is committed to enhancing data integrity, optimizing database performance, and standardizing data storage practices. To achieve these goals, we propose the adoption of the Essential Tuple Normalization Form (ETNF) across our database systems."
   },
   {
-    "objectID": "decisions/20230812-constraint-all-bones.html#in-core-and-done-by-us",
-    "href": "decisions/20230812-constraint-all-bones.html#in-core-and-done-by-us",
-    "title": "Proposed: Constrain the entire Godot Humanoid Skeleton",
+    "objectID": "decisions/20240217-essential-typle-normalization-form.html#problem-statement",
+    "href": "decisions/20240217-essential-typle-normalization-form.html#problem-statement",
+    "title": "Proposed: Implementation of Essential Tuple Normalization Form (ETNF) for relational databases (rdbms, sql)",
     "section": "",
-    "text": "Yes, this change would be implemented in the core system by the V-Sekai team."
+    "text": "Currently, V-Sekai’s database systems lack a standardized approach to normalization. This leads to data redundancy, inconsistency, and inefficiencies in data management, which can hamper system performance and scalability."
   },
   {
-    "objectID": "decisions/20230812-constraint-all-bones.html#further-reading",
-    "href": "decisions/20230812-constraint-all-bones.html#further-reading",
-    "title": "Proposed: Constrain the entire Godot Humanoid Skeleton",
+    "objectID": "decisions/20240217-essential-typle-normalization-form.html#proposed-overview-etnf-implementation",
+    "href": "decisions/20240217-essential-typle-normalization-form.html#proposed-overview-etnf-implementation",
+    "title": "Proposed: Implementation of Essential Tuple Normalization Form (ETNF) for relational databases (rdbms, sql)",
     "section": "",
-    "text": "V-Sekai\nThis article is assisted by AI."
+    "text": "We propose implementing ETNF, a normalization form that strikes an optimal balance between eliminating redundancy and maintaining manageable complexity in database schemas. Positioned between the fourth normal form (4NF) and the fifth normal form (5NF), ETNF provides a sophisticated yet practical approach to database normalization.\n\n\nA relation schema R is in Essential Tuple Normal Form (ETNF) if every tuple in every instance of R is essential. This means that no tuple in the database can be generated from other tuples, thus eliminating redundancy.\nIn mathematical terms, a relation R is in ETNF if and only if it is in Boyce-Codd Normal Form (BCNF) and some component of every explicit join dependency (JD) of R is a superkey. Specifically, for every nontrivial join dependency {R1, R2, …, Rn} that holds over R, the intersection of each pair of Ri and Rj is a superkey for at least one of Ri or Rj.\nThis concept is further illustrated by the theorem stating that if R is a relation schema specified only by functional dependencies (FDs) and join dependencies (JDs), then R is in ETNF if and only if it is in BCNF and some component of every explicit JD of R is a superkey.\nTherefore, ETNF is an effective normalization form that reduces data redundancy while maintaining manageable complexity in database schemas. It provides a balance between the elimination of unnecessary redundancy and the avoidance of extensive decomposition associated with higher normal forms like 5NF.\n\n\nConsider a V-Sekai database table storing information about parts, suppliers, and respective shipments. The table is not normalized and contains redundant data.\n\n\n\nSupplierID\nSupplierName\nPartID\nPartName\nShipmentQuantity\n\n\n\n\nS1\nAlice\nP1\nPart1\n100\n\n\nS1\nAlice\nP2\nPart2\n200\n\n\nS2\nBob\nP1\nPart1\n150\n\n\nS2\nBob\nP3\nPart3\n300\n\n\nS3\nCharlie\nP2\nPart2\n250\n\n\n\nIn this table, SupplierName and PartName are repeated for each SupplierID and PartID, respectively. This redundancy can lead to inconsistencies and anomalies.\n\n\n\nTo normalize the above table into ETNF, we would decompose it into three separate tables: Supplier, Part, and Shipment.\n\n\n\n\n\nSupplierID\nSupplierName\n\n\n\n\nS1\nAlice\n\n\nS2\nBob\n\n\nS3\nCharlie\n\n\n\n\n\n\n\n\n\nPartID\nPartName\n\n\n\n\nP1\nPart1\n\n\nP2\nPart2\n\n\nP3\nPart3\n\n\n\n\n\n\n\n\n\nSupplierID\nPartID\nShipmentQuantity\n\n\n\n\nS1\nP1\n100\n\n\nS1\nP2\n200\n\n\nS2\nP1\n150\n\n\nS2\nP3\n300\n\n\nS3\nP2\n250\n\n\n\nIn these normalized tables, each tuple is essential and there is no redundancy. The SupplierName is not repeated for each shipment from the same supplier, and similarly, the PartName is not repeated for each shipment of the same part. This design adheres to the principles of ETNF, enhancing data integrity and consistency.\n\n\n\n\n\n\nRedundancy Reduction: ETNF effectively reduces data redundancy by ensuring that all data stored in the database is essential and non-repetitive.\nData Integrity and Consistency: By minimizing redundancy, ETNF enhances the integrity and consistency of the database, making data more reliable and accurate.\nBalanced Complexity: ETNF offers a middle ground between 4NF and 5NF, reducing redundancy without the complexity of decomposing relations into smaller, more numerous relations as often required by 5NF.\n\n\n\n\n\nDependency Analysis: The first step involves a detailed analysis of all functional and join dependencies across the database to identify redundancy and determine the scope for normalization to ETNF.\nSchema Evaluation and Restructuring: Evaluate existing database schemas against ETNF criteria, identifying areas where restructuring is required to eliminate redundancy and enhance efficiency.\nPractical Application and Migration: Implement the ETNF principles through schema redesign and careful data migration, ensuring that the transition does not impact data integrity or system availability."
   },
   {
-    "objectID": "decisions/20230123-player-scripting.html",
-    "href": "decisions/20230123-player-scripting.html",
-    "title": "Proposed: Provide user generated scripting using WasGO",
+    "objectID": "decisions/20240217-essential-typle-normalization-form.html#benefits-for-v-sekai",
+    "href": "decisions/20240217-essential-typle-normalization-form.html#benefits-for-v-sekai",
+    "title": "Proposed: Implementation of Essential Tuple Normalization Form (ETNF) for relational databases (rdbms, sql)",
     "section": "",
-    "text": "Proposed: Provide user generated scripting using WasGO\n\nMetadata\n\nStatus: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nContext and Problem Statement\nWe want to provide user scripting.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nWe want to be able to co simulate scripts across multiple clients without arbitrary remote code execution.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nWasGO, using dynamic call function, and Variant APIs.\n\n\nPositive Consequences\nWe can add interactivity to V-Sekai.\n\n\nNegative Consequences\nWe cannot get other features in.\n\n\nOption graveyard\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nThis adding the ability to use code.\n\n\nIs there a reason why this should be core and done by us?\nUsability is a core feature.\n\n\nReferences\n\nV-Sekai\n\n\n\nLicense of the contribution\nMIT License\n\nCopyright (c) 2018-present SaracenOne\nCopyright (c) 2019-present K. S. Ernest (iFire) Lee (fire)\nCopyright (c) 2020-present Lyuma\nCopyright (c) 2020-present MMMaellon\nCopyright (c) 2022-present See authors.md\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
+    "text": "Enhanced Data Integrity: Implementation of ETNF will significantly improve the integrity and reliability of V-Sekai’s data.\nOptimized Performance: By reducing redundancy, ETNF will streamline data storage and retrieval processes, enhancing overall system performance.\nStrategic Data Management: Adopting ETNF aligns with strategic initiatives for scalable, efficient, and consistent data management practices."
   },
   {
-    "objectID": "decisions/20211005-use-materialx-for-asset-interchange.html",
-    "href": "decisions/20211005-use-materialx-for-asset-interchange.html",
-    "title": "Proposed: Use materialx for asset interchange",
+    "objectID": "decisions/20240217-essential-typle-normalization-form.html#further-reading",
+    "href": "decisions/20240217-essential-typle-normalization-form.html#further-reading",
+    "title": "Proposed: Implementation of Essential Tuple Normalization Form (ETNF) for relational databases (rdbms, sql)",
     "section": "",
-    "text": "Proposed: Use materialx for asset interchange\n\nContext and Problem Statement\nUse #materialx for asset interchange\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nI was challenged to assemble a green IKEA chair with #materialx https://github.com/KhronosGroup/3DC-Certification/tree/main/models/GreenChair by humbletim.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n\nbake #materialx\nadd gltf2 extension\ncreate an IO/Blender\ncreate an IO/Godot\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nThis is so complicated.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nI am championing this workflow.\n\n\nReferences\n\nmaterialx.org/\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nA normal form for preventing redundant tuples in relational databases\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html",
-    "href": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html",
-    "title": "Proposed: Polish demo of V-Sekai by making invisible meshes appear via the use of the exporter.",
+    "objectID": "decisions/20231110-blender-manual-t-pose.html",
+    "href": "decisions/20231110-blender-manual-t-pose.html",
+    "title": "Accepted: Overcoming the Blender T-Pose Limitation with Documentation",
     "section": "",
-    "text": "Status: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nPolish the demo of V-Sekai\n\n\n\nWe want to validate the V-Sekai exporter addon works.\n\n\n\n\nValidate the broken V-Sekai scene exporter addon.\nExport test scene.\n\n\n\n\n\nRemove the high priority bug of the missing meshes.\n\n\n\n\n\n[e.g., compromising quality attribute, follow-up decisions required, …]\n\n[this section can be repeated for each option if more than one option is open for consideration]\n\n\n\n\nOption: Work on making the text have higher texel density.\nRejection Reason: Is time consuming and not as priority.\n\n\n\n\nThe is core V-Sekai.\n\n\n\nOnly we can set the initial scene.\n\n\n\n\nhttps://v-sekai.org/\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Status: Accepted\nDeciders: V-Sekai, fire, Lyuma, Zodiepupper, Cthulhoo\nTags: V-Sekai, VRM, Godot Engine, T-Pose, A-Pose\n\n\n\n\nThe VRM importer and specification in Godot Engine necessitates a T-Pose. However, artists often prefer using an A-Pose as it simplifies body modeling.\n\n\n\nThe issue arises when Blender VRM defaults the skeleton without adjusting the pose.\n\n\n\nHere’s a step-by-step guide to overcome this limitation:\n\nSelect all bones and create an animation pose for A-Pose. (Optional)\nClick on the mirror axis butterfly icon and the x-axis.\nAdjust the shoulder by approximately 15 degrees and position the upper arm to form a T-Pose.\nPosition the legs straight and at shoulder width apart to match the T-Pose.\nSelect all bones again and create an animation pose for T-Pose. (Optional)\n\n\n\n\nThis solution allows artists to continue using their preferred A-Pose for modeling while still meeting the T-Pose requirement of the VRM importer in Godot Engine.\n\n\n\nThe process of manually adjusting the pose from A-Pose to T-Pose can be time-consuming and may require some technical knowledge.\n\n\n\nAt this time, no other alternatives have been pursued.\n\n\n\nThis solution is primarily beneficial for artists who prefer using A-Pose for modeling but need to meet the T-Pose requirement of the VRM importer in Godot Engine.\n\n\n\nYes, this solution was developed by us.\n\n\n\n\nV-Sekai · GitHub - The official GitHub account for the V-Sekai development community, which focuses on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - The GitHub page for the V-Sekai open-source project that brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis article was assisted by AI."
   },
   {
-    "objectID": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html#context-and-problem-statement",
-    "href": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html#context-and-problem-statement",
-    "title": "Proposed: Polish demo of V-Sekai by making invisible meshes appear via the use of the exporter.",
+    "objectID": "decisions/20231110-blender-manual-t-pose.html#metadata",
+    "href": "decisions/20231110-blender-manual-t-pose.html#metadata",
+    "title": "Accepted: Overcoming the Blender T-Pose Limitation with Documentation",
     "section": "",
-    "text": "Polish the demo of V-Sekai"
+    "text": "Status: Accepted\nDeciders: V-Sekai, fire, Lyuma, Zodiepupper, Cthulhoo\nTags: V-Sekai, VRM, Godot Engine, T-Pose, A-Pose"
   },
   {
-    "objectID": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: Polish demo of V-Sekai by making invisible meshes appear via the use of the exporter.",
+    "objectID": "decisions/20231110-blender-manual-t-pose.html#context",
+    "href": "decisions/20231110-blender-manual-t-pose.html#context",
+    "title": "Accepted: Overcoming the Blender T-Pose Limitation with Documentation",
     "section": "",
-    "text": "We want to validate the V-Sekai exporter addon works."
+    "text": "The VRM importer and specification in Godot Engine necessitates a T-Pose. However, artists often prefer using an A-Pose as it simplifies body modeling."
   },
   {
-    "objectID": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Polish demo of V-Sekai by making invisible meshes appear via the use of the exporter.",
+    "objectID": "decisions/20231110-blender-manual-t-pose.html#problem",
+    "href": "decisions/20231110-blender-manual-t-pose.html#problem",
+    "title": "Accepted: Overcoming the Blender T-Pose Limitation with Documentation",
     "section": "",
-    "text": "Validate the broken V-Sekai scene exporter addon.\nExport test scene."
+    "text": "The issue arises when Blender VRM defaults the skeleton without adjusting the pose."
   },
   {
-    "objectID": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html#positive-consequences",
-    "href": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html#positive-consequences",
-    "title": "Proposed: Polish demo of V-Sekai by making invisible meshes appear via the use of the exporter.",
+    "objectID": "decisions/20231110-blender-manual-t-pose.html#solution",
+    "href": "decisions/20231110-blender-manual-t-pose.html#solution",
+    "title": "Accepted: Overcoming the Blender T-Pose Limitation with Documentation",
     "section": "",
-    "text": "Remove the high priority bug of the missing meshes."
+    "text": "Here’s a step-by-step guide to overcome this limitation:\n\nSelect all bones and create an animation pose for A-Pose. (Optional)\nClick on the mirror axis butterfly icon and the x-axis.\nAdjust the shoulder by approximately 15 degrees and position the upper arm to form a T-Pose.\nPosition the legs straight and at shoulder width apart to match the T-Pose.\nSelect all bones again and create an animation pose for T-Pose. (Optional)"
   },
   {
-    "objectID": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html#negative-consequences",
-    "href": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html#negative-consequences",
-    "title": "Proposed: Polish demo of V-Sekai by making invisible meshes appear via the use of the exporter.",
+    "objectID": "decisions/20231110-blender-manual-t-pose.html#benefits",
+    "href": "decisions/20231110-blender-manual-t-pose.html#benefits",
+    "title": "Accepted: Overcoming the Blender T-Pose Limitation with Documentation",
     "section": "",
-    "text": "[e.g., compromising quality attribute, follow-up decisions required, …]\n\n[this section can be repeated for each option if more than one option is open for consideration]"
+    "text": "This solution allows artists to continue using their preferred A-Pose for modeling while still meeting the T-Pose requirement of the VRM importer in Godot Engine."
   },
   {
-    "objectID": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html#option-graveyard",
-    "href": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html#option-graveyard",
-    "title": "Proposed: Polish demo of V-Sekai by making invisible meshes appear via the use of the exporter.",
+    "objectID": "decisions/20231110-blender-manual-t-pose.html#drawbacks",
+    "href": "decisions/20231110-blender-manual-t-pose.html#drawbacks",
+    "title": "Accepted: Overcoming the Blender T-Pose Limitation with Documentation",
     "section": "",
-    "text": "Option: Work on making the text have higher texel density.\nRejection Reason: Is time consuming and not as priority."
+    "text": "The process of manually adjusting the pose from A-Pose to T-Pose can be time-consuming and may require some technical knowledge."
   },
   {
-    "objectID": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Polish demo of V-Sekai by making invisible meshes appear via the use of the exporter.",
+    "objectID": "decisions/20231110-blender-manual-t-pose.html#alternatives-not-pursued",
+    "href": "decisions/20231110-blender-manual-t-pose.html#alternatives-not-pursued",
+    "title": "Accepted: Overcoming the Blender T-Pose Limitation with Documentation",
     "section": "",
-    "text": "The is core V-Sekai."
+    "text": "At this time, no other alternatives have been pursued."
   },
   {
-    "objectID": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Polish demo of V-Sekai by making invisible meshes appear via the use of the exporter.",
+    "objectID": "decisions/20231110-blender-manual-t-pose.html#rare-use-cases",
+    "href": "decisions/20231110-blender-manual-t-pose.html#rare-use-cases",
+    "title": "Accepted: Overcoming the Blender T-Pose Limitation with Documentation",
     "section": "",
-    "text": "Only we can set the initial scene."
+    "text": "This solution is primarily beneficial for artists who prefer using A-Pose for modeling but need to meet the T-Pose requirement of the VRM importer in Godot Engine."
   },
   {
-    "objectID": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html#references",
-    "href": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html#references",
-    "title": "Proposed: Polish demo of V-Sekai by making invisible meshes appear via the use of the exporter.",
+    "objectID": "decisions/20231110-blender-manual-t-pose.html#in-house-solution",
+    "href": "decisions/20231110-blender-manual-t-pose.html#in-house-solution",
+    "title": "Accepted: Overcoming the Blender T-Pose Limitation with Documentation",
     "section": "",
-    "text": "https://v-sekai.org/"
+    "text": "Yes, this solution was developed by us."
   },
   {
-    "objectID": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html#derivative-license",
-    "href": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html#derivative-license",
-    "title": "Proposed: Polish demo of V-Sekai by making invisible meshes appear via the use of the exporter.",
+    "objectID": "decisions/20231110-blender-manual-t-pose.html#additional-resources",
+    "href": "decisions/20231110-blender-manual-t-pose.html#additional-resources",
+    "title": "Accepted: Overcoming the Blender T-Pose Limitation with Documentation",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "V-Sekai · GitHub - The official GitHub account for the V-Sekai development community, which focuses on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - The GitHub page for the V-Sekai open-source project that brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis article was assisted by AI."
   },
   {
-    "objectID": "decisions/20230611-wasm-in-v-sekai.html",
-    "href": "decisions/20230611-wasm-in-v-sekai.html",
-    "title": "Proposed: Wasm in V-Sekai Proposal",
+    "objectID": "decisions/20240411-elixir-libgodot-bundlex.html",
+    "href": "decisions/20240411-elixir-libgodot-bundlex.html",
+    "title": "Proposed: Use Bundlex for Binding GDExtension to Elixir for Libgodot to Implement a Distributed Simulation",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai, fire\nTags: V-Sekai\n\n\n\n\nV-Sekai aims to provide a high-performance platform for virtual worlds and avatar-based social games. The current implementation relies on GDScript or C++ native modules, which may not offer the desired performance, user agency, complex calculations, graphics rendering, and algorithm execution.\n\n\n\nV-Sekai utilizes WebAssembly (Wasm) to enhance performance, offering an alternative to GDScript.\n\n\n\nCore modules: Owned by V-Sekai\nCustom modules: Owned by users\n\n\n\n\nUser-uploaded Wasm modules undergo a two-step process for safety and unauthorized access prevention:\n\nValidation: Ensure module structure and integrity adhere to security standards.\nSandboxing: Confine modules in a secure environment, restricting system resource access and mitigating potential harm.\n\n\n\n\nWasm modules facilitate advanced functions in virtual worlds and avatar-based social games, such as:\n\nEfficient character animations\nInteractive environments\nReal-time multiplayer networking\nImmersive gameplay experiences\n\n\n\n\n\nThe proposed solution uses WebAssembly (Wasm) to enhance performance and functionality in V-Sekai through User-Generated Content (UGC) Wasm modules. These modules are attached to an existing base node as a script, enabling them to provide property data and behavior for nodes in the virtual world or game.\nHere’s a concise explanation of the implementation:\n\nUser uploads a Wasm module: Custom Wasm modules with desired functionality are uploaded to V-Sekai.\nAttach Wasm module to a node: The Wasm module is attached to a node as a script, providing advanced functionality for the node.\nImplement behavior within the Variant dictionary: Node behavior is defined within script variable, enabling Wasm modules to provide both property data and behavior.\nUtilize Godot’s set_script property: Using Godot’s set_script property, Wasm modules are attached to nodes and objects, simplifying dependency handling.\nProperties after the set script: Adding properties directly onto the node after the script = property is set\n\nThis approach ensures graceful handling of missing resources while offering advanced functionality through user-uploaded Wasm modules.\n\n\n\n\nImproved performance for complex calculations, graphics rendering, and algorithm execution\nGreater user control over scripts and customization\nEnhanced functionality for virtual worlds and avatar-based social games\n\n\n\n\n\nPotential security risks with user-uploaded Wasm modules\nIncreased complexity in implementation and maintenance\nEnsuring a wasm module has no defects is difficult with or without source code.\n\n\n\n\n\nOptimizing GDScript: Improving the performance of GDScript was considered, but it would not provide the same level of performance boost as WebAssembly.\nUsing a different scripting language: Alternative scripting languages like Lua or Python were considered, but they also do not offer the desired performance improvements compared to WebAssembly.\nNative code integration: Integrating native code (C++, Rust, etc.) directly into V-Sekai was considered, but it would increase complexity and maintenance efforts. Additionally, it would not provide the same level of security and sandboxing as WebAssembly.\n\n\n\n\nNo, the enhancement aims to provide a significant performance boost and advanced functionality that cannot be achieved with a few lines of script.\n\n\n\nYes, integrating Wasm into V-Sekai’s core ensures optimal performance and seamless integration with existing systems.\n\n\n\n\nV-Sekai\nashtonmeuser/godot-wasm/issues/43\nThis article was assisted by AI.\n\n\n\n\nHere’s a glossary of definitions to help people understand the terms used in the Wasm in V-Sekai proposal:\n\nWebAssembly (Wasm): A type of code that is more portable than regular code, making games and virtual worlds work better. Originally made for the web.\nGDScript: A programming language used to make games and apps in the Godot game engine.\nC++ native modules: Pieces of code written in the C++ programming language that can be added to a game or app to make it work better.\nV-Sekai: A platform for creating virtual worlds and avatar-based social games.\nMetadata: Information about something, like who made it and what it’s for.\nValidation: Checking if something is correct and follows the rules.\nSandboxing: Putting something in a safe area where it can’t cause harm or access things it shouldn’t.\nUser-Generated Content (UGC): Things that people who use a game or app create themselves, like characters, levels, or stories.\nMissingNode: A part of the game or app that needs a script to tell it what to do.\nMissingResource: Something that a game or app needs but doesn’t have yet, like an image or sound.\nVariant: A data type in Godot that can store different kinds of information, like numbers, text, or objects. It is used to represent and manipulate data in various ways within the game engine.\nNode3D: A point in a 3D space that helps build a virtual world or game.\nGodot: A free and open-source game engine used to create games and apps.\nLua: A programming language often used in game development.\nPython: A popular programming language used for many purposes, including game development.\nRust: A programming language focused on safety and performance, often used for creating fast and reliable software."
+    "text": "The V-Sekai development team is striving to enhance the simulation experience in our VR game. We aim to create a more immersive and interactive environment for our players.\n\n\n\nWe can bind GDExtension to a C-like language for libgodot to implement a distributed simulation.\n\n\n\nInstead of godot-zig, we propose using Bundlex, a multi-platform tool for compiling C and C++ code along with Elixir projects. This will allow us to leverage the power of Elixir’s concurrency and fault-tolerance features, which are ideal for creating distributed simulations.\ndefmodule MyProject do\n  use Bundlex.Project\n\n  def project() do\n    [\n      app: :my_project,\n      compilers: [:bundlex],\n      deps: deps()\n    ]\n  end\n\n  defp deps do\n    [\n      {:bundlex, \"~&gt; 0.2\"}\n    ]\n  end\nend\n\n\n\n\nEnhanced simulation performance due to Elixir’s efficient handling of concurrent processes.\nImproved fault tolerance, as Elixir’s supervisor trees can automatically recover from errors.\nIncreased developer productivity, as Elixir’s syntax is concise and expressive.\n\n\n\n\n\nRequires learning a new programming language (Elixir), which may increase the development time initially.\nPotential compatibility issues between Elixir and existing parts of the system.\n\n\n\n\nWe considered using other languages like Rust or Go, but they did not offer the same level of concurrency and fault-tolerance features as Elixir.\n\n\n\nThis proposal may not be suitable for smaller projects that do not require complex distributed simulations.\n\n\n\nThe V-Sekai development team will implement this proposal.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nBundlex\n\nAssisted by Aria."
   },
   {
-    "objectID": "decisions/20230611-wasm-in-v-sekai.html#metadata",
-    "href": "decisions/20230611-wasm-in-v-sekai.html#metadata",
-    "title": "Proposed: Wasm in V-Sekai Proposal",
+    "objectID": "decisions/20240411-elixir-libgodot-bundlex.html#context",
+    "href": "decisions/20240411-elixir-libgodot-bundlex.html#context",
+    "title": "Proposed: Use Bundlex for Binding GDExtension to Elixir for Libgodot to Implement a Distributed Simulation",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai, fire\nTags: V-Sekai"
+    "text": "The V-Sekai development team is striving to enhance the simulation experience in our VR game. We aim to create a more immersive and interactive environment for our players."
   },
   {
-    "objectID": "decisions/20230611-wasm-in-v-sekai.html#context-and-problem-statement",
-    "href": "decisions/20230611-wasm-in-v-sekai.html#context-and-problem-statement",
-    "title": "Proposed: Wasm in V-Sekai Proposal",
+    "objectID": "decisions/20240411-elixir-libgodot-bundlex.html#problem-statement",
+    "href": "decisions/20240411-elixir-libgodot-bundlex.html#problem-statement",
+    "title": "Proposed: Use Bundlex for Binding GDExtension to Elixir for Libgodot to Implement a Distributed Simulation",
     "section": "",
-    "text": "V-Sekai aims to provide a high-performance platform for virtual worlds and avatar-based social games. The current implementation relies on GDScript or C++ native modules, which may not offer the desired performance, user agency, complex calculations, graphics rendering, and algorithm execution."
+    "text": "We can bind GDExtension to a C-like language for libgodot to implement a distributed simulation."
   },
   {
-    "objectID": "decisions/20230611-wasm-in-v-sekai.html#proposed-solution",
-    "href": "decisions/20230611-wasm-in-v-sekai.html#proposed-solution",
-    "title": "Proposed: Wasm in V-Sekai Proposal",
+    "objectID": "decisions/20240411-elixir-libgodot-bundlex.html#proposed-solution",
+    "href": "decisions/20240411-elixir-libgodot-bundlex.html#proposed-solution",
+    "title": "Proposed: Use Bundlex for Binding GDExtension to Elixir for Libgodot to Implement a Distributed Simulation",
     "section": "",
-    "text": "V-Sekai utilizes WebAssembly (Wasm) to enhance performance, offering an alternative to GDScript.\n\n\n\nCore modules: Owned by V-Sekai\nCustom modules: Owned by users\n\n\n\n\nUser-uploaded Wasm modules undergo a two-step process for safety and unauthorized access prevention:\n\nValidation: Ensure module structure and integrity adhere to security standards.\nSandboxing: Confine modules in a secure environment, restricting system resource access and mitigating potential harm.\n\n\n\n\nWasm modules facilitate advanced functions in virtual worlds and avatar-based social games, such as:\n\nEfficient character animations\nInteractive environments\nReal-time multiplayer networking\nImmersive gameplay experiences"
+    "text": "Instead of godot-zig, we propose using Bundlex, a multi-platform tool for compiling C and C++ code along with Elixir projects. This will allow us to leverage the power of Elixir’s concurrency and fault-tolerance features, which are ideal for creating distributed simulations.\ndefmodule MyProject do\n  use Bundlex.Project\n\n  def project() do\n    [\n      app: :my_project,\n      compilers: [:bundlex],\n      deps: deps()\n    ]\n  end\n\n  defp deps do\n    [\n      {:bundlex, \"~&gt; 0.2\"}\n    ]\n  end\nend"
   },
   {
-    "objectID": "decisions/20230611-wasm-in-v-sekai.html#implementation",
-    "href": "decisions/20230611-wasm-in-v-sekai.html#implementation",
-    "title": "Proposed: Wasm in V-Sekai Proposal",
+    "objectID": "decisions/20240411-elixir-libgodot-bundlex.html#benefits",
+    "href": "decisions/20240411-elixir-libgodot-bundlex.html#benefits",
+    "title": "Proposed: Use Bundlex for Binding GDExtension to Elixir for Libgodot to Implement a Distributed Simulation",
     "section": "",
-    "text": "The proposed solution uses WebAssembly (Wasm) to enhance performance and functionality in V-Sekai through User-Generated Content (UGC) Wasm modules. These modules are attached to an existing base node as a script, enabling them to provide property data and behavior for nodes in the virtual world or game.\nHere’s a concise explanation of the implementation:\n\nUser uploads a Wasm module: Custom Wasm modules with desired functionality are uploaded to V-Sekai.\nAttach Wasm module to a node: The Wasm module is attached to a node as a script, providing advanced functionality for the node.\nImplement behavior within the Variant dictionary: Node behavior is defined within script variable, enabling Wasm modules to provide both property data and behavior.\nUtilize Godot’s set_script property: Using Godot’s set_script property, Wasm modules are attached to nodes and objects, simplifying dependency handling.\nProperties after the set script: Adding properties directly onto the node after the script = property is set\n\nThis approach ensures graceful handling of missing resources while offering advanced functionality through user-uploaded Wasm modules."
+    "text": "Enhanced simulation performance due to Elixir’s efficient handling of concurrent processes.\nImproved fault tolerance, as Elixir’s supervisor trees can automatically recover from errors.\nIncreased developer productivity, as Elixir’s syntax is concise and expressive."
   },
   {
-    "objectID": "decisions/20230611-wasm-in-v-sekai.html#positive-consequences",
-    "href": "decisions/20230611-wasm-in-v-sekai.html#positive-consequences",
-    "title": "Proposed: Wasm in V-Sekai Proposal",
+    "objectID": "decisions/20240411-elixir-libgodot-bundlex.html#downsides",
+    "href": "decisions/20240411-elixir-libgodot-bundlex.html#downsides",
+    "title": "Proposed: Use Bundlex for Binding GDExtension to Elixir for Libgodot to Implement a Distributed Simulation",
     "section": "",
-    "text": "Improved performance for complex calculations, graphics rendering, and algorithm execution\nGreater user control over scripts and customization\nEnhanced functionality for virtual worlds and avatar-based social games"
+    "text": "Requires learning a new programming language (Elixir), which may increase the development time initially.\nPotential compatibility issues between Elixir and existing parts of the system."
   },
   {
-    "objectID": "decisions/20230611-wasm-in-v-sekai.html#negative-consequences",
-    "href": "decisions/20230611-wasm-in-v-sekai.html#negative-consequences",
-    "title": "Proposed: Wasm in V-Sekai Proposal",
+    "objectID": "decisions/20240411-elixir-libgodot-bundlex.html#alternatives-considered",
+    "href": "decisions/20240411-elixir-libgodot-bundlex.html#alternatives-considered",
+    "title": "Proposed: Use Bundlex for Binding GDExtension to Elixir for Libgodot to Implement a Distributed Simulation",
     "section": "",
-    "text": "Potential security risks with user-uploaded Wasm modules\nIncreased complexity in implementation and maintenance\nEnsuring a wasm module has no defects is difficult with or without source code."
+    "text": "We considered using other languages like Rust or Go, but they did not offer the same level of concurrency and fault-tolerance features as Elixir."
   },
   {
-    "objectID": "decisions/20230611-wasm-in-v-sekai.html#option-graveyard",
-    "href": "decisions/20230611-wasm-in-v-sekai.html#option-graveyard",
-    "title": "Proposed: Wasm in V-Sekai Proposal",
+    "objectID": "decisions/20240411-elixir-libgodot-bundlex.html#infrequent-use-case",
+    "href": "decisions/20240411-elixir-libgodot-bundlex.html#infrequent-use-case",
+    "title": "Proposed: Use Bundlex for Binding GDExtension to Elixir for Libgodot to Implement a Distributed Simulation",
     "section": "",
-    "text": "Optimizing GDScript: Improving the performance of GDScript was considered, but it would not provide the same level of performance boost as WebAssembly.\nUsing a different scripting language: Alternative scripting languages like Lua or Python were considered, but they also do not offer the desired performance improvements compared to WebAssembly.\nNative code integration: Integrating native code (C++, Rust, etc.) directly into V-Sekai was considered, but it would increase complexity and maintenance efforts. Additionally, it would not provide the same level of security and sandboxing as WebAssembly."
+    "text": "This proposal may not be suitable for smaller projects that do not require complex distributed simulations."
   },
   {
-    "objectID": "decisions/20230611-wasm-in-v-sekai.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230611-wasm-in-v-sekai.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Wasm in V-Sekai Proposal",
+    "objectID": "decisions/20240411-elixir-libgodot-bundlex.html#implementation",
+    "href": "decisions/20240411-elixir-libgodot-bundlex.html#implementation",
+    "title": "Proposed: Use Bundlex for Binding GDExtension to Elixir for Libgodot to Implement a Distributed Simulation",
     "section": "",
-    "text": "No, the enhancement aims to provide a significant performance boost and advanced functionality that cannot be achieved with a few lines of script."
+    "text": "The V-Sekai development team will implement this proposal."
   },
   {
-    "objectID": "decisions/20230611-wasm-in-v-sekai.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230611-wasm-in-v-sekai.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Wasm in V-Sekai Proposal",
+    "objectID": "decisions/20240411-elixir-libgodot-bundlex.html#status",
+    "href": "decisions/20240411-elixir-libgodot-bundlex.html#status",
+    "title": "Proposed: Use Bundlex for Binding GDExtension to Elixir for Libgodot to Implement a Distributed Simulation",
     "section": "",
-    "text": "Yes, integrating Wasm into V-Sekai’s core ensures optimal performance and seamless integration with existing systems."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20230611-wasm-in-v-sekai.html#references",
-    "href": "decisions/20230611-wasm-in-v-sekai.html#references",
-    "title": "Proposed: Wasm in V-Sekai Proposal",
+    "objectID": "decisions/20240411-elixir-libgodot-bundlex.html#decision-makers",
+    "href": "decisions/20240411-elixir-libgodot-bundlex.html#decision-makers",
+    "title": "Proposed: Use Bundlex for Binding GDExtension to Elixir for Libgodot to Implement a Distributed Simulation",
     "section": "",
-    "text": "V-Sekai\nashtonmeuser/godot-wasm/issues/43\nThis article was assisted by AI."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20230611-wasm-in-v-sekai.html#glossary",
-    "href": "decisions/20230611-wasm-in-v-sekai.html#glossary",
-    "title": "Proposed: Wasm in V-Sekai Proposal",
+    "objectID": "decisions/20240411-elixir-libgodot-bundlex.html#tags",
+    "href": "decisions/20240411-elixir-libgodot-bundlex.html#tags",
+    "title": "Proposed: Use Bundlex for Binding GDExtension to Elixir for Libgodot to Implement a Distributed Simulation",
     "section": "",
-    "text": "Here’s a glossary of definitions to help people understand the terms used in the Wasm in V-Sekai proposal:\n\nWebAssembly (Wasm): A type of code that is more portable than regular code, making games and virtual worlds work better. Originally made for the web.\nGDScript: A programming language used to make games and apps in the Godot game engine.\nC++ native modules: Pieces of code written in the C++ programming language that can be added to a game or app to make it work better.\nV-Sekai: A platform for creating virtual worlds and avatar-based social games.\nMetadata: Information about something, like who made it and what it’s for.\nValidation: Checking if something is correct and follows the rules.\nSandboxing: Putting something in a safe area where it can’t cause harm or access things it shouldn’t.\nUser-Generated Content (UGC): Things that people who use a game or app create themselves, like characters, levels, or stories.\nMissingNode: A part of the game or app that needs a script to tell it what to do.\nMissingResource: Something that a game or app needs but doesn’t have yet, like an image or sound.\nVariant: A data type in Godot that can store different kinds of information, like numbers, text, or objects. It is used to represent and manipulate data in various ways within the game engine.\nNode3D: A point in a 3D space that helps build a virtual world or game.\nGodot: A free and open-source game engine used to create games and apps.\nLua: A programming language often used in game development.\nPython: A popular programming language used for many purposes, including game development.\nRust: A programming language focused on safety and performance, often used for creating fast and reliable software."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20220317-protect-minumum-spec-steam-deck.html",
-    "href": "decisions/20220317-protect-minumum-spec-steam-deck.html",
-    "title": "Proposed: To protect the minimum spec maintain steam deck version of flatmode V-Sekai",
+    "objectID": "decisions/20240411-elixir-libgodot-bundlex.html#further-reading",
+    "href": "decisions/20240411-elixir-libgodot-bundlex.html#further-reading",
+    "title": "Proposed: Use Bundlex for Binding GDExtension to Elixir for Libgodot to Implement a Distributed Simulation",
     "section": "",
-    "text": "Proposed: To protect the minimum spec maintain steam deck version of flatmode V-Sekai\n\nDescribe the status of the issue.\nproposed\n\n\nList the deciders of the issue.\nV-Sekai,fire,\n\n\nDescribe the tags of the issue.\nV-Sekai,\n\n\nContext and Problem Statement\nProvide a restricted environment that can limit our art, compute, storage budget.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nPropose to use the steam deck as the minimum platform for V-Sekai flat mode.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nMust hit the screen refresh rate or more.\n\n\nPositive Consequences\n\nConstrained system provide better tests and code.\n\n\n\nNegative Consequences\n\nFlatmode is not the main design of V-Sekai\n\n\n\nOption graveyard\nNo response\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\n\nThis is a complex integration test. Not a few lines of script.\n\n\n\nIs there a reason why this should be core and done by us?\nSetting minimum requirements is a core feature.\n\n\nReferences\n\nV-Sekai\n\n\n\nLicense of the contribution\nCopyright (c) 2022 V-Sekai contributors. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nBundlex\n\nAssisted by Aria."
   },
   {
-    "objectID": "decisions/20240810-steamvr-dongles-separate.html",
-    "href": "decisions/20240810-steamvr-dongles-separate.html",
-    "title": "Proposed: Improving Connectivity for Valve StreamVR Light House Dongles",
+    "objectID": "decisions/20240324-v-sekai-as-slc.html",
+    "href": "decisions/20240324-v-sekai-as-slc.html",
+    "title": "Proposed: V-Sekai Implementation Using SLC Framework",
     "section": "",
-    "text": "Valve StreamVR Light House Dongles are unable to connect.\n\n\n\nValve StreamVR Light House Dongles are unable to connect because of wireless interference if plugged into hubs upright and side by side.\n\n\n\nUse the supplied HTCVive cradles for the dongles. Keep the dongles upright.\n\n\n\n\nReduced Interference: By using the supplied cradles and keeping the dongles upright, wireless interference is minimized.\nImproved Connectivity: Ensures stable and reliable connections for the Valve StreamVR Light House Dongles.\nUser-Friendly: Simple implementation that leverages existing hardware (HTCVive cradles).\n\n\n\n\n\nAdditional Space Required: Using cradles may require more physical space compared to plugging dongles directly into a hub.\nPotential Cost: If users do not already have the HTCVive cradles, they may need to purchase them separately.\n\n\n\n\n\nAlternative Positioning: Exploring other physical arrangements for the dongles without using cradles.\nSoftware Solutions: Investigating software-based solutions to mitigate wireless interference.\n\n\n\n\n\nLimited Setup Scenarios: Users with unique setups where space constraints make it difficult to use the cradles effectively.\n\n\n\n\n\nImplementation: The V-Sekai development team will handle the implementation and testing of this proposal.\nDocumentation: Detailed instructions and guidelines will be provided to users for setting up their dongles using the cradles.\n\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "VR gaming requires a seamless, inviting experience. A VR dating game can utilize simplicity, engagement, and completeness principles.\n\n\n\nThe challenge is creating an intuitive, engaging VR dating game with a comprehensive feature set from the start.\n\n\n\nUsing the SLC framework—Simple, Lovable, Complete—the project should:\n\nSimple: Emphasize user-friendly design and easy navigation.\nfunction interact_with_object(object):\n    if object.is_interactable:\n        show_prompt(\"Press X to interact\")\n        wait_for_input()\n        execute_interaction()\nLovable: Develop appealing characters and environments.\nCharacter customization concept art\nComplete: Launch with diverse scenarios and detailed character interactions.\nlaunch_features:\n  - CompleteCharacterCustomization\n  - DiverseScenarios\n  - InDepthCharacterInteractions\n  - RealTimeChat\n\n\n\n\nThis approach ensures an accessible, captivating product without immediate expansion need, catering to a wide audience.\n\n\n\nAn extensive initial development phase may delay release, and simplicity could limit advanced functionalities.\n\n\n\nA leaner initial version might allow earlier release but risk losing early adopters.\n\n\n\nDesign a user-friendly re-engagement process for returning users.\n\n\n\nFocus on essential launch features, expand based on user feedback.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai GitHub Repository\nV-Sekai Game Project\n\nAssistance provided by AI assistant Aria."
   },
   {
-    "objectID": "decisions/20240810-steamvr-dongles-separate.html#the-context",
-    "href": "decisions/20240810-steamvr-dongles-separate.html#the-context",
-    "title": "Proposed: Improving Connectivity for Valve StreamVR Light House Dongles",
+    "objectID": "decisions/20240324-v-sekai-as-slc.html#context",
+    "href": "decisions/20240324-v-sekai-as-slc.html#context",
+    "title": "Proposed: V-Sekai Implementation Using SLC Framework",
     "section": "",
-    "text": "Valve StreamVR Light House Dongles are unable to connect."
+    "text": "VR gaming requires a seamless, inviting experience. A VR dating game can utilize simplicity, engagement, and completeness principles."
   },
   {
-    "objectID": "decisions/20240810-steamvr-dongles-separate.html#the-problem-statement",
-    "href": "decisions/20240810-steamvr-dongles-separate.html#the-problem-statement",
-    "title": "Proposed: Improving Connectivity for Valve StreamVR Light House Dongles",
+    "objectID": "decisions/20240324-v-sekai-as-slc.html#problem",
+    "href": "decisions/20240324-v-sekai-as-slc.html#problem",
+    "title": "Proposed: V-Sekai Implementation Using SLC Framework",
     "section": "",
-    "text": "Valve StreamVR Light House Dongles are unable to connect because of wireless interference if plugged into hubs upright and side by side."
+    "text": "The challenge is creating an intuitive, engaging VR dating game with a comprehensive feature set from the start."
   },
   {
-    "objectID": "decisions/20240810-steamvr-dongles-separate.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240810-steamvr-dongles-separate.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Improving Connectivity for Valve StreamVR Light House Dongles",
+    "objectID": "decisions/20240324-v-sekai-as-slc.html#proposal",
+    "href": "decisions/20240324-v-sekai-as-slc.html#proposal",
+    "title": "Proposed: V-Sekai Implementation Using SLC Framework",
     "section": "",
-    "text": "Use the supplied HTCVive cradles for the dongles. Keep the dongles upright."
+    "text": "Using the SLC framework—Simple, Lovable, Complete—the project should:\n\nSimple: Emphasize user-friendly design and easy navigation.\nfunction interact_with_object(object):\n    if object.is_interactable:\n        show_prompt(\"Press X to interact\")\n        wait_for_input()\n        execute_interaction()\nLovable: Develop appealing characters and environments.\nCharacter customization concept art\nComplete: Launch with diverse scenarios and detailed character interactions.\nlaunch_features:\n  - CompleteCharacterCustomization\n  - DiverseScenarios\n  - InDepthCharacterInteractions\n  - RealTimeChat"
   },
   {
-    "objectID": "decisions/20240810-steamvr-dongles-separate.html#the-benefits",
-    "href": "decisions/20240810-steamvr-dongles-separate.html#the-benefits",
-    "title": "Proposed: Improving Connectivity for Valve StreamVR Light House Dongles",
+    "objectID": "decisions/20240324-v-sekai-as-slc.html#benefits",
+    "href": "decisions/20240324-v-sekai-as-slc.html#benefits",
+    "title": "Proposed: V-Sekai Implementation Using SLC Framework",
     "section": "",
-    "text": "Reduced Interference: By using the supplied cradles and keeping the dongles upright, wireless interference is minimized.\nImproved Connectivity: Ensures stable and reliable connections for the Valve StreamVR Light House Dongles.\nUser-Friendly: Simple implementation that leverages existing hardware (HTCVive cradles)."
+    "text": "This approach ensures an accessible, captivating product without immediate expansion need, catering to a wide audience."
   },
   {
-    "objectID": "decisions/20240810-steamvr-dongles-separate.html#the-downsides",
-    "href": "decisions/20240810-steamvr-dongles-separate.html#the-downsides",
-    "title": "Proposed: Improving Connectivity for Valve StreamVR Light House Dongles",
+    "objectID": "decisions/20240324-v-sekai-as-slc.html#downsides",
+    "href": "decisions/20240324-v-sekai-as-slc.html#downsides",
+    "title": "Proposed: V-Sekai Implementation Using SLC Framework",
     "section": "",
-    "text": "Additional Space Required: Using cradles may require more physical space compared to plugging dongles directly into a hub.\nPotential Cost: If users do not already have the HTCVive cradles, they may need to purchase them separately."
+    "text": "An extensive initial development phase may delay release, and simplicity could limit advanced functionalities."
   },
   {
-    "objectID": "decisions/20240810-steamvr-dongles-separate.html#the-road-not-taken",
-    "href": "decisions/20240810-steamvr-dongles-separate.html#the-road-not-taken",
-    "title": "Proposed: Improving Connectivity for Valve StreamVR Light House Dongles",
+    "objectID": "decisions/20240324-v-sekai-as-slc.html#alternate-approach",
+    "href": "decisions/20240324-v-sekai-as-slc.html#alternate-approach",
+    "title": "Proposed: V-Sekai Implementation Using SLC Framework",
     "section": "",
-    "text": "Alternative Positioning: Exploring other physical arrangements for the dongles without using cradles.\nSoftware Solutions: Investigating software-based solutions to mitigate wireless interference."
+    "text": "A leaner initial version might allow earlier release but risk losing early adopters."
   },
   {
-    "objectID": "decisions/20240810-steamvr-dongles-separate.html#the-infrequent-use-case",
-    "href": "decisions/20240810-steamvr-dongles-separate.html#the-infrequent-use-case",
-    "title": "Proposed: Improving Connectivity for Valve StreamVR Light House Dongles",
+    "objectID": "decisions/20240324-v-sekai-as-slc.html#infrequent-users-consideration",
+    "href": "decisions/20240324-v-sekai-as-slc.html#infrequent-users-consideration",
+    "title": "Proposed: V-Sekai Implementation Using SLC Framework",
     "section": "",
-    "text": "Limited Setup Scenarios: Users with unique setups where space constraints make it difficult to use the cradles effectively."
+    "text": "Design a user-friendly re-engagement process for returning users."
   },
   {
-    "objectID": "decisions/20240810-steamvr-dongles-separate.html#in-core-and-done-by-us",
-    "href": "decisions/20240810-steamvr-dongles-separate.html#in-core-and-done-by-us",
-    "title": "Proposed: Improving Connectivity for Valve StreamVR Light House Dongles",
+    "objectID": "decisions/20240324-v-sekai-as-slc.html#development-philosophy",
+    "href": "decisions/20240324-v-sekai-as-slc.html#development-philosophy",
+    "title": "Proposed: V-Sekai Implementation Using SLC Framework",
     "section": "",
-    "text": "Implementation: The V-Sekai development team will handle the implementation and testing of this proposal.\nDocumentation: Detailed instructions and guidelines will be provided to users for setting up their dongles using the cradles."
+    "text": "Focus on essential launch features, expand based on user feedback."
   },
   {
-    "objectID": "decisions/20240810-steamvr-dongles-separate.html#status",
-    "href": "decisions/20240810-steamvr-dongles-separate.html#status",
-    "title": "Proposed: Improving Connectivity for Valve StreamVR Light House Dongles",
+    "objectID": "decisions/20240324-v-sekai-as-slc.html#status",
+    "href": "decisions/20240324-v-sekai-as-slc.html#status",
+    "title": "Proposed: V-Sekai Implementation Using SLC Framework",
     "section": "",
     "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20240810-steamvr-dongles-separate.html#decision-makers",
-    "href": "decisions/20240810-steamvr-dongles-separate.html#decision-makers",
-    "title": "Proposed: Improving Connectivity for Valve StreamVR Light House Dongles",
+    "objectID": "decisions/20240324-v-sekai-as-slc.html#decision-makers",
+    "href": "decisions/20240324-v-sekai-as-slc.html#decision-makers",
+    "title": "Proposed: V-Sekai Implementation Using SLC Framework",
     "section": "",
     "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20240810-steamvr-dongles-separate.html#tags",
-    "href": "decisions/20240810-steamvr-dongles-separate.html#tags",
-    "title": "Proposed: Improving Connectivity for Valve StreamVR Light House Dongles",
+    "objectID": "decisions/20240324-v-sekai-as-slc.html#tags",
+    "href": "decisions/20240324-v-sekai-as-slc.html#tags",
+    "title": "Proposed: V-Sekai Implementation Using SLC Framework",
     "section": "",
     "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20240810-steamvr-dongles-separate.html#further-reading",
-    "href": "decisions/20240810-steamvr-dongles-separate.html#further-reading",
-    "title": "Proposed: Improving Connectivity for Valve StreamVR Light House Dongles",
+    "objectID": "decisions/20240324-v-sekai-as-slc.html#further-reading",
+    "href": "decisions/20240324-v-sekai-as-slc.html#further-reading",
+    "title": "Proposed: V-Sekai Implementation Using SLC Framework",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "V-Sekai GitHub Repository\nV-Sekai Game Project\n\nAssistance provided by AI assistant Aria."
   },
   {
-    "objectID": "decisions/20220228-v-sekai-version-three-plan.html",
-    "href": "decisions/20220228-v-sekai-version-three-plan.html",
-    "title": "Accepted: Planning V-Sekai Version 3 on 2022-02-28",
+    "objectID": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html",
+    "href": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html",
+    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Kinoite and #steam",
     "section": "",
-    "text": "Status: accepted \nDeciders: V-Sekai,ifire,lyuma,\nTags: V-Sekai,\n\n\n\nKnow where we’re going by describing what we want.\n\n\n\nProposed mission and a list of tasks.\n\n\n\n\n\n\nGodot Engine pull requests.\n\n\n\n\n\nImprove making and using avatar and map content enhancement\nAble to have our group of people join and communicate (godot speech) enhancement\nRestore VR support (openxr) in V-Sekai enhancement\nTest easier with desktop interaction with objects enhancement\nInteract with objects in vr enhancement\nImport a CCBY, CC0 MMD stage for testing dance stages enhancement\nProvide user generated scripting using WasGo enhancement\n\n\n\n\n\nGain clarity of mission.\n\n\n\n\nThe cost of overhead.\n\n\n\n\n\nOption: Status quo. \nRejection Reason: Complete the wrong thing. \n\n\n\n\nThis is a planning document.\n\n\n\nWe know what we want to do.\n\n\n\n\nNone\n\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Status: rejected \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nI don’t have a #steam Deck since it was delayed til February 2022 to test V-Sekai.\n\n\n\nInstall Fedora Kinoite and Steam.\n\n\n\n\nInstall Ventoy on a USB Stick\nInstall iso of Fedora Kinoite onto the drive on Ventoy\nInstall Fedora Kinoite onto hardware proxy defined in another proposal.\nInstall #steam via RPMFusion\n\n\n\n\n\nAble to test builds from Windows?\n\n\n\n\n\nUnknown\n\n\n\n\n\nOption: Use Arch Manjaor\nRejection Reason: Unfamiliar with OS.\n\n\n\n\nNot lines of code.\n\n\n\nQA testing needs to be inhouse.\n\n\n\n\nhttps://en.wikipedia.org/wiki/Steam_Deck\nhttps://download.fedoraproject.org/pub/fedora/linux/releases/35/Kinoite/x86_64/iso/Fedora-Kinoite-ostree-x86_64-35-1.2.iso\n\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20220228-v-sekai-version-three-plan.html#context-and-problem-statement",
-    "href": "decisions/20220228-v-sekai-version-three-plan.html#context-and-problem-statement",
-    "title": "Accepted: Planning V-Sekai Version 3 on 2022-02-28",
+    "objectID": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html#context-and-problem-statement",
+    "href": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html#context-and-problem-statement",
+    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Kinoite and #steam",
     "section": "",
-    "text": "Know where we’re going by describing what we want."
+    "text": "I don’t have a #steam Deck since it was delayed til February 2022 to test V-Sekai."
   },
   {
-    "objectID": "decisions/20220228-v-sekai-version-three-plan.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20220228-v-sekai-version-three-plan.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Accepted: Planning V-Sekai Version 3 on 2022-02-28",
+    "objectID": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Kinoite and #steam",
+    "section": "",
+    "text": "Install Fedora Kinoite and Steam."
+  },
+  {
+    "objectID": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Kinoite and #steam",
     "section": "",
-    "text": "Proposed mission and a list of tasks."
+    "text": "Install Ventoy on a USB Stick\nInstall iso of Fedora Kinoite onto the drive on Ventoy\nInstall Fedora Kinoite onto hardware proxy defined in another proposal.\nInstall #steam via RPMFusion"
   },
   {
-    "objectID": "decisions/20220228-v-sekai-version-three-plan.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20220228-v-sekai-version-three-plan.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Accepted: Planning V-Sekai Version 3 on 2022-02-28",
+    "objectID": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html#positive-consequences",
+    "href": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html#positive-consequences",
+    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Kinoite and #steam",
     "section": "",
-    "text": "Godot Engine pull requests.\n\n\n\n\n\nImprove making and using avatar and map content enhancement\nAble to have our group of people join and communicate (godot speech) enhancement\nRestore VR support (openxr) in V-Sekai enhancement\nTest easier with desktop interaction with objects enhancement\nInteract with objects in vr enhancement\nImport a CCBY, CC0 MMD stage for testing dance stages enhancement\nProvide user generated scripting using WasGo enhancement"
+    "text": "Able to test builds from Windows?"
   },
   {
-    "objectID": "decisions/20220228-v-sekai-version-three-plan.html#positive-consequences",
-    "href": "decisions/20220228-v-sekai-version-three-plan.html#positive-consequences",
-    "title": "Accepted: Planning V-Sekai Version 3 on 2022-02-28",
+    "objectID": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html#negative-consequences",
+    "href": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html#negative-consequences",
+    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Kinoite and #steam",
     "section": "",
-    "text": "Gain clarity of mission."
+    "text": "Unknown"
   },
   {
-    "objectID": "decisions/20220228-v-sekai-version-three-plan.html#negative-consequences",
-    "href": "decisions/20220228-v-sekai-version-three-plan.html#negative-consequences",
-    "title": "Accepted: Planning V-Sekai Version 3 on 2022-02-28",
+    "objectID": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html#option-graveyard",
+    "href": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html#option-graveyard",
+    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Kinoite and #steam",
     "section": "",
-    "text": "The cost of overhead."
+    "text": "Option: Use Arch Manjaor\nRejection Reason: Unfamiliar with OS."
   },
   {
-    "objectID": "decisions/20220228-v-sekai-version-three-plan.html#option-graveyard",
-    "href": "decisions/20220228-v-sekai-version-three-plan.html#option-graveyard",
-    "title": "Accepted: Planning V-Sekai Version 3 on 2022-02-28",
+    "objectID": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Kinoite and #steam",
     "section": "",
-    "text": "Option: Status quo. \nRejection Reason: Complete the wrong thing."
+    "text": "Not lines of code."
   },
   {
-    "objectID": "decisions/20220228-v-sekai-version-three-plan.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20220228-v-sekai-version-three-plan.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Accepted: Planning V-Sekai Version 3 on 2022-02-28",
+    "objectID": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Kinoite and #steam",
     "section": "",
-    "text": "This is a planning document."
+    "text": "QA testing needs to be inhouse."
   },
   {
-    "objectID": "decisions/20220228-v-sekai-version-three-plan.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20220228-v-sekai-version-three-plan.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Accepted: Planning V-Sekai Version 3 on 2022-02-28",
+    "objectID": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html#references",
+    "href": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html#references",
+    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Kinoite and #steam",
     "section": "",
-    "text": "We know what we want to do."
+    "text": "https://en.wikipedia.org/wiki/Steam_Deck\nhttps://download.fedoraproject.org/pub/fedora/linux/releases/35/Kinoite/x86_64/iso/Fedora-Kinoite-ostree-x86_64-35-1.2.iso"
   },
   {
-    "objectID": "decisions/20220228-v-sekai-version-three-plan.html#references",
-    "href": "decisions/20220228-v-sekai-version-three-plan.html#references",
-    "title": "Accepted: Planning V-Sekai Version 3 on 2022-02-28",
+    "objectID": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html#derivative-license",
+    "href": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html#derivative-license",
+    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Kinoite and #steam",
     "section": "",
-    "text": "None"
+    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20220228-v-sekai-version-three-plan.html#derivative-license",
-    "href": "decisions/20220228-v-sekai-version-three-plan.html#derivative-license",
-    "title": "Accepted: Planning V-Sekai Version 3 on 2022-02-28",
+    "objectID": "decisions/20220820-cloth-sim.html",
+    "href": "decisions/20220820-cloth-sim.html",
+    "title": "Proposed: Simulate cloth on characters",
     "section": "",
-    "text": "Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Proposed: Simulate cloth on characters\nLabels: enhancement\n\nContext and Problem Statement\nWe want to simulate clothing on characters without wardrobe malfunction.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nUse opensource tooling to accomplish this.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nRun conditioner on inputs. https://github.com/fire/preconditioner-for-cloth-and-deformable-body-simulation\n\n\nPositive Consequences\nCan have clothing.\n\n\nNegative Consequences\nCan have clothing.\n\n\nOption graveyard\nNo response\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot trivial.\n\n\nIs there a reason why this should be core and done by us?\nTrying out a test.\n\n\nReferences\n\nV-Sekai\n\n\n\nLicense of the contribution\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240423-building-metaverse-with-glue-mechanic.html",
-    "href": "decisions/20240423-building-metaverse-with-glue-mechanic.html",
-    "title": "Accepted: Building a Metaverse with Glue Mechanic in V-Sekai",
+    "objectID": "decisions/20231110-efficient-llm-training.html",
+    "href": "decisions/20231110-efficient-llm-training.html",
+    "title": "Proposed: Efficient Training of LLMs in V-Sekai",
     "section": "",
-    "text": "V-Sekai is an open-source project that brings social VR/VRSNS/metaverse components to the Godot Engine. The current focus of the project is on avatar movement and interaction within a confined space.\n\n\n\nThe current model of V-Sekai, while functional, seems limited in its scope. It primarily focuses on avatars moving in a room, which restricts the potential for expansive world-building and exploration.\n\n\n\nThe proposed solution is to introduce a “glue mechanic” into the system. This mechanic would allow users to build their own vehicles and structures by gluing different elements together. This could potentially open up the possibility for creating entire universes within the metaverse.\nThis idea was inspired by a game called “Crazy Contraptions” developed by Mantafloof during the Ludum Dare 55 game jam. The game was created in just 48 hours and successfully implemented the glue mechanic concept.\nUsers can combine different elements (represented here as ‘blocks’ and ‘wheels’) to create new structures or vehicles.\n\n\n\n\nEncourages creativity and innovation among users.\nOpens up possibilities for expansive world-building and exploration.\nProvides a reason to work on LODs and memory management for loading worlds.\n\n\n\n\n\nMay require significant changes to the existing codebase.\nThis could potentially increase the complexity of the system.\n\n\n\n\nAn alternative approach could be to continue focusing on avatar movement and interaction within a confined space. However, this may limit the potential for expansive world-building and exploration.\n\n\n\nIn cases where users prefer a more confined and controlled environment, the glue mechanic may not be as appealing. However, it could still provide an interesting option for those looking to experiment with world-building.\n\n\n\nThe implementation of the glue mechanic would be done by the V-Sekai development team.\n\n\n\nStatus: Accepted\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, LLM, Training\n\n\n\n\nGiven the limited resources available to V-Sekai, it is crucial to optimize the training time for Language Learning Models (LLMs) like Aria assistant.\n\n\n\nThe challenge lies in efficiently training these models within a constrained timeframe - ideally not exceeding one day.\n\n\n\nTo expedite the training process, we propose the following adjustments to Ludwig:\n\nSet trainable=false to make training over 50x faster.\nEnable Automatic Mixed Precision (AMP) training, which is available when both trainable=true and trainable=false.\nImplement approximate training set evaluation (evaluate_training_set=false). This computes the reported training set metrics at the end of each epoch as a running aggregation of the metrics during training, rather than a separate pass over the training set at the end of each epoch of training. Although this may result in “noisy” metrics in the early epochs, it generally leads to a 33% speedup in training time.\n\n\n\n\nPros:\n\nSignificantly reduces training time.\nAllows for more efficient use of resources.\n\nCons:\n\nEarly training metrics may appear “noisy”.\n\n\n\n\nThis section will be updated with potential alternatives if the proposed solution does not yield the expected results.\n\n\n\nThis section will be updated with infrequent use cases that may arise during the implementation of the proposed solution.\n\n\n\nIs this solution core to our operations and will it be implemented by us? This section will be updated accordingly.\n\n\n\n\nV-Sekai · GitHub\nV-Sekai/v-sekai-game\nLLM Classification - Ludwig\n\nThis proposal was assisted by Aria, an AI assistant."
   },
   {
-    "objectID": "decisions/20240423-building-metaverse-with-glue-mechanic.html#the-context",
-    "href": "decisions/20240423-building-metaverse-with-glue-mechanic.html#the-context",
-    "title": "Accepted: Building a Metaverse with Glue Mechanic in V-Sekai",
+    "objectID": "decisions/20231110-efficient-llm-training.html#metadata",
+    "href": "decisions/20231110-efficient-llm-training.html#metadata",
+    "title": "Proposed: Efficient Training of LLMs in V-Sekai",
     "section": "",
-    "text": "V-Sekai is an open-source project that brings social VR/VRSNS/metaverse components to the Godot Engine. The current focus of the project is on avatar movement and interaction within a confined space."
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, LLM, Training"
   },
   {
-    "objectID": "decisions/20240423-building-metaverse-with-glue-mechanic.html#the-problem-statement",
-    "href": "decisions/20240423-building-metaverse-with-glue-mechanic.html#the-problem-statement",
-    "title": "Accepted: Building a Metaverse with Glue Mechanic in V-Sekai",
+    "objectID": "decisions/20231110-efficient-llm-training.html#context",
+    "href": "decisions/20231110-efficient-llm-training.html#context",
+    "title": "Proposed: Efficient Training of LLMs in V-Sekai",
     "section": "",
-    "text": "The current model of V-Sekai, while functional, seems limited in its scope. It primarily focuses on avatars moving in a room, which restricts the potential for expansive world-building and exploration."
+    "text": "Given the limited resources available to V-Sekai, it is crucial to optimize the training time for Language Learning Models (LLMs) like Aria assistant."
   },
   {
-    "objectID": "decisions/20240423-building-metaverse-with-glue-mechanic.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240423-building-metaverse-with-glue-mechanic.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Accepted: Building a Metaverse with Glue Mechanic in V-Sekai",
+    "objectID": "decisions/20231110-efficient-llm-training.html#problem",
+    "href": "decisions/20231110-efficient-llm-training.html#problem",
+    "title": "Proposed: Efficient Training of LLMs in V-Sekai",
     "section": "",
-    "text": "The proposed solution is to introduce a “glue mechanic” into the system. This mechanic would allow users to build their own vehicles and structures by gluing different elements together. This could potentially open up the possibility for creating entire universes within the metaverse.\nThis idea was inspired by a game called “Crazy Contraptions” developed by Mantafloof during the Ludum Dare 55 game jam. The game was created in just 48 hours and successfully implemented the glue mechanic concept.\nUsers can combine different elements (represented here as ‘blocks’ and ‘wheels’) to create new structures or vehicles."
+    "text": "The challenge lies in efficiently training these models within a constrained timeframe - ideally not exceeding one day."
   },
   {
-    "objectID": "decisions/20240423-building-metaverse-with-glue-mechanic.html#the-benefits",
-    "href": "decisions/20240423-building-metaverse-with-glue-mechanic.html#the-benefits",
-    "title": "Accepted: Building a Metaverse with Glue Mechanic in V-Sekai",
+    "objectID": "decisions/20231110-efficient-llm-training.html#solution",
+    "href": "decisions/20231110-efficient-llm-training.html#solution",
+    "title": "Proposed: Efficient Training of LLMs in V-Sekai",
     "section": "",
-    "text": "Encourages creativity and innovation among users.\nOpens up possibilities for expansive world-building and exploration.\nProvides a reason to work on LODs and memory management for loading worlds."
+    "text": "To expedite the training process, we propose the following adjustments to Ludwig:\n\nSet trainable=false to make training over 50x faster.\nEnable Automatic Mixed Precision (AMP) training, which is available when both trainable=true and trainable=false.\nImplement approximate training set evaluation (evaluate_training_set=false). This computes the reported training set metrics at the end of each epoch as a running aggregation of the metrics during training, rather than a separate pass over the training set at the end of each epoch of training. Although this may result in “noisy” metrics in the early epochs, it generally leads to a 33% speedup in training time."
   },
   {
-    "objectID": "decisions/20240423-building-metaverse-with-glue-mechanic.html#the-downsides",
-    "href": "decisions/20240423-building-metaverse-with-glue-mechanic.html#the-downsides",
-    "title": "Accepted: Building a Metaverse with Glue Mechanic in V-Sekai",
+    "objectID": "decisions/20231110-efficient-llm-training.html#pros-and-cons",
+    "href": "decisions/20231110-efficient-llm-training.html#pros-and-cons",
+    "title": "Proposed: Efficient Training of LLMs in V-Sekai",
     "section": "",
-    "text": "May require significant changes to the existing codebase.\nThis could potentially increase the complexity of the system."
+    "text": "Pros:\n\nSignificantly reduces training time.\nAllows for more efficient use of resources.\n\nCons:\n\nEarly training metrics may appear “noisy”."
   },
   {
-    "objectID": "decisions/20240423-building-metaverse-with-glue-mechanic.html#the-road-not-taken",
-    "href": "decisions/20240423-building-metaverse-with-glue-mechanic.html#the-road-not-taken",
-    "title": "Accepted: Building a Metaverse with Glue Mechanic in V-Sekai",
+    "objectID": "decisions/20231110-efficient-llm-training.html#alternatives",
+    "href": "decisions/20231110-efficient-llm-training.html#alternatives",
+    "title": "Proposed: Efficient Training of LLMs in V-Sekai",
     "section": "",
-    "text": "An alternative approach could be to continue focusing on avatar movement and interaction within a confined space. However, this may limit the potential for expansive world-building and exploration."
+    "text": "This section will be updated with potential alternatives if the proposed solution does not yield the expected results."
   },
   {
-    "objectID": "decisions/20240423-building-metaverse-with-glue-mechanic.html#the-infrequent-use-case",
-    "href": "decisions/20240423-building-metaverse-with-glue-mechanic.html#the-infrequent-use-case",
-    "title": "Accepted: Building a Metaverse with Glue Mechanic in V-Sekai",
+    "objectID": "decisions/20231110-efficient-llm-training.html#rare-use-cases",
+    "href": "decisions/20231110-efficient-llm-training.html#rare-use-cases",
+    "title": "Proposed: Efficient Training of LLMs in V-Sekai",
     "section": "",
-    "text": "In cases where users prefer a more confined and controlled environment, the glue mechanic may not be as appealing. However, it could still provide an interesting option for those looking to experiment with world-building."
+    "text": "This section will be updated with infrequent use cases that may arise during the implementation of the proposed solution."
   },
   {
-    "objectID": "decisions/20240423-building-metaverse-with-glue-mechanic.html#in-core-and-done-by-us",
-    "href": "decisions/20240423-building-metaverse-with-glue-mechanic.html#in-core-and-done-by-us",
-    "title": "Accepted: Building a Metaverse with Glue Mechanic in V-Sekai",
+    "objectID": "decisions/20231110-efficient-llm-training.html#implementation",
+    "href": "decisions/20231110-efficient-llm-training.html#implementation",
+    "title": "Proposed: Efficient Training of LLMs in V-Sekai",
     "section": "",
-    "text": "The implementation of the glue mechanic would be done by the V-Sekai development team."
+    "text": "Is this solution core to our operations and will it be implemented by us? This section will be updated accordingly."
   },
   {
-    "objectID": "decisions/20240423-building-metaverse-with-glue-mechanic.html#status",
-    "href": "decisions/20240423-building-metaverse-with-glue-mechanic.html#status",
-    "title": "Accepted: Building a Metaverse with Glue Mechanic in V-Sekai",
+    "objectID": "decisions/20231110-efficient-llm-training.html#references",
+    "href": "decisions/20231110-efficient-llm-training.html#references",
+    "title": "Proposed: Efficient Training of LLMs in V-Sekai",
     "section": "",
-    "text": "Status: Accepted"
+    "text": "V-Sekai · GitHub\nV-Sekai/v-sekai-game\nLLM Classification - Ludwig\n\nThis proposal was assisted by Aria, an AI assistant."
   },
   {
-    "objectID": "decisions/20240423-building-metaverse-with-glue-mechanic.html#decision-makers",
-    "href": "decisions/20240423-building-metaverse-with-glue-mechanic.html#decision-makers",
-    "title": "Accepted: Building a Metaverse with Glue Mechanic in V-Sekai",
+    "objectID": "decisions/20231127-performance-test.html",
+    "href": "decisions/20231127-performance-test.html",
+    "title": "Accepted: Benchmarking Network Performance for Scalable Multiplayer in Godot",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "Status: Proposed \nDeciders: V-Sekai Team, Bioblaze Payne, fire\nTags: Networking, Performance, Godot Engine, V-Sekai, Test\n\n\n\n\nIn the pursuit of optimizing network performance for the V-Sekai project, we’re at a point where we need to evaluate different networking strategies provided by the Godot Engine.\n\n\n\nDesign a comprehensive series of tests to measure and compare the performance of the three different networked multiplayer strategies within the Godot Engine:\n\nThe many servers approach: A decentralized model where numerous smaller servers handle subsets of users.\nThe many worlds approach: A single server hosts multiple distinct world instances.\nThe one world with threaded process group nodes: A monolithic single world that leverages threading to manage users and activities.\n\n\n\n\nThe testing was suggested by Bioblaze Payne, who has outlined a sequential approach:\n\nPhase 1: Basic Connection Test\n\nConnect a user, send a message, await 1000 messages in return, disconnect, then reconnect.\n\nPhase 2: Large Scale Stress Test\n\nSimultaneously connect 4000 users, with each sending a message upon connection every 500ms. Ensure all messages are replicated to all connected clients.\n\n\nDuring these tests, we’ll monitor:\n\nLoad times for initial connections and reconnections.\nThroughput and latency of message delivery.\nServer resource usage (CPU, RAM, Network I/O).\nAny errors or dropped connections that occur.\n\nAll relevant events should be timestamped and logged to a centralized logging system for analysis.\n\n\n\nBy conducting this research, we aim to:\n\nIdentify the most scalable and efficient networking strategy for the V-Sekai project.\nGather empirical data to inform future development decisions.\nContribute findings back to the wider Godot community to aid in similar multiplayer projects.\n\n\n\n\nPotential risks and drawbacks include:\n\nTime and resources required for test setup and execution.\nInterpretation of results may vary, leading to indecision.\nPossible discovery of fundamental issues that could delay project timelines.\n\n\n\n\nThis section will detail alternative methods and practices considered but ultimately not chosen, with justifications for their exclusion.\n\n\n\nWe will also explore less common user scenarios that may have unique performance characteristics under each networking strategy.\n\n\n\nDiscussion on whether the outcomes of this initiative should be integrated into the core V-Sekai codebase or maintained as separate modules.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis design document was completed with assistance from AI developer Aria."
   },
   {
-    "objectID": "decisions/20240423-building-metaverse-with-glue-mechanic.html#tags",
-    "href": "decisions/20240423-building-metaverse-with-glue-mechanic.html#tags",
-    "title": "Accepted: Building a Metaverse with Glue Mechanic in V-Sekai",
+    "objectID": "decisions/20231127-performance-test.html#metadata",
+    "href": "decisions/20231127-performance-test.html#metadata",
+    "title": "Accepted: Benchmarking Network Performance for Scalable Multiplayer in Godot",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Status: Proposed \nDeciders: V-Sekai Team, Bioblaze Payne, fire\nTags: Networking, Performance, Godot Engine, V-Sekai, Test"
   },
   {
-    "objectID": "decisions/20240423-building-metaverse-with-glue-mechanic.html#further-reading",
-    "href": "decisions/20240423-building-metaverse-with-glue-mechanic.html#further-reading",
-    "title": "Accepted: Building a Metaverse with Glue Mechanic in V-Sekai",
+    "objectID": "decisions/20231127-performance-test.html#the-backdrop",
+    "href": "decisions/20231127-performance-test.html#the-backdrop",
+    "title": "Accepted: Benchmarking Network Performance for Scalable Multiplayer in Godot",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "In the pursuit of optimizing network performance for the V-Sekai project, we’re at a point where we need to evaluate different networking strategies provided by the Godot Engine."
   },
   {
-    "objectID": "decisions/20230125-create-an-in-game-tablet-interface-we-can-activate.html",
-    "href": "decisions/20230125-create-an-in-game-tablet-interface-we-can-activate.html",
-    "title": "Proposed: Create an in-game tablet interface we can activate",
+    "objectID": "decisions/20231127-performance-test.html#the-challenge",
+    "href": "decisions/20231127-performance-test.html#the-challenge",
+    "title": "Accepted: Benchmarking Network Performance for Scalable Multiplayer in Godot",
     "section": "",
-    "text": "Proposed: Create an in-game tablet interface we can activate\n\nMetadata\n\nStatus: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nContext and Problem Statement\nWe want to activate things in vr\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nShow a menu on each hand and have it be possible to activate grid cell options.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\n\nTrigger presents a menu\nShort press\nLong press\n\n\n\nPositive Consequences\nWe are able to use V-Sekai easier.\n\n\nNegative Consequences\nWe cannot get other features to trigger things.\n\n\nOption graveyard\n\nOption: The status quo to go out of the game to trigger menus. \nRejection Reason: This solves nothing. \n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nKnowing what to do is hard.\n\n\nIs there a reason why this should be core and done by us?\nUsability is a core feature.\n\n\nReferences\n\nV-Sekai"
+    "text": "Design a comprehensive series of tests to measure and compare the performance of the three different networked multiplayer strategies within the Godot Engine:\n\nThe many servers approach: A decentralized model where numerous smaller servers handle subsets of users.\nThe many worlds approach: A single server hosts multiple distinct world instances.\nThe one world with threaded process group nodes: A monolithic single world that leverages threading to manage users and activities."
   },
   {
-    "objectID": "decisions/20230803-publish-vrm-to-assetlibrary.html",
-    "href": "decisions/20230803-publish-vrm-to-assetlibrary.html",
-    "title": "Accepted: Completing VRM 1.0 Support and Publishing to Godot Engine Asset Library",
+    "objectID": "decisions/20231127-performance-test.html#the-strategy",
+    "href": "decisions/20231127-performance-test.html#the-strategy",
+    "title": "Accepted: Benchmarking Network Performance for Scalable Multiplayer in Godot",
     "section": "",
-    "text": "Status: Accepted\nDeciders: V-Sekai, lyuma, fire\nTags: VRM, Avatars, VRM 1.0, Export, Godot Engine\n\n\n\n\nWe currently support an older revision of the VRM standard for avatars. However, VRM 1.0 is a new revision that we need to implement. A key feature of this new revision is the ability to export VRM 1.0 files. Additionally, we also need to publish our implementation to the Godot Engine asset library.\n\n\n\n\n\n\nAnalyze the current implementation of the VRM standard in our system.\nUnderstand the changes and enhancements introduced in VRM 1.0.\nPlan the implementation of VRM 1.0 support, including the export feature.\nImplement the planned features and changes.\nTest the newly implemented VRM 1.0 support in different scenarios.\nPrepare the implementation for publishing to the Godot Engine asset library.\nPublish the implementation to the Godot Engine asset library.\n\n\n\n\n\nThe implementation details will be decided upon acceptance of this proposal.\n\n\n\n\nEnhanced avatar functionality with VRM 1.0 support.\nAbility to export VRM 1.0 files, increasing compatibility with other systems.\nStaying up-to-date with the latest standards in the industry.\nIncreased visibility and usage through publishing to the Godot Engine asset library.\n\n\n\n\n\nRequires understanding of the new VRM 1.0 standard.\nPotential increase in development time due to the complexity of implementing a new standard and preparing it for publishing.\nNeed to maintain the published asset in the Godot Engine asset library.\n\n\n\n\nThis section will be filled as we explore different options and discard those that are not feasible or effective.\n\n\n\nGiven the complexity of implementing a new standard like VRM 1.0 and publishing it to the Godot Engine asset library, it cannot be simply worked around with a few lines of script.\n\n\n\nImplementing VRM 1.0 support and publishing it to the Godot Engine asset library is crucial for staying competitive and relevant in the industry. It also aligns with our goal of providing the best possible avatar functionalities to our users.\n\n\n\n\nVRM 1.0 Specification"
+    "text": "The testing was suggested by Bioblaze Payne, who has outlined a sequential approach:\n\nPhase 1: Basic Connection Test\n\nConnect a user, send a message, await 1000 messages in return, disconnect, then reconnect.\n\nPhase 2: Large Scale Stress Test\n\nSimultaneously connect 4000 users, with each sending a message upon connection every 500ms. Ensure all messages are replicated to all connected clients.\n\n\nDuring these tests, we’ll monitor:\n\nLoad times for initial connections and reconnections.\nThroughput and latency of message delivery.\nServer resource usage (CPU, RAM, Network I/O).\nAny errors or dropped connections that occur.\n\nAll relevant events should be timestamped and logged to a centralized logging system for analysis."
   },
   {
-    "objectID": "decisions/20230803-publish-vrm-to-assetlibrary.html#metadata",
-    "href": "decisions/20230803-publish-vrm-to-assetlibrary.html#metadata",
-    "title": "Accepted: Completing VRM 1.0 Support and Publishing to Godot Engine Asset Library",
+    "objectID": "decisions/20231127-performance-test.html#the-upside",
+    "href": "decisions/20231127-performance-test.html#the-upside",
+    "title": "Accepted: Benchmarking Network Performance for Scalable Multiplayer in Godot",
     "section": "",
-    "text": "Status: Accepted\nDeciders: V-Sekai, lyuma, fire\nTags: VRM, Avatars, VRM 1.0, Export, Godot Engine"
+    "text": "By conducting this research, we aim to:\n\nIdentify the most scalable and efficient networking strategy for the V-Sekai project.\nGather empirical data to inform future development decisions.\nContribute findings back to the wider Godot community to aid in similar multiplayer projects."
   },
   {
-    "objectID": "decisions/20230803-publish-vrm-to-assetlibrary.html#context-and-problem-statement",
-    "href": "decisions/20230803-publish-vrm-to-assetlibrary.html#context-and-problem-statement",
-    "title": "Accepted: Completing VRM 1.0 Support and Publishing to Godot Engine Asset Library",
+    "objectID": "decisions/20231127-performance-test.html#the-downside",
+    "href": "decisions/20231127-performance-test.html#the-downside",
+    "title": "Accepted: Benchmarking Network Performance for Scalable Multiplayer in Godot",
     "section": "",
-    "text": "We currently support an older revision of the VRM standard for avatars. However, VRM 1.0 is a new revision that we need to implement. A key feature of this new revision is the ability to export VRM 1.0 files. Additionally, we also need to publish our implementation to the Godot Engine asset library."
+    "text": "Potential risks and drawbacks include:\n\nTime and resources required for test setup and execution.\nInterpretation of results may vary, leading to indecision.\nPossible discovery of fundamental issues that could delay project timelines."
   },
   {
-    "objectID": "decisions/20230803-publish-vrm-to-assetlibrary.html#proposed-solution",
-    "href": "decisions/20230803-publish-vrm-to-assetlibrary.html#proposed-solution",
-    "title": "Accepted: Completing VRM 1.0 Support and Publishing to Godot Engine Asset Library",
+    "objectID": "decisions/20231127-performance-test.html#the-road-not-taken",
+    "href": "decisions/20231127-performance-test.html#the-road-not-taken",
+    "title": "Accepted: Benchmarking Network Performance for Scalable Multiplayer in Godot",
     "section": "",
-    "text": "Analyze the current implementation of the VRM standard in our system.\nUnderstand the changes and enhancements introduced in VRM 1.0.\nPlan the implementation of VRM 1.0 support, including the export feature.\nImplement the planned features and changes.\nTest the newly implemented VRM 1.0 support in different scenarios.\nPrepare the implementation for publishing to the Godot Engine asset library.\nPublish the implementation to the Godot Engine asset library."
+    "text": "This section will detail alternative methods and practices considered but ultimately not chosen, with justifications for their exclusion."
   },
   {
-    "objectID": "decisions/20230803-publish-vrm-to-assetlibrary.html#implementation",
-    "href": "decisions/20230803-publish-vrm-to-assetlibrary.html#implementation",
-    "title": "Accepted: Completing VRM 1.0 Support and Publishing to Godot Engine Asset Library",
+    "objectID": "decisions/20231127-performance-test.html#the-infrequent-use-case",
+    "href": "decisions/20231127-performance-test.html#the-infrequent-use-case",
+    "title": "Accepted: Benchmarking Network Performance for Scalable Multiplayer in Godot",
     "section": "",
-    "text": "The implementation details will be decided upon acceptance of this proposal."
+    "text": "We will also explore less common user scenarios that may have unique performance characteristics under each networking strategy."
   },
   {
-    "objectID": "decisions/20230803-publish-vrm-to-assetlibrary.html#positive-consequences",
-    "href": "decisions/20230803-publish-vrm-to-assetlibrary.html#positive-consequences",
-    "title": "Accepted: Completing VRM 1.0 Support and Publishing to Godot Engine Asset Library",
+    "objectID": "decisions/20231127-performance-test.html#in-core-and-done-by-us",
+    "href": "decisions/20231127-performance-test.html#in-core-and-done-by-us",
+    "title": "Accepted: Benchmarking Network Performance for Scalable Multiplayer in Godot",
     "section": "",
-    "text": "Enhanced avatar functionality with VRM 1.0 support.\nAbility to export VRM 1.0 files, increasing compatibility with other systems.\nStaying up-to-date with the latest standards in the industry.\nIncreased visibility and usage through publishing to the Godot Engine asset library."
+    "text": "Discussion on whether the outcomes of this initiative should be integrated into the core V-Sekai codebase or maintained as separate modules."
   },
   {
-    "objectID": "decisions/20230803-publish-vrm-to-assetlibrary.html#negative-consequences",
-    "href": "decisions/20230803-publish-vrm-to-assetlibrary.html#negative-consequences",
-    "title": "Accepted: Completing VRM 1.0 Support and Publishing to Godot Engine Asset Library",
+    "objectID": "decisions/20231127-performance-test.html#further-reading",
+    "href": "decisions/20231127-performance-test.html#further-reading",
+    "title": "Accepted: Benchmarking Network Performance for Scalable Multiplayer in Godot",
     "section": "",
-    "text": "Requires understanding of the new VRM 1.0 standard.\nPotential increase in development time due to the complexity of implementing a new standard and preparing it for publishing.\nNeed to maintain the published asset in the Godot Engine asset library."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis design document was completed with assistance from AI developer Aria."
   },
   {
-    "objectID": "decisions/20230803-publish-vrm-to-assetlibrary.html#option-graveyard",
-    "href": "decisions/20230803-publish-vrm-to-assetlibrary.html#option-graveyard",
-    "title": "Accepted: Completing VRM 1.0 Support and Publishing to Godot Engine Asset Library",
+    "objectID": "decisions/20240117-pivot-painting.html",
+    "href": "decisions/20240117-pivot-painting.html",
+    "title": "Proposed: Provide Pivot Painting Resources",
     "section": "",
-    "text": "This section will be filled as we explore different options and discard those that are not feasible or effective."
+    "text": "Status: Proposed\nDeciders: V-Sekai, Silent, fire\nTags: V-Sekai\n\n\n\n\nThe V-Sekai community has identified the need for tools that assist with pivot painting, a technique to enhance animations in game development.\n\n\n\nSilent inquired about available pivot painting tools compatible with our workflow.\n\n\n\nOur strategy involves curating a list of pivot painting resources, documenting best practices, and providing educational content to facilitate their use.\n\n\n\nThese resources will allow for more complex animations and efficiency gains in our creative process.\n\n\n\nAdoption of new tools comes with a learning curve that might slow down initial productivity.\n\n\n\nWe need to assess whether in-house tool development justifies the required investment based on our pipeline needs.\n\n\n\n\nV-Sekai · GitHub\nV-Sekai/v-sekai-game\nSideFX Tutorial on Pivot Painter\nBlender Pivot Painter\nNot Unreal Tools: Vertex Animation Tools\n\nAssistance from AI assistant Aria acknowledged."
   },
   {
-    "objectID": "decisions/20230803-publish-vrm-to-assetlibrary.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230803-publish-vrm-to-assetlibrary.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Accepted: Completing VRM 1.0 Support and Publishing to Godot Engine Asset Library",
+    "objectID": "decisions/20240117-pivot-painting.html#metadata",
+    "href": "decisions/20240117-pivot-painting.html#metadata",
+    "title": "Proposed: Provide Pivot Painting Resources",
     "section": "",
-    "text": "Given the complexity of implementing a new standard like VRM 1.0 and publishing it to the Godot Engine asset library, it cannot be simply worked around with a few lines of script."
+    "text": "Status: Proposed\nDeciders: V-Sekai, Silent, fire\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20230803-publish-vrm-to-assetlibrary.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230803-publish-vrm-to-assetlibrary.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Accepted: Completing VRM 1.0 Support and Publishing to Godot Engine Asset Library",
+    "objectID": "decisions/20240117-pivot-painting.html#the-backdrop",
+    "href": "decisions/20240117-pivot-painting.html#the-backdrop",
+    "title": "Proposed: Provide Pivot Painting Resources",
     "section": "",
-    "text": "Implementing VRM 1.0 support and publishing it to the Godot Engine asset library is crucial for staying competitive and relevant in the industry. It also aligns with our goal of providing the best possible avatar functionalities to our users."
+    "text": "The V-Sekai community has identified the need for tools that assist with pivot painting, a technique to enhance animations in game development."
   },
   {
-    "objectID": "decisions/20230803-publish-vrm-to-assetlibrary.html#references",
-    "href": "decisions/20230803-publish-vrm-to-assetlibrary.html#references",
-    "title": "Accepted: Completing VRM 1.0 Support and Publishing to Godot Engine Asset Library",
+    "objectID": "decisions/20240117-pivot-painting.html#the-challenge",
+    "href": "decisions/20240117-pivot-painting.html#the-challenge",
+    "title": "Proposed: Provide Pivot Painting Resources",
     "section": "",
-    "text": "VRM 1.0 Specification"
+    "text": "Silent inquired about available pivot painting tools compatible with our workflow."
   },
   {
-    "objectID": "decisions/20220515-profile-using-perf.html",
-    "href": "decisions/20220515-profile-using-perf.html",
-    "title": "Proposed: Profile using perf",
+    "objectID": "decisions/20240117-pivot-painting.html#the-strategy",
+    "href": "decisions/20240117-pivot-painting.html#the-strategy",
+    "title": "Proposed: Provide Pivot Painting Resources",
     "section": "",
-    "text": "Proposed: Profile using perf\n\nDescribe the status of the issue.\n\nproposed\ndraft\nrejected\naccepted\ndeprecated\nsuperseded by\n\n\n\nList the deciders of the issue.\nV-Sekai,fire,\n\n\nDescribe the tags of the issue.\nV-Sekai,\n\n\nContext and Problem Statement\nWant a workflow to profile Godot Groups.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nUse perf and hotspot.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nsudo apt-get install linux-tools-common linux-tools-generic linux-tools-`uname -r`\nperf record -o perf.data --call-graph dwarf --aio --sample-cpu ./godot/bin/godot.linuxbsd.opt.tools.64.llvm --path groups hotspot perf.data\n\n\n\nimage\n\n\n\n\nPositive Consequences\nCan better find hotspots.\n\n\nNegative Consequences\nCurrently Linux only.\n\n\nOption graveyard\n\nSuperluminal is Windows only.\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot Godot Engine code.\n\n\nIs there a reason why this should be core and done by us?\nWe need to be aware of performance.\n\n\nReferences\n\nV-Sekai\n\n\n\nLicense of the contribution\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Our strategy involves curating a list of pivot painting resources, documenting best practices, and providing educational content to facilitate their use."
   },
   {
-    "objectID": "decisions/20240330-k8s-harvester-hci.html",
-    "href": "decisions/20240330-k8s-harvester-hci.html",
-    "title": "Accepted: k8s on harvester hci",
+    "objectID": "decisions/20240117-pivot-painting.html#the-upside",
+    "href": "decisions/20240117-pivot-painting.html#the-upside",
+    "title": "Proposed: Provide Pivot Painting Resources",
     "section": "",
-    "text": "Kubernetes is a standard for managing containerized applications. Harvester, an open-source HCI software built on Kubernetes, manages virtual machines, storage, and network resources. Installing Rancher on Harvester enhances Kubernetes management.\n\n\n\nThe challenge is installing Rancher directly on a Harvester VM using the rancher-vcluster addon, which allows Rancher Manager to run as a workload on the Harvester cluster.\n\n\n\nThe solution involves:\n\nInstalling the rancher-vcluster Addon The rancher-vcluster addon is not packaged with Harvester, but you can find it in the experimental-addons repository.\n\nAssuming you are using the Harvester kubeconfig, you can run the following command to apply the YAML file:\nssh rancher@xxx.xxx.xxx.xx\nsudo kubectl apply -f https://raw.githubusercontent.com/harvester/experimental-addons/main/rancher-vcluster/rancher-vcluster.yaml\n# Users can define the rancher url and password via addon interface.\n# hostname: \"rancher.172.19.108.3.sslip.io\"\n# password: \"hunter2\"\n# Open https://rancher.192.168.0.65.sslip.io/dashboard/auth/setup\nThis command will fetch the rancher-vcluster.yaml file from the experimental-addons repository and apply it to your Kubernetes cluster.\n\nConfiguring the Addon: Configure the addon through the Harvester UI under Advanced &gt; Addons. Edit the config for the rancher-vcluster addon, specify a hostname that points to the Harvester VIP and set a bootstrap password for Rancher.\nAccessing Rancher: Access Rancher using the DNS hostname provided during configuration after installation.\n\nThis approach integrates Rancher into Harvester, leveraging Harvester’s infrastructure to manage both VMs and containers centrally.\n\n\n\nEdit the namespace to remove its finalizers:\nFirst, you’ll need to edit the namespace to remove any finalizers that are preventing it from being deleted.\nkubectl get namespace rancher-vcluster -o json &gt; tmp.json\nOpen the tmp.json file and remove the finalizers field:\nLook for the spec section and remove the finalizers array. It should look something like this:\n\"spec\": {\n  \"finalizers\": [\n    \"kubernetes\"\n  ]\n}\nAfter removal, it should look like this:\n\"spec\": {}\nApply the modified JSON back to the cluster:\nkubectl replace --raw \"/api/v1/namespaces/rancher-vcluster/finalize\" -f ./tmp.json\nVerify the namespace has been deleted:\nkubectl get namespaces\n\nIf the namespace still does not delete, you may need to manually clean up resources within the namespace before retrying the above steps.\n\n\nForcefully removing a namespace can lead to orphaned resources. Ensure that you understand the implications of this action and have backups if necessary.\n\n\n\n\n\nThis setup enables creation and management of Kubernetes clusters through Harvester’s integration with Rancher and deployment of a Kubernetes cluster based on specific requirements (K3s).\n\n\n\nThe process can be complex and requires attention to detail. Misconfiguration could lead to issues with the installation or operation of Harvester and Rancher.\n\n\n\nAn alternative could be a network-based installation method, not feasible in an air-gapped environment.\n\n\n\nThis setup is useful in environments where internet access is restricted or unavailable, necessitating the use of the rancher-vcluster addon.\n\n\n\nThe user performs the entire process of installing and configuring the rancher-vcluster addon with guidance from this proposal.\n\n\n\nStatus: Accepted\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nRancher Vcluster\n\nAI assistant Aria assisted with this article."
+    "text": "These resources will allow for more complex animations and efficiency gains in our creative process."
   },
   {
-    "objectID": "decisions/20240330-k8s-harvester-hci.html#the-context",
-    "href": "decisions/20240330-k8s-harvester-hci.html#the-context",
-    "title": "Accepted: k8s on harvester hci",
+    "objectID": "decisions/20240117-pivot-painting.html#the-downside",
+    "href": "decisions/20240117-pivot-painting.html#the-downside",
+    "title": "Proposed: Provide Pivot Painting Resources",
     "section": "",
-    "text": "Kubernetes is a standard for managing containerized applications. Harvester, an open-source HCI software built on Kubernetes, manages virtual machines, storage, and network resources. Installing Rancher on Harvester enhances Kubernetes management."
+    "text": "Adoption of new tools comes with a learning curve that might slow down initial productivity."
   },
   {
-    "objectID": "decisions/20240330-k8s-harvester-hci.html#the-problem-statement",
-    "href": "decisions/20240330-k8s-harvester-hci.html#the-problem-statement",
-    "title": "Accepted: k8s on harvester hci",
+    "objectID": "decisions/20240117-pivot-painting.html#in-core-and-done-by-us",
+    "href": "decisions/20240117-pivot-painting.html#in-core-and-done-by-us",
+    "title": "Proposed: Provide Pivot Painting Resources",
     "section": "",
-    "text": "The challenge is installing Rancher directly on a Harvester VM using the rancher-vcluster addon, which allows Rancher Manager to run as a workload on the Harvester cluster."
+    "text": "We need to assess whether in-house tool development justifies the required investment based on our pipeline needs."
   },
   {
-    "objectID": "decisions/20240330-k8s-harvester-hci.html#solution",
-    "href": "decisions/20240330-k8s-harvester-hci.html#solution",
-    "title": "Accepted: k8s on harvester hci",
+    "objectID": "decisions/20240117-pivot-painting.html#further-reading",
+    "href": "decisions/20240117-pivot-painting.html#further-reading",
+    "title": "Proposed: Provide Pivot Painting Resources",
     "section": "",
-    "text": "The solution involves:\n\nInstalling the rancher-vcluster Addon The rancher-vcluster addon is not packaged with Harvester, but you can find it in the experimental-addons repository.\n\nAssuming you are using the Harvester kubeconfig, you can run the following command to apply the YAML file:\nssh rancher@xxx.xxx.xxx.xx\nsudo kubectl apply -f https://raw.githubusercontent.com/harvester/experimental-addons/main/rancher-vcluster/rancher-vcluster.yaml\n# Users can define the rancher url and password via addon interface.\n# hostname: \"rancher.172.19.108.3.sslip.io\"\n# password: \"hunter2\"\n# Open https://rancher.192.168.0.65.sslip.io/dashboard/auth/setup\nThis command will fetch the rancher-vcluster.yaml file from the experimental-addons repository and apply it to your Kubernetes cluster.\n\nConfiguring the Addon: Configure the addon through the Harvester UI under Advanced &gt; Addons. Edit the config for the rancher-vcluster addon, specify a hostname that points to the Harvester VIP and set a bootstrap password for Rancher.\nAccessing Rancher: Access Rancher using the DNS hostname provided during configuration after installation.\n\nThis approach integrates Rancher into Harvester, leveraging Harvester’s infrastructure to manage both VMs and containers centrally.\n\n\n\nEdit the namespace to remove its finalizers:\nFirst, you’ll need to edit the namespace to remove any finalizers that are preventing it from being deleted.\nkubectl get namespace rancher-vcluster -o json &gt; tmp.json\nOpen the tmp.json file and remove the finalizers field:\nLook for the spec section and remove the finalizers array. It should look something like this:\n\"spec\": {\n  \"finalizers\": [\n    \"kubernetes\"\n  ]\n}\nAfter removal, it should look like this:\n\"spec\": {}\nApply the modified JSON back to the cluster:\nkubectl replace --raw \"/api/v1/namespaces/rancher-vcluster/finalize\" -f ./tmp.json\nVerify the namespace has been deleted:\nkubectl get namespaces\n\nIf the namespace still does not delete, you may need to manually clean up resources within the namespace before retrying the above steps.\n\n\nForcefully removing a namespace can lead to orphaned resources. Ensure that you understand the implications of this action and have backups if necessary."
+    "text": "V-Sekai · GitHub\nV-Sekai/v-sekai-game\nSideFX Tutorial on Pivot Painter\nBlender Pivot Painter\nNot Unreal Tools: Vertex Animation Tools\n\nAssistance from AI assistant Aria acknowledged."
   },
   {
-    "objectID": "decisions/20240330-k8s-harvester-hci.html#the-benefits",
-    "href": "decisions/20240330-k8s-harvester-hci.html#the-benefits",
-    "title": "Accepted: k8s on harvester hci",
+    "objectID": "decisions/20240613-training-dataset-creation-with-csg.html",
+    "href": "decisions/20240613-training-dataset-creation-with-csg.html",
+    "title": "Proposed: Dataset Creation with CSG",
     "section": "",
-    "text": "This setup enables creation and management of Kubernetes clusters through Harvester’s integration with Rancher and deployment of a Kubernetes cluster based on specific requirements (K3s)."
+    "text": "We’re working on a project that involves creating 3D models using Constructive Solid Geometry (CSG). We need to create a dataset of these models, but we can’t afford to pay for it and we don’t want to build our own platform.\n\n\n\nThe challenge is how to gather a large and diverse set of 3D models represented as CSG trees without financial expenditure and without building our own platform.\n\n\n\n\nEngage Open-Source Communities: Connect with people who are into 3D modeling and CSG. They might be interested in contributing to our project.\nCollaborate with Educational Institutions: Partner with colleges that offer courses in 3D modeling. Students could contribute to our project as part of their coursework or for extra credit.\nProvide Clear Guidelines: Write up detailed instructions on how to create and submit the models. This should include technical specifications, style guides, and examples.\nImplement a Review Process: Each model should be reviewed to ensure it meets our quality standards and follows our style guide.\nUse Existing Platforms for Submission: Use platforms like GitHub or Google Drive for contributors to submit their models.\n\n\n\n\n\nWe can gather a large and diverse dataset without having to pay.\nChecking the models ourselves ensures they’ll be of good quality and consistent.\nUsing an existing platform saves us time and resources.\n\n\n\n\n\nManaging a project with volunteers can be complex and time-consuming.\nEnsuring consistent quality and style across all submissions may be challenging.\nDepending on external platforms for submission might limit some functionalities that could be possible with a custom-built platform.\n\n\n\n\nWe could consider using existing open-source 3D model datasets, but these might not meet our specific needs in terms of quality, style, and representation as CSG trees.\n\n\n\nThis approach might not be suitable if we need very specific models in our dataset that require specialized knowledge or skills to create.\n\n\n\nThe management of the project, the provision of clear guidelines, and the review of the submissions will be done by us, using our resources and expertise.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\niFire\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nConstructive Solid Geometry (CSG) - More about CSG.\nOpen Source - More about open source.\nV-Sekai · GitHub - The GitHub account for V-Sekai.\nV-Sekai/v-sekai-game - The GitHub page for the V-Sekai project.\n\nAI assistant Aria assisted with this proposal."
   },
   {
-    "objectID": "decisions/20240330-k8s-harvester-hci.html#the-downsides",
-    "href": "decisions/20240330-k8s-harvester-hci.html#the-downsides",
-    "title": "Accepted: k8s on harvester hci",
+    "objectID": "decisions/20240613-training-dataset-creation-with-csg.html#the-context",
+    "href": "decisions/20240613-training-dataset-creation-with-csg.html#the-context",
+    "title": "Proposed: Dataset Creation with CSG",
     "section": "",
-    "text": "The process can be complex and requires attention to detail. Misconfiguration could lead to issues with the installation or operation of Harvester and Rancher."
+    "text": "We’re working on a project that involves creating 3D models using Constructive Solid Geometry (CSG). We need to create a dataset of these models, but we can’t afford to pay for it and we don’t want to build our own platform."
   },
   {
-    "objectID": "decisions/20240330-k8s-harvester-hci.html#the-road-not-taken",
-    "href": "decisions/20240330-k8s-harvester-hci.html#the-road-not-taken",
-    "title": "Accepted: k8s on harvester hci",
+    "objectID": "decisions/20240613-training-dataset-creation-with-csg.html#the-problem-statement",
+    "href": "decisions/20240613-training-dataset-creation-with-csg.html#the-problem-statement",
+    "title": "Proposed: Dataset Creation with CSG",
     "section": "",
-    "text": "An alternative could be a network-based installation method, not feasible in an air-gapped environment."
+    "text": "The challenge is how to gather a large and diverse set of 3D models represented as CSG trees without financial expenditure and without building our own platform."
   },
   {
-    "objectID": "decisions/20240330-k8s-harvester-hci.html#the-infrequent-use-case",
-    "href": "decisions/20240330-k8s-harvester-hci.html#the-infrequent-use-case",
-    "title": "Accepted: k8s on harvester hci",
+    "objectID": "decisions/20240613-training-dataset-creation-with-csg.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240613-training-dataset-creation-with-csg.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Dataset Creation with CSG",
     "section": "",
-    "text": "This setup is useful in environments where internet access is restricted or unavailable, necessitating the use of the rancher-vcluster addon."
+    "text": "Engage Open-Source Communities: Connect with people who are into 3D modeling and CSG. They might be interested in contributing to our project.\nCollaborate with Educational Institutions: Partner with colleges that offer courses in 3D modeling. Students could contribute to our project as part of their coursework or for extra credit.\nProvide Clear Guidelines: Write up detailed instructions on how to create and submit the models. This should include technical specifications, style guides, and examples.\nImplement a Review Process: Each model should be reviewed to ensure it meets our quality standards and follows our style guide.\nUse Existing Platforms for Submission: Use platforms like GitHub or Google Drive for contributors to submit their models."
   },
   {
-    "objectID": "decisions/20240330-k8s-harvester-hci.html#in-core-and-done-by-us",
-    "href": "decisions/20240330-k8s-harvester-hci.html#in-core-and-done-by-us",
-    "title": "Accepted: k8s on harvester hci",
+    "objectID": "decisions/20240613-training-dataset-creation-with-csg.html#the-benefits",
+    "href": "decisions/20240613-training-dataset-creation-with-csg.html#the-benefits",
+    "title": "Proposed: Dataset Creation with CSG",
     "section": "",
-    "text": "The user performs the entire process of installing and configuring the rancher-vcluster addon with guidance from this proposal."
+    "text": "We can gather a large and diverse dataset without having to pay.\nChecking the models ourselves ensures they’ll be of good quality and consistent.\nUsing an existing platform saves us time and resources."
   },
   {
-    "objectID": "decisions/20240330-k8s-harvester-hci.html#status",
-    "href": "decisions/20240330-k8s-harvester-hci.html#status",
-    "title": "Accepted: k8s on harvester hci",
+    "objectID": "decisions/20240613-training-dataset-creation-with-csg.html#the-downsides",
+    "href": "decisions/20240613-training-dataset-creation-with-csg.html#the-downsides",
+    "title": "Proposed: Dataset Creation with CSG",
     "section": "",
-    "text": "Status: Accepted"
+    "text": "Managing a project with volunteers can be complex and time-consuming.\nEnsuring consistent quality and style across all submissions may be challenging.\nDepending on external platforms for submission might limit some functionalities that could be possible with a custom-built platform."
   },
   {
-    "objectID": "decisions/20240330-k8s-harvester-hci.html#decision-makers",
-    "href": "decisions/20240330-k8s-harvester-hci.html#decision-makers",
-    "title": "Accepted: k8s on harvester hci",
+    "objectID": "decisions/20240613-training-dataset-creation-with-csg.html#the-road-not-taken",
+    "href": "decisions/20240613-training-dataset-creation-with-csg.html#the-road-not-taken",
+    "title": "Proposed: Dataset Creation with CSG",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "We could consider using existing open-source 3D model datasets, but these might not meet our specific needs in terms of quality, style, and representation as CSG trees."
   },
   {
-    "objectID": "decisions/20240330-k8s-harvester-hci.html#tags",
-    "href": "decisions/20240330-k8s-harvester-hci.html#tags",
-    "title": "Accepted: k8s on harvester hci",
+    "objectID": "decisions/20240613-training-dataset-creation-with-csg.html#the-infrequent-use-case",
+    "href": "decisions/20240613-training-dataset-creation-with-csg.html#the-infrequent-use-case",
+    "title": "Proposed: Dataset Creation with CSG",
     "section": "",
-    "text": "V-Sekai"
+    "text": "This approach might not be suitable if we need very specific models in our dataset that require specialized knowledge or skills to create."
   },
   {
-    "objectID": "decisions/20240330-k8s-harvester-hci.html#further-reading",
-    "href": "decisions/20240330-k8s-harvester-hci.html#further-reading",
-    "title": "Accepted: k8s on harvester hci",
+    "objectID": "decisions/20240613-training-dataset-creation-with-csg.html#in-core-and-done-by-us",
+    "href": "decisions/20240613-training-dataset-creation-with-csg.html#in-core-and-done-by-us",
+    "title": "Proposed: Dataset Creation with CSG",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nRancher Vcluster\n\nAI assistant Aria assisted with this article."
+    "text": "The management of the project, the provision of clear guidelines, and the review of the submissions will be done by us, using our resources and expertise."
   },
   {
-    "objectID": "decisions/20211005-solve-mocap-by-connecting-mediapipe-to-blender.html",
-    "href": "decisions/20211005-solve-mocap-by-connecting-mediapipe-to-blender.html",
-    "title": "Proposed: Solve Mocap By Connecting Mediapipe to Blender",
+    "objectID": "decisions/20240613-training-dataset-creation-with-csg.html#status",
+    "href": "decisions/20240613-training-dataset-creation-with-csg.html#status",
+    "title": "Proposed: Dataset Creation with CSG",
     "section": "",
-    "text": "Want to animate a blender file with mediapipe\n\n\n\nBy writing a c++ executable on Linux, we can connect Mediapipe to Blender.\n\n\n\n\nCreate a wrapper for https://github.com/infosia/vmc2bvh/tree/master/osc\nInstall Blender addon https://github.com/maybites/blender.NodeOSC\nConvert python script to c++\nMake c++ buildable by bazel\nBuild executables on Github Actions\n\n\n\n\nhttps://github.com/CLIUtils/CLI11 for command line parsing\nhttps://github.com/infosia/vmc2bvh/blob/master/code/Vmc2Bvh.cpp for example code\nFor each process send osc to node osc (Blender).\nCreate a structure for the messages\n\n\n\n\n\nML and armature work is hard\n\n\n\nIs there a reason why this should be core and done by us?\n\n\n\nFrom Kendrick\n\nmedia_pipe_demo.zip\nhttps://github.com/V-Sekai/game-tools-V-Sekai\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20211005-solve-mocap-by-connecting-mediapipe-to-blender.html#context-and-problem-statement",
-    "href": "decisions/20211005-solve-mocap-by-connecting-mediapipe-to-blender.html#context-and-problem-statement",
-    "title": "Proposed: Solve Mocap By Connecting Mediapipe to Blender",
+    "objectID": "decisions/20240613-training-dataset-creation-with-csg.html#decision-makers",
+    "href": "decisions/20240613-training-dataset-creation-with-csg.html#decision-makers",
+    "title": "Proposed: Dataset Creation with CSG",
     "section": "",
-    "text": "Want to animate a blender file with mediapipe"
+    "text": "V-Sekai development team\niFire"
   },
   {
-    "objectID": "decisions/20211005-solve-mocap-by-connecting-mediapipe-to-blender.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20211005-solve-mocap-by-connecting-mediapipe-to-blender.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: Solve Mocap By Connecting Mediapipe to Blender",
+    "objectID": "decisions/20240613-training-dataset-creation-with-csg.html#tags",
+    "href": "decisions/20240613-training-dataset-creation-with-csg.html#tags",
+    "title": "Proposed: Dataset Creation with CSG",
     "section": "",
-    "text": "By writing a c++ executable on Linux, we can connect Mediapipe to Blender."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20211005-solve-mocap-by-connecting-mediapipe-to-blender.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20211005-solve-mocap-by-connecting-mediapipe-to-blender.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Solve Mocap By Connecting Mediapipe to Blender",
+    "objectID": "decisions/20240613-training-dataset-creation-with-csg.html#further-reading",
+    "href": "decisions/20240613-training-dataset-creation-with-csg.html#further-reading",
+    "title": "Proposed: Dataset Creation with CSG",
     "section": "",
-    "text": "Create a wrapper for https://github.com/infosia/vmc2bvh/tree/master/osc\nInstall Blender addon https://github.com/maybites/blender.NodeOSC\nConvert python script to c++\nMake c++ buildable by bazel\nBuild executables on Github Actions\n\n\n\n\nhttps://github.com/CLIUtils/CLI11 for command line parsing\nhttps://github.com/infosia/vmc2bvh/blob/master/code/Vmc2Bvh.cpp for example code\nFor each process send osc to node osc (Blender).\nCreate a structure for the messages"
+    "text": "Constructive Solid Geometry (CSG) - More about CSG.\nOpen Source - More about open source.\nV-Sekai · GitHub - The GitHub account for V-Sekai.\nV-Sekai/v-sekai-game - The GitHub page for the V-Sekai project.\n\nAI assistant Aria assisted with this proposal."
   },
   {
-    "objectID": "decisions/20211005-solve-mocap-by-connecting-mediapipe-to-blender.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20211005-solve-mocap-by-connecting-mediapipe-to-blender.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Solve Mocap By Connecting Mediapipe to Blender",
+    "objectID": "decisions/20241028-use-data-tables-for-godot-constraints.html",
+    "href": "decisions/20241028-use-data-tables-for-godot-constraints.html",
+    "title": "Proposal: Use Data Tables for Godot Constraints",
     "section": "",
-    "text": "ML and armature work is hard"
+    "text": "In the development of VR applications using the Godot Engine, managing complex interactions and constraints can become cumbersome and error-prone when handled purely through code.\n\n\n\nCurrently, developers must manually code each constraint and interaction within the Godot Engine, which is time-consuming and increases the risk of errors. This approach lacks scalability and efficiency, particularly in large-scale VR projects like those developed by V-Sekai.\n\n\n\nThe proposal involves integrating a data table system within the Godot Engine to manage constraints. Here’s a basic example of how it might look in pseudo-code:\n\n\n\n\nScalability: Easier to manage large numbers of constraints.\nEfficiency: Reduces development time by allowing non-programmers to adjust constraints.\nError Reduction: Minimizes coding errors associated with manual constraint setup.\n\n\n\n\n\nComplexity in Setup: Initial setup of data tables and integration into the Godot project might be complex.\nPerformance Concerns: Reading from data tables at runtime could impact performance if not properly optimized.\n\n\n\n\nAn alternative could have been to develop a visual editor for constraints within Godot, but this would require significantly more development resources and may not offer the same flexibility as a data-driven approach.\n\n\n\nFor projects where constraints are minimal or highly static, this system might introduce unnecessary complexity and overhead.\n\n\n\nThis feature should be developed and maintained by the core V-Sekai team to ensure it aligns with the overall architecture and performance standards of the engine.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20211005-solve-mocap-by-connecting-mediapipe-to-blender.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20211005-solve-mocap-by-connecting-mediapipe-to-blender.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Solve Mocap By Connecting Mediapipe to Blender",
+    "objectID": "decisions/20241028-use-data-tables-for-godot-constraints.html#the-context",
+    "href": "decisions/20241028-use-data-tables-for-godot-constraints.html#the-context",
+    "title": "Proposal: Use Data Tables for Godot Constraints",
     "section": "",
-    "text": "Is there a reason why this should be core and done by us?"
+    "text": "In the development of VR applications using the Godot Engine, managing complex interactions and constraints can become cumbersome and error-prone when handled purely through code."
   },
   {
-    "objectID": "decisions/20211005-solve-mocap-by-connecting-mediapipe-to-blender.html#references",
-    "href": "decisions/20211005-solve-mocap-by-connecting-mediapipe-to-blender.html#references",
-    "title": "Proposed: Solve Mocap By Connecting Mediapipe to Blender",
+    "objectID": "decisions/20241028-use-data-tables-for-godot-constraints.html#the-problem-statement",
+    "href": "decisions/20241028-use-data-tables-for-godot-constraints.html#the-problem-statement",
+    "title": "Proposal: Use Data Tables for Godot Constraints",
     "section": "",
-    "text": "From Kendrick\n\nmedia_pipe_demo.zip\nhttps://github.com/V-Sekai/game-tools-V-Sekai"
+    "text": "Currently, developers must manually code each constraint and interaction within the Godot Engine, which is time-consuming and increases the risk of errors. This approach lacks scalability and efficiency, particularly in large-scale VR projects like those developed by V-Sekai."
   },
   {
-    "objectID": "decisions/20211005-solve-mocap-by-connecting-mediapipe-to-blender.html#derivative-license",
-    "href": "decisions/20211005-solve-mocap-by-connecting-mediapipe-to-blender.html#derivative-license",
-    "title": "Proposed: Solve Mocap By Connecting Mediapipe to Blender",
+    "objectID": "decisions/20241028-use-data-tables-for-godot-constraints.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20241028-use-data-tables-for-godot-constraints.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposal: Use Data Tables for Godot Constraints",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "The proposal involves integrating a data table system within the Godot Engine to manage constraints. Here’s a basic example of how it might look in pseudo-code:"
   },
   {
-    "objectID": "decisions/20210523-distribute-trusted-clients-with-notary.html",
-    "href": "decisions/20210523-distribute-trusted-clients-with-notary.html",
-    "title": "Proposed: Distribute trusted clients with notary",
+    "objectID": "decisions/20241028-use-data-tables-for-godot-constraints.html#the-benefits",
+    "href": "decisions/20241028-use-data-tables-for-godot-constraints.html#the-benefits",
+    "title": "Proposal: Use Data Tables for Godot Constraints",
     "section": "",
-    "text": "We use itch.io distribute our software clients.\n\nSecurity concerns with trust. We do not control hosting.\nWant ability to mirror package sources.\nResearch use to distribute avatars and worlds\nWant something off the shelf\n\n\n\n\nUse the notary system so we can establish trust.\n\n\nWe distribute the notary updater and make it fetch the launcher and V-Sekai.\nWe provide a notary server.\nWe setup the #trust relationship during the install and maintenance.\n\n\n\n\nCode reviewed and trusted by large corporations (Docker Images) and in safety critial fields (Automobiles)\nOff the shelf\n\n\n\n\n\nUnknown support costs\n\n\n\n\n\nSteam provides a distribution network and marketplace.\nList the reasons for the rejection: (the Bad traits)\n\nThird party #trust\n\n\n\n\nItch.io provides a distribution network and marketplace.\nList the reasons for the rejection: (the Bad traits)\n\nThird party #trust\n\n\n\n\nNot trivial. The documentation of Notary start by the description of a possible security model and provides several attacks against it.\n\n\n\nFrom a security standpoint, we need to ensure that there is a #trust between the software we send and the client supply chain to get it.\n\n\n\n\nhttps://github.com/kolide/updater\nhttps://github.com/theupdateframework/notary\nhttps://github.com/theupdateframework/specification/blob/master/tuf-spec.md\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Scalability: Easier to manage large numbers of constraints.\nEfficiency: Reduces development time by allowing non-programmers to adjust constraints.\nError Reduction: Minimizes coding errors associated with manual constraint setup."
   },
   {
-    "objectID": "decisions/20210523-distribute-trusted-clients-with-notary.html#context-and-problem-statement",
-    "href": "decisions/20210523-distribute-trusted-clients-with-notary.html#context-and-problem-statement",
-    "title": "Proposed: Distribute trusted clients with notary",
+    "objectID": "decisions/20241028-use-data-tables-for-godot-constraints.html#the-downsides",
+    "href": "decisions/20241028-use-data-tables-for-godot-constraints.html#the-downsides",
+    "title": "Proposal: Use Data Tables for Godot Constraints",
     "section": "",
-    "text": "We use itch.io distribute our software clients.\n\nSecurity concerns with trust. We do not control hosting.\nWant ability to mirror package sources.\nResearch use to distribute avatars and worlds\nWant something off the shelf"
+    "text": "Complexity in Setup: Initial setup of data tables and integration into the Godot project might be complex.\nPerformance Concerns: Reading from data tables at runtime could impact performance if not properly optimized."
   },
   {
-    "objectID": "decisions/20210523-distribute-trusted-clients-with-notary.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20210523-distribute-trusted-clients-with-notary.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: Distribute trusted clients with notary",
+    "objectID": "decisions/20241028-use-data-tables-for-godot-constraints.html#the-road-not-taken",
+    "href": "decisions/20241028-use-data-tables-for-godot-constraints.html#the-road-not-taken",
+    "title": "Proposal: Use Data Tables for Godot Constraints",
     "section": "",
-    "text": "Use the notary system so we can establish trust.\n\n\nWe distribute the notary updater and make it fetch the launcher and V-Sekai.\nWe provide a notary server.\nWe setup the #trust relationship during the install and maintenance.\n\n\n\n\nCode reviewed and trusted by large corporations (Docker Images) and in safety critial fields (Automobiles)\nOff the shelf\n\n\n\n\n\nUnknown support costs"
+    "text": "An alternative could have been to develop a visual editor for constraints within Godot, but this would require significantly more development resources and may not offer the same flexibility as a data-driven approach."
   },
   {
-    "objectID": "decisions/20210523-distribute-trusted-clients-with-notary.html#option-graveyard-steam-only",
-    "href": "decisions/20210523-distribute-trusted-clients-with-notary.html#option-graveyard-steam-only",
-    "title": "Proposed: Distribute trusted clients with notary",
+    "objectID": "decisions/20241028-use-data-tables-for-godot-constraints.html#the-infrequent-use-case",
+    "href": "decisions/20241028-use-data-tables-for-godot-constraints.html#the-infrequent-use-case",
+    "title": "Proposal: Use Data Tables for Godot Constraints",
     "section": "",
-    "text": "Steam provides a distribution network and marketplace.\nList the reasons for the rejection: (the Bad traits)\n\nThird party #trust"
+    "text": "For projects where constraints are minimal or highly static, this system might introduce unnecessary complexity and overhead."
   },
   {
-    "objectID": "decisions/20210523-distribute-trusted-clients-with-notary.html#option-graveyard-itch.io-only",
-    "href": "decisions/20210523-distribute-trusted-clients-with-notary.html#option-graveyard-itch.io-only",
-    "title": "Proposed: Distribute trusted clients with notary",
+    "objectID": "decisions/20241028-use-data-tables-for-godot-constraints.html#in-core-and-done-by-us",
+    "href": "decisions/20241028-use-data-tables-for-godot-constraints.html#in-core-and-done-by-us",
+    "title": "Proposal: Use Data Tables for Godot Constraints",
     "section": "",
-    "text": "Itch.io provides a distribution network and marketplace.\nList the reasons for the rejection: (the Bad traits)\n\nThird party #trust"
+    "text": "This feature should be developed and maintained by the core V-Sekai team to ensure it aligns with the overall architecture and performance standards of the engine."
   },
   {
-    "objectID": "decisions/20210523-distribute-trusted-clients-with-notary.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20210523-distribute-trusted-clients-with-notary.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Distribute trusted clients with notary",
+    "objectID": "decisions/20241028-use-data-tables-for-godot-constraints.html#status",
+    "href": "decisions/20241028-use-data-tables-for-godot-constraints.html#status",
+    "title": "Proposal: Use Data Tables for Godot Constraints",
     "section": "",
-    "text": "Not trivial. The documentation of Notary start by the description of a possible security model and provides several attacks against it."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20210523-distribute-trusted-clients-with-notary.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20210523-distribute-trusted-clients-with-notary.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Distribute trusted clients with notary",
+    "objectID": "decisions/20241028-use-data-tables-for-godot-constraints.html#decision-makers",
+    "href": "decisions/20241028-use-data-tables-for-godot-constraints.html#decision-makers",
+    "title": "Proposal: Use Data Tables for Godot Constraints",
     "section": "",
-    "text": "From a security standpoint, we need to ensure that there is a #trust between the software we send and the client supply chain to get it."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20210523-distribute-trusted-clients-with-notary.html#references",
-    "href": "decisions/20210523-distribute-trusted-clients-with-notary.html#references",
-    "title": "Proposed: Distribute trusted clients with notary",
+    "objectID": "decisions/20241028-use-data-tables-for-godot-constraints.html#tags",
+    "href": "decisions/20241028-use-data-tables-for-godot-constraints.html#tags",
+    "title": "Proposal: Use Data Tables for Godot Constraints",
     "section": "",
-    "text": "https://github.com/kolide/updater\nhttps://github.com/theupdateframework/notary\nhttps://github.com/theupdateframework/specification/blob/master/tuf-spec.md"
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20210523-distribute-trusted-clients-with-notary.html#derivative-license",
-    "href": "decisions/20210523-distribute-trusted-clients-with-notary.html#derivative-license",
-    "title": "Proposed: Distribute trusted clients with notary",
+    "objectID": "decisions/20241028-use-data-tables-for-godot-constraints.html#further-reading",
+    "href": "decisions/20241028-use-data-tables-for-godot-constraints.html#further-reading",
+    "title": "Proposal: Use Data Tables for Godot Constraints",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240627-gdextension-as-libriscv.html",
-    "href": "decisions/20240627-gdextension-as-libriscv.html",
-    "title": "Superceded: RISCV Binaries as Shared Libraries",
+    "objectID": "decisions/20231230-spatiallabs-openvr.html",
+    "href": "decisions/20231230-spatiallabs-openvr.html",
+    "title": "Deprecated: Valid configuration of Spatiallabs and Openxr",
     "section": "",
-    "text": "In the current development landscape, there is a growing need for more efficient and flexible ways to handle gdextension binaries. This proposal was inspired by a conversation between Fire and ホロ on June 27, 2024.\nWe also want to investigate players distributing riscv binaries as user generated scripts inside of godot scenes.\n\n\n\nTraditionally we have to compile gdextension for like 5-10 platform variants which is inefficient.\n\n\n\nFire proposed an idea where many gdextension modules can be compiled as RISCV binaries.\nFunctioning like shared libraries via librisc emulation both as an intepreter or a register machine.\nThis could potentially allow wrapping up the entire gdextension API.\nHere’s an example of how function calls into the guest VM could work:\n// See further reading section.\n// Host:\nint ret = machine.vmcall(\"test\", 111, 222, \"333\");\nprintf(\"test returned %d\\n\", ret);\n\n// Guest:\nextern \"C\" __attribute__((used, retain))\nint test(int a, int b, const char* c) {\n    return a + b;\n}\nThis approach would make arbitrary function calls into the VM guest possible. The functions must be C ABI, and if you use the string name, the function must be in the symbol table.\nThis can also be a future approach into compiling gdscript bytecode as more performant code via string templating the bytecode as c and compiling it, but that is reserved for future work.\n\n\n\n\nIncreased efficiency and flexibility in handling RISCV binaries.\nPotential to wrap the entire gdextension API.\nMore convenient and capable of doing things that can’t be done in gdscript.\nCan also be built as a gdextension.\n\n\n\n\n\nRequires significant changes to the existing system.\nMay introduce new complexities and potential security risks.\n\n\n\n\n\nExploring other methods of improving flexibility of loading binaries - like wasm.\nHolo has given me an implementation of riscv processors in godot engine via zig language.\n\n\n\n\n\nThis proposal may not be beneficial for small-scale projects or those that do not require high levels of efficiency and flexibility in handling RISCV binaries.\n\n\n\n\n\nThis proposal will be implemented by the V-Sekai development team, with potential contributions from the wider open-source community.\n\n\n\n\nStatus: Superseded by Build a tiny RISC virtual machine which can interpret and execute GDExtensions\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nlibriscv VM Call Documentation - Detailed documentation on making function calls into the VM guest.\n[https://c9x.me/compile/]\n[https://github.com/Vahera/godot-orchestrator]\n\nAI assistant Aria assisted with this article."
+    "text": "Status: Deprecated\nDeciders: V-Sekai\nTags: V-Sekai, fixed\n\n\n\n\nThis proposal aims to define a valid configuration of OpenVR and SpatialLabs display.\n\n\n\nThe main challenge is to display Unity applications like SteamVR home and others.\n\n\n\nTo overcome the challenge, use these exact versions:\n\nSpatialLabs EC PRO_Acer_1.2.288_Win11x64\nAcer SteamVR Bridge.Installer.1.00.1001\n\n\n\n\nBy using these specific versions, we can avoid the latest update that causes the screen to be black. This ensures a seamless experience for users.\n\n\n\nThe downside of this approach is that we are losing out on the latest updates and improvements that come with them.\n\n\n\nAn alternative approach could have been to use a different product like the Looking Glass Factory, but they don’t support openxr.\n\n\n\nAnother infrequent use case could be only flat desktop.\n\n\n\nI have access to equipment and it’s not easy to get access. This means that the implementation and testing of this proposal will be done by us.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240627-gdextension-as-libriscv.html#the-context",
-    "href": "decisions/20240627-gdextension-as-libriscv.html#the-context",
-    "title": "Superceded: RISCV Binaries as Shared Libraries",
+    "objectID": "decisions/20231230-spatiallabs-openvr.html#metadata",
+    "href": "decisions/20231230-spatiallabs-openvr.html#metadata",
+    "title": "Deprecated: Valid configuration of Spatiallabs and Openxr",
     "section": "",
-    "text": "In the current development landscape, there is a growing need for more efficient and flexible ways to handle gdextension binaries. This proposal was inspired by a conversation between Fire and ホロ on June 27, 2024.\nWe also want to investigate players distributing riscv binaries as user generated scripts inside of godot scenes."
+    "text": "Status: Deprecated\nDeciders: V-Sekai\nTags: V-Sekai, fixed"
   },
   {
-    "objectID": "decisions/20240627-gdextension-as-libriscv.html#the-problem-statement",
-    "href": "decisions/20240627-gdextension-as-libriscv.html#the-problem-statement",
-    "title": "Superceded: RISCV Binaries as Shared Libraries",
+    "objectID": "decisions/20231230-spatiallabs-openvr.html#the-backdrop",
+    "href": "decisions/20231230-spatiallabs-openvr.html#the-backdrop",
+    "title": "Deprecated: Valid configuration of Spatiallabs and Openxr",
     "section": "",
-    "text": "Traditionally we have to compile gdextension for like 5-10 platform variants which is inefficient."
+    "text": "This proposal aims to define a valid configuration of OpenVR and SpatialLabs display."
   },
   {
-    "objectID": "decisions/20240627-gdextension-as-libriscv.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240627-gdextension-as-libriscv.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Superceded: RISCV Binaries as Shared Libraries",
+    "objectID": "decisions/20231230-spatiallabs-openvr.html#the-challenge",
+    "href": "decisions/20231230-spatiallabs-openvr.html#the-challenge",
+    "title": "Deprecated: Valid configuration of Spatiallabs and Openxr",
     "section": "",
-    "text": "Fire proposed an idea where many gdextension modules can be compiled as RISCV binaries.\nFunctioning like shared libraries via librisc emulation both as an intepreter or a register machine.\nThis could potentially allow wrapping up the entire gdextension API.\nHere’s an example of how function calls into the guest VM could work:\n// See further reading section.\n// Host:\nint ret = machine.vmcall(\"test\", 111, 222, \"333\");\nprintf(\"test returned %d\\n\", ret);\n\n// Guest:\nextern \"C\" __attribute__((used, retain))\nint test(int a, int b, const char* c) {\n    return a + b;\n}\nThis approach would make arbitrary function calls into the VM guest possible. The functions must be C ABI, and if you use the string name, the function must be in the symbol table.\nThis can also be a future approach into compiling gdscript bytecode as more performant code via string templating the bytecode as c and compiling it, but that is reserved for future work."
+    "text": "The main challenge is to display Unity applications like SteamVR home and others."
   },
   {
-    "objectID": "decisions/20240627-gdextension-as-libriscv.html#the-benefits",
-    "href": "decisions/20240627-gdextension-as-libriscv.html#the-benefits",
-    "title": "Superceded: RISCV Binaries as Shared Libraries",
+    "objectID": "decisions/20231230-spatiallabs-openvr.html#the-strategy",
+    "href": "decisions/20231230-spatiallabs-openvr.html#the-strategy",
+    "title": "Deprecated: Valid configuration of Spatiallabs and Openxr",
     "section": "",
-    "text": "Increased efficiency and flexibility in handling RISCV binaries.\nPotential to wrap the entire gdextension API.\nMore convenient and capable of doing things that can’t be done in gdscript.\nCan also be built as a gdextension."
+    "text": "To overcome the challenge, use these exact versions:\n\nSpatialLabs EC PRO_Acer_1.2.288_Win11x64\nAcer SteamVR Bridge.Installer.1.00.1001"
   },
   {
-    "objectID": "decisions/20240627-gdextension-as-libriscv.html#the-downsides",
-    "href": "decisions/20240627-gdextension-as-libriscv.html#the-downsides",
-    "title": "Superceded: RISCV Binaries as Shared Libraries",
+    "objectID": "decisions/20231230-spatiallabs-openvr.html#the-upside",
+    "href": "decisions/20231230-spatiallabs-openvr.html#the-upside",
+    "title": "Deprecated: Valid configuration of Spatiallabs and Openxr",
     "section": "",
-    "text": "Requires significant changes to the existing system.\nMay introduce new complexities and potential security risks."
+    "text": "By using these specific versions, we can avoid the latest update that causes the screen to be black. This ensures a seamless experience for users."
   },
   {
-    "objectID": "decisions/20240627-gdextension-as-libriscv.html#the-road-not-taken",
-    "href": "decisions/20240627-gdextension-as-libriscv.html#the-road-not-taken",
-    "title": "Superceded: RISCV Binaries as Shared Libraries",
+    "objectID": "decisions/20231230-spatiallabs-openvr.html#the-downside",
+    "href": "decisions/20231230-spatiallabs-openvr.html#the-downside",
+    "title": "Deprecated: Valid configuration of Spatiallabs and Openxr",
     "section": "",
-    "text": "Exploring other methods of improving flexibility of loading binaries - like wasm.\nHolo has given me an implementation of riscv processors in godot engine via zig language."
+    "text": "The downside of this approach is that we are losing out on the latest updates and improvements that come with them."
   },
   {
-    "objectID": "decisions/20240627-gdextension-as-libriscv.html#the-infrequent-use-case",
-    "href": "decisions/20240627-gdextension-as-libriscv.html#the-infrequent-use-case",
-    "title": "Superceded: RISCV Binaries as Shared Libraries",
+    "objectID": "decisions/20231230-spatiallabs-openvr.html#the-road-not-taken",
+    "href": "decisions/20231230-spatiallabs-openvr.html#the-road-not-taken",
+    "title": "Deprecated: Valid configuration of Spatiallabs and Openxr",
     "section": "",
-    "text": "This proposal may not be beneficial for small-scale projects or those that do not require high levels of efficiency and flexibility in handling RISCV binaries."
+    "text": "An alternative approach could have been to use a different product like the Looking Glass Factory, but they don’t support openxr."
   },
   {
-    "objectID": "decisions/20240627-gdextension-as-libriscv.html#in-core-and-done-by-us",
-    "href": "decisions/20240627-gdextension-as-libriscv.html#in-core-and-done-by-us",
-    "title": "Superceded: RISCV Binaries as Shared Libraries",
+    "objectID": "decisions/20231230-spatiallabs-openvr.html#the-infrequent-use-case",
+    "href": "decisions/20231230-spatiallabs-openvr.html#the-infrequent-use-case",
+    "title": "Deprecated: Valid configuration of Spatiallabs and Openxr",
     "section": "",
-    "text": "This proposal will be implemented by the V-Sekai development team, with potential contributions from the wider open-source community."
+    "text": "Another infrequent use case could be only flat desktop."
   },
   {
-    "objectID": "decisions/20240627-gdextension-as-libriscv.html#status",
-    "href": "decisions/20240627-gdextension-as-libriscv.html#status",
-    "title": "Superceded: RISCV Binaries as Shared Libraries",
+    "objectID": "decisions/20231230-spatiallabs-openvr.html#in-core-and-done-by-us",
+    "href": "decisions/20231230-spatiallabs-openvr.html#in-core-and-done-by-us",
+    "title": "Deprecated: Valid configuration of Spatiallabs and Openxr",
     "section": "",
-    "text": "Status: Superseded by Build a tiny RISC virtual machine which can interpret and execute GDExtensions"
+    "text": "I have access to equipment and it’s not easy to get access. This means that the implementation and testing of this proposal will be done by us."
   },
   {
-    "objectID": "decisions/20240627-gdextension-as-libriscv.html#decision-makers",
-    "href": "decisions/20240627-gdextension-as-libriscv.html#decision-makers",
-    "title": "Superceded: RISCV Binaries as Shared Libraries",
+    "objectID": "decisions/20231230-spatiallabs-openvr.html#further-reading",
+    "href": "decisions/20231230-spatiallabs-openvr.html#further-reading",
+    "title": "Deprecated: Valid configuration of Spatiallabs and Openxr",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240627-gdextension-as-libriscv.html#tags",
-    "href": "decisions/20240627-gdextension-as-libriscv.html#tags",
-    "title": "Superceded: RISCV Binaries as Shared Libraries",
+    "objectID": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html",
+    "href": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html",
+    "title": "Superseded: Planning V-Sekai on 2022-02-21 Superseded",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Status: superseded \nDeciders: V-Sekai,ifire,lyuma,\nTags: V-Sekai,\n\n\n\nSuperseded - See https://github.com/V-Sekai/V-Sekai/blob/master/decisions/20220224-v-sekai-version-two-plan.md\nKnow where we’re going by describing what we want.\n\n\n\nProposed mission and a list of tasks.\n\n\n\n\n\n\nGodot Engine pull requests.\n\n\n\n\n\nOne gitlab repo with source assets? (sky celebration and sponza).\n\n\nThe ability to upload maps and avatars standalone via a SDK (set of submodules?) https://github.com/V-Sekai/vsk_sdk.\n\nBeing able to enter a vsk map ∀ maps (mvp = 1 map).\nEnter a vsk map with an entity in it (upload sky celebration OR upload sponza with one beachball).\n\nVSK_map source asset repositories\nLyuma will make a new github repo V-Sekai/vrm_submodule - we need a script for updating all submodules to the latest on a given branch.\nVSK_map source asset repositories\nI think vsk_sdk should only be submodules, no assets.\nWe can git rebase -i to remove the binary assets from it.\ngit merge to install the vsk_sdk into another project (such as gitlab). we need to look if git subtree supports .gitmodules and we can use it if it does.\nmake vsk_sdk the head for all of the sdk related submodules. do our development there and commit submodules regularly.\nIn groups project, pretend we delete all submodules in vsk_sdk. Then git merge vsk_sdk/main to bring in the submodules from that repo.\nEvery time we update vsk_sdk, do a git merge into groups and our source asset repo with sponza etc.\nVSK_map source asset repositories\n\nDon’t save .scn assets in git.\n\nno GLB.\nblend files ~10MB ok. &gt; 100MB let’s either use GitLab LFS or something else.\nEvaluate https://dvc.org/\n\n\n\n\nBeing able to have our group of people join and communicate. (godot speech).\n\n\nPorting C++ was discussed as a way forward to make it easier to debug\n\n\nVR support (openxr).\nInteracting with objects in desktop mode is important so that we can test easier.\nInteracting with objects in vr.\nScripting (wasgo).\nNetwork server to support 1000.\n\n\n\n\n\nGain clarity of mission.\n\n\n\n\nThe cost of overhead.\n\n\n\n\n\nOption: Status quo. \nRejection Reason: Complete the wrong thing. \n\n\n\n\nThis is a planning document.\n\n\n\nWe know what we want to do.\n\n\n\n\nNone\n\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240627-gdextension-as-libriscv.html#further-reading",
-    "href": "decisions/20240627-gdextension-as-libriscv.html#further-reading",
-    "title": "Superceded: RISCV Binaries as Shared Libraries",
+    "objectID": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html#context-and-problem-statement",
+    "href": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html#context-and-problem-statement",
+    "title": "Superseded: Planning V-Sekai on 2022-02-21 Superseded",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nlibriscv VM Call Documentation - Detailed documentation on making function calls into the VM guest.\n[https://c9x.me/compile/]\n[https://github.com/Vahera/godot-orchestrator]\n\nAI assistant Aria assisted with this article."
+    "text": "Superseded - See https://github.com/V-Sekai/V-Sekai/blob/master/decisions/20220224-v-sekai-version-two-plan.md\nKnow where we’re going by describing what we want."
   },
   {
-    "objectID": "decisions/20230505-cross-platform-artwork-distribution.html",
-    "href": "decisions/20230505-cross-platform-artwork-distribution.html",
-    "title": "Proposed: Enhancing Cross-Platform Compatibility and User Experience for V-Sekai VR Social Players",
+    "objectID": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Superseded: Planning V-Sekai on 2022-02-21 Superseded",
     "section": "",
-    "text": "Status: proposed \nDeciders: V-Sekai, fire\nTags: V-Sekai, ChatGPT-4\n\n\n\n\nV-Sekai faces limitations in providing a seamless cross-platform experience for VR Social players. How can we improve compatibility and user experience across various platforms?\n\n\n\nDistribute artwork in Blend, VRM, and Unity Asset Package formats to ensure easy portability and compatibility with multiple platforms, enhancing the overall user experience.\n\n\n\n\nCreate and export artwork in Blend, VRM, and Unity Asset Package formats.\nUtilize appropriate formats for each platform, ensuring compatibility and optimal performance.\n\n\n\n\n\nImproved compatibility across various platforms.\nEnhanced user experience for VR Social players.\nIncreased adoption of V-Sekai due to better cross-platform support.\n\n\n\n\n\nAdditional development time and resources required to create and maintain multiple asset formats.\nPotential performance issues on lower-end devices.\n\n\n\n\n\nCreating separate assets and configurations for each platform, increasing development time and maintenance complexity.\n\n\n\n\nThis enhancement aims to improve the core experience for users across various platforms and cannot be achieved with a simple workaround.\n\n\n\nProviding a seamless cross-platform experience is essential for V-Sekai’s success. Implementing this feature in-house ensures full control over its development and tailoring to specific needs.\n\n\n\n\nV-Sekai\nUnityVRM: https://github.com/vrm-c/UniVRM\nSilent Cel Shading Shader for Unity Game Engine: https://gitlab.com/s-ilent/SCSS\nSilent Cel Shading Shader for Godot Engine: https://github.com/lyuma/SCSS-Godot"
+    "text": "Proposed mission and a list of tasks."
   },
   {
-    "objectID": "decisions/20230505-cross-platform-artwork-distribution.html#metadata",
-    "href": "decisions/20230505-cross-platform-artwork-distribution.html#metadata",
-    "title": "Proposed: Enhancing Cross-Platform Compatibility and User Experience for V-Sekai VR Social Players",
+    "objectID": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Superseded: Planning V-Sekai on 2022-02-21 Superseded",
     "section": "",
-    "text": "Status: proposed \nDeciders: V-Sekai, fire\nTags: V-Sekai, ChatGPT-4"
+    "text": "Godot Engine pull requests.\n\n\n\n\n\nOne gitlab repo with source assets? (sky celebration and sponza).\n\n\nThe ability to upload maps and avatars standalone via a SDK (set of submodules?) https://github.com/V-Sekai/vsk_sdk.\n\nBeing able to enter a vsk map ∀ maps (mvp = 1 map).\nEnter a vsk map with an entity in it (upload sky celebration OR upload sponza with one beachball).\n\nVSK_map source asset repositories\nLyuma will make a new github repo V-Sekai/vrm_submodule - we need a script for updating all submodules to the latest on a given branch.\nVSK_map source asset repositories\nI think vsk_sdk should only be submodules, no assets.\nWe can git rebase -i to remove the binary assets from it.\ngit merge to install the vsk_sdk into another project (such as gitlab). we need to look if git subtree supports .gitmodules and we can use it if it does.\nmake vsk_sdk the head for all of the sdk related submodules. do our development there and commit submodules regularly.\nIn groups project, pretend we delete all submodules in vsk_sdk. Then git merge vsk_sdk/main to bring in the submodules from that repo.\nEvery time we update vsk_sdk, do a git merge into groups and our source asset repo with sponza etc.\nVSK_map source asset repositories\n\nDon’t save .scn assets in git.\n\nno GLB.\nblend files ~10MB ok. &gt; 100MB let’s either use GitLab LFS or something else.\nEvaluate https://dvc.org/\n\n\n\n\nBeing able to have our group of people join and communicate. (godot speech).\n\n\nPorting C++ was discussed as a way forward to make it easier to debug\n\n\nVR support (openxr).\nInteracting with objects in desktop mode is important so that we can test easier.\nInteracting with objects in vr.\nScripting (wasgo).\nNetwork server to support 1000."
   },
   {
-    "objectID": "decisions/20230505-cross-platform-artwork-distribution.html#context-and-problem-statement",
-    "href": "decisions/20230505-cross-platform-artwork-distribution.html#context-and-problem-statement",
-    "title": "Proposed: Enhancing Cross-Platform Compatibility and User Experience for V-Sekai VR Social Players",
+    "objectID": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html#positive-consequences",
+    "href": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html#positive-consequences",
+    "title": "Superseded: Planning V-Sekai on 2022-02-21 Superseded",
     "section": "",
-    "text": "V-Sekai faces limitations in providing a seamless cross-platform experience for VR Social players. How can we improve compatibility and user experience across various platforms?"
+    "text": "Gain clarity of mission."
   },
   {
-    "objectID": "decisions/20230505-cross-platform-artwork-distribution.html#proposed-solution",
-    "href": "decisions/20230505-cross-platform-artwork-distribution.html#proposed-solution",
-    "title": "Proposed: Enhancing Cross-Platform Compatibility and User Experience for V-Sekai VR Social Players",
+    "objectID": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html#negative-consequences",
+    "href": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html#negative-consequences",
+    "title": "Superseded: Planning V-Sekai on 2022-02-21 Superseded",
     "section": "",
-    "text": "Distribute artwork in Blend, VRM, and Unity Asset Package formats to ensure easy portability and compatibility with multiple platforms, enhancing the overall user experience."
+    "text": "The cost of overhead."
   },
   {
-    "objectID": "decisions/20230505-cross-platform-artwork-distribution.html#implementation",
-    "href": "decisions/20230505-cross-platform-artwork-distribution.html#implementation",
-    "title": "Proposed: Enhancing Cross-Platform Compatibility and User Experience for V-Sekai VR Social Players",
+    "objectID": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html#option-graveyard",
+    "href": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html#option-graveyard",
+    "title": "Superseded: Planning V-Sekai on 2022-02-21 Superseded",
     "section": "",
-    "text": "Create and export artwork in Blend, VRM, and Unity Asset Package formats.\nUtilize appropriate formats for each platform, ensuring compatibility and optimal performance."
+    "text": "Option: Status quo. \nRejection Reason: Complete the wrong thing."
   },
   {
-    "objectID": "decisions/20230505-cross-platform-artwork-distribution.html#positive-consequences",
-    "href": "decisions/20230505-cross-platform-artwork-distribution.html#positive-consequences",
-    "title": "Proposed: Enhancing Cross-Platform Compatibility and User Experience for V-Sekai VR Social Players",
+    "objectID": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Superseded: Planning V-Sekai on 2022-02-21 Superseded",
     "section": "",
-    "text": "Improved compatibility across various platforms.\nEnhanced user experience for VR Social players.\nIncreased adoption of V-Sekai due to better cross-platform support."
+    "text": "This is a planning document."
   },
   {
-    "objectID": "decisions/20230505-cross-platform-artwork-distribution.html#negative-consequences",
-    "href": "decisions/20230505-cross-platform-artwork-distribution.html#negative-consequences",
-    "title": "Proposed: Enhancing Cross-Platform Compatibility and User Experience for V-Sekai VR Social Players",
+    "objectID": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Superseded: Planning V-Sekai on 2022-02-21 Superseded",
     "section": "",
-    "text": "Additional development time and resources required to create and maintain multiple asset formats.\nPotential performance issues on lower-end devices."
+    "text": "We know what we want to do."
   },
   {
-    "objectID": "decisions/20230505-cross-platform-artwork-distribution.html#option-graveyard",
-    "href": "decisions/20230505-cross-platform-artwork-distribution.html#option-graveyard",
-    "title": "Proposed: Enhancing Cross-Platform Compatibility and User Experience for V-Sekai VR Social Players",
+    "objectID": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html#references",
+    "href": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html#references",
+    "title": "Superseded: Planning V-Sekai on 2022-02-21 Superseded",
     "section": "",
-    "text": "Creating separate assets and configurations for each platform, increasing development time and maintenance complexity."
+    "text": "None"
   },
   {
-    "objectID": "decisions/20230505-cross-platform-artwork-distribution.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230505-cross-platform-artwork-distribution.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Enhancing Cross-Platform Compatibility and User Experience for V-Sekai VR Social Players",
+    "objectID": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html#derivative-license",
+    "href": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html#derivative-license",
+    "title": "Superseded: Planning V-Sekai on 2022-02-21 Superseded",
     "section": "",
-    "text": "This enhancement aims to improve the core experience for users across various platforms and cannot be achieved with a simple workaround."
+    "text": "Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230505-cross-platform-artwork-distribution.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230505-cross-platform-artwork-distribution.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Enhancing Cross-Platform Compatibility and User Experience for V-Sekai VR Social Players",
+    "objectID": "decisions/20211031-standard-backup-procedures.html",
+    "href": "decisions/20211031-standard-backup-procedures.html",
+    "title": "Proposed: Standard backup procedures",
     "section": "",
-    "text": "Providing a seamless cross-platform experience is essential for V-Sekai’s success. Implementing this feature in-house ensures full control over its development and tailoring to specific needs."
+    "text": "Proposed: Standard backup procedures\n\nContext and Problem Statement\nThings that aren’t backed up get lost.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nBackup V-Sekai Github organization with V-Sekai-gitm and V-Sekai-github-backup.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nUse https://github.com/muhasturk/gitim to backup V-sekai. (tested 7b6e898b7587f61b0c5f00c3ab9862868f94479d )\ngit clone https://github.com/muhasturk/gitim.git\ncd gitim\npip install .\ncd -\nexport ACCESS_TOKEN=AAAA\npython3 -m gitim -o V-Sekai -d V-Sekai-godot-gitm-`date --iso=date --utc` --ssh --token $ACCESS_TOKEN\nUse https://github.com/josegonzalez/python-github-backup to backup. (tested 0.40.0)\npip install github-backup\nexport ACCESS_TOKEN=AAAA\ngithub-backup V-Sekai --token $ACCESS_TOKEN --organization --output-directory V-Sekai-Backup-`date --iso=date --utc` --incremental --prefer-ssh --lfs --private --fork --private --all\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot able to.\n\n\nPositive Consequences\n\nTwo backups combined should cover all cases\n\n\n\nNegative Consequences\n\ngithub-backup doesn’t backup repos that are accessible in the dependencies\ngitm doesn’t backup issues\n\n\n\nIs there a reason why this should be core and done by us?\nOnly we have access to a complete copy of the repo.\n\n\nReferences\n\nhttps://github.com/josegonzalez/python-github-backup\nhttps://github.com/muhasturk/gitim\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230505-cross-platform-artwork-distribution.html#references",
-    "href": "decisions/20230505-cross-platform-artwork-distribution.html#references",
-    "title": "Proposed: Enhancing Cross-Platform Compatibility and User Experience for V-Sekai VR Social Players",
+    "objectID": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html",
+    "href": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html",
+    "title": "Accepted: PCI-E Lane Depletion and Thunderbolt 4 Issues",
     "section": "",
-    "text": "V-Sekai\nUnityVRM: https://github.com/vrm-c/UniVRM\nSilent Cel Shading Shader for Unity Game Engine: https://gitlab.com/s-ilent/SCSS\nSilent Cel Shading Shader for Godot Engine: https://github.com/lyuma/SCSS-Godot"
+    "text": "In modern computing, PCI-E lanes are a critical resource for connecting various high-speed components such as GPUs, SSDs, and network cards. However, the number of available PCI-E lanes is finite and can become a bottleneck when multiple high-bandwidth devices are connected. This proposal addresses the issue of PCI-E lane depletion, particularly in systems utilizing Thunderbolt 4.\n\n\n\nWhen all PCI-E slots are utilized, especially with high-bandwidth devices like GPUs and Thunderbolt 4 controllers, users may experience performance degradation or device malfunctions due to insufficient PCI-E lanes. This problem was highlighted by a user who reported that their Thunderbolt 4 connection broke after using their last PCI-E slot.\n\n\n\nTo mitigate this issue, it is recommended to keep the last PCI-E slot empty to ensure sufficient lanes for all connected devices.\n+-------------------+\n|   CPU             |\n|                   |\n| PCI-E Lanes    |\n+---------+---------+\n          |\n          v\n+---------+---------+\n|       PCI-E       |\n|      Switch       |\n+---------+---------+\n          |\n          v\n+---------+---------+---------+---------+\n|   GPU   | Thunderbolt 4 |  NVMe SSD  |\n|     |           |        |\n+---------+---------+---------+---------+\n\n\n\n\nImproved System Stability: Ensuring sufficient PCI-E lanes for all devices will prevent system crashes and performance issues.\nOptimized Resource Allocation: Users can make informed decisions about which devices to prioritize based on available PCI-E lanes.\nEnhanced User Experience: By avoiding unexpected device failures, users will have a more reliable and predictable computing experience.\n\n\n\n\n\nComplexity: Implementing checks for PCI-E lane availability adds complexity to system configuration and management.\nHardware Limitations: Users with limited PCI-E lanes may need to upgrade their hardware to fully utilize all desired devices.\n\n\n\n\nAn alternative approach could be to develop software solutions that dynamically manage PCI-E lane allocation based on real-time usage patterns. However, this would require significant changes to both hardware and software architectures and may not be feasible for all users.\n\n\n\nIn scenarios where users only utilize a single high-bandwidth device, such as a GPU, PCI-E lane depletion is unlikely to be an issue. This proposal primarily targets power users and professionals with multiple high-bandwidth devices.\n\n\n\nThe V-Sekai development team will integrate PCI-E lane checks into the system configuration process, ensuring that users are alerted to potential lane depletion issues before they occur.\n\n\n\nStatus: Accepted \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20230131-adopt-best-product-development-practices.html",
-    "href": "decisions/20230131-adopt-best-product-development-practices.html",
-    "title": "Proposed: Adopt best practices for product development",
+    "objectID": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#the-context",
+    "href": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#the-context",
+    "title": "Accepted: PCI-E Lane Depletion and Thunderbolt 4 Issues",
     "section": "",
-    "text": "Proposed: Adopt best practices for product development\n\nMetadata\n\nStatus: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nContext and Problem Statement\nWe should adopt best practices in developing products.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nToyota has a system that was designed with decades of best practices.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\n\nCoordination Based on Writing\nMentoring Supervisors\nIntegrative Leaders\nStandard Skills\nFlexible Work Standards\nLiving Design Standards\n\nThe six mechanisms that make up the quality control system are mentoring supervision, chief engineers, cross-functional communication, working instructions and standards.\nMentoring supervision serves mainly to build functional expertise, but it also teaches young engineers how to write and interpret reports, work with chief engineers, and understand and use standards. The chief engineer’s prestige reinforces the importance of expertise while it also balances out the functional bent of the other engineers. The chief engineer also promotes mutual adjustment by providing the working instructions for each vehicle program and by resolving cross-functional disagreements.\nThe second mechanism is cross-functional communication. Every major feature requires at least an introduction so it needs a corresponding page with a descriptive title.\n\n\nPositive Consequences\nWe are able to use V-Sekai easier.\n\n\nNegative Consequences\nThese aspects can be incompatible with current practices.\n\n\nOption graveyard\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nKnowing what to do is hard.\n\n\nIs there a reason why this should be core and done by us?\nHow we develop the project is a core task.\n\n\nReferences\n\nV-Sekai\nanother-look-at-how-toyota-integrates-product-development"
+    "text": "In modern computing, PCI-E lanes are a critical resource for connecting various high-speed components such as GPUs, SSDs, and network cards. However, the number of available PCI-E lanes is finite and can become a bottleneck when multiple high-bandwidth devices are connected. This proposal addresses the issue of PCI-E lane depletion, particularly in systems utilizing Thunderbolt 4."
   },
   {
-    "objectID": "decisions/20240830-use-dokku-to-host-vsk-backend.html",
-    "href": "decisions/20240830-use-dokku-to-host-vsk-backend.html",
-    "title": "Proposed: Transition to Dokku from Kubernetes Proposal",
+    "objectID": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#the-problem-statement",
+    "href": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#the-problem-statement",
+    "title": "Accepted: PCI-E Lane Depletion and Thunderbolt 4 Issues",
     "section": "",
-    "text": "This proposal outlines the transition of our backend services from Kubernetes to Dokku, aiming to reduce complexity and maintenance costs.\n\n\n\nDokku is a minimalistic, open-source PAAS that provides a cost-effective alternative to Heroku. Our current use of Kubernetes has become prohibitively complex and expensive.\n\n\n\nWe aim to migrate our backend services from Kubernetes to Dokku to simplify operations and reduce expenses.\n\n\n\n\n\n\nPostgreSQL: Deploy using the Dokku PostgreSQL plugin.\nFile Object Store: Implement an S3 compatible storage solution within Dokku.\nElixir “Uro” Backend: Ensure seamless deployment and operation of our Elixir application on Dokku.\nCaddy: Set up Caddy as a web server and reverse proxy for secure HTTP and SSL management.\nRabbitMQ: Integrate RabbitMQ for robust messaging and queuing capabilities.\nBackups: Implement an S3 compatible backup storage solution.\nTelemetry: Use OpenTelemetry for monitoring and tracing by integrating it with Signoz as outlined in this guide.\n\n\n\n\n# Install Dokku plugins\ndokku plugin:install https://github.com/dokku/dokku-postgres.git postgres\ndokku plugin:install https://github.com/dokku/dokku-rabbitmq.git rabbitmq\n\n# Create PostgreSQL service\ndokku postgres:create my-database\n\n# Create RabbitMQ service\ndokku rabbitmq:create my-messaging-service\n\n# Deploy Elixir application\ngit push dokku master\n\n# Setup OpenTelemetry\n# Follow the specific instructions from the Signoz guide\n\n\n\n\n\nCost Efficiency: Significant reduction in operational and maintenance costs.\nSimplicity: Streamlined management and deployment processes.\nScalability: Adequate scaling capabilities without Kubernetes’ overhead.\nSecurity: Enhanced security features with automatic SSL through Caddy.\nReliability: Dependable inter-service communication with RabbitMQ.\n\n\n\n\n\nFeature Limitations: Dokku may not support all Kubernetes features.\nMigration Challenges: Initial hurdles in transferring services and data.\n\n\n\n\n\nPersisting with Kubernetes despite its drawbacks.\nAdopting other PAAS solutions like Heroku or AWS Elastic Beanstalk.\n\n\n\n\nHandling very high traffic levels might require additional Dokku configurations, which are inherently simpler in Kubernetes.\n\n\n\nThe transition will be managed internally by our development team.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai GitHub - Explore more about V-Sekai’s initiatives on social VR.\nV-Sekai Game Repository - Official repository for the V-Sekai game project.\nTigrisData\n\nAssisted by AI assistant Aria."
+    "text": "When all PCI-E slots are utilized, especially with high-bandwidth devices like GPUs and Thunderbolt 4 controllers, users may experience performance degradation or device malfunctions due to insufficient PCI-E lanes. This problem was highlighted by a user who reported that their Thunderbolt 4 connection broke after using their last PCI-E slot."
   },
   {
-    "objectID": "decisions/20240830-use-dokku-to-host-vsk-backend.html#overview",
-    "href": "decisions/20240830-use-dokku-to-host-vsk-backend.html#overview",
-    "title": "Proposed: Transition to Dokku from Kubernetes Proposal",
+    "objectID": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#proposal-implementation",
+    "href": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#proposal-implementation",
+    "title": "Accepted: PCI-E Lane Depletion and Thunderbolt 4 Issues",
     "section": "",
-    "text": "This proposal outlines the transition of our backend services from Kubernetes to Dokku, aiming to reduce complexity and maintenance costs."
+    "text": "To mitigate this issue, it is recommended to keep the last PCI-E slot empty to ensure sufficient lanes for all connected devices.\n+-------------------+\n|   CPU             |\n|                   |\n| PCI-E Lanes    |\n+---------+---------+\n          |\n          v\n+---------+---------+\n|       PCI-E       |\n|      Switch       |\n+---------+---------+\n          |\n          v\n+---------+---------+---------+---------+\n|   GPU   | Thunderbolt 4 |  NVMe SSD  |\n|     |           |        |\n+---------+---------+---------+---------+"
   },
   {
-    "objectID": "decisions/20240830-use-dokku-to-host-vsk-backend.html#context",
-    "href": "decisions/20240830-use-dokku-to-host-vsk-backend.html#context",
-    "title": "Proposed: Transition to Dokku from Kubernetes Proposal",
+    "objectID": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#the-benefits",
+    "href": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#the-benefits",
+    "title": "Accepted: PCI-E Lane Depletion and Thunderbolt 4 Issues",
     "section": "",
-    "text": "Dokku is a minimalistic, open-source PAAS that provides a cost-effective alternative to Heroku. Our current use of Kubernetes has become prohibitively complex and expensive."
+    "text": "Improved System Stability: Ensuring sufficient PCI-E lanes for all devices will prevent system crashes and performance issues.\nOptimized Resource Allocation: Users can make informed decisions about which devices to prioritize based on available PCI-E lanes.\nEnhanced User Experience: By avoiding unexpected device failures, users will have a more reliable and predictable computing experience."
   },
   {
-    "objectID": "decisions/20240830-use-dokku-to-host-vsk-backend.html#problem-statement",
-    "href": "decisions/20240830-use-dokku-to-host-vsk-backend.html#problem-statement",
-    "title": "Proposed: Transition to Dokku from Kubernetes Proposal",
+    "objectID": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#the-downsides",
+    "href": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#the-downsides",
+    "title": "Accepted: PCI-E Lane Depletion and Thunderbolt 4 Issues",
     "section": "",
-    "text": "We aim to migrate our backend services from Kubernetes to Dokku to simplify operations and reduce expenses."
+    "text": "Complexity: Implementing checks for PCI-E lane availability adds complexity to system configuration and management.\nHardware Limitations: Users with limited PCI-E lanes may need to upgrade their hardware to fully utilize all desired devices."
   },
   {
-    "objectID": "decisions/20240830-use-dokku-to-host-vsk-backend.html#implementation-details",
-    "href": "decisions/20240830-use-dokku-to-host-vsk-backend.html#implementation-details",
-    "title": "Proposed: Transition to Dokku from Kubernetes Proposal",
+    "objectID": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#the-road-not-taken",
+    "href": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#the-road-not-taken",
+    "title": "Accepted: PCI-E Lane Depletion and Thunderbolt 4 Issues",
     "section": "",
-    "text": "PostgreSQL: Deploy using the Dokku PostgreSQL plugin.\nFile Object Store: Implement an S3 compatible storage solution within Dokku.\nElixir “Uro” Backend: Ensure seamless deployment and operation of our Elixir application on Dokku.\nCaddy: Set up Caddy as a web server and reverse proxy for secure HTTP and SSL management.\nRabbitMQ: Integrate RabbitMQ for robust messaging and queuing capabilities.\nBackups: Implement an S3 compatible backup storage solution.\nTelemetry: Use OpenTelemetry for monitoring and tracing by integrating it with Signoz as outlined in this guide.\n\n\n\n\n# Install Dokku plugins\ndokku plugin:install https://github.com/dokku/dokku-postgres.git postgres\ndokku plugin:install https://github.com/dokku/dokku-rabbitmq.git rabbitmq\n\n# Create PostgreSQL service\ndokku postgres:create my-database\n\n# Create RabbitMQ service\ndokku rabbitmq:create my-messaging-service\n\n# Deploy Elixir application\ngit push dokku master\n\n# Setup OpenTelemetry\n# Follow the specific instructions from the Signoz guide"
+    "text": "An alternative approach could be to develop software solutions that dynamically manage PCI-E lane allocation based on real-time usage patterns. However, this would require significant changes to both hardware and software architectures and may not be feasible for all users."
   },
   {
-    "objectID": "decisions/20240830-use-dokku-to-host-vsk-backend.html#benefits",
-    "href": "decisions/20240830-use-dokku-to-host-vsk-backend.html#benefits",
-    "title": "Proposed: Transition to Dokku from Kubernetes Proposal",
+    "objectID": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#the-infrequent-use-case",
+    "href": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#the-infrequent-use-case",
+    "title": "Accepted: PCI-E Lane Depletion and Thunderbolt 4 Issues",
     "section": "",
-    "text": "Cost Efficiency: Significant reduction in operational and maintenance costs.\nSimplicity: Streamlined management and deployment processes.\nScalability: Adequate scaling capabilities without Kubernetes’ overhead.\nSecurity: Enhanced security features with automatic SSL through Caddy.\nReliability: Dependable inter-service communication with RabbitMQ."
+    "text": "In scenarios where users only utilize a single high-bandwidth device, such as a GPU, PCI-E lane depletion is unlikely to be an issue. This proposal primarily targets power users and professionals with multiple high-bandwidth devices."
   },
   {
-    "objectID": "decisions/20240830-use-dokku-to-host-vsk-backend.html#potential-downsides",
-    "href": "decisions/20240830-use-dokku-to-host-vsk-backend.html#potential-downsides",
-    "title": "Proposed: Transition to Dokku from Kubernetes Proposal",
+    "objectID": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#in-core-and-done-by-us",
+    "href": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#in-core-and-done-by-us",
+    "title": "Accepted: PCI-E Lane Depletion and Thunderbolt 4 Issues",
     "section": "",
-    "text": "Feature Limitations: Dokku may not support all Kubernetes features.\nMigration Challenges: Initial hurdles in transferring services and data."
+    "text": "The V-Sekai development team will integrate PCI-E lane checks into the system configuration process, ensuring that users are alerted to potential lane depletion issues before they occur."
   },
   {
-    "objectID": "decisions/20240830-use-dokku-to-host-vsk-backend.html#alternatives-considered",
-    "href": "decisions/20240830-use-dokku-to-host-vsk-backend.html#alternatives-considered",
-    "title": "Proposed: Transition to Dokku from Kubernetes Proposal",
+    "objectID": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#status",
+    "href": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#status",
+    "title": "Accepted: PCI-E Lane Depletion and Thunderbolt 4 Issues",
     "section": "",
-    "text": "Persisting with Kubernetes despite its drawbacks.\nAdopting other PAAS solutions like Heroku or AWS Elastic Beanstalk."
+    "text": "Status: Accepted"
   },
   {
-    "objectID": "decisions/20240830-use-dokku-to-host-vsk-backend.html#special-considerations",
-    "href": "decisions/20240830-use-dokku-to-host-vsk-backend.html#special-considerations",
-    "title": "Proposed: Transition to Dokku from Kubernetes Proposal",
+    "objectID": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#decision-makers",
+    "href": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#decision-makers",
+    "title": "Accepted: PCI-E Lane Depletion and Thunderbolt 4 Issues",
     "section": "",
-    "text": "Handling very high traffic levels might require additional Dokku configurations, which are inherently simpler in Kubernetes."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20240830-use-dokku-to-host-vsk-backend.html#project-management",
-    "href": "decisions/20240830-use-dokku-to-host-vsk-backend.html#project-management",
-    "title": "Proposed: Transition to Dokku from Kubernetes Proposal",
+    "objectID": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#tags",
+    "href": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#tags",
+    "title": "Accepted: PCI-E Lane Depletion and Thunderbolt 4 Issues",
     "section": "",
-    "text": "The transition will be managed internally by our development team."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20240830-use-dokku-to-host-vsk-backend.html#current-status",
-    "href": "decisions/20240830-use-dokku-to-host-vsk-backend.html#current-status",
-    "title": "Proposed: Transition to Dokku from Kubernetes Proposal",
+    "objectID": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#further-reading",
+    "href": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#further-reading",
+    "title": "Accepted: PCI-E Lane Depletion and Thunderbolt 4 Issues",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240830-use-dokku-to-host-vsk-backend.html#decision-makers",
-    "href": "decisions/20240830-use-dokku-to-host-vsk-backend.html#decision-makers",
-    "title": "Proposed: Transition to Dokku from Kubernetes Proposal",
+    "objectID": "decisions/20211005-want-to-summon-friends-and-acquaintances-via-presence.html",
+    "href": "decisions/20211005-want-to-summon-friends-and-acquaintances-via-presence.html",
+    "title": "Proposed: Summon #friend and acquaintances via presence to the current world.",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "Proposed: Summon #friend and acquaintances via presence to the current world.\n\nContext and Problem Statement\nWant to summon #friend and acquaintances via presence.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nBy using rich presence #friend can join my location.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nAble to be a tray item and a graphical window.\nAble to have new friends.\nUpdate my current world and current position on changes.\nNotification is a visually distinct status that reflects presence of friends.\n\nPrivacy\n\nShare nothing\nShare world\nShare world location\n\n\n\nEngineering\nUse libp2p as a Godot Engine 4 c++ module working on Godot Engine on Win10, Macos and Linux (Popos! 21.04).\nHow do we get presence information?\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot a few lines of script to implement presence.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nCan be done as a group.\n\n\nReferences\n\nhttps://github.com/libp2p/cpp-libp2p\nhttps://github.com/fire/godot-p2p/\nhttps://did-ipid.github.io/ipid-did-method/\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240830-use-dokku-to-host-vsk-backend.html#tags",
-    "href": "decisions/20240830-use-dokku-to-host-vsk-backend.html#tags",
-    "title": "Proposed: Transition to Dokku from Kubernetes Proposal",
+    "objectID": "decisions/20240615-what-is-mesh-transformers.html",
+    "href": "decisions/20240615-what-is-mesh-transformers.html",
+    "title": "Proposed: Explain the concept of Mesh Transformers",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Many of my friends are not tech-savvy.\n\n\n\nHow can we explain the concept of Mesh Transformers to a student?\n\n\n\nMesh Transformers can be understood as two parts - a construction worker (auto encoder) and an architect (transformer).\nThe construction worker learns how to construct and build a building, while the architect learns about all the items needed for a building and then instructs the construction worker on what to do.\nThe goal is to allow users to generate a 3D model on the fly using a prompt, instead of searching through numerous 3D libraries and forums. They can simply write what they want and within a few seconds get exactly what they want without settling on a 3D model that they kind of want.\n\n\n\nThis approach simplifies the process of creating 3D models, making it accessible even to those with little to no technical knowledge. It also saves time by eliminating the need to search through various resources.\n\n\n\nThere might be a learning curve involved in understanding how to use prompts effectively. Also, the quality of the generated 3D model may vary based on the specificity of the prompt.\n\n\n\nAn alternative could have been to create a user-friendly interface for browsing and selecting from pre-existing 3D models. However, this would not offer the same level of customization and convenience as generating a model from a prompt.\n\n\n\nUsers who require highly detailed and specific 3D models may find the prompt-based generation less useful, as it may not always produce the desired level of detail or accuracy.\n\n\n\nThis proposal involves developing a new feature for our platform, which will be done by our development team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - This is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis proposal was assisted by AI assistant Aria."
   },
   {
-    "objectID": "decisions/20240830-use-dokku-to-host-vsk-backend.html#further-information",
-    "href": "decisions/20240830-use-dokku-to-host-vsk-backend.html#further-information",
-    "title": "Proposed: Transition to Dokku from Kubernetes Proposal",
+    "objectID": "decisions/20240615-what-is-mesh-transformers.html#the-context",
+    "href": "decisions/20240615-what-is-mesh-transformers.html#the-context",
+    "title": "Proposed: Explain the concept of Mesh Transformers",
     "section": "",
-    "text": "V-Sekai GitHub - Explore more about V-Sekai’s initiatives on social VR.\nV-Sekai Game Repository - Official repository for the V-Sekai game project.\nTigrisData\n\nAssisted by AI assistant Aria."
+    "text": "Many of my friends are not tech-savvy."
   },
   {
-    "objectID": "decisions/20220820-market-booth-tutorial.html",
-    "href": "decisions/20220820-market-booth-tutorial.html",
-    "title": "Proposed: Make a market booth creation tutorial.",
+    "objectID": "decisions/20240615-what-is-mesh-transformers.html#the-problem-statement",
+    "href": "decisions/20240615-what-is-mesh-transformers.html#the-problem-statement",
+    "title": "Proposed: Explain the concept of Mesh Transformers",
     "section": "",
-    "text": "To present at various virtual market locations, we need to do various workflow steps that are quickly forgotten.\n\n\n\nWe can write down our collective workflows for creation.\n\n\n\nWrite a guide to makie a 3d market booth that is the 4m x 4m x 5m standard size and 2m x 2m x 2.5m constrained size.\n\n\n\n\nSubstance designer\nBlender\n\n\n\n\n\nMake a procedural grid texture and some text.\nPut the booth in blender on the booth boundaries (cube).\n\n\n\n\n\nUpload to Github organization.\n\n\n\n\nIncrease our workflow\n\n\n\n\n\nLoss of creativity\n\n\n\n\n\nOption: Recreate the workflow from scratch\n\n\n\n\nWorkflow enhancement.\n\n\n\nWe are doing this, so we can record how we did it.\n\n\n\n\nV-Sekai\nhttps://www.youtube.com/watch?v=LGZWjyeUPHU\n\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "How can we explain the concept of Mesh Transformers to a student?"
   },
   {
-    "objectID": "decisions/20220820-market-booth-tutorial.html#tools-used",
-    "href": "decisions/20220820-market-booth-tutorial.html#tools-used",
-    "title": "Proposed: Make a market booth creation tutorial.",
+    "objectID": "decisions/20240615-what-is-mesh-transformers.html#solution-proposal",
+    "href": "decisions/20240615-what-is-mesh-transformers.html#solution-proposal",
+    "title": "Proposed: Explain the concept of Mesh Transformers",
     "section": "",
-    "text": "Substance designer\nBlender"
+    "text": "Mesh Transformers can be understood as two parts - a construction worker (auto encoder) and an architect (transformer).\nThe construction worker learns how to construct and build a building, while the architect learns about all the items needed for a building and then instructs the construction worker on what to do.\nThe goal is to allow users to generate a 3D model on the fly using a prompt, instead of searching through numerous 3D libraries and forums. They can simply write what they want and within a few seconds get exactly what they want without settling on a 3D model that they kind of want."
   },
   {
-    "objectID": "decisions/20220820-market-booth-tutorial.html#initial-task",
-    "href": "decisions/20220820-market-booth-tutorial.html#initial-task",
-    "title": "Proposed: Make a market booth creation tutorial.",
+    "objectID": "decisions/20240615-what-is-mesh-transformers.html#the-benefits",
+    "href": "decisions/20240615-what-is-mesh-transformers.html#the-benefits",
+    "title": "Proposed: Explain the concept of Mesh Transformers",
     "section": "",
-    "text": "Make a procedural grid texture and some text.\nPut the booth in blender on the booth boundaries (cube)."
+    "text": "This approach simplifies the process of creating 3D models, making it accessible even to those with little to no technical knowledge. It also saves time by eliminating the need to search through various resources."
   },
   {
-    "objectID": "decisions/20220820-market-booth-tutorial.html#storage",
-    "href": "decisions/20220820-market-booth-tutorial.html#storage",
-    "title": "Proposed: Make a market booth creation tutorial.",
+    "objectID": "decisions/20240615-what-is-mesh-transformers.html#the-downsides",
+    "href": "decisions/20240615-what-is-mesh-transformers.html#the-downsides",
+    "title": "Proposed: Explain the concept of Mesh Transformers",
     "section": "",
-    "text": "Upload to Github organization.\n\n\n\n\nIncrease our workflow\n\n\n\n\n\nLoss of creativity\n\n\n\n\n\nOption: Recreate the workflow from scratch\n\n\n\n\nWorkflow enhancement.\n\n\n\nWe are doing this, so we can record how we did it.\n\n\n\n\nV-Sekai\nhttps://www.youtube.com/watch?v=LGZWjyeUPHU\n\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "There might be a learning curve involved in understanding how to use prompts effectively. Also, the quality of the generated 3D model may vary based on the specificity of the prompt."
   },
   {
-    "objectID": "decisions/20240218-vrm-acronym-correction.html",
-    "href": "decisions/20240218-vrm-acronym-correction.html",
-    "title": "Accepted: VRM Acronym Correction",
+    "objectID": "decisions/20240615-what-is-mesh-transformers.html#the-road-not-taken",
+    "href": "decisions/20240615-what-is-mesh-transformers.html#the-road-not-taken",
+    "title": "Proposed: Explain the concept of Mesh Transformers",
     "section": "",
-    "text": "It has come to our attention that the term VRM has been incorrectly defined in earlier communications. We would like to clarify that VRM does not stand for “VRoid Model”, “Virtual Reality Model”, or any other previous interpretations provided.\n\n\n\nNot applicable as this involves correcting documentation and communication.\n\n\n\n\nEnsures everyone has a correct understanding of VRM.\nMaintains consistency in project materials.\n\n\n\n\n\nPossible brief confusion during the transition phase.\n\n\n\n\nChoosing not to publicly campaign about this error since it’s manageable through targeted updates.\n\n\n\nMinor impact on casual users who may overlook the correction.\n\n\n\nThe correction is directly handled by our team with ongoing oversight.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team and community stakeholders.\n\n\n\n\n\nV-Sekai, Avatar Customization, AI, Facial Expressions\n\n\n\n\n\nV-Sekai · GitHub - Official source for V-Sekai dev community.\nV-Sekai/v-sekai-game - Repository for V-Sekai project on social VR in Godot Engine.\n3D humanoid avatar file format for VR\n\nAria assisted with this content."
+    "text": "An alternative could have been to create a user-friendly interface for browsing and selecting from pre-existing 3D models. However, this would not offer the same level of customization and convenience as generating a model from a prompt."
   },
   {
-    "objectID": "decisions/20240218-vrm-acronym-correction.html#overview",
-    "href": "decisions/20240218-vrm-acronym-correction.html#overview",
-    "title": "Accepted: VRM Acronym Correction",
+    "objectID": "decisions/20240615-what-is-mesh-transformers.html#the-infrequent-use-case",
+    "href": "decisions/20240615-what-is-mesh-transformers.html#the-infrequent-use-case",
+    "title": "Proposed: Explain the concept of Mesh Transformers",
     "section": "",
-    "text": "It has come to our attention that the term VRM has been incorrectly defined in earlier communications. We would like to clarify that VRM does not stand for “VRoid Model”, “Virtual Reality Model”, or any other previous interpretations provided."
+    "text": "Users who require highly detailed and specific 3D models may find the prompt-based generation less useful, as it may not always produce the desired level of detail or accuracy."
   },
   {
-    "objectID": "decisions/20240218-vrm-acronym-correction.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240218-vrm-acronym-correction.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Accepted: VRM Acronym Correction",
+    "objectID": "decisions/20240615-what-is-mesh-transformers.html#in-core-and-done-by-us",
+    "href": "decisions/20240615-what-is-mesh-transformers.html#in-core-and-done-by-us",
+    "title": "Proposed: Explain the concept of Mesh Transformers",
     "section": "",
-    "text": "Not applicable as this involves correcting documentation and communication."
+    "text": "This proposal involves developing a new feature for our platform, which will be done by our development team."
   },
   {
-    "objectID": "decisions/20240218-vrm-acronym-correction.html#the-benefits",
-    "href": "decisions/20240218-vrm-acronym-correction.html#the-benefits",
-    "title": "Accepted: VRM Acronym Correction",
+    "objectID": "decisions/20240615-what-is-mesh-transformers.html#status",
+    "href": "decisions/20240615-what-is-mesh-transformers.html#status",
+    "title": "Proposed: Explain the concept of Mesh Transformers",
     "section": "",
-    "text": "Ensures everyone has a correct understanding of VRM.\nMaintains consistency in project materials."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20240218-vrm-acronym-correction.html#the-downsides",
-    "href": "decisions/20240218-vrm-acronym-correction.html#the-downsides",
-    "title": "Accepted: VRM Acronym Correction",
+    "objectID": "decisions/20240615-what-is-mesh-transformers.html#decision-makers",
+    "href": "decisions/20240615-what-is-mesh-transformers.html#decision-makers",
+    "title": "Proposed: Explain the concept of Mesh Transformers",
     "section": "",
-    "text": "Possible brief confusion during the transition phase."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20240218-vrm-acronym-correction.html#the-road-not-taken",
-    "href": "decisions/20240218-vrm-acronym-correction.html#the-road-not-taken",
-    "title": "Accepted: VRM Acronym Correction",
+    "objectID": "decisions/20240615-what-is-mesh-transformers.html#tags",
+    "href": "decisions/20240615-what-is-mesh-transformers.html#tags",
+    "title": "Proposed: Explain the concept of Mesh Transformers",
     "section": "",
-    "text": "Choosing not to publicly campaign about this error since it’s manageable through targeted updates."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20240218-vrm-acronym-correction.html#the-infrequent-use-case",
-    "href": "decisions/20240218-vrm-acronym-correction.html#the-infrequent-use-case",
-    "title": "Accepted: VRM Acronym Correction",
+    "objectID": "decisions/20240615-what-is-mesh-transformers.html#further-reading",
+    "href": "decisions/20240615-what-is-mesh-transformers.html#further-reading",
+    "title": "Proposed: Explain the concept of Mesh Transformers",
     "section": "",
-    "text": "Minor impact on casual users who may overlook the correction."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - This is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis proposal was assisted by AI assistant Aria."
   },
   {
-    "objectID": "decisions/20240218-vrm-acronym-correction.html#in-core-and-done-by-us",
-    "href": "decisions/20240218-vrm-acronym-correction.html#in-core-and-done-by-us",
-    "title": "Accepted: VRM Acronym Correction",
+    "objectID": "decisions/20220317-baserow.io-truenas.html",
+    "href": "decisions/20220317-baserow.io-truenas.html",
+    "title": "Draft: To provide an asset library prototype use baserow",
     "section": "",
-    "text": "The correction is directly handled by our team with ongoing oversight."
+    "text": "Draft: To provide an asset library prototype use baserow\n\nDescribe the status of the issue.\ndraft\n\n\nList the deciders of the issue.\nV-Sekai,fire,\n\n\nDescribe the tags of the issue.\nV-Sekai,\n\n\nContext and Problem Statement\nWant to prototype a game asset library system.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nNeed a sandbox to prototype asset library.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\n\ninstall truenas on two redundant data drives and on a os drive\ninstall baserow.io as a docker compose\nadd vrm three.js viewer to baserow for .gltf and .vrm\n\n\n\nPositive Consequences\nAble to lean prototype asset libraries.\n\n\nNegative Consequences\nNo response\n\n\nOption graveyard\nNo response\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot a few lines of script.\n\n\nIs there a reason why this should be core and done by us?\nWanted to lean prototype.\n\n\nReferences\n\nV-Sekai\n\n\n\nLicense of the contribution\nCopyright (c) 2022 V-Sekai contributors. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240218-vrm-acronym-correction.html#status",
-    "href": "decisions/20240218-vrm-acronym-correction.html#status",
-    "title": "Accepted: VRM Acronym Correction",
+    "objectID": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html",
+    "href": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html",
+    "title": "Proposal: Sustainable Version Management for Godot Engine in V-Sekai",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "The continuous growth of upstream versions in the Godot Engine presents a challenge for the V-Sekai project. With finite resources and brainpower, keeping up with this “infinite” growth and its associated delays becomes increasingly difficult.\n\n\n\nHow can we manage the version growth of the Godot Engine more sustainably, focusing our limited resources on what matters most for our project?\n\n\n\nWe propose a sustainable approach to handle the version growth of the Godot Engine:\n\nDesigning for Finite Funds: Instead of investing heavily in trying to keep up with every new version, focus on key updates that significantly impact or improve our project.\nDesigning for Finite Performance: Prioritize optimization and performance over trying to incorporate every new feature from the latest versions.\nDesigning for Finite Data: Be selective about the data we choose to update with each new version, focusing on what’s most relevant to our project.\nDesign for Finite Brainpower: Invest in knowledge sharing and training to ensure our team can effectively work with the chosen versions of Godot Engine.\n\n\n\n\nThis approach will allow us to manage version growth more sustainably. It will also help us avoid unnecessary delays caused by trying to keep up with every new version.\n\n\n\nWe may miss out on some features or improvements introduced in the versions we choose not to adopt. However, by focusing on significant updates, we aim to mitigate this risk.\n\n\n\nContinuing to try and keep up with every new version of the Godot Engine, despite our limited resources.\n\n\n\nWhile our focus is on managing the version growth of the Godot Engine sustainably, there may be infrequent cases where we need to adopt a new version immediately. This could occur if a new version introduces a critical security patch or a feature that significantly benefits our project. In such cases, we will prioritize updating to the new version, even if it requires additional resources.\n\n\n\nThis proposal involves changes to our core version management practices and will be implemented by our development team.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai Development Team\n\n\n\n\n\nVersion Management\nGodot Engine\nSustainability\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - The GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nCoding for a Finite World - A blog post discussing the need for sustainable coding practices in a finite world.\n\nThis proposal was assisted by AI assistant, Aria."
   },
   {
-    "objectID": "decisions/20240218-vrm-acronym-correction.html#decision-makers",
-    "href": "decisions/20240218-vrm-acronym-correction.html#decision-makers",
-    "title": "Accepted: VRM Acronym Correction",
+    "objectID": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#the-context",
+    "href": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#the-context",
+    "title": "Proposal: Sustainable Version Management for Godot Engine in V-Sekai",
     "section": "",
-    "text": "V-Sekai development team and community stakeholders."
+    "text": "The continuous growth of upstream versions in the Godot Engine presents a challenge for the V-Sekai project. With finite resources and brainpower, keeping up with this “infinite” growth and its associated delays becomes increasingly difficult."
   },
   {
-    "objectID": "decisions/20240218-vrm-acronym-correction.html#tags",
-    "href": "decisions/20240218-vrm-acronym-correction.html#tags",
-    "title": "Accepted: VRM Acronym Correction",
+    "objectID": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#the-problem-statement",
+    "href": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#the-problem-statement",
+    "title": "Proposal: Sustainable Version Management for Godot Engine in V-Sekai",
     "section": "",
-    "text": "V-Sekai, Avatar Customization, AI, Facial Expressions"
+    "text": "How can we manage the version growth of the Godot Engine more sustainably, focusing our limited resources on what matters most for our project?"
   },
   {
-    "objectID": "decisions/20240218-vrm-acronym-correction.html#further-reading",
-    "href": "decisions/20240218-vrm-acronym-correction.html#further-reading",
-    "title": "Accepted: VRM Acronym Correction",
+    "objectID": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposal: Sustainable Version Management for Godot Engine in V-Sekai",
     "section": "",
-    "text": "V-Sekai · GitHub - Official source for V-Sekai dev community.\nV-Sekai/v-sekai-game - Repository for V-Sekai project on social VR in Godot Engine.\n3D humanoid avatar file format for VR\n\nAria assisted with this content."
+    "text": "We propose a sustainable approach to handle the version growth of the Godot Engine:\n\nDesigning for Finite Funds: Instead of investing heavily in trying to keep up with every new version, focus on key updates that significantly impact or improve our project.\nDesigning for Finite Performance: Prioritize optimization and performance over trying to incorporate every new feature from the latest versions.\nDesigning for Finite Data: Be selective about the data we choose to update with each new version, focusing on what’s most relevant to our project.\nDesign for Finite Brainpower: Invest in knowledge sharing and training to ensure our team can effectively work with the chosen versions of Godot Engine."
   },
   {
-    "objectID": "decisions/20230505-v-sekai-ai-completion.html",
-    "href": "decisions/20230505-v-sekai-ai-completion.html",
-    "title": "Superseded: Solve V-Sekai limitations using ChatGPT-4 AI completion.",
+    "objectID": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#the-benefits",
+    "href": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#the-benefits",
+    "title": "Proposal: Sustainable Version Management for Godot Engine in V-Sekai",
     "section": "",
-    "text": "Status: superseded by 20230522-proposal-template.md \nDeciders: V-Sekai,fire,\nTags: V-Sekai,ChatGPT-4,AI_assistance,problem solving,proposal generation,Visual Studio Code addon,\n\n\n\n\nWe sometimes need help finding solutions to our issues. ChatGPT-4 artificial intelligence completion can help us solve the entire problem when we only have the start of the solution.\n\n\n\nHow can we leverage ChatGPT-4 AI completion to assist in solving problems and completing proposals for V-Sekai?\n\n\n\nUse ChatGPT-4 AI completion with the Visual Studio Code “Genie” addon to fill in as many sections as possible in a given proposal template, helping to generate complete and well-rounded solutions.\n\n\n\n\nEnsure access to the chatgpt4 API access. There is a waiting list.\nCopy the proposal template.\nFill in as many sections as possible in the proposal template.\nUse the Visual Studio Code “Genie” addon with ChatGPT-4 AI completion to complete the remaining sections of the proposal.\nReview and refine the completed proposal.\nReview with copy editing software if accessible.\nRecord the decisions on GitHub at https://github.com/V-Sekai/manuals.\n\nExample of using ChatGPT-4 AI completion with the proposal template.\n# Issue: Feature implementation proposal\n\n## Propose a possible solution to solve a V-Sekai limitation. If this doesn't look right, choose a different type.\n\n## Metadata\n\n- Status: proposed &lt;!-- draft | proposed | rejected | accepted | deprecated | superseded by --&gt;\n- Deciders: V-Sekai\n- Tags: V-Sekai, GPT-4\n\n## Context and Problem Statement\n\n## Proposed Solution\n\n## Implementation\n\n## Positive Consequences\n\n## Negative Consequences\n\n## Option graveyard\n\n## If this enhancement will be used infrequently, can it be worked around with a few lines of script?\n\n## Is there a reason why this should be core and done by us?\n\n## References\n\n- [V-Sekai](https://v-sekai.org/)\n\n\n\n\nImproved problem-solving capabilities.\nMore complete and well-rounded proposals.\nFaster generation of solutions.\n\n\n\n\n\nPotential reliance on AI-generated content, which may only sometimes be accurate or suitable.\nAdditional time spent reviewing and refining AI-generated content.\n\n\n\n\nUse only human assistance.\n\n\n\nNo, this enhancement requires integrating ChatGPT-4 AI completion into the development workflow and cannot be achieved with a simple script.\n\n\n\nYes, leveraging AI-generated content can help improve the efficiency and effectiveness of our problem-solving process, leading to better solutions and faster development.\n\n\n\n\nV-Sekai\nGenie addon for Visual Studio Code"
+    "text": "This approach will allow us to manage version growth more sustainably. It will also help us avoid unnecessary delays caused by trying to keep up with every new version."
   },
   {
-    "objectID": "decisions/20230505-v-sekai-ai-completion.html#metadata",
-    "href": "decisions/20230505-v-sekai-ai-completion.html#metadata",
-    "title": "Superseded: Solve V-Sekai limitations using ChatGPT-4 AI completion.",
+    "objectID": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#the-downsides",
+    "href": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#the-downsides",
+    "title": "Proposal: Sustainable Version Management for Godot Engine in V-Sekai",
     "section": "",
-    "text": "Status: superseded by 20230522-proposal-template.md \nDeciders: V-Sekai,fire,\nTags: V-Sekai,ChatGPT-4,AI_assistance,problem solving,proposal generation,Visual Studio Code addon,"
+    "text": "We may miss out on some features or improvements introduced in the versions we choose not to adopt. However, by focusing on significant updates, we aim to mitigate this risk."
   },
   {
-    "objectID": "decisions/20230505-v-sekai-ai-completion.html#context-and-problem-statement",
-    "href": "decisions/20230505-v-sekai-ai-completion.html#context-and-problem-statement",
-    "title": "Superseded: Solve V-Sekai limitations using ChatGPT-4 AI completion.",
+    "objectID": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#the-road-not-taken",
+    "href": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#the-road-not-taken",
+    "title": "Proposal: Sustainable Version Management for Godot Engine in V-Sekai",
     "section": "",
-    "text": "We sometimes need help finding solutions to our issues. ChatGPT-4 artificial intelligence completion can help us solve the entire problem when we only have the start of the solution."
+    "text": "Continuing to try and keep up with every new version of the Godot Engine, despite our limited resources."
   },
   {
-    "objectID": "decisions/20230505-v-sekai-ai-completion.html#describe-the-problem-or-limitation-you-have-in-your-project-e.g.-in-free-form-using-two-to-three-sentences.-consider-articulating-the-case-in-the-form-of-a-question.",
-    "href": "decisions/20230505-v-sekai-ai-completion.html#describe-the-problem-or-limitation-you-have-in-your-project-e.g.-in-free-form-using-two-to-three-sentences.-consider-articulating-the-case-in-the-form-of-a-question.",
-    "title": "Superseded: Solve V-Sekai limitations using ChatGPT-4 AI completion.",
+    "objectID": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#the-infrequent-use-case",
+    "href": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#the-infrequent-use-case",
+    "title": "Proposal: Sustainable Version Management for Godot Engine in V-Sekai",
     "section": "",
-    "text": "How can we leverage ChatGPT-4 AI completion to assist in solving problems and completing proposals for V-Sekai?"
+    "text": "While our focus is on managing the version growth of the Godot Engine sustainably, there may be infrequent cases where we need to adopt a new version immediately. This could occur if a new version introduces a critical security patch or a feature that significantly benefits our project. In such cases, we will prioritize updating to the new version, even if it requires additional resources."
   },
   {
-    "objectID": "decisions/20230505-v-sekai-ai-completion.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20230505-v-sekai-ai-completion.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Superseded: Solve V-Sekai limitations using ChatGPT-4 AI completion.",
+    "objectID": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#in-core-and-done-by-us",
+    "href": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#in-core-and-done-by-us",
+    "title": "Proposal: Sustainable Version Management for Godot Engine in V-Sekai",
     "section": "",
-    "text": "Use ChatGPT-4 AI completion with the Visual Studio Code “Genie” addon to fill in as many sections as possible in a given proposal template, helping to generate complete and well-rounded solutions."
+    "text": "This proposal involves changes to our core version management practices and will be implemented by our development team."
   },
   {
-    "objectID": "decisions/20230505-v-sekai-ai-completion.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20230505-v-sekai-ai-completion.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Superseded: Solve V-Sekai limitations using ChatGPT-4 AI completion.",
+    "objectID": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#status",
+    "href": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#status",
+    "title": "Proposal: Sustainable Version Management for Godot Engine in V-Sekai",
     "section": "",
-    "text": "Ensure access to the chatgpt4 API access. There is a waiting list.\nCopy the proposal template.\nFill in as many sections as possible in the proposal template.\nUse the Visual Studio Code “Genie” addon with ChatGPT-4 AI completion to complete the remaining sections of the proposal.\nReview and refine the completed proposal.\nReview with copy editing software if accessible.\nRecord the decisions on GitHub at https://github.com/V-Sekai/manuals.\n\nExample of using ChatGPT-4 AI completion with the proposal template.\n# Issue: Feature implementation proposal\n\n## Propose a possible solution to solve a V-Sekai limitation. If this doesn't look right, choose a different type.\n\n## Metadata\n\n- Status: proposed &lt;!-- draft | proposed | rejected | accepted | deprecated | superseded by --&gt;\n- Deciders: V-Sekai\n- Tags: V-Sekai, GPT-4\n\n## Context and Problem Statement\n\n## Proposed Solution\n\n## Implementation\n\n## Positive Consequences\n\n## Negative Consequences\n\n## Option graveyard\n\n## If this enhancement will be used infrequently, can it be worked around with a few lines of script?\n\n## Is there a reason why this should be core and done by us?\n\n## References\n\n- [V-Sekai](https://v-sekai.org/)"
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20230505-v-sekai-ai-completion.html#positive-consequences",
-    "href": "decisions/20230505-v-sekai-ai-completion.html#positive-consequences",
-    "title": "Superseded: Solve V-Sekai limitations using ChatGPT-4 AI completion.",
+    "objectID": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#decision-makers",
+    "href": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#decision-makers",
+    "title": "Proposal: Sustainable Version Management for Godot Engine in V-Sekai",
     "section": "",
-    "text": "Improved problem-solving capabilities.\nMore complete and well-rounded proposals.\nFaster generation of solutions."
+    "text": "V-Sekai Development Team"
   },
   {
-    "objectID": "decisions/20230505-v-sekai-ai-completion.html#negative-consequences",
-    "href": "decisions/20230505-v-sekai-ai-completion.html#negative-consequences",
-    "title": "Superseded: Solve V-Sekai limitations using ChatGPT-4 AI completion.",
+    "objectID": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#tags",
+    "href": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#tags",
+    "title": "Proposal: Sustainable Version Management for Godot Engine in V-Sekai",
     "section": "",
-    "text": "Potential reliance on AI-generated content, which may only sometimes be accurate or suitable.\nAdditional time spent reviewing and refining AI-generated content."
+    "text": "Version Management\nGodot Engine\nSustainability"
   },
   {
-    "objectID": "decisions/20230505-v-sekai-ai-completion.html#option-graveyard",
-    "href": "decisions/20230505-v-sekai-ai-completion.html#option-graveyard",
-    "title": "Superseded: Solve V-Sekai limitations using ChatGPT-4 AI completion.",
+    "objectID": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#further-reading",
+    "href": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#further-reading",
+    "title": "Proposal: Sustainable Version Management for Godot Engine in V-Sekai",
     "section": "",
-    "text": "Use only human assistance."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - The GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nCoding for a Finite World - A blog post discussing the need for sustainable coding practices in a finite world.\n\nThis proposal was assisted by AI assistant, Aria."
   },
   {
-    "objectID": "decisions/20230505-v-sekai-ai-completion.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230505-v-sekai-ai-completion.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Superseded: Solve V-Sekai limitations using ChatGPT-4 AI completion.",
+    "objectID": "decisions/20211104-research-mesh-tooling-with-nglod.html",
+    "href": "decisions/20211104-research-mesh-tooling-with-nglod.html",
+    "title": "Draft: Research mesh tooling with nglod",
     "section": "",
-    "text": "No, this enhancement requires integrating ChatGPT-4 AI completion into the development workflow and cannot be achieved with a simple script."
+    "text": "Status: draft \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nNeed geometric tools for many things in the V-Sekai.\n\n\n\nUse nglod for some of the 3d geometric tools.\n\n\n\n\ngit clone https://github.com/nv-tlabs/nglod.git\nInstall https://github.com/conda-forge/miniforge#mambaforge\nconda create --name nglod python=3.9\nconda activate nglod\nconda install pytorch torchvision torchaudio cudatoolkit=11.3 -c pytorch\npip install -r ./infra/requirements.txt\n\npython app/main.py --net OctreeSDF --num-lods 5 --dataset-path data/armadillo.obj --epoch 250 --exp-name armadillo\n\n\n\n\nMaybe possible to encode as onnx\nMaybe usable cpu only.\n\n\n\n\n\nMight require the GPU.\nInferencing may be difficult at interactive rates.\n\n\n\n\n\nOption: \nRejection Reason: \n\n\n\n\nCUDA, PyTorch and c++ are significant works.\n\n\n\nI have an approach!\n\n\n\n\nhttps://kaolin.readthedocs.io/en/latest/notes/installation.html\nhttps://www.alecjacobson.com/weblog/?tag=qslim\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230505-v-sekai-ai-completion.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230505-v-sekai-ai-completion.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Superseded: Solve V-Sekai limitations using ChatGPT-4 AI completion.",
+    "objectID": "decisions/20211104-research-mesh-tooling-with-nglod.html#context-and-problem-statement",
+    "href": "decisions/20211104-research-mesh-tooling-with-nglod.html#context-and-problem-statement",
+    "title": "Draft: Research mesh tooling with nglod",
     "section": "",
-    "text": "Yes, leveraging AI-generated content can help improve the efficiency and effectiveness of our problem-solving process, leading to better solutions and faster development."
+    "text": "Need geometric tools for many things in the V-Sekai."
   },
   {
-    "objectID": "decisions/20230505-v-sekai-ai-completion.html#references",
-    "href": "decisions/20230505-v-sekai-ai-completion.html#references",
-    "title": "Superseded: Solve V-Sekai limitations using ChatGPT-4 AI completion.",
+    "objectID": "decisions/20211104-research-mesh-tooling-with-nglod.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20211104-research-mesh-tooling-with-nglod.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Draft: Research mesh tooling with nglod",
     "section": "",
-    "text": "V-Sekai\nGenie addon for Visual Studio Code"
+    "text": "Use nglod for some of the 3d geometric tools."
   },
   {
-    "objectID": "decisions/20210811-minecraft-voxel.html",
-    "href": "decisions/20210811-minecraft-voxel.html",
-    "title": "Proposed: Import Minecraft worlds to Godot Engine",
+    "objectID": "decisions/20211104-research-mesh-tooling-with-nglod.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20211104-research-mesh-tooling-with-nglod.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Draft: Research mesh tooling with nglod",
     "section": "",
-    "text": "Proposed: Import Minecraft worlds to Godot Engine\n\nContext and Problem Statement\nWe want more content in Godot Engine.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nWe want to import Minecraft worlds as .Vox and as standard gltf.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nSave the minecraft world.\nUse amulet_map_editor.\n\ngit clone https://github.com/Amulet-Team/Amulet-Map-Editor.git\ncd Amulet-Map-Editor\npython3 -m pip install amulet-map-editor\npython3 -m amulet_map_editor\nUse wxpython 4.x\nexport world to .schematic\nuse FileToVox\nUse fire’s vox module for godot 4.x\n\nUse Schematic and Mineways and export to .obj.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot a small number of lines.\n\n\nPositive Consequences\nMore content!\n\n\nNegative Consequences\nWorkflow changes.\n\n\nIs there a reason why this should be core and done by us?\nCan remix work by Zylann and others.\n\n\nReferences\n nova_world.zip\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject nova_world.zip to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "git clone https://github.com/nv-tlabs/nglod.git\nInstall https://github.com/conda-forge/miniforge#mambaforge\nconda create --name nglod python=3.9\nconda activate nglod\nconda install pytorch torchvision torchaudio cudatoolkit=11.3 -c pytorch\npip install -r ./infra/requirements.txt\n\npython app/main.py --net OctreeSDF --num-lods 5 --dataset-path data/armadillo.obj --epoch 250 --exp-name armadillo"
   },
   {
-    "objectID": "decisions/20210811-neural-blend-shape-rigging.html",
-    "href": "decisions/20210811-neural-blend-shape-rigging.html",
-    "title": "Proposed: Neural Blend Shape Rigging",
+    "objectID": "decisions/20211104-research-mesh-tooling-with-nglod.html#positive-consequences",
+    "href": "decisions/20211104-research-mesh-tooling-with-nglod.html#positive-consequences",
+    "title": "Draft: Research mesh tooling with nglod",
     "section": "",
-    "text": "Proposed: Neural Blend Shape Rigging\n\nContext and Problem Statement\nRigging characters takes too much effort and skill.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nUse Neural Blend Shapes to rig a base mesh.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n\nRequirements\n\nt-pose base mesh\nSimilar to the smpl_std.\n\n\n\nGet neural Blend shapes\nClone neural blend shapes\ngit clone https://github.com/PeizhuoLi/neural-blend-shapes.git\n\n\nBlender\n\nOpen your base mesh\nOpen the smpl_std.obj into the Blender mesh\nEnable the mesh align Blender addon\nSelect the rest of the meshes and then the smpl_std mesh\nAlign base_mesh.obj to the base mesh and then translate it so it stands on the floor \n\n\n\nNeural Blend Shapes\nwget https://github.com/conda-forge/miniforge/releases/latest/download/Mambaforge-pypy3-Linux-x86_64.sh\nsh Mambaforge-pypy3-Linux-x86_64.sh\nmamba create --name neural python=3.7\nmamba activate neural\nmamba install tensorboard tqdm PyTorch torchvision torchaudio -c PyTorch -y\npython demo.py --pose_file=./eval_constant/sequences/house-dance.npy --obj_path=./eval_constant/meshes/ALPAPAAM.obj --normalize=1 --animated_bvh=1 --obj_output=0\nsudo flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo\nsudo flatpak install org.blender.Blender\ncd blender_scripts\nflatpak run org.blender.Blender -b -P `pwd`/nbs_fbx_output.py -- --input `pwd`/../demo --output `pwd`/../demo/output.fbx\n\n\nUse voxel diffuse skinning\n\nThe skeleton model above weighted the eye area. This is not good.\nUse https://www.blendermarket.com/products/voxel-heat-diffuse-skinning\nTake skeleton from output.fbx and reweight it onto the original mesh set\n\n\n\nVRM\n\n\n\nimage\n\n\n\nSet bone mappings\nIn the scripting set first person json to use bone “22” for the head\nTODO Move the skeleton so it stands on the floor\n\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot workaround-able.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo finger support yet.\n\n\nIs there a reason why this should be core and done by us?\nMixamo is a black box and V-Sekai would be more robust to have an alternative.\n\n\nReferences\n\nhttps://github.com/PeizhuoLi/neural-blend-shapes\nSkeleton https://github.com/Xananax/ALPAPATAM\nMannequin https://github.com/V-Sekai/blue-tin-fox-models/actions\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Maybe possible to encode as onnx\nMaybe usable cpu only."
   },
   {
-    "objectID": "decisions/20241014-xr-interface-for-rigging.html",
-    "href": "decisions/20241014-xr-interface-for-rigging.html",
-    "title": "Proposed: Editing Character Body Bone Constraints in Immersive Mode",
+    "objectID": "decisions/20211104-research-mesh-tooling-with-nglod.html#negative-consequences",
+    "href": "decisions/20211104-research-mesh-tooling-with-nglod.html#negative-consequences",
+    "title": "Draft: Research mesh tooling with nglod",
     "section": "",
-    "text": "V-Sekai is a social VR community.\n\n\n\nWe aim to develop a prototype interface for editing bone constraints such as position, rotation, twist rotation, and swing rotation on character body bones within an immersive environment.\nInteractivity makes a difference, similar to the feeling of presence and being fully engaged with the editor. This greater flow state occurs because you don’t have to switch contexts, allowing for continuous interaction and focus.\n\n\n\n\n\nThe proposed system will allow users to interact directly with avatar bone structures in a 3D space, manipulating constraints through intuitive gestures and tools. This approach aims to enhance user engagement and precision in modifying avatars.\n\n\n\n\nVisual Representation of Bones:\n\nEach bone will be represented by a dot that becomes visible and enlarges when the user’s hand or controller approaches it, facilitating easy selection.\n\nAvoiding Selection Mechanism:\n\nInstead of using a traditional selection mechanism, the system will employ proximity-based interaction. When a user’s hand or controller is near a bone, the relevant constraints automatically appear, allowing immediate manipulation without the need for explicit selection. This reduces complexity and enhances flow in the immersive environment.\n\nConstraint Manipulation Tools:\n\nA virtual tool palette will be available to the user, containing different constraint modifiers.\nUsers can grab these tools and attach them to bones to adjust constraints like positions and rotations.\n\nTool Switcher Interface:\n\nIn addition to the tool palette, a tool switcher mechanism will be implemented allowing users to quickly switch between tools without returning to the palette. This could be activated via a gesture or a button press, bringing up a radial or linear menu to select the desired tool.\n\nIntuitive Constraint Adjustment:\n\nFor position constraints, a 3D gizmo will appear, allowing users to manipulate the position directly within the VR space.\nFor rotational constraints, a 3D gizmo will appear, allowing users to manipulate the angle directly within the VR space.\nTwist constraints will be adjusted using a 2d disk arc interface where permissible rotation areas are defined by the user.\nSwing constraints can be adjusted using a spherical interface where permissible rotation areas are defined by the user.\nSwing constraints can be adjusted using a 2d orbit map interface where permissible rotation areas are defined by the user.\n\nFeedback and Precision:\n\nVisual and haptic feedback will be provided to ensure users are aware of the changes they are making.\nPrecision tools and snapping features will help in making exact adjustments.\n\nDeselection and Context Switching:\n\nMoving the controller away from the bones or performing a specific gesture will clear the current interaction, allowing for a smooth workflow without accidental adjustments.\n\n\n\n\n\n[User Interface Mock-up]\n+------------------------------------------------+\n|                                                |\n|  [Avatar]                                      |\n|    * (Head)                                    |\n|    * (Shoulder)                                |\n|    * (Elbow) &lt;-- [Interacting]                 |\n|    * (Wrist)                                   |\n|                                                |\n|  [Tool Palette]                                |\n|    - Grab Tool                                 |\n|    - Rotate Tool                               |\n|    - Swing Tool                                |\n|    - Twist Tool                                |\n|                                                |\n|  [Tool Switcher]                               |\n|    - Quick Switch Gesture                      |\n|    - Radial Menu for Tool Selection            |\n|                                                |\n+------------------------------------------------+\n\n\n\n\n\nEnhanced User Experience: Direct manipulation of bones and constraints in VR enhances the intuitiveness and enjoyment of avatar customization.\nIncreased Precision: Fine control over adjustments leads to more accurate and satisfying results.\nSeamless Workflow: Integration of tools and interactions within the VR environment reduces the cognitive load and context switching, fostering a more creative and productive user experience.\n\n\n\n\n\nComplexity in Implementation: Developing a fully interactive 3D UI with precise control mechanisms can be challenging and time-consuming.\nPerformance Concerns: High fidelity models and real-time updates in VR may lead to performance issues on lower-end systems.\nIn a shared space app on the Apple Vision Pro neither switching or tool palette will work.\nIn an immersive app on the Apple Vision Pro either switching or tool palette will work with hand tracking.\n\n\n\n\n\n2D GUI for Constraint Management: Using a traditional 2D interface for constraint management was considered but rejected due to the lack of immersion and intuitiveness in a VR context.\n\nThe implementation of scale for matching clothing to the character’s body, as well as the adjustment of constraint weight, will be addressed in future work.\n\n\n\nThis feature is core to the V-Sekai project’s mission of enhancing VR interaction and will be developed internally to maintain control over quality and integration.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\nFire\nNova\n\n\n\n\n\nV-Sekai, interactive presence, unfolding complexity, avatar dots, maximum precision, angle constraints, twist constraint, sphere visualization, constraint palette, tool shadow, localized selection, proprioceptive action, switcher interface, tool palette, deselection method, user flow\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nV-Sekai/lasso - GitHub for vr interaction.\n\nAI assistant Aria assisted with this article."
+    "text": "Might require the GPU.\nInferencing may be difficult at interactive rates."
   },
   {
-    "objectID": "decisions/20241014-xr-interface-for-rigging.html#the-context",
-    "href": "decisions/20241014-xr-interface-for-rigging.html#the-context",
-    "title": "Proposed: Editing Character Body Bone Constraints in Immersive Mode",
+    "objectID": "decisions/20211104-research-mesh-tooling-with-nglod.html#option-graveyard",
+    "href": "decisions/20211104-research-mesh-tooling-with-nglod.html#option-graveyard",
+    "title": "Draft: Research mesh tooling with nglod",
     "section": "",
-    "text": "V-Sekai is a social VR community."
+    "text": "Option: \nRejection Reason:"
   },
   {
-    "objectID": "decisions/20241014-xr-interface-for-rigging.html#the-problem-statement",
-    "href": "decisions/20241014-xr-interface-for-rigging.html#the-problem-statement",
-    "title": "Proposed: Editing Character Body Bone Constraints in Immersive Mode",
+    "objectID": "decisions/20211104-research-mesh-tooling-with-nglod.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20211104-research-mesh-tooling-with-nglod.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Draft: Research mesh tooling with nglod",
     "section": "",
-    "text": "We aim to develop a prototype interface for editing bone constraints such as position, rotation, twist rotation, and swing rotation on character body bones within an immersive environment.\nInteractivity makes a difference, similar to the feeling of presence and being fully engaged with the editor. This greater flow state occurs because you don’t have to switch contexts, allowing for continuous interaction and focus."
+    "text": "CUDA, PyTorch and c++ are significant works."
   },
   {
-    "objectID": "decisions/20241014-xr-interface-for-rigging.html#proposal-description",
-    "href": "decisions/20241014-xr-interface-for-rigging.html#proposal-description",
-    "title": "Proposed: Editing Character Body Bone Constraints in Immersive Mode",
+    "objectID": "decisions/20211104-research-mesh-tooling-with-nglod.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20211104-research-mesh-tooling-with-nglod.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Draft: Research mesh tooling with nglod",
     "section": "",
-    "text": "The proposed system will allow users to interact directly with avatar bone structures in a 3D space, manipulating constraints through intuitive gestures and tools. This approach aims to enhance user engagement and precision in modifying avatars.\n\n\n\n\nVisual Representation of Bones:\n\nEach bone will be represented by a dot that becomes visible and enlarges when the user’s hand or controller approaches it, facilitating easy selection.\n\nAvoiding Selection Mechanism:\n\nInstead of using a traditional selection mechanism, the system will employ proximity-based interaction. When a user’s hand or controller is near a bone, the relevant constraints automatically appear, allowing immediate manipulation without the need for explicit selection. This reduces complexity and enhances flow in the immersive environment.\n\nConstraint Manipulation Tools:\n\nA virtual tool palette will be available to the user, containing different constraint modifiers.\nUsers can grab these tools and attach them to bones to adjust constraints like positions and rotations.\n\nTool Switcher Interface:\n\nIn addition to the tool palette, a tool switcher mechanism will be implemented allowing users to quickly switch between tools without returning to the palette. This could be activated via a gesture or a button press, bringing up a radial or linear menu to select the desired tool.\n\nIntuitive Constraint Adjustment:\n\nFor position constraints, a 3D gizmo will appear, allowing users to manipulate the position directly within the VR space.\nFor rotational constraints, a 3D gizmo will appear, allowing users to manipulate the angle directly within the VR space.\nTwist constraints will be adjusted using a 2d disk arc interface where permissible rotation areas are defined by the user.\nSwing constraints can be adjusted using a spherical interface where permissible rotation areas are defined by the user.\nSwing constraints can be adjusted using a 2d orbit map interface where permissible rotation areas are defined by the user.\n\nFeedback and Precision:\n\nVisual and haptic feedback will be provided to ensure users are aware of the changes they are making.\nPrecision tools and snapping features will help in making exact adjustments.\n\nDeselection and Context Switching:\n\nMoving the controller away from the bones or performing a specific gesture will clear the current interaction, allowing for a smooth workflow without accidental adjustments.\n\n\n\n\n\n[User Interface Mock-up]\n+------------------------------------------------+\n|                                                |\n|  [Avatar]                                      |\n|    * (Head)                                    |\n|    * (Shoulder)                                |\n|    * (Elbow) &lt;-- [Interacting]                 |\n|    * (Wrist)                                   |\n|                                                |\n|  [Tool Palette]                                |\n|    - Grab Tool                                 |\n|    - Rotate Tool                               |\n|    - Swing Tool                                |\n|    - Twist Tool                                |\n|                                                |\n|  [Tool Switcher]                               |\n|    - Quick Switch Gesture                      |\n|    - Radial Menu for Tool Selection            |\n|                                                |\n+------------------------------------------------+"
+    "text": "I have an approach!"
   },
   {
-    "objectID": "decisions/20241014-xr-interface-for-rigging.html#benefits",
-    "href": "decisions/20241014-xr-interface-for-rigging.html#benefits",
-    "title": "Proposed: Editing Character Body Bone Constraints in Immersive Mode",
+    "objectID": "decisions/20211104-research-mesh-tooling-with-nglod.html#references",
+    "href": "decisions/20211104-research-mesh-tooling-with-nglod.html#references",
+    "title": "Draft: Research mesh tooling with nglod",
     "section": "",
-    "text": "Enhanced User Experience: Direct manipulation of bones and constraints in VR enhances the intuitiveness and enjoyment of avatar customization.\nIncreased Precision: Fine control over adjustments leads to more accurate and satisfying results.\nSeamless Workflow: Integration of tools and interactions within the VR environment reduces the cognitive load and context switching, fostering a more creative and productive user experience."
+    "text": "https://kaolin.readthedocs.io/en/latest/notes/installation.html\nhttps://www.alecjacobson.com/weblog/?tag=qslim"
   },
   {
-    "objectID": "decisions/20241014-xr-interface-for-rigging.html#downsides",
-    "href": "decisions/20241014-xr-interface-for-rigging.html#downsides",
-    "title": "Proposed: Editing Character Body Bone Constraints in Immersive Mode",
+    "objectID": "decisions/20211104-research-mesh-tooling-with-nglod.html#derivative-license",
+    "href": "decisions/20211104-research-mesh-tooling-with-nglod.html#derivative-license",
+    "title": "Draft: Research mesh tooling with nglod",
     "section": "",
-    "text": "Complexity in Implementation: Developing a fully interactive 3D UI with precise control mechanisms can be challenging and time-consuming.\nPerformance Concerns: High fidelity models and real-time updates in VR may lead to performance issues on lower-end systems.\nIn a shared space app on the Apple Vision Pro neither switching or tool palette will work.\nIn an immersive app on the Apple Vision Pro either switching or tool palette will work with hand tracking."
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20241014-xr-interface-for-rigging.html#the-road-not-taken",
-    "href": "decisions/20241014-xr-interface-for-rigging.html#the-road-not-taken",
-    "title": "Proposed: Editing Character Body Bone Constraints in Immersive Mode",
+    "objectID": "decisions/20240623-do-cdn-for-launcher.html",
+    "href": "decisions/20240623-do-cdn-for-launcher.html",
+    "title": "Proposed: Use GitHub Actions and Digital Ocean Spaces for a V-Sekai Launcher",
     "section": "",
-    "text": "2D GUI for Constraint Management: Using a traditional 2D interface for constraint management was considered but rejected due to the lack of immersion and intuitiveness in a VR context.\n\nThe implementation of scale for matching clothing to the character’s body, as well as the adjustment of constraint weight, will be addressed in future work."
+    "text": "V-Sekai is an open-source project that brings social VR/VRSNS/metaverse components to the Godot Engine. The current setup for providing a launcher to players via itch.io is too complicated and needs simplification.\n\n\n\nWe need a more streamlined process to provide a launcher to players.\n\n\n\nLeverage GitHub Actions to build the launcher and then upload it to Digital Ocean Spaces using the casync protocol (with the Desync golang library). This approach will replace the current reliance on gocd.\n\n\n\n\nSimplified deployment process.\nReduced dependency on other developers.\nUtilization of familiar and widely-used technologies (GitHub Actions, Digital Ocean Spaces).\n\n\n\n\nThe potential downsides could include:\n\nLearning curve associated with new technologies for some team members.\nPotential costs associated with using Digital Ocean Spaces.\nPossible limitations or issues with the cassync protocol or the Desync golang library.\n\n\n\n\nAlternative solutions such as continuing with the itch.io setup or exploring other cloud storage services were considered. However, they were not chosen due to their complexity or potential cost implications.\n\n\n\nThis solution might not be optimal in scenarios where there are significant changes in the game’s codebase that would require substantial modifications to the GitHub Actions scripts.\n\n\n\nThis proposal is core to the V-Sekai project and will be implemented by the V-Sekai development team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20241014-xr-interface-for-rigging.html#in-core-and-done-by-us",
-    "href": "decisions/20241014-xr-interface-for-rigging.html#in-core-and-done-by-us",
-    "title": "Proposed: Editing Character Body Bone Constraints in Immersive Mode",
+    "objectID": "decisions/20240623-do-cdn-for-launcher.html#context",
+    "href": "decisions/20240623-do-cdn-for-launcher.html#context",
+    "title": "Proposed: Use GitHub Actions and Digital Ocean Spaces for a V-Sekai Launcher",
     "section": "",
-    "text": "This feature is core to the V-Sekai project’s mission of enhancing VR interaction and will be developed internally to maintain control over quality and integration."
+    "text": "V-Sekai is an open-source project that brings social VR/VRSNS/metaverse components to the Godot Engine. The current setup for providing a launcher to players via itch.io is too complicated and needs simplification."
   },
   {
-    "objectID": "decisions/20241014-xr-interface-for-rigging.html#status",
-    "href": "decisions/20241014-xr-interface-for-rigging.html#status",
-    "title": "Proposed: Editing Character Body Bone Constraints in Immersive Mode",
+    "objectID": "decisions/20240623-do-cdn-for-launcher.html#problem-statement",
+    "href": "decisions/20240623-do-cdn-for-launcher.html#problem-statement",
+    "title": "Proposed: Use GitHub Actions and Digital Ocean Spaces for a V-Sekai Launcher",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "We need a more streamlined process to provide a launcher to players."
   },
   {
-    "objectID": "decisions/20241014-xr-interface-for-rigging.html#decision-makers",
-    "href": "decisions/20241014-xr-interface-for-rigging.html#decision-makers",
-    "title": "Proposed: Editing Character Body Bone Constraints in Immersive Mode",
+    "objectID": "decisions/20240623-do-cdn-for-launcher.html#proposal",
+    "href": "decisions/20240623-do-cdn-for-launcher.html#proposal",
+    "title": "Proposed: Use GitHub Actions and Digital Ocean Spaces for a V-Sekai Launcher",
     "section": "",
-    "text": "V-Sekai development team\nFire\nNova"
+    "text": "Leverage GitHub Actions to build the launcher and then upload it to Digital Ocean Spaces using the casync protocol (with the Desync golang library). This approach will replace the current reliance on gocd."
   },
   {
-    "objectID": "decisions/20241014-xr-interface-for-rigging.html#tags",
-    "href": "decisions/20241014-xr-interface-for-rigging.html#tags",
-    "title": "Proposed: Editing Character Body Bone Constraints in Immersive Mode",
+    "objectID": "decisions/20240623-do-cdn-for-launcher.html#benefits",
+    "href": "decisions/20240623-do-cdn-for-launcher.html#benefits",
+    "title": "Proposed: Use GitHub Actions and Digital Ocean Spaces for a V-Sekai Launcher",
     "section": "",
-    "text": "V-Sekai, interactive presence, unfolding complexity, avatar dots, maximum precision, angle constraints, twist constraint, sphere visualization, constraint palette, tool shadow, localized selection, proprioceptive action, switcher interface, tool palette, deselection method, user flow"
+    "text": "Simplified deployment process.\nReduced dependency on other developers.\nUtilization of familiar and widely-used technologies (GitHub Actions, Digital Ocean Spaces)."
   },
   {
-    "objectID": "decisions/20241014-xr-interface-for-rigging.html#further-reading",
-    "href": "decisions/20241014-xr-interface-for-rigging.html#further-reading",
-    "title": "Proposed: Editing Character Body Bone Constraints in Immersive Mode",
+    "objectID": "decisions/20240623-do-cdn-for-launcher.html#downsides",
+    "href": "decisions/20240623-do-cdn-for-launcher.html#downsides",
+    "title": "Proposed: Use GitHub Actions and Digital Ocean Spaces for a V-Sekai Launcher",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nV-Sekai/lasso - GitHub for vr interaction.\n\nAI assistant Aria assisted with this article."
+    "text": "The potential downsides could include:\n\nLearning curve associated with new technologies for some team members.\nPotential costs associated with using Digital Ocean Spaces.\nPossible limitations or issues with the cassync protocol or the Desync golang library."
   },
   {
-    "objectID": "decisions/20230523-marketing-cycle.html",
-    "href": "decisions/20230523-marketing-cycle.html",
-    "title": "Draft: Improve V-Sekai marketing",
+    "objectID": "decisions/20240623-do-cdn-for-launcher.html#the-road-not-taken",
+    "href": "decisions/20240623-do-cdn-for-launcher.html#the-road-not-taken",
+    "title": "Proposed: Use GitHub Actions and Digital Ocean Spaces for a V-Sekai Launcher",
     "section": "",
-    "text": "Status: draft \nDeciders: V-Sekai\nTags: V-Sekai, GPT-4\n\n\n\n\nV-Sekai is a virtual world platform that allows users to create, explore, and interact with others in various immersive environments.\nV-Sekai is facing a limitation in its marketing efforts. The challenge is to find a way to make marketing more manageable and effective for V-Sekai.\n\n\n\n\nStrategy\nPositioning\nMessaging\nExperimentation\n\nThe first three steps are initial preparations that create a strong foundation for marketing efforts. The fourth step, Experimentation, is a recurring process that helps us continuously improve our marketing strategies.\n\n\n\n\n\nDefine the overall marketing strategy by identifying target audiences, setting goals, and determining the best channels to reach potential customers.\n\n\n\nEstablish a unique selling proposition (USP) that sets the product or service apart from competitors. This will help potential customers understand why they should choose the offering over others in the market.\n\n\n\nDevelop clear and compelling messaging that communicates the USP and resonates with the target audience. This messaging should be consistent across all marketing channels.\n\n\n\nConduct regular experiments to test and refine marketing tactics. This can include A/B testing, trying new channels, or adjusting messaging. Analyze the results of these experiments and use the insights gained to improve future marketing efforts.\n\n\n\n\n\nImproved marketing effectiveness for V-Sekai\nBetter time management and prioritization of tasks\nIncreased revenue and business growth\n\n\n\n\n\nPotential initial time investment in setting up the marketing habit\nPossible resistance to change or adopting new habits\n\n\n\n\nDo nothing.\n\n\n\nNo, this marketing strategy is a comprehensive marketing approach that requires ongoing commitment and cannot be replaced by a simple script.\n\n\n\nYes, as the creators and maintainers of V-Sekai, we have the best understanding of our product and target audience. By taking charge of our marketing efforts, we can ensure that our messaging and strategies align with our goals and vision, ultimately leading to better results.\n\n\n\n\nV-Sekai\nMaterial from 2quiet2market"
+    "text": "Alternative solutions such as continuing with the itch.io setup or exploring other cloud storage services were considered. However, they were not chosen due to their complexity or potential cost implications."
   },
   {
-    "objectID": "decisions/20230523-marketing-cycle.html#metadata",
-    "href": "decisions/20230523-marketing-cycle.html#metadata",
-    "title": "Draft: Improve V-Sekai marketing",
+    "objectID": "decisions/20240623-do-cdn-for-launcher.html#the-infrequent-use-case",
+    "href": "decisions/20240623-do-cdn-for-launcher.html#the-infrequent-use-case",
+    "title": "Proposed: Use GitHub Actions and Digital Ocean Spaces for a V-Sekai Launcher",
     "section": "",
-    "text": "Status: draft \nDeciders: V-Sekai\nTags: V-Sekai, GPT-4"
+    "text": "This solution might not be optimal in scenarios where there are significant changes in the game’s codebase that would require substantial modifications to the GitHub Actions scripts."
   },
   {
-    "objectID": "decisions/20230523-marketing-cycle.html#context-and-problem-statement",
-    "href": "decisions/20230523-marketing-cycle.html#context-and-problem-statement",
-    "title": "Draft: Improve V-Sekai marketing",
+    "objectID": "decisions/20240623-do-cdn-for-launcher.html#in-core-and-done-by-us",
+    "href": "decisions/20240623-do-cdn-for-launcher.html#in-core-and-done-by-us",
+    "title": "Proposed: Use GitHub Actions and Digital Ocean Spaces for a V-Sekai Launcher",
     "section": "",
-    "text": "V-Sekai is a virtual world platform that allows users to create, explore, and interact with others in various immersive environments.\nV-Sekai is facing a limitation in its marketing efforts. The challenge is to find a way to make marketing more manageable and effective for V-Sekai."
+    "text": "This proposal is core to the V-Sekai project and will be implemented by the V-Sekai development team."
   },
   {
-    "objectID": "decisions/20230523-marketing-cycle.html#proposed-solution",
-    "href": "decisions/20230523-marketing-cycle.html#proposed-solution",
-    "title": "Draft: Improve V-Sekai marketing",
+    "objectID": "decisions/20240623-do-cdn-for-launcher.html#status",
+    "href": "decisions/20240623-do-cdn-for-launcher.html#status",
+    "title": "Proposed: Use GitHub Actions and Digital Ocean Spaces for a V-Sekai Launcher",
     "section": "",
-    "text": "Strategy\nPositioning\nMessaging\nExperimentation\n\nThe first three steps are initial preparations that create a strong foundation for marketing efforts. The fourth step, Experimentation, is a recurring process that helps us continuously improve our marketing strategies."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20230523-marketing-cycle.html#implementation",
-    "href": "decisions/20230523-marketing-cycle.html#implementation",
-    "title": "Draft: Improve V-Sekai marketing",
+    "objectID": "decisions/20240623-do-cdn-for-launcher.html#decision-makers",
+    "href": "decisions/20240623-do-cdn-for-launcher.html#decision-makers",
+    "title": "Proposed: Use GitHub Actions and Digital Ocean Spaces for a V-Sekai Launcher",
     "section": "",
-    "text": "Define the overall marketing strategy by identifying target audiences, setting goals, and determining the best channels to reach potential customers.\n\n\n\nEstablish a unique selling proposition (USP) that sets the product or service apart from competitors. This will help potential customers understand why they should choose the offering over others in the market.\n\n\n\nDevelop clear and compelling messaging that communicates the USP and resonates with the target audience. This messaging should be consistent across all marketing channels.\n\n\n\nConduct regular experiments to test and refine marketing tactics. This can include A/B testing, trying new channels, or adjusting messaging. Analyze the results of these experiments and use the insights gained to improve future marketing efforts."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20230523-marketing-cycle.html#positive-consequences",
-    "href": "decisions/20230523-marketing-cycle.html#positive-consequences",
-    "title": "Draft: Improve V-Sekai marketing",
+    "objectID": "decisions/20240623-do-cdn-for-launcher.html#tags",
+    "href": "decisions/20240623-do-cdn-for-launcher.html#tags",
+    "title": "Proposed: Use GitHub Actions and Digital Ocean Spaces for a V-Sekai Launcher",
     "section": "",
-    "text": "Improved marketing effectiveness for V-Sekai\nBetter time management and prioritization of tasks\nIncreased revenue and business growth"
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20230523-marketing-cycle.html#negative-consequences",
-    "href": "decisions/20230523-marketing-cycle.html#negative-consequences",
-    "title": "Draft: Improve V-Sekai marketing",
+    "objectID": "decisions/20240623-do-cdn-for-launcher.html#further-reading",
+    "href": "decisions/20240623-do-cdn-for-launcher.html#further-reading",
+    "title": "Proposed: Use GitHub Actions and Digital Ocean Spaces for a V-Sekai Launcher",
     "section": "",
-    "text": "Potential initial time investment in setting up the marketing habit\nPossible resistance to change or adopting new habits"
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20230523-marketing-cycle.html#option-graveyard",
-    "href": "decisions/20230523-marketing-cycle.html#option-graveyard",
-    "title": "Draft: Improve V-Sekai marketing",
+    "objectID": "decisions/20231022-hover-to-ocean-game.html",
+    "href": "decisions/20231022-hover-to-ocean-game.html",
+    "title": "Proposed: Navigating New Horizons: A Proposal for Expanding Exploration in V-Sekai",
     "section": "",
-    "text": "Do nothing."
+    "text": "Status: Proposed\nDeciders: V-Sekai, fire, cyberpunkmermaid\nTags: V-Sekai\n\n\n\n\nThe player starts with a hovercar and uses an upgrade to transform it into a hover submarine for ocean exploration. This involves navigating through surreal landscapes, encountering storms, avoiding volcanic eruptions, exploring coral reefs, and finally reaching a new island.\n\n\n\nThe main challenge lies in transitioning from land to underwater exploration while maintaining an engaging experience for the player. Creating diverse and interactive environments such as the cyber surrealist/impressionist voxel blocks landscape and the vibrant coral reef poses its own set of challenges.\n\n\n\nWe can use voxel-based rendering for creating the surreal landscapes and procedural generation for creating diverse marine life in the coral reef. For the transition from hovercar to hover submarine, we can design a special animation sequence that showcases the transformation.\n\n\n\nImplementing this would result in a unique and engaging gaming experience that combines elements of exploration, adventure, and survival. It would also showcase the capabilities of V-Sekai in creating diverse and immersive virtual worlds.\n\n\n\nThe complexity involved in implementing the proposed features would require significant resources and expertise. There’s also a risk that the final product may not meet the expectations due to technical limitations or unforeseen challenges.\n\n\n\nAn alternative approach could be to simplify the journey by limiting the number of environments or removing the transformation aspect. However, this would likely result in a less engaging experience for the player.\n\n\n\nYes, this proposal aligns with the core values of V-Sekai and can be implemented by our team with the right resources and planning.\n\n\n\n\nV-Sekai"
   },
   {
-    "objectID": "decisions/20230523-marketing-cycle.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230523-marketing-cycle.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Draft: Improve V-Sekai marketing",
+    "objectID": "decisions/20231022-hover-to-ocean-game.html#metadata",
+    "href": "decisions/20231022-hover-to-ocean-game.html#metadata",
+    "title": "Proposed: Navigating New Horizons: A Proposal for Expanding Exploration in V-Sekai",
     "section": "",
-    "text": "No, this marketing strategy is a comprehensive marketing approach that requires ongoing commitment and cannot be replaced by a simple script."
+    "text": "Status: Proposed\nDeciders: V-Sekai, fire, cyberpunkmermaid\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20230523-marketing-cycle.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230523-marketing-cycle.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Draft: Improve V-Sekai marketing",
+    "objectID": "decisions/20231022-hover-to-ocean-game.html#the-backdrop",
+    "href": "decisions/20231022-hover-to-ocean-game.html#the-backdrop",
+    "title": "Proposed: Navigating New Horizons: A Proposal for Expanding Exploration in V-Sekai",
     "section": "",
-    "text": "Yes, as the creators and maintainers of V-Sekai, we have the best understanding of our product and target audience. By taking charge of our marketing efforts, we can ensure that our messaging and strategies align with our goals and vision, ultimately leading to better results."
+    "text": "The player starts with a hovercar and uses an upgrade to transform it into a hover submarine for ocean exploration. This involves navigating through surreal landscapes, encountering storms, avoiding volcanic eruptions, exploring coral reefs, and finally reaching a new island."
   },
   {
-    "objectID": "decisions/20230523-marketing-cycle.html#references",
-    "href": "decisions/20230523-marketing-cycle.html#references",
-    "title": "Draft: Improve V-Sekai marketing",
+    "objectID": "decisions/20231022-hover-to-ocean-game.html#the-challenge",
+    "href": "decisions/20231022-hover-to-ocean-game.html#the-challenge",
+    "title": "Proposed: Navigating New Horizons: A Proposal for Expanding Exploration in V-Sekai",
     "section": "",
-    "text": "V-Sekai\nMaterial from 2quiet2market"
+    "text": "The main challenge lies in transitioning from land to underwater exploration while maintaining an engaging experience for the player. Creating diverse and interactive environments such as the cyber surrealist/impressionist voxel blocks landscape and the vibrant coral reef poses its own set of challenges."
   },
   {
-    "objectID": "decisions/20240623-only-save-tools-in-our-cdn.html",
-    "href": "decisions/20240623-only-save-tools-in-our-cdn.html",
-    "title": "Proposal: Only Save Tools in Our CDN",
+    "objectID": "decisions/20231022-hover-to-ocean-game.html#the-strategy",
+    "href": "decisions/20231022-hover-to-ocean-game.html#the-strategy",
+    "title": "Proposed: Navigating New Horizons: A Proposal for Expanding Exploration in V-Sekai",
     "section": "",
-    "text": "Currently, our Content Delivery Network (CDN) is responsible for storing a variety of assets. These include home world props, avatars, worlds, V-Sekai tools, and our sources.\n\n\n\nThe main issue we face is the need to optimize storage space while ensuring that essential tools are readily accessible for use.\n\n\n\nOur proposed solution is to limit the types of assets stored in our CDN. Specifically, we suggest not saving home world props, avatars, or worlds in our CDN. This would help conserve storage space. Instead, we would focus on storing only the V-Sekai tools and our tool sources. The underlying idea is that homeworlds should be responsible for storing their own content.\n\n\n\nThis strategy ensures the sovereignty of the content by allowing each homeworld to manage its own assets.\n\n\n\nThere may be potential issues with accessibility and latency as homeworlds will have to manage their own content delivery.\n\n\n\nAn alternative approach could have been to upgrade our CDN to accommodate all types of assets. However, this would increase costs and still not address the issue of content sovereignty.\n\n\n\nIn cases where a homeworld’s server is down or experiencing issues, users might not be able to access certain assets.\n\n\n\nThe implementation of this proposal will be done by us, the V-Sekai development team. It aligns with our core principle of decentralization and user empowerment.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis proposal was assisted by AI assistant Aria."
+    "text": "We can use voxel-based rendering for creating the surreal landscapes and procedural generation for creating diverse marine life in the coral reef. For the transition from hovercar to hover submarine, we can design a special animation sequence that showcases the transformation."
   },
   {
-    "objectID": "decisions/20240623-only-save-tools-in-our-cdn.html#context",
-    "href": "decisions/20240623-only-save-tools-in-our-cdn.html#context",
-    "title": "Proposal: Only Save Tools in Our CDN",
+    "objectID": "decisions/20231022-hover-to-ocean-game.html#the-upside",
+    "href": "decisions/20231022-hover-to-ocean-game.html#the-upside",
+    "title": "Proposed: Navigating New Horizons: A Proposal for Expanding Exploration in V-Sekai",
     "section": "",
-    "text": "Currently, our Content Delivery Network (CDN) is responsible for storing a variety of assets. These include home world props, avatars, worlds, V-Sekai tools, and our sources."
+    "text": "Implementing this would result in a unique and engaging gaming experience that combines elements of exploration, adventure, and survival. It would also showcase the capabilities of V-Sekai in creating diverse and immersive virtual worlds."
   },
   {
-    "objectID": "decisions/20240623-only-save-tools-in-our-cdn.html#problem-statement",
-    "href": "decisions/20240623-only-save-tools-in-our-cdn.html#problem-statement",
-    "title": "Proposal: Only Save Tools in Our CDN",
+    "objectID": "decisions/20231022-hover-to-ocean-game.html#the-downside",
+    "href": "decisions/20231022-hover-to-ocean-game.html#the-downside",
+    "title": "Proposed: Navigating New Horizons: A Proposal for Expanding Exploration in V-Sekai",
     "section": "",
-    "text": "The main issue we face is the need to optimize storage space while ensuring that essential tools are readily accessible for use."
+    "text": "The complexity involved in implementing the proposed features would require significant resources and expertise. There’s also a risk that the final product may not meet the expectations due to technical limitations or unforeseen challenges."
   },
   {
-    "objectID": "decisions/20240623-only-save-tools-in-our-cdn.html#proposed-solution",
-    "href": "decisions/20240623-only-save-tools-in-our-cdn.html#proposed-solution",
-    "title": "Proposal: Only Save Tools in Our CDN",
+    "objectID": "decisions/20231022-hover-to-ocean-game.html#the-road-not-taken",
+    "href": "decisions/20231022-hover-to-ocean-game.html#the-road-not-taken",
+    "title": "Proposed: Navigating New Horizons: A Proposal for Expanding Exploration in V-Sekai",
     "section": "",
-    "text": "Our proposed solution is to limit the types of assets stored in our CDN. Specifically, we suggest not saving home world props, avatars, or worlds in our CDN. This would help conserve storage space. Instead, we would focus on storing only the V-Sekai tools and our tool sources. The underlying idea is that homeworlds should be responsible for storing their own content."
+    "text": "An alternative approach could be to simplify the journey by limiting the number of environments or removing the transformation aspect. However, this would likely result in a less engaging experience for the player."
   },
   {
-    "objectID": "decisions/20240623-only-save-tools-in-our-cdn.html#benefits",
-    "href": "decisions/20240623-only-save-tools-in-our-cdn.html#benefits",
-    "title": "Proposal: Only Save Tools in Our CDN",
+    "objectID": "decisions/20231022-hover-to-ocean-game.html#in-core-and-done-by-us",
+    "href": "decisions/20231022-hover-to-ocean-game.html#in-core-and-done-by-us",
+    "title": "Proposed: Navigating New Horizons: A Proposal for Expanding Exploration in V-Sekai",
     "section": "",
-    "text": "This strategy ensures the sovereignty of the content by allowing each homeworld to manage its own assets."
+    "text": "Yes, this proposal aligns with the core values of V-Sekai and can be implemented by our team with the right resources and planning."
   },
   {
-    "objectID": "decisions/20240623-only-save-tools-in-our-cdn.html#downsides",
-    "href": "decisions/20240623-only-save-tools-in-our-cdn.html#downsides",
-    "title": "Proposal: Only Save Tools in Our CDN",
+    "objectID": "decisions/20231022-hover-to-ocean-game.html#further-reading",
+    "href": "decisions/20231022-hover-to-ocean-game.html#further-reading",
+    "title": "Proposed: Navigating New Horizons: A Proposal for Expanding Exploration in V-Sekai",
     "section": "",
-    "text": "There may be potential issues with accessibility and latency as homeworlds will have to manage their own content delivery."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20240623-only-save-tools-in-our-cdn.html#the-road-not-taken",
-    "href": "decisions/20240623-only-save-tools-in-our-cdn.html#the-road-not-taken",
-    "title": "Proposal: Only Save Tools in Our CDN",
+    "objectID": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html",
+    "href": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html",
+    "title": "Accepted: Complete glTF2 / VRM import and export pipeline in Godot Engine",
     "section": "",
-    "text": "An alternative approach could have been to upgrade our CDN to accommodate all types of assets. However, this would increase costs and still not address the issue of content sovereignty."
+    "text": "We are unable to import characters in animations and unable to export them.\n\n\n\nVRM and glTF import allows us to bring models in and export allows us to get the models out.\n\n\n\nTo be determined.\n\n\n\n\nCharacter import supports\nWorld export support\n\n\n\n\n\nTechnical debt\n\n(this section can be repeated for each option, if more than one option is open for consideration\n\n\n\nList the proposed options no longer open for consideration.\nList the reasons for the rejection: (the Bad traits)\n\nRequires GDNative\nComplicated\n\n\n\n\nPossible to be gdscript\n\n\n\nWe need to provide trust for the toolchains.\n\n\n\n\nNotary Trust\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240623-only-save-tools-in-our-cdn.html#the-infrequent-use-case",
-    "href": "decisions/20240623-only-save-tools-in-our-cdn.html#the-infrequent-use-case",
-    "title": "Proposal: Only Save Tools in Our CDN",
+    "objectID": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html#context-and-problem-statement",
+    "href": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html#context-and-problem-statement",
+    "title": "Accepted: Complete glTF2 / VRM import and export pipeline in Godot Engine",
     "section": "",
-    "text": "In cases where a homeworld’s server is down or experiencing issues, users might not be able to access certain assets."
+    "text": "We are unable to import characters in animations and unable to export them."
   },
   {
-    "objectID": "decisions/20240623-only-save-tools-in-our-cdn.html#in-core-and-done-by-us",
-    "href": "decisions/20240623-only-save-tools-in-our-cdn.html#in-core-and-done-by-us",
-    "title": "Proposal: Only Save Tools in Our CDN",
+    "objectID": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Accepted: Complete glTF2 / VRM import and export pipeline in Godot Engine",
     "section": "",
-    "text": "The implementation of this proposal will be done by us, the V-Sekai development team. It aligns with our core principle of decentralization and user empowerment."
+    "text": "VRM and glTF import allows us to bring models in and export allows us to get the models out."
   },
   {
-    "objectID": "decisions/20240623-only-save-tools-in-our-cdn.html#status",
-    "href": "decisions/20240623-only-save-tools-in-our-cdn.html#status",
-    "title": "Proposal: Only Save Tools in Our CDN",
+    "objectID": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-andor-diagrams",
+    "href": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-andor-diagrams",
+    "title": "Accepted: Complete glTF2 / VRM import and export pipeline in Godot Engine",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "To be determined."
   },
   {
-    "objectID": "decisions/20240623-only-save-tools-in-our-cdn.html#decision-makers",
-    "href": "decisions/20240623-only-save-tools-in-our-cdn.html#decision-makers",
-    "title": "Proposal: Only Save Tools in Our CDN",
+    "objectID": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html#positive-consequences",
+    "href": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html#positive-consequences",
+    "title": "Accepted: Complete glTF2 / VRM import and export pipeline in Godot Engine",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "Character import supports\nWorld export support"
   },
   {
-    "objectID": "decisions/20240623-only-save-tools-in-our-cdn.html#tags",
-    "href": "decisions/20240623-only-save-tools-in-our-cdn.html#tags",
-    "title": "Proposal: Only Save Tools in Our CDN",
+    "objectID": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html#negative-consequences",
+    "href": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html#negative-consequences",
+    "title": "Accepted: Complete glTF2 / VRM import and export pipeline in Godot Engine",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Technical debt\n\n(this section can be repeated for each option, if more than one option is open for consideration"
   },
   {
-    "objectID": "decisions/20240623-only-save-tools-in-our-cdn.html#further-reading",
-    "href": "decisions/20240623-only-save-tools-in-our-cdn.html#further-reading",
-    "title": "Proposal: Only Save Tools in Our CDN",
+    "objectID": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html#option-graveyard-usdz",
+    "href": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html#option-graveyard-usdz",
+    "title": "Accepted: Complete glTF2 / VRM import and export pipeline in Godot Engine",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis proposal was assisted by AI assistant Aria."
+    "text": "List the proposed options no longer open for consideration.\nList the reasons for the rejection: (the Bad traits)\n\nRequires GDNative\nComplicated"
   },
   {
-    "objectID": "decisions/20220131-run-own-infrastructure.html",
-    "href": "decisions/20220131-run-own-infrastructure.html",
-    "title": "Rejected: To allow independent deployment run our own infrastructure",
+    "objectID": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Accepted: Complete glTF2 / VRM import and export pipeline in Godot Engine",
     "section": "",
-    "text": "Status: rejected \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nIt needs to be possible to replicate (or substitute) all of the existing infrasture and setup. This is important for a few reasons:\n\nThe current host may disappear or the physical hardware could break (as it is not in a cloud)\nPart of our project’s purpose is to allow anyone to fork the project or run their own version V-Sekai however they want.\nAs a use for “staging” or testing changes to infrastructure.\nAs a means for replicating live data such as CDN content, metadata or other databases. (some assets may depend on other assets in the future)\n\n\n\n\n\nRun TrueNAS Scale in DigitalOcean (Droplet/standalone VM, not kubernetes).\n(It should be possible in other cloud providers, and on own infrastructure, but we will pick this environment to focus on)\nWrite TrueNAS Scale charts for gocd; cockroachdb; uro\nLetsEncrypt certs require open port 443 or 80 for http01; or any dns01 provider using a plugin.\nTrueNAS Scale supports backups and snapshots.\n\n\n\n\n\nCreate new droplet. (Minimum configuration????):\n\nCustom Image -&gt; pick our TrueNAS image or some custom one we make.\nBasic: pick a number of cpus. Direct storage is only used for the OS.\nAdd a block volume for $10. TrueNAS requires a separate block device.\nDo not enable backups because TrueNAS has its own backup systems.\n\nAdd one extra block volume after the machine spins up to get redundancy (RAID-1?)\n(Note that block volumes can be moved between VMs, so doing things this way gives pretty good redundancy.\n\n\n\n\n\nGiving people many ways to remix, host or fork our work is part of our mission.\nIt will give us a way to quickly spin up redundant infrastructure in the cloud, either if a disaster happens or we want to scale.\n\n\n\n\n\nSupporting more configurations will take more time from us.\n\n[this section can be repeated for each option if more than one option is open for consideration]\n\n\n\n\nOption: Support only bare metal infrastructure\nRejection Reason: This is not ideal unless you are at scale, because bare metal can die and cannot scale.\n\n\n\n\nThis project is to document what the script will be\n\n\n\nInfra is part of our mission.\n\n\n\n\nhttps://docs.digitalocean.com/products/volumes/how-to/move-between-droplets/\n\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Possible to be gdscript"
   },
   {
-    "objectID": "decisions/20220131-run-own-infrastructure.html#context-and-problem-statement",
-    "href": "decisions/20220131-run-own-infrastructure.html#context-and-problem-statement",
-    "title": "Rejected: To allow independent deployment run our own infrastructure",
+    "objectID": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Accepted: Complete glTF2 / VRM import and export pipeline in Godot Engine",
     "section": "",
-    "text": "It needs to be possible to replicate (or substitute) all of the existing infrasture and setup. This is important for a few reasons:\n\nThe current host may disappear or the physical hardware could break (as it is not in a cloud)\nPart of our project’s purpose is to allow anyone to fork the project or run their own version V-Sekai however they want.\nAs a use for “staging” or testing changes to infrastructure.\nAs a means for replicating live data such as CDN content, metadata or other databases. (some assets may depend on other assets in the future)"
+    "text": "We need to provide trust for the toolchains."
   },
   {
-    "objectID": "decisions/20220131-run-own-infrastructure.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20220131-run-own-infrastructure.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Rejected: To allow independent deployment run our own infrastructure",
+    "objectID": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html#references",
+    "href": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html#references",
+    "title": "Accepted: Complete glTF2 / VRM import and export pipeline in Godot Engine",
     "section": "",
-    "text": "Run TrueNAS Scale in DigitalOcean (Droplet/standalone VM, not kubernetes).\n(It should be possible in other cloud providers, and on own infrastructure, but we will pick this environment to focus on)\nWrite TrueNAS Scale charts for gocd; cockroachdb; uro\nLetsEncrypt certs require open port 443 or 80 for http01; or any dns01 provider using a plugin.\nTrueNAS Scale supports backups and snapshots."
+    "text": "Notary Trust"
   },
   {
-    "objectID": "decisions/20220131-run-own-infrastructure.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20220131-run-own-infrastructure.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Rejected: To allow independent deployment run our own infrastructure",
+    "objectID": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html#derivative-license",
+    "href": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html#derivative-license",
+    "title": "Accepted: Complete glTF2 / VRM import and export pipeline in Godot Engine",
     "section": "",
-    "text": "Create new droplet. (Minimum configuration????):\n\nCustom Image -&gt; pick our TrueNAS image or some custom one we make.\nBasic: pick a number of cpus. Direct storage is only used for the OS.\nAdd a block volume for $10. TrueNAS requires a separate block device.\nDo not enable backups because TrueNAS has its own backup systems.\n\nAdd one extra block volume after the machine spins up to get redundancy (RAID-1?)\n(Note that block volumes can be moved between VMs, so doing things this way gives pretty good redundancy."
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20220131-run-own-infrastructure.html#positive-consequences",
-    "href": "decisions/20220131-run-own-infrastructure.html#positive-consequences",
-    "title": "Rejected: To allow independent deployment run our own infrastructure",
+    "objectID": "decisions/20230527-server-sidecar.html",
+    "href": "decisions/20230527-server-sidecar.html",
+    "title": "Proposed: Efficiently managing and synchronizing game data with a server sidecar",
     "section": "",
-    "text": "Giving people many ways to remix, host or fork our work is part of our mission.\nIt will give us a way to quickly spin up redundant infrastructure in the cloud, either if a disaster happens or we want to scale."
+    "text": "Status: proposed\nDeciders: V-Sekai, Bioblaze Payne, fire\nTags: V-Sekai, GPT-4\n\n\n\n\nV-Sekai is facing a problem with efficiently managing and synchronizing data across multiple devices and platforms.\nThe goal is to find a more reliable and efficient solution for data synchronization that can handle large amounts of data, minimize latency, and ensure data consistency across all devices and platforms.\n\n\n\nWe propose a new approach that involves directly inserting data into the MVSQLite cluster database and implementing a robust syncing mechanism to ensure data consistency across all devices and platforms.\n\nModify the editor export process to stream MVSQLite to the Godot Engine server.\nSchedule externally consistent syncing of MVSQLite with the Godot Engine server (1 frame).\nSchedule periodic syncing of MVSQLite to a backup (e.g., every 30 minutes).\n\n\n\n\n# Step 1: Insert MVSQLite data directly into the MVSQLite database.\nfunc insert_data_to_database():\n    var mvsqlite_data = get_mvsqlite_data()\n    var db = MVSQLite.new()\n    db.open(\"user://your_database_name.db\")\n    for data in mvsqlite_data:\n        db.execute(\"INSERT INTO your_table_name (column1, column2) VALUES (?, ?)\", [data.column1, data.column2])\n    db.close()\n\n# Step 2: Schedule externally consistent syncing of MVSQLite with the SQLite database (1 frame).\nfunc _process(delta):\n    if should_sync():\n        insert_data_to_database()\n\n# Step 3: Schedule periodic syncing of MVSQLite to a backup (e.g., every 30 minutes).\nvar backup_timer = Timer.new()\nfunc _ready():\n    backup_timer.set_wait_time(1800) # 30 minutes in seconds\n    backup_timer.connect(\"timeout\", self, \"_on_backup_timer_timeout\")\n    add_child(backup_timer)\n    backup_timer.start()\n\nfunc _on_backup_timer_timeout():\n    insert_data_to_database()\n\n# Helper functions\nfunc get_mvsqlite_data():\n    # Placeholder for obtaining MVSQLite data from the project\n    pass\n\nfunc should_sync():\n    # Placeholder for determining when to sync MVSQLite data with the SQLite database\n    pass\n\n\n\n\nImproved data management and performance.\nEnhanced security through server validation and sanitization.\nReduced load on the client-side.\n\n\n\n\n\nIncreased complexity in the system architecture.\nPotential challenges in implementing the new architecture.\n\n\n\n\n\nClient-side caching: Storing data on the client-side to reduce server load. However, this approach can lead to security vulnerabilities and inconsistent data across clients.\nStatic file export: Exporting data as static files instead of using MVSQLite. This option was rejected due to limited flexibility and scalability.\n\nThese options were considered but ultimately rejected in favor of the proposed solution, which aims to balance performance, security, and maintainability.\n\n\n\nThe proposed enhancement is designed to address core limitations in V-Sekai’s architecture and cannot be easily worked around with a few lines of script.\n\n\n\nImplementing this solution at the core level ensures that all users benefit from improved data management, performance, and security. Additionally, addressing these limitations at the core level allows for better integration with other components of the system.\n\n\n\n\nV-Sekai"
   },
   {
-    "objectID": "decisions/20220131-run-own-infrastructure.html#negative-consequences",
-    "href": "decisions/20220131-run-own-infrastructure.html#negative-consequences",
-    "title": "Rejected: To allow independent deployment run our own infrastructure",
+    "objectID": "decisions/20230527-server-sidecar.html#metadata",
+    "href": "decisions/20230527-server-sidecar.html#metadata",
+    "title": "Proposed: Efficiently managing and synchronizing game data with a server sidecar",
     "section": "",
-    "text": "Supporting more configurations will take more time from us.\n\n[this section can be repeated for each option if more than one option is open for consideration]"
+    "text": "Status: proposed\nDeciders: V-Sekai, Bioblaze Payne, fire\nTags: V-Sekai, GPT-4"
   },
   {
-    "objectID": "decisions/20220131-run-own-infrastructure.html#option-graveyard",
-    "href": "decisions/20220131-run-own-infrastructure.html#option-graveyard",
-    "title": "Rejected: To allow independent deployment run our own infrastructure",
+    "objectID": "decisions/20230527-server-sidecar.html#context-and-problem-statement",
+    "href": "decisions/20230527-server-sidecar.html#context-and-problem-statement",
+    "title": "Proposed: Efficiently managing and synchronizing game data with a server sidecar",
     "section": "",
-    "text": "Option: Support only bare metal infrastructure\nRejection Reason: This is not ideal unless you are at scale, because bare metal can die and cannot scale."
+    "text": "V-Sekai is facing a problem with efficiently managing and synchronizing data across multiple devices and platforms.\nThe goal is to find a more reliable and efficient solution for data synchronization that can handle large amounts of data, minimize latency, and ensure data consistency across all devices and platforms."
   },
   {
-    "objectID": "decisions/20220131-run-own-infrastructure.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20220131-run-own-infrastructure.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Rejected: To allow independent deployment run our own infrastructure",
+    "objectID": "decisions/20230527-server-sidecar.html#proposed-solution",
+    "href": "decisions/20230527-server-sidecar.html#proposed-solution",
+    "title": "Proposed: Efficiently managing and synchronizing game data with a server sidecar",
     "section": "",
-    "text": "This project is to document what the script will be"
+    "text": "We propose a new approach that involves directly inserting data into the MVSQLite cluster database and implementing a robust syncing mechanism to ensure data consistency across all devices and platforms.\n\nModify the editor export process to stream MVSQLite to the Godot Engine server.\nSchedule externally consistent syncing of MVSQLite with the Godot Engine server (1 frame).\nSchedule periodic syncing of MVSQLite to a backup (e.g., every 30 minutes)."
   },
   {
-    "objectID": "decisions/20220131-run-own-infrastructure.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20220131-run-own-infrastructure.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Rejected: To allow independent deployment run our own infrastructure",
+    "objectID": "decisions/20230527-server-sidecar.html#implementation",
+    "href": "decisions/20230527-server-sidecar.html#implementation",
+    "title": "Proposed: Efficiently managing and synchronizing game data with a server sidecar",
     "section": "",
-    "text": "Infra is part of our mission."
+    "text": "# Step 1: Insert MVSQLite data directly into the MVSQLite database.\nfunc insert_data_to_database():\n    var mvsqlite_data = get_mvsqlite_data()\n    var db = MVSQLite.new()\n    db.open(\"user://your_database_name.db\")\n    for data in mvsqlite_data:\n        db.execute(\"INSERT INTO your_table_name (column1, column2) VALUES (?, ?)\", [data.column1, data.column2])\n    db.close()\n\n# Step 2: Schedule externally consistent syncing of MVSQLite with the SQLite database (1 frame).\nfunc _process(delta):\n    if should_sync():\n        insert_data_to_database()\n\n# Step 3: Schedule periodic syncing of MVSQLite to a backup (e.g., every 30 minutes).\nvar backup_timer = Timer.new()\nfunc _ready():\n    backup_timer.set_wait_time(1800) # 30 minutes in seconds\n    backup_timer.connect(\"timeout\", self, \"_on_backup_timer_timeout\")\n    add_child(backup_timer)\n    backup_timer.start()\n\nfunc _on_backup_timer_timeout():\n    insert_data_to_database()\n\n# Helper functions\nfunc get_mvsqlite_data():\n    # Placeholder for obtaining MVSQLite data from the project\n    pass\n\nfunc should_sync():\n    # Placeholder for determining when to sync MVSQLite data with the SQLite database\n    pass"
   },
   {
-    "objectID": "decisions/20220131-run-own-infrastructure.html#references",
-    "href": "decisions/20220131-run-own-infrastructure.html#references",
-    "title": "Rejected: To allow independent deployment run our own infrastructure",
+    "objectID": "decisions/20230527-server-sidecar.html#positive-consequences",
+    "href": "decisions/20230527-server-sidecar.html#positive-consequences",
+    "title": "Proposed: Efficiently managing and synchronizing game data with a server sidecar",
     "section": "",
-    "text": "https://docs.digitalocean.com/products/volumes/how-to/move-between-droplets/"
+    "text": "Improved data management and performance.\nEnhanced security through server validation and sanitization.\nReduced load on the client-side."
   },
   {
-    "objectID": "decisions/20220131-run-own-infrastructure.html#derivative-license",
-    "href": "decisions/20220131-run-own-infrastructure.html#derivative-license",
-    "title": "Rejected: To allow independent deployment run our own infrastructure",
+    "objectID": "decisions/20230527-server-sidecar.html#negative-consequences",
+    "href": "decisions/20230527-server-sidecar.html#negative-consequences",
+    "title": "Proposed: Efficiently managing and synchronizing game data with a server sidecar",
     "section": "",
-    "text": "Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Increased complexity in the system architecture.\nPotential challenges in implementing the new architecture."
   },
   {
-    "objectID": "decisions/20231024-training-simulators.html",
-    "href": "decisions/20231024-training-simulators.html",
-    "title": "Proposed: Implementing Advanced Training Simulators in V-Sekai",
+    "objectID": "decisions/20230527-server-sidecar.html#option-graveyard",
+    "href": "decisions/20230527-server-sidecar.html#option-graveyard",
+    "title": "Proposed: Efficiently managing and synchronizing game data with a server sidecar",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, Game Development, Skill Simulation\n\n\n\n\nIn the world of V-Sekai, players can level up their skills and unlock advanced training simulators. These simulators provide access to comprehensive Standard Operating Procedures (SOPs) and allow players to practice actions in a safe environment.\n\n\n\nThe challenge lies in creating an immersive and realistic simulation experience that doesn’t harm the player’s character. For instance, if a player is an engineer, they should be able to practice replacing a plasma conduit, learn how to use the tools, and understand how to safely isolate sections for repairs.\n\n\n\nTo overcome this challenge, we propose developing a robust system that allows players to interact with the game environment in a meaningful way. This includes creating detailed SOPs, designing intuitive user interfaces for tool manipulation, and implementing safety measures within the game.\n\n\n\nBy providing a realistic and immersive simulation experience, we can enhance player engagement and satisfaction. Players will have the opportunity to learn and practice new skills, which can add depth to the gameplay.\n\n\n\nThe main downside is the complexity and resources required to implement such a system. It may also be challenging to balance realism with fun gameplay.\n\n\n\nAn alternative approach could be to simplify the skill system and focus more on traditional gameplay elements. However, this would not provide the same level of immersion and learning opportunities for the players.\n\n\n\nIn some cases, players may prefer a more straightforward gameplay experience and may not fully utilize the advanced training simulators.\n\n\n\nYes, this feature is core to the V-Sekai experience and will be developed by our team.\n\n\n\n\nV-Sekai\nAI assists this article."
+    "text": "Client-side caching: Storing data on the client-side to reduce server load. However, this approach can lead to security vulnerabilities and inconsistent data across clients.\nStatic file export: Exporting data as static files instead of using MVSQLite. This option was rejected due to limited flexibility and scalability.\n\nThese options were considered but ultimately rejected in favor of the proposed solution, which aims to balance performance, security, and maintainability."
   },
   {
-    "objectID": "decisions/20231024-training-simulators.html#metadata",
-    "href": "decisions/20231024-training-simulators.html#metadata",
-    "title": "Proposed: Implementing Advanced Training Simulators in V-Sekai",
+    "objectID": "decisions/20230527-server-sidecar.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230527-server-sidecar.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Efficiently managing and synchronizing game data with a server sidecar",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, Game Development, Skill Simulation"
+    "text": "The proposed enhancement is designed to address core limitations in V-Sekai’s architecture and cannot be easily worked around with a few lines of script."
   },
   {
-    "objectID": "decisions/20231024-training-simulators.html#the-backdrop",
-    "href": "decisions/20231024-training-simulators.html#the-backdrop",
-    "title": "Proposed: Implementing Advanced Training Simulators in V-Sekai",
+    "objectID": "decisions/20230527-server-sidecar.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230527-server-sidecar.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Efficiently managing and synchronizing game data with a server sidecar",
     "section": "",
-    "text": "In the world of V-Sekai, players can level up their skills and unlock advanced training simulators. These simulators provide access to comprehensive Standard Operating Procedures (SOPs) and allow players to practice actions in a safe environment."
+    "text": "Implementing this solution at the core level ensures that all users benefit from improved data management, performance, and security. Additionally, addressing these limitations at the core level allows for better integration with other components of the system."
   },
   {
-    "objectID": "decisions/20231024-training-simulators.html#the-challenge",
-    "href": "decisions/20231024-training-simulators.html#the-challenge",
-    "title": "Proposed: Implementing Advanced Training Simulators in V-Sekai",
+    "objectID": "decisions/20230527-server-sidecar.html#references",
+    "href": "decisions/20230527-server-sidecar.html#references",
+    "title": "Proposed: Efficiently managing and synchronizing game data with a server sidecar",
     "section": "",
-    "text": "The challenge lies in creating an immersive and realistic simulation experience that doesn’t harm the player’s character. For instance, if a player is an engineer, they should be able to practice replacing a plasma conduit, learn how to use the tools, and understand how to safely isolate sections for repairs."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20231024-training-simulators.html#the-strategy",
-    "href": "decisions/20231024-training-simulators.html#the-strategy",
-    "title": "Proposed: Implementing Advanced Training Simulators in V-Sekai",
+    "objectID": "decisions/20220217-omi-chan-oni-chan.html",
+    "href": "decisions/20220217-omi-chan-oni-chan.html",
+    "title": "Accepted: To create omi chan rig a #256FES",
     "section": "",
-    "text": "To overcome this challenge, we propose developing a robust system that allows players to interact with the game environment in a meaningful way. This includes creating detailed SOPs, designing intuitive user interfaces for tool manipulation, and implementing safety measures within the game."
+    "text": "Status: accepted \nDeciders: V-Sekai,jeana,fire,\nTags: V-Sekai,\n\n\n\nFormed an OMI Chan working group.\nTo create omi chan rig a #256FES.\n\n\n\nUse my know-how to rig a #256fes character.\n\n\n\n\n\n\n\nimage\n\n\n\nGiven mesh model that is unrigged and #256FES\n\n\n\nForearm is out of proportion\nHead is out of proportion\nNo base color\n\n\n\n\n\nhttps://github.com/saturday06/VRM_Addon_for_Blender/releases/tag/2_1_9\nCreate a vrm default armature template in Blender 3.0.1\nScale equally the entire mesh to be 1.7m (female Caucasian female on the tall statistical range)\nEnable equal scaling of bones button\nScale the arms and the neck/head\nUse autorig https://blendermarket.com/products/voxel-heat-diffuse-skinning\nUse xatlas to generate uv\nhttps://github.com/V-Sekai/V-Sekai-Blender-tools/tree/main/addons/blender_xatlas\nhttps://github.com/V-Sekai/V-Sekai-Blender-tools/tree/main/addons/Principled-Baker-master to bake uvs\nhttps://github.com/V-Sekai/V-Sekai-Blender-tools/tree/main/addons/corrective_smooth_baker\nExport to vrm\nAdd VRM mtoon material\nMake VRM mtoon material use black as shaded color.\nTest in 3tene and cluster.mu\nhttps://3d.kalidoface.com/ (first photo)\n\n\n\n\n\n\nWritten steps to vrm rigging #fes256\n\n\n\n\n\nMight be still too hard.\n\n\n\n\n\nOption: current situation.\nRejection Reason: No changes.\n\n\n\n\nThis uses several plugins of code.\n\n\n\nI know how to do it!\n\n\n\n\nReleased under the same license as Jeana’s work. CC-BY or CC0 if in doubt.\nSK_omi_chan_oni_chan.zip\n\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20231024-training-simulators.html#the-upside",
-    "href": "decisions/20231024-training-simulators.html#the-upside",
-    "title": "Proposed: Implementing Advanced Training Simulators in V-Sekai",
+    "objectID": "decisions/20220217-omi-chan-oni-chan.html#context-and-problem-statement",
+    "href": "decisions/20220217-omi-chan-oni-chan.html#context-and-problem-statement",
+    "title": "Accepted: To create omi chan rig a #256FES",
     "section": "",
-    "text": "By providing a realistic and immersive simulation experience, we can enhance player engagement and satisfaction. Players will have the opportunity to learn and practice new skills, which can add depth to the gameplay."
+    "text": "Formed an OMI Chan working group.\nTo create omi chan rig a #256FES."
   },
   {
-    "objectID": "decisions/20231024-training-simulators.html#the-downside",
-    "href": "decisions/20231024-training-simulators.html#the-downside",
-    "title": "Proposed: Implementing Advanced Training Simulators in V-Sekai",
+    "objectID": "decisions/20220217-omi-chan-oni-chan.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20220217-omi-chan-oni-chan.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Accepted: To create omi chan rig a #256FES",
     "section": "",
-    "text": "The main downside is the complexity and resources required to implement such a system. It may also be challenging to balance realism with fun gameplay."
+    "text": "Use my know-how to rig a #256fes character."
   },
   {
-    "objectID": "decisions/20231024-training-simulators.html#the-road-not-taken",
-    "href": "decisions/20231024-training-simulators.html#the-road-not-taken",
-    "title": "Proposed: Implementing Advanced Training Simulators in V-Sekai",
+    "objectID": "decisions/20220217-omi-chan-oni-chan.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20220217-omi-chan-oni-chan.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Accepted: To create omi chan rig a #256FES",
     "section": "",
-    "text": "An alternative approach could be to simplify the skill system and focus more on traditional gameplay elements. However, this would not provide the same level of immersion and learning opportunities for the players."
+    "text": "image\n\n\n\nGiven mesh model that is unrigged and #256FES\n\n\n\nForearm is out of proportion\nHead is out of proportion\nNo base color\n\n\n\n\n\nhttps://github.com/saturday06/VRM_Addon_for_Blender/releases/tag/2_1_9\nCreate a vrm default armature template in Blender 3.0.1\nScale equally the entire mesh to be 1.7m (female Caucasian female on the tall statistical range)\nEnable equal scaling of bones button\nScale the arms and the neck/head\nUse autorig https://blendermarket.com/products/voxel-heat-diffuse-skinning\nUse xatlas to generate uv\nhttps://github.com/V-Sekai/V-Sekai-Blender-tools/tree/main/addons/blender_xatlas\nhttps://github.com/V-Sekai/V-Sekai-Blender-tools/tree/main/addons/Principled-Baker-master to bake uvs\nhttps://github.com/V-Sekai/V-Sekai-Blender-tools/tree/main/addons/corrective_smooth_baker\nExport to vrm\nAdd VRM mtoon material\nMake VRM mtoon material use black as shaded color.\nTest in 3tene and cluster.mu\nhttps://3d.kalidoface.com/ (first photo)"
   },
   {
-    "objectID": "decisions/20231024-training-simulators.html#the-infrequent-use-case",
-    "href": "decisions/20231024-training-simulators.html#the-infrequent-use-case",
-    "title": "Proposed: Implementing Advanced Training Simulators in V-Sekai",
+    "objectID": "decisions/20220217-omi-chan-oni-chan.html#positive-consequences",
+    "href": "decisions/20220217-omi-chan-oni-chan.html#positive-consequences",
+    "title": "Accepted: To create omi chan rig a #256FES",
     "section": "",
-    "text": "In some cases, players may prefer a more straightforward gameplay experience and may not fully utilize the advanced training simulators."
+    "text": "Written steps to vrm rigging #fes256"
   },
   {
-    "objectID": "decisions/20231024-training-simulators.html#in-core-and-done-by-us",
-    "href": "decisions/20231024-training-simulators.html#in-core-and-done-by-us",
-    "title": "Proposed: Implementing Advanced Training Simulators in V-Sekai",
+    "objectID": "decisions/20220217-omi-chan-oni-chan.html#negative-consequences",
+    "href": "decisions/20220217-omi-chan-oni-chan.html#negative-consequences",
+    "title": "Accepted: To create omi chan rig a #256FES",
     "section": "",
-    "text": "Yes, this feature is core to the V-Sekai experience and will be developed by our team."
+    "text": "Might be still too hard."
   },
   {
-    "objectID": "decisions/20231024-training-simulators.html#further-reading",
-    "href": "decisions/20231024-training-simulators.html#further-reading",
-    "title": "Proposed: Implementing Advanced Training Simulators in V-Sekai",
+    "objectID": "decisions/20220217-omi-chan-oni-chan.html#option-graveyard",
+    "href": "decisions/20220217-omi-chan-oni-chan.html#option-graveyard",
+    "title": "Accepted: To create omi chan rig a #256FES",
     "section": "",
-    "text": "V-Sekai\nAI assists this article."
+    "text": "Option: current situation.\nRejection Reason: No changes."
   },
   {
-    "objectID": "decisions/20230107-elixir-uro-dev-sqlite.html",
-    "href": "decisions/20230107-elixir-uro-dev-sqlite.html",
-    "title": "Accepted: How to start a EXPERIMENTAL environment for sqlite and elixir?",
+    "objectID": "decisions/20220217-omi-chan-oni-chan.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20220217-omi-chan-oni-chan.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Accepted: To create omi chan rig a #256FES",
     "section": "",
-    "text": "Accepted: How to start a EXPERIMENTAL environment for sqlite and elixir?\n\nDescribe the status of the issue.\n\nproposed\ndraft\nrejected\naccepted\ndeprecated\nsuperseded by\n\n\n\nList the deciders of the issue.\nV-Sekai,lyuma,fire,\n\n\nDescribe the tags of the issue.\nV-Sekai,\n\n\nContext and Problem Statement\nHow do we start our uro backend?\nUSE 20220531-elixir-uro-dev.md for the production URO\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nWrite documentation how to update elixir.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nCompile uro. You will need Elixir installed.\nI recommend getting the latest, but for these steps, I am using Elixir v1.14.4.\nDownload Uro from https://github.com/V-Sekai/uro\nWe are using the dev environment. It is the default, but you can also set MIX_ENV=dev.\nTo compile HTML/CSS webpack:\ncd assets\nnpm install\nnpm run deploy\ncd ..\nIf the compile gives issues, you can run it multiple times. To compile dependencies:\nmix do compile, phx.digest\nIf one of them gives an error due to nmake or not having a compiler, you can fix it by opening a x64 Native Tools command prompt from visual studio and run mix deps.compile bcrypt_elixir\nFinally, create and migrate the database and start the development server:\nmix ecto.create\nmix ecto.migrate\niex.bat --werl -S mix phx.server\nThis will start uro at http://localhost:4000/\nCreate a user in the website register user page.\nGo to the console and set the user to be admin.\niex.bat --werl -S mix phx.server\n# TODO\n# Call Uro.Accounts.update_user_as_admin\nGitHub - V-Sekai/uro: Server backend for V-Sekai written in Elixir …\nThe docker image docker-uro is compiled using GoCD, so after pushing, check that the pipeline ran.\nThen, go to DockerHub at https://hub.docker.com/r/groupsinfra/uro/tags and check the most recently pushed tag (it will not be the latest one, but instead a specific version).\nNow, edit the flux config at https://github.com/V-Sekai/flux-config/blob/flux2/workloads/uro-deployment.yaml and replace the uro image version with the tag from above.\nCheck that uro-deployment was updated.\n\n\nPositive Consequences\nWe’re able to update uro!\n\n\nNegative Consequences\nNo response\n\n\nOption graveyard\nNo response\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nIt’s arguably a few lines of script, but it’s our script!\n\n\nIs there a reason why this should be core and done by us?\nWe maintain the website.\n\n\nReferences\n\nV-Sekai\nUro\nhttps://github.com/V-Sekai/uro/issues/52\n\n\n\nLicense of the contribution\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "This uses several plugins of code."
   },
   {
-    "objectID": "decisions/20240330-hyperv-harvester-test.html",
-    "href": "decisions/20240330-hyperv-harvester-test.html",
-    "title": "Proposed: Hyperv windows Harvester Test",
+    "objectID": "decisions/20220217-omi-chan-oni-chan.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20220217-omi-chan-oni-chan.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Accepted: To create omi chan rig a #256FES",
     "section": "",
-    "text": "Currently, we are operating a Kubernetes cluster in a Linux environment. However, the need to test our applications in a Windows environment has been identified. This is where Hyper-V Windows Harvester becomes relevant.\n\n\n\nOur existing testing environment does not cater to Windows-based applications. We require a solution that enables us to test these applications in a Windows environment without the necessity of setting up an entirely new cluster.\n\n\n\nWe can utilize Hyper-V to establish a Harvester HCI virtual machine (VM) on our current Windows desktop. Here’s a basic outline of the steps involved:\n\nInstall Hyper-V on the Windows desktop.\nCreate a new VM using Hyper-V.\nInstall Harvester HCI on the new VM.\nConfigure the Harvester HCI VM for our testing needs.\nRun tests on the Harvester HCI VM.\n\n\n\n\n\nEnables us to test Windows-based applications without the need for a separate Windows server.\nConserves resources by leveraging our existing infrastructure.\nEnhances our testing coverage and improves the quality of our software.\n\n\n\n\n\nRequires additional configuration and maintenance.\nPotential performance issues due to running a VM on top of the Windows desktop.\n\n\n\n\nWe could have opted to set up a separate Windows server for testing. However, this would necessitate significant resources and may not be cost-effective.\n\n\n\nThis setup might not be ideal if we need to run high-performance applications that demand all the resources of a dedicated server.\n\n\n\nThe implementation of this proposal will be carried out by our internal development team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
+    "text": "I know how to do it!"
   },
   {
-    "objectID": "decisions/20240330-hyperv-harvester-test.html#the-context",
-    "href": "decisions/20240330-hyperv-harvester-test.html#the-context",
-    "title": "Proposed: Hyperv windows Harvester Test",
+    "objectID": "decisions/20220217-omi-chan-oni-chan.html#references",
+    "href": "decisions/20220217-omi-chan-oni-chan.html#references",
+    "title": "Accepted: To create omi chan rig a #256FES",
     "section": "",
-    "text": "Currently, we are operating a Kubernetes cluster in a Linux environment. However, the need to test our applications in a Windows environment has been identified. This is where Hyper-V Windows Harvester becomes relevant."
+    "text": "Released under the same license as Jeana’s work. CC-BY or CC0 if in doubt.\nSK_omi_chan_oni_chan.zip"
   },
   {
-    "objectID": "decisions/20240330-hyperv-harvester-test.html#the-problem-statement",
-    "href": "decisions/20240330-hyperv-harvester-test.html#the-problem-statement",
-    "title": "Proposed: Hyperv windows Harvester Test",
+    "objectID": "decisions/20220217-omi-chan-oni-chan.html#derivative-license",
+    "href": "decisions/20220217-omi-chan-oni-chan.html#derivative-license",
+    "title": "Accepted: To create omi chan rig a #256FES",
     "section": "",
-    "text": "Our existing testing environment does not cater to Windows-based applications. We require a solution that enables us to test these applications in a Windows environment without the necessity of setting up an entirely new cluster."
+    "text": "Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240330-hyperv-harvester-test.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240330-hyperv-harvester-test.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Hyperv windows Harvester Test",
+    "objectID": "decisions/20210212-add-build-notifications.html",
+    "href": "decisions/20210212-add-build-notifications.html",
+    "title": "Proposed: Add build notifications",
     "section": "",
-    "text": "We can utilize Hyper-V to establish a Harvester HCI virtual machine (VM) on our current Windows desktop. Here’s a basic outline of the steps involved:\n\nInstall Hyper-V on the Windows desktop.\nCreate a new VM using Hyper-V.\nInstall Harvester HCI on the new VM.\nConfigure the Harvester HCI VM for our testing needs.\nRun tests on the Harvester HCI VM."
+    "text": "Add build notifications because we do not know when a build completed in the CI system to test it.\n\n\n\n\nChannels people use\n\n\n\n\n\nEmail notifications\nDiscord webhook notifications\n\n\n\n\nChosen option: Discord webhooks\n\n\n\nKnow when to test\nSystem stability\n\n\n\n\n\nEngineering effort\n\n\n\n\n\n\n\nUse the existing gocd email notifier.\n\nGood, because email is common\nBad, not everyone wants to use email\n\n\n\n\nMake a gocd Discord notifier\n\nGood, because everyone is on discord\nBad, because engineering needs to be done.\n\n\n\n\n\n\nhttps://docs.gocd.org/current/configuration/dev_notifications.html\nhttps://github.com/gocd-contrib/notification-skeleton-plugin\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240330-hyperv-harvester-test.html#the-benefits",
-    "href": "decisions/20240330-hyperv-harvester-test.html#the-benefits",
-    "title": "Proposed: Hyperv windows Harvester Test",
+    "objectID": "decisions/20210212-add-build-notifications.html#context-and-problem-statement",
+    "href": "decisions/20210212-add-build-notifications.html#context-and-problem-statement",
+    "title": "Proposed: Add build notifications",
     "section": "",
-    "text": "Enables us to test Windows-based applications without the need for a separate Windows server.\nConserves resources by leveraging our existing infrastructure.\nEnhances our testing coverage and improves the quality of our software."
+    "text": "Add build notifications because we do not know when a build completed in the CI system to test it."
   },
   {
-    "objectID": "decisions/20240330-hyperv-harvester-test.html#the-downsides",
-    "href": "decisions/20240330-hyperv-harvester-test.html#the-downsides",
-    "title": "Proposed: Hyperv windows Harvester Test",
+    "objectID": "decisions/20210212-add-build-notifications.html#decision-drivers",
+    "href": "decisions/20210212-add-build-notifications.html#decision-drivers",
+    "title": "Proposed: Add build notifications",
     "section": "",
-    "text": "Requires additional configuration and maintenance.\nPotential performance issues due to running a VM on top of the Windows desktop."
+    "text": "Channels people use"
   },
   {
-    "objectID": "decisions/20240330-hyperv-harvester-test.html#the-road-not-taken",
-    "href": "decisions/20240330-hyperv-harvester-test.html#the-road-not-taken",
-    "title": "Proposed: Hyperv windows Harvester Test",
+    "objectID": "decisions/20210212-add-build-notifications.html#considered-options",
+    "href": "decisions/20210212-add-build-notifications.html#considered-options",
+    "title": "Proposed: Add build notifications",
     "section": "",
-    "text": "We could have opted to set up a separate Windows server for testing. However, this would necessitate significant resources and may not be cost-effective."
+    "text": "Email notifications\nDiscord webhook notifications"
   },
   {
-    "objectID": "decisions/20240330-hyperv-harvester-test.html#the-infrequent-use-case",
-    "href": "decisions/20240330-hyperv-harvester-test.html#the-infrequent-use-case",
-    "title": "Proposed: Hyperv windows Harvester Test",
+    "objectID": "decisions/20210212-add-build-notifications.html#decision-outcome",
+    "href": "decisions/20210212-add-build-notifications.html#decision-outcome",
+    "title": "Proposed: Add build notifications",
     "section": "",
-    "text": "This setup might not be ideal if we need to run high-performance applications that demand all the resources of a dedicated server."
+    "text": "Chosen option: Discord webhooks\n\n\n\nKnow when to test\nSystem stability\n\n\n\n\n\nEngineering effort"
   },
   {
-    "objectID": "decisions/20240330-hyperv-harvester-test.html#in-core-and-done-by-us",
-    "href": "decisions/20240330-hyperv-harvester-test.html#in-core-and-done-by-us",
-    "title": "Proposed: Hyperv windows Harvester Test",
+    "objectID": "decisions/20210212-add-build-notifications.html#pros-and-cons-of-the-options",
+    "href": "decisions/20210212-add-build-notifications.html#pros-and-cons-of-the-options",
+    "title": "Proposed: Add build notifications",
     "section": "",
-    "text": "The implementation of this proposal will be carried out by our internal development team."
+    "text": "Use the existing gocd email notifier.\n\nGood, because email is common\nBad, not everyone wants to use email\n\n\n\n\nMake a gocd Discord notifier\n\nGood, because everyone is on discord\nBad, because engineering needs to be done."
   },
   {
-    "objectID": "decisions/20240330-hyperv-harvester-test.html#status",
-    "href": "decisions/20240330-hyperv-harvester-test.html#status",
-    "title": "Proposed: Hyperv windows Harvester Test",
+    "objectID": "decisions/20210212-add-build-notifications.html#references",
+    "href": "decisions/20210212-add-build-notifications.html#references",
+    "title": "Proposed: Add build notifications",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "https://docs.gocd.org/current/configuration/dev_notifications.html\nhttps://github.com/gocd-contrib/notification-skeleton-plugin"
   },
   {
-    "objectID": "decisions/20240330-hyperv-harvester-test.html#decision-makers",
-    "href": "decisions/20240330-hyperv-harvester-test.html#decision-makers",
-    "title": "Proposed: Hyperv windows Harvester Test",
+    "objectID": "decisions/20210212-add-build-notifications.html#derivative-license",
+    "href": "decisions/20210212-add-build-notifications.html#derivative-license",
+    "title": "Proposed: Add build notifications",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240330-hyperv-harvester-test.html#tags",
-    "href": "decisions/20240330-hyperv-harvester-test.html#tags",
-    "title": "Proposed: Hyperv windows Harvester Test",
+    "objectID": "decisions/20230806-v-sekai-ipad-projection-compatibility.html",
+    "href": "decisions/20230806-v-sekai-ipad-projection-compatibility.html",
+    "title": "Proposed: V-Sekai Navigation Compatibility with VR",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, iPad, Presentation Screen, Compatibility\n\n\n\n\nWe are developing a VR game that MUST be compatible with a wide range of devices. Our goal is to make our VR game accessible and enjoyable for this vast majority of users.\n\n\n\nThe challenge is to ensure the game’s user interface and controls work seamlessly across these different display sizes and touch interfaces.\n\n\n\nWe considered two options: Virtual joystick for touchscreen devices and Navmesh and 3D navigation points. We chose the “Virtual joystick for touchscreen devices” because it addresses the core issue of ensuring compatibility with iPads and large projector screens, and it is more cost-effective.\n\n\n\n\nImproved user experience across different devices and screen sizes.\nIncreased versatility of the game, making it suitable for various applications.\nEnhanced navigation in 3D spaces.\nMore cost-effective solution.\n\n\n\n\n\nPotential increase in development time and costs.\nAdditional resources for testing on different devices and screens.\n\n\n\n\nNavmeshes and 3D Navigation Points are tools used to define traversable spaces in a 3D environment. However, they might not be suitable when the spaces aren’t already defined, such as grids. Waypoints have similar limitations.\nIn Godot, any modification triggers a rebuild of the entire navigation map. If the map is large and complex, this rebuilding process can take a significant amount of time and lead to performance issues.\n\n\n\nWhile Navmesh and 3D Navigation Points provide an intuitive user interface for navigating 3D spaces, they might not translate well to continuous interaction on touchscreens, which is often expected by users on such devices.\n\n\n\nYes, the decision to implement a virtual joystick for touchscreen devices was made by us, V-Sekai. This decision is at the core of our strategy to ensure compatibility with iPads and large projector screens while also being cost-effective.\n\n\n\n\nV-Sekai\nThis article is assisted by AI."
   },
   {
-    "objectID": "decisions/20240330-hyperv-harvester-test.html#further-reading",
-    "href": "decisions/20240330-hyperv-harvester-test.html#further-reading",
-    "title": "Proposed: Hyperv windows Harvester Test",
+    "objectID": "decisions/20230806-v-sekai-ipad-projection-compatibility.html#metadata",
+    "href": "decisions/20230806-v-sekai-ipad-projection-compatibility.html#metadata",
+    "title": "Proposed: V-Sekai Navigation Compatibility with VR",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, iPad, Presentation Screen, Compatibility"
   },
   {
-    "objectID": "decisions/20240522-webrtc-relay-test.html",
-    "href": "decisions/20240522-webrtc-relay-test.html",
-    "title": "Proposed: Draft WebRTC Relay Test",
+    "objectID": "decisions/20230806-v-sekai-ipad-projection-compatibility.html#the-backdrop",
+    "href": "decisions/20230806-v-sekai-ipad-projection-compatibility.html#the-backdrop",
+    "title": "Proposed: V-Sekai Navigation Compatibility with VR",
     "section": "",
-    "text": "Status: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "We are developing a VR game that MUST be compatible with a wide range of devices. Our goal is to make our VR game accessible and enjoyable for this vast majority of users."
   },
   {
-    "objectID": "decisions/20240522-webrtc-relay-test.html#status",
-    "href": "decisions/20240522-webrtc-relay-test.html#status",
-    "title": "Proposed: Draft WebRTC Relay Test",
+    "objectID": "decisions/20230806-v-sekai-ipad-projection-compatibility.html#the-challenge",
+    "href": "decisions/20230806-v-sekai-ipad-projection-compatibility.html#the-challenge",
+    "title": "Proposed: V-Sekai Navigation Compatibility with VR",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "The challenge is to ensure the game’s user interface and controls work seamlessly across these different display sizes and touch interfaces."
   },
   {
-    "objectID": "decisions/20240522-webrtc-relay-test.html#decision-makers",
-    "href": "decisions/20240522-webrtc-relay-test.html#decision-makers",
-    "title": "Proposed: Draft WebRTC Relay Test",
+    "objectID": "decisions/20230806-v-sekai-ipad-projection-compatibility.html#the-strategy",
+    "href": "decisions/20230806-v-sekai-ipad-projection-compatibility.html#the-strategy",
+    "title": "Proposed: V-Sekai Navigation Compatibility with VR",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "We considered two options: Virtual joystick for touchscreen devices and Navmesh and 3D navigation points. We chose the “Virtual joystick for touchscreen devices” because it addresses the core issue of ensuring compatibility with iPads and large projector screens, and it is more cost-effective."
   },
   {
-    "objectID": "decisions/20240522-webrtc-relay-test.html#tags",
-    "href": "decisions/20240522-webrtc-relay-test.html#tags",
-    "title": "Proposed: Draft WebRTC Relay Test",
+    "objectID": "decisions/20230806-v-sekai-ipad-projection-compatibility.html#the-upside",
+    "href": "decisions/20230806-v-sekai-ipad-projection-compatibility.html#the-upside",
+    "title": "Proposed: V-Sekai Navigation Compatibility with VR",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Improved user experience across different devices and screen sizes.\nIncreased versatility of the game, making it suitable for various applications.\nEnhanced navigation in 3D spaces.\nMore cost-effective solution."
   },
   {
-    "objectID": "decisions/20240522-webrtc-relay-test.html#further-reading",
-    "href": "decisions/20240522-webrtc-relay-test.html#further-reading",
-    "title": "Proposed: Draft WebRTC Relay Test",
+    "objectID": "decisions/20230806-v-sekai-ipad-projection-compatibility.html#the-downside",
+    "href": "decisions/20230806-v-sekai-ipad-projection-compatibility.html#the-downside",
+    "title": "Proposed: V-Sekai Navigation Compatibility with VR",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "Potential increase in development time and costs.\nAdditional resources for testing on different devices and screens."
   },
   {
-    "objectID": "decisions/20220601-lightweight-quality-avatars.html",
-    "href": "decisions/20220601-lightweight-quality-avatars.html",
-    "title": "Proposed: Lightweight quality avatars",
+    "objectID": "decisions/20230806-v-sekai-ipad-projection-compatibility.html#the-road-not-taken",
+    "href": "decisions/20230806-v-sekai-ipad-projection-compatibility.html#the-road-not-taken",
+    "title": "Proposed: V-Sekai Navigation Compatibility with VR",
     "section": "",
-    "text": "Proposed: Lightweight quality avatars\n\nDescribe the status of the issue.\n\nproposed\ndraft\nrejected\naccepted\ndeprecated\nsuperseded by\n\n\n\nList the deciders of the issue.\nV-Sekai,fire,Yin Chien YEAP,\n\n\nDescribe the tags of the issue.\nV-Sekai,avatars,\n\n\nContext and Problem Statement\nYin works a lot in webxr, and noticed in the avatar ecosystem (VRchat, secondlife, etc.) most of these avatars are too high quality.\nWhat tools have we come across that have enabled lightweight avatars?\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nTo try to make things work for webxr, yin is interested in lightweight avatars in as many ways as possible. exploring avatars that are as parametric as possible.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nFind ways to define volumes as parametric, and textures based on vectors instead of bitmaps.\nFrame time: Using a mobile chip gives less headroom re: polys that can be dropped. Download sizes. How long does loading take.\nYin doesn’t love blender, more focused on web based tools fit for mobile processors and reasonable download speeds.\nYin has been looking into procedural materials as a lightweight mechanism.\nThere are two systems, skeleton system and blendshapes. Conversion of blend shapes to skeletons is possible.\nCan also describe a quad subdivision workflow.\n\nquad based subdivision of detail https://github.com/godotengine/godot-proposals/issues/784\nprocedural materials\nbake blendshapes to skeletons\nFire is researching CSG based extraction combined with sliders. https://kacperkan.github.io/ucsgnet/ https://github.com/eliemichel/DagAmendment\n\n\n\nPositive Consequences\nWorks on the most widely accessible HMDs.\n\n\nNegative Consequences\nNo response\n\n\nOption graveyard\nNo response\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nHeavyweight avatars is a systematic problem.\n\n\nIs there a reason why this should be core and done by us?\nAvatars is our special area.\n\n\nReferences\n\nV-Sekai\n\n\n\nLicense of the contribution\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Navmeshes and 3D Navigation Points are tools used to define traversable spaces in a 3D environment. However, they might not be suitable when the spaces aren’t already defined, such as grids. Waypoints have similar limitations.\nIn Godot, any modification triggers a rebuild of the entire navigation map. If the map is large and complex, this rebuilding process can take a significant amount of time and lead to performance issues."
   },
   {
-    "objectID": "decisions/ai-assisted-proposal-style-guide.html",
-    "href": "decisions/ai-assisted-proposal-style-guide.html",
-    "title": "Accepted: AI Assisted Style Guide",
+    "objectID": "decisions/20230806-v-sekai-ipad-projection-compatibility.html#the-infrequent-use-case",
+    "href": "decisions/20230806-v-sekai-ipad-projection-compatibility.html#the-infrequent-use-case",
+    "title": "Proposed: V-Sekai Navigation Compatibility with VR",
     "section": "",
-    "text": "In the realm of proposal writing, maintaining a consistent and professional style is crucial. However, when utilizing AI to assist in this process, the output often lacks the desired stylistic quality.\n\n\n\nWhen we instruct AI to help complete our proposals, we often encounter issues with poor style and inconsistent formatting.\n\n\n\n\nAvoid Purple Speech: Ensure that the language used is clear and concise, avoiding overly elaborate or flowery expressions.\nBe Snappy: Keep sentences short and to the point to maintain reader engagement.\nAvoid Redundant Phrases: Refrain from using redundant phrases like “effective altruism” since true altruism inherently implies effectiveness.\nMaintain Consistent Headers: Adhere to the header structure provided in the template to ensure uniformity across documents.\n\n\n\n\n\nImproved Readability: Clear and concise language enhances the readability of proposals.\nConsistency: Maintaining a consistent style ensures that all documents have a professional appearance.\nEfficiency: Streamlined guidelines make it easier for AI to generate high-quality content quickly.\n\n\n\n\n\nLimited Creativity: Strict adherence to style guidelines may limit creative expression.\nInitial Setup Time: Establishing and fine-tuning the style guide may require an initial investment of time and resources.\n\n\n\n\nAlternative approaches such as manual editing or using different AI models were considered but ultimately deemed less efficient or effective.\n\n\n\nIn scenarios where highly specialized or technical language is required, additional human oversight may be necessary to ensure accuracy and appropriateness.\n\n\n\nThis proposal aligns with our core values of efficiency and professionalism and will be implemented by our team.\n\n\n\nStatus: Accepted \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "While Navmesh and 3D Navigation Points provide an intuitive user interface for navigating 3D spaces, they might not translate well to continuous interaction on touchscreens, which is often expected by users on such devices."
   },
   {
-    "objectID": "decisions/ai-assisted-proposal-style-guide.html#the-context",
-    "href": "decisions/ai-assisted-proposal-style-guide.html#the-context",
-    "title": "Accepted: AI Assisted Style Guide",
+    "objectID": "decisions/20230806-v-sekai-ipad-projection-compatibility.html#in-core-and-done-by-us",
+    "href": "decisions/20230806-v-sekai-ipad-projection-compatibility.html#in-core-and-done-by-us",
+    "title": "Proposed: V-Sekai Navigation Compatibility with VR",
     "section": "",
-    "text": "In the realm of proposal writing, maintaining a consistent and professional style is crucial. However, when utilizing AI to assist in this process, the output often lacks the desired stylistic quality."
+    "text": "Yes, the decision to implement a virtual joystick for touchscreen devices was made by us, V-Sekai. This decision is at the core of our strategy to ensure compatibility with iPads and large projector screens while also being cost-effective."
   },
   {
-    "objectID": "decisions/ai-assisted-proposal-style-guide.html#the-problem-statement",
-    "href": "decisions/ai-assisted-proposal-style-guide.html#the-problem-statement",
-    "title": "Accepted: AI Assisted Style Guide",
+    "objectID": "decisions/20230806-v-sekai-ipad-projection-compatibility.html#further-reading",
+    "href": "decisions/20230806-v-sekai-ipad-projection-compatibility.html#further-reading",
+    "title": "Proposed: V-Sekai Navigation Compatibility with VR",
     "section": "",
-    "text": "When we instruct AI to help complete our proposals, we often encounter issues with poor style and inconsistent formatting."
+    "text": "V-Sekai\nThis article is assisted by AI."
   },
   {
-    "objectID": "decisions/ai-assisted-proposal-style-guide.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/ai-assisted-proposal-style-guide.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Accepted: AI Assisted Style Guide",
+    "objectID": "decisions/20230911-xr-grid-with-drawing.html",
+    "href": "decisions/20230911-xr-grid-with-drawing.html",
+    "title": "Proposed: Improving xr grid with new enhancements",
     "section": "",
-    "text": "Avoid Purple Speech: Ensure that the language used is clear and concise, avoiding overly elaborate or flowery expressions.\nBe Snappy: Keep sentences short and to the point to maintain reader engagement.\nAvoid Redundant Phrases: Refrain from using redundant phrases like “effective altruism” since true altruism inherently implies effectiveness.\nMaintain Consistent Headers: Adhere to the header structure provided in the template to ensure uniformity across documents."
+    "text": "Status: proposed\nDeciders: V-Sekai, fire, detox,\nTags: V-Sekai\n\n\n\n\nWe are developing an xr grid project, but it’s in a nice easy to understand state.\n\n\n\nDETOX suggested comparing different modes of navigation before making any changes. Fire shared that they have three modes in mind: blob pen, 2D beautifications for 3D, and patch mode. However, these are not functioning correctly yet due to complexity.\n\n\n\nFire will think up some UI for xr-grid, create a simple UI system based on GUI in VR, and add it to xr-grid. We also discuss the possibility of adding a glTF export menu and other features to the UI.\n\n\n\nThe team is considering various improvements such as fixing grid bugs, exporting loadable content in Blender, adding branding/instructions, and improving the UI.\n\n\n\nThe main challenge is to avoid bloating the main project with art tools. This might require branching or forking the project.\n\n\n\nDETOX suggested creating a branch for the new features, while Fire expressed a desire to work on networking. They also discussed the possibility of building a tool similar to Cassie on the branch.\n\n\n\n\nV-Sekai\nThis article is assisted by AI."
   },
   {
-    "objectID": "decisions/ai-assisted-proposal-style-guide.html#the-benefits",
-    "href": "decisions/ai-assisted-proposal-style-guide.html#the-benefits",
-    "title": "Accepted: AI Assisted Style Guide",
+    "objectID": "decisions/20230911-xr-grid-with-drawing.html#metadata",
+    "href": "decisions/20230911-xr-grid-with-drawing.html#metadata",
+    "title": "Proposed: Improving xr grid with new enhancements",
     "section": "",
-    "text": "Improved Readability: Clear and concise language enhances the readability of proposals.\nConsistency: Maintaining a consistent style ensures that all documents have a professional appearance.\nEfficiency: Streamlined guidelines make it easier for AI to generate high-quality content quickly."
+    "text": "Status: proposed\nDeciders: V-Sekai, fire, detox,\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/ai-assisted-proposal-style-guide.html#the-downsides",
-    "href": "decisions/ai-assisted-proposal-style-guide.html#the-downsides",
-    "title": "Accepted: AI Assisted Style Guide",
+    "objectID": "decisions/20230911-xr-grid-with-drawing.html#context-and-problem-statement",
+    "href": "decisions/20230911-xr-grid-with-drawing.html#context-and-problem-statement",
+    "title": "Proposed: Improving xr grid with new enhancements",
     "section": "",
-    "text": "Limited Creativity: Strict adherence to style guidelines may limit creative expression.\nInitial Setup Time: Establishing and fine-tuning the style guide may require an initial investment of time and resources."
+    "text": "We are developing an xr grid project, but it’s in a nice easy to understand state."
   },
   {
-    "objectID": "decisions/ai-assisted-proposal-style-guide.html#the-road-not-taken",
-    "href": "decisions/ai-assisted-proposal-style-guide.html#the-road-not-taken",
-    "title": "Accepted: AI Assisted Style Guide",
+    "objectID": "decisions/20230911-xr-grid-with-drawing.html#considered-options",
+    "href": "decisions/20230911-xr-grid-with-drawing.html#considered-options",
+    "title": "Proposed: Improving xr grid with new enhancements",
     "section": "",
-    "text": "Alternative approaches such as manual editing or using different AI models were considered but ultimately deemed less efficient or effective."
+    "text": "DETOX suggested comparing different modes of navigation before making any changes. Fire shared that they have three modes in mind: blob pen, 2D beautifications for 3D, and patch mode. However, these are not functioning correctly yet due to complexity."
   },
   {
-    "objectID": "decisions/ai-assisted-proposal-style-guide.html#the-infrequent-use-case",
-    "href": "decisions/ai-assisted-proposal-style-guide.html#the-infrequent-use-case",
-    "title": "Accepted: AI Assisted Style Guide",
+    "objectID": "decisions/20230911-xr-grid-with-drawing.html#decision-outcome",
+    "href": "decisions/20230911-xr-grid-with-drawing.html#decision-outcome",
+    "title": "Proposed: Improving xr grid with new enhancements",
     "section": "",
-    "text": "In scenarios where highly specialized or technical language is required, additional human oversight may be necessary to ensure accuracy and appropriateness."
+    "text": "Fire will think up some UI for xr-grid, create a simple UI system based on GUI in VR, and add it to xr-grid. We also discuss the possibility of adding a glTF export menu and other features to the UI."
   },
   {
-    "objectID": "decisions/ai-assisted-proposal-style-guide.html#in-core-and-done-by-us",
-    "href": "decisions/ai-assisted-proposal-style-guide.html#in-core-and-done-by-us",
-    "title": "Accepted: AI Assisted Style Guide",
+    "objectID": "decisions/20230911-xr-grid-with-drawing.html#positive-consequences",
+    "href": "decisions/20230911-xr-grid-with-drawing.html#positive-consequences",
+    "title": "Proposed: Improving xr grid with new enhancements",
     "section": "",
-    "text": "This proposal aligns with our core values of efficiency and professionalism and will be implemented by our team."
+    "text": "The team is considering various improvements such as fixing grid bugs, exporting loadable content in Blender, adding branding/instructions, and improving the UI."
   },
   {
-    "objectID": "decisions/ai-assisted-proposal-style-guide.html#status",
-    "href": "decisions/ai-assisted-proposal-style-guide.html#status",
-    "title": "Accepted: AI Assisted Style Guide",
+    "objectID": "decisions/20230911-xr-grid-with-drawing.html#negative-consequences",
+    "href": "decisions/20230911-xr-grid-with-drawing.html#negative-consequences",
+    "title": "Proposed: Improving xr grid with new enhancements",
     "section": "",
-    "text": "Status: Accepted"
+    "text": "The main challenge is to avoid bloating the main project with art tools. This might require branching or forking the project."
   },
   {
-    "objectID": "decisions/ai-assisted-proposal-style-guide.html#decision-makers",
-    "href": "decisions/ai-assisted-proposal-style-guide.html#decision-makers",
-    "title": "Accepted: AI Assisted Style Guide",
+    "objectID": "decisions/20230911-xr-grid-with-drawing.html#prospects-for-the-future",
+    "href": "decisions/20230911-xr-grid-with-drawing.html#prospects-for-the-future",
+    "title": "Proposed: Improving xr grid with new enhancements",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "DETOX suggested creating a branch for the new features, while Fire expressed a desire to work on networking. They also discussed the possibility of building a tool similar to Cassie on the branch."
   },
   {
-    "objectID": "decisions/ai-assisted-proposal-style-guide.html#tags",
-    "href": "decisions/ai-assisted-proposal-style-guide.html#tags",
-    "title": "Accepted: AI Assisted Style Guide",
+    "objectID": "decisions/20230911-xr-grid-with-drawing.html#links",
+    "href": "decisions/20230911-xr-grid-with-drawing.html#links",
+    "title": "Proposed: Improving xr grid with new enhancements",
     "section": "",
-    "text": "V-Sekai"
+    "text": "V-Sekai\nThis article is assisted by AI."
   },
   {
-    "objectID": "decisions/ai-assisted-proposal-style-guide.html#further-reading",
-    "href": "decisions/ai-assisted-proposal-style-guide.html#further-reading",
-    "title": "Accepted: AI Assisted Style Guide",
+    "objectID": "decisions/present-proposal-template.html",
+    "href": "decisions/present-proposal-template.html",
+    "title": "Proposed: Template",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "Status: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html",
-    "href": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html",
-    "title": "Proposed: Implementing a 3D Multiplayer Movement System with Parented Objects and Inventory Management",
+    "objectID": "decisions/present-proposal-template.html#status",
+    "href": "decisions/present-proposal-template.html#status",
+    "title": "Proposed: Template",
     "section": "",
-    "text": "The V-Sekai development team is working on enhancing the multiplayer experience in our VR game. We aim to create a more immersive and interactive environment for our players, akin to electrons circling in an atom or bustling activity on an MMOG street.\n\n\n\nOur VR game lacks a robust system for managing 3D multiplayer movement, parented objects, tracking validation, authentication, account metadata information, server boundaries, inventory management, and asset delivery. We also need to implement a mechanism for players to seamlessly leave and rejoin the game.\n\n\n\nOur proposed solution involves implementing a series of features:\n\n3D Multiplayer Movement: We will use the libgodot process to manage 3D multiplayer movements. This will allow players to interactively move around in the 3D space, similar to electrons circling in an atom.\nParented Objects: We will develop a system to handle parented objects, allowing for complex interactions between game entities.\nTracking Validation & Authentication: We will implement mechanisms to validate cross-communication and user inputs, along with an authentication system for account security.\nAccount Metadata Information: We will store and manage account metadata information to personalize the user experience.\nServer Boundaries: We will set limitations on the server, such as boundaries, to maintain game balance and performance.\nInventory Management: Players can spawn items from their inventory, create new items, and return them to the inventory.\nGame Rejoining: Players will have the ability to leave and rejoin the game without losing their progress.\nAsset Delivery and Upload: We will establish an efficient asset delivery and upload system.\nVoice Communication: We plan to add voice communication to enhance player interaction.\n\n\n\n\n\nEnhanced player interaction with 3D multiplayer movement and voice communication.\nImproved game balance and performance with server boundaries.\nBetter user experience with personalized account metadata information.\nSeamless gameplay with the ability to leave and rejoin the game.\n\n\n\n\n\nRequires significant development effort.\nPotential for increased system complexity.\n\n\n\n\nWe considered using existing game engines or libraries, but they did not meet our specific requirements for a highly interactive and immersive VR game.\n\n\n\nThis proposal may not be suitable for smaller projects that do not require complex 3D multiplayer interactions or inventory management.\n\n\n\nThe V-Sekai development team will implement this proposal.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team, “Bioblaze Payne”, “fire”\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAssisted by Aria."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#the-context",
-    "href": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#the-context",
-    "title": "Proposed: Implementing a 3D Multiplayer Movement System with Parented Objects and Inventory Management",
+    "objectID": "decisions/present-proposal-template.html#decision-makers",
+    "href": "decisions/present-proposal-template.html#decision-makers",
+    "title": "Proposed: Template",
     "section": "",
-    "text": "The V-Sekai development team is working on enhancing the multiplayer experience in our VR game. We aim to create a more immersive and interactive environment for our players, akin to electrons circling in an atom or bustling activity on an MMOG street."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#the-problem-statement",
-    "href": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#the-problem-statement",
-    "title": "Proposed: Implementing a 3D Multiplayer Movement System with Parented Objects and Inventory Management",
+    "objectID": "decisions/present-proposal-template.html#tags",
+    "href": "decisions/present-proposal-template.html#tags",
+    "title": "Proposed: Template",
     "section": "",
-    "text": "Our VR game lacks a robust system for managing 3D multiplayer movement, parented objects, tracking validation, authentication, account metadata information, server boundaries, inventory management, and asset delivery. We also need to implement a mechanism for players to seamlessly leave and rejoin the game."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Implementing a 3D Multiplayer Movement System with Parented Objects and Inventory Management",
+    "objectID": "decisions/present-proposal-template.html#further-reading",
+    "href": "decisions/present-proposal-template.html#further-reading",
+    "title": "Proposed: Template",
     "section": "",
-    "text": "Our proposed solution involves implementing a series of features:\n\n3D Multiplayer Movement: We will use the libgodot process to manage 3D multiplayer movements. This will allow players to interactively move around in the 3D space, similar to electrons circling in an atom.\nParented Objects: We will develop a system to handle parented objects, allowing for complex interactions between game entities.\nTracking Validation & Authentication: We will implement mechanisms to validate cross-communication and user inputs, along with an authentication system for account security.\nAccount Metadata Information: We will store and manage account metadata information to personalize the user experience.\nServer Boundaries: We will set limitations on the server, such as boundaries, to maintain game balance and performance.\nInventory Management: Players can spawn items from their inventory, create new items, and return them to the inventory.\nGame Rejoining: Players will have the ability to leave and rejoin the game without losing their progress.\nAsset Delivery and Upload: We will establish an efficient asset delivery and upload system.\nVoice Communication: We plan to add voice communication to enhance player interaction."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#the-benefits",
-    "href": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#the-benefits",
-    "title": "Proposed: Implementing a 3D Multiplayer Movement System with Parented Objects and Inventory Management",
+    "objectID": "decisions/20231126-v-sekai-report.html",
+    "href": "decisions/20231126-v-sekai-report.html",
+    "title": "Accepted: V-Sekai 2023-11-26 Report",
     "section": "",
-    "text": "Enhanced player interaction with 3D multiplayer movement and voice communication.\nImproved game balance and performance with server boundaries.\nBetter user experience with personalized account metadata information.\nSeamless gameplay with the ability to leave and rejoin the game."
+    "text": "Status: Accepted\nDeciders: V-Sekai, fire, PLYSHKA🐧, SaracenOne\nTags: V-Sekai, Linux, Bug Fix, Godot Engine, User Support\n\n\n\n\nV-Sekai, pronounced vee-say-kai, is a collective of developers passionate about creating open-source VR technology. We aim to contribute to social VR and provide alternatives to proprietary engines like Unity and Unreal.\nDespite challenges, we’ve grown into a global community committed to advancing open standards and open-source software for virtual worlds.\nOur strategy focuses on providing comprehensive documentation and support to help users understand the platform better. We’re also committed to investigating and resolving issues like the reported Linux build problem.\n\n\n\nOver the past month, our team has been deeply involved in the Godot Engine conference in Munich, Germany. Our primary responsibility during this period has been to prepare for the upcoming launch of Godot Engine 4.2, to which we are contributing as part of the animation and 3D pipeline teams.\n\n\n\nWhat state is V-Sekai in, and what can it do?\n\n\n\n\n\n\nMultiplayer Voice Chat: The multiplayer voice chat feature in V-Sekai is broken.\nMenu Editing: In V-Sekai, menus can’t be edited in VR. They can only be edited on the desktop before entering a game.\nDefault Avatar IK: V-Sekai’s default ik is currently twisted incorrectly.\n\n\n\n\n\nAvatar Uploading and Downloading: V-Sekai can upload from the editor and, download avatars, and load them into the game at runtime.\nWorld Uploading and Downloading: V-Sekai can upload from the editor and, download worlds, and load them into the game at runtime.\nVR Mode Loading: V-Sekai can successfully load in VR mode.\n\n\n\n\n\nContributions: V-Sekai is actively looking for more contributions.\n\n\n\n\n\nPros:\nAddressing these challenges can enhance the user experience, boost platform adoption, and collect crucial feedback for subsequent development.\nCons:\nThere may be underlying issues causing the Linux build problem that could take significant time and resources to resolve.\n\n\n\nAn alternative approach could have been to ignore the user’s query and continue with the current development roadmap. However, this would not foster a supportive community or encourage user engagement.\n\n\n\nWhile most users may not encounter the same issue as PLYSHKA🐧, addressing even infrequent use cases is essential to ensure a robust and user-friendly platform.\n\n\n\nAddressing this issue falls within our core responsibilities as the V-Sekai development team.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#the-downsides",
-    "href": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#the-downsides",
-    "title": "Proposed: Implementing a 3D Multiplayer Movement System with Parented Objects and Inventory Management",
+    "objectID": "decisions/20231126-v-sekai-report.html#metadata",
+    "href": "decisions/20231126-v-sekai-report.html#metadata",
+    "title": "Accepted: V-Sekai 2023-11-26 Report",
     "section": "",
-    "text": "Requires significant development effort.\nPotential for increased system complexity."
+    "text": "Status: Accepted\nDeciders: V-Sekai, fire, PLYSHKA🐧, SaracenOne\nTags: V-Sekai, Linux, Bug Fix, Godot Engine, User Support"
   },
   {
-    "objectID": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#the-road-not-taken",
-    "href": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#the-road-not-taken",
-    "title": "Proposed: Implementing a 3D Multiplayer Movement System with Parented Objects and Inventory Management",
+    "objectID": "decisions/20231126-v-sekai-report.html#what-is-v-sekai",
+    "href": "decisions/20231126-v-sekai-report.html#what-is-v-sekai",
+    "title": "Accepted: V-Sekai 2023-11-26 Report",
     "section": "",
-    "text": "We considered using existing game engines or libraries, but they did not meet our specific requirements for a highly interactive and immersive VR game."
+    "text": "V-Sekai, pronounced vee-say-kai, is a collective of developers passionate about creating open-source VR technology. We aim to contribute to social VR and provide alternatives to proprietary engines like Unity and Unreal.\nDespite challenges, we’ve grown into a global community committed to advancing open standards and open-source software for virtual worlds.\nOur strategy focuses on providing comprehensive documentation and support to help users understand the platform better. We’re also committed to investigating and resolving issues like the reported Linux build problem."
   },
   {
-    "objectID": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#the-infrequent-use-case",
-    "href": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#the-infrequent-use-case",
-    "title": "Proposed: Implementing a 3D Multiplayer Movement System with Parented Objects and Inventory Management",
+    "objectID": "decisions/20231126-v-sekai-report.html#background",
+    "href": "decisions/20231126-v-sekai-report.html#background",
+    "title": "Accepted: V-Sekai 2023-11-26 Report",
     "section": "",
-    "text": "This proposal may not be suitable for smaller projects that do not require complex 3D multiplayer interactions or inventory management."
+    "text": "Over the past month, our team has been deeply involved in the Godot Engine conference in Munich, Germany. Our primary responsibility during this period has been to prepare for the upcoming launch of Godot Engine 4.2, to which we are contributing as part of the animation and 3D pipeline teams."
   },
   {
-    "objectID": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#in-core-and-done-by-us",
-    "href": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#in-core-and-done-by-us",
-    "title": "Proposed: Implementing a 3D Multiplayer Movement System with Parented Objects and Inventory Management",
+    "objectID": "decisions/20231126-v-sekai-report.html#problem-statement",
+    "href": "decisions/20231126-v-sekai-report.html#problem-statement",
+    "title": "Accepted: V-Sekai 2023-11-26 Report",
     "section": "",
-    "text": "The V-Sekai development team will implement this proposal."
+    "text": "What state is V-Sekai in, and what can it do?"
   },
   {
-    "objectID": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#status",
-    "href": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#status",
-    "title": "Proposed: Implementing a 3D Multiplayer Movement System with Parented Objects and Inventory Management",
+    "objectID": "decisions/20231126-v-sekai-report.html#strategy",
+    "href": "decisions/20231126-v-sekai-report.html#strategy",
+    "title": "Accepted: V-Sekai 2023-11-26 Report",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "Multiplayer Voice Chat: The multiplayer voice chat feature in V-Sekai is broken.\nMenu Editing: In V-Sekai, menus can’t be edited in VR. They can only be edited on the desktop before entering a game.\nDefault Avatar IK: V-Sekai’s default ik is currently twisted incorrectly.\n\n\n\n\n\nAvatar Uploading and Downloading: V-Sekai can upload from the editor and, download avatars, and load them into the game at runtime.\nWorld Uploading and Downloading: V-Sekai can upload from the editor and, download worlds, and load them into the game at runtime.\nVR Mode Loading: V-Sekai can successfully load in VR mode.\n\n\n\n\n\nContributions: V-Sekai is actively looking for more contributions."
   },
   {
-    "objectID": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#decision-makers",
-    "href": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#decision-makers",
-    "title": "Proposed: Implementing a 3D Multiplayer Movement System with Parented Objects and Inventory Management",
+    "objectID": "decisions/20231126-v-sekai-report.html#pros-and-cons",
+    "href": "decisions/20231126-v-sekai-report.html#pros-and-cons",
+    "title": "Accepted: V-Sekai 2023-11-26 Report",
     "section": "",
-    "text": "V-Sekai development team, “Bioblaze Payne”, “fire”"
+    "text": "Pros:\nAddressing these challenges can enhance the user experience, boost platform adoption, and collect crucial feedback for subsequent development.\nCons:\nThere may be underlying issues causing the Linux build problem that could take significant time and resources to resolve."
   },
   {
-    "objectID": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#tags",
-    "href": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#tags",
-    "title": "Proposed: Implementing a 3D Multiplayer Movement System with Parented Objects and Inventory Management",
+    "objectID": "decisions/20231126-v-sekai-report.html#alternative-approach",
+    "href": "decisions/20231126-v-sekai-report.html#alternative-approach",
+    "title": "Accepted: V-Sekai 2023-11-26 Report",
     "section": "",
-    "text": "V-Sekai"
+    "text": "An alternative approach could have been to ignore the user’s query and continue with the current development roadmap. However, this would not foster a supportive community or encourage user engagement."
   },
   {
-    "objectID": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#further-reading",
-    "href": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#further-reading",
-    "title": "Proposed: Implementing a 3D Multiplayer Movement System with Parented Objects and Inventory Management",
+    "objectID": "decisions/20231126-v-sekai-report.html#infrequent-use-case",
+    "href": "decisions/20231126-v-sekai-report.html#infrequent-use-case",
+    "title": "Accepted: V-Sekai 2023-11-26 Report",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAssisted by Aria."
+    "text": "While most users may not encounter the same issue as PLYSHKA🐧, addressing even infrequent use cases is essential to ensure a robust and user-friendly platform."
   },
   {
-    "objectID": "decisions/20230419-limited-tracker-placement.html",
-    "href": "decisions/20230419-limited-tracker-placement.html",
-    "title": "Proposed: Capturing accurate body movements with limited tracker placement",
+    "objectID": "decisions/20231126-v-sekai-report.html#responsibility",
+    "href": "decisions/20231126-v-sekai-report.html#responsibility",
+    "title": "Accepted: V-Sekai 2023-11-26 Report",
     "section": "",
-    "text": "Proposed: Capturing accurate body movements with limited tracker placement\n\nMetadata\n\nStatus: superseded by 20230602-limited-tracker-placement.md \nDeciders: V-Sekai,fire,\nTags: V-Sekai,\n\n\n\nContext and Problem Statement\nIn our current VR project, we face the challenge of capturing accurate body movements for both soccer and dancing experiences with a limited budget. How can we prioritize the placement of a limited number of trackers to ensure a realistic and immersive experience for both activities?\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nThe proposed option involves prioritizing tracker placement for the head, hands, hips, and feet, as they are essential for both soccer and dancing experiences. This approach allows for an effective trade-off between tracking accuracy and budget constraints while ensuring a satisfactory level of immersion in both activities.\n\n\nDescribe how your proposal will work with code, pseudo-code, mock-ups, or diagrams\n\nHead: At the base of the neck to monitor head rotation and tilt.\nLeft Hand: On the left wrist to track the overall motion of the left hand.\nRight Hand: On the right wrist to track the overall motion of the right hand.\nHips: A tracker on the hips to monitor lower body movement.\nLeft Foot: A tracker on the left foot to capture left foot movement, essential for both soccer and dancing.\nRight Foot: A tracker on the right foot to capture right foot movement, also crucial for both activities.\n\nAs the budget permits, additional trackers can be incorporated into the setup to further enhance tracking accuracy, particularly for the upper body and leg movements. This expansion can be achieved by following the prioritized list of additional trackers below:\n\nChest: A tracker on the chest to monitor upper body rotation, providing more detailed information about the user’s torso movements.\nLeft Shoulder: A tracker on the left shoulder to track upper arm rotation, allowing for more precise tracking of arm movements during soccer and dancing.\nRight Shoulder: A tracker on the right shoulder to track upper arm rotation, complementing the left shoulder tracker for better arm movement tracking.\nLeft Knee: A tracker on the left knee to track left leg movement, enhancing the realism of leg movements and providing more accurate feedback for actions like kicking in soccer or complex footwork in dancing.\nRight Knee: A tracker on the right knee to track right leg movement, mirroring the benefits of the left knee tracker for a balanced leg movement representation.\n\nBy gradually adding these trackers to the initial setup, the overall tracking accuracy of the system will be improved. This will result in more natural and immersive interactions within the VR environment, leading to a more satisfying user experience for both soccer and dancing activities.\n\n\nPositive Consequences\n\nEffective use of a limited budget while maintaining immersive experiences.\nThe solution caters to both soccer and dancing activities in VR.\nFlexibility in adding more trackers as budget permits.\n\n\n\nNegative Consequences\n\nReduced tracking accuracy for upper body and leg movements compared to a setup with more trackers.\nPotential limitations in supporting advanced features or interactions in VR.\n\n\n\nOption graveyard\nCamera-based tracking: Utilizing external cameras to track body movements without the need for wearable trackers. While this approach can be cost-effective, it may not provide the same level of accuracy and precision as wearable trackers, particularly for fast and complex movements in soccer and dancing. Additionally, camera-based tracking can be sensitive to lighting conditions and may require a specific setup to function optimally.\nCamera-based tracking might be a viable solution if budget constraints are severe, but it is essential to consider the potential trade-offs in terms of tracking accuracy and reliability compared to wearable trackers.\n\n\nIf this enhancement will be used infrequently, can it be worked around with a few lines of script?\nNo, as the proposed solution deals with hardware configuration and the strategic placement of physical trackers to balance budget and immersion.\n\n\nIs there a reason why this should be core and done by us?\nYes, ensuring an immersive VR experience with a limited budget is a fundamental challenge that requires expertise in tracker placement and prioritization.\n\n\nReferences\n\nV-Sekai"
+    "text": "Addressing this issue falls within our core responsibilities as the V-Sekai development team."
   },
   {
-    "objectID": "decisions/20210811-glb-in-video.html",
-    "href": "decisions/20210811-glb-in-video.html",
-    "title": "Proposed: GLB data in a Movie",
+    "objectID": "decisions/20231126-v-sekai-report.html#further-reading",
+    "href": "decisions/20231126-v-sekai-report.html#further-reading",
+    "title": "Accepted: V-Sekai 2023-11-26 Report",
     "section": "",
-    "text": "Proposed: GLB data in a Movie\n\nContext and Problem Statement\nStore ~20 mb of glb data in a mp4.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nMatroska supports storage of related files and data in the Attachments Element (a Top-Level Element). Attachment Elements can be used to store related cover art, font files, transcripts, reports, error recovery files, picture, or text-based annotations, copies of specifications, or other ancillary files related to the Segment.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nStore a glb in a mkv in the attachment sections.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nMaybe a small script.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nInteresting\n\n\nReferences\nhttps://www.matroska.org/technical/attachments.html\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20231110-v-sekai-dependencies.html",
-    "href": "decisions/20231110-v-sekai-dependencies.html",
-    "title": "Accepted: V-Sekai dependencies",
+    "objectID": "decisions/20230830-better-backend-services.html",
+    "href": "decisions/20230830-better-backend-services.html",
+    "title": "Proposed: Integrating Backend Services",
     "section": "",
-    "text": "Status: Proposed \nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nV-Sekai is a rapidly evolving platform with a diverse set of requirements. As the platform grows, so does the need for robust and scalable technologies to support its development.\n\n\n\nThe challenge lies in selecting and integrating the right technologies that can cater to V-Sekai’s unique needs while ensuring scalability, performance, and reliability.\n\n\n\n\n\nElixir is a dynamic, functional language designed for building scalable and maintainable applications. It leverages the Erlang VM, known for running low-latency, distributed and fault-tolerant systems.\ndefmodule Hello do\n def world do\n   IO.puts(\"Hello, World!\")\n end\nend\n\n\n\nCockroachDB is a cloud-native SQL database for building global, scalable cloud services that survive disasters. It’s a distributed SQL database built on a transactional and strongly-consistent key-value store.\nCREATE DATABASE bank;\nUSE bank;\nCREATE TABLE accounts (id INT PRIMARY KEY, balance DECIMAL);\nINSERT INTO accounts VALUES (1, 1000.50);\n\n\n\nSeaweedFS is a simple and highly scalable distributed file system. It focuses on two objectives: storing billions of files, and serving them fast! SeaweedFS implements an object store with O(1) disk seek and an optional Filer with POSIX interface.\nweed master\nweed volume -dir=\"/tmp/1\" -mserver=\"localhost:9333\" -port=8080\ncurl -F file=@/path/to/file http://localhost:9333/dir/assign\nEach of these technologies has its own use cases and can be used in combination depending on the requirements of your project.\n\n\n\n\nThe proposed strategy allows for a scalable, robust, and efficient system that can handle V-Sekai’s growing needs. It also provides a solid foundation for future development and expansion.\n\n\n\nThe downside is the potential complexity of managing multiple technologies and ensuring they work seamlessly together. However, with proper documentation and best practices, this can be mitigated.\n\n\n\nOther technologies could have been considered, but the chosen ones provide the best balance between performance, scalability, and reliability for V-Sekai’s specific needs.\n\n\n\nWhile the proposed technologies are well-suited for most use cases, there may be infrequent scenarios where additional solutions might be needed. These should be evaluated on a case-by-case basis.\n\n\n\nThe integration and management of these technologies will be handled by the V-Sekai team, ensuring that they align with our core values and objectives.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nThis article was assisted by AI."
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nV-Sekai is a virtual reality (VR) platform that offers users the opportunity to immerse themselves in virtual worlds. However, there are certain limitations that hinder the overall user experience. This documentation aims to address these limitations by proposing specific areas for improvement within V-Sekai.\n\n\n\nV-Sekai currently faces several limitations, including non-functional menus in VR mode and a limited number of available worlds. To overcome these challenges and enhance the user experience, we must prioritize and focus on one area for improvement.\n\n\nExploring Backend Services Integration: Integrating V-Sekai with backend services can enhance the platform’s features and capabilities. This could involve incorporating external APIs or services to provide additional resources and functionalities.\n\n\n\n\nTo ensure efficient use of time and resources, it is advisable to choose one area to focus on and strive to complete it within a two-week timeframe. This focused approach allows for significant progress in improving V-Sekai.\n\n\n\nBy addressing these limitations, V-Sekai can be transformed into a more immersive and engaging VR platform. Enhancing menus and object pickup mechanics, expanding the variety of worlds, or integrating backend services can greatly enhance the overall user experience for users.\n\n\n\nGiven the limited timeframe, it may not be possible to address all the identified limitations simultaneously. Prioritizing one area means that other aspects may need to wait for future improvements. Additionally, the complexity of the chosen area may present challenges in achieving substantial improvements within the two-week timeframe.\n\n\n\nWhile focusing on one area is recommended for the given timeframe, it’s important to acknowledge that there are other potential avenues for improvement. Exploring options such as performance optimization, improving UI design, or implementing additional features can be considered in future iterations of V-Sekai.\n\n\n\nThe development team at V-Sekai should primarily handle the implementation and integration of the chosen improvement. However, collaborative efforts, involving developers, designers, and technical writers, are essential for documenting the enhancements.\n\n\n\n\nV-Sekai\nThis article is assisted by AI."
   },
   {
-    "objectID": "decisions/20231110-v-sekai-dependencies.html#metadata",
-    "href": "decisions/20231110-v-sekai-dependencies.html#metadata",
-    "title": "Accepted: V-Sekai dependencies",
+    "objectID": "decisions/20230830-better-backend-services.html#metadata",
+    "href": "decisions/20230830-better-backend-services.html#metadata",
+    "title": "Proposed: Integrating Backend Services",
     "section": "",
-    "text": "Status: Proposed \nDeciders: V-Sekai\nTags: V-Sekai"
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20231110-v-sekai-dependencies.html#the-backdrop",
-    "href": "decisions/20231110-v-sekai-dependencies.html#the-backdrop",
-    "title": "Accepted: V-Sekai dependencies",
+    "objectID": "decisions/20230830-better-backend-services.html#introduction",
+    "href": "decisions/20230830-better-backend-services.html#introduction",
+    "title": "Proposed: Integrating Backend Services",
     "section": "",
-    "text": "V-Sekai is a rapidly evolving platform with a diverse set of requirements. As the platform grows, so does the need for robust and scalable technologies to support its development."
+    "text": "V-Sekai is a virtual reality (VR) platform that offers users the opportunity to immerse themselves in virtual worlds. However, there are certain limitations that hinder the overall user experience. This documentation aims to address these limitations by proposing specific areas for improvement within V-Sekai."
   },
   {
-    "objectID": "decisions/20231110-v-sekai-dependencies.html#the-challenge",
-    "href": "decisions/20231110-v-sekai-dependencies.html#the-challenge",
-    "title": "Accepted: V-Sekai dependencies",
+    "objectID": "decisions/20230830-better-backend-services.html#the-challenge",
+    "href": "decisions/20230830-better-backend-services.html#the-challenge",
+    "title": "Proposed: Integrating Backend Services",
     "section": "",
-    "text": "The challenge lies in selecting and integrating the right technologies that can cater to V-Sekai’s unique needs while ensuring scalability, performance, and reliability."
+    "text": "V-Sekai currently faces several limitations, including non-functional menus in VR mode and a limited number of available worlds. To overcome these challenges and enhance the user experience, we must prioritize and focus on one area for improvement.\n\n\nExploring Backend Services Integration: Integrating V-Sekai with backend services can enhance the platform’s features and capabilities. This could involve incorporating external APIs or services to provide additional resources and functionalities."
   },
   {
-    "objectID": "decisions/20231110-v-sekai-dependencies.html#the-strategy",
-    "href": "decisions/20231110-v-sekai-dependencies.html#the-strategy",
-    "title": "Accepted: V-Sekai dependencies",
+    "objectID": "decisions/20230830-better-backend-services.html#the-strategy",
+    "href": "decisions/20230830-better-backend-services.html#the-strategy",
+    "title": "Proposed: Integrating Backend Services",
     "section": "",
-    "text": "Elixir is a dynamic, functional language designed for building scalable and maintainable applications. It leverages the Erlang VM, known for running low-latency, distributed and fault-tolerant systems.\ndefmodule Hello do\n def world do\n   IO.puts(\"Hello, World!\")\n end\nend\n\n\n\nCockroachDB is a cloud-native SQL database for building global, scalable cloud services that survive disasters. It’s a distributed SQL database built on a transactional and strongly-consistent key-value store.\nCREATE DATABASE bank;\nUSE bank;\nCREATE TABLE accounts (id INT PRIMARY KEY, balance DECIMAL);\nINSERT INTO accounts VALUES (1, 1000.50);\n\n\n\nSeaweedFS is a simple and highly scalable distributed file system. It focuses on two objectives: storing billions of files, and serving them fast! SeaweedFS implements an object store with O(1) disk seek and an optional Filer with POSIX interface.\nweed master\nweed volume -dir=\"/tmp/1\" -mserver=\"localhost:9333\" -port=8080\ncurl -F file=@/path/to/file http://localhost:9333/dir/assign\nEach of these technologies has its own use cases and can be used in combination depending on the requirements of your project."
+    "text": "To ensure efficient use of time and resources, it is advisable to choose one area to focus on and strive to complete it within a two-week timeframe. This focused approach allows for significant progress in improving V-Sekai."
   },
   {
-    "objectID": "decisions/20231110-v-sekai-dependencies.html#the-upside",
-    "href": "decisions/20231110-v-sekai-dependencies.html#the-upside",
-    "title": "Accepted: V-Sekai dependencies",
+    "objectID": "decisions/20230830-better-backend-services.html#upsides",
+    "href": "decisions/20230830-better-backend-services.html#upsides",
+    "title": "Proposed: Integrating Backend Services",
     "section": "",
-    "text": "The proposed strategy allows for a scalable, robust, and efficient system that can handle V-Sekai’s growing needs. It also provides a solid foundation for future development and expansion."
+    "text": "By addressing these limitations, V-Sekai can be transformed into a more immersive and engaging VR platform. Enhancing menus and object pickup mechanics, expanding the variety of worlds, or integrating backend services can greatly enhance the overall user experience for users."
   },
   {
-    "objectID": "decisions/20231110-v-sekai-dependencies.html#the-downside",
-    "href": "decisions/20231110-v-sekai-dependencies.html#the-downside",
-    "title": "Accepted: V-Sekai dependencies",
+    "objectID": "decisions/20230830-better-backend-services.html#downsides",
+    "href": "decisions/20230830-better-backend-services.html#downsides",
+    "title": "Proposed: Integrating Backend Services",
     "section": "",
-    "text": "The downside is the potential complexity of managing multiple technologies and ensuring they work seamlessly together. However, with proper documentation and best practices, this can be mitigated."
+    "text": "Given the limited timeframe, it may not be possible to address all the identified limitations simultaneously. Prioritizing one area means that other aspects may need to wait for future improvements. Additionally, the complexity of the chosen area may present challenges in achieving substantial improvements within the two-week timeframe."
   },
   {
-    "objectID": "decisions/20231110-v-sekai-dependencies.html#the-road-not-taken",
-    "href": "decisions/20231110-v-sekai-dependencies.html#the-road-not-taken",
-    "title": "Accepted: V-Sekai dependencies",
+    "objectID": "decisions/20230830-better-backend-services.html#the-road-not-taken",
+    "href": "decisions/20230830-better-backend-services.html#the-road-not-taken",
+    "title": "Proposed: Integrating Backend Services",
     "section": "",
-    "text": "Other technologies could have been considered, but the chosen ones provide the best balance between performance, scalability, and reliability for V-Sekai’s specific needs."
+    "text": "While focusing on one area is recommended for the given timeframe, it’s important to acknowledge that there are other potential avenues for improvement. Exploring options such as performance optimization, improving UI design, or implementing additional features can be considered in future iterations of V-Sekai."
   },
   {
-    "objectID": "decisions/20231110-v-sekai-dependencies.html#the-infrequent-use-case",
-    "href": "decisions/20231110-v-sekai-dependencies.html#the-infrequent-use-case",
-    "title": "Accepted: V-Sekai dependencies",
+    "objectID": "decisions/20230830-better-backend-services.html#in-core-and-done-by-us",
+    "href": "decisions/20230830-better-backend-services.html#in-core-and-done-by-us",
+    "title": "Proposed: Integrating Backend Services",
     "section": "",
-    "text": "While the proposed technologies are well-suited for most use cases, there may be infrequent scenarios where additional solutions might be needed. These should be evaluated on a case-by-case basis."
+    "text": "The development team at V-Sekai should primarily handle the implementation and integration of the chosen improvement. However, collaborative efforts, involving developers, designers, and technical writers, are essential for documenting the enhancements."
   },
   {
-    "objectID": "decisions/20231110-v-sekai-dependencies.html#in-core-and-done-by-us",
-    "href": "decisions/20231110-v-sekai-dependencies.html#in-core-and-done-by-us",
-    "title": "Accepted: V-Sekai dependencies",
+    "objectID": "decisions/20230830-better-backend-services.html#further-reading",
+    "href": "decisions/20230830-better-backend-services.html#further-reading",
+    "title": "Proposed: Integrating Backend Services",
     "section": "",
-    "text": "The integration and management of these technologies will be handled by the V-Sekai team, ensuring that they align with our core values and objectives."
+    "text": "V-Sekai\nThis article is assisted by AI."
   },
   {
-    "objectID": "decisions/20231110-v-sekai-dependencies.html#further-reading",
-    "href": "decisions/20231110-v-sekai-dependencies.html#further-reading",
-    "title": "Accepted: V-Sekai dependencies",
+    "objectID": "decisions/20231108-ansible-new-server-provisioning.html",
+    "href": "decisions/20231108-ansible-new-server-provisioning.html",
+    "title": "Proposed: Ansible Server Provisioning",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nThis article was assisted by AI."
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nIn the world of DevOps, server provisioning is a critical task. It involves setting up a server to a particular specification. This includes installing an operating system, software packages, and configuring settings.\n\n\n\nThe challenge lies in choosing the right configuration management tool for a small project. Factors such as ease of use, scalability, and community support are crucial.\n\n\n\nBased on these parameters, Ansible emerges as a strong contender. Its simple syntax written in YAML makes it easy to understand even for those new to automation. Being agentless, it’s easier to manage and scale. Moreover, Ansible has a large and active community, providing plenty of resources and support.\n# Sample Ansible playbook\n---\n- hosts: webservers\n  tasks:\n    - name: ensure apache is at the latest version\n      yum:\n        name: httpd\n        state: latest\n\n\n\nChoosing Ansible can simplify server provisioning due to its simplicity and ease of use. It doesn’t require any special coding skills, making it accessible for beginners.\n\n\n\nWhile Ansible is powerful and user-friendly, it may not be as feature-rich as some other tools like Chef or Puppet. However, for a small project, this might not be a significant concern.\n\n\n\nOther tools like Chef, Puppet, and SaltStack were also considered. While they all have their strengths, they may not be as beginner-friendly as Ansible.\n\n\n\nFor complex infrastructures or specific use cases, other tools might be more suitable. It’s always a good idea to try out different tools before making a decision.\n\n\n\nThe decision to use Ansible for server provisioning is proposed by V-Sekai.\n\n\n\n\nV-Sekai\nAnsible Tower: FAQ\n\nThis article was assisted by Aria, an AI."
   },
   {
-    "objectID": "decisions/20230507-supabase.html",
-    "href": "decisions/20230507-supabase.html",
-    "title": "Rejected: Using Deno to handle the conversion of GLB files to Godot Engine packed scenes",
+    "objectID": "decisions/20231108-ansible-new-server-provisioning.html#metadata",
+    "href": "decisions/20231108-ansible-new-server-provisioning.html#metadata",
+    "title": "Proposed: Ansible Server Provisioning",
     "section": "",
-    "text": "Status: rejected \nDeciders: V-Sekai\nTags: V-Sekai, ChatGPT-4\n\n\n\n\nV-Sekai currently has a limitation in converting 3D models from the GLB format to the Godot Engine packed scene format. This conversion process is essential for seamless integration of 3D assets into the V-Sekai platform.\n\n\n\nImplement serverless edge functions using Deno to handle the conversion of GLB files to Godot Engine packed scenes and manage data storage and retrieval.\n\n\n\n\nWasm edge functions: Utilize WebAssembly (Wasm) to run the edge functions efficiently.\nCompute time estimation: Estimate the required compute time for the conversion process.\nData storage: Set up a storage system for the converted Godot packed scenes.\nTable editing UI: Create a user interface for managing the stored Godot packed scenes.\nEdge Function use case: Implement the following serverless Deno functions:\n\nglbToGodotPackedScene: Convert a GLB file to a Godot packed scene and store it.\ninsertGodotPackedScene: Insert a Godot packed scene into the V-Sekai server.\nhelloWorld: Return a JSON object containing “Hello, World!” as a test function.\n\n\n\n\n\n\nSeamless integration of 3D assets into the V-Sekai platform.\nImproved performance and reduced latency due to edge computing.\nScalable and maintainable architecture with serverless functions.\n\n\n\n\n\nAdditional complexity in setting up and managing serverless functions.\nPotential increase in costs due to serverless architecture.\n\n\n\n\nUse the current process of editor upload.\n\n\n\nNo, this enhancement is essential for the seamless integration of 3D assets into the V-Sekai platform and cannot be easily worked around with a simple script.\n\n\n\nYes, this feature is crucial for the V-Sekai platform’s functionality and user experience. Implementing it as a core feature ensures that it is well-integrated, maintainable, and scalable.\n\n\n\n\nV-Sekai"
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20230507-supabase.html#metadata",
-    "href": "decisions/20230507-supabase.html#metadata",
-    "title": "Rejected: Using Deno to handle the conversion of GLB files to Godot Engine packed scenes",
+    "objectID": "decisions/20231108-ansible-new-server-provisioning.html#the-backdrop",
+    "href": "decisions/20231108-ansible-new-server-provisioning.html#the-backdrop",
+    "title": "Proposed: Ansible Server Provisioning",
     "section": "",
-    "text": "Status: rejected \nDeciders: V-Sekai\nTags: V-Sekai, ChatGPT-4"
+    "text": "In the world of DevOps, server provisioning is a critical task. It involves setting up a server to a particular specification. This includes installing an operating system, software packages, and configuring settings."
   },
   {
-    "objectID": "decisions/20230507-supabase.html#context-and-problem-statement",
-    "href": "decisions/20230507-supabase.html#context-and-problem-statement",
-    "title": "Rejected: Using Deno to handle the conversion of GLB files to Godot Engine packed scenes",
+    "objectID": "decisions/20231108-ansible-new-server-provisioning.html#the-challenge",
+    "href": "decisions/20231108-ansible-new-server-provisioning.html#the-challenge",
+    "title": "Proposed: Ansible Server Provisioning",
     "section": "",
-    "text": "V-Sekai currently has a limitation in converting 3D models from the GLB format to the Godot Engine packed scene format. This conversion process is essential for seamless integration of 3D assets into the V-Sekai platform."
+    "text": "The challenge lies in choosing the right configuration management tool for a small project. Factors such as ease of use, scalability, and community support are crucial."
   },
   {
-    "objectID": "decisions/20230507-supabase.html#proposed-solution",
-    "href": "decisions/20230507-supabase.html#proposed-solution",
-    "title": "Rejected: Using Deno to handle the conversion of GLB files to Godot Engine packed scenes",
+    "objectID": "decisions/20231108-ansible-new-server-provisioning.html#the-strategy",
+    "href": "decisions/20231108-ansible-new-server-provisioning.html#the-strategy",
+    "title": "Proposed: Ansible Server Provisioning",
     "section": "",
-    "text": "Implement serverless edge functions using Deno to handle the conversion of GLB files to Godot Engine packed scenes and manage data storage and retrieval."
+    "text": "Based on these parameters, Ansible emerges as a strong contender. Its simple syntax written in YAML makes it easy to understand even for those new to automation. Being agentless, it’s easier to manage and scale. Moreover, Ansible has a large and active community, providing plenty of resources and support.\n# Sample Ansible playbook\n---\n- hosts: webservers\n  tasks:\n    - name: ensure apache is at the latest version\n      yum:\n        name: httpd\n        state: latest"
   },
   {
-    "objectID": "decisions/20230507-supabase.html#implementation",
-    "href": "decisions/20230507-supabase.html#implementation",
-    "title": "Rejected: Using Deno to handle the conversion of GLB files to Godot Engine packed scenes",
+    "objectID": "decisions/20231108-ansible-new-server-provisioning.html#the-upside",
+    "href": "decisions/20231108-ansible-new-server-provisioning.html#the-upside",
+    "title": "Proposed: Ansible Server Provisioning",
     "section": "",
-    "text": "Wasm edge functions: Utilize WebAssembly (Wasm) to run the edge functions efficiently.\nCompute time estimation: Estimate the required compute time for the conversion process.\nData storage: Set up a storage system for the converted Godot packed scenes.\nTable editing UI: Create a user interface for managing the stored Godot packed scenes.\nEdge Function use case: Implement the following serverless Deno functions:\n\nglbToGodotPackedScene: Convert a GLB file to a Godot packed scene and store it.\ninsertGodotPackedScene: Insert a Godot packed scene into the V-Sekai server.\nhelloWorld: Return a JSON object containing “Hello, World!” as a test function."
+    "text": "Choosing Ansible can simplify server provisioning due to its simplicity and ease of use. It doesn’t require any special coding skills, making it accessible for beginners."
   },
   {
-    "objectID": "decisions/20230507-supabase.html#positive-consequences",
-    "href": "decisions/20230507-supabase.html#positive-consequences",
-    "title": "Rejected: Using Deno to handle the conversion of GLB files to Godot Engine packed scenes",
+    "objectID": "decisions/20231108-ansible-new-server-provisioning.html#the-downside",
+    "href": "decisions/20231108-ansible-new-server-provisioning.html#the-downside",
+    "title": "Proposed: Ansible Server Provisioning",
     "section": "",
-    "text": "Seamless integration of 3D assets into the V-Sekai platform.\nImproved performance and reduced latency due to edge computing.\nScalable and maintainable architecture with serverless functions."
+    "text": "While Ansible is powerful and user-friendly, it may not be as feature-rich as some other tools like Chef or Puppet. However, for a small project, this might not be a significant concern."
   },
   {
-    "objectID": "decisions/20230507-supabase.html#negative-consequences",
-    "href": "decisions/20230507-supabase.html#negative-consequences",
-    "title": "Rejected: Using Deno to handle the conversion of GLB files to Godot Engine packed scenes",
+    "objectID": "decisions/20231108-ansible-new-server-provisioning.html#the-road-not-taken",
+    "href": "decisions/20231108-ansible-new-server-provisioning.html#the-road-not-taken",
+    "title": "Proposed: Ansible Server Provisioning",
     "section": "",
-    "text": "Additional complexity in setting up and managing serverless functions.\nPotential increase in costs due to serverless architecture."
+    "text": "Other tools like Chef, Puppet, and SaltStack were also considered. While they all have their strengths, they may not be as beginner-friendly as Ansible."
   },
   {
-    "objectID": "decisions/20230507-supabase.html#option-graveyard",
-    "href": "decisions/20230507-supabase.html#option-graveyard",
-    "title": "Rejected: Using Deno to handle the conversion of GLB files to Godot Engine packed scenes",
+    "objectID": "decisions/20231108-ansible-new-server-provisioning.html#the-infrequent-use-case",
+    "href": "decisions/20231108-ansible-new-server-provisioning.html#the-infrequent-use-case",
+    "title": "Proposed: Ansible Server Provisioning",
     "section": "",
-    "text": "Use the current process of editor upload."
+    "text": "For complex infrastructures or specific use cases, other tools might be more suitable. It’s always a good idea to try out different tools before making a decision."
   },
   {
-    "objectID": "decisions/20230507-supabase.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230507-supabase.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Rejected: Using Deno to handle the conversion of GLB files to Godot Engine packed scenes",
+    "objectID": "decisions/20231108-ansible-new-server-provisioning.html#in-core-and-done-by-us",
+    "href": "decisions/20231108-ansible-new-server-provisioning.html#in-core-and-done-by-us",
+    "title": "Proposed: Ansible Server Provisioning",
     "section": "",
-    "text": "No, this enhancement is essential for the seamless integration of 3D assets into the V-Sekai platform and cannot be easily worked around with a simple script."
+    "text": "The decision to use Ansible for server provisioning is proposed by V-Sekai."
   },
   {
-    "objectID": "decisions/20230507-supabase.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230507-supabase.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Rejected: Using Deno to handle the conversion of GLB files to Godot Engine packed scenes",
+    "objectID": "decisions/20231108-ansible-new-server-provisioning.html#further-reading",
+    "href": "decisions/20231108-ansible-new-server-provisioning.html#further-reading",
+    "title": "Proposed: Ansible Server Provisioning",
     "section": "",
-    "text": "Yes, this feature is crucial for the V-Sekai platform’s functionality and user experience. Implementing it as a core feature ensures that it is well-integrated, maintainable, and scalable."
+    "text": "V-Sekai\nAnsible Tower: FAQ\n\nThis article was assisted by Aria, an AI."
   },
   {
-    "objectID": "decisions/20230507-supabase.html#references",
-    "href": "decisions/20230507-supabase.html#references",
-    "title": "Rejected: Using Deno to handle the conversion of GLB files to Godot Engine packed scenes",
+    "objectID": "decisions/20230527-godot-test-game.html",
+    "href": "decisions/20230527-godot-test-game.html",
+    "title": "Proposed: Create a 12x12 meter 3D demo map with 2-meter-high obstacles and walls",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, GPT-4\n\n\n\n\nV-Sekai users struggle navigating complex 3D environments with obstacles and walls, limiting user experience and potential applications.\n\n\n\nCreate a 12x12 meter 3D map with 2-meter-high obstacles and walls. Implement a navigation system for users to move around while avoiding obstacles and walls.\n\n\n\n\nDesign the 3D map using modeling software (e.g., Blender).\nImport the map into a game engine.\nImplement a character controller for navigation.\nAdd collision detection and response.\nOptimize navigation system performance.\n\n\n\n\n\nImproved user experience.\nIncreased V-Sekai applications.\nEnhanced immersion.\n\n\n\n\n\nAdditional development time and resources.\nPotential performance issues if not optimized.\n\n\n\n\n\nUsing pre-built navigation systems.\nIgnoring the limitation.\n\n\n\n\nNo simple workaround; complex implementation required for seamless user experience.\n\n\n\nImproving navigation is essential for enhancing user experience and expanding V-Sekai’s potential applications.\n\n\n\n\nV-Sekai"
   },
   {
-    "objectID": "decisions/20230623-fdn-reverb-solution.html",
-    "href": "decisions/20230623-fdn-reverb-solution.html",
-    "title": "Proposed: Implementing Feedback Delay Networks for Enhanced Audio Reverb Simulation in V-Sekai",
+    "objectID": "decisions/20230527-godot-test-game.html#metadata",
+    "href": "decisions/20230527-godot-test-game.html#metadata",
+    "title": "Proposed: Create a 12x12 meter 3D demo map with 2-meter-high obstacles and walls",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai, ellenhp, fire\nTags: V-Sekai, ai assisted\n\n\n\n\nThe problem of simulating audio reverb in Godot Engine 4 involves accurately modeling the way sound waves propagate, reflect, and interact within a given environment. This requires sampling a chaotic 7-dimensional space every frame, either through precomputation or real-time processing. The complexity arises from the fact that sound behaves more like light with intense diffraction, making it impossible to rasterize.\n\n\n\nImplement Feedback Delay Networks (FDNs) for artificial reverberation. FDNs consist of multiple delay lines connected in a feedback loop with a mixing matrix. The output is a combination of the input signal and the delayed signals.\n\n\n\nChoose the number of delay lines and their lengths based on the desired reverberation time and room characteristics.\nImplement a mixing matrix to control the energy distribution between the delay lines.\nCreate a feedback loop by connecting the outputs of the delay lines to the inputs through the mixing matrix.\nCombine the input signal with the delayed signals to produce the reverberated output.\n\n\n\n\n\nclass_name FDN\nextends Node\n\nvar num_delay_lines : int\nvar delay_lines : Array\nvar mixing_matrix : Array\nvar room_characteristics : Dictionary\n\nfunc _init(num_delay_lines: int, delay_lengths: Array, mixing_matrix: Array, room_characteristics: Dictionary):\n    self.num_delay_lines = num_delay_lines\n    self.delay_lines = []\n    for length in delay_lengths:\n        self.delay_lines.append(DelayLine.new(length))\n    self.mixing_matrix = mixing_matrix\n    self.room_characteristics = room_characteristics\n\nfunc process(input_signal: float) -&gt; float:\n    # Step 1: Calculate the output of each delay line\n    var delay_outputs = []\n    for dl in self.delay_lines:\n        delay_outputs.append(dl.process(input_signal))\n\n    # Step 2: Apply the room characteristics to the delay line outputs\n    var processed_outputs = apply_room_characteristics(delay_outputs)\n\n    # Step 3: Apply the mixing matrix to the processed delay line outputs\n    var mixed_outputs = apply_mixing_matrix(processed_outputs)\n\n    # Step 4: Update the delay lines with the mixed outputs\n    for i in range(self.num_delay_lines):\n        self.delay_lines[i].update(mixed_outputs[i])\n\n    # Step 5: Combine the input signal with the delayed signals\n    var output_signal = input_signal + sum(mixed_outputs)\n    return output_signal\n\nfunc apply_room_characteristics(delay_outputs: Array) -&gt; Array:\n    var processed_outputs = []\n    for i in range(len(delay_outputs)):\n        processed_output = delay_outputs[i] * room_characteristics[\"absorption\"][i]\n        processed_outputs.append(processed_output)\n    return processed_outputs\n\nfunc apply_mixing_matrix(delay_outputs: Array) -&gt; Array:\n    # TODO: Implement the mixing matrix application logic\n    pass\n\n\n\n\nImproved audio reverb simulation\nMore realistic sound propagation and interaction within environments\nSmarter estimation of long reverb times\n\n\n\n\n\nIncreased computational complexity\nPotential performance impact on real-time processing\n\n\n\n\n\nGeneralized Dijkstra Pathfinding\nDWN (Digital Waveguide Network): A method for simulating audio reverb by modeling sound propagation as waves traveling along waveguides with bidirectional delay lines and scattering junctions.\nRay tracing can be used to simulate sound propagation in 3D environments. It involves casting rays from the sound source and tracing their paths as they interact with the environment (reflect, refract, and diffract). By calculating the time delay and attenuation of each ray reaching the listener, you can generate an impulse response that represents the acoustic properties of the space.\nConvolution reverb is a technique that uses recorded impulse responses (IRs) of real spaces or digital simulations to recreate the reverberation characteristics of those spaces. The process involves convolving the dry audio signal with the impulse response to produce the reverberated audio.\n\n\n\n\nNo, implementing FDNs requires a more complex algorithm and cannot be achieved with just a few lines of script.\n\n\n\nYes, as it directly impacts the audio experience within V-Sekai environments, it should be a core feature to ensure consistent and high-quality audio reverb simulation.\n\n\n\n\nV-Sekai: A virtual reality platform that allows users to create and explore immersive environments.\nGodot Engine 4: An open-source game engine used for creating 2D and 3D games and interactive applications.\nAudio Reverb: The persistence of sound in a particular space after the original sound has stopped, caused by reflections off surfaces within the environment.\nFeedback Delay Networks (FDNs): A method for simulating artificial reverberation using multiple delay lines connected in a feedback loop with a mixing matrix.\nDelay Line: A digital signal processing technique that introduces a time delay to an input signal, often used in audio effects such as reverb and echo.\nMixing Matrix: A mathematical construct used to control the energy distribution between the delay lines in an FDN.\nRoom Characteristics: Acoustic properties of a room or environment, such as absorption, reflection, and diffusion, which affect how sound propagates within the space.\nReverberation Time: The time it takes for the sound level in a room to decrease by 60 decibels after the sound source has stopped.\nDigital Waveguide Network (DWN): An alternative method for simulating audio reverb by modeling sound propagation as waves traveling along waveguides with bidirectional delay lines and scattering junctions.\nRay Tracing: A technique used to simulate sound propagation in 3D environments by casting rays from the sound source and tracing their paths as they interact with the environment (reflect, refract, and diffract).\nConvolution Reverb: A technique that uses recorded impulse responses (IRs) of real spaces or digital simulations to recreate the reverberation characteristics of those spaces by convolving the dry audio signal with the impulse response.\nImpulse Response (IR): A recording or simulation of the acoustic properties of a space, used in convolution reverb to recreate the reverberation characteristics of that space.\n\n\n\n\nLet’s consider an example of implementing a Feedback Delay Network (FDN) for audio reverb simulation with 8 delay lines. We will analyze the computational and I/O complexity involved in this specific case.\n\n\n\nFor a medium-quality reverb effect, let’s consider using 8 delay lines in the FDN.\nFor an 8x8 matrix, there are 64 multiplications and 56 additions required for each sample.\nOverall, the computational complexity for a medium-quality reverb effect with 8 delay lines is manageable for most modern CPUs and can be efficiently processed in real-time.\nIn summary, implementing a medium-quality reverb effect using an FDN with 8 delay lines has a manageable computational and I/O complexity, making it suitable for real-time processing on most modern hardware.\n\n\n\n\nFor a medium-quality reverb effect, let’s consider using 8 delay lines in the FDN. The main components contributing to the computational complexity are:\n\nDelay Lines: Each delay line requires memory for storing the delayed samples and computations for updating the delay buffer. For 8 delay lines, the complexity scales linearly with the number of delay lines.\nMatrix Mixing: The mixing matrix combines the outputs of the delay lines in a specific way to create the desired reverb effect. For an 8x8 matrix, there are 64 multiplications and 56 additions required for each sample.\nFeedback and Input/Output Processing: Additional processing, such as filtering or gain adjustments, may be applied to the input, output, or feedback paths. This complexity depends on the specific filters or processing used but is generally proportional to the number of delay lines.\n\nOverall, the computational complexity for a medium-quality reverb effect with 8 delay lines is manageable for most modern CPUs and can be efficiently processed in real-time.\n\n\n\nThe I/O complexity refers to the amount of data that needs to be read from and written to memory during the processing of the reverb effect. In the case of an FDN with 8 delay lines, the I/O complexity is mainly determined by:\n\nReading and Writing Delay Line Buffers: Each delay line requires reading and writing operations for updating the delay buffer. The I/O complexity scales linearly with the number of delay lines.\nInput and Output Audio Data: The audio input data must be read, processed, and combined with the output of the FDN to generate the final reverberated audio signal. The I/O complexity for input and output audio data is generally low compared to the delay line buffer operations.\n\nIn summary, implementing a medium-quality reverb effect using an FDN with 8 delay lines has a manageable computational and I/O complexity, making it suitable for real-time processing on most modern hardware."
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, GPT-4"
   },
   {
-    "objectID": "decisions/20230623-fdn-reverb-solution.html#metadata",
-    "href": "decisions/20230623-fdn-reverb-solution.html#metadata",
-    "title": "Proposed: Implementing Feedback Delay Networks for Enhanced Audio Reverb Simulation in V-Sekai",
+    "objectID": "decisions/20230527-godot-test-game.html#problem-statement",
+    "href": "decisions/20230527-godot-test-game.html#problem-statement",
+    "title": "Proposed: Create a 12x12 meter 3D demo map with 2-meter-high obstacles and walls",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai, ellenhp, fire\nTags: V-Sekai, ai assisted"
+    "text": "V-Sekai users struggle navigating complex 3D environments with obstacles and walls, limiting user experience and potential applications."
   },
   {
-    "objectID": "decisions/20230623-fdn-reverb-solution.html#context-and-problem-statement",
-    "href": "decisions/20230623-fdn-reverb-solution.html#context-and-problem-statement",
-    "title": "Proposed: Implementing Feedback Delay Networks for Enhanced Audio Reverb Simulation in V-Sekai",
+    "objectID": "decisions/20230527-godot-test-game.html#proposed-solution",
+    "href": "decisions/20230527-godot-test-game.html#proposed-solution",
+    "title": "Proposed: Create a 12x12 meter 3D demo map with 2-meter-high obstacles and walls",
     "section": "",
-    "text": "The problem of simulating audio reverb in Godot Engine 4 involves accurately modeling the way sound waves propagate, reflect, and interact within a given environment. This requires sampling a chaotic 7-dimensional space every frame, either through precomputation or real-time processing. The complexity arises from the fact that sound behaves more like light with intense diffraction, making it impossible to rasterize."
+    "text": "Create a 12x12 meter 3D map with 2-meter-high obstacles and walls. Implement a navigation system for users to move around while avoiding obstacles and walls."
   },
   {
-    "objectID": "decisions/20230623-fdn-reverb-solution.html#proposed-solution",
-    "href": "decisions/20230623-fdn-reverb-solution.html#proposed-solution",
-    "title": "Proposed: Implementing Feedback Delay Networks for Enhanced Audio Reverb Simulation in V-Sekai",
+    "objectID": "decisions/20230527-godot-test-game.html#implementation",
+    "href": "decisions/20230527-godot-test-game.html#implementation",
+    "title": "Proposed: Create a 12x12 meter 3D demo map with 2-meter-high obstacles and walls",
     "section": "",
-    "text": "Implement Feedback Delay Networks (FDNs) for artificial reverberation. FDNs consist of multiple delay lines connected in a feedback loop with a mixing matrix. The output is a combination of the input signal and the delayed signals.\n\n\n\nChoose the number of delay lines and their lengths based on the desired reverberation time and room characteristics.\nImplement a mixing matrix to control the energy distribution between the delay lines.\nCreate a feedback loop by connecting the outputs of the delay lines to the inputs through the mixing matrix.\nCombine the input signal with the delayed signals to produce the reverberated output."
+    "text": "Design the 3D map using modeling software (e.g., Blender).\nImport the map into a game engine.\nImplement a character controller for navigation.\nAdd collision detection and response.\nOptimize navigation system performance."
   },
   {
-    "objectID": "decisions/20230623-fdn-reverb-solution.html#implementation",
-    "href": "decisions/20230623-fdn-reverb-solution.html#implementation",
-    "title": "Proposed: Implementing Feedback Delay Networks for Enhanced Audio Reverb Simulation in V-Sekai",
+    "objectID": "decisions/20230527-godot-test-game.html#positive-consequences",
+    "href": "decisions/20230527-godot-test-game.html#positive-consequences",
+    "title": "Proposed: Create a 12x12 meter 3D demo map with 2-meter-high obstacles and walls",
     "section": "",
-    "text": "class_name FDN\nextends Node\n\nvar num_delay_lines : int\nvar delay_lines : Array\nvar mixing_matrix : Array\nvar room_characteristics : Dictionary\n\nfunc _init(num_delay_lines: int, delay_lengths: Array, mixing_matrix: Array, room_characteristics: Dictionary):\n    self.num_delay_lines = num_delay_lines\n    self.delay_lines = []\n    for length in delay_lengths:\n        self.delay_lines.append(DelayLine.new(length))\n    self.mixing_matrix = mixing_matrix\n    self.room_characteristics = room_characteristics\n\nfunc process(input_signal: float) -&gt; float:\n    # Step 1: Calculate the output of each delay line\n    var delay_outputs = []\n    for dl in self.delay_lines:\n        delay_outputs.append(dl.process(input_signal))\n\n    # Step 2: Apply the room characteristics to the delay line outputs\n    var processed_outputs = apply_room_characteristics(delay_outputs)\n\n    # Step 3: Apply the mixing matrix to the processed delay line outputs\n    var mixed_outputs = apply_mixing_matrix(processed_outputs)\n\n    # Step 4: Update the delay lines with the mixed outputs\n    for i in range(self.num_delay_lines):\n        self.delay_lines[i].update(mixed_outputs[i])\n\n    # Step 5: Combine the input signal with the delayed signals\n    var output_signal = input_signal + sum(mixed_outputs)\n    return output_signal\n\nfunc apply_room_characteristics(delay_outputs: Array) -&gt; Array:\n    var processed_outputs = []\n    for i in range(len(delay_outputs)):\n        processed_output = delay_outputs[i] * room_characteristics[\"absorption\"][i]\n        processed_outputs.append(processed_output)\n    return processed_outputs\n\nfunc apply_mixing_matrix(delay_outputs: Array) -&gt; Array:\n    # TODO: Implement the mixing matrix application logic\n    pass"
+    "text": "Improved user experience.\nIncreased V-Sekai applications.\nEnhanced immersion."
   },
   {
-    "objectID": "decisions/20230623-fdn-reverb-solution.html#positive-consequences",
-    "href": "decisions/20230623-fdn-reverb-solution.html#positive-consequences",
-    "title": "Proposed: Implementing Feedback Delay Networks for Enhanced Audio Reverb Simulation in V-Sekai",
+    "objectID": "decisions/20230527-godot-test-game.html#negative-consequences",
+    "href": "decisions/20230527-godot-test-game.html#negative-consequences",
+    "title": "Proposed: Create a 12x12 meter 3D demo map with 2-meter-high obstacles and walls",
     "section": "",
-    "text": "Improved audio reverb simulation\nMore realistic sound propagation and interaction within environments\nSmarter estimation of long reverb times"
+    "text": "Additional development time and resources.\nPotential performance issues if not optimized."
   },
   {
-    "objectID": "decisions/20230623-fdn-reverb-solution.html#negative-consequences",
-    "href": "decisions/20230623-fdn-reverb-solution.html#negative-consequences",
-    "title": "Proposed: Implementing Feedback Delay Networks for Enhanced Audio Reverb Simulation in V-Sekai",
+    "objectID": "decisions/20230527-godot-test-game.html#option-graveyard",
+    "href": "decisions/20230527-godot-test-game.html#option-graveyard",
+    "title": "Proposed: Create a 12x12 meter 3D demo map with 2-meter-high obstacles and walls",
     "section": "",
-    "text": "Increased computational complexity\nPotential performance impact on real-time processing"
+    "text": "Using pre-built navigation systems.\nIgnoring the limitation."
   },
   {
-    "objectID": "decisions/20230623-fdn-reverb-solution.html#option-graveyard",
-    "href": "decisions/20230623-fdn-reverb-solution.html#option-graveyard",
-    "title": "Proposed: Implementing Feedback Delay Networks for Enhanced Audio Reverb Simulation in V-Sekai",
+    "objectID": "decisions/20230527-godot-test-game.html#enhancement-workaround",
+    "href": "decisions/20230527-godot-test-game.html#enhancement-workaround",
+    "title": "Proposed: Create a 12x12 meter 3D demo map with 2-meter-high obstacles and walls",
     "section": "",
-    "text": "Generalized Dijkstra Pathfinding\nDWN (Digital Waveguide Network): A method for simulating audio reverb by modeling sound propagation as waves traveling along waveguides with bidirectional delay lines and scattering junctions.\nRay tracing can be used to simulate sound propagation in 3D environments. It involves casting rays from the sound source and tracing their paths as they interact with the environment (reflect, refract, and diffract). By calculating the time delay and attenuation of each ray reaching the listener, you can generate an impulse response that represents the acoustic properties of the space.\nConvolution reverb is a technique that uses recorded impulse responses (IRs) of real spaces or digital simulations to recreate the reverberation characteristics of those spaces. The process involves convolving the dry audio signal with the impulse response to produce the reverberated audio."
+    "text": "No simple workaround; complex implementation required for seamless user experience."
   },
   {
-    "objectID": "decisions/20230623-fdn-reverb-solution.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230623-fdn-reverb-solution.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Implementing Feedback Delay Networks for Enhanced Audio Reverb Simulation in V-Sekai",
+    "objectID": "decisions/20230527-godot-test-game.html#core-reasoning",
+    "href": "decisions/20230527-godot-test-game.html#core-reasoning",
+    "title": "Proposed: Create a 12x12 meter 3D demo map with 2-meter-high obstacles and walls",
     "section": "",
-    "text": "No, implementing FDNs requires a more complex algorithm and cannot be achieved with just a few lines of script."
+    "text": "Improving navigation is essential for enhancing user experience and expanding V-Sekai’s potential applications."
   },
   {
-    "objectID": "decisions/20230623-fdn-reverb-solution.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230623-fdn-reverb-solution.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Implementing Feedback Delay Networks for Enhanced Audio Reverb Simulation in V-Sekai",
+    "objectID": "decisions/20230527-godot-test-game.html#references",
+    "href": "decisions/20230527-godot-test-game.html#references",
+    "title": "Proposed: Create a 12x12 meter 3D demo map with 2-meter-high obstacles and walls",
     "section": "",
-    "text": "Yes, as it directly impacts the audio experience within V-Sekai environments, it should be a core feature to ensure consistent and high-quality audio reverb simulation."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20230623-fdn-reverb-solution.html#glossary-implementing-feedback-delay-networks-for-enhanced-audio-reverb-simulation-in-v-sekai",
-    "href": "decisions/20230623-fdn-reverb-solution.html#glossary-implementing-feedback-delay-networks-for-enhanced-audio-reverb-simulation-in-v-sekai",
-    "title": "Proposed: Implementing Feedback Delay Networks for Enhanced Audio Reverb Simulation in V-Sekai",
+    "objectID": "decisions/20230123-no-traversal-loading-screen.html",
+    "href": "decisions/20230123-no-traversal-loading-screen.html",
+    "title": "Proposed: No traversal loading screen",
     "section": "",
-    "text": "V-Sekai: A virtual reality platform that allows users to create and explore immersive environments.\nGodot Engine 4: An open-source game engine used for creating 2D and 3D games and interactive applications.\nAudio Reverb: The persistence of sound in a particular space after the original sound has stopped, caused by reflections off surfaces within the environment.\nFeedback Delay Networks (FDNs): A method for simulating artificial reverberation using multiple delay lines connected in a feedback loop with a mixing matrix.\nDelay Line: A digital signal processing technique that introduces a time delay to an input signal, often used in audio effects such as reverb and echo.\nMixing Matrix: A mathematical construct used to control the energy distribution between the delay lines in an FDN.\nRoom Characteristics: Acoustic properties of a room or environment, such as absorption, reflection, and diffusion, which affect how sound propagates within the space.\nReverberation Time: The time it takes for the sound level in a room to decrease by 60 decibels after the sound source has stopped.\nDigital Waveguide Network (DWN): An alternative method for simulating audio reverb by modeling sound propagation as waves traveling along waveguides with bidirectional delay lines and scattering junctions.\nRay Tracing: A technique used to simulate sound propagation in 3D environments by casting rays from the sound source and tracing their paths as they interact with the environment (reflect, refract, and diffract).\nConvolution Reverb: A technique that uses recorded impulse responses (IRs) of real spaces or digital simulations to recreate the reverberation characteristics of those spaces by convolving the dry audio signal with the impulse response.\nImpulse Response (IR): A recording or simulation of the acoustic properties of a space, used in convolution reverb to recreate the reverberation characteristics of that space."
+    "text": "Proposed: No traversal loading screen\n\nMetadata\n\nStatus: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nContext and Problem Statement\nThis is a proposal to mask the loading time, but it doesn’t solve it.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nTrim the steps needed to enter the game.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nWhen you first start up the application, you will see a loading screen. This screen will be displayed until all the assets needed to load your world have been downloaded.\nWhen switching between worlds, there is technically no need for a loading screen. Both leading platforms have chosen to include one in their applications, but this is not necessary. The leading platform displays a loading screen when clicking to go to a new world, while the secondary leading platform does not display one–you stay in your original world while also loading into the second world and then switch over once enough of it has been downloaded that you can be there.\nYou click go and are left in your current world while loading in the other world, once the other world is completely loaded in you are transported to it instantaneously.\n\n\nPositive Consequences\nAble to mask loading times\nAble to direct players to the positive parts of v-sekai\nFor style points we could enforce portals that seamlessly transport you between different worlds, at least, as the default option, you place a portal, it has a camera, and you can walk through it, and after a certain point it disappears.\n\n\nNegative Consequences\ncoordinating cats\nThe drawback to the multi-world load is that it is more resource intensive, though it should only last a short while, so if we do go that route it should be an option to use a loading screen instead.\nIt makes for a far less friction-less experience\nBut again, resource intensive issues, so will have to be optional\nWe could even add a little button you click once you are ready to be transported, so it doesn’t happen against your will if your trying to say something last minute.\n\n\nOption graveyard\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot script.\n\n\nIs there a reason why this should be core and done by us?\nWorld traversal is a problem.\n\n\nReferences\n\nV-Sekai\n\n\n\nLicense of the contribution\nMIT License\n\nCopyright (c) 2018-present SaracenOne\nCopyright (c) 2019-present K. S. Ernest (iFire) Lee (fire)\nCopyright (c) 2020-present Lyuma\nCopyright (c) 2020-present MMMaellon\nCopyright (c) 2022-present See authors.md\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
   },
   {
-    "objectID": "decisions/20230623-fdn-reverb-solution.html#computational-and-io-complexity-an-example",
-    "href": "decisions/20230623-fdn-reverb-solution.html#computational-and-io-complexity-an-example",
-    "title": "Proposed: Implementing Feedback Delay Networks for Enhanced Audio Reverb Simulation in V-Sekai",
+    "objectID": "decisions/20211031-play-preprocessed-animations-on-any-vrm-model.html",
+    "href": "decisions/20211031-play-preprocessed-animations-on-any-vrm-model.html",
+    "title": "Superseded: Play preprocessed #animation on any VRM model",
     "section": "",
-    "text": "Let’s consider an example of implementing a Feedback Delay Network (FDN) for audio reverb simulation with 8 delay lines. We will analyze the computational and I/O complexity involved in this specific case.\n\n\n\nFor a medium-quality reverb effect, let’s consider using 8 delay lines in the FDN.\nFor an 8x8 matrix, there are 64 multiplications and 56 additions required for each sample.\nOverall, the computational complexity for a medium-quality reverb effect with 8 delay lines is manageable for most modern CPUs and can be efficiently processed in real-time.\nIn summary, implementing a medium-quality reverb effect using an FDN with 8 delay lines has a manageable computational and I/O complexity, making it suitable for real-time processing on most modern hardware.\n\n\n\n\nFor a medium-quality reverb effect, let’s consider using 8 delay lines in the FDN. The main components contributing to the computational complexity are:\n\nDelay Lines: Each delay line requires memory for storing the delayed samples and computations for updating the delay buffer. For 8 delay lines, the complexity scales linearly with the number of delay lines.\nMatrix Mixing: The mixing matrix combines the outputs of the delay lines in a specific way to create the desired reverb effect. For an 8x8 matrix, there are 64 multiplications and 56 additions required for each sample.\nFeedback and Input/Output Processing: Additional processing, such as filtering or gain adjustments, may be applied to the input, output, or feedback paths. This complexity depends on the specific filters or processing used but is generally proportional to the number of delay lines.\n\nOverall, the computational complexity for a medium-quality reverb effect with 8 delay lines is manageable for most modern CPUs and can be efficiently processed in real-time.\n\n\n\nThe I/O complexity refers to the amount of data that needs to be read from and written to memory during the processing of the reverb effect. In the case of an FDN with 8 delay lines, the I/O complexity is mainly determined by:\n\nReading and Writing Delay Line Buffers: Each delay line requires reading and writing operations for updating the delay buffer. The I/O complexity scales linearly with the number of delay lines.\nInput and Output Audio Data: The audio input data must be read, processed, and combined with the output of the FDN to generate the final reverberated audio signal. The I/O complexity for input and output audio data is generally low compared to the delay line buffer operations.\n\nIn summary, implementing a medium-quality reverb effect using an FDN with 8 delay lines has a manageable computational and I/O complexity, making it suitable for real-time processing on most modern hardware."
+    "text": "Superseded: Play preprocessed #animation on any VRM model\nSuperseded\nThis is now a Godot Engine 4.0 core feature. https://godotengine.org/article/animation-retargeting-in-godot-4-0/\n\nContext and Problem Statement\nGiven any vrm and a carefully made animation, we should be able to play back the animation.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nNeed to work out a flow for making #animation play back on vrm.\nThis is dependency for a VRM based character controller that can play existing #animation clips and blend them\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n???\nCollaborate with Saracen on a bone roll corrected VRM skeleton.\nConvert #animation to VRM named bones.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot trivial.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nWe control the default #animation tree, therefore we need to do this.\n\n\nReferences\n\nProposal on baking blend shapes to linear skin blending.\nUseful for tokage’s character movement demo. https://github.com/TokageItLab/3d-platform-test-for-godot4\nFree #animation – https://github.com/V-Sekai/shadermotion-video-to-anims\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240326-verifying-and-finetuning-plans.html",
-    "href": "decisions/20240326-verifying-and-finetuning-plans.html",
-    "title": "Proposed: Teaching Large Language Models (LLMs) with Goal-Task Planners",
+    "objectID": "decisions/20210612-flow-avatar-asset-pipeline.html",
+    "href": "decisions/20210612-flow-avatar-asset-pipeline.html",
+    "title": "Proposed: Convert FBX and glTF2 to VRM via flow-avatar-asset-pipeline",
     "section": "",
-    "text": "We’re looking at using LLMs and goal-task planners like pyhop to generate innovative, executable plans. This approach combines the creativity of LLMs with the structured planning processes of goal-task planners.\n\n\n\nThe main challenges are computational overhead due to the two-step process and potential inaccuracies in the feasibility check.\n\n\n\nWe propose using an LLM for idea generation and a goal-task planner for checking feasibility. This could lead to creative and feasible plans. The accurate plans generated by this model can then be used to further train the LLM.\n# Pseudo-code\ngpt = GPT()\nidea = gpt.generate_idea()\n\npyhop = Pyhop()\nfeasible = pyhop.find_plan(state, goal_generator())\n\nif feasible:\n    gpt.train(idea)\n\n\n\n\nInnovation: Using LLMs for idea generation can lead to creative ideas.\nPracticality: Passing the generated ideas through a goal-task planner ensures that the plans are innovative but also feasible and executable.\nContinuous Learning: The LLM can learn from the accurate plans, improving its performance over time.\n\n\n\n\n\nComputational Overhead: There might be a computational overhead due to the two-step process.\nAccuracy of Feasibility Check: The feasibility check might not always be accurate.\n\n\n\n\nAn alternative approach could be to run the LLM and the goal-task planner in parallel to address the computational overhead.\n\n\n\nThis method may not be suitable for tasks that require immediate results due to the time taken by the two-step process.\n\n\n\nThe V-Sekai development team will implement this proposal.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nLLMs Can’t Plan, But Can Help Planning in LLM-Modulo Frameworks\n\nAI assistant Aria assisted with this feedback."
+    "text": "How to convert FBX and glTF2 to VRM?\n\n\n\nIf we can convert FBX and glTF to VRM we have a reliable way of importing things to groups.\n\n\n\nConvert avatar-asset-pipeline to use the membrane framework.\nHave the concept of a source glb we run again as many individual solvers for the input data.\nOnce the input is solved and it passes QA, that is one that is the outputted.\n\n\n\n\nWe have a standard way of importing characters.\nWe already have elixir backend infrastructure.\n\n\n\n\n\nHave no humans in the loop can be bad for quality assurance.\n\n\n\n\n\nOption:\nhttps://github.com/infosia/avatar-asset-pipeline\nRejection Reason:\nNeed to integrate with backend.\n\n\n\n\nNon trivial.\n\n\n\nThis is a core part of Groups and we depend on it.\n\n\n\n\nhttps://github.com/infosia/avatar-asset-pipeline\nhttps://github.com/fire/flow-avatar-asset-pipeline\nhttps://membraneframework.org/\nhttps://github.com/membraneframework/membrane_dashboard\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240326-verifying-and-finetuning-plans.html#context",
-    "href": "decisions/20240326-verifying-and-finetuning-plans.html#context",
-    "title": "Proposed: Teaching Large Language Models (LLMs) with Goal-Task Planners",
+    "objectID": "decisions/20210612-flow-avatar-asset-pipeline.html#context-and-problem-statement",
+    "href": "decisions/20210612-flow-avatar-asset-pipeline.html#context-and-problem-statement",
+    "title": "Proposed: Convert FBX and glTF2 to VRM via flow-avatar-asset-pipeline",
     "section": "",
-    "text": "We’re looking at using LLMs and goal-task planners like pyhop to generate innovative, executable plans. This approach combines the creativity of LLMs with the structured planning processes of goal-task planners."
+    "text": "How to convert FBX and glTF2 to VRM?"
   },
   {
-    "objectID": "decisions/20240326-verifying-and-finetuning-plans.html#problem-statement",
-    "href": "decisions/20240326-verifying-and-finetuning-plans.html#problem-statement",
-    "title": "Proposed: Teaching Large Language Models (LLMs) with Goal-Task Planners",
+    "objectID": "decisions/20210612-flow-avatar-asset-pipeline.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20210612-flow-avatar-asset-pipeline.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: Convert FBX and glTF2 to VRM via flow-avatar-asset-pipeline",
     "section": "",
-    "text": "The main challenges are computational overhead due to the two-step process and potential inaccuracies in the feasibility check."
+    "text": "If we can convert FBX and glTF to VRM we have a reliable way of importing things to groups."
   },
   {
-    "objectID": "decisions/20240326-verifying-and-finetuning-plans.html#proposed-solution",
-    "href": "decisions/20240326-verifying-and-finetuning-plans.html#proposed-solution",
-    "title": "Proposed: Teaching Large Language Models (LLMs) with Goal-Task Planners",
+    "objectID": "decisions/20210612-flow-avatar-asset-pipeline.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20210612-flow-avatar-asset-pipeline.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Convert FBX and glTF2 to VRM via flow-avatar-asset-pipeline",
     "section": "",
-    "text": "We propose using an LLM for idea generation and a goal-task planner for checking feasibility. This could lead to creative and feasible plans. The accurate plans generated by this model can then be used to further train the LLM.\n# Pseudo-code\ngpt = GPT()\nidea = gpt.generate_idea()\n\npyhop = Pyhop()\nfeasible = pyhop.find_plan(state, goal_generator())\n\nif feasible:\n    gpt.train(idea)"
+    "text": "Convert avatar-asset-pipeline to use the membrane framework.\nHave the concept of a source glb we run again as many individual solvers for the input data.\nOnce the input is solved and it passes QA, that is one that is the outputted."
   },
   {
-    "objectID": "decisions/20240326-verifying-and-finetuning-plans.html#benefits",
-    "href": "decisions/20240326-verifying-and-finetuning-plans.html#benefits",
-    "title": "Proposed: Teaching Large Language Models (LLMs) with Goal-Task Planners",
+    "objectID": "decisions/20210612-flow-avatar-asset-pipeline.html#positive-consequences",
+    "href": "decisions/20210612-flow-avatar-asset-pipeline.html#positive-consequences",
+    "title": "Proposed: Convert FBX and glTF2 to VRM via flow-avatar-asset-pipeline",
     "section": "",
-    "text": "Innovation: Using LLMs for idea generation can lead to creative ideas.\nPracticality: Passing the generated ideas through a goal-task planner ensures that the plans are innovative but also feasible and executable.\nContinuous Learning: The LLM can learn from the accurate plans, improving its performance over time."
+    "text": "We have a standard way of importing characters.\nWe already have elixir backend infrastructure."
   },
   {
-    "objectID": "decisions/20240326-verifying-and-finetuning-plans.html#downsides",
-    "href": "decisions/20240326-verifying-and-finetuning-plans.html#downsides",
-    "title": "Proposed: Teaching Large Language Models (LLMs) with Goal-Task Planners",
+    "objectID": "decisions/20210612-flow-avatar-asset-pipeline.html#negative-consequences",
+    "href": "decisions/20210612-flow-avatar-asset-pipeline.html#negative-consequences",
+    "title": "Proposed: Convert FBX and glTF2 to VRM via flow-avatar-asset-pipeline",
     "section": "",
-    "text": "Computational Overhead: There might be a computational overhead due to the two-step process.\nAccuracy of Feasibility Check: The feasibility check might not always be accurate."
+    "text": "Have no humans in the loop can be bad for quality assurance."
   },
   {
-    "objectID": "decisions/20240326-verifying-and-finetuning-plans.html#road-not-taken",
-    "href": "decisions/20240326-verifying-and-finetuning-plans.html#road-not-taken",
-    "title": "Proposed: Teaching Large Language Models (LLMs) with Goal-Task Planners",
+    "objectID": "decisions/20210612-flow-avatar-asset-pipeline.html#option-graveyard",
+    "href": "decisions/20210612-flow-avatar-asset-pipeline.html#option-graveyard",
+    "title": "Proposed: Convert FBX and glTF2 to VRM via flow-avatar-asset-pipeline",
     "section": "",
-    "text": "An alternative approach could be to run the LLM and the goal-task planner in parallel to address the computational overhead."
+    "text": "Option:\nhttps://github.com/infosia/avatar-asset-pipeline\nRejection Reason:\nNeed to integrate with backend."
   },
   {
-    "objectID": "decisions/20240326-verifying-and-finetuning-plans.html#infrequent-use-case",
-    "href": "decisions/20240326-verifying-and-finetuning-plans.html#infrequent-use-case",
-    "title": "Proposed: Teaching Large Language Models (LLMs) with Goal-Task Planners",
+    "objectID": "decisions/20210612-flow-avatar-asset-pipeline.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20210612-flow-avatar-asset-pipeline.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Convert FBX and glTF2 to VRM via flow-avatar-asset-pipeline",
     "section": "",
-    "text": "This method may not be suitable for tasks that require immediate results due to the time taken by the two-step process."
+    "text": "Non trivial."
   },
   {
-    "objectID": "decisions/20240326-verifying-and-finetuning-plans.html#in-core-and-done-by-us",
-    "href": "decisions/20240326-verifying-and-finetuning-plans.html#in-core-and-done-by-us",
-    "title": "Proposed: Teaching Large Language Models (LLMs) with Goal-Task Planners",
+    "objectID": "decisions/20210612-flow-avatar-asset-pipeline.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20210612-flow-avatar-asset-pipeline.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Convert FBX and glTF2 to VRM via flow-avatar-asset-pipeline",
     "section": "",
-    "text": "The V-Sekai development team will implement this proposal."
+    "text": "This is a core part of Groups and we depend on it."
   },
   {
-    "objectID": "decisions/20240326-verifying-and-finetuning-plans.html#status",
-    "href": "decisions/20240326-verifying-and-finetuning-plans.html#status",
-    "title": "Proposed: Teaching Large Language Models (LLMs) with Goal-Task Planners",
+    "objectID": "decisions/20210612-flow-avatar-asset-pipeline.html#references",
+    "href": "decisions/20210612-flow-avatar-asset-pipeline.html#references",
+    "title": "Proposed: Convert FBX and glTF2 to VRM via flow-avatar-asset-pipeline",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "https://github.com/infosia/avatar-asset-pipeline\nhttps://github.com/fire/flow-avatar-asset-pipeline\nhttps://membraneframework.org/\nhttps://github.com/membraneframework/membrane_dashboard"
   },
   {
-    "objectID": "decisions/20240326-verifying-and-finetuning-plans.html#decision-makers",
-    "href": "decisions/20240326-verifying-and-finetuning-plans.html#decision-makers",
-    "title": "Proposed: Teaching Large Language Models (LLMs) with Goal-Task Planners",
+    "objectID": "decisions/20210612-flow-avatar-asset-pipeline.html#derivative-license",
+    "href": "decisions/20210612-flow-avatar-asset-pipeline.html#derivative-license",
+    "title": "Proposed: Convert FBX and glTF2 to VRM via flow-avatar-asset-pipeline",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240326-verifying-and-finetuning-plans.html#tags",
-    "href": "decisions/20240326-verifying-and-finetuning-plans.html#tags",
-    "title": "Proposed: Teaching Large Language Models (LLMs) with Goal-Task Planners",
+    "objectID": "decisions/20221203-block-direct-pushes-to-main.html",
+    "href": "decisions/20221203-block-direct-pushes-to-main.html",
+    "title": "Rejected: Blocking direct push to MAIN to avoid build breakage",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Status: rejected \nDeciders: V-Sekai,fire,lyuma,\nTags: V-Sekai,\n\n\n\nDirect push to main cause build breakage.\nNote: This has been rejected by Lyuma.\n\n\n\nWe block direct pushes to the main and use pull requests and merges.\n\n\n\nUse the GitHub workflow with pull requests.\n\n\n\nWe don’t have to wait 2 hours to see if our changes break the build.\n\n\n\nThere are consequences of increased developer merging friction.\n\n\n\n\nOption: The status quo. \nRejection Reason: We keep breaking the build. \n\n\n\n\nThis is a dev ops change.\n\n\n\nWe own the GitHub repositories.\n\n\n\n\nV-Sekai\nPending head\nGodot Pull request\n\n\n\n\nCopyright (c) 2022 K. S. Ernest (iFire) Lee\nCopyright (c) 2022 V-Sekai contributors\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240326-verifying-and-finetuning-plans.html#further-reading",
-    "href": "decisions/20240326-verifying-and-finetuning-plans.html#further-reading",
-    "title": "Proposed: Teaching Large Language Models (LLMs) with Goal-Task Planners",
+    "objectID": "decisions/20221203-block-direct-pushes-to-main.html#context-and-problem-statement",
+    "href": "decisions/20221203-block-direct-pushes-to-main.html#context-and-problem-statement",
+    "title": "Rejected: Blocking direct push to MAIN to avoid build breakage",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nLLMs Can’t Plan, But Can Help Planning in LLM-Modulo Frameworks\n\nAI assistant Aria assisted with this feedback."
+    "text": "Direct push to main cause build breakage.\nNote: This has been rejected by Lyuma."
   },
   {
-    "objectID": "decisions/20241016-instantiating-v-sekai-content.html",
-    "href": "decisions/20241016-instantiating-v-sekai-content.html",
-    "title": "Proposed: Evaluate three proposals for V-Sekai content distribution",
+    "objectID": "decisions/20221203-block-direct-pushes-to-main.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20221203-block-direct-pushes-to-main.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Rejected: Blocking direct push to MAIN to avoid build breakage",
     "section": "",
-    "text": "Address security concerns with V-Sekai content distribution like including the sandbox API surface, file size management, resource loading, and packed scene instantiation.\n\n\n\nWe aim to safely initialize an avatar body from the V-Sekai content distribution network into the virtual world without compromising security or performance.\nWe wish to enable Godot to load older content seamlessly.\nWe want to avoid animations causing security issues.\n\n\n\n\n\nThis method involves loading chunks of an average packed scene from the web, instantiating it in the sandbox, and applying runtime verification. This approach prevents double initializer security concerns and avoids using double the memory to copy PackedScene.\n\n\nDifferent content initializers becomes a security problem as code drifts and fixes are lost.\n\n\n\n\nFor this option, we would stream an average glTF file from the web and develop a loader for glTF within the Godot sandbox equipped with a set of verifiers.\nWe must create custom VSEKAI or GODOT extensions for each unspecified resource and node type, though simple schemas could be autogenerated from classes.\n\n\n\nCreating a JSON schema for arbitrary Godot-packed scene resources that have been converted to JSON is a complex task. This option might be more challenging than adapting glTF for sandbox C++.\n\n\n\n\nA significant benefit of these approaches is the ability to enforce specific requirements, such as using PCVR and mobile image textures through formats like Basis Universal, BPTC, and ASTC during upload and download. By controlling the instantiation process, we can also prevent loading when, for example, an avatar exceeds a polycount of 70,000 triangles. We can size worlds according to predefined constraints, with various optimization settings available.\n\n\n\nThe primary downside is the complexity of these security measures and their potential performance impact. Each option requires substantial development effort and may introduce latency or processing overhead. Furthermore, maintaining these systems as Godot evolves could increase long-term maintenance costs.\n\n\n\nWe could have explored simpler, less secure methods of content distribution that rely more heavily on post-load validation rather than stringent pre-load checks.\n\n\n\nThese methods are designed to handle extremely large or complex scenes that might exceed the proposed limits and infrequent resource types not covered by standard validators.\n\n\n\nWe will maintain the core functionality of the sandbox and basic loaders, ensuring that critical updates or security patches can be applied swiftly and uniformly.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\nFire\nLyuma\nfwsgonzo\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - This GitHub page hosts the V-Sekai open-source project, which integrates social VR/VRSNS/metaverse components into the Godot Engine."
+    "text": "We block direct pushes to the main and use pull requests and merges."
   },
   {
-    "objectID": "decisions/20241016-instantiating-v-sekai-content.html#the-context",
-    "href": "decisions/20241016-instantiating-v-sekai-content.html#the-context",
-    "title": "Proposed: Evaluate three proposals for V-Sekai content distribution",
+    "objectID": "decisions/20221203-block-direct-pushes-to-main.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20221203-block-direct-pushes-to-main.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Rejected: Blocking direct push to MAIN to avoid build breakage",
     "section": "",
-    "text": "Address security concerns with V-Sekai content distribution like including the sandbox API surface, file size management, resource loading, and packed scene instantiation."
+    "text": "Use the GitHub workflow with pull requests."
   },
   {
-    "objectID": "decisions/20241016-instantiating-v-sekai-content.html#the-problem-statement",
-    "href": "decisions/20241016-instantiating-v-sekai-content.html#the-problem-statement",
-    "title": "Proposed: Evaluate three proposals for V-Sekai content distribution",
+    "objectID": "decisions/20221203-block-direct-pushes-to-main.html#positive-consequences",
+    "href": "decisions/20221203-block-direct-pushes-to-main.html#positive-consequences",
+    "title": "Rejected: Blocking direct push to MAIN to avoid build breakage",
     "section": "",
-    "text": "We aim to safely initialize an avatar body from the V-Sekai content distribution network into the virtual world without compromising security or performance.\nWe wish to enable Godot to load older content seamlessly.\nWe want to avoid animations causing security issues."
+    "text": "We don’t have to wait 2 hours to see if our changes break the build."
   },
   {
-    "objectID": "decisions/20241016-instantiating-v-sekai-content.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20241016-instantiating-v-sekai-content.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Evaluate three proposals for V-Sekai content distribution",
+    "objectID": "decisions/20221203-block-direct-pushes-to-main.html#negative-consequences",
+    "href": "decisions/20221203-block-direct-pushes-to-main.html#negative-consequences",
+    "title": "Rejected: Blocking direct push to MAIN to avoid build breakage",
     "section": "",
-    "text": "This method involves loading chunks of an average packed scene from the web, instantiating it in the sandbox, and applying runtime verification. This approach prevents double initializer security concerns and avoids using double the memory to copy PackedScene.\n\n\nDifferent content initializers becomes a security problem as code drifts and fixes are lost.\n\n\n\n\nFor this option, we would stream an average glTF file from the web and develop a loader for glTF within the Godot sandbox equipped with a set of verifiers.\nWe must create custom VSEKAI or GODOT extensions for each unspecified resource and node type, though simple schemas could be autogenerated from classes.\n\n\n\nCreating a JSON schema for arbitrary Godot-packed scene resources that have been converted to JSON is a complex task. This option might be more challenging than adapting glTF for sandbox C++."
+    "text": "There are consequences of increased developer merging friction."
   },
   {
-    "objectID": "decisions/20241016-instantiating-v-sekai-content.html#the-benefits",
-    "href": "decisions/20241016-instantiating-v-sekai-content.html#the-benefits",
-    "title": "Proposed: Evaluate three proposals for V-Sekai content distribution",
+    "objectID": "decisions/20221203-block-direct-pushes-to-main.html#option-graveyard",
+    "href": "decisions/20221203-block-direct-pushes-to-main.html#option-graveyard",
+    "title": "Rejected: Blocking direct push to MAIN to avoid build breakage",
     "section": "",
-    "text": "A significant benefit of these approaches is the ability to enforce specific requirements, such as using PCVR and mobile image textures through formats like Basis Universal, BPTC, and ASTC during upload and download. By controlling the instantiation process, we can also prevent loading when, for example, an avatar exceeds a polycount of 70,000 triangles. We can size worlds according to predefined constraints, with various optimization settings available."
+    "text": "Option: The status quo. \nRejection Reason: We keep breaking the build."
   },
   {
-    "objectID": "decisions/20241016-instantiating-v-sekai-content.html#the-downsides",
-    "href": "decisions/20241016-instantiating-v-sekai-content.html#the-downsides",
-    "title": "Proposed: Evaluate three proposals for V-Sekai content distribution",
+    "objectID": "decisions/20221203-block-direct-pushes-to-main.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20221203-block-direct-pushes-to-main.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Rejected: Blocking direct push to MAIN to avoid build breakage",
     "section": "",
-    "text": "The primary downside is the complexity of these security measures and their potential performance impact. Each option requires substantial development effort and may introduce latency or processing overhead. Furthermore, maintaining these systems as Godot evolves could increase long-term maintenance costs."
+    "text": "This is a dev ops change."
   },
   {
-    "objectID": "decisions/20241016-instantiating-v-sekai-content.html#the-road-not-taken",
-    "href": "decisions/20241016-instantiating-v-sekai-content.html#the-road-not-taken",
-    "title": "Proposed: Evaluate three proposals for V-Sekai content distribution",
+    "objectID": "decisions/20221203-block-direct-pushes-to-main.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20221203-block-direct-pushes-to-main.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Rejected: Blocking direct push to MAIN to avoid build breakage",
     "section": "",
-    "text": "We could have explored simpler, less secure methods of content distribution that rely more heavily on post-load validation rather than stringent pre-load checks."
+    "text": "We own the GitHub repositories."
   },
   {
-    "objectID": "decisions/20241016-instantiating-v-sekai-content.html#the-infrequent-use-case",
-    "href": "decisions/20241016-instantiating-v-sekai-content.html#the-infrequent-use-case",
-    "title": "Proposed: Evaluate three proposals for V-Sekai content distribution",
+    "objectID": "decisions/20221203-block-direct-pushes-to-main.html#references",
+    "href": "decisions/20221203-block-direct-pushes-to-main.html#references",
+    "title": "Rejected: Blocking direct push to MAIN to avoid build breakage",
     "section": "",
-    "text": "These methods are designed to handle extremely large or complex scenes that might exceed the proposed limits and infrequent resource types not covered by standard validators."
+    "text": "V-Sekai\nPending head\nGodot Pull request"
   },
   {
-    "objectID": "decisions/20241016-instantiating-v-sekai-content.html#in-core-and-done-by-us",
-    "href": "decisions/20241016-instantiating-v-sekai-content.html#in-core-and-done-by-us",
-    "title": "Proposed: Evaluate three proposals for V-Sekai content distribution",
+    "objectID": "decisions/20221203-block-direct-pushes-to-main.html#license-of-the-contribution",
+    "href": "decisions/20221203-block-direct-pushes-to-main.html#license-of-the-contribution",
+    "title": "Rejected: Blocking direct push to MAIN to avoid build breakage",
     "section": "",
-    "text": "We will maintain the core functionality of the sandbox and basic loaders, ensuring that critical updates or security patches can be applied swiftly and uniformly."
+    "text": "Copyright (c) 2022 K. S. Ernest (iFire) Lee\nCopyright (c) 2022 V-Sekai contributors\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20241016-instantiating-v-sekai-content.html#status",
-    "href": "decisions/20241016-instantiating-v-sekai-content.html#status",
-    "title": "Proposed: Evaluate three proposals for V-Sekai content distribution",
+    "objectID": "decisions/20220130-optimize-cicd.html",
+    "href": "decisions/20220130-optimize-cicd.html",
+    "title": "Proposal: Optimize cicd for costs because it’s limited",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "Status: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nCICD isn’t optimized.\n\n\n\nDo not upload the template .tpz.\n\n\n\n\nGo to gocd cicd.\nRemove .tpz package workflow.\nMove each output to a separate release.\nDo not duplicate editor and game builds if they’re the same.\nPublish a web build with editor if built.\n\n\n\n\n\nReduce the costs of upload\n\n\n\n\n\nChange in a stable system is disruptive.\n\n\n\n\n\nOption: Do nothing.\nRejection Reason: Expensive.\n\n\n\n\nNot a code but devops.\n\n\n\nWe are running the cicd service.\n\n\n\n\nGOCD\n\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20241016-instantiating-v-sekai-content.html#decision-makers",
-    "href": "decisions/20241016-instantiating-v-sekai-content.html#decision-makers",
-    "title": "Proposed: Evaluate three proposals for V-Sekai content distribution",
+    "objectID": "decisions/20220130-optimize-cicd.html#context-and-problem-statement",
+    "href": "decisions/20220130-optimize-cicd.html#context-and-problem-statement",
+    "title": "Proposal: Optimize cicd for costs because it’s limited",
     "section": "",
-    "text": "V-Sekai development team\nFire\nLyuma\nfwsgonzo"
+    "text": "CICD isn’t optimized."
   },
   {
-    "objectID": "decisions/20241016-instantiating-v-sekai-content.html#tags",
-    "href": "decisions/20241016-instantiating-v-sekai-content.html#tags",
-    "title": "Proposed: Evaluate three proposals for V-Sekai content distribution",
+    "objectID": "decisions/20220130-optimize-cicd.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20220130-optimize-cicd.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposal: Optimize cicd for costs because it’s limited",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Do not upload the template .tpz."
   },
   {
-    "objectID": "decisions/20241016-instantiating-v-sekai-content.html#further-reading",
-    "href": "decisions/20241016-instantiating-v-sekai-content.html#further-reading",
-    "title": "Proposed: Evaluate three proposals for V-Sekai content distribution",
+    "objectID": "decisions/20220130-optimize-cicd.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20220130-optimize-cicd.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposal: Optimize cicd for costs because it’s limited",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - This GitHub page hosts the V-Sekai open-source project, which integrates social VR/VRSNS/metaverse components into the Godot Engine."
+    "text": "Go to gocd cicd.\nRemove .tpz package workflow.\nMove each output to a separate release.\nDo not duplicate editor and game builds if they’re the same.\nPublish a web build with editor if built."
   },
   {
-    "objectID": "decisions/20240511-wasm-cache-incident.html",
-    "href": "decisions/20240511-wasm-cache-incident.html",
-    "title": "Accepted: Wasm Cache Incident Report",
+    "objectID": "decisions/20220130-optimize-cicd.html#positive-consequences",
+    "href": "decisions/20220130-optimize-cicd.html#positive-consequences",
+    "title": "Proposal: Optimize cicd for costs because it’s limited",
     "section": "",
-    "text": "The issue arose while attempting to build the desync module for Godot Engine 4.3 on Github actions.\n\n\n\nThe following error was encountered even though the module is disabled from building and other code was identical to master:\nerror: undefined symbol: saveSetjmp (referenced by root reference (e.g. compiled C/C++ code))\nwarning: To disable errors for undefined symbols use `-sERROR_ON_UNDEFINED_SYMBOLS=0`\nwarning: _saveSetjmp may need to be added to EXPORTED_FUNCTIONS if it arrives from a system library\nerror: undefined symbol: testSetjmp (referenced by root reference (e.g. compiled C/C++ code))\nwarning: _testSetjmp may need to be added to EXPORTED_FUNCTIONS if it arrives from a system library\nError: Aborting compilation due to previous errors\nem++: error: '/home/runner/work/_temp/5ca5bc6c-db6b-4fae-a502-2fde903054ae/emsdk-main/node/16.20.0_64bit/bin/node /home/runner/work/_temp/5ca5bc6c-db6b-4fae-a502-2fde903054ae/emsdk-main/upstream/emscripten/src/compiler.mjs /tmp/tmpjyhtoot1.json' failed (returned 1)\nscons: *** [bin/godot.web.template_release.wasm32.js] Error 1\nscons: building terminated because of errors.\n\n\n\nThe proposed solution involves modifying the web build Github Actions and suffixing the branch name. The steps are as follows:\n\nModify the GODOT_BASE_BRANCH environment variable in the Github Actions workflow file:\n\nname: 🌐 Web Builds\non:\n  workflow_call:\n\n# Global Settings\nenv:\n  # Used for the cache key. Add version suffix to force clean build.\n  GODOT_BASE_BRANCH: master # Add a suffix here.\n\nCombine master with em version: master-em-3.1.59\nCommit the changes.\n\n\n\n\nThis solution will help in resolving the current build issue and ensure that the Godot Engine 4.3 desync module is built successfully.\n\n\n\nThe downside of this approach is that it requires manual intervention for each build process, which might not be feasible for continuous integration/continuous deployment (CI/CD) pipelines.\n\n\n\nAn alternative could be to investigate the root cause of the undefined symbols and fix them at the source code level.\n\n\n\nThis solution is specifically for the current build issue and may not apply to other build problems or modules.\n\n\n\nThis proposal is made by us and is intended to be implemented in the core build process of the Godot Engine.\n\n\n\nStatus: Accepted\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - The GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis proposal was assisted by Aria, an AI assistant."
+    "text": "Reduce the costs of upload"
   },
   {
-    "objectID": "decisions/20240511-wasm-cache-incident.html#context",
-    "href": "decisions/20240511-wasm-cache-incident.html#context",
-    "title": "Accepted: Wasm Cache Incident Report",
+    "objectID": "decisions/20220130-optimize-cicd.html#negative-consequences",
+    "href": "decisions/20220130-optimize-cicd.html#negative-consequences",
+    "title": "Proposal: Optimize cicd for costs because it’s limited",
     "section": "",
-    "text": "The issue arose while attempting to build the desync module for Godot Engine 4.3 on Github actions."
+    "text": "Change in a stable system is disruptive."
   },
   {
-    "objectID": "decisions/20240511-wasm-cache-incident.html#problem-statement",
-    "href": "decisions/20240511-wasm-cache-incident.html#problem-statement",
-    "title": "Accepted: Wasm Cache Incident Report",
+    "objectID": "decisions/20220130-optimize-cicd.html#option-graveyard",
+    "href": "decisions/20220130-optimize-cicd.html#option-graveyard",
+    "title": "Proposal: Optimize cicd for costs because it’s limited",
     "section": "",
-    "text": "The following error was encountered even though the module is disabled from building and other code was identical to master:\nerror: undefined symbol: saveSetjmp (referenced by root reference (e.g. compiled C/C++ code))\nwarning: To disable errors for undefined symbols use `-sERROR_ON_UNDEFINED_SYMBOLS=0`\nwarning: _saveSetjmp may need to be added to EXPORTED_FUNCTIONS if it arrives from a system library\nerror: undefined symbol: testSetjmp (referenced by root reference (e.g. compiled C/C++ code))\nwarning: _testSetjmp may need to be added to EXPORTED_FUNCTIONS if it arrives from a system library\nError: Aborting compilation due to previous errors\nem++: error: '/home/runner/work/_temp/5ca5bc6c-db6b-4fae-a502-2fde903054ae/emsdk-main/node/16.20.0_64bit/bin/node /home/runner/work/_temp/5ca5bc6c-db6b-4fae-a502-2fde903054ae/emsdk-main/upstream/emscripten/src/compiler.mjs /tmp/tmpjyhtoot1.json' failed (returned 1)\nscons: *** [bin/godot.web.template_release.wasm32.js] Error 1\nscons: building terminated because of errors."
+    "text": "Option: Do nothing.\nRejection Reason: Expensive."
   },
   {
-    "objectID": "decisions/20240511-wasm-cache-incident.html#proposed-solution",
-    "href": "decisions/20240511-wasm-cache-incident.html#proposed-solution",
-    "title": "Accepted: Wasm Cache Incident Report",
+    "objectID": "decisions/20220130-optimize-cicd.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20220130-optimize-cicd.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposal: Optimize cicd for costs because it’s limited",
     "section": "",
-    "text": "The proposed solution involves modifying the web build Github Actions and suffixing the branch name. The steps are as follows:\n\nModify the GODOT_BASE_BRANCH environment variable in the Github Actions workflow file:\n\nname: 🌐 Web Builds\non:\n  workflow_call:\n\n# Global Settings\nenv:\n  # Used for the cache key. Add version suffix to force clean build.\n  GODOT_BASE_BRANCH: master # Add a suffix here.\n\nCombine master with em version: master-em-3.1.59\nCommit the changes."
+    "text": "Not a code but devops."
   },
   {
-    "objectID": "decisions/20240511-wasm-cache-incident.html#benefits",
-    "href": "decisions/20240511-wasm-cache-incident.html#benefits",
-    "title": "Accepted: Wasm Cache Incident Report",
+    "objectID": "decisions/20220130-optimize-cicd.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20220130-optimize-cicd.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposal: Optimize cicd for costs because it’s limited",
     "section": "",
-    "text": "This solution will help in resolving the current build issue and ensure that the Godot Engine 4.3 desync module is built successfully."
+    "text": "We are running the cicd service."
   },
   {
-    "objectID": "decisions/20240511-wasm-cache-incident.html#downsides",
-    "href": "decisions/20240511-wasm-cache-incident.html#downsides",
-    "title": "Accepted: Wasm Cache Incident Report",
+    "objectID": "decisions/20220130-optimize-cicd.html#references",
+    "href": "decisions/20220130-optimize-cicd.html#references",
+    "title": "Proposal: Optimize cicd for costs because it’s limited",
     "section": "",
-    "text": "The downside of this approach is that it requires manual intervention for each build process, which might not be feasible for continuous integration/continuous deployment (CI/CD) pipelines."
+    "text": "GOCD"
   },
   {
-    "objectID": "decisions/20240511-wasm-cache-incident.html#alternatives-considered",
-    "href": "decisions/20240511-wasm-cache-incident.html#alternatives-considered",
-    "title": "Accepted: Wasm Cache Incident Report",
+    "objectID": "decisions/20220130-optimize-cicd.html#derivative-license",
+    "href": "decisions/20220130-optimize-cicd.html#derivative-license",
+    "title": "Proposal: Optimize cicd for costs because it’s limited",
     "section": "",
-    "text": "An alternative could be to investigate the root cause of the undefined symbols and fix them at the source code level."
+    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240511-wasm-cache-incident.html#infrequent-use-case",
-    "href": "decisions/20240511-wasm-cache-incident.html#infrequent-use-case",
-    "title": "Accepted: Wasm Cache Incident Report",
+    "objectID": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html",
+    "href": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html",
+    "title": "Rejected: File or attestation for virtual worlds using ssh signatures",
     "section": "",
-    "text": "This solution is specifically for the current build issue and may not apply to other build problems or modules."
+    "text": "Status: rejected \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nFile or attestation for virtual worlds\n\n\n\nUse ssh signatures.\n\n\n\nAn analogy of a CD and a CD case with stickers.\n\n\nRead your public key.\n$ ssh-add -L &gt; me.pub # Can be related to a X.509 `.crt`\nCreate a file.\n$ touch avatar-sample.vrm\nSign your file.\nssh-keygen -Y sign -f &lt;(ssh-add -L) -n \"avatar@v-sekai.org\" &lt; avatar-sample.vrm &gt;&gt; avatar-sample.vrm.avatar%40V-sekai.com.sig\nssh-keygen -Y sign -f &lt;(ssh-add -L) -n \"me@v-sekai.org\" &lt; avatar-sample.vrm &gt;&gt; avatar-sample.vrm.me%40V-sekai.com.sig\nWrite signature to avatar-sample.vrm.sig # Can be attested by multiple people with multiple .sig.\necho -n ernest.lee@chibifire.com | cat - &lt;(echo -n \" \") | cat - &lt;(ssh-add -L) &gt; allowed_signers # Can have more than o\nne line.\nThe allowed_signers file associates a string that represents a person (Principle) to a Public Key.\nssh-keygen -Y verify -f allowed_signers -I ernest.lee@chibifire.com -n \"avatar@v-sekai.org\" -s avatar-sample.vrm.avatar%40V-sekai.com.sig &lt; avatar-sample.vrm\nssh-keygen -Y verify -f allowed_signers -I ernest.lee@chibifire.com -n \"me@v-sekai.org\" -s  avatar-sample.vrm.me%40V-sekai.com.sig &lt; avatar-sample.vrm\nReferenced https://www.agwa.name/blog/post/ssh_signatures\n\n\n\n# ssh-add ~/.ssh/id_ed25519\n# or smartcard\n# TODO: How do you change authorization of the delegation?\nssh-keygen -Us &lt;(ssh-add -L) -I fire@example.com -n avatar@V-Sekai.com -V +1h KEYFILE.pub\n\n\n\n# Resulting file is namespace.allowed_signers but uri_encoded.\ncurl https://github.com/fire.keys &gt; avatars%40V-Sekai.com.allowed_signers # Needs a id in email syntax in front of a key\ncurl files://uro &gt; avatars%40V-sekai.com.allowed_signers # Assumed in correct format\ncurl http://matrix-homeserver.example.com/fire &gt; avatars%40V-sekai.com.allowed_signers # Assumed in correct format\n\n\n\n\n\nAble to distribute a game launcher.\nAble to add a makers mark to items.\nUse for verifying binaries\nUse for verifying game modifications\nUsed for lobby servers to prove to the player that they are official.\nDouble sided friending\n\n\n\n\n\nNo data encryption\n\n\n\n\n\nOption: Matrix\nRejection Reason: Technically complicated to devops start and multiple layers compared to an offline approach.\nOption: Ipfs and Etherium\nRejection Reason: Requires a globally distributed database.\nOption: Sigstore https://www.sigstore.dev/\nRejection Reason: Why aren’t we using sigstore?\n\n\n\n\nNot able to use a few lines of code.\n\n\n\nWe have to define the trust.\n\n\n\n\nhttps://github.com/V-Sekai/\nhttps://github.com/sigstore/rekor/tree/main/pkg/pki/ssh\nhttps://stackoverflow.com/questions/4629537/how-to-encrypt-data-in-php-using-public-private-keys\nhttps://stackoverflow.com/questions/60160082/how-to-achieve-openssl-smime-encrypt-with-public-key-functionality-in-code\nhttps://github.com/cloudtools/ssh-cert-authority\nhttps://github.com/je9000/ssh-smime\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240511-wasm-cache-incident.html#in-core-and-done-by-us",
-    "href": "decisions/20240511-wasm-cache-incident.html#in-core-and-done-by-us",
-    "title": "Accepted: Wasm Cache Incident Report",
+    "objectID": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html#context-and-problem-statement",
+    "href": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html#context-and-problem-statement",
+    "title": "Rejected: File or attestation for virtual worlds using ssh signatures",
     "section": "",
-    "text": "This proposal is made by us and is intended to be implemented in the core build process of the Godot Engine."
+    "text": "File or attestation for virtual worlds"
   },
   {
-    "objectID": "decisions/20240511-wasm-cache-incident.html#status",
-    "href": "decisions/20240511-wasm-cache-incident.html#status",
-    "title": "Accepted: Wasm Cache Incident Report",
+    "objectID": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Rejected: File or attestation for virtual worlds using ssh signatures",
     "section": "",
-    "text": "Status: Accepted"
+    "text": "Use ssh signatures."
   },
   {
-    "objectID": "decisions/20240511-wasm-cache-incident.html#decision-makers",
-    "href": "decisions/20240511-wasm-cache-incident.html#decision-makers",
-    "title": "Accepted: Wasm Cache Incident Report",
+    "objectID": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Rejected: File or attestation for virtual worlds using ssh signatures",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "An analogy of a CD and a CD case with stickers.\n\n\nRead your public key.\n$ ssh-add -L &gt; me.pub # Can be related to a X.509 `.crt`\nCreate a file.\n$ touch avatar-sample.vrm\nSign your file.\nssh-keygen -Y sign -f &lt;(ssh-add -L) -n \"avatar@v-sekai.org\" &lt; avatar-sample.vrm &gt;&gt; avatar-sample.vrm.avatar%40V-sekai.com.sig\nssh-keygen -Y sign -f &lt;(ssh-add -L) -n \"me@v-sekai.org\" &lt; avatar-sample.vrm &gt;&gt; avatar-sample.vrm.me%40V-sekai.com.sig\nWrite signature to avatar-sample.vrm.sig # Can be attested by multiple people with multiple .sig.\necho -n ernest.lee@chibifire.com | cat - &lt;(echo -n \" \") | cat - &lt;(ssh-add -L) &gt; allowed_signers # Can have more than o\nne line.\nThe allowed_signers file associates a string that represents a person (Principle) to a Public Key.\nssh-keygen -Y verify -f allowed_signers -I ernest.lee@chibifire.com -n \"avatar@v-sekai.org\" -s avatar-sample.vrm.avatar%40V-sekai.com.sig &lt; avatar-sample.vrm\nssh-keygen -Y verify -f allowed_signers -I ernest.lee@chibifire.com -n \"me@v-sekai.org\" -s  avatar-sample.vrm.me%40V-sekai.com.sig &lt; avatar-sample.vrm\nReferenced https://www.agwa.name/blog/post/ssh_signatures\n\n\n\n# ssh-add ~/.ssh/id_ed25519\n# or smartcard\n# TODO: How do you change authorization of the delegation?\nssh-keygen -Us &lt;(ssh-add -L) -I fire@example.com -n avatar@V-Sekai.com -V +1h KEYFILE.pub\n\n\n\n# Resulting file is namespace.allowed_signers but uri_encoded.\ncurl https://github.com/fire.keys &gt; avatars%40V-Sekai.com.allowed_signers # Needs a id in email syntax in front of a key\ncurl files://uro &gt; avatars%40V-sekai.com.allowed_signers # Assumed in correct format\ncurl http://matrix-homeserver.example.com/fire &gt; avatars%40V-sekai.com.allowed_signers # Assumed in correct format"
   },
   {
-    "objectID": "decisions/20240511-wasm-cache-incident.html#tags",
-    "href": "decisions/20240511-wasm-cache-incident.html#tags",
-    "title": "Accepted: Wasm Cache Incident Report",
+    "objectID": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html#positive-consequences",
+    "href": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html#positive-consequences",
+    "title": "Rejected: File or attestation for virtual worlds using ssh signatures",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Able to distribute a game launcher.\nAble to add a makers mark to items.\nUse for verifying binaries\nUse for verifying game modifications\nUsed for lobby servers to prove to the player that they are official.\nDouble sided friending"
   },
   {
-    "objectID": "decisions/20240511-wasm-cache-incident.html#further-reading",
-    "href": "decisions/20240511-wasm-cache-incident.html#further-reading",
-    "title": "Accepted: Wasm Cache Incident Report",
+    "objectID": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html#negative-consequences",
+    "href": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html#negative-consequences",
+    "title": "Rejected: File or attestation for virtual worlds using ssh signatures",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - The GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis proposal was assisted by Aria, an AI assistant."
+    "text": "No data encryption"
   },
   {
-    "objectID": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html",
-    "href": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html",
-    "title": "Proposed: FFMPEG Wave/Mic and Speaker/Play",
+    "objectID": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html#option-graveyard",
+    "href": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html#option-graveyard",
+    "title": "Rejected: File or attestation for virtual worlds using ssh signatures",
     "section": "",
-    "text": "Testing audio input and output for VOIP applications.\n\n\n\nSimulate microphone input and capture speaker output to debug and test audio functionality.\n\n\n\nThe following script uses ffmpeg to either generate a test tone or play a provided WAV file as microphone input and record the speaker output. This setup is designed to work on macOS, Windows, and Linux.\n\n\n#!/bin/bash\n\n# Define file paths and device IDs\nINPUT_WAV=\"\"  # Path to an optional input WAV file\nOUTPUT_WAV=\"/path/to/output/speaker_output.wav\"\nMIC_DEVICE=\"plughw:0,0\"      # Replace with your actual mic device ID\nSPEAKER_DEVICE=\"plughw:0,0\"  # Replace with your actual speaker device ID\nDURATION=10                   # Duration in seconds\n\nif [ -z \"$INPUT_WAV\" ]; then\n    # Generate a test tone and play it as microphone input using ffmpeg\n    ffmpeg -f lavfi -i \"sine=frequency=1000:duration=$DURATION\" -f alsa -ac 2 -ar 44100 hw:$MIC_DEVICE &\nelse\n    # Play the provided WAV file as microphone input using ffmpeg\n    ffmpeg -re -i $INPUT_WAV -f alsa -ac 2 -ar 44100 hw:$MIC_DEVICE &\nfi\n\n# Record the speaker output to a WAV file\nffmpeg -f alsa -i $SPEAKER_DEVICE -t $DURATION -ac 2 -ar 44100 $OUTPUT_WAV\n\n# Wait for background processes to finish\nwait\n\n\n\n@echo off\n\n:: Define file paths and device IDs\nset INPUT_WAV=  :: Path to an optional input WAV file\nset OUTPUT_WAV=C:\\path\\to\\output\\speaker_output.wav\nset MIC_DEVICE=audio=\"Microphone (Realtek High Definition Audio)\"  :: Replace with your actual mic device name\nset SPEAKER_DEVICE=audio=\"Speakers (Realtek High Definition Audio)\" :: Replace with your actual speaker device name\nset DURATION=10  :: Duration in seconds\n\nif \"%INPUT_WAV%\"==\"\" (\n    :: Generate a test tone and play it as microphone input using ffmpeg\n    start /B ffmpeg -f lavfi -i \"sine=frequency=1000:duration=%DURATION%\" -f dshow -i %MIC_DEVICE%\n) else (\n    :: Play the provided WAV file as microphone input using ffmpeg\n    start /B ffmpeg -re -i %INPUT_WAV% -f dshow -i %MIC_DEVICE%\n)\n\n:: Record the speaker output to a WAV file\nffmpeg -f dshow -i %SPEAKER_DEVICE% -t %DURATION% -ac 2 -ar 44100 %OUTPUT_WAV%\n\n:: Wait for background processes to finish\nwait\n\n\n\n\n\nTo list available audio devices on Windows, you can use the following command:\nffmpeg -list_devices true -f dshow -i dummy\nThis will output a list of all available audio devices, which you can then use to replace the MIC_DEVICE and SPEAKER_DEVICE placeholders in the batch script.\n\n\n\nOn macOS, you can list audio devices using the following command:\nffmpeg -f avfoundation -list_devices true -i \"\"\nThis command will display both video and audio devices. Look for the audio devices and use their indices or names as needed in your scripts.\n\n\n\nFor Linux, to list audio devices using ffmpeg, you can execute the following command:\nffmpeg -f alsa -list_devices true -i dummy\nThis command will help identify available ALSA audio devices, which can be used similarly to how devices are specified in scripts on other operating systems.\n\n\n\n\n\nDefine File Paths and Device IDs:\n\nINPUT_WAV: Path to an optional input WAV file.\nOUTPUT_WAV: Path where the recorded speaker output will be saved.\nMIC_DEVICE: Microphone device ID (replace with actual device ID).\nSPEAKER_DEVICE: Speaker device ID (replace with actual device ID).\nDURATION: Duration of the recording in seconds.\n\nGenerate a Test Tone or Play Provided WAV File as Microphone Input:\n\nIf INPUT_WAV is not provided, use ffmpeg to generate a 1000 Hz sine wave test tone and play it as if it were coming from the microphone.\nIf INPUT_WAV is provided, use ffmpeg to play the WAV file as if it were coming from the microphone.\n\nRecord the Speaker Output:\n\nUse ffmpeg to record the speaker output to a WAV file for the specified duration.\n\nWait for Background Processes:\n\nEnsure all background processes complete before the script exits.\n\n\n\n\n\n\n\nAutomated Testing: Enables automated testing of VOIP clients.\nVersatility: Can be used to test various VOIP applications like Discord and VRChat.\nPrototyping: Useful for prototyping WebRTC later.\n\n\n\n\n\nComplex Setup: Requires knowledge of audio systems and command-line tools.\nPotential Compatibility Issues: May not work seamlessly across all hardware configurations.\n\n\n\n\nUsing Godot-specific audio stream players and effects was considered but found to be too closely tied to Godot, limiting broader application testing.\n\n\n\nIn cases where precise audio sample rate configuration is critical, additional adjustments may be needed to avoid issues.\n\n\n\nThis approach aligns with our goal of robust and versatile testing methodologies and will be implemented by our team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "Option: Matrix\nRejection Reason: Technically complicated to devops start and multiple layers compared to an offline approach.\nOption: Ipfs and Etherium\nRejection Reason: Requires a globally distributed database.\nOption: Sigstore https://www.sigstore.dev/\nRejection Reason: Why aren’t we using sigstore?"
   },
   {
-    "objectID": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#the-context",
-    "href": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#the-context",
-    "title": "Proposed: FFMPEG Wave/Mic and Speaker/Play",
+    "objectID": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Rejected: File or attestation for virtual worlds using ssh signatures",
     "section": "",
-    "text": "Testing audio input and output for VOIP applications."
+    "text": "Not able to use a few lines of code."
   },
   {
-    "objectID": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#the-problem-statement",
-    "href": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#the-problem-statement",
-    "title": "Proposed: FFMPEG Wave/Mic and Speaker/Play",
+    "objectID": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Rejected: File or attestation for virtual worlds using ssh signatures",
     "section": "",
-    "text": "Simulate microphone input and capture speaker output to debug and test audio functionality."
+    "text": "We have to define the trust."
   },
   {
-    "objectID": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: FFMPEG Wave/Mic and Speaker/Play",
+    "objectID": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html#references",
+    "href": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html#references",
+    "title": "Rejected: File or attestation for virtual worlds using ssh signatures",
     "section": "",
-    "text": "The following script uses ffmpeg to either generate a test tone or play a provided WAV file as microphone input and record the speaker output. This setup is designed to work on macOS, Windows, and Linux.\n\n\n#!/bin/bash\n\n# Define file paths and device IDs\nINPUT_WAV=\"\"  # Path to an optional input WAV file\nOUTPUT_WAV=\"/path/to/output/speaker_output.wav\"\nMIC_DEVICE=\"plughw:0,0\"      # Replace with your actual mic device ID\nSPEAKER_DEVICE=\"plughw:0,0\"  # Replace with your actual speaker device ID\nDURATION=10                   # Duration in seconds\n\nif [ -z \"$INPUT_WAV\" ]; then\n    # Generate a test tone and play it as microphone input using ffmpeg\n    ffmpeg -f lavfi -i \"sine=frequency=1000:duration=$DURATION\" -f alsa -ac 2 -ar 44100 hw:$MIC_DEVICE &\nelse\n    # Play the provided WAV file as microphone input using ffmpeg\n    ffmpeg -re -i $INPUT_WAV -f alsa -ac 2 -ar 44100 hw:$MIC_DEVICE &\nfi\n\n# Record the speaker output to a WAV file\nffmpeg -f alsa -i $SPEAKER_DEVICE -t $DURATION -ac 2 -ar 44100 $OUTPUT_WAV\n\n# Wait for background processes to finish\nwait\n\n\n\n@echo off\n\n:: Define file paths and device IDs\nset INPUT_WAV=  :: Path to an optional input WAV file\nset OUTPUT_WAV=C:\\path\\to\\output\\speaker_output.wav\nset MIC_DEVICE=audio=\"Microphone (Realtek High Definition Audio)\"  :: Replace with your actual mic device name\nset SPEAKER_DEVICE=audio=\"Speakers (Realtek High Definition Audio)\" :: Replace with your actual speaker device name\nset DURATION=10  :: Duration in seconds\n\nif \"%INPUT_WAV%\"==\"\" (\n    :: Generate a test tone and play it as microphone input using ffmpeg\n    start /B ffmpeg -f lavfi -i \"sine=frequency=1000:duration=%DURATION%\" -f dshow -i %MIC_DEVICE%\n) else (\n    :: Play the provided WAV file as microphone input using ffmpeg\n    start /B ffmpeg -re -i %INPUT_WAV% -f dshow -i %MIC_DEVICE%\n)\n\n:: Record the speaker output to a WAV file\nffmpeg -f dshow -i %SPEAKER_DEVICE% -t %DURATION% -ac 2 -ar 44100 %OUTPUT_WAV%\n\n:: Wait for background processes to finish\nwait\n\n\n\n\n\nTo list available audio devices on Windows, you can use the following command:\nffmpeg -list_devices true -f dshow -i dummy\nThis will output a list of all available audio devices, which you can then use to replace the MIC_DEVICE and SPEAKER_DEVICE placeholders in the batch script.\n\n\n\nOn macOS, you can list audio devices using the following command:\nffmpeg -f avfoundation -list_devices true -i \"\"\nThis command will display both video and audio devices. Look for the audio devices and use their indices or names as needed in your scripts.\n\n\n\nFor Linux, to list audio devices using ffmpeg, you can execute the following command:\nffmpeg -f alsa -list_devices true -i dummy\nThis command will help identify available ALSA audio devices, which can be used similarly to how devices are specified in scripts on other operating systems.\n\n\n\n\n\nDefine File Paths and Device IDs:\n\nINPUT_WAV: Path to an optional input WAV file.\nOUTPUT_WAV: Path where the recorded speaker output will be saved.\nMIC_DEVICE: Microphone device ID (replace with actual device ID).\nSPEAKER_DEVICE: Speaker device ID (replace with actual device ID).\nDURATION: Duration of the recording in seconds.\n\nGenerate a Test Tone or Play Provided WAV File as Microphone Input:\n\nIf INPUT_WAV is not provided, use ffmpeg to generate a 1000 Hz sine wave test tone and play it as if it were coming from the microphone.\nIf INPUT_WAV is provided, use ffmpeg to play the WAV file as if it were coming from the microphone.\n\nRecord the Speaker Output:\n\nUse ffmpeg to record the speaker output to a WAV file for the specified duration.\n\nWait for Background Processes:\n\nEnsure all background processes complete before the script exits."
+    "text": "https://github.com/V-Sekai/\nhttps://github.com/sigstore/rekor/tree/main/pkg/pki/ssh\nhttps://stackoverflow.com/questions/4629537/how-to-encrypt-data-in-php-using-public-private-keys\nhttps://stackoverflow.com/questions/60160082/how-to-achieve-openssl-smime-encrypt-with-public-key-functionality-in-code\nhttps://github.com/cloudtools/ssh-cert-authority\nhttps://github.com/je9000/ssh-smime"
   },
   {
-    "objectID": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#the-benefits",
-    "href": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#the-benefits",
-    "title": "Proposed: FFMPEG Wave/Mic and Speaker/Play",
+    "objectID": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html#derivative-license",
+    "href": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html#derivative-license",
+    "title": "Rejected: File or attestation for virtual worlds using ssh signatures",
     "section": "",
-    "text": "Automated Testing: Enables automated testing of VOIP clients.\nVersatility: Can be used to test various VOIP applications like Discord and VRChat.\nPrototyping: Useful for prototyping WebRTC later."
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#the-downsides",
-    "href": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#the-downsides",
-    "title": "Proposed: FFMPEG Wave/Mic and Speaker/Play",
+    "objectID": "decisions/20230505-automated-avatar-garment-rigging.html",
+    "href": "decisions/20230505-automated-avatar-garment-rigging.html",
+    "title": "Proposed: Automated avatar garment rigging",
     "section": "",
-    "text": "Complex Setup: Requires knowledge of audio systems and command-line tools.\nPotential Compatibility Issues: May not work seamlessly across all hardware configurations."
+    "text": "Status: proposed\nDeciders: V-Sekai,\nTags: V-Sekai, chatgpt4, automated rigging, avatar customization, garment application, 3d modeling, Blender addons,\n\n\n\n\nRigging every possible avatar and garment combination is not feasible. We need a system that allows garments to be easily applied to various avatars without manual rigging each time a new garment or avatar is created.\n\n\n\nHow can we create a system that allows garments to be easily applied to various avatars without the need for manual rigging each time a new garment or avatar is created?\n\n\n\nImplement an automated rigging and wrapping system using known base meshes and garments for easy application of garments to avatars without manual rigging.\n\n\n\n\nCreate avatar and garment models: Create a 3D model representing the basic shape and structure of an avatar without any clothing or accessories, and a 3D model of a piece of clothing or accessory.\nRig models: Rig the avatar and garment models by creating a skeleton structure that defines how they move and deform. Use the Blender Dem Bones add-on to automate the rigging process.\nGenerate cage mesh: Generate a simplified “cage” mesh around the avatar base mesh using the Simplicage add-on. This cage will be used to help apply the garment to the avatar.\nAttach garment to cage: Attach the garment model to the cage created in the previous step, so that it follows the cage’s movement and deformation.\nConform garment to avatar: Utilize the Mesh Materializer add-on to conform the garment model to the avatar base mesh, using a UV texture map to guide the wrapping process. This ensures the garment fits correctly on the avatar.\nManage multiple layers: Develop a system to manage multiple layers of clothing or accessories on the avatar, allowing for proper layering and interaction between clothing items.\n\n\n\n\n\nReduced manual rigging efforts for each garment and avatar combination\nStreamlined process of applying garments to avatars\nEasier customization and creation of new avatars with various garments\n\n\n\n\n\nAdditional development time required to implement the automated system\nPotential compatibility issues with existing assets or workflows\nDependent on third party addons\n\nResearch and evaluate alternative solutions or develop custom tools to replace or supplement the functionality provided by these third-party add-ons. This will help ensure long-term stability and maintainability of the project.\n\nPerformance concerns with complex avatars and garments\n\nOptimize the algorithms used in the automated rigging and wrapping process to handle complex models efficiently. Additionally, consider implementing a level of detail (LOD) system to reduce the complexity of models during runtime without compromising visual quality.\n\nDifficulty in handling edge cases.\n\nDevelop a set of guidelines for creating avatar and garment models that work well with the automated system. Additionally, provide manual intervention options for users to fine-tune the rigging and wrapping results in case of edge cases.\n\n\n\n\n\n\nRelying solely on creators is inefficient; they need tools.\n\n\n\n\nNo, this enhancement requires a more complex solution involving multiple tools and processes.\n\n\n\nThis enhancement requires a complex solution involving multiple tools and processes, and cannot be worked around with a few lines of script. Implementing this feature as part of the core functionality will greatly improve the user experience and streamline the process of creating and customizing avatars with different garments.\n\n\n\n\nV-Sekai\nBlender Dem Bones\nSimplicage\nMesh Materializer"
   },
   {
-    "objectID": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#the-road-not-taken",
-    "href": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#the-road-not-taken",
-    "title": "Proposed: FFMPEG Wave/Mic and Speaker/Play",
+    "objectID": "decisions/20230505-automated-avatar-garment-rigging.html#metadata",
+    "href": "decisions/20230505-automated-avatar-garment-rigging.html#metadata",
+    "title": "Proposed: Automated avatar garment rigging",
     "section": "",
-    "text": "Using Godot-specific audio stream players and effects was considered but found to be too closely tied to Godot, limiting broader application testing."
+    "text": "Status: proposed\nDeciders: V-Sekai,\nTags: V-Sekai, chatgpt4, automated rigging, avatar customization, garment application, 3d modeling, Blender addons,"
   },
   {
-    "objectID": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#the-infrequent-use-case",
-    "href": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#the-infrequent-use-case",
-    "title": "Proposed: FFMPEG Wave/Mic and Speaker/Play",
+    "objectID": "decisions/20230505-automated-avatar-garment-rigging.html#context-and-problem-statement",
+    "href": "decisions/20230505-automated-avatar-garment-rigging.html#context-and-problem-statement",
+    "title": "Proposed: Automated avatar garment rigging",
     "section": "",
-    "text": "In cases where precise audio sample rate configuration is critical, additional adjustments may be needed to avoid issues."
+    "text": "Rigging every possible avatar and garment combination is not feasible. We need a system that allows garments to be easily applied to various avatars without manual rigging each time a new garment or avatar is created."
   },
   {
-    "objectID": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#in-core-and-done-by-us",
-    "href": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#in-core-and-done-by-us",
-    "title": "Proposed: FFMPEG Wave/Mic and Speaker/Play",
+    "objectID": "decisions/20230505-automated-avatar-garment-rigging.html#describe-the-problem-or-limitation-you-have-in-your-project-e.g.-in-free-form-using-two-to-three-sentences.-consider-articulating-the-case-in-the-form-of-a-question.",
+    "href": "decisions/20230505-automated-avatar-garment-rigging.html#describe-the-problem-or-limitation-you-have-in-your-project-e.g.-in-free-form-using-two-to-three-sentences.-consider-articulating-the-case-in-the-form-of-a-question.",
+    "title": "Proposed: Automated avatar garment rigging",
     "section": "",
-    "text": "This approach aligns with our goal of robust and versatile testing methodologies and will be implemented by our team."
+    "text": "How can we create a system that allows garments to be easily applied to various avatars without the need for manual rigging each time a new garment or avatar is created?"
   },
   {
-    "objectID": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#status",
-    "href": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#status",
-    "title": "Proposed: FFMPEG Wave/Mic and Speaker/Play",
+    "objectID": "decisions/20230505-automated-avatar-garment-rigging.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20230505-automated-avatar-garment-rigging.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: Automated avatar garment rigging",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "Implement an automated rigging and wrapping system using known base meshes and garments for easy application of garments to avatars without manual rigging."
   },
   {
-    "objectID": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#decision-makers",
-    "href": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#decision-makers",
-    "title": "Proposed: FFMPEG Wave/Mic and Speaker/Play",
+    "objectID": "decisions/20230505-automated-avatar-garment-rigging.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20230505-automated-avatar-garment-rigging.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Automated avatar garment rigging",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "Create avatar and garment models: Create a 3D model representing the basic shape and structure of an avatar without any clothing or accessories, and a 3D model of a piece of clothing or accessory.\nRig models: Rig the avatar and garment models by creating a skeleton structure that defines how they move and deform. Use the Blender Dem Bones add-on to automate the rigging process.\nGenerate cage mesh: Generate a simplified “cage” mesh around the avatar base mesh using the Simplicage add-on. This cage will be used to help apply the garment to the avatar.\nAttach garment to cage: Attach the garment model to the cage created in the previous step, so that it follows the cage’s movement and deformation.\nConform garment to avatar: Utilize the Mesh Materializer add-on to conform the garment model to the avatar base mesh, using a UV texture map to guide the wrapping process. This ensures the garment fits correctly on the avatar.\nManage multiple layers: Develop a system to manage multiple layers of clothing or accessories on the avatar, allowing for proper layering and interaction between clothing items."
   },
   {
-    "objectID": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#tags",
-    "href": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#tags",
-    "title": "Proposed: FFMPEG Wave/Mic and Speaker/Play",
+    "objectID": "decisions/20230505-automated-avatar-garment-rigging.html#positive-consequences",
+    "href": "decisions/20230505-automated-avatar-garment-rigging.html#positive-consequences",
+    "title": "Proposed: Automated avatar garment rigging",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Reduced manual rigging efforts for each garment and avatar combination\nStreamlined process of applying garments to avatars\nEasier customization and creation of new avatars with various garments"
   },
   {
-    "objectID": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#further-reading",
-    "href": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#further-reading",
-    "title": "Proposed: FFMPEG Wave/Mic and Speaker/Play",
+    "objectID": "decisions/20230505-automated-avatar-garment-rigging.html#negative-consequences",
+    "href": "decisions/20230505-automated-avatar-garment-rigging.html#negative-consequences",
+    "title": "Proposed: Automated avatar garment rigging",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "Additional development time required to implement the automated system\nPotential compatibility issues with existing assets or workflows\nDependent on third party addons\n\nResearch and evaluate alternative solutions or develop custom tools to replace or supplement the functionality provided by these third-party add-ons. This will help ensure long-term stability and maintainability of the project.\n\nPerformance concerns with complex avatars and garments\n\nOptimize the algorithms used in the automated rigging and wrapping process to handle complex models efficiently. Additionally, consider implementing a level of detail (LOD) system to reduce the complexity of models during runtime without compromising visual quality.\n\nDifficulty in handling edge cases.\n\nDevelop a set of guidelines for creating avatar and garment models that work well with the automated system. Additionally, provide manual intervention options for users to fine-tune the rigging and wrapping results in case of edge cases."
   },
   {
-    "objectID": "decisions/20230812-vsekai-update-process.html",
-    "href": "decisions/20230812-vsekai-update-process.html",
-    "title": "Proposed: Update V-Sekai game engine procedure",
+    "objectID": "decisions/20230505-automated-avatar-garment-rigging.html#option-graveyard",
+    "href": "decisions/20230505-automated-avatar-garment-rigging.html#option-graveyard",
+    "title": "Proposed: Automated avatar garment rigging",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nV-Sekai is an open-source project that aims to create a virtual world. However, it has some limitations that need to be addressed to improve its performance and user experience.\n\n\n\nThe main challenge is to update the V-Sekai game engine to enhance its features and fix existing issues.\n\n\n\nHere are the steps we propose to take:\n\nUpdate the Godot Engine fork with git assembler.\nRelease the fork to the godot engine branch.\nUpdate the V-Sekai-game engine commit hash.\nCheck the built V-Sekai-game binaries on Github.\n\n\n\n\nUpdating the game engine will provide better performance, improved features, and a more enjoyable user experience.\n\n\n\nThe downside could be potential bugs or issues that might arise during the update process. It may also require additional resources and time to implement the updates.\n\n\n\nThere might be other solutions or strategies that were considered but not chosen for this particular challenge. These could be documented here for future reference.\n\n\n\nThis section can be used to discuss any infrequent use cases that might arise from implementing this decision.\n\n\n\nThis section can be used to discuss whether this decision is core to the project and whether it should be implemented by us or outsourced to another team.\n\n\n\nFor more information about V-Sekai, you can visit their official website.\nThis article is assisted by AI."
+    "text": "Relying solely on creators is inefficient; they need tools."
   },
   {
-    "objectID": "decisions/20230812-vsekai-update-process.html#metadata",
-    "href": "decisions/20230812-vsekai-update-process.html#metadata",
-    "title": "Proposed: Update V-Sekai game engine procedure",
+    "objectID": "decisions/20230505-automated-avatar-garment-rigging.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230505-automated-avatar-garment-rigging.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Automated avatar garment rigging",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai"
+    "text": "No, this enhancement requires a more complex solution involving multiple tools and processes."
   },
   {
-    "objectID": "decisions/20230812-vsekai-update-process.html#the-backdrop",
-    "href": "decisions/20230812-vsekai-update-process.html#the-backdrop",
-    "title": "Proposed: Update V-Sekai game engine procedure",
+    "objectID": "decisions/20230505-automated-avatar-garment-rigging.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230505-automated-avatar-garment-rigging.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Automated avatar garment rigging",
     "section": "",
-    "text": "V-Sekai is an open-source project that aims to create a virtual world. However, it has some limitations that need to be addressed to improve its performance and user experience."
+    "text": "This enhancement requires a complex solution involving multiple tools and processes, and cannot be worked around with a few lines of script. Implementing this feature as part of the core functionality will greatly improve the user experience and streamline the process of creating and customizing avatars with different garments."
   },
   {
-    "objectID": "decisions/20230812-vsekai-update-process.html#the-challenge",
-    "href": "decisions/20230812-vsekai-update-process.html#the-challenge",
-    "title": "Proposed: Update V-Sekai game engine procedure",
+    "objectID": "decisions/20230505-automated-avatar-garment-rigging.html#references",
+    "href": "decisions/20230505-automated-avatar-garment-rigging.html#references",
+    "title": "Proposed: Automated avatar garment rigging",
     "section": "",
-    "text": "The main challenge is to update the V-Sekai game engine to enhance its features and fix existing issues."
+    "text": "V-Sekai\nBlender Dem Bones\nSimplicage\nMesh Materializer"
   },
   {
-    "objectID": "decisions/20230812-vsekai-update-process.html#the-strategy",
-    "href": "decisions/20230812-vsekai-update-process.html#the-strategy",
-    "title": "Proposed: Update V-Sekai game engine procedure",
+    "objectID": "decisions/20240618-schedule-as-binary-tree.html",
+    "href": "decisions/20240618-schedule-as-binary-tree.html",
+    "title": "Proposed: Transforming Schedule DAG into a Left-child Right-sibling Binary Tree",
     "section": "",
-    "text": "Here are the steps we propose to take:\n\nUpdate the Godot Engine fork with git assembler.\nRelease the fork to the godot engine branch.\nUpdate the V-Sekai-game engine commit hash.\nCheck the built V-Sekai-game binaries on Github."
+    "text": "You have a Directed Acyclic Graph (DAG) for a schedule.\n\n\n\nYou want to transform the schedule DAG into a Left-child right-sibling binary tree. This transformation will help in finding ways to hasten the critical path.\n\n\n\nThe original graph was a Directed Acyclic Graph (DAG) where each node could have multiple children. The operations performed on this DAG were aimed at transforming it into a Left-child right-sibling binary tree. Here’s a description of the operations:\n\nIdentifying the First Child: For each node in the original DAG, we identified the first child node. This is the left-most child in the original diagram.\nIdentifying Siblings: For each first child identified in step 1, we then identified its siblings. These are the nodes that share the same parent as the first child.\nCreating Binary Tree: We created a new binary tree where each node has at most two children: the left child is the first child from the original diagram, and the right child is the next sibling of the left child.\nPreserving Order: The order of the nodes in the binary tree follows the order of the nodes in the original DAG.\n\nThe resulting binary tree maintains the directed acyclic property of the original DAG, but now each node has at most two children, making it easier to traverse and manage.\n\n\n\nTransforming the schedule DAG into a Left-child right-sibling binary tree simplifies the structure, making it easier to traverse and manage. It also helps in identifying the critical path more efficiently, which can lead to improved scheduling and better resource allocation.\n\n\n\nThe transformation process may require additional computational resources, especially for large DAGs. Also, if the original DAG has nodes with more than two children, some information may be lost in the transformation.\n\n\n\nAn alternative approach could have been to keep the original DAG structure and optimize the scheduling algorithm. However, this would not simplify the structure or make it easier to manage.\n\n\n\nThis proposal may not be beneficial for small DAGs or DAGs where the critical path is easily identifiable without transformation.\n\n\n\nThe proposed transformation process will be implemented by the V-Sekai development team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\nFire\n\n\n\n\n\nV-Sekai\nDAG\nBinary Tree\nSchedule Optimization\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20230812-vsekai-update-process.html#the-upside",
-    "href": "decisions/20230812-vsekai-update-process.html#the-upside",
-    "title": "Proposed: Update V-Sekai game engine procedure",
+    "objectID": "decisions/20240618-schedule-as-binary-tree.html#the-context",
+    "href": "decisions/20240618-schedule-as-binary-tree.html#the-context",
+    "title": "Proposed: Transforming Schedule DAG into a Left-child Right-sibling Binary Tree",
     "section": "",
-    "text": "Updating the game engine will provide better performance, improved features, and a more enjoyable user experience."
+    "text": "You have a Directed Acyclic Graph (DAG) for a schedule."
   },
   {
-    "objectID": "decisions/20230812-vsekai-update-process.html#the-downside",
-    "href": "decisions/20230812-vsekai-update-process.html#the-downside",
-    "title": "Proposed: Update V-Sekai game engine procedure",
+    "objectID": "decisions/20240618-schedule-as-binary-tree.html#the-problem-statement",
+    "href": "decisions/20240618-schedule-as-binary-tree.html#the-problem-statement",
+    "title": "Proposed: Transforming Schedule DAG into a Left-child Right-sibling Binary Tree",
     "section": "",
-    "text": "The downside could be potential bugs or issues that might arise during the update process. It may also require additional resources and time to implement the updates."
+    "text": "You want to transform the schedule DAG into a Left-child right-sibling binary tree. This transformation will help in finding ways to hasten the critical path."
   },
   {
-    "objectID": "decisions/20230812-vsekai-update-process.html#the-road-not-taken",
-    "href": "decisions/20230812-vsekai-update-process.html#the-road-not-taken",
-    "title": "Proposed: Update V-Sekai game engine procedure",
+    "objectID": "decisions/20240618-schedule-as-binary-tree.html#solution-proposal",
+    "href": "decisions/20240618-schedule-as-binary-tree.html#solution-proposal",
+    "title": "Proposed: Transforming Schedule DAG into a Left-child Right-sibling Binary Tree",
     "section": "",
-    "text": "There might be other solutions or strategies that were considered but not chosen for this particular challenge. These could be documented here for future reference."
+    "text": "The original graph was a Directed Acyclic Graph (DAG) where each node could have multiple children. The operations performed on this DAG were aimed at transforming it into a Left-child right-sibling binary tree. Here’s a description of the operations:\n\nIdentifying the First Child: For each node in the original DAG, we identified the first child node. This is the left-most child in the original diagram.\nIdentifying Siblings: For each first child identified in step 1, we then identified its siblings. These are the nodes that share the same parent as the first child.\nCreating Binary Tree: We created a new binary tree where each node has at most two children: the left child is the first child from the original diagram, and the right child is the next sibling of the left child.\nPreserving Order: The order of the nodes in the binary tree follows the order of the nodes in the original DAG.\n\nThe resulting binary tree maintains the directed acyclic property of the original DAG, but now each node has at most two children, making it easier to traverse and manage."
   },
   {
-    "objectID": "decisions/20230812-vsekai-update-process.html#the-infrequent-use-case",
-    "href": "decisions/20230812-vsekai-update-process.html#the-infrequent-use-case",
-    "title": "Proposed: Update V-Sekai game engine procedure",
+    "objectID": "decisions/20240618-schedule-as-binary-tree.html#the-benefits",
+    "href": "decisions/20240618-schedule-as-binary-tree.html#the-benefits",
+    "title": "Proposed: Transforming Schedule DAG into a Left-child Right-sibling Binary Tree",
     "section": "",
-    "text": "This section can be used to discuss any infrequent use cases that might arise from implementing this decision."
+    "text": "Transforming the schedule DAG into a Left-child right-sibling binary tree simplifies the structure, making it easier to traverse and manage. It also helps in identifying the critical path more efficiently, which can lead to improved scheduling and better resource allocation."
   },
   {
-    "objectID": "decisions/20230812-vsekai-update-process.html#in-core-and-done-by-us",
-    "href": "decisions/20230812-vsekai-update-process.html#in-core-and-done-by-us",
-    "title": "Proposed: Update V-Sekai game engine procedure",
+    "objectID": "decisions/20240618-schedule-as-binary-tree.html#the-downsides",
+    "href": "decisions/20240618-schedule-as-binary-tree.html#the-downsides",
+    "title": "Proposed: Transforming Schedule DAG into a Left-child Right-sibling Binary Tree",
     "section": "",
-    "text": "This section can be used to discuss whether this decision is core to the project and whether it should be implemented by us or outsourced to another team."
+    "text": "The transformation process may require additional computational resources, especially for large DAGs. Also, if the original DAG has nodes with more than two children, some information may be lost in the transformation."
   },
   {
-    "objectID": "decisions/20230812-vsekai-update-process.html#further-reading",
-    "href": "decisions/20230812-vsekai-update-process.html#further-reading",
-    "title": "Proposed: Update V-Sekai game engine procedure",
+    "objectID": "decisions/20240618-schedule-as-binary-tree.html#the-road-not-taken",
+    "href": "decisions/20240618-schedule-as-binary-tree.html#the-road-not-taken",
+    "title": "Proposed: Transforming Schedule DAG into a Left-child Right-sibling Binary Tree",
     "section": "",
-    "text": "For more information about V-Sekai, you can visit their official website.\nThis article is assisted by AI."
+    "text": "An alternative approach could have been to keep the original DAG structure and optimize the scheduling algorithm. However, this would not simplify the structure or make it easier to manage."
   },
   {
-    "objectID": "decisions/20240418-college-quest.html",
-    "href": "decisions/20240418-college-quest.html",
-    "title": "Proposed: Town Courier",
+    "objectID": "decisions/20240618-schedule-as-binary-tree.html#the-infrequent-use-case",
+    "href": "decisions/20240618-schedule-as-binary-tree.html#the-infrequent-use-case",
+    "title": "Proposed: Transforming Schedule DAG into a Left-child Right-sibling Binary Tree",
     "section": "",
-    "text": "In the current gaming landscape, there is a noticeable gap for immersive, open-world games set in realistic environments such as a college town. Most games focus on fantasy or post-apocalyptic settings, leaving room for games that engagingly simulate everyday life.\n\n\n\nThe goal is to create an open-world game that provides players with a unique and dynamic environment, offering a fresh experience every time they play. The game should be set in a bustling college town and allow players to take on the role of a delivery person completing quests. The delivery person will navigate the town on a moped, adding an extra layer of fun and challenge to the gameplay.\n\n\n\n“Town Courier” will be developed using the Godot Engine. The game world will be procedurally generated, ensuring that no two playthroughs are identical. NPCs will assign delivery quests to the player, who must navigate the town and deliver items on a moped within a specified time limit. We will utilize the preexisting vehicle code from “Crappy Contraptions” to facilitate the movement mechanics in our game.\n\n\n\nThis game will fill a niche in the market for realistic, open-world games. It will provide players with a unique and dynamic gaming experience, keeping them engaged and encouraging replayability.\n\n\n\nThe development of a procedurally generated open-world game can be complex and time-consuming. Additionally, balancing the difficulty of the quests to ensure they are challenging but not frustrating may require extensive testing and tweaking.\n\n\n\nAn alternative approach could be to create a static game world with pre-defined quests. However, this would not provide the same level of replayability and could become repetitive for players.\n\n\n\nIn rare cases, the procedural generation may create a game world that is difficult or impossible to navigate. This will need to be addressed during testing.\n\n\n\nThe core gameplay mechanics, including movement, item pickup, and quest assignment, will be developed by our team. We will also handle the creation of the procedurally generated game world.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nCrappy Contraptions\n“City Grid Block” (https://skfb.ly/onMzQ) by antoniojmonteiro is licensed under Creative Commons Attribution\n\nAI assistant Aria assisted with this article."
+    "text": "This proposal may not be beneficial for small DAGs or DAGs where the critical path is easily identifiable without transformation."
   },
   {
-    "objectID": "decisions/20240418-college-quest.html#the-context",
-    "href": "decisions/20240418-college-quest.html#the-context",
-    "title": "Proposed: Town Courier",
+    "objectID": "decisions/20240618-schedule-as-binary-tree.html#in-core-and-done-by-us",
+    "href": "decisions/20240618-schedule-as-binary-tree.html#in-core-and-done-by-us",
+    "title": "Proposed: Transforming Schedule DAG into a Left-child Right-sibling Binary Tree",
     "section": "",
-    "text": "In the current gaming landscape, there is a noticeable gap for immersive, open-world games set in realistic environments such as a college town. Most games focus on fantasy or post-apocalyptic settings, leaving room for games that engagingly simulate everyday life."
+    "text": "The proposed transformation process will be implemented by the V-Sekai development team."
   },
   {
-    "objectID": "decisions/20240418-college-quest.html#the-problem-statement",
-    "href": "decisions/20240418-college-quest.html#the-problem-statement",
-    "title": "Proposed: Town Courier",
+    "objectID": "decisions/20240618-schedule-as-binary-tree.html#status",
+    "href": "decisions/20240618-schedule-as-binary-tree.html#status",
+    "title": "Proposed: Transforming Schedule DAG into a Left-child Right-sibling Binary Tree",
     "section": "",
-    "text": "The goal is to create an open-world game that provides players with a unique and dynamic environment, offering a fresh experience every time they play. The game should be set in a bustling college town and allow players to take on the role of a delivery person completing quests. The delivery person will navigate the town on a moped, adding an extra layer of fun and challenge to the gameplay."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20240418-college-quest.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240418-college-quest.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Town Courier",
+    "objectID": "decisions/20240618-schedule-as-binary-tree.html#decision-makers",
+    "href": "decisions/20240618-schedule-as-binary-tree.html#decision-makers",
+    "title": "Proposed: Transforming Schedule DAG into a Left-child Right-sibling Binary Tree",
     "section": "",
-    "text": "“Town Courier” will be developed using the Godot Engine. The game world will be procedurally generated, ensuring that no two playthroughs are identical. NPCs will assign delivery quests to the player, who must navigate the town and deliver items on a moped within a specified time limit. We will utilize the preexisting vehicle code from “Crappy Contraptions” to facilitate the movement mechanics in our game."
+    "text": "V-Sekai development team\nFire"
   },
   {
-    "objectID": "decisions/20240418-college-quest.html#the-benefits",
-    "href": "decisions/20240418-college-quest.html#the-benefits",
-    "title": "Proposed: Town Courier",
+    "objectID": "decisions/20240618-schedule-as-binary-tree.html#tags",
+    "href": "decisions/20240618-schedule-as-binary-tree.html#tags",
+    "title": "Proposed: Transforming Schedule DAG into a Left-child Right-sibling Binary Tree",
     "section": "",
-    "text": "This game will fill a niche in the market for realistic, open-world games. It will provide players with a unique and dynamic gaming experience, keeping them engaged and encouraging replayability."
+    "text": "V-Sekai\nDAG\nBinary Tree\nSchedule Optimization"
   },
   {
-    "objectID": "decisions/20240418-college-quest.html#the-downsides",
-    "href": "decisions/20240418-college-quest.html#the-downsides",
-    "title": "Proposed: Town Courier",
+    "objectID": "decisions/20240618-schedule-as-binary-tree.html#further-reading",
+    "href": "decisions/20240618-schedule-as-binary-tree.html#further-reading",
+    "title": "Proposed: Transforming Schedule DAG into a Left-child Right-sibling Binary Tree",
     "section": "",
-    "text": "The development of a procedurally generated open-world game can be complex and time-consuming. Additionally, balancing the difficulty of the quests to ensure they are challenging but not frustrating may require extensive testing and tweaking."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240418-college-quest.html#the-road-not-taken",
-    "href": "decisions/20240418-college-quest.html#the-road-not-taken",
-    "title": "Proposed: Town Courier",
+    "objectID": "decisions/20220223-store-source-VSK_map-files-via-DVC.html",
+    "href": "decisions/20220223-store-source-VSK_map-files-via-DVC.html",
+    "title": "Rejected: Storing raw VSK_map files via DVC to avoid limitations",
     "section": "",
-    "text": "An alternative approach could be to create a static game world with pre-defined quests. However, this would not provide the same level of replayability and could become repetitive for players."
+    "text": "pipeline\nV-Sekai\n\n\n\n\n\nrejected \n\n\n\n\n\nV-Sekai\nifire\nlyuma\n\n\n\n\nHow do I version control large binary game assets?\nNeed a procedure to version control large file folders like game map levels.\n\n\n\nPropose using DVC as the version control system on top of git with a S3 remote on Digital Ocean.\n\n\n\nInitial list of binaries to transfer to DVC\nUse a Linux command to get the top 20 by size file types.\n\n*.glb\n*.gltf\n*.bin*\n*.png\n*.webp\n*.jpg\n*.jpeg\n*.exr\n*.scn\n\n\n\nS3 Compatible has multiple implementations. Intent on using digital ocean spaces.\n\n\n\n\nPermissions?\nOpen bucket\nCost of storage\n\n\n\n\n\nhttps://dvc.org/doc/install/windows\n\nhttps://github.com/iterative/dvc/releases/download/2.9.5/dvc-2.9.5.exe\n\nhttps://dvc.org/doc/install/linux\n\n\n\n\ngit clone https://github.com/fire/avatar-wellness.git\ndvc init\ndvc remote add -d chibifire-dvc-web https://chibifire.sfo3.digitaloceanspaces.com/dvc/\n# dvc remote add --local chibifire-dvc-s3 s3://chibifire/dvc\n# dvc remote modify --local chibifire-dvc-s3 endpointurl sfo3.digitaloceanspaces.com\n# dvc remote modify --local chibifire-dvc-s3 access_key_id 'AAAA'\n# dvc remote modify --local chibifire-dvc-s3 secret_access_key 'BBBB'\ndvc config core.autostage true\n\n\n\nDiscussed with Lyuma how it is possible to make a V-Sekai alternative organization for creator repositories.\n\n\n\n\n\nAble to version control maps.\n\n\n\n\n\nUsability now has a gap.\n\n\n\n\n\nOption: Do not use DVC remote on Google drive.\nRejection Reason: Google Drive does not have two implementations\nOption: Use Github with git-lfs\nRejection Reason: The last time I checked it was 50 USD per 50 gigabytes.\nOption: Use Gitlab git-lfs\nRejection Reason: There is slightly larger limit on https://gitlab.com git-lfs but gitlab.com does not scale with usage.\nOption: Use Gitlab.com\nRejection Reason: Gitlab.com commrcial is expensive\n\n\n\n\nA version control system and object stores are not trivial and hard.\n\n\n\nWe want to present V-Sekai maps for others to remix.\n\n\n\n\nDVC Version Control system \n\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240418-college-quest.html#the-infrequent-use-case",
-    "href": "decisions/20240418-college-quest.html#the-infrequent-use-case",
-    "title": "Proposed: Town Courier",
+    "objectID": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#categories",
+    "href": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#categories",
+    "title": "Rejected: Storing raw VSK_map files via DVC to avoid limitations",
     "section": "",
-    "text": "In rare cases, the procedural generation may create a game world that is difficult or impossible to navigate. This will need to be addressed during testing."
+    "text": "pipeline\nV-Sekai"
   },
   {
-    "objectID": "decisions/20240418-college-quest.html#in-core-and-done-by-us",
-    "href": "decisions/20240418-college-quest.html#in-core-and-done-by-us",
-    "title": "Proposed: Town Courier",
+    "objectID": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#status",
+    "href": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#status",
+    "title": "Rejected: Storing raw VSK_map files via DVC to avoid limitations",
     "section": "",
-    "text": "The core gameplay mechanics, including movement, item pickup, and quest assignment, will be developed by our team. We will also handle the creation of the procedurally generated game world."
+    "text": "rejected"
   },
   {
-    "objectID": "decisions/20240418-college-quest.html#status",
-    "href": "decisions/20240418-college-quest.html#status",
-    "title": "Proposed: Town Courier",
+    "objectID": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#deciders",
+    "href": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#deciders",
+    "title": "Rejected: Storing raw VSK_map files via DVC to avoid limitations",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "V-Sekai\nifire\nlyuma"
   },
   {
-    "objectID": "decisions/20240418-college-quest.html#decision-makers",
-    "href": "decisions/20240418-college-quest.html#decision-makers",
-    "title": "Proposed: Town Courier",
+    "objectID": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#context-and-problem-statement",
+    "href": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#context-and-problem-statement",
+    "title": "Rejected: Storing raw VSK_map files via DVC to avoid limitations",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "How do I version control large binary game assets?\nNeed a procedure to version control large file folders like game map levels."
   },
   {
-    "objectID": "decisions/20240418-college-quest.html#tags",
-    "href": "decisions/20240418-college-quest.html#tags",
-    "title": "Proposed: Town Courier",
+    "objectID": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Rejected: Storing raw VSK_map files via DVC to avoid limitations",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Propose using DVC as the version control system on top of git with a S3 remote on Digital Ocean."
   },
   {
-    "objectID": "decisions/20240418-college-quest.html#further-reading",
-    "href": "decisions/20240418-college-quest.html#further-reading",
-    "title": "Proposed: Town Courier",
+    "objectID": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Rejected: Storing raw VSK_map files via DVC to avoid limitations",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nCrappy Contraptions\n“City Grid Block” (https://skfb.ly/onMzQ) by antoniojmonteiro is licensed under Creative Commons Attribution\n\nAI assistant Aria assisted with this article."
+    "text": "Initial list of binaries to transfer to DVC\nUse a Linux command to get the top 20 by size file types.\n\n*.glb\n*.gltf\n*.bin*\n*.png\n*.webp\n*.jpg\n*.jpeg\n*.exr\n*.scn\n\n\n\nS3 Compatible has multiple implementations. Intent on using digital ocean spaces.\n\n\n\n\nPermissions?\nOpen bucket\nCost of storage\n\n\n\n\n\nhttps://dvc.org/doc/install/windows\n\nhttps://github.com/iterative/dvc/releases/download/2.9.5/dvc-2.9.5.exe\n\nhttps://dvc.org/doc/install/linux\n\n\n\n\ngit clone https://github.com/fire/avatar-wellness.git\ndvc init\ndvc remote add -d chibifire-dvc-web https://chibifire.sfo3.digitaloceanspaces.com/dvc/\n# dvc remote add --local chibifire-dvc-s3 s3://chibifire/dvc\n# dvc remote modify --local chibifire-dvc-s3 endpointurl sfo3.digitaloceanspaces.com\n# dvc remote modify --local chibifire-dvc-s3 access_key_id 'AAAA'\n# dvc remote modify --local chibifire-dvc-s3 secret_access_key 'BBBB'\ndvc config core.autostage true\n\n\n\nDiscussed with Lyuma how it is possible to make a V-Sekai alternative organization for creator repositories."
   },
   {
-    "objectID": "decisions/20211005-use-kvm-to-test-our-amd-apu-test-computer-via-barrier.html",
-    "href": "decisions/20211005-use-kvm-to-test-our-amd-apu-test-computer-via-barrier.html",
-    "title": "Proposed: Use KVM to test our AMD APU test computer via Barrier.",
+    "objectID": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#positive-consequences",
+    "href": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#positive-consequences",
+    "title": "Rejected: Storing raw VSK_map files via DVC to avoid limitations",
     "section": "",
-    "text": "Proposed: Use KVM to test our AMD APU test computer via Barrier.\n\nContext and Problem Statement\nUse KVM to test our AMD APU test computer via Barrier.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nBarrier allows us to use the keyboard and mouse transferring commands from Linux to Windows.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nBarrier allows us to use the keyboard and mouse transferring commands from Linux to Windows.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nThis is an operating procedure guide.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nThis a guide.\n\n\nReferences\n\nhttps://github.com/debauchee/barrier\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Able to version control maps."
   },
   {
-    "objectID": "decisions/20211031-thorvg.html",
-    "href": "decisions/20211031-thorvg.html",
-    "title": "Accepted: ThorVG",
+    "objectID": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#negative-consequences",
+    "href": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#negative-consequences",
+    "title": "Rejected: Storing raw VSK_map files via DVC to avoid limitations",
     "section": "",
-    "text": "Accepted: ThorVG\n\nStatus: accepted\n\n\nContext and Problem Statement\nBetter vector art.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nThorvg supports more art\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n\nThorVG\nsupport light and dark theme\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\n\nnot a few lines of code to do. It’s complicated.\n\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\n@fire know how to approach this.\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Usability now has a gap."
   },
   {
-    "objectID": "decisions/20200729-entity-networking.html",
-    "href": "decisions/20200729-entity-networking.html",
-    "title": "Accepted: Adding Entity Networking to Groups",
+    "objectID": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#option-graveyard",
+    "href": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#option-graveyard",
+    "title": "Rejected: Storing raw VSK_map files via DVC to avoid limitations",
     "section": "",
-    "text": "Status: accepted\nDeciders: V-Sekai,Lyuma,SaracenOne\n\n\n\nFor Groups, this system aims to solve the following issues:\n\n(A) Need a way to standardize scene spawning.\n(B) Need a way to refer to nodes/instances that is consistent across clients (for example, “Set parent to …”).\n(C) Need a way to synchronize state between clients.\n(D) Provides a basic set of standard protocols and interactions.\n(E) Provides the basis for a security/privacy model regarding entity communication/permissions over the network.\n(F) Provides a security model locally for access between nodes of one entity and nodes of another entity (assuming a secure scripting framework is implemented).\n(G) This also solves the problem of abstracting away implementation details of entities; for example, there should be no need to deal with Godot nodes on an individual basis.\n(H) Provide a unified way to create top-level physics hierarchies isolated from other game logic.\n\nNote: This proposal covers three Spawn Types:\n\nSpawn type (i) Entities integrated into a map;\nSpawn type (ii) map entities spawned by clients; and\nSpawn type (iii) avatar entities/props spawned by clients.)\n\n\n\n\nAs indicated in point (G), everything documented here relates to Scenes and Entities. Aside from the Entity script being attached to the root node of a scene(?), and the scene itself being a node. Additionally, it may be necessary to query a node to find its containing entity (parent node). Note: Interaction between nodes within a single entity is considered an implementation detail of that entity and is out of the scope of the entity system. Any security model assumes that nodes cannot be transferred, shared or reparented between entities.\nEntities are objects known to the server and with explicit handling for state synchronization.\nSome entities may choose to synchronize little state, or position only, or no state at all. Also, some entities may choose to provide no security or isolation, while others may be private and appear not to even exist to other nodes. For example, a local player menu built upon the Entity System’s interaction features, gaining features A, D, F and G. By building this common framework, it means that systems built as Entities can be trivially synchronized over the network.\n\n\n\nTodo: We may want a way to optimistically spawn an entity client-side to achieve maximal responsiveness and fun.\nHowever, these entities will not yet know their server-side entity ID. Proposals: Reserve portion of ID space; or locally hold onto events/state and flush once the ID is known.\n\n\nThere will be a global directory of spawnable objects as part of a server connection. Players and maps can reference scenes by some name to spawn an entity with that name.\n\n\n\nEntities will have a server-assigned ID. Todo: What to do if an entity is spawned locally and an ID is not yet known.\n\n\n\nEntities will define a set of state variables that must be synced. The network protocol will take care of updating the state gradually over time, as well as rate-limiting. Events can be used to provide forced updates. Guarantees? Exposing metadata about when the state was updated?\nEntity properties:\n\nState that is synced is properties.\nSome properties are only assignable at spawn time (for example, scene file?)\nSome properties such as transform may require special handling.\n\nUpdate intervals:\nEntity refreshing / full state synchronization & serialization:\nDelta encoding & ACK protocol:\nWhen to use reliable events vs. “unreliable” (eventual) state synchronization: Events as a means for state synchronization.\n\n\n\nTODO: What classes / bespoke types exist? Examples: Physics, Physics Pickup; Button; Movable Platform; Vehicle\n\n\n\nConcepts:\nOwnership:\nAll entities will be owned by the player who interacts with them or by the server.\nEntity ownership will be transferred if the current owner leaves.\nMastership:\nMap entities may largely be mastered by a dedicated server.\nAvatar entities and props will be mastered by the player that spawned them, even if another player owns them.\n(Example: Alice personally spawns a ball avatar prop and throws it to Bob, who catches it. Alice has Mastership; Bob has Ownership.)\nMastership may be transferred on map exit; or they may be despawned (the player “takes” their props with them.)\nPrivacy: Entities may reveal very little state to the network. Are there cases where different players may be given different permissions?\nExample: Cooperative game, in which state is shared between some players but not others.\nExample: Team Melee\n\n\n\nScript-level guarantees that information about other entities is either restricted or absent entirely.\nIt may require a custom scripting language to achieve these guarantees fully.\n\n\n\nNot much to say here. We should see as little as possible built on top of pure Godot Nodes, except as a means for providing the entity’s functions.\n\n\n\nEntities will not be allowed to contain physics objects within the node hierarchy. Instead, physics objects must be attached to the entity in specific ways.\nQuestions: how does this work with PhysicalBone; how are physics objects linked to the entity; what about animations? (scale, rotation, skeleton attachments driving physical bodies?)\n\n\n\nMaps will have entities that might not be spawnable but will be automatically created and referenced within the parent scene.\nFor example, a button/door; or a state “god object”; or physics objects; built-in TV screens.\n\n\n\nMaps will provide a directory of map-spawnable scene references, which can be instantiated in response to events.\nThese will usually have specific functions within a particular map.\nExamples: Game-specific weapons; Keys; Buildings constructed\n\n\n\nPlayers may also provide a directory of avatar-spawnable scenes; Additionally, a prop database may exist or be negotiated.\nThese may include local UIs; weapons, pencils; media players; pets (parrots, mounts); vehicles; flight mechanics (wings?); visual effects.\n\n\n\nNodePath references (../) out of an entity hierarchy must be disallowed. Parenting should be implemented carefully: If nodes are literally parented to another entity (e.g. vehicles), NodePath references could expose implementation details from one entity to another entity.\nPart of a solution to this is to provide Attachment points as a feature of an Entity, but this needs to be implemented carefully to prevent unusual situations, for example, parent entity/node is destroyed (queue_free()) or removed from the scene tree (remove_child()); or animation paths referencing a node of the child entity.\n\n\n\n\n\nPossibility of:\n\nvehicle games\nbow and arrow games\npickup of balls\n\n\n\n\n\n\nComplexity\n\n\n\n\nA networking system is not a few lines of code.\n\n\n\nYes, this is the foundation of the protocol and the basic set of nodes and behavior upon which content will be created.\n\n\n\nAldridge, David. “I Shot You First: networking the Gameplay of Halo: Reach”. GDC 2011. https://www.youtube.com/watch?v=h47zZrqjgLc\nFiedler, Glenn. “Networking for Physics Programmers”. GDC 2015. https://www.youtube.com/watch?v=Z9X4lysFr64\nFiedler, Glenn. “Networked Physics in Virtual Reality”. 2018-02-22. https://www.gafferongames.com/post/networked_physics_in_virtual_reality/\nRouwe, Jorrit. “Killzone Shadow Fall: Threading the Entity Update on PS4”. GDCEU 2014. https://archive.org/details/GDCEU2014Rouwe\nSaracen, text and voice discussions on Discord: search Discord for “entity networking” and “networking model”\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Option: Do not use DVC remote on Google drive.\nRejection Reason: Google Drive does not have two implementations\nOption: Use Github with git-lfs\nRejection Reason: The last time I checked it was 50 USD per 50 gigabytes.\nOption: Use Gitlab git-lfs\nRejection Reason: There is slightly larger limit on https://gitlab.com git-lfs but gitlab.com does not scale with usage.\nOption: Use Gitlab.com\nRejection Reason: Gitlab.com commrcial is expensive"
   },
   {
-    "objectID": "decisions/20200729-entity-networking.html#context-and-problem-statement",
-    "href": "decisions/20200729-entity-networking.html#context-and-problem-statement",
-    "title": "Accepted: Adding Entity Networking to Groups",
+    "objectID": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Rejected: Storing raw VSK_map files via DVC to avoid limitations",
     "section": "",
-    "text": "For Groups, this system aims to solve the following issues:\n\n(A) Need a way to standardize scene spawning.\n(B) Need a way to refer to nodes/instances that is consistent across clients (for example, “Set parent to …”).\n(C) Need a way to synchronize state between clients.\n(D) Provides a basic set of standard protocols and interactions.\n(E) Provides the basis for a security/privacy model regarding entity communication/permissions over the network.\n(F) Provides a security model locally for access between nodes of one entity and nodes of another entity (assuming a secure scripting framework is implemented).\n(G) This also solves the problem of abstracting away implementation details of entities; for example, there should be no need to deal with Godot nodes on an individual basis.\n(H) Provide a unified way to create top-level physics hierarchies isolated from other game logic.\n\nNote: This proposal covers three Spawn Types:\n\nSpawn type (i) Entities integrated into a map;\nSpawn type (ii) map entities spawned by clients; and\nSpawn type (iii) avatar entities/props spawned by clients.)"
+    "text": "A version control system and object stores are not trivial and hard."
   },
   {
-    "objectID": "decisions/20200729-entity-networking.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20200729-entity-networking.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Accepted: Adding Entity Networking to Groups",
+    "objectID": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Rejected: Storing raw VSK_map files via DVC to avoid limitations",
     "section": "",
-    "text": "As indicated in point (G), everything documented here relates to Scenes and Entities. Aside from the Entity script being attached to the root node of a scene(?), and the scene itself being a node. Additionally, it may be necessary to query a node to find its containing entity (parent node). Note: Interaction between nodes within a single entity is considered an implementation detail of that entity and is out of the scope of the entity system. Any security model assumes that nodes cannot be transferred, shared or reparented between entities.\nEntities are objects known to the server and with explicit handling for state synchronization.\nSome entities may choose to synchronize little state, or position only, or no state at all. Also, some entities may choose to provide no security or isolation, while others may be private and appear not to even exist to other nodes. For example, a local player menu built upon the Entity System’s interaction features, gaining features A, D, F and G. By building this common framework, it means that systems built as Entities can be trivially synchronized over the network."
+    "text": "We want to present V-Sekai maps for others to remix."
   },
   {
-    "objectID": "decisions/20200729-entity-networking.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-andor-diagrams",
-    "href": "decisions/20200729-entity-networking.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-andor-diagrams",
-    "title": "Accepted: Adding Entity Networking to Groups",
+    "objectID": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#references",
+    "href": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#references",
+    "title": "Rejected: Storing raw VSK_map files via DVC to avoid limitations",
     "section": "",
-    "text": "Todo: We may want a way to optimistically spawn an entity client-side to achieve maximal responsiveness and fun.\nHowever, these entities will not yet know their server-side entity ID. Proposals: Reserve portion of ID space; or locally hold onto events/state and flush once the ID is known.\n\n\nThere will be a global directory of spawnable objects as part of a server connection. Players and maps can reference scenes by some name to spawn an entity with that name.\n\n\n\nEntities will have a server-assigned ID. Todo: What to do if an entity is spawned locally and an ID is not yet known.\n\n\n\nEntities will define a set of state variables that must be synced. The network protocol will take care of updating the state gradually over time, as well as rate-limiting. Events can be used to provide forced updates. Guarantees? Exposing metadata about when the state was updated?\nEntity properties:\n\nState that is synced is properties.\nSome properties are only assignable at spawn time (for example, scene file?)\nSome properties such as transform may require special handling.\n\nUpdate intervals:\nEntity refreshing / full state synchronization & serialization:\nDelta encoding & ACK protocol:\nWhen to use reliable events vs. “unreliable” (eventual) state synchronization: Events as a means for state synchronization.\n\n\n\nTODO: What classes / bespoke types exist? Examples: Physics, Physics Pickup; Button; Movable Platform; Vehicle\n\n\n\nConcepts:\nOwnership:\nAll entities will be owned by the player who interacts with them or by the server.\nEntity ownership will be transferred if the current owner leaves.\nMastership:\nMap entities may largely be mastered by a dedicated server.\nAvatar entities and props will be mastered by the player that spawned them, even if another player owns them.\n(Example: Alice personally spawns a ball avatar prop and throws it to Bob, who catches it. Alice has Mastership; Bob has Ownership.)\nMastership may be transferred on map exit; or they may be despawned (the player “takes” their props with them.)\nPrivacy: Entities may reveal very little state to the network. Are there cases where different players may be given different permissions?\nExample: Cooperative game, in which state is shared between some players but not others.\nExample: Team Melee\n\n\n\nScript-level guarantees that information about other entities is either restricted or absent entirely.\nIt may require a custom scripting language to achieve these guarantees fully.\n\n\n\nNot much to say here. We should see as little as possible built on top of pure Godot Nodes, except as a means for providing the entity’s functions.\n\n\n\nEntities will not be allowed to contain physics objects within the node hierarchy. Instead, physics objects must be attached to the entity in specific ways.\nQuestions: how does this work with PhysicalBone; how are physics objects linked to the entity; what about animations? (scale, rotation, skeleton attachments driving physical bodies?)\n\n\n\nMaps will have entities that might not be spawnable but will be automatically created and referenced within the parent scene.\nFor example, a button/door; or a state “god object”; or physics objects; built-in TV screens.\n\n\n\nMaps will provide a directory of map-spawnable scene references, which can be instantiated in response to events.\nThese will usually have specific functions within a particular map.\nExamples: Game-specific weapons; Keys; Buildings constructed\n\n\n\nPlayers may also provide a directory of avatar-spawnable scenes; Additionally, a prop database may exist or be negotiated.\nThese may include local UIs; weapons, pencils; media players; pets (parrots, mounts); vehicles; flight mechanics (wings?); visual effects.\n\n\n\nNodePath references (../) out of an entity hierarchy must be disallowed. Parenting should be implemented carefully: If nodes are literally parented to another entity (e.g. vehicles), NodePath references could expose implementation details from one entity to another entity.\nPart of a solution to this is to provide Attachment points as a feature of an Entity, but this needs to be implemented carefully to prevent unusual situations, for example, parent entity/node is destroyed (queue_free()) or removed from the scene tree (remove_child()); or animation paths referencing a node of the child entity."
+    "text": "DVC Version Control system"
   },
   {
-    "objectID": "decisions/20200729-entity-networking.html#positive-consequences-list",
-    "href": "decisions/20200729-entity-networking.html#positive-consequences-list",
-    "title": "Accepted: Adding Entity Networking to Groups",
+    "objectID": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#derivative-license",
+    "href": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#derivative-license",
+    "title": "Rejected: Storing raw VSK_map files via DVC to avoid limitations",
     "section": "",
-    "text": "Possibility of:\n\nvehicle games\nbow and arrow games\npickup of balls"
+    "text": "Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20200729-entity-networking.html#negative-consequences-list",
-    "href": "decisions/20200729-entity-networking.html#negative-consequences-list",
-    "title": "Accepted: Adding Entity Networking to Groups",
+    "objectID": "decisions/20220605-host-internal-baserow.html",
+    "href": "decisions/20220605-host-internal-baserow.html",
+    "title": "Proposed: Host a baserow application for internal use.",
     "section": "",
-    "text": "Complexity"
+    "text": "Proposed: Host a baserow application for internal use.\n\nDescribe the status of the issue.\n\nproposed\ndraft\nrejected\naccepted\ndeprecated\nsuperseded by\n\n\n\nList the deciders of the issue.\nV-Sekai,fire\n\n\nDescribe the tags of the issue.\nV-Sekai,\n\n\nContext and Problem Statement\nI want to store adjacent information related to V-Sekai in a database.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nAdd a digital ocean apps config.\nhttps://www.digitalocean.com/products/app-platform\nFeatures:\n\nmanaged postgresql database\nno managed redis\ndigital ocean spaces\napps platform\n\ndatabases:\n- engine: PG\n  name: baserow-db\n  num_nodes: 1\n  size: basic-xs\n  version: \"12\"\nname: chibifire-base\nregion: tor\nservices:\n- envs:\n  - key: BASEROW_PUBLIC_URL\n    scope: RUN_AND_BUILD_TIME\n    value: https://${APP_DOMAIN}\n  - key: DATABASE_URL\n    scope: RUN_AND_BUILD_TIME\n    value: postgresql://${baserow-db.USERNAME}:${baserow-db.PASSWORD}@${baserow-db.HOSTNAME}:${baserow-db.PORT}/${baserow-db.DATABASE}\n  - key: AWS_ACCESS_KEY_ID\n    scope: RUN_AND_BUILD_TIME\n    value: AWS_ACCESS_KEY_ID_AWS_ACCESS_KEY_ID\n  - key: AWS_S3_ENDPOINT_URL\n    scope: RUN_AND_BUILD_TIME\n    value: https://sfo3.digitaloceanspaces.com\n  - key: AWS_S3_CUSTOM_DOMAIN\n    scope: RUN_AND_BUILD_TIME\n    value: 'chibifire.sfo3.digitaloceanspaces.com '\n  - key: AWS_S3_REGION_NAME\n    scope: RUN_AND_BUILD_TIME\n    value: sfo3\n  - key: AWS_STORAGE_BUCKET_NAME\n    scope: RUN_AND_BUILD_TIME\n    value: chibifire\n  - key: AWS_SECRET_ACCESS_KEY\n    scope: RUN_AND_BUILD_TIME\n    type: SECRET\n    value: SECRETSECRETSECRET\n    scope: RUN_AND_BUILD_TIME\n    value: \"true\"\n  - key: SYNC_TEMPLATES_ON_STARTUP\n    scope: RUN_AND_BUILD_TIME\n    value: \"false\"\n  - key: PRIVATE_BACKEND_URL\n    scope: RUN_AND_BUILD_TIME\n    value: ${_self.PRIVATE_URL}\n  http_port: 80\n  image:\n    registry: baserow\n    registry_type: DOCKER_HUB\n    repository: baserow\n    tag: 1.10.2\n  instance_count: 1\n  instance_size_slug: basic-xs\n  name: baserow-baserow\n  routes:\n  - path: /\n\n\n\nPositive Consequences\nI can finally store things.\n\n\nNegative Consequences\nPay for the baserow service.\n\n\nOption graveyard\n\nRejected using premium saas from baserow\nRejected using airtable\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot a few lines of code, but fairly simple.\n\n\nIs there a reason why this should be core and done by us?\nI need to store things.\n\n\nReferences\n\nV-Sekai\nCreate digital ocean instructions\n\n\n\nLicense of the contribution\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20200729-entity-networking.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20200729-entity-networking.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Accepted: Adding Entity Networking to Groups",
+    "objectID": "decisions/20240622-gocd-agent-docker-image-update.html",
+    "href": "decisions/20240622-gocd-agent-docker-image-update.html",
+    "title": "Accepted: GoCD Agent Docker Image Update",
     "section": "",
-    "text": "A networking system is not a few lines of code."
+    "text": "We are currently using a GoCD Agent Docker image for our V-Sekai development environment. This Docker image contains all the necessary tools and libraries required for building our projects.\n\n\n\nThe GoCD Agent Docker image we are using is not up-to-date, which could potentially lead to compatibility issues, security vulnerabilities, and missed improvements from newer versions of the tools and libraries.\n\n\n\nWe propose to update all components within the GoCD Agent Docker image. This includes the base OS, installed libraries, and any other software included in the image.\n\n\n\nUpdating the GoCD Agent Docker image ensures that we are using the most recent and secure versions of our tools and libraries. It also allows us to take advantage of any new features or performance improvements that have been introduced.\n\n\n\nThere may be breaking changes in the newer versions of the tools and libraries, which could require modifications to our existing codebase.\n\n\n\nWe could choose not to update the GoCD Agent Docker image, but this could leave us vulnerable to known security issues and prevent us from utilizing improvements in the tools and libraries.\n\n\n\nThis proposal does not directly address infrequent use cases, as it is focused on maintaining an up-to-date development environment.\n\n\n\nThe updating process will be handled by the V-Sekai development team.\n\n\n\nStatus: Accepted \n\n\n\n\nV-Sekai development team\nfire\nlyuma\n\n\n\n\n\nV-Sekai\nDocker\nGoCD Agent\nUpdate\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20200729-entity-networking.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20200729-entity-networking.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Accepted: Adding Entity Networking to Groups",
+    "objectID": "decisions/20240622-gocd-agent-docker-image-update.html#the-context",
+    "href": "decisions/20240622-gocd-agent-docker-image-update.html#the-context",
+    "title": "Accepted: GoCD Agent Docker Image Update",
     "section": "",
-    "text": "Yes, this is the foundation of the protocol and the basic set of nodes and behavior upon which content will be created."
+    "text": "We are currently using a GoCD Agent Docker image for our V-Sekai development environment. This Docker image contains all the necessary tools and libraries required for building our projects."
   },
   {
-    "objectID": "decisions/20200729-entity-networking.html#references",
-    "href": "decisions/20200729-entity-networking.html#references",
-    "title": "Accepted: Adding Entity Networking to Groups",
+    "objectID": "decisions/20240622-gocd-agent-docker-image-update.html#the-problem-statement",
+    "href": "decisions/20240622-gocd-agent-docker-image-update.html#the-problem-statement",
+    "title": "Accepted: GoCD Agent Docker Image Update",
     "section": "",
-    "text": "Aldridge, David. “I Shot You First: networking the Gameplay of Halo: Reach”. GDC 2011. https://www.youtube.com/watch?v=h47zZrqjgLc\nFiedler, Glenn. “Networking for Physics Programmers”. GDC 2015. https://www.youtube.com/watch?v=Z9X4lysFr64\nFiedler, Glenn. “Networked Physics in Virtual Reality”. 2018-02-22. https://www.gafferongames.com/post/networked_physics_in_virtual_reality/\nRouwe, Jorrit. “Killzone Shadow Fall: Threading the Entity Update on PS4”. GDCEU 2014. https://archive.org/details/GDCEU2014Rouwe\nSaracen, text and voice discussions on Discord: search Discord for “entity networking” and “networking model”"
+    "text": "The GoCD Agent Docker image we are using is not up-to-date, which could potentially lead to compatibility issues, security vulnerabilities, and missed improvements from newer versions of the tools and libraries."
   },
   {
-    "objectID": "decisions/20200729-entity-networking.html#derivative-license",
-    "href": "decisions/20200729-entity-networking.html#derivative-license",
-    "title": "Accepted: Adding Entity Networking to Groups",
+    "objectID": "decisions/20240622-gocd-agent-docker-image-update.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240622-gocd-agent-docker-image-update.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Accepted: GoCD Agent Docker Image Update",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "We propose to update all components within the GoCD Agent Docker image. This includes the base OS, installed libraries, and any other software included in the image."
   },
   {
-    "objectID": "decisions/20220206-logging-notifications-from-discord.html",
-    "href": "decisions/20220206-logging-notifications-from-discord.html",
-    "title": "Proposed: Log change notifications using DiscordChatExporter",
+    "objectID": "decisions/20240622-gocd-agent-docker-image-update.html#the-benefits",
+    "href": "decisions/20240622-gocd-agent-docker-image-update.html#the-benefits",
+    "title": "Accepted: GoCD Agent Docker Image Update",
     "section": "",
-    "text": "Status: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nWe use discord to log changes. At any moment, Discord can disappear.\n\n\n\nUse DiscordChatExporter to export our change notifications.\n\n\n\n\ngenerate a bot key\nenter key\nselect channels to write to\nexport while being careful to be in utc.\n\n\n\n\n\nLogs can be created for notifications.\n\n\n\n\n\nNeed to avoid Discord selfbots\n\n\n\n\n\nOption: Current status.\nRejection Reason: Discord servers can be arbitrarily lost.\n\n\n\n\nNot a trivial amount of coding to log into Discord.\n\n\n\nWe are the ones designing and using Discord.\n\n\n\n\nDiscordChatExporter \n\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Updating the GoCD Agent Docker image ensures that we are using the most recent and secure versions of our tools and libraries. It also allows us to take advantage of any new features or performance improvements that have been introduced."
   },
   {
-    "objectID": "decisions/20220206-logging-notifications-from-discord.html#context-and-problem-statement",
-    "href": "decisions/20220206-logging-notifications-from-discord.html#context-and-problem-statement",
-    "title": "Proposed: Log change notifications using DiscordChatExporter",
+    "objectID": "decisions/20240622-gocd-agent-docker-image-update.html#the-downsides",
+    "href": "decisions/20240622-gocd-agent-docker-image-update.html#the-downsides",
+    "title": "Accepted: GoCD Agent Docker Image Update",
     "section": "",
-    "text": "We use discord to log changes. At any moment, Discord can disappear."
+    "text": "There may be breaking changes in the newer versions of the tools and libraries, which could require modifications to our existing codebase."
   },
   {
-    "objectID": "decisions/20220206-logging-notifications-from-discord.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20220206-logging-notifications-from-discord.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: Log change notifications using DiscordChatExporter",
+    "objectID": "decisions/20240622-gocd-agent-docker-image-update.html#the-road-not-taken",
+    "href": "decisions/20240622-gocd-agent-docker-image-update.html#the-road-not-taken",
+    "title": "Accepted: GoCD Agent Docker Image Update",
     "section": "",
-    "text": "Use DiscordChatExporter to export our change notifications."
+    "text": "We could choose not to update the GoCD Agent Docker image, but this could leave us vulnerable to known security issues and prevent us from utilizing improvements in the tools and libraries."
   },
   {
-    "objectID": "decisions/20220206-logging-notifications-from-discord.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20220206-logging-notifications-from-discord.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Log change notifications using DiscordChatExporter",
+    "objectID": "decisions/20240622-gocd-agent-docker-image-update.html#the-infrequent-use-case",
+    "href": "decisions/20240622-gocd-agent-docker-image-update.html#the-infrequent-use-case",
+    "title": "Accepted: GoCD Agent Docker Image Update",
     "section": "",
-    "text": "generate a bot key\nenter key\nselect channels to write to\nexport while being careful to be in utc."
+    "text": "This proposal does not directly address infrequent use cases, as it is focused on maintaining an up-to-date development environment."
   },
   {
-    "objectID": "decisions/20220206-logging-notifications-from-discord.html#positive-consequences",
-    "href": "decisions/20220206-logging-notifications-from-discord.html#positive-consequences",
-    "title": "Proposed: Log change notifications using DiscordChatExporter",
+    "objectID": "decisions/20240622-gocd-agent-docker-image-update.html#in-core-and-done-by-us",
+    "href": "decisions/20240622-gocd-agent-docker-image-update.html#in-core-and-done-by-us",
+    "title": "Accepted: GoCD Agent Docker Image Update",
     "section": "",
-    "text": "Logs can be created for notifications."
+    "text": "The updating process will be handled by the V-Sekai development team."
   },
   {
-    "objectID": "decisions/20220206-logging-notifications-from-discord.html#negative-consequences",
-    "href": "decisions/20220206-logging-notifications-from-discord.html#negative-consequences",
-    "title": "Proposed: Log change notifications using DiscordChatExporter",
+    "objectID": "decisions/20240622-gocd-agent-docker-image-update.html#status",
+    "href": "decisions/20240622-gocd-agent-docker-image-update.html#status",
+    "title": "Accepted: GoCD Agent Docker Image Update",
     "section": "",
-    "text": "Need to avoid Discord selfbots"
+    "text": "Status: Accepted"
   },
   {
-    "objectID": "decisions/20220206-logging-notifications-from-discord.html#option-graveyard",
-    "href": "decisions/20220206-logging-notifications-from-discord.html#option-graveyard",
-    "title": "Proposed: Log change notifications using DiscordChatExporter",
+    "objectID": "decisions/20240622-gocd-agent-docker-image-update.html#decision-makers",
+    "href": "decisions/20240622-gocd-agent-docker-image-update.html#decision-makers",
+    "title": "Accepted: GoCD Agent Docker Image Update",
     "section": "",
-    "text": "Option: Current status.\nRejection Reason: Discord servers can be arbitrarily lost."
+    "text": "V-Sekai development team\nfire\nlyuma"
   },
   {
-    "objectID": "decisions/20220206-logging-notifications-from-discord.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20220206-logging-notifications-from-discord.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Log change notifications using DiscordChatExporter",
+    "objectID": "decisions/20240622-gocd-agent-docker-image-update.html#tags",
+    "href": "decisions/20240622-gocd-agent-docker-image-update.html#tags",
+    "title": "Accepted: GoCD Agent Docker Image Update",
     "section": "",
-    "text": "Not a trivial amount of coding to log into Discord."
+    "text": "V-Sekai\nDocker\nGoCD Agent\nUpdate"
   },
   {
-    "objectID": "decisions/20220206-logging-notifications-from-discord.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20220206-logging-notifications-from-discord.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Log change notifications using DiscordChatExporter",
+    "objectID": "decisions/20240622-gocd-agent-docker-image-update.html#further-reading",
+    "href": "decisions/20240622-gocd-agent-docker-image-update.html#further-reading",
+    "title": "Accepted: GoCD Agent Docker Image Update",
     "section": "",
-    "text": "We are the ones designing and using Discord."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20220206-logging-notifications-from-discord.html#references",
-    "href": "decisions/20220206-logging-notifications-from-discord.html#references",
-    "title": "Proposed: Log change notifications using DiscordChatExporter",
+    "objectID": "decisions/20240706-motion-capture-bill-of-materials.html",
+    "href": "decisions/20240706-motion-capture-bill-of-materials.html",
+    "title": "Proposed: Maximum Streaming Bill of Materials Setup for Motion Capture",
     "section": "",
-    "text": "DiscordChatExporter"
+    "text": "In the realm of virtual reality (VR) and motion capture, having a comprehensive setup is crucial for achieving high-quality streaming and accurate motion tracking. This proposal outlines the maximum bill of materials required to set up an advanced motion capture system for VR streaming.\n\n\n\nDescribe a streaming bill of materials setup for motion capture.\n\n\n\n\n\n\n\n\n\n\n\n\nComponent\nModel/Specification\nQuantity\nDescription\n\n\n\n\nVR Headset\nHTCVive XR Elite\n1\nHigh-resolution VR headset\n\n\nControllers\nHTCVive XR Elite Controllers\n2\nHandheld motion controllers\n\n\nMotion Trackers\nVIVE Ultimate Trackers\n5\nTrackers for motion capture\n\n\nFacial Tracker\nVIVE Full Facial Tracker\n1\nTracker for capturing facial movements\n\n\nStreaming PC\nSteamVR Capable Wireless Streaming PC with RTX 4080\n1\nPC with RTX 4080 GPU capable of wireless streaming for SteamVR\n\n\nWiFi Router\nHigh-speed WiFi Router with Internet\n1\nRouter for wireless internet connectivity\n\n\nUSB-C Cable\n5m USB-C Cable from UGreen\n1\nCable for data transfer\n\n\nCharging Cable\nUSB-C to USB-C Charging Cable\n3\nCable for charging devices\n\n\nCharging Cable\nUSB-C to USB-A Charging Cable\n1\nCable for charging devices\n\n\nChest Strap\nEOZ VRChat Chest Strap\n1\nChest strap for VRChat\n\n\nPelvis Belt\nTrackStrap Pelvis Belt (VIVE Ultimate Tracker Edition)\n1\nPelvis belt for motion tracking\n\n\nFoot Straps\nEOZ VRChat Strap Version 2 (Left and Right)\n2\nFoot straps for VRChat\n\n\nTracker Dongle\nHTCVive Ultimate Tracker Dongle\n1\nDongle for connecting trackers\n\n\n\n\n\n\n\nHigh-Quality Streaming: The setup ensures high-resolution streaming with minimal latency.\nAccurate Motion Capture: Multiple trackers provide precise motion capture for various body parts.\nEnhanced User Experience: The combination of facial and motion trackers offers a more immersive VR experience.\n\n\n\n\n\nCost: The setup involves high-end components, which can be expensive.\nComplexity: Setting up and maintaining the system requires technical expertise.\nSpace Requirements: Adequate space is needed to use the motion capture system effectively.\n\n\n\n\nAlternative solutions such as using lower-end VR headsets or fewer motion trackers were considered but not chosen due to their limitations in providing high-quality streaming and accurate motion capture.\n\n\n\nInfrequent use cases include scenarios where only basic motion capture is needed, such as simple VR interactions without the need for full-body tracking or high-resolution streaming.\n\n\n\nThe V-Sekai development team will handle the integration and setup of the proposed components into the core system.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\nFire\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20220206-logging-notifications-from-discord.html#derivative-license",
-    "href": "decisions/20220206-logging-notifications-from-discord.html#derivative-license",
-    "title": "Proposed: Log change notifications using DiscordChatExporter",
+    "objectID": "decisions/20240706-motion-capture-bill-of-materials.html#the-context",
+    "href": "decisions/20240706-motion-capture-bill-of-materials.html#the-context",
+    "title": "Proposed: Maximum Streaming Bill of Materials Setup for Motion Capture",
     "section": "",
-    "text": "Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "In the realm of virtual reality (VR) and motion capture, having a comprehensive setup is crucial for achieving high-quality streaming and accurate motion tracking. This proposal outlines the maximum bill of materials required to set up an advanced motion capture system for VR streaming."
   },
   {
-    "objectID": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html",
-    "href": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html",
-    "title": "Proposed: Reduce Size Difference Between Capsules and Mesh Volume",
+    "objectID": "decisions/20240706-motion-capture-bill-of-materials.html#the-problem-statement",
+    "href": "decisions/20240706-motion-capture-bill-of-materials.html#the-problem-statement",
+    "title": "Proposed: Maximum Streaming Bill of Materials Setup for Motion Capture",
     "section": "",
-    "text": "Accurately fit capsules around bones in skinned skeleton meshes. The example provided involves a rectangle skinned by two bones, with each vertex influenced by up to 8 weights.\n\n\n\nThe goal is to minimize the size discrepancies between the capsules surrounding the bones and the actual volume defined by the skin mesh. This will be approached using the Minimum Deviation Flow problem in bidirected graphs (Bi-MDF).\n\n\n\n\n\n\nSkeleton: Represent each bone as a node in a graph.\nSkin Mesh: Each vertex of the mesh is also a node. Connect a bone to a vertex with an edge if the vertex is influenced by that bone, based on skin weights.\n\n\n\n\n\nThe objective is to minimize the size differences between the capsules (nodes) and the volume of the skin mesh. This is quantified using a cost function that measures the deviation from ideal capsule sizes.\n\n\n\n\nI have no idea.\n\n\n\n\n\nAccuracy: Improves the fit of capsules to the actual mesh, enhancing animation quality.\nEfficiency: Reduces computational overhead by focusing on significant discrepancies.\n\n\n\n\n\nComplexity: Implementing and tuning the Bi-MDF algorithm can be complex.\nDependency: Relies heavily on accurate weight assignments and initial conditions.\n\n\n\n\n\nAlternative methods such as direct geometric fitting or machine learning approaches were considered but not pursued due to their complexity and computational requirements.\n\n\n\n\n\nHandling cases where bones have minimal influence on any vertices, which might lead to underutilized algorithms and resources.\n\n\n\n\n\nThe development and integration of this feature are handled internally by the V-Sekai development team, ensuring it aligns with the core functionalities of the Godot Engine used for VR.\n\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\ncgg-bern/libSatsuma Exact and approximate solvers for minimum-cost-flow problems in bi-directed graphs.\n\nAI assistant Aria assisted with this article."
+    "text": "Describe a streaming bill of materials setup for motion capture."
   },
   {
-    "objectID": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#the-context",
-    "href": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#the-context",
-    "title": "Proposed: Reduce Size Difference Between Capsules and Mesh Volume",
+    "objectID": "decisions/20240706-motion-capture-bill-of-materials.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240706-motion-capture-bill-of-materials.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Maximum Streaming Bill of Materials Setup for Motion Capture",
     "section": "",
-    "text": "Accurately fit capsules around bones in skinned skeleton meshes. The example provided involves a rectangle skinned by two bones, with each vertex influenced by up to 8 weights."
+    "text": "Component\nModel/Specification\nQuantity\nDescription\n\n\n\n\nVR Headset\nHTCVive XR Elite\n1\nHigh-resolution VR headset\n\n\nControllers\nHTCVive XR Elite Controllers\n2\nHandheld motion controllers\n\n\nMotion Trackers\nVIVE Ultimate Trackers\n5\nTrackers for motion capture\n\n\nFacial Tracker\nVIVE Full Facial Tracker\n1\nTracker for capturing facial movements\n\n\nStreaming PC\nSteamVR Capable Wireless Streaming PC with RTX 4080\n1\nPC with RTX 4080 GPU capable of wireless streaming for SteamVR\n\n\nWiFi Router\nHigh-speed WiFi Router with Internet\n1\nRouter for wireless internet connectivity\n\n\nUSB-C Cable\n5m USB-C Cable from UGreen\n1\nCable for data transfer\n\n\nCharging Cable\nUSB-C to USB-C Charging Cable\n3\nCable for charging devices\n\n\nCharging Cable\nUSB-C to USB-A Charging Cable\n1\nCable for charging devices\n\n\nChest Strap\nEOZ VRChat Chest Strap\n1\nChest strap for VRChat\n\n\nPelvis Belt\nTrackStrap Pelvis Belt (VIVE Ultimate Tracker Edition)\n1\nPelvis belt for motion tracking\n\n\nFoot Straps\nEOZ VRChat Strap Version 2 (Left and Right)\n2\nFoot straps for VRChat\n\n\nTracker Dongle\nHTCVive Ultimate Tracker Dongle\n1\nDongle for connecting trackers"
   },
   {
-    "objectID": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#the-problem-statement",
-    "href": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#the-problem-statement",
-    "title": "Proposed: Reduce Size Difference Between Capsules and Mesh Volume",
+    "objectID": "decisions/20240706-motion-capture-bill-of-materials.html#the-benefits",
+    "href": "decisions/20240706-motion-capture-bill-of-materials.html#the-benefits",
+    "title": "Proposed: Maximum Streaming Bill of Materials Setup for Motion Capture",
     "section": "",
-    "text": "The goal is to minimize the size discrepancies between the capsules surrounding the bones and the actual volume defined by the skin mesh. This will be approached using the Minimum Deviation Flow problem in bidirected graphs (Bi-MDF)."
+    "text": "High-Quality Streaming: The setup ensures high-resolution streaming with minimal latency.\nAccurate Motion Capture: Multiple trackers provide precise motion capture for various body parts.\nEnhanced User Experience: The combination of facial and motion trackers offers a more immersive VR experience."
   },
   {
-    "objectID": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Reduce Size Difference Between Capsules and Mesh Volume",
+    "objectID": "decisions/20240706-motion-capture-bill-of-materials.html#the-downsides",
+    "href": "decisions/20240706-motion-capture-bill-of-materials.html#the-downsides",
+    "title": "Proposed: Maximum Streaming Bill of Materials Setup for Motion Capture",
     "section": "",
-    "text": "Skeleton: Represent each bone as a node in a graph.\nSkin Mesh: Each vertex of the mesh is also a node. Connect a bone to a vertex with an edge if the vertex is influenced by that bone, based on skin weights.\n\n\n\n\n\nThe objective is to minimize the size differences between the capsules (nodes) and the volume of the skin mesh. This is quantified using a cost function that measures the deviation from ideal capsule sizes.\n\n\n\n\nI have no idea."
+    "text": "Cost: The setup involves high-end components, which can be expensive.\nComplexity: Setting up and maintaining the system requires technical expertise.\nSpace Requirements: Adequate space is needed to use the motion capture system effectively."
   },
   {
-    "objectID": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#the-benefits",
-    "href": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#the-benefits",
-    "title": "Proposed: Reduce Size Difference Between Capsules and Mesh Volume",
+    "objectID": "decisions/20240706-motion-capture-bill-of-materials.html#the-road-not-taken",
+    "href": "decisions/20240706-motion-capture-bill-of-materials.html#the-road-not-taken",
+    "title": "Proposed: Maximum Streaming Bill of Materials Setup for Motion Capture",
     "section": "",
-    "text": "Accuracy: Improves the fit of capsules to the actual mesh, enhancing animation quality.\nEfficiency: Reduces computational overhead by focusing on significant discrepancies."
+    "text": "Alternative solutions such as using lower-end VR headsets or fewer motion trackers were considered but not chosen due to their limitations in providing high-quality streaming and accurate motion capture."
   },
   {
-    "objectID": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#the-downsides",
-    "href": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#the-downsides",
-    "title": "Proposed: Reduce Size Difference Between Capsules and Mesh Volume",
+    "objectID": "decisions/20240706-motion-capture-bill-of-materials.html#the-infrequent-use-case",
+    "href": "decisions/20240706-motion-capture-bill-of-materials.html#the-infrequent-use-case",
+    "title": "Proposed: Maximum Streaming Bill of Materials Setup for Motion Capture",
     "section": "",
-    "text": "Complexity: Implementing and tuning the Bi-MDF algorithm can be complex.\nDependency: Relies heavily on accurate weight assignments and initial conditions."
+    "text": "Infrequent use cases include scenarios where only basic motion capture is needed, such as simple VR interactions without the need for full-body tracking or high-resolution streaming."
   },
   {
-    "objectID": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#the-road-not-taken",
-    "href": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#the-road-not-taken",
-    "title": "Proposed: Reduce Size Difference Between Capsules and Mesh Volume",
+    "objectID": "decisions/20240706-motion-capture-bill-of-materials.html#in-core-and-done-by-us",
+    "href": "decisions/20240706-motion-capture-bill-of-materials.html#in-core-and-done-by-us",
+    "title": "Proposed: Maximum Streaming Bill of Materials Setup for Motion Capture",
     "section": "",
-    "text": "Alternative methods such as direct geometric fitting or machine learning approaches were considered but not pursued due to their complexity and computational requirements."
+    "text": "The V-Sekai development team will handle the integration and setup of the proposed components into the core system."
   },
   {
-    "objectID": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#the-infrequent-use-case",
-    "href": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#the-infrequent-use-case",
-    "title": "Proposed: Reduce Size Difference Between Capsules and Mesh Volume",
+    "objectID": "decisions/20240706-motion-capture-bill-of-materials.html#status",
+    "href": "decisions/20240706-motion-capture-bill-of-materials.html#status",
+    "title": "Proposed: Maximum Streaming Bill of Materials Setup for Motion Capture",
     "section": "",
-    "text": "Handling cases where bones have minimal influence on any vertices, which might lead to underutilized algorithms and resources."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#in-core-and-done-by-us",
-    "href": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#in-core-and-done-by-us",
-    "title": "Proposed: Reduce Size Difference Between Capsules and Mesh Volume",
+    "objectID": "decisions/20240706-motion-capture-bill-of-materials.html#decision-makers",
+    "href": "decisions/20240706-motion-capture-bill-of-materials.html#decision-makers",
+    "title": "Proposed: Maximum Streaming Bill of Materials Setup for Motion Capture",
     "section": "",
-    "text": "The development and integration of this feature are handled internally by the V-Sekai development team, ensuring it aligns with the core functionalities of the Godot Engine used for VR."
+    "text": "V-Sekai development team\nFire"
   },
   {
-    "objectID": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#status",
-    "href": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#status",
-    "title": "Proposed: Reduce Size Difference Between Capsules and Mesh Volume",
+    "objectID": "decisions/20240706-motion-capture-bill-of-materials.html#tags",
+    "href": "decisions/20240706-motion-capture-bill-of-materials.html#tags",
+    "title": "Proposed: Maximum Streaming Bill of Materials Setup for Motion Capture",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#decision-makers",
-    "href": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#decision-makers",
-    "title": "Proposed: Reduce Size Difference Between Capsules and Mesh Volume",
+    "objectID": "decisions/20240706-motion-capture-bill-of-materials.html#further-reading",
+    "href": "decisions/20240706-motion-capture-bill-of-materials.html#further-reading",
+    "title": "Proposed: Maximum Streaming Bill of Materials Setup for Motion Capture",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#tags",
-    "href": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#tags",
-    "title": "Proposed: Reduce Size Difference Between Capsules and Mesh Volume",
+    "objectID": "decisions/20240621-caption-photos-for-cicd.html",
+    "href": "decisions/20240621-caption-photos-for-cicd.html",
+    "title": "Proposed: Image Captioning Tool",
     "section": "",
-    "text": "V-Sekai"
+    "text": "In the V-Sekai project, we are developing a continuous integration and continuous delivery (CI/CD) tool for Meta Platform Inc.’s Virtual Reality OpenXR API headset simulator (Windows 11). A key feature of this tool is the ability to caption images.\n\n\n\nWe need to caption images for two main reasons:\n\nDebugging: Developers can quickly identify issues by reading the captions.\nDataset Creation: We can create a nominal vs anomaly dataset for visual anomaly detection.\n\n\n\n\nHere’s a Python script that uses the Gradio client to generate captions for images:\n# Copyright (c) 2019-2022 K. S. Ernest (iFire) Lee (fire)\n# SPDX-License-Identifier: MIT\n# pip3 install gradio_client\nfrom gradio_client import Client, handle_file\n\nfile_or_url_paths = [\"//192.168.1.72/share/Screenshot 2024-05-22 at 6.05.58 PM.png\"]\nclient = Client(\"gokaygokay/PaliGemma-PixelProse\")\n\nfor path in file_or_url_paths:\n    try:\n        result = client.predict(\n            image=handle_file(path),\n            api_name=\"/create_captions_rich\"\n        )\n        print(result)\n    except Exception as e:\n        print(f\"An error occurred while processing {path}: {e}\")\n\n\n\n\nImproved debugging process.\nFacilitates the creation of a dataset for visual anomaly detection.\n\n\n\n\n\nThe accuracy of the captions depends on the performance of the Gradio client.\n\n\n\n\n\nWe could have used other image captioning tools or libraries, but we chose Gradio due to its simplicity and ease of use.\n\n\n\n\n\nThis tool may not be useful when working with non-visual data or when debugging is not required.\n\n\n\n\n\nThis feature will be developed and maintained by the V-Sekai development team.\n\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - The GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n[https://github.com/V-Sekai-fire/character-rigging-anomaly-detection]\n[https://anomalib.readthedocs.io/en/v1.1.0/]\n[https://developer.oculus.com/documentation/native/xrsim-intro/]\n[https://github.com/V-Sekai-fire/cog-caption-image.git]\n[https://huggingface.co/spaces/gokaygokay/Florence-2]\n\nThis proposal was assisted by Aria, an AI assistant."
   },
   {
-    "objectID": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#further-reading",
-    "href": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#further-reading",
-    "title": "Proposed: Reduce Size Difference Between Capsules and Mesh Volume",
+    "objectID": "decisions/20240621-caption-photos-for-cicd.html#context",
+    "href": "decisions/20240621-caption-photos-for-cicd.html#context",
+    "title": "Proposed: Image Captioning Tool",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\ncgg-bern/libSatsuma Exact and approximate solvers for minimum-cost-flow problems in bi-directed graphs.\n\nAI assistant Aria assisted with this article."
+    "text": "In the V-Sekai project, we are developing a continuous integration and continuous delivery (CI/CD) tool for Meta Platform Inc.’s Virtual Reality OpenXR API headset simulator (Windows 11). A key feature of this tool is the ability to caption images."
   },
   {
-    "objectID": "decisions/20211005-test-google-mediapipe.html",
-    "href": "decisions/20211005-test-google-mediapipe.html",
-    "title": "Proposed: Test Google Mediapipe",
+    "objectID": "decisions/20240621-caption-photos-for-cicd.html#problem-statement",
+    "href": "decisions/20240621-caption-photos-for-cicd.html#problem-statement",
+    "title": "Proposed: Image Captioning Tool",
     "section": "",
-    "text": "We’re unable to test media pipe for iris.\n\n\n\nSetup github actions so we can package mediapipe to demo iris tracking.\n\n\n\n\nsetup cicd for linux to media pipe\nsetup cid for media pipe iris tracking\ncreate win10 support\n\n\n\nsudo apt install v4l-utils -y\nv4l2-ctl --all\n\n\n\nsudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade\ngit clone https://github.com/IntelRealSense/librealsense.git\ncd librealsense\nsudo apt-get install git libssl-dev libusb-1.0-0-dev pkg-config libgtk-3-dev -y\nsudo apt-get install libglfw3-dev libgl1-mesa-dev libglu1-mesa-dev -y\n./scripts/setup_udev_rules.sh\n# Use Postos 21.04 NVIDIA\nmkdir build && cd build\ncmake ../ -DBUILD_EXAMPLES=true -DCMAKE_BUILD_TYPE=Release\nsudo make uninstall && make clean && make && sudo make install -j`nproc`"
+    "text": "We need to caption images for two main reasons:\n\nDebugging: Developers can quickly identify issues by reading the captions.\nDataset Creation: We can create a nominal vs anomaly dataset for visual anomaly detection."
   },
   {
-    "objectID": "decisions/20211005-test-google-mediapipe.html#context-and-problem-statement",
-    "href": "decisions/20211005-test-google-mediapipe.html#context-and-problem-statement",
-    "title": "Proposed: Test Google Mediapipe",
+    "objectID": "decisions/20240621-caption-photos-for-cicd.html#proposal",
+    "href": "decisions/20240621-caption-photos-for-cicd.html#proposal",
+    "title": "Proposed: Image Captioning Tool",
     "section": "",
-    "text": "We’re unable to test media pipe for iris."
+    "text": "Here’s a Python script that uses the Gradio client to generate captions for images:\n# Copyright (c) 2019-2022 K. S. Ernest (iFire) Lee (fire)\n# SPDX-License-Identifier: MIT\n# pip3 install gradio_client\nfrom gradio_client import Client, handle_file\n\nfile_or_url_paths = [\"//192.168.1.72/share/Screenshot 2024-05-22 at 6.05.58 PM.png\"]\nclient = Client(\"gokaygokay/PaliGemma-PixelProse\")\n\nfor path in file_or_url_paths:\n    try:\n        result = client.predict(\n            image=handle_file(path),\n            api_name=\"/create_captions_rich\"\n        )\n        print(result)\n    except Exception as e:\n        print(f\"An error occurred while processing {path}: {e}\")"
   },
   {
-    "objectID": "decisions/20211005-test-google-mediapipe.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20211005-test-google-mediapipe.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: Test Google Mediapipe",
+    "objectID": "decisions/20240621-caption-photos-for-cicd.html#benefits",
+    "href": "decisions/20240621-caption-photos-for-cicd.html#benefits",
+    "title": "Proposed: Image Captioning Tool",
     "section": "",
-    "text": "Setup github actions so we can package mediapipe to demo iris tracking."
+    "text": "Improved debugging process.\nFacilitates the creation of a dataset for visual anomaly detection."
   },
   {
-    "objectID": "decisions/20211005-test-google-mediapipe.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20211005-test-google-mediapipe.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Test Google Mediapipe",
+    "objectID": "decisions/20240621-caption-photos-for-cicd.html#downsides",
+    "href": "decisions/20240621-caption-photos-for-cicd.html#downsides",
+    "title": "Proposed: Image Captioning Tool",
     "section": "",
-    "text": "setup cicd for linux to media pipe\nsetup cid for media pipe iris tracking\ncreate win10 support\n\n\n\nsudo apt install v4l-utils -y\nv4l2-ctl --all\n\n\n\nsudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade\ngit clone https://github.com/IntelRealSense/librealsense.git\ncd librealsense\nsudo apt-get install git libssl-dev libusb-1.0-0-dev pkg-config libgtk-3-dev -y\nsudo apt-get install libglfw3-dev libgl1-mesa-dev libglu1-mesa-dev -y\n./scripts/setup_udev_rules.sh\n# Use Postos 21.04 NVIDIA\nmkdir build && cd build\ncmake ../ -DBUILD_EXAMPLES=true -DCMAKE_BUILD_TYPE=Release\nsudo make uninstall && make clean && make && sudo make install -j`nproc`"
-  },
-  {
-    "objectID": "decisions/20211005-test-google-mediapipe.html#positive-consequences",
-    "href": "decisions/20211005-test-google-mediapipe.html#positive-consequences",
-    "title": "Proposed: Test Google Mediapipe",
-    "section": "Positive Consequences ",
-    "text": "Positive Consequences \nAble to mocap faces.\nAble to use the human body as vr controllers."
+    "text": "The accuracy of the captions depends on the performance of the Gradio client."
   },
   {
-    "objectID": "decisions/20211005-test-google-mediapipe.html#negative-consequences",
-    "href": "decisions/20211005-test-google-mediapipe.html#negative-consequences",
-    "title": "Proposed: Test Google Mediapipe",
-    "section": "Negative Consequences ",
-    "text": "Negative Consequences \nNo response"
+    "objectID": "decisions/20240621-caption-photos-for-cicd.html#road-not-taken",
+    "href": "decisions/20240621-caption-photos-for-cicd.html#road-not-taken",
+    "title": "Proposed: Image Captioning Tool",
+    "section": "",
+    "text": "We could have used other image captioning tools or libraries, but we chose Gradio due to its simplicity and ease of use."
   },
   {
-    "objectID": "decisions/20211005-test-google-mediapipe.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20211005-test-google-mediapipe.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Test Google Mediapipe",
-    "section": "If this enhancement will not be used often, can it be worked around with a few lines of script?",
-    "text": "If this enhancement will not be used often, can it be worked around with a few lines of script?\nPose estimation is interesting and we have someone who wants to collaborate."
+    "objectID": "decisions/20240621-caption-photos-for-cicd.html#infrequent-use-case",
+    "href": "decisions/20240621-caption-photos-for-cicd.html#infrequent-use-case",
+    "title": "Proposed: Image Captioning Tool",
+    "section": "",
+    "text": "This tool may not be useful when working with non-visual data or when debugging is not required."
   },
   {
-    "objectID": "decisions/20211005-test-google-mediapipe.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20211005-test-google-mediapipe.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Test Google Mediapipe",
-    "section": "Is there a reason why this should be core and done by us?",
-    "text": "Is there a reason why this should be core and done by us?\nNo response"
+    "objectID": "decisions/20240621-caption-photos-for-cicd.html#in-core-and-done-by-us",
+    "href": "decisions/20240621-caption-photos-for-cicd.html#in-core-and-done-by-us",
+    "title": "Proposed: Image Captioning Tool",
+    "section": "",
+    "text": "This feature will be developed and maintained by the V-Sekai development team."
   },
   {
-    "objectID": "decisions/20211005-test-google-mediapipe.html#references",
-    "href": "decisions/20211005-test-google-mediapipe.html#references",
-    "title": "Proposed: Test Google Mediapipe",
-    "section": "References ",
-    "text": "References \n\nhttps://google.github.io/mediapipe/getting_started/hello_world_cpp.html\nhttps://google.github.io/mediapipe/getting_started/cpp.html\nhttps://google.github.io/mediapipe/solutions/iris.html\nhttps://github.com/google/mediapipe/issues/1530\nhttps://github.com/V-Sekai/mediapipe"
+    "objectID": "decisions/20240621-caption-photos-for-cicd.html#status",
+    "href": "decisions/20240621-caption-photos-for-cicd.html#status",
+    "title": "Proposed: Image Captioning Tool",
+    "section": "",
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20211005-test-google-mediapipe.html#derivative-license",
-    "href": "decisions/20211005-test-google-mediapipe.html#derivative-license",
-    "title": "Proposed: Test Google Mediapipe",
-    "section": "Derivative License",
-    "text": "Derivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "objectID": "decisions/20240621-caption-photos-for-cicd.html#decision-makers",
+    "href": "decisions/20240621-caption-photos-for-cicd.html#decision-makers",
+    "title": "Proposed: Image Captioning Tool",
+    "section": "",
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20231228-v-sekai-slogan.html",
-    "href": "decisions/20231228-v-sekai-slogan.html",
-    "title": "Proposed: V-Sekai: Gateways to Virtual Worlds",
+    "objectID": "decisions/20240621-caption-photos-for-cicd.html#tags",
+    "href": "decisions/20240621-caption-photos-for-cicd.html#tags",
+    "title": "Proposed: Image Captioning Tool",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, Slogan, Virtual Reality, VR\n\n\n\n\nV-Sekai is a project in the realm of virtual reality. Our aim is to create immersive and interactive virtual worlds that offer users an awesome experience.\n\n\n\nIt’s important to have a slogan that encapsulates our vision and mission. It should be catchy, memorable, and reflective of what we do.\n\n\n\nWe propose the slogan: V-Sekai: Gateways to Virtual Worlds\nThis slogan succinctly communicates our goal of providing access to expansive virtual realities.\n\n\n\nThe proposed slogan is concise, catchy, and directly related to our work. It emphasizes our role as a gateway to new, immersive experiences.\n\n\n\nThe term “Virtual Worlds” might be too broad or vague for some people, potentially leading to misunderstandings about our specific services.\n\n\n\nAlternative slogans were considered, such as “V-Sekai: Forging Gateways to Virtual Worlds”, but they didn’t convey our message as effectively.\n\n\n\nFor those unfamiliar with the concept of virtual reality, the slogan might require further explanation.\n\n\n\nYes, this proposal was created internally by the V-Sekai team with assistance from AI assistant Aria.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\nVket 2023: Tram Ride\n\nAI assistant Aria assisted with this article."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20231228-v-sekai-slogan.html#metadata",
-    "href": "decisions/20231228-v-sekai-slogan.html#metadata",
-    "title": "Proposed: V-Sekai: Gateways to Virtual Worlds",
+    "objectID": "decisions/20240621-caption-photos-for-cicd.html#further-reading",
+    "href": "decisions/20240621-caption-photos-for-cicd.html#further-reading",
+    "title": "Proposed: Image Captioning Tool",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, Slogan, Virtual Reality, VR"
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - The GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n[https://github.com/V-Sekai-fire/character-rigging-anomaly-detection]\n[https://anomalib.readthedocs.io/en/v1.1.0/]\n[https://developer.oculus.com/documentation/native/xrsim-intro/]\n[https://github.com/V-Sekai-fire/cog-caption-image.git]\n[https://huggingface.co/spaces/gokaygokay/Florence-2]\n\nThis proposal was assisted by Aria, an AI assistant."
   },
   {
-    "objectID": "decisions/20231228-v-sekai-slogan.html#the-backdrop",
-    "href": "decisions/20231228-v-sekai-slogan.html#the-backdrop",
-    "title": "Proposed: V-Sekai: Gateways to Virtual Worlds",
+    "objectID": "decisions/20240330-bitnami-rancher-helm-catalog.html",
+    "href": "decisions/20240330-bitnami-rancher-helm-catalog.html",
+    "title": "Proposed: Installing Helm Chart from a Git Repository using Rancher",
     "section": "",
-    "text": "V-Sekai is a project in the realm of virtual reality. Our aim is to create immersive and interactive virtual worlds that offer users an awesome experience."
+    "text": "Rancher is an open-source platform for managing Kubernetes at scale. It provides a user-friendly interface for deploying, scaling and managing applications on top of Kubernetes.\n\n\n\nYou want to install a Helm chart from a specific location, in this case, a Git repository: https://charts.bitnami.com/bitnami, using Rancher.\n\n\n\nRancher does not directly support installing Helm charts from a Git repository. However, you can add the Git repository as a catalog in Rancher, and then use Rancher’s UI to deploy the chart.\nHere’s how you can do it:\n\nNavigate to the Rancher UI.\nGo to Global -&gt; Catalogs.\nClick on “Add Catalog”, fill in the details:\n\nName: Give your catalog a name.\nURL: Enter the URL of your Git repository (https://charts.bitnami.com/bitnami).\nBranch: Specify the branch to use (usually master or main).\n\nClick on “Create”.\nNow, you can navigate to your project, click on “Apps” -&gt; “Launch”, and you should see your newly added catalog. You can select the chart you want to install and follow the prompts.\n\n\n\n\nThis method allows you to manage and deploy Helm charts directly from the Rancher UI, providing a more user-friendly way to handle deployments.\n\n\n\nThe main downside is that this method requires manual setup in the Rancher UI, which might not be ideal for automated workflows.\n\n\n\nAn alternative approach would be to clone the Git repository locally, package the chart into a .tgz file, and upload it directly to Rancher.\n\n\n\nThis approach is particularly useful when you want to manage your Helm charts and deployments through a user-friendly interface, rather than dealing with command-line tools.\n\n\n\nThis solution is based on the core functionality provided by Rancher and does not require any additional tools or services.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\nbitnami/charts\n\nThis article was assisted by Aria, your AI assistant."
   },
   {
-    "objectID": "decisions/20231228-v-sekai-slogan.html#the-challenge",
-    "href": "decisions/20231228-v-sekai-slogan.html#the-challenge",
-    "title": "Proposed: V-Sekai: Gateways to Virtual Worlds",
+    "objectID": "decisions/20240330-bitnami-rancher-helm-catalog.html#context",
+    "href": "decisions/20240330-bitnami-rancher-helm-catalog.html#context",
+    "title": "Proposed: Installing Helm Chart from a Git Repository using Rancher",
     "section": "",
-    "text": "It’s important to have a slogan that encapsulates our vision and mission. It should be catchy, memorable, and reflective of what we do."
+    "text": "Rancher is an open-source platform for managing Kubernetes at scale. It provides a user-friendly interface for deploying, scaling and managing applications on top of Kubernetes."
   },
   {
-    "objectID": "decisions/20231228-v-sekai-slogan.html#the-strategy",
-    "href": "decisions/20231228-v-sekai-slogan.html#the-strategy",
-    "title": "Proposed: V-Sekai: Gateways to Virtual Worlds",
+    "objectID": "decisions/20240330-bitnami-rancher-helm-catalog.html#problem-statement",
+    "href": "decisions/20240330-bitnami-rancher-helm-catalog.html#problem-statement",
+    "title": "Proposed: Installing Helm Chart from a Git Repository using Rancher",
     "section": "",
-    "text": "We propose the slogan: V-Sekai: Gateways to Virtual Worlds\nThis slogan succinctly communicates our goal of providing access to expansive virtual realities."
+    "text": "You want to install a Helm chart from a specific location, in this case, a Git repository: https://charts.bitnami.com/bitnami, using Rancher."
   },
   {
-    "objectID": "decisions/20231228-v-sekai-slogan.html#the-upside",
-    "href": "decisions/20231228-v-sekai-slogan.html#the-upside",
-    "title": "Proposed: V-Sekai: Gateways to Virtual Worlds",
+    "objectID": "decisions/20240330-bitnami-rancher-helm-catalog.html#solution",
+    "href": "decisions/20240330-bitnami-rancher-helm-catalog.html#solution",
+    "title": "Proposed: Installing Helm Chart from a Git Repository using Rancher",
     "section": "",
-    "text": "The proposed slogan is concise, catchy, and directly related to our work. It emphasizes our role as a gateway to new, immersive experiences."
+    "text": "Rancher does not directly support installing Helm charts from a Git repository. However, you can add the Git repository as a catalog in Rancher, and then use Rancher’s UI to deploy the chart.\nHere’s how you can do it:\n\nNavigate to the Rancher UI.\nGo to Global -&gt; Catalogs.\nClick on “Add Catalog”, fill in the details:\n\nName: Give your catalog a name.\nURL: Enter the URL of your Git repository (https://charts.bitnami.com/bitnami).\nBranch: Specify the branch to use (usually master or main).\n\nClick on “Create”.\nNow, you can navigate to your project, click on “Apps” -&gt; “Launch”, and you should see your newly added catalog. You can select the chart you want to install and follow the prompts."
   },
   {
-    "objectID": "decisions/20231228-v-sekai-slogan.html#the-downside",
-    "href": "decisions/20231228-v-sekai-slogan.html#the-downside",
-    "title": "Proposed: V-Sekai: Gateways to Virtual Worlds",
+    "objectID": "decisions/20240330-bitnami-rancher-helm-catalog.html#benefits",
+    "href": "decisions/20240330-bitnami-rancher-helm-catalog.html#benefits",
+    "title": "Proposed: Installing Helm Chart from a Git Repository using Rancher",
     "section": "",
-    "text": "The term “Virtual Worlds” might be too broad or vague for some people, potentially leading to misunderstandings about our specific services."
+    "text": "This method allows you to manage and deploy Helm charts directly from the Rancher UI, providing a more user-friendly way to handle deployments."
   },
   {
-    "objectID": "decisions/20231228-v-sekai-slogan.html#the-road-not-taken",
-    "href": "decisions/20231228-v-sekai-slogan.html#the-road-not-taken",
-    "title": "Proposed: V-Sekai: Gateways to Virtual Worlds",
+    "objectID": "decisions/20240330-bitnami-rancher-helm-catalog.html#downsides",
+    "href": "decisions/20240330-bitnami-rancher-helm-catalog.html#downsides",
+    "title": "Proposed: Installing Helm Chart from a Git Repository using Rancher",
     "section": "",
-    "text": "Alternative slogans were considered, such as “V-Sekai: Forging Gateways to Virtual Worlds”, but they didn’t convey our message as effectively."
+    "text": "The main downside is that this method requires manual setup in the Rancher UI, which might not be ideal for automated workflows."
   },
   {
-    "objectID": "decisions/20231228-v-sekai-slogan.html#the-infrequent-use-case",
-    "href": "decisions/20231228-v-sekai-slogan.html#the-infrequent-use-case",
-    "title": "Proposed: V-Sekai: Gateways to Virtual Worlds",
+    "objectID": "decisions/20240330-bitnami-rancher-helm-catalog.html#the-road-not-taken",
+    "href": "decisions/20240330-bitnami-rancher-helm-catalog.html#the-road-not-taken",
+    "title": "Proposed: Installing Helm Chart from a Git Repository using Rancher",
     "section": "",
-    "text": "For those unfamiliar with the concept of virtual reality, the slogan might require further explanation."
+    "text": "An alternative approach would be to clone the Git repository locally, package the chart into a .tgz file, and upload it directly to Rancher."
   },
   {
-    "objectID": "decisions/20231228-v-sekai-slogan.html#in-core-and-done-by-us",
-    "href": "decisions/20231228-v-sekai-slogan.html#in-core-and-done-by-us",
-    "title": "Proposed: V-Sekai: Gateways to Virtual Worlds",
+    "objectID": "decisions/20240330-bitnami-rancher-helm-catalog.html#infrequent-use-case",
+    "href": "decisions/20240330-bitnami-rancher-helm-catalog.html#infrequent-use-case",
+    "title": "Proposed: Installing Helm Chart from a Git Repository using Rancher",
     "section": "",
-    "text": "Yes, this proposal was created internally by the V-Sekai team with assistance from AI assistant Aria."
+    "text": "This approach is particularly useful when you want to manage your Helm charts and deployments through a user-friendly interface, rather than dealing with command-line tools."
   },
   {
-    "objectID": "decisions/20231228-v-sekai-slogan.html#further-reading",
-    "href": "decisions/20231228-v-sekai-slogan.html#further-reading",
-    "title": "Proposed: V-Sekai: Gateways to Virtual Worlds",
+    "objectID": "decisions/20240330-bitnami-rancher-helm-catalog.html#in-core-and-done-by-us",
+    "href": "decisions/20240330-bitnami-rancher-helm-catalog.html#in-core-and-done-by-us",
+    "title": "Proposed: Installing Helm Chart from a Git Repository using Rancher",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\nVket 2023: Tram Ride\n\nAI assistant Aria assisted with this article."
+    "text": "This solution is based on the core functionality provided by Rancher and does not require any additional tools or services."
   },
   {
-    "objectID": "decisions/20220215-uro-deployment-process.html",
-    "href": "decisions/20220215-uro-deployment-process.html",
-    "title": "Proposed: To deploy backend services like Uro safely use a defined process",
+    "objectID": "decisions/20240330-bitnami-rancher-helm-catalog.html#status",
+    "href": "decisions/20240330-bitnami-rancher-helm-catalog.html#status",
+    "title": "Proposed: Installing Helm Chart from a Git Repository using Rancher",
     "section": "",
-    "text": "Status: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nWe need a process for deploying Uro and other backend services safely\n\n\n\nCommit code to uro sandbox branch\n- GoCD job creates uro-sandbox docker image\n- docker image is auto deployed to sandbox\nPR merges code to uro main branch\n- GoCD job creates uro docker image\n- docker image is auto deployed to staging (A/B)\n- manual interface to swap staging and live branch\n\n\n\nNot done yet. Probably relies on a custom Elixir service in Kubernetes using Role-Based Access Control, so it can automatically change services:\nhttps://kubernetes.io/docs/reference/access-authn-authz/rbac/\n\n\n\n\n[e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]\n\n\n\n\n\n[e.g., compromising quality attribute, follow-up decisions required, …]\n\n[this section can be repeated for each option if more than one option is open for consideration]\n\n\n\n\nOption: \nRejection Reason: \n\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\n\n\n\nIs there a reason why this should be core and done by us?\n\n\n\n\nLink type \n\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20220215-uro-deployment-process.html#context-and-problem-statement",
-    "href": "decisions/20220215-uro-deployment-process.html#context-and-problem-statement",
-    "title": "Proposed: To deploy backend services like Uro safely use a defined process",
+    "objectID": "decisions/20240330-bitnami-rancher-helm-catalog.html#decision-makers",
+    "href": "decisions/20240330-bitnami-rancher-helm-catalog.html#decision-makers",
+    "title": "Proposed: Installing Helm Chart from a Git Repository using Rancher",
     "section": "",
-    "text": "We need a process for deploying Uro and other backend services safely"
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20220215-uro-deployment-process.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20220215-uro-deployment-process.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: To deploy backend services like Uro safely use a defined process",
+    "objectID": "decisions/20240330-bitnami-rancher-helm-catalog.html#tags",
+    "href": "decisions/20240330-bitnami-rancher-helm-catalog.html#tags",
+    "title": "Proposed: Installing Helm Chart from a Git Repository using Rancher",
     "section": "",
-    "text": "Commit code to uro sandbox branch\n- GoCD job creates uro-sandbox docker image\n- docker image is auto deployed to sandbox\nPR merges code to uro main branch\n- GoCD job creates uro docker image\n- docker image is auto deployed to staging (A/B)\n- manual interface to swap staging and live branch"
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20220215-uro-deployment-process.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20220215-uro-deployment-process.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: To deploy backend services like Uro safely use a defined process",
+    "objectID": "decisions/20240330-bitnami-rancher-helm-catalog.html#further-reading",
+    "href": "decisions/20240330-bitnami-rancher-helm-catalog.html#further-reading",
+    "title": "Proposed: Installing Helm Chart from a Git Repository using Rancher",
     "section": "",
-    "text": "Not done yet. Probably relies on a custom Elixir service in Kubernetes using Role-Based Access Control, so it can automatically change services:\nhttps://kubernetes.io/docs/reference/access-authn-authz/rbac/"
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\nbitnami/charts\n\nThis article was assisted by Aria, your AI assistant."
   },
   {
-    "objectID": "decisions/20220215-uro-deployment-process.html#positive-consequences",
-    "href": "decisions/20220215-uro-deployment-process.html#positive-consequences",
-    "title": "Proposed: To deploy backend services like Uro safely use a defined process",
+    "objectID": "decisions/20230716-enhancing-avatar-creation-process-02-advanced.html",
+    "href": "decisions/20230716-enhancing-avatar-creation-process-02-advanced.html",
+    "title": "Proposed: Enhancing Avatar Creation Process in V-Sekai Advanced",
     "section": "",
-    "text": "[e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]"
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nV-Sekai currently has limitations when it comes to creating avatars with specific features and customizations. This can be a hindrance for users who want to have more control over the appearance of their avatars. To address this, we propose an enhancement that introduces various tools and techniques to overcome these limitations and provide a more comprehensive avatar creation process.\n\n\n\nHere is a list of raw processes to be broken down.\n\n\n\nSource: The source will provide the initial avatar model and any additional assets required. The input mime type for the source could be application/gltf+json or model/gltf+json if the avatar is in GLTF format, or image/png or image/svg+xml if the avatar is provided as a 2D image.\nFilter: The filter will handle all the customization steps mentioned above. It will take the input from the source and apply the necessary modifications to create the desired avatar. The input mime type for the filter would be the same as the output mime type of the source, depending on whether the avatar is in GLTF format or represented as an image.\nSink: The sink will receive the customized avatar from the filter and store it as the final output. For this project, the sink should support both PNG and SVG images for 2D avatars, and GLTF for 3D avatars. Therefore, the output mime types for the sink would be image/png or image/svg+xml for 2D avatars, and application/gltf+json or model/gltf+json for 3D avatars.\n\nNote: To avoid lossy formats, we are using PNG or SVG for 2D images and GLTF for 3D formats. PNG and SVG are lossless image formats, while GLTF is a lossless 3D format that preserves the fidelity of the avatar model.\n\n\n\nHere are the converted inputs and outputs in the xstate format for each step:\n\nImporting the avatar into Godot Engine and “Project Mirage”:\n\nInput: .vrm file\nOutput: .vrm file\n\nRefining the imported avatar:\n\nInput: .vrm file\nOutput: .vrm file\n\nConverting spring bone to physical simulation bones and colliders:\n\nInput: .vrm file\nOutput: assetpackage file\n\nAddressing painting errors:\n\nInput: .vrm file\nOutput: .vrm file\n\nChoosing a material:\n\nInput: .vrm file\nOutput: .vrm file\n\nResolving issues with materials and bones:\n\nInput: .vrm file\nOutput: .vrm file\n\nCorrecting colors and addressing pleated folds:\n\nInput: .vrm file\nOutput: .vrm file\n\nCreating complex geometric structures:\n\nInput: .vrm file\nOutput: .vrm file\n\nUtilizing Vroid Hub’s hair painter and mesh generator:\n\n\nInput: .vrm file\nOutput: .vrm enhanced data\n\n\nAdding facial expressions for motion capture:\n\n\nInput: .vrm file\nOutput: .gltf motion capture data\n\n\nSetting up motion capture:\n\n\nInput: .vrm file\nOutput: vrm animations data stored as .gltf.\n\n\n\n\n\n\nUsers will be able to create highly customizable avatars with specific features.\nThe avatar creation process will be enhanced with a variety of tools and techniques.\nDetailed customization of colors, clothing, accessories, and facial expressions will be possible.\nMotion capture capabilities can be integrated for more realistic animations.\n\n\n\n\n\nThe implementation process is complex and may require advanced technical skills from users.\nSome steps, like creating a 3D model of the back of the avatar, may not always be successful.\nPainting errors and other imperfections may remain in the final avatar.\n\n\n\n\n\nExcessive complexity or technical requirements: We want the avatar creation process to be user-friendly and accessible to a wide range of users, so any options that require advanced technical skills or have excessively complex customization controls will not be included.\n\n\n\n\nNo, the proposed enhancement involves a multi-step process that cannot be easily replicated with just a few lines of script.\n\n\n\nThe proposed enhancement addresses the limitations in V-Sekai’s avatar creation process, providing users with a comprehensive solution for creating highly customizable avatars. By implementing these tools and techniques within the platform, V-Sekai can offer a more robust and user-friendly experience for its community.\n\n\n\n\nV-Sekai"
   },
   {
-    "objectID": "decisions/20220215-uro-deployment-process.html#negative-consequences",
-    "href": "decisions/20220215-uro-deployment-process.html#negative-consequences",
-    "title": "Proposed: To deploy backend services like Uro safely use a defined process",
+    "objectID": "decisions/20230716-enhancing-avatar-creation-process-02-advanced.html#metadata",
+    "href": "decisions/20230716-enhancing-avatar-creation-process-02-advanced.html#metadata",
+    "title": "Proposed: Enhancing Avatar Creation Process in V-Sekai Advanced",
     "section": "",
-    "text": "[e.g., compromising quality attribute, follow-up decisions required, …]\n\n[this section can be repeated for each option if more than one option is open for consideration]"
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20220215-uro-deployment-process.html#option-graveyard",
-    "href": "decisions/20220215-uro-deployment-process.html#option-graveyard",
-    "title": "Proposed: To deploy backend services like Uro safely use a defined process",
+    "objectID": "decisions/20230716-enhancing-avatar-creation-process-02-advanced.html#context-and-problem-statement",
+    "href": "decisions/20230716-enhancing-avatar-creation-process-02-advanced.html#context-and-problem-statement",
+    "title": "Proposed: Enhancing Avatar Creation Process in V-Sekai Advanced",
     "section": "",
-    "text": "Option: \nRejection Reason:"
+    "text": "V-Sekai currently has limitations when it comes to creating avatars with specific features and customizations. This can be a hindrance for users who want to have more control over the appearance of their avatars. To address this, we propose an enhancement that introduces various tools and techniques to overcome these limitations and provide a more comprehensive avatar creation process."
   },
   {
-    "objectID": "decisions/20220215-uro-deployment-process.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20220215-uro-deployment-process.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: To deploy backend services like Uro safely use a defined process",
+    "objectID": "decisions/20230716-enhancing-avatar-creation-process-02-advanced.html#proposed-solution",
+    "href": "decisions/20230716-enhancing-avatar-creation-process-02-advanced.html#proposed-solution",
+    "title": "Proposed: Enhancing Avatar Creation Process in V-Sekai Advanced",
     "section": "",
-    "text": "If this enhancement will not be used often, can it be worked around with a few lines of script?"
+    "text": "Here is a list of raw processes to be broken down.\n\n\n\nSource: The source will provide the initial avatar model and any additional assets required. The input mime type for the source could be application/gltf+json or model/gltf+json if the avatar is in GLTF format, or image/png or image/svg+xml if the avatar is provided as a 2D image.\nFilter: The filter will handle all the customization steps mentioned above. It will take the input from the source and apply the necessary modifications to create the desired avatar. The input mime type for the filter would be the same as the output mime type of the source, depending on whether the avatar is in GLTF format or represented as an image.\nSink: The sink will receive the customized avatar from the filter and store it as the final output. For this project, the sink should support both PNG and SVG images for 2D avatars, and GLTF for 3D avatars. Therefore, the output mime types for the sink would be image/png or image/svg+xml for 2D avatars, and application/gltf+json or model/gltf+json for 3D avatars.\n\nNote: To avoid lossy formats, we are using PNG or SVG for 2D images and GLTF for 3D formats. PNG and SVG are lossless image formats, while GLTF is a lossless 3D format that preserves the fidelity of the avatar model.\n\n\n\nHere are the converted inputs and outputs in the xstate format for each step:\n\nImporting the avatar into Godot Engine and “Project Mirage”:\n\nInput: .vrm file\nOutput: .vrm file\n\nRefining the imported avatar:\n\nInput: .vrm file\nOutput: .vrm file\n\nConverting spring bone to physical simulation bones and colliders:\n\nInput: .vrm file\nOutput: assetpackage file\n\nAddressing painting errors:\n\nInput: .vrm file\nOutput: .vrm file\n\nChoosing a material:\n\nInput: .vrm file\nOutput: .vrm file\n\nResolving issues with materials and bones:\n\nInput: .vrm file\nOutput: .vrm file\n\nCorrecting colors and addressing pleated folds:\n\nInput: .vrm file\nOutput: .vrm file\n\nCreating complex geometric structures:\n\nInput: .vrm file\nOutput: .vrm file\n\nUtilizing Vroid Hub’s hair painter and mesh generator:\n\n\nInput: .vrm file\nOutput: .vrm enhanced data\n\n\nAdding facial expressions for motion capture:\n\n\nInput: .vrm file\nOutput: .gltf motion capture data\n\n\nSetting up motion capture:\n\n\nInput: .vrm file\nOutput: vrm animations data stored as .gltf."
   },
   {
-    "objectID": "decisions/20220215-uro-deployment-process.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20220215-uro-deployment-process.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: To deploy backend services like Uro safely use a defined process",
+    "objectID": "decisions/20230716-enhancing-avatar-creation-process-02-advanced.html#positive-consequences",
+    "href": "decisions/20230716-enhancing-avatar-creation-process-02-advanced.html#positive-consequences",
+    "title": "Proposed: Enhancing Avatar Creation Process in V-Sekai Advanced",
     "section": "",
-    "text": "Is there a reason why this should be core and done by us?"
+    "text": "Users will be able to create highly customizable avatars with specific features.\nThe avatar creation process will be enhanced with a variety of tools and techniques.\nDetailed customization of colors, clothing, accessories, and facial expressions will be possible.\nMotion capture capabilities can be integrated for more realistic animations."
   },
   {
-    "objectID": "decisions/20220215-uro-deployment-process.html#references",
-    "href": "decisions/20220215-uro-deployment-process.html#references",
-    "title": "Proposed: To deploy backend services like Uro safely use a defined process",
+    "objectID": "decisions/20230716-enhancing-avatar-creation-process-02-advanced.html#negative-consequences",
+    "href": "decisions/20230716-enhancing-avatar-creation-process-02-advanced.html#negative-consequences",
+    "title": "Proposed: Enhancing Avatar Creation Process in V-Sekai Advanced",
     "section": "",
-    "text": "Link type"
+    "text": "The implementation process is complex and may require advanced technical skills from users.\nSome steps, like creating a 3D model of the back of the avatar, may not always be successful.\nPainting errors and other imperfections may remain in the final avatar."
   },
   {
-    "objectID": "decisions/20220215-uro-deployment-process.html#derivative-license",
-    "href": "decisions/20220215-uro-deployment-process.html#derivative-license",
-    "title": "Proposed: To deploy backend services like Uro safely use a defined process",
+    "objectID": "decisions/20230716-enhancing-avatar-creation-process-02-advanced.html#option-graveyard",
+    "href": "decisions/20230716-enhancing-avatar-creation-process-02-advanced.html#option-graveyard",
+    "title": "Proposed: Enhancing Avatar Creation Process in V-Sekai Advanced",
     "section": "",
-    "text": "Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Excessive complexity or technical requirements: We want the avatar creation process to be user-friendly and accessible to a wide range of users, so any options that require advanced technical skills or have excessively complex customization controls will not be included."
   },
   {
-    "objectID": "decisions/20231203-mesh-rwkv-test-metrics.html",
-    "href": "decisions/20231203-mesh-rwkv-test-metrics.html",
-    "title": "Draft: Initial Training of the MeshRWVK Model",
+    "objectID": "decisions/20230716-enhancing-avatar-creation-process-02-advanced.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230716-enhancing-avatar-creation-process-02-advanced.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Enhancing Avatar Creation Process in V-Sekai Advanced",
     "section": "",
-    "text": "Status: Draft\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nCurrently, there is no model for MeshRWVK. This presents a challenge in generating diverse and complex 3D shapes for virtual environments.\n\n\n\nThe lack of a model for MeshRWVK limits the diversity and complexity of 3D shapes that can be generated for virtual environments.\n\n\n\nTo address this issue, we propose to enhance the training of the GPT model using a dataset known as Objaverse-XL, which includes various categories of 3D shapes. The training phase will employ several techniques such as random shifts, scaling, and planar decimation to improve the model’s ability to create diverse shapes.\n\n\n\nThe performance of the model will be evaluated using several metrics including Minimum Matching Distance (MMD), Coverage (COV), 1-Nearest-Neighbor Accuracy (1-NNA), Chamfer Distance (CD), FID and KID scores, and compactness.\n\n\n\nEnhancing the training of the GPT model will improve its ability to generate more complex 3D shapes, allowing for greater diversity and realism in the virtual environments created by V-Sekai.\n\n\n\nThe proposed strategy may require significant computational resources and time. There may also be a learning curve associated with understanding and implementing the proposed enhancements.\n\n\n\nAn alternative approach could have been to use a different model for generating 3D shapes. However, this would require a complete overhaul of the current system and may not necessarily yield better results.\n\n\n\nThe proposed enhancements may not be necessary for simpler virtual environments. In such cases, the current implementation of the MeshGPT model may suffice.\n\n\n\nYes, the proposed enhancements will be implemented by the V-Sekai development team.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nObjaverse-XL\n\nThis article was assisted by AI assistant, Aria."
+    "text": "No, the proposed enhancement involves a multi-step process that cannot be easily replicated with just a few lines of script."
   },
   {
-    "objectID": "decisions/20231203-mesh-rwkv-test-metrics.html#metadata",
-    "href": "decisions/20231203-mesh-rwkv-test-metrics.html#metadata",
-    "title": "Draft: Initial Training of the MeshRWVK Model",
+    "objectID": "decisions/20230716-enhancing-avatar-creation-process-02-advanced.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230716-enhancing-avatar-creation-process-02-advanced.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Enhancing Avatar Creation Process in V-Sekai Advanced",
     "section": "",
-    "text": "Status: Draft\nDeciders: V-Sekai\nTags: V-Sekai"
+    "text": "The proposed enhancement addresses the limitations in V-Sekai’s avatar creation process, providing users with a comprehensive solution for creating highly customizable avatars. By implementing these tools and techniques within the platform, V-Sekai can offer a more robust and user-friendly experience for its community."
   },
   {
-    "objectID": "decisions/20231203-mesh-rwkv-test-metrics.html#context",
-    "href": "decisions/20231203-mesh-rwkv-test-metrics.html#context",
-    "title": "Draft: Initial Training of the MeshRWVK Model",
+    "objectID": "decisions/20230716-enhancing-avatar-creation-process-02-advanced.html#references",
+    "href": "decisions/20230716-enhancing-avatar-creation-process-02-advanced.html#references",
+    "title": "Proposed: Enhancing Avatar Creation Process in V-Sekai Advanced",
     "section": "",
-    "text": "Currently, there is no model for MeshRWVK. This presents a challenge in generating diverse and complex 3D shapes for virtual environments."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20231203-mesh-rwkv-test-metrics.html#problem",
-    "href": "decisions/20231203-mesh-rwkv-test-metrics.html#problem",
-    "title": "Draft: Initial Training of the MeshRWVK Model",
+    "objectID": "decisions/20231111-ayon-evaluation.html",
+    "href": "decisions/20231111-ayon-evaluation.html",
+    "title": "Proposed: Evaluate AYON pipeline platform on hosted cloud services",
     "section": "",
-    "text": "The lack of a model for MeshRWVK limits the diversity and complexity of 3D shapes that can be generated for virtual environments."
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\n\n\nAYON is an open-source pipeline platform designed for creative studios, particularly those involved in animation and visual effects (VFX). It provides a robust and scalable solution for managing and executing creative projects. AYON’s source code is publicly accessible, allowing for community-driven development and customization. It is geared towards creative studios, particularly those working in animation and VFX. Evolved from OpenPype, it has been used since 2018 in various production environments. Supported and funded by the creative industry, AYON also offers comprehensive documentation for users, including guides for administrators and developers.\n\n\n\nHosted cloud services provide a flexible and scalable infrastructure solution that can be tailored to meet the specific needs of an organization. They offer a range of services including compute power, storage, and networking capabilities, as well as advanced services such as machine learning and data analytics. These services are typically provided on a pay-as-you-go basis, making them a cost-effective option for many organizations.\n\n\n\n\nEvaluate AYON on hosted cloud services for a game development studio.\n\n\n\nDeploy AYON using a single Docker image with hosted cloud services for Redis and PostgreSQL.\n\n\nRun a release of https://github.com/ynput/OpenPype/releases on Windows 11 desktop.\n\n\n\nWhy does OpenPype use mongodb?\n\n\n\n\nNext, we will configure AYON according to the needs of a typical game development studio. This includes setting up workflows for creating assets and assemblages in Blender, and importing them into the Godot Engine.\n\nSet the fps to 30.\nSet the resolution to 3840 × 2160\n\n\n\n\n\nIn this step, we will integrate Google Drive with the AYON homesite. This will allow us to store all our files and data directly into Google Drive from the AYON homesite.\n\n\n\nWe will then run a series of tests to assess the performance, reliability, and usability of AYON on hosted cloud services. These tests will simulate tasks a 3D game studio would typically perform, such as creating and modifying assets in Blender, and importing these assets into the Godot Engine.\n\n\n\nFinally, we will document our findings from the tests and provide recommendations based on the evaluation results. This will help us understand how well AYON performs on hosted cloud services, and whether it is a suitable solution for game development studios using the Godot Engine.\n\n\n\n\nImplementing AYON on hosted cloud services could potentially streamline the workflow of game development studios, making project management more efficient and effective.\n\n\n\nThere may be compatibility issues between AYON and hosted cloud services that could affect performance or functionality. Additionally, there may be a learning curve for teams unfamiliar with AYON.\n\n\n\nAlternative solutions such as proprietary pipeline platforms were considered. However, the open-source nature of AYON provides more flexibility and customization options.\n\n\n\nIn cases where the studio is working on multiple platforms or using a variety of software, additional configuration and testing may be required to ensure AYON works seamlessly across all environments.\n\n\n\nThis evaluation aligns with our core competencies in evaluating and implementing technology solutions. As such, it should be executed by our team.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nAYON Docker\nayon-2023-8-production-beta\n\nThis article was assisted by AI assistant Aria."
   },
   {
-    "objectID": "decisions/20231203-mesh-rwkv-test-metrics.html#solution",
-    "href": "decisions/20231203-mesh-rwkv-test-metrics.html#solution",
-    "title": "Draft: Initial Training of the MeshRWVK Model",
+    "objectID": "decisions/20231111-ayon-evaluation.html#metadata",
+    "href": "decisions/20231111-ayon-evaluation.html#metadata",
+    "title": "Proposed: Evaluate AYON pipeline platform on hosted cloud services",
     "section": "",
-    "text": "To address this issue, we propose to enhance the training of the GPT model using a dataset known as Objaverse-XL, which includes various categories of 3D shapes. The training phase will employ several techniques such as random shifts, scaling, and planar decimation to improve the model’s ability to create diverse shapes."
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20231203-mesh-rwkv-test-metrics.html#evaluation",
-    "href": "decisions/20231203-mesh-rwkv-test-metrics.html#evaluation",
-    "title": "Draft: Initial Training of the MeshRWVK Model",
+    "objectID": "decisions/20231111-ayon-evaluation.html#the-backdrop",
+    "href": "decisions/20231111-ayon-evaluation.html#the-backdrop",
+    "title": "Proposed: Evaluate AYON pipeline platform on hosted cloud services",
     "section": "",
-    "text": "The performance of the model will be evaluated using several metrics including Minimum Matching Distance (MMD), Coverage (COV), 1-Nearest-Neighbor Accuracy (1-NNA), Chamfer Distance (CD), FID and KID scores, and compactness."
+    "text": "AYON is an open-source pipeline platform designed for creative studios, particularly those involved in animation and visual effects (VFX). It provides a robust and scalable solution for managing and executing creative projects. AYON’s source code is publicly accessible, allowing for community-driven development and customization. It is geared towards creative studios, particularly those working in animation and VFX. Evolved from OpenPype, it has been used since 2018 in various production environments. Supported and funded by the creative industry, AYON also offers comprehensive documentation for users, including guides for administrators and developers.\n\n\n\nHosted cloud services provide a flexible and scalable infrastructure solution that can be tailored to meet the specific needs of an organization. They offer a range of services including compute power, storage, and networking capabilities, as well as advanced services such as machine learning and data analytics. These services are typically provided on a pay-as-you-go basis, making them a cost-effective option for many organizations."
   },
   {
-    "objectID": "decisions/20231203-mesh-rwkv-test-metrics.html#benefits",
-    "href": "decisions/20231203-mesh-rwkv-test-metrics.html#benefits",
-    "title": "Draft: Initial Training of the MeshRWVK Model",
+    "objectID": "decisions/20231111-ayon-evaluation.html#the-challenge",
+    "href": "decisions/20231111-ayon-evaluation.html#the-challenge",
+    "title": "Proposed: Evaluate AYON pipeline platform on hosted cloud services",
     "section": "",
-    "text": "Enhancing the training of the GPT model will improve its ability to generate more complex 3D shapes, allowing for greater diversity and realism in the virtual environments created by V-Sekai."
+    "text": "Evaluate AYON on hosted cloud services for a game development studio."
   },
   {
-    "objectID": "decisions/20231203-mesh-rwkv-test-metrics.html#risks",
-    "href": "decisions/20231203-mesh-rwkv-test-metrics.html#risks",
-    "title": "Draft: Initial Training of the MeshRWVK Model",
+    "objectID": "decisions/20231111-ayon-evaluation.html#the-strategy",
+    "href": "decisions/20231111-ayon-evaluation.html#the-strategy",
+    "title": "Proposed: Evaluate AYON pipeline platform on hosted cloud services",
     "section": "",
-    "text": "The proposed strategy may require significant computational resources and time. There may also be a learning curve associated with understanding and implementing the proposed enhancements."
+    "text": "Deploy AYON using a single Docker image with hosted cloud services for Redis and PostgreSQL.\n\n\nRun a release of https://github.com/ynput/OpenPype/releases on Windows 11 desktop.\n\n\n\nWhy does OpenPype use mongodb?\n\n\n\n\nNext, we will configure AYON according to the needs of a typical game development studio. This includes setting up workflows for creating assets and assemblages in Blender, and importing them into the Godot Engine.\n\nSet the fps to 30.\nSet the resolution to 3840 × 2160\n\n\n\n\n\nIn this step, we will integrate Google Drive with the AYON homesite. This will allow us to store all our files and data directly into Google Drive from the AYON homesite.\n\n\n\nWe will then run a series of tests to assess the performance, reliability, and usability of AYON on hosted cloud services. These tests will simulate tasks a 3D game studio would typically perform, such as creating and modifying assets in Blender, and importing these assets into the Godot Engine.\n\n\n\nFinally, we will document our findings from the tests and provide recommendations based on the evaluation results. This will help us understand how well AYON performs on hosted cloud services, and whether it is a suitable solution for game development studios using the Godot Engine."
   },
   {
-    "objectID": "decisions/20231203-mesh-rwkv-test-metrics.html#alternatives",
-    "href": "decisions/20231203-mesh-rwkv-test-metrics.html#alternatives",
-    "title": "Draft: Initial Training of the MeshRWVK Model",
+    "objectID": "decisions/20231111-ayon-evaluation.html#the-upside",
+    "href": "decisions/20231111-ayon-evaluation.html#the-upside",
+    "title": "Proposed: Evaluate AYON pipeline platform on hosted cloud services",
     "section": "",
-    "text": "An alternative approach could have been to use a different model for generating 3D shapes. However, this would require a complete overhaul of the current system and may not necessarily yield better results."
+    "text": "Implementing AYON on hosted cloud services could potentially streamline the workflow of game development studios, making project management more efficient and effective."
   },
   {
-    "objectID": "decisions/20231203-mesh-rwkv-test-metrics.html#limitations",
-    "href": "decisions/20231203-mesh-rwkv-test-metrics.html#limitations",
-    "title": "Draft: Initial Training of the MeshRWVK Model",
+    "objectID": "decisions/20231111-ayon-evaluation.html#the-downside",
+    "href": "decisions/20231111-ayon-evaluation.html#the-downside",
+    "title": "Proposed: Evaluate AYON pipeline platform on hosted cloud services",
     "section": "",
-    "text": "The proposed enhancements may not be necessary for simpler virtual environments. In such cases, the current implementation of the MeshGPT model may suffice."
+    "text": "There may be compatibility issues between AYON and hosted cloud services that could affect performance or functionality. Additionally, there may be a learning curve for teams unfamiliar with AYON."
   },
   {
-    "objectID": "decisions/20231203-mesh-rwkv-test-metrics.html#implementation",
-    "href": "decisions/20231203-mesh-rwkv-test-metrics.html#implementation",
-    "title": "Draft: Initial Training of the MeshRWVK Model",
+    "objectID": "decisions/20231111-ayon-evaluation.html#the-road-not-taken",
+    "href": "decisions/20231111-ayon-evaluation.html#the-road-not-taken",
+    "title": "Proposed: Evaluate AYON pipeline platform on hosted cloud services",
     "section": "",
-    "text": "Yes, the proposed enhancements will be implemented by the V-Sekai development team."
+    "text": "Alternative solutions such as proprietary pipeline platforms were considered. However, the open-source nature of AYON provides more flexibility and customization options."
   },
   {
-    "objectID": "decisions/20231203-mesh-rwkv-test-metrics.html#references",
-    "href": "decisions/20231203-mesh-rwkv-test-metrics.html#references",
-    "title": "Draft: Initial Training of the MeshRWVK Model",
+    "objectID": "decisions/20231111-ayon-evaluation.html#the-infrequent-use-case",
+    "href": "decisions/20231111-ayon-evaluation.html#the-infrequent-use-case",
+    "title": "Proposed: Evaluate AYON pipeline platform on hosted cloud services",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nObjaverse-XL\n\nThis article was assisted by AI assistant, Aria."
+    "text": "In cases where the studio is working on multiple platforms or using a variety of software, additional configuration and testing may be required to ensure AYON works seamlessly across all environments."
   },
   {
-    "objectID": "decisions/20231019-quest3-mocap-steam-lighthouse.html",
-    "href": "decisions/20231019-quest3-mocap-steam-lighthouse.html",
-    "title": "Proposed: Valve VR Ecosystem with Quest 3",
+    "objectID": "decisions/20231111-ayon-evaluation.html#in-core-and-done-by-us",
+    "href": "decisions/20231111-ayon-evaluation.html#in-core-and-done-by-us",
+    "title": "Proposed: Evaluate AYON pipeline platform on hosted cloud services",
     "section": "",
-    "text": "Status: Proposed \nDeciders: V-Sekai\nTags: V-Sekai, Valve VR Ecosystem, Quest 3\n\n\n\n\nThe conversation between iFire and cyberpunkmermaid reveals an innovative idea of creating a portable VR setup. iFire has a cart with a PCVR computer in it. This setup streams to a Quest 3, which is a virtual reality headset. The system uses portable light houses on clamped sticks for tracking.\n\n\n\nThe challenge lies in integrating the power of the Valve VR ecosystem with the portability of the Quest series. It requires careful selection and arrangement of components to create a mobile VR station that can stream your desktop to your Meta Quest 2 or 3.\n\n\n\nThe strategy involves using 6 HTC or Tundra trackers motion capture. One tracker is dedicated to the continuous calibration with the Meta Quest 3 HMD and the SteamVR ecosystem. Two are used for the foot, two for the shoulders, one for the chest, one for the hips. The setup also includes 2 or 4 light houses and requires the purchase of Virtual Desktop for the Meta Quest 3.\n\n\n\nThe upside of this setup is its portability and versatility. It essentially turns your laptop into a mobile VR station, allowing you to leverage the power of the Valve VR ecosystem anywhere you go.\n\n\n\nThe downside could be the complexity of the setup and the cost of purchasing all the necessary components. However, the benefits of having a portable VR setup may outweigh these drawbacks for many users.\n\n\n\nAn alternative approach could be to keep using the tethered VR headset like the Valve Index, but the freedom of being untethered decreases friction to VR use.\n\n\n\nIn addition to regular use, the V-Sekai-faceless repository on GitHub provides a solution for interacting with the virtual world without needing to wear the HMD (Head-Mounted Display). This can be beneficial in various scenarios such as testing or when the HMD is uncomfortable to wear for extended periods.\n\n\n\nThis setup is not part of the core V-Sekai offering but is an innovative idea proposed by members of the community. It demonstrates the potential for creativity and innovation within the V-Sekai ecosystem.\n\n\n\n\n[V-Sekai] - AI assists this article.\nOpenVR-SpaceCalibrator\nV-Sekai-faceless"
+    "text": "This evaluation aligns with our core competencies in evaluating and implementing technology solutions. As such, it should be executed by our team."
   },
   {
-    "objectID": "decisions/20231019-quest3-mocap-steam-lighthouse.html#metadata",
-    "href": "decisions/20231019-quest3-mocap-steam-lighthouse.html#metadata",
-    "title": "Proposed: Valve VR Ecosystem with Quest 3",
+    "objectID": "decisions/20231111-ayon-evaluation.html#further-reading",
+    "href": "decisions/20231111-ayon-evaluation.html#further-reading",
+    "title": "Proposed: Evaluate AYON pipeline platform on hosted cloud services",
     "section": "",
-    "text": "Status: Proposed \nDeciders: V-Sekai\nTags: V-Sekai, Valve VR Ecosystem, Quest 3"
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nAYON Docker\nayon-2023-8-production-beta\n\nThis article was assisted by AI assistant Aria."
   },
   {
-    "objectID": "decisions/20231019-quest3-mocap-steam-lighthouse.html#the-backdrop",
-    "href": "decisions/20231019-quest3-mocap-steam-lighthouse.html#the-backdrop",
-    "title": "Proposed: Valve VR Ecosystem with Quest 3",
+    "objectID": "decisions/20230527-server-cdn-session-url.html",
+    "href": "decisions/20230527-server-cdn-session-url.html",
+    "title": "Proposed: Handling access to session based game data",
     "section": "",
-    "text": "The conversation between iFire and cyberpunkmermaid reveals an innovative idea of creating a portable VR setup. iFire has a cart with a PCVR computer in it. This setup streams to a Quest 3, which is a virtual reality headset. The system uses portable light houses on clamped sticks for tracking."
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, GPT-4\n\n\n\n\nV-Sekai is facing limitations in handling large amounts of data efficiently and securely. The current system needs improvements in data management, performance, and security.\n\n\n\nAssigning session IDs and URLs to every asset to improve data management, performance, and security.\n\n\n\n\nGenerate unique session IDs and URLs for each asset.\nStore the session IDs and URLs in a secure database.\nUse the session IDs and URLs for accessing and managing assets.\n\n\n\n\n\nImproved data management through unique identifiers for each asset.\nEnhanced security by using session IDs and URLs for access control.\nBetter performance due to efficient asset management.\n\n\n\n\n\nIncreased complexity in the system architecture.\nPotential challenges in implementing and maintaining unique session IDs and URLs.\n\n\n\n\n\nCaching assets locally: This option was considered for improving performance, but it would not address data management and security concerns.\nUsing a centralized server for asset management: This approach could improve data management but might introduce single points of failure and potential bottlenecks in performance.\nEncrypting all assets: While this would enhance security, it would not address data management issues and could negatively impact performance due to the overhead of encryption and decryption processes.\n\n\n\n\nNo, this enhancement requires significant changes to the system architecture and cannot be achieved with a simple script workaround.\n\n\n\nYes, this enhancement addresses core limitations in the V-Sekai system and should be implemented by the V-Sekai team to ensure proper integration and compatibility with existing components.\n\n\n\n\nV-Sekai"
   },
   {
-    "objectID": "decisions/20231019-quest3-mocap-steam-lighthouse.html#the-challenge",
-    "href": "decisions/20231019-quest3-mocap-steam-lighthouse.html#the-challenge",
-    "title": "Proposed: Valve VR Ecosystem with Quest 3",
+    "objectID": "decisions/20230527-server-cdn-session-url.html#metadata",
+    "href": "decisions/20230527-server-cdn-session-url.html#metadata",
+    "title": "Proposed: Handling access to session based game data",
     "section": "",
-    "text": "The challenge lies in integrating the power of the Valve VR ecosystem with the portability of the Quest series. It requires careful selection and arrangement of components to create a mobile VR station that can stream your desktop to your Meta Quest 2 or 3."
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, GPT-4"
   },
   {
-    "objectID": "decisions/20231019-quest3-mocap-steam-lighthouse.html#the-strategy",
-    "href": "decisions/20231019-quest3-mocap-steam-lighthouse.html#the-strategy",
-    "title": "Proposed: Valve VR Ecosystem with Quest 3",
+    "objectID": "decisions/20230527-server-cdn-session-url.html#context-and-problem-statement",
+    "href": "decisions/20230527-server-cdn-session-url.html#context-and-problem-statement",
+    "title": "Proposed: Handling access to session based game data",
     "section": "",
-    "text": "The strategy involves using 6 HTC or Tundra trackers motion capture. One tracker is dedicated to the continuous calibration with the Meta Quest 3 HMD and the SteamVR ecosystem. Two are used for the foot, two for the shoulders, one for the chest, one for the hips. The setup also includes 2 or 4 light houses and requires the purchase of Virtual Desktop for the Meta Quest 3."
+    "text": "V-Sekai is facing limitations in handling large amounts of data efficiently and securely. The current system needs improvements in data management, performance, and security."
   },
   {
-    "objectID": "decisions/20231019-quest3-mocap-steam-lighthouse.html#the-upside",
-    "href": "decisions/20231019-quest3-mocap-steam-lighthouse.html#the-upside",
-    "title": "Proposed: Valve VR Ecosystem with Quest 3",
+    "objectID": "decisions/20230527-server-cdn-session-url.html#proposed-solution",
+    "href": "decisions/20230527-server-cdn-session-url.html#proposed-solution",
+    "title": "Proposed: Handling access to session based game data",
     "section": "",
-    "text": "The upside of this setup is its portability and versatility. It essentially turns your laptop into a mobile VR station, allowing you to leverage the power of the Valve VR ecosystem anywhere you go."
+    "text": "Assigning session IDs and URLs to every asset to improve data management, performance, and security."
   },
   {
-    "objectID": "decisions/20231019-quest3-mocap-steam-lighthouse.html#the-downside",
-    "href": "decisions/20231019-quest3-mocap-steam-lighthouse.html#the-downside",
-    "title": "Proposed: Valve VR Ecosystem with Quest 3",
+    "objectID": "decisions/20230527-server-cdn-session-url.html#implementation",
+    "href": "decisions/20230527-server-cdn-session-url.html#implementation",
+    "title": "Proposed: Handling access to session based game data",
     "section": "",
-    "text": "The downside could be the complexity of the setup and the cost of purchasing all the necessary components. However, the benefits of having a portable VR setup may outweigh these drawbacks for many users."
+    "text": "Generate unique session IDs and URLs for each asset.\nStore the session IDs and URLs in a secure database.\nUse the session IDs and URLs for accessing and managing assets."
   },
   {
-    "objectID": "decisions/20231019-quest3-mocap-steam-lighthouse.html#the-road-not-taken",
-    "href": "decisions/20231019-quest3-mocap-steam-lighthouse.html#the-road-not-taken",
-    "title": "Proposed: Valve VR Ecosystem with Quest 3",
+    "objectID": "decisions/20230527-server-cdn-session-url.html#positive-consequences",
+    "href": "decisions/20230527-server-cdn-session-url.html#positive-consequences",
+    "title": "Proposed: Handling access to session based game data",
     "section": "",
-    "text": "An alternative approach could be to keep using the tethered VR headset like the Valve Index, but the freedom of being untethered decreases friction to VR use."
+    "text": "Improved data management through unique identifiers for each asset.\nEnhanced security by using session IDs and URLs for access control.\nBetter performance due to efficient asset management."
   },
   {
-    "objectID": "decisions/20231019-quest3-mocap-steam-lighthouse.html#the-infrequent-use-case",
-    "href": "decisions/20231019-quest3-mocap-steam-lighthouse.html#the-infrequent-use-case",
-    "title": "Proposed: Valve VR Ecosystem with Quest 3",
+    "objectID": "decisions/20230527-server-cdn-session-url.html#negative-consequences",
+    "href": "decisions/20230527-server-cdn-session-url.html#negative-consequences",
+    "title": "Proposed: Handling access to session based game data",
     "section": "",
-    "text": "In addition to regular use, the V-Sekai-faceless repository on GitHub provides a solution for interacting with the virtual world without needing to wear the HMD (Head-Mounted Display). This can be beneficial in various scenarios such as testing or when the HMD is uncomfortable to wear for extended periods."
+    "text": "Increased complexity in the system architecture.\nPotential challenges in implementing and maintaining unique session IDs and URLs."
   },
   {
-    "objectID": "decisions/20231019-quest3-mocap-steam-lighthouse.html#in-core-and-done-by-us",
-    "href": "decisions/20231019-quest3-mocap-steam-lighthouse.html#in-core-and-done-by-us",
-    "title": "Proposed: Valve VR Ecosystem with Quest 3",
+    "objectID": "decisions/20230527-server-cdn-session-url.html#option-graveyard",
+    "href": "decisions/20230527-server-cdn-session-url.html#option-graveyard",
+    "title": "Proposed: Handling access to session based game data",
     "section": "",
-    "text": "This setup is not part of the core V-Sekai offering but is an innovative idea proposed by members of the community. It demonstrates the potential for creativity and innovation within the V-Sekai ecosystem."
+    "text": "Caching assets locally: This option was considered for improving performance, but it would not address data management and security concerns.\nUsing a centralized server for asset management: This approach could improve data management but might introduce single points of failure and potential bottlenecks in performance.\nEncrypting all assets: While this would enhance security, it would not address data management issues and could negatively impact performance due to the overhead of encryption and decryption processes."
   },
   {
-    "objectID": "decisions/20231019-quest3-mocap-steam-lighthouse.html#further-reading",
-    "href": "decisions/20231019-quest3-mocap-steam-lighthouse.html#further-reading",
-    "title": "Proposed: Valve VR Ecosystem with Quest 3",
+    "objectID": "decisions/20230527-server-cdn-session-url.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230527-server-cdn-session-url.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Handling access to session based game data",
     "section": "",
-    "text": "[V-Sekai] - AI assists this article.\nOpenVR-SpaceCalibrator\nV-Sekai-faceless"
+    "text": "No, this enhancement requires significant changes to the system architecture and cannot be achieved with a simple script workaround."
   },
   {
-    "objectID": "decisions/20211031-voip.html",
-    "href": "decisions/20211031-voip.html",
-    "title": "Accepted: VOIP",
+    "objectID": "decisions/20230527-server-cdn-session-url.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230527-server-cdn-session-url.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Handling access to session based game data",
     "section": "",
-    "text": "Accepted: VOIP\n\nContext and Problem Statement\nNeed to see our work for integration testing.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nNeed to integration test our features without multiplying work.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n\nCreate a series of projects\nHave them be exportable and testable\nSee robot framework\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot workaroundable\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nI have an approach!\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Yes, this enhancement addresses core limitations in the V-Sekai system and should be implemented by the V-Sekai team to ensure proper integration and compatibility with existing components."
   },
   {
-    "objectID": "decisions/20240410-data-storage-elixir.html",
-    "href": "decisions/20240410-data-storage-elixir.html",
-    "title": "Proposed: Implementing Elixir Data Models for Memory, Local, Bulk, and Global Storage",
+    "objectID": "decisions/20230527-server-cdn-session-url.html#references",
+    "href": "decisions/20230527-server-cdn-session-url.html#references",
+    "title": "Proposed: Handling access to session based game data",
     "section": "",
-    "text": "The goal is to effectively manage large volumes of 3D model data and game entity replication reliably and efficiently.\n\n\n\nThe current system faces challenges handling large amounts of 3D model data and managing game entity replication. This leads to performance issues and potential data loss.\n\n\n\nThe solution involves several steps to ensure data consistency and durability:\n\nContent Delivery Network (CDN): We will create a CDN similar to a static sftp file store for efficient content delivery.\nEtso for Erlang Term Storage (ETS): Etso will be configured to manage temporary, in-memory data structures with Ecto schemas in Elixir applications. This is ideal for quick data manipulation and caching.\nRaft/Ra for Distributed Consensus: Raft/Ra will be deployed to ensure distributed consensus across system nodes, which is crucial for coordinated state changes and maintaining data consistency.\nCockroachDB for Persistent Storage: CockroachDB will store critical, structured data that requires ACID transactions and global accessibility. This ensures the durability of our data.\nData Flow Management: Protocols will be established to move temporary data from Etso/ETS to the CDN for bulk storage. For structured data persistence, we will use CockroachDB.\nConsistency Management: Raft/Ra will manage write operations across the CDN and CockroachDB to ensure consistency and fault tolerance.\n\n\n\ndefmodule MyApp.Cache do\n  use Etso.Schema\n  @primary_key {:id, :binary_id, autogenerate: true}\n  field :key, :string\n  field :value, :any\nend\n\n\n\nRaft/Ra will be implemented to ensure distributed consensus across system nodes.\n\n\n\nCockroachDB will store critical, structured data that requires ACID transactions and global accessibility.\n\n\n\nThe Membrane Framework will establish Data flow protocols to move temporary data from Etso/ETS to the CDN for bulk storage and CockroachDB for structured data persistence.\n\n\n\nRaft/Ra will manage write operations across the CDN and CockroachDB, ensuring consistency and fault tolerance.\n\n\n\n\n\nEfficient storage of bulk 3D model data\nEffective management of game entity replication\nImproved system performance\nReduced risk of data loss\n\n\n\n\n\nRequires significant development effort\nPotential for increased system complexity\n\n\n\n\nTraditional databases or file systems were considered but rejected due to their limitations in handling large volumes of 3D model data and managing game entity replication.\n\n\n\nThis proposal may not be suitable for smaller projects that do not require the storage of large volumes of 3D model data or managing game entity replication.\n\n\n\nThe V-Sekai development team will implement this proposal.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team, “Bioblaze Payne”, “fire”\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAssisted by Aria."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20240410-data-storage-elixir.html#context",
-    "href": "decisions/20240410-data-storage-elixir.html#context",
-    "title": "Proposed: Implementing Elixir Data Models for Memory, Local, Bulk, and Global Storage",
+    "objectID": "decisions/20240608-skin-weight-transfer-skeleton-merge.html",
+    "href": "decisions/20240608-skin-weight-transfer-skeleton-merge.html",
+    "title": "Accepted: Better Skeleton Merge with Robust Skin Weight Transfer",
     "section": "",
-    "text": "The goal is to effectively manage large volumes of 3D model data and game entity replication reliably and efficiently."
+    "text": "Rigging and clothing fitting are intricate tasks in game development, demanding a deep understanding of 3D modeling, animation, and the specific requirements of the game engine. In the context of V-Sekai, a social VR game built on the Godot Engine, these tasks become even more challenging due to the need for real-time performance and compatibility with various hardware devices.\n\n\n\nOur goal is to provide a solution that enables players and creators to incorporate their own clothing into the V-Sekai game, without turning the game into an impenetrable black box. The current process of rigging and fitting clothing onto characters is labor-intensive and requires specialized knowledge, limiting the ability of players and creators to fully express themselves through their avatars.\n\n\n\nThe proposed solution involves aligning the vertices from one set of faces to match the vertices in the other set. In Godot, this can be achieved by retrieving mesh arrays and invoking a function with arrays[Mesh.ARRAY_VERTEX], arrays[Mesh.ARRAY_INDEX].\nPassing in the Skeleton3D is not necessary. The recently merged API by smix8 allows baking a skeleton to a static mesh, which can be used for baking and then applying the delta.\nWe plan to utilize robust skin weight transfer code and robust Laplacians. The robust Laplacians algorithm is implemented in geometry-central, which loads a mesh, constructs our intrinsic tufted cover, and generates the resulting Laplace (and mass) matrix.\nPlayer creators will have a fully skin-weighted base mesh (a naked character mesh with no clothing). They can then use robust skin weight transfer with a variable distance and the infilling feature to rig their clothing for use in V-Sekai and anywhere that can handle VRM1.\n\n\n\n\nPlayer customization: Our solution empowers players to use their own clothing designs in the game, enhancing their ability to express themselves and engage with the game world.\nEnhanced game experience: By offering more customization options, we can boost player engagement and satisfaction.\n\n\n\n\n\nLimited platform support: Not all platforms support VRM1 for avatars; most only support VRM0. This could restrict the compatibility of our solution with other platforms and games.\n\n\n\n\nAn alternative approach would have been to create a set of predefined clothing options within the game itself. However, this would limit the creativity and expression of our players. By enabling them to use their own clothing designs, we are fostering a more vibrant and diverse game community.\n\n\n\nWhile the primary use case is for players to rig and fit their own clothing designs, this solution could also be used by game developers to quickly and easily rig and fit clothing for non-player characters (NPCs). This could save development time and resources.\n\n\n\nThis proposal is core to the functionality of the V-Sekai game and will be implemented by us. It aligns with our goal of creating a highly customizable and immersive social VR experience.\n\n\n\nStatus: Accepted \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nRobust Skin Weights Transfer via Weight Inpainting\nA Laplacian for Nonmanifold Triangle Meshes\n\nAI assistant Aria assisted with this article.\n\n\n\nRigging: The process of creating a skeleton for a 3D model (character or object) and defining how it can move. This is crucial for animation in video games.\nClothing Fitting: In the context of game development, this refers to the process of designing and applying clothing to a character model in a way that it moves naturally with the character’s movements.\n3D Modeling: The process of creating a three-dimensional representation of any surface or object by manipulating polygons, edges, and vertices in simulated 3D space.\nAnimation: The technique of photographing successive drawings or positions of puppets or models to create an illusion of movement when the movie is shown as a sequence.\nGame Engine: A software framework designed for the creation and development of video games. Developers use them to create games for consoles, mobile devices, and personal computers.\nReal-Time Performance: Refers to the ability of a computing system or software to instantly respond to user input. In gaming, real-time performance is critical to ensure smooth gameplay and user experience.\nVertices: In 3D modeling, a vertex is a data structure that describes certain attributes, like the position of a point in 2D or 3D space or multiple points on a surface.\nMesh Arrays: In computer graphics, a mesh is a collection of vertices, edges, and faces that define the shape of a polyhedral object in 3D applications.\nSkeleton3D: A node that represents a skeleton in Godot Engine. It contains a hierarchy of bones, which are used to animate the vertices of a MeshInstance.\nRobust Skin Weight Transfer: A method used in 3D modeling to transfer the skin weights from one model to another. This is useful when you want to apply the same skinning (deformation) properties from one model to another.\nRobust Laplacians: A method used in 3D modeling for smoothing and enhancing the quality of a mesh.\nVRM1: A file format for handling 3D humanoid avatar data for VR applications. It’s based on glTF2.0, a file format standard by Khronos Group.\nNon-Player Characters (NPCs): In video games, these are the characters that are not controlled by a player. They can be friends, foes, merchants, or even neutral parties in the game world.\nSocial VR: Virtual Reality that allows users to interact with each other in a virtual environment. It’s like social media but in VR.\nGodot Engine: An open-source game engine developed by the community-driven Godot Engine project. It’s used for creating both 2D and 3D games.\nV-Sekai: A social VR game built on the Godot Engine. The game focuses on providing a highly customizable and immersive social VR experience."
   },
   {
-    "objectID": "decisions/20240410-data-storage-elixir.html#problem-statement",
-    "href": "decisions/20240410-data-storage-elixir.html#problem-statement",
-    "title": "Proposed: Implementing Elixir Data Models for Memory, Local, Bulk, and Global Storage",
+    "objectID": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#the-context",
+    "href": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#the-context",
+    "title": "Accepted: Better Skeleton Merge with Robust Skin Weight Transfer",
     "section": "",
-    "text": "The current system faces challenges handling large amounts of 3D model data and managing game entity replication. This leads to performance issues and potential data loss."
+    "text": "Rigging and clothing fitting are intricate tasks in game development, demanding a deep understanding of 3D modeling, animation, and the specific requirements of the game engine. In the context of V-Sekai, a social VR game built on the Godot Engine, these tasks become even more challenging due to the need for real-time performance and compatibility with various hardware devices."
   },
   {
-    "objectID": "decisions/20240410-data-storage-elixir.html#proposed-solution",
-    "href": "decisions/20240410-data-storage-elixir.html#proposed-solution",
-    "title": "Proposed: Implementing Elixir Data Models for Memory, Local, Bulk, and Global Storage",
+    "objectID": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#the-problem-statement",
+    "href": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#the-problem-statement",
+    "title": "Accepted: Better Skeleton Merge with Robust Skin Weight Transfer",
     "section": "",
-    "text": "The solution involves several steps to ensure data consistency and durability:\n\nContent Delivery Network (CDN): We will create a CDN similar to a static sftp file store for efficient content delivery.\nEtso for Erlang Term Storage (ETS): Etso will be configured to manage temporary, in-memory data structures with Ecto schemas in Elixir applications. This is ideal for quick data manipulation and caching.\nRaft/Ra for Distributed Consensus: Raft/Ra will be deployed to ensure distributed consensus across system nodes, which is crucial for coordinated state changes and maintaining data consistency.\nCockroachDB for Persistent Storage: CockroachDB will store critical, structured data that requires ACID transactions and global accessibility. This ensures the durability of our data.\nData Flow Management: Protocols will be established to move temporary data from Etso/ETS to the CDN for bulk storage. For structured data persistence, we will use CockroachDB.\nConsistency Management: Raft/Ra will manage write operations across the CDN and CockroachDB to ensure consistency and fault tolerance.\n\n\n\ndefmodule MyApp.Cache do\n  use Etso.Schema\n  @primary_key {:id, :binary_id, autogenerate: true}\n  field :key, :string\n  field :value, :any\nend\n\n\n\nRaft/Ra will be implemented to ensure distributed consensus across system nodes.\n\n\n\nCockroachDB will store critical, structured data that requires ACID transactions and global accessibility.\n\n\n\nThe Membrane Framework will establish Data flow protocols to move temporary data from Etso/ETS to the CDN for bulk storage and CockroachDB for structured data persistence.\n\n\n\nRaft/Ra will manage write operations across the CDN and CockroachDB, ensuring consistency and fault tolerance."
+    "text": "Our goal is to provide a solution that enables players and creators to incorporate their own clothing into the V-Sekai game, without turning the game into an impenetrable black box. The current process of rigging and fitting clothing onto characters is labor-intensive and requires specialized knowledge, limiting the ability of players and creators to fully express themselves through their avatars."
   },
   {
-    "objectID": "decisions/20240410-data-storage-elixir.html#benefits",
-    "href": "decisions/20240410-data-storage-elixir.html#benefits",
-    "title": "Proposed: Implementing Elixir Data Models for Memory, Local, Bulk, and Global Storage",
+    "objectID": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Accepted: Better Skeleton Merge with Robust Skin Weight Transfer",
     "section": "",
-    "text": "Efficient storage of bulk 3D model data\nEffective management of game entity replication\nImproved system performance\nReduced risk of data loss"
+    "text": "The proposed solution involves aligning the vertices from one set of faces to match the vertices in the other set. In Godot, this can be achieved by retrieving mesh arrays and invoking a function with arrays[Mesh.ARRAY_VERTEX], arrays[Mesh.ARRAY_INDEX].\nPassing in the Skeleton3D is not necessary. The recently merged API by smix8 allows baking a skeleton to a static mesh, which can be used for baking and then applying the delta.\nWe plan to utilize robust skin weight transfer code and robust Laplacians. The robust Laplacians algorithm is implemented in geometry-central, which loads a mesh, constructs our intrinsic tufted cover, and generates the resulting Laplace (and mass) matrix.\nPlayer creators will have a fully skin-weighted base mesh (a naked character mesh with no clothing). They can then use robust skin weight transfer with a variable distance and the infilling feature to rig their clothing for use in V-Sekai and anywhere that can handle VRM1."
   },
   {
-    "objectID": "decisions/20240410-data-storage-elixir.html#downsides",
-    "href": "decisions/20240410-data-storage-elixir.html#downsides",
-    "title": "Proposed: Implementing Elixir Data Models for Memory, Local, Bulk, and Global Storage",
+    "objectID": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#the-benefits",
+    "href": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#the-benefits",
+    "title": "Accepted: Better Skeleton Merge with Robust Skin Weight Transfer",
     "section": "",
-    "text": "Requires significant development effort\nPotential for increased system complexity"
+    "text": "Player customization: Our solution empowers players to use their own clothing designs in the game, enhancing their ability to express themselves and engage with the game world.\nEnhanced game experience: By offering more customization options, we can boost player engagement and satisfaction."
   },
   {
-    "objectID": "decisions/20240410-data-storage-elixir.html#alternatives-considered",
-    "href": "decisions/20240410-data-storage-elixir.html#alternatives-considered",
-    "title": "Proposed: Implementing Elixir Data Models for Memory, Local, Bulk, and Global Storage",
+    "objectID": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#the-downsides",
+    "href": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#the-downsides",
+    "title": "Accepted: Better Skeleton Merge with Robust Skin Weight Transfer",
     "section": "",
-    "text": "Traditional databases or file systems were considered but rejected due to their limitations in handling large volumes of 3D model data and managing game entity replication."
+    "text": "Limited platform support: Not all platforms support VRM1 for avatars; most only support VRM0. This could restrict the compatibility of our solution with other platforms and games."
   },
   {
-    "objectID": "decisions/20240410-data-storage-elixir.html#infrequent-use-case",
-    "href": "decisions/20240410-data-storage-elixir.html#infrequent-use-case",
-    "title": "Proposed: Implementing Elixir Data Models for Memory, Local, Bulk, and Global Storage",
+    "objectID": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#the-road-not-taken",
+    "href": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#the-road-not-taken",
+    "title": "Accepted: Better Skeleton Merge with Robust Skin Weight Transfer",
     "section": "",
-    "text": "This proposal may not be suitable for smaller projects that do not require the storage of large volumes of 3D model data or managing game entity replication."
+    "text": "An alternative approach would have been to create a set of predefined clothing options within the game itself. However, this would limit the creativity and expression of our players. By enabling them to use their own clothing designs, we are fostering a more vibrant and diverse game community."
   },
   {
-    "objectID": "decisions/20240410-data-storage-elixir.html#implementation",
-    "href": "decisions/20240410-data-storage-elixir.html#implementation",
-    "title": "Proposed: Implementing Elixir Data Models for Memory, Local, Bulk, and Global Storage",
+    "objectID": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#the-infrequent-use-case",
+    "href": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#the-infrequent-use-case",
+    "title": "Accepted: Better Skeleton Merge with Robust Skin Weight Transfer",
     "section": "",
-    "text": "The V-Sekai development team will implement this proposal."
+    "text": "While the primary use case is for players to rig and fit their own clothing designs, this solution could also be used by game developers to quickly and easily rig and fit clothing for non-player characters (NPCs). This could save development time and resources."
   },
   {
-    "objectID": "decisions/20240410-data-storage-elixir.html#status",
-    "href": "decisions/20240410-data-storage-elixir.html#status",
-    "title": "Proposed: Implementing Elixir Data Models for Memory, Local, Bulk, and Global Storage",
+    "objectID": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#in-core-and-done-by-us",
+    "href": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#in-core-and-done-by-us",
+    "title": "Accepted: Better Skeleton Merge with Robust Skin Weight Transfer",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "This proposal is core to the functionality of the V-Sekai game and will be implemented by us. It aligns with our goal of creating a highly customizable and immersive social VR experience."
   },
   {
-    "objectID": "decisions/20240410-data-storage-elixir.html#decision-makers",
-    "href": "decisions/20240410-data-storage-elixir.html#decision-makers",
-    "title": "Proposed: Implementing Elixir Data Models for Memory, Local, Bulk, and Global Storage",
+    "objectID": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#status",
+    "href": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#status",
+    "title": "Accepted: Better Skeleton Merge with Robust Skin Weight Transfer",
     "section": "",
-    "text": "V-Sekai development team, “Bioblaze Payne”, “fire”"
+    "text": "Status: Accepted"
   },
   {
-    "objectID": "decisions/20240410-data-storage-elixir.html#tags",
-    "href": "decisions/20240410-data-storage-elixir.html#tags",
-    "title": "Proposed: Implementing Elixir Data Models for Memory, Local, Bulk, and Global Storage",
+    "objectID": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#decision-makers",
+    "href": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#decision-makers",
+    "title": "Accepted: Better Skeleton Merge with Robust Skin Weight Transfer",
     "section": "",
-    "text": "V-Sekai"
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20240410-data-storage-elixir.html#further-reading",
-    "href": "decisions/20240410-data-storage-elixir.html#further-reading",
-    "title": "Proposed: Implementing Elixir Data Models for Memory, Local, Bulk, and Global Storage",
+    "objectID": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#tags",
+    "href": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#tags",
+    "title": "Accepted: Better Skeleton Merge with Robust Skin Weight Transfer",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAssisted by Aria."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html",
-    "href": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html",
-    "title": "Proposed: Store presentation and book content via Lottie",
+    "objectID": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#further-reading",
+    "href": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#further-reading",
+    "title": "Accepted: Better Skeleton Merge with Robust Skin Weight Transfer",
     "section": "",
-    "text": "[Safety brochure in Lottie format]\nWe want to display book content and presentation content in groups.\nIf the original content is in vectorized format, we want to keep it.\nWe do not have enterprise levels of engineering power.\nLicenses have to be compatible with groups.\n\n\n\nLottie via Samsung’s rlottie library helps solve this problem. Lottie keeps pixel and curve data.\nRGBA8 data is big and Lottie keeps it as pixel and does not rasterize curves.\nLottie exports may turn fonts into curves.\nV-Sekai already has the rlottie implementation in Godot engine so engineering effort is minimized.\nrlottie is Groups license compatible.\n\n\n\n\n\n\nInstall synfig-studio\nIn synfig, for each page of pdf, epub, and others export a lottie json per page\nEnsure the documents are sorted correctly\nSave the folder as zstd compress 7zip archive\nName the archive .cbzl This is file that is similar to CBZ but has an extra l to make it easy to identify as Lottie.\n\n\n\n\n\nOpen the zip.\nFor each sorted entry of the zip\nMake a Godot Engine PackedScene using the Groups Lottie importer.\n\n\n\n\n\n\nIn engine presentation engine\n\n\n\n\n\nLottie is an obscure format\n\n\n\n\n\nOption: Create single executable Pdfium thing that writes to png\nRejection Reason:\nChromium build processes are difficult, but someone made a pdfium binary repository.\nOption: Import pdfium into Godot Engine as a static library\nRejection Reason:\nAdding pdf support to Godot Engine is difficult.\nThe straight-forward pdf implementation writes the RGBA8 data into the cache.\nOption: Use Godot Engine’s native SVG library\nRejection Reason:\nDoes not support pixel data.\nUnreliable\n\n\n\n\nrlottie and pdf formats are complicated.\n\n\n\nPresentations and books should be a first-class feature in groups.\n\n\n\n\nhttps://www.synfig.org/\nhttps://github.com/Samsung/rlottie\nhttps://github.com/godot-extended-libraries/lottie\nhttps://www.adobe.com/products/aftereffects.html\nhttps://airbnb.io/lottie/#/\nhttps://lottiefiles.com/\nhttps://github.com/reMarkable/pdfium-binaries\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nRobust Skin Weights Transfer via Weight Inpainting\nA Laplacian for Nonmanifold Triangle Meshes\n\nAI assistant Aria assisted with this article.\n\n\n\nRigging: The process of creating a skeleton for a 3D model (character or object) and defining how it can move. This is crucial for animation in video games.\nClothing Fitting: In the context of game development, this refers to the process of designing and applying clothing to a character model in a way that it moves naturally with the character’s movements.\n3D Modeling: The process of creating a three-dimensional representation of any surface or object by manipulating polygons, edges, and vertices in simulated 3D space.\nAnimation: The technique of photographing successive drawings or positions of puppets or models to create an illusion of movement when the movie is shown as a sequence.\nGame Engine: A software framework designed for the creation and development of video games. Developers use them to create games for consoles, mobile devices, and personal computers.\nReal-Time Performance: Refers to the ability of a computing system or software to instantly respond to user input. In gaming, real-time performance is critical to ensure smooth gameplay and user experience.\nVertices: In 3D modeling, a vertex is a data structure that describes certain attributes, like the position of a point in 2D or 3D space or multiple points on a surface.\nMesh Arrays: In computer graphics, a mesh is a collection of vertices, edges, and faces that define the shape of a polyhedral object in 3D applications.\nSkeleton3D: A node that represents a skeleton in Godot Engine. It contains a hierarchy of bones, which are used to animate the vertices of a MeshInstance.\nRobust Skin Weight Transfer: A method used in 3D modeling to transfer the skin weights from one model to another. This is useful when you want to apply the same skinning (deformation) properties from one model to another.\nRobust Laplacians: A method used in 3D modeling for smoothing and enhancing the quality of a mesh.\nVRM1: A file format for handling 3D humanoid avatar data for VR applications. It’s based on glTF2.0, a file format standard by Khronos Group.\nNon-Player Characters (NPCs): In video games, these are the characters that are not controlled by a player. They can be friends, foes, merchants, or even neutral parties in the game world.\nSocial VR: Virtual Reality that allows users to interact with each other in a virtual environment. It’s like social media but in VR.\nGodot Engine: An open-source game engine developed by the community-driven Godot Engine project. It’s used for creating both 2D and 3D games.\nV-Sekai: A social VR game built on the Godot Engine. The game focuses on providing a highly customizable and immersive social VR experience."
   },
   {
-    "objectID": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html#context-and-problem-statement",
-    "href": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html#context-and-problem-statement",
-    "title": "Proposed: Store presentation and book content via Lottie",
+    "objectID": "decisions/20240502-where-can-I-use-gltf.html",
+    "href": "decisions/20240502-where-can-I-use-gltf.html",
+    "title": "Proposed: Can I use V-Sekai for 3d assets & 3d extensions?",
     "section": "",
-    "text": "[Safety brochure in Lottie format]\nWe want to display book content and presentation content in groups.\nIf the original content is in vectorized format, we want to keep it.\nWe do not have enterprise levels of engineering power.\nLicenses have to be compatible with groups."
+    "text": "In the current digital landscape, there is a chaos of many different platforms.\n\n\n\nThe problem lies in the lack of interoperability among various platforms. This leads to inefficiencies and difficulties in sharing and utilizing resources across these platforms, especially when it comes to 3D assets and extensions.\n\n\n\nWe propose to develop an Elixir website that facilitates the sharing of interoperability among different file formats including fbx, usd, gltf, Godot Engine tscn, and vrm. This would allow for easier sharing and utilization of 3D assets and extensions across various platforms.\n\n\n\nThis proposal, if implemented, would streamline the process of sharing and using 3D resources across different platforms. It would also foster collaboration and innovation by making it easier for developers to utilize resources from various sources.\n\n\n\nPotential downsides could include the complexity of developing such a platform and ensuring its compatibility with all the mentioned file formats. There may also be potential security concerns that need to be addressed.\n\n\n\nAlternative solutions could involve developing individual converters for each file format, but this would not provide the same level of efficiency and convenience as a unified platform.\n\n\n\nIn cases where only one or two file formats are being used, the benefits of this platform may not be fully realized.\n\n\n\nThis project would be developed and maintained by the V-Sekai development team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\ncaniuse\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: Store presentation and book content via Lottie",
+    "objectID": "decisions/20240502-where-can-I-use-gltf.html#the-context",
+    "href": "decisions/20240502-where-can-I-use-gltf.html#the-context",
+    "title": "Proposed: Can I use V-Sekai for 3d assets & 3d extensions?",
     "section": "",
-    "text": "Lottie via Samsung’s rlottie library helps solve this problem. Lottie keeps pixel and curve data.\nRGBA8 data is big and Lottie keeps it as pixel and does not rasterize curves.\nLottie exports may turn fonts into curves.\nV-Sekai already has the rlottie implementation in Godot engine so engineering effort is minimized.\nrlottie is Groups license compatible."
+    "text": "In the current digital landscape, there is a chaos of many different platforms."
   },
   {
-    "objectID": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Store presentation and book content via Lottie",
+    "objectID": "decisions/20240502-where-can-I-use-gltf.html#the-problem-statement",
+    "href": "decisions/20240502-where-can-I-use-gltf.html#the-problem-statement",
+    "title": "Proposed: Can I use V-Sekai for 3d assets & 3d extensions?",
     "section": "",
-    "text": "Install synfig-studio\nIn synfig, for each page of pdf, epub, and others export a lottie json per page\nEnsure the documents are sorted correctly\nSave the folder as zstd compress 7zip archive\nName the archive .cbzl This is file that is similar to CBZ but has an extra l to make it easy to identify as Lottie.\n\n\n\n\n\nOpen the zip.\nFor each sorted entry of the zip\nMake a Godot Engine PackedScene using the Groups Lottie importer."
+    "text": "The problem lies in the lack of interoperability among various platforms. This leads to inefficiencies and difficulties in sharing and utilizing resources across these platforms, especially when it comes to 3D assets and extensions."
   },
   {
-    "objectID": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html#positive-consequences",
-    "href": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html#positive-consequences",
-    "title": "Proposed: Store presentation and book content via Lottie",
+    "objectID": "decisions/20240502-where-can-I-use-gltf.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240502-where-can-I-use-gltf.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Can I use V-Sekai for 3d assets & 3d extensions?",
     "section": "",
-    "text": "In engine presentation engine"
+    "text": "We propose to develop an Elixir website that facilitates the sharing of interoperability among different file formats including fbx, usd, gltf, Godot Engine tscn, and vrm. This would allow for easier sharing and utilization of 3D assets and extensions across various platforms."
   },
   {
-    "objectID": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html#negative-consequences",
-    "href": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html#negative-consequences",
-    "title": "Proposed: Store presentation and book content via Lottie",
+    "objectID": "decisions/20240502-where-can-I-use-gltf.html#the-benefits",
+    "href": "decisions/20240502-where-can-I-use-gltf.html#the-benefits",
+    "title": "Proposed: Can I use V-Sekai for 3d assets & 3d extensions?",
     "section": "",
-    "text": "Lottie is an obscure format"
+    "text": "This proposal, if implemented, would streamline the process of sharing and using 3D resources across different platforms. It would also foster collaboration and innovation by making it easier for developers to utilize resources from various sources."
   },
   {
-    "objectID": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html#option-graveyard",
-    "href": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html#option-graveyard",
-    "title": "Proposed: Store presentation and book content via Lottie",
+    "objectID": "decisions/20240502-where-can-I-use-gltf.html#the-downsides",
+    "href": "decisions/20240502-where-can-I-use-gltf.html#the-downsides",
+    "title": "Proposed: Can I use V-Sekai for 3d assets & 3d extensions?",
     "section": "",
-    "text": "Option: Create single executable Pdfium thing that writes to png\nRejection Reason:\nChromium build processes are difficult, but someone made a pdfium binary repository.\nOption: Import pdfium into Godot Engine as a static library\nRejection Reason:\nAdding pdf support to Godot Engine is difficult.\nThe straight-forward pdf implementation writes the RGBA8 data into the cache.\nOption: Use Godot Engine’s native SVG library\nRejection Reason:\nDoes not support pixel data.\nUnreliable"
+    "text": "Potential downsides could include the complexity of developing such a platform and ensuring its compatibility with all the mentioned file formats. There may also be potential security concerns that need to be addressed."
   },
   {
-    "objectID": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Store presentation and book content via Lottie",
+    "objectID": "decisions/20240502-where-can-I-use-gltf.html#the-road-not-taken",
+    "href": "decisions/20240502-where-can-I-use-gltf.html#the-road-not-taken",
+    "title": "Proposed: Can I use V-Sekai for 3d assets & 3d extensions?",
     "section": "",
-    "text": "rlottie and pdf formats are complicated."
+    "text": "Alternative solutions could involve developing individual converters for each file format, but this would not provide the same level of efficiency and convenience as a unified platform."
   },
   {
-    "objectID": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Store presentation and book content via Lottie",
+    "objectID": "decisions/20240502-where-can-I-use-gltf.html#the-infrequent-use-case",
+    "href": "decisions/20240502-where-can-I-use-gltf.html#the-infrequent-use-case",
+    "title": "Proposed: Can I use V-Sekai for 3d assets & 3d extensions?",
     "section": "",
-    "text": "Presentations and books should be a first-class feature in groups."
+    "text": "In cases where only one or two file formats are being used, the benefits of this platform may not be fully realized."
   },
   {
-    "objectID": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html#references",
-    "href": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html#references",
-    "title": "Proposed: Store presentation and book content via Lottie",
+    "objectID": "decisions/20240502-where-can-I-use-gltf.html#in-core-and-done-by-us",
+    "href": "decisions/20240502-where-can-I-use-gltf.html#in-core-and-done-by-us",
+    "title": "Proposed: Can I use V-Sekai for 3d assets & 3d extensions?",
     "section": "",
-    "text": "https://www.synfig.org/\nhttps://github.com/Samsung/rlottie\nhttps://github.com/godot-extended-libraries/lottie\nhttps://www.adobe.com/products/aftereffects.html\nhttps://airbnb.io/lottie/#/\nhttps://lottiefiles.com/\nhttps://github.com/reMarkable/pdfium-binaries"
+    "text": "This project would be developed and maintained by the V-Sekai development team."
   },
   {
-    "objectID": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html#derivative-license",
-    "href": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html#derivative-license",
-    "title": "Proposed: Store presentation and book content via Lottie",
+    "objectID": "decisions/20240502-where-can-I-use-gltf.html#status",
+    "href": "decisions/20240502-where-can-I-use-gltf.html#status",
+    "title": "Proposed: Can I use V-Sekai for 3d assets & 3d extensions?",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20240529-improve-godot-import-ecosystem.html",
-    "href": "decisions/20240529-improve-godot-import-ecosystem.html",
-    "title": "Proposed: Improve the Godot Ecosystem",
+    "objectID": "decisions/20240502-where-can-I-use-gltf.html#decision-makers",
+    "href": "decisions/20240502-where-can-I-use-gltf.html#decision-makers",
+    "title": "Proposed: Can I use V-Sekai for 3d assets & 3d extensions?",
     "section": "",
-    "text": "Godot is a powerful open-source game engine that has been gaining popularity due to its flexibility and ease of use. However, there are still areas where it can be improved, particularly in terms of integration with other tools such as Blender.\n\n\n\nThe current process of exporting assets from Blender to Godot can be cumbersome and inefficient. Additionally, there are certain features in Blender that cannot be exported to Godot at all. This proposal aims to address these issues and improve the overall workflow between the two tools.\n\n\n\nHere are some of the key strategies we propose:\n\nExporting of Blender materials to Godot via a custom GLTF2 extension as Godot shaders.\n\nStrategy: Add MaterialX as a Godot engine shader and then have Blender export it.\nWork in progress: Translate MaterialX as a Godot Visual Shader.\nPlan B: Reuse the Blender exporter and use it to export Godot shaders as a glTF extension.\n\nExporting Blender scene settings (sky, etc) via custom GLTF2 extension as Godot shaders.\n\nStrategy: Find all Godot engine scene properties and write a glTF extension that can save or export it.\n\nExport Blender collision shapes to Godot.\n\nStrategy: Through KHR physics. Official Khronos ratification will give Blender and Godot engine glTF support through Aaron Franke’s PR.\n\nCreate and save unique IDs on Blender objects on export.\n\nThis needs to be researched a bit more (may need to be a Blender add-on, GLTF proposal).\n\nUnification of tangent space generation.\n\nThe revised design is that we move all tangent generation to the ImporterMesh3D for the importers.\n\nImprove the asset import dialog based on proposal GH-7238.\nFinalization of the IES light importer from pull request GH-63835.\n\nNeeds work on the equirectangular transform.\n\n\n\n\n\nImproving the Godot ecosystem will make it easier for developers to create and export assets, streamline workflows, and ultimately produce better games.\n\n\n\nThe main downside is that this will require a significant amount of development time and resources.\n\n\n\nAn alternative approach could be to focus on improving Godot’s native tools and capabilities, rather than its integration with other software.\n\n\n\nThis proposal may not benefit developers who do not use Blender or those who prefer to use other game engines.\n\n\n\nThe proposed improvements will be implemented in the core of the Godot engine and will be carried out by our team.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20240529-improve-godot-import-ecosystem.html#the-context",
-    "href": "decisions/20240529-improve-godot-import-ecosystem.html#the-context",
-    "title": "Proposed: Improve the Godot Ecosystem",
+    "objectID": "decisions/20240502-where-can-I-use-gltf.html#tags",
+    "href": "decisions/20240502-where-can-I-use-gltf.html#tags",
+    "title": "Proposed: Can I use V-Sekai for 3d assets & 3d extensions?",
     "section": "",
-    "text": "Godot is a powerful open-source game engine that has been gaining popularity due to its flexibility and ease of use. However, there are still areas where it can be improved, particularly in terms of integration with other tools such as Blender."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20240529-improve-godot-import-ecosystem.html#the-problem-statement",
-    "href": "decisions/20240529-improve-godot-import-ecosystem.html#the-problem-statement",
-    "title": "Proposed: Improve the Godot Ecosystem",
+    "objectID": "decisions/20240502-where-can-I-use-gltf.html#further-reading",
+    "href": "decisions/20240502-where-can-I-use-gltf.html#further-reading",
+    "title": "Proposed: Can I use V-Sekai for 3d assets & 3d extensions?",
     "section": "",
-    "text": "The current process of exporting assets from Blender to Godot can be cumbersome and inefficient. Additionally, there are certain features in Blender that cannot be exported to Godot at all. This proposal aims to address these issues and improve the overall workflow between the two tools."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\ncaniuse\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240529-improve-godot-import-ecosystem.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240529-improve-godot-import-ecosystem.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Improve the Godot Ecosystem",
+    "objectID": "decisions/20231114-upload-creative-commons-fbx-test-files.html",
+    "href": "decisions/20231114-upload-creative-commons-fbx-test-files.html",
+    "title": "Proposed: Upload Creative Commons FBX Test Files for Enhanced LOD Optimization in V-Sekai",
     "section": "",
-    "text": "Here are some of the key strategies we propose:\n\nExporting of Blender materials to Godot via a custom GLTF2 extension as Godot shaders.\n\nStrategy: Add MaterialX as a Godot engine shader and then have Blender export it.\nWork in progress: Translate MaterialX as a Godot Visual Shader.\nPlan B: Reuse the Blender exporter and use it to export Godot shaders as a glTF extension.\n\nExporting Blender scene settings (sky, etc) via custom GLTF2 extension as Godot shaders.\n\nStrategy: Find all Godot engine scene properties and write a glTF extension that can save or export it.\n\nExport Blender collision shapes to Godot.\n\nStrategy: Through KHR physics. Official Khronos ratification will give Blender and Godot engine glTF support through Aaron Franke’s PR.\n\nCreate and save unique IDs on Blender objects on export.\n\nThis needs to be researched a bit more (may need to be a Blender add-on, GLTF proposal).\n\nUnification of tangent space generation.\n\nThe revised design is that we move all tangent generation to the ImporterMesh3D for the importers.\n\nImprove the asset import dialog based on proposal GH-7238.\nFinalization of the IES light importer from pull request GH-63835.\n\nNeeds work on the equirectangular transform."
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: FBX Test Files, LOD Optimization, V-Sekai, File Testing\n\n\n\n\nV-Sekai is continually improving its VR environments and functionalities. A key aspect of this development is optimizing Level of Detail (LOD) to enhance performance without sacrificing visual quality.\n\n\n\nCurrent LOD optimization processes are facing issues, notably crashing when handling multi-gigabyte FBX to OBJ test cases. This limits the ability to effectively test and optimize large, complex models in V-Sekai.\n\n\n\nPropose uploading a suite of Creative Commons FBX test files, credited to bbqbarbhg, to provide a more comprehensive and challenging dataset for LOD optimization testing.\n\n\n\nHaving access to a diverse and complex set of FBX files will allow for more thorough testing and optimization of LOD algorithms, leading to improved performance and stability in handling large and detailed models in the V-Sekai environment.\n\n\n\nThe process of integrating and testing with these new files may require significant resources and time. Additionally, if the files are extremely large or complex, they may pose challenges in terms of storage and processing requirements.\n\n\n\nAlternative approaches might involve optimizing the current LOD algorithms without the use of these specific test files, but this could limit the effectiveness of optimization efforts.\n\n\n\nWhile primarily aimed at enhancing LOD optimization, these test files could also be useful for other aspects of V-Sekai’s development, such as stress-testing the engine and other optimization tasks.\n\n\n\nThis initiative involves incorporating external resources (Creative Commons FBX files) into the core development and testing processes of V-Sekai, potentially requiring adjustments in testing protocols and optimization strategies.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis article was assisted by AI assistant Aria."
   },
   {
-    "objectID": "decisions/20240529-improve-godot-import-ecosystem.html#the-benefits",
-    "href": "decisions/20240529-improve-godot-import-ecosystem.html#the-benefits",
-    "title": "Proposed: Improve the Godot Ecosystem",
+    "objectID": "decisions/20231114-upload-creative-commons-fbx-test-files.html#metadata",
+    "href": "decisions/20231114-upload-creative-commons-fbx-test-files.html#metadata",
+    "title": "Proposed: Upload Creative Commons FBX Test Files for Enhanced LOD Optimization in V-Sekai",
     "section": "",
-    "text": "Improving the Godot ecosystem will make it easier for developers to create and export assets, streamline workflows, and ultimately produce better games."
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: FBX Test Files, LOD Optimization, V-Sekai, File Testing"
   },
   {
-    "objectID": "decisions/20240529-improve-godot-import-ecosystem.html#the-downsides",
-    "href": "decisions/20240529-improve-godot-import-ecosystem.html#the-downsides",
-    "title": "Proposed: Improve the Godot Ecosystem",
+    "objectID": "decisions/20231114-upload-creative-commons-fbx-test-files.html#the-backdrop",
+    "href": "decisions/20231114-upload-creative-commons-fbx-test-files.html#the-backdrop",
+    "title": "Proposed: Upload Creative Commons FBX Test Files for Enhanced LOD Optimization in V-Sekai",
     "section": "",
-    "text": "The main downside is that this will require a significant amount of development time and resources."
+    "text": "V-Sekai is continually improving its VR environments and functionalities. A key aspect of this development is optimizing Level of Detail (LOD) to enhance performance without sacrificing visual quality."
   },
   {
-    "objectID": "decisions/20240529-improve-godot-import-ecosystem.html#the-road-not-taken",
-    "href": "decisions/20240529-improve-godot-import-ecosystem.html#the-road-not-taken",
-    "title": "Proposed: Improve the Godot Ecosystem",
+    "objectID": "decisions/20231114-upload-creative-commons-fbx-test-files.html#the-challenge",
+    "href": "decisions/20231114-upload-creative-commons-fbx-test-files.html#the-challenge",
+    "title": "Proposed: Upload Creative Commons FBX Test Files for Enhanced LOD Optimization in V-Sekai",
     "section": "",
-    "text": "An alternative approach could be to focus on improving Godot’s native tools and capabilities, rather than its integration with other software."
+    "text": "Current LOD optimization processes are facing issues, notably crashing when handling multi-gigabyte FBX to OBJ test cases. This limits the ability to effectively test and optimize large, complex models in V-Sekai."
   },
   {
-    "objectID": "decisions/20240529-improve-godot-import-ecosystem.html#the-infrequent-use-case",
-    "href": "decisions/20240529-improve-godot-import-ecosystem.html#the-infrequent-use-case",
-    "title": "Proposed: Improve the Godot Ecosystem",
+    "objectID": "decisions/20231114-upload-creative-commons-fbx-test-files.html#the-strategy",
+    "href": "decisions/20231114-upload-creative-commons-fbx-test-files.html#the-strategy",
+    "title": "Proposed: Upload Creative Commons FBX Test Files for Enhanced LOD Optimization in V-Sekai",
     "section": "",
-    "text": "This proposal may not benefit developers who do not use Blender or those who prefer to use other game engines."
+    "text": "Propose uploading a suite of Creative Commons FBX test files, credited to bbqbarbhg, to provide a more comprehensive and challenging dataset for LOD optimization testing."
   },
   {
-    "objectID": "decisions/20240529-improve-godot-import-ecosystem.html#in-core-and-done-by-us",
-    "href": "decisions/20240529-improve-godot-import-ecosystem.html#in-core-and-done-by-us",
-    "title": "Proposed: Improve the Godot Ecosystem",
+    "objectID": "decisions/20231114-upload-creative-commons-fbx-test-files.html#the-upside",
+    "href": "decisions/20231114-upload-creative-commons-fbx-test-files.html#the-upside",
+    "title": "Proposed: Upload Creative Commons FBX Test Files for Enhanced LOD Optimization in V-Sekai",
     "section": "",
-    "text": "The proposed improvements will be implemented in the core of the Godot engine and will be carried out by our team."
+    "text": "Having access to a diverse and complex set of FBX files will allow for more thorough testing and optimization of LOD algorithms, leading to improved performance and stability in handling large and detailed models in the V-Sekai environment."
   },
   {
-    "objectID": "decisions/20240529-improve-godot-import-ecosystem.html#status",
-    "href": "decisions/20240529-improve-godot-import-ecosystem.html#status",
-    "title": "Proposed: Improve the Godot Ecosystem",
+    "objectID": "decisions/20231114-upload-creative-commons-fbx-test-files.html#the-downside",
+    "href": "decisions/20231114-upload-creative-commons-fbx-test-files.html#the-downside",
+    "title": "Proposed: Upload Creative Commons FBX Test Files for Enhanced LOD Optimization in V-Sekai",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "The process of integrating and testing with these new files may require significant resources and time. Additionally, if the files are extremely large or complex, they may pose challenges in terms of storage and processing requirements."
   },
   {
-    "objectID": "decisions/20240529-improve-godot-import-ecosystem.html#decision-makers",
-    "href": "decisions/20240529-improve-godot-import-ecosystem.html#decision-makers",
-    "title": "Proposed: Improve the Godot Ecosystem",
+    "objectID": "decisions/20231114-upload-creative-commons-fbx-test-files.html#the-road-not-taken",
+    "href": "decisions/20231114-upload-creative-commons-fbx-test-files.html#the-road-not-taken",
+    "title": "Proposed: Upload Creative Commons FBX Test Files for Enhanced LOD Optimization in V-Sekai",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "Alternative approaches might involve optimizing the current LOD algorithms without the use of these specific test files, but this could limit the effectiveness of optimization efforts."
   },
   {
-    "objectID": "decisions/20240529-improve-godot-import-ecosystem.html#tags",
-    "href": "decisions/20240529-improve-godot-import-ecosystem.html#tags",
-    "title": "Proposed: Improve the Godot Ecosystem",
+    "objectID": "decisions/20231114-upload-creative-commons-fbx-test-files.html#the-infrequent-use-case",
+    "href": "decisions/20231114-upload-creative-commons-fbx-test-files.html#the-infrequent-use-case",
+    "title": "Proposed: Upload Creative Commons FBX Test Files for Enhanced LOD Optimization in V-Sekai",
     "section": "",
-    "text": "V-Sekai"
+    "text": "While primarily aimed at enhancing LOD optimization, these test files could also be useful for other aspects of V-Sekai’s development, such as stress-testing the engine and other optimization tasks."
   },
   {
-    "objectID": "decisions/20240529-improve-godot-import-ecosystem.html#further-reading",
-    "href": "decisions/20240529-improve-godot-import-ecosystem.html#further-reading",
-    "title": "Proposed: Improve the Godot Ecosystem",
+    "objectID": "decisions/20231114-upload-creative-commons-fbx-test-files.html#in-core-and-done-by-us",
+    "href": "decisions/20231114-upload-creative-commons-fbx-test-files.html#in-core-and-done-by-us",
+    "title": "Proposed: Upload Creative Commons FBX Test Files for Enhanced LOD Optimization in V-Sekai",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "This initiative involves incorporating external resources (Creative Commons FBX files) into the core development and testing processes of V-Sekai, potentially requiring adjustments in testing protocols and optimization strategies."
   },
   {
-    "objectID": "decisions/20230602-limited-tracker-placement.html",
-    "href": "decisions/20230602-limited-tracker-placement.html",
-    "title": "Proposed: Capturing accurate body movements with limited tracker placement",
+    "objectID": "decisions/20231114-upload-creative-commons-fbx-test-files.html#further-reading",
+    "href": "decisions/20231114-upload-creative-commons-fbx-test-files.html#further-reading",
+    "title": "Proposed: Upload Creative Commons FBX Test Files for Enhanced LOD Optimization in V-Sekai",
     "section": "",
-    "text": "Proposed: Capturing accurate body movements with limited tracker placement\n\nMetadata\n\nStatus: proposed \nDeciders: V-Sekai,fire,\nTags: V-Sekai,\n\n\n\nContext and Problem Statement\nIn our current VR project, we face the challenge of capturing accurate body movements for both soccer and dancing experiences with a limited budget. How can we prioritize the placement of a limited number of trackers to ensure a realistic and immersive experience for both activities?\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nThe proposed option involves prioritizing tracker placement for the head, hands, hips, and feet, as they are essential for both soccer and dancing experiences. This approach allows for an effective trade-off between tracking accuracy and budget constraints while ensuring a satisfactory level of immersion in both activities.\n\n\nDescribe how your proposal will work with code, pseudo-code, mock-ups, or diagrams\nVR Tracker USB dongles need line of sight.\n\nHead: At the base of the neck to monitor head rotation and tilt.\nLeft Hand: On the left wrist to track the overall motion of the left hand.\nRight Hand: On the right wrist to track the overall motion of the right hand.\nHips: A tracker on the hips to monitor lower body movement. Placed behind the body.\nLeft Foot: A tracker on the left foot to capture left foot movement, essential for both soccer and dancing.\nRight Foot: A tracker on the right foot to capture right foot movement, also crucial for both activities.\n\nAs the budget permits, additional trackers can be incorporated into the setup to further enhance tracking accuracy, particularly for the upper body and leg movements. This expansion can be achieved by following the prioritized list of additional trackers below:\n\nChest: A tracker on the chest to monitor upper body rotation, providing more detailed information about the user’s torso movements.\nLeft Elbow: Attach a tracker to the left elbow to monitor its angle, speed, and position. This helps improve the accuracy of tracking arm movements during activities like soccer and dancing.\nRight Elbow: In the same way, place a tracker on the right elbow to keep track of its angle, speed, and position. This also enhances the precision of tracking arm movements in sports such as soccer and dance performances.\n\nBy gradually adding these trackers to the initial setup, the overall tracking accuracy of the system will be improved. This will result in more natural and immersive interactions within the VR environment, leading to a more satisfying user experience for both soccer and dancing activities.\n\n\nPositive Consequences\n\nEffective use of a limited budget while maintaining immersive experiences.\nThe solution caters to both soccer and dancing activities in VR.\nFlexibility in adding more trackers as budget permits.\n\n\n\nNegative Consequences\n\nReduced tracking accuracy for upper body and leg movements compared to a setup with more trackers.\nPotential limitations in supporting advanced features or interactions in VR.\n\n\n\nOption graveyard\nCamera-based tracking: Utilizing external cameras to track body movements without the need for wearable trackers. While this approach can be cost-effective, it may not provide the same level of accuracy and precision as wearable trackers, particularly for fast and complex movements in soccer and dancing. Additionally, camera-based tracking can be sensitive to lighting conditions and may require a specific setup to function optimally.\nCamera-based tracking might be a viable solution if budget constraints are severe, but it is essential to consider the potential trade-offs in terms of tracking accuracy and reliability compared to wearable trackers.\n\n\nIf this enhancement will be used infrequently, can it be worked around with a few lines of script?\nNo, as the proposed solution deals with hardware configuration and the strategic placement of physical trackers to balance budget and immersion.\n\n\nIs there a reason why this should be core and done by us?\nYes, ensuring an immersive VR experience with a limited budget is a fundamental challenge that requires expertise in tracker placement and prioritization.\n\n\nReferences\n\nV-Sekai"
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis article was assisted by AI assistant Aria."
   },
   {
-    "objectID": "decisions/20221212-world-and-character-tools.html",
-    "href": "decisions/20221212-world-and-character-tools.html",
-    "title": "Proposed: Tools helpful for creating Avatars and Worlds",
+    "objectID": "decisions/20240502-install-windows-on-older-computers.html",
+    "href": "decisions/20240502-install-windows-on-older-computers.html",
+    "title": "Proposed: Enable Windows 11 Installation on Older Computers",
     "section": "",
-    "text": "Status: proposed \nDeciders: V-Sekai,fire,\nTags: V-Sekai,\n\n\n\nWant to list some useful tools for world and character creation and are free, open-source and remixable for commercial uses.\n\n\n\nThere many tools out there that are helpful for world and character creation.\n\n\n\n\nAn ESRGAN model made for upscaling normal maps. https://github.com/RunDevelopment/ESRGAN-models/tree/main/normals\nA Blender vrm addon. https://vrm-addon-for-blender.info/en/\nThe easiest way to install and use Stable Diffusion https://github.com/cmdr2/stable-diffusion-ui#installation\nImage prompt interrogator https://huggingface.co/spaces/pharma/CLIP-Interrogator/tree/main\nRepository for artwork and community for filming https://open3dlab.com/\nImage Upscaling GUI based on ESRGAN https://github.com/n00mkrad/cupscale\nDiscover trending open-source projects and their alternatives https://www.libhunt.com/\nHugging Face arrives to the Elixir community https://huggingface.co/blog/elixir-bumblebee\n\n\n\n\nA place to put related tools is helpful.\n\n\n\nA small amount of space and time is used.\n\n\n\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\n\nThese are not small tools.\n\n\n\nWriting down stuff that’s useful.\n\n\n\n\nV-Sekai\n\n\n\n\nMIT License\n\nCopyright (c) 2019-2022 K. S. Ernest (iFire) Lee (fire)\nCopyright (c) 2022 V-Sekai Contributors\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
+    "text": "Many users with older computers wish to upgrade to Windows 11, but face compatibility issues.\n\n\n\nFacilitating the installation of Windows 11 on older computer systems.\n\n\n\nThe following steps outline a method to bypass certain system requirements during the Windows 11 installation process:\n\nInitiate the Windows 11 installer.\nPress SHIFT + F10 to open the command prompt.\nEnter regedit and press Enter to open the registry editor.\nNavigate to HKEY_LOCAL_MACHINE\\SYSTEM\\Setup.\nCreate a new registry key under Setup named LabConfig.\nWithin LabConfig, create DWORD values named BypassTPMCheck and BypassSecureBootCheck, setting each to 1. If you also want to bypass the RAM requirement, add a DWORD value for BypassRAMCheck.\nClose both regedit and the command prompt. You should now be able to proceed with your Windows 11 installation.\n\n\n\n\n\nAllows users with older hardware to access Windows 11 features.\nExtends the lifespan of older devices.\n\n\n\n\n\nPotential security risks due to bypassing TPM and Secure Boot checks.\nPerformance may not be optimal on older hardware.\n\n\n\n\n\nUpgrading hardware to meet Windows 11 requirements.\nSticking with Windows 10 or other operating systems.\n\n\n\n\nThis proposal is primarily beneficial for users with older hardware who wish to use Windows 11.\n\n\n\nThis proposal is currently under consideration by the V-Sekai development team.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai Development Team\n\n\n\n\n\nV-Sekai\nWindows 11\nInstallation\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community.\nV-Sekai/v-sekai-game - The GitHub page for the V-Sekai open-source project.\nToms Hardware: bypass-windows-11-tpm-requirement\n\nAssisted by AI assistant Aria."
   },
   {
-    "objectID": "decisions/20221212-world-and-character-tools.html#context-and-problem-statement",
-    "href": "decisions/20221212-world-and-character-tools.html#context-and-problem-statement",
-    "title": "Proposed: Tools helpful for creating Avatars and Worlds",
+    "objectID": "decisions/20240502-install-windows-on-older-computers.html#context",
+    "href": "decisions/20240502-install-windows-on-older-computers.html#context",
+    "title": "Proposed: Enable Windows 11 Installation on Older Computers",
     "section": "",
-    "text": "Want to list some useful tools for world and character creation and are free, open-source and remixable for commercial uses."
+    "text": "Many users with older computers wish to upgrade to Windows 11, but face compatibility issues."
   },
   {
-    "objectID": "decisions/20221212-world-and-character-tools.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20221212-world-and-character-tools.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: Tools helpful for creating Avatars and Worlds",
+    "objectID": "decisions/20240502-install-windows-on-older-computers.html#problem-statement",
+    "href": "decisions/20240502-install-windows-on-older-computers.html#problem-statement",
+    "title": "Proposed: Enable Windows 11 Installation on Older Computers",
     "section": "",
-    "text": "There many tools out there that are helpful for world and character creation."
+    "text": "Facilitating the installation of Windows 11 on older computer systems."
   },
   {
-    "objectID": "decisions/20221212-world-and-character-tools.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20221212-world-and-character-tools.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Tools helpful for creating Avatars and Worlds",
+    "objectID": "decisions/20240502-install-windows-on-older-computers.html#solution-overview",
+    "href": "decisions/20240502-install-windows-on-older-computers.html#solution-overview",
+    "title": "Proposed: Enable Windows 11 Installation on Older Computers",
     "section": "",
-    "text": "An ESRGAN model made for upscaling normal maps. https://github.com/RunDevelopment/ESRGAN-models/tree/main/normals\nA Blender vrm addon. https://vrm-addon-for-blender.info/en/\nThe easiest way to install and use Stable Diffusion https://github.com/cmdr2/stable-diffusion-ui#installation\nImage prompt interrogator https://huggingface.co/spaces/pharma/CLIP-Interrogator/tree/main\nRepository for artwork and community for filming https://open3dlab.com/\nImage Upscaling GUI based on ESRGAN https://github.com/n00mkrad/cupscale\nDiscover trending open-source projects and their alternatives https://www.libhunt.com/\nHugging Face arrives to the Elixir community https://huggingface.co/blog/elixir-bumblebee"
+    "text": "The following steps outline a method to bypass certain system requirements during the Windows 11 installation process:\n\nInitiate the Windows 11 installer.\nPress SHIFT + F10 to open the command prompt.\nEnter regedit and press Enter to open the registry editor.\nNavigate to HKEY_LOCAL_MACHINE\\SYSTEM\\Setup.\nCreate a new registry key under Setup named LabConfig.\nWithin LabConfig, create DWORD values named BypassTPMCheck and BypassSecureBootCheck, setting each to 1. If you also want to bypass the RAM requirement, add a DWORD value for BypassRAMCheck.\nClose both regedit and the command prompt. You should now be able to proceed with your Windows 11 installation."
   },
   {
-    "objectID": "decisions/20221212-world-and-character-tools.html#positive-consequences",
-    "href": "decisions/20221212-world-and-character-tools.html#positive-consequences",
-    "title": "Proposed: Tools helpful for creating Avatars and Worlds",
+    "objectID": "decisions/20240502-install-windows-on-older-computers.html#benefits",
+    "href": "decisions/20240502-install-windows-on-older-computers.html#benefits",
+    "title": "Proposed: Enable Windows 11 Installation on Older Computers",
     "section": "",
-    "text": "A place to put related tools is helpful."
+    "text": "Allows users with older hardware to access Windows 11 features.\nExtends the lifespan of older devices."
   },
   {
-    "objectID": "decisions/20221212-world-and-character-tools.html#negative-consequences",
-    "href": "decisions/20221212-world-and-character-tools.html#negative-consequences",
-    "title": "Proposed: Tools helpful for creating Avatars and Worlds",
+    "objectID": "decisions/20240502-install-windows-on-older-computers.html#downsides",
+    "href": "decisions/20240502-install-windows-on-older-computers.html#downsides",
+    "title": "Proposed: Enable Windows 11 Installation on Older Computers",
     "section": "",
-    "text": "A small amount of space and time is used."
+    "text": "Potential security risks due to bypassing TPM and Secure Boot checks.\nPerformance may not be optimal on older hardware."
   },
   {
-    "objectID": "decisions/20221212-world-and-character-tools.html#option-graveyard",
-    "href": "decisions/20221212-world-and-character-tools.html#option-graveyard",
-    "title": "Proposed: Tools helpful for creating Avatars and Worlds",
+    "objectID": "decisions/20240502-install-windows-on-older-computers.html#alternatives-considered",
+    "href": "decisions/20240502-install-windows-on-older-computers.html#alternatives-considered",
+    "title": "Proposed: Enable Windows 11 Installation on Older Computers",
     "section": "",
-    "text": "Option: The status quo. \nRejection Reason: This solves nothing."
+    "text": "Upgrading hardware to meet Windows 11 requirements.\nSticking with Windows 10 or other operating systems."
   },
   {
-    "objectID": "decisions/20221212-world-and-character-tools.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20221212-world-and-character-tools.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Tools helpful for creating Avatars and Worlds",
+    "objectID": "decisions/20240502-install-windows-on-older-computers.html#infrequent-use-case",
+    "href": "decisions/20240502-install-windows-on-older-computers.html#infrequent-use-case",
+    "title": "Proposed: Enable Windows 11 Installation on Older Computers",
     "section": "",
-    "text": "These are not small tools."
+    "text": "This proposal is primarily beneficial for users with older hardware who wish to use Windows 11."
   },
   {
-    "objectID": "decisions/20221212-world-and-character-tools.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20221212-world-and-character-tools.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Tools helpful for creating Avatars and Worlds",
+    "objectID": "decisions/20240502-install-windows-on-older-computers.html#in-core-and-done-by-us",
+    "href": "decisions/20240502-install-windows-on-older-computers.html#in-core-and-done-by-us",
+    "title": "Proposed: Enable Windows 11 Installation on Older Computers",
     "section": "",
-    "text": "Writing down stuff that’s useful."
+    "text": "This proposal is currently under consideration by the V-Sekai development team."
   },
   {
-    "objectID": "decisions/20221212-world-and-character-tools.html#references",
-    "href": "decisions/20221212-world-and-character-tools.html#references",
-    "title": "Proposed: Tools helpful for creating Avatars and Worlds",
+    "objectID": "decisions/20240502-install-windows-on-older-computers.html#status",
+    "href": "decisions/20240502-install-windows-on-older-computers.html#status",
+    "title": "Proposed: Enable Windows 11 Installation on Older Computers",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20221212-world-and-character-tools.html#license-of-the-contribution",
-    "href": "decisions/20221212-world-and-character-tools.html#license-of-the-contribution",
-    "title": "Proposed: Tools helpful for creating Avatars and Worlds",
+    "objectID": "decisions/20240502-install-windows-on-older-computers.html#decision-makers",
+    "href": "decisions/20240502-install-windows-on-older-computers.html#decision-makers",
+    "title": "Proposed: Enable Windows 11 Installation on Older Computers",
     "section": "",
-    "text": "MIT License\n\nCopyright (c) 2019-2022 K. S. Ernest (iFire) Lee (fire)\nCopyright (c) 2022 V-Sekai Contributors\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
+    "text": "V-Sekai Development Team"
   },
   {
-    "objectID": "decisions/20240218-blender-to-godot.html",
-    "href": "decisions/20240218-blender-to-godot.html",
-    "title": "Proposed: Blender to Godot API Conversion",
+    "objectID": "decisions/20240502-install-windows-on-older-computers.html#tags",
+    "href": "decisions/20240502-install-windows-on-older-computers.html#tags",
+    "title": "Proposed: Enable Windows 11 Installation on Older Computers",
     "section": "",
-    "text": "The current project involves transferring scene tree, mesh data, animation data, and sometimes textures from Blender to Godot. There are challenges due to extra data hiding in metadata and the shifting Blender API.\n\n\n\nThe Blender API keeps changing, causing issues with the transfer of data to Godot. Additionally, dumping all properties from Blender can cause crashes.\n\n\n\nInstead of trying to adapt to the shifting Blender API, we propose to keep the Blender API the same and create a converter on the Godot side. This way, the Blender side only needs to focus on sending/linking data, while Godot handles the conversion and integration.\n\n\n\n\nReduces dependency on Blender’s shifting API.\nSimplifies the process for engineers on both Blender and Godot sides.\nMakes it easier to update if things change.\n\n\n\n\n\nRequires development of a robust converter on the Godot side.\nAny changes in Blender’s data structure might still require updates to the converter.\n\n\n\n\nAn alternative approach would be to continually adapt to the shifting Blender API, but this could lead to more complex maintenance and potential crashes.\n\n\n\nIn cases where there is additional metadata or other non-standard data types, these would need to be handled separately by the converter.\n\n\n\nThis proposal suggests a core change in our approach to handling Blender data, moving the conversion responsibility to the Godot side.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team and community stakeholders.\n\n\n\n\n\nV-Sekai, Blender, Godot, API Conversion\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "V-Sekai\nWindows 11\nInstallation"
   },
   {
-    "objectID": "decisions/20240218-blender-to-godot.html#the-context",
-    "href": "decisions/20240218-blender-to-godot.html#the-context",
-    "title": "Proposed: Blender to Godot API Conversion",
+    "objectID": "decisions/20240502-install-windows-on-older-computers.html#further-reading",
+    "href": "decisions/20240502-install-windows-on-older-computers.html#further-reading",
+    "title": "Proposed: Enable Windows 11 Installation on Older Computers",
     "section": "",
-    "text": "The current project involves transferring scene tree, mesh data, animation data, and sometimes textures from Blender to Godot. There are challenges due to extra data hiding in metadata and the shifting Blender API."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community.\nV-Sekai/v-sekai-game - The GitHub page for the V-Sekai open-source project.\nToms Hardware: bypass-windows-11-tpm-requirement\n\nAssisted by AI assistant Aria."
   },
   {
-    "objectID": "decisions/20240218-blender-to-godot.html#the-problem-statement",
-    "href": "decisions/20240218-blender-to-godot.html#the-problem-statement",
-    "title": "Proposed: Blender to Godot API Conversion",
+    "objectID": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html",
+    "href": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html",
+    "title": "Accepted: Allow cicd to pass by fixing spatial audio branch",
     "section": "",
-    "text": "The Blender API keeps changing, causing issues with the transfer of data to Godot. Additionally, dumping all properties from Blender can cause crashes."
+    "text": "Status: accepted \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nCICD not passing causes quality to degrade.\n\n\n\nFix spatial audio branch of godot engine.\n\n\n\n\nResolve static checks\nFix platform errors.\n\n\n\n\n\nGood estimates of the work required.\n\n\n\n\n\nCICD passing is a chore.\n\n\n\n\n\nOption: Current status.\nRejection Reason: It’s bad to leave cicd broken.\n\n\n\n\nNot a few lines.\n\n\n\nWe are the maintainers.\n\n\n\n\nSpatial Audio branch\n\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240218-blender-to-godot.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240218-blender-to-godot.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Blender to Godot API Conversion",
+    "objectID": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html#context-and-problem-statement",
+    "href": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html#context-and-problem-statement",
+    "title": "Accepted: Allow cicd to pass by fixing spatial audio branch",
     "section": "",
-    "text": "Instead of trying to adapt to the shifting Blender API, we propose to keep the Blender API the same and create a converter on the Godot side. This way, the Blender side only needs to focus on sending/linking data, while Godot handles the conversion and integration."
+    "text": "CICD not passing causes quality to degrade."
   },
   {
-    "objectID": "decisions/20240218-blender-to-godot.html#the-benefits",
-    "href": "decisions/20240218-blender-to-godot.html#the-benefits",
-    "title": "Proposed: Blender to Godot API Conversion",
+    "objectID": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Accepted: Allow cicd to pass by fixing spatial audio branch",
     "section": "",
-    "text": "Reduces dependency on Blender’s shifting API.\nSimplifies the process for engineers on both Blender and Godot sides.\nMakes it easier to update if things change."
+    "text": "Fix spatial audio branch of godot engine."
   },
   {
-    "objectID": "decisions/20240218-blender-to-godot.html#the-downsides",
-    "href": "decisions/20240218-blender-to-godot.html#the-downsides",
-    "title": "Proposed: Blender to Godot API Conversion",
+    "objectID": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Accepted: Allow cicd to pass by fixing spatial audio branch",
     "section": "",
-    "text": "Requires development of a robust converter on the Godot side.\nAny changes in Blender’s data structure might still require updates to the converter."
+    "text": "Resolve static checks\nFix platform errors."
   },
   {
-    "objectID": "decisions/20240218-blender-to-godot.html#the-road-not-taken",
-    "href": "decisions/20240218-blender-to-godot.html#the-road-not-taken",
-    "title": "Proposed: Blender to Godot API Conversion",
+    "objectID": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html#positive-consequences",
+    "href": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html#positive-consequences",
+    "title": "Accepted: Allow cicd to pass by fixing spatial audio branch",
     "section": "",
-    "text": "An alternative approach would be to continually adapt to the shifting Blender API, but this could lead to more complex maintenance and potential crashes."
+    "text": "Good estimates of the work required."
   },
   {
-    "objectID": "decisions/20240218-blender-to-godot.html#the-infrequent-use-case",
-    "href": "decisions/20240218-blender-to-godot.html#the-infrequent-use-case",
-    "title": "Proposed: Blender to Godot API Conversion",
+    "objectID": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html#negative-consequences",
+    "href": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html#negative-consequences",
+    "title": "Accepted: Allow cicd to pass by fixing spatial audio branch",
     "section": "",
-    "text": "In cases where there is additional metadata or other non-standard data types, these would need to be handled separately by the converter."
+    "text": "CICD passing is a chore."
   },
   {
-    "objectID": "decisions/20240218-blender-to-godot.html#in-core-and-done-by-us",
-    "href": "decisions/20240218-blender-to-godot.html#in-core-and-done-by-us",
-    "title": "Proposed: Blender to Godot API Conversion",
+    "objectID": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html#option-graveyard",
+    "href": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html#option-graveyard",
+    "title": "Accepted: Allow cicd to pass by fixing spatial audio branch",
     "section": "",
-    "text": "This proposal suggests a core change in our approach to handling Blender data, moving the conversion responsibility to the Godot side."
+    "text": "Option: Current status.\nRejection Reason: It’s bad to leave cicd broken."
   },
   {
-    "objectID": "decisions/20240218-blender-to-godot.html#status",
-    "href": "decisions/20240218-blender-to-godot.html#status",
-    "title": "Proposed: Blender to Godot API Conversion",
+    "objectID": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Accepted: Allow cicd to pass by fixing spatial audio branch",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "Not a few lines."
   },
   {
-    "objectID": "decisions/20240218-blender-to-godot.html#decision-makers",
-    "href": "decisions/20240218-blender-to-godot.html#decision-makers",
-    "title": "Proposed: Blender to Godot API Conversion",
+    "objectID": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Accepted: Allow cicd to pass by fixing spatial audio branch",
     "section": "",
-    "text": "V-Sekai development team and community stakeholders."
+    "text": "We are the maintainers."
   },
   {
-    "objectID": "decisions/20240218-blender-to-godot.html#tags",
-    "href": "decisions/20240218-blender-to-godot.html#tags",
-    "title": "Proposed: Blender to Godot API Conversion",
+    "objectID": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html#references",
+    "href": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html#references",
+    "title": "Accepted: Allow cicd to pass by fixing spatial audio branch",
     "section": "",
-    "text": "V-Sekai, Blender, Godot, API Conversion"
+    "text": "Spatial Audio branch"
   },
   {
-    "objectID": "decisions/20240218-blender-to-godot.html#further-reading",
-    "href": "decisions/20240218-blender-to-godot.html#further-reading",
-    "title": "Proposed: Blender to Godot API Conversion",
+    "objectID": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html#derivative-license",
+    "href": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html#derivative-license",
+    "title": "Accepted: Allow cicd to pass by fixing spatial audio branch",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20241001-small-game-tools.html",
-    "href": "decisions/20241001-small-game-tools.html",
-    "title": "Proposed: Small V-Sekai Creation Tools",
+    "objectID": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html",
+    "href": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html",
+    "title": "Proposed: Use shrink wrap blender modifier to fit",
     "section": "",
-    "text": "The Godot Editor now integrates a 2D editor on a screen for VR, which cannot be fully optimized for VR screens like the Meta Quest 3. However, the Quest 3’s multiwindow support offers new possibilities.\n\n\n\nWe want to create a suite of tools for V-Sekai game development that leverages the capabilities of current hardware without requiring full VR integration.\n\n\n\nDevelop a series of small, efficient tools that can connect remotely to the V-Sekai game project, facilitating world creation and other development tasks from a 2D interface displayed within a VR environment.\n\n\n\n\nEnhanced Accessibility: Developers can use tools within a VR environment without the need for full VR tool conversion, combining comfort with functionality.\nReal-Time Interaction: Enables immediate feedback and interaction with the game world, enhancing development speed and efficiency.\nInnovative Approach: By using a hybrid approach, V-Sekai remains at the cutting edge, integrating new technologies while maintaining usability.\n\n\n\n\n\nTechnical Challenges: Creating tools that function seamlessly between 2D and VR environments is complex and may require significant resources.\nUser Adaptation: There might be a learning curve as developers adjust to using a 2D interface in a VR context.\nHardware Limitations: The performance and functionality are still bound by the limitations of existing VR hardware like the Meta Quest 3.\n\n\n\n\nFull VR development tools and augmented reality interfaces were considered but deemed not yet viable for our goals due to current technological constraints and development focus.\n\n\n\nFor developers who prefer traditional desktop-based environments, or where VR integration provides no clear advantage, existing non-VR tools will continue to be supported and developed.\n\n\n\nThis initiative aligns with our core mission to innovate within accessible VR and game development tools, and will be developed internally by the V-Sekai team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\nHumbletim\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "Want to make an avatar clothing for VRChat.\n\n\n\nOur cloth shirt is too baggy, we want to fit to the person.\n\n\n\n\nUse modifier shrinkswap in Blender 3d modeling tool.\nNearest surface points\nAbove surface\nTarget the body of the character\nOffset 2 mm.\n\n\n\n\n\nImproved Fit: Ensures that the clothing fits snugly to the avatar’s body.\nEnhanced Appearance: Provides a more realistic and appealing look for the avatar.\nCustomization: Allows for easy adjustments to fit different body types.\n\n\n\n\n\nComplexity: Requires familiarity with Blender and its modifiers.\nTime-Consuming: Initial setup and fine-tuning may take time.\n\n\n\n\nAlternative methods such as manual adjustment or using other software tools were considered but found to be less efficient or effective.\n\n\n\nIn scenarios where highly detailed or custom-fitted clothing is required, additional manual adjustments may be necessary to achieve the desired result.\n\n\n\nWe need to fill in a starter list of content.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20241001-small-game-tools.html#the-context",
-    "href": "decisions/20241001-small-game-tools.html#the-context",
-    "title": "Proposed: Small V-Sekai Creation Tools",
+    "objectID": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#the-context",
+    "href": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#the-context",
+    "title": "Proposed: Use shrink wrap blender modifier to fit",
     "section": "",
-    "text": "The Godot Editor now integrates a 2D editor on a screen for VR, which cannot be fully optimized for VR screens like the Meta Quest 3. However, the Quest 3’s multiwindow support offers new possibilities."
+    "text": "Want to make an avatar clothing for VRChat."
   },
   {
-    "objectID": "decisions/20241001-small-game-tools.html#the-problem-statement",
-    "href": "decisions/20241001-small-game-tools.html#the-problem-statement",
-    "title": "Proposed: Small V-Sekai Creation Tools",
+    "objectID": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#the-problem-statement",
+    "href": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#the-problem-statement",
+    "title": "Proposed: Use shrink wrap blender modifier to fit",
     "section": "",
-    "text": "We want to create a suite of tools for V-Sekai game development that leverages the capabilities of current hardware without requiring full VR integration."
+    "text": "Our cloth shirt is too baggy, we want to fit to the person."
   },
   {
-    "objectID": "decisions/20241001-small-game-tools.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20241001-small-game-tools.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Small V-Sekai Creation Tools",
+    "objectID": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Use shrink wrap blender modifier to fit",
     "section": "",
-    "text": "Develop a series of small, efficient tools that can connect remotely to the V-Sekai game project, facilitating world creation and other development tasks from a 2D interface displayed within a VR environment."
+    "text": "Use modifier shrinkswap in Blender 3d modeling tool.\nNearest surface points\nAbove surface\nTarget the body of the character\nOffset 2 mm."
   },
   {
-    "objectID": "decisions/20241001-small-game-tools.html#the-benefits",
-    "href": "decisions/20241001-small-game-tools.html#the-benefits",
-    "title": "Proposed: Small V-Sekai Creation Tools",
+    "objectID": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#the-benefits",
+    "href": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#the-benefits",
+    "title": "Proposed: Use shrink wrap blender modifier to fit",
     "section": "",
-    "text": "Enhanced Accessibility: Developers can use tools within a VR environment without the need for full VR tool conversion, combining comfort with functionality.\nReal-Time Interaction: Enables immediate feedback and interaction with the game world, enhancing development speed and efficiency.\nInnovative Approach: By using a hybrid approach, V-Sekai remains at the cutting edge, integrating new technologies while maintaining usability."
+    "text": "Improved Fit: Ensures that the clothing fits snugly to the avatar’s body.\nEnhanced Appearance: Provides a more realistic and appealing look for the avatar.\nCustomization: Allows for easy adjustments to fit different body types."
   },
   {
-    "objectID": "decisions/20241001-small-game-tools.html#the-downsides",
-    "href": "decisions/20241001-small-game-tools.html#the-downsides",
-    "title": "Proposed: Small V-Sekai Creation Tools",
+    "objectID": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#the-downsides",
+    "href": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#the-downsides",
+    "title": "Proposed: Use shrink wrap blender modifier to fit",
     "section": "",
-    "text": "Technical Challenges: Creating tools that function seamlessly between 2D and VR environments is complex and may require significant resources.\nUser Adaptation: There might be a learning curve as developers adjust to using a 2D interface in a VR context.\nHardware Limitations: The performance and functionality are still bound by the limitations of existing VR hardware like the Meta Quest 3."
+    "text": "Complexity: Requires familiarity with Blender and its modifiers.\nTime-Consuming: Initial setup and fine-tuning may take time."
   },
   {
-    "objectID": "decisions/20241001-small-game-tools.html#the-road-not-taken",
-    "href": "decisions/20241001-small-game-tools.html#the-road-not-taken",
-    "title": "Proposed: Small V-Sekai Creation Tools",
+    "objectID": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#the-road-not-taken",
+    "href": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#the-road-not-taken",
+    "title": "Proposed: Use shrink wrap blender modifier to fit",
     "section": "",
-    "text": "Full VR development tools and augmented reality interfaces were considered but deemed not yet viable for our goals due to current technological constraints and development focus."
+    "text": "Alternative methods such as manual adjustment or using other software tools were considered but found to be less efficient or effective."
   },
   {
-    "objectID": "decisions/20241001-small-game-tools.html#the-infrequent-use-case",
-    "href": "decisions/20241001-small-game-tools.html#the-infrequent-use-case",
-    "title": "Proposed: Small V-Sekai Creation Tools",
+    "objectID": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#the-infrequent-use-case",
+    "href": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#the-infrequent-use-case",
+    "title": "Proposed: Use shrink wrap blender modifier to fit",
     "section": "",
-    "text": "For developers who prefer traditional desktop-based environments, or where VR integration provides no clear advantage, existing non-VR tools will continue to be supported and developed."
+    "text": "In scenarios where highly detailed or custom-fitted clothing is required, additional manual adjustments may be necessary to achieve the desired result."
   },
   {
-    "objectID": "decisions/20241001-small-game-tools.html#in-core-and-done-by-us",
-    "href": "decisions/20241001-small-game-tools.html#in-core-and-done-by-us",
-    "title": "Proposed: Small V-Sekai Creation Tools",
+    "objectID": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#in-core-and-done-by-us",
+    "href": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#in-core-and-done-by-us",
+    "title": "Proposed: Use shrink wrap blender modifier to fit",
     "section": "",
-    "text": "This initiative aligns with our core mission to innovate within accessible VR and game development tools, and will be developed internally by the V-Sekai team."
+    "text": "We need to fill in a starter list of content."
   },
   {
-    "objectID": "decisions/20241001-small-game-tools.html#status",
-    "href": "decisions/20241001-small-game-tools.html#status",
-    "title": "Proposed: Small V-Sekai Creation Tools",
+    "objectID": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#status",
+    "href": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#status",
+    "title": "Proposed: Use shrink wrap blender modifier to fit",
     "section": "",
     "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20241001-small-game-tools.html#decision-makers",
-    "href": "decisions/20241001-small-game-tools.html#decision-makers",
-    "title": "Proposed: Small V-Sekai Creation Tools",
+    "objectID": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#decision-makers",
+    "href": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#decision-makers",
+    "title": "Proposed: Use shrink wrap blender modifier to fit",
     "section": "",
-    "text": "V-Sekai development team\nHumbletim"
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20241001-small-game-tools.html#tags",
-    "href": "decisions/20241001-small-game-tools.html#tags",
-    "title": "Proposed: Small V-Sekai Creation Tools",
+    "objectID": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#tags",
+    "href": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#tags",
+    "title": "Proposed: Use shrink wrap blender modifier to fit",
     "section": "",
     "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20241001-small-game-tools.html#further-reading",
-    "href": "decisions/20241001-small-game-tools.html#further-reading",
-    "title": "Proposed: Small V-Sekai Creation Tools",
+    "objectID": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#further-reading",
+    "href": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#further-reading",
+    "title": "Proposed: Use shrink wrap blender modifier to fit",
     "section": "",
     "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20211031-make-a-place-to-record.html",
-    "href": "decisions/20211031-make-a-place-to-record.html",
-    "title": "Proposed: Make a place to record",
-    "section": "",
-    "text": "Proposed: Make a place to record\n\nContext and Problem Statement\nStages are useful to record motion\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nCreate a stage for 3d avatars to move.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nCreate a 3d environment\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nThis is artwork.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nCan be requested.\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
-  },
-  {
-    "objectID": "decisions/20230911-first-alpha-tag.html",
-    "href": "decisions/20230911-first-alpha-tag.html",
-    "title": "Proposed: Implementing Semantic Versioning for Alpha Releases in V-Sekai",
+    "objectID": "decisions/20230108-bolster-creating-the-metaverse.html",
+    "href": "decisions/20230108-bolster-creating-the-metaverse.html",
+    "title": "Accepted: Bolster creating the metaverse",
     "section": "",
-    "text": "Status: Proposed \nDeciders: V-Sekai\nTags: V-Sekai, Semantic Versioning, Alpha Release\n\n\n\n\nIn software development, semantic versioning (semver) is a popular method for versioning software. It provides a clear and concise way to communicate changes in versions and the associated implications.\n\n\n\nThe challenge lies in correctly denoting the first alpha release in semver. This is crucial as it communicates the stability of the software and sets expectations for users and developers.\n\n\n\nIn semver, the first alpha release would typically be denoted with a hyphen followed by the word “alpha” and a number. For example, it could be something like “0.1.0-alpha.1”. The specific alpha release number may vary depending on the project and its release cycle.\n\n\n\nUsing semver for alpha releases helps to set clear expectations about the stability and features of the software. It allows developers and users to understand that the software is in an early stage of development and may not yet have all planned features or be fully stable.\n\n\n\nThe downside could be the potential confusion around the naming convention, especially for those unfamiliar with semver. However, this can be mitigated through clear documentation and communication.\n\n\n\nAn alternative approach could be to use a different versioning system or to not denote alpha releases specifically. However, these approaches may not provide the same level of clarity and communication as semver.\n\n\n\nWhile the alpha release notation is common in semver, it may not be used frequently in projects that have shorter development cycles or that do not release alpha versions to the public.\n\n\n\nYes, this strategy of using semver for denoting alpha releases is a core part of the V-Sekai project management and release process.\n\n\n\n\n[V-Sekai] - AI assists this article.\nSemantic Versioning"
+    "text": "Status: accepted \n\n\n\nThe metaverse needs creators.\n\nOpen Metaverse Interoperability Group’s mission: We bolster the metaverse as an open and interoperable resource for anyone, inspired by the collaborative efforts of the community.\n\n\nThe Open Metaverse Interoperability Group is focused on bridging virtual worlds by designing and promoting protocols for identity, social graphs, inventory, and more. Our members include businesses and individuals working towards this common goal. Aside from technical work, OMI aims to create a community of artists, creators, developers, and other innovators to discuss and explore concepts surrounding the design and development of virtual worlds. OMI Core Values\n\n\nWe collaborate, driven by research, privacy and accessibility, to make the metaverse more human.\nWe work incrementally, iteratively, and with intent.\nWe are creating a cooperative, sustainable culture of innovation.\nWe empower the people making the metaverse.\nWe must cultivate resiliency by championing diversity, and freedom of choice.\n\n\n\n\nWe propose to create a V-Sekai #guide to creating the metaverse, creating your own virtual you and creating a part of the world. This can be a collaboration with others to provide matching #guide to other metaverses.\n\n\n\nLearn from how experienced educators how to bloster new creators.\n\n\n\n\nMore creators are available.\n\n\n\n\n\nEffort and time are spent for unknown results.\n\n\n\n\n\nOption: \nRejection Reason: \n\n\n\n\nNot a coding script, but can be a #guide script.\n\n\n\nOnly we can create official V-Sekai guides.\n\n\n\n\nhttps://v-sekai.org/\n\n\n\n\nCopyright (c) 2020-present V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230911-first-alpha-tag.html#metadata",
-    "href": "decisions/20230911-first-alpha-tag.html#metadata",
-    "title": "Proposed: Implementing Semantic Versioning for Alpha Releases in V-Sekai",
+    "objectID": "decisions/20230108-bolster-creating-the-metaverse.html#context-and-problem-statement",
+    "href": "decisions/20230108-bolster-creating-the-metaverse.html#context-and-problem-statement",
+    "title": "Accepted: Bolster creating the metaverse",
     "section": "",
-    "text": "Status: Proposed \nDeciders: V-Sekai\nTags: V-Sekai, Semantic Versioning, Alpha Release"
+    "text": "The metaverse needs creators.\n\nOpen Metaverse Interoperability Group’s mission: We bolster the metaverse as an open and interoperable resource for anyone, inspired by the collaborative efforts of the community.\n\n\nThe Open Metaverse Interoperability Group is focused on bridging virtual worlds by designing and promoting protocols for identity, social graphs, inventory, and more. Our members include businesses and individuals working towards this common goal. Aside from technical work, OMI aims to create a community of artists, creators, developers, and other innovators to discuss and explore concepts surrounding the design and development of virtual worlds. OMI Core Values\n\n\nWe collaborate, driven by research, privacy and accessibility, to make the metaverse more human.\nWe work incrementally, iteratively, and with intent.\nWe are creating a cooperative, sustainable culture of innovation.\nWe empower the people making the metaverse.\nWe must cultivate resiliency by championing diversity, and freedom of choice."
   },
   {
-    "objectID": "decisions/20230911-first-alpha-tag.html#the-backdrop",
-    "href": "decisions/20230911-first-alpha-tag.html#the-backdrop",
-    "title": "Proposed: Implementing Semantic Versioning for Alpha Releases in V-Sekai",
+    "objectID": "decisions/20230108-bolster-creating-the-metaverse.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20230108-bolster-creating-the-metaverse.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Accepted: Bolster creating the metaverse",
     "section": "",
-    "text": "In software development, semantic versioning (semver) is a popular method for versioning software. It provides a clear and concise way to communicate changes in versions and the associated implications."
+    "text": "We propose to create a V-Sekai #guide to creating the metaverse, creating your own virtual you and creating a part of the world. This can be a collaboration with others to provide matching #guide to other metaverses."
   },
   {
-    "objectID": "decisions/20230911-first-alpha-tag.html#the-challenge",
-    "href": "decisions/20230911-first-alpha-tag.html#the-challenge",
-    "title": "Proposed: Implementing Semantic Versioning for Alpha Releases in V-Sekai",
+    "objectID": "decisions/20230108-bolster-creating-the-metaverse.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20230108-bolster-creating-the-metaverse.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Accepted: Bolster creating the metaverse",
     "section": "",
-    "text": "The challenge lies in correctly denoting the first alpha release in semver. This is crucial as it communicates the stability of the software and sets expectations for users and developers."
+    "text": "Learn from how experienced educators how to bloster new creators."
   },
   {
-    "objectID": "decisions/20230911-first-alpha-tag.html#the-strategy",
-    "href": "decisions/20230911-first-alpha-tag.html#the-strategy",
-    "title": "Proposed: Implementing Semantic Versioning for Alpha Releases in V-Sekai",
+    "objectID": "decisions/20230108-bolster-creating-the-metaverse.html#positive-consequences",
+    "href": "decisions/20230108-bolster-creating-the-metaverse.html#positive-consequences",
+    "title": "Accepted: Bolster creating the metaverse",
     "section": "",
-    "text": "In semver, the first alpha release would typically be denoted with a hyphen followed by the word “alpha” and a number. For example, it could be something like “0.1.0-alpha.1”. The specific alpha release number may vary depending on the project and its release cycle."
+    "text": "More creators are available."
   },
   {
-    "objectID": "decisions/20230911-first-alpha-tag.html#the-upside",
-    "href": "decisions/20230911-first-alpha-tag.html#the-upside",
-    "title": "Proposed: Implementing Semantic Versioning for Alpha Releases in V-Sekai",
+    "objectID": "decisions/20230108-bolster-creating-the-metaverse.html#negative-consequences",
+    "href": "decisions/20230108-bolster-creating-the-metaverse.html#negative-consequences",
+    "title": "Accepted: Bolster creating the metaverse",
     "section": "",
-    "text": "Using semver for alpha releases helps to set clear expectations about the stability and features of the software. It allows developers and users to understand that the software is in an early stage of development and may not yet have all planned features or be fully stable."
+    "text": "Effort and time are spent for unknown results."
   },
   {
-    "objectID": "decisions/20230911-first-alpha-tag.html#the-downside",
-    "href": "decisions/20230911-first-alpha-tag.html#the-downside",
-    "title": "Proposed: Implementing Semantic Versioning for Alpha Releases in V-Sekai",
+    "objectID": "decisions/20230108-bolster-creating-the-metaverse.html#option-graveyard",
+    "href": "decisions/20230108-bolster-creating-the-metaverse.html#option-graveyard",
+    "title": "Accepted: Bolster creating the metaverse",
     "section": "",
-    "text": "The downside could be the potential confusion around the naming convention, especially for those unfamiliar with semver. However, this can be mitigated through clear documentation and communication."
+    "text": "Option: \nRejection Reason:"
   },
   {
-    "objectID": "decisions/20230911-first-alpha-tag.html#the-road-not-taken",
-    "href": "decisions/20230911-first-alpha-tag.html#the-road-not-taken",
-    "title": "Proposed: Implementing Semantic Versioning for Alpha Releases in V-Sekai",
+    "objectID": "decisions/20230108-bolster-creating-the-metaverse.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230108-bolster-creating-the-metaverse.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Accepted: Bolster creating the metaverse",
     "section": "",
-    "text": "An alternative approach could be to use a different versioning system or to not denote alpha releases specifically. However, these approaches may not provide the same level of clarity and communication as semver."
+    "text": "Not a coding script, but can be a #guide script."
   },
   {
-    "objectID": "decisions/20230911-first-alpha-tag.html#the-infrequent-use-case",
-    "href": "decisions/20230911-first-alpha-tag.html#the-infrequent-use-case",
-    "title": "Proposed: Implementing Semantic Versioning for Alpha Releases in V-Sekai",
+    "objectID": "decisions/20230108-bolster-creating-the-metaverse.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230108-bolster-creating-the-metaverse.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Accepted: Bolster creating the metaverse",
     "section": "",
-    "text": "While the alpha release notation is common in semver, it may not be used frequently in projects that have shorter development cycles or that do not release alpha versions to the public."
+    "text": "Only we can create official V-Sekai guides."
   },
   {
-    "objectID": "decisions/20230911-first-alpha-tag.html#in-core-and-done-by-us",
-    "href": "decisions/20230911-first-alpha-tag.html#in-core-and-done-by-us",
-    "title": "Proposed: Implementing Semantic Versioning for Alpha Releases in V-Sekai",
+    "objectID": "decisions/20230108-bolster-creating-the-metaverse.html#references",
+    "href": "decisions/20230108-bolster-creating-the-metaverse.html#references",
+    "title": "Accepted: Bolster creating the metaverse",
     "section": "",
-    "text": "Yes, this strategy of using semver for denoting alpha releases is a core part of the V-Sekai project management and release process."
+    "text": "https://v-sekai.org/"
   },
   {
-    "objectID": "decisions/20230911-first-alpha-tag.html#further-reading",
-    "href": "decisions/20230911-first-alpha-tag.html#further-reading",
-    "title": "Proposed: Implementing Semantic Versioning for Alpha Releases in V-Sekai",
+    "objectID": "decisions/20230108-bolster-creating-the-metaverse.html#derivative-license",
+    "href": "decisions/20230108-bolster-creating-the-metaverse.html#derivative-license",
+    "title": "Accepted: Bolster creating the metaverse",
     "section": "",
-    "text": "[V-Sekai] - AI assists this article.\nSemantic Versioning"
+    "text": "Copyright (c) 2020-present V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20220203-create-default-animation-set.html",
-    "href": "decisions/20220203-create-default-animation-set.html",
-    "title": "Draft: To have a default set of motions on a 3d character by creating a default animation set",
+    "objectID": "decisions/20240325-fdb-sqlite-blender-godot.html",
+    "href": "decisions/20240325-fdb-sqlite-blender-godot.html",
+    "title": "Proposed: Synchronizing Blender and FDB-SQLite for Proxy Movement",
     "section": "",
-    "text": "Status: draft \nDeciders: V-Sekai,tokage,fire,\nTags: V-Sekai,\n\n\n\nWanted to have a default list of animations set.\n\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\n\n\n\n\n\n\nInit\nNeutralFront\nNeutralRight\nNeutralLeft\nWalkFront\nWalkBack\nWalkRightFront\nWalkRightBack\nWalkLeftFront\nWalkLeftBack\nStrafeRight\nStrafeLeft\nSprintFront\nSprintBack\nSprintRightFront\nSprintRightBack\nSprintLeftFront\nSprintLeftFrontBack\nJump\nFall\nLand\n\n\n\n\nSit\n(NeutralToSit)\n(SitToNeutral)\nLay\n(NeutralToLay)\n(LayToNeutral)\n\n\n\n\n\nDuckNeutral\nDuckMoveFront\nDuckMoveBack\nDuckMoveRight\nDuckMoveLeft\n(DuckToSit)\n(SitToDuck)\n(DuckToLay)\n(LayToDuck)\nCrawlNeutral\nCrawlMoveFront\nCrawlMoveBack\nCrawlMoveRight\nCrawlMoveLeft\n(CrawlToSit)\n(SitToCrawl)\n(CrawlToLay)\n(LayToCrawl)\n(NeutralToDuck)\n(DuckToNeutral)\n(NeutralToCrawl)\n(CrawlToNeutral)\n(DuckToCrawl)\n(CrawlToDuck)\n\n\n\n\n\nChair\n\n\n\n\n\n\n\n[e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]\n\n\n\n\n\n[e.g., compromising quality attribute, follow-up decisions required, …]\n\n[this section can be repeated for each option if more than one option is open for consideration]\n\n\n\n\nOption: \nRejection Reason: \n\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\n\n\n\nIs there a reason why this should be core and done by us?\n\n\n\n\nLink type \n\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Blender is a powerful open-source 3D creation suite that supports the entirety of the 3D pipeline. On the other hand, FDB-SQLite is a SQL layer built on top of the key-value store FoundationDB. The goal is to synchronize these two systems to proxy movement.\n\n\n\nThe challenge is to create a system where movements made in Blender are reflected in the FDB-SQLite database. This would allow for real-time tracking and manipulation of 3D models in a database environment.\n\n\n\nWe can achieve this by creating an interface between Blender and FDB-SQLite. This interface will listen for changes in Blender and update the corresponding entries in the FDB-SQLite database.\nclass BlenderFDBInterface:\n    def __init__(self, blender, fdb):\n        self.blender = blender\n        self.fdb = fdb\n\n    def sync(self):\n        # Get current state from Blender\n        state = self.blender.get_state()\n\n        # Update FDB with current state\n        self.fdb.update(state)\n\n\n\n\nReal-time synchronization between Blender and FDB-SQLite.\nAllows for complex queries and manipulations on 3D model data.\nOpens up possibilities for advanced analytics and machine learning applications.\n\n\n\n\n\nRequires careful management of database transactions to avoid conflicts.\nPotential performance issues due to constant syncing.\n\n\n\n\nAn alternative approach could be to use a different database system that has built-in support for 3D data. However, this would require migrating all existing data and potentially reworking other parts of the system.\n\n\n\nThis solution may not be suitable for scenarios where the 3D models are rarely updated, as the constant syncing could be unnecessary overhead.\n\n\n\nThis feature will be developed by our in-house team, ensuring that it fits seamlessly into our existing infrastructure.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20220203-create-default-animation-set.html#context-and-problem-statement",
-    "href": "decisions/20220203-create-default-animation-set.html#context-and-problem-statement",
-    "title": "Draft: To have a default set of motions on a 3d character by creating a default animation set",
+    "objectID": "decisions/20240325-fdb-sqlite-blender-godot.html#context",
+    "href": "decisions/20240325-fdb-sqlite-blender-godot.html#context",
+    "title": "Proposed: Synchronizing Blender and FDB-SQLite for Proxy Movement",
     "section": "",
-    "text": "Wanted to have a default list of animations set."
+    "text": "Blender is a powerful open-source 3D creation suite that supports the entirety of the 3D pipeline. On the other hand, FDB-SQLite is a SQL layer built on top of the key-value store FoundationDB. The goal is to synchronize these two systems to proxy movement."
   },
   {
-    "objectID": "decisions/20220203-create-default-animation-set.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20220203-create-default-animation-set.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Draft: To have a default set of motions on a 3d character by creating a default animation set",
+    "objectID": "decisions/20240325-fdb-sqlite-blender-godot.html#problem-statement",
+    "href": "decisions/20240325-fdb-sqlite-blender-godot.html#problem-statement",
+    "title": "Proposed: Synchronizing Blender and FDB-SQLite for Proxy Movement",
     "section": "",
-    "text": "Describe the proposed option and how it helps to overcome the problem or limitation"
+    "text": "The challenge is to create a system where movements made in Blender are reflected in the FDB-SQLite database. This would allow for real-time tracking and manipulation of 3D models in a database environment."
   },
   {
-    "objectID": "decisions/20220203-create-default-animation-set.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20220203-create-default-animation-set.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Draft: To have a default set of motions on a 3d character by creating a default animation set",
+    "objectID": "decisions/20240325-fdb-sqlite-blender-godot.html#proposed-solution",
+    "href": "decisions/20240325-fdb-sqlite-blender-godot.html#proposed-solution",
+    "title": "Proposed: Synchronizing Blender and FDB-SQLite for Proxy Movement",
     "section": "",
-    "text": "Init\nNeutralFront\nNeutralRight\nNeutralLeft\nWalkFront\nWalkBack\nWalkRightFront\nWalkRightBack\nWalkLeftFront\nWalkLeftBack\nStrafeRight\nStrafeLeft\nSprintFront\nSprintBack\nSprintRightFront\nSprintRightBack\nSprintLeftFront\nSprintLeftFrontBack\nJump\nFall\nLand\n\n\n\n\nSit\n(NeutralToSit)\n(SitToNeutral)\nLay\n(NeutralToLay)\n(LayToNeutral)\n\n\n\n\n\nDuckNeutral\nDuckMoveFront\nDuckMoveBack\nDuckMoveRight\nDuckMoveLeft\n(DuckToSit)\n(SitToDuck)\n(DuckToLay)\n(LayToDuck)\nCrawlNeutral\nCrawlMoveFront\nCrawlMoveBack\nCrawlMoveRight\nCrawlMoveLeft\n(CrawlToSit)\n(SitToCrawl)\n(CrawlToLay)\n(LayToCrawl)\n(NeutralToDuck)\n(DuckToNeutral)\n(NeutralToCrawl)\n(CrawlToNeutral)\n(DuckToCrawl)\n(CrawlToDuck)\n\n\n\n\n\nChair"
+    "text": "We can achieve this by creating an interface between Blender and FDB-SQLite. This interface will listen for changes in Blender and update the corresponding entries in the FDB-SQLite database.\nclass BlenderFDBInterface:\n    def __init__(self, blender, fdb):\n        self.blender = blender\n        self.fdb = fdb\n\n    def sync(self):\n        # Get current state from Blender\n        state = self.blender.get_state()\n\n        # Update FDB with current state\n        self.fdb.update(state)"
   },
   {
-    "objectID": "decisions/20220203-create-default-animation-set.html#positive-consequences",
-    "href": "decisions/20220203-create-default-animation-set.html#positive-consequences",
-    "title": "Draft: To have a default set of motions on a 3d character by creating a default animation set",
+    "objectID": "decisions/20240325-fdb-sqlite-blender-godot.html#benefits",
+    "href": "decisions/20240325-fdb-sqlite-blender-godot.html#benefits",
+    "title": "Proposed: Synchronizing Blender and FDB-SQLite for Proxy Movement",
     "section": "",
-    "text": "[e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]"
+    "text": "Real-time synchronization between Blender and FDB-SQLite.\nAllows for complex queries and manipulations on 3D model data.\nOpens up possibilities for advanced analytics and machine learning applications."
   },
   {
-    "objectID": "decisions/20220203-create-default-animation-set.html#negative-consequences",
-    "href": "decisions/20220203-create-default-animation-set.html#negative-consequences",
-    "title": "Draft: To have a default set of motions on a 3d character by creating a default animation set",
+    "objectID": "decisions/20240325-fdb-sqlite-blender-godot.html#downsides",
+    "href": "decisions/20240325-fdb-sqlite-blender-godot.html#downsides",
+    "title": "Proposed: Synchronizing Blender and FDB-SQLite for Proxy Movement",
     "section": "",
-    "text": "[e.g., compromising quality attribute, follow-up decisions required, …]\n\n[this section can be repeated for each option if more than one option is open for consideration]"
+    "text": "Requires careful management of database transactions to avoid conflicts.\nPotential performance issues due to constant syncing."
   },
   {
-    "objectID": "decisions/20220203-create-default-animation-set.html#option-graveyard",
-    "href": "decisions/20220203-create-default-animation-set.html#option-graveyard",
-    "title": "Draft: To have a default set of motions on a 3d character by creating a default animation set",
+    "objectID": "decisions/20240325-fdb-sqlite-blender-godot.html#the-road-not-taken",
+    "href": "decisions/20240325-fdb-sqlite-blender-godot.html#the-road-not-taken",
+    "title": "Proposed: Synchronizing Blender and FDB-SQLite for Proxy Movement",
     "section": "",
-    "text": "Option: \nRejection Reason:"
+    "text": "An alternative approach could be to use a different database system that has built-in support for 3D data. However, this would require migrating all existing data and potentially reworking other parts of the system."
   },
   {
-    "objectID": "decisions/20220203-create-default-animation-set.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20220203-create-default-animation-set.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Draft: To have a default set of motions on a 3d character by creating a default animation set",
+    "objectID": "decisions/20240325-fdb-sqlite-blender-godot.html#the-infrequent-use-case",
+    "href": "decisions/20240325-fdb-sqlite-blender-godot.html#the-infrequent-use-case",
+    "title": "Proposed: Synchronizing Blender and FDB-SQLite for Proxy Movement",
     "section": "",
-    "text": "If this enhancement will not be used often, can it be worked around with a few lines of script?"
+    "text": "This solution may not be suitable for scenarios where the 3D models are rarely updated, as the constant syncing could be unnecessary overhead."
   },
   {
-    "objectID": "decisions/20220203-create-default-animation-set.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20220203-create-default-animation-set.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Draft: To have a default set of motions on a 3d character by creating a default animation set",
+    "objectID": "decisions/20240325-fdb-sqlite-blender-godot.html#in-core-and-done-by-us",
+    "href": "decisions/20240325-fdb-sqlite-blender-godot.html#in-core-and-done-by-us",
+    "title": "Proposed: Synchronizing Blender and FDB-SQLite for Proxy Movement",
     "section": "",
-    "text": "Is there a reason why this should be core and done by us?"
+    "text": "This feature will be developed by our in-house team, ensuring that it fits seamlessly into our existing infrastructure."
   },
   {
-    "objectID": "decisions/20220203-create-default-animation-set.html#references",
-    "href": "decisions/20220203-create-default-animation-set.html#references",
-    "title": "Draft: To have a default set of motions on a 3d character by creating a default animation set",
+    "objectID": "decisions/20240325-fdb-sqlite-blender-godot.html#status",
+    "href": "decisions/20240325-fdb-sqlite-blender-godot.html#status",
+    "title": "Proposed: Synchronizing Blender and FDB-SQLite for Proxy Movement",
     "section": "",
-    "text": "Link type"
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20220203-create-default-animation-set.html#derivative-license",
-    "href": "decisions/20220203-create-default-animation-set.html#derivative-license",
-    "title": "Draft: To have a default set of motions on a 3d character by creating a default animation set",
+    "objectID": "decisions/20240325-fdb-sqlite-blender-godot.html#decision-makers",
+    "href": "decisions/20240325-fdb-sqlite-blender-godot.html#decision-makers",
+    "title": "Proposed: Synchronizing Blender and FDB-SQLite for Proxy Movement",
     "section": "",
-    "text": "Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html",
-    "href": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html",
-    "title": "Proposed: Learn how to scale V-Sekai using bots and multipliers",
+    "objectID": "decisions/20240325-fdb-sqlite-blender-godot.html#tags",
+    "href": "decisions/20240325-fdb-sqlite-blender-godot.html#tags",
+    "title": "Proposed: Synchronizing Blender and FDB-SQLite for Proxy Movement",
     "section": "",
-    "text": "Status: proposed \nDeciders: V-Sekai,fire,\nTags: V-Sekai,\n\n\n\nWanted to scale V-Sekai.\n\n\n\nNeed find options to learn how to scale V-Sekai.\n\n\n\n\nBots\nMultiplier ghosts\n\n\n\n\n\nWe dream of more players.\n\n\n\n\n\nPainful engineering.\n\n\n\n\n\nOption: Paying $250 for 400 players per event.\nRejection Reason: Would work for a venture funded company in the Bay Area but hard for an opensoruce project.\n\n\n\n\nThis is an end to end integration test and it is trivial to setup bot creating but runs through all the systems.\n\n\n\nWe depend on the player load performance.\n\n\n\n\nhttps://github.com/V-Sekai/\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html#context-and-problem-statement",
-    "href": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html#context-and-problem-statement",
-    "title": "Proposed: Learn how to scale V-Sekai using bots and multipliers",
+    "objectID": "decisions/20240325-fdb-sqlite-blender-godot.html#further-reading",
+    "href": "decisions/20240325-fdb-sqlite-blender-godot.html#further-reading",
+    "title": "Proposed: Synchronizing Blender and FDB-SQLite for Proxy Movement",
     "section": "",
-    "text": "Wanted to scale V-Sekai."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: Learn how to scale V-Sekai using bots and multipliers",
+    "objectID": "decisions/20230125-user-generated-scripting-with-libsql-and-wasm.html",
+    "href": "decisions/20230125-user-generated-scripting-with-libsql-and-wasm.html",
+    "title": "Proposed: Provide user generated scripting with libsql and wasm",
     "section": "",
-    "text": "Need find options to learn how to scale V-Sekai."
+    "text": "Proposed: Provide user generated scripting with libsql and wasm\n\nMetadata\n\nStatus: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nContext and Problem Statement\nWe want to have user scripting for interactivity for objects, pets and npcs.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nWe implement the wasm scripts using libsql and a wasm runtime to be determined.\nWe had a previous implementation called WASGO. Possible names for the new one is WASGOQuery and WASGO.\nAdvantages:\n\nWAMR wasn’t well liked because it’s written in c/c++ and because it’s not widely used.\nWASMTIME is widely used and used for commercial / financial applications\n\nDisadvantages:\n\nWASMTIME rust is hard to deploy\nWAMR is hard to use.\n\nOpen Questions:\nDoes it require determinism for clustering?\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nWe ONLY support floating point, integers, strings and byte arrays.\n\nCompile libsqlite\nAdd a wasm engine\nTyped:\nSave a UDF of the notification function of _notification as a string of arbitrary length\nreturns a row\n\n\n\n\nimage\n\n\n\n\nPositive Consequences\nWe can user script our worlds.\n\n\nNegative Consequences\nWe cannot get other features in.\n\n\nOption graveyard\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nKnowing what to do is hard.\n\n\nIs there a reason why this should be core and done by us?\nScriptability is a core feature.\n\n\nReferences\n\nV-Sekai\nlibsql bindgen\nwasm udfs in sqlite"
   },
   {
-    "objectID": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Learn how to scale V-Sekai using bots and multipliers",
+    "objectID": "decisions/20221022-have-larger-worlds-by-server-state-migration.html",
+    "href": "decisions/20221022-have-larger-worlds-by-server-state-migration.html",
+    "title": "Draft: Simulate larger 3d multiplayer worlds using “brickworlds partition layout”",
     "section": "",
-    "text": "Bots\nMultiplier ghosts"
+    "text": "Status: draft \nDeciders: V-Sekai,Fire,Groak,\nTags: V-Sekai,\n\n\n\nEach V-Sekai game server has a scalability limit. Transfer each player to a different server when needed.\n\n\n\n\nTransfer the state using a database that can handle commits in commit order despite parallel transactions.\nFoundationdb is used by Apple for their cloud services and is trusted to handle distributed data safely.\nGodot Engine is a game engine where the interiors are easy to rearrange.\nSqlite is a well written database that is fully tested.\nRust is a good language for failures in math or computer language, but does not handle non code errors (like cosmic rays) through language based software redundancy like Erlang.\nMvsqlite merges sqlite with Foundationdb with Rust glue.\n\n\n\n\nPartition the world into tiles via Prasetya, Kusno’s design.\n\n\n\nDefine the tiles with a premigration and migration border.\n\nPremigration and migration border via Prasetya, Kusno’s design.\n\n\nTransfer the player from one server to another by first syncing all the frames, and have the player connect to the other side. Then the server does the transfer and the player disconnects from the previous side when the migration boundary is hit.\n\nServer state transfer.\n\nTest using a multiplayer simulator via Prasetya, Kusno’s design\n\n\n\n\n\n\nAllows player transfer from one server to the others servers.\n\n\n\n\n\nNeeds to connect the servers to the foundation database simulation servers.\n\n\n\n\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\n\nIt’s not a few lines of script.\n\n\n\nWe maintain the networking stack.\n\n\n\n\nV-Sekai\nEfficient_Methods_for_Improving_Scalability_and_Playability_of_Massively_Multiplayer_Online_Game_MMOG by Prasetya, Kusno\ngodot sqlite mvsqlite\ngodot mvsql demo\nmvsqlite for windows\nmvsqlite\nApple’s foundationdb\nRust lang\nSpecial thanks to the TigerBeetle for the sql schema\n\n\n\n\n\n\nextends Node3D\n\nfunc _ready():\n    var db : SQLite = SQLite.new();\n    if (!db.open(\"test\")):\n        print(\"Failed opening database.\");\n        return;\n    var _drop : String = \"\"\"drop table if exists entity;\n\"\"\"\n    var _create_entity_table : String = \"\"\"\nCREATE TABLE entity (\n    id TEXT PRIMARY KEY NOT NULL CHECK(LENGTH(id) = 36),\n    user_data blob NOT NULL CHECK( LENGTH(user_data) = 16) DEFAULT (zeroblob(16)),\n    reserved blob NOT NULL CHECK( LENGTH(reserved) = 48)  DEFAULT (zeroblob(48)),\n    shard   INTEGER NOT NULL,\n    code    INTEGER NOT NULL,\n    flags   INTEGER NOT NULL,\n    past_pending    BLOB NOT NULL CHECK( LENGTH(past_pending) &lt;= 1024) DEFAULT (zeroblob(64)),\n    past_posted BLOB NOT NULL CHECK( LENGTH(past_posted) &lt;= 1024) DEFAULT (zeroblob(64)),\n    current_pending BLOB NOT NULL CHECK( LENGTH(current_pending) &lt;= 1024) DEFAULT (zeroblob(64)),\n    current_posted  BLOB NOT NULL CHECK( LENGTH(current_posted) &lt;= 1024) DEFAULT (zeroblob(64)),\n    timestamp INTEGER NOT NULL\n) WITHOUT ROWID, STRICT;\n\"\"\"\n#   db.query(create_entity_table)\n    var _truncate_entities : String = \"\"\"\nDELETE FROM entity;\n    \"\"\"\n#   db.query(truncate_entities)\n    for i in range(32):\n        var node_3d : Node3D = Node3D.new()\n        var script = load(\"res://sqlite_write/sqlite_write_scene.gd\")\n        node_3d.set_script(script)\n        add_child(node_3d, true)\n        node_3d.owner = self\n\n\n\nextends Node3D\n\nvar db : SQLite = null\nvar result_create : SQLiteQuery\nvar result_delete : SQLiteQuery\nvar uuid : String\n\nfunc _ready():\n    db = SQLite.new();\n    if (!db.open(\"test\")):\n        print(\"Failed opening database.\");\n        return;\n\n    var select_uuid : String = \"\"\"\n    SELECT lower(hex(randomblob(4)) || '-' || hex(randomblob(2)) || '-' || '4' ||\n    substr(hex( randomblob(2)), 2) || '-' ||\n    substr('AB89', 1 + (abs(random()) % 4) , 1)  ||\n    substr(hex(randomblob(2)), 2) || '-' ||\n    hex(randomblob(6))) as uuid;\n    \"\"\"\n    uuid = db.fetch_array(select_uuid)[0][\"uuid\"]\n    var query_create_original = \"\"\"\nINSERT INTO entity (\"id\", \"user_data\", \"reserved\", \"shard\", \"code\", \"flags\", \"past_pending\", \"past_posted\",\n\"current_pending\", \"current_posted\", \"timestamp\")\nVALUES (?, zeroblob(16), zeroblob(48), 0, 0, 0, zeroblob(64), zeroblob(64), zeroblob(64), ?, UNIXEPOCH());\n\"\"\"\n    result_create = db.create_query(query_create_original)\n    var query_delete = \"\"\"\n    DELETE FROM entity\n    WHERE id = ?;\n\"\"\"\n    result_delete = db.create_query(query_delete)\n\nfunc _process(_delta):\n    if db == null:\n        return\n    var packed_array : Array = Array()\n    packed_array.push_back(global_transform)\n    var bytes : PackedByteArray = var_to_bytes(packed_array)\n    bytes = bytes.compress(FileAccess.COMPRESSION_ZSTD)\n    var statement : Array = [uuid, bytes]\n    var _result_batch = result_create.batch_execute([statement])\n\nfunc _exit_tree():\n    var statement : Array = [uuid]\n    var _result_batch = result_delete.batch_execute([statement])\n\n\n\n\ncmd\nscoop install llvm openssl-mingw llvm-mingw\ncargo build --release -p mvsqlite\ncd mvsqlite-sqlite3\nmingw32-make.exe build-patched-sqlite3\nset RUST_LOG=info\nset MVSQLITE_DATA_PLANE=http://localhost:7000\nsqlite3 test\n.tables\n\n\nfdbcli\nstatus\n# Force create a database\n# configure new single memory\n\n\n\nmsys2\ncurl http://localhost:7001/api/create_namespace -i -d '{\"key\":\"test\"}'\n\n\n\n# on Linux\nwget https://github.com/apple/foundationdb/releases/download/7.1.15/foundationdb-clients_7.1.15-1_amd64.deb\nsudo dpkg -i foundationdb-clients_7.1.15-1_amd64.deb\nwget https://github.com/apple/foundationdb/releases/download/7.1.15/foundationdb-server_7.1.15-1_amd64.deb\nsudo dpkg -i foundationdb-server_7.1.15-1_amd64.deb\ncargo build --release -p mvstore\nRUST_LOG=info ./mvstore \\\n  --data-plane 127.0.0.1:7000 \\\n  --admin-api 127.0.0.1:7001 \\\n  --metadata-prefix mvstore \\\n  --raw-data-prefix m\n\n\n\ncmd\ncargo build --release -p mvstore\nset RUST_LOG=info\nmvstore --data-plane 127.0.0.1:7000 --admin-api 127.0.0.1:7001 --metadata-prefix mvstore --raw-data-prefix m --cluster \"C:/ProgramData/foundationdb/fdb.cluster\"\n\n\n\n\n\n\nset RUST_LOG=info\nset MVSQLITE_DATA_PLANE=http://localhost:7000\nsqlite3 test\n\n\n\nset RUST_LOG=error\nmvstore --data-plane 127.0.0.1:7000 --admin-api 127.0.0.1:7001 --metadata-prefix mvstore --raw-data-prefix m --cluster \"C:/ProgramData/foundationdb/fdb.cluster\"\n\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html#positive-consequences",
-    "href": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html#positive-consequences",
-    "title": "Proposed: Learn how to scale V-Sekai using bots and multipliers",
+    "objectID": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#context-and-problem-statement",
+    "href": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#context-and-problem-statement",
+    "title": "Draft: Simulate larger 3d multiplayer worlds using “brickworlds partition layout”",
     "section": "",
-    "text": "We dream of more players."
+    "text": "Each V-Sekai game server has a scalability limit. Transfer each player to a different server when needed."
   },
   {
-    "objectID": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html#negative-consequences",
-    "href": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html#negative-consequences",
-    "title": "Proposed: Learn how to scale V-Sekai using bots and multipliers",
+    "objectID": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Draft: Simulate larger 3d multiplayer worlds using “brickworlds partition layout”",
     "section": "",
-    "text": "Painful engineering."
+    "text": "Transfer the state using a database that can handle commits in commit order despite parallel transactions.\nFoundationdb is used by Apple for their cloud services and is trusted to handle distributed data safely.\nGodot Engine is a game engine where the interiors are easy to rearrange.\nSqlite is a well written database that is fully tested.\nRust is a good language for failures in math or computer language, but does not handle non code errors (like cosmic rays) through language based software redundancy like Erlang.\nMvsqlite merges sqlite with Foundationdb with Rust glue."
   },
   {
-    "objectID": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html#option-graveyard",
-    "href": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html#option-graveyard",
-    "title": "Proposed: Learn how to scale V-Sekai using bots and multipliers",
+    "objectID": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Draft: Simulate larger 3d multiplayer worlds using “brickworlds partition layout”",
     "section": "",
-    "text": "Option: Paying $250 for 400 players per event.\nRejection Reason: Would work for a venture funded company in the Bay Area but hard for an opensoruce project."
+    "text": "Partition the world into tiles via Prasetya, Kusno’s design.\n\n\n\nDefine the tiles with a premigration and migration border.\n\nPremigration and migration border via Prasetya, Kusno’s design.\n\n\nTransfer the player from one server to another by first syncing all the frames, and have the player connect to the other side. Then the server does the transfer and the player disconnects from the previous side when the migration boundary is hit.\n\nServer state transfer.\n\nTest using a multiplayer simulator via Prasetya, Kusno’s design"
   },
   {
-    "objectID": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Learn how to scale V-Sekai using bots and multipliers",
+    "objectID": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#positive-consequences",
+    "href": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#positive-consequences",
+    "title": "Draft: Simulate larger 3d multiplayer worlds using “brickworlds partition layout”",
     "section": "",
-    "text": "This is an end to end integration test and it is trivial to setup bot creating but runs through all the systems."
+    "text": "Allows player transfer from one server to the others servers."
   },
   {
-    "objectID": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Learn how to scale V-Sekai using bots and multipliers",
+    "objectID": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#negative-consequences",
+    "href": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#negative-consequences",
+    "title": "Draft: Simulate larger 3d multiplayer worlds using “brickworlds partition layout”",
     "section": "",
-    "text": "We depend on the player load performance."
+    "text": "Needs to connect the servers to the foundation database simulation servers."
   },
   {
-    "objectID": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html#references",
-    "href": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html#references",
-    "title": "Proposed: Learn how to scale V-Sekai using bots and multipliers",
+    "objectID": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#option-graveyard",
+    "href": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#option-graveyard",
+    "title": "Draft: Simulate larger 3d multiplayer worlds using “brickworlds partition layout”",
     "section": "",
-    "text": "https://github.com/V-Sekai/"
+    "text": "Option: The status quo. \nRejection Reason: This solves nothing."
   },
   {
-    "objectID": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html#derivative-license",
-    "href": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html#derivative-license",
-    "title": "Proposed: Learn how to scale V-Sekai using bots and multipliers",
+    "objectID": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Draft: Simulate larger 3d multiplayer worlds using “brickworlds partition layout”",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "It’s not a few lines of script."
   },
   {
-    "objectID": "decisions/20211031-keep-a-changelog.html",
-    "href": "decisions/20211031-keep-a-changelog.html",
-    "title": "Accepted: Keep a changelog",
+    "objectID": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Draft: Simulate larger 3d multiplayer worlds using “brickworlds partition layout”",
     "section": "",
-    "text": "Accepted: Keep a changelog\n\nStatus: accepted\n\n\nContext and Problem Statement\nHumans need to know what has changed\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nCopied from https://keepachangelog.com.\n\nWhat is a changelog?\n\n\nA changelog is a file which contains a curated, chronologically ordered list of notable changes for each version of a project. Why keep a changelog?\n\n\nTo make it easier for users and contributors to see precisely what notable changes have been made between each release (or version) of the project. Who needs a changelog?\n\n\nPeople do. Whether consumers or developers, the end users of software are human beings who care about what’s in the software. When the software changes, people want to know why and how.\n\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nKeep a changelog.\n\nUse the https://github.com/V-Sekai/v-sekai-proposals #repository as a placeholder.\nDelay migrations to main project #repository to a later date.\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot code.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nWe are the best to know what changed.\n\n\nReferences\n\nhttps://keepachangelog.com/en/1.0.0/\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "We maintain the networking stack."
   },
   {
-    "objectID": "decisions/20230531-godot-engine-learning.html",
-    "href": "decisions/20230531-godot-engine-learning.html",
-    "title": "Proposed: Propose a solution to improve V-Sekai contributors’ design skills for navigating 3D environments",
+    "objectID": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#references",
+    "href": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#references",
+    "title": "Draft: Simulate larger 3d multiplayer worlds using “brickworlds partition layout”",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, GPT-4\n\n\n\n\nV-Sekai contributors lack the knowledge to create decent designs for navigating complex 3D environments with obstacles and walls, limiting user experience and potential applications.\n\n\n\nDevelop a comprehensive training program for V-Sekai contributors that focuses on designing effective navigation systems for complex 3D environments.\n\n\n\n\nIdentify key concepts and best practices for designing navigation systems in 3D environments.\nCreate a curriculum that covers these concepts and best practices, including hands-on exercises and real-world examples.\nOrganize workshops or webinars led by experienced professionals in the field of 3D environment design.\nProvide access to resources such as articles, tutorials, and online courses for self-paced learning.\nEncourage collaboration and peer review among contributors to share knowledge and improve designs.\nEvaluate contributors’ progress and provide feedback to ensure continuous improvement.\n\n\n\n\n\nImproved design skills among V-Sekai contributors.\nEnhanced user experience and potential applications.\nIncreased collaboration and knowledge sharing within the community.\n\n\n\n\n\nAdditional time and resources required for training and development.\nPotential delays in project timelines due to training commitments.\n\n\n\n\n\nHiring external designers with expertise in 3D environment navigation.\nIgnoring the issue and continuing with suboptimal designs.\n\n\n\n\nNo simple workaround; a comprehensive training program is necessary to improve contributors’ design skills for navigating 3D environments.\n\n\n\nInvesting in the development of V-Sekai contributors’ design skills is essential for enhancing user experience and expanding the potential applications of the platform.\n\n\n\n\nV-Sekai"
+    "text": "V-Sekai\nEfficient_Methods_for_Improving_Scalability_and_Playability_of_Massively_Multiplayer_Online_Game_MMOG by Prasetya, Kusno\ngodot sqlite mvsqlite\ngodot mvsql demo\nmvsqlite for windows\nmvsqlite\nApple’s foundationdb\nRust lang\nSpecial thanks to the TigerBeetle for the sql schema"
   },
   {
-    "objectID": "decisions/20230531-godot-engine-learning.html#metadata",
-    "href": "decisions/20230531-godot-engine-learning.html#metadata",
-    "title": "Proposed: Propose a solution to improve V-Sekai contributors’ design skills for navigating 3D environments",
+    "objectID": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#code-references",
+    "href": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#code-references",
+    "title": "Draft: Simulate larger 3d multiplayer worlds using “brickworlds partition layout”",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, GPT-4"
+    "text": "extends Node3D\n\nfunc _ready():\n    var db : SQLite = SQLite.new();\n    if (!db.open(\"test\")):\n        print(\"Failed opening database.\");\n        return;\n    var _drop : String = \"\"\"drop table if exists entity;\n\"\"\"\n    var _create_entity_table : String = \"\"\"\nCREATE TABLE entity (\n    id TEXT PRIMARY KEY NOT NULL CHECK(LENGTH(id) = 36),\n    user_data blob NOT NULL CHECK( LENGTH(user_data) = 16) DEFAULT (zeroblob(16)),\n    reserved blob NOT NULL CHECK( LENGTH(reserved) = 48)  DEFAULT (zeroblob(48)),\n    shard   INTEGER NOT NULL,\n    code    INTEGER NOT NULL,\n    flags   INTEGER NOT NULL,\n    past_pending    BLOB NOT NULL CHECK( LENGTH(past_pending) &lt;= 1024) DEFAULT (zeroblob(64)),\n    past_posted BLOB NOT NULL CHECK( LENGTH(past_posted) &lt;= 1024) DEFAULT (zeroblob(64)),\n    current_pending BLOB NOT NULL CHECK( LENGTH(current_pending) &lt;= 1024) DEFAULT (zeroblob(64)),\n    current_posted  BLOB NOT NULL CHECK( LENGTH(current_posted) &lt;= 1024) DEFAULT (zeroblob(64)),\n    timestamp INTEGER NOT NULL\n) WITHOUT ROWID, STRICT;\n\"\"\"\n#   db.query(create_entity_table)\n    var _truncate_entities : String = \"\"\"\nDELETE FROM entity;\n    \"\"\"\n#   db.query(truncate_entities)\n    for i in range(32):\n        var node_3d : Node3D = Node3D.new()\n        var script = load(\"res://sqlite_write/sqlite_write_scene.gd\")\n        node_3d.set_script(script)\n        add_child(node_3d, true)\n        node_3d.owner = self\n\n\n\nextends Node3D\n\nvar db : SQLite = null\nvar result_create : SQLiteQuery\nvar result_delete : SQLiteQuery\nvar uuid : String\n\nfunc _ready():\n    db = SQLite.new();\n    if (!db.open(\"test\")):\n        print(\"Failed opening database.\");\n        return;\n\n    var select_uuid : String = \"\"\"\n    SELECT lower(hex(randomblob(4)) || '-' || hex(randomblob(2)) || '-' || '4' ||\n    substr(hex( randomblob(2)), 2) || '-' ||\n    substr('AB89', 1 + (abs(random()) % 4) , 1)  ||\n    substr(hex(randomblob(2)), 2) || '-' ||\n    hex(randomblob(6))) as uuid;\n    \"\"\"\n    uuid = db.fetch_array(select_uuid)[0][\"uuid\"]\n    var query_create_original = \"\"\"\nINSERT INTO entity (\"id\", \"user_data\", \"reserved\", \"shard\", \"code\", \"flags\", \"past_pending\", \"past_posted\",\n\"current_pending\", \"current_posted\", \"timestamp\")\nVALUES (?, zeroblob(16), zeroblob(48), 0, 0, 0, zeroblob(64), zeroblob(64), zeroblob(64), ?, UNIXEPOCH());\n\"\"\"\n    result_create = db.create_query(query_create_original)\n    var query_delete = \"\"\"\n    DELETE FROM entity\n    WHERE id = ?;\n\"\"\"\n    result_delete = db.create_query(query_delete)\n\nfunc _process(_delta):\n    if db == null:\n        return\n    var packed_array : Array = Array()\n    packed_array.push_back(global_transform)\n    var bytes : PackedByteArray = var_to_bytes(packed_array)\n    bytes = bytes.compress(FileAccess.COMPRESSION_ZSTD)\n    var statement : Array = [uuid, bytes]\n    var _result_batch = result_create.batch_execute([statement])\n\nfunc _exit_tree():\n    var statement : Array = [uuid]\n    var _result_batch = result_delete.batch_execute([statement])"
   },
   {
-    "objectID": "decisions/20230531-godot-engine-learning.html#problem-statement",
-    "href": "decisions/20230531-godot-engine-learning.html#problem-statement",
-    "title": "Proposed: Propose a solution to improve V-Sekai contributors’ design skills for navigating 3D environments",
+    "objectID": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#mvsqlite-for-windows",
+    "href": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#mvsqlite-for-windows",
+    "title": "Draft: Simulate larger 3d multiplayer worlds using “brickworlds partition layout”",
     "section": "",
-    "text": "V-Sekai contributors lack the knowledge to create decent designs for navigating complex 3D environments with obstacles and walls, limiting user experience and potential applications."
+    "text": "cmd\nscoop install llvm openssl-mingw llvm-mingw\ncargo build --release -p mvsqlite\ncd mvsqlite-sqlite3\nmingw32-make.exe build-patched-sqlite3\nset RUST_LOG=info\nset MVSQLITE_DATA_PLANE=http://localhost:7000\nsqlite3 test\n.tables\n\n\nfdbcli\nstatus\n# Force create a database\n# configure new single memory\n\n\n\nmsys2\ncurl http://localhost:7001/api/create_namespace -i -d '{\"key\":\"test\"}'\n\n\n\n# on Linux\nwget https://github.com/apple/foundationdb/releases/download/7.1.15/foundationdb-clients_7.1.15-1_amd64.deb\nsudo dpkg -i foundationdb-clients_7.1.15-1_amd64.deb\nwget https://github.com/apple/foundationdb/releases/download/7.1.15/foundationdb-server_7.1.15-1_amd64.deb\nsudo dpkg -i foundationdb-server_7.1.15-1_amd64.deb\ncargo build --release -p mvstore\nRUST_LOG=info ./mvstore \\\n  --data-plane 127.0.0.1:7000 \\\n  --admin-api 127.0.0.1:7001 \\\n  --metadata-prefix mvstore \\\n  --raw-data-prefix m\n\n\n\ncmd\ncargo build --release -p mvstore\nset RUST_LOG=info\nmvstore --data-plane 127.0.0.1:7000 --admin-api 127.0.0.1:7001 --metadata-prefix mvstore --raw-data-prefix m --cluster \"C:/ProgramData/foundationdb/fdb.cluster\""
   },
   {
-    "objectID": "decisions/20230531-godot-engine-learning.html#proposed-solution",
-    "href": "decisions/20230531-godot-engine-learning.html#proposed-solution",
-    "title": "Proposed: Propose a solution to improve V-Sekai contributors’ design skills for navigating 3D environments",
+    "objectID": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#launch-scripts",
+    "href": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#launch-scripts",
+    "title": "Draft: Simulate larger 3d multiplayer worlds using “brickworlds partition layout”",
     "section": "",
-    "text": "Develop a comprehensive training program for V-Sekai contributors that focuses on designing effective navigation systems for complex 3D environments."
+    "text": "set RUST_LOG=info\nset MVSQLITE_DATA_PLANE=http://localhost:7000\nsqlite3 test\n\n\n\nset RUST_LOG=error\nmvstore --data-plane 127.0.0.1:7000 --admin-api 127.0.0.1:7001 --metadata-prefix mvstore --raw-data-prefix m --cluster \"C:/ProgramData/foundationdb/fdb.cluster\""
   },
   {
-    "objectID": "decisions/20230531-godot-engine-learning.html#implementation",
-    "href": "decisions/20230531-godot-engine-learning.html#implementation",
-    "title": "Proposed: Propose a solution to improve V-Sekai contributors’ design skills for navigating 3D environments",
+    "objectID": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#license-of-the-contribution",
+    "href": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#license-of-the-contribution",
+    "title": "Draft: Simulate larger 3d multiplayer worlds using “brickworlds partition layout”",
     "section": "",
-    "text": "Identify key concepts and best practices for designing navigation systems in 3D environments.\nCreate a curriculum that covers these concepts and best practices, including hands-on exercises and real-world examples.\nOrganize workshops or webinars led by experienced professionals in the field of 3D environment design.\nProvide access to resources such as articles, tutorials, and online courses for self-paced learning.\nEncourage collaboration and peer review among contributors to share knowledge and improve designs.\nEvaluate contributors’ progress and provide feedback to ensure continuous improvement."
+    "text": "Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230531-godot-engine-learning.html#positive-consequences",
-    "href": "decisions/20230531-godot-engine-learning.html#positive-consequences",
-    "title": "Proposed: Propose a solution to improve V-Sekai contributors’ design skills for navigating 3D environments",
+    "objectID": "decisions/20240710-web-and-pcvr-networking.html",
+    "href": "decisions/20240710-web-and-pcvr-networking.html",
+    "title": "Proposed: Networking PCVR with the Web",
     "section": "",
-    "text": "Improved design skills among V-Sekai contributors.\nEnhanced user experience and potential applications.\nIncreased collaboration and knowledge sharing within the community."
+    "text": "In the development of virtual reality (VR) applications, focusing on both PC-based VR (PCVR) and web platforms can provide a broader reach and enhanced user experience.\nNote: When referring to “web” in this document, it specifically means web desktop platforms and not WebXR.\nWe use Godot Engine 4.3 pre-release. PCVR uses OpenXR and the web uses threading.\n\n\n\nPCVR platforms must be able to communicate with the web platform in a low latency (UDP) network so the web can be a fallback to support everyone.\n\n\n\n\nCommunication Protocol: Implement a UDP-based communication protocol for low-latency data transfer between PCVR and web platforms.\nGodot’s Multiplayer API: Use Godot’s high-level multiplayer API to manage connections and data synchronization.\nCustom Patch for Godot WebRTC: Utilize our custom patch for Godot WebRTC for PCVR.\nStandard Browser WebRTC: Employ the standard browser WebRTC for the web.\n\n\n\nTo test the interoperability between PCVR and web platforms, we propose developing a simple real-time chat application. This will involve:\n\nA basic text input field and display area for messages on both PCVR and web platforms.\nEstablishing a UDP connection between the PCVR and web clients.\nUsing Godot’s high-level multiplayer API to handle message sending and receiving.\nEnsuring that messages sent from the PCVR client appear in real-time on the web client and vice versa.\n\nTo enhance the functionality and flexibility of the communication system, we propose implementing multiple channels for different types of data. This will allow for more organized and efficient data transfer. The channels could include:\n\nText Channel:\n\nFor sending and receiving text messages.\nUsed in the real-time chat application.\n\nVoice Channel:\n\nFor transmitting voice data.\nEnables real-time voice communication between PCVR and web clients.\n\nData Channel:\n\nFor sending miscellaneous data such as user actions, game state updates, etc.\nEnsures that non-textual data is transmitted efficiently.\n\n\n\n\n\n\n\nEnsures real-time interaction between PCVR and web platforms.\nExpands the user base by supporting both PCVR and web platforms.\nProvides seamless integration and interaction across different platforms.\n\n\n\n\n\nIncreased complexity in managing cross-platform communication.\nRequires ongoing maintenance and updates to ensure compatibility and performance.\n\n\n\n\nConsideration of other communication protocols like TCP, which may offer reliability but at the cost of higher latency.\n\n\n\nHandling scenarios where network conditions are poor or intermittent, requiring robust error handling and reconnection strategies.\n\n\n\nThis proposal involves integrating the solution directly into the core of the V-Sekai project, managed by the V-Sekai development team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\nfire\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20230531-godot-engine-learning.html#negative-consequences",
-    "href": "decisions/20230531-godot-engine-learning.html#negative-consequences",
-    "title": "Proposed: Propose a solution to improve V-Sekai contributors’ design skills for navigating 3D environments",
+    "objectID": "decisions/20240710-web-and-pcvr-networking.html#the-context",
+    "href": "decisions/20240710-web-and-pcvr-networking.html#the-context",
+    "title": "Proposed: Networking PCVR with the Web",
     "section": "",
-    "text": "Additional time and resources required for training and development.\nPotential delays in project timelines due to training commitments."
+    "text": "In the development of virtual reality (VR) applications, focusing on both PC-based VR (PCVR) and web platforms can provide a broader reach and enhanced user experience.\nNote: When referring to “web” in this document, it specifically means web desktop platforms and not WebXR.\nWe use Godot Engine 4.3 pre-release. PCVR uses OpenXR and the web uses threading."
   },
   {
-    "objectID": "decisions/20230531-godot-engine-learning.html#option-graveyard",
-    "href": "decisions/20230531-godot-engine-learning.html#option-graveyard",
-    "title": "Proposed: Propose a solution to improve V-Sekai contributors’ design skills for navigating 3D environments",
+    "objectID": "decisions/20240710-web-and-pcvr-networking.html#the-problem-statement",
+    "href": "decisions/20240710-web-and-pcvr-networking.html#the-problem-statement",
+    "title": "Proposed: Networking PCVR with the Web",
     "section": "",
-    "text": "Hiring external designers with expertise in 3D environment navigation.\nIgnoring the issue and continuing with suboptimal designs."
+    "text": "PCVR platforms must be able to communicate with the web platform in a low latency (UDP) network so the web can be a fallback to support everyone."
   },
   {
-    "objectID": "decisions/20230531-godot-engine-learning.html#enhancement-workaround",
-    "href": "decisions/20230531-godot-engine-learning.html#enhancement-workaround",
-    "title": "Proposed: Propose a solution to improve V-Sekai contributors’ design skills for navigating 3D environments",
+    "objectID": "decisions/20240710-web-and-pcvr-networking.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240710-web-and-pcvr-networking.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Networking PCVR with the Web",
     "section": "",
-    "text": "No simple workaround; a comprehensive training program is necessary to improve contributors’ design skills for navigating 3D environments."
+    "text": "Communication Protocol: Implement a UDP-based communication protocol for low-latency data transfer between PCVR and web platforms.\nGodot’s Multiplayer API: Use Godot’s high-level multiplayer API to manage connections and data synchronization.\nCustom Patch for Godot WebRTC: Utilize our custom patch for Godot WebRTC for PCVR.\nStandard Browser WebRTC: Employ the standard browser WebRTC for the web.\n\n\n\nTo test the interoperability between PCVR and web platforms, we propose developing a simple real-time chat application. This will involve:\n\nA basic text input field and display area for messages on both PCVR and web platforms.\nEstablishing a UDP connection between the PCVR and web clients.\nUsing Godot’s high-level multiplayer API to handle message sending and receiving.\nEnsuring that messages sent from the PCVR client appear in real-time on the web client and vice versa.\n\nTo enhance the functionality and flexibility of the communication system, we propose implementing multiple channels for different types of data. This will allow for more organized and efficient data transfer. The channels could include:\n\nText Channel:\n\nFor sending and receiving text messages.\nUsed in the real-time chat application.\n\nVoice Channel:\n\nFor transmitting voice data.\nEnables real-time voice communication between PCVR and web clients.\n\nData Channel:\n\nFor sending miscellaneous data such as user actions, game state updates, etc.\nEnsures that non-textual data is transmitted efficiently."
   },
   {
-    "objectID": "decisions/20230531-godot-engine-learning.html#core-reasoning",
-    "href": "decisions/20230531-godot-engine-learning.html#core-reasoning",
-    "title": "Proposed: Propose a solution to improve V-Sekai contributors’ design skills for navigating 3D environments",
+    "objectID": "decisions/20240710-web-and-pcvr-networking.html#the-benefits",
+    "href": "decisions/20240710-web-and-pcvr-networking.html#the-benefits",
+    "title": "Proposed: Networking PCVR with the Web",
     "section": "",
-    "text": "Investing in the development of V-Sekai contributors’ design skills is essential for enhancing user experience and expanding the potential applications of the platform."
+    "text": "Ensures real-time interaction between PCVR and web platforms.\nExpands the user base by supporting both PCVR and web platforms.\nProvides seamless integration and interaction across different platforms."
   },
   {
-    "objectID": "decisions/20230531-godot-engine-learning.html#references",
-    "href": "decisions/20230531-godot-engine-learning.html#references",
-    "title": "Proposed: Propose a solution to improve V-Sekai contributors’ design skills for navigating 3D environments",
+    "objectID": "decisions/20240710-web-and-pcvr-networking.html#the-downsides",
+    "href": "decisions/20240710-web-and-pcvr-networking.html#the-downsides",
+    "title": "Proposed: Networking PCVR with the Web",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Increased complexity in managing cross-platform communication.\nRequires ongoing maintenance and updates to ensure compatibility and performance."
   },
   {
-    "objectID": "decisions/20210811-spoke-to-v-sekai.html",
-    "href": "decisions/20210811-spoke-to-v-sekai.html",
-    "title": "Proposed: Spoke to V-Sekai",
+    "objectID": "decisions/20240710-web-and-pcvr-networking.html#the-road-not-taken",
+    "href": "decisions/20240710-web-and-pcvr-networking.html#the-road-not-taken",
+    "title": "Proposed: Networking PCVR with the Web",
     "section": "",
-    "text": "Proposed: Spoke to V-Sekai\n\nContext and Problem Statement\nWe desire portable content.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nCreate an art workflow.\n[Blender] -&gt; [OMI.glb]\n[OMI.glb] -&gt; [Godot Engine Packed Scene]\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nCreate an OMI Blender addon under W3C license.\nCreate glTF2 extension pull request for Godot Engine.\nFlow:\n\nOMI importer to Blender\nExporter of extended blender with OMI extensions to extended gltf\nSupport for OMI extended gltf in godot with definition of in-memory format for OMI extensions in Godot Engine for bidirectionality.\n\nExpected output:\n\nExport/Import as OMI format in Blender\nSupport OMI GLB in Godot\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nInterlapping projects are complicated.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nCan collaborate with Mozilla hubs team and OMI.\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Consideration of other communication protocols like TCP, which may offer reliability but at the cost of higher latency."
   },
   {
-    "objectID": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html",
-    "href": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html",
-    "title": "Proposed: Run the maintenance scripts from Windows in Unix mode with msys2",
+    "objectID": "decisions/20240710-web-and-pcvr-networking.html#the-infrequent-use-case",
+    "href": "decisions/20240710-web-and-pcvr-networking.html#the-infrequent-use-case",
+    "title": "Proposed: Networking PCVR with the Web",
     "section": "",
-    "text": "Status: proposed &lt;– draft | rejected | accepted | deprecated | superseded by –&gt;\n\n\n\nI want to use Unix tools but the experience of Linux is lacking.\n\n\n\nUse msys2 on Windows to improve this.\n\n\n\n\nInstall Windows 10 or Windows 11\nOpen Powershell.\nSet-ExecutionPolicy RemoteSigned -scope CurrentUser\niwr -useb get.scoop.sh | iex\nscoop install msys\nmsys2 Restart to setup msys2.\npacman -S ssh-pageant openssh git python3\nCopy to ~/.bashrc\neval $(/usr/bin/ssh-pageant -r -a \"/tmp/.ssh-pageant-$USERNAME\")\n\n\n\n\n\n[e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]\n[…]\n\n\n\n\n\nI can use the better experience of Windows without the frustration of Linux.\n\n[this section can be repeated for each option if more than one option is open for consideration]\n\n\n\n\nOption: \nRejection Reason: \n\n\n\n\nThis is a quality of life improvement.\n\n\n\nI use this.\n\n\n\n\nhttps://www.msys2.org/\nhttps://github.com/cuviper/ssh-pageant\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Handling scenarios where network conditions are poor or intermittent, requiring robust error handling and reconnection strategies."
   },
   {
-    "objectID": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html#context-and-problem-statement",
-    "href": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html#context-and-problem-statement",
-    "title": "Proposed: Run the maintenance scripts from Windows in Unix mode with msys2",
+    "objectID": "decisions/20240710-web-and-pcvr-networking.html#in-core-and-done-by-us",
+    "href": "decisions/20240710-web-and-pcvr-networking.html#in-core-and-done-by-us",
+    "title": "Proposed: Networking PCVR with the Web",
     "section": "",
-    "text": "I want to use Unix tools but the experience of Linux is lacking."
+    "text": "This proposal involves integrating the solution directly into the core of the V-Sekai project, managed by the V-Sekai development team."
   },
   {
-    "objectID": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: Run the maintenance scripts from Windows in Unix mode with msys2",
+    "objectID": "decisions/20240710-web-and-pcvr-networking.html#status",
+    "href": "decisions/20240710-web-and-pcvr-networking.html#status",
+    "title": "Proposed: Networking PCVR with the Web",
     "section": "",
-    "text": "Use msys2 on Windows to improve this."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Run the maintenance scripts from Windows in Unix mode with msys2",
+    "objectID": "decisions/20240710-web-and-pcvr-networking.html#decision-makers",
+    "href": "decisions/20240710-web-and-pcvr-networking.html#decision-makers",
+    "title": "Proposed: Networking PCVR with the Web",
     "section": "",
-    "text": "Install Windows 10 or Windows 11\nOpen Powershell.\nSet-ExecutionPolicy RemoteSigned -scope CurrentUser\niwr -useb get.scoop.sh | iex\nscoop install msys\nmsys2 Restart to setup msys2.\npacman -S ssh-pageant openssh git python3\nCopy to ~/.bashrc\neval $(/usr/bin/ssh-pageant -r -a \"/tmp/.ssh-pageant-$USERNAME\")"
+    "text": "V-Sekai development team\nfire"
   },
   {
-    "objectID": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html#positive-consequences",
-    "href": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html#positive-consequences",
-    "title": "Proposed: Run the maintenance scripts from Windows in Unix mode with msys2",
+    "objectID": "decisions/20240710-web-and-pcvr-networking.html#tags",
+    "href": "decisions/20240710-web-and-pcvr-networking.html#tags",
+    "title": "Proposed: Networking PCVR with the Web",
     "section": "",
-    "text": "[e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]\n[…]"
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html#negative-consequences",
-    "href": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html#negative-consequences",
-    "title": "Proposed: Run the maintenance scripts from Windows in Unix mode with msys2",
+    "objectID": "decisions/20240710-web-and-pcvr-networking.html#further-reading",
+    "href": "decisions/20240710-web-and-pcvr-networking.html#further-reading",
+    "title": "Proposed: Networking PCVR with the Web",
     "section": "",
-    "text": "I can use the better experience of Windows without the frustration of Linux.\n\n[this section can be repeated for each option if more than one option is open for consideration]"
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html#option-graveyard",
-    "href": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html#option-graveyard",
-    "title": "Proposed: Run the maintenance scripts from Windows in Unix mode with msys2",
+    "objectID": "decisions/20221205-port-renik-to-many-bone-ik.html",
+    "href": "decisions/20221205-port-renik-to-many-bone-ik.html",
+    "title": "Proposed: Port RENIK to Many Bone IK for better quality",
     "section": "",
-    "text": "Option: \nRejection Reason:"
+    "text": "Status: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nRenik is a character controller and many bone ik is an ik solver. We have not merged them.\nThe quality is low for the FABRIK solver.\n\n\n\nWe wish to merge many bone ik and renik to improve quality.\n\n\n\n\nReplace renik’s usage of FABRIK with many bone ik.\n\n\n\n\n\nBetter animation quality\n\n\n\n\n\n\n\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\n\nIK is hard and not a few lines of code.\n\n\n\nWe know how to do it.\n\n\n\n\nV-Sekai\n\n\n\n\nMIT License\n\nCopyright (c) 2018-2022 SaracenOne\nCopyright (c) 2019-2022 K. S. Ernest (iFire) Lee (fire)\nCopyright (c) 2020-2022 Lyuma\nCopyright (c) 2020-2022 MMMaellon\nCopyright (c) 2022 V-Sekai Contributors\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
   },
   {
-    "objectID": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Run the maintenance scripts from Windows in Unix mode with msys2",
+    "objectID": "decisions/20221205-port-renik-to-many-bone-ik.html#context-and-problem-statement",
+    "href": "decisions/20221205-port-renik-to-many-bone-ik.html#context-and-problem-statement",
+    "title": "Proposed: Port RENIK to Many Bone IK for better quality",
     "section": "",
-    "text": "This is a quality of life improvement."
+    "text": "Renik is a character controller and many bone ik is an ik solver. We have not merged them.\nThe quality is low for the FABRIK solver."
   },
   {
-    "objectID": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Run the maintenance scripts from Windows in Unix mode with msys2",
+    "objectID": "decisions/20221205-port-renik-to-many-bone-ik.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20221205-port-renik-to-many-bone-ik.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: Port RENIK to Many Bone IK for better quality",
     "section": "",
-    "text": "I use this."
+    "text": "We wish to merge many bone ik and renik to improve quality."
   },
   {
-    "objectID": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html#references",
-    "href": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html#references",
-    "title": "Proposed: Run the maintenance scripts from Windows in Unix mode with msys2",
+    "objectID": "decisions/20221205-port-renik-to-many-bone-ik.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20221205-port-renik-to-many-bone-ik.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Port RENIK to Many Bone IK for better quality",
     "section": "",
-    "text": "https://www.msys2.org/\nhttps://github.com/cuviper/ssh-pageant"
+    "text": "Replace renik’s usage of FABRIK with many bone ik."
   },
   {
-    "objectID": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html#derivative-license",
-    "href": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html#derivative-license",
-    "title": "Proposed: Run the maintenance scripts from Windows in Unix mode with msys2",
+    "objectID": "decisions/20221205-port-renik-to-many-bone-ik.html#positive-consequences",
+    "href": "decisions/20221205-port-renik-to-many-bone-ik.html#positive-consequences",
+    "title": "Proposed: Port RENIK to Many Bone IK for better quality",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Better animation quality"
   },
   {
-    "objectID": "decisions/20231108-neon-postgresql.html",
-    "href": "decisions/20231108-neon-postgresql.html",
-    "title": "Proposed: Adopting Neon for a More Manageable Backend at V-Sekai",
+    "objectID": "decisions/20221205-port-renik-to-many-bone-ik.html#option-graveyard",
+    "href": "decisions/20221205-port-renik-to-many-bone-ik.html#option-graveyard",
+    "title": "Proposed: Port RENIK to Many Bone IK for better quality",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai, Fire\nTags: Backend Management, Neon, Ease-of-Use, Postgres\n\n\n\n\nV-Sekai’s current setup with Postgres and Uro is hitting roadblocks due to the lack of dedicated server management expertise.\n\n\n\nIs Neon the key to a more manageable Postgres system that fits our community-driven model?\n\n\n\nWe plan to run a Neon pilot to see if it eases our backend management woes. Steps include:\n\nTesting Neon’s compatibility with our current data.\nExploring Neon’s manageability features.\nDrafting straightforward documentation for team reference.\nEnsuring a hassle-free data migration process.\n\n\n\n\n\nA more user-friendly backend system.\nReduced need for server management know-how.\nPotential performance benefits are a bonus.\n\n\n\n\n\nTime investment in learning a new system.\nPossible initial dependence on external support.\n\n\n\n\nSticking with Uro or other complex solutions that don’t align with our manageability goals.\n\n\n\nSituations where Uro’s specific configurations are essential; these will require special attention.\n\n\n\nPlanning to make Neon a central part of our backend, relying on our collective skills to implement it.\n\n\n\n\nV-Sekai on GitHub\nNeon’s Architecture\n\nThis article was assisted by AI."
+    "text": "Option: The status quo. \nRejection Reason: This solves nothing."
   },
   {
-    "objectID": "decisions/20231108-neon-postgresql.html#metadata",
-    "href": "decisions/20231108-neon-postgresql.html#metadata",
-    "title": "Proposed: Adopting Neon for a More Manageable Backend at V-Sekai",
+    "objectID": "decisions/20221205-port-renik-to-many-bone-ik.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20221205-port-renik-to-many-bone-ik.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Port RENIK to Many Bone IK for better quality",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai, Fire\nTags: Backend Management, Neon, Ease-of-Use, Postgres"
+    "text": "IK is hard and not a few lines of code."
   },
   {
-    "objectID": "decisions/20231108-neon-postgresql.html#the-backdrop",
-    "href": "decisions/20231108-neon-postgresql.html#the-backdrop",
-    "title": "Proposed: Adopting Neon for a More Manageable Backend at V-Sekai",
+    "objectID": "decisions/20221205-port-renik-to-many-bone-ik.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20221205-port-renik-to-many-bone-ik.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Port RENIK to Many Bone IK for better quality",
     "section": "",
-    "text": "V-Sekai’s current setup with Postgres and Uro is hitting roadblocks due to the lack of dedicated server management expertise."
+    "text": "We know how to do it."
   },
   {
-    "objectID": "decisions/20231108-neon-postgresql.html#the-challenge",
-    "href": "decisions/20231108-neon-postgresql.html#the-challenge",
-    "title": "Proposed: Adopting Neon for a More Manageable Backend at V-Sekai",
+    "objectID": "decisions/20221205-port-renik-to-many-bone-ik.html#references",
+    "href": "decisions/20221205-port-renik-to-many-bone-ik.html#references",
+    "title": "Proposed: Port RENIK to Many Bone IK for better quality",
     "section": "",
-    "text": "Is Neon the key to a more manageable Postgres system that fits our community-driven model?"
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20231108-neon-postgresql.html#the-strategy",
-    "href": "decisions/20231108-neon-postgresql.html#the-strategy",
-    "title": "Proposed: Adopting Neon for a More Manageable Backend at V-Sekai",
+    "objectID": "decisions/20221205-port-renik-to-many-bone-ik.html#license-of-the-contribution",
+    "href": "decisions/20221205-port-renik-to-many-bone-ik.html#license-of-the-contribution",
+    "title": "Proposed: Port RENIK to Many Bone IK for better quality",
     "section": "",
-    "text": "We plan to run a Neon pilot to see if it eases our backend management woes. Steps include:\n\nTesting Neon’s compatibility with our current data.\nExploring Neon’s manageability features.\nDrafting straightforward documentation for team reference.\nEnsuring a hassle-free data migration process."
+    "text": "MIT License\n\nCopyright (c) 2018-2022 SaracenOne\nCopyright (c) 2019-2022 K. S. Ernest (iFire) Lee (fire)\nCopyright (c) 2020-2022 Lyuma\nCopyright (c) 2020-2022 MMMaellon\nCopyright (c) 2022 V-Sekai Contributors\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
   },
   {
-    "objectID": "decisions/20231108-neon-postgresql.html#the-upside",
-    "href": "decisions/20231108-neon-postgresql.html#the-upside",
-    "title": "Proposed: Adopting Neon for a More Manageable Backend at V-Sekai",
+    "objectID": "decisions/20210724-Spreadsheet-animation-preview.html",
+    "href": "decisions/20210724-Spreadsheet-animation-preview.html",
+    "title": "Proposed: Spreadsheet Animation Preview",
     "section": "",
-    "text": "A more user-friendly backend system.\nReduced need for server management know-how.\nPotential performance benefits are a bonus."
+    "text": "Proposed: Spreadsheet Animation Preview\n\nContext and Problem Statement\nWorkflow for QA testing animations\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nLoad in a spreadsheet dataview of animation tracks and play animation back.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nWork on https://github.com/V-Sekai/godot-hop-spin-dance.\n\nDisplay a spreadsheet view.\n\n\n\n\nKey\nEN\nAnimation\nQueue Play\n\n\n\n\n\n\n\n\n\n\n\n\nShow the debug animation tree.\nShow graphical playback on a VRM character\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot trivial, combines a spreadsheet with animations, an animation tree debugger and a animation player.\n\n\nPositive Consequences\nAble to QA animations easier.\n\n\nNegative Consequences\nA sizable amount of work.\n\n\nIs there a reason why this should be core and done by us?\nWe care about characters.\n\n\nReferences\nGDC 2021 Summer:\n\n‘Genshin Impact’: Building a Scalable AI System This session reviews some of AI programming challenges in developing open-world game ‘Genshin Impact’ and describes several handful methods to improve AI system scalability. It details an AI framework and production pipeline that allow designers to craft huge amount of AI archetypes quickly and flexibly. Next, Genshin’s pathfinding service is introduced, an approach to reduce NavMesh disk and memory space overhead, caused by continuously-growing world map. Finally, this session discusses AI performance optimization and shows how AI system can be modularized and broke down into multi-threaded tasks on CPU.\nEmotional Systemic Facial of ‘Last of Us Part II’ As graphic fidelity in video games has rapidly accelerated, one aspect of development has overwhelmingly remained stagnant; in-game character emotions. In this talk, Naughty Dog explores how they addressed this industry wide limitation in The Last of Us Part II. Represented by team members from character rigging, animation, dialog, and design; this talk comprehensively covers how character emotion was brought into gameplay ranging from nuanced narrative moments to adrenaline charged melee combat. Learn about the challenges, implementation, and innovation that occurred to develop the systemic emotion system that brought over 65 characters speaking 13 languages with up to 20 individual emotions to life.\nMotion Matching in ‘The Last of Us Part II’ Naughty Dog is known for the animation quality of their titles. For The Last of Us Part II, they decided to take a leap of faith and switch to at that time pretty experimental animation system called Motion Matching. Two Naughty Dog technical animators will tell you the story of initial joy, later frustration and ultimate fear as the development of the new project went on and but not everything went according to plan. Thanks to many clever solution, hard work and a very talented team, Naughty Dog was able to ship a game that was unanimously praised for animation quality among critics and players.\nhttps://tabletomarkdown.com/convert-spreadsheet-to-markdown/\nhttps://github.com/deflinhec/GodotGoogleSheet\nhttps://baserow.io/\nhttps://github.com/fenix-hub/godot-engine.easy-charts\nhttps://github.com/godotengine/godot/pull/32408\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20231108-neon-postgresql.html#the-downside",
-    "href": "decisions/20231108-neon-postgresql.html#the-downside",
-    "title": "Proposed: Adopting Neon for a More Manageable Backend at V-Sekai",
+    "objectID": "decisions/20240502-mvsqlite-launchd.html",
+    "href": "decisions/20240502-mvsqlite-launchd.html",
+    "title": "Proposed: Launching the mvsqlite rdbms server",
     "section": "",
-    "text": "Time investment in learning a new system.\nPossible initial dependence on external support."
+    "text": "In software development and maintenance, automation of routine tasks is crucial for efficiency. One such task is launching a database server at system startup. For macOS users, this can be achieved using launchd, an open-source service management framework. In this context, we are specifically interested in automating the launch of the mvsqlite RDBMS server.\n\n\n\nThe task at hand is to create a launchd service for macOS that will automatically run the following command at system startup:\n/usr/local/bin/mvstore --data-plane 127.0.0.1:7000 --admin-api 127.0.0.1:7001 --metadata-prefix mvstore-test --raw-data-prefix m --auto-create-namespace --cluster /usr/local/etc/foundationdb/fdb.cluster\nAdditionally, we need to be able to retrieve logs from this service and check its status.\n\n\n\nTo solve this problem, we can create a .plist file in the ~/Library/LaunchAgents directory. This file will define our launchd service and specify the command it should run. We can also add keys to redirect the standard output and error to log files. Finally, we can use the launchctl list command to check the status of our service.\nHere are the detailed steps:\n\n\n\nOpen Terminal and navigate to the LaunchAgents directory:\n\ncd ~/Library/LaunchAgents\n\nCreate a new .plist file called com.user.mvstore.plist:\n\ntouch com.user.mvstore.plist\n\nOpen the file with a text editor (e.g., nano):\n\nnano com.user.mvstore.plist\n\nPaste the following content into the file:\n\n&lt;?xml version=\"1.0\" encoding=\"UTF-8\"?&gt;\n&lt;!DOCTYPE plist PUBLIC \"-//Apple//DTD PLIST 1.0//EN\" \"http://www.apple.com/DTDs/PropertyList-1.0.dtd\"&gt;\n&lt;plist version=\"1.0\"&gt;\n&lt;dict&gt;\n    &lt;key&gt;Label&lt;/key&gt;\n    &lt;string&gt;com.user.mvstore&lt;/string&gt;\n    &lt;key&gt;ProgramArguments&lt;/key&gt;\n    &lt;array&gt;\n        &lt;string&gt;/usr/local/bin/mvstore&lt;/string&gt;\n        &lt;string&gt;--data-plane&lt;/string&gt;\n        &lt;string&gt;127.0.0.1:7000&lt;/string&gt;\n        &lt;string&gt;--admin-api&lt;/string&gt;\n        &lt;string&gt;127.0.0.1:7001&lt;/string&gt;\n        &lt;string&gt;--metadata-prefix&lt;/string&gt;\n        &lt;string&gt;mvstore-test&lt;/string&gt;\n        &lt;string&gt;--raw-data-prefix&lt;/string&gt;\n        &lt;string&gt;m&lt;/string&gt;\n        &lt;string&gt;--auto-create-namespace&lt;/string&gt;\n        &lt;string&gt;--cluster&lt;/string&gt;\n        &lt;string&gt;/usr/local/etc/foundationdb/fdb.cluster&lt;/string&gt;\n    &lt;/array&gt;\n    &lt;key&gt;RunAtLoad&lt;/key&gt;\n    &lt;true/&gt;\n    &lt;key&gt;EnvironmentVariables&lt;/key&gt;\n    &lt;dict&gt;\n        &lt;key&gt;RUST_LOG&lt;/key&gt;\n        &lt;string&gt;info&lt;/string&gt;\n        &lt;key&gt;DYLD_LIBRARY_PATH&lt;/key&gt;\n        &lt;string&gt;/usr/local/lib&lt;/string&gt;\n    &lt;/dict&gt;\n&lt;/dict&gt;\n&lt;/plist&gt;\n\nSave and close the file.\nLoad the new service:\n\nlaunchctl load ~/Library/LaunchAgents/com.user.mvstore.plist\n\n\n\nTo retrieve logs from the launchd service, add the StandardOutPath and StandardErrorPath keys to the .plist file. These keys will redirect the standard output (stdout) and standard error (stderr) to specified log files.\n\n\n\nTo check the launchd status for mvsqlite, use the launchctl list command:\nlaunchctl list | grep mvstore\n\n\n\n\nAutomating tasks with launchd can save time and reduce the risk of errors. It also provides a standardized way to manage services on macOS.\n\n\n\nThe main downside is that launchd is specific to macOS, so this solution won’t work on other operating systems.\n\n\n\nAn alternative approach could be to use cron jobs or another task scheduler, but these may not offer the same level of control and flexibility as launchd.\n\n\n\nThis solution is most useful for developers who frequently need to run certain commands at system startup. It may be less relevant for casual users or those who don’t use macOS.\n\n\n\nThis solution was developed in-house by the V-Sekai development team.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAssistance provided by Aria, an AI assistant."
   },
   {
-    "objectID": "decisions/20231108-neon-postgresql.html#the-road-not-taken",
-    "href": "decisions/20231108-neon-postgresql.html#the-road-not-taken",
-    "title": "Proposed: Adopting Neon for a More Manageable Backend at V-Sekai",
+    "objectID": "decisions/20240502-mvsqlite-launchd.html#context",
+    "href": "decisions/20240502-mvsqlite-launchd.html#context",
+    "title": "Proposed: Launching the mvsqlite rdbms server",
     "section": "",
-    "text": "Sticking with Uro or other complex solutions that don’t align with our manageability goals."
+    "text": "In software development and maintenance, automation of routine tasks is crucial for efficiency. One such task is launching a database server at system startup. For macOS users, this can be achieved using launchd, an open-source service management framework. In this context, we are specifically interested in automating the launch of the mvsqlite RDBMS server."
   },
   {
-    "objectID": "decisions/20231108-neon-postgresql.html#the-infrequent-use-case",
-    "href": "decisions/20231108-neon-postgresql.html#the-infrequent-use-case",
-    "title": "Proposed: Adopting Neon for a More Manageable Backend at V-Sekai",
+    "objectID": "decisions/20240502-mvsqlite-launchd.html#problem-statement",
+    "href": "decisions/20240502-mvsqlite-launchd.html#problem-statement",
+    "title": "Proposed: Launching the mvsqlite rdbms server",
     "section": "",
-    "text": "Situations where Uro’s specific configurations are essential; these will require special attention."
+    "text": "The task at hand is to create a launchd service for macOS that will automatically run the following command at system startup:\n/usr/local/bin/mvstore --data-plane 127.0.0.1:7000 --admin-api 127.0.0.1:7001 --metadata-prefix mvstore-test --raw-data-prefix m --auto-create-namespace --cluster /usr/local/etc/foundationdb/fdb.cluster\nAdditionally, we need to be able to retrieve logs from this service and check its status."
   },
   {
-    "objectID": "decisions/20231108-neon-postgresql.html#in-core-and-done-by-us",
-    "href": "decisions/20231108-neon-postgresql.html#in-core-and-done-by-us",
-    "title": "Proposed: Adopting Neon for a More Manageable Backend at V-Sekai",
+    "objectID": "decisions/20240502-mvsqlite-launchd.html#solution",
+    "href": "decisions/20240502-mvsqlite-launchd.html#solution",
+    "title": "Proposed: Launching the mvsqlite rdbms server",
     "section": "",
-    "text": "Planning to make Neon a central part of our backend, relying on our collective skills to implement it."
+    "text": "To solve this problem, we can create a .plist file in the ~/Library/LaunchAgents directory. This file will define our launchd service and specify the command it should run. We can also add keys to redirect the standard output and error to log files. Finally, we can use the launchctl list command to check the status of our service.\nHere are the detailed steps:\n\n\n\nOpen Terminal and navigate to the LaunchAgents directory:\n\ncd ~/Library/LaunchAgents\n\nCreate a new .plist file called com.user.mvstore.plist:\n\ntouch com.user.mvstore.plist\n\nOpen the file with a text editor (e.g., nano):\n\nnano com.user.mvstore.plist\n\nPaste the following content into the file:\n\n&lt;?xml version=\"1.0\" encoding=\"UTF-8\"?&gt;\n&lt;!DOCTYPE plist PUBLIC \"-//Apple//DTD PLIST 1.0//EN\" \"http://www.apple.com/DTDs/PropertyList-1.0.dtd\"&gt;\n&lt;plist version=\"1.0\"&gt;\n&lt;dict&gt;\n    &lt;key&gt;Label&lt;/key&gt;\n    &lt;string&gt;com.user.mvstore&lt;/string&gt;\n    &lt;key&gt;ProgramArguments&lt;/key&gt;\n    &lt;array&gt;\n        &lt;string&gt;/usr/local/bin/mvstore&lt;/string&gt;\n        &lt;string&gt;--data-plane&lt;/string&gt;\n        &lt;string&gt;127.0.0.1:7000&lt;/string&gt;\n        &lt;string&gt;--admin-api&lt;/string&gt;\n        &lt;string&gt;127.0.0.1:7001&lt;/string&gt;\n        &lt;string&gt;--metadata-prefix&lt;/string&gt;\n        &lt;string&gt;mvstore-test&lt;/string&gt;\n        &lt;string&gt;--raw-data-prefix&lt;/string&gt;\n        &lt;string&gt;m&lt;/string&gt;\n        &lt;string&gt;--auto-create-namespace&lt;/string&gt;\n        &lt;string&gt;--cluster&lt;/string&gt;\n        &lt;string&gt;/usr/local/etc/foundationdb/fdb.cluster&lt;/string&gt;\n    &lt;/array&gt;\n    &lt;key&gt;RunAtLoad&lt;/key&gt;\n    &lt;true/&gt;\n    &lt;key&gt;EnvironmentVariables&lt;/key&gt;\n    &lt;dict&gt;\n        &lt;key&gt;RUST_LOG&lt;/key&gt;\n        &lt;string&gt;info&lt;/string&gt;\n        &lt;key&gt;DYLD_LIBRARY_PATH&lt;/key&gt;\n        &lt;string&gt;/usr/local/lib&lt;/string&gt;\n    &lt;/dict&gt;\n&lt;/dict&gt;\n&lt;/plist&gt;\n\nSave and close the file.\nLoad the new service:\n\nlaunchctl load ~/Library/LaunchAgents/com.user.mvstore.plist\n\n\n\nTo retrieve logs from the launchd service, add the StandardOutPath and StandardErrorPath keys to the .plist file. These keys will redirect the standard output (stdout) and standard error (stderr) to specified log files.\n\n\n\nTo check the launchd status for mvsqlite, use the launchctl list command:\nlaunchctl list | grep mvstore"
   },
   {
-    "objectID": "decisions/20231108-neon-postgresql.html#further-reading",
-    "href": "decisions/20231108-neon-postgresql.html#further-reading",
-    "title": "Proposed: Adopting Neon for a More Manageable Backend at V-Sekai",
+    "objectID": "decisions/20240502-mvsqlite-launchd.html#benefits",
+    "href": "decisions/20240502-mvsqlite-launchd.html#benefits",
+    "title": "Proposed: Launching the mvsqlite rdbms server",
     "section": "",
-    "text": "V-Sekai on GitHub\nNeon’s Architecture\n\nThis article was assisted by AI."
+    "text": "Automating tasks with launchd can save time and reduce the risk of errors. It also provides a standardized way to manage services on macOS."
   },
   {
-    "objectID": "authors.html",
-    "href": "authors.html",
-    "title": "V-Sekai Manual Authors",
+    "objectID": "decisions/20240502-mvsqlite-launchd.html#downsides",
+    "href": "decisions/20240502-mvsqlite-launchd.html#downsides",
+    "title": "Proposed: Launching the mvsqlite rdbms server",
     "section": "",
-    "text": "V-Sekai Manual Authors\n\nK. S. Ernest (iFire) Lee (fire)\nLyuma\nMalekiRe Malek\nGDQuest"
+    "text": "The main downside is that launchd is specific to macOS, so this solution won’t work on other operating systems."
   },
   {
-    "objectID": "changelog.html",
-    "href": "changelog.html",
-    "title": "Changes to V-Sekai",
+    "objectID": "decisions/20240502-mvsqlite-launchd.html#the-road-not-taken",
+    "href": "decisions/20240502-mvsqlite-launchd.html#the-road-not-taken",
+    "title": "Proposed: Launching the mvsqlite rdbms server",
     "section": "",
-    "text": "All notable changes to this project will be documented in this file.\nThe format is based on Keep a Changelog, and this project does not adhere to Semantic Versioning.\nAdded for new features.\nChanged for changes in existing functionality.\nDeprecated for soon-to-be removed features.\nRemoved for now removed features.\nFixed for any bug fixes.\nSecurity in case of vulnerabilities.\n\n\n\n\n\n\n   \n     \n     \n       Order By\n       Default\n         \n          Title\n        \n     \n  \n    \n      \n      \n    \n\n\n\n\n\nTitle\n\n\n\n\n\n\nV-Sekai Changelog - October 2024\n\n\n\n\nV-Sekai Changelog - September 2024\n\n\n\n\nV-Sekai Changelog - July 2024\n\n\n\n\nSpecial Notice: V-Sekai 2023-2024\n\n\n\n\nV-Sekai Changelog - June 2024\n\n\n\n\nV-Sekai Changelog - May 2024\n\n\n\n\nV-Sekai Changelog - March 2024\n\n\n\n\nV-Sekai Changelog - February 2024\n\n\n\n\nV-Sekai Changelog - January 2024\n\n\n\n\nV-Sekai Changelog - December 2023\n\n\n\n\nV-Sekai Changelog - November 2023\n\n\n\n\nV-Sekai Changelog - October 2023\n\n\n\n\nV-Sekai Changelog - September 2023\n\n\n\n\nV-Sekai Changelog - August 2023\n\n\n\n\nV-Sekai Changelog - July 2023\n\n\n\n\nV-Sekai Changelog - 2023-06\n\n\n\n\nV-Sekai Changelog - 2023-05\n\n\n\n\nV-Sekai Changelog - 2023-03\n\n\n\n\nV-Sekai Changelog - 2023-02\n\n\n\n\nV-Sekai Changelog - 2023-01\n\n\n\n\nV-Sekai Changelog - 2022-12\n\n\n\n\nV-Sekai Changelog - 2022-11\n\n\n\n\nV-Sekai Changelog - 2022-10\n\n\n\n\nV-Sekai Changelog - 2022-09\n\n\n\n\nV-Sekai Changelog - 2022-08\n\n\n\n\nV-Sekai Changelog - 2022-06\n\n\n\n\nV-Sekai Changelog - 2022-05\n\n\n\n\nV-Sekai Changelog - 2022-04\n\n\n\n\nV-Sekai Changelog - 2022-03\n\n\n\n\nV-Sekai Changelog - 2022-02\n\n\n\n\nV-Sekai Changelog - 2022-01\n\n\n\n\nV-Sekai Changelog - 2021-11\n\n\n\n\nV-Sekai Changelog - 2021-10\n\n\n\n\nV-Sekai Changelog - 2021-09\n\n\n\n\nV-Sekai Changelog - 2021-08\n\n\n\n\nV-Sekai Changelog - 2021-07\n\n\n\n\nV-Sekai Changelog - 2021-06\n\n\n\n\nV-Sekai Changelog - 2021-05\n\n\n\n\nV-Sekai Changelog - 2021-04\n\n\n\n\n\nNo matching items"
+    "text": "An alternative approach could be to use cron jobs or another task scheduler, but these may not offer the same level of control and flexibility as launchd."
   },
   {
-    "objectID": "decisions.html",
-    "href": "decisions.html",
-    "title": "Decisions of V-Sekai",
+    "objectID": "decisions/20240502-mvsqlite-launchd.html#infrequent-use-case",
+    "href": "decisions/20240502-mvsqlite-launchd.html#infrequent-use-case",
+    "title": "Proposed: Launching the mvsqlite rdbms server",
     "section": "",
-    "text": "Order By\n       Default\n         \n          Title\n        \n     \n  \n\n\n\n\n\nTitle\n\n\nReading Time\n\n\nFile Name\n\n\n\n\n\n\nProposed: Template\n\n\n1 min\n\n\npresent-proposal-template.md\n\n\n\n\nAccepted: AI Assisted Style Guide\n\n\n2 min\n\n\nai-assisted-proposal-style-guide.md\n\n\n\n\nProposal: Use Data Tables for Godot Constraints\n\n\n2 min\n\n\n20241028-use-data-tables-for-godot-constraints.md\n\n\n\n\nProposed: Reduce Size Difference Between Capsules and Mesh Volume\n\n\n2 min\n\n\n20241019-reduce-size-difference-between-capsules-and-mesh-volume.md\n\n\n\n\nProposed: Evaluate three proposals for V-Sekai content distribution\n\n\n3 min\n\n\n20241016-instantiating-v-sekai-content.md\n\n\n\n\nProposed: Editing Character Body Bone Constraints in Immersive Mode\n\n\n8 min\n\n\n20241014-xr-interface-for-rigging.md\n\n\n\n\nProposed: Basic Real-Time Interaction for Character and World Scenes\n\n\n5 min\n\n\n20241014-basic-realtime-interaction.md\n\n\n\n\nProposed: Updater No-Op Implementation Using Velopack\n\n\n2 min\n\n\n20241014-app-updater.md\n\n\n\n\nProposed: Recovering MakeHuman Parameters Using Depth Map Comparison with Godot Engine\n\n\n3 min\n\n\n20241011-recovering-makehuman-parameters.md\n\n\n\n\nAccepted: Restoring Default User Directory Structure in Windows 11\n\n\n2 min\n\n\n20241006-restore-onedrive-shortcut-overrides.md\n\n\n\n\nProposed: Small V-Sekai Creation Tools\n\n\n2 min\n\n\n20241001-small-game-tools.md\n\n\n\n\nAccepted: Godot Engine XR Elite HMD Conference Setup\n\n\n3 min\n\n\n20240914-godot-engine-xr-elite-conference-setup.md\n\n\n\n\nProposed: Revised Tracker Configuration and Constraints for HTC VIVE XR Elite\n\n\n3 min\n\n\n20240905-revised-tracker-configuration-and-constraints.md\n\n\n\n\nProposed: Transition to Dokku from Kubernetes Proposal\n\n\n2 min\n\n\n20240830-use-dokku-to-host-vsk-backend.md\n\n\n\n\nAccepted: PCI-E Lane Depletion and Thunderbolt 4 Issues\n\n\n3 min\n\n\n20240830-pcie-lane-depletion-thunderbolt-4-issues.md\n\n\n\n\nProposed: FFMPEG Wave/Mic and Speaker/Play\n\n\n5 min\n\n\n20240824-ffmpeg-wav-mic-speaker-play.md\n\n\n\n\nProposed: Improving Connectivity for Valve StreamVR Light House Dongles\n\n\n2 min\n\n\n20240810-steamvr-dongles-separate.md\n\n\n\n\nProposal: Core V-Sekai Scripting with Wasm\n\n\n4 min\n\n\n20240717-core-vsekai-scripting.md\n\n\n\n\nProposed: Create a Conceptual Model of VRChat Networking\n\n\n47 min\n\n\n20240715-vrchat-networking-mental-model.md\n\n\n\n\nProposed: Use shrink wrap blender modifier to fit\n\n\n2 min\n\n\n20240712-use-shrinkwrap-blender-modiifer-to-fit.md\n\n\n\n\nProposed: Networking PCVR with the Web\n\n\n3 min\n\n\n20240710-web-and-pcvr-networking.md\n\n\n\n\nProposed: Use WebRTC to Native to Interop with Godot Engine\n\n\n2 min\n\n\n20240710-use-webrtc-to-native-interop.md\n\n\n\n\nProposed: Use Godot Engine Web Threaded\n\n\n3 min\n\n\n20240710-use-godot-engine-web-threaded.md\n\n\n\n\nProposed: Focus on PCVR and the Web\n\n\n2 min\n\n\n20240710-platform-focus-on-pcvr-and-web.md\n\n\n\n\nProposed: Convert Blender CC0 Base Mesh to Godot Engine T-Pose\n\n\n4 min\n\n\n20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.md\n\n\n\n\nProposed: Art Direction in V-Sekai Process\n\n\n2 min\n\n\n20240710-art-direction-in-vsekai.md\n\n\n\n\nProposed: A Wired-First Strategy for PCVR\n\n\n2 min\n\n\n20240709-wired-first.md\n\n\n\n\nProposed: Set Nvidia Watt Limit with Anwave\n\n\n2 min\n\n\n20240709-anwave-set-nvidia-watt-limit.md\n\n\n\n\nProposed: V-Sekai: My Life as a Princess\n\n\n5 min\n\n\n20240708-vsekai-my-life-as-a-queen.md\n\n\n\n\nProposed: Maximum Streaming Bill of Materials Setup for Motion Capture\n\n\n8 min\n\n\n20240706-motion-capture-bill-of-materials.md\n\n\n\n\nProposal: RPG Town in V-Sekai\n\n\n3 min\n\n\n20240705-rpg_town.md\n\n\n\n\nProposed: Use motion transformers for motion prediction\n\n\n2 min\n\n\n20240630-use-motion-transformers-for-prediction.md\n\n\n\n\nSuperceded: RISCV Binaries as Shared Libraries\n\n\n3 min\n\n\n20240627-gdextension-as-libriscv.md\n\n\n\n\nProposed: Every Commit Push Pass Cicd\n\n\n2 min\n\n\n20240627-every-commit-push-pass-cicd.md\n\n\n\n\nProposed: Update python3 macOS Certificates\n\n\n3 min\n\n\n20240626-update-python3-macos-certicates.md\n\n\n\n\nProposed: Why did we build “Uro”?\n\n\n3 min\n\n\n20240623-what-is-uro-backend.md\n\n\n\n\nProposed: Talk Length Game Prototypes\n\n\n2 min\n\n\n20240623-talk-length-prototypes.md\n\n\n\n\nProposal: Only Save Tools in Our CDN\n\n\n2 min\n\n\n20240623-only-save-tools-in-our-cdn.md\n\n\n\n\nProposed: Use GitHub Actions and Digital Ocean Spaces for a V-Sekai Launcher\n\n\n2 min\n\n\n20240623-do-cdn-for-launcher.md\n\n\n\n\nProposed: Create a process for testing V-Sekai.\n\n\n2 min\n\n\n20240622-process-for-testing-vsekai.md\n\n\n\n\nAccepted: GoCD Agent Docker Image Update\n\n\n2 min\n\n\n20240622-gocd-agent-docker-image-update.md\n\n\n\n\nProposed: Build V-Sekai editor for many platforms\n\n\n2 min\n\n\n20240622-build-for-many-platforms.md\n\n\n\n\nProposed: Command Traces with Server Backend\n\n\n1 min\n\n\n20240621-proposal-template copy.md\n\n\n\n\nProposed: Image Captioning Tool\n\n\n2 min\n\n\n20240621-caption-photos-for-cicd.md\n\n\n\n\nProposed: Transforming Schedule DAG into a Left-child Right-sibling Binary Tree\n\n\n3 min\n\n\n20240618-schedule-as-binary-tree.md\n\n\n\n\nProposed: 4 Player Test V-Sekai\n\n\n2 min\n\n\n20240618-4-player-test-vsekai.md\n\n\n\n\nProposed: Triangle to Quad Mesh Dataset Creation\n\n\n2 min\n\n\n20240616-request-for-quad-mesh-dataset.md\n\n\n\n\nProposed: Explain the concept of Mesh Transformers\n\n\n2 min\n\n\n20240615-what-is-mesh-transformers.md\n\n\n\n\nProposed: Dataset Scaling for Training Mesh Transformer\n\n\n2 min\n\n\n20240613-training-dataset.md\n\n\n\n\nProposed: Dataset Creation with CSG\n\n\n3 min\n\n\n20240613-training-dataset-creation-with-csg.md\n\n\n\n\nProposed: Modify the Mesh Transformer for Quads\n\n\n2 min\n\n\n20240613-modifying-the-mesh-transformer-for-quads.md\n\n\n\n\nProposed: Training Mesh Transformer for 3D Avatar Creation\n\n\n3 min\n\n\n20240613-1k-quad-limit.md\n\n\n\n\nProposed: Managing Multiple Training Runs in Separate Pods\n\n\n2 min\n\n\n20240611-test-1x-and-4x.md\n\n\n\n\nProposed: Switch learning rate to be lower.\n\n\n2 min\n\n\n20240611-lower-learning-rate.md\n\n\n\n\nAccepted: Better Skeleton Merge with Robust Skin Weight Transfer\n\n\n6 min\n\n\n20240608-skin-weight-transfer-skeleton-merge.md\n\n\n\n\nAccepted: Use the Humanoid Profile for Character Motion Mirroring\n\n\n5 min\n\n\n20240608-for-skeleton-mirroring-use-the-godot-humanoid.md\n\n\n\n\nProposal: Sustainable Version Management for Godot Engine in V-Sekai\n\n\n3 min\n\n\n20240605-sustainable-version-management-for-godot-engine-in-v-sekai.md\n\n\n\n\nProposed: Improve the Godot Ecosystem\n\n\n3 min\n\n\n20240529-improve-godot-import-ecosystem.md\n\n\n\n\nProposed: Godot Engine as Wasm Importer\n\n\n2 min\n\n\n20240528-pipeline-godot-wasm-importer.md\n\n\n\n\nProposed: Draft WebRTC Relay Test\n\n\n1 min\n\n\n20240522-webrtc-relay-test.md\n\n\n\n\nDraft: shadermotion to BVH\n\n\n2 min\n\n\n20240522-shader-motion-to-bvh.md\n\n\n\n\nDraft: View the worlds and interact with people in VR without being in VR via a Discord Inward Portal\n\n\n2 min\n\n\n20240522-discord-inworld-portal.md\n\n\n\n\nDraft: Notify community members and users about activity and updates via a Discord bot\n\n\n3 min\n\n\n20240522-discord-bot.md\n\n\n\n\nAccepted: Wasm Cache Incident Report\n\n\n2 min\n\n\n20240511-wasm-cache-incident.md\n\n\n\n\nRejected: VR Game with 80 Players and One World Server\n\n\n2 min\n\n\n20240511-review-80-vr.md\n\n\n\n\nProposed: Can I use V-Sekai for 3d assets & 3d extensions?\n\n\n2 min\n\n\n20240502-where-can-I-use-gltf.md\n\n\n\n\nProposed: Launching the mvsqlite rdbms server\n\n\n4 min\n\n\n20240502-mvsqlite-launchd.md\n\n\n\n\nProposed: Stress Testing Godot Engine’s Networking System\n\n\n3 min\n\n\n20240502-mesh-object-sync-benchmark.md\n\n\n\n\nProposed: Process the glTF2 input file and return it as is\n\n\n2 min\n\n\n20240502-membrane-framework-identity-post.md\n\n\n\n\nProposed: Enable Windows 11 Installation on Older Computers\n\n\n2 min\n\n\n20240502-install-windows-on-older-computers.md\n\n\n\n\nProposed: Workflows for 3D Model Conversion\n\n\n3 min\n\n\n20240502-gltf-fbx-tscn-vrm.md\n\n\n\n\nProposed: Stuck / Recharge Cycle\n\n\n2 min\n\n\n20240425-recharge-cycle.md\n\n\n\n\nProposed: ChatGPT-4 Based Proposal Prompt System\n\n\n2 min\n\n\n20240425-proposal-prompt-system.md\n\n\n\n\nAccepted: Prioritizing Valve Controllers Over Meta Quest 3 Controllers\n\n\n2 min\n\n\n20240424-reset-steamvr-controllers.md\n\n\n\n\nAccepted: Building a Metaverse with Glue Mechanic in V-Sekai\n\n\n2 min\n\n\n20240423-building-metaverse-with-glue-mechanic.md\n\n\n\n\nProposed: Town Courier\n\n\n3 min\n\n\n20240418-college-quest.md\n\n\n\n\nProposed: Implementing a 3D Previewer for GLTF with XMP Metadata\n\n\n2 min\n\n\n20240416-previewer-upload-gltf-to-glb.md\n\n\n\n\nProposed: Train quad-based Meshgpt within constraints\n\n\n3 min\n\n\n20240413-training-quad-based-meshgpt-with-40gb-vram.md\n\n\n\n\nProposed: Calling Open Source LLM with Aria\n\n\n2 min\n\n\n20240413-calling-opensource-llm-with-aria.md\n\n\n\n\nProposed: Implementing a 3D Multiplayer Movement System with Parented Objects and Inventory Management\n\n\n3 min\n\n\n20240411-multiplayer-movement-with-parented-obejcts.md\n\n\n\n\nRejected: Binding GDExtension to a C-like Language for Libgodot to Implement a Distributed Simulation\n\n\n2 min\n\n\n20240411-elixir-libgodot-zig.md\n\n\n\n\nProposed: Use Bundlex for Binding GDExtension to Elixir for Libgodot to Implement a Distributed Simulation\n\n\n2 min\n\n\n20240411-elixir-libgodot-bundlex.md\n\n\n\n\nProposed: Implementing Elixir Data Models for Memory, Local, Bulk, and Global Storage\n\n\n3 min\n\n\n20240410-data-storage-elixir.md\n\n\n\n\nRejected: RabbitMQ RA vs SQLite on FoundationDB vs CockroachDB\n\n\n3 min\n\n\n20240409-elixir-raft-vs-sqlite-fdb.md\n\n\n\n\nAccepted: “Sunny Park” Test Case for 3D Tile Sync\n\n\n2 min\n\n\n20240409-crud-godot-tiles.md\n\n\n\n\nAccepted: Focusing on PCVR vs Android Build vs Web Build\n\n\n2 min\n\n\n20240407-pcvr-vs-standalone.md\n\n\n\n\nProposed: Web-Based Exploration of V-Sekai\n\n\n2 min\n\n\n20240406-web-based-explore.md\n\n\n\n\nProposed: Provide a V-Sekai Starter Kit\n\n\n2 min\n\n\n20240406-itch-github-actions.md\n\n\n\n\nProposed: Material Shader Graphic Shirt with Sharp Edges\n\n\n3 min\n\n\n20240401-shader-graphic.md\n\n\n\n\nProposed: VRC and VRM compatibility\n\n\n4 min\n\n\n20240331-vrc-vrm-compatibility.md\n\n\n\n\nAccepted: k8s on harvester hci\n\n\n4 min\n\n\n20240330-k8s-harvester-hci.md\n\n\n\n\nProposed: Hyperv windows Harvester Test\n\n\n2 min\n\n\n20240330-hyperv-harvester-test.md\n\n\n\n\nProposed: Integrating Helm for Kubernetes Runner Installation with S3 Cache\n\n\n4 min\n\n\n20240330-gitlab-helm.md\n\n\n\n\nProposed: CI/CD Setup with Docker and Other Platforms\n\n\n3 min\n\n\n20240330-cicd-gitlab.md\n\n\n\n\nProposed: Installing Helm Chart from a Git Repository using Rancher\n\n\n2 min\n\n\n20240330-bitnami-rancher-helm-catalog.md\n\n\n\n\nProposed: V-Sekai Setup as a Ready-to-Go Kit\n\n\n2 min\n\n\n20240329-ready-to-go-kit-windows-11.md\n\n\n\n\nProposed: Teaching Large Language Models (LLMs) with Goal-Task Planners\n\n\n2 min\n\n\n20240326-verifying-and-finetuning-plans.md\n\n\n\n\nProposed: “Cafe Serenade” - A VR Dating Sim Experience\n\n\n3 min\n\n\n20240326-heartstrings-vr.md\n\n\n\n\nProposed: for 3d Asset Schema Design and Database Backend Selection\n\n\n2 min\n\n\n20240325-table-avatar-embedded-xmp.md\n\n\n\n\nProposed: Synchronizing Blender and FDB-SQLite for Proxy Movement\n\n\n2 min\n\n\n20240325-fdb-sqlite-blender-godot.md\n\n\n\n\nProposed: V-Sekai Implementation Using SLC Framework\n\n\n2 min\n\n\n20240324-v-sekai-as-slc.md\n\n\n\n\nProposed: Real-Time Motion Capture and Animation Synchronization\n\n\n2 min\n\n\n20240314-live-collab.md\n\n\n\n\nProposed: Implement Ra in V-Sekai\n\n\n1 min\n\n\n20240307-rabbitmq-ra.md\n\n\n\n\nProposed: V-Sekai Game Launcher\n\n\n3 min\n\n\n20240305-v-sekai-launcher.md\n\n\n\n\nProposed VRM mtoon in Substance Designer\n\n\n32 min\n\n\n20240218-vrm-substance-editor.md\n\n\n\n\nAccepted: VRM Acronym Correction\n\n\n1 min\n\n\n20240218-vrm-acronym-correction.md\n\n\n\n\nProposed: Blender to Godot API Conversion\n\n\n2 min\n\n\n20240218-blender-to-godot.md\n\n\n\n\nProposed: for using workloads to emulate the usage patterns\n\n\n2 min\n\n\n20240217-workload-benchmarking.md\n\n\n\n\nProposed: Adoption of Intended Effort Versioning (EffVer) in V-Sekai\n\n\n2 min\n\n\n20240217-intended-effort-versioning.md\n\n\n\n\nProposed: Implementation of Essential Tuple Normalization Form (ETNF) for relational databases (rdbms, sql)\n\n\n7 min\n\n\n20240217-essential-typle-normalization-form.md\n\n\n\n\nProposed: Comprehensive Documentation for V-Sekai\n\n\n2 min\n\n\n20240217-documentation-guidelines.md\n\n\n\n\nProposed: Container2Wasm Integration in V-Sekai\n\n\n2 min\n\n\n20240217-container-2-wasm.md\n\n\n\n\nProposed: Enhancing Avatar Expressiveness with AI-Generated Blend Shapes\n\n\n2 min\n\n\n20240215-avatar-customization-with-ai-facial-expressions.md\n\n\n\n\nProposed: Urban Navigator: The City Unveiled\n\n\n2 min\n\n\n20240127-urban-explorer-gdc-2024-sample.md\n\n\n\n\nProposed: Macos cicd setup.\n\n\n4 min\n\n\n20240121-mac-setup.md\n\n\n\n\nProposed: Elixir Livebook on Fedora 39\n\n\n3 min\n\n\n20240121-livebook-fedora-install.md\n\n\n\n\nProposed: Installing Tailscale on Linux Fedora 39\n\n\n2 min\n\n\n20240121-install-tailscale.md\n\n\n\n\nProposed: Easy Diffusion AI Setup on Linux Systems\n\n\n2 min\n\n\n20240121-easy-diffusion-fedora-install.md\n\n\n\n\nProposed: Advanced VR Armature System for V-Sekai\n\n\n2 min\n\n\n20240120-vr-armature-system.md\n\n\n\n\nProposed: Provide Pivot Painting Resources\n\n\n1 min\n\n\n20240117-pivot-painting.md\n\n\n\n\nProposed: Camera matching with fSpy.\n\n\n2 min\n\n\n20240111-fspy.md\n\n\n\n\nDraft: Fit Clothing on Humans Without Tearing\n\n\n2 min\n\n\n20240111-fit-clothing-on-humans-without-tearing.md\n\n\n\n\nProposed: Magical Girls College Manager Simulator\n\n\n3 min\n\n\n20240110-magical-girls-college-novel.md\n\n\n\n\nProposed: 1 Meter Cubed 128 Quantized\n\n\n2 min\n\n\n20240105-1-meter-128-quantize.md\n\n\n\n\nDeprecated: Valid configuration of Spatiallabs and Openxr\n\n\n2 min\n\n\n20231230-spatiallabs-openvr.md\n\n\n\n\nProposed: Choosing a terminal emulator for Windows\n\n\n2 min\n\n\n20231229-mRemoteNG.md\n\n\n\n\nProposed: Byobu terminal multiplexer\n\n\n2 min\n\n\n20231229-byobu.md\n\n\n\n\nProposed: V-Sekai: Gateways to Virtual Worlds\n\n\n2 min\n\n\n20231228-v-sekai-slogan.md\n\n\n\n\nProposed: Use the “Punchline Reports” Method\n\n\n2 min\n\n\n20231227-punchline-reports.md\n\n\n\n\nProposed: Blue Green new shadows for new avatars\n\n\n2 min\n\n\n20231227-blue-green-shadows.md\n\n\n\n\nProposed: Hardsurface vs Organic\n\n\n2 min\n\n\n20231226-furniture-vs-organic.md\n\n\n\n\nProposed: Mesh Transformer Expressive Facial Features\n\n\n2 min\n\n\n20231225-mesh-transformer-facial-features.md\n\n\n\n\nProposed: Mesh Transformer Clothing\n\n\n2 min\n\n\n20231225-mesh-transformer-clothing.md\n\n\n\n\nProposed: MaterialX try two.\n\n\n2 min\n\n\n20231218-mtlx-try-two.md\n\n\n\n\nProposed: Automating Game Testing Process Using Appium 2\n\n\n3 min\n\n\n20231209-appium-testing-win11.md\n\n\n\n\nProposed: Appium Testing for Windows 11\n\n\n2 min\n\n\n20231209-appium-testing-fbx-to-gltf.md\n\n\n\n\nProposed: Triangle Meshes Inferencing with MeshRWKV\n\n\n5 min\n\n\n20231203-mesh-rwkv.md\n\n\n\n\nDraft: Initial Training of the MeshRWVK Model\n\n\n2 min\n\n\n20231203-mesh-rwkv-test-metrics.md\n\n\n\n\nDraft: GraphSAGE Embedding Algorithm Explanation\n\n\n4 min\n\n\n20231203-graphsage-embedding-generation.md\n\n\n\n\nProposed: Seamless Integration of XR Tracking in Godot Engine\n\n\n3 min\n\n\n20231201-xr-hands-animation-node.md\n\n\n\n\nProposed: Headless Launcher Backend with Elixir and Server-Side CockroachDB\n\n\n7 min\n\n\n20231201-headless-launcher-backend.md\n\n\n\n\nAccepted: Benchmarking Network Performance for Scalable Multiplayer in Godot\n\n\n3 min\n\n\n20231127-performance-test.md\n\n\n\n\nAccepted: V-Sekai 2023-11-26 Report\n\n\n3 min\n\n\n20231126-v-sekai-report.md\n\n\n\n\nSuperseded: V-Sekai 2023-11-25 Report\n\n\n4 min\n\n\n20231125-v-sekai-report.md\n\n\n\n\nProposed: Upload Creative Commons FBX Test Files for Enhanced LOD Optimization in V-Sekai\n\n\n2 min\n\n\n20231114-upload-creative-commons-fbx-test-files.md\n\n\n\n\nProposed: Enhancing VR Book Reading through SVG Optimization\n\n\n2 min\n\n\n20231114-maintain-svgcleaner.md\n\n\n\n\nProposed: Defining the List of Godot Types in Elixir Godot Parsers\n\n\n2 min\n\n\n20231114-elixir-definition-of-godot-types.md\n\n\n\n\nProposed: Validator Service for V-Sekai\n\n\n2 min\n\n\n20231112-validation-service.md\n\n\n\n\nProposed: Effective V-Sekai project archival strategy\n\n\n3 min\n\n\n20231112-archive-projects.md\n\n\n\n\nProposed: Evaluate AYON pipeline platform on hosted cloud services\n\n\n3 min\n\n\n20231111-ayon-evaluation.md\n\n\n\n\nAccepted: V-Sekai dependencies\n\n\n3 min\n\n\n20231110-v-sekai-dependencies.md\n\n\n\n\nProposed: Efficient Training of LLMs in V-Sekai\n\n\n2 min\n\n\n20231110-efficient-llm-training.md\n\n\n\n\nAccepted: Overcoming the Blender T-Pose Limitation with Documentation\n\n\n2 min\n\n\n20231110-blender-manual-t-pose.md\n\n\n\n\nProposed: Enhancing V-Sekai x Godot Engine x AYON for a Superior Workflow\n\n\n2 min\n\n\n20231110-better-pipeline-tools.md\n\n\n\n\nProposed: Streamlining Game Development with AI-Based Aria’s Guidance\n\n\n2 min\n\n\n20231110-ai-based-outlier-detection.md\n\n\n\n\nProposed: Character Customization Discord Bot PoC for V-Sekai\n\n\n4 min\n\n\n20231109-discord-polygonjs-generator.md\n\n\n\n\nProposed: Creation of an ‘Ask V-Sekai’ Chatbot Using Vercel, OpenAI, and Neon PostgreSQL\n\n\n2 min\n\n\n20231108-v-sekai-chat-bot.md\n\n\n\n\nProposed: PostgreSQL bytea Storage Optimization for V-Sekai’s Edge CDN\n\n\n2 min\n\n\n20231108-postgres-bytea-optimizations.md\n\n\n\n\nProposed: “Freedom is in a future that you did not have in the past” - A Game Development Philosophy from NieR:Automata\n\n\n3 min\n\n\n20231108-nier-automata-world-expansion.md\n\n\n\n\nProposed: Development of a Community Polling Discord Bot Using Vercel and Neon PostgreSQL\n\n\n2 min\n\n\n20231108-neon-vercel-functions-toy-problem.md\n\n\n\n\nProposed: Adopting Neon for a More Manageable Backend at V-Sekai\n\n\n1 min\n\n\n20231108-neon-postgresql.md\n\n\n\n\nProposed: Adopting Neon’s Bottomless Storage with S3-Compatible Object Store for Edge CDN Data Management\n\n\n2 min\n\n\n20231108-neon-1-gb-scene-storage.md\n\n\n\n\nProposed: Enhancing V-Sekai Through Effective Documentation\n\n\n2 min\n\n\n20231108-munich-godot-engine-conference.md\n\n\n\n\nProposed: Ansible Server Provisioning\n\n\n2 min\n\n\n20231108-ansible-new-server-provisioning.md\n\n\n\n\nProposed: PDF to SVG Conversion for VR Books\n\n\n2 min\n\n\n20231105-pdf-embed-raster-svg-vr.md\n\n\n\n\nRejected: Merge Scene Tool for Godot Editor with FlatBuffer-based JSON Serialization\n\n\n2 min\n\n\n20231104-flatbuffer_packed_scenes.md\n\n\n\n\nAccepted: Write List of Github Pull Requests for Review\n\n\n6 min\n\n\n20231027-write-a-list-of-github-pull-requests.md\n\n\n\n\nProposed: DreamCraft3D - A Hierarchical 3D Content Generation Method\n\n\n2 min\n\n\n20231027-dreamcraft3d-workflow.md\n\n\n\n\nProposed: Drawing Concept to Blockout\n\n\n2 min\n\n\n20231027-drawing-concept-to-blockout.md\n\n\n\n\nProposed: Build a Cozy Apartment in VR for V-Sekai\n\n\n2 min\n\n\n20231027-apartment-building-vr.md\n\n\n\n\nProposed: Solve Blender versions by locking LTS versions on Blender (3.6)\n\n\n1 min\n\n\n20231026-blender-steam-beta-version.md\n\n\n\n\nProposed: Implementing Advanced Training Simulators in V-Sekai\n\n\n2 min\n\n\n20231024-training-simulators.md\n\n\n\n\nProposed: Enhancing Task-Specific Model Performance through Fine-Tuning with Axolotl\n\n\n2 min\n\n\n20231024-finetuning-workflow.md\n\n\n\n\nProposed: Navigating New Horizons: A Proposal for Expanding Exploration in V-Sekai\n\n\n2 min\n\n\n20231022-hover-to-ocean-game.md\n\n\n\n\nProposed: Llama CPP AI Model NPC\n\n\n2 min\n\n\n20231020-llama-cpp-mistral-npc.md\n\n\n\n\nProposed: Valve VR Ecosystem with Quest 3\n\n\n2 min\n\n\n20231019-quest3-mocap-steam-lighthouse.md\n\n\n\n\nProposed: Streamlining V-Sekai Performance\n\n\n2 min\n\n\n20230922-spacetime-shadow-shards-sync.md\n\n\n\n\nProposed: Use embedding search with Godot Engine projects\n\n\n2 min\n\n\n20230920-godot-project-search.md\n\n\n\n\nProposed: Challenges that need to be addressed in V-Sekai\n\n\n2 min\n\n\n20230913-V-Sekai-bugs.md\n\n\n\n\nProposed: Address Screen Resolution Compatibility Issues\n\n\n1 min\n\n\n20230912-target-most-popular-resolution.md\n\n\n\n\nProposed: Improving xr grid with new enhancements\n\n\n1 min\n\n\n20230911-xr-grid-with-drawing.md\n\n\n\n\nDraft: XPR in Elixir\n\n\n3 min\n\n\n20230911-xpr.exs.md\n\n\n\n\nProposed: Implementing Semantic Versioning for Alpha Releases in V-Sekai\n\n\n2 min\n\n\n20230911-first-alpha-tag.md\n\n\n\n\nDraft: Can Poly Green Coords extend to 3d?\n\n\n1 min\n\n\n20230911-can-poly-green-coords-extend-to-3d.md\n\n\n\n\nDraft: Translation/Transcription Badge with GGML’s Whisper\n\n\n3 min\n\n\n20230908-bendable-screen-generative-assistant-ggml.md\n\n\n\n\nRejected: Enabling VRM to Blender Conversion with Cloud GPUs and replicate.com\n\n\n3 min\n\n\n20230903-replicate-vrm-transform.md\n\n\n\n\nAccepted: Enhancing Map Uploads\n\n\n2 min\n\n\n20230831-fixing-upload-limits.md\n\n\n\n\nAccepted: Fix menus in-game\n\n\n1 min\n\n\n20230831-fixing-menus.md\n\n\n\n\nProposed: Expanding Worlds\n\n\n4 min\n\n\n20230830-generating-v-sekai-worlds.md\n\n\n\n\nProposed: Improving VR Experience\n\n\n2 min\n\n\n20230830-better-object-pick.md\n\n\n\n\nProposed: Integrating Backend Services\n\n\n2 min\n\n\n20230830-better-backend-services.md\n\n\n\n\nProposed: OMIFest 2023 - The Call\n\n\n5 min\n\n\n20230829-omifest-2023.md\n\n\n\n\nAccepted: Use opensubdiv for level of detail\n\n\n2 min\n\n\n20230824-subdiv-for-lods.md\n\n\n\n\nProposed: Developing a Unified Model for Speech-to-Facial Shape Generation Using Outlines 〰 Library\n\n\n4 min\n\n\n20230823-speech-to-blendshapes.md\n\n\n\n\nProposed: Following Tracks: Enhancing VR Train Station Simulation in V-Sekai using Godot Engine\n\n\n2 min\n\n\n20230819-train-game.md\n\n\n\n\nRejected: Rewriting Mixer Broadcaster Into Membrane Framework Pipelines\n\n\n3 min\n\n\n20230813-mixer-broadcaster-into-membrane-framework copy.md\n\n\n\n\nProposed: Transitioning to Membrane Framework Pipelines with JSON-RPC Blender Runner\n\n\n5 min\n\n\n20230813-blender-runner-into-membrane-framework.md\n\n\n\n\nProposed: Update V-Sekai game engine procedure\n\n\n2 min\n\n\n20230812-vsekai-update-process.md\n\n\n\n\nProposed: Procedure to unmerge and then merge solves a V-Sekai source code broken tree\n\n\n2 min\n\n\n20230812-unmerge-and-merge-procedure-source-code-tree.md\n\n\n\n\nProposed: Configuring GoCD Agents in V-Sekai\n\n\n3 min\n\n\n20230812-gocd-agent-setup.md\n\n\n\n\nProposed: Constrain the entire Godot Humanoid Skeleton\n\n\n2 min\n\n\n20230812-constraint-all-bones.md\n\n\n\n\nAccepted: Punchline based reports\n\n\n3 min\n\n\n20230811-punchline-reports.md\n\n\n\n\nProposed: V-Sekai Navigation Compatibility with VR\n\n\n2 min\n\n\n20230806-v-sekai-ipad-projection-compatibility.md\n\n\n\n\nProposed: Sonic Symphony: Crafting Melodies with Machine Intelligence\n\n\n3 min\n\n\n20230806-music-gen.md\n\n\n\n\nProposed: Dokku for V-Sekai URO Backend Services Hosting and Development\n\n\n2 min\n\n\n20230804-dokku.md\n\n\n\n\nAccepted: Git Subrepo Addon Management\n\n\n2 min\n\n\n20230803-subrepo-addon-management.md\n\n\n\n\nAccepted: Completing VRM 1.0 Support and Publishing to Godot Engine Asset Library\n\n\n2 min\n\n\n20230803-publish-vrm-to-assetlibrary.md\n\n\n\n\nProposed: Port Godot Jolt from GDExtension to C++ Module\n\n\n2 min\n\n\n20230803-jolt-gextension-to-module.md\n\n\n\n\nProposed: Social RPG World Proposal\n\n\n2 min\n\n\n20230803-idle-rpg-home.md\n\n\n\n\nProposed: Solve Renik directly rather than through many bone ik\n\n\n2 min\n\n\n20230726-solve-renik-directly-rather-than-many-bone-ik.md\n\n\n\n\nProposed: Enhancing the Many Bone IK Configuration\n\n\n3 min\n\n\n20230719-pose-kusudama-constraints-in-vr.md\n\n\n\n\nProposed: Game simulation server sidekick process\n\n\n2 min\n\n\n20230719-dual-databases-cockroachdb-khepri.md\n\n\n\n\nProposed: Enhancing Avatar Creation Process in V-Sekai Advanced\n\n\n4 min\n\n\n20230716-enhancing-avatar-creation-process-02-advanced.md\n\n\n\n\nProposed: Enhancing Avatar Creation Process in V-Sekai Regular\n\n\n5 min\n\n\n20230716-enhancing-avatar-creation-process-01-regular.md\n\n\n\n\nProposed: V-Sekai Feature Enhancement Proposal\n\n\n6 min\n\n\n20230701-vsekai-broken-down-goals.md\n\n\n\n\nAccepted: V-Sekai Meeting - Friday, June 30, 2023\n\n\n2 min\n\n\n20230630-vsekai-goal-meeting.md\n\n\n\n\nProposed: Ship Godot Engine VRM1 to solve portable humanoid avatars\n\n\n3 min\n\n\n20230626-godot-vrm1-addon.md\n\n\n\n\nAccepted: V-Sekai Roadmap and Goals 2023-06-24\n\n\n2 min\n\n\n20230624-v-sekai-roadmap.md\n\n\n\n\nProposed: Implementing Feedback Delay Networks for Enhanced Audio Reverb Simulation in V-Sekai\n\n\n8 min\n\n\n20230623-fdn-reverb-solution.md\n\n\n\n\nProposed: Large language model t5 generating xstate json reliabily for digital beings\n\n\n5 min\n\n\n20230620-t5-jsonformer-xstate.md\n\n\n\n\nProposed: A Potential Solution for V-Sekai’s Identifier Assignment Challenge\n\n\n2 min\n\n\n20230620-doi-github.md\n\n\n\n\nRejected: V-Sekai Database Solution for 50,000 Concurrent Online Users\n\n\n2 min\n\n\n20230619-move-cockroachdb-to-yugabyte.md\n\n\n\n\nProposed: Networked Procedural Generation as a Sidecar to the Godot Engine Server\n\n\n3 min\n\n\n20230619-membrane-framework-for-mesh-processing.md\n\n\n\n\nAccepted: V-Sekai Roadmap and Goals 2023-06-18\n\n\n3 min\n\n\n20230618-v-sekai-roadmap.md\n\n\n\n\nProposed: V-Sekai Bone Hierarchy Conversion\n\n\n2 min\n\n\n20230616-pmx-to-vrm.md\n\n\n\n\nProposed: Increase variety and quality with generated animation trees\n\n\n2 min\n\n\n20230614-llm-statechart.md\n\n\n\n\nProposed: Wasm in V-Sekai Proposal\n\n\n5 min\n\n\n20230611-wasm-in-v-sekai.md\n\n\n\n\nSuperseded: V-Sekai Roadmap and Goals 2023-06-08\n\n\n2 min\n\n\n20230608-v-sekai-roadmap.md\n\n\n\n\nSuperseded: V-Sekai Roadmap and Goals 2023-06-02\n\n\n2 min\n\n\n20230602-v-sekai-roadmap.md\n\n\n\n\nProposed: Pmx module integration\n\n\n3 min\n\n\n20230602-pmx-module-integration.md\n\n\n\n\nProposed: Capturing accurate body movements with limited tracker placement\n\n\n4 min\n\n\n20230602-limited-tracker-placement.md\n\n\n\n\nProposed: Propose a solution to improve V-Sekai contributors’ design skills for navigating 3D environments\n\n\n2 min\n\n\n20230531-godot-engine-learning.md\n\n\n\n\nProposed: Build a Single-Instance MacOS Editor for the iPad\n\n\n3 min\n\n\n20230531-godot-engine-ipad.md\n\n\n\n\nSuperseded: V-Sekai Roadmap and Goals 2023-05-19\n\n\n2 min\n\n\n20230527-v-sekai-roadmap.md\n\n\n\n\nProposed: Efficiently managing and synchronizing game data with a server sidecar\n\n\n3 min\n\n\n20230527-server-sidecar.md\n\n\n\n\nProposed: Implement server-side content validation export followed by a sanitization service and CDN support\n\n\n2 min\n\n\n20230527-server-side-content-validation.md\n\n\n\n\nProposed: Generating Random Text Data for testing V-Sekai systems\n\n\n3 min\n\n\n20230527-server-performance-test.md\n\n\n\n\nProposed: Handling access to session based game data\n\n\n2 min\n\n\n20230527-server-cdn-session-url.md\n\n\n\n\nDraft: Finding ways to attract users, developers, and creators sustaining V-Sekai\n\n\n2 min\n\n\n20230527-organization.md\n\n\n\n\nProposed: Create a 12x12 meter 3D demo map with 2-meter-high obstacles and walls\n\n\n1 min\n\n\n20230527-godot-test-game.md\n\n\n\n\nProposed: Convert IK solvers to be using the AnimationTree\n\n\n3 min\n\n\n20230525-animation-ik-node.md\n\n\n\n\nDraft: Improve V-Sekai marketing\n\n\n2 min\n\n\n20230523-marketing-cycle.md\n\n\n\n\nRejected: Defeating your fictional enemies in their blood\n\n\n1 min\n\n\n20230522-JOKE-fictional-blood-combat.md\n\n\n\n\nProposed: Improving Jitter-Buffer Implementation for Voice Chat in V-Sekai Projects\n\n\n2 min\n\n\n20230521-audio-jitter-buffer-voip.md\n\n\n\n\nSuperseded: V-Sekai Roadmap and Goals 2023-05-19\n\n\n2 min\n\n\n20230519-v-sekai-roadmap.md\n\n\n\n\nProposed: Add VRM portable avatars and OMI_personality to the GLTF Transform tool\n\n\n3 min\n\n\n20230519-add-vrm-omi-personality-gltf-extension.md\n\n\n\n\nSuperseded: V-Sekai Roadmap and Goals 2023-05-16\n\n\n2 min\n\n\n20230516-v-sekai-roadmap.md\n\n\n\n\nAccepted: Aquarium Nightclub Booth for Virtual Market Exhibition\n\n\n2 min\n\n\n20230516-create-an-aquarium-nightclub-booth-for-virtual-market.md\n\n\n\n\nRejected: Additional 3D Import Functionality\n\n\n3 min\n\n\n20230516-additional-3d-import.md\n\n\n\n\nDraft: Exchange data between Godot Engine and WASM using handles\n\n\n2 min\n\n\n20230509-wasm-data-exchange.md\n\n\n\n\nDraft: Convert segmented front facing 3D Garment images to novel 3d views for 3d modeling\n\n\n2 min\n\n\n20230508-novel-3d-views.md\n\n\n\n\nRejected: Using Deno to handle the conversion of GLB files to Godot Engine packed scenes\n\n\n2 min\n\n\n20230507-supabase.md\n\n\n\n\nRejected: Distributed simulation\n\n\n17 min\n\n\n20230507-distributed-sim.md\n\n\n\n\nDraft: Describe a avatar publishing workflow for portability\n\n\n2 min\n\n\n20230507-avatar-publishing-workflow-portability.md\n\n\n\n\nSuperseded: Solve V-Sekai limitations using ChatGPT-4 AI completion.\n\n\n3 min\n\n\n20230505-v-sekai-ai-completion.md\n\n\n\n\nProposed: VR design application for V-Sekai\n\n\n2 min\n\n\n20230505-polygon-mesh-based-sculpting-tools.md\n\n\n\n\nProposed: Enhancing Cross-Platform Compatibility and User Experience for V-Sekai VR Social Players\n\n\n2 min\n\n\n20230505-cross-platform-artwork-distribution.md\n\n\n\n\nProposed: Solve a V-Sekai naming convention limitation.\n\n\n3 min\n\n\n20230505-consistent-v-sekai-naming.md\n\n\n\n\nProposed: Automated avatar garment rigging\n\n\n4 min\n\n\n20230505-automated-avatar-garment-rigging.md\n\n\n\n\nAccepted: Adding IREE to Godot Engine for Image Superresolution\n\n\n3 min\n\n\n20230502-add-iree-to-godot-engine-for-image-superresolution.md\n\n\n\n\nSuperseded: V-Sekai Roadmap and Goals 2023-04-20\n\n\n3 min\n\n\n20230429-v-sekai-roadmap.md\n\n\n\n\nProposed: Improve the collaboration process and attract more contributors to work on the project\n\n\n3 min\n\n\n20230429-improve-collab.md\n\n\n\n\nAccepted: Challenges in managing and synchronizing multiple assets and libraries across different git repositories\n\n\n2 min\n\n\n20230429-git-subrepo-challenges.md\n\n\n\n\nRejected: Package Godot for pkgin\n\n\n5 min\n\n\n20230419-package-godot-for-pkgin.md\n\n\n\n\nProposed: Capturing accurate body movements with limited tracker placement\n\n\n4 min\n\n\n20230419-limited-tracker-placement.md\n\n\n\n\nProposed: Use godot rgbaf textures to store integers\n\n\n3 min\n\n\n20230415-rgbaf-to-store-integers.md\n\n\n\n\nProposed: Procedurally create variations for our props, environments and avatars\n\n\n3 min\n\n\n20230415-procedural-variations-props-envs-avatars.md\n\n\n\n\nProposed: Hit a collaborate button to load up into V-Sekai\n\n\n2 min\n\n\n20230415-load-collaborate.md\n\n\n\n\nProposed: Provide v-sekai-game in a launcher to make it easier to use v-sekai\n\n\n1 min\n\n\n20230408-v-sekai-launcher.md\n\n\n\n\nProposed: Use junit xml based tests in github\n\n\n1 min\n\n\n20230310-xml-based-tests.md\n\n\n\n\nProposed: Don’t merge incomplete work.\n\n\n1 min\n\n\n20230310-don’t-merge-incomplete-work.md\n\n\n\n\nSuperseded: Creating a Godot Engine C++ module with IREE backend for machine learning computations using Vulkan and CUDA\n\n\n2 min\n\n\n20230310-IREE-backend-for-machine-learning-computations.md\n\n\n\n\nAccepted: Meet at GDC SF 2023\n\n\n2 min\n\n\n20230131-meeting-at-gdc-2023.md\n\n\n\n\nAccepted: Default test plan for testing V-Sekai engine upgrades.\n\n\n2 min\n\n\n20230131-default-test-plan.md\n\n\n\n\nProposed: Adopt best practices for product development\n\n\n2 min\n\n\n20230131-adopt-best-product-development-practices.md\n\n\n\n\nProposed: Without visualization, we cannot easily compare the interpolation states\n\n\n2 min\n\n\n20230125-without-viz-we-cannot-compare-the-interpolation.md\n\n\n\n\nProposed: Provide user generated scripting with libsql and wasm\n\n\n2 min\n\n\n20230125-user-generated-scripting-with-libsql-and-wasm.md\n\n\n\n\nProposed: Have two groups move towards each other battle demo\n\n\n2 min\n\n\n20230125-two-groups-battle-demo.md\n\n\n\n\nProposed: Provide metadata to pre-check if maps and avatars are compatible to load\n\n\n1 min\n\n\n20230125-provide-metadata-to-match-compatibile-maps-and-avatars.md\n\n\n\n\nProposed: Possible futures\n\n\n2 min\n\n\n20230125-possible-futures.md\n\n\n\n\nProposed: Grow the community with a reactive Discord bot.\n\n\n2 min\n\n\n20230125-grow-the-community-with-a-reactive-discord-bot.md\n\n\n\n\nProposed: Create an in-game tablet interface we can activate\n\n\n1 min\n\n\n20230125-create-an-in-game-tablet-interface-we-can-activate.md\n\n\n\n\nProposed: Cover 80% to 95% of the player base.\n\n\n1 min\n\n\n20230125-cover-80-95-percent-of-the-userbase.md\n\n\n\n\nProposed: Use Easy Charts for observability\n\n\n1 min\n\n\n20230123-use-easy-charts-for-observability.md\n\n\n\n\nProposed: Recording demo checklist\n\n\n2 min\n\n\n20230123-recording-demo-checklist.md\n\n\n\n\nProposed: Ready net demo\n\n\n2 min\n\n\n20230123-ready-the-net-demo.md\n\n\n\n\nProposed: Publish Godot VRM for Godot 4 for production use\n\n\n2 min\n\n\n20230123-publish-godot-vrm-4.md\n\n\n\n\nProposed: Provide user generated scripting using WasGO\n\n\n2 min\n\n\n20230123-player-scripting.md\n\n\n\n\nProposed: No traversal loading screen\n\n\n4 min\n\n\n20230123-no-traversal-loading-screen.md\n\n\n\n\nProposed: Better Godot Engine integration with Blender with gltf extensions\n\n\n2 min\n\n\n20230123-integrate-blender-with-gltf-extensions-and-godot.md\n\n\n\n\nProposed: Face helmet capture\n\n\n2 min\n\n\n20230123-face-helmet-capture.md\n\n\n\n\nProposed: Add WMF for windows media playback\n\n\n2 min\n\n\n20230108-wmf-video-playback.md\n\n\n\n\nAccepted: Bolster creating the metaverse\n\n\n3 min\n\n\n20230108-bolster-creating-the-metaverse.md\n\n\n\n\nAccepted: How to start a EXPERIMENTAL environment for sqlite and elixir?\n\n\n3 min\n\n\n20230107-elixir-uro-dev-sqlite.md\n\n\n\n\nAccepted: Separate walking controller from RenIK for ManyBoneIK\n\n\n2 min\n\n\n20230106-walking-controller-renik.md\n\n\n\n\nProposed: Powershell autocomplete uses right arrow\n\n\n2 min\n\n\n20221214-powershell-autocomplete-use-right-arrow.md\n\n\n\n\nProposed: Tools helpful for creating Avatars and Worlds\n\n\n3 min\n\n\n20221212-world-and-character-tools.md\n\n\n\n\nProposed: Prepare godot-vrm for asset library publishing\n\n\n4 min\n\n\n20221206-export-godot-vrm-to-the-asset-library.md\n\n\n\n\nProposed: Port RENIK to Many Bone IK for better quality\n\n\n2 min\n\n\n20221205-port-renik-to-many-bone-ik.md\n\n\n\n\nProposed: Move fast without breaking things for V-Sekai\n\n\n2 min\n\n\n20221205-moving-fast-philosophy-development.md\n\n\n\n\nProposed: Debug Linux Export\n\n\n3 min\n\n\n20221205-debug-linux-export.md\n\n\n\n\nProposed: Target 10 minutes cicd builds to improve our iterations\n\n\n2 min\n\n\n20221203-target-10-minutes-cicd.md\n\n\n\n\nRejected: Blocking direct push to MAIN to avoid build breakage\n\n\n2 min\n\n\n20221203-block-direct-pushes-to-main.md\n\n\n\n\nDraft: Simulate larger 3d multiplayer worlds using “brickworlds partition layout”\n\n\n5 min\n\n\n20221022-have-larger-worlds-by-server-state-migration.md\n\n\n\n\nProposed: Make it easier to propose and file bugs by simplifying the templates\n\n\n3 min\n\n\n20221021-make-it-easier-propose-and-post-bugs.md\n\n\n\n\nProposed: Replicate sync 100’000 entities using a solution (Revision 1)\n\n\n2 min\n\n\n20221019-replicate-sync-100-000-entities.md\n\n\n\n\nProposed: Networking with 100000 Entities and Ownership (Revision 2)\n\n\n4 min\n\n\n20221019-networking-100000-entities-ownership.md\n\n\n\n\nProposed: Replicate sync 100’000 entities using Godot Engine, mvsqlite and Foundationdb\n\n\n3 min\n\n\n20221019-develop-a-replication-sync-for-100-000-entities.md\n\n\n\n\nProposed: To remember how to update the engine and game write a procedure\n\n\n3 min\n\n\n20221018-v-sekai-game-update-procedure.md\n\n\n\n\nRejected: Use view replication algorithm for multiplayer multirelay sync\n\n\n9 min\n\n\n20221016-v-sekai-view-replication.md\n\n\n\n\nDraft: Networking Overhaul\n\n\n5 min\n\n\n20221014-networking-overhaul-proposal.md\n\n\n\n\nProposed: Unidot is optional\n\n\n2 min\n\n\n20221006-unidot-is-optional.md\n\n\n\n\nProposed: Rename master to godot3 and main to godot4\n\n\n2 min\n\n\n20221006-rename-to-main.md\n\n\n\n\nProposed: We have too many branches on V-Sekai/godot.\n\n\n2 min\n\n\n20220916-too-many-branches-on-v-sekai-godot.md\n\n\n\n\nProposed: Extended asset library packages in addition to the upstream asset library\n\n\n2 min\n\n\n20220901-mirror-extend-asset-library-packages.md\n\n\n\n\nProposed: Provide pdf reading\n\n\n2 min\n\n\n20220830-godot-pdf-workflow.md\n\n\n\n\nProposed: Make a market booth creation tutorial.\n\n\n2 min\n\n\n20220820-market-booth-tutorial.md\n\n\n\n\nProposed: Simulate cloth on characters\n\n\n2 min\n\n\n20220820-cloth-sim.md\n\n\n\n\nProposed: Bake alembic imports by running blender script.\n\n\n3 min\n\n\n20220820-bake alembic-anim-via-blender.md\n\n\n\n\nProposed: Connect Mediapipe to Blender\n\n\n3 min\n\n\n20220624-webcam-to-posed-characters.md\n\n\n\n\nProposed: Host a baserow application for internal use.\n\n\n3 min\n\n\n20220605-host-internal-baserow.md\n\n\n\n\nAccepted: To avoid git submodule but recreate the gocd pipelines\n\n\n2 min\n\n\n20220605-gocd-pipeline-reset.md\n\n\n\n\nProposed: Lightweight quality avatars\n\n\n3 min\n\n\n20220601-lightweight-quality-avatars.md\n\n\n\n\nRejected: To create a deployment kit use truescale to host gocd agents for cicd.\n\n\n2 min\n\n\n20220531-truenas-scale.md\n\n\n\n\nAccepted: How to start a development environment for cockroach and elixir?\n\n\n3 min\n\n\n20220531-elixir-uro-dev.md\n\n\n\n\nProposed: Profile using perf\n\n\n2 min\n\n\n20220515-profile-using-perf.md\n\n\n\n\nProposed: Merge retargeting feature into Godot Engine master\n\n\n4 min\n\n\n20220318-merge-retargeting-pr.md\n\n\n\n\nProposed: Use specular vec3 from gltf to show multicoloured metals\n\n\n2 min\n\n\n20220317-use-spec-rough-metal.md\n\n\n\n\nProposed: To protect the minimum spec maintain steam deck version of flatmode V-Sekai\n\n\n2 min\n\n\n20220317-protect-minumum-spec-steam-deck.md\n\n\n\n\nDraft: To provide an asset library prototype use baserow\n\n\n2 min\n\n\n20220317-baserow.io-truenas.md\n\n\n\n\nAccepted: Planning V-Sekai Version 3 on 2022-02-28\n\n\n3 min\n\n\n20220228-v-sekai-version-three-plan.md\n\n\n\n\nSuperseded: Planning V-Sekai Version 2 on 2022-02-24\n\n\n4 min\n\n\n20220224-v-sekai-version-two-plan.md\n\n\n\n\nRejected: Storing raw VSK_map files via DVC to avoid limitations\n\n\n3 min\n\n\n20220223-store-source-VSK_map-files-via-DVC.md\n\n\n\n\nAccepted: Rank skeleton #bone names with catboost\n\n\n4 min\n\n\n20220222-rank-skeleton-bone-names-with-catboost.md\n\n\n\n\nAccepted: Rank skeleton #bone names with xgboost\n\n\n3 min\n\n\n20220222-rank-bone-skeletons-with-xgboost.md\n\n\n\n\nAccepted: Rank skeleton #bone names with transformer4rec\n\n\n3 min\n\n\n20220222-rank-bone-names-with-transformer.md\n\n\n\n\nSuperseded: Planning V-Sekai on 2022-02-21 Superseded\n\n\n4 min\n\n\n20220222-know-where-we-re-going-by-planning-vsekai.md\n\n\n\n\nAccepted: To create omi chan rig a #256FES\n\n\n3 min\n\n\n20220217-omi-chan-oni-chan.md\n\n\n\n\nProposed: To deploy backend services like Uro safely use a defined process\n\n\n3 min\n\n\n20220215-uro-deployment-process.md\n\n\n\n\nAccepted: To make a virtual pet game given Jeana’s designs\n\n\n2 min\n\n\n20220207-virtual-pets.md\n\n\n\n\nProposed: Log change notifications using DiscordChatExporter\n\n\n2 min\n\n\n20220206-logging-notifications-from-discord.md\n\n\n\n\nAccepted: Allow cicd to pass by fixing spatial audio branch\n\n\n2 min\n\n\n20220205-cicd-to-pass by-fixing-spatial-audio-branch.md\n\n\n\n\nDraft: To have a default set of motions on a 3d character by creating a default animation set\n\n\n3 min\n\n\n20220203-create-default-animation-set.md\n\n\n\n\nAccepted: Interoperability between platforms using gltf extensions\n\n\n4 min\n\n\n20220202-gltf-extensions-for-interoperability.md\n\n\n\n\nRejected: To allow independent deployment run our own infrastructure\n\n\n4 min\n\n\n20220131-run-own-infrastructure.md\n\n\n\n\nAccepted: To have an alternative CICD use Github Actions.\n\n\n3 min\n\n\n20220131-github-actions-support.md\n\n\n\n\nProposed: Make a desktop version of Uro for ease of development.\n\n\n2 min\n\n\n20220131-elixir-desktop-uro.md\n\n\n\n\nAccepted: To record decisions write a proposal.\n\n\n4 min\n\n\n20220130-to-record-decisions-write-a-proposal.md\n\n\n\n\nProposal: Optimize cicd for costs because it’s limited\n\n\n2 min\n\n\n20220130-optimize-cicd.md\n\n\n\n\nAccepted: To make it easier to upload V-Sekai maps and Avatars use Godot Engine 4 script templates.\n\n\n2 min\n\n\n20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.md\n\n\n\n\nAccepted: Convert gltf to a scene with AudioStreamPlayer3D, convert AudiostreamPlayer3D to gltf and expose usability.\n\n\n2 min\n\n\n20220118-convert-gltf-to-a-scene.md\n\n\n\n\nProposal: Change transform by CRDT.\n\n\n2 min\n\n\n20220113-change-transform-by-crdt.md\n\n\n\n\nProposal: Bake blend shapes to skeletons for performance\n\n\n3 min\n\n\n20220108-bake-blend-shapes-to-skeletons-for-performance.md\n\n\n\n\nProposal: Stream a character from a webcam to the vmc protocol\n\n\n2 min\n\n\n20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.md\n\n\n\n\nAccepted: Run meetings using Lean Coffee\n\n\n3 min\n\n\n20211229-run-meetings-using-lean-coffee.md\n\n\n\n\nRejected: Network the Ubisoft Mixer server\n\n\n2 min\n\n\n20211220-network-the-ubisoft-mixer-server.md\n\n\n\n\nAccepted: Create an open metaverse by working on V-Sekai\n\n\n4 min\n\n\n20211214-create-an-open-metaverse-by-working-on-v-sekai.md\n\n\n\n\nRejected: Create Steamdeck hardware proxy by installing Fedora Silverblue and #steam\n\n\n2 min\n\n\n20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.md\n\n\n\n\nRejected: Create Steamdeck hardware proxy by installing Fedora Kinoite and #steam\n\n\n2 min\n\n\n20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.md\n\n\n\n\nAccepted: For Godot Engine changes use a decision flowchart\n\n\n3 min\n\n\n20211207-for-godot-engine-changes-use-a-decision-flowchart.md\n\n\n\n\nAccepted: Create an upstream pull request for all non-V-Sekai related patches\n\n\n2 min\n\n\n20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.md\n\n\n\n\nAccepted: Avoid avatar breaking by following quality checklist\n\n\n3 min\n\n\n20211130-avoid-avatar-breaking-by-following-quality-checklist.md\n\n\n\n\nAccepted: Create a Godot Engine asset store service on elixir and on sqlite.\n\n\n3 min\n\n\n20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.md\n\n\n\n\nAccepted: Stabilize Godot Engine updates by delaying to 2 week cycles\n\n\n2 min\n\n\n20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.md\n\n\n\n\nProposed: Allow Godot Asset Library browser to use alternative sources\n\n\n2 min\n\n\n20211117-allow-godot-asset-library-browser-to-use-alternative-sources.md\n\n\n\n\nProposed: Learn how to scale V-Sekai using bots and multipliers\n\n\n2 min\n\n\n20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.md\n\n\n\n\nRejected: File or attestation for virtual worlds using ssh signatures\n\n\n3 min\n\n\n20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.md\n\n\n\n\nAccepted: Degrade V-Sekai’s networking model to work in 2d and with webrtc.\n\n\n2 min\n\n\n20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.md\n\n\n\n\nDraft: Create a VRM character by experimenting with written workflows.\n\n\n2 min\n\n\n20211109-create-a-vrm-character-by-experimenting-with-written-workflows.md\n\n\n\n\nProposed: Polish demo of V-Sekai by making invisible meshes appear via the use of the exporter.\n\n\n2 min\n\n\n20211108-invisible-meshes-appear-via-the-use-of-the-exporter.md\n\n\n\n\nProposed: Integrate with blender\n\n\n2 min\n\n\n20211108-integrate-with-blender.md\n\n\n\n\nDraft: Preview #materialx materials on the Web in Godot Engine\n\n\n2 min\n\n\n20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.md\n\n\n\n\nDraft: Use single player WebXR in Godot Engine to prototype CASSIE.\n\n\n2 min\n\n\n20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.md\n\n\n\n\nAccepted: Take a list of 3D points that form a vaguely closed boundary in space and triangulate in Godot Engine\n\n\n3 min\n\n\n20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.md\n\n\n\n\nRejected: Iterate faster on WasGo prototype by using Godot 3.4\n\n\n2 min\n\n\n20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.md\n\n\n\n\nRejected: Have an WebXR version of V-Sekai that is more accessible\n\n\n2 min\n\n\n20211105-have-an-webxr-version-of-v-sekai.md\n\n\n\n\nDraft: Research mesh tooling with nglod\n\n\n2 min\n\n\n20211104-research-mesh-tooling-with-nglod.md\n\n\n\n\nDraft: Research mesh tooling with kaolin\n\n\n3 min\n\n\n20211104-research-mesh-tooling-with-kaolin.md\n\n\n\n\nDraft: Use a standard reference platform called VFX Reference platform\n\n\n3 min\n\n\n20211103-use-platform-called-vfx-reference-platform.md\n\n\n\n\nAccepted: VOIP\n\n\n2 min\n\n\n20211031-voip.md\n\n\n\n\nDraft: VMD on VRM AnimationTree Node\n\n\n3 min\n\n\n20211031-vmd-on-vrm-animationtree-node.md\n\n\n\n\nDraft: Verification tools\n\n\n2 min\n\n\n20211031-verification-tools.md\n\n\n\n\nAccepted: Use our custom fullbody IK\n\n\n2 min\n\n\n20211031-use-our-custom-fullbody-ik.md\n\n\n\n\nProposed: Rank skeleton bone names by using BPR\n\n\n2 min\n\n\n20211031-use-bpr-to-rank-skeleton-bone-names.md\n\n\n\n\nProposed: Update URO for Godot 4\n\n\n2 min\n\n\n20211031-update-uro-for-godot-4.md\n\n\n\n\nProposed: Tire model car sim\n\n\n2 min\n\n\n20211031-tire-model-car-sim.md\n\n\n\n\nAccepted: ThorVG\n\n\n2 min\n\n\n20211031-thorvg.md\n\n\n\n\nProposed: Take a streaming godot game and streaming the VRM to OpenSoundControl\n\n\n2 min\n\n\n20211031-streaming-godot-to-opensoundcontrol.md\n\n\n\n\nProposed: Stream shader motion\n\n\n2 min\n\n\n20211031-stream-shader-motion.md\n\n\n\n\nProposed: Standard backup procedures\n\n\n2 min\n\n\n20211031-standard-backup-procedures.md\n\n\n\n\nProposed: To provide a performance and portable script use WasGo\n\n\n2 min\n\n\n20211031-script-as-a-binary.md\n\n\n\n\nProposed: Run the maintenance scripts from Windows in Unix mode with msys2\n\n\n2 min\n\n\n20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.md\n\n\n\n\nSuperseded: Play preprocessed #animation on any VRM model\n\n\n2 min\n\n\n20211031-play-preprocessed-animations-on-any-vrm-model.md\n\n\n\n\nProposed: Plausible npc behavior\n\n\n2 min\n\n\n20211031-plausable-npc-behaviour.md\n\n\n\n\nProposed: Phase out groups in the branding to make it more recognizable\n\n\n2 min\n\n\n20211031-phase-out-groups-terminology-for-vskdefault.md\n\n\n\n\nRejected: OpenVR for Godot Engine\n\n\n2 min\n\n\n20211031-openvr-for-godot-engine.md\n\n\n\n\nProposed: Membrane Framework streaming Mixer\n\n\n2 min\n\n\n20211031-membrane-framework-streaming-mixer.md\n\n\n\n\nProposed: Meeting area\n\n\n2 min\n\n\n20211031-meeting-area.md\n\n\n\n\nProposed: Make a place to record\n\n\n2 min\n\n\n20211031-make-a-place-to-record.md\n\n\n\n\nAccepted: Keep a changelog\n\n\n2 min\n\n\n20211031-keep-a-changelog.md\n\n\n\n\nProposed: How to make a V-Sekai/godot update?\n\n\n2 min\n\n\n20211031-how-to-make-a-v-sekaigodot-update.md\n\n\n\n\nProposed: Have wires in 3d\n\n\n2 min\n\n\n20211031-have-wires-in-3d.md\n\n\n\n\nProposed: Have better user developer experience\n\n\n2 min\n\n\n20211031-have-better-user-developer-experience.md\n\n\n\n\nProposed: Godot Database viewer for proposals\n\n\n3 min\n\n\n20211031-godot-database-viewer-for-proposals.md\n\n\n\n\nProposed: glTF - importer should bind animation players to the closest root node\n\n\n2 min\n\n\n20211031-gltf-importer-should-bind-animation-players-to-the-closest-root-node.md\n\n\n\n\nProposed: Face motion tracking requires standard shapes\n\n\n2 min\n\n\n20211031-face-motion-tracking-requires-standard-shapes.md\n\n\n\n\nProposed: Extract proposals into proposals\n\n\n23 min\n\n\n20211031-extract-proposals-into-proposals.md\n\n\n\n\nProposed: Export / Import testing via robot-framework and swiftshader\n\n\n2 min\n\n\n20211031-export-import-testing-via-robot-framework-and-swiftshader.md\n\n\n\n\nProposed: Create a demo viewer gallery\n\n\n3 min\n\n\n20211031-create-a-demo-viewer-gallery.md\n\n\n\n\nProposed: Construct the virtual #world\n\n\n2 min\n\n\n20211031-construct-the-virtual-world.md\n\n\n\n\nProposed: Client and Mast\n\n\n2 min\n\n\n20211031-client-and-mast.md\n\n\n\n\nProposed: CICD Export V-Sekai\n\n\n2 min\n\n\n20211031-cicd-export-v-sekai.md\n\n\n\n\nProposed: Character workshop\n\n\n2 min\n\n\n20211031-character-workshop.md\n\n\n\n\nProposed: Benchmark #animation playback\n\n\n2 min\n\n\n20211031-benchmark-animation-playback.md\n\n\n\n\nProposed: Bake blend shape to skeleton animation\n\n\n2 min\n\n\n20211031-bake-blend-shape-to-skeleton-animation.md\n\n\n\n\nProposed: Bake a #materialx into a custom Godot StandardMaterial3D\n\n\n2 min\n\n\n20211031-bake-a-materialx-into-a-custom-godot-standardmaterial3d.md\n\n\n\n\nProposed: ARC radial menu\n\n\n2 min\n\n\n20211031-arc-radial-menu.md\n\n\n\n\nProposed: 1000 player servers\n\n\n2 min\n\n\n20211031-1000-player-servers.md\n\n\n\n\nProposed: We want to proxy udp datagrams at production quality of service.\n\n\n2 min\n\n\n20211005-we-want-to-proxy-udp-datagrams-at-production-quality-of-service.md\n\n\n\n\nProposed: Want to use the same cluster for the same web and native.\n\n\n3 min\n\n\n20211005-want-to-use-the-same-cluster-for-the-same-web-and-native.md\n\n\n\n\nProposed: Summon #friend and acquaintances via presence to the current world.\n\n\n2 min\n\n\n20211005-want-to-summon-friends-and-acquaintances-via-presence.md\n\n\n\n\nProposed: Use materialx for asset interchange\n\n\n2 min\n\n\n20211005-use-materialx-for-asset-interchange.md\n\n\n\n\nProposed: Use KVM to test our AMD APU test computer via Barrier.\n\n\n2 min\n\n\n20211005-use-kvm-to-test-our-amd-apu-test-computer-via-barrier.md\n\n\n\n\nProposed: Test Google Mediapipe\n\n\n3 min\n\n\n20211005-test-google-mediapipe.md\n\n\n\n\nProposed: Solve Mocap By Connecting Mediapipe to Blender\n\n\n2 min\n\n\n20211005-solve-mocap-by-connecting-mediapipe-to-blender.md\n\n\n\n\nProposed: Improve Meshing Results by Subdivision in Godot Engine\n\n\n2 min\n\n\n20211005-improve-meshing-results-by-subdivision-in-godot-engine.md\n\n\n\n\nProposed: Create SOP for VRM #creation\n\n\n2 min\n\n\n20211005-create-sop-for-vrm-creation.md\n\n\n\n\nProposed: Create a standard procedure from adding spring bones to VRM models.\n\n\n2 min\n\n\n20211005-create-add-spring-bones-to-vrm-models.md\n\n\n\n\nProposed: Music is important to human experience and should be bridged to XR\n\n\n2 min\n\n\n20211005-bridge-music-to-xr.md\n\n\n\n\nProposed: Spoke to V-Sekai\n\n\n2 min\n\n\n20210811-spoke-to-v-sekai.md\n\n\n\n\nProposed: Soiree party mode\n\n\n3 min\n\n\n20210811-soiree-party.md\n\n\n\n\nProposed: OMI Glb Portable Content\n\n\n2 min\n\n\n20210811-omi-glb.md\n\n\n\n\nProposed: Neural Blend Shape Rigging\n\n\n3 min\n\n\n20210811-neural-blend-shape-rigging.md\n\n\n\n\nProposed: Import Minecraft worlds to Godot Engine\n\n\n2 min\n\n\n20210811-minecraft-voxel.md\n\n\n\n\nProposed: Minimum Specification V-Sekai Hardware\n\n\n3 min\n\n\n20210811-min-spec-v-sekai.md\n\n\n\n\nAccepted: OIT in Godot Engine\n\n\n2 min\n\n\n20210811-godot-transparency.md\n\n\n\n\nProposed: GLB data in a Movie\n\n\n2 min\n\n\n20210811-glb-in-video.md\n\n\n\n\nProposed: Membrane Framework to Process Game Workflows\n\n\n2 min\n\n\n20210811-game-workflow-membrane.md\n\n\n\n\nProposed: Godot Engine implementation of disconnected IPFS\n\n\n2 min\n\n\n20210811-disconnected-ipfs.md\n\n\n\n\nProposed: Spreadsheet Animation Preview\n\n\n4 min\n\n\n20210724-Spreadsheet-animation-preview.md\n\n\n\n\nProposed: Portable #world Content\n\n\n2 min\n\n\n20210715-portable-world-content.md\n\n\n\n\nProposed: Material Addon Blender\n\n\n2 min\n\n\n20210715-Material-Addon-Blender.md\n\n\n\n\nProposed: Describe a Godot Engine pr verification workflow\n\n\n2 min\n\n\n20210710-verify-pr-workflow.md\n\n\n\n\nProposed: Transfer animation by baking reset\n\n\n3 min\n\n\n20210707-transfer-animations-by-baking-reset.md\n\n\n\n\nProposed: Convert #shadermotion to be played in Godot Engine\n\n\n2 min\n\n\n20210622-shadermotion-to-godot-engine.md\n\n\n\n\nProposed: Convert FBX and glTF2 to VRM via flow-avatar-asset-pipeline\n\n\n2 min\n\n\n20210612-flow-avatar-asset-pipeline.md\n\n\n\n\nProposed: Store presentation and book content via Lottie\n\n\n3 min\n\n\n20210601-store-presentation-and-book-content-via-lottie-2.md\n\n\n\n\nProposed: Performance profile the game with AMDuProf\n\n\n2 min\n\n\n20210529-performance-profiling.md\n\n\n\n\nProposed: Trial install of Gravity for Kubernetes\n\n\n2 min\n\n\n20210528-trial-install-of-gravity-for-kubernetes.md\n\n\n\n\nProposed: Simplify Meshes and LODs better with Quads\n\n\n2 min\n\n\n20210523-simplfy-meshes-and-lods-better-with-quads.md\n\n\n\n\nProposed: Retarget VRM Motion Blender Workflow\n\n\n4 min\n\n\n20210523-retarget-motion-for-vrm-type-models.md\n\n\n\n\nProposed: Distribute trusted clients with notary\n\n\n3 min\n\n\n20210523-distribute-trusted-clients-with-notary.md\n\n\n\n\nAccepted: Complete glTF2 / VRM import and export pipeline in Godot Engine\n\n\n2 min\n\n\n20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.md\n\n\n\n\nAccepted: Support more flexible texture import via Basis Universal in Godot Engine\n\n\n2 min\n\n\n20210523-basis-universal-import.md\n\n\n\n\nAccepted: Use Markdown Architectural Decision Records\n\n\n2 min\n\n\n20210212-use-markdown-architectural-decision-records.md\n\n\n\n\nSuperseded: Use Log4brains to manage the ADRs\n\n\n2 min\n\n\n20210212-use-log4brains-to-manage-the-adrs.md\n\n\n\n\nProposed: Add build notifications\n\n\n2 min\n\n\n20210212-add-build-notifications.md\n\n\n\n\nAccepted: Adding Entity Networking to Groups\n\n\n7 min\n\n\n20200729-entity-networking.md\n\n\n\n\nMozilla Builders Summer MVP Lab (SUBMITTED ON JUNE 8 2020)\n\n\n12 min\n\n\n20200608-vsekai-charter.md\n\n\n\n\nAccepted: Manage backend resources on one or more physical machines with K3S\n\n\n26 min\n\n\n20200602-manage-backend-with-k3s.md\n\n\n\n\n\nNo matching items"
+    "text": "This solution is most useful for developers who frequently need to run certain commands at system startup. It may be less relevant for casual users or those who don’t use macOS."
   },
   {
-    "objectID": "index.html",
-    "href": "index.html",
-    "title": "V-Sekai Social VR",
+    "objectID": "decisions/20240502-mvsqlite-launchd.html#in-core-and-done-by-us",
+    "href": "decisions/20240502-mvsqlite-launchd.html#in-core-and-done-by-us",
+    "title": "Proposed: Launching the mvsqlite rdbms server",
     "section": "",
-    "text": "V-Sekai Social VR\n\n\n\n\n\n\nNote\n\n\n\n\n“V-Sekai” (pronounced vee-say-kai) stands for virtual, and in Japanese, “Sekai” means “World”.\n\n\n\n\nChit-Chat on Discord.\nEmbark to our world at v-sekai.org.\nFollow us on Twitter.\nContribute on GitHub here.\nReach Out to SaracenOne, Lyuma, or Fire."
+    "text": "This solution was developed in-house by the V-Sekai development team."
   },
   {
-    "objectID": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html",
-    "href": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html",
-    "title": "Rejected: RabbitMQ RA vs SQLite on FoundationDB vs CockroachDB",
+    "objectID": "decisions/20240502-mvsqlite-launchd.html#status",
+    "href": "decisions/20240502-mvsqlite-launchd.html#status",
+    "title": "Proposed: Launching the mvsqlite rdbms server",
     "section": "",
-    "text": "We are at a critical juncture in our system design process. The primary question is whether to utilize the RabbitMQ RA system for distributed state machines, implement an SQLite cluster database built on top of FoundationDB, or use CockroachDB.\n\n\n\nThe core issue is identifying which options deliver the fastest and most reliable service. We require a system capable of handling high data volumes, maintaining consistency, and ensuring rapid response times, particularly when transferring 3D scene format tiles from Blender or Godot Engine.\n\n\n\n\n\nRabbitMQ RA system might be the better choice if speed and low latency are the primary concerns. It’s designed for high-throughput scenarios and can handle many messages without significant delays.\n\n\n\nAn SQLite cluster database on FoundationDB, while also fast, focuses more on providing ACID transactions and scalability. Therefore, it could be better if the workload involves complex transactions or needs to scale over time.\n\n\n\nCockroachDB is a cloud-native SQL database for building global, scalable cloud services that survive disasters. It provides ACID transactional consistency and versioned values as first-class features.\n\n\n\n\n\nAll three systems offer robust solutions for handling large amounts of data.\nRabbitMQ RA system provides a reliable messaging system focusing on processing speed and low latency.\nSQLite cluster database on FoundationDB offers a scalable solution with ACID transactions.\nCockroachDB is a cloud-native SQL database that provides global scalability and disaster recovery.\n\n\n\n\n\nRabbitMQ RA system may not be as scalable as the SQLite cluster database on FoundationDB or CockroachDB.\nSQLite cluster database on FoundationDB might have slower response times than the RabbitMQ RA system.\nCockroachDB, while offering strong consistency and scalability, might not be as fast as RabbitMQ RA system for certain workloads.\n\n\n\n\nWe could also consider other databases or messaging systems, but these three options seem the most promising given our specific needs and constraints.\n\n\n\nIn cases where data volume is low, the difference in performance between these three systems may not be significant.\n\n\n\nOur development team will decide whether to use any of these systems. We will also handle the implementation and maintenance of the chosen system.\n\n\n\nStatus: Rejected \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nEfficient_Methods_for_Improving_Scalability_and_Playability_of_Massively_Multiplayer_Online_Game_MMOG\n\nAria assisted with this analysis."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#context",
-    "href": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#context",
-    "title": "Rejected: RabbitMQ RA vs SQLite on FoundationDB vs CockroachDB",
+    "objectID": "decisions/20240502-mvsqlite-launchd.html#decision-makers",
+    "href": "decisions/20240502-mvsqlite-launchd.html#decision-makers",
+    "title": "Proposed: Launching the mvsqlite rdbms server",
     "section": "",
-    "text": "We are at a critical juncture in our system design process. The primary question is whether to utilize the RabbitMQ RA system for distributed state machines, implement an SQLite cluster database built on top of FoundationDB, or use CockroachDB."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#problem-statement",
-    "href": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#problem-statement",
-    "title": "Rejected: RabbitMQ RA vs SQLite on FoundationDB vs CockroachDB",
+    "objectID": "decisions/20240502-mvsqlite-launchd.html#tags",
+    "href": "decisions/20240502-mvsqlite-launchd.html#tags",
+    "title": "Proposed: Launching the mvsqlite rdbms server",
     "section": "",
-    "text": "The core issue is identifying which options deliver the fastest and most reliable service. We require a system capable of handling high data volumes, maintaining consistency, and ensuring rapid response times, particularly when transferring 3D scene format tiles from Blender or Godot Engine."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#proposal",
-    "href": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#proposal",
-    "title": "Rejected: RabbitMQ RA vs SQLite on FoundationDB vs CockroachDB",
+    "objectID": "decisions/20240502-mvsqlite-launchd.html#further-reading",
+    "href": "decisions/20240502-mvsqlite-launchd.html#further-reading",
+    "title": "Proposed: Launching the mvsqlite rdbms server",
     "section": "",
-    "text": "RabbitMQ RA system might be the better choice if speed and low latency are the primary concerns. It’s designed for high-throughput scenarios and can handle many messages without significant delays.\n\n\n\nAn SQLite cluster database on FoundationDB, while also fast, focuses more on providing ACID transactions and scalability. Therefore, it could be better if the workload involves complex transactions or needs to scale over time.\n\n\n\nCockroachDB is a cloud-native SQL database for building global, scalable cloud services that survive disasters. It provides ACID transactional consistency and versioned values as first-class features."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAssistance provided by Aria, an AI assistant."
   },
   {
-    "objectID": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#benefits",
-    "href": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#benefits",
-    "title": "Rejected: RabbitMQ RA vs SQLite on FoundationDB vs CockroachDB",
+    "objectID": "decisions/20221019-replicate-sync-100-000-entities.html",
+    "href": "decisions/20221019-replicate-sync-100-000-entities.html",
+    "title": "Proposed: Replicate sync 100’000 entities using a solution (Revision 1)",
     "section": "",
-    "text": "All three systems offer robust solutions for handling large amounts of data.\nRabbitMQ RA system provides a reliable messaging system focusing on processing speed and low latency.\nSQLite cluster database on FoundationDB offers a scalable solution with ACID transactions.\nCockroachDB is a cloud-native SQL database that provides global scalability and disaster recovery."
+    "text": "Status: proposed\nDeciders: V-Sekai,fire,\nTags: V-Sekai,sync,view replication,\n\n\n\nDevelop a performant and robust (correctly and with liveness) network entity sync in V-Sekai.\nA client is one Godot Engine connection, it can view and change entities.\nThere are 100’000 networked entities in a city and we go from position a to position b in a loop in a mover with one or more attached cabins.\n\n\n\nThis document is a general problem statement.\n\n\n\n\nLarge sims!\n\n\n\n\n\n\n\n\nOption: Current V-Sekai replication\nRejection Reason: Can’t link servers\n\n\n\n\nEntity replication is not trivial.\n\n\n\nWe’re doing the networking layer.\n\n\n\n\n20221019-develop-a-replication-sync-for-100-000-entities.md\n20221016-v-sekai-view-replication.md\n20221014-networking-overhaul-proposal.md\nEfficientMethods_for_Improving_Scalability_and_Playability_of_Massively_Multiplayer_Online_Game_MMOG.pdf\n\n\n\nHow many clients can be in this simulation?\nThe state database should be smaller to avoid replication traffic on non-liveliness.\n\n\n\n\nThe calculation of who to pair and to find nearby or relevant players is a N^2 loop. Use better algorithms to lower O (N^2) into O (N log N).\nThe proposed solution can be solved in O (N log N).\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#downsides",
-    "href": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#downsides",
-    "title": "Rejected: RabbitMQ RA vs SQLite on FoundationDB vs CockroachDB",
+    "objectID": "decisions/20221019-replicate-sync-100-000-entities.html#context-and-problem-statement",
+    "href": "decisions/20221019-replicate-sync-100-000-entities.html#context-and-problem-statement",
+    "title": "Proposed: Replicate sync 100’000 entities using a solution (Revision 1)",
     "section": "",
-    "text": "RabbitMQ RA system may not be as scalable as the SQLite cluster database on FoundationDB or CockroachDB.\nSQLite cluster database on FoundationDB might have slower response times than the RabbitMQ RA system.\nCockroachDB, while offering strong consistency and scalability, might not be as fast as RabbitMQ RA system for certain workloads."
+    "text": "Develop a performant and robust (correctly and with liveness) network entity sync in V-Sekai.\nA client is one Godot Engine connection, it can view and change entities.\nThere are 100’000 networked entities in a city and we go from position a to position b in a loop in a mover with one or more attached cabins."
   },
   {
-    "objectID": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#alternatives",
-    "href": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#alternatives",
-    "title": "Rejected: RabbitMQ RA vs SQLite on FoundationDB vs CockroachDB",
+    "objectID": "decisions/20221019-replicate-sync-100-000-entities.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20221019-replicate-sync-100-000-entities.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: Replicate sync 100’000 entities using a solution (Revision 1)",
     "section": "",
-    "text": "We could also consider other databases or messaging systems, but these three options seem the most promising given our specific needs and constraints."
+    "text": "This document is a general problem statement."
   },
   {
-    "objectID": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#infrequent-use-case",
-    "href": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#infrequent-use-case",
-    "title": "Rejected: RabbitMQ RA vs SQLite on FoundationDB vs CockroachDB",
+    "objectID": "decisions/20221019-replicate-sync-100-000-entities.html#positive-consequences",
+    "href": "decisions/20221019-replicate-sync-100-000-entities.html#positive-consequences",
+    "title": "Proposed: Replicate sync 100’000 entities using a solution (Revision 1)",
     "section": "",
-    "text": "In cases where data volume is low, the difference in performance between these three systems may not be significant."
+    "text": "Large sims!"
   },
   {
-    "objectID": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#implementation",
-    "href": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#implementation",
-    "title": "Rejected: RabbitMQ RA vs SQLite on FoundationDB vs CockroachDB",
+    "objectID": "decisions/20221019-replicate-sync-100-000-entities.html#option-graveyard",
+    "href": "decisions/20221019-replicate-sync-100-000-entities.html#option-graveyard",
+    "title": "Proposed: Replicate sync 100’000 entities using a solution (Revision 1)",
     "section": "",
-    "text": "Our development team will decide whether to use any of these systems. We will also handle the implementation and maintenance of the chosen system."
+    "text": "Option: Current V-Sekai replication\nRejection Reason: Can’t link servers"
   },
   {
-    "objectID": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#status",
-    "href": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#status",
-    "title": "Rejected: RabbitMQ RA vs SQLite on FoundationDB vs CockroachDB",
+    "objectID": "decisions/20221019-replicate-sync-100-000-entities.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20221019-replicate-sync-100-000-entities.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Replicate sync 100’000 entities using a solution (Revision 1)",
     "section": "",
-    "text": "Status: Rejected"
+    "text": "Entity replication is not trivial."
   },
   {
-    "objectID": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#decision-makers",
-    "href": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#decision-makers",
-    "title": "Rejected: RabbitMQ RA vs SQLite on FoundationDB vs CockroachDB",
+    "objectID": "decisions/20221019-replicate-sync-100-000-entities.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20221019-replicate-sync-100-000-entities.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Replicate sync 100’000 entities using a solution (Revision 1)",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "We’re doing the networking layer."
   },
   {
-    "objectID": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#tags",
-    "href": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#tags",
-    "title": "Rejected: RabbitMQ RA vs SQLite on FoundationDB vs CockroachDB",
+    "objectID": "decisions/20221019-replicate-sync-100-000-entities.html#references",
+    "href": "decisions/20221019-replicate-sync-100-000-entities.html#references",
+    "title": "Proposed: Replicate sync 100’000 entities using a solution (Revision 1)",
     "section": "",
-    "text": "V-Sekai"
+    "text": "20221019-develop-a-replication-sync-for-100-000-entities.md\n20221016-v-sekai-view-replication.md\n20221014-networking-overhaul-proposal.md\nEfficientMethods_for_Improving_Scalability_and_Playability_of_Massively_Multiplayer_Online_Game_MMOG.pdf\n\n\n\nHow many clients can be in this simulation?\nThe state database should be smaller to avoid replication traffic on non-liveliness."
   },
   {
-    "objectID": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#further-reading",
-    "href": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#further-reading",
-    "title": "Rejected: RabbitMQ RA vs SQLite on FoundationDB vs CockroachDB",
+    "objectID": "decisions/20221019-replicate-sync-100-000-entities.html#math",
+    "href": "decisions/20221019-replicate-sync-100-000-entities.html#math",
+    "title": "Proposed: Replicate sync 100’000 entities using a solution (Revision 1)",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nEfficient_Methods_for_Improving_Scalability_and_Playability_of_Massively_Multiplayer_Online_Game_MMOG\n\nAria assisted with this analysis."
+    "text": "The calculation of who to pair and to find nearby or relevant players is a N^2 loop. Use better algorithms to lower O (N^2) into O (N log N).\nThe proposed solution can be solved in O (N log N)."
   },
   {
-    "objectID": "decisions/20240326-heartstrings-vr.html",
-    "href": "decisions/20240326-heartstrings-vr.html",
-    "title": "Proposed: “Cafe Serenade” - A VR Dating Sim Experience",
+    "objectID": "decisions/20221019-replicate-sync-100-000-entities.html#derivative-license",
+    "href": "decisions/20221019-replicate-sync-100-000-entities.html#derivative-license",
+    "title": "Proposed: Replicate sync 100’000 entities using a solution (Revision 1)",
     "section": "",
-    "text": "The growing interest in VR as a medium for more intimate and engaging storytelling provides a unique opportunity for innovative game designs. Within this space, the concept of a VR dating simulation offers a fresh avenue to explore personal connections and storytelling.\n\n\n\nMost VR experiences lack the depth and emotional engagement found in traditional dating sims. There’s a gap in the VR market for a game that combines the immersive aspects of VR with the rich narratives and character development of dating sims.\n\n\n\n// Example interaction system\nfunction initiate_conversation(character):\n    if player_approaches(character):\n        display_dialogue_options()\n        player_selection = get_player_input()\n        update_character_affinity(player_selection)\n        reveal_next_story_bit(character, player_selection)\n\n// Mock-up of cafe environment and character placement\n[ Cafe Layout ]\n[Table1] [Character1]    [Bar]    [Character2]\n                 [PlayerStartPoint]\n                              [Character3] [Table2]\n\n\n\n\nImmersive Engagement: By leveraging VR, players can experience a deeper sense of presence and emotional connection with the characters.\nInnovative Storytelling: Utilizing VR to tell stories in a dating sim format opens new narrative possibilities, such as non-verbal communication and spatial storytelling.\nAccessibility: Simple interaction models make the game accessible to VR newcomers, while the depth of story appeals to dating sim enthusiasts.\n\n\n\n\n\nDevelopment Complexity: Crafting a VR experience that is both immersive and interactive can be resource-intensive.\nNiche Appeal: The combination of VR and dating sims may cater to a niche market, potentially limiting the audience size.\n\n\n\n\nAn alternate approach would have been to develop a traditional 2D dating sim with VR elements as secondary features. This would reduce development complexity but also diminish the uniqueness and immersive potential of the experience.\n\n\n\nFor players who may not frequently engage with VR or dating sims, “Cafe Serenade” will offer a “casual mode” with simplified interactions and the ability to observe stories without active participation, encouraging them to explore the game at their own pace.\n\n\n\nThe core game mechanics, narrative development, and character design will be handled in-house to maintain a cohesive vision and quality. External collaborations may involve additional art assets and voice acting.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
+    "text": "Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240326-heartstrings-vr.html#the-context",
-    "href": "decisions/20240326-heartstrings-vr.html#the-context",
-    "title": "Proposed: “Cafe Serenade” - A VR Dating Sim Experience",
+    "objectID": "decisions/20210811-soiree-party.html",
+    "href": "decisions/20210811-soiree-party.html",
+    "title": "Proposed: Soiree party mode",
     "section": "",
-    "text": "The growing interest in VR as a medium for more intimate and engaging storytelling provides a unique opportunity for innovative game designs. Within this space, the concept of a VR dating simulation offers a fresh avenue to explore personal connections and storytelling."
+    "text": "Proposed: Soiree party mode\n\nContext and Problem Statement\nV-Sekai aspires to be an open source 3d virtual world platform that has VR and desktop modes.\nWe want to make it easy to deploy V-Sekai in Soiree mode.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nWe package V-Sekai in Soiree Party mode, so it is easier to test the system.\nA Soiree is a party or gathering, typically in a private house, for conversation or music.\n\nRisks\nSandstorm network access APIs may not work for the use case.\nIn most cases, things that run over plain HTTP requests should be able to work, but other network protocols tend to be nontrivial.\nSandstorm at current would neither support WebRTC or UDP traffic through the Powerbox, but it is uncertain what is needed to add it.\nRisk to migrate the Sandstorm ecosystem to Kubernetes helm system to match the devops status quo. Vargrant is not the status quo.\n\nProxying\nSome udp based proxying methods are known\n\nhttps://github.com/yyyar/gobetween for standalone\ncillium for kubernetes\nWebRTC ice, stun, turn\n\n\n\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n\nV-Sekai Developers\nWe package V-Sekai in Soiree party mode.\n\nWe start a single server of CockroachDB SQL database and not the default 3 server mode.\nWe provide installs of the Godot game engine client and server.\nWe re-arrange our elixir application Uro to work as a Sandstorm.io application.\n\n\n\nV-Sekai Packages\n\nV-Sekai provides a Server Download Package connecting via PowerBox.\nV-Sekai a Client Download Package connecting via PowerBox.\nV-Sekai a Uro Download Package connecting via PowerBox.\n\nThere is an open question if V-Sekai sandbox design works with powerbox.\n\n\nPlayer and Hosts\n\nIndividual hosts of Sandstorm.io can start their own grains of V-Sekai in Soiree mode.\nPlayers download the Godot Engine client and play.\n\n\n\nHosts\n\nMust provide a way to access the Godot Engine server and the Sandstorm server.\n\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nIt is not trivial and not a few lines to implement a distributed system for a developer.\n\n\nPositive Consequences\nSelf-hosted is a feature.\nWe can use Soiree Party mode to test V-Sekai.\n\n\nNegative Consequences\nMaybe too complicated for the developers.\n\n\nIs there a reason why this should be core and done by us?\nWe are investigating how to implement the Soiree Party mode.\n\n\nReferences\n\nhttps://www.cockroachlabs.com/\nhttps://github.com/V-Sekai/uro\nhttps://docs.sandstorm.io/en/latest/developing/powerbox/\nhttps://docs.sandstorm.io/en/latest/vagrant-spk/services/\nhttps://github.com/sandstorm-io/sandstorm\nhttps://github.com/mrmetaverse/soiree\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240326-heartstrings-vr.html#the-problem-statement",
-    "href": "decisions/20240326-heartstrings-vr.html#the-problem-statement",
-    "title": "Proposed: “Cafe Serenade” - A VR Dating Sim Experience",
+    "objectID": "decisions/20231110-ai-based-outlier-detection.html",
+    "href": "decisions/20231110-ai-based-outlier-detection.html",
+    "title": "Proposed: Streamlining Game Development with AI-Based Aria’s Guidance",
     "section": "",
-    "text": "Most VR experiences lack the depth and emotional engagement found in traditional dating sims. There’s a gap in the VR market for a game that combines the immersive aspects of VR with the rich narratives and character development of dating sims."
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, AI, Game Development, Outlier Detection\n\n\n\n\nGame assets often contain defects. Aria, an AI-based game creation assistant, can help detect and rectify these issues by calling necessary functions to perform tests.\n\n\n\nThe challenge is to efficiently identify and correct common errors in game assets, ranging from minor glitches to major bugs. Manual detection is time-consuming and prone to human error. Additionally, managing the size of data being processed by a large language model (LLM) with a 128k token context presents a challenge.\n\n\n\nWe propose implementing an AI-Based Outlier Detector game creation assistant that detects common errors. This system would analyze game assets, identify anomalies, and suggest corrections. To manage the large token context, we suggest using proxy resources - simplified versions of original assets that retain enough detail for the AI to perform its analysis.\nA key requirement is for the assistant to retain input data only until it has been processed. Permission is required to incorporate any input data into the learning dataset, ensuring user privacy and data security.\n\n\n\n\nReduces debugging and error correction time.\nImproves game quality by ensuring all assets function as intended.\nEfficiently processes large amounts of data using proxy resources.\n\n\n\n\n\nRequires significant resources for development and integration.\nMay not identify all types of bugs, especially those requiring contextual understanding.\nProxy resources may not capture all nuances of original assets.\n\n\n\n\nAn alternative could be enhancing existing manual testing processes or using traditional bug tracking software. However, these methods may not offer the same efficiency and accuracy as an AI-based system.\n\n\n\nThis solution is particularly useful for large-scale game projects with numerous assets where manual error detection would be inefficient.\n\n\n\nYes, this proposal suggests the development of an in-house AI system tailored to our specific needs.\n\n\n\n\nV-Sekai · GitHub\nV-Sekai/v-sekai-game\nNousResearch Yarn Mistral 7b 128k - Hugging Face\n\nThis proposal was assisted by Aria, an AI assistant."
   },
   {
-    "objectID": "decisions/20240326-heartstrings-vr.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240326-heartstrings-vr.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: “Cafe Serenade” - A VR Dating Sim Experience",
+    "objectID": "decisions/20231110-ai-based-outlier-detection.html#metadata",
+    "href": "decisions/20231110-ai-based-outlier-detection.html#metadata",
+    "title": "Proposed: Streamlining Game Development with AI-Based Aria’s Guidance",
     "section": "",
-    "text": "// Example interaction system\nfunction initiate_conversation(character):\n    if player_approaches(character):\n        display_dialogue_options()\n        player_selection = get_player_input()\n        update_character_affinity(player_selection)\n        reveal_next_story_bit(character, player_selection)\n\n// Mock-up of cafe environment and character placement\n[ Cafe Layout ]\n[Table1] [Character1]    [Bar]    [Character2]\n                 [PlayerStartPoint]\n                              [Character3] [Table2]"
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, AI, Game Development, Outlier Detection"
   },
   {
-    "objectID": "decisions/20240326-heartstrings-vr.html#the-benefits",
-    "href": "decisions/20240326-heartstrings-vr.html#the-benefits",
-    "title": "Proposed: “Cafe Serenade” - A VR Dating Sim Experience",
+    "objectID": "decisions/20231110-ai-based-outlier-detection.html#the-backdrop",
+    "href": "decisions/20231110-ai-based-outlier-detection.html#the-backdrop",
+    "title": "Proposed: Streamlining Game Development with AI-Based Aria’s Guidance",
     "section": "",
-    "text": "Immersive Engagement: By leveraging VR, players can experience a deeper sense of presence and emotional connection with the characters.\nInnovative Storytelling: Utilizing VR to tell stories in a dating sim format opens new narrative possibilities, such as non-verbal communication and spatial storytelling.\nAccessibility: Simple interaction models make the game accessible to VR newcomers, while the depth of story appeals to dating sim enthusiasts."
+    "text": "Game assets often contain defects. Aria, an AI-based game creation assistant, can help detect and rectify these issues by calling necessary functions to perform tests."
   },
   {
-    "objectID": "decisions/20240326-heartstrings-vr.html#the-downsides",
-    "href": "decisions/20240326-heartstrings-vr.html#the-downsides",
-    "title": "Proposed: “Cafe Serenade” - A VR Dating Sim Experience",
+    "objectID": "decisions/20231110-ai-based-outlier-detection.html#the-challenge",
+    "href": "decisions/20231110-ai-based-outlier-detection.html#the-challenge",
+    "title": "Proposed: Streamlining Game Development with AI-Based Aria’s Guidance",
     "section": "",
-    "text": "Development Complexity: Crafting a VR experience that is both immersive and interactive can be resource-intensive.\nNiche Appeal: The combination of VR and dating sims may cater to a niche market, potentially limiting the audience size."
+    "text": "The challenge is to efficiently identify and correct common errors in game assets, ranging from minor glitches to major bugs. Manual detection is time-consuming and prone to human error. Additionally, managing the size of data being processed by a large language model (LLM) with a 128k token context presents a challenge."
   },
   {
-    "objectID": "decisions/20240326-heartstrings-vr.html#the-road-not-taken",
-    "href": "decisions/20240326-heartstrings-vr.html#the-road-not-taken",
-    "title": "Proposed: “Cafe Serenade” - A VR Dating Sim Experience",
+    "objectID": "decisions/20231110-ai-based-outlier-detection.html#the-strategy",
+    "href": "decisions/20231110-ai-based-outlier-detection.html#the-strategy",
+    "title": "Proposed: Streamlining Game Development with AI-Based Aria’s Guidance",
     "section": "",
-    "text": "An alternate approach would have been to develop a traditional 2D dating sim with VR elements as secondary features. This would reduce development complexity but also diminish the uniqueness and immersive potential of the experience."
+    "text": "We propose implementing an AI-Based Outlier Detector game creation assistant that detects common errors. This system would analyze game assets, identify anomalies, and suggest corrections. To manage the large token context, we suggest using proxy resources - simplified versions of original assets that retain enough detail for the AI to perform its analysis.\nA key requirement is for the assistant to retain input data only until it has been processed. Permission is required to incorporate any input data into the learning dataset, ensuring user privacy and data security."
   },
   {
-    "objectID": "decisions/20240326-heartstrings-vr.html#the-infrequent-use-case",
-    "href": "decisions/20240326-heartstrings-vr.html#the-infrequent-use-case",
-    "title": "Proposed: “Cafe Serenade” - A VR Dating Sim Experience",
+    "objectID": "decisions/20231110-ai-based-outlier-detection.html#the-upside",
+    "href": "decisions/20231110-ai-based-outlier-detection.html#the-upside",
+    "title": "Proposed: Streamlining Game Development with AI-Based Aria’s Guidance",
     "section": "",
-    "text": "For players who may not frequently engage with VR or dating sims, “Cafe Serenade” will offer a “casual mode” with simplified interactions and the ability to observe stories without active participation, encouraging them to explore the game at their own pace."
+    "text": "Reduces debugging and error correction time.\nImproves game quality by ensuring all assets function as intended.\nEfficiently processes large amounts of data using proxy resources."
   },
   {
-    "objectID": "decisions/20240326-heartstrings-vr.html#in-core-and-done-by-us",
-    "href": "decisions/20240326-heartstrings-vr.html#in-core-and-done-by-us",
-    "title": "Proposed: “Cafe Serenade” - A VR Dating Sim Experience",
+    "objectID": "decisions/20231110-ai-based-outlier-detection.html#the-downside",
+    "href": "decisions/20231110-ai-based-outlier-detection.html#the-downside",
+    "title": "Proposed: Streamlining Game Development with AI-Based Aria’s Guidance",
     "section": "",
-    "text": "The core game mechanics, narrative development, and character design will be handled in-house to maintain a cohesive vision and quality. External collaborations may involve additional art assets and voice acting."
+    "text": "Requires significant resources for development and integration.\nMay not identify all types of bugs, especially those requiring contextual understanding.\nProxy resources may not capture all nuances of original assets."
   },
   {
-    "objectID": "decisions/20240326-heartstrings-vr.html#status",
-    "href": "decisions/20240326-heartstrings-vr.html#status",
-    "title": "Proposed: “Cafe Serenade” - A VR Dating Sim Experience",
+    "objectID": "decisions/20231110-ai-based-outlier-detection.html#alternatives",
+    "href": "decisions/20231110-ai-based-outlier-detection.html#alternatives",
+    "title": "Proposed: Streamlining Game Development with AI-Based Aria’s Guidance",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "An alternative could be enhancing existing manual testing processes or using traditional bug tracking software. However, these methods may not offer the same efficiency and accuracy as an AI-based system."
   },
   {
-    "objectID": "decisions/20240326-heartstrings-vr.html#decision-makers",
-    "href": "decisions/20240326-heartstrings-vr.html#decision-makers",
-    "title": "Proposed: “Cafe Serenade” - A VR Dating Sim Experience",
+    "objectID": "decisions/20231110-ai-based-outlier-detection.html#the-infrequent-use-case",
+    "href": "decisions/20231110-ai-based-outlier-detection.html#the-infrequent-use-case",
+    "title": "Proposed: Streamlining Game Development with AI-Based Aria’s Guidance",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "This solution is particularly useful for large-scale game projects with numerous assets where manual error detection would be inefficient."
   },
   {
-    "objectID": "decisions/20240326-heartstrings-vr.html#tags",
-    "href": "decisions/20240326-heartstrings-vr.html#tags",
-    "title": "Proposed: “Cafe Serenade” - A VR Dating Sim Experience",
+    "objectID": "decisions/20231110-ai-based-outlier-detection.html#in-core-and-done-by-us",
+    "href": "decisions/20231110-ai-based-outlier-detection.html#in-core-and-done-by-us",
+    "title": "Proposed: Streamlining Game Development with AI-Based Aria’s Guidance",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Yes, this proposal suggests the development of an in-house AI system tailored to our specific needs."
   },
   {
-    "objectID": "decisions/20240326-heartstrings-vr.html#further-reading",
-    "href": "decisions/20240326-heartstrings-vr.html#further-reading",
-    "title": "Proposed: “Cafe Serenade” - A VR Dating Sim Experience",
+    "objectID": "decisions/20231110-ai-based-outlier-detection.html#further-reading",
+    "href": "decisions/20231110-ai-based-outlier-detection.html#further-reading",
+    "title": "Proposed: Streamlining Game Development with AI-Based Aria’s Guidance",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
+    "text": "V-Sekai · GitHub\nV-Sekai/v-sekai-game\nNousResearch Yarn Mistral 7b 128k - Hugging Face\n\nThis proposal was assisted by Aria, an AI assistant."
   },
   {
-    "objectID": "decisions/20210715-Material-Addon-Blender.html",
-    "href": "decisions/20210715-Material-Addon-Blender.html",
-    "title": "Proposed: Material Addon Blender",
+    "objectID": "decisions/20211031-export-import-testing-via-robot-framework-and-swiftshader.html",
+    "href": "decisions/20211031-export-import-testing-via-robot-framework-and-swiftshader.html",
+    "title": "Proposed: Export / Import testing via robot-framework and swiftshader",
     "section": "",
-    "text": "Proposed: Material Addon Blender\n\nContext and Problem Statement\nWant to bake procedural materials to Godot Engine that change based on input\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nImplement a Material Addon for Blender\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n\nMake a stand alone baker https://github.com/materialx/MaterialX/pull/651\nMake a Blender addon that creates a custom node\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nProcedural Materials are not easy to implement in a few lines of code.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nProcedural Materials are not easy\n\n\nReferences\n\nhttps://github.com/materialx/MaterialX\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Proposed: Export / Import testing via robot-framework and swiftshader\n\nContext and Problem Statement\nNeed to automated test the game\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nUse robot framework and swift shader.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nExport / Import testing via robot-framework and swiftshader\nAutomate scripts.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot trivial.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nI can improve this.\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
     "objectID": "decisions/20240709-wired-first.html",
@@ -14574,14402 +14490,14486 @@
     "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20211031-export-import-testing-via-robot-framework-and-swiftshader.html",
-    "href": "decisions/20211031-export-import-testing-via-robot-framework-and-swiftshader.html",
-    "title": "Proposed: Export / Import testing via robot-framework and swiftshader",
+    "objectID": "decisions/20210715-Material-Addon-Blender.html",
+    "href": "decisions/20210715-Material-Addon-Blender.html",
+    "title": "Proposed: Material Addon Blender",
     "section": "",
-    "text": "Proposed: Export / Import testing via robot-framework and swiftshader\n\nContext and Problem Statement\nNeed to automated test the game\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nUse robot framework and swift shader.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nExport / Import testing via robot-framework and swiftshader\nAutomate scripts.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot trivial.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nI can improve this.\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Proposed: Material Addon Blender\n\nContext and Problem Statement\nWant to bake procedural materials to Godot Engine that change based on input\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nImplement a Material Addon for Blender\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n\nMake a stand alone baker https://github.com/materialx/MaterialX/pull/651\nMake a Blender addon that creates a custom node\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nProcedural Materials are not easy to implement in a few lines of code.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nProcedural Materials are not easy\n\n\nReferences\n\nhttps://github.com/materialx/MaterialX\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20231110-ai-based-outlier-detection.html",
-    "href": "decisions/20231110-ai-based-outlier-detection.html",
-    "title": "Proposed: Streamlining Game Development with AI-Based Aria’s Guidance",
+    "objectID": "decisions/20240326-heartstrings-vr.html",
+    "href": "decisions/20240326-heartstrings-vr.html",
+    "title": "Proposed: “Cafe Serenade” - A VR Dating Sim Experience",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, AI, Game Development, Outlier Detection\n\n\n\n\nGame assets often contain defects. Aria, an AI-based game creation assistant, can help detect and rectify these issues by calling necessary functions to perform tests.\n\n\n\nThe challenge is to efficiently identify and correct common errors in game assets, ranging from minor glitches to major bugs. Manual detection is time-consuming and prone to human error. Additionally, managing the size of data being processed by a large language model (LLM) with a 128k token context presents a challenge.\n\n\n\nWe propose implementing an AI-Based Outlier Detector game creation assistant that detects common errors. This system would analyze game assets, identify anomalies, and suggest corrections. To manage the large token context, we suggest using proxy resources - simplified versions of original assets that retain enough detail for the AI to perform its analysis.\nA key requirement is for the assistant to retain input data only until it has been processed. Permission is required to incorporate any input data into the learning dataset, ensuring user privacy and data security.\n\n\n\n\nReduces debugging and error correction time.\nImproves game quality by ensuring all assets function as intended.\nEfficiently processes large amounts of data using proxy resources.\n\n\n\n\n\nRequires significant resources for development and integration.\nMay not identify all types of bugs, especially those requiring contextual understanding.\nProxy resources may not capture all nuances of original assets.\n\n\n\n\nAn alternative could be enhancing existing manual testing processes or using traditional bug tracking software. However, these methods may not offer the same efficiency and accuracy as an AI-based system.\n\n\n\nThis solution is particularly useful for large-scale game projects with numerous assets where manual error detection would be inefficient.\n\n\n\nYes, this proposal suggests the development of an in-house AI system tailored to our specific needs.\n\n\n\n\nV-Sekai · GitHub\nV-Sekai/v-sekai-game\nNousResearch Yarn Mistral 7b 128k - Hugging Face\n\nThis proposal was assisted by Aria, an AI assistant."
+    "text": "The growing interest in VR as a medium for more intimate and engaging storytelling provides a unique opportunity for innovative game designs. Within this space, the concept of a VR dating simulation offers a fresh avenue to explore personal connections and storytelling.\n\n\n\nMost VR experiences lack the depth and emotional engagement found in traditional dating sims. There’s a gap in the VR market for a game that combines the immersive aspects of VR with the rich narratives and character development of dating sims.\n\n\n\n// Example interaction system\nfunction initiate_conversation(character):\n    if player_approaches(character):\n        display_dialogue_options()\n        player_selection = get_player_input()\n        update_character_affinity(player_selection)\n        reveal_next_story_bit(character, player_selection)\n\n// Mock-up of cafe environment and character placement\n[ Cafe Layout ]\n[Table1] [Character1]    [Bar]    [Character2]\n                 [PlayerStartPoint]\n                              [Character3] [Table2]\n\n\n\n\nImmersive Engagement: By leveraging VR, players can experience a deeper sense of presence and emotional connection with the characters.\nInnovative Storytelling: Utilizing VR to tell stories in a dating sim format opens new narrative possibilities, such as non-verbal communication and spatial storytelling.\nAccessibility: Simple interaction models make the game accessible to VR newcomers, while the depth of story appeals to dating sim enthusiasts.\n\n\n\n\n\nDevelopment Complexity: Crafting a VR experience that is both immersive and interactive can be resource-intensive.\nNiche Appeal: The combination of VR and dating sims may cater to a niche market, potentially limiting the audience size.\n\n\n\n\nAn alternate approach would have been to develop a traditional 2D dating sim with VR elements as secondary features. This would reduce development complexity but also diminish the uniqueness and immersive potential of the experience.\n\n\n\nFor players who may not frequently engage with VR or dating sims, “Cafe Serenade” will offer a “casual mode” with simplified interactions and the ability to observe stories without active participation, encouraging them to explore the game at their own pace.\n\n\n\nThe core game mechanics, narrative development, and character design will be handled in-house to maintain a cohesive vision and quality. External collaborations may involve additional art assets and voice acting.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20231110-ai-based-outlier-detection.html#metadata",
-    "href": "decisions/20231110-ai-based-outlier-detection.html#metadata",
-    "title": "Proposed: Streamlining Game Development with AI-Based Aria’s Guidance",
+    "objectID": "decisions/20240326-heartstrings-vr.html#the-context",
+    "href": "decisions/20240326-heartstrings-vr.html#the-context",
+    "title": "Proposed: “Cafe Serenade” - A VR Dating Sim Experience",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, AI, Game Development, Outlier Detection"
+    "text": "The growing interest in VR as a medium for more intimate and engaging storytelling provides a unique opportunity for innovative game designs. Within this space, the concept of a VR dating simulation offers a fresh avenue to explore personal connections and storytelling."
   },
   {
-    "objectID": "decisions/20231110-ai-based-outlier-detection.html#the-backdrop",
-    "href": "decisions/20231110-ai-based-outlier-detection.html#the-backdrop",
-    "title": "Proposed: Streamlining Game Development with AI-Based Aria’s Guidance",
+    "objectID": "decisions/20240326-heartstrings-vr.html#the-problem-statement",
+    "href": "decisions/20240326-heartstrings-vr.html#the-problem-statement",
+    "title": "Proposed: “Cafe Serenade” - A VR Dating Sim Experience",
     "section": "",
-    "text": "Game assets often contain defects. Aria, an AI-based game creation assistant, can help detect and rectify these issues by calling necessary functions to perform tests."
+    "text": "Most VR experiences lack the depth and emotional engagement found in traditional dating sims. There’s a gap in the VR market for a game that combines the immersive aspects of VR with the rich narratives and character development of dating sims."
   },
   {
-    "objectID": "decisions/20231110-ai-based-outlier-detection.html#the-challenge",
-    "href": "decisions/20231110-ai-based-outlier-detection.html#the-challenge",
-    "title": "Proposed: Streamlining Game Development with AI-Based Aria’s Guidance",
+    "objectID": "decisions/20240326-heartstrings-vr.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240326-heartstrings-vr.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: “Cafe Serenade” - A VR Dating Sim Experience",
     "section": "",
-    "text": "The challenge is to efficiently identify and correct common errors in game assets, ranging from minor glitches to major bugs. Manual detection is time-consuming and prone to human error. Additionally, managing the size of data being processed by a large language model (LLM) with a 128k token context presents a challenge."
+    "text": "// Example interaction system\nfunction initiate_conversation(character):\n    if player_approaches(character):\n        display_dialogue_options()\n        player_selection = get_player_input()\n        update_character_affinity(player_selection)\n        reveal_next_story_bit(character, player_selection)\n\n// Mock-up of cafe environment and character placement\n[ Cafe Layout ]\n[Table1] [Character1]    [Bar]    [Character2]\n                 [PlayerStartPoint]\n                              [Character3] [Table2]"
   },
   {
-    "objectID": "decisions/20231110-ai-based-outlier-detection.html#the-strategy",
-    "href": "decisions/20231110-ai-based-outlier-detection.html#the-strategy",
-    "title": "Proposed: Streamlining Game Development with AI-Based Aria’s Guidance",
+    "objectID": "decisions/20240326-heartstrings-vr.html#the-benefits",
+    "href": "decisions/20240326-heartstrings-vr.html#the-benefits",
+    "title": "Proposed: “Cafe Serenade” - A VR Dating Sim Experience",
     "section": "",
-    "text": "We propose implementing an AI-Based Outlier Detector game creation assistant that detects common errors. This system would analyze game assets, identify anomalies, and suggest corrections. To manage the large token context, we suggest using proxy resources - simplified versions of original assets that retain enough detail for the AI to perform its analysis.\nA key requirement is for the assistant to retain input data only until it has been processed. Permission is required to incorporate any input data into the learning dataset, ensuring user privacy and data security."
+    "text": "Immersive Engagement: By leveraging VR, players can experience a deeper sense of presence and emotional connection with the characters.\nInnovative Storytelling: Utilizing VR to tell stories in a dating sim format opens new narrative possibilities, such as non-verbal communication and spatial storytelling.\nAccessibility: Simple interaction models make the game accessible to VR newcomers, while the depth of story appeals to dating sim enthusiasts."
   },
   {
-    "objectID": "decisions/20231110-ai-based-outlier-detection.html#the-upside",
-    "href": "decisions/20231110-ai-based-outlier-detection.html#the-upside",
-    "title": "Proposed: Streamlining Game Development with AI-Based Aria’s Guidance",
+    "objectID": "decisions/20240326-heartstrings-vr.html#the-downsides",
+    "href": "decisions/20240326-heartstrings-vr.html#the-downsides",
+    "title": "Proposed: “Cafe Serenade” - A VR Dating Sim Experience",
     "section": "",
-    "text": "Reduces debugging and error correction time.\nImproves game quality by ensuring all assets function as intended.\nEfficiently processes large amounts of data using proxy resources."
+    "text": "Development Complexity: Crafting a VR experience that is both immersive and interactive can be resource-intensive.\nNiche Appeal: The combination of VR and dating sims may cater to a niche market, potentially limiting the audience size."
   },
   {
-    "objectID": "decisions/20231110-ai-based-outlier-detection.html#the-downside",
-    "href": "decisions/20231110-ai-based-outlier-detection.html#the-downside",
-    "title": "Proposed: Streamlining Game Development with AI-Based Aria’s Guidance",
+    "objectID": "decisions/20240326-heartstrings-vr.html#the-road-not-taken",
+    "href": "decisions/20240326-heartstrings-vr.html#the-road-not-taken",
+    "title": "Proposed: “Cafe Serenade” - A VR Dating Sim Experience",
     "section": "",
-    "text": "Requires significant resources for development and integration.\nMay not identify all types of bugs, especially those requiring contextual understanding.\nProxy resources may not capture all nuances of original assets."
+    "text": "An alternate approach would have been to develop a traditional 2D dating sim with VR elements as secondary features. This would reduce development complexity but also diminish the uniqueness and immersive potential of the experience."
   },
   {
-    "objectID": "decisions/20231110-ai-based-outlier-detection.html#alternatives",
-    "href": "decisions/20231110-ai-based-outlier-detection.html#alternatives",
-    "title": "Proposed: Streamlining Game Development with AI-Based Aria’s Guidance",
+    "objectID": "decisions/20240326-heartstrings-vr.html#the-infrequent-use-case",
+    "href": "decisions/20240326-heartstrings-vr.html#the-infrequent-use-case",
+    "title": "Proposed: “Cafe Serenade” - A VR Dating Sim Experience",
     "section": "",
-    "text": "An alternative could be enhancing existing manual testing processes or using traditional bug tracking software. However, these methods may not offer the same efficiency and accuracy as an AI-based system."
+    "text": "For players who may not frequently engage with VR or dating sims, “Cafe Serenade” will offer a “casual mode” with simplified interactions and the ability to observe stories without active participation, encouraging them to explore the game at their own pace."
   },
   {
-    "objectID": "decisions/20231110-ai-based-outlier-detection.html#the-infrequent-use-case",
-    "href": "decisions/20231110-ai-based-outlier-detection.html#the-infrequent-use-case",
-    "title": "Proposed: Streamlining Game Development with AI-Based Aria’s Guidance",
+    "objectID": "decisions/20240326-heartstrings-vr.html#in-core-and-done-by-us",
+    "href": "decisions/20240326-heartstrings-vr.html#in-core-and-done-by-us",
+    "title": "Proposed: “Cafe Serenade” - A VR Dating Sim Experience",
     "section": "",
-    "text": "This solution is particularly useful for large-scale game projects with numerous assets where manual error detection would be inefficient."
+    "text": "The core game mechanics, narrative development, and character design will be handled in-house to maintain a cohesive vision and quality. External collaborations may involve additional art assets and voice acting."
   },
   {
-    "objectID": "decisions/20231110-ai-based-outlier-detection.html#in-core-and-done-by-us",
-    "href": "decisions/20231110-ai-based-outlier-detection.html#in-core-and-done-by-us",
-    "title": "Proposed: Streamlining Game Development with AI-Based Aria’s Guidance",
+    "objectID": "decisions/20240326-heartstrings-vr.html#status",
+    "href": "decisions/20240326-heartstrings-vr.html#status",
+    "title": "Proposed: “Cafe Serenade” - A VR Dating Sim Experience",
     "section": "",
-    "text": "Yes, this proposal suggests the development of an in-house AI system tailored to our specific needs."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20231110-ai-based-outlier-detection.html#further-reading",
-    "href": "decisions/20231110-ai-based-outlier-detection.html#further-reading",
-    "title": "Proposed: Streamlining Game Development with AI-Based Aria’s Guidance",
+    "objectID": "decisions/20240326-heartstrings-vr.html#decision-makers",
+    "href": "decisions/20240326-heartstrings-vr.html#decision-makers",
+    "title": "Proposed: “Cafe Serenade” - A VR Dating Sim Experience",
     "section": "",
-    "text": "V-Sekai · GitHub\nV-Sekai/v-sekai-game\nNousResearch Yarn Mistral 7b 128k - Hugging Face\n\nThis proposal was assisted by Aria, an AI assistant."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20210811-soiree-party.html",
-    "href": "decisions/20210811-soiree-party.html",
-    "title": "Proposed: Soiree party mode",
+    "objectID": "decisions/20240326-heartstrings-vr.html#tags",
+    "href": "decisions/20240326-heartstrings-vr.html#tags",
+    "title": "Proposed: “Cafe Serenade” - A VR Dating Sim Experience",
     "section": "",
-    "text": "Proposed: Soiree party mode\n\nContext and Problem Statement\nV-Sekai aspires to be an open source 3d virtual world platform that has VR and desktop modes.\nWe want to make it easy to deploy V-Sekai in Soiree mode.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nWe package V-Sekai in Soiree Party mode, so it is easier to test the system.\nA Soiree is a party or gathering, typically in a private house, for conversation or music.\n\nRisks\nSandstorm network access APIs may not work for the use case.\nIn most cases, things that run over plain HTTP requests should be able to work, but other network protocols tend to be nontrivial.\nSandstorm at current would neither support WebRTC or UDP traffic through the Powerbox, but it is uncertain what is needed to add it.\nRisk to migrate the Sandstorm ecosystem to Kubernetes helm system to match the devops status quo. Vargrant is not the status quo.\n\nProxying\nSome udp based proxying methods are known\n\nhttps://github.com/yyyar/gobetween for standalone\ncillium for kubernetes\nWebRTC ice, stun, turn\n\n\n\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n\nV-Sekai Developers\nWe package V-Sekai in Soiree party mode.\n\nWe start a single server of CockroachDB SQL database and not the default 3 server mode.\nWe provide installs of the Godot game engine client and server.\nWe re-arrange our elixir application Uro to work as a Sandstorm.io application.\n\n\n\nV-Sekai Packages\n\nV-Sekai provides a Server Download Package connecting via PowerBox.\nV-Sekai a Client Download Package connecting via PowerBox.\nV-Sekai a Uro Download Package connecting via PowerBox.\n\nThere is an open question if V-Sekai sandbox design works with powerbox.\n\n\nPlayer and Hosts\n\nIndividual hosts of Sandstorm.io can start their own grains of V-Sekai in Soiree mode.\nPlayers download the Godot Engine client and play.\n\n\n\nHosts\n\nMust provide a way to access the Godot Engine server and the Sandstorm server.\n\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nIt is not trivial and not a few lines to implement a distributed system for a developer.\n\n\nPositive Consequences\nSelf-hosted is a feature.\nWe can use Soiree Party mode to test V-Sekai.\n\n\nNegative Consequences\nMaybe too complicated for the developers.\n\n\nIs there a reason why this should be core and done by us?\nWe are investigating how to implement the Soiree Party mode.\n\n\nReferences\n\nhttps://www.cockroachlabs.com/\nhttps://github.com/V-Sekai/uro\nhttps://docs.sandstorm.io/en/latest/developing/powerbox/\nhttps://docs.sandstorm.io/en/latest/vagrant-spk/services/\nhttps://github.com/sandstorm-io/sandstorm\nhttps://github.com/mrmetaverse/soiree\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20221019-replicate-sync-100-000-entities.html",
-    "href": "decisions/20221019-replicate-sync-100-000-entities.html",
-    "title": "Proposed: Replicate sync 100’000 entities using a solution (Revision 1)",
+    "objectID": "decisions/20240326-heartstrings-vr.html#further-reading",
+    "href": "decisions/20240326-heartstrings-vr.html#further-reading",
+    "title": "Proposed: “Cafe Serenade” - A VR Dating Sim Experience",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai,fire,\nTags: V-Sekai,sync,view replication,\n\n\n\nDevelop a performant and robust (correctly and with liveness) network entity sync in V-Sekai.\nA client is one Godot Engine connection, it can view and change entities.\nThere are 100’000 networked entities in a city and we go from position a to position b in a loop in a mover with one or more attached cabins.\n\n\n\nThis document is a general problem statement.\n\n\n\n\nLarge sims!\n\n\n\n\n\n\n\n\nOption: Current V-Sekai replication\nRejection Reason: Can’t link servers\n\n\n\n\nEntity replication is not trivial.\n\n\n\nWe’re doing the networking layer.\n\n\n\n\n20221019-develop-a-replication-sync-for-100-000-entities.md\n20221016-v-sekai-view-replication.md\n20221014-networking-overhaul-proposal.md\nEfficientMethods_for_Improving_Scalability_and_Playability_of_Massively_Multiplayer_Online_Game_MMOG.pdf\n\n\n\nHow many clients can be in this simulation?\nThe state database should be smaller to avoid replication traffic on non-liveliness.\n\n\n\n\nThe calculation of who to pair and to find nearby or relevant players is a N^2 loop. Use better algorithms to lower O (N^2) into O (N log N).\nThe proposed solution can be solved in O (N log N).\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20221019-replicate-sync-100-000-entities.html#context-and-problem-statement",
-    "href": "decisions/20221019-replicate-sync-100-000-entities.html#context-and-problem-statement",
-    "title": "Proposed: Replicate sync 100’000 entities using a solution (Revision 1)",
+    "objectID": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html",
+    "href": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html",
+    "title": "Rejected: RabbitMQ RA vs SQLite on FoundationDB vs CockroachDB",
     "section": "",
-    "text": "Develop a performant and robust (correctly and with liveness) network entity sync in V-Sekai.\nA client is one Godot Engine connection, it can view and change entities.\nThere are 100’000 networked entities in a city and we go from position a to position b in a loop in a mover with one or more attached cabins."
+    "text": "We are at a critical juncture in our system design process. The primary question is whether to utilize the RabbitMQ RA system for distributed state machines, implement an SQLite cluster database built on top of FoundationDB, or use CockroachDB.\n\n\n\nThe core issue is identifying which options deliver the fastest and most reliable service. We require a system capable of handling high data volumes, maintaining consistency, and ensuring rapid response times, particularly when transferring 3D scene format tiles from Blender or Godot Engine.\n\n\n\n\n\nRabbitMQ RA system might be the better choice if speed and low latency are the primary concerns. It’s designed for high-throughput scenarios and can handle many messages without significant delays.\n\n\n\nAn SQLite cluster database on FoundationDB, while also fast, focuses more on providing ACID transactions and scalability. Therefore, it could be better if the workload involves complex transactions or needs to scale over time.\n\n\n\nCockroachDB is a cloud-native SQL database for building global, scalable cloud services that survive disasters. It provides ACID transactional consistency and versioned values as first-class features.\n\n\n\n\n\nAll three systems offer robust solutions for handling large amounts of data.\nRabbitMQ RA system provides a reliable messaging system focusing on processing speed and low latency.\nSQLite cluster database on FoundationDB offers a scalable solution with ACID transactions.\nCockroachDB is a cloud-native SQL database that provides global scalability and disaster recovery.\n\n\n\n\n\nRabbitMQ RA system may not be as scalable as the SQLite cluster database on FoundationDB or CockroachDB.\nSQLite cluster database on FoundationDB might have slower response times than the RabbitMQ RA system.\nCockroachDB, while offering strong consistency and scalability, might not be as fast as RabbitMQ RA system for certain workloads.\n\n\n\n\nWe could also consider other databases or messaging systems, but these three options seem the most promising given our specific needs and constraints.\n\n\n\nIn cases where data volume is low, the difference in performance between these three systems may not be significant.\n\n\n\nOur development team will decide whether to use any of these systems. We will also handle the implementation and maintenance of the chosen system.\n\n\n\nStatus: Rejected \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nEfficient_Methods_for_Improving_Scalability_and_Playability_of_Massively_Multiplayer_Online_Game_MMOG\n\nAria assisted with this analysis."
   },
   {
-    "objectID": "decisions/20221019-replicate-sync-100-000-entities.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20221019-replicate-sync-100-000-entities.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: Replicate sync 100’000 entities using a solution (Revision 1)",
+    "objectID": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#context",
+    "href": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#context",
+    "title": "Rejected: RabbitMQ RA vs SQLite on FoundationDB vs CockroachDB",
+    "section": "",
+    "text": "We are at a critical juncture in our system design process. The primary question is whether to utilize the RabbitMQ RA system for distributed state machines, implement an SQLite cluster database built on top of FoundationDB, or use CockroachDB."
+  },
+  {
+    "objectID": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#problem-statement",
+    "href": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#problem-statement",
+    "title": "Rejected: RabbitMQ RA vs SQLite on FoundationDB vs CockroachDB",
+    "section": "",
+    "text": "The core issue is identifying which options deliver the fastest and most reliable service. We require a system capable of handling high data volumes, maintaining consistency, and ensuring rapid response times, particularly when transferring 3D scene format tiles from Blender or Godot Engine."
+  },
+  {
+    "objectID": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#proposal",
+    "href": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#proposal",
+    "title": "Rejected: RabbitMQ RA vs SQLite on FoundationDB vs CockroachDB",
+    "section": "",
+    "text": "RabbitMQ RA system might be the better choice if speed and low latency are the primary concerns. It’s designed for high-throughput scenarios and can handle many messages without significant delays.\n\n\n\nAn SQLite cluster database on FoundationDB, while also fast, focuses more on providing ACID transactions and scalability. Therefore, it could be better if the workload involves complex transactions or needs to scale over time.\n\n\n\nCockroachDB is a cloud-native SQL database for building global, scalable cloud services that survive disasters. It provides ACID transactional consistency and versioned values as first-class features."
+  },
+  {
+    "objectID": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#benefits",
+    "href": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#benefits",
+    "title": "Rejected: RabbitMQ RA vs SQLite on FoundationDB vs CockroachDB",
+    "section": "",
+    "text": "All three systems offer robust solutions for handling large amounts of data.\nRabbitMQ RA system provides a reliable messaging system focusing on processing speed and low latency.\nSQLite cluster database on FoundationDB offers a scalable solution with ACID transactions.\nCockroachDB is a cloud-native SQL database that provides global scalability and disaster recovery."
+  },
+  {
+    "objectID": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#downsides",
+    "href": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#downsides",
+    "title": "Rejected: RabbitMQ RA vs SQLite on FoundationDB vs CockroachDB",
+    "section": "",
+    "text": "RabbitMQ RA system may not be as scalable as the SQLite cluster database on FoundationDB or CockroachDB.\nSQLite cluster database on FoundationDB might have slower response times than the RabbitMQ RA system.\nCockroachDB, while offering strong consistency and scalability, might not be as fast as RabbitMQ RA system for certain workloads."
+  },
+  {
+    "objectID": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#alternatives",
+    "href": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#alternatives",
+    "title": "Rejected: RabbitMQ RA vs SQLite on FoundationDB vs CockroachDB",
+    "section": "",
+    "text": "We could also consider other databases or messaging systems, but these three options seem the most promising given our specific needs and constraints."
+  },
+  {
+    "objectID": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#infrequent-use-case",
+    "href": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#infrequent-use-case",
+    "title": "Rejected: RabbitMQ RA vs SQLite on FoundationDB vs CockroachDB",
+    "section": "",
+    "text": "In cases where data volume is low, the difference in performance between these three systems may not be significant."
+  },
+  {
+    "objectID": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#implementation",
+    "href": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#implementation",
+    "title": "Rejected: RabbitMQ RA vs SQLite on FoundationDB vs CockroachDB",
+    "section": "",
+    "text": "Our development team will decide whether to use any of these systems. We will also handle the implementation and maintenance of the chosen system."
+  },
+  {
+    "objectID": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#status",
+    "href": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#status",
+    "title": "Rejected: RabbitMQ RA vs SQLite on FoundationDB vs CockroachDB",
+    "section": "",
+    "text": "Status: Rejected"
+  },
+  {
+    "objectID": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#decision-makers",
+    "href": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#decision-makers",
+    "title": "Rejected: RabbitMQ RA vs SQLite on FoundationDB vs CockroachDB",
     "section": "",
-    "text": "This document is a general problem statement."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20221019-replicate-sync-100-000-entities.html#positive-consequences",
-    "href": "decisions/20221019-replicate-sync-100-000-entities.html#positive-consequences",
-    "title": "Proposed: Replicate sync 100’000 entities using a solution (Revision 1)",
+    "objectID": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#tags",
+    "href": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#tags",
+    "title": "Rejected: RabbitMQ RA vs SQLite on FoundationDB vs CockroachDB",
     "section": "",
-    "text": "Large sims!"
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20221019-replicate-sync-100-000-entities.html#option-graveyard",
-    "href": "decisions/20221019-replicate-sync-100-000-entities.html#option-graveyard",
-    "title": "Proposed: Replicate sync 100’000 entities using a solution (Revision 1)",
+    "objectID": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#further-reading",
+    "href": "decisions/20240409-elixir-raft-vs-sqlite-fdb.html#further-reading",
+    "title": "Rejected: RabbitMQ RA vs SQLite on FoundationDB vs CockroachDB",
     "section": "",
-    "text": "Option: Current V-Sekai replication\nRejection Reason: Can’t link servers"
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nEfficient_Methods_for_Improving_Scalability_and_Playability_of_Massively_Multiplayer_Online_Game_MMOG\n\nAria assisted with this analysis."
   },
   {
-    "objectID": "decisions/20221019-replicate-sync-100-000-entities.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20221019-replicate-sync-100-000-entities.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Replicate sync 100’000 entities using a solution (Revision 1)",
+    "objectID": "index.html",
+    "href": "index.html",
+    "title": "V-Sekai Social VR",
     "section": "",
-    "text": "Entity replication is not trivial."
+    "text": "V-Sekai Social VR\n\n\n\n\n\n\nNote\n\n\n\n\n“V-Sekai” (pronounced vee-say-kai) stands for virtual, and in Japanese, “Sekai” means “World”.\n\n\n\n\nChit-Chat on Discord.\nEmbark to our world at v-sekai.org.\nFollow us on Twitter.\nContribute on GitHub here.\nReach Out to SaracenOne, Lyuma, or Fire."
   },
   {
-    "objectID": "decisions/20221019-replicate-sync-100-000-entities.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20221019-replicate-sync-100-000-entities.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Replicate sync 100’000 entities using a solution (Revision 1)",
+    "objectID": "authors.html",
+    "href": "authors.html",
+    "title": "V-Sekai Manual Authors",
     "section": "",
-    "text": "We’re doing the networking layer."
+    "text": "V-Sekai Manual Authors\n\nK. S. Ernest (iFire) Lee (fire)\nLyuma\nMalekiRe Malek\nGDQuest"
   },
   {
-    "objectID": "decisions/20221019-replicate-sync-100-000-entities.html#references",
-    "href": "decisions/20221019-replicate-sync-100-000-entities.html#references",
-    "title": "Proposed: Replicate sync 100’000 entities using a solution (Revision 1)",
+    "objectID": "changelog.html",
+    "href": "changelog.html",
+    "title": "Changes to V-Sekai",
     "section": "",
-    "text": "20221019-develop-a-replication-sync-for-100-000-entities.md\n20221016-v-sekai-view-replication.md\n20221014-networking-overhaul-proposal.md\nEfficientMethods_for_Improving_Scalability_and_Playability_of_Massively_Multiplayer_Online_Game_MMOG.pdf\n\n\n\nHow many clients can be in this simulation?\nThe state database should be smaller to avoid replication traffic on non-liveliness."
+    "text": "All notable changes to this project will be documented in this file.\nThe format is based on Keep a Changelog, and this project does not adhere to Semantic Versioning.\nAdded for new features.\nChanged for changes in existing functionality.\nDeprecated for soon-to-be removed features.\nRemoved for now removed features.\nFixed for any bug fixes.\nSecurity in case of vulnerabilities.\n\n\n\n\n\n\n   \n     \n     \n       Order By\n       Default\n         \n          Title\n        \n     \n  \n    \n      \n      \n    \n\n\n\n\n\nTitle\n\n\n\n\n\n\nV-Sekai Changelog - October 2024\n\n\n\n\nV-Sekai Changelog - September 2024\n\n\n\n\nV-Sekai Changelog - July 2024\n\n\n\n\nSpecial Notice: V-Sekai 2023-2024\n\n\n\n\nV-Sekai Changelog - June 2024\n\n\n\n\nV-Sekai Changelog - May 2024\n\n\n\n\nV-Sekai Changelog - March 2024\n\n\n\n\nV-Sekai Changelog - February 2024\n\n\n\n\nV-Sekai Changelog - January 2024\n\n\n\n\nV-Sekai Changelog - December 2023\n\n\n\n\nV-Sekai Changelog - November 2023\n\n\n\n\nV-Sekai Changelog - October 2023\n\n\n\n\nV-Sekai Changelog - September 2023\n\n\n\n\nV-Sekai Changelog - August 2023\n\n\n\n\nV-Sekai Changelog - July 2023\n\n\n\n\nV-Sekai Changelog - 2023-06\n\n\n\n\nV-Sekai Changelog - 2023-05\n\n\n\n\nV-Sekai Changelog - 2023-03\n\n\n\n\nV-Sekai Changelog - 2023-02\n\n\n\n\nV-Sekai Changelog - 2023-01\n\n\n\n\nV-Sekai Changelog - 2022-12\n\n\n\n\nV-Sekai Changelog - 2022-11\n\n\n\n\nV-Sekai Changelog - 2022-10\n\n\n\n\nV-Sekai Changelog - 2022-09\n\n\n\n\nV-Sekai Changelog - 2022-08\n\n\n\n\nV-Sekai Changelog - 2022-06\n\n\n\n\nV-Sekai Changelog - 2022-05\n\n\n\n\nV-Sekai Changelog - 2022-04\n\n\n\n\nV-Sekai Changelog - 2022-03\n\n\n\n\nV-Sekai Changelog - 2022-02\n\n\n\n\nV-Sekai Changelog - 2022-01\n\n\n\n\nV-Sekai Changelog - 2021-11\n\n\n\n\nV-Sekai Changelog - 2021-10\n\n\n\n\nV-Sekai Changelog - 2021-09\n\n\n\n\nV-Sekai Changelog - 2021-08\n\n\n\n\nV-Sekai Changelog - 2021-07\n\n\n\n\nV-Sekai Changelog - 2021-06\n\n\n\n\nV-Sekai Changelog - 2021-05\n\n\n\n\nV-Sekai Changelog - 2021-04\n\n\n\n\n\nNo matching items"
   },
   {
-    "objectID": "decisions/20221019-replicate-sync-100-000-entities.html#math",
-    "href": "decisions/20221019-replicate-sync-100-000-entities.html#math",
-    "title": "Proposed: Replicate sync 100’000 entities using a solution (Revision 1)",
+    "objectID": "decisions.html",
+    "href": "decisions.html",
+    "title": "Decisions of V-Sekai",
     "section": "",
-    "text": "The calculation of who to pair and to find nearby or relevant players is a N^2 loop. Use better algorithms to lower O (N^2) into O (N log N).\nThe proposed solution can be solved in O (N log N)."
+    "text": "Order By\n       Default\n         \n          Title\n        \n     \n  \n\n\n\n\n\nTitle\n\n\nReading Time\n\n\nFile Name\n\n\n\n\n\n\nProposed: Template\n\n\n1 min\n\n\npresent-proposal-template.md\n\n\n\n\nAccepted: AI Assisted Style Guide\n\n\n2 min\n\n\nai-assisted-proposal-style-guide.md\n\n\n\n\nProposal: Use Data Tables for Godot Constraints\n\n\n2 min\n\n\n20241028-use-data-tables-for-godot-constraints.md\n\n\n\n\nProposed: Reduce Size Difference Between Capsules and Mesh Volume\n\n\n2 min\n\n\n20241019-reduce-size-difference-between-capsules-and-mesh-volume.md\n\n\n\n\nProposed: Evaluate three proposals for V-Sekai content distribution\n\n\n3 min\n\n\n20241016-instantiating-v-sekai-content.md\n\n\n\n\nProposed: Editing Character Body Bone Constraints in Immersive Mode\n\n\n8 min\n\n\n20241014-xr-interface-for-rigging.md\n\n\n\n\nProposed: Basic Real-Time Interaction for Character and World Scenes\n\n\n5 min\n\n\n20241014-basic-realtime-interaction.md\n\n\n\n\nProposed: Updater No-Op Implementation Using Velopack\n\n\n2 min\n\n\n20241014-app-updater.md\n\n\n\n\nProposed: Recovering MakeHuman Parameters Using Depth Map Comparison with Godot Engine\n\n\n3 min\n\n\n20241011-recovering-makehuman-parameters.md\n\n\n\n\nAccepted: Restoring Default User Directory Structure in Windows 11\n\n\n2 min\n\n\n20241006-restore-onedrive-shortcut-overrides.md\n\n\n\n\nProposed: Small V-Sekai Creation Tools\n\n\n2 min\n\n\n20241001-small-game-tools.md\n\n\n\n\nAccepted: Godot Engine XR Elite HMD Conference Setup\n\n\n3 min\n\n\n20240914-godot-engine-xr-elite-conference-setup.md\n\n\n\n\nProposed: Revised Tracker Configuration and Constraints for HTC VIVE XR Elite\n\n\n3 min\n\n\n20240905-revised-tracker-configuration-and-constraints.md\n\n\n\n\nProposed: Transition to Dokku from Kubernetes Proposal\n\n\n2 min\n\n\n20240830-use-dokku-to-host-vsk-backend.md\n\n\n\n\nAccepted: PCI-E Lane Depletion and Thunderbolt 4 Issues\n\n\n3 min\n\n\n20240830-pcie-lane-depletion-thunderbolt-4-issues.md\n\n\n\n\nProposed: FFMPEG Wave/Mic and Speaker/Play\n\n\n5 min\n\n\n20240824-ffmpeg-wav-mic-speaker-play.md\n\n\n\n\nProposed: Improving Connectivity for Valve StreamVR Light House Dongles\n\n\n2 min\n\n\n20240810-steamvr-dongles-separate.md\n\n\n\n\nProposal: Core V-Sekai Scripting with Wasm\n\n\n4 min\n\n\n20240717-core-vsekai-scripting.md\n\n\n\n\nProposed: Create a Conceptual Model of VRChat Networking\n\n\n47 min\n\n\n20240715-vrchat-networking-mental-model.md\n\n\n\n\nProposed: Use shrink wrap blender modifier to fit\n\n\n2 min\n\n\n20240712-use-shrinkwrap-blender-modiifer-to-fit.md\n\n\n\n\nProposed: Networking PCVR with the Web\n\n\n3 min\n\n\n20240710-web-and-pcvr-networking.md\n\n\n\n\nProposed: Use WebRTC to Native to Interop with Godot Engine\n\n\n2 min\n\n\n20240710-use-webrtc-to-native-interop.md\n\n\n\n\nProposed: Use Godot Engine Web Threaded\n\n\n3 min\n\n\n20240710-use-godot-engine-web-threaded.md\n\n\n\n\nProposed: Focus on PCVR and the Web\n\n\n2 min\n\n\n20240710-platform-focus-on-pcvr-and-web.md\n\n\n\n\nProposed: Convert Blender CC0 Base Mesh to Godot Engine T-Pose\n\n\n4 min\n\n\n20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.md\n\n\n\n\nProposed: Art Direction in V-Sekai Process\n\n\n2 min\n\n\n20240710-art-direction-in-vsekai.md\n\n\n\n\nProposed: A Wired-First Strategy for PCVR\n\n\n2 min\n\n\n20240709-wired-first.md\n\n\n\n\nProposed: Set Nvidia Watt Limit with Anwave\n\n\n2 min\n\n\n20240709-anwave-set-nvidia-watt-limit.md\n\n\n\n\nProposed: V-Sekai: My Life as a Princess\n\n\n5 min\n\n\n20240708-vsekai-my-life-as-a-queen.md\n\n\n\n\nProposed: Maximum Streaming Bill of Materials Setup for Motion Capture\n\n\n8 min\n\n\n20240706-motion-capture-bill-of-materials.md\n\n\n\n\nProposal: RPG Town in V-Sekai\n\n\n3 min\n\n\n20240705-rpg_town.md\n\n\n\n\nProposed: Use motion transformers for motion prediction\n\n\n2 min\n\n\n20240630-use-motion-transformers-for-prediction.md\n\n\n\n\nSuperceded: RISCV Binaries as Shared Libraries\n\n\n3 min\n\n\n20240627-gdextension-as-libriscv.md\n\n\n\n\nProposed: Every Commit Push Pass Cicd\n\n\n2 min\n\n\n20240627-every-commit-push-pass-cicd.md\n\n\n\n\nProposed: Update python3 macOS Certificates\n\n\n3 min\n\n\n20240626-update-python3-macos-certicates.md\n\n\n\n\nProposed: Why did we build “Uro”?\n\n\n3 min\n\n\n20240623-what-is-uro-backend.md\n\n\n\n\nProposed: Talk Length Game Prototypes\n\n\n2 min\n\n\n20240623-talk-length-prototypes.md\n\n\n\n\nProposal: Only Save Tools in Our CDN\n\n\n2 min\n\n\n20240623-only-save-tools-in-our-cdn.md\n\n\n\n\nProposed: Use GitHub Actions and Digital Ocean Spaces for a V-Sekai Launcher\n\n\n2 min\n\n\n20240623-do-cdn-for-launcher.md\n\n\n\n\nProposed: Create a process for testing V-Sekai.\n\n\n2 min\n\n\n20240622-process-for-testing-vsekai.md\n\n\n\n\nAccepted: GoCD Agent Docker Image Update\n\n\n2 min\n\n\n20240622-gocd-agent-docker-image-update.md\n\n\n\n\nProposed: Build V-Sekai editor for many platforms\n\n\n2 min\n\n\n20240622-build-for-many-platforms.md\n\n\n\n\nProposed: Command Traces with Server Backend\n\n\n1 min\n\n\n20240621-proposal-template copy.md\n\n\n\n\nProposed: Image Captioning Tool\n\n\n2 min\n\n\n20240621-caption-photos-for-cicd.md\n\n\n\n\nProposed: Transforming Schedule DAG into a Left-child Right-sibling Binary Tree\n\n\n3 min\n\n\n20240618-schedule-as-binary-tree.md\n\n\n\n\nProposed: 4 Player Test V-Sekai\n\n\n2 min\n\n\n20240618-4-player-test-vsekai.md\n\n\n\n\nProposed: Triangle to Quad Mesh Dataset Creation\n\n\n2 min\n\n\n20240616-request-for-quad-mesh-dataset.md\n\n\n\n\nProposed: Explain the concept of Mesh Transformers\n\n\n2 min\n\n\n20240615-what-is-mesh-transformers.md\n\n\n\n\nProposed: Dataset Scaling for Training Mesh Transformer\n\n\n2 min\n\n\n20240613-training-dataset.md\n\n\n\n\nProposed: Dataset Creation with CSG\n\n\n3 min\n\n\n20240613-training-dataset-creation-with-csg.md\n\n\n\n\nProposed: Modify the Mesh Transformer for Quads\n\n\n2 min\n\n\n20240613-modifying-the-mesh-transformer-for-quads.md\n\n\n\n\nProposed: Training Mesh Transformer for 3D Avatar Creation\n\n\n3 min\n\n\n20240613-1k-quad-limit.md\n\n\n\n\nProposed: Managing Multiple Training Runs in Separate Pods\n\n\n2 min\n\n\n20240611-test-1x-and-4x.md\n\n\n\n\nProposed: Switch learning rate to be lower.\n\n\n2 min\n\n\n20240611-lower-learning-rate.md\n\n\n\n\nAccepted: Better Skeleton Merge with Robust Skin Weight Transfer\n\n\n6 min\n\n\n20240608-skin-weight-transfer-skeleton-merge.md\n\n\n\n\nAccepted: Use the Humanoid Profile for Character Motion Mirroring\n\n\n5 min\n\n\n20240608-for-skeleton-mirroring-use-the-godot-humanoid.md\n\n\n\n\nProposal: Sustainable Version Management for Godot Engine in V-Sekai\n\n\n3 min\n\n\n20240605-sustainable-version-management-for-godot-engine-in-v-sekai.md\n\n\n\n\nProposed: Improve the Godot Ecosystem\n\n\n3 min\n\n\n20240529-improve-godot-import-ecosystem.md\n\n\n\n\nProposed: Godot Engine as Wasm Importer\n\n\n2 min\n\n\n20240528-pipeline-godot-wasm-importer.md\n\n\n\n\nProposed: Draft WebRTC Relay Test\n\n\n1 min\n\n\n20240522-webrtc-relay-test.md\n\n\n\n\nDraft: shadermotion to BVH\n\n\n2 min\n\n\n20240522-shader-motion-to-bvh.md\n\n\n\n\nDraft: View the worlds and interact with people in VR without being in VR via a Discord Inward Portal\n\n\n2 min\n\n\n20240522-discord-inworld-portal.md\n\n\n\n\nDraft: Notify community members and users about activity and updates via a Discord bot\n\n\n3 min\n\n\n20240522-discord-bot.md\n\n\n\n\nAccepted: Wasm Cache Incident Report\n\n\n2 min\n\n\n20240511-wasm-cache-incident.md\n\n\n\n\nRejected: VR Game with 80 Players and One World Server\n\n\n2 min\n\n\n20240511-review-80-vr.md\n\n\n\n\nProposed: Can I use V-Sekai for 3d assets & 3d extensions?\n\n\n2 min\n\n\n20240502-where-can-I-use-gltf.md\n\n\n\n\nProposed: Launching the mvsqlite rdbms server\n\n\n4 min\n\n\n20240502-mvsqlite-launchd.md\n\n\n\n\nProposed: Stress Testing Godot Engine’s Networking System\n\n\n3 min\n\n\n20240502-mesh-object-sync-benchmark.md\n\n\n\n\nProposed: Process the glTF2 input file and return it as is\n\n\n2 min\n\n\n20240502-membrane-framework-identity-post.md\n\n\n\n\nProposed: Enable Windows 11 Installation on Older Computers\n\n\n2 min\n\n\n20240502-install-windows-on-older-computers.md\n\n\n\n\nProposed: Workflows for 3D Model Conversion\n\n\n3 min\n\n\n20240502-gltf-fbx-tscn-vrm.md\n\n\n\n\nProposed: Stuck / Recharge Cycle\n\n\n2 min\n\n\n20240425-recharge-cycle.md\n\n\n\n\nProposed: ChatGPT-4 Based Proposal Prompt System\n\n\n2 min\n\n\n20240425-proposal-prompt-system.md\n\n\n\n\nAccepted: Prioritizing Valve Controllers Over Meta Quest 3 Controllers\n\n\n2 min\n\n\n20240424-reset-steamvr-controllers.md\n\n\n\n\nAccepted: Building a Metaverse with Glue Mechanic in V-Sekai\n\n\n2 min\n\n\n20240423-building-metaverse-with-glue-mechanic.md\n\n\n\n\nProposed: Town Courier\n\n\n3 min\n\n\n20240418-college-quest.md\n\n\n\n\nProposed: Implementing a 3D Previewer for GLTF with XMP Metadata\n\n\n2 min\n\n\n20240416-previewer-upload-gltf-to-glb.md\n\n\n\n\nProposed: Train quad-based Meshgpt within constraints\n\n\n3 min\n\n\n20240413-training-quad-based-meshgpt-with-40gb-vram.md\n\n\n\n\nProposed: Calling Open Source LLM with Aria\n\n\n2 min\n\n\n20240413-calling-opensource-llm-with-aria.md\n\n\n\n\nProposed: Implementing a 3D Multiplayer Movement System with Parented Objects and Inventory Management\n\n\n3 min\n\n\n20240411-multiplayer-movement-with-parented-obejcts.md\n\n\n\n\nRejected: Binding GDExtension to a C-like Language for Libgodot to Implement a Distributed Simulation\n\n\n2 min\n\n\n20240411-elixir-libgodot-zig.md\n\n\n\n\nProposed: Use Bundlex for Binding GDExtension to Elixir for Libgodot to Implement a Distributed Simulation\n\n\n2 min\n\n\n20240411-elixir-libgodot-bundlex.md\n\n\n\n\nProposed: Implementing Elixir Data Models for Memory, Local, Bulk, and Global Storage\n\n\n3 min\n\n\n20240410-data-storage-elixir.md\n\n\n\n\nRejected: RabbitMQ RA vs SQLite on FoundationDB vs CockroachDB\n\n\n3 min\n\n\n20240409-elixir-raft-vs-sqlite-fdb.md\n\n\n\n\nAccepted: “Sunny Park” Test Case for 3D Tile Sync\n\n\n2 min\n\n\n20240409-crud-godot-tiles.md\n\n\n\n\nAccepted: Focusing on PCVR vs Android Build vs Web Build\n\n\n2 min\n\n\n20240407-pcvr-vs-standalone.md\n\n\n\n\nProposed: Web-Based Exploration of V-Sekai\n\n\n2 min\n\n\n20240406-web-based-explore.md\n\n\n\n\nProposed: Provide a V-Sekai Starter Kit\n\n\n2 min\n\n\n20240406-itch-github-actions.md\n\n\n\n\nProposed: Material Shader Graphic Shirt with Sharp Edges\n\n\n3 min\n\n\n20240401-shader-graphic.md\n\n\n\n\nProposed: VRC and VRM compatibility\n\n\n4 min\n\n\n20240331-vrc-vrm-compatibility.md\n\n\n\n\nAccepted: k8s on harvester hci\n\n\n4 min\n\n\n20240330-k8s-harvester-hci.md\n\n\n\n\nProposed: Hyperv windows Harvester Test\n\n\n2 min\n\n\n20240330-hyperv-harvester-test.md\n\n\n\n\nProposed: Integrating Helm for Kubernetes Runner Installation with S3 Cache\n\n\n4 min\n\n\n20240330-gitlab-helm.md\n\n\n\n\nProposed: CI/CD Setup with Docker and Other Platforms\n\n\n3 min\n\n\n20240330-cicd-gitlab.md\n\n\n\n\nProposed: Installing Helm Chart from a Git Repository using Rancher\n\n\n2 min\n\n\n20240330-bitnami-rancher-helm-catalog.md\n\n\n\n\nProposed: V-Sekai Setup as a Ready-to-Go Kit\n\n\n2 min\n\n\n20240329-ready-to-go-kit-windows-11.md\n\n\n\n\nProposed: Teaching Large Language Models (LLMs) with Goal-Task Planners\n\n\n2 min\n\n\n20240326-verifying-and-finetuning-plans.md\n\n\n\n\nProposed: “Cafe Serenade” - A VR Dating Sim Experience\n\n\n3 min\n\n\n20240326-heartstrings-vr.md\n\n\n\n\nProposed: for 3d Asset Schema Design and Database Backend Selection\n\n\n2 min\n\n\n20240325-table-avatar-embedded-xmp.md\n\n\n\n\nProposed: Synchronizing Blender and FDB-SQLite for Proxy Movement\n\n\n2 min\n\n\n20240325-fdb-sqlite-blender-godot.md\n\n\n\n\nProposed: V-Sekai Implementation Using SLC Framework\n\n\n2 min\n\n\n20240324-v-sekai-as-slc.md\n\n\n\n\nProposed: Real-Time Motion Capture and Animation Synchronization\n\n\n2 min\n\n\n20240314-live-collab.md\n\n\n\n\nProposed: Implement Ra in V-Sekai\n\n\n1 min\n\n\n20240307-rabbitmq-ra.md\n\n\n\n\nProposed: V-Sekai Game Launcher\n\n\n3 min\n\n\n20240305-v-sekai-launcher.md\n\n\n\n\nProposed VRM mtoon in Substance Designer\n\n\n32 min\n\n\n20240218-vrm-substance-editor.md\n\n\n\n\nAccepted: VRM Acronym Correction\n\n\n1 min\n\n\n20240218-vrm-acronym-correction.md\n\n\n\n\nProposed: Blender to Godot API Conversion\n\n\n2 min\n\n\n20240218-blender-to-godot.md\n\n\n\n\nProposed: for using workloads to emulate the usage patterns\n\n\n2 min\n\n\n20240217-workload-benchmarking.md\n\n\n\n\nProposed: Adoption of Intended Effort Versioning (EffVer) in V-Sekai\n\n\n2 min\n\n\n20240217-intended-effort-versioning.md\n\n\n\n\nProposed: Implementation of Essential Tuple Normalization Form (ETNF) for relational databases (rdbms, sql)\n\n\n7 min\n\n\n20240217-essential-typle-normalization-form.md\n\n\n\n\nProposed: Comprehensive Documentation for V-Sekai\n\n\n2 min\n\n\n20240217-documentation-guidelines.md\n\n\n\n\nProposed: Container2Wasm Integration in V-Sekai\n\n\n2 min\n\n\n20240217-container-2-wasm.md\n\n\n\n\nProposed: Enhancing Avatar Expressiveness with AI-Generated Blend Shapes\n\n\n2 min\n\n\n20240215-avatar-customization-with-ai-facial-expressions.md\n\n\n\n\nProposed: Urban Navigator: The City Unveiled\n\n\n2 min\n\n\n20240127-urban-explorer-gdc-2024-sample.md\n\n\n\n\nProposed: Macos cicd setup.\n\n\n4 min\n\n\n20240121-mac-setup.md\n\n\n\n\nProposed: Elixir Livebook on Fedora 39\n\n\n3 min\n\n\n20240121-livebook-fedora-install.md\n\n\n\n\nProposed: Installing Tailscale on Linux Fedora 39\n\n\n2 min\n\n\n20240121-install-tailscale.md\n\n\n\n\nProposed: Easy Diffusion AI Setup on Linux Systems\n\n\n2 min\n\n\n20240121-easy-diffusion-fedora-install.md\n\n\n\n\nProposed: Advanced VR Armature System for V-Sekai\n\n\n2 min\n\n\n20240120-vr-armature-system.md\n\n\n\n\nProposed: Provide Pivot Painting Resources\n\n\n1 min\n\n\n20240117-pivot-painting.md\n\n\n\n\nProposed: Camera matching with fSpy.\n\n\n2 min\n\n\n20240111-fspy.md\n\n\n\n\nDraft: Fit Clothing on Humans Without Tearing\n\n\n2 min\n\n\n20240111-fit-clothing-on-humans-without-tearing.md\n\n\n\n\nProposed: Magical Girls College Manager Simulator\n\n\n3 min\n\n\n20240110-magical-girls-college-novel.md\n\n\n\n\nProposed: 1 Meter Cubed 128 Quantized\n\n\n2 min\n\n\n20240105-1-meter-128-quantize.md\n\n\n\n\nDeprecated: Valid configuration of Spatiallabs and Openxr\n\n\n2 min\n\n\n20231230-spatiallabs-openvr.md\n\n\n\n\nProposed: Choosing a terminal emulator for Windows\n\n\n2 min\n\n\n20231229-mRemoteNG.md\n\n\n\n\nProposed: Byobu terminal multiplexer\n\n\n2 min\n\n\n20231229-byobu.md\n\n\n\n\nProposed: V-Sekai: Gateways to Virtual Worlds\n\n\n2 min\n\n\n20231228-v-sekai-slogan.md\n\n\n\n\nProposed: Use the “Punchline Reports” Method\n\n\n2 min\n\n\n20231227-punchline-reports.md\n\n\n\n\nProposed: Blue Green new shadows for new avatars\n\n\n2 min\n\n\n20231227-blue-green-shadows.md\n\n\n\n\nProposed: Hardsurface vs Organic\n\n\n2 min\n\n\n20231226-furniture-vs-organic.md\n\n\n\n\nProposed: Mesh Transformer Expressive Facial Features\n\n\n2 min\n\n\n20231225-mesh-transformer-facial-features.md\n\n\n\n\nProposed: Mesh Transformer Clothing\n\n\n2 min\n\n\n20231225-mesh-transformer-clothing.md\n\n\n\n\nProposed: MaterialX try two.\n\n\n2 min\n\n\n20231218-mtlx-try-two.md\n\n\n\n\nProposed: Automating Game Testing Process Using Appium 2\n\n\n3 min\n\n\n20231209-appium-testing-win11.md\n\n\n\n\nProposed: Appium Testing for Windows 11\n\n\n2 min\n\n\n20231209-appium-testing-fbx-to-gltf.md\n\n\n\n\nProposed: Triangle Meshes Inferencing with MeshRWKV\n\n\n5 min\n\n\n20231203-mesh-rwkv.md\n\n\n\n\nDraft: Initial Training of the MeshRWVK Model\n\n\n2 min\n\n\n20231203-mesh-rwkv-test-metrics.md\n\n\n\n\nDraft: GraphSAGE Embedding Algorithm Explanation\n\n\n4 min\n\n\n20231203-graphsage-embedding-generation.md\n\n\n\n\nProposed: Seamless Integration of XR Tracking in Godot Engine\n\n\n3 min\n\n\n20231201-xr-hands-animation-node.md\n\n\n\n\nProposed: Headless Launcher Backend with Elixir and Server-Side CockroachDB\n\n\n7 min\n\n\n20231201-headless-launcher-backend.md\n\n\n\n\nAccepted: Benchmarking Network Performance for Scalable Multiplayer in Godot\n\n\n3 min\n\n\n20231127-performance-test.md\n\n\n\n\nAccepted: V-Sekai 2023-11-26 Report\n\n\n3 min\n\n\n20231126-v-sekai-report.md\n\n\n\n\nSuperseded: V-Sekai 2023-11-25 Report\n\n\n4 min\n\n\n20231125-v-sekai-report.md\n\n\n\n\nProposed: Upload Creative Commons FBX Test Files for Enhanced LOD Optimization in V-Sekai\n\n\n2 min\n\n\n20231114-upload-creative-commons-fbx-test-files.md\n\n\n\n\nProposed: Enhancing VR Book Reading through SVG Optimization\n\n\n2 min\n\n\n20231114-maintain-svgcleaner.md\n\n\n\n\nProposed: Defining the List of Godot Types in Elixir Godot Parsers\n\n\n2 min\n\n\n20231114-elixir-definition-of-godot-types.md\n\n\n\n\nProposed: Validator Service for V-Sekai\n\n\n2 min\n\n\n20231112-validation-service.md\n\n\n\n\nProposed: Effective V-Sekai project archival strategy\n\n\n3 min\n\n\n20231112-archive-projects.md\n\n\n\n\nProposed: Evaluate AYON pipeline platform on hosted cloud services\n\n\n3 min\n\n\n20231111-ayon-evaluation.md\n\n\n\n\nAccepted: V-Sekai dependencies\n\n\n3 min\n\n\n20231110-v-sekai-dependencies.md\n\n\n\n\nProposed: Efficient Training of LLMs in V-Sekai\n\n\n2 min\n\n\n20231110-efficient-llm-training.md\n\n\n\n\nAccepted: Overcoming the Blender T-Pose Limitation with Documentation\n\n\n2 min\n\n\n20231110-blender-manual-t-pose.md\n\n\n\n\nProposed: Enhancing V-Sekai x Godot Engine x AYON for a Superior Workflow\n\n\n2 min\n\n\n20231110-better-pipeline-tools.md\n\n\n\n\nProposed: Streamlining Game Development with AI-Based Aria’s Guidance\n\n\n2 min\n\n\n20231110-ai-based-outlier-detection.md\n\n\n\n\nProposed: Character Customization Discord Bot PoC for V-Sekai\n\n\n4 min\n\n\n20231109-discord-polygonjs-generator.md\n\n\n\n\nProposed: Creation of an ‘Ask V-Sekai’ Chatbot Using Vercel, OpenAI, and Neon PostgreSQL\n\n\n2 min\n\n\n20231108-v-sekai-chat-bot.md\n\n\n\n\nProposed: PostgreSQL bytea Storage Optimization for V-Sekai’s Edge CDN\n\n\n2 min\n\n\n20231108-postgres-bytea-optimizations.md\n\n\n\n\nProposed: “Freedom is in a future that you did not have in the past” - A Game Development Philosophy from NieR:Automata\n\n\n3 min\n\n\n20231108-nier-automata-world-expansion.md\n\n\n\n\nProposed: Development of a Community Polling Discord Bot Using Vercel and Neon PostgreSQL\n\n\n2 min\n\n\n20231108-neon-vercel-functions-toy-problem.md\n\n\n\n\nProposed: Adopting Neon for a More Manageable Backend at V-Sekai\n\n\n1 min\n\n\n20231108-neon-postgresql.md\n\n\n\n\nProposed: Adopting Neon’s Bottomless Storage with S3-Compatible Object Store for Edge CDN Data Management\n\n\n2 min\n\n\n20231108-neon-1-gb-scene-storage.md\n\n\n\n\nProposed: Enhancing V-Sekai Through Effective Documentation\n\n\n2 min\n\n\n20231108-munich-godot-engine-conference.md\n\n\n\n\nProposed: Ansible Server Provisioning\n\n\n2 min\n\n\n20231108-ansible-new-server-provisioning.md\n\n\n\n\nProposed: PDF to SVG Conversion for VR Books\n\n\n2 min\n\n\n20231105-pdf-embed-raster-svg-vr.md\n\n\n\n\nRejected: Merge Scene Tool for Godot Editor with FlatBuffer-based JSON Serialization\n\n\n2 min\n\n\n20231104-flatbuffer_packed_scenes.md\n\n\n\n\nAccepted: Write List of Github Pull Requests for Review\n\n\n6 min\n\n\n20231027-write-a-list-of-github-pull-requests.md\n\n\n\n\nProposed: DreamCraft3D - A Hierarchical 3D Content Generation Method\n\n\n2 min\n\n\n20231027-dreamcraft3d-workflow.md\n\n\n\n\nProposed: Drawing Concept to Blockout\n\n\n2 min\n\n\n20231027-drawing-concept-to-blockout.md\n\n\n\n\nProposed: Build a Cozy Apartment in VR for V-Sekai\n\n\n2 min\n\n\n20231027-apartment-building-vr.md\n\n\n\n\nProposed: Solve Blender versions by locking LTS versions on Blender (3.6)\n\n\n1 min\n\n\n20231026-blender-steam-beta-version.md\n\n\n\n\nProposed: Implementing Advanced Training Simulators in V-Sekai\n\n\n2 min\n\n\n20231024-training-simulators.md\n\n\n\n\nProposed: Enhancing Task-Specific Model Performance through Fine-Tuning with Axolotl\n\n\n2 min\n\n\n20231024-finetuning-workflow.md\n\n\n\n\nProposed: Navigating New Horizons: A Proposal for Expanding Exploration in V-Sekai\n\n\n2 min\n\n\n20231022-hover-to-ocean-game.md\n\n\n\n\nProposed: Llama CPP AI Model NPC\n\n\n2 min\n\n\n20231020-llama-cpp-mistral-npc.md\n\n\n\n\nProposed: Valve VR Ecosystem with Quest 3\n\n\n2 min\n\n\n20231019-quest3-mocap-steam-lighthouse.md\n\n\n\n\nProposed: Streamlining V-Sekai Performance\n\n\n2 min\n\n\n20230922-spacetime-shadow-shards-sync.md\n\n\n\n\nProposed: Use embedding search with Godot Engine projects\n\n\n2 min\n\n\n20230920-godot-project-search.md\n\n\n\n\nProposed: Challenges that need to be addressed in V-Sekai\n\n\n2 min\n\n\n20230913-V-Sekai-bugs.md\n\n\n\n\nProposed: Address Screen Resolution Compatibility Issues\n\n\n1 min\n\n\n20230912-target-most-popular-resolution.md\n\n\n\n\nProposed: Improving xr grid with new enhancements\n\n\n1 min\n\n\n20230911-xr-grid-with-drawing.md\n\n\n\n\nDraft: XPR in Elixir\n\n\n3 min\n\n\n20230911-xpr.exs.md\n\n\n\n\nProposed: Implementing Semantic Versioning for Alpha Releases in V-Sekai\n\n\n2 min\n\n\n20230911-first-alpha-tag.md\n\n\n\n\nDraft: Can Poly Green Coords extend to 3d?\n\n\n1 min\n\n\n20230911-can-poly-green-coords-extend-to-3d.md\n\n\n\n\nDraft: Translation/Transcription Badge with GGML’s Whisper\n\n\n3 min\n\n\n20230908-bendable-screen-generative-assistant-ggml.md\n\n\n\n\nRejected: Enabling VRM to Blender Conversion with Cloud GPUs and replicate.com\n\n\n3 min\n\n\n20230903-replicate-vrm-transform.md\n\n\n\n\nAccepted: Enhancing Map Uploads\n\n\n2 min\n\n\n20230831-fixing-upload-limits.md\n\n\n\n\nAccepted: Fix menus in-game\n\n\n1 min\n\n\n20230831-fixing-menus.md\n\n\n\n\nProposed: Expanding Worlds\n\n\n4 min\n\n\n20230830-generating-v-sekai-worlds.md\n\n\n\n\nProposed: Improving VR Experience\n\n\n2 min\n\n\n20230830-better-object-pick.md\n\n\n\n\nProposed: Integrating Backend Services\n\n\n2 min\n\n\n20230830-better-backend-services.md\n\n\n\n\nProposed: OMIFest 2023 - The Call\n\n\n5 min\n\n\n20230829-omifest-2023.md\n\n\n\n\nAccepted: Use opensubdiv for level of detail\n\n\n2 min\n\n\n20230824-subdiv-for-lods.md\n\n\n\n\nProposed: Developing a Unified Model for Speech-to-Facial Shape Generation Using Outlines 〰 Library\n\n\n4 min\n\n\n20230823-speech-to-blendshapes.md\n\n\n\n\nProposed: Following Tracks: Enhancing VR Train Station Simulation in V-Sekai using Godot Engine\n\n\n2 min\n\n\n20230819-train-game.md\n\n\n\n\nRejected: Rewriting Mixer Broadcaster Into Membrane Framework Pipelines\n\n\n3 min\n\n\n20230813-mixer-broadcaster-into-membrane-framework copy.md\n\n\n\n\nProposed: Transitioning to Membrane Framework Pipelines with JSON-RPC Blender Runner\n\n\n5 min\n\n\n20230813-blender-runner-into-membrane-framework.md\n\n\n\n\nProposed: Update V-Sekai game engine procedure\n\n\n2 min\n\n\n20230812-vsekai-update-process.md\n\n\n\n\nProposed: Procedure to unmerge and then merge solves a V-Sekai source code broken tree\n\n\n2 min\n\n\n20230812-unmerge-and-merge-procedure-source-code-tree.md\n\n\n\n\nProposed: Configuring GoCD Agents in V-Sekai\n\n\n3 min\n\n\n20230812-gocd-agent-setup.md\n\n\n\n\nProposed: Constrain the entire Godot Humanoid Skeleton\n\n\n2 min\n\n\n20230812-constraint-all-bones.md\n\n\n\n\nAccepted: Punchline based reports\n\n\n3 min\n\n\n20230811-punchline-reports.md\n\n\n\n\nProposed: V-Sekai Navigation Compatibility with VR\n\n\n2 min\n\n\n20230806-v-sekai-ipad-projection-compatibility.md\n\n\n\n\nProposed: Sonic Symphony: Crafting Melodies with Machine Intelligence\n\n\n3 min\n\n\n20230806-music-gen.md\n\n\n\n\nProposed: Dokku for V-Sekai URO Backend Services Hosting and Development\n\n\n2 min\n\n\n20230804-dokku.md\n\n\n\n\nAccepted: Git Subrepo Addon Management\n\n\n2 min\n\n\n20230803-subrepo-addon-management.md\n\n\n\n\nAccepted: Completing VRM 1.0 Support and Publishing to Godot Engine Asset Library\n\n\n2 min\n\n\n20230803-publish-vrm-to-assetlibrary.md\n\n\n\n\nProposed: Port Godot Jolt from GDExtension to C++ Module\n\n\n2 min\n\n\n20230803-jolt-gextension-to-module.md\n\n\n\n\nProposed: Social RPG World Proposal\n\n\n2 min\n\n\n20230803-idle-rpg-home.md\n\n\n\n\nProposed: Solve Renik directly rather than through many bone ik\n\n\n2 min\n\n\n20230726-solve-renik-directly-rather-than-many-bone-ik.md\n\n\n\n\nProposed: Enhancing the Many Bone IK Configuration\n\n\n3 min\n\n\n20230719-pose-kusudama-constraints-in-vr.md\n\n\n\n\nProposed: Game simulation server sidekick process\n\n\n2 min\n\n\n20230719-dual-databases-cockroachdb-khepri.md\n\n\n\n\nProposed: Enhancing Avatar Creation Process in V-Sekai Advanced\n\n\n4 min\n\n\n20230716-enhancing-avatar-creation-process-02-advanced.md\n\n\n\n\nProposed: Enhancing Avatar Creation Process in V-Sekai Regular\n\n\n5 min\n\n\n20230716-enhancing-avatar-creation-process-01-regular.md\n\n\n\n\nProposed: V-Sekai Feature Enhancement Proposal\n\n\n6 min\n\n\n20230701-vsekai-broken-down-goals.md\n\n\n\n\nAccepted: V-Sekai Meeting - Friday, June 30, 2023\n\n\n2 min\n\n\n20230630-vsekai-goal-meeting.md\n\n\n\n\nProposed: Ship Godot Engine VRM1 to solve portable humanoid avatars\n\n\n3 min\n\n\n20230626-godot-vrm1-addon.md\n\n\n\n\nAccepted: V-Sekai Roadmap and Goals 2023-06-24\n\n\n2 min\n\n\n20230624-v-sekai-roadmap.md\n\n\n\n\nProposed: Implementing Feedback Delay Networks for Enhanced Audio Reverb Simulation in V-Sekai\n\n\n8 min\n\n\n20230623-fdn-reverb-solution.md\n\n\n\n\nProposed: Large language model t5 generating xstate json reliabily for digital beings\n\n\n5 min\n\n\n20230620-t5-jsonformer-xstate.md\n\n\n\n\nProposed: A Potential Solution for V-Sekai’s Identifier Assignment Challenge\n\n\n2 min\n\n\n20230620-doi-github.md\n\n\n\n\nRejected: V-Sekai Database Solution for 50,000 Concurrent Online Users\n\n\n2 min\n\n\n20230619-move-cockroachdb-to-yugabyte.md\n\n\n\n\nProposed: Networked Procedural Generation as a Sidecar to the Godot Engine Server\n\n\n3 min\n\n\n20230619-membrane-framework-for-mesh-processing.md\n\n\n\n\nAccepted: V-Sekai Roadmap and Goals 2023-06-18\n\n\n3 min\n\n\n20230618-v-sekai-roadmap.md\n\n\n\n\nProposed: V-Sekai Bone Hierarchy Conversion\n\n\n2 min\n\n\n20230616-pmx-to-vrm.md\n\n\n\n\nProposed: Increase variety and quality with generated animation trees\n\n\n2 min\n\n\n20230614-llm-statechart.md\n\n\n\n\nProposed: Wasm in V-Sekai Proposal\n\n\n5 min\n\n\n20230611-wasm-in-v-sekai.md\n\n\n\n\nSuperseded: V-Sekai Roadmap and Goals 2023-06-08\n\n\n2 min\n\n\n20230608-v-sekai-roadmap.md\n\n\n\n\nSuperseded: V-Sekai Roadmap and Goals 2023-06-02\n\n\n2 min\n\n\n20230602-v-sekai-roadmap.md\n\n\n\n\nProposed: Pmx module integration\n\n\n3 min\n\n\n20230602-pmx-module-integration.md\n\n\n\n\nProposed: Capturing accurate body movements with limited tracker placement\n\n\n4 min\n\n\n20230602-limited-tracker-placement.md\n\n\n\n\nProposed: Propose a solution to improve V-Sekai contributors’ design skills for navigating 3D environments\n\n\n2 min\n\n\n20230531-godot-engine-learning.md\n\n\n\n\nProposed: Build a Single-Instance MacOS Editor for the iPad\n\n\n3 min\n\n\n20230531-godot-engine-ipad.md\n\n\n\n\nSuperseded: V-Sekai Roadmap and Goals 2023-05-19\n\n\n2 min\n\n\n20230527-v-sekai-roadmap.md\n\n\n\n\nProposed: Efficiently managing and synchronizing game data with a server sidecar\n\n\n3 min\n\n\n20230527-server-sidecar.md\n\n\n\n\nProposed: Implement server-side content validation export followed by a sanitization service and CDN support\n\n\n2 min\n\n\n20230527-server-side-content-validation.md\n\n\n\n\nProposed: Generating Random Text Data for testing V-Sekai systems\n\n\n3 min\n\n\n20230527-server-performance-test.md\n\n\n\n\nProposed: Handling access to session based game data\n\n\n2 min\n\n\n20230527-server-cdn-session-url.md\n\n\n\n\nDraft: Finding ways to attract users, developers, and creators sustaining V-Sekai\n\n\n2 min\n\n\n20230527-organization.md\n\n\n\n\nProposed: Create a 12x12 meter 3D demo map with 2-meter-high obstacles and walls\n\n\n1 min\n\n\n20230527-godot-test-game.md\n\n\n\n\nProposed: Convert IK solvers to be using the AnimationTree\n\n\n3 min\n\n\n20230525-animation-ik-node.md\n\n\n\n\nDraft: Improve V-Sekai marketing\n\n\n2 min\n\n\n20230523-marketing-cycle.md\n\n\n\n\nRejected: Defeating your fictional enemies in their blood\n\n\n1 min\n\n\n20230522-JOKE-fictional-blood-combat.md\n\n\n\n\nProposed: Improving Jitter-Buffer Implementation for Voice Chat in V-Sekai Projects\n\n\n2 min\n\n\n20230521-audio-jitter-buffer-voip.md\n\n\n\n\nSuperseded: V-Sekai Roadmap and Goals 2023-05-19\n\n\n2 min\n\n\n20230519-v-sekai-roadmap.md\n\n\n\n\nProposed: Add VRM portable avatars and OMI_personality to the GLTF Transform tool\n\n\n3 min\n\n\n20230519-add-vrm-omi-personality-gltf-extension.md\n\n\n\n\nSuperseded: V-Sekai Roadmap and Goals 2023-05-16\n\n\n2 min\n\n\n20230516-v-sekai-roadmap.md\n\n\n\n\nAccepted: Aquarium Nightclub Booth for Virtual Market Exhibition\n\n\n2 min\n\n\n20230516-create-an-aquarium-nightclub-booth-for-virtual-market.md\n\n\n\n\nRejected: Additional 3D Import Functionality\n\n\n3 min\n\n\n20230516-additional-3d-import.md\n\n\n\n\nDraft: Exchange data between Godot Engine and WASM using handles\n\n\n2 min\n\n\n20230509-wasm-data-exchange.md\n\n\n\n\nDraft: Convert segmented front facing 3D Garment images to novel 3d views for 3d modeling\n\n\n2 min\n\n\n20230508-novel-3d-views.md\n\n\n\n\nRejected: Using Deno to handle the conversion of GLB files to Godot Engine packed scenes\n\n\n2 min\n\n\n20230507-supabase.md\n\n\n\n\nRejected: Distributed simulation\n\n\n17 min\n\n\n20230507-distributed-sim.md\n\n\n\n\nDraft: Describe a avatar publishing workflow for portability\n\n\n2 min\n\n\n20230507-avatar-publishing-workflow-portability.md\n\n\n\n\nSuperseded: Solve V-Sekai limitations using ChatGPT-4 AI completion.\n\n\n3 min\n\n\n20230505-v-sekai-ai-completion.md\n\n\n\n\nProposed: VR design application for V-Sekai\n\n\n2 min\n\n\n20230505-polygon-mesh-based-sculpting-tools.md\n\n\n\n\nProposed: Enhancing Cross-Platform Compatibility and User Experience for V-Sekai VR Social Players\n\n\n2 min\n\n\n20230505-cross-platform-artwork-distribution.md\n\n\n\n\nProposed: Solve a V-Sekai naming convention limitation.\n\n\n3 min\n\n\n20230505-consistent-v-sekai-naming.md\n\n\n\n\nProposed: Automated avatar garment rigging\n\n\n4 min\n\n\n20230505-automated-avatar-garment-rigging.md\n\n\n\n\nAccepted: Adding IREE to Godot Engine for Image Superresolution\n\n\n3 min\n\n\n20230502-add-iree-to-godot-engine-for-image-superresolution.md\n\n\n\n\nSuperseded: V-Sekai Roadmap and Goals 2023-04-20\n\n\n3 min\n\n\n20230429-v-sekai-roadmap.md\n\n\n\n\nProposed: Improve the collaboration process and attract more contributors to work on the project\n\n\n3 min\n\n\n20230429-improve-collab.md\n\n\n\n\nAccepted: Challenges in managing and synchronizing multiple assets and libraries across different git repositories\n\n\n2 min\n\n\n20230429-git-subrepo-challenges.md\n\n\n\n\nRejected: Package Godot for pkgin\n\n\n5 min\n\n\n20230419-package-godot-for-pkgin.md\n\n\n\n\nProposed: Capturing accurate body movements with limited tracker placement\n\n\n4 min\n\n\n20230419-limited-tracker-placement.md\n\n\n\n\nProposed: Use godot rgbaf textures to store integers\n\n\n3 min\n\n\n20230415-rgbaf-to-store-integers.md\n\n\n\n\nProposed: Procedurally create variations for our props, environments and avatars\n\n\n3 min\n\n\n20230415-procedural-variations-props-envs-avatars.md\n\n\n\n\nProposed: Hit a collaborate button to load up into V-Sekai\n\n\n2 min\n\n\n20230415-load-collaborate.md\n\n\n\n\nProposed: Provide v-sekai-game in a launcher to make it easier to use v-sekai\n\n\n1 min\n\n\n20230408-v-sekai-launcher.md\n\n\n\n\nProposed: Use junit xml based tests in github\n\n\n1 min\n\n\n20230310-xml-based-tests.md\n\n\n\n\nProposed: Don’t merge incomplete work.\n\n\n1 min\n\n\n20230310-don’t-merge-incomplete-work.md\n\n\n\n\nSuperseded: Creating a Godot Engine C++ module with IREE backend for machine learning computations using Vulkan and CUDA\n\n\n2 min\n\n\n20230310-IREE-backend-for-machine-learning-computations.md\n\n\n\n\nAccepted: Meet at GDC SF 2023\n\n\n2 min\n\n\n20230131-meeting-at-gdc-2023.md\n\n\n\n\nAccepted: Default test plan for testing V-Sekai engine upgrades.\n\n\n2 min\n\n\n20230131-default-test-plan.md\n\n\n\n\nProposed: Adopt best practices for product development\n\n\n2 min\n\n\n20230131-adopt-best-product-development-practices.md\n\n\n\n\nProposed: Without visualization, we cannot easily compare the interpolation states\n\n\n2 min\n\n\n20230125-without-viz-we-cannot-compare-the-interpolation.md\n\n\n\n\nProposed: Provide user generated scripting with libsql and wasm\n\n\n2 min\n\n\n20230125-user-generated-scripting-with-libsql-and-wasm.md\n\n\n\n\nProposed: Have two groups move towards each other battle demo\n\n\n2 min\n\n\n20230125-two-groups-battle-demo.md\n\n\n\n\nProposed: Provide metadata to pre-check if maps and avatars are compatible to load\n\n\n1 min\n\n\n20230125-provide-metadata-to-match-compatibile-maps-and-avatars.md\n\n\n\n\nProposed: Possible futures\n\n\n2 min\n\n\n20230125-possible-futures.md\n\n\n\n\nProposed: Grow the community with a reactive Discord bot.\n\n\n2 min\n\n\n20230125-grow-the-community-with-a-reactive-discord-bot.md\n\n\n\n\nProposed: Create an in-game tablet interface we can activate\n\n\n1 min\n\n\n20230125-create-an-in-game-tablet-interface-we-can-activate.md\n\n\n\n\nProposed: Cover 80% to 95% of the player base.\n\n\n1 min\n\n\n20230125-cover-80-95-percent-of-the-userbase.md\n\n\n\n\nProposed: Use Easy Charts for observability\n\n\n1 min\n\n\n20230123-use-easy-charts-for-observability.md\n\n\n\n\nProposed: Recording demo checklist\n\n\n2 min\n\n\n20230123-recording-demo-checklist.md\n\n\n\n\nProposed: Ready net demo\n\n\n2 min\n\n\n20230123-ready-the-net-demo.md\n\n\n\n\nProposed: Publish Godot VRM for Godot 4 for production use\n\n\n2 min\n\n\n20230123-publish-godot-vrm-4.md\n\n\n\n\nProposed: Provide user generated scripting using WasGO\n\n\n2 min\n\n\n20230123-player-scripting.md\n\n\n\n\nProposed: No traversal loading screen\n\n\n4 min\n\n\n20230123-no-traversal-loading-screen.md\n\n\n\n\nProposed: Better Godot Engine integration with Blender with gltf extensions\n\n\n2 min\n\n\n20230123-integrate-blender-with-gltf-extensions-and-godot.md\n\n\n\n\nProposed: Face helmet capture\n\n\n2 min\n\n\n20230123-face-helmet-capture.md\n\n\n\n\nProposed: Add WMF for windows media playback\n\n\n2 min\n\n\n20230108-wmf-video-playback.md\n\n\n\n\nAccepted: Bolster creating the metaverse\n\n\n3 min\n\n\n20230108-bolster-creating-the-metaverse.md\n\n\n\n\nAccepted: How to start a EXPERIMENTAL environment for sqlite and elixir?\n\n\n3 min\n\n\n20230107-elixir-uro-dev-sqlite.md\n\n\n\n\nAccepted: Separate walking controller from RenIK for ManyBoneIK\n\n\n2 min\n\n\n20230106-walking-controller-renik.md\n\n\n\n\nProposed: Powershell autocomplete uses right arrow\n\n\n2 min\n\n\n20221214-powershell-autocomplete-use-right-arrow.md\n\n\n\n\nProposed: Tools helpful for creating Avatars and Worlds\n\n\n3 min\n\n\n20221212-world-and-character-tools.md\n\n\n\n\nProposed: Prepare godot-vrm for asset library publishing\n\n\n4 min\n\n\n20221206-export-godot-vrm-to-the-asset-library.md\n\n\n\n\nProposed: Port RENIK to Many Bone IK for better quality\n\n\n2 min\n\n\n20221205-port-renik-to-many-bone-ik.md\n\n\n\n\nProposed: Move fast without breaking things for V-Sekai\n\n\n2 min\n\n\n20221205-moving-fast-philosophy-development.md\n\n\n\n\nProposed: Debug Linux Export\n\n\n3 min\n\n\n20221205-debug-linux-export.md\n\n\n\n\nProposed: Target 10 minutes cicd builds to improve our iterations\n\n\n2 min\n\n\n20221203-target-10-minutes-cicd.md\n\n\n\n\nRejected: Blocking direct push to MAIN to avoid build breakage\n\n\n2 min\n\n\n20221203-block-direct-pushes-to-main.md\n\n\n\n\nDraft: Simulate larger 3d multiplayer worlds using “brickworlds partition layout”\n\n\n5 min\n\n\n20221022-have-larger-worlds-by-server-state-migration.md\n\n\n\n\nProposed: Make it easier to propose and file bugs by simplifying the templates\n\n\n3 min\n\n\n20221021-make-it-easier-propose-and-post-bugs.md\n\n\n\n\nProposed: Replicate sync 100’000 entities using a solution (Revision 1)\n\n\n2 min\n\n\n20221019-replicate-sync-100-000-entities.md\n\n\n\n\nProposed: Networking with 100000 Entities and Ownership (Revision 2)\n\n\n4 min\n\n\n20221019-networking-100000-entities-ownership.md\n\n\n\n\nProposed: Replicate sync 100’000 entities using Godot Engine, mvsqlite and Foundationdb\n\n\n3 min\n\n\n20221019-develop-a-replication-sync-for-100-000-entities.md\n\n\n\n\nProposed: To remember how to update the engine and game write a procedure\n\n\n3 min\n\n\n20221018-v-sekai-game-update-procedure.md\n\n\n\n\nRejected: Use view replication algorithm for multiplayer multirelay sync\n\n\n9 min\n\n\n20221016-v-sekai-view-replication.md\n\n\n\n\nDraft: Networking Overhaul\n\n\n5 min\n\n\n20221014-networking-overhaul-proposal.md\n\n\n\n\nProposed: Unidot is optional\n\n\n2 min\n\n\n20221006-unidot-is-optional.md\n\n\n\n\nProposed: Rename master to godot3 and main to godot4\n\n\n2 min\n\n\n20221006-rename-to-main.md\n\n\n\n\nProposed: We have too many branches on V-Sekai/godot.\n\n\n2 min\n\n\n20220916-too-many-branches-on-v-sekai-godot.md\n\n\n\n\nProposed: Extended asset library packages in addition to the upstream asset library\n\n\n2 min\n\n\n20220901-mirror-extend-asset-library-packages.md\n\n\n\n\nProposed: Provide pdf reading\n\n\n2 min\n\n\n20220830-godot-pdf-workflow.md\n\n\n\n\nProposed: Make a market booth creation tutorial.\n\n\n2 min\n\n\n20220820-market-booth-tutorial.md\n\n\n\n\nProposed: Simulate cloth on characters\n\n\n2 min\n\n\n20220820-cloth-sim.md\n\n\n\n\nProposed: Bake alembic imports by running blender script.\n\n\n3 min\n\n\n20220820-bake alembic-anim-via-blender.md\n\n\n\n\nProposed: Connect Mediapipe to Blender\n\n\n3 min\n\n\n20220624-webcam-to-posed-characters.md\n\n\n\n\nProposed: Host a baserow application for internal use.\n\n\n3 min\n\n\n20220605-host-internal-baserow.md\n\n\n\n\nAccepted: To avoid git submodule but recreate the gocd pipelines\n\n\n2 min\n\n\n20220605-gocd-pipeline-reset.md\n\n\n\n\nProposed: Lightweight quality avatars\n\n\n3 min\n\n\n20220601-lightweight-quality-avatars.md\n\n\n\n\nRejected: To create a deployment kit use truescale to host gocd agents for cicd.\n\n\n2 min\n\n\n20220531-truenas-scale.md\n\n\n\n\nAccepted: How to start a development environment for cockroach and elixir?\n\n\n3 min\n\n\n20220531-elixir-uro-dev.md\n\n\n\n\nProposed: Profile using perf\n\n\n2 min\n\n\n20220515-profile-using-perf.md\n\n\n\n\nProposed: Merge retargeting feature into Godot Engine master\n\n\n4 min\n\n\n20220318-merge-retargeting-pr.md\n\n\n\n\nProposed: Use specular vec3 from gltf to show multicoloured metals\n\n\n2 min\n\n\n20220317-use-spec-rough-metal.md\n\n\n\n\nProposed: To protect the minimum spec maintain steam deck version of flatmode V-Sekai\n\n\n2 min\n\n\n20220317-protect-minumum-spec-steam-deck.md\n\n\n\n\nDraft: To provide an asset library prototype use baserow\n\n\n2 min\n\n\n20220317-baserow.io-truenas.md\n\n\n\n\nAccepted: Planning V-Sekai Version 3 on 2022-02-28\n\n\n3 min\n\n\n20220228-v-sekai-version-three-plan.md\n\n\n\n\nSuperseded: Planning V-Sekai Version 2 on 2022-02-24\n\n\n4 min\n\n\n20220224-v-sekai-version-two-plan.md\n\n\n\n\nRejected: Storing raw VSK_map files via DVC to avoid limitations\n\n\n3 min\n\n\n20220223-store-source-VSK_map-files-via-DVC.md\n\n\n\n\nAccepted: Rank skeleton #bone names with catboost\n\n\n4 min\n\n\n20220222-rank-skeleton-bone-names-with-catboost.md\n\n\n\n\nAccepted: Rank skeleton #bone names with xgboost\n\n\n3 min\n\n\n20220222-rank-bone-skeletons-with-xgboost.md\n\n\n\n\nAccepted: Rank skeleton #bone names with transformer4rec\n\n\n3 min\n\n\n20220222-rank-bone-names-with-transformer.md\n\n\n\n\nSuperseded: Planning V-Sekai on 2022-02-21 Superseded\n\n\n4 min\n\n\n20220222-know-where-we-re-going-by-planning-vsekai.md\n\n\n\n\nAccepted: To create omi chan rig a #256FES\n\n\n3 min\n\n\n20220217-omi-chan-oni-chan.md\n\n\n\n\nProposed: To deploy backend services like Uro safely use a defined process\n\n\n3 min\n\n\n20220215-uro-deployment-process.md\n\n\n\n\nAccepted: To make a virtual pet game given Jeana’s designs\n\n\n2 min\n\n\n20220207-virtual-pets.md\n\n\n\n\nProposed: Log change notifications using DiscordChatExporter\n\n\n2 min\n\n\n20220206-logging-notifications-from-discord.md\n\n\n\n\nAccepted: Allow cicd to pass by fixing spatial audio branch\n\n\n2 min\n\n\n20220205-cicd-to-pass by-fixing-spatial-audio-branch.md\n\n\n\n\nDraft: To have a default set of motions on a 3d character by creating a default animation set\n\n\n3 min\n\n\n20220203-create-default-animation-set.md\n\n\n\n\nAccepted: Interoperability between platforms using gltf extensions\n\n\n4 min\n\n\n20220202-gltf-extensions-for-interoperability.md\n\n\n\n\nRejected: To allow independent deployment run our own infrastructure\n\n\n4 min\n\n\n20220131-run-own-infrastructure.md\n\n\n\n\nAccepted: To have an alternative CICD use Github Actions.\n\n\n3 min\n\n\n20220131-github-actions-support.md\n\n\n\n\nProposed: Make a desktop version of Uro for ease of development.\n\n\n2 min\n\n\n20220131-elixir-desktop-uro.md\n\n\n\n\nAccepted: To record decisions write a proposal.\n\n\n4 min\n\n\n20220130-to-record-decisions-write-a-proposal.md\n\n\n\n\nProposal: Optimize cicd for costs because it’s limited\n\n\n2 min\n\n\n20220130-optimize-cicd.md\n\n\n\n\nAccepted: To make it easier to upload V-Sekai maps and Avatars use Godot Engine 4 script templates.\n\n\n2 min\n\n\n20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.md\n\n\n\n\nAccepted: Convert gltf to a scene with AudioStreamPlayer3D, convert AudiostreamPlayer3D to gltf and expose usability.\n\n\n2 min\n\n\n20220118-convert-gltf-to-a-scene.md\n\n\n\n\nProposal: Change transform by CRDT.\n\n\n2 min\n\n\n20220113-change-transform-by-crdt.md\n\n\n\n\nProposal: Bake blend shapes to skeletons for performance\n\n\n3 min\n\n\n20220108-bake-blend-shapes-to-skeletons-for-performance.md\n\n\n\n\nProposal: Stream a character from a webcam to the vmc protocol\n\n\n2 min\n\n\n20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.md\n\n\n\n\nAccepted: Run meetings using Lean Coffee\n\n\n3 min\n\n\n20211229-run-meetings-using-lean-coffee.md\n\n\n\n\nRejected: Network the Ubisoft Mixer server\n\n\n2 min\n\n\n20211220-network-the-ubisoft-mixer-server.md\n\n\n\n\nAccepted: Create an open metaverse by working on V-Sekai\n\n\n4 min\n\n\n20211214-create-an-open-metaverse-by-working-on-v-sekai.md\n\n\n\n\nRejected: Create Steamdeck hardware proxy by installing Fedora Silverblue and #steam\n\n\n2 min\n\n\n20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.md\n\n\n\n\nRejected: Create Steamdeck hardware proxy by installing Fedora Kinoite and #steam\n\n\n2 min\n\n\n20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.md\n\n\n\n\nAccepted: For Godot Engine changes use a decision flowchart\n\n\n3 min\n\n\n20211207-for-godot-engine-changes-use-a-decision-flowchart.md\n\n\n\n\nAccepted: Create an upstream pull request for all non-V-Sekai related patches\n\n\n2 min\n\n\n20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.md\n\n\n\n\nAccepted: Avoid avatar breaking by following quality checklist\n\n\n3 min\n\n\n20211130-avoid-avatar-breaking-by-following-quality-checklist.md\n\n\n\n\nAccepted: Create a Godot Engine asset store service on elixir and on sqlite.\n\n\n3 min\n\n\n20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.md\n\n\n\n\nAccepted: Stabilize Godot Engine updates by delaying to 2 week cycles\n\n\n2 min\n\n\n20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.md\n\n\n\n\nProposed: Allow Godot Asset Library browser to use alternative sources\n\n\n2 min\n\n\n20211117-allow-godot-asset-library-browser-to-use-alternative-sources.md\n\n\n\n\nProposed: Learn how to scale V-Sekai using bots and multipliers\n\n\n2 min\n\n\n20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.md\n\n\n\n\nRejected: File or attestation for virtual worlds using ssh signatures\n\n\n3 min\n\n\n20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.md\n\n\n\n\nAccepted: Degrade V-Sekai’s networking model to work in 2d and with webrtc.\n\n\n2 min\n\n\n20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.md\n\n\n\n\nDraft: Create a VRM character by experimenting with written workflows.\n\n\n2 min\n\n\n20211109-create-a-vrm-character-by-experimenting-with-written-workflows.md\n\n\n\n\nProposed: Polish demo of V-Sekai by making invisible meshes appear via the use of the exporter.\n\n\n2 min\n\n\n20211108-invisible-meshes-appear-via-the-use-of-the-exporter.md\n\n\n\n\nProposed: Integrate with blender\n\n\n2 min\n\n\n20211108-integrate-with-blender.md\n\n\n\n\nDraft: Preview #materialx materials on the Web in Godot Engine\n\n\n2 min\n\n\n20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.md\n\n\n\n\nDraft: Use single player WebXR in Godot Engine to prototype CASSIE.\n\n\n2 min\n\n\n20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.md\n\n\n\n\nAccepted: Take a list of 3D points that form a vaguely closed boundary in space and triangulate in Godot Engine\n\n\n3 min\n\n\n20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.md\n\n\n\n\nRejected: Iterate faster on WasGo prototype by using Godot 3.4\n\n\n2 min\n\n\n20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.md\n\n\n\n\nRejected: Have an WebXR version of V-Sekai that is more accessible\n\n\n2 min\n\n\n20211105-have-an-webxr-version-of-v-sekai.md\n\n\n\n\nDraft: Research mesh tooling with nglod\n\n\n2 min\n\n\n20211104-research-mesh-tooling-with-nglod.md\n\n\n\n\nDraft: Research mesh tooling with kaolin\n\n\n3 min\n\n\n20211104-research-mesh-tooling-with-kaolin.md\n\n\n\n\nDraft: Use a standard reference platform called VFX Reference platform\n\n\n3 min\n\n\n20211103-use-platform-called-vfx-reference-platform.md\n\n\n\n\nAccepted: VOIP\n\n\n2 min\n\n\n20211031-voip.md\n\n\n\n\nDraft: VMD on VRM AnimationTree Node\n\n\n3 min\n\n\n20211031-vmd-on-vrm-animationtree-node.md\n\n\n\n\nDraft: Verification tools\n\n\n2 min\n\n\n20211031-verification-tools.md\n\n\n\n\nAccepted: Use our custom fullbody IK\n\n\n2 min\n\n\n20211031-use-our-custom-fullbody-ik.md\n\n\n\n\nProposed: Rank skeleton bone names by using BPR\n\n\n2 min\n\n\n20211031-use-bpr-to-rank-skeleton-bone-names.md\n\n\n\n\nProposed: Update URO for Godot 4\n\n\n2 min\n\n\n20211031-update-uro-for-godot-4.md\n\n\n\n\nProposed: Tire model car sim\n\n\n2 min\n\n\n20211031-tire-model-car-sim.md\n\n\n\n\nAccepted: ThorVG\n\n\n2 min\n\n\n20211031-thorvg.md\n\n\n\n\nProposed: Take a streaming godot game and streaming the VRM to OpenSoundControl\n\n\n2 min\n\n\n20211031-streaming-godot-to-opensoundcontrol.md\n\n\n\n\nProposed: Stream shader motion\n\n\n2 min\n\n\n20211031-stream-shader-motion.md\n\n\n\n\nProposed: Standard backup procedures\n\n\n2 min\n\n\n20211031-standard-backup-procedures.md\n\n\n\n\nProposed: To provide a performance and portable script use WasGo\n\n\n2 min\n\n\n20211031-script-as-a-binary.md\n\n\n\n\nProposed: Run the maintenance scripts from Windows in Unix mode with msys2\n\n\n2 min\n\n\n20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.md\n\n\n\n\nSuperseded: Play preprocessed #animation on any VRM model\n\n\n2 min\n\n\n20211031-play-preprocessed-animations-on-any-vrm-model.md\n\n\n\n\nProposed: Plausible npc behavior\n\n\n2 min\n\n\n20211031-plausable-npc-behaviour.md\n\n\n\n\nProposed: Phase out groups in the branding to make it more recognizable\n\n\n2 min\n\n\n20211031-phase-out-groups-terminology-for-vskdefault.md\n\n\n\n\nRejected: OpenVR for Godot Engine\n\n\n2 min\n\n\n20211031-openvr-for-godot-engine.md\n\n\n\n\nProposed: Membrane Framework streaming Mixer\n\n\n2 min\n\n\n20211031-membrane-framework-streaming-mixer.md\n\n\n\n\nProposed: Meeting area\n\n\n2 min\n\n\n20211031-meeting-area.md\n\n\n\n\nProposed: Make a place to record\n\n\n2 min\n\n\n20211031-make-a-place-to-record.md\n\n\n\n\nAccepted: Keep a changelog\n\n\n2 min\n\n\n20211031-keep-a-changelog.md\n\n\n\n\nProposed: How to make a V-Sekai/godot update?\n\n\n2 min\n\n\n20211031-how-to-make-a-v-sekaigodot-update.md\n\n\n\n\nProposed: Have wires in 3d\n\n\n2 min\n\n\n20211031-have-wires-in-3d.md\n\n\n\n\nProposed: Have better user developer experience\n\n\n2 min\n\n\n20211031-have-better-user-developer-experience.md\n\n\n\n\nProposed: Godot Database viewer for proposals\n\n\n3 min\n\n\n20211031-godot-database-viewer-for-proposals.md\n\n\n\n\nProposed: glTF - importer should bind animation players to the closest root node\n\n\n2 min\n\n\n20211031-gltf-importer-should-bind-animation-players-to-the-closest-root-node.md\n\n\n\n\nProposed: Face motion tracking requires standard shapes\n\n\n2 min\n\n\n20211031-face-motion-tracking-requires-standard-shapes.md\n\n\n\n\nProposed: Extract proposals into proposals\n\n\n23 min\n\n\n20211031-extract-proposals-into-proposals.md\n\n\n\n\nProposed: Export / Import testing via robot-framework and swiftshader\n\n\n2 min\n\n\n20211031-export-import-testing-via-robot-framework-and-swiftshader.md\n\n\n\n\nProposed: Create a demo viewer gallery\n\n\n3 min\n\n\n20211031-create-a-demo-viewer-gallery.md\n\n\n\n\nProposed: Construct the virtual #world\n\n\n2 min\n\n\n20211031-construct-the-virtual-world.md\n\n\n\n\nProposed: Client and Mast\n\n\n2 min\n\n\n20211031-client-and-mast.md\n\n\n\n\nProposed: CICD Export V-Sekai\n\n\n2 min\n\n\n20211031-cicd-export-v-sekai.md\n\n\n\n\nProposed: Character workshop\n\n\n2 min\n\n\n20211031-character-workshop.md\n\n\n\n\nProposed: Benchmark #animation playback\n\n\n2 min\n\n\n20211031-benchmark-animation-playback.md\n\n\n\n\nProposed: Bake blend shape to skeleton animation\n\n\n2 min\n\n\n20211031-bake-blend-shape-to-skeleton-animation.md\n\n\n\n\nProposed: Bake a #materialx into a custom Godot StandardMaterial3D\n\n\n2 min\n\n\n20211031-bake-a-materialx-into-a-custom-godot-standardmaterial3d.md\n\n\n\n\nProposed: ARC radial menu\n\n\n2 min\n\n\n20211031-arc-radial-menu.md\n\n\n\n\nProposed: 1000 player servers\n\n\n2 min\n\n\n20211031-1000-player-servers.md\n\n\n\n\nProposed: We want to proxy udp datagrams at production quality of service.\n\n\n2 min\n\n\n20211005-we-want-to-proxy-udp-datagrams-at-production-quality-of-service.md\n\n\n\n\nProposed: Want to use the same cluster for the same web and native.\n\n\n3 min\n\n\n20211005-want-to-use-the-same-cluster-for-the-same-web-and-native.md\n\n\n\n\nProposed: Summon #friend and acquaintances via presence to the current world.\n\n\n2 min\n\n\n20211005-want-to-summon-friends-and-acquaintances-via-presence.md\n\n\n\n\nProposed: Use materialx for asset interchange\n\n\n2 min\n\n\n20211005-use-materialx-for-asset-interchange.md\n\n\n\n\nProposed: Use KVM to test our AMD APU test computer via Barrier.\n\n\n2 min\n\n\n20211005-use-kvm-to-test-our-amd-apu-test-computer-via-barrier.md\n\n\n\n\nProposed: Test Google Mediapipe\n\n\n3 min\n\n\n20211005-test-google-mediapipe.md\n\n\n\n\nProposed: Solve Mocap By Connecting Mediapipe to Blender\n\n\n2 min\n\n\n20211005-solve-mocap-by-connecting-mediapipe-to-blender.md\n\n\n\n\nProposed: Improve Meshing Results by Subdivision in Godot Engine\n\n\n2 min\n\n\n20211005-improve-meshing-results-by-subdivision-in-godot-engine.md\n\n\n\n\nProposed: Create SOP for VRM #creation\n\n\n2 min\n\n\n20211005-create-sop-for-vrm-creation.md\n\n\n\n\nProposed: Create a standard procedure from adding spring bones to VRM models.\n\n\n2 min\n\n\n20211005-create-add-spring-bones-to-vrm-models.md\n\n\n\n\nProposed: Music is important to human experience and should be bridged to XR\n\n\n2 min\n\n\n20211005-bridge-music-to-xr.md\n\n\n\n\nProposed: Spoke to V-Sekai\n\n\n2 min\n\n\n20210811-spoke-to-v-sekai.md\n\n\n\n\nProposed: Soiree party mode\n\n\n3 min\n\n\n20210811-soiree-party.md\n\n\n\n\nProposed: OMI Glb Portable Content\n\n\n2 min\n\n\n20210811-omi-glb.md\n\n\n\n\nProposed: Neural Blend Shape Rigging\n\n\n3 min\n\n\n20210811-neural-blend-shape-rigging.md\n\n\n\n\nProposed: Import Minecraft worlds to Godot Engine\n\n\n2 min\n\n\n20210811-minecraft-voxel.md\n\n\n\n\nProposed: Minimum Specification V-Sekai Hardware\n\n\n3 min\n\n\n20210811-min-spec-v-sekai.md\n\n\n\n\nAccepted: OIT in Godot Engine\n\n\n2 min\n\n\n20210811-godot-transparency.md\n\n\n\n\nProposed: GLB data in a Movie\n\n\n2 min\n\n\n20210811-glb-in-video.md\n\n\n\n\nProposed: Membrane Framework to Process Game Workflows\n\n\n2 min\n\n\n20210811-game-workflow-membrane.md\n\n\n\n\nProposed: Godot Engine implementation of disconnected IPFS\n\n\n2 min\n\n\n20210811-disconnected-ipfs.md\n\n\n\n\nProposed: Spreadsheet Animation Preview\n\n\n4 min\n\n\n20210724-Spreadsheet-animation-preview.md\n\n\n\n\nProposed: Portable #world Content\n\n\n2 min\n\n\n20210715-portable-world-content.md\n\n\n\n\nProposed: Material Addon Blender\n\n\n2 min\n\n\n20210715-Material-Addon-Blender.md\n\n\n\n\nProposed: Describe a Godot Engine pr verification workflow\n\n\n2 min\n\n\n20210710-verify-pr-workflow.md\n\n\n\n\nProposed: Transfer animation by baking reset\n\n\n3 min\n\n\n20210707-transfer-animations-by-baking-reset.md\n\n\n\n\nProposed: Convert #shadermotion to be played in Godot Engine\n\n\n2 min\n\n\n20210622-shadermotion-to-godot-engine.md\n\n\n\n\nProposed: Convert FBX and glTF2 to VRM via flow-avatar-asset-pipeline\n\n\n2 min\n\n\n20210612-flow-avatar-asset-pipeline.md\n\n\n\n\nProposed: Store presentation and book content via Lottie\n\n\n3 min\n\n\n20210601-store-presentation-and-book-content-via-lottie-2.md\n\n\n\n\nProposed: Performance profile the game with AMDuProf\n\n\n2 min\n\n\n20210529-performance-profiling.md\n\n\n\n\nProposed: Trial install of Gravity for Kubernetes\n\n\n2 min\n\n\n20210528-trial-install-of-gravity-for-kubernetes.md\n\n\n\n\nProposed: Simplify Meshes and LODs better with Quads\n\n\n2 min\n\n\n20210523-simplfy-meshes-and-lods-better-with-quads.md\n\n\n\n\nProposed: Retarget VRM Motion Blender Workflow\n\n\n4 min\n\n\n20210523-retarget-motion-for-vrm-type-models.md\n\n\n\n\nProposed: Distribute trusted clients with notary\n\n\n3 min\n\n\n20210523-distribute-trusted-clients-with-notary.md\n\n\n\n\nAccepted: Complete glTF2 / VRM import and export pipeline in Godot Engine\n\n\n2 min\n\n\n20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.md\n\n\n\n\nAccepted: Support more flexible texture import via Basis Universal in Godot Engine\n\n\n2 min\n\n\n20210523-basis-universal-import.md\n\n\n\n\nAccepted: Use Markdown Architectural Decision Records\n\n\n2 min\n\n\n20210212-use-markdown-architectural-decision-records.md\n\n\n\n\nSuperseded: Use Log4brains to manage the ADRs\n\n\n2 min\n\n\n20210212-use-log4brains-to-manage-the-adrs.md\n\n\n\n\nProposed: Add build notifications\n\n\n2 min\n\n\n20210212-add-build-notifications.md\n\n\n\n\nAccepted: Adding Entity Networking to Groups\n\n\n7 min\n\n\n20200729-entity-networking.md\n\n\n\n\nMozilla Builders Summer MVP Lab (SUBMITTED ON JUNE 8 2020)\n\n\n12 min\n\n\n20200608-vsekai-charter.md\n\n\n\n\nAccepted: Manage backend resources on one or more physical machines with K3S\n\n\n26 min\n\n\n20200602-manage-backend-with-k3s.md\n\n\n\n\n\nNo matching items"
   },
   {
-    "objectID": "decisions/20221019-replicate-sync-100-000-entities.html#derivative-license",
-    "href": "decisions/20221019-replicate-sync-100-000-entities.html#derivative-license",
-    "title": "Proposed: Replicate sync 100’000 entities using a solution (Revision 1)",
+    "objectID": "plans.html",
+    "href": "plans.html",
+    "title": "V-Sekai - Manuals",
     "section": "",
-    "text": "Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "%% V-Sekai Social Virtual Reality Project\n\ngraph TD\n    %% Define tasks and dependencies based on your project\n\n    A[Restore old V-Sekai]\n    B[Game Telemetry System]\n    C[Integrate Motion Matching Techniques]\n    D[Implement Crash Reporting System and Performance Metrics]\n    E[Optimize Engine for Smooth Framerates]\n    F[Recruit Artist for Default Home Map]\n    G[Implement Account System, TOS, Privacy Policy]\n    H[Integration of Video Playback & Streaming]\n\n    A --&gt; C\n    C --&gt; D\n    D --&gt; E\n    A --&gt; F\n    A --&gt; G\n    A --&gt; H\n\n    %% Task styling\n    classDef taskInfo fill:#f9f,stroke:#333,stroke-width:2px;"
   },
   {
-    "objectID": "decisions/20240502-mvsqlite-launchd.html",
-    "href": "decisions/20240502-mvsqlite-launchd.html",
-    "title": "Proposed: Launching the mvsqlite rdbms server",
+    "objectID": "decisions/20231108-neon-postgresql.html",
+    "href": "decisions/20231108-neon-postgresql.html",
+    "title": "Proposed: Adopting Neon for a More Manageable Backend at V-Sekai",
     "section": "",
-    "text": "In software development and maintenance, automation of routine tasks is crucial for efficiency. One such task is launching a database server at system startup. For macOS users, this can be achieved using launchd, an open-source service management framework. In this context, we are specifically interested in automating the launch of the mvsqlite RDBMS server.\n\n\n\nThe task at hand is to create a launchd service for macOS that will automatically run the following command at system startup:\n/usr/local/bin/mvstore --data-plane 127.0.0.1:7000 --admin-api 127.0.0.1:7001 --metadata-prefix mvstore-test --raw-data-prefix m --auto-create-namespace --cluster /usr/local/etc/foundationdb/fdb.cluster\nAdditionally, we need to be able to retrieve logs from this service and check its status.\n\n\n\nTo solve this problem, we can create a .plist file in the ~/Library/LaunchAgents directory. This file will define our launchd service and specify the command it should run. We can also add keys to redirect the standard output and error to log files. Finally, we can use the launchctl list command to check the status of our service.\nHere are the detailed steps:\n\n\n\nOpen Terminal and navigate to the LaunchAgents directory:\n\ncd ~/Library/LaunchAgents\n\nCreate a new .plist file called com.user.mvstore.plist:\n\ntouch com.user.mvstore.plist\n\nOpen the file with a text editor (e.g., nano):\n\nnano com.user.mvstore.plist\n\nPaste the following content into the file:\n\n&lt;?xml version=\"1.0\" encoding=\"UTF-8\"?&gt;\n&lt;!DOCTYPE plist PUBLIC \"-//Apple//DTD PLIST 1.0//EN\" \"http://www.apple.com/DTDs/PropertyList-1.0.dtd\"&gt;\n&lt;plist version=\"1.0\"&gt;\n&lt;dict&gt;\n    &lt;key&gt;Label&lt;/key&gt;\n    &lt;string&gt;com.user.mvstore&lt;/string&gt;\n    &lt;key&gt;ProgramArguments&lt;/key&gt;\n    &lt;array&gt;\n        &lt;string&gt;/usr/local/bin/mvstore&lt;/string&gt;\n        &lt;string&gt;--data-plane&lt;/string&gt;\n        &lt;string&gt;127.0.0.1:7000&lt;/string&gt;\n        &lt;string&gt;--admin-api&lt;/string&gt;\n        &lt;string&gt;127.0.0.1:7001&lt;/string&gt;\n        &lt;string&gt;--metadata-prefix&lt;/string&gt;\n        &lt;string&gt;mvstore-test&lt;/string&gt;\n        &lt;string&gt;--raw-data-prefix&lt;/string&gt;\n        &lt;string&gt;m&lt;/string&gt;\n        &lt;string&gt;--auto-create-namespace&lt;/string&gt;\n        &lt;string&gt;--cluster&lt;/string&gt;\n        &lt;string&gt;/usr/local/etc/foundationdb/fdb.cluster&lt;/string&gt;\n    &lt;/array&gt;\n    &lt;key&gt;RunAtLoad&lt;/key&gt;\n    &lt;true/&gt;\n    &lt;key&gt;EnvironmentVariables&lt;/key&gt;\n    &lt;dict&gt;\n        &lt;key&gt;RUST_LOG&lt;/key&gt;\n        &lt;string&gt;info&lt;/string&gt;\n        &lt;key&gt;DYLD_LIBRARY_PATH&lt;/key&gt;\n        &lt;string&gt;/usr/local/lib&lt;/string&gt;\n    &lt;/dict&gt;\n&lt;/dict&gt;\n&lt;/plist&gt;\n\nSave and close the file.\nLoad the new service:\n\nlaunchctl load ~/Library/LaunchAgents/com.user.mvstore.plist\n\n\n\nTo retrieve logs from the launchd service, add the StandardOutPath and StandardErrorPath keys to the .plist file. These keys will redirect the standard output (stdout) and standard error (stderr) to specified log files.\n\n\n\nTo check the launchd status for mvsqlite, use the launchctl list command:\nlaunchctl list | grep mvstore\n\n\n\n\nAutomating tasks with launchd can save time and reduce the risk of errors. It also provides a standardized way to manage services on macOS.\n\n\n\nThe main downside is that launchd is specific to macOS, so this solution won’t work on other operating systems.\n\n\n\nAn alternative approach could be to use cron jobs or another task scheduler, but these may not offer the same level of control and flexibility as launchd.\n\n\n\nThis solution is most useful for developers who frequently need to run certain commands at system startup. It may be less relevant for casual users or those who don’t use macOS.\n\n\n\nThis solution was developed in-house by the V-Sekai development team.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAssistance provided by Aria, an AI assistant."
+    "text": "Status: Proposed\nDeciders: V-Sekai, Fire\nTags: Backend Management, Neon, Ease-of-Use, Postgres\n\n\n\n\nV-Sekai’s current setup with Postgres and Uro is hitting roadblocks due to the lack of dedicated server management expertise.\n\n\n\nIs Neon the key to a more manageable Postgres system that fits our community-driven model?\n\n\n\nWe plan to run a Neon pilot to see if it eases our backend management woes. Steps include:\n\nTesting Neon’s compatibility with our current data.\nExploring Neon’s manageability features.\nDrafting straightforward documentation for team reference.\nEnsuring a hassle-free data migration process.\n\n\n\n\n\nA more user-friendly backend system.\nReduced need for server management know-how.\nPotential performance benefits are a bonus.\n\n\n\n\n\nTime investment in learning a new system.\nPossible initial dependence on external support.\n\n\n\n\nSticking with Uro or other complex solutions that don’t align with our manageability goals.\n\n\n\nSituations where Uro’s specific configurations are essential; these will require special attention.\n\n\n\nPlanning to make Neon a central part of our backend, relying on our collective skills to implement it.\n\n\n\n\nV-Sekai on GitHub\nNeon’s Architecture\n\nThis article was assisted by AI."
   },
   {
-    "objectID": "decisions/20240502-mvsqlite-launchd.html#context",
-    "href": "decisions/20240502-mvsqlite-launchd.html#context",
-    "title": "Proposed: Launching the mvsqlite rdbms server",
+    "objectID": "decisions/20231108-neon-postgresql.html#metadata",
+    "href": "decisions/20231108-neon-postgresql.html#metadata",
+    "title": "Proposed: Adopting Neon for a More Manageable Backend at V-Sekai",
     "section": "",
-    "text": "In software development and maintenance, automation of routine tasks is crucial for efficiency. One such task is launching a database server at system startup. For macOS users, this can be achieved using launchd, an open-source service management framework. In this context, we are specifically interested in automating the launch of the mvsqlite RDBMS server."
+    "text": "Status: Proposed\nDeciders: V-Sekai, Fire\nTags: Backend Management, Neon, Ease-of-Use, Postgres"
   },
   {
-    "objectID": "decisions/20240502-mvsqlite-launchd.html#problem-statement",
-    "href": "decisions/20240502-mvsqlite-launchd.html#problem-statement",
-    "title": "Proposed: Launching the mvsqlite rdbms server",
+    "objectID": "decisions/20231108-neon-postgresql.html#the-backdrop",
+    "href": "decisions/20231108-neon-postgresql.html#the-backdrop",
+    "title": "Proposed: Adopting Neon for a More Manageable Backend at V-Sekai",
     "section": "",
-    "text": "The task at hand is to create a launchd service for macOS that will automatically run the following command at system startup:\n/usr/local/bin/mvstore --data-plane 127.0.0.1:7000 --admin-api 127.0.0.1:7001 --metadata-prefix mvstore-test --raw-data-prefix m --auto-create-namespace --cluster /usr/local/etc/foundationdb/fdb.cluster\nAdditionally, we need to be able to retrieve logs from this service and check its status."
+    "text": "V-Sekai’s current setup with Postgres and Uro is hitting roadblocks due to the lack of dedicated server management expertise."
   },
   {
-    "objectID": "decisions/20240502-mvsqlite-launchd.html#solution",
-    "href": "decisions/20240502-mvsqlite-launchd.html#solution",
-    "title": "Proposed: Launching the mvsqlite rdbms server",
+    "objectID": "decisions/20231108-neon-postgresql.html#the-challenge",
+    "href": "decisions/20231108-neon-postgresql.html#the-challenge",
+    "title": "Proposed: Adopting Neon for a More Manageable Backend at V-Sekai",
     "section": "",
-    "text": "To solve this problem, we can create a .plist file in the ~/Library/LaunchAgents directory. This file will define our launchd service and specify the command it should run. We can also add keys to redirect the standard output and error to log files. Finally, we can use the launchctl list command to check the status of our service.\nHere are the detailed steps:\n\n\n\nOpen Terminal and navigate to the LaunchAgents directory:\n\ncd ~/Library/LaunchAgents\n\nCreate a new .plist file called com.user.mvstore.plist:\n\ntouch com.user.mvstore.plist\n\nOpen the file with a text editor (e.g., nano):\n\nnano com.user.mvstore.plist\n\nPaste the following content into the file:\n\n&lt;?xml version=\"1.0\" encoding=\"UTF-8\"?&gt;\n&lt;!DOCTYPE plist PUBLIC \"-//Apple//DTD PLIST 1.0//EN\" \"http://www.apple.com/DTDs/PropertyList-1.0.dtd\"&gt;\n&lt;plist version=\"1.0\"&gt;\n&lt;dict&gt;\n    &lt;key&gt;Label&lt;/key&gt;\n    &lt;string&gt;com.user.mvstore&lt;/string&gt;\n    &lt;key&gt;ProgramArguments&lt;/key&gt;\n    &lt;array&gt;\n        &lt;string&gt;/usr/local/bin/mvstore&lt;/string&gt;\n        &lt;string&gt;--data-plane&lt;/string&gt;\n        &lt;string&gt;127.0.0.1:7000&lt;/string&gt;\n        &lt;string&gt;--admin-api&lt;/string&gt;\n        &lt;string&gt;127.0.0.1:7001&lt;/string&gt;\n        &lt;string&gt;--metadata-prefix&lt;/string&gt;\n        &lt;string&gt;mvstore-test&lt;/string&gt;\n        &lt;string&gt;--raw-data-prefix&lt;/string&gt;\n        &lt;string&gt;m&lt;/string&gt;\n        &lt;string&gt;--auto-create-namespace&lt;/string&gt;\n        &lt;string&gt;--cluster&lt;/string&gt;\n        &lt;string&gt;/usr/local/etc/foundationdb/fdb.cluster&lt;/string&gt;\n    &lt;/array&gt;\n    &lt;key&gt;RunAtLoad&lt;/key&gt;\n    &lt;true/&gt;\n    &lt;key&gt;EnvironmentVariables&lt;/key&gt;\n    &lt;dict&gt;\n        &lt;key&gt;RUST_LOG&lt;/key&gt;\n        &lt;string&gt;info&lt;/string&gt;\n        &lt;key&gt;DYLD_LIBRARY_PATH&lt;/key&gt;\n        &lt;string&gt;/usr/local/lib&lt;/string&gt;\n    &lt;/dict&gt;\n&lt;/dict&gt;\n&lt;/plist&gt;\n\nSave and close the file.\nLoad the new service:\n\nlaunchctl load ~/Library/LaunchAgents/com.user.mvstore.plist\n\n\n\nTo retrieve logs from the launchd service, add the StandardOutPath and StandardErrorPath keys to the .plist file. These keys will redirect the standard output (stdout) and standard error (stderr) to specified log files.\n\n\n\nTo check the launchd status for mvsqlite, use the launchctl list command:\nlaunchctl list | grep mvstore"
+    "text": "Is Neon the key to a more manageable Postgres system that fits our community-driven model?"
   },
   {
-    "objectID": "decisions/20240502-mvsqlite-launchd.html#benefits",
-    "href": "decisions/20240502-mvsqlite-launchd.html#benefits",
-    "title": "Proposed: Launching the mvsqlite rdbms server",
+    "objectID": "decisions/20231108-neon-postgresql.html#the-strategy",
+    "href": "decisions/20231108-neon-postgresql.html#the-strategy",
+    "title": "Proposed: Adopting Neon for a More Manageable Backend at V-Sekai",
     "section": "",
-    "text": "Automating tasks with launchd can save time and reduce the risk of errors. It also provides a standardized way to manage services on macOS."
+    "text": "We plan to run a Neon pilot to see if it eases our backend management woes. Steps include:\n\nTesting Neon’s compatibility with our current data.\nExploring Neon’s manageability features.\nDrafting straightforward documentation for team reference.\nEnsuring a hassle-free data migration process."
   },
   {
-    "objectID": "decisions/20240502-mvsqlite-launchd.html#downsides",
-    "href": "decisions/20240502-mvsqlite-launchd.html#downsides",
-    "title": "Proposed: Launching the mvsqlite rdbms server",
+    "objectID": "decisions/20231108-neon-postgresql.html#the-upside",
+    "href": "decisions/20231108-neon-postgresql.html#the-upside",
+    "title": "Proposed: Adopting Neon for a More Manageable Backend at V-Sekai",
     "section": "",
-    "text": "The main downside is that launchd is specific to macOS, so this solution won’t work on other operating systems."
+    "text": "A more user-friendly backend system.\nReduced need for server management know-how.\nPotential performance benefits are a bonus."
   },
   {
-    "objectID": "decisions/20240502-mvsqlite-launchd.html#the-road-not-taken",
-    "href": "decisions/20240502-mvsqlite-launchd.html#the-road-not-taken",
-    "title": "Proposed: Launching the mvsqlite rdbms server",
+    "objectID": "decisions/20231108-neon-postgresql.html#the-downside",
+    "href": "decisions/20231108-neon-postgresql.html#the-downside",
+    "title": "Proposed: Adopting Neon for a More Manageable Backend at V-Sekai",
     "section": "",
-    "text": "An alternative approach could be to use cron jobs or another task scheduler, but these may not offer the same level of control and flexibility as launchd."
+    "text": "Time investment in learning a new system.\nPossible initial dependence on external support."
   },
   {
-    "objectID": "decisions/20240502-mvsqlite-launchd.html#infrequent-use-case",
-    "href": "decisions/20240502-mvsqlite-launchd.html#infrequent-use-case",
-    "title": "Proposed: Launching the mvsqlite rdbms server",
+    "objectID": "decisions/20231108-neon-postgresql.html#the-road-not-taken",
+    "href": "decisions/20231108-neon-postgresql.html#the-road-not-taken",
+    "title": "Proposed: Adopting Neon for a More Manageable Backend at V-Sekai",
     "section": "",
-    "text": "This solution is most useful for developers who frequently need to run certain commands at system startup. It may be less relevant for casual users or those who don’t use macOS."
+    "text": "Sticking with Uro or other complex solutions that don’t align with our manageability goals."
   },
   {
-    "objectID": "decisions/20240502-mvsqlite-launchd.html#in-core-and-done-by-us",
-    "href": "decisions/20240502-mvsqlite-launchd.html#in-core-and-done-by-us",
-    "title": "Proposed: Launching the mvsqlite rdbms server",
+    "objectID": "decisions/20231108-neon-postgresql.html#the-infrequent-use-case",
+    "href": "decisions/20231108-neon-postgresql.html#the-infrequent-use-case",
+    "title": "Proposed: Adopting Neon for a More Manageable Backend at V-Sekai",
     "section": "",
-    "text": "This solution was developed in-house by the V-Sekai development team."
+    "text": "Situations where Uro’s specific configurations are essential; these will require special attention."
   },
   {
-    "objectID": "decisions/20240502-mvsqlite-launchd.html#status",
-    "href": "decisions/20240502-mvsqlite-launchd.html#status",
-    "title": "Proposed: Launching the mvsqlite rdbms server",
+    "objectID": "decisions/20231108-neon-postgresql.html#in-core-and-done-by-us",
+    "href": "decisions/20231108-neon-postgresql.html#in-core-and-done-by-us",
+    "title": "Proposed: Adopting Neon for a More Manageable Backend at V-Sekai",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "Planning to make Neon a central part of our backend, relying on our collective skills to implement it."
   },
   {
-    "objectID": "decisions/20240502-mvsqlite-launchd.html#decision-makers",
-    "href": "decisions/20240502-mvsqlite-launchd.html#decision-makers",
-    "title": "Proposed: Launching the mvsqlite rdbms server",
+    "objectID": "decisions/20231108-neon-postgresql.html#further-reading",
+    "href": "decisions/20231108-neon-postgresql.html#further-reading",
+    "title": "Proposed: Adopting Neon for a More Manageable Backend at V-Sekai",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "V-Sekai on GitHub\nNeon’s Architecture\n\nThis article was assisted by AI."
   },
   {
-    "objectID": "decisions/20240502-mvsqlite-launchd.html#tags",
-    "href": "decisions/20240502-mvsqlite-launchd.html#tags",
-    "title": "Proposed: Launching the mvsqlite rdbms server",
+    "objectID": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html",
+    "href": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html",
+    "title": "Proposed: Run the maintenance scripts from Windows in Unix mode with msys2",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Status: proposed &lt;– draft | rejected | accepted | deprecated | superseded by –&gt;\n\n\n\nI want to use Unix tools but the experience of Linux is lacking.\n\n\n\nUse msys2 on Windows to improve this.\n\n\n\n\nInstall Windows 10 or Windows 11\nOpen Powershell.\nSet-ExecutionPolicy RemoteSigned -scope CurrentUser\niwr -useb get.scoop.sh | iex\nscoop install msys\nmsys2 Restart to setup msys2.\npacman -S ssh-pageant openssh git python3\nCopy to ~/.bashrc\neval $(/usr/bin/ssh-pageant -r -a \"/tmp/.ssh-pageant-$USERNAME\")\n\n\n\n\n\n[e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]\n[…]\n\n\n\n\n\nI can use the better experience of Windows without the frustration of Linux.\n\n[this section can be repeated for each option if more than one option is open for consideration]\n\n\n\n\nOption: \nRejection Reason: \n\n\n\n\nThis is a quality of life improvement.\n\n\n\nI use this.\n\n\n\n\nhttps://www.msys2.org/\nhttps://github.com/cuviper/ssh-pageant\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240502-mvsqlite-launchd.html#further-reading",
-    "href": "decisions/20240502-mvsqlite-launchd.html#further-reading",
-    "title": "Proposed: Launching the mvsqlite rdbms server",
+    "objectID": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html#context-and-problem-statement",
+    "href": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html#context-and-problem-statement",
+    "title": "Proposed: Run the maintenance scripts from Windows in Unix mode with msys2",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAssistance provided by Aria, an AI assistant."
+    "text": "I want to use Unix tools but the experience of Linux is lacking."
   },
   {
-    "objectID": "decisions/20210724-Spreadsheet-animation-preview.html",
-    "href": "decisions/20210724-Spreadsheet-animation-preview.html",
-    "title": "Proposed: Spreadsheet Animation Preview",
+    "objectID": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: Run the maintenance scripts from Windows in Unix mode with msys2",
     "section": "",
-    "text": "Proposed: Spreadsheet Animation Preview\n\nContext and Problem Statement\nWorkflow for QA testing animations\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nLoad in a spreadsheet dataview of animation tracks and play animation back.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nWork on https://github.com/V-Sekai/godot-hop-spin-dance.\n\nDisplay a spreadsheet view.\n\n\n\n\nKey\nEN\nAnimation\nQueue Play\n\n\n\n\n\n\n\n\n\n\n\n\nShow the debug animation tree.\nShow graphical playback on a VRM character\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot trivial, combines a spreadsheet with animations, an animation tree debugger and a animation player.\n\n\nPositive Consequences\nAble to QA animations easier.\n\n\nNegative Consequences\nA sizable amount of work.\n\n\nIs there a reason why this should be core and done by us?\nWe care about characters.\n\n\nReferences\nGDC 2021 Summer:\n\n‘Genshin Impact’: Building a Scalable AI System This session reviews some of AI programming challenges in developing open-world game ‘Genshin Impact’ and describes several handful methods to improve AI system scalability. It details an AI framework and production pipeline that allow designers to craft huge amount of AI archetypes quickly and flexibly. Next, Genshin’s pathfinding service is introduced, an approach to reduce NavMesh disk and memory space overhead, caused by continuously-growing world map. Finally, this session discusses AI performance optimization and shows how AI system can be modularized and broke down into multi-threaded tasks on CPU.\nEmotional Systemic Facial of ‘Last of Us Part II’ As graphic fidelity in video games has rapidly accelerated, one aspect of development has overwhelmingly remained stagnant; in-game character emotions. In this talk, Naughty Dog explores how they addressed this industry wide limitation in The Last of Us Part II. Represented by team members from character rigging, animation, dialog, and design; this talk comprehensively covers how character emotion was brought into gameplay ranging from nuanced narrative moments to adrenaline charged melee combat. Learn about the challenges, implementation, and innovation that occurred to develop the systemic emotion system that brought over 65 characters speaking 13 languages with up to 20 individual emotions to life.\nMotion Matching in ‘The Last of Us Part II’ Naughty Dog is known for the animation quality of their titles. For The Last of Us Part II, they decided to take a leap of faith and switch to at that time pretty experimental animation system called Motion Matching. Two Naughty Dog technical animators will tell you the story of initial joy, later frustration and ultimate fear as the development of the new project went on and but not everything went according to plan. Thanks to many clever solution, hard work and a very talented team, Naughty Dog was able to ship a game that was unanimously praised for animation quality among critics and players.\nhttps://tabletomarkdown.com/convert-spreadsheet-to-markdown/\nhttps://github.com/deflinhec/GodotGoogleSheet\nhttps://baserow.io/\nhttps://github.com/fenix-hub/godot-engine.easy-charts\nhttps://github.com/godotengine/godot/pull/32408\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Use msys2 on Windows to improve this."
   },
   {
-    "objectID": "decisions/20221205-port-renik-to-many-bone-ik.html",
-    "href": "decisions/20221205-port-renik-to-many-bone-ik.html",
-    "title": "Proposed: Port RENIK to Many Bone IK for better quality",
+    "objectID": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Run the maintenance scripts from Windows in Unix mode with msys2",
     "section": "",
-    "text": "Status: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nRenik is a character controller and many bone ik is an ik solver. We have not merged them.\nThe quality is low for the FABRIK solver.\n\n\n\nWe wish to merge many bone ik and renik to improve quality.\n\n\n\n\nReplace renik’s usage of FABRIK with many bone ik.\n\n\n\n\n\nBetter animation quality\n\n\n\n\n\n\n\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\n\nIK is hard and not a few lines of code.\n\n\n\nWe know how to do it.\n\n\n\n\nV-Sekai\n\n\n\n\nMIT License\n\nCopyright (c) 2018-2022 SaracenOne\nCopyright (c) 2019-2022 K. S. Ernest (iFire) Lee (fire)\nCopyright (c) 2020-2022 Lyuma\nCopyright (c) 2020-2022 MMMaellon\nCopyright (c) 2022 V-Sekai Contributors\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
+    "text": "Install Windows 10 or Windows 11\nOpen Powershell.\nSet-ExecutionPolicy RemoteSigned -scope CurrentUser\niwr -useb get.scoop.sh | iex\nscoop install msys\nmsys2 Restart to setup msys2.\npacman -S ssh-pageant openssh git python3\nCopy to ~/.bashrc\neval $(/usr/bin/ssh-pageant -r -a \"/tmp/.ssh-pageant-$USERNAME\")"
   },
   {
-    "objectID": "decisions/20221205-port-renik-to-many-bone-ik.html#context-and-problem-statement",
-    "href": "decisions/20221205-port-renik-to-many-bone-ik.html#context-and-problem-statement",
-    "title": "Proposed: Port RENIK to Many Bone IK for better quality",
+    "objectID": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html#positive-consequences",
+    "href": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html#positive-consequences",
+    "title": "Proposed: Run the maintenance scripts from Windows in Unix mode with msys2",
     "section": "",
-    "text": "Renik is a character controller and many bone ik is an ik solver. We have not merged them.\nThe quality is low for the FABRIK solver."
+    "text": "[e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]\n[…]"
   },
   {
-    "objectID": "decisions/20221205-port-renik-to-many-bone-ik.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20221205-port-renik-to-many-bone-ik.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: Port RENIK to Many Bone IK for better quality",
+    "objectID": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html#negative-consequences",
+    "href": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html#negative-consequences",
+    "title": "Proposed: Run the maintenance scripts from Windows in Unix mode with msys2",
     "section": "",
-    "text": "We wish to merge many bone ik and renik to improve quality."
+    "text": "I can use the better experience of Windows without the frustration of Linux.\n\n[this section can be repeated for each option if more than one option is open for consideration]"
   },
   {
-    "objectID": "decisions/20221205-port-renik-to-many-bone-ik.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20221205-port-renik-to-many-bone-ik.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Port RENIK to Many Bone IK for better quality",
+    "objectID": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html#option-graveyard",
+    "href": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html#option-graveyard",
+    "title": "Proposed: Run the maintenance scripts from Windows in Unix mode with msys2",
     "section": "",
-    "text": "Replace renik’s usage of FABRIK with many bone ik."
+    "text": "Option: \nRejection Reason:"
   },
   {
-    "objectID": "decisions/20221205-port-renik-to-many-bone-ik.html#positive-consequences",
-    "href": "decisions/20221205-port-renik-to-many-bone-ik.html#positive-consequences",
-    "title": "Proposed: Port RENIK to Many Bone IK for better quality",
+    "objectID": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Run the maintenance scripts from Windows in Unix mode with msys2",
     "section": "",
-    "text": "Better animation quality"
+    "text": "This is a quality of life improvement."
   },
   {
-    "objectID": "decisions/20221205-port-renik-to-many-bone-ik.html#option-graveyard",
-    "href": "decisions/20221205-port-renik-to-many-bone-ik.html#option-graveyard",
-    "title": "Proposed: Port RENIK to Many Bone IK for better quality",
+    "objectID": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Run the maintenance scripts from Windows in Unix mode with msys2",
     "section": "",
-    "text": "Option: The status quo. \nRejection Reason: This solves nothing."
+    "text": "I use this."
   },
   {
-    "objectID": "decisions/20221205-port-renik-to-many-bone-ik.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20221205-port-renik-to-many-bone-ik.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Port RENIK to Many Bone IK for better quality",
+    "objectID": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html#references",
+    "href": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html#references",
+    "title": "Proposed: Run the maintenance scripts from Windows in Unix mode with msys2",
     "section": "",
-    "text": "IK is hard and not a few lines of code."
+    "text": "https://www.msys2.org/\nhttps://github.com/cuviper/ssh-pageant"
   },
   {
-    "objectID": "decisions/20221205-port-renik-to-many-bone-ik.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20221205-port-renik-to-many-bone-ik.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Port RENIK to Many Bone IK for better quality",
+    "objectID": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html#derivative-license",
+    "href": "decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html#derivative-license",
+    "title": "Proposed: Run the maintenance scripts from Windows in Unix mode with msys2",
     "section": "",
-    "text": "We know how to do it."
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20221205-port-renik-to-many-bone-ik.html#references",
-    "href": "decisions/20221205-port-renik-to-many-bone-ik.html#references",
-    "title": "Proposed: Port RENIK to Many Bone IK for better quality",
+    "objectID": "decisions/20210811-spoke-to-v-sekai.html",
+    "href": "decisions/20210811-spoke-to-v-sekai.html",
+    "title": "Proposed: Spoke to V-Sekai",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Proposed: Spoke to V-Sekai\n\nContext and Problem Statement\nWe desire portable content.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nCreate an art workflow.\n[Blender] -&gt; [OMI.glb]\n[OMI.glb] -&gt; [Godot Engine Packed Scene]\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nCreate an OMI Blender addon under W3C license.\nCreate glTF2 extension pull request for Godot Engine.\nFlow:\n\nOMI importer to Blender\nExporter of extended blender with OMI extensions to extended gltf\nSupport for OMI extended gltf in godot with definition of in-memory format for OMI extensions in Godot Engine for bidirectionality.\n\nExpected output:\n\nExport/Import as OMI format in Blender\nSupport OMI GLB in Godot\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nInterlapping projects are complicated.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nCan collaborate with Mozilla hubs team and OMI.\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20221205-port-renik-to-many-bone-ik.html#license-of-the-contribution",
-    "href": "decisions/20221205-port-renik-to-many-bone-ik.html#license-of-the-contribution",
-    "title": "Proposed: Port RENIK to Many Bone IK for better quality",
+    "objectID": "decisions/20230531-godot-engine-learning.html",
+    "href": "decisions/20230531-godot-engine-learning.html",
+    "title": "Proposed: Propose a solution to improve V-Sekai contributors’ design skills for navigating 3D environments",
     "section": "",
-    "text": "MIT License\n\nCopyright (c) 2018-2022 SaracenOne\nCopyright (c) 2019-2022 K. S. Ernest (iFire) Lee (fire)\nCopyright (c) 2020-2022 Lyuma\nCopyright (c) 2020-2022 MMMaellon\nCopyright (c) 2022 V-Sekai Contributors\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, GPT-4\n\n\n\n\nV-Sekai contributors lack the knowledge to create decent designs for navigating complex 3D environments with obstacles and walls, limiting user experience and potential applications.\n\n\n\nDevelop a comprehensive training program for V-Sekai contributors that focuses on designing effective navigation systems for complex 3D environments.\n\n\n\n\nIdentify key concepts and best practices for designing navigation systems in 3D environments.\nCreate a curriculum that covers these concepts and best practices, including hands-on exercises and real-world examples.\nOrganize workshops or webinars led by experienced professionals in the field of 3D environment design.\nProvide access to resources such as articles, tutorials, and online courses for self-paced learning.\nEncourage collaboration and peer review among contributors to share knowledge and improve designs.\nEvaluate contributors’ progress and provide feedback to ensure continuous improvement.\n\n\n\n\n\nImproved design skills among V-Sekai contributors.\nEnhanced user experience and potential applications.\nIncreased collaboration and knowledge sharing within the community.\n\n\n\n\n\nAdditional time and resources required for training and development.\nPotential delays in project timelines due to training commitments.\n\n\n\n\n\nHiring external designers with expertise in 3D environment navigation.\nIgnoring the issue and continuing with suboptimal designs.\n\n\n\n\nNo simple workaround; a comprehensive training program is necessary to improve contributors’ design skills for navigating 3D environments.\n\n\n\nInvesting in the development of V-Sekai contributors’ design skills is essential for enhancing user experience and expanding the potential applications of the platform.\n\n\n\n\nV-Sekai"
   },
   {
-    "objectID": "decisions/20240710-web-and-pcvr-networking.html",
-    "href": "decisions/20240710-web-and-pcvr-networking.html",
-    "title": "Proposed: Networking PCVR with the Web",
+    "objectID": "decisions/20230531-godot-engine-learning.html#metadata",
+    "href": "decisions/20230531-godot-engine-learning.html#metadata",
+    "title": "Proposed: Propose a solution to improve V-Sekai contributors’ design skills for navigating 3D environments",
     "section": "",
-    "text": "In the development of virtual reality (VR) applications, focusing on both PC-based VR (PCVR) and web platforms can provide a broader reach and enhanced user experience.\nNote: When referring to “web” in this document, it specifically means web desktop platforms and not WebXR.\nWe use Godot Engine 4.3 pre-release. PCVR uses OpenXR and the web uses threading.\n\n\n\nPCVR platforms must be able to communicate with the web platform in a low latency (UDP) network so the web can be a fallback to support everyone.\n\n\n\n\nCommunication Protocol: Implement a UDP-based communication protocol for low-latency data transfer between PCVR and web platforms.\nGodot’s Multiplayer API: Use Godot’s high-level multiplayer API to manage connections and data synchronization.\nCustom Patch for Godot WebRTC: Utilize our custom patch for Godot WebRTC for PCVR.\nStandard Browser WebRTC: Employ the standard browser WebRTC for the web.\n\n\n\nTo test the interoperability between PCVR and web platforms, we propose developing a simple real-time chat application. This will involve:\n\nA basic text input field and display area for messages on both PCVR and web platforms.\nEstablishing a UDP connection between the PCVR and web clients.\nUsing Godot’s high-level multiplayer API to handle message sending and receiving.\nEnsuring that messages sent from the PCVR client appear in real-time on the web client and vice versa.\n\nTo enhance the functionality and flexibility of the communication system, we propose implementing multiple channels for different types of data. This will allow for more organized and efficient data transfer. The channels could include:\n\nText Channel:\n\nFor sending and receiving text messages.\nUsed in the real-time chat application.\n\nVoice Channel:\n\nFor transmitting voice data.\nEnables real-time voice communication between PCVR and web clients.\n\nData Channel:\n\nFor sending miscellaneous data such as user actions, game state updates, etc.\nEnsures that non-textual data is transmitted efficiently.\n\n\n\n\n\n\n\nEnsures real-time interaction between PCVR and web platforms.\nExpands the user base by supporting both PCVR and web platforms.\nProvides seamless integration and interaction across different platforms.\n\n\n\n\n\nIncreased complexity in managing cross-platform communication.\nRequires ongoing maintenance and updates to ensure compatibility and performance.\n\n\n\n\nConsideration of other communication protocols like TCP, which may offer reliability but at the cost of higher latency.\n\n\n\nHandling scenarios where network conditions are poor or intermittent, requiring robust error handling and reconnection strategies.\n\n\n\nThis proposal involves integrating the solution directly into the core of the V-Sekai project, managed by the V-Sekai development team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\nfire\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, GPT-4"
   },
   {
-    "objectID": "decisions/20240710-web-and-pcvr-networking.html#the-context",
-    "href": "decisions/20240710-web-and-pcvr-networking.html#the-context",
-    "title": "Proposed: Networking PCVR with the Web",
+    "objectID": "decisions/20230531-godot-engine-learning.html#problem-statement",
+    "href": "decisions/20230531-godot-engine-learning.html#problem-statement",
+    "title": "Proposed: Propose a solution to improve V-Sekai contributors’ design skills for navigating 3D environments",
     "section": "",
-    "text": "In the development of virtual reality (VR) applications, focusing on both PC-based VR (PCVR) and web platforms can provide a broader reach and enhanced user experience.\nNote: When referring to “web” in this document, it specifically means web desktop platforms and not WebXR.\nWe use Godot Engine 4.3 pre-release. PCVR uses OpenXR and the web uses threading."
+    "text": "V-Sekai contributors lack the knowledge to create decent designs for navigating complex 3D environments with obstacles and walls, limiting user experience and potential applications."
   },
   {
-    "objectID": "decisions/20240710-web-and-pcvr-networking.html#the-problem-statement",
-    "href": "decisions/20240710-web-and-pcvr-networking.html#the-problem-statement",
-    "title": "Proposed: Networking PCVR with the Web",
+    "objectID": "decisions/20230531-godot-engine-learning.html#proposed-solution",
+    "href": "decisions/20230531-godot-engine-learning.html#proposed-solution",
+    "title": "Proposed: Propose a solution to improve V-Sekai contributors’ design skills for navigating 3D environments",
     "section": "",
-    "text": "PCVR platforms must be able to communicate with the web platform in a low latency (UDP) network so the web can be a fallback to support everyone."
+    "text": "Develop a comprehensive training program for V-Sekai contributors that focuses on designing effective navigation systems for complex 3D environments."
   },
   {
-    "objectID": "decisions/20240710-web-and-pcvr-networking.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240710-web-and-pcvr-networking.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Networking PCVR with the Web",
+    "objectID": "decisions/20230531-godot-engine-learning.html#implementation",
+    "href": "decisions/20230531-godot-engine-learning.html#implementation",
+    "title": "Proposed: Propose a solution to improve V-Sekai contributors’ design skills for navigating 3D environments",
     "section": "",
-    "text": "Communication Protocol: Implement a UDP-based communication protocol for low-latency data transfer between PCVR and web platforms.\nGodot’s Multiplayer API: Use Godot’s high-level multiplayer API to manage connections and data synchronization.\nCustom Patch for Godot WebRTC: Utilize our custom patch for Godot WebRTC for PCVR.\nStandard Browser WebRTC: Employ the standard browser WebRTC for the web.\n\n\n\nTo test the interoperability between PCVR and web platforms, we propose developing a simple real-time chat application. This will involve:\n\nA basic text input field and display area for messages on both PCVR and web platforms.\nEstablishing a UDP connection between the PCVR and web clients.\nUsing Godot’s high-level multiplayer API to handle message sending and receiving.\nEnsuring that messages sent from the PCVR client appear in real-time on the web client and vice versa.\n\nTo enhance the functionality and flexibility of the communication system, we propose implementing multiple channels for different types of data. This will allow for more organized and efficient data transfer. The channels could include:\n\nText Channel:\n\nFor sending and receiving text messages.\nUsed in the real-time chat application.\n\nVoice Channel:\n\nFor transmitting voice data.\nEnables real-time voice communication between PCVR and web clients.\n\nData Channel:\n\nFor sending miscellaneous data such as user actions, game state updates, etc.\nEnsures that non-textual data is transmitted efficiently."
+    "text": "Identify key concepts and best practices for designing navigation systems in 3D environments.\nCreate a curriculum that covers these concepts and best practices, including hands-on exercises and real-world examples.\nOrganize workshops or webinars led by experienced professionals in the field of 3D environment design.\nProvide access to resources such as articles, tutorials, and online courses for self-paced learning.\nEncourage collaboration and peer review among contributors to share knowledge and improve designs.\nEvaluate contributors’ progress and provide feedback to ensure continuous improvement."
   },
   {
-    "objectID": "decisions/20240710-web-and-pcvr-networking.html#the-benefits",
-    "href": "decisions/20240710-web-and-pcvr-networking.html#the-benefits",
-    "title": "Proposed: Networking PCVR with the Web",
+    "objectID": "decisions/20230531-godot-engine-learning.html#positive-consequences",
+    "href": "decisions/20230531-godot-engine-learning.html#positive-consequences",
+    "title": "Proposed: Propose a solution to improve V-Sekai contributors’ design skills for navigating 3D environments",
     "section": "",
-    "text": "Ensures real-time interaction between PCVR and web platforms.\nExpands the user base by supporting both PCVR and web platforms.\nProvides seamless integration and interaction across different platforms."
+    "text": "Improved design skills among V-Sekai contributors.\nEnhanced user experience and potential applications.\nIncreased collaboration and knowledge sharing within the community."
   },
   {
-    "objectID": "decisions/20240710-web-and-pcvr-networking.html#the-downsides",
-    "href": "decisions/20240710-web-and-pcvr-networking.html#the-downsides",
-    "title": "Proposed: Networking PCVR with the Web",
+    "objectID": "decisions/20230531-godot-engine-learning.html#negative-consequences",
+    "href": "decisions/20230531-godot-engine-learning.html#negative-consequences",
+    "title": "Proposed: Propose a solution to improve V-Sekai contributors’ design skills for navigating 3D environments",
     "section": "",
-    "text": "Increased complexity in managing cross-platform communication.\nRequires ongoing maintenance and updates to ensure compatibility and performance."
+    "text": "Additional time and resources required for training and development.\nPotential delays in project timelines due to training commitments."
   },
   {
-    "objectID": "decisions/20240710-web-and-pcvr-networking.html#the-road-not-taken",
-    "href": "decisions/20240710-web-and-pcvr-networking.html#the-road-not-taken",
-    "title": "Proposed: Networking PCVR with the Web",
+    "objectID": "decisions/20230531-godot-engine-learning.html#option-graveyard",
+    "href": "decisions/20230531-godot-engine-learning.html#option-graveyard",
+    "title": "Proposed: Propose a solution to improve V-Sekai contributors’ design skills for navigating 3D environments",
     "section": "",
-    "text": "Consideration of other communication protocols like TCP, which may offer reliability but at the cost of higher latency."
+    "text": "Hiring external designers with expertise in 3D environment navigation.\nIgnoring the issue and continuing with suboptimal designs."
   },
   {
-    "objectID": "decisions/20240710-web-and-pcvr-networking.html#the-infrequent-use-case",
-    "href": "decisions/20240710-web-and-pcvr-networking.html#the-infrequent-use-case",
-    "title": "Proposed: Networking PCVR with the Web",
+    "objectID": "decisions/20230531-godot-engine-learning.html#enhancement-workaround",
+    "href": "decisions/20230531-godot-engine-learning.html#enhancement-workaround",
+    "title": "Proposed: Propose a solution to improve V-Sekai contributors’ design skills for navigating 3D environments",
     "section": "",
-    "text": "Handling scenarios where network conditions are poor or intermittent, requiring robust error handling and reconnection strategies."
+    "text": "No simple workaround; a comprehensive training program is necessary to improve contributors’ design skills for navigating 3D environments."
   },
   {
-    "objectID": "decisions/20240710-web-and-pcvr-networking.html#in-core-and-done-by-us",
-    "href": "decisions/20240710-web-and-pcvr-networking.html#in-core-and-done-by-us",
-    "title": "Proposed: Networking PCVR with the Web",
+    "objectID": "decisions/20230531-godot-engine-learning.html#core-reasoning",
+    "href": "decisions/20230531-godot-engine-learning.html#core-reasoning",
+    "title": "Proposed: Propose a solution to improve V-Sekai contributors’ design skills for navigating 3D environments",
     "section": "",
-    "text": "This proposal involves integrating the solution directly into the core of the V-Sekai project, managed by the V-Sekai development team."
+    "text": "Investing in the development of V-Sekai contributors’ design skills is essential for enhancing user experience and expanding the potential applications of the platform."
   },
   {
-    "objectID": "decisions/20240710-web-and-pcvr-networking.html#status",
-    "href": "decisions/20240710-web-and-pcvr-networking.html#status",
-    "title": "Proposed: Networking PCVR with the Web",
+    "objectID": "decisions/20230531-godot-engine-learning.html#references",
+    "href": "decisions/20230531-godot-engine-learning.html#references",
+    "title": "Proposed: Propose a solution to improve V-Sekai contributors’ design skills for navigating 3D environments",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20240710-web-and-pcvr-networking.html#decision-makers",
-    "href": "decisions/20240710-web-and-pcvr-networking.html#decision-makers",
-    "title": "Proposed: Networking PCVR with the Web",
+    "objectID": "decisions/20211031-keep-a-changelog.html",
+    "href": "decisions/20211031-keep-a-changelog.html",
+    "title": "Accepted: Keep a changelog",
     "section": "",
-    "text": "V-Sekai development team\nfire"
+    "text": "Accepted: Keep a changelog\n\nStatus: accepted\n\n\nContext and Problem Statement\nHumans need to know what has changed\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nCopied from https://keepachangelog.com.\n\nWhat is a changelog?\n\n\nA changelog is a file which contains a curated, chronologically ordered list of notable changes for each version of a project. Why keep a changelog?\n\n\nTo make it easier for users and contributors to see precisely what notable changes have been made between each release (or version) of the project. Who needs a changelog?\n\n\nPeople do. Whether consumers or developers, the end users of software are human beings who care about what’s in the software. When the software changes, people want to know why and how.\n\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nKeep a changelog.\n\nUse the https://github.com/V-Sekai/v-sekai-proposals #repository as a placeholder.\nDelay migrations to main project #repository to a later date.\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot code.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nWe are the best to know what changed.\n\n\nReferences\n\nhttps://keepachangelog.com/en/1.0.0/\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240710-web-and-pcvr-networking.html#tags",
-    "href": "decisions/20240710-web-and-pcvr-networking.html#tags",
-    "title": "Proposed: Networking PCVR with the Web",
+    "objectID": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html",
+    "href": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html",
+    "title": "Proposed: Learn how to scale V-Sekai using bots and multipliers",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Status: proposed \nDeciders: V-Sekai,fire,\nTags: V-Sekai,\n\n\n\nWanted to scale V-Sekai.\n\n\n\nNeed find options to learn how to scale V-Sekai.\n\n\n\n\nBots\nMultiplier ghosts\n\n\n\n\n\nWe dream of more players.\n\n\n\n\n\nPainful engineering.\n\n\n\n\n\nOption: Paying $250 for 400 players per event.\nRejection Reason: Would work for a venture funded company in the Bay Area but hard for an opensoruce project.\n\n\n\n\nThis is an end to end integration test and it is trivial to setup bot creating but runs through all the systems.\n\n\n\nWe depend on the player load performance.\n\n\n\n\nhttps://github.com/V-Sekai/\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240710-web-and-pcvr-networking.html#further-reading",
-    "href": "decisions/20240710-web-and-pcvr-networking.html#further-reading",
-    "title": "Proposed: Networking PCVR with the Web",
+    "objectID": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html#context-and-problem-statement",
+    "href": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html#context-and-problem-statement",
+    "title": "Proposed: Learn how to scale V-Sekai using bots and multipliers",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "Wanted to scale V-Sekai."
   },
   {
-    "objectID": "decisions/20221022-have-larger-worlds-by-server-state-migration.html",
-    "href": "decisions/20221022-have-larger-worlds-by-server-state-migration.html",
-    "title": "Draft: Simulate larger 3d multiplayer worlds using “brickworlds partition layout”",
+    "objectID": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: Learn how to scale V-Sekai using bots and multipliers",
     "section": "",
-    "text": "Status: draft \nDeciders: V-Sekai,Fire,Groak,\nTags: V-Sekai,\n\n\n\nEach V-Sekai game server has a scalability limit. Transfer each player to a different server when needed.\n\n\n\n\nTransfer the state using a database that can handle commits in commit order despite parallel transactions.\nFoundationdb is used by Apple for their cloud services and is trusted to handle distributed data safely.\nGodot Engine is a game engine where the interiors are easy to rearrange.\nSqlite is a well written database that is fully tested.\nRust is a good language for failures in math or computer language, but does not handle non code errors (like cosmic rays) through language based software redundancy like Erlang.\nMvsqlite merges sqlite with Foundationdb with Rust glue.\n\n\n\n\nPartition the world into tiles via Prasetya, Kusno’s design.\n\n\n\nDefine the tiles with a premigration and migration border.\n\nPremigration and migration border via Prasetya, Kusno’s design.\n\n\nTransfer the player from one server to another by first syncing all the frames, and have the player connect to the other side. Then the server does the transfer and the player disconnects from the previous side when the migration boundary is hit.\n\nServer state transfer.\n\nTest using a multiplayer simulator via Prasetya, Kusno’s design\n\n\n\n\n\n\nAllows player transfer from one server to the others servers.\n\n\n\n\n\nNeeds to connect the servers to the foundation database simulation servers.\n\n\n\n\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\n\nIt’s not a few lines of script.\n\n\n\nWe maintain the networking stack.\n\n\n\n\nV-Sekai\nEfficient_Methods_for_Improving_Scalability_and_Playability_of_Massively_Multiplayer_Online_Game_MMOG by Prasetya, Kusno\ngodot sqlite mvsqlite\ngodot mvsql demo\nmvsqlite for windows\nmvsqlite\nApple’s foundationdb\nRust lang\nSpecial thanks to the TigerBeetle for the sql schema\n\n\n\n\n\n\nextends Node3D\n\nfunc _ready():\n    var db : SQLite = SQLite.new();\n    if (!db.open(\"test\")):\n        print(\"Failed opening database.\");\n        return;\n    var _drop : String = \"\"\"drop table if exists entity;\n\"\"\"\n    var _create_entity_table : String = \"\"\"\nCREATE TABLE entity (\n    id TEXT PRIMARY KEY NOT NULL CHECK(LENGTH(id) = 36),\n    user_data blob NOT NULL CHECK( LENGTH(user_data) = 16) DEFAULT (zeroblob(16)),\n    reserved blob NOT NULL CHECK( LENGTH(reserved) = 48)  DEFAULT (zeroblob(48)),\n    shard   INTEGER NOT NULL,\n    code    INTEGER NOT NULL,\n    flags   INTEGER NOT NULL,\n    past_pending    BLOB NOT NULL CHECK( LENGTH(past_pending) &lt;= 1024) DEFAULT (zeroblob(64)),\n    past_posted BLOB NOT NULL CHECK( LENGTH(past_posted) &lt;= 1024) DEFAULT (zeroblob(64)),\n    current_pending BLOB NOT NULL CHECK( LENGTH(current_pending) &lt;= 1024) DEFAULT (zeroblob(64)),\n    current_posted  BLOB NOT NULL CHECK( LENGTH(current_posted) &lt;= 1024) DEFAULT (zeroblob(64)),\n    timestamp INTEGER NOT NULL\n) WITHOUT ROWID, STRICT;\n\"\"\"\n#   db.query(create_entity_table)\n    var _truncate_entities : String = \"\"\"\nDELETE FROM entity;\n    \"\"\"\n#   db.query(truncate_entities)\n    for i in range(32):\n        var node_3d : Node3D = Node3D.new()\n        var script = load(\"res://sqlite_write/sqlite_write_scene.gd\")\n        node_3d.set_script(script)\n        add_child(node_3d, true)\n        node_3d.owner = self\n\n\n\nextends Node3D\n\nvar db : SQLite = null\nvar result_create : SQLiteQuery\nvar result_delete : SQLiteQuery\nvar uuid : String\n\nfunc _ready():\n    db = SQLite.new();\n    if (!db.open(\"test\")):\n        print(\"Failed opening database.\");\n        return;\n\n    var select_uuid : String = \"\"\"\n    SELECT lower(hex(randomblob(4)) || '-' || hex(randomblob(2)) || '-' || '4' ||\n    substr(hex( randomblob(2)), 2) || '-' ||\n    substr('AB89', 1 + (abs(random()) % 4) , 1)  ||\n    substr(hex(randomblob(2)), 2) || '-' ||\n    hex(randomblob(6))) as uuid;\n    \"\"\"\n    uuid = db.fetch_array(select_uuid)[0][\"uuid\"]\n    var query_create_original = \"\"\"\nINSERT INTO entity (\"id\", \"user_data\", \"reserved\", \"shard\", \"code\", \"flags\", \"past_pending\", \"past_posted\",\n\"current_pending\", \"current_posted\", \"timestamp\")\nVALUES (?, zeroblob(16), zeroblob(48), 0, 0, 0, zeroblob(64), zeroblob(64), zeroblob(64), ?, UNIXEPOCH());\n\"\"\"\n    result_create = db.create_query(query_create_original)\n    var query_delete = \"\"\"\n    DELETE FROM entity\n    WHERE id = ?;\n\"\"\"\n    result_delete = db.create_query(query_delete)\n\nfunc _process(_delta):\n    if db == null:\n        return\n    var packed_array : Array = Array()\n    packed_array.push_back(global_transform)\n    var bytes : PackedByteArray = var_to_bytes(packed_array)\n    bytes = bytes.compress(FileAccess.COMPRESSION_ZSTD)\n    var statement : Array = [uuid, bytes]\n    var _result_batch = result_create.batch_execute([statement])\n\nfunc _exit_tree():\n    var statement : Array = [uuid]\n    var _result_batch = result_delete.batch_execute([statement])\n\n\n\n\ncmd\nscoop install llvm openssl-mingw llvm-mingw\ncargo build --release -p mvsqlite\ncd mvsqlite-sqlite3\nmingw32-make.exe build-patched-sqlite3\nset RUST_LOG=info\nset MVSQLITE_DATA_PLANE=http://localhost:7000\nsqlite3 test\n.tables\n\n\nfdbcli\nstatus\n# Force create a database\n# configure new single memory\n\n\n\nmsys2\ncurl http://localhost:7001/api/create_namespace -i -d '{\"key\":\"test\"}'\n\n\n\n# on Linux\nwget https://github.com/apple/foundationdb/releases/download/7.1.15/foundationdb-clients_7.1.15-1_amd64.deb\nsudo dpkg -i foundationdb-clients_7.1.15-1_amd64.deb\nwget https://github.com/apple/foundationdb/releases/download/7.1.15/foundationdb-server_7.1.15-1_amd64.deb\nsudo dpkg -i foundationdb-server_7.1.15-1_amd64.deb\ncargo build --release -p mvstore\nRUST_LOG=info ./mvstore \\\n  --data-plane 127.0.0.1:7000 \\\n  --admin-api 127.0.0.1:7001 \\\n  --metadata-prefix mvstore \\\n  --raw-data-prefix m\n\n\n\ncmd\ncargo build --release -p mvstore\nset RUST_LOG=info\nmvstore --data-plane 127.0.0.1:7000 --admin-api 127.0.0.1:7001 --metadata-prefix mvstore --raw-data-prefix m --cluster \"C:/ProgramData/foundationdb/fdb.cluster\"\n\n\n\n\n\n\nset RUST_LOG=info\nset MVSQLITE_DATA_PLANE=http://localhost:7000\nsqlite3 test\n\n\n\nset RUST_LOG=error\nmvstore --data-plane 127.0.0.1:7000 --admin-api 127.0.0.1:7001 --metadata-prefix mvstore --raw-data-prefix m --cluster \"C:/ProgramData/foundationdb/fdb.cluster\"\n\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Need find options to learn how to scale V-Sekai."
   },
   {
-    "objectID": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#context-and-problem-statement",
-    "href": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#context-and-problem-statement",
-    "title": "Draft: Simulate larger 3d multiplayer worlds using “brickworlds partition layout”",
+    "objectID": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Learn how to scale V-Sekai using bots and multipliers",
     "section": "",
-    "text": "Each V-Sekai game server has a scalability limit. Transfer each player to a different server when needed."
+    "text": "Bots\nMultiplier ghosts"
   },
   {
-    "objectID": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Draft: Simulate larger 3d multiplayer worlds using “brickworlds partition layout”",
+    "objectID": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html#positive-consequences",
+    "href": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html#positive-consequences",
+    "title": "Proposed: Learn how to scale V-Sekai using bots and multipliers",
     "section": "",
-    "text": "Transfer the state using a database that can handle commits in commit order despite parallel transactions.\nFoundationdb is used by Apple for their cloud services and is trusted to handle distributed data safely.\nGodot Engine is a game engine where the interiors are easy to rearrange.\nSqlite is a well written database that is fully tested.\nRust is a good language for failures in math or computer language, but does not handle non code errors (like cosmic rays) through language based software redundancy like Erlang.\nMvsqlite merges sqlite with Foundationdb with Rust glue."
+    "text": "We dream of more players."
   },
   {
-    "objectID": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Draft: Simulate larger 3d multiplayer worlds using “brickworlds partition layout”",
+    "objectID": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html#negative-consequences",
+    "href": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html#negative-consequences",
+    "title": "Proposed: Learn how to scale V-Sekai using bots and multipliers",
     "section": "",
-    "text": "Partition the world into tiles via Prasetya, Kusno’s design.\n\n\n\nDefine the tiles with a premigration and migration border.\n\nPremigration and migration border via Prasetya, Kusno’s design.\n\n\nTransfer the player from one server to another by first syncing all the frames, and have the player connect to the other side. Then the server does the transfer and the player disconnects from the previous side when the migration boundary is hit.\n\nServer state transfer.\n\nTest using a multiplayer simulator via Prasetya, Kusno’s design"
+    "text": "Painful engineering."
   },
   {
-    "objectID": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#positive-consequences",
-    "href": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#positive-consequences",
-    "title": "Draft: Simulate larger 3d multiplayer worlds using “brickworlds partition layout”",
+    "objectID": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html#option-graveyard",
+    "href": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html#option-graveyard",
+    "title": "Proposed: Learn how to scale V-Sekai using bots and multipliers",
     "section": "",
-    "text": "Allows player transfer from one server to the others servers."
+    "text": "Option: Paying $250 for 400 players per event.\nRejection Reason: Would work for a venture funded company in the Bay Area but hard for an opensoruce project."
   },
   {
-    "objectID": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#negative-consequences",
-    "href": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#negative-consequences",
-    "title": "Draft: Simulate larger 3d multiplayer worlds using “brickworlds partition layout”",
+    "objectID": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Learn how to scale V-Sekai using bots and multipliers",
     "section": "",
-    "text": "Needs to connect the servers to the foundation database simulation servers."
+    "text": "This is an end to end integration test and it is trivial to setup bot creating but runs through all the systems."
   },
   {
-    "objectID": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#option-graveyard",
-    "href": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#option-graveyard",
-    "title": "Draft: Simulate larger 3d multiplayer worlds using “brickworlds partition layout”",
+    "objectID": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Learn how to scale V-Sekai using bots and multipliers",
     "section": "",
-    "text": "Option: The status quo. \nRejection Reason: This solves nothing."
+    "text": "We depend on the player load performance."
   },
   {
-    "objectID": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Draft: Simulate larger 3d multiplayer worlds using “brickworlds partition layout”",
+    "objectID": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html#references",
+    "href": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html#references",
+    "title": "Proposed: Learn how to scale V-Sekai using bots and multipliers",
     "section": "",
-    "text": "It’s not a few lines of script."
+    "text": "https://github.com/V-Sekai/"
   },
   {
-    "objectID": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Draft: Simulate larger 3d multiplayer worlds using “brickworlds partition layout”",
+    "objectID": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html#derivative-license",
+    "href": "decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html#derivative-license",
+    "title": "Proposed: Learn how to scale V-Sekai using bots and multipliers",
     "section": "",
-    "text": "We maintain the networking stack."
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#references",
-    "href": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#references",
-    "title": "Draft: Simulate larger 3d multiplayer worlds using “brickworlds partition layout”",
+    "objectID": "decisions/20220203-create-default-animation-set.html",
+    "href": "decisions/20220203-create-default-animation-set.html",
+    "title": "Draft: To have a default set of motions on a 3d character by creating a default animation set",
     "section": "",
-    "text": "V-Sekai\nEfficient_Methods_for_Improving_Scalability_and_Playability_of_Massively_Multiplayer_Online_Game_MMOG by Prasetya, Kusno\ngodot sqlite mvsqlite\ngodot mvsql demo\nmvsqlite for windows\nmvsqlite\nApple’s foundationdb\nRust lang\nSpecial thanks to the TigerBeetle for the sql schema"
+    "text": "Status: draft \nDeciders: V-Sekai,tokage,fire,\nTags: V-Sekai,\n\n\n\nWanted to have a default list of animations set.\n\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\n\n\n\n\n\n\nInit\nNeutralFront\nNeutralRight\nNeutralLeft\nWalkFront\nWalkBack\nWalkRightFront\nWalkRightBack\nWalkLeftFront\nWalkLeftBack\nStrafeRight\nStrafeLeft\nSprintFront\nSprintBack\nSprintRightFront\nSprintRightBack\nSprintLeftFront\nSprintLeftFrontBack\nJump\nFall\nLand\n\n\n\n\nSit\n(NeutralToSit)\n(SitToNeutral)\nLay\n(NeutralToLay)\n(LayToNeutral)\n\n\n\n\n\nDuckNeutral\nDuckMoveFront\nDuckMoveBack\nDuckMoveRight\nDuckMoveLeft\n(DuckToSit)\n(SitToDuck)\n(DuckToLay)\n(LayToDuck)\nCrawlNeutral\nCrawlMoveFront\nCrawlMoveBack\nCrawlMoveRight\nCrawlMoveLeft\n(CrawlToSit)\n(SitToCrawl)\n(CrawlToLay)\n(LayToCrawl)\n(NeutralToDuck)\n(DuckToNeutral)\n(NeutralToCrawl)\n(CrawlToNeutral)\n(DuckToCrawl)\n(CrawlToDuck)\n\n\n\n\n\nChair\n\n\n\n\n\n\n\n[e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]\n\n\n\n\n\n[e.g., compromising quality attribute, follow-up decisions required, …]\n\n[this section can be repeated for each option if more than one option is open for consideration]\n\n\n\n\nOption: \nRejection Reason: \n\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\n\n\n\nIs there a reason why this should be core and done by us?\n\n\n\n\nLink type \n\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#code-references",
-    "href": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#code-references",
-    "title": "Draft: Simulate larger 3d multiplayer worlds using “brickworlds partition layout”",
+    "objectID": "decisions/20220203-create-default-animation-set.html#context-and-problem-statement",
+    "href": "decisions/20220203-create-default-animation-set.html#context-and-problem-statement",
+    "title": "Draft: To have a default set of motions on a 3d character by creating a default animation set",
     "section": "",
-    "text": "extends Node3D\n\nfunc _ready():\n    var db : SQLite = SQLite.new();\n    if (!db.open(\"test\")):\n        print(\"Failed opening database.\");\n        return;\n    var _drop : String = \"\"\"drop table if exists entity;\n\"\"\"\n    var _create_entity_table : String = \"\"\"\nCREATE TABLE entity (\n    id TEXT PRIMARY KEY NOT NULL CHECK(LENGTH(id) = 36),\n    user_data blob NOT NULL CHECK( LENGTH(user_data) = 16) DEFAULT (zeroblob(16)),\n    reserved blob NOT NULL CHECK( LENGTH(reserved) = 48)  DEFAULT (zeroblob(48)),\n    shard   INTEGER NOT NULL,\n    code    INTEGER NOT NULL,\n    flags   INTEGER NOT NULL,\n    past_pending    BLOB NOT NULL CHECK( LENGTH(past_pending) &lt;= 1024) DEFAULT (zeroblob(64)),\n    past_posted BLOB NOT NULL CHECK( LENGTH(past_posted) &lt;= 1024) DEFAULT (zeroblob(64)),\n    current_pending BLOB NOT NULL CHECK( LENGTH(current_pending) &lt;= 1024) DEFAULT (zeroblob(64)),\n    current_posted  BLOB NOT NULL CHECK( LENGTH(current_posted) &lt;= 1024) DEFAULT (zeroblob(64)),\n    timestamp INTEGER NOT NULL\n) WITHOUT ROWID, STRICT;\n\"\"\"\n#   db.query(create_entity_table)\n    var _truncate_entities : String = \"\"\"\nDELETE FROM entity;\n    \"\"\"\n#   db.query(truncate_entities)\n    for i in range(32):\n        var node_3d : Node3D = Node3D.new()\n        var script = load(\"res://sqlite_write/sqlite_write_scene.gd\")\n        node_3d.set_script(script)\n        add_child(node_3d, true)\n        node_3d.owner = self\n\n\n\nextends Node3D\n\nvar db : SQLite = null\nvar result_create : SQLiteQuery\nvar result_delete : SQLiteQuery\nvar uuid : String\n\nfunc _ready():\n    db = SQLite.new();\n    if (!db.open(\"test\")):\n        print(\"Failed opening database.\");\n        return;\n\n    var select_uuid : String = \"\"\"\n    SELECT lower(hex(randomblob(4)) || '-' || hex(randomblob(2)) || '-' || '4' ||\n    substr(hex( randomblob(2)), 2) || '-' ||\n    substr('AB89', 1 + (abs(random()) % 4) , 1)  ||\n    substr(hex(randomblob(2)), 2) || '-' ||\n    hex(randomblob(6))) as uuid;\n    \"\"\"\n    uuid = db.fetch_array(select_uuid)[0][\"uuid\"]\n    var query_create_original = \"\"\"\nINSERT INTO entity (\"id\", \"user_data\", \"reserved\", \"shard\", \"code\", \"flags\", \"past_pending\", \"past_posted\",\n\"current_pending\", \"current_posted\", \"timestamp\")\nVALUES (?, zeroblob(16), zeroblob(48), 0, 0, 0, zeroblob(64), zeroblob(64), zeroblob(64), ?, UNIXEPOCH());\n\"\"\"\n    result_create = db.create_query(query_create_original)\n    var query_delete = \"\"\"\n    DELETE FROM entity\n    WHERE id = ?;\n\"\"\"\n    result_delete = db.create_query(query_delete)\n\nfunc _process(_delta):\n    if db == null:\n        return\n    var packed_array : Array = Array()\n    packed_array.push_back(global_transform)\n    var bytes : PackedByteArray = var_to_bytes(packed_array)\n    bytes = bytes.compress(FileAccess.COMPRESSION_ZSTD)\n    var statement : Array = [uuid, bytes]\n    var _result_batch = result_create.batch_execute([statement])\n\nfunc _exit_tree():\n    var statement : Array = [uuid]\n    var _result_batch = result_delete.batch_execute([statement])"
+    "text": "Wanted to have a default list of animations set."
   },
   {
-    "objectID": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#mvsqlite-for-windows",
-    "href": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#mvsqlite-for-windows",
-    "title": "Draft: Simulate larger 3d multiplayer worlds using “brickworlds partition layout”",
+    "objectID": "decisions/20220203-create-default-animation-set.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20220203-create-default-animation-set.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Draft: To have a default set of motions on a 3d character by creating a default animation set",
     "section": "",
-    "text": "cmd\nscoop install llvm openssl-mingw llvm-mingw\ncargo build --release -p mvsqlite\ncd mvsqlite-sqlite3\nmingw32-make.exe build-patched-sqlite3\nset RUST_LOG=info\nset MVSQLITE_DATA_PLANE=http://localhost:7000\nsqlite3 test\n.tables\n\n\nfdbcli\nstatus\n# Force create a database\n# configure new single memory\n\n\n\nmsys2\ncurl http://localhost:7001/api/create_namespace -i -d '{\"key\":\"test\"}'\n\n\n\n# on Linux\nwget https://github.com/apple/foundationdb/releases/download/7.1.15/foundationdb-clients_7.1.15-1_amd64.deb\nsudo dpkg -i foundationdb-clients_7.1.15-1_amd64.deb\nwget https://github.com/apple/foundationdb/releases/download/7.1.15/foundationdb-server_7.1.15-1_amd64.deb\nsudo dpkg -i foundationdb-server_7.1.15-1_amd64.deb\ncargo build --release -p mvstore\nRUST_LOG=info ./mvstore \\\n  --data-plane 127.0.0.1:7000 \\\n  --admin-api 127.0.0.1:7001 \\\n  --metadata-prefix mvstore \\\n  --raw-data-prefix m\n\n\n\ncmd\ncargo build --release -p mvstore\nset RUST_LOG=info\nmvstore --data-plane 127.0.0.1:7000 --admin-api 127.0.0.1:7001 --metadata-prefix mvstore --raw-data-prefix m --cluster \"C:/ProgramData/foundationdb/fdb.cluster\""
+    "text": "Describe the proposed option and how it helps to overcome the problem or limitation"
   },
   {
-    "objectID": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#launch-scripts",
-    "href": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#launch-scripts",
-    "title": "Draft: Simulate larger 3d multiplayer worlds using “brickworlds partition layout”",
+    "objectID": "decisions/20220203-create-default-animation-set.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20220203-create-default-animation-set.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Draft: To have a default set of motions on a 3d character by creating a default animation set",
     "section": "",
-    "text": "set RUST_LOG=info\nset MVSQLITE_DATA_PLANE=http://localhost:7000\nsqlite3 test\n\n\n\nset RUST_LOG=error\nmvstore --data-plane 127.0.0.1:7000 --admin-api 127.0.0.1:7001 --metadata-prefix mvstore --raw-data-prefix m --cluster \"C:/ProgramData/foundationdb/fdb.cluster\""
+    "text": "Init\nNeutralFront\nNeutralRight\nNeutralLeft\nWalkFront\nWalkBack\nWalkRightFront\nWalkRightBack\nWalkLeftFront\nWalkLeftBack\nStrafeRight\nStrafeLeft\nSprintFront\nSprintBack\nSprintRightFront\nSprintRightBack\nSprintLeftFront\nSprintLeftFrontBack\nJump\nFall\nLand\n\n\n\n\nSit\n(NeutralToSit)\n(SitToNeutral)\nLay\n(NeutralToLay)\n(LayToNeutral)\n\n\n\n\n\nDuckNeutral\nDuckMoveFront\nDuckMoveBack\nDuckMoveRight\nDuckMoveLeft\n(DuckToSit)\n(SitToDuck)\n(DuckToLay)\n(LayToDuck)\nCrawlNeutral\nCrawlMoveFront\nCrawlMoveBack\nCrawlMoveRight\nCrawlMoveLeft\n(CrawlToSit)\n(SitToCrawl)\n(CrawlToLay)\n(LayToCrawl)\n(NeutralToDuck)\n(DuckToNeutral)\n(NeutralToCrawl)\n(CrawlToNeutral)\n(DuckToCrawl)\n(CrawlToDuck)\n\n\n\n\n\nChair"
   },
   {
-    "objectID": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#license-of-the-contribution",
-    "href": "decisions/20221022-have-larger-worlds-by-server-state-migration.html#license-of-the-contribution",
-    "title": "Draft: Simulate larger 3d multiplayer worlds using “brickworlds partition layout”",
+    "objectID": "decisions/20220203-create-default-animation-set.html#positive-consequences",
+    "href": "decisions/20220203-create-default-animation-set.html#positive-consequences",
+    "title": "Draft: To have a default set of motions on a 3d character by creating a default animation set",
     "section": "",
-    "text": "Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "[e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]"
   },
   {
-    "objectID": "decisions/20230125-user-generated-scripting-with-libsql-and-wasm.html",
-    "href": "decisions/20230125-user-generated-scripting-with-libsql-and-wasm.html",
-    "title": "Proposed: Provide user generated scripting with libsql and wasm",
+    "objectID": "decisions/20220203-create-default-animation-set.html#negative-consequences",
+    "href": "decisions/20220203-create-default-animation-set.html#negative-consequences",
+    "title": "Draft: To have a default set of motions on a 3d character by creating a default animation set",
     "section": "",
-    "text": "Proposed: Provide user generated scripting with libsql and wasm\n\nMetadata\n\nStatus: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nContext and Problem Statement\nWe want to have user scripting for interactivity for objects, pets and npcs.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nWe implement the wasm scripts using libsql and a wasm runtime to be determined.\nWe had a previous implementation called WASGO. Possible names for the new one is WASGOQuery and WASGO.\nAdvantages:\n\nWAMR wasn’t well liked because it’s written in c/c++ and because it’s not widely used.\nWASMTIME is widely used and used for commercial / financial applications\n\nDisadvantages:\n\nWASMTIME rust is hard to deploy\nWAMR is hard to use.\n\nOpen Questions:\nDoes it require determinism for clustering?\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nWe ONLY support floating point, integers, strings and byte arrays.\n\nCompile libsqlite\nAdd a wasm engine\nTyped:\nSave a UDF of the notification function of _notification as a string of arbitrary length\nreturns a row\n\n\n\n\nimage\n\n\n\n\nPositive Consequences\nWe can user script our worlds.\n\n\nNegative Consequences\nWe cannot get other features in.\n\n\nOption graveyard\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nKnowing what to do is hard.\n\n\nIs there a reason why this should be core and done by us?\nScriptability is a core feature.\n\n\nReferences\n\nV-Sekai\nlibsql bindgen\nwasm udfs in sqlite"
+    "text": "[e.g., compromising quality attribute, follow-up decisions required, …]\n\n[this section can be repeated for each option if more than one option is open for consideration]"
   },
   {
-    "objectID": "decisions/20240325-fdb-sqlite-blender-godot.html",
-    "href": "decisions/20240325-fdb-sqlite-blender-godot.html",
-    "title": "Proposed: Synchronizing Blender and FDB-SQLite for Proxy Movement",
+    "objectID": "decisions/20220203-create-default-animation-set.html#option-graveyard",
+    "href": "decisions/20220203-create-default-animation-set.html#option-graveyard",
+    "title": "Draft: To have a default set of motions on a 3d character by creating a default animation set",
     "section": "",
-    "text": "Blender is a powerful open-source 3D creation suite that supports the entirety of the 3D pipeline. On the other hand, FDB-SQLite is a SQL layer built on top of the key-value store FoundationDB. The goal is to synchronize these two systems to proxy movement.\n\n\n\nThe challenge is to create a system where movements made in Blender are reflected in the FDB-SQLite database. This would allow for real-time tracking and manipulation of 3D models in a database environment.\n\n\n\nWe can achieve this by creating an interface between Blender and FDB-SQLite. This interface will listen for changes in Blender and update the corresponding entries in the FDB-SQLite database.\nclass BlenderFDBInterface:\n    def __init__(self, blender, fdb):\n        self.blender = blender\n        self.fdb = fdb\n\n    def sync(self):\n        # Get current state from Blender\n        state = self.blender.get_state()\n\n        # Update FDB with current state\n        self.fdb.update(state)\n\n\n\n\nReal-time synchronization between Blender and FDB-SQLite.\nAllows for complex queries and manipulations on 3D model data.\nOpens up possibilities for advanced analytics and machine learning applications.\n\n\n\n\n\nRequires careful management of database transactions to avoid conflicts.\nPotential performance issues due to constant syncing.\n\n\n\n\nAn alternative approach could be to use a different database system that has built-in support for 3D data. However, this would require migrating all existing data and potentially reworking other parts of the system.\n\n\n\nThis solution may not be suitable for scenarios where the 3D models are rarely updated, as the constant syncing could be unnecessary overhead.\n\n\n\nThis feature will be developed by our in-house team, ensuring that it fits seamlessly into our existing infrastructure.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "Option: \nRejection Reason:"
   },
   {
-    "objectID": "decisions/20240325-fdb-sqlite-blender-godot.html#context",
-    "href": "decisions/20240325-fdb-sqlite-blender-godot.html#context",
-    "title": "Proposed: Synchronizing Blender and FDB-SQLite for Proxy Movement",
+    "objectID": "decisions/20220203-create-default-animation-set.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20220203-create-default-animation-set.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Draft: To have a default set of motions on a 3d character by creating a default animation set",
     "section": "",
-    "text": "Blender is a powerful open-source 3D creation suite that supports the entirety of the 3D pipeline. On the other hand, FDB-SQLite is a SQL layer built on top of the key-value store FoundationDB. The goal is to synchronize these two systems to proxy movement."
+    "text": "If this enhancement will not be used often, can it be worked around with a few lines of script?"
   },
   {
-    "objectID": "decisions/20240325-fdb-sqlite-blender-godot.html#problem-statement",
-    "href": "decisions/20240325-fdb-sqlite-blender-godot.html#problem-statement",
-    "title": "Proposed: Synchronizing Blender and FDB-SQLite for Proxy Movement",
+    "objectID": "decisions/20220203-create-default-animation-set.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20220203-create-default-animation-set.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Draft: To have a default set of motions on a 3d character by creating a default animation set",
     "section": "",
-    "text": "The challenge is to create a system where movements made in Blender are reflected in the FDB-SQLite database. This would allow for real-time tracking and manipulation of 3D models in a database environment."
+    "text": "Is there a reason why this should be core and done by us?"
   },
   {
-    "objectID": "decisions/20240325-fdb-sqlite-blender-godot.html#proposed-solution",
-    "href": "decisions/20240325-fdb-sqlite-blender-godot.html#proposed-solution",
-    "title": "Proposed: Synchronizing Blender and FDB-SQLite for Proxy Movement",
+    "objectID": "decisions/20220203-create-default-animation-set.html#references",
+    "href": "decisions/20220203-create-default-animation-set.html#references",
+    "title": "Draft: To have a default set of motions on a 3d character by creating a default animation set",
     "section": "",
-    "text": "We can achieve this by creating an interface between Blender and FDB-SQLite. This interface will listen for changes in Blender and update the corresponding entries in the FDB-SQLite database.\nclass BlenderFDBInterface:\n    def __init__(self, blender, fdb):\n        self.blender = blender\n        self.fdb = fdb\n\n    def sync(self):\n        # Get current state from Blender\n        state = self.blender.get_state()\n\n        # Update FDB with current state\n        self.fdb.update(state)"
+    "text": "Link type"
   },
   {
-    "objectID": "decisions/20240325-fdb-sqlite-blender-godot.html#benefits",
-    "href": "decisions/20240325-fdb-sqlite-blender-godot.html#benefits",
-    "title": "Proposed: Synchronizing Blender and FDB-SQLite for Proxy Movement",
+    "objectID": "decisions/20220203-create-default-animation-set.html#derivative-license",
+    "href": "decisions/20220203-create-default-animation-set.html#derivative-license",
+    "title": "Draft: To have a default set of motions on a 3d character by creating a default animation set",
     "section": "",
-    "text": "Real-time synchronization between Blender and FDB-SQLite.\nAllows for complex queries and manipulations on 3D model data.\nOpens up possibilities for advanced analytics and machine learning applications."
+    "text": "Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240325-fdb-sqlite-blender-godot.html#downsides",
-    "href": "decisions/20240325-fdb-sqlite-blender-godot.html#downsides",
-    "title": "Proposed: Synchronizing Blender and FDB-SQLite for Proxy Movement",
+    "objectID": "decisions/20230911-first-alpha-tag.html",
+    "href": "decisions/20230911-first-alpha-tag.html",
+    "title": "Proposed: Implementing Semantic Versioning for Alpha Releases in V-Sekai",
     "section": "",
-    "text": "Requires careful management of database transactions to avoid conflicts.\nPotential performance issues due to constant syncing."
+    "text": "Status: Proposed \nDeciders: V-Sekai\nTags: V-Sekai, Semantic Versioning, Alpha Release\n\n\n\n\nIn software development, semantic versioning (semver) is a popular method for versioning software. It provides a clear and concise way to communicate changes in versions and the associated implications.\n\n\n\nThe challenge lies in correctly denoting the first alpha release in semver. This is crucial as it communicates the stability of the software and sets expectations for users and developers.\n\n\n\nIn semver, the first alpha release would typically be denoted with a hyphen followed by the word “alpha” and a number. For example, it could be something like “0.1.0-alpha.1”. The specific alpha release number may vary depending on the project and its release cycle.\n\n\n\nUsing semver for alpha releases helps to set clear expectations about the stability and features of the software. It allows developers and users to understand that the software is in an early stage of development and may not yet have all planned features or be fully stable.\n\n\n\nThe downside could be the potential confusion around the naming convention, especially for those unfamiliar with semver. However, this can be mitigated through clear documentation and communication.\n\n\n\nAn alternative approach could be to use a different versioning system or to not denote alpha releases specifically. However, these approaches may not provide the same level of clarity and communication as semver.\n\n\n\nWhile the alpha release notation is common in semver, it may not be used frequently in projects that have shorter development cycles or that do not release alpha versions to the public.\n\n\n\nYes, this strategy of using semver for denoting alpha releases is a core part of the V-Sekai project management and release process.\n\n\n\n\n[V-Sekai] - AI assists this article.\nSemantic Versioning"
   },
   {
-    "objectID": "decisions/20240325-fdb-sqlite-blender-godot.html#the-road-not-taken",
-    "href": "decisions/20240325-fdb-sqlite-blender-godot.html#the-road-not-taken",
-    "title": "Proposed: Synchronizing Blender and FDB-SQLite for Proxy Movement",
+    "objectID": "decisions/20230911-first-alpha-tag.html#metadata",
+    "href": "decisions/20230911-first-alpha-tag.html#metadata",
+    "title": "Proposed: Implementing Semantic Versioning for Alpha Releases in V-Sekai",
     "section": "",
-    "text": "An alternative approach could be to use a different database system that has built-in support for 3D data. However, this would require migrating all existing data and potentially reworking other parts of the system."
+    "text": "Status: Proposed \nDeciders: V-Sekai\nTags: V-Sekai, Semantic Versioning, Alpha Release"
   },
   {
-    "objectID": "decisions/20240325-fdb-sqlite-blender-godot.html#the-infrequent-use-case",
-    "href": "decisions/20240325-fdb-sqlite-blender-godot.html#the-infrequent-use-case",
-    "title": "Proposed: Synchronizing Blender and FDB-SQLite for Proxy Movement",
+    "objectID": "decisions/20230911-first-alpha-tag.html#the-backdrop",
+    "href": "decisions/20230911-first-alpha-tag.html#the-backdrop",
+    "title": "Proposed: Implementing Semantic Versioning for Alpha Releases in V-Sekai",
     "section": "",
-    "text": "This solution may not be suitable for scenarios where the 3D models are rarely updated, as the constant syncing could be unnecessary overhead."
+    "text": "In software development, semantic versioning (semver) is a popular method for versioning software. It provides a clear and concise way to communicate changes in versions and the associated implications."
   },
   {
-    "objectID": "decisions/20240325-fdb-sqlite-blender-godot.html#in-core-and-done-by-us",
-    "href": "decisions/20240325-fdb-sqlite-blender-godot.html#in-core-and-done-by-us",
-    "title": "Proposed: Synchronizing Blender and FDB-SQLite for Proxy Movement",
+    "objectID": "decisions/20230911-first-alpha-tag.html#the-challenge",
+    "href": "decisions/20230911-first-alpha-tag.html#the-challenge",
+    "title": "Proposed: Implementing Semantic Versioning for Alpha Releases in V-Sekai",
     "section": "",
-    "text": "This feature will be developed by our in-house team, ensuring that it fits seamlessly into our existing infrastructure."
+    "text": "The challenge lies in correctly denoting the first alpha release in semver. This is crucial as it communicates the stability of the software and sets expectations for users and developers."
   },
   {
-    "objectID": "decisions/20240325-fdb-sqlite-blender-godot.html#status",
-    "href": "decisions/20240325-fdb-sqlite-blender-godot.html#status",
-    "title": "Proposed: Synchronizing Blender and FDB-SQLite for Proxy Movement",
+    "objectID": "decisions/20230911-first-alpha-tag.html#the-strategy",
+    "href": "decisions/20230911-first-alpha-tag.html#the-strategy",
+    "title": "Proposed: Implementing Semantic Versioning for Alpha Releases in V-Sekai",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "In semver, the first alpha release would typically be denoted with a hyphen followed by the word “alpha” and a number. For example, it could be something like “0.1.0-alpha.1”. The specific alpha release number may vary depending on the project and its release cycle."
   },
   {
-    "objectID": "decisions/20240325-fdb-sqlite-blender-godot.html#decision-makers",
-    "href": "decisions/20240325-fdb-sqlite-blender-godot.html#decision-makers",
-    "title": "Proposed: Synchronizing Blender and FDB-SQLite for Proxy Movement",
+    "objectID": "decisions/20230911-first-alpha-tag.html#the-upside",
+    "href": "decisions/20230911-first-alpha-tag.html#the-upside",
+    "title": "Proposed: Implementing Semantic Versioning for Alpha Releases in V-Sekai",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "Using semver for alpha releases helps to set clear expectations about the stability and features of the software. It allows developers and users to understand that the software is in an early stage of development and may not yet have all planned features or be fully stable."
   },
   {
-    "objectID": "decisions/20240325-fdb-sqlite-blender-godot.html#tags",
-    "href": "decisions/20240325-fdb-sqlite-blender-godot.html#tags",
-    "title": "Proposed: Synchronizing Blender and FDB-SQLite for Proxy Movement",
+    "objectID": "decisions/20230911-first-alpha-tag.html#the-downside",
+    "href": "decisions/20230911-first-alpha-tag.html#the-downside",
+    "title": "Proposed: Implementing Semantic Versioning for Alpha Releases in V-Sekai",
     "section": "",
-    "text": "V-Sekai"
+    "text": "The downside could be the potential confusion around the naming convention, especially for those unfamiliar with semver. However, this can be mitigated through clear documentation and communication."
   },
   {
-    "objectID": "decisions/20240325-fdb-sqlite-blender-godot.html#further-reading",
-    "href": "decisions/20240325-fdb-sqlite-blender-godot.html#further-reading",
-    "title": "Proposed: Synchronizing Blender and FDB-SQLite for Proxy Movement",
+    "objectID": "decisions/20230911-first-alpha-tag.html#the-road-not-taken",
+    "href": "decisions/20230911-first-alpha-tag.html#the-road-not-taken",
+    "title": "Proposed: Implementing Semantic Versioning for Alpha Releases in V-Sekai",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "An alternative approach could be to use a different versioning system or to not denote alpha releases specifically. However, these approaches may not provide the same level of clarity and communication as semver."
   },
   {
-    "objectID": "decisions/20230108-bolster-creating-the-metaverse.html",
-    "href": "decisions/20230108-bolster-creating-the-metaverse.html",
-    "title": "Accepted: Bolster creating the metaverse",
+    "objectID": "decisions/20230911-first-alpha-tag.html#the-infrequent-use-case",
+    "href": "decisions/20230911-first-alpha-tag.html#the-infrequent-use-case",
+    "title": "Proposed: Implementing Semantic Versioning for Alpha Releases in V-Sekai",
     "section": "",
-    "text": "Status: accepted \n\n\n\nThe metaverse needs creators.\n\nOpen Metaverse Interoperability Group’s mission: We bolster the metaverse as an open and interoperable resource for anyone, inspired by the collaborative efforts of the community.\n\n\nThe Open Metaverse Interoperability Group is focused on bridging virtual worlds by designing and promoting protocols for identity, social graphs, inventory, and more. Our members include businesses and individuals working towards this common goal. Aside from technical work, OMI aims to create a community of artists, creators, developers, and other innovators to discuss and explore concepts surrounding the design and development of virtual worlds. OMI Core Values\n\n\nWe collaborate, driven by research, privacy and accessibility, to make the metaverse more human.\nWe work incrementally, iteratively, and with intent.\nWe are creating a cooperative, sustainable culture of innovation.\nWe empower the people making the metaverse.\nWe must cultivate resiliency by championing diversity, and freedom of choice.\n\n\n\n\nWe propose to create a V-Sekai #guide to creating the metaverse, creating your own virtual you and creating a part of the world. This can be a collaboration with others to provide matching #guide to other metaverses.\n\n\n\nLearn from how experienced educators how to bloster new creators.\n\n\n\n\nMore creators are available.\n\n\n\n\n\nEffort and time are spent for unknown results.\n\n\n\n\n\nOption: \nRejection Reason: \n\n\n\n\nNot a coding script, but can be a #guide script.\n\n\n\nOnly we can create official V-Sekai guides.\n\n\n\n\nhttps://v-sekai.org/\n\n\n\n\nCopyright (c) 2020-present V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "While the alpha release notation is common in semver, it may not be used frequently in projects that have shorter development cycles or that do not release alpha versions to the public."
   },
   {
-    "objectID": "decisions/20230108-bolster-creating-the-metaverse.html#context-and-problem-statement",
-    "href": "decisions/20230108-bolster-creating-the-metaverse.html#context-and-problem-statement",
-    "title": "Accepted: Bolster creating the metaverse",
+    "objectID": "decisions/20230911-first-alpha-tag.html#in-core-and-done-by-us",
+    "href": "decisions/20230911-first-alpha-tag.html#in-core-and-done-by-us",
+    "title": "Proposed: Implementing Semantic Versioning for Alpha Releases in V-Sekai",
     "section": "",
-    "text": "The metaverse needs creators.\n\nOpen Metaverse Interoperability Group’s mission: We bolster the metaverse as an open and interoperable resource for anyone, inspired by the collaborative efforts of the community.\n\n\nThe Open Metaverse Interoperability Group is focused on bridging virtual worlds by designing and promoting protocols for identity, social graphs, inventory, and more. Our members include businesses and individuals working towards this common goal. Aside from technical work, OMI aims to create a community of artists, creators, developers, and other innovators to discuss and explore concepts surrounding the design and development of virtual worlds. OMI Core Values\n\n\nWe collaborate, driven by research, privacy and accessibility, to make the metaverse more human.\nWe work incrementally, iteratively, and with intent.\nWe are creating a cooperative, sustainable culture of innovation.\nWe empower the people making the metaverse.\nWe must cultivate resiliency by championing diversity, and freedom of choice."
+    "text": "Yes, this strategy of using semver for denoting alpha releases is a core part of the V-Sekai project management and release process."
   },
   {
-    "objectID": "decisions/20230108-bolster-creating-the-metaverse.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20230108-bolster-creating-the-metaverse.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Accepted: Bolster creating the metaverse",
+    "objectID": "decisions/20230911-first-alpha-tag.html#further-reading",
+    "href": "decisions/20230911-first-alpha-tag.html#further-reading",
+    "title": "Proposed: Implementing Semantic Versioning for Alpha Releases in V-Sekai",
     "section": "",
-    "text": "We propose to create a V-Sekai #guide to creating the metaverse, creating your own virtual you and creating a part of the world. This can be a collaboration with others to provide matching #guide to other metaverses."
+    "text": "[V-Sekai] - AI assists this article.\nSemantic Versioning"
   },
   {
-    "objectID": "decisions/20230108-bolster-creating-the-metaverse.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20230108-bolster-creating-the-metaverse.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Accepted: Bolster creating the metaverse",
+    "objectID": "decisions/20211031-make-a-place-to-record.html",
+    "href": "decisions/20211031-make-a-place-to-record.html",
+    "title": "Proposed: Make a place to record",
     "section": "",
-    "text": "Learn from how experienced educators how to bloster new creators."
+    "text": "Proposed: Make a place to record\n\nContext and Problem Statement\nStages are useful to record motion\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nCreate a stage for 3d avatars to move.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nCreate a 3d environment\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nThis is artwork.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nCan be requested.\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230108-bolster-creating-the-metaverse.html#positive-consequences",
-    "href": "decisions/20230108-bolster-creating-the-metaverse.html#positive-consequences",
-    "title": "Accepted: Bolster creating the metaverse",
+    "objectID": "decisions/20241001-small-game-tools.html",
+    "href": "decisions/20241001-small-game-tools.html",
+    "title": "Proposed: Small V-Sekai Creation Tools",
     "section": "",
-    "text": "More creators are available."
+    "text": "The Godot Editor now integrates a 2D editor on a screen for VR, which cannot be fully optimized for VR screens like the Meta Quest 3. However, the Quest 3’s multiwindow support offers new possibilities.\n\n\n\nWe want to create a suite of tools for V-Sekai game development that leverages the capabilities of current hardware without requiring full VR integration.\n\n\n\nDevelop a series of small, efficient tools that can connect remotely to the V-Sekai game project, facilitating world creation and other development tasks from a 2D interface displayed within a VR environment.\n\n\n\n\nEnhanced Accessibility: Developers can use tools within a VR environment without the need for full VR tool conversion, combining comfort with functionality.\nReal-Time Interaction: Enables immediate feedback and interaction with the game world, enhancing development speed and efficiency.\nInnovative Approach: By using a hybrid approach, V-Sekai remains at the cutting edge, integrating new technologies while maintaining usability.\n\n\n\n\n\nTechnical Challenges: Creating tools that function seamlessly between 2D and VR environments is complex and may require significant resources.\nUser Adaptation: There might be a learning curve as developers adjust to using a 2D interface in a VR context.\nHardware Limitations: The performance and functionality are still bound by the limitations of existing VR hardware like the Meta Quest 3.\n\n\n\n\nFull VR development tools and augmented reality interfaces were considered but deemed not yet viable for our goals due to current technological constraints and development focus.\n\n\n\nFor developers who prefer traditional desktop-based environments, or where VR integration provides no clear advantage, existing non-VR tools will continue to be supported and developed.\n\n\n\nThis initiative aligns with our core mission to innovate within accessible VR and game development tools, and will be developed internally by the V-Sekai team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\nHumbletim\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20230108-bolster-creating-the-metaverse.html#negative-consequences",
-    "href": "decisions/20230108-bolster-creating-the-metaverse.html#negative-consequences",
-    "title": "Accepted: Bolster creating the metaverse",
+    "objectID": "decisions/20241001-small-game-tools.html#the-context",
+    "href": "decisions/20241001-small-game-tools.html#the-context",
+    "title": "Proposed: Small V-Sekai Creation Tools",
     "section": "",
-    "text": "Effort and time are spent for unknown results."
+    "text": "The Godot Editor now integrates a 2D editor on a screen for VR, which cannot be fully optimized for VR screens like the Meta Quest 3. However, the Quest 3’s multiwindow support offers new possibilities."
   },
   {
-    "objectID": "decisions/20230108-bolster-creating-the-metaverse.html#option-graveyard",
-    "href": "decisions/20230108-bolster-creating-the-metaverse.html#option-graveyard",
-    "title": "Accepted: Bolster creating the metaverse",
+    "objectID": "decisions/20241001-small-game-tools.html#the-problem-statement",
+    "href": "decisions/20241001-small-game-tools.html#the-problem-statement",
+    "title": "Proposed: Small V-Sekai Creation Tools",
     "section": "",
-    "text": "Option: \nRejection Reason:"
+    "text": "We want to create a suite of tools for V-Sekai game development that leverages the capabilities of current hardware without requiring full VR integration."
   },
   {
-    "objectID": "decisions/20230108-bolster-creating-the-metaverse.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230108-bolster-creating-the-metaverse.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Accepted: Bolster creating the metaverse",
+    "objectID": "decisions/20241001-small-game-tools.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20241001-small-game-tools.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Small V-Sekai Creation Tools",
     "section": "",
-    "text": "Not a coding script, but can be a #guide script."
+    "text": "Develop a series of small, efficient tools that can connect remotely to the V-Sekai game project, facilitating world creation and other development tasks from a 2D interface displayed within a VR environment."
   },
   {
-    "objectID": "decisions/20230108-bolster-creating-the-metaverse.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230108-bolster-creating-the-metaverse.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Accepted: Bolster creating the metaverse",
+    "objectID": "decisions/20241001-small-game-tools.html#the-benefits",
+    "href": "decisions/20241001-small-game-tools.html#the-benefits",
+    "title": "Proposed: Small V-Sekai Creation Tools",
     "section": "",
-    "text": "Only we can create official V-Sekai guides."
+    "text": "Enhanced Accessibility: Developers can use tools within a VR environment without the need for full VR tool conversion, combining comfort with functionality.\nReal-Time Interaction: Enables immediate feedback and interaction with the game world, enhancing development speed and efficiency.\nInnovative Approach: By using a hybrid approach, V-Sekai remains at the cutting edge, integrating new technologies while maintaining usability."
   },
   {
-    "objectID": "decisions/20230108-bolster-creating-the-metaverse.html#references",
-    "href": "decisions/20230108-bolster-creating-the-metaverse.html#references",
-    "title": "Accepted: Bolster creating the metaverse",
+    "objectID": "decisions/20241001-small-game-tools.html#the-downsides",
+    "href": "decisions/20241001-small-game-tools.html#the-downsides",
+    "title": "Proposed: Small V-Sekai Creation Tools",
     "section": "",
-    "text": "https://v-sekai.org/"
+    "text": "Technical Challenges: Creating tools that function seamlessly between 2D and VR environments is complex and may require significant resources.\nUser Adaptation: There might be a learning curve as developers adjust to using a 2D interface in a VR context.\nHardware Limitations: The performance and functionality are still bound by the limitations of existing VR hardware like the Meta Quest 3."
   },
   {
-    "objectID": "decisions/20230108-bolster-creating-the-metaverse.html#derivative-license",
-    "href": "decisions/20230108-bolster-creating-the-metaverse.html#derivative-license",
-    "title": "Accepted: Bolster creating the metaverse",
+    "objectID": "decisions/20241001-small-game-tools.html#the-road-not-taken",
+    "href": "decisions/20241001-small-game-tools.html#the-road-not-taken",
+    "title": "Proposed: Small V-Sekai Creation Tools",
     "section": "",
-    "text": "Copyright (c) 2020-present V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Full VR development tools and augmented reality interfaces were considered but deemed not yet viable for our goals due to current technological constraints and development focus."
   },
   {
-    "objectID": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html",
-    "href": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html",
-    "title": "Proposed: Use shrink wrap blender modifier to fit",
+    "objectID": "decisions/20241001-small-game-tools.html#the-infrequent-use-case",
+    "href": "decisions/20241001-small-game-tools.html#the-infrequent-use-case",
+    "title": "Proposed: Small V-Sekai Creation Tools",
     "section": "",
-    "text": "Want to make an avatar clothing for VRChat.\n\n\n\nOur cloth shirt is too baggy, we want to fit to the person.\n\n\n\n\nUse modifier shrinkswap in Blender 3d modeling tool.\nNearest surface points\nAbove surface\nTarget the body of the character\nOffset 2 mm.\n\n\n\n\n\nImproved Fit: Ensures that the clothing fits snugly to the avatar’s body.\nEnhanced Appearance: Provides a more realistic and appealing look for the avatar.\nCustomization: Allows for easy adjustments to fit different body types.\n\n\n\n\n\nComplexity: Requires familiarity with Blender and its modifiers.\nTime-Consuming: Initial setup and fine-tuning may take time.\n\n\n\n\nAlternative methods such as manual adjustment or using other software tools were considered but found to be less efficient or effective.\n\n\n\nIn scenarios where highly detailed or custom-fitted clothing is required, additional manual adjustments may be necessary to achieve the desired result.\n\n\n\nWe need to fill in a starter list of content.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "For developers who prefer traditional desktop-based environments, or where VR integration provides no clear advantage, existing non-VR tools will continue to be supported and developed."
   },
   {
-    "objectID": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#the-context",
-    "href": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#the-context",
-    "title": "Proposed: Use shrink wrap blender modifier to fit",
+    "objectID": "decisions/20241001-small-game-tools.html#in-core-and-done-by-us",
+    "href": "decisions/20241001-small-game-tools.html#in-core-and-done-by-us",
+    "title": "Proposed: Small V-Sekai Creation Tools",
     "section": "",
-    "text": "Want to make an avatar clothing for VRChat."
+    "text": "This initiative aligns with our core mission to innovate within accessible VR and game development tools, and will be developed internally by the V-Sekai team."
   },
   {
-    "objectID": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#the-problem-statement",
-    "href": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#the-problem-statement",
-    "title": "Proposed: Use shrink wrap blender modifier to fit",
+    "objectID": "decisions/20241001-small-game-tools.html#status",
+    "href": "decisions/20241001-small-game-tools.html#status",
+    "title": "Proposed: Small V-Sekai Creation Tools",
     "section": "",
-    "text": "Our cloth shirt is too baggy, we want to fit to the person."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Use shrink wrap blender modifier to fit",
+    "objectID": "decisions/20241001-small-game-tools.html#decision-makers",
+    "href": "decisions/20241001-small-game-tools.html#decision-makers",
+    "title": "Proposed: Small V-Sekai Creation Tools",
     "section": "",
-    "text": "Use modifier shrinkswap in Blender 3d modeling tool.\nNearest surface points\nAbove surface\nTarget the body of the character\nOffset 2 mm."
+    "text": "V-Sekai development team\nHumbletim"
   },
   {
-    "objectID": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#the-benefits",
-    "href": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#the-benefits",
-    "title": "Proposed: Use shrink wrap blender modifier to fit",
+    "objectID": "decisions/20241001-small-game-tools.html#tags",
+    "href": "decisions/20241001-small-game-tools.html#tags",
+    "title": "Proposed: Small V-Sekai Creation Tools",
     "section": "",
-    "text": "Improved Fit: Ensures that the clothing fits snugly to the avatar’s body.\nEnhanced Appearance: Provides a more realistic and appealing look for the avatar.\nCustomization: Allows for easy adjustments to fit different body types."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#the-downsides",
-    "href": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#the-downsides",
-    "title": "Proposed: Use shrink wrap blender modifier to fit",
+    "objectID": "decisions/20241001-small-game-tools.html#further-reading",
+    "href": "decisions/20241001-small-game-tools.html#further-reading",
+    "title": "Proposed: Small V-Sekai Creation Tools",
     "section": "",
-    "text": "Complexity: Requires familiarity with Blender and its modifiers.\nTime-Consuming: Initial setup and fine-tuning may take time."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#the-road-not-taken",
-    "href": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#the-road-not-taken",
-    "title": "Proposed: Use shrink wrap blender modifier to fit",
+    "objectID": "decisions/20240218-blender-to-godot.html",
+    "href": "decisions/20240218-blender-to-godot.html",
+    "title": "Proposed: Blender to Godot API Conversion",
     "section": "",
-    "text": "Alternative methods such as manual adjustment or using other software tools were considered but found to be less efficient or effective."
+    "text": "The current project involves transferring scene tree, mesh data, animation data, and sometimes textures from Blender to Godot. There are challenges due to extra data hiding in metadata and the shifting Blender API.\n\n\n\nThe Blender API keeps changing, causing issues with the transfer of data to Godot. Additionally, dumping all properties from Blender can cause crashes.\n\n\n\nInstead of trying to adapt to the shifting Blender API, we propose to keep the Blender API the same and create a converter on the Godot side. This way, the Blender side only needs to focus on sending/linking data, while Godot handles the conversion and integration.\n\n\n\n\nReduces dependency on Blender’s shifting API.\nSimplifies the process for engineers on both Blender and Godot sides.\nMakes it easier to update if things change.\n\n\n\n\n\nRequires development of a robust converter on the Godot side.\nAny changes in Blender’s data structure might still require updates to the converter.\n\n\n\n\nAn alternative approach would be to continually adapt to the shifting Blender API, but this could lead to more complex maintenance and potential crashes.\n\n\n\nIn cases where there is additional metadata or other non-standard data types, these would need to be handled separately by the converter.\n\n\n\nThis proposal suggests a core change in our approach to handling Blender data, moving the conversion responsibility to the Godot side.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team and community stakeholders.\n\n\n\n\n\nV-Sekai, Blender, Godot, API Conversion\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#the-infrequent-use-case",
-    "href": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#the-infrequent-use-case",
-    "title": "Proposed: Use shrink wrap blender modifier to fit",
+    "objectID": "decisions/20240218-blender-to-godot.html#the-context",
+    "href": "decisions/20240218-blender-to-godot.html#the-context",
+    "title": "Proposed: Blender to Godot API Conversion",
     "section": "",
-    "text": "In scenarios where highly detailed or custom-fitted clothing is required, additional manual adjustments may be necessary to achieve the desired result."
+    "text": "The current project involves transferring scene tree, mesh data, animation data, and sometimes textures from Blender to Godot. There are challenges due to extra data hiding in metadata and the shifting Blender API."
   },
   {
-    "objectID": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#in-core-and-done-by-us",
-    "href": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#in-core-and-done-by-us",
-    "title": "Proposed: Use shrink wrap blender modifier to fit",
+    "objectID": "decisions/20240218-blender-to-godot.html#the-problem-statement",
+    "href": "decisions/20240218-blender-to-godot.html#the-problem-statement",
+    "title": "Proposed: Blender to Godot API Conversion",
     "section": "",
-    "text": "We need to fill in a starter list of content."
+    "text": "The Blender API keeps changing, causing issues with the transfer of data to Godot. Additionally, dumping all properties from Blender can cause crashes."
   },
   {
-    "objectID": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#status",
-    "href": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#status",
-    "title": "Proposed: Use shrink wrap blender modifier to fit",
+    "objectID": "decisions/20240218-blender-to-godot.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240218-blender-to-godot.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Blender to Godot API Conversion",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "Instead of trying to adapt to the shifting Blender API, we propose to keep the Blender API the same and create a converter on the Godot side. This way, the Blender side only needs to focus on sending/linking data, while Godot handles the conversion and integration."
   },
   {
-    "objectID": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#decision-makers",
-    "href": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#decision-makers",
-    "title": "Proposed: Use shrink wrap blender modifier to fit",
+    "objectID": "decisions/20240218-blender-to-godot.html#the-benefits",
+    "href": "decisions/20240218-blender-to-godot.html#the-benefits",
+    "title": "Proposed: Blender to Godot API Conversion",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "Reduces dependency on Blender’s shifting API.\nSimplifies the process for engineers on both Blender and Godot sides.\nMakes it easier to update if things change."
   },
   {
-    "objectID": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#tags",
-    "href": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#tags",
-    "title": "Proposed: Use shrink wrap blender modifier to fit",
+    "objectID": "decisions/20240218-blender-to-godot.html#the-downsides",
+    "href": "decisions/20240218-blender-to-godot.html#the-downsides",
+    "title": "Proposed: Blender to Godot API Conversion",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Requires development of a robust converter on the Godot side.\nAny changes in Blender’s data structure might still require updates to the converter."
   },
   {
-    "objectID": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#further-reading",
-    "href": "decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html#further-reading",
-    "title": "Proposed: Use shrink wrap blender modifier to fit",
+    "objectID": "decisions/20240218-blender-to-godot.html#the-road-not-taken",
+    "href": "decisions/20240218-blender-to-godot.html#the-road-not-taken",
+    "title": "Proposed: Blender to Godot API Conversion",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "An alternative approach would be to continually adapt to the shifting Blender API, but this could lead to more complex maintenance and potential crashes."
   },
   {
-    "objectID": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html",
-    "href": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html",
-    "title": "Accepted: Allow cicd to pass by fixing spatial audio branch",
+    "objectID": "decisions/20240218-blender-to-godot.html#the-infrequent-use-case",
+    "href": "decisions/20240218-blender-to-godot.html#the-infrequent-use-case",
+    "title": "Proposed: Blender to Godot API Conversion",
     "section": "",
-    "text": "Status: accepted \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nCICD not passing causes quality to degrade.\n\n\n\nFix spatial audio branch of godot engine.\n\n\n\n\nResolve static checks\nFix platform errors.\n\n\n\n\n\nGood estimates of the work required.\n\n\n\n\n\nCICD passing is a chore.\n\n\n\n\n\nOption: Current status.\nRejection Reason: It’s bad to leave cicd broken.\n\n\n\n\nNot a few lines.\n\n\n\nWe are the maintainers.\n\n\n\n\nSpatial Audio branch\n\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "In cases where there is additional metadata or other non-standard data types, these would need to be handled separately by the converter."
   },
   {
-    "objectID": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html#context-and-problem-statement",
-    "href": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html#context-and-problem-statement",
-    "title": "Accepted: Allow cicd to pass by fixing spatial audio branch",
+    "objectID": "decisions/20240218-blender-to-godot.html#in-core-and-done-by-us",
+    "href": "decisions/20240218-blender-to-godot.html#in-core-and-done-by-us",
+    "title": "Proposed: Blender to Godot API Conversion",
     "section": "",
-    "text": "CICD not passing causes quality to degrade."
+    "text": "This proposal suggests a core change in our approach to handling Blender data, moving the conversion responsibility to the Godot side."
   },
   {
-    "objectID": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Accepted: Allow cicd to pass by fixing spatial audio branch",
+    "objectID": "decisions/20240218-blender-to-godot.html#status",
+    "href": "decisions/20240218-blender-to-godot.html#status",
+    "title": "Proposed: Blender to Godot API Conversion",
     "section": "",
-    "text": "Fix spatial audio branch of godot engine."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Accepted: Allow cicd to pass by fixing spatial audio branch",
+    "objectID": "decisions/20240218-blender-to-godot.html#decision-makers",
+    "href": "decisions/20240218-blender-to-godot.html#decision-makers",
+    "title": "Proposed: Blender to Godot API Conversion",
     "section": "",
-    "text": "Resolve static checks\nFix platform errors."
+    "text": "V-Sekai development team and community stakeholders."
   },
   {
-    "objectID": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html#positive-consequences",
-    "href": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html#positive-consequences",
-    "title": "Accepted: Allow cicd to pass by fixing spatial audio branch",
+    "objectID": "decisions/20240218-blender-to-godot.html#tags",
+    "href": "decisions/20240218-blender-to-godot.html#tags",
+    "title": "Proposed: Blender to Godot API Conversion",
     "section": "",
-    "text": "Good estimates of the work required."
+    "text": "V-Sekai, Blender, Godot, API Conversion"
   },
   {
-    "objectID": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html#negative-consequences",
-    "href": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html#negative-consequences",
-    "title": "Accepted: Allow cicd to pass by fixing spatial audio branch",
+    "objectID": "decisions/20240218-blender-to-godot.html#further-reading",
+    "href": "decisions/20240218-blender-to-godot.html#further-reading",
+    "title": "Proposed: Blender to Godot API Conversion",
     "section": "",
-    "text": "CICD passing is a chore."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html#option-graveyard",
-    "href": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html#option-graveyard",
-    "title": "Accepted: Allow cicd to pass by fixing spatial audio branch",
+    "objectID": "decisions/20221212-world-and-character-tools.html",
+    "href": "decisions/20221212-world-and-character-tools.html",
+    "title": "Proposed: Tools helpful for creating Avatars and Worlds",
     "section": "",
-    "text": "Option: Current status.\nRejection Reason: It’s bad to leave cicd broken."
+    "text": "Status: proposed \nDeciders: V-Sekai,fire,\nTags: V-Sekai,\n\n\n\nWant to list some useful tools for world and character creation and are free, open-source and remixable for commercial uses.\n\n\n\nThere many tools out there that are helpful for world and character creation.\n\n\n\n\nAn ESRGAN model made for upscaling normal maps. https://github.com/RunDevelopment/ESRGAN-models/tree/main/normals\nA Blender vrm addon. https://vrm-addon-for-blender.info/en/\nThe easiest way to install and use Stable Diffusion https://github.com/cmdr2/stable-diffusion-ui#installation\nImage prompt interrogator https://huggingface.co/spaces/pharma/CLIP-Interrogator/tree/main\nRepository for artwork and community for filming https://open3dlab.com/\nImage Upscaling GUI based on ESRGAN https://github.com/n00mkrad/cupscale\nDiscover trending open-source projects and their alternatives https://www.libhunt.com/\nHugging Face arrives to the Elixir community https://huggingface.co/blog/elixir-bumblebee\n\n\n\n\nA place to put related tools is helpful.\n\n\n\nA small amount of space and time is used.\n\n\n\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\n\nThese are not small tools.\n\n\n\nWriting down stuff that’s useful.\n\n\n\n\nV-Sekai\n\n\n\n\nMIT License\n\nCopyright (c) 2019-2022 K. S. Ernest (iFire) Lee (fire)\nCopyright (c) 2022 V-Sekai Contributors\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
   },
   {
-    "objectID": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Accepted: Allow cicd to pass by fixing spatial audio branch",
+    "objectID": "decisions/20221212-world-and-character-tools.html#context-and-problem-statement",
+    "href": "decisions/20221212-world-and-character-tools.html#context-and-problem-statement",
+    "title": "Proposed: Tools helpful for creating Avatars and Worlds",
     "section": "",
-    "text": "Not a few lines."
+    "text": "Want to list some useful tools for world and character creation and are free, open-source and remixable for commercial uses."
   },
   {
-    "objectID": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Accepted: Allow cicd to pass by fixing spatial audio branch",
+    "objectID": "decisions/20221212-world-and-character-tools.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20221212-world-and-character-tools.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: Tools helpful for creating Avatars and Worlds",
     "section": "",
-    "text": "We are the maintainers."
+    "text": "There many tools out there that are helpful for world and character creation."
   },
   {
-    "objectID": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html#references",
-    "href": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html#references",
-    "title": "Accepted: Allow cicd to pass by fixing spatial audio branch",
+    "objectID": "decisions/20221212-world-and-character-tools.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20221212-world-and-character-tools.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Tools helpful for creating Avatars and Worlds",
     "section": "",
-    "text": "Spatial Audio branch"
+    "text": "An ESRGAN model made for upscaling normal maps. https://github.com/RunDevelopment/ESRGAN-models/tree/main/normals\nA Blender vrm addon. https://vrm-addon-for-blender.info/en/\nThe easiest way to install and use Stable Diffusion https://github.com/cmdr2/stable-diffusion-ui#installation\nImage prompt interrogator https://huggingface.co/spaces/pharma/CLIP-Interrogator/tree/main\nRepository for artwork and community for filming https://open3dlab.com/\nImage Upscaling GUI based on ESRGAN https://github.com/n00mkrad/cupscale\nDiscover trending open-source projects and their alternatives https://www.libhunt.com/\nHugging Face arrives to the Elixir community https://huggingface.co/blog/elixir-bumblebee"
   },
   {
-    "objectID": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html#derivative-license",
-    "href": "decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html#derivative-license",
-    "title": "Accepted: Allow cicd to pass by fixing spatial audio branch",
+    "objectID": "decisions/20221212-world-and-character-tools.html#positive-consequences",
+    "href": "decisions/20221212-world-and-character-tools.html#positive-consequences",
+    "title": "Proposed: Tools helpful for creating Avatars and Worlds",
     "section": "",
-    "text": "Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "A place to put related tools is helpful."
   },
   {
-    "objectID": "decisions/20240502-install-windows-on-older-computers.html",
-    "href": "decisions/20240502-install-windows-on-older-computers.html",
-    "title": "Proposed: Enable Windows 11 Installation on Older Computers",
+    "objectID": "decisions/20221212-world-and-character-tools.html#negative-consequences",
+    "href": "decisions/20221212-world-and-character-tools.html#negative-consequences",
+    "title": "Proposed: Tools helpful for creating Avatars and Worlds",
     "section": "",
-    "text": "Many users with older computers wish to upgrade to Windows 11, but face compatibility issues.\n\n\n\nFacilitating the installation of Windows 11 on older computer systems.\n\n\n\nThe following steps outline a method to bypass certain system requirements during the Windows 11 installation process:\n\nInitiate the Windows 11 installer.\nPress SHIFT + F10 to open the command prompt.\nEnter regedit and press Enter to open the registry editor.\nNavigate to HKEY_LOCAL_MACHINE\\SYSTEM\\Setup.\nCreate a new registry key under Setup named LabConfig.\nWithin LabConfig, create DWORD values named BypassTPMCheck and BypassSecureBootCheck, setting each to 1. If you also want to bypass the RAM requirement, add a DWORD value for BypassRAMCheck.\nClose both regedit and the command prompt. You should now be able to proceed with your Windows 11 installation.\n\n\n\n\n\nAllows users with older hardware to access Windows 11 features.\nExtends the lifespan of older devices.\n\n\n\n\n\nPotential security risks due to bypassing TPM and Secure Boot checks.\nPerformance may not be optimal on older hardware.\n\n\n\n\n\nUpgrading hardware to meet Windows 11 requirements.\nSticking with Windows 10 or other operating systems.\n\n\n\n\nThis proposal is primarily beneficial for users with older hardware who wish to use Windows 11.\n\n\n\nThis proposal is currently under consideration by the V-Sekai development team.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai Development Team\n\n\n\n\n\nV-Sekai\nWindows 11\nInstallation\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community.\nV-Sekai/v-sekai-game - The GitHub page for the V-Sekai open-source project.\nToms Hardware: bypass-windows-11-tpm-requirement\n\nAssisted by AI assistant Aria."
+    "text": "A small amount of space and time is used."
   },
   {
-    "objectID": "decisions/20240502-install-windows-on-older-computers.html#context",
-    "href": "decisions/20240502-install-windows-on-older-computers.html#context",
-    "title": "Proposed: Enable Windows 11 Installation on Older Computers",
+    "objectID": "decisions/20221212-world-and-character-tools.html#option-graveyard",
+    "href": "decisions/20221212-world-and-character-tools.html#option-graveyard",
+    "title": "Proposed: Tools helpful for creating Avatars and Worlds",
     "section": "",
-    "text": "Many users with older computers wish to upgrade to Windows 11, but face compatibility issues."
+    "text": "Option: The status quo. \nRejection Reason: This solves nothing."
   },
   {
-    "objectID": "decisions/20240502-install-windows-on-older-computers.html#problem-statement",
-    "href": "decisions/20240502-install-windows-on-older-computers.html#problem-statement",
-    "title": "Proposed: Enable Windows 11 Installation on Older Computers",
+    "objectID": "decisions/20221212-world-and-character-tools.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20221212-world-and-character-tools.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Tools helpful for creating Avatars and Worlds",
     "section": "",
-    "text": "Facilitating the installation of Windows 11 on older computer systems."
+    "text": "These are not small tools."
   },
   {
-    "objectID": "decisions/20240502-install-windows-on-older-computers.html#solution-overview",
-    "href": "decisions/20240502-install-windows-on-older-computers.html#solution-overview",
-    "title": "Proposed: Enable Windows 11 Installation on Older Computers",
+    "objectID": "decisions/20221212-world-and-character-tools.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20221212-world-and-character-tools.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Tools helpful for creating Avatars and Worlds",
     "section": "",
-    "text": "The following steps outline a method to bypass certain system requirements during the Windows 11 installation process:\n\nInitiate the Windows 11 installer.\nPress SHIFT + F10 to open the command prompt.\nEnter regedit and press Enter to open the registry editor.\nNavigate to HKEY_LOCAL_MACHINE\\SYSTEM\\Setup.\nCreate a new registry key under Setup named LabConfig.\nWithin LabConfig, create DWORD values named BypassTPMCheck and BypassSecureBootCheck, setting each to 1. If you also want to bypass the RAM requirement, add a DWORD value for BypassRAMCheck.\nClose both regedit and the command prompt. You should now be able to proceed with your Windows 11 installation."
+    "text": "Writing down stuff that’s useful."
   },
   {
-    "objectID": "decisions/20240502-install-windows-on-older-computers.html#benefits",
-    "href": "decisions/20240502-install-windows-on-older-computers.html#benefits",
-    "title": "Proposed: Enable Windows 11 Installation on Older Computers",
+    "objectID": "decisions/20221212-world-and-character-tools.html#references",
+    "href": "decisions/20221212-world-and-character-tools.html#references",
+    "title": "Proposed: Tools helpful for creating Avatars and Worlds",
     "section": "",
-    "text": "Allows users with older hardware to access Windows 11 features.\nExtends the lifespan of older devices."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20240502-install-windows-on-older-computers.html#downsides",
-    "href": "decisions/20240502-install-windows-on-older-computers.html#downsides",
-    "title": "Proposed: Enable Windows 11 Installation on Older Computers",
+    "objectID": "decisions/20221212-world-and-character-tools.html#license-of-the-contribution",
+    "href": "decisions/20221212-world-and-character-tools.html#license-of-the-contribution",
+    "title": "Proposed: Tools helpful for creating Avatars and Worlds",
     "section": "",
-    "text": "Potential security risks due to bypassing TPM and Secure Boot checks.\nPerformance may not be optimal on older hardware."
+    "text": "MIT License\n\nCopyright (c) 2019-2022 K. S. Ernest (iFire) Lee (fire)\nCopyright (c) 2022 V-Sekai Contributors\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
   },
   {
-    "objectID": "decisions/20240502-install-windows-on-older-computers.html#alternatives-considered",
-    "href": "decisions/20240502-install-windows-on-older-computers.html#alternatives-considered",
-    "title": "Proposed: Enable Windows 11 Installation on Older Computers",
+    "objectID": "decisions/20230602-limited-tracker-placement.html",
+    "href": "decisions/20230602-limited-tracker-placement.html",
+    "title": "Proposed: Capturing accurate body movements with limited tracker placement",
     "section": "",
-    "text": "Upgrading hardware to meet Windows 11 requirements.\nSticking with Windows 10 or other operating systems."
+    "text": "Proposed: Capturing accurate body movements with limited tracker placement\n\nMetadata\n\nStatus: proposed \nDeciders: V-Sekai,fire,\nTags: V-Sekai,\n\n\n\nContext and Problem Statement\nIn our current VR project, we face the challenge of capturing accurate body movements for both soccer and dancing experiences with a limited budget. How can we prioritize the placement of a limited number of trackers to ensure a realistic and immersive experience for both activities?\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nThe proposed option involves prioritizing tracker placement for the head, hands, hips, and feet, as they are essential for both soccer and dancing experiences. This approach allows for an effective trade-off between tracking accuracy and budget constraints while ensuring a satisfactory level of immersion in both activities.\n\n\nDescribe how your proposal will work with code, pseudo-code, mock-ups, or diagrams\nVR Tracker USB dongles need line of sight.\n\nHead: At the base of the neck to monitor head rotation and tilt.\nLeft Hand: On the left wrist to track the overall motion of the left hand.\nRight Hand: On the right wrist to track the overall motion of the right hand.\nHips: A tracker on the hips to monitor lower body movement. Placed behind the body.\nLeft Foot: A tracker on the left foot to capture left foot movement, essential for both soccer and dancing.\nRight Foot: A tracker on the right foot to capture right foot movement, also crucial for both activities.\n\nAs the budget permits, additional trackers can be incorporated into the setup to further enhance tracking accuracy, particularly for the upper body and leg movements. This expansion can be achieved by following the prioritized list of additional trackers below:\n\nChest: A tracker on the chest to monitor upper body rotation, providing more detailed information about the user’s torso movements.\nLeft Elbow: Attach a tracker to the left elbow to monitor its angle, speed, and position. This helps improve the accuracy of tracking arm movements during activities like soccer and dancing.\nRight Elbow: In the same way, place a tracker on the right elbow to keep track of its angle, speed, and position. This also enhances the precision of tracking arm movements in sports such as soccer and dance performances.\n\nBy gradually adding these trackers to the initial setup, the overall tracking accuracy of the system will be improved. This will result in more natural and immersive interactions within the VR environment, leading to a more satisfying user experience for both soccer and dancing activities.\n\n\nPositive Consequences\n\nEffective use of a limited budget while maintaining immersive experiences.\nThe solution caters to both soccer and dancing activities in VR.\nFlexibility in adding more trackers as budget permits.\n\n\n\nNegative Consequences\n\nReduced tracking accuracy for upper body and leg movements compared to a setup with more trackers.\nPotential limitations in supporting advanced features or interactions in VR.\n\n\n\nOption graveyard\nCamera-based tracking: Utilizing external cameras to track body movements without the need for wearable trackers. While this approach can be cost-effective, it may not provide the same level of accuracy and precision as wearable trackers, particularly for fast and complex movements in soccer and dancing. Additionally, camera-based tracking can be sensitive to lighting conditions and may require a specific setup to function optimally.\nCamera-based tracking might be a viable solution if budget constraints are severe, but it is essential to consider the potential trade-offs in terms of tracking accuracy and reliability compared to wearable trackers.\n\n\nIf this enhancement will be used infrequently, can it be worked around with a few lines of script?\nNo, as the proposed solution deals with hardware configuration and the strategic placement of physical trackers to balance budget and immersion.\n\n\nIs there a reason why this should be core and done by us?\nYes, ensuring an immersive VR experience with a limited budget is a fundamental challenge that requires expertise in tracker placement and prioritization.\n\n\nReferences\n\nV-Sekai"
   },
   {
-    "objectID": "decisions/20240502-install-windows-on-older-computers.html#infrequent-use-case",
-    "href": "decisions/20240502-install-windows-on-older-computers.html#infrequent-use-case",
-    "title": "Proposed: Enable Windows 11 Installation on Older Computers",
+    "objectID": "decisions/20240529-improve-godot-import-ecosystem.html",
+    "href": "decisions/20240529-improve-godot-import-ecosystem.html",
+    "title": "Proposed: Improve the Godot Ecosystem",
     "section": "",
-    "text": "This proposal is primarily beneficial for users with older hardware who wish to use Windows 11."
+    "text": "Godot is a powerful open-source game engine that has been gaining popularity due to its flexibility and ease of use. However, there are still areas where it can be improved, particularly in terms of integration with other tools such as Blender.\n\n\n\nThe current process of exporting assets from Blender to Godot can be cumbersome and inefficient. Additionally, there are certain features in Blender that cannot be exported to Godot at all. This proposal aims to address these issues and improve the overall workflow between the two tools.\n\n\n\nHere are some of the key strategies we propose:\n\nExporting of Blender materials to Godot via a custom GLTF2 extension as Godot shaders.\n\nStrategy: Add MaterialX as a Godot engine shader and then have Blender export it.\nWork in progress: Translate MaterialX as a Godot Visual Shader.\nPlan B: Reuse the Blender exporter and use it to export Godot shaders as a glTF extension.\n\nExporting Blender scene settings (sky, etc) via custom GLTF2 extension as Godot shaders.\n\nStrategy: Find all Godot engine scene properties and write a glTF extension that can save or export it.\n\nExport Blender collision shapes to Godot.\n\nStrategy: Through KHR physics. Official Khronos ratification will give Blender and Godot engine glTF support through Aaron Franke’s PR.\n\nCreate and save unique IDs on Blender objects on export.\n\nThis needs to be researched a bit more (may need to be a Blender add-on, GLTF proposal).\n\nUnification of tangent space generation.\n\nThe revised design is that we move all tangent generation to the ImporterMesh3D for the importers.\n\nImprove the asset import dialog based on proposal GH-7238.\nFinalization of the IES light importer from pull request GH-63835.\n\nNeeds work on the equirectangular transform.\n\n\n\n\n\nImproving the Godot ecosystem will make it easier for developers to create and export assets, streamline workflows, and ultimately produce better games.\n\n\n\nThe main downside is that this will require a significant amount of development time and resources.\n\n\n\nAn alternative approach could be to focus on improving Godot’s native tools and capabilities, rather than its integration with other software.\n\n\n\nThis proposal may not benefit developers who do not use Blender or those who prefer to use other game engines.\n\n\n\nThe proposed improvements will be implemented in the core of the Godot engine and will be carried out by our team.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240502-install-windows-on-older-computers.html#in-core-and-done-by-us",
-    "href": "decisions/20240502-install-windows-on-older-computers.html#in-core-and-done-by-us",
-    "title": "Proposed: Enable Windows 11 Installation on Older Computers",
+    "objectID": "decisions/20240529-improve-godot-import-ecosystem.html#the-context",
+    "href": "decisions/20240529-improve-godot-import-ecosystem.html#the-context",
+    "title": "Proposed: Improve the Godot Ecosystem",
     "section": "",
-    "text": "This proposal is currently under consideration by the V-Sekai development team."
+    "text": "Godot is a powerful open-source game engine that has been gaining popularity due to its flexibility and ease of use. However, there are still areas where it can be improved, particularly in terms of integration with other tools such as Blender."
   },
   {
-    "objectID": "decisions/20240502-install-windows-on-older-computers.html#status",
-    "href": "decisions/20240502-install-windows-on-older-computers.html#status",
-    "title": "Proposed: Enable Windows 11 Installation on Older Computers",
+    "objectID": "decisions/20240529-improve-godot-import-ecosystem.html#the-problem-statement",
+    "href": "decisions/20240529-improve-godot-import-ecosystem.html#the-problem-statement",
+    "title": "Proposed: Improve the Godot Ecosystem",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "The current process of exporting assets from Blender to Godot can be cumbersome and inefficient. Additionally, there are certain features in Blender that cannot be exported to Godot at all. This proposal aims to address these issues and improve the overall workflow between the two tools."
   },
   {
-    "objectID": "decisions/20240502-install-windows-on-older-computers.html#decision-makers",
-    "href": "decisions/20240502-install-windows-on-older-computers.html#decision-makers",
-    "title": "Proposed: Enable Windows 11 Installation on Older Computers",
+    "objectID": "decisions/20240529-improve-godot-import-ecosystem.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240529-improve-godot-import-ecosystem.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Improve the Godot Ecosystem",
     "section": "",
-    "text": "V-Sekai Development Team"
+    "text": "Here are some of the key strategies we propose:\n\nExporting of Blender materials to Godot via a custom GLTF2 extension as Godot shaders.\n\nStrategy: Add MaterialX as a Godot engine shader and then have Blender export it.\nWork in progress: Translate MaterialX as a Godot Visual Shader.\nPlan B: Reuse the Blender exporter and use it to export Godot shaders as a glTF extension.\n\nExporting Blender scene settings (sky, etc) via custom GLTF2 extension as Godot shaders.\n\nStrategy: Find all Godot engine scene properties and write a glTF extension that can save or export it.\n\nExport Blender collision shapes to Godot.\n\nStrategy: Through KHR physics. Official Khronos ratification will give Blender and Godot engine glTF support through Aaron Franke’s PR.\n\nCreate and save unique IDs on Blender objects on export.\n\nThis needs to be researched a bit more (may need to be a Blender add-on, GLTF proposal).\n\nUnification of tangent space generation.\n\nThe revised design is that we move all tangent generation to the ImporterMesh3D for the importers.\n\nImprove the asset import dialog based on proposal GH-7238.\nFinalization of the IES light importer from pull request GH-63835.\n\nNeeds work on the equirectangular transform."
   },
   {
-    "objectID": "decisions/20240502-install-windows-on-older-computers.html#tags",
-    "href": "decisions/20240502-install-windows-on-older-computers.html#tags",
-    "title": "Proposed: Enable Windows 11 Installation on Older Computers",
+    "objectID": "decisions/20240529-improve-godot-import-ecosystem.html#the-benefits",
+    "href": "decisions/20240529-improve-godot-import-ecosystem.html#the-benefits",
+    "title": "Proposed: Improve the Godot Ecosystem",
     "section": "",
-    "text": "V-Sekai\nWindows 11\nInstallation"
+    "text": "Improving the Godot ecosystem will make it easier for developers to create and export assets, streamline workflows, and ultimately produce better games."
   },
   {
-    "objectID": "decisions/20240502-install-windows-on-older-computers.html#further-reading",
-    "href": "decisions/20240502-install-windows-on-older-computers.html#further-reading",
-    "title": "Proposed: Enable Windows 11 Installation on Older Computers",
+    "objectID": "decisions/20240529-improve-godot-import-ecosystem.html#the-downsides",
+    "href": "decisions/20240529-improve-godot-import-ecosystem.html#the-downsides",
+    "title": "Proposed: Improve the Godot Ecosystem",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community.\nV-Sekai/v-sekai-game - The GitHub page for the V-Sekai open-source project.\nToms Hardware: bypass-windows-11-tpm-requirement\n\nAssisted by AI assistant Aria."
+    "text": "The main downside is that this will require a significant amount of development time and resources."
   },
   {
-    "objectID": "decisions/20231114-upload-creative-commons-fbx-test-files.html",
-    "href": "decisions/20231114-upload-creative-commons-fbx-test-files.html",
-    "title": "Proposed: Upload Creative Commons FBX Test Files for Enhanced LOD Optimization in V-Sekai",
+    "objectID": "decisions/20240529-improve-godot-import-ecosystem.html#the-road-not-taken",
+    "href": "decisions/20240529-improve-godot-import-ecosystem.html#the-road-not-taken",
+    "title": "Proposed: Improve the Godot Ecosystem",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: FBX Test Files, LOD Optimization, V-Sekai, File Testing\n\n\n\n\nV-Sekai is continually improving its VR environments and functionalities. A key aspect of this development is optimizing Level of Detail (LOD) to enhance performance without sacrificing visual quality.\n\n\n\nCurrent LOD optimization processes are facing issues, notably crashing when handling multi-gigabyte FBX to OBJ test cases. This limits the ability to effectively test and optimize large, complex models in V-Sekai.\n\n\n\nPropose uploading a suite of Creative Commons FBX test files, credited to bbqbarbhg, to provide a more comprehensive and challenging dataset for LOD optimization testing.\n\n\n\nHaving access to a diverse and complex set of FBX files will allow for more thorough testing and optimization of LOD algorithms, leading to improved performance and stability in handling large and detailed models in the V-Sekai environment.\n\n\n\nThe process of integrating and testing with these new files may require significant resources and time. Additionally, if the files are extremely large or complex, they may pose challenges in terms of storage and processing requirements.\n\n\n\nAlternative approaches might involve optimizing the current LOD algorithms without the use of these specific test files, but this could limit the effectiveness of optimization efforts.\n\n\n\nWhile primarily aimed at enhancing LOD optimization, these test files could also be useful for other aspects of V-Sekai’s development, such as stress-testing the engine and other optimization tasks.\n\n\n\nThis initiative involves incorporating external resources (Creative Commons FBX files) into the core development and testing processes of V-Sekai, potentially requiring adjustments in testing protocols and optimization strategies.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis article was assisted by AI assistant Aria."
+    "text": "An alternative approach could be to focus on improving Godot’s native tools and capabilities, rather than its integration with other software."
   },
   {
-    "objectID": "decisions/20231114-upload-creative-commons-fbx-test-files.html#metadata",
-    "href": "decisions/20231114-upload-creative-commons-fbx-test-files.html#metadata",
-    "title": "Proposed: Upload Creative Commons FBX Test Files for Enhanced LOD Optimization in V-Sekai",
+    "objectID": "decisions/20240529-improve-godot-import-ecosystem.html#the-infrequent-use-case",
+    "href": "decisions/20240529-improve-godot-import-ecosystem.html#the-infrequent-use-case",
+    "title": "Proposed: Improve the Godot Ecosystem",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: FBX Test Files, LOD Optimization, V-Sekai, File Testing"
+    "text": "This proposal may not benefit developers who do not use Blender or those who prefer to use other game engines."
   },
   {
-    "objectID": "decisions/20231114-upload-creative-commons-fbx-test-files.html#the-backdrop",
-    "href": "decisions/20231114-upload-creative-commons-fbx-test-files.html#the-backdrop",
-    "title": "Proposed: Upload Creative Commons FBX Test Files for Enhanced LOD Optimization in V-Sekai",
+    "objectID": "decisions/20240529-improve-godot-import-ecosystem.html#in-core-and-done-by-us",
+    "href": "decisions/20240529-improve-godot-import-ecosystem.html#in-core-and-done-by-us",
+    "title": "Proposed: Improve the Godot Ecosystem",
     "section": "",
-    "text": "V-Sekai is continually improving its VR environments and functionalities. A key aspect of this development is optimizing Level of Detail (LOD) to enhance performance without sacrificing visual quality."
+    "text": "The proposed improvements will be implemented in the core of the Godot engine and will be carried out by our team."
   },
   {
-    "objectID": "decisions/20231114-upload-creative-commons-fbx-test-files.html#the-challenge",
-    "href": "decisions/20231114-upload-creative-commons-fbx-test-files.html#the-challenge",
-    "title": "Proposed: Upload Creative Commons FBX Test Files for Enhanced LOD Optimization in V-Sekai",
+    "objectID": "decisions/20240529-improve-godot-import-ecosystem.html#status",
+    "href": "decisions/20240529-improve-godot-import-ecosystem.html#status",
+    "title": "Proposed: Improve the Godot Ecosystem",
     "section": "",
-    "text": "Current LOD optimization processes are facing issues, notably crashing when handling multi-gigabyte FBX to OBJ test cases. This limits the ability to effectively test and optimize large, complex models in V-Sekai."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20231114-upload-creative-commons-fbx-test-files.html#the-strategy",
-    "href": "decisions/20231114-upload-creative-commons-fbx-test-files.html#the-strategy",
-    "title": "Proposed: Upload Creative Commons FBX Test Files for Enhanced LOD Optimization in V-Sekai",
+    "objectID": "decisions/20240529-improve-godot-import-ecosystem.html#decision-makers",
+    "href": "decisions/20240529-improve-godot-import-ecosystem.html#decision-makers",
+    "title": "Proposed: Improve the Godot Ecosystem",
     "section": "",
-    "text": "Propose uploading a suite of Creative Commons FBX test files, credited to bbqbarbhg, to provide a more comprehensive and challenging dataset for LOD optimization testing."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20231114-upload-creative-commons-fbx-test-files.html#the-upside",
-    "href": "decisions/20231114-upload-creative-commons-fbx-test-files.html#the-upside",
-    "title": "Proposed: Upload Creative Commons FBX Test Files for Enhanced LOD Optimization in V-Sekai",
+    "objectID": "decisions/20240529-improve-godot-import-ecosystem.html#tags",
+    "href": "decisions/20240529-improve-godot-import-ecosystem.html#tags",
+    "title": "Proposed: Improve the Godot Ecosystem",
     "section": "",
-    "text": "Having access to a diverse and complex set of FBX files will allow for more thorough testing and optimization of LOD algorithms, leading to improved performance and stability in handling large and detailed models in the V-Sekai environment."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20231114-upload-creative-commons-fbx-test-files.html#the-downside",
-    "href": "decisions/20231114-upload-creative-commons-fbx-test-files.html#the-downside",
-    "title": "Proposed: Upload Creative Commons FBX Test Files for Enhanced LOD Optimization in V-Sekai",
+    "objectID": "decisions/20240529-improve-godot-import-ecosystem.html#further-reading",
+    "href": "decisions/20240529-improve-godot-import-ecosystem.html#further-reading",
+    "title": "Proposed: Improve the Godot Ecosystem",
     "section": "",
-    "text": "The process of integrating and testing with these new files may require significant resources and time. Additionally, if the files are extremely large or complex, they may pose challenges in terms of storage and processing requirements."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20231114-upload-creative-commons-fbx-test-files.html#the-road-not-taken",
-    "href": "decisions/20231114-upload-creative-commons-fbx-test-files.html#the-road-not-taken",
-    "title": "Proposed: Upload Creative Commons FBX Test Files for Enhanced LOD Optimization in V-Sekai",
+    "objectID": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html",
+    "href": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html",
+    "title": "Proposed: Store presentation and book content via Lottie",
     "section": "",
-    "text": "Alternative approaches might involve optimizing the current LOD algorithms without the use of these specific test files, but this could limit the effectiveness of optimization efforts."
+    "text": "[Safety brochure in Lottie format]\nWe want to display book content and presentation content in groups.\nIf the original content is in vectorized format, we want to keep it.\nWe do not have enterprise levels of engineering power.\nLicenses have to be compatible with groups.\n\n\n\nLottie via Samsung’s rlottie library helps solve this problem. Lottie keeps pixel and curve data.\nRGBA8 data is big and Lottie keeps it as pixel and does not rasterize curves.\nLottie exports may turn fonts into curves.\nV-Sekai already has the rlottie implementation in Godot engine so engineering effort is minimized.\nrlottie is Groups license compatible.\n\n\n\n\n\n\nInstall synfig-studio\nIn synfig, for each page of pdf, epub, and others export a lottie json per page\nEnsure the documents are sorted correctly\nSave the folder as zstd compress 7zip archive\nName the archive .cbzl This is file that is similar to CBZ but has an extra l to make it easy to identify as Lottie.\n\n\n\n\n\nOpen the zip.\nFor each sorted entry of the zip\nMake a Godot Engine PackedScene using the Groups Lottie importer.\n\n\n\n\n\n\nIn engine presentation engine\n\n\n\n\n\nLottie is an obscure format\n\n\n\n\n\nOption: Create single executable Pdfium thing that writes to png\nRejection Reason:\nChromium build processes are difficult, but someone made a pdfium binary repository.\nOption: Import pdfium into Godot Engine as a static library\nRejection Reason:\nAdding pdf support to Godot Engine is difficult.\nThe straight-forward pdf implementation writes the RGBA8 data into the cache.\nOption: Use Godot Engine’s native SVG library\nRejection Reason:\nDoes not support pixel data.\nUnreliable\n\n\n\n\nrlottie and pdf formats are complicated.\n\n\n\nPresentations and books should be a first-class feature in groups.\n\n\n\n\nhttps://www.synfig.org/\nhttps://github.com/Samsung/rlottie\nhttps://github.com/godot-extended-libraries/lottie\nhttps://www.adobe.com/products/aftereffects.html\nhttps://airbnb.io/lottie/#/\nhttps://lottiefiles.com/\nhttps://github.com/reMarkable/pdfium-binaries\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20231114-upload-creative-commons-fbx-test-files.html#the-infrequent-use-case",
-    "href": "decisions/20231114-upload-creative-commons-fbx-test-files.html#the-infrequent-use-case",
-    "title": "Proposed: Upload Creative Commons FBX Test Files for Enhanced LOD Optimization in V-Sekai",
+    "objectID": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html#context-and-problem-statement",
+    "href": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html#context-and-problem-statement",
+    "title": "Proposed: Store presentation and book content via Lottie",
     "section": "",
-    "text": "While primarily aimed at enhancing LOD optimization, these test files could also be useful for other aspects of V-Sekai’s development, such as stress-testing the engine and other optimization tasks."
+    "text": "[Safety brochure in Lottie format]\nWe want to display book content and presentation content in groups.\nIf the original content is in vectorized format, we want to keep it.\nWe do not have enterprise levels of engineering power.\nLicenses have to be compatible with groups."
   },
   {
-    "objectID": "decisions/20231114-upload-creative-commons-fbx-test-files.html#in-core-and-done-by-us",
-    "href": "decisions/20231114-upload-creative-commons-fbx-test-files.html#in-core-and-done-by-us",
-    "title": "Proposed: Upload Creative Commons FBX Test Files for Enhanced LOD Optimization in V-Sekai",
+    "objectID": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: Store presentation and book content via Lottie",
     "section": "",
-    "text": "This initiative involves incorporating external resources (Creative Commons FBX files) into the core development and testing processes of V-Sekai, potentially requiring adjustments in testing protocols and optimization strategies."
+    "text": "Lottie via Samsung’s rlottie library helps solve this problem. Lottie keeps pixel and curve data.\nRGBA8 data is big and Lottie keeps it as pixel and does not rasterize curves.\nLottie exports may turn fonts into curves.\nV-Sekai already has the rlottie implementation in Godot engine so engineering effort is minimized.\nrlottie is Groups license compatible."
   },
   {
-    "objectID": "decisions/20231114-upload-creative-commons-fbx-test-files.html#further-reading",
-    "href": "decisions/20231114-upload-creative-commons-fbx-test-files.html#further-reading",
-    "title": "Proposed: Upload Creative Commons FBX Test Files for Enhanced LOD Optimization in V-Sekai",
+    "objectID": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Store presentation and book content via Lottie",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis article was assisted by AI assistant Aria."
+    "text": "Install synfig-studio\nIn synfig, for each page of pdf, epub, and others export a lottie json per page\nEnsure the documents are sorted correctly\nSave the folder as zstd compress 7zip archive\nName the archive .cbzl This is file that is similar to CBZ but has an extra l to make it easy to identify as Lottie.\n\n\n\n\n\nOpen the zip.\nFor each sorted entry of the zip\nMake a Godot Engine PackedScene using the Groups Lottie importer."
   },
   {
-    "objectID": "decisions/20240502-where-can-I-use-gltf.html",
-    "href": "decisions/20240502-where-can-I-use-gltf.html",
-    "title": "Proposed: Can I use V-Sekai for 3d assets & 3d extensions?",
+    "objectID": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html#positive-consequences",
+    "href": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html#positive-consequences",
+    "title": "Proposed: Store presentation and book content via Lottie",
     "section": "",
-    "text": "In the current digital landscape, there is a chaos of many different platforms.\n\n\n\nThe problem lies in the lack of interoperability among various platforms. This leads to inefficiencies and difficulties in sharing and utilizing resources across these platforms, especially when it comes to 3D assets and extensions.\n\n\n\nWe propose to develop an Elixir website that facilitates the sharing of interoperability among different file formats including fbx, usd, gltf, Godot Engine tscn, and vrm. This would allow for easier sharing and utilization of 3D assets and extensions across various platforms.\n\n\n\nThis proposal, if implemented, would streamline the process of sharing and using 3D resources across different platforms. It would also foster collaboration and innovation by making it easier for developers to utilize resources from various sources.\n\n\n\nPotential downsides could include the complexity of developing such a platform and ensuring its compatibility with all the mentioned file formats. There may also be potential security concerns that need to be addressed.\n\n\n\nAlternative solutions could involve developing individual converters for each file format, but this would not provide the same level of efficiency and convenience as a unified platform.\n\n\n\nIn cases where only one or two file formats are being used, the benefits of this platform may not be fully realized.\n\n\n\nThis project would be developed and maintained by the V-Sekai development team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\ncaniuse\n\nAI assistant Aria assisted with this article."
+    "text": "In engine presentation engine"
   },
   {
-    "objectID": "decisions/20240502-where-can-I-use-gltf.html#the-context",
-    "href": "decisions/20240502-where-can-I-use-gltf.html#the-context",
-    "title": "Proposed: Can I use V-Sekai for 3d assets & 3d extensions?",
+    "objectID": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html#negative-consequences",
+    "href": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html#negative-consequences",
+    "title": "Proposed: Store presentation and book content via Lottie",
     "section": "",
-    "text": "In the current digital landscape, there is a chaos of many different platforms."
+    "text": "Lottie is an obscure format"
   },
   {
-    "objectID": "decisions/20240502-where-can-I-use-gltf.html#the-problem-statement",
-    "href": "decisions/20240502-where-can-I-use-gltf.html#the-problem-statement",
-    "title": "Proposed: Can I use V-Sekai for 3d assets & 3d extensions?",
+    "objectID": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html#option-graveyard",
+    "href": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html#option-graveyard",
+    "title": "Proposed: Store presentation and book content via Lottie",
     "section": "",
-    "text": "The problem lies in the lack of interoperability among various platforms. This leads to inefficiencies and difficulties in sharing and utilizing resources across these platforms, especially when it comes to 3D assets and extensions."
+    "text": "Option: Create single executable Pdfium thing that writes to png\nRejection Reason:\nChromium build processes are difficult, but someone made a pdfium binary repository.\nOption: Import pdfium into Godot Engine as a static library\nRejection Reason:\nAdding pdf support to Godot Engine is difficult.\nThe straight-forward pdf implementation writes the RGBA8 data into the cache.\nOption: Use Godot Engine’s native SVG library\nRejection Reason:\nDoes not support pixel data.\nUnreliable"
   },
   {
-    "objectID": "decisions/20240502-where-can-I-use-gltf.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240502-where-can-I-use-gltf.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Can I use V-Sekai for 3d assets & 3d extensions?",
+    "objectID": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Store presentation and book content via Lottie",
     "section": "",
-    "text": "We propose to develop an Elixir website that facilitates the sharing of interoperability among different file formats including fbx, usd, gltf, Godot Engine tscn, and vrm. This would allow for easier sharing and utilization of 3D assets and extensions across various platforms."
+    "text": "rlottie and pdf formats are complicated."
   },
   {
-    "objectID": "decisions/20240502-where-can-I-use-gltf.html#the-benefits",
-    "href": "decisions/20240502-where-can-I-use-gltf.html#the-benefits",
-    "title": "Proposed: Can I use V-Sekai for 3d assets & 3d extensions?",
+    "objectID": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Store presentation and book content via Lottie",
     "section": "",
-    "text": "This proposal, if implemented, would streamline the process of sharing and using 3D resources across different platforms. It would also foster collaboration and innovation by making it easier for developers to utilize resources from various sources."
+    "text": "Presentations and books should be a first-class feature in groups."
   },
   {
-    "objectID": "decisions/20240502-where-can-I-use-gltf.html#the-downsides",
-    "href": "decisions/20240502-where-can-I-use-gltf.html#the-downsides",
-    "title": "Proposed: Can I use V-Sekai for 3d assets & 3d extensions?",
+    "objectID": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html#references",
+    "href": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html#references",
+    "title": "Proposed: Store presentation and book content via Lottie",
     "section": "",
-    "text": "Potential downsides could include the complexity of developing such a platform and ensuring its compatibility with all the mentioned file formats. There may also be potential security concerns that need to be addressed."
+    "text": "https://www.synfig.org/\nhttps://github.com/Samsung/rlottie\nhttps://github.com/godot-extended-libraries/lottie\nhttps://www.adobe.com/products/aftereffects.html\nhttps://airbnb.io/lottie/#/\nhttps://lottiefiles.com/\nhttps://github.com/reMarkable/pdfium-binaries"
   },
   {
-    "objectID": "decisions/20240502-where-can-I-use-gltf.html#the-road-not-taken",
-    "href": "decisions/20240502-where-can-I-use-gltf.html#the-road-not-taken",
-    "title": "Proposed: Can I use V-Sekai for 3d assets & 3d extensions?",
+    "objectID": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html#derivative-license",
+    "href": "decisions/20210601-store-presentation-and-book-content-via-lottie-2.html#derivative-license",
+    "title": "Proposed: Store presentation and book content via Lottie",
     "section": "",
-    "text": "Alternative solutions could involve developing individual converters for each file format, but this would not provide the same level of efficiency and convenience as a unified platform."
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240502-where-can-I-use-gltf.html#the-infrequent-use-case",
-    "href": "decisions/20240502-where-can-I-use-gltf.html#the-infrequent-use-case",
-    "title": "Proposed: Can I use V-Sekai for 3d assets & 3d extensions?",
+    "objectID": "decisions/20240410-data-storage-elixir.html",
+    "href": "decisions/20240410-data-storage-elixir.html",
+    "title": "Proposed: Implementing Elixir Data Models for Memory, Local, Bulk, and Global Storage",
     "section": "",
-    "text": "In cases where only one or two file formats are being used, the benefits of this platform may not be fully realized."
+    "text": "The goal is to effectively manage large volumes of 3D model data and game entity replication reliably and efficiently.\n\n\n\nThe current system faces challenges handling large amounts of 3D model data and managing game entity replication. This leads to performance issues and potential data loss.\n\n\n\nThe solution involves several steps to ensure data consistency and durability:\n\nContent Delivery Network (CDN): We will create a CDN similar to a static sftp file store for efficient content delivery.\nEtso for Erlang Term Storage (ETS): Etso will be configured to manage temporary, in-memory data structures with Ecto schemas in Elixir applications. This is ideal for quick data manipulation and caching.\nRaft/Ra for Distributed Consensus: Raft/Ra will be deployed to ensure distributed consensus across system nodes, which is crucial for coordinated state changes and maintaining data consistency.\nCockroachDB for Persistent Storage: CockroachDB will store critical, structured data that requires ACID transactions and global accessibility. This ensures the durability of our data.\nData Flow Management: Protocols will be established to move temporary data from Etso/ETS to the CDN for bulk storage. For structured data persistence, we will use CockroachDB.\nConsistency Management: Raft/Ra will manage write operations across the CDN and CockroachDB to ensure consistency and fault tolerance.\n\n\n\ndefmodule MyApp.Cache do\n  use Etso.Schema\n  @primary_key {:id, :binary_id, autogenerate: true}\n  field :key, :string\n  field :value, :any\nend\n\n\n\nRaft/Ra will be implemented to ensure distributed consensus across system nodes.\n\n\n\nCockroachDB will store critical, structured data that requires ACID transactions and global accessibility.\n\n\n\nThe Membrane Framework will establish Data flow protocols to move temporary data from Etso/ETS to the CDN for bulk storage and CockroachDB for structured data persistence.\n\n\n\nRaft/Ra will manage write operations across the CDN and CockroachDB, ensuring consistency and fault tolerance.\n\n\n\n\n\nEfficient storage of bulk 3D model data\nEffective management of game entity replication\nImproved system performance\nReduced risk of data loss\n\n\n\n\n\nRequires significant development effort\nPotential for increased system complexity\n\n\n\n\nTraditional databases or file systems were considered but rejected due to their limitations in handling large volumes of 3D model data and managing game entity replication.\n\n\n\nThis proposal may not be suitable for smaller projects that do not require the storage of large volumes of 3D model data or managing game entity replication.\n\n\n\nThe V-Sekai development team will implement this proposal.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team, “Bioblaze Payne”, “fire”\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAssisted by Aria."
   },
   {
-    "objectID": "decisions/20240502-where-can-I-use-gltf.html#in-core-and-done-by-us",
-    "href": "decisions/20240502-where-can-I-use-gltf.html#in-core-and-done-by-us",
-    "title": "Proposed: Can I use V-Sekai for 3d assets & 3d extensions?",
+    "objectID": "decisions/20240410-data-storage-elixir.html#context",
+    "href": "decisions/20240410-data-storage-elixir.html#context",
+    "title": "Proposed: Implementing Elixir Data Models for Memory, Local, Bulk, and Global Storage",
     "section": "",
-    "text": "This project would be developed and maintained by the V-Sekai development team."
+    "text": "The goal is to effectively manage large volumes of 3D model data and game entity replication reliably and efficiently."
   },
   {
-    "objectID": "decisions/20240502-where-can-I-use-gltf.html#status",
-    "href": "decisions/20240502-where-can-I-use-gltf.html#status",
-    "title": "Proposed: Can I use V-Sekai for 3d assets & 3d extensions?",
+    "objectID": "decisions/20240410-data-storage-elixir.html#problem-statement",
+    "href": "decisions/20240410-data-storage-elixir.html#problem-statement",
+    "title": "Proposed: Implementing Elixir Data Models for Memory, Local, Bulk, and Global Storage",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "The current system faces challenges handling large amounts of 3D model data and managing game entity replication. This leads to performance issues and potential data loss."
   },
   {
-    "objectID": "decisions/20240502-where-can-I-use-gltf.html#decision-makers",
-    "href": "decisions/20240502-where-can-I-use-gltf.html#decision-makers",
-    "title": "Proposed: Can I use V-Sekai for 3d assets & 3d extensions?",
+    "objectID": "decisions/20240410-data-storage-elixir.html#proposed-solution",
+    "href": "decisions/20240410-data-storage-elixir.html#proposed-solution",
+    "title": "Proposed: Implementing Elixir Data Models for Memory, Local, Bulk, and Global Storage",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "The solution involves several steps to ensure data consistency and durability:\n\nContent Delivery Network (CDN): We will create a CDN similar to a static sftp file store for efficient content delivery.\nEtso for Erlang Term Storage (ETS): Etso will be configured to manage temporary, in-memory data structures with Ecto schemas in Elixir applications. This is ideal for quick data manipulation and caching.\nRaft/Ra for Distributed Consensus: Raft/Ra will be deployed to ensure distributed consensus across system nodes, which is crucial for coordinated state changes and maintaining data consistency.\nCockroachDB for Persistent Storage: CockroachDB will store critical, structured data that requires ACID transactions and global accessibility. This ensures the durability of our data.\nData Flow Management: Protocols will be established to move temporary data from Etso/ETS to the CDN for bulk storage. For structured data persistence, we will use CockroachDB.\nConsistency Management: Raft/Ra will manage write operations across the CDN and CockroachDB to ensure consistency and fault tolerance.\n\n\n\ndefmodule MyApp.Cache do\n  use Etso.Schema\n  @primary_key {:id, :binary_id, autogenerate: true}\n  field :key, :string\n  field :value, :any\nend\n\n\n\nRaft/Ra will be implemented to ensure distributed consensus across system nodes.\n\n\n\nCockroachDB will store critical, structured data that requires ACID transactions and global accessibility.\n\n\n\nThe Membrane Framework will establish Data flow protocols to move temporary data from Etso/ETS to the CDN for bulk storage and CockroachDB for structured data persistence.\n\n\n\nRaft/Ra will manage write operations across the CDN and CockroachDB, ensuring consistency and fault tolerance."
   },
   {
-    "objectID": "decisions/20240502-where-can-I-use-gltf.html#tags",
-    "href": "decisions/20240502-where-can-I-use-gltf.html#tags",
-    "title": "Proposed: Can I use V-Sekai for 3d assets & 3d extensions?",
+    "objectID": "decisions/20240410-data-storage-elixir.html#benefits",
+    "href": "decisions/20240410-data-storage-elixir.html#benefits",
+    "title": "Proposed: Implementing Elixir Data Models for Memory, Local, Bulk, and Global Storage",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Efficient storage of bulk 3D model data\nEffective management of game entity replication\nImproved system performance\nReduced risk of data loss"
   },
   {
-    "objectID": "decisions/20240502-where-can-I-use-gltf.html#further-reading",
-    "href": "decisions/20240502-where-can-I-use-gltf.html#further-reading",
-    "title": "Proposed: Can I use V-Sekai for 3d assets & 3d extensions?",
+    "objectID": "decisions/20240410-data-storage-elixir.html#downsides",
+    "href": "decisions/20240410-data-storage-elixir.html#downsides",
+    "title": "Proposed: Implementing Elixir Data Models for Memory, Local, Bulk, and Global Storage",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\ncaniuse\n\nAI assistant Aria assisted with this article."
+    "text": "Requires significant development effort\nPotential for increased system complexity"
   },
   {
-    "objectID": "decisions/20240608-skin-weight-transfer-skeleton-merge.html",
-    "href": "decisions/20240608-skin-weight-transfer-skeleton-merge.html",
-    "title": "Accepted: Better Skeleton Merge with Robust Skin Weight Transfer",
+    "objectID": "decisions/20240410-data-storage-elixir.html#alternatives-considered",
+    "href": "decisions/20240410-data-storage-elixir.html#alternatives-considered",
+    "title": "Proposed: Implementing Elixir Data Models for Memory, Local, Bulk, and Global Storage",
     "section": "",
-    "text": "Rigging and clothing fitting are intricate tasks in game development, demanding a deep understanding of 3D modeling, animation, and the specific requirements of the game engine. In the context of V-Sekai, a social VR game built on the Godot Engine, these tasks become even more challenging due to the need for real-time performance and compatibility with various hardware devices.\n\n\n\nOur goal is to provide a solution that enables players and creators to incorporate their own clothing into the V-Sekai game, without turning the game into an impenetrable black box. The current process of rigging and fitting clothing onto characters is labor-intensive and requires specialized knowledge, limiting the ability of players and creators to fully express themselves through their avatars.\n\n\n\nThe proposed solution involves aligning the vertices from one set of faces to match the vertices in the other set. In Godot, this can be achieved by retrieving mesh arrays and invoking a function with arrays[Mesh.ARRAY_VERTEX], arrays[Mesh.ARRAY_INDEX].\nPassing in the Skeleton3D is not necessary. The recently merged API by smix8 allows baking a skeleton to a static mesh, which can be used for baking and then applying the delta.\nWe plan to utilize robust skin weight transfer code and robust Laplacians. The robust Laplacians algorithm is implemented in geometry-central, which loads a mesh, constructs our intrinsic tufted cover, and generates the resulting Laplace (and mass) matrix.\nPlayer creators will have a fully skin-weighted base mesh (a naked character mesh with no clothing). They can then use robust skin weight transfer with a variable distance and the infilling feature to rig their clothing for use in V-Sekai and anywhere that can handle VRM1.\n\n\n\n\nPlayer customization: Our solution empowers players to use their own clothing designs in the game, enhancing their ability to express themselves and engage with the game world.\nEnhanced game experience: By offering more customization options, we can boost player engagement and satisfaction.\n\n\n\n\n\nLimited platform support: Not all platforms support VRM1 for avatars; most only support VRM0. This could restrict the compatibility of our solution with other platforms and games.\n\n\n\n\nAn alternative approach would have been to create a set of predefined clothing options within the game itself. However, this would limit the creativity and expression of our players. By enabling them to use their own clothing designs, we are fostering a more vibrant and diverse game community.\n\n\n\nWhile the primary use case is for players to rig and fit their own clothing designs, this solution could also be used by game developers to quickly and easily rig and fit clothing for non-player characters (NPCs). This could save development time and resources.\n\n\n\nThis proposal is core to the functionality of the V-Sekai game and will be implemented by us. It aligns with our goal of creating a highly customizable and immersive social VR experience.\n\n\n\nStatus: Accepted \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nRobust Skin Weights Transfer via Weight Inpainting\nA Laplacian for Nonmanifold Triangle Meshes\n\nAI assistant Aria assisted with this article.\n\n\n\nRigging: The process of creating a skeleton for a 3D model (character or object) and defining how it can move. This is crucial for animation in video games.\nClothing Fitting: In the context of game development, this refers to the process of designing and applying clothing to a character model in a way that it moves naturally with the character’s movements.\n3D Modeling: The process of creating a three-dimensional representation of any surface or object by manipulating polygons, edges, and vertices in simulated 3D space.\nAnimation: The technique of photographing successive drawings or positions of puppets or models to create an illusion of movement when the movie is shown as a sequence.\nGame Engine: A software framework designed for the creation and development of video games. Developers use them to create games for consoles, mobile devices, and personal computers.\nReal-Time Performance: Refers to the ability of a computing system or software to instantly respond to user input. In gaming, real-time performance is critical to ensure smooth gameplay and user experience.\nVertices: In 3D modeling, a vertex is a data structure that describes certain attributes, like the position of a point in 2D or 3D space or multiple points on a surface.\nMesh Arrays: In computer graphics, a mesh is a collection of vertices, edges, and faces that define the shape of a polyhedral object in 3D applications.\nSkeleton3D: A node that represents a skeleton in Godot Engine. It contains a hierarchy of bones, which are used to animate the vertices of a MeshInstance.\nRobust Skin Weight Transfer: A method used in 3D modeling to transfer the skin weights from one model to another. This is useful when you want to apply the same skinning (deformation) properties from one model to another.\nRobust Laplacians: A method used in 3D modeling for smoothing and enhancing the quality of a mesh.\nVRM1: A file format for handling 3D humanoid avatar data for VR applications. It’s based on glTF2.0, a file format standard by Khronos Group.\nNon-Player Characters (NPCs): In video games, these are the characters that are not controlled by a player. They can be friends, foes, merchants, or even neutral parties in the game world.\nSocial VR: Virtual Reality that allows users to interact with each other in a virtual environment. It’s like social media but in VR.\nGodot Engine: An open-source game engine developed by the community-driven Godot Engine project. It’s used for creating both 2D and 3D games.\nV-Sekai: A social VR game built on the Godot Engine. The game focuses on providing a highly customizable and immersive social VR experience."
+    "text": "Traditional databases or file systems were considered but rejected due to their limitations in handling large volumes of 3D model data and managing game entity replication."
   },
   {
-    "objectID": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#the-context",
-    "href": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#the-context",
-    "title": "Accepted: Better Skeleton Merge with Robust Skin Weight Transfer",
+    "objectID": "decisions/20240410-data-storage-elixir.html#infrequent-use-case",
+    "href": "decisions/20240410-data-storage-elixir.html#infrequent-use-case",
+    "title": "Proposed: Implementing Elixir Data Models for Memory, Local, Bulk, and Global Storage",
     "section": "",
-    "text": "Rigging and clothing fitting are intricate tasks in game development, demanding a deep understanding of 3D modeling, animation, and the specific requirements of the game engine. In the context of V-Sekai, a social VR game built on the Godot Engine, these tasks become even more challenging due to the need for real-time performance and compatibility with various hardware devices."
+    "text": "This proposal may not be suitable for smaller projects that do not require the storage of large volumes of 3D model data or managing game entity replication."
   },
   {
-    "objectID": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#the-problem-statement",
-    "href": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#the-problem-statement",
-    "title": "Accepted: Better Skeleton Merge with Robust Skin Weight Transfer",
+    "objectID": "decisions/20240410-data-storage-elixir.html#implementation",
+    "href": "decisions/20240410-data-storage-elixir.html#implementation",
+    "title": "Proposed: Implementing Elixir Data Models for Memory, Local, Bulk, and Global Storage",
     "section": "",
-    "text": "Our goal is to provide a solution that enables players and creators to incorporate their own clothing into the V-Sekai game, without turning the game into an impenetrable black box. The current process of rigging and fitting clothing onto characters is labor-intensive and requires specialized knowledge, limiting the ability of players and creators to fully express themselves through their avatars."
+    "text": "The V-Sekai development team will implement this proposal."
   },
   {
-    "objectID": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Accepted: Better Skeleton Merge with Robust Skin Weight Transfer",
+    "objectID": "decisions/20240410-data-storage-elixir.html#status",
+    "href": "decisions/20240410-data-storage-elixir.html#status",
+    "title": "Proposed: Implementing Elixir Data Models for Memory, Local, Bulk, and Global Storage",
     "section": "",
-    "text": "The proposed solution involves aligning the vertices from one set of faces to match the vertices in the other set. In Godot, this can be achieved by retrieving mesh arrays and invoking a function with arrays[Mesh.ARRAY_VERTEX], arrays[Mesh.ARRAY_INDEX].\nPassing in the Skeleton3D is not necessary. The recently merged API by smix8 allows baking a skeleton to a static mesh, which can be used for baking and then applying the delta.\nWe plan to utilize robust skin weight transfer code and robust Laplacians. The robust Laplacians algorithm is implemented in geometry-central, which loads a mesh, constructs our intrinsic tufted cover, and generates the resulting Laplace (and mass) matrix.\nPlayer creators will have a fully skin-weighted base mesh (a naked character mesh with no clothing). They can then use robust skin weight transfer with a variable distance and the infilling feature to rig their clothing for use in V-Sekai and anywhere that can handle VRM1."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#the-benefits",
-    "href": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#the-benefits",
-    "title": "Accepted: Better Skeleton Merge with Robust Skin Weight Transfer",
+    "objectID": "decisions/20240410-data-storage-elixir.html#decision-makers",
+    "href": "decisions/20240410-data-storage-elixir.html#decision-makers",
+    "title": "Proposed: Implementing Elixir Data Models for Memory, Local, Bulk, and Global Storage",
     "section": "",
-    "text": "Player customization: Our solution empowers players to use their own clothing designs in the game, enhancing their ability to express themselves and engage with the game world.\nEnhanced game experience: By offering more customization options, we can boost player engagement and satisfaction."
+    "text": "V-Sekai development team, “Bioblaze Payne”, “fire”"
   },
   {
-    "objectID": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#the-downsides",
-    "href": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#the-downsides",
-    "title": "Accepted: Better Skeleton Merge with Robust Skin Weight Transfer",
+    "objectID": "decisions/20240410-data-storage-elixir.html#tags",
+    "href": "decisions/20240410-data-storage-elixir.html#tags",
+    "title": "Proposed: Implementing Elixir Data Models for Memory, Local, Bulk, and Global Storage",
     "section": "",
-    "text": "Limited platform support: Not all platforms support VRM1 for avatars; most only support VRM0. This could restrict the compatibility of our solution with other platforms and games."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#the-road-not-taken",
-    "href": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#the-road-not-taken",
-    "title": "Accepted: Better Skeleton Merge with Robust Skin Weight Transfer",
+    "objectID": "decisions/20240410-data-storage-elixir.html#further-reading",
+    "href": "decisions/20240410-data-storage-elixir.html#further-reading",
+    "title": "Proposed: Implementing Elixir Data Models for Memory, Local, Bulk, and Global Storage",
     "section": "",
-    "text": "An alternative approach would have been to create a set of predefined clothing options within the game itself. However, this would limit the creativity and expression of our players. By enabling them to use their own clothing designs, we are fostering a more vibrant and diverse game community."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAssisted by Aria."
   },
   {
-    "objectID": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#the-infrequent-use-case",
-    "href": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#the-infrequent-use-case",
-    "title": "Accepted: Better Skeleton Merge with Robust Skin Weight Transfer",
+    "objectID": "decisions/20211031-voip.html",
+    "href": "decisions/20211031-voip.html",
+    "title": "Accepted: VOIP",
     "section": "",
-    "text": "While the primary use case is for players to rig and fit their own clothing designs, this solution could also be used by game developers to quickly and easily rig and fit clothing for non-player characters (NPCs). This could save development time and resources."
+    "text": "Accepted: VOIP\n\nContext and Problem Statement\nNeed to see our work for integration testing.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nNeed to integration test our features without multiplying work.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n\nCreate a series of projects\nHave them be exportable and testable\nSee robot framework\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot workaroundable\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nI have an approach!\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#in-core-and-done-by-us",
-    "href": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#in-core-and-done-by-us",
-    "title": "Accepted: Better Skeleton Merge with Robust Skin Weight Transfer",
+    "objectID": "decisions/20231019-quest3-mocap-steam-lighthouse.html",
+    "href": "decisions/20231019-quest3-mocap-steam-lighthouse.html",
+    "title": "Proposed: Valve VR Ecosystem with Quest 3",
     "section": "",
-    "text": "This proposal is core to the functionality of the V-Sekai game and will be implemented by us. It aligns with our goal of creating a highly customizable and immersive social VR experience."
+    "text": "Status: Proposed \nDeciders: V-Sekai\nTags: V-Sekai, Valve VR Ecosystem, Quest 3\n\n\n\n\nThe conversation between iFire and cyberpunkmermaid reveals an innovative idea of creating a portable VR setup. iFire has a cart with a PCVR computer in it. This setup streams to a Quest 3, which is a virtual reality headset. The system uses portable light houses on clamped sticks for tracking.\n\n\n\nThe challenge lies in integrating the power of the Valve VR ecosystem with the portability of the Quest series. It requires careful selection and arrangement of components to create a mobile VR station that can stream your desktop to your Meta Quest 2 or 3.\n\n\n\nThe strategy involves using 6 HTC or Tundra trackers motion capture. One tracker is dedicated to the continuous calibration with the Meta Quest 3 HMD and the SteamVR ecosystem. Two are used for the foot, two for the shoulders, one for the chest, one for the hips. The setup also includes 2 or 4 light houses and requires the purchase of Virtual Desktop for the Meta Quest 3.\n\n\n\nThe upside of this setup is its portability and versatility. It essentially turns your laptop into a mobile VR station, allowing you to leverage the power of the Valve VR ecosystem anywhere you go.\n\n\n\nThe downside could be the complexity of the setup and the cost of purchasing all the necessary components. However, the benefits of having a portable VR setup may outweigh these drawbacks for many users.\n\n\n\nAn alternative approach could be to keep using the tethered VR headset like the Valve Index, but the freedom of being untethered decreases friction to VR use.\n\n\n\nIn addition to regular use, the V-Sekai-faceless repository on GitHub provides a solution for interacting with the virtual world without needing to wear the HMD (Head-Mounted Display). This can be beneficial in various scenarios such as testing or when the HMD is uncomfortable to wear for extended periods.\n\n\n\nThis setup is not part of the core V-Sekai offering but is an innovative idea proposed by members of the community. It demonstrates the potential for creativity and innovation within the V-Sekai ecosystem.\n\n\n\n\n[V-Sekai] - AI assists this article.\nOpenVR-SpaceCalibrator\nV-Sekai-faceless"
   },
   {
-    "objectID": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#status",
-    "href": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#status",
-    "title": "Accepted: Better Skeleton Merge with Robust Skin Weight Transfer",
+    "objectID": "decisions/20231019-quest3-mocap-steam-lighthouse.html#metadata",
+    "href": "decisions/20231019-quest3-mocap-steam-lighthouse.html#metadata",
+    "title": "Proposed: Valve VR Ecosystem with Quest 3",
     "section": "",
-    "text": "Status: Accepted"
+    "text": "Status: Proposed \nDeciders: V-Sekai\nTags: V-Sekai, Valve VR Ecosystem, Quest 3"
   },
   {
-    "objectID": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#decision-makers",
-    "href": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#decision-makers",
-    "title": "Accepted: Better Skeleton Merge with Robust Skin Weight Transfer",
+    "objectID": "decisions/20231019-quest3-mocap-steam-lighthouse.html#the-backdrop",
+    "href": "decisions/20231019-quest3-mocap-steam-lighthouse.html#the-backdrop",
+    "title": "Proposed: Valve VR Ecosystem with Quest 3",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "The conversation between iFire and cyberpunkmermaid reveals an innovative idea of creating a portable VR setup. iFire has a cart with a PCVR computer in it. This setup streams to a Quest 3, which is a virtual reality headset. The system uses portable light houses on clamped sticks for tracking."
   },
   {
-    "objectID": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#tags",
-    "href": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#tags",
-    "title": "Accepted: Better Skeleton Merge with Robust Skin Weight Transfer",
+    "objectID": "decisions/20231019-quest3-mocap-steam-lighthouse.html#the-challenge",
+    "href": "decisions/20231019-quest3-mocap-steam-lighthouse.html#the-challenge",
+    "title": "Proposed: Valve VR Ecosystem with Quest 3",
     "section": "",
-    "text": "V-Sekai"
+    "text": "The challenge lies in integrating the power of the Valve VR ecosystem with the portability of the Quest series. It requires careful selection and arrangement of components to create a mobile VR station that can stream your desktop to your Meta Quest 2 or 3."
   },
   {
-    "objectID": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#further-reading",
-    "href": "decisions/20240608-skin-weight-transfer-skeleton-merge.html#further-reading",
-    "title": "Accepted: Better Skeleton Merge with Robust Skin Weight Transfer",
+    "objectID": "decisions/20231019-quest3-mocap-steam-lighthouse.html#the-strategy",
+    "href": "decisions/20231019-quest3-mocap-steam-lighthouse.html#the-strategy",
+    "title": "Proposed: Valve VR Ecosystem with Quest 3",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nRobust Skin Weights Transfer via Weight Inpainting\nA Laplacian for Nonmanifold Triangle Meshes\n\nAI assistant Aria assisted with this article.\n\n\n\nRigging: The process of creating a skeleton for a 3D model (character or object) and defining how it can move. This is crucial for animation in video games.\nClothing Fitting: In the context of game development, this refers to the process of designing and applying clothing to a character model in a way that it moves naturally with the character’s movements.\n3D Modeling: The process of creating a three-dimensional representation of any surface or object by manipulating polygons, edges, and vertices in simulated 3D space.\nAnimation: The technique of photographing successive drawings or positions of puppets or models to create an illusion of movement when the movie is shown as a sequence.\nGame Engine: A software framework designed for the creation and development of video games. Developers use them to create games for consoles, mobile devices, and personal computers.\nReal-Time Performance: Refers to the ability of a computing system or software to instantly respond to user input. In gaming, real-time performance is critical to ensure smooth gameplay and user experience.\nVertices: In 3D modeling, a vertex is a data structure that describes certain attributes, like the position of a point in 2D or 3D space or multiple points on a surface.\nMesh Arrays: In computer graphics, a mesh is a collection of vertices, edges, and faces that define the shape of a polyhedral object in 3D applications.\nSkeleton3D: A node that represents a skeleton in Godot Engine. It contains a hierarchy of bones, which are used to animate the vertices of a MeshInstance.\nRobust Skin Weight Transfer: A method used in 3D modeling to transfer the skin weights from one model to another. This is useful when you want to apply the same skinning (deformation) properties from one model to another.\nRobust Laplacians: A method used in 3D modeling for smoothing and enhancing the quality of a mesh.\nVRM1: A file format for handling 3D humanoid avatar data for VR applications. It’s based on glTF2.0, a file format standard by Khronos Group.\nNon-Player Characters (NPCs): In video games, these are the characters that are not controlled by a player. They can be friends, foes, merchants, or even neutral parties in the game world.\nSocial VR: Virtual Reality that allows users to interact with each other in a virtual environment. It’s like social media but in VR.\nGodot Engine: An open-source game engine developed by the community-driven Godot Engine project. It’s used for creating both 2D and 3D games.\nV-Sekai: A social VR game built on the Godot Engine. The game focuses on providing a highly customizable and immersive social VR experience."
+    "text": "The strategy involves using 6 HTC or Tundra trackers motion capture. One tracker is dedicated to the continuous calibration with the Meta Quest 3 HMD and the SteamVR ecosystem. Two are used for the foot, two for the shoulders, one for the chest, one for the hips. The setup also includes 2 or 4 light houses and requires the purchase of Virtual Desktop for the Meta Quest 3."
   },
   {
-    "objectID": "decisions/20230527-server-cdn-session-url.html",
-    "href": "decisions/20230527-server-cdn-session-url.html",
-    "title": "Proposed: Handling access to session based game data",
+    "objectID": "decisions/20231019-quest3-mocap-steam-lighthouse.html#the-upside",
+    "href": "decisions/20231019-quest3-mocap-steam-lighthouse.html#the-upside",
+    "title": "Proposed: Valve VR Ecosystem with Quest 3",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, GPT-4\n\n\n\n\nV-Sekai is facing limitations in handling large amounts of data efficiently and securely. The current system needs improvements in data management, performance, and security.\n\n\n\nAssigning session IDs and URLs to every asset to improve data management, performance, and security.\n\n\n\n\nGenerate unique session IDs and URLs for each asset.\nStore the session IDs and URLs in a secure database.\nUse the session IDs and URLs for accessing and managing assets.\n\n\n\n\n\nImproved data management through unique identifiers for each asset.\nEnhanced security by using session IDs and URLs for access control.\nBetter performance due to efficient asset management.\n\n\n\n\n\nIncreased complexity in the system architecture.\nPotential challenges in implementing and maintaining unique session IDs and URLs.\n\n\n\n\n\nCaching assets locally: This option was considered for improving performance, but it would not address data management and security concerns.\nUsing a centralized server for asset management: This approach could improve data management but might introduce single points of failure and potential bottlenecks in performance.\nEncrypting all assets: While this would enhance security, it would not address data management issues and could negatively impact performance due to the overhead of encryption and decryption processes.\n\n\n\n\nNo, this enhancement requires significant changes to the system architecture and cannot be achieved with a simple script workaround.\n\n\n\nYes, this enhancement addresses core limitations in the V-Sekai system and should be implemented by the V-Sekai team to ensure proper integration and compatibility with existing components.\n\n\n\n\nV-Sekai"
+    "text": "The upside of this setup is its portability and versatility. It essentially turns your laptop into a mobile VR station, allowing you to leverage the power of the Valve VR ecosystem anywhere you go."
   },
   {
-    "objectID": "decisions/20230527-server-cdn-session-url.html#metadata",
-    "href": "decisions/20230527-server-cdn-session-url.html#metadata",
-    "title": "Proposed: Handling access to session based game data",
+    "objectID": "decisions/20231019-quest3-mocap-steam-lighthouse.html#the-downside",
+    "href": "decisions/20231019-quest3-mocap-steam-lighthouse.html#the-downside",
+    "title": "Proposed: Valve VR Ecosystem with Quest 3",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, GPT-4"
+    "text": "The downside could be the complexity of the setup and the cost of purchasing all the necessary components. However, the benefits of having a portable VR setup may outweigh these drawbacks for many users."
   },
   {
-    "objectID": "decisions/20230527-server-cdn-session-url.html#context-and-problem-statement",
-    "href": "decisions/20230527-server-cdn-session-url.html#context-and-problem-statement",
-    "title": "Proposed: Handling access to session based game data",
+    "objectID": "decisions/20231019-quest3-mocap-steam-lighthouse.html#the-road-not-taken",
+    "href": "decisions/20231019-quest3-mocap-steam-lighthouse.html#the-road-not-taken",
+    "title": "Proposed: Valve VR Ecosystem with Quest 3",
     "section": "",
-    "text": "V-Sekai is facing limitations in handling large amounts of data efficiently and securely. The current system needs improvements in data management, performance, and security."
+    "text": "An alternative approach could be to keep using the tethered VR headset like the Valve Index, but the freedom of being untethered decreases friction to VR use."
   },
   {
-    "objectID": "decisions/20230527-server-cdn-session-url.html#proposed-solution",
-    "href": "decisions/20230527-server-cdn-session-url.html#proposed-solution",
-    "title": "Proposed: Handling access to session based game data",
+    "objectID": "decisions/20231019-quest3-mocap-steam-lighthouse.html#the-infrequent-use-case",
+    "href": "decisions/20231019-quest3-mocap-steam-lighthouse.html#the-infrequent-use-case",
+    "title": "Proposed: Valve VR Ecosystem with Quest 3",
     "section": "",
-    "text": "Assigning session IDs and URLs to every asset to improve data management, performance, and security."
+    "text": "In addition to regular use, the V-Sekai-faceless repository on GitHub provides a solution for interacting with the virtual world without needing to wear the HMD (Head-Mounted Display). This can be beneficial in various scenarios such as testing or when the HMD is uncomfortable to wear for extended periods."
   },
   {
-    "objectID": "decisions/20230527-server-cdn-session-url.html#implementation",
-    "href": "decisions/20230527-server-cdn-session-url.html#implementation",
-    "title": "Proposed: Handling access to session based game data",
+    "objectID": "decisions/20231019-quest3-mocap-steam-lighthouse.html#in-core-and-done-by-us",
+    "href": "decisions/20231019-quest3-mocap-steam-lighthouse.html#in-core-and-done-by-us",
+    "title": "Proposed: Valve VR Ecosystem with Quest 3",
     "section": "",
-    "text": "Generate unique session IDs and URLs for each asset.\nStore the session IDs and URLs in a secure database.\nUse the session IDs and URLs for accessing and managing assets."
+    "text": "This setup is not part of the core V-Sekai offering but is an innovative idea proposed by members of the community. It demonstrates the potential for creativity and innovation within the V-Sekai ecosystem."
   },
   {
-    "objectID": "decisions/20230527-server-cdn-session-url.html#positive-consequences",
-    "href": "decisions/20230527-server-cdn-session-url.html#positive-consequences",
-    "title": "Proposed: Handling access to session based game data",
+    "objectID": "decisions/20231019-quest3-mocap-steam-lighthouse.html#further-reading",
+    "href": "decisions/20231019-quest3-mocap-steam-lighthouse.html#further-reading",
+    "title": "Proposed: Valve VR Ecosystem with Quest 3",
     "section": "",
-    "text": "Improved data management through unique identifiers for each asset.\nEnhanced security by using session IDs and URLs for access control.\nBetter performance due to efficient asset management."
+    "text": "[V-Sekai] - AI assists this article.\nOpenVR-SpaceCalibrator\nV-Sekai-faceless"
   },
   {
-    "objectID": "decisions/20230527-server-cdn-session-url.html#negative-consequences",
-    "href": "decisions/20230527-server-cdn-session-url.html#negative-consequences",
-    "title": "Proposed: Handling access to session based game data",
+    "objectID": "decisions/20231203-mesh-rwkv-test-metrics.html",
+    "href": "decisions/20231203-mesh-rwkv-test-metrics.html",
+    "title": "Draft: Initial Training of the MeshRWVK Model",
     "section": "",
-    "text": "Increased complexity in the system architecture.\nPotential challenges in implementing and maintaining unique session IDs and URLs."
+    "text": "Status: Draft\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nCurrently, there is no model for MeshRWVK. This presents a challenge in generating diverse and complex 3D shapes for virtual environments.\n\n\n\nThe lack of a model for MeshRWVK limits the diversity and complexity of 3D shapes that can be generated for virtual environments.\n\n\n\nTo address this issue, we propose to enhance the training of the GPT model using a dataset known as Objaverse-XL, which includes various categories of 3D shapes. The training phase will employ several techniques such as random shifts, scaling, and planar decimation to improve the model’s ability to create diverse shapes.\n\n\n\nThe performance of the model will be evaluated using several metrics including Minimum Matching Distance (MMD), Coverage (COV), 1-Nearest-Neighbor Accuracy (1-NNA), Chamfer Distance (CD), FID and KID scores, and compactness.\n\n\n\nEnhancing the training of the GPT model will improve its ability to generate more complex 3D shapes, allowing for greater diversity and realism in the virtual environments created by V-Sekai.\n\n\n\nThe proposed strategy may require significant computational resources and time. There may also be a learning curve associated with understanding and implementing the proposed enhancements.\n\n\n\nAn alternative approach could have been to use a different model for generating 3D shapes. However, this would require a complete overhaul of the current system and may not necessarily yield better results.\n\n\n\nThe proposed enhancements may not be necessary for simpler virtual environments. In such cases, the current implementation of the MeshGPT model may suffice.\n\n\n\nYes, the proposed enhancements will be implemented by the V-Sekai development team.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nObjaverse-XL\n\nThis article was assisted by AI assistant, Aria."
   },
   {
-    "objectID": "decisions/20230527-server-cdn-session-url.html#option-graveyard",
-    "href": "decisions/20230527-server-cdn-session-url.html#option-graveyard",
-    "title": "Proposed: Handling access to session based game data",
+    "objectID": "decisions/20231203-mesh-rwkv-test-metrics.html#metadata",
+    "href": "decisions/20231203-mesh-rwkv-test-metrics.html#metadata",
+    "title": "Draft: Initial Training of the MeshRWVK Model",
     "section": "",
-    "text": "Caching assets locally: This option was considered for improving performance, but it would not address data management and security concerns.\nUsing a centralized server for asset management: This approach could improve data management but might introduce single points of failure and potential bottlenecks in performance.\nEncrypting all assets: While this would enhance security, it would not address data management issues and could negatively impact performance due to the overhead of encryption and decryption processes."
+    "text": "Status: Draft\nDeciders: V-Sekai\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20230527-server-cdn-session-url.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230527-server-cdn-session-url.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Handling access to session based game data",
+    "objectID": "decisions/20231203-mesh-rwkv-test-metrics.html#context",
+    "href": "decisions/20231203-mesh-rwkv-test-metrics.html#context",
+    "title": "Draft: Initial Training of the MeshRWVK Model",
     "section": "",
-    "text": "No, this enhancement requires significant changes to the system architecture and cannot be achieved with a simple script workaround."
+    "text": "Currently, there is no model for MeshRWVK. This presents a challenge in generating diverse and complex 3D shapes for virtual environments."
   },
   {
-    "objectID": "decisions/20230527-server-cdn-session-url.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230527-server-cdn-session-url.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Handling access to session based game data",
+    "objectID": "decisions/20231203-mesh-rwkv-test-metrics.html#problem",
+    "href": "decisions/20231203-mesh-rwkv-test-metrics.html#problem",
+    "title": "Draft: Initial Training of the MeshRWVK Model",
     "section": "",
-    "text": "Yes, this enhancement addresses core limitations in the V-Sekai system and should be implemented by the V-Sekai team to ensure proper integration and compatibility with existing components."
+    "text": "The lack of a model for MeshRWVK limits the diversity and complexity of 3D shapes that can be generated for virtual environments."
   },
   {
-    "objectID": "decisions/20230527-server-cdn-session-url.html#references",
-    "href": "decisions/20230527-server-cdn-session-url.html#references",
-    "title": "Proposed: Handling access to session based game data",
+    "objectID": "decisions/20231203-mesh-rwkv-test-metrics.html#solution",
+    "href": "decisions/20231203-mesh-rwkv-test-metrics.html#solution",
+    "title": "Draft: Initial Training of the MeshRWVK Model",
     "section": "",
-    "text": "V-Sekai"
+    "text": "To address this issue, we propose to enhance the training of the GPT model using a dataset known as Objaverse-XL, which includes various categories of 3D shapes. The training phase will employ several techniques such as random shifts, scaling, and planar decimation to improve the model’s ability to create diverse shapes."
   },
   {
-    "objectID": "decisions/20231111-ayon-evaluation.html",
-    "href": "decisions/20231111-ayon-evaluation.html",
-    "title": "Proposed: Evaluate AYON pipeline platform on hosted cloud services",
+    "objectID": "decisions/20231203-mesh-rwkv-test-metrics.html#evaluation",
+    "href": "decisions/20231203-mesh-rwkv-test-metrics.html#evaluation",
+    "title": "Draft: Initial Training of the MeshRWVK Model",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\n\n\nAYON is an open-source pipeline platform designed for creative studios, particularly those involved in animation and visual effects (VFX). It provides a robust and scalable solution for managing and executing creative projects. AYON’s source code is publicly accessible, allowing for community-driven development and customization. It is geared towards creative studios, particularly those working in animation and VFX. Evolved from OpenPype, it has been used since 2018 in various production environments. Supported and funded by the creative industry, AYON also offers comprehensive documentation for users, including guides for administrators and developers.\n\n\n\nHosted cloud services provide a flexible and scalable infrastructure solution that can be tailored to meet the specific needs of an organization. They offer a range of services including compute power, storage, and networking capabilities, as well as advanced services such as machine learning and data analytics. These services are typically provided on a pay-as-you-go basis, making them a cost-effective option for many organizations.\n\n\n\n\nEvaluate AYON on hosted cloud services for a game development studio.\n\n\n\nDeploy AYON using a single Docker image with hosted cloud services for Redis and PostgreSQL.\n\n\nRun a release of https://github.com/ynput/OpenPype/releases on Windows 11 desktop.\n\n\n\nWhy does OpenPype use mongodb?\n\n\n\n\nNext, we will configure AYON according to the needs of a typical game development studio. This includes setting up workflows for creating assets and assemblages in Blender, and importing them into the Godot Engine.\n\nSet the fps to 30.\nSet the resolution to 3840 × 2160\n\n\n\n\n\nIn this step, we will integrate Google Drive with the AYON homesite. This will allow us to store all our files and data directly into Google Drive from the AYON homesite.\n\n\n\nWe will then run a series of tests to assess the performance, reliability, and usability of AYON on hosted cloud services. These tests will simulate tasks a 3D game studio would typically perform, such as creating and modifying assets in Blender, and importing these assets into the Godot Engine.\n\n\n\nFinally, we will document our findings from the tests and provide recommendations based on the evaluation results. This will help us understand how well AYON performs on hosted cloud services, and whether it is a suitable solution for game development studios using the Godot Engine.\n\n\n\n\nImplementing AYON on hosted cloud services could potentially streamline the workflow of game development studios, making project management more efficient and effective.\n\n\n\nThere may be compatibility issues between AYON and hosted cloud services that could affect performance or functionality. Additionally, there may be a learning curve for teams unfamiliar with AYON.\n\n\n\nAlternative solutions such as proprietary pipeline platforms were considered. However, the open-source nature of AYON provides more flexibility and customization options.\n\n\n\nIn cases where the studio is working on multiple platforms or using a variety of software, additional configuration and testing may be required to ensure AYON works seamlessly across all environments.\n\n\n\nThis evaluation aligns with our core competencies in evaluating and implementing technology solutions. As such, it should be executed by our team.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nAYON Docker\nayon-2023-8-production-beta\n\nThis article was assisted by AI assistant Aria."
+    "text": "The performance of the model will be evaluated using several metrics including Minimum Matching Distance (MMD), Coverage (COV), 1-Nearest-Neighbor Accuracy (1-NNA), Chamfer Distance (CD), FID and KID scores, and compactness."
   },
   {
-    "objectID": "decisions/20231111-ayon-evaluation.html#metadata",
-    "href": "decisions/20231111-ayon-evaluation.html#metadata",
-    "title": "Proposed: Evaluate AYON pipeline platform on hosted cloud services",
+    "objectID": "decisions/20231203-mesh-rwkv-test-metrics.html#benefits",
+    "href": "decisions/20231203-mesh-rwkv-test-metrics.html#benefits",
+    "title": "Draft: Initial Training of the MeshRWVK Model",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai"
+    "text": "Enhancing the training of the GPT model will improve its ability to generate more complex 3D shapes, allowing for greater diversity and realism in the virtual environments created by V-Sekai."
   },
   {
-    "objectID": "decisions/20231111-ayon-evaluation.html#the-backdrop",
-    "href": "decisions/20231111-ayon-evaluation.html#the-backdrop",
-    "title": "Proposed: Evaluate AYON pipeline platform on hosted cloud services",
+    "objectID": "decisions/20231203-mesh-rwkv-test-metrics.html#risks",
+    "href": "decisions/20231203-mesh-rwkv-test-metrics.html#risks",
+    "title": "Draft: Initial Training of the MeshRWVK Model",
     "section": "",
-    "text": "AYON is an open-source pipeline platform designed for creative studios, particularly those involved in animation and visual effects (VFX). It provides a robust and scalable solution for managing and executing creative projects. AYON’s source code is publicly accessible, allowing for community-driven development and customization. It is geared towards creative studios, particularly those working in animation and VFX. Evolved from OpenPype, it has been used since 2018 in various production environments. Supported and funded by the creative industry, AYON also offers comprehensive documentation for users, including guides for administrators and developers.\n\n\n\nHosted cloud services provide a flexible and scalable infrastructure solution that can be tailored to meet the specific needs of an organization. They offer a range of services including compute power, storage, and networking capabilities, as well as advanced services such as machine learning and data analytics. These services are typically provided on a pay-as-you-go basis, making them a cost-effective option for many organizations."
+    "text": "The proposed strategy may require significant computational resources and time. There may also be a learning curve associated with understanding and implementing the proposed enhancements."
   },
   {
-    "objectID": "decisions/20231111-ayon-evaluation.html#the-challenge",
-    "href": "decisions/20231111-ayon-evaluation.html#the-challenge",
-    "title": "Proposed: Evaluate AYON pipeline platform on hosted cloud services",
+    "objectID": "decisions/20231203-mesh-rwkv-test-metrics.html#alternatives",
+    "href": "decisions/20231203-mesh-rwkv-test-metrics.html#alternatives",
+    "title": "Draft: Initial Training of the MeshRWVK Model",
     "section": "",
-    "text": "Evaluate AYON on hosted cloud services for a game development studio."
+    "text": "An alternative approach could have been to use a different model for generating 3D shapes. However, this would require a complete overhaul of the current system and may not necessarily yield better results."
   },
   {
-    "objectID": "decisions/20231111-ayon-evaluation.html#the-strategy",
-    "href": "decisions/20231111-ayon-evaluation.html#the-strategy",
-    "title": "Proposed: Evaluate AYON pipeline platform on hosted cloud services",
+    "objectID": "decisions/20231203-mesh-rwkv-test-metrics.html#limitations",
+    "href": "decisions/20231203-mesh-rwkv-test-metrics.html#limitations",
+    "title": "Draft: Initial Training of the MeshRWVK Model",
     "section": "",
-    "text": "Deploy AYON using a single Docker image with hosted cloud services for Redis and PostgreSQL.\n\n\nRun a release of https://github.com/ynput/OpenPype/releases on Windows 11 desktop.\n\n\n\nWhy does OpenPype use mongodb?\n\n\n\n\nNext, we will configure AYON according to the needs of a typical game development studio. This includes setting up workflows for creating assets and assemblages in Blender, and importing them into the Godot Engine.\n\nSet the fps to 30.\nSet the resolution to 3840 × 2160\n\n\n\n\n\nIn this step, we will integrate Google Drive with the AYON homesite. This will allow us to store all our files and data directly into Google Drive from the AYON homesite.\n\n\n\nWe will then run a series of tests to assess the performance, reliability, and usability of AYON on hosted cloud services. These tests will simulate tasks a 3D game studio would typically perform, such as creating and modifying assets in Blender, and importing these assets into the Godot Engine.\n\n\n\nFinally, we will document our findings from the tests and provide recommendations based on the evaluation results. This will help us understand how well AYON performs on hosted cloud services, and whether it is a suitable solution for game development studios using the Godot Engine."
+    "text": "The proposed enhancements may not be necessary for simpler virtual environments. In such cases, the current implementation of the MeshGPT model may suffice."
   },
   {
-    "objectID": "decisions/20231111-ayon-evaluation.html#the-upside",
-    "href": "decisions/20231111-ayon-evaluation.html#the-upside",
-    "title": "Proposed: Evaluate AYON pipeline platform on hosted cloud services",
+    "objectID": "decisions/20231203-mesh-rwkv-test-metrics.html#implementation",
+    "href": "decisions/20231203-mesh-rwkv-test-metrics.html#implementation",
+    "title": "Draft: Initial Training of the MeshRWVK Model",
     "section": "",
-    "text": "Implementing AYON on hosted cloud services could potentially streamline the workflow of game development studios, making project management more efficient and effective."
+    "text": "Yes, the proposed enhancements will be implemented by the V-Sekai development team."
   },
   {
-    "objectID": "decisions/20231111-ayon-evaluation.html#the-downside",
-    "href": "decisions/20231111-ayon-evaluation.html#the-downside",
-    "title": "Proposed: Evaluate AYON pipeline platform on hosted cloud services",
+    "objectID": "decisions/20231203-mesh-rwkv-test-metrics.html#references",
+    "href": "decisions/20231203-mesh-rwkv-test-metrics.html#references",
+    "title": "Draft: Initial Training of the MeshRWVK Model",
     "section": "",
-    "text": "There may be compatibility issues between AYON and hosted cloud services that could affect performance or functionality. Additionally, there may be a learning curve for teams unfamiliar with AYON."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nObjaverse-XL\n\nThis article was assisted by AI assistant, Aria."
   },
   {
-    "objectID": "decisions/20231111-ayon-evaluation.html#the-road-not-taken",
-    "href": "decisions/20231111-ayon-evaluation.html#the-road-not-taken",
-    "title": "Proposed: Evaluate AYON pipeline platform on hosted cloud services",
+    "objectID": "decisions/20220215-uro-deployment-process.html",
+    "href": "decisions/20220215-uro-deployment-process.html",
+    "title": "Proposed: To deploy backend services like Uro safely use a defined process",
     "section": "",
-    "text": "Alternative solutions such as proprietary pipeline platforms were considered. However, the open-source nature of AYON provides more flexibility and customization options."
+    "text": "Status: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nWe need a process for deploying Uro and other backend services safely\n\n\n\nCommit code to uro sandbox branch\n- GoCD job creates uro-sandbox docker image\n- docker image is auto deployed to sandbox\nPR merges code to uro main branch\n- GoCD job creates uro docker image\n- docker image is auto deployed to staging (A/B)\n- manual interface to swap staging and live branch\n\n\n\nNot done yet. Probably relies on a custom Elixir service in Kubernetes using Role-Based Access Control, so it can automatically change services:\nhttps://kubernetes.io/docs/reference/access-authn-authz/rbac/\n\n\n\n\n[e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]\n\n\n\n\n\n[e.g., compromising quality attribute, follow-up decisions required, …]\n\n[this section can be repeated for each option if more than one option is open for consideration]\n\n\n\n\nOption: \nRejection Reason: \n\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\n\n\n\nIs there a reason why this should be core and done by us?\n\n\n\n\nLink type \n\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20231111-ayon-evaluation.html#the-infrequent-use-case",
-    "href": "decisions/20231111-ayon-evaluation.html#the-infrequent-use-case",
-    "title": "Proposed: Evaluate AYON pipeline platform on hosted cloud services",
+    "objectID": "decisions/20220215-uro-deployment-process.html#context-and-problem-statement",
+    "href": "decisions/20220215-uro-deployment-process.html#context-and-problem-statement",
+    "title": "Proposed: To deploy backend services like Uro safely use a defined process",
     "section": "",
-    "text": "In cases where the studio is working on multiple platforms or using a variety of software, additional configuration and testing may be required to ensure AYON works seamlessly across all environments."
+    "text": "We need a process for deploying Uro and other backend services safely"
   },
   {
-    "objectID": "decisions/20231111-ayon-evaluation.html#in-core-and-done-by-us",
-    "href": "decisions/20231111-ayon-evaluation.html#in-core-and-done-by-us",
-    "title": "Proposed: Evaluate AYON pipeline platform on hosted cloud services",
+    "objectID": "decisions/20220215-uro-deployment-process.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20220215-uro-deployment-process.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: To deploy backend services like Uro safely use a defined process",
     "section": "",
-    "text": "This evaluation aligns with our core competencies in evaluating and implementing technology solutions. As such, it should be executed by our team."
+    "text": "Commit code to uro sandbox branch\n- GoCD job creates uro-sandbox docker image\n- docker image is auto deployed to sandbox\nPR merges code to uro main branch\n- GoCD job creates uro docker image\n- docker image is auto deployed to staging (A/B)\n- manual interface to swap staging and live branch"
   },
   {
-    "objectID": "decisions/20231111-ayon-evaluation.html#further-reading",
-    "href": "decisions/20231111-ayon-evaluation.html#further-reading",
-    "title": "Proposed: Evaluate AYON pipeline platform on hosted cloud services",
+    "objectID": "decisions/20220215-uro-deployment-process.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20220215-uro-deployment-process.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: To deploy backend services like Uro safely use a defined process",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nAYON Docker\nayon-2023-8-production-beta\n\nThis article was assisted by AI assistant Aria."
+    "text": "Not done yet. Probably relies on a custom Elixir service in Kubernetes using Role-Based Access Control, so it can automatically change services:\nhttps://kubernetes.io/docs/reference/access-authn-authz/rbac/"
   },
   {
-    "objectID": "decisions/20230716-enhancing-avatar-creation-process-02-advanced.html",
-    "href": "decisions/20230716-enhancing-avatar-creation-process-02-advanced.html",
-    "title": "Proposed: Enhancing Avatar Creation Process in V-Sekai Advanced",
+    "objectID": "decisions/20220215-uro-deployment-process.html#positive-consequences",
+    "href": "decisions/20220215-uro-deployment-process.html#positive-consequences",
+    "title": "Proposed: To deploy backend services like Uro safely use a defined process",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nV-Sekai currently has limitations when it comes to creating avatars with specific features and customizations. This can be a hindrance for users who want to have more control over the appearance of their avatars. To address this, we propose an enhancement that introduces various tools and techniques to overcome these limitations and provide a more comprehensive avatar creation process.\n\n\n\nHere is a list of raw processes to be broken down.\n\n\n\nSource: The source will provide the initial avatar model and any additional assets required. The input mime type for the source could be application/gltf+json or model/gltf+json if the avatar is in GLTF format, or image/png or image/svg+xml if the avatar is provided as a 2D image.\nFilter: The filter will handle all the customization steps mentioned above. It will take the input from the source and apply the necessary modifications to create the desired avatar. The input mime type for the filter would be the same as the output mime type of the source, depending on whether the avatar is in GLTF format or represented as an image.\nSink: The sink will receive the customized avatar from the filter and store it as the final output. For this project, the sink should support both PNG and SVG images for 2D avatars, and GLTF for 3D avatars. Therefore, the output mime types for the sink would be image/png or image/svg+xml for 2D avatars, and application/gltf+json or model/gltf+json for 3D avatars.\n\nNote: To avoid lossy formats, we are using PNG or SVG for 2D images and GLTF for 3D formats. PNG and SVG are lossless image formats, while GLTF is a lossless 3D format that preserves the fidelity of the avatar model.\n\n\n\nHere are the converted inputs and outputs in the xstate format for each step:\n\nImporting the avatar into Godot Engine and “Project Mirage”:\n\nInput: .vrm file\nOutput: .vrm file\n\nRefining the imported avatar:\n\nInput: .vrm file\nOutput: .vrm file\n\nConverting spring bone to physical simulation bones and colliders:\n\nInput: .vrm file\nOutput: assetpackage file\n\nAddressing painting errors:\n\nInput: .vrm file\nOutput: .vrm file\n\nChoosing a material:\n\nInput: .vrm file\nOutput: .vrm file\n\nResolving issues with materials and bones:\n\nInput: .vrm file\nOutput: .vrm file\n\nCorrecting colors and addressing pleated folds:\n\nInput: .vrm file\nOutput: .vrm file\n\nCreating complex geometric structures:\n\nInput: .vrm file\nOutput: .vrm file\n\nUtilizing Vroid Hub’s hair painter and mesh generator:\n\n\nInput: .vrm file\nOutput: .vrm enhanced data\n\n\nAdding facial expressions for motion capture:\n\n\nInput: .vrm file\nOutput: .gltf motion capture data\n\n\nSetting up motion capture:\n\n\nInput: .vrm file\nOutput: vrm animations data stored as .gltf.\n\n\n\n\n\n\nUsers will be able to create highly customizable avatars with specific features.\nThe avatar creation process will be enhanced with a variety of tools and techniques.\nDetailed customization of colors, clothing, accessories, and facial expressions will be possible.\nMotion capture capabilities can be integrated for more realistic animations.\n\n\n\n\n\nThe implementation process is complex and may require advanced technical skills from users.\nSome steps, like creating a 3D model of the back of the avatar, may not always be successful.\nPainting errors and other imperfections may remain in the final avatar.\n\n\n\n\n\nExcessive complexity or technical requirements: We want the avatar creation process to be user-friendly and accessible to a wide range of users, so any options that require advanced technical skills or have excessively complex customization controls will not be included.\n\n\n\n\nNo, the proposed enhancement involves a multi-step process that cannot be easily replicated with just a few lines of script.\n\n\n\nThe proposed enhancement addresses the limitations in V-Sekai’s avatar creation process, providing users with a comprehensive solution for creating highly customizable avatars. By implementing these tools and techniques within the platform, V-Sekai can offer a more robust and user-friendly experience for its community.\n\n\n\n\nV-Sekai"
+    "text": "[e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]"
   },
   {
-    "objectID": "decisions/20230716-enhancing-avatar-creation-process-02-advanced.html#metadata",
-    "href": "decisions/20230716-enhancing-avatar-creation-process-02-advanced.html#metadata",
-    "title": "Proposed: Enhancing Avatar Creation Process in V-Sekai Advanced",
+    "objectID": "decisions/20220215-uro-deployment-process.html#negative-consequences",
+    "href": "decisions/20220215-uro-deployment-process.html#negative-consequences",
+    "title": "Proposed: To deploy backend services like Uro safely use a defined process",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai"
+    "text": "[e.g., compromising quality attribute, follow-up decisions required, …]\n\n[this section can be repeated for each option if more than one option is open for consideration]"
   },
   {
-    "objectID": "decisions/20230716-enhancing-avatar-creation-process-02-advanced.html#context-and-problem-statement",
-    "href": "decisions/20230716-enhancing-avatar-creation-process-02-advanced.html#context-and-problem-statement",
-    "title": "Proposed: Enhancing Avatar Creation Process in V-Sekai Advanced",
+    "objectID": "decisions/20220215-uro-deployment-process.html#option-graveyard",
+    "href": "decisions/20220215-uro-deployment-process.html#option-graveyard",
+    "title": "Proposed: To deploy backend services like Uro safely use a defined process",
     "section": "",
-    "text": "V-Sekai currently has limitations when it comes to creating avatars with specific features and customizations. This can be a hindrance for users who want to have more control over the appearance of their avatars. To address this, we propose an enhancement that introduces various tools and techniques to overcome these limitations and provide a more comprehensive avatar creation process."
+    "text": "Option: \nRejection Reason:"
   },
   {
-    "objectID": "decisions/20230716-enhancing-avatar-creation-process-02-advanced.html#proposed-solution",
-    "href": "decisions/20230716-enhancing-avatar-creation-process-02-advanced.html#proposed-solution",
-    "title": "Proposed: Enhancing Avatar Creation Process in V-Sekai Advanced",
+    "objectID": "decisions/20220215-uro-deployment-process.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20220215-uro-deployment-process.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: To deploy backend services like Uro safely use a defined process",
     "section": "",
-    "text": "Here is a list of raw processes to be broken down.\n\n\n\nSource: The source will provide the initial avatar model and any additional assets required. The input mime type for the source could be application/gltf+json or model/gltf+json if the avatar is in GLTF format, or image/png or image/svg+xml if the avatar is provided as a 2D image.\nFilter: The filter will handle all the customization steps mentioned above. It will take the input from the source and apply the necessary modifications to create the desired avatar. The input mime type for the filter would be the same as the output mime type of the source, depending on whether the avatar is in GLTF format or represented as an image.\nSink: The sink will receive the customized avatar from the filter and store it as the final output. For this project, the sink should support both PNG and SVG images for 2D avatars, and GLTF for 3D avatars. Therefore, the output mime types for the sink would be image/png or image/svg+xml for 2D avatars, and application/gltf+json or model/gltf+json for 3D avatars.\n\nNote: To avoid lossy formats, we are using PNG or SVG for 2D images and GLTF for 3D formats. PNG and SVG are lossless image formats, while GLTF is a lossless 3D format that preserves the fidelity of the avatar model.\n\n\n\nHere are the converted inputs and outputs in the xstate format for each step:\n\nImporting the avatar into Godot Engine and “Project Mirage”:\n\nInput: .vrm file\nOutput: .vrm file\n\nRefining the imported avatar:\n\nInput: .vrm file\nOutput: .vrm file\n\nConverting spring bone to physical simulation bones and colliders:\n\nInput: .vrm file\nOutput: assetpackage file\n\nAddressing painting errors:\n\nInput: .vrm file\nOutput: .vrm file\n\nChoosing a material:\n\nInput: .vrm file\nOutput: .vrm file\n\nResolving issues with materials and bones:\n\nInput: .vrm file\nOutput: .vrm file\n\nCorrecting colors and addressing pleated folds:\n\nInput: .vrm file\nOutput: .vrm file\n\nCreating complex geometric structures:\n\nInput: .vrm file\nOutput: .vrm file\n\nUtilizing Vroid Hub’s hair painter and mesh generator:\n\n\nInput: .vrm file\nOutput: .vrm enhanced data\n\n\nAdding facial expressions for motion capture:\n\n\nInput: .vrm file\nOutput: .gltf motion capture data\n\n\nSetting up motion capture:\n\n\nInput: .vrm file\nOutput: vrm animations data stored as .gltf."
+    "text": "If this enhancement will not be used often, can it be worked around with a few lines of script?"
   },
   {
-    "objectID": "decisions/20230716-enhancing-avatar-creation-process-02-advanced.html#positive-consequences",
-    "href": "decisions/20230716-enhancing-avatar-creation-process-02-advanced.html#positive-consequences",
-    "title": "Proposed: Enhancing Avatar Creation Process in V-Sekai Advanced",
+    "objectID": "decisions/20220215-uro-deployment-process.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20220215-uro-deployment-process.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: To deploy backend services like Uro safely use a defined process",
     "section": "",
-    "text": "Users will be able to create highly customizable avatars with specific features.\nThe avatar creation process will be enhanced with a variety of tools and techniques.\nDetailed customization of colors, clothing, accessories, and facial expressions will be possible.\nMotion capture capabilities can be integrated for more realistic animations."
+    "text": "Is there a reason why this should be core and done by us?"
   },
   {
-    "objectID": "decisions/20230716-enhancing-avatar-creation-process-02-advanced.html#negative-consequences",
-    "href": "decisions/20230716-enhancing-avatar-creation-process-02-advanced.html#negative-consequences",
-    "title": "Proposed: Enhancing Avatar Creation Process in V-Sekai Advanced",
+    "objectID": "decisions/20220215-uro-deployment-process.html#references",
+    "href": "decisions/20220215-uro-deployment-process.html#references",
+    "title": "Proposed: To deploy backend services like Uro safely use a defined process",
     "section": "",
-    "text": "The implementation process is complex and may require advanced technical skills from users.\nSome steps, like creating a 3D model of the back of the avatar, may not always be successful.\nPainting errors and other imperfections may remain in the final avatar."
+    "text": "Link type"
   },
   {
-    "objectID": "decisions/20230716-enhancing-avatar-creation-process-02-advanced.html#option-graveyard",
-    "href": "decisions/20230716-enhancing-avatar-creation-process-02-advanced.html#option-graveyard",
-    "title": "Proposed: Enhancing Avatar Creation Process in V-Sekai Advanced",
+    "objectID": "decisions/20220215-uro-deployment-process.html#derivative-license",
+    "href": "decisions/20220215-uro-deployment-process.html#derivative-license",
+    "title": "Proposed: To deploy backend services like Uro safely use a defined process",
     "section": "",
-    "text": "Excessive complexity or technical requirements: We want the avatar creation process to be user-friendly and accessible to a wide range of users, so any options that require advanced technical skills or have excessively complex customization controls will not be included."
+    "text": "Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230716-enhancing-avatar-creation-process-02-advanced.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230716-enhancing-avatar-creation-process-02-advanced.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Enhancing Avatar Creation Process in V-Sekai Advanced",
+    "objectID": "decisions/20231228-v-sekai-slogan.html",
+    "href": "decisions/20231228-v-sekai-slogan.html",
+    "title": "Proposed: V-Sekai: Gateways to Virtual Worlds",
     "section": "",
-    "text": "No, the proposed enhancement involves a multi-step process that cannot be easily replicated with just a few lines of script."
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, Slogan, Virtual Reality, VR\n\n\n\n\nV-Sekai is a project in the realm of virtual reality. Our aim is to create immersive and interactive virtual worlds that offer users an awesome experience.\n\n\n\nIt’s important to have a slogan that encapsulates our vision and mission. It should be catchy, memorable, and reflective of what we do.\n\n\n\nWe propose the slogan: V-Sekai: Gateways to Virtual Worlds\nThis slogan succinctly communicates our goal of providing access to expansive virtual realities.\n\n\n\nThe proposed slogan is concise, catchy, and directly related to our work. It emphasizes our role as a gateway to new, immersive experiences.\n\n\n\nThe term “Virtual Worlds” might be too broad or vague for some people, potentially leading to misunderstandings about our specific services.\n\n\n\nAlternative slogans were considered, such as “V-Sekai: Forging Gateways to Virtual Worlds”, but they didn’t convey our message as effectively.\n\n\n\nFor those unfamiliar with the concept of virtual reality, the slogan might require further explanation.\n\n\n\nYes, this proposal was created internally by the V-Sekai team with assistance from AI assistant Aria.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\nVket 2023: Tram Ride\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20230716-enhancing-avatar-creation-process-02-advanced.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230716-enhancing-avatar-creation-process-02-advanced.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Enhancing Avatar Creation Process in V-Sekai Advanced",
+    "objectID": "decisions/20231228-v-sekai-slogan.html#metadata",
+    "href": "decisions/20231228-v-sekai-slogan.html#metadata",
+    "title": "Proposed: V-Sekai: Gateways to Virtual Worlds",
     "section": "",
-    "text": "The proposed enhancement addresses the limitations in V-Sekai’s avatar creation process, providing users with a comprehensive solution for creating highly customizable avatars. By implementing these tools and techniques within the platform, V-Sekai can offer a more robust and user-friendly experience for its community."
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, Slogan, Virtual Reality, VR"
   },
   {
-    "objectID": "decisions/20230716-enhancing-avatar-creation-process-02-advanced.html#references",
-    "href": "decisions/20230716-enhancing-avatar-creation-process-02-advanced.html#references",
-    "title": "Proposed: Enhancing Avatar Creation Process in V-Sekai Advanced",
+    "objectID": "decisions/20231228-v-sekai-slogan.html#the-backdrop",
+    "href": "decisions/20231228-v-sekai-slogan.html#the-backdrop",
+    "title": "Proposed: V-Sekai: Gateways to Virtual Worlds",
     "section": "",
-    "text": "V-Sekai"
+    "text": "V-Sekai is a project in the realm of virtual reality. Our aim is to create immersive and interactive virtual worlds that offer users an awesome experience."
   },
   {
-    "objectID": "decisions/20240330-bitnami-rancher-helm-catalog.html",
-    "href": "decisions/20240330-bitnami-rancher-helm-catalog.html",
-    "title": "Proposed: Installing Helm Chart from a Git Repository using Rancher",
+    "objectID": "decisions/20231228-v-sekai-slogan.html#the-challenge",
+    "href": "decisions/20231228-v-sekai-slogan.html#the-challenge",
+    "title": "Proposed: V-Sekai: Gateways to Virtual Worlds",
     "section": "",
-    "text": "Rancher is an open-source platform for managing Kubernetes at scale. It provides a user-friendly interface for deploying, scaling and managing applications on top of Kubernetes.\n\n\n\nYou want to install a Helm chart from a specific location, in this case, a Git repository: https://charts.bitnami.com/bitnami, using Rancher.\n\n\n\nRancher does not directly support installing Helm charts from a Git repository. However, you can add the Git repository as a catalog in Rancher, and then use Rancher’s UI to deploy the chart.\nHere’s how you can do it:\n\nNavigate to the Rancher UI.\nGo to Global -&gt; Catalogs.\nClick on “Add Catalog”, fill in the details:\n\nName: Give your catalog a name.\nURL: Enter the URL of your Git repository (https://charts.bitnami.com/bitnami).\nBranch: Specify the branch to use (usually master or main).\n\nClick on “Create”.\nNow, you can navigate to your project, click on “Apps” -&gt; “Launch”, and you should see your newly added catalog. You can select the chart you want to install and follow the prompts.\n\n\n\n\nThis method allows you to manage and deploy Helm charts directly from the Rancher UI, providing a more user-friendly way to handle deployments.\n\n\n\nThe main downside is that this method requires manual setup in the Rancher UI, which might not be ideal for automated workflows.\n\n\n\nAn alternative approach would be to clone the Git repository locally, package the chart into a .tgz file, and upload it directly to Rancher.\n\n\n\nThis approach is particularly useful when you want to manage your Helm charts and deployments through a user-friendly interface, rather than dealing with command-line tools.\n\n\n\nThis solution is based on the core functionality provided by Rancher and does not require any additional tools or services.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\nbitnami/charts\n\nThis article was assisted by Aria, your AI assistant."
+    "text": "It’s important to have a slogan that encapsulates our vision and mission. It should be catchy, memorable, and reflective of what we do."
   },
   {
-    "objectID": "decisions/20240330-bitnami-rancher-helm-catalog.html#context",
-    "href": "decisions/20240330-bitnami-rancher-helm-catalog.html#context",
-    "title": "Proposed: Installing Helm Chart from a Git Repository using Rancher",
+    "objectID": "decisions/20231228-v-sekai-slogan.html#the-strategy",
+    "href": "decisions/20231228-v-sekai-slogan.html#the-strategy",
+    "title": "Proposed: V-Sekai: Gateways to Virtual Worlds",
     "section": "",
-    "text": "Rancher is an open-source platform for managing Kubernetes at scale. It provides a user-friendly interface for deploying, scaling and managing applications on top of Kubernetes."
+    "text": "We propose the slogan: V-Sekai: Gateways to Virtual Worlds\nThis slogan succinctly communicates our goal of providing access to expansive virtual realities."
   },
   {
-    "objectID": "decisions/20240330-bitnami-rancher-helm-catalog.html#problem-statement",
-    "href": "decisions/20240330-bitnami-rancher-helm-catalog.html#problem-statement",
-    "title": "Proposed: Installing Helm Chart from a Git Repository using Rancher",
+    "objectID": "decisions/20231228-v-sekai-slogan.html#the-upside",
+    "href": "decisions/20231228-v-sekai-slogan.html#the-upside",
+    "title": "Proposed: V-Sekai: Gateways to Virtual Worlds",
     "section": "",
-    "text": "You want to install a Helm chart from a specific location, in this case, a Git repository: https://charts.bitnami.com/bitnami, using Rancher."
+    "text": "The proposed slogan is concise, catchy, and directly related to our work. It emphasizes our role as a gateway to new, immersive experiences."
   },
   {
-    "objectID": "decisions/20240330-bitnami-rancher-helm-catalog.html#solution",
-    "href": "decisions/20240330-bitnami-rancher-helm-catalog.html#solution",
-    "title": "Proposed: Installing Helm Chart from a Git Repository using Rancher",
+    "objectID": "decisions/20231228-v-sekai-slogan.html#the-downside",
+    "href": "decisions/20231228-v-sekai-slogan.html#the-downside",
+    "title": "Proposed: V-Sekai: Gateways to Virtual Worlds",
     "section": "",
-    "text": "Rancher does not directly support installing Helm charts from a Git repository. However, you can add the Git repository as a catalog in Rancher, and then use Rancher’s UI to deploy the chart.\nHere’s how you can do it:\n\nNavigate to the Rancher UI.\nGo to Global -&gt; Catalogs.\nClick on “Add Catalog”, fill in the details:\n\nName: Give your catalog a name.\nURL: Enter the URL of your Git repository (https://charts.bitnami.com/bitnami).\nBranch: Specify the branch to use (usually master or main).\n\nClick on “Create”.\nNow, you can navigate to your project, click on “Apps” -&gt; “Launch”, and you should see your newly added catalog. You can select the chart you want to install and follow the prompts."
+    "text": "The term “Virtual Worlds” might be too broad or vague for some people, potentially leading to misunderstandings about our specific services."
   },
   {
-    "objectID": "decisions/20240330-bitnami-rancher-helm-catalog.html#benefits",
-    "href": "decisions/20240330-bitnami-rancher-helm-catalog.html#benefits",
-    "title": "Proposed: Installing Helm Chart from a Git Repository using Rancher",
+    "objectID": "decisions/20231228-v-sekai-slogan.html#the-road-not-taken",
+    "href": "decisions/20231228-v-sekai-slogan.html#the-road-not-taken",
+    "title": "Proposed: V-Sekai: Gateways to Virtual Worlds",
     "section": "",
-    "text": "This method allows you to manage and deploy Helm charts directly from the Rancher UI, providing a more user-friendly way to handle deployments."
+    "text": "Alternative slogans were considered, such as “V-Sekai: Forging Gateways to Virtual Worlds”, but they didn’t convey our message as effectively."
   },
   {
-    "objectID": "decisions/20240330-bitnami-rancher-helm-catalog.html#downsides",
-    "href": "decisions/20240330-bitnami-rancher-helm-catalog.html#downsides",
-    "title": "Proposed: Installing Helm Chart from a Git Repository using Rancher",
+    "objectID": "decisions/20231228-v-sekai-slogan.html#the-infrequent-use-case",
+    "href": "decisions/20231228-v-sekai-slogan.html#the-infrequent-use-case",
+    "title": "Proposed: V-Sekai: Gateways to Virtual Worlds",
     "section": "",
-    "text": "The main downside is that this method requires manual setup in the Rancher UI, which might not be ideal for automated workflows."
+    "text": "For those unfamiliar with the concept of virtual reality, the slogan might require further explanation."
   },
   {
-    "objectID": "decisions/20240330-bitnami-rancher-helm-catalog.html#the-road-not-taken",
-    "href": "decisions/20240330-bitnami-rancher-helm-catalog.html#the-road-not-taken",
-    "title": "Proposed: Installing Helm Chart from a Git Repository using Rancher",
+    "objectID": "decisions/20231228-v-sekai-slogan.html#in-core-and-done-by-us",
+    "href": "decisions/20231228-v-sekai-slogan.html#in-core-and-done-by-us",
+    "title": "Proposed: V-Sekai: Gateways to Virtual Worlds",
     "section": "",
-    "text": "An alternative approach would be to clone the Git repository locally, package the chart into a .tgz file, and upload it directly to Rancher."
+    "text": "Yes, this proposal was created internally by the V-Sekai team with assistance from AI assistant Aria."
   },
   {
-    "objectID": "decisions/20240330-bitnami-rancher-helm-catalog.html#infrequent-use-case",
-    "href": "decisions/20240330-bitnami-rancher-helm-catalog.html#infrequent-use-case",
-    "title": "Proposed: Installing Helm Chart from a Git Repository using Rancher",
+    "objectID": "decisions/20231228-v-sekai-slogan.html#further-reading",
+    "href": "decisions/20231228-v-sekai-slogan.html#further-reading",
+    "title": "Proposed: V-Sekai: Gateways to Virtual Worlds",
     "section": "",
-    "text": "This approach is particularly useful when you want to manage your Helm charts and deployments through a user-friendly interface, rather than dealing with command-line tools."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\nVket 2023: Tram Ride\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240330-bitnami-rancher-helm-catalog.html#in-core-and-done-by-us",
-    "href": "decisions/20240330-bitnami-rancher-helm-catalog.html#in-core-and-done-by-us",
-    "title": "Proposed: Installing Helm Chart from a Git Repository using Rancher",
+    "objectID": "decisions/20211005-test-google-mediapipe.html",
+    "href": "decisions/20211005-test-google-mediapipe.html",
+    "title": "Proposed: Test Google Mediapipe",
     "section": "",
-    "text": "This solution is based on the core functionality provided by Rancher and does not require any additional tools or services."
+    "text": "We’re unable to test media pipe for iris.\n\n\n\nSetup github actions so we can package mediapipe to demo iris tracking.\n\n\n\n\nsetup cicd for linux to media pipe\nsetup cid for media pipe iris tracking\ncreate win10 support\n\n\n\nsudo apt install v4l-utils -y\nv4l2-ctl --all\n\n\n\nsudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade\ngit clone https://github.com/IntelRealSense/librealsense.git\ncd librealsense\nsudo apt-get install git libssl-dev libusb-1.0-0-dev pkg-config libgtk-3-dev -y\nsudo apt-get install libglfw3-dev libgl1-mesa-dev libglu1-mesa-dev -y\n./scripts/setup_udev_rules.sh\n# Use Postos 21.04 NVIDIA\nmkdir build && cd build\ncmake ../ -DBUILD_EXAMPLES=true -DCMAKE_BUILD_TYPE=Release\nsudo make uninstall && make clean && make && sudo make install -j`nproc`"
   },
   {
-    "objectID": "decisions/20240330-bitnami-rancher-helm-catalog.html#status",
-    "href": "decisions/20240330-bitnami-rancher-helm-catalog.html#status",
-    "title": "Proposed: Installing Helm Chart from a Git Repository using Rancher",
+    "objectID": "decisions/20211005-test-google-mediapipe.html#context-and-problem-statement",
+    "href": "decisions/20211005-test-google-mediapipe.html#context-and-problem-statement",
+    "title": "Proposed: Test Google Mediapipe",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "We’re unable to test media pipe for iris."
   },
   {
-    "objectID": "decisions/20240330-bitnami-rancher-helm-catalog.html#decision-makers",
-    "href": "decisions/20240330-bitnami-rancher-helm-catalog.html#decision-makers",
-    "title": "Proposed: Installing Helm Chart from a Git Repository using Rancher",
+    "objectID": "decisions/20211005-test-google-mediapipe.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20211005-test-google-mediapipe.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: Test Google Mediapipe",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "Setup github actions so we can package mediapipe to demo iris tracking."
   },
   {
-    "objectID": "decisions/20240330-bitnami-rancher-helm-catalog.html#tags",
-    "href": "decisions/20240330-bitnami-rancher-helm-catalog.html#tags",
-    "title": "Proposed: Installing Helm Chart from a Git Repository using Rancher",
+    "objectID": "decisions/20211005-test-google-mediapipe.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20211005-test-google-mediapipe.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Test Google Mediapipe",
     "section": "",
-    "text": "V-Sekai"
+    "text": "setup cicd for linux to media pipe\nsetup cid for media pipe iris tracking\ncreate win10 support\n\n\n\nsudo apt install v4l-utils -y\nv4l2-ctl --all\n\n\n\nsudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade\ngit clone https://github.com/IntelRealSense/librealsense.git\ncd librealsense\nsudo apt-get install git libssl-dev libusb-1.0-0-dev pkg-config libgtk-3-dev -y\nsudo apt-get install libglfw3-dev libgl1-mesa-dev libglu1-mesa-dev -y\n./scripts/setup_udev_rules.sh\n# Use Postos 21.04 NVIDIA\nmkdir build && cd build\ncmake ../ -DBUILD_EXAMPLES=true -DCMAKE_BUILD_TYPE=Release\nsudo make uninstall && make clean && make && sudo make install -j`nproc`"
   },
   {
-    "objectID": "decisions/20240330-bitnami-rancher-helm-catalog.html#further-reading",
-    "href": "decisions/20240330-bitnami-rancher-helm-catalog.html#further-reading",
-    "title": "Proposed: Installing Helm Chart from a Git Repository using Rancher",
-    "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\nbitnami/charts\n\nThis article was assisted by Aria, your AI assistant."
+    "objectID": "decisions/20211005-test-google-mediapipe.html#positive-consequences",
+    "href": "decisions/20211005-test-google-mediapipe.html#positive-consequences",
+    "title": "Proposed: Test Google Mediapipe",
+    "section": "Positive Consequences ",
+    "text": "Positive Consequences \nAble to mocap faces.\nAble to use the human body as vr controllers."
   },
   {
-    "objectID": "decisions/20240621-caption-photos-for-cicd.html",
-    "href": "decisions/20240621-caption-photos-for-cicd.html",
-    "title": "Proposed: Image Captioning Tool",
-    "section": "",
-    "text": "In the V-Sekai project, we are developing a continuous integration and continuous delivery (CI/CD) tool for Meta Platform Inc.’s Virtual Reality OpenXR API headset simulator (Windows 11). A key feature of this tool is the ability to caption images.\n\n\n\nWe need to caption images for two main reasons:\n\nDebugging: Developers can quickly identify issues by reading the captions.\nDataset Creation: We can create a nominal vs anomaly dataset for visual anomaly detection.\n\n\n\n\nHere’s a Python script that uses the Gradio client to generate captions for images:\n# Copyright (c) 2019-2022 K. S. Ernest (iFire) Lee (fire)\n# SPDX-License-Identifier: MIT\n# pip3 install gradio_client\nfrom gradio_client import Client, handle_file\n\nfile_or_url_paths = [\"//192.168.1.72/share/Screenshot 2024-05-22 at 6.05.58 PM.png\"]\nclient = Client(\"gokaygokay/PaliGemma-PixelProse\")\n\nfor path in file_or_url_paths:\n    try:\n        result = client.predict(\n            image=handle_file(path),\n            api_name=\"/create_captions_rich\"\n        )\n        print(result)\n    except Exception as e:\n        print(f\"An error occurred while processing {path}: {e}\")\n\n\n\n\nImproved debugging process.\nFacilitates the creation of a dataset for visual anomaly detection.\n\n\n\n\n\nThe accuracy of the captions depends on the performance of the Gradio client.\n\n\n\n\n\nWe could have used other image captioning tools or libraries, but we chose Gradio due to its simplicity and ease of use.\n\n\n\n\n\nThis tool may not be useful when working with non-visual data or when debugging is not required.\n\n\n\n\n\nThis feature will be developed and maintained by the V-Sekai development team.\n\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - The GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n[https://github.com/V-Sekai-fire/character-rigging-anomaly-detection]\n[https://anomalib.readthedocs.io/en/v1.1.0/]\n[https://developer.oculus.com/documentation/native/xrsim-intro/]\n[https://github.com/V-Sekai-fire/cog-caption-image.git]\n[https://huggingface.co/spaces/gokaygokay/Florence-2]\n\nThis proposal was assisted by Aria, an AI assistant."
+    "objectID": "decisions/20211005-test-google-mediapipe.html#negative-consequences",
+    "href": "decisions/20211005-test-google-mediapipe.html#negative-consequences",
+    "title": "Proposed: Test Google Mediapipe",
+    "section": "Negative Consequences ",
+    "text": "Negative Consequences \nNo response"
   },
   {
-    "objectID": "decisions/20240621-caption-photos-for-cicd.html#context",
-    "href": "decisions/20240621-caption-photos-for-cicd.html#context",
-    "title": "Proposed: Image Captioning Tool",
-    "section": "",
-    "text": "In the V-Sekai project, we are developing a continuous integration and continuous delivery (CI/CD) tool for Meta Platform Inc.’s Virtual Reality OpenXR API headset simulator (Windows 11). A key feature of this tool is the ability to caption images."
+    "objectID": "decisions/20211005-test-google-mediapipe.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20211005-test-google-mediapipe.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Test Google Mediapipe",
+    "section": "If this enhancement will not be used often, can it be worked around with a few lines of script?",
+    "text": "If this enhancement will not be used often, can it be worked around with a few lines of script?\nPose estimation is interesting and we have someone who wants to collaborate."
   },
   {
-    "objectID": "decisions/20240621-caption-photos-for-cicd.html#problem-statement",
-    "href": "decisions/20240621-caption-photos-for-cicd.html#problem-statement",
-    "title": "Proposed: Image Captioning Tool",
-    "section": "",
-    "text": "We need to caption images for two main reasons:\n\nDebugging: Developers can quickly identify issues by reading the captions.\nDataset Creation: We can create a nominal vs anomaly dataset for visual anomaly detection."
+    "objectID": "decisions/20211005-test-google-mediapipe.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20211005-test-google-mediapipe.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Test Google Mediapipe",
+    "section": "Is there a reason why this should be core and done by us?",
+    "text": "Is there a reason why this should be core and done by us?\nNo response"
   },
   {
-    "objectID": "decisions/20240621-caption-photos-for-cicd.html#proposal",
-    "href": "decisions/20240621-caption-photos-for-cicd.html#proposal",
-    "title": "Proposed: Image Captioning Tool",
-    "section": "",
-    "text": "Here’s a Python script that uses the Gradio client to generate captions for images:\n# Copyright (c) 2019-2022 K. S. Ernest (iFire) Lee (fire)\n# SPDX-License-Identifier: MIT\n# pip3 install gradio_client\nfrom gradio_client import Client, handle_file\n\nfile_or_url_paths = [\"//192.168.1.72/share/Screenshot 2024-05-22 at 6.05.58 PM.png\"]\nclient = Client(\"gokaygokay/PaliGemma-PixelProse\")\n\nfor path in file_or_url_paths:\n    try:\n        result = client.predict(\n            image=handle_file(path),\n            api_name=\"/create_captions_rich\"\n        )\n        print(result)\n    except Exception as e:\n        print(f\"An error occurred while processing {path}: {e}\")"
+    "objectID": "decisions/20211005-test-google-mediapipe.html#references",
+    "href": "decisions/20211005-test-google-mediapipe.html#references",
+    "title": "Proposed: Test Google Mediapipe",
+    "section": "References ",
+    "text": "References \n\nhttps://google.github.io/mediapipe/getting_started/hello_world_cpp.html\nhttps://google.github.io/mediapipe/getting_started/cpp.html\nhttps://google.github.io/mediapipe/solutions/iris.html\nhttps://github.com/google/mediapipe/issues/1530\nhttps://github.com/V-Sekai/mediapipe"
   },
   {
-    "objectID": "decisions/20240621-caption-photos-for-cicd.html#benefits",
-    "href": "decisions/20240621-caption-photos-for-cicd.html#benefits",
-    "title": "Proposed: Image Captioning Tool",
-    "section": "",
-    "text": "Improved debugging process.\nFacilitates the creation of a dataset for visual anomaly detection."
+    "objectID": "decisions/20211005-test-google-mediapipe.html#derivative-license",
+    "href": "decisions/20211005-test-google-mediapipe.html#derivative-license",
+    "title": "Proposed: Test Google Mediapipe",
+    "section": "Derivative License",
+    "text": "Derivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240621-caption-photos-for-cicd.html#downsides",
-    "href": "decisions/20240621-caption-photos-for-cicd.html#downsides",
-    "title": "Proposed: Image Captioning Tool",
+    "objectID": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html",
+    "href": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html",
+    "title": "Proposed: Reduce Size Difference Between Capsules and Mesh Volume",
     "section": "",
-    "text": "The accuracy of the captions depends on the performance of the Gradio client."
+    "text": "Accurately fit capsules around bones in skinned skeleton meshes. The example provided involves a rectangle skinned by two bones, with each vertex influenced by up to 8 weights.\n\n\n\nThe goal is to minimize the size discrepancies between the capsules surrounding the bones and the actual volume defined by the skin mesh. This will be approached using the Minimum Deviation Flow problem in bidirected graphs (Bi-MDF).\n\n\n\n\n\n\nSkeleton: Represent each bone as a node in a graph.\nSkin Mesh: Each vertex of the mesh is also a node. Connect a bone to a vertex with an edge if the vertex is influenced by that bone, based on skin weights.\n\n\n\n\n\nThe objective is to minimize the size differences between the capsules (nodes) and the volume of the skin mesh. This is quantified using a cost function that measures the deviation from ideal capsule sizes.\n\n\n\n\nI have no idea.\n\n\n\n\n\nAccuracy: Improves the fit of capsules to the actual mesh, enhancing animation quality.\nEfficiency: Reduces computational overhead by focusing on significant discrepancies.\n\n\n\n\n\nComplexity: Implementing and tuning the Bi-MDF algorithm can be complex.\nDependency: Relies heavily on accurate weight assignments and initial conditions.\n\n\n\n\n\nAlternative methods such as direct geometric fitting or machine learning approaches were considered but not pursued due to their complexity and computational requirements.\n\n\n\n\n\nHandling cases where bones have minimal influence on any vertices, which might lead to underutilized algorithms and resources.\n\n\n\n\n\nThe development and integration of this feature are handled internally by the V-Sekai development team, ensuring it aligns with the core functionalities of the Godot Engine used for VR.\n\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\ncgg-bern/libSatsuma Exact and approximate solvers for minimum-cost-flow problems in bi-directed graphs.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240621-caption-photos-for-cicd.html#road-not-taken",
-    "href": "decisions/20240621-caption-photos-for-cicd.html#road-not-taken",
-    "title": "Proposed: Image Captioning Tool",
+    "objectID": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#the-context",
+    "href": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#the-context",
+    "title": "Proposed: Reduce Size Difference Between Capsules and Mesh Volume",
     "section": "",
-    "text": "We could have used other image captioning tools or libraries, but we chose Gradio due to its simplicity and ease of use."
+    "text": "Accurately fit capsules around bones in skinned skeleton meshes. The example provided involves a rectangle skinned by two bones, with each vertex influenced by up to 8 weights."
   },
   {
-    "objectID": "decisions/20240621-caption-photos-for-cicd.html#infrequent-use-case",
-    "href": "decisions/20240621-caption-photos-for-cicd.html#infrequent-use-case",
-    "title": "Proposed: Image Captioning Tool",
+    "objectID": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#the-problem-statement",
+    "href": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#the-problem-statement",
+    "title": "Proposed: Reduce Size Difference Between Capsules and Mesh Volume",
     "section": "",
-    "text": "This tool may not be useful when working with non-visual data or when debugging is not required."
+    "text": "The goal is to minimize the size discrepancies between the capsules surrounding the bones and the actual volume defined by the skin mesh. This will be approached using the Minimum Deviation Flow problem in bidirected graphs (Bi-MDF)."
   },
   {
-    "objectID": "decisions/20240621-caption-photos-for-cicd.html#in-core-and-done-by-us",
-    "href": "decisions/20240621-caption-photos-for-cicd.html#in-core-and-done-by-us",
-    "title": "Proposed: Image Captioning Tool",
+    "objectID": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Reduce Size Difference Between Capsules and Mesh Volume",
     "section": "",
-    "text": "This feature will be developed and maintained by the V-Sekai development team."
+    "text": "Skeleton: Represent each bone as a node in a graph.\nSkin Mesh: Each vertex of the mesh is also a node. Connect a bone to a vertex with an edge if the vertex is influenced by that bone, based on skin weights.\n\n\n\n\n\nThe objective is to minimize the size differences between the capsules (nodes) and the volume of the skin mesh. This is quantified using a cost function that measures the deviation from ideal capsule sizes.\n\n\n\n\nI have no idea."
   },
   {
-    "objectID": "decisions/20240621-caption-photos-for-cicd.html#status",
-    "href": "decisions/20240621-caption-photos-for-cicd.html#status",
-    "title": "Proposed: Image Captioning Tool",
+    "objectID": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#the-benefits",
+    "href": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#the-benefits",
+    "title": "Proposed: Reduce Size Difference Between Capsules and Mesh Volume",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "Accuracy: Improves the fit of capsules to the actual mesh, enhancing animation quality.\nEfficiency: Reduces computational overhead by focusing on significant discrepancies."
   },
   {
-    "objectID": "decisions/20240621-caption-photos-for-cicd.html#decision-makers",
-    "href": "decisions/20240621-caption-photos-for-cicd.html#decision-makers",
-    "title": "Proposed: Image Captioning Tool",
+    "objectID": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#the-downsides",
+    "href": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#the-downsides",
+    "title": "Proposed: Reduce Size Difference Between Capsules and Mesh Volume",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "Complexity: Implementing and tuning the Bi-MDF algorithm can be complex.\nDependency: Relies heavily on accurate weight assignments and initial conditions."
   },
   {
-    "objectID": "decisions/20240621-caption-photos-for-cicd.html#tags",
-    "href": "decisions/20240621-caption-photos-for-cicd.html#tags",
-    "title": "Proposed: Image Captioning Tool",
+    "objectID": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#the-road-not-taken",
+    "href": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#the-road-not-taken",
+    "title": "Proposed: Reduce Size Difference Between Capsules and Mesh Volume",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Alternative methods such as direct geometric fitting or machine learning approaches were considered but not pursued due to their complexity and computational requirements."
   },
   {
-    "objectID": "decisions/20240621-caption-photos-for-cicd.html#further-reading",
-    "href": "decisions/20240621-caption-photos-for-cicd.html#further-reading",
-    "title": "Proposed: Image Captioning Tool",
+    "objectID": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#the-infrequent-use-case",
+    "href": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#the-infrequent-use-case",
+    "title": "Proposed: Reduce Size Difference Between Capsules and Mesh Volume",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - The GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n[https://github.com/V-Sekai-fire/character-rigging-anomaly-detection]\n[https://anomalib.readthedocs.io/en/v1.1.0/]\n[https://developer.oculus.com/documentation/native/xrsim-intro/]\n[https://github.com/V-Sekai-fire/cog-caption-image.git]\n[https://huggingface.co/spaces/gokaygokay/Florence-2]\n\nThis proposal was assisted by Aria, an AI assistant."
+    "text": "Handling cases where bones have minimal influence on any vertices, which might lead to underutilized algorithms and resources."
   },
   {
-    "objectID": "decisions/20240706-motion-capture-bill-of-materials.html",
-    "href": "decisions/20240706-motion-capture-bill-of-materials.html",
-    "title": "Proposed: Maximum Streaming Bill of Materials Setup for Motion Capture",
+    "objectID": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#in-core-and-done-by-us",
+    "href": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#in-core-and-done-by-us",
+    "title": "Proposed: Reduce Size Difference Between Capsules and Mesh Volume",
     "section": "",
-    "text": "In the realm of virtual reality (VR) and motion capture, having a comprehensive setup is crucial for achieving high-quality streaming and accurate motion tracking. This proposal outlines the maximum bill of materials required to set up an advanced motion capture system for VR streaming.\n\n\n\nDescribe a streaming bill of materials setup for motion capture.\n\n\n\n\n\n\n\n\n\n\n\n\nComponent\nModel/Specification\nQuantity\nDescription\n\n\n\n\nVR Headset\nHTCVive XR Elite\n1\nHigh-resolution VR headset\n\n\nControllers\nHTCVive XR Elite Controllers\n2\nHandheld motion controllers\n\n\nMotion Trackers\nVIVE Ultimate Trackers\n5\nTrackers for motion capture\n\n\nFacial Tracker\nVIVE Full Facial Tracker\n1\nTracker for capturing facial movements\n\n\nStreaming PC\nSteamVR Capable Wireless Streaming PC with RTX 4080\n1\nPC with RTX 4080 GPU capable of wireless streaming for SteamVR\n\n\nWiFi Router\nHigh-speed WiFi Router with Internet\n1\nRouter for wireless internet connectivity\n\n\nUSB-C Cable\n5m USB-C Cable from UGreen\n1\nCable for data transfer\n\n\nCharging Cable\nUSB-C to USB-C Charging Cable\n3\nCable for charging devices\n\n\nCharging Cable\nUSB-C to USB-A Charging Cable\n1\nCable for charging devices\n\n\nChest Strap\nEOZ VRChat Chest Strap\n1\nChest strap for VRChat\n\n\nPelvis Belt\nTrackStrap Pelvis Belt (VIVE Ultimate Tracker Edition)\n1\nPelvis belt for motion tracking\n\n\nFoot Straps\nEOZ VRChat Strap Version 2 (Left and Right)\n2\nFoot straps for VRChat\n\n\nTracker Dongle\nHTCVive Ultimate Tracker Dongle\n1\nDongle for connecting trackers\n\n\n\n\n\n\n\nHigh-Quality Streaming: The setup ensures high-resolution streaming with minimal latency.\nAccurate Motion Capture: Multiple trackers provide precise motion capture for various body parts.\nEnhanced User Experience: The combination of facial and motion trackers offers a more immersive VR experience.\n\n\n\n\n\nCost: The setup involves high-end components, which can be expensive.\nComplexity: Setting up and maintaining the system requires technical expertise.\nSpace Requirements: Adequate space is needed to use the motion capture system effectively.\n\n\n\n\nAlternative solutions such as using lower-end VR headsets or fewer motion trackers were considered but not chosen due to their limitations in providing high-quality streaming and accurate motion capture.\n\n\n\nInfrequent use cases include scenarios where only basic motion capture is needed, such as simple VR interactions without the need for full-body tracking or high-resolution streaming.\n\n\n\nThe V-Sekai development team will handle the integration and setup of the proposed components into the core system.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\nFire\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "The development and integration of this feature are handled internally by the V-Sekai development team, ensuring it aligns with the core functionalities of the Godot Engine used for VR."
   },
   {
-    "objectID": "decisions/20240706-motion-capture-bill-of-materials.html#the-context",
-    "href": "decisions/20240706-motion-capture-bill-of-materials.html#the-context",
-    "title": "Proposed: Maximum Streaming Bill of Materials Setup for Motion Capture",
+    "objectID": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#status",
+    "href": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#status",
+    "title": "Proposed: Reduce Size Difference Between Capsules and Mesh Volume",
     "section": "",
-    "text": "In the realm of virtual reality (VR) and motion capture, having a comprehensive setup is crucial for achieving high-quality streaming and accurate motion tracking. This proposal outlines the maximum bill of materials required to set up an advanced motion capture system for VR streaming."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20240706-motion-capture-bill-of-materials.html#the-problem-statement",
-    "href": "decisions/20240706-motion-capture-bill-of-materials.html#the-problem-statement",
-    "title": "Proposed: Maximum Streaming Bill of Materials Setup for Motion Capture",
+    "objectID": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#decision-makers",
+    "href": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#decision-makers",
+    "title": "Proposed: Reduce Size Difference Between Capsules and Mesh Volume",
     "section": "",
-    "text": "Describe a streaming bill of materials setup for motion capture."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20240706-motion-capture-bill-of-materials.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240706-motion-capture-bill-of-materials.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Maximum Streaming Bill of Materials Setup for Motion Capture",
+    "objectID": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#tags",
+    "href": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#tags",
+    "title": "Proposed: Reduce Size Difference Between Capsules and Mesh Volume",
     "section": "",
-    "text": "Component\nModel/Specification\nQuantity\nDescription\n\n\n\n\nVR Headset\nHTCVive XR Elite\n1\nHigh-resolution VR headset\n\n\nControllers\nHTCVive XR Elite Controllers\n2\nHandheld motion controllers\n\n\nMotion Trackers\nVIVE Ultimate Trackers\n5\nTrackers for motion capture\n\n\nFacial Tracker\nVIVE Full Facial Tracker\n1\nTracker for capturing facial movements\n\n\nStreaming PC\nSteamVR Capable Wireless Streaming PC with RTX 4080\n1\nPC with RTX 4080 GPU capable of wireless streaming for SteamVR\n\n\nWiFi Router\nHigh-speed WiFi Router with Internet\n1\nRouter for wireless internet connectivity\n\n\nUSB-C Cable\n5m USB-C Cable from UGreen\n1\nCable for data transfer\n\n\nCharging Cable\nUSB-C to USB-C Charging Cable\n3\nCable for charging devices\n\n\nCharging Cable\nUSB-C to USB-A Charging Cable\n1\nCable for charging devices\n\n\nChest Strap\nEOZ VRChat Chest Strap\n1\nChest strap for VRChat\n\n\nPelvis Belt\nTrackStrap Pelvis Belt (VIVE Ultimate Tracker Edition)\n1\nPelvis belt for motion tracking\n\n\nFoot Straps\nEOZ VRChat Strap Version 2 (Left and Right)\n2\nFoot straps for VRChat\n\n\nTracker Dongle\nHTCVive Ultimate Tracker Dongle\n1\nDongle for connecting trackers"
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20240706-motion-capture-bill-of-materials.html#the-benefits",
-    "href": "decisions/20240706-motion-capture-bill-of-materials.html#the-benefits",
-    "title": "Proposed: Maximum Streaming Bill of Materials Setup for Motion Capture",
+    "objectID": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#further-reading",
+    "href": "decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html#further-reading",
+    "title": "Proposed: Reduce Size Difference Between Capsules and Mesh Volume",
     "section": "",
-    "text": "High-Quality Streaming: The setup ensures high-resolution streaming with minimal latency.\nAccurate Motion Capture: Multiple trackers provide precise motion capture for various body parts.\nEnhanced User Experience: The combination of facial and motion trackers offers a more immersive VR experience."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\ncgg-bern/libSatsuma Exact and approximate solvers for minimum-cost-flow problems in bi-directed graphs.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240706-motion-capture-bill-of-materials.html#the-downsides",
-    "href": "decisions/20240706-motion-capture-bill-of-materials.html#the-downsides",
-    "title": "Proposed: Maximum Streaming Bill of Materials Setup for Motion Capture",
+    "objectID": "decisions/20220206-logging-notifications-from-discord.html",
+    "href": "decisions/20220206-logging-notifications-from-discord.html",
+    "title": "Proposed: Log change notifications using DiscordChatExporter",
     "section": "",
-    "text": "Cost: The setup involves high-end components, which can be expensive.\nComplexity: Setting up and maintaining the system requires technical expertise.\nSpace Requirements: Adequate space is needed to use the motion capture system effectively."
+    "text": "Status: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nWe use discord to log changes. At any moment, Discord can disappear.\n\n\n\nUse DiscordChatExporter to export our change notifications.\n\n\n\n\ngenerate a bot key\nenter key\nselect channels to write to\nexport while being careful to be in utc.\n\n\n\n\n\nLogs can be created for notifications.\n\n\n\n\n\nNeed to avoid Discord selfbots\n\n\n\n\n\nOption: Current status.\nRejection Reason: Discord servers can be arbitrarily lost.\n\n\n\n\nNot a trivial amount of coding to log into Discord.\n\n\n\nWe are the ones designing and using Discord.\n\n\n\n\nDiscordChatExporter \n\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240706-motion-capture-bill-of-materials.html#the-road-not-taken",
-    "href": "decisions/20240706-motion-capture-bill-of-materials.html#the-road-not-taken",
-    "title": "Proposed: Maximum Streaming Bill of Materials Setup for Motion Capture",
+    "objectID": "decisions/20220206-logging-notifications-from-discord.html#context-and-problem-statement",
+    "href": "decisions/20220206-logging-notifications-from-discord.html#context-and-problem-statement",
+    "title": "Proposed: Log change notifications using DiscordChatExporter",
     "section": "",
-    "text": "Alternative solutions such as using lower-end VR headsets or fewer motion trackers were considered but not chosen due to their limitations in providing high-quality streaming and accurate motion capture."
+    "text": "We use discord to log changes. At any moment, Discord can disappear."
   },
   {
-    "objectID": "decisions/20240706-motion-capture-bill-of-materials.html#the-infrequent-use-case",
-    "href": "decisions/20240706-motion-capture-bill-of-materials.html#the-infrequent-use-case",
-    "title": "Proposed: Maximum Streaming Bill of Materials Setup for Motion Capture",
+    "objectID": "decisions/20220206-logging-notifications-from-discord.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20220206-logging-notifications-from-discord.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: Log change notifications using DiscordChatExporter",
     "section": "",
-    "text": "Infrequent use cases include scenarios where only basic motion capture is needed, such as simple VR interactions without the need for full-body tracking or high-resolution streaming."
+    "text": "Use DiscordChatExporter to export our change notifications."
   },
   {
-    "objectID": "decisions/20240706-motion-capture-bill-of-materials.html#in-core-and-done-by-us",
-    "href": "decisions/20240706-motion-capture-bill-of-materials.html#in-core-and-done-by-us",
-    "title": "Proposed: Maximum Streaming Bill of Materials Setup for Motion Capture",
+    "objectID": "decisions/20220206-logging-notifications-from-discord.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20220206-logging-notifications-from-discord.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Log change notifications using DiscordChatExporter",
     "section": "",
-    "text": "The V-Sekai development team will handle the integration and setup of the proposed components into the core system."
+    "text": "generate a bot key\nenter key\nselect channels to write to\nexport while being careful to be in utc."
   },
   {
-    "objectID": "decisions/20240706-motion-capture-bill-of-materials.html#status",
-    "href": "decisions/20240706-motion-capture-bill-of-materials.html#status",
-    "title": "Proposed: Maximum Streaming Bill of Materials Setup for Motion Capture",
+    "objectID": "decisions/20220206-logging-notifications-from-discord.html#positive-consequences",
+    "href": "decisions/20220206-logging-notifications-from-discord.html#positive-consequences",
+    "title": "Proposed: Log change notifications using DiscordChatExporter",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "Logs can be created for notifications."
   },
   {
-    "objectID": "decisions/20240706-motion-capture-bill-of-materials.html#decision-makers",
-    "href": "decisions/20240706-motion-capture-bill-of-materials.html#decision-makers",
-    "title": "Proposed: Maximum Streaming Bill of Materials Setup for Motion Capture",
+    "objectID": "decisions/20220206-logging-notifications-from-discord.html#negative-consequences",
+    "href": "decisions/20220206-logging-notifications-from-discord.html#negative-consequences",
+    "title": "Proposed: Log change notifications using DiscordChatExporter",
     "section": "",
-    "text": "V-Sekai development team\nFire"
+    "text": "Need to avoid Discord selfbots"
   },
   {
-    "objectID": "decisions/20240706-motion-capture-bill-of-materials.html#tags",
-    "href": "decisions/20240706-motion-capture-bill-of-materials.html#tags",
-    "title": "Proposed: Maximum Streaming Bill of Materials Setup for Motion Capture",
+    "objectID": "decisions/20220206-logging-notifications-from-discord.html#option-graveyard",
+    "href": "decisions/20220206-logging-notifications-from-discord.html#option-graveyard",
+    "title": "Proposed: Log change notifications using DiscordChatExporter",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Option: Current status.\nRejection Reason: Discord servers can be arbitrarily lost."
   },
   {
-    "objectID": "decisions/20240706-motion-capture-bill-of-materials.html#further-reading",
-    "href": "decisions/20240706-motion-capture-bill-of-materials.html#further-reading",
-    "title": "Proposed: Maximum Streaming Bill of Materials Setup for Motion Capture",
+    "objectID": "decisions/20220206-logging-notifications-from-discord.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20220206-logging-notifications-from-discord.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Log change notifications using DiscordChatExporter",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "Not a trivial amount of coding to log into Discord."
   },
   {
-    "objectID": "decisions/20240622-gocd-agent-docker-image-update.html",
-    "href": "decisions/20240622-gocd-agent-docker-image-update.html",
-    "title": "Accepted: GoCD Agent Docker Image Update",
+    "objectID": "decisions/20220206-logging-notifications-from-discord.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20220206-logging-notifications-from-discord.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Log change notifications using DiscordChatExporter",
     "section": "",
-    "text": "We are currently using a GoCD Agent Docker image for our V-Sekai development environment. This Docker image contains all the necessary tools and libraries required for building our projects.\n\n\n\nThe GoCD Agent Docker image we are using is not up-to-date, which could potentially lead to compatibility issues, security vulnerabilities, and missed improvements from newer versions of the tools and libraries.\n\n\n\nWe propose to update all components within the GoCD Agent Docker image. This includes the base OS, installed libraries, and any other software included in the image.\n\n\n\nUpdating the GoCD Agent Docker image ensures that we are using the most recent and secure versions of our tools and libraries. It also allows us to take advantage of any new features or performance improvements that have been introduced.\n\n\n\nThere may be breaking changes in the newer versions of the tools and libraries, which could require modifications to our existing codebase.\n\n\n\nWe could choose not to update the GoCD Agent Docker image, but this could leave us vulnerable to known security issues and prevent us from utilizing improvements in the tools and libraries.\n\n\n\nThis proposal does not directly address infrequent use cases, as it is focused on maintaining an up-to-date development environment.\n\n\n\nThe updating process will be handled by the V-Sekai development team.\n\n\n\nStatus: Accepted \n\n\n\n\nV-Sekai development team\nfire\nlyuma\n\n\n\n\n\nV-Sekai\nDocker\nGoCD Agent\nUpdate\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "We are the ones designing and using Discord."
   },
   {
-    "objectID": "decisions/20240622-gocd-agent-docker-image-update.html#the-context",
-    "href": "decisions/20240622-gocd-agent-docker-image-update.html#the-context",
-    "title": "Accepted: GoCD Agent Docker Image Update",
+    "objectID": "decisions/20220206-logging-notifications-from-discord.html#references",
+    "href": "decisions/20220206-logging-notifications-from-discord.html#references",
+    "title": "Proposed: Log change notifications using DiscordChatExporter",
     "section": "",
-    "text": "We are currently using a GoCD Agent Docker image for our V-Sekai development environment. This Docker image contains all the necessary tools and libraries required for building our projects."
+    "text": "DiscordChatExporter"
   },
   {
-    "objectID": "decisions/20240622-gocd-agent-docker-image-update.html#the-problem-statement",
-    "href": "decisions/20240622-gocd-agent-docker-image-update.html#the-problem-statement",
-    "title": "Accepted: GoCD Agent Docker Image Update",
+    "objectID": "decisions/20220206-logging-notifications-from-discord.html#derivative-license",
+    "href": "decisions/20220206-logging-notifications-from-discord.html#derivative-license",
+    "title": "Proposed: Log change notifications using DiscordChatExporter",
     "section": "",
-    "text": "The GoCD Agent Docker image we are using is not up-to-date, which could potentially lead to compatibility issues, security vulnerabilities, and missed improvements from newer versions of the tools and libraries."
+    "text": "Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240622-gocd-agent-docker-image-update.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240622-gocd-agent-docker-image-update.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Accepted: GoCD Agent Docker Image Update",
+    "objectID": "decisions/20200729-entity-networking.html",
+    "href": "decisions/20200729-entity-networking.html",
+    "title": "Accepted: Adding Entity Networking to Groups",
     "section": "",
-    "text": "We propose to update all components within the GoCD Agent Docker image. This includes the base OS, installed libraries, and any other software included in the image."
+    "text": "Status: accepted\nDeciders: V-Sekai,Lyuma,SaracenOne\n\n\n\nFor Groups, this system aims to solve the following issues:\n\n(A) Need a way to standardize scene spawning.\n(B) Need a way to refer to nodes/instances that is consistent across clients (for example, “Set parent to …”).\n(C) Need a way to synchronize state between clients.\n(D) Provides a basic set of standard protocols and interactions.\n(E) Provides the basis for a security/privacy model regarding entity communication/permissions over the network.\n(F) Provides a security model locally for access between nodes of one entity and nodes of another entity (assuming a secure scripting framework is implemented).\n(G) This also solves the problem of abstracting away implementation details of entities; for example, there should be no need to deal with Godot nodes on an individual basis.\n(H) Provide a unified way to create top-level physics hierarchies isolated from other game logic.\n\nNote: This proposal covers three Spawn Types:\n\nSpawn type (i) Entities integrated into a map;\nSpawn type (ii) map entities spawned by clients; and\nSpawn type (iii) avatar entities/props spawned by clients.)\n\n\n\n\nAs indicated in point (G), everything documented here relates to Scenes and Entities. Aside from the Entity script being attached to the root node of a scene(?), and the scene itself being a node. Additionally, it may be necessary to query a node to find its containing entity (parent node). Note: Interaction between nodes within a single entity is considered an implementation detail of that entity and is out of the scope of the entity system. Any security model assumes that nodes cannot be transferred, shared or reparented between entities.\nEntities are objects known to the server and with explicit handling for state synchronization.\nSome entities may choose to synchronize little state, or position only, or no state at all. Also, some entities may choose to provide no security or isolation, while others may be private and appear not to even exist to other nodes. For example, a local player menu built upon the Entity System’s interaction features, gaining features A, D, F and G. By building this common framework, it means that systems built as Entities can be trivially synchronized over the network.\n\n\n\nTodo: We may want a way to optimistically spawn an entity client-side to achieve maximal responsiveness and fun.\nHowever, these entities will not yet know their server-side entity ID. Proposals: Reserve portion of ID space; or locally hold onto events/state and flush once the ID is known.\n\n\nThere will be a global directory of spawnable objects as part of a server connection. Players and maps can reference scenes by some name to spawn an entity with that name.\n\n\n\nEntities will have a server-assigned ID. Todo: What to do if an entity is spawned locally and an ID is not yet known.\n\n\n\nEntities will define a set of state variables that must be synced. The network protocol will take care of updating the state gradually over time, as well as rate-limiting. Events can be used to provide forced updates. Guarantees? Exposing metadata about when the state was updated?\nEntity properties:\n\nState that is synced is properties.\nSome properties are only assignable at spawn time (for example, scene file?)\nSome properties such as transform may require special handling.\n\nUpdate intervals:\nEntity refreshing / full state synchronization & serialization:\nDelta encoding & ACK protocol:\nWhen to use reliable events vs. “unreliable” (eventual) state synchronization: Events as a means for state synchronization.\n\n\n\nTODO: What classes / bespoke types exist? Examples: Physics, Physics Pickup; Button; Movable Platform; Vehicle\n\n\n\nConcepts:\nOwnership:\nAll entities will be owned by the player who interacts with them or by the server.\nEntity ownership will be transferred if the current owner leaves.\nMastership:\nMap entities may largely be mastered by a dedicated server.\nAvatar entities and props will be mastered by the player that spawned them, even if another player owns them.\n(Example: Alice personally spawns a ball avatar prop and throws it to Bob, who catches it. Alice has Mastership; Bob has Ownership.)\nMastership may be transferred on map exit; or they may be despawned (the player “takes” their props with them.)\nPrivacy: Entities may reveal very little state to the network. Are there cases where different players may be given different permissions?\nExample: Cooperative game, in which state is shared between some players but not others.\nExample: Team Melee\n\n\n\nScript-level guarantees that information about other entities is either restricted or absent entirely.\nIt may require a custom scripting language to achieve these guarantees fully.\n\n\n\nNot much to say here. We should see as little as possible built on top of pure Godot Nodes, except as a means for providing the entity’s functions.\n\n\n\nEntities will not be allowed to contain physics objects within the node hierarchy. Instead, physics objects must be attached to the entity in specific ways.\nQuestions: how does this work with PhysicalBone; how are physics objects linked to the entity; what about animations? (scale, rotation, skeleton attachments driving physical bodies?)\n\n\n\nMaps will have entities that might not be spawnable but will be automatically created and referenced within the parent scene.\nFor example, a button/door; or a state “god object”; or physics objects; built-in TV screens.\n\n\n\nMaps will provide a directory of map-spawnable scene references, which can be instantiated in response to events.\nThese will usually have specific functions within a particular map.\nExamples: Game-specific weapons; Keys; Buildings constructed\n\n\n\nPlayers may also provide a directory of avatar-spawnable scenes; Additionally, a prop database may exist or be negotiated.\nThese may include local UIs; weapons, pencils; media players; pets (parrots, mounts); vehicles; flight mechanics (wings?); visual effects.\n\n\n\nNodePath references (../) out of an entity hierarchy must be disallowed. Parenting should be implemented carefully: If nodes are literally parented to another entity (e.g. vehicles), NodePath references could expose implementation details from one entity to another entity.\nPart of a solution to this is to provide Attachment points as a feature of an Entity, but this needs to be implemented carefully to prevent unusual situations, for example, parent entity/node is destroyed (queue_free()) or removed from the scene tree (remove_child()); or animation paths referencing a node of the child entity.\n\n\n\n\n\nPossibility of:\n\nvehicle games\nbow and arrow games\npickup of balls\n\n\n\n\n\n\nComplexity\n\n\n\n\nA networking system is not a few lines of code.\n\n\n\nYes, this is the foundation of the protocol and the basic set of nodes and behavior upon which content will be created.\n\n\n\nAldridge, David. “I Shot You First: networking the Gameplay of Halo: Reach”. GDC 2011. https://www.youtube.com/watch?v=h47zZrqjgLc\nFiedler, Glenn. “Networking for Physics Programmers”. GDC 2015. https://www.youtube.com/watch?v=Z9X4lysFr64\nFiedler, Glenn. “Networked Physics in Virtual Reality”. 2018-02-22. https://www.gafferongames.com/post/networked_physics_in_virtual_reality/\nRouwe, Jorrit. “Killzone Shadow Fall: Threading the Entity Update on PS4”. GDCEU 2014. https://archive.org/details/GDCEU2014Rouwe\nSaracen, text and voice discussions on Discord: search Discord for “entity networking” and “networking model”\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240622-gocd-agent-docker-image-update.html#the-benefits",
-    "href": "decisions/20240622-gocd-agent-docker-image-update.html#the-benefits",
-    "title": "Accepted: GoCD Agent Docker Image Update",
+    "objectID": "decisions/20200729-entity-networking.html#context-and-problem-statement",
+    "href": "decisions/20200729-entity-networking.html#context-and-problem-statement",
+    "title": "Accepted: Adding Entity Networking to Groups",
     "section": "",
-    "text": "Updating the GoCD Agent Docker image ensures that we are using the most recent and secure versions of our tools and libraries. It also allows us to take advantage of any new features or performance improvements that have been introduced."
+    "text": "For Groups, this system aims to solve the following issues:\n\n(A) Need a way to standardize scene spawning.\n(B) Need a way to refer to nodes/instances that is consistent across clients (for example, “Set parent to …”).\n(C) Need a way to synchronize state between clients.\n(D) Provides a basic set of standard protocols and interactions.\n(E) Provides the basis for a security/privacy model regarding entity communication/permissions over the network.\n(F) Provides a security model locally for access between nodes of one entity and nodes of another entity (assuming a secure scripting framework is implemented).\n(G) This also solves the problem of abstracting away implementation details of entities; for example, there should be no need to deal with Godot nodes on an individual basis.\n(H) Provide a unified way to create top-level physics hierarchies isolated from other game logic.\n\nNote: This proposal covers three Spawn Types:\n\nSpawn type (i) Entities integrated into a map;\nSpawn type (ii) map entities spawned by clients; and\nSpawn type (iii) avatar entities/props spawned by clients.)"
   },
   {
-    "objectID": "decisions/20240622-gocd-agent-docker-image-update.html#the-downsides",
-    "href": "decisions/20240622-gocd-agent-docker-image-update.html#the-downsides",
-    "title": "Accepted: GoCD Agent Docker Image Update",
+    "objectID": "decisions/20200729-entity-networking.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20200729-entity-networking.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Accepted: Adding Entity Networking to Groups",
     "section": "",
-    "text": "There may be breaking changes in the newer versions of the tools and libraries, which could require modifications to our existing codebase."
+    "text": "As indicated in point (G), everything documented here relates to Scenes and Entities. Aside from the Entity script being attached to the root node of a scene(?), and the scene itself being a node. Additionally, it may be necessary to query a node to find its containing entity (parent node). Note: Interaction between nodes within a single entity is considered an implementation detail of that entity and is out of the scope of the entity system. Any security model assumes that nodes cannot be transferred, shared or reparented between entities.\nEntities are objects known to the server and with explicit handling for state synchronization.\nSome entities may choose to synchronize little state, or position only, or no state at all. Also, some entities may choose to provide no security or isolation, while others may be private and appear not to even exist to other nodes. For example, a local player menu built upon the Entity System’s interaction features, gaining features A, D, F and G. By building this common framework, it means that systems built as Entities can be trivially synchronized over the network."
   },
   {
-    "objectID": "decisions/20240622-gocd-agent-docker-image-update.html#the-road-not-taken",
-    "href": "decisions/20240622-gocd-agent-docker-image-update.html#the-road-not-taken",
-    "title": "Accepted: GoCD Agent Docker Image Update",
+    "objectID": "decisions/20200729-entity-networking.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-andor-diagrams",
+    "href": "decisions/20200729-entity-networking.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-andor-diagrams",
+    "title": "Accepted: Adding Entity Networking to Groups",
     "section": "",
-    "text": "We could choose not to update the GoCD Agent Docker image, but this could leave us vulnerable to known security issues and prevent us from utilizing improvements in the tools and libraries."
+    "text": "Todo: We may want a way to optimistically spawn an entity client-side to achieve maximal responsiveness and fun.\nHowever, these entities will not yet know their server-side entity ID. Proposals: Reserve portion of ID space; or locally hold onto events/state and flush once the ID is known.\n\n\nThere will be a global directory of spawnable objects as part of a server connection. Players and maps can reference scenes by some name to spawn an entity with that name.\n\n\n\nEntities will have a server-assigned ID. Todo: What to do if an entity is spawned locally and an ID is not yet known.\n\n\n\nEntities will define a set of state variables that must be synced. The network protocol will take care of updating the state gradually over time, as well as rate-limiting. Events can be used to provide forced updates. Guarantees? Exposing metadata about when the state was updated?\nEntity properties:\n\nState that is synced is properties.\nSome properties are only assignable at spawn time (for example, scene file?)\nSome properties such as transform may require special handling.\n\nUpdate intervals:\nEntity refreshing / full state synchronization & serialization:\nDelta encoding & ACK protocol:\nWhen to use reliable events vs. “unreliable” (eventual) state synchronization: Events as a means for state synchronization.\n\n\n\nTODO: What classes / bespoke types exist? Examples: Physics, Physics Pickup; Button; Movable Platform; Vehicle\n\n\n\nConcepts:\nOwnership:\nAll entities will be owned by the player who interacts with them or by the server.\nEntity ownership will be transferred if the current owner leaves.\nMastership:\nMap entities may largely be mastered by a dedicated server.\nAvatar entities and props will be mastered by the player that spawned them, even if another player owns them.\n(Example: Alice personally spawns a ball avatar prop and throws it to Bob, who catches it. Alice has Mastership; Bob has Ownership.)\nMastership may be transferred on map exit; or they may be despawned (the player “takes” their props with them.)\nPrivacy: Entities may reveal very little state to the network. Are there cases where different players may be given different permissions?\nExample: Cooperative game, in which state is shared between some players but not others.\nExample: Team Melee\n\n\n\nScript-level guarantees that information about other entities is either restricted or absent entirely.\nIt may require a custom scripting language to achieve these guarantees fully.\n\n\n\nNot much to say here. We should see as little as possible built on top of pure Godot Nodes, except as a means for providing the entity’s functions.\n\n\n\nEntities will not be allowed to contain physics objects within the node hierarchy. Instead, physics objects must be attached to the entity in specific ways.\nQuestions: how does this work with PhysicalBone; how are physics objects linked to the entity; what about animations? (scale, rotation, skeleton attachments driving physical bodies?)\n\n\n\nMaps will have entities that might not be spawnable but will be automatically created and referenced within the parent scene.\nFor example, a button/door; or a state “god object”; or physics objects; built-in TV screens.\n\n\n\nMaps will provide a directory of map-spawnable scene references, which can be instantiated in response to events.\nThese will usually have specific functions within a particular map.\nExamples: Game-specific weapons; Keys; Buildings constructed\n\n\n\nPlayers may also provide a directory of avatar-spawnable scenes; Additionally, a prop database may exist or be negotiated.\nThese may include local UIs; weapons, pencils; media players; pets (parrots, mounts); vehicles; flight mechanics (wings?); visual effects.\n\n\n\nNodePath references (../) out of an entity hierarchy must be disallowed. Parenting should be implemented carefully: If nodes are literally parented to another entity (e.g. vehicles), NodePath references could expose implementation details from one entity to another entity.\nPart of a solution to this is to provide Attachment points as a feature of an Entity, but this needs to be implemented carefully to prevent unusual situations, for example, parent entity/node is destroyed (queue_free()) or removed from the scene tree (remove_child()); or animation paths referencing a node of the child entity."
   },
   {
-    "objectID": "decisions/20240622-gocd-agent-docker-image-update.html#the-infrequent-use-case",
-    "href": "decisions/20240622-gocd-agent-docker-image-update.html#the-infrequent-use-case",
-    "title": "Accepted: GoCD Agent Docker Image Update",
+    "objectID": "decisions/20200729-entity-networking.html#positive-consequences-list",
+    "href": "decisions/20200729-entity-networking.html#positive-consequences-list",
+    "title": "Accepted: Adding Entity Networking to Groups",
     "section": "",
-    "text": "This proposal does not directly address infrequent use cases, as it is focused on maintaining an up-to-date development environment."
+    "text": "Possibility of:\n\nvehicle games\nbow and arrow games\npickup of balls"
   },
   {
-    "objectID": "decisions/20240622-gocd-agent-docker-image-update.html#in-core-and-done-by-us",
-    "href": "decisions/20240622-gocd-agent-docker-image-update.html#in-core-and-done-by-us",
-    "title": "Accepted: GoCD Agent Docker Image Update",
+    "objectID": "decisions/20200729-entity-networking.html#negative-consequences-list",
+    "href": "decisions/20200729-entity-networking.html#negative-consequences-list",
+    "title": "Accepted: Adding Entity Networking to Groups",
     "section": "",
-    "text": "The updating process will be handled by the V-Sekai development team."
+    "text": "Complexity"
   },
   {
-    "objectID": "decisions/20240622-gocd-agent-docker-image-update.html#status",
-    "href": "decisions/20240622-gocd-agent-docker-image-update.html#status",
-    "title": "Accepted: GoCD Agent Docker Image Update",
+    "objectID": "decisions/20200729-entity-networking.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20200729-entity-networking.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Accepted: Adding Entity Networking to Groups",
     "section": "",
-    "text": "Status: Accepted"
+    "text": "A networking system is not a few lines of code."
   },
   {
-    "objectID": "decisions/20240622-gocd-agent-docker-image-update.html#decision-makers",
-    "href": "decisions/20240622-gocd-agent-docker-image-update.html#decision-makers",
-    "title": "Accepted: GoCD Agent Docker Image Update",
+    "objectID": "decisions/20200729-entity-networking.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20200729-entity-networking.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Accepted: Adding Entity Networking to Groups",
     "section": "",
-    "text": "V-Sekai development team\nfire\nlyuma"
+    "text": "Yes, this is the foundation of the protocol and the basic set of nodes and behavior upon which content will be created."
   },
   {
-    "objectID": "decisions/20240622-gocd-agent-docker-image-update.html#tags",
-    "href": "decisions/20240622-gocd-agent-docker-image-update.html#tags",
-    "title": "Accepted: GoCD Agent Docker Image Update",
+    "objectID": "decisions/20200729-entity-networking.html#references",
+    "href": "decisions/20200729-entity-networking.html#references",
+    "title": "Accepted: Adding Entity Networking to Groups",
     "section": "",
-    "text": "V-Sekai\nDocker\nGoCD Agent\nUpdate"
+    "text": "Aldridge, David. “I Shot You First: networking the Gameplay of Halo: Reach”. GDC 2011. https://www.youtube.com/watch?v=h47zZrqjgLc\nFiedler, Glenn. “Networking for Physics Programmers”. GDC 2015. https://www.youtube.com/watch?v=Z9X4lysFr64\nFiedler, Glenn. “Networked Physics in Virtual Reality”. 2018-02-22. https://www.gafferongames.com/post/networked_physics_in_virtual_reality/\nRouwe, Jorrit. “Killzone Shadow Fall: Threading the Entity Update on PS4”. GDCEU 2014. https://archive.org/details/GDCEU2014Rouwe\nSaracen, text and voice discussions on Discord: search Discord for “entity networking” and “networking model”"
   },
   {
-    "objectID": "decisions/20240622-gocd-agent-docker-image-update.html#further-reading",
-    "href": "decisions/20240622-gocd-agent-docker-image-update.html#further-reading",
-    "title": "Accepted: GoCD Agent Docker Image Update",
+    "objectID": "decisions/20200729-entity-networking.html#derivative-license",
+    "href": "decisions/20200729-entity-networking.html#derivative-license",
+    "title": "Accepted: Adding Entity Networking to Groups",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20220605-host-internal-baserow.html",
-    "href": "decisions/20220605-host-internal-baserow.html",
-    "title": "Proposed: Host a baserow application for internal use.",
+    "objectID": "decisions/20211031-thorvg.html",
+    "href": "decisions/20211031-thorvg.html",
+    "title": "Accepted: ThorVG",
     "section": "",
-    "text": "Proposed: Host a baserow application for internal use.\n\nDescribe the status of the issue.\n\nproposed\ndraft\nrejected\naccepted\ndeprecated\nsuperseded by\n\n\n\nList the deciders of the issue.\nV-Sekai,fire\n\n\nDescribe the tags of the issue.\nV-Sekai,\n\n\nContext and Problem Statement\nI want to store adjacent information related to V-Sekai in a database.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nAdd a digital ocean apps config.\nhttps://www.digitalocean.com/products/app-platform\nFeatures:\n\nmanaged postgresql database\nno managed redis\ndigital ocean spaces\napps platform\n\ndatabases:\n- engine: PG\n  name: baserow-db\n  num_nodes: 1\n  size: basic-xs\n  version: \"12\"\nname: chibifire-base\nregion: tor\nservices:\n- envs:\n  - key: BASEROW_PUBLIC_URL\n    scope: RUN_AND_BUILD_TIME\n    value: https://${APP_DOMAIN}\n  - key: DATABASE_URL\n    scope: RUN_AND_BUILD_TIME\n    value: postgresql://${baserow-db.USERNAME}:${baserow-db.PASSWORD}@${baserow-db.HOSTNAME}:${baserow-db.PORT}/${baserow-db.DATABASE}\n  - key: AWS_ACCESS_KEY_ID\n    scope: RUN_AND_BUILD_TIME\n    value: AWS_ACCESS_KEY_ID_AWS_ACCESS_KEY_ID\n  - key: AWS_S3_ENDPOINT_URL\n    scope: RUN_AND_BUILD_TIME\n    value: https://sfo3.digitaloceanspaces.com\n  - key: AWS_S3_CUSTOM_DOMAIN\n    scope: RUN_AND_BUILD_TIME\n    value: 'chibifire.sfo3.digitaloceanspaces.com '\n  - key: AWS_S3_REGION_NAME\n    scope: RUN_AND_BUILD_TIME\n    value: sfo3\n  - key: AWS_STORAGE_BUCKET_NAME\n    scope: RUN_AND_BUILD_TIME\n    value: chibifire\n  - key: AWS_SECRET_ACCESS_KEY\n    scope: RUN_AND_BUILD_TIME\n    type: SECRET\n    value: SECRETSECRETSECRET\n    scope: RUN_AND_BUILD_TIME\n    value: \"true\"\n  - key: SYNC_TEMPLATES_ON_STARTUP\n    scope: RUN_AND_BUILD_TIME\n    value: \"false\"\n  - key: PRIVATE_BACKEND_URL\n    scope: RUN_AND_BUILD_TIME\n    value: ${_self.PRIVATE_URL}\n  http_port: 80\n  image:\n    registry: baserow\n    registry_type: DOCKER_HUB\n    repository: baserow\n    tag: 1.10.2\n  instance_count: 1\n  instance_size_slug: basic-xs\n  name: baserow-baserow\n  routes:\n  - path: /\n\n\n\nPositive Consequences\nI can finally store things.\n\n\nNegative Consequences\nPay for the baserow service.\n\n\nOption graveyard\n\nRejected using premium saas from baserow\nRejected using airtable\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot a few lines of code, but fairly simple.\n\n\nIs there a reason why this should be core and done by us?\nI need to store things.\n\n\nReferences\n\nV-Sekai\nCreate digital ocean instructions\n\n\n\nLicense of the contribution\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Accepted: ThorVG\n\nStatus: accepted\n\n\nContext and Problem Statement\nBetter vector art.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nThorvg supports more art\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n\nThorVG\nsupport light and dark theme\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\n\nnot a few lines of code to do. It’s complicated.\n\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\n@fire know how to approach this.\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20220223-store-source-VSK_map-files-via-DVC.html",
-    "href": "decisions/20220223-store-source-VSK_map-files-via-DVC.html",
-    "title": "Rejected: Storing raw VSK_map files via DVC to avoid limitations",
+    "objectID": "decisions/20211005-use-kvm-to-test-our-amd-apu-test-computer-via-barrier.html",
+    "href": "decisions/20211005-use-kvm-to-test-our-amd-apu-test-computer-via-barrier.html",
+    "title": "Proposed: Use KVM to test our AMD APU test computer via Barrier.",
     "section": "",
-    "text": "pipeline\nV-Sekai\n\n\n\n\n\nrejected \n\n\n\n\n\nV-Sekai\nifire\nlyuma\n\n\n\n\nHow do I version control large binary game assets?\nNeed a procedure to version control large file folders like game map levels.\n\n\n\nPropose using DVC as the version control system on top of git with a S3 remote on Digital Ocean.\n\n\n\nInitial list of binaries to transfer to DVC\nUse a Linux command to get the top 20 by size file types.\n\n*.glb\n*.gltf\n*.bin*\n*.png\n*.webp\n*.jpg\n*.jpeg\n*.exr\n*.scn\n\n\n\nS3 Compatible has multiple implementations. Intent on using digital ocean spaces.\n\n\n\n\nPermissions?\nOpen bucket\nCost of storage\n\n\n\n\n\nhttps://dvc.org/doc/install/windows\n\nhttps://github.com/iterative/dvc/releases/download/2.9.5/dvc-2.9.5.exe\n\nhttps://dvc.org/doc/install/linux\n\n\n\n\ngit clone https://github.com/fire/avatar-wellness.git\ndvc init\ndvc remote add -d chibifire-dvc-web https://chibifire.sfo3.digitaloceanspaces.com/dvc/\n# dvc remote add --local chibifire-dvc-s3 s3://chibifire/dvc\n# dvc remote modify --local chibifire-dvc-s3 endpointurl sfo3.digitaloceanspaces.com\n# dvc remote modify --local chibifire-dvc-s3 access_key_id 'AAAA'\n# dvc remote modify --local chibifire-dvc-s3 secret_access_key 'BBBB'\ndvc config core.autostage true\n\n\n\nDiscussed with Lyuma how it is possible to make a V-Sekai alternative organization for creator repositories.\n\n\n\n\n\nAble to version control maps.\n\n\n\n\n\nUsability now has a gap.\n\n\n\n\n\nOption: Do not use DVC remote on Google drive.\nRejection Reason: Google Drive does not have two implementations\nOption: Use Github with git-lfs\nRejection Reason: The last time I checked it was 50 USD per 50 gigabytes.\nOption: Use Gitlab git-lfs\nRejection Reason: There is slightly larger limit on https://gitlab.com git-lfs but gitlab.com does not scale with usage.\nOption: Use Gitlab.com\nRejection Reason: Gitlab.com commrcial is expensive\n\n\n\n\nA version control system and object stores are not trivial and hard.\n\n\n\nWe want to present V-Sekai maps for others to remix.\n\n\n\n\nDVC Version Control system \n\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Proposed: Use KVM to test our AMD APU test computer via Barrier.\n\nContext and Problem Statement\nUse KVM to test our AMD APU test computer via Barrier.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nBarrier allows us to use the keyboard and mouse transferring commands from Linux to Windows.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nBarrier allows us to use the keyboard and mouse transferring commands from Linux to Windows.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nThis is an operating procedure guide.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nThis a guide.\n\n\nReferences\n\nhttps://github.com/debauchee/barrier\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#categories",
-    "href": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#categories",
-    "title": "Rejected: Storing raw VSK_map files via DVC to avoid limitations",
+    "objectID": "decisions/20240418-college-quest.html",
+    "href": "decisions/20240418-college-quest.html",
+    "title": "Proposed: Town Courier",
     "section": "",
-    "text": "pipeline\nV-Sekai"
+    "text": "In the current gaming landscape, there is a noticeable gap for immersive, open-world games set in realistic environments such as a college town. Most games focus on fantasy or post-apocalyptic settings, leaving room for games that engagingly simulate everyday life.\n\n\n\nThe goal is to create an open-world game that provides players with a unique and dynamic environment, offering a fresh experience every time they play. The game should be set in a bustling college town and allow players to take on the role of a delivery person completing quests. The delivery person will navigate the town on a moped, adding an extra layer of fun and challenge to the gameplay.\n\n\n\n“Town Courier” will be developed using the Godot Engine. The game world will be procedurally generated, ensuring that no two playthroughs are identical. NPCs will assign delivery quests to the player, who must navigate the town and deliver items on a moped within a specified time limit. We will utilize the preexisting vehicle code from “Crappy Contraptions” to facilitate the movement mechanics in our game.\n\n\n\nThis game will fill a niche in the market for realistic, open-world games. It will provide players with a unique and dynamic gaming experience, keeping them engaged and encouraging replayability.\n\n\n\nThe development of a procedurally generated open-world game can be complex and time-consuming. Additionally, balancing the difficulty of the quests to ensure they are challenging but not frustrating may require extensive testing and tweaking.\n\n\n\nAn alternative approach could be to create a static game world with pre-defined quests. However, this would not provide the same level of replayability and could become repetitive for players.\n\n\n\nIn rare cases, the procedural generation may create a game world that is difficult or impossible to navigate. This will need to be addressed during testing.\n\n\n\nThe core gameplay mechanics, including movement, item pickup, and quest assignment, will be developed by our team. We will also handle the creation of the procedurally generated game world.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nCrappy Contraptions\n“City Grid Block” (https://skfb.ly/onMzQ) by antoniojmonteiro is licensed under Creative Commons Attribution\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#status",
-    "href": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#status",
-    "title": "Rejected: Storing raw VSK_map files via DVC to avoid limitations",
+    "objectID": "decisions/20240418-college-quest.html#the-context",
+    "href": "decisions/20240418-college-quest.html#the-context",
+    "title": "Proposed: Town Courier",
     "section": "",
-    "text": "rejected"
+    "text": "In the current gaming landscape, there is a noticeable gap for immersive, open-world games set in realistic environments such as a college town. Most games focus on fantasy or post-apocalyptic settings, leaving room for games that engagingly simulate everyday life."
   },
   {
-    "objectID": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#deciders",
-    "href": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#deciders",
-    "title": "Rejected: Storing raw VSK_map files via DVC to avoid limitations",
+    "objectID": "decisions/20240418-college-quest.html#the-problem-statement",
+    "href": "decisions/20240418-college-quest.html#the-problem-statement",
+    "title": "Proposed: Town Courier",
     "section": "",
-    "text": "V-Sekai\nifire\nlyuma"
+    "text": "The goal is to create an open-world game that provides players with a unique and dynamic environment, offering a fresh experience every time they play. The game should be set in a bustling college town and allow players to take on the role of a delivery person completing quests. The delivery person will navigate the town on a moped, adding an extra layer of fun and challenge to the gameplay."
   },
   {
-    "objectID": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#context-and-problem-statement",
-    "href": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#context-and-problem-statement",
-    "title": "Rejected: Storing raw VSK_map files via DVC to avoid limitations",
+    "objectID": "decisions/20240418-college-quest.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240418-college-quest.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Town Courier",
     "section": "",
-    "text": "How do I version control large binary game assets?\nNeed a procedure to version control large file folders like game map levels."
+    "text": "“Town Courier” will be developed using the Godot Engine. The game world will be procedurally generated, ensuring that no two playthroughs are identical. NPCs will assign delivery quests to the player, who must navigate the town and deliver items on a moped within a specified time limit. We will utilize the preexisting vehicle code from “Crappy Contraptions” to facilitate the movement mechanics in our game."
   },
   {
-    "objectID": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Rejected: Storing raw VSK_map files via DVC to avoid limitations",
+    "objectID": "decisions/20240418-college-quest.html#the-benefits",
+    "href": "decisions/20240418-college-quest.html#the-benefits",
+    "title": "Proposed: Town Courier",
     "section": "",
-    "text": "Propose using DVC as the version control system on top of git with a S3 remote on Digital Ocean."
+    "text": "This game will fill a niche in the market for realistic, open-world games. It will provide players with a unique and dynamic gaming experience, keeping them engaged and encouraging replayability."
   },
   {
-    "objectID": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Rejected: Storing raw VSK_map files via DVC to avoid limitations",
+    "objectID": "decisions/20240418-college-quest.html#the-downsides",
+    "href": "decisions/20240418-college-quest.html#the-downsides",
+    "title": "Proposed: Town Courier",
     "section": "",
-    "text": "Initial list of binaries to transfer to DVC\nUse a Linux command to get the top 20 by size file types.\n\n*.glb\n*.gltf\n*.bin*\n*.png\n*.webp\n*.jpg\n*.jpeg\n*.exr\n*.scn\n\n\n\nS3 Compatible has multiple implementations. Intent on using digital ocean spaces.\n\n\n\n\nPermissions?\nOpen bucket\nCost of storage\n\n\n\n\n\nhttps://dvc.org/doc/install/windows\n\nhttps://github.com/iterative/dvc/releases/download/2.9.5/dvc-2.9.5.exe\n\nhttps://dvc.org/doc/install/linux\n\n\n\n\ngit clone https://github.com/fire/avatar-wellness.git\ndvc init\ndvc remote add -d chibifire-dvc-web https://chibifire.sfo3.digitaloceanspaces.com/dvc/\n# dvc remote add --local chibifire-dvc-s3 s3://chibifire/dvc\n# dvc remote modify --local chibifire-dvc-s3 endpointurl sfo3.digitaloceanspaces.com\n# dvc remote modify --local chibifire-dvc-s3 access_key_id 'AAAA'\n# dvc remote modify --local chibifire-dvc-s3 secret_access_key 'BBBB'\ndvc config core.autostage true\n\n\n\nDiscussed with Lyuma how it is possible to make a V-Sekai alternative organization for creator repositories."
+    "text": "The development of a procedurally generated open-world game can be complex and time-consuming. Additionally, balancing the difficulty of the quests to ensure they are challenging but not frustrating may require extensive testing and tweaking."
   },
   {
-    "objectID": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#positive-consequences",
-    "href": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#positive-consequences",
-    "title": "Rejected: Storing raw VSK_map files via DVC to avoid limitations",
+    "objectID": "decisions/20240418-college-quest.html#the-road-not-taken",
+    "href": "decisions/20240418-college-quest.html#the-road-not-taken",
+    "title": "Proposed: Town Courier",
     "section": "",
-    "text": "Able to version control maps."
+    "text": "An alternative approach could be to create a static game world with pre-defined quests. However, this would not provide the same level of replayability and could become repetitive for players."
   },
   {
-    "objectID": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#negative-consequences",
-    "href": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#negative-consequences",
-    "title": "Rejected: Storing raw VSK_map files via DVC to avoid limitations",
+    "objectID": "decisions/20240418-college-quest.html#the-infrequent-use-case",
+    "href": "decisions/20240418-college-quest.html#the-infrequent-use-case",
+    "title": "Proposed: Town Courier",
     "section": "",
-    "text": "Usability now has a gap."
+    "text": "In rare cases, the procedural generation may create a game world that is difficult or impossible to navigate. This will need to be addressed during testing."
   },
   {
-    "objectID": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#option-graveyard",
-    "href": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#option-graveyard",
-    "title": "Rejected: Storing raw VSK_map files via DVC to avoid limitations",
+    "objectID": "decisions/20240418-college-quest.html#in-core-and-done-by-us",
+    "href": "decisions/20240418-college-quest.html#in-core-and-done-by-us",
+    "title": "Proposed: Town Courier",
     "section": "",
-    "text": "Option: Do not use DVC remote on Google drive.\nRejection Reason: Google Drive does not have two implementations\nOption: Use Github with git-lfs\nRejection Reason: The last time I checked it was 50 USD per 50 gigabytes.\nOption: Use Gitlab git-lfs\nRejection Reason: There is slightly larger limit on https://gitlab.com git-lfs but gitlab.com does not scale with usage.\nOption: Use Gitlab.com\nRejection Reason: Gitlab.com commrcial is expensive"
+    "text": "The core gameplay mechanics, including movement, item pickup, and quest assignment, will be developed by our team. We will also handle the creation of the procedurally generated game world."
   },
   {
-    "objectID": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Rejected: Storing raw VSK_map files via DVC to avoid limitations",
+    "objectID": "decisions/20240418-college-quest.html#status",
+    "href": "decisions/20240418-college-quest.html#status",
+    "title": "Proposed: Town Courier",
     "section": "",
-    "text": "A version control system and object stores are not trivial and hard."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Rejected: Storing raw VSK_map files via DVC to avoid limitations",
+    "objectID": "decisions/20240418-college-quest.html#decision-makers",
+    "href": "decisions/20240418-college-quest.html#decision-makers",
+    "title": "Proposed: Town Courier",
     "section": "",
-    "text": "We want to present V-Sekai maps for others to remix."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#references",
-    "href": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#references",
-    "title": "Rejected: Storing raw VSK_map files via DVC to avoid limitations",
+    "objectID": "decisions/20240418-college-quest.html#tags",
+    "href": "decisions/20240418-college-quest.html#tags",
+    "title": "Proposed: Town Courier",
     "section": "",
-    "text": "DVC Version Control system"
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#derivative-license",
-    "href": "decisions/20220223-store-source-VSK_map-files-via-DVC.html#derivative-license",
-    "title": "Rejected: Storing raw VSK_map files via DVC to avoid limitations",
+    "objectID": "decisions/20240418-college-quest.html#further-reading",
+    "href": "decisions/20240418-college-quest.html#further-reading",
+    "title": "Proposed: Town Courier",
     "section": "",
-    "text": "Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nCrappy Contraptions\n“City Grid Block” (https://skfb.ly/onMzQ) by antoniojmonteiro is licensed under Creative Commons Attribution\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240618-schedule-as-binary-tree.html",
-    "href": "decisions/20240618-schedule-as-binary-tree.html",
-    "title": "Proposed: Transforming Schedule DAG into a Left-child Right-sibling Binary Tree",
+    "objectID": "decisions/20230812-vsekai-update-process.html",
+    "href": "decisions/20230812-vsekai-update-process.html",
+    "title": "Proposed: Update V-Sekai game engine procedure",
     "section": "",
-    "text": "You have a Directed Acyclic Graph (DAG) for a schedule.\n\n\n\nYou want to transform the schedule DAG into a Left-child right-sibling binary tree. This transformation will help in finding ways to hasten the critical path.\n\n\n\nThe original graph was a Directed Acyclic Graph (DAG) where each node could have multiple children. The operations performed on this DAG were aimed at transforming it into a Left-child right-sibling binary tree. Here’s a description of the operations:\n\nIdentifying the First Child: For each node in the original DAG, we identified the first child node. This is the left-most child in the original diagram.\nIdentifying Siblings: For each first child identified in step 1, we then identified its siblings. These are the nodes that share the same parent as the first child.\nCreating Binary Tree: We created a new binary tree where each node has at most two children: the left child is the first child from the original diagram, and the right child is the next sibling of the left child.\nPreserving Order: The order of the nodes in the binary tree follows the order of the nodes in the original DAG.\n\nThe resulting binary tree maintains the directed acyclic property of the original DAG, but now each node has at most two children, making it easier to traverse and manage.\n\n\n\nTransforming the schedule DAG into a Left-child right-sibling binary tree simplifies the structure, making it easier to traverse and manage. It also helps in identifying the critical path more efficiently, which can lead to improved scheduling and better resource allocation.\n\n\n\nThe transformation process may require additional computational resources, especially for large DAGs. Also, if the original DAG has nodes with more than two children, some information may be lost in the transformation.\n\n\n\nAn alternative approach could have been to keep the original DAG structure and optimize the scheduling algorithm. However, this would not simplify the structure or make it easier to manage.\n\n\n\nThis proposal may not be beneficial for small DAGs or DAGs where the critical path is easily identifiable without transformation.\n\n\n\nThe proposed transformation process will be implemented by the V-Sekai development team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\nFire\n\n\n\n\n\nV-Sekai\nDAG\nBinary Tree\nSchedule Optimization\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nV-Sekai is an open-source project that aims to create a virtual world. However, it has some limitations that need to be addressed to improve its performance and user experience.\n\n\n\nThe main challenge is to update the V-Sekai game engine to enhance its features and fix existing issues.\n\n\n\nHere are the steps we propose to take:\n\nUpdate the Godot Engine fork with git assembler.\nRelease the fork to the godot engine branch.\nUpdate the V-Sekai-game engine commit hash.\nCheck the built V-Sekai-game binaries on Github.\n\n\n\n\nUpdating the game engine will provide better performance, improved features, and a more enjoyable user experience.\n\n\n\nThe downside could be potential bugs or issues that might arise during the update process. It may also require additional resources and time to implement the updates.\n\n\n\nThere might be other solutions or strategies that were considered but not chosen for this particular challenge. These could be documented here for future reference.\n\n\n\nThis section can be used to discuss any infrequent use cases that might arise from implementing this decision.\n\n\n\nThis section can be used to discuss whether this decision is core to the project and whether it should be implemented by us or outsourced to another team.\n\n\n\nFor more information about V-Sekai, you can visit their official website.\nThis article is assisted by AI."
   },
   {
-    "objectID": "decisions/20240618-schedule-as-binary-tree.html#the-context",
-    "href": "decisions/20240618-schedule-as-binary-tree.html#the-context",
-    "title": "Proposed: Transforming Schedule DAG into a Left-child Right-sibling Binary Tree",
+    "objectID": "decisions/20230812-vsekai-update-process.html#metadata",
+    "href": "decisions/20230812-vsekai-update-process.html#metadata",
+    "title": "Proposed: Update V-Sekai game engine procedure",
     "section": "",
-    "text": "You have a Directed Acyclic Graph (DAG) for a schedule."
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20240618-schedule-as-binary-tree.html#the-problem-statement",
-    "href": "decisions/20240618-schedule-as-binary-tree.html#the-problem-statement",
-    "title": "Proposed: Transforming Schedule DAG into a Left-child Right-sibling Binary Tree",
+    "objectID": "decisions/20230812-vsekai-update-process.html#the-backdrop",
+    "href": "decisions/20230812-vsekai-update-process.html#the-backdrop",
+    "title": "Proposed: Update V-Sekai game engine procedure",
     "section": "",
-    "text": "You want to transform the schedule DAG into a Left-child right-sibling binary tree. This transformation will help in finding ways to hasten the critical path."
+    "text": "V-Sekai is an open-source project that aims to create a virtual world. However, it has some limitations that need to be addressed to improve its performance and user experience."
   },
   {
-    "objectID": "decisions/20240618-schedule-as-binary-tree.html#solution-proposal",
-    "href": "decisions/20240618-schedule-as-binary-tree.html#solution-proposal",
-    "title": "Proposed: Transforming Schedule DAG into a Left-child Right-sibling Binary Tree",
+    "objectID": "decisions/20230812-vsekai-update-process.html#the-challenge",
+    "href": "decisions/20230812-vsekai-update-process.html#the-challenge",
+    "title": "Proposed: Update V-Sekai game engine procedure",
     "section": "",
-    "text": "The original graph was a Directed Acyclic Graph (DAG) where each node could have multiple children. The operations performed on this DAG were aimed at transforming it into a Left-child right-sibling binary tree. Here’s a description of the operations:\n\nIdentifying the First Child: For each node in the original DAG, we identified the first child node. This is the left-most child in the original diagram.\nIdentifying Siblings: For each first child identified in step 1, we then identified its siblings. These are the nodes that share the same parent as the first child.\nCreating Binary Tree: We created a new binary tree where each node has at most two children: the left child is the first child from the original diagram, and the right child is the next sibling of the left child.\nPreserving Order: The order of the nodes in the binary tree follows the order of the nodes in the original DAG.\n\nThe resulting binary tree maintains the directed acyclic property of the original DAG, but now each node has at most two children, making it easier to traverse and manage."
+    "text": "The main challenge is to update the V-Sekai game engine to enhance its features and fix existing issues."
   },
   {
-    "objectID": "decisions/20240618-schedule-as-binary-tree.html#the-benefits",
-    "href": "decisions/20240618-schedule-as-binary-tree.html#the-benefits",
-    "title": "Proposed: Transforming Schedule DAG into a Left-child Right-sibling Binary Tree",
+    "objectID": "decisions/20230812-vsekai-update-process.html#the-strategy",
+    "href": "decisions/20230812-vsekai-update-process.html#the-strategy",
+    "title": "Proposed: Update V-Sekai game engine procedure",
     "section": "",
-    "text": "Transforming the schedule DAG into a Left-child right-sibling binary tree simplifies the structure, making it easier to traverse and manage. It also helps in identifying the critical path more efficiently, which can lead to improved scheduling and better resource allocation."
+    "text": "Here are the steps we propose to take:\n\nUpdate the Godot Engine fork with git assembler.\nRelease the fork to the godot engine branch.\nUpdate the V-Sekai-game engine commit hash.\nCheck the built V-Sekai-game binaries on Github."
   },
   {
-    "objectID": "decisions/20240618-schedule-as-binary-tree.html#the-downsides",
-    "href": "decisions/20240618-schedule-as-binary-tree.html#the-downsides",
-    "title": "Proposed: Transforming Schedule DAG into a Left-child Right-sibling Binary Tree",
+    "objectID": "decisions/20230812-vsekai-update-process.html#the-upside",
+    "href": "decisions/20230812-vsekai-update-process.html#the-upside",
+    "title": "Proposed: Update V-Sekai game engine procedure",
     "section": "",
-    "text": "The transformation process may require additional computational resources, especially for large DAGs. Also, if the original DAG has nodes with more than two children, some information may be lost in the transformation."
+    "text": "Updating the game engine will provide better performance, improved features, and a more enjoyable user experience."
   },
   {
-    "objectID": "decisions/20240618-schedule-as-binary-tree.html#the-road-not-taken",
-    "href": "decisions/20240618-schedule-as-binary-tree.html#the-road-not-taken",
-    "title": "Proposed: Transforming Schedule DAG into a Left-child Right-sibling Binary Tree",
+    "objectID": "decisions/20230812-vsekai-update-process.html#the-downside",
+    "href": "decisions/20230812-vsekai-update-process.html#the-downside",
+    "title": "Proposed: Update V-Sekai game engine procedure",
     "section": "",
-    "text": "An alternative approach could have been to keep the original DAG structure and optimize the scheduling algorithm. However, this would not simplify the structure or make it easier to manage."
+    "text": "The downside could be potential bugs or issues that might arise during the update process. It may also require additional resources and time to implement the updates."
   },
   {
-    "objectID": "decisions/20240618-schedule-as-binary-tree.html#the-infrequent-use-case",
-    "href": "decisions/20240618-schedule-as-binary-tree.html#the-infrequent-use-case",
-    "title": "Proposed: Transforming Schedule DAG into a Left-child Right-sibling Binary Tree",
+    "objectID": "decisions/20230812-vsekai-update-process.html#the-road-not-taken",
+    "href": "decisions/20230812-vsekai-update-process.html#the-road-not-taken",
+    "title": "Proposed: Update V-Sekai game engine procedure",
     "section": "",
-    "text": "This proposal may not be beneficial for small DAGs or DAGs where the critical path is easily identifiable without transformation."
+    "text": "There might be other solutions or strategies that were considered but not chosen for this particular challenge. These could be documented here for future reference."
   },
   {
-    "objectID": "decisions/20240618-schedule-as-binary-tree.html#in-core-and-done-by-us",
-    "href": "decisions/20240618-schedule-as-binary-tree.html#in-core-and-done-by-us",
-    "title": "Proposed: Transforming Schedule DAG into a Left-child Right-sibling Binary Tree",
+    "objectID": "decisions/20230812-vsekai-update-process.html#the-infrequent-use-case",
+    "href": "decisions/20230812-vsekai-update-process.html#the-infrequent-use-case",
+    "title": "Proposed: Update V-Sekai game engine procedure",
     "section": "",
-    "text": "The proposed transformation process will be implemented by the V-Sekai development team."
+    "text": "This section can be used to discuss any infrequent use cases that might arise from implementing this decision."
   },
   {
-    "objectID": "decisions/20240618-schedule-as-binary-tree.html#status",
-    "href": "decisions/20240618-schedule-as-binary-tree.html#status",
-    "title": "Proposed: Transforming Schedule DAG into a Left-child Right-sibling Binary Tree",
+    "objectID": "decisions/20230812-vsekai-update-process.html#in-core-and-done-by-us",
+    "href": "decisions/20230812-vsekai-update-process.html#in-core-and-done-by-us",
+    "title": "Proposed: Update V-Sekai game engine procedure",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "This section can be used to discuss whether this decision is core to the project and whether it should be implemented by us or outsourced to another team."
   },
   {
-    "objectID": "decisions/20240618-schedule-as-binary-tree.html#decision-makers",
-    "href": "decisions/20240618-schedule-as-binary-tree.html#decision-makers",
-    "title": "Proposed: Transforming Schedule DAG into a Left-child Right-sibling Binary Tree",
+    "objectID": "decisions/20230812-vsekai-update-process.html#further-reading",
+    "href": "decisions/20230812-vsekai-update-process.html#further-reading",
+    "title": "Proposed: Update V-Sekai game engine procedure",
     "section": "",
-    "text": "V-Sekai development team\nFire"
+    "text": "For more information about V-Sekai, you can visit their official website.\nThis article is assisted by AI."
   },
   {
-    "objectID": "decisions/20240618-schedule-as-binary-tree.html#tags",
-    "href": "decisions/20240618-schedule-as-binary-tree.html#tags",
-    "title": "Proposed: Transforming Schedule DAG into a Left-child Right-sibling Binary Tree",
+    "objectID": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html",
+    "href": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html",
+    "title": "Proposed: FFMPEG Wave/Mic and Speaker/Play",
     "section": "",
-    "text": "V-Sekai\nDAG\nBinary Tree\nSchedule Optimization"
+    "text": "Testing audio input and output for VOIP applications.\n\n\n\nSimulate microphone input and capture speaker output to debug and test audio functionality.\n\n\n\nThe following script uses ffmpeg to either generate a test tone or play a provided WAV file as microphone input and record the speaker output. This setup is designed to work on macOS, Windows, and Linux.\n\n\n#!/bin/bash\n\n# Define file paths and device IDs\nINPUT_WAV=\"\"  # Path to an optional input WAV file\nOUTPUT_WAV=\"/path/to/output/speaker_output.wav\"\nMIC_DEVICE=\"plughw:0,0\"      # Replace with your actual mic device ID\nSPEAKER_DEVICE=\"plughw:0,0\"  # Replace with your actual speaker device ID\nDURATION=10                   # Duration in seconds\n\nif [ -z \"$INPUT_WAV\" ]; then\n    # Generate a test tone and play it as microphone input using ffmpeg\n    ffmpeg -f lavfi -i \"sine=frequency=1000:duration=$DURATION\" -f alsa -ac 2 -ar 44100 hw:$MIC_DEVICE &\nelse\n    # Play the provided WAV file as microphone input using ffmpeg\n    ffmpeg -re -i $INPUT_WAV -f alsa -ac 2 -ar 44100 hw:$MIC_DEVICE &\nfi\n\n# Record the speaker output to a WAV file\nffmpeg -f alsa -i $SPEAKER_DEVICE -t $DURATION -ac 2 -ar 44100 $OUTPUT_WAV\n\n# Wait for background processes to finish\nwait\n\n\n\n@echo off\n\n:: Define file paths and device IDs\nset INPUT_WAV=  :: Path to an optional input WAV file\nset OUTPUT_WAV=C:\\path\\to\\output\\speaker_output.wav\nset MIC_DEVICE=audio=\"Microphone (Realtek High Definition Audio)\"  :: Replace with your actual mic device name\nset SPEAKER_DEVICE=audio=\"Speakers (Realtek High Definition Audio)\" :: Replace with your actual speaker device name\nset DURATION=10  :: Duration in seconds\n\nif \"%INPUT_WAV%\"==\"\" (\n    :: Generate a test tone and play it as microphone input using ffmpeg\n    start /B ffmpeg -f lavfi -i \"sine=frequency=1000:duration=%DURATION%\" -f dshow -i %MIC_DEVICE%\n) else (\n    :: Play the provided WAV file as microphone input using ffmpeg\n    start /B ffmpeg -re -i %INPUT_WAV% -f dshow -i %MIC_DEVICE%\n)\n\n:: Record the speaker output to a WAV file\nffmpeg -f dshow -i %SPEAKER_DEVICE% -t %DURATION% -ac 2 -ar 44100 %OUTPUT_WAV%\n\n:: Wait for background processes to finish\nwait\n\n\n\n\n\nTo list available audio devices on Windows, you can use the following command:\nffmpeg -list_devices true -f dshow -i dummy\nThis will output a list of all available audio devices, which you can then use to replace the MIC_DEVICE and SPEAKER_DEVICE placeholders in the batch script.\n\n\n\nOn macOS, you can list audio devices using the following command:\nffmpeg -f avfoundation -list_devices true -i \"\"\nThis command will display both video and audio devices. Look for the audio devices and use their indices or names as needed in your scripts.\n\n\n\nFor Linux, to list audio devices using ffmpeg, you can execute the following command:\nffmpeg -f alsa -list_devices true -i dummy\nThis command will help identify available ALSA audio devices, which can be used similarly to how devices are specified in scripts on other operating systems.\n\n\n\n\n\nDefine File Paths and Device IDs:\n\nINPUT_WAV: Path to an optional input WAV file.\nOUTPUT_WAV: Path where the recorded speaker output will be saved.\nMIC_DEVICE: Microphone device ID (replace with actual device ID).\nSPEAKER_DEVICE: Speaker device ID (replace with actual device ID).\nDURATION: Duration of the recording in seconds.\n\nGenerate a Test Tone or Play Provided WAV File as Microphone Input:\n\nIf INPUT_WAV is not provided, use ffmpeg to generate a 1000 Hz sine wave test tone and play it as if it were coming from the microphone.\nIf INPUT_WAV is provided, use ffmpeg to play the WAV file as if it were coming from the microphone.\n\nRecord the Speaker Output:\n\nUse ffmpeg to record the speaker output to a WAV file for the specified duration.\n\nWait for Background Processes:\n\nEnsure all background processes complete before the script exits.\n\n\n\n\n\n\n\nAutomated Testing: Enables automated testing of VOIP clients.\nVersatility: Can be used to test various VOIP applications like Discord and VRChat.\nPrototyping: Useful for prototyping WebRTC later.\n\n\n\n\n\nComplex Setup: Requires knowledge of audio systems and command-line tools.\nPotential Compatibility Issues: May not work seamlessly across all hardware configurations.\n\n\n\n\nUsing Godot-specific audio stream players and effects was considered but found to be too closely tied to Godot, limiting broader application testing.\n\n\n\nIn cases where precise audio sample rate configuration is critical, additional adjustments may be needed to avoid issues.\n\n\n\nThis approach aligns with our goal of robust and versatile testing methodologies and will be implemented by our team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240618-schedule-as-binary-tree.html#further-reading",
-    "href": "decisions/20240618-schedule-as-binary-tree.html#further-reading",
-    "title": "Proposed: Transforming Schedule DAG into a Left-child Right-sibling Binary Tree",
+    "objectID": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#the-context",
+    "href": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#the-context",
+    "title": "Proposed: FFMPEG Wave/Mic and Speaker/Play",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "Testing audio input and output for VOIP applications."
   },
   {
-    "objectID": "decisions/20230505-automated-avatar-garment-rigging.html",
-    "href": "decisions/20230505-automated-avatar-garment-rigging.html",
-    "title": "Proposed: Automated avatar garment rigging",
+    "objectID": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#the-problem-statement",
+    "href": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#the-problem-statement",
+    "title": "Proposed: FFMPEG Wave/Mic and Speaker/Play",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai,\nTags: V-Sekai, chatgpt4, automated rigging, avatar customization, garment application, 3d modeling, Blender addons,\n\n\n\n\nRigging every possible avatar and garment combination is not feasible. We need a system that allows garments to be easily applied to various avatars without manual rigging each time a new garment or avatar is created.\n\n\n\nHow can we create a system that allows garments to be easily applied to various avatars without the need for manual rigging each time a new garment or avatar is created?\n\n\n\nImplement an automated rigging and wrapping system using known base meshes and garments for easy application of garments to avatars without manual rigging.\n\n\n\n\nCreate avatar and garment models: Create a 3D model representing the basic shape and structure of an avatar without any clothing or accessories, and a 3D model of a piece of clothing or accessory.\nRig models: Rig the avatar and garment models by creating a skeleton structure that defines how they move and deform. Use the Blender Dem Bones add-on to automate the rigging process.\nGenerate cage mesh: Generate a simplified “cage” mesh around the avatar base mesh using the Simplicage add-on. This cage will be used to help apply the garment to the avatar.\nAttach garment to cage: Attach the garment model to the cage created in the previous step, so that it follows the cage’s movement and deformation.\nConform garment to avatar: Utilize the Mesh Materializer add-on to conform the garment model to the avatar base mesh, using a UV texture map to guide the wrapping process. This ensures the garment fits correctly on the avatar.\nManage multiple layers: Develop a system to manage multiple layers of clothing or accessories on the avatar, allowing for proper layering and interaction between clothing items.\n\n\n\n\n\nReduced manual rigging efforts for each garment and avatar combination\nStreamlined process of applying garments to avatars\nEasier customization and creation of new avatars with various garments\n\n\n\n\n\nAdditional development time required to implement the automated system\nPotential compatibility issues with existing assets or workflows\nDependent on third party addons\n\nResearch and evaluate alternative solutions or develop custom tools to replace or supplement the functionality provided by these third-party add-ons. This will help ensure long-term stability and maintainability of the project.\n\nPerformance concerns with complex avatars and garments\n\nOptimize the algorithms used in the automated rigging and wrapping process to handle complex models efficiently. Additionally, consider implementing a level of detail (LOD) system to reduce the complexity of models during runtime without compromising visual quality.\n\nDifficulty in handling edge cases.\n\nDevelop a set of guidelines for creating avatar and garment models that work well with the automated system. Additionally, provide manual intervention options for users to fine-tune the rigging and wrapping results in case of edge cases.\n\n\n\n\n\n\nRelying solely on creators is inefficient; they need tools.\n\n\n\n\nNo, this enhancement requires a more complex solution involving multiple tools and processes.\n\n\n\nThis enhancement requires a complex solution involving multiple tools and processes, and cannot be worked around with a few lines of script. Implementing this feature as part of the core functionality will greatly improve the user experience and streamline the process of creating and customizing avatars with different garments.\n\n\n\n\nV-Sekai\nBlender Dem Bones\nSimplicage\nMesh Materializer"
+    "text": "Simulate microphone input and capture speaker output to debug and test audio functionality."
   },
   {
-    "objectID": "decisions/20230505-automated-avatar-garment-rigging.html#metadata",
-    "href": "decisions/20230505-automated-avatar-garment-rigging.html#metadata",
-    "title": "Proposed: Automated avatar garment rigging",
+    "objectID": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: FFMPEG Wave/Mic and Speaker/Play",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai,\nTags: V-Sekai, chatgpt4, automated rigging, avatar customization, garment application, 3d modeling, Blender addons,"
+    "text": "The following script uses ffmpeg to either generate a test tone or play a provided WAV file as microphone input and record the speaker output. This setup is designed to work on macOS, Windows, and Linux.\n\n\n#!/bin/bash\n\n# Define file paths and device IDs\nINPUT_WAV=\"\"  # Path to an optional input WAV file\nOUTPUT_WAV=\"/path/to/output/speaker_output.wav\"\nMIC_DEVICE=\"plughw:0,0\"      # Replace with your actual mic device ID\nSPEAKER_DEVICE=\"plughw:0,0\"  # Replace with your actual speaker device ID\nDURATION=10                   # Duration in seconds\n\nif [ -z \"$INPUT_WAV\" ]; then\n    # Generate a test tone and play it as microphone input using ffmpeg\n    ffmpeg -f lavfi -i \"sine=frequency=1000:duration=$DURATION\" -f alsa -ac 2 -ar 44100 hw:$MIC_DEVICE &\nelse\n    # Play the provided WAV file as microphone input using ffmpeg\n    ffmpeg -re -i $INPUT_WAV -f alsa -ac 2 -ar 44100 hw:$MIC_DEVICE &\nfi\n\n# Record the speaker output to a WAV file\nffmpeg -f alsa -i $SPEAKER_DEVICE -t $DURATION -ac 2 -ar 44100 $OUTPUT_WAV\n\n# Wait for background processes to finish\nwait\n\n\n\n@echo off\n\n:: Define file paths and device IDs\nset INPUT_WAV=  :: Path to an optional input WAV file\nset OUTPUT_WAV=C:\\path\\to\\output\\speaker_output.wav\nset MIC_DEVICE=audio=\"Microphone (Realtek High Definition Audio)\"  :: Replace with your actual mic device name\nset SPEAKER_DEVICE=audio=\"Speakers (Realtek High Definition Audio)\" :: Replace with your actual speaker device name\nset DURATION=10  :: Duration in seconds\n\nif \"%INPUT_WAV%\"==\"\" (\n    :: Generate a test tone and play it as microphone input using ffmpeg\n    start /B ffmpeg -f lavfi -i \"sine=frequency=1000:duration=%DURATION%\" -f dshow -i %MIC_DEVICE%\n) else (\n    :: Play the provided WAV file as microphone input using ffmpeg\n    start /B ffmpeg -re -i %INPUT_WAV% -f dshow -i %MIC_DEVICE%\n)\n\n:: Record the speaker output to a WAV file\nffmpeg -f dshow -i %SPEAKER_DEVICE% -t %DURATION% -ac 2 -ar 44100 %OUTPUT_WAV%\n\n:: Wait for background processes to finish\nwait\n\n\n\n\n\nTo list available audio devices on Windows, you can use the following command:\nffmpeg -list_devices true -f dshow -i dummy\nThis will output a list of all available audio devices, which you can then use to replace the MIC_DEVICE and SPEAKER_DEVICE placeholders in the batch script.\n\n\n\nOn macOS, you can list audio devices using the following command:\nffmpeg -f avfoundation -list_devices true -i \"\"\nThis command will display both video and audio devices. Look for the audio devices and use their indices or names as needed in your scripts.\n\n\n\nFor Linux, to list audio devices using ffmpeg, you can execute the following command:\nffmpeg -f alsa -list_devices true -i dummy\nThis command will help identify available ALSA audio devices, which can be used similarly to how devices are specified in scripts on other operating systems.\n\n\n\n\n\nDefine File Paths and Device IDs:\n\nINPUT_WAV: Path to an optional input WAV file.\nOUTPUT_WAV: Path where the recorded speaker output will be saved.\nMIC_DEVICE: Microphone device ID (replace with actual device ID).\nSPEAKER_DEVICE: Speaker device ID (replace with actual device ID).\nDURATION: Duration of the recording in seconds.\n\nGenerate a Test Tone or Play Provided WAV File as Microphone Input:\n\nIf INPUT_WAV is not provided, use ffmpeg to generate a 1000 Hz sine wave test tone and play it as if it were coming from the microphone.\nIf INPUT_WAV is provided, use ffmpeg to play the WAV file as if it were coming from the microphone.\n\nRecord the Speaker Output:\n\nUse ffmpeg to record the speaker output to a WAV file for the specified duration.\n\nWait for Background Processes:\n\nEnsure all background processes complete before the script exits."
   },
   {
-    "objectID": "decisions/20230505-automated-avatar-garment-rigging.html#context-and-problem-statement",
-    "href": "decisions/20230505-automated-avatar-garment-rigging.html#context-and-problem-statement",
-    "title": "Proposed: Automated avatar garment rigging",
+    "objectID": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#the-benefits",
+    "href": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#the-benefits",
+    "title": "Proposed: FFMPEG Wave/Mic and Speaker/Play",
     "section": "",
-    "text": "Rigging every possible avatar and garment combination is not feasible. We need a system that allows garments to be easily applied to various avatars without manual rigging each time a new garment or avatar is created."
+    "text": "Automated Testing: Enables automated testing of VOIP clients.\nVersatility: Can be used to test various VOIP applications like Discord and VRChat.\nPrototyping: Useful for prototyping WebRTC later."
   },
   {
-    "objectID": "decisions/20230505-automated-avatar-garment-rigging.html#describe-the-problem-or-limitation-you-have-in-your-project-e.g.-in-free-form-using-two-to-three-sentences.-consider-articulating-the-case-in-the-form-of-a-question.",
-    "href": "decisions/20230505-automated-avatar-garment-rigging.html#describe-the-problem-or-limitation-you-have-in-your-project-e.g.-in-free-form-using-two-to-three-sentences.-consider-articulating-the-case-in-the-form-of-a-question.",
-    "title": "Proposed: Automated avatar garment rigging",
+    "objectID": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#the-downsides",
+    "href": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#the-downsides",
+    "title": "Proposed: FFMPEG Wave/Mic and Speaker/Play",
     "section": "",
-    "text": "How can we create a system that allows garments to be easily applied to various avatars without the need for manual rigging each time a new garment or avatar is created?"
+    "text": "Complex Setup: Requires knowledge of audio systems and command-line tools.\nPotential Compatibility Issues: May not work seamlessly across all hardware configurations."
   },
   {
-    "objectID": "decisions/20230505-automated-avatar-garment-rigging.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20230505-automated-avatar-garment-rigging.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: Automated avatar garment rigging",
+    "objectID": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#the-road-not-taken",
+    "href": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#the-road-not-taken",
+    "title": "Proposed: FFMPEG Wave/Mic and Speaker/Play",
     "section": "",
-    "text": "Implement an automated rigging and wrapping system using known base meshes and garments for easy application of garments to avatars without manual rigging."
+    "text": "Using Godot-specific audio stream players and effects was considered but found to be too closely tied to Godot, limiting broader application testing."
   },
   {
-    "objectID": "decisions/20230505-automated-avatar-garment-rigging.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20230505-automated-avatar-garment-rigging.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Automated avatar garment rigging",
+    "objectID": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#the-infrequent-use-case",
+    "href": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#the-infrequent-use-case",
+    "title": "Proposed: FFMPEG Wave/Mic and Speaker/Play",
     "section": "",
-    "text": "Create avatar and garment models: Create a 3D model representing the basic shape and structure of an avatar without any clothing or accessories, and a 3D model of a piece of clothing or accessory.\nRig models: Rig the avatar and garment models by creating a skeleton structure that defines how they move and deform. Use the Blender Dem Bones add-on to automate the rigging process.\nGenerate cage mesh: Generate a simplified “cage” mesh around the avatar base mesh using the Simplicage add-on. This cage will be used to help apply the garment to the avatar.\nAttach garment to cage: Attach the garment model to the cage created in the previous step, so that it follows the cage’s movement and deformation.\nConform garment to avatar: Utilize the Mesh Materializer add-on to conform the garment model to the avatar base mesh, using a UV texture map to guide the wrapping process. This ensures the garment fits correctly on the avatar.\nManage multiple layers: Develop a system to manage multiple layers of clothing or accessories on the avatar, allowing for proper layering and interaction between clothing items."
+    "text": "In cases where precise audio sample rate configuration is critical, additional adjustments may be needed to avoid issues."
   },
   {
-    "objectID": "decisions/20230505-automated-avatar-garment-rigging.html#positive-consequences",
-    "href": "decisions/20230505-automated-avatar-garment-rigging.html#positive-consequences",
-    "title": "Proposed: Automated avatar garment rigging",
+    "objectID": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#in-core-and-done-by-us",
+    "href": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#in-core-and-done-by-us",
+    "title": "Proposed: FFMPEG Wave/Mic and Speaker/Play",
     "section": "",
-    "text": "Reduced manual rigging efforts for each garment and avatar combination\nStreamlined process of applying garments to avatars\nEasier customization and creation of new avatars with various garments"
+    "text": "This approach aligns with our goal of robust and versatile testing methodologies and will be implemented by our team."
   },
   {
-    "objectID": "decisions/20230505-automated-avatar-garment-rigging.html#negative-consequences",
-    "href": "decisions/20230505-automated-avatar-garment-rigging.html#negative-consequences",
-    "title": "Proposed: Automated avatar garment rigging",
+    "objectID": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#status",
+    "href": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#status",
+    "title": "Proposed: FFMPEG Wave/Mic and Speaker/Play",
     "section": "",
-    "text": "Additional development time required to implement the automated system\nPotential compatibility issues with existing assets or workflows\nDependent on third party addons\n\nResearch and evaluate alternative solutions or develop custom tools to replace or supplement the functionality provided by these third-party add-ons. This will help ensure long-term stability and maintainability of the project.\n\nPerformance concerns with complex avatars and garments\n\nOptimize the algorithms used in the automated rigging and wrapping process to handle complex models efficiently. Additionally, consider implementing a level of detail (LOD) system to reduce the complexity of models during runtime without compromising visual quality.\n\nDifficulty in handling edge cases.\n\nDevelop a set of guidelines for creating avatar and garment models that work well with the automated system. Additionally, provide manual intervention options for users to fine-tune the rigging and wrapping results in case of edge cases."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20230505-automated-avatar-garment-rigging.html#option-graveyard",
-    "href": "decisions/20230505-automated-avatar-garment-rigging.html#option-graveyard",
-    "title": "Proposed: Automated avatar garment rigging",
+    "objectID": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#decision-makers",
+    "href": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#decision-makers",
+    "title": "Proposed: FFMPEG Wave/Mic and Speaker/Play",
     "section": "",
-    "text": "Relying solely on creators is inefficient; they need tools."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20230505-automated-avatar-garment-rigging.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230505-automated-avatar-garment-rigging.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Automated avatar garment rigging",
+    "objectID": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#tags",
+    "href": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#tags",
+    "title": "Proposed: FFMPEG Wave/Mic and Speaker/Play",
     "section": "",
-    "text": "No, this enhancement requires a more complex solution involving multiple tools and processes."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20230505-automated-avatar-garment-rigging.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230505-automated-avatar-garment-rigging.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Automated avatar garment rigging",
+    "objectID": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#further-reading",
+    "href": "decisions/20240824-ffmpeg-wav-mic-speaker-play.html#further-reading",
+    "title": "Proposed: FFMPEG Wave/Mic and Speaker/Play",
     "section": "",
-    "text": "This enhancement requires a complex solution involving multiple tools and processes, and cannot be worked around with a few lines of script. Implementing this feature as part of the core functionality will greatly improve the user experience and streamline the process of creating and customizing avatars with different garments."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20230505-automated-avatar-garment-rigging.html#references",
-    "href": "decisions/20230505-automated-avatar-garment-rigging.html#references",
-    "title": "Proposed: Automated avatar garment rigging",
+    "objectID": "decisions/20240511-wasm-cache-incident.html",
+    "href": "decisions/20240511-wasm-cache-incident.html",
+    "title": "Accepted: Wasm Cache Incident Report",
     "section": "",
-    "text": "V-Sekai\nBlender Dem Bones\nSimplicage\nMesh Materializer"
+    "text": "The issue arose while attempting to build the desync module for Godot Engine 4.3 on Github actions.\n\n\n\nThe following error was encountered even though the module is disabled from building and other code was identical to master:\nerror: undefined symbol: saveSetjmp (referenced by root reference (e.g. compiled C/C++ code))\nwarning: To disable errors for undefined symbols use `-sERROR_ON_UNDEFINED_SYMBOLS=0`\nwarning: _saveSetjmp may need to be added to EXPORTED_FUNCTIONS if it arrives from a system library\nerror: undefined symbol: testSetjmp (referenced by root reference (e.g. compiled C/C++ code))\nwarning: _testSetjmp may need to be added to EXPORTED_FUNCTIONS if it arrives from a system library\nError: Aborting compilation due to previous errors\nem++: error: '/home/runner/work/_temp/5ca5bc6c-db6b-4fae-a502-2fde903054ae/emsdk-main/node/16.20.0_64bit/bin/node /home/runner/work/_temp/5ca5bc6c-db6b-4fae-a502-2fde903054ae/emsdk-main/upstream/emscripten/src/compiler.mjs /tmp/tmpjyhtoot1.json' failed (returned 1)\nscons: *** [bin/godot.web.template_release.wasm32.js] Error 1\nscons: building terminated because of errors.\n\n\n\nThe proposed solution involves modifying the web build Github Actions and suffixing the branch name. The steps are as follows:\n\nModify the GODOT_BASE_BRANCH environment variable in the Github Actions workflow file:\n\nname: 🌐 Web Builds\non:\n  workflow_call:\n\n# Global Settings\nenv:\n  # Used for the cache key. Add version suffix to force clean build.\n  GODOT_BASE_BRANCH: master # Add a suffix here.\n\nCombine master with em version: master-em-3.1.59\nCommit the changes.\n\n\n\n\nThis solution will help in resolving the current build issue and ensure that the Godot Engine 4.3 desync module is built successfully.\n\n\n\nThe downside of this approach is that it requires manual intervention for each build process, which might not be feasible for continuous integration/continuous deployment (CI/CD) pipelines.\n\n\n\nAn alternative could be to investigate the root cause of the undefined symbols and fix them at the source code level.\n\n\n\nThis solution is specifically for the current build issue and may not apply to other build problems or modules.\n\n\n\nThis proposal is made by us and is intended to be implemented in the core build process of the Godot Engine.\n\n\n\nStatus: Accepted\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - The GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis proposal was assisted by Aria, an AI assistant."
   },
   {
-    "objectID": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html",
-    "href": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html",
-    "title": "Rejected: File or attestation for virtual worlds using ssh signatures",
+    "objectID": "decisions/20240511-wasm-cache-incident.html#context",
+    "href": "decisions/20240511-wasm-cache-incident.html#context",
+    "title": "Accepted: Wasm Cache Incident Report",
     "section": "",
-    "text": "Status: rejected \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nFile or attestation for virtual worlds\n\n\n\nUse ssh signatures.\n\n\n\nAn analogy of a CD and a CD case with stickers.\n\n\nRead your public key.\n$ ssh-add -L &gt; me.pub # Can be related to a X.509 `.crt`\nCreate a file.\n$ touch avatar-sample.vrm\nSign your file.\nssh-keygen -Y sign -f &lt;(ssh-add -L) -n \"avatar@v-sekai.org\" &lt; avatar-sample.vrm &gt;&gt; avatar-sample.vrm.avatar%40V-sekai.com.sig\nssh-keygen -Y sign -f &lt;(ssh-add -L) -n \"me@v-sekai.org\" &lt; avatar-sample.vrm &gt;&gt; avatar-sample.vrm.me%40V-sekai.com.sig\nWrite signature to avatar-sample.vrm.sig # Can be attested by multiple people with multiple .sig.\necho -n ernest.lee@chibifire.com | cat - &lt;(echo -n \" \") | cat - &lt;(ssh-add -L) &gt; allowed_signers # Can have more than o\nne line.\nThe allowed_signers file associates a string that represents a person (Principle) to a Public Key.\nssh-keygen -Y verify -f allowed_signers -I ernest.lee@chibifire.com -n \"avatar@v-sekai.org\" -s avatar-sample.vrm.avatar%40V-sekai.com.sig &lt; avatar-sample.vrm\nssh-keygen -Y verify -f allowed_signers -I ernest.lee@chibifire.com -n \"me@v-sekai.org\" -s  avatar-sample.vrm.me%40V-sekai.com.sig &lt; avatar-sample.vrm\nReferenced https://www.agwa.name/blog/post/ssh_signatures\n\n\n\n# ssh-add ~/.ssh/id_ed25519\n# or smartcard\n# TODO: How do you change authorization of the delegation?\nssh-keygen -Us &lt;(ssh-add -L) -I fire@example.com -n avatar@V-Sekai.com -V +1h KEYFILE.pub\n\n\n\n# Resulting file is namespace.allowed_signers but uri_encoded.\ncurl https://github.com/fire.keys &gt; avatars%40V-Sekai.com.allowed_signers # Needs a id in email syntax in front of a key\ncurl files://uro &gt; avatars%40V-sekai.com.allowed_signers # Assumed in correct format\ncurl http://matrix-homeserver.example.com/fire &gt; avatars%40V-sekai.com.allowed_signers # Assumed in correct format\n\n\n\n\n\nAble to distribute a game launcher.\nAble to add a makers mark to items.\nUse for verifying binaries\nUse for verifying game modifications\nUsed for lobby servers to prove to the player that they are official.\nDouble sided friending\n\n\n\n\n\nNo data encryption\n\n\n\n\n\nOption: Matrix\nRejection Reason: Technically complicated to devops start and multiple layers compared to an offline approach.\nOption: Ipfs and Etherium\nRejection Reason: Requires a globally distributed database.\nOption: Sigstore https://www.sigstore.dev/\nRejection Reason: Why aren’t we using sigstore?\n\n\n\n\nNot able to use a few lines of code.\n\n\n\nWe have to define the trust.\n\n\n\n\nhttps://github.com/V-Sekai/\nhttps://github.com/sigstore/rekor/tree/main/pkg/pki/ssh\nhttps://stackoverflow.com/questions/4629537/how-to-encrypt-data-in-php-using-public-private-keys\nhttps://stackoverflow.com/questions/60160082/how-to-achieve-openssl-smime-encrypt-with-public-key-functionality-in-code\nhttps://github.com/cloudtools/ssh-cert-authority\nhttps://github.com/je9000/ssh-smime\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "The issue arose while attempting to build the desync module for Godot Engine 4.3 on Github actions."
   },
   {
-    "objectID": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html#context-and-problem-statement",
-    "href": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html#context-and-problem-statement",
-    "title": "Rejected: File or attestation for virtual worlds using ssh signatures",
+    "objectID": "decisions/20240511-wasm-cache-incident.html#problem-statement",
+    "href": "decisions/20240511-wasm-cache-incident.html#problem-statement",
+    "title": "Accepted: Wasm Cache Incident Report",
     "section": "",
-    "text": "File or attestation for virtual worlds"
+    "text": "The following error was encountered even though the module is disabled from building and other code was identical to master:\nerror: undefined symbol: saveSetjmp (referenced by root reference (e.g. compiled C/C++ code))\nwarning: To disable errors for undefined symbols use `-sERROR_ON_UNDEFINED_SYMBOLS=0`\nwarning: _saveSetjmp may need to be added to EXPORTED_FUNCTIONS if it arrives from a system library\nerror: undefined symbol: testSetjmp (referenced by root reference (e.g. compiled C/C++ code))\nwarning: _testSetjmp may need to be added to EXPORTED_FUNCTIONS if it arrives from a system library\nError: Aborting compilation due to previous errors\nem++: error: '/home/runner/work/_temp/5ca5bc6c-db6b-4fae-a502-2fde903054ae/emsdk-main/node/16.20.0_64bit/bin/node /home/runner/work/_temp/5ca5bc6c-db6b-4fae-a502-2fde903054ae/emsdk-main/upstream/emscripten/src/compiler.mjs /tmp/tmpjyhtoot1.json' failed (returned 1)\nscons: *** [bin/godot.web.template_release.wasm32.js] Error 1\nscons: building terminated because of errors."
   },
   {
-    "objectID": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Rejected: File or attestation for virtual worlds using ssh signatures",
+    "objectID": "decisions/20240511-wasm-cache-incident.html#proposed-solution",
+    "href": "decisions/20240511-wasm-cache-incident.html#proposed-solution",
+    "title": "Accepted: Wasm Cache Incident Report",
     "section": "",
-    "text": "Use ssh signatures."
+    "text": "The proposed solution involves modifying the web build Github Actions and suffixing the branch name. The steps are as follows:\n\nModify the GODOT_BASE_BRANCH environment variable in the Github Actions workflow file:\n\nname: 🌐 Web Builds\non:\n  workflow_call:\n\n# Global Settings\nenv:\n  # Used for the cache key. Add version suffix to force clean build.\n  GODOT_BASE_BRANCH: master # Add a suffix here.\n\nCombine master with em version: master-em-3.1.59\nCommit the changes."
   },
   {
-    "objectID": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Rejected: File or attestation for virtual worlds using ssh signatures",
+    "objectID": "decisions/20240511-wasm-cache-incident.html#benefits",
+    "href": "decisions/20240511-wasm-cache-incident.html#benefits",
+    "title": "Accepted: Wasm Cache Incident Report",
     "section": "",
-    "text": "An analogy of a CD and a CD case with stickers.\n\n\nRead your public key.\n$ ssh-add -L &gt; me.pub # Can be related to a X.509 `.crt`\nCreate a file.\n$ touch avatar-sample.vrm\nSign your file.\nssh-keygen -Y sign -f &lt;(ssh-add -L) -n \"avatar@v-sekai.org\" &lt; avatar-sample.vrm &gt;&gt; avatar-sample.vrm.avatar%40V-sekai.com.sig\nssh-keygen -Y sign -f &lt;(ssh-add -L) -n \"me@v-sekai.org\" &lt; avatar-sample.vrm &gt;&gt; avatar-sample.vrm.me%40V-sekai.com.sig\nWrite signature to avatar-sample.vrm.sig # Can be attested by multiple people with multiple .sig.\necho -n ernest.lee@chibifire.com | cat - &lt;(echo -n \" \") | cat - &lt;(ssh-add -L) &gt; allowed_signers # Can have more than o\nne line.\nThe allowed_signers file associates a string that represents a person (Principle) to a Public Key.\nssh-keygen -Y verify -f allowed_signers -I ernest.lee@chibifire.com -n \"avatar@v-sekai.org\" -s avatar-sample.vrm.avatar%40V-sekai.com.sig &lt; avatar-sample.vrm\nssh-keygen -Y verify -f allowed_signers -I ernest.lee@chibifire.com -n \"me@v-sekai.org\" -s  avatar-sample.vrm.me%40V-sekai.com.sig &lt; avatar-sample.vrm\nReferenced https://www.agwa.name/blog/post/ssh_signatures\n\n\n\n# ssh-add ~/.ssh/id_ed25519\n# or smartcard\n# TODO: How do you change authorization of the delegation?\nssh-keygen -Us &lt;(ssh-add -L) -I fire@example.com -n avatar@V-Sekai.com -V +1h KEYFILE.pub\n\n\n\n# Resulting file is namespace.allowed_signers but uri_encoded.\ncurl https://github.com/fire.keys &gt; avatars%40V-Sekai.com.allowed_signers # Needs a id in email syntax in front of a key\ncurl files://uro &gt; avatars%40V-sekai.com.allowed_signers # Assumed in correct format\ncurl http://matrix-homeserver.example.com/fire &gt; avatars%40V-sekai.com.allowed_signers # Assumed in correct format"
+    "text": "This solution will help in resolving the current build issue and ensure that the Godot Engine 4.3 desync module is built successfully."
   },
   {
-    "objectID": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html#positive-consequences",
-    "href": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html#positive-consequences",
-    "title": "Rejected: File or attestation for virtual worlds using ssh signatures",
+    "objectID": "decisions/20240511-wasm-cache-incident.html#downsides",
+    "href": "decisions/20240511-wasm-cache-incident.html#downsides",
+    "title": "Accepted: Wasm Cache Incident Report",
     "section": "",
-    "text": "Able to distribute a game launcher.\nAble to add a makers mark to items.\nUse for verifying binaries\nUse for verifying game modifications\nUsed for lobby servers to prove to the player that they are official.\nDouble sided friending"
+    "text": "The downside of this approach is that it requires manual intervention for each build process, which might not be feasible for continuous integration/continuous deployment (CI/CD) pipelines."
   },
   {
-    "objectID": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html#negative-consequences",
-    "href": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html#negative-consequences",
-    "title": "Rejected: File or attestation for virtual worlds using ssh signatures",
+    "objectID": "decisions/20240511-wasm-cache-incident.html#alternatives-considered",
+    "href": "decisions/20240511-wasm-cache-incident.html#alternatives-considered",
+    "title": "Accepted: Wasm Cache Incident Report",
     "section": "",
-    "text": "No data encryption"
+    "text": "An alternative could be to investigate the root cause of the undefined symbols and fix them at the source code level."
   },
   {
-    "objectID": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html#option-graveyard",
-    "href": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html#option-graveyard",
-    "title": "Rejected: File or attestation for virtual worlds using ssh signatures",
+    "objectID": "decisions/20240511-wasm-cache-incident.html#infrequent-use-case",
+    "href": "decisions/20240511-wasm-cache-incident.html#infrequent-use-case",
+    "title": "Accepted: Wasm Cache Incident Report",
     "section": "",
-    "text": "Option: Matrix\nRejection Reason: Technically complicated to devops start and multiple layers compared to an offline approach.\nOption: Ipfs and Etherium\nRejection Reason: Requires a globally distributed database.\nOption: Sigstore https://www.sigstore.dev/\nRejection Reason: Why aren’t we using sigstore?"
+    "text": "This solution is specifically for the current build issue and may not apply to other build problems or modules."
   },
   {
-    "objectID": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Rejected: File or attestation for virtual worlds using ssh signatures",
+    "objectID": "decisions/20240511-wasm-cache-incident.html#in-core-and-done-by-us",
+    "href": "decisions/20240511-wasm-cache-incident.html#in-core-and-done-by-us",
+    "title": "Accepted: Wasm Cache Incident Report",
     "section": "",
-    "text": "Not able to use a few lines of code."
+    "text": "This proposal is made by us and is intended to be implemented in the core build process of the Godot Engine."
   },
   {
-    "objectID": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Rejected: File or attestation for virtual worlds using ssh signatures",
+    "objectID": "decisions/20240511-wasm-cache-incident.html#status",
+    "href": "decisions/20240511-wasm-cache-incident.html#status",
+    "title": "Accepted: Wasm Cache Incident Report",
     "section": "",
-    "text": "We have to define the trust."
+    "text": "Status: Accepted"
   },
   {
-    "objectID": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html#references",
-    "href": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html#references",
-    "title": "Rejected: File or attestation for virtual worlds using ssh signatures",
+    "objectID": "decisions/20240511-wasm-cache-incident.html#decision-makers",
+    "href": "decisions/20240511-wasm-cache-incident.html#decision-makers",
+    "title": "Accepted: Wasm Cache Incident Report",
     "section": "",
-    "text": "https://github.com/V-Sekai/\nhttps://github.com/sigstore/rekor/tree/main/pkg/pki/ssh\nhttps://stackoverflow.com/questions/4629537/how-to-encrypt-data-in-php-using-public-private-keys\nhttps://stackoverflow.com/questions/60160082/how-to-achieve-openssl-smime-encrypt-with-public-key-functionality-in-code\nhttps://github.com/cloudtools/ssh-cert-authority\nhttps://github.com/je9000/ssh-smime"
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html#derivative-license",
-    "href": "decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html#derivative-license",
-    "title": "Rejected: File or attestation for virtual worlds using ssh signatures",
+    "objectID": "decisions/20240511-wasm-cache-incident.html#tags",
+    "href": "decisions/20240511-wasm-cache-incident.html#tags",
+    "title": "Accepted: Wasm Cache Incident Report",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20220130-optimize-cicd.html",
-    "href": "decisions/20220130-optimize-cicd.html",
-    "title": "Proposal: Optimize cicd for costs because it’s limited",
+    "objectID": "decisions/20240511-wasm-cache-incident.html#further-reading",
+    "href": "decisions/20240511-wasm-cache-incident.html#further-reading",
+    "title": "Accepted: Wasm Cache Incident Report",
     "section": "",
-    "text": "Status: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nCICD isn’t optimized.\n\n\n\nDo not upload the template .tpz.\n\n\n\n\nGo to gocd cicd.\nRemove .tpz package workflow.\nMove each output to a separate release.\nDo not duplicate editor and game builds if they’re the same.\nPublish a web build with editor if built.\n\n\n\n\n\nReduce the costs of upload\n\n\n\n\n\nChange in a stable system is disruptive.\n\n\n\n\n\nOption: Do nothing.\nRejection Reason: Expensive.\n\n\n\n\nNot a code but devops.\n\n\n\nWe are running the cicd service.\n\n\n\n\nGOCD\n\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - The GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis proposal was assisted by Aria, an AI assistant."
   },
   {
-    "objectID": "decisions/20220130-optimize-cicd.html#context-and-problem-statement",
-    "href": "decisions/20220130-optimize-cicd.html#context-and-problem-statement",
-    "title": "Proposal: Optimize cicd for costs because it’s limited",
+    "objectID": "decisions/20241016-instantiating-v-sekai-content.html",
+    "href": "decisions/20241016-instantiating-v-sekai-content.html",
+    "title": "Proposed: Evaluate three proposals for V-Sekai content distribution",
     "section": "",
-    "text": "CICD isn’t optimized."
+    "text": "Address security concerns with V-Sekai content distribution like including the sandbox API surface, file size management, resource loading, and packed scene instantiation.\n\n\n\nWe aim to safely initialize an avatar body from the V-Sekai content distribution network into the virtual world without compromising security or performance.\nWe wish to enable Godot to load older content seamlessly.\nWe want to avoid animations causing security issues.\n\n\n\n\n\nThis method involves loading chunks of an average packed scene from the web, instantiating it in the sandbox, and applying runtime verification. This approach prevents double initializer security concerns and avoids using double the memory to copy PackedScene.\n\n\nDifferent content initializers becomes a security problem as code drifts and fixes are lost.\n\n\n\n\nFor this option, we would stream an average glTF file from the web and develop a loader for glTF within the Godot sandbox equipped with a set of verifiers.\nWe must create custom VSEKAI or GODOT extensions for each unspecified resource and node type, though simple schemas could be autogenerated from classes.\n\n\n\nCreating a JSON schema for arbitrary Godot-packed scene resources that have been converted to JSON is a complex task. This option might be more challenging than adapting glTF for sandbox C++.\n\n\n\n\nA significant benefit of these approaches is the ability to enforce specific requirements, such as using PCVR and mobile image textures through formats like Basis Universal, BPTC, and ASTC during upload and download. By controlling the instantiation process, we can also prevent loading when, for example, an avatar exceeds a polycount of 70,000 triangles. We can size worlds according to predefined constraints, with various optimization settings available.\n\n\n\nThe primary downside is the complexity of these security measures and their potential performance impact. Each option requires substantial development effort and may introduce latency or processing overhead. Furthermore, maintaining these systems as Godot evolves could increase long-term maintenance costs.\n\n\n\nWe could have explored simpler, less secure methods of content distribution that rely more heavily on post-load validation rather than stringent pre-load checks.\n\n\n\nThese methods are designed to handle extremely large or complex scenes that might exceed the proposed limits and infrequent resource types not covered by standard validators.\n\n\n\nWe will maintain the core functionality of the sandbox and basic loaders, ensuring that critical updates or security patches can be applied swiftly and uniformly.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\nFire\nLyuma\nfwsgonzo\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - This GitHub page hosts the V-Sekai open-source project, which integrates social VR/VRSNS/metaverse components into the Godot Engine."
   },
   {
-    "objectID": "decisions/20220130-optimize-cicd.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20220130-optimize-cicd.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposal: Optimize cicd for costs because it’s limited",
+    "objectID": "decisions/20241016-instantiating-v-sekai-content.html#the-context",
+    "href": "decisions/20241016-instantiating-v-sekai-content.html#the-context",
+    "title": "Proposed: Evaluate three proposals for V-Sekai content distribution",
     "section": "",
-    "text": "Do not upload the template .tpz."
+    "text": "Address security concerns with V-Sekai content distribution like including the sandbox API surface, file size management, resource loading, and packed scene instantiation."
   },
   {
-    "objectID": "decisions/20220130-optimize-cicd.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20220130-optimize-cicd.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposal: Optimize cicd for costs because it’s limited",
+    "objectID": "decisions/20241016-instantiating-v-sekai-content.html#the-problem-statement",
+    "href": "decisions/20241016-instantiating-v-sekai-content.html#the-problem-statement",
+    "title": "Proposed: Evaluate three proposals for V-Sekai content distribution",
     "section": "",
-    "text": "Go to gocd cicd.\nRemove .tpz package workflow.\nMove each output to a separate release.\nDo not duplicate editor and game builds if they’re the same.\nPublish a web build with editor if built."
+    "text": "We aim to safely initialize an avatar body from the V-Sekai content distribution network into the virtual world without compromising security or performance.\nWe wish to enable Godot to load older content seamlessly.\nWe want to avoid animations causing security issues."
   },
   {
-    "objectID": "decisions/20220130-optimize-cicd.html#positive-consequences",
-    "href": "decisions/20220130-optimize-cicd.html#positive-consequences",
-    "title": "Proposal: Optimize cicd for costs because it’s limited",
+    "objectID": "decisions/20241016-instantiating-v-sekai-content.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20241016-instantiating-v-sekai-content.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Evaluate three proposals for V-Sekai content distribution",
     "section": "",
-    "text": "Reduce the costs of upload"
+    "text": "This method involves loading chunks of an average packed scene from the web, instantiating it in the sandbox, and applying runtime verification. This approach prevents double initializer security concerns and avoids using double the memory to copy PackedScene.\n\n\nDifferent content initializers becomes a security problem as code drifts and fixes are lost.\n\n\n\n\nFor this option, we would stream an average glTF file from the web and develop a loader for glTF within the Godot sandbox equipped with a set of verifiers.\nWe must create custom VSEKAI or GODOT extensions for each unspecified resource and node type, though simple schemas could be autogenerated from classes.\n\n\n\nCreating a JSON schema for arbitrary Godot-packed scene resources that have been converted to JSON is a complex task. This option might be more challenging than adapting glTF for sandbox C++."
   },
   {
-    "objectID": "decisions/20220130-optimize-cicd.html#negative-consequences",
-    "href": "decisions/20220130-optimize-cicd.html#negative-consequences",
-    "title": "Proposal: Optimize cicd for costs because it’s limited",
+    "objectID": "decisions/20241016-instantiating-v-sekai-content.html#the-benefits",
+    "href": "decisions/20241016-instantiating-v-sekai-content.html#the-benefits",
+    "title": "Proposed: Evaluate three proposals for V-Sekai content distribution",
     "section": "",
-    "text": "Change in a stable system is disruptive."
+    "text": "A significant benefit of these approaches is the ability to enforce specific requirements, such as using PCVR and mobile image textures through formats like Basis Universal, BPTC, and ASTC during upload and download. By controlling the instantiation process, we can also prevent loading when, for example, an avatar exceeds a polycount of 70,000 triangles. We can size worlds according to predefined constraints, with various optimization settings available."
   },
   {
-    "objectID": "decisions/20220130-optimize-cicd.html#option-graveyard",
-    "href": "decisions/20220130-optimize-cicd.html#option-graveyard",
-    "title": "Proposal: Optimize cicd for costs because it’s limited",
+    "objectID": "decisions/20241016-instantiating-v-sekai-content.html#the-downsides",
+    "href": "decisions/20241016-instantiating-v-sekai-content.html#the-downsides",
+    "title": "Proposed: Evaluate three proposals for V-Sekai content distribution",
     "section": "",
-    "text": "Option: Do nothing.\nRejection Reason: Expensive."
+    "text": "The primary downside is the complexity of these security measures and their potential performance impact. Each option requires substantial development effort and may introduce latency or processing overhead. Furthermore, maintaining these systems as Godot evolves could increase long-term maintenance costs."
   },
   {
-    "objectID": "decisions/20220130-optimize-cicd.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20220130-optimize-cicd.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposal: Optimize cicd for costs because it’s limited",
+    "objectID": "decisions/20241016-instantiating-v-sekai-content.html#the-road-not-taken",
+    "href": "decisions/20241016-instantiating-v-sekai-content.html#the-road-not-taken",
+    "title": "Proposed: Evaluate three proposals for V-Sekai content distribution",
     "section": "",
-    "text": "Not a code but devops."
+    "text": "We could have explored simpler, less secure methods of content distribution that rely more heavily on post-load validation rather than stringent pre-load checks."
   },
   {
-    "objectID": "decisions/20220130-optimize-cicd.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20220130-optimize-cicd.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposal: Optimize cicd for costs because it’s limited",
+    "objectID": "decisions/20241016-instantiating-v-sekai-content.html#the-infrequent-use-case",
+    "href": "decisions/20241016-instantiating-v-sekai-content.html#the-infrequent-use-case",
+    "title": "Proposed: Evaluate three proposals for V-Sekai content distribution",
     "section": "",
-    "text": "We are running the cicd service."
+    "text": "These methods are designed to handle extremely large or complex scenes that might exceed the proposed limits and infrequent resource types not covered by standard validators."
   },
   {
-    "objectID": "decisions/20220130-optimize-cicd.html#references",
-    "href": "decisions/20220130-optimize-cicd.html#references",
-    "title": "Proposal: Optimize cicd for costs because it’s limited",
+    "objectID": "decisions/20241016-instantiating-v-sekai-content.html#in-core-and-done-by-us",
+    "href": "decisions/20241016-instantiating-v-sekai-content.html#in-core-and-done-by-us",
+    "title": "Proposed: Evaluate three proposals for V-Sekai content distribution",
     "section": "",
-    "text": "GOCD"
+    "text": "We will maintain the core functionality of the sandbox and basic loaders, ensuring that critical updates or security patches can be applied swiftly and uniformly."
   },
   {
-    "objectID": "decisions/20220130-optimize-cicd.html#derivative-license",
-    "href": "decisions/20220130-optimize-cicd.html#derivative-license",
-    "title": "Proposal: Optimize cicd for costs because it’s limited",
+    "objectID": "decisions/20241016-instantiating-v-sekai-content.html#status",
+    "href": "decisions/20241016-instantiating-v-sekai-content.html#status",
+    "title": "Proposed: Evaluate three proposals for V-Sekai content distribution",
     "section": "",
-    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20221203-block-direct-pushes-to-main.html",
-    "href": "decisions/20221203-block-direct-pushes-to-main.html",
-    "title": "Rejected: Blocking direct push to MAIN to avoid build breakage",
+    "objectID": "decisions/20241016-instantiating-v-sekai-content.html#decision-makers",
+    "href": "decisions/20241016-instantiating-v-sekai-content.html#decision-makers",
+    "title": "Proposed: Evaluate three proposals for V-Sekai content distribution",
     "section": "",
-    "text": "Status: rejected \nDeciders: V-Sekai,fire,lyuma,\nTags: V-Sekai,\n\n\n\nDirect push to main cause build breakage.\nNote: This has been rejected by Lyuma.\n\n\n\nWe block direct pushes to the main and use pull requests and merges.\n\n\n\nUse the GitHub workflow with pull requests.\n\n\n\nWe don’t have to wait 2 hours to see if our changes break the build.\n\n\n\nThere are consequences of increased developer merging friction.\n\n\n\n\nOption: The status quo. \nRejection Reason: We keep breaking the build. \n\n\n\n\nThis is a dev ops change.\n\n\n\nWe own the GitHub repositories.\n\n\n\n\nV-Sekai\nPending head\nGodot Pull request\n\n\n\n\nCopyright (c) 2022 K. S. Ernest (iFire) Lee\nCopyright (c) 2022 V-Sekai contributors\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "V-Sekai development team\nFire\nLyuma\nfwsgonzo"
   },
   {
-    "objectID": "decisions/20221203-block-direct-pushes-to-main.html#context-and-problem-statement",
-    "href": "decisions/20221203-block-direct-pushes-to-main.html#context-and-problem-statement",
-    "title": "Rejected: Blocking direct push to MAIN to avoid build breakage",
+    "objectID": "decisions/20241016-instantiating-v-sekai-content.html#tags",
+    "href": "decisions/20241016-instantiating-v-sekai-content.html#tags",
+    "title": "Proposed: Evaluate three proposals for V-Sekai content distribution",
     "section": "",
-    "text": "Direct push to main cause build breakage.\nNote: This has been rejected by Lyuma."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20221203-block-direct-pushes-to-main.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20221203-block-direct-pushes-to-main.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Rejected: Blocking direct push to MAIN to avoid build breakage",
+    "objectID": "decisions/20241016-instantiating-v-sekai-content.html#further-reading",
+    "href": "decisions/20241016-instantiating-v-sekai-content.html#further-reading",
+    "title": "Proposed: Evaluate three proposals for V-Sekai content distribution",
     "section": "",
-    "text": "We block direct pushes to the main and use pull requests and merges."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - This GitHub page hosts the V-Sekai open-source project, which integrates social VR/VRSNS/metaverse components into the Godot Engine."
   },
   {
-    "objectID": "decisions/20221203-block-direct-pushes-to-main.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20221203-block-direct-pushes-to-main.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Rejected: Blocking direct push to MAIN to avoid build breakage",
+    "objectID": "decisions/20240326-verifying-and-finetuning-plans.html",
+    "href": "decisions/20240326-verifying-and-finetuning-plans.html",
+    "title": "Proposed: Teaching Large Language Models (LLMs) with Goal-Task Planners",
     "section": "",
-    "text": "Use the GitHub workflow with pull requests."
+    "text": "We’re looking at using LLMs and goal-task planners like pyhop to generate innovative, executable plans. This approach combines the creativity of LLMs with the structured planning processes of goal-task planners.\n\n\n\nThe main challenges are computational overhead due to the two-step process and potential inaccuracies in the feasibility check.\n\n\n\nWe propose using an LLM for idea generation and a goal-task planner for checking feasibility. This could lead to creative and feasible plans. The accurate plans generated by this model can then be used to further train the LLM.\n# Pseudo-code\ngpt = GPT()\nidea = gpt.generate_idea()\n\npyhop = Pyhop()\nfeasible = pyhop.find_plan(state, goal_generator())\n\nif feasible:\n    gpt.train(idea)\n\n\n\n\nInnovation: Using LLMs for idea generation can lead to creative ideas.\nPracticality: Passing the generated ideas through a goal-task planner ensures that the plans are innovative but also feasible and executable.\nContinuous Learning: The LLM can learn from the accurate plans, improving its performance over time.\n\n\n\n\n\nComputational Overhead: There might be a computational overhead due to the two-step process.\nAccuracy of Feasibility Check: The feasibility check might not always be accurate.\n\n\n\n\nAn alternative approach could be to run the LLM and the goal-task planner in parallel to address the computational overhead.\n\n\n\nThis method may not be suitable for tasks that require immediate results due to the time taken by the two-step process.\n\n\n\nThe V-Sekai development team will implement this proposal.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nLLMs Can’t Plan, But Can Help Planning in LLM-Modulo Frameworks\n\nAI assistant Aria assisted with this feedback."
   },
   {
-    "objectID": "decisions/20221203-block-direct-pushes-to-main.html#positive-consequences",
-    "href": "decisions/20221203-block-direct-pushes-to-main.html#positive-consequences",
-    "title": "Rejected: Blocking direct push to MAIN to avoid build breakage",
+    "objectID": "decisions/20240326-verifying-and-finetuning-plans.html#context",
+    "href": "decisions/20240326-verifying-and-finetuning-plans.html#context",
+    "title": "Proposed: Teaching Large Language Models (LLMs) with Goal-Task Planners",
     "section": "",
-    "text": "We don’t have to wait 2 hours to see if our changes break the build."
+    "text": "We’re looking at using LLMs and goal-task planners like pyhop to generate innovative, executable plans. This approach combines the creativity of LLMs with the structured planning processes of goal-task planners."
   },
   {
-    "objectID": "decisions/20221203-block-direct-pushes-to-main.html#negative-consequences",
-    "href": "decisions/20221203-block-direct-pushes-to-main.html#negative-consequences",
-    "title": "Rejected: Blocking direct push to MAIN to avoid build breakage",
+    "objectID": "decisions/20240326-verifying-and-finetuning-plans.html#problem-statement",
+    "href": "decisions/20240326-verifying-and-finetuning-plans.html#problem-statement",
+    "title": "Proposed: Teaching Large Language Models (LLMs) with Goal-Task Planners",
     "section": "",
-    "text": "There are consequences of increased developer merging friction."
+    "text": "The main challenges are computational overhead due to the two-step process and potential inaccuracies in the feasibility check."
   },
   {
-    "objectID": "decisions/20221203-block-direct-pushes-to-main.html#option-graveyard",
-    "href": "decisions/20221203-block-direct-pushes-to-main.html#option-graveyard",
-    "title": "Rejected: Blocking direct push to MAIN to avoid build breakage",
+    "objectID": "decisions/20240326-verifying-and-finetuning-plans.html#proposed-solution",
+    "href": "decisions/20240326-verifying-and-finetuning-plans.html#proposed-solution",
+    "title": "Proposed: Teaching Large Language Models (LLMs) with Goal-Task Planners",
     "section": "",
-    "text": "Option: The status quo. \nRejection Reason: We keep breaking the build."
+    "text": "We propose using an LLM for idea generation and a goal-task planner for checking feasibility. This could lead to creative and feasible plans. The accurate plans generated by this model can then be used to further train the LLM.\n# Pseudo-code\ngpt = GPT()\nidea = gpt.generate_idea()\n\npyhop = Pyhop()\nfeasible = pyhop.find_plan(state, goal_generator())\n\nif feasible:\n    gpt.train(idea)"
   },
   {
-    "objectID": "decisions/20221203-block-direct-pushes-to-main.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20221203-block-direct-pushes-to-main.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Rejected: Blocking direct push to MAIN to avoid build breakage",
+    "objectID": "decisions/20240326-verifying-and-finetuning-plans.html#benefits",
+    "href": "decisions/20240326-verifying-and-finetuning-plans.html#benefits",
+    "title": "Proposed: Teaching Large Language Models (LLMs) with Goal-Task Planners",
     "section": "",
-    "text": "This is a dev ops change."
+    "text": "Innovation: Using LLMs for idea generation can lead to creative ideas.\nPracticality: Passing the generated ideas through a goal-task planner ensures that the plans are innovative but also feasible and executable.\nContinuous Learning: The LLM can learn from the accurate plans, improving its performance over time."
   },
   {
-    "objectID": "decisions/20221203-block-direct-pushes-to-main.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20221203-block-direct-pushes-to-main.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Rejected: Blocking direct push to MAIN to avoid build breakage",
+    "objectID": "decisions/20240326-verifying-and-finetuning-plans.html#downsides",
+    "href": "decisions/20240326-verifying-and-finetuning-plans.html#downsides",
+    "title": "Proposed: Teaching Large Language Models (LLMs) with Goal-Task Planners",
     "section": "",
-    "text": "We own the GitHub repositories."
+    "text": "Computational Overhead: There might be a computational overhead due to the two-step process.\nAccuracy of Feasibility Check: The feasibility check might not always be accurate."
   },
   {
-    "objectID": "decisions/20221203-block-direct-pushes-to-main.html#references",
-    "href": "decisions/20221203-block-direct-pushes-to-main.html#references",
-    "title": "Rejected: Blocking direct push to MAIN to avoid build breakage",
+    "objectID": "decisions/20240326-verifying-and-finetuning-plans.html#road-not-taken",
+    "href": "decisions/20240326-verifying-and-finetuning-plans.html#road-not-taken",
+    "title": "Proposed: Teaching Large Language Models (LLMs) with Goal-Task Planners",
     "section": "",
-    "text": "V-Sekai\nPending head\nGodot Pull request"
+    "text": "An alternative approach could be to run the LLM and the goal-task planner in parallel to address the computational overhead."
   },
   {
-    "objectID": "decisions/20221203-block-direct-pushes-to-main.html#license-of-the-contribution",
-    "href": "decisions/20221203-block-direct-pushes-to-main.html#license-of-the-contribution",
-    "title": "Rejected: Blocking direct push to MAIN to avoid build breakage",
+    "objectID": "decisions/20240326-verifying-and-finetuning-plans.html#infrequent-use-case",
+    "href": "decisions/20240326-verifying-and-finetuning-plans.html#infrequent-use-case",
+    "title": "Proposed: Teaching Large Language Models (LLMs) with Goal-Task Planners",
     "section": "",
-    "text": "Copyright (c) 2022 K. S. Ernest (iFire) Lee\nCopyright (c) 2022 V-Sekai contributors\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "This method may not be suitable for tasks that require immediate results due to the time taken by the two-step process."
   },
   {
-    "objectID": "decisions/20210612-flow-avatar-asset-pipeline.html",
-    "href": "decisions/20210612-flow-avatar-asset-pipeline.html",
-    "title": "Proposed: Convert FBX and glTF2 to VRM via flow-avatar-asset-pipeline",
+    "objectID": "decisions/20240326-verifying-and-finetuning-plans.html#in-core-and-done-by-us",
+    "href": "decisions/20240326-verifying-and-finetuning-plans.html#in-core-and-done-by-us",
+    "title": "Proposed: Teaching Large Language Models (LLMs) with Goal-Task Planners",
     "section": "",
-    "text": "How to convert FBX and glTF2 to VRM?\n\n\n\nIf we can convert FBX and glTF to VRM we have a reliable way of importing things to groups.\n\n\n\nConvert avatar-asset-pipeline to use the membrane framework.\nHave the concept of a source glb we run again as many individual solvers for the input data.\nOnce the input is solved and it passes QA, that is one that is the outputted.\n\n\n\n\nWe have a standard way of importing characters.\nWe already have elixir backend infrastructure.\n\n\n\n\n\nHave no humans in the loop can be bad for quality assurance.\n\n\n\n\n\nOption:\nhttps://github.com/infosia/avatar-asset-pipeline\nRejection Reason:\nNeed to integrate with backend.\n\n\n\n\nNon trivial.\n\n\n\nThis is a core part of Groups and we depend on it.\n\n\n\n\nhttps://github.com/infosia/avatar-asset-pipeline\nhttps://github.com/fire/flow-avatar-asset-pipeline\nhttps://membraneframework.org/\nhttps://github.com/membraneframework/membrane_dashboard\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "The V-Sekai development team will implement this proposal."
   },
   {
-    "objectID": "decisions/20210612-flow-avatar-asset-pipeline.html#context-and-problem-statement",
-    "href": "decisions/20210612-flow-avatar-asset-pipeline.html#context-and-problem-statement",
-    "title": "Proposed: Convert FBX and glTF2 to VRM via flow-avatar-asset-pipeline",
+    "objectID": "decisions/20240326-verifying-and-finetuning-plans.html#status",
+    "href": "decisions/20240326-verifying-and-finetuning-plans.html#status",
+    "title": "Proposed: Teaching Large Language Models (LLMs) with Goal-Task Planners",
     "section": "",
-    "text": "How to convert FBX and glTF2 to VRM?"
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20210612-flow-avatar-asset-pipeline.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20210612-flow-avatar-asset-pipeline.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: Convert FBX and glTF2 to VRM via flow-avatar-asset-pipeline",
+    "objectID": "decisions/20240326-verifying-and-finetuning-plans.html#decision-makers",
+    "href": "decisions/20240326-verifying-and-finetuning-plans.html#decision-makers",
+    "title": "Proposed: Teaching Large Language Models (LLMs) with Goal-Task Planners",
     "section": "",
-    "text": "If we can convert FBX and glTF to VRM we have a reliable way of importing things to groups."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20210612-flow-avatar-asset-pipeline.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20210612-flow-avatar-asset-pipeline.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Convert FBX and glTF2 to VRM via flow-avatar-asset-pipeline",
+    "objectID": "decisions/20240326-verifying-and-finetuning-plans.html#tags",
+    "href": "decisions/20240326-verifying-and-finetuning-plans.html#tags",
+    "title": "Proposed: Teaching Large Language Models (LLMs) with Goal-Task Planners",
     "section": "",
-    "text": "Convert avatar-asset-pipeline to use the membrane framework.\nHave the concept of a source glb we run again as many individual solvers for the input data.\nOnce the input is solved and it passes QA, that is one that is the outputted."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20210612-flow-avatar-asset-pipeline.html#positive-consequences",
-    "href": "decisions/20210612-flow-avatar-asset-pipeline.html#positive-consequences",
-    "title": "Proposed: Convert FBX and glTF2 to VRM via flow-avatar-asset-pipeline",
+    "objectID": "decisions/20240326-verifying-and-finetuning-plans.html#further-reading",
+    "href": "decisions/20240326-verifying-and-finetuning-plans.html#further-reading",
+    "title": "Proposed: Teaching Large Language Models (LLMs) with Goal-Task Planners",
     "section": "",
-    "text": "We have a standard way of importing characters.\nWe already have elixir backend infrastructure."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nLLMs Can’t Plan, But Can Help Planning in LLM-Modulo Frameworks\n\nAI assistant Aria assisted with this feedback."
   },
   {
-    "objectID": "decisions/20210612-flow-avatar-asset-pipeline.html#negative-consequences",
-    "href": "decisions/20210612-flow-avatar-asset-pipeline.html#negative-consequences",
-    "title": "Proposed: Convert FBX and glTF2 to VRM via flow-avatar-asset-pipeline",
+    "objectID": "decisions/20230623-fdn-reverb-solution.html",
+    "href": "decisions/20230623-fdn-reverb-solution.html",
+    "title": "Proposed: Implementing Feedback Delay Networks for Enhanced Audio Reverb Simulation in V-Sekai",
     "section": "",
-    "text": "Have no humans in the loop can be bad for quality assurance."
+    "text": "Status: proposed\nDeciders: V-Sekai, ellenhp, fire\nTags: V-Sekai, ai assisted\n\n\n\n\nThe problem of simulating audio reverb in Godot Engine 4 involves accurately modeling the way sound waves propagate, reflect, and interact within a given environment. This requires sampling a chaotic 7-dimensional space every frame, either through precomputation or real-time processing. The complexity arises from the fact that sound behaves more like light with intense diffraction, making it impossible to rasterize.\n\n\n\nImplement Feedback Delay Networks (FDNs) for artificial reverberation. FDNs consist of multiple delay lines connected in a feedback loop with a mixing matrix. The output is a combination of the input signal and the delayed signals.\n\n\n\nChoose the number of delay lines and their lengths based on the desired reverberation time and room characteristics.\nImplement a mixing matrix to control the energy distribution between the delay lines.\nCreate a feedback loop by connecting the outputs of the delay lines to the inputs through the mixing matrix.\nCombine the input signal with the delayed signals to produce the reverberated output.\n\n\n\n\n\nclass_name FDN\nextends Node\n\nvar num_delay_lines : int\nvar delay_lines : Array\nvar mixing_matrix : Array\nvar room_characteristics : Dictionary\n\nfunc _init(num_delay_lines: int, delay_lengths: Array, mixing_matrix: Array, room_characteristics: Dictionary):\n    self.num_delay_lines = num_delay_lines\n    self.delay_lines = []\n    for length in delay_lengths:\n        self.delay_lines.append(DelayLine.new(length))\n    self.mixing_matrix = mixing_matrix\n    self.room_characteristics = room_characteristics\n\nfunc process(input_signal: float) -&gt; float:\n    # Step 1: Calculate the output of each delay line\n    var delay_outputs = []\n    for dl in self.delay_lines:\n        delay_outputs.append(dl.process(input_signal))\n\n    # Step 2: Apply the room characteristics to the delay line outputs\n    var processed_outputs = apply_room_characteristics(delay_outputs)\n\n    # Step 3: Apply the mixing matrix to the processed delay line outputs\n    var mixed_outputs = apply_mixing_matrix(processed_outputs)\n\n    # Step 4: Update the delay lines with the mixed outputs\n    for i in range(self.num_delay_lines):\n        self.delay_lines[i].update(mixed_outputs[i])\n\n    # Step 5: Combine the input signal with the delayed signals\n    var output_signal = input_signal + sum(mixed_outputs)\n    return output_signal\n\nfunc apply_room_characteristics(delay_outputs: Array) -&gt; Array:\n    var processed_outputs = []\n    for i in range(len(delay_outputs)):\n        processed_output = delay_outputs[i] * room_characteristics[\"absorption\"][i]\n        processed_outputs.append(processed_output)\n    return processed_outputs\n\nfunc apply_mixing_matrix(delay_outputs: Array) -&gt; Array:\n    # TODO: Implement the mixing matrix application logic\n    pass\n\n\n\n\nImproved audio reverb simulation\nMore realistic sound propagation and interaction within environments\nSmarter estimation of long reverb times\n\n\n\n\n\nIncreased computational complexity\nPotential performance impact on real-time processing\n\n\n\n\n\nGeneralized Dijkstra Pathfinding\nDWN (Digital Waveguide Network): A method for simulating audio reverb by modeling sound propagation as waves traveling along waveguides with bidirectional delay lines and scattering junctions.\nRay tracing can be used to simulate sound propagation in 3D environments. It involves casting rays from the sound source and tracing their paths as they interact with the environment (reflect, refract, and diffract). By calculating the time delay and attenuation of each ray reaching the listener, you can generate an impulse response that represents the acoustic properties of the space.\nConvolution reverb is a technique that uses recorded impulse responses (IRs) of real spaces or digital simulations to recreate the reverberation characteristics of those spaces. The process involves convolving the dry audio signal with the impulse response to produce the reverberated audio.\n\n\n\n\nNo, implementing FDNs requires a more complex algorithm and cannot be achieved with just a few lines of script.\n\n\n\nYes, as it directly impacts the audio experience within V-Sekai environments, it should be a core feature to ensure consistent and high-quality audio reverb simulation.\n\n\n\n\nV-Sekai: A virtual reality platform that allows users to create and explore immersive environments.\nGodot Engine 4: An open-source game engine used for creating 2D and 3D games and interactive applications.\nAudio Reverb: The persistence of sound in a particular space after the original sound has stopped, caused by reflections off surfaces within the environment.\nFeedback Delay Networks (FDNs): A method for simulating artificial reverberation using multiple delay lines connected in a feedback loop with a mixing matrix.\nDelay Line: A digital signal processing technique that introduces a time delay to an input signal, often used in audio effects such as reverb and echo.\nMixing Matrix: A mathematical construct used to control the energy distribution between the delay lines in an FDN.\nRoom Characteristics: Acoustic properties of a room or environment, such as absorption, reflection, and diffusion, which affect how sound propagates within the space.\nReverberation Time: The time it takes for the sound level in a room to decrease by 60 decibels after the sound source has stopped.\nDigital Waveguide Network (DWN): An alternative method for simulating audio reverb by modeling sound propagation as waves traveling along waveguides with bidirectional delay lines and scattering junctions.\nRay Tracing: A technique used to simulate sound propagation in 3D environments by casting rays from the sound source and tracing their paths as they interact with the environment (reflect, refract, and diffract).\nConvolution Reverb: A technique that uses recorded impulse responses (IRs) of real spaces or digital simulations to recreate the reverberation characteristics of those spaces by convolving the dry audio signal with the impulse response.\nImpulse Response (IR): A recording or simulation of the acoustic properties of a space, used in convolution reverb to recreate the reverberation characteristics of that space.\n\n\n\n\nLet’s consider an example of implementing a Feedback Delay Network (FDN) for audio reverb simulation with 8 delay lines. We will analyze the computational and I/O complexity involved in this specific case.\n\n\n\nFor a medium-quality reverb effect, let’s consider using 8 delay lines in the FDN.\nFor an 8x8 matrix, there are 64 multiplications and 56 additions required for each sample.\nOverall, the computational complexity for a medium-quality reverb effect with 8 delay lines is manageable for most modern CPUs and can be efficiently processed in real-time.\nIn summary, implementing a medium-quality reverb effect using an FDN with 8 delay lines has a manageable computational and I/O complexity, making it suitable for real-time processing on most modern hardware.\n\n\n\n\nFor a medium-quality reverb effect, let’s consider using 8 delay lines in the FDN. The main components contributing to the computational complexity are:\n\nDelay Lines: Each delay line requires memory for storing the delayed samples and computations for updating the delay buffer. For 8 delay lines, the complexity scales linearly with the number of delay lines.\nMatrix Mixing: The mixing matrix combines the outputs of the delay lines in a specific way to create the desired reverb effect. For an 8x8 matrix, there are 64 multiplications and 56 additions required for each sample.\nFeedback and Input/Output Processing: Additional processing, such as filtering or gain adjustments, may be applied to the input, output, or feedback paths. This complexity depends on the specific filters or processing used but is generally proportional to the number of delay lines.\n\nOverall, the computational complexity for a medium-quality reverb effect with 8 delay lines is manageable for most modern CPUs and can be efficiently processed in real-time.\n\n\n\nThe I/O complexity refers to the amount of data that needs to be read from and written to memory during the processing of the reverb effect. In the case of an FDN with 8 delay lines, the I/O complexity is mainly determined by:\n\nReading and Writing Delay Line Buffers: Each delay line requires reading and writing operations for updating the delay buffer. The I/O complexity scales linearly with the number of delay lines.\nInput and Output Audio Data: The audio input data must be read, processed, and combined with the output of the FDN to generate the final reverberated audio signal. The I/O complexity for input and output audio data is generally low compared to the delay line buffer operations.\n\nIn summary, implementing a medium-quality reverb effect using an FDN with 8 delay lines has a manageable computational and I/O complexity, making it suitable for real-time processing on most modern hardware."
   },
   {
-    "objectID": "decisions/20210612-flow-avatar-asset-pipeline.html#option-graveyard",
-    "href": "decisions/20210612-flow-avatar-asset-pipeline.html#option-graveyard",
-    "title": "Proposed: Convert FBX and glTF2 to VRM via flow-avatar-asset-pipeline",
+    "objectID": "decisions/20230623-fdn-reverb-solution.html#metadata",
+    "href": "decisions/20230623-fdn-reverb-solution.html#metadata",
+    "title": "Proposed: Implementing Feedback Delay Networks for Enhanced Audio Reverb Simulation in V-Sekai",
     "section": "",
-    "text": "Option:\nhttps://github.com/infosia/avatar-asset-pipeline\nRejection Reason:\nNeed to integrate with backend."
+    "text": "Status: proposed\nDeciders: V-Sekai, ellenhp, fire\nTags: V-Sekai, ai assisted"
   },
   {
-    "objectID": "decisions/20210612-flow-avatar-asset-pipeline.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20210612-flow-avatar-asset-pipeline.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Convert FBX and glTF2 to VRM via flow-avatar-asset-pipeline",
+    "objectID": "decisions/20230623-fdn-reverb-solution.html#context-and-problem-statement",
+    "href": "decisions/20230623-fdn-reverb-solution.html#context-and-problem-statement",
+    "title": "Proposed: Implementing Feedback Delay Networks for Enhanced Audio Reverb Simulation in V-Sekai",
     "section": "",
-    "text": "Non trivial."
+    "text": "The problem of simulating audio reverb in Godot Engine 4 involves accurately modeling the way sound waves propagate, reflect, and interact within a given environment. This requires sampling a chaotic 7-dimensional space every frame, either through precomputation or real-time processing. The complexity arises from the fact that sound behaves more like light with intense diffraction, making it impossible to rasterize."
   },
   {
-    "objectID": "decisions/20210612-flow-avatar-asset-pipeline.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20210612-flow-avatar-asset-pipeline.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Convert FBX and glTF2 to VRM via flow-avatar-asset-pipeline",
+    "objectID": "decisions/20230623-fdn-reverb-solution.html#proposed-solution",
+    "href": "decisions/20230623-fdn-reverb-solution.html#proposed-solution",
+    "title": "Proposed: Implementing Feedback Delay Networks for Enhanced Audio Reverb Simulation in V-Sekai",
     "section": "",
-    "text": "This is a core part of Groups and we depend on it."
+    "text": "Implement Feedback Delay Networks (FDNs) for artificial reverberation. FDNs consist of multiple delay lines connected in a feedback loop with a mixing matrix. The output is a combination of the input signal and the delayed signals.\n\n\n\nChoose the number of delay lines and their lengths based on the desired reverberation time and room characteristics.\nImplement a mixing matrix to control the energy distribution between the delay lines.\nCreate a feedback loop by connecting the outputs of the delay lines to the inputs through the mixing matrix.\nCombine the input signal with the delayed signals to produce the reverberated output."
   },
   {
-    "objectID": "decisions/20210612-flow-avatar-asset-pipeline.html#references",
-    "href": "decisions/20210612-flow-avatar-asset-pipeline.html#references",
-    "title": "Proposed: Convert FBX and glTF2 to VRM via flow-avatar-asset-pipeline",
+    "objectID": "decisions/20230623-fdn-reverb-solution.html#implementation",
+    "href": "decisions/20230623-fdn-reverb-solution.html#implementation",
+    "title": "Proposed: Implementing Feedback Delay Networks for Enhanced Audio Reverb Simulation in V-Sekai",
     "section": "",
-    "text": "https://github.com/infosia/avatar-asset-pipeline\nhttps://github.com/fire/flow-avatar-asset-pipeline\nhttps://membraneframework.org/\nhttps://github.com/membraneframework/membrane_dashboard"
+    "text": "class_name FDN\nextends Node\n\nvar num_delay_lines : int\nvar delay_lines : Array\nvar mixing_matrix : Array\nvar room_characteristics : Dictionary\n\nfunc _init(num_delay_lines: int, delay_lengths: Array, mixing_matrix: Array, room_characteristics: Dictionary):\n    self.num_delay_lines = num_delay_lines\n    self.delay_lines = []\n    for length in delay_lengths:\n        self.delay_lines.append(DelayLine.new(length))\n    self.mixing_matrix = mixing_matrix\n    self.room_characteristics = room_characteristics\n\nfunc process(input_signal: float) -&gt; float:\n    # Step 1: Calculate the output of each delay line\n    var delay_outputs = []\n    for dl in self.delay_lines:\n        delay_outputs.append(dl.process(input_signal))\n\n    # Step 2: Apply the room characteristics to the delay line outputs\n    var processed_outputs = apply_room_characteristics(delay_outputs)\n\n    # Step 3: Apply the mixing matrix to the processed delay line outputs\n    var mixed_outputs = apply_mixing_matrix(processed_outputs)\n\n    # Step 4: Update the delay lines with the mixed outputs\n    for i in range(self.num_delay_lines):\n        self.delay_lines[i].update(mixed_outputs[i])\n\n    # Step 5: Combine the input signal with the delayed signals\n    var output_signal = input_signal + sum(mixed_outputs)\n    return output_signal\n\nfunc apply_room_characteristics(delay_outputs: Array) -&gt; Array:\n    var processed_outputs = []\n    for i in range(len(delay_outputs)):\n        processed_output = delay_outputs[i] * room_characteristics[\"absorption\"][i]\n        processed_outputs.append(processed_output)\n    return processed_outputs\n\nfunc apply_mixing_matrix(delay_outputs: Array) -&gt; Array:\n    # TODO: Implement the mixing matrix application logic\n    pass"
   },
   {
-    "objectID": "decisions/20210612-flow-avatar-asset-pipeline.html#derivative-license",
-    "href": "decisions/20210612-flow-avatar-asset-pipeline.html#derivative-license",
-    "title": "Proposed: Convert FBX and glTF2 to VRM via flow-avatar-asset-pipeline",
+    "objectID": "decisions/20230623-fdn-reverb-solution.html#positive-consequences",
+    "href": "decisions/20230623-fdn-reverb-solution.html#positive-consequences",
+    "title": "Proposed: Implementing Feedback Delay Networks for Enhanced Audio Reverb Simulation in V-Sekai",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Improved audio reverb simulation\nMore realistic sound propagation and interaction within environments\nSmarter estimation of long reverb times"
   },
   {
-    "objectID": "decisions/20211031-play-preprocessed-animations-on-any-vrm-model.html",
-    "href": "decisions/20211031-play-preprocessed-animations-on-any-vrm-model.html",
-    "title": "Superseded: Play preprocessed #animation on any VRM model",
+    "objectID": "decisions/20230623-fdn-reverb-solution.html#negative-consequences",
+    "href": "decisions/20230623-fdn-reverb-solution.html#negative-consequences",
+    "title": "Proposed: Implementing Feedback Delay Networks for Enhanced Audio Reverb Simulation in V-Sekai",
     "section": "",
-    "text": "Superseded: Play preprocessed #animation on any VRM model\nSuperseded\nThis is now a Godot Engine 4.0 core feature. https://godotengine.org/article/animation-retargeting-in-godot-4-0/\n\nContext and Problem Statement\nGiven any vrm and a carefully made animation, we should be able to play back the animation.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nNeed to work out a flow for making #animation play back on vrm.\nThis is dependency for a VRM based character controller that can play existing #animation clips and blend them\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n???\nCollaborate with Saracen on a bone roll corrected VRM skeleton.\nConvert #animation to VRM named bones.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot trivial.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nWe control the default #animation tree, therefore we need to do this.\n\n\nReferences\n\nProposal on baking blend shapes to linear skin blending.\nUseful for tokage’s character movement demo. https://github.com/TokageItLab/3d-platform-test-for-godot4\nFree #animation – https://github.com/V-Sekai/shadermotion-video-to-anims\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Increased computational complexity\nPotential performance impact on real-time processing"
   },
   {
-    "objectID": "decisions/20230123-no-traversal-loading-screen.html",
-    "href": "decisions/20230123-no-traversal-loading-screen.html",
-    "title": "Proposed: No traversal loading screen",
+    "objectID": "decisions/20230623-fdn-reverb-solution.html#option-graveyard",
+    "href": "decisions/20230623-fdn-reverb-solution.html#option-graveyard",
+    "title": "Proposed: Implementing Feedback Delay Networks for Enhanced Audio Reverb Simulation in V-Sekai",
     "section": "",
-    "text": "Proposed: No traversal loading screen\n\nMetadata\n\nStatus: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nContext and Problem Statement\nThis is a proposal to mask the loading time, but it doesn’t solve it.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nTrim the steps needed to enter the game.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nWhen you first start up the application, you will see a loading screen. This screen will be displayed until all the assets needed to load your world have been downloaded.\nWhen switching between worlds, there is technically no need for a loading screen. Both leading platforms have chosen to include one in their applications, but this is not necessary. The leading platform displays a loading screen when clicking to go to a new world, while the secondary leading platform does not display one–you stay in your original world while also loading into the second world and then switch over once enough of it has been downloaded that you can be there.\nYou click go and are left in your current world while loading in the other world, once the other world is completely loaded in you are transported to it instantaneously.\n\n\nPositive Consequences\nAble to mask loading times\nAble to direct players to the positive parts of v-sekai\nFor style points we could enforce portals that seamlessly transport you between different worlds, at least, as the default option, you place a portal, it has a camera, and you can walk through it, and after a certain point it disappears.\n\n\nNegative Consequences\ncoordinating cats\nThe drawback to the multi-world load is that it is more resource intensive, though it should only last a short while, so if we do go that route it should be an option to use a loading screen instead.\nIt makes for a far less friction-less experience\nBut again, resource intensive issues, so will have to be optional\nWe could even add a little button you click once you are ready to be transported, so it doesn’t happen against your will if your trying to say something last minute.\n\n\nOption graveyard\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot script.\n\n\nIs there a reason why this should be core and done by us?\nWorld traversal is a problem.\n\n\nReferences\n\nV-Sekai\n\n\n\nLicense of the contribution\nMIT License\n\nCopyright (c) 2018-present SaracenOne\nCopyright (c) 2019-present K. S. Ernest (iFire) Lee (fire)\nCopyright (c) 2020-present Lyuma\nCopyright (c) 2020-present MMMaellon\nCopyright (c) 2022-present See authors.md\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
+    "text": "Generalized Dijkstra Pathfinding\nDWN (Digital Waveguide Network): A method for simulating audio reverb by modeling sound propagation as waves traveling along waveguides with bidirectional delay lines and scattering junctions.\nRay tracing can be used to simulate sound propagation in 3D environments. It involves casting rays from the sound source and tracing their paths as they interact with the environment (reflect, refract, and diffract). By calculating the time delay and attenuation of each ray reaching the listener, you can generate an impulse response that represents the acoustic properties of the space.\nConvolution reverb is a technique that uses recorded impulse responses (IRs) of real spaces or digital simulations to recreate the reverberation characteristics of those spaces. The process involves convolving the dry audio signal with the impulse response to produce the reverberated audio."
   },
   {
-    "objectID": "decisions/20230527-godot-test-game.html",
-    "href": "decisions/20230527-godot-test-game.html",
-    "title": "Proposed: Create a 12x12 meter 3D demo map with 2-meter-high obstacles and walls",
+    "objectID": "decisions/20230623-fdn-reverb-solution.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230623-fdn-reverb-solution.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Implementing Feedback Delay Networks for Enhanced Audio Reverb Simulation in V-Sekai",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, GPT-4\n\n\n\n\nV-Sekai users struggle navigating complex 3D environments with obstacles and walls, limiting user experience and potential applications.\n\n\n\nCreate a 12x12 meter 3D map with 2-meter-high obstacles and walls. Implement a navigation system for users to move around while avoiding obstacles and walls.\n\n\n\n\nDesign the 3D map using modeling software (e.g., Blender).\nImport the map into a game engine.\nImplement a character controller for navigation.\nAdd collision detection and response.\nOptimize navigation system performance.\n\n\n\n\n\nImproved user experience.\nIncreased V-Sekai applications.\nEnhanced immersion.\n\n\n\n\n\nAdditional development time and resources.\nPotential performance issues if not optimized.\n\n\n\n\n\nUsing pre-built navigation systems.\nIgnoring the limitation.\n\n\n\n\nNo simple workaround; complex implementation required for seamless user experience.\n\n\n\nImproving navigation is essential for enhancing user experience and expanding V-Sekai’s potential applications.\n\n\n\n\nV-Sekai"
+    "text": "No, implementing FDNs requires a more complex algorithm and cannot be achieved with just a few lines of script."
   },
   {
-    "objectID": "decisions/20230527-godot-test-game.html#metadata",
-    "href": "decisions/20230527-godot-test-game.html#metadata",
-    "title": "Proposed: Create a 12x12 meter 3D demo map with 2-meter-high obstacles and walls",
+    "objectID": "decisions/20230623-fdn-reverb-solution.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230623-fdn-reverb-solution.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Implementing Feedback Delay Networks for Enhanced Audio Reverb Simulation in V-Sekai",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, GPT-4"
+    "text": "Yes, as it directly impacts the audio experience within V-Sekai environments, it should be a core feature to ensure consistent and high-quality audio reverb simulation."
   },
   {
-    "objectID": "decisions/20230527-godot-test-game.html#problem-statement",
-    "href": "decisions/20230527-godot-test-game.html#problem-statement",
-    "title": "Proposed: Create a 12x12 meter 3D demo map with 2-meter-high obstacles and walls",
+    "objectID": "decisions/20230623-fdn-reverb-solution.html#glossary-implementing-feedback-delay-networks-for-enhanced-audio-reverb-simulation-in-v-sekai",
+    "href": "decisions/20230623-fdn-reverb-solution.html#glossary-implementing-feedback-delay-networks-for-enhanced-audio-reverb-simulation-in-v-sekai",
+    "title": "Proposed: Implementing Feedback Delay Networks for Enhanced Audio Reverb Simulation in V-Sekai",
     "section": "",
-    "text": "V-Sekai users struggle navigating complex 3D environments with obstacles and walls, limiting user experience and potential applications."
+    "text": "V-Sekai: A virtual reality platform that allows users to create and explore immersive environments.\nGodot Engine 4: An open-source game engine used for creating 2D and 3D games and interactive applications.\nAudio Reverb: The persistence of sound in a particular space after the original sound has stopped, caused by reflections off surfaces within the environment.\nFeedback Delay Networks (FDNs): A method for simulating artificial reverberation using multiple delay lines connected in a feedback loop with a mixing matrix.\nDelay Line: A digital signal processing technique that introduces a time delay to an input signal, often used in audio effects such as reverb and echo.\nMixing Matrix: A mathematical construct used to control the energy distribution between the delay lines in an FDN.\nRoom Characteristics: Acoustic properties of a room or environment, such as absorption, reflection, and diffusion, which affect how sound propagates within the space.\nReverberation Time: The time it takes for the sound level in a room to decrease by 60 decibels after the sound source has stopped.\nDigital Waveguide Network (DWN): An alternative method for simulating audio reverb by modeling sound propagation as waves traveling along waveguides with bidirectional delay lines and scattering junctions.\nRay Tracing: A technique used to simulate sound propagation in 3D environments by casting rays from the sound source and tracing their paths as they interact with the environment (reflect, refract, and diffract).\nConvolution Reverb: A technique that uses recorded impulse responses (IRs) of real spaces or digital simulations to recreate the reverberation characteristics of those spaces by convolving the dry audio signal with the impulse response.\nImpulse Response (IR): A recording or simulation of the acoustic properties of a space, used in convolution reverb to recreate the reverberation characteristics of that space."
   },
   {
-    "objectID": "decisions/20230527-godot-test-game.html#proposed-solution",
-    "href": "decisions/20230527-godot-test-game.html#proposed-solution",
-    "title": "Proposed: Create a 12x12 meter 3D demo map with 2-meter-high obstacles and walls",
+    "objectID": "decisions/20230623-fdn-reverb-solution.html#computational-and-io-complexity-an-example",
+    "href": "decisions/20230623-fdn-reverb-solution.html#computational-and-io-complexity-an-example",
+    "title": "Proposed: Implementing Feedback Delay Networks for Enhanced Audio Reverb Simulation in V-Sekai",
     "section": "",
-    "text": "Create a 12x12 meter 3D map with 2-meter-high obstacles and walls. Implement a navigation system for users to move around while avoiding obstacles and walls."
+    "text": "Let’s consider an example of implementing a Feedback Delay Network (FDN) for audio reverb simulation with 8 delay lines. We will analyze the computational and I/O complexity involved in this specific case.\n\n\n\nFor a medium-quality reverb effect, let’s consider using 8 delay lines in the FDN.\nFor an 8x8 matrix, there are 64 multiplications and 56 additions required for each sample.\nOverall, the computational complexity for a medium-quality reverb effect with 8 delay lines is manageable for most modern CPUs and can be efficiently processed in real-time.\nIn summary, implementing a medium-quality reverb effect using an FDN with 8 delay lines has a manageable computational and I/O complexity, making it suitable for real-time processing on most modern hardware.\n\n\n\n\nFor a medium-quality reverb effect, let’s consider using 8 delay lines in the FDN. The main components contributing to the computational complexity are:\n\nDelay Lines: Each delay line requires memory for storing the delayed samples and computations for updating the delay buffer. For 8 delay lines, the complexity scales linearly with the number of delay lines.\nMatrix Mixing: The mixing matrix combines the outputs of the delay lines in a specific way to create the desired reverb effect. For an 8x8 matrix, there are 64 multiplications and 56 additions required for each sample.\nFeedback and Input/Output Processing: Additional processing, such as filtering or gain adjustments, may be applied to the input, output, or feedback paths. This complexity depends on the specific filters or processing used but is generally proportional to the number of delay lines.\n\nOverall, the computational complexity for a medium-quality reverb effect with 8 delay lines is manageable for most modern CPUs and can be efficiently processed in real-time.\n\n\n\nThe I/O complexity refers to the amount of data that needs to be read from and written to memory during the processing of the reverb effect. In the case of an FDN with 8 delay lines, the I/O complexity is mainly determined by:\n\nReading and Writing Delay Line Buffers: Each delay line requires reading and writing operations for updating the delay buffer. The I/O complexity scales linearly with the number of delay lines.\nInput and Output Audio Data: The audio input data must be read, processed, and combined with the output of the FDN to generate the final reverberated audio signal. The I/O complexity for input and output audio data is generally low compared to the delay line buffer operations.\n\nIn summary, implementing a medium-quality reverb effect using an FDN with 8 delay lines has a manageable computational and I/O complexity, making it suitable for real-time processing on most modern hardware."
   },
   {
-    "objectID": "decisions/20230527-godot-test-game.html#implementation",
-    "href": "decisions/20230527-godot-test-game.html#implementation",
-    "title": "Proposed: Create a 12x12 meter 3D demo map with 2-meter-high obstacles and walls",
+    "objectID": "decisions/20230507-supabase.html",
+    "href": "decisions/20230507-supabase.html",
+    "title": "Rejected: Using Deno to handle the conversion of GLB files to Godot Engine packed scenes",
     "section": "",
-    "text": "Design the 3D map using modeling software (e.g., Blender).\nImport the map into a game engine.\nImplement a character controller for navigation.\nAdd collision detection and response.\nOptimize navigation system performance."
+    "text": "Status: rejected \nDeciders: V-Sekai\nTags: V-Sekai, ChatGPT-4\n\n\n\n\nV-Sekai currently has a limitation in converting 3D models from the GLB format to the Godot Engine packed scene format. This conversion process is essential for seamless integration of 3D assets into the V-Sekai platform.\n\n\n\nImplement serverless edge functions using Deno to handle the conversion of GLB files to Godot Engine packed scenes and manage data storage and retrieval.\n\n\n\n\nWasm edge functions: Utilize WebAssembly (Wasm) to run the edge functions efficiently.\nCompute time estimation: Estimate the required compute time for the conversion process.\nData storage: Set up a storage system for the converted Godot packed scenes.\nTable editing UI: Create a user interface for managing the stored Godot packed scenes.\nEdge Function use case: Implement the following serverless Deno functions:\n\nglbToGodotPackedScene: Convert a GLB file to a Godot packed scene and store it.\ninsertGodotPackedScene: Insert a Godot packed scene into the V-Sekai server.\nhelloWorld: Return a JSON object containing “Hello, World!” as a test function.\n\n\n\n\n\n\nSeamless integration of 3D assets into the V-Sekai platform.\nImproved performance and reduced latency due to edge computing.\nScalable and maintainable architecture with serverless functions.\n\n\n\n\n\nAdditional complexity in setting up and managing serverless functions.\nPotential increase in costs due to serverless architecture.\n\n\n\n\nUse the current process of editor upload.\n\n\n\nNo, this enhancement is essential for the seamless integration of 3D assets into the V-Sekai platform and cannot be easily worked around with a simple script.\n\n\n\nYes, this feature is crucial for the V-Sekai platform’s functionality and user experience. Implementing it as a core feature ensures that it is well-integrated, maintainable, and scalable.\n\n\n\n\nV-Sekai"
   },
   {
-    "objectID": "decisions/20230527-godot-test-game.html#positive-consequences",
-    "href": "decisions/20230527-godot-test-game.html#positive-consequences",
-    "title": "Proposed: Create a 12x12 meter 3D demo map with 2-meter-high obstacles and walls",
+    "objectID": "decisions/20230507-supabase.html#metadata",
+    "href": "decisions/20230507-supabase.html#metadata",
+    "title": "Rejected: Using Deno to handle the conversion of GLB files to Godot Engine packed scenes",
     "section": "",
-    "text": "Improved user experience.\nIncreased V-Sekai applications.\nEnhanced immersion."
+    "text": "Status: rejected \nDeciders: V-Sekai\nTags: V-Sekai, ChatGPT-4"
   },
   {
-    "objectID": "decisions/20230527-godot-test-game.html#negative-consequences",
-    "href": "decisions/20230527-godot-test-game.html#negative-consequences",
-    "title": "Proposed: Create a 12x12 meter 3D demo map with 2-meter-high obstacles and walls",
+    "objectID": "decisions/20230507-supabase.html#context-and-problem-statement",
+    "href": "decisions/20230507-supabase.html#context-and-problem-statement",
+    "title": "Rejected: Using Deno to handle the conversion of GLB files to Godot Engine packed scenes",
     "section": "",
-    "text": "Additional development time and resources.\nPotential performance issues if not optimized."
+    "text": "V-Sekai currently has a limitation in converting 3D models from the GLB format to the Godot Engine packed scene format. This conversion process is essential for seamless integration of 3D assets into the V-Sekai platform."
   },
   {
-    "objectID": "decisions/20230527-godot-test-game.html#option-graveyard",
-    "href": "decisions/20230527-godot-test-game.html#option-graveyard",
-    "title": "Proposed: Create a 12x12 meter 3D demo map with 2-meter-high obstacles and walls",
+    "objectID": "decisions/20230507-supabase.html#proposed-solution",
+    "href": "decisions/20230507-supabase.html#proposed-solution",
+    "title": "Rejected: Using Deno to handle the conversion of GLB files to Godot Engine packed scenes",
     "section": "",
-    "text": "Using pre-built navigation systems.\nIgnoring the limitation."
+    "text": "Implement serverless edge functions using Deno to handle the conversion of GLB files to Godot Engine packed scenes and manage data storage and retrieval."
   },
   {
-    "objectID": "decisions/20230527-godot-test-game.html#enhancement-workaround",
-    "href": "decisions/20230527-godot-test-game.html#enhancement-workaround",
-    "title": "Proposed: Create a 12x12 meter 3D demo map with 2-meter-high obstacles and walls",
+    "objectID": "decisions/20230507-supabase.html#implementation",
+    "href": "decisions/20230507-supabase.html#implementation",
+    "title": "Rejected: Using Deno to handle the conversion of GLB files to Godot Engine packed scenes",
     "section": "",
-    "text": "No simple workaround; complex implementation required for seamless user experience."
+    "text": "Wasm edge functions: Utilize WebAssembly (Wasm) to run the edge functions efficiently.\nCompute time estimation: Estimate the required compute time for the conversion process.\nData storage: Set up a storage system for the converted Godot packed scenes.\nTable editing UI: Create a user interface for managing the stored Godot packed scenes.\nEdge Function use case: Implement the following serverless Deno functions:\n\nglbToGodotPackedScene: Convert a GLB file to a Godot packed scene and store it.\ninsertGodotPackedScene: Insert a Godot packed scene into the V-Sekai server.\nhelloWorld: Return a JSON object containing “Hello, World!” as a test function."
   },
   {
-    "objectID": "decisions/20230527-godot-test-game.html#core-reasoning",
-    "href": "decisions/20230527-godot-test-game.html#core-reasoning",
-    "title": "Proposed: Create a 12x12 meter 3D demo map with 2-meter-high obstacles and walls",
+    "objectID": "decisions/20230507-supabase.html#positive-consequences",
+    "href": "decisions/20230507-supabase.html#positive-consequences",
+    "title": "Rejected: Using Deno to handle the conversion of GLB files to Godot Engine packed scenes",
     "section": "",
-    "text": "Improving navigation is essential for enhancing user experience and expanding V-Sekai’s potential applications."
+    "text": "Seamless integration of 3D assets into the V-Sekai platform.\nImproved performance and reduced latency due to edge computing.\nScalable and maintainable architecture with serverless functions."
   },
   {
-    "objectID": "decisions/20230527-godot-test-game.html#references",
-    "href": "decisions/20230527-godot-test-game.html#references",
-    "title": "Proposed: Create a 12x12 meter 3D demo map with 2-meter-high obstacles and walls",
+    "objectID": "decisions/20230507-supabase.html#negative-consequences",
+    "href": "decisions/20230507-supabase.html#negative-consequences",
+    "title": "Rejected: Using Deno to handle the conversion of GLB files to Godot Engine packed scenes",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Additional complexity in setting up and managing serverless functions.\nPotential increase in costs due to serverless architecture."
   },
   {
-    "objectID": "decisions/20231108-ansible-new-server-provisioning.html",
-    "href": "decisions/20231108-ansible-new-server-provisioning.html",
-    "title": "Proposed: Ansible Server Provisioning",
+    "objectID": "decisions/20230507-supabase.html#option-graveyard",
+    "href": "decisions/20230507-supabase.html#option-graveyard",
+    "title": "Rejected: Using Deno to handle the conversion of GLB files to Godot Engine packed scenes",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nIn the world of DevOps, server provisioning is a critical task. It involves setting up a server to a particular specification. This includes installing an operating system, software packages, and configuring settings.\n\n\n\nThe challenge lies in choosing the right configuration management tool for a small project. Factors such as ease of use, scalability, and community support are crucial.\n\n\n\nBased on these parameters, Ansible emerges as a strong contender. Its simple syntax written in YAML makes it easy to understand even for those new to automation. Being agentless, it’s easier to manage and scale. Moreover, Ansible has a large and active community, providing plenty of resources and support.\n# Sample Ansible playbook\n---\n- hosts: webservers\n  tasks:\n    - name: ensure apache is at the latest version\n      yum:\n        name: httpd\n        state: latest\n\n\n\nChoosing Ansible can simplify server provisioning due to its simplicity and ease of use. It doesn’t require any special coding skills, making it accessible for beginners.\n\n\n\nWhile Ansible is powerful and user-friendly, it may not be as feature-rich as some other tools like Chef or Puppet. However, for a small project, this might not be a significant concern.\n\n\n\nOther tools like Chef, Puppet, and SaltStack were also considered. While they all have their strengths, they may not be as beginner-friendly as Ansible.\n\n\n\nFor complex infrastructures or specific use cases, other tools might be more suitable. It’s always a good idea to try out different tools before making a decision.\n\n\n\nThe decision to use Ansible for server provisioning is proposed by V-Sekai.\n\n\n\n\nV-Sekai\nAnsible Tower: FAQ\n\nThis article was assisted by Aria, an AI."
+    "text": "Use the current process of editor upload."
   },
   {
-    "objectID": "decisions/20231108-ansible-new-server-provisioning.html#metadata",
-    "href": "decisions/20231108-ansible-new-server-provisioning.html#metadata",
-    "title": "Proposed: Ansible Server Provisioning",
+    "objectID": "decisions/20230507-supabase.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230507-supabase.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Rejected: Using Deno to handle the conversion of GLB files to Godot Engine packed scenes",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai"
+    "text": "No, this enhancement is essential for the seamless integration of 3D assets into the V-Sekai platform and cannot be easily worked around with a simple script."
   },
   {
-    "objectID": "decisions/20231108-ansible-new-server-provisioning.html#the-backdrop",
-    "href": "decisions/20231108-ansible-new-server-provisioning.html#the-backdrop",
-    "title": "Proposed: Ansible Server Provisioning",
+    "objectID": "decisions/20230507-supabase.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230507-supabase.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Rejected: Using Deno to handle the conversion of GLB files to Godot Engine packed scenes",
     "section": "",
-    "text": "In the world of DevOps, server provisioning is a critical task. It involves setting up a server to a particular specification. This includes installing an operating system, software packages, and configuring settings."
+    "text": "Yes, this feature is crucial for the V-Sekai platform’s functionality and user experience. Implementing it as a core feature ensures that it is well-integrated, maintainable, and scalable."
   },
   {
-    "objectID": "decisions/20231108-ansible-new-server-provisioning.html#the-challenge",
-    "href": "decisions/20231108-ansible-new-server-provisioning.html#the-challenge",
-    "title": "Proposed: Ansible Server Provisioning",
+    "objectID": "decisions/20230507-supabase.html#references",
+    "href": "decisions/20230507-supabase.html#references",
+    "title": "Rejected: Using Deno to handle the conversion of GLB files to Godot Engine packed scenes",
     "section": "",
-    "text": "The challenge lies in choosing the right configuration management tool for a small project. Factors such as ease of use, scalability, and community support are crucial."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20231108-ansible-new-server-provisioning.html#the-strategy",
-    "href": "decisions/20231108-ansible-new-server-provisioning.html#the-strategy",
-    "title": "Proposed: Ansible Server Provisioning",
+    "objectID": "decisions/20231110-v-sekai-dependencies.html",
+    "href": "decisions/20231110-v-sekai-dependencies.html",
+    "title": "Accepted: V-Sekai dependencies",
     "section": "",
-    "text": "Based on these parameters, Ansible emerges as a strong contender. Its simple syntax written in YAML makes it easy to understand even for those new to automation. Being agentless, it’s easier to manage and scale. Moreover, Ansible has a large and active community, providing plenty of resources and support.\n# Sample Ansible playbook\n---\n- hosts: webservers\n  tasks:\n    - name: ensure apache is at the latest version\n      yum:\n        name: httpd\n        state: latest"
+    "text": "Status: Proposed \nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nV-Sekai is a rapidly evolving platform with a diverse set of requirements. As the platform grows, so does the need for robust and scalable technologies to support its development.\n\n\n\nThe challenge lies in selecting and integrating the right technologies that can cater to V-Sekai’s unique needs while ensuring scalability, performance, and reliability.\n\n\n\n\n\nElixir is a dynamic, functional language designed for building scalable and maintainable applications. It leverages the Erlang VM, known for running low-latency, distributed and fault-tolerant systems.\ndefmodule Hello do\n def world do\n   IO.puts(\"Hello, World!\")\n end\nend\n\n\n\nCockroachDB is a cloud-native SQL database for building global, scalable cloud services that survive disasters. It’s a distributed SQL database built on a transactional and strongly-consistent key-value store.\nCREATE DATABASE bank;\nUSE bank;\nCREATE TABLE accounts (id INT PRIMARY KEY, balance DECIMAL);\nINSERT INTO accounts VALUES (1, 1000.50);\n\n\n\nSeaweedFS is a simple and highly scalable distributed file system. It focuses on two objectives: storing billions of files, and serving them fast! SeaweedFS implements an object store with O(1) disk seek and an optional Filer with POSIX interface.\nweed master\nweed volume -dir=\"/tmp/1\" -mserver=\"localhost:9333\" -port=8080\ncurl -F file=@/path/to/file http://localhost:9333/dir/assign\nEach of these technologies has its own use cases and can be used in combination depending on the requirements of your project.\n\n\n\n\nThe proposed strategy allows for a scalable, robust, and efficient system that can handle V-Sekai’s growing needs. It also provides a solid foundation for future development and expansion.\n\n\n\nThe downside is the potential complexity of managing multiple technologies and ensuring they work seamlessly together. However, with proper documentation and best practices, this can be mitigated.\n\n\n\nOther technologies could have been considered, but the chosen ones provide the best balance between performance, scalability, and reliability for V-Sekai’s specific needs.\n\n\n\nWhile the proposed technologies are well-suited for most use cases, there may be infrequent scenarios where additional solutions might be needed. These should be evaluated on a case-by-case basis.\n\n\n\nThe integration and management of these technologies will be handled by the V-Sekai team, ensuring that they align with our core values and objectives.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nThis article was assisted by AI."
   },
   {
-    "objectID": "decisions/20231108-ansible-new-server-provisioning.html#the-upside",
-    "href": "decisions/20231108-ansible-new-server-provisioning.html#the-upside",
-    "title": "Proposed: Ansible Server Provisioning",
+    "objectID": "decisions/20231110-v-sekai-dependencies.html#metadata",
+    "href": "decisions/20231110-v-sekai-dependencies.html#metadata",
+    "title": "Accepted: V-Sekai dependencies",
     "section": "",
-    "text": "Choosing Ansible can simplify server provisioning due to its simplicity and ease of use. It doesn’t require any special coding skills, making it accessible for beginners."
+    "text": "Status: Proposed \nDeciders: V-Sekai\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20231108-ansible-new-server-provisioning.html#the-downside",
-    "href": "decisions/20231108-ansible-new-server-provisioning.html#the-downside",
-    "title": "Proposed: Ansible Server Provisioning",
+    "objectID": "decisions/20231110-v-sekai-dependencies.html#the-backdrop",
+    "href": "decisions/20231110-v-sekai-dependencies.html#the-backdrop",
+    "title": "Accepted: V-Sekai dependencies",
     "section": "",
-    "text": "While Ansible is powerful and user-friendly, it may not be as feature-rich as some other tools like Chef or Puppet. However, for a small project, this might not be a significant concern."
+    "text": "V-Sekai is a rapidly evolving platform with a diverse set of requirements. As the platform grows, so does the need for robust and scalable technologies to support its development."
   },
   {
-    "objectID": "decisions/20231108-ansible-new-server-provisioning.html#the-road-not-taken",
-    "href": "decisions/20231108-ansible-new-server-provisioning.html#the-road-not-taken",
-    "title": "Proposed: Ansible Server Provisioning",
+    "objectID": "decisions/20231110-v-sekai-dependencies.html#the-challenge",
+    "href": "decisions/20231110-v-sekai-dependencies.html#the-challenge",
+    "title": "Accepted: V-Sekai dependencies",
     "section": "",
-    "text": "Other tools like Chef, Puppet, and SaltStack were also considered. While they all have their strengths, they may not be as beginner-friendly as Ansible."
+    "text": "The challenge lies in selecting and integrating the right technologies that can cater to V-Sekai’s unique needs while ensuring scalability, performance, and reliability."
   },
   {
-    "objectID": "decisions/20231108-ansible-new-server-provisioning.html#the-infrequent-use-case",
-    "href": "decisions/20231108-ansible-new-server-provisioning.html#the-infrequent-use-case",
-    "title": "Proposed: Ansible Server Provisioning",
+    "objectID": "decisions/20231110-v-sekai-dependencies.html#the-strategy",
+    "href": "decisions/20231110-v-sekai-dependencies.html#the-strategy",
+    "title": "Accepted: V-Sekai dependencies",
     "section": "",
-    "text": "For complex infrastructures or specific use cases, other tools might be more suitable. It’s always a good idea to try out different tools before making a decision."
+    "text": "Elixir is a dynamic, functional language designed for building scalable and maintainable applications. It leverages the Erlang VM, known for running low-latency, distributed and fault-tolerant systems.\ndefmodule Hello do\n def world do\n   IO.puts(\"Hello, World!\")\n end\nend\n\n\n\nCockroachDB is a cloud-native SQL database for building global, scalable cloud services that survive disasters. It’s a distributed SQL database built on a transactional and strongly-consistent key-value store.\nCREATE DATABASE bank;\nUSE bank;\nCREATE TABLE accounts (id INT PRIMARY KEY, balance DECIMAL);\nINSERT INTO accounts VALUES (1, 1000.50);\n\n\n\nSeaweedFS is a simple and highly scalable distributed file system. It focuses on two objectives: storing billions of files, and serving them fast! SeaweedFS implements an object store with O(1) disk seek and an optional Filer with POSIX interface.\nweed master\nweed volume -dir=\"/tmp/1\" -mserver=\"localhost:9333\" -port=8080\ncurl -F file=@/path/to/file http://localhost:9333/dir/assign\nEach of these technologies has its own use cases and can be used in combination depending on the requirements of your project."
   },
   {
-    "objectID": "decisions/20231108-ansible-new-server-provisioning.html#in-core-and-done-by-us",
-    "href": "decisions/20231108-ansible-new-server-provisioning.html#in-core-and-done-by-us",
-    "title": "Proposed: Ansible Server Provisioning",
+    "objectID": "decisions/20231110-v-sekai-dependencies.html#the-upside",
+    "href": "decisions/20231110-v-sekai-dependencies.html#the-upside",
+    "title": "Accepted: V-Sekai dependencies",
     "section": "",
-    "text": "The decision to use Ansible for server provisioning is proposed by V-Sekai."
+    "text": "The proposed strategy allows for a scalable, robust, and efficient system that can handle V-Sekai’s growing needs. It also provides a solid foundation for future development and expansion."
   },
   {
-    "objectID": "decisions/20231108-ansible-new-server-provisioning.html#further-reading",
-    "href": "decisions/20231108-ansible-new-server-provisioning.html#further-reading",
-    "title": "Proposed: Ansible Server Provisioning",
+    "objectID": "decisions/20231110-v-sekai-dependencies.html#the-downside",
+    "href": "decisions/20231110-v-sekai-dependencies.html#the-downside",
+    "title": "Accepted: V-Sekai dependencies",
     "section": "",
-    "text": "V-Sekai\nAnsible Tower: FAQ\n\nThis article was assisted by Aria, an AI."
+    "text": "The downside is the potential complexity of managing multiple technologies and ensuring they work seamlessly together. However, with proper documentation and best practices, this can be mitigated."
   },
   {
-    "objectID": "decisions/20230830-better-backend-services.html",
-    "href": "decisions/20230830-better-backend-services.html",
-    "title": "Proposed: Integrating Backend Services",
+    "objectID": "decisions/20231110-v-sekai-dependencies.html#the-road-not-taken",
+    "href": "decisions/20231110-v-sekai-dependencies.html#the-road-not-taken",
+    "title": "Accepted: V-Sekai dependencies",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nV-Sekai is a virtual reality (VR) platform that offers users the opportunity to immerse themselves in virtual worlds. However, there are certain limitations that hinder the overall user experience. This documentation aims to address these limitations by proposing specific areas for improvement within V-Sekai.\n\n\n\nV-Sekai currently faces several limitations, including non-functional menus in VR mode and a limited number of available worlds. To overcome these challenges and enhance the user experience, we must prioritize and focus on one area for improvement.\n\n\nExploring Backend Services Integration: Integrating V-Sekai with backend services can enhance the platform’s features and capabilities. This could involve incorporating external APIs or services to provide additional resources and functionalities.\n\n\n\n\nTo ensure efficient use of time and resources, it is advisable to choose one area to focus on and strive to complete it within a two-week timeframe. This focused approach allows for significant progress in improving V-Sekai.\n\n\n\nBy addressing these limitations, V-Sekai can be transformed into a more immersive and engaging VR platform. Enhancing menus and object pickup mechanics, expanding the variety of worlds, or integrating backend services can greatly enhance the overall user experience for users.\n\n\n\nGiven the limited timeframe, it may not be possible to address all the identified limitations simultaneously. Prioritizing one area means that other aspects may need to wait for future improvements. Additionally, the complexity of the chosen area may present challenges in achieving substantial improvements within the two-week timeframe.\n\n\n\nWhile focusing on one area is recommended for the given timeframe, it’s important to acknowledge that there are other potential avenues for improvement. Exploring options such as performance optimization, improving UI design, or implementing additional features can be considered in future iterations of V-Sekai.\n\n\n\nThe development team at V-Sekai should primarily handle the implementation and integration of the chosen improvement. However, collaborative efforts, involving developers, designers, and technical writers, are essential for documenting the enhancements.\n\n\n\n\nV-Sekai\nThis article is assisted by AI."
+    "text": "Other technologies could have been considered, but the chosen ones provide the best balance between performance, scalability, and reliability for V-Sekai’s specific needs."
   },
   {
-    "objectID": "decisions/20230830-better-backend-services.html#metadata",
-    "href": "decisions/20230830-better-backend-services.html#metadata",
-    "title": "Proposed: Integrating Backend Services",
+    "objectID": "decisions/20231110-v-sekai-dependencies.html#the-infrequent-use-case",
+    "href": "decisions/20231110-v-sekai-dependencies.html#the-infrequent-use-case",
+    "title": "Accepted: V-Sekai dependencies",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai"
+    "text": "While the proposed technologies are well-suited for most use cases, there may be infrequent scenarios where additional solutions might be needed. These should be evaluated on a case-by-case basis."
   },
   {
-    "objectID": "decisions/20230830-better-backend-services.html#introduction",
-    "href": "decisions/20230830-better-backend-services.html#introduction",
-    "title": "Proposed: Integrating Backend Services",
+    "objectID": "decisions/20231110-v-sekai-dependencies.html#in-core-and-done-by-us",
+    "href": "decisions/20231110-v-sekai-dependencies.html#in-core-and-done-by-us",
+    "title": "Accepted: V-Sekai dependencies",
     "section": "",
-    "text": "V-Sekai is a virtual reality (VR) platform that offers users the opportunity to immerse themselves in virtual worlds. However, there are certain limitations that hinder the overall user experience. This documentation aims to address these limitations by proposing specific areas for improvement within V-Sekai."
+    "text": "The integration and management of these technologies will be handled by the V-Sekai team, ensuring that they align with our core values and objectives."
   },
   {
-    "objectID": "decisions/20230830-better-backend-services.html#the-challenge",
-    "href": "decisions/20230830-better-backend-services.html#the-challenge",
-    "title": "Proposed: Integrating Backend Services",
+    "objectID": "decisions/20231110-v-sekai-dependencies.html#further-reading",
+    "href": "decisions/20231110-v-sekai-dependencies.html#further-reading",
+    "title": "Accepted: V-Sekai dependencies",
     "section": "",
-    "text": "V-Sekai currently faces several limitations, including non-functional menus in VR mode and a limited number of available worlds. To overcome these challenges and enhance the user experience, we must prioritize and focus on one area for improvement.\n\n\nExploring Backend Services Integration: Integrating V-Sekai with backend services can enhance the platform’s features and capabilities. This could involve incorporating external APIs or services to provide additional resources and functionalities."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nThis article was assisted by AI."
   },
   {
-    "objectID": "decisions/20230830-better-backend-services.html#the-strategy",
-    "href": "decisions/20230830-better-backend-services.html#the-strategy",
-    "title": "Proposed: Integrating Backend Services",
+    "objectID": "decisions/20210811-glb-in-video.html",
+    "href": "decisions/20210811-glb-in-video.html",
+    "title": "Proposed: GLB data in a Movie",
     "section": "",
-    "text": "To ensure efficient use of time and resources, it is advisable to choose one area to focus on and strive to complete it within a two-week timeframe. This focused approach allows for significant progress in improving V-Sekai."
+    "text": "Proposed: GLB data in a Movie\n\nContext and Problem Statement\nStore ~20 mb of glb data in a mp4.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nMatroska supports storage of related files and data in the Attachments Element (a Top-Level Element). Attachment Elements can be used to store related cover art, font files, transcripts, reports, error recovery files, picture, or text-based annotations, copies of specifications, or other ancillary files related to the Segment.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nStore a glb in a mkv in the attachment sections.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nMaybe a small script.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nInteresting\n\n\nReferences\nhttps://www.matroska.org/technical/attachments.html\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230830-better-backend-services.html#upsides",
-    "href": "decisions/20230830-better-backend-services.html#upsides",
-    "title": "Proposed: Integrating Backend Services",
+    "objectID": "decisions/20230419-limited-tracker-placement.html",
+    "href": "decisions/20230419-limited-tracker-placement.html",
+    "title": "Proposed: Capturing accurate body movements with limited tracker placement",
     "section": "",
-    "text": "By addressing these limitations, V-Sekai can be transformed into a more immersive and engaging VR platform. Enhancing menus and object pickup mechanics, expanding the variety of worlds, or integrating backend services can greatly enhance the overall user experience for users."
+    "text": "Proposed: Capturing accurate body movements with limited tracker placement\n\nMetadata\n\nStatus: superseded by 20230602-limited-tracker-placement.md \nDeciders: V-Sekai,fire,\nTags: V-Sekai,\n\n\n\nContext and Problem Statement\nIn our current VR project, we face the challenge of capturing accurate body movements for both soccer and dancing experiences with a limited budget. How can we prioritize the placement of a limited number of trackers to ensure a realistic and immersive experience for both activities?\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nThe proposed option involves prioritizing tracker placement for the head, hands, hips, and feet, as they are essential for both soccer and dancing experiences. This approach allows for an effective trade-off between tracking accuracy and budget constraints while ensuring a satisfactory level of immersion in both activities.\n\n\nDescribe how your proposal will work with code, pseudo-code, mock-ups, or diagrams\n\nHead: At the base of the neck to monitor head rotation and tilt.\nLeft Hand: On the left wrist to track the overall motion of the left hand.\nRight Hand: On the right wrist to track the overall motion of the right hand.\nHips: A tracker on the hips to monitor lower body movement.\nLeft Foot: A tracker on the left foot to capture left foot movement, essential for both soccer and dancing.\nRight Foot: A tracker on the right foot to capture right foot movement, also crucial for both activities.\n\nAs the budget permits, additional trackers can be incorporated into the setup to further enhance tracking accuracy, particularly for the upper body and leg movements. This expansion can be achieved by following the prioritized list of additional trackers below:\n\nChest: A tracker on the chest to monitor upper body rotation, providing more detailed information about the user’s torso movements.\nLeft Shoulder: A tracker on the left shoulder to track upper arm rotation, allowing for more precise tracking of arm movements during soccer and dancing.\nRight Shoulder: A tracker on the right shoulder to track upper arm rotation, complementing the left shoulder tracker for better arm movement tracking.\nLeft Knee: A tracker on the left knee to track left leg movement, enhancing the realism of leg movements and providing more accurate feedback for actions like kicking in soccer or complex footwork in dancing.\nRight Knee: A tracker on the right knee to track right leg movement, mirroring the benefits of the left knee tracker for a balanced leg movement representation.\n\nBy gradually adding these trackers to the initial setup, the overall tracking accuracy of the system will be improved. This will result in more natural and immersive interactions within the VR environment, leading to a more satisfying user experience for both soccer and dancing activities.\n\n\nPositive Consequences\n\nEffective use of a limited budget while maintaining immersive experiences.\nThe solution caters to both soccer and dancing activities in VR.\nFlexibility in adding more trackers as budget permits.\n\n\n\nNegative Consequences\n\nReduced tracking accuracy for upper body and leg movements compared to a setup with more trackers.\nPotential limitations in supporting advanced features or interactions in VR.\n\n\n\nOption graveyard\nCamera-based tracking: Utilizing external cameras to track body movements without the need for wearable trackers. While this approach can be cost-effective, it may not provide the same level of accuracy and precision as wearable trackers, particularly for fast and complex movements in soccer and dancing. Additionally, camera-based tracking can be sensitive to lighting conditions and may require a specific setup to function optimally.\nCamera-based tracking might be a viable solution if budget constraints are severe, but it is essential to consider the potential trade-offs in terms of tracking accuracy and reliability compared to wearable trackers.\n\n\nIf this enhancement will be used infrequently, can it be worked around with a few lines of script?\nNo, as the proposed solution deals with hardware configuration and the strategic placement of physical trackers to balance budget and immersion.\n\n\nIs there a reason why this should be core and done by us?\nYes, ensuring an immersive VR experience with a limited budget is a fundamental challenge that requires expertise in tracker placement and prioritization.\n\n\nReferences\n\nV-Sekai"
   },
   {
-    "objectID": "decisions/20230830-better-backend-services.html#downsides",
-    "href": "decisions/20230830-better-backend-services.html#downsides",
-    "title": "Proposed: Integrating Backend Services",
+    "objectID": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html",
+    "href": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html",
+    "title": "Proposed: Implementing a 3D Multiplayer Movement System with Parented Objects and Inventory Management",
     "section": "",
-    "text": "Given the limited timeframe, it may not be possible to address all the identified limitations simultaneously. Prioritizing one area means that other aspects may need to wait for future improvements. Additionally, the complexity of the chosen area may present challenges in achieving substantial improvements within the two-week timeframe."
+    "text": "The V-Sekai development team is working on enhancing the multiplayer experience in our VR game. We aim to create a more immersive and interactive environment for our players, akin to electrons circling in an atom or bustling activity on an MMOG street.\n\n\n\nOur VR game lacks a robust system for managing 3D multiplayer movement, parented objects, tracking validation, authentication, account metadata information, server boundaries, inventory management, and asset delivery. We also need to implement a mechanism for players to seamlessly leave and rejoin the game.\n\n\n\nOur proposed solution involves implementing a series of features:\n\n3D Multiplayer Movement: We will use the libgodot process to manage 3D multiplayer movements. This will allow players to interactively move around in the 3D space, similar to electrons circling in an atom.\nParented Objects: We will develop a system to handle parented objects, allowing for complex interactions between game entities.\nTracking Validation & Authentication: We will implement mechanisms to validate cross-communication and user inputs, along with an authentication system for account security.\nAccount Metadata Information: We will store and manage account metadata information to personalize the user experience.\nServer Boundaries: We will set limitations on the server, such as boundaries, to maintain game balance and performance.\nInventory Management: Players can spawn items from their inventory, create new items, and return them to the inventory.\nGame Rejoining: Players will have the ability to leave and rejoin the game without losing their progress.\nAsset Delivery and Upload: We will establish an efficient asset delivery and upload system.\nVoice Communication: We plan to add voice communication to enhance player interaction.\n\n\n\n\n\nEnhanced player interaction with 3D multiplayer movement and voice communication.\nImproved game balance and performance with server boundaries.\nBetter user experience with personalized account metadata information.\nSeamless gameplay with the ability to leave and rejoin the game.\n\n\n\n\n\nRequires significant development effort.\nPotential for increased system complexity.\n\n\n\n\nWe considered using existing game engines or libraries, but they did not meet our specific requirements for a highly interactive and immersive VR game.\n\n\n\nThis proposal may not be suitable for smaller projects that do not require complex 3D multiplayer interactions or inventory management.\n\n\n\nThe V-Sekai development team will implement this proposal.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team, “Bioblaze Payne”, “fire”\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAssisted by Aria."
   },
   {
-    "objectID": "decisions/20230830-better-backend-services.html#the-road-not-taken",
-    "href": "decisions/20230830-better-backend-services.html#the-road-not-taken",
-    "title": "Proposed: Integrating Backend Services",
+    "objectID": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#the-context",
+    "href": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#the-context",
+    "title": "Proposed: Implementing a 3D Multiplayer Movement System with Parented Objects and Inventory Management",
     "section": "",
-    "text": "While focusing on one area is recommended for the given timeframe, it’s important to acknowledge that there are other potential avenues for improvement. Exploring options such as performance optimization, improving UI design, or implementing additional features can be considered in future iterations of V-Sekai."
+    "text": "The V-Sekai development team is working on enhancing the multiplayer experience in our VR game. We aim to create a more immersive and interactive environment for our players, akin to electrons circling in an atom or bustling activity on an MMOG street."
   },
   {
-    "objectID": "decisions/20230830-better-backend-services.html#in-core-and-done-by-us",
-    "href": "decisions/20230830-better-backend-services.html#in-core-and-done-by-us",
-    "title": "Proposed: Integrating Backend Services",
+    "objectID": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#the-problem-statement",
+    "href": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#the-problem-statement",
+    "title": "Proposed: Implementing a 3D Multiplayer Movement System with Parented Objects and Inventory Management",
     "section": "",
-    "text": "The development team at V-Sekai should primarily handle the implementation and integration of the chosen improvement. However, collaborative efforts, involving developers, designers, and technical writers, are essential for documenting the enhancements."
+    "text": "Our VR game lacks a robust system for managing 3D multiplayer movement, parented objects, tracking validation, authentication, account metadata information, server boundaries, inventory management, and asset delivery. We also need to implement a mechanism for players to seamlessly leave and rejoin the game."
   },
   {
-    "objectID": "decisions/20230830-better-backend-services.html#further-reading",
-    "href": "decisions/20230830-better-backend-services.html#further-reading",
-    "title": "Proposed: Integrating Backend Services",
+    "objectID": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Implementing a 3D Multiplayer Movement System with Parented Objects and Inventory Management",
     "section": "",
-    "text": "V-Sekai\nThis article is assisted by AI."
+    "text": "Our proposed solution involves implementing a series of features:\n\n3D Multiplayer Movement: We will use the libgodot process to manage 3D multiplayer movements. This will allow players to interactively move around in the 3D space, similar to electrons circling in an atom.\nParented Objects: We will develop a system to handle parented objects, allowing for complex interactions between game entities.\nTracking Validation & Authentication: We will implement mechanisms to validate cross-communication and user inputs, along with an authentication system for account security.\nAccount Metadata Information: We will store and manage account metadata information to personalize the user experience.\nServer Boundaries: We will set limitations on the server, such as boundaries, to maintain game balance and performance.\nInventory Management: Players can spawn items from their inventory, create new items, and return them to the inventory.\nGame Rejoining: Players will have the ability to leave and rejoin the game without losing their progress.\nAsset Delivery and Upload: We will establish an efficient asset delivery and upload system.\nVoice Communication: We plan to add voice communication to enhance player interaction."
   },
   {
-    "objectID": "decisions/20231126-v-sekai-report.html",
-    "href": "decisions/20231126-v-sekai-report.html",
-    "title": "Accepted: V-Sekai 2023-11-26 Report",
+    "objectID": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#the-benefits",
+    "href": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#the-benefits",
+    "title": "Proposed: Implementing a 3D Multiplayer Movement System with Parented Objects and Inventory Management",
     "section": "",
-    "text": "Status: Accepted\nDeciders: V-Sekai, fire, PLYSHKA🐧, SaracenOne\nTags: V-Sekai, Linux, Bug Fix, Godot Engine, User Support\n\n\n\n\nV-Sekai, pronounced vee-say-kai, is a collective of developers passionate about creating open-source VR technology. We aim to contribute to social VR and provide alternatives to proprietary engines like Unity and Unreal.\nDespite challenges, we’ve grown into a global community committed to advancing open standards and open-source software for virtual worlds.\nOur strategy focuses on providing comprehensive documentation and support to help users understand the platform better. We’re also committed to investigating and resolving issues like the reported Linux build problem.\n\n\n\nOver the past month, our team has been deeply involved in the Godot Engine conference in Munich, Germany. Our primary responsibility during this period has been to prepare for the upcoming launch of Godot Engine 4.2, to which we are contributing as part of the animation and 3D pipeline teams.\n\n\n\nWhat state is V-Sekai in, and what can it do?\n\n\n\n\n\n\nMultiplayer Voice Chat: The multiplayer voice chat feature in V-Sekai is broken.\nMenu Editing: In V-Sekai, menus can’t be edited in VR. They can only be edited on the desktop before entering a game.\nDefault Avatar IK: V-Sekai’s default ik is currently twisted incorrectly.\n\n\n\n\n\nAvatar Uploading and Downloading: V-Sekai can upload from the editor and, download avatars, and load them into the game at runtime.\nWorld Uploading and Downloading: V-Sekai can upload from the editor and, download worlds, and load them into the game at runtime.\nVR Mode Loading: V-Sekai can successfully load in VR mode.\n\n\n\n\n\nContributions: V-Sekai is actively looking for more contributions.\n\n\n\n\n\nPros:\nAddressing these challenges can enhance the user experience, boost platform adoption, and collect crucial feedback for subsequent development.\nCons:\nThere may be underlying issues causing the Linux build problem that could take significant time and resources to resolve.\n\n\n\nAn alternative approach could have been to ignore the user’s query and continue with the current development roadmap. However, this would not foster a supportive community or encourage user engagement.\n\n\n\nWhile most users may not encounter the same issue as PLYSHKA🐧, addressing even infrequent use cases is essential to ensure a robust and user-friendly platform.\n\n\n\nAddressing this issue falls within our core responsibilities as the V-Sekai development team.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI Aria assisted with this article."
+    "text": "Enhanced player interaction with 3D multiplayer movement and voice communication.\nImproved game balance and performance with server boundaries.\nBetter user experience with personalized account metadata information.\nSeamless gameplay with the ability to leave and rejoin the game."
   },
   {
-    "objectID": "decisions/20231126-v-sekai-report.html#metadata",
-    "href": "decisions/20231126-v-sekai-report.html#metadata",
-    "title": "Accepted: V-Sekai 2023-11-26 Report",
+    "objectID": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#the-downsides",
+    "href": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#the-downsides",
+    "title": "Proposed: Implementing a 3D Multiplayer Movement System with Parented Objects and Inventory Management",
     "section": "",
-    "text": "Status: Accepted\nDeciders: V-Sekai, fire, PLYSHKA🐧, SaracenOne\nTags: V-Sekai, Linux, Bug Fix, Godot Engine, User Support"
+    "text": "Requires significant development effort.\nPotential for increased system complexity."
   },
   {
-    "objectID": "decisions/20231126-v-sekai-report.html#what-is-v-sekai",
-    "href": "decisions/20231126-v-sekai-report.html#what-is-v-sekai",
-    "title": "Accepted: V-Sekai 2023-11-26 Report",
+    "objectID": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#the-road-not-taken",
+    "href": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#the-road-not-taken",
+    "title": "Proposed: Implementing a 3D Multiplayer Movement System with Parented Objects and Inventory Management",
     "section": "",
-    "text": "V-Sekai, pronounced vee-say-kai, is a collective of developers passionate about creating open-source VR technology. We aim to contribute to social VR and provide alternatives to proprietary engines like Unity and Unreal.\nDespite challenges, we’ve grown into a global community committed to advancing open standards and open-source software for virtual worlds.\nOur strategy focuses on providing comprehensive documentation and support to help users understand the platform better. We’re also committed to investigating and resolving issues like the reported Linux build problem."
+    "text": "We considered using existing game engines or libraries, but they did not meet our specific requirements for a highly interactive and immersive VR game."
   },
   {
-    "objectID": "decisions/20231126-v-sekai-report.html#background",
-    "href": "decisions/20231126-v-sekai-report.html#background",
-    "title": "Accepted: V-Sekai 2023-11-26 Report",
+    "objectID": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#the-infrequent-use-case",
+    "href": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#the-infrequent-use-case",
+    "title": "Proposed: Implementing a 3D Multiplayer Movement System with Parented Objects and Inventory Management",
     "section": "",
-    "text": "Over the past month, our team has been deeply involved in the Godot Engine conference in Munich, Germany. Our primary responsibility during this period has been to prepare for the upcoming launch of Godot Engine 4.2, to which we are contributing as part of the animation and 3D pipeline teams."
+    "text": "This proposal may not be suitable for smaller projects that do not require complex 3D multiplayer interactions or inventory management."
   },
   {
-    "objectID": "decisions/20231126-v-sekai-report.html#problem-statement",
-    "href": "decisions/20231126-v-sekai-report.html#problem-statement",
-    "title": "Accepted: V-Sekai 2023-11-26 Report",
+    "objectID": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#in-core-and-done-by-us",
+    "href": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#in-core-and-done-by-us",
+    "title": "Proposed: Implementing a 3D Multiplayer Movement System with Parented Objects and Inventory Management",
     "section": "",
-    "text": "What state is V-Sekai in, and what can it do?"
+    "text": "The V-Sekai development team will implement this proposal."
   },
   {
-    "objectID": "decisions/20231126-v-sekai-report.html#strategy",
-    "href": "decisions/20231126-v-sekai-report.html#strategy",
-    "title": "Accepted: V-Sekai 2023-11-26 Report",
+    "objectID": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#status",
+    "href": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#status",
+    "title": "Proposed: Implementing a 3D Multiplayer Movement System with Parented Objects and Inventory Management",
     "section": "",
-    "text": "Multiplayer Voice Chat: The multiplayer voice chat feature in V-Sekai is broken.\nMenu Editing: In V-Sekai, menus can’t be edited in VR. They can only be edited on the desktop before entering a game.\nDefault Avatar IK: V-Sekai’s default ik is currently twisted incorrectly.\n\n\n\n\n\nAvatar Uploading and Downloading: V-Sekai can upload from the editor and, download avatars, and load them into the game at runtime.\nWorld Uploading and Downloading: V-Sekai can upload from the editor and, download worlds, and load them into the game at runtime.\nVR Mode Loading: V-Sekai can successfully load in VR mode.\n\n\n\n\n\nContributions: V-Sekai is actively looking for more contributions."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20231126-v-sekai-report.html#pros-and-cons",
-    "href": "decisions/20231126-v-sekai-report.html#pros-and-cons",
-    "title": "Accepted: V-Sekai 2023-11-26 Report",
+    "objectID": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#decision-makers",
+    "href": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#decision-makers",
+    "title": "Proposed: Implementing a 3D Multiplayer Movement System with Parented Objects and Inventory Management",
     "section": "",
-    "text": "Pros:\nAddressing these challenges can enhance the user experience, boost platform adoption, and collect crucial feedback for subsequent development.\nCons:\nThere may be underlying issues causing the Linux build problem that could take significant time and resources to resolve."
+    "text": "V-Sekai development team, “Bioblaze Payne”, “fire”"
   },
   {
-    "objectID": "decisions/20231126-v-sekai-report.html#alternative-approach",
-    "href": "decisions/20231126-v-sekai-report.html#alternative-approach",
-    "title": "Accepted: V-Sekai 2023-11-26 Report",
+    "objectID": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#tags",
+    "href": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#tags",
+    "title": "Proposed: Implementing a 3D Multiplayer Movement System with Parented Objects and Inventory Management",
     "section": "",
-    "text": "An alternative approach could have been to ignore the user’s query and continue with the current development roadmap. However, this would not foster a supportive community or encourage user engagement."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20231126-v-sekai-report.html#infrequent-use-case",
-    "href": "decisions/20231126-v-sekai-report.html#infrequent-use-case",
-    "title": "Accepted: V-Sekai 2023-11-26 Report",
+    "objectID": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#further-reading",
+    "href": "decisions/20240411-multiplayer-movement-with-parented-obejcts.html#further-reading",
+    "title": "Proposed: Implementing a 3D Multiplayer Movement System with Parented Objects and Inventory Management",
     "section": "",
-    "text": "While most users may not encounter the same issue as PLYSHKA🐧, addressing even infrequent use cases is essential to ensure a robust and user-friendly platform."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAssisted by Aria."
   },
   {
-    "objectID": "decisions/20231126-v-sekai-report.html#responsibility",
-    "href": "decisions/20231126-v-sekai-report.html#responsibility",
-    "title": "Accepted: V-Sekai 2023-11-26 Report",
+    "objectID": "decisions/ai-assisted-proposal-style-guide.html",
+    "href": "decisions/ai-assisted-proposal-style-guide.html",
+    "title": "Accepted: AI Assisted Style Guide",
     "section": "",
-    "text": "Addressing this issue falls within our core responsibilities as the V-Sekai development team."
+    "text": "In the realm of proposal writing, maintaining a consistent and professional style is crucial. However, when utilizing AI to assist in this process, the output often lacks the desired stylistic quality.\n\n\n\nWhen we instruct AI to help complete our proposals, we often encounter issues with poor style and inconsistent formatting.\n\n\n\n\nAvoid Purple Speech: Ensure that the language used is clear and concise, avoiding overly elaborate or flowery expressions.\nBe Snappy: Keep sentences short and to the point to maintain reader engagement.\nAvoid Redundant Phrases: Refrain from using redundant phrases like “effective altruism” since true altruism inherently implies effectiveness.\nMaintain Consistent Headers: Adhere to the header structure provided in the template to ensure uniformity across documents.\n\n\n\n\n\nImproved Readability: Clear and concise language enhances the readability of proposals.\nConsistency: Maintaining a consistent style ensures that all documents have a professional appearance.\nEfficiency: Streamlined guidelines make it easier for AI to generate high-quality content quickly.\n\n\n\n\n\nLimited Creativity: Strict adherence to style guidelines may limit creative expression.\nInitial Setup Time: Establishing and fine-tuning the style guide may require an initial investment of time and resources.\n\n\n\n\nAlternative approaches such as manual editing or using different AI models were considered but ultimately deemed less efficient or effective.\n\n\n\nIn scenarios where highly specialized or technical language is required, additional human oversight may be necessary to ensure accuracy and appropriateness.\n\n\n\nThis proposal aligns with our core values of efficiency and professionalism and will be implemented by our team.\n\n\n\nStatus: Accepted \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20231126-v-sekai-report.html#further-reading",
-    "href": "decisions/20231126-v-sekai-report.html#further-reading",
-    "title": "Accepted: V-Sekai 2023-11-26 Report",
+    "objectID": "decisions/ai-assisted-proposal-style-guide.html#the-context",
+    "href": "decisions/ai-assisted-proposal-style-guide.html#the-context",
+    "title": "Accepted: AI Assisted Style Guide",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI Aria assisted with this article."
+    "text": "In the realm of proposal writing, maintaining a consistent and professional style is crucial. However, when utilizing AI to assist in this process, the output often lacks the desired stylistic quality."
   },
   {
-    "objectID": "decisions/present-proposal-template.html",
-    "href": "decisions/present-proposal-template.html",
-    "title": "Proposed: Template",
+    "objectID": "decisions/ai-assisted-proposal-style-guide.html#the-problem-statement",
+    "href": "decisions/ai-assisted-proposal-style-guide.html#the-problem-statement",
+    "title": "Accepted: AI Assisted Style Guide",
     "section": "",
-    "text": "Status: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "When we instruct AI to help complete our proposals, we often encounter issues with poor style and inconsistent formatting."
   },
   {
-    "objectID": "decisions/present-proposal-template.html#status",
-    "href": "decisions/present-proposal-template.html#status",
-    "title": "Proposed: Template",
+    "objectID": "decisions/ai-assisted-proposal-style-guide.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/ai-assisted-proposal-style-guide.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Accepted: AI Assisted Style Guide",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "Avoid Purple Speech: Ensure that the language used is clear and concise, avoiding overly elaborate or flowery expressions.\nBe Snappy: Keep sentences short and to the point to maintain reader engagement.\nAvoid Redundant Phrases: Refrain from using redundant phrases like “effective altruism” since true altruism inherently implies effectiveness.\nMaintain Consistent Headers: Adhere to the header structure provided in the template to ensure uniformity across documents."
   },
   {
-    "objectID": "decisions/present-proposal-template.html#decision-makers",
-    "href": "decisions/present-proposal-template.html#decision-makers",
-    "title": "Proposed: Template",
+    "objectID": "decisions/ai-assisted-proposal-style-guide.html#the-benefits",
+    "href": "decisions/ai-assisted-proposal-style-guide.html#the-benefits",
+    "title": "Accepted: AI Assisted Style Guide",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "Improved Readability: Clear and concise language enhances the readability of proposals.\nConsistency: Maintaining a consistent style ensures that all documents have a professional appearance.\nEfficiency: Streamlined guidelines make it easier for AI to generate high-quality content quickly."
   },
   {
-    "objectID": "decisions/present-proposal-template.html#tags",
-    "href": "decisions/present-proposal-template.html#tags",
-    "title": "Proposed: Template",
+    "objectID": "decisions/ai-assisted-proposal-style-guide.html#the-downsides",
+    "href": "decisions/ai-assisted-proposal-style-guide.html#the-downsides",
+    "title": "Accepted: AI Assisted Style Guide",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Limited Creativity: Strict adherence to style guidelines may limit creative expression.\nInitial Setup Time: Establishing and fine-tuning the style guide may require an initial investment of time and resources."
   },
   {
-    "objectID": "decisions/present-proposal-template.html#further-reading",
-    "href": "decisions/present-proposal-template.html#further-reading",
-    "title": "Proposed: Template",
+    "objectID": "decisions/ai-assisted-proposal-style-guide.html#the-road-not-taken",
+    "href": "decisions/ai-assisted-proposal-style-guide.html#the-road-not-taken",
+    "title": "Accepted: AI Assisted Style Guide",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "Alternative approaches such as manual editing or using different AI models were considered but ultimately deemed less efficient or effective."
   },
   {
-    "objectID": "decisions/20230911-xr-grid-with-drawing.html",
-    "href": "decisions/20230911-xr-grid-with-drawing.html",
-    "title": "Proposed: Improving xr grid with new enhancements",
+    "objectID": "decisions/ai-assisted-proposal-style-guide.html#the-infrequent-use-case",
+    "href": "decisions/ai-assisted-proposal-style-guide.html#the-infrequent-use-case",
+    "title": "Accepted: AI Assisted Style Guide",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai, fire, detox,\nTags: V-Sekai\n\n\n\n\nWe are developing an xr grid project, but it’s in a nice easy to understand state.\n\n\n\nDETOX suggested comparing different modes of navigation before making any changes. Fire shared that they have three modes in mind: blob pen, 2D beautifications for 3D, and patch mode. However, these are not functioning correctly yet due to complexity.\n\n\n\nFire will think up some UI for xr-grid, create a simple UI system based on GUI in VR, and add it to xr-grid. We also discuss the possibility of adding a glTF export menu and other features to the UI.\n\n\n\nThe team is considering various improvements such as fixing grid bugs, exporting loadable content in Blender, adding branding/instructions, and improving the UI.\n\n\n\nThe main challenge is to avoid bloating the main project with art tools. This might require branching or forking the project.\n\n\n\nDETOX suggested creating a branch for the new features, while Fire expressed a desire to work on networking. They also discussed the possibility of building a tool similar to Cassie on the branch.\n\n\n\n\nV-Sekai\nThis article is assisted by AI."
+    "text": "In scenarios where highly specialized or technical language is required, additional human oversight may be necessary to ensure accuracy and appropriateness."
   },
   {
-    "objectID": "decisions/20230911-xr-grid-with-drawing.html#metadata",
-    "href": "decisions/20230911-xr-grid-with-drawing.html#metadata",
-    "title": "Proposed: Improving xr grid with new enhancements",
+    "objectID": "decisions/ai-assisted-proposal-style-guide.html#in-core-and-done-by-us",
+    "href": "decisions/ai-assisted-proposal-style-guide.html#in-core-and-done-by-us",
+    "title": "Accepted: AI Assisted Style Guide",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai, fire, detox,\nTags: V-Sekai"
+    "text": "This proposal aligns with our core values of efficiency and professionalism and will be implemented by our team."
   },
   {
-    "objectID": "decisions/20230911-xr-grid-with-drawing.html#context-and-problem-statement",
-    "href": "decisions/20230911-xr-grid-with-drawing.html#context-and-problem-statement",
-    "title": "Proposed: Improving xr grid with new enhancements",
+    "objectID": "decisions/ai-assisted-proposal-style-guide.html#status",
+    "href": "decisions/ai-assisted-proposal-style-guide.html#status",
+    "title": "Accepted: AI Assisted Style Guide",
     "section": "",
-    "text": "We are developing an xr grid project, but it’s in a nice easy to understand state."
+    "text": "Status: Accepted"
   },
   {
-    "objectID": "decisions/20230911-xr-grid-with-drawing.html#considered-options",
-    "href": "decisions/20230911-xr-grid-with-drawing.html#considered-options",
-    "title": "Proposed: Improving xr grid with new enhancements",
+    "objectID": "decisions/ai-assisted-proposal-style-guide.html#decision-makers",
+    "href": "decisions/ai-assisted-proposal-style-guide.html#decision-makers",
+    "title": "Accepted: AI Assisted Style Guide",
     "section": "",
-    "text": "DETOX suggested comparing different modes of navigation before making any changes. Fire shared that they have three modes in mind: blob pen, 2D beautifications for 3D, and patch mode. However, these are not functioning correctly yet due to complexity."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20230911-xr-grid-with-drawing.html#decision-outcome",
-    "href": "decisions/20230911-xr-grid-with-drawing.html#decision-outcome",
-    "title": "Proposed: Improving xr grid with new enhancements",
+    "objectID": "decisions/ai-assisted-proposal-style-guide.html#tags",
+    "href": "decisions/ai-assisted-proposal-style-guide.html#tags",
+    "title": "Accepted: AI Assisted Style Guide",
     "section": "",
-    "text": "Fire will think up some UI for xr-grid, create a simple UI system based on GUI in VR, and add it to xr-grid. We also discuss the possibility of adding a glTF export menu and other features to the UI."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20230911-xr-grid-with-drawing.html#positive-consequences",
-    "href": "decisions/20230911-xr-grid-with-drawing.html#positive-consequences",
-    "title": "Proposed: Improving xr grid with new enhancements",
+    "objectID": "decisions/ai-assisted-proposal-style-guide.html#further-reading",
+    "href": "decisions/ai-assisted-proposal-style-guide.html#further-reading",
+    "title": "Accepted: AI Assisted Style Guide",
     "section": "",
-    "text": "The team is considering various improvements such as fixing grid bugs, exporting loadable content in Blender, adding branding/instructions, and improving the UI."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20230911-xr-grid-with-drawing.html#negative-consequences",
-    "href": "decisions/20230911-xr-grid-with-drawing.html#negative-consequences",
-    "title": "Proposed: Improving xr grid with new enhancements",
+    "objectID": "decisions/20220601-lightweight-quality-avatars.html",
+    "href": "decisions/20220601-lightweight-quality-avatars.html",
+    "title": "Proposed: Lightweight quality avatars",
     "section": "",
-    "text": "The main challenge is to avoid bloating the main project with art tools. This might require branching or forking the project."
+    "text": "Proposed: Lightweight quality avatars\n\nDescribe the status of the issue.\n\nproposed\ndraft\nrejected\naccepted\ndeprecated\nsuperseded by\n\n\n\nList the deciders of the issue.\nV-Sekai,fire,Yin Chien YEAP,\n\n\nDescribe the tags of the issue.\nV-Sekai,avatars,\n\n\nContext and Problem Statement\nYin works a lot in webxr, and noticed in the avatar ecosystem (VRchat, secondlife, etc.) most of these avatars are too high quality.\nWhat tools have we come across that have enabled lightweight avatars?\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nTo try to make things work for webxr, yin is interested in lightweight avatars in as many ways as possible. exploring avatars that are as parametric as possible.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nFind ways to define volumes as parametric, and textures based on vectors instead of bitmaps.\nFrame time: Using a mobile chip gives less headroom re: polys that can be dropped. Download sizes. How long does loading take.\nYin doesn’t love blender, more focused on web based tools fit for mobile processors and reasonable download speeds.\nYin has been looking into procedural materials as a lightweight mechanism.\nThere are two systems, skeleton system and blendshapes. Conversion of blend shapes to skeletons is possible.\nCan also describe a quad subdivision workflow.\n\nquad based subdivision of detail https://github.com/godotengine/godot-proposals/issues/784\nprocedural materials\nbake blendshapes to skeletons\nFire is researching CSG based extraction combined with sliders. https://kacperkan.github.io/ucsgnet/ https://github.com/eliemichel/DagAmendment\n\n\n\nPositive Consequences\nWorks on the most widely accessible HMDs.\n\n\nNegative Consequences\nNo response\n\n\nOption graveyard\nNo response\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nHeavyweight avatars is a systematic problem.\n\n\nIs there a reason why this should be core and done by us?\nAvatars is our special area.\n\n\nReferences\n\nV-Sekai\n\n\n\nLicense of the contribution\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230911-xr-grid-with-drawing.html#prospects-for-the-future",
-    "href": "decisions/20230911-xr-grid-with-drawing.html#prospects-for-the-future",
-    "title": "Proposed: Improving xr grid with new enhancements",
+    "objectID": "decisions/20240522-webrtc-relay-test.html",
+    "href": "decisions/20240522-webrtc-relay-test.html",
+    "title": "Proposed: Draft WebRTC Relay Test",
     "section": "",
-    "text": "DETOX suggested creating a branch for the new features, while Fire expressed a desire to work on networking. They also discussed the possibility of building a tool similar to Cassie on the branch."
+    "text": "Status: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20230911-xr-grid-with-drawing.html#links",
-    "href": "decisions/20230911-xr-grid-with-drawing.html#links",
-    "title": "Proposed: Improving xr grid with new enhancements",
+    "objectID": "decisions/20240522-webrtc-relay-test.html#status",
+    "href": "decisions/20240522-webrtc-relay-test.html#status",
+    "title": "Proposed: Draft WebRTC Relay Test",
     "section": "",
-    "text": "V-Sekai\nThis article is assisted by AI."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20230806-v-sekai-ipad-projection-compatibility.html",
-    "href": "decisions/20230806-v-sekai-ipad-projection-compatibility.html",
-    "title": "Proposed: V-Sekai Navigation Compatibility with VR",
+    "objectID": "decisions/20240522-webrtc-relay-test.html#decision-makers",
+    "href": "decisions/20240522-webrtc-relay-test.html#decision-makers",
+    "title": "Proposed: Draft WebRTC Relay Test",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, iPad, Presentation Screen, Compatibility\n\n\n\n\nWe are developing a VR game that MUST be compatible with a wide range of devices. Our goal is to make our VR game accessible and enjoyable for this vast majority of users.\n\n\n\nThe challenge is to ensure the game’s user interface and controls work seamlessly across these different display sizes and touch interfaces.\n\n\n\nWe considered two options: Virtual joystick for touchscreen devices and Navmesh and 3D navigation points. We chose the “Virtual joystick for touchscreen devices” because it addresses the core issue of ensuring compatibility with iPads and large projector screens, and it is more cost-effective.\n\n\n\n\nImproved user experience across different devices and screen sizes.\nIncreased versatility of the game, making it suitable for various applications.\nEnhanced navigation in 3D spaces.\nMore cost-effective solution.\n\n\n\n\n\nPotential increase in development time and costs.\nAdditional resources for testing on different devices and screens.\n\n\n\n\nNavmeshes and 3D Navigation Points are tools used to define traversable spaces in a 3D environment. However, they might not be suitable when the spaces aren’t already defined, such as grids. Waypoints have similar limitations.\nIn Godot, any modification triggers a rebuild of the entire navigation map. If the map is large and complex, this rebuilding process can take a significant amount of time and lead to performance issues.\n\n\n\nWhile Navmesh and 3D Navigation Points provide an intuitive user interface for navigating 3D spaces, they might not translate well to continuous interaction on touchscreens, which is often expected by users on such devices.\n\n\n\nYes, the decision to implement a virtual joystick for touchscreen devices was made by us, V-Sekai. This decision is at the core of our strategy to ensure compatibility with iPads and large projector screens while also being cost-effective.\n\n\n\n\nV-Sekai\nThis article is assisted by AI."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20230806-v-sekai-ipad-projection-compatibility.html#metadata",
-    "href": "decisions/20230806-v-sekai-ipad-projection-compatibility.html#metadata",
-    "title": "Proposed: V-Sekai Navigation Compatibility with VR",
+    "objectID": "decisions/20240522-webrtc-relay-test.html#tags",
+    "href": "decisions/20240522-webrtc-relay-test.html#tags",
+    "title": "Proposed: Draft WebRTC Relay Test",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, iPad, Presentation Screen, Compatibility"
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20230806-v-sekai-ipad-projection-compatibility.html#the-backdrop",
-    "href": "decisions/20230806-v-sekai-ipad-projection-compatibility.html#the-backdrop",
-    "title": "Proposed: V-Sekai Navigation Compatibility with VR",
+    "objectID": "decisions/20240522-webrtc-relay-test.html#further-reading",
+    "href": "decisions/20240522-webrtc-relay-test.html#further-reading",
+    "title": "Proposed: Draft WebRTC Relay Test",
     "section": "",
-    "text": "We are developing a VR game that MUST be compatible with a wide range of devices. Our goal is to make our VR game accessible and enjoyable for this vast majority of users."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20230806-v-sekai-ipad-projection-compatibility.html#the-challenge",
-    "href": "decisions/20230806-v-sekai-ipad-projection-compatibility.html#the-challenge",
-    "title": "Proposed: V-Sekai Navigation Compatibility with VR",
+    "objectID": "decisions/20240330-hyperv-harvester-test.html",
+    "href": "decisions/20240330-hyperv-harvester-test.html",
+    "title": "Proposed: Hyperv windows Harvester Test",
     "section": "",
-    "text": "The challenge is to ensure the game’s user interface and controls work seamlessly across these different display sizes and touch interfaces."
+    "text": "Currently, we are operating a Kubernetes cluster in a Linux environment. However, the need to test our applications in a Windows environment has been identified. This is where Hyper-V Windows Harvester becomes relevant.\n\n\n\nOur existing testing environment does not cater to Windows-based applications. We require a solution that enables us to test these applications in a Windows environment without the necessity of setting up an entirely new cluster.\n\n\n\nWe can utilize Hyper-V to establish a Harvester HCI virtual machine (VM) on our current Windows desktop. Here’s a basic outline of the steps involved:\n\nInstall Hyper-V on the Windows desktop.\nCreate a new VM using Hyper-V.\nInstall Harvester HCI on the new VM.\nConfigure the Harvester HCI VM for our testing needs.\nRun tests on the Harvester HCI VM.\n\n\n\n\n\nEnables us to test Windows-based applications without the need for a separate Windows server.\nConserves resources by leveraging our existing infrastructure.\nEnhances our testing coverage and improves the quality of our software.\n\n\n\n\n\nRequires additional configuration and maintenance.\nPotential performance issues due to running a VM on top of the Windows desktop.\n\n\n\n\nWe could have opted to set up a separate Windows server for testing. However, this would necessitate significant resources and may not be cost-effective.\n\n\n\nThis setup might not be ideal if we need to run high-performance applications that demand all the resources of a dedicated server.\n\n\n\nThe implementation of this proposal will be carried out by our internal development team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20230806-v-sekai-ipad-projection-compatibility.html#the-strategy",
-    "href": "decisions/20230806-v-sekai-ipad-projection-compatibility.html#the-strategy",
-    "title": "Proposed: V-Sekai Navigation Compatibility with VR",
+    "objectID": "decisions/20240330-hyperv-harvester-test.html#the-context",
+    "href": "decisions/20240330-hyperv-harvester-test.html#the-context",
+    "title": "Proposed: Hyperv windows Harvester Test",
     "section": "",
-    "text": "We considered two options: Virtual joystick for touchscreen devices and Navmesh and 3D navigation points. We chose the “Virtual joystick for touchscreen devices” because it addresses the core issue of ensuring compatibility with iPads and large projector screens, and it is more cost-effective."
+    "text": "Currently, we are operating a Kubernetes cluster in a Linux environment. However, the need to test our applications in a Windows environment has been identified. This is where Hyper-V Windows Harvester becomes relevant."
   },
   {
-    "objectID": "decisions/20230806-v-sekai-ipad-projection-compatibility.html#the-upside",
-    "href": "decisions/20230806-v-sekai-ipad-projection-compatibility.html#the-upside",
-    "title": "Proposed: V-Sekai Navigation Compatibility with VR",
+    "objectID": "decisions/20240330-hyperv-harvester-test.html#the-problem-statement",
+    "href": "decisions/20240330-hyperv-harvester-test.html#the-problem-statement",
+    "title": "Proposed: Hyperv windows Harvester Test",
     "section": "",
-    "text": "Improved user experience across different devices and screen sizes.\nIncreased versatility of the game, making it suitable for various applications.\nEnhanced navigation in 3D spaces.\nMore cost-effective solution."
+    "text": "Our existing testing environment does not cater to Windows-based applications. We require a solution that enables us to test these applications in a Windows environment without the necessity of setting up an entirely new cluster."
   },
   {
-    "objectID": "decisions/20230806-v-sekai-ipad-projection-compatibility.html#the-downside",
-    "href": "decisions/20230806-v-sekai-ipad-projection-compatibility.html#the-downside",
-    "title": "Proposed: V-Sekai Navigation Compatibility with VR",
+    "objectID": "decisions/20240330-hyperv-harvester-test.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240330-hyperv-harvester-test.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Hyperv windows Harvester Test",
     "section": "",
-    "text": "Potential increase in development time and costs.\nAdditional resources for testing on different devices and screens."
+    "text": "We can utilize Hyper-V to establish a Harvester HCI virtual machine (VM) on our current Windows desktop. Here’s a basic outline of the steps involved:\n\nInstall Hyper-V on the Windows desktop.\nCreate a new VM using Hyper-V.\nInstall Harvester HCI on the new VM.\nConfigure the Harvester HCI VM for our testing needs.\nRun tests on the Harvester HCI VM."
   },
   {
-    "objectID": "decisions/20230806-v-sekai-ipad-projection-compatibility.html#the-road-not-taken",
-    "href": "decisions/20230806-v-sekai-ipad-projection-compatibility.html#the-road-not-taken",
-    "title": "Proposed: V-Sekai Navigation Compatibility with VR",
+    "objectID": "decisions/20240330-hyperv-harvester-test.html#the-benefits",
+    "href": "decisions/20240330-hyperv-harvester-test.html#the-benefits",
+    "title": "Proposed: Hyperv windows Harvester Test",
     "section": "",
-    "text": "Navmeshes and 3D Navigation Points are tools used to define traversable spaces in a 3D environment. However, they might not be suitable when the spaces aren’t already defined, such as grids. Waypoints have similar limitations.\nIn Godot, any modification triggers a rebuild of the entire navigation map. If the map is large and complex, this rebuilding process can take a significant amount of time and lead to performance issues."
+    "text": "Enables us to test Windows-based applications without the need for a separate Windows server.\nConserves resources by leveraging our existing infrastructure.\nEnhances our testing coverage and improves the quality of our software."
   },
   {
-    "objectID": "decisions/20230806-v-sekai-ipad-projection-compatibility.html#the-infrequent-use-case",
-    "href": "decisions/20230806-v-sekai-ipad-projection-compatibility.html#the-infrequent-use-case",
-    "title": "Proposed: V-Sekai Navigation Compatibility with VR",
+    "objectID": "decisions/20240330-hyperv-harvester-test.html#the-downsides",
+    "href": "decisions/20240330-hyperv-harvester-test.html#the-downsides",
+    "title": "Proposed: Hyperv windows Harvester Test",
     "section": "",
-    "text": "While Navmesh and 3D Navigation Points provide an intuitive user interface for navigating 3D spaces, they might not translate well to continuous interaction on touchscreens, which is often expected by users on such devices."
+    "text": "Requires additional configuration and maintenance.\nPotential performance issues due to running a VM on top of the Windows desktop."
   },
   {
-    "objectID": "decisions/20230806-v-sekai-ipad-projection-compatibility.html#in-core-and-done-by-us",
-    "href": "decisions/20230806-v-sekai-ipad-projection-compatibility.html#in-core-and-done-by-us",
-    "title": "Proposed: V-Sekai Navigation Compatibility with VR",
+    "objectID": "decisions/20240330-hyperv-harvester-test.html#the-road-not-taken",
+    "href": "decisions/20240330-hyperv-harvester-test.html#the-road-not-taken",
+    "title": "Proposed: Hyperv windows Harvester Test",
     "section": "",
-    "text": "Yes, the decision to implement a virtual joystick for touchscreen devices was made by us, V-Sekai. This decision is at the core of our strategy to ensure compatibility with iPads and large projector screens while also being cost-effective."
+    "text": "We could have opted to set up a separate Windows server for testing. However, this would necessitate significant resources and may not be cost-effective."
   },
   {
-    "objectID": "decisions/20230806-v-sekai-ipad-projection-compatibility.html#further-reading",
-    "href": "decisions/20230806-v-sekai-ipad-projection-compatibility.html#further-reading",
-    "title": "Proposed: V-Sekai Navigation Compatibility with VR",
+    "objectID": "decisions/20240330-hyperv-harvester-test.html#the-infrequent-use-case",
+    "href": "decisions/20240330-hyperv-harvester-test.html#the-infrequent-use-case",
+    "title": "Proposed: Hyperv windows Harvester Test",
     "section": "",
-    "text": "V-Sekai\nThis article is assisted by AI."
+    "text": "This setup might not be ideal if we need to run high-performance applications that demand all the resources of a dedicated server."
   },
   {
-    "objectID": "decisions/20210212-add-build-notifications.html",
-    "href": "decisions/20210212-add-build-notifications.html",
-    "title": "Proposed: Add build notifications",
+    "objectID": "decisions/20240330-hyperv-harvester-test.html#in-core-and-done-by-us",
+    "href": "decisions/20240330-hyperv-harvester-test.html#in-core-and-done-by-us",
+    "title": "Proposed: Hyperv windows Harvester Test",
     "section": "",
-    "text": "Add build notifications because we do not know when a build completed in the CI system to test it.\n\n\n\n\nChannels people use\n\n\n\n\n\nEmail notifications\nDiscord webhook notifications\n\n\n\n\nChosen option: Discord webhooks\n\n\n\nKnow when to test\nSystem stability\n\n\n\n\n\nEngineering effort\n\n\n\n\n\n\n\nUse the existing gocd email notifier.\n\nGood, because email is common\nBad, not everyone wants to use email\n\n\n\n\nMake a gocd Discord notifier\n\nGood, because everyone is on discord\nBad, because engineering needs to be done.\n\n\n\n\n\n\nhttps://docs.gocd.org/current/configuration/dev_notifications.html\nhttps://github.com/gocd-contrib/notification-skeleton-plugin\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "The implementation of this proposal will be carried out by our internal development team."
   },
   {
-    "objectID": "decisions/20210212-add-build-notifications.html#context-and-problem-statement",
-    "href": "decisions/20210212-add-build-notifications.html#context-and-problem-statement",
-    "title": "Proposed: Add build notifications",
+    "objectID": "decisions/20240330-hyperv-harvester-test.html#status",
+    "href": "decisions/20240330-hyperv-harvester-test.html#status",
+    "title": "Proposed: Hyperv windows Harvester Test",
     "section": "",
-    "text": "Add build notifications because we do not know when a build completed in the CI system to test it."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20210212-add-build-notifications.html#decision-drivers",
-    "href": "decisions/20210212-add-build-notifications.html#decision-drivers",
-    "title": "Proposed: Add build notifications",
+    "objectID": "decisions/20240330-hyperv-harvester-test.html#decision-makers",
+    "href": "decisions/20240330-hyperv-harvester-test.html#decision-makers",
+    "title": "Proposed: Hyperv windows Harvester Test",
     "section": "",
-    "text": "Channels people use"
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20210212-add-build-notifications.html#considered-options",
-    "href": "decisions/20210212-add-build-notifications.html#considered-options",
-    "title": "Proposed: Add build notifications",
+    "objectID": "decisions/20240330-hyperv-harvester-test.html#tags",
+    "href": "decisions/20240330-hyperv-harvester-test.html#tags",
+    "title": "Proposed: Hyperv windows Harvester Test",
     "section": "",
-    "text": "Email notifications\nDiscord webhook notifications"
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20210212-add-build-notifications.html#decision-outcome",
-    "href": "decisions/20210212-add-build-notifications.html#decision-outcome",
-    "title": "Proposed: Add build notifications",
+    "objectID": "decisions/20240330-hyperv-harvester-test.html#further-reading",
+    "href": "decisions/20240330-hyperv-harvester-test.html#further-reading",
+    "title": "Proposed: Hyperv windows Harvester Test",
     "section": "",
-    "text": "Chosen option: Discord webhooks\n\n\n\nKnow when to test\nSystem stability\n\n\n\n\n\nEngineering effort"
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20210212-add-build-notifications.html#pros-and-cons-of-the-options",
-    "href": "decisions/20210212-add-build-notifications.html#pros-and-cons-of-the-options",
-    "title": "Proposed: Add build notifications",
+    "objectID": "decisions/20230107-elixir-uro-dev-sqlite.html",
+    "href": "decisions/20230107-elixir-uro-dev-sqlite.html",
+    "title": "Accepted: How to start a EXPERIMENTAL environment for sqlite and elixir?",
     "section": "",
-    "text": "Use the existing gocd email notifier.\n\nGood, because email is common\nBad, not everyone wants to use email\n\n\n\n\nMake a gocd Discord notifier\n\nGood, because everyone is on discord\nBad, because engineering needs to be done."
+    "text": "Accepted: How to start a EXPERIMENTAL environment for sqlite and elixir?\n\nDescribe the status of the issue.\n\nproposed\ndraft\nrejected\naccepted\ndeprecated\nsuperseded by\n\n\n\nList the deciders of the issue.\nV-Sekai,lyuma,fire,\n\n\nDescribe the tags of the issue.\nV-Sekai,\n\n\nContext and Problem Statement\nHow do we start our uro backend?\nUSE 20220531-elixir-uro-dev.md for the production URO\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nWrite documentation how to update elixir.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nCompile uro. You will need Elixir installed.\nI recommend getting the latest, but for these steps, I am using Elixir v1.14.4.\nDownload Uro from https://github.com/V-Sekai/uro\nWe are using the dev environment. It is the default, but you can also set MIX_ENV=dev.\nTo compile HTML/CSS webpack:\ncd assets\nnpm install\nnpm run deploy\ncd ..\nIf the compile gives issues, you can run it multiple times. To compile dependencies:\nmix do compile, phx.digest\nIf one of them gives an error due to nmake or not having a compiler, you can fix it by opening a x64 Native Tools command prompt from visual studio and run mix deps.compile bcrypt_elixir\nFinally, create and migrate the database and start the development server:\nmix ecto.create\nmix ecto.migrate\niex.bat --werl -S mix phx.server\nThis will start uro at http://localhost:4000/\nCreate a user in the website register user page.\nGo to the console and set the user to be admin.\niex.bat --werl -S mix phx.server\n# TODO\n# Call Uro.Accounts.update_user_as_admin\nGitHub - V-Sekai/uro: Server backend for V-Sekai written in Elixir …\nThe docker image docker-uro is compiled using GoCD, so after pushing, check that the pipeline ran.\nThen, go to DockerHub at https://hub.docker.com/r/groupsinfra/uro/tags and check the most recently pushed tag (it will not be the latest one, but instead a specific version).\nNow, edit the flux config at https://github.com/V-Sekai/flux-config/blob/flux2/workloads/uro-deployment.yaml and replace the uro image version with the tag from above.\nCheck that uro-deployment was updated.\n\n\nPositive Consequences\nWe’re able to update uro!\n\n\nNegative Consequences\nNo response\n\n\nOption graveyard\nNo response\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nIt’s arguably a few lines of script, but it’s our script!\n\n\nIs there a reason why this should be core and done by us?\nWe maintain the website.\n\n\nReferences\n\nV-Sekai\nUro\nhttps://github.com/V-Sekai/uro/issues/52\n\n\n\nLicense of the contribution\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20210212-add-build-notifications.html#references",
-    "href": "decisions/20210212-add-build-notifications.html#references",
-    "title": "Proposed: Add build notifications",
+    "objectID": "decisions/20231024-training-simulators.html",
+    "href": "decisions/20231024-training-simulators.html",
+    "title": "Proposed: Implementing Advanced Training Simulators in V-Sekai",
     "section": "",
-    "text": "https://docs.gocd.org/current/configuration/dev_notifications.html\nhttps://github.com/gocd-contrib/notification-skeleton-plugin"
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, Game Development, Skill Simulation\n\n\n\n\nIn the world of V-Sekai, players can level up their skills and unlock advanced training simulators. These simulators provide access to comprehensive Standard Operating Procedures (SOPs) and allow players to practice actions in a safe environment.\n\n\n\nThe challenge lies in creating an immersive and realistic simulation experience that doesn’t harm the player’s character. For instance, if a player is an engineer, they should be able to practice replacing a plasma conduit, learn how to use the tools, and understand how to safely isolate sections for repairs.\n\n\n\nTo overcome this challenge, we propose developing a robust system that allows players to interact with the game environment in a meaningful way. This includes creating detailed SOPs, designing intuitive user interfaces for tool manipulation, and implementing safety measures within the game.\n\n\n\nBy providing a realistic and immersive simulation experience, we can enhance player engagement and satisfaction. Players will have the opportunity to learn and practice new skills, which can add depth to the gameplay.\n\n\n\nThe main downside is the complexity and resources required to implement such a system. It may also be challenging to balance realism with fun gameplay.\n\n\n\nAn alternative approach could be to simplify the skill system and focus more on traditional gameplay elements. However, this would not provide the same level of immersion and learning opportunities for the players.\n\n\n\nIn some cases, players may prefer a more straightforward gameplay experience and may not fully utilize the advanced training simulators.\n\n\n\nYes, this feature is core to the V-Sekai experience and will be developed by our team.\n\n\n\n\nV-Sekai\nAI assists this article."
   },
   {
-    "objectID": "decisions/20210212-add-build-notifications.html#derivative-license",
-    "href": "decisions/20210212-add-build-notifications.html#derivative-license",
-    "title": "Proposed: Add build notifications",
+    "objectID": "decisions/20231024-training-simulators.html#metadata",
+    "href": "decisions/20231024-training-simulators.html#metadata",
+    "title": "Proposed: Implementing Advanced Training Simulators in V-Sekai",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, Game Development, Skill Simulation"
   },
   {
-    "objectID": "decisions/20220217-omi-chan-oni-chan.html",
-    "href": "decisions/20220217-omi-chan-oni-chan.html",
-    "title": "Accepted: To create omi chan rig a #256FES",
+    "objectID": "decisions/20231024-training-simulators.html#the-backdrop",
+    "href": "decisions/20231024-training-simulators.html#the-backdrop",
+    "title": "Proposed: Implementing Advanced Training Simulators in V-Sekai",
     "section": "",
-    "text": "Status: accepted \nDeciders: V-Sekai,jeana,fire,\nTags: V-Sekai,\n\n\n\nFormed an OMI Chan working group.\nTo create omi chan rig a #256FES.\n\n\n\nUse my know-how to rig a #256fes character.\n\n\n\n\n\n\n\nimage\n\n\n\nGiven mesh model that is unrigged and #256FES\n\n\n\nForearm is out of proportion\nHead is out of proportion\nNo base color\n\n\n\n\n\nhttps://github.com/saturday06/VRM_Addon_for_Blender/releases/tag/2_1_9\nCreate a vrm default armature template in Blender 3.0.1\nScale equally the entire mesh to be 1.7m (female Caucasian female on the tall statistical range)\nEnable equal scaling of bones button\nScale the arms and the neck/head\nUse autorig https://blendermarket.com/products/voxel-heat-diffuse-skinning\nUse xatlas to generate uv\nhttps://github.com/V-Sekai/V-Sekai-Blender-tools/tree/main/addons/blender_xatlas\nhttps://github.com/V-Sekai/V-Sekai-Blender-tools/tree/main/addons/Principled-Baker-master to bake uvs\nhttps://github.com/V-Sekai/V-Sekai-Blender-tools/tree/main/addons/corrective_smooth_baker\nExport to vrm\nAdd VRM mtoon material\nMake VRM mtoon material use black as shaded color.\nTest in 3tene and cluster.mu\nhttps://3d.kalidoface.com/ (first photo)\n\n\n\n\n\n\nWritten steps to vrm rigging #fes256\n\n\n\n\n\nMight be still too hard.\n\n\n\n\n\nOption: current situation.\nRejection Reason: No changes.\n\n\n\n\nThis uses several plugins of code.\n\n\n\nI know how to do it!\n\n\n\n\nReleased under the same license as Jeana’s work. CC-BY or CC0 if in doubt.\nSK_omi_chan_oni_chan.zip\n\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "In the world of V-Sekai, players can level up their skills and unlock advanced training simulators. These simulators provide access to comprehensive Standard Operating Procedures (SOPs) and allow players to practice actions in a safe environment."
   },
   {
-    "objectID": "decisions/20220217-omi-chan-oni-chan.html#context-and-problem-statement",
-    "href": "decisions/20220217-omi-chan-oni-chan.html#context-and-problem-statement",
-    "title": "Accepted: To create omi chan rig a #256FES",
+    "objectID": "decisions/20231024-training-simulators.html#the-challenge",
+    "href": "decisions/20231024-training-simulators.html#the-challenge",
+    "title": "Proposed: Implementing Advanced Training Simulators in V-Sekai",
     "section": "",
-    "text": "Formed an OMI Chan working group.\nTo create omi chan rig a #256FES."
+    "text": "The challenge lies in creating an immersive and realistic simulation experience that doesn’t harm the player’s character. For instance, if a player is an engineer, they should be able to practice replacing a plasma conduit, learn how to use the tools, and understand how to safely isolate sections for repairs."
   },
   {
-    "objectID": "decisions/20220217-omi-chan-oni-chan.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20220217-omi-chan-oni-chan.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Accepted: To create omi chan rig a #256FES",
+    "objectID": "decisions/20231024-training-simulators.html#the-strategy",
+    "href": "decisions/20231024-training-simulators.html#the-strategy",
+    "title": "Proposed: Implementing Advanced Training Simulators in V-Sekai",
     "section": "",
-    "text": "Use my know-how to rig a #256fes character."
+    "text": "To overcome this challenge, we propose developing a robust system that allows players to interact with the game environment in a meaningful way. This includes creating detailed SOPs, designing intuitive user interfaces for tool manipulation, and implementing safety measures within the game."
   },
   {
-    "objectID": "decisions/20220217-omi-chan-oni-chan.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20220217-omi-chan-oni-chan.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Accepted: To create omi chan rig a #256FES",
+    "objectID": "decisions/20231024-training-simulators.html#the-upside",
+    "href": "decisions/20231024-training-simulators.html#the-upside",
+    "title": "Proposed: Implementing Advanced Training Simulators in V-Sekai",
     "section": "",
-    "text": "image\n\n\n\nGiven mesh model that is unrigged and #256FES\n\n\n\nForearm is out of proportion\nHead is out of proportion\nNo base color\n\n\n\n\n\nhttps://github.com/saturday06/VRM_Addon_for_Blender/releases/tag/2_1_9\nCreate a vrm default armature template in Blender 3.0.1\nScale equally the entire mesh to be 1.7m (female Caucasian female on the tall statistical range)\nEnable equal scaling of bones button\nScale the arms and the neck/head\nUse autorig https://blendermarket.com/products/voxel-heat-diffuse-skinning\nUse xatlas to generate uv\nhttps://github.com/V-Sekai/V-Sekai-Blender-tools/tree/main/addons/blender_xatlas\nhttps://github.com/V-Sekai/V-Sekai-Blender-tools/tree/main/addons/Principled-Baker-master to bake uvs\nhttps://github.com/V-Sekai/V-Sekai-Blender-tools/tree/main/addons/corrective_smooth_baker\nExport to vrm\nAdd VRM mtoon material\nMake VRM mtoon material use black as shaded color.\nTest in 3tene and cluster.mu\nhttps://3d.kalidoface.com/ (first photo)"
+    "text": "By providing a realistic and immersive simulation experience, we can enhance player engagement and satisfaction. Players will have the opportunity to learn and practice new skills, which can add depth to the gameplay."
   },
   {
-    "objectID": "decisions/20220217-omi-chan-oni-chan.html#positive-consequences",
-    "href": "decisions/20220217-omi-chan-oni-chan.html#positive-consequences",
-    "title": "Accepted: To create omi chan rig a #256FES",
+    "objectID": "decisions/20231024-training-simulators.html#the-downside",
+    "href": "decisions/20231024-training-simulators.html#the-downside",
+    "title": "Proposed: Implementing Advanced Training Simulators in V-Sekai",
     "section": "",
-    "text": "Written steps to vrm rigging #fes256"
+    "text": "The main downside is the complexity and resources required to implement such a system. It may also be challenging to balance realism with fun gameplay."
   },
   {
-    "objectID": "decisions/20220217-omi-chan-oni-chan.html#negative-consequences",
-    "href": "decisions/20220217-omi-chan-oni-chan.html#negative-consequences",
-    "title": "Accepted: To create omi chan rig a #256FES",
+    "objectID": "decisions/20231024-training-simulators.html#the-road-not-taken",
+    "href": "decisions/20231024-training-simulators.html#the-road-not-taken",
+    "title": "Proposed: Implementing Advanced Training Simulators in V-Sekai",
     "section": "",
-    "text": "Might be still too hard."
+    "text": "An alternative approach could be to simplify the skill system and focus more on traditional gameplay elements. However, this would not provide the same level of immersion and learning opportunities for the players."
   },
   {
-    "objectID": "decisions/20220217-omi-chan-oni-chan.html#option-graveyard",
-    "href": "decisions/20220217-omi-chan-oni-chan.html#option-graveyard",
-    "title": "Accepted: To create omi chan rig a #256FES",
+    "objectID": "decisions/20231024-training-simulators.html#the-infrequent-use-case",
+    "href": "decisions/20231024-training-simulators.html#the-infrequent-use-case",
+    "title": "Proposed: Implementing Advanced Training Simulators in V-Sekai",
     "section": "",
-    "text": "Option: current situation.\nRejection Reason: No changes."
+    "text": "In some cases, players may prefer a more straightforward gameplay experience and may not fully utilize the advanced training simulators."
   },
   {
-    "objectID": "decisions/20220217-omi-chan-oni-chan.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20220217-omi-chan-oni-chan.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Accepted: To create omi chan rig a #256FES",
+    "objectID": "decisions/20231024-training-simulators.html#in-core-and-done-by-us",
+    "href": "decisions/20231024-training-simulators.html#in-core-and-done-by-us",
+    "title": "Proposed: Implementing Advanced Training Simulators in V-Sekai",
     "section": "",
-    "text": "This uses several plugins of code."
+    "text": "Yes, this feature is core to the V-Sekai experience and will be developed by our team."
   },
   {
-    "objectID": "decisions/20220217-omi-chan-oni-chan.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20220217-omi-chan-oni-chan.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Accepted: To create omi chan rig a #256FES",
+    "objectID": "decisions/20231024-training-simulators.html#further-reading",
+    "href": "decisions/20231024-training-simulators.html#further-reading",
+    "title": "Proposed: Implementing Advanced Training Simulators in V-Sekai",
     "section": "",
-    "text": "I know how to do it!"
+    "text": "V-Sekai\nAI assists this article."
   },
   {
-    "objectID": "decisions/20220217-omi-chan-oni-chan.html#references",
-    "href": "decisions/20220217-omi-chan-oni-chan.html#references",
-    "title": "Accepted: To create omi chan rig a #256FES",
+    "objectID": "decisions/20220131-run-own-infrastructure.html",
+    "href": "decisions/20220131-run-own-infrastructure.html",
+    "title": "Rejected: To allow independent deployment run our own infrastructure",
     "section": "",
-    "text": "Released under the same license as Jeana’s work. CC-BY or CC0 if in doubt.\nSK_omi_chan_oni_chan.zip"
+    "text": "Status: rejected \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nIt needs to be possible to replicate (or substitute) all of the existing infrasture and setup. This is important for a few reasons:\n\nThe current host may disappear or the physical hardware could break (as it is not in a cloud)\nPart of our project’s purpose is to allow anyone to fork the project or run their own version V-Sekai however they want.\nAs a use for “staging” or testing changes to infrastructure.\nAs a means for replicating live data such as CDN content, metadata or other databases. (some assets may depend on other assets in the future)\n\n\n\n\n\nRun TrueNAS Scale in DigitalOcean (Droplet/standalone VM, not kubernetes).\n(It should be possible in other cloud providers, and on own infrastructure, but we will pick this environment to focus on)\nWrite TrueNAS Scale charts for gocd; cockroachdb; uro\nLetsEncrypt certs require open port 443 or 80 for http01; or any dns01 provider using a plugin.\nTrueNAS Scale supports backups and snapshots.\n\n\n\n\n\nCreate new droplet. (Minimum configuration????):\n\nCustom Image -&gt; pick our TrueNAS image or some custom one we make.\nBasic: pick a number of cpus. Direct storage is only used for the OS.\nAdd a block volume for $10. TrueNAS requires a separate block device.\nDo not enable backups because TrueNAS has its own backup systems.\n\nAdd one extra block volume after the machine spins up to get redundancy (RAID-1?)\n(Note that block volumes can be moved between VMs, so doing things this way gives pretty good redundancy.\n\n\n\n\n\nGiving people many ways to remix, host or fork our work is part of our mission.\nIt will give us a way to quickly spin up redundant infrastructure in the cloud, either if a disaster happens or we want to scale.\n\n\n\n\n\nSupporting more configurations will take more time from us.\n\n[this section can be repeated for each option if more than one option is open for consideration]\n\n\n\n\nOption: Support only bare metal infrastructure\nRejection Reason: This is not ideal unless you are at scale, because bare metal can die and cannot scale.\n\n\n\n\nThis project is to document what the script will be\n\n\n\nInfra is part of our mission.\n\n\n\n\nhttps://docs.digitalocean.com/products/volumes/how-to/move-between-droplets/\n\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20220217-omi-chan-oni-chan.html#derivative-license",
-    "href": "decisions/20220217-omi-chan-oni-chan.html#derivative-license",
-    "title": "Accepted: To create omi chan rig a #256FES",
+    "objectID": "decisions/20220131-run-own-infrastructure.html#context-and-problem-statement",
+    "href": "decisions/20220131-run-own-infrastructure.html#context-and-problem-statement",
+    "title": "Rejected: To allow independent deployment run our own infrastructure",
     "section": "",
-    "text": "Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "It needs to be possible to replicate (or substitute) all of the existing infrasture and setup. This is important for a few reasons:\n\nThe current host may disappear or the physical hardware could break (as it is not in a cloud)\nPart of our project’s purpose is to allow anyone to fork the project or run their own version V-Sekai however they want.\nAs a use for “staging” or testing changes to infrastructure.\nAs a means for replicating live data such as CDN content, metadata or other databases. (some assets may depend on other assets in the future)"
   },
   {
-    "objectID": "decisions/20230527-server-sidecar.html",
-    "href": "decisions/20230527-server-sidecar.html",
-    "title": "Proposed: Efficiently managing and synchronizing game data with a server sidecar",
+    "objectID": "decisions/20220131-run-own-infrastructure.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20220131-run-own-infrastructure.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Rejected: To allow independent deployment run our own infrastructure",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai, Bioblaze Payne, fire\nTags: V-Sekai, GPT-4\n\n\n\n\nV-Sekai is facing a problem with efficiently managing and synchronizing data across multiple devices and platforms.\nThe goal is to find a more reliable and efficient solution for data synchronization that can handle large amounts of data, minimize latency, and ensure data consistency across all devices and platforms.\n\n\n\nWe propose a new approach that involves directly inserting data into the MVSQLite cluster database and implementing a robust syncing mechanism to ensure data consistency across all devices and platforms.\n\nModify the editor export process to stream MVSQLite to the Godot Engine server.\nSchedule externally consistent syncing of MVSQLite with the Godot Engine server (1 frame).\nSchedule periodic syncing of MVSQLite to a backup (e.g., every 30 minutes).\n\n\n\n\n# Step 1: Insert MVSQLite data directly into the MVSQLite database.\nfunc insert_data_to_database():\n    var mvsqlite_data = get_mvsqlite_data()\n    var db = MVSQLite.new()\n    db.open(\"user://your_database_name.db\")\n    for data in mvsqlite_data:\n        db.execute(\"INSERT INTO your_table_name (column1, column2) VALUES (?, ?)\", [data.column1, data.column2])\n    db.close()\n\n# Step 2: Schedule externally consistent syncing of MVSQLite with the SQLite database (1 frame).\nfunc _process(delta):\n    if should_sync():\n        insert_data_to_database()\n\n# Step 3: Schedule periodic syncing of MVSQLite to a backup (e.g., every 30 minutes).\nvar backup_timer = Timer.new()\nfunc _ready():\n    backup_timer.set_wait_time(1800) # 30 minutes in seconds\n    backup_timer.connect(\"timeout\", self, \"_on_backup_timer_timeout\")\n    add_child(backup_timer)\n    backup_timer.start()\n\nfunc _on_backup_timer_timeout():\n    insert_data_to_database()\n\n# Helper functions\nfunc get_mvsqlite_data():\n    # Placeholder for obtaining MVSQLite data from the project\n    pass\n\nfunc should_sync():\n    # Placeholder for determining when to sync MVSQLite data with the SQLite database\n    pass\n\n\n\n\nImproved data management and performance.\nEnhanced security through server validation and sanitization.\nReduced load on the client-side.\n\n\n\n\n\nIncreased complexity in the system architecture.\nPotential challenges in implementing the new architecture.\n\n\n\n\n\nClient-side caching: Storing data on the client-side to reduce server load. However, this approach can lead to security vulnerabilities and inconsistent data across clients.\nStatic file export: Exporting data as static files instead of using MVSQLite. This option was rejected due to limited flexibility and scalability.\n\nThese options were considered but ultimately rejected in favor of the proposed solution, which aims to balance performance, security, and maintainability.\n\n\n\nThe proposed enhancement is designed to address core limitations in V-Sekai’s architecture and cannot be easily worked around with a few lines of script.\n\n\n\nImplementing this solution at the core level ensures that all users benefit from improved data management, performance, and security. Additionally, addressing these limitations at the core level allows for better integration with other components of the system.\n\n\n\n\nV-Sekai"
+    "text": "Run TrueNAS Scale in DigitalOcean (Droplet/standalone VM, not kubernetes).\n(It should be possible in other cloud providers, and on own infrastructure, but we will pick this environment to focus on)\nWrite TrueNAS Scale charts for gocd; cockroachdb; uro\nLetsEncrypt certs require open port 443 or 80 for http01; or any dns01 provider using a plugin.\nTrueNAS Scale supports backups and snapshots."
   },
   {
-    "objectID": "decisions/20230527-server-sidecar.html#metadata",
-    "href": "decisions/20230527-server-sidecar.html#metadata",
-    "title": "Proposed: Efficiently managing and synchronizing game data with a server sidecar",
+    "objectID": "decisions/20220131-run-own-infrastructure.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20220131-run-own-infrastructure.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Rejected: To allow independent deployment run our own infrastructure",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai, Bioblaze Payne, fire\nTags: V-Sekai, GPT-4"
+    "text": "Create new droplet. (Minimum configuration????):\n\nCustom Image -&gt; pick our TrueNAS image or some custom one we make.\nBasic: pick a number of cpus. Direct storage is only used for the OS.\nAdd a block volume for $10. TrueNAS requires a separate block device.\nDo not enable backups because TrueNAS has its own backup systems.\n\nAdd one extra block volume after the machine spins up to get redundancy (RAID-1?)\n(Note that block volumes can be moved between VMs, so doing things this way gives pretty good redundancy."
   },
   {
-    "objectID": "decisions/20230527-server-sidecar.html#context-and-problem-statement",
-    "href": "decisions/20230527-server-sidecar.html#context-and-problem-statement",
-    "title": "Proposed: Efficiently managing and synchronizing game data with a server sidecar",
+    "objectID": "decisions/20220131-run-own-infrastructure.html#positive-consequences",
+    "href": "decisions/20220131-run-own-infrastructure.html#positive-consequences",
+    "title": "Rejected: To allow independent deployment run our own infrastructure",
     "section": "",
-    "text": "V-Sekai is facing a problem with efficiently managing and synchronizing data across multiple devices and platforms.\nThe goal is to find a more reliable and efficient solution for data synchronization that can handle large amounts of data, minimize latency, and ensure data consistency across all devices and platforms."
+    "text": "Giving people many ways to remix, host or fork our work is part of our mission.\nIt will give us a way to quickly spin up redundant infrastructure in the cloud, either if a disaster happens or we want to scale."
   },
   {
-    "objectID": "decisions/20230527-server-sidecar.html#proposed-solution",
-    "href": "decisions/20230527-server-sidecar.html#proposed-solution",
-    "title": "Proposed: Efficiently managing and synchronizing game data with a server sidecar",
+    "objectID": "decisions/20220131-run-own-infrastructure.html#negative-consequences",
+    "href": "decisions/20220131-run-own-infrastructure.html#negative-consequences",
+    "title": "Rejected: To allow independent deployment run our own infrastructure",
     "section": "",
-    "text": "We propose a new approach that involves directly inserting data into the MVSQLite cluster database and implementing a robust syncing mechanism to ensure data consistency across all devices and platforms.\n\nModify the editor export process to stream MVSQLite to the Godot Engine server.\nSchedule externally consistent syncing of MVSQLite with the Godot Engine server (1 frame).\nSchedule periodic syncing of MVSQLite to a backup (e.g., every 30 minutes)."
+    "text": "Supporting more configurations will take more time from us.\n\n[this section can be repeated for each option if more than one option is open for consideration]"
   },
   {
-    "objectID": "decisions/20230527-server-sidecar.html#implementation",
-    "href": "decisions/20230527-server-sidecar.html#implementation",
-    "title": "Proposed: Efficiently managing and synchronizing game data with a server sidecar",
+    "objectID": "decisions/20220131-run-own-infrastructure.html#option-graveyard",
+    "href": "decisions/20220131-run-own-infrastructure.html#option-graveyard",
+    "title": "Rejected: To allow independent deployment run our own infrastructure",
     "section": "",
-    "text": "# Step 1: Insert MVSQLite data directly into the MVSQLite database.\nfunc insert_data_to_database():\n    var mvsqlite_data = get_mvsqlite_data()\n    var db = MVSQLite.new()\n    db.open(\"user://your_database_name.db\")\n    for data in mvsqlite_data:\n        db.execute(\"INSERT INTO your_table_name (column1, column2) VALUES (?, ?)\", [data.column1, data.column2])\n    db.close()\n\n# Step 2: Schedule externally consistent syncing of MVSQLite with the SQLite database (1 frame).\nfunc _process(delta):\n    if should_sync():\n        insert_data_to_database()\n\n# Step 3: Schedule periodic syncing of MVSQLite to a backup (e.g., every 30 minutes).\nvar backup_timer = Timer.new()\nfunc _ready():\n    backup_timer.set_wait_time(1800) # 30 minutes in seconds\n    backup_timer.connect(\"timeout\", self, \"_on_backup_timer_timeout\")\n    add_child(backup_timer)\n    backup_timer.start()\n\nfunc _on_backup_timer_timeout():\n    insert_data_to_database()\n\n# Helper functions\nfunc get_mvsqlite_data():\n    # Placeholder for obtaining MVSQLite data from the project\n    pass\n\nfunc should_sync():\n    # Placeholder for determining when to sync MVSQLite data with the SQLite database\n    pass"
+    "text": "Option: Support only bare metal infrastructure\nRejection Reason: This is not ideal unless you are at scale, because bare metal can die and cannot scale."
   },
   {
-    "objectID": "decisions/20230527-server-sidecar.html#positive-consequences",
-    "href": "decisions/20230527-server-sidecar.html#positive-consequences",
-    "title": "Proposed: Efficiently managing and synchronizing game data with a server sidecar",
+    "objectID": "decisions/20220131-run-own-infrastructure.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20220131-run-own-infrastructure.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Rejected: To allow independent deployment run our own infrastructure",
     "section": "",
-    "text": "Improved data management and performance.\nEnhanced security through server validation and sanitization.\nReduced load on the client-side."
+    "text": "This project is to document what the script will be"
   },
   {
-    "objectID": "decisions/20230527-server-sidecar.html#negative-consequences",
-    "href": "decisions/20230527-server-sidecar.html#negative-consequences",
-    "title": "Proposed: Efficiently managing and synchronizing game data with a server sidecar",
+    "objectID": "decisions/20220131-run-own-infrastructure.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20220131-run-own-infrastructure.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Rejected: To allow independent deployment run our own infrastructure",
     "section": "",
-    "text": "Increased complexity in the system architecture.\nPotential challenges in implementing the new architecture."
+    "text": "Infra is part of our mission."
   },
   {
-    "objectID": "decisions/20230527-server-sidecar.html#option-graveyard",
-    "href": "decisions/20230527-server-sidecar.html#option-graveyard",
-    "title": "Proposed: Efficiently managing and synchronizing game data with a server sidecar",
+    "objectID": "decisions/20220131-run-own-infrastructure.html#references",
+    "href": "decisions/20220131-run-own-infrastructure.html#references",
+    "title": "Rejected: To allow independent deployment run our own infrastructure",
     "section": "",
-    "text": "Client-side caching: Storing data on the client-side to reduce server load. However, this approach can lead to security vulnerabilities and inconsistent data across clients.\nStatic file export: Exporting data as static files instead of using MVSQLite. This option was rejected due to limited flexibility and scalability.\n\nThese options were considered but ultimately rejected in favor of the proposed solution, which aims to balance performance, security, and maintainability."
+    "text": "https://docs.digitalocean.com/products/volumes/how-to/move-between-droplets/"
   },
   {
-    "objectID": "decisions/20230527-server-sidecar.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230527-server-sidecar.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Efficiently managing and synchronizing game data with a server sidecar",
+    "objectID": "decisions/20220131-run-own-infrastructure.html#derivative-license",
+    "href": "decisions/20220131-run-own-infrastructure.html#derivative-license",
+    "title": "Rejected: To allow independent deployment run our own infrastructure",
     "section": "",
-    "text": "The proposed enhancement is designed to address core limitations in V-Sekai’s architecture and cannot be easily worked around with a few lines of script."
+    "text": "Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230527-server-sidecar.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230527-server-sidecar.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Efficiently managing and synchronizing game data with a server sidecar",
+    "objectID": "decisions/20240623-only-save-tools-in-our-cdn.html",
+    "href": "decisions/20240623-only-save-tools-in-our-cdn.html",
+    "title": "Proposal: Only Save Tools in Our CDN",
     "section": "",
-    "text": "Implementing this solution at the core level ensures that all users benefit from improved data management, performance, and security. Additionally, addressing these limitations at the core level allows for better integration with other components of the system."
+    "text": "Currently, our Content Delivery Network (CDN) is responsible for storing a variety of assets. These include home world props, avatars, worlds, V-Sekai tools, and our sources.\n\n\n\nThe main issue we face is the need to optimize storage space while ensuring that essential tools are readily accessible for use.\n\n\n\nOur proposed solution is to limit the types of assets stored in our CDN. Specifically, we suggest not saving home world props, avatars, or worlds in our CDN. This would help conserve storage space. Instead, we would focus on storing only the V-Sekai tools and our tool sources. The underlying idea is that homeworlds should be responsible for storing their own content.\n\n\n\nThis strategy ensures the sovereignty of the content by allowing each homeworld to manage its own assets.\n\n\n\nThere may be potential issues with accessibility and latency as homeworlds will have to manage their own content delivery.\n\n\n\nAn alternative approach could have been to upgrade our CDN to accommodate all types of assets. However, this would increase costs and still not address the issue of content sovereignty.\n\n\n\nIn cases where a homeworld’s server is down or experiencing issues, users might not be able to access certain assets.\n\n\n\nThe implementation of this proposal will be done by us, the V-Sekai development team. It aligns with our core principle of decentralization and user empowerment.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis proposal was assisted by AI assistant Aria."
   },
   {
-    "objectID": "decisions/20230527-server-sidecar.html#references",
-    "href": "decisions/20230527-server-sidecar.html#references",
-    "title": "Proposed: Efficiently managing and synchronizing game data with a server sidecar",
+    "objectID": "decisions/20240623-only-save-tools-in-our-cdn.html#context",
+    "href": "decisions/20240623-only-save-tools-in-our-cdn.html#context",
+    "title": "Proposal: Only Save Tools in Our CDN",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Currently, our Content Delivery Network (CDN) is responsible for storing a variety of assets. These include home world props, avatars, worlds, V-Sekai tools, and our sources."
   },
   {
-    "objectID": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html",
-    "href": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html",
-    "title": "Accepted: Complete glTF2 / VRM import and export pipeline in Godot Engine",
+    "objectID": "decisions/20240623-only-save-tools-in-our-cdn.html#problem-statement",
+    "href": "decisions/20240623-only-save-tools-in-our-cdn.html#problem-statement",
+    "title": "Proposal: Only Save Tools in Our CDN",
     "section": "",
-    "text": "We are unable to import characters in animations and unable to export them.\n\n\n\nVRM and glTF import allows us to bring models in and export allows us to get the models out.\n\n\n\nTo be determined.\n\n\n\n\nCharacter import supports\nWorld export support\n\n\n\n\n\nTechnical debt\n\n(this section can be repeated for each option, if more than one option is open for consideration\n\n\n\nList the proposed options no longer open for consideration.\nList the reasons for the rejection: (the Bad traits)\n\nRequires GDNative\nComplicated\n\n\n\n\nPossible to be gdscript\n\n\n\nWe need to provide trust for the toolchains.\n\n\n\n\nNotary Trust\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "The main issue we face is the need to optimize storage space while ensuring that essential tools are readily accessible for use."
   },
   {
-    "objectID": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html#context-and-problem-statement",
-    "href": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html#context-and-problem-statement",
-    "title": "Accepted: Complete glTF2 / VRM import and export pipeline in Godot Engine",
+    "objectID": "decisions/20240623-only-save-tools-in-our-cdn.html#proposed-solution",
+    "href": "decisions/20240623-only-save-tools-in-our-cdn.html#proposed-solution",
+    "title": "Proposal: Only Save Tools in Our CDN",
     "section": "",
-    "text": "We are unable to import characters in animations and unable to export them."
+    "text": "Our proposed solution is to limit the types of assets stored in our CDN. Specifically, we suggest not saving home world props, avatars, or worlds in our CDN. This would help conserve storage space. Instead, we would focus on storing only the V-Sekai tools and our tool sources. The underlying idea is that homeworlds should be responsible for storing their own content."
   },
   {
-    "objectID": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Accepted: Complete glTF2 / VRM import and export pipeline in Godot Engine",
+    "objectID": "decisions/20240623-only-save-tools-in-our-cdn.html#benefits",
+    "href": "decisions/20240623-only-save-tools-in-our-cdn.html#benefits",
+    "title": "Proposal: Only Save Tools in Our CDN",
     "section": "",
-    "text": "VRM and glTF import allows us to bring models in and export allows us to get the models out."
+    "text": "This strategy ensures the sovereignty of the content by allowing each homeworld to manage its own assets."
   },
   {
-    "objectID": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-andor-diagrams",
-    "href": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-andor-diagrams",
-    "title": "Accepted: Complete glTF2 / VRM import and export pipeline in Godot Engine",
+    "objectID": "decisions/20240623-only-save-tools-in-our-cdn.html#downsides",
+    "href": "decisions/20240623-only-save-tools-in-our-cdn.html#downsides",
+    "title": "Proposal: Only Save Tools in Our CDN",
     "section": "",
-    "text": "To be determined."
+    "text": "There may be potential issues with accessibility and latency as homeworlds will have to manage their own content delivery."
   },
   {
-    "objectID": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html#positive-consequences",
-    "href": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html#positive-consequences",
-    "title": "Accepted: Complete glTF2 / VRM import and export pipeline in Godot Engine",
+    "objectID": "decisions/20240623-only-save-tools-in-our-cdn.html#the-road-not-taken",
+    "href": "decisions/20240623-only-save-tools-in-our-cdn.html#the-road-not-taken",
+    "title": "Proposal: Only Save Tools in Our CDN",
     "section": "",
-    "text": "Character import supports\nWorld export support"
+    "text": "An alternative approach could have been to upgrade our CDN to accommodate all types of assets. However, this would increase costs and still not address the issue of content sovereignty."
   },
   {
-    "objectID": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html#negative-consequences",
-    "href": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html#negative-consequences",
-    "title": "Accepted: Complete glTF2 / VRM import and export pipeline in Godot Engine",
+    "objectID": "decisions/20240623-only-save-tools-in-our-cdn.html#the-infrequent-use-case",
+    "href": "decisions/20240623-only-save-tools-in-our-cdn.html#the-infrequent-use-case",
+    "title": "Proposal: Only Save Tools in Our CDN",
     "section": "",
-    "text": "Technical debt\n\n(this section can be repeated for each option, if more than one option is open for consideration"
+    "text": "In cases where a homeworld’s server is down or experiencing issues, users might not be able to access certain assets."
   },
   {
-    "objectID": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html#option-graveyard-usdz",
-    "href": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html#option-graveyard-usdz",
-    "title": "Accepted: Complete glTF2 / VRM import and export pipeline in Godot Engine",
+    "objectID": "decisions/20240623-only-save-tools-in-our-cdn.html#in-core-and-done-by-us",
+    "href": "decisions/20240623-only-save-tools-in-our-cdn.html#in-core-and-done-by-us",
+    "title": "Proposal: Only Save Tools in Our CDN",
     "section": "",
-    "text": "List the proposed options no longer open for consideration.\nList the reasons for the rejection: (the Bad traits)\n\nRequires GDNative\nComplicated"
+    "text": "The implementation of this proposal will be done by us, the V-Sekai development team. It aligns with our core principle of decentralization and user empowerment."
   },
   {
-    "objectID": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Accepted: Complete glTF2 / VRM import and export pipeline in Godot Engine",
+    "objectID": "decisions/20240623-only-save-tools-in-our-cdn.html#status",
+    "href": "decisions/20240623-only-save-tools-in-our-cdn.html#status",
+    "title": "Proposal: Only Save Tools in Our CDN",
     "section": "",
-    "text": "Possible to be gdscript"
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Accepted: Complete glTF2 / VRM import and export pipeline in Godot Engine",
+    "objectID": "decisions/20240623-only-save-tools-in-our-cdn.html#decision-makers",
+    "href": "decisions/20240623-only-save-tools-in-our-cdn.html#decision-makers",
+    "title": "Proposal: Only Save Tools in Our CDN",
     "section": "",
-    "text": "We need to provide trust for the toolchains."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html#references",
-    "href": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html#references",
-    "title": "Accepted: Complete glTF2 / VRM import and export pipeline in Godot Engine",
+    "objectID": "decisions/20240623-only-save-tools-in-our-cdn.html#tags",
+    "href": "decisions/20240623-only-save-tools-in-our-cdn.html#tags",
+    "title": "Proposal: Only Save Tools in Our CDN",
     "section": "",
-    "text": "Notary Trust"
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html#derivative-license",
-    "href": "decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html#derivative-license",
-    "title": "Accepted: Complete glTF2 / VRM import and export pipeline in Godot Engine",
+    "objectID": "decisions/20240623-only-save-tools-in-our-cdn.html#further-reading",
+    "href": "decisions/20240623-only-save-tools-in-our-cdn.html#further-reading",
+    "title": "Proposal: Only Save Tools in Our CDN",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis proposal was assisted by AI assistant Aria."
   },
   {
-    "objectID": "decisions/20231022-hover-to-ocean-game.html",
-    "href": "decisions/20231022-hover-to-ocean-game.html",
-    "title": "Proposed: Navigating New Horizons: A Proposal for Expanding Exploration in V-Sekai",
+    "objectID": "decisions/20230523-marketing-cycle.html",
+    "href": "decisions/20230523-marketing-cycle.html",
+    "title": "Draft: Improve V-Sekai marketing",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai, fire, cyberpunkmermaid\nTags: V-Sekai\n\n\n\n\nThe player starts with a hovercar and uses an upgrade to transform it into a hover submarine for ocean exploration. This involves navigating through surreal landscapes, encountering storms, avoiding volcanic eruptions, exploring coral reefs, and finally reaching a new island.\n\n\n\nThe main challenge lies in transitioning from land to underwater exploration while maintaining an engaging experience for the player. Creating diverse and interactive environments such as the cyber surrealist/impressionist voxel blocks landscape and the vibrant coral reef poses its own set of challenges.\n\n\n\nWe can use voxel-based rendering for creating the surreal landscapes and procedural generation for creating diverse marine life in the coral reef. For the transition from hovercar to hover submarine, we can design a special animation sequence that showcases the transformation.\n\n\n\nImplementing this would result in a unique and engaging gaming experience that combines elements of exploration, adventure, and survival. It would also showcase the capabilities of V-Sekai in creating diverse and immersive virtual worlds.\n\n\n\nThe complexity involved in implementing the proposed features would require significant resources and expertise. There’s also a risk that the final product may not meet the expectations due to technical limitations or unforeseen challenges.\n\n\n\nAn alternative approach could be to simplify the journey by limiting the number of environments or removing the transformation aspect. However, this would likely result in a less engaging experience for the player.\n\n\n\nYes, this proposal aligns with the core values of V-Sekai and can be implemented by our team with the right resources and planning.\n\n\n\n\nV-Sekai"
+    "text": "Status: draft \nDeciders: V-Sekai\nTags: V-Sekai, GPT-4\n\n\n\n\nV-Sekai is a virtual world platform that allows users to create, explore, and interact with others in various immersive environments.\nV-Sekai is facing a limitation in its marketing efforts. The challenge is to find a way to make marketing more manageable and effective for V-Sekai.\n\n\n\n\nStrategy\nPositioning\nMessaging\nExperimentation\n\nThe first three steps are initial preparations that create a strong foundation for marketing efforts. The fourth step, Experimentation, is a recurring process that helps us continuously improve our marketing strategies.\n\n\n\n\n\nDefine the overall marketing strategy by identifying target audiences, setting goals, and determining the best channels to reach potential customers.\n\n\n\nEstablish a unique selling proposition (USP) that sets the product or service apart from competitors. This will help potential customers understand why they should choose the offering over others in the market.\n\n\n\nDevelop clear and compelling messaging that communicates the USP and resonates with the target audience. This messaging should be consistent across all marketing channels.\n\n\n\nConduct regular experiments to test and refine marketing tactics. This can include A/B testing, trying new channels, or adjusting messaging. Analyze the results of these experiments and use the insights gained to improve future marketing efforts.\n\n\n\n\n\nImproved marketing effectiveness for V-Sekai\nBetter time management and prioritization of tasks\nIncreased revenue and business growth\n\n\n\n\n\nPotential initial time investment in setting up the marketing habit\nPossible resistance to change or adopting new habits\n\n\n\n\nDo nothing.\n\n\n\nNo, this marketing strategy is a comprehensive marketing approach that requires ongoing commitment and cannot be replaced by a simple script.\n\n\n\nYes, as the creators and maintainers of V-Sekai, we have the best understanding of our product and target audience. By taking charge of our marketing efforts, we can ensure that our messaging and strategies align with our goals and vision, ultimately leading to better results.\n\n\n\n\nV-Sekai\nMaterial from 2quiet2market"
   },
   {
-    "objectID": "decisions/20231022-hover-to-ocean-game.html#metadata",
-    "href": "decisions/20231022-hover-to-ocean-game.html#metadata",
-    "title": "Proposed: Navigating New Horizons: A Proposal for Expanding Exploration in V-Sekai",
+    "objectID": "decisions/20230523-marketing-cycle.html#metadata",
+    "href": "decisions/20230523-marketing-cycle.html#metadata",
+    "title": "Draft: Improve V-Sekai marketing",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai, fire, cyberpunkmermaid\nTags: V-Sekai"
+    "text": "Status: draft \nDeciders: V-Sekai\nTags: V-Sekai, GPT-4"
   },
   {
-    "objectID": "decisions/20231022-hover-to-ocean-game.html#the-backdrop",
-    "href": "decisions/20231022-hover-to-ocean-game.html#the-backdrop",
-    "title": "Proposed: Navigating New Horizons: A Proposal for Expanding Exploration in V-Sekai",
+    "objectID": "decisions/20230523-marketing-cycle.html#context-and-problem-statement",
+    "href": "decisions/20230523-marketing-cycle.html#context-and-problem-statement",
+    "title": "Draft: Improve V-Sekai marketing",
     "section": "",
-    "text": "The player starts with a hovercar and uses an upgrade to transform it into a hover submarine for ocean exploration. This involves navigating through surreal landscapes, encountering storms, avoiding volcanic eruptions, exploring coral reefs, and finally reaching a new island."
+    "text": "V-Sekai is a virtual world platform that allows users to create, explore, and interact with others in various immersive environments.\nV-Sekai is facing a limitation in its marketing efforts. The challenge is to find a way to make marketing more manageable and effective for V-Sekai."
   },
   {
-    "objectID": "decisions/20231022-hover-to-ocean-game.html#the-challenge",
-    "href": "decisions/20231022-hover-to-ocean-game.html#the-challenge",
-    "title": "Proposed: Navigating New Horizons: A Proposal for Expanding Exploration in V-Sekai",
+    "objectID": "decisions/20230523-marketing-cycle.html#proposed-solution",
+    "href": "decisions/20230523-marketing-cycle.html#proposed-solution",
+    "title": "Draft: Improve V-Sekai marketing",
     "section": "",
-    "text": "The main challenge lies in transitioning from land to underwater exploration while maintaining an engaging experience for the player. Creating diverse and interactive environments such as the cyber surrealist/impressionist voxel blocks landscape and the vibrant coral reef poses its own set of challenges."
+    "text": "Strategy\nPositioning\nMessaging\nExperimentation\n\nThe first three steps are initial preparations that create a strong foundation for marketing efforts. The fourth step, Experimentation, is a recurring process that helps us continuously improve our marketing strategies."
   },
   {
-    "objectID": "decisions/20231022-hover-to-ocean-game.html#the-strategy",
-    "href": "decisions/20231022-hover-to-ocean-game.html#the-strategy",
-    "title": "Proposed: Navigating New Horizons: A Proposal for Expanding Exploration in V-Sekai",
+    "objectID": "decisions/20230523-marketing-cycle.html#implementation",
+    "href": "decisions/20230523-marketing-cycle.html#implementation",
+    "title": "Draft: Improve V-Sekai marketing",
     "section": "",
-    "text": "We can use voxel-based rendering for creating the surreal landscapes and procedural generation for creating diverse marine life in the coral reef. For the transition from hovercar to hover submarine, we can design a special animation sequence that showcases the transformation."
+    "text": "Define the overall marketing strategy by identifying target audiences, setting goals, and determining the best channels to reach potential customers.\n\n\n\nEstablish a unique selling proposition (USP) that sets the product or service apart from competitors. This will help potential customers understand why they should choose the offering over others in the market.\n\n\n\nDevelop clear and compelling messaging that communicates the USP and resonates with the target audience. This messaging should be consistent across all marketing channels.\n\n\n\nConduct regular experiments to test and refine marketing tactics. This can include A/B testing, trying new channels, or adjusting messaging. Analyze the results of these experiments and use the insights gained to improve future marketing efforts."
   },
   {
-    "objectID": "decisions/20231022-hover-to-ocean-game.html#the-upside",
-    "href": "decisions/20231022-hover-to-ocean-game.html#the-upside",
-    "title": "Proposed: Navigating New Horizons: A Proposal for Expanding Exploration in V-Sekai",
+    "objectID": "decisions/20230523-marketing-cycle.html#positive-consequences",
+    "href": "decisions/20230523-marketing-cycle.html#positive-consequences",
+    "title": "Draft: Improve V-Sekai marketing",
     "section": "",
-    "text": "Implementing this would result in a unique and engaging gaming experience that combines elements of exploration, adventure, and survival. It would also showcase the capabilities of V-Sekai in creating diverse and immersive virtual worlds."
+    "text": "Improved marketing effectiveness for V-Sekai\nBetter time management and prioritization of tasks\nIncreased revenue and business growth"
   },
   {
-    "objectID": "decisions/20231022-hover-to-ocean-game.html#the-downside",
-    "href": "decisions/20231022-hover-to-ocean-game.html#the-downside",
-    "title": "Proposed: Navigating New Horizons: A Proposal for Expanding Exploration in V-Sekai",
+    "objectID": "decisions/20230523-marketing-cycle.html#negative-consequences",
+    "href": "decisions/20230523-marketing-cycle.html#negative-consequences",
+    "title": "Draft: Improve V-Sekai marketing",
     "section": "",
-    "text": "The complexity involved in implementing the proposed features would require significant resources and expertise. There’s also a risk that the final product may not meet the expectations due to technical limitations or unforeseen challenges."
+    "text": "Potential initial time investment in setting up the marketing habit\nPossible resistance to change or adopting new habits"
   },
   {
-    "objectID": "decisions/20231022-hover-to-ocean-game.html#the-road-not-taken",
-    "href": "decisions/20231022-hover-to-ocean-game.html#the-road-not-taken",
-    "title": "Proposed: Navigating New Horizons: A Proposal for Expanding Exploration in V-Sekai",
+    "objectID": "decisions/20230523-marketing-cycle.html#option-graveyard",
+    "href": "decisions/20230523-marketing-cycle.html#option-graveyard",
+    "title": "Draft: Improve V-Sekai marketing",
     "section": "",
-    "text": "An alternative approach could be to simplify the journey by limiting the number of environments or removing the transformation aspect. However, this would likely result in a less engaging experience for the player."
+    "text": "Do nothing."
   },
   {
-    "objectID": "decisions/20231022-hover-to-ocean-game.html#in-core-and-done-by-us",
-    "href": "decisions/20231022-hover-to-ocean-game.html#in-core-and-done-by-us",
-    "title": "Proposed: Navigating New Horizons: A Proposal for Expanding Exploration in V-Sekai",
+    "objectID": "decisions/20230523-marketing-cycle.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230523-marketing-cycle.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Draft: Improve V-Sekai marketing",
     "section": "",
-    "text": "Yes, this proposal aligns with the core values of V-Sekai and can be implemented by our team with the right resources and planning."
+    "text": "No, this marketing strategy is a comprehensive marketing approach that requires ongoing commitment and cannot be replaced by a simple script."
   },
   {
-    "objectID": "decisions/20231022-hover-to-ocean-game.html#further-reading",
-    "href": "decisions/20231022-hover-to-ocean-game.html#further-reading",
-    "title": "Proposed: Navigating New Horizons: A Proposal for Expanding Exploration in V-Sekai",
+    "objectID": "decisions/20230523-marketing-cycle.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230523-marketing-cycle.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Draft: Improve V-Sekai marketing",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Yes, as the creators and maintainers of V-Sekai, we have the best understanding of our product and target audience. By taking charge of our marketing efforts, we can ensure that our messaging and strategies align with our goals and vision, ultimately leading to better results."
   },
   {
-    "objectID": "decisions/20240623-do-cdn-for-launcher.html",
-    "href": "decisions/20240623-do-cdn-for-launcher.html",
-    "title": "Proposed: Use GitHub Actions and Digital Ocean Spaces for a V-Sekai Launcher",
+    "objectID": "decisions/20230523-marketing-cycle.html#references",
+    "href": "decisions/20230523-marketing-cycle.html#references",
+    "title": "Draft: Improve V-Sekai marketing",
     "section": "",
-    "text": "V-Sekai is an open-source project that brings social VR/VRSNS/metaverse components to the Godot Engine. The current setup for providing a launcher to players via itch.io is too complicated and needs simplification.\n\n\n\nWe need a more streamlined process to provide a launcher to players.\n\n\n\nLeverage GitHub Actions to build the launcher and then upload it to Digital Ocean Spaces using the casync protocol (with the Desync golang library). This approach will replace the current reliance on gocd.\n\n\n\n\nSimplified deployment process.\nReduced dependency on other developers.\nUtilization of familiar and widely-used technologies (GitHub Actions, Digital Ocean Spaces).\n\n\n\n\nThe potential downsides could include:\n\nLearning curve associated with new technologies for some team members.\nPotential costs associated with using Digital Ocean Spaces.\nPossible limitations or issues with the cassync protocol or the Desync golang library.\n\n\n\n\nAlternative solutions such as continuing with the itch.io setup or exploring other cloud storage services were considered. However, they were not chosen due to their complexity or potential cost implications.\n\n\n\nThis solution might not be optimal in scenarios where there are significant changes in the game’s codebase that would require substantial modifications to the GitHub Actions scripts.\n\n\n\nThis proposal is core to the V-Sekai project and will be implemented by the V-Sekai development team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project.\n\nAI assistant Aria assisted with this article."
+    "text": "V-Sekai\nMaterial from 2quiet2market"
   },
   {
-    "objectID": "decisions/20240623-do-cdn-for-launcher.html#context",
-    "href": "decisions/20240623-do-cdn-for-launcher.html#context",
-    "title": "Proposed: Use GitHub Actions and Digital Ocean Spaces for a V-Sekai Launcher",
+    "objectID": "decisions/20241014-xr-interface-for-rigging.html",
+    "href": "decisions/20241014-xr-interface-for-rigging.html",
+    "title": "Proposed: Editing Character Body Bone Constraints in Immersive Mode",
     "section": "",
-    "text": "V-Sekai is an open-source project that brings social VR/VRSNS/metaverse components to the Godot Engine. The current setup for providing a launcher to players via itch.io is too complicated and needs simplification."
+    "text": "V-Sekai is a social VR community.\n\n\n\nWe aim to develop a prototype interface for editing bone constraints such as position, rotation, twist rotation, and swing rotation on character body bones within an immersive environment.\nInteractivity makes a difference, similar to the feeling of presence and being fully engaged with the editor. This greater flow state occurs because you don’t have to switch contexts, allowing for continuous interaction and focus.\n\n\n\n\n\nThe proposed system will allow users to interact directly with avatar bone structures in a 3D space, manipulating constraints through intuitive gestures and tools. This approach aims to enhance user engagement and precision in modifying avatars.\n\n\n\n\nVisual Representation of Bones:\n\nEach bone will be represented by a dot that becomes visible and enlarges when the user’s hand or controller approaches it, facilitating easy selection.\n\nAvoiding Selection Mechanism:\n\nInstead of using a traditional selection mechanism, the system will employ proximity-based interaction. When a user’s hand or controller is near a bone, the relevant constraints automatically appear, allowing immediate manipulation without the need for explicit selection. This reduces complexity and enhances flow in the immersive environment.\n\nConstraint Manipulation Tools:\n\nA virtual tool palette will be available to the user, containing different constraint modifiers.\nUsers can grab these tools and attach them to bones to adjust constraints like positions and rotations.\n\nTool Switcher Interface:\n\nIn addition to the tool palette, a tool switcher mechanism will be implemented allowing users to quickly switch between tools without returning to the palette. This could be activated via a gesture or a button press, bringing up a radial or linear menu to select the desired tool.\n\nIntuitive Constraint Adjustment:\n\nFor position constraints, a 3D gizmo will appear, allowing users to manipulate the position directly within the VR space.\nFor rotational constraints, a 3D gizmo will appear, allowing users to manipulate the angle directly within the VR space.\nTwist constraints will be adjusted using a 2d disk arc interface where permissible rotation areas are defined by the user.\nSwing constraints can be adjusted using a spherical interface where permissible rotation areas are defined by the user.\nSwing constraints can be adjusted using a 2d orbit map interface where permissible rotation areas are defined by the user.\n\nFeedback and Precision:\n\nVisual and haptic feedback will be provided to ensure users are aware of the changes they are making.\nPrecision tools and snapping features will help in making exact adjustments.\n\nDeselection and Context Switching:\n\nMoving the controller away from the bones or performing a specific gesture will clear the current interaction, allowing for a smooth workflow without accidental adjustments.\n\n\n\n\n\n[User Interface Mock-up]\n+------------------------------------------------+\n|                                                |\n|  [Avatar]                                      |\n|    * (Head)                                    |\n|    * (Shoulder)                                |\n|    * (Elbow) &lt;-- [Interacting]                 |\n|    * (Wrist)                                   |\n|                                                |\n|  [Tool Palette]                                |\n|    - Grab Tool                                 |\n|    - Rotate Tool                               |\n|    - Swing Tool                                |\n|    - Twist Tool                                |\n|                                                |\n|  [Tool Switcher]                               |\n|    - Quick Switch Gesture                      |\n|    - Radial Menu for Tool Selection            |\n|                                                |\n+------------------------------------------------+\n\n\n\n\n\nEnhanced User Experience: Direct manipulation of bones and constraints in VR enhances the intuitiveness and enjoyment of avatar customization.\nIncreased Precision: Fine control over adjustments leads to more accurate and satisfying results.\nSeamless Workflow: Integration of tools and interactions within the VR environment reduces the cognitive load and context switching, fostering a more creative and productive user experience.\n\n\n\n\n\nComplexity in Implementation: Developing a fully interactive 3D UI with precise control mechanisms can be challenging and time-consuming.\nPerformance Concerns: High fidelity models and real-time updates in VR may lead to performance issues on lower-end systems.\nIn a shared space app on the Apple Vision Pro neither switching or tool palette will work.\nIn an immersive app on the Apple Vision Pro either switching or tool palette will work with hand tracking.\n\n\n\n\n\n2D GUI for Constraint Management: Using a traditional 2D interface for constraint management was considered but rejected due to the lack of immersion and intuitiveness in a VR context.\n\nThe implementation of scale for matching clothing to the character’s body, as well as the adjustment of constraint weight, will be addressed in future work.\n\n\n\nThis feature is core to the V-Sekai project’s mission of enhancing VR interaction and will be developed internally to maintain control over quality and integration.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\nFire\nNova\n\n\n\n\n\nV-Sekai, interactive presence, unfolding complexity, avatar dots, maximum precision, angle constraints, twist constraint, sphere visualization, constraint palette, tool shadow, localized selection, proprioceptive action, switcher interface, tool palette, deselection method, user flow\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nV-Sekai/lasso - GitHub for vr interaction.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240623-do-cdn-for-launcher.html#problem-statement",
-    "href": "decisions/20240623-do-cdn-for-launcher.html#problem-statement",
-    "title": "Proposed: Use GitHub Actions and Digital Ocean Spaces for a V-Sekai Launcher",
+    "objectID": "decisions/20241014-xr-interface-for-rigging.html#the-context",
+    "href": "decisions/20241014-xr-interface-for-rigging.html#the-context",
+    "title": "Proposed: Editing Character Body Bone Constraints in Immersive Mode",
     "section": "",
-    "text": "We need a more streamlined process to provide a launcher to players."
+    "text": "V-Sekai is a social VR community."
   },
   {
-    "objectID": "decisions/20240623-do-cdn-for-launcher.html#proposal",
-    "href": "decisions/20240623-do-cdn-for-launcher.html#proposal",
-    "title": "Proposed: Use GitHub Actions and Digital Ocean Spaces for a V-Sekai Launcher",
+    "objectID": "decisions/20241014-xr-interface-for-rigging.html#the-problem-statement",
+    "href": "decisions/20241014-xr-interface-for-rigging.html#the-problem-statement",
+    "title": "Proposed: Editing Character Body Bone Constraints in Immersive Mode",
     "section": "",
-    "text": "Leverage GitHub Actions to build the launcher and then upload it to Digital Ocean Spaces using the casync protocol (with the Desync golang library). This approach will replace the current reliance on gocd."
+    "text": "We aim to develop a prototype interface for editing bone constraints such as position, rotation, twist rotation, and swing rotation on character body bones within an immersive environment.\nInteractivity makes a difference, similar to the feeling of presence and being fully engaged with the editor. This greater flow state occurs because you don’t have to switch contexts, allowing for continuous interaction and focus."
   },
   {
-    "objectID": "decisions/20240623-do-cdn-for-launcher.html#benefits",
-    "href": "decisions/20240623-do-cdn-for-launcher.html#benefits",
-    "title": "Proposed: Use GitHub Actions and Digital Ocean Spaces for a V-Sekai Launcher",
+    "objectID": "decisions/20241014-xr-interface-for-rigging.html#proposal-description",
+    "href": "decisions/20241014-xr-interface-for-rigging.html#proposal-description",
+    "title": "Proposed: Editing Character Body Bone Constraints in Immersive Mode",
     "section": "",
-    "text": "Simplified deployment process.\nReduced dependency on other developers.\nUtilization of familiar and widely-used technologies (GitHub Actions, Digital Ocean Spaces)."
+    "text": "The proposed system will allow users to interact directly with avatar bone structures in a 3D space, manipulating constraints through intuitive gestures and tools. This approach aims to enhance user engagement and precision in modifying avatars.\n\n\n\n\nVisual Representation of Bones:\n\nEach bone will be represented by a dot that becomes visible and enlarges when the user’s hand or controller approaches it, facilitating easy selection.\n\nAvoiding Selection Mechanism:\n\nInstead of using a traditional selection mechanism, the system will employ proximity-based interaction. When a user’s hand or controller is near a bone, the relevant constraints automatically appear, allowing immediate manipulation without the need for explicit selection. This reduces complexity and enhances flow in the immersive environment.\n\nConstraint Manipulation Tools:\n\nA virtual tool palette will be available to the user, containing different constraint modifiers.\nUsers can grab these tools and attach them to bones to adjust constraints like positions and rotations.\n\nTool Switcher Interface:\n\nIn addition to the tool palette, a tool switcher mechanism will be implemented allowing users to quickly switch between tools without returning to the palette. This could be activated via a gesture or a button press, bringing up a radial or linear menu to select the desired tool.\n\nIntuitive Constraint Adjustment:\n\nFor position constraints, a 3D gizmo will appear, allowing users to manipulate the position directly within the VR space.\nFor rotational constraints, a 3D gizmo will appear, allowing users to manipulate the angle directly within the VR space.\nTwist constraints will be adjusted using a 2d disk arc interface where permissible rotation areas are defined by the user.\nSwing constraints can be adjusted using a spherical interface where permissible rotation areas are defined by the user.\nSwing constraints can be adjusted using a 2d orbit map interface where permissible rotation areas are defined by the user.\n\nFeedback and Precision:\n\nVisual and haptic feedback will be provided to ensure users are aware of the changes they are making.\nPrecision tools and snapping features will help in making exact adjustments.\n\nDeselection and Context Switching:\n\nMoving the controller away from the bones or performing a specific gesture will clear the current interaction, allowing for a smooth workflow without accidental adjustments.\n\n\n\n\n\n[User Interface Mock-up]\n+------------------------------------------------+\n|                                                |\n|  [Avatar]                                      |\n|    * (Head)                                    |\n|    * (Shoulder)                                |\n|    * (Elbow) &lt;-- [Interacting]                 |\n|    * (Wrist)                                   |\n|                                                |\n|  [Tool Palette]                                |\n|    - Grab Tool                                 |\n|    - Rotate Tool                               |\n|    - Swing Tool                                |\n|    - Twist Tool                                |\n|                                                |\n|  [Tool Switcher]                               |\n|    - Quick Switch Gesture                      |\n|    - Radial Menu for Tool Selection            |\n|                                                |\n+------------------------------------------------+"
   },
   {
-    "objectID": "decisions/20240623-do-cdn-for-launcher.html#downsides",
-    "href": "decisions/20240623-do-cdn-for-launcher.html#downsides",
-    "title": "Proposed: Use GitHub Actions and Digital Ocean Spaces for a V-Sekai Launcher",
+    "objectID": "decisions/20241014-xr-interface-for-rigging.html#benefits",
+    "href": "decisions/20241014-xr-interface-for-rigging.html#benefits",
+    "title": "Proposed: Editing Character Body Bone Constraints in Immersive Mode",
     "section": "",
-    "text": "The potential downsides could include:\n\nLearning curve associated with new technologies for some team members.\nPotential costs associated with using Digital Ocean Spaces.\nPossible limitations or issues with the cassync protocol or the Desync golang library."
+    "text": "Enhanced User Experience: Direct manipulation of bones and constraints in VR enhances the intuitiveness and enjoyment of avatar customization.\nIncreased Precision: Fine control over adjustments leads to more accurate and satisfying results.\nSeamless Workflow: Integration of tools and interactions within the VR environment reduces the cognitive load and context switching, fostering a more creative and productive user experience."
   },
   {
-    "objectID": "decisions/20240623-do-cdn-for-launcher.html#the-road-not-taken",
-    "href": "decisions/20240623-do-cdn-for-launcher.html#the-road-not-taken",
-    "title": "Proposed: Use GitHub Actions and Digital Ocean Spaces for a V-Sekai Launcher",
+    "objectID": "decisions/20241014-xr-interface-for-rigging.html#downsides",
+    "href": "decisions/20241014-xr-interface-for-rigging.html#downsides",
+    "title": "Proposed: Editing Character Body Bone Constraints in Immersive Mode",
     "section": "",
-    "text": "Alternative solutions such as continuing with the itch.io setup or exploring other cloud storage services were considered. However, they were not chosen due to their complexity or potential cost implications."
+    "text": "Complexity in Implementation: Developing a fully interactive 3D UI with precise control mechanisms can be challenging and time-consuming.\nPerformance Concerns: High fidelity models and real-time updates in VR may lead to performance issues on lower-end systems.\nIn a shared space app on the Apple Vision Pro neither switching or tool palette will work.\nIn an immersive app on the Apple Vision Pro either switching or tool palette will work with hand tracking."
   },
   {
-    "objectID": "decisions/20240623-do-cdn-for-launcher.html#the-infrequent-use-case",
-    "href": "decisions/20240623-do-cdn-for-launcher.html#the-infrequent-use-case",
-    "title": "Proposed: Use GitHub Actions and Digital Ocean Spaces for a V-Sekai Launcher",
+    "objectID": "decisions/20241014-xr-interface-for-rigging.html#the-road-not-taken",
+    "href": "decisions/20241014-xr-interface-for-rigging.html#the-road-not-taken",
+    "title": "Proposed: Editing Character Body Bone Constraints in Immersive Mode",
     "section": "",
-    "text": "This solution might not be optimal in scenarios where there are significant changes in the game’s codebase that would require substantial modifications to the GitHub Actions scripts."
+    "text": "2D GUI for Constraint Management: Using a traditional 2D interface for constraint management was considered but rejected due to the lack of immersion and intuitiveness in a VR context.\n\nThe implementation of scale for matching clothing to the character’s body, as well as the adjustment of constraint weight, will be addressed in future work."
   },
   {
-    "objectID": "decisions/20240623-do-cdn-for-launcher.html#in-core-and-done-by-us",
-    "href": "decisions/20240623-do-cdn-for-launcher.html#in-core-and-done-by-us",
-    "title": "Proposed: Use GitHub Actions and Digital Ocean Spaces for a V-Sekai Launcher",
+    "objectID": "decisions/20241014-xr-interface-for-rigging.html#in-core-and-done-by-us",
+    "href": "decisions/20241014-xr-interface-for-rigging.html#in-core-and-done-by-us",
+    "title": "Proposed: Editing Character Body Bone Constraints in Immersive Mode",
     "section": "",
-    "text": "This proposal is core to the V-Sekai project and will be implemented by the V-Sekai development team."
+    "text": "This feature is core to the V-Sekai project’s mission of enhancing VR interaction and will be developed internally to maintain control over quality and integration."
   },
   {
-    "objectID": "decisions/20240623-do-cdn-for-launcher.html#status",
-    "href": "decisions/20240623-do-cdn-for-launcher.html#status",
-    "title": "Proposed: Use GitHub Actions and Digital Ocean Spaces for a V-Sekai Launcher",
+    "objectID": "decisions/20241014-xr-interface-for-rigging.html#status",
+    "href": "decisions/20241014-xr-interface-for-rigging.html#status",
+    "title": "Proposed: Editing Character Body Bone Constraints in Immersive Mode",
     "section": "",
     "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20240623-do-cdn-for-launcher.html#decision-makers",
-    "href": "decisions/20240623-do-cdn-for-launcher.html#decision-makers",
-    "title": "Proposed: Use GitHub Actions and Digital Ocean Spaces for a V-Sekai Launcher",
+    "objectID": "decisions/20241014-xr-interface-for-rigging.html#decision-makers",
+    "href": "decisions/20241014-xr-interface-for-rigging.html#decision-makers",
+    "title": "Proposed: Editing Character Body Bone Constraints in Immersive Mode",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "V-Sekai development team\nFire\nNova"
   },
   {
-    "objectID": "decisions/20240623-do-cdn-for-launcher.html#tags",
-    "href": "decisions/20240623-do-cdn-for-launcher.html#tags",
-    "title": "Proposed: Use GitHub Actions and Digital Ocean Spaces for a V-Sekai Launcher",
+    "objectID": "decisions/20241014-xr-interface-for-rigging.html#tags",
+    "href": "decisions/20241014-xr-interface-for-rigging.html#tags",
+    "title": "Proposed: Editing Character Body Bone Constraints in Immersive Mode",
     "section": "",
-    "text": "V-Sekai"
+    "text": "V-Sekai, interactive presence, unfolding complexity, avatar dots, maximum precision, angle constraints, twist constraint, sphere visualization, constraint palette, tool shadow, localized selection, proprioceptive action, switcher interface, tool palette, deselection method, user flow"
   },
   {
-    "objectID": "decisions/20240623-do-cdn-for-launcher.html#further-reading",
-    "href": "decisions/20240623-do-cdn-for-launcher.html#further-reading",
-    "title": "Proposed: Use GitHub Actions and Digital Ocean Spaces for a V-Sekai Launcher",
+    "objectID": "decisions/20241014-xr-interface-for-rigging.html#further-reading",
+    "href": "decisions/20241014-xr-interface-for-rigging.html#further-reading",
+    "title": "Proposed: Editing Character Body Bone Constraints in Immersive Mode",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project.\n\nAI assistant Aria assisted with this article."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nV-Sekai/lasso - GitHub for vr interaction.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20211104-research-mesh-tooling-with-nglod.html",
-    "href": "decisions/20211104-research-mesh-tooling-with-nglod.html",
-    "title": "Draft: Research mesh tooling with nglod",
+    "objectID": "decisions/20210811-neural-blend-shape-rigging.html",
+    "href": "decisions/20210811-neural-blend-shape-rigging.html",
+    "title": "Proposed: Neural Blend Shape Rigging",
     "section": "",
-    "text": "Status: draft \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nNeed geometric tools for many things in the V-Sekai.\n\n\n\nUse nglod for some of the 3d geometric tools.\n\n\n\n\ngit clone https://github.com/nv-tlabs/nglod.git\nInstall https://github.com/conda-forge/miniforge#mambaforge\nconda create --name nglod python=3.9\nconda activate nglod\nconda install pytorch torchvision torchaudio cudatoolkit=11.3 -c pytorch\npip install -r ./infra/requirements.txt\n\npython app/main.py --net OctreeSDF --num-lods 5 --dataset-path data/armadillo.obj --epoch 250 --exp-name armadillo\n\n\n\n\nMaybe possible to encode as onnx\nMaybe usable cpu only.\n\n\n\n\n\nMight require the GPU.\nInferencing may be difficult at interactive rates.\n\n\n\n\n\nOption: \nRejection Reason: \n\n\n\n\nCUDA, PyTorch and c++ are significant works.\n\n\n\nI have an approach!\n\n\n\n\nhttps://kaolin.readthedocs.io/en/latest/notes/installation.html\nhttps://www.alecjacobson.com/weblog/?tag=qslim\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Proposed: Neural Blend Shape Rigging\n\nContext and Problem Statement\nRigging characters takes too much effort and skill.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nUse Neural Blend Shapes to rig a base mesh.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n\nRequirements\n\nt-pose base mesh\nSimilar to the smpl_std.\n\n\n\nGet neural Blend shapes\nClone neural blend shapes\ngit clone https://github.com/PeizhuoLi/neural-blend-shapes.git\n\n\nBlender\n\nOpen your base mesh\nOpen the smpl_std.obj into the Blender mesh\nEnable the mesh align Blender addon\nSelect the rest of the meshes and then the smpl_std mesh\nAlign base_mesh.obj to the base mesh and then translate it so it stands on the floor \n\n\n\nNeural Blend Shapes\nwget https://github.com/conda-forge/miniforge/releases/latest/download/Mambaforge-pypy3-Linux-x86_64.sh\nsh Mambaforge-pypy3-Linux-x86_64.sh\nmamba create --name neural python=3.7\nmamba activate neural\nmamba install tensorboard tqdm PyTorch torchvision torchaudio -c PyTorch -y\npython demo.py --pose_file=./eval_constant/sequences/house-dance.npy --obj_path=./eval_constant/meshes/ALPAPAAM.obj --normalize=1 --animated_bvh=1 --obj_output=0\nsudo flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo\nsudo flatpak install org.blender.Blender\ncd blender_scripts\nflatpak run org.blender.Blender -b -P `pwd`/nbs_fbx_output.py -- --input `pwd`/../demo --output `pwd`/../demo/output.fbx\n\n\nUse voxel diffuse skinning\n\nThe skeleton model above weighted the eye area. This is not good.\nUse https://www.blendermarket.com/products/voxel-heat-diffuse-skinning\nTake skeleton from output.fbx and reweight it onto the original mesh set\n\n\n\nVRM\n\n\n\nimage\n\n\n\nSet bone mappings\nIn the scripting set first person json to use bone “22” for the head\nTODO Move the skeleton so it stands on the floor\n\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot workaround-able.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo finger support yet.\n\n\nIs there a reason why this should be core and done by us?\nMixamo is a black box and V-Sekai would be more robust to have an alternative.\n\n\nReferences\n\nhttps://github.com/PeizhuoLi/neural-blend-shapes\nSkeleton https://github.com/Xananax/ALPAPATAM\nMannequin https://github.com/V-Sekai/blue-tin-fox-models/actions\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20211104-research-mesh-tooling-with-nglod.html#context-and-problem-statement",
-    "href": "decisions/20211104-research-mesh-tooling-with-nglod.html#context-and-problem-statement",
-    "title": "Draft: Research mesh tooling with nglod",
+    "objectID": "decisions/20210811-minecraft-voxel.html",
+    "href": "decisions/20210811-minecraft-voxel.html",
+    "title": "Proposed: Import Minecraft worlds to Godot Engine",
     "section": "",
-    "text": "Need geometric tools for many things in the V-Sekai."
+    "text": "Proposed: Import Minecraft worlds to Godot Engine\n\nContext and Problem Statement\nWe want more content in Godot Engine.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nWe want to import Minecraft worlds as .Vox and as standard gltf.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nSave the minecraft world.\nUse amulet_map_editor.\n\ngit clone https://github.com/Amulet-Team/Amulet-Map-Editor.git\ncd Amulet-Map-Editor\npython3 -m pip install amulet-map-editor\npython3 -m amulet_map_editor\nUse wxpython 4.x\nexport world to .schematic\nuse FileToVox\nUse fire’s vox module for godot 4.x\n\nUse Schematic and Mineways and export to .obj.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot a small number of lines.\n\n\nPositive Consequences\nMore content!\n\n\nNegative Consequences\nWorkflow changes.\n\n\nIs there a reason why this should be core and done by us?\nCan remix work by Zylann and others.\n\n\nReferences\n nova_world.zip\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject nova_world.zip to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20211104-research-mesh-tooling-with-nglod.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20211104-research-mesh-tooling-with-nglod.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Draft: Research mesh tooling with nglod",
+    "objectID": "decisions/20230505-v-sekai-ai-completion.html",
+    "href": "decisions/20230505-v-sekai-ai-completion.html",
+    "title": "Superseded: Solve V-Sekai limitations using ChatGPT-4 AI completion.",
     "section": "",
-    "text": "Use nglod for some of the 3d geometric tools."
+    "text": "Status: superseded by 20230522-proposal-template.md \nDeciders: V-Sekai,fire,\nTags: V-Sekai,ChatGPT-4,AI_assistance,problem solving,proposal generation,Visual Studio Code addon,\n\n\n\n\nWe sometimes need help finding solutions to our issues. ChatGPT-4 artificial intelligence completion can help us solve the entire problem when we only have the start of the solution.\n\n\n\nHow can we leverage ChatGPT-4 AI completion to assist in solving problems and completing proposals for V-Sekai?\n\n\n\nUse ChatGPT-4 AI completion with the Visual Studio Code “Genie” addon to fill in as many sections as possible in a given proposal template, helping to generate complete and well-rounded solutions.\n\n\n\n\nEnsure access to the chatgpt4 API access. There is a waiting list.\nCopy the proposal template.\nFill in as many sections as possible in the proposal template.\nUse the Visual Studio Code “Genie” addon with ChatGPT-4 AI completion to complete the remaining sections of the proposal.\nReview and refine the completed proposal.\nReview with copy editing software if accessible.\nRecord the decisions on GitHub at https://github.com/V-Sekai/manuals.\n\nExample of using ChatGPT-4 AI completion with the proposal template.\n# Issue: Feature implementation proposal\n\n## Propose a possible solution to solve a V-Sekai limitation. If this doesn't look right, choose a different type.\n\n## Metadata\n\n- Status: proposed &lt;!-- draft | proposed | rejected | accepted | deprecated | superseded by --&gt;\n- Deciders: V-Sekai\n- Tags: V-Sekai, GPT-4\n\n## Context and Problem Statement\n\n## Proposed Solution\n\n## Implementation\n\n## Positive Consequences\n\n## Negative Consequences\n\n## Option graveyard\n\n## If this enhancement will be used infrequently, can it be worked around with a few lines of script?\n\n## Is there a reason why this should be core and done by us?\n\n## References\n\n- [V-Sekai](https://v-sekai.org/)\n\n\n\n\nImproved problem-solving capabilities.\nMore complete and well-rounded proposals.\nFaster generation of solutions.\n\n\n\n\n\nPotential reliance on AI-generated content, which may only sometimes be accurate or suitable.\nAdditional time spent reviewing and refining AI-generated content.\n\n\n\n\nUse only human assistance.\n\n\n\nNo, this enhancement requires integrating ChatGPT-4 AI completion into the development workflow and cannot be achieved with a simple script.\n\n\n\nYes, leveraging AI-generated content can help improve the efficiency and effectiveness of our problem-solving process, leading to better solutions and faster development.\n\n\n\n\nV-Sekai\nGenie addon for Visual Studio Code"
   },
   {
-    "objectID": "decisions/20211104-research-mesh-tooling-with-nglod.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20211104-research-mesh-tooling-with-nglod.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Draft: Research mesh tooling with nglod",
+    "objectID": "decisions/20230505-v-sekai-ai-completion.html#metadata",
+    "href": "decisions/20230505-v-sekai-ai-completion.html#metadata",
+    "title": "Superseded: Solve V-Sekai limitations using ChatGPT-4 AI completion.",
     "section": "",
-    "text": "git clone https://github.com/nv-tlabs/nglod.git\nInstall https://github.com/conda-forge/miniforge#mambaforge\nconda create --name nglod python=3.9\nconda activate nglod\nconda install pytorch torchvision torchaudio cudatoolkit=11.3 -c pytorch\npip install -r ./infra/requirements.txt\n\npython app/main.py --net OctreeSDF --num-lods 5 --dataset-path data/armadillo.obj --epoch 250 --exp-name armadillo"
+    "text": "Status: superseded by 20230522-proposal-template.md \nDeciders: V-Sekai,fire,\nTags: V-Sekai,ChatGPT-4,AI_assistance,problem solving,proposal generation,Visual Studio Code addon,"
   },
   {
-    "objectID": "decisions/20211104-research-mesh-tooling-with-nglod.html#positive-consequences",
-    "href": "decisions/20211104-research-mesh-tooling-with-nglod.html#positive-consequences",
-    "title": "Draft: Research mesh tooling with nglod",
+    "objectID": "decisions/20230505-v-sekai-ai-completion.html#context-and-problem-statement",
+    "href": "decisions/20230505-v-sekai-ai-completion.html#context-and-problem-statement",
+    "title": "Superseded: Solve V-Sekai limitations using ChatGPT-4 AI completion.",
     "section": "",
-    "text": "Maybe possible to encode as onnx\nMaybe usable cpu only."
+    "text": "We sometimes need help finding solutions to our issues. ChatGPT-4 artificial intelligence completion can help us solve the entire problem when we only have the start of the solution."
   },
   {
-    "objectID": "decisions/20211104-research-mesh-tooling-with-nglod.html#negative-consequences",
-    "href": "decisions/20211104-research-mesh-tooling-with-nglod.html#negative-consequences",
-    "title": "Draft: Research mesh tooling with nglod",
+    "objectID": "decisions/20230505-v-sekai-ai-completion.html#describe-the-problem-or-limitation-you-have-in-your-project-e.g.-in-free-form-using-two-to-three-sentences.-consider-articulating-the-case-in-the-form-of-a-question.",
+    "href": "decisions/20230505-v-sekai-ai-completion.html#describe-the-problem-or-limitation-you-have-in-your-project-e.g.-in-free-form-using-two-to-three-sentences.-consider-articulating-the-case-in-the-form-of-a-question.",
+    "title": "Superseded: Solve V-Sekai limitations using ChatGPT-4 AI completion.",
     "section": "",
-    "text": "Might require the GPU.\nInferencing may be difficult at interactive rates."
+    "text": "How can we leverage ChatGPT-4 AI completion to assist in solving problems and completing proposals for V-Sekai?"
   },
   {
-    "objectID": "decisions/20211104-research-mesh-tooling-with-nglod.html#option-graveyard",
-    "href": "decisions/20211104-research-mesh-tooling-with-nglod.html#option-graveyard",
-    "title": "Draft: Research mesh tooling with nglod",
+    "objectID": "decisions/20230505-v-sekai-ai-completion.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20230505-v-sekai-ai-completion.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Superseded: Solve V-Sekai limitations using ChatGPT-4 AI completion.",
     "section": "",
-    "text": "Option: \nRejection Reason:"
+    "text": "Use ChatGPT-4 AI completion with the Visual Studio Code “Genie” addon to fill in as many sections as possible in a given proposal template, helping to generate complete and well-rounded solutions."
   },
   {
-    "objectID": "decisions/20211104-research-mesh-tooling-with-nglod.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20211104-research-mesh-tooling-with-nglod.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Draft: Research mesh tooling with nglod",
+    "objectID": "decisions/20230505-v-sekai-ai-completion.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20230505-v-sekai-ai-completion.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Superseded: Solve V-Sekai limitations using ChatGPT-4 AI completion.",
     "section": "",
-    "text": "CUDA, PyTorch and c++ are significant works."
+    "text": "Ensure access to the chatgpt4 API access. There is a waiting list.\nCopy the proposal template.\nFill in as many sections as possible in the proposal template.\nUse the Visual Studio Code “Genie” addon with ChatGPT-4 AI completion to complete the remaining sections of the proposal.\nReview and refine the completed proposal.\nReview with copy editing software if accessible.\nRecord the decisions on GitHub at https://github.com/V-Sekai/manuals.\n\nExample of using ChatGPT-4 AI completion with the proposal template.\n# Issue: Feature implementation proposal\n\n## Propose a possible solution to solve a V-Sekai limitation. If this doesn't look right, choose a different type.\n\n## Metadata\n\n- Status: proposed &lt;!-- draft | proposed | rejected | accepted | deprecated | superseded by --&gt;\n- Deciders: V-Sekai\n- Tags: V-Sekai, GPT-4\n\n## Context and Problem Statement\n\n## Proposed Solution\n\n## Implementation\n\n## Positive Consequences\n\n## Negative Consequences\n\n## Option graveyard\n\n## If this enhancement will be used infrequently, can it be worked around with a few lines of script?\n\n## Is there a reason why this should be core and done by us?\n\n## References\n\n- [V-Sekai](https://v-sekai.org/)"
   },
   {
-    "objectID": "decisions/20211104-research-mesh-tooling-with-nglod.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20211104-research-mesh-tooling-with-nglod.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Draft: Research mesh tooling with nglod",
+    "objectID": "decisions/20230505-v-sekai-ai-completion.html#positive-consequences",
+    "href": "decisions/20230505-v-sekai-ai-completion.html#positive-consequences",
+    "title": "Superseded: Solve V-Sekai limitations using ChatGPT-4 AI completion.",
     "section": "",
-    "text": "I have an approach!"
+    "text": "Improved problem-solving capabilities.\nMore complete and well-rounded proposals.\nFaster generation of solutions."
   },
   {
-    "objectID": "decisions/20211104-research-mesh-tooling-with-nglod.html#references",
-    "href": "decisions/20211104-research-mesh-tooling-with-nglod.html#references",
-    "title": "Draft: Research mesh tooling with nglod",
+    "objectID": "decisions/20230505-v-sekai-ai-completion.html#negative-consequences",
+    "href": "decisions/20230505-v-sekai-ai-completion.html#negative-consequences",
+    "title": "Superseded: Solve V-Sekai limitations using ChatGPT-4 AI completion.",
     "section": "",
-    "text": "https://kaolin.readthedocs.io/en/latest/notes/installation.html\nhttps://www.alecjacobson.com/weblog/?tag=qslim"
+    "text": "Potential reliance on AI-generated content, which may only sometimes be accurate or suitable.\nAdditional time spent reviewing and refining AI-generated content."
   },
   {
-    "objectID": "decisions/20211104-research-mesh-tooling-with-nglod.html#derivative-license",
-    "href": "decisions/20211104-research-mesh-tooling-with-nglod.html#derivative-license",
-    "title": "Draft: Research mesh tooling with nglod",
+    "objectID": "decisions/20230505-v-sekai-ai-completion.html#option-graveyard",
+    "href": "decisions/20230505-v-sekai-ai-completion.html#option-graveyard",
+    "title": "Superseded: Solve V-Sekai limitations using ChatGPT-4 AI completion.",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Use only human assistance."
   },
   {
-    "objectID": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html",
-    "href": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html",
-    "title": "Proposal: Sustainable Version Management for Godot Engine in V-Sekai",
+    "objectID": "decisions/20230505-v-sekai-ai-completion.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230505-v-sekai-ai-completion.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Superseded: Solve V-Sekai limitations using ChatGPT-4 AI completion.",
     "section": "",
-    "text": "The continuous growth of upstream versions in the Godot Engine presents a challenge for the V-Sekai project. With finite resources and brainpower, keeping up with this “infinite” growth and its associated delays becomes increasingly difficult.\n\n\n\nHow can we manage the version growth of the Godot Engine more sustainably, focusing our limited resources on what matters most for our project?\n\n\n\nWe propose a sustainable approach to handle the version growth of the Godot Engine:\n\nDesigning for Finite Funds: Instead of investing heavily in trying to keep up with every new version, focus on key updates that significantly impact or improve our project.\nDesigning for Finite Performance: Prioritize optimization and performance over trying to incorporate every new feature from the latest versions.\nDesigning for Finite Data: Be selective about the data we choose to update with each new version, focusing on what’s most relevant to our project.\nDesign for Finite Brainpower: Invest in knowledge sharing and training to ensure our team can effectively work with the chosen versions of Godot Engine.\n\n\n\n\nThis approach will allow us to manage version growth more sustainably. It will also help us avoid unnecessary delays caused by trying to keep up with every new version.\n\n\n\nWe may miss out on some features or improvements introduced in the versions we choose not to adopt. However, by focusing on significant updates, we aim to mitigate this risk.\n\n\n\nContinuing to try and keep up with every new version of the Godot Engine, despite our limited resources.\n\n\n\nWhile our focus is on managing the version growth of the Godot Engine sustainably, there may be infrequent cases where we need to adopt a new version immediately. This could occur if a new version introduces a critical security patch or a feature that significantly benefits our project. In such cases, we will prioritize updating to the new version, even if it requires additional resources.\n\n\n\nThis proposal involves changes to our core version management practices and will be implemented by our development team.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai Development Team\n\n\n\n\n\nVersion Management\nGodot Engine\nSustainability\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - The GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nCoding for a Finite World - A blog post discussing the need for sustainable coding practices in a finite world.\n\nThis proposal was assisted by AI assistant, Aria."
+    "text": "No, this enhancement requires integrating ChatGPT-4 AI completion into the development workflow and cannot be achieved with a simple script."
   },
   {
-    "objectID": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#the-context",
-    "href": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#the-context",
-    "title": "Proposal: Sustainable Version Management for Godot Engine in V-Sekai",
+    "objectID": "decisions/20230505-v-sekai-ai-completion.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230505-v-sekai-ai-completion.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Superseded: Solve V-Sekai limitations using ChatGPT-4 AI completion.",
     "section": "",
-    "text": "The continuous growth of upstream versions in the Godot Engine presents a challenge for the V-Sekai project. With finite resources and brainpower, keeping up with this “infinite” growth and its associated delays becomes increasingly difficult."
+    "text": "Yes, leveraging AI-generated content can help improve the efficiency and effectiveness of our problem-solving process, leading to better solutions and faster development."
   },
   {
-    "objectID": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#the-problem-statement",
-    "href": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#the-problem-statement",
-    "title": "Proposal: Sustainable Version Management for Godot Engine in V-Sekai",
+    "objectID": "decisions/20230505-v-sekai-ai-completion.html#references",
+    "href": "decisions/20230505-v-sekai-ai-completion.html#references",
+    "title": "Superseded: Solve V-Sekai limitations using ChatGPT-4 AI completion.",
     "section": "",
-    "text": "How can we manage the version growth of the Godot Engine more sustainably, focusing our limited resources on what matters most for our project?"
+    "text": "V-Sekai\nGenie addon for Visual Studio Code"
   },
   {
-    "objectID": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposal: Sustainable Version Management for Godot Engine in V-Sekai",
+    "objectID": "decisions/20240218-vrm-acronym-correction.html",
+    "href": "decisions/20240218-vrm-acronym-correction.html",
+    "title": "Accepted: VRM Acronym Correction",
     "section": "",
-    "text": "We propose a sustainable approach to handle the version growth of the Godot Engine:\n\nDesigning for Finite Funds: Instead of investing heavily in trying to keep up with every new version, focus on key updates that significantly impact or improve our project.\nDesigning for Finite Performance: Prioritize optimization and performance over trying to incorporate every new feature from the latest versions.\nDesigning for Finite Data: Be selective about the data we choose to update with each new version, focusing on what’s most relevant to our project.\nDesign for Finite Brainpower: Invest in knowledge sharing and training to ensure our team can effectively work with the chosen versions of Godot Engine."
+    "text": "It has come to our attention that the term VRM has been incorrectly defined in earlier communications. We would like to clarify that VRM does not stand for “VRoid Model”, “Virtual Reality Model”, or any other previous interpretations provided.\n\n\n\nNot applicable as this involves correcting documentation and communication.\n\n\n\n\nEnsures everyone has a correct understanding of VRM.\nMaintains consistency in project materials.\n\n\n\n\n\nPossible brief confusion during the transition phase.\n\n\n\n\nChoosing not to publicly campaign about this error since it’s manageable through targeted updates.\n\n\n\nMinor impact on casual users who may overlook the correction.\n\n\n\nThe correction is directly handled by our team with ongoing oversight.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team and community stakeholders.\n\n\n\n\n\nV-Sekai, Avatar Customization, AI, Facial Expressions\n\n\n\n\n\nV-Sekai · GitHub - Official source for V-Sekai dev community.\nV-Sekai/v-sekai-game - Repository for V-Sekai project on social VR in Godot Engine.\n3D humanoid avatar file format for VR\n\nAria assisted with this content."
   },
   {
-    "objectID": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#the-benefits",
-    "href": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#the-benefits",
-    "title": "Proposal: Sustainable Version Management for Godot Engine in V-Sekai",
+    "objectID": "decisions/20240218-vrm-acronym-correction.html#overview",
+    "href": "decisions/20240218-vrm-acronym-correction.html#overview",
+    "title": "Accepted: VRM Acronym Correction",
     "section": "",
-    "text": "This approach will allow us to manage version growth more sustainably. It will also help us avoid unnecessary delays caused by trying to keep up with every new version."
+    "text": "It has come to our attention that the term VRM has been incorrectly defined in earlier communications. We would like to clarify that VRM does not stand for “VRoid Model”, “Virtual Reality Model”, or any other previous interpretations provided."
   },
   {
-    "objectID": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#the-downsides",
-    "href": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#the-downsides",
-    "title": "Proposal: Sustainable Version Management for Godot Engine in V-Sekai",
+    "objectID": "decisions/20240218-vrm-acronym-correction.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240218-vrm-acronym-correction.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Accepted: VRM Acronym Correction",
     "section": "",
-    "text": "We may miss out on some features or improvements introduced in the versions we choose not to adopt. However, by focusing on significant updates, we aim to mitigate this risk."
+    "text": "Not applicable as this involves correcting documentation and communication."
   },
   {
-    "objectID": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#the-road-not-taken",
-    "href": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#the-road-not-taken",
-    "title": "Proposal: Sustainable Version Management for Godot Engine in V-Sekai",
+    "objectID": "decisions/20240218-vrm-acronym-correction.html#the-benefits",
+    "href": "decisions/20240218-vrm-acronym-correction.html#the-benefits",
+    "title": "Accepted: VRM Acronym Correction",
     "section": "",
-    "text": "Continuing to try and keep up with every new version of the Godot Engine, despite our limited resources."
+    "text": "Ensures everyone has a correct understanding of VRM.\nMaintains consistency in project materials."
   },
   {
-    "objectID": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#the-infrequent-use-case",
-    "href": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#the-infrequent-use-case",
-    "title": "Proposal: Sustainable Version Management for Godot Engine in V-Sekai",
+    "objectID": "decisions/20240218-vrm-acronym-correction.html#the-downsides",
+    "href": "decisions/20240218-vrm-acronym-correction.html#the-downsides",
+    "title": "Accepted: VRM Acronym Correction",
     "section": "",
-    "text": "While our focus is on managing the version growth of the Godot Engine sustainably, there may be infrequent cases where we need to adopt a new version immediately. This could occur if a new version introduces a critical security patch or a feature that significantly benefits our project. In such cases, we will prioritize updating to the new version, even if it requires additional resources."
+    "text": "Possible brief confusion during the transition phase."
   },
   {
-    "objectID": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#in-core-and-done-by-us",
-    "href": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#in-core-and-done-by-us",
-    "title": "Proposal: Sustainable Version Management for Godot Engine in V-Sekai",
+    "objectID": "decisions/20240218-vrm-acronym-correction.html#the-road-not-taken",
+    "href": "decisions/20240218-vrm-acronym-correction.html#the-road-not-taken",
+    "title": "Accepted: VRM Acronym Correction",
     "section": "",
-    "text": "This proposal involves changes to our core version management practices and will be implemented by our development team."
+    "text": "Choosing not to publicly campaign about this error since it’s manageable through targeted updates."
   },
   {
-    "objectID": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#status",
-    "href": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#status",
-    "title": "Proposal: Sustainable Version Management for Godot Engine in V-Sekai",
+    "objectID": "decisions/20240218-vrm-acronym-correction.html#the-infrequent-use-case",
+    "href": "decisions/20240218-vrm-acronym-correction.html#the-infrequent-use-case",
+    "title": "Accepted: VRM Acronym Correction",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "Minor impact on casual users who may overlook the correction."
   },
   {
-    "objectID": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#decision-makers",
-    "href": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#decision-makers",
-    "title": "Proposal: Sustainable Version Management for Godot Engine in V-Sekai",
+    "objectID": "decisions/20240218-vrm-acronym-correction.html#in-core-and-done-by-us",
+    "href": "decisions/20240218-vrm-acronym-correction.html#in-core-and-done-by-us",
+    "title": "Accepted: VRM Acronym Correction",
     "section": "",
-    "text": "V-Sekai Development Team"
+    "text": "The correction is directly handled by our team with ongoing oversight."
   },
   {
-    "objectID": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#tags",
-    "href": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#tags",
-    "title": "Proposal: Sustainable Version Management for Godot Engine in V-Sekai",
+    "objectID": "decisions/20240218-vrm-acronym-correction.html#status",
+    "href": "decisions/20240218-vrm-acronym-correction.html#status",
+    "title": "Accepted: VRM Acronym Correction",
     "section": "",
-    "text": "Version Management\nGodot Engine\nSustainability"
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#further-reading",
-    "href": "decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html#further-reading",
-    "title": "Proposal: Sustainable Version Management for Godot Engine in V-Sekai",
+    "objectID": "decisions/20240218-vrm-acronym-correction.html#decision-makers",
+    "href": "decisions/20240218-vrm-acronym-correction.html#decision-makers",
+    "title": "Accepted: VRM Acronym Correction",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - The GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nCoding for a Finite World - A blog post discussing the need for sustainable coding practices in a finite world.\n\nThis proposal was assisted by AI assistant, Aria."
+    "text": "V-Sekai development team and community stakeholders."
   },
   {
-    "objectID": "decisions/20220317-baserow.io-truenas.html",
-    "href": "decisions/20220317-baserow.io-truenas.html",
-    "title": "Draft: To provide an asset library prototype use baserow",
+    "objectID": "decisions/20240218-vrm-acronym-correction.html#tags",
+    "href": "decisions/20240218-vrm-acronym-correction.html#tags",
+    "title": "Accepted: VRM Acronym Correction",
     "section": "",
-    "text": "Draft: To provide an asset library prototype use baserow\n\nDescribe the status of the issue.\ndraft\n\n\nList the deciders of the issue.\nV-Sekai,fire,\n\n\nDescribe the tags of the issue.\nV-Sekai,\n\n\nContext and Problem Statement\nWant to prototype a game asset library system.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nNeed a sandbox to prototype asset library.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\n\ninstall truenas on two redundant data drives and on a os drive\ninstall baserow.io as a docker compose\nadd vrm three.js viewer to baserow for .gltf and .vrm\n\n\n\nPositive Consequences\nAble to lean prototype asset libraries.\n\n\nNegative Consequences\nNo response\n\n\nOption graveyard\nNo response\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot a few lines of script.\n\n\nIs there a reason why this should be core and done by us?\nWanted to lean prototype.\n\n\nReferences\n\nV-Sekai\n\n\n\nLicense of the contribution\nCopyright (c) 2022 V-Sekai contributors. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "V-Sekai, Avatar Customization, AI, Facial Expressions"
   },
   {
-    "objectID": "decisions/20240615-what-is-mesh-transformers.html",
-    "href": "decisions/20240615-what-is-mesh-transformers.html",
-    "title": "Proposed: Explain the concept of Mesh Transformers",
+    "objectID": "decisions/20240218-vrm-acronym-correction.html#further-reading",
+    "href": "decisions/20240218-vrm-acronym-correction.html#further-reading",
+    "title": "Accepted: VRM Acronym Correction",
     "section": "",
-    "text": "Many of my friends are not tech-savvy.\n\n\n\nHow can we explain the concept of Mesh Transformers to a student?\n\n\n\nMesh Transformers can be understood as two parts - a construction worker (auto encoder) and an architect (transformer).\nThe construction worker learns how to construct and build a building, while the architect learns about all the items needed for a building and then instructs the construction worker on what to do.\nThe goal is to allow users to generate a 3D model on the fly using a prompt, instead of searching through numerous 3D libraries and forums. They can simply write what they want and within a few seconds get exactly what they want without settling on a 3D model that they kind of want.\n\n\n\nThis approach simplifies the process of creating 3D models, making it accessible even to those with little to no technical knowledge. It also saves time by eliminating the need to search through various resources.\n\n\n\nThere might be a learning curve involved in understanding how to use prompts effectively. Also, the quality of the generated 3D model may vary based on the specificity of the prompt.\n\n\n\nAn alternative could have been to create a user-friendly interface for browsing and selecting from pre-existing 3D models. However, this would not offer the same level of customization and convenience as generating a model from a prompt.\n\n\n\nUsers who require highly detailed and specific 3D models may find the prompt-based generation less useful, as it may not always produce the desired level of detail or accuracy.\n\n\n\nThis proposal involves developing a new feature for our platform, which will be done by our development team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - This is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis proposal was assisted by AI assistant Aria."
+    "text": "V-Sekai · GitHub - Official source for V-Sekai dev community.\nV-Sekai/v-sekai-game - Repository for V-Sekai project on social VR in Godot Engine.\n3D humanoid avatar file format for VR\n\nAria assisted with this content."
   },
   {
-    "objectID": "decisions/20240615-what-is-mesh-transformers.html#the-context",
-    "href": "decisions/20240615-what-is-mesh-transformers.html#the-context",
-    "title": "Proposed: Explain the concept of Mesh Transformers",
+    "objectID": "decisions/20220820-market-booth-tutorial.html",
+    "href": "decisions/20220820-market-booth-tutorial.html",
+    "title": "Proposed: Make a market booth creation tutorial.",
     "section": "",
-    "text": "Many of my friends are not tech-savvy."
+    "text": "To present at various virtual market locations, we need to do various workflow steps that are quickly forgotten.\n\n\n\nWe can write down our collective workflows for creation.\n\n\n\nWrite a guide to makie a 3d market booth that is the 4m x 4m x 5m standard size and 2m x 2m x 2.5m constrained size.\n\n\n\n\nSubstance designer\nBlender\n\n\n\n\n\nMake a procedural grid texture and some text.\nPut the booth in blender on the booth boundaries (cube).\n\n\n\n\n\nUpload to Github organization.\n\n\n\n\nIncrease our workflow\n\n\n\n\n\nLoss of creativity\n\n\n\n\n\nOption: Recreate the workflow from scratch\n\n\n\n\nWorkflow enhancement.\n\n\n\nWe are doing this, so we can record how we did it.\n\n\n\n\nV-Sekai\nhttps://www.youtube.com/watch?v=LGZWjyeUPHU\n\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240615-what-is-mesh-transformers.html#the-problem-statement",
-    "href": "decisions/20240615-what-is-mesh-transformers.html#the-problem-statement",
-    "title": "Proposed: Explain the concept of Mesh Transformers",
+    "objectID": "decisions/20220820-market-booth-tutorial.html#tools-used",
+    "href": "decisions/20220820-market-booth-tutorial.html#tools-used",
+    "title": "Proposed: Make a market booth creation tutorial.",
     "section": "",
-    "text": "How can we explain the concept of Mesh Transformers to a student?"
+    "text": "Substance designer\nBlender"
   },
   {
-    "objectID": "decisions/20240615-what-is-mesh-transformers.html#solution-proposal",
-    "href": "decisions/20240615-what-is-mesh-transformers.html#solution-proposal",
-    "title": "Proposed: Explain the concept of Mesh Transformers",
+    "objectID": "decisions/20220820-market-booth-tutorial.html#initial-task",
+    "href": "decisions/20220820-market-booth-tutorial.html#initial-task",
+    "title": "Proposed: Make a market booth creation tutorial.",
     "section": "",
-    "text": "Mesh Transformers can be understood as two parts - a construction worker (auto encoder) and an architect (transformer).\nThe construction worker learns how to construct and build a building, while the architect learns about all the items needed for a building and then instructs the construction worker on what to do.\nThe goal is to allow users to generate a 3D model on the fly using a prompt, instead of searching through numerous 3D libraries and forums. They can simply write what they want and within a few seconds get exactly what they want without settling on a 3D model that they kind of want."
+    "text": "Make a procedural grid texture and some text.\nPut the booth in blender on the booth boundaries (cube)."
   },
   {
-    "objectID": "decisions/20240615-what-is-mesh-transformers.html#the-benefits",
-    "href": "decisions/20240615-what-is-mesh-transformers.html#the-benefits",
-    "title": "Proposed: Explain the concept of Mesh Transformers",
+    "objectID": "decisions/20220820-market-booth-tutorial.html#storage",
+    "href": "decisions/20220820-market-booth-tutorial.html#storage",
+    "title": "Proposed: Make a market booth creation tutorial.",
     "section": "",
-    "text": "This approach simplifies the process of creating 3D models, making it accessible even to those with little to no technical knowledge. It also saves time by eliminating the need to search through various resources."
+    "text": "Upload to Github organization.\n\n\n\n\nIncrease our workflow\n\n\n\n\n\nLoss of creativity\n\n\n\n\n\nOption: Recreate the workflow from scratch\n\n\n\n\nWorkflow enhancement.\n\n\n\nWe are doing this, so we can record how we did it.\n\n\n\n\nV-Sekai\nhttps://www.youtube.com/watch?v=LGZWjyeUPHU\n\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240615-what-is-mesh-transformers.html#the-downsides",
-    "href": "decisions/20240615-what-is-mesh-transformers.html#the-downsides",
-    "title": "Proposed: Explain the concept of Mesh Transformers",
+    "objectID": "decisions/20240830-use-dokku-to-host-vsk-backend.html",
+    "href": "decisions/20240830-use-dokku-to-host-vsk-backend.html",
+    "title": "Proposed: Transition to Dokku from Kubernetes Proposal",
     "section": "",
-    "text": "There might be a learning curve involved in understanding how to use prompts effectively. Also, the quality of the generated 3D model may vary based on the specificity of the prompt."
+    "text": "This proposal outlines the transition of our backend services from Kubernetes to Dokku, aiming to reduce complexity and maintenance costs.\n\n\n\nDokku is a minimalistic, open-source PAAS that provides a cost-effective alternative to Heroku. Our current use of Kubernetes has become prohibitively complex and expensive.\n\n\n\nWe aim to migrate our backend services from Kubernetes to Dokku to simplify operations and reduce expenses.\n\n\n\n\n\n\nPostgreSQL: Deploy using the Dokku PostgreSQL plugin.\nFile Object Store: Implement an S3 compatible storage solution within Dokku.\nElixir “Uro” Backend: Ensure seamless deployment and operation of our Elixir application on Dokku.\nCaddy: Set up Caddy as a web server and reverse proxy for secure HTTP and SSL management.\nRabbitMQ: Integrate RabbitMQ for robust messaging and queuing capabilities.\nBackups: Implement an S3 compatible backup storage solution.\nTelemetry: Use OpenTelemetry for monitoring and tracing by integrating it with Signoz as outlined in this guide.\n\n\n\n\n# Install Dokku plugins\ndokku plugin:install https://github.com/dokku/dokku-postgres.git postgres\ndokku plugin:install https://github.com/dokku/dokku-rabbitmq.git rabbitmq\n\n# Create PostgreSQL service\ndokku postgres:create my-database\n\n# Create RabbitMQ service\ndokku rabbitmq:create my-messaging-service\n\n# Deploy Elixir application\ngit push dokku master\n\n# Setup OpenTelemetry\n# Follow the specific instructions from the Signoz guide\n\n\n\n\n\nCost Efficiency: Significant reduction in operational and maintenance costs.\nSimplicity: Streamlined management and deployment processes.\nScalability: Adequate scaling capabilities without Kubernetes’ overhead.\nSecurity: Enhanced security features with automatic SSL through Caddy.\nReliability: Dependable inter-service communication with RabbitMQ.\n\n\n\n\n\nFeature Limitations: Dokku may not support all Kubernetes features.\nMigration Challenges: Initial hurdles in transferring services and data.\n\n\n\n\n\nPersisting with Kubernetes despite its drawbacks.\nAdopting other PAAS solutions like Heroku or AWS Elastic Beanstalk.\n\n\n\n\nHandling very high traffic levels might require additional Dokku configurations, which are inherently simpler in Kubernetes.\n\n\n\nThe transition will be managed internally by our development team.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai GitHub - Explore more about V-Sekai’s initiatives on social VR.\nV-Sekai Game Repository - Official repository for the V-Sekai game project.\nTigrisData\n\nAssisted by AI assistant Aria."
   },
   {
-    "objectID": "decisions/20240615-what-is-mesh-transformers.html#the-road-not-taken",
-    "href": "decisions/20240615-what-is-mesh-transformers.html#the-road-not-taken",
-    "title": "Proposed: Explain the concept of Mesh Transformers",
+    "objectID": "decisions/20240830-use-dokku-to-host-vsk-backend.html#overview",
+    "href": "decisions/20240830-use-dokku-to-host-vsk-backend.html#overview",
+    "title": "Proposed: Transition to Dokku from Kubernetes Proposal",
     "section": "",
-    "text": "An alternative could have been to create a user-friendly interface for browsing and selecting from pre-existing 3D models. However, this would not offer the same level of customization and convenience as generating a model from a prompt."
+    "text": "This proposal outlines the transition of our backend services from Kubernetes to Dokku, aiming to reduce complexity and maintenance costs."
   },
   {
-    "objectID": "decisions/20240615-what-is-mesh-transformers.html#the-infrequent-use-case",
-    "href": "decisions/20240615-what-is-mesh-transformers.html#the-infrequent-use-case",
-    "title": "Proposed: Explain the concept of Mesh Transformers",
+    "objectID": "decisions/20240830-use-dokku-to-host-vsk-backend.html#context",
+    "href": "decisions/20240830-use-dokku-to-host-vsk-backend.html#context",
+    "title": "Proposed: Transition to Dokku from Kubernetes Proposal",
     "section": "",
-    "text": "Users who require highly detailed and specific 3D models may find the prompt-based generation less useful, as it may not always produce the desired level of detail or accuracy."
+    "text": "Dokku is a minimalistic, open-source PAAS that provides a cost-effective alternative to Heroku. Our current use of Kubernetes has become prohibitively complex and expensive."
   },
   {
-    "objectID": "decisions/20240615-what-is-mesh-transformers.html#in-core-and-done-by-us",
-    "href": "decisions/20240615-what-is-mesh-transformers.html#in-core-and-done-by-us",
-    "title": "Proposed: Explain the concept of Mesh Transformers",
+    "objectID": "decisions/20240830-use-dokku-to-host-vsk-backend.html#problem-statement",
+    "href": "decisions/20240830-use-dokku-to-host-vsk-backend.html#problem-statement",
+    "title": "Proposed: Transition to Dokku from Kubernetes Proposal",
     "section": "",
-    "text": "This proposal involves developing a new feature for our platform, which will be done by our development team."
+    "text": "We aim to migrate our backend services from Kubernetes to Dokku to simplify operations and reduce expenses."
   },
   {
-    "objectID": "decisions/20240615-what-is-mesh-transformers.html#status",
-    "href": "decisions/20240615-what-is-mesh-transformers.html#status",
-    "title": "Proposed: Explain the concept of Mesh Transformers",
+    "objectID": "decisions/20240830-use-dokku-to-host-vsk-backend.html#implementation-details",
+    "href": "decisions/20240830-use-dokku-to-host-vsk-backend.html#implementation-details",
+    "title": "Proposed: Transition to Dokku from Kubernetes Proposal",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "PostgreSQL: Deploy using the Dokku PostgreSQL plugin.\nFile Object Store: Implement an S3 compatible storage solution within Dokku.\nElixir “Uro” Backend: Ensure seamless deployment and operation of our Elixir application on Dokku.\nCaddy: Set up Caddy as a web server and reverse proxy for secure HTTP and SSL management.\nRabbitMQ: Integrate RabbitMQ for robust messaging and queuing capabilities.\nBackups: Implement an S3 compatible backup storage solution.\nTelemetry: Use OpenTelemetry for monitoring and tracing by integrating it with Signoz as outlined in this guide.\n\n\n\n\n# Install Dokku plugins\ndokku plugin:install https://github.com/dokku/dokku-postgres.git postgres\ndokku plugin:install https://github.com/dokku/dokku-rabbitmq.git rabbitmq\n\n# Create PostgreSQL service\ndokku postgres:create my-database\n\n# Create RabbitMQ service\ndokku rabbitmq:create my-messaging-service\n\n# Deploy Elixir application\ngit push dokku master\n\n# Setup OpenTelemetry\n# Follow the specific instructions from the Signoz guide"
   },
   {
-    "objectID": "decisions/20240615-what-is-mesh-transformers.html#decision-makers",
-    "href": "decisions/20240615-what-is-mesh-transformers.html#decision-makers",
-    "title": "Proposed: Explain the concept of Mesh Transformers",
+    "objectID": "decisions/20240830-use-dokku-to-host-vsk-backend.html#benefits",
+    "href": "decisions/20240830-use-dokku-to-host-vsk-backend.html#benefits",
+    "title": "Proposed: Transition to Dokku from Kubernetes Proposal",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "Cost Efficiency: Significant reduction in operational and maintenance costs.\nSimplicity: Streamlined management and deployment processes.\nScalability: Adequate scaling capabilities without Kubernetes’ overhead.\nSecurity: Enhanced security features with automatic SSL through Caddy.\nReliability: Dependable inter-service communication with RabbitMQ."
   },
   {
-    "objectID": "decisions/20240615-what-is-mesh-transformers.html#tags",
-    "href": "decisions/20240615-what-is-mesh-transformers.html#tags",
-    "title": "Proposed: Explain the concept of Mesh Transformers",
+    "objectID": "decisions/20240830-use-dokku-to-host-vsk-backend.html#potential-downsides",
+    "href": "decisions/20240830-use-dokku-to-host-vsk-backend.html#potential-downsides",
+    "title": "Proposed: Transition to Dokku from Kubernetes Proposal",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Feature Limitations: Dokku may not support all Kubernetes features.\nMigration Challenges: Initial hurdles in transferring services and data."
   },
   {
-    "objectID": "decisions/20240615-what-is-mesh-transformers.html#further-reading",
-    "href": "decisions/20240615-what-is-mesh-transformers.html#further-reading",
-    "title": "Proposed: Explain the concept of Mesh Transformers",
+    "objectID": "decisions/20240830-use-dokku-to-host-vsk-backend.html#alternatives-considered",
+    "href": "decisions/20240830-use-dokku-to-host-vsk-backend.html#alternatives-considered",
+    "title": "Proposed: Transition to Dokku from Kubernetes Proposal",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - This is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis proposal was assisted by AI assistant Aria."
+    "text": "Persisting with Kubernetes despite its drawbacks.\nAdopting other PAAS solutions like Heroku or AWS Elastic Beanstalk."
   },
   {
-    "objectID": "decisions/20211005-want-to-summon-friends-and-acquaintances-via-presence.html",
-    "href": "decisions/20211005-want-to-summon-friends-and-acquaintances-via-presence.html",
-    "title": "Proposed: Summon #friend and acquaintances via presence to the current world.",
+    "objectID": "decisions/20240830-use-dokku-to-host-vsk-backend.html#special-considerations",
+    "href": "decisions/20240830-use-dokku-to-host-vsk-backend.html#special-considerations",
+    "title": "Proposed: Transition to Dokku from Kubernetes Proposal",
     "section": "",
-    "text": "Proposed: Summon #friend and acquaintances via presence to the current world.\n\nContext and Problem Statement\nWant to summon #friend and acquaintances via presence.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nBy using rich presence #friend can join my location.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nAble to be a tray item and a graphical window.\nAble to have new friends.\nUpdate my current world and current position on changes.\nNotification is a visually distinct status that reflects presence of friends.\n\nPrivacy\n\nShare nothing\nShare world\nShare world location\n\n\n\nEngineering\nUse libp2p as a Godot Engine 4 c++ module working on Godot Engine on Win10, Macos and Linux (Popos! 21.04).\nHow do we get presence information?\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot a few lines of script to implement presence.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nCan be done as a group.\n\n\nReferences\n\nhttps://github.com/libp2p/cpp-libp2p\nhttps://github.com/fire/godot-p2p/\nhttps://did-ipid.github.io/ipid-did-method/\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Handling very high traffic levels might require additional Dokku configurations, which are inherently simpler in Kubernetes."
   },
   {
-    "objectID": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html",
-    "href": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html",
-    "title": "Accepted: PCI-E Lane Depletion and Thunderbolt 4 Issues",
+    "objectID": "decisions/20240830-use-dokku-to-host-vsk-backend.html#project-management",
+    "href": "decisions/20240830-use-dokku-to-host-vsk-backend.html#project-management",
+    "title": "Proposed: Transition to Dokku from Kubernetes Proposal",
     "section": "",
-    "text": "In modern computing, PCI-E lanes are a critical resource for connecting various high-speed components such as GPUs, SSDs, and network cards. However, the number of available PCI-E lanes is finite and can become a bottleneck when multiple high-bandwidth devices are connected. This proposal addresses the issue of PCI-E lane depletion, particularly in systems utilizing Thunderbolt 4.\n\n\n\nWhen all PCI-E slots are utilized, especially with high-bandwidth devices like GPUs and Thunderbolt 4 controllers, users may experience performance degradation or device malfunctions due to insufficient PCI-E lanes. This problem was highlighted by a user who reported that their Thunderbolt 4 connection broke after using their last PCI-E slot.\n\n\n\nTo mitigate this issue, it is recommended to keep the last PCI-E slot empty to ensure sufficient lanes for all connected devices.\n+-------------------+\n|   CPU             |\n|                   |\n| PCI-E Lanes    |\n+---------+---------+\n          |\n          v\n+---------+---------+\n|       PCI-E       |\n|      Switch       |\n+---------+---------+\n          |\n          v\n+---------+---------+---------+---------+\n|   GPU   | Thunderbolt 4 |  NVMe SSD  |\n|     |           |        |\n+---------+---------+---------+---------+\n\n\n\n\nImproved System Stability: Ensuring sufficient PCI-E lanes for all devices will prevent system crashes and performance issues.\nOptimized Resource Allocation: Users can make informed decisions about which devices to prioritize based on available PCI-E lanes.\nEnhanced User Experience: By avoiding unexpected device failures, users will have a more reliable and predictable computing experience.\n\n\n\n\n\nComplexity: Implementing checks for PCI-E lane availability adds complexity to system configuration and management.\nHardware Limitations: Users with limited PCI-E lanes may need to upgrade their hardware to fully utilize all desired devices.\n\n\n\n\nAn alternative approach could be to develop software solutions that dynamically manage PCI-E lane allocation based on real-time usage patterns. However, this would require significant changes to both hardware and software architectures and may not be feasible for all users.\n\n\n\nIn scenarios where users only utilize a single high-bandwidth device, such as a GPU, PCI-E lane depletion is unlikely to be an issue. This proposal primarily targets power users and professionals with multiple high-bandwidth devices.\n\n\n\nThe V-Sekai development team will integrate PCI-E lane checks into the system configuration process, ensuring that users are alerted to potential lane depletion issues before they occur.\n\n\n\nStatus: Accepted \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "The transition will be managed internally by our development team."
   },
   {
-    "objectID": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#the-context",
-    "href": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#the-context",
-    "title": "Accepted: PCI-E Lane Depletion and Thunderbolt 4 Issues",
+    "objectID": "decisions/20240830-use-dokku-to-host-vsk-backend.html#current-status",
+    "href": "decisions/20240830-use-dokku-to-host-vsk-backend.html#current-status",
+    "title": "Proposed: Transition to Dokku from Kubernetes Proposal",
     "section": "",
-    "text": "In modern computing, PCI-E lanes are a critical resource for connecting various high-speed components such as GPUs, SSDs, and network cards. However, the number of available PCI-E lanes is finite and can become a bottleneck when multiple high-bandwidth devices are connected. This proposal addresses the issue of PCI-E lane depletion, particularly in systems utilizing Thunderbolt 4."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#the-problem-statement",
-    "href": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#the-problem-statement",
-    "title": "Accepted: PCI-E Lane Depletion and Thunderbolt 4 Issues",
+    "objectID": "decisions/20240830-use-dokku-to-host-vsk-backend.html#decision-makers",
+    "href": "decisions/20240830-use-dokku-to-host-vsk-backend.html#decision-makers",
+    "title": "Proposed: Transition to Dokku from Kubernetes Proposal",
     "section": "",
-    "text": "When all PCI-E slots are utilized, especially with high-bandwidth devices like GPUs and Thunderbolt 4 controllers, users may experience performance degradation or device malfunctions due to insufficient PCI-E lanes. This problem was highlighted by a user who reported that their Thunderbolt 4 connection broke after using their last PCI-E slot."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#proposal-implementation",
-    "href": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#proposal-implementation",
-    "title": "Accepted: PCI-E Lane Depletion and Thunderbolt 4 Issues",
+    "objectID": "decisions/20240830-use-dokku-to-host-vsk-backend.html#tags",
+    "href": "decisions/20240830-use-dokku-to-host-vsk-backend.html#tags",
+    "title": "Proposed: Transition to Dokku from Kubernetes Proposal",
     "section": "",
-    "text": "To mitigate this issue, it is recommended to keep the last PCI-E slot empty to ensure sufficient lanes for all connected devices.\n+-------------------+\n|   CPU             |\n|                   |\n| PCI-E Lanes    |\n+---------+---------+\n          |\n          v\n+---------+---------+\n|       PCI-E       |\n|      Switch       |\n+---------+---------+\n          |\n          v\n+---------+---------+---------+---------+\n|   GPU   | Thunderbolt 4 |  NVMe SSD  |\n|     |           |        |\n+---------+---------+---------+---------+"
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#the-benefits",
-    "href": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#the-benefits",
-    "title": "Accepted: PCI-E Lane Depletion and Thunderbolt 4 Issues",
+    "objectID": "decisions/20240830-use-dokku-to-host-vsk-backend.html#further-information",
+    "href": "decisions/20240830-use-dokku-to-host-vsk-backend.html#further-information",
+    "title": "Proposed: Transition to Dokku from Kubernetes Proposal",
     "section": "",
-    "text": "Improved System Stability: Ensuring sufficient PCI-E lanes for all devices will prevent system crashes and performance issues.\nOptimized Resource Allocation: Users can make informed decisions about which devices to prioritize based on available PCI-E lanes.\nEnhanced User Experience: By avoiding unexpected device failures, users will have a more reliable and predictable computing experience."
+    "text": "V-Sekai GitHub - Explore more about V-Sekai’s initiatives on social VR.\nV-Sekai Game Repository - Official repository for the V-Sekai game project.\nTigrisData\n\nAssisted by AI assistant Aria."
   },
   {
-    "objectID": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#the-downsides",
-    "href": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#the-downsides",
-    "title": "Accepted: PCI-E Lane Depletion and Thunderbolt 4 Issues",
+    "objectID": "decisions/20230131-adopt-best-product-development-practices.html",
+    "href": "decisions/20230131-adopt-best-product-development-practices.html",
+    "title": "Proposed: Adopt best practices for product development",
     "section": "",
-    "text": "Complexity: Implementing checks for PCI-E lane availability adds complexity to system configuration and management.\nHardware Limitations: Users with limited PCI-E lanes may need to upgrade their hardware to fully utilize all desired devices."
+    "text": "Proposed: Adopt best practices for product development\n\nMetadata\n\nStatus: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nContext and Problem Statement\nWe should adopt best practices in developing products.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nToyota has a system that was designed with decades of best practices.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\n\nCoordination Based on Writing\nMentoring Supervisors\nIntegrative Leaders\nStandard Skills\nFlexible Work Standards\nLiving Design Standards\n\nThe six mechanisms that make up the quality control system are mentoring supervision, chief engineers, cross-functional communication, working instructions and standards.\nMentoring supervision serves mainly to build functional expertise, but it also teaches young engineers how to write and interpret reports, work with chief engineers, and understand and use standards. The chief engineer’s prestige reinforces the importance of expertise while it also balances out the functional bent of the other engineers. The chief engineer also promotes mutual adjustment by providing the working instructions for each vehicle program and by resolving cross-functional disagreements.\nThe second mechanism is cross-functional communication. Every major feature requires at least an introduction so it needs a corresponding page with a descriptive title.\n\n\nPositive Consequences\nWe are able to use V-Sekai easier.\n\n\nNegative Consequences\nThese aspects can be incompatible with current practices.\n\n\nOption graveyard\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nKnowing what to do is hard.\n\n\nIs there a reason why this should be core and done by us?\nHow we develop the project is a core task.\n\n\nReferences\n\nV-Sekai\nanother-look-at-how-toyota-integrates-product-development"
   },
   {
-    "objectID": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#the-road-not-taken",
-    "href": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#the-road-not-taken",
-    "title": "Accepted: PCI-E Lane Depletion and Thunderbolt 4 Issues",
+    "objectID": "decisions/20230505-cross-platform-artwork-distribution.html",
+    "href": "decisions/20230505-cross-platform-artwork-distribution.html",
+    "title": "Proposed: Enhancing Cross-Platform Compatibility and User Experience for V-Sekai VR Social Players",
     "section": "",
-    "text": "An alternative approach could be to develop software solutions that dynamically manage PCI-E lane allocation based on real-time usage patterns. However, this would require significant changes to both hardware and software architectures and may not be feasible for all users."
+    "text": "Status: proposed \nDeciders: V-Sekai, fire\nTags: V-Sekai, ChatGPT-4\n\n\n\n\nV-Sekai faces limitations in providing a seamless cross-platform experience for VR Social players. How can we improve compatibility and user experience across various platforms?\n\n\n\nDistribute artwork in Blend, VRM, and Unity Asset Package formats to ensure easy portability and compatibility with multiple platforms, enhancing the overall user experience.\n\n\n\n\nCreate and export artwork in Blend, VRM, and Unity Asset Package formats.\nUtilize appropriate formats for each platform, ensuring compatibility and optimal performance.\n\n\n\n\n\nImproved compatibility across various platforms.\nEnhanced user experience for VR Social players.\nIncreased adoption of V-Sekai due to better cross-platform support.\n\n\n\n\n\nAdditional development time and resources required to create and maintain multiple asset formats.\nPotential performance issues on lower-end devices.\n\n\n\n\n\nCreating separate assets and configurations for each platform, increasing development time and maintenance complexity.\n\n\n\n\nThis enhancement aims to improve the core experience for users across various platforms and cannot be achieved with a simple workaround.\n\n\n\nProviding a seamless cross-platform experience is essential for V-Sekai’s success. Implementing this feature in-house ensures full control over its development and tailoring to specific needs.\n\n\n\n\nV-Sekai\nUnityVRM: https://github.com/vrm-c/UniVRM\nSilent Cel Shading Shader for Unity Game Engine: https://gitlab.com/s-ilent/SCSS\nSilent Cel Shading Shader for Godot Engine: https://github.com/lyuma/SCSS-Godot"
   },
   {
-    "objectID": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#the-infrequent-use-case",
-    "href": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#the-infrequent-use-case",
-    "title": "Accepted: PCI-E Lane Depletion and Thunderbolt 4 Issues",
+    "objectID": "decisions/20230505-cross-platform-artwork-distribution.html#metadata",
+    "href": "decisions/20230505-cross-platform-artwork-distribution.html#metadata",
+    "title": "Proposed: Enhancing Cross-Platform Compatibility and User Experience for V-Sekai VR Social Players",
     "section": "",
-    "text": "In scenarios where users only utilize a single high-bandwidth device, such as a GPU, PCI-E lane depletion is unlikely to be an issue. This proposal primarily targets power users and professionals with multiple high-bandwidth devices."
+    "text": "Status: proposed \nDeciders: V-Sekai, fire\nTags: V-Sekai, ChatGPT-4"
   },
   {
-    "objectID": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#in-core-and-done-by-us",
-    "href": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#in-core-and-done-by-us",
-    "title": "Accepted: PCI-E Lane Depletion and Thunderbolt 4 Issues",
+    "objectID": "decisions/20230505-cross-platform-artwork-distribution.html#context-and-problem-statement",
+    "href": "decisions/20230505-cross-platform-artwork-distribution.html#context-and-problem-statement",
+    "title": "Proposed: Enhancing Cross-Platform Compatibility and User Experience for V-Sekai VR Social Players",
     "section": "",
-    "text": "The V-Sekai development team will integrate PCI-E lane checks into the system configuration process, ensuring that users are alerted to potential lane depletion issues before they occur."
+    "text": "V-Sekai faces limitations in providing a seamless cross-platform experience for VR Social players. How can we improve compatibility and user experience across various platforms?"
   },
   {
-    "objectID": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#status",
-    "href": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#status",
-    "title": "Accepted: PCI-E Lane Depletion and Thunderbolt 4 Issues",
+    "objectID": "decisions/20230505-cross-platform-artwork-distribution.html#proposed-solution",
+    "href": "decisions/20230505-cross-platform-artwork-distribution.html#proposed-solution",
+    "title": "Proposed: Enhancing Cross-Platform Compatibility and User Experience for V-Sekai VR Social Players",
     "section": "",
-    "text": "Status: Accepted"
+    "text": "Distribute artwork in Blend, VRM, and Unity Asset Package formats to ensure easy portability and compatibility with multiple platforms, enhancing the overall user experience."
   },
   {
-    "objectID": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#decision-makers",
-    "href": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#decision-makers",
-    "title": "Accepted: PCI-E Lane Depletion and Thunderbolt 4 Issues",
+    "objectID": "decisions/20230505-cross-platform-artwork-distribution.html#implementation",
+    "href": "decisions/20230505-cross-platform-artwork-distribution.html#implementation",
+    "title": "Proposed: Enhancing Cross-Platform Compatibility and User Experience for V-Sekai VR Social Players",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "Create and export artwork in Blend, VRM, and Unity Asset Package formats.\nUtilize appropriate formats for each platform, ensuring compatibility and optimal performance."
   },
   {
-    "objectID": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#tags",
-    "href": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#tags",
-    "title": "Accepted: PCI-E Lane Depletion and Thunderbolt 4 Issues",
+    "objectID": "decisions/20230505-cross-platform-artwork-distribution.html#positive-consequences",
+    "href": "decisions/20230505-cross-platform-artwork-distribution.html#positive-consequences",
+    "title": "Proposed: Enhancing Cross-Platform Compatibility and User Experience for V-Sekai VR Social Players",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Improved compatibility across various platforms.\nEnhanced user experience for VR Social players.\nIncreased adoption of V-Sekai due to better cross-platform support."
   },
   {
-    "objectID": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#further-reading",
-    "href": "decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html#further-reading",
-    "title": "Accepted: PCI-E Lane Depletion and Thunderbolt 4 Issues",
+    "objectID": "decisions/20230505-cross-platform-artwork-distribution.html#negative-consequences",
+    "href": "decisions/20230505-cross-platform-artwork-distribution.html#negative-consequences",
+    "title": "Proposed: Enhancing Cross-Platform Compatibility and User Experience for V-Sekai VR Social Players",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "Additional development time and resources required to create and maintain multiple asset formats.\nPotential performance issues on lower-end devices."
   },
   {
-    "objectID": "decisions/20211031-standard-backup-procedures.html",
-    "href": "decisions/20211031-standard-backup-procedures.html",
-    "title": "Proposed: Standard backup procedures",
+    "objectID": "decisions/20230505-cross-platform-artwork-distribution.html#option-graveyard",
+    "href": "decisions/20230505-cross-platform-artwork-distribution.html#option-graveyard",
+    "title": "Proposed: Enhancing Cross-Platform Compatibility and User Experience for V-Sekai VR Social Players",
     "section": "",
-    "text": "Proposed: Standard backup procedures\n\nContext and Problem Statement\nThings that aren’t backed up get lost.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nBackup V-Sekai Github organization with V-Sekai-gitm and V-Sekai-github-backup.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nUse https://github.com/muhasturk/gitim to backup V-sekai. (tested 7b6e898b7587f61b0c5f00c3ab9862868f94479d )\ngit clone https://github.com/muhasturk/gitim.git\ncd gitim\npip install .\ncd -\nexport ACCESS_TOKEN=AAAA\npython3 -m gitim -o V-Sekai -d V-Sekai-godot-gitm-`date --iso=date --utc` --ssh --token $ACCESS_TOKEN\nUse https://github.com/josegonzalez/python-github-backup to backup. (tested 0.40.0)\npip install github-backup\nexport ACCESS_TOKEN=AAAA\ngithub-backup V-Sekai --token $ACCESS_TOKEN --organization --output-directory V-Sekai-Backup-`date --iso=date --utc` --incremental --prefer-ssh --lfs --private --fork --private --all\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot able to.\n\n\nPositive Consequences\n\nTwo backups combined should cover all cases\n\n\n\nNegative Consequences\n\ngithub-backup doesn’t backup repos that are accessible in the dependencies\ngitm doesn’t backup issues\n\n\n\nIs there a reason why this should be core and done by us?\nOnly we have access to a complete copy of the repo.\n\n\nReferences\n\nhttps://github.com/josegonzalez/python-github-backup\nhttps://github.com/muhasturk/gitim\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Creating separate assets and configurations for each platform, increasing development time and maintenance complexity."
   },
   {
-    "objectID": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html",
-    "href": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html",
-    "title": "Superseded: Planning V-Sekai on 2022-02-21 Superseded",
+    "objectID": "decisions/20230505-cross-platform-artwork-distribution.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230505-cross-platform-artwork-distribution.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Enhancing Cross-Platform Compatibility and User Experience for V-Sekai VR Social Players",
     "section": "",
-    "text": "Status: superseded \nDeciders: V-Sekai,ifire,lyuma,\nTags: V-Sekai,\n\n\n\nSuperseded - See https://github.com/V-Sekai/V-Sekai/blob/master/decisions/20220224-v-sekai-version-two-plan.md\nKnow where we’re going by describing what we want.\n\n\n\nProposed mission and a list of tasks.\n\n\n\n\n\n\nGodot Engine pull requests.\n\n\n\n\n\nOne gitlab repo with source assets? (sky celebration and sponza).\n\n\nThe ability to upload maps and avatars standalone via a SDK (set of submodules?) https://github.com/V-Sekai/vsk_sdk.\n\nBeing able to enter a vsk map ∀ maps (mvp = 1 map).\nEnter a vsk map with an entity in it (upload sky celebration OR upload sponza with one beachball).\n\nVSK_map source asset repositories\nLyuma will make a new github repo V-Sekai/vrm_submodule - we need a script for updating all submodules to the latest on a given branch.\nVSK_map source asset repositories\nI think vsk_sdk should only be submodules, no assets.\nWe can git rebase -i to remove the binary assets from it.\ngit merge to install the vsk_sdk into another project (such as gitlab). we need to look if git subtree supports .gitmodules and we can use it if it does.\nmake vsk_sdk the head for all of the sdk related submodules. do our development there and commit submodules regularly.\nIn groups project, pretend we delete all submodules in vsk_sdk. Then git merge vsk_sdk/main to bring in the submodules from that repo.\nEvery time we update vsk_sdk, do a git merge into groups and our source asset repo with sponza etc.\nVSK_map source asset repositories\n\nDon’t save .scn assets in git.\n\nno GLB.\nblend files ~10MB ok. &gt; 100MB let’s either use GitLab LFS or something else.\nEvaluate https://dvc.org/\n\n\n\n\nBeing able to have our group of people join and communicate. (godot speech).\n\n\nPorting C++ was discussed as a way forward to make it easier to debug\n\n\nVR support (openxr).\nInteracting with objects in desktop mode is important so that we can test easier.\nInteracting with objects in vr.\nScripting (wasgo).\nNetwork server to support 1000.\n\n\n\n\n\nGain clarity of mission.\n\n\n\n\nThe cost of overhead.\n\n\n\n\n\nOption: Status quo. \nRejection Reason: Complete the wrong thing. \n\n\n\n\nThis is a planning document.\n\n\n\nWe know what we want to do.\n\n\n\n\nNone\n\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "This enhancement aims to improve the core experience for users across various platforms and cannot be achieved with a simple workaround."
   },
   {
-    "objectID": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html#context-and-problem-statement",
-    "href": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html#context-and-problem-statement",
-    "title": "Superseded: Planning V-Sekai on 2022-02-21 Superseded",
+    "objectID": "decisions/20230505-cross-platform-artwork-distribution.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230505-cross-platform-artwork-distribution.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Enhancing Cross-Platform Compatibility and User Experience for V-Sekai VR Social Players",
     "section": "",
-    "text": "Superseded - See https://github.com/V-Sekai/V-Sekai/blob/master/decisions/20220224-v-sekai-version-two-plan.md\nKnow where we’re going by describing what we want."
+    "text": "Providing a seamless cross-platform experience is essential for V-Sekai’s success. Implementing this feature in-house ensures full control over its development and tailoring to specific needs."
   },
   {
-    "objectID": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Superseded: Planning V-Sekai on 2022-02-21 Superseded",
+    "objectID": "decisions/20230505-cross-platform-artwork-distribution.html#references",
+    "href": "decisions/20230505-cross-platform-artwork-distribution.html#references",
+    "title": "Proposed: Enhancing Cross-Platform Compatibility and User Experience for V-Sekai VR Social Players",
     "section": "",
-    "text": "Proposed mission and a list of tasks."
+    "text": "V-Sekai\nUnityVRM: https://github.com/vrm-c/UniVRM\nSilent Cel Shading Shader for Unity Game Engine: https://gitlab.com/s-ilent/SCSS\nSilent Cel Shading Shader for Godot Engine: https://github.com/lyuma/SCSS-Godot"
   },
   {
-    "objectID": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Superseded: Planning V-Sekai on 2022-02-21 Superseded",
+    "objectID": "decisions/20240627-gdextension-as-libriscv.html",
+    "href": "decisions/20240627-gdextension-as-libriscv.html",
+    "title": "Superceded: RISCV Binaries as Shared Libraries",
     "section": "",
-    "text": "Godot Engine pull requests.\n\n\n\n\n\nOne gitlab repo with source assets? (sky celebration and sponza).\n\n\nThe ability to upload maps and avatars standalone via a SDK (set of submodules?) https://github.com/V-Sekai/vsk_sdk.\n\nBeing able to enter a vsk map ∀ maps (mvp = 1 map).\nEnter a vsk map with an entity in it (upload sky celebration OR upload sponza with one beachball).\n\nVSK_map source asset repositories\nLyuma will make a new github repo V-Sekai/vrm_submodule - we need a script for updating all submodules to the latest on a given branch.\nVSK_map source asset repositories\nI think vsk_sdk should only be submodules, no assets.\nWe can git rebase -i to remove the binary assets from it.\ngit merge to install the vsk_sdk into another project (such as gitlab). we need to look if git subtree supports .gitmodules and we can use it if it does.\nmake vsk_sdk the head for all of the sdk related submodules. do our development there and commit submodules regularly.\nIn groups project, pretend we delete all submodules in vsk_sdk. Then git merge vsk_sdk/main to bring in the submodules from that repo.\nEvery time we update vsk_sdk, do a git merge into groups and our source asset repo with sponza etc.\nVSK_map source asset repositories\n\nDon’t save .scn assets in git.\n\nno GLB.\nblend files ~10MB ok. &gt; 100MB let’s either use GitLab LFS or something else.\nEvaluate https://dvc.org/\n\n\n\n\nBeing able to have our group of people join and communicate. (godot speech).\n\n\nPorting C++ was discussed as a way forward to make it easier to debug\n\n\nVR support (openxr).\nInteracting with objects in desktop mode is important so that we can test easier.\nInteracting with objects in vr.\nScripting (wasgo).\nNetwork server to support 1000."
+    "text": "In the current development landscape, there is a growing need for more efficient and flexible ways to handle gdextension binaries. This proposal was inspired by a conversation between Fire and ホロ on June 27, 2024.\nWe also want to investigate players distributing riscv binaries as user generated scripts inside of godot scenes.\n\n\n\nTraditionally we have to compile gdextension for like 5-10 platform variants which is inefficient.\n\n\n\nFire proposed an idea where many gdextension modules can be compiled as RISCV binaries.\nFunctioning like shared libraries via librisc emulation both as an intepreter or a register machine.\nThis could potentially allow wrapping up the entire gdextension API.\nHere’s an example of how function calls into the guest VM could work:\n// See further reading section.\n// Host:\nint ret = machine.vmcall(\"test\", 111, 222, \"333\");\nprintf(\"test returned %d\\n\", ret);\n\n// Guest:\nextern \"C\" __attribute__((used, retain))\nint test(int a, int b, const char* c) {\n    return a + b;\n}\nThis approach would make arbitrary function calls into the VM guest possible. The functions must be C ABI, and if you use the string name, the function must be in the symbol table.\nThis can also be a future approach into compiling gdscript bytecode as more performant code via string templating the bytecode as c and compiling it, but that is reserved for future work.\n\n\n\n\nIncreased efficiency and flexibility in handling RISCV binaries.\nPotential to wrap the entire gdextension API.\nMore convenient and capable of doing things that can’t be done in gdscript.\nCan also be built as a gdextension.\n\n\n\n\n\nRequires significant changes to the existing system.\nMay introduce new complexities and potential security risks.\n\n\n\n\n\nExploring other methods of improving flexibility of loading binaries - like wasm.\nHolo has given me an implementation of riscv processors in godot engine via zig language.\n\n\n\n\n\nThis proposal may not be beneficial for small-scale projects or those that do not require high levels of efficiency and flexibility in handling RISCV binaries.\n\n\n\n\n\nThis proposal will be implemented by the V-Sekai development team, with potential contributions from the wider open-source community.\n\n\n\n\nStatus: Superseded by Build a tiny RISC virtual machine which can interpret and execute GDExtensions\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nlibriscv VM Call Documentation - Detailed documentation on making function calls into the VM guest.\n[https://c9x.me/compile/]\n[https://github.com/Vahera/godot-orchestrator]\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html#positive-consequences",
-    "href": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html#positive-consequences",
-    "title": "Superseded: Planning V-Sekai on 2022-02-21 Superseded",
+    "objectID": "decisions/20240627-gdextension-as-libriscv.html#the-context",
+    "href": "decisions/20240627-gdextension-as-libriscv.html#the-context",
+    "title": "Superceded: RISCV Binaries as Shared Libraries",
     "section": "",
-    "text": "Gain clarity of mission."
+    "text": "In the current development landscape, there is a growing need for more efficient and flexible ways to handle gdextension binaries. This proposal was inspired by a conversation between Fire and ホロ on June 27, 2024.\nWe also want to investigate players distributing riscv binaries as user generated scripts inside of godot scenes."
   },
   {
-    "objectID": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html#negative-consequences",
-    "href": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html#negative-consequences",
-    "title": "Superseded: Planning V-Sekai on 2022-02-21 Superseded",
+    "objectID": "decisions/20240627-gdextension-as-libriscv.html#the-problem-statement",
+    "href": "decisions/20240627-gdextension-as-libriscv.html#the-problem-statement",
+    "title": "Superceded: RISCV Binaries as Shared Libraries",
     "section": "",
-    "text": "The cost of overhead."
+    "text": "Traditionally we have to compile gdextension for like 5-10 platform variants which is inefficient."
   },
   {
-    "objectID": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html#option-graveyard",
-    "href": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html#option-graveyard",
-    "title": "Superseded: Planning V-Sekai on 2022-02-21 Superseded",
+    "objectID": "decisions/20240627-gdextension-as-libriscv.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240627-gdextension-as-libriscv.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Superceded: RISCV Binaries as Shared Libraries",
     "section": "",
-    "text": "Option: Status quo. \nRejection Reason: Complete the wrong thing."
+    "text": "Fire proposed an idea where many gdextension modules can be compiled as RISCV binaries.\nFunctioning like shared libraries via librisc emulation both as an intepreter or a register machine.\nThis could potentially allow wrapping up the entire gdextension API.\nHere’s an example of how function calls into the guest VM could work:\n// See further reading section.\n// Host:\nint ret = machine.vmcall(\"test\", 111, 222, \"333\");\nprintf(\"test returned %d\\n\", ret);\n\n// Guest:\nextern \"C\" __attribute__((used, retain))\nint test(int a, int b, const char* c) {\n    return a + b;\n}\nThis approach would make arbitrary function calls into the VM guest possible. The functions must be C ABI, and if you use the string name, the function must be in the symbol table.\nThis can also be a future approach into compiling gdscript bytecode as more performant code via string templating the bytecode as c and compiling it, but that is reserved for future work."
   },
   {
-    "objectID": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Superseded: Planning V-Sekai on 2022-02-21 Superseded",
+    "objectID": "decisions/20240627-gdextension-as-libriscv.html#the-benefits",
+    "href": "decisions/20240627-gdextension-as-libriscv.html#the-benefits",
+    "title": "Superceded: RISCV Binaries as Shared Libraries",
     "section": "",
-    "text": "This is a planning document."
+    "text": "Increased efficiency and flexibility in handling RISCV binaries.\nPotential to wrap the entire gdextension API.\nMore convenient and capable of doing things that can’t be done in gdscript.\nCan also be built as a gdextension."
   },
   {
-    "objectID": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Superseded: Planning V-Sekai on 2022-02-21 Superseded",
+    "objectID": "decisions/20240627-gdextension-as-libriscv.html#the-downsides",
+    "href": "decisions/20240627-gdextension-as-libriscv.html#the-downsides",
+    "title": "Superceded: RISCV Binaries as Shared Libraries",
     "section": "",
-    "text": "We know what we want to do."
+    "text": "Requires significant changes to the existing system.\nMay introduce new complexities and potential security risks."
   },
   {
-    "objectID": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html#references",
-    "href": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html#references",
-    "title": "Superseded: Planning V-Sekai on 2022-02-21 Superseded",
+    "objectID": "decisions/20240627-gdextension-as-libriscv.html#the-road-not-taken",
+    "href": "decisions/20240627-gdextension-as-libriscv.html#the-road-not-taken",
+    "title": "Superceded: RISCV Binaries as Shared Libraries",
     "section": "",
-    "text": "None"
+    "text": "Exploring other methods of improving flexibility of loading binaries - like wasm.\nHolo has given me an implementation of riscv processors in godot engine via zig language."
   },
   {
-    "objectID": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html#derivative-license",
-    "href": "decisions/20220222-know-where-we-re-going-by-planning-vsekai.html#derivative-license",
-    "title": "Superseded: Planning V-Sekai on 2022-02-21 Superseded",
+    "objectID": "decisions/20240627-gdextension-as-libriscv.html#the-infrequent-use-case",
+    "href": "decisions/20240627-gdextension-as-libriscv.html#the-infrequent-use-case",
+    "title": "Superceded: RISCV Binaries as Shared Libraries",
     "section": "",
-    "text": "Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "This proposal may not be beneficial for small-scale projects or those that do not require high levels of efficiency and flexibility in handling RISCV binaries."
   },
   {
-    "objectID": "decisions/20231230-spatiallabs-openvr.html",
-    "href": "decisions/20231230-spatiallabs-openvr.html",
-    "title": "Deprecated: Valid configuration of Spatiallabs and Openxr",
+    "objectID": "decisions/20240627-gdextension-as-libriscv.html#in-core-and-done-by-us",
+    "href": "decisions/20240627-gdextension-as-libriscv.html#in-core-and-done-by-us",
+    "title": "Superceded: RISCV Binaries as Shared Libraries",
     "section": "",
-    "text": "Status: Deprecated\nDeciders: V-Sekai\nTags: V-Sekai, fixed\n\n\n\n\nThis proposal aims to define a valid configuration of OpenVR and SpatialLabs display.\n\n\n\nThe main challenge is to display Unity applications like SteamVR home and others.\n\n\n\nTo overcome the challenge, use these exact versions:\n\nSpatialLabs EC PRO_Acer_1.2.288_Win11x64\nAcer SteamVR Bridge.Installer.1.00.1001\n\n\n\n\nBy using these specific versions, we can avoid the latest update that causes the screen to be black. This ensures a seamless experience for users.\n\n\n\nThe downside of this approach is that we are losing out on the latest updates and improvements that come with them.\n\n\n\nAn alternative approach could have been to use a different product like the Looking Glass Factory, but they don’t support openxr.\n\n\n\nAnother infrequent use case could be only flat desktop.\n\n\n\nI have access to equipment and it’s not easy to get access. This means that the implementation and testing of this proposal will be done by us.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\n\nAI assistant Aria assisted with this article."
+    "text": "This proposal will be implemented by the V-Sekai development team, with potential contributions from the wider open-source community."
   },
   {
-    "objectID": "decisions/20231230-spatiallabs-openvr.html#metadata",
-    "href": "decisions/20231230-spatiallabs-openvr.html#metadata",
-    "title": "Deprecated: Valid configuration of Spatiallabs and Openxr",
+    "objectID": "decisions/20240627-gdextension-as-libriscv.html#status",
+    "href": "decisions/20240627-gdextension-as-libriscv.html#status",
+    "title": "Superceded: RISCV Binaries as Shared Libraries",
     "section": "",
-    "text": "Status: Deprecated\nDeciders: V-Sekai\nTags: V-Sekai, fixed"
+    "text": "Status: Superseded by Build a tiny RISC virtual machine which can interpret and execute GDExtensions"
   },
   {
-    "objectID": "decisions/20231230-spatiallabs-openvr.html#the-backdrop",
-    "href": "decisions/20231230-spatiallabs-openvr.html#the-backdrop",
-    "title": "Deprecated: Valid configuration of Spatiallabs and Openxr",
+    "objectID": "decisions/20240627-gdextension-as-libriscv.html#decision-makers",
+    "href": "decisions/20240627-gdextension-as-libriscv.html#decision-makers",
+    "title": "Superceded: RISCV Binaries as Shared Libraries",
     "section": "",
-    "text": "This proposal aims to define a valid configuration of OpenVR and SpatialLabs display."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20231230-spatiallabs-openvr.html#the-challenge",
-    "href": "decisions/20231230-spatiallabs-openvr.html#the-challenge",
-    "title": "Deprecated: Valid configuration of Spatiallabs and Openxr",
+    "objectID": "decisions/20240627-gdextension-as-libriscv.html#tags",
+    "href": "decisions/20240627-gdextension-as-libriscv.html#tags",
+    "title": "Superceded: RISCV Binaries as Shared Libraries",
     "section": "",
-    "text": "The main challenge is to display Unity applications like SteamVR home and others."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20231230-spatiallabs-openvr.html#the-strategy",
-    "href": "decisions/20231230-spatiallabs-openvr.html#the-strategy",
-    "title": "Deprecated: Valid configuration of Spatiallabs and Openxr",
+    "objectID": "decisions/20240627-gdextension-as-libriscv.html#further-reading",
+    "href": "decisions/20240627-gdextension-as-libriscv.html#further-reading",
+    "title": "Superceded: RISCV Binaries as Shared Libraries",
     "section": "",
-    "text": "To overcome the challenge, use these exact versions:\n\nSpatialLabs EC PRO_Acer_1.2.288_Win11x64\nAcer SteamVR Bridge.Installer.1.00.1001"
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nlibriscv VM Call Documentation - Detailed documentation on making function calls into the VM guest.\n[https://c9x.me/compile/]\n[https://github.com/Vahera/godot-orchestrator]\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20231230-spatiallabs-openvr.html#the-upside",
-    "href": "decisions/20231230-spatiallabs-openvr.html#the-upside",
-    "title": "Deprecated: Valid configuration of Spatiallabs and Openxr",
+    "objectID": "decisions/20210523-distribute-trusted-clients-with-notary.html",
+    "href": "decisions/20210523-distribute-trusted-clients-with-notary.html",
+    "title": "Proposed: Distribute trusted clients with notary",
     "section": "",
-    "text": "By using these specific versions, we can avoid the latest update that causes the screen to be black. This ensures a seamless experience for users."
+    "text": "We use itch.io distribute our software clients.\n\nSecurity concerns with trust. We do not control hosting.\nWant ability to mirror package sources.\nResearch use to distribute avatars and worlds\nWant something off the shelf\n\n\n\n\nUse the notary system so we can establish trust.\n\n\nWe distribute the notary updater and make it fetch the launcher and V-Sekai.\nWe provide a notary server.\nWe setup the #trust relationship during the install and maintenance.\n\n\n\n\nCode reviewed and trusted by large corporations (Docker Images) and in safety critial fields (Automobiles)\nOff the shelf\n\n\n\n\n\nUnknown support costs\n\n\n\n\n\nSteam provides a distribution network and marketplace.\nList the reasons for the rejection: (the Bad traits)\n\nThird party #trust\n\n\n\n\nItch.io provides a distribution network and marketplace.\nList the reasons for the rejection: (the Bad traits)\n\nThird party #trust\n\n\n\n\nNot trivial. The documentation of Notary start by the description of a possible security model and provides several attacks against it.\n\n\n\nFrom a security standpoint, we need to ensure that there is a #trust between the software we send and the client supply chain to get it.\n\n\n\n\nhttps://github.com/kolide/updater\nhttps://github.com/theupdateframework/notary\nhttps://github.com/theupdateframework/specification/blob/master/tuf-spec.md\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20231230-spatiallabs-openvr.html#the-downside",
-    "href": "decisions/20231230-spatiallabs-openvr.html#the-downside",
-    "title": "Deprecated: Valid configuration of Spatiallabs and Openxr",
+    "objectID": "decisions/20210523-distribute-trusted-clients-with-notary.html#context-and-problem-statement",
+    "href": "decisions/20210523-distribute-trusted-clients-with-notary.html#context-and-problem-statement",
+    "title": "Proposed: Distribute trusted clients with notary",
     "section": "",
-    "text": "The downside of this approach is that we are losing out on the latest updates and improvements that come with them."
+    "text": "We use itch.io distribute our software clients.\n\nSecurity concerns with trust. We do not control hosting.\nWant ability to mirror package sources.\nResearch use to distribute avatars and worlds\nWant something off the shelf"
   },
   {
-    "objectID": "decisions/20231230-spatiallabs-openvr.html#the-road-not-taken",
-    "href": "decisions/20231230-spatiallabs-openvr.html#the-road-not-taken",
-    "title": "Deprecated: Valid configuration of Spatiallabs and Openxr",
+    "objectID": "decisions/20210523-distribute-trusted-clients-with-notary.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20210523-distribute-trusted-clients-with-notary.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: Distribute trusted clients with notary",
     "section": "",
-    "text": "An alternative approach could have been to use a different product like the Looking Glass Factory, but they don’t support openxr."
+    "text": "Use the notary system so we can establish trust.\n\n\nWe distribute the notary updater and make it fetch the launcher and V-Sekai.\nWe provide a notary server.\nWe setup the #trust relationship during the install and maintenance.\n\n\n\n\nCode reviewed and trusted by large corporations (Docker Images) and in safety critial fields (Automobiles)\nOff the shelf\n\n\n\n\n\nUnknown support costs"
   },
   {
-    "objectID": "decisions/20231230-spatiallabs-openvr.html#the-infrequent-use-case",
-    "href": "decisions/20231230-spatiallabs-openvr.html#the-infrequent-use-case",
-    "title": "Deprecated: Valid configuration of Spatiallabs and Openxr",
+    "objectID": "decisions/20210523-distribute-trusted-clients-with-notary.html#option-graveyard-steam-only",
+    "href": "decisions/20210523-distribute-trusted-clients-with-notary.html#option-graveyard-steam-only",
+    "title": "Proposed: Distribute trusted clients with notary",
     "section": "",
-    "text": "Another infrequent use case could be only flat desktop."
+    "text": "Steam provides a distribution network and marketplace.\nList the reasons for the rejection: (the Bad traits)\n\nThird party #trust"
   },
   {
-    "objectID": "decisions/20231230-spatiallabs-openvr.html#in-core-and-done-by-us",
-    "href": "decisions/20231230-spatiallabs-openvr.html#in-core-and-done-by-us",
-    "title": "Deprecated: Valid configuration of Spatiallabs and Openxr",
+    "objectID": "decisions/20210523-distribute-trusted-clients-with-notary.html#option-graveyard-itch.io-only",
+    "href": "decisions/20210523-distribute-trusted-clients-with-notary.html#option-graveyard-itch.io-only",
+    "title": "Proposed: Distribute trusted clients with notary",
     "section": "",
-    "text": "I have access to equipment and it’s not easy to get access. This means that the implementation and testing of this proposal will be done by us."
+    "text": "Itch.io provides a distribution network and marketplace.\nList the reasons for the rejection: (the Bad traits)\n\nThird party #trust"
   },
   {
-    "objectID": "decisions/20231230-spatiallabs-openvr.html#further-reading",
-    "href": "decisions/20231230-spatiallabs-openvr.html#further-reading",
-    "title": "Deprecated: Valid configuration of Spatiallabs and Openxr",
+    "objectID": "decisions/20210523-distribute-trusted-clients-with-notary.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20210523-distribute-trusted-clients-with-notary.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Distribute trusted clients with notary",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\n\nAI assistant Aria assisted with this article."
+    "text": "Not trivial. The documentation of Notary start by the description of a possible security model and provides several attacks against it."
   },
   {
-    "objectID": "decisions/20241028-use-data-tables-for-godot-constraints.html",
-    "href": "decisions/20241028-use-data-tables-for-godot-constraints.html",
-    "title": "Proposal: Use Data Tables for Godot Constraints",
+    "objectID": "decisions/20210523-distribute-trusted-clients-with-notary.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20210523-distribute-trusted-clients-with-notary.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Distribute trusted clients with notary",
     "section": "",
-    "text": "In the development of VR applications using the Godot Engine, managing complex interactions and constraints can become cumbersome and error-prone when handled purely through code.\n\n\n\nCurrently, developers must manually code each constraint and interaction within the Godot Engine, which is time-consuming and increases the risk of errors. This approach lacks scalability and efficiency, particularly in large-scale VR projects like those developed by V-Sekai.\n\n\n\nThe proposal involves integrating a data table system within the Godot Engine to manage constraints. Here’s a basic example of how it might look in pseudo-code:\n\n\n\n\nScalability: Easier to manage large numbers of constraints.\nEfficiency: Reduces development time by allowing non-programmers to adjust constraints.\nError Reduction: Minimizes coding errors associated with manual constraint setup.\n\n\n\n\n\nComplexity in Setup: Initial setup of data tables and integration into the Godot project might be complex.\nPerformance Concerns: Reading from data tables at runtime could impact performance if not properly optimized.\n\n\n\n\nAn alternative could have been to develop a visual editor for constraints within Godot, but this would require significantly more development resources and may not offer the same flexibility as a data-driven approach.\n\n\n\nFor projects where constraints are minimal or highly static, this system might introduce unnecessary complexity and overhead.\n\n\n\nThis feature should be developed and maintained by the core V-Sekai team to ensure it aligns with the overall architecture and performance standards of the engine.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "From a security standpoint, we need to ensure that there is a #trust between the software we send and the client supply chain to get it."
   },
   {
-    "objectID": "decisions/20241028-use-data-tables-for-godot-constraints.html#the-context",
-    "href": "decisions/20241028-use-data-tables-for-godot-constraints.html#the-context",
-    "title": "Proposal: Use Data Tables for Godot Constraints",
+    "objectID": "decisions/20210523-distribute-trusted-clients-with-notary.html#references",
+    "href": "decisions/20210523-distribute-trusted-clients-with-notary.html#references",
+    "title": "Proposed: Distribute trusted clients with notary",
     "section": "",
-    "text": "In the development of VR applications using the Godot Engine, managing complex interactions and constraints can become cumbersome and error-prone when handled purely through code."
+    "text": "https://github.com/kolide/updater\nhttps://github.com/theupdateframework/notary\nhttps://github.com/theupdateframework/specification/blob/master/tuf-spec.md"
   },
   {
-    "objectID": "decisions/20241028-use-data-tables-for-godot-constraints.html#the-problem-statement",
-    "href": "decisions/20241028-use-data-tables-for-godot-constraints.html#the-problem-statement",
-    "title": "Proposal: Use Data Tables for Godot Constraints",
+    "objectID": "decisions/20210523-distribute-trusted-clients-with-notary.html#derivative-license",
+    "href": "decisions/20210523-distribute-trusted-clients-with-notary.html#derivative-license",
+    "title": "Proposed: Distribute trusted clients with notary",
     "section": "",
-    "text": "Currently, developers must manually code each constraint and interaction within the Godot Engine, which is time-consuming and increases the risk of errors. This approach lacks scalability and efficiency, particularly in large-scale VR projects like those developed by V-Sekai."
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20241028-use-data-tables-for-godot-constraints.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20241028-use-data-tables-for-godot-constraints.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposal: Use Data Tables for Godot Constraints",
+    "objectID": "decisions/20211005-solve-mocap-by-connecting-mediapipe-to-blender.html",
+    "href": "decisions/20211005-solve-mocap-by-connecting-mediapipe-to-blender.html",
+    "title": "Proposed: Solve Mocap By Connecting Mediapipe to Blender",
     "section": "",
-    "text": "The proposal involves integrating a data table system within the Godot Engine to manage constraints. Here’s a basic example of how it might look in pseudo-code:"
+    "text": "Want to animate a blender file with mediapipe\n\n\n\nBy writing a c++ executable on Linux, we can connect Mediapipe to Blender.\n\n\n\n\nCreate a wrapper for https://github.com/infosia/vmc2bvh/tree/master/osc\nInstall Blender addon https://github.com/maybites/blender.NodeOSC\nConvert python script to c++\nMake c++ buildable by bazel\nBuild executables on Github Actions\n\n\n\n\nhttps://github.com/CLIUtils/CLI11 for command line parsing\nhttps://github.com/infosia/vmc2bvh/blob/master/code/Vmc2Bvh.cpp for example code\nFor each process send osc to node osc (Blender).\nCreate a structure for the messages\n\n\n\n\n\nML and armature work is hard\n\n\n\nIs there a reason why this should be core and done by us?\n\n\n\nFrom Kendrick\n\nmedia_pipe_demo.zip\nhttps://github.com/V-Sekai/game-tools-V-Sekai\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20241028-use-data-tables-for-godot-constraints.html#the-benefits",
-    "href": "decisions/20241028-use-data-tables-for-godot-constraints.html#the-benefits",
-    "title": "Proposal: Use Data Tables for Godot Constraints",
+    "objectID": "decisions/20211005-solve-mocap-by-connecting-mediapipe-to-blender.html#context-and-problem-statement",
+    "href": "decisions/20211005-solve-mocap-by-connecting-mediapipe-to-blender.html#context-and-problem-statement",
+    "title": "Proposed: Solve Mocap By Connecting Mediapipe to Blender",
     "section": "",
-    "text": "Scalability: Easier to manage large numbers of constraints.\nEfficiency: Reduces development time by allowing non-programmers to adjust constraints.\nError Reduction: Minimizes coding errors associated with manual constraint setup."
+    "text": "Want to animate a blender file with mediapipe"
   },
   {
-    "objectID": "decisions/20241028-use-data-tables-for-godot-constraints.html#the-downsides",
-    "href": "decisions/20241028-use-data-tables-for-godot-constraints.html#the-downsides",
-    "title": "Proposal: Use Data Tables for Godot Constraints",
+    "objectID": "decisions/20211005-solve-mocap-by-connecting-mediapipe-to-blender.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20211005-solve-mocap-by-connecting-mediapipe-to-blender.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: Solve Mocap By Connecting Mediapipe to Blender",
     "section": "",
-    "text": "Complexity in Setup: Initial setup of data tables and integration into the Godot project might be complex.\nPerformance Concerns: Reading from data tables at runtime could impact performance if not properly optimized."
+    "text": "By writing a c++ executable on Linux, we can connect Mediapipe to Blender."
   },
   {
-    "objectID": "decisions/20241028-use-data-tables-for-godot-constraints.html#the-road-not-taken",
-    "href": "decisions/20241028-use-data-tables-for-godot-constraints.html#the-road-not-taken",
-    "title": "Proposal: Use Data Tables for Godot Constraints",
+    "objectID": "decisions/20211005-solve-mocap-by-connecting-mediapipe-to-blender.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20211005-solve-mocap-by-connecting-mediapipe-to-blender.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Solve Mocap By Connecting Mediapipe to Blender",
     "section": "",
-    "text": "An alternative could have been to develop a visual editor for constraints within Godot, but this would require significantly more development resources and may not offer the same flexibility as a data-driven approach."
+    "text": "Create a wrapper for https://github.com/infosia/vmc2bvh/tree/master/osc\nInstall Blender addon https://github.com/maybites/blender.NodeOSC\nConvert python script to c++\nMake c++ buildable by bazel\nBuild executables on Github Actions\n\n\n\n\nhttps://github.com/CLIUtils/CLI11 for command line parsing\nhttps://github.com/infosia/vmc2bvh/blob/master/code/Vmc2Bvh.cpp for example code\nFor each process send osc to node osc (Blender).\nCreate a structure for the messages"
   },
   {
-    "objectID": "decisions/20241028-use-data-tables-for-godot-constraints.html#the-infrequent-use-case",
-    "href": "decisions/20241028-use-data-tables-for-godot-constraints.html#the-infrequent-use-case",
-    "title": "Proposal: Use Data Tables for Godot Constraints",
+    "objectID": "decisions/20211005-solve-mocap-by-connecting-mediapipe-to-blender.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20211005-solve-mocap-by-connecting-mediapipe-to-blender.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Solve Mocap By Connecting Mediapipe to Blender",
     "section": "",
-    "text": "For projects where constraints are minimal or highly static, this system might introduce unnecessary complexity and overhead."
+    "text": "ML and armature work is hard"
   },
   {
-    "objectID": "decisions/20241028-use-data-tables-for-godot-constraints.html#in-core-and-done-by-us",
-    "href": "decisions/20241028-use-data-tables-for-godot-constraints.html#in-core-and-done-by-us",
-    "title": "Proposal: Use Data Tables for Godot Constraints",
+    "objectID": "decisions/20211005-solve-mocap-by-connecting-mediapipe-to-blender.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20211005-solve-mocap-by-connecting-mediapipe-to-blender.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Solve Mocap By Connecting Mediapipe to Blender",
     "section": "",
-    "text": "This feature should be developed and maintained by the core V-Sekai team to ensure it aligns with the overall architecture and performance standards of the engine."
+    "text": "Is there a reason why this should be core and done by us?"
   },
   {
-    "objectID": "decisions/20241028-use-data-tables-for-godot-constraints.html#status",
-    "href": "decisions/20241028-use-data-tables-for-godot-constraints.html#status",
-    "title": "Proposal: Use Data Tables for Godot Constraints",
+    "objectID": "decisions/20211005-solve-mocap-by-connecting-mediapipe-to-blender.html#references",
+    "href": "decisions/20211005-solve-mocap-by-connecting-mediapipe-to-blender.html#references",
+    "title": "Proposed: Solve Mocap By Connecting Mediapipe to Blender",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "From Kendrick\n\nmedia_pipe_demo.zip\nhttps://github.com/V-Sekai/game-tools-V-Sekai"
   },
   {
-    "objectID": "decisions/20241028-use-data-tables-for-godot-constraints.html#decision-makers",
-    "href": "decisions/20241028-use-data-tables-for-godot-constraints.html#decision-makers",
-    "title": "Proposal: Use Data Tables for Godot Constraints",
+    "objectID": "decisions/20211005-solve-mocap-by-connecting-mediapipe-to-blender.html#derivative-license",
+    "href": "decisions/20211005-solve-mocap-by-connecting-mediapipe-to-blender.html#derivative-license",
+    "title": "Proposed: Solve Mocap By Connecting Mediapipe to Blender",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20241028-use-data-tables-for-godot-constraints.html#tags",
-    "href": "decisions/20241028-use-data-tables-for-godot-constraints.html#tags",
-    "title": "Proposal: Use Data Tables for Godot Constraints",
+    "objectID": "decisions/20240330-k8s-harvester-hci.html",
+    "href": "decisions/20240330-k8s-harvester-hci.html",
+    "title": "Accepted: k8s on harvester hci",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Kubernetes is a standard for managing containerized applications. Harvester, an open-source HCI software built on Kubernetes, manages virtual machines, storage, and network resources. Installing Rancher on Harvester enhances Kubernetes management.\n\n\n\nThe challenge is installing Rancher directly on a Harvester VM using the rancher-vcluster addon, which allows Rancher Manager to run as a workload on the Harvester cluster.\n\n\n\nThe solution involves:\n\nInstalling the rancher-vcluster Addon The rancher-vcluster addon is not packaged with Harvester, but you can find it in the experimental-addons repository.\n\nAssuming you are using the Harvester kubeconfig, you can run the following command to apply the YAML file:\nssh rancher@xxx.xxx.xxx.xx\nsudo kubectl apply -f https://raw.githubusercontent.com/harvester/experimental-addons/main/rancher-vcluster/rancher-vcluster.yaml\n# Users can define the rancher url and password via addon interface.\n# hostname: \"rancher.172.19.108.3.sslip.io\"\n# password: \"hunter2\"\n# Open https://rancher.192.168.0.65.sslip.io/dashboard/auth/setup\nThis command will fetch the rancher-vcluster.yaml file from the experimental-addons repository and apply it to your Kubernetes cluster.\n\nConfiguring the Addon: Configure the addon through the Harvester UI under Advanced &gt; Addons. Edit the config for the rancher-vcluster addon, specify a hostname that points to the Harvester VIP and set a bootstrap password for Rancher.\nAccessing Rancher: Access Rancher using the DNS hostname provided during configuration after installation.\n\nThis approach integrates Rancher into Harvester, leveraging Harvester’s infrastructure to manage both VMs and containers centrally.\n\n\n\nEdit the namespace to remove its finalizers:\nFirst, you’ll need to edit the namespace to remove any finalizers that are preventing it from being deleted.\nkubectl get namespace rancher-vcluster -o json &gt; tmp.json\nOpen the tmp.json file and remove the finalizers field:\nLook for the spec section and remove the finalizers array. It should look something like this:\n\"spec\": {\n  \"finalizers\": [\n    \"kubernetes\"\n  ]\n}\nAfter removal, it should look like this:\n\"spec\": {}\nApply the modified JSON back to the cluster:\nkubectl replace --raw \"/api/v1/namespaces/rancher-vcluster/finalize\" -f ./tmp.json\nVerify the namespace has been deleted:\nkubectl get namespaces\n\nIf the namespace still does not delete, you may need to manually clean up resources within the namespace before retrying the above steps.\n\n\nForcefully removing a namespace can lead to orphaned resources. Ensure that you understand the implications of this action and have backups if necessary.\n\n\n\n\n\nThis setup enables creation and management of Kubernetes clusters through Harvester’s integration with Rancher and deployment of a Kubernetes cluster based on specific requirements (K3s).\n\n\n\nThe process can be complex and requires attention to detail. Misconfiguration could lead to issues with the installation or operation of Harvester and Rancher.\n\n\n\nAn alternative could be a network-based installation method, not feasible in an air-gapped environment.\n\n\n\nThis setup is useful in environments where internet access is restricted or unavailable, necessitating the use of the rancher-vcluster addon.\n\n\n\nThe user performs the entire process of installing and configuring the rancher-vcluster addon with guidance from this proposal.\n\n\n\nStatus: Accepted\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nRancher Vcluster\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20241028-use-data-tables-for-godot-constraints.html#further-reading",
-    "href": "decisions/20241028-use-data-tables-for-godot-constraints.html#further-reading",
-    "title": "Proposal: Use Data Tables for Godot Constraints",
+    "objectID": "decisions/20240330-k8s-harvester-hci.html#the-context",
+    "href": "decisions/20240330-k8s-harvester-hci.html#the-context",
+    "title": "Accepted: k8s on harvester hci",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "Kubernetes is a standard for managing containerized applications. Harvester, an open-source HCI software built on Kubernetes, manages virtual machines, storage, and network resources. Installing Rancher on Harvester enhances Kubernetes management."
   },
   {
-    "objectID": "decisions/20240613-training-dataset-creation-with-csg.html",
-    "href": "decisions/20240613-training-dataset-creation-with-csg.html",
-    "title": "Proposed: Dataset Creation with CSG",
+    "objectID": "decisions/20240330-k8s-harvester-hci.html#the-problem-statement",
+    "href": "decisions/20240330-k8s-harvester-hci.html#the-problem-statement",
+    "title": "Accepted: k8s on harvester hci",
     "section": "",
-    "text": "We’re working on a project that involves creating 3D models using Constructive Solid Geometry (CSG). We need to create a dataset of these models, but we can’t afford to pay for it and we don’t want to build our own platform.\n\n\n\nThe challenge is how to gather a large and diverse set of 3D models represented as CSG trees without financial expenditure and without building our own platform.\n\n\n\n\nEngage Open-Source Communities: Connect with people who are into 3D modeling and CSG. They might be interested in contributing to our project.\nCollaborate with Educational Institutions: Partner with colleges that offer courses in 3D modeling. Students could contribute to our project as part of their coursework or for extra credit.\nProvide Clear Guidelines: Write up detailed instructions on how to create and submit the models. This should include technical specifications, style guides, and examples.\nImplement a Review Process: Each model should be reviewed to ensure it meets our quality standards and follows our style guide.\nUse Existing Platforms for Submission: Use platforms like GitHub or Google Drive for contributors to submit their models.\n\n\n\n\n\nWe can gather a large and diverse dataset without having to pay.\nChecking the models ourselves ensures they’ll be of good quality and consistent.\nUsing an existing platform saves us time and resources.\n\n\n\n\n\nManaging a project with volunteers can be complex and time-consuming.\nEnsuring consistent quality and style across all submissions may be challenging.\nDepending on external platforms for submission might limit some functionalities that could be possible with a custom-built platform.\n\n\n\n\nWe could consider using existing open-source 3D model datasets, but these might not meet our specific needs in terms of quality, style, and representation as CSG trees.\n\n\n\nThis approach might not be suitable if we need very specific models in our dataset that require specialized knowledge or skills to create.\n\n\n\nThe management of the project, the provision of clear guidelines, and the review of the submissions will be done by us, using our resources and expertise.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\niFire\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nConstructive Solid Geometry (CSG) - More about CSG.\nOpen Source - More about open source.\nV-Sekai · GitHub - The GitHub account for V-Sekai.\nV-Sekai/v-sekai-game - The GitHub page for the V-Sekai project.\n\nAI assistant Aria assisted with this proposal."
+    "text": "The challenge is installing Rancher directly on a Harvester VM using the rancher-vcluster addon, which allows Rancher Manager to run as a workload on the Harvester cluster."
   },
   {
-    "objectID": "decisions/20240613-training-dataset-creation-with-csg.html#the-context",
-    "href": "decisions/20240613-training-dataset-creation-with-csg.html#the-context",
-    "title": "Proposed: Dataset Creation with CSG",
+    "objectID": "decisions/20240330-k8s-harvester-hci.html#solution",
+    "href": "decisions/20240330-k8s-harvester-hci.html#solution",
+    "title": "Accepted: k8s on harvester hci",
     "section": "",
-    "text": "We’re working on a project that involves creating 3D models using Constructive Solid Geometry (CSG). We need to create a dataset of these models, but we can’t afford to pay for it and we don’t want to build our own platform."
+    "text": "The solution involves:\n\nInstalling the rancher-vcluster Addon The rancher-vcluster addon is not packaged with Harvester, but you can find it in the experimental-addons repository.\n\nAssuming you are using the Harvester kubeconfig, you can run the following command to apply the YAML file:\nssh rancher@xxx.xxx.xxx.xx\nsudo kubectl apply -f https://raw.githubusercontent.com/harvester/experimental-addons/main/rancher-vcluster/rancher-vcluster.yaml\n# Users can define the rancher url and password via addon interface.\n# hostname: \"rancher.172.19.108.3.sslip.io\"\n# password: \"hunter2\"\n# Open https://rancher.192.168.0.65.sslip.io/dashboard/auth/setup\nThis command will fetch the rancher-vcluster.yaml file from the experimental-addons repository and apply it to your Kubernetes cluster.\n\nConfiguring the Addon: Configure the addon through the Harvester UI under Advanced &gt; Addons. Edit the config for the rancher-vcluster addon, specify a hostname that points to the Harvester VIP and set a bootstrap password for Rancher.\nAccessing Rancher: Access Rancher using the DNS hostname provided during configuration after installation.\n\nThis approach integrates Rancher into Harvester, leveraging Harvester’s infrastructure to manage both VMs and containers centrally.\n\n\n\nEdit the namespace to remove its finalizers:\nFirst, you’ll need to edit the namespace to remove any finalizers that are preventing it from being deleted.\nkubectl get namespace rancher-vcluster -o json &gt; tmp.json\nOpen the tmp.json file and remove the finalizers field:\nLook for the spec section and remove the finalizers array. It should look something like this:\n\"spec\": {\n  \"finalizers\": [\n    \"kubernetes\"\n  ]\n}\nAfter removal, it should look like this:\n\"spec\": {}\nApply the modified JSON back to the cluster:\nkubectl replace --raw \"/api/v1/namespaces/rancher-vcluster/finalize\" -f ./tmp.json\nVerify the namespace has been deleted:\nkubectl get namespaces\n\nIf the namespace still does not delete, you may need to manually clean up resources within the namespace before retrying the above steps.\n\n\nForcefully removing a namespace can lead to orphaned resources. Ensure that you understand the implications of this action and have backups if necessary."
   },
   {
-    "objectID": "decisions/20240613-training-dataset-creation-with-csg.html#the-problem-statement",
-    "href": "decisions/20240613-training-dataset-creation-with-csg.html#the-problem-statement",
-    "title": "Proposed: Dataset Creation with CSG",
+    "objectID": "decisions/20240330-k8s-harvester-hci.html#the-benefits",
+    "href": "decisions/20240330-k8s-harvester-hci.html#the-benefits",
+    "title": "Accepted: k8s on harvester hci",
     "section": "",
-    "text": "The challenge is how to gather a large and diverse set of 3D models represented as CSG trees without financial expenditure and without building our own platform."
+    "text": "This setup enables creation and management of Kubernetes clusters through Harvester’s integration with Rancher and deployment of a Kubernetes cluster based on specific requirements (K3s)."
   },
   {
-    "objectID": "decisions/20240613-training-dataset-creation-with-csg.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240613-training-dataset-creation-with-csg.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Dataset Creation with CSG",
+    "objectID": "decisions/20240330-k8s-harvester-hci.html#the-downsides",
+    "href": "decisions/20240330-k8s-harvester-hci.html#the-downsides",
+    "title": "Accepted: k8s on harvester hci",
     "section": "",
-    "text": "Engage Open-Source Communities: Connect with people who are into 3D modeling and CSG. They might be interested in contributing to our project.\nCollaborate with Educational Institutions: Partner with colleges that offer courses in 3D modeling. Students could contribute to our project as part of their coursework or for extra credit.\nProvide Clear Guidelines: Write up detailed instructions on how to create and submit the models. This should include technical specifications, style guides, and examples.\nImplement a Review Process: Each model should be reviewed to ensure it meets our quality standards and follows our style guide.\nUse Existing Platforms for Submission: Use platforms like GitHub or Google Drive for contributors to submit their models."
+    "text": "The process can be complex and requires attention to detail. Misconfiguration could lead to issues with the installation or operation of Harvester and Rancher."
   },
   {
-    "objectID": "decisions/20240613-training-dataset-creation-with-csg.html#the-benefits",
-    "href": "decisions/20240613-training-dataset-creation-with-csg.html#the-benefits",
-    "title": "Proposed: Dataset Creation with CSG",
+    "objectID": "decisions/20240330-k8s-harvester-hci.html#the-road-not-taken",
+    "href": "decisions/20240330-k8s-harvester-hci.html#the-road-not-taken",
+    "title": "Accepted: k8s on harvester hci",
     "section": "",
-    "text": "We can gather a large and diverse dataset without having to pay.\nChecking the models ourselves ensures they’ll be of good quality and consistent.\nUsing an existing platform saves us time and resources."
+    "text": "An alternative could be a network-based installation method, not feasible in an air-gapped environment."
   },
   {
-    "objectID": "decisions/20240613-training-dataset-creation-with-csg.html#the-downsides",
-    "href": "decisions/20240613-training-dataset-creation-with-csg.html#the-downsides",
-    "title": "Proposed: Dataset Creation with CSG",
+    "objectID": "decisions/20240330-k8s-harvester-hci.html#the-infrequent-use-case",
+    "href": "decisions/20240330-k8s-harvester-hci.html#the-infrequent-use-case",
+    "title": "Accepted: k8s on harvester hci",
     "section": "",
-    "text": "Managing a project with volunteers can be complex and time-consuming.\nEnsuring consistent quality and style across all submissions may be challenging.\nDepending on external platforms for submission might limit some functionalities that could be possible with a custom-built platform."
+    "text": "This setup is useful in environments where internet access is restricted or unavailable, necessitating the use of the rancher-vcluster addon."
   },
   {
-    "objectID": "decisions/20240613-training-dataset-creation-with-csg.html#the-road-not-taken",
-    "href": "decisions/20240613-training-dataset-creation-with-csg.html#the-road-not-taken",
-    "title": "Proposed: Dataset Creation with CSG",
+    "objectID": "decisions/20240330-k8s-harvester-hci.html#in-core-and-done-by-us",
+    "href": "decisions/20240330-k8s-harvester-hci.html#in-core-and-done-by-us",
+    "title": "Accepted: k8s on harvester hci",
     "section": "",
-    "text": "We could consider using existing open-source 3D model datasets, but these might not meet our specific needs in terms of quality, style, and representation as CSG trees."
+    "text": "The user performs the entire process of installing and configuring the rancher-vcluster addon with guidance from this proposal."
   },
   {
-    "objectID": "decisions/20240613-training-dataset-creation-with-csg.html#the-infrequent-use-case",
-    "href": "decisions/20240613-training-dataset-creation-with-csg.html#the-infrequent-use-case",
-    "title": "Proposed: Dataset Creation with CSG",
+    "objectID": "decisions/20240330-k8s-harvester-hci.html#status",
+    "href": "decisions/20240330-k8s-harvester-hci.html#status",
+    "title": "Accepted: k8s on harvester hci",
     "section": "",
-    "text": "This approach might not be suitable if we need very specific models in our dataset that require specialized knowledge or skills to create."
+    "text": "Status: Accepted"
   },
   {
-    "objectID": "decisions/20240613-training-dataset-creation-with-csg.html#in-core-and-done-by-us",
-    "href": "decisions/20240613-training-dataset-creation-with-csg.html#in-core-and-done-by-us",
-    "title": "Proposed: Dataset Creation with CSG",
+    "objectID": "decisions/20240330-k8s-harvester-hci.html#decision-makers",
+    "href": "decisions/20240330-k8s-harvester-hci.html#decision-makers",
+    "title": "Accepted: k8s on harvester hci",
     "section": "",
-    "text": "The management of the project, the provision of clear guidelines, and the review of the submissions will be done by us, using our resources and expertise."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20240613-training-dataset-creation-with-csg.html#status",
-    "href": "decisions/20240613-training-dataset-creation-with-csg.html#status",
-    "title": "Proposed: Dataset Creation with CSG",
+    "objectID": "decisions/20240330-k8s-harvester-hci.html#tags",
+    "href": "decisions/20240330-k8s-harvester-hci.html#tags",
+    "title": "Accepted: k8s on harvester hci",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20240613-training-dataset-creation-with-csg.html#decision-makers",
-    "href": "decisions/20240613-training-dataset-creation-with-csg.html#decision-makers",
-    "title": "Proposed: Dataset Creation with CSG",
+    "objectID": "decisions/20240330-k8s-harvester-hci.html#further-reading",
+    "href": "decisions/20240330-k8s-harvester-hci.html#further-reading",
+    "title": "Accepted: k8s on harvester hci",
     "section": "",
-    "text": "V-Sekai development team\niFire"
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nRancher Vcluster\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240613-training-dataset-creation-with-csg.html#tags",
-    "href": "decisions/20240613-training-dataset-creation-with-csg.html#tags",
-    "title": "Proposed: Dataset Creation with CSG",
+    "objectID": "decisions/20220515-profile-using-perf.html",
+    "href": "decisions/20220515-profile-using-perf.html",
+    "title": "Proposed: Profile using perf",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Proposed: Profile using perf\n\nDescribe the status of the issue.\n\nproposed\ndraft\nrejected\naccepted\ndeprecated\nsuperseded by\n\n\n\nList the deciders of the issue.\nV-Sekai,fire,\n\n\nDescribe the tags of the issue.\nV-Sekai,\n\n\nContext and Problem Statement\nWant a workflow to profile Godot Groups.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nUse perf and hotspot.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nsudo apt-get install linux-tools-common linux-tools-generic linux-tools-`uname -r`\nperf record -o perf.data --call-graph dwarf --aio --sample-cpu ./godot/bin/godot.linuxbsd.opt.tools.64.llvm --path groups hotspot perf.data\n\n\n\nimage\n\n\n\n\nPositive Consequences\nCan better find hotspots.\n\n\nNegative Consequences\nCurrently Linux only.\n\n\nOption graveyard\n\nSuperluminal is Windows only.\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot Godot Engine code.\n\n\nIs there a reason why this should be core and done by us?\nWe need to be aware of performance.\n\n\nReferences\n\nV-Sekai\n\n\n\nLicense of the contribution\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240613-training-dataset-creation-with-csg.html#further-reading",
-    "href": "decisions/20240613-training-dataset-creation-with-csg.html#further-reading",
-    "title": "Proposed: Dataset Creation with CSG",
+    "objectID": "decisions/20230803-publish-vrm-to-assetlibrary.html",
+    "href": "decisions/20230803-publish-vrm-to-assetlibrary.html",
+    "title": "Accepted: Completing VRM 1.0 Support and Publishing to Godot Engine Asset Library",
     "section": "",
-    "text": "Constructive Solid Geometry (CSG) - More about CSG.\nOpen Source - More about open source.\nV-Sekai · GitHub - The GitHub account for V-Sekai.\nV-Sekai/v-sekai-game - The GitHub page for the V-Sekai project.\n\nAI assistant Aria assisted with this proposal."
+    "text": "Status: Accepted\nDeciders: V-Sekai, lyuma, fire\nTags: VRM, Avatars, VRM 1.0, Export, Godot Engine\n\n\n\n\nWe currently support an older revision of the VRM standard for avatars. However, VRM 1.0 is a new revision that we need to implement. A key feature of this new revision is the ability to export VRM 1.0 files. Additionally, we also need to publish our implementation to the Godot Engine asset library.\n\n\n\n\n\n\nAnalyze the current implementation of the VRM standard in our system.\nUnderstand the changes and enhancements introduced in VRM 1.0.\nPlan the implementation of VRM 1.0 support, including the export feature.\nImplement the planned features and changes.\nTest the newly implemented VRM 1.0 support in different scenarios.\nPrepare the implementation for publishing to the Godot Engine asset library.\nPublish the implementation to the Godot Engine asset library.\n\n\n\n\n\nThe implementation details will be decided upon acceptance of this proposal.\n\n\n\n\nEnhanced avatar functionality with VRM 1.0 support.\nAbility to export VRM 1.0 files, increasing compatibility with other systems.\nStaying up-to-date with the latest standards in the industry.\nIncreased visibility and usage through publishing to the Godot Engine asset library.\n\n\n\n\n\nRequires understanding of the new VRM 1.0 standard.\nPotential increase in development time due to the complexity of implementing a new standard and preparing it for publishing.\nNeed to maintain the published asset in the Godot Engine asset library.\n\n\n\n\nThis section will be filled as we explore different options and discard those that are not feasible or effective.\n\n\n\nGiven the complexity of implementing a new standard like VRM 1.0 and publishing it to the Godot Engine asset library, it cannot be simply worked around with a few lines of script.\n\n\n\nImplementing VRM 1.0 support and publishing it to the Godot Engine asset library is crucial for staying competitive and relevant in the industry. It also aligns with our goal of providing the best possible avatar functionalities to our users.\n\n\n\n\nVRM 1.0 Specification"
   },
   {
-    "objectID": "decisions/20240117-pivot-painting.html",
-    "href": "decisions/20240117-pivot-painting.html",
-    "title": "Proposed: Provide Pivot Painting Resources",
+    "objectID": "decisions/20230803-publish-vrm-to-assetlibrary.html#metadata",
+    "href": "decisions/20230803-publish-vrm-to-assetlibrary.html#metadata",
+    "title": "Accepted: Completing VRM 1.0 Support and Publishing to Godot Engine Asset Library",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai, Silent, fire\nTags: V-Sekai\n\n\n\n\nThe V-Sekai community has identified the need for tools that assist with pivot painting, a technique to enhance animations in game development.\n\n\n\nSilent inquired about available pivot painting tools compatible with our workflow.\n\n\n\nOur strategy involves curating a list of pivot painting resources, documenting best practices, and providing educational content to facilitate their use.\n\n\n\nThese resources will allow for more complex animations and efficiency gains in our creative process.\n\n\n\nAdoption of new tools comes with a learning curve that might slow down initial productivity.\n\n\n\nWe need to assess whether in-house tool development justifies the required investment based on our pipeline needs.\n\n\n\n\nV-Sekai · GitHub\nV-Sekai/v-sekai-game\nSideFX Tutorial on Pivot Painter\nBlender Pivot Painter\nNot Unreal Tools: Vertex Animation Tools\n\nAssistance from AI assistant Aria acknowledged."
+    "text": "Status: Accepted\nDeciders: V-Sekai, lyuma, fire\nTags: VRM, Avatars, VRM 1.0, Export, Godot Engine"
   },
   {
-    "objectID": "decisions/20240117-pivot-painting.html#metadata",
-    "href": "decisions/20240117-pivot-painting.html#metadata",
-    "title": "Proposed: Provide Pivot Painting Resources",
+    "objectID": "decisions/20230803-publish-vrm-to-assetlibrary.html#context-and-problem-statement",
+    "href": "decisions/20230803-publish-vrm-to-assetlibrary.html#context-and-problem-statement",
+    "title": "Accepted: Completing VRM 1.0 Support and Publishing to Godot Engine Asset Library",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai, Silent, fire\nTags: V-Sekai"
+    "text": "We currently support an older revision of the VRM standard for avatars. However, VRM 1.0 is a new revision that we need to implement. A key feature of this new revision is the ability to export VRM 1.0 files. Additionally, we also need to publish our implementation to the Godot Engine asset library."
   },
   {
-    "objectID": "decisions/20240117-pivot-painting.html#the-backdrop",
-    "href": "decisions/20240117-pivot-painting.html#the-backdrop",
-    "title": "Proposed: Provide Pivot Painting Resources",
+    "objectID": "decisions/20230803-publish-vrm-to-assetlibrary.html#proposed-solution",
+    "href": "decisions/20230803-publish-vrm-to-assetlibrary.html#proposed-solution",
+    "title": "Accepted: Completing VRM 1.0 Support and Publishing to Godot Engine Asset Library",
     "section": "",
-    "text": "The V-Sekai community has identified the need for tools that assist with pivot painting, a technique to enhance animations in game development."
+    "text": "Analyze the current implementation of the VRM standard in our system.\nUnderstand the changes and enhancements introduced in VRM 1.0.\nPlan the implementation of VRM 1.0 support, including the export feature.\nImplement the planned features and changes.\nTest the newly implemented VRM 1.0 support in different scenarios.\nPrepare the implementation for publishing to the Godot Engine asset library.\nPublish the implementation to the Godot Engine asset library."
   },
   {
-    "objectID": "decisions/20240117-pivot-painting.html#the-challenge",
-    "href": "decisions/20240117-pivot-painting.html#the-challenge",
-    "title": "Proposed: Provide Pivot Painting Resources",
+    "objectID": "decisions/20230803-publish-vrm-to-assetlibrary.html#implementation",
+    "href": "decisions/20230803-publish-vrm-to-assetlibrary.html#implementation",
+    "title": "Accepted: Completing VRM 1.0 Support and Publishing to Godot Engine Asset Library",
     "section": "",
-    "text": "Silent inquired about available pivot painting tools compatible with our workflow."
+    "text": "The implementation details will be decided upon acceptance of this proposal."
   },
   {
-    "objectID": "decisions/20240117-pivot-painting.html#the-strategy",
-    "href": "decisions/20240117-pivot-painting.html#the-strategy",
-    "title": "Proposed: Provide Pivot Painting Resources",
+    "objectID": "decisions/20230803-publish-vrm-to-assetlibrary.html#positive-consequences",
+    "href": "decisions/20230803-publish-vrm-to-assetlibrary.html#positive-consequences",
+    "title": "Accepted: Completing VRM 1.0 Support and Publishing to Godot Engine Asset Library",
     "section": "",
-    "text": "Our strategy involves curating a list of pivot painting resources, documenting best practices, and providing educational content to facilitate their use."
+    "text": "Enhanced avatar functionality with VRM 1.0 support.\nAbility to export VRM 1.0 files, increasing compatibility with other systems.\nStaying up-to-date with the latest standards in the industry.\nIncreased visibility and usage through publishing to the Godot Engine asset library."
   },
   {
-    "objectID": "decisions/20240117-pivot-painting.html#the-upside",
-    "href": "decisions/20240117-pivot-painting.html#the-upside",
-    "title": "Proposed: Provide Pivot Painting Resources",
+    "objectID": "decisions/20230803-publish-vrm-to-assetlibrary.html#negative-consequences",
+    "href": "decisions/20230803-publish-vrm-to-assetlibrary.html#negative-consequences",
+    "title": "Accepted: Completing VRM 1.0 Support and Publishing to Godot Engine Asset Library",
     "section": "",
-    "text": "These resources will allow for more complex animations and efficiency gains in our creative process."
+    "text": "Requires understanding of the new VRM 1.0 standard.\nPotential increase in development time due to the complexity of implementing a new standard and preparing it for publishing.\nNeed to maintain the published asset in the Godot Engine asset library."
   },
   {
-    "objectID": "decisions/20240117-pivot-painting.html#the-downside",
-    "href": "decisions/20240117-pivot-painting.html#the-downside",
-    "title": "Proposed: Provide Pivot Painting Resources",
+    "objectID": "decisions/20230803-publish-vrm-to-assetlibrary.html#option-graveyard",
+    "href": "decisions/20230803-publish-vrm-to-assetlibrary.html#option-graveyard",
+    "title": "Accepted: Completing VRM 1.0 Support and Publishing to Godot Engine Asset Library",
     "section": "",
-    "text": "Adoption of new tools comes with a learning curve that might slow down initial productivity."
+    "text": "This section will be filled as we explore different options and discard those that are not feasible or effective."
   },
   {
-    "objectID": "decisions/20240117-pivot-painting.html#in-core-and-done-by-us",
-    "href": "decisions/20240117-pivot-painting.html#in-core-and-done-by-us",
-    "title": "Proposed: Provide Pivot Painting Resources",
+    "objectID": "decisions/20230803-publish-vrm-to-assetlibrary.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230803-publish-vrm-to-assetlibrary.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Accepted: Completing VRM 1.0 Support and Publishing to Godot Engine Asset Library",
     "section": "",
-    "text": "We need to assess whether in-house tool development justifies the required investment based on our pipeline needs."
+    "text": "Given the complexity of implementing a new standard like VRM 1.0 and publishing it to the Godot Engine asset library, it cannot be simply worked around with a few lines of script."
   },
   {
-    "objectID": "decisions/20240117-pivot-painting.html#further-reading",
-    "href": "decisions/20240117-pivot-painting.html#further-reading",
-    "title": "Proposed: Provide Pivot Painting Resources",
+    "objectID": "decisions/20230803-publish-vrm-to-assetlibrary.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230803-publish-vrm-to-assetlibrary.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Accepted: Completing VRM 1.0 Support and Publishing to Godot Engine Asset Library",
     "section": "",
-    "text": "V-Sekai · GitHub\nV-Sekai/v-sekai-game\nSideFX Tutorial on Pivot Painter\nBlender Pivot Painter\nNot Unreal Tools: Vertex Animation Tools\n\nAssistance from AI assistant Aria acknowledged."
+    "text": "Implementing VRM 1.0 support and publishing it to the Godot Engine asset library is crucial for staying competitive and relevant in the industry. It also aligns with our goal of providing the best possible avatar functionalities to our users."
   },
   {
-    "objectID": "decisions/20231127-performance-test.html",
-    "href": "decisions/20231127-performance-test.html",
-    "title": "Accepted: Benchmarking Network Performance for Scalable Multiplayer in Godot",
+    "objectID": "decisions/20230803-publish-vrm-to-assetlibrary.html#references",
+    "href": "decisions/20230803-publish-vrm-to-assetlibrary.html#references",
+    "title": "Accepted: Completing VRM 1.0 Support and Publishing to Godot Engine Asset Library",
     "section": "",
-    "text": "Status: Proposed \nDeciders: V-Sekai Team, Bioblaze Payne, fire\nTags: Networking, Performance, Godot Engine, V-Sekai, Test\n\n\n\n\nIn the pursuit of optimizing network performance for the V-Sekai project, we’re at a point where we need to evaluate different networking strategies provided by the Godot Engine.\n\n\n\nDesign a comprehensive series of tests to measure and compare the performance of the three different networked multiplayer strategies within the Godot Engine:\n\nThe many servers approach: A decentralized model where numerous smaller servers handle subsets of users.\nThe many worlds approach: A single server hosts multiple distinct world instances.\nThe one world with threaded process group nodes: A monolithic single world that leverages threading to manage users and activities.\n\n\n\n\nThe testing was suggested by Bioblaze Payne, who has outlined a sequential approach:\n\nPhase 1: Basic Connection Test\n\nConnect a user, send a message, await 1000 messages in return, disconnect, then reconnect.\n\nPhase 2: Large Scale Stress Test\n\nSimultaneously connect 4000 users, with each sending a message upon connection every 500ms. Ensure all messages are replicated to all connected clients.\n\n\nDuring these tests, we’ll monitor:\n\nLoad times for initial connections and reconnections.\nThroughput and latency of message delivery.\nServer resource usage (CPU, RAM, Network I/O).\nAny errors or dropped connections that occur.\n\nAll relevant events should be timestamped and logged to a centralized logging system for analysis.\n\n\n\nBy conducting this research, we aim to:\n\nIdentify the most scalable and efficient networking strategy for the V-Sekai project.\nGather empirical data to inform future development decisions.\nContribute findings back to the wider Godot community to aid in similar multiplayer projects.\n\n\n\n\nPotential risks and drawbacks include:\n\nTime and resources required for test setup and execution.\nInterpretation of results may vary, leading to indecision.\nPossible discovery of fundamental issues that could delay project timelines.\n\n\n\n\nThis section will detail alternative methods and practices considered but ultimately not chosen, with justifications for their exclusion.\n\n\n\nWe will also explore less common user scenarios that may have unique performance characteristics under each networking strategy.\n\n\n\nDiscussion on whether the outcomes of this initiative should be integrated into the core V-Sekai codebase or maintained as separate modules.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis design document was completed with assistance from AI developer Aria."
+    "text": "VRM 1.0 Specification"
   },
   {
-    "objectID": "decisions/20231127-performance-test.html#metadata",
-    "href": "decisions/20231127-performance-test.html#metadata",
-    "title": "Accepted: Benchmarking Network Performance for Scalable Multiplayer in Godot",
+    "objectID": "decisions/20230125-create-an-in-game-tablet-interface-we-can-activate.html",
+    "href": "decisions/20230125-create-an-in-game-tablet-interface-we-can-activate.html",
+    "title": "Proposed: Create an in-game tablet interface we can activate",
     "section": "",
-    "text": "Status: Proposed \nDeciders: V-Sekai Team, Bioblaze Payne, fire\nTags: Networking, Performance, Godot Engine, V-Sekai, Test"
+    "text": "Proposed: Create an in-game tablet interface we can activate\n\nMetadata\n\nStatus: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nContext and Problem Statement\nWe want to activate things in vr\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nShow a menu on each hand and have it be possible to activate grid cell options.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\n\nTrigger presents a menu\nShort press\nLong press\n\n\n\nPositive Consequences\nWe are able to use V-Sekai easier.\n\n\nNegative Consequences\nWe cannot get other features to trigger things.\n\n\nOption graveyard\n\nOption: The status quo to go out of the game to trigger menus. \nRejection Reason: This solves nothing. \n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nKnowing what to do is hard.\n\n\nIs there a reason why this should be core and done by us?\nUsability is a core feature.\n\n\nReferences\n\nV-Sekai"
   },
   {
-    "objectID": "decisions/20231127-performance-test.html#the-backdrop",
-    "href": "decisions/20231127-performance-test.html#the-backdrop",
-    "title": "Accepted: Benchmarking Network Performance for Scalable Multiplayer in Godot",
+    "objectID": "decisions/20240423-building-metaverse-with-glue-mechanic.html",
+    "href": "decisions/20240423-building-metaverse-with-glue-mechanic.html",
+    "title": "Accepted: Building a Metaverse with Glue Mechanic in V-Sekai",
     "section": "",
-    "text": "In the pursuit of optimizing network performance for the V-Sekai project, we’re at a point where we need to evaluate different networking strategies provided by the Godot Engine."
+    "text": "V-Sekai is an open-source project that brings social VR/VRSNS/metaverse components to the Godot Engine. The current focus of the project is on avatar movement and interaction within a confined space.\n\n\n\nThe current model of V-Sekai, while functional, seems limited in its scope. It primarily focuses on avatars moving in a room, which restricts the potential for expansive world-building and exploration.\n\n\n\nThe proposed solution is to introduce a “glue mechanic” into the system. This mechanic would allow users to build their own vehicles and structures by gluing different elements together. This could potentially open up the possibility for creating entire universes within the metaverse.\nThis idea was inspired by a game called “Crazy Contraptions” developed by Mantafloof during the Ludum Dare 55 game jam. The game was created in just 48 hours and successfully implemented the glue mechanic concept.\nUsers can combine different elements (represented here as ‘blocks’ and ‘wheels’) to create new structures or vehicles.\n\n\n\n\nEncourages creativity and innovation among users.\nOpens up possibilities for expansive world-building and exploration.\nProvides a reason to work on LODs and memory management for loading worlds.\n\n\n\n\n\nMay require significant changes to the existing codebase.\nThis could potentially increase the complexity of the system.\n\n\n\n\nAn alternative approach could be to continue focusing on avatar movement and interaction within a confined space. However, this may limit the potential for expansive world-building and exploration.\n\n\n\nIn cases where users prefer a more confined and controlled environment, the glue mechanic may not be as appealing. However, it could still provide an interesting option for those looking to experiment with world-building.\n\n\n\nThe implementation of the glue mechanic would be done by the V-Sekai development team.\n\n\n\nStatus: Accepted\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20231127-performance-test.html#the-challenge",
-    "href": "decisions/20231127-performance-test.html#the-challenge",
-    "title": "Accepted: Benchmarking Network Performance for Scalable Multiplayer in Godot",
+    "objectID": "decisions/20240423-building-metaverse-with-glue-mechanic.html#the-context",
+    "href": "decisions/20240423-building-metaverse-with-glue-mechanic.html#the-context",
+    "title": "Accepted: Building a Metaverse with Glue Mechanic in V-Sekai",
     "section": "",
-    "text": "Design a comprehensive series of tests to measure and compare the performance of the three different networked multiplayer strategies within the Godot Engine:\n\nThe many servers approach: A decentralized model where numerous smaller servers handle subsets of users.\nThe many worlds approach: A single server hosts multiple distinct world instances.\nThe one world with threaded process group nodes: A monolithic single world that leverages threading to manage users and activities."
+    "text": "V-Sekai is an open-source project that brings social VR/VRSNS/metaverse components to the Godot Engine. The current focus of the project is on avatar movement and interaction within a confined space."
   },
   {
-    "objectID": "decisions/20231127-performance-test.html#the-strategy",
-    "href": "decisions/20231127-performance-test.html#the-strategy",
-    "title": "Accepted: Benchmarking Network Performance for Scalable Multiplayer in Godot",
+    "objectID": "decisions/20240423-building-metaverse-with-glue-mechanic.html#the-problem-statement",
+    "href": "decisions/20240423-building-metaverse-with-glue-mechanic.html#the-problem-statement",
+    "title": "Accepted: Building a Metaverse with Glue Mechanic in V-Sekai",
     "section": "",
-    "text": "The testing was suggested by Bioblaze Payne, who has outlined a sequential approach:\n\nPhase 1: Basic Connection Test\n\nConnect a user, send a message, await 1000 messages in return, disconnect, then reconnect.\n\nPhase 2: Large Scale Stress Test\n\nSimultaneously connect 4000 users, with each sending a message upon connection every 500ms. Ensure all messages are replicated to all connected clients.\n\n\nDuring these tests, we’ll monitor:\n\nLoad times for initial connections and reconnections.\nThroughput and latency of message delivery.\nServer resource usage (CPU, RAM, Network I/O).\nAny errors or dropped connections that occur.\n\nAll relevant events should be timestamped and logged to a centralized logging system for analysis."
+    "text": "The current model of V-Sekai, while functional, seems limited in its scope. It primarily focuses on avatars moving in a room, which restricts the potential for expansive world-building and exploration."
   },
   {
-    "objectID": "decisions/20231127-performance-test.html#the-upside",
-    "href": "decisions/20231127-performance-test.html#the-upside",
-    "title": "Accepted: Benchmarking Network Performance for Scalable Multiplayer in Godot",
+    "objectID": "decisions/20240423-building-metaverse-with-glue-mechanic.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240423-building-metaverse-with-glue-mechanic.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Accepted: Building a Metaverse with Glue Mechanic in V-Sekai",
     "section": "",
-    "text": "By conducting this research, we aim to:\n\nIdentify the most scalable and efficient networking strategy for the V-Sekai project.\nGather empirical data to inform future development decisions.\nContribute findings back to the wider Godot community to aid in similar multiplayer projects."
+    "text": "The proposed solution is to introduce a “glue mechanic” into the system. This mechanic would allow users to build their own vehicles and structures by gluing different elements together. This could potentially open up the possibility for creating entire universes within the metaverse.\nThis idea was inspired by a game called “Crazy Contraptions” developed by Mantafloof during the Ludum Dare 55 game jam. The game was created in just 48 hours and successfully implemented the glue mechanic concept.\nUsers can combine different elements (represented here as ‘blocks’ and ‘wheels’) to create new structures or vehicles."
   },
   {
-    "objectID": "decisions/20231127-performance-test.html#the-downside",
-    "href": "decisions/20231127-performance-test.html#the-downside",
-    "title": "Accepted: Benchmarking Network Performance for Scalable Multiplayer in Godot",
+    "objectID": "decisions/20240423-building-metaverse-with-glue-mechanic.html#the-benefits",
+    "href": "decisions/20240423-building-metaverse-with-glue-mechanic.html#the-benefits",
+    "title": "Accepted: Building a Metaverse with Glue Mechanic in V-Sekai",
     "section": "",
-    "text": "Potential risks and drawbacks include:\n\nTime and resources required for test setup and execution.\nInterpretation of results may vary, leading to indecision.\nPossible discovery of fundamental issues that could delay project timelines."
+    "text": "Encourages creativity and innovation among users.\nOpens up possibilities for expansive world-building and exploration.\nProvides a reason to work on LODs and memory management for loading worlds."
   },
   {
-    "objectID": "decisions/20231127-performance-test.html#the-road-not-taken",
-    "href": "decisions/20231127-performance-test.html#the-road-not-taken",
-    "title": "Accepted: Benchmarking Network Performance for Scalable Multiplayer in Godot",
+    "objectID": "decisions/20240423-building-metaverse-with-glue-mechanic.html#the-downsides",
+    "href": "decisions/20240423-building-metaverse-with-glue-mechanic.html#the-downsides",
+    "title": "Accepted: Building a Metaverse with Glue Mechanic in V-Sekai",
     "section": "",
-    "text": "This section will detail alternative methods and practices considered but ultimately not chosen, with justifications for their exclusion."
+    "text": "May require significant changes to the existing codebase.\nThis could potentially increase the complexity of the system."
   },
   {
-    "objectID": "decisions/20231127-performance-test.html#the-infrequent-use-case",
-    "href": "decisions/20231127-performance-test.html#the-infrequent-use-case",
-    "title": "Accepted: Benchmarking Network Performance for Scalable Multiplayer in Godot",
+    "objectID": "decisions/20240423-building-metaverse-with-glue-mechanic.html#the-road-not-taken",
+    "href": "decisions/20240423-building-metaverse-with-glue-mechanic.html#the-road-not-taken",
+    "title": "Accepted: Building a Metaverse with Glue Mechanic in V-Sekai",
     "section": "",
-    "text": "We will also explore less common user scenarios that may have unique performance characteristics under each networking strategy."
+    "text": "An alternative approach could be to continue focusing on avatar movement and interaction within a confined space. However, this may limit the potential for expansive world-building and exploration."
   },
   {
-    "objectID": "decisions/20231127-performance-test.html#in-core-and-done-by-us",
-    "href": "decisions/20231127-performance-test.html#in-core-and-done-by-us",
-    "title": "Accepted: Benchmarking Network Performance for Scalable Multiplayer in Godot",
+    "objectID": "decisions/20240423-building-metaverse-with-glue-mechanic.html#the-infrequent-use-case",
+    "href": "decisions/20240423-building-metaverse-with-glue-mechanic.html#the-infrequent-use-case",
+    "title": "Accepted: Building a Metaverse with Glue Mechanic in V-Sekai",
     "section": "",
-    "text": "Discussion on whether the outcomes of this initiative should be integrated into the core V-Sekai codebase or maintained as separate modules."
+    "text": "In cases where users prefer a more confined and controlled environment, the glue mechanic may not be as appealing. However, it could still provide an interesting option for those looking to experiment with world-building."
   },
   {
-    "objectID": "decisions/20231127-performance-test.html#further-reading",
-    "href": "decisions/20231127-performance-test.html#further-reading",
-    "title": "Accepted: Benchmarking Network Performance for Scalable Multiplayer in Godot",
+    "objectID": "decisions/20240423-building-metaverse-with-glue-mechanic.html#in-core-and-done-by-us",
+    "href": "decisions/20240423-building-metaverse-with-glue-mechanic.html#in-core-and-done-by-us",
+    "title": "Accepted: Building a Metaverse with Glue Mechanic in V-Sekai",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis design document was completed with assistance from AI developer Aria."
+    "text": "The implementation of the glue mechanic would be done by the V-Sekai development team."
   },
   {
-    "objectID": "decisions/20231110-efficient-llm-training.html",
-    "href": "decisions/20231110-efficient-llm-training.html",
-    "title": "Proposed: Efficient Training of LLMs in V-Sekai",
+    "objectID": "decisions/20240423-building-metaverse-with-glue-mechanic.html#status",
+    "href": "decisions/20240423-building-metaverse-with-glue-mechanic.html#status",
+    "title": "Accepted: Building a Metaverse with Glue Mechanic in V-Sekai",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, LLM, Training\n\n\n\n\nGiven the limited resources available to V-Sekai, it is crucial to optimize the training time for Language Learning Models (LLMs) like Aria assistant.\n\n\n\nThe challenge lies in efficiently training these models within a constrained timeframe - ideally not exceeding one day.\n\n\n\nTo expedite the training process, we propose the following adjustments to Ludwig:\n\nSet trainable=false to make training over 50x faster.\nEnable Automatic Mixed Precision (AMP) training, which is available when both trainable=true and trainable=false.\nImplement approximate training set evaluation (evaluate_training_set=false). This computes the reported training set metrics at the end of each epoch as a running aggregation of the metrics during training, rather than a separate pass over the training set at the end of each epoch of training. Although this may result in “noisy” metrics in the early epochs, it generally leads to a 33% speedup in training time.\n\n\n\n\nPros:\n\nSignificantly reduces training time.\nAllows for more efficient use of resources.\n\nCons:\n\nEarly training metrics may appear “noisy”.\n\n\n\n\nThis section will be updated with potential alternatives if the proposed solution does not yield the expected results.\n\n\n\nThis section will be updated with infrequent use cases that may arise during the implementation of the proposed solution.\n\n\n\nIs this solution core to our operations and will it be implemented by us? This section will be updated accordingly.\n\n\n\n\nV-Sekai · GitHub\nV-Sekai/v-sekai-game\nLLM Classification - Ludwig\n\nThis proposal was assisted by Aria, an AI assistant."
+    "text": "Status: Accepted"
   },
   {
-    "objectID": "decisions/20231110-efficient-llm-training.html#metadata",
-    "href": "decisions/20231110-efficient-llm-training.html#metadata",
-    "title": "Proposed: Efficient Training of LLMs in V-Sekai",
+    "objectID": "decisions/20240423-building-metaverse-with-glue-mechanic.html#decision-makers",
+    "href": "decisions/20240423-building-metaverse-with-glue-mechanic.html#decision-makers",
+    "title": "Accepted: Building a Metaverse with Glue Mechanic in V-Sekai",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, LLM, Training"
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20231110-efficient-llm-training.html#context",
-    "href": "decisions/20231110-efficient-llm-training.html#context",
-    "title": "Proposed: Efficient Training of LLMs in V-Sekai",
+    "objectID": "decisions/20240423-building-metaverse-with-glue-mechanic.html#tags",
+    "href": "decisions/20240423-building-metaverse-with-glue-mechanic.html#tags",
+    "title": "Accepted: Building a Metaverse with Glue Mechanic in V-Sekai",
     "section": "",
-    "text": "Given the limited resources available to V-Sekai, it is crucial to optimize the training time for Language Learning Models (LLMs) like Aria assistant."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20231110-efficient-llm-training.html#problem",
-    "href": "decisions/20231110-efficient-llm-training.html#problem",
-    "title": "Proposed: Efficient Training of LLMs in V-Sekai",
+    "objectID": "decisions/20240423-building-metaverse-with-glue-mechanic.html#further-reading",
+    "href": "decisions/20240423-building-metaverse-with-glue-mechanic.html#further-reading",
+    "title": "Accepted: Building a Metaverse with Glue Mechanic in V-Sekai",
     "section": "",
-    "text": "The challenge lies in efficiently training these models within a constrained timeframe - ideally not exceeding one day."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20231110-efficient-llm-training.html#solution",
-    "href": "decisions/20231110-efficient-llm-training.html#solution",
-    "title": "Proposed: Efficient Training of LLMs in V-Sekai",
+    "objectID": "decisions/20220228-v-sekai-version-three-plan.html",
+    "href": "decisions/20220228-v-sekai-version-three-plan.html",
+    "title": "Accepted: Planning V-Sekai Version 3 on 2022-02-28",
     "section": "",
-    "text": "To expedite the training process, we propose the following adjustments to Ludwig:\n\nSet trainable=false to make training over 50x faster.\nEnable Automatic Mixed Precision (AMP) training, which is available when both trainable=true and trainable=false.\nImplement approximate training set evaluation (evaluate_training_set=false). This computes the reported training set metrics at the end of each epoch as a running aggregation of the metrics during training, rather than a separate pass over the training set at the end of each epoch of training. Although this may result in “noisy” metrics in the early epochs, it generally leads to a 33% speedup in training time."
+    "text": "Status: accepted \nDeciders: V-Sekai,ifire,lyuma,\nTags: V-Sekai,\n\n\n\nKnow where we’re going by describing what we want.\n\n\n\nProposed mission and a list of tasks.\n\n\n\n\n\n\nGodot Engine pull requests.\n\n\n\n\n\nImprove making and using avatar and map content enhancement\nAble to have our group of people join and communicate (godot speech) enhancement\nRestore VR support (openxr) in V-Sekai enhancement\nTest easier with desktop interaction with objects enhancement\nInteract with objects in vr enhancement\nImport a CCBY, CC0 MMD stage for testing dance stages enhancement\nProvide user generated scripting using WasGo enhancement\n\n\n\n\n\nGain clarity of mission.\n\n\n\n\nThe cost of overhead.\n\n\n\n\n\nOption: Status quo. \nRejection Reason: Complete the wrong thing. \n\n\n\n\nThis is a planning document.\n\n\n\nWe know what we want to do.\n\n\n\n\nNone\n\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20231110-efficient-llm-training.html#pros-and-cons",
-    "href": "decisions/20231110-efficient-llm-training.html#pros-and-cons",
-    "title": "Proposed: Efficient Training of LLMs in V-Sekai",
+    "objectID": "decisions/20220228-v-sekai-version-three-plan.html#context-and-problem-statement",
+    "href": "decisions/20220228-v-sekai-version-three-plan.html#context-and-problem-statement",
+    "title": "Accepted: Planning V-Sekai Version 3 on 2022-02-28",
     "section": "",
-    "text": "Pros:\n\nSignificantly reduces training time.\nAllows for more efficient use of resources.\n\nCons:\n\nEarly training metrics may appear “noisy”."
+    "text": "Know where we’re going by describing what we want."
   },
   {
-    "objectID": "decisions/20231110-efficient-llm-training.html#alternatives",
-    "href": "decisions/20231110-efficient-llm-training.html#alternatives",
-    "title": "Proposed: Efficient Training of LLMs in V-Sekai",
+    "objectID": "decisions/20220228-v-sekai-version-three-plan.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20220228-v-sekai-version-three-plan.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Accepted: Planning V-Sekai Version 3 on 2022-02-28",
     "section": "",
-    "text": "This section will be updated with potential alternatives if the proposed solution does not yield the expected results."
+    "text": "Proposed mission and a list of tasks."
   },
   {
-    "objectID": "decisions/20231110-efficient-llm-training.html#rare-use-cases",
-    "href": "decisions/20231110-efficient-llm-training.html#rare-use-cases",
-    "title": "Proposed: Efficient Training of LLMs in V-Sekai",
+    "objectID": "decisions/20220228-v-sekai-version-three-plan.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20220228-v-sekai-version-three-plan.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Accepted: Planning V-Sekai Version 3 on 2022-02-28",
     "section": "",
-    "text": "This section will be updated with infrequent use cases that may arise during the implementation of the proposed solution."
+    "text": "Godot Engine pull requests.\n\n\n\n\n\nImprove making and using avatar and map content enhancement\nAble to have our group of people join and communicate (godot speech) enhancement\nRestore VR support (openxr) in V-Sekai enhancement\nTest easier with desktop interaction with objects enhancement\nInteract with objects in vr enhancement\nImport a CCBY, CC0 MMD stage for testing dance stages enhancement\nProvide user generated scripting using WasGo enhancement"
   },
   {
-    "objectID": "decisions/20231110-efficient-llm-training.html#implementation",
-    "href": "decisions/20231110-efficient-llm-training.html#implementation",
-    "title": "Proposed: Efficient Training of LLMs in V-Sekai",
+    "objectID": "decisions/20220228-v-sekai-version-three-plan.html#positive-consequences",
+    "href": "decisions/20220228-v-sekai-version-three-plan.html#positive-consequences",
+    "title": "Accepted: Planning V-Sekai Version 3 on 2022-02-28",
     "section": "",
-    "text": "Is this solution core to our operations and will it be implemented by us? This section will be updated accordingly."
+    "text": "Gain clarity of mission."
   },
   {
-    "objectID": "decisions/20231110-efficient-llm-training.html#references",
-    "href": "decisions/20231110-efficient-llm-training.html#references",
-    "title": "Proposed: Efficient Training of LLMs in V-Sekai",
+    "objectID": "decisions/20220228-v-sekai-version-three-plan.html#negative-consequences",
+    "href": "decisions/20220228-v-sekai-version-three-plan.html#negative-consequences",
+    "title": "Accepted: Planning V-Sekai Version 3 on 2022-02-28",
     "section": "",
-    "text": "V-Sekai · GitHub\nV-Sekai/v-sekai-game\nLLM Classification - Ludwig\n\nThis proposal was assisted by Aria, an AI assistant."
+    "text": "The cost of overhead."
   },
   {
-    "objectID": "decisions/20220820-cloth-sim.html",
-    "href": "decisions/20220820-cloth-sim.html",
-    "title": "Proposed: Simulate cloth on characters",
+    "objectID": "decisions/20220228-v-sekai-version-three-plan.html#option-graveyard",
+    "href": "decisions/20220228-v-sekai-version-three-plan.html#option-graveyard",
+    "title": "Accepted: Planning V-Sekai Version 3 on 2022-02-28",
     "section": "",
-    "text": "Proposed: Simulate cloth on characters\nLabels: enhancement\n\nContext and Problem Statement\nWe want to simulate clothing on characters without wardrobe malfunction.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nUse opensource tooling to accomplish this.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nRun conditioner on inputs. https://github.com/fire/preconditioner-for-cloth-and-deformable-body-simulation\n\n\nPositive Consequences\nCan have clothing.\n\n\nNegative Consequences\nCan have clothing.\n\n\nOption graveyard\nNo response\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot trivial.\n\n\nIs there a reason why this should be core and done by us?\nTrying out a test.\n\n\nReferences\n\nV-Sekai\n\n\n\nLicense of the contribution\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Option: Status quo. \nRejection Reason: Complete the wrong thing."
   },
   {
-    "objectID": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html",
-    "href": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html",
-    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Kinoite and #steam",
+    "objectID": "decisions/20220228-v-sekai-version-three-plan.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20220228-v-sekai-version-three-plan.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Accepted: Planning V-Sekai Version 3 on 2022-02-28",
     "section": "",
-    "text": "Status: rejected \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nI don’t have a #steam Deck since it was delayed til February 2022 to test V-Sekai.\n\n\n\nInstall Fedora Kinoite and Steam.\n\n\n\n\nInstall Ventoy on a USB Stick\nInstall iso of Fedora Kinoite onto the drive on Ventoy\nInstall Fedora Kinoite onto hardware proxy defined in another proposal.\nInstall #steam via RPMFusion\n\n\n\n\n\nAble to test builds from Windows?\n\n\n\n\n\nUnknown\n\n\n\n\n\nOption: Use Arch Manjaor\nRejection Reason: Unfamiliar with OS.\n\n\n\n\nNot lines of code.\n\n\n\nQA testing needs to be inhouse.\n\n\n\n\nhttps://en.wikipedia.org/wiki/Steam_Deck\nhttps://download.fedoraproject.org/pub/fedora/linux/releases/35/Kinoite/x86_64/iso/Fedora-Kinoite-ostree-x86_64-35-1.2.iso\n\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "This is a planning document."
   },
   {
-    "objectID": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html#context-and-problem-statement",
-    "href": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html#context-and-problem-statement",
-    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Kinoite and #steam",
+    "objectID": "decisions/20220228-v-sekai-version-three-plan.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20220228-v-sekai-version-three-plan.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Accepted: Planning V-Sekai Version 3 on 2022-02-28",
     "section": "",
-    "text": "I don’t have a #steam Deck since it was delayed til February 2022 to test V-Sekai."
+    "text": "We know what we want to do."
   },
   {
-    "objectID": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Kinoite and #steam",
+    "objectID": "decisions/20220228-v-sekai-version-three-plan.html#references",
+    "href": "decisions/20220228-v-sekai-version-three-plan.html#references",
+    "title": "Accepted: Planning V-Sekai Version 3 on 2022-02-28",
     "section": "",
-    "text": "Install Fedora Kinoite and Steam."
+    "text": "None"
   },
   {
-    "objectID": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Kinoite and #steam",
+    "objectID": "decisions/20220228-v-sekai-version-three-plan.html#derivative-license",
+    "href": "decisions/20220228-v-sekai-version-three-plan.html#derivative-license",
+    "title": "Accepted: Planning V-Sekai Version 3 on 2022-02-28",
     "section": "",
-    "text": "Install Ventoy on a USB Stick\nInstall iso of Fedora Kinoite onto the drive on Ventoy\nInstall Fedora Kinoite onto hardware proxy defined in another proposal.\nInstall #steam via RPMFusion"
+    "text": "Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html#positive-consequences",
-    "href": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html#positive-consequences",
-    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Kinoite and #steam",
+    "objectID": "decisions/20240810-steamvr-dongles-separate.html",
+    "href": "decisions/20240810-steamvr-dongles-separate.html",
+    "title": "Proposed: Improving Connectivity for Valve StreamVR Light House Dongles",
     "section": "",
-    "text": "Able to test builds from Windows?"
+    "text": "Valve StreamVR Light House Dongles are unable to connect.\n\n\n\nValve StreamVR Light House Dongles are unable to connect because of wireless interference if plugged into hubs upright and side by side.\n\n\n\nUse the supplied HTCVive cradles for the dongles. Keep the dongles upright.\n\n\n\n\nReduced Interference: By using the supplied cradles and keeping the dongles upright, wireless interference is minimized.\nImproved Connectivity: Ensures stable and reliable connections for the Valve StreamVR Light House Dongles.\nUser-Friendly: Simple implementation that leverages existing hardware (HTCVive cradles).\n\n\n\n\n\nAdditional Space Required: Using cradles may require more physical space compared to plugging dongles directly into a hub.\nPotential Cost: If users do not already have the HTCVive cradles, they may need to purchase them separately.\n\n\n\n\n\nAlternative Positioning: Exploring other physical arrangements for the dongles without using cradles.\nSoftware Solutions: Investigating software-based solutions to mitigate wireless interference.\n\n\n\n\n\nLimited Setup Scenarios: Users with unique setups where space constraints make it difficult to use the cradles effectively.\n\n\n\n\n\nImplementation: The V-Sekai development team will handle the implementation and testing of this proposal.\nDocumentation: Detailed instructions and guidelines will be provided to users for setting up their dongles using the cradles.\n\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html#negative-consequences",
-    "href": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html#negative-consequences",
-    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Kinoite and #steam",
+    "objectID": "decisions/20240810-steamvr-dongles-separate.html#the-context",
+    "href": "decisions/20240810-steamvr-dongles-separate.html#the-context",
+    "title": "Proposed: Improving Connectivity for Valve StreamVR Light House Dongles",
     "section": "",
-    "text": "Unknown"
+    "text": "Valve StreamVR Light House Dongles are unable to connect."
   },
   {
-    "objectID": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html#option-graveyard",
-    "href": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html#option-graveyard",
-    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Kinoite and #steam",
+    "objectID": "decisions/20240810-steamvr-dongles-separate.html#the-problem-statement",
+    "href": "decisions/20240810-steamvr-dongles-separate.html#the-problem-statement",
+    "title": "Proposed: Improving Connectivity for Valve StreamVR Light House Dongles",
     "section": "",
-    "text": "Option: Use Arch Manjaor\nRejection Reason: Unfamiliar with OS."
+    "text": "Valve StreamVR Light House Dongles are unable to connect because of wireless interference if plugged into hubs upright and side by side."
   },
   {
-    "objectID": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Kinoite and #steam",
+    "objectID": "decisions/20240810-steamvr-dongles-separate.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240810-steamvr-dongles-separate.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Improving Connectivity for Valve StreamVR Light House Dongles",
     "section": "",
-    "text": "Not lines of code."
+    "text": "Use the supplied HTCVive cradles for the dongles. Keep the dongles upright."
   },
   {
-    "objectID": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Kinoite and #steam",
+    "objectID": "decisions/20240810-steamvr-dongles-separate.html#the-benefits",
+    "href": "decisions/20240810-steamvr-dongles-separate.html#the-benefits",
+    "title": "Proposed: Improving Connectivity for Valve StreamVR Light House Dongles",
     "section": "",
-    "text": "QA testing needs to be inhouse."
+    "text": "Reduced Interference: By using the supplied cradles and keeping the dongles upright, wireless interference is minimized.\nImproved Connectivity: Ensures stable and reliable connections for the Valve StreamVR Light House Dongles.\nUser-Friendly: Simple implementation that leverages existing hardware (HTCVive cradles)."
   },
   {
-    "objectID": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html#references",
-    "href": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html#references",
-    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Kinoite and #steam",
+    "objectID": "decisions/20240810-steamvr-dongles-separate.html#the-downsides",
+    "href": "decisions/20240810-steamvr-dongles-separate.html#the-downsides",
+    "title": "Proposed: Improving Connectivity for Valve StreamVR Light House Dongles",
     "section": "",
-    "text": "https://en.wikipedia.org/wiki/Steam_Deck\nhttps://download.fedoraproject.org/pub/fedora/linux/releases/35/Kinoite/x86_64/iso/Fedora-Kinoite-ostree-x86_64-35-1.2.iso"
+    "text": "Additional Space Required: Using cradles may require more physical space compared to plugging dongles directly into a hub.\nPotential Cost: If users do not already have the HTCVive cradles, they may need to purchase them separately."
   },
   {
-    "objectID": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html#derivative-license",
-    "href": "decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html#derivative-license",
-    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Kinoite and #steam",
+    "objectID": "decisions/20240810-steamvr-dongles-separate.html#the-road-not-taken",
+    "href": "decisions/20240810-steamvr-dongles-separate.html#the-road-not-taken",
+    "title": "Proposed: Improving Connectivity for Valve StreamVR Light House Dongles",
     "section": "",
-    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Alternative Positioning: Exploring other physical arrangements for the dongles without using cradles.\nSoftware Solutions: Investigating software-based solutions to mitigate wireless interference."
   },
   {
-    "objectID": "decisions/20240324-v-sekai-as-slc.html",
-    "href": "decisions/20240324-v-sekai-as-slc.html",
-    "title": "Proposed: V-Sekai Implementation Using SLC Framework",
+    "objectID": "decisions/20240810-steamvr-dongles-separate.html#the-infrequent-use-case",
+    "href": "decisions/20240810-steamvr-dongles-separate.html#the-infrequent-use-case",
+    "title": "Proposed: Improving Connectivity for Valve StreamVR Light House Dongles",
     "section": "",
-    "text": "VR gaming requires a seamless, inviting experience. A VR dating game can utilize simplicity, engagement, and completeness principles.\n\n\n\nThe challenge is creating an intuitive, engaging VR dating game with a comprehensive feature set from the start.\n\n\n\nUsing the SLC framework—Simple, Lovable, Complete—the project should:\n\nSimple: Emphasize user-friendly design and easy navigation.\nfunction interact_with_object(object):\n    if object.is_interactable:\n        show_prompt(\"Press X to interact\")\n        wait_for_input()\n        execute_interaction()\nLovable: Develop appealing characters and environments.\nCharacter customization concept art\nComplete: Launch with diverse scenarios and detailed character interactions.\nlaunch_features:\n  - CompleteCharacterCustomization\n  - DiverseScenarios\n  - InDepthCharacterInteractions\n  - RealTimeChat\n\n\n\n\nThis approach ensures an accessible, captivating product without immediate expansion need, catering to a wide audience.\n\n\n\nAn extensive initial development phase may delay release, and simplicity could limit advanced functionalities.\n\n\n\nA leaner initial version might allow earlier release but risk losing early adopters.\n\n\n\nDesign a user-friendly re-engagement process for returning users.\n\n\n\nFocus on essential launch features, expand based on user feedback.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai GitHub Repository\nV-Sekai Game Project\n\nAssistance provided by AI assistant Aria."
+    "text": "Limited Setup Scenarios: Users with unique setups where space constraints make it difficult to use the cradles effectively."
   },
   {
-    "objectID": "decisions/20240324-v-sekai-as-slc.html#context",
-    "href": "decisions/20240324-v-sekai-as-slc.html#context",
-    "title": "Proposed: V-Sekai Implementation Using SLC Framework",
+    "objectID": "decisions/20240810-steamvr-dongles-separate.html#in-core-and-done-by-us",
+    "href": "decisions/20240810-steamvr-dongles-separate.html#in-core-and-done-by-us",
+    "title": "Proposed: Improving Connectivity for Valve StreamVR Light House Dongles",
     "section": "",
-    "text": "VR gaming requires a seamless, inviting experience. A VR dating game can utilize simplicity, engagement, and completeness principles."
+    "text": "Implementation: The V-Sekai development team will handle the implementation and testing of this proposal.\nDocumentation: Detailed instructions and guidelines will be provided to users for setting up their dongles using the cradles."
   },
   {
-    "objectID": "decisions/20240324-v-sekai-as-slc.html#problem",
-    "href": "decisions/20240324-v-sekai-as-slc.html#problem",
-    "title": "Proposed: V-Sekai Implementation Using SLC Framework",
+    "objectID": "decisions/20240810-steamvr-dongles-separate.html#status",
+    "href": "decisions/20240810-steamvr-dongles-separate.html#status",
+    "title": "Proposed: Improving Connectivity for Valve StreamVR Light House Dongles",
     "section": "",
-    "text": "The challenge is creating an intuitive, engaging VR dating game with a comprehensive feature set from the start."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20240324-v-sekai-as-slc.html#proposal",
-    "href": "decisions/20240324-v-sekai-as-slc.html#proposal",
-    "title": "Proposed: V-Sekai Implementation Using SLC Framework",
+    "objectID": "decisions/20240810-steamvr-dongles-separate.html#decision-makers",
+    "href": "decisions/20240810-steamvr-dongles-separate.html#decision-makers",
+    "title": "Proposed: Improving Connectivity for Valve StreamVR Light House Dongles",
     "section": "",
-    "text": "Using the SLC framework—Simple, Lovable, Complete—the project should:\n\nSimple: Emphasize user-friendly design and easy navigation.\nfunction interact_with_object(object):\n    if object.is_interactable:\n        show_prompt(\"Press X to interact\")\n        wait_for_input()\n        execute_interaction()\nLovable: Develop appealing characters and environments.\nCharacter customization concept art\nComplete: Launch with diverse scenarios and detailed character interactions.\nlaunch_features:\n  - CompleteCharacterCustomization\n  - DiverseScenarios\n  - InDepthCharacterInteractions\n  - RealTimeChat"
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20240324-v-sekai-as-slc.html#benefits",
-    "href": "decisions/20240324-v-sekai-as-slc.html#benefits",
-    "title": "Proposed: V-Sekai Implementation Using SLC Framework",
+    "objectID": "decisions/20240810-steamvr-dongles-separate.html#tags",
+    "href": "decisions/20240810-steamvr-dongles-separate.html#tags",
+    "title": "Proposed: Improving Connectivity for Valve StreamVR Light House Dongles",
     "section": "",
-    "text": "This approach ensures an accessible, captivating product without immediate expansion need, catering to a wide audience."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20240324-v-sekai-as-slc.html#downsides",
-    "href": "decisions/20240324-v-sekai-as-slc.html#downsides",
-    "title": "Proposed: V-Sekai Implementation Using SLC Framework",
+    "objectID": "decisions/20240810-steamvr-dongles-separate.html#further-reading",
+    "href": "decisions/20240810-steamvr-dongles-separate.html#further-reading",
+    "title": "Proposed: Improving Connectivity for Valve StreamVR Light House Dongles",
     "section": "",
-    "text": "An extensive initial development phase may delay release, and simplicity could limit advanced functionalities."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240324-v-sekai-as-slc.html#alternate-approach",
-    "href": "decisions/20240324-v-sekai-as-slc.html#alternate-approach",
-    "title": "Proposed: V-Sekai Implementation Using SLC Framework",
+    "objectID": "decisions/20220317-protect-minumum-spec-steam-deck.html",
+    "href": "decisions/20220317-protect-minumum-spec-steam-deck.html",
+    "title": "Proposed: To protect the minimum spec maintain steam deck version of flatmode V-Sekai",
     "section": "",
-    "text": "A leaner initial version might allow earlier release but risk losing early adopters."
+    "text": "Proposed: To protect the minimum spec maintain steam deck version of flatmode V-Sekai\n\nDescribe the status of the issue.\nproposed\n\n\nList the deciders of the issue.\nV-Sekai,fire,\n\n\nDescribe the tags of the issue.\nV-Sekai,\n\n\nContext and Problem Statement\nProvide a restricted environment that can limit our art, compute, storage budget.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nPropose to use the steam deck as the minimum platform for V-Sekai flat mode.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nMust hit the screen refresh rate or more.\n\n\nPositive Consequences\n\nConstrained system provide better tests and code.\n\n\n\nNegative Consequences\n\nFlatmode is not the main design of V-Sekai\n\n\n\nOption graveyard\nNo response\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\n\nThis is a complex integration test. Not a few lines of script.\n\n\n\nIs there a reason why this should be core and done by us?\nSetting minimum requirements is a core feature.\n\n\nReferences\n\nV-Sekai\n\n\n\nLicense of the contribution\nCopyright (c) 2022 V-Sekai contributors. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240324-v-sekai-as-slc.html#infrequent-users-consideration",
-    "href": "decisions/20240324-v-sekai-as-slc.html#infrequent-users-consideration",
-    "title": "Proposed: V-Sekai Implementation Using SLC Framework",
+    "objectID": "decisions/20230611-wasm-in-v-sekai.html",
+    "href": "decisions/20230611-wasm-in-v-sekai.html",
+    "title": "Proposed: Wasm in V-Sekai Proposal",
     "section": "",
-    "text": "Design a user-friendly re-engagement process for returning users."
+    "text": "Status: proposed\nDeciders: V-Sekai, fire\nTags: V-Sekai\n\n\n\n\nV-Sekai aims to provide a high-performance platform for virtual worlds and avatar-based social games. The current implementation relies on GDScript or C++ native modules, which may not offer the desired performance, user agency, complex calculations, graphics rendering, and algorithm execution.\n\n\n\nV-Sekai utilizes WebAssembly (Wasm) to enhance performance, offering an alternative to GDScript.\n\n\n\nCore modules: Owned by V-Sekai\nCustom modules: Owned by users\n\n\n\n\nUser-uploaded Wasm modules undergo a two-step process for safety and unauthorized access prevention:\n\nValidation: Ensure module structure and integrity adhere to security standards.\nSandboxing: Confine modules in a secure environment, restricting system resource access and mitigating potential harm.\n\n\n\n\nWasm modules facilitate advanced functions in virtual worlds and avatar-based social games, such as:\n\nEfficient character animations\nInteractive environments\nReal-time multiplayer networking\nImmersive gameplay experiences\n\n\n\n\n\nThe proposed solution uses WebAssembly (Wasm) to enhance performance and functionality in V-Sekai through User-Generated Content (UGC) Wasm modules. These modules are attached to an existing base node as a script, enabling them to provide property data and behavior for nodes in the virtual world or game.\nHere’s a concise explanation of the implementation:\n\nUser uploads a Wasm module: Custom Wasm modules with desired functionality are uploaded to V-Sekai.\nAttach Wasm module to a node: The Wasm module is attached to a node as a script, providing advanced functionality for the node.\nImplement behavior within the Variant dictionary: Node behavior is defined within script variable, enabling Wasm modules to provide both property data and behavior.\nUtilize Godot’s set_script property: Using Godot’s set_script property, Wasm modules are attached to nodes and objects, simplifying dependency handling.\nProperties after the set script: Adding properties directly onto the node after the script = property is set\n\nThis approach ensures graceful handling of missing resources while offering advanced functionality through user-uploaded Wasm modules.\n\n\n\n\nImproved performance for complex calculations, graphics rendering, and algorithm execution\nGreater user control over scripts and customization\nEnhanced functionality for virtual worlds and avatar-based social games\n\n\n\n\n\nPotential security risks with user-uploaded Wasm modules\nIncreased complexity in implementation and maintenance\nEnsuring a wasm module has no defects is difficult with or without source code.\n\n\n\n\n\nOptimizing GDScript: Improving the performance of GDScript was considered, but it would not provide the same level of performance boost as WebAssembly.\nUsing a different scripting language: Alternative scripting languages like Lua or Python were considered, but they also do not offer the desired performance improvements compared to WebAssembly.\nNative code integration: Integrating native code (C++, Rust, etc.) directly into V-Sekai was considered, but it would increase complexity and maintenance efforts. Additionally, it would not provide the same level of security and sandboxing as WebAssembly.\n\n\n\n\nNo, the enhancement aims to provide a significant performance boost and advanced functionality that cannot be achieved with a few lines of script.\n\n\n\nYes, integrating Wasm into V-Sekai’s core ensures optimal performance and seamless integration with existing systems.\n\n\n\n\nV-Sekai\nashtonmeuser/godot-wasm/issues/43\nThis article was assisted by AI.\n\n\n\n\nHere’s a glossary of definitions to help people understand the terms used in the Wasm in V-Sekai proposal:\n\nWebAssembly (Wasm): A type of code that is more portable than regular code, making games and virtual worlds work better. Originally made for the web.\nGDScript: A programming language used to make games and apps in the Godot game engine.\nC++ native modules: Pieces of code written in the C++ programming language that can be added to a game or app to make it work better.\nV-Sekai: A platform for creating virtual worlds and avatar-based social games.\nMetadata: Information about something, like who made it and what it’s for.\nValidation: Checking if something is correct and follows the rules.\nSandboxing: Putting something in a safe area where it can’t cause harm or access things it shouldn’t.\nUser-Generated Content (UGC): Things that people who use a game or app create themselves, like characters, levels, or stories.\nMissingNode: A part of the game or app that needs a script to tell it what to do.\nMissingResource: Something that a game or app needs but doesn’t have yet, like an image or sound.\nVariant: A data type in Godot that can store different kinds of information, like numbers, text, or objects. It is used to represent and manipulate data in various ways within the game engine.\nNode3D: A point in a 3D space that helps build a virtual world or game.\nGodot: A free and open-source game engine used to create games and apps.\nLua: A programming language often used in game development.\nPython: A popular programming language used for many purposes, including game development.\nRust: A programming language focused on safety and performance, often used for creating fast and reliable software."
   },
   {
-    "objectID": "decisions/20240324-v-sekai-as-slc.html#development-philosophy",
-    "href": "decisions/20240324-v-sekai-as-slc.html#development-philosophy",
-    "title": "Proposed: V-Sekai Implementation Using SLC Framework",
+    "objectID": "decisions/20230611-wasm-in-v-sekai.html#metadata",
+    "href": "decisions/20230611-wasm-in-v-sekai.html#metadata",
+    "title": "Proposed: Wasm in V-Sekai Proposal",
     "section": "",
-    "text": "Focus on essential launch features, expand based on user feedback."
+    "text": "Status: proposed\nDeciders: V-Sekai, fire\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20240324-v-sekai-as-slc.html#status",
-    "href": "decisions/20240324-v-sekai-as-slc.html#status",
-    "title": "Proposed: V-Sekai Implementation Using SLC Framework",
+    "objectID": "decisions/20230611-wasm-in-v-sekai.html#context-and-problem-statement",
+    "href": "decisions/20230611-wasm-in-v-sekai.html#context-and-problem-statement",
+    "title": "Proposed: Wasm in V-Sekai Proposal",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "V-Sekai aims to provide a high-performance platform for virtual worlds and avatar-based social games. The current implementation relies on GDScript or C++ native modules, which may not offer the desired performance, user agency, complex calculations, graphics rendering, and algorithm execution."
   },
   {
-    "objectID": "decisions/20240324-v-sekai-as-slc.html#decision-makers",
-    "href": "decisions/20240324-v-sekai-as-slc.html#decision-makers",
-    "title": "Proposed: V-Sekai Implementation Using SLC Framework",
+    "objectID": "decisions/20230611-wasm-in-v-sekai.html#proposed-solution",
+    "href": "decisions/20230611-wasm-in-v-sekai.html#proposed-solution",
+    "title": "Proposed: Wasm in V-Sekai Proposal",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "V-Sekai utilizes WebAssembly (Wasm) to enhance performance, offering an alternative to GDScript.\n\n\n\nCore modules: Owned by V-Sekai\nCustom modules: Owned by users\n\n\n\n\nUser-uploaded Wasm modules undergo a two-step process for safety and unauthorized access prevention:\n\nValidation: Ensure module structure and integrity adhere to security standards.\nSandboxing: Confine modules in a secure environment, restricting system resource access and mitigating potential harm.\n\n\n\n\nWasm modules facilitate advanced functions in virtual worlds and avatar-based social games, such as:\n\nEfficient character animations\nInteractive environments\nReal-time multiplayer networking\nImmersive gameplay experiences"
   },
   {
-    "objectID": "decisions/20240324-v-sekai-as-slc.html#tags",
-    "href": "decisions/20240324-v-sekai-as-slc.html#tags",
-    "title": "Proposed: V-Sekai Implementation Using SLC Framework",
+    "objectID": "decisions/20230611-wasm-in-v-sekai.html#implementation",
+    "href": "decisions/20230611-wasm-in-v-sekai.html#implementation",
+    "title": "Proposed: Wasm in V-Sekai Proposal",
     "section": "",
-    "text": "V-Sekai"
+    "text": "The proposed solution uses WebAssembly (Wasm) to enhance performance and functionality in V-Sekai through User-Generated Content (UGC) Wasm modules. These modules are attached to an existing base node as a script, enabling them to provide property data and behavior for nodes in the virtual world or game.\nHere’s a concise explanation of the implementation:\n\nUser uploads a Wasm module: Custom Wasm modules with desired functionality are uploaded to V-Sekai.\nAttach Wasm module to a node: The Wasm module is attached to a node as a script, providing advanced functionality for the node.\nImplement behavior within the Variant dictionary: Node behavior is defined within script variable, enabling Wasm modules to provide both property data and behavior.\nUtilize Godot’s set_script property: Using Godot’s set_script property, Wasm modules are attached to nodes and objects, simplifying dependency handling.\nProperties after the set script: Adding properties directly onto the node after the script = property is set\n\nThis approach ensures graceful handling of missing resources while offering advanced functionality through user-uploaded Wasm modules."
   },
   {
-    "objectID": "decisions/20240324-v-sekai-as-slc.html#further-reading",
-    "href": "decisions/20240324-v-sekai-as-slc.html#further-reading",
-    "title": "Proposed: V-Sekai Implementation Using SLC Framework",
+    "objectID": "decisions/20230611-wasm-in-v-sekai.html#positive-consequences",
+    "href": "decisions/20230611-wasm-in-v-sekai.html#positive-consequences",
+    "title": "Proposed: Wasm in V-Sekai Proposal",
     "section": "",
-    "text": "V-Sekai GitHub Repository\nV-Sekai Game Project\n\nAssistance provided by AI assistant Aria."
+    "text": "Improved performance for complex calculations, graphics rendering, and algorithm execution\nGreater user control over scripts and customization\nEnhanced functionality for virtual worlds and avatar-based social games"
   },
   {
-    "objectID": "decisions/20240411-elixir-libgodot-bundlex.html",
-    "href": "decisions/20240411-elixir-libgodot-bundlex.html",
-    "title": "Proposed: Use Bundlex for Binding GDExtension to Elixir for Libgodot to Implement a Distributed Simulation",
+    "objectID": "decisions/20230611-wasm-in-v-sekai.html#negative-consequences",
+    "href": "decisions/20230611-wasm-in-v-sekai.html#negative-consequences",
+    "title": "Proposed: Wasm in V-Sekai Proposal",
     "section": "",
-    "text": "The V-Sekai development team is striving to enhance the simulation experience in our VR game. We aim to create a more immersive and interactive environment for our players.\n\n\n\nWe can bind GDExtension to a C-like language for libgodot to implement a distributed simulation.\n\n\n\nInstead of godot-zig, we propose using Bundlex, a multi-platform tool for compiling C and C++ code along with Elixir projects. This will allow us to leverage the power of Elixir’s concurrency and fault-tolerance features, which are ideal for creating distributed simulations.\ndefmodule MyProject do\n  use Bundlex.Project\n\n  def project() do\n    [\n      app: :my_project,\n      compilers: [:bundlex],\n      deps: deps()\n    ]\n  end\n\n  defp deps do\n    [\n      {:bundlex, \"~&gt; 0.2\"}\n    ]\n  end\nend\n\n\n\n\nEnhanced simulation performance due to Elixir’s efficient handling of concurrent processes.\nImproved fault tolerance, as Elixir’s supervisor trees can automatically recover from errors.\nIncreased developer productivity, as Elixir’s syntax is concise and expressive.\n\n\n\n\n\nRequires learning a new programming language (Elixir), which may increase the development time initially.\nPotential compatibility issues between Elixir and existing parts of the system.\n\n\n\n\nWe considered using other languages like Rust or Go, but they did not offer the same level of concurrency and fault-tolerance features as Elixir.\n\n\n\nThis proposal may not be suitable for smaller projects that do not require complex distributed simulations.\n\n\n\nThe V-Sekai development team will implement this proposal.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nBundlex\n\nAssisted by Aria."
+    "text": "Potential security risks with user-uploaded Wasm modules\nIncreased complexity in implementation and maintenance\nEnsuring a wasm module has no defects is difficult with or without source code."
   },
   {
-    "objectID": "decisions/20240411-elixir-libgodot-bundlex.html#context",
-    "href": "decisions/20240411-elixir-libgodot-bundlex.html#context",
-    "title": "Proposed: Use Bundlex for Binding GDExtension to Elixir for Libgodot to Implement a Distributed Simulation",
+    "objectID": "decisions/20230611-wasm-in-v-sekai.html#option-graveyard",
+    "href": "decisions/20230611-wasm-in-v-sekai.html#option-graveyard",
+    "title": "Proposed: Wasm in V-Sekai Proposal",
     "section": "",
-    "text": "The V-Sekai development team is striving to enhance the simulation experience in our VR game. We aim to create a more immersive and interactive environment for our players."
+    "text": "Optimizing GDScript: Improving the performance of GDScript was considered, but it would not provide the same level of performance boost as WebAssembly.\nUsing a different scripting language: Alternative scripting languages like Lua or Python were considered, but they also do not offer the desired performance improvements compared to WebAssembly.\nNative code integration: Integrating native code (C++, Rust, etc.) directly into V-Sekai was considered, but it would increase complexity and maintenance efforts. Additionally, it would not provide the same level of security and sandboxing as WebAssembly."
   },
   {
-    "objectID": "decisions/20240411-elixir-libgodot-bundlex.html#problem-statement",
-    "href": "decisions/20240411-elixir-libgodot-bundlex.html#problem-statement",
-    "title": "Proposed: Use Bundlex for Binding GDExtension to Elixir for Libgodot to Implement a Distributed Simulation",
+    "objectID": "decisions/20230611-wasm-in-v-sekai.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230611-wasm-in-v-sekai.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Wasm in V-Sekai Proposal",
     "section": "",
-    "text": "We can bind GDExtension to a C-like language for libgodot to implement a distributed simulation."
+    "text": "No, the enhancement aims to provide a significant performance boost and advanced functionality that cannot be achieved with a few lines of script."
   },
   {
-    "objectID": "decisions/20240411-elixir-libgodot-bundlex.html#proposed-solution",
-    "href": "decisions/20240411-elixir-libgodot-bundlex.html#proposed-solution",
-    "title": "Proposed: Use Bundlex for Binding GDExtension to Elixir for Libgodot to Implement a Distributed Simulation",
+    "objectID": "decisions/20230611-wasm-in-v-sekai.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230611-wasm-in-v-sekai.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Wasm in V-Sekai Proposal",
     "section": "",
-    "text": "Instead of godot-zig, we propose using Bundlex, a multi-platform tool for compiling C and C++ code along with Elixir projects. This will allow us to leverage the power of Elixir’s concurrency and fault-tolerance features, which are ideal for creating distributed simulations.\ndefmodule MyProject do\n  use Bundlex.Project\n\n  def project() do\n    [\n      app: :my_project,\n      compilers: [:bundlex],\n      deps: deps()\n    ]\n  end\n\n  defp deps do\n    [\n      {:bundlex, \"~&gt; 0.2\"}\n    ]\n  end\nend"
+    "text": "Yes, integrating Wasm into V-Sekai’s core ensures optimal performance and seamless integration with existing systems."
   },
   {
-    "objectID": "decisions/20240411-elixir-libgodot-bundlex.html#benefits",
-    "href": "decisions/20240411-elixir-libgodot-bundlex.html#benefits",
-    "title": "Proposed: Use Bundlex for Binding GDExtension to Elixir for Libgodot to Implement a Distributed Simulation",
+    "objectID": "decisions/20230611-wasm-in-v-sekai.html#references",
+    "href": "decisions/20230611-wasm-in-v-sekai.html#references",
+    "title": "Proposed: Wasm in V-Sekai Proposal",
     "section": "",
-    "text": "Enhanced simulation performance due to Elixir’s efficient handling of concurrent processes.\nImproved fault tolerance, as Elixir’s supervisor trees can automatically recover from errors.\nIncreased developer productivity, as Elixir’s syntax is concise and expressive."
+    "text": "V-Sekai\nashtonmeuser/godot-wasm/issues/43\nThis article was assisted by AI."
   },
   {
-    "objectID": "decisions/20240411-elixir-libgodot-bundlex.html#downsides",
-    "href": "decisions/20240411-elixir-libgodot-bundlex.html#downsides",
-    "title": "Proposed: Use Bundlex for Binding GDExtension to Elixir for Libgodot to Implement a Distributed Simulation",
+    "objectID": "decisions/20230611-wasm-in-v-sekai.html#glossary",
+    "href": "decisions/20230611-wasm-in-v-sekai.html#glossary",
+    "title": "Proposed: Wasm in V-Sekai Proposal",
     "section": "",
-    "text": "Requires learning a new programming language (Elixir), which may increase the development time initially.\nPotential compatibility issues between Elixir and existing parts of the system."
+    "text": "Here’s a glossary of definitions to help people understand the terms used in the Wasm in V-Sekai proposal:\n\nWebAssembly (Wasm): A type of code that is more portable than regular code, making games and virtual worlds work better. Originally made for the web.\nGDScript: A programming language used to make games and apps in the Godot game engine.\nC++ native modules: Pieces of code written in the C++ programming language that can be added to a game or app to make it work better.\nV-Sekai: A platform for creating virtual worlds and avatar-based social games.\nMetadata: Information about something, like who made it and what it’s for.\nValidation: Checking if something is correct and follows the rules.\nSandboxing: Putting something in a safe area where it can’t cause harm or access things it shouldn’t.\nUser-Generated Content (UGC): Things that people who use a game or app create themselves, like characters, levels, or stories.\nMissingNode: A part of the game or app that needs a script to tell it what to do.\nMissingResource: Something that a game or app needs but doesn’t have yet, like an image or sound.\nVariant: A data type in Godot that can store different kinds of information, like numbers, text, or objects. It is used to represent and manipulate data in various ways within the game engine.\nNode3D: A point in a 3D space that helps build a virtual world or game.\nGodot: A free and open-source game engine used to create games and apps.\nLua: A programming language often used in game development.\nPython: A popular programming language used for many purposes, including game development.\nRust: A programming language focused on safety and performance, often used for creating fast and reliable software."
   },
   {
-    "objectID": "decisions/20240411-elixir-libgodot-bundlex.html#alternatives-considered",
-    "href": "decisions/20240411-elixir-libgodot-bundlex.html#alternatives-considered",
-    "title": "Proposed: Use Bundlex for Binding GDExtension to Elixir for Libgodot to Implement a Distributed Simulation",
+    "objectID": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html",
+    "href": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html",
+    "title": "Proposed: Polish demo of V-Sekai by making invisible meshes appear via the use of the exporter.",
     "section": "",
-    "text": "We considered using other languages like Rust or Go, but they did not offer the same level of concurrency and fault-tolerance features as Elixir."
+    "text": "Status: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nPolish the demo of V-Sekai\n\n\n\nWe want to validate the V-Sekai exporter addon works.\n\n\n\n\nValidate the broken V-Sekai scene exporter addon.\nExport test scene.\n\n\n\n\n\nRemove the high priority bug of the missing meshes.\n\n\n\n\n\n[e.g., compromising quality attribute, follow-up decisions required, …]\n\n[this section can be repeated for each option if more than one option is open for consideration]\n\n\n\n\nOption: Work on making the text have higher texel density.\nRejection Reason: Is time consuming and not as priority.\n\n\n\n\nThe is core V-Sekai.\n\n\n\nOnly we can set the initial scene.\n\n\n\n\nhttps://v-sekai.org/\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240411-elixir-libgodot-bundlex.html#infrequent-use-case",
-    "href": "decisions/20240411-elixir-libgodot-bundlex.html#infrequent-use-case",
-    "title": "Proposed: Use Bundlex for Binding GDExtension to Elixir for Libgodot to Implement a Distributed Simulation",
+    "objectID": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html#context-and-problem-statement",
+    "href": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html#context-and-problem-statement",
+    "title": "Proposed: Polish demo of V-Sekai by making invisible meshes appear via the use of the exporter.",
     "section": "",
-    "text": "This proposal may not be suitable for smaller projects that do not require complex distributed simulations."
+    "text": "Polish the demo of V-Sekai"
   },
   {
-    "objectID": "decisions/20240411-elixir-libgodot-bundlex.html#implementation",
-    "href": "decisions/20240411-elixir-libgodot-bundlex.html#implementation",
-    "title": "Proposed: Use Bundlex for Binding GDExtension to Elixir for Libgodot to Implement a Distributed Simulation",
+    "objectID": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: Polish demo of V-Sekai by making invisible meshes appear via the use of the exporter.",
     "section": "",
-    "text": "The V-Sekai development team will implement this proposal."
+    "text": "We want to validate the V-Sekai exporter addon works."
   },
   {
-    "objectID": "decisions/20240411-elixir-libgodot-bundlex.html#status",
-    "href": "decisions/20240411-elixir-libgodot-bundlex.html#status",
-    "title": "Proposed: Use Bundlex for Binding GDExtension to Elixir for Libgodot to Implement a Distributed Simulation",
+    "objectID": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Polish demo of V-Sekai by making invisible meshes appear via the use of the exporter.",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "Validate the broken V-Sekai scene exporter addon.\nExport test scene."
   },
   {
-    "objectID": "decisions/20240411-elixir-libgodot-bundlex.html#decision-makers",
-    "href": "decisions/20240411-elixir-libgodot-bundlex.html#decision-makers",
-    "title": "Proposed: Use Bundlex for Binding GDExtension to Elixir for Libgodot to Implement a Distributed Simulation",
+    "objectID": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html#positive-consequences",
+    "href": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html#positive-consequences",
+    "title": "Proposed: Polish demo of V-Sekai by making invisible meshes appear via the use of the exporter.",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "Remove the high priority bug of the missing meshes."
   },
   {
-    "objectID": "decisions/20240411-elixir-libgodot-bundlex.html#tags",
-    "href": "decisions/20240411-elixir-libgodot-bundlex.html#tags",
-    "title": "Proposed: Use Bundlex for Binding GDExtension to Elixir for Libgodot to Implement a Distributed Simulation",
+    "objectID": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html#negative-consequences",
+    "href": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html#negative-consequences",
+    "title": "Proposed: Polish demo of V-Sekai by making invisible meshes appear via the use of the exporter.",
     "section": "",
-    "text": "V-Sekai"
+    "text": "[e.g., compromising quality attribute, follow-up decisions required, …]\n\n[this section can be repeated for each option if more than one option is open for consideration]"
   },
   {
-    "objectID": "decisions/20240411-elixir-libgodot-bundlex.html#further-reading",
-    "href": "decisions/20240411-elixir-libgodot-bundlex.html#further-reading",
-    "title": "Proposed: Use Bundlex for Binding GDExtension to Elixir for Libgodot to Implement a Distributed Simulation",
+    "objectID": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html#option-graveyard",
+    "href": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html#option-graveyard",
+    "title": "Proposed: Polish demo of V-Sekai by making invisible meshes appear via the use of the exporter.",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nBundlex\n\nAssisted by Aria."
+    "text": "Option: Work on making the text have higher texel density.\nRejection Reason: Is time consuming and not as priority."
   },
   {
-    "objectID": "decisions/20231110-blender-manual-t-pose.html",
-    "href": "decisions/20231110-blender-manual-t-pose.html",
-    "title": "Accepted: Overcoming the Blender T-Pose Limitation with Documentation",
+    "objectID": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Polish demo of V-Sekai by making invisible meshes appear via the use of the exporter.",
     "section": "",
-    "text": "Status: Accepted\nDeciders: V-Sekai, fire, Lyuma, Zodiepupper, Cthulhoo\nTags: V-Sekai, VRM, Godot Engine, T-Pose, A-Pose\n\n\n\n\nThe VRM importer and specification in Godot Engine necessitates a T-Pose. However, artists often prefer using an A-Pose as it simplifies body modeling.\n\n\n\nThe issue arises when Blender VRM defaults the skeleton without adjusting the pose.\n\n\n\nHere’s a step-by-step guide to overcome this limitation:\n\nSelect all bones and create an animation pose for A-Pose. (Optional)\nClick on the mirror axis butterfly icon and the x-axis.\nAdjust the shoulder by approximately 15 degrees and position the upper arm to form a T-Pose.\nPosition the legs straight and at shoulder width apart to match the T-Pose.\nSelect all bones again and create an animation pose for T-Pose. (Optional)\n\n\n\n\nThis solution allows artists to continue using their preferred A-Pose for modeling while still meeting the T-Pose requirement of the VRM importer in Godot Engine.\n\n\n\nThe process of manually adjusting the pose from A-Pose to T-Pose can be time-consuming and may require some technical knowledge.\n\n\n\nAt this time, no other alternatives have been pursued.\n\n\n\nThis solution is primarily beneficial for artists who prefer using A-Pose for modeling but need to meet the T-Pose requirement of the VRM importer in Godot Engine.\n\n\n\nYes, this solution was developed by us.\n\n\n\n\nV-Sekai · GitHub - The official GitHub account for the V-Sekai development community, which focuses on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - The GitHub page for the V-Sekai open-source project that brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis article was assisted by AI."
+    "text": "The is core V-Sekai."
   },
   {
-    "objectID": "decisions/20231110-blender-manual-t-pose.html#metadata",
-    "href": "decisions/20231110-blender-manual-t-pose.html#metadata",
-    "title": "Accepted: Overcoming the Blender T-Pose Limitation with Documentation",
+    "objectID": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Polish demo of V-Sekai by making invisible meshes appear via the use of the exporter.",
     "section": "",
-    "text": "Status: Accepted\nDeciders: V-Sekai, fire, Lyuma, Zodiepupper, Cthulhoo\nTags: V-Sekai, VRM, Godot Engine, T-Pose, A-Pose"
+    "text": "Only we can set the initial scene."
   },
   {
-    "objectID": "decisions/20231110-blender-manual-t-pose.html#context",
-    "href": "decisions/20231110-blender-manual-t-pose.html#context",
-    "title": "Accepted: Overcoming the Blender T-Pose Limitation with Documentation",
+    "objectID": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html#references",
+    "href": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html#references",
+    "title": "Proposed: Polish demo of V-Sekai by making invisible meshes appear via the use of the exporter.",
     "section": "",
-    "text": "The VRM importer and specification in Godot Engine necessitates a T-Pose. However, artists often prefer using an A-Pose as it simplifies body modeling."
+    "text": "https://v-sekai.org/"
   },
   {
-    "objectID": "decisions/20231110-blender-manual-t-pose.html#problem",
-    "href": "decisions/20231110-blender-manual-t-pose.html#problem",
-    "title": "Accepted: Overcoming the Blender T-Pose Limitation with Documentation",
+    "objectID": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html#derivative-license",
+    "href": "decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html#derivative-license",
+    "title": "Proposed: Polish demo of V-Sekai by making invisible meshes appear via the use of the exporter.",
     "section": "",
-    "text": "The issue arises when Blender VRM defaults the skeleton without adjusting the pose."
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20231110-blender-manual-t-pose.html#solution",
-    "href": "decisions/20231110-blender-manual-t-pose.html#solution",
-    "title": "Accepted: Overcoming the Blender T-Pose Limitation with Documentation",
+    "objectID": "decisions/20211005-use-materialx-for-asset-interchange.html",
+    "href": "decisions/20211005-use-materialx-for-asset-interchange.html",
+    "title": "Proposed: Use materialx for asset interchange",
     "section": "",
-    "text": "Here’s a step-by-step guide to overcome this limitation:\n\nSelect all bones and create an animation pose for A-Pose. (Optional)\nClick on the mirror axis butterfly icon and the x-axis.\nAdjust the shoulder by approximately 15 degrees and position the upper arm to form a T-Pose.\nPosition the legs straight and at shoulder width apart to match the T-Pose.\nSelect all bones again and create an animation pose for T-Pose. (Optional)"
+    "text": "Proposed: Use materialx for asset interchange\n\nContext and Problem Statement\nUse #materialx for asset interchange\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nI was challenged to assemble a green IKEA chair with #materialx https://github.com/KhronosGroup/3DC-Certification/tree/main/models/GreenChair by humbletim.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n\nbake #materialx\nadd gltf2 extension\ncreate an IO/Blender\ncreate an IO/Godot\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nThis is so complicated.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nI am championing this workflow.\n\n\nReferences\n\nmaterialx.org/\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20231110-blender-manual-t-pose.html#benefits",
-    "href": "decisions/20231110-blender-manual-t-pose.html#benefits",
-    "title": "Accepted: Overcoming the Blender T-Pose Limitation with Documentation",
+    "objectID": "decisions/20230123-player-scripting.html",
+    "href": "decisions/20230123-player-scripting.html",
+    "title": "Proposed: Provide user generated scripting using WasGO",
     "section": "",
-    "text": "This solution allows artists to continue using their preferred A-Pose for modeling while still meeting the T-Pose requirement of the VRM importer in Godot Engine."
+    "text": "Proposed: Provide user generated scripting using WasGO\n\nMetadata\n\nStatus: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nContext and Problem Statement\nWe want to provide user scripting.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nWe want to be able to co simulate scripts across multiple clients without arbitrary remote code execution.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nWasGO, using dynamic call function, and Variant APIs.\n\n\nPositive Consequences\nWe can add interactivity to V-Sekai.\n\n\nNegative Consequences\nWe cannot get other features in.\n\n\nOption graveyard\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nThis adding the ability to use code.\n\n\nIs there a reason why this should be core and done by us?\nUsability is a core feature.\n\n\nReferences\n\nV-Sekai\n\n\n\nLicense of the contribution\nMIT License\n\nCopyright (c) 2018-present SaracenOne\nCopyright (c) 2019-present K. S. Ernest (iFire) Lee (fire)\nCopyright (c) 2020-present Lyuma\nCopyright (c) 2020-present MMMaellon\nCopyright (c) 2022-present See authors.md\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
   },
   {
-    "objectID": "decisions/20231110-blender-manual-t-pose.html#drawbacks",
-    "href": "decisions/20231110-blender-manual-t-pose.html#drawbacks",
-    "title": "Accepted: Overcoming the Blender T-Pose Limitation with Documentation",
+    "objectID": "decisions/20230812-constraint-all-bones.html",
+    "href": "decisions/20230812-constraint-all-bones.html",
+    "title": "Proposed: Constrain the entire Godot Humanoid Skeleton",
     "section": "",
-    "text": "The process of manually adjusting the pose from A-Pose to T-Pose can be time-consuming and may require some technical knowledge."
+    "text": "Status: proposed\nDeciders: V-Sekai, fire\nTags: V-Sekai\n\n\n\n\nThe current Godot humanoid skeleton system lacks proper constraints for all bones, specifically in terms of rotation swing and rotation twist limits. This has led to issues when trying to move parts of the skeleton such as the head or legs towards the torso.\n\n\n\nThe challenge lies in implementing these constraints without causing other issues within the system. Some bones are not solved and should not be constrained, adding complexity to the task.\n\n\n\nThe strategy is to carefully analyze each bone and determine the appropriate constraints. This will involve a combination of swing rotation and twist rotation constraints, depending on the specific bone.\n\n\n\nBy implementing these constraints, we can improve the functionality and reliability of the Godot humanoid skeleton system. This will allow for more realistic movements and prevent system errors when moving certain parts of the skeleton.\n\n\n\nThere may be potential challenges in implementing these constraints, particularly for the unsolved bones. It will require careful testing and adjustment to ensure that the new constraints do not introduce new issues.\n\n\n\nAn alternative would be to leave the system as it is, accepting its limitations. However, this would mean missing out on the potential improvements that could be achieved through this proposal.\n\n\n\nIn some rare cases, the lack of constraints might actually be beneficial, allowing for unusual or exaggerated movements. These cases will need to be considered and potentially addressed separately.\n\n\n\nYes, this change would be implemented in the core system by the V-Sekai team.\n\n\n\n\nV-Sekai\nThis article is assisted by AI."
   },
   {
-    "objectID": "decisions/20231110-blender-manual-t-pose.html#alternatives-not-pursued",
-    "href": "decisions/20231110-blender-manual-t-pose.html#alternatives-not-pursued",
-    "title": "Accepted: Overcoming the Blender T-Pose Limitation with Documentation",
+    "objectID": "decisions/20230812-constraint-all-bones.html#metadata",
+    "href": "decisions/20230812-constraint-all-bones.html#metadata",
+    "title": "Proposed: Constrain the entire Godot Humanoid Skeleton",
     "section": "",
-    "text": "At this time, no other alternatives have been pursued."
+    "text": "Status: proposed\nDeciders: V-Sekai, fire\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20231110-blender-manual-t-pose.html#rare-use-cases",
-    "href": "decisions/20231110-blender-manual-t-pose.html#rare-use-cases",
-    "title": "Accepted: Overcoming the Blender T-Pose Limitation with Documentation",
+    "objectID": "decisions/20230812-constraint-all-bones.html#the-backdrop",
+    "href": "decisions/20230812-constraint-all-bones.html#the-backdrop",
+    "title": "Proposed: Constrain the entire Godot Humanoid Skeleton",
     "section": "",
-    "text": "This solution is primarily beneficial for artists who prefer using A-Pose for modeling but need to meet the T-Pose requirement of the VRM importer in Godot Engine."
+    "text": "The current Godot humanoid skeleton system lacks proper constraints for all bones, specifically in terms of rotation swing and rotation twist limits. This has led to issues when trying to move parts of the skeleton such as the head or legs towards the torso."
   },
   {
-    "objectID": "decisions/20231110-blender-manual-t-pose.html#in-house-solution",
-    "href": "decisions/20231110-blender-manual-t-pose.html#in-house-solution",
-    "title": "Accepted: Overcoming the Blender T-Pose Limitation with Documentation",
+    "objectID": "decisions/20230812-constraint-all-bones.html#the-challenge",
+    "href": "decisions/20230812-constraint-all-bones.html#the-challenge",
+    "title": "Proposed: Constrain the entire Godot Humanoid Skeleton",
     "section": "",
-    "text": "Yes, this solution was developed by us."
+    "text": "The challenge lies in implementing these constraints without causing other issues within the system. Some bones are not solved and should not be constrained, adding complexity to the task."
   },
   {
-    "objectID": "decisions/20231110-blender-manual-t-pose.html#additional-resources",
-    "href": "decisions/20231110-blender-manual-t-pose.html#additional-resources",
-    "title": "Accepted: Overcoming the Blender T-Pose Limitation with Documentation",
+    "objectID": "decisions/20230812-constraint-all-bones.html#the-strategy",
+    "href": "decisions/20230812-constraint-all-bones.html#the-strategy",
+    "title": "Proposed: Constrain the entire Godot Humanoid Skeleton",
     "section": "",
-    "text": "V-Sekai · GitHub - The official GitHub account for the V-Sekai development community, which focuses on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - The GitHub page for the V-Sekai open-source project that brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis article was assisted by AI."
+    "text": "The strategy is to carefully analyze each bone and determine the appropriate constraints. This will involve a combination of swing rotation and twist rotation constraints, depending on the specific bone."
   },
   {
-    "objectID": "decisions/20240217-essential-typle-normalization-form.html",
-    "href": "decisions/20240217-essential-typle-normalization-form.html",
-    "title": "Proposed: Implementation of Essential Tuple Normalization Form (ETNF) for relational databases (rdbms, sql)",
+    "objectID": "decisions/20230812-constraint-all-bones.html#the-upside",
+    "href": "decisions/20230812-constraint-all-bones.html#the-upside",
+    "title": "Proposed: Constrain the entire Godot Humanoid Skeleton",
     "section": "",
-    "text": "V-Sekai is committed to enhancing data integrity, optimizing database performance, and standardizing data storage practices. To achieve these goals, we propose the adoption of the Essential Tuple Normalization Form (ETNF) across our database systems.\n\n\n\nCurrently, V-Sekai’s database systems lack a standardized approach to normalization. This leads to data redundancy, inconsistency, and inefficiencies in data management, which can hamper system performance and scalability.\n\n\n\nWe propose implementing ETNF, a normalization form that strikes an optimal balance between eliminating redundancy and maintaining manageable complexity in database schemas. Positioned between the fourth normal form (4NF) and the fifth normal form (5NF), ETNF provides a sophisticated yet practical approach to database normalization.\n\n\nA relation schema R is in Essential Tuple Normal Form (ETNF) if every tuple in every instance of R is essential. This means that no tuple in the database can be generated from other tuples, thus eliminating redundancy.\nIn mathematical terms, a relation R is in ETNF if and only if it is in Boyce-Codd Normal Form (BCNF) and some component of every explicit join dependency (JD) of R is a superkey. Specifically, for every nontrivial join dependency {R1, R2, …, Rn} that holds over R, the intersection of each pair of Ri and Rj is a superkey for at least one of Ri or Rj.\nThis concept is further illustrated by the theorem stating that if R is a relation schema specified only by functional dependencies (FDs) and join dependencies (JDs), then R is in ETNF if and only if it is in BCNF and some component of every explicit JD of R is a superkey.\nTherefore, ETNF is an effective normalization form that reduces data redundancy while maintaining manageable complexity in database schemas. It provides a balance between the elimination of unnecessary redundancy and the avoidance of extensive decomposition associated with higher normal forms like 5NF.\n\n\nConsider a V-Sekai database table storing information about parts, suppliers, and respective shipments. The table is not normalized and contains redundant data.\n\n\n\nSupplierID\nSupplierName\nPartID\nPartName\nShipmentQuantity\n\n\n\n\nS1\nAlice\nP1\nPart1\n100\n\n\nS1\nAlice\nP2\nPart2\n200\n\n\nS2\nBob\nP1\nPart1\n150\n\n\nS2\nBob\nP3\nPart3\n300\n\n\nS3\nCharlie\nP2\nPart2\n250\n\n\n\nIn this table, SupplierName and PartName are repeated for each SupplierID and PartID, respectively. This redundancy can lead to inconsistencies and anomalies.\n\n\n\nTo normalize the above table into ETNF, we would decompose it into three separate tables: Supplier, Part, and Shipment.\n\n\n\n\n\nSupplierID\nSupplierName\n\n\n\n\nS1\nAlice\n\n\nS2\nBob\n\n\nS3\nCharlie\n\n\n\n\n\n\n\n\n\nPartID\nPartName\n\n\n\n\nP1\nPart1\n\n\nP2\nPart2\n\n\nP3\nPart3\n\n\n\n\n\n\n\n\n\nSupplierID\nPartID\nShipmentQuantity\n\n\n\n\nS1\nP1\n100\n\n\nS1\nP2\n200\n\n\nS2\nP1\n150\n\n\nS2\nP3\n300\n\n\nS3\nP2\n250\n\n\n\nIn these normalized tables, each tuple is essential and there is no redundancy. The SupplierName is not repeated for each shipment from the same supplier, and similarly, the PartName is not repeated for each shipment of the same part. This design adheres to the principles of ETNF, enhancing data integrity and consistency.\n\n\n\n\n\n\nRedundancy Reduction: ETNF effectively reduces data redundancy by ensuring that all data stored in the database is essential and non-repetitive.\nData Integrity and Consistency: By minimizing redundancy, ETNF enhances the integrity and consistency of the database, making data more reliable and accurate.\nBalanced Complexity: ETNF offers a middle ground between 4NF and 5NF, reducing redundancy without the complexity of decomposing relations into smaller, more numerous relations as often required by 5NF.\n\n\n\n\n\nDependency Analysis: The first step involves a detailed analysis of all functional and join dependencies across the database to identify redundancy and determine the scope for normalization to ETNF.\nSchema Evaluation and Restructuring: Evaluate existing database schemas against ETNF criteria, identifying areas where restructuring is required to eliminate redundancy and enhance efficiency.\nPractical Application and Migration: Implement the ETNF principles through schema redesign and careful data migration, ensuring that the transition does not impact data integrity or system availability.\n\n\n\n\n\n\nEnhanced Data Integrity: Implementation of ETNF will significantly improve the integrity and reliability of V-Sekai’s data.\nOptimized Performance: By reducing redundancy, ETNF will streamline data storage and retrieval processes, enhancing overall system performance.\nStrategic Data Management: Adopting ETNF aligns with strategic initiatives for scalable, efficient, and consistent data management practices.\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nA normal form for preventing redundant tuples in relational databases\n\nAI assistant Aria assisted with this article."
+    "text": "By implementing these constraints, we can improve the functionality and reliability of the Godot humanoid skeleton system. This will allow for more realistic movements and prevent system errors when moving certain parts of the skeleton."
   },
   {
-    "objectID": "decisions/20240217-essential-typle-normalization-form.html#context",
-    "href": "decisions/20240217-essential-typle-normalization-form.html#context",
-    "title": "Proposed: Implementation of Essential Tuple Normalization Form (ETNF) for relational databases (rdbms, sql)",
+    "objectID": "decisions/20230812-constraint-all-bones.html#the-downside",
+    "href": "decisions/20230812-constraint-all-bones.html#the-downside",
+    "title": "Proposed: Constrain the entire Godot Humanoid Skeleton",
     "section": "",
-    "text": "V-Sekai is committed to enhancing data integrity, optimizing database performance, and standardizing data storage practices. To achieve these goals, we propose the adoption of the Essential Tuple Normalization Form (ETNF) across our database systems."
+    "text": "There may be potential challenges in implementing these constraints, particularly for the unsolved bones. It will require careful testing and adjustment to ensure that the new constraints do not introduce new issues."
   },
   {
-    "objectID": "decisions/20240217-essential-typle-normalization-form.html#problem-statement",
-    "href": "decisions/20240217-essential-typle-normalization-form.html#problem-statement",
-    "title": "Proposed: Implementation of Essential Tuple Normalization Form (ETNF) for relational databases (rdbms, sql)",
+    "objectID": "decisions/20230812-constraint-all-bones.html#the-road-not-taken",
+    "href": "decisions/20230812-constraint-all-bones.html#the-road-not-taken",
+    "title": "Proposed: Constrain the entire Godot Humanoid Skeleton",
     "section": "",
-    "text": "Currently, V-Sekai’s database systems lack a standardized approach to normalization. This leads to data redundancy, inconsistency, and inefficiencies in data management, which can hamper system performance and scalability."
+    "text": "An alternative would be to leave the system as it is, accepting its limitations. However, this would mean missing out on the potential improvements that could be achieved through this proposal."
   },
   {
-    "objectID": "decisions/20240217-essential-typle-normalization-form.html#proposed-overview-etnf-implementation",
-    "href": "decisions/20240217-essential-typle-normalization-form.html#proposed-overview-etnf-implementation",
-    "title": "Proposed: Implementation of Essential Tuple Normalization Form (ETNF) for relational databases (rdbms, sql)",
+    "objectID": "decisions/20230812-constraint-all-bones.html#the-infrequent-use-case",
+    "href": "decisions/20230812-constraint-all-bones.html#the-infrequent-use-case",
+    "title": "Proposed: Constrain the entire Godot Humanoid Skeleton",
     "section": "",
-    "text": "We propose implementing ETNF, a normalization form that strikes an optimal balance between eliminating redundancy and maintaining manageable complexity in database schemas. Positioned between the fourth normal form (4NF) and the fifth normal form (5NF), ETNF provides a sophisticated yet practical approach to database normalization.\n\n\nA relation schema R is in Essential Tuple Normal Form (ETNF) if every tuple in every instance of R is essential. This means that no tuple in the database can be generated from other tuples, thus eliminating redundancy.\nIn mathematical terms, a relation R is in ETNF if and only if it is in Boyce-Codd Normal Form (BCNF) and some component of every explicit join dependency (JD) of R is a superkey. Specifically, for every nontrivial join dependency {R1, R2, …, Rn} that holds over R, the intersection of each pair of Ri and Rj is a superkey for at least one of Ri or Rj.\nThis concept is further illustrated by the theorem stating that if R is a relation schema specified only by functional dependencies (FDs) and join dependencies (JDs), then R is in ETNF if and only if it is in BCNF and some component of every explicit JD of R is a superkey.\nTherefore, ETNF is an effective normalization form that reduces data redundancy while maintaining manageable complexity in database schemas. It provides a balance between the elimination of unnecessary redundancy and the avoidance of extensive decomposition associated with higher normal forms like 5NF.\n\n\nConsider a V-Sekai database table storing information about parts, suppliers, and respective shipments. The table is not normalized and contains redundant data.\n\n\n\nSupplierID\nSupplierName\nPartID\nPartName\nShipmentQuantity\n\n\n\n\nS1\nAlice\nP1\nPart1\n100\n\n\nS1\nAlice\nP2\nPart2\n200\n\n\nS2\nBob\nP1\nPart1\n150\n\n\nS2\nBob\nP3\nPart3\n300\n\n\nS3\nCharlie\nP2\nPart2\n250\n\n\n\nIn this table, SupplierName and PartName are repeated for each SupplierID and PartID, respectively. This redundancy can lead to inconsistencies and anomalies.\n\n\n\nTo normalize the above table into ETNF, we would decompose it into three separate tables: Supplier, Part, and Shipment.\n\n\n\n\n\nSupplierID\nSupplierName\n\n\n\n\nS1\nAlice\n\n\nS2\nBob\n\n\nS3\nCharlie\n\n\n\n\n\n\n\n\n\nPartID\nPartName\n\n\n\n\nP1\nPart1\n\n\nP2\nPart2\n\n\nP3\nPart3\n\n\n\n\n\n\n\n\n\nSupplierID\nPartID\nShipmentQuantity\n\n\n\n\nS1\nP1\n100\n\n\nS1\nP2\n200\n\n\nS2\nP1\n150\n\n\nS2\nP3\n300\n\n\nS3\nP2\n250\n\n\n\nIn these normalized tables, each tuple is essential and there is no redundancy. The SupplierName is not repeated for each shipment from the same supplier, and similarly, the PartName is not repeated for each shipment of the same part. This design adheres to the principles of ETNF, enhancing data integrity and consistency.\n\n\n\n\n\n\nRedundancy Reduction: ETNF effectively reduces data redundancy by ensuring that all data stored in the database is essential and non-repetitive.\nData Integrity and Consistency: By minimizing redundancy, ETNF enhances the integrity and consistency of the database, making data more reliable and accurate.\nBalanced Complexity: ETNF offers a middle ground between 4NF and 5NF, reducing redundancy without the complexity of decomposing relations into smaller, more numerous relations as often required by 5NF.\n\n\n\n\n\nDependency Analysis: The first step involves a detailed analysis of all functional and join dependencies across the database to identify redundancy and determine the scope for normalization to ETNF.\nSchema Evaluation and Restructuring: Evaluate existing database schemas against ETNF criteria, identifying areas where restructuring is required to eliminate redundancy and enhance efficiency.\nPractical Application and Migration: Implement the ETNF principles through schema redesign and careful data migration, ensuring that the transition does not impact data integrity or system availability."
+    "text": "In some rare cases, the lack of constraints might actually be beneficial, allowing for unusual or exaggerated movements. These cases will need to be considered and potentially addressed separately."
   },
   {
-    "objectID": "decisions/20240217-essential-typle-normalization-form.html#benefits-for-v-sekai",
-    "href": "decisions/20240217-essential-typle-normalization-form.html#benefits-for-v-sekai",
-    "title": "Proposed: Implementation of Essential Tuple Normalization Form (ETNF) for relational databases (rdbms, sql)",
+    "objectID": "decisions/20230812-constraint-all-bones.html#in-core-and-done-by-us",
+    "href": "decisions/20230812-constraint-all-bones.html#in-core-and-done-by-us",
+    "title": "Proposed: Constrain the entire Godot Humanoid Skeleton",
     "section": "",
-    "text": "Enhanced Data Integrity: Implementation of ETNF will significantly improve the integrity and reliability of V-Sekai’s data.\nOptimized Performance: By reducing redundancy, ETNF will streamline data storage and retrieval processes, enhancing overall system performance.\nStrategic Data Management: Adopting ETNF aligns with strategic initiatives for scalable, efficient, and consistent data management practices."
+    "text": "Yes, this change would be implemented in the core system by the V-Sekai team."
   },
   {
-    "objectID": "decisions/20240217-essential-typle-normalization-form.html#further-reading",
-    "href": "decisions/20240217-essential-typle-normalization-form.html#further-reading",
-    "title": "Proposed: Implementation of Essential Tuple Normalization Form (ETNF) for relational databases (rdbms, sql)",
+    "objectID": "decisions/20230812-constraint-all-bones.html#further-reading",
+    "href": "decisions/20230812-constraint-all-bones.html#further-reading",
+    "title": "Proposed: Constrain the entire Godot Humanoid Skeleton",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nA normal form for preventing redundant tuples in relational databases\n\nAI assistant Aria assisted with this article."
+    "text": "V-Sekai\nThis article is assisted by AI."
   },
   {
-    "objectID": "decisions/20240401-shader-graphic.html",
-    "href": "decisions/20240401-shader-graphic.html",
-    "title": "Proposed: Material Shader Graphic Shirt with Sharp Edges",
+    "objectID": "decisions/20230505-consistent-v-sekai-naming.html",
+    "href": "decisions/20230505-consistent-v-sekai-naming.html",
+    "title": "Proposed: Solve a V-Sekai naming convention limitation.",
     "section": "",
-    "text": "In the vibrant and ever-evolving realm of virtual reality, personal expression is paramount. Users crave the ability to showcase their unique style and personality through their avatars. One powerful avenue for this self-expression is through avatar apparel customization. In this scenario, we’re exploring the creation of a virtual shirt adorned with two distinct patterns. These patterns are applied using SVG files that are converted into a signed distance field mask, ensuring the edges remain crisp and sharp.\n\n\n\nAt present, there’s no straightforward method to design a shirt featuring two different patterns using SVG files in MaterialX, while also maintaining sharp pattern edges. This proposal seeks to address and resolve this issue.\n\n\n\nWe can harness the power of MaterialX’s shader graph system to craft a custom shader for our shirt. Here’s a rudimentary sketch of how it might be structured:\n# Import MaterialX library\nimport MaterialX as mx\n\n# Create a new document\ndoc = mx.createDocument()\n\n# Create a new shader graph\nshaderGraph = doc.addNode('shadergraph', 'myShaderGraph', 'surfaceshader')\n\n# Add two image nodes for our SVG patterns\npattern1 = shaderGraph.addInput('pattern1', 'filename')\npattern2 = shaderGraph.addInput('pattern2', 'filename')\n\n# Convert SVGs to signed distance fields for sharp edges\nsdfPattern1 = convertSVGToSDF(pattern1)\nsdfPattern2 = convertSVGToSDF(pattern2)\n\n# Add a mix node to blend the two patterns together\nmix = shaderGraph.addNode('mix', 'mix', 'color3')\nmix.setInputValue('fg', sdfPattern1)\nmix.setInputValue('bg', sdfPattern2)\n\n# Connect the mix node to the shader graph output\nshaderGraph.setOutputValue(mix)\nPlease note, this is a simplified example and may require adjustments based on your project’s specific needs.\n\n\n\nImplementing this feature will empower users with additional options for avatar customization. This could potentially boost user engagement and satisfaction. Moreover, by utilizing signed distance fields, we can guarantee sharp pattern edges, enhancing the visual appeal of the shirt.\n\n\n\nThe primary drawback is that this feature could potentially amplify the complexity of the codebase. It may also necessitate additional resources for implementation and ongoing maintenance.\n\n\n\nAn alternative approach might involve using a different library or tool that already supports this feature. However, this could potentially introduce other challenges such as compatibility issues or increased project complexity.\n\n\n\nThis feature might not see frequent use if the majority of users favor simpler designs for their avatars’ clothing. Nonetheless, it could still prove beneficial for those desiring more advanced customization options.\n\n\n\nThis feature will be developed by the V-Sekai development team and will form an integral part of our project’s core functionality.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
+    "text": "Status: proposed \nDeciders: V-Sekai,fire,\nTags: V-Sekai,chatgpt4,naming conventions,standardization,code organization,documentation,project management,\n\n\n\n\nWe use different kinds of names for V-Sekai, such as v-sekai, V-Sekai, vsk, and v_sekai. It is confusing to find a scheme that fits the various naming conventions. Hyphens are banned in Godot Engine file systems, but allowed in GitHub branch names. We also use the godot_addon convention sometimes. How can we document and unify the naming conventions across different platforms and contexts?\n\n\n\nCreate a standardized naming convention guideline that defines the preferred format for all instances of V-Sekai’s name in code, documentation, and other materials, taking into account the specific requirements and limitations of each platform and context.\n\n\n\n\nDefine the preferred naming convention for V-Sekai in different contexts:\n\nGodot Engine file systems: vsk_default\nGitHub branch names: v-sekai-wasm\nAddon naming: addons/vsk_avatar\nGithub repository names must all be lowercase:\n\nGitHub is case-insensitive: this can result in users or devs inadvertently typing the wrong case in one case\nWindows is case-insensitive, so the above mistake can go unnoticed until the addon is used on a different OS\n\n\nCreate a guideline document outlining the naming convention rules for each context.\nUpdate existing code, documentation, and materials to follow the new naming conventions.\nEnforce the naming conventions in future development and contributions.\n\n# Example of following the naming convention in Godot Engine file system\nvsk_default/core/object.gd\n\n# Example of following the naming convention in GitHub branch names\nv-sekai-wasm\n\n# Example of following the naming convention for addons\naddons/vsk_avatar # in the file system\ngodot_vsk_avatar # on Github\n\n\n\n\nConsistent naming conventions across different platforms and contexts.\nReduced confusion among developers and users.\n\n\n\n\n\nTime and effort required to update existing code and materials to follow the new naming conventions.\n\n\n\n\nDoing nothing is a problem.\n\n\n\nNo, establishing consistent naming conventions requires updating all instances of V-Sekai’s name across the project and cannot be achieved with a simple script.\n\n\n\nYes, maintaining consistent naming conventions is essential for a professional and well-organized project. It will improve the overall quality of the codebase and documentation, making it easier for developers and users to understand and work with V-Sekai.\n\n\n\n\nV-Sekai\ngoblin.tools: https://goblin.tools/\nopenai: https://openai.com/"
   },
   {
-    "objectID": "decisions/20240401-shader-graphic.html#the-context",
-    "href": "decisions/20240401-shader-graphic.html#the-context",
-    "title": "Proposed: Material Shader Graphic Shirt with Sharp Edges",
+    "objectID": "decisions/20230505-consistent-v-sekai-naming.html#metadata",
+    "href": "decisions/20230505-consistent-v-sekai-naming.html#metadata",
+    "title": "Proposed: Solve a V-Sekai naming convention limitation.",
     "section": "",
-    "text": "In the vibrant and ever-evolving realm of virtual reality, personal expression is paramount. Users crave the ability to showcase their unique style and personality through their avatars. One powerful avenue for this self-expression is through avatar apparel customization. In this scenario, we’re exploring the creation of a virtual shirt adorned with two distinct patterns. These patterns are applied using SVG files that are converted into a signed distance field mask, ensuring the edges remain crisp and sharp."
+    "text": "Status: proposed \nDeciders: V-Sekai,fire,\nTags: V-Sekai,chatgpt4,naming conventions,standardization,code organization,documentation,project management,"
   },
   {
-    "objectID": "decisions/20240401-shader-graphic.html#the-problem-statement",
-    "href": "decisions/20240401-shader-graphic.html#the-problem-statement",
-    "title": "Proposed: Material Shader Graphic Shirt with Sharp Edges",
+    "objectID": "decisions/20230505-consistent-v-sekai-naming.html#context-and-problem-statement",
+    "href": "decisions/20230505-consistent-v-sekai-naming.html#context-and-problem-statement",
+    "title": "Proposed: Solve a V-Sekai naming convention limitation.",
     "section": "",
-    "text": "At present, there’s no straightforward method to design a shirt featuring two different patterns using SVG files in MaterialX, while also maintaining sharp pattern edges. This proposal seeks to address and resolve this issue."
+    "text": "We use different kinds of names for V-Sekai, such as v-sekai, V-Sekai, vsk, and v_sekai. It is confusing to find a scheme that fits the various naming conventions. Hyphens are banned in Godot Engine file systems, but allowed in GitHub branch names. We also use the godot_addon convention sometimes. How can we document and unify the naming conventions across different platforms and contexts?"
   },
   {
-    "objectID": "decisions/20240401-shader-graphic.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240401-shader-graphic.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Material Shader Graphic Shirt with Sharp Edges",
+    "objectID": "decisions/20230505-consistent-v-sekai-naming.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20230505-consistent-v-sekai-naming.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: Solve a V-Sekai naming convention limitation.",
     "section": "",
-    "text": "We can harness the power of MaterialX’s shader graph system to craft a custom shader for our shirt. Here’s a rudimentary sketch of how it might be structured:\n# Import MaterialX library\nimport MaterialX as mx\n\n# Create a new document\ndoc = mx.createDocument()\n\n# Create a new shader graph\nshaderGraph = doc.addNode('shadergraph', 'myShaderGraph', 'surfaceshader')\n\n# Add two image nodes for our SVG patterns\npattern1 = shaderGraph.addInput('pattern1', 'filename')\npattern2 = shaderGraph.addInput('pattern2', 'filename')\n\n# Convert SVGs to signed distance fields for sharp edges\nsdfPattern1 = convertSVGToSDF(pattern1)\nsdfPattern2 = convertSVGToSDF(pattern2)\n\n# Add a mix node to blend the two patterns together\nmix = shaderGraph.addNode('mix', 'mix', 'color3')\nmix.setInputValue('fg', sdfPattern1)\nmix.setInputValue('bg', sdfPattern2)\n\n# Connect the mix node to the shader graph output\nshaderGraph.setOutputValue(mix)\nPlease note, this is a simplified example and may require adjustments based on your project’s specific needs."
+    "text": "Create a standardized naming convention guideline that defines the preferred format for all instances of V-Sekai’s name in code, documentation, and other materials, taking into account the specific requirements and limitations of each platform and context."
   },
   {
-    "objectID": "decisions/20240401-shader-graphic.html#the-benefits",
-    "href": "decisions/20240401-shader-graphic.html#the-benefits",
-    "title": "Proposed: Material Shader Graphic Shirt with Sharp Edges",
+    "objectID": "decisions/20230505-consistent-v-sekai-naming.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20230505-consistent-v-sekai-naming.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Solve a V-Sekai naming convention limitation.",
     "section": "",
-    "text": "Implementing this feature will empower users with additional options for avatar customization. This could potentially boost user engagement and satisfaction. Moreover, by utilizing signed distance fields, we can guarantee sharp pattern edges, enhancing the visual appeal of the shirt."
+    "text": "Define the preferred naming convention for V-Sekai in different contexts:\n\nGodot Engine file systems: vsk_default\nGitHub branch names: v-sekai-wasm\nAddon naming: addons/vsk_avatar\nGithub repository names must all be lowercase:\n\nGitHub is case-insensitive: this can result in users or devs inadvertently typing the wrong case in one case\nWindows is case-insensitive, so the above mistake can go unnoticed until the addon is used on a different OS\n\n\nCreate a guideline document outlining the naming convention rules for each context.\nUpdate existing code, documentation, and materials to follow the new naming conventions.\nEnforce the naming conventions in future development and contributions.\n\n# Example of following the naming convention in Godot Engine file system\nvsk_default/core/object.gd\n\n# Example of following the naming convention in GitHub branch names\nv-sekai-wasm\n\n# Example of following the naming convention for addons\naddons/vsk_avatar # in the file system\ngodot_vsk_avatar # on Github"
   },
   {
-    "objectID": "decisions/20240401-shader-graphic.html#the-downsides",
-    "href": "decisions/20240401-shader-graphic.html#the-downsides",
-    "title": "Proposed: Material Shader Graphic Shirt with Sharp Edges",
+    "objectID": "decisions/20230505-consistent-v-sekai-naming.html#positive-consequences",
+    "href": "decisions/20230505-consistent-v-sekai-naming.html#positive-consequences",
+    "title": "Proposed: Solve a V-Sekai naming convention limitation.",
     "section": "",
-    "text": "The primary drawback is that this feature could potentially amplify the complexity of the codebase. It may also necessitate additional resources for implementation and ongoing maintenance."
+    "text": "Consistent naming conventions across different platforms and contexts.\nReduced confusion among developers and users."
   },
   {
-    "objectID": "decisions/20240401-shader-graphic.html#the-road-not-taken",
-    "href": "decisions/20240401-shader-graphic.html#the-road-not-taken",
-    "title": "Proposed: Material Shader Graphic Shirt with Sharp Edges",
+    "objectID": "decisions/20230505-consistent-v-sekai-naming.html#negative-consequences",
+    "href": "decisions/20230505-consistent-v-sekai-naming.html#negative-consequences",
+    "title": "Proposed: Solve a V-Sekai naming convention limitation.",
     "section": "",
-    "text": "An alternative approach might involve using a different library or tool that already supports this feature. However, this could potentially introduce other challenges such as compatibility issues or increased project complexity."
+    "text": "Time and effort required to update existing code and materials to follow the new naming conventions."
   },
   {
-    "objectID": "decisions/20240401-shader-graphic.html#the-infrequent-use-case",
-    "href": "decisions/20240401-shader-graphic.html#the-infrequent-use-case",
-    "title": "Proposed: Material Shader Graphic Shirt with Sharp Edges",
+    "objectID": "decisions/20230505-consistent-v-sekai-naming.html#option-graveyard",
+    "href": "decisions/20230505-consistent-v-sekai-naming.html#option-graveyard",
+    "title": "Proposed: Solve a V-Sekai naming convention limitation.",
     "section": "",
-    "text": "This feature might not see frequent use if the majority of users favor simpler designs for their avatars’ clothing. Nonetheless, it could still prove beneficial for those desiring more advanced customization options."
+    "text": "Doing nothing is a problem."
   },
   {
-    "objectID": "decisions/20240401-shader-graphic.html#in-core-and-done-by-us",
-    "href": "decisions/20240401-shader-graphic.html#in-core-and-done-by-us",
-    "title": "Proposed: Material Shader Graphic Shirt with Sharp Edges",
+    "objectID": "decisions/20230505-consistent-v-sekai-naming.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230505-consistent-v-sekai-naming.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Solve a V-Sekai naming convention limitation.",
     "section": "",
-    "text": "This feature will be developed by the V-Sekai development team and will form an integral part of our project’s core functionality."
+    "text": "No, establishing consistent naming conventions requires updating all instances of V-Sekai’s name across the project and cannot be achieved with a simple script."
   },
   {
-    "objectID": "decisions/20240401-shader-graphic.html#status",
-    "href": "decisions/20240401-shader-graphic.html#status",
-    "title": "Proposed: Material Shader Graphic Shirt with Sharp Edges",
+    "objectID": "decisions/20230505-consistent-v-sekai-naming.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230505-consistent-v-sekai-naming.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Solve a V-Sekai naming convention limitation.",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "Yes, maintaining consistent naming conventions is essential for a professional and well-organized project. It will improve the overall quality of the codebase and documentation, making it easier for developers and users to understand and work with V-Sekai."
   },
   {
-    "objectID": "decisions/20240401-shader-graphic.html#decision-makers",
-    "href": "decisions/20240401-shader-graphic.html#decision-makers",
-    "title": "Proposed: Material Shader Graphic Shirt with Sharp Edges",
+    "objectID": "decisions/20230505-consistent-v-sekai-naming.html#references",
+    "href": "decisions/20230505-consistent-v-sekai-naming.html#references",
+    "title": "Proposed: Solve a V-Sekai naming convention limitation.",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "V-Sekai\ngoblin.tools: https://goblin.tools/\nopenai: https://openai.com/"
   },
   {
-    "objectID": "decisions/20240401-shader-graphic.html#tags",
-    "href": "decisions/20240401-shader-graphic.html#tags",
-    "title": "Proposed: Material Shader Graphic Shirt with Sharp Edges",
+    "objectID": "decisions/20231209-appium-testing-fbx-to-gltf.html",
+    "href": "decisions/20231209-appium-testing-fbx-to-gltf.html",
+    "title": "Proposed: Appium Testing for Windows 11",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nIn the realm of game development, providing a seamless user experience across various platforms is crucial. This necessitates the implementation of effective testing methodologies.\n\n\n\nThe primary challenge we face is the establishment of a robust testing framework that ensures cross-platform compatibility. Our focus is particularly on ensuring compatibility with the VR compatible desktop mode on Windows 11.\n\n\n\nTo address this problem, we propose the automation of the testing process using Appium. A significant part of this strategy involves the conversion of FBX files, which are commonly used formats for 3D models and animations, into GLB format.\n\n\n\nThis strategy promises to ensure a high-quality gaming experience.\n\n\n\nIt may require substantial resources and could potentially present unforeseen challenges.\n\n\n\nWe have considered other testing frameworks, but our proposed strategy with Appium offers the best balance between effectiveness and efficiency.\n\n\n\nOur strategy might not cover infrequent or edge cases in game development. However, these will be identified and addressed as they arise.\n\n\n\nYes, this strategy is core to our project and will be implemented by our team.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAssisted by Aria, an AI assistant."
   },
   {
-    "objectID": "decisions/20240401-shader-graphic.html#further-reading",
-    "href": "decisions/20240401-shader-graphic.html#further-reading",
-    "title": "Proposed: Material Shader Graphic Shirt with Sharp Edges",
+    "objectID": "decisions/20231209-appium-testing-fbx-to-gltf.html#metadata",
+    "href": "decisions/20231209-appium-testing-fbx-to-gltf.html#metadata",
+    "title": "Proposed: Appium Testing for Windows 11",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20230516-v-sekai-roadmap.html",
-    "href": "decisions/20230516-v-sekai-roadmap.html",
-    "title": "Superseded: V-Sekai Roadmap and Goals 2023-05-16",
+    "objectID": "decisions/20231209-appium-testing-fbx-to-gltf.html#the-backdrop",
+    "href": "decisions/20231209-appium-testing-fbx-to-gltf.html#the-backdrop",
+    "title": "Proposed: Appium Testing for Windows 11",
     "section": "",
-    "text": "Superseded: V-Sekai Roadmap and Goals 2023-05-16\n\nMetadata\n\nStatus: superseded by 20230519-v-sekai-roadmap.md \nDeciders: V-Sekai,fire,lyuma,\nTags: V-Sekai,chatgpt4 summary,\n\n\n\nContext and Problem Statement\nWhat is the V-Sekai Roadmap and Goals?\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nThe roadmap presented here is short-term.\n\n\nDescribe how your proposal will work with code, pseudo-code, mock-ups, or diagrams\ngraph LR\n  subgraph Short Term\n    A[May 16th, 2023] --&gt; B[Solving SkeletonIK3D before May 30th. Will literally debug the two implementations in lockstep.]\n    B --&gt; C[Assist Tokageit with Godot Engine 4.1 features before May 30th feature freeze]\n    B --&gt; D[Assist Godot Engine 4.1 features before May 30th feature freeze]\n    C --&gt; E\n    D --&gt; E[Vrm upload to the asset library after May 30th, 2023]\n    E --&gt; F[Unidot fix import bugs that blocked assets import]\n    F --&gt; G[Unidot Unity Import upload to the asset library after May 30th, 2023]\n    G --&gt; H[Implement onevoip]\n  end\n\n\nPositive Consequences\nWe can create V-Sekai easier.\n\n\nNegative Consequences\nOverhead might be hard.\n\n\nOption graveyard\n\nImplementing a custom voice chat solution instead of using onevoip\nWaiting for Godot Engine 4.2 instead of assisting with 4.1 features\nIgnoring SkeletonIK3D issues and focusing on other aspects\n\n\n\nIf this enhancement will be used infrequently, can it be worked around with a few lines of script?\nNo. This is a process.\n\n\nIs there a reason why this should be core and done by us?\nThis is a core process for V-Sekai.\n\n\nReferences\n\nV-Sekai"
+    "text": "In the realm of game development, providing a seamless user experience across various platforms is crucial. This necessitates the implementation of effective testing methodologies."
   },
   {
-    "objectID": "decisions/20210528-trial-install-of-gravity-for-kubernetes.html",
-    "href": "decisions/20210528-trial-install-of-gravity-for-kubernetes.html",
-    "title": "Proposed: Trial install of Gravity for Kubernetes",
+    "objectID": "decisions/20231209-appium-testing-fbx-to-gltf.html#the-challenge",
+    "href": "decisions/20231209-appium-testing-fbx-to-gltf.html#the-challenge",
+    "title": "Proposed: Appium Testing for Windows 11",
     "section": "",
-    "text": "Status: rejected\n\n\n\nGRAVITY IS EOL.\nWe have trouble installing Kubernetes.\nIt is difficult to use Kubernetes because of at least these reasons. Networking is hard, storage creation is hard and the number of steps is not split between config and install.\n\n\n\nGravity claims to be a easy to prepare system for preinstalled and airgapped Kubernetes systems.\n\n\n\nCreate a prototype for a toy problem.\nThe toy problem is serving the shader motion html/js static #website as a Kubernetes application.\nEvaluate the complexity.\n\n\n\n\nIncrease quality of life\nEasier distributon\n\n\n\n\n\nAnother layer of complexity\n\n\n\n\nKubernetes is a massive project.\n\n\n\nThis is an attempt to use off the shelf tooling.\n\n\n\n\nhttps://gravitational.com/\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "The primary challenge we face is the establishment of a robust testing framework that ensures cross-platform compatibility. Our focus is particularly on ensuring compatibility with the VR compatible desktop mode on Windows 11."
   },
   {
-    "objectID": "decisions/20210528-trial-install-of-gravity-for-kubernetes.html#context-and-problem-statement",
-    "href": "decisions/20210528-trial-install-of-gravity-for-kubernetes.html#context-and-problem-statement",
-    "title": "Proposed: Trial install of Gravity for Kubernetes",
+    "objectID": "decisions/20231209-appium-testing-fbx-to-gltf.html#the-strategy",
+    "href": "decisions/20231209-appium-testing-fbx-to-gltf.html#the-strategy",
+    "title": "Proposed: Appium Testing for Windows 11",
     "section": "",
-    "text": "GRAVITY IS EOL.\nWe have trouble installing Kubernetes.\nIt is difficult to use Kubernetes because of at least these reasons. Networking is hard, storage creation is hard and the number of steps is not split between config and install."
+    "text": "To address this problem, we propose the automation of the testing process using Appium. A significant part of this strategy involves the conversion of FBX files, which are commonly used formats for 3D models and animations, into GLB format."
   },
   {
-    "objectID": "decisions/20210528-trial-install-of-gravity-for-kubernetes.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20210528-trial-install-of-gravity-for-kubernetes.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: Trial install of Gravity for Kubernetes",
+    "objectID": "decisions/20231209-appium-testing-fbx-to-gltf.html#the-upside",
+    "href": "decisions/20231209-appium-testing-fbx-to-gltf.html#the-upside",
+    "title": "Proposed: Appium Testing for Windows 11",
     "section": "",
-    "text": "Gravity claims to be a easy to prepare system for preinstalled and airgapped Kubernetes systems."
+    "text": "This strategy promises to ensure a high-quality gaming experience."
   },
   {
-    "objectID": "decisions/20210528-trial-install-of-gravity-for-kubernetes.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-andor-diagrams",
-    "href": "decisions/20210528-trial-install-of-gravity-for-kubernetes.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-andor-diagrams",
-    "title": "Proposed: Trial install of Gravity for Kubernetes",
+    "objectID": "decisions/20231209-appium-testing-fbx-to-gltf.html#the-downside",
+    "href": "decisions/20231209-appium-testing-fbx-to-gltf.html#the-downside",
+    "title": "Proposed: Appium Testing for Windows 11",
     "section": "",
-    "text": "Create a prototype for a toy problem.\nThe toy problem is serving the shader motion html/js static #website as a Kubernetes application.\nEvaluate the complexity."
+    "text": "It may require substantial resources and could potentially present unforeseen challenges."
   },
   {
-    "objectID": "decisions/20210528-trial-install-of-gravity-for-kubernetes.html#positive-consequences",
-    "href": "decisions/20210528-trial-install-of-gravity-for-kubernetes.html#positive-consequences",
-    "title": "Proposed: Trial install of Gravity for Kubernetes",
+    "objectID": "decisions/20231209-appium-testing-fbx-to-gltf.html#the-road-not-taken",
+    "href": "decisions/20231209-appium-testing-fbx-to-gltf.html#the-road-not-taken",
+    "title": "Proposed: Appium Testing for Windows 11",
     "section": "",
-    "text": "Increase quality of life\nEasier distributon"
+    "text": "We have considered other testing frameworks, but our proposed strategy with Appium offers the best balance between effectiveness and efficiency."
   },
   {
-    "objectID": "decisions/20210528-trial-install-of-gravity-for-kubernetes.html#negative-consequences",
-    "href": "decisions/20210528-trial-install-of-gravity-for-kubernetes.html#negative-consequences",
-    "title": "Proposed: Trial install of Gravity for Kubernetes",
+    "objectID": "decisions/20231209-appium-testing-fbx-to-gltf.html#the-infrequent-use-case",
+    "href": "decisions/20231209-appium-testing-fbx-to-gltf.html#the-infrequent-use-case",
+    "title": "Proposed: Appium Testing for Windows 11",
     "section": "",
-    "text": "Another layer of complexity"
+    "text": "Our strategy might not cover infrequent or edge cases in game development. However, these will be identified and addressed as they arise."
   },
   {
-    "objectID": "decisions/20210528-trial-install-of-gravity-for-kubernetes.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20210528-trial-install-of-gravity-for-kubernetes.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Trial install of Gravity for Kubernetes",
+    "objectID": "decisions/20231209-appium-testing-fbx-to-gltf.html#in-core-and-done-by-us",
+    "href": "decisions/20231209-appium-testing-fbx-to-gltf.html#in-core-and-done-by-us",
+    "title": "Proposed: Appium Testing for Windows 11",
     "section": "",
-    "text": "Kubernetes is a massive project."
+    "text": "Yes, this strategy is core to our project and will be implemented by our team."
   },
   {
-    "objectID": "decisions/20210528-trial-install-of-gravity-for-kubernetes.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20210528-trial-install-of-gravity-for-kubernetes.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Trial install of Gravity for Kubernetes",
+    "objectID": "decisions/20231209-appium-testing-fbx-to-gltf.html#further-reading",
+    "href": "decisions/20231209-appium-testing-fbx-to-gltf.html#further-reading",
+    "title": "Proposed: Appium Testing for Windows 11",
     "section": "",
-    "text": "This is an attempt to use off the shelf tooling."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAssisted by Aria, an AI assistant."
   },
   {
-    "objectID": "decisions/20210528-trial-install-of-gravity-for-kubernetes.html#references",
-    "href": "decisions/20210528-trial-install-of-gravity-for-kubernetes.html#references",
-    "title": "Proposed: Trial install of Gravity for Kubernetes",
+    "objectID": "decisions/20220224-v-sekai-version-two-plan.html",
+    "href": "decisions/20220224-v-sekai-version-two-plan.html",
+    "title": "Superseded: Planning V-Sekai Version 2 on 2022-02-24",
     "section": "",
-    "text": "https://gravitational.com/"
+    "text": "Status: superseded by 20220228-v-sekai-version-three-plan.md \nDeciders: V-Sekai,ifire,lyuma,\nTags: V-Sekai,\n\n\n\nKnow where we’re going by describing what we want.\n\n\n\nProposed mission and a list of tasks.\n\n\n\n\n\n\nGodot Engine pull requests.\n\n\n\n\n\nOne gitlab repo with source assets? (sky celebration and sponza).\n\n\nThe ability to upload maps and avatars standalone via a SDK (set of submodules?) https://github.com/V-Sekai/vsk_sdk.\n\nBeing able to enter a vsk map ∀ maps (mvp = 1 map).\nEnter a vsk map with an entity in it (upload sky celebration OR upload sponza with one beachball).\n\nVSK_map source asset repositories\nLyuma will make a new github repo V-Sekai/vrm_submodule - we need a script for updating all submodules to the latest on a given branch.\nVSK_map source asset repositories\nI think vsk_sdk should only be submodules, no assets.\nWe can git rebase -i to remove the binary assets from it.\ngit merge to install the vsk_sdk into another project (such as gitlab). we need to look if git subtree supports .gitmodules and we can use it if it does.\nmake vsk_sdk the head for all of the sdk related submodules. do our development there and commit submodules regularly.\nIn groups project, pretend we delete all submodules in vsk_sdk. Then git merge vsk_sdk/main to bring in the submodules from that repo.\nEvery time we update vsk_sdk, do a git merge into groups and our source asset repo with sponza etc.\nVSK_map source asset repositories\n\nDon’t save .scn assets in git.\n\nno GLB.\nblend files ~10MB ok. &gt; 100MB let’s either use GitLab LFS or something else.\nEvaluate https://dvc.org/\n\n\n\n\nBeing able to have our group of people join and communicate. (godot speech).\n\n\nPorting C++ was discussed as a way forward to make it easier to debug\n\n\nVR support (openxr).\nInteracting with objects in desktop mode is important so that we can test easier.\nInteracting with objects in vr.\nScripting (wasgo).\nNetwork server to support 1000.\n\n\n\n\n\nGain clarity of mission.\n\n\n\n\nThe cost of overhead.\n\n\n\n\n\nOption: Status quo. \nRejection Reason: Complete the wrong thing. \n\n\n\n\nThis is a planning document.\n\n\n\nWe know what we want to do.\n\n\n\n\nNone\n\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20210528-trial-install-of-gravity-for-kubernetes.html#derivative-license",
-    "href": "decisions/20210528-trial-install-of-gravity-for-kubernetes.html#derivative-license",
-    "title": "Proposed: Trial install of Gravity for Kubernetes",
+    "objectID": "decisions/20220224-v-sekai-version-two-plan.html#context-and-problem-statement",
+    "href": "decisions/20220224-v-sekai-version-two-plan.html#context-and-problem-statement",
+    "title": "Superseded: Planning V-Sekai Version 2 on 2022-02-24",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Know where we’re going by describing what we want."
   },
   {
-    "objectID": "decisions/20221214-powershell-autocomplete-use-right-arrow.html",
-    "href": "decisions/20221214-powershell-autocomplete-use-right-arrow.html",
-    "title": "Proposed: Powershell autocomplete uses right arrow",
+    "objectID": "decisions/20220224-v-sekai-version-two-plan.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20220224-v-sekai-version-two-plan.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Superseded: Planning V-Sekai Version 2 on 2022-02-24",
     "section": "",
-    "text": "Status: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nPowershell was updated and there is auto complete. However, the exact prediction command is unknown.\n\n\n\nDocument that powershell autocomplete uses the right arrow.\n\n\n\nWrite down that right arrow completes the prediction.\n\n\n\nCan auto complete.\n\n\n\nDocumentation is work.\n\n\n\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\n\nNone.\n\n\n\nI wanted to write this down and it’s not a core thing.\n\n\n\n\nV-Sekai\nhttps://mnaoumov.wordpress.com/2022/11/21/powershell-predictive-intellisense/\n\n\n\n\nMIT License\n\nCopyright (c) 2019-2022 K. S. Ernest (iFire) Lee (fire)\nCopyright (c) 2022 V-Sekai Contributors\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
+    "text": "Proposed mission and a list of tasks."
   },
   {
-    "objectID": "decisions/20221214-powershell-autocomplete-use-right-arrow.html#context-and-problem-statement",
-    "href": "decisions/20221214-powershell-autocomplete-use-right-arrow.html#context-and-problem-statement",
-    "title": "Proposed: Powershell autocomplete uses right arrow",
+    "objectID": "decisions/20220224-v-sekai-version-two-plan.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20220224-v-sekai-version-two-plan.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Superseded: Planning V-Sekai Version 2 on 2022-02-24",
     "section": "",
-    "text": "Powershell was updated and there is auto complete. However, the exact prediction command is unknown."
+    "text": "Godot Engine pull requests.\n\n\n\n\n\nOne gitlab repo with source assets? (sky celebration and sponza).\n\n\nThe ability to upload maps and avatars standalone via a SDK (set of submodules?) https://github.com/V-Sekai/vsk_sdk.\n\nBeing able to enter a vsk map ∀ maps (mvp = 1 map).\nEnter a vsk map with an entity in it (upload sky celebration OR upload sponza with one beachball).\n\nVSK_map source asset repositories\nLyuma will make a new github repo V-Sekai/vrm_submodule - we need a script for updating all submodules to the latest on a given branch.\nVSK_map source asset repositories\nI think vsk_sdk should only be submodules, no assets.\nWe can git rebase -i to remove the binary assets from it.\ngit merge to install the vsk_sdk into another project (such as gitlab). we need to look if git subtree supports .gitmodules and we can use it if it does.\nmake vsk_sdk the head for all of the sdk related submodules. do our development there and commit submodules regularly.\nIn groups project, pretend we delete all submodules in vsk_sdk. Then git merge vsk_sdk/main to bring in the submodules from that repo.\nEvery time we update vsk_sdk, do a git merge into groups and our source asset repo with sponza etc.\nVSK_map source asset repositories\n\nDon’t save .scn assets in git.\n\nno GLB.\nblend files ~10MB ok. &gt; 100MB let’s either use GitLab LFS or something else.\nEvaluate https://dvc.org/\n\n\n\n\nBeing able to have our group of people join and communicate. (godot speech).\n\n\nPorting C++ was discussed as a way forward to make it easier to debug\n\n\nVR support (openxr).\nInteracting with objects in desktop mode is important so that we can test easier.\nInteracting with objects in vr.\nScripting (wasgo).\nNetwork server to support 1000."
   },
   {
-    "objectID": "decisions/20221214-powershell-autocomplete-use-right-arrow.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20221214-powershell-autocomplete-use-right-arrow.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: Powershell autocomplete uses right arrow",
+    "objectID": "decisions/20220224-v-sekai-version-two-plan.html#positive-consequences",
+    "href": "decisions/20220224-v-sekai-version-two-plan.html#positive-consequences",
+    "title": "Superseded: Planning V-Sekai Version 2 on 2022-02-24",
     "section": "",
-    "text": "Document that powershell autocomplete uses the right arrow."
+    "text": "Gain clarity of mission."
   },
   {
-    "objectID": "decisions/20221214-powershell-autocomplete-use-right-arrow.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20221214-powershell-autocomplete-use-right-arrow.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Powershell autocomplete uses right arrow",
+    "objectID": "decisions/20220224-v-sekai-version-two-plan.html#negative-consequences",
+    "href": "decisions/20220224-v-sekai-version-two-plan.html#negative-consequences",
+    "title": "Superseded: Planning V-Sekai Version 2 on 2022-02-24",
     "section": "",
-    "text": "Write down that right arrow completes the prediction."
+    "text": "The cost of overhead."
   },
   {
-    "objectID": "decisions/20221214-powershell-autocomplete-use-right-arrow.html#positive-consequences",
-    "href": "decisions/20221214-powershell-autocomplete-use-right-arrow.html#positive-consequences",
-    "title": "Proposed: Powershell autocomplete uses right arrow",
+    "objectID": "decisions/20220224-v-sekai-version-two-plan.html#option-graveyard",
+    "href": "decisions/20220224-v-sekai-version-two-plan.html#option-graveyard",
+    "title": "Superseded: Planning V-Sekai Version 2 on 2022-02-24",
     "section": "",
-    "text": "Can auto complete."
+    "text": "Option: Status quo. \nRejection Reason: Complete the wrong thing."
   },
   {
-    "objectID": "decisions/20221214-powershell-autocomplete-use-right-arrow.html#negative-consequences",
-    "href": "decisions/20221214-powershell-autocomplete-use-right-arrow.html#negative-consequences",
-    "title": "Proposed: Powershell autocomplete uses right arrow",
+    "objectID": "decisions/20220224-v-sekai-version-two-plan.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20220224-v-sekai-version-two-plan.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Superseded: Planning V-Sekai Version 2 on 2022-02-24",
     "section": "",
-    "text": "Documentation is work."
+    "text": "This is a planning document."
   },
   {
-    "objectID": "decisions/20221214-powershell-autocomplete-use-right-arrow.html#option-graveyard",
-    "href": "decisions/20221214-powershell-autocomplete-use-right-arrow.html#option-graveyard",
-    "title": "Proposed: Powershell autocomplete uses right arrow",
+    "objectID": "decisions/20220224-v-sekai-version-two-plan.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20220224-v-sekai-version-two-plan.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Superseded: Planning V-Sekai Version 2 on 2022-02-24",
     "section": "",
-    "text": "Option: The status quo. \nRejection Reason: This solves nothing."
+    "text": "We know what we want to do."
   },
   {
-    "objectID": "decisions/20221214-powershell-autocomplete-use-right-arrow.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20221214-powershell-autocomplete-use-right-arrow.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Powershell autocomplete uses right arrow",
+    "objectID": "decisions/20220224-v-sekai-version-two-plan.html#references",
+    "href": "decisions/20220224-v-sekai-version-two-plan.html#references",
+    "title": "Superseded: Planning V-Sekai Version 2 on 2022-02-24",
     "section": "",
-    "text": "None."
+    "text": "None"
   },
   {
-    "objectID": "decisions/20221214-powershell-autocomplete-use-right-arrow.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20221214-powershell-autocomplete-use-right-arrow.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Powershell autocomplete uses right arrow",
+    "objectID": "decisions/20220224-v-sekai-version-two-plan.html#derivative-license",
+    "href": "decisions/20220224-v-sekai-version-two-plan.html#derivative-license",
+    "title": "Superseded: Planning V-Sekai Version 2 on 2022-02-24",
     "section": "",
-    "text": "I wanted to write this down and it’s not a core thing."
+    "text": "Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20221214-powershell-autocomplete-use-right-arrow.html#references",
-    "href": "decisions/20221214-powershell-autocomplete-use-right-arrow.html#references",
-    "title": "Proposed: Powershell autocomplete uses right arrow",
+    "objectID": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html",
+    "href": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html",
+    "title": "Proposed: Procedure to unmerge and then merge solves a V-Sekai source code broken tree",
     "section": "",
-    "text": "V-Sekai\nhttps://mnaoumov.wordpress.com/2022/11/21/powershell-predictive-intellisense/"
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nThe V-Sekai source code tree has been broken due to an unsuccessful merge. This has resulted in a halt in the development process, causing delays in project timelines.\n\n\n\nThe main challenge is to unmerge the broken tree and then successfully merge it again. This requires careful analysis of the code and understanding the root cause of the initial failed merge.\n\n\n\nWe use a tool called Git Assembly which makes reapplying branches on master easy. Here’s the strategy:\n\nIdentify the commit hash where the merge went wrong.\nRemove the item from the Git Assembler.\nAnalyze the code and identify the conflicts that caused the merge to fail.\nResolve the conflicts manually.\nFix the branch.\nReapply the branch on master using Git Assembly.\n\n\n\n\nBy following this strategy, we can potentially fix the broken source code tree without losing any significant work. This will allow us to resume the development process and meet our project deadlines.\n\n\n\nThe process of unmerging and merging can be time-consuming and complex. If not done correctly, it may lead to further issues in the codebase.\n\n\n\nAn alternative approach could have been to abandon the current branch and start a new one from the last known good state. However, this would mean losing all the changes made after the last good state.\n\n\n\nThis procedure is not commonly used as merges usually go smoothly. It’s only needed when a merge results in a broken source code tree.\n\n\n\nYes, this procedure is core to our operations and is performed by our team.\n\n\n\n\nV-Sekai\nThis article is assisted by AI."
   },
   {
-    "objectID": "decisions/20221214-powershell-autocomplete-use-right-arrow.html#license-of-the-contribution",
-    "href": "decisions/20221214-powershell-autocomplete-use-right-arrow.html#license-of-the-contribution",
-    "title": "Proposed: Powershell autocomplete uses right arrow",
+    "objectID": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html#metadata",
+    "href": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html#metadata",
+    "title": "Proposed: Procedure to unmerge and then merge solves a V-Sekai source code broken tree",
     "section": "",
-    "text": "MIT License\n\nCopyright (c) 2019-2022 K. S. Ernest (iFire) Lee (fire)\nCopyright (c) 2022 V-Sekai Contributors\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20210523-retarget-motion-for-vrm-type-models.html",
-    "href": "decisions/20210523-retarget-motion-for-vrm-type-models.html",
-    "title": "Proposed: Retarget VRM Motion Blender Workflow",
+    "objectID": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html#the-backdrop",
+    "href": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html#the-backdrop",
+    "title": "Proposed: Procedure to unmerge and then merge solves a V-Sekai source code broken tree",
     "section": "",
-    "text": "We need to retarget motion for VRM type models.\nThis is a lengthy offline process to retarget other motions to VRM type models.\n\n\n\nUse Blender to retarget t-posed characters.\n\n\n\nInputs: bvh + t-pose avatar\nOutput: glb w/retargetted animation\n\n\n\n\nBlender v2.91 or v2.92 (may work with other versions)\nBlender Add-On: skeletal-motion-retarget-blender\n\nDownload .zip\nUse Blender Edit =&gt; Preferences, Add-ons, Install that zip\nCheck the box for the new install an add-on to activate\n\n(optional) if using a VRM avatar Blender Add-On: saturday06/VRM_Addon_for_Blender\n\nDownload .zip\nUse Blender Edit =&gt; Preferences, Add-ons, Install that zip\nCheck the box for the newly install an add-on to activate\n\n\n\n\n\n\n\nHave a rigged, T-Pose humanoid avatar\nStart a new scene?\n\nUnder the Scene Settings property panel, set Frame Rate to 30 fps\n(or you may want to match your .mp4 frame rate used during capture)\n\nImport your avatar model\n\nif using a VRM avatar, be sure to use Import VRM (otherwise, retargeting may not work!)\n\nImport the generated BVH. In the Animation section, enable the following options\n\nScale FPS\nScene Duration\n\nUse the Pose Transfer tab (vertical tab part of the “N” options panel?)\n\nSource: the imported BVH armature\nTarget: the imported avatar armature\nClick the Rebuild Bone List\n\nmanually map over any bones not automatically mapped\neg: LeftLowerArm =&gt; “Left elbow”\nnote: it is possible to save your mapping to .json and reuse\n\nClick Retarget Animation\n\nretargeting may take several minutes\n\n\nVerify retargeting by playing the animation via the Blender play button\nExport the scene as a .glb (using default settings)\n\n\n\n\nQ: Retargeted animation seems to have legs crossed / backwards\nA: This can happen if you import a VRM avatar as a .gltf (re-import using the VRM importer add-on)\nQ: Legs/arms bend unnaturally\nA: Check the armature bone name mappings\n\nat most, each target bone name should appear once\nleave BVH joints not present in your avatar blank\n\n\n\n\nThanks to humbletim for being the scribe\nThanks to lyuma for being test pilot flying these steps\n\n\n\n\nHave a generally robust process of retargeting motions to VRM-type models.\n\n\n\n\n\nOnly VRM\nMMD does not work.\n\n\n\n\n\nList the reasons for the rejection: (the Bad traits)\n\nProprietary Online Service\nBlackbox technology\n\n\n\n\nMotion retargeting is not trivial offline or online.\n\n\n\nWe need motions for our character controller without using an off-the-shelf black box solution.\n\n\n\n\nhttps://www.blender.org/\nhttps://hackmd.io/EmOAt375S8KFqaNdPDJCXQ\nhttps://github.com/V-Sekai/V-Sekai-Blender-tools/tree/main/addons/blender-skeletal-motion-animate\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "The V-Sekai source code tree has been broken due to an unsuccessful merge. This has resulted in a halt in the development process, causing delays in project timelines."
   },
   {
-    "objectID": "decisions/20210523-retarget-motion-for-vrm-type-models.html#context-and-problem-statement",
-    "href": "decisions/20210523-retarget-motion-for-vrm-type-models.html#context-and-problem-statement",
-    "title": "Proposed: Retarget VRM Motion Blender Workflow",
+    "objectID": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html#the-challenge",
+    "href": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html#the-challenge",
+    "title": "Proposed: Procedure to unmerge and then merge solves a V-Sekai source code broken tree",
     "section": "",
-    "text": "We need to retarget motion for VRM type models.\nThis is a lengthy offline process to retarget other motions to VRM type models."
+    "text": "The main challenge is to unmerge the broken tree and then successfully merge it again. This requires careful analysis of the code and understanding the root cause of the initial failed merge."
   },
   {
-    "objectID": "decisions/20210523-retarget-motion-for-vrm-type-models.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20210523-retarget-motion-for-vrm-type-models.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: Retarget VRM Motion Blender Workflow",
+    "objectID": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html#the-strategy",
+    "href": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html#the-strategy",
+    "title": "Proposed: Procedure to unmerge and then merge solves a V-Sekai source code broken tree",
     "section": "",
-    "text": "Use Blender to retarget t-posed characters.\n\n\n\nInputs: bvh + t-pose avatar\nOutput: glb w/retargetted animation\n\n\n\n\nBlender v2.91 or v2.92 (may work with other versions)\nBlender Add-On: skeletal-motion-retarget-blender\n\nDownload .zip\nUse Blender Edit =&gt; Preferences, Add-ons, Install that zip\nCheck the box for the new install an add-on to activate\n\n(optional) if using a VRM avatar Blender Add-On: saturday06/VRM_Addon_for_Blender\n\nDownload .zip\nUse Blender Edit =&gt; Preferences, Add-ons, Install that zip\nCheck the box for the newly install an add-on to activate\n\n\n\n\n\n\n\nHave a rigged, T-Pose humanoid avatar\nStart a new scene?\n\nUnder the Scene Settings property panel, set Frame Rate to 30 fps\n(or you may want to match your .mp4 frame rate used during capture)\n\nImport your avatar model\n\nif using a VRM avatar, be sure to use Import VRM (otherwise, retargeting may not work!)\n\nImport the generated BVH. In the Animation section, enable the following options\n\nScale FPS\nScene Duration\n\nUse the Pose Transfer tab (vertical tab part of the “N” options panel?)\n\nSource: the imported BVH armature\nTarget: the imported avatar armature\nClick the Rebuild Bone List\n\nmanually map over any bones not automatically mapped\neg: LeftLowerArm =&gt; “Left elbow”\nnote: it is possible to save your mapping to .json and reuse\n\nClick Retarget Animation\n\nretargeting may take several minutes\n\n\nVerify retargeting by playing the animation via the Blender play button\nExport the scene as a .glb (using default settings)\n\n\n\n\nQ: Retargeted animation seems to have legs crossed / backwards\nA: This can happen if you import a VRM avatar as a .gltf (re-import using the VRM importer add-on)\nQ: Legs/arms bend unnaturally\nA: Check the armature bone name mappings\n\nat most, each target bone name should appear once\nleave BVH joints not present in your avatar blank\n\n\n\n\nThanks to humbletim for being the scribe\nThanks to lyuma for being test pilot flying these steps\n\n\n\n\nHave a generally robust process of retargeting motions to VRM-type models.\n\n\n\n\n\nOnly VRM\nMMD does not work."
+    "text": "We use a tool called Git Assembly which makes reapplying branches on master easy. Here’s the strategy:\n\nIdentify the commit hash where the merge went wrong.\nRemove the item from the Git Assembler.\nAnalyze the code and identify the conflicts that caused the merge to fail.\nResolve the conflicts manually.\nFix the branch.\nReapply the branch on master using Git Assembly."
   },
   {
-    "objectID": "decisions/20210523-retarget-motion-for-vrm-type-models.html#option-graveyard-adobe-mixamo",
-    "href": "decisions/20210523-retarget-motion-for-vrm-type-models.html#option-graveyard-adobe-mixamo",
-    "title": "Proposed: Retarget VRM Motion Blender Workflow",
+    "objectID": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html#the-upside",
+    "href": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html#the-upside",
+    "title": "Proposed: Procedure to unmerge and then merge solves a V-Sekai source code broken tree",
     "section": "",
-    "text": "List the reasons for the rejection: (the Bad traits)\n\nProprietary Online Service\nBlackbox technology"
+    "text": "By following this strategy, we can potentially fix the broken source code tree without losing any significant work. This will allow us to resume the development process and meet our project deadlines."
   },
   {
-    "objectID": "decisions/20210523-retarget-motion-for-vrm-type-models.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20210523-retarget-motion-for-vrm-type-models.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Retarget VRM Motion Blender Workflow",
+    "objectID": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html#the-downside",
+    "href": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html#the-downside",
+    "title": "Proposed: Procedure to unmerge and then merge solves a V-Sekai source code broken tree",
     "section": "",
-    "text": "Motion retargeting is not trivial offline or online."
+    "text": "The process of unmerging and merging can be time-consuming and complex. If not done correctly, it may lead to further issues in the codebase."
   },
   {
-    "objectID": "decisions/20210523-retarget-motion-for-vrm-type-models.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20210523-retarget-motion-for-vrm-type-models.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Retarget VRM Motion Blender Workflow",
+    "objectID": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html#the-road-not-taken",
+    "href": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html#the-road-not-taken",
+    "title": "Proposed: Procedure to unmerge and then merge solves a V-Sekai source code broken tree",
     "section": "",
-    "text": "We need motions for our character controller without using an off-the-shelf black box solution."
+    "text": "An alternative approach could have been to abandon the current branch and start a new one from the last known good state. However, this would mean losing all the changes made after the last good state."
   },
   {
-    "objectID": "decisions/20210523-retarget-motion-for-vrm-type-models.html#references",
-    "href": "decisions/20210523-retarget-motion-for-vrm-type-models.html#references",
-    "title": "Proposed: Retarget VRM Motion Blender Workflow",
+    "objectID": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html#the-infrequent-use-case",
+    "href": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html#the-infrequent-use-case",
+    "title": "Proposed: Procedure to unmerge and then merge solves a V-Sekai source code broken tree",
     "section": "",
-    "text": "https://www.blender.org/\nhttps://hackmd.io/EmOAt375S8KFqaNdPDJCXQ\nhttps://github.com/V-Sekai/V-Sekai-Blender-tools/tree/main/addons/blender-skeletal-motion-animate"
+    "text": "This procedure is not commonly used as merges usually go smoothly. It’s only needed when a merge results in a broken source code tree."
   },
   {
-    "objectID": "decisions/20210523-retarget-motion-for-vrm-type-models.html#derivative-license",
-    "href": "decisions/20210523-retarget-motion-for-vrm-type-models.html#derivative-license",
-    "title": "Proposed: Retarget VRM Motion Blender Workflow",
+    "objectID": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html#in-core-and-done-by-us",
+    "href": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html#in-core-and-done-by-us",
+    "title": "Proposed: Procedure to unmerge and then merge solves a V-Sekai source code broken tree",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Yes, this procedure is core to our operations and is performed by our team."
   },
   {
-    "objectID": "decisions/20221021-make-it-easier-propose-and-post-bugs.html",
-    "href": "decisions/20221021-make-it-easier-propose-and-post-bugs.html",
-    "title": "Proposed: Make it easier to propose and file bugs by simplifying the templates",
+    "objectID": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html#further-reading",
+    "href": "decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html#further-reading",
+    "title": "Proposed: Procedure to unmerge and then merge solves a V-Sekai source code broken tree",
     "section": "",
-    "text": "Status: proposed \nDeciders: V-Sekai,lyuma\nTags: V-Sekai,\n\n\n\nAbout issue templates, I know Godot doesn’t permit plain feature requests in the main godot issue tracker. To propose something you have to have a fleshed out proposal.\nThat works well for Godot for two reasons: Godot has lots of users so there are already too many feature proposals; and the users of Godot are developers who can be asked to do research and write a whole implementation proposal\nThe users of V-Sekai are not technical in the same way; and furthermore we are not at the scale Godot was in 3.2 when they switched to requiring proposals.\nIf we ever do get big enough that feature requests propose a burden then we can consider making it harder to file them\n\n\n\nModify the V-Sekai-game issue templates to be easier to use.\n\n\n\nRemove required fields. Make them easier to use.\n\n\n\n\nMore bug filing\nMore proposals\n\n\n\n\n\nMore work on the devs to catalog\n\n\n\n\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\n\nNot a script.\n\n\n\nWe own the repos.\n\n\n\n\nV-Sekai\n\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "V-Sekai\nThis article is assisted by AI."
   },
   {
-    "objectID": "decisions/20221021-make-it-easier-propose-and-post-bugs.html#context-and-problem-statement",
-    "href": "decisions/20221021-make-it-easier-propose-and-post-bugs.html#context-and-problem-statement",
-    "title": "Proposed: Make it easier to propose and file bugs by simplifying the templates",
+    "objectID": "decisions/20211005-want-to-use-the-same-cluster-for-the-same-web-and-native.html",
+    "href": "decisions/20211005-want-to-use-the-same-cluster-for-the-same-web-and-native.html",
+    "title": "Proposed: Want to use the same cluster for the same web and native.",
     "section": "",
-    "text": "About issue templates, I know Godot doesn’t permit plain feature requests in the main godot issue tracker. To propose something you have to have a fleshed out proposal.\nThat works well for Godot for two reasons: Godot has lots of users so there are already too many feature proposals; and the users of Godot are developers who can be asked to do research and write a whole implementation proposal\nThe users of V-Sekai are not technical in the same way; and furthermore we are not at the scale Godot was in 3.2 when they switched to requiring proposals.\nIf we ever do get big enough that feature requests propose a burden then we can consider making it harder to file them"
+    "text": "Proposed: Want to use the same cluster for the same web and native.\n\nContext and Problem Statement\nWant to use the same cluster for the same web and native.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nBy using webrtc only, we are able to reuse the same servers.\nAn alternative of a webserver that has both webrtc and enet is also possible.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nSuppose the server cluster sets up the infrastructure. In that case, it feels like WebRTC may jump past firewalls easier, and there’s existing turn-ice stuff.\nMy colleague noted that you could have one Godot engine server provide a proxy to another Godot server. The design was similar to cell phone vs cell phone tower vs tower to tower distribution of messages. It wasn’t clear that was possible, but he found something. Any thoughts about that?\n\n\nProblems\nWebRTC is much more complex to set up, so I don’t think it is a good alternative for ENet for indies.\nWebRTC needs infrastructure; ENet does not.\nDependency problems between ScriptInstance and PacketPeer. What do you mean?\nThe script_language.h includes packet_peer.h, so PacketPeer cannot use GDVIRTUAL because that needs script_language.h\n\nQuestions\nHow do modern games different games have different bandwidth minimums?\nCents per hour to host how many players?\nHole-punching for pure peer-to-peer games.\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nThis is compiled into the project and is work to change.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nNetworking is part of the project and can’t be changed by mods.\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20221021-make-it-easier-propose-and-post-bugs.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20221021-make-it-easier-propose-and-post-bugs.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: Make it easier to propose and file bugs by simplifying the templates",
+    "objectID": "decisions/20220108-bake-blend-shapes-to-skeletons-for-performance.html",
+    "href": "decisions/20220108-bake-blend-shapes-to-skeletons-for-performance.html",
+    "title": "Proposal: Bake blend shapes to skeletons for performance",
     "section": "",
-    "text": "Modify the V-Sekai-game issue templates to be easier to use."
+    "text": "Status: proposed \nDeciders: V-Sekai,fire,\nTags: V-Sekai,\n\n\n\nBlend shapes are slow to render.\n\n\n\nBake blend shapes to skeletal animation.\n\n\n\n\nI want to bake blendshapes\n\n52 face blendshape face movements\nVRM blend shapes\nThe blend shapes are interpolated between 0s and 1s.\nsingle animation track.\n\nI can send it to dem #bone and bake the blend shapes.\n\n\n\n\nRemove empties that are unused.\nExtract the blend shape from the mesh\nExport as alembic 1 meter is 1 unit. Flatten hierarchy.\nNote that all transforms on un-rigged meshes should be applied.\nRemove the skeleton and fbx export as 1 meter is 0.01 units.\nRun dem #bone (parameters to be determined)\n\n./dembones -i=\"a.fbx\" -a=\"a.abc\" -z=4 --bindUpdate=2 -b=200 -o=\"a_res.fbx\"\n# Note that RMSE should be in the same range as 0.01\nComputing Skinning Decomposition:\n    Iter #0: Updating trans..... Done! Updating weights... Done! RMSE = 0.0917716\n`\n\n11. Check the RMSE is less than 0.001.\n\n#### Options\n\nSkinning decomposition to generate bone transformations and skinning weights from input meshes sequence\n\n`call #dembones -i=\"Bone_Geom.fbx\" -a=\"Bone_Anim.abc\" -b=20 -o=\"Decomposition_20.fbx\"`\n\nJoint grouping\n\n`call #dembones -i=\"Bone_Geom.fbx\" -a=\"Bone_Anim.abc\" -b=20 --bindUpdate=2 -o=\"Decomposition_20_grouped.fbx\"`\n\nSolve skinning weights from input meshes sequence and input bone transformations\n\n`call #dembones -i=\"Bone_Trans.fbx\" -a=\"Bone_Anim.abc\" --nTransIters=0 -o=\"SolvedWeights.fbx\"`\n\nSolve bone transformations from input meshes sequence and input skinning weights\n\n`call #dembones -i=\"Bone_Skin.fbx\" -a=\"Bone_Anim.abc\" --nWeightsIters=0 -o=\"SolvedTransformations.fbx\"`\n\nOptimize given bone transformations and skinning weights from input meshes sequence\n\n`call #dembones -i=\"Bone_All.fbx\" -a=\"Bone_Anim.abc\" --bindUpdate=1 -o=\"Optimized.fbx\"`\n\nOnly solve helper #bone using demLock attribute of the joints\n\n`call #dembones -i=\"Bone_Helpers.fbx\" -a=\"Bone_Anim.abc\" --bindUpdate=1 -o=\"SolvedHelpers.fbx\"`\n\nPartially solve skinning weights using per-vertex color attribute of the mesh\n\n`call #dembones -i=\"Bone_PartiallySkinned.fbx\" -a=\"Bone_Anim.abc\" --nTransIters=0 -o=\"SolvedPartialWeights.fbx\"`\n\n### Open questions:\n\nI align each track to a second? one after the others?\n\nHow do I find the tracks again?\n\n## Positive Consequences &lt;!-- optional --&gt;\n\n- Better performance\n- Able to compose animations\n\n## Negative Consequences &lt;!-- optional --&gt;\n\n- More #bone\n\n## Option graveyard: &lt;!-- same as above --&gt;\n\n- Option: Status quo\n- Rejection Reason: Blend shapes are slow and uncomposable.\n\n## If this enhancement will not be used often, can it be worked around with a few lines of script?\n\nNot a few lines of code to do error bound matching and geometry processing.\n\n## Is there a reason why this should be core and done by us?\n\nI know how to do this!\n\n## References &lt;!-- optional and numbers of links can vary --&gt;\n\n- https://github.com/electronicarts/dem-bones\n\n## Derivative License\n\nCopyright (c) 2021 V-Sekai contributors.\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
   },
   {
-    "objectID": "decisions/20221021-make-it-easier-propose-and-post-bugs.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20221021-make-it-easier-propose-and-post-bugs.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Make it easier to propose and file bugs by simplifying the templates",
+    "objectID": "decisions/20220108-bake-blend-shapes-to-skeletons-for-performance.html#context-and-problem-statement",
+    "href": "decisions/20220108-bake-blend-shapes-to-skeletons-for-performance.html#context-and-problem-statement",
+    "title": "Proposal: Bake blend shapes to skeletons for performance",
     "section": "",
-    "text": "Remove required fields. Make them easier to use."
+    "text": "Blend shapes are slow to render."
   },
   {
-    "objectID": "decisions/20221021-make-it-easier-propose-and-post-bugs.html#positive-consequences",
-    "href": "decisions/20221021-make-it-easier-propose-and-post-bugs.html#positive-consequences",
-    "title": "Proposed: Make it easier to propose and file bugs by simplifying the templates",
+    "objectID": "decisions/20220108-bake-blend-shapes-to-skeletons-for-performance.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20220108-bake-blend-shapes-to-skeletons-for-performance.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposal: Bake blend shapes to skeletons for performance",
     "section": "",
-    "text": "More bug filing\nMore proposals"
+    "text": "Bake blend shapes to skeletal animation."
   },
   {
-    "objectID": "decisions/20221021-make-it-easier-propose-and-post-bugs.html#negative-consequences",
-    "href": "decisions/20221021-make-it-easier-propose-and-post-bugs.html#negative-consequences",
-    "title": "Proposed: Make it easier to propose and file bugs by simplifying the templates",
+    "objectID": "decisions/20220108-bake-blend-shapes-to-skeletons-for-performance.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20220108-bake-blend-shapes-to-skeletons-for-performance.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposal: Bake blend shapes to skeletons for performance",
     "section": "",
-    "text": "More work on the devs to catalog"
+    "text": "I want to bake blendshapes\n\n52 face blendshape face movements\nVRM blend shapes\nThe blend shapes are interpolated between 0s and 1s.\nsingle animation track.\n\nI can send it to dem #bone and bake the blend shapes.\n\n\n\n\nRemove empties that are unused.\nExtract the blend shape from the mesh\nExport as alembic 1 meter is 1 unit. Flatten hierarchy.\nNote that all transforms on un-rigged meshes should be applied.\nRemove the skeleton and fbx export as 1 meter is 0.01 units.\nRun dem #bone (parameters to be determined)\n\n./dembones -i=\"a.fbx\" -a=\"a.abc\" -z=4 --bindUpdate=2 -b=200 -o=\"a_res.fbx\"\n# Note that RMSE should be in the same range as 0.01\nComputing Skinning Decomposition:\n    Iter #0: Updating trans..... Done! Updating weights... Done! RMSE = 0.0917716\n`\n\n11. Check the RMSE is less than 0.001.\n\n#### Options\n\nSkinning decomposition to generate bone transformations and skinning weights from input meshes sequence\n\n`call #dembones -i=\"Bone_Geom.fbx\" -a=\"Bone_Anim.abc\" -b=20 -o=\"Decomposition_20.fbx\"`\n\nJoint grouping\n\n`call #dembones -i=\"Bone_Geom.fbx\" -a=\"Bone_Anim.abc\" -b=20 --bindUpdate=2 -o=\"Decomposition_20_grouped.fbx\"`\n\nSolve skinning weights from input meshes sequence and input bone transformations\n\n`call #dembones -i=\"Bone_Trans.fbx\" -a=\"Bone_Anim.abc\" --nTransIters=0 -o=\"SolvedWeights.fbx\"`\n\nSolve bone transformations from input meshes sequence and input skinning weights\n\n`call #dembones -i=\"Bone_Skin.fbx\" -a=\"Bone_Anim.abc\" --nWeightsIters=0 -o=\"SolvedTransformations.fbx\"`\n\nOptimize given bone transformations and skinning weights from input meshes sequence\n\n`call #dembones -i=\"Bone_All.fbx\" -a=\"Bone_Anim.abc\" --bindUpdate=1 -o=\"Optimized.fbx\"`\n\nOnly solve helper #bone using demLock attribute of the joints\n\n`call #dembones -i=\"Bone_Helpers.fbx\" -a=\"Bone_Anim.abc\" --bindUpdate=1 -o=\"SolvedHelpers.fbx\"`\n\nPartially solve skinning weights using per-vertex color attribute of the mesh\n\n`call #dembones -i=\"Bone_PartiallySkinned.fbx\" -a=\"Bone_Anim.abc\" --nTransIters=0 -o=\"SolvedPartialWeights.fbx\"`\n\n### Open questions:\n\nI align each track to a second? one after the others?\n\nHow do I find the tracks again?\n\n## Positive Consequences &lt;!-- optional --&gt;\n\n- Better performance\n- Able to compose animations\n\n## Negative Consequences &lt;!-- optional --&gt;\n\n- More #bone\n\n## Option graveyard: &lt;!-- same as above --&gt;\n\n- Option: Status quo\n- Rejection Reason: Blend shapes are slow and uncomposable.\n\n## If this enhancement will not be used often, can it be worked around with a few lines of script?\n\nNot a few lines of code to do error bound matching and geometry processing.\n\n## Is there a reason why this should be core and done by us?\n\nI know how to do this!\n\n## References &lt;!-- optional and numbers of links can vary --&gt;\n\n- https://github.com/electronicarts/dem-bones\n\n## Derivative License\n\nCopyright (c) 2021 V-Sekai contributors.\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
   },
   {
-    "objectID": "decisions/20221021-make-it-easier-propose-and-post-bugs.html#option-graveyard",
-    "href": "decisions/20221021-make-it-easier-propose-and-post-bugs.html#option-graveyard",
-    "title": "Proposed: Make it easier to propose and file bugs by simplifying the templates",
+    "objectID": "decisions/20200608-vsekai-charter.html",
+    "href": "decisions/20200608-vsekai-charter.html",
+    "title": "Mozilla Builders Summer MVP Lab (SUBMITTED ON JUNE 8 2020)",
     "section": "",
-    "text": "Option: The status quo. \nRejection Reason: This solves nothing."
+    "text": "Mozilla Builders Summer MVP Lab (SUBMITTED ON JUNE 8 2020)\nDid you apply for our Spring MVP Lab program?\nCheck this if at least one team member applied.\nOne line summary of the MVP:\nA fully remixable and self-hosted collaborative VR environment based on Godot Engine.\nDescription of the product: What will the MVP be in 8 weeks?\nOur standalone Virtual Reality (VR) application will be usable from all SteamVR compatible PC headsets, as well as the mobile Oculus Quest VR platform. The MVP features a social hub with both 3D spatialized voice and realtime upper body tracking, with simple games, physics and social video viewing.\nCategory Category\n\nCollaboration & Society\nDecentralized Web : YES\nMessaging & Social Networking : YES\nSurveillance Capitalism\nMisinformation & Content\nArtificial Intelligence\nWeb Assembly\n\nCheck all that apply.\nOptional Video\nhttps://www.youtube.com/watch?v=j2PTDXG1Hc4\nWhy does your idea matter: How will it help deliver on the full promise of the internet, or make the internet more awesome? * The core principles of the Internet are openness and communication. We see VR as the basis for a new frontier of communication products, Social VR platforms. Hastened by the closure and general failings of the once-open source High Fidelity platform, we are now in desperate need of open source alternatives to the growing number of closed source VR-compatible walled gardens in development.\nWe are at the pinnacle of a new wave of VR and related tech, and with the impending maturity of open game engines, audio and video codecs, combined with faster internet connectivity capable of hosting services, and increasingly available VR hardware, the time is right to lead the development of an open platform.\nWe believe in putting power back in the hands of individuals, and thus we are strong believers in decentralized technology. Our initial goal will be to produce a polished, well-functioning service, but we also have plans to integrate decentralized authentication and encryption schemes, including GPG and web of trust based E2EE, as well as decentralized content distribution tech such as Bittorrent and IPFS.\nWho are your users or potential users?\nWe are building a product for all users of social VR, online collaboration or communication products. Social VR is a growing space, and its potential is only beginning to be realized, with a mass movement towards virtual collaboration.\nEven VR as a whole is still in very early stages, but it represents a large potential market, especially with the recent availability of affordable and easy to install headsets such as the Oculus Quest, which has seen rapid growth after its release one year ago.\nAn example of a leading VR platform with public numbers, VRChat has recently between 12000 and 15000 concurrent online users across VR and Desktop platforms, with roughly 4000 concurrent VR users using this platform (out of a reported 4 million registered users as of 2019).\nWhat is your personal connection to the service & the user group you are planning to reach with your product? *\nWe’re a passionate team of VR enthusiasts, some of us tinkering in our spare time with visual effects, level design, or graphics concepts still in research.\nIn an age where collaborating and connecting at distance is increasingly important, meeting in real life can often be a barrier to people. VR has the potential to bring people together and immerse them in a shared space, in a way that not even the best video collaboration can. I and another member of our group have participated in Virtual Market 4, the most recent iteration of a Japanese-run exponentially-growing marketplace of virtual content spanning multiple platforms.\nOther Social VR platforms have found ways to immerse me in a multitude of realities: for example, engaging in real time with people around the world at all times of day and night: attending live dance and music events, seeing performers breakdance and do pole acrobatics using VIVE full body trackers, forming friendships through exchanging personal stories around a campfire, programming environments defined by a math function and then experiencing them in VR, even solving a 1000 piece jigsaw puzzle with friends. It is my dream to enable these experiences and more in a setting that is sustainable, open and accessible.\nIf we do not fund this project, will your team still work on it? To what extent? *\nAn Injection of capital by Mozilla will speed up our development and let me take leave of my company to focus full time on the MVP. This could give us the opportunity to outrun these walled gardens in a very short time.\nIf not funded, we will be able to continue to advance it more slowly in our spare time, but other closed platforms are catching up, and time is of the essence. Our project will additionally drive development around open source VR support and 3D tools, and we can see lasting effects from our contributions in those areas.\nWhy did you pick this idea? Do you have domain expertise? How do you know people need what you’re building? *\nWe’re seeding the beginning of the VR frontier, and we already see a sizable fraction of the current VR population spending a substantial amount of time in Social VR walled gardens, such as VRChat.\nIt can be difficult or impossible to build atop walled garden platforms outside of their respective visions: we’ve run into such roadblocks in past projects. For example a combination of lack of the persistence, access to media/web requests, and general customizability has made other platforms unsuitable for building long games, and unsuitable for building complex collaboration tools. Meanwhile, our platform can be self hosted, allows private usage and can be modified.\nOur team includes significant backend and operations experience and several years of work on Godot Engine, all of which will be relevant to building this platform.\nWe suspect the need exists for an open alternative to other competing walled gardens. While many VR platforms are currently free-to-use and advertise a minimal set of privacy features, there is no guarantee that popular platforms will remain free or private forever: for example, a widely used product could be acquired by a corporation with different goals.\nAdditionally, we see potential for a customizable, open platform to be used within enterprises, as well as to build the foundation for games or other content which share needs with our platform, such as its VOIP or VR interaction features.\nAre you looking for any teammates? If so, please indicate what skills or roles you seek.\nNot at this time\nWe have created a Slack Channel and GitHub repository and issues list where you can post your project and look for teammates. You can also pivot or abandon your project as you connect with teammates:\nGitHub: https://github.com/fix-the-internet/spring-mvp-lab/issues\nSlack: https://join.slack.com/t/mozillabuilders/shared_invite/zt-czo6bp37-R9I5mKJVYPtCkTQFu1NLWw\nDescribe your work plan.\nTHIS IS A COPY OF OUR GANTT CHART. THIS WAS NOT SUBMITTED ~Lyuma\nWeek 1: Maintain continuous integration of Windows SteamVR and Oculus Quest, and Linux server builds running on a public server against which to test and dogfood the product. VOIP implementation: basic lipsync based on volume, integrate spatialization library. Improve Inverse Kinematics implementation and add non-VR support.\nWeek 2: Headless clients to extensively stress test the system. Implement crash reporting system, and reporting metrics including performance. Content: Use a basic scripting API to implement physics based games. Begin work on engine changes necessary to give smooth framerates even when during content loading.\nWeek 3: Networking interpolation: eliminate stuttering caused by networking. Godot OpenVR Plugin: fix bugs causing inconsistent framerate in VR. Pre-load content where needed to avoid stutters in the 3d environment.\nWeek 4: Content: Begin work on specific set of hardcoded avatars. Content: Recruit artist to begin work on create default home map. Physics: fix physics errors such as sliding down ramps. Test performance on regular vr hardware and optimization.\nWeek 5-6: Account system, TOS, Privacy Policy. Allow closed registration of users, starting with people who have already shown interest. Continue working on content. Fix bugs and issues as needed. Integration of video playback. Focus on stress testing.\nWeek 7-8 Fix bugs discovered during testing. Monitor performance metrics captured by users, keep fixing performance\nDescribe the approach the team will take to develop the Minimum Viable Product throughout the summer. This includes, but not limited to:\n\nWho are your competitors?\n\nVRChat, Facebook Horizon, RecRoom, AltSpace, EngageVR, Spatial (quest), Mozilla Hubs, VirtualCast, cluster, Sansar, HTC Vive Sync, OasisVR, ChilloutVR, Lavender, Roblox VR (We are not considering non-VR capable platforms or MMORPGs as competition)\n\nHow will you attract your first 1000 users? Your first 1,000,000?\n\nWe anticipate contacts from our immediate VR communities who have already shown interest in our project will seed the first 50 users.\nAt a minimum, we will provide the real time presence features available in other VR platforms: appearing in a room of people who you can hear and to break past 100 users, we will need to provide experiences which are not easily accessible on other platforms such as VRChat.\nTo move beyond thousands of users: being a neutral, open platform to host events: for example, Virtual Market had on the order of a million visitors ( https://www.youtube.com/watch?v=lLX7UNKV1fk ; https://v-market.work/ ), was hosted just as a collection of VRChat world instances, and still had to deal with several glitches as a result of instabilities of the underlying platform.\nAnother source of usage will be business meetings, and anything where privacy and self-hosting is a concern. Making sure that it is lightweight and remains very easy to compile will allow novel usages and customizations of the platform.\n\nFirst 2 week development milestone\n\nFirst two weeks:\n\nMaintain continuous integration of Windows SteamVR and Oculus Quest, and Linux server builds running on a public server against which to test and dogfood the product.\nVOIP implementation: basic lipsync based on volume, integrate spatialization library.\nImprove Inverse Kinematics implementation and add non-VR support.\nHeadless clients to extensively stress test the system.\nImplement crash reporting system, and reporting metrics including performance.\nContent: Use a basic scripting API to implement physics based games.\nBegin work on engine changes necessary to give smooth framerates even when during content loading.\nTech stack you plan to use (Cloud services, APIs, mobile platforms, languages, etc)\n\nGodot Engine, k3s, Elixir, OAuth, CockroachDB, nginx, Fedora, CentOS 8, Digital Ocean Spaces, Oculus Quest SDK on Android, Valve OpenVR on Windows.\n\nLink to simple sketches (can be as simple as paper and pencil) of your product or idea\n\nhttps://cdn.discordapp.com/attachments/659137056991346708/718332831687901224/vsekai-sketch.png\nLinks to mockups, prototypes, pitches.\nWhat challenges do you anticipate with this idea?\nWith the exception of Hubs, the now-defunct High Fidelity, and a handful of proprietary VR platforms, most Social VR applications are being developed in Unity. This leads to a design challenge in building around infrastructure and content that was created specifically with Unity in mind. For example, one of the leading open model sharing formats VRM only officially supports exporting from Unity.\nSocial platforms are strongly impacted by network effect, which puts a challenge towards acquisition. On top of this, VR applications tend to have extremely low retention compared with conventional applications. One possible reason is the restriction of only running one application at a time.\nWe are likely to encounter several unanticipated engineering challenges: VR platforms combine most of the hardest problems in all aspects of computing, from art, networking, social features to graphics optimization.\nTeam Member Locations by Country\nAdd location of all team members by country. COMMA SEPARATED.\nCanada, United States, United Kingdom\nTeam Details\nDescribe the background of ALL team members including finished projects, design skills, technologies, languages + frameworks you are familiar with or briefly describe any professional experience.\nMMMaellon: C++, Java, and Python. Familiar with the Android and iOS frameworks. Design skills come from working professionally as a motion graphics and VFX artist, and video editor. Used to work for a mobile app developer and in the process of getting a masters in computer science.\nSaracen: C++, C, C#, Java, Python, GDScript, Android. Worked several years professionally on mobile app development, self-taught experience working on game mods and game engine architecture including forks of the Id Software GPL releases, code contributions to the open source Godot Engine and to other VR platforms, tools development including Unity, Godot, and Blender plugins, and work on reimplementing legacy game engines for modern platforms.\nLyuma: C++, Java, Python, Javascript, C#, Android, iOS. Familiar with backend, operations, networking. Spent 9 years working in industry: led a team developing the VOIP and video implementation on an iOS and Android app reaching hundreds of millions of users, including the backend architecture, scaling, operations, and networking, as well as the stats and monitoring needed to optimize the design.\niFire: C++. Familiar with Godot Engine and Unreal Engine. Working professionally in game development. For Godot Engine, created a Blender to glTF2 pipeline and coordinating a FBX pipeline. Shipped Offworld Industries’ Squad (80 player War Simulator) as a programmer, devops, and IT for nearly two years. As a team, I implemented a Unreal Engine touch screen product demo for an aerospace company that was exhibited at the Las Vegas NBAA convention using HTML5 and Blueprints.\nWill all team members be committing their full-time energy to this project during the 8 weeks of the program? Not all successful MVP applicants will, but we do expect a major commitment to the MVP Lab. Please explain if you’re not able to commit fulltime to this & how we can be sure this will be a very serious commitment by you and your team\nMMMaellon is making individual contributions, including a VR character movement system, that have proved extremely valuable, as needed.\nSaracen will be working full time on the core client written for Godot.\nLyuma will be working full time on this project starting with the MVP Lab, focusing on dev ops, operations, backend and testing.\niFire is heavily engaged with the wider open source community surrounding Godot Engine, and takes on projects which help further Godot as an ecosystem, on top of spending part time dedicated to this MVP project.\nHow did you hear about the MVP Lab?\nWe heard about it from Hacker News: https://news.ycombinator.com/item?id=23194178\nAnything else we should know?\nAside from being passionate in the VR space, we are all committed to open source/decentralization, and we strive to bring value to the internet community as a whole."
   },
   {
-    "objectID": "decisions/20221021-make-it-easier-propose-and-post-bugs.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20221021-make-it-easier-propose-and-post-bugs.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Make it easier to propose and file bugs by simplifying the templates",
+    "objectID": "decisions/20220317-use-spec-rough-metal.html",
+    "href": "decisions/20220317-use-spec-rough-metal.html",
+    "title": "Proposed: Use specular vec3 from gltf to show multicoloured metals",
     "section": "",
-    "text": "Not a script."
+    "text": "Proposed: Use specular vec3 from gltf to show multicoloured metals\n\nDesc\nribe the status of the issue.\nrejected\n\n\nList the deciders of the issue.\nV-Sekai,fire,\n\n\nDescribe the tags of the issue.\nV-Sekai,\n\n\nContext and Problem Statement\nWe want to be able to use Specular from gltf and Specular from spec gloss, but previous solutions did not compose with the principled pbr roughness metallness model.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nImplement specular from gltf.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\n???\n\n\nPositive Consequences\nWe can import spec gloss for compatibility.\nDemos show multicolored transparency.\n\n\nNegative Consequences\n\nMore complexity\n\n\n\nOption graveyard\n\nOption: Add spec gloss extension\nDoes not compose with roughness metalness.\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot a few lines of code.\n\n\nIs there a reason why this should be core and done by us?\nChanging the standard material 3d is a core decision.\n\n\nReferences\n\nV-Sekai\n\n\n\nLicense of the contribution\nCopyright (c) 2022 V-Sekai contributors. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20221021-make-it-easier-propose-and-post-bugs.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20221021-make-it-easier-propose-and-post-bugs.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Make it easier to propose and file bugs by simplifying the templates",
+    "objectID": "decisions/20211031-bake-a-materialx-into-a-custom-godot-standardmaterial3d.html",
+    "href": "decisions/20211031-bake-a-materialx-into-a-custom-godot-standardmaterial3d.html",
+    "title": "Proposed: Bake a #materialx into a custom Godot StandardMaterial3D",
     "section": "",
-    "text": "We own the repos."
+    "text": "Proposed: Bake a #materialx into a custom Godot StandardMaterial3D\n\nContext and Problem Statement\nThere is not many procedural material Makers.\nThe two the come to mind is Godot’s Material Maker and Adobe’s Substance Designer.\nMore options would be helpful.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nCreate a #materialx to Godot Standard Material tool.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nMake a GDscript tool that takes the #materialx bake tool I already made and bake it to a standard material 3D in Godot Engine.\nCraft a GDScript that uses the command line tool and converts mtlx to a standard material 3d.\n\napt install -y libglew-dev\n\n\ncmake -GNinja .. -DMATERIALX_BUILD_BAKER=ON\n\n\n.\\bin\\MaterialXBake.exe --material .\\resources\\Materials\\Examples\\glTFPBR\\gltf_pbr_boombox.mtlx --bakeFilename ../demo.mtlx --bakeWidth 8192 --bakeHeight 8192\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nEh. Not simple.\n\n\nPositive Consequences\nExpansion into a web tool.\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nI found an approach and it can be done.\n\n\nReferences\n\nhttps://github.com/fire/MaterialX/tree/gltf\nhttps://godotengine.org/showcase/material-maker\nhttps://en.wikipedia.org/wiki/Procedural_texture\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20221021-make-it-easier-propose-and-post-bugs.html#references",
-    "href": "decisions/20221021-make-it-easier-propose-and-post-bugs.html#references",
-    "title": "Proposed: Make it easier to propose and file bugs by simplifying the templates",
+    "objectID": "decisions/20230829-omifest-2023.html",
+    "href": "decisions/20230829-omifest-2023.html",
+    "title": "Proposed: OMIFest 2023 - The Call",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Status: Proposed\nDeciders: OMIGroup, Fire, Indiebio\nTags: OMIGroup, V-Sekai\n\n\n\n\n\n\nOMIFest 2023 is an online event set against the backdrop of a rapidly evolving digital landscape. As virtual reality and augmented reality technologies become more accessible, there’s an increasing need for platforms that allow artists, tinkerers, hackers, players, and professionals to showcase their talents and collaborate in a digital environment.\n\n\n\nThe challenge is to create an event that not only celebrates these individuals but also encourages conversation and collaboration within our community. We aim to build a webpage on the OMI website for more information and updates about this online event.\n\n\n\n\n\n\nOur strategy is to host a series of monthly events leading up to the main event in October 2024. Each month we will focus on different aspects of the event, such as building the vehicle, avatars, textures, scenery, and workshops on content creation.\n\n\n\nResearch: Held in conjunction with an academically minded in-person conference.\nAssets, protocols, and specification testing: Build assets and test protocols to ensure interoperability.\nCommunity Celebration: Celebrate with the global community in a digital setting.\n\n\n\n\nThis online event is open to everyone. Individuals, teams, corporate members, community groups, anyone and everyone can submit an entry. Registration will be required for our information, and some moderation may be required, but everyone is welcome.\n\n\n\n\nNotice boards for help needed, job board, find a team etc\nLimited poster advertising\nMusic\nBooths for nonprofit, education, community organizations\nMetaverse library/blockbuster to find how-to guides, videos, etc\nThrift shop for free stuff\nMarket for assets\nJunk yard for abandoned assets\nPortals to other worlds\nAssets that are created remain in the world\nScenery around the parade\nParade with floats\n\n\n\n\nIt is free to register and submit assets. The event will be free to attend. Some aspects and mini events may require payment.\n\n\n\nWe are open to sponsorships for this online event. More details will be provided soon.\n\n\n\nHere is a rough schedule of our monthly events:\n\n\n\nDate\nTopic\n\n\n\n\nAugust 2023\nContent sharing workshop\n\n\nSeptember 2023\nMaking a basic vehicle\n\n\nOctober 2023\nMaking an avatar\n\n\nNovember 2023\nMaking textures\n\n\nDecember 2023\nMaking scenery\n\n\nJanuary 2024\nMusic in the metaverse\n\n\nFebruary 2024\nAI\n\n\nMarch 2024\nCommunity, public spheres\n\n\nApril 2024\nPortals\n\n\nMay 2024\n(repeat the above?)\n\n\nJune 2024\nUse art to explore data\n\n\nJuly 2024\nReal world challenge\n\n\n\n\n\n\n\nThe upside of this online event is that it provides a platform for individuals from various backgrounds to showcase their talents, learn from each other, and collaborate on projects. It also helps in promoting the use of VR/AR technologies and encourages innovation in this field.\n\n\n\nThe downside could be the potential logistical challenges involved in organizing such a large-scale online event. There might also be issues related to ensuring fair participation and dealing with intellectual property rights.\n\n\n\nAn alternative approach could have been to organize smaller, more frequent online events throughout the year. However, we decided to go with a larger annual event to create more impact and allow participants enough time to prepare.\n\n\n\nWhile the event is designed to cater to a wide range of participants, there might be some who might not be able to participate due to lack of access to necessary technology or skills. We plan to address this by providing resources and learning materials to help them get started.\n\n\n\nYes, the event is being organized by us, OMIGroup, in collaboration with V-Sekai. We are responsible for planning, coordinating, and executing aspects of the event. The success of such a large-scale online event relies on the collective efforts of many individuals and organizations.\n\n\n\n\n\nOMIGroup\nV-Sekai\nMetaverse Float Parade\nThis article is assisted by AI."
   },
   {
-    "objectID": "decisions/20221021-make-it-easier-propose-and-post-bugs.html#license-of-the-contribution",
-    "href": "decisions/20221021-make-it-easier-propose-and-post-bugs.html#license-of-the-contribution",
-    "title": "Proposed: Make it easier to propose and file bugs by simplifying the templates",
+    "objectID": "decisions/20230829-omifest-2023.html#metadata",
+    "href": "decisions/20230829-omifest-2023.html#metadata",
+    "title": "Proposed: OMIFest 2023 - The Call",
     "section": "",
-    "text": "Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Status: Proposed\nDeciders: OMIGroup, Fire, Indiebio\nTags: OMIGroup, V-Sekai"
   },
   {
-    "objectID": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html",
-    "href": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html",
-    "title": "Rejected: Iterate faster on WasGo prototype by using Godot 3.4",
+    "objectID": "decisions/20230829-omifest-2023.html#context",
+    "href": "decisions/20230829-omifest-2023.html#context",
+    "title": "Proposed: OMIFest 2023 - The Call",
     "section": "",
-    "text": "Status: rejected \nDeciders: V-Sekai,fire,\nTags: V-Sekai,\n\n\n\nIterating on WasGo is too slow.\n\n\n\nPropose iterating on WasGo on Godot 3.4.\n\n\n\n\nBranch off Godot 3.4\nUse our version of wasgo\nRestore wasgo demos.\nImplement templated C++ code via mustashe for Wasgo\nPort to master\n\n\n\n\n\nSeparate the two axis of development. The first axis is Godot Engine master and the second axis is Wasgo development.\n\n\n\n\n\nMay or may not be more expensive.\nTook too much effort to verify.\n\n\n\n\n\nOption: \nRejection Reason: \n\n\n\n\nCoding strategy is not coding.\n\n\n\nThis is a V-Sekai strategy plan.\n\n\n\n\nhttps://github.com/V-Sekai/WasGo\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "OMIFest 2023 is an online event set against the backdrop of a rapidly evolving digital landscape. As virtual reality and augmented reality technologies become more accessible, there’s an increasing need for platforms that allow artists, tinkerers, hackers, players, and professionals to showcase their talents and collaborate in a digital environment.\n\n\n\nThe challenge is to create an event that not only celebrates these individuals but also encourages conversation and collaboration within our community. We aim to build a webpage on the OMI website for more information and updates about this online event."
   },
   {
-    "objectID": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html#context-and-problem-statement",
-    "href": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html#context-and-problem-statement",
-    "title": "Rejected: Iterate faster on WasGo prototype by using Godot 3.4",
+    "objectID": "decisions/20230829-omifest-2023.html#decision",
+    "href": "decisions/20230829-omifest-2023.html#decision",
+    "title": "Proposed: OMIFest 2023 - The Call",
     "section": "",
-    "text": "Iterating on WasGo is too slow."
+    "text": "Our strategy is to host a series of monthly events leading up to the main event in October 2024. Each month we will focus on different aspects of the event, such as building the vehicle, avatars, textures, scenery, and workshops on content creation.\n\n\n\nResearch: Held in conjunction with an academically minded in-person conference.\nAssets, protocols, and specification testing: Build assets and test protocols to ensure interoperability.\nCommunity Celebration: Celebrate with the global community in a digital setting.\n\n\n\n\nThis online event is open to everyone. Individuals, teams, corporate members, community groups, anyone and everyone can submit an entry. Registration will be required for our information, and some moderation may be required, but everyone is welcome.\n\n\n\n\nNotice boards for help needed, job board, find a team etc\nLimited poster advertising\nMusic\nBooths for nonprofit, education, community organizations\nMetaverse library/blockbuster to find how-to guides, videos, etc\nThrift shop for free stuff\nMarket for assets\nJunk yard for abandoned assets\nPortals to other worlds\nAssets that are created remain in the world\nScenery around the parade\nParade with floats\n\n\n\n\nIt is free to register and submit assets. The event will be free to attend. Some aspects and mini events may require payment.\n\n\n\nWe are open to sponsorships for this online event. More details will be provided soon.\n\n\n\nHere is a rough schedule of our monthly events:\n\n\n\nDate\nTopic\n\n\n\n\nAugust 2023\nContent sharing workshop\n\n\nSeptember 2023\nMaking a basic vehicle\n\n\nOctober 2023\nMaking an avatar\n\n\nNovember 2023\nMaking textures\n\n\nDecember 2023\nMaking scenery\n\n\nJanuary 2024\nMusic in the metaverse\n\n\nFebruary 2024\nAI\n\n\nMarch 2024\nCommunity, public spheres\n\n\nApril 2024\nPortals\n\n\nMay 2024\n(repeat the above?)\n\n\nJune 2024\nUse art to explore data\n\n\nJuly 2024\nReal world challenge\n\n\n\n\n\n\n\nThe upside of this online event is that it provides a platform for individuals from various backgrounds to showcase their talents, learn from each other, and collaborate on projects. It also helps in promoting the use of VR/AR technologies and encourages innovation in this field.\n\n\n\nThe downside could be the potential logistical challenges involved in organizing such a large-scale online event. There might also be issues related to ensuring fair participation and dealing with intellectual property rights.\n\n\n\nAn alternative approach could have been to organize smaller, more frequent online events throughout the year. However, we decided to go with a larger annual event to create more impact and allow participants enough time to prepare.\n\n\n\nWhile the event is designed to cater to a wide range of participants, there might be some who might not be able to participate due to lack of access to necessary technology or skills. We plan to address this by providing resources and learning materials to help them get started.\n\n\n\nYes, the event is being organized by us, OMIGroup, in collaboration with V-Sekai. We are responsible for planning, coordinating, and executing aspects of the event. The success of such a large-scale online event relies on the collective efforts of many individuals and organizations."
   },
   {
-    "objectID": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Rejected: Iterate faster on WasGo prototype by using Godot 3.4",
+    "objectID": "decisions/20230829-omifest-2023.html#references",
+    "href": "decisions/20230829-omifest-2023.html#references",
+    "title": "Proposed: OMIFest 2023 - The Call",
     "section": "",
-    "text": "Propose iterating on WasGo on Godot 3.4."
+    "text": "OMIGroup\nV-Sekai\nMetaverse Float Parade\nThis article is assisted by AI."
   },
   {
-    "objectID": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Rejected: Iterate faster on WasGo prototype by using Godot 3.4",
+    "objectID": "decisions/20211031-vmd-on-vrm-animationtree-node.html",
+    "href": "decisions/20211031-vmd-on-vrm-animationtree-node.html",
+    "title": "Draft: VMD on VRM AnimationTree Node",
     "section": "",
-    "text": "Branch off Godot 3.4\nUse our version of wasgo\nRestore wasgo demos.\nImplement templated C++ code via mustashe for Wasgo\nPort to master"
+    "text": "Draft: VMD on VRM AnimationTree Node\n\nContext and Problem Statement\nEirexe made a VMD player based on Lox’s work.\nThis new ability means we now have a viable way to load VMD motions and use them as a VRM motion player.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nWe want to make an AnimationTree node to drive Miku Miku VMD motion and add other procedural animation features to blend motion on the VRM Avatar.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nHowever, we need to make some changes to the AnimationTree UI editor to make the changes possible. We want an expanded AnimationTree to customize nodes, mainly when Godot Engine adds procedural animation features.\nSaracen wants to make sure that the AnimationTree gets the features needed so any custom nodes can be quickly prototyped via scripted extensions if needed. Doing it in purely c++ can limit scripting.\niFire’s “hard coding” definition tests if the node is different from writing the node from a composition of existing nodes. A VMD animation tree node would be “hard coding.”\nThere are currently some limitations with the AnimationTree, which makes the animation tree somewhat challenging to extend with custom nodes via scripting. However, the good news is, we do not think it would take much to make a VMD AnimationTree node work. The AnimationTree work is primarily a UI limitation and a small one at that.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNOT A FEW LINES OF CODE!\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nWe currently know how to do this, if we don’t who else will?\n\n\nReferences\n\nhttps://github.com/EIRTeam/VMDMotionGD\nhttps://github.com/V-Sekai/godot-vrm\nhttps://en.wikipedia.org/wiki/MikuMikuDance\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html#positive-consequences",
-    "href": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html#positive-consequences",
-    "title": "Rejected: Iterate faster on WasGo prototype by using Godot 3.4",
+    "objectID": "decisions/20230908-bendable-screen-generative-assistant-ggml.html",
+    "href": "decisions/20230908-bendable-screen-generative-assistant-ggml.html",
+    "title": "Draft: Translation/Transcription Badge with GGML’s Whisper",
     "section": "",
-    "text": "Separate the two axis of development. The first axis is Godot Engine master and the second axis is Wasgo development."
+    "text": "The project aims to develop a translation/transcription badge using GGML’s Whisper, a part of the GGML library that provides access to large language models (LLMs). The primary focus is on voice interactions.\n\n\n\n\nVoice Interactions: The system will prioritize voice interactions, leveraging GGML’s Whisper capabilities to create a responsive AI. Python will not be used in this context.\nSpeech-to-Text Interface: A speech-to-text interface will be incorporated to process voice inputs effectively.\nDirect Connection to Compute Module: The display, set in portrait mode, will connect directly to the compute module, a standard Linux amd64 computer, eliminating the need for embedded software development.\nFlexible OLED Display: The system will utilize a 6-inch flexible OLED display from Wisecoco with a resolution of 2880*1440 at 60Hz refresh rate.\nNo Holograph Displays: The design will be streamlined and efficient, excluding holograph displays.\n\n\n\n\nThe project’s complexity and the expertise required in areas such as GGML, the Godot engine, and AI development pose significant challenges.\n\n\n\nWe have decided against integrating Python with GGML and using a pre-existing AI framework instead of developing one from scratch.\n\n\n\nThe project may not be suitable for individuals without familiarity with GGML or a background in AI development.\n\n\n\nThe project will be developed in-house, utilizing our expertise in AI and game development.\n\n\n\nFor more information, please refer to these resources:\n\nV-Sekai\nGGML on GitHub\nWhisper JAX on GitHub\nTwitter inspiration\nwisecoco 6 inch 2K Flexible OLED Display IPS 2880 * 1440 Flexible Screen Curved Bendable Screen\n\n\n\n\ngraph TD\nA[Edge Device: Compute Unit] --&gt;|Hosts| B[VRM1 Character Layer]\nC[Whisper for Speech-to-Text running on GGML] -- Audio Processing --&gt; B\nB --&gt; D[Wisecoco 6-inch Flexible OLED Display in Portrait Mode]\nE[Microphone] -- Audio Input --&gt; C\n\n\n\n\n\nThis unit is a standard Linux amd64 computer that hosts the VRM1 Character Layer (B).\n\n\n\nThis module, running on GGML, captures audio input from the Microphone (E) and converts it into text.\n\n\n\nThe processed data from the Whisper module animates a virtual character in this layer. The character can be in speaking or idle mode.\n\n\n\nThe resulting texts are displayed on this screen.\n\nNote: Currently, the system only supports speaking and idle states. Other modes are not available.\n\nThe choice of portrait mode for the display aligns with the specific needs and constraints of the project. As the project heavily relies on text-based interactions, specifically transcriptions, portrait mode allows more lines of text to be visible at once, thereby improving the user experience.\nThe system utilizes a 6-inch flexible OLED display from Wisecoco. Portrait mode is more space-efficient in such scenarios, taking up less horizontal space while still providing ample vertical space for text display.\nGiven that the primary focus of the project is voice interactions, the display mode should ideally support easy reading of transcriptions. Portrait mode, with its vertical orientation, is more suited to this task as it mimics the natural top-to-bottom reading flow.\nAccording to the system diagram, the processed data from the Whisper for Speech-to-Text module running on GGML is used to animate a virtual character and display the resulting texts. These texts are likely to be dialog or conversation-based, and portrait mode would allow for a more coherent and continuous display of these text blocks."
   },
   {
-    "objectID": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html#negative-consequences",
-    "href": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html#negative-consequences",
-    "title": "Rejected: Iterate faster on WasGo prototype by using Godot 3.4",
+    "objectID": "decisions/20230908-bendable-screen-generative-assistant-ggml.html#overview",
+    "href": "decisions/20230908-bendable-screen-generative-assistant-ggml.html#overview",
+    "title": "Draft: Translation/Transcription Badge with GGML’s Whisper",
     "section": "",
-    "text": "May or may not be more expensive.\nTook too much effort to verify."
+    "text": "The project aims to develop a translation/transcription badge using GGML’s Whisper, a part of the GGML library that provides access to large language models (LLMs). The primary focus is on voice interactions."
   },
   {
-    "objectID": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html#option-graveyard",
-    "href": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html#option-graveyard",
-    "title": "Rejected: Iterate faster on WasGo prototype by using Godot 3.4",
+    "objectID": "decisions/20230908-bendable-screen-generative-assistant-ggml.html#key-features",
+    "href": "decisions/20230908-bendable-screen-generative-assistant-ggml.html#key-features",
+    "title": "Draft: Translation/Transcription Badge with GGML’s Whisper",
     "section": "",
-    "text": "Option: \nRejection Reason:"
+    "text": "Voice Interactions: The system will prioritize voice interactions, leveraging GGML’s Whisper capabilities to create a responsive AI. Python will not be used in this context.\nSpeech-to-Text Interface: A speech-to-text interface will be incorporated to process voice inputs effectively.\nDirect Connection to Compute Module: The display, set in portrait mode, will connect directly to the compute module, a standard Linux amd64 computer, eliminating the need for embedded software development.\nFlexible OLED Display: The system will utilize a 6-inch flexible OLED display from Wisecoco with a resolution of 2880*1440 at 60Hz refresh rate.\nNo Holograph Displays: The design will be streamlined and efficient, excluding holograph displays."
   },
   {
-    "objectID": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Rejected: Iterate faster on WasGo prototype by using Godot 3.4",
+    "objectID": "decisions/20230908-bendable-screen-generative-assistant-ggml.html#potential-challenges",
+    "href": "decisions/20230908-bendable-screen-generative-assistant-ggml.html#potential-challenges",
+    "title": "Draft: Translation/Transcription Badge with GGML’s Whisper",
     "section": "",
-    "text": "Coding strategy is not coding."
+    "text": "The project’s complexity and the expertise required in areas such as GGML, the Godot engine, and AI development pose significant challenges."
   },
   {
-    "objectID": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Rejected: Iterate faster on WasGo prototype by using Godot 3.4",
+    "objectID": "decisions/20230908-bendable-screen-generative-assistant-ggml.html#alternatives-not-considered",
+    "href": "decisions/20230908-bendable-screen-generative-assistant-ggml.html#alternatives-not-considered",
+    "title": "Draft: Translation/Transcription Badge with GGML’s Whisper",
     "section": "",
-    "text": "This is a V-Sekai strategy plan."
+    "text": "We have decided against integrating Python with GGML and using a pre-existing AI framework instead of developing one from scratch."
   },
   {
-    "objectID": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html#references",
-    "href": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html#references",
-    "title": "Rejected: Iterate faster on WasGo prototype by using Godot 3.4",
+    "objectID": "decisions/20230908-bendable-screen-generative-assistant-ggml.html#target-audience",
+    "href": "decisions/20230908-bendable-screen-generative-assistant-ggml.html#target-audience",
+    "title": "Draft: Translation/Transcription Badge with GGML’s Whisper",
     "section": "",
-    "text": "https://github.com/V-Sekai/WasGo"
+    "text": "The project may not be suitable for individuals without familiarity with GGML or a background in AI development."
   },
   {
-    "objectID": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html#derivative-license",
-    "href": "decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html#derivative-license",
-    "title": "Rejected: Iterate faster on WasGo prototype by using Godot 3.4",
+    "objectID": "decisions/20230908-bendable-screen-generative-assistant-ggml.html#development-strategy",
+    "href": "decisions/20230908-bendable-screen-generative-assistant-ggml.html#development-strategy",
+    "title": "Draft: Translation/Transcription Badge with GGML’s Whisper",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "The project will be developed in-house, utilizing our expertise in AI and game development."
   },
   {
-    "objectID": "decisions/20230108-wmf-video-playback.html",
-    "href": "decisions/20230108-wmf-video-playback.html",
-    "title": "Proposed: Add WMF for windows media playback",
+    "objectID": "decisions/20230908-bendable-screen-generative-assistant-ggml.html#further-reading",
+    "href": "decisions/20230908-bendable-screen-generative-assistant-ggml.html#further-reading",
+    "title": "Draft: Translation/Transcription Badge with GGML’s Whisper",
     "section": "",
-    "text": "Proposed: Add WMF for windows media playback\n\nContext and Problem Statement\nWe don’t have any good ways of playing video and also large 4k videos.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nAdd WMF support to godot for the windows platform.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nSee https://github.com/V-Sekai/godot/tree/wmf\n\n\nPositive Consequences\nCan play videos.\nOS platform supported playback will be hardware accelerated.\n\n\nNegative Consequences\nNo response\n\n\nOption graveyard\nNo response\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nIt’s not a few lines.\n\n\nIs there a reason why this should be core and done by us?\nI found this!\n\n\nReferences\n\nV-Sekai\n\n\n\nLicense of the contribution\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "For more information, please refer to these resources:\n\nV-Sekai\nGGML on GitHub\nWhisper JAX on GitHub\nTwitter inspiration\nwisecoco 6 inch 2K Flexible OLED Display IPS 2880 * 1440 Flexible Screen Curved Bendable Screen"
   },
   {
-    "objectID": "decisions/20211108-integrate-with-blender.html",
-    "href": "decisions/20211108-integrate-with-blender.html",
-    "title": "Proposed: Integrate with blender",
+    "objectID": "decisions/20230908-bendable-screen-generative-assistant-ggml.html#system-diagram",
+    "href": "decisions/20230908-bendable-screen-generative-assistant-ggml.html#system-diagram",
+    "title": "Draft: Translation/Transcription Badge with GGML’s Whisper",
     "section": "",
-    "text": "Status: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nBlend files are too difficult to write an importer for in Godot Engine.\n\n\n\nMake an addon that calls Blender directly and tell it to export to the proper place.\n\n\n\n\nEnable addon\nOpen blend\nSee the blend as a Godot Engine scene.\n\n\n\n\n\nIntegrates Blender into Godot Engine workflows.\nDownside of Blender version updates can be fixed by the use of the V-Sekai exporter tool.\n\n\n\n\n\nRequires blender to export cicd.\nChanges to the Blender version causes the project to desync.\n\n\n\n\n\nOption: \nRejection Reason: \n\n\n\n\n\nThis is a script but not a few lines.\n\n\n\n\nI know how to do this and others don’t.\n\n\n\n\nhttps://www.blender.org/\nhttps://github.com/V-Sekai/godot-blender\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "graph TD\nA[Edge Device: Compute Unit] --&gt;|Hosts| B[VRM1 Character Layer]\nC[Whisper for Speech-to-Text running on GGML] -- Audio Processing --&gt; B\nB --&gt; D[Wisecoco 6-inch Flexible OLED Display in Portrait Mode]\nE[Microphone] -- Audio Input --&gt; C"
   },
   {
-    "objectID": "decisions/20211108-integrate-with-blender.html#context-and-problem-statement",
-    "href": "decisions/20211108-integrate-with-blender.html#context-and-problem-statement",
-    "title": "Proposed: Integrate with blender",
+    "objectID": "decisions/20230908-bendable-screen-generative-assistant-ggml.html#system-diagram-explanation",
+    "href": "decisions/20230908-bendable-screen-generative-assistant-ggml.html#system-diagram-explanation",
+    "title": "Draft: Translation/Transcription Badge with GGML’s Whisper",
     "section": "",
-    "text": "Blend files are too difficult to write an importer for in Godot Engine."
+    "text": "This unit is a standard Linux amd64 computer that hosts the VRM1 Character Layer (B).\n\n\n\nThis module, running on GGML, captures audio input from the Microphone (E) and converts it into text.\n\n\n\nThe processed data from the Whisper module animates a virtual character in this layer. The character can be in speaking or idle mode.\n\n\n\nThe resulting texts are displayed on this screen.\n\nNote: Currently, the system only supports speaking and idle states. Other modes are not available.\n\nThe choice of portrait mode for the display aligns with the specific needs and constraints of the project. As the project heavily relies on text-based interactions, specifically transcriptions, portrait mode allows more lines of text to be visible at once, thereby improving the user experience.\nThe system utilizes a 6-inch flexible OLED display from Wisecoco. Portrait mode is more space-efficient in such scenarios, taking up less horizontal space while still providing ample vertical space for text display.\nGiven that the primary focus of the project is voice interactions, the display mode should ideally support easy reading of transcriptions. Portrait mode, with its vertical orientation, is more suited to this task as it mimics the natural top-to-bottom reading flow.\nAccording to the system diagram, the processed data from the Whisper for Speech-to-Text module running on GGML is used to animate a virtual character and display the resulting texts. These texts are likely to be dialog or conversation-based, and portrait mode would allow for a more coherent and continuous display of these text blocks."
   },
   {
-    "objectID": "decisions/20211108-integrate-with-blender.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20211108-integrate-with-blender.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: Integrate with blender",
+    "objectID": "decisions/20220222-rank-bone-names-with-transformer.html",
+    "href": "decisions/20220222-rank-bone-names-with-transformer.html",
+    "title": "Accepted: Rank skeleton #bone names with transformer4rec",
     "section": "",
-    "text": "Make an addon that calls Blender directly and tell it to export to the proper place."
+    "text": "Status: accepted \n\n\n\nImprove automatic #bone selection\n\n\n\nUse transformer4rec to rank bones.\n\n\n\n\nInvestigate\nlibtorch?\n\n\n\n\n\nWe can guess the proper name.\nUseful for the facial mapping problem?\nUseful for the character generator slider recommendation problem?\nGenerate test data by moving the character\nInference requires only single pose inputs.\n\n\n\n\n\nStarring at the abyss.\n\n\n\n\n\nOption:\n\nbpr from Quora\n\nRejection Reason:\n\nBpr from Quora is not used in production.\n\nOption:\n\ndlrm from facebook\n\nRejection Reason:\n\nToo difficult to run\n\nOption:\n\ncatboost\n\nRejection Reason:\n\nToo difficult to run\n\n\n\n\n\nNot a few lines of code.\n\n\n\nWe need this to make the quality of life of creators better.\n\n\n\n\nhttps://github.com/BayesWitnesses/m2cgen\nhttps://stackoverflow.com/questions/36071672/using-xgboost-in-c\nhttps://github.com/facebookresearch/dlrm\nhttps://medium.com/@marthawhite_81346/learning-with-the-criteo-tb-dataset-e3ec12d9d77e\nhttps://www.kaggle.com/c/criteo-display-ad-challenge/data\nSkeleton pool operator from neural blend shapes.\nhttps://tailor.fandom.com/wiki/Types_of_measurement\nhttps://knarkowicz.wordpress.com/2014/04/16/octahedron-normal-vector-encoding/\nhttps://www.kaggle.com/egordm/deep-learning-recommendation-model-dlrm\n\n    @article{li2021learning,\n    author = {Li, Peizhuo and Aberman, Kfir and Hanocka, Rana and Liu, Libin and Sorkine-Hornung, Olga and Chen, Baoquan},\n    title = {Learning Skeletal Articulations with Neural Blend Shapes},\n    journal = {ACM Transactions on Graphics (TOG)},\n    volume = {40},\n    number = {4},\n    pages = {1},\n    year = {2021},\n    publisher = {ACM}\n    }\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.\n\n\n\n\nSupersedes 20211031-use-bpr-to-rank-skeleton-bone-names"
   },
   {
-    "objectID": "decisions/20211108-integrate-with-blender.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20211108-integrate-with-blender.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Integrate with blender",
+    "objectID": "decisions/20220222-rank-bone-names-with-transformer.html#context-and-problem-statement",
+    "href": "decisions/20220222-rank-bone-names-with-transformer.html#context-and-problem-statement",
+    "title": "Accepted: Rank skeleton #bone names with transformer4rec",
     "section": "",
-    "text": "Enable addon\nOpen blend\nSee the blend as a Godot Engine scene."
+    "text": "Improve automatic #bone selection"
   },
   {
-    "objectID": "decisions/20211108-integrate-with-blender.html#positive-consequences",
-    "href": "decisions/20211108-integrate-with-blender.html#positive-consequences",
-    "title": "Proposed: Integrate with blender",
+    "objectID": "decisions/20220222-rank-bone-names-with-transformer.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20220222-rank-bone-names-with-transformer.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Accepted: Rank skeleton #bone names with transformer4rec",
     "section": "",
-    "text": "Integrates Blender into Godot Engine workflows.\nDownside of Blender version updates can be fixed by the use of the V-Sekai exporter tool."
+    "text": "Use transformer4rec to rank bones."
   },
   {
-    "objectID": "decisions/20211108-integrate-with-blender.html#negative-consequences",
-    "href": "decisions/20211108-integrate-with-blender.html#negative-consequences",
-    "title": "Proposed: Integrate with blender",
+    "objectID": "decisions/20220222-rank-bone-names-with-transformer.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20220222-rank-bone-names-with-transformer.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Accepted: Rank skeleton #bone names with transformer4rec",
     "section": "",
-    "text": "Requires blender to export cicd.\nChanges to the Blender version causes the project to desync."
+    "text": "Investigate\nlibtorch?"
   },
   {
-    "objectID": "decisions/20211108-integrate-with-blender.html#option-graveyard",
-    "href": "decisions/20211108-integrate-with-blender.html#option-graveyard",
-    "title": "Proposed: Integrate with blender",
+    "objectID": "decisions/20220222-rank-bone-names-with-transformer.html#positive-consequences",
+    "href": "decisions/20220222-rank-bone-names-with-transformer.html#positive-consequences",
+    "title": "Accepted: Rank skeleton #bone names with transformer4rec",
     "section": "",
-    "text": "Option: \nRejection Reason:"
+    "text": "We can guess the proper name.\nUseful for the facial mapping problem?\nUseful for the character generator slider recommendation problem?\nGenerate test data by moving the character\nInference requires only single pose inputs."
   },
   {
-    "objectID": "decisions/20211108-integrate-with-blender.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20211108-integrate-with-blender.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Integrate with blender",
+    "objectID": "decisions/20220222-rank-bone-names-with-transformer.html#negative-consequences",
+    "href": "decisions/20220222-rank-bone-names-with-transformer.html#negative-consequences",
+    "title": "Accepted: Rank skeleton #bone names with transformer4rec",
     "section": "",
-    "text": "This is a script but not a few lines."
+    "text": "Starring at the abyss."
   },
   {
-    "objectID": "decisions/20211108-integrate-with-blender.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20211108-integrate-with-blender.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Integrate with blender",
+    "objectID": "decisions/20220222-rank-bone-names-with-transformer.html#option-graveyard",
+    "href": "decisions/20220222-rank-bone-names-with-transformer.html#option-graveyard",
+    "title": "Accepted: Rank skeleton #bone names with transformer4rec",
     "section": "",
-    "text": "I know how to do this and others don’t."
+    "text": "Option:\n\nbpr from Quora\n\nRejection Reason:\n\nBpr from Quora is not used in production.\n\nOption:\n\ndlrm from facebook\n\nRejection Reason:\n\nToo difficult to run\n\nOption:\n\ncatboost\n\nRejection Reason:\n\nToo difficult to run"
   },
   {
-    "objectID": "decisions/20211108-integrate-with-blender.html#references",
-    "href": "decisions/20211108-integrate-with-blender.html#references",
-    "title": "Proposed: Integrate with blender",
+    "objectID": "decisions/20220222-rank-bone-names-with-transformer.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20220222-rank-bone-names-with-transformer.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Accepted: Rank skeleton #bone names with transformer4rec",
     "section": "",
-    "text": "https://www.blender.org/\nhttps://github.com/V-Sekai/godot-blender"
+    "text": "Not a few lines of code."
   },
   {
-    "objectID": "decisions/20211108-integrate-with-blender.html#derivative-license",
-    "href": "decisions/20211108-integrate-with-blender.html#derivative-license",
-    "title": "Proposed: Integrate with blender",
+    "objectID": "decisions/20220222-rank-bone-names-with-transformer.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20220222-rank-bone-names-with-transformer.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Accepted: Rank skeleton #bone names with transformer4rec",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "We need this to make the quality of life of creators better."
   },
   {
-    "objectID": "decisions/20230502-add-iree-to-godot-engine-for-image-superresolution.html",
-    "href": "decisions/20230502-add-iree-to-godot-engine-for-image-superresolution.html",
-    "title": "Accepted: Adding IREE to Godot Engine for Image Superresolution",
+    "objectID": "decisions/20220222-rank-bone-names-with-transformer.html#references",
+    "href": "decisions/20220222-rank-bone-names-with-transformer.html#references",
+    "title": "Accepted: Rank skeleton #bone names with transformer4rec",
     "section": "",
-    "text": "Accepted: Adding IREE to Godot Engine for Image Superresolution\n\nMetadata\n\nStatus: accepted \nDeciders: V-Sekai,fire,\nTags: V-Sekai, IREE, Godot Engine, Image Superresolution, Vulkan Backend,chatgpt 4,Google,\n\n\n\nContext and Problem Statement\nV-Sekai currently faces a limitation in the quality of upscaled images, particularly when the image needs to be magnified by a factor of 4x or more.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nIntegrate the Intermediate Representation Execution Environment (IREE) into the Godot Engine 4.0 as a C++ GDExtension. Utilize the Vulkan backend to run an image superresolution demo that generates 4x larger images. IREE is an MLIR-based end-to-end compiler and runtime that lowers Machine Learning (ML) models to a unified IR, allowing for better performance and scaling.\n\n\nDescribe how your proposal will work with code, pseudo-code, mock-ups, or diagrams\n\nCompile IREE as a C++ GDExtension for Godot Engine 4.0.\nUse the Vulkan backend to run the image superresolution demo.\nLoad and process ML models for image superresolution using IREE.\nIntegrate the resulting functionality into V-Sekai’s existing image processing pipeline.\n\n\n\nPositive Consequences\n\nAllow image superresolution in V-Sekai.\nEnhanced performance due to IREE’s efficient MLIR-based compiler and runtime.\nScalable solution that adapts to various hardware and software constraints. Not only NVIDIA, but ARM, Intel, AMD and Apple gpus.\nAllow using other machine learning models from PyTorch and Tensorflow\n\n\n\nNegative Consequences\n\nAdditional development time required for integration and optimization.\nPotential trade-offs in implementing other features.\n\n\n\nOption graveyard\n\nUse a custom script to work around the image superresolution issue.\n\nThis might not provide a scalable or high-performance solution.\n\nImplement a different image superresolution algorithm.\n\nThis could lead to suboptimal results compared to IREE’s capabilities.\n\n\n\n\nIf this enhancement will be used infrequently, can it be worked around with a few lines of script?\nA custom script could serve as a workaround for infrequent use of image superresolution, but it may have drawbacks in terms of efficiency, output quality, and maintenance efforts. If the feature aligns with V-Sekai’s goals and significantly improves user experience, integrating the IREE-based solution into the core might be more effective.\n\n\nIs there a reason why this should be core and done by us?\nIn summary, integrating the IREE-based image superresolution feature into V-Sekai’s core offers several benefits, including an enhanced user experience, performance optimization, alignment with open source values, and easier maintenance and support. These advantages contribute to a better, more immersive VR experience while staying true to V-Sekai’s project goals.\n\n\nReferences\n\nV-Sekai: https://v-sekai.org/\nIREE (Intermediate Representation Execution Environment): https://github.com/openxla/iree\nGodot Engine: https://godotengine.org\nVulkan Backend: https://www.khronos.org/vulkan/\nIREE.gd: https://github.com/RechieKho/IREE.gd"
+    "text": "https://github.com/BayesWitnesses/m2cgen\nhttps://stackoverflow.com/questions/36071672/using-xgboost-in-c\nhttps://github.com/facebookresearch/dlrm\nhttps://medium.com/@marthawhite_81346/learning-with-the-criteo-tb-dataset-e3ec12d9d77e\nhttps://www.kaggle.com/c/criteo-display-ad-challenge/data\nSkeleton pool operator from neural blend shapes.\nhttps://tailor.fandom.com/wiki/Types_of_measurement\nhttps://knarkowicz.wordpress.com/2014/04/16/octahedron-normal-vector-encoding/\nhttps://www.kaggle.com/egordm/deep-learning-recommendation-model-dlrm\n\n    @article{li2021learning,\n    author = {Li, Peizhuo and Aberman, Kfir and Hanocka, Rana and Liu, Libin and Sorkine-Hornung, Olga and Chen, Baoquan},\n    title = {Learning Skeletal Articulations with Neural Blend Shapes},\n    journal = {ACM Transactions on Graphics (TOG)},\n    volume = {40},\n    number = {4},\n    pages = {1},\n    year = {2021},\n    publisher = {ACM}\n    }"
   },
   {
-    "objectID": "decisions/20230415-procedural-variations-props-envs-avatars.html",
-    "href": "decisions/20230415-procedural-variations-props-envs-avatars.html",
-    "title": "Proposed: Procedurally create variations for our props, environments and avatars",
+    "objectID": "decisions/20220222-rank-bone-names-with-transformer.html#derivative-license",
+    "href": "decisions/20220222-rank-bone-names-with-transformer.html#derivative-license",
+    "title": "Accepted: Rank skeleton #bone names with transformer4rec",
     "section": "",
-    "text": "Proposed: Procedurally create variations for our props, environments and avatars\n\nMetadata\n\nStatus: proposed \nDeciders: V-Sekai,fire,\nTags: V-Sekai,chatgp4,\n\n\n\nContext and Problem Statement\nLack of variety and customization in V-Sekai’s 3D props, environments, and avatars.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nIntroducing a procedural generator for 3D props, environments, and avatars in V-Sekai will significantly enhance user experience by offering a broad range of customizable options. Procedural generation is an algorithmic method of content creation that replaces manual design, resulting in a larger array of unique combinations.\nThe procedural generator can be developed using a mix of algorithms, libraries, and assets to produce a vast assortment of variations for props, environments, and avatars. Users’ input parameters, such as prop type, color, size, and material, will guide the generator in crafting distinctive content.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\ngraph TD\n  A[Prop Type] --&gt; B(Select Base Model)\n  A[Prop Type] --&gt; C(Apply Procedural Variations)\n  A[Prop Type] --&gt; D(Combine Variations)\n  B --&gt; E(Base Model)\n  C --&gt; F(Shape Variation)\n  C --&gt; G(Color Variation)\n  C --&gt; H(Texture Variation)\n  F --&gt; I(Combined Variations)\n  G --&gt; I(Combined Variations)\n  H --&gt; I(Combined Variations)\n  E --&gt; I(Combined Variations)\n  I --&gt; J(Final Output)\nThis flowchart demonstrates the procedural generation process using the following steps:\n\nUser Input Parameters: Users provide their preferences for prop type, color, size, and material.\nSelect Base Model: The generator selects a base model corresponding to the chosen prop type.\nApply Procedural Variations: The generator applies algorithmic variations to the base model, modifying its shape, color, and texture based on user input.\nCombine Variations: The generator combines these variations to create a unique prop with the specified properties.\nGenerate Unique Prop, Environment, or Avatar: The final output is a unique prop, environment, or avatar that meets the user’s preferences.\n\nThis approach increases the variety and customization options in V-Sekai, enhancing the platform’s appeal and offering a more engaging experience for users.\n\n\nPositive Consequences\n\nEnhanced variety: Procedural generation enables a wide array of unique content, delivering a diverse and constantly evolving experience for users.\nUser personalization: By incorporating user preferences, the generator can produce content that aligns with individual tastes and needs.\nEfficient resource utilization: Procedural content generation minimizes the need for manual design and asset creation, leading to a more cost-effective platform.\n\n\n\nNegative Consequences\n\nComplexity: Developing a procedural generator can be intricate, necessitating expertise in algorithms, 3D modeling, and other technical domains.\nPerformance impact: Real-time content generation might affect performance, particularly if algorithms are not optimized or if the platform experiences high user traffic.\n\n\n\nOption graveyard\nDo nothing.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nThis is a few lines of code.\n\n\nIs there a reason why this should be core and done by us?\nWe care about v-sekai more than others.\n\n\nReferences\n\nV-Sekai"
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230125-two-groups-battle-demo.html",
-    "href": "decisions/20230125-two-groups-battle-demo.html",
-    "title": "Proposed: Have two groups move towards each other battle demo",
+    "objectID": "decisions/20220222-rank-bone-names-with-transformer.html#links",
+    "href": "decisions/20220222-rank-bone-names-with-transformer.html#links",
+    "title": "Accepted: Rank skeleton #bone names with transformer4rec",
     "section": "",
-    "text": "Status: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\n\nWe need a demo of our work.\n\n\n\nMake a game out of having two groups attack each other.\n\n\n\n\nCreate two groups: mass A and mass B\nImplement pathfinding for both groups to find each other\nAdd avoidance behavior to prevent collisions between group members\nImplement attack functionality when groups are in range\n\nfunction createGroups() {\n  massA = createGroupA();\n  massB = createGroupB();\n}\n\nfunction update() {\n  pathfind(massA, massB);\n  pathfind(massB, massA);\n\n  avoidance(massA);\n  avoidance(massB);\n\n  attack(massA, massB);\n  attack(massB, massA);\n}\n\n\n\n\nCan use WebAssembly (WASM) scripting\nIn-game tablet drag to place objects\n\n\n\n\nWe are able to use V-Sekai easier.\n\n\n\n\n\nWe cannot get other features in.\n\n\n\n\n\nOption: The status quo.\nRejection Reason: This solves nothing.\n\n\n\n\nThis is an integration test.\n\n\n\nIt helps us focus.\n\n\n\n\nV-Sekai\nrenown"
+    "text": "Supersedes 20211031-use-bpr-to-rank-skeleton-bone-names"
   },
   {
-    "objectID": "decisions/20230125-two-groups-battle-demo.html#additional-features-for-the-test",
-    "href": "decisions/20230125-two-groups-battle-demo.html#additional-features-for-the-test",
-    "title": "Proposed: Have two groups move towards each other battle demo",
+    "objectID": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html",
+    "href": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html",
+    "title": "Accepted: Aquarium Nightclub Booth for Virtual Market Exhibition",
     "section": "",
-    "text": "Can use WebAssembly (WASM) scripting\nIn-game tablet drag to place objects\n\n\n\n\nWe are able to use V-Sekai easier.\n\n\n\n\n\nWe cannot get other features in.\n\n\n\n\n\nOption: The status quo.\nRejection Reason: This solves nothing.\n\n\n\n\nThis is an integration test.\n\n\n\nIt helps us focus.\n\n\n\n\nV-Sekai\nrenown"
+    "text": "Status: accepted \nDeciders: V-Sekai, fire, etc, Aeris, cyberpunkmermaid,\nTags: V-Sekai, GPT-4, Virtual Reality, Cocoon Art Aquarium, VKET 2023 Summer, Voiceless,\n\n\n\n\nDesign a 4m x 4m x 5m Aquarium Nightclub themed booth.\n\n\n\nCreate an immersive environment combining aquarium and nightclub elements, including aquatic decorations, lighting, interactivity, a hostess, and ambient music.\n\n\n\nAquatic-themed decorations: Use 3D models of marine life, such as fish, corals, and seaweed, to create a colorful underwater environment.\nImplement the ambience of a nightclub.\nInteractive elements: Add interactive components, such as touch-sensitive screens or motion sensors, to allow visitors to interact with the marine life and control the lighting effects.\nJellyfish Hostess:\n\nJellyBell: Enchanting hostess engaging visitors in the booth experience.\nIridescent Gown: Amplifies her aquatic charm with sheer fabric and ribbons\n\nAmbient music: Include background music that complements the aquarium and nightclub themes.\n\n\n\n\n\n\nDesign and model 3D assets.\nImplement interactive elements.\nAdd hostess character.\nIntegrate ambient music.\n\n\n\n\n\nUnique and engaging theme attracts visitors.\nImmersive experience combines education and entertainment.\nEncourages interaction and exploration.\nHostess enhances visitor engagement.\n\n\n\n\n\nRequires significant development time and resources.\nBalancing two themes may be challenging.\nIntegrating dynamic lighting and shaders may require extra effort.\n\n\n\n\n\nStatic environment without interactivity.\nFocusing on one theme only.\n\n\n\n\nNo, requires significant design and development work.\n\n\n\nCreating a unique booth is essential for attracting visitors and showcasing VR development capabilities.\n\n\n\n\nV-Sekai\nVKET 2023 Summer\nSilent’s Cel Shading Shader"
   },
   {
-    "objectID": "decisions/20230125-grow-the-community-with-a-reactive-discord-bot.html",
-    "href": "decisions/20230125-grow-the-community-with-a-reactive-discord-bot.html",
-    "title": "Proposed: Grow the community with a reactive Discord bot.",
+    "objectID": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html#metadata",
+    "href": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html#metadata",
+    "title": "Accepted: Aquarium Nightclub Booth for Virtual Market Exhibition",
     "section": "",
-    "text": "Proposed: Grow the community with a reactive Discord bot.\n\nMetadata\n\nStatus: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nContext and Problem Statement\nV-Sekai discord is cumbersome to use.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nGrant the “Member” role to all members who click a reaction from the Discord bot.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nWe need to review the code and set up a runner in kubernetes.\n\n\nPositive Consequences\nWe are able to use the community easier.\n\n\nNegative Consequences\nWe cannot get other features in.\n\n\nOption graveyard\n\nOption: The status quo. \nRejection Reason: This solves nothing. \nOption: Use discord’s standard moderation tools with mass ban. \nRejection Reason: This is actually a good feature. Need to re-evaluate. \n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nKnowing what to do is hard.\n\n\nIs there a reason why this should be core and done by us?\nWe administrate the V-Sekai Discord.\n\n\nReferences\n\nV-Sekai\nVSona"
+    "text": "Status: accepted \nDeciders: V-Sekai, fire, etc, Aeris, cyberpunkmermaid,\nTags: V-Sekai, GPT-4, Virtual Reality, Cocoon Art Aquarium, VKET 2023 Summer, Voiceless,"
   },
   {
-    "objectID": "decisions/20220113-change-transform-by-crdt.html",
-    "href": "decisions/20220113-change-transform-by-crdt.html",
-    "title": "Proposal: Change transform by CRDT.",
+    "objectID": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html#context-and-problem-statement",
+    "href": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html#context-and-problem-statement",
+    "title": "Accepted: Aquarium Nightclub Booth for Virtual Market Exhibition",
     "section": "",
-    "text": "Status: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nChange transform and resolve conflict.\n\n\n\n???\n\n\n\n???\n\n\n\n\n???\n\n\n\n\n\n???\n\n\n\n\n\nOption: Status quo\nRejection Reason: ???\n\n\n\n\nNot small.\n\n\n\n\nResearch.\n\n\n\n\n\nhttps://github.com/gritzko/ron\nDescribed in Webaverse.\n\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Design a 4m x 4m x 5m Aquarium Nightclub themed booth."
   },
   {
-    "objectID": "decisions/20220113-change-transform-by-crdt.html#context-and-problem-statement",
-    "href": "decisions/20220113-change-transform-by-crdt.html#context-and-problem-statement",
-    "title": "Proposal: Change transform by CRDT.",
+    "objectID": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html#proposed-solution",
+    "href": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html#proposed-solution",
+    "title": "Accepted: Aquarium Nightclub Booth for Virtual Market Exhibition",
     "section": "",
-    "text": "Change transform and resolve conflict."
+    "text": "Create an immersive environment combining aquarium and nightclub elements, including aquatic decorations, lighting, interactivity, a hostess, and ambient music.\n\n\n\nAquatic-themed decorations: Use 3D models of marine life, such as fish, corals, and seaweed, to create a colorful underwater environment.\nImplement the ambience of a nightclub.\nInteractive elements: Add interactive components, such as touch-sensitive screens or motion sensors, to allow visitors to interact with the marine life and control the lighting effects.\nJellyfish Hostess:\n\nJellyBell: Enchanting hostess engaging visitors in the booth experience.\nIridescent Gown: Amplifies her aquatic charm with sheer fabric and ribbons\n\nAmbient music: Include background music that complements the aquarium and nightclub themes."
   },
   {
-    "objectID": "decisions/20220113-change-transform-by-crdt.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20220113-change-transform-by-crdt.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposal: Change transform by CRDT.",
+    "objectID": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html#implementation",
+    "href": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html#implementation",
+    "title": "Accepted: Aquarium Nightclub Booth for Virtual Market Exhibition",
     "section": "",
-    "text": "???"
+    "text": "Design and model 3D assets.\nImplement interactive elements.\nAdd hostess character.\nIntegrate ambient music."
   },
   {
-    "objectID": "decisions/20220113-change-transform-by-crdt.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20220113-change-transform-by-crdt.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposal: Change transform by CRDT.",
+    "objectID": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html#positive-consequences",
+    "href": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html#positive-consequences",
+    "title": "Accepted: Aquarium Nightclub Booth for Virtual Market Exhibition",
     "section": "",
-    "text": "???"
+    "text": "Unique and engaging theme attracts visitors.\nImmersive experience combines education and entertainment.\nEncourages interaction and exploration.\nHostess enhances visitor engagement."
   },
   {
-    "objectID": "decisions/20220113-change-transform-by-crdt.html#positive-consequences",
-    "href": "decisions/20220113-change-transform-by-crdt.html#positive-consequences",
-    "title": "Proposal: Change transform by CRDT.",
+    "objectID": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html#negative-consequences",
+    "href": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html#negative-consequences",
+    "title": "Accepted: Aquarium Nightclub Booth for Virtual Market Exhibition",
     "section": "",
-    "text": "???"
+    "text": "Requires significant development time and resources.\nBalancing two themes may be challenging.\nIntegrating dynamic lighting and shaders may require extra effort."
   },
   {
-    "objectID": "decisions/20220113-change-transform-by-crdt.html#negative-consequences",
-    "href": "decisions/20220113-change-transform-by-crdt.html#negative-consequences",
-    "title": "Proposal: Change transform by CRDT.",
+    "objectID": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html#option-graveyard",
+    "href": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html#option-graveyard",
+    "title": "Accepted: Aquarium Nightclub Booth for Virtual Market Exhibition",
     "section": "",
-    "text": "???"
+    "text": "Static environment without interactivity.\nFocusing on one theme only."
   },
   {
-    "objectID": "decisions/20220113-change-transform-by-crdt.html#option-graveyard",
-    "href": "decisions/20220113-change-transform-by-crdt.html#option-graveyard",
-    "title": "Proposal: Change transform by CRDT.",
+    "objectID": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Accepted: Aquarium Nightclub Booth for Virtual Market Exhibition",
     "section": "",
-    "text": "Option: Status quo\nRejection Reason: ???"
+    "text": "No, requires significant design and development work."
   },
   {
-    "objectID": "decisions/20220113-change-transform-by-crdt.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20220113-change-transform-by-crdt.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposal: Change transform by CRDT.",
+    "objectID": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Accepted: Aquarium Nightclub Booth for Virtual Market Exhibition",
     "section": "",
-    "text": "Not small."
+    "text": "Creating a unique booth is essential for attracting visitors and showcasing VR development capabilities."
   },
   {
-    "objectID": "decisions/20220113-change-transform-by-crdt.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20220113-change-transform-by-crdt.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposal: Change transform by CRDT.",
+    "objectID": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html#references",
+    "href": "decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html#references",
+    "title": "Accepted: Aquarium Nightclub Booth for Virtual Market Exhibition",
     "section": "",
-    "text": "Research."
+    "text": "V-Sekai\nVKET 2023 Summer\nSilent’s Cel Shading Shader"
   },
   {
-    "objectID": "decisions/20220113-change-transform-by-crdt.html#references",
-    "href": "decisions/20220113-change-transform-by-crdt.html#references",
-    "title": "Proposal: Change transform by CRDT.",
+    "objectID": "decisions/20230522-JOKE-fictional-blood-combat.html",
+    "href": "decisions/20230522-JOKE-fictional-blood-combat.html",
+    "title": "Rejected: Defeating your fictional enemies in their blood",
     "section": "",
-    "text": "https://github.com/gritzko/ron\nDescribed in Webaverse."
+    "text": "Propose a solution to enhance realism in enemy defeat simulations.\n\n\n\nStatus: rejected \nDeciders: V-Sekai\nTags: V-Sekai, GPT-4, joke,\n\n\n\n\nGaming often involves defeating enemies, but current blood effects lack realism and immersion.\n\n\n\nImplement a realistic blood simulation system considering factors like enemy type, weapon, and environment.\n\n\n\n\nBlood simulation system: Develop a system generating realistic blood effects.\nIntegration: Ensure compatibility with existing game mechanics.\nOptimization: Minimize performance impact.\nTesting & refinement: Test extensively and refine based on feedback.\n\n\n\n\n\nEnhanced realism and immersion\nImproved visual effects\nIncreased player satisfaction\n\n\n\n\n\nIncreased development time and resources\nPotential performance issues\nUnsuitability for some games or audiences\n\n\n\n\n\nSimpler blood effect system\nPre-rendered blood effects only\n\n\n\n\nNo, significant development effort is required.\n\n\n\nEasier integration, optimization, control, and refinement as part of the core game engine.\n\n\n\n\nV-Sekai"
   },
   {
-    "objectID": "decisions/20220113-change-transform-by-crdt.html#derivative-license",
-    "href": "decisions/20220113-change-transform-by-crdt.html#derivative-license",
-    "title": "Proposal: Change transform by CRDT.",
+    "objectID": "decisions/20230522-JOKE-fictional-blood-combat.html#metadata",
+    "href": "decisions/20230522-JOKE-fictional-blood-combat.html#metadata",
+    "title": "Rejected: Defeating your fictional enemies in their blood",
     "section": "",
-    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Status: rejected \nDeciders: V-Sekai\nTags: V-Sekai, GPT-4, joke,"
   },
   {
-    "objectID": "decisions/20240330-gitlab-helm.html",
-    "href": "decisions/20240330-gitlab-helm.html",
-    "title": "Proposed: Integrating Helm for Kubernetes Runner Installation with S3 Cache",
+    "objectID": "decisions/20230522-JOKE-fictional-blood-combat.html#context-and-problem-statement",
+    "href": "decisions/20230522-JOKE-fictional-blood-combat.html#context-and-problem-statement",
+    "title": "Rejected: Defeating your fictional enemies in their blood",
     "section": "",
-    "text": "The V-Sekai project, focused on integrating social VR capabilities into the Godot Engine, necessitates a flexible and scalable CI/CD infrastructure to manage the development workflow across various environments effectively. Given the diversity of platforms our contributors use, including Linux, macOS, Windows, Docker, and Kubernetes, there is a critical need to standardize our CI/CD processes to ensure consistency and efficiency.\n\n\n\nThe current CI/CD setup at V-Sekai lacks a unified approach to deploying and managing runners in Kubernetes clusters, leading to potential inconsistencies in build and test environments. This fragmentation could slow down the development pipeline and impact the project’s ability to iterate rapidly on new features.\n\n\n\nWe propose to enhance our CI/CD pipeline by integrating Helm to streamline the installation and management of GitLab Runners in our Kubernetes clusters. Additionally, we will configure the runners to use S3 (Digital Ocean Spaces) as a cache, improving build times and reducing network traffic. Here’s how we plan to implement this solution:\n\n\nEnsure Helm is installed on your system. Helm will be used to deploy GitLab Runner instances as Helm charts, providing an easy and scalable way to manage runners within Kubernetes clusters.\ncurl https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3 | bash\n\n\n\nAdd the GitLab Runner Helm chart repository to your Helm setup. This repository contains the necessary templates for deploying GitLab Runners in a Kubernetes cluster.\nhelm repo add gitlab https://charts.gitlab.io/\nhelm repo update\n\n\n\nUpdate your values.yaml file with the following values to switch to the Ubuntu-based image and configure S3 as a cache:\n# Specify the Ubuntu image. Remember to set the version. You can also use the `ubuntu` or `latest` tags.\nimage: gitlab/gitlab-runner:v16.5.0\n\n# Update the security context values to the user ID in the ubuntu image\nsecurityContext:\n  fsGroup: 999\n  runAsUser: 999\n\n# Configure S3 as a cache\nrunners:\n  config: |\n    [[runners]]\n      [runners.kubernetes]\n        image = \"ubuntu:22.04\"\n      [runners.cache]\n        Type = \"s3\"\n        Path = \"runner\"\n        Shared = true\n        [runners.cache.s3]\n          ServerAddress = \"s3.amazonaws.com\"\n          BucketName = \"my_bucket_name\"\n          BucketLocation = \"eu-west-1\"\n          Insecure = false\n          AuthenticationType = \"access-key\"\n  cache:\n    secretName: s3access\n\n\n\nCreate an s3access Kubernetes secret that contains your access key and secret key:\nkubectl create secret generic s3access --from-literal=accesskey=\"YourAccessKey\" --from-literal=secretkey=\"YourSecretKey\"\n\n\n\nDeploy the GitLab Runner using Helm with the customized values.yaml file.\nhelm install gitlab-runner gitlab/gitlab-runner -f values.yaml\nEnsure to replace https://gitlab.example.com/ with your GitLab instance URL and \"REGISTRATION_TOKEN\" with your actual registration token.\n\n\n\n\n\nScalable and Efficient CI/CD: Leveraging Kubernetes for CI/CD runners allows for dynamic scaling based on the workload, improving resource efficiency.\nConsistency Across Environments: Using Helm charts for deployment ensures consistent environments for all CI/CD pipelines, reducing “it works on my machine” issues.\nImproved Build Times and Reduced Network Traffic: By using S3 as a cache, build times can be significantly reduced and network traffic minimized.\n\n\n\n\n\nComplexity: The initial setup and configuration may require a deep understanding of Kubernetes and Helm, posing a learning curve for some team members.\nMaintenance: Ongoing maintenance of Helm charts could increase operational overhead.\n\n\n\n\n\nManual Runner Installation: Avoided due to its lack of scalability and increased potential for configuration errors.\n\n\n\n\n\nTemporary or One-off CI/CD Tasks: For tasks that do not justify the overhead of Kubernetes runners, alternative, simpler CI/CD solutions might be temporarily employed.\n\n\n\n\nThis initiative aligns with our core mission of developing social VR capabilities within the Godot Engine. The V-Sekai development team will lead this project, ensuring it meets our technical standards and project goals.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai, CI/CD, Kubernetes, Helm, S3 Cache\n\n\n\n\n\nHelm Documentation\nGitLab Runner Helm Chart\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAssisted by Aria, your AI assistant."
+    "text": "Gaming often involves defeating enemies, but current blood effects lack realism and immersion."
   },
   {
-    "objectID": "decisions/20240330-gitlab-helm.html#context",
-    "href": "decisions/20240330-gitlab-helm.html#context",
-    "title": "Proposed: Integrating Helm for Kubernetes Runner Installation with S3 Cache",
+    "objectID": "decisions/20230522-JOKE-fictional-blood-combat.html#proposed-solution",
+    "href": "decisions/20230522-JOKE-fictional-blood-combat.html#proposed-solution",
+    "title": "Rejected: Defeating your fictional enemies in their blood",
     "section": "",
-    "text": "The V-Sekai project, focused on integrating social VR capabilities into the Godot Engine, necessitates a flexible and scalable CI/CD infrastructure to manage the development workflow across various environments effectively. Given the diversity of platforms our contributors use, including Linux, macOS, Windows, Docker, and Kubernetes, there is a critical need to standardize our CI/CD processes to ensure consistency and efficiency."
+    "text": "Implement a realistic blood simulation system considering factors like enemy type, weapon, and environment."
   },
   {
-    "objectID": "decisions/20240330-gitlab-helm.html#problem-statement",
-    "href": "decisions/20240330-gitlab-helm.html#problem-statement",
-    "title": "Proposed: Integrating Helm for Kubernetes Runner Installation with S3 Cache",
+    "objectID": "decisions/20230522-JOKE-fictional-blood-combat.html#implementation",
+    "href": "decisions/20230522-JOKE-fictional-blood-combat.html#implementation",
+    "title": "Rejected: Defeating your fictional enemies in their blood",
     "section": "",
-    "text": "The current CI/CD setup at V-Sekai lacks a unified approach to deploying and managing runners in Kubernetes clusters, leading to potential inconsistencies in build and test environments. This fragmentation could slow down the development pipeline and impact the project’s ability to iterate rapidly on new features."
+    "text": "Blood simulation system: Develop a system generating realistic blood effects.\nIntegration: Ensure compatibility with existing game mechanics.\nOptimization: Minimize performance impact.\nTesting & refinement: Test extensively and refine based on feedback."
   },
   {
-    "objectID": "decisions/20240330-gitlab-helm.html#proposed-solution",
-    "href": "decisions/20240330-gitlab-helm.html#proposed-solution",
-    "title": "Proposed: Integrating Helm for Kubernetes Runner Installation with S3 Cache",
+    "objectID": "decisions/20230522-JOKE-fictional-blood-combat.html#positive-consequences",
+    "href": "decisions/20230522-JOKE-fictional-blood-combat.html#positive-consequences",
+    "title": "Rejected: Defeating your fictional enemies in their blood",
     "section": "",
-    "text": "We propose to enhance our CI/CD pipeline by integrating Helm to streamline the installation and management of GitLab Runners in our Kubernetes clusters. Additionally, we will configure the runners to use S3 (Digital Ocean Spaces) as a cache, improving build times and reducing network traffic. Here’s how we plan to implement this solution:\n\n\nEnsure Helm is installed on your system. Helm will be used to deploy GitLab Runner instances as Helm charts, providing an easy and scalable way to manage runners within Kubernetes clusters.\ncurl https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3 | bash\n\n\n\nAdd the GitLab Runner Helm chart repository to your Helm setup. This repository contains the necessary templates for deploying GitLab Runners in a Kubernetes cluster.\nhelm repo add gitlab https://charts.gitlab.io/\nhelm repo update\n\n\n\nUpdate your values.yaml file with the following values to switch to the Ubuntu-based image and configure S3 as a cache:\n# Specify the Ubuntu image. Remember to set the version. You can also use the `ubuntu` or `latest` tags.\nimage: gitlab/gitlab-runner:v16.5.0\n\n# Update the security context values to the user ID in the ubuntu image\nsecurityContext:\n  fsGroup: 999\n  runAsUser: 999\n\n# Configure S3 as a cache\nrunners:\n  config: |\n    [[runners]]\n      [runners.kubernetes]\n        image = \"ubuntu:22.04\"\n      [runners.cache]\n        Type = \"s3\"\n        Path = \"runner\"\n        Shared = true\n        [runners.cache.s3]\n          ServerAddress = \"s3.amazonaws.com\"\n          BucketName = \"my_bucket_name\"\n          BucketLocation = \"eu-west-1\"\n          Insecure = false\n          AuthenticationType = \"access-key\"\n  cache:\n    secretName: s3access\n\n\n\nCreate an s3access Kubernetes secret that contains your access key and secret key:\nkubectl create secret generic s3access --from-literal=accesskey=\"YourAccessKey\" --from-literal=secretkey=\"YourSecretKey\"\n\n\n\nDeploy the GitLab Runner using Helm with the customized values.yaml file.\nhelm install gitlab-runner gitlab/gitlab-runner -f values.yaml\nEnsure to replace https://gitlab.example.com/ with your GitLab instance URL and \"REGISTRATION_TOKEN\" with your actual registration token."
+    "text": "Enhanced realism and immersion\nImproved visual effects\nIncreased player satisfaction"
   },
   {
-    "objectID": "decisions/20240330-gitlab-helm.html#benefits",
-    "href": "decisions/20240330-gitlab-helm.html#benefits",
-    "title": "Proposed: Integrating Helm for Kubernetes Runner Installation with S3 Cache",
+    "objectID": "decisions/20230522-JOKE-fictional-blood-combat.html#negative-consequences",
+    "href": "decisions/20230522-JOKE-fictional-blood-combat.html#negative-consequences",
+    "title": "Rejected: Defeating your fictional enemies in their blood",
     "section": "",
-    "text": "Scalable and Efficient CI/CD: Leveraging Kubernetes for CI/CD runners allows for dynamic scaling based on the workload, improving resource efficiency.\nConsistency Across Environments: Using Helm charts for deployment ensures consistent environments for all CI/CD pipelines, reducing “it works on my machine” issues.\nImproved Build Times and Reduced Network Traffic: By using S3 as a cache, build times can be significantly reduced and network traffic minimized."
+    "text": "Increased development time and resources\nPotential performance issues\nUnsuitability for some games or audiences"
   },
   {
-    "objectID": "decisions/20240330-gitlab-helm.html#downsides",
-    "href": "decisions/20240330-gitlab-helm.html#downsides",
-    "title": "Proposed: Integrating Helm for Kubernetes Runner Installation with S3 Cache",
+    "objectID": "decisions/20230522-JOKE-fictional-blood-combat.html#option-graveyard",
+    "href": "decisions/20230522-JOKE-fictional-blood-combat.html#option-graveyard",
+    "title": "Rejected: Defeating your fictional enemies in their blood",
     "section": "",
-    "text": "Complexity: The initial setup and configuration may require a deep understanding of Kubernetes and Helm, posing a learning curve for some team members.\nMaintenance: Ongoing maintenance of Helm charts could increase operational overhead."
+    "text": "Simpler blood effect system\nPre-rendered blood effects only"
   },
   {
-    "objectID": "decisions/20240330-gitlab-helm.html#alternatives-not-chosen",
-    "href": "decisions/20240330-gitlab-helm.html#alternatives-not-chosen",
-    "title": "Proposed: Integrating Helm for Kubernetes Runner Installation with S3 Cache",
+    "objectID": "decisions/20230522-JOKE-fictional-blood-combat.html#script-workaround",
+    "href": "decisions/20230522-JOKE-fictional-blood-combat.html#script-workaround",
+    "title": "Rejected: Defeating your fictional enemies in their blood",
     "section": "",
-    "text": "Manual Runner Installation: Avoided due to its lack of scalability and increased potential for configuration errors."
+    "text": "No, significant development effort is required."
   },
   {
-    "objectID": "decisions/20240330-gitlab-helm.html#infrequent-use-case",
-    "href": "decisions/20240330-gitlab-helm.html#infrequent-use-case",
-    "title": "Proposed: Integrating Helm for Kubernetes Runner Installation with S3 Cache",
+    "objectID": "decisions/20230522-JOKE-fictional-blood-combat.html#core-implementation-rationale",
+    "href": "decisions/20230522-JOKE-fictional-blood-combat.html#core-implementation-rationale",
+    "title": "Rejected: Defeating your fictional enemies in their blood",
     "section": "",
-    "text": "Temporary or One-off CI/CD Tasks: For tasks that do not justify the overhead of Kubernetes runners, alternative, simpler CI/CD solutions might be temporarily employed."
+    "text": "Easier integration, optimization, control, and refinement as part of the core game engine."
   },
   {
-    "objectID": "decisions/20240330-gitlab-helm.html#in-core-and-done-by-us",
-    "href": "decisions/20240330-gitlab-helm.html#in-core-and-done-by-us",
-    "title": "Proposed: Integrating Helm for Kubernetes Runner Installation with S3 Cache",
+    "objectID": "decisions/20230522-JOKE-fictional-blood-combat.html#references",
+    "href": "decisions/20230522-JOKE-fictional-blood-combat.html#references",
+    "title": "Rejected: Defeating your fictional enemies in their blood",
     "section": "",
-    "text": "This initiative aligns with our core mission of developing social VR capabilities within the Godot Engine. The V-Sekai development team will lead this project, ensuring it meets our technical standards and project goals."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20240330-gitlab-helm.html#status",
-    "href": "decisions/20240330-gitlab-helm.html#status",
-    "title": "Proposed: Integrating Helm for Kubernetes Runner Installation with S3 Cache",
+    "objectID": "decisions/20211031-cicd-export-v-sekai.html",
+    "href": "decisions/20211031-cicd-export-v-sekai.html",
+    "title": "Proposed: CICD Export V-Sekai",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "Proposed: CICD Export V-Sekai\n\nContext and Problem Statement\nCICD Export V-Sekai\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nNeed to ship.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n\nGOCD\nDebug export bugs\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\n\nlots of devops work\n\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\n\nWe know how to do this.\n\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240330-gitlab-helm.html#decision-makers",
-    "href": "decisions/20240330-gitlab-helm.html#decision-makers",
-    "title": "Proposed: Integrating Helm for Kubernetes Runner Installation with S3 Cache",
+    "objectID": "decisions/20211031-stream-shader-motion.html",
+    "href": "decisions/20211031-stream-shader-motion.html",
+    "title": "Proposed: Stream shader motion",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "Proposed: Stream shader motion\n\nContext and Problem Statement\nWant to stream shader motion to multiple people.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nCreate a membrane Pipeline app for ShaderMotion and multiple people\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n\nfor each person send shader motion frames\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot trivial\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nI can move this forward.\n\n\nReferences\n\nMembrane framework\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240330-gitlab-helm.html#tags",
-    "href": "decisions/20240330-gitlab-helm.html#tags",
-    "title": "Proposed: Integrating Helm for Kubernetes Runner Installation with S3 Cache",
+    "objectID": "decisions/20240522-discord-inworld-portal.html",
+    "href": "decisions/20240522-discord-inworld-portal.html",
+    "title": "Draft: View the worlds and interact with people in VR without being in VR via a Discord Inward Portal",
     "section": "",
-    "text": "V-Sekai, CI/CD, Kubernetes, Helm, S3 Cache"
+    "text": "I want to see the worlds and interact with people in VR, without being in VR myself.\n\n\n\nA Discord voice/video call bot would allow players within the virtual world and outside to interact with each other.\n\n\n\nThis would be a bot client that connects to at least one server shard, and joins a Discord voice call, using WebRTC APIs to communicate voice and video data from Godot into discord.\n\n\n\n\nGrowing engagement with Groups\n\n\n\n\n\nRequires Discord\n\n\n\n\nPlayers can stream using OBS or discord screen sharing, but this requires players to do it, and only provides uni-directional communication.\n\n\n\nIt should be a standalone project based on Groups, but not core. The WebRTC dependency, if needed, would make integration difficult.\n\n\n\n\nhttps://discord.com/\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240330-gitlab-helm.html#further-reading",
-    "href": "decisions/20240330-gitlab-helm.html#further-reading",
-    "title": "Proposed: Integrating Helm for Kubernetes Runner Installation with S3 Cache",
+    "objectID": "decisions/20240522-discord-inworld-portal.html#context-and-problem-statement",
+    "href": "decisions/20240522-discord-inworld-portal.html#context-and-problem-statement",
+    "title": "Draft: View the worlds and interact with people in VR without being in VR via a Discord Inward Portal",
     "section": "",
-    "text": "Helm Documentation\nGitLab Runner Helm Chart\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAssisted by Aria, your AI assistant."
+    "text": "I want to see the worlds and interact with people in VR, without being in VR myself."
   },
   {
-    "objectID": "decisions/20231024-finetuning-workflow.html",
-    "href": "decisions/20231024-finetuning-workflow.html",
-    "title": "Proposed: Enhancing Task-Specific Model Performance through Fine-Tuning with Axolotl",
+    "objectID": "decisions/20240522-discord-inworld-portal.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20240522-discord-inworld-portal.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Draft: View the worlds and interact with people in VR without being in VR via a Discord Inward Portal",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai, fire\nTags: V-Sekai, Model Fine-tuning, Axolotl\n\n\n\n\nWe have multiple tasks each with a minimum of 100 samples and we want to fine-tune the latest models with our data. We are considering using the Axolotl library in a mode that batches the inputs.\n\n\n\nThe challenge is to effectively use these samples to fine-tune the model for each task without overfitting, while also ensuring that the model generalizes well to unseen data.\n\n\n\n\nData Preparation: First, we need to prepare our data for each task. This involves cleaning the data and splitting it into training and validation sets.\nModel Selection: Next, we select the latest models that we want to fine-tune. These could be models from Hugging Face’s model hub or any other source.\nFine-tuning with Axolotl: We will use the Axolotl library for fine-tuning. We can batch-mask our inputs to efficiently utilize our computational resources. This process will be repeated for each task.\nEvaluation: After fine-tuning, we evaluate the model on our validation set for each task to see how well it performs.\n\n\n\n\nBy fine-tuning the latest models on our specific tasks, we can potentially achieve better performance than using pre-trained models out-of-the-box. Also, Axolotl provides an easy-to-use interface for fine-tuning models.\n\n\n\nFine-tuning models requires computational resources and time. Also, with only 100 samples per task, there’s a risk of overfitting.\n\n\n\nAn alternative approach could be to use data augmentation techniques to increase the size of our dataset before fine-tuning.\n\n\n\nIf we have tasks that are infrequently performed, it might not be worth the effort to fine-tune a model specifically for these tasks.\n\n\n\nYes, this strategy involves us actively participating in the fine-tuning process.\n\n\n\n\nV-Sekai\nAxolotl\nAI assists this article."
+    "text": "A Discord voice/video call bot would allow players within the virtual world and outside to interact with each other."
   },
   {
-    "objectID": "decisions/20231024-finetuning-workflow.html#metadata",
-    "href": "decisions/20231024-finetuning-workflow.html#metadata",
-    "title": "Proposed: Enhancing Task-Specific Model Performance through Fine-Tuning with Axolotl",
+    "objectID": "decisions/20240522-discord-inworld-portal.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240522-discord-inworld-portal.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Draft: View the worlds and interact with people in VR without being in VR via a Discord Inward Portal",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai, fire\nTags: V-Sekai, Model Fine-tuning, Axolotl"
+    "text": "This would be a bot client that connects to at least one server shard, and joins a Discord voice call, using WebRTC APIs to communicate voice and video data from Godot into discord."
   },
   {
-    "objectID": "decisions/20231024-finetuning-workflow.html#the-backdrop",
-    "href": "decisions/20231024-finetuning-workflow.html#the-backdrop",
-    "title": "Proposed: Enhancing Task-Specific Model Performance through Fine-Tuning with Axolotl",
+    "objectID": "decisions/20240522-discord-inworld-portal.html#positive-consequences",
+    "href": "decisions/20240522-discord-inworld-portal.html#positive-consequences",
+    "title": "Draft: View the worlds and interact with people in VR without being in VR via a Discord Inward Portal",
     "section": "",
-    "text": "We have multiple tasks each with a minimum of 100 samples and we want to fine-tune the latest models with our data. We are considering using the Axolotl library in a mode that batches the inputs."
+    "text": "Growing engagement with Groups"
   },
   {
-    "objectID": "decisions/20231024-finetuning-workflow.html#the-challenge",
-    "href": "decisions/20231024-finetuning-workflow.html#the-challenge",
-    "title": "Proposed: Enhancing Task-Specific Model Performance through Fine-Tuning with Axolotl",
+    "objectID": "decisions/20240522-discord-inworld-portal.html#negative-consequences",
+    "href": "decisions/20240522-discord-inworld-portal.html#negative-consequences",
+    "title": "Draft: View the worlds and interact with people in VR without being in VR via a Discord Inward Portal",
     "section": "",
-    "text": "The challenge is to effectively use these samples to fine-tune the model for each task without overfitting, while also ensuring that the model generalizes well to unseen data."
+    "text": "Requires Discord"
   },
   {
-    "objectID": "decisions/20231024-finetuning-workflow.html#the-strategy",
-    "href": "decisions/20231024-finetuning-workflow.html#the-strategy",
-    "title": "Proposed: Enhancing Task-Specific Model Performance through Fine-Tuning with Axolotl",
+    "objectID": "decisions/20240522-discord-inworld-portal.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20240522-discord-inworld-portal.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Draft: View the worlds and interact with people in VR without being in VR via a Discord Inward Portal",
     "section": "",
-    "text": "Data Preparation: First, we need to prepare our data for each task. This involves cleaning the data and splitting it into training and validation sets.\nModel Selection: Next, we select the latest models that we want to fine-tune. These could be models from Hugging Face’s model hub or any other source.\nFine-tuning with Axolotl: We will use the Axolotl library for fine-tuning. We can batch-mask our inputs to efficiently utilize our computational resources. This process will be repeated for each task.\nEvaluation: After fine-tuning, we evaluate the model on our validation set for each task to see how well it performs."
+    "text": "Players can stream using OBS or discord screen sharing, but this requires players to do it, and only provides uni-directional communication."
   },
   {
-    "objectID": "decisions/20231024-finetuning-workflow.html#the-upside",
-    "href": "decisions/20231024-finetuning-workflow.html#the-upside",
-    "title": "Proposed: Enhancing Task-Specific Model Performance through Fine-Tuning with Axolotl",
+    "objectID": "decisions/20240522-discord-inworld-portal.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20240522-discord-inworld-portal.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Draft: View the worlds and interact with people in VR without being in VR via a Discord Inward Portal",
     "section": "",
-    "text": "By fine-tuning the latest models on our specific tasks, we can potentially achieve better performance than using pre-trained models out-of-the-box. Also, Axolotl provides an easy-to-use interface for fine-tuning models."
+    "text": "It should be a standalone project based on Groups, but not core. The WebRTC dependency, if needed, would make integration difficult."
   },
   {
-    "objectID": "decisions/20231024-finetuning-workflow.html#the-downside",
-    "href": "decisions/20231024-finetuning-workflow.html#the-downside",
-    "title": "Proposed: Enhancing Task-Specific Model Performance through Fine-Tuning with Axolotl",
+    "objectID": "decisions/20240522-discord-inworld-portal.html#references",
+    "href": "decisions/20240522-discord-inworld-portal.html#references",
+    "title": "Draft: View the worlds and interact with people in VR without being in VR via a Discord Inward Portal",
     "section": "",
-    "text": "Fine-tuning models requires computational resources and time. Also, with only 100 samples per task, there’s a risk of overfitting."
+    "text": "https://discord.com/"
   },
   {
-    "objectID": "decisions/20231024-finetuning-workflow.html#the-road-not-taken",
-    "href": "decisions/20231024-finetuning-workflow.html#the-road-not-taken",
-    "title": "Proposed: Enhancing Task-Specific Model Performance through Fine-Tuning with Axolotl",
+    "objectID": "decisions/20240522-discord-inworld-portal.html#derivative-license",
+    "href": "decisions/20240522-discord-inworld-portal.html#derivative-license",
+    "title": "Draft: View the worlds and interact with people in VR without being in VR via a Discord Inward Portal",
     "section": "",
-    "text": "An alternative approach could be to use data augmentation techniques to increase the size of our dataset before fine-tuning."
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20231024-finetuning-workflow.html#the-infrequent-use-case",
-    "href": "decisions/20231024-finetuning-workflow.html#the-infrequent-use-case",
-    "title": "Proposed: Enhancing Task-Specific Model Performance through Fine-Tuning with Axolotl",
+    "objectID": "decisions/20240413-calling-opensource-llm-with-aria.html",
+    "href": "decisions/20240413-calling-opensource-llm-with-aria.html",
+    "title": "Proposed: Calling Open Source LLM with Aria",
     "section": "",
-    "text": "If we have tasks that are infrequently performed, it might not be worth the effort to fine-tune a model specifically for these tasks."
+    "text": "Access to OpenAI’s ChatGPT-4 cannot last forever.\n\n\n\nUsing the assistant name Aria, I want to call an Apache2 licensed large language model (LLM) with open weights in my code editor, Visual Studio Code by Microsoft.\n\n\n\n\nInstall LM Studio: A tool for managing and deploying large language models.\nDownload a quantized version of Hermes-2-Pro-Mistral-7B: This model is available at Hugging Face Model Card.\nInstall Visual Studio Code: The popular code editor by Microsoft.\nInstall the Genie extension: This lets you interact with AI models directly in Visual Studio Code. ai-genie.chatgpt-vscode\nSet Genie to use the assistant name “Aria”: This will give the AI a unique identity within Visual Studio Code.\n{\n  \"genie.assistantName\": \"Aria\",\n  \"genie.apiUrl\": \"http://localhost:1234/v1/chat/completions\",\n  \"genie.model\": {\n    \"id\": \"nousresearch/hermes-2-pro-mistral-7b\",\n    \"tokenLimit\": 8192\n  }\n}\nStart using Aria in Visual Studio Code: With the above settings, you can now access and interact with the open source large language model (LLM) named Hermes-2-Pro-Mistral-7B through the Genie extension.\n\n\n\n\n\nAccess to an AI assistant large language model.\nAbility to develop and fine-tune your data models on open-source datasets.\n\n\n\n\n\nRequires a good understanding of natural language processing (NLP) and machine learning concepts.\nMay require additional hardware resources for running the LLM locally.\n\n\n\n\n\nUsing proprietary AI models that are not open-source or freely available, such as OpenAI’s ChatGPT-4.\nRelying on cloud-based services for AI interactions instead of local deployment.\n\n\n\n\n\nIn cases where real-time performance is critical, using an LLM might not be the optimal solution due to its computational requirements.\n\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\nFire\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20231024-finetuning-workflow.html#in-core-and-done-by-us",
-    "href": "decisions/20231024-finetuning-workflow.html#in-core-and-done-by-us",
-    "title": "Proposed: Enhancing Task-Specific Model Performance through Fine-Tuning with Axolotl",
+    "objectID": "decisions/20240413-calling-opensource-llm-with-aria.html#further-reading",
+    "href": "decisions/20240413-calling-opensource-llm-with-aria.html#further-reading",
+    "title": "Proposed: Calling Open Source LLM with Aria",
     "section": "",
-    "text": "Yes, this strategy involves us actively participating in the fine-tuning process."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20231024-finetuning-workflow.html#further-reading",
-    "href": "decisions/20231024-finetuning-workflow.html#further-reading",
-    "title": "Proposed: Enhancing Task-Specific Model Performance through Fine-Tuning with Axolotl",
+    "objectID": "decisions/20211031-plausable-npc-behaviour.html",
+    "href": "decisions/20211031-plausable-npc-behaviour.html",
+    "title": "Proposed: Plausible npc behavior",
     "section": "",
-    "text": "V-Sekai\nAxolotl\nAI assists this article."
+    "text": "Proposed: Plausible npc behavior\n\nContext and Problem Statement\nCreate plausible npc behavior\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nPlausible npc behavior using a htn planner\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nUpgrade my htn planner to a production state.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot a few lines.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nI have an approach!\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240905-revised-tracker-configuration-and-constraints.html",
-    "href": "decisions/20240905-revised-tracker-configuration-and-constraints.html",
-    "title": "Proposed: Revised Tracker Configuration and Constraints for HTC VIVE XR Elite",
+    "objectID": "decisions/20240502-membrane-framework-identity-post.html",
+    "href": "decisions/20240502-membrane-framework-identity-post.html",
+    "title": "Proposed: Process the glTF2 input file and return it as is",
     "section": "",
-    "text": "In virtual reality (VR), precise motion tracking is import for immersive experiences. Effective tracker configuration is essential to enhance interaction within VR environments, specifically for the HTC VIVE XR Elite.\n\n\n\nTracker configurations distribution across available dongles, affects the setup of motion capture in VR applications, particularly with the HTC VIVE XR Elite.\n\n\n\n\n\n\nHips (1 tracker)\nFoot Right (1 tracker)\nFoot Left (1 tracker)\nElbow Left (1 tracker)\nElbow Right (1 tracker)\n\n\n\n\n\nKnee Right (1 tracker)\nKnee Left (1 tracker)\nChest (1 tracker)\nHips (1 tracker optional)\nChest (1 tracker optional)\n\n\n\n\nEach dongle supports a maximum of 5 trackers. This constraint is critical in determining how trackers are distributed between the two dongles to ensure optimal performance without exceeding the connectivity limit, specifically for the HTC VIVE XR Elite.\n\n\n\n\n\n\nEnhanced Lower Limb Tracking: By connecting both knee trackers to the HMD dongle, we ensure precise tracking of lower limb movements, which is essential for accurate motion capture in activities that involve significant leg movement.\nUpper Extremity Tracking: Including both elbow trackers on this dongle allows for detailed arm movement tracking, enhancing the realism and responsiveness of upper body interactions in VR.\n\n\n\n\n\nComprehensive Upper Body Tracking:\n\nChest and Hips Trackers: These trackers are crucial for capturing the core movements of the body, providing a stable base for upper body motion tracking.\nDual Foot Tracking: Placing the foot trackers on the PC-connected dongle ensures that foot movements are captured accurately, which is vital for walking, running, and other foot-based interactions in VR environments.\n\n\n\n\n\n\n\n\nImproved Accuracy: Optimized tracker placement enhances the precision of motion capture.\nEnhanced User Experience: More accurate tracking translates to a more immersive and responsive VR experience.\nScalability: This setup allows for easy adjustments and scalability as new trackers or technologies become available.\n\n\n\n\n\nComplex Setup: Initial configuration and calibration may be more complex and time-consuming.\nHardware Dependency: Performance is heavily dependent on the quality and capability of the hardware used.\n\n\n\n\nAlternative configurations that involved different distributions of trackers were considered but were not pursued due to potential compromises in tracking accuracy and performance.\n\n\n\nIn cases where extreme precision is not required, such as in less interactive VR applications, a simpler tracker setup might suffice.\n\n\n\nThis proposal aligns with our core mission to push the boundaries of VR technology and will be implemented by our internal development team, focusing on the HTC VIVE XR Elite.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\nHTC VIVE XR Elite\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "We are working on a project that involves the use of the Elixir Membrane Framework. Our goal is to process glTF (GL Transmission Format) files, which are standard file formats for 3D scenes and models.\n\n\n\nWe need to create a job in the Membrane Framework that can take an input glTF file and return it as is. However, we are currently stuck and unable to proceed with this task.\n\n\n\ndefmodule MyPipeline do\n  use Membrane.Pipeline\n\n  @impl true\n  def handle_init(_) do\n    children = %{\n      source: %Membrane.File.Source{location: \"input.gltf\"},\n      sink: Membrane.File.Sink\n    }\n\n    links = [\n      link(:source)\n      |&gt; to(:sink)\n    ]\n\n    {{:ok, %ParentSpec{children: children, links: links}}, %{}}\n  end\nend\nThis is a basic pipeline that reads a file and writes it back out. It’s not doing any processing yet, but it’s a start.\n\n\n\nImplementing this feature will allow us to process glTF files within our application, opening up new possibilities for 3D model manipulation and visualization.\n\n\n\nThe main downside is the complexity involved in understanding and implementing the Membrane Framework. This could potentially slow down development time.\n\n\n\nAn alternative approach would have been to use a different framework or language that might be easier to implement but may not offer the same level of control and flexibility as the Membrane Framework.\n\n\n\nThis feature may not be used frequently if our application does not heavily rely on 3D model manipulation.\n\n\n\nThis feature will be implemented by the V-Sekai development team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240905-revised-tracker-configuration-and-constraints.html#the-context",
-    "href": "decisions/20240905-revised-tracker-configuration-and-constraints.html#the-context",
-    "title": "Proposed: Revised Tracker Configuration and Constraints for HTC VIVE XR Elite",
+    "objectID": "decisions/20240502-membrane-framework-identity-post.html#the-context",
+    "href": "decisions/20240502-membrane-framework-identity-post.html#the-context",
+    "title": "Proposed: Process the glTF2 input file and return it as is",
     "section": "",
-    "text": "In virtual reality (VR), precise motion tracking is import for immersive experiences. Effective tracker configuration is essential to enhance interaction within VR environments, specifically for the HTC VIVE XR Elite."
+    "text": "We are working on a project that involves the use of the Elixir Membrane Framework. Our goal is to process glTF (GL Transmission Format) files, which are standard file formats for 3D scenes and models."
   },
   {
-    "objectID": "decisions/20240905-revised-tracker-configuration-and-constraints.html#the-problem-statement",
-    "href": "decisions/20240905-revised-tracker-configuration-and-constraints.html#the-problem-statement",
-    "title": "Proposed: Revised Tracker Configuration and Constraints for HTC VIVE XR Elite",
+    "objectID": "decisions/20240502-membrane-framework-identity-post.html#the-problem-statement",
+    "href": "decisions/20240502-membrane-framework-identity-post.html#the-problem-statement",
+    "title": "Proposed: Process the glTF2 input file and return it as is",
     "section": "",
-    "text": "Tracker configurations distribution across available dongles, affects the setup of motion capture in VR applications, particularly with the HTC VIVE XR Elite."
+    "text": "We need to create a job in the Membrane Framework that can take an input glTF file and return it as is. However, we are currently stuck and unable to proceed with this task."
   },
   {
-    "objectID": "decisions/20240905-revised-tracker-configuration-and-constraints.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240905-revised-tracker-configuration-and-constraints.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Revised Tracker Configuration and Constraints for HTC VIVE XR Elite",
+    "objectID": "decisions/20240502-membrane-framework-identity-post.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240502-membrane-framework-identity-post.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Process the glTF2 input file and return it as is",
     "section": "",
-    "text": "Hips (1 tracker)\nFoot Right (1 tracker)\nFoot Left (1 tracker)\nElbow Left (1 tracker)\nElbow Right (1 tracker)\n\n\n\n\n\nKnee Right (1 tracker)\nKnee Left (1 tracker)\nChest (1 tracker)\nHips (1 tracker optional)\nChest (1 tracker optional)\n\n\n\n\nEach dongle supports a maximum of 5 trackers. This constraint is critical in determining how trackers are distributed between the two dongles to ensure optimal performance without exceeding the connectivity limit, specifically for the HTC VIVE XR Elite.\n\n\n\n\n\n\nEnhanced Lower Limb Tracking: By connecting both knee trackers to the HMD dongle, we ensure precise tracking of lower limb movements, which is essential for accurate motion capture in activities that involve significant leg movement.\nUpper Extremity Tracking: Including both elbow trackers on this dongle allows for detailed arm movement tracking, enhancing the realism and responsiveness of upper body interactions in VR.\n\n\n\n\n\nComprehensive Upper Body Tracking:\n\nChest and Hips Trackers: These trackers are crucial for capturing the core movements of the body, providing a stable base for upper body motion tracking.\nDual Foot Tracking: Placing the foot trackers on the PC-connected dongle ensures that foot movements are captured accurately, which is vital for walking, running, and other foot-based interactions in VR environments."
+    "text": "defmodule MyPipeline do\n  use Membrane.Pipeline\n\n  @impl true\n  def handle_init(_) do\n    children = %{\n      source: %Membrane.File.Source{location: \"input.gltf\"},\n      sink: Membrane.File.Sink\n    }\n\n    links = [\n      link(:source)\n      |&gt; to(:sink)\n    ]\n\n    {{:ok, %ParentSpec{children: children, links: links}}, %{}}\n  end\nend\nThis is a basic pipeline that reads a file and writes it back out. It’s not doing any processing yet, but it’s a start."
   },
   {
-    "objectID": "decisions/20240905-revised-tracker-configuration-and-constraints.html#the-benefits",
-    "href": "decisions/20240905-revised-tracker-configuration-and-constraints.html#the-benefits",
-    "title": "Proposed: Revised Tracker Configuration and Constraints for HTC VIVE XR Elite",
+    "objectID": "decisions/20240502-membrane-framework-identity-post.html#the-benefits",
+    "href": "decisions/20240502-membrane-framework-identity-post.html#the-benefits",
+    "title": "Proposed: Process the glTF2 input file and return it as is",
     "section": "",
-    "text": "Improved Accuracy: Optimized tracker placement enhances the precision of motion capture.\nEnhanced User Experience: More accurate tracking translates to a more immersive and responsive VR experience.\nScalability: This setup allows for easy adjustments and scalability as new trackers or technologies become available."
+    "text": "Implementing this feature will allow us to process glTF files within our application, opening up new possibilities for 3D model manipulation and visualization."
   },
   {
-    "objectID": "decisions/20240905-revised-tracker-configuration-and-constraints.html#the-downsides",
-    "href": "decisions/20240905-revised-tracker-configuration-and-constraints.html#the-downsides",
-    "title": "Proposed: Revised Tracker Configuration and Constraints for HTC VIVE XR Elite",
+    "objectID": "decisions/20240502-membrane-framework-identity-post.html#the-downsides",
+    "href": "decisions/20240502-membrane-framework-identity-post.html#the-downsides",
+    "title": "Proposed: Process the glTF2 input file and return it as is",
     "section": "",
-    "text": "Complex Setup: Initial configuration and calibration may be more complex and time-consuming.\nHardware Dependency: Performance is heavily dependent on the quality and capability of the hardware used."
+    "text": "The main downside is the complexity involved in understanding and implementing the Membrane Framework. This could potentially slow down development time."
   },
   {
-    "objectID": "decisions/20240905-revised-tracker-configuration-and-constraints.html#the-road-not-taken",
-    "href": "decisions/20240905-revised-tracker-configuration-and-constraints.html#the-road-not-taken",
-    "title": "Proposed: Revised Tracker Configuration and Constraints for HTC VIVE XR Elite",
+    "objectID": "decisions/20240502-membrane-framework-identity-post.html#the-road-not-taken",
+    "href": "decisions/20240502-membrane-framework-identity-post.html#the-road-not-taken",
+    "title": "Proposed: Process the glTF2 input file and return it as is",
     "section": "",
-    "text": "Alternative configurations that involved different distributions of trackers were considered but were not pursued due to potential compromises in tracking accuracy and performance."
+    "text": "An alternative approach would have been to use a different framework or language that might be easier to implement but may not offer the same level of control and flexibility as the Membrane Framework."
   },
   {
-    "objectID": "decisions/20240905-revised-tracker-configuration-and-constraints.html#the-infrequent-use-case",
-    "href": "decisions/20240905-revised-tracker-configuration-and-constraints.html#the-infrequent-use-case",
-    "title": "Proposed: Revised Tracker Configuration and Constraints for HTC VIVE XR Elite",
+    "objectID": "decisions/20240502-membrane-framework-identity-post.html#the-infrequent-use-case",
+    "href": "decisions/20240502-membrane-framework-identity-post.html#the-infrequent-use-case",
+    "title": "Proposed: Process the glTF2 input file and return it as is",
     "section": "",
-    "text": "In cases where extreme precision is not required, such as in less interactive VR applications, a simpler tracker setup might suffice."
+    "text": "This feature may not be used frequently if our application does not heavily rely on 3D model manipulation."
   },
   {
-    "objectID": "decisions/20240905-revised-tracker-configuration-and-constraints.html#in-core-and-done-by-us",
-    "href": "decisions/20240905-revised-tracker-configuration-and-constraints.html#in-core-and-done-by-us",
-    "title": "Proposed: Revised Tracker Configuration and Constraints for HTC VIVE XR Elite",
+    "objectID": "decisions/20240502-membrane-framework-identity-post.html#in-core-and-done-by-us",
+    "href": "decisions/20240502-membrane-framework-identity-post.html#in-core-and-done-by-us",
+    "title": "Proposed: Process the glTF2 input file and return it as is",
     "section": "",
-    "text": "This proposal aligns with our core mission to push the boundaries of VR technology and will be implemented by our internal development team, focusing on the HTC VIVE XR Elite."
+    "text": "This feature will be implemented by the V-Sekai development team."
   },
   {
-    "objectID": "decisions/20240905-revised-tracker-configuration-and-constraints.html#status",
-    "href": "decisions/20240905-revised-tracker-configuration-and-constraints.html#status",
-    "title": "Proposed: Revised Tracker Configuration and Constraints for HTC VIVE XR Elite",
+    "objectID": "decisions/20240502-membrane-framework-identity-post.html#status",
+    "href": "decisions/20240502-membrane-framework-identity-post.html#status",
+    "title": "Proposed: Process the glTF2 input file and return it as is",
     "section": "",
     "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20240905-revised-tracker-configuration-and-constraints.html#decision-makers",
-    "href": "decisions/20240905-revised-tracker-configuration-and-constraints.html#decision-makers",
-    "title": "Proposed: Revised Tracker Configuration and Constraints for HTC VIVE XR Elite",
+    "objectID": "decisions/20240502-membrane-framework-identity-post.html#decision-makers",
+    "href": "decisions/20240502-membrane-framework-identity-post.html#decision-makers",
+    "title": "Proposed: Process the glTF2 input file and return it as is",
     "section": "",
     "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20240905-revised-tracker-configuration-and-constraints.html#tags",
-    "href": "decisions/20240905-revised-tracker-configuration-and-constraints.html#tags",
-    "title": "Proposed: Revised Tracker Configuration and Constraints for HTC VIVE XR Elite",
+    "objectID": "decisions/20240502-membrane-framework-identity-post.html#tags",
+    "href": "decisions/20240502-membrane-framework-identity-post.html#tags",
+    "title": "Proposed: Process the glTF2 input file and return it as is",
     "section": "",
-    "text": "V-Sekai\nHTC VIVE XR Elite"
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20240905-revised-tracker-configuration-and-constraints.html#further-reading",
-    "href": "decisions/20240905-revised-tracker-configuration-and-constraints.html#further-reading",
-    "title": "Proposed: Revised Tracker Configuration and Constraints for HTC VIVE XR Elite",
+    "objectID": "decisions/20240502-membrane-framework-identity-post.html#further-reading",
+    "href": "decisions/20240502-membrane-framework-identity-post.html#further-reading",
+    "title": "Proposed: Process the glTF2 input file and return it as is",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20211031-client-and-mast.html",
-    "href": "decisions/20211031-client-and-mast.html",
-    "title": "Proposed: Client and Mast",
+    "objectID": "decisions/20211031-how-to-make-a-v-sekaigodot-update.html",
+    "href": "decisions/20211031-how-to-make-a-v-sekaigodot-update.html",
+    "title": "Proposed: How to make a V-Sekai/godot update?",
     "section": "",
-    "text": "Proposed: Client and Mast\n\nContext and Problem Statement\nClient and Mast\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nClient and Mast\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nClient and Mast.\nScripting / entity APIs: wasm / barebones messaging protocols + notification / scripted objects? entities?\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot a few lines of script.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nI know how this works.\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Proposed: How to make a V-Sekai/godot update?\n\nContext and Problem Statement\nWrite down how we make branch updates.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nNeed to write down how to do updates.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nOn the Github UI, go to the mater branch and update from Godot Engine master.\ngit clone https://github.com/V-Sekai/groups_merge_script\ncd groups_merge_script\nsh update_repos.sh\ngit clone https://github.com/V-Sekai/groups-workspace-fire -b 4.x --single-branch --recurse-submodules\ncd groups-workspace-fire\n# open folder in visual studio code\n# use update repositories visual studio code command\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot code, but procedure.\n\n\nPositive Consequences\nLower bus factor.\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nThis a V-Sekai organization task.\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240425-proposal-prompt-system.html",
-    "href": "decisions/20240425-proposal-prompt-system.html",
-    "title": "Proposed: ChatGPT-4 Based Proposal Prompt System",
+    "objectID": "decisions/20230125-possible-futures.html",
+    "href": "decisions/20230125-possible-futures.html",
+    "title": "Proposed: Possible futures",
     "section": "",
-    "text": "In the current scenario, creating proposals can be a time-consuming task. It requires a lot of brainstorming and writing which can sometimes lead to inefficiency and delay in work.\n\n\n\nThe problem lies in the manual creation of proposals. The process is slow and often lacks creativity due to human limitations. There is a need for an automated system that can generate proposals efficiently and creatively.\n\n\n\nWe propose a system that uses OpenAI’s ChatGPT-4 to generate proposals. The user will provide a prompt such as Create a proposal. Don't be purple. Be snappy. and the system will use this prompt to generate a proposal.\n\n\n\n\nEfficiency: This system will significantly reduce the time taken to create proposals.\nCreativity: With GPT-4’s advanced language model, the proposals generated will be creative and engaging.\nEase of Use: Users just need to provide a prompt and the system will take care of the rest.\n\n\n\n\nThe system may not always provide the best decision but only the most common wisdom. It might require human intervention to fine-tune the proposals.\n\n\n\nThere could be other AI models or methods to automate the proposal generation process. However, considering the performance and capabilities of GPT-4, it seems to be the most suitable choice.\n\n\n\nThis system might not be very useful for users who rarely need to create proposals.\n\n\n\nThe system will be developed and maintained by the V-Sekai development team.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\nProposal Generation\nGPT-4\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis proposal was assisted by AI assistant Aria."
+    "text": "Proposed: Possible futures\n\nMetadata\n\nStatus: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nContext and Problem Statement\nWe need to choose features to add to V-Sekai.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nTrim the steps needed to create the game.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nMain development:\n\nDevelop prototype of in-game tablet interface (L)\n\nImplement features to place objects (M)\nDebug color picker (S)\n\n\nFuture development:\n\nDebug joining separate worlds with different steps (L)\nRefine UI and user experience (L)\n\nTest and debug prototype (L)\n\nDebug backend upload support (L)\nDebug backend server lobby (L)\nDebug engine multiplayer (L)\nDefine architecture and create design document (S)\nImplement text input (S)\nAdjust objects with PLY (M)\nIntegrate the PLY addon for manifold meshes (L)\nImplement features to lock objects (M)\nDebug VOIP chat (M)\nMerge, subtract and intersect 3D models (XL)\nFocus a group of 3d models M)\nTools with sliders (M)\n\nAdjust constraints of the tool sliders with dag adjustment.\n\n\n\n\nPositive Consequences\nWe are able to use V-Sekai for fun and work.\n\n\nNegative Consequences\nWe cannot get other features in.\n\n\nOption graveyard\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nKnowing what to do is hard.\n\n\nIs there a reason why this should be core and done by us?\nThis is a list of core features.\n\n\nReferences\n\nV-Sekai"
   },
   {
-    "objectID": "decisions/20240425-proposal-prompt-system.html#context",
-    "href": "decisions/20240425-proposal-prompt-system.html#context",
-    "title": "Proposed: ChatGPT-4 Based Proposal Prompt System",
+    "objectID": "decisions/20240622-build-for-many-platforms.html",
+    "href": "decisions/20240622-build-for-many-platforms.html",
+    "title": "Proposed: Build V-Sekai editor for many platforms",
     "section": "",
-    "text": "In the current scenario, creating proposals can be a time-consuming task. It requires a lot of brainstorming and writing which can sometimes lead to inefficiency and delay in work."
+    "text": "V-Sekai is a versatile tool that we utilize across various domains. Its adaptability and functionality make it an integral part of our operations.\n\n\n\nThe challenge at hand is to build the V-Sekai editor for multiple platforms, thereby enhancing its accessibility and usability.\n\n\n\nOur approach to this problem involves leveraging existing resources and tools:\n\nUtilize our existing gocd pipeline.\nEmploy osxcross for Mac builds.\nUse mingw for Windows builds.\nApply clang for Linux builds.\nImplement emscripten for web assembly.\nUtilize the android sdk on linux for Android builds.\n\nIn addition to these steps, we will also implement automated testing to ensure consistency across all systems. This will involve creating test scripts that can run on each platform, checking for any discrepancies or issues.\n\n\n\nOur goal is to showcase V-Sekai in October 2024. To achieve this, we need to prepare for various hardware targets. This multi-platform build will significantly enhance our reach and impact.\n\n\n\nThe primary downside is the potential complexity and challenges associated with managing and testing numerous build targets. Automated testing should help mitigate this issue, but it will still require careful management and oversight.\n\n\n\nWe could have chosen to focus on a single platform, but this would limit the reach and versatility of V-Sekai. By targeting multiple platforms, we can ensure that V-Sekai is accessible to a wider audience.\n\n\n\nWhile the main use case is for regular users, there may be infrequent use cases where developers or other tech-savvy individuals might want to customize or extend the functionality of V-Sekai. Our multi-platform approach caters to these users as well.\n\n\n\nThis project is core to our mission and will be executed by me. We believe that having control over the development process will allow us to maintain the high quality and consistency that we strive for.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\nFire\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - This is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis proposal was assisted by AI assistant Aria."
   },
   {
-    "objectID": "decisions/20240425-proposal-prompt-system.html#problem-statement",
-    "href": "decisions/20240425-proposal-prompt-system.html#problem-statement",
-    "title": "Proposed: ChatGPT-4 Based Proposal Prompt System",
+    "objectID": "decisions/20240622-build-for-many-platforms.html#the-context",
+    "href": "decisions/20240622-build-for-many-platforms.html#the-context",
+    "title": "Proposed: Build V-Sekai editor for many platforms",
     "section": "",
-    "text": "The problem lies in the manual creation of proposals. The process is slow and often lacks creativity due to human limitations. There is a need for an automated system that can generate proposals efficiently and creatively."
+    "text": "V-Sekai is a versatile tool that we utilize across various domains. Its adaptability and functionality make it an integral part of our operations."
   },
   {
-    "objectID": "decisions/20240425-proposal-prompt-system.html#proposed-solution",
-    "href": "decisions/20240425-proposal-prompt-system.html#proposed-solution",
-    "title": "Proposed: ChatGPT-4 Based Proposal Prompt System",
+    "objectID": "decisions/20240622-build-for-many-platforms.html#the-problem-statement",
+    "href": "decisions/20240622-build-for-many-platforms.html#the-problem-statement",
+    "title": "Proposed: Build V-Sekai editor for many platforms",
     "section": "",
-    "text": "We propose a system that uses OpenAI’s ChatGPT-4 to generate proposals. The user will provide a prompt such as Create a proposal. Don't be purple. Be snappy. and the system will use this prompt to generate a proposal."
+    "text": "The challenge at hand is to build the V-Sekai editor for multiple platforms, thereby enhancing its accessibility and usability."
   },
   {
-    "objectID": "decisions/20240425-proposal-prompt-system.html#benefits",
-    "href": "decisions/20240425-proposal-prompt-system.html#benefits",
-    "title": "Proposed: ChatGPT-4 Based Proposal Prompt System",
+    "objectID": "decisions/20240622-build-for-many-platforms.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240622-build-for-many-platforms.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Build V-Sekai editor for many platforms",
     "section": "",
-    "text": "Efficiency: This system will significantly reduce the time taken to create proposals.\nCreativity: With GPT-4’s advanced language model, the proposals generated will be creative and engaging.\nEase of Use: Users just need to provide a prompt and the system will take care of the rest."
+    "text": "Our approach to this problem involves leveraging existing resources and tools:\n\nUtilize our existing gocd pipeline.\nEmploy osxcross for Mac builds.\nUse mingw for Windows builds.\nApply clang for Linux builds.\nImplement emscripten for web assembly.\nUtilize the android sdk on linux for Android builds.\n\nIn addition to these steps, we will also implement automated testing to ensure consistency across all systems. This will involve creating test scripts that can run on each platform, checking for any discrepancies or issues."
   },
   {
-    "objectID": "decisions/20240425-proposal-prompt-system.html#downsides",
-    "href": "decisions/20240425-proposal-prompt-system.html#downsides",
-    "title": "Proposed: ChatGPT-4 Based Proposal Prompt System",
+    "objectID": "decisions/20240622-build-for-many-platforms.html#the-benefits",
+    "href": "decisions/20240622-build-for-many-platforms.html#the-benefits",
+    "title": "Proposed: Build V-Sekai editor for many platforms",
     "section": "",
-    "text": "The system may not always provide the best decision but only the most common wisdom. It might require human intervention to fine-tune the proposals."
+    "text": "Our goal is to showcase V-Sekai in October 2024. To achieve this, we need to prepare for various hardware targets. This multi-platform build will significantly enhance our reach and impact."
   },
   {
-    "objectID": "decisions/20240425-proposal-prompt-system.html#the-road-not-taken",
-    "href": "decisions/20240425-proposal-prompt-system.html#the-road-not-taken",
-    "title": "Proposed: ChatGPT-4 Based Proposal Prompt System",
+    "objectID": "decisions/20240622-build-for-many-platforms.html#the-downsides",
+    "href": "decisions/20240622-build-for-many-platforms.html#the-downsides",
+    "title": "Proposed: Build V-Sekai editor for many platforms",
     "section": "",
-    "text": "There could be other AI models or methods to automate the proposal generation process. However, considering the performance and capabilities of GPT-4, it seems to be the most suitable choice."
+    "text": "The primary downside is the potential complexity and challenges associated with managing and testing numerous build targets. Automated testing should help mitigate this issue, but it will still require careful management and oversight."
   },
   {
-    "objectID": "decisions/20240425-proposal-prompt-system.html#the-infrequent-use-case",
-    "href": "decisions/20240425-proposal-prompt-system.html#the-infrequent-use-case",
-    "title": "Proposed: ChatGPT-4 Based Proposal Prompt System",
+    "objectID": "decisions/20240622-build-for-many-platforms.html#the-road-not-taken",
+    "href": "decisions/20240622-build-for-many-platforms.html#the-road-not-taken",
+    "title": "Proposed: Build V-Sekai editor for many platforms",
     "section": "",
-    "text": "This system might not be very useful for users who rarely need to create proposals."
+    "text": "We could have chosen to focus on a single platform, but this would limit the reach and versatility of V-Sekai. By targeting multiple platforms, we can ensure that V-Sekai is accessible to a wider audience."
   },
   {
-    "objectID": "decisions/20240425-proposal-prompt-system.html#in-core-and-done-by-us",
-    "href": "decisions/20240425-proposal-prompt-system.html#in-core-and-done-by-us",
-    "title": "Proposed: ChatGPT-4 Based Proposal Prompt System",
+    "objectID": "decisions/20240622-build-for-many-platforms.html#the-infrequent-use-case",
+    "href": "decisions/20240622-build-for-many-platforms.html#the-infrequent-use-case",
+    "title": "Proposed: Build V-Sekai editor for many platforms",
     "section": "",
-    "text": "The system will be developed and maintained by the V-Sekai development team."
+    "text": "While the main use case is for regular users, there may be infrequent use cases where developers or other tech-savvy individuals might want to customize or extend the functionality of V-Sekai. Our multi-platform approach caters to these users as well."
   },
   {
-    "objectID": "decisions/20240425-proposal-prompt-system.html#status",
-    "href": "decisions/20240425-proposal-prompt-system.html#status",
-    "title": "Proposed: ChatGPT-4 Based Proposal Prompt System",
+    "objectID": "decisions/20240622-build-for-many-platforms.html#in-core-and-done-by-us",
+    "href": "decisions/20240622-build-for-many-platforms.html#in-core-and-done-by-us",
+    "title": "Proposed: Build V-Sekai editor for many platforms",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "This project is core to our mission and will be executed by me. We believe that having control over the development process will allow us to maintain the high quality and consistency that we strive for."
   },
   {
-    "objectID": "decisions/20240425-proposal-prompt-system.html#decision-makers",
-    "href": "decisions/20240425-proposal-prompt-system.html#decision-makers",
-    "title": "Proposed: ChatGPT-4 Based Proposal Prompt System",
+    "objectID": "decisions/20240622-build-for-many-platforms.html#status",
+    "href": "decisions/20240622-build-for-many-platforms.html#status",
+    "title": "Proposed: Build V-Sekai editor for many platforms",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20240425-proposal-prompt-system.html#tags",
-    "href": "decisions/20240425-proposal-prompt-system.html#tags",
-    "title": "Proposed: ChatGPT-4 Based Proposal Prompt System",
+    "objectID": "decisions/20240622-build-for-many-platforms.html#decision-makers",
+    "href": "decisions/20240622-build-for-many-platforms.html#decision-makers",
+    "title": "Proposed: Build V-Sekai editor for many platforms",
     "section": "",
-    "text": "V-Sekai\nProposal Generation\nGPT-4"
+    "text": "V-Sekai development team\nFire"
   },
   {
-    "objectID": "decisions/20240425-proposal-prompt-system.html#further-reading",
-    "href": "decisions/20240425-proposal-prompt-system.html#further-reading",
-    "title": "Proposed: ChatGPT-4 Based Proposal Prompt System",
+    "objectID": "decisions/20240622-build-for-many-platforms.html#tags",
+    "href": "decisions/20240622-build-for-many-platforms.html#tags",
+    "title": "Proposed: Build V-Sekai editor for many platforms",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis proposal was assisted by AI assistant Aria."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20241006-restore-onedrive-shortcut-overrides.html",
-    "href": "decisions/20241006-restore-onedrive-shortcut-overrides.html",
-    "title": "Accepted: Restoring Default User Directory Structure in Windows 11",
+    "objectID": "decisions/20240622-build-for-many-platforms.html#further-reading",
+    "href": "decisions/20240622-build-for-many-platforms.html#further-reading",
+    "title": "Proposed: Build V-Sekai editor for many platforms",
     "section": "",
-    "text": "Using Windows 11.\n\n\n\nMicrosoft has configured OneDrive to automatically move key user folders such as Documents, Desktop, and others from the user directory into the OneDrive folder. This change can disrupt users’ familiar file organization and system workflows.\n\n\n\nThe solution involves two main steps:\n\nDisabling OneDrive Sync: Users need to pause or stop OneDrive from syncing these folders.\nRunning a Restore Default Paths Script: Execute a script that resets the default paths of user directories back to their original locations on the local drive.\n\n\n\n\n\nRestores traditional file paths for ease of access and familiarity.\nReduces dependency on cloud synchronization for essential folders.\nImproves system performance by reducing unnecessary sync operations.\n\n\n\n\n\nManual intervention required by users not comfortable with script execution.\nPotential data discrepancies if files are not fully synchronized before the change.\n\n\n\n\nAlternative solutions like using third-party tools or different cloud services were considered but dismissed due to increased complexity and potential security concerns.\n\n\n\nUsers who operate primarily offline or have strict data handling policies may find this change particularly beneficial.\n\n\n\nThis proposal is to be implemented internally within the V-Sekai development team’s systems before considering broader deployment.\n\n\n\nStatus: Accepted \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nWindows 10/11 User Shell Folders Restore Default Paths\n\nAI assistant Aria assisted with this article."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - This is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis proposal was assisted by AI assistant Aria."
   },
   {
-    "objectID": "decisions/20241006-restore-onedrive-shortcut-overrides.html#the-context",
-    "href": "decisions/20241006-restore-onedrive-shortcut-overrides.html#the-context",
-    "title": "Accepted: Restoring Default User Directory Structure in Windows 11",
+    "objectID": "decisions/20240406-itch-github-actions.html",
+    "href": "decisions/20240406-itch-github-actions.html",
+    "title": "Proposed: Provide a V-Sekai Starter Kit",
     "section": "",
-    "text": "Using Windows 11."
+    "text": "Provide a V-Sekai starter kit that is complete and usable.\n\n\n\nUse desync (casync) to generate catars. Then upload this to itchio.\n\n\n\nWe will use the casync tool to create .catar files from our project directory. This will be followed by uploading these files to Itch.io using their Butler CLI tool.\n# Generate .catar file\ncasync make myproject.catar myproject/\n\n# Upload to Itch.io\nbutler push myproject.catar user/game:channel\n\n\n\nSeed a cdn. This will allow us to distribute our SDK more efficiently and reliably.\n\n\n\nThe main downside is the additional complexity introduced by the use of casync and Butler. There may also be potential issues with compatibility or performance.\n\n\n\nAn alternative approach could have been to directly upload the SDK files to Itch.io without using casync. However, this would not provide the benefits of seeding a CDN.\n\n\n\nThis process might be less efficient for small updates, as it involves creating a new .catar file and uploading it each time.\n\n\n\nThis proposal is core to our project and will be implemented by the V-Sekai development team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20241006-restore-onedrive-shortcut-overrides.html#the-problem-statement",
-    "href": "decisions/20241006-restore-onedrive-shortcut-overrides.html#the-problem-statement",
-    "title": "Accepted: Restoring Default User Directory Structure in Windows 11",
+    "objectID": "decisions/20240406-itch-github-actions.html#the-context",
+    "href": "decisions/20240406-itch-github-actions.html#the-context",
+    "title": "Proposed: Provide a V-Sekai Starter Kit",
     "section": "",
-    "text": "Microsoft has configured OneDrive to automatically move key user folders such as Documents, Desktop, and others from the user directory into the OneDrive folder. This change can disrupt users’ familiar file organization and system workflows."
+    "text": "Provide a V-Sekai starter kit that is complete and usable."
   },
   {
-    "objectID": "decisions/20241006-restore-onedrive-shortcut-overrides.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20241006-restore-onedrive-shortcut-overrides.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Accepted: Restoring Default User Directory Structure in Windows 11",
+    "objectID": "decisions/20240406-itch-github-actions.html#the-problem-statement",
+    "href": "decisions/20240406-itch-github-actions.html#the-problem-statement",
+    "title": "Proposed: Provide a V-Sekai Starter Kit",
     "section": "",
-    "text": "The solution involves two main steps:\n\nDisabling OneDrive Sync: Users need to pause or stop OneDrive from syncing these folders.\nRunning a Restore Default Paths Script: Execute a script that resets the default paths of user directories back to their original locations on the local drive."
+    "text": "Use desync (casync) to generate catars. Then upload this to itchio."
   },
   {
-    "objectID": "decisions/20241006-restore-onedrive-shortcut-overrides.html#the-benefits",
-    "href": "decisions/20241006-restore-onedrive-shortcut-overrides.html#the-benefits",
-    "title": "Accepted: Restoring Default User Directory Structure in Windows 11",
+    "objectID": "decisions/20240406-itch-github-actions.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240406-itch-github-actions.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Provide a V-Sekai Starter Kit",
     "section": "",
-    "text": "Restores traditional file paths for ease of access and familiarity.\nReduces dependency on cloud synchronization for essential folders.\nImproves system performance by reducing unnecessary sync operations."
+    "text": "We will use the casync tool to create .catar files from our project directory. This will be followed by uploading these files to Itch.io using their Butler CLI tool.\n# Generate .catar file\ncasync make myproject.catar myproject/\n\n# Upload to Itch.io\nbutler push myproject.catar user/game:channel"
   },
   {
-    "objectID": "decisions/20241006-restore-onedrive-shortcut-overrides.html#the-downsides",
-    "href": "decisions/20241006-restore-onedrive-shortcut-overrides.html#the-downsides",
-    "title": "Accepted: Restoring Default User Directory Structure in Windows 11",
+    "objectID": "decisions/20240406-itch-github-actions.html#the-benefits",
+    "href": "decisions/20240406-itch-github-actions.html#the-benefits",
+    "title": "Proposed: Provide a V-Sekai Starter Kit",
     "section": "",
-    "text": "Manual intervention required by users not comfortable with script execution.\nPotential data discrepancies if files are not fully synchronized before the change."
+    "text": "Seed a cdn. This will allow us to distribute our SDK more efficiently and reliably."
   },
   {
-    "objectID": "decisions/20241006-restore-onedrive-shortcut-overrides.html#the-road-not-taken",
-    "href": "decisions/20241006-restore-onedrive-shortcut-overrides.html#the-road-not-taken",
-    "title": "Accepted: Restoring Default User Directory Structure in Windows 11",
+    "objectID": "decisions/20240406-itch-github-actions.html#the-downsides",
+    "href": "decisions/20240406-itch-github-actions.html#the-downsides",
+    "title": "Proposed: Provide a V-Sekai Starter Kit",
     "section": "",
-    "text": "Alternative solutions like using third-party tools or different cloud services were considered but dismissed due to increased complexity and potential security concerns."
+    "text": "The main downside is the additional complexity introduced by the use of casync and Butler. There may also be potential issues with compatibility or performance."
   },
   {
-    "objectID": "decisions/20241006-restore-onedrive-shortcut-overrides.html#the-infrequent-use-case",
-    "href": "decisions/20241006-restore-onedrive-shortcut-overrides.html#the-infrequent-use-case",
-    "title": "Accepted: Restoring Default User Directory Structure in Windows 11",
+    "objectID": "decisions/20240406-itch-github-actions.html#the-road-not-taken",
+    "href": "decisions/20240406-itch-github-actions.html#the-road-not-taken",
+    "title": "Proposed: Provide a V-Sekai Starter Kit",
     "section": "",
-    "text": "Users who operate primarily offline or have strict data handling policies may find this change particularly beneficial."
+    "text": "An alternative approach could have been to directly upload the SDK files to Itch.io without using casync. However, this would not provide the benefits of seeding a CDN."
   },
   {
-    "objectID": "decisions/20241006-restore-onedrive-shortcut-overrides.html#in-core-and-done-by-us",
-    "href": "decisions/20241006-restore-onedrive-shortcut-overrides.html#in-core-and-done-by-us",
-    "title": "Accepted: Restoring Default User Directory Structure in Windows 11",
+    "objectID": "decisions/20240406-itch-github-actions.html#the-infrequent-use-case",
+    "href": "decisions/20240406-itch-github-actions.html#the-infrequent-use-case",
+    "title": "Proposed: Provide a V-Sekai Starter Kit",
     "section": "",
-    "text": "This proposal is to be implemented internally within the V-Sekai development team’s systems before considering broader deployment."
+    "text": "This process might be less efficient for small updates, as it involves creating a new .catar file and uploading it each time."
   },
   {
-    "objectID": "decisions/20241006-restore-onedrive-shortcut-overrides.html#status",
-    "href": "decisions/20241006-restore-onedrive-shortcut-overrides.html#status",
-    "title": "Accepted: Restoring Default User Directory Structure in Windows 11",
+    "objectID": "decisions/20240406-itch-github-actions.html#in-core-and-done-by-us",
+    "href": "decisions/20240406-itch-github-actions.html#in-core-and-done-by-us",
+    "title": "Proposed: Provide a V-Sekai Starter Kit",
+    "section": "",
+    "text": "This proposal is core to our project and will be implemented by the V-Sekai development team."
+  },
+  {
+    "objectID": "decisions/20240406-itch-github-actions.html#status",
+    "href": "decisions/20240406-itch-github-actions.html#status",
+    "title": "Proposed: Provide a V-Sekai Starter Kit",
     "section": "",
-    "text": "Status: Accepted"
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20241006-restore-onedrive-shortcut-overrides.html#decision-makers",
-    "href": "decisions/20241006-restore-onedrive-shortcut-overrides.html#decision-makers",
-    "title": "Accepted: Restoring Default User Directory Structure in Windows 11",
+    "objectID": "decisions/20240406-itch-github-actions.html#decision-makers",
+    "href": "decisions/20240406-itch-github-actions.html#decision-makers",
+    "title": "Proposed: Provide a V-Sekai Starter Kit",
     "section": "",
     "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20241006-restore-onedrive-shortcut-overrides.html#tags",
-    "href": "decisions/20241006-restore-onedrive-shortcut-overrides.html#tags",
-    "title": "Accepted: Restoring Default User Directory Structure in Windows 11",
+    "objectID": "decisions/20240406-itch-github-actions.html#tags",
+    "href": "decisions/20240406-itch-github-actions.html#tags",
+    "title": "Proposed: Provide a V-Sekai Starter Kit",
     "section": "",
     "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20241006-restore-onedrive-shortcut-overrides.html#further-reading",
-    "href": "decisions/20241006-restore-onedrive-shortcut-overrides.html#further-reading",
-    "title": "Accepted: Restoring Default User Directory Structure in Windows 11",
+    "objectID": "decisions/20240406-itch-github-actions.html#further-reading",
+    "href": "decisions/20240406-itch-github-actions.html#further-reading",
+    "title": "Proposed: Provide a V-Sekai Starter Kit",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nWindows 10/11 User Shell Folders Restore Default Paths\n\nAI assistant Aria assisted with this article."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20231125-v-sekai-report.html",
-    "href": "decisions/20231125-v-sekai-report.html",
-    "title": "Superseded: V-Sekai 2023-11-25 Report",
+    "objectID": "decisions/20231209-appium-testing-win11.html",
+    "href": "decisions/20231209-appium-testing-win11.html",
+    "title": "Proposed: Automating Game Testing Process Using Appium 2",
     "section": "",
-    "text": "Status: Superseded by 20231126-v-sekai-report.md\nDeciders: V-Sekai, fire, PLYSHKA🐧, SaracenOne\nTags: V-Sekai, Linux, Bug Fix, Godot Engine, User Support\n\n\n\n\nV-Sekai, pronounced vee-say-kai, is a collective of developers passionate about creating open-source VR technology. We aim to contribute to social VR and provide alternatives to proprietary engines like Unity and Unreal.\nDespite challenges, we’ve grown into a global community committed to advancing open standards and open-source software for virtual worlds.\nOur strategy focuses on providing comprehensive documentation and support to help users understand the platform better. We’re also committed to investigating and resolving issues like the reported Linux build problem.\n\n\n\nOver the past month, our team has been deeply involved in the Godot Engine conference in Munich, Germany. Our primary responsibility during this period has been to prepare for the upcoming launch of Godot Engine 4.2, to which we are contributing as part of the animation and 3D pipeline teams.\nPLYSHKA🐧 asked on our Discord about the current state of V-Sekai:\n\nPLYSHKA🐧&gt; I’m fairly new to this platform overall, can someone explain in what state its currently in? What can it do and what can’t? I couldn’t launch Linux build properly (black screen), and when started from terminal it just opened Godot editor (it was game binary), so not sure what’s happening there, maybe I don’t understand something\n\n\n\n\nWhat state is V-Sekai in, and what can it do?\n\n\n\n\n\n\nDesktop Mode Loading: V-Sekai is currently unable to load in desktop mode.\nThe purple screen on the desktop: The black screen issue seems related to our current problem of Issue #341\nMultiplayer Voice Chat: The multiplayer voice chat feature in V-Sekai is broken.\n\n\n\n\n\nMenu Editing: In V-Sekai, menus can’t be edited in VR. They can only be edited on the desktop before entering a game.\nDefault Avatar: V-Sekai does not have a default avatar. This causes confusion as players load in with an error avatar.\nDefault Avatar IK: V-Sekai’s default ik is currently twisted incorrectly.\n\n\n\n\n\nAvatar Uploading and Downloading:** V-Sekai can upload from the editor and, download avatars, and load them into the game at runtime.\nWorld Uploading and Downloading:** V-Sekai can upload from the editor and, download worlds, and load them into the game at runtime.\nVR Mode Loading: V-Sekai can successfully load in VR mode.\n\n\n\n\n\nContributions: V-Sekai is actively looking for more contributions.\n\n\n\n\n\nFire is set to merge ufbx, freeing the industry-standard FBX file format from the Autodesk ecosystem for V-Sekai. However, due to limited funding, we won’t be able to implement the upcoming 3D format standard USDZ in next months.\n\n\n\n\n\n\n\nWeek Starting\nTask\n\n\n\n\nNovember 26th, 2023\nInvestigate and resolve “purple screen” bug in V-Sekai.\n\n\nDecember 3rd, 2023\nInitiate the merging of godot-ufbx in Godot Engine 4.3.\n\n\n\n\n\n\nPros:\nAddressing these challenges can enhance the user experience, boost platform adoption, and collect crucial feedback for subsequent development.\nCons:\nThere may be underlying issues causing the Linux build problem that could take significant time and resources to resolve.\n\n\n\nAn alternative approach could have been to ignore the user’s query and continue with the current development roadmap. However, this would not foster a supportive community or encourage user engagement.\n\n\n\nWhile most users may not encounter the same issue as PLYSHKA🐧, addressing even infrequent use cases is essential to ensure a robust and user-friendly platform.\n\n\n\nAddressing this issue falls within our core responsibilities as the V-Sekai development team.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI Aria assisted with this article."
+    "text": "Status: Draft\nDeciders: V-Sekai, fire\nTags: V-Sekai\n\n\n\n\nIn the field of game development, it’s crucial to provide a seamless user experience across various platforms. This requires the implementation of effective testing methodologies.\n\n\n\nOur primary challenge is automating the testing process using Appium. A significant part of this strategy involves converting FBX files, which are commonly used formats for 3D models and animations, into GLB format.\n\n\n\n\n\n\nInstall the Appium server on the Mac using sudo npm install -g appium. Make sure Node.js version 12 or higher is installed.\nLaunch the server using the appium command.\nUse appium driver list and appium driver update [driverName]. For iOS, install drivers with appium driver install xcuitest and install appium driver install xcuitest\nInstall plugins with appium plugin install [pluginName] and integrate them using appium --use-plugins=[appiumPlugin].\nInstall all the plugins\n\nappium plugin install execute-driver\nappium plugin install images\nappium plugin install universal-xml\nappium plugin install relaxed-caps\n\n\n\n\nInstall scoop npm.\n\nscoop install sudo\n# sudo scoop install tailscale # optional\nscoop install nodejs\n\nOn Windows, install the Appium client using Node Package Manager (NPM) with the command npm install -g appium.\nForce Install https://github.com/microsoft/WinAppDriver/releases/download/v1.2.1/WindowsApplicationDriver_1.2.1.msi\nUse appium driver list and appium driver update [driverName]. For Windows, install drivers with appium driver install --source=npm appium-windows-driver\nInstall all the plugins\n\nappium plugin install execute-driver\nappium plugin install images\nappium plugin install universal-xml\nappium plugin install relaxed-caps\n\nRun appium --use-plugins \"execute-driver,images,universal-xml,relaxed-caps\"\n\nEnsure that the network settings and firewall configurations on both the Windows client and the Mac server are compatible for seamless communication.\n\n\n\n\nThe proposed strategy will ensure a high-quality gaming experience by automating the testing process. It will also save time and resources by reducing manual testing efforts.\n\n\n\nThe implementation of this strategy may require substantial resources and could potentially present unforeseen challenges. Additionally, there might be compatibility issues between different versions of Appium and the operating systems.\n\n\n\nWe have considered other testing frameworks, but our proposed strategy with Appium offers the best balance between effectiveness and efficiency.\n\n\n\nOur strategy might not cover infrequent or edge cases in game development. However, these will be identified and addressed as they arise.\n\n\n\nYes, this strategy is core to our project and will be implemented by our team.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAssisted by Aria, an AI assistant."
   },
   {
-    "objectID": "decisions/20231125-v-sekai-report.html#metadata",
-    "href": "decisions/20231125-v-sekai-report.html#metadata",
-    "title": "Superseded: V-Sekai 2023-11-25 Report",
+    "objectID": "decisions/20231209-appium-testing-win11.html#metadata",
+    "href": "decisions/20231209-appium-testing-win11.html#metadata",
+    "title": "Proposed: Automating Game Testing Process Using Appium 2",
     "section": "",
-    "text": "Status: Superseded by 20231126-v-sekai-report.md\nDeciders: V-Sekai, fire, PLYSHKA🐧, SaracenOne\nTags: V-Sekai, Linux, Bug Fix, Godot Engine, User Support"
+    "text": "Status: Draft\nDeciders: V-Sekai, fire\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20231125-v-sekai-report.html#what-is-v-sekai",
-    "href": "decisions/20231125-v-sekai-report.html#what-is-v-sekai",
-    "title": "Superseded: V-Sekai 2023-11-25 Report",
+    "objectID": "decisions/20231209-appium-testing-win11.html#context",
+    "href": "decisions/20231209-appium-testing-win11.html#context",
+    "title": "Proposed: Automating Game Testing Process Using Appium 2",
     "section": "",
-    "text": "V-Sekai, pronounced vee-say-kai, is a collective of developers passionate about creating open-source VR technology. We aim to contribute to social VR and provide alternatives to proprietary engines like Unity and Unreal.\nDespite challenges, we’ve grown into a global community committed to advancing open standards and open-source software for virtual worlds.\nOur strategy focuses on providing comprehensive documentation and support to help users understand the platform better. We’re also committed to investigating and resolving issues like the reported Linux build problem."
+    "text": "In the field of game development, it’s crucial to provide a seamless user experience across various platforms. This requires the implementation of effective testing methodologies."
   },
   {
-    "objectID": "decisions/20231125-v-sekai-report.html#background",
-    "href": "decisions/20231125-v-sekai-report.html#background",
-    "title": "Superseded: V-Sekai 2023-11-25 Report",
+    "objectID": "decisions/20231209-appium-testing-win11.html#problem",
+    "href": "decisions/20231209-appium-testing-win11.html#problem",
+    "title": "Proposed: Automating Game Testing Process Using Appium 2",
     "section": "",
-    "text": "Over the past month, our team has been deeply involved in the Godot Engine conference in Munich, Germany. Our primary responsibility during this period has been to prepare for the upcoming launch of Godot Engine 4.2, to which we are contributing as part of the animation and 3D pipeline teams.\nPLYSHKA🐧 asked on our Discord about the current state of V-Sekai:\n\nPLYSHKA🐧&gt; I’m fairly new to this platform overall, can someone explain in what state its currently in? What can it do and what can’t? I couldn’t launch Linux build properly (black screen), and when started from terminal it just opened Godot editor (it was game binary), so not sure what’s happening there, maybe I don’t understand something"
+    "text": "Our primary challenge is automating the testing process using Appium. A significant part of this strategy involves converting FBX files, which are commonly used formats for 3D models and animations, into GLB format."
   },
   {
-    "objectID": "decisions/20231125-v-sekai-report.html#problem-statement",
-    "href": "decisions/20231125-v-sekai-report.html#problem-statement",
-    "title": "Superseded: V-Sekai 2023-11-25 Report",
+    "objectID": "decisions/20231209-appium-testing-win11.html#solution",
+    "href": "decisions/20231209-appium-testing-win11.html#solution",
+    "title": "Proposed: Automating Game Testing Process Using Appium 2",
     "section": "",
-    "text": "What state is V-Sekai in, and what can it do?"
+    "text": "Install the Appium server on the Mac using sudo npm install -g appium. Make sure Node.js version 12 or higher is installed.\nLaunch the server using the appium command.\nUse appium driver list and appium driver update [driverName]. For iOS, install drivers with appium driver install xcuitest and install appium driver install xcuitest\nInstall plugins with appium plugin install [pluginName] and integrate them using appium --use-plugins=[appiumPlugin].\nInstall all the plugins\n\nappium plugin install execute-driver\nappium plugin install images\nappium plugin install universal-xml\nappium plugin install relaxed-caps\n\n\n\n\nInstall scoop npm.\n\nscoop install sudo\n# sudo scoop install tailscale # optional\nscoop install nodejs\n\nOn Windows, install the Appium client using Node Package Manager (NPM) with the command npm install -g appium.\nForce Install https://github.com/microsoft/WinAppDriver/releases/download/v1.2.1/WindowsApplicationDriver_1.2.1.msi\nUse appium driver list and appium driver update [driverName]. For Windows, install drivers with appium driver install --source=npm appium-windows-driver\nInstall all the plugins\n\nappium plugin install execute-driver\nappium plugin install images\nappium plugin install universal-xml\nappium plugin install relaxed-caps\n\nRun appium --use-plugins \"execute-driver,images,universal-xml,relaxed-caps\"\n\nEnsure that the network settings and firewall configurations on both the Windows client and the Mac server are compatible for seamless communication."
   },
   {
-    "objectID": "decisions/20231125-v-sekai-report.html#strategy",
-    "href": "decisions/20231125-v-sekai-report.html#strategy",
-    "title": "Superseded: V-Sekai 2023-11-25 Report",
+    "objectID": "decisions/20231209-appium-testing-win11.html#benefits",
+    "href": "decisions/20231209-appium-testing-win11.html#benefits",
+    "title": "Proposed: Automating Game Testing Process Using Appium 2",
     "section": "",
-    "text": "Desktop Mode Loading: V-Sekai is currently unable to load in desktop mode.\nThe purple screen on the desktop: The black screen issue seems related to our current problem of Issue #341\nMultiplayer Voice Chat: The multiplayer voice chat feature in V-Sekai is broken.\n\n\n\n\n\nMenu Editing: In V-Sekai, menus can’t be edited in VR. They can only be edited on the desktop before entering a game.\nDefault Avatar: V-Sekai does not have a default avatar. This causes confusion as players load in with an error avatar.\nDefault Avatar IK: V-Sekai’s default ik is currently twisted incorrectly.\n\n\n\n\n\nAvatar Uploading and Downloading:** V-Sekai can upload from the editor and, download avatars, and load them into the game at runtime.\nWorld Uploading and Downloading:** V-Sekai can upload from the editor and, download worlds, and load them into the game at runtime.\nVR Mode Loading: V-Sekai can successfully load in VR mode.\n\n\n\n\n\nContributions: V-Sekai is actively looking for more contributions."
+    "text": "The proposed strategy will ensure a high-quality gaming experience by automating the testing process. It will also save time and resources by reducing manual testing efforts."
   },
   {
-    "objectID": "decisions/20231125-v-sekai-report.html#timeline-for-the-next-weeks",
-    "href": "decisions/20231125-v-sekai-report.html#timeline-for-the-next-weeks",
-    "title": "Superseded: V-Sekai 2023-11-25 Report",
+    "objectID": "decisions/20231209-appium-testing-win11.html#risks",
+    "href": "decisions/20231209-appium-testing-win11.html#risks",
+    "title": "Proposed: Automating Game Testing Process Using Appium 2",
     "section": "",
-    "text": "Fire is set to merge ufbx, freeing the industry-standard FBX file format from the Autodesk ecosystem for V-Sekai. However, due to limited funding, we won’t be able to implement the upcoming 3D format standard USDZ in next months.\n\n\n\n\n\n\n\nWeek Starting\nTask\n\n\n\n\nNovember 26th, 2023\nInvestigate and resolve “purple screen” bug in V-Sekai.\n\n\nDecember 3rd, 2023\nInitiate the merging of godot-ufbx in Godot Engine 4.3."
+    "text": "The implementation of this strategy may require substantial resources and could potentially present unforeseen challenges. Additionally, there might be compatibility issues between different versions of Appium and the operating systems."
   },
   {
-    "objectID": "decisions/20231125-v-sekai-report.html#pros-and-cons",
-    "href": "decisions/20231125-v-sekai-report.html#pros-and-cons",
-    "title": "Superseded: V-Sekai 2023-11-25 Report",
+    "objectID": "decisions/20231209-appium-testing-win11.html#alternatives",
+    "href": "decisions/20231209-appium-testing-win11.html#alternatives",
+    "title": "Proposed: Automating Game Testing Process Using Appium 2",
     "section": "",
-    "text": "Pros:\nAddressing these challenges can enhance the user experience, boost platform adoption, and collect crucial feedback for subsequent development.\nCons:\nThere may be underlying issues causing the Linux build problem that could take significant time and resources to resolve."
+    "text": "We have considered other testing frameworks, but our proposed strategy with Appium offers the best balance between effectiveness and efficiency."
   },
   {
-    "objectID": "decisions/20231125-v-sekai-report.html#alternative-approach",
-    "href": "decisions/20231125-v-sekai-report.html#alternative-approach",
-    "title": "Superseded: V-Sekai 2023-11-25 Report",
+    "objectID": "decisions/20231209-appium-testing-win11.html#limitations",
+    "href": "decisions/20231209-appium-testing-win11.html#limitations",
+    "title": "Proposed: Automating Game Testing Process Using Appium 2",
     "section": "",
-    "text": "An alternative approach could have been to ignore the user’s query and continue with the current development roadmap. However, this would not foster a supportive community or encourage user engagement."
+    "text": "Our strategy might not cover infrequent or edge cases in game development. However, these will be identified and addressed as they arise."
   },
   {
-    "objectID": "decisions/20231125-v-sekai-report.html#infrequent-use-case",
-    "href": "decisions/20231125-v-sekai-report.html#infrequent-use-case",
-    "title": "Superseded: V-Sekai 2023-11-25 Report",
+    "objectID": "decisions/20231209-appium-testing-win11.html#ownership",
+    "href": "decisions/20231209-appium-testing-win11.html#ownership",
+    "title": "Proposed: Automating Game Testing Process Using Appium 2",
     "section": "",
-    "text": "While most users may not encounter the same issue as PLYSHKA🐧, addressing even infrequent use cases is essential to ensure a robust and user-friendly platform."
+    "text": "Yes, this strategy is core to our project and will be implemented by our team."
   },
   {
-    "objectID": "decisions/20231125-v-sekai-report.html#responsibility",
-    "href": "decisions/20231125-v-sekai-report.html#responsibility",
-    "title": "Superseded: V-Sekai 2023-11-25 Report",
+    "objectID": "decisions/20231209-appium-testing-win11.html#references",
+    "href": "decisions/20231209-appium-testing-win11.html#references",
+    "title": "Proposed: Automating Game Testing Process Using Appium 2",
     "section": "",
-    "text": "Addressing this issue falls within our core responsibilities as the V-Sekai development team."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAssisted by Aria, an AI assistant."
   },
   {
-    "objectID": "decisions/20231125-v-sekai-report.html#further-reading",
-    "href": "decisions/20231125-v-sekai-report.html#further-reading",
-    "title": "Superseded: V-Sekai 2023-11-25 Report",
+    "objectID": "decisions/20220830-godot-pdf-workflow.html",
+    "href": "decisions/20220830-godot-pdf-workflow.html",
+    "title": "Proposed: Provide pdf reading",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI Aria assisted with this article."
+    "text": "Proposed: Provide pdf reading\n\nContext and Problem Statement\nProvide a workflow to read pdf documents.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nWe want to provide pdf reading without implementing a pdf reader.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\n\nConvert pdf into a series of svgs (raster + vector)\nPut svgs in a folder\nClean with https://github.com/RazrFalcon/svgcleaner\nUse godot engine 4’s thorvg\n\n\n\nPositive Consequences\nCan import artwork.\n\n\nNegative Consequences\nNot a real pdf viewer.\n\n\nOption graveyard\nDo nothing.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nA few lines of cli.\n\n\nIs there a reason why this should be core and done by us?\nWanted to write the workflow down.\n\n\nReferences\n\nV-Sekai\n\n\n\nLicense of the contribution\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240111-fspy.html",
-    "href": "decisions/20240111-fspy.html",
-    "title": "Proposed: Camera matching with fSpy.",
+    "objectID": "decisions/20221205-moving-fast-philosophy-development.html",
+    "href": "decisions/20221205-moving-fast-philosophy-development.html",
+    "title": "Proposed: Move fast without breaking things for V-Sekai",
     "section": "",
-    "text": "Status: Proposed \nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nV-Sekai’s mission to be gateways to 3D environments needs camera matching, which is currently a bottleneck in our workflow.\n\n\n\nOur artists and developers need to align concept screenshots within the 3D spaces due to inconsistent camera parameter estimation.\n\n\n\nWe will adopt the fSpy tool that uses vanishing points to estimate camera parameters from images, facilitating a more precise camera match-moving process.\n\n\n\nFind parallel lines and use the longest lines you can.\nYou can move the axes to recenter.\n\n\n\n\n\nThe integration of fSpy into our workflow promises:\n\nA considerable reduction in time for setting up camera parameters.\nEnhanced accuracy and realism in matching 3D models with background images.\nStreamlined asset creation processes, thereby supporting quick iterations.\n\n\n\n\nSome challenges associated with this strategy include:\n\nAn initial learning phase required for effective use of the fSpy tool.\nPotential limitations in images that lack well-defined perspective lines or geometric structure.\nReliance on an external tool which may necessitate ongoing maintenance efforts.\n\n\n\n\nRather than using fSpy, we could continue manual estimation techniques or even develop a custom solution tailored to our specific requirements—both are valid but likely less efficient approaches.\n\n\n\nFor cases where fSpy struggles due to images with no clear vanishing points, alternative methods of camera estimation must be devised, potentially falling back on manual techniques or other specialized tools.\n\n\n\nfSpy integration should become central to our asset creation pipeline. We’ll need to invest in training and potentially develop complementary in-house tools to bridge the gap between fSpy outputs and our existing systems.\n\n\n\n\nV-Sekai GitHub Repository - Explore how V-Sekai leverages social VR functions within Godot Engine.\nV-Sekai Game Project - Delve into the collaborative effort of creating social VR/VRSNS/metaverse elements, all open-source and accessible.\n\nAI assistant Aria assisted with this proposal."
+    "text": "Status: proposed \nDeciders: V-Sekai,fire,\nTags: V-Sekai,\n\n\n\nWe want to discover ways to move faster.\n\n\n\nWe want to discover ways to move faster and last longer.\n\n\n\nPrototype quickly and be adaptive to change.\nWe use continuous integration and continuous deployment.\nWe record our decisions in documentation.\n\n\n\nWe improve our processes.\n\n\n\nProcesses become dead weight.\n\n\n\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\n\nThis is not code but a workflow document.\n\n\n\nWe work on V-Sekai.\n\n\n\n\nV-Sekai\n\n\n\n\nMIT License\n\nCopyright (c) 2018-2022 SaracenOne\nCopyright (c) 2019-2022 K. S. Ernest (iFire) Lee (fire)\nCopyright (c) 2020-2022 Lyuma\nCopyright (c) 2020-2022 MMMaellon\nCopyright (c) 2022 V-Sekai Contributors\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
   },
   {
-    "objectID": "decisions/20240111-fspy.html#metadata",
-    "href": "decisions/20240111-fspy.html#metadata",
-    "title": "Proposed: Camera matching with fSpy.",
+    "objectID": "decisions/20221205-moving-fast-philosophy-development.html#context-and-problem-statement",
+    "href": "decisions/20221205-moving-fast-philosophy-development.html#context-and-problem-statement",
+    "title": "Proposed: Move fast without breaking things for V-Sekai",
     "section": "",
-    "text": "Status: Proposed \nDeciders: V-Sekai\nTags: V-Sekai"
+    "text": "We want to discover ways to move faster."
   },
   {
-    "objectID": "decisions/20240111-fspy.html#the-backdrop",
-    "href": "decisions/20240111-fspy.html#the-backdrop",
-    "title": "Proposed: Camera matching with fSpy.",
+    "objectID": "decisions/20221205-moving-fast-philosophy-development.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20221205-moving-fast-philosophy-development.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: Move fast without breaking things for V-Sekai",
     "section": "",
-    "text": "V-Sekai’s mission to be gateways to 3D environments needs camera matching, which is currently a bottleneck in our workflow."
+    "text": "We want to discover ways to move faster and last longer."
   },
   {
-    "objectID": "decisions/20240111-fspy.html#the-challenge",
-    "href": "decisions/20240111-fspy.html#the-challenge",
-    "title": "Proposed: Camera matching with fSpy.",
+    "objectID": "decisions/20221205-moving-fast-philosophy-development.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20221205-moving-fast-philosophy-development.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Move fast without breaking things for V-Sekai",
     "section": "",
-    "text": "Our artists and developers need to align concept screenshots within the 3D spaces due to inconsistent camera parameter estimation."
+    "text": "Prototype quickly and be adaptive to change.\nWe use continuous integration and continuous deployment.\nWe record our decisions in documentation."
   },
   {
-    "objectID": "decisions/20240111-fspy.html#the-strategy",
-    "href": "decisions/20240111-fspy.html#the-strategy",
-    "title": "Proposed: Camera matching with fSpy.",
+    "objectID": "decisions/20221205-moving-fast-philosophy-development.html#positive-consequences",
+    "href": "decisions/20221205-moving-fast-philosophy-development.html#positive-consequences",
+    "title": "Proposed: Move fast without breaking things for V-Sekai",
     "section": "",
-    "text": "We will adopt the fSpy tool that uses vanishing points to estimate camera parameters from images, facilitating a more precise camera match-moving process.\n\n\n\nFind parallel lines and use the longest lines you can.\nYou can move the axes to recenter."
+    "text": "We improve our processes."
   },
   {
-    "objectID": "decisions/20240111-fspy.html#the-upside",
-    "href": "decisions/20240111-fspy.html#the-upside",
-    "title": "Proposed: Camera matching with fSpy.",
+    "objectID": "decisions/20221205-moving-fast-philosophy-development.html#negative-consequences",
+    "href": "decisions/20221205-moving-fast-philosophy-development.html#negative-consequences",
+    "title": "Proposed: Move fast without breaking things for V-Sekai",
     "section": "",
-    "text": "The integration of fSpy into our workflow promises:\n\nA considerable reduction in time for setting up camera parameters.\nEnhanced accuracy and realism in matching 3D models with background images.\nStreamlined asset creation processes, thereby supporting quick iterations."
+    "text": "Processes become dead weight."
   },
   {
-    "objectID": "decisions/20240111-fspy.html#the-downside",
-    "href": "decisions/20240111-fspy.html#the-downside",
-    "title": "Proposed: Camera matching with fSpy.",
+    "objectID": "decisions/20221205-moving-fast-philosophy-development.html#option-graveyard",
+    "href": "decisions/20221205-moving-fast-philosophy-development.html#option-graveyard",
+    "title": "Proposed: Move fast without breaking things for V-Sekai",
     "section": "",
-    "text": "Some challenges associated with this strategy include:\n\nAn initial learning phase required for effective use of the fSpy tool.\nPotential limitations in images that lack well-defined perspective lines or geometric structure.\nReliance on an external tool which may necessitate ongoing maintenance efforts."
+    "text": "Option: The status quo. \nRejection Reason: This solves nothing."
   },
   {
-    "objectID": "decisions/20240111-fspy.html#the-road-not-taken",
-    "href": "decisions/20240111-fspy.html#the-road-not-taken",
-    "title": "Proposed: Camera matching with fSpy.",
+    "objectID": "decisions/20221205-moving-fast-philosophy-development.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20221205-moving-fast-philosophy-development.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Move fast without breaking things for V-Sekai",
     "section": "",
-    "text": "Rather than using fSpy, we could continue manual estimation techniques or even develop a custom solution tailored to our specific requirements—both are valid but likely less efficient approaches."
+    "text": "This is not code but a workflow document."
   },
   {
-    "objectID": "decisions/20240111-fspy.html#the-infrequent-use-case",
-    "href": "decisions/20240111-fspy.html#the-infrequent-use-case",
-    "title": "Proposed: Camera matching with fSpy.",
+    "objectID": "decisions/20221205-moving-fast-philosophy-development.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20221205-moving-fast-philosophy-development.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Move fast without breaking things for V-Sekai",
     "section": "",
-    "text": "For cases where fSpy struggles due to images with no clear vanishing points, alternative methods of camera estimation must be devised, potentially falling back on manual techniques or other specialized tools."
+    "text": "We work on V-Sekai."
   },
   {
-    "objectID": "decisions/20240111-fspy.html#in-core-and-done-by-us",
-    "href": "decisions/20240111-fspy.html#in-core-and-done-by-us",
-    "title": "Proposed: Camera matching with fSpy.",
+    "objectID": "decisions/20221205-moving-fast-philosophy-development.html#references",
+    "href": "decisions/20221205-moving-fast-philosophy-development.html#references",
+    "title": "Proposed: Move fast without breaking things for V-Sekai",
     "section": "",
-    "text": "fSpy integration should become central to our asset creation pipeline. We’ll need to invest in training and potentially develop complementary in-house tools to bridge the gap between fSpy outputs and our existing systems."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20240111-fspy.html#further-reading",
-    "href": "decisions/20240111-fspy.html#further-reading",
-    "title": "Proposed: Camera matching with fSpy.",
+    "objectID": "decisions/20221205-moving-fast-philosophy-development.html#license-of-the-contribution",
+    "href": "decisions/20221205-moving-fast-philosophy-development.html#license-of-the-contribution",
+    "title": "Proposed: Move fast without breaking things for V-Sekai",
     "section": "",
-    "text": "V-Sekai GitHub Repository - Explore how V-Sekai leverages social VR functions within Godot Engine.\nV-Sekai Game Project - Delve into the collaborative effort of creating social VR/VRSNS/metaverse elements, all open-source and accessible.\n\nAI assistant Aria assisted with this proposal."
+    "text": "MIT License\n\nCopyright (c) 2018-2022 SaracenOne\nCopyright (c) 2019-2022 K. S. Ernest (iFire) Lee (fire)\nCopyright (c) 2020-2022 Lyuma\nCopyright (c) 2020-2022 MMMaellon\nCopyright (c) 2022 V-Sekai Contributors\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
   },
   {
-    "objectID": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html",
-    "href": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html",
-    "title": "Accepted: Degrade V-Sekai’s networking model to work in 2d and with webrtc.",
+    "objectID": "decisions/20231026-blender-steam-beta-version.html",
+    "href": "decisions/20231026-blender-steam-beta-version.html",
+    "title": "Proposed: Solve Blender versions by locking LTS versions on Blender (3.6)",
     "section": "",
-    "text": "Status: accepted \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nMake V-Sekai Godot work in 2D and on the web.\n\n\n\nDegrade the V-Sekai networking model.\n\n\n\n\nThe networking system exclusively uses the MultiplayerAPI, which by default is implemented via ENet, so one would have to swap that part with the WebRTC equivalent. Convert the ENet module to use WebRTC\n\n\n\n\n\nWorks in Opengl Godot 4\nWorks on the web with webrtc\nCan disable 3D for size.\n\n\n\n\n\n[e.g., compromising quality attribute, follow-up decisions required, …]\n\n[this section can be repeated for each option if more than one option is open for consideration]\n\n\n\n\nOption: \nRejection Reason: \n\n\n\n\nNot a few lines of gdscript.\n\n\n\nThis is core.\n\n\n\n\nLink type \n\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Status: Proposed \nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nConstantly changing blender versions is a problem for blender import\n\n\n\nWe want to pin the blender version.\n\n\n\nPin the blender version to the steam version of LTS Blender – Blender (3.6)\n\n\n\nWe get the fast upgrades of steam and the pinning requirement satisfied.\n\n\n\nDependent on steam.\n\n\n\nDownload a version of Blender directly.\n\n\n\nAsk someone to use blender for you.\n\n\n\nThis is a staff note.\n\n\n\n\nV-Sekai\nAI assists this article.\nhttps://www.blender.org/\nhttps://store.steampowered.com/"
   },
   {
-    "objectID": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html#context-and-problem-statement",
-    "href": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html#context-and-problem-statement",
-    "title": "Accepted: Degrade V-Sekai’s networking model to work in 2d and with webrtc.",
+    "objectID": "decisions/20231026-blender-steam-beta-version.html#metadata",
+    "href": "decisions/20231026-blender-steam-beta-version.html#metadata",
+    "title": "Proposed: Solve Blender versions by locking LTS versions on Blender (3.6)",
     "section": "",
-    "text": "Make V-Sekai Godot work in 2D and on the web."
+    "text": "Status: Proposed \nDeciders: V-Sekai\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Accepted: Degrade V-Sekai’s networking model to work in 2d and with webrtc.",
+    "objectID": "decisions/20231026-blender-steam-beta-version.html#the-backdrop",
+    "href": "decisions/20231026-blender-steam-beta-version.html#the-backdrop",
+    "title": "Proposed: Solve Blender versions by locking LTS versions on Blender (3.6)",
     "section": "",
-    "text": "Degrade the V-Sekai networking model."
+    "text": "Constantly changing blender versions is a problem for blender import"
   },
   {
-    "objectID": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Accepted: Degrade V-Sekai’s networking model to work in 2d and with webrtc.",
+    "objectID": "decisions/20231026-blender-steam-beta-version.html#the-challenge",
+    "href": "decisions/20231026-blender-steam-beta-version.html#the-challenge",
+    "title": "Proposed: Solve Blender versions by locking LTS versions on Blender (3.6)",
     "section": "",
-    "text": "The networking system exclusively uses the MultiplayerAPI, which by default is implemented via ENet, so one would have to swap that part with the WebRTC equivalent. Convert the ENet module to use WebRTC"
+    "text": "We want to pin the blender version."
   },
   {
-    "objectID": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html#positive-consequences",
-    "href": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html#positive-consequences",
-    "title": "Accepted: Degrade V-Sekai’s networking model to work in 2d and with webrtc.",
+    "objectID": "decisions/20231026-blender-steam-beta-version.html#the-strategy",
+    "href": "decisions/20231026-blender-steam-beta-version.html#the-strategy",
+    "title": "Proposed: Solve Blender versions by locking LTS versions on Blender (3.6)",
     "section": "",
-    "text": "Works in Opengl Godot 4\nWorks on the web with webrtc\nCan disable 3D for size."
+    "text": "Pin the blender version to the steam version of LTS Blender – Blender (3.6)"
+  },
+  {
+    "objectID": "decisions/20231026-blender-steam-beta-version.html#the-upside",
+    "href": "decisions/20231026-blender-steam-beta-version.html#the-upside",
+    "title": "Proposed: Solve Blender versions by locking LTS versions on Blender (3.6)",
+    "section": "",
+    "text": "We get the fast upgrades of steam and the pinning requirement satisfied."
   },
   {
-    "objectID": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html#negative-consequences",
-    "href": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html#negative-consequences",
-    "title": "Accepted: Degrade V-Sekai’s networking model to work in 2d and with webrtc.",
+    "objectID": "decisions/20231026-blender-steam-beta-version.html#the-downside",
+    "href": "decisions/20231026-blender-steam-beta-version.html#the-downside",
+    "title": "Proposed: Solve Blender versions by locking LTS versions on Blender (3.6)",
     "section": "",
-    "text": "[e.g., compromising quality attribute, follow-up decisions required, …]\n\n[this section can be repeated for each option if more than one option is open for consideration]"
+    "text": "Dependent on steam."
   },
   {
-    "objectID": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html#option-graveyard",
-    "href": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html#option-graveyard",
-    "title": "Accepted: Degrade V-Sekai’s networking model to work in 2d and with webrtc.",
+    "objectID": "decisions/20231026-blender-steam-beta-version.html#the-road-not-taken",
+    "href": "decisions/20231026-blender-steam-beta-version.html#the-road-not-taken",
+    "title": "Proposed: Solve Blender versions by locking LTS versions on Blender (3.6)",
     "section": "",
-    "text": "Option: \nRejection Reason:"
+    "text": "Download a version of Blender directly."
   },
   {
-    "objectID": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Accepted: Degrade V-Sekai’s networking model to work in 2d and with webrtc.",
+    "objectID": "decisions/20231026-blender-steam-beta-version.html#the-infrequent-use-case",
+    "href": "decisions/20231026-blender-steam-beta-version.html#the-infrequent-use-case",
+    "title": "Proposed: Solve Blender versions by locking LTS versions on Blender (3.6)",
     "section": "",
-    "text": "Not a few lines of gdscript."
+    "text": "Ask someone to use blender for you."
   },
   {
-    "objectID": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Accepted: Degrade V-Sekai’s networking model to work in 2d and with webrtc.",
+    "objectID": "decisions/20231026-blender-steam-beta-version.html#in-core-and-done-by-us",
+    "href": "decisions/20231026-blender-steam-beta-version.html#in-core-and-done-by-us",
+    "title": "Proposed: Solve Blender versions by locking LTS versions on Blender (3.6)",
     "section": "",
-    "text": "This is core."
+    "text": "This is a staff note."
   },
   {
-    "objectID": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html#references",
-    "href": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html#references",
-    "title": "Accepted: Degrade V-Sekai’s networking model to work in 2d and with webrtc.",
+    "objectID": "decisions/20231026-blender-steam-beta-version.html#further-reading",
+    "href": "decisions/20231026-blender-steam-beta-version.html#further-reading",
+    "title": "Proposed: Solve Blender versions by locking LTS versions on Blender (3.6)",
     "section": "",
-    "text": "Link type"
+    "text": "V-Sekai\nAI assists this article.\nhttps://www.blender.org/\nhttps://store.steampowered.com/"
   },
   {
-    "objectID": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html#derivative-license",
-    "href": "decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html#derivative-license",
-    "title": "Accepted: Degrade V-Sekai’s networking model to work in 2d and with webrtc.",
+    "objectID": "decisions/20220222-rank-bone-skeletons-with-xgboost.html",
+    "href": "decisions/20220222-rank-bone-skeletons-with-xgboost.html",
+    "title": "Accepted: Rank skeleton #bone names with xgboost",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Status: accepted \n\n\n\nImprove automatic #bone selection\n\n\n\nUse xgboost to rank bones.\n\n\n\n\nInvestigate\n\n\n\n\n\nWe can guess the proper name.\nUseful for the facial mapping problem?\nUseful for the character generator slider recommendation problem?\nGenerate test data by moving the character\nInference requires only single pose inputs.\n\n\n\n\n\nStarring at the abyss.\n\n\n\n\n\nOption:\n\nbpr from Quora\n\nRejection Reason:\n\nBpr from Quora is not used in production.\n\nOption:\n\ndlrm from facebook\n\nRejection Reason:\n\nToo difficult to run\n\nOption:\n\ncatboost\n\nRejection Reason:\n\nToo difficult to run\n\n\n\n\n\nNot a few lines of code.\n\n\n\nWe need this to make the quality of life of creators better.\n\n\n\n\nhttps://github.com/BayesWitnesses/m2cgen\nhttps://stackoverflow.com/questions/36071672/using-xgboost-in-c\nhttps://github.com/facebookresearch/dlrm\nhttps://medium.com/@marthawhite_81346/learning-with-the-criteo-tb-dataset-e3ec12d9d77e\nhttps://www.kaggle.com/c/criteo-display-ad-challenge/data\nSkeleton pool operator from neural blend shapes.\nhttps://tailor.fandom.com/wiki/Types_of_measurement\nhttps://knarkowicz.wordpress.com/2014/04/16/octahedron-normal-vector-encoding/\nhttps://www.kaggle.com/egordm/deep-learning-recommendation-model-dlrm\n\n    @article{li2021learning,\n    author = {Li, Peizhuo and Aberman, Kfir and Hanocka, Rana and Liu, Libin and Sorkine-Hornung, Olga and Chen, Baoquan},\n    title = {Learning Skeletal Articulations with Neural Blend Shapes},\n    journal = {ACM Transactions on Graphics (TOG)},\n    volume = {40},\n    number = {4},\n    pages = {1},\n    year = {2021},\n    publisher = {ACM}\n    }\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.\n\n\n\n\nSupersedes 20211031-use-bpr-to-rank-skeleton-bone-names"
   },
   {
-    "objectID": "decisions/20230813-blender-runner-into-membrane-framework.html",
-    "href": "decisions/20230813-blender-runner-into-membrane-framework.html",
-    "title": "Proposed: Transitioning to Membrane Framework Pipelines with JSON-RPC Blender Runner",
+    "objectID": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#context-and-problem-statement",
+    "href": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#context-and-problem-statement",
+    "title": "Accepted: Rank skeleton #bone names with xgboost",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, Elixir, Membrane Framework, Multiplayer Blender, JSON-RPC\n\n\n\n\nThe current solution for handling multiplayer Blender has its limitations when it comes to scalability and real-time performance. To address these issues, we propose a new approach that leverages Elixir and the Membrane Framework. This will involve rewriting the code and introducing a JSON-RPC Blender runner.\n\n\nIn this new approach, character posing will be handled in real-time and shared across multiple clients. This means that any changes made to a 3D model by one user will be immediately reflected on all other connected clients. This feature will enhance the collaborative experience and allow users to interact with the same 3D models simultaneously.\n\n\n\nThe state of the world, including objects, lighting, camera position, etc., will also be synchronized across all clients. This ensures that all users are experiencing the same environment, further enhancing the sense of immersion and collaboration.\n\n\n\nWe will introduce procedural generation techniques to create unique and dynamic environments. These generated worlds will be shared across all clients, ensuring that each user’s experience is not only immersive but also unique and engaging.\n\n\n\nAny drawings or annotations made using the Grease Pencil tool will be visible to all clients. This allows for collaborative sketching and planning, making it easier for teams to communicate their ideas visually.\n\n\n\nTo facilitate efficient communication with Blender, we’ll implement a JSON-RPC Blender runner. This will allow us to send commands to Blender and receive responses in a structured and standardized format. This feature will streamline the process of interacting with Blender, making it more efficient and user-friendly.\nBy implementing these features, we aim to improve the scalability and real-time performance of our multiplayer Blender solution. This will lead to a more immersive and collaborative experience for our users.\n\n\n\n\nThe main challenge is to translate the existing code into Elixir while maintaining the functionality and improving upon the limitations of the current system. This includes ensuring that the new code can handle larger volumes of users and provide real-time updates without lag or delay.\n\n\n\ngraph LR\n  A[Current Code] --&gt; B[Elixir & Membrane Framework Code]\n  C[No Authentication] --&gt; D[GitHub OAuth 2.0 Login]\n  E[No Database] --&gt; F[Khepri Database Library]\n  G[Blender Runner] --&gt; H[JSON-RPC Blender Runner]\n  I[Triangle Only] --&gt; J[Airlocks for Environment Translation]\nThis strategy leverages Elixir and the Membrane Framework’s unique features, uses the Khepri database library for data management, implements GitHub login using OAuth 2.0 protocol for single sign-on, introduces a JSON-RPC Blender runner for improved communication with Blender, and focuses on the use of triangles (a polygon with 3 vertices) and “Airlocks” for environment translation.\nHere are the key steps:\n\nCodebase: Transition from the current code to Elixir & Membrane Framework Code, tracked in a version control system.\nDependencies: Declare and isolate dependencies explicitly, avoiding reliance on system-wide packages.\nConfig: Store configuration (including GitHub OAuth 2.0 Login credentials) in the environment, not in the code.\nBacking Services: Replace in-memory data persistence with Khepri Database Library, attached as a backing service.\nBuild, Release, Run: Strictly separate these stages, facilitated by the Elixir & Membrane Framework Code.\nProcesses: Execute application as one or more stateless processes, storing needed state in the Khepri database.\nPort Binding: Export services via port binding, making the application self-contained.\nConcurrency: Scale out the application via the process model, allowing for handling increased load.\nDisposability: Aim for fast startup and graceful shutdown to maximize robustness.\nDev/Prod Parity: Keep development, staging, and production environments as similar as possible.\nLogs: Treat logs as event streams, handled by the executing environment.\nAdmin Processes: Run any needed one-off administrative tasks in an identical environment as the regular long-running processes of the app.\nBlender Runner: Implement a JSON-RPC Blender runner to facilitate efficient communication with Blender.\nTriangle Only: This principle ensures that only triangles (polygons with 3 vertices) are used in the graphical representation. This simplifies the rendering process and reduces computational complexity.\nAirlocks: Use airlocks to translate the remote environment to the local environment. This allows for seamless interaction between different parts of the system while maintaining isolation and security.\n\n\n\n\nBy rewriting the code in Elixir, using the Membrane Framework, implementing the Khepri database library, introducing a JSON-RPC Blender runner, focusing on the use of triangles, and employing the “Airlocks” principles, we can expect improved scalability and real-time performance. This will allow for more users to use the system simultaneously without experiencing delays or lags. Additionally, the fault-tolerance feature of Elixir will ensure that the system remains operational even when errors occur.\n\n\n\nRewriting the code will require time and resources. There may also be a learning curve for developers who are not familiar with Elixir, the Membrane Framework, the Khepri database library, JSON-RPC, the concept of using triangles in graphics, and “Airlocks”.\n\n\n\nAn alternative approach would have been to optimize the existing code instead of rewriting it. However, this would not have addressed the inherent limitations of the current system.\n\n\n\nIn cases where the number of users is low and real-time updates are not critical, the current system may still be sufficient. However, as the user base grows and the demand for real-time updates increases, the need for a more scalable and efficient system becomes apparent.\n\n\n\nYes, the rewriting of the code will indeed be done by us as we also maintain the backend services.\n\n\n\n\nV-Sekai\nElixir\nMembrane Framework\nKhepri Database Library\nJSON-RPC\n\nThis article is assisted by AI."
+    "text": "Improve automatic #bone selection"
   },
   {
-    "objectID": "decisions/20230813-blender-runner-into-membrane-framework.html#metadata",
-    "href": "decisions/20230813-blender-runner-into-membrane-framework.html#metadata",
-    "title": "Proposed: Transitioning to Membrane Framework Pipelines with JSON-RPC Blender Runner",
+    "objectID": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Accepted: Rank skeleton #bone names with xgboost",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, Elixir, Membrane Framework, Multiplayer Blender, JSON-RPC"
+    "text": "Use xgboost to rank bones."
   },
   {
-    "objectID": "decisions/20230813-blender-runner-into-membrane-framework.html#backdrop",
-    "href": "decisions/20230813-blender-runner-into-membrane-framework.html#backdrop",
-    "title": "Proposed: Transitioning to Membrane Framework Pipelines with JSON-RPC Blender Runner",
+    "objectID": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Accepted: Rank skeleton #bone names with xgboost",
     "section": "",
-    "text": "The current solution for handling multiplayer Blender has its limitations when it comes to scalability and real-time performance. To address these issues, we propose a new approach that leverages Elixir and the Membrane Framework. This will involve rewriting the code and introducing a JSON-RPC Blender runner.\n\n\nIn this new approach, character posing will be handled in real-time and shared across multiple clients. This means that any changes made to a 3D model by one user will be immediately reflected on all other connected clients. This feature will enhance the collaborative experience and allow users to interact with the same 3D models simultaneously.\n\n\n\nThe state of the world, including objects, lighting, camera position, etc., will also be synchronized across all clients. This ensures that all users are experiencing the same environment, further enhancing the sense of immersion and collaboration.\n\n\n\nWe will introduce procedural generation techniques to create unique and dynamic environments. These generated worlds will be shared across all clients, ensuring that each user’s experience is not only immersive but also unique and engaging.\n\n\n\nAny drawings or annotations made using the Grease Pencil tool will be visible to all clients. This allows for collaborative sketching and planning, making it easier for teams to communicate their ideas visually.\n\n\n\nTo facilitate efficient communication with Blender, we’ll implement a JSON-RPC Blender runner. This will allow us to send commands to Blender and receive responses in a structured and standardized format. This feature will streamline the process of interacting with Blender, making it more efficient and user-friendly.\nBy implementing these features, we aim to improve the scalability and real-time performance of our multiplayer Blender solution. This will lead to a more immersive and collaborative experience for our users."
+    "text": "Investigate"
   },
   {
-    "objectID": "decisions/20230813-blender-runner-into-membrane-framework.html#the-challenge",
-    "href": "decisions/20230813-blender-runner-into-membrane-framework.html#the-challenge",
-    "title": "Proposed: Transitioning to Membrane Framework Pipelines with JSON-RPC Blender Runner",
+    "objectID": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#positive-consequences",
+    "href": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#positive-consequences",
+    "title": "Accepted: Rank skeleton #bone names with xgboost",
     "section": "",
-    "text": "The main challenge is to translate the existing code into Elixir while maintaining the functionality and improving upon the limitations of the current system. This includes ensuring that the new code can handle larger volumes of users and provide real-time updates without lag or delay."
+    "text": "We can guess the proper name.\nUseful for the facial mapping problem?\nUseful for the character generator slider recommendation problem?\nGenerate test data by moving the character\nInference requires only single pose inputs."
   },
   {
-    "objectID": "decisions/20230813-blender-runner-into-membrane-framework.html#strategy",
-    "href": "decisions/20230813-blender-runner-into-membrane-framework.html#strategy",
-    "title": "Proposed: Transitioning to Membrane Framework Pipelines with JSON-RPC Blender Runner",
+    "objectID": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#negative-consequences",
+    "href": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#negative-consequences",
+    "title": "Accepted: Rank skeleton #bone names with xgboost",
     "section": "",
-    "text": "graph LR\n  A[Current Code] --&gt; B[Elixir & Membrane Framework Code]\n  C[No Authentication] --&gt; D[GitHub OAuth 2.0 Login]\n  E[No Database] --&gt; F[Khepri Database Library]\n  G[Blender Runner] --&gt; H[JSON-RPC Blender Runner]\n  I[Triangle Only] --&gt; J[Airlocks for Environment Translation]\nThis strategy leverages Elixir and the Membrane Framework’s unique features, uses the Khepri database library for data management, implements GitHub login using OAuth 2.0 protocol for single sign-on, introduces a JSON-RPC Blender runner for improved communication with Blender, and focuses on the use of triangles (a polygon with 3 vertices) and “Airlocks” for environment translation.\nHere are the key steps:\n\nCodebase: Transition from the current code to Elixir & Membrane Framework Code, tracked in a version control system.\nDependencies: Declare and isolate dependencies explicitly, avoiding reliance on system-wide packages.\nConfig: Store configuration (including GitHub OAuth 2.0 Login credentials) in the environment, not in the code.\nBacking Services: Replace in-memory data persistence with Khepri Database Library, attached as a backing service.\nBuild, Release, Run: Strictly separate these stages, facilitated by the Elixir & Membrane Framework Code.\nProcesses: Execute application as one or more stateless processes, storing needed state in the Khepri database.\nPort Binding: Export services via port binding, making the application self-contained.\nConcurrency: Scale out the application via the process model, allowing for handling increased load.\nDisposability: Aim for fast startup and graceful shutdown to maximize robustness.\nDev/Prod Parity: Keep development, staging, and production environments as similar as possible.\nLogs: Treat logs as event streams, handled by the executing environment.\nAdmin Processes: Run any needed one-off administrative tasks in an identical environment as the regular long-running processes of the app.\nBlender Runner: Implement a JSON-RPC Blender runner to facilitate efficient communication with Blender.\nTriangle Only: This principle ensures that only triangles (polygons with 3 vertices) are used in the graphical representation. This simplifies the rendering process and reduces computational complexity.\nAirlocks: Use airlocks to translate the remote environment to the local environment. This allows for seamless interaction between different parts of the system while maintaining isolation and security."
+    "text": "Starring at the abyss."
   },
   {
-    "objectID": "decisions/20230813-blender-runner-into-membrane-framework.html#the-upside",
-    "href": "decisions/20230813-blender-runner-into-membrane-framework.html#the-upside",
-    "title": "Proposed: Transitioning to Membrane Framework Pipelines with JSON-RPC Blender Runner",
+    "objectID": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#option-graveyard",
+    "href": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#option-graveyard",
+    "title": "Accepted: Rank skeleton #bone names with xgboost",
     "section": "",
-    "text": "By rewriting the code in Elixir, using the Membrane Framework, implementing the Khepri database library, introducing a JSON-RPC Blender runner, focusing on the use of triangles, and employing the “Airlocks” principles, we can expect improved scalability and real-time performance. This will allow for more users to use the system simultaneously without experiencing delays or lags. Additionally, the fault-tolerance feature of Elixir will ensure that the system remains operational even when errors occur."
+    "text": "Option:\n\nbpr from Quora\n\nRejection Reason:\n\nBpr from Quora is not used in production.\n\nOption:\n\ndlrm from facebook\n\nRejection Reason:\n\nToo difficult to run\n\nOption:\n\ncatboost\n\nRejection Reason:\n\nToo difficult to run"
   },
   {
-    "objectID": "decisions/20230813-blender-runner-into-membrane-framework.html#the-downside",
-    "href": "decisions/20230813-blender-runner-into-membrane-framework.html#the-downside",
-    "title": "Proposed: Transitioning to Membrane Framework Pipelines with JSON-RPC Blender Runner",
+    "objectID": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Accepted: Rank skeleton #bone names with xgboost",
     "section": "",
-    "text": "Rewriting the code will require time and resources. There may also be a learning curve for developers who are not familiar with Elixir, the Membrane Framework, the Khepri database library, JSON-RPC, the concept of using triangles in graphics, and “Airlocks”."
+    "text": "Not a few lines of code."
   },
   {
-    "objectID": "decisions/20230813-blender-runner-into-membrane-framework.html#the-road-not-taken",
-    "href": "decisions/20230813-blender-runner-into-membrane-framework.html#the-road-not-taken",
-    "title": "Proposed: Transitioning to Membrane Framework Pipelines with JSON-RPC Blender Runner",
+    "objectID": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Accepted: Rank skeleton #bone names with xgboost",
     "section": "",
-    "text": "An alternative approach would have been to optimize the existing code instead of rewriting it. However, this would not have addressed the inherent limitations of the current system."
+    "text": "We need this to make the quality of life of creators better."
   },
   {
-    "objectID": "decisions/20230813-blender-runner-into-membrane-framework.html#the-infrequent-use-case",
-    "href": "decisions/20230813-blender-runner-into-membrane-framework.html#the-infrequent-use-case",
-    "title": "Proposed: Transitioning to Membrane Framework Pipelines with JSON-RPC Blender Runner",
+    "objectID": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#references",
+    "href": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#references",
+    "title": "Accepted: Rank skeleton #bone names with xgboost",
     "section": "",
-    "text": "In cases where the number of users is low and real-time updates are not critical, the current system may still be sufficient. However, as the user base grows and the demand for real-time updates increases, the need for a more scalable and efficient system becomes apparent."
+    "text": "https://github.com/BayesWitnesses/m2cgen\nhttps://stackoverflow.com/questions/36071672/using-xgboost-in-c\nhttps://github.com/facebookresearch/dlrm\nhttps://medium.com/@marthawhite_81346/learning-with-the-criteo-tb-dataset-e3ec12d9d77e\nhttps://www.kaggle.com/c/criteo-display-ad-challenge/data\nSkeleton pool operator from neural blend shapes.\nhttps://tailor.fandom.com/wiki/Types_of_measurement\nhttps://knarkowicz.wordpress.com/2014/04/16/octahedron-normal-vector-encoding/\nhttps://www.kaggle.com/egordm/deep-learning-recommendation-model-dlrm\n\n    @article{li2021learning,\n    author = {Li, Peizhuo and Aberman, Kfir and Hanocka, Rana and Liu, Libin and Sorkine-Hornung, Olga and Chen, Baoquan},\n    title = {Learning Skeletal Articulations with Neural Blend Shapes},\n    journal = {ACM Transactions on Graphics (TOG)},\n    volume = {40},\n    number = {4},\n    pages = {1},\n    year = {2021},\n    publisher = {ACM}\n    }"
   },
   {
-    "objectID": "decisions/20230813-blender-runner-into-membrane-framework.html#in-core-and-done-by-us",
-    "href": "decisions/20230813-blender-runner-into-membrane-framework.html#in-core-and-done-by-us",
-    "title": "Proposed: Transitioning to Membrane Framework Pipelines with JSON-RPC Blender Runner",
+    "objectID": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#derivative-license",
+    "href": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#derivative-license",
+    "title": "Accepted: Rank skeleton #bone names with xgboost",
     "section": "",
-    "text": "Yes, the rewriting of the code will indeed be done by us as we also maintain the backend services."
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230813-blender-runner-into-membrane-framework.html#further-reading",
-    "href": "decisions/20230813-blender-runner-into-membrane-framework.html#further-reading",
-    "title": "Proposed: Transitioning to Membrane Framework Pipelines with JSON-RPC Blender Runner",
+    "objectID": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#links",
+    "href": "decisions/20220222-rank-bone-skeletons-with-xgboost.html#links",
+    "title": "Accepted: Rank skeleton #bone names with xgboost",
     "section": "",
-    "text": "V-Sekai\nElixir\nMembrane Framework\nKhepri Database Library\nJSON-RPC\n\nThis article is assisted by AI."
+    "text": "Supersedes 20211031-use-bpr-to-rank-skeleton-bone-names"
   },
   {
-    "objectID": "decisions/20240217-workload-benchmarking.html",
-    "href": "decisions/20240217-workload-benchmarking.html",
-    "title": "Proposed: for using workloads to emulate the usage patterns",
+    "objectID": "decisions/20230527-server-side-content-validation.html",
+    "href": "decisions/20230527-server-side-content-validation.html",
+    "title": "Proposed: Implement server-side content validation export followed by a sanitization service and CDN support",
     "section": "",
-    "text": "V-Sekai is a social virtual reality platform. Users interact with each other through avatars in different environments. The main operations include high read operations, moderate to high write operations, and latency sensitivity.\n\n\n\nTo ensure the best performance and user experience, we need to understand how the database system might perform under conditions similar to those experienced by V-Sekai. This includes balancing between high read operations for content delivery and write operations for dynamic user interactions, all while maintaining low latency.\n\n\n\nWe propose to use the Yahoo! Cloud Serving Benchmark (YCSB) workload to emulate the usage patterns of V-Sekai. This would involve a combination of workloads:\n\n\n\n50% read and 50% update operations.\nSimulates user interactions within V-Sekai, such as position updates, gestures, or environment interactions.\n\n\n\n\n\n95% read and 5% update operations.\nRepresents the frequent fetching of environment and avatar details.\n\n\n\n\n\nAdjusting the read and write ratios to reflect the real-time, interactive nature of V-Sekai.\nEmphasizing low latency in the benchmarking parameters.\n\n1. Set up YCSB with Workload A and B\n2. Customize the read/write ratio based on V-Sekai's usage patterns\n3. Emphasize low latency in the benchmarking parameters\n4. Run the benchmark and analyze the results\n\n\n\n\n\nProvides insights into how a database system might perform under V-Sekai-like conditions.\nHelps optimize the balance between read and write operations.\nEnsures low latency for a seamless user experience.\n\n\n\n\n\nRequires careful tuning and understanding of YCSB workloads.\nThe benchmark results might not perfectly reflect real-world usage due to the synthetic nature of benchmarks.\n\n\n\n\nAn alternative would be to use pre-defined YCSB workloads without customization. However, this might not accurately reflect V-Sekai’s specific usage patterns.\n\n\n\nIn scenarios where the usage patterns are not consistent or predictable, customizing the YCSB workload might not provide accurate insights.\n\n\n\nThe setup and customization of the YCSB benchmark will be done by the V-Sekai development team with support from the community stakeholders.\n\n\n\nStatus: Rejected\n\n\n\n\nV-Sekai development team and community stakeholders.\n\n\n\n\n\nV-Sekai, Performance Benchmarking, Database Optimization\n\n\n\n\n\nV-Sekai · GitHub\nV-Sekai/v-sekai-game\n\nThis proposal was assisted by Aria, an AI assistant."
+    "text": "Status: proposed\nDeciders: V-Sekai, Bioblaze Payne, fire\nTags: V-Sekai, GPT-4\n\n\n\n\nV-Sekai is a virtual world platform that allows users to create and share content. However, there are limitations in terms of content validation and distribution, which can lead to potential security risks and slow content delivery.\n\n\n\nImplement server-side validation export followed by a sanitization service and integrate with a Content Delivery Network (CDN) for efficient content distribution.\n\n\n\n\nServer-side validation: Develop a server-side validation system that checks the uploaded content for any malicious code or vulnerabilities.\nSanitization service: Implement a sanitization service that cleanses the content from any harmful elements before it’s distributed.\nCDN integration: Integrate the platform with a CDN to ensure fast and reliable content delivery to users worldwide.\n\n\n\n\n\nEnhanced security: Server-side validation and sanitization will help prevent malicious content from being distributed.\nImproved performance: CDN integration will speed up content delivery and provide a better user experience.\nScalability: The proposed solution will allow the platform to handle increased traffic and content uploads efficiently.\n\n\n\n\n\nIncreased development time: Implementing the proposed solution may require additional development time and resources.\nMaintenance: Ongoing maintenance of the server-side validation, sanitization service, and CDN integration will be required.\n\n\n\n\n\nClient-side validation only: This option was discarded due to its limited effectiveness in preventing malicious content distribution.\nNo CDN integration: This option was discarded as it would not address the issue of slow content delivery.\n\n\n\n\nNo, the proposed solution requires a more comprehensive approach to ensure secure and efficient content distribution.\n\n\n\nYes, implementing server-side validation, sanitization service, and CDN integration is essential for maintaining the platform’s security and providing a seamless user experience. These features should be part of the core functionality to ensure consistent performance and reliability.\n\n\n\n\nV-Sekai\nContent Delivery Network (CDN)"
   },
   {
-    "objectID": "decisions/20240217-workload-benchmarking.html#context",
-    "href": "decisions/20240217-workload-benchmarking.html#context",
-    "title": "Proposed: for using workloads to emulate the usage patterns",
+    "objectID": "decisions/20230527-server-side-content-validation.html#metadata",
+    "href": "decisions/20230527-server-side-content-validation.html#metadata",
+    "title": "Proposed: Implement server-side content validation export followed by a sanitization service and CDN support",
     "section": "",
-    "text": "V-Sekai is a social virtual reality platform. Users interact with each other through avatars in different environments. The main operations include high read operations, moderate to high write operations, and latency sensitivity."
+    "text": "Status: proposed\nDeciders: V-Sekai, Bioblaze Payne, fire\nTags: V-Sekai, GPT-4"
   },
   {
-    "objectID": "decisions/20240217-workload-benchmarking.html#problem-statement",
-    "href": "decisions/20240217-workload-benchmarking.html#problem-statement",
-    "title": "Proposed: for using workloads to emulate the usage patterns",
+    "objectID": "decisions/20230527-server-side-content-validation.html#context-and-problem-statement",
+    "href": "decisions/20230527-server-side-content-validation.html#context-and-problem-statement",
+    "title": "Proposed: Implement server-side content validation export followed by a sanitization service and CDN support",
     "section": "",
-    "text": "To ensure the best performance and user experience, we need to understand how the database system might perform under conditions similar to those experienced by V-Sekai. This includes balancing between high read operations for content delivery and write operations for dynamic user interactions, all while maintaining low latency."
+    "text": "V-Sekai is a virtual world platform that allows users to create and share content. However, there are limitations in terms of content validation and distribution, which can lead to potential security risks and slow content delivery."
   },
   {
-    "objectID": "decisions/20240217-workload-benchmarking.html#proposed-solution",
-    "href": "decisions/20240217-workload-benchmarking.html#proposed-solution",
-    "title": "Proposed: for using workloads to emulate the usage patterns",
+    "objectID": "decisions/20230527-server-side-content-validation.html#proposed-solution",
+    "href": "decisions/20230527-server-side-content-validation.html#proposed-solution",
+    "title": "Proposed: Implement server-side content validation export followed by a sanitization service and CDN support",
     "section": "",
-    "text": "We propose to use the Yahoo! Cloud Serving Benchmark (YCSB) workload to emulate the usage patterns of V-Sekai. This would involve a combination of workloads:\n\n\n\n50% read and 50% update operations.\nSimulates user interactions within V-Sekai, such as position updates, gestures, or environment interactions.\n\n\n\n\n\n95% read and 5% update operations.\nRepresents the frequent fetching of environment and avatar details.\n\n\n\n\n\nAdjusting the read and write ratios to reflect the real-time, interactive nature of V-Sekai.\nEmphasizing low latency in the benchmarking parameters.\n\n1. Set up YCSB with Workload A and B\n2. Customize the read/write ratio based on V-Sekai's usage patterns\n3. Emphasize low latency in the benchmarking parameters\n4. Run the benchmark and analyze the results"
+    "text": "Implement server-side validation export followed by a sanitization service and integrate with a Content Delivery Network (CDN) for efficient content distribution."
   },
   {
-    "objectID": "decisions/20240217-workload-benchmarking.html#benefits",
-    "href": "decisions/20240217-workload-benchmarking.html#benefits",
-    "title": "Proposed: for using workloads to emulate the usage patterns",
+    "objectID": "decisions/20230527-server-side-content-validation.html#implementation",
+    "href": "decisions/20230527-server-side-content-validation.html#implementation",
+    "title": "Proposed: Implement server-side content validation export followed by a sanitization service and CDN support",
     "section": "",
-    "text": "Provides insights into how a database system might perform under V-Sekai-like conditions.\nHelps optimize the balance between read and write operations.\nEnsures low latency for a seamless user experience."
+    "text": "Server-side validation: Develop a server-side validation system that checks the uploaded content for any malicious code or vulnerabilities.\nSanitization service: Implement a sanitization service that cleanses the content from any harmful elements before it’s distributed.\nCDN integration: Integrate the platform with a CDN to ensure fast and reliable content delivery to users worldwide."
   },
   {
-    "objectID": "decisions/20240217-workload-benchmarking.html#downsides",
-    "href": "decisions/20240217-workload-benchmarking.html#downsides",
-    "title": "Proposed: for using workloads to emulate the usage patterns",
+    "objectID": "decisions/20230527-server-side-content-validation.html#positive-consequences",
+    "href": "decisions/20230527-server-side-content-validation.html#positive-consequences",
+    "title": "Proposed: Implement server-side content validation export followed by a sanitization service and CDN support",
     "section": "",
-    "text": "Requires careful tuning and understanding of YCSB workloads.\nThe benchmark results might not perfectly reflect real-world usage due to the synthetic nature of benchmarks."
+    "text": "Enhanced security: Server-side validation and sanitization will help prevent malicious content from being distributed.\nImproved performance: CDN integration will speed up content delivery and provide a better user experience.\nScalability: The proposed solution will allow the platform to handle increased traffic and content uploads efficiently."
   },
   {
-    "objectID": "decisions/20240217-workload-benchmarking.html#the-road-not-taken",
-    "href": "decisions/20240217-workload-benchmarking.html#the-road-not-taken",
-    "title": "Proposed: for using workloads to emulate the usage patterns",
+    "objectID": "decisions/20230527-server-side-content-validation.html#negative-consequences",
+    "href": "decisions/20230527-server-side-content-validation.html#negative-consequences",
+    "title": "Proposed: Implement server-side content validation export followed by a sanitization service and CDN support",
     "section": "",
-    "text": "An alternative would be to use pre-defined YCSB workloads without customization. However, this might not accurately reflect V-Sekai’s specific usage patterns."
+    "text": "Increased development time: Implementing the proposed solution may require additional development time and resources.\nMaintenance: Ongoing maintenance of the server-side validation, sanitization service, and CDN integration will be required."
   },
   {
-    "objectID": "decisions/20240217-workload-benchmarking.html#the-infrequent-use-case",
-    "href": "decisions/20240217-workload-benchmarking.html#the-infrequent-use-case",
-    "title": "Proposed: for using workloads to emulate the usage patterns",
+    "objectID": "decisions/20230527-server-side-content-validation.html#option-graveyard",
+    "href": "decisions/20230527-server-side-content-validation.html#option-graveyard",
+    "title": "Proposed: Implement server-side content validation export followed by a sanitization service and CDN support",
     "section": "",
-    "text": "In scenarios where the usage patterns are not consistent or predictable, customizing the YCSB workload might not provide accurate insights."
+    "text": "Client-side validation only: This option was discarded due to its limited effectiveness in preventing malicious content distribution.\nNo CDN integration: This option was discarded as it would not address the issue of slow content delivery."
   },
   {
-    "objectID": "decisions/20240217-workload-benchmarking.html#in-core-and-done-by-us",
-    "href": "decisions/20240217-workload-benchmarking.html#in-core-and-done-by-us",
-    "title": "Proposed: for using workloads to emulate the usage patterns",
+    "objectID": "decisions/20230527-server-side-content-validation.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230527-server-side-content-validation.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Implement server-side content validation export followed by a sanitization service and CDN support",
     "section": "",
-    "text": "The setup and customization of the YCSB benchmark will be done by the V-Sekai development team with support from the community stakeholders."
+    "text": "No, the proposed solution requires a more comprehensive approach to ensure secure and efficient content distribution."
   },
   {
-    "objectID": "decisions/20240217-workload-benchmarking.html#status",
-    "href": "decisions/20240217-workload-benchmarking.html#status",
-    "title": "Proposed: for using workloads to emulate the usage patterns",
+    "objectID": "decisions/20230527-server-side-content-validation.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230527-server-side-content-validation.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Implement server-side content validation export followed by a sanitization service and CDN support",
     "section": "",
-    "text": "Status: Rejected"
+    "text": "Yes, implementing server-side validation, sanitization service, and CDN integration is essential for maintaining the platform’s security and providing a seamless user experience. These features should be part of the core functionality to ensure consistent performance and reliability."
   },
   {
-    "objectID": "decisions/20240217-workload-benchmarking.html#decision-makers",
-    "href": "decisions/20240217-workload-benchmarking.html#decision-makers",
-    "title": "Proposed: for using workloads to emulate the usage patterns",
+    "objectID": "decisions/20230527-server-side-content-validation.html#references",
+    "href": "decisions/20230527-server-side-content-validation.html#references",
+    "title": "Proposed: Implement server-side content validation export followed by a sanitization service and CDN support",
     "section": "",
-    "text": "V-Sekai development team and community stakeholders."
+    "text": "V-Sekai\nContent Delivery Network (CDN)"
   },
   {
-    "objectID": "decisions/20240217-workload-benchmarking.html#tags",
-    "href": "decisions/20240217-workload-benchmarking.html#tags",
-    "title": "Proposed: for using workloads to emulate the usage patterns",
+    "objectID": "decisions/20230830-better-object-pick.html",
+    "href": "decisions/20230830-better-object-pick.html",
+    "title": "Proposed: Improving VR Experience",
     "section": "",
-    "text": "V-Sekai, Performance Benchmarking, Database Optimization"
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nV-Sekai is a virtual reality (VR) platform that offers users the opportunity to immerse themselves in virtual worlds. However, there are certain limitations that hinder the overall user experience. This documentation aims to address these limitations by proposing specific areas for improvement within V-Sekai.\n\n\n\nV-Sekai currently faces several limitations, including non-functional menus in VR mode and a limited number of available worlds. To overcome these challenges and enhance the user experience, we must prioritize and focus on one area for improvement.\n\n\nImproving Object Pickup and Menus: Enhancing object pickup mechanics and menus can make interactions within V-Sekai more intuitive and user-friendly. This may include refining controls, feedback mechanisms for object pickup, and finding alternative methods to access menus while in VR mode.\n\n\n\n\nTo ensure efficient use of time and resources, it is advisable to choose one area to focus on and strive to complete it within a two-week timeframe. This focused approach allows for significant progress in improving V-Sekai.\n\n\n\nBy addressing these limitations, V-Sekai can offer a more seamless and immersive VR experience. Improving object pickup and menus will enhance user interactions, making them more intuitive and user-friendly. This will ultimately result in a more engaging and enjoyable experience for V-Sekai users.\n\n\n\nGiven the limited timeframe, it may not be possible to address all the identified limitations simultaneously. Additionally, the complexity of refining object pickup mechanics and menus may present challenges in achieving substantial improvements within the two-week timeframe. It’s important to carefully assess the scope and feasibility of the proposed enhancements before committing to the timeframe.\n\n\n\nWhile focusing on improving object pickup and menus is recommended for the given timeframe, it’s important to acknowledge that there are other potential areas for improvement. Exploring options such as expanding the variety of worlds, integrating backend services, or optimizing performance can be considered in future iterations of V-Sekai.\n\n\n\nThe development team at V-Sekai should primarily handle the implementation and integration of the chosen improvement. However, collaborative efforts involving developers, designers, and user experience experts may be necessary to ensure the improvements align with the overall vision and goals of V-Sekai.\n\n\n\n\nV-Sekai\nThis article is assisted by AI."
   },
   {
-    "objectID": "decisions/20240217-workload-benchmarking.html#further-reading",
-    "href": "decisions/20240217-workload-benchmarking.html#further-reading",
-    "title": "Proposed: for using workloads to emulate the usage patterns",
+    "objectID": "decisions/20230830-better-object-pick.html#metadata",
+    "href": "decisions/20230830-better-object-pick.html#metadata",
+    "title": "Proposed: Improving VR Experience",
     "section": "",
-    "text": "V-Sekai · GitHub\nV-Sekai/v-sekai-game\n\nThis proposal was assisted by Aria, an AI assistant."
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20210212-use-log4brains-to-manage-the-adrs.html",
-    "href": "decisions/20210212-use-log4brains-to-manage-the-adrs.html",
-    "title": "Superseded: Use Log4brains to manage the ADRs",
+    "objectID": "decisions/20230830-better-object-pick.html#introduction",
+    "href": "decisions/20230830-better-object-pick.html#introduction",
+    "title": "Proposed: Improving VR Experience",
     "section": "",
-    "text": "Status: superseded\nDate: 2021-02-11\nTags: dev-tools, doc\n\n\n\nWe want to record architectural decisions made in this project. Which tool(s) should we use to manage these records?\n\n\n\n\nLog4brains: architecture knowledge base (command-line + static site generator)\nADR Tools: command-line to create ADRs\nADR Tools Python: command-line to create ADRs\nadr-viewer: static site generator\nadr-log: command-line to create a TOC of ADRs\n\n\n\n\nChosen option: “Log4brains”, because it includes the features of all the other tools, and even more.\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "V-Sekai is a virtual reality (VR) platform that offers users the opportunity to immerse themselves in virtual worlds. However, there are certain limitations that hinder the overall user experience. This documentation aims to address these limitations by proposing specific areas for improvement within V-Sekai."
   },
   {
-    "objectID": "decisions/20210212-use-log4brains-to-manage-the-adrs.html#context-and-problem-statement",
-    "href": "decisions/20210212-use-log4brains-to-manage-the-adrs.html#context-and-problem-statement",
-    "title": "Superseded: Use Log4brains to manage the ADRs",
+    "objectID": "decisions/20230830-better-object-pick.html#the-challenge",
+    "href": "decisions/20230830-better-object-pick.html#the-challenge",
+    "title": "Proposed: Improving VR Experience",
     "section": "",
-    "text": "We want to record architectural decisions made in this project. Which tool(s) should we use to manage these records?"
+    "text": "V-Sekai currently faces several limitations, including non-functional menus in VR mode and a limited number of available worlds. To overcome these challenges and enhance the user experience, we must prioritize and focus on one area for improvement.\n\n\nImproving Object Pickup and Menus: Enhancing object pickup mechanics and menus can make interactions within V-Sekai more intuitive and user-friendly. This may include refining controls, feedback mechanisms for object pickup, and finding alternative methods to access menus while in VR mode."
   },
   {
-    "objectID": "decisions/20210212-use-log4brains-to-manage-the-adrs.html#considered-options",
-    "href": "decisions/20210212-use-log4brains-to-manage-the-adrs.html#considered-options",
-    "title": "Superseded: Use Log4brains to manage the ADRs",
+    "objectID": "decisions/20230830-better-object-pick.html#the-strategy",
+    "href": "decisions/20230830-better-object-pick.html#the-strategy",
+    "title": "Proposed: Improving VR Experience",
     "section": "",
-    "text": "Log4brains: architecture knowledge base (command-line + static site generator)\nADR Tools: command-line to create ADRs\nADR Tools Python: command-line to create ADRs\nadr-viewer: static site generator\nadr-log: command-line to create a TOC of ADRs"
+    "text": "To ensure efficient use of time and resources, it is advisable to choose one area to focus on and strive to complete it within a two-week timeframe. This focused approach allows for significant progress in improving V-Sekai."
   },
   {
-    "objectID": "decisions/20210212-use-log4brains-to-manage-the-adrs.html#decision-outcome",
-    "href": "decisions/20210212-use-log4brains-to-manage-the-adrs.html#decision-outcome",
-    "title": "Superseded: Use Log4brains to manage the ADRs",
+    "objectID": "decisions/20230830-better-object-pick.html#upsides",
+    "href": "decisions/20230830-better-object-pick.html#upsides",
+    "title": "Proposed: Improving VR Experience",
     "section": "",
-    "text": "Chosen option: “Log4brains”, because it includes the features of all the other tools, and even more."
+    "text": "By addressing these limitations, V-Sekai can offer a more seamless and immersive VR experience. Improving object pickup and menus will enhance user interactions, making them more intuitive and user-friendly. This will ultimately result in a more engaging and enjoyable experience for V-Sekai users."
   },
   {
-    "objectID": "decisions/20210212-use-log4brains-to-manage-the-adrs.html#derivative-license",
-    "href": "decisions/20210212-use-log4brains-to-manage-the-adrs.html#derivative-license",
-    "title": "Superseded: Use Log4brains to manage the ADRs",
+    "objectID": "decisions/20230830-better-object-pick.html#downsides",
+    "href": "decisions/20230830-better-object-pick.html#downsides",
+    "title": "Proposed: Improving VR Experience",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Given the limited timeframe, it may not be possible to address all the identified limitations simultaneously. Additionally, the complexity of refining object pickup mechanics and menus may present challenges in achieving substantial improvements within the two-week timeframe. It’s important to carefully assess the scope and feasibility of the proposed enhancements before committing to the timeframe."
   },
   {
-    "objectID": "decisions/20230608-v-sekai-roadmap.html",
-    "href": "decisions/20230608-v-sekai-roadmap.html",
-    "title": "Superseded: V-Sekai Roadmap and Goals 2023-06-08",
+    "objectID": "decisions/20230830-better-object-pick.html#the-road-not-taken",
+    "href": "decisions/20230830-better-object-pick.html#the-road-not-taken",
+    "title": "Proposed: Improving VR Experience",
     "section": "",
-    "text": "Superseded: V-Sekai Roadmap and Goals 2023-06-08\n\nMetadata\n\nStatus: superseded by 20230618-v-sekai-roadmap.md \nDeciders: V-Sekai,fire,lyuma,\nTags: V-Sekai,chatgpt4 summary,\n\n\n\nContext and Problem Statement\nWhat is the V-Sekai Roadmap and Goals?\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nThe roadmap presented here is short-term.\n\n\nDescribe how your proposal will work with code, pseudo-code, mock-ups, or diagrams\ngraph LR\n  subgraph Short Term\n    A[June 08th, 2023] --&gt; D[IK Points for V-sekai]\n    D --&gt; E[Investigate ManyBoneIK & mediapipe to support Facial Mocap to ARKit 52 blendshape and audio to face]\n    E --&gt; F[Elixir mvsqlite Serversidecar]\n    F --&gt; I[Add jitter buffer to godot_speech]\n  end\n  subgraph Mid-term Term\n    D --&gt; E[Vrm upload to the asset library]\n    F --&gt; G[Unidot Unity Import upload to the asset library]\n    G --&gt; H[Add jitter buffer to godot_speech]\n    H --&gt; I[Implement onevoip]\n  end\n\n\nPositive Consequences\nWe can create V-Sekai easier.\n\n\nNegative Consequences\nOverhead might be hard.\n\n\nOption graveyard\n\nImplementing a custom voice chat solution instead of using onevoip\nWaiting for Godot Engine 4.2 instead of assisting with 4.1 features\nIgnoring SkeletonIK3D issues and focusing on other aspects\n\n\n\nIf this enhancement will be used infrequently, can it be worked around with a few lines of script?\nNo. This is a process.\n\n\nIs there a reason why this should be core and done by us?\nThis is a core process for V-Sekai.\n\n\nReferences\n\nV-Sekai"
+    "text": "While focusing on improving object pickup and menus is recommended for the given timeframe, it’s important to acknowledge that there are other potential areas for improvement. Exploring options such as expanding the variety of worlds, integrating backend services, or optimizing performance can be considered in future iterations of V-Sekai."
   },
   {
-    "objectID": "decisions/20211031-membrane-framework-streaming-mixer.html",
-    "href": "decisions/20211031-membrane-framework-streaming-mixer.html",
-    "title": "Proposed: Membrane Framework streaming Mixer",
+    "objectID": "decisions/20230830-better-object-pick.html#in-core-and-done-by-us",
+    "href": "decisions/20230830-better-object-pick.html#in-core-and-done-by-us",
+    "title": "Proposed: Improving VR Experience",
     "section": "",
-    "text": "Proposed: Membrane Framework streaming Mixer\n\nContext and Problem Statement\nI want to stream 3d content to godot engine live.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nCurrently having an import and export pipeline that isn’t live is frustrating.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n\nFind a stable version of Blender\nUse mixer plugin with that stable version\nMake Godot Engine sync plugin\n???\nMake a mixer sync server\nCreate python pickle packet\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot a few lines of code.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nI found this idea and its cool.\n\n\nReferences\n\nhttps://github.com/ubisoft/mixer\nhttps://github.com/ubisoft/vrtist\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "The development team at V-Sekai should primarily handle the implementation and integration of the chosen improvement. However, collaborative efforts involving developers, designers, and user experience experts may be necessary to ensure the improvements align with the overall vision and goals of V-Sekai."
   },
   {
-    "objectID": "decisions/20240111-fit-clothing-on-humans-without-tearing.html",
-    "href": "decisions/20240111-fit-clothing-on-humans-without-tearing.html",
-    "title": "Draft: Fit Clothing on Humans Without Tearing",
+    "objectID": "decisions/20230830-better-object-pick.html#further-reading",
+    "href": "decisions/20230830-better-object-pick.html#further-reading",
+    "title": "Proposed: Improving VR Experience",
     "section": "",
-    "text": "Status: Draft\nDeciders: V-Sekai, Fire, Joe Cat\nTags: V-Sekai\n\n\n\n\nThe challenge is to accurately fit clothing on a 3D human model without causing any tearing in the fabric. The proposed solution involves utilizing machine learning technology that ensures constraints are maintained for vertex faces during the fitting process."
+    "text": "V-Sekai\nThis article is assisted by AI."
   },
   {
-    "objectID": "decisions/20240111-fit-clothing-on-humans-without-tearing.html#metadata",
-    "href": "decisions/20240111-fit-clothing-on-humans-without-tearing.html#metadata",
-    "title": "Draft: Fit Clothing on Humans Without Tearing",
+    "objectID": "decisions/20211031-1000-player-servers.html",
+    "href": "decisions/20211031-1000-player-servers.html",
+    "title": "Proposed: 1000 player servers",
     "section": "",
-    "text": "Status: Draft\nDeciders: V-Sekai, Fire, Joe Cat\nTags: V-Sekai"
+    "text": "Proposed: 1000 player servers\n\nContext and Problem Statement\nWant to support large groups of players\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nSmall crowds aren’t plausible.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n\nperformance testing\nrobots\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nRequires devops and scripting.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nI have an approach!\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240111-fit-clothing-on-humans-without-tearing.html#context",
-    "href": "decisions/20240111-fit-clothing-on-humans-without-tearing.html#context",
-    "title": "Draft: Fit Clothing on Humans Without Tearing",
+    "objectID": "decisions/20220131-elixir-desktop-uro.html",
+    "href": "decisions/20220131-elixir-desktop-uro.html",
+    "title": "Proposed: Make a desktop version of Uro for ease of development.",
     "section": "",
-    "text": "The challenge is to accurately fit clothing on a 3D human model without causing any tearing in the fabric. The proposed solution involves utilizing machine learning technology that ensures constraints are maintained for vertex faces during the fitting process."
+    "text": "Status: proposed \nDeciders: V-Sekai,fire,\nTags: V-Sekai,\n\n\n\nIt is hard to deploy URO.\n\n\n\nDeploy URO using Elixir Desktop.\n\n\n\n\nBuild of Elixir Desktop\nValidate both Windows and Linux builds.\nFocus on Linux first.\n\n\n\n\n\nAble to deploy Uro easier.\n\n\n\n\n\nIs this the most important thing to do with limited resources?\n\n\n\n\n\nOption: Current status.\nRejection Reason: Don’t have a platform for developing the backend.\n\n\n\n\nNot a few lines of code.\n\n\n\nWe are the maintainers of uro.\n\n\n\n\nhttps://github.com/elixir-desktop/desktop\nhttps://github.com/V-Sekai/uro\n\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230619-move-cockroachdb-to-yugabyte.html",
-    "href": "decisions/20230619-move-cockroachdb-to-yugabyte.html",
-    "title": "Rejected: V-Sekai Database Solution for 50,000 Concurrent Online Users",
+    "objectID": "decisions/20220131-elixir-desktop-uro.html#context-and-problem-statement",
+    "href": "decisions/20220131-elixir-desktop-uro.html#context-and-problem-statement",
+    "title": "Proposed: Make a desktop version of Uro for ease of development.",
     "section": "",
-    "text": "Status: rejected\nDeciders: V-Sekai, fire\nTags: V-Sekai, llm summarization\n\n\n\n\nV-Sekai is currently facing a decision on which database solution to use for their project that can handle the load of 50,000 concurrent online users. The options being considered are PostgreSQL, CockroachDB, SQLite on FoundationDB, or YugabyteDB. Each option has its own set of advantages and disadvantages, and the team needs to determine which one best fits their requirements.\n\n\n\nBased on the discussion, it seems that YugabyteDB might be a suitable choice for V-Sekai’s needs. It offers a single-node setup with the potential for growth, supports a wide range of data types, and provides externally consistent transaction levels. Additionally, YugabyteDB appears to be more compatible with the existing schema compared to SQLite.\n\n\n\nTo implement YugabyteDB as the chosen database solution, the following steps should be taken:\n\nEvaluate YugabyteDB’s compatibility with the existing schema and identify any necessary adjustments.\nSet up a single-node YugabyteDB instance for initial development and testing.\nMigrate existing data from the current database solution to YugabyteDB.\nUpdate the application code to work with YugabyteDB.\nPerform thorough testing to ensure stability and performance meet expectations.\n\n\n\n\n\nSingle-node setup with the potential for growth\nCompatibility with the existing schema\nSupport for a wide range of data types\nExternally consistent transaction levels\n\n\n\n\n\nPotential new problems and challenges associated with adopting a new database solution\nPossible learning curve for the team in working with YugabyteDB\nCannot do online primary key upgrades.\n\n\n\n\n\nPostgreSQL: While a popular and powerful database solution, it may not offer the desired single-node setup with growth potential.\nCockroachDB: The current implementation has been problematic due to its 3-node distributed configuration in Kubernetes.\nSQLite on FoundationDB: Limited data types and compatibility issues with the existing schema make this option less desirable.\n\n\n\n\nNo, the choice of database solution is a core aspect of the project and cannot be easily worked around with a script.\n\n\n\nYes, selecting the appropriate database solution is crucial for the success and stability of V-Sekai. It directly impacts the performance, scalability, and maintainability of the platform.\n\n\n\n\nV-Sekai\nYugabyteDB Data Types\nCockroach Labs\nMVSQLite: Distributed MVCC SQLite that runs on FoundationDB\nPostgreSQL"
+    "text": "It is hard to deploy URO."
   },
   {
-    "objectID": "decisions/20230619-move-cockroachdb-to-yugabyte.html#metadata",
-    "href": "decisions/20230619-move-cockroachdb-to-yugabyte.html#metadata",
-    "title": "Rejected: V-Sekai Database Solution for 50,000 Concurrent Online Users",
+    "objectID": "decisions/20220131-elixir-desktop-uro.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20220131-elixir-desktop-uro.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: Make a desktop version of Uro for ease of development.",
     "section": "",
-    "text": "Status: rejected\nDeciders: V-Sekai, fire\nTags: V-Sekai, llm summarization"
+    "text": "Deploy URO using Elixir Desktop."
   },
   {
-    "objectID": "decisions/20230619-move-cockroachdb-to-yugabyte.html#context-and-problem-statement",
-    "href": "decisions/20230619-move-cockroachdb-to-yugabyte.html#context-and-problem-statement",
-    "title": "Rejected: V-Sekai Database Solution for 50,000 Concurrent Online Users",
+    "objectID": "decisions/20220131-elixir-desktop-uro.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20220131-elixir-desktop-uro.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Make a desktop version of Uro for ease of development.",
     "section": "",
-    "text": "V-Sekai is currently facing a decision on which database solution to use for their project that can handle the load of 50,000 concurrent online users. The options being considered are PostgreSQL, CockroachDB, SQLite on FoundationDB, or YugabyteDB. Each option has its own set of advantages and disadvantages, and the team needs to determine which one best fits their requirements."
+    "text": "Build of Elixir Desktop\nValidate both Windows and Linux builds.\nFocus on Linux first."
   },
   {
-    "objectID": "decisions/20230619-move-cockroachdb-to-yugabyte.html#proposed-solution",
-    "href": "decisions/20230619-move-cockroachdb-to-yugabyte.html#proposed-solution",
-    "title": "Rejected: V-Sekai Database Solution for 50,000 Concurrent Online Users",
+    "objectID": "decisions/20220131-elixir-desktop-uro.html#positive-consequences",
+    "href": "decisions/20220131-elixir-desktop-uro.html#positive-consequences",
+    "title": "Proposed: Make a desktop version of Uro for ease of development.",
     "section": "",
-    "text": "Based on the discussion, it seems that YugabyteDB might be a suitable choice for V-Sekai’s needs. It offers a single-node setup with the potential for growth, supports a wide range of data types, and provides externally consistent transaction levels. Additionally, YugabyteDB appears to be more compatible with the existing schema compared to SQLite."
+    "text": "Able to deploy Uro easier."
   },
   {
-    "objectID": "decisions/20230619-move-cockroachdb-to-yugabyte.html#implementation",
-    "href": "decisions/20230619-move-cockroachdb-to-yugabyte.html#implementation",
-    "title": "Rejected: V-Sekai Database Solution for 50,000 Concurrent Online Users",
+    "objectID": "decisions/20220131-elixir-desktop-uro.html#negative-consequences",
+    "href": "decisions/20220131-elixir-desktop-uro.html#negative-consequences",
+    "title": "Proposed: Make a desktop version of Uro for ease of development.",
     "section": "",
-    "text": "To implement YugabyteDB as the chosen database solution, the following steps should be taken:\n\nEvaluate YugabyteDB’s compatibility with the existing schema and identify any necessary adjustments.\nSet up a single-node YugabyteDB instance for initial development and testing.\nMigrate existing data from the current database solution to YugabyteDB.\nUpdate the application code to work with YugabyteDB.\nPerform thorough testing to ensure stability and performance meet expectations."
+    "text": "Is this the most important thing to do with limited resources?"
   },
   {
-    "objectID": "decisions/20230619-move-cockroachdb-to-yugabyte.html#positive-consequences",
-    "href": "decisions/20230619-move-cockroachdb-to-yugabyte.html#positive-consequences",
-    "title": "Rejected: V-Sekai Database Solution for 50,000 Concurrent Online Users",
+    "objectID": "decisions/20220131-elixir-desktop-uro.html#option-graveyard",
+    "href": "decisions/20220131-elixir-desktop-uro.html#option-graveyard",
+    "title": "Proposed: Make a desktop version of Uro for ease of development.",
     "section": "",
-    "text": "Single-node setup with the potential for growth\nCompatibility with the existing schema\nSupport for a wide range of data types\nExternally consistent transaction levels"
+    "text": "Option: Current status.\nRejection Reason: Don’t have a platform for developing the backend."
   },
   {
-    "objectID": "decisions/20230619-move-cockroachdb-to-yugabyte.html#negative-consequences",
-    "href": "decisions/20230619-move-cockroachdb-to-yugabyte.html#negative-consequences",
-    "title": "Rejected: V-Sekai Database Solution for 50,000 Concurrent Online Users",
+    "objectID": "decisions/20220131-elixir-desktop-uro.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20220131-elixir-desktop-uro.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Make a desktop version of Uro for ease of development.",
     "section": "",
-    "text": "Potential new problems and challenges associated with adopting a new database solution\nPossible learning curve for the team in working with YugabyteDB\nCannot do online primary key upgrades."
+    "text": "Not a few lines of code."
   },
   {
-    "objectID": "decisions/20230619-move-cockroachdb-to-yugabyte.html#option-graveyard",
-    "href": "decisions/20230619-move-cockroachdb-to-yugabyte.html#option-graveyard",
-    "title": "Rejected: V-Sekai Database Solution for 50,000 Concurrent Online Users",
+    "objectID": "decisions/20220131-elixir-desktop-uro.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20220131-elixir-desktop-uro.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Make a desktop version of Uro for ease of development.",
     "section": "",
-    "text": "PostgreSQL: While a popular and powerful database solution, it may not offer the desired single-node setup with growth potential.\nCockroachDB: The current implementation has been problematic due to its 3-node distributed configuration in Kubernetes.\nSQLite on FoundationDB: Limited data types and compatibility issues with the existing schema make this option less desirable."
+    "text": "We are the maintainers of uro."
   },
   {
-    "objectID": "decisions/20230619-move-cockroachdb-to-yugabyte.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230619-move-cockroachdb-to-yugabyte.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Rejected: V-Sekai Database Solution for 50,000 Concurrent Online Users",
+    "objectID": "decisions/20220131-elixir-desktop-uro.html#references",
+    "href": "decisions/20220131-elixir-desktop-uro.html#references",
+    "title": "Proposed: Make a desktop version of Uro for ease of development.",
     "section": "",
-    "text": "No, the choice of database solution is a core aspect of the project and cannot be easily worked around with a script."
+    "text": "https://github.com/elixir-desktop/desktop\nhttps://github.com/V-Sekai/uro"
   },
   {
-    "objectID": "decisions/20230619-move-cockroachdb-to-yugabyte.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230619-move-cockroachdb-to-yugabyte.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Rejected: V-Sekai Database Solution for 50,000 Concurrent Online Users",
+    "objectID": "decisions/20220131-elixir-desktop-uro.html#derivative-license",
+    "href": "decisions/20220131-elixir-desktop-uro.html#derivative-license",
+    "title": "Proposed: Make a desktop version of Uro for ease of development.",
     "section": "",
-    "text": "Yes, selecting the appropriate database solution is crucial for the success and stability of V-Sekai. It directly impacts the performance, scalability, and maintainability of the platform."
+    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230619-move-cockroachdb-to-yugabyte.html#references",
-    "href": "decisions/20230619-move-cockroachdb-to-yugabyte.html#references",
-    "title": "Rejected: V-Sekai Database Solution for 50,000 Concurrent Online Users",
+    "objectID": "decisions/20240416-previewer-upload-gltf-to-glb.html",
+    "href": "decisions/20240416-previewer-upload-gltf-to-glb.html",
+    "title": "Proposed: Implementing a 3D Previewer for GLTF with XMP Metadata",
     "section": "",
-    "text": "V-Sekai\nYugabyteDB Data Types\nCockroach Labs\nMVSQLite: Distributed MVCC SQLite that runs on FoundationDB\nPostgreSQL"
+    "text": "The current project involves the use of 3D models in GLTF format. These models also contain XMP metadata which needs to be previewed.\n\n\n\nThe challenge lies in creating a 3D previewer that handles GLTF files and their associated XMP metadata. The aim is to have one file per entry, making it easier to manage and organize the data.\n\n\n\nThe proposed solution involves loading a GLTF file and saving it as a GLB file. This process is lossless, meaning no data will be lost during the conversion. The GLB file will then preview the 3D model and its metadata.\nfunction convertToGLB(gltfFile) {\n    // Load the GLTF file\n    var gltf = loadGLTF(gltfFile);\n\n    // Convert the GLTF to GLB\n    var glb = gltf.toGLB();\n\n    // Save the GLB file\n    saveGLB(glb);\n}\n\n\n\n\nSimplifies the workflow by having only one file per entry.\nNo loss of data during the conversion from GLTF to GLB.\nMakes it easier to compress in Godot Engine’s workflow.\n\n\n\n\n\nRequires additional processing to convert GLTF files to GLB.\nMight increase the overall size of the project due to the conversion.\n\n\n\n\nAn alternative approach could be to keep the GLTF and XMP metadata separate and create a previewer that can handle multiple files. However, this would complicate the workflow and make it harder to manage the data.\n\n\n\nThis proposal might not be beneficial for projects that do not require a 3D previewer or do not use GLTF files.\n\n\n\nThe implementation of this proposal will be done by the V-Sekai development team.\n\n\n\nProposed\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis proposal was assisted by AI assistant Aria."
   },
   {
-    "objectID": "decisions/20230123-recording-demo-checklist.html",
-    "href": "decisions/20230123-recording-demo-checklist.html",
-    "title": "Proposed: Recording demo checklist",
+    "objectID": "decisions/20240416-previewer-upload-gltf-to-glb.html#context",
+    "href": "decisions/20240416-previewer-upload-gltf-to-glb.html#context",
+    "title": "Proposed: Implementing a 3D Previewer for GLTF with XMP Metadata",
     "section": "",
-    "text": "Proposed: Recording demo checklist\n\nContext and Problem Statement\nHave a checklist of tasks needed for recording demos.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nI want to have consistency for the videos I record.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\n\nDo I have a keyboard to screen displayer?\nDoes the video have a V-Sekai logo?\nDoes the video have a work in progress disclaimer?\nDo I have a time code bar with V-Sekai Game prefix and a timezone suffix? https://obsproject.com/forum/resources/rtc-timecode-generator.1301/\nIs it under 4 megabytes?\n\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nOption graveyard\nNo response\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nThis is a script for filming.\n\n\nIs there a reason why this should be core and done by us?\nWanted to write down my preferences.\n\n\nReferences\n\nV-Sekai\n\n\n\nLicense of the contribution\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "The current project involves the use of 3D models in GLTF format. These models also contain XMP metadata which needs to be previewed."
   },
   {
-    "objectID": "decisions/20210710-verify-pr-workflow.html",
-    "href": "decisions/20210710-verify-pr-workflow.html",
-    "title": "Proposed: Describe a Godot Engine pr verification workflow",
+    "objectID": "decisions/20240416-previewer-upload-gltf-to-glb.html#problem-statement",
+    "href": "decisions/20240416-previewer-upload-gltf-to-glb.html#problem-statement",
+    "title": "Proposed: Implementing a 3D Previewer for GLTF with XMP Metadata",
     "section": "",
-    "text": "Proposed: Describe a Godot Engine pr verification workflow\n\nContext and Problem Statement\nA Godot Engine pr needs to be verified for correctness and style.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nThis workflows describes how fire checks pull requests.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n\nStart Windows 10.\nInstall scoop\nscoop install visual-studio-code llvm-mingw\nInstall python and scons\ngit checkout https://github.com/V-Sekai/v-sekai-pr-template --recurse-submodules\nOpen repository in Visual Studio Code.\nSwitch godot engine branch\nPress launch in Visual Studio Code\nVerify fixes.\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nThis is a workflow.\n\n\nPositive Consequences\nMore robust techniques for doing prs.\n\n\nNegative Consequences\nPaperwork and complexity.\n\n\nIs there a reason why this should be core and done by us?\nThis is a core procedure.\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "The challenge lies in creating a 3D previewer that handles GLTF files and their associated XMP metadata. The aim is to have one file per entry, making it easier to manage and organize the data."
   },
   {
-    "objectID": "decisions/20230618-v-sekai-roadmap.html",
-    "href": "decisions/20230618-v-sekai-roadmap.html",
-    "title": "Accepted: V-Sekai Roadmap and Goals 2023-06-18",
+    "objectID": "decisions/20240416-previewer-upload-gltf-to-glb.html#proposed-solution",
+    "href": "decisions/20240416-previewer-upload-gltf-to-glb.html#proposed-solution",
+    "title": "Proposed: Implementing a 3D Previewer for GLTF with XMP Metadata",
     "section": "",
-    "text": "Accepted: V-Sekai Roadmap and Goals 2023-06-18\n\nMetadata\n\nStatus: superseded\nDeciders: V-Sekai, fire, guillefix\nTags: V-Sekai, chatgpt4 summary,\n\n\n\nContext and Problem Statement\nWhat is the V-Sekai Roadmap and Goals?\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nThe roadmap presented here is short-term.\n\n\nDescribe how your proposal will work with code, pseudo-code, mock-ups, or diagrams\nBy avoiding work on User Generated Content (UGC) and world building, we can prioritize the three main states in the roadmap: “World / Avatar Performance” (WAP), “Networking” (NET), and “UI/UX”. This allows the team to focus on the core aspects of V-Sekai and achieve the goals more efficiently.\n\n\nGoals\n\nWorld / Avatar Performance (WAP)\n\nTimeline: Q2-Q3\nImplement light assets and asynchronous loading to reduce load time by 30%\nUtilize modern rendering techniques and high-performance libraries to achieve 60 FPS on mid-range devices\nApply network optimization and low latency protocols for better performance, reducing latency by 50%\n\n\n\nNetworking (NET)\n\nTimeline: Q2-Q3\nUse efficient data formats and optimized compression algorithms to reduce file size by 40%\nEnsure accurate IK points are respected, achieving 95% accuracy\nExplore multiple technologies and alternative solutions for continuous improvement, evaluating 3 new technologies per quarter\n\n\n\nFirst Time User Experience (FTUX)\n\nTimeline: Q3-Q4\nOptimize first-time user experience by improving the loading process, increasing user retention by 20%\n\n\n\nDiagram\nsequenceDiagram\n    participant V-Sekai\n    participant Player\n    participant Creator\n    participant Lyuma as \"Lyuma (VRM1 - WAP)\"\n\n    Note over Lyuma: WAP: World / Avatar Performance\n    Note over Lyuma: Timeline: Q2-Q3\n\n    Creator-&gt;&gt;V-Sekai: Implement light assets and asynchronous loading (reduce load time by 30%)\n    V-Sekai-&gt;&gt;Player: Utilize modern rendering techniques and high-performance libraries (achieve 60 FPS on mid-range devices)\n    Player-&gt;&gt;Creator: Apply network optimization and low latency protocols for better performance (reduce latency by 50%)\n\n    Note over Player, Creator: NET: Network Optimization Techniques\n    Note over Player, Creator: Timeline: Q2-Q3\n\n    Creator-&gt;&gt;V-Sekai: Use efficient data formats and optimized compression algorithms (reduce file size by 40%)\n    V-Sekai-&gt;&gt;Player: Ensure accurate IK points are respected (achieve 95% accuracy)\n    V-Sekai-&gt;&gt;Player: Explore multiple technologies and alternative solutions for continuous improvement (evaluate 3 new technologies per quarter)\n\n    %% Metrics\n    Note over Player, Creator: Metrics:\n    Player-&gt;&gt;Player: File size reduction\n    Player-&gt;&gt;Player: IK accuracy\n    Player-&gt;&gt;Player: Technologies evaluated\n\nsequenceDiagram\n    participant Fire\n    participant Creator\n\n    Fire-&gt;&gt;Creator: Optimize first-time user experience by improving the loading process (increase user retention by 20%)\n\n    Note over Fire, Creator: FTUX: First Time User Experience\n    Note over Fire, Creator: Timeline: Q3-Q4\n\n    %% Metrics\n    Note over Fire, Creator: Metrics:\n    Fire-&gt;&gt;Fire: Load time reduction\n    Fire-&gt;&gt;Fire: Frame rate (FPS) for flat desktop\n    Fire-&gt;&gt;Fire: Frame rate (FPS) for VR desktop\n    Fire-&gt;&gt;Fire: Latency reduction\n    Fire-&gt;&gt;Fire: User retention rate\n\n\n\nPositive Consequences\n\nEasier creation of V-Sekai.\nFocused development on core aspects.\n\n\n\nNegative Consequences\n\nPotential overhead challenges.\n\n\n\nOption graveyard\n\nWaiting for Godot Engine 4.2 instead of assisting with 4.1 features.\n\n\n\nIf this enhancement will be used infrequently, can it be worked around with a few lines of script?\nNo. This is a process.\n\n\nIs there a reason why this should be core and done by us?\nThis is a core process for V-Sekai.\n\n\nReferences\n\nV-Sekai"
+    "text": "The proposed solution involves loading a GLTF file and saving it as a GLB file. This process is lossless, meaning no data will be lost during the conversion. The GLB file will then preview the 3D model and its metadata.\nfunction convertToGLB(gltfFile) {\n    // Load the GLTF file\n    var gltf = loadGLTF(gltfFile);\n\n    // Convert the GLTF to GLB\n    var glb = gltf.toGLB();\n\n    // Save the GLB file\n    saveGLB(glb);\n}"
   },
   {
-    "objectID": "decisions/20230624-v-sekai-roadmap.html",
-    "href": "decisions/20230624-v-sekai-roadmap.html",
-    "title": "Accepted: V-Sekai Roadmap and Goals 2023-06-24",
+    "objectID": "decisions/20240416-previewer-upload-gltf-to-glb.html#benefits",
+    "href": "decisions/20240416-previewer-upload-gltf-to-glb.html#benefits",
+    "title": "Proposed: Implementing a 3D Previewer for GLTF with XMP Metadata",
     "section": "",
-    "text": "Accepted: V-Sekai Roadmap and Goals 2023-06-24\n\nMetadata\n\nStatus: accepted\nDeciders: V-Sekai, fire\nTags: V-Sekai, chatgpt4 summary,\n\n\n\nContext and Problem Statement\nWhat is the V-Sekai Roadmap and Goals?\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nThe roadmap presented here is short-term.\n\n\nDescribe how your proposal will work with code, pseudo-code, mock-ups, or diagrams\nBy avoiding work on User Generated Content (UGC) and world building, we can prioritize the three main states in the roadmap: “World / Avatar Performance” (WAP), “Networking” (NET), and “UI/UX”. This allows the team to focus on the core aspects of V-Sekai and achieve the goals more efficiently.\n\nMonitoring and Logging System Test:\n\nSetup logging framework\nConfigure monitoring system\nCreate a dashboard\n\nTest Environment with Simulated Data Test:\n\nCreate test scenarios\nGenerate simulated data\nConfigure test environment\nExecute test scenarios\nAnalyze test results\n\n\n\n\nPositive Consequences\n\nEasier creation of V-Sekai.\nFocused development on core aspects.\n\n\n\nNegative Consequences\n\nPotential overhead challenges.\n\n\n\nOption graveyard\n\nWaiting for Godot Engine 4.2 instead of assisting with 4.1 features.\n\n\n\nIf this enhancement will be used infrequently, can it be worked around with a few lines of script?\nNo. This is a process.\n\n\nIs there a reason why this should be core and done by us?\nThis is a core process for V-Sekai.\n\n\nReferences\n\nV-Sekai"
+    "text": "Simplifies the workflow by having only one file per entry.\nNo loss of data during the conversion from GLTF to GLB.\nMakes it easier to compress in Godot Engine’s workflow."
   },
   {
-    "objectID": "decisions/20211031-tire-model-car-sim.html",
-    "href": "decisions/20211031-tire-model-car-sim.html",
-    "title": "Proposed: Tire model car sim",
+    "objectID": "decisions/20240416-previewer-upload-gltf-to-glb.html#downsides",
+    "href": "decisions/20240416-previewer-upload-gltf-to-glb.html#downsides",
+    "title": "Proposed: Implementing a 3D Previewer for GLTF with XMP Metadata",
     "section": "",
-    "text": "Proposed: Tire model car sim\n\nContext and Problem Statement\nCreate a vehicle simulation\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nUse physx’s tire simulation. While citing their mit license.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nUse math model.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nOne does not simply make a vehicle sim.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nMaybe out of scope? But I have an approach.\n\n\nReferences\n\n\nTire Modeling #########################################\nThe default tire model employed by PhysX vehicles is discussed in Appendix H of the CarSimEd documentation:\nhttp://www.eggert.highpeakpress.com/ME485/Docs/CarSimEd.pdf\nPhysX vehicles allow any tire model to be simulated by specifying a tire shader, as discussed in :ref:Tire Shaders. A tire model commonly used in engineering simulation is the Pacejka tire model:\nhttp://phors.locost7.info/phors21.htm\n\nhttp://phors.locost7.info/phors22.htm\n\n\nhttps://github.com/NVIDIAGameWorks/PhysX/blob/ae80dede0546d652040ae6260a810e53e20a06fa/physx/documentation/PhysXGuide/_sources/Manual/Vehicles.txt#L2058\nhttps://web.archive.org/web/20180712141747/http://www.eggert.highpeakpress.com/ME485/Docs/CarSimEd.pdf\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Requires additional processing to convert GLTF files to GLB.\nMight increase the overall size of the project due to the conversion."
   },
   {
-    "objectID": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html",
-    "href": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html",
-    "title": "Proposed: Enhancing Avatar Expressiveness with AI-Generated Blend Shapes",
+    "objectID": "decisions/20240416-previewer-upload-gltf-to-glb.html#the-road-not-taken",
+    "href": "decisions/20240416-previewer-upload-gltf-to-glb.html#the-road-not-taken",
+    "title": "Proposed: Implementing a 3D Previewer for GLTF with XMP Metadata",
     "section": "",
-    "text": "In the realm of virtual reality, expressiveness is paramount for a rich social experience. V-Sekai is dedicated to providing users with robust avatar customization options, particularly in the realm of facial expressions.\n\n\n\nThe current scope of facial expression customization in V-Sekai is limited. It lacks the depth necessary for users to craft avatars that can exhibit a comprehensive range of emotions, which detracts from the immersive experience and social interaction within the platform.\n\n\n\nTo be determined.\n\n\n\n\nEnhanced realism and emotional conveyance in avatars.\nGreater diversity in facial expressions enriches communication between users.\nSimplification of complex expression creation makes avatar personalization accessible to all skill levels.\n\n\n\n\n\nPotential performance impact due to real-time AI processing.\nThe requirement for ongoing dataset updates to improve and maintain AI model accuracy.\n\n\n\n\nAlternative options included manual blend shape sculpting by artists and community-driven expression templates, both of which were deemed to lack scalability and flexibility compared to an AI-based solution.\n\n\n\nFor users requiring highly specialized expressions seldom encountered in regular interactions, such as niche cultural facial gestures.\n\n\n\nThis initiative is core to V-Sekai’s mission of enhanced user interaction and must be developed in-house to ensure deep integration and alignment with existing systems.\n\n\n\nStatus: Proposed\n\n\n\n\n\nV-Sekai development team and community stakeholders.\n\n\n\n\n\nV-Sekai, Avatar Customization, AI, Facial Expressions\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nAssisted by Aria."
+    "text": "An alternative approach could be to keep the GLTF and XMP metadata separate and create a previewer that can handle multiple files. However, this would complicate the workflow and make it harder to manage the data."
   },
   {
-    "objectID": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#the-context",
-    "href": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#the-context",
-    "title": "Proposed: Enhancing Avatar Expressiveness with AI-Generated Blend Shapes",
+    "objectID": "decisions/20240416-previewer-upload-gltf-to-glb.html#the-infrequent-use-case",
+    "href": "decisions/20240416-previewer-upload-gltf-to-glb.html#the-infrequent-use-case",
+    "title": "Proposed: Implementing a 3D Previewer for GLTF with XMP Metadata",
     "section": "",
-    "text": "In the realm of virtual reality, expressiveness is paramount for a rich social experience. V-Sekai is dedicated to providing users with robust avatar customization options, particularly in the realm of facial expressions."
+    "text": "This proposal might not be beneficial for projects that do not require a 3D previewer or do not use GLTF files."
   },
   {
-    "objectID": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#the-problem-statement",
-    "href": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#the-problem-statement",
-    "title": "Proposed: Enhancing Avatar Expressiveness with AI-Generated Blend Shapes",
+    "objectID": "decisions/20240416-previewer-upload-gltf-to-glb.html#in-core-and-done-by-us",
+    "href": "decisions/20240416-previewer-upload-gltf-to-glb.html#in-core-and-done-by-us",
+    "title": "Proposed: Implementing a 3D Previewer for GLTF with XMP Metadata",
     "section": "",
-    "text": "The current scope of facial expression customization in V-Sekai is limited. It lacks the depth necessary for users to craft avatars that can exhibit a comprehensive range of emotions, which detracts from the immersive experience and social interaction within the platform."
+    "text": "The implementation of this proposal will be done by the V-Sekai development team."
   },
   {
-    "objectID": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Enhancing Avatar Expressiveness with AI-Generated Blend Shapes",
+    "objectID": "decisions/20240416-previewer-upload-gltf-to-glb.html#status",
+    "href": "decisions/20240416-previewer-upload-gltf-to-glb.html#status",
+    "title": "Proposed: Implementing a 3D Previewer for GLTF with XMP Metadata",
     "section": "",
-    "text": "To be determined."
+    "text": "Proposed"
   },
   {
-    "objectID": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#the-benefits",
-    "href": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#the-benefits",
-    "title": "Proposed: Enhancing Avatar Expressiveness with AI-Generated Blend Shapes",
+    "objectID": "decisions/20240416-previewer-upload-gltf-to-glb.html#decision-makers",
+    "href": "decisions/20240416-previewer-upload-gltf-to-glb.html#decision-makers",
+    "title": "Proposed: Implementing a 3D Previewer for GLTF with XMP Metadata",
     "section": "",
-    "text": "Enhanced realism and emotional conveyance in avatars.\nGreater diversity in facial expressions enriches communication between users.\nSimplification of complex expression creation makes avatar personalization accessible to all skill levels."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#the-downsides",
-    "href": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#the-downsides",
-    "title": "Proposed: Enhancing Avatar Expressiveness with AI-Generated Blend Shapes",
+    "objectID": "decisions/20240416-previewer-upload-gltf-to-glb.html#tags",
+    "href": "decisions/20240416-previewer-upload-gltf-to-glb.html#tags",
+    "title": "Proposed: Implementing a 3D Previewer for GLTF with XMP Metadata",
     "section": "",
-    "text": "Potential performance impact due to real-time AI processing.\nThe requirement for ongoing dataset updates to improve and maintain AI model accuracy."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#the-road-not-taken",
-    "href": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#the-road-not-taken",
-    "title": "Proposed: Enhancing Avatar Expressiveness with AI-Generated Blend Shapes",
+    "objectID": "decisions/20240416-previewer-upload-gltf-to-glb.html#further-reading",
+    "href": "decisions/20240416-previewer-upload-gltf-to-glb.html#further-reading",
+    "title": "Proposed: Implementing a 3D Previewer for GLTF with XMP Metadata",
     "section": "",
-    "text": "Alternative options included manual blend shape sculpting by artists and community-driven expression templates, both of which were deemed to lack scalability and flexibility compared to an AI-based solution."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis proposal was assisted by AI assistant Aria."
   },
   {
-    "objectID": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#the-infrequent-use-case",
-    "href": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#the-infrequent-use-case",
-    "title": "Proposed: Enhancing Avatar Expressiveness with AI-Generated Blend Shapes",
+    "objectID": "decisions/20211031-use-bpr-to-rank-skeleton-bone-names.html",
+    "href": "decisions/20211031-use-bpr-to-rank-skeleton-bone-names.html",
+    "title": "Proposed: Rank skeleton bone names by using BPR",
     "section": "",
-    "text": "For users requiring highly specialized expressions seldom encountered in regular interactions, such as niche cultural facial gestures."
+    "text": "Proposed: Rank skeleton bone names by using BPR\n\nStatus: proposed\n\n\nContext and Problem Statement\nImprove automatic bone selection\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nUse brp to rank bones while storing in duckdb.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nUse duckdb and brp. Prototype concept then port to c++.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nTrying.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nI have the idea.\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#in-core-and-done-by-us",
-    "href": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#in-core-and-done-by-us",
-    "title": "Proposed: Enhancing Avatar Expressiveness with AI-Generated Blend Shapes",
+    "objectID": "decisions/20230920-godot-project-search.html",
+    "href": "decisions/20230920-godot-project-search.html",
+    "title": "Proposed: Use embedding search with Godot Engine projects",
     "section": "",
-    "text": "This initiative is core to V-Sekai’s mission of enhanced user interaction and must be developed in-house to ensure deep integration and alignment with existing systems."
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nThe Godot Engine is a powerful tool for creating games and other interactive content. However, finding specific pieces of code or resources within a large project can be challenging. This is where an embedding search engine like SeaGOAT can come in handy.\n\n\n\nThe challenge lies in integrating the SeaGOAT search engine with Godot Engine projects. Specifically, we need to ensure that it can effectively index and search .tscn, .tres, .gd, .cpp, .h, and .xml files, which are commonly used in Godot projects.\n\n\n\nTo use SeaGOAT with Godot Engine projects, you’ll need to add support for .tscn, .tres, .gd, .cpp, .h, and .xml files. You can do this by modifying the common.py file in the SeaGOAT repository. Specifically, you’ll want to add these extensions to the FILE_EXTENSIONS list:\nFILE_EXTENSIONS = [\n    # existing extensions...\n    \".tscn\",\n    \".tres\",\n    \".gd\",\n    \".cpp\",\n    \".h\",\n    \".xml\"\n]\nOnce you’ve done this, SeaGOAT should be able to index and search your Godot Engine projects.\n\n\n\nBy integrating SeaGOAT with your Godot Engine projects, you’ll be able to quickly and easily find specific pieces of code or resources. This can greatly speed up your development process and make it easier to manage large projects.\n\n\n\nThe downside is that this requires modifying the SeaGOAT source code, which may not be ideal if you’re not comfortable with Python or if you want to keep your SeaGOAT installation up-to-date with the official repository.\n\n\n\nAn alternative approach would be to use a different search engine that already supports .tscn, .tres, .gd, .cpp, .h, and .xml files. However, this may not provide the same level of functionality as SeaGOAT.\n\n\n\nThis strategy is most useful for large Godot Engine projects where finding specific pieces of code or resources can be challenging. For smaller projects, the built-in search functionality in Godot may be sufficient.\n\n\n\nThis modification would need to be done by us, as it involves changing the SeaGOAT source code. It’s not clear whether this change would be accepted into the core SeaGOAT project.\n\n\n\n\nV-Sekai\nSeaGOAT\nThis article is assisted by AI."
   },
   {
-    "objectID": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#status",
-    "href": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#status",
-    "title": "Proposed: Enhancing Avatar Expressiveness with AI-Generated Blend Shapes",
+    "objectID": "decisions/20230920-godot-project-search.html#metadata",
+    "href": "decisions/20230920-godot-project-search.html#metadata",
+    "title": "Proposed: Use embedding search with Godot Engine projects",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#decision-makers",
-    "href": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#decision-makers",
-    "title": "Proposed: Enhancing Avatar Expressiveness with AI-Generated Blend Shapes",
+    "objectID": "decisions/20230920-godot-project-search.html#the-backdrop",
+    "href": "decisions/20230920-godot-project-search.html#the-backdrop",
+    "title": "Proposed: Use embedding search with Godot Engine projects",
     "section": "",
-    "text": "V-Sekai development team and community stakeholders."
+    "text": "The Godot Engine is a powerful tool for creating games and other interactive content. However, finding specific pieces of code or resources within a large project can be challenging. This is where an embedding search engine like SeaGOAT can come in handy."
   },
   {
-    "objectID": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#tags",
-    "href": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#tags",
-    "title": "Proposed: Enhancing Avatar Expressiveness with AI-Generated Blend Shapes",
+    "objectID": "decisions/20230920-godot-project-search.html#the-challenge",
+    "href": "decisions/20230920-godot-project-search.html#the-challenge",
+    "title": "Proposed: Use embedding search with Godot Engine projects",
     "section": "",
-    "text": "V-Sekai, Avatar Customization, AI, Facial Expressions"
+    "text": "The challenge lies in integrating the SeaGOAT search engine with Godot Engine projects. Specifically, we need to ensure that it can effectively index and search .tscn, .tres, .gd, .cpp, .h, and .xml files, which are commonly used in Godot projects."
   },
   {
-    "objectID": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#further-reading",
-    "href": "decisions/20240215-avatar-customization-with-ai-facial-expressions.html#further-reading",
-    "title": "Proposed: Enhancing Avatar Expressiveness with AI-Generated Blend Shapes",
+    "objectID": "decisions/20230920-godot-project-search.html#the-strategy",
+    "href": "decisions/20230920-godot-project-search.html#the-strategy",
+    "title": "Proposed: Use embedding search with Godot Engine projects",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nAssisted by Aria."
+    "text": "To use SeaGOAT with Godot Engine projects, you’ll need to add support for .tscn, .tres, .gd, .cpp, .h, and .xml files. You can do this by modifying the common.py file in the SeaGOAT repository. Specifically, you’ll want to add these extensions to the FILE_EXTENSIONS list:\nFILE_EXTENSIONS = [\n    # existing extensions...\n    \".tscn\",\n    \".tres\",\n    \".gd\",\n    \".cpp\",\n    \".h\",\n    \".xml\"\n]\nOnce you’ve done this, SeaGOAT should be able to index and search your Godot Engine projects."
   },
   {
-    "objectID": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html",
-    "href": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html",
-    "title": "Proposed: Allow Godot Asset Library browser to use alternative sources",
+    "objectID": "decisions/20230920-godot-project-search.html#the-upside",
+    "href": "decisions/20230920-godot-project-search.html#the-upside",
+    "title": "Proposed: Use embedding search with Godot Engine projects",
     "section": "",
-    "text": "Status: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nGodot Engine has a great asset library browser.\nWhy can’t we reuse it for alternative Godot engine asset libraries?\n\n\n\nAdd an alternative server and document the current api as an openapi schema.\n\n\n\n\nOpenapi schema for the official asset library api.\nElixir server implementation\nPatch to Godot Engine to add arbitrary asset libraries\n\n\n\n\n\nMore freedom.\nXananax said he’ll use it. Xanax’s games are made 100% of addons with assets and glue code being the game.\n\n\n\n\n\nDifferent libraries\n\n\n\n\n\nOption: \nRejection Reason: \n\n\n\n\nCould be a few lines of script. Unsure of scope. The server can be a lot too.\n\n\n\nNot so core, but I can do it.\n\n\n\n\nhttps://github.com/godotengine/godot-asset-library/blob/master/API.md\n\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "By integrating SeaGOAT with your Godot Engine projects, you’ll be able to quickly and easily find specific pieces of code or resources. This can greatly speed up your development process and make it easier to manage large projects."
   },
   {
-    "objectID": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html#context-and-problem-statement",
-    "href": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html#context-and-problem-statement",
-    "title": "Proposed: Allow Godot Asset Library browser to use alternative sources",
+    "objectID": "decisions/20230920-godot-project-search.html#the-downside",
+    "href": "decisions/20230920-godot-project-search.html#the-downside",
+    "title": "Proposed: Use embedding search with Godot Engine projects",
     "section": "",
-    "text": "Godot Engine has a great asset library browser.\nWhy can’t we reuse it for alternative Godot engine asset libraries?"
+    "text": "The downside is that this requires modifying the SeaGOAT source code, which may not be ideal if you’re not comfortable with Python or if you want to keep your SeaGOAT installation up-to-date with the official repository."
   },
   {
-    "objectID": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: Allow Godot Asset Library browser to use alternative sources",
+    "objectID": "decisions/20230920-godot-project-search.html#the-road-not-taken",
+    "href": "decisions/20230920-godot-project-search.html#the-road-not-taken",
+    "title": "Proposed: Use embedding search with Godot Engine projects",
     "section": "",
-    "text": "Add an alternative server and document the current api as an openapi schema."
+    "text": "An alternative approach would be to use a different search engine that already supports .tscn, .tres, .gd, .cpp, .h, and .xml files. However, this may not provide the same level of functionality as SeaGOAT."
   },
   {
-    "objectID": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Allow Godot Asset Library browser to use alternative sources",
+    "objectID": "decisions/20230920-godot-project-search.html#the-infrequent-use-case",
+    "href": "decisions/20230920-godot-project-search.html#the-infrequent-use-case",
+    "title": "Proposed: Use embedding search with Godot Engine projects",
     "section": "",
-    "text": "Openapi schema for the official asset library api.\nElixir server implementation\nPatch to Godot Engine to add arbitrary asset libraries"
+    "text": "This strategy is most useful for large Godot Engine projects where finding specific pieces of code or resources can be challenging. For smaller projects, the built-in search functionality in Godot may be sufficient."
   },
   {
-    "objectID": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html#positive-consequences",
-    "href": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html#positive-consequences",
-    "title": "Proposed: Allow Godot Asset Library browser to use alternative sources",
+    "objectID": "decisions/20230920-godot-project-search.html#in-core-and-done-by-us",
+    "href": "decisions/20230920-godot-project-search.html#in-core-and-done-by-us",
+    "title": "Proposed: Use embedding search with Godot Engine projects",
     "section": "",
-    "text": "More freedom.\nXananax said he’ll use it. Xanax’s games are made 100% of addons with assets and glue code being the game."
+    "text": "This modification would need to be done by us, as it involves changing the SeaGOAT source code. It’s not clear whether this change would be accepted into the core SeaGOAT project."
   },
   {
-    "objectID": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html#negative-consequences",
-    "href": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html#negative-consequences",
-    "title": "Proposed: Allow Godot Asset Library browser to use alternative sources",
+    "objectID": "decisions/20230920-godot-project-search.html#further-reading",
+    "href": "decisions/20230920-godot-project-search.html#further-reading",
+    "title": "Proposed: Use embedding search with Godot Engine projects",
     "section": "",
-    "text": "Different libraries"
+    "text": "V-Sekai\nSeaGOAT\nThis article is assisted by AI."
   },
   {
-    "objectID": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html#option-graveyard",
-    "href": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html#option-graveyard",
-    "title": "Proposed: Allow Godot Asset Library browser to use alternative sources",
+    "objectID": "decisions/20230415-rgbaf-to-store-integers.html",
+    "href": "decisions/20230415-rgbaf-to-store-integers.html",
+    "title": "Proposed: Use godot rgbaf textures to store integers",
     "section": "",
-    "text": "Option: \nRejection Reason:"
+    "text": "Proposed: Use godot rgbaf textures to store integers\n\nMetadata\n\nStatus: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nContext and Problem Statement\nUse godot rgbaf textures to store integer.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nGodot Shader to extract the raw 16-bit integer in a FORMAT_RGBAH texture by Lyuma.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\n\nshader_type spatial;\nrender_mode unshaded;\nuniform usampler2D data_tex;\n\n/*\nUse with the following GDScript code:\n    var data_img = Image.new()\n    var data := PoolByteArray()\n    var indexin = 0x8400\n    data.append(indexin&0xff)\n    data.append((indexin&gt;&gt;8)&0xff)\n    data_img.create_from_data(1, 1, false, Image.FORMAT_RH, data)\n    var data_tex = ImageTexture.new()\n    data_tex.create_from_image(data_img, 0)\n    self.get_surface_material(0).set_shader_param(\"data_tex\", data_tex)\n*/\n\n// Extract the raw 16-bit integer assigned in a GL_RGBA16F or similar texture format\n// (in Godot, Image.FORMAT_RGBAH or Image.FORMAT_RH)\n\n// vectorized ?:\n// In GLSL, you are supposed to do this using a mix(uvec4, uvec4, bvec4)\n// However, in Godot, they forgot this overload existed, so we reimplement it.\n\nuvec4 godot_hack_mix(uvec4 a, uvec4 b, bvec4 c) {\n    return uvec4(c.x ? b.x : a.x, c.y ? b.y : a.y, c.z ? b.z : a.z, c.w ? b.w : a.w);\n}\n\nvoid fragment() {\n    // Fetch half precision texture using usampler2D.\n    // For some reason, it first converts to 32-bit float (but losslessly????)\n    // and so we have to convert the 32-bit float back to 16-bits.\n    uvec4 data = texelFetch(data_tex, ivec2(0,0), 0);\n\n    // Calculate bit shifted exponent\n    uvec4 exps = godot_hack_mix(\n        // Adjust floating point from 8-bit in float32 (127 bias) to 5-bit in half (15 bias)\n        uvec4((uvec4((ivec4((data & uvec4(0x7F800000)) &gt;&gt; uvec4(23)) - ivec4(127)) + ivec4(15)) & uvec4(0x1F)) &lt;&lt; uvec4(10)),\n        // Inf and NaN will remain Inf and Nan (maximum half exponent = 31)\n        uvec4(ivec4(31 &lt;&lt; 10)),\n        // Check for maximum float32 exponent = 255\n        equal((data) & uvec4(0x7F800000), uvec4(0x7F800000)));\n\n    // calculate final data.\n    data = godot_hack_mix(\n        // mantissa | exponent | signbit\n        ((data & uvec4(0x007FFFFF)) &gt;&gt; uvec4(13)) | exps | (((data &gt;&gt; uvec4(31)) & uvec4(1)) &lt;&lt; uvec4(15)),\n        // Denormalized case: exponent is all over the place, so instead we add the smallest non-denormalized half, then extract the mantessa bits.\n        // Finally, or the sign bit (and exponent = 0)\n        (((floatBitsToUint(uintBitsToFloat(data & uvec4(0x7FFFFFFF)) + 1.0/16384.0) & uvec4(0x007FFFFF)) &gt;&gt; uvec4(13))) | (((data &gt;&gt; uvec4(31)) & uvec4(1)) &lt;&lt; uvec4(15)),\n        // Denormalized case can be detected with half exponent &lt;= -15.\n        lessThanEqual((data) & uvec4(0x7F800000), uvec4(0x38000000)));\n\n    // Parse out individual bits if needed\n    ivec2 datar = ivec2((uvec2(data.r) &gt;&gt; uvec2(0,8)) & uvec2(0xFF));\n    ivec2 datag = ivec2((uvec2(data.g) &gt;&gt; uvec2(0,8)) & uvec2(0xFF));\n    ivec2 datab = ivec2((uvec2(data.b) &gt;&gt; uvec2(0,8)) & uvec2(0xFF));\n    ivec2 dataa = ivec2((uvec2(data.a) &gt;&gt; uvec2(0,8)) & uvec2(0xFF));\n\n    // Example code: check for precise 16-bit value that matches GDScript.\n    ALBEDO = vec3(0,0,0);\n    if (data.r == uint(0xFFFF)) {\n        ALBEDO = vec3(1,1,1);\n    }\n}\n\n\nPositive Consequences\nWe are able to use V-Sekai easier.\n\n\nNegative Consequences\nWe cannot get other features in.\n\n\nOption graveyard\nUse 8 bit colors.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nThis is a few lines of script.\n\n\nIs there a reason why this should be core and done by us?\nWanted to record this.\n\n\nReferences\n\nV-Sekai"
   },
   {
-    "objectID": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Allow Godot Asset Library browser to use alternative sources",
+    "objectID": "decisions/20240511-review-80-vr.html",
+    "href": "decisions/20240511-review-80-vr.html",
+    "title": "Rejected: VR Game with 80 Players and One World Server",
     "section": "",
-    "text": "Could be a few lines of script. Unsure of scope. The server can be a lot too."
+    "text": "We aim to create a virtual reality (VR) game that can support eighty players simultaneously using a single world server.\n\n\n\nThe challenge lies in managing the load of player simulations, world server, and game state delivery.\nWe update the state of PLAYER_COUNT vsync times on a TBD CPU bare metal machine.\nIt takes 30ms to update the database on the prototype on VSK_godot/modules/mvsqlite/demo returning the list of all changed states.\nWe are going with the grid approach. Our world is a 1km by 1km area and each grid cell is 100m squared.\nA 1x1 grid of 100m squared requires 1 server.\nOur database is SQLite FoundationDB.\nThe game state delivery process involves the world server generating a stream of data containing the states of all players. This data is then sent to the client-side for rendering and interaction.\nThis list can then be used to generate the TBD gigabit/sec stream of packets that is sent from the world server.\nPlease note that the limiting factor here is due to the lack of multicast support over the internet.\n\n\n\n\nSupports a moderate number of players simultaneously\nProvides a rich, immersive gaming experience\nSimplified infrastructure with only one world server\n\n\n\n\n\nRequires significant resources and infrastructure\nBandwidth requirements may be high for some players\nLack of multicast support over the internet could limit game state delivery\n\n\n\n\nAn alternative would be to increase the number of players or world servers, but this would require more resources and infrastructure.\n\n\n\nIn cases where player traffic is consistently low, the infrastructure may be underutilized.\n\n\n\nThe proposed stress testing will be conducted by the V-Sekai development team.\n\n\n\nStatus: Rejected \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\ncreating-a-first-person-shooter-that-scales-to-millions-of-players\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Allow Godot Asset Library browser to use alternative sources",
+    "objectID": "decisions/20240511-review-80-vr.html#the-context",
+    "href": "decisions/20240511-review-80-vr.html#the-context",
+    "title": "Rejected: VR Game with 80 Players and One World Server",
     "section": "",
-    "text": "Not so core, but I can do it."
+    "text": "We aim to create a virtual reality (VR) game that can support eighty players simultaneously using a single world server."
   },
   {
-    "objectID": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html#references",
-    "href": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html#references",
-    "title": "Proposed: Allow Godot Asset Library browser to use alternative sources",
+    "objectID": "decisions/20240511-review-80-vr.html#the-problem-statement",
+    "href": "decisions/20240511-review-80-vr.html#the-problem-statement",
+    "title": "Rejected: VR Game with 80 Players and One World Server",
     "section": "",
-    "text": "https://github.com/godotengine/godot-asset-library/blob/master/API.md"
+    "text": "The challenge lies in managing the load of player simulations, world server, and game state delivery.\nWe update the state of PLAYER_COUNT vsync times on a TBD CPU bare metal machine.\nIt takes 30ms to update the database on the prototype on VSK_godot/modules/mvsqlite/demo returning the list of all changed states.\nWe are going with the grid approach. Our world is a 1km by 1km area and each grid cell is 100m squared.\nA 1x1 grid of 100m squared requires 1 server.\nOur database is SQLite FoundationDB.\nThe game state delivery process involves the world server generating a stream of data containing the states of all players. This data is then sent to the client-side for rendering and interaction.\nThis list can then be used to generate the TBD gigabit/sec stream of packets that is sent from the world server.\nPlease note that the limiting factor here is due to the lack of multicast support over the internet."
   },
   {
-    "objectID": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html#derivative-license",
-    "href": "decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html#derivative-license",
-    "title": "Proposed: Allow Godot Asset Library browser to use alternative sources",
+    "objectID": "decisions/20240511-review-80-vr.html#the-benefits",
+    "href": "decisions/20240511-review-80-vr.html#the-benefits",
+    "title": "Rejected: VR Game with 80 Players and One World Server",
     "section": "",
-    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Supports a moderate number of players simultaneously\nProvides a rich, immersive gaming experience\nSimplified infrastructure with only one world server"
   },
   {
-    "objectID": "decisions/20230125-cover-80-95-percent-of-the-userbase.html",
-    "href": "decisions/20230125-cover-80-95-percent-of-the-userbase.html",
-    "title": "Proposed: Cover 80% to 95% of the player base.",
+    "objectID": "decisions/20240511-review-80-vr.html#the-downsides",
+    "href": "decisions/20240511-review-80-vr.html#the-downsides",
+    "title": "Rejected: VR Game with 80 Players and One World Server",
     "section": "",
-    "text": "Proposed: Cover 80% to 95% of the player base.\n\nMetadata\n\nStatus: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nContext and Problem Statement\nPeople want to use V-Sekai, we need to provide coverage of their electronic equipment.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nCover 80% to 95% percent of the userbase’s equipment, so people can play V-Sekai.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nProvide coverage of:\n\nDesktop mode\nMeta Quest 2\nValve Index\nHTC Vive\n\n\n\nPositive Consequences\nWe are able to use V-Sekai easier.\n\n\nNegative Consequences\nWe cannot get other features in.\n\n\nOption graveyard\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nKnowing what to do is hard.\n\n\nIs there a reason why this should be core and done by us?\nUsability is a core feature.\n\n\nReferences\n\nV-Sekai"
+    "text": "Requires significant resources and infrastructure\nBandwidth requirements may be high for some players\nLack of multicast support over the internet could limit game state delivery"
   },
   {
-    "objectID": "decisions/20211031-openvr-for-godot-engine.html",
-    "href": "decisions/20211031-openvr-for-godot-engine.html",
-    "title": "Rejected: OpenVR for Godot Engine",
+    "objectID": "decisions/20240511-review-80-vr.html#the-road-not-taken",
+    "href": "decisions/20240511-review-80-vr.html#the-road-not-taken",
+    "title": "Rejected: VR Game with 80 Players and One World Server",
     "section": "",
-    "text": "Rejected: OpenVR for Godot Engine\n\nContext and Problem Statement\nOpenVR for Godot Engine\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nOpenVR for Godot Engine\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n\nCompile gdextension\nCompile openvr\nRun\nModify game code\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNo.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nThis is core.\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "An alternative would be to increase the number of players or world servers, but this would require more resources and infrastructure."
   },
   {
-    "objectID": "decisions/20240630-use-motion-transformers-for-prediction.html",
-    "href": "decisions/20240630-use-motion-transformers-for-prediction.html",
-    "title": "Proposed: Use motion transformers for motion prediction",
+    "objectID": "decisions/20240511-review-80-vr.html#the-infrequent-use-case",
+    "href": "decisions/20240511-review-80-vr.html#the-infrequent-use-case",
+    "title": "Rejected: VR Game with 80 Players and One World Server",
     "section": "",
-    "text": "In virtual reality and gaming, predicting human motion is a critical aspect. It helps in creating more realistic characters and enhancing user interaction. Currently, we use traditional methods that are not very efficient and lack accuracy.\n\n\n\nThe main problem we are trying to solve is to predict the next tokens for motion. This will help us in creating more realistic movements for our characters in the game. Additionally, it can be used for generating new animations and for networking compression.\n\n\n\nWe propose to use MotionGPT, a transformer-based model that treats human motion as a foreign language. It learns the ‘grammar’ of human motion from data and uses it to generate new motions.\n# Pseudo-code for MotionGPT\ndef MotionGPT(data):\n    model = TransformerModel()\n    model.train(data)\n    return model.generate_motion()\n\n\n\n\nImproved accuracy in motion prediction.\nMore realistic character movements.\nEnhanced user experience.\nGeneration of new animations.\nNetworking compression.\n\n\n\n\n\nRequires large amounts of data for training.\nMight be computationally expensive.\n\n\n\n\nWe could have continued using traditional methods for motion prediction but they lack the efficiency and accuracy provided by transformer models.\n\n\n\nThis proposal might not be beneficial for games that do not require realistic human motion or where the computational resources are limited.\n\n\n\nThis proposal is core to our project as it directly impacts the realism and user experience of our game. It will be implemented by our development team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nMotionGPT: Human Motion\n\nAI assistant Aria assisted with this article."
+    "text": "In cases where player traffic is consistently low, the infrastructure may be underutilized."
   },
   {
-    "objectID": "decisions/20240630-use-motion-transformers-for-prediction.html#motiongpt-human-motion-as-foreign-language",
-    "href": "decisions/20240630-use-motion-transformers-for-prediction.html#motiongpt-human-motion-as-foreign-language",
-    "title": "Proposed: Use motion transformers for motion prediction",
+    "objectID": "decisions/20240511-review-80-vr.html#in-core-and-done-by-us",
+    "href": "decisions/20240511-review-80-vr.html#in-core-and-done-by-us",
+    "title": "Rejected: VR Game with 80 Players and One World Server",
     "section": "",
-    "text": "In virtual reality and gaming, predicting human motion is a critical aspect. It helps in creating more realistic characters and enhancing user interaction. Currently, we use traditional methods that are not very efficient and lack accuracy.\n\n\n\nThe main problem we are trying to solve is to predict the next tokens for motion. This will help us in creating more realistic movements for our characters in the game. Additionally, it can be used for generating new animations and for networking compression.\n\n\n\nWe propose to use MotionGPT, a transformer-based model that treats human motion as a foreign language. It learns the ‘grammar’ of human motion from data and uses it to generate new motions.\n# Pseudo-code for MotionGPT\ndef MotionGPT(data):\n    model = TransformerModel()\n    model.train(data)\n    return model.generate_motion()\n\n\n\n\nImproved accuracy in motion prediction.\nMore realistic character movements.\nEnhanced user experience.\nGeneration of new animations.\nNetworking compression.\n\n\n\n\n\nRequires large amounts of data for training.\nMight be computationally expensive.\n\n\n\n\nWe could have continued using traditional methods for motion prediction but they lack the efficiency and accuracy provided by transformer models.\n\n\n\nThis proposal might not be beneficial for games that do not require realistic human motion or where the computational resources are limited.\n\n\n\nThis proposal is core to our project as it directly impacts the realism and user experience of our game. It will be implemented by our development team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nMotionGPT: Human Motion\n\nAI assistant Aria assisted with this article."
+    "text": "The proposed stress testing will be conducted by the V-Sekai development team."
   },
   {
-    "objectID": "decisions/20240522-shader-motion-to-bvh.html",
-    "href": "decisions/20240522-shader-motion-to-bvh.html",
-    "title": "Draft: shadermotion to BVH",
+    "objectID": "decisions/20240511-review-80-vr.html#status",
+    "href": "decisions/20240511-review-80-vr.html#status",
+    "title": "Rejected: VR Game with 80 Players and One World Server",
     "section": "",
-    "text": "Lacking characters motions to work with.\nTransferring motions across platforms via video.\n\n\n\n#shadermotion allows us to transfer motion for other VR platforms into a standard motion format.\n\n\n\nShaderMotion: “OBS” etc. motion captured video from VRChat.\n\n\n\nFloss.mp4\n\n\nExample: Floss.mp4\n(repo: lox9973/ShaderMotion)\nShaderMotion =&gt; BVH\n\ninput: mpeg4\noutput: bvh\n\n\n\n\n.mp4 #shadermotion video\nshadermotion-to-bvh by guillefix\n\ndownload shadermotion-to-bvh.zip from XXX github repo releases\nunpack to a folder\n\n\n\n\n\nRun shadermotion2.exe --video \"yourvideo.mp4\"\nKEEP THE WINDOW FOCUSED\nOnce completed, look for yourvideo.bvh\n\n\n\nThanks to humbletim for being the scribe\nThanks to lyuma for being test pilot flying these steps\n\n\n\n\n\nAble to have motion for characters\n\n\n\n\n\nMany steps\n\n\n\n\n#shadermotion is a novel solution to capturing motion from VRChat.\n\n\n\nThis document describes how to integrate #shadermotion with us.\n\n\n\n\nhttps://chibifire.com/shader_motion/\nhttps://hackmd.io/EmOAt375S8KFqaNdPDJCXQ\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Status: Rejected"
   },
   {
-    "objectID": "decisions/20240522-shader-motion-to-bvh.html#context-and-problem-statement",
-    "href": "decisions/20240522-shader-motion-to-bvh.html#context-and-problem-statement",
-    "title": "Draft: shadermotion to BVH",
+    "objectID": "decisions/20240511-review-80-vr.html#decision-makers",
+    "href": "decisions/20240511-review-80-vr.html#decision-makers",
+    "title": "Rejected: VR Game with 80 Players and One World Server",
     "section": "",
-    "text": "Lacking characters motions to work with.\nTransferring motions across platforms via video."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20240522-shader-motion-to-bvh.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20240522-shader-motion-to-bvh.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Draft: shadermotion to BVH",
+    "objectID": "decisions/20240511-review-80-vr.html#tags",
+    "href": "decisions/20240511-review-80-vr.html#tags",
+    "title": "Rejected: VR Game with 80 Players and One World Server",
     "section": "",
-    "text": "#shadermotion allows us to transfer motion for other VR platforms into a standard motion format."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20240522-shader-motion-to-bvh.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-andor-diagrams",
-    "href": "decisions/20240522-shader-motion-to-bvh.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-andor-diagrams",
-    "title": "Draft: shadermotion to BVH",
+    "objectID": "decisions/20240511-review-80-vr.html#further-reading",
+    "href": "decisions/20240511-review-80-vr.html#further-reading",
+    "title": "Rejected: VR Game with 80 Players and One World Server",
     "section": "",
-    "text": "ShaderMotion: “OBS” etc. motion captured video from VRChat.\n\n\n\nFloss.mp4\n\n\nExample: Floss.mp4\n(repo: lox9973/ShaderMotion)\nShaderMotion =&gt; BVH\n\ninput: mpeg4\noutput: bvh\n\n\n\n\n.mp4 #shadermotion video\nshadermotion-to-bvh by guillefix\n\ndownload shadermotion-to-bvh.zip from XXX github repo releases\nunpack to a folder\n\n\n\n\n\nRun shadermotion2.exe --video \"yourvideo.mp4\"\nKEEP THE WINDOW FOCUSED\nOnce completed, look for yourvideo.bvh\n\n\n\nThanks to humbletim for being the scribe\nThanks to lyuma for being test pilot flying these steps"
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\ncreating-a-first-person-shooter-that-scales-to-millions-of-players\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240522-shader-motion-to-bvh.html#positive-consequences",
-    "href": "decisions/20240522-shader-motion-to-bvh.html#positive-consequences",
-    "title": "Draft: shadermotion to BVH",
+    "objectID": "decisions/20240105-1-meter-128-quantize.html",
+    "href": "decisions/20240105-1-meter-128-quantize.html",
+    "title": "Proposed: 1 Meter Cubed 128 Quantized",
     "section": "",
-    "text": "Able to have motion for characters"
+    "text": "Status: Proposed \nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nMeshGPT’s “1 Meter Cubed 128 Quantized” format has emerged as a potential method to achieve standardized precision within virtual reality (VR) content creation, centring around polygonal modeling rather than voxel methods.\n\n\n\nThe key objective is to harness the potential of the “1 Meter Cubed 128 Quantized” format to enhance procedural generation processes within VR development.\n\n\n\n\nDevelop a comprehensive framework for environment generation that leverages the strengths of the polygonal quantized format.\nIntegrate adaptive algorithms tailored for this format to ensure dynamic responsiveness in VR spaces.\nEmbrace modular design paradigms that align with polygonal modeling to expedite the construction of VR environments.\n\n\n\n\n\nFosters a more intuitive AI-creator collaboration using a polygonal format conducive to AI tools.\nLowers barriers to entry for creators, leading to increased efficiency and innovation.\nStreamlines procedural generation to operate with enhanced speed and reduced resource consumption.\nProvides a scalable and flexible model to cater to diverse design requirements in VR environments.\n\n\n\n\n\nRequires considerable investment in research and development for effective technique integration.\nMay present a learning curve for developers not familiar with non-voxel formats.\n\n\n\n\n\nDependence on traditional voxel-based procedural generation technologies could be left behind in favor of the enhanced capabilities offered by the polygonal quantized format.\n\n\n\n\n\nSpecialized VR environments may demand generation methods that extend beyond the standard capacities of the “1 Meter Cubed 128 Quantized” format.\n\n\n\n\n\nThe enhancement of procedural generation via the adoption of the 1 Meter Cubed 128 Quantized polygonal format is an initiative headed by the V-Sekai team.\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nShadows of Doubt on Steam - A showcase of the advancements made possible through procedural generation in gaming.\n\nAssisted by AI Aria."
   },
   {
-    "objectID": "decisions/20240522-shader-motion-to-bvh.html#negative-consequences",
-    "href": "decisions/20240522-shader-motion-to-bvh.html#negative-consequences",
-    "title": "Draft: shadermotion to BVH",
+    "objectID": "decisions/20240105-1-meter-128-quantize.html#metadata",
+    "href": "decisions/20240105-1-meter-128-quantize.html#metadata",
+    "title": "Proposed: 1 Meter Cubed 128 Quantized",
     "section": "",
-    "text": "Many steps"
+    "text": "Status: Proposed \nDeciders: V-Sekai\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20240522-shader-motion-to-bvh.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20240522-shader-motion-to-bvh.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Draft: shadermotion to BVH",
+    "objectID": "decisions/20240105-1-meter-128-quantize.html#the-backdrop",
+    "href": "decisions/20240105-1-meter-128-quantize.html#the-backdrop",
+    "title": "Proposed: 1 Meter Cubed 128 Quantized",
     "section": "",
-    "text": "#shadermotion is a novel solution to capturing motion from VRChat."
+    "text": "MeshGPT’s “1 Meter Cubed 128 Quantized” format has emerged as a potential method to achieve standardized precision within virtual reality (VR) content creation, centring around polygonal modeling rather than voxel methods."
   },
   {
-    "objectID": "decisions/20240522-shader-motion-to-bvh.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20240522-shader-motion-to-bvh.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Draft: shadermotion to BVH",
+    "objectID": "decisions/20240105-1-meter-128-quantize.html#the-challenge",
+    "href": "decisions/20240105-1-meter-128-quantize.html#the-challenge",
+    "title": "Proposed: 1 Meter Cubed 128 Quantized",
     "section": "",
-    "text": "This document describes how to integrate #shadermotion with us."
+    "text": "The key objective is to harness the potential of the “1 Meter Cubed 128 Quantized” format to enhance procedural generation processes within VR development."
   },
   {
-    "objectID": "decisions/20240522-shader-motion-to-bvh.html#references",
-    "href": "decisions/20240522-shader-motion-to-bvh.html#references",
-    "title": "Draft: shadermotion to BVH",
+    "objectID": "decisions/20240105-1-meter-128-quantize.html#the-strategy",
+    "href": "decisions/20240105-1-meter-128-quantize.html#the-strategy",
+    "title": "Proposed: 1 Meter Cubed 128 Quantized",
     "section": "",
-    "text": "https://chibifire.com/shader_motion/\nhttps://hackmd.io/EmOAt375S8KFqaNdPDJCXQ"
+    "text": "Develop a comprehensive framework for environment generation that leverages the strengths of the polygonal quantized format.\nIntegrate adaptive algorithms tailored for this format to ensure dynamic responsiveness in VR spaces.\nEmbrace modular design paradigms that align with polygonal modeling to expedite the construction of VR environments."
   },
   {
-    "objectID": "decisions/20240522-shader-motion-to-bvh.html#derivative-license",
-    "href": "decisions/20240522-shader-motion-to-bvh.html#derivative-license",
-    "title": "Draft: shadermotion to BVH",
+    "objectID": "decisions/20240105-1-meter-128-quantize.html#the-upside",
+    "href": "decisions/20240105-1-meter-128-quantize.html#the-upside",
+    "title": "Proposed: 1 Meter Cubed 128 Quantized",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Fosters a more intuitive AI-creator collaboration using a polygonal format conducive to AI tools.\nLowers barriers to entry for creators, leading to increased efficiency and innovation.\nStreamlines procedural generation to operate with enhanced speed and reduced resource consumption.\nProvides a scalable and flexible model to cater to diverse design requirements in VR environments."
   },
   {
-    "objectID": "decisions/20210811-disconnected-ipfs.html",
-    "href": "decisions/20210811-disconnected-ipfs.html",
-    "title": "Proposed: Godot Engine implementation of disconnected IPFS",
+    "objectID": "decisions/20240105-1-meter-128-quantize.html#the-downside",
+    "href": "decisions/20240105-1-meter-128-quantize.html#the-downside",
+    "title": "Proposed: 1 Meter Cubed 128 Quantized",
     "section": "",
-    "text": "Proposed: Godot Engine implementation of disconnected IPFS\n\nContext and Problem Statement\nDisconnect IPFS from the internet\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nDisconnect IPFS so it can be standalone packages.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nImplement https://github.com/skogard/nebulus as a c++ library.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nMay be able to be done by others.\n\n\nPositive Consequences\n\nsend a offline package\n\n\n\nNegative Consequences\n\nin javascript\n\n\n\nIs there a reason why this should be core and done by us?\n\nMight be an extension\n\n\n\nReferences\n\nhttps://github.com/skogard/nebulus\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Requires considerable investment in research and development for effective technique integration.\nMay present a learning curve for developers not familiar with non-voxel formats."
   },
   {
-    "objectID": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html",
-    "href": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html",
-    "title": "Proposed: Modify the Mesh Transformer for Quads",
+    "objectID": "decisions/20240105-1-meter-128-quantize.html#the-road-not-taken",
+    "href": "decisions/20240105-1-meter-128-quantize.html#the-road-not-taken",
+    "title": "Proposed: 1 Meter Cubed 128 Quantized",
     "section": "",
-    "text": "We’re working on a project that involves using an autoencoder/transformer for 3D models. The current setup does not have a setting for quads, which is a requirement for our project.\n\n\n\nThe challenge is to modify the autoencoder/transformer to include a setting for quads and achieve a loss around 0.35.\n\n\n\n\nModify the Autoencoder/Transformer: Update the existing code to include a quads=True parameter in the autoencoder/transformer.\nTest the Modification: Run tests to ensure that the modification works as expected and doesn’t break existing functionality.\nOptimize the Loss: Adjust the parameters and settings of the autoencoder/transformer to aim for a loss around 0.35 when processing quads.\n\n\n\n\n\nThis modification will allow us to process quads in our 3D models.\nAchieving a loss around 0.35 will improve the quality of our model transformations.\n\n\n\n\n\nModifying the existing code could introduce new bugs or issues.\nIt might be challenging to achieve the desired loss.\n\n\n\n\nAn alternative approach could be to convert quads into triangles before processing them with the autoencoder/transformer. However, this might result in loss of information or quality.\n\n\n\nThis modification might not be necessary if we are dealing with 3D models that do not contain quads.\n\n\n\nThe V-Sekai development team will handle the modification of the autoencoder/transformer and the optimization of the loss.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - The GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this proposal."
+    "text": "Dependence on traditional voxel-based procedural generation technologies could be left behind in favor of the enhanced capabilities offered by the polygonal quantized format."
   },
   {
-    "objectID": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#the-context",
-    "href": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#the-context",
-    "title": "Proposed: Modify the Mesh Transformer for Quads",
+    "objectID": "decisions/20240105-1-meter-128-quantize.html#the-infrequent-use-case",
+    "href": "decisions/20240105-1-meter-128-quantize.html#the-infrequent-use-case",
+    "title": "Proposed: 1 Meter Cubed 128 Quantized",
     "section": "",
-    "text": "We’re working on a project that involves using an autoencoder/transformer for 3D models. The current setup does not have a setting for quads, which is a requirement for our project."
+    "text": "Specialized VR environments may demand generation methods that extend beyond the standard capacities of the “1 Meter Cubed 128 Quantized” format."
   },
   {
-    "objectID": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#the-problem-statement",
-    "href": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#the-problem-statement",
-    "title": "Proposed: Modify the Mesh Transformer for Quads",
+    "objectID": "decisions/20240105-1-meter-128-quantize.html#in-core-and-done-by-us",
+    "href": "decisions/20240105-1-meter-128-quantize.html#in-core-and-done-by-us",
+    "title": "Proposed: 1 Meter Cubed 128 Quantized",
     "section": "",
-    "text": "The challenge is to modify the autoencoder/transformer to include a setting for quads and achieve a loss around 0.35."
+    "text": "The enhancement of procedural generation via the adoption of the 1 Meter Cubed 128 Quantized polygonal format is an initiative headed by the V-Sekai team."
   },
   {
-    "objectID": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Modify the Mesh Transformer for Quads",
+    "objectID": "decisions/20240105-1-meter-128-quantize.html#further-reading",
+    "href": "decisions/20240105-1-meter-128-quantize.html#further-reading",
+    "title": "Proposed: 1 Meter Cubed 128 Quantized",
     "section": "",
-    "text": "Modify the Autoencoder/Transformer: Update the existing code to include a quads=True parameter in the autoencoder/transformer.\nTest the Modification: Run tests to ensure that the modification works as expected and doesn’t break existing functionality.\nOptimize the Loss: Adjust the parameters and settings of the autoencoder/transformer to aim for a loss around 0.35 when processing quads."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nShadows of Doubt on Steam - A showcase of the advancements made possible through procedural generation in gaming.\n\nAssisted by AI Aria."
   },
   {
-    "objectID": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#the-benefits",
-    "href": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#the-benefits",
-    "title": "Proposed: Modify the Mesh Transformer for Quads",
+    "objectID": "decisions/20240121-easy-diffusion-fedora-install.html",
+    "href": "decisions/20240121-easy-diffusion-fedora-install.html",
+    "title": "Proposed: Easy Diffusion AI Setup on Linux Systems",
     "section": "",
-    "text": "This modification will allow us to process quads in our 3D models.\nAchieving a loss around 0.35 will improve the quality of our model transformations."
+    "text": "Status: Proposed\nDeciders: Development Team\nTags: AI, Easy Diffusion, Linux\n\n\n\n\nThe goal is to streamline the installation process of Easy Diffusion for creating AI-generated images on Linux systems.\n\n\n\nThe challenge lies in ensuring a simple and repeatable setup process for installing and configuring Easy Diffusion on various Linux distributions.\n\n\n\n\nAssess compatibility between Easy Diffusion and popular Linux distributions.\nIdentify dependencies and prerequisites required for Easy Diffusion.\nDevelop a script or instructions for a hassle-free setup experience.\nConduct test installations across different environments.\n\nFirst, download the latest release of Easy Diffusion for Linux. Then create a dedicated user for running Easy Diffusion and establish a standard location for the tool, like /opt/easy_diffusion.\n# As root or using sudo\ndnf install curl bzip2 -y\nuseradd --system --create-home --home-dir /opt/easy_diffusion easy_diffusion_user\nmkdir -p /opt/easy_diffusion\ncurl -L https://github.com/cmdr2/stable-diffusion-ui/releases/latest/download/Easy-Diffusion-Linux.zip -o /opt/easy_diffusion/Easy-Diffusion-Linux.zip\nunzip /opt/easy_diffusion/Easy-Diffusion-Linux.zip -d /opt/easy_diffusion/\n\nsudo bash -c 'cat &gt; /opt/easy_diffusion/easy-diffusion/config.yaml &lt;&lt;EOF\n# Configuration for Easy Diffusion\n# Change listen_port if port 9000 is already in use on your system.\n# Set listen_to_network to true to make Easy Diffusion accessible on your local network.\n\nnet:\n  listen_port: 9000\n  listen_to_network: true\n\n# Multi GPU setup\nrender_devices: auto\n\n# Set open_browser_on_start to false to disable opening a new browser tab on each restart.\nui:\n  open_browser_on_start: false\n\n# Set update_branch to main to use the stable version, or to beta to use the experimental\n# beta version.\nupdate_branch: beta\n\n# Set force_save_path to enforce an auto save path. Clients will not be able to change or\n# disable auto save when this option is set. Please adapt the path in the examples to your\n# needs.\n# Windows:\n# force_save_path: C:\\\\Easy Diffusion Images\\\\\n# Linux:\n# force_save_path: /data/easy_diffusion_images/\nforce_save_path: /opt/easy_diffusion/easy_diffusion_images/\nEOF'\nchown -R easy_diffusion_user: /opt/easy_diffusion\nchmod +x /opt/easy_diffusion/easy-diffusion/start.sh\nA systemd service configuration is used to manage the Easy Diffusion process:\nsudo bash -c 'cat &gt; /etc/systemd/system/easy-diffusion.service &lt;&lt;EOF\n[Unit]\nDescription=Easy Diffusion AI Image Generation Tool\nAfter=network.target\n\n[Service]\nUser=easy_diffusion_user\nWorkingDirectory=/opt/easy_diffusion/easy-diffusion\nExecStart=/bin/bash /opt/easy_diffusion/easy-diffusion/start.sh\nRestart=on-failure\n\n[Install]\nWantedBy=multi-user.target\nEOF'\nEnable and start the service as follows:\nsudo systemctl daemon-reload\nsudo systemctl enable easy-diffusion.service\nsudo systemctl start easy-diffusion.service\nCheck the status to confirm correct operation:\nsudo systemctl status easy-diffusion.service\nTo view detailed logs, use:\njournalctl -u easy-diffusion.service\n\n\n\n\nAutomates the setup process, minimizing user intervention.\nOffers consistency across different installations.\nSimplifies management with systemd integration.\n\n\n\n\n\nRequires thorough testing to ensure broad compatibility.\nSystemd is not universally adopted among all Linux distributions.\nAdditional effort is needed to maintain the service file and update paths as necessary when new versions are released.\n\n\n\n\n\nDownload for Linux: Official source code and documentation.\n\nAria, an AI assistant, provided support in formulating this proposal."
   },
   {
-    "objectID": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#the-downsides",
-    "href": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#the-downsides",
-    "title": "Proposed: Modify the Mesh Transformer for Quads",
+    "objectID": "decisions/20240121-easy-diffusion-fedora-install.html#metadata",
+    "href": "decisions/20240121-easy-diffusion-fedora-install.html#metadata",
+    "title": "Proposed: Easy Diffusion AI Setup on Linux Systems",
     "section": "",
-    "text": "Modifying the existing code could introduce new bugs or issues.\nIt might be challenging to achieve the desired loss."
+    "text": "Status: Proposed\nDeciders: Development Team\nTags: AI, Easy Diffusion, Linux"
   },
   {
-    "objectID": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#the-road-not-taken",
-    "href": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#the-road-not-taken",
-    "title": "Proposed: Modify the Mesh Transformer for Quads",
+    "objectID": "decisions/20240121-easy-diffusion-fedora-install.html#backdrop",
+    "href": "decisions/20240121-easy-diffusion-fedora-install.html#backdrop",
+    "title": "Proposed: Easy Diffusion AI Setup on Linux Systems",
     "section": "",
-    "text": "An alternative approach could be to convert quads into triangles before processing them with the autoencoder/transformer. However, this might result in loss of information or quality."
+    "text": "The goal is to streamline the installation process of Easy Diffusion for creating AI-generated images on Linux systems."
   },
   {
-    "objectID": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#the-infrequent-use-case",
-    "href": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#the-infrequent-use-case",
-    "title": "Proposed: Modify the Mesh Transformer for Quads",
+    "objectID": "decisions/20240121-easy-diffusion-fedora-install.html#challenge",
+    "href": "decisions/20240121-easy-diffusion-fedora-install.html#challenge",
+    "title": "Proposed: Easy Diffusion AI Setup on Linux Systems",
     "section": "",
-    "text": "This modification might not be necessary if we are dealing with 3D models that do not contain quads."
+    "text": "The challenge lies in ensuring a simple and repeatable setup process for installing and configuring Easy Diffusion on various Linux distributions."
   },
   {
-    "objectID": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#in-core-and-done-by-us",
-    "href": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#in-core-and-done-by-us",
-    "title": "Proposed: Modify the Mesh Transformer for Quads",
+    "objectID": "decisions/20240121-easy-diffusion-fedora-install.html#strategy",
+    "href": "decisions/20240121-easy-diffusion-fedora-install.html#strategy",
+    "title": "Proposed: Easy Diffusion AI Setup on Linux Systems",
     "section": "",
-    "text": "The V-Sekai development team will handle the modification of the autoencoder/transformer and the optimization of the loss."
+    "text": "Assess compatibility between Easy Diffusion and popular Linux distributions.\nIdentify dependencies and prerequisites required for Easy Diffusion.\nDevelop a script or instructions for a hassle-free setup experience.\nConduct test installations across different environments.\n\nFirst, download the latest release of Easy Diffusion for Linux. Then create a dedicated user for running Easy Diffusion and establish a standard location for the tool, like /opt/easy_diffusion.\n# As root or using sudo\ndnf install curl bzip2 -y\nuseradd --system --create-home --home-dir /opt/easy_diffusion easy_diffusion_user\nmkdir -p /opt/easy_diffusion\ncurl -L https://github.com/cmdr2/stable-diffusion-ui/releases/latest/download/Easy-Diffusion-Linux.zip -o /opt/easy_diffusion/Easy-Diffusion-Linux.zip\nunzip /opt/easy_diffusion/Easy-Diffusion-Linux.zip -d /opt/easy_diffusion/\n\nsudo bash -c 'cat &gt; /opt/easy_diffusion/easy-diffusion/config.yaml &lt;&lt;EOF\n# Configuration for Easy Diffusion\n# Change listen_port if port 9000 is already in use on your system.\n# Set listen_to_network to true to make Easy Diffusion accessible on your local network.\n\nnet:\n  listen_port: 9000\n  listen_to_network: true\n\n# Multi GPU setup\nrender_devices: auto\n\n# Set open_browser_on_start to false to disable opening a new browser tab on each restart.\nui:\n  open_browser_on_start: false\n\n# Set update_branch to main to use the stable version, or to beta to use the experimental\n# beta version.\nupdate_branch: beta\n\n# Set force_save_path to enforce an auto save path. Clients will not be able to change or\n# disable auto save when this option is set. Please adapt the path in the examples to your\n# needs.\n# Windows:\n# force_save_path: C:\\\\Easy Diffusion Images\\\\\n# Linux:\n# force_save_path: /data/easy_diffusion_images/\nforce_save_path: /opt/easy_diffusion/easy_diffusion_images/\nEOF'\nchown -R easy_diffusion_user: /opt/easy_diffusion\nchmod +x /opt/easy_diffusion/easy-diffusion/start.sh\nA systemd service configuration is used to manage the Easy Diffusion process:\nsudo bash -c 'cat &gt; /etc/systemd/system/easy-diffusion.service &lt;&lt;EOF\n[Unit]\nDescription=Easy Diffusion AI Image Generation Tool\nAfter=network.target\n\n[Service]\nUser=easy_diffusion_user\nWorkingDirectory=/opt/easy_diffusion/easy-diffusion\nExecStart=/bin/bash /opt/easy_diffusion/easy-diffusion/start.sh\nRestart=on-failure\n\n[Install]\nWantedBy=multi-user.target\nEOF'\nEnable and start the service as follows:\nsudo systemctl daemon-reload\nsudo systemctl enable easy-diffusion.service\nsudo systemctl start easy-diffusion.service\nCheck the status to confirm correct operation:\nsudo systemctl status easy-diffusion.service\nTo view detailed logs, use:\njournalctl -u easy-diffusion.service"
   },
   {
-    "objectID": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#status",
-    "href": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#status",
-    "title": "Proposed: Modify the Mesh Transformer for Quads",
+    "objectID": "decisions/20240121-easy-diffusion-fedora-install.html#upside",
+    "href": "decisions/20240121-easy-diffusion-fedora-install.html#upside",
+    "title": "Proposed: Easy Diffusion AI Setup on Linux Systems",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "Automates the setup process, minimizing user intervention.\nOffers consistency across different installations.\nSimplifies management with systemd integration."
   },
   {
-    "objectID": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#decision-makers",
-    "href": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#decision-makers",
-    "title": "Proposed: Modify the Mesh Transformer for Quads",
+    "objectID": "decisions/20240121-easy-diffusion-fedora-install.html#downside",
+    "href": "decisions/20240121-easy-diffusion-fedora-install.html#downside",
+    "title": "Proposed: Easy Diffusion AI Setup on Linux Systems",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "Requires thorough testing to ensure broad compatibility.\nSystemd is not universally adopted among all Linux distributions.\nAdditional effort is needed to maintain the service file and update paths as necessary when new versions are released."
   },
   {
-    "objectID": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#tags",
-    "href": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#tags",
-    "title": "Proposed: Modify the Mesh Transformer for Quads",
+    "objectID": "decisions/20240121-easy-diffusion-fedora-install.html#further-reading",
+    "href": "decisions/20240121-easy-diffusion-fedora-install.html#further-reading",
+    "title": "Proposed: Easy Diffusion AI Setup on Linux Systems",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Download for Linux: Official source code and documentation.\n\nAria, an AI assistant, provided support in formulating this proposal."
   },
   {
-    "objectID": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#further-reading",
-    "href": "decisions/20240613-modifying-the-mesh-transformer-for-quads.html#further-reading",
-    "title": "Proposed: Modify the Mesh Transformer for Quads",
+    "objectID": "decisions/20230803-jolt-gextension-to-module.html",
+    "href": "decisions/20230803-jolt-gextension-to-module.html",
+    "title": "Proposed: Port Godot Jolt from GDExtension to C++ Module",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - The GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this proposal."
+    "text": "Status: Proposed\nDeciders: v-sekai, fire\nTags: Godot, Jolt, GDExtension, C++ Module, SCons, CMake\n\n\n\n\nGodot Jolt is currently implemented as a GDExtension C++ extension. However, we want to use it as a C++ module, which requires porting from CMake to SCons. This change will also allow us to experiment with soft physics.\n\n\n\n\n\n\nAnalyze the current structure of Godot Jolt as a GDExtension.\nPlan the new structure as a C++ module.\nConvert the build system from CMake to SCons.\nTest the newly created C++ module in different scenarios.\nExperiment with soft physics once the module is stable.\n\n\n\n\n\nThe implementation details will be decided upon acceptance of this proposal.\n\n\n\n\nMore control over the engine’s core functionality.\nAbility to experiment with soft physics.\nBetter integration with Godot’s core systems.\nEnable double precision support\n\n\n\n\n\nRequires knowledge of both CMake and SCons.\nPotential increase in development time due to the complexity of porting.\n\n\n\n\nThis section will be filled as we explore different options and discard those that are not feasible or effective.\n\n\n\nGiven the complexity of porting a GDExtension to a C++ module, it cannot be simply worked around with a few lines of script.\n\n\n\nPorting Godot Jolt to a C++ module will provide more flexibility and control over its functionalities. It aligns with our goal of enhancing the capabilities of our game engine.\n\n\n\n\nGodot Engine\nSCons\nCMake"
   },
   {
-    "objectID": "decisions/20230830-generating-v-sekai-worlds.html",
-    "href": "decisions/20230830-generating-v-sekai-worlds.html",
-    "title": "Proposed: Expanding Worlds",
+    "objectID": "decisions/20230803-jolt-gextension-to-module.html#metadata",
+    "href": "decisions/20230803-jolt-gextension-to-module.html#metadata",
+    "title": "Proposed: Port Godot Jolt from GDExtension to C++ Module",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nV-Sekai is a virtual reality (VR) platform that offers users the opportunity to immerse themselves in virtual worlds. However, there are certain limitations that hinder the overall user experience. This proposal aims to address these limitations by proposing specific areas for improvement within V-Sekai.\n\n\n\nV-Sekai currently faces several limitations, including non-functional menus in VR mode and a limited number of available worlds. These challenges affect the usability and variety of experiences for the users. To overcome these challenges and enhance the V-Sekai user experience, we must prioritize and focus on one area for improvement.\n\n\nWe propose focusing on Generating More Worlds as the first step towards enhancing V-Sekai. By creating new VR worlds within V-Sekai, users will have a wider range of experiences to explore. This involves designing and implementing new environments to expand the options available. With more worlds to choose from, users will have increased engagement and longer sessions within the V-Sekai platform.\n\n\n\n\nTo generate more worlds for V-Sekai, we will follow a comprehensive strategy that includes the following steps:\n\nIdentify User Preferences: Understand the target audience and their preferences. Research popular VR themes, genres, and settings to get an idea of what users would enjoy.\nDesign New Environments: Use 3D modeling software like Blender or Unity to design new virtual environments for V-Sekai. Consider creating diverse worlds like fantasy realms, futuristic cities, natural landscapes, or historical settings.\nImplement Interactive Elements: Make the new worlds interactive by adding objects, characters, and elements that users can engage with. This can include non-playable characters (NPCs), puzzles, hidden items, or mini-games within each world.\nTest and Refine: Conduct thorough testing to ensure the new worlds are visually appealing, optimized for performance, and provide a seamless VR experience. Gather user feedback and make necessary improvements based on their suggestions.\nIntegrate with V-Sekai: Once the new worlds are ready, integrate them into the V-Sekai platform. Ensure they are easily accessible through the menus or navigation system within V-Sekai’s VR interface.\nRelease and Promote: Launch the updated version of V-Sekai with the newly generated worlds. Promote the release through various channels, such as social media, gaming forums, Virtual Reality communities, and V-Sekai’s official website.\n\nBy following this strategy, we will not only address the current limitations but also create an engaging and immersive VR experience for V-Sekai users.\n\n\n\n\nIncreased user engagement: The availability of more worlds will provide users with greater options to explore, leading to longer sessions and increased immersion in V-Sekai.\nExpanded user base: With a wider range of experiences, V-Sekai will attract new users who are looking for diverse VR environments.\nPositive word-of-mouth: Satisfied users will share their experiences with others, generating positive reviews and recommendations for V-Sekai.\n\n\n\n\n\nDevelopment complexity: Creating new worlds requires significant effort and resources, including 3D modeling, programming, and testing. This may lead to increased development time and costs.\nUpfront investment: Generating more worlds will require upfront investment in terms of design, implementation, and integration with V-Sekai.\nUser feedback and iteration: Continuous user feedback is crucial to refine and improve the new worlds. This iterative process may extend the development timeline.\n\n\n\n\nAn alternative solution that was considered was Integrating Backend Services. This would involve improving the backend infrastructure of V-Sekai to enhance scalability, performance, and reliability. However, after careful consideration, we prioritize generating more worlds as it directly addresses user experience limitations and provides tangible benefits in terms of user engagement and appeal.\n\n\n\nThe generation of more worlds is within the core capabilities of our team at V-Sekai. We have experienced 3D designers, developers, and testers who are skilled in creating immersive VR environments. Therefore, we are confident in our ability to execute this proposed solution effectively and efficiently.\n\n\n\n\nV-Sekai\nThis article is assisted by AI.\n\nIf you have any further questions or need clarification on any aspect of this proposal, please feel free to ask."
+    "text": "Status: Proposed\nDeciders: v-sekai, fire\nTags: Godot, Jolt, GDExtension, C++ Module, SCons, CMake"
   },
   {
-    "objectID": "decisions/20230830-generating-v-sekai-worlds.html#metadata",
-    "href": "decisions/20230830-generating-v-sekai-worlds.html#metadata",
-    "title": "Proposed: Expanding Worlds",
+    "objectID": "decisions/20230803-jolt-gextension-to-module.html#context-and-problem-statement",
+    "href": "decisions/20230803-jolt-gextension-to-module.html#context-and-problem-statement",
+    "title": "Proposed: Port Godot Jolt from GDExtension to C++ Module",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai"
+    "text": "Godot Jolt is currently implemented as a GDExtension C++ extension. However, we want to use it as a C++ module, which requires porting from CMake to SCons. This change will also allow us to experiment with soft physics."
   },
   {
-    "objectID": "decisions/20230830-generating-v-sekai-worlds.html#introduction",
-    "href": "decisions/20230830-generating-v-sekai-worlds.html#introduction",
-    "title": "Proposed: Expanding Worlds",
+    "objectID": "decisions/20230803-jolt-gextension-to-module.html#proposed-solution",
+    "href": "decisions/20230803-jolt-gextension-to-module.html#proposed-solution",
+    "title": "Proposed: Port Godot Jolt from GDExtension to C++ Module",
     "section": "",
-    "text": "V-Sekai is a virtual reality (VR) platform that offers users the opportunity to immerse themselves in virtual worlds. However, there are certain limitations that hinder the overall user experience. This proposal aims to address these limitations by proposing specific areas for improvement within V-Sekai."
+    "text": "Analyze the current structure of Godot Jolt as a GDExtension.\nPlan the new structure as a C++ module.\nConvert the build system from CMake to SCons.\nTest the newly created C++ module in different scenarios.\nExperiment with soft physics once the module is stable."
   },
   {
-    "objectID": "decisions/20230830-generating-v-sekai-worlds.html#the-challenge",
-    "href": "decisions/20230830-generating-v-sekai-worlds.html#the-challenge",
-    "title": "Proposed: Expanding Worlds",
+    "objectID": "decisions/20230803-jolt-gextension-to-module.html#implementation",
+    "href": "decisions/20230803-jolt-gextension-to-module.html#implementation",
+    "title": "Proposed: Port Godot Jolt from GDExtension to C++ Module",
     "section": "",
-    "text": "V-Sekai currently faces several limitations, including non-functional menus in VR mode and a limited number of available worlds. These challenges affect the usability and variety of experiences for the users. To overcome these challenges and enhance the V-Sekai user experience, we must prioritize and focus on one area for improvement.\n\n\nWe propose focusing on Generating More Worlds as the first step towards enhancing V-Sekai. By creating new VR worlds within V-Sekai, users will have a wider range of experiences to explore. This involves designing and implementing new environments to expand the options available. With more worlds to choose from, users will have increased engagement and longer sessions within the V-Sekai platform."
+    "text": "The implementation details will be decided upon acceptance of this proposal."
   },
   {
-    "objectID": "decisions/20230830-generating-v-sekai-worlds.html#the-strategy",
-    "href": "decisions/20230830-generating-v-sekai-worlds.html#the-strategy",
-    "title": "Proposed: Expanding Worlds",
+    "objectID": "decisions/20230803-jolt-gextension-to-module.html#positive-consequences",
+    "href": "decisions/20230803-jolt-gextension-to-module.html#positive-consequences",
+    "title": "Proposed: Port Godot Jolt from GDExtension to C++ Module",
     "section": "",
-    "text": "To generate more worlds for V-Sekai, we will follow a comprehensive strategy that includes the following steps:\n\nIdentify User Preferences: Understand the target audience and their preferences. Research popular VR themes, genres, and settings to get an idea of what users would enjoy.\nDesign New Environments: Use 3D modeling software like Blender or Unity to design new virtual environments for V-Sekai. Consider creating diverse worlds like fantasy realms, futuristic cities, natural landscapes, or historical settings.\nImplement Interactive Elements: Make the new worlds interactive by adding objects, characters, and elements that users can engage with. This can include non-playable characters (NPCs), puzzles, hidden items, or mini-games within each world.\nTest and Refine: Conduct thorough testing to ensure the new worlds are visually appealing, optimized for performance, and provide a seamless VR experience. Gather user feedback and make necessary improvements based on their suggestions.\nIntegrate with V-Sekai: Once the new worlds are ready, integrate them into the V-Sekai platform. Ensure they are easily accessible through the menus or navigation system within V-Sekai’s VR interface.\nRelease and Promote: Launch the updated version of V-Sekai with the newly generated worlds. Promote the release through various channels, such as social media, gaming forums, Virtual Reality communities, and V-Sekai’s official website.\n\nBy following this strategy, we will not only address the current limitations but also create an engaging and immersive VR experience for V-Sekai users."
+    "text": "More control over the engine’s core functionality.\nAbility to experiment with soft physics.\nBetter integration with Godot’s core systems.\nEnable double precision support"
   },
   {
-    "objectID": "decisions/20230830-generating-v-sekai-worlds.html#upsides",
-    "href": "decisions/20230830-generating-v-sekai-worlds.html#upsides",
-    "title": "Proposed: Expanding Worlds",
+    "objectID": "decisions/20230803-jolt-gextension-to-module.html#negative-consequences",
+    "href": "decisions/20230803-jolt-gextension-to-module.html#negative-consequences",
+    "title": "Proposed: Port Godot Jolt from GDExtension to C++ Module",
     "section": "",
-    "text": "Increased user engagement: The availability of more worlds will provide users with greater options to explore, leading to longer sessions and increased immersion in V-Sekai.\nExpanded user base: With a wider range of experiences, V-Sekai will attract new users who are looking for diverse VR environments.\nPositive word-of-mouth: Satisfied users will share their experiences with others, generating positive reviews and recommendations for V-Sekai."
+    "text": "Requires knowledge of both CMake and SCons.\nPotential increase in development time due to the complexity of porting."
   },
   {
-    "objectID": "decisions/20230830-generating-v-sekai-worlds.html#downsides",
-    "href": "decisions/20230830-generating-v-sekai-worlds.html#downsides",
-    "title": "Proposed: Expanding Worlds",
+    "objectID": "decisions/20230803-jolt-gextension-to-module.html#option-graveyard",
+    "href": "decisions/20230803-jolt-gextension-to-module.html#option-graveyard",
+    "title": "Proposed: Port Godot Jolt from GDExtension to C++ Module",
     "section": "",
-    "text": "Development complexity: Creating new worlds requires significant effort and resources, including 3D modeling, programming, and testing. This may lead to increased development time and costs.\nUpfront investment: Generating more worlds will require upfront investment in terms of design, implementation, and integration with V-Sekai.\nUser feedback and iteration: Continuous user feedback is crucial to refine and improve the new worlds. This iterative process may extend the development timeline."
+    "text": "This section will be filled as we explore different options and discard those that are not feasible or effective."
   },
   {
-    "objectID": "decisions/20230830-generating-v-sekai-worlds.html#the-road-not-taken",
-    "href": "decisions/20230830-generating-v-sekai-worlds.html#the-road-not-taken",
-    "title": "Proposed: Expanding Worlds",
+    "objectID": "decisions/20230803-jolt-gextension-to-module.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230803-jolt-gextension-to-module.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Port Godot Jolt from GDExtension to C++ Module",
     "section": "",
-    "text": "An alternative solution that was considered was Integrating Backend Services. This would involve improving the backend infrastructure of V-Sekai to enhance scalability, performance, and reliability. However, after careful consideration, we prioritize generating more worlds as it directly addresses user experience limitations and provides tangible benefits in terms of user engagement and appeal."
+    "text": "Given the complexity of porting a GDExtension to a C++ module, it cannot be simply worked around with a few lines of script."
   },
   {
-    "objectID": "decisions/20230830-generating-v-sekai-worlds.html#in-core-and-done-by-us",
-    "href": "decisions/20230830-generating-v-sekai-worlds.html#in-core-and-done-by-us",
-    "title": "Proposed: Expanding Worlds",
+    "objectID": "decisions/20230803-jolt-gextension-to-module.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230803-jolt-gextension-to-module.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Port Godot Jolt from GDExtension to C++ Module",
     "section": "",
-    "text": "The generation of more worlds is within the core capabilities of our team at V-Sekai. We have experienced 3D designers, developers, and testers who are skilled in creating immersive VR environments. Therefore, we are confident in our ability to execute this proposed solution effectively and efficiently."
+    "text": "Porting Godot Jolt to a C++ module will provide more flexibility and control over its functionalities. It aligns with our goal of enhancing the capabilities of our game engine."
   },
   {
-    "objectID": "decisions/20230830-generating-v-sekai-worlds.html#further-reading",
-    "href": "decisions/20230830-generating-v-sekai-worlds.html#further-reading",
-    "title": "Proposed: Expanding Worlds",
+    "objectID": "decisions/20230803-jolt-gextension-to-module.html#references",
+    "href": "decisions/20230803-jolt-gextension-to-module.html#references",
+    "title": "Proposed: Port Godot Jolt from GDExtension to C++ Module",
     "section": "",
-    "text": "V-Sekai\nThis article is assisted by AI.\n\nIf you have any further questions or need clarification on any aspect of this proposal, please feel free to ask."
+    "text": "Godot Engine\nSCons\nCMake"
   },
   {
-    "objectID": "decisions/20231109-discord-polygonjs-generator.html",
-    "href": "decisions/20231109-discord-polygonjs-generator.html",
-    "title": "Proposed: Character Customization Discord Bot PoC for V-Sekai",
+    "objectID": "decisions/20240710-use-godot-engine-web-threaded.html",
+    "href": "decisions/20240710-use-godot-engine-web-threaded.html",
+    "title": "Proposed: Use Godot Engine Web Threaded",
     "section": "",
-    "text": "Status: Proposed \nDeciders: V-Sekai, fire\nTags: V-Sekai, Character Customization, Discord Bot, PoC\n\n\n\n\nWithin the V-Sekai community, there is a desire to enhance user engagement through interactive tools that allow for creative expression. The community seeks to leverage Discord as a platform to introduce such tools.\n\n\n\nThe current challenge is to create an interactive Discord bot that allows for immersive character customization, aligning with V-Sekai’s vision of fostering a creative and engaged community.\n\n\n\nTo create a Discord bot as a Proof of Concept (PoC) that demonstrates the feasibility of character customization using trait-based input, we will execute the following steps:\n\nDefine Key Traits: We will select a set of fundamental character traits such as height, body shape, hair color, and clothing style. Each trait will be associated with a Unicode emoji for straightforward identification and interaction within the Discord interface.\nBot Development: A bot will be developed to parse textual commands linked to each trait. For example, a user might input !height 📏 to set the character’s height or !hair 🎨 to choose a hair color.\nImage Generation: The bot will map each trait to a specific set of 2D image assets. It will have the logic to composite these assets into a single image that represents the character based on the selected traits.\nUser Interaction: Reaction buttons for ‘like’ 👍, ‘dislike’ 👎, and ‘regenerate’ 🔄 will be implemented to allow users to interact with the generated character. This will provide immediate feedback mechanisms for the community.\nTesting and Iteration: The bot will be deployed in a controlled Discord environment and tested by real users. Their feedback will be crucial for refining the bot’s functionality and user experience.\nDocumentation: All development processes, user interactions, and iterations will be thoroughly documented. This documentation will be critical for understanding user needs and will inform future development cycles.\n\nThis PoC will serve to validate the core idea, engage the user community early in the development process, and provide critical insights for scaling the bot to handle more complex trait manipulation and 3D character rendering in future phases.\n\n\n\nImplementing this bot will potentially increase community engagement by providing a fun and interactive character creation tool. It will also lay the foundation for future developments in VR and character design within the V-Sekai ecosystem.\n\n\n\nThe initial development of the bot may require significant resources and there is a risk of low user adoption. Additionally, ensuring the bot’s scalability and handling user feedback for improvements could be challenging.\n\n\n\nAlternatives, such as outsourcing the tool or purchasing an existing solution, were considered but ultimately rejected in favor of in-house development to retain creative control and better integration with V-Sekai’s infrastructure.\n\n\n\nThere might be less frequent use cases for the bot, such as character customization for one-time events or non-regular users. The bot’s design will need to account for these to ensure it remains relevant and accessible.\n\n\n\nThe core functionality of the bot aligns with V-Sekai’s objectives and values. The development will be handled internally to ensure the tool’s compatibility with the community’s needs and expectations.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nV-Sekai Official Website - Community of enthusiasts building a next-generation social and gaming VR platform powered by the Godot Engine 4.0\nNousResearch Yarn Mistral 7b 128k - Hugging Face - A Hugging Face Space by realgenius\nIssue #68 · polygonjs/polygonjs - GitHub - Discussion on using polygon.js as a Discord webhook watcher to output messages and attachments\n\nThis article was assisted by AI."
+    "text": "In the development of web-based applications using the Godot Engine, performance and responsiveness are critical. Leveraging multi-threading can significantly enhance these aspects.\n\n\n\nWhen developing web applications with Godot, we face challenges related to loading large resources and maintaining smooth audio playback. Single-threaded implementations often fall short in handling these tasks efficiently.\n\n\n\n\n\n\nFeature\nMulti-Threaded\nSingle-Threaded\n\n\n\n\nAudio Sampling\nx\nx\n\n\nNormal Audio Files\nx\n\n\n\nShared Array Buffer\nx\n\n\n\nLoad Large Maps in the Background\nx\n\n\n\nFull Browser Support\n\nx\n\n\nPotential Bugs\n\nx\n\n\n\n\n\n\n\nImproved Performance: Multi-threading allows for background resource loading, enhancing application responsiveness.\nBetter User Experience: Smooth audio playback and faster load times contribute to a more seamless user experience.\n\n\n\n\n\nComplexity: Implementing multi-threading can introduce complexity and potential bugs.\nBrowser Compatibility: Ensuring full browser support for multi-threaded features may require additional effort.\n\n\n\n\nAlternative approaches such as sticking with single-threaded implementations were considered but ultimately deemed less effective for handling large resources.\n\n\n\nIn cases where the application does not involve large resources or complex audio processing, single-threaded implementation might suffice.\n\n\n\nThis proposal aligns with our core values of efficiency and performance and will be implemented by our team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20231109-discord-polygonjs-generator.html#metadata",
-    "href": "decisions/20231109-discord-polygonjs-generator.html#metadata",
-    "title": "Proposed: Character Customization Discord Bot PoC for V-Sekai",
+    "objectID": "decisions/20240710-use-godot-engine-web-threaded.html#the-context",
+    "href": "decisions/20240710-use-godot-engine-web-threaded.html#the-context",
+    "title": "Proposed: Use Godot Engine Web Threaded",
     "section": "",
-    "text": "Status: Proposed \nDeciders: V-Sekai, fire\nTags: V-Sekai, Character Customization, Discord Bot, PoC"
+    "text": "In the development of web-based applications using the Godot Engine, performance and responsiveness are critical. Leveraging multi-threading can significantly enhance these aspects."
   },
   {
-    "objectID": "decisions/20231109-discord-polygonjs-generator.html#the-backdrop",
-    "href": "decisions/20231109-discord-polygonjs-generator.html#the-backdrop",
-    "title": "Proposed: Character Customization Discord Bot PoC for V-Sekai",
+    "objectID": "decisions/20240710-use-godot-engine-web-threaded.html#the-problem-statement",
+    "href": "decisions/20240710-use-godot-engine-web-threaded.html#the-problem-statement",
+    "title": "Proposed: Use Godot Engine Web Threaded",
     "section": "",
-    "text": "Within the V-Sekai community, there is a desire to enhance user engagement through interactive tools that allow for creative expression. The community seeks to leverage Discord as a platform to introduce such tools."
+    "text": "When developing web applications with Godot, we face challenges related to loading large resources and maintaining smooth audio playback. Single-threaded implementations often fall short in handling these tasks efficiently."
   },
   {
-    "objectID": "decisions/20231109-discord-polygonjs-generator.html#the-challenge",
-    "href": "decisions/20231109-discord-polygonjs-generator.html#the-challenge",
-    "title": "Proposed: Character Customization Discord Bot PoC for V-Sekai",
+    "objectID": "decisions/20240710-use-godot-engine-web-threaded.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240710-use-godot-engine-web-threaded.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Use Godot Engine Web Threaded",
     "section": "",
-    "text": "The current challenge is to create an interactive Discord bot that allows for immersive character customization, aligning with V-Sekai’s vision of fostering a creative and engaged community."
+    "text": "Feature\nMulti-Threaded\nSingle-Threaded\n\n\n\n\nAudio Sampling\nx\nx\n\n\nNormal Audio Files\nx\n\n\n\nShared Array Buffer\nx\n\n\n\nLoad Large Maps in the Background\nx\n\n\n\nFull Browser Support\n\nx\n\n\nPotential Bugs\n\nx"
   },
   {
-    "objectID": "decisions/20231109-discord-polygonjs-generator.html#the-strategy",
-    "href": "decisions/20231109-discord-polygonjs-generator.html#the-strategy",
-    "title": "Proposed: Character Customization Discord Bot PoC for V-Sekai",
+    "objectID": "decisions/20240710-use-godot-engine-web-threaded.html#the-benefits",
+    "href": "decisions/20240710-use-godot-engine-web-threaded.html#the-benefits",
+    "title": "Proposed: Use Godot Engine Web Threaded",
     "section": "",
-    "text": "To create a Discord bot as a Proof of Concept (PoC) that demonstrates the feasibility of character customization using trait-based input, we will execute the following steps:\n\nDefine Key Traits: We will select a set of fundamental character traits such as height, body shape, hair color, and clothing style. Each trait will be associated with a Unicode emoji for straightforward identification and interaction within the Discord interface.\nBot Development: A bot will be developed to parse textual commands linked to each trait. For example, a user might input !height 📏 to set the character’s height or !hair 🎨 to choose a hair color.\nImage Generation: The bot will map each trait to a specific set of 2D image assets. It will have the logic to composite these assets into a single image that represents the character based on the selected traits.\nUser Interaction: Reaction buttons for ‘like’ 👍, ‘dislike’ 👎, and ‘regenerate’ 🔄 will be implemented to allow users to interact with the generated character. This will provide immediate feedback mechanisms for the community.\nTesting and Iteration: The bot will be deployed in a controlled Discord environment and tested by real users. Their feedback will be crucial for refining the bot’s functionality and user experience.\nDocumentation: All development processes, user interactions, and iterations will be thoroughly documented. This documentation will be critical for understanding user needs and will inform future development cycles.\n\nThis PoC will serve to validate the core idea, engage the user community early in the development process, and provide critical insights for scaling the bot to handle more complex trait manipulation and 3D character rendering in future phases."
+    "text": "Improved Performance: Multi-threading allows for background resource loading, enhancing application responsiveness.\nBetter User Experience: Smooth audio playback and faster load times contribute to a more seamless user experience."
   },
   {
-    "objectID": "decisions/20231109-discord-polygonjs-generator.html#the-upside",
-    "href": "decisions/20231109-discord-polygonjs-generator.html#the-upside",
-    "title": "Proposed: Character Customization Discord Bot PoC for V-Sekai",
+    "objectID": "decisions/20240710-use-godot-engine-web-threaded.html#the-downsides",
+    "href": "decisions/20240710-use-godot-engine-web-threaded.html#the-downsides",
+    "title": "Proposed: Use Godot Engine Web Threaded",
     "section": "",
-    "text": "Implementing this bot will potentially increase community engagement by providing a fun and interactive character creation tool. It will also lay the foundation for future developments in VR and character design within the V-Sekai ecosystem."
+    "text": "Complexity: Implementing multi-threading can introduce complexity and potential bugs.\nBrowser Compatibility: Ensuring full browser support for multi-threaded features may require additional effort."
   },
   {
-    "objectID": "decisions/20231109-discord-polygonjs-generator.html#the-downside",
-    "href": "decisions/20231109-discord-polygonjs-generator.html#the-downside",
-    "title": "Proposed: Character Customization Discord Bot PoC for V-Sekai",
+    "objectID": "decisions/20240710-use-godot-engine-web-threaded.html#the-road-not-taken",
+    "href": "decisions/20240710-use-godot-engine-web-threaded.html#the-road-not-taken",
+    "title": "Proposed: Use Godot Engine Web Threaded",
     "section": "",
-    "text": "The initial development of the bot may require significant resources and there is a risk of low user adoption. Additionally, ensuring the bot’s scalability and handling user feedback for improvements could be challenging."
+    "text": "Alternative approaches such as sticking with single-threaded implementations were considered but ultimately deemed less effective for handling large resources."
   },
   {
-    "objectID": "decisions/20231109-discord-polygonjs-generator.html#the-road-not-taken",
-    "href": "decisions/20231109-discord-polygonjs-generator.html#the-road-not-taken",
-    "title": "Proposed: Character Customization Discord Bot PoC for V-Sekai",
+    "objectID": "decisions/20240710-use-godot-engine-web-threaded.html#the-infrequent-use-case",
+    "href": "decisions/20240710-use-godot-engine-web-threaded.html#the-infrequent-use-case",
+    "title": "Proposed: Use Godot Engine Web Threaded",
     "section": "",
-    "text": "Alternatives, such as outsourcing the tool or purchasing an existing solution, were considered but ultimately rejected in favor of in-house development to retain creative control and better integration with V-Sekai’s infrastructure."
+    "text": "In cases where the application does not involve large resources or complex audio processing, single-threaded implementation might suffice."
   },
   {
-    "objectID": "decisions/20231109-discord-polygonjs-generator.html#the-infrequent-use-case",
-    "href": "decisions/20231109-discord-polygonjs-generator.html#the-infrequent-use-case",
-    "title": "Proposed: Character Customization Discord Bot PoC for V-Sekai",
+    "objectID": "decisions/20240710-use-godot-engine-web-threaded.html#in-core-and-done-by-us",
+    "href": "decisions/20240710-use-godot-engine-web-threaded.html#in-core-and-done-by-us",
+    "title": "Proposed: Use Godot Engine Web Threaded",
     "section": "",
-    "text": "There might be less frequent use cases for the bot, such as character customization for one-time events or non-regular users. The bot’s design will need to account for these to ensure it remains relevant and accessible."
+    "text": "This proposal aligns with our core values of efficiency and performance and will be implemented by our team."
   },
   {
-    "objectID": "decisions/20231109-discord-polygonjs-generator.html#in-core-and-done-by-us",
-    "href": "decisions/20231109-discord-polygonjs-generator.html#in-core-and-done-by-us",
-    "title": "Proposed: Character Customization Discord Bot PoC for V-Sekai",
+    "objectID": "decisions/20240710-use-godot-engine-web-threaded.html#status",
+    "href": "decisions/20240710-use-godot-engine-web-threaded.html#status",
+    "title": "Proposed: Use Godot Engine Web Threaded",
     "section": "",
-    "text": "The core functionality of the bot aligns with V-Sekai’s objectives and values. The development will be handled internally to ensure the tool’s compatibility with the community’s needs and expectations."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20231109-discord-polygonjs-generator.html#further-reading",
-    "href": "decisions/20231109-discord-polygonjs-generator.html#further-reading",
-    "title": "Proposed: Character Customization Discord Bot PoC for V-Sekai",
+    "objectID": "decisions/20240710-use-godot-engine-web-threaded.html#decision-makers",
+    "href": "decisions/20240710-use-godot-engine-web-threaded.html#decision-makers",
+    "title": "Proposed: Use Godot Engine Web Threaded",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nV-Sekai Official Website - Community of enthusiasts building a next-generation social and gaming VR platform powered by the Godot Engine 4.0\nNousResearch Yarn Mistral 7b 128k - Hugging Face - A Hugging Face Space by realgenius\nIssue #68 · polygonjs/polygonjs - GitHub - Discussion on using polygon.js as a Discord webhook watcher to output messages and attachments\n\nThis article was assisted by AI."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20211005-we-want-to-proxy-udp-datagrams-at-production-quality-of-service.html",
-    "href": "decisions/20211005-we-want-to-proxy-udp-datagrams-at-production-quality-of-service.html",
-    "title": "Proposed: We want to proxy udp datagrams at production quality of service.",
+    "objectID": "decisions/20240710-use-godot-engine-web-threaded.html#tags",
+    "href": "decisions/20240710-use-godot-engine-web-threaded.html#tags",
+    "title": "Proposed: Use Godot Engine Web Threaded",
     "section": "",
-    "text": "Proposed: We want to proxy udp datagrams at production quality of service.\n\nContext and Problem Statement\nWe want to proxy udp datagrams at production quality of service.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nThe ability to proxy V-Sekai game datagrams is an important part of the player experience.\nWe require that the proxy is able to handle both versions of DTLS inside of WebRTC and also with ENET.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nNo idea.\n\nWIP\n\nWireGuard in Cilium allows mesh kubernetes clustering\n\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNetworking and game networking are not a few lines of code. Game networking is game specific and the quality matters.\n\n\nPositive Consequences\n\nAllows greater access to potential users.\nWeb browser support requires webrtc.\n\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nWe own game networking.\n\n\nReferences\n\nhttps://github.com/yyyar/gobetween\nhttps://ebpf.io/\nhttps://cilium.io/\nhttps://docs.cilium.io/en/stable/gettingstarted/encryption-wireguard/\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20210811-min-spec-v-sekai.html",
-    "href": "decisions/20210811-min-spec-v-sekai.html",
-    "title": "Proposed: Minimum Specification V-Sekai Hardware",
+    "objectID": "decisions/20240710-use-godot-engine-web-threaded.html#further-reading",
+    "href": "decisions/20240710-use-godot-engine-web-threaded.html#further-reading",
+    "title": "Proposed: Use Godot Engine Web Threaded",
     "section": "",
-    "text": "Proposed: Minimum Specification V-Sekai Hardware\n\nContext and Problem Statement\nTags: hardware proxy, minimum spec,\nWe want to create standardized performance numbers for V-Sekai.\nPerformance targets:\n\nAchieve 16.67 milliseconds (60 FPS) frame time on a 4k screen for V-Sekai in desktop flat mode.\nThe 16.67 milliseconds target should be achieved smoothly and not as the average.\nFrom the Steam Hardware Survey (July 2021) accessed on August 2021, there are 25% of gamers who have a maximum of 8 gigabytes of ram.\n\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nWe want to create a standard test platform for V-Sekai to get performance data.\n\nCanonical test/reference hardware by platform (desktop-flat, desktop-vr, mobile-vr)\nCanonical content by platform (avatar+map): both low end (Mozilla Hubs + static avatars) and mid-end and high-end\n\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nSpecify a minimum specification.\n\nSingle Board Computers UDOO BOLT GEAR - kit based on UDOOBOLT V8 with metallic case.\n\nThis is the computer we think is the most similar to a Valve Steamdeck.\n\nSolid State Drives - SSD 1 TB\nSolid State Drive - OS Drive (Size TBD)\nMemory Modules “NCNR” 260pin SODIMM ECC DDR4 2666 16GB1.2v 1Gx8(0-85) We use ECC to during testing avoid “Godbolts” from the universe.\nWindows 10 operating system Windows 10 is what typical PCVR uses.\nPopos! 20.04 operating system Popos! Linux is similar to the Arch Linux that Steam Deck uses.\n\nUse a scripted fly through demo.\n\nhttps://github.com/Calinou/godot-cmvalley\nhttps://github.com/TokageItLab/3d-platform-test-for-godot4\nAn animated camera can be exported from Blender.\nRecord performance data in .res format and also json.\nRecord OBS videos of the fly through with frametime and stats.\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot coding related.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\n\nOnly represent AMD APUs.\nHardware is fairly new. Only a few years old.\nSteam Deck uses quad-channel DDR5 instead of dual-channel DDR4, and also DLNA2 instead of Vega graphics\n\n\n\nIs there a reason why this should be core and done by us?\nAs a platform holder, it would be our responsibility to understand the limits of the platform.\n\n\nReferences\n\nUDOO Bolt datasheet_udoo_bolt_gear-1947342.pdf\nMouser Electronics Canada V-Sekai Platform.pdf\nhttps://developer.oculus.com/documentation/unity/unity-perf/\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20221019-networking-100000-entities-ownership.html",
-    "href": "decisions/20221019-networking-100000-entities-ownership.html",
-    "title": "Proposed: Networking with 100000 Entities and Ownership (Revision 2)",
+    "objectID": "decisions/20231225-mesh-transformer-facial-features.html",
+    "href": "decisions/20231225-mesh-transformer-facial-features.html",
+    "title": "Proposed: Mesh Transformer Expressive Facial Features",
     "section": "",
-    "text": "Status: proposed \nDeciders: V-Sekai,\nTags: V-Sekai, Networking\n\n\n\nIn short, replication of state while permitting object ownership to transfer, at scale.\n\n\n\nIf we go with a model in which objects have one of three policies:\n\nDeny\nAsk Master\nAllow always (synchronous replication)\n\nWe want to ensure various guarantees in each case.\n\nThere is no problem\nWe will delay sync by 1 round trip, so there is no problem because everything is synchronized against the master.\nWe will follow a “last-write wins” strategy from the perspective of the relay server responsible for mastership.\n\nOther relays only need to know which server owns each object (and possibly the ownership / mastership table), and where each entity is.\nHaving this constraint permits us to use a model where we do not need consistent and transactional global information about object ownership, which allows the system to be simpler.\nIdea of separation of presence queries (who is here, reliably, tricky to figure out who of 100000 clients is relevant?) from realtime networking sync, which can flow directly from relay to relay, degrading over distance.\n\n\n\nNone yet. We may try prototyping this type of system in multiple ways.\n\n\n\nThis keeps low latency but reduces the needed bandwidth to sync 100,000 entities.\nNapkin math:\n50 bytes per frame per object * 100,000 objects = 5MB per frame.\n5MB/frame * 20 fps = 100MB = 1Gbps\nIf we send updates of all objects to all objects, that requires 100Tb/s\n\n&gt; yea 100k users at once is impossible any way you put it. I think a realistic goal is 1k, as like, our max goal\n\nRight, so you would need to not send updates for far away objects\n\nOnly send 1000 closest objects: 1Tb/s\n\n+ Send faraway objects at 2Hz: 100Gb/s\n\n+ Heavy delta compression: 10Gb/s\n\nThis is for all players\n\nThie means, in a hypothetical universe where distant objects only need position sync, a server with 10Gb/s NIC could theoretically run 100,000 concurrent users, if optimizzed!\n\nAlso, therefore, per player bandwidth **of distant objects** would be 100Kbit/s of downstream data, which is pretty small.\n\nAgain I haven't accounted for IK synchronization, or for additional nearby objects, so it could be higher here.\nNearby objects is a smaller problem and easier to solve, and belongs in a separate proposal.\n\n\n\nWe may be overcomplicating a problem that doesn’t need to be solved yet. Pure interest management may be sufficient, and we do not currently have this many users.\n\n\n\n\n\n\n\n\n\n\n\n\nSource:\nDiscord VC with Malek and iFire\nDiscord channel forum-v-sekai “Networking with librg” thread: https://discord.com/channels/471446618156040210/1031379649776848900/1032401929587929208\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, first rank\n\n\n\n\nVirtual Reality (VR) is a rapidly evolving field, with new technologies and techniques being developed constantly. One of the key areas of focus in VR development is creating realistic and expressive avatars. This is where Mesh Transformers comes into play.\n\n\n\nThe challenge lies in enhancing non-verbal communication in virtual reality by generating diverse facial structures and features that are expressive yet efficient in terms of polygon count. This includes creating a variety of facial shapes, eye configurations, nose shapes, and mouth designs.\n\n\n\nThe strategy is to employ Mesh Transformers to generate these facial features. The aim is to offer a range of facial features that can later be animated or rigged for various expressions, greatly enriching the social and emotional dynamics of VR experiences.\n\n\n\nThe upside is the creation of more immersive and engaging virtual environments, with avatars that can express a wide range of emotions and reactions.\n\n\n\nThe downside could be the potential increase in complexity and computational requirements due to the addition of more detailed and expressive facial features.\n\n\n\nAn alternative approach could have been to use simpler, less expressive avatar designs. However, this would limit the range of non-verbal communication possible in VR environments.\n\n\n\nIn cases where VR environments are used for simple tasks or interactions, the need for highly expressive avatars may not be as high.\n\n\n\nYes, this proposal is core to our mission of enhancing VR experiences and will be implemented by our team.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20221019-networking-100000-entities-ownership.html#context-and-problem-statement",
-    "href": "decisions/20221019-networking-100000-entities-ownership.html#context-and-problem-statement",
-    "title": "Proposed: Networking with 100000 Entities and Ownership (Revision 2)",
+    "objectID": "decisions/20231225-mesh-transformer-facial-features.html#metadata",
+    "href": "decisions/20231225-mesh-transformer-facial-features.html#metadata",
+    "title": "Proposed: Mesh Transformer Expressive Facial Features",
     "section": "",
-    "text": "In short, replication of state while permitting object ownership to transfer, at scale."
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, first rank"
   },
   {
-    "objectID": "decisions/20221019-networking-100000-entities-ownership.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20221019-networking-100000-entities-ownership.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: Networking with 100000 Entities and Ownership (Revision 2)",
+    "objectID": "decisions/20231225-mesh-transformer-facial-features.html#the-backdrop",
+    "href": "decisions/20231225-mesh-transformer-facial-features.html#the-backdrop",
+    "title": "Proposed: Mesh Transformer Expressive Facial Features",
     "section": "",
-    "text": "If we go with a model in which objects have one of three policies:\n\nDeny\nAsk Master\nAllow always (synchronous replication)\n\nWe want to ensure various guarantees in each case.\n\nThere is no problem\nWe will delay sync by 1 round trip, so there is no problem because everything is synchronized against the master.\nWe will follow a “last-write wins” strategy from the perspective of the relay server responsible for mastership.\n\nOther relays only need to know which server owns each object (and possibly the ownership / mastership table), and where each entity is.\nHaving this constraint permits us to use a model where we do not need consistent and transactional global information about object ownership, which allows the system to be simpler.\nIdea of separation of presence queries (who is here, reliably, tricky to figure out who of 100000 clients is relevant?) from realtime networking sync, which can flow directly from relay to relay, degrading over distance."
+    "text": "Virtual Reality (VR) is a rapidly evolving field, with new technologies and techniques being developed constantly. One of the key areas of focus in VR development is creating realistic and expressive avatars. This is where Mesh Transformers comes into play."
   },
   {
-    "objectID": "decisions/20221019-networking-100000-entities-ownership.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20221019-networking-100000-entities-ownership.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Networking with 100000 Entities and Ownership (Revision 2)",
+    "objectID": "decisions/20231225-mesh-transformer-facial-features.html#the-challenge",
+    "href": "decisions/20231225-mesh-transformer-facial-features.html#the-challenge",
+    "title": "Proposed: Mesh Transformer Expressive Facial Features",
     "section": "",
-    "text": "None yet. We may try prototyping this type of system in multiple ways."
+    "text": "The challenge lies in enhancing non-verbal communication in virtual reality by generating diverse facial structures and features that are expressive yet efficient in terms of polygon count. This includes creating a variety of facial shapes, eye configurations, nose shapes, and mouth designs."
   },
   {
-    "objectID": "decisions/20221019-networking-100000-entities-ownership.html#positive-consequences",
-    "href": "decisions/20221019-networking-100000-entities-ownership.html#positive-consequences",
-    "title": "Proposed: Networking with 100000 Entities and Ownership (Revision 2)",
+    "objectID": "decisions/20231225-mesh-transformer-facial-features.html#the-strategy",
+    "href": "decisions/20231225-mesh-transformer-facial-features.html#the-strategy",
+    "title": "Proposed: Mesh Transformer Expressive Facial Features",
     "section": "",
-    "text": "This keeps low latency but reduces the needed bandwidth to sync 100,000 entities.\nNapkin math:\n50 bytes per frame per object * 100,000 objects = 5MB per frame.\n5MB/frame * 20 fps = 100MB = 1Gbps\nIf we send updates of all objects to all objects, that requires 100Tb/s\n\n&gt; yea 100k users at once is impossible any way you put it. I think a realistic goal is 1k, as like, our max goal\n\nRight, so you would need to not send updates for far away objects\n\nOnly send 1000 closest objects: 1Tb/s\n\n+ Send faraway objects at 2Hz: 100Gb/s\n\n+ Heavy delta compression: 10Gb/s\n\nThis is for all players\n\nThie means, in a hypothetical universe where distant objects only need position sync, a server with 10Gb/s NIC could theoretically run 100,000 concurrent users, if optimizzed!\n\nAlso, therefore, per player bandwidth **of distant objects** would be 100Kbit/s of downstream data, which is pretty small.\n\nAgain I haven't accounted for IK synchronization, or for additional nearby objects, so it could be higher here.\nNearby objects is a smaller problem and easier to solve, and belongs in a separate proposal."
+    "text": "The strategy is to employ Mesh Transformers to generate these facial features. The aim is to offer a range of facial features that can later be animated or rigged for various expressions, greatly enriching the social and emotional dynamics of VR experiences."
   },
   {
-    "objectID": "decisions/20221019-networking-100000-entities-ownership.html#negative-consequences",
-    "href": "decisions/20221019-networking-100000-entities-ownership.html#negative-consequences",
-    "title": "Proposed: Networking with 100000 Entities and Ownership (Revision 2)",
+    "objectID": "decisions/20231225-mesh-transformer-facial-features.html#the-upside",
+    "href": "decisions/20231225-mesh-transformer-facial-features.html#the-upside",
+    "title": "Proposed: Mesh Transformer Expressive Facial Features",
     "section": "",
-    "text": "We may be overcomplicating a problem that doesn’t need to be solved yet. Pure interest management may be sufficient, and we do not currently have this many users."
+    "text": "The upside is the creation of more immersive and engaging virtual environments, with avatars that can express a wide range of emotions and reactions."
   },
   {
-    "objectID": "decisions/20221019-networking-100000-entities-ownership.html#references",
-    "href": "decisions/20221019-networking-100000-entities-ownership.html#references",
-    "title": "Proposed: Networking with 100000 Entities and Ownership (Revision 2)",
+    "objectID": "decisions/20231225-mesh-transformer-facial-features.html#the-downside",
+    "href": "decisions/20231225-mesh-transformer-facial-features.html#the-downside",
+    "title": "Proposed: Mesh Transformer Expressive Facial Features",
     "section": "",
-    "text": "Source:\nDiscord VC with Malek and iFire\nDiscord channel forum-v-sekai “Networking with librg” thread: https://discord.com/channels/471446618156040210/1031379649776848900/1032401929587929208"
+    "text": "The downside could be the potential increase in complexity and computational requirements due to the addition of more detailed and expressive facial features."
   },
   {
-    "objectID": "decisions/20221019-networking-100000-entities-ownership.html#license-of-the-contribution",
-    "href": "decisions/20221019-networking-100000-entities-ownership.html#license-of-the-contribution",
-    "title": "Proposed: Networking with 100000 Entities and Ownership (Revision 2)",
+    "objectID": "decisions/20231225-mesh-transformer-facial-features.html#the-road-not-taken",
+    "href": "decisions/20231225-mesh-transformer-facial-features.html#the-road-not-taken",
+    "title": "Proposed: Mesh Transformer Expressive Facial Features",
     "section": "",
-    "text": "Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "An alternative approach could have been to use simpler, less expressive avatar designs. However, this would limit the range of non-verbal communication possible in VR environments."
   },
   {
-    "objectID": "decisions/20210707-transfer-animations-by-baking-reset.html",
-    "href": "decisions/20210707-transfer-animations-by-baking-reset.html",
-    "title": "Proposed: Transfer animation by baking reset",
+    "objectID": "decisions/20231225-mesh-transformer-facial-features.html#the-infrequent-use-case",
+    "href": "decisions/20231225-mesh-transformer-facial-features.html#the-infrequent-use-case",
+    "title": "Proposed: Mesh Transformer Expressive Facial Features",
     "section": "",
-    "text": "Given two animations .glbs in gltf, you cannot transfer the animation between the same character in different files in some cases.\nFixes: https://github.com/godotengine/godot/issues/50212\nWe are NOT retargeting between different rigs in the RESET baker stage.\nWe are NOT defining how to generate the RESET #animation in this proposal.\n\n\nWe want to transfer #animation between exact scenes with the same matching RESET animation.\nWe can import unlimited motion capture #animation to use if we can enforce a certain T-POSE and ensure the rigs are corresponding.\nMultiple different specifications exist on bone rolls on specific bone names. If the skeleton matches one of them, we can use that set of rig animations.\n\n\n\n\nWe bake the RESET #animation and then set it to identity so that rigs with corresponding RESET #animation can have their #animation transferred.\n\n\n\n\n\n\nImport a new scene with animations.\nA RESET #animation from the imported scene will automatically be baked to the skeleton.\nKey all RESET #animation frames to identity.\n\n\n\n\n\nPick an #animation frame time and click\nFirst bake any existing RESET animation.\nBake the RESET #animation\nEnsure that a RESET #animation track exists and is set to identity transform\n\n\n\n\n\nMake a tool that can take a human character and make it T-pose (A-pose?) and then save it to the RESET animation.\nEnforce bone rolls on the rig and then save it to the RESET animation.\nRoot motion centering (move to the origin) tool and then save it as the RESET animation.\nFilter the RESET axes when baking per animation.\n\n\n\n\n\nThis is a confusing problem and hard to explain. So the code to solve it is non-obvious to propose and non-trivial to discover.\n\n\n\n#animation are a core feature of Godot Engine.\n\n\n\n\nBone roll parent to child baking. https://github.com/V-Sekai/godot/commit/99a9f79e25f7760cb5a0990e67545d78e9dd0423\nImplementation: https://github.com/godot-extended-libraries/godot-fire/tree/feature/bake-reset-anim\nReference bone roll spec. https://tokage.info/lab/?id=5\nUse the entire surface of the mesh to match to the SMPL rig. (Siggraph 2021) https://github.com/PeizhuoLi/neural-blend-shapes/issues\nGuessing “Blender edit” https://github.com/KhronosGroup/glTF-Blender-IO/pull/941\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "In cases where VR environments are used for simple tasks or interactions, the need for highly expressive avatars may not be as high."
   },
   {
-    "objectID": "decisions/20210707-transfer-animations-by-baking-reset.html#context-and-problem-statement",
-    "href": "decisions/20210707-transfer-animations-by-baking-reset.html#context-and-problem-statement",
-    "title": "Proposed: Transfer animation by baking reset",
+    "objectID": "decisions/20231225-mesh-transformer-facial-features.html#in-core-and-done-by-us",
+    "href": "decisions/20231225-mesh-transformer-facial-features.html#in-core-and-done-by-us",
+    "title": "Proposed: Mesh Transformer Expressive Facial Features",
     "section": "",
-    "text": "Given two animations .glbs in gltf, you cannot transfer the animation between the same character in different files in some cases.\nFixes: https://github.com/godotengine/godot/issues/50212\nWe are NOT retargeting between different rigs in the RESET baker stage.\nWe are NOT defining how to generate the RESET #animation in this proposal.\n\n\nWe want to transfer #animation between exact scenes with the same matching RESET animation.\nWe can import unlimited motion capture #animation to use if we can enforce a certain T-POSE and ensure the rigs are corresponding.\nMultiple different specifications exist on bone rolls on specific bone names. If the skeleton matches one of them, we can use that set of rig animations."
+    "text": "Yes, this proposal is core to our mission of enhancing VR experiences and will be implemented by our team."
   },
   {
-    "objectID": "decisions/20210707-transfer-animations-by-baking-reset.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20210707-transfer-animations-by-baking-reset.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: Transfer animation by baking reset",
+    "objectID": "decisions/20231225-mesh-transformer-facial-features.html#further-reading",
+    "href": "decisions/20231225-mesh-transformer-facial-features.html#further-reading",
+    "title": "Proposed: Mesh Transformer Expressive Facial Features",
     "section": "",
-    "text": "We bake the RESET #animation and then set it to identity so that rigs with corresponding RESET #animation can have their #animation transferred."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20210707-transfer-animations-by-baking-reset.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20210707-transfer-animations-by-baking-reset.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Transfer animation by baking reset",
+    "objectID": "decisions/20230811-punchline-reports.html",
+    "href": "decisions/20230811-punchline-reports.html",
+    "title": "Accepted: Punchline based reports",
     "section": "",
-    "text": "Import a new scene with animations.\nA RESET #animation from the imported scene will automatically be baked to the skeleton.\nKey all RESET #animation frames to identity.\n\n\n\n\n\nPick an #animation frame time and click\nFirst bake any existing RESET animation.\nBake the RESET #animation\nEnsure that a RESET #animation track exists and is set to identity transform\n\n\n\n\n\nMake a tool that can take a human character and make it T-pose (A-pose?) and then save it to the RESET animation.\nEnforce bone rolls on the rig and then save it to the RESET animation.\nRoot motion centering (move to the origin) tool and then save it as the RESET animation.\nFilter the RESET axes when baking per animation."
+    "text": "Status: proposed \nDeciders: V-Sekai, fire\nTags: V-Sekai\n\n\n\n\nCommunication and project management within your game development team can be better.\n\n\n\nUsing the reverse reporting style in game development, the project manager gets the most important information first, followed by supporting details.\n\n\n\n\n\nThis is where you present the facts related to the game development process. For example:\n\"The AI behavior for enemy characters wasn't completed on time, and we didn't start the level design for Stage 3 as planned.\"\nor\n\"Completed the character modeling as scheduled.\"\n\n\n\nIn this step, you explain how the punch line affects the game development project. For instance:\n\"Because of the incomplete AI behavior, the game testing has been delayed by a week.\"\n\n\n\nHere, you propose solutions to the problem if there are any. An example could be:\n\"I will be able to complete the AI behavior in the next four days but the level design for Stage 3 will still be behind schedule.\"\n\n\n\nFinally, you provide the reasons behind the punch line. This is where you can give a detailed account of why things happened the way they did. For example:\n\"Three days' delay in AI behavior is due to an unexpected bug in the pathfinding system, and the remaining delay is due to being called to assist the graphics team with texture optimization.\"\n\n\n\n\nThe upside of this strategy is that it allows for clear and concise communication within the team. It ensures that everyone is aware of the current status of the project and what needs to be done moving forward.\n\n\n\nThe downside is that it requires all team members to be diligent in their reporting. If someone fails to accurately report their progress or issues, it could lead to miscommunication and delays in the project.\n\n\n\nAn alternative approach could have been to use traditional reporting methods, where each team member provides a detailed report of their work. However, this method can often lead to information overload and important details may get lost in the process.\n\n\n\nThis strategy may not be as effective in smaller teams or projects where communication is more direct and less formal.\n\n\n\nYes, this strategy should be implemented by us as it aligns with our goal of improving communication and project management within the team.\n\n\n\n\nV-Sekai\nI’m OK; The Bull Is Dead\nThis article is assisted by AI."
   },
   {
-    "objectID": "decisions/20210707-transfer-animations-by-baking-reset.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20210707-transfer-animations-by-baking-reset.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Transfer animation by baking reset",
+    "objectID": "decisions/20230811-punchline-reports.html#metadata",
+    "href": "decisions/20230811-punchline-reports.html#metadata",
+    "title": "Accepted: Punchline based reports",
     "section": "",
-    "text": "This is a confusing problem and hard to explain. So the code to solve it is non-obvious to propose and non-trivial to discover."
+    "text": "Status: proposed \nDeciders: V-Sekai, fire\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20210707-transfer-animations-by-baking-reset.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20210707-transfer-animations-by-baking-reset.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Transfer animation by baking reset",
+    "objectID": "decisions/20230811-punchline-reports.html#the-backdrop",
+    "href": "decisions/20230811-punchline-reports.html#the-backdrop",
+    "title": "Accepted: Punchline based reports",
     "section": "",
-    "text": "#animation are a core feature of Godot Engine."
+    "text": "Communication and project management within your game development team can be better."
   },
   {
-    "objectID": "decisions/20210707-transfer-animations-by-baking-reset.html#references",
-    "href": "decisions/20210707-transfer-animations-by-baking-reset.html#references",
-    "title": "Proposed: Transfer animation by baking reset",
+    "objectID": "decisions/20230811-punchline-reports.html#the-challenge",
+    "href": "decisions/20230811-punchline-reports.html#the-challenge",
+    "title": "Accepted: Punchline based reports",
     "section": "",
-    "text": "Bone roll parent to child baking. https://github.com/V-Sekai/godot/commit/99a9f79e25f7760cb5a0990e67545d78e9dd0423\nImplementation: https://github.com/godot-extended-libraries/godot-fire/tree/feature/bake-reset-anim\nReference bone roll spec. https://tokage.info/lab/?id=5\nUse the entire surface of the mesh to match to the SMPL rig. (Siggraph 2021) https://github.com/PeizhuoLi/neural-blend-shapes/issues\nGuessing “Blender edit” https://github.com/KhronosGroup/glTF-Blender-IO/pull/941"
+    "text": "Using the reverse reporting style in game development, the project manager gets the most important information first, followed by supporting details."
   },
   {
-    "objectID": "decisions/20210707-transfer-animations-by-baking-reset.html#derivative-license",
-    "href": "decisions/20210707-transfer-animations-by-baking-reset.html#derivative-license",
-    "title": "Proposed: Transfer animation by baking reset",
+    "objectID": "decisions/20230811-punchline-reports.html#the-strategy",
+    "href": "decisions/20230811-punchline-reports.html#the-strategy",
+    "title": "Accepted: Punchline based reports",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "This is where you present the facts related to the game development process. For example:\n\"The AI behavior for enemy characters wasn't completed on time, and we didn't start the level design for Stage 3 as planned.\"\nor\n\"Completed the character modeling as scheduled.\"\n\n\n\nIn this step, you explain how the punch line affects the game development project. For instance:\n\"Because of the incomplete AI behavior, the game testing has been delayed by a week.\"\n\n\n\nHere, you propose solutions to the problem if there are any. An example could be:\n\"I will be able to complete the AI behavior in the next four days but the level design for Stage 3 will still be behind schedule.\"\n\n\n\nFinally, you provide the reasons behind the punch line. This is where you can give a detailed account of why things happened the way they did. For example:\n\"Three days' delay in AI behavior is due to an unexpected bug in the pathfinding system, and the remaining delay is due to being called to assist the graphics team with texture optimization.\""
   },
   {
-    "objectID": "decisions/20240120-vr-armature-system.html",
-    "href": "decisions/20240120-vr-armature-system.html",
-    "title": "Proposed: Advanced VR Armature System for V-Sekai",
+    "objectID": "decisions/20230811-punchline-reports.html#the-upside",
+    "href": "decisions/20230811-punchline-reports.html#the-upside",
+    "title": "Accepted: Punchline based reports",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai Core Team\nTags: Virtual Reality, Rigging, Animation, IK Systems, Development\n\n\n\n\nThe V-Sekai community needs better rigging and animation tools specifically tailored for VR. The goal is to move beyond the current limitations of traditional approaches.\n\n\n\nDevelop an intuitive inverse kinematics (IK) system for VR avatars that removes the need for numerical input, enhancing the user experience.\n\n\n\nThe proposed VR Armature System includes:\n\nHandles designed for VR interaction.\nVisual indicators for joint movement ranges.\nStraightforward adjustment methods without requiring numbers.\n\n\n\n\n\nHandle Control Design:\n\nCraft VR-appropriate ergonomic handles.\nTrack VR controller for handle interaction.\n\nVisual Indicator Development:\n\nVisualize joint limits.\nUpdate indicators with joint movement.\n\nIK Solver Integration:\n\nEmploy IK solver for joint positioning.\nValidate across different avatar models.\n\nInterface & Interaction:\n\nInterface design for easy joint manipulation.\nImplement feedback for joint limit reach.\n\nTesting & Debugging:\n\nUser testing for intuitive use.\nRefine system via user feedback.\n\nSystem Finalization:\n\nEstablish final iteration post-testing.\nOptimize for VR performance.\n\nDocumentation & Training:\n\nProduce user guides and tutorials.\nConduct capability and usage training sessions.\n\n\n\n\n\nImplementing this system aims to improve the creation process in VR and establish V-Sekai as a cutting-edge developer of VR tools.\n\n\n\nThe introduction of a new system may require substantial resources and time for users to become familiar with it.\n\n\n\nOther options, like enhancing existing numerical controls or looking into traditional motion capture technologies, were considered but didn’t meet our immersive needs.\n\n\n\nWhile focused on VR, this system could also benefit animators using more conventional methods by providing improved interfaces and easier rig manipulation.\n\n\n\nIt’s crucial for V-Sekai to maintain this project to ensure it meets our quality standards and integrates seamlessly with our core technologies.\n\n\n\nFor insights into V-Sekai’s contributions to social VR in Godot Engine and our open-source work, please see:\n\nV-Sekai GitHub Repository\nV-Sekai Game Repository\n\nThis proposal was refined with assistance from Aria."
+    "text": "The upside of this strategy is that it allows for clear and concise communication within the team. It ensures that everyone is aware of the current status of the project and what needs to be done moving forward."
   },
   {
-    "objectID": "decisions/20240120-vr-armature-system.html#metadata",
-    "href": "decisions/20240120-vr-armature-system.html#metadata",
-    "title": "Proposed: Advanced VR Armature System for V-Sekai",
+    "objectID": "decisions/20230811-punchline-reports.html#the-downside",
+    "href": "decisions/20230811-punchline-reports.html#the-downside",
+    "title": "Accepted: Punchline based reports",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai Core Team\nTags: Virtual Reality, Rigging, Animation, IK Systems, Development"
+    "text": "The downside is that it requires all team members to be diligent in their reporting. If someone fails to accurately report their progress or issues, it could lead to miscommunication and delays in the project."
   },
   {
-    "objectID": "decisions/20240120-vr-armature-system.html#introduction",
-    "href": "decisions/20240120-vr-armature-system.html#introduction",
-    "title": "Proposed: Advanced VR Armature System for V-Sekai",
+    "objectID": "decisions/20230811-punchline-reports.html#the-road-not-taken",
+    "href": "decisions/20230811-punchline-reports.html#the-road-not-taken",
+    "title": "Accepted: Punchline based reports",
     "section": "",
-    "text": "The V-Sekai community needs better rigging and animation tools specifically tailored for VR. The goal is to move beyond the current limitations of traditional approaches."
+    "text": "An alternative approach could have been to use traditional reporting methods, where each team member provides a detailed report of their work. However, this method can often lead to information overload and important details may get lost in the process."
   },
   {
-    "objectID": "decisions/20240120-vr-armature-system.html#objective",
-    "href": "decisions/20240120-vr-armature-system.html#objective",
-    "title": "Proposed: Advanced VR Armature System for V-Sekai",
+    "objectID": "decisions/20230811-punchline-reports.html#the-infrequent-use-case",
+    "href": "decisions/20230811-punchline-reports.html#the-infrequent-use-case",
+    "title": "Accepted: Punchline based reports",
     "section": "",
-    "text": "Develop an intuitive inverse kinematics (IK) system for VR avatars that removes the need for numerical input, enhancing the user experience."
+    "text": "This strategy may not be as effective in smaller teams or projects where communication is more direct and less formal."
   },
   {
-    "objectID": "decisions/20240120-vr-armature-system.html#proposed-solution",
-    "href": "decisions/20240120-vr-armature-system.html#proposed-solution",
-    "title": "Proposed: Advanced VR Armature System for V-Sekai",
+    "objectID": "decisions/20230811-punchline-reports.html#in-core-and-done-by-us",
+    "href": "decisions/20230811-punchline-reports.html#in-core-and-done-by-us",
+    "title": "Accepted: Punchline based reports",
     "section": "",
-    "text": "The proposed VR Armature System includes:\n\nHandles designed for VR interaction.\nVisual indicators for joint movement ranges.\nStraightforward adjustment methods without requiring numbers."
+    "text": "Yes, this strategy should be implemented by us as it aligns with our goal of improving communication and project management within the team."
   },
   {
-    "objectID": "decisions/20240120-vr-armature-system.html#technical-implementation-steps",
-    "href": "decisions/20240120-vr-armature-system.html#technical-implementation-steps",
-    "title": "Proposed: Advanced VR Armature System for V-Sekai",
+    "objectID": "decisions/20230811-punchline-reports.html#further-reading",
+    "href": "decisions/20230811-punchline-reports.html#further-reading",
+    "title": "Accepted: Punchline based reports",
     "section": "",
-    "text": "Handle Control Design:\n\nCraft VR-appropriate ergonomic handles.\nTrack VR controller for handle interaction.\n\nVisual Indicator Development:\n\nVisualize joint limits.\nUpdate indicators with joint movement.\n\nIK Solver Integration:\n\nEmploy IK solver for joint positioning.\nValidate across different avatar models.\n\nInterface & Interaction:\n\nInterface design for easy joint manipulation.\nImplement feedback for joint limit reach.\n\nTesting & Debugging:\n\nUser testing for intuitive use.\nRefine system via user feedback.\n\nSystem Finalization:\n\nEstablish final iteration post-testing.\nOptimize for VR performance.\n\nDocumentation & Training:\n\nProduce user guides and tutorials.\nConduct capability and usage training sessions."
+    "text": "V-Sekai\nI’m OK; The Bull Is Dead\nThis article is assisted by AI."
   },
   {
-    "objectID": "decisions/20240120-vr-armature-system.html#benefits",
-    "href": "decisions/20240120-vr-armature-system.html#benefits",
-    "title": "Proposed: Advanced VR Armature System for V-Sekai",
+    "objectID": "decisions/20210529-performance-profiling.html",
+    "href": "decisions/20210529-performance-profiling.html",
+    "title": "Proposed: Performance profile the game with AMDuProf",
     "section": "",
-    "text": "Implementing this system aims to improve the creation process in VR and establish V-Sekai as a cutting-edge developer of VR tools."
+    "text": "How do we profile the game?\nThe context is for example importing files are slow (they’re not the biggest bottleneck anymore). What tools and techniques can we use?\n\n\n\nUse AMDuProf\n\n\n\nAMDuProf shows the slower functions and there’s also a callgraph and flamegraph feature.\nA callgraph is similar to a stacktrace.\nA flamegraph is a way of visualizing performance. The first link is an ACM article describing the design.\nThe workflow is for each item start from the top and go down.\n\n\n\n\nWorks for both Intel and AMD\nWorks on Windows 10 and Linux\n\n\n\n\n\nLess usable than superluminal\nSlower than superluminal\n\n\n\n\n\nOption: superluminal\nRejection reason:\n\nNot free\n\n\n\n\n\nNot applicable.\n\n\n\nNot in code. This is documenting a technique.\n\n\n\n\nhttps://queue.acm.org/detail.cfm?id=2927301\nhttps://superluminal.eu/\nhttps://developer.amd.com/amd-uprof\nhttp://www.brendangregg.com/flamegraphs.html\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240120-vr-armature-system.html#considerations",
-    "href": "decisions/20240120-vr-armature-system.html#considerations",
-    "title": "Proposed: Advanced VR Armature System for V-Sekai",
+    "objectID": "decisions/20210529-performance-profiling.html#context-and-problem-statement",
+    "href": "decisions/20210529-performance-profiling.html#context-and-problem-statement",
+    "title": "Proposed: Performance profile the game with AMDuProf",
     "section": "",
-    "text": "The introduction of a new system may require substantial resources and time for users to become familiar with it."
+    "text": "How do we profile the game?\nThe context is for example importing files are slow (they’re not the biggest bottleneck anymore). What tools and techniques can we use?"
   },
   {
-    "objectID": "decisions/20240120-vr-armature-system.html#alternatives-evaluated",
-    "href": "decisions/20240120-vr-armature-system.html#alternatives-evaluated",
-    "title": "Proposed: Advanced VR Armature System for V-Sekai",
+    "objectID": "decisions/20210529-performance-profiling.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20210529-performance-profiling.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: Performance profile the game with AMDuProf",
     "section": "",
-    "text": "Other options, like enhancing existing numerical controls or looking into traditional motion capture technologies, were considered but didn’t meet our immersive needs."
+    "text": "Use AMDuProf"
   },
   {
-    "objectID": "decisions/20240120-vr-armature-system.html#extended-applications",
-    "href": "decisions/20240120-vr-armature-system.html#extended-applications",
-    "title": "Proposed: Advanced VR Armature System for V-Sekai",
+    "objectID": "decisions/20210529-performance-profiling.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-andor-diagrams",
+    "href": "decisions/20210529-performance-profiling.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-andor-diagrams",
+    "title": "Proposed: Performance profile the game with AMDuProf",
     "section": "",
-    "text": "While focused on VR, this system could also benefit animators using more conventional methods by providing improved interfaces and easier rig manipulation."
+    "text": "AMDuProf shows the slower functions and there’s also a callgraph and flamegraph feature.\nA callgraph is similar to a stacktrace.\nA flamegraph is a way of visualizing performance. The first link is an ACM article describing the design.\nThe workflow is for each item start from the top and go down."
   },
   {
-    "objectID": "decisions/20240120-vr-armature-system.html#alignment-with-v-sekai",
-    "href": "decisions/20240120-vr-armature-system.html#alignment-with-v-sekai",
-    "title": "Proposed: Advanced VR Armature System for V-Sekai",
+    "objectID": "decisions/20210529-performance-profiling.html#positive-consequences",
+    "href": "decisions/20210529-performance-profiling.html#positive-consequences",
+    "title": "Proposed: Performance profile the game with AMDuProf",
     "section": "",
-    "text": "It’s crucial for V-Sekai to maintain this project to ensure it meets our quality standards and integrates seamlessly with our core technologies."
+    "text": "Works for both Intel and AMD\nWorks on Windows 10 and Linux"
   },
   {
-    "objectID": "decisions/20240120-vr-armature-system.html#resources",
-    "href": "decisions/20240120-vr-armature-system.html#resources",
-    "title": "Proposed: Advanced VR Armature System for V-Sekai",
+    "objectID": "decisions/20210529-performance-profiling.html#negative-consequences",
+    "href": "decisions/20210529-performance-profiling.html#negative-consequences",
+    "title": "Proposed: Performance profile the game with AMDuProf",
     "section": "",
-    "text": "For insights into V-Sekai’s contributions to social VR in Godot Engine and our open-source work, please see:\n\nV-Sekai GitHub Repository\nV-Sekai Game Repository\n\nThis proposal was refined with assistance from Aria."
+    "text": "Less usable than superluminal\nSlower than superluminal"
   },
   {
-    "objectID": "decisions/20231227-punchline-reports.html",
-    "href": "decisions/20231227-punchline-reports.html",
-    "title": "Proposed: Use the “Punchline Reports” Method",
+    "objectID": "decisions/20210529-performance-profiling.html#option-graveyard-same-as-above",
+    "href": "decisions/20210529-performance-profiling.html#option-graveyard-same-as-above",
+    "title": "Proposed: Performance profile the game with AMDuProf",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai, fire\nTags: V-Sekai\n\n\n\n\nThe article “I’m OK; The Bull Is Dead” from Computerworld discusses a method for reporting project status effectively. This method prioritizes delivering the most important information first, followed by supporting details.\n\n\n\nTraditional reporting styles often start with lengthy explanations which can delay the delivery of crucial information.\n\n\n\nImplement a four-step approach to reporting:\n\nStart with the punch line – the facts without adjectives or modifiers.\nDescribe the current status and how it affects the project.\nOutline the next steps or solutions.\nProvide an explanation or reason behind the punch line.\n\nThis approach is likened to the inverted pyramid style in journalism, where conclusions are presented first, followed by key facts, and then details.\n\n\n\n\nFaster delivery of crucial information.\nClearer understanding of the project status.\nMore effective communication within the team.\n\n\n\n\n\nMay require training or adjustment period for team members used to traditional reporting styles.\n\n\n\n\nContinuing with traditional reporting styles.\n\n\n\nThis method may not be suitable for projects where the context or background information is as important as the main facts.\n\n\n\nShould we decide to proceed, we will need to train our team on this new reporting method and adjust our project management tools accordingly.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\nI’m OK; The Bull Is Dead\n\nThis proposal was assisted by AI assistant, Aria."
+    "text": "Option: superluminal\nRejection reason:\n\nNot free"
   },
   {
-    "objectID": "decisions/20231227-punchline-reports.html#metadata",
-    "href": "decisions/20231227-punchline-reports.html#metadata",
-    "title": "Proposed: Use the “Punchline Reports” Method",
+    "objectID": "decisions/20210529-performance-profiling.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20210529-performance-profiling.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Performance profile the game with AMDuProf",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai, fire\nTags: V-Sekai"
+    "text": "Not applicable."
   },
   {
-    "objectID": "decisions/20231227-punchline-reports.html#context",
-    "href": "decisions/20231227-punchline-reports.html#context",
-    "title": "Proposed: Use the “Punchline Reports” Method",
+    "objectID": "decisions/20210529-performance-profiling.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20210529-performance-profiling.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Performance profile the game with AMDuProf",
     "section": "",
-    "text": "The article “I’m OK; The Bull Is Dead” from Computerworld discusses a method for reporting project status effectively. This method prioritizes delivering the most important information first, followed by supporting details."
+    "text": "Not in code. This is documenting a technique."
   },
   {
-    "objectID": "decisions/20231227-punchline-reports.html#problem",
-    "href": "decisions/20231227-punchline-reports.html#problem",
-    "title": "Proposed: Use the “Punchline Reports” Method",
+    "objectID": "decisions/20210529-performance-profiling.html#references",
+    "href": "decisions/20210529-performance-profiling.html#references",
+    "title": "Proposed: Performance profile the game with AMDuProf",
     "section": "",
-    "text": "Traditional reporting styles often start with lengthy explanations which can delay the delivery of crucial information."
+    "text": "https://queue.acm.org/detail.cfm?id=2927301\nhttps://superluminal.eu/\nhttps://developer.amd.com/amd-uprof\nhttp://www.brendangregg.com/flamegraphs.html"
   },
   {
-    "objectID": "decisions/20231227-punchline-reports.html#solution",
-    "href": "decisions/20231227-punchline-reports.html#solution",
-    "title": "Proposed: Use the “Punchline Reports” Method",
+    "objectID": "decisions/20210529-performance-profiling.html#derivative-license",
+    "href": "decisions/20210529-performance-profiling.html#derivative-license",
+    "title": "Proposed: Performance profile the game with AMDuProf",
     "section": "",
-    "text": "Implement a four-step approach to reporting:\n\nStart with the punch line – the facts without adjectives or modifiers.\nDescribe the current status and how it affects the project.\nOutline the next steps or solutions.\nProvide an explanation or reason behind the punch line.\n\nThis approach is likened to the inverted pyramid style in journalism, where conclusions are presented first, followed by key facts, and then details."
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20231227-punchline-reports.html#benefits",
-    "href": "decisions/20231227-punchline-reports.html#benefits",
-    "title": "Proposed: Use the “Punchline Reports” Method",
+    "objectID": "decisions/20230903-replicate-vrm-transform.html",
+    "href": "decisions/20230903-replicate-vrm-transform.html",
+    "title": "Rejected: Enabling VRM to Blender Conversion with Cloud GPUs and replicate.com",
     "section": "",
-    "text": "Faster delivery of crucial information.\nClearer understanding of the project status.\nMore effective communication within the team."
+    "text": "Status: rejected\nDeciders: V-Sekai, fire, antpb\nTags: V-Sekai\n\n\n\n\nThe VRM format is becoming increasingly popular in the field of 3D modeling and animation. It allows for easy sharing and transfer of humanoid 3D models with skeletal animations between different software applications. One such application is the Godot Engine, a popular open-source game engine.\n\n\n\nCurrently, developers working with VRM files in Godot Engine face difficulties when trying to convert these files to Blender format for further editing or manipulation. Manual conversion processes can be time-consuming and error-prone.\n\n\n\nThe proposed strategy for enabling VRM to Blender conversion involves leveraging the computational power of cloud GPUs provided by replicate.com. By running a GPU-accelerated Blender instance, developers can perform an identity operation on the VRM input, converting it to Blender format. This simplifies the process of converting VRM files to Blender format.\nTo convert VRM files to Blender format, developers can follow these steps:\n\nInstall the necessary libraries or plugins in Blender that support the VRM format.\nLeverage replicate.com’s infrastructure to spin up a GPU-accelerated Blender instance.\nDevelop a script or tool that takes the VRM file as input and sends it to the GPU-accelerated Blender instance via a REST interface.\nIn the GPU-accelerated Blender instance, use the installed libraries or plugins to perform the conversion from VRM to Blender format.\nAlso use Blender to perform the conversion from Blender to VRM/GLTF format.\n\nThis strategy streamlines the workflow for developers, saving time and improving collaboration between designers and developers. The use of cloud GPUs and replicate.com’s infrastructure ensures fast and efficient conversion processes.\nAdditionally, this strategy can also be extended to other software applications or websites that can utilize a REST interface, allowing developers working with VRM files to convert them to Blender format seamlessly, regardless of the software they are using.\n\n\n\n\nStreamlined workflow: Developers can easily convert VRM files to Blender format, opening up a wide range of editing and manipulation possibilities.\nTime-saving: The use of cloud GPUs and replicate.com’s infrastructure ensures fast and efficient conversion processes.\nImproved collaboration: The ability to work with VRM models in both Godot Engine and Blender facilitates collaboration between designers and developers.\n\n\n\n\n\nDevelopment effort and expertise: Creating the necessary library or plugin may require significant technical knowledge in both the Godot Engine and VRM format.\nCompatibility issues: Different versions of FBX or GLB files may introduce compatibility challenges during the conversion process.\nMaintenance challenges: Keeping up with future updates to the Godot Engine and VRM specifications may require ongoing effort.\n\n\n\n\nWe considered developing a web application, but it was deemed to have heavy engineering costs.\n\n\n\nWhile the proposed solution focuses on streamlining VRM to Blender conversion for the Godot Engine ecosystem, the same concept can be extended to other software applications or websites that can utilize a REST interface. This allows developers working with VRM files to convert them to Blender format seamlessly, regardless of the software they are using. The use of cloud GPUs and replicate.com’s infrastructure still ensures fast and efficient conversion processes.\n\n\n\nFire knows the way.\n\n\n\n\nV-Sekai\nVRM Animation Specification\nReplicate - Cloud GPU Toy\n\nThis article is assisted by AI.\nIs there anything else I can assist you with?"
   },
   {
-    "objectID": "decisions/20231227-punchline-reports.html#potential-drawbacks",
-    "href": "decisions/20231227-punchline-reports.html#potential-drawbacks",
-    "title": "Proposed: Use the “Punchline Reports” Method",
+    "objectID": "decisions/20230903-replicate-vrm-transform.html#metadata",
+    "href": "decisions/20230903-replicate-vrm-transform.html#metadata",
+    "title": "Rejected: Enabling VRM to Blender Conversion with Cloud GPUs and replicate.com",
     "section": "",
-    "text": "May require training or adjustment period for team members used to traditional reporting styles."
+    "text": "Status: rejected\nDeciders: V-Sekai, fire, antpb\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20231227-punchline-reports.html#alternatives-considered",
-    "href": "decisions/20231227-punchline-reports.html#alternatives-considered",
-    "title": "Proposed: Use the “Punchline Reports” Method",
+    "objectID": "decisions/20230903-replicate-vrm-transform.html#the-backdrop",
+    "href": "decisions/20230903-replicate-vrm-transform.html#the-backdrop",
+    "title": "Rejected: Enabling VRM to Blender Conversion with Cloud GPUs and replicate.com",
     "section": "",
-    "text": "Continuing with traditional reporting styles."
+    "text": "The VRM format is becoming increasingly popular in the field of 3D modeling and animation. It allows for easy sharing and transfer of humanoid 3D models with skeletal animations between different software applications. One such application is the Godot Engine, a popular open-source game engine."
   },
   {
-    "objectID": "decisions/20231227-punchline-reports.html#rare-use-cases",
-    "href": "decisions/20231227-punchline-reports.html#rare-use-cases",
-    "title": "Proposed: Use the “Punchline Reports” Method",
+    "objectID": "decisions/20230903-replicate-vrm-transform.html#the-challenge",
+    "href": "decisions/20230903-replicate-vrm-transform.html#the-challenge",
+    "title": "Rejected: Enabling VRM to Blender Conversion with Cloud GPUs and replicate.com",
     "section": "",
-    "text": "This method may not be suitable for projects where the context or background information is as important as the main facts."
+    "text": "Currently, developers working with VRM files in Godot Engine face difficulties when trying to convert these files to Blender format for further editing or manipulation. Manual conversion processes can be time-consuming and error-prone."
   },
   {
-    "objectID": "decisions/20231227-punchline-reports.html#implementation",
-    "href": "decisions/20231227-punchline-reports.html#implementation",
-    "title": "Proposed: Use the “Punchline Reports” Method",
+    "objectID": "decisions/20230903-replicate-vrm-transform.html#the-strategy",
+    "href": "decisions/20230903-replicate-vrm-transform.html#the-strategy",
+    "title": "Rejected: Enabling VRM to Blender Conversion with Cloud GPUs and replicate.com",
     "section": "",
-    "text": "Should we decide to proceed, we will need to train our team on this new reporting method and adjust our project management tools accordingly."
+    "text": "The proposed strategy for enabling VRM to Blender conversion involves leveraging the computational power of cloud GPUs provided by replicate.com. By running a GPU-accelerated Blender instance, developers can perform an identity operation on the VRM input, converting it to Blender format. This simplifies the process of converting VRM files to Blender format.\nTo convert VRM files to Blender format, developers can follow these steps:\n\nInstall the necessary libraries or plugins in Blender that support the VRM format.\nLeverage replicate.com’s infrastructure to spin up a GPU-accelerated Blender instance.\nDevelop a script or tool that takes the VRM file as input and sends it to the GPU-accelerated Blender instance via a REST interface.\nIn the GPU-accelerated Blender instance, use the installed libraries or plugins to perform the conversion from VRM to Blender format.\nAlso use Blender to perform the conversion from Blender to VRM/GLTF format.\n\nThis strategy streamlines the workflow for developers, saving time and improving collaboration between designers and developers. The use of cloud GPUs and replicate.com’s infrastructure ensures fast and efficient conversion processes.\nAdditionally, this strategy can also be extended to other software applications or websites that can utilize a REST interface, allowing developers working with VRM files to convert them to Blender format seamlessly, regardless of the software they are using."
   },
   {
-    "objectID": "decisions/20231227-punchline-reports.html#references",
-    "href": "decisions/20231227-punchline-reports.html#references",
-    "title": "Proposed: Use the “Punchline Reports” Method",
+    "objectID": "decisions/20230903-replicate-vrm-transform.html#the-upside",
+    "href": "decisions/20230903-replicate-vrm-transform.html#the-upside",
+    "title": "Rejected: Enabling VRM to Blender Conversion with Cloud GPUs and replicate.com",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\nI’m OK; The Bull Is Dead\n\nThis proposal was assisted by AI assistant, Aria."
+    "text": "Streamlined workflow: Developers can easily convert VRM files to Blender format, opening up a wide range of editing and manipulation possibilities.\nTime-saving: The use of cloud GPUs and replicate.com’s infrastructure ensures fast and efficient conversion processes.\nImproved collaboration: The ability to work with VRM models in both Godot Engine and Blender facilitates collaboration between designers and developers."
   },
   {
-    "objectID": "decisions/20240611-lower-learning-rate.html",
-    "href": "decisions/20240611-lower-learning-rate.html",
-    "title": "Proposed: Switch learning rate to be lower.",
+    "objectID": "decisions/20230903-replicate-vrm-transform.html#the-downside",
+    "href": "decisions/20230903-replicate-vrm-transform.html#the-downside",
+    "title": "Rejected: Enabling VRM to Blender Conversion with Cloud GPUs and replicate.com",
     "section": "",
-    "text": "We are currently training a mesh transformer’s auto encoder.\n\n\n\nThe current learning rate might not be optimal for our training process. We need to find a way to adjust it dynamically based on the progress of the training.\n\n\n\nWe propose to monitor the reconstruction loss after each epoch. If the loss decreases by less than 0.004 per epoch, we switch the learning rate to 1e-4.\nNote: Don’t forget to change the load method that the model uses to load the model.\n\n\n\nBy adjusting the learning rate based on the progress of the training, we can potentially achieve better results and prevent overfitting.\n\n\n\nThis approach requires careful monitoring of the training process and might require additional computational resources.\n\n\n\nAn alternative could be to use a fixed learning rate throughout the training process. However, this might not yield optimal results.\n\n\n\nThis approach might not be suitable for all types of models or datasets.\n\n\n\nThis proposal is made by the V-Sekai development team and will be implemented by us.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "Development effort and expertise: Creating the necessary library or plugin may require significant technical knowledge in both the Godot Engine and VRM format.\nCompatibility issues: Different versions of FBX or GLB files may introduce compatibility challenges during the conversion process.\nMaintenance challenges: Keeping up with future updates to the Godot Engine and VRM specifications may require ongoing effort."
   },
   {
-    "objectID": "decisions/20240611-lower-learning-rate.html#the-context",
-    "href": "decisions/20240611-lower-learning-rate.html#the-context",
-    "title": "Proposed: Switch learning rate to be lower.",
+    "objectID": "decisions/20230903-replicate-vrm-transform.html#the-road-not-taken",
+    "href": "decisions/20230903-replicate-vrm-transform.html#the-road-not-taken",
+    "title": "Rejected: Enabling VRM to Blender Conversion with Cloud GPUs and replicate.com",
     "section": "",
-    "text": "We are currently training a mesh transformer’s auto encoder."
+    "text": "We considered developing a web application, but it was deemed to have heavy engineering costs."
   },
   {
-    "objectID": "decisions/20240611-lower-learning-rate.html#the-problem-statement",
-    "href": "decisions/20240611-lower-learning-rate.html#the-problem-statement",
-    "title": "Proposed: Switch learning rate to be lower.",
+    "objectID": "decisions/20230903-replicate-vrm-transform.html#the-infrequent-use-case",
+    "href": "decisions/20230903-replicate-vrm-transform.html#the-infrequent-use-case",
+    "title": "Rejected: Enabling VRM to Blender Conversion with Cloud GPUs and replicate.com",
     "section": "",
-    "text": "The current learning rate might not be optimal for our training process. We need to find a way to adjust it dynamically based on the progress of the training."
+    "text": "While the proposed solution focuses on streamlining VRM to Blender conversion for the Godot Engine ecosystem, the same concept can be extended to other software applications or websites that can utilize a REST interface. This allows developers working with VRM files to convert them to Blender format seamlessly, regardless of the software they are using. The use of cloud GPUs and replicate.com’s infrastructure still ensures fast and efficient conversion processes."
   },
   {
-    "objectID": "decisions/20240611-lower-learning-rate.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240611-lower-learning-rate.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Switch learning rate to be lower.",
+    "objectID": "decisions/20230903-replicate-vrm-transform.html#in-core-and-done-by-us",
+    "href": "decisions/20230903-replicate-vrm-transform.html#in-core-and-done-by-us",
+    "title": "Rejected: Enabling VRM to Blender Conversion with Cloud GPUs and replicate.com",
     "section": "",
-    "text": "We propose to monitor the reconstruction loss after each epoch. If the loss decreases by less than 0.004 per epoch, we switch the learning rate to 1e-4.\nNote: Don’t forget to change the load method that the model uses to load the model."
+    "text": "Fire knows the way."
   },
   {
-    "objectID": "decisions/20240611-lower-learning-rate.html#the-benefits",
-    "href": "decisions/20240611-lower-learning-rate.html#the-benefits",
-    "title": "Proposed: Switch learning rate to be lower.",
+    "objectID": "decisions/20230903-replicate-vrm-transform.html#further-reading",
+    "href": "decisions/20230903-replicate-vrm-transform.html#further-reading",
+    "title": "Rejected: Enabling VRM to Blender Conversion with Cloud GPUs and replicate.com",
     "section": "",
-    "text": "By adjusting the learning rate based on the progress of the training, we can potentially achieve better results and prevent overfitting."
+    "text": "V-Sekai\nVRM Animation Specification\nReplicate - Cloud GPU Toy\n\nThis article is assisted by AI.\nIs there anything else I can assist you with?"
   },
   {
-    "objectID": "decisions/20240611-lower-learning-rate.html#the-downsides",
-    "href": "decisions/20240611-lower-learning-rate.html#the-downsides",
-    "title": "Proposed: Switch learning rate to be lower.",
+    "objectID": "decisions/20211031-update-uro-for-godot-4.html",
+    "href": "decisions/20211031-update-uro-for-godot-4.html",
+    "title": "Proposed: Update URO for Godot 4",
     "section": "",
-    "text": "This approach requires careful monitoring of the training process and might require additional computational resources."
+    "text": "Proposed: Update URO for Godot 4\n\nContext and Problem Statement\nNeed a lobby server\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nUpdate URO for Godot 4.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nTo be determined.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot a few lines of script.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nWe can do it!\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240611-lower-learning-rate.html#the-road-not-taken",
-    "href": "decisions/20240611-lower-learning-rate.html#the-road-not-taken",
-    "title": "Proposed: Switch learning rate to be lower.",
+    "objectID": "decisions/20241014-basic-realtime-interaction.html",
+    "href": "decisions/20241014-basic-realtime-interaction.html",
+    "title": "Proposed: Basic Real-Time Interaction for Character and World Scenes",
     "section": "",
-    "text": "An alternative could be to use a fixed learning rate throughout the training process. However, this might not yield optimal results."
+    "text": "The project will enable users to interact in real-time by manipulating objects within a shared virtual environment, enhancing the user experience.\n\n\n\nI want to extend V-Sekai’s functionality to support real-time interaction with uploaded character and world scenes. This includes the ability for users to manipulate objects within the scene and have those changes reflected in real-time for other users connected to the same session. Additionally, seamless integration of new elements into the environment is crucial.\nHere’s a detailed breakdown of the features we plan to implement:\n\nReal-time Interaction: Users can move and rotate objects in the scene. Changes appear instantly, providing immediate visual feedback.\nNetworked Synchronization: When one user modifies something, the change is immediately visible to all other users in the same session.\nObject Persistence: Users can save their current scene setup to continue working on it later or retrieve it in another session.\nDynamic Environment Integration: Facilitate the introduction of new interactive elements during live sessions.\nMediator Role: A special user, called a mediator, can manage permissions like who can move what, start or end the session, and oversee interactions between users.\nLimited Scope: Initially, this feature will support multiple users interacting in one scene without additional complexities like handling multiple scenes or advanced physics.\n\nThis upgrade leverages the existing functionality of V-Sekai for uploading and rendering game engine assets. It assumes the utilization of V-Sekai’s current game engine and networking capabilities, or the integration of clearly specified, readily available libraries or services to achieve the desired real-time interaction and synchronization.\n\n\n\n\n\n[Scene Interaction Mock-up]\n+------------------------------------------------+\n|                                                |\n|  [User1]                                       |\n|    * (Object1) &lt;-- [Moving]                    |\n|                                                |\n|  [Tool Switcher Pie Menu]                      |\n|    - Move Tool                                 |\n|    - Rotate Tool                               |\n|    - Close                                     |\n|                                                |\n|  [User2]                                       |\n|    * (Object2)                                 |\n|                                                |\n+------------------------------------------------+\n\n\n\n\nEnhanced user engagement allows users to interact dynamically with objects, increasing the sense of presence. Establishing basic functionalities lays the foundation for future features that can include more complex interactions. Immediate feedback is crucial for collaborative environments, and intuitive tool selection through the Tool Switcher Pie Menu enhances workflow efficiency.\n\n\n\nThe initial features are limited to basic manipulations, which might not meet all user expectations. As the user base grows, the current simple synchronization mechanism may need significant enhancements.\n\n\n\nA full-scale interaction suite was initially considered, including scaling and advanced physics, but it was decided against due to complexity and resource constraints.\n\n\n\nWhile the system is designed for multiple users, it will also support single-user sessions, although this is not the primary focus.\n\n\n\nThis feature is core to the project’s mission of enhancing interactive capabilities and will be developed internally to ensure seamless integration and maintain control over quality.\n\n\n\nStatus: Proposed \n\n\n\n\nProject development team\nFire\nHumble Tim\n\n\n\n\nReal-time interaction, basic object manipulation, networked synchronization, user engagement, virtual collaboration, intuitive tool switching\n\n\n\n\nProject GitHub - Official GitHub account for the project development community focusing on enhancing virtual interaction capabilities.\nProject Documentation - Comprehensive documentation on the project’s features and development guidelines.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240611-lower-learning-rate.html#the-infrequent-use-case",
-    "href": "decisions/20240611-lower-learning-rate.html#the-infrequent-use-case",
-    "title": "Proposed: Switch learning rate to be lower.",
+    "objectID": "decisions/20241014-basic-realtime-interaction.html#the-context",
+    "href": "decisions/20241014-basic-realtime-interaction.html#the-context",
+    "title": "Proposed: Basic Real-Time Interaction for Character and World Scenes",
     "section": "",
-    "text": "This approach might not be suitable for all types of models or datasets."
+    "text": "The project will enable users to interact in real-time by manipulating objects within a shared virtual environment, enhancing the user experience."
   },
   {
-    "objectID": "decisions/20240611-lower-learning-rate.html#in-core-and-done-by-us",
-    "href": "decisions/20240611-lower-learning-rate.html#in-core-and-done-by-us",
-    "title": "Proposed: Switch learning rate to be lower.",
+    "objectID": "decisions/20241014-basic-realtime-interaction.html#the-problem-statement",
+    "href": "decisions/20241014-basic-realtime-interaction.html#the-problem-statement",
+    "title": "Proposed: Basic Real-Time Interaction for Character and World Scenes",
     "section": "",
-    "text": "This proposal is made by the V-Sekai development team and will be implemented by us."
+    "text": "I want to extend V-Sekai’s functionality to support real-time interaction with uploaded character and world scenes. This includes the ability for users to manipulate objects within the scene and have those changes reflected in real-time for other users connected to the same session. Additionally, seamless integration of new elements into the environment is crucial.\nHere’s a detailed breakdown of the features we plan to implement:\n\nReal-time Interaction: Users can move and rotate objects in the scene. Changes appear instantly, providing immediate visual feedback.\nNetworked Synchronization: When one user modifies something, the change is immediately visible to all other users in the same session.\nObject Persistence: Users can save their current scene setup to continue working on it later or retrieve it in another session.\nDynamic Environment Integration: Facilitate the introduction of new interactive elements during live sessions.\nMediator Role: A special user, called a mediator, can manage permissions like who can move what, start or end the session, and oversee interactions between users.\nLimited Scope: Initially, this feature will support multiple users interacting in one scene without additional complexities like handling multiple scenes or advanced physics.\n\nThis upgrade leverages the existing functionality of V-Sekai for uploading and rendering game engine assets. It assumes the utilization of V-Sekai’s current game engine and networking capabilities, or the integration of clearly specified, readily available libraries or services to achieve the desired real-time interaction and synchronization."
   },
   {
-    "objectID": "decisions/20240611-lower-learning-rate.html#status",
-    "href": "decisions/20240611-lower-learning-rate.html#status",
-    "title": "Proposed: Switch learning rate to be lower.",
+    "objectID": "decisions/20241014-basic-realtime-interaction.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20241014-basic-realtime-interaction.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Basic Real-Time Interaction for Character and World Scenes",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "[Scene Interaction Mock-up]\n+------------------------------------------------+\n|                                                |\n|  [User1]                                       |\n|    * (Object1) &lt;-- [Moving]                    |\n|                                                |\n|  [Tool Switcher Pie Menu]                      |\n|    - Move Tool                                 |\n|    - Rotate Tool                               |\n|    - Close                                     |\n|                                                |\n|  [User2]                                       |\n|    * (Object2)                                 |\n|                                                |\n+------------------------------------------------+"
   },
   {
-    "objectID": "decisions/20240611-lower-learning-rate.html#decision-makers",
-    "href": "decisions/20240611-lower-learning-rate.html#decision-makers",
-    "title": "Proposed: Switch learning rate to be lower.",
+    "objectID": "decisions/20241014-basic-realtime-interaction.html#the-benefits",
+    "href": "decisions/20241014-basic-realtime-interaction.html#the-benefits",
+    "title": "Proposed: Basic Real-Time Interaction for Character and World Scenes",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "Enhanced user engagement allows users to interact dynamically with objects, increasing the sense of presence. Establishing basic functionalities lays the foundation for future features that can include more complex interactions. Immediate feedback is crucial for collaborative environments, and intuitive tool selection through the Tool Switcher Pie Menu enhances workflow efficiency."
   },
   {
-    "objectID": "decisions/20240611-lower-learning-rate.html#tags",
-    "href": "decisions/20240611-lower-learning-rate.html#tags",
-    "title": "Proposed: Switch learning rate to be lower.",
+    "objectID": "decisions/20241014-basic-realtime-interaction.html#the-downsides",
+    "href": "decisions/20241014-basic-realtime-interaction.html#the-downsides",
+    "title": "Proposed: Basic Real-Time Interaction for Character and World Scenes",
     "section": "",
-    "text": "V-Sekai"
+    "text": "The initial features are limited to basic manipulations, which might not meet all user expectations. As the user base grows, the current simple synchronization mechanism may need significant enhancements."
   },
   {
-    "objectID": "decisions/20240611-lower-learning-rate.html#further-reading",
-    "href": "decisions/20240611-lower-learning-rate.html#further-reading",
-    "title": "Proposed: Switch learning rate to be lower.",
+    "objectID": "decisions/20241014-basic-realtime-interaction.html#the-road-not-taken",
+    "href": "decisions/20241014-basic-realtime-interaction.html#the-road-not-taken",
+    "title": "Proposed: Basic Real-Time Interaction for Character and World Scenes",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "A full-scale interaction suite was initially considered, including scaling and advanced physics, but it was decided against due to complexity and resource constraints."
   },
   {
-    "objectID": "decisions/20240331-vrc-vrm-compatibility.html",
-    "href": "decisions/20240331-vrc-vrm-compatibility.html",
-    "title": "Proposed: VRC and VRM compatibility",
+    "objectID": "decisions/20241014-basic-realtime-interaction.html#the-infrequent-use-case",
+    "href": "decisions/20241014-basic-realtime-interaction.html#the-infrequent-use-case",
+    "title": "Proposed: Basic Real-Time Interaction for Character and World Scenes",
     "section": "",
-    "text": "VRChat (VRC) and Virtual Reality Model (VRM) are two popular things used in the creation of virtual reality content. However, they are not inherently compatible with each other, which can cause issues for developers trying to use both in their projects.\n\n\n\nThe lack of compatibility between VRC and VRM can lead to inefficiencies and limitations in the development process. This proposal aims to address this issue by providing a solution that allows for seamless integration of these two groups.\n\n\n\nThe proposed solution involves a series of steps outlined in the README below:\n\nDO NOT remove transparent triangles for [hair, face, body]\nMake sure the Body has all blend shapes deleted.\nAdd face shapes with hana tool\nSplit the skin from the clothing using separate by material.\nOn all the clothing delete vertex groups.\nUse Robust Weight Transfer for Blender to rig clothing\nUnpack the prefab.\nConvert to vrchat. Combine meshes, remove upper chest\nDelete skirt bones that are not used.\nAdd vrcfury direct tree\nAdd vrcfury fix write defaults\nAdd vrcfury anchor override fix\nAdd vrcfury jerry’s templates\nAdd vrcfury unlimited parameters\nMake sure the Body has the perfect sync blend shapes.\nRemember that VRM Mouth Joy is similar to jawOpen.\nRemember that brown down and eye blink can be buggy.\nChoose either the MPEG4 blendshapes or Perfect sync. Delete one or the other.\nRemove empty vrc parameters\nRemove Physbones with missing transforms from secondary.\nConvert bone clusters in sphere colliders to capsule colliders to go from VERY POOR to POOR.\nContinue converting capsules until satisfied “POOR”.\nThe FX controller must match the name and not be temporary.\nUse Auto VRMColliders.\nMake sure all pipeline IDs are detached.\nRemember to delete the upper chest from the humanoid.\nEye look is behind the nose bridge\nMake sure the breast bones are parented as the same bone as the clothing chest bones correspond to.\nCross eyed fix in vrcfury breaks eye tracking.\nUpload. (Pick a new slot. DO NOT REUSE A SLOT.)\n\n\n\n\nvrc sdk base\nvrc sdk avatar\nvrcfury\nvrcft - jerry’s templates\n\n\n\n\n\nin liltoon turn saturation to 2.\n\n\n\n\n\nTry in blender to merge by distance\n\n\n\n\n\n0.0125 m for distance\n15 degrees for angle match\n\n\n\n\n\nCore movement\nEars :3\n\n\n\n\n\nVRCFury blink controller\nVRCFury blend shape optimizer\nVRCFury direct tree optimizer\nVRCFury fix write defaults\nVRCFury unlimited parameters\nVRCFury anchor override fix\nVRCFury GoGo\n\n\n\n\n\nThe proposed solution will allow developers to use VRC and VRM together in their projects, leading to increased flexibility and efficiency.\n\n\n\nThe process may be complex and time-consuming, especially for those unfamiliar with these formats.\n\n\n\nAn alternative approach could involve developing a new format that combines the features of both VRC and VRM. However, this would likely require significant resources and may not be feasible for all developers.\n\n\n\nThis proposal may not be beneficial for developers who only use one of these formats in their projects.\n\n\n\nThe proposed solution has been developed by us and is integrated into our core system.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nvrc-get gui\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n[https://vcc.vrcfury.com]\n[https://Adjerry91.github.io/VRCFaceTracking-Templates/index.json]\n[https://esperecyan.github.io/VRMConverterForVRChat/registry.json]\n[https://vpm.nadena.dev/vpm.json]\n[https://lilxyzw.github.io/vpm-repos/vpm.json]\n[https://fujisunflower.booth.pm/items/2087178]\nVRM Downgrader\nGoGo Loco\n\nAI assistant Aria assisted with this article."
+    "text": "While the system is designed for multiple users, it will also support single-user sessions, although this is not the primary focus."
   },
   {
-    "objectID": "decisions/20240331-vrc-vrm-compatibility.html#the-context",
-    "href": "decisions/20240331-vrc-vrm-compatibility.html#the-context",
-    "title": "Proposed: VRC and VRM compatibility",
+    "objectID": "decisions/20241014-basic-realtime-interaction.html#in-core-and-done-by-us",
+    "href": "decisions/20241014-basic-realtime-interaction.html#in-core-and-done-by-us",
+    "title": "Proposed: Basic Real-Time Interaction for Character and World Scenes",
     "section": "",
-    "text": "VRChat (VRC) and Virtual Reality Model (VRM) are two popular things used in the creation of virtual reality content. However, they are not inherently compatible with each other, which can cause issues for developers trying to use both in their projects."
+    "text": "This feature is core to the project’s mission of enhancing interactive capabilities and will be developed internally to ensure seamless integration and maintain control over quality."
   },
   {
-    "objectID": "decisions/20240331-vrc-vrm-compatibility.html#the-problem-statement",
-    "href": "decisions/20240331-vrc-vrm-compatibility.html#the-problem-statement",
-    "title": "Proposed: VRC and VRM compatibility",
+    "objectID": "decisions/20241014-basic-realtime-interaction.html#status",
+    "href": "decisions/20241014-basic-realtime-interaction.html#status",
+    "title": "Proposed: Basic Real-Time Interaction for Character and World Scenes",
     "section": "",
-    "text": "The lack of compatibility between VRC and VRM can lead to inefficiencies and limitations in the development process. This proposal aims to address this issue by providing a solution that allows for seamless integration of these two groups."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20240331-vrc-vrm-compatibility.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240331-vrc-vrm-compatibility.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: VRC and VRM compatibility",
+    "objectID": "decisions/20241014-basic-realtime-interaction.html#decision-makers",
+    "href": "decisions/20241014-basic-realtime-interaction.html#decision-makers",
+    "title": "Proposed: Basic Real-Time Interaction for Character and World Scenes",
     "section": "",
-    "text": "The proposed solution involves a series of steps outlined in the README below:\n\nDO NOT remove transparent triangles for [hair, face, body]\nMake sure the Body has all blend shapes deleted.\nAdd face shapes with hana tool\nSplit the skin from the clothing using separate by material.\nOn all the clothing delete vertex groups.\nUse Robust Weight Transfer for Blender to rig clothing\nUnpack the prefab.\nConvert to vrchat. Combine meshes, remove upper chest\nDelete skirt bones that are not used.\nAdd vrcfury direct tree\nAdd vrcfury fix write defaults\nAdd vrcfury anchor override fix\nAdd vrcfury jerry’s templates\nAdd vrcfury unlimited parameters\nMake sure the Body has the perfect sync blend shapes.\nRemember that VRM Mouth Joy is similar to jawOpen.\nRemember that brown down and eye blink can be buggy.\nChoose either the MPEG4 blendshapes or Perfect sync. Delete one or the other.\nRemove empty vrc parameters\nRemove Physbones with missing transforms from secondary.\nConvert bone clusters in sphere colliders to capsule colliders to go from VERY POOR to POOR.\nContinue converting capsules until satisfied “POOR”.\nThe FX controller must match the name and not be temporary.\nUse Auto VRMColliders.\nMake sure all pipeline IDs are detached.\nRemember to delete the upper chest from the humanoid.\nEye look is behind the nose bridge\nMake sure the breast bones are parented as the same bone as the clothing chest bones correspond to.\nCross eyed fix in vrcfury breaks eye tracking.\nUpload. (Pick a new slot. DO NOT REUSE A SLOT.)\n\n\n\n\nvrc sdk base\nvrc sdk avatar\nvrcfury\nvrcft - jerry’s templates\n\n\n\n\n\nin liltoon turn saturation to 2.\n\n\n\n\n\nTry in blender to merge by distance\n\n\n\n\n\n0.0125 m for distance\n15 degrees for angle match\n\n\n\n\n\nCore movement\nEars :3\n\n\n\n\n\nVRCFury blink controller\nVRCFury blend shape optimizer\nVRCFury direct tree optimizer\nVRCFury fix write defaults\nVRCFury unlimited parameters\nVRCFury anchor override fix\nVRCFury GoGo"
+    "text": "Project development team\nFire\nHumble Tim"
   },
   {
-    "objectID": "decisions/20240331-vrc-vrm-compatibility.html#the-benefits",
-    "href": "decisions/20240331-vrc-vrm-compatibility.html#the-benefits",
-    "title": "Proposed: VRC and VRM compatibility",
+    "objectID": "decisions/20241014-basic-realtime-interaction.html#tags",
+    "href": "decisions/20241014-basic-realtime-interaction.html#tags",
+    "title": "Proposed: Basic Real-Time Interaction for Character and World Scenes",
     "section": "",
-    "text": "The proposed solution will allow developers to use VRC and VRM together in their projects, leading to increased flexibility and efficiency."
+    "text": "Real-time interaction, basic object manipulation, networked synchronization, user engagement, virtual collaboration, intuitive tool switching"
   },
   {
-    "objectID": "decisions/20240331-vrc-vrm-compatibility.html#the-downsides",
-    "href": "decisions/20240331-vrc-vrm-compatibility.html#the-downsides",
-    "title": "Proposed: VRC and VRM compatibility",
+    "objectID": "decisions/20241014-basic-realtime-interaction.html#further-reading",
+    "href": "decisions/20241014-basic-realtime-interaction.html#further-reading",
+    "title": "Proposed: Basic Real-Time Interaction for Character and World Scenes",
     "section": "",
-    "text": "The process may be complex and time-consuming, especially for those unfamiliar with these formats."
+    "text": "Project GitHub - Official GitHub account for the project development community focusing on enhancing virtual interaction capabilities.\nProject Documentation - Comprehensive documentation on the project’s features and development guidelines.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240331-vrc-vrm-compatibility.html#the-road-not-taken",
-    "href": "decisions/20240331-vrc-vrm-compatibility.html#the-road-not-taken",
-    "title": "Proposed: VRC and VRM compatibility",
+    "objectID": "decisions/20211031-verification-tools.html",
+    "href": "decisions/20211031-verification-tools.html",
+    "title": "Draft: Verification tools",
     "section": "",
-    "text": "An alternative approach could involve developing a new format that combines the features of both VRC and VRM. However, this would likely require significant resources and may not be feasible for all developers."
+    "text": "Draft: Verification tools\n\nContext and Problem Statement\nNeed to verify color, motion and scale\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nProduce a reference for color, motion and scene scales.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n\nColor using industry standard reference chart\nRange of motion animations\nMeter scale tests\n100 avatar bottleneck test\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNo.\n\n\nPositive Consequences\nNeed to standardize\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nOnly we can set standards\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240331-vrc-vrm-compatibility.html#the-infrequent-use-case",
-    "href": "decisions/20240331-vrc-vrm-compatibility.html#the-infrequent-use-case",
-    "title": "Proposed: VRC and VRM compatibility",
+    "objectID": "decisions/20211220-network-the-ubisoft-mixer-server.html",
+    "href": "decisions/20211220-network-the-ubisoft-mixer-server.html",
+    "title": "Rejected: Network the Ubisoft Mixer server",
     "section": "",
-    "text": "This proposal may not be beneficial for developers who only use one of these formats in their projects."
+    "text": "Status: rejected \nDeciders: V-Sekai,fire,\nTags: V-Sekai,\n\n\n\nWe want to use the Ubisoft Mixer project more easily.\nThe Ubisoft mixer project is also a good way to share Godot Engine scenes.\nThe problem is the mixer project is in Python and doesn’t have file sync.\n\n\n\nMy proposed solution is to write a elixir server that syncs the Blender file and the file share.\n\n\n\n\nExtract Mixer broadcaster code\nWrite an Elixir udp based broadcaster with webrtc\nWrite an Elixir file sync (SECURITY WARNING)\n\n\n\n\n\nEasier to host mixer.\n\n\n\n\n\nThe software may be a vector for security attacks.\n\n\n\n\n\nOption: Use V-Sekai as a networking sync.\nRejection Reason: Not ready yet and someone is working on it.\n\n\n\n\nNot a few lines of script.\n\n\n\nI know how to do this and no one else is doing it.\n\n\n\n\nhttps://github.com/ubisoft/mixer/issues\n\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240331-vrc-vrm-compatibility.html#in-core-and-done-by-us",
-    "href": "decisions/20240331-vrc-vrm-compatibility.html#in-core-and-done-by-us",
-    "title": "Proposed: VRC and VRM compatibility",
+    "objectID": "decisions/20211220-network-the-ubisoft-mixer-server.html#context-and-problem-statement",
+    "href": "decisions/20211220-network-the-ubisoft-mixer-server.html#context-and-problem-statement",
+    "title": "Rejected: Network the Ubisoft Mixer server",
     "section": "",
-    "text": "The proposed solution has been developed by us and is integrated into our core system."
+    "text": "We want to use the Ubisoft Mixer project more easily.\nThe Ubisoft mixer project is also a good way to share Godot Engine scenes.\nThe problem is the mixer project is in Python and doesn’t have file sync."
   },
   {
-    "objectID": "decisions/20240331-vrc-vrm-compatibility.html#status",
-    "href": "decisions/20240331-vrc-vrm-compatibility.html#status",
-    "title": "Proposed: VRC and VRM compatibility",
+    "objectID": "decisions/20211220-network-the-ubisoft-mixer-server.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20211220-network-the-ubisoft-mixer-server.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Rejected: Network the Ubisoft Mixer server",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "My proposed solution is to write a elixir server that syncs the Blender file and the file share."
   },
   {
-    "objectID": "decisions/20240331-vrc-vrm-compatibility.html#decision-makers",
-    "href": "decisions/20240331-vrc-vrm-compatibility.html#decision-makers",
-    "title": "Proposed: VRC and VRM compatibility",
+    "objectID": "decisions/20211220-network-the-ubisoft-mixer-server.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20211220-network-the-ubisoft-mixer-server.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Rejected: Network the Ubisoft Mixer server",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "Extract Mixer broadcaster code\nWrite an Elixir udp based broadcaster with webrtc\nWrite an Elixir file sync (SECURITY WARNING)"
   },
   {
-    "objectID": "decisions/20240331-vrc-vrm-compatibility.html#tags",
-    "href": "decisions/20240331-vrc-vrm-compatibility.html#tags",
-    "title": "Proposed: VRC and VRM compatibility",
+    "objectID": "decisions/20211220-network-the-ubisoft-mixer-server.html#positive-consequences",
+    "href": "decisions/20211220-network-the-ubisoft-mixer-server.html#positive-consequences",
+    "title": "Rejected: Network the Ubisoft Mixer server",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Easier to host mixer."
   },
   {
-    "objectID": "decisions/20240331-vrc-vrm-compatibility.html#further-reading",
-    "href": "decisions/20240331-vrc-vrm-compatibility.html#further-reading",
-    "title": "Proposed: VRC and VRM compatibility",
+    "objectID": "decisions/20211220-network-the-ubisoft-mixer-server.html#negative-consequences",
+    "href": "decisions/20211220-network-the-ubisoft-mixer-server.html#negative-consequences",
+    "title": "Rejected: Network the Ubisoft Mixer server",
     "section": "",
-    "text": "vrc-get gui\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n[https://vcc.vrcfury.com]\n[https://Adjerry91.github.io/VRCFaceTracking-Templates/index.json]\n[https://esperecyan.github.io/VRMConverterForVRChat/registry.json]\n[https://vpm.nadena.dev/vpm.json]\n[https://lilxyzw.github.io/vpm-repos/vpm.json]\n[https://fujisunflower.booth.pm/items/2087178]\nVRM Downgrader\nGoGo Loco\n\nAI assistant Aria assisted with this article."
+    "text": "The software may be a vector for security attacks."
   },
   {
-    "objectID": "decisions/20240314-live-collab.html",
-    "href": "decisions/20240314-live-collab.html",
-    "title": "Proposed: Real-Time Motion Capture and Animation Synchronization",
+    "objectID": "decisions/20211220-network-the-ubisoft-mixer-server.html#option-graveyard",
+    "href": "decisions/20211220-network-the-ubisoft-mixer-server.html#option-graveyard",
+    "title": "Rejected: Network the Ubisoft Mixer server",
     "section": "",
-    "text": "In the context of V-Sekai, a VR social network, we are looking to enhance the user experience by introducing real-time motion capture and animation synchronization features. This would allow users to interact with each other in real-time within the Godot engine.\n\n\n\nCurrently, there’s no mechanism for real-time synchronization of skeleton motion capture (mocap), blend shape animations, and skeleton animations between different users. This limits the interactive capabilities of the platform and hinders the creation of a truly immersive virtual environment.\n\n\n\nWe propose to extend the live collaboration feature to include real-time synchronization of mocap and animations. This will enable users to see each other’s movements and expressions in real-time, further enhancing the interactivity of the platform.\n\n\n\n\nReal-Time Interaction: Users can see each other’s movements and expressions in real-time, creating a more immersive and interactive experience.\nAnimation Synchronization: Changes made to the animations by one user are instantly visible to others.\nEnhanced User Experience: The ability to interact with each other in a more realistic manner greatly enhances the overall user experience.\n\n\n\n\n\nIncreased Complexity: The addition of mocap and animation synchronization could increase the complexity of the project.\nPerformance Impact: Real-time synchronization of animations could have an impact on performance, especially for users with slower internet connections.\n\n\n\n\nThe minimum viable product would include the ability to move a model around on one machine and have those positions updated on another, as well as the ability to perform basic animations that are visible to other users. Given the simplicity of the Godot scene format, this should be achievable.\n\n\n\nThe V-Sekai team will implement this feature.\n\n\n\nProposed\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\nGodot\nLive Collaboration\nMotion Capture\nAnimation Synchronization\n\n\n\n\n\nV-Sekai · GitHub\nV-Sekai/v-sekai-game\n\nAssisted by Aria, an AI assistant."
+    "text": "Option: Use V-Sekai as a networking sync.\nRejection Reason: Not ready yet and someone is working on it."
   },
   {
-    "objectID": "decisions/20240314-live-collab.html#context",
-    "href": "decisions/20240314-live-collab.html#context",
-    "title": "Proposed: Real-Time Motion Capture and Animation Synchronization",
+    "objectID": "decisions/20211220-network-the-ubisoft-mixer-server.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20211220-network-the-ubisoft-mixer-server.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Rejected: Network the Ubisoft Mixer server",
     "section": "",
-    "text": "In the context of V-Sekai, a VR social network, we are looking to enhance the user experience by introducing real-time motion capture and animation synchronization features. This would allow users to interact with each other in real-time within the Godot engine."
+    "text": "Not a few lines of script."
   },
   {
-    "objectID": "decisions/20240314-live-collab.html#problem",
-    "href": "decisions/20240314-live-collab.html#problem",
-    "title": "Proposed: Real-Time Motion Capture and Animation Synchronization",
+    "objectID": "decisions/20211220-network-the-ubisoft-mixer-server.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20211220-network-the-ubisoft-mixer-server.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Rejected: Network the Ubisoft Mixer server",
     "section": "",
-    "text": "Currently, there’s no mechanism for real-time synchronization of skeleton motion capture (mocap), blend shape animations, and skeleton animations between different users. This limits the interactive capabilities of the platform and hinders the creation of a truly immersive virtual environment."
+    "text": "I know how to do this and no one else is doing it."
   },
   {
-    "objectID": "decisions/20240314-live-collab.html#solution",
-    "href": "decisions/20240314-live-collab.html#solution",
-    "title": "Proposed: Real-Time Motion Capture and Animation Synchronization",
+    "objectID": "decisions/20211220-network-the-ubisoft-mixer-server.html#references",
+    "href": "decisions/20211220-network-the-ubisoft-mixer-server.html#references",
+    "title": "Rejected: Network the Ubisoft Mixer server",
     "section": "",
-    "text": "We propose to extend the live collaboration feature to include real-time synchronization of mocap and animations. This will enable users to see each other’s movements and expressions in real-time, further enhancing the interactivity of the platform."
+    "text": "https://github.com/ubisoft/mixer/issues"
   },
   {
-    "objectID": "decisions/20240314-live-collab.html#benefits",
-    "href": "decisions/20240314-live-collab.html#benefits",
-    "title": "Proposed: Real-Time Motion Capture and Animation Synchronization",
+    "objectID": "decisions/20211220-network-the-ubisoft-mixer-server.html#derivative-license",
+    "href": "decisions/20211220-network-the-ubisoft-mixer-server.html#derivative-license",
+    "title": "Rejected: Network the Ubisoft Mixer server",
     "section": "",
-    "text": "Real-Time Interaction: Users can see each other’s movements and expressions in real-time, creating a more immersive and interactive experience.\nAnimation Synchronization: Changes made to the animations by one user are instantly visible to others.\nEnhanced User Experience: The ability to interact with each other in a more realistic manner greatly enhances the overall user experience."
+    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240314-live-collab.html#downsides",
-    "href": "decisions/20240314-live-collab.html#downsides",
-    "title": "Proposed: Real-Time Motion Capture and Animation Synchronization",
+    "objectID": "decisions/20240522-discord-bot.html",
+    "href": "decisions/20240522-discord-bot.html",
+    "title": "Draft: Notify community members and users about activity and updates via a Discord bot",
     "section": "",
-    "text": "Increased Complexity: The addition of mocap and animation synchronization could increase the complexity of the project.\nPerformance Impact: Real-time synchronization of animations could have an impact on performance, especially for users with slower internet connections."
+    "text": "Status: draft\n\n\n\nWe want a way to notify community members and users about activity and updates.\n\n\n\nA discord bot would be able to inform users via Discord about updates and changes.\n\n\n\nWe would connect to Discord API from Elixir using one of several integration libraries.\nWe can report #information such as server player count by editing a message; or updating the bot status.\nI would also like to poll #information such as CI/CD builds and deployments. We could make an API where someone or something can post a message displayed in Discord using curl or some command, though we would have to make sure this is locked behind a secret key. Unclear.\n\n\n\n\nGrow the community\nHelp us manage the project\n\n\n\n\n\nMaintenance costs of having a service fed"
   },
   {
-    "objectID": "decisions/20240314-live-collab.html#mvp",
-    "href": "decisions/20240314-live-collab.html#mvp",
-    "title": "Proposed: Real-Time Motion Capture and Animation Synchronization",
+    "objectID": "decisions/20240522-discord-bot.html#context-and-problem-statement",
+    "href": "decisions/20240522-discord-bot.html#context-and-problem-statement",
+    "title": "Draft: Notify community members and users about activity and updates via a Discord bot",
     "section": "",
-    "text": "The minimum viable product would include the ability to move a model around on one machine and have those positions updated on another, as well as the ability to perform basic animations that are visible to other users. Given the simplicity of the Godot scene format, this should be achievable."
+    "text": "We want a way to notify community members and users about activity and updates."
   },
   {
-    "objectID": "decisions/20240314-live-collab.html#implementation",
-    "href": "decisions/20240314-live-collab.html#implementation",
-    "title": "Proposed: Real-Time Motion Capture and Animation Synchronization",
+    "objectID": "decisions/20240522-discord-bot.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20240522-discord-bot.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Draft: Notify community members and users about activity and updates via a Discord bot",
     "section": "",
-    "text": "The V-Sekai team will implement this feature."
+    "text": "A discord bot would be able to inform users via Discord about updates and changes."
   },
   {
-    "objectID": "decisions/20240314-live-collab.html#status",
-    "href": "decisions/20240314-live-collab.html#status",
-    "title": "Proposed: Real-Time Motion Capture and Animation Synchronization",
+    "objectID": "decisions/20240522-discord-bot.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240522-discord-bot.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Draft: Notify community members and users about activity and updates via a Discord bot",
     "section": "",
-    "text": "Proposed"
+    "text": "We would connect to Discord API from Elixir using one of several integration libraries.\nWe can report #information such as server player count by editing a message; or updating the bot status.\nI would also like to poll #information such as CI/CD builds and deployments. We could make an API where someone or something can post a message displayed in Discord using curl or some command, though we would have to make sure this is locked behind a secret key. Unclear."
   },
   {
-    "objectID": "decisions/20240314-live-collab.html#decision-makers",
-    "href": "decisions/20240314-live-collab.html#decision-makers",
-    "title": "Proposed: Real-Time Motion Capture and Animation Synchronization",
+    "objectID": "decisions/20240522-discord-bot.html#positive-consequences",
+    "href": "decisions/20240522-discord-bot.html#positive-consequences",
+    "title": "Draft: Notify community members and users about activity and updates via a Discord bot",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "Grow the community\nHelp us manage the project"
   },
   {
-    "objectID": "decisions/20240314-live-collab.html#tags",
-    "href": "decisions/20240314-live-collab.html#tags",
-    "title": "Proposed: Real-Time Motion Capture and Animation Synchronization",
+    "objectID": "decisions/20240522-discord-bot.html#negative-consequences",
+    "href": "decisions/20240522-discord-bot.html#negative-consequences",
+    "title": "Draft: Notify community members and users about activity and updates via a Discord bot",
     "section": "",
-    "text": "V-Sekai\nGodot\nLive Collaboration\nMotion Capture\nAnimation Synchronization"
+    "text": "Maintenance costs of having a service fed"
   },
   {
-    "objectID": "decisions/20240314-live-collab.html#further-reading",
-    "href": "decisions/20240314-live-collab.html#further-reading",
-    "title": "Proposed: Real-Time Motion Capture and Animation Synchronization",
-    "section": "",
-    "text": "V-Sekai · GitHub\nV-Sekai/v-sekai-game\n\nAssisted by Aria, an AI assistant."
+    "objectID": "decisions/20240522-discord-bot.html#positive-consequences-1",
+    "href": "decisions/20240522-discord-bot.html#positive-consequences-1",
+    "title": "Draft: Notify community members and users about activity and updates via a Discord bot",
+    "section": "Positive Consequences",
+    "text": "Positive Consequences\n\nLower maintenance burden"
   },
   {
-    "objectID": "decisions/20240627-every-commit-push-pass-cicd.html",
-    "href": "decisions/20240627-every-commit-push-pass-cicd.html",
-    "title": "Proposed: Every Commit Push Pass Cicd",
-    "section": "",
-    "text": "We are working on V-Sekai, a virtual reality social network. Our development workflow involves multiple developers making frequent changes to the codebase.\n\n\n\nWe have trouble understanding the logical flow of work. This is causing delays in development and making it difficult to track changes and debug issues. Currently, our commits are checked after they are merged into the main branch, which can lead to problems if the commit does not pass the checks.\n\n\n\nThe proposal is to implement a system where every commit and push operation passes through our CI/CD pipeline as a logical unit before being checked into the main branch. This means that each commit will trigger a build and test process, ensuring that all changes are validated before they are merged.\nOn every commit:\n  Trigger CI/CD pipeline\n    Build application\n    Run tests\nIf tests pass:\n  Allow check-in to main branch\nElse:\n  Return error and prevent check-in\n\n\n\n\nImproved traceability of changes\nFaster identification and resolution of issues\nMore efficient development workflow\nPrevention of problematic commits entering the main branch\n\n\n\n\n\nPotential increase in build times\nRequires investment in robust testing infrastructure\n\n\n\n\nAn alternative approach could be to only run the CI/CD pipeline on specific branches or at specific times. However, this would not provide the same level of validation and could lead to issues being missed.\n\n\n\nIn cases where commits are made infrequently, this approach may result in longer periods between builds. However, the benefits of improved traceability and issue resolution outweigh this potential downside.\n\n\n\nThis change will be implemented by the V-Sekai development team and will become a core part of our development workflow.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "objectID": "decisions/20240522-discord-bot.html#negative-consequences-1",
+    "href": "decisions/20240522-discord-bot.html#negative-consequences-1",
+    "title": "Draft: Notify community members and users about activity and updates via a Discord bot",
+    "section": "Negative Consequences",
+    "text": "Negative Consequences\n\nNo access to commands or statuses. Only capable of posting messages."
   },
   {
-    "objectID": "decisions/20240627-every-commit-push-pass-cicd.html#the-context",
-    "href": "decisions/20240627-every-commit-push-pass-cicd.html#the-context",
-    "title": "Proposed: Every Commit Push Pass Cicd",
-    "section": "",
-    "text": "We are working on V-Sekai, a virtual reality social network. Our development workflow involves multiple developers making frequent changes to the codebase."
+    "objectID": "decisions/20240522-discord-bot.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20240522-discord-bot.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Draft: Notify community members and users about activity and updates via a Discord bot",
+    "section": "If this enhancement will not be used often, can it be worked around with a few lines of script?",
+    "text": "If this enhancement will not be used often, can it be worked around with a few lines of script?\nYes, it is possible to script querying the itch.io or Uro shards API. This proposal aims to make this #information more accessible to those who would not script it."
   },
   {
-    "objectID": "decisions/20240627-every-commit-push-pass-cicd.html#the-problem-statement",
-    "href": "decisions/20240627-every-commit-push-pass-cicd.html#the-problem-statement",
-    "title": "Proposed: Every Commit Push Pass Cicd",
-    "section": "",
-    "text": "We have trouble understanding the logical flow of work. This is causing delays in development and making it difficult to track changes and debug issues. Currently, our commits are checked after they are merged into the main branch, which can lead to problems if the commit does not pass the checks."
+    "objectID": "decisions/20240522-discord-bot.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20240522-discord-bot.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Draft: Notify community members and users about activity and updates via a Discord bot",
+    "section": "Is there a reason why this should be core and done by us?",
+    "text": "Is there a reason why this should be core and done by us?\nWe need this to grow the community."
   },
   {
-    "objectID": "decisions/20240627-every-commit-push-pass-cicd.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240627-every-commit-push-pass-cicd.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Every Commit Push Pass Cicd",
+    "objectID": "decisions/20240522-discord-bot.html#derivative-license",
+    "href": "decisions/20240522-discord-bot.html#derivative-license",
+    "title": "Draft: Notify community members and users about activity and updates via a Discord bot",
+    "section": "Derivative License",
+    "text": "Derivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+  },
+  {
+    "objectID": "decisions/20240121-install-tailscale.html",
+    "href": "decisions/20240121-install-tailscale.html",
+    "title": "Proposed: Installing Tailscale on Linux Fedora 39",
     "section": "",
-    "text": "The proposal is to implement a system where every commit and push operation passes through our CI/CD pipeline as a logical unit before being checked into the main branch. This means that each commit will trigger a build and test process, ensuring that all changes are validated before they are merged.\nOn every commit:\n  Trigger CI/CD pipeline\n    Build application\n    Run tests\nIf tests pass:\n  Allow check-in to main branch\nElse:\n  Return error and prevent check-in"
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nIn the current digital age, secure and efficient networking is a necessity. Tailscale provides a secure network connection between devices, regardless of location. This proposal aims to guide the installation of Tailscale on Linux Fedora 39.\n\n\n\nThe challenge lies in setting up Tailscale on Linux Fedora 39. The process involves adding the Tailscale repository, installing the software, enabling the service, and connecting to the Tailscale network.\n\n\n\nHere’s a concise step-by-step guide:\n# Add the Tailscale repository\nsudo dnf config-manager --add-repo https://pkgs.tailscale.com/stable/rhel/8/tailscale.repo\n\n# Install Tailscale\nsudo dnf install tailscale -y\n\n# Enable and start the service\nsudo systemctl enable --now tailscaled\n\n# Connect to your Tailscale network and authenticate in your browser\nsudo tailscale up\n\n# Find your Tailscale IPv4 address\ntailscale ip -4\n\n# Disable key expiry\n\n\n\n\nSecure: Tailscale uses end-to-end encryption for all traffic.\nEasy to set up: The process is straightforward and can be done quickly.\nScalable: Tailscale can handle connections between a large number of devices.\n\n\n\n\n\nRequires internet access: Tailscale requires an active internet connection to establish the network.\nCompatibility issues: There may be compatibility issues with certain applications or systems.\n\n\n\n\n\nOpenVPN: A well-established VPN solution, but it requires more complex setup and maintenance.\nWireGuard: Another VPN solution that is simpler and faster but less mature.\n\n\n\n\nThis solution is particularly useful for remote teams who need to access shared resources securely, or for individuals who want to connect their devices in a private network.\n\n\n\nIn-house development of a similar solution would require significant resources and expertise in networking and security. It is more cost-effective and efficient to use an existing solution like Tailscale.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis proposal was assisted by Aria, the AI assistant."
   },
   {
-    "objectID": "decisions/20240627-every-commit-push-pass-cicd.html#the-benefits",
-    "href": "decisions/20240627-every-commit-push-pass-cicd.html#the-benefits",
-    "title": "Proposed: Every Commit Push Pass Cicd",
+    "objectID": "decisions/20240121-install-tailscale.html#metadata",
+    "href": "decisions/20240121-install-tailscale.html#metadata",
+    "title": "Proposed: Installing Tailscale on Linux Fedora 39",
     "section": "",
-    "text": "Improved traceability of changes\nFaster identification and resolution of issues\nMore efficient development workflow\nPrevention of problematic commits entering the main branch"
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20240627-every-commit-push-pass-cicd.html#the-downsides",
-    "href": "decisions/20240627-every-commit-push-pass-cicd.html#the-downsides",
-    "title": "Proposed: Every Commit Push Pass Cicd",
+    "objectID": "decisions/20240121-install-tailscale.html#context",
+    "href": "decisions/20240121-install-tailscale.html#context",
+    "title": "Proposed: Installing Tailscale on Linux Fedora 39",
     "section": "",
-    "text": "Potential increase in build times\nRequires investment in robust testing infrastructure"
+    "text": "In the current digital age, secure and efficient networking is a necessity. Tailscale provides a secure network connection between devices, regardless of location. This proposal aims to guide the installation of Tailscale on Linux Fedora 39."
   },
   {
-    "objectID": "decisions/20240627-every-commit-push-pass-cicd.html#the-road-not-taken",
-    "href": "decisions/20240627-every-commit-push-pass-cicd.html#the-road-not-taken",
-    "title": "Proposed: Every Commit Push Pass Cicd",
+    "objectID": "decisions/20240121-install-tailscale.html#problem",
+    "href": "decisions/20240121-install-tailscale.html#problem",
+    "title": "Proposed: Installing Tailscale on Linux Fedora 39",
     "section": "",
-    "text": "An alternative approach could be to only run the CI/CD pipeline on specific branches or at specific times. However, this would not provide the same level of validation and could lead to issues being missed."
+    "text": "The challenge lies in setting up Tailscale on Linux Fedora 39. The process involves adding the Tailscale repository, installing the software, enabling the service, and connecting to the Tailscale network."
   },
   {
-    "objectID": "decisions/20240627-every-commit-push-pass-cicd.html#the-infrequent-use-case",
-    "href": "decisions/20240627-every-commit-push-pass-cicd.html#the-infrequent-use-case",
-    "title": "Proposed: Every Commit Push Pass Cicd",
+    "objectID": "decisions/20240121-install-tailscale.html#solution",
+    "href": "decisions/20240121-install-tailscale.html#solution",
+    "title": "Proposed: Installing Tailscale on Linux Fedora 39",
     "section": "",
-    "text": "In cases where commits are made infrequently, this approach may result in longer periods between builds. However, the benefits of improved traceability and issue resolution outweigh this potential downside."
+    "text": "Here’s a concise step-by-step guide:\n# Add the Tailscale repository\nsudo dnf config-manager --add-repo https://pkgs.tailscale.com/stable/rhel/8/tailscale.repo\n\n# Install Tailscale\nsudo dnf install tailscale -y\n\n# Enable and start the service\nsudo systemctl enable --now tailscaled\n\n# Connect to your Tailscale network and authenticate in your browser\nsudo tailscale up\n\n# Find your Tailscale IPv4 address\ntailscale ip -4\n\n# Disable key expiry"
   },
   {
-    "objectID": "decisions/20240627-every-commit-push-pass-cicd.html#in-core-and-done-by-us",
-    "href": "decisions/20240627-every-commit-push-pass-cicd.html#in-core-and-done-by-us",
-    "title": "Proposed: Every Commit Push Pass Cicd",
+    "objectID": "decisions/20240121-install-tailscale.html#pros",
+    "href": "decisions/20240121-install-tailscale.html#pros",
+    "title": "Proposed: Installing Tailscale on Linux Fedora 39",
     "section": "",
-    "text": "This change will be implemented by the V-Sekai development team and will become a core part of our development workflow."
+    "text": "Secure: Tailscale uses end-to-end encryption for all traffic.\nEasy to set up: The process is straightforward and can be done quickly.\nScalable: Tailscale can handle connections between a large number of devices."
   },
   {
-    "objectID": "decisions/20240627-every-commit-push-pass-cicd.html#status",
-    "href": "decisions/20240627-every-commit-push-pass-cicd.html#status",
-    "title": "Proposed: Every Commit Push Pass Cicd",
+    "objectID": "decisions/20240121-install-tailscale.html#cons",
+    "href": "decisions/20240121-install-tailscale.html#cons",
+    "title": "Proposed: Installing Tailscale on Linux Fedora 39",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "Requires internet access: Tailscale requires an active internet connection to establish the network.\nCompatibility issues: There may be compatibility issues with certain applications or systems."
   },
   {
-    "objectID": "decisions/20240627-every-commit-push-pass-cicd.html#decision-makers",
-    "href": "decisions/20240627-every-commit-push-pass-cicd.html#decision-makers",
-    "title": "Proposed: Every Commit Push Pass Cicd",
+    "objectID": "decisions/20240121-install-tailscale.html#alternatives-considered",
+    "href": "decisions/20240121-install-tailscale.html#alternatives-considered",
+    "title": "Proposed: Installing Tailscale on Linux Fedora 39",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "OpenVPN: A well-established VPN solution, but it requires more complex setup and maintenance.\nWireGuard: Another VPN solution that is simpler and faster but less mature."
   },
   {
-    "objectID": "decisions/20240627-every-commit-push-pass-cicd.html#tags",
-    "href": "decisions/20240627-every-commit-push-pass-cicd.html#tags",
-    "title": "Proposed: Every Commit Push Pass Cicd",
+    "objectID": "decisions/20240121-install-tailscale.html#rare-use-case",
+    "href": "decisions/20240121-install-tailscale.html#rare-use-case",
+    "title": "Proposed: Installing Tailscale on Linux Fedora 39",
     "section": "",
-    "text": "V-Sekai"
+    "text": "This solution is particularly useful for remote teams who need to access shared resources securely, or for individuals who want to connect their devices in a private network."
   },
   {
-    "objectID": "decisions/20240627-every-commit-push-pass-cicd.html#further-reading",
-    "href": "decisions/20240627-every-commit-push-pass-cicd.html#further-reading",
-    "title": "Proposed: Every Commit Push Pass Cicd",
+    "objectID": "decisions/20240121-install-tailscale.html#in-house-development",
+    "href": "decisions/20240121-install-tailscale.html#in-house-development",
+    "title": "Proposed: Installing Tailscale on Linux Fedora 39",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "In-house development of a similar solution would require significant resources and expertise in networking and security. It is more cost-effective and efficient to use an existing solution like Tailscale."
   },
   {
-    "objectID": "decisions/20240305-v-sekai-launcher.html",
-    "href": "decisions/20240305-v-sekai-launcher.html",
-    "title": "Proposed: V-Sekai Game Launcher",
+    "objectID": "decisions/20240121-install-tailscale.html#references",
+    "href": "decisions/20240121-install-tailscale.html#references",
+    "title": "Proposed: Installing Tailscale on Linux Fedora 39",
     "section": "",
-    "text": "The game project’s current distribution and dependency management is a challenge. The existing setup, which involves a Godot project with multiple add-ons, is complex and challenging to manage and distribute.\n\n\n\n\nThe editor plugin is deeply intertwined with the gameplay elements, making it hard to develop.\nWe aim to make the editor plugin lightweight and easy to distribute so that users can easily incorporate it into their regular projects to convert their existing Godot content into V-Sekai-compatible content.\nThere is a code duplication problem between vsk_game and vsk_editor/sdk.\nWe must consider what changes we can make to the plugin’s design to make it more user-friendly.\nThe lack of a package manager and universal plugins or a dependency graph for plugins is a significant issue, potentially overlapping with a core problem in Godot.\n\nThe priority question is how to transform this into an SDK with the cleanest possible distribution method.\n\n\n\nTo address these issues, we propose the creation of a V-Sekai Game Launcher. This launcher will be built using Godot and will replace the regular Godot project manager. It will handle all package-related tasks, ensuring smooth distribution and dependency management.\n\n\n\n\nSimplified distribution: The launcher will handle the distribution of the game, making it easier for users to access and install the game.\nImproved dependency management: The launcher will also manage the game’s dependencies, resolving the current issues faced due to the lack of a package manager.\nEnhanced user experience: With the launcher handling package and project management, users can focus on creating content or playing the game.\n\n\n\n\n\nDevelopment time: Building a new launcher will require additional development time and resources.\nUser adoption: Users may need time to adapt to the new launcher and its functionalities.\n\n\n\n\nAn alternative solution considered was to use the Godot Asset Store for distribution. However, it does not solve the dependency management problem and is not ready yet for such a task.\n\n\n\nIn cases where users want to manage their packages manually or prefer using the regular Godot project manager, they may find the launcher unnecessary or intrusive.\n\n\n\nThe V-Sekai development team will develop the V-Sekai Game Launcher.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team and community stakeholders.\n\n\n\n\n\nV-Sekai, Avatar Customization, AI, Facial Expressions, Game Launcher\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this proposal."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis proposal was assisted by Aria, the AI assistant."
   },
   {
-    "objectID": "decisions/20240305-v-sekai-launcher.html#the-context",
-    "href": "decisions/20240305-v-sekai-launcher.html#the-context",
-    "title": "Proposed: V-Sekai Game Launcher",
+    "objectID": "decisions/20231112-validation-service.html",
+    "href": "decisions/20231112-validation-service.html",
+    "title": "Proposed: Validator Service for V-Sekai",
     "section": "",
-    "text": "The game project’s current distribution and dependency management is a challenge. The existing setup, which involves a Godot project with multiple add-ons, is complex and challenging to manage and distribute."
+    "text": "Status: Proposed\nDeciders: iFire, Bioblaze Payne, V-Sekai Team\nTags: V-Sekai, Validator Service, Godot Engine, GLTF, Websockets, API\n\n\n\n\nV-Sekai is an open-source project that brings social VR/VRSNS/metaverse components to the Godot Engine. The team is considering implementing a validator service to enhance the functionality and reliability of their projects.\n\n\n\nThe current backend system lacks a mechanism to validate scenes, count triangles, convert GLTF to Godot scene, and strip bad code from Godot scenes. This can lead to errors and inefficiencies in the development process.\n\n\n\nThe proposed solution is to create a validator service that conforms to a specific specification. This service would:\n\nConvert GLTF to Godot scene.\nGo over the scene and print the number of triangles.\nIf necessary, run LOD on the scene.\nRun a validation that strips the bad code from the Godot scene.\nUse websockets and an API for communication and function calls.\n\nThe front-end for this service could be a CLI that calls the function locally. The asset service would call the validator service, which would then notify the websocket service via its API call.\n\n\n\nImplementing this validator service would provide several benefits:\n\nImproved accuracy and efficiency in the development process.\nEnhanced error detection and prevention.\nStreamlined communication between different parts of the system.\n\n\n\n\nPotential challenges or downsides could include:\n\nComplexity in setting up and maintaining the validator service.\nNeed for thorough testing to ensure the validator service works as expected.\n\n\n\n\nAn alternative approach could be to use gdscript + webrtc instead of websockets + API for communication and function calls. However, this would need to be evaluated for feasibility and efficiency.\n\n\n\nThe next steps would be to:\n\nFinalize the specification for the validator service.\nDevelop the validator service according to the agreed-upon specification.\nTest the validator service thoroughly to ensure it works as expected.\nImplement the validator service in the V-Sekai system.\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nThis proposal was assisted by AI assistant Aria."
   },
   {
-    "objectID": "decisions/20240305-v-sekai-launcher.html#the-problem-statement",
-    "href": "decisions/20240305-v-sekai-launcher.html#the-problem-statement",
-    "title": "Proposed: V-Sekai Game Launcher",
+    "objectID": "decisions/20231112-validation-service.html#metadata",
+    "href": "decisions/20231112-validation-service.html#metadata",
+    "title": "Proposed: Validator Service for V-Sekai",
     "section": "",
-    "text": "The editor plugin is deeply intertwined with the gameplay elements, making it hard to develop.\nWe aim to make the editor plugin lightweight and easy to distribute so that users can easily incorporate it into their regular projects to convert their existing Godot content into V-Sekai-compatible content.\nThere is a code duplication problem between vsk_game and vsk_editor/sdk.\nWe must consider what changes we can make to the plugin’s design to make it more user-friendly.\nThe lack of a package manager and universal plugins or a dependency graph for plugins is a significant issue, potentially overlapping with a core problem in Godot.\n\nThe priority question is how to transform this into an SDK with the cleanest possible distribution method."
+    "text": "Status: Proposed\nDeciders: iFire, Bioblaze Payne, V-Sekai Team\nTags: V-Sekai, Validator Service, Godot Engine, GLTF, Websockets, API"
   },
   {
-    "objectID": "decisions/20240305-v-sekai-launcher.html#proposed-solution",
-    "href": "decisions/20240305-v-sekai-launcher.html#proposed-solution",
-    "title": "Proposed: V-Sekai Game Launcher",
+    "objectID": "decisions/20231112-validation-service.html#context",
+    "href": "decisions/20231112-validation-service.html#context",
+    "title": "Proposed: Validator Service for V-Sekai",
     "section": "",
-    "text": "To address these issues, we propose the creation of a V-Sekai Game Launcher. This launcher will be built using Godot and will replace the regular Godot project manager. It will handle all package-related tasks, ensuring smooth distribution and dependency management."
+    "text": "V-Sekai is an open-source project that brings social VR/VRSNS/metaverse components to the Godot Engine. The team is considering implementing a validator service to enhance the functionality and reliability of their projects."
   },
   {
-    "objectID": "decisions/20240305-v-sekai-launcher.html#the-benefits",
-    "href": "decisions/20240305-v-sekai-launcher.html#the-benefits",
-    "title": "Proposed: V-Sekai Game Launcher",
+    "objectID": "decisions/20231112-validation-service.html#problem",
+    "href": "decisions/20231112-validation-service.html#problem",
+    "title": "Proposed: Validator Service for V-Sekai",
     "section": "",
-    "text": "Simplified distribution: The launcher will handle the distribution of the game, making it easier for users to access and install the game.\nImproved dependency management: The launcher will also manage the game’s dependencies, resolving the current issues faced due to the lack of a package manager.\nEnhanced user experience: With the launcher handling package and project management, users can focus on creating content or playing the game."
+    "text": "The current backend system lacks a mechanism to validate scenes, count triangles, convert GLTF to Godot scene, and strip bad code from Godot scenes. This can lead to errors and inefficiencies in the development process."
   },
   {
-    "objectID": "decisions/20240305-v-sekai-launcher.html#the-downsides",
-    "href": "decisions/20240305-v-sekai-launcher.html#the-downsides",
-    "title": "Proposed: V-Sekai Game Launcher",
+    "objectID": "decisions/20231112-validation-service.html#proposed-solution",
+    "href": "decisions/20231112-validation-service.html#proposed-solution",
+    "title": "Proposed: Validator Service for V-Sekai",
     "section": "",
-    "text": "Development time: Building a new launcher will require additional development time and resources.\nUser adoption: Users may need time to adapt to the new launcher and its functionalities."
+    "text": "The proposed solution is to create a validator service that conforms to a specific specification. This service would:\n\nConvert GLTF to Godot scene.\nGo over the scene and print the number of triangles.\nIf necessary, run LOD on the scene.\nRun a validation that strips the bad code from the Godot scene.\nUse websockets and an API for communication and function calls.\n\nThe front-end for this service could be a CLI that calls the function locally. The asset service would call the validator service, which would then notify the websocket service via its API call."
   },
   {
-    "objectID": "decisions/20240305-v-sekai-launcher.html#the-road-not-taken",
-    "href": "decisions/20240305-v-sekai-launcher.html#the-road-not-taken",
-    "title": "Proposed: V-Sekai Game Launcher",
+    "objectID": "decisions/20231112-validation-service.html#benefits",
+    "href": "decisions/20231112-validation-service.html#benefits",
+    "title": "Proposed: Validator Service for V-Sekai",
     "section": "",
-    "text": "An alternative solution considered was to use the Godot Asset Store for distribution. However, it does not solve the dependency management problem and is not ready yet for such a task."
+    "text": "Implementing this validator service would provide several benefits:\n\nImproved accuracy and efficiency in the development process.\nEnhanced error detection and prevention.\nStreamlined communication between different parts of the system."
   },
   {
-    "objectID": "decisions/20240305-v-sekai-launcher.html#the-infrequent-use-case",
-    "href": "decisions/20240305-v-sekai-launcher.html#the-infrequent-use-case",
-    "title": "Proposed: V-Sekai Game Launcher",
+    "objectID": "decisions/20231112-validation-service.html#potential-downsides",
+    "href": "decisions/20231112-validation-service.html#potential-downsides",
+    "title": "Proposed: Validator Service for V-Sekai",
     "section": "",
-    "text": "In cases where users want to manage their packages manually or prefer using the regular Godot project manager, they may find the launcher unnecessary or intrusive."
+    "text": "Potential challenges or downsides could include:\n\nComplexity in setting up and maintaining the validator service.\nNeed for thorough testing to ensure the validator service works as expected."
   },
   {
-    "objectID": "decisions/20240305-v-sekai-launcher.html#in-core-and-done-by-us",
-    "href": "decisions/20240305-v-sekai-launcher.html#in-core-and-done-by-us",
-    "title": "Proposed: V-Sekai Game Launcher",
+    "objectID": "decisions/20231112-validation-service.html#alternatives-considered",
+    "href": "decisions/20231112-validation-service.html#alternatives-considered",
+    "title": "Proposed: Validator Service for V-Sekai",
     "section": "",
-    "text": "The V-Sekai development team will develop the V-Sekai Game Launcher."
+    "text": "An alternative approach could be to use gdscript + webrtc instead of websockets + API for communication and function calls. However, this would need to be evaluated for feasibility and efficiency."
   },
   {
-    "objectID": "decisions/20240305-v-sekai-launcher.html#status",
-    "href": "decisions/20240305-v-sekai-launcher.html#status",
-    "title": "Proposed: V-Sekai Game Launcher",
+    "objectID": "decisions/20231112-validation-service.html#next-steps",
+    "href": "decisions/20231112-validation-service.html#next-steps",
+    "title": "Proposed: Validator Service for V-Sekai",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "The next steps would be to:\n\nFinalize the specification for the validator service.\nDevelop the validator service according to the agreed-upon specification.\nTest the validator service thoroughly to ensure it works as expected.\nImplement the validator service in the V-Sekai system."
   },
   {
-    "objectID": "decisions/20240305-v-sekai-launcher.html#decision-makers",
-    "href": "decisions/20240305-v-sekai-launcher.html#decision-makers",
-    "title": "Proposed: V-Sekai Game Launcher",
+    "objectID": "decisions/20231112-validation-service.html#references",
+    "href": "decisions/20231112-validation-service.html#references",
+    "title": "Proposed: Validator Service for V-Sekai",
     "section": "",
-    "text": "V-Sekai development team and community stakeholders."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nThis proposal was assisted by AI assistant Aria."
   },
   {
-    "objectID": "decisions/20240305-v-sekai-launcher.html#tags",
-    "href": "decisions/20240305-v-sekai-launcher.html#tags",
-    "title": "Proposed: V-Sekai Game Launcher",
+    "objectID": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html",
+    "href": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html",
+    "title": "Draft: Use single player WebXR in Godot Engine to prototype CASSIE.",
     "section": "",
-    "text": "V-Sekai, Avatar Customization, AI, Facial Expressions, Game Launcher"
+    "text": "Status: draft \nDeciders: V-Sekai,fire\nTags: V-Sekai,\n\n\n\nWant to prototype a drawing environment in vr for the web.\nUnable to commit much resources.\n\n\n\nUse a fork of Godot 3.4 for WebXR that includes delauney tetrahedralization processing.\nPostponed until Godot Engine master has WebXR\n\n\n\n\nExtract geometry class from Godot Engine 4.0 to 3.4.\n\n\n\n\n\nStable\n\n\n\n\n\nSlower than Godot Engine master\n\n\n\n\n\nOption: Godot master as of 2021-11-05\nRejection Reason: Godot Master doesn’t have WebXR on this date.\n\n\n\n\nThis is a project proposal.\n\n\n\nI found an approach to do it.\n\n\n\n\nhttps://godotengine.org/news\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240305-v-sekai-launcher.html#further-reading",
-    "href": "decisions/20240305-v-sekai-launcher.html#further-reading",
-    "title": "Proposed: V-Sekai Game Launcher",
+    "objectID": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html#context-and-problem-statement",
+    "href": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html#context-and-problem-statement",
+    "title": "Draft: Use single player WebXR in Godot Engine to prototype CASSIE.",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this proposal."
+    "text": "Want to prototype a drawing environment in vr for the web.\nUnable to commit much resources."
   },
   {
-    "objectID": "decisions/20240613-training-dataset.html",
-    "href": "decisions/20240613-training-dataset.html",
-    "title": "Proposed: Dataset Scaling for Training Mesh Transformer",
+    "objectID": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Draft: Use single player WebXR in Godot Engine to prototype CASSIE.",
     "section": "",
-    "text": "We are working on training a mesh transformer to create 3D avatar characters. The avatars are represented using quads, and we aim to keep the quad count to 1024 or less.\n\n\n\nThe question at hand is determining the size of the dataset needed for training the model effectively.\n\n\n\nThe size of the dataset required for training a model effectively depends on the desired type of outputs from the model.\n\nGeneric Outputs: If the goal is to have the model generate outputs that it has already seen during training, a smaller dataset is sufficient. In this case, a dataset size in the range of 2,000 to 10,000 would be appropriate.\nNovel Outputs: On the other hand, if the aim is for the model to generate novel or never-seen-before outputs, a larger dataset is necessary. Here, a dataset size between 10,000 and 100,000 would be more suitable.\n\n\n\n\n\nA smaller dataset is easier to manage and requires less computational resources for training.\nA larger dataset allows the model to generate novel outputs, enhancing its creativity and versatility.\n\n\n\n\n\nA smaller dataset might limit the model’s ability to generate novel outputs.\nA larger dataset requires more computational resources for training and may lead to longer training times.\n\n\n\n\n\nWe could have chosen to use a fixed dataset size without considering the type of outputs we want from the model.\n\n\n\n\n\nThis approach may not be suitable if we want the model to generate both generic and novel outputs equally well.\n\n\n\n\n\nThe decision on the dataset size and the training of the mesh transformer will be done by us, using our acquired resources and expertise.\n\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\niFire\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "Use a fork of Godot 3.4 for WebXR that includes delauney tetrahedralization processing.\nPostponed until Godot Engine master has WebXR"
   },
   {
-    "objectID": "decisions/20240613-training-dataset.html#the-context",
-    "href": "decisions/20240613-training-dataset.html#the-context",
-    "title": "Proposed: Dataset Scaling for Training Mesh Transformer",
+    "objectID": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Draft: Use single player WebXR in Godot Engine to prototype CASSIE.",
     "section": "",
-    "text": "We are working on training a mesh transformer to create 3D avatar characters. The avatars are represented using quads, and we aim to keep the quad count to 1024 or less."
+    "text": "Extract geometry class from Godot Engine 4.0 to 3.4."
   },
   {
-    "objectID": "decisions/20240613-training-dataset.html#the-problem-statement",
-    "href": "decisions/20240613-training-dataset.html#the-problem-statement",
-    "title": "Proposed: Dataset Scaling for Training Mesh Transformer",
+    "objectID": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html#positive-consequences",
+    "href": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html#positive-consequences",
+    "title": "Draft: Use single player WebXR in Godot Engine to prototype CASSIE.",
     "section": "",
-    "text": "The question at hand is determining the size of the dataset needed for training the model effectively."
+    "text": "Stable"
   },
   {
-    "objectID": "decisions/20240613-training-dataset.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240613-training-dataset.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Dataset Scaling for Training Mesh Transformer",
+    "objectID": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html#negative-consequences",
+    "href": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html#negative-consequences",
+    "title": "Draft: Use single player WebXR in Godot Engine to prototype CASSIE.",
     "section": "",
-    "text": "The size of the dataset required for training a model effectively depends on the desired type of outputs from the model.\n\nGeneric Outputs: If the goal is to have the model generate outputs that it has already seen during training, a smaller dataset is sufficient. In this case, a dataset size in the range of 2,000 to 10,000 would be appropriate.\nNovel Outputs: On the other hand, if the aim is for the model to generate novel or never-seen-before outputs, a larger dataset is necessary. Here, a dataset size between 10,000 and 100,000 would be more suitable."
+    "text": "Slower than Godot Engine master"
   },
   {
-    "objectID": "decisions/20240613-training-dataset.html#the-benefits",
-    "href": "decisions/20240613-training-dataset.html#the-benefits",
-    "title": "Proposed: Dataset Scaling for Training Mesh Transformer",
+    "objectID": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html#option-graveyard",
+    "href": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html#option-graveyard",
+    "title": "Draft: Use single player WebXR in Godot Engine to prototype CASSIE.",
     "section": "",
-    "text": "A smaller dataset is easier to manage and requires less computational resources for training.\nA larger dataset allows the model to generate novel outputs, enhancing its creativity and versatility."
+    "text": "Option: Godot master as of 2021-11-05\nRejection Reason: Godot Master doesn’t have WebXR on this date."
   },
   {
-    "objectID": "decisions/20240613-training-dataset.html#the-downsides",
-    "href": "decisions/20240613-training-dataset.html#the-downsides",
-    "title": "Proposed: Dataset Scaling for Training Mesh Transformer",
+    "objectID": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Draft: Use single player WebXR in Godot Engine to prototype CASSIE.",
     "section": "",
-    "text": "A smaller dataset might limit the model’s ability to generate novel outputs.\nA larger dataset requires more computational resources for training and may lead to longer training times."
+    "text": "This is a project proposal."
   },
   {
-    "objectID": "decisions/20240613-training-dataset.html#the-road-not-taken",
-    "href": "decisions/20240613-training-dataset.html#the-road-not-taken",
-    "title": "Proposed: Dataset Scaling for Training Mesh Transformer",
+    "objectID": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Draft: Use single player WebXR in Godot Engine to prototype CASSIE.",
     "section": "",
-    "text": "We could have chosen to use a fixed dataset size without considering the type of outputs we want from the model."
+    "text": "I found an approach to do it."
   },
   {
-    "objectID": "decisions/20240613-training-dataset.html#the-infrequent-use-case",
-    "href": "decisions/20240613-training-dataset.html#the-infrequent-use-case",
-    "title": "Proposed: Dataset Scaling for Training Mesh Transformer",
+    "objectID": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html#references",
+    "href": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html#references",
+    "title": "Draft: Use single player WebXR in Godot Engine to prototype CASSIE.",
     "section": "",
-    "text": "This approach may not be suitable if we want the model to generate both generic and novel outputs equally well."
+    "text": "https://godotengine.org/news"
   },
   {
-    "objectID": "decisions/20240613-training-dataset.html#in-core-and-done-by-us",
-    "href": "decisions/20240613-training-dataset.html#in-core-and-done-by-us",
-    "title": "Proposed: Dataset Scaling for Training Mesh Transformer",
+    "objectID": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html#derivative-license",
+    "href": "decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html#derivative-license",
+    "title": "Draft: Use single player WebXR in Godot Engine to prototype CASSIE.",
     "section": "",
-    "text": "The decision on the dataset size and the training of the mesh transformer will be done by us, using our acquired resources and expertise."
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240613-training-dataset.html#status",
-    "href": "decisions/20240613-training-dataset.html#status",
-    "title": "Proposed: Dataset Scaling for Training Mesh Transformer",
+    "objectID": "decisions/20220901-mirror-extend-asset-library-packages.html",
+    "href": "decisions/20220901-mirror-extend-asset-library-packages.html",
+    "title": "Proposed: Extended asset library packages in addition to the upstream asset library",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "Proposed: Extended asset library packages in addition to the upstream asset library\n\nContext and Problem Statement\nHave a way to deploy custom asset libs via the godot engine asset library ui\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nWe propose to use the V-Sekai uro server to provide an asset library url to Godot Engine.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nImplement\n\nrest passthrough https://github.com/godotengine/godot-asset-library/blob/master/API.md\naccount based package bundles (does not include the original package, only the metadata)\n\n\n\nPositive Consequences\nWe can have our own asset archives.\n\n\nNegative Consequences\nMay compromise security.\n\n\nOption graveyard\nUpload to the asset library directly.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot a few lines of script.\n\n\nIs there a reason why this should be core and done by us?\nWe maintain uro.\n\n\nReferences\n\nV-Sekai\n\n\n\nLicense of the contribution\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240613-training-dataset.html#decision-makers",
-    "href": "decisions/20240613-training-dataset.html#decision-makers",
-    "title": "Proposed: Dataset Scaling for Training Mesh Transformer",
+    "objectID": "decisions/20240121-livebook-fedora-install.html",
+    "href": "decisions/20240121-livebook-fedora-install.html",
+    "title": "Proposed: Elixir Livebook on Fedora 39",
     "section": "",
-    "text": "V-Sekai development team\niFire"
+    "text": "Status: Proposed\nDeciders: V-Sekai Team\nTags: Elixir, Livebook, Fedora 39\n\n\n\n\nThe goal is to utilize Elixir NX for data science and numerical computing applications relevant to V-Sekai.\n\n\n\nThe challenge lies in ensuring a successful installation and configuration of Elixir Livebook on Fedora 39, which will serve as a development platform.\n\n\n\n\nAssess compatibility between Elixir Livebook and Fedora 39.\nIdentify all dependencies required for Elixir Livebook.\nDevelop comprehensive guidelines for the installation process.\nConduct a test run of the install procedure on a Fedora 39 system.\n\nCreate a dedicated user for running Livebook and determine an appropriate location for the installation, such as /opt/livebook.\nsudo yum groupinstall -y 'Development Tools' 'C Development Tools and Libraries'\nsudo dnf install -y \\\n  autoconf \\\n  ncurses-devel \\\n  wxGTK3-devel \\\n  wxBase3 \\\n  openssl-devel \\\n  java-1.8.0-openjdk-devel \\\n  libiodbc \\\n  unixODBC-devel.x86_64 \\\n  erlang-odbc.x86_64 \\\n  libxslt \\\n  fop \\\n  automake \\\n  readline-devel \\\n  git \\\n  gcc \\\n  unzip \\\n  curl\nsudo dnf copr enable vbatts/bazel -y && dnf install bazel5 -y\nsudo dnf install akmod-nvidia xorg-x11-drv-nvidia-cuda -y\n\n# As root or using sudo\nuseradd --system --create-home --home-dir /opt/livebook livebook\nchown -R livebook: /opt/livebook\nsu - livebook\ncd /opt/livebook\ngit clone https://github.com/asdf-vm/asdf.git ~/.asdf\necho -e '\\n. $HOME/.asdf/asdf.sh' &gt;&gt; ~/.bashrc\necho -e '\\n. $HOME/.asdf/completions/asdf.bash' &gt;&gt; ~/.bashrc\nsource ~/.bashrc\nasdf plugin-add erlang https://github.com/asdf-vm/asdf-erlang.git\nasdf install erlang 26.2.1\nasdf global erlang 26.2.1\nasdf plugin-add elixir https://github.com/asdf-vm/asdf-elixir.git\nasdf install elixir 1.16-otp-26\nasdf global elixir 1.16-otp-26\nerl -version\nelixir -v\nmix do local.rebar --force, local.hex --force\nmix escript.install hex livebook --force\nTo insert or overwrite the existing systemd service configuration for Elixir Livebook directly from the shell, you can use the following commands:\nFirst, open your terminal and use cat combined with a here-document to overwrite the file with the new configuration:\nsudo cat &gt; /etc/systemd/system/livebook.service &lt;&lt;EOF\n[Unit]\nDescription=Elixir Livebook server\nAfter=network.target\n\n[Service]\nUser=livebook\nWorkingDirectory=/opt/livebook\nExecStart=/bin/bash -c '. /opt/livebook/.asdf/asdf.sh && exec /opt/livebook/.asdf/installs/elixir/1.16-otp-26/.mix/escripts/livebook server'\nEnvironment=MIX_ENV=prod\nEnvironment=LIVEBOOK_PORT=8080\nEnvironment=LIVEBOOK_IP=0.0.0.0\nEnvironment=LIVEBOOK_HOME=/opt/livebook\nRestart=on-failure\n\n[Install]\nWantedBy=multi-user.target\nEOF\nEnsure that you have the necessary permissions to write to /etc/systemd/system/.\nAfter saving the file, reload systemd to apply the changes:\nsudo systemctl daemon-reload\nsudo systemctl enable livebook.service\nsudo systemctl restart livebook.service\nVerify that the service is running correctly with:\nsudo systemctl status livebook.service # Check this for the authentication token.\nDebug the service with journalctl.\nsudo journalctl -u livebook.service\nRemember to adjust the path specified in the ExecStart directive if required and set any additional environment variables as needed.\n\n\n\n\nProvides a real-time collaborative tool for Elixir development.\nHelps in verifying Elixir NX’s capabilities through visualization.\nStreamlines the code development cycle with instant feedback.\n\n\n\n\n\nTime allocation needed for the seamless functioning of Livebook on Fedora 39.\nDependencies might add a layer of complexity in ongoing maintenance.\nThe initial setup could pose challenges for non-expert users.\n\n\n\n\nOther tools and languages were assessed but did not fulfill V-Sekai’s requirements as effectively as Elixir Livebook.\n\n\n\nEvaluating occasional usage to justify the demand for an efficient installation approach.\n\n\n\nDetermining if this integration should be centralized within V-Sekai’s primary offerings and whether internal resources can achieve this implementation.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account of V-Sekai’s developer community.\nV-Sekai/v-sekai-game - Repository dedicated to V-Sekai’s project for merging social VR and metaverse elements with Godot Engine.\n\nAria, an AI assistant, contributed to the drafting of this proposal."
   },
   {
-    "objectID": "decisions/20240613-training-dataset.html#tags",
-    "href": "decisions/20240613-training-dataset.html#tags",
-    "title": "Proposed: Dataset Scaling for Training Mesh Transformer",
+    "objectID": "decisions/20240121-livebook-fedora-install.html#metadata",
+    "href": "decisions/20240121-livebook-fedora-install.html#metadata",
+    "title": "Proposed: Elixir Livebook on Fedora 39",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Status: Proposed\nDeciders: V-Sekai Team\nTags: Elixir, Livebook, Fedora 39"
   },
   {
-    "objectID": "decisions/20240613-training-dataset.html#further-reading",
-    "href": "decisions/20240613-training-dataset.html#further-reading",
-    "title": "Proposed: Dataset Scaling for Training Mesh Transformer",
+    "objectID": "decisions/20240121-livebook-fedora-install.html#backdrop",
+    "href": "decisions/20240121-livebook-fedora-install.html#backdrop",
+    "title": "Proposed: Elixir Livebook on Fedora 39",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "The goal is to utilize Elixir NX for data science and numerical computing applications relevant to V-Sekai."
   },
   {
-    "objectID": "decisions/20230823-speech-to-blendshapes.html",
-    "href": "decisions/20230823-speech-to-blendshapes.html",
-    "title": "Proposed: Developing a Unified Model for Speech-to-Facial Shape Generation Using Outlines 〰 Library",
+    "objectID": "decisions/20240121-livebook-fedora-install.html#challenge",
+    "href": "decisions/20240121-livebook-fedora-install.html#challenge",
+    "title": "Proposed: Elixir Livebook on Fedora 39",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nV-Sekai is embarking on a project that translates speech into corresponding facial shapes for virtual reality applications. This process eliminates the need for a face camera and leverages the SpeechEncoderDecoderModel from Hugging Face’s Transformers library for comprehensive speech recognition.\nThe SpeakingFaces dataset, a collection from 142 diverse subjects, will be utilized for this project. The dataset is accessible via the server of the Institute for Smart Systems and Artificial Intelligence (ISSAI) under the Creative Commons Attribution 4.0 International License.\nOutlines 〰, a neural text generation library, will also play a crucial role in this project. It offers robust prompting primitives, separates the prompting from the execution logic, and is compatible with all models. It interfaces with models through the next-token logits and can be used with API-based models as well.\n\n\n\nThe primary challenge lies in developing a model capable of generating text and blendshapes simultaneously from the same input speech using the Outlines 〰 library.\n\n\n\nThe proposed strategy involves creating a custom model that accepts speech as input and outputs both text and blendshapes. This unified model would incorporate a shared encoder to process the speech input, and a single decoder to generate the text and blendshape outputs. The Outlines 〰 library will be used to conform the output to the desired format.\nfrom outlines import Outline\nfrom transformers import SpeechEncoderDecoderModel, Speech2Text2Processor, Wav2Vec2Model\nimport json\n\n# Initialize the processor and encoder\nprocessor = Speech2Text2Processor.from_pretrained(\"facebook/s2t-small-librispeech-asr\")\nencoder = Wav2Vec2Model.from_pretrained(\"facebook/wav2vec2-base-960h\")\n\n# Initialize the decoder\ndecoder = Speech2Text2Model.from_pretrained(\"facebook/s2t-small-librispeech-asr\")\n\n# Initialize the unified model\nmodel = UnifiedSpeechEncoderDecoderModel(encoder=encoder, decoder=decoder)\n\n# Define an outline for the model\noutline = Outline(model).to(device)\n\n# Generate text and blendshapes\ngenerated_text, generated_blendshapes = outline.generate(input_speech)\n\n# Conform to JSON schemaßß\nblendshapes_keys = [\"BrowInnerUp\", \"BrowDownLeft\", \"BrowDownRight\", \"BrowOuterUpLeft\", \"BrowOuterUpRight\",\n                    \"EyeLookUpLeft\", \"EyeLookUpRight\", \"EyeLookDownLeft\", \"EyeLookDownRight\", \"EyeLookInLeft\",\n                    \"EyeLookInRight\", \"EyeLookOutLeft\", \"EyeLookOutRight\", \"EyeBlinkLeft\", \"EyeBlinkRight\",\n                    \"EyeSquintRight\", \"EyeSquintLeft\", \"EyeWideLeft\", \"EyeWideRight\", \"CheekPuff\",\n                    \"CheekSquintLeft\", \"CheekSquintRight\", \"NoseSneerLeft\", \"NoseSneerRight\", \"JawOpen\",\n                    \"JawForward\", \"JawLeft\", \"JawRight\", \"MouthFunnel\", \"MouthPucker\", \"MouthLeft\",\n                    \"MouthRight\", \"MouthRollUpper\", \"MouthRollLower\", \"MouthShrugUpper\", \"MouthShrugLower\",\n                    \"MouthClose\", \"MouthSmileLeft\", \"MouthSmileRight\", \"MouthFrownLeft\", \"MouthFrownRight\",\n                    \"MouthDimpleLeft\", \"MouthDimpleRight\", \"MouthUpperUpLeft\", \"MouthUpperUpRight\",\n                    \"MouthLowerDownLeft\", \"MouthLowerDownRight\", \"MouthPressLeft\", \"MouthPressRight\",\n                    \"MouthStretchLeft\", \"MouthStretchRight\", \"TongueOut\"]\n\noutput = {\n    \"text\": generated_text,\n    \"blendshapes\": dict(zip(blendshapes_keys, generated_blendshapes))\n}\n\njson_output = json.dumps(output)\n\n\n\nDeveloping our own unified model for generating both text and blendshapes from speech using the Outlines 〰 library is a strategic move that provides us with greater control and customization to meet our specific needs. It not only deepens our understanding of the model, aiding in troubleshooting and improvements, but also allows us to optimize it for better performance and efficiency.\n\n\n\nThe limitation of this approach is that the UnifiedSpeechEncoderDecoderModel, and Outline are placeholders for your actual unified model classes, and outline respectively. You would need to implement these classes yourself, or find pre-trained models that suit your needs.\n\n\n\nBeing self-reliant in maintaining and updating our model eliminates dependence on third parties, providing flexibility to make changes as needed. Moreover, it ensures seamless integration with other parts of our system.\n\n\n\nWhile this approach requires more initial effort, the potential for improvement and fine-tuning with our unique data sets makes it worthwhile, leading to superior results in the long run.\n\n\n\nYes, the development and maintenance of the unified model will be done by us.\n\n\n\n\nV-Sekai\nThis article is assisted by AI."
+    "text": "The challenge lies in ensuring a successful installation and configuration of Elixir Livebook on Fedora 39, which will serve as a development platform."
   },
   {
-    "objectID": "decisions/20230823-speech-to-blendshapes.html#metadata",
-    "href": "decisions/20230823-speech-to-blendshapes.html#metadata",
-    "title": "Proposed: Developing a Unified Model for Speech-to-Facial Shape Generation Using Outlines 〰 Library",
+    "objectID": "decisions/20240121-livebook-fedora-install.html#strategy",
+    "href": "decisions/20240121-livebook-fedora-install.html#strategy",
+    "title": "Proposed: Elixir Livebook on Fedora 39",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai"
+    "text": "Assess compatibility between Elixir Livebook and Fedora 39.\nIdentify all dependencies required for Elixir Livebook.\nDevelop comprehensive guidelines for the installation process.\nConduct a test run of the install procedure on a Fedora 39 system.\n\nCreate a dedicated user for running Livebook and determine an appropriate location for the installation, such as /opt/livebook.\nsudo yum groupinstall -y 'Development Tools' 'C Development Tools and Libraries'\nsudo dnf install -y \\\n  autoconf \\\n  ncurses-devel \\\n  wxGTK3-devel \\\n  wxBase3 \\\n  openssl-devel \\\n  java-1.8.0-openjdk-devel \\\n  libiodbc \\\n  unixODBC-devel.x86_64 \\\n  erlang-odbc.x86_64 \\\n  libxslt \\\n  fop \\\n  automake \\\n  readline-devel \\\n  git \\\n  gcc \\\n  unzip \\\n  curl\nsudo dnf copr enable vbatts/bazel -y && dnf install bazel5 -y\nsudo dnf install akmod-nvidia xorg-x11-drv-nvidia-cuda -y\n\n# As root or using sudo\nuseradd --system --create-home --home-dir /opt/livebook livebook\nchown -R livebook: /opt/livebook\nsu - livebook\ncd /opt/livebook\ngit clone https://github.com/asdf-vm/asdf.git ~/.asdf\necho -e '\\n. $HOME/.asdf/asdf.sh' &gt;&gt; ~/.bashrc\necho -e '\\n. $HOME/.asdf/completions/asdf.bash' &gt;&gt; ~/.bashrc\nsource ~/.bashrc\nasdf plugin-add erlang https://github.com/asdf-vm/asdf-erlang.git\nasdf install erlang 26.2.1\nasdf global erlang 26.2.1\nasdf plugin-add elixir https://github.com/asdf-vm/asdf-elixir.git\nasdf install elixir 1.16-otp-26\nasdf global elixir 1.16-otp-26\nerl -version\nelixir -v\nmix do local.rebar --force, local.hex --force\nmix escript.install hex livebook --force\nTo insert or overwrite the existing systemd service configuration for Elixir Livebook directly from the shell, you can use the following commands:\nFirst, open your terminal and use cat combined with a here-document to overwrite the file with the new configuration:\nsudo cat &gt; /etc/systemd/system/livebook.service &lt;&lt;EOF\n[Unit]\nDescription=Elixir Livebook server\nAfter=network.target\n\n[Service]\nUser=livebook\nWorkingDirectory=/opt/livebook\nExecStart=/bin/bash -c '. /opt/livebook/.asdf/asdf.sh && exec /opt/livebook/.asdf/installs/elixir/1.16-otp-26/.mix/escripts/livebook server'\nEnvironment=MIX_ENV=prod\nEnvironment=LIVEBOOK_PORT=8080\nEnvironment=LIVEBOOK_IP=0.0.0.0\nEnvironment=LIVEBOOK_HOME=/opt/livebook\nRestart=on-failure\n\n[Install]\nWantedBy=multi-user.target\nEOF\nEnsure that you have the necessary permissions to write to /etc/systemd/system/.\nAfter saving the file, reload systemd to apply the changes:\nsudo systemctl daemon-reload\nsudo systemctl enable livebook.service\nsudo systemctl restart livebook.service\nVerify that the service is running correctly with:\nsudo systemctl status livebook.service # Check this for the authentication token.\nDebug the service with journalctl.\nsudo journalctl -u livebook.service\nRemember to adjust the path specified in the ExecStart directive if required and set any additional environment variables as needed."
   },
   {
-    "objectID": "decisions/20230823-speech-to-blendshapes.html#the-backdrop",
-    "href": "decisions/20230823-speech-to-blendshapes.html#the-backdrop",
-    "title": "Proposed: Developing a Unified Model for Speech-to-Facial Shape Generation Using Outlines 〰 Library",
+    "objectID": "decisions/20240121-livebook-fedora-install.html#upside",
+    "href": "decisions/20240121-livebook-fedora-install.html#upside",
+    "title": "Proposed: Elixir Livebook on Fedora 39",
     "section": "",
-    "text": "V-Sekai is embarking on a project that translates speech into corresponding facial shapes for virtual reality applications. This process eliminates the need for a face camera and leverages the SpeechEncoderDecoderModel from Hugging Face’s Transformers library for comprehensive speech recognition.\nThe SpeakingFaces dataset, a collection from 142 diverse subjects, will be utilized for this project. The dataset is accessible via the server of the Institute for Smart Systems and Artificial Intelligence (ISSAI) under the Creative Commons Attribution 4.0 International License.\nOutlines 〰, a neural text generation library, will also play a crucial role in this project. It offers robust prompting primitives, separates the prompting from the execution logic, and is compatible with all models. It interfaces with models through the next-token logits and can be used with API-based models as well."
+    "text": "Provides a real-time collaborative tool for Elixir development.\nHelps in verifying Elixir NX’s capabilities through visualization.\nStreamlines the code development cycle with instant feedback."
   },
   {
-    "objectID": "decisions/20230823-speech-to-blendshapes.html#the-challenge",
-    "href": "decisions/20230823-speech-to-blendshapes.html#the-challenge",
-    "title": "Proposed: Developing a Unified Model for Speech-to-Facial Shape Generation Using Outlines 〰 Library",
+    "objectID": "decisions/20240121-livebook-fedora-install.html#downside",
+    "href": "decisions/20240121-livebook-fedora-install.html#downside",
+    "title": "Proposed: Elixir Livebook on Fedora 39",
     "section": "",
-    "text": "The primary challenge lies in developing a model capable of generating text and blendshapes simultaneously from the same input speech using the Outlines 〰 library."
+    "text": "Time allocation needed for the seamless functioning of Livebook on Fedora 39.\nDependencies might add a layer of complexity in ongoing maintenance.\nThe initial setup could pose challenges for non-expert users."
   },
   {
-    "objectID": "decisions/20230823-speech-to-blendshapes.html#the-strategy",
-    "href": "decisions/20230823-speech-to-blendshapes.html#the-strategy",
-    "title": "Proposed: Developing a Unified Model for Speech-to-Facial Shape Generation Using Outlines 〰 Library",
+    "objectID": "decisions/20240121-livebook-fedora-install.html#road-not-taken",
+    "href": "decisions/20240121-livebook-fedora-install.html#road-not-taken",
+    "title": "Proposed: Elixir Livebook on Fedora 39",
     "section": "",
-    "text": "The proposed strategy involves creating a custom model that accepts speech as input and outputs both text and blendshapes. This unified model would incorporate a shared encoder to process the speech input, and a single decoder to generate the text and blendshape outputs. The Outlines 〰 library will be used to conform the output to the desired format.\nfrom outlines import Outline\nfrom transformers import SpeechEncoderDecoderModel, Speech2Text2Processor, Wav2Vec2Model\nimport json\n\n# Initialize the processor and encoder\nprocessor = Speech2Text2Processor.from_pretrained(\"facebook/s2t-small-librispeech-asr\")\nencoder = Wav2Vec2Model.from_pretrained(\"facebook/wav2vec2-base-960h\")\n\n# Initialize the decoder\ndecoder = Speech2Text2Model.from_pretrained(\"facebook/s2t-small-librispeech-asr\")\n\n# Initialize the unified model\nmodel = UnifiedSpeechEncoderDecoderModel(encoder=encoder, decoder=decoder)\n\n# Define an outline for the model\noutline = Outline(model).to(device)\n\n# Generate text and blendshapes\ngenerated_text, generated_blendshapes = outline.generate(input_speech)\n\n# Conform to JSON schemaßß\nblendshapes_keys = [\"BrowInnerUp\", \"BrowDownLeft\", \"BrowDownRight\", \"BrowOuterUpLeft\", \"BrowOuterUpRight\",\n                    \"EyeLookUpLeft\", \"EyeLookUpRight\", \"EyeLookDownLeft\", \"EyeLookDownRight\", \"EyeLookInLeft\",\n                    \"EyeLookInRight\", \"EyeLookOutLeft\", \"EyeLookOutRight\", \"EyeBlinkLeft\", \"EyeBlinkRight\",\n                    \"EyeSquintRight\", \"EyeSquintLeft\", \"EyeWideLeft\", \"EyeWideRight\", \"CheekPuff\",\n                    \"CheekSquintLeft\", \"CheekSquintRight\", \"NoseSneerLeft\", \"NoseSneerRight\", \"JawOpen\",\n                    \"JawForward\", \"JawLeft\", \"JawRight\", \"MouthFunnel\", \"MouthPucker\", \"MouthLeft\",\n                    \"MouthRight\", \"MouthRollUpper\", \"MouthRollLower\", \"MouthShrugUpper\", \"MouthShrugLower\",\n                    \"MouthClose\", \"MouthSmileLeft\", \"MouthSmileRight\", \"MouthFrownLeft\", \"MouthFrownRight\",\n                    \"MouthDimpleLeft\", \"MouthDimpleRight\", \"MouthUpperUpLeft\", \"MouthUpperUpRight\",\n                    \"MouthLowerDownLeft\", \"MouthLowerDownRight\", \"MouthPressLeft\", \"MouthPressRight\",\n                    \"MouthStretchLeft\", \"MouthStretchRight\", \"TongueOut\"]\n\noutput = {\n    \"text\": generated_text,\n    \"blendshapes\": dict(zip(blendshapes_keys, generated_blendshapes))\n}\n\njson_output = json.dumps(output)"
+    "text": "Other tools and languages were assessed but did not fulfill V-Sekai’s requirements as effectively as Elixir Livebook."
   },
   {
-    "objectID": "decisions/20230823-speech-to-blendshapes.html#the-upside",
-    "href": "decisions/20230823-speech-to-blendshapes.html#the-upside",
-    "title": "Proposed: Developing a Unified Model for Speech-to-Facial Shape Generation Using Outlines 〰 Library",
+    "objectID": "decisions/20240121-livebook-fedora-install.html#infrequent-use-case",
+    "href": "decisions/20240121-livebook-fedora-install.html#infrequent-use-case",
+    "title": "Proposed: Elixir Livebook on Fedora 39",
     "section": "",
-    "text": "Developing our own unified model for generating both text and blendshapes from speech using the Outlines 〰 library is a strategic move that provides us with greater control and customization to meet our specific needs. It not only deepens our understanding of the model, aiding in troubleshooting and improvements, but also allows us to optimize it for better performance and efficiency."
+    "text": "Evaluating occasional usage to justify the demand for an efficient installation approach."
   },
   {
-    "objectID": "decisions/20230823-speech-to-blendshapes.html#the-downside",
-    "href": "decisions/20230823-speech-to-blendshapes.html#the-downside",
-    "title": "Proposed: Developing a Unified Model for Speech-to-Facial Shape Generation Using Outlines 〰 Library",
+    "objectID": "decisions/20240121-livebook-fedora-install.html#in-core-and-done-by-us",
+    "href": "decisions/20240121-livebook-fedora-install.html#in-core-and-done-by-us",
+    "title": "Proposed: Elixir Livebook on Fedora 39",
     "section": "",
-    "text": "The limitation of this approach is that the UnifiedSpeechEncoderDecoderModel, and Outline are placeholders for your actual unified model classes, and outline respectively. You would need to implement these classes yourself, or find pre-trained models that suit your needs."
+    "text": "Determining if this integration should be centralized within V-Sekai’s primary offerings and whether internal resources can achieve this implementation."
   },
   {
-    "objectID": "decisions/20230823-speech-to-blendshapes.html#the-road-not-taken",
-    "href": "decisions/20230823-speech-to-blendshapes.html#the-road-not-taken",
-    "title": "Proposed: Developing a Unified Model for Speech-to-Facial Shape Generation Using Outlines 〰 Library",
+    "objectID": "decisions/20240121-livebook-fedora-install.html#further-reading",
+    "href": "decisions/20240121-livebook-fedora-install.html#further-reading",
+    "title": "Proposed: Elixir Livebook on Fedora 39",
     "section": "",
-    "text": "Being self-reliant in maintaining and updating our model eliminates dependence on third parties, providing flexibility to make changes as needed. Moreover, it ensures seamless integration with other parts of our system."
+    "text": "V-Sekai · GitHub - Official GitHub account of V-Sekai’s developer community.\nV-Sekai/v-sekai-game - Repository dedicated to V-Sekai’s project for merging social VR and metaverse elements with Godot Engine.\n\nAria, an AI assistant, contributed to the drafting of this proposal."
   },
   {
-    "objectID": "decisions/20230823-speech-to-blendshapes.html#the-infrequent-use-case",
-    "href": "decisions/20230823-speech-to-blendshapes.html#the-infrequent-use-case",
-    "title": "Proposed: Developing a Unified Model for Speech-to-Facial Shape Generation Using Outlines 〰 Library",
+    "objectID": "decisions/20210715-portable-world-content.html",
+    "href": "decisions/20210715-portable-world-content.html",
+    "title": "Proposed: Portable #world Content",
     "section": "",
-    "text": "While this approach requires more initial effort, the potential for improvement and fine-tuning with our unique data sets makes it worthwhile, leading to superior results in the long run."
+    "text": "Proposed: Portable #world Content\n\nContext and Problem Statement\nIndependent meta-verses (virtual worlds) lack content because their communities are too small to fund much content work.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nCollaborate with Mozilla Hub’s Spoke Editor and OMI Group’s glTF2 extensions to have portable #world content.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nProvide basic glTF2 extensions. Here is an initial list.\n\nURI scene linking\nArchive binary format\nAudio emitters\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nThere are many moving parts and a web client, which is not a few lines of code.\n\n\nPositive Consequences\n\nEasier creation of new virtual worlds.\nEncourage remixing content\nKeeping old content portable to new virtual #world\n\n\n\nNegative Consequences\n\nHave to find different monetization means for independent virtual #world\n\n\n\nIs there a reason why this should be core and done by us?\nNo one is doing it.\n\n\nReferences\n\nhttps://github.com/ubisoft/mixer/issues/19\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230823-speech-to-blendshapes.html#in-core-and-done-by-us",
-    "href": "decisions/20230823-speech-to-blendshapes.html#in-core-and-done-by-us",
-    "title": "Proposed: Developing a Unified Model for Speech-to-Facial Shape Generation Using Outlines 〰 Library",
+    "objectID": "decisions/20210212-use-markdown-architectural-decision-records.html",
+    "href": "decisions/20210212-use-markdown-architectural-decision-records.html",
+    "title": "Accepted: Use Markdown Architectural Decision Records",
     "section": "",
-    "text": "Yes, the development and maintenance of the unified model will be done by us."
+    "text": "Status: accepted\nDate: 2021-02-11\nTags: doc\n\n\n\nWe want to record architectural decisions made in this project. Which format and structure should these records follow?\n\n\n\n\nMADR 2.1.2 with Log4brains patch\nMADR 2.1.2 – The original Markdown Architectural Decision Records\nMichael Nygard’s template – The first incarnation of the term “ADR”\nSustainable Architectural Decisions – The Y-Statements\nOther templates listed at https://github.com/joelparkerhenderson/architecture_decision_record\nFormless – No conventions for file format and structure\n\n\n\n\nChosen option: “MADR 2.1.2 with Log4brains patch”, because\n\nImplicit assumptions should be made explicit. Design documentation is important to enable people understanding the decisions later on. See also A rational design process: How and why to fake it.\nThe MADR format is lean and fits our development style.\nThe MADR structure is comprehensible and facilitates usage & maintenance.\nThe MADR project is vivid.\nVersion 2.1.2 is the latest one available when starting to document ADRs.\nThe Log4brains patch adds more features, like tags.\n\nThe “Log4brains patch” performs the following modifications to the original template:\n\nChange the ADR filenames format (NNN-adr-name becomes YYYYMMDD-adr-name), to avoid conflicts during Git merges.\nAdd a draft status, to enable collaborative writing.\nAdd a Tags field.\n\n\n\n\n\nRelates to Use Log4brains to manage the ADRs\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230823-speech-to-blendshapes.html#further-reading",
-    "href": "decisions/20230823-speech-to-blendshapes.html#further-reading",
-    "title": "Proposed: Developing a Unified Model for Speech-to-Facial Shape Generation Using Outlines 〰 Library",
+    "objectID": "decisions/20210212-use-markdown-architectural-decision-records.html#context-and-problem-statement",
+    "href": "decisions/20210212-use-markdown-architectural-decision-records.html#context-and-problem-statement",
+    "title": "Accepted: Use Markdown Architectural Decision Records",
     "section": "",
-    "text": "V-Sekai\nThis article is assisted by AI."
+    "text": "We want to record architectural decisions made in this project. Which format and structure should these records follow?"
   },
   {
-    "objectID": "decisions/20211031-extract-proposals-into-proposals.html",
-    "href": "decisions/20211031-extract-proposals-into-proposals.html",
-    "title": "Proposed: Extract proposals into proposals",
+    "objectID": "decisions/20210212-use-markdown-architectural-decision-records.html#considered-options",
+    "href": "decisions/20210212-use-markdown-architectural-decision-records.html#considered-options",
+    "title": "Accepted: Use Markdown Architectural Decision Records",
     "section": "",
-    "text": "Proposed: Extract proposals into proposals\n\nContext and Problem Statement\nDecision trees are hard to use\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nConvert items in a decision tree into proposals\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n\n\n\n\n\n\n\n\nName\nDescription\nTask Stage\n\n\n\n\nGLTF #materialx\n\nidea\n\n\nGodot CASSIE\n\nidea\n\n\nElixir membrane gltf processor\n\nidea\n\n\nGodot Dem Bones\nConvert blend shapes to skeletal animation\nidea\n\n\nrobust-voip\nvoip or audio problems?\nidea\n\n\nCVTT\nAllow the use of BC6 and BC7 instead of DXT5.\nidea\n\n\nSpiceDB\nAuthorization\nidea\n\n\nLibcurl\nLibcurl for Godot Engine\nevaluate\n\n\nGodot OSC\nhttps://github.com/infosia/vmc2bvh\nclosed abandoned\n\n\nGLTF wasm\n\nidea\n\n\nGodot AI Planner\n\nidea\n\n\nProfile Picture taker\nBetter VRM full profile and portrait taker\nidea\n\n\nGLTF omi-audio-emitter\n\nidea\n\n\nRobust Networking\nnetworking problems: max room capacity? other unknown bandwidth limits? server hosting problems: dedicated server support? self hosting / upnp / holepunching?\nidea\n\n\nGLTF animation tree\n\nidea\n\n\n#materialx Godot Plugin\nGLTF2 #materialx BSDF\nidea\n\n\n#materialx Grid Texture Generator\n\nidea\n\n\nAvatar Customization\nhow to import avatars from various places: Only VRM? Use Blender to convert GLTF?\nidea\n\n\nV-Sekai homeroom\n\nidea\n\n\nEWBIK Json debug\nPrint EWBIK json debug\nidea\n\n\nAnimation Tree\nAnimation tree\nidea\n\n\nDecimate character to 60’000 polygons\nUse for VRCHAT https://sketchfab.com/3d-models/haveto-blue-mage-ray-tachie-dialog-5e15ae6513d74f63b7bdf5ec4ba884e6\nidea\n\n\nFlat Avatar Animation\nHow do I get an animation set to play on my V-Sekai avatar (T-Pose with correct bone rotations) Native Blender FBX? Unity? Others?\nidea\n\n\nEventful Activities\nactivities: mirrors? physics interactables? games? video players? Custom cameras? Selfie cameras?\nidea\n\n\nUDIM bake to textures\n\nidea\n\n\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot code, but ideas.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nOnly we know.\n\n\nReferences\n\nplan-V-Sekai.txt\nplan-cassie.txt\nplan_lyuma\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "MADR 2.1.2 with Log4brains patch\nMADR 2.1.2 – The original Markdown Architectural Decision Records\nMichael Nygard’s template – The first incarnation of the term “ADR”\nSustainable Architectural Decisions – The Y-Statements\nOther templates listed at https://github.com/joelparkerhenderson/architecture_decision_record\nFormless – No conventions for file format and structure"
   },
   {
-    "objectID": "decisions/20221206-export-godot-vrm-to-the-asset-library.html",
-    "href": "decisions/20221206-export-godot-vrm-to-the-asset-library.html",
-    "title": "Proposed: Prepare godot-vrm for asset library publishing",
+    "objectID": "decisions/20210212-use-markdown-architectural-decision-records.html#decision-outcome",
+    "href": "decisions/20210212-use-markdown-architectural-decision-records.html#decision-outcome",
+    "title": "Accepted: Use Markdown Architectural Decision Records",
     "section": "",
-    "text": "Status: accepted \nDeciders: V-Sekai,lyuma,fire,\nTags: V-Sekai,\n\n\n\n\nWe want to prepare godot-vrm for asset library publishing, but the format for publishing is incompatible with development.\n\n\n\nWe convert godot-vrm into a format suitable for development and then write a converter to a format ready for the asset library.\n\n\n\nHow to migrate to Godot-VRM to submodule format?\nThe thing Lyuma got blocked on is that VRM contains two addons: VRM and Godot-MToon-Shader\nRevive the Godot-MToon-Shader repository which Lyuma previously archived.\nBut Lyuma will change it so it’s only the submodule (contents of the addons folder) and then Lyuma will make the Godot VRM addon (submodule) a branch in the godot-vrm repository\nThen we’ll make a script to sync the changes to/from the godot-vrm example project which we submit to asset lib\nWriting this up for Fire, since we talked about the issue with addons/vrm being duplicated in multiple projects since Godot Asset Library doesn’t allow submodules / raw addons folders.\nDid some unarchiving and renames so that https://github.com/V-Sekai/Godot-MToon-Shader gets the top google slot\n\nMake sure the godot-vrm code is synced up with other repositories where it was duplicated.\nMake a mtoon addon repository with a copy of the Godot-MToon-Shader code.\nMake a branch in godot-vrm with ONLY the 4.0 vrm addon, usable as a submodule.\nChange v-sekai-game and other similar projects to use Godot-MToon-Shader and vrm as a submodules\nWrite a script to sync up repository contents from one to the other.\n\n\n\nIs there a functional difference between if not stringvar.is_empty(): vs if stringvar != \"\": x != “” is a bit shorter and easier to type, but I noticed some recommendation to use is_empty().\n\n\n\n\nWe don’t have duplicate godot-vrm copies and the copies stay in sync.\n\n\n\nAsset library copy is different than development.\n\n\n\n\nOption: The status quo. \nRejection Reason: This solves nothing. We have duplicate development versions. \n\n\n\n\nThis is a repository layout and not code.\n\n\n\nWe own the godot-vrm and the mtoon repositories.\n\n\n\n\nV-Sekai\n\n\n\n\nMIT License\n\nCopyright (c) 2018-2022 SaracenOne\nCopyright (c) 2019-2022 K. S. Ernest (iFire) Lee (fire)\nCopyright (c) 2020-2022 Lyuma\nCopyright (c) 2020-2022 MMMaellon\nCopyright (c) 2022 V-Sekai Contributors\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
+    "text": "Chosen option: “MADR 2.1.2 with Log4brains patch”, because\n\nImplicit assumptions should be made explicit. Design documentation is important to enable people understanding the decisions later on. See also A rational design process: How and why to fake it.\nThe MADR format is lean and fits our development style.\nThe MADR structure is comprehensible and facilitates usage & maintenance.\nThe MADR project is vivid.\nVersion 2.1.2 is the latest one available when starting to document ADRs.\nThe Log4brains patch adds more features, like tags.\n\nThe “Log4brains patch” performs the following modifications to the original template:\n\nChange the ADR filenames format (NNN-adr-name becomes YYYYMMDD-adr-name), to avoid conflicts during Git merges.\nAdd a draft status, to enable collaborative writing.\nAdd a Tags field."
   },
   {
-    "objectID": "decisions/20221206-export-godot-vrm-to-the-asset-library.html#context-and-problem-statement",
-    "href": "decisions/20221206-export-godot-vrm-to-the-asset-library.html#context-and-problem-statement",
-    "title": "Proposed: Prepare godot-vrm for asset library publishing",
+    "objectID": "decisions/20210212-use-markdown-architectural-decision-records.html#references",
+    "href": "decisions/20210212-use-markdown-architectural-decision-records.html#references",
+    "title": "Accepted: Use Markdown Architectural Decision Records",
     "section": "",
-    "text": "We want to prepare godot-vrm for asset library publishing, but the format for publishing is incompatible with development."
+    "text": "Relates to Use Log4brains to manage the ADRs"
   },
   {
-    "objectID": "decisions/20221206-export-godot-vrm-to-the-asset-library.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20221206-export-godot-vrm-to-the-asset-library.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: Prepare godot-vrm for asset library publishing",
+    "objectID": "decisions/20210212-use-markdown-architectural-decision-records.html#derivative-license",
+    "href": "decisions/20210212-use-markdown-architectural-decision-records.html#derivative-license",
+    "title": "Accepted: Use Markdown Architectural Decision Records",
     "section": "",
-    "text": "We convert godot-vrm into a format suitable for development and then write a converter to a format ready for the asset library."
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20221206-export-godot-vrm-to-the-asset-library.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20221206-export-godot-vrm-to-the-asset-library.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Prepare godot-vrm for asset library publishing",
+    "objectID": "decisions/20230527-server-performance-test.html",
+    "href": "decisions/20230527-server-performance-test.html",
+    "title": "Proposed: Generating Random Text Data for testing V-Sekai systems",
     "section": "",
-    "text": "How to migrate to Godot-VRM to submodule format?\nThe thing Lyuma got blocked on is that VRM contains two addons: VRM and Godot-MToon-Shader\nRevive the Godot-MToon-Shader repository which Lyuma previously archived.\nBut Lyuma will change it so it’s only the submodule (contents of the addons folder) and then Lyuma will make the Godot VRM addon (submodule) a branch in the godot-vrm repository\nThen we’ll make a script to sync the changes to/from the godot-vrm example project which we submit to asset lib\nWriting this up for Fire, since we talked about the issue with addons/vrm being duplicated in multiple projects since Godot Asset Library doesn’t allow submodules / raw addons folders.\nDid some unarchiving and renames so that https://github.com/V-Sekai/Godot-MToon-Shader gets the top google slot\n\nMake sure the godot-vrm code is synced up with other repositories where it was duplicated.\nMake a mtoon addon repository with a copy of the Godot-MToon-Shader code.\nMake a branch in godot-vrm with ONLY the 4.0 vrm addon, usable as a submodule.\nChange v-sekai-game and other similar projects to use Godot-MToon-Shader and vrm as a submodules\nWrite a script to sync up repository contents from one to the other.\n\n\n\nIs there a functional difference between if not stringvar.is_empty(): vs if stringvar != \"\": x != “” is a bit shorter and easier to type, but I noticed some recommendation to use is_empty()."
+    "text": "Status: proposed\nDeciders: V-Sekai, Bioblaze Payne, fire\nTags: V-Sekai, GPT-4\n\n\n\n\nV-Sekai is a project that aims to provide an immersive virtual world experience for users. As the project grows in complexity, it becomes increasingly important to ensure that the system is thoroughly tested and can handle various scenarios. One of the challenges faced by the V-Sekai team is the lack of diverse and realistic data for testing purposes. This limitation hinders the ability to identify potential issues and optimize the system’s performance.\n\n\n\nTo address the limitations in testing the V-Sekai system due to the lack of diverse and realistic data, this proposal suggests generating random text data for testing purposes.\n\n\nWe will use a tool like Chance.js library to generate random text data for testing purposes and use the database.\n\n\nFor generating random sentences, we will use something like the following method:\nchance.sentence();\nReference: Chance.js Sentence\n\n\n\nFor generating random user names, we will use something like the following method:\nchance.name();\nReference: Chance.js Name\n\n\n\nWe will perform the following SQL operations on the user and chat tables:\n\nSELECT All Data in Table\nSELECT LIKE Data based on %NA%\nSELECT Specific Row Data\nINSERT\nUPDATE\nDELETE\n\n\n\nTable user\nid | username | password | updated_on | created_on |\nTable chat\nid | user_id | name | text | updated_on | deleted_on | created_on |\n\n\n\n\nWe will create a SQL function to check if the username/password match and return ‘OK’. We will also check if the query returned is ‘OK’ and add false information randomly in the nodes to signify a user doing invalid calls for production testing.\nThe implementation will generate 90 days of data, generating 100,000 text data entries for testing purposes.\n\n\n\n\n\n\nImproved testing capabilities with diverse and realistic data\nEnhanced system reliability due to thorough testing\nIdentification of potential issues before they impact users\n\n\n\n\n\nAdditional development time required to implement the solution\nPotential increase in storage requirements for generated data\n\n\n\n\n\nUsing static test data: This option was considered for simplicity, but it would not provide the diverse and realistic data needed for thorough testing.\nManual data generation: This option involved manually creating test data, but it was deemed time-consuming and inefficient compared to using a library like Chance.js.\nThird-party data generation services: While there are external services that can generate random text data, using them would introduce dependencies and potential costs. Implementing our a solution similar to Chance.js allows for better control over the process.\nCrowdsourcing test data: This option involved gathering test data from users or volunteers. However, it raised concerns about data privacy, consistency, and quality.\n\n\n\n\nNo, this enhancement is essential for thorough testing and cannot be easily worked around with a few lines of script.\n\n\n\nYes, addressing the V-Sekai limitation is crucial for ensuring the system’s reliability and performance. Implementing this solution internally allows for better control over the testing process and data generation.\n\n\n\n\nV-Sekai"
   },
   {
-    "objectID": "decisions/20221206-export-godot-vrm-to-the-asset-library.html#positive-consequences",
-    "href": "decisions/20221206-export-godot-vrm-to-the-asset-library.html#positive-consequences",
-    "title": "Proposed: Prepare godot-vrm for asset library publishing",
+    "objectID": "decisions/20230527-server-performance-test.html#metadata",
+    "href": "decisions/20230527-server-performance-test.html#metadata",
+    "title": "Proposed: Generating Random Text Data for testing V-Sekai systems",
     "section": "",
-    "text": "We don’t have duplicate godot-vrm copies and the copies stay in sync."
+    "text": "Status: proposed\nDeciders: V-Sekai, Bioblaze Payne, fire\nTags: V-Sekai, GPT-4"
   },
   {
-    "objectID": "decisions/20221206-export-godot-vrm-to-the-asset-library.html#negative-consequences",
-    "href": "decisions/20221206-export-godot-vrm-to-the-asset-library.html#negative-consequences",
-    "title": "Proposed: Prepare godot-vrm for asset library publishing",
+    "objectID": "decisions/20230527-server-performance-test.html#context-and-problem-statement",
+    "href": "decisions/20230527-server-performance-test.html#context-and-problem-statement",
+    "title": "Proposed: Generating Random Text Data for testing V-Sekai systems",
     "section": "",
-    "text": "Asset library copy is different than development."
+    "text": "V-Sekai is a project that aims to provide an immersive virtual world experience for users. As the project grows in complexity, it becomes increasingly important to ensure that the system is thoroughly tested and can handle various scenarios. One of the challenges faced by the V-Sekai team is the lack of diverse and realistic data for testing purposes. This limitation hinders the ability to identify potential issues and optimize the system’s performance."
   },
   {
-    "objectID": "decisions/20221206-export-godot-vrm-to-the-asset-library.html#option-graveyard",
-    "href": "decisions/20221206-export-godot-vrm-to-the-asset-library.html#option-graveyard",
-    "title": "Proposed: Prepare godot-vrm for asset library publishing",
+    "objectID": "decisions/20230527-server-performance-test.html#proposed-solution",
+    "href": "decisions/20230527-server-performance-test.html#proposed-solution",
+    "title": "Proposed: Generating Random Text Data for testing V-Sekai systems",
     "section": "",
-    "text": "Option: The status quo. \nRejection Reason: This solves nothing. We have duplicate development versions."
+    "text": "To address the limitations in testing the V-Sekai system due to the lack of diverse and realistic data, this proposal suggests generating random text data for testing purposes.\n\n\nWe will use a tool like Chance.js library to generate random text data for testing purposes and use the database.\n\n\nFor generating random sentences, we will use something like the following method:\nchance.sentence();\nReference: Chance.js Sentence\n\n\n\nFor generating random user names, we will use something like the following method:\nchance.name();\nReference: Chance.js Name\n\n\n\nWe will perform the following SQL operations on the user and chat tables:\n\nSELECT All Data in Table\nSELECT LIKE Data based on %NA%\nSELECT Specific Row Data\nINSERT\nUPDATE\nDELETE\n\n\n\nTable user\nid | username | password | updated_on | created_on |\nTable chat\nid | user_id | name | text | updated_on | deleted_on | created_on |\n\n\n\n\nWe will create a SQL function to check if the username/password match and return ‘OK’. We will also check if the query returned is ‘OK’ and add false information randomly in the nodes to signify a user doing invalid calls for production testing.\nThe implementation will generate 90 days of data, generating 100,000 text data entries for testing purposes."
   },
   {
-    "objectID": "decisions/20221206-export-godot-vrm-to-the-asset-library.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20221206-export-godot-vrm-to-the-asset-library.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Prepare godot-vrm for asset library publishing",
+    "objectID": "decisions/20230527-server-performance-test.html#positive-consequences",
+    "href": "decisions/20230527-server-performance-test.html#positive-consequences",
+    "title": "Proposed: Generating Random Text Data for testing V-Sekai systems",
     "section": "",
-    "text": "This is a repository layout and not code."
+    "text": "Improved testing capabilities with diverse and realistic data\nEnhanced system reliability due to thorough testing\nIdentification of potential issues before they impact users"
   },
   {
-    "objectID": "decisions/20221206-export-godot-vrm-to-the-asset-library.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20221206-export-godot-vrm-to-the-asset-library.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Prepare godot-vrm for asset library publishing",
+    "objectID": "decisions/20230527-server-performance-test.html#negative-consequences",
+    "href": "decisions/20230527-server-performance-test.html#negative-consequences",
+    "title": "Proposed: Generating Random Text Data for testing V-Sekai systems",
     "section": "",
-    "text": "We own the godot-vrm and the mtoon repositories."
+    "text": "Additional development time required to implement the solution\nPotential increase in storage requirements for generated data"
   },
   {
-    "objectID": "decisions/20221206-export-godot-vrm-to-the-asset-library.html#references",
-    "href": "decisions/20221206-export-godot-vrm-to-the-asset-library.html#references",
-    "title": "Proposed: Prepare godot-vrm for asset library publishing",
+    "objectID": "decisions/20230527-server-performance-test.html#option-graveyard",
+    "href": "decisions/20230527-server-performance-test.html#option-graveyard",
+    "title": "Proposed: Generating Random Text Data for testing V-Sekai systems",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Using static test data: This option was considered for simplicity, but it would not provide the diverse and realistic data needed for thorough testing.\nManual data generation: This option involved manually creating test data, but it was deemed time-consuming and inefficient compared to using a library like Chance.js.\nThird-party data generation services: While there are external services that can generate random text data, using them would introduce dependencies and potential costs. Implementing our a solution similar to Chance.js allows for better control over the process.\nCrowdsourcing test data: This option involved gathering test data from users or volunteers. However, it raised concerns about data privacy, consistency, and quality."
   },
   {
-    "objectID": "decisions/20221206-export-godot-vrm-to-the-asset-library.html#license-of-the-contribution",
-    "href": "decisions/20221206-export-godot-vrm-to-the-asset-library.html#license-of-the-contribution",
-    "title": "Proposed: Prepare godot-vrm for asset library publishing",
+    "objectID": "decisions/20230527-server-performance-test.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230527-server-performance-test.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Generating Random Text Data for testing V-Sekai systems",
     "section": "",
-    "text": "MIT License\n\nCopyright (c) 2018-2022 SaracenOne\nCopyright (c) 2019-2022 K. S. Ernest (iFire) Lee (fire)\nCopyright (c) 2020-2022 Lyuma\nCopyright (c) 2020-2022 MMMaellon\nCopyright (c) 2022 V-Sekai Contributors\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
+    "text": "No, this enhancement is essential for thorough testing and cannot be easily worked around with a few lines of script."
   },
   {
-    "objectID": "decisions/20230912-target-most-popular-resolution.html",
-    "href": "decisions/20230912-target-most-popular-resolution.html",
-    "title": "Proposed: Address Screen Resolution Compatibility Issues",
+    "objectID": "decisions/20230527-server-performance-test.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230527-server-performance-test.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Generating Random Text Data for testing V-Sekai systems",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nSeveral users, including Lyuma, have reported that their monitors are not compatible with the V-Sekai menu system. This issue is causing a significant hindrance in the user experience.\n\n\n\n\nUser satisfaction\nCompatibility with various screen resolutions\n\n\n\n\n\nLeave as is\nSet V-Sekai’s screen resolution to fit the default resolution of the Valve hardware survey’s most popular resolution.\n\n\n\n\nChosen option: “Set V-Sekai’s screen resolution to fit the default resolution of the Valve hardware survey’s most popular resolution.”, because it will increase compatibility and improve user experience.\n\n\n\n\n\n\nGood, because it increases compatibility with the majority of users’ monitors.\nBad, because it may not cover all possible monitor resolutions, leaving some users still facing issues.\n\n\n\n\n\nGood, because it requires no additional work or changes.\nBad, because it does not solve the problem and leaves users frustrated.\n\n\n\n\n\n\nV-Sekai\nThis article is assisted by AI."
+    "text": "Yes, addressing the V-Sekai limitation is crucial for ensuring the system’s reliability and performance. Implementing this solution internally allows for better control over the testing process and data generation."
   },
   {
-    "objectID": "decisions/20230912-target-most-popular-resolution.html#metadata",
-    "href": "decisions/20230912-target-most-popular-resolution.html#metadata",
-    "title": "Proposed: Address Screen Resolution Compatibility Issues",
+    "objectID": "decisions/20230527-server-performance-test.html#references",
+    "href": "decisions/20230527-server-performance-test.html#references",
+    "title": "Proposed: Generating Random Text Data for testing V-Sekai systems",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai"
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20230912-target-most-popular-resolution.html#context-and-problem-statement",
-    "href": "decisions/20230912-target-most-popular-resolution.html#context-and-problem-statement",
-    "title": "Proposed: Address Screen Resolution Compatibility Issues",
+    "objectID": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html",
+    "href": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html",
+    "title": "Accepted: Stabilize Godot Engine updates by delaying to 2 week cycles",
     "section": "",
-    "text": "Several users, including Lyuma, have reported that their monitors are not compatible with the V-Sekai menu system. This issue is causing a significant hindrance in the user experience."
+    "text": "Status: accepted \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nStabilize Godot Engine updates because the update broke Groups broke once.\n\n\n\nWe use multiple ways to harden Godot Engine.\n\n\n\n\nDelay to around 2 week cycles\nMove V-Sekai godot to use a branch that is not tracked with Godot Engine master.\n\n\n\n\n\nMore stability\n\n\n\n\n\nLosing the pulse of Godot Engine development.\n\n\n\n\n\nOption: \nRejection Reason: \n\n\n\n\nNot a few lines of script in core.\n\n\n\nWe maintain the engine.\n\n\n\n\nhttps://godotengine.org\n\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230912-target-most-popular-resolution.html#decision-drivers",
-    "href": "decisions/20230912-target-most-popular-resolution.html#decision-drivers",
-    "title": "Proposed: Address Screen Resolution Compatibility Issues",
+    "objectID": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html#context-and-problem-statement",
+    "href": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html#context-and-problem-statement",
+    "title": "Accepted: Stabilize Godot Engine updates by delaying to 2 week cycles",
     "section": "",
-    "text": "User satisfaction\nCompatibility with various screen resolutions"
+    "text": "Stabilize Godot Engine updates because the update broke Groups broke once."
   },
   {
-    "objectID": "decisions/20230912-target-most-popular-resolution.html#considered-options",
-    "href": "decisions/20230912-target-most-popular-resolution.html#considered-options",
-    "title": "Proposed: Address Screen Resolution Compatibility Issues",
+    "objectID": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Accepted: Stabilize Godot Engine updates by delaying to 2 week cycles",
     "section": "",
-    "text": "Leave as is\nSet V-Sekai’s screen resolution to fit the default resolution of the Valve hardware survey’s most popular resolution."
+    "text": "We use multiple ways to harden Godot Engine."
   },
   {
-    "objectID": "decisions/20230912-target-most-popular-resolution.html#decision-outcome",
-    "href": "decisions/20230912-target-most-popular-resolution.html#decision-outcome",
-    "title": "Proposed: Address Screen Resolution Compatibility Issues",
+    "objectID": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Accepted: Stabilize Godot Engine updates by delaying to 2 week cycles",
     "section": "",
-    "text": "Chosen option: “Set V-Sekai’s screen resolution to fit the default resolution of the Valve hardware survey’s most popular resolution.”, because it will increase compatibility and improve user experience."
+    "text": "Delay to around 2 week cycles\nMove V-Sekai godot to use a branch that is not tracked with Godot Engine master."
   },
   {
-    "objectID": "decisions/20230912-target-most-popular-resolution.html#pros-and-cons-of-the-options",
-    "href": "decisions/20230912-target-most-popular-resolution.html#pros-and-cons-of-the-options",
-    "title": "Proposed: Address Screen Resolution Compatibility Issues",
+    "objectID": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html#positive-consequences",
+    "href": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html#positive-consequences",
+    "title": "Accepted: Stabilize Godot Engine updates by delaying to 2 week cycles",
     "section": "",
-    "text": "Good, because it increases compatibility with the majority of users’ monitors.\nBad, because it may not cover all possible monitor resolutions, leaving some users still facing issues.\n\n\n\n\n\nGood, because it requires no additional work or changes.\nBad, because it does not solve the problem and leaves users frustrated."
+    "text": "More stability"
   },
   {
-    "objectID": "decisions/20230912-target-most-popular-resolution.html#links",
-    "href": "decisions/20230912-target-most-popular-resolution.html#links",
-    "title": "Proposed: Address Screen Resolution Compatibility Issues",
+    "objectID": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html#negative-consequences",
+    "href": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html#negative-consequences",
+    "title": "Accepted: Stabilize Godot Engine updates by delaying to 2 week cycles",
     "section": "",
-    "text": "V-Sekai\nThis article is assisted by AI."
+    "text": "Losing the pulse of Godot Engine development."
   },
   {
-    "objectID": "decisions/20240622-process-for-testing-vsekai.html",
-    "href": "decisions/20240622-process-for-testing-vsekai.html",
-    "title": "Proposed: Create a process for testing V-Sekai.",
+    "objectID": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html#option-graveyard",
+    "href": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html#option-graveyard",
+    "title": "Accepted: Stabilize Godot Engine updates by delaying to 2 week cycles",
     "section": "",
-    "text": "We’re making V-Sekai, an immersive VR game that brings social VR/VRSNS/metaverse components to the Godot Engine.\n\n\n\nSometimes our flow doesn’t work and we can’t play the game because we broke the script.\nWe want to introduce automated testing to make it easier to debug.\n\n\n\nWe propose to use a test-driven development (TDD) approach.\n\n\n\n\nReduced time spent on debugging.\nIncreased confidence in the stability of the game.\nFaster development cycle as bugs are caught early.\n\n\n\n\n\nInitial setup of automated testing can be time-consuming.\nTests need to be maintained and updated as the game evolves.\n\n\n\n\nWe could continue without automated testing, but this could lead to more time spent on debugging and less time on developing new features.\n\n\n\nIn cases where new features are added infrequently, the overhead of maintaining tests might outweigh the benefits.\n\n\n\nThe testing framework would be part of the core game engine and maintained by us, the V-Sekai development team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\nAutomated Testing\nGame Development\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "Option: \nRejection Reason:"
   },
   {
-    "objectID": "decisions/20240622-process-for-testing-vsekai.html#the-context",
-    "href": "decisions/20240622-process-for-testing-vsekai.html#the-context",
-    "title": "Proposed: Create a process for testing V-Sekai.",
+    "objectID": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Accepted: Stabilize Godot Engine updates by delaying to 2 week cycles",
     "section": "",
-    "text": "We’re making V-Sekai, an immersive VR game that brings social VR/VRSNS/metaverse components to the Godot Engine."
+    "text": "Not a few lines of script in core."
   },
   {
-    "objectID": "decisions/20240622-process-for-testing-vsekai.html#the-problem-statement",
-    "href": "decisions/20240622-process-for-testing-vsekai.html#the-problem-statement",
-    "title": "Proposed: Create a process for testing V-Sekai.",
+    "objectID": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Accepted: Stabilize Godot Engine updates by delaying to 2 week cycles",
     "section": "",
-    "text": "Sometimes our flow doesn’t work and we can’t play the game because we broke the script.\nWe want to introduce automated testing to make it easier to debug."
+    "text": "We maintain the engine."
   },
   {
-    "objectID": "decisions/20240622-process-for-testing-vsekai.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240622-process-for-testing-vsekai.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Create a process for testing V-Sekai.",
+    "objectID": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html#references",
+    "href": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html#references",
+    "title": "Accepted: Stabilize Godot Engine updates by delaying to 2 week cycles",
     "section": "",
-    "text": "We propose to use a test-driven development (TDD) approach."
+    "text": "https://godotengine.org"
   },
   {
-    "objectID": "decisions/20240622-process-for-testing-vsekai.html#the-benefits",
-    "href": "decisions/20240622-process-for-testing-vsekai.html#the-benefits",
-    "title": "Proposed: Create a process for testing V-Sekai.",
+    "objectID": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html#derivative-license",
+    "href": "decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html#derivative-license",
+    "title": "Accepted: Stabilize Godot Engine updates by delaying to 2 week cycles",
     "section": "",
-    "text": "Reduced time spent on debugging.\nIncreased confidence in the stability of the game.\nFaster development cycle as bugs are caught early."
+    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240622-process-for-testing-vsekai.html#the-downsides",
-    "href": "decisions/20240622-process-for-testing-vsekai.html#the-downsides",
-    "title": "Proposed: Create a process for testing V-Sekai.",
+    "objectID": "decisions/20211031-face-motion-tracking-requires-standard-shapes.html",
+    "href": "decisions/20211031-face-motion-tracking-requires-standard-shapes.html",
+    "title": "Proposed: Face motion tracking requires standard shapes",
     "section": "",
-    "text": "Initial setup of automated testing can be time-consuming.\nTests need to be maintained and updated as the game evolves."
+    "text": "Proposed: Face motion tracking requires standard shapes\n\nContext and Problem Statement\nMake VRM faces sync with Perfectsync, SRanipal or Mediapipe faces.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nPeople use many standard types of face definitions.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n???\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot trivial.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nIt is a dependency of doing VR avatars.\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240622-process-for-testing-vsekai.html#the-road-not-taken",
-    "href": "decisions/20240622-process-for-testing-vsekai.html#the-road-not-taken",
-    "title": "Proposed: Create a process for testing V-Sekai.",
+    "objectID": "decisions/20210811-game-workflow-membrane.html",
+    "href": "decisions/20210811-game-workflow-membrane.html",
+    "title": "Proposed: Membrane Framework to Process Game Workflows",
     "section": "",
-    "text": "We could continue without automated testing, but this could lead to more time spent on debugging and less time on developing new features."
+    "text": "Proposed: Membrane Framework to Process Game Workflows\n\nContext and Problem Statement\nUse a workflow tool to process game things.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nMembrane is a workflow tool and can be used to orchestrate Blender.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nModify Blender input\nStretch goal. Push from Blender Mixer to Godot Engine.\n\nAutomatic correct skeleton mesh skinning for VRMs.\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot a few lines of code because it orchestrates multiple tools.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nNeeded to be done by us.\n\n\nReferences\n\nhttps://www.membraneframework.org/\nhttps://github.com/Pyrlang/Pyrlang\nhttp://www.wings3d.com/\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240622-process-for-testing-vsekai.html#the-infrequent-use-case",
-    "href": "decisions/20240622-process-for-testing-vsekai.html#the-infrequent-use-case",
-    "title": "Proposed: Create a process for testing V-Sekai.",
+    "objectID": "decisions/20230701-vsekai-broken-down-goals.html",
+    "href": "decisions/20230701-vsekai-broken-down-goals.html",
+    "title": "Proposed: V-Sekai Feature Enhancement Proposal",
     "section": "",
-    "text": "In cases where new features are added infrequently, the overhead of maintaining tests might outweigh the benefits."
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, ai summarized\n\n\n\n\nWe are developing a virtual reality platform, V-Sekai. To ensure the platform meets user needs and expectations, we have identified several features that need to be implemented. These features have been categorized based on their priority and necessity for the initial release.\n\n\n\nThe features have been organized into three categories: Must-Have, Nice-to-Have, and Out of Scope Initially. The priority within each category reflects the relative importance of the features for an initial release.\n\n\n\n\n\n\n\n\n\n\nPriority\nFeature\nDependencies\n\n\n\n\n1\nEnvironment (scene loading, world hosting, instancing)\nNone\n\n\n2\nWeb requests to servers (HTTP/WebSocket API)\nEnvironment\n\n\n3\nPerson to person interaction (avatars, animation, synchronization)\nEnvironment\n\n\n4\nInteraction with the world (interactive elements, physics)\nEnvironment\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nPriority\nFeature\nDependencies\n\n\n\n\n5\nCollaboration features (doodling, modeling, content loading)\nEnvironment, Person to person interaction\n\n\n6\nStatic content creation in editor (import avatars, create worlds)\nEnvironment\n\n\n7\nShareable content (inventory)\nEnvironment, Static content creation in editor\n\n\n8\nLocal API for extending platform\nEnvironment, Web requests to servers\n\n\n9\nVideo playback\nEnvironment\n\n\n10\nSupport for proprietary video hosting\nVideo playback\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nPriority\nFeature\nDependencies\n\n\n\n\n11\nText chat\nEnvironment, Person to person interaction\n\n\n12\nScreen sharing (OBS)\nEnvironment, Person to person interaction\n\n\n13\nModeling and 3D Creation (Blender)\nEnvironment, Static content creation in editor\n\n\n\n\n\n\n\nThe implementation details will be determined once the proposal is accepted and the features are finalized.\n\n\n\n\nA well-structured and prioritized feature list will guide development efforts.\nClear categorization helps manage stakeholder expectations about what will be included in the initial release.\n\n\n\n\n\nSome features may require more time and resources than initially estimated.\nStakeholders may have different opinions on the priority of certain features.\n\n\n\n\nThis section will include any options considered but ultimately rejected during the decision-making process.\n\n\n\nThis question will be addressed during the implementation phase for each feature.\n\n\n\nAs these features form the core functionality of the V-Sekai platform, they should be developed by our team to ensure quality and consistency.\n\n\n\n\nV-Sekai"
   },
   {
-    "objectID": "decisions/20240622-process-for-testing-vsekai.html#in-core-and-done-by-us",
-    "href": "decisions/20240622-process-for-testing-vsekai.html#in-core-and-done-by-us",
-    "title": "Proposed: Create a process for testing V-Sekai.",
+    "objectID": "decisions/20230701-vsekai-broken-down-goals.html#metadata",
+    "href": "decisions/20230701-vsekai-broken-down-goals.html#metadata",
+    "title": "Proposed: V-Sekai Feature Enhancement Proposal",
     "section": "",
-    "text": "The testing framework would be part of the core game engine and maintained by us, the V-Sekai development team."
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, ai summarized"
   },
   {
-    "objectID": "decisions/20240622-process-for-testing-vsekai.html#status",
-    "href": "decisions/20240622-process-for-testing-vsekai.html#status",
-    "title": "Proposed: Create a process for testing V-Sekai.",
+    "objectID": "decisions/20230701-vsekai-broken-down-goals.html#context-and-problem-statement",
+    "href": "decisions/20230701-vsekai-broken-down-goals.html#context-and-problem-statement",
+    "title": "Proposed: V-Sekai Feature Enhancement Proposal",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "We are developing a virtual reality platform, V-Sekai. To ensure the platform meets user needs and expectations, we have identified several features that need to be implemented. These features have been categorized based on their priority and necessity for the initial release."
   },
   {
-    "objectID": "decisions/20240622-process-for-testing-vsekai.html#decision-makers",
-    "href": "decisions/20240622-process-for-testing-vsekai.html#decision-makers",
-    "title": "Proposed: Create a process for testing V-Sekai.",
+    "objectID": "decisions/20230701-vsekai-broken-down-goals.html#proposed-solution",
+    "href": "decisions/20230701-vsekai-broken-down-goals.html#proposed-solution",
+    "title": "Proposed: V-Sekai Feature Enhancement Proposal",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "The features have been organized into three categories: Must-Have, Nice-to-Have, and Out of Scope Initially. The priority within each category reflects the relative importance of the features for an initial release.\n\n\n\n\n\n\n\n\n\n\nPriority\nFeature\nDependencies\n\n\n\n\n1\nEnvironment (scene loading, world hosting, instancing)\nNone\n\n\n2\nWeb requests to servers (HTTP/WebSocket API)\nEnvironment\n\n\n3\nPerson to person interaction (avatars, animation, synchronization)\nEnvironment\n\n\n4\nInteraction with the world (interactive elements, physics)\nEnvironment\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nPriority\nFeature\nDependencies\n\n\n\n\n5\nCollaboration features (doodling, modeling, content loading)\nEnvironment, Person to person interaction\n\n\n6\nStatic content creation in editor (import avatars, create worlds)\nEnvironment\n\n\n7\nShareable content (inventory)\nEnvironment, Static content creation in editor\n\n\n8\nLocal API for extending platform\nEnvironment, Web requests to servers\n\n\n9\nVideo playback\nEnvironment\n\n\n10\nSupport for proprietary video hosting\nVideo playback\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nPriority\nFeature\nDependencies\n\n\n\n\n11\nText chat\nEnvironment, Person to person interaction\n\n\n12\nScreen sharing (OBS)\nEnvironment, Person to person interaction\n\n\n13\nModeling and 3D Creation (Blender)\nEnvironment, Static content creation in editor"
   },
   {
-    "objectID": "decisions/20240622-process-for-testing-vsekai.html#tags",
-    "href": "decisions/20240622-process-for-testing-vsekai.html#tags",
-    "title": "Proposed: Create a process for testing V-Sekai.",
+    "objectID": "decisions/20230701-vsekai-broken-down-goals.html#implementation",
+    "href": "decisions/20230701-vsekai-broken-down-goals.html#implementation",
+    "title": "Proposed: V-Sekai Feature Enhancement Proposal",
     "section": "",
-    "text": "V-Sekai\nAutomated Testing\nGame Development"
+    "text": "The implementation details will be determined once the proposal is accepted and the features are finalized."
   },
   {
-    "objectID": "decisions/20240622-process-for-testing-vsekai.html#further-reading",
-    "href": "decisions/20240622-process-for-testing-vsekai.html#further-reading",
-    "title": "Proposed: Create a process for testing V-Sekai.",
+    "objectID": "decisions/20230701-vsekai-broken-down-goals.html#positive-consequences",
+    "href": "decisions/20230701-vsekai-broken-down-goals.html#positive-consequences",
+    "title": "Proposed: V-Sekai Feature Enhancement Proposal",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "A well-structured and prioritized feature list will guide development efforts.\nClear categorization helps manage stakeholder expectations about what will be included in the initial release."
   },
   {
-    "objectID": "decisions/20221014-networking-overhaul-proposal.html",
-    "href": "decisions/20221014-networking-overhaul-proposal.html",
-    "title": "Draft: Networking Overhaul",
+    "objectID": "decisions/20230701-vsekai-broken-down-goals.html#negative-consequences",
+    "href": "decisions/20230701-vsekai-broken-down-goals.html#negative-consequences",
+    "title": "Proposed: V-Sekai Feature Enhancement Proposal",
     "section": "",
-    "text": "Status: draft\nDeciders: V-Sekai, Malek, Lyuma, SaracenOne, Fire,\nTags: Networking,\n\n\n\nWe seek to solve these issues:\n\n(A) Use godot 4.0’s networking tools.\n(B) Use a relay server that doesn’t run any game code, rather than a headless V-Sekai server.\n(C) Make the costs of hosting V-Sekai as small as possible.\n(D) Write the server in Rust, for the speed and safety guarantees.\n(E) Make networking highly scalable for a single server.\n(F) Allow a client to connect to multiple servers simultaneously without issues, for seamless travel and portals.\n(G) Synchronize state between clients\n\nNote: This proposal does not cover Permissions, and is based in part on the previous Entity Networking proposal.\n\n\n\nBy using the technologies described below, we will cover A-G.\n\n\n\n\n\nTo reduce complexity, latency, and processing power, we have created a simple Mastership/Ownership model.\nClients are defined as individuals connecting to a Server, they have their own v-sekai game instance running.\nThe Relay Server, as of now, does not contain information about the state of the world, the only information the Relay Server contains is on Mastership/Ownership rules.\nP1 connects to the Server.\n\nP2 connects to the Server.\n\nP3 connects to the Server.\n\nP1 spawns in a Ball.\n\nServer marks that P1 has both Mastership and Ownership of Ball.\n\nServer synchronizes with P1 and sends the state of the Ball to P2, its location, rotation, the very fact of its existence, and its owner, master, and rule.\n\nServer State\n\n\n\nObjects\nMaster\nOwner\nRule\n\n\n\n\nBall\nP1\nP1\nAsk\n\n\n\nWhat does this mean?\n\n\nSince P1 is the Owner of the Ball, this means that P1 is the only one who can change the state of the ball. When Server synchronizes, if P2 were to have the ball in a different location then P1, the Server would tell P2 that the Ball is in the location P1 has it, and would do the same for P3. It can be thought of as a mutex on the state of the Ball. Whoever holds the Mutex is the one who can modify the state therein. This also means that all calculations for game state are split up among all the players, every player only has to run code modifying what they own, which in large scale player events would otherwise increase exponentially with custom scripts for each player’s props or avatars.\n\n\n\nThis presents a problem however, how could P2 take the Ball from P1? The solution is Mastership. Whoever is the Master can change who is the Owner at any time. The Master also can change whatever the default Rule is, which is what the Server, and Client references when looking to change Ownership to itself (or someone else?).\n\nAsk: Take a round trip to the Master and back to the Server so the Master can decide based on external factors whether or not to allow ownership transfer or deny it. This could be used for example, if someone only wants a gun to be grabbable if they are a “shooter” and not if they are a “civilian”\nDeny: You cannot ask for ownership transfer, good for things like Avatar’s transform node, you don’t wanna be involuntarily moved around, or for the root of the world map.\nAllow: You can ask for ownership any time, and it is automatically granted.\n\n\n\n\n\nWe can change the rate of synchronization based on the closest clients owned model, and other things like that, there are a lot of areas for optimization when it comes to using this.\n\n\n\n\n\nLow Latency for Competitive/Real-Time interactions\nLow processing power on both the server and client side\nBroad enough to be easily modifiable for optimizations in the future without changing the model\n\n\n\n\n\nComplexity, we will have to code this all from scratch basically\nMulti-user interactions become impossible on a single object, at least to do simply, some smart coding could get around it but it isn’t easy to do.\nResolutions for the allow rule could lead to inconsistencies, such as two different people picking up a gun and firing it, and two resulting bullets being spawned from the same gun before it gets removed from one individual.\n\n\n\n\nAbsolutely, this is the foundation of basically everything content wise in V-sekai.\n\n\n\nhttps://github.com/V-Sekai/V-Sekai.github.io/blob/master/decisions/2020/20200729-entity-networking.md\nMalek’s forum post on networking in the Discord server.\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Some features may require more time and resources than initially estimated.\nStakeholders may have different opinions on the priority of certain features."
   },
   {
-    "objectID": "decisions/20221014-networking-overhaul-proposal.html#context-and-problem-statement",
-    "href": "decisions/20221014-networking-overhaul-proposal.html#context-and-problem-statement",
-    "title": "Draft: Networking Overhaul",
+    "objectID": "decisions/20230701-vsekai-broken-down-goals.html#option-graveyard",
+    "href": "decisions/20230701-vsekai-broken-down-goals.html#option-graveyard",
+    "title": "Proposed: V-Sekai Feature Enhancement Proposal",
     "section": "",
-    "text": "We seek to solve these issues:\n\n(A) Use godot 4.0’s networking tools.\n(B) Use a relay server that doesn’t run any game code, rather than a headless V-Sekai server.\n(C) Make the costs of hosting V-Sekai as small as possible.\n(D) Write the server in Rust, for the speed and safety guarantees.\n(E) Make networking highly scalable for a single server.\n(F) Allow a client to connect to multiple servers simultaneously without issues, for seamless travel and portals.\n(G) Synchronize state between clients\n\nNote: This proposal does not cover Permissions, and is based in part on the previous Entity Networking proposal."
+    "text": "This section will include any options considered but ultimately rejected during the decision-making process."
   },
   {
-    "objectID": "decisions/20221014-networking-overhaul-proposal.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20221014-networking-overhaul-proposal.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Draft: Networking Overhaul",
+    "objectID": "decisions/20230701-vsekai-broken-down-goals.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230701-vsekai-broken-down-goals.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: V-Sekai Feature Enhancement Proposal",
     "section": "",
-    "text": "By using the technologies described below, we will cover A-G."
+    "text": "This question will be addressed during the implementation phase for each feature."
   },
   {
-    "objectID": "decisions/20221014-networking-overhaul-proposal.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-andor-diagrams",
-    "href": "decisions/20221014-networking-overhaul-proposal.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-andor-diagrams",
-    "title": "Draft: Networking Overhaul",
+    "objectID": "decisions/20230701-vsekai-broken-down-goals.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230701-vsekai-broken-down-goals.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: V-Sekai Feature Enhancement Proposal",
     "section": "",
-    "text": "To reduce complexity, latency, and processing power, we have created a simple Mastership/Ownership model.\nClients are defined as individuals connecting to a Server, they have their own v-sekai game instance running.\nThe Relay Server, as of now, does not contain information about the state of the world, the only information the Relay Server contains is on Mastership/Ownership rules.\nP1 connects to the Server.\n\nP2 connects to the Server.\n\nP3 connects to the Server.\n\nP1 spawns in a Ball.\n\nServer marks that P1 has both Mastership and Ownership of Ball.\n\nServer synchronizes with P1 and sends the state of the Ball to P2, its location, rotation, the very fact of its existence, and its owner, master, and rule.\n\nServer State\n\n\n\nObjects\nMaster\nOwner\nRule\n\n\n\n\nBall\nP1\nP1\nAsk\n\n\n\nWhat does this mean?\n\n\nSince P1 is the Owner of the Ball, this means that P1 is the only one who can change the state of the ball. When Server synchronizes, if P2 were to have the ball in a different location then P1, the Server would tell P2 that the Ball is in the location P1 has it, and would do the same for P3. It can be thought of as a mutex on the state of the Ball. Whoever holds the Mutex is the one who can modify the state therein. This also means that all calculations for game state are split up among all the players, every player only has to run code modifying what they own, which in large scale player events would otherwise increase exponentially with custom scripts for each player’s props or avatars.\n\n\n\nThis presents a problem however, how could P2 take the Ball from P1? The solution is Mastership. Whoever is the Master can change who is the Owner at any time. The Master also can change whatever the default Rule is, which is what the Server, and Client references when looking to change Ownership to itself (or someone else?).\n\nAsk: Take a round trip to the Master and back to the Server so the Master can decide based on external factors whether or not to allow ownership transfer or deny it. This could be used for example, if someone only wants a gun to be grabbable if they are a “shooter” and not if they are a “civilian”\nDeny: You cannot ask for ownership transfer, good for things like Avatar’s transform node, you don’t wanna be involuntarily moved around, or for the root of the world map.\nAllow: You can ask for ownership any time, and it is automatically granted.\n\n\n\n\n\nWe can change the rate of synchronization based on the closest clients owned model, and other things like that, there are a lot of areas for optimization when it comes to using this."
+    "text": "As these features form the core functionality of the V-Sekai platform, they should be developed by our team to ensure quality and consistency."
   },
   {
-    "objectID": "decisions/20221014-networking-overhaul-proposal.html#positive-consequences-list",
-    "href": "decisions/20221014-networking-overhaul-proposal.html#positive-consequences-list",
-    "title": "Draft: Networking Overhaul",
+    "objectID": "decisions/20230701-vsekai-broken-down-goals.html#references",
+    "href": "decisions/20230701-vsekai-broken-down-goals.html#references",
+    "title": "Proposed: V-Sekai Feature Enhancement Proposal",
     "section": "",
-    "text": "Low Latency for Competitive/Real-Time interactions\nLow processing power on both the server and client side\nBroad enough to be easily modifiable for optimizations in the future without changing the model"
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20221014-networking-overhaul-proposal.html#negative-consequences-list",
-    "href": "decisions/20221014-networking-overhaul-proposal.html#negative-consequences-list",
-    "title": "Draft: Networking Overhaul",
+    "objectID": "decisions/20240715-vrchat-networking-mental-model.html",
+    "href": "decisions/20240715-vrchat-networking-mental-model.html",
+    "title": "Proposed: Create a Conceptual Model of VRChat Networking",
     "section": "",
-    "text": "Complexity, we will have to code this all from scratch basically\nMulti-user interactions become impossible on a single object, at least to do simply, some smart coding could get around it but it isn’t easy to do.\nResolutions for the allow rule could lead to inconsistencies, such as two different people picking up a gun and firing it, and two resulting bullets being spawned from the same gun before it gets removed from one individual."
+    "text": "In the realm of virtual reality, particularly within VRChat, understanding the networking model is crucial for developers. This proposal aims to create a comprehensive conceptual model of VRChat’s networking system.\n\n\n\nDevelopers often struggle with the intricacies of VRChat’s networking, leading to inefficient code and suboptimal user experiences. A clear and concise guide is needed to demystify the process.\n\n\n\n\n\nThere are two primary methods to send data in VRChat:\n\nUdonsynced Variables:\n\nMark variables as [UdonSynced].\nCall RequestSerialization() in the script to send a copy of the synced variables to all other clients.\nOnly the owner can call RequestSerialization(), so ensure you call Networking.SetOwner() first.\nAn event called OnDeserialization is triggered when a network packet is received.\n\nNetwork Events:\n\nUse SendCustomNetworkEvent() to send an event.\nSpecify a string that matches the name of a function taking no arguments; this function will run upon receiving the event.\nChoose to send the event either to the owner or all clients.\n\n\n// Example of Udonsynced variable\n[UdonBehaviourSyncMode(BehaviourSyncMode.Manual)]\npublic class SyncExample : UdonSharpBehaviour\n{\n    [UdonSynced] private int syncedVariable;\n\n    public void UpdateVariable(int newValue)\n    {\n        if (Networking.IsOwner(gameObject))\n        {\n            syncedVariable = newValue;\n            RequestSerialization();\n        }\n    }\n\n    public override void OnDeserialization()\n    {\n        // Handle deserialized data\n    }\n}\n\n// Example of Network Event\npublic class EventExample : UdonSharpBehaviour\n{\n    public void TriggerEvent()\n    {\n        SendCustomNetworkEvent(VRC.Udon.Common.Interfaces.NetworkEventTarget.All, \"HandleEvent\");\n    }\n\n    public void HandleEvent()\n    {\n        // Handle the event\n    }\n}\n\n\n\n\n\nImproved Readability: Clear guidelines enhance the readability of networking code.\nConsistency: Ensures uniformity in how networking tasks are handled across different projects.\nEfficiency: Streamlined processes make it easier for developers to implement networking features quickly.\n\n\n\n\n\nInitial Setup Time: Establishing and fine-tuning the mental model requires an initial investment of time and resources.\nLimited Flexibility: Strict adherence to the model may limit creative solutions to unique problems.\n\n\n\n\nAlternative approaches such as manual editing or using different networking models were considered but ultimately impossible as we don’t run VRChat.\n\n\n\nIn scenarios where highly specialized or technical networking solutions are required, additional human oversight may be necessary to ensure accuracy and appropriateness.\n\n\n\nWe need to understand how networking models work.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\nFire\nMMMaellon\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article.\n\n\nCentauri2442 recorded the byte count(s) of every synced variable type in udon\n\n\n\n\n\n\n\n\n\n\nSystem Type\nmaxByte\nminByte\nvariableType\nNotes\n\n\n\n\nSystem.Boolean\n2\n2\nBool\n\n\n\nSystem.Char\n2\n2\nChar\n\n\n\nSystem.Byte\n2\n2\nByte\n\n\n\nSystem.SByte\n2\n2\nSByte\n\n\n\nSystem.Int16\n4\n2\nShort\nSwaps every other\n\n\nSystem.UInt16\n4\n2\nUShort\nSwaps every other\n\n\nSystem.Int32\n8\n4\nInt\nSwaps every other\n\n\nSystem.UInt32\n8\n4\nUInt\nSwaps every other\n\n\nSystem.Int64\n12\n8\nLong\nSwaps every other\n\n\nSystem.UInt64\n12\n8\nULong\nSwaps every other\n\n\nSystem.Single\n8\n4\nFloat\nSwaps every other\n\n\nSystem.Double\n12\n8\nDouble\nSwaps every other\n\n\nUnityEngine.Vector2\n8\n8\nVector2\n\n\n\nUnityEngine.Vector3\n12\n12\nVector3\n\n\n\nUnityEngine.Vector4\n16\n16\nVector4\n\n\n\nUnityEngine.Quaternion\n16\n16\nQuaternion\n\n\n\nSystem.String\n84\n1\nString\nNull: No serialization | 84 + 1 byte per character, byte size allocated per for (84, 88, 92, etc)\n\n\nRVCUInt\n8\n8\nRVCUInt\n\n\n\nUnityEngine.Color\n8\n8\nColor\n\n\n\nUnityEngine.Color32\n8\n8\nColor32\n\n\n\nSystem.BooleanArray\n80\n80\nBooleanArray\n80 + array size in increments of 4 as buffer (80, 84, 88, etc) | Will increase every 4 values (5, 9, 13, etc)\n\n\nSystem.CharArray\n80\n80\nCharArray\n80 + array size in increments of 4 as buffer (80, 84, 88, etc) | Will increase every 4 values (5, 9, 13, etc)\n\n\nSystem.ByteArray\n80\n80\nByteArray\n80 + array size in increments of 4 as buffer (80, 84, 88, etc) | Will increase every 4 values (5, 9, 13, etc)\n\n\nSystem.SByteArray\n80\n80\nSByteArray\n80 + array size in increments of 4 as buffer (80, 84, 88, etc) | Will increase every 4 values (5, 9, 13, etc)\n\n\nSystem.Int16Array\n80\n80\nShortArray\n80 + array size in increments of 4 as buffer (80, 84, 88, etc) | Will increase every 2 values (3, 5, 7, etc)\n\n\nSystem.UInt16Array\n80\n80\nUShortArray\n80 + array size in increments of 4 as buffer (80, 84, 88, etc) | Will increase every 2 values (3, 5, 7, etc)\n\n\nSystem.Int32Array\n80\n80\nIntArray\n80 + array size * 4\n\n\nSystem.UInt32Array\n80\n80\nUIntArray\n80 + array size * 4\n\n\nSystem.Int64Array\n80\n80\nLongArray\n80 + array size * 8\n\n\nSystem.UInt64Array\n80\n80\nULongArray\n80 + array size * 8\n\n\nSystem.SingleArray\n80\n80\nFloatArray\n80 + array size * 4\n\n\nSystem.DoubleArray\n80\n80\nDoubleArray\n80 + array size * 8\n\n\nUnityEngine.Vector2Array\n80\n80\nVector2Array\n80 + array size * 8\n\n\nUnityEngine.Vector3Array\n80\n80\nVector3Array\n80 + array size * 12\n\n\nUnityEngine.Vector4Array\n80\n80\nVector4Array\n80 + array size * 16\n\n\nUnityEngine.QuaternionArray\n80\n80\nQuaternionArray\n80 + array size * 16\n\n\nSystem.StringArray\n80\n80\nStringArray\n84 + (2, 4, or 8 bytes per character). Size of 0: 84 bytes. Size greater than 0 but with any null values: 0 bytes. Size greater than 0 with all valid strings: 84 + (2, 4, or 8 bytes per character)\n\n\nRVCUStringArray\n80\n80\nRVCUStringArray\n84 + (2, 4, or 8 bytes per character). Size of 0: 84 bytes. Size greater than 0 but with any null values: 0 bytes. Size greater than 0 with all valid strings: 84 + (2, 4, or 8 bytes per character)\n\n\nUnityEngine.ColorArray\n80\n80\nColorArray\n80 + array size * 16\n\n\nUnityEngine.Color32Array\n80\n80\nColor32Array\n80 + array size * 4\n\n\n\n\n\n\nAnswer: In VRChat, which uses UdonSharp for scripting, there isn’t a hard limit on the number of UdonSharpBehaviour instances a world (or server instance) can have. However, practical limits are imposed by performance considerations. Each UdonSharpBehaviour consumes memory and processing power, so the total number you can effectively use will depend on the complexity of your scripts and the capabilities of the hardware running the world. It’s essential to optimize your scripts and manage resources efficiently to ensure smooth performance.\n\n\n\nAnswer: Yes, UdonSharpBehaviour instances can communicate with each other. Here are some ways they can interact:\n\nCustom Network Events: You can send custom network events (with zero parameters) to trigger actions in other UdonSharpBehaviour instances. The receiver won’t know who the sender is, and the action will be performed locally on the UdonSharpBehaviour’s current frame.\nSynced Variables: If you need to send data, it’s better to use synced variables rather than mixing them with network events. When these variables get updated, the OnDeserialization() method will be called. This is a function in UdonSharpBehaviour that you can override to handle any work needed with the updated variables.\n\n\n\n\nAnswer: You typically don’t mix network events with synced variables. If you need to send data, just use synced variables. When the variables get updated, OnDeserialization() will be called. That’s a function in UdonSharpBehaviour that you can override. Do all the work needed with the variables in OnDeserialization.\n\n\n\nAnswer: There’s an advanced feature called FieldChangeCallbacks that allows for code simplification. Basically, create a C# property with a getter and a setter and specify it as the field change callback. The setter will be called in addition to OnDeserialization when network updates come in. This helps combine the code for local and remote clients in the setter. This is an advanced code-writing optimization for making your code cleaner. No, it does not affect performance in terms of space and time. FieldChangeCallbacks reduces code repetition, thereby simplifying the codebase and making it more maintainable.\n\n\n\nAnswer: Assume we calculate the state of the world independently for each frame, without depending on previous frames. This means that while the exact values of the three variables are crucial for determining the current state, the order of changes within the same frame does not affect the final state interpretation at that frame."
   },
   {
-    "objectID": "decisions/20221014-networking-overhaul-proposal.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20221014-networking-overhaul-proposal.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Draft: Networking Overhaul",
+    "objectID": "decisions/20240715-vrchat-networking-mental-model.html#the-context",
+    "href": "decisions/20240715-vrchat-networking-mental-model.html#the-context",
+    "title": "Proposed: Create a Conceptual Model of VRChat Networking",
     "section": "",
-    "text": "Absolutely, this is the foundation of basically everything content wise in V-sekai."
+    "text": "In the realm of virtual reality, particularly within VRChat, understanding the networking model is crucial for developers. This proposal aims to create a comprehensive conceptual model of VRChat’s networking system."
   },
   {
-    "objectID": "decisions/20221014-networking-overhaul-proposal.html#references",
-    "href": "decisions/20221014-networking-overhaul-proposal.html#references",
-    "title": "Draft: Networking Overhaul",
+    "objectID": "decisions/20240715-vrchat-networking-mental-model.html#the-problem-statement",
+    "href": "decisions/20240715-vrchat-networking-mental-model.html#the-problem-statement",
+    "title": "Proposed: Create a Conceptual Model of VRChat Networking",
     "section": "",
-    "text": "https://github.com/V-Sekai/V-Sekai.github.io/blob/master/decisions/2020/20200729-entity-networking.md\nMalek’s forum post on networking in the Discord server."
+    "text": "Developers often struggle with the intricacies of VRChat’s networking, leading to inefficient code and suboptimal user experiences. A clear and concise guide is needed to demystify the process."
   },
   {
-    "objectID": "decisions/20221014-networking-overhaul-proposal.html#derivative-license",
-    "href": "decisions/20221014-networking-overhaul-proposal.html#derivative-license",
-    "title": "Draft: Networking Overhaul",
+    "objectID": "decisions/20240715-vrchat-networking-mental-model.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240715-vrchat-networking-mental-model.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Create a Conceptual Model of VRChat Networking",
     "section": "",
-    "text": "Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "There are two primary methods to send data in VRChat:\n\nUdonsynced Variables:\n\nMark variables as [UdonSynced].\nCall RequestSerialization() in the script to send a copy of the synced variables to all other clients.\nOnly the owner can call RequestSerialization(), so ensure you call Networking.SetOwner() first.\nAn event called OnDeserialization is triggered when a network packet is received.\n\nNetwork Events:\n\nUse SendCustomNetworkEvent() to send an event.\nSpecify a string that matches the name of a function taking no arguments; this function will run upon receiving the event.\nChoose to send the event either to the owner or all clients.\n\n\n// Example of Udonsynced variable\n[UdonBehaviourSyncMode(BehaviourSyncMode.Manual)]\npublic class SyncExample : UdonSharpBehaviour\n{\n    [UdonSynced] private int syncedVariable;\n\n    public void UpdateVariable(int newValue)\n    {\n        if (Networking.IsOwner(gameObject))\n        {\n            syncedVariable = newValue;\n            RequestSerialization();\n        }\n    }\n\n    public override void OnDeserialization()\n    {\n        // Handle deserialized data\n    }\n}\n\n// Example of Network Event\npublic class EventExample : UdonSharpBehaviour\n{\n    public void TriggerEvent()\n    {\n        SendCustomNetworkEvent(VRC.Udon.Common.Interfaces.NetworkEventTarget.All, \"HandleEvent\");\n    }\n\n    public void HandleEvent()\n    {\n        // Handle the event\n    }\n}"
   },
   {
-    "objectID": "decisions/20220605-gocd-pipeline-reset.html",
-    "href": "decisions/20220605-gocd-pipeline-reset.html",
-    "title": "Accepted: To avoid git submodule but recreate the gocd pipelines",
+    "objectID": "decisions/20240715-vrchat-networking-mental-model.html#the-benefits",
+    "href": "decisions/20240715-vrchat-networking-mental-model.html#the-benefits",
+    "title": "Proposed: Create a Conceptual Model of VRChat Networking",
     "section": "",
-    "text": "Accepted: To avoid git submodule but recreate the gocd pipelines\n\nDescribe the status of the issue.\n\nproposed\ndraft\nrejected\naccepted\ndeprecated\nsuperseded by\n\n\n\nList the deciders of the issue.\nV-Sekai,fire,\n\n\nDescribe the tags of the issue.\nV-Sekai,gocd,\n\n\nContext and Problem Statement\nGocd git submodule failed to load.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nReset the gocd pipeline by renaming the initial pipeline name.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\n\nclone https://github.com/V-Sekai/groups-gocd-pipelines\nModify https://github.com/V-Sekai/groups-gocd-pipelines/blob/master/src/godot_4_x.jsonnet\ngodot_template_groups_editor to have increment the revision number.\n./bin/generate\ncommit to git\n\n\n\nPositive Consequences\nAble to build again.\n\n\nNegative Consequences\nIncreases cache size.\n\n\nOption graveyard\nNo response\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nIt is a few lines of script.\n\n\nIs there a reason why this should be core and done by us?\nIt’s our release process.\n\n\nReferences\n\nV-Sekai\n\n\n\nLicense of the contribution\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Improved Readability: Clear guidelines enhance the readability of networking code.\nConsistency: Ensures uniformity in how networking tasks are handled across different projects.\nEfficiency: Streamlined processes make it easier for developers to implement networking features quickly."
   },
   {
-    "objectID": "decisions/20230310-don't-merge-incomplete-work.html",
-    "href": "decisions/20230310-don't-merge-incomplete-work.html",
-    "title": "Proposed: Don’t merge incomplete work.",
+    "objectID": "decisions/20240715-vrchat-networking-mental-model.html#the-downsides",
+    "href": "decisions/20240715-vrchat-networking-mental-model.html#the-downsides",
+    "title": "Proposed: Create a Conceptual Model of VRChat Networking",
     "section": "",
-    "text": "Proposed: Don’t merge incomplete work.\n\nV-Sekai version\nlatest on 2022-06-05\n\n\nSystem information\nWin 11, Vulkan, Nvidia 3000\n\n\nIssue description\nDon’t merge changes when the tests or the compile fails.\n\n\nSteps to reproduce\n\nPush a build\nIt fails\nBuild is broken\n\n\n\nMinimal reproduction project\nV-Sekai project."
+    "text": "Initial Setup Time: Establishing and fine-tuning the mental model requires an initial investment of time and resources.\nLimited Flexibility: Strict adherence to the model may limit creative solutions to unique problems."
   },
   {
-    "objectID": "decisions/20211005-bridge-music-to-xr.html",
-    "href": "decisions/20211005-bridge-music-to-xr.html",
-    "title": "Proposed: Music is important to human experience and should be bridged to XR",
+    "objectID": "decisions/20240715-vrchat-networking-mental-model.html#the-road-not-taken",
+    "href": "decisions/20240715-vrchat-networking-mental-model.html#the-road-not-taken",
+    "title": "Proposed: Create a Conceptual Model of VRChat Networking",
     "section": "",
-    "text": "Proposed: Music is important to human experience and should be bridged to XR\n\nContext and Problem Statement\nMusic is important to human experience\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nBridge membrane given a video file play to on a website.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nNo idea\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nRTSP -&gt; #website\n\n\nPositive Consequences\n\nCreate know how for video rooms\n\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nUseful to bridge into other things.\n\n\nReferences\n\nhttps://github.com/ROZ-MOFUMOFU-ME/TopazBot\nhttps://github.com/membraneframework/membrane_rtc_engine\nhttps://github.com/membraneframework/membrane_rtsp\nhttps://github.com/membraneframework/membrane_rtp_plugin\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Alternative approaches such as manual editing or using different networking models were considered but ultimately impossible as we don’t run VRChat."
   },
   {
-    "objectID": "decisions/20230419-package-godot-for-pkgin.html",
-    "href": "decisions/20230419-package-godot-for-pkgin.html",
-    "title": "Rejected: Package Godot for pkgin",
+    "objectID": "decisions/20240715-vrchat-networking-mental-model.html#the-infrequent-use-case",
+    "href": "decisions/20240715-vrchat-networking-mental-model.html#the-infrequent-use-case",
+    "title": "Proposed: Create a Conceptual Model of VRChat Networking",
     "section": "",
-    "text": "Rejected: Package Godot for pkgin\n\nMetadata\n\nStatus: rejected \nDeciders: V-Sekai,fire,\nTags: V-Sekai,chatgpt4,\n\n\n\nContext and Problem Statement\nAccording to Netflix, the BSD-type operating systems are competitive, and supporting pkgsrc is an excellent way to start.\n\npkgsrc is a framework for managing third-party software on UNIX-like systems containing over 26,000 packages. It is the default package manager of NetBSD and SmartOS and can be used to enable freely available software to be built quickly on a large number of other UNIX-like platforms.\n\n\nV-Sekai is developing a free, open-source virtual reality platform. We work to make it user-friendly and fulfill a need in the VR community.\n\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\n\nEffortless installation and updates: Packaging Godot Engine for pkgin makes it easier to install and update the software on macOS, Linux, and NetBSD, offering a smooth experience for users at all expertise levels.\nWider platform support: By embracing pkgsrc and packaging Godot Engine for pkgin, compatibility with an array of UNIX-like systems is ensured, broadening the user base and fostering adoption across different platforms.\nPromoting cooperation: V-Sekai’s support for pkgsrc and packaging of the Godot Engine for pkgin enables collaboration through the vast third-party software ecosystem available for UNIX-like systems, stimulating the exchange of ideas and resources.\nReinforcing open-source ideals: V-Sekai’s decision to package the Godot Engine for pkgin strengthens its commitment to open-source values like accessibility, transparency, and community-driven development, enhancing growth within the VR community.\n\n\n\nDescribe how your proposal will work with code, pseudo-code, mock-ups, or diagrams\ngraph LR\nA[Godot Engine Source Code] --&gt; B[Build and Package]\nB --&gt; C[Godot Engine pkgin Package]\nC --&gt; D{Platform Compatibility}\nD --&gt; E[macOS]\nD --&gt; F[Linux]\nD --&gt; G[NetBSD]\nC --&gt; H[Package Repository]\nI[User] --&gt; J[pkgin command]\nJ --&gt; H\nH --&gt; K[Install/Update Godot Engine]\nK --&gt; I\n\n\nPositive Consequences\n\nEasy installation and updates: Pkgin support simplifies installing and updating the Godot Engine on UNIX-like systems, such as macOS, Linux, and NetBSD, providing a hassle-free experience for users.\nWide platform support: Pkgin compatibility ensures that the Godot Engine works seamlessly with multiple UNIX-like systems, expanding the user base and promoting adoption across various platforms.\nEfficient dependency handling: Pkgin automatically manages dependencies, streamlining the installation process and minimizing conflicts or issues due to unmet requirements.\nUniform software environment: Pkgin helps maintain consistency in software versions and configurations, which is crucial for collaboration and reducing the need for troubleshooting.\nConnection to the pkgsrc ecosystem: Supporting pkgin allows users to tap into the extensive third-party software ecosystem for UNIX-like systems, fostering the exchange of ideas and resources within the open-source community.\nResource and time savings: By offering pkgin support, developers can concentrate on enhancing the Godot Engine and V-Sekai’s VR platform features rather than manually managing software installations and updates.\nEmphasizing open-source principles: By endorsing pkgin, both V-Sekai and the Godot Engine reaffirm their commitment to open-source values, such as accessibility, transparency, and community-driven development, fostering growth and collaboration within the VR community.\n\n\n\nNegative Consequences\nThere are some potential downsides to packaging the Godot Engine for pkgin, which include:\nAdditional maintenance work: Supporting pkgin may necessitate regular package updates to ensure compatibility with different systems and to keep up with new Godot Engine versions and features. This could require extra time and resources from the development team.\nIncomplete platform support: Pkgin is designed for UNIX-like systems, but it doesn’t directly cater to users on other platforms, such as Windows. Supporting alternative package managers for non-UNIX platforms may demand extra efforts.\nUser learning curve: Users unfamiliar with pkgin or pkgsrc might need to invest time in learning to use the package manager effectively, which could pose a barrier for some users, particularly those new to UNIX-like systems or with limited package management experience.\nPotential compatibility challenges: While pkgin aims to provide compatibility across various UNIX-like systems, certain configurations or system setups may still pose difficulties. Addressing these issues might require more development and troubleshooting efforts.\nUnnecessary overhead for small projects: For smaller projects or users with minimal requirements, the added features and capabilities provided by pkgin support might be excessive. In such cases, the effort needed to maintain and use a pkgin package could outweigh its benefits.\nDespite these potential downsides, offering pkgin support can bring significant advantages, such as streamlining installation and updates, ensuring compatibility with UNIX-like systems, and promoting collaboration within the open-source community.\n\n\nOption graveyard\nAlternative package managers: While other package managers like apt or yum might have been considered, they may need to provide different compatibility with BSD-type systems than pkgsrc. Pkgin, designed for pkgsrc, is the default package manager for systems like NetBSD and SmartOS, making it the ideal choice.\nManual installation: Requiring users to compile and install Godot Engine manually would complicate the process and be less user-friendly, particularly for novices. This approach could also result in software version inconsistencies and configuration issues, affecting user experience.\nCustom package manager: Developing a custom package manager specifically for V-Sekai’s platform is resource-intensive and duplicates existing package managers’ efforts, such as pkgin, which already offers compatibility with BSD-type systems.\nExclusively focusing on other platforms: By targeting only Linux, macOS, or Windows, V-Sekai would limit its potential user base and overlook the advantages of supporting UNIX-like systems like NetBSD and SmartOS. So instead, packaging Godot Engine for pkgin enables V-Sekai to reach a wider audience using BSD-type operating systems.\n\n\nIf this enhancement will be used infrequently, can it be worked around with a few lines of script?\nUsing a script for Godot Engine may have drawbacks, such as being less user-friendly, requiring more maintenance, having limited compatibility with BSD-type systems, and potentially impacting integration with the pkgsrc ecosystem.\n\n\nIs there a reason why this should be core and done by us?\nPackaging the Godot Engine for pkgin as a core task our team handles ensures quality control, streamlined support, customization, alignment with your platform’s vision, and trust-building with users. These factors contribute to the overall success and adoption of your open-source virtual reality platform.\n\n\nReferences\n\nV-Sekai\nhttps://pkgsrc.joyent.com/"
+    "text": "In scenarios where highly specialized or technical networking solutions are required, additional human oversight may be necessary to ensure accuracy and appropriateness."
   },
   {
-    "objectID": "decisions/20230812-gocd-agent-setup.html",
-    "href": "decisions/20230812-gocd-agent-setup.html",
-    "title": "Proposed: Configuring GoCD Agents in V-Sekai",
+    "objectID": "decisions/20240715-vrchat-networking-mental-model.html#in-core-and-done-by-us",
+    "href": "decisions/20240715-vrchat-networking-mental-model.html#in-core-and-done-by-us",
+    "title": "Proposed: Create a Conceptual Model of VRChat Networking",
     "section": "",
-    "text": "Status: proposed \nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nV-Sekai is a platform that requires regular configuration of GoCD agents. This process can be time-consuming and prone to errors if not done correctly.\n\n\n\nThe challenge is to configure the GoCD agents after a restart of the host machine. This involves accessing the GoCD server, navigating to the Agents page, enabling new agents, configuring agent resources, assigning environments, and saving changes.\n\n\n\nThe strategy is to follow a step-by-step guide to ensure that all the necessary configurations are made correctly. This includes:\n\nAccessing the GoCD Server\nNavigating to the Agents Page\nEnabling New Agents\nConfiguring Agent Resources\nAssigning Environments\nSaving Changes\n\n\n\n\nBy following this guide, users can ensure that their GoCD agents are configured correctly and ready to run jobs. This can save time and reduce the risk of errors.\n\n\n\nThe downside is that this process needs to be repeated every time the host machine is restarted. However, this is a necessary step to ensure that the GoCD agents function correctly.\n\n\n\nAn alternative approach could be to automate this process using scripts or other automation tools. However, this would require additional technical expertise and may not be feasible for all users.\n\n\n\nIn some cases, users may need to configure additional settings or use different resources and environments. These cases will require additional steps and may not be covered by this guide.\n\n\n\nYes, this guide was created by us and is part of our core documentation.\n\n\n\n\nV-Sekai\nThis article is assisted by AI.\n\n\n\n\n\n\n\n\n\n\n\n\nAgent Type\nResources\nEnvironments\n\n\n\n\ngocd-agent-59dbf9989-vp4d66\nlinux, mingw5\ndevelopment, itch-fire\n\n\ngocd-agent-dind-96575468d4-s29l2\ndind\ndevelopment, itch-fire\n\n\ngocd-agent-59dbf9989-cczqj\nlinux, mingw5\ndevelopment, itch-fire\n\n\ngocd-agent-59dbf9989-p6vs5\nlinux, mingw5\ndevelopment, itch-fire\n\n\ngocd-agent-59dbf9989-t4ckd\nlinux, mingw5\ndevelopment, itch-fire\n\n\ngocd-agent-dind-96575468d4-b6gq9\ndind\ndevelopment, itch-fire\n\n\n\nPlease note that the actual resources and environments will vary based on your specific setup."
+    "text": "We need to understand how networking models work."
   },
   {
-    "objectID": "decisions/20230812-gocd-agent-setup.html#metadata",
-    "href": "decisions/20230812-gocd-agent-setup.html#metadata",
-    "title": "Proposed: Configuring GoCD Agents in V-Sekai",
+    "objectID": "decisions/20240715-vrchat-networking-mental-model.html#status",
+    "href": "decisions/20240715-vrchat-networking-mental-model.html#status",
+    "title": "Proposed: Create a Conceptual Model of VRChat Networking",
     "section": "",
-    "text": "Status: proposed \nDeciders: V-Sekai\nTags: V-Sekai"
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20230812-gocd-agent-setup.html#the-backdrop",
-    "href": "decisions/20230812-gocd-agent-setup.html#the-backdrop",
-    "title": "Proposed: Configuring GoCD Agents in V-Sekai",
+    "objectID": "decisions/20240715-vrchat-networking-mental-model.html#decision-makers",
+    "href": "decisions/20240715-vrchat-networking-mental-model.html#decision-makers",
+    "title": "Proposed: Create a Conceptual Model of VRChat Networking",
     "section": "",
-    "text": "V-Sekai is a platform that requires regular configuration of GoCD agents. This process can be time-consuming and prone to errors if not done correctly."
+    "text": "V-Sekai development team\nFire\nMMMaellon"
   },
   {
-    "objectID": "decisions/20230812-gocd-agent-setup.html#the-challenge",
-    "href": "decisions/20230812-gocd-agent-setup.html#the-challenge",
-    "title": "Proposed: Configuring GoCD Agents in V-Sekai",
+    "objectID": "decisions/20240715-vrchat-networking-mental-model.html#tags",
+    "href": "decisions/20240715-vrchat-networking-mental-model.html#tags",
+    "title": "Proposed: Create a Conceptual Model of VRChat Networking",
     "section": "",
-    "text": "The challenge is to configure the GoCD agents after a restart of the host machine. This involves accessing the GoCD server, navigating to the Agents page, enabling new agents, configuring agent resources, assigning environments, and saving changes."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20230812-gocd-agent-setup.html#the-strategy",
-    "href": "decisions/20230812-gocd-agent-setup.html#the-strategy",
-    "title": "Proposed: Configuring GoCD Agents in V-Sekai",
+    "objectID": "decisions/20240715-vrchat-networking-mental-model.html#further-reading",
+    "href": "decisions/20240715-vrchat-networking-mental-model.html#further-reading",
+    "title": "Proposed: Create a Conceptual Model of VRChat Networking",
     "section": "",
-    "text": "The strategy is to follow a step-by-step guide to ensure that all the necessary configurations are made correctly. This includes:\n\nAccessing the GoCD Server\nNavigating to the Agents Page\nEnabling New Agents\nConfiguring Agent Resources\nAssigning Environments\nSaving Changes"
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article.\n\n\nCentauri2442 recorded the byte count(s) of every synced variable type in udon\n\n\n\n\n\n\n\n\n\n\nSystem Type\nmaxByte\nminByte\nvariableType\nNotes\n\n\n\n\nSystem.Boolean\n2\n2\nBool\n\n\n\nSystem.Char\n2\n2\nChar\n\n\n\nSystem.Byte\n2\n2\nByte\n\n\n\nSystem.SByte\n2\n2\nSByte\n\n\n\nSystem.Int16\n4\n2\nShort\nSwaps every other\n\n\nSystem.UInt16\n4\n2\nUShort\nSwaps every other\n\n\nSystem.Int32\n8\n4\nInt\nSwaps every other\n\n\nSystem.UInt32\n8\n4\nUInt\nSwaps every other\n\n\nSystem.Int64\n12\n8\nLong\nSwaps every other\n\n\nSystem.UInt64\n12\n8\nULong\nSwaps every other\n\n\nSystem.Single\n8\n4\nFloat\nSwaps every other\n\n\nSystem.Double\n12\n8\nDouble\nSwaps every other\n\n\nUnityEngine.Vector2\n8\n8\nVector2\n\n\n\nUnityEngine.Vector3\n12\n12\nVector3\n\n\n\nUnityEngine.Vector4\n16\n16\nVector4\n\n\n\nUnityEngine.Quaternion\n16\n16\nQuaternion\n\n\n\nSystem.String\n84\n1\nString\nNull: No serialization | 84 + 1 byte per character, byte size allocated per for (84, 88, 92, etc)\n\n\nRVCUInt\n8\n8\nRVCUInt\n\n\n\nUnityEngine.Color\n8\n8\nColor\n\n\n\nUnityEngine.Color32\n8\n8\nColor32\n\n\n\nSystem.BooleanArray\n80\n80\nBooleanArray\n80 + array size in increments of 4 as buffer (80, 84, 88, etc) | Will increase every 4 values (5, 9, 13, etc)\n\n\nSystem.CharArray\n80\n80\nCharArray\n80 + array size in increments of 4 as buffer (80, 84, 88, etc) | Will increase every 4 values (5, 9, 13, etc)\n\n\nSystem.ByteArray\n80\n80\nByteArray\n80 + array size in increments of 4 as buffer (80, 84, 88, etc) | Will increase every 4 values (5, 9, 13, etc)\n\n\nSystem.SByteArray\n80\n80\nSByteArray\n80 + array size in increments of 4 as buffer (80, 84, 88, etc) | Will increase every 4 values (5, 9, 13, etc)\n\n\nSystem.Int16Array\n80\n80\nShortArray\n80 + array size in increments of 4 as buffer (80, 84, 88, etc) | Will increase every 2 values (3, 5, 7, etc)\n\n\nSystem.UInt16Array\n80\n80\nUShortArray\n80 + array size in increments of 4 as buffer (80, 84, 88, etc) | Will increase every 2 values (3, 5, 7, etc)\n\n\nSystem.Int32Array\n80\n80\nIntArray\n80 + array size * 4\n\n\nSystem.UInt32Array\n80\n80\nUIntArray\n80 + array size * 4\n\n\nSystem.Int64Array\n80\n80\nLongArray\n80 + array size * 8\n\n\nSystem.UInt64Array\n80\n80\nULongArray\n80 + array size * 8\n\n\nSystem.SingleArray\n80\n80\nFloatArray\n80 + array size * 4\n\n\nSystem.DoubleArray\n80\n80\nDoubleArray\n80 + array size * 8\n\n\nUnityEngine.Vector2Array\n80\n80\nVector2Array\n80 + array size * 8\n\n\nUnityEngine.Vector3Array\n80\n80\nVector3Array\n80 + array size * 12\n\n\nUnityEngine.Vector4Array\n80\n80\nVector4Array\n80 + array size * 16\n\n\nUnityEngine.QuaternionArray\n80\n80\nQuaternionArray\n80 + array size * 16\n\n\nSystem.StringArray\n80\n80\nStringArray\n84 + (2, 4, or 8 bytes per character). Size of 0: 84 bytes. Size greater than 0 but with any null values: 0 bytes. Size greater than 0 with all valid strings: 84 + (2, 4, or 8 bytes per character)\n\n\nRVCUStringArray\n80\n80\nRVCUStringArray\n84 + (2, 4, or 8 bytes per character). Size of 0: 84 bytes. Size greater than 0 but with any null values: 0 bytes. Size greater than 0 with all valid strings: 84 + (2, 4, or 8 bytes per character)\n\n\nUnityEngine.ColorArray\n80\n80\nColorArray\n80 + array size * 16\n\n\nUnityEngine.Color32Array\n80\n80\nColor32Array\n80 + array size * 4\n\n\n\n\n\n\nAnswer: In VRChat, which uses UdonSharp for scripting, there isn’t a hard limit on the number of UdonSharpBehaviour instances a world (or server instance) can have. However, practical limits are imposed by performance considerations. Each UdonSharpBehaviour consumes memory and processing power, so the total number you can effectively use will depend on the complexity of your scripts and the capabilities of the hardware running the world. It’s essential to optimize your scripts and manage resources efficiently to ensure smooth performance.\n\n\n\nAnswer: Yes, UdonSharpBehaviour instances can communicate with each other. Here are some ways they can interact:\n\nCustom Network Events: You can send custom network events (with zero parameters) to trigger actions in other UdonSharpBehaviour instances. The receiver won’t know who the sender is, and the action will be performed locally on the UdonSharpBehaviour’s current frame.\nSynced Variables: If you need to send data, it’s better to use synced variables rather than mixing them with network events. When these variables get updated, the OnDeserialization() method will be called. This is a function in UdonSharpBehaviour that you can override to handle any work needed with the updated variables.\n\n\n\n\nAnswer: You typically don’t mix network events with synced variables. If you need to send data, just use synced variables. When the variables get updated, OnDeserialization() will be called. That’s a function in UdonSharpBehaviour that you can override. Do all the work needed with the variables in OnDeserialization.\n\n\n\nAnswer: There’s an advanced feature called FieldChangeCallbacks that allows for code simplification. Basically, create a C# property with a getter and a setter and specify it as the field change callback. The setter will be called in addition to OnDeserialization when network updates come in. This helps combine the code for local and remote clients in the setter. This is an advanced code-writing optimization for making your code cleaner. No, it does not affect performance in terms of space and time. FieldChangeCallbacks reduces code repetition, thereby simplifying the codebase and making it more maintainable.\n\n\n\nAnswer: Assume we calculate the state of the world independently for each frame, without depending on previous frames. This means that while the exact values of the three variables are crucial for determining the current state, the order of changes within the same frame does not affect the final state interpretation at that frame."
   },
   {
-    "objectID": "decisions/20230812-gocd-agent-setup.html#the-upside",
-    "href": "decisions/20230812-gocd-agent-setup.html#the-upside",
-    "title": "Proposed: Configuring GoCD Agents in V-Sekai",
+    "objectID": "decisions/20240618-4-player-test-vsekai.html",
+    "href": "decisions/20240618-4-player-test-vsekai.html",
+    "title": "Proposed: 4 Player Test V-Sekai",
     "section": "",
-    "text": "By following this guide, users can ensure that their GoCD agents are configured correctly and ready to run jobs. This can save time and reduce the risk of errors."
+    "text": "V-Sekai is a social VR functionality for the Godot Engine. It’s an open-source project that brings social VR/VRSNS/metaverse components to the Godot Engine.\n\n\n\nWe want to host a 4 player test tonight.\n\n\n\nHere is a step-by-step guide on how we can achieve this:\n\nImport a map into V-Sekai: We will use a map with a CC-BY or CC0 license for the world upload.\nStart a server: We will set up and start a server where the test will be hosted.\nInvite people: We will then invite the players to join the test.\n\n\n\n\nHosting a 4 player test will allow us to:\n\nUnderstand the performance of our application with multiple users.\nIdentify any bugs or issues that may arise in a multi-player environment.\n\n\n\n\nPotential downsides could include:\n\nServer issues due to multiple connections.\nUnidentified bugs causing disruptions during the test.\n\n\n\n\nAlternative solutions could have been to conduct individual tests with each player, but this would not give us insights into the multi-player experience.\n\n\n\nThis proposal does not cover scenarios where more than 4 players are needed for testing.\n\n\n\nThe entire process from importing the map to inviting the players will be done by the V-Sekai development team.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20230812-gocd-agent-setup.html#the-downside",
-    "href": "decisions/20230812-gocd-agent-setup.html#the-downside",
-    "title": "Proposed: Configuring GoCD Agents in V-Sekai",
+    "objectID": "decisions/20240618-4-player-test-vsekai.html#context",
+    "href": "decisions/20240618-4-player-test-vsekai.html#context",
+    "title": "Proposed: 4 Player Test V-Sekai",
     "section": "",
-    "text": "The downside is that this process needs to be repeated every time the host machine is restarted. However, this is a necessary step to ensure that the GoCD agents function correctly."
+    "text": "V-Sekai is a social VR functionality for the Godot Engine. It’s an open-source project that brings social VR/VRSNS/metaverse components to the Godot Engine."
   },
   {
-    "objectID": "decisions/20230812-gocd-agent-setup.html#the-road-not-taken",
-    "href": "decisions/20230812-gocd-agent-setup.html#the-road-not-taken",
-    "title": "Proposed: Configuring GoCD Agents in V-Sekai",
+    "objectID": "decisions/20240618-4-player-test-vsekai.html#problem-statement",
+    "href": "decisions/20240618-4-player-test-vsekai.html#problem-statement",
+    "title": "Proposed: 4 Player Test V-Sekai",
     "section": "",
-    "text": "An alternative approach could be to automate this process using scripts or other automation tools. However, this would require additional technical expertise and may not be feasible for all users."
+    "text": "We want to host a 4 player test tonight."
   },
   {
-    "objectID": "decisions/20230812-gocd-agent-setup.html#the-infrequent-use-case",
-    "href": "decisions/20230812-gocd-agent-setup.html#the-infrequent-use-case",
-    "title": "Proposed: Configuring GoCD Agents in V-Sekai",
+    "objectID": "decisions/20240618-4-player-test-vsekai.html#solution",
+    "href": "decisions/20240618-4-player-test-vsekai.html#solution",
+    "title": "Proposed: 4 Player Test V-Sekai",
     "section": "",
-    "text": "In some cases, users may need to configure additional settings or use different resources and environments. These cases will require additional steps and may not be covered by this guide."
+    "text": "Here is a step-by-step guide on how we can achieve this:\n\nImport a map into V-Sekai: We will use a map with a CC-BY or CC0 license for the world upload.\nStart a server: We will set up and start a server where the test will be hosted.\nInvite people: We will then invite the players to join the test."
   },
   {
-    "objectID": "decisions/20230812-gocd-agent-setup.html#in-core-and-done-by-us",
-    "href": "decisions/20230812-gocd-agent-setup.html#in-core-and-done-by-us",
-    "title": "Proposed: Configuring GoCD Agents in V-Sekai",
+    "objectID": "decisions/20240618-4-player-test-vsekai.html#benefits",
+    "href": "decisions/20240618-4-player-test-vsekai.html#benefits",
+    "title": "Proposed: 4 Player Test V-Sekai",
     "section": "",
-    "text": "Yes, this guide was created by us and is part of our core documentation."
+    "text": "Hosting a 4 player test will allow us to:\n\nUnderstand the performance of our application with multiple users.\nIdentify any bugs or issues that may arise in a multi-player environment."
   },
   {
-    "objectID": "decisions/20230812-gocd-agent-setup.html#further-reading",
-    "href": "decisions/20230812-gocd-agent-setup.html#further-reading",
-    "title": "Proposed: Configuring GoCD Agents in V-Sekai",
+    "objectID": "decisions/20240618-4-player-test-vsekai.html#downsides",
+    "href": "decisions/20240618-4-player-test-vsekai.html#downsides",
+    "title": "Proposed: 4 Player Test V-Sekai",
     "section": "",
-    "text": "V-Sekai\nThis article is assisted by AI."
+    "text": "Potential downsides could include:\n\nServer issues due to multiple connections.\nUnidentified bugs causing disruptions during the test."
   },
   {
-    "objectID": "decisions/20230812-gocd-agent-setup.html#example-configuration",
-    "href": "decisions/20230812-gocd-agent-setup.html#example-configuration",
-    "title": "Proposed: Configuring GoCD Agents in V-Sekai",
+    "objectID": "decisions/20240618-4-player-test-vsekai.html#the-road-not-taken",
+    "href": "decisions/20240618-4-player-test-vsekai.html#the-road-not-taken",
+    "title": "Proposed: 4 Player Test V-Sekai",
     "section": "",
-    "text": "Agent Type\nResources\nEnvironments\n\n\n\n\ngocd-agent-59dbf9989-vp4d66\nlinux, mingw5\ndevelopment, itch-fire\n\n\ngocd-agent-dind-96575468d4-s29l2\ndind\ndevelopment, itch-fire\n\n\ngocd-agent-59dbf9989-cczqj\nlinux, mingw5\ndevelopment, itch-fire\n\n\ngocd-agent-59dbf9989-p6vs5\nlinux, mingw5\ndevelopment, itch-fire\n\n\ngocd-agent-59dbf9989-t4ckd\nlinux, mingw5\ndevelopment, itch-fire\n\n\ngocd-agent-dind-96575468d4-b6gq9\ndind\ndevelopment, itch-fire\n\n\n\nPlease note that the actual resources and environments will vary based on your specific setup."
+    "text": "Alternative solutions could have been to conduct individual tests with each player, but this would not give us insights into the multi-player experience."
   },
   {
-    "objectID": "decisions/20230602-v-sekai-roadmap.html",
-    "href": "decisions/20230602-v-sekai-roadmap.html",
-    "title": "Superseded: V-Sekai Roadmap and Goals 2023-06-02",
+    "objectID": "decisions/20240618-4-player-test-vsekai.html#the-infrequent-use-case",
+    "href": "decisions/20240618-4-player-test-vsekai.html#the-infrequent-use-case",
+    "title": "Proposed: 4 Player Test V-Sekai",
     "section": "",
-    "text": "Superseded: V-Sekai Roadmap and Goals 2023-06-02\n\nMetadata\n\nStatus: superseded by 20230608-v-sekai-roadmap.md \nDeciders: V-Sekai, fire, lyuma\nTags: V-Sekai,gpt4 summary\n\n\n\nContext and Problem Statement\nWhat is the V-Sekai Roadmap and Goals?\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nThe roadmap presented here is short-term.\n\n\nDescribe how your proposal will work with code, pseudo-code, mock-ups, or diagrams\ngraph LR\n  subgraph Short Term\n    A[June 02th, 2023] --&gt; E[VRM 1 import and export]\n    E --&gt; F[VRM 1 and OMI_personality]\n    F --&gt; G[Nightclub aquarium booth 4mx4mx5m]\n    G --&gt; H[Add jitter buffer to godot_speech]\n    H --&gt; I[Assist with onevoip]\n    I --&gt; K[What is stretchsense?]\n    K --&gt; L[How can we get more artwork?]\n    L --&gt; M[Collective work and other matters?]\n  end\n\n\nPositive Consequences\nWe can create V-Sekai easier.\n\n\nNegative Consequences\nOverhead might be hard.\n\n\nOption graveyard\nWe can avoid planning.\n\n\nIf this enhancement will be used infrequently, can it be worked around with a few lines of script?\nNo. This is a process.\n\n\nIs there a reason why this should be core and done by us?\nThis is a core process for V-Sekai.\n\n\nReferences\n\nV-Sekai"
+    "text": "This proposal does not cover scenarios where more than 4 players are needed for testing."
   },
   {
-    "objectID": "decisions/20240616-request-for-quad-mesh-dataset.html",
-    "href": "decisions/20240616-request-for-quad-mesh-dataset.html",
-    "title": "Proposed: Triangle to Quad Mesh Dataset Creation",
+    "objectID": "decisions/20240618-4-player-test-vsekai.html#in-core-and-done-by-us",
+    "href": "decisions/20240618-4-player-test-vsekai.html#in-core-and-done-by-us",
+    "title": "Proposed: 4 Player Test V-Sekai",
     "section": "",
-    "text": "Mesh Transformers, which consist of a construction worker (auto encoder) and an architect (transformer), aim to simplify the process of generating 3D models. Users can generate a 3D model using a prompt, eliminating the need to search through numerous 3D libraries.\n\n\n\nThe task at hand is to create a triangle mesh to quad mesh dataset that’s suitable for machine learning training. The meshes should be converted from triangles to quads, have captions, contain a maximum of 1k quads, and include at least 100 objects, should be 100_000 objects.\nNote that triangulating a quad mesh is not the same task.\n\n\n\nWe propose using remeshing tools convert triangle meshes to quad meshes.\nThe first dataset will focus on items an avatar would wear. This includes clothing, accessories, and other wearable items.\n\n\n\ncaption\ntype annotation\nmaterial annotation\n\n\n\n\n\nThis proposal simplifies the process of creating 3D models. It allows users to quickly receive a 3D model that fits their needs.\n\n\n\nThe proposal may require significant computational resources. Additionally, there may be some loss of detail during the conversion process.\n\n\n\nAn alternative approach would involve manually converting each quad mesh to a triangle mesh and adding captions. However, this method would be time-consuming and not feasible for large datasets.\n\n\n\nThe proposal may not benefit users who only need a small number of 3D models or those with very specific requirements.\n\n\n\nThe V-Sekai development team will be responsible for creating and converting the meshes.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\nFire\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - The GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nobjaverse_annotations\nV-Sekai.blue-tin-fox-models\n[https://github.com/maria-korosteleva/garment-pattern-generator]\n[https://cmp.felk.cvut.cz/t-less/index.html]\n\nAI assistant Aria assisted with this article."
+    "text": "The entire process from importing the map to inviting the players will be done by the V-Sekai development team."
   },
   {
-    "objectID": "decisions/20240616-request-for-quad-mesh-dataset.html#the-context",
-    "href": "decisions/20240616-request-for-quad-mesh-dataset.html#the-context",
-    "title": "Proposed: Triangle to Quad Mesh Dataset Creation",
+    "objectID": "decisions/20240618-4-player-test-vsekai.html#status",
+    "href": "decisions/20240618-4-player-test-vsekai.html#status",
+    "title": "Proposed: 4 Player Test V-Sekai",
     "section": "",
-    "text": "Mesh Transformers, which consist of a construction worker (auto encoder) and an architect (transformer), aim to simplify the process of generating 3D models. Users can generate a 3D model using a prompt, eliminating the need to search through numerous 3D libraries."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20240616-request-for-quad-mesh-dataset.html#the-problem-statement",
-    "href": "decisions/20240616-request-for-quad-mesh-dataset.html#the-problem-statement",
-    "title": "Proposed: Triangle to Quad Mesh Dataset Creation",
+    "objectID": "decisions/20240618-4-player-test-vsekai.html#decision-makers",
+    "href": "decisions/20240618-4-player-test-vsekai.html#decision-makers",
+    "title": "Proposed: 4 Player Test V-Sekai",
     "section": "",
-    "text": "The task at hand is to create a triangle mesh to quad mesh dataset that’s suitable for machine learning training. The meshes should be converted from triangles to quads, have captions, contain a maximum of 1k quads, and include at least 100 objects, should be 100_000 objects.\nNote that triangulating a quad mesh is not the same task."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20240616-request-for-quad-mesh-dataset.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240616-request-for-quad-mesh-dataset.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Triangle to Quad Mesh Dataset Creation",
+    "objectID": "decisions/20240618-4-player-test-vsekai.html#tags",
+    "href": "decisions/20240618-4-player-test-vsekai.html#tags",
+    "title": "Proposed: 4 Player Test V-Sekai",
     "section": "",
-    "text": "We propose using remeshing tools convert triangle meshes to quad meshes.\nThe first dataset will focus on items an avatar would wear. This includes clothing, accessories, and other wearable items.\n\n\n\ncaption\ntype annotation\nmaterial annotation"
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20240616-request-for-quad-mesh-dataset.html#the-benefits",
-    "href": "decisions/20240616-request-for-quad-mesh-dataset.html#the-benefits",
-    "title": "Proposed: Triangle to Quad Mesh Dataset Creation",
+    "objectID": "decisions/20240618-4-player-test-vsekai.html#further-reading",
+    "href": "decisions/20240618-4-player-test-vsekai.html#further-reading",
+    "title": "Proposed: 4 Player Test V-Sekai",
     "section": "",
-    "text": "This proposal simplifies the process of creating 3D models. It allows users to quickly receive a 3D model that fits their needs."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240616-request-for-quad-mesh-dataset.html#the-downsides",
-    "href": "decisions/20240616-request-for-quad-mesh-dataset.html#the-downsides",
-    "title": "Proposed: Triangle to Quad Mesh Dataset Creation",
+    "objectID": "decisions/20211031-create-a-demo-viewer-gallery.html",
+    "href": "decisions/20211031-create-a-demo-viewer-gallery.html",
+    "title": "Proposed: Create a demo viewer gallery",
     "section": "",
-    "text": "The proposal may require significant computational resources. Additionally, there may be some loss of detail during the conversion process."
+    "text": "[Describe the problem or limitation you are having in your project]\n[Describe the context and problem statement, e.g., in free form using two to three sentences. You may want to articulate the problem in the form of a question.]\n\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\n\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\n\n\n\n\n[e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]\n[…]\n\n\n\n\n\n[e.g., compromising quality attribute, follow-up decisions required, …]\n[…]\n\n[this section can be repeated for each option if more than one option is open for consideration]\n\n\n\n\nOption: \nRejection Reason: \n\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\n\n\n\nIs there a reason why this should be core and done by us?\n\n\n\n\nLink type \n… \n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240616-request-for-quad-mesh-dataset.html#the-road-not-taken",
-    "href": "decisions/20240616-request-for-quad-mesh-dataset.html#the-road-not-taken",
-    "title": "Proposed: Triangle to Quad Mesh Dataset Creation",
+    "objectID": "decisions/20211031-create-a-demo-viewer-gallery.html#context-and-problem-statement",
+    "href": "decisions/20211031-create-a-demo-viewer-gallery.html#context-and-problem-statement",
+    "title": "Proposed: Create a demo viewer gallery",
     "section": "",
-    "text": "An alternative approach would involve manually converting each quad mesh to a triangle mesh and adding captions. However, this method would be time-consuming and not feasible for large datasets."
+    "text": "[Describe the problem or limitation you are having in your project]\n[Describe the context and problem statement, e.g., in free form using two to three sentences. You may want to articulate the problem in the form of a question.]"
   },
   {
-    "objectID": "decisions/20240616-request-for-quad-mesh-dataset.html#the-infrequent-use-case",
-    "href": "decisions/20240616-request-for-quad-mesh-dataset.html#the-infrequent-use-case",
-    "title": "Proposed: Triangle to Quad Mesh Dataset Creation",
+    "objectID": "decisions/20211031-create-a-demo-viewer-gallery.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20211031-create-a-demo-viewer-gallery.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: Create a demo viewer gallery",
     "section": "",
-    "text": "The proposal may not benefit users who only need a small number of 3D models or those with very specific requirements."
+    "text": "Describe the proposed option and how it helps to overcome the problem or limitation"
   },
   {
-    "objectID": "decisions/20240616-request-for-quad-mesh-dataset.html#in-core-and-done-by-us",
-    "href": "decisions/20240616-request-for-quad-mesh-dataset.html#in-core-and-done-by-us",
-    "title": "Proposed: Triangle to Quad Mesh Dataset Creation",
+    "objectID": "decisions/20211031-create-a-demo-viewer-gallery.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20211031-create-a-demo-viewer-gallery.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Create a demo viewer gallery",
     "section": "",
-    "text": "The V-Sekai development team will be responsible for creating and converting the meshes."
+    "text": "Describe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams"
   },
   {
-    "objectID": "decisions/20240616-request-for-quad-mesh-dataset.html#status",
-    "href": "decisions/20240616-request-for-quad-mesh-dataset.html#status",
-    "title": "Proposed: Triangle to Quad Mesh Dataset Creation",
+    "objectID": "decisions/20211031-create-a-demo-viewer-gallery.html#positive-consequences",
+    "href": "decisions/20211031-create-a-demo-viewer-gallery.html#positive-consequences",
+    "title": "Proposed: Create a demo viewer gallery",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "[e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]\n[…]"
   },
   {
-    "objectID": "decisions/20240616-request-for-quad-mesh-dataset.html#decision-makers",
-    "href": "decisions/20240616-request-for-quad-mesh-dataset.html#decision-makers",
-    "title": "Proposed: Triangle to Quad Mesh Dataset Creation",
+    "objectID": "decisions/20211031-create-a-demo-viewer-gallery.html#negative-consequences",
+    "href": "decisions/20211031-create-a-demo-viewer-gallery.html#negative-consequences",
+    "title": "Proposed: Create a demo viewer gallery",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "[e.g., compromising quality attribute, follow-up decisions required, …]\n[…]\n\n[this section can be repeated for each option if more than one option is open for consideration]"
   },
   {
-    "objectID": "decisions/20240616-request-for-quad-mesh-dataset.html#tags",
-    "href": "decisions/20240616-request-for-quad-mesh-dataset.html#tags",
-    "title": "Proposed: Triangle to Quad Mesh Dataset Creation",
+    "objectID": "decisions/20211031-create-a-demo-viewer-gallery.html#option-graveyard",
+    "href": "decisions/20211031-create-a-demo-viewer-gallery.html#option-graveyard",
+    "title": "Proposed: Create a demo viewer gallery",
     "section": "",
-    "text": "V-Sekai\nFire"
+    "text": "Option: \nRejection Reason:"
   },
   {
-    "objectID": "decisions/20240616-request-for-quad-mesh-dataset.html#further-reading",
-    "href": "decisions/20240616-request-for-quad-mesh-dataset.html#further-reading",
-    "title": "Proposed: Triangle to Quad Mesh Dataset Creation",
+    "objectID": "decisions/20211031-create-a-demo-viewer-gallery.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20211031-create-a-demo-viewer-gallery.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Create a demo viewer gallery",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - The GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nobjaverse_annotations\nV-Sekai.blue-tin-fox-models\n[https://github.com/maria-korosteleva/garment-pattern-generator]\n[https://cmp.felk.cvut.cz/t-less/index.html]\n\nAI assistant Aria assisted with this article."
+    "text": "If this enhancement will not be used often, can it be worked around with a few lines of script?"
   },
   {
-    "objectID": "decisions/20230616-pmx-to-vrm.html",
-    "href": "decisions/20230616-pmx-to-vrm.html",
-    "title": "Proposed: V-Sekai Bone Hierarchy Conversion",
+    "objectID": "decisions/20211031-create-a-demo-viewer-gallery.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20211031-create-a-demo-viewer-gallery.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Create a demo viewer gallery",
     "section": "",
-    "text": "Status: proposed \nDeciders: V-Sekai, fire\nTags: V-Sekai, AI Assisted\n\n\n\n\nV-Sekai has a problem with its bone hierarchy conversion. This causes issues with Alicia’s hips-spine angle.\n\n\n\nWe suggest a new conversion method. It keeps the original bone hierarchy and translates bone names from Japanese to English. This avoids problems caused by changing the hierarchy.\n\n\n\n\nOriginal hierarchy (Japanese names):\nCenter (センター)\n├ UpperBody (上半身)\n└ LowerBody (下半身)\nNew method, same hierarchy, translated names:\nCenter (Hips)\n├ UpperBody (Spine)\n└ LowerBody (Legs)\nAfter the second conversion, the hierarchy changes:\nHips (LowerBody)\n└ Spine (UpperBody)\n\nThis solution keeps the right hips-spine angle for Alicia.\n\n\n\n\nKeeps the original bone hierarchy, avoiding animation issues.\nTranslates bone names to English, helping non-Japanese speakers.\n\n\n\n\n\nMight need more time to create the new method.\n\n\n\n\n\nChanging the hierarchy during conversion caused the problem.\n\n\n\n\nNo, this needs a new method in the bone hierarchy conversion process.\n\n\n\nYes, it affects character animations and user experience with V-Sekai models.\n\n\n\n\nV-Sekai"
+    "text": "Is there a reason why this should be core and done by us?"
   },
   {
-    "objectID": "decisions/20230616-pmx-to-vrm.html#metadata",
-    "href": "decisions/20230616-pmx-to-vrm.html#metadata",
-    "title": "Proposed: V-Sekai Bone Hierarchy Conversion",
+    "objectID": "decisions/20211031-create-a-demo-viewer-gallery.html#references",
+    "href": "decisions/20211031-create-a-demo-viewer-gallery.html#references",
+    "title": "Proposed: Create a demo viewer gallery",
     "section": "",
-    "text": "Status: proposed \nDeciders: V-Sekai, fire\nTags: V-Sekai, AI Assisted"
+    "text": "Link type \n…"
   },
   {
-    "objectID": "decisions/20230616-pmx-to-vrm.html#problem",
-    "href": "decisions/20230616-pmx-to-vrm.html#problem",
-    "title": "Proposed: V-Sekai Bone Hierarchy Conversion",
+    "objectID": "decisions/20211031-create-a-demo-viewer-gallery.html#derivative-license",
+    "href": "decisions/20211031-create-a-demo-viewer-gallery.html#derivative-license",
+    "title": "Proposed: Create a demo viewer gallery",
     "section": "",
-    "text": "V-Sekai has a problem with its bone hierarchy conversion. This causes issues with Alicia’s hips-spine angle."
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230616-pmx-to-vrm.html#solution",
-    "href": "decisions/20230616-pmx-to-vrm.html#solution",
-    "title": "Proposed: V-Sekai Bone Hierarchy Conversion",
+    "objectID": "decisions/20231027-apartment-building-vr.html",
+    "href": "decisions/20231027-apartment-building-vr.html",
+    "title": "Proposed: Build a Cozy Apartment in VR for V-Sekai",
     "section": "",
-    "text": "We suggest a new conversion method. It keeps the original bone hierarchy and translates bone names from Japanese to English. This avoids problems caused by changing the hierarchy."
+    "text": "Status: Proposed\nDeciders: V-Sekai, fire\nTags: V-Sekai, VR, 3D Modeling, Virtual Reality\n\n\n\n\nVirtual Reality (VR) is a rapidly growing technology with applications in various fields. One such application is the creation of virtual environments, such as apartments. This proposal aims to outline a strategy for building a cozy apartment in VR as a default environment for V-Sekai.\n\n\n\nThe main challenge is to create a realistic and immersive virtual environment that accurately represents a cozy apartment. This includes creating detailed 3D models of the apartment’s interior and exterior, as well as implementing realistic lighting and textures.\n\n\n\n\nMake a rough SVG sketch of the floor plan from the top for each of the topographical levels.\nConvert SVG to geometry using a suitable software tool.\nUse basic shapes to extrude the walls, floors, and ceilings of the apartment.\nCheck human dimensions to ensure the scale of the apartment is accurate and realistic.\nRevise and refine the model in virtual reality.\n\n\n\n\nBuilding a cozy apartment in VR can provide a unique and immersive experience for users. It can also be used for various purposes such as virtual tours, real estate marketing, and interior design planning.\n\n\n\nThe process of building a detailed and realistic VR apartment can be time-consuming and requires expertise in 3D modeling and VR technologies. Additionally, users will need VR equipment to fully experience the virtual apartment.\n\n\n\nAn alternative approach could have been to use pre-made 3D models of apartments. However, this would limit the customization options and may not provide the same level of detail and realism.\n\n\n\nIn cases where the VR apartment is used infrequently, it may not justify the time and resources spent on building it.\n\n\n\nThis project aligns with our core expertise in VR technologies and 3D modeling. Therefore, it can be done by us.\n\n\n\n\nV-Sekai GitHub Repository\nAI assists this article."
   },
   {
-    "objectID": "decisions/20230616-pmx-to-vrm.html#changes",
-    "href": "decisions/20230616-pmx-to-vrm.html#changes",
-    "title": "Proposed: V-Sekai Bone Hierarchy Conversion",
+    "objectID": "decisions/20231027-apartment-building-vr.html#metadata",
+    "href": "decisions/20231027-apartment-building-vr.html#metadata",
+    "title": "Proposed: Build a Cozy Apartment in VR for V-Sekai",
     "section": "",
-    "text": "Original hierarchy (Japanese names):\nCenter (センター)\n├ UpperBody (上半身)\n└ LowerBody (下半身)\nNew method, same hierarchy, translated names:\nCenter (Hips)\n├ UpperBody (Spine)\n└ LowerBody (Legs)\nAfter the second conversion, the hierarchy changes:\nHips (LowerBody)\n└ Spine (UpperBody)\n\nThis solution keeps the right hips-spine angle for Alicia."
+    "text": "Status: Proposed\nDeciders: V-Sekai, fire\nTags: V-Sekai, VR, 3D Modeling, Virtual Reality"
   },
   {
-    "objectID": "decisions/20230616-pmx-to-vrm.html#good-outcomes",
-    "href": "decisions/20230616-pmx-to-vrm.html#good-outcomes",
-    "title": "Proposed: V-Sekai Bone Hierarchy Conversion",
+    "objectID": "decisions/20231027-apartment-building-vr.html#the-backdrop",
+    "href": "decisions/20231027-apartment-building-vr.html#the-backdrop",
+    "title": "Proposed: Build a Cozy Apartment in VR for V-Sekai",
     "section": "",
-    "text": "Keeps the original bone hierarchy, avoiding animation issues.\nTranslates bone names to English, helping non-Japanese speakers."
+    "text": "Virtual Reality (VR) is a rapidly growing technology with applications in various fields. One such application is the creation of virtual environments, such as apartments. This proposal aims to outline a strategy for building a cozy apartment in VR as a default environment for V-Sekai."
   },
   {
-    "objectID": "decisions/20230616-pmx-to-vrm.html#bad-outcomes",
-    "href": "decisions/20230616-pmx-to-vrm.html#bad-outcomes",
-    "title": "Proposed: V-Sekai Bone Hierarchy Conversion",
+    "objectID": "decisions/20231027-apartment-building-vr.html#the-challenge",
+    "href": "decisions/20231027-apartment-building-vr.html#the-challenge",
+    "title": "Proposed: Build a Cozy Apartment in VR for V-Sekai",
     "section": "",
-    "text": "Might need more time to create the new method."
+    "text": "The main challenge is to create a realistic and immersive virtual environment that accurately represents a cozy apartment. This includes creating detailed 3D models of the apartment’s interior and exterior, as well as implementing realistic lighting and textures."
   },
   {
-    "objectID": "decisions/20230616-pmx-to-vrm.html#other-options",
-    "href": "decisions/20230616-pmx-to-vrm.html#other-options",
-    "title": "Proposed: V-Sekai Bone Hierarchy Conversion",
+    "objectID": "decisions/20231027-apartment-building-vr.html#the-strategy",
+    "href": "decisions/20231027-apartment-building-vr.html#the-strategy",
+    "title": "Proposed: Build a Cozy Apartment in VR for V-Sekai",
     "section": "",
-    "text": "Changing the hierarchy during conversion caused the problem."
+    "text": "Make a rough SVG sketch of the floor plan from the top for each of the topographical levels.\nConvert SVG to geometry using a suitable software tool.\nUse basic shapes to extrude the walls, floors, and ceilings of the apartment.\nCheck human dimensions to ensure the scale of the apartment is accurate and realistic.\nRevise and refine the model in virtual reality."
   },
   {
-    "objectID": "decisions/20230616-pmx-to-vrm.html#can-it-be-fixed-with-a-script",
-    "href": "decisions/20230616-pmx-to-vrm.html#can-it-be-fixed-with-a-script",
-    "title": "Proposed: V-Sekai Bone Hierarchy Conversion",
+    "objectID": "decisions/20231027-apartment-building-vr.html#the-upside",
+    "href": "decisions/20231027-apartment-building-vr.html#the-upside",
+    "title": "Proposed: Build a Cozy Apartment in VR for V-Sekai",
     "section": "",
-    "text": "No, this needs a new method in the bone hierarchy conversion process."
+    "text": "Building a cozy apartment in VR can provide a unique and immersive experience for users. It can also be used for various purposes such as virtual tours, real estate marketing, and interior design planning."
   },
   {
-    "objectID": "decisions/20230616-pmx-to-vrm.html#should-we-do-it",
-    "href": "decisions/20230616-pmx-to-vrm.html#should-we-do-it",
-    "title": "Proposed: V-Sekai Bone Hierarchy Conversion",
+    "objectID": "decisions/20231027-apartment-building-vr.html#the-downside",
+    "href": "decisions/20231027-apartment-building-vr.html#the-downside",
+    "title": "Proposed: Build a Cozy Apartment in VR for V-Sekai",
     "section": "",
-    "text": "Yes, it affects character animations and user experience with V-Sekai models."
+    "text": "The process of building a detailed and realistic VR apartment can be time-consuming and requires expertise in 3D modeling and VR technologies. Additionally, users will need VR equipment to fully experience the virtual apartment."
   },
   {
-    "objectID": "decisions/20230616-pmx-to-vrm.html#references",
-    "href": "decisions/20230616-pmx-to-vrm.html#references",
-    "title": "Proposed: V-Sekai Bone Hierarchy Conversion",
+    "objectID": "decisions/20231027-apartment-building-vr.html#the-road-not-taken",
+    "href": "decisions/20231027-apartment-building-vr.html#the-road-not-taken",
+    "title": "Proposed: Build a Cozy Apartment in VR for V-Sekai",
     "section": "",
-    "text": "V-Sekai"
+    "text": "An alternative approach could have been to use pre-made 3D models of apartments. However, this would limit the customization options and may not provide the same level of detail and realism."
   },
   {
-    "objectID": "decisions/20240621-proposal-template copy.html",
-    "href": "decisions/20240621-proposal-template copy.html",
-    "title": "Proposed: Command Traces with Server Backend",
+    "objectID": "decisions/20231027-apartment-building-vr.html#the-infrequent-use-case",
+    "href": "decisions/20231027-apartment-building-vr.html#the-infrequent-use-case",
+    "title": "Proposed: Build a Cozy Apartment in VR for V-Sekai",
     "section": "",
-    "text": "Status: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "In cases where the VR apartment is used infrequently, it may not justify the time and resources spent on building it."
   },
   {
-    "objectID": "decisions/20240621-proposal-template copy.html#status",
-    "href": "decisions/20240621-proposal-template copy.html#status",
-    "title": "Proposed: Command Traces with Server Backend",
+    "objectID": "decisions/20231027-apartment-building-vr.html#in-core-and-done-by-us",
+    "href": "decisions/20231027-apartment-building-vr.html#in-core-and-done-by-us",
+    "title": "Proposed: Build a Cozy Apartment in VR for V-Sekai",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "This project aligns with our core expertise in VR technologies and 3D modeling. Therefore, it can be done by us."
   },
   {
-    "objectID": "decisions/20240621-proposal-template copy.html#decision-makers",
-    "href": "decisions/20240621-proposal-template copy.html#decision-makers",
-    "title": "Proposed: Command Traces with Server Backend",
+    "objectID": "decisions/20231027-apartment-building-vr.html#further-reading",
+    "href": "decisions/20231027-apartment-building-vr.html#further-reading",
+    "title": "Proposed: Build a Cozy Apartment in VR for V-Sekai",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "V-Sekai GitHub Repository\nAI assists this article."
   },
   {
-    "objectID": "decisions/20240621-proposal-template copy.html#tags",
-    "href": "decisions/20240621-proposal-template copy.html#tags",
-    "title": "Proposed: Command Traces with Server Backend",
+    "objectID": "decisions/20231027-write-a-list-of-github-pull-requests.html",
+    "href": "decisions/20231027-write-a-list-of-github-pull-requests.html",
+    "title": "Accepted: Write List of Github Pull Requests for Review",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Status: Accepted\nDeciders: V-Sekai, fire\nTags: V-Sekai, Elixir, GitHub API, Pull Requests\n\n\n\n\nThe objective is to fetch and compile a list of open pull requests from the Godot Engine repository on GitHub using Elixir.\n\n\n\nThe challenge lies in utilizing the GitHub GraphQL API to retrieve data about open pull requests in a specific milestone of the Godot Engine repository. This data should then be written to a text file for subsequent review.\n\n\n\nHere’s the proposed solution:\n\nUtilize the HTTPoison library to send a POST request to the GitHub GraphQL API.\nParse the response with the Jason library.\nWrite the relevant data to a text file using Elixir’s built-in File module.\n\n\n\n\nThis method allows us to fetch and store data about open pull requests in a structured and automated manner. It also facilitates offline review of this data or sharing it with others.\n\n\n\nWhile the script is designed to handle pagination and fetch all open pull requests, it may still encounter issues if the number of requests exceeds the rate limit set by GitHub’s API. In such cases, some data might not be fetched until the rate limit resets. Additionally, as the script fetches data in batches of 50, it could take a significant amount of time to fetch all data if there are hundreds or thousands of open pull requests.\n\n\n\nAn alternative approach could have been to use the GitHub REST API instead of the GraphQL API. However, the GraphQL API allows for more flexible and efficient data fetching.\n\n\n\nThis script might not be suitable if you need to fetch data about closed pull requests or pull requests in other repositories or milestones.\n\n\n\nYes, this is a core part of our development process and is done by us.\n\n\n\nFor more information, you can visit the following links:\n\nV-Sekai\nGitHub GraphQL API\nElixir HTTPoison Library\nElixir Jason Library\nAllourideas Wiki Survey\n\nThis article was assisted by AI."
   },
   {
-    "objectID": "decisions/20240621-proposal-template copy.html#further-reading",
-    "href": "decisions/20240621-proposal-template copy.html#further-reading",
-    "title": "Proposed: Command Traces with Server Backend",
+    "objectID": "decisions/20231027-write-a-list-of-github-pull-requests.html#metadata",
+    "href": "decisions/20231027-write-a-list-of-github-pull-requests.html#metadata",
+    "title": "Accepted: Write List of Github Pull Requests for Review",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "Status: Accepted\nDeciders: V-Sekai, fire\nTags: V-Sekai, Elixir, GitHub API, Pull Requests"
   },
   {
-    "objectID": "decisions/20230527-v-sekai-roadmap.html",
-    "href": "decisions/20230527-v-sekai-roadmap.html",
-    "title": "Superseded: V-Sekai Roadmap and Goals 2023-05-19",
+    "objectID": "decisions/20231027-write-a-list-of-github-pull-requests.html#context",
+    "href": "decisions/20231027-write-a-list-of-github-pull-requests.html#context",
+    "title": "Accepted: Write List of Github Pull Requests for Review",
     "section": "",
-    "text": "Superseded: V-Sekai Roadmap and Goals 2023-05-19\n\nMetadata\n\nStatus: superseded by 20230602-v-sekai-roadmap.md \nDeciders: V-Sekai,fire,lyuma,\nTags: V-Sekai,chatgpt4 summary,\n\n\n\nContext and Problem Statement\nWhat is the V-Sekai Roadmap and Goals?\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nThe roadmap presented here is short-term.\n\n\nDescribe how your proposal will work with code, pseudo-code, mock-ups, or diagrams\ngraph LR\n  subgraph Short Term\n    A[May 27th, 2023] --&gt; D[Assist Godot Engine 4.1 features before May 30th feature freeze]\n    D --&gt; E[Vrm upload to the asset library after May 30th, 2023]\n    F --&gt; G[Unidot Unity Import upload to the asset library after May 30th, 2023]\n    G --&gt; H[Add jitter buffer to godot_speech]\n    H --&gt; I[Implement onevoip]\n  end\n\n\nPositive Consequences\nWe can create V-Sekai easier.\n\n\nNegative Consequences\nOverhead might be hard.\n\n\nOption graveyard\n\nImplementing a custom voice chat solution instead of using onevoip\nWaiting for Godot Engine 4.2 instead of assisting with 4.1 features\nIgnoring SkeletonIK3D issues and focusing on other aspects\n\n\n\nIf this enhancement will be used infrequently, can it be worked around with a few lines of script?\nNo. This is a process.\n\n\nIs there a reason why this should be core and done by us?\nThis is a core process for V-Sekai.\n\n\nReferences\n\nV-Sekai"
+    "text": "The objective is to fetch and compile a list of open pull requests from the Godot Engine repository on GitHub using Elixir."
   },
   {
-    "objectID": "decisions/20240613-1k-quad-limit.html",
-    "href": "decisions/20240613-1k-quad-limit.html",
-    "title": "Proposed: Training Mesh Transformer for 3D Avatar Creation",
+    "objectID": "decisions/20231027-write-a-list-of-github-pull-requests.html#problem",
+    "href": "decisions/20231027-write-a-list-of-github-pull-requests.html#problem",
+    "title": "Accepted: Write List of Github Pull Requests for Review",
     "section": "",
-    "text": "We are working with mesh transformer large language models.\n\n\n\nThe goal is to train the mesh transformer to create 3D avatar characters. The challenge lies in managing the complexity of the model and the computational resources required for training.\n\n\n\nOur approach involves using quad support for the avatars, which allows us to cut the avatar into smaller objects as part of the body. This method is more manageable and efficient than trying to train the model on larger body parts or the entire avatar.\nHowever, it’s important to note that we cannot use triangles and quads at the same time. Also, having a context length of 32k or more will require a bigger model, which might not be feasible unless we have a substantial GPU budget for computation.\nFor our training data, we aim to keep the triangle count below 5k triangles. We also need to consider the shape of the training data and the type of quad data we need to provide.\nIn terms of numbers, we’re looking at around 1500 triangles, which would result in 6k to 9k tokens. If these triangles are converted to quads and there is a reduction, we could aim for around MAX 8k tokens. In this case, 1 triangle equals 6 tokens, and 1 quad equals 8 tokens.\nThis means that 8,000 tokens would equate to 1,000 quads.\n\n\n\n\nTraining the mesh transformer on smaller body parts will make it more manageable and efficient.\nUsing quads instead of triangles could potentially reduce the complexity of the model.\n\n\n\n\n\nThe process requires a significant amount of GPU compute power, which could be expensive.\nThe model might not be able to handle large context lengths effectively.\n\n\n\n\n\nWe could have chosen to train the model on larger body parts or the entire avatar, but this would require significantly more computational resources.\n\n\n\n\n\nThis approach may not be suitable for avatars with complex structures or high polygon counts.\n\n\n\n\n\nThe training of the mesh transformer will be done by us, using our acquired resources and expertise.\n\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\niFire\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "The challenge lies in utilizing the GitHub GraphQL API to retrieve data about open pull requests in a specific milestone of the Godot Engine repository. This data should then be written to a text file for subsequent review."
   },
   {
-    "objectID": "decisions/20240613-1k-quad-limit.html#the-context",
-    "href": "decisions/20240613-1k-quad-limit.html#the-context",
-    "title": "Proposed: Training Mesh Transformer for 3D Avatar Creation",
+    "objectID": "decisions/20231027-write-a-list-of-github-pull-requests.html#solution",
+    "href": "decisions/20231027-write-a-list-of-github-pull-requests.html#solution",
+    "title": "Accepted: Write List of Github Pull Requests for Review",
     "section": "",
-    "text": "We are working with mesh transformer large language models."
+    "text": "Here’s the proposed solution:\n\nUtilize the HTTPoison library to send a POST request to the GitHub GraphQL API.\nParse the response with the Jason library.\nWrite the relevant data to a text file using Elixir’s built-in File module."
   },
   {
-    "objectID": "decisions/20240613-1k-quad-limit.html#the-problem-statement",
-    "href": "decisions/20240613-1k-quad-limit.html#the-problem-statement",
-    "title": "Proposed: Training Mesh Transformer for 3D Avatar Creation",
+    "objectID": "decisions/20231027-write-a-list-of-github-pull-requests.html#advantages",
+    "href": "decisions/20231027-write-a-list-of-github-pull-requests.html#advantages",
+    "title": "Accepted: Write List of Github Pull Requests for Review",
     "section": "",
-    "text": "The goal is to train the mesh transformer to create 3D avatar characters. The challenge lies in managing the complexity of the model and the computational resources required for training."
+    "text": "This method allows us to fetch and store data about open pull requests in a structured and automated manner. It also facilitates offline review of this data or sharing it with others."
   },
   {
-    "objectID": "decisions/20240613-1k-quad-limit.html#proposal",
-    "href": "decisions/20240613-1k-quad-limit.html#proposal",
-    "title": "Proposed: Training Mesh Transformer for 3D Avatar Creation",
+    "objectID": "decisions/20231027-write-a-list-of-github-pull-requests.html#disadvantages",
+    "href": "decisions/20231027-write-a-list-of-github-pull-requests.html#disadvantages",
+    "title": "Accepted: Write List of Github Pull Requests for Review",
     "section": "",
-    "text": "Our approach involves using quad support for the avatars, which allows us to cut the avatar into smaller objects as part of the body. This method is more manageable and efficient than trying to train the model on larger body parts or the entire avatar.\nHowever, it’s important to note that we cannot use triangles and quads at the same time. Also, having a context length of 32k or more will require a bigger model, which might not be feasible unless we have a substantial GPU budget for computation.\nFor our training data, we aim to keep the triangle count below 5k triangles. We also need to consider the shape of the training data and the type of quad data we need to provide.\nIn terms of numbers, we’re looking at around 1500 triangles, which would result in 6k to 9k tokens. If these triangles are converted to quads and there is a reduction, we could aim for around MAX 8k tokens. In this case, 1 triangle equals 6 tokens, and 1 quad equals 8 tokens.\nThis means that 8,000 tokens would equate to 1,000 quads."
+    "text": "While the script is designed to handle pagination and fetch all open pull requests, it may still encounter issues if the number of requests exceeds the rate limit set by GitHub’s API. In such cases, some data might not be fetched until the rate limit resets. Additionally, as the script fetches data in batches of 50, it could take a significant amount of time to fetch all data if there are hundreds or thousands of open pull requests."
   },
   {
-    "objectID": "decisions/20240613-1k-quad-limit.html#the-benefits",
-    "href": "decisions/20240613-1k-quad-limit.html#the-benefits",
-    "title": "Proposed: Training Mesh Transformer for 3D Avatar Creation",
+    "objectID": "decisions/20231027-write-a-list-of-github-pull-requests.html#alternatives",
+    "href": "decisions/20231027-write-a-list-of-github-pull-requests.html#alternatives",
+    "title": "Accepted: Write List of Github Pull Requests for Review",
     "section": "",
-    "text": "Training the mesh transformer on smaller body parts will make it more manageable and efficient.\nUsing quads instead of triangles could potentially reduce the complexity of the model."
+    "text": "An alternative approach could have been to use the GitHub REST API instead of the GraphQL API. However, the GraphQL API allows for more flexible and efficient data fetching."
   },
   {
-    "objectID": "decisions/20240613-1k-quad-limit.html#the-downsides",
-    "href": "decisions/20240613-1k-quad-limit.html#the-downsides",
-    "title": "Proposed: Training Mesh Transformer for 3D Avatar Creation",
+    "objectID": "decisions/20231027-write-a-list-of-github-pull-requests.html#limitations",
+    "href": "decisions/20231027-write-a-list-of-github-pull-requests.html#limitations",
+    "title": "Accepted: Write List of Github Pull Requests for Review",
     "section": "",
-    "text": "The process requires a significant amount of GPU compute power, which could be expensive.\nThe model might not be able to handle large context lengths effectively."
+    "text": "This script might not be suitable if you need to fetch data about closed pull requests or pull requests in other repositories or milestones."
   },
   {
-    "objectID": "decisions/20240613-1k-quad-limit.html#the-road-not-taken",
-    "href": "decisions/20240613-1k-quad-limit.html#the-road-not-taken",
-    "title": "Proposed: Training Mesh Transformer for 3D Avatar Creation",
+    "objectID": "decisions/20231027-write-a-list-of-github-pull-requests.html#ownership",
+    "href": "decisions/20231027-write-a-list-of-github-pull-requests.html#ownership",
+    "title": "Accepted: Write List of Github Pull Requests for Review",
     "section": "",
-    "text": "We could have chosen to train the model on larger body parts or the entire avatar, but this would require significantly more computational resources."
+    "text": "Yes, this is a core part of our development process and is done by us."
   },
   {
-    "objectID": "decisions/20240613-1k-quad-limit.html#the-infrequent-use-case",
-    "href": "decisions/20240613-1k-quad-limit.html#the-infrequent-use-case",
-    "title": "Proposed: Training Mesh Transformer for 3D Avatar Creation",
+    "objectID": "decisions/20231027-write-a-list-of-github-pull-requests.html#references",
+    "href": "decisions/20231027-write-a-list-of-github-pull-requests.html#references",
+    "title": "Accepted: Write List of Github Pull Requests for Review",
     "section": "",
-    "text": "This approach may not be suitable for avatars with complex structures or high polygon counts."
+    "text": "For more information, you can visit the following links:\n\nV-Sekai\nGitHub GraphQL API\nElixir HTTPoison Library\nElixir Jason Library\nAllourideas Wiki Survey\n\nThis article was assisted by AI."
   },
   {
-    "objectID": "decisions/20240613-1k-quad-limit.html#in-core-and-done-by-us",
-    "href": "decisions/20240613-1k-quad-limit.html#in-core-and-done-by-us",
-    "title": "Proposed: Training Mesh Transformer for 3D Avatar Creation",
-    "section": "",
-    "text": "The training of the mesh transformer will be done by us, using our acquired resources and expertise."
+    "objectID": "decisions/20231027-write-a-list-of-github-pull-requests.html#section",
+    "href": "decisions/20231027-write-a-list-of-github-pull-requests.html#section",
+    "title": "Accepted: Write List of Github Pull Requests for Review",
+    "section": "Section",
+    "text": "Section\ndefmodule PullRequestFetcher do\n  @query \"\"\"\n  {\n    repository(owner: \"godotengine\", name: \"godot\") {\n      milestone(number: 18) {\n        title\n        pullRequests(states: OPEN, first: 50) {\n          pageInfo {\n            endCursor\n            hasNextPage\n          }\n          nodes {\n            number\n            title\n            labels(first: 10) {\n              nodes {\n                name\n              }\n            }\n          }\n        }\n      }\n    }\n  }\n  \"\"\"\n\n  def fetch_and_write_pull_requests(query \\\\ @query, file \\\\ nil) do\n    file = if file, do: file, else: File.open!(\"pull_requests.txt\", [:write, :utf8])\n\n    {:ok, response} =\n      HTTPoison.post(\n        \"https://api.github.com/graphql\",\n        Jason.encode!(%{query: query}),\n        [\n          {\"Authorization\", \"Bearer #{System.fetch_env!(\"LB_GITHUB_TOKEN\")}\"},\n          {\"Content-Type\", \"application/json\"}\n        ],\n        timeout: 500_000,\n        reciv_timeout: 500_000\n      )\n\n    data = Jason.decode!(response.body)\n    pull_requests = data[\"data\"][\"repository\"][\"milestone\"][\"pullRequests\"]\n\n    for pull_request &lt;- pull_requests[\"nodes\"] do\n      labels = pull_request[\"labels\"][\"nodes\"] |&gt; Enum.map(& &1[\"name\"]) |&gt; Enum.join(\", \")\n      row = \"#{pull_request[\"title\"]} (##{pull_request[\"number\"]}) - Labels: [#{labels}]\"\n      IO.write(file, row &lt;&gt; \"\\n\")\n    end\n\n    if pull_requests[\"pageInfo\"][\"hasNextPage\"] do\n      next_query = \"\"\"\n      {\n        repository(owner: \"godotengine\", name: \"godot\") {\n          milestone(number: 18) {\n            title\n            pullRequests(states: OPEN, first: 50, after: \"#{pull_requests[\"pageInfo\"][\"endCursor\"]}\") {\n              pageInfo {\n                endCursor\n                hasNextPage\n              }\n              nodes {\n                number\n                title\n                labels(first: 10) {\n                  nodes {\n                    name\n                  }\n                }\n              }\n            }\n          }\n        }\n      }\n      \"\"\"\n\n      fetch_and_write_pull_requests(next_query, file)\n    else\n      :ok = File.close(file)\n    end\n  end\nend\n\nPullRequestFetcher.fetch_and_write_pull_requests()\n\n:ok"
   },
   {
-    "objectID": "decisions/20240613-1k-quad-limit.html#status",
-    "href": "decisions/20240613-1k-quad-limit.html#status",
-    "title": "Proposed: Training Mesh Transformer for 3D Avatar Creation",
+    "objectID": "decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html",
+    "href": "decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html",
+    "title": "Accepted: For Godot Engine changes use a decision flowchart",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "Status: accepted \nDeciders: V-Sekai,fire,lyuma,\nTags: V-Sekai,\n\n\n\nWe have conflicts on how to merge Godot. We need to organize our strategies.\n\n\n\nWe will write a decision flow chart on what to do.\n\n\n\nIs it upstreamable?\nIf upstreamable, commit to your own godot fork, and submit a Godot PR.\nThen, add this commit into the .gitassembly\nIf not upstreamable, and intended as a V-Sekai specific feature, make the commit in the V-Sekai godot fork, don’t submit a godot PR, and add to the .gitassembly.\nIf two upstreamable commits conflict, that is a godot problem because it implies the upstream open PRs would be broken if they both merged. There are two options:\nFirst, if the resolution to this merge conflict is itself something which must be upstreamed, a new PR should be opened or communication needs to happen between the PR maintainers.\nTemporarily, a new V-Sekai branch could be created which resolves this conflict while waiting for the upstream Godot maintainers to resolve the build issues.\nWorkflow for updating merge script.\n\nMake a local commit to merge-script-master\nRun the merge script\nIf successful, push (might happen automatically)\n\n\n\n\n\nEasier to remember solutions.\n\n\n\n\n\nLoss of flexibility.\n\n\n\n\n\nOption: Do adhoc decisions.\nRejection Reason: Not a better strategy.\n\n\n\n\nThis is a workflow design.\n\n\n\nOnly we care about our own policies.\n\n\n\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240613-1k-quad-limit.html#decision-makers",
-    "href": "decisions/20240613-1k-quad-limit.html#decision-makers",
-    "title": "Proposed: Training Mesh Transformer for 3D Avatar Creation",
+    "objectID": "decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html#context-and-problem-statement",
+    "href": "decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html#context-and-problem-statement",
+    "title": "Accepted: For Godot Engine changes use a decision flowchart",
     "section": "",
-    "text": "V-Sekai development team\niFire"
+    "text": "We have conflicts on how to merge Godot. We need to organize our strategies."
   },
   {
-    "objectID": "decisions/20240613-1k-quad-limit.html#tags",
-    "href": "decisions/20240613-1k-quad-limit.html#tags",
-    "title": "Proposed: Training Mesh Transformer for 3D Avatar Creation",
+    "objectID": "decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Accepted: For Godot Engine changes use a decision flowchart",
     "section": "",
-    "text": "V-Sekai"
+    "text": "We will write a decision flow chart on what to do."
   },
   {
-    "objectID": "decisions/20240613-1k-quad-limit.html#further-reading",
-    "href": "decisions/20240613-1k-quad-limit.html#further-reading",
-    "title": "Proposed: Training Mesh Transformer for 3D Avatar Creation",
+    "objectID": "decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Accepted: For Godot Engine changes use a decision flowchart",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "Is it upstreamable?\nIf upstreamable, commit to your own godot fork, and submit a Godot PR.\nThen, add this commit into the .gitassembly\nIf not upstreamable, and intended as a V-Sekai specific feature, make the commit in the V-Sekai godot fork, don’t submit a godot PR, and add to the .gitassembly.\nIf two upstreamable commits conflict, that is a godot problem because it implies the upstream open PRs would be broken if they both merged. There are two options:\nFirst, if the resolution to this merge conflict is itself something which must be upstreamed, a new PR should be opened or communication needs to happen between the PR maintainers.\nTemporarily, a new V-Sekai branch could be created which resolves this conflict while waiting for the upstream Godot maintainers to resolve the build issues.\nWorkflow for updating merge script.\n\nMake a local commit to merge-script-master\nRun the merge script\nIf successful, push (might happen automatically)"
   },
   {
-    "objectID": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html",
-    "href": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html",
-    "title": "Accepted: Create a Godot Engine asset store service on elixir and on sqlite.",
+    "objectID": "decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html#positive-consequences",
+    "href": "decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html#positive-consequences",
+    "title": "Accepted: For Godot Engine changes use a decision flowchart",
     "section": "",
-    "text": "Status: accepted \nDeciders: V-Sekai,fire,\nTags: V-Sekai,\n\n\n\nGodot Engine lacks an asset store service.\n\n\n\nWrite an elixir service that stores data in a database.\n\n\n\nUse elixir.\nUse ecto with sqlite.\n\nUpgrade elixir-sqlite/exqlite to 3.37.0\nUpgrade elixir-sqlite/ecto_sqlite3 to support strict mode.\nPunt using elixir-sqlite/ecto_sqlite3\n\nUse ecto with cockroachdb.\n\nMake distribution of OSS cockroachdb for windows.\n\nConvert godot asset store api to an openapi schema.\n\nhttps://mermade.github.io/openapi-gui/\n\nProvide a phoenix web server.\nWorks on Windows.\nDesign a sqlite dataabase schema.\nInvestigate membrane framework.\n\n\n\n\nAble to publish v-sekai addons.\nOverlay existing asset library\nAble to in a future feature post process packed scenes exported by V-Selai\n\n\n\n\n\n[e.g., compromising quality attribute, follow-up decisions required, …]\n\n[this section can be repeated for each option if more than one option is open for consideration]\n\n\n\n\nOption: Use the existing asset library backend\nRejection Reason: Does not use a modern tech stack.\n\n\n\n\nDon’t need a line of script.\n\n\n\nThis is a V-Sekai service and I know of an approach.\n\n\n\n\nhttps://github.com/godotengine/godot-asset-library/blob/master/API.md\nhttps://godotengine.org/\nhttps://www.sqlite.org/draft/stricttables.html\nhttps://github.com/elixir-sqlite/ecto_sqlite3/issues\nhttps://www.phoenixframework.org/\nhttps://github.com/elixir-sqlite/exqlite/issues/175 Upgrade to Sqlite 3.37\n\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Easier to remember solutions."
   },
   {
-    "objectID": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html#context-and-problem-statement",
-    "href": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html#context-and-problem-statement",
-    "title": "Accepted: Create a Godot Engine asset store service on elixir and on sqlite.",
+    "objectID": "decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html#negative-consequences",
+    "href": "decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html#negative-consequences",
+    "title": "Accepted: For Godot Engine changes use a decision flowchart",
     "section": "",
-    "text": "Godot Engine lacks an asset store service."
+    "text": "Loss of flexibility."
   },
   {
-    "objectID": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Accepted: Create a Godot Engine asset store service on elixir and on sqlite.",
+    "objectID": "decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html#option-graveyard",
+    "href": "decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html#option-graveyard",
+    "title": "Accepted: For Godot Engine changes use a decision flowchart",
     "section": "",
-    "text": "Write an elixir service that stores data in a database."
+    "text": "Option: Do adhoc decisions.\nRejection Reason: Not a better strategy."
   },
   {
-    "objectID": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Accepted: Create a Godot Engine asset store service on elixir and on sqlite.",
+    "objectID": "decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Accepted: For Godot Engine changes use a decision flowchart",
     "section": "",
-    "text": "Use elixir.\nUse ecto with sqlite.\n\nUpgrade elixir-sqlite/exqlite to 3.37.0\nUpgrade elixir-sqlite/ecto_sqlite3 to support strict mode.\nPunt using elixir-sqlite/ecto_sqlite3\n\nUse ecto with cockroachdb.\n\nMake distribution of OSS cockroachdb for windows.\n\nConvert godot asset store api to an openapi schema.\n\nhttps://mermade.github.io/openapi-gui/\n\nProvide a phoenix web server.\nWorks on Windows.\nDesign a sqlite dataabase schema.\nInvestigate membrane framework."
+    "text": "This is a workflow design."
   },
   {
-    "objectID": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html#positive-consequences",
-    "href": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html#positive-consequences",
-    "title": "Accepted: Create a Godot Engine asset store service on elixir and on sqlite.",
+    "objectID": "decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Accepted: For Godot Engine changes use a decision flowchart",
     "section": "",
-    "text": "Able to publish v-sekai addons.\nOverlay existing asset library\nAble to in a future feature post process packed scenes exported by V-Selai"
+    "text": "Only we care about our own policies."
   },
   {
-    "objectID": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html#negative-consequences",
-    "href": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html#negative-consequences",
-    "title": "Accepted: Create a Godot Engine asset store service on elixir and on sqlite.",
+    "objectID": "decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html#derivative-license",
+    "href": "decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html#derivative-license",
+    "title": "Accepted: For Godot Engine changes use a decision flowchart",
     "section": "",
-    "text": "[e.g., compromising quality attribute, follow-up decisions required, …]\n\n[this section can be repeated for each option if more than one option is open for consideration]"
+    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html#option-graveyard",
-    "href": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html#option-graveyard",
-    "title": "Accepted: Create a Godot Engine asset store service on elixir and on sqlite.",
+    "objectID": "decisions/20230123-integrate-blender-with-gltf-extensions-and-godot.html",
+    "href": "decisions/20230123-integrate-blender-with-gltf-extensions-and-godot.html",
+    "title": "Proposed: Better Godot Engine integration with Blender with gltf extensions",
     "section": "",
-    "text": "Option: Use the existing asset library backend\nRejection Reason: Does not use a modern tech stack."
+    "text": "Proposed: Better Godot Engine integration with Blender with gltf extensions\n\nContext and Problem Statement\nIntegration between blender and Godot Engine could be better.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nThe import of Godot Shaders to Godot Engine can help developers and developer artists workflows.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nWrite a design for embed the Godot shader and material information in the exported GLTF as an extension, then parse it in the Godot importer\n\n\nPositive Consequences\nEasier to use Godot Engine\n\n\nNegative Consequences\nThe Godot Engine shader definition may change\n\n\nOption graveyard\nStatus quo.\nCan we do nothing?\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nThis is probably a folder of python scripts.\n\n\nIs there a reason why this should be core and done by us?\nWe manage the Godot Engine import experience.\n\n\nReferences\n\nV-Sekai\n\n\n\nLicense of the contribution\nCopyright (c) 2022-present K. S. Ernest (iFire) Lee Copyright (c) 2022-present V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Accepted: Create a Godot Engine asset store service on elixir and on sqlite.",
+    "objectID": "decisions/20230415-load-collaborate.html",
+    "href": "decisions/20230415-load-collaborate.html",
+    "title": "Proposed: Hit a collaborate button to load up into V-Sekai",
     "section": "",
-    "text": "Don’t need a line of script."
+    "text": "Proposed: Hit a collaborate button to load up into V-Sekai\n\nContext and Problem Statement\nLoad up into V-Sekai as a server and then they hit a collaborate button\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\n\nThe host player invites friends to their world\nThe friends’ clients will automatically connect to the caching solution\nThe host player has a valid V-Sekai map project on their computer that they load up into V-Sekai as a server\n\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nAdd mvsqlite+godot script to collaboration.\n\n\nPositive Consequences\nSummoning new friends and collaborators.\n\n\nNegative Consequences\nNo response\n\n\nOption graveyard\nNo response\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nThis is more of a user experience thing.\n\n\nIs there a reason why this should be core and done by us?\nWe are driving this.\n\n\nReferences\n\nV-Sekai\n\n\n\nLicense of the contribution\nCopyright (c) 2022 K. S. Ernest (iFire) Lee Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Accepted: Create a Godot Engine asset store service on elixir and on sqlite.",
+    "objectID": "decisions/20230106-walking-controller-renik.html",
+    "href": "decisions/20230106-walking-controller-renik.html",
+    "title": "Accepted: Separate walking controller from RenIK for ManyBoneIK",
     "section": "",
-    "text": "This is a V-Sekai service and I know of an approach."
+    "text": "Status: accepted \nDeciders: V-Sekai,fire,lyuma,\nTags: V-Sekai,\n\n\n\nTo be able to implement ManyBoneIk we need to extract the walking controller from RenIK.\n\n\n\nExtract the walking controller into like a gdscript.\n\n\n\nSplit the tracker IKPoints from the controller.\n\n\n\nWe can migrate to many bone ik.\n\n\n\nConversion to gdscript may be slower.\n\n\n\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\n\nIt is a few lines of script.\n\n\n\nWe manage the avatar experience.\n\n\n\n\nV-Sekai\n\n\n\n\nMIT License\n\nCopyright (c) 2018-2022 SaracenOne\nCopyright (c) 2019-2022 K. S. Ernest (iFire) Lee (fire)\nCopyright (c) 2020-2022 Lyuma\nCopyright (c) 2020-2022 MMMaellon\nCopyright (c) 2022 V-Sekai Contributors\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
   },
   {
-    "objectID": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html#references",
-    "href": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html#references",
-    "title": "Accepted: Create a Godot Engine asset store service on elixir and on sqlite.",
+    "objectID": "decisions/20230106-walking-controller-renik.html#context-and-problem-statement",
+    "href": "decisions/20230106-walking-controller-renik.html#context-and-problem-statement",
+    "title": "Accepted: Separate walking controller from RenIK for ManyBoneIK",
     "section": "",
-    "text": "https://github.com/godotengine/godot-asset-library/blob/master/API.md\nhttps://godotengine.org/\nhttps://www.sqlite.org/draft/stricttables.html\nhttps://github.com/elixir-sqlite/ecto_sqlite3/issues\nhttps://www.phoenixframework.org/\nhttps://github.com/elixir-sqlite/exqlite/issues/175 Upgrade to Sqlite 3.37"
+    "text": "To be able to implement ManyBoneIk we need to extract the walking controller from RenIK."
   },
   {
-    "objectID": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html#derivative-license",
-    "href": "decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html#derivative-license",
-    "title": "Accepted: Create a Godot Engine asset store service on elixir and on sqlite.",
+    "objectID": "decisions/20230106-walking-controller-renik.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20230106-walking-controller-renik.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Accepted: Separate walking controller from RenIK for ManyBoneIK",
     "section": "",
-    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Extract the walking controller into like a gdscript."
   },
   {
-    "objectID": "decisions/20220916-too-many-branches-on-v-sekai-godot.html",
-    "href": "decisions/20220916-too-many-branches-on-v-sekai-godot.html",
-    "title": "Proposed: We have too many branches on V-Sekai/godot.",
+    "objectID": "decisions/20230106-walking-controller-renik.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20230106-walking-controller-renik.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Accepted: Separate walking controller from RenIK for ManyBoneIK",
     "section": "",
-    "text": "Proposed: We have too many branches on V-Sekai/godot.\n\nContext and Problem Statement\nWe have too many branches on V-Sekai/godot.\nA lot of branches are already merged, some are godot 3.x, some were for old alphas.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nCreate a procedure for deleting branches.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nWe should be able to delete merged branches after we remove it from merge script or move the branches to an archive repo with all the PRs.\n&lt;lyuma&gt; It’s definitely ok to delete when godot merges . you can still get the commit hash by git log | grep v-sekai/branchname in godotengine/godot.\n\n\nPositive Consequences\nLess confusion.\n\n\nNegative Consequences\nAccidentally deleting a used branch.\n\n\nOption graveyard\nDo nothing.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot applicable.\n\n\nIs there a reason why this should be core and done by us?\nWe own the V-Sekai/godot repository.\n\n\nReferences\n\nV-Sekai\n\n\n\nLicense of the contribution\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Split the tracker IKPoints from the controller."
   },
   {
-    "objectID": "decisions/20211104-research-mesh-tooling-with-kaolin.html",
-    "href": "decisions/20211104-research-mesh-tooling-with-kaolin.html",
-    "title": "Draft: Research mesh tooling with kaolin",
+    "objectID": "decisions/20230106-walking-controller-renik.html#positive-consequences",
+    "href": "decisions/20230106-walking-controller-renik.html#positive-consequences",
+    "title": "Accepted: Separate walking controller from RenIK for ManyBoneIK",
     "section": "",
-    "text": "Status: draft \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nNeed geometric tools for many things in the V-Sekai.\n[Describe the context and problem statement, e.g., in free form using two to three sentences. You may want to articulate the problem in the form of a question.]\n\n\n\nUse kaolin for some of the tools.\n\n\n\n\ngit clone https://github.com/NVIDIAGameWorks/kaolin.git\nInstall https://github.com/conda-forge/miniforge#mambaforge\nconda create --name kaolin python=3.9\nconda activate kaolin\nconda install pytorch torchvision torchaudio cudatoolkit=11.3 -c pytorch\npython setup.py develop\nTest the install. python -c \"import kaolin; print(kaolin.__version__)\"\n\n\n\nHi fire , thanks for your interest in Kaolin. Currently probably the best way to learn Kaolin is to take a look through the documentation and look for relevant functions. We hope to make more demos which will make learning Kaolin smoother in the future.\nThe functions which will be useful to you would be:\nkaolin.io.obj.import_mesh to import a mesh.\ntorch.meshgrid to generate a bunch of 3D coordinates of a voxel grid.\nkaolin.metrics.trianglemesh.point_to_mesh_distance to get the distance function for those points.\nkaolin.ops.mesh.check_sign to get the sign of the points to multiply with the distance.\nkaolin.ops.conversions.voxelgrids_to_trianglemeshes to convert the SDF grid to a mesh.\n\n\n\n\n\n[e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]\n\n\n\n\n\nMight require the GPU.\nInferencing may be difficult at interactive rates.\n\n\n\n\n\nOption: \nRejection Reason: \n\n\n\n\nCUDA, PyTorch and c++ are significant works.\n\n\n\nI have an approach!\n\n\n\n\nhttps://kaolin.readthedocs.io/en/latest/notes/installation.html\nhttps://www.alecjacobson.com/weblog/?tag=qslim\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "We can migrate to many bone ik."
   },
   {
-    "objectID": "decisions/20211104-research-mesh-tooling-with-kaolin.html#context-and-problem-statement",
-    "href": "decisions/20211104-research-mesh-tooling-with-kaolin.html#context-and-problem-statement",
-    "title": "Draft: Research mesh tooling with kaolin",
+    "objectID": "decisions/20230106-walking-controller-renik.html#negative-consequences",
+    "href": "decisions/20230106-walking-controller-renik.html#negative-consequences",
+    "title": "Accepted: Separate walking controller from RenIK for ManyBoneIK",
     "section": "",
-    "text": "Need geometric tools for many things in the V-Sekai.\n[Describe the context and problem statement, e.g., in free form using two to three sentences. You may want to articulate the problem in the form of a question.]"
+    "text": "Conversion to gdscript may be slower."
   },
   {
-    "objectID": "decisions/20211104-research-mesh-tooling-with-kaolin.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20211104-research-mesh-tooling-with-kaolin.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Draft: Research mesh tooling with kaolin",
+    "objectID": "decisions/20230106-walking-controller-renik.html#option-graveyard",
+    "href": "decisions/20230106-walking-controller-renik.html#option-graveyard",
+    "title": "Accepted: Separate walking controller from RenIK for ManyBoneIK",
     "section": "",
-    "text": "Use kaolin for some of the tools."
+    "text": "Option: The status quo. \nRejection Reason: This solves nothing."
   },
   {
-    "objectID": "decisions/20211104-research-mesh-tooling-with-kaolin.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20211104-research-mesh-tooling-with-kaolin.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Draft: Research mesh tooling with kaolin",
+    "objectID": "decisions/20230106-walking-controller-renik.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230106-walking-controller-renik.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Accepted: Separate walking controller from RenIK for ManyBoneIK",
     "section": "",
-    "text": "git clone https://github.com/NVIDIAGameWorks/kaolin.git\nInstall https://github.com/conda-forge/miniforge#mambaforge\nconda create --name kaolin python=3.9\nconda activate kaolin\nconda install pytorch torchvision torchaudio cudatoolkit=11.3 -c pytorch\npython setup.py develop\nTest the install. python -c \"import kaolin; print(kaolin.__version__)\"\n\n\n\nHi fire , thanks for your interest in Kaolin. Currently probably the best way to learn Kaolin is to take a look through the documentation and look for relevant functions. We hope to make more demos which will make learning Kaolin smoother in the future.\nThe functions which will be useful to you would be:\nkaolin.io.obj.import_mesh to import a mesh.\ntorch.meshgrid to generate a bunch of 3D coordinates of a voxel grid.\nkaolin.metrics.trianglemesh.point_to_mesh_distance to get the distance function for those points.\nkaolin.ops.mesh.check_sign to get the sign of the points to multiply with the distance.\nkaolin.ops.conversions.voxelgrids_to_trianglemeshes to convert the SDF grid to a mesh."
+    "text": "It is a few lines of script."
   },
   {
-    "objectID": "decisions/20211104-research-mesh-tooling-with-kaolin.html#positive-consequences",
-    "href": "decisions/20211104-research-mesh-tooling-with-kaolin.html#positive-consequences",
-    "title": "Draft: Research mesh tooling with kaolin",
+    "objectID": "decisions/20230106-walking-controller-renik.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230106-walking-controller-renik.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Accepted: Separate walking controller from RenIK for ManyBoneIK",
     "section": "",
-    "text": "[e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]"
+    "text": "We manage the avatar experience."
   },
   {
-    "objectID": "decisions/20211104-research-mesh-tooling-with-kaolin.html#negative-consequences",
-    "href": "decisions/20211104-research-mesh-tooling-with-kaolin.html#negative-consequences",
-    "title": "Draft: Research mesh tooling with kaolin",
+    "objectID": "decisions/20230106-walking-controller-renik.html#references",
+    "href": "decisions/20230106-walking-controller-renik.html#references",
+    "title": "Accepted: Separate walking controller from RenIK for ManyBoneIK",
     "section": "",
-    "text": "Might require the GPU.\nInferencing may be difficult at interactive rates."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20211104-research-mesh-tooling-with-kaolin.html#option-graveyard",
-    "href": "decisions/20211104-research-mesh-tooling-with-kaolin.html#option-graveyard",
-    "title": "Draft: Research mesh tooling with kaolin",
+    "objectID": "decisions/20230106-walking-controller-renik.html#license-of-the-contribution",
+    "href": "decisions/20230106-walking-controller-renik.html#license-of-the-contribution",
+    "title": "Accepted: Separate walking controller from RenIK for ManyBoneIK",
     "section": "",
-    "text": "Option: \nRejection Reason:"
+    "text": "MIT License\n\nCopyright (c) 2018-2022 SaracenOne\nCopyright (c) 2019-2022 K. S. Ernest (iFire) Lee (fire)\nCopyright (c) 2020-2022 Lyuma\nCopyright (c) 2020-2022 MMMaellon\nCopyright (c) 2022 V-Sekai Contributors\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
   },
   {
-    "objectID": "decisions/20211104-research-mesh-tooling-with-kaolin.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20211104-research-mesh-tooling-with-kaolin.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Draft: Research mesh tooling with kaolin",
+    "objectID": "decisions/20231027-dreamcraft3d-workflow.html",
+    "href": "decisions/20231027-dreamcraft3d-workflow.html",
+    "title": "Proposed: DreamCraft3D - A Hierarchical 3D Content Generation Method",
     "section": "",
-    "text": "CUDA, PyTorch and c++ are significant works."
+    "text": "Status: Proposed\nDeciders: V-Sekai, fire, Joseph Cat\nTags: V-Sekai, VRM, Rigging, 3D Modeling, DreamCraft3D\n\n\n\n\nDreamCraft3D is a hierarchical 3D content generation method that produces high-fidelity and coherent 3D objects. It uses a 2D reference image to guide the stages of geometry sculpting and texture boosting.\n\n\n\nThe main challenge lies in addressing the consistency issue that existing works encounter. To sculpt geometries that render coherently, DreamCraft3D performs score distillation sampling via a view-dependent diffusion model.\n\n\n\nThe strategy for implementing DreamCraft3D involves several steps:\n\nUse DreamCraft3D to generate high-fidelity and coherent 3D objects from 2D concept art.\nUtilize existing projects like Mixamo or AccuRig for rigging models.\nIf the topology isn’t suitable for animation, employ tools such as Quadwild BIMDF or Exoside’s Quad Remesher to enhance it.\nCorrect bad rigs using delta mush with the help of the Corrective Smooth Baker addon for Blender.\nDevelop software to perform clothing simulation differentially, referring to V-Sekai’s Cloth Dynamics as a guide.\n\n\n\n\nDreamCraft3D, with its tailored 3D priors throughout the hierarchical generation, can generate coherent 3D objects with photorealistic renderings. This advances the state-of-the-art in 3D content generation.\n\n\n\nThe process of converting 2D concept art into a rigged 3D model can be complex and time-consuming. It also requires expertise in 3D modeling and rigging.\n\n\n\nAn alternative approach could have been to manually create and rig the 3D models. However, this would be even more time-consuming and require even more expertise.\n\n\n\nIf the feature is used infrequently, it may not justify the time and resources spent on developing it.\n\n\n\nThis project aligns with our core expertise in VR technologies and 3D modeling. Therefore, it can be done by us.\n\n\n\nFor further reading, please refer to:\n\nV-Sekai GitHub Repository\nDreamCraft3D Code\nAI assists this article."
   },
   {
-    "objectID": "decisions/20211104-research-mesh-tooling-with-kaolin.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20211104-research-mesh-tooling-with-kaolin.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Draft: Research mesh tooling with kaolin",
+    "objectID": "decisions/20231027-dreamcraft3d-workflow.html#metadata",
+    "href": "decisions/20231027-dreamcraft3d-workflow.html#metadata",
+    "title": "Proposed: DreamCraft3D - A Hierarchical 3D Content Generation Method",
     "section": "",
-    "text": "I have an approach!"
+    "text": "Status: Proposed\nDeciders: V-Sekai, fire, Joseph Cat\nTags: V-Sekai, VRM, Rigging, 3D Modeling, DreamCraft3D"
   },
   {
-    "objectID": "decisions/20211104-research-mesh-tooling-with-kaolin.html#references",
-    "href": "decisions/20211104-research-mesh-tooling-with-kaolin.html#references",
-    "title": "Draft: Research mesh tooling with kaolin",
+    "objectID": "decisions/20231027-dreamcraft3d-workflow.html#context",
+    "href": "decisions/20231027-dreamcraft3d-workflow.html#context",
+    "title": "Proposed: DreamCraft3D - A Hierarchical 3D Content Generation Method",
     "section": "",
-    "text": "https://kaolin.readthedocs.io/en/latest/notes/installation.html\nhttps://www.alecjacobson.com/weblog/?tag=qslim"
+    "text": "DreamCraft3D is a hierarchical 3D content generation method that produces high-fidelity and coherent 3D objects. It uses a 2D reference image to guide the stages of geometry sculpting and texture boosting."
   },
   {
-    "objectID": "decisions/20211104-research-mesh-tooling-with-kaolin.html#derivative-license",
-    "href": "decisions/20211104-research-mesh-tooling-with-kaolin.html#derivative-license",
-    "title": "Draft: Research mesh tooling with kaolin",
+    "objectID": "decisions/20231027-dreamcraft3d-workflow.html#problem",
+    "href": "decisions/20231027-dreamcraft3d-workflow.html#problem",
+    "title": "Proposed: DreamCraft3D - A Hierarchical 3D Content Generation Method",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "The main challenge lies in addressing the consistency issue that existing works encounter. To sculpt geometries that render coherently, DreamCraft3D performs score distillation sampling via a view-dependent diffusion model."
   },
   {
-    "objectID": "decisions/20231108-v-sekai-chat-bot.html",
-    "href": "decisions/20231108-v-sekai-chat-bot.html",
-    "title": "Proposed: Creation of an ‘Ask V-Sekai’ Chatbot Using Vercel, OpenAI, and Neon PostgreSQL",
+    "objectID": "decisions/20231027-dreamcraft3d-workflow.html#solution",
+    "href": "decisions/20231027-dreamcraft3d-workflow.html#solution",
+    "title": "Proposed: DreamCraft3D - A Hierarchical 3D Content Generation Method",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai Development Team\nTags: V-Sekai, Chatbot, Vercel, OpenAI, Neon, PostgreSQL, AI, Serverless\n\n\n\n\nV-Sekai aims to provide immediate, AI-driven answers to community queries using a chatbot integrated with Discord.\n\n\n\nHow to develop an ‘Ask V-Sekai’ chatbot that utilizes Vercel serverless functions for interaction, OpenAI for natural language understanding, and Neon PostgreSQL for storing and retrieving knowledge?\n\n\n\n\nDesign and deploy a serverless function on Vercel that interfaces with Discord to receive questions.\nUse OpenAI’s API to process natural language queries and generate responses.\nStore and retrieve chatbot training and interaction data using Neon’s PostgreSQL service, leveraging the pgvector extension for efficient similarity analysis.\nContinuously improve the chatbot’s accuracy and response quality through data analytics and model fine-tuning.\n\n\n\n\n\nQuick, accurate responses to user inquiries, enhancing the V-Sekai community experience.\nLeverage cutting-edge AI and serverless technologies for a scalable, low-overhead solution.\nGather valuable interaction data to refine the chatbot and community support strategies.\n\n\n\n\n\nInitial complexity in setting up the integration between Vercel, OpenAI, and Neon PostgreSQL.\nOngoing maintenance and potential costs associated with OpenAI API usage.\n\n\n\n\n\nTraditional FAQ systems that do not offer real-time, AI-driven interaction and learning capabilities.\n\n\n\n\n\nComplex queries that require human intervention and are not yet within the scope of the AI’s training.\n\n\n\n\n\nThe development, deployment, and maintenance of the ‘Ask V-Sekai’ chatbot will be managed internally as a strategic tool for community engagement.\n\n\n\n\n\nVercel Serverless Functions Documentation\nOpenAI API Documentation\nNeon Tech Blog on Building an AI ChatBot\nAsk Neon This strategy was formulated with AI assistance."
+    "text": "The strategy for implementing DreamCraft3D involves several steps:\n\nUse DreamCraft3D to generate high-fidelity and coherent 3D objects from 2D concept art.\nUtilize existing projects like Mixamo or AccuRig for rigging models.\nIf the topology isn’t suitable for animation, employ tools such as Quadwild BIMDF or Exoside’s Quad Remesher to enhance it.\nCorrect bad rigs using delta mush with the help of the Corrective Smooth Baker addon for Blender.\nDevelop software to perform clothing simulation differentially, referring to V-Sekai’s Cloth Dynamics as a guide."
   },
   {
-    "objectID": "decisions/20231108-v-sekai-chat-bot.html#metadata",
-    "href": "decisions/20231108-v-sekai-chat-bot.html#metadata",
-    "title": "Proposed: Creation of an ‘Ask V-Sekai’ Chatbot Using Vercel, OpenAI, and Neon PostgreSQL",
+    "objectID": "decisions/20231027-dreamcraft3d-workflow.html#pros",
+    "href": "decisions/20231027-dreamcraft3d-workflow.html#pros",
+    "title": "Proposed: DreamCraft3D - A Hierarchical 3D Content Generation Method",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai Development Team\nTags: V-Sekai, Chatbot, Vercel, OpenAI, Neon, PostgreSQL, AI, Serverless"
+    "text": "DreamCraft3D, with its tailored 3D priors throughout the hierarchical generation, can generate coherent 3D objects with photorealistic renderings. This advances the state-of-the-art in 3D content generation."
   },
   {
-    "objectID": "decisions/20231108-v-sekai-chat-bot.html#the-backdrop",
-    "href": "decisions/20231108-v-sekai-chat-bot.html#the-backdrop",
-    "title": "Proposed: Creation of an ‘Ask V-Sekai’ Chatbot Using Vercel, OpenAI, and Neon PostgreSQL",
+    "objectID": "decisions/20231027-dreamcraft3d-workflow.html#cons",
+    "href": "decisions/20231027-dreamcraft3d-workflow.html#cons",
+    "title": "Proposed: DreamCraft3D - A Hierarchical 3D Content Generation Method",
     "section": "",
-    "text": "V-Sekai aims to provide immediate, AI-driven answers to community queries using a chatbot integrated with Discord."
+    "text": "The process of converting 2D concept art into a rigged 3D model can be complex and time-consuming. It also requires expertise in 3D modeling and rigging."
   },
   {
-    "objectID": "decisions/20231108-v-sekai-chat-bot.html#the-challenge",
-    "href": "decisions/20231108-v-sekai-chat-bot.html#the-challenge",
-    "title": "Proposed: Creation of an ‘Ask V-Sekai’ Chatbot Using Vercel, OpenAI, and Neon PostgreSQL",
+    "objectID": "decisions/20231027-dreamcraft3d-workflow.html#alternatives",
+    "href": "decisions/20231027-dreamcraft3d-workflow.html#alternatives",
+    "title": "Proposed: DreamCraft3D - A Hierarchical 3D Content Generation Method",
     "section": "",
-    "text": "How to develop an ‘Ask V-Sekai’ chatbot that utilizes Vercel serverless functions for interaction, OpenAI for natural language understanding, and Neon PostgreSQL for storing and retrieving knowledge?"
+    "text": "An alternative approach could have been to manually create and rig the 3D models. However, this would be even more time-consuming and require even more expertise."
   },
   {
-    "objectID": "decisions/20231108-v-sekai-chat-bot.html#the-strategy",
-    "href": "decisions/20231108-v-sekai-chat-bot.html#the-strategy",
-    "title": "Proposed: Creation of an ‘Ask V-Sekai’ Chatbot Using Vercel, OpenAI, and Neon PostgreSQL",
+    "objectID": "decisions/20231027-dreamcraft3d-workflow.html#infrequent-use-case",
+    "href": "decisions/20231027-dreamcraft3d-workflow.html#infrequent-use-case",
+    "title": "Proposed: DreamCraft3D - A Hierarchical 3D Content Generation Method",
     "section": "",
-    "text": "Design and deploy a serverless function on Vercel that interfaces with Discord to receive questions.\nUse OpenAI’s API to process natural language queries and generate responses.\nStore and retrieve chatbot training and interaction data using Neon’s PostgreSQL service, leveraging the pgvector extension for efficient similarity analysis.\nContinuously improve the chatbot’s accuracy and response quality through data analytics and model fine-tuning."
+    "text": "If the feature is used infrequently, it may not justify the time and resources spent on developing it."
   },
   {
-    "objectID": "decisions/20231108-v-sekai-chat-bot.html#the-upside",
-    "href": "decisions/20231108-v-sekai-chat-bot.html#the-upside",
-    "title": "Proposed: Creation of an ‘Ask V-Sekai’ Chatbot Using Vercel, OpenAI, and Neon PostgreSQL",
+    "objectID": "decisions/20231027-dreamcraft3d-workflow.html#ownership",
+    "href": "decisions/20231027-dreamcraft3d-workflow.html#ownership",
+    "title": "Proposed: DreamCraft3D - A Hierarchical 3D Content Generation Method",
     "section": "",
-    "text": "Quick, accurate responses to user inquiries, enhancing the V-Sekai community experience.\nLeverage cutting-edge AI and serverless technologies for a scalable, low-overhead solution.\nGather valuable interaction data to refine the chatbot and community support strategies."
+    "text": "This project aligns with our core expertise in VR technologies and 3D modeling. Therefore, it can be done by us."
   },
   {
-    "objectID": "decisions/20231108-v-sekai-chat-bot.html#the-downside",
-    "href": "decisions/20231108-v-sekai-chat-bot.html#the-downside",
-    "title": "Proposed: Creation of an ‘Ask V-Sekai’ Chatbot Using Vercel, OpenAI, and Neon PostgreSQL",
+    "objectID": "decisions/20231027-dreamcraft3d-workflow.html#references",
+    "href": "decisions/20231027-dreamcraft3d-workflow.html#references",
+    "title": "Proposed: DreamCraft3D - A Hierarchical 3D Content Generation Method",
     "section": "",
-    "text": "Initial complexity in setting up the integration between Vercel, OpenAI, and Neon PostgreSQL.\nOngoing maintenance and potential costs associated with OpenAI API usage."
+    "text": "For further reading, please refer to:\n\nV-Sekai GitHub Repository\nDreamCraft3D Code\nAI assists this article."
   },
   {
-    "objectID": "decisions/20231108-v-sekai-chat-bot.html#the-road-not-taken",
-    "href": "decisions/20231108-v-sekai-chat-bot.html#the-road-not-taken",
-    "title": "Proposed: Creation of an ‘Ask V-Sekai’ Chatbot Using Vercel, OpenAI, and Neon PostgreSQL",
+    "objectID": "decisions/20230123-face-helmet-capture.html",
+    "href": "decisions/20230123-face-helmet-capture.html",
+    "title": "Proposed: Face helmet capture",
     "section": "",
-    "text": "Traditional FAQ systems that do not offer real-time, AI-driven interaction and learning capabilities."
+    "text": "Proposed: Face helmet capture\n\nContext and Problem Statement\nWith a face helmet we can capture the face movement reliably.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nWe don’t have a way to talk to v-sekai for capture.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\n\nRun the v-sekai app\nExport either VMC or Godot Networking protocol for facial tracking\nOpen question on how to have tracking.\n\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nOption graveyard\nNo response\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot a few lines of script.\n\n\nIs there a reason why this should be core and done by us?\nI have the raw materials to do this.\n\n\nReferences\n\nV-Sekai\n\n\n\nLicense of the contribution\nCopyright (c) 2022 K. S. Ernest (iFire) Lee Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20231108-v-sekai-chat-bot.html#the-infrequent-use-case",
-    "href": "decisions/20231108-v-sekai-chat-bot.html#the-infrequent-use-case",
-    "title": "Proposed: Creation of an ‘Ask V-Sekai’ Chatbot Using Vercel, OpenAI, and Neon PostgreSQL",
+    "objectID": "decisions/20240709-anwave-set-nvidia-watt-limit.html",
+    "href": "decisions/20240709-anwave-set-nvidia-watt-limit.html",
+    "title": "Proposed: Set Nvidia Watt Limit with Anwave",
     "section": "",
-    "text": "Complex queries that require human intervention and are not yet within the scope of the AI’s training."
+    "text": "Users have reported issues with their PCs overheating, particularly during the summer months. This problem is exacerbated for those using high-performance GPUs on Windows 11 and using PC virtual reality apps like VRChat.\n\n\n\nOn Windows 11, my PC was overheating in the summer heat.\n\n\n\nTo mitigate the overheating issue, we propose using Anwave to power limit the GPU to 140 watts. This can be achieved by configuring the power management settings of the GPU.\n\nOpen Anwave application.\nNavigate to the power management section.\nSet the power limit of the GPU to 140 watts.\nApply the changes and monitor the GPU temperature.\n\n\n\n\n\nReduced Overheating: By limiting the power consumption of the GPU, the overall heat generated will be reduced.\nImproved Stability: Lower temperatures can lead to more stable system performance.\nExtended Hardware Lifespan: Reducing thermal stress can prolong the life of the GPU and other components.\n\n\n\n\n\nPerformance Impact: Limiting the power may reduce the performance of the GPU, affecting tasks that require high computational power.\nComplexity: Users need to be familiar with tools like Anwave and comfortable making changes to power settings.\n\n\n\n\nAlternative solutions such as improving cooling systems (e.g., adding more fans or using liquid cooling) were considered but deemed more costly and complex compared to software-based power management.\n\n\n\nThis solution might not be necessary for users in cooler climates or those who do not push their GPUs to high performance levels.\n\n\n\nThe implementation of this proposal will be handled internally by the V-Sekai development team, ensuring compatibility and stability with our existing systems.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nnvidia-power-management-power-control\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20231108-v-sekai-chat-bot.html#in-core-and-done-by-us",
-    "href": "decisions/20231108-v-sekai-chat-bot.html#in-core-and-done-by-us",
-    "title": "Proposed: Creation of an ‘Ask V-Sekai’ Chatbot Using Vercel, OpenAI, and Neon PostgreSQL",
+    "objectID": "decisions/20240709-anwave-set-nvidia-watt-limit.html#the-context",
+    "href": "decisions/20240709-anwave-set-nvidia-watt-limit.html#the-context",
+    "title": "Proposed: Set Nvidia Watt Limit with Anwave",
     "section": "",
-    "text": "The development, deployment, and maintenance of the ‘Ask V-Sekai’ chatbot will be managed internally as a strategic tool for community engagement."
+    "text": "Users have reported issues with their PCs overheating, particularly during the summer months. This problem is exacerbated for those using high-performance GPUs on Windows 11 and using PC virtual reality apps like VRChat."
   },
   {
-    "objectID": "decisions/20231108-v-sekai-chat-bot.html#further-reading",
-    "href": "decisions/20231108-v-sekai-chat-bot.html#further-reading",
-    "title": "Proposed: Creation of an ‘Ask V-Sekai’ Chatbot Using Vercel, OpenAI, and Neon PostgreSQL",
+    "objectID": "decisions/20240709-anwave-set-nvidia-watt-limit.html#the-problem-statement",
+    "href": "decisions/20240709-anwave-set-nvidia-watt-limit.html#the-problem-statement",
+    "title": "Proposed: Set Nvidia Watt Limit with Anwave",
     "section": "",
-    "text": "Vercel Serverless Functions Documentation\nOpenAI API Documentation\nNeon Tech Blog on Building an AI ChatBot\nAsk Neon This strategy was formulated with AI assistance."
+    "text": "On Windows 11, my PC was overheating in the summer heat."
   },
   {
-    "objectID": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html",
-    "href": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html",
-    "title": "Accepted: Rank skeleton #bone names with catboost",
+    "objectID": "decisions/20240709-anwave-set-nvidia-watt-limit.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240709-anwave-set-nvidia-watt-limit.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Set Nvidia Watt Limit with Anwave",
     "section": "",
-    "text": "Status: accepted \n\n\n\nImprove automatic #bone selection\n\n\n\nUse catboost to rank bones.\n\nCompile catboost as a library\nya make -r catboost/libs/model_interface/static\n\n\n\n\n\nInstall catboost\nGenerate training data.\nMapping to #bone names, attributes and categories.\nUse a training app create test data.\nGenerate train and test datasets for T-Posed character surfaces\nExample: CSV.\nLabel,Feature: #bone X global location in meters,Feature: #bone Y global location in meters,Feature: #bone Z global location in meters,Feature: #bone truncated normalized basis axis x 0,Feature: #bone truncated normalized basis axis x 1,Feature: #bone truncated normalized basis axis x 2,Feature: #bone truncated normalized basis axis y 0,Feature: #bone truncated normalized basis axis y 1,Feature: #bone truncated normalized basis axis y 2,Feature: #bone X global scale in meters,Feature: #bone Y global scale in meters,Feature: #bone Z global scale in meters,Feature: #bone Parent X global location in meters,Feature: #bone Parent Y global location in meters,Feature: #bone Parent Z global location in meters,Feature: #bone Parent truncated normalized basis axis x 0,Feature: #bone Parent truncated normalized basis axis x 1,Feature: #bone Parent truncated normalized basis axis x 2,Feature: #bone Parent truncated normalized basis axis y 0,Feature: #bone Parent truncated normalized basis axis y 1,Feature: #bone Parent truncated normalized basis axis y 2,Feature: #bone Parent X global scale in meters,Feature: #bone Parent Y global scale in meters,Feature: #bone Parent Z global scale in meters,Feature: Masculine (-1.0) and feminine (1.0),Feature: Body mass in kilograms,Feature: Head circumference in meters,Feature: Neckline circumference in meters,Feature: Left Shoulder circumference in meters,Feature: Right Shoulder circumference in meters,Feature: Left Elbow circumference in meters,Feature: Right Elbow circumference in meters,Feature: Left wrist circumference in meters,Feature: Right wrist circumference in meters,Feature: Waist circumference in meters,Feature: Left thigh circumference in meters,Feature: Right thigh circumference in meters,Feature: Left ankle circumference in meters,Feature: Right ankle circumference in meters,Feature: Animation Time,Category: Corresponding VRM Bone,Category: Title,Category: Author,Category: Specification Version,Category: Animation 1,0,0,0,1,0,0,0,1,0,1,1,1,0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,,AvatarSample_A,VRoid,,T-Pose\nA missing value means the field is empty.\nTrain.\nTest.\nUse on cpu and in Godot Engine.\nProbability of a click.\n\n\n\n\n\nWe can guess the proper name.\nUseful for the facial mapping problem?\nUseful for the character generator slider recommendation problem?\nGenerate test data by moving the character\nInference requires only single pose inputs.\n\n\n\n\n\nStarring at the abyss.\nNeeds to be have a smaller library size. Not almost 200 mb.\n\n\n\n\n\nOption:\n\nbpr from Quora\n\nRejection Reason:\n\nBpr from Quora is not used in production.\n\nOption:\n\ndlrm from facebook\n\nRejection Reason:\n\nToo difficult to run\n\n\n\n\n\nNot a few lines of code.\n\n\n\nWe need this to make the quality of life of creators better.\n\n\n\n\nhttps://github.com/facebookresearch/dlrm\nhttps://medium.com/@marthawhite_81346/learning-with-the-criteo-tb-dataset-e3ec12d9d77e\nhttps://www.kaggle.com/c/criteo-display-ad-challenge/data\nSkeleton pool operator from neural blend shapes.\nhttps://tailor.fandom.com/wiki/Types_of_measurement\nhttps://knarkowicz.wordpress.com/2014/04/16/octahedron-normal-vector-encoding/\nhttps://www.kaggle.com/egordm/deep-learning-recommendation-model-dlrm\n\n    @article{li2021learning,\n    author = {Li, Peizhuo and Aberman, Kfir and Hanocka, Rana and Liu, Libin and Sorkine-Hornung, Olga and Chen, Baoquan},\n    title = {Learning Skeletal Articulations with Neural Blend Shapes},\n    journal = {ACM Transactions on Graphics (TOG)},\n    volume = {40},\n    number = {4},\n    pages = {1},\n    year = {2021},\n    publisher = {ACM}\n    }\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.\n\n\n\n\nSupersedes 20211031-use-bpr-to-rank-skeleton-bone-names"
+    "text": "To mitigate the overheating issue, we propose using Anwave to power limit the GPU to 140 watts. This can be achieved by configuring the power management settings of the GPU.\n\nOpen Anwave application.\nNavigate to the power management section.\nSet the power limit of the GPU to 140 watts.\nApply the changes and monitor the GPU temperature."
   },
   {
-    "objectID": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#context-and-problem-statement",
-    "href": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#context-and-problem-statement",
-    "title": "Accepted: Rank skeleton #bone names with catboost",
+    "objectID": "decisions/20240709-anwave-set-nvidia-watt-limit.html#the-benefits",
+    "href": "decisions/20240709-anwave-set-nvidia-watt-limit.html#the-benefits",
+    "title": "Proposed: Set Nvidia Watt Limit with Anwave",
     "section": "",
-    "text": "Improve automatic #bone selection"
+    "text": "Reduced Overheating: By limiting the power consumption of the GPU, the overall heat generated will be reduced.\nImproved Stability: Lower temperatures can lead to more stable system performance.\nExtended Hardware Lifespan: Reducing thermal stress can prolong the life of the GPU and other components."
   },
   {
-    "objectID": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Accepted: Rank skeleton #bone names with catboost",
+    "objectID": "decisions/20240709-anwave-set-nvidia-watt-limit.html#the-downsides",
+    "href": "decisions/20240709-anwave-set-nvidia-watt-limit.html#the-downsides",
+    "title": "Proposed: Set Nvidia Watt Limit with Anwave",
     "section": "",
-    "text": "Use catboost to rank bones.\n\nCompile catboost as a library\nya make -r catboost/libs/model_interface/static"
+    "text": "Performance Impact: Limiting the power may reduce the performance of the GPU, affecting tasks that require high computational power.\nComplexity: Users need to be familiar with tools like Anwave and comfortable making changes to power settings."
   },
   {
-    "objectID": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Accepted: Rank skeleton #bone names with catboost",
+    "objectID": "decisions/20240709-anwave-set-nvidia-watt-limit.html#the-road-not-taken",
+    "href": "decisions/20240709-anwave-set-nvidia-watt-limit.html#the-road-not-taken",
+    "title": "Proposed: Set Nvidia Watt Limit with Anwave",
     "section": "",
-    "text": "Install catboost\nGenerate training data.\nMapping to #bone names, attributes and categories.\nUse a training app create test data.\nGenerate train and test datasets for T-Posed character surfaces\nExample: CSV.\nLabel,Feature: #bone X global location in meters,Feature: #bone Y global location in meters,Feature: #bone Z global location in meters,Feature: #bone truncated normalized basis axis x 0,Feature: #bone truncated normalized basis axis x 1,Feature: #bone truncated normalized basis axis x 2,Feature: #bone truncated normalized basis axis y 0,Feature: #bone truncated normalized basis axis y 1,Feature: #bone truncated normalized basis axis y 2,Feature: #bone X global scale in meters,Feature: #bone Y global scale in meters,Feature: #bone Z global scale in meters,Feature: #bone Parent X global location in meters,Feature: #bone Parent Y global location in meters,Feature: #bone Parent Z global location in meters,Feature: #bone Parent truncated normalized basis axis x 0,Feature: #bone Parent truncated normalized basis axis x 1,Feature: #bone Parent truncated normalized basis axis x 2,Feature: #bone Parent truncated normalized basis axis y 0,Feature: #bone Parent truncated normalized basis axis y 1,Feature: #bone Parent truncated normalized basis axis y 2,Feature: #bone Parent X global scale in meters,Feature: #bone Parent Y global scale in meters,Feature: #bone Parent Z global scale in meters,Feature: Masculine (-1.0) and feminine (1.0),Feature: Body mass in kilograms,Feature: Head circumference in meters,Feature: Neckline circumference in meters,Feature: Left Shoulder circumference in meters,Feature: Right Shoulder circumference in meters,Feature: Left Elbow circumference in meters,Feature: Right Elbow circumference in meters,Feature: Left wrist circumference in meters,Feature: Right wrist circumference in meters,Feature: Waist circumference in meters,Feature: Left thigh circumference in meters,Feature: Right thigh circumference in meters,Feature: Left ankle circumference in meters,Feature: Right ankle circumference in meters,Feature: Animation Time,Category: Corresponding VRM Bone,Category: Title,Category: Author,Category: Specification Version,Category: Animation 1,0,0,0,1,0,0,0,1,0,1,1,1,0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,,AvatarSample_A,VRoid,,T-Pose\nA missing value means the field is empty.\nTrain.\nTest.\nUse on cpu and in Godot Engine.\nProbability of a click."
+    "text": "Alternative solutions such as improving cooling systems (e.g., adding more fans or using liquid cooling) were considered but deemed more costly and complex compared to software-based power management."
   },
   {
-    "objectID": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#positive-consequences",
-    "href": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#positive-consequences",
-    "title": "Accepted: Rank skeleton #bone names with catboost",
+    "objectID": "decisions/20240709-anwave-set-nvidia-watt-limit.html#the-infrequent-use-case",
+    "href": "decisions/20240709-anwave-set-nvidia-watt-limit.html#the-infrequent-use-case",
+    "title": "Proposed: Set Nvidia Watt Limit with Anwave",
     "section": "",
-    "text": "We can guess the proper name.\nUseful for the facial mapping problem?\nUseful for the character generator slider recommendation problem?\nGenerate test data by moving the character\nInference requires only single pose inputs."
+    "text": "This solution might not be necessary for users in cooler climates or those who do not push their GPUs to high performance levels."
   },
   {
-    "objectID": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#negative-consequences",
-    "href": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#negative-consequences",
-    "title": "Accepted: Rank skeleton #bone names with catboost",
+    "objectID": "decisions/20240709-anwave-set-nvidia-watt-limit.html#in-core-and-done-by-us",
+    "href": "decisions/20240709-anwave-set-nvidia-watt-limit.html#in-core-and-done-by-us",
+    "title": "Proposed: Set Nvidia Watt Limit with Anwave",
     "section": "",
-    "text": "Starring at the abyss.\nNeeds to be have a smaller library size. Not almost 200 mb."
+    "text": "The implementation of this proposal will be handled internally by the V-Sekai development team, ensuring compatibility and stability with our existing systems."
   },
   {
-    "objectID": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#option-graveyard",
-    "href": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#option-graveyard",
-    "title": "Accepted: Rank skeleton #bone names with catboost",
+    "objectID": "decisions/20240709-anwave-set-nvidia-watt-limit.html#status",
+    "href": "decisions/20240709-anwave-set-nvidia-watt-limit.html#status",
+    "title": "Proposed: Set Nvidia Watt Limit with Anwave",
     "section": "",
-    "text": "Option:\n\nbpr from Quora\n\nRejection Reason:\n\nBpr from Quora is not used in production.\n\nOption:\n\ndlrm from facebook\n\nRejection Reason:\n\nToo difficult to run"
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Accepted: Rank skeleton #bone names with catboost",
+    "objectID": "decisions/20240709-anwave-set-nvidia-watt-limit.html#decision-makers",
+    "href": "decisions/20240709-anwave-set-nvidia-watt-limit.html#decision-makers",
+    "title": "Proposed: Set Nvidia Watt Limit with Anwave",
     "section": "",
-    "text": "Not a few lines of code."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Accepted: Rank skeleton #bone names with catboost",
+    "objectID": "decisions/20240709-anwave-set-nvidia-watt-limit.html#tags",
+    "href": "decisions/20240709-anwave-set-nvidia-watt-limit.html#tags",
+    "title": "Proposed: Set Nvidia Watt Limit with Anwave",
     "section": "",
-    "text": "We need this to make the quality of life of creators better."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#references",
-    "href": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#references",
-    "title": "Accepted: Rank skeleton #bone names with catboost",
+    "objectID": "decisions/20240709-anwave-set-nvidia-watt-limit.html#further-reading",
+    "href": "decisions/20240709-anwave-set-nvidia-watt-limit.html#further-reading",
+    "title": "Proposed: Set Nvidia Watt Limit with Anwave",
     "section": "",
-    "text": "https://github.com/facebookresearch/dlrm\nhttps://medium.com/@marthawhite_81346/learning-with-the-criteo-tb-dataset-e3ec12d9d77e\nhttps://www.kaggle.com/c/criteo-display-ad-challenge/data\nSkeleton pool operator from neural blend shapes.\nhttps://tailor.fandom.com/wiki/Types_of_measurement\nhttps://knarkowicz.wordpress.com/2014/04/16/octahedron-normal-vector-encoding/\nhttps://www.kaggle.com/egordm/deep-learning-recommendation-model-dlrm\n\n    @article{li2021learning,\n    author = {Li, Peizhuo and Aberman, Kfir and Hanocka, Rana and Liu, Libin and Sorkine-Hornung, Olga and Chen, Baoquan},\n    title = {Learning Skeletal Articulations with Neural Blend Shapes},\n    journal = {ACM Transactions on Graphics (TOG)},\n    volume = {40},\n    number = {4},\n    pages = {1},\n    year = {2021},\n    publisher = {ACM}\n    }"
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nnvidia-power-management-power-control\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#derivative-license",
-    "href": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#derivative-license",
-    "title": "Accepted: Rank skeleton #bone names with catboost",
+    "objectID": "decisions/20230620-doi-github.html",
+    "href": "decisions/20230620-doi-github.html",
+    "title": "Proposed: A Potential Solution for V-Sekai’s Identifier Assignment Challenge",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Status: proposed\nDeciders: V-Sekai, fire\nTags: V-Sekai, AI-augmented\n\n\n\n\nV-Sekai requires a method to assign permanent Digital Object Identifiers (DOIs) to their digital artifacts.\n\n\n\nLeverage Github and Zenodo to create a permanent DOI for V-Sekai’s data and code.\n\n\n\nFollow these steps in the guide below:\n\nSet up a Github Repository\nConnect Github to Zenodo\nActivate Github Repository in Zenodo\nGenerate a Release in Github\nObtain Your DOI from Zenodo\nShowcase DOI Badge in Github README (optional)\n\n\n\n\n\nPersistent DOIs for data and code\nEffortless referencing of repositories across browsers\nEnhanced visibility and accessibility of V-Sekai’s digital artifacts\n\n\n\n\n\nNecessitates managing multiple platforms (Github and Zenodo)\nPossible learning curve for users unfamiliar with Github and Zenodo\n\n\n\n\n\nUtilizing Figshare: Figshare is an alternative platform that enables assigning DOIs to digital artifacts. However, its integration with Github may not be as smooth as Zenodo’s.\nManual DOI registration: Manually registering a DOI through agencies like DataCite or CrossRef. This option can be labor-intensive and might involve additional fees.\nDepending on publisher-assigned DOIs: Some publishers allocate DOIs to supplementary materials during article publication. However, this option relies on the publisher’s policies and may not encompass all digital artifacts.\nEmploying institutional repositories: Certain institutions provide their own repositories for hosting digital artifacts and assigning DOIs. This option could be constrained by institutional policies and access limitations.\nNo DOI: Opting not to assign a DOI to V-Sekai’s digital artifacts, which would complicate referencing and long-term accessibility.\n\n\n\n\nNo, this solution demands integration between Github and Zenodo to produce a permanent DOI.\n\n\n\nYes, allocating a permanent DOI to V-Sekai’s digital artifacts guarantees long-term accessibility and accurate referencing in publications or other materials.\n\n\n\n\nV-Sekai\nGithub\nZenodo\nhttps://github.com/GlobalEcologyFlinders/assignDOI"
   },
   {
-    "objectID": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#links",
-    "href": "decisions/20220222-rank-skeleton-bone-names-with-catboost.html#links",
-    "title": "Accepted: Rank skeleton #bone names with catboost",
+    "objectID": "decisions/20230620-doi-github.html#metadata",
+    "href": "decisions/20230620-doi-github.html#metadata",
+    "title": "Proposed: A Potential Solution for V-Sekai’s Identifier Assignment Challenge",
     "section": "",
-    "text": "Supersedes 20211031-use-bpr-to-rank-skeleton-bone-names"
+    "text": "Status: proposed\nDeciders: V-Sekai, fire\nTags: V-Sekai, AI-augmented"
   },
   {
-    "objectID": "decisions/20230626-godot-vrm1-addon.html",
-    "href": "decisions/20230626-godot-vrm1-addon.html",
-    "title": "Proposed: Ship Godot Engine VRM1 to solve portable humanoid avatars",
+    "objectID": "decisions/20230620-doi-github.html#context-and-problem-statement",
+    "href": "decisions/20230620-doi-github.html#context-and-problem-statement",
+    "title": "Proposed: A Potential Solution for V-Sekai’s Identifier Assignment Challenge",
     "section": "",
-    "text": "Status: proposed \nDeciders: V-Sekai, fire, lyuma\nTags: V-Sekai, ai copilot\n\n\n\n\nHave portable humanoid avatars.\n\n\n\nShip Godot Engine VRM1 to Godot Engine asset Library.\n\n\n\n\nImplement basic humanoid avatar functionality such as rigging, animation, and basic physics through VRM1 spring bones.\nImplement support for both MToon1 and MToon0 materials, which provide a physically-based rendering approach for anime-style graphics.\nImplement support for the glTF PBR material type, which provides a more physically-based rendering approach for realistic graphics.\nImplement facial expressions, eye tracking, and lip syncing for a more immersive experience.\nImplement export by copying the import code in reverse, and refine it over time.\nUse the VRM spec’s suggested algorithm for implementing first-person view, which eliminates the need for head scaling.\nPrioritize necessary features and say no to suggestions that are not necessary to avoid feature bloat.\nDo not implement AnimationTree for this proposal.\n\n\n\n\n\nPortable humanoid avatars can be easily created and used in Godot Engine projects.\nThe addition of MToon1 material support provides a physically-based rendering approach for anime-style graphics.\nFacial expressions, eye tracking, and lip syncing enhance the immersive experience for users.\nExport functionality allows for easy sharing of avatars between projects and with other users.\nThe use of the VRM spec’s suggested algorithm for implementing first-person view simplifies the implementation process.\n\n\n\n\n\nThe implementation of these features may require additional development time and resources.\nThe addition of new features may increase the complexity of the codebase and require additional maintenance.\nThe use of the MToon1 material may require additional GPU resources and may not be suitable for low-end hardware.\nThe implementation of facial expressions, eye tracking, and lip syncing may require additional hardware or software support.\n\n\n\n\nWe are not implementing support for other material types beyond MToon0, MToon1 and gltf PBR, which could limit the range of visual styles that can be achieved with Godot Engine.\n\n\n\nIt is unlikely that these enhancements can be easily worked around with a few lines of script, as they require significant development effort and integration with the Godot Engine codebase.\n\n\n\n\nPortable humanoid avatars are a key feature for many Godot Engine projects, and the ability to easily create and use them is important for the success of the engine.\nThe addition of MToon1 material support and other enhancements will improve the quality and visual fidelity of Godot Engine projects.\nBy implementing these features in-house, we can ensure that they are well-integrated with the Godot Engine codebase and meet our quality standards.\n\n\n\n\n\nV-Sekai\nhttps://github.com/vrm-c/vrm-specification\nhttps://github.com/vrm-c/vrm-specification/blob/master/specification/VRMC_vrm-1.0/firstPerson.md#meshannotationauto-algorithm"
+    "text": "V-Sekai requires a method to assign permanent Digital Object Identifiers (DOIs) to their digital artifacts."
   },
   {
-    "objectID": "decisions/20230626-godot-vrm1-addon.html#metadata",
-    "href": "decisions/20230626-godot-vrm1-addon.html#metadata",
-    "title": "Proposed: Ship Godot Engine VRM1 to solve portable humanoid avatars",
+    "objectID": "decisions/20230620-doi-github.html#suggested-solution",
+    "href": "decisions/20230620-doi-github.html#suggested-solution",
+    "title": "Proposed: A Potential Solution for V-Sekai’s Identifier Assignment Challenge",
     "section": "",
-    "text": "Status: proposed \nDeciders: V-Sekai, fire, lyuma\nTags: V-Sekai, ai copilot"
+    "text": "Leverage Github and Zenodo to create a permanent DOI for V-Sekai’s data and code."
   },
   {
-    "objectID": "decisions/20230626-godot-vrm1-addon.html#context-and-problem-statement",
-    "href": "decisions/20230626-godot-vrm1-addon.html#context-and-problem-statement",
-    "title": "Proposed: Ship Godot Engine VRM1 to solve portable humanoid avatars",
+    "objectID": "decisions/20230620-doi-github.html#implementation",
+    "href": "decisions/20230620-doi-github.html#implementation",
+    "title": "Proposed: A Potential Solution for V-Sekai’s Identifier Assignment Challenge",
     "section": "",
-    "text": "Have portable humanoid avatars."
+    "text": "Follow these steps in the guide below:\n\nSet up a Github Repository\nConnect Github to Zenodo\nActivate Github Repository in Zenodo\nGenerate a Release in Github\nObtain Your DOI from Zenodo\nShowcase DOI Badge in Github README (optional)"
   },
   {
-    "objectID": "decisions/20230626-godot-vrm1-addon.html#proposed-solution",
-    "href": "decisions/20230626-godot-vrm1-addon.html#proposed-solution",
-    "title": "Proposed: Ship Godot Engine VRM1 to solve portable humanoid avatars",
+    "objectID": "decisions/20230620-doi-github.html#positive-consequences",
+    "href": "decisions/20230620-doi-github.html#positive-consequences",
+    "title": "Proposed: A Potential Solution for V-Sekai’s Identifier Assignment Challenge",
     "section": "",
-    "text": "Ship Godot Engine VRM1 to Godot Engine asset Library."
+    "text": "Persistent DOIs for data and code\nEffortless referencing of repositories across browsers\nEnhanced visibility and accessibility of V-Sekai’s digital artifacts"
   },
   {
-    "objectID": "decisions/20230626-godot-vrm1-addon.html#implementation",
-    "href": "decisions/20230626-godot-vrm1-addon.html#implementation",
-    "title": "Proposed: Ship Godot Engine VRM1 to solve portable humanoid avatars",
+    "objectID": "decisions/20230620-doi-github.html#negative-consequences",
+    "href": "decisions/20230620-doi-github.html#negative-consequences",
+    "title": "Proposed: A Potential Solution for V-Sekai’s Identifier Assignment Challenge",
     "section": "",
-    "text": "Implement basic humanoid avatar functionality such as rigging, animation, and basic physics through VRM1 spring bones.\nImplement support for both MToon1 and MToon0 materials, which provide a physically-based rendering approach for anime-style graphics.\nImplement support for the glTF PBR material type, which provides a more physically-based rendering approach for realistic graphics.\nImplement facial expressions, eye tracking, and lip syncing for a more immersive experience.\nImplement export by copying the import code in reverse, and refine it over time.\nUse the VRM spec’s suggested algorithm for implementing first-person view, which eliminates the need for head scaling.\nPrioritize necessary features and say no to suggestions that are not necessary to avoid feature bloat.\nDo not implement AnimationTree for this proposal."
+    "text": "Necessitates managing multiple platforms (Github and Zenodo)\nPossible learning curve for users unfamiliar with Github and Zenodo"
   },
   {
-    "objectID": "decisions/20230626-godot-vrm1-addon.html#positive-consequences",
-    "href": "decisions/20230626-godot-vrm1-addon.html#positive-consequences",
-    "title": "Proposed: Ship Godot Engine VRM1 to solve portable humanoid avatars",
+    "objectID": "decisions/20230620-doi-github.html#alternative-options",
+    "href": "decisions/20230620-doi-github.html#alternative-options",
+    "title": "Proposed: A Potential Solution for V-Sekai’s Identifier Assignment Challenge",
     "section": "",
-    "text": "Portable humanoid avatars can be easily created and used in Godot Engine projects.\nThe addition of MToon1 material support provides a physically-based rendering approach for anime-style graphics.\nFacial expressions, eye tracking, and lip syncing enhance the immersive experience for users.\nExport functionality allows for easy sharing of avatars between projects and with other users.\nThe use of the VRM spec’s suggested algorithm for implementing first-person view simplifies the implementation process."
+    "text": "Utilizing Figshare: Figshare is an alternative platform that enables assigning DOIs to digital artifacts. However, its integration with Github may not be as smooth as Zenodo’s.\nManual DOI registration: Manually registering a DOI through agencies like DataCite or CrossRef. This option can be labor-intensive and might involve additional fees.\nDepending on publisher-assigned DOIs: Some publishers allocate DOIs to supplementary materials during article publication. However, this option relies on the publisher’s policies and may not encompass all digital artifacts.\nEmploying institutional repositories: Certain institutions provide their own repositories for hosting digital artifacts and assigning DOIs. This option could be constrained by institutional policies and access limitations.\nNo DOI: Opting not to assign a DOI to V-Sekai’s digital artifacts, which would complicate referencing and long-term accessibility."
   },
   {
-    "objectID": "decisions/20230626-godot-vrm1-addon.html#negative-consequences",
-    "href": "decisions/20230626-godot-vrm1-addon.html#negative-consequences",
-    "title": "Proposed: Ship Godot Engine VRM1 to solve portable humanoid avatars",
+    "objectID": "decisions/20230620-doi-github.html#can-this-enhancement-be-worked-around-with-a-few-lines-of-script-if-used-infrequently",
+    "href": "decisions/20230620-doi-github.html#can-this-enhancement-be-worked-around-with-a-few-lines-of-script-if-used-infrequently",
+    "title": "Proposed: A Potential Solution for V-Sekai’s Identifier Assignment Challenge",
     "section": "",
-    "text": "The implementation of these features may require additional development time and resources.\nThe addition of new features may increase the complexity of the codebase and require additional maintenance.\nThe use of the MToon1 material may require additional GPU resources and may not be suitable for low-end hardware.\nThe implementation of facial expressions, eye tracking, and lip syncing may require additional hardware or software support."
+    "text": "No, this solution demands integration between Github and Zenodo to produce a permanent DOI."
   },
   {
-    "objectID": "decisions/20230626-godot-vrm1-addon.html#option-graveyard",
-    "href": "decisions/20230626-godot-vrm1-addon.html#option-graveyard",
-    "title": "Proposed: Ship Godot Engine VRM1 to solve portable humanoid avatars",
+    "objectID": "decisions/20230620-doi-github.html#is-there-a-reason-why-this-should-be-core-and-implemented-by-us",
+    "href": "decisions/20230620-doi-github.html#is-there-a-reason-why-this-should-be-core-and-implemented-by-us",
+    "title": "Proposed: A Potential Solution for V-Sekai’s Identifier Assignment Challenge",
     "section": "",
-    "text": "We are not implementing support for other material types beyond MToon0, MToon1 and gltf PBR, which could limit the range of visual styles that can be achieved with Godot Engine."
+    "text": "Yes, allocating a permanent DOI to V-Sekai’s digital artifacts guarantees long-term accessibility and accurate referencing in publications or other materials."
   },
   {
-    "objectID": "decisions/20230626-godot-vrm1-addon.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230626-godot-vrm1-addon.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Ship Godot Engine VRM1 to solve portable humanoid avatars",
+    "objectID": "decisions/20230620-doi-github.html#references",
+    "href": "decisions/20230620-doi-github.html#references",
+    "title": "Proposed: A Potential Solution for V-Sekai’s Identifier Assignment Challenge",
     "section": "",
-    "text": "It is unlikely that these enhancements can be easily worked around with a few lines of script, as they require significant development effort and integration with the Godot Engine codebase."
+    "text": "V-Sekai\nGithub\nZenodo\nhttps://github.com/GlobalEcologyFlinders/assignDOI"
   },
   {
-    "objectID": "decisions/20230626-godot-vrm1-addon.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230626-godot-vrm1-addon.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Ship Godot Engine VRM1 to solve portable humanoid avatars",
+    "objectID": "decisions/20230803-idle-rpg-home.html",
+    "href": "decisions/20230803-idle-rpg-home.html",
+    "title": "Proposed: Social RPG World Proposal",
     "section": "",
-    "text": "Portable humanoid avatars are a key feature for many Godot Engine projects, and the ability to easily create and use them is important for the success of the engine.\nThe addition of MToon1 material support and other enhancements will improve the quality and visual fidelity of Godot Engine projects.\nBy implementing these features in-house, we can ensure that they are well-integrated with the Godot Engine codebase and meet our quality standards."
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nWe aim to engage users in the V-Sekai world. A social RPG game could be the solution, offering continuous gameplay that encourages interaction.\n\n\n\n\n\nOur game is set in a “Comfortable Cyberprep” realm. It merges sci-fi with ease, where tech and humans coexist. Players explore a future city where technology is part of life. The city glows with neon lights, holographic interfaces, and advanced AI, yet retains homeliness.\n\nStatic couch collider: A fixed location for player interaction.\nNon-functional Static bed without collider: A rejuvenation spot for characters.\nNon-functional Mirror that is off: A decorative element with potential uses.\nNon-functional Video player screen that is off: A feature for entertainment or information.\n\n\n\n\n\nChill and hang with friends: The game provides a relaxed environment for socializing.\nPlay a game: Beyond socializing, players can engage in an RPG game.\n\n\n\n\n\nRPG game with level rewards: Players improve through play.\nCombat System: Players choose between different types of weapons or defensive items.\nStationary Target Combat System: A mechanism where players engage in combat with fixed-position targets.\n\n\n\n\n\nSettings are not persisted past server restart.\nLimited number of weapon choices: To maintain balance.\nCooldown period for using healing items: To prevent spamming.\n\n\n\n\n\nImplementation details will be decided upon proposal acceptance.\n\n\n\n\nIncreased user engagement\nProlonged interaction within the V-Sekai world\nEnhanced socialization among players\n\n\n\n\n\nPotential increase in development time and resources\nRisk of unbalanced gameplay if the RPG system is not properly designed\n\n\n\n\nOptions considered but discarded:\n\nIdle RPG Mechanic: Removed due to potential decrease in active engagement from players.\n\n\n\n\nThe frequency of use depends on the players’ engagement level. However, given the complexity of an RPG system, it cannot be simply worked around with a few lines of script.\n\n\n\nCreating an RPG system as a feature of V-Sekai will enhance the overall user experience and engagement, which aligns with our goal of providing a compelling virtual world.\n\n\n\n\nV-Sekai"
   },
   {
-    "objectID": "decisions/20230626-godot-vrm1-addon.html#references",
-    "href": "decisions/20230626-godot-vrm1-addon.html#references",
-    "title": "Proposed: Ship Godot Engine VRM1 to solve portable humanoid avatars",
+    "objectID": "decisions/20230803-idle-rpg-home.html#metadata",
+    "href": "decisions/20230803-idle-rpg-home.html#metadata",
+    "title": "Proposed: Social RPG World Proposal",
     "section": "",
-    "text": "V-Sekai\nhttps://github.com/vrm-c/vrm-specification\nhttps://github.com/vrm-c/vrm-specification/blob/master/specification/VRMC_vrm-1.0/firstPerson.md#meshannotationauto-algorithm"
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20240217-container-2-wasm.html",
-    "href": "decisions/20240217-container-2-wasm.html",
-    "title": "Proposed: Container2Wasm Integration in V-Sekai",
+    "objectID": "decisions/20230803-idle-rpg-home.html#context-and-problem-statement",
+    "href": "decisions/20230803-idle-rpg-home.html#context-and-problem-statement",
+    "title": "Proposed: Social RPG World Proposal",
     "section": "",
-    "text": "V-Sekai is a project focused on social VR functionality for the Godot Engine. It aims to bring social VR/VRSNS/metaverse components to the Godot Engine, enhancing avatar customization and AI-driven facial expressions.\n\n\n\nIntegrating complex backend services directly within a browser or lightweight client environments can be challenging. This integration is crucial for enhancing avatar customization and AI-driven facial expressions by leveraging containerized services.\n\n\n\nWe propose to use container2wasm, a tool that converts container images to WebAssembly (WASM) format. This will enable these containers to run on WASM with emulation support for x86_64 and riscv64 containers. The tool works with various WASI runtimes like wasmtime, wamr, wasmer, wasmedge, and wazero, and it can also run in the browser.\n\nConvert container image to WASM using container2wasm\nDeploy the WASM module in the desired environment\nRun the WASM module using a suitable WASI runtime\n\n\n\n\n\nEnables running of containerized services directly in the browser or lightweight client environments.\nEnhances avatar customization and AI-driven facial expressions in V-Sekai.\nLeverages the power of WASM for efficient, safe, and portable execution.\n\n\n\n\n\nRequires understanding and maintenance of WASM modules.\nPotential compatibility issues with certain containerized services.\n\n\n\n\nAn alternative would be to run the backend services on dedicated servers and communicate with them via APIs. However, this could introduce latency and require more resources.\n\n\n\nIn scenarios where the backend service is not frequently used, converting it to WASM might not provide significant benefits.\n\n\n\nThe integration of container2wasm will be done by the V-Sekai development team with support from the community stakeholders.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team and community stakeholders.\n\n\n\n\n\nV-Sekai, Avatar Customization, AI, Facial Expressions\n\n\n\n\n\nV-Sekai · GitHub\nV-Sekai/v-sekai-game\nContainer2Wasm · GitHub\n\nThis proposal was assisted by Aria, an AI assistant."
+    "text": "We aim to engage users in the V-Sekai world. A social RPG game could be the solution, offering continuous gameplay that encourages interaction."
   },
   {
-    "objectID": "decisions/20240217-container-2-wasm.html#context",
-    "href": "decisions/20240217-container-2-wasm.html#context",
-    "title": "Proposed: Container2Wasm Integration in V-Sekai",
+    "objectID": "decisions/20230803-idle-rpg-home.html#proposed-solution",
+    "href": "decisions/20230803-idle-rpg-home.html#proposed-solution",
+    "title": "Proposed: Social RPG World Proposal",
     "section": "",
-    "text": "V-Sekai is a project focused on social VR functionality for the Godot Engine. It aims to bring social VR/VRSNS/metaverse components to the Godot Engine, enhancing avatar customization and AI-driven facial expressions."
+    "text": "Our game is set in a “Comfortable Cyberprep” realm. It merges sci-fi with ease, where tech and humans coexist. Players explore a future city where technology is part of life. The city glows with neon lights, holographic interfaces, and advanced AI, yet retains homeliness.\n\nStatic couch collider: A fixed location for player interaction.\nNon-functional Static bed without collider: A rejuvenation spot for characters.\nNon-functional Mirror that is off: A decorative element with potential uses.\nNon-functional Video player screen that is off: A feature for entertainment or information.\n\n\n\n\n\nChill and hang with friends: The game provides a relaxed environment for socializing.\nPlay a game: Beyond socializing, players can engage in an RPG game.\n\n\n\n\n\nRPG game with level rewards: Players improve through play.\nCombat System: Players choose between different types of weapons or defensive items.\nStationary Target Combat System: A mechanism where players engage in combat with fixed-position targets.\n\n\n\n\n\nSettings are not persisted past server restart.\nLimited number of weapon choices: To maintain balance.\nCooldown period for using healing items: To prevent spamming."
   },
   {
-    "objectID": "decisions/20240217-container-2-wasm.html#problem-statement",
-    "href": "decisions/20240217-container-2-wasm.html#problem-statement",
-    "title": "Proposed: Container2Wasm Integration in V-Sekai",
+    "objectID": "decisions/20230803-idle-rpg-home.html#implementation",
+    "href": "decisions/20230803-idle-rpg-home.html#implementation",
+    "title": "Proposed: Social RPG World Proposal",
     "section": "",
-    "text": "Integrating complex backend services directly within a browser or lightweight client environments can be challenging. This integration is crucial for enhancing avatar customization and AI-driven facial expressions by leveraging containerized services."
+    "text": "Implementation details will be decided upon proposal acceptance."
   },
   {
-    "objectID": "decisions/20240217-container-2-wasm.html#proposed-solution",
-    "href": "decisions/20240217-container-2-wasm.html#proposed-solution",
-    "title": "Proposed: Container2Wasm Integration in V-Sekai",
+    "objectID": "decisions/20230803-idle-rpg-home.html#positive-consequences",
+    "href": "decisions/20230803-idle-rpg-home.html#positive-consequences",
+    "title": "Proposed: Social RPG World Proposal",
     "section": "",
-    "text": "We propose to use container2wasm, a tool that converts container images to WebAssembly (WASM) format. This will enable these containers to run on WASM with emulation support for x86_64 and riscv64 containers. The tool works with various WASI runtimes like wasmtime, wamr, wasmer, wasmedge, and wazero, and it can also run in the browser.\n\nConvert container image to WASM using container2wasm\nDeploy the WASM module in the desired environment\nRun the WASM module using a suitable WASI runtime"
+    "text": "Increased user engagement\nProlonged interaction within the V-Sekai world\nEnhanced socialization among players"
   },
   {
-    "objectID": "decisions/20240217-container-2-wasm.html#benefits",
-    "href": "decisions/20240217-container-2-wasm.html#benefits",
-    "title": "Proposed: Container2Wasm Integration in V-Sekai",
+    "objectID": "decisions/20230803-idle-rpg-home.html#negative-consequences",
+    "href": "decisions/20230803-idle-rpg-home.html#negative-consequences",
+    "title": "Proposed: Social RPG World Proposal",
     "section": "",
-    "text": "Enables running of containerized services directly in the browser or lightweight client environments.\nEnhances avatar customization and AI-driven facial expressions in V-Sekai.\nLeverages the power of WASM for efficient, safe, and portable execution."
+    "text": "Potential increase in development time and resources\nRisk of unbalanced gameplay if the RPG system is not properly designed"
   },
   {
-    "objectID": "decisions/20240217-container-2-wasm.html#downsides",
-    "href": "decisions/20240217-container-2-wasm.html#downsides",
-    "title": "Proposed: Container2Wasm Integration in V-Sekai",
+    "objectID": "decisions/20230803-idle-rpg-home.html#option-graveyard",
+    "href": "decisions/20230803-idle-rpg-home.html#option-graveyard",
+    "title": "Proposed: Social RPG World Proposal",
     "section": "",
-    "text": "Requires understanding and maintenance of WASM modules.\nPotential compatibility issues with certain containerized services."
+    "text": "Options considered but discarded:\n\nIdle RPG Mechanic: Removed due to potential decrease in active engagement from players."
   },
   {
-    "objectID": "decisions/20240217-container-2-wasm.html#the-road-not-taken",
-    "href": "decisions/20240217-container-2-wasm.html#the-road-not-taken",
-    "title": "Proposed: Container2Wasm Integration in V-Sekai",
+    "objectID": "decisions/20230803-idle-rpg-home.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230803-idle-rpg-home.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Social RPG World Proposal",
     "section": "",
-    "text": "An alternative would be to run the backend services on dedicated servers and communicate with them via APIs. However, this could introduce latency and require more resources."
+    "text": "The frequency of use depends on the players’ engagement level. However, given the complexity of an RPG system, it cannot be simply worked around with a few lines of script."
   },
   {
-    "objectID": "decisions/20240217-container-2-wasm.html#the-infrequent-use-case",
-    "href": "decisions/20240217-container-2-wasm.html#the-infrequent-use-case",
-    "title": "Proposed: Container2Wasm Integration in V-Sekai",
+    "objectID": "decisions/20230803-idle-rpg-home.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230803-idle-rpg-home.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Social RPG World Proposal",
     "section": "",
-    "text": "In scenarios where the backend service is not frequently used, converting it to WASM might not provide significant benefits."
+    "text": "Creating an RPG system as a feature of V-Sekai will enhance the overall user experience and engagement, which aligns with our goal of providing a compelling virtual world."
   },
   {
-    "objectID": "decisions/20240217-container-2-wasm.html#in-core-and-done-by-us",
-    "href": "decisions/20240217-container-2-wasm.html#in-core-and-done-by-us",
-    "title": "Proposed: Container2Wasm Integration in V-Sekai",
+    "objectID": "decisions/20230803-idle-rpg-home.html#references",
+    "href": "decisions/20230803-idle-rpg-home.html#references",
+    "title": "Proposed: Social RPG World Proposal",
     "section": "",
-    "text": "The integration of container2wasm will be done by the V-Sekai development team with support from the community stakeholders."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20240217-container-2-wasm.html#status",
-    "href": "decisions/20240217-container-2-wasm.html#status",
-    "title": "Proposed: Container2Wasm Integration in V-Sekai",
+    "objectID": "decisions/20240407-pcvr-vs-standalone.html",
+    "href": "decisions/20240407-pcvr-vs-standalone.html",
+    "title": "Accepted: Focusing on PCVR vs Android Build vs Web Build",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "V-Sekai is a project that aims to bring social VR functionality to the Godot Engine. The current dilemma is whether to focus on an Android/Web build, potentially moving away from PCVR as the primary platform, or continue focusing on PCVR.\n\n\n\nThe team lacks a high-powered enterprise sales team for enterprise PCVR. The mobile Vulkan is considered due to its ability to use compute shaders to skeleton skin meshes for large avatar counts. However, Meta dominates the standalone VR software market, and matching their offerings requires a superior product.\nMeta dominates the standalone VR software market but they are limited by the laws of physics.\n\n\n\nGiven the current market situation and V-Sekai’s capabilities, it is suggested to focus on PCVR. This platform can offer high-quality AAA games with lots of content, which standalone games cannot currently provide.\n\n\n\n\nAbility to offer high-quality AAA games with lots of content.\nLess crowded market compared to the standalone VR software market.\nWe can make more experiences.\nWe can make better experiences.\nThe PCVR hardware is more capable (vulkan, shader functions, less need to optimize), so the same experiences are easier to create.\nPCVR is easier to develop and test.\nPCVR is more open to collaboration.\n\n\n\n\n\nRequires a significant investment in PCVR development.\nThe market for PCVR is growing but lacks spotlight.\n\n\n\n\nFocusing on an Android build would mean entering a highly competitive market dominated by established players like Meta. It would also require aggressively pursuing game developers for exclusive content, which could be a challenging strategy.\n\n\n\nIf Meta decides to shift focus towards the consumer AR market, leaving the gaming market, there could be an opportunity for V-Sekai to fill the gap.\n\n\n\nThe decision to focus on PCVR will be a core strategy for V-Sekai, implemented by the development team.\n\n\n\nAccepted\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\nPCVR\nVR Development\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis article was assisted by AI assistant Aria."
   },
   {
-    "objectID": "decisions/20240217-container-2-wasm.html#decision-makers",
-    "href": "decisions/20240217-container-2-wasm.html#decision-makers",
-    "title": "Proposed: Container2Wasm Integration in V-Sekai",
+    "objectID": "decisions/20240407-pcvr-vs-standalone.html#context",
+    "href": "decisions/20240407-pcvr-vs-standalone.html#context",
+    "title": "Accepted: Focusing on PCVR vs Android Build vs Web Build",
     "section": "",
-    "text": "V-Sekai development team and community stakeholders."
+    "text": "V-Sekai is a project that aims to bring social VR functionality to the Godot Engine. The current dilemma is whether to focus on an Android/Web build, potentially moving away from PCVR as the primary platform, or continue focusing on PCVR."
   },
   {
-    "objectID": "decisions/20240217-container-2-wasm.html#tags",
-    "href": "decisions/20240217-container-2-wasm.html#tags",
-    "title": "Proposed: Container2Wasm Integration in V-Sekai",
+    "objectID": "decisions/20240407-pcvr-vs-standalone.html#problem-statement",
+    "href": "decisions/20240407-pcvr-vs-standalone.html#problem-statement",
+    "title": "Accepted: Focusing on PCVR vs Android Build vs Web Build",
     "section": "",
-    "text": "V-Sekai, Avatar Customization, AI, Facial Expressions"
+    "text": "The team lacks a high-powered enterprise sales team for enterprise PCVR. The mobile Vulkan is considered due to its ability to use compute shaders to skeleton skin meshes for large avatar counts. However, Meta dominates the standalone VR software market, and matching their offerings requires a superior product.\nMeta dominates the standalone VR software market but they are limited by the laws of physics."
   },
   {
-    "objectID": "decisions/20240217-container-2-wasm.html#further-reading",
-    "href": "decisions/20240217-container-2-wasm.html#further-reading",
-    "title": "Proposed: Container2Wasm Integration in V-Sekai",
+    "objectID": "decisions/20240407-pcvr-vs-standalone.html#proposal",
+    "href": "decisions/20240407-pcvr-vs-standalone.html#proposal",
+    "title": "Accepted: Focusing on PCVR vs Android Build vs Web Build",
     "section": "",
-    "text": "V-Sekai · GitHub\nV-Sekai/v-sekai-game\nContainer2Wasm · GitHub\n\nThis proposal was assisted by Aria, an AI assistant."
+    "text": "Given the current market situation and V-Sekai’s capabilities, it is suggested to focus on PCVR. This platform can offer high-quality AAA games with lots of content, which standalone games cannot currently provide."
   },
   {
-    "objectID": "decisions/20230824-subdiv-for-lods.html",
-    "href": "decisions/20230824-subdiv-for-lods.html",
-    "title": "Accepted: Use opensubdiv for level of detail",
+    "objectID": "decisions/20240407-pcvr-vs-standalone.html#benefits",
+    "href": "decisions/20240407-pcvr-vs-standalone.html#benefits",
+    "title": "Accepted: Focusing on PCVR vs Android Build vs Web Build",
     "section": "",
-    "text": "Status: accepted \nDeciders: V-Sekai, fire\nTags: V-Sekai\n\n\n\n\nCreators want more. Players want more. The platform can only support a limited amount of content.\n\n\n\nThe challenge lies in optimizing the content to fit within the platform’s limitations without compromising on the quality and detail.\n\n\n\nUse OpenSubdiv to increase detail, which can then be reduced through Godot Engine’s LOD (Level of Detail) scheme. This allows for high-quality models that are optimized for performance.\n\n\n\nThe upside is that this approach allows for more detailed models while still maintaining good performance.\n\n\n\nThe downside is that it requires additional processing to create the LOD models, which could potentially slow down the development process.\n\n\n\nAn alternative approach would have been to manually create lower detail models for use in less demanding scenarios. However, this would require significantly more work from the creators.\n\n\n\nThis strategy might not be beneficial for very simple models or scenes where the level of detail is not a significant factor.\n\n\n\nYes, this strategy is implemented in the core of our platform and maintained by us.\n\n\n\n\nV-Sekai\nThis article is assisted by AI."
+    "text": "Ability to offer high-quality AAA games with lots of content.\nLess crowded market compared to the standalone VR software market.\nWe can make more experiences.\nWe can make better experiences.\nThe PCVR hardware is more capable (vulkan, shader functions, less need to optimize), so the same experiences are easier to create.\nPCVR is easier to develop and test.\nPCVR is more open to collaboration."
   },
   {
-    "objectID": "decisions/20230824-subdiv-for-lods.html#metadata",
-    "href": "decisions/20230824-subdiv-for-lods.html#metadata",
-    "title": "Accepted: Use opensubdiv for level of detail",
+    "objectID": "decisions/20240407-pcvr-vs-standalone.html#downsides",
+    "href": "decisions/20240407-pcvr-vs-standalone.html#downsides",
+    "title": "Accepted: Focusing on PCVR vs Android Build vs Web Build",
     "section": "",
-    "text": "Status: accepted \nDeciders: V-Sekai, fire\nTags: V-Sekai"
+    "text": "Requires a significant investment in PCVR development.\nThe market for PCVR is growing but lacks spotlight."
   },
   {
-    "objectID": "decisions/20230824-subdiv-for-lods.html#the-backdrop",
-    "href": "decisions/20230824-subdiv-for-lods.html#the-backdrop",
-    "title": "Accepted: Use opensubdiv for level of detail",
+    "objectID": "decisions/20240407-pcvr-vs-standalone.html#the-road-not-taken",
+    "href": "decisions/20240407-pcvr-vs-standalone.html#the-road-not-taken",
+    "title": "Accepted: Focusing on PCVR vs Android Build vs Web Build",
     "section": "",
-    "text": "Creators want more. Players want more. The platform can only support a limited amount of content."
+    "text": "Focusing on an Android build would mean entering a highly competitive market dominated by established players like Meta. It would also require aggressively pursuing game developers for exclusive content, which could be a challenging strategy."
   },
   {
-    "objectID": "decisions/20230824-subdiv-for-lods.html#the-challenge",
-    "href": "decisions/20230824-subdiv-for-lods.html#the-challenge",
-    "title": "Accepted: Use opensubdiv for level of detail",
+    "objectID": "decisions/20240407-pcvr-vs-standalone.html#infrequent-use-case",
+    "href": "decisions/20240407-pcvr-vs-standalone.html#infrequent-use-case",
+    "title": "Accepted: Focusing on PCVR vs Android Build vs Web Build",
     "section": "",
-    "text": "The challenge lies in optimizing the content to fit within the platform’s limitations without compromising on the quality and detail."
+    "text": "If Meta decides to shift focus towards the consumer AR market, leaving the gaming market, there could be an opportunity for V-Sekai to fill the gap."
   },
   {
-    "objectID": "decisions/20230824-subdiv-for-lods.html#the-strategy",
-    "href": "decisions/20230824-subdiv-for-lods.html#the-strategy",
-    "title": "Accepted: Use opensubdiv for level of detail",
+    "objectID": "decisions/20240407-pcvr-vs-standalone.html#in-core-and-done-by-us",
+    "href": "decisions/20240407-pcvr-vs-standalone.html#in-core-and-done-by-us",
+    "title": "Accepted: Focusing on PCVR vs Android Build vs Web Build",
     "section": "",
-    "text": "Use OpenSubdiv to increase detail, which can then be reduced through Godot Engine’s LOD (Level of Detail) scheme. This allows for high-quality models that are optimized for performance."
+    "text": "The decision to focus on PCVR will be a core strategy for V-Sekai, implemented by the development team."
   },
   {
-    "objectID": "decisions/20230824-subdiv-for-lods.html#the-upside",
-    "href": "decisions/20230824-subdiv-for-lods.html#the-upside",
-    "title": "Accepted: Use opensubdiv for level of detail",
+    "objectID": "decisions/20240407-pcvr-vs-standalone.html#status",
+    "href": "decisions/20240407-pcvr-vs-standalone.html#status",
+    "title": "Accepted: Focusing on PCVR vs Android Build vs Web Build",
     "section": "",
-    "text": "The upside is that this approach allows for more detailed models while still maintaining good performance."
+    "text": "Accepted"
   },
   {
-    "objectID": "decisions/20230824-subdiv-for-lods.html#the-downside",
-    "href": "decisions/20230824-subdiv-for-lods.html#the-downside",
-    "title": "Accepted: Use opensubdiv for level of detail",
+    "objectID": "decisions/20240407-pcvr-vs-standalone.html#decision-makers",
+    "href": "decisions/20240407-pcvr-vs-standalone.html#decision-makers",
+    "title": "Accepted: Focusing on PCVR vs Android Build vs Web Build",
     "section": "",
-    "text": "The downside is that it requires additional processing to create the LOD models, which could potentially slow down the development process."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20230824-subdiv-for-lods.html#the-road-not-taken",
-    "href": "decisions/20230824-subdiv-for-lods.html#the-road-not-taken",
-    "title": "Accepted: Use opensubdiv for level of detail",
+    "objectID": "decisions/20240407-pcvr-vs-standalone.html#tags",
+    "href": "decisions/20240407-pcvr-vs-standalone.html#tags",
+    "title": "Accepted: Focusing on PCVR vs Android Build vs Web Build",
     "section": "",
-    "text": "An alternative approach would have been to manually create lower detail models for use in less demanding scenarios. However, this would require significantly more work from the creators."
+    "text": "V-Sekai\nPCVR\nVR Development"
   },
   {
-    "objectID": "decisions/20230824-subdiv-for-lods.html#the-infrequent-use-case",
-    "href": "decisions/20230824-subdiv-for-lods.html#the-infrequent-use-case",
-    "title": "Accepted: Use opensubdiv for level of detail",
+    "objectID": "decisions/20240407-pcvr-vs-standalone.html#further-reading",
+    "href": "decisions/20240407-pcvr-vs-standalone.html#further-reading",
+    "title": "Accepted: Focusing on PCVR vs Android Build vs Web Build",
     "section": "",
-    "text": "This strategy might not be beneficial for very simple models or scenes where the level of detail is not a significant factor."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis article was assisted by AI assistant Aria."
   },
   {
-    "objectID": "decisions/20230824-subdiv-for-lods.html#in-core-and-done-by-us",
-    "href": "decisions/20230824-subdiv-for-lods.html#in-core-and-done-by-us",
-    "title": "Accepted: Use opensubdiv for level of detail",
+    "objectID": "decisions/20230831-fixing-menus.html",
+    "href": "decisions/20230831-fixing-menus.html",
+    "title": "Accepted: Fix menus in-game",
     "section": "",
-    "text": "Yes, this strategy is implemented in the core of our platform and maintained by us."
+    "text": "Status: accepted\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\n\n\n\nThe menus in-game are unable to capture events from the VR controllers.\n\n\n\nDebug the on_pointer_pressed function as it is not working correctly due to an issue with Transform3D.xform_inv. The current implementation mimics mouse input, but it fails to translate global positions correctly. Review the global_to_viewport function and ensure it returns the correct value for local_at.\n\n\n\nFixing the menus will enable players to interact with them using VR controllers, enhancing the user experience.\n\n\n\nFixing the menus may require significant code changes, introducing potential bugs or conflicts that need proper testing to ensure stability.\n\n\n\nExploring alternative input systems specifically designed for VR controllers could be considered, but it may involve rewriting a large portion of the menu code and potentially introducing new dependencies.\n\n\n\nThis fix targets players using VR controllers to interact with the menus. Players without VR controllers will not be affected.\n\n\n\nYes, this issue falls within our core development responsibilities, and we will take ownership of fixing the menus.\n\n\n\n\nV-Sekai\nThis article is assisted by AI."
   },
   {
-    "objectID": "decisions/20230824-subdiv-for-lods.html#further-reading",
-    "href": "decisions/20230824-subdiv-for-lods.html#further-reading",
-    "title": "Accepted: Use opensubdiv for level of detail",
+    "objectID": "decisions/20230831-fixing-menus.html#metadata",
+    "href": "decisions/20230831-fixing-menus.html#metadata",
+    "title": "Accepted: Fix menus in-game",
     "section": "",
-    "text": "V-Sekai\nThis article is assisted by AI."
+    "text": "Status: accepted\nDeciders: V-Sekai\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20231227-blue-green-shadows.html",
-    "href": "decisions/20231227-blue-green-shadows.html",
-    "title": "Proposed: Blue Green new shadows for new avatars",
+    "objectID": "decisions/20230831-fixing-menus.html#the-challenge",
+    "href": "decisions/20230831-fixing-menus.html#the-challenge",
+    "title": "Accepted: Fix menus in-game",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nThe default avatar format in V-Sekai, vrm0, has a shadow color that is too pink (F7CFDB). This has been a point of contention among users and developers alike.\n\n\n\nThe challenge lies in changing the default shadow color for new models to something more universally appealing. Two colors have been suggested as alternatives:\n\n\n\nColor Description\nASCII Hex Code\n\n\n\n\nSage Green\n#8F9779\n\n\nSoft Sky Blue\n#B4C8E5\n\n\n\n\n\n\nThe strategy would involve modifying the default settings in the vrm0 avatar format for new models to use one of the proposed colors instead of the current pink shade.\n\n\n\nChanging the default shadow color for new models could lead to a more visually pleasing user experience. It could also potentially increase user satisfaction and engagement.\n\n\n\nSome users may prefer the current pink shadow color. Changing it for new models could lead to dissatisfaction among this group of users.\n\n\n\nAn alternative approach could be to allow users to customize the shadow color themselves. However, this could potentially complicate the user interface and make the platform more difficult to use for beginners.\n\n\n\nIn some cases, the pink shadow color might actually be preferred. For example, in certain lighting conditions or for certain types of avatars, the pink color might look better than the proposed alternatives.\n\n\n\nThis change would need to be implemented by the V-Sekai development team. It would likely require modifications to the core code of the platform.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nThis article was assisted by Aria, your AI assistant."
+    "text": "The menus in-game are unable to capture events from the VR controllers."
   },
   {
-    "objectID": "decisions/20231227-blue-green-shadows.html#metadata",
-    "href": "decisions/20231227-blue-green-shadows.html#metadata",
-    "title": "Proposed: Blue Green new shadows for new avatars",
+    "objectID": "decisions/20230831-fixing-menus.html#the-strategy",
+    "href": "decisions/20230831-fixing-menus.html#the-strategy",
+    "title": "Accepted: Fix menus in-game",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai"
+    "text": "Debug the on_pointer_pressed function as it is not working correctly due to an issue with Transform3D.xform_inv. The current implementation mimics mouse input, but it fails to translate global positions correctly. Review the global_to_viewport function and ensure it returns the correct value for local_at."
   },
   {
-    "objectID": "decisions/20231227-blue-green-shadows.html#the-backdrop",
-    "href": "decisions/20231227-blue-green-shadows.html#the-backdrop",
-    "title": "Proposed: Blue Green new shadows for new avatars",
+    "objectID": "decisions/20230831-fixing-menus.html#the-upside",
+    "href": "decisions/20230831-fixing-menus.html#the-upside",
+    "title": "Accepted: Fix menus in-game",
     "section": "",
-    "text": "The default avatar format in V-Sekai, vrm0, has a shadow color that is too pink (F7CFDB). This has been a point of contention among users and developers alike."
+    "text": "Fixing the menus will enable players to interact with them using VR controllers, enhancing the user experience."
   },
   {
-    "objectID": "decisions/20231227-blue-green-shadows.html#the-challenge",
-    "href": "decisions/20231227-blue-green-shadows.html#the-challenge",
-    "title": "Proposed: Blue Green new shadows for new avatars",
+    "objectID": "decisions/20230831-fixing-menus.html#the-downside",
+    "href": "decisions/20230831-fixing-menus.html#the-downside",
+    "title": "Accepted: Fix menus in-game",
     "section": "",
-    "text": "The challenge lies in changing the default shadow color for new models to something more universally appealing. Two colors have been suggested as alternatives:\n\n\n\nColor Description\nASCII Hex Code\n\n\n\n\nSage Green\n#8F9779\n\n\nSoft Sky Blue\n#B4C8E5"
+    "text": "Fixing the menus may require significant code changes, introducing potential bugs or conflicts that need proper testing to ensure stability."
   },
   {
-    "objectID": "decisions/20231227-blue-green-shadows.html#the-strategy",
-    "href": "decisions/20231227-blue-green-shadows.html#the-strategy",
-    "title": "Proposed: Blue Green new shadows for new avatars",
+    "objectID": "decisions/20230831-fixing-menus.html#the-road-not-taken",
+    "href": "decisions/20230831-fixing-menus.html#the-road-not-taken",
+    "title": "Accepted: Fix menus in-game",
     "section": "",
-    "text": "The strategy would involve modifying the default settings in the vrm0 avatar format for new models to use one of the proposed colors instead of the current pink shade."
+    "text": "Exploring alternative input systems specifically designed for VR controllers could be considered, but it may involve rewriting a large portion of the menu code and potentially introducing new dependencies."
   },
   {
-    "objectID": "decisions/20231227-blue-green-shadows.html#the-upside",
-    "href": "decisions/20231227-blue-green-shadows.html#the-upside",
-    "title": "Proposed: Blue Green new shadows for new avatars",
+    "objectID": "decisions/20230831-fixing-menus.html#the-infrequent-use-case",
+    "href": "decisions/20230831-fixing-menus.html#the-infrequent-use-case",
+    "title": "Accepted: Fix menus in-game",
     "section": "",
-    "text": "Changing the default shadow color for new models could lead to a more visually pleasing user experience. It could also potentially increase user satisfaction and engagement."
+    "text": "This fix targets players using VR controllers to interact with the menus. Players without VR controllers will not be affected."
   },
   {
-    "objectID": "decisions/20231227-blue-green-shadows.html#the-downside",
-    "href": "decisions/20231227-blue-green-shadows.html#the-downside",
-    "title": "Proposed: Blue Green new shadows for new avatars",
+    "objectID": "decisions/20230831-fixing-menus.html#in-core-and-done-by-us",
+    "href": "decisions/20230831-fixing-menus.html#in-core-and-done-by-us",
+    "title": "Accepted: Fix menus in-game",
     "section": "",
-    "text": "Some users may prefer the current pink shadow color. Changing it for new models could lead to dissatisfaction among this group of users."
+    "text": "Yes, this issue falls within our core development responsibilities, and we will take ownership of fixing the menus."
   },
   {
-    "objectID": "decisions/20231227-blue-green-shadows.html#the-road-not-taken",
-    "href": "decisions/20231227-blue-green-shadows.html#the-road-not-taken",
-    "title": "Proposed: Blue Green new shadows for new avatars",
+    "objectID": "decisions/20230831-fixing-menus.html#further-reading",
+    "href": "decisions/20230831-fixing-menus.html#further-reading",
+    "title": "Accepted: Fix menus in-game",
     "section": "",
-    "text": "An alternative approach could be to allow users to customize the shadow color themselves. However, this could potentially complicate the user interface and make the platform more difficult to use for beginners."
+    "text": "V-Sekai\nThis article is assisted by AI."
   },
   {
-    "objectID": "decisions/20231227-blue-green-shadows.html#the-infrequent-use-case",
-    "href": "decisions/20231227-blue-green-shadows.html#the-infrequent-use-case",
-    "title": "Proposed: Blue Green new shadows for new avatars",
+    "objectID": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html",
+    "href": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html",
+    "title": "Draft: Preview #materialx materials on the Web in Godot Engine",
     "section": "",
-    "text": "In some cases, the pink shadow color might actually be preferred. For example, in certain lighting conditions or for certain types of avatars, the pink color might look better than the proposed alternatives."
+    "text": "Status: draft \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nThere is no process for previewing #materialx on the web.\n\n\n\nPropose using Godot Engine 4.0 as a WebGL2 previewer for MaterialX.\n\n\n\n\nCompile Godot Engine 4.0 for WebGL2\nMake a 2D app\nExport to the Itch.io web store.\n\n\n\n\n\nCan use the same code base as the rest\n\n\n\n\n\nGodot monopolizing yet another platform.\n\n\n\n\n\nOption: \nRejection Reason: \n\n\n\n\nThis requires devops.\n\n\n\nCan be outside of core.\n\n\n\n\nhttps://github.com/godotengine/godot\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20231227-blue-green-shadows.html#in-core-and-done-by-us",
-    "href": "decisions/20231227-blue-green-shadows.html#in-core-and-done-by-us",
-    "title": "Proposed: Blue Green new shadows for new avatars",
+    "objectID": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html#context-and-problem-statement",
+    "href": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html#context-and-problem-statement",
+    "title": "Draft: Preview #materialx materials on the Web in Godot Engine",
     "section": "",
-    "text": "This change would need to be implemented by the V-Sekai development team. It would likely require modifications to the core code of the platform."
+    "text": "There is no process for previewing #materialx on the web."
   },
   {
-    "objectID": "decisions/20231227-blue-green-shadows.html#further-reading",
-    "href": "decisions/20231227-blue-green-shadows.html#further-reading",
-    "title": "Proposed: Blue Green new shadows for new avatars",
+    "objectID": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Draft: Preview #materialx materials on the Web in Godot Engine",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nThis article was assisted by Aria, your AI assistant."
+    "text": "Propose using Godot Engine 4.0 as a WebGL2 previewer for MaterialX."
   },
   {
-    "objectID": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html",
-    "href": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html",
-    "title": "Draft: Create a VRM character by experimenting with written workflows.",
+    "objectID": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Draft: Preview #materialx materials on the Web in Godot Engine",
     "section": "",
-    "text": "Status: draft \nDeciders: V-Sekai,fire,\nTags: V-Sekai,\n\n\n\nWant to experiment with character creation workflows.\n\n\n\nWant to document VRM character creation workflows.\n\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\n\n\n\n\nChecks can be automated for use in a workshop.\n\n\n\n\n\n[e.g., compromising quality attribute, follow-up decisions required, …]\n\n[this section can be repeated for each option if more than one option is open for consideration]\n\n\n\n\nOption: \nRejection Reason: \n\n\n\n\nThis is educational material and not code.\n\n\n\nI know how to do this.\n\n\n\n\nhttps://github.com/vrm-c\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Compile Godot Engine 4.0 for WebGL2\nMake a 2D app\nExport to the Itch.io web store."
   },
   {
-    "objectID": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html#context-and-problem-statement",
-    "href": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html#context-and-problem-statement",
-    "title": "Draft: Create a VRM character by experimenting with written workflows.",
+    "objectID": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html#positive-consequences",
+    "href": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html#positive-consequences",
+    "title": "Draft: Preview #materialx materials on the Web in Godot Engine",
     "section": "",
-    "text": "Want to experiment with character creation workflows."
+    "text": "Can use the same code base as the rest"
   },
   {
-    "objectID": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Draft: Create a VRM character by experimenting with written workflows.",
+    "objectID": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html#negative-consequences",
+    "href": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html#negative-consequences",
+    "title": "Draft: Preview #materialx materials on the Web in Godot Engine",
     "section": "",
-    "text": "Want to document VRM character creation workflows."
+    "text": "Godot monopolizing yet another platform."
   },
   {
-    "objectID": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Draft: Create a VRM character by experimenting with written workflows.",
+    "objectID": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html#option-graveyard",
+    "href": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html#option-graveyard",
+    "title": "Draft: Preview #materialx materials on the Web in Godot Engine",
     "section": "",
-    "text": "Describe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams"
+    "text": "Option: \nRejection Reason:"
   },
   {
-    "objectID": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html#positive-consequences",
-    "href": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html#positive-consequences",
-    "title": "Draft: Create a VRM character by experimenting with written workflows.",
+    "objectID": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Draft: Preview #materialx materials on the Web in Godot Engine",
     "section": "",
-    "text": "Checks can be automated for use in a workshop."
+    "text": "This requires devops."
   },
   {
-    "objectID": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html#negative-consequences",
-    "href": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html#negative-consequences",
-    "title": "Draft: Create a VRM character by experimenting with written workflows.",
+    "objectID": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Draft: Preview #materialx materials on the Web in Godot Engine",
     "section": "",
-    "text": "[e.g., compromising quality attribute, follow-up decisions required, …]\n\n[this section can be repeated for each option if more than one option is open for consideration]"
+    "text": "Can be outside of core."
   },
   {
-    "objectID": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html#option-graveyard",
-    "href": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html#option-graveyard",
-    "title": "Draft: Create a VRM character by experimenting with written workflows.",
+    "objectID": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html#references",
+    "href": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html#references",
+    "title": "Draft: Preview #materialx materials on the Web in Godot Engine",
     "section": "",
-    "text": "Option: \nRejection Reason:"
+    "text": "https://github.com/godotengine/godot"
   },
   {
-    "objectID": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Draft: Create a VRM character by experimenting with written workflows.",
+    "objectID": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html#derivative-license",
+    "href": "decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html#derivative-license",
+    "title": "Draft: Preview #materialx materials on the Web in Godot Engine",
     "section": "",
-    "text": "This is educational material and not code."
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Draft: Create a VRM character by experimenting with written workflows.",
+    "objectID": "decisions/20240411-elixir-libgodot-zig.html",
+    "href": "decisions/20240411-elixir-libgodot-zig.html",
+    "title": "Rejected: Binding GDExtension to a C-like Language for Libgodot to Implement a Distributed Simulation",
     "section": "",
-    "text": "I know how to do this."
+    "text": "The V-Sekai development team is working on enhancing the simulation experience in our VR game. We aim to create a more immersive and interactive environment for our players.\n\n\n\nWe can bind GDExtension to a C-like language for libgodot to implement a distributed simulation.\n\n\n\nWe propose to use godot-zig to bind GDExtension to Elixir. This will allow us to leverage the power of Elixir’s concurrency and fault-tolerance features, which are ideal for creating distributed simulations.\n\n\n\n\nEnhanced simulation performance due to Elixir’s efficient handling of concurrent processes.\nImproved fault tolerance, as Elixir’s supervisor trees can automatically recover from errors.\nIncreased developer productivity, as Elixir’s syntax is concise and expressive.\n\n\n\n\n\nRequires learning a new programming language (Elixir), which may increase the development time initially.\nPotential compatibility issues between Elixir and existing parts of the system.\n\n\n\n\nWe considered using other languages like Rust or Go, but they did not offer the same level of concurrency and fault-tolerance features as Elixir.\n\n\n\nThis proposal may not be suitable for smaller projects that do not require complex distributed simulations.\n\n\n\nThe V-Sekai development team will implement this proposal.\n\n\n\nStatus: Rejected \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\ngodot-zig\nzigler\n\nAssisted by Aria."
   },
   {
-    "objectID": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html#references",
-    "href": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html#references",
-    "title": "Draft: Create a VRM character by experimenting with written workflows.",
+    "objectID": "decisions/20240411-elixir-libgodot-zig.html#the-context",
+    "href": "decisions/20240411-elixir-libgodot-zig.html#the-context",
+    "title": "Rejected: Binding GDExtension to a C-like Language for Libgodot to Implement a Distributed Simulation",
     "section": "",
-    "text": "https://github.com/vrm-c"
+    "text": "The V-Sekai development team is working on enhancing the simulation experience in our VR game. We aim to create a more immersive and interactive environment for our players."
   },
   {
-    "objectID": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html#derivative-license",
-    "href": "decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html#derivative-license",
-    "title": "Draft: Create a VRM character by experimenting with written workflows.",
+    "objectID": "decisions/20240411-elixir-libgodot-zig.html#the-problem-statement",
+    "href": "decisions/20240411-elixir-libgodot-zig.html#the-problem-statement",
+    "title": "Rejected: Binding GDExtension to a C-like Language for Libgodot to Implement a Distributed Simulation",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "We can bind GDExtension to a C-like language for libgodot to implement a distributed simulation."
   },
   {
-    "objectID": "decisions/20210811-omi-glb.html",
-    "href": "decisions/20210811-omi-glb.html",
-    "title": "Proposed: OMI Glb Portable Content",
+    "objectID": "decisions/20240411-elixir-libgodot-zig.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240411-elixir-libgodot-zig.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Rejected: Binding GDExtension to a C-like Language for Libgodot to Implement a Distributed Simulation",
     "section": "",
-    "text": "Proposed: OMI Glb Portable Content\n\nContext and Problem Statement\nWe desire portable content.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nCreate an art workflow.\n[Blender] -&gt; [OMI.glb]\n[OMI.glb] -&gt; [Godot Engine Packed Scene]\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nCreate an OMI Blender addon under W3C license.\nCreate glTF2 extension pull request for Godot Engine.\nFlow:\n\nOMI importer to Blender\nExporter of extended blender with OMI extensions to extended gltf\nSupport for OMI extended gltf in godot with definition of in-memory format for OMI extensions in Godot Engine for bidirectionality.\n\nExpected output:\n\nExport/Import as OMI format in Blender\nSupport OMI GLB in Godot\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nInterlapping projects are complicated.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nCan collaborate with Mozilla hubs team and OMI.\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "We propose to use godot-zig to bind GDExtension to Elixir. This will allow us to leverage the power of Elixir’s concurrency and fault-tolerance features, which are ideal for creating distributed simulations."
   },
   {
-    "objectID": "decisions/20231229-mRemoteNG.html",
-    "href": "decisions/20231229-mRemoteNG.html",
-    "title": "Proposed: Choosing a terminal emulator for Windows",
+    "objectID": "decisions/20240411-elixir-libgodot-zig.html#the-benefits",
+    "href": "decisions/20240411-elixir-libgodot-zig.html#the-benefits",
+    "title": "Rejected: Binding GDExtension to a C-like Language for Libgodot to Implement a Distributed Simulation",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nA need for efficient and effective remote access to multiple devices. As the world becomes more interconnected, the ability to manage and control various devices remotely has become crucial.\n\n\n\nSoftware that can log into multiple devices, providing users with the ability to perform tasks on those devices without physical access.\n\n\n\nAccording to AlternativeTo, mRemoteNG is a popular open-source alternative to MobaXterm. It’s a fork of mRemote, an open source, tabbed, multi-protocol, remote connections manager.\nKey points:\n\nmRemoteNG is the most popular Windows alternative to MobaXterm.\nmRemoteNG is the most popular Open Source & free alternative to MobaXterm.\n\n\n\n\nThe upside of using mRemoteNG is its versatility and cost-effectiveness. Being an open-source tool, it allows for customization and improvements from the user community. It also supports multiple protocols for managing remote connections.\n\n\n\nThe downside could be the potential learning curve associated with using a new tool. Additionally, as it is open-source, support might not be as readily available or comprehensive as with commercial software.\n\n\n\nThe road not taken would be sticking with traditional, possibly proprietary, terminal emulators. While these may offer robust features and dedicated support, they often come at a significant cost and lack the flexibility of open-source solutions.\n\n\n\nAn infrequent use case might be using mRemoteNG for managing a small number of devices or connections. In such cases, the full potential of the tool may not be utilized.\n\n\n\nThis strategy is not in core and done by us. It involves leveraging an existing open-source solution to address our needs.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
+    "text": "Enhanced simulation performance due to Elixir’s efficient handling of concurrent processes.\nImproved fault tolerance, as Elixir’s supervisor trees can automatically recover from errors.\nIncreased developer productivity, as Elixir’s syntax is concise and expressive."
   },
   {
-    "objectID": "decisions/20231229-mRemoteNG.html#metadata",
-    "href": "decisions/20231229-mRemoteNG.html#metadata",
-    "title": "Proposed: Choosing a terminal emulator for Windows",
+    "objectID": "decisions/20240411-elixir-libgodot-zig.html#the-downsides",
+    "href": "decisions/20240411-elixir-libgodot-zig.html#the-downsides",
+    "title": "Rejected: Binding GDExtension to a C-like Language for Libgodot to Implement a Distributed Simulation",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai"
+    "text": "Requires learning a new programming language (Elixir), which may increase the development time initially.\nPotential compatibility issues between Elixir and existing parts of the system."
   },
   {
-    "objectID": "decisions/20231229-mRemoteNG.html#the-backdrop",
-    "href": "decisions/20231229-mRemoteNG.html#the-backdrop",
-    "title": "Proposed: Choosing a terminal emulator for Windows",
+    "objectID": "decisions/20240411-elixir-libgodot-zig.html#the-road-not-taken",
+    "href": "decisions/20240411-elixir-libgodot-zig.html#the-road-not-taken",
+    "title": "Rejected: Binding GDExtension to a C-like Language for Libgodot to Implement a Distributed Simulation",
     "section": "",
-    "text": "A need for efficient and effective remote access to multiple devices. As the world becomes more interconnected, the ability to manage and control various devices remotely has become crucial."
+    "text": "We considered using other languages like Rust or Go, but they did not offer the same level of concurrency and fault-tolerance features as Elixir."
   },
   {
-    "objectID": "decisions/20231229-mRemoteNG.html#the-challenge",
-    "href": "decisions/20231229-mRemoteNG.html#the-challenge",
-    "title": "Proposed: Choosing a terminal emulator for Windows",
+    "objectID": "decisions/20240411-elixir-libgodot-zig.html#the-infrequent-use-case",
+    "href": "decisions/20240411-elixir-libgodot-zig.html#the-infrequent-use-case",
+    "title": "Rejected: Binding GDExtension to a C-like Language for Libgodot to Implement a Distributed Simulation",
     "section": "",
-    "text": "Software that can log into multiple devices, providing users with the ability to perform tasks on those devices without physical access."
+    "text": "This proposal may not be suitable for smaller projects that do not require complex distributed simulations."
   },
   {
-    "objectID": "decisions/20231229-mRemoteNG.html#the-strategy",
-    "href": "decisions/20231229-mRemoteNG.html#the-strategy",
-    "title": "Proposed: Choosing a terminal emulator for Windows",
+    "objectID": "decisions/20240411-elixir-libgodot-zig.html#in-core-and-done-by-us",
+    "href": "decisions/20240411-elixir-libgodot-zig.html#in-core-and-done-by-us",
+    "title": "Rejected: Binding GDExtension to a C-like Language for Libgodot to Implement a Distributed Simulation",
     "section": "",
-    "text": "According to AlternativeTo, mRemoteNG is a popular open-source alternative to MobaXterm. It’s a fork of mRemote, an open source, tabbed, multi-protocol, remote connections manager.\nKey points:\n\nmRemoteNG is the most popular Windows alternative to MobaXterm.\nmRemoteNG is the most popular Open Source & free alternative to MobaXterm."
+    "text": "The V-Sekai development team will implement this proposal."
   },
   {
-    "objectID": "decisions/20231229-mRemoteNG.html#the-upside",
-    "href": "decisions/20231229-mRemoteNG.html#the-upside",
-    "title": "Proposed: Choosing a terminal emulator for Windows",
+    "objectID": "decisions/20240411-elixir-libgodot-zig.html#status",
+    "href": "decisions/20240411-elixir-libgodot-zig.html#status",
+    "title": "Rejected: Binding GDExtension to a C-like Language for Libgodot to Implement a Distributed Simulation",
     "section": "",
-    "text": "The upside of using mRemoteNG is its versatility and cost-effectiveness. Being an open-source tool, it allows for customization and improvements from the user community. It also supports multiple protocols for managing remote connections."
+    "text": "Status: Rejected"
   },
   {
-    "objectID": "decisions/20231229-mRemoteNG.html#the-downside",
-    "href": "decisions/20231229-mRemoteNG.html#the-downside",
-    "title": "Proposed: Choosing a terminal emulator for Windows",
+    "objectID": "decisions/20240411-elixir-libgodot-zig.html#decision-makers",
+    "href": "decisions/20240411-elixir-libgodot-zig.html#decision-makers",
+    "title": "Rejected: Binding GDExtension to a C-like Language for Libgodot to Implement a Distributed Simulation",
     "section": "",
-    "text": "The downside could be the potential learning curve associated with using a new tool. Additionally, as it is open-source, support might not be as readily available or comprehensive as with commercial software."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20231229-mRemoteNG.html#the-road-not-taken",
-    "href": "decisions/20231229-mRemoteNG.html#the-road-not-taken",
-    "title": "Proposed: Choosing a terminal emulator for Windows",
+    "objectID": "decisions/20240411-elixir-libgodot-zig.html#tags",
+    "href": "decisions/20240411-elixir-libgodot-zig.html#tags",
+    "title": "Rejected: Binding GDExtension to a C-like Language for Libgodot to Implement a Distributed Simulation",
     "section": "",
-    "text": "The road not taken would be sticking with traditional, possibly proprietary, terminal emulators. While these may offer robust features and dedicated support, they often come at a significant cost and lack the flexibility of open-source solutions."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20231229-mRemoteNG.html#the-infrequent-use-case",
-    "href": "decisions/20231229-mRemoteNG.html#the-infrequent-use-case",
-    "title": "Proposed: Choosing a terminal emulator for Windows",
+    "objectID": "decisions/20240411-elixir-libgodot-zig.html#further-reading",
+    "href": "decisions/20240411-elixir-libgodot-zig.html#further-reading",
+    "title": "Rejected: Binding GDExtension to a C-like Language for Libgodot to Implement a Distributed Simulation",
     "section": "",
-    "text": "An infrequent use case might be using mRemoteNG for managing a small number of devices or connections. In such cases, the full potential of the tool may not be utilized."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\ngodot-zig\nzigler\n\nAssisted by Aria."
   },
   {
-    "objectID": "decisions/20231229-mRemoteNG.html#in-core-and-done-by-us",
-    "href": "decisions/20231229-mRemoteNG.html#in-core-and-done-by-us",
-    "title": "Proposed: Choosing a terminal emulator for Windows",
+    "objectID": "decisions/20220130-to-record-decisions-write-a-proposal.html",
+    "href": "decisions/20220130-to-record-decisions-write-a-proposal.html",
+    "title": "Accepted: To record decisions write a proposal.",
     "section": "",
-    "text": "This strategy is not in core and done by us. It involves leveraging an existing open-source solution to address our needs."
+    "text": "Status: accepted\nDeciders: V-Sekai,ifire,\nTags: V-Sekai,\n\n\n\nWe need to record our decisions.\n\n\n\nUse the decision record format.\n\n\n\n# [short title of solved problem and solution]\n\n- Status: proposed &lt;!-- draft | rejected | accepted | deprecated | superseded by --&gt;\n- Deciders: V-Sekai,\n- Tags: V-Sekai,\n\n## Context and Problem Statement\n\n[Describe the problem or limitation you are having in your project]\n\n[Describe the context and problem statement, e.g., in free form using two to three sentences. You may want to articulate the problem in the form of a question.]\n\n## Describe the proposed option and how it helps to overcome the problem or limitation\n\n[Describe the proposed option and how it helps to overcome the problem or limitation]\n\n## Describe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\n\n[Describe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams]\n\n## Positive Consequences &lt;!-- optional --&gt;\n\n- [e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]\n\n## Negative Consequences &lt;!-- optional --&gt;\n\n- [e.g., compromising quality attribute, follow-up decisions required, …]\n\n[this section can be repeated for each option if more than one option is open for consideration]\n\n## Option graveyard: &lt;!-- same as above --&gt;\n\n- Option: &lt;!-- [List the proposed options no longer open for consideration.] --&gt;\n- Rejection Reason: &lt;!-- [List the reasons for the rejection: (the Bad traits)] --&gt;\n\n## If this enhancement will not be used often, can it be worked around with a few lines of script?\n\n[If this enhancement will not be used often, can it be worked around with a few lines of script?]\n\n## Is there a reason why this should be core and done by us?\n\n[Is there a reason why this should be core and done by us?]\n\n## References &lt;!-- optional and numbers of links can vary --&gt;\n\n- [Link type](link to decision) &lt;!-- example: Refined by [xxx](yyyymmdd-xxx.md) --&gt;\n\n## Derivative License\n\nCopyright (c) 2021 V-Sekai contributors.\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE.\n\n\n\n\nAble to backtrack ideas.\n\n\n\n\n\nWork\n\n\n\n\n\nOption: Forgetting decisions.\nRejection Reason: We won’t remember the original reasons why we did things.\n\n\n\n\nNot code.\n\n\n\nWe are running the project.\n\n\n\n\nhttps://adr.github.io/\n\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20231229-mRemoteNG.html#further-reading",
-    "href": "decisions/20231229-mRemoteNG.html#further-reading",
-    "title": "Proposed: Choosing a terminal emulator for Windows",
+    "objectID": "decisions/20220130-to-record-decisions-write-a-proposal.html#context-and-problem-statement",
+    "href": "decisions/20220130-to-record-decisions-write-a-proposal.html#context-and-problem-statement",
+    "title": "Accepted: To record decisions write a proposal.",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
+    "text": "We need to record our decisions."
   },
   {
-    "objectID": "decisions/20230519-v-sekai-roadmap.html",
-    "href": "decisions/20230519-v-sekai-roadmap.html",
-    "title": "Superseded: V-Sekai Roadmap and Goals 2023-05-19",
+    "objectID": "decisions/20220130-to-record-decisions-write-a-proposal.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20220130-to-record-decisions-write-a-proposal.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Accepted: To record decisions write a proposal.",
     "section": "",
-    "text": "Superseded: V-Sekai Roadmap and Goals 2023-05-19\n\nMetadata\n\nStatus: superseded by 20230527-v-sekai-roadmap.md \nDeciders: V-Sekai,fire,lyuma,\nTags: V-Sekai,chatgpt4 summary,\n\n\n\nContext and Problem Statement\nWhat is the V-Sekai Roadmap and Goals?\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nThe roadmap presented here is short-term.\n\n\nDescribe how your proposal will work with code, pseudo-code, mock-ups, or diagrams\ngraph LR\n  subgraph Short Term\n    A[May 16th, 2023] --&gt; C[Assist Tokageit with Godot Engine 4.1 features before May 30th feature freeze]\n    B --&gt; D[Assist Godot Engine 4.1 features before May 30th feature freeze]\n    C --&gt; E\n    D --&gt; E[Vrm upload to the asset library after May 30th, 2023]\n    E --&gt; F[Unidot fix import bugs that blocked assets import]\n    F --&gt; G[Unidot Unity Import upload to the asset library after May 30th, 2023]\n    G --&gt; H[Implement onevoip]\n  end\n\n\nPositive Consequences\nWe can create V-Sekai easier.\n\n\nNegative Consequences\nOverhead might be hard.\n\n\nOption graveyard\n\nImplementing a custom voice chat solution instead of using onevoip\nWaiting for Godot Engine 4.2 instead of assisting with 4.1 features\nIgnoring SkeletonIK3D issues and focusing on other aspects\n\n\n\nIf this enhancement will be used infrequently, can it be worked around with a few lines of script?\nNo. This is a process.\n\n\nIs there a reason why this should be core and done by us?\nThis is a core process for V-Sekai.\n\n\nReferences\n\nV-Sekai"
+    "text": "Use the decision record format."
   },
   {
-    "objectID": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html",
-    "href": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html",
-    "title": "Proposed: Add VRM portable avatars and OMI_personality to the GLTF Transform tool",
+    "objectID": "decisions/20220130-to-record-decisions-write-a-proposal.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20220130-to-record-decisions-write-a-proposal.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Accepted: To record decisions write a proposal.",
     "section": "",
-    "text": "Status: proposed \nDeciders: V-Sekai\nTags: V-Sekai, GPT-4\n\n\n\n\nWe want to use OMI_personality, but it needs to be injected into a VRM file by tooling like GLTF Transform and GLTF Transform needs to know completely the VRM0 and VRM1 specification.\n\n\n\n\nStudy and understand the VRM0 and VRM1 specifications.\nImplement support for VRM portable avatars in GLTF Transform.\nAdd functionality to add OMI_personality into VRM files using GLTF Transform.\n\n\n\n\n\n\n\nReview the official VRM documentation and specifications.\nIdentify key components and features required for supporting VRM portable avatars in GLTF Transform.\n\n\n\n\n\nDesign and implement a new extension for GLTF Transform that can handle VRM portable avatars.\n\nEnable “.vrm” io reads\nWrite a plugin that increases the VRM version by one.\n\nEnsure compatibility with existing GLTF Transform features and extensions.\n\n\n\n\n\nModify the CLI configuration to accept OMI_personality data as input.\nImplement functionality to add OMI_personality data into VRM files using the new extension.\n\n\n\n\n\nCreate test cases with different VRM files and OMI_personality configurations.\nVerify the correct injection of OMI_personality data into VRM files.\nEnsure compatibility with other GLTF Transform features and extensions.\n\n\n\n\n\n\nSupport for VRM portable avatars in GLTF Transform.\nAbility to inject OMI_personality into VRM files.\nIncreased adoption of GLTF Transform for VRM-related projects.\n\n\n\n\n\nAdditional development and maintenance effort required for the new extension.\n\n\n\n\nN/A\n\n\n\nNo, this enhancement requires a deeper integration with GLTF Transform and understanding of the VRM specifications.\n\n\n\nYes, implementing this feature will provide a valuable addition to the GLTF Transform tool and cater to the growing VRM community.\n\n\n\n\nV-Sekai\nFor an example similar to KHR_lights_punctual, refer to this implementation.\nNo known design for VRM glTF_transform. However, there are two npm packages by quantumcraft that deal with VRM data, but they’re not open source.\nThe glTF Transform CLI allows specifying a config file, which can register additional glTF extensions and CLI functionality. Check out the CLI configuration documentation. Needle Tools has been trying this approach for NEEDLE_* extensions.\nOMI_personality"
+    "text": "# [short title of solved problem and solution]\n\n- Status: proposed &lt;!-- draft | rejected | accepted | deprecated | superseded by --&gt;\n- Deciders: V-Sekai,\n- Tags: V-Sekai,\n\n## Context and Problem Statement\n\n[Describe the problem or limitation you are having in your project]\n\n[Describe the context and problem statement, e.g., in free form using two to three sentences. You may want to articulate the problem in the form of a question.]\n\n## Describe the proposed option and how it helps to overcome the problem or limitation\n\n[Describe the proposed option and how it helps to overcome the problem or limitation]\n\n## Describe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\n\n[Describe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams]\n\n## Positive Consequences &lt;!-- optional --&gt;\n\n- [e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]\n\n## Negative Consequences &lt;!-- optional --&gt;\n\n- [e.g., compromising quality attribute, follow-up decisions required, …]\n\n[this section can be repeated for each option if more than one option is open for consideration]\n\n## Option graveyard: &lt;!-- same as above --&gt;\n\n- Option: &lt;!-- [List the proposed options no longer open for consideration.] --&gt;\n- Rejection Reason: &lt;!-- [List the reasons for the rejection: (the Bad traits)] --&gt;\n\n## If this enhancement will not be used often, can it be worked around with a few lines of script?\n\n[If this enhancement will not be used often, can it be worked around with a few lines of script?]\n\n## Is there a reason why this should be core and done by us?\n\n[Is there a reason why this should be core and done by us?]\n\n## References &lt;!-- optional and numbers of links can vary --&gt;\n\n- [Link type](link to decision) &lt;!-- example: Refined by [xxx](yyyymmdd-xxx.md) --&gt;\n\n## Derivative License\n\nCopyright (c) 2021 V-Sekai contributors.\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
   },
   {
-    "objectID": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html#metadata",
-    "href": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html#metadata",
-    "title": "Proposed: Add VRM portable avatars and OMI_personality to the GLTF Transform tool",
+    "objectID": "decisions/20220130-to-record-decisions-write-a-proposal.html#positive-consequences",
+    "href": "decisions/20220130-to-record-decisions-write-a-proposal.html#positive-consequences",
+    "title": "Accepted: To record decisions write a proposal.",
     "section": "",
-    "text": "Status: proposed \nDeciders: V-Sekai\nTags: V-Sekai, GPT-4"
+    "text": "Able to backtrack ideas."
   },
   {
-    "objectID": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html#context-and-problem-statement",
-    "href": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html#context-and-problem-statement",
-    "title": "Proposed: Add VRM portable avatars and OMI_personality to the GLTF Transform tool",
+    "objectID": "decisions/20220130-to-record-decisions-write-a-proposal.html#negative-consequences",
+    "href": "decisions/20220130-to-record-decisions-write-a-proposal.html#negative-consequences",
+    "title": "Accepted: To record decisions write a proposal.",
     "section": "",
-    "text": "We want to use OMI_personality, but it needs to be injected into a VRM file by tooling like GLTF Transform and GLTF Transform needs to know completely the VRM0 and VRM1 specification."
+    "text": "Work"
   },
   {
-    "objectID": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html#proposed-solution",
-    "href": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html#proposed-solution",
-    "title": "Proposed: Add VRM portable avatars and OMI_personality to the GLTF Transform tool",
+    "objectID": "decisions/20220130-to-record-decisions-write-a-proposal.html#option-graveyard",
+    "href": "decisions/20220130-to-record-decisions-write-a-proposal.html#option-graveyard",
+    "title": "Accepted: To record decisions write a proposal.",
     "section": "",
-    "text": "Study and understand the VRM0 and VRM1 specifications.\nImplement support for VRM portable avatars in GLTF Transform.\nAdd functionality to add OMI_personality into VRM files using GLTF Transform."
+    "text": "Option: Forgetting decisions.\nRejection Reason: We won’t remember the original reasons why we did things."
   },
   {
-    "objectID": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html#implementation",
-    "href": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html#implementation",
-    "title": "Proposed: Add VRM portable avatars and OMI_personality to the GLTF Transform tool",
+    "objectID": "decisions/20220130-to-record-decisions-write-a-proposal.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20220130-to-record-decisions-write-a-proposal.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Accepted: To record decisions write a proposal.",
     "section": "",
-    "text": "Review the official VRM documentation and specifications.\nIdentify key components and features required for supporting VRM portable avatars in GLTF Transform.\n\n\n\n\n\nDesign and implement a new extension for GLTF Transform that can handle VRM portable avatars.\n\nEnable “.vrm” io reads\nWrite a plugin that increases the VRM version by one.\n\nEnsure compatibility with existing GLTF Transform features and extensions.\n\n\n\n\n\nModify the CLI configuration to accept OMI_personality data as input.\nImplement functionality to add OMI_personality data into VRM files using the new extension.\n\n\n\n\n\nCreate test cases with different VRM files and OMI_personality configurations.\nVerify the correct injection of OMI_personality data into VRM files.\nEnsure compatibility with other GLTF Transform features and extensions."
+    "text": "Not code."
   },
   {
-    "objectID": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html#positive-consequences",
-    "href": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html#positive-consequences",
-    "title": "Proposed: Add VRM portable avatars and OMI_personality to the GLTF Transform tool",
+    "objectID": "decisions/20220130-to-record-decisions-write-a-proposal.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20220130-to-record-decisions-write-a-proposal.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Accepted: To record decisions write a proposal.",
     "section": "",
-    "text": "Support for VRM portable avatars in GLTF Transform.\nAbility to inject OMI_personality into VRM files.\nIncreased adoption of GLTF Transform for VRM-related projects."
+    "text": "We are running the project."
   },
   {
-    "objectID": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html#negative-consequences",
-    "href": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html#negative-consequences",
-    "title": "Proposed: Add VRM portable avatars and OMI_personality to the GLTF Transform tool",
+    "objectID": "decisions/20220130-to-record-decisions-write-a-proposal.html#references",
+    "href": "decisions/20220130-to-record-decisions-write-a-proposal.html#references",
+    "title": "Accepted: To record decisions write a proposal.",
     "section": "",
-    "text": "Additional development and maintenance effort required for the new extension."
+    "text": "https://adr.github.io/"
   },
   {
-    "objectID": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html#option-graveyard",
-    "href": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html#option-graveyard",
-    "title": "Proposed: Add VRM portable avatars and OMI_personality to the GLTF Transform tool",
+    "objectID": "decisions/20220130-to-record-decisions-write-a-proposal.html#derivative-license",
+    "href": "decisions/20220130-to-record-decisions-write-a-proposal.html#derivative-license",
+    "title": "Accepted: To record decisions write a proposal.",
     "section": "",
-    "text": "N/A"
+    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Add VRM portable avatars and OMI_personality to the GLTF Transform tool",
+    "objectID": "decisions/20221006-unidot-is-optional.html",
+    "href": "decisions/20221006-unidot-is-optional.html",
+    "title": "Proposed: Unidot is optional",
     "section": "",
-    "text": "No, this enhancement requires a deeper integration with GLTF Transform and understanding of the VRM specifications."
+    "text": "Status: proposed \nDeciders: V-Sekai,fire,MalekiRe\nTags: V-Sekai,\n\n\n\nIs this error of concerning building Godot Engine with V-Sekai game?\n\n\n\nUnidot addon error\n\n\n\n\n\nLet MalekiRe know that the Unidot addon is not critical to V-Sekai game.\n\n\n\nLeft this document here.\n\n\n\n\nIt’s not essential.\n\n\n\n\n\nProbably should fix the unidot addon.\n\n[this section can be repeated for each option if more than one option is open for consideration]\n\n\n\n\nOption: Do something.\nRejection Reason: It’s not essential.\n\n\n\n\nThis is a broken addon.\n\n\n\nWe maintain V-Sekai.\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Add VRM portable avatars and OMI_personality to the GLTF Transform tool",
+    "objectID": "decisions/20221006-unidot-is-optional.html#context-and-problem-statement",
+    "href": "decisions/20221006-unidot-is-optional.html#context-and-problem-statement",
+    "title": "Proposed: Unidot is optional",
     "section": "",
-    "text": "Yes, implementing this feature will provide a valuable addition to the GLTF Transform tool and cater to the growing VRM community."
+    "text": "Is this error of concerning building Godot Engine with V-Sekai game?\n\n\n\nUnidot addon error"
   },
   {
-    "objectID": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html#references",
-    "href": "decisions/20230519-add-vrm-omi-personality-gltf-extension.html#references",
-    "title": "Proposed: Add VRM portable avatars and OMI_personality to the GLTF Transform tool",
+    "objectID": "decisions/20221006-unidot-is-optional.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20221006-unidot-is-optional.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: Unidot is optional",
     "section": "",
-    "text": "V-Sekai\nFor an example similar to KHR_lights_punctual, refer to this implementation.\nNo known design for VRM glTF_transform. However, there are two npm packages by quantumcraft that deal with VRM data, but they’re not open source.\nThe glTF Transform CLI allows specifying a config file, which can register additional glTF extensions and CLI functionality. Check out the CLI configuration documentation. Needle Tools has been trying this approach for NEEDLE_* extensions.\nOMI_personality"
+    "text": "Let MalekiRe know that the Unidot addon is not critical to V-Sekai game."
   },
   {
-    "objectID": "decisions/20230125-without-viz-we-cannot-compare-the-interpolation.html",
-    "href": "decisions/20230125-without-viz-we-cannot-compare-the-interpolation.html",
-    "title": "Proposed: Without visualization, we cannot easily compare the interpolation states",
+    "objectID": "decisions/20221006-unidot-is-optional.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20221006-unidot-is-optional.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Unidot is optional",
     "section": "",
-    "text": "Proposed: Without visualization, we cannot easily compare the interpolation states\n\nMetadata\n\nStatus: proposed \nDeciders: V-Sekai,fire,\nTags: V-Sekai,\n\n\n\nContext and Problem Statement\nV-Sekai interpolation is poor.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nProvide visualization for interpolation.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nTo optimize end to end interpolation, you can use line graphs and scatter plots. A line graph shows the progress of an animation over time, while a scatter plot shows the data points that were used to create an animation.\nA line graph can help you debug physics interpolation issues. If your object’s position is not moving smoothly, you can look at how it moved over time and see if there are any sudden changes or jumps in its motion that might be causing problems. This will help you determine whether you need to adjust your physics simulation or tweak some other aspect of your game design.\nSecond, you can use scatter plots to visualize how different variables interact with each other. For example, if you have an object that’s supposed to move along a straight line but instead moves in a curved path, then it might be helpful for you to see whether there are any correlations between its position and its velocity. This will help you isolate which variables are causing this behavior so that you can optimize them individually or together.\n\n\nPositive Consequences\nWe are able to use V-Sekai easier.\n\n\nNegative Consequences\nWe cannot get other features in.\n\n\nOption graveyard\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nEasy chart is a gdscript addon but it is not trivial to reimplement.\n\n\nIs there a reason why this should be core and done by us?\nMotion posing is a core feature.\n\n\nReferences\n\nV-Sekai\nEasy Charts"
+    "text": "Left this document here."
   },
   {
-    "objectID": "decisions/20240329-ready-to-go-kit-windows-11.html",
-    "href": "decisions/20240329-ready-to-go-kit-windows-11.html",
-    "title": "Proposed: V-Sekai Setup as a Ready-to-Go Kit",
+    "objectID": "decisions/20221006-unidot-is-optional.html#positive-consequences",
+    "href": "decisions/20221006-unidot-is-optional.html#positive-consequences",
+    "title": "Proposed: Unidot is optional",
     "section": "",
-    "text": "V-Sekai is an open-source project that focuses on bringing social VR functionality to the Godot Engine. It aims to create a metaverse where users can interact and engage in various activities.\n\n\n\nThe current setup process for V-Sekai is complex and time-consuming, which may deter potential users and developers. We need to simplify this process by creating a ready-to-go kit.\n\n\n\nThe ready-to-go kit will be a pre-configured package containing all necessary files and dependencies for running V-Sekai. Users will simply need to download and extract the package to get started.\n\nDownload V-Sekai Kit\nExtract Files\nRun V-Sekai\n\n\n\n\n\nSimplified setup process\nIncreased accessibility for non-technical users\nPotential increase in user base and community contributions\n\n\n\n\n\nMaintenance of the kit could become resource-intensive if not automated\nPotential security risks if not properly managed\n\n\n\n\nWe could have continued with the existing setup process, but this would likely limit the growth and accessibility of V-Sekai.\n\n\n\nUsers who wish to customize their V-Sekai experience extensively may find the ready-to-go kit limiting. However, they still have the option to manually set up V-Sekai.\n\n\n\nThis proposal will be implemented by the V-Sekai development team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
+    "text": "It’s not essential."
   },
   {
-    "objectID": "decisions/20240329-ready-to-go-kit-windows-11.html#the-context",
-    "href": "decisions/20240329-ready-to-go-kit-windows-11.html#the-context",
-    "title": "Proposed: V-Sekai Setup as a Ready-to-Go Kit",
+    "objectID": "decisions/20221006-unidot-is-optional.html#negative-consequences",
+    "href": "decisions/20221006-unidot-is-optional.html#negative-consequences",
+    "title": "Proposed: Unidot is optional",
     "section": "",
-    "text": "V-Sekai is an open-source project that focuses on bringing social VR functionality to the Godot Engine. It aims to create a metaverse where users can interact and engage in various activities."
+    "text": "Probably should fix the unidot addon.\n\n[this section can be repeated for each option if more than one option is open for consideration]"
   },
   {
-    "objectID": "decisions/20240329-ready-to-go-kit-windows-11.html#the-problem-statement",
-    "href": "decisions/20240329-ready-to-go-kit-windows-11.html#the-problem-statement",
-    "title": "Proposed: V-Sekai Setup as a Ready-to-Go Kit",
+    "objectID": "decisions/20221006-unidot-is-optional.html#option-graveyard",
+    "href": "decisions/20221006-unidot-is-optional.html#option-graveyard",
+    "title": "Proposed: Unidot is optional",
     "section": "",
-    "text": "The current setup process for V-Sekai is complex and time-consuming, which may deter potential users and developers. We need to simplify this process by creating a ready-to-go kit."
+    "text": "Option: Do something.\nRejection Reason: It’s not essential."
   },
   {
-    "objectID": "decisions/20240329-ready-to-go-kit-windows-11.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240329-ready-to-go-kit-windows-11.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: V-Sekai Setup as a Ready-to-Go Kit",
+    "objectID": "decisions/20221006-unidot-is-optional.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20221006-unidot-is-optional.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Unidot is optional",
     "section": "",
-    "text": "The ready-to-go kit will be a pre-configured package containing all necessary files and dependencies for running V-Sekai. Users will simply need to download and extract the package to get started.\n\nDownload V-Sekai Kit\nExtract Files\nRun V-Sekai"
+    "text": "This is a broken addon."
   },
   {
-    "objectID": "decisions/20240329-ready-to-go-kit-windows-11.html#the-benefits",
-    "href": "decisions/20240329-ready-to-go-kit-windows-11.html#the-benefits",
-    "title": "Proposed: V-Sekai Setup as a Ready-to-Go Kit",
+    "objectID": "decisions/20221006-unidot-is-optional.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20221006-unidot-is-optional.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Unidot is optional",
     "section": "",
-    "text": "Simplified setup process\nIncreased accessibility for non-technical users\nPotential increase in user base and community contributions"
+    "text": "We maintain V-Sekai."
   },
   {
-    "objectID": "decisions/20240329-ready-to-go-kit-windows-11.html#the-downsides",
-    "href": "decisions/20240329-ready-to-go-kit-windows-11.html#the-downsides",
-    "title": "Proposed: V-Sekai Setup as a Ready-to-Go Kit",
+    "objectID": "decisions/20221006-unidot-is-optional.html#derivative-license",
+    "href": "decisions/20221006-unidot-is-optional.html#derivative-license",
+    "title": "Proposed: Unidot is optional",
     "section": "",
-    "text": "Maintenance of the kit could become resource-intensive if not automated\nPotential security risks if not properly managed"
+    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240329-ready-to-go-kit-windows-11.html#the-road-not-taken",
-    "href": "decisions/20240329-ready-to-go-kit-windows-11.html#the-road-not-taken",
-    "title": "Proposed: V-Sekai Setup as a Ready-to-Go Kit",
+    "objectID": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html",
+    "href": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html",
+    "title": "Proposed: Convert Blender CC0 Base Mesh to Godot Engine T-Pose",
     "section": "",
-    "text": "We could have continued with the existing setup process, but this would likely limit the growth and accessibility of V-Sekai."
+    "text": "We would like to have several base meshes for testing and for skeleton merge clothing tests.\n\n\n\nThe current process of converting Blender CC0 base meshes to a format compatible with the Godot Engine is cumbersome and lacks a standardized approach. This proposal aims to streamline the conversion process, ensuring consistency and efficiency.\n\n\n\n\nInstall Blender 4.1.1\nDownload “Human Base Meshes bundle by Blender Studio CC0 Licensed”\nTest Auto Rig Pro version 3.70.38\nPick a category:\n\nA. Stylized\nB. Realistic\nC. Stylized Parts\nD. Realistic Parts\n\nWe’re picking realistic.\nPick feminine or masculine: We’re picking feminine.\nSelect all the meshes\nUse Auto-Rig Pro Smart: “Get Selected Objects”\nAdd armature: Human\n\nSet biped\nAdd additional: Twist\n\nClick on the body parts:\n\nNeck (This is the base of the neck)\nChin (This is the tip of the chin)\nShoulder (It’s in between the arm.)\nSpine root (Crotch area.)\nAnkles (Above the foot.)\n\nSet skeleton type to “UE5 Manny-Quinn”\nAdd facial\nRemember to set eyes (required)\nSet pelvis up to be enabled\nClick on the facial areas:\n\nEyebrows\nEyes\nMouth\n\nSet character name (it’s an option in misc tab) to body_feminine_realistic\nClick match to rig\nSelect all meshes, and the rig. Then go to the Skin tab\nSelect scale fix\nDo not enable preserve volume\nThen hit bind (Ensure the engine is heat map, voxel skinning gives poor results around the shoulder blades on base meshes.)\nGo to Rig\nDo not set pose to T-Pose. It is not reversible.\nSet the pose to “UE5 Manny-Quinn”\nTODO: Create a new animation action and name it “A-POSE”\nConfigure FBX exporter:\n\nUnity humanoid\nClick fix rig (again)\nSelect advanced\nFull facial\nExport root bone c_traj\nSet root motion\n\nEnsure that the multi-mesh GEO-body_female_realistic is set to render disabled\nExport as GLB\nOpen GLB in Godot Engine\nTODO: Instructions on the bone map\nTODO: Instructions on silhouette fixer:\n\nDisable list:\n\nLeftFoot\nRightFoot\nNeck\nHead\nUpperChest\n\n\n\n\n\n\n\nImproved Efficiency: Streamlining the conversion process saves time and reduces manual effort.\nConsistency: Standardizing the approach ensures uniformity across different base meshes.\nEnhanced Compatibility: Ensures that the converted meshes are fully compatible with the Godot Engine.\n\n\n\n\n\nInitial Learning Curve: Team members may need time to familiarize themselves with the new process.\nTool Dependency: Reliance on specific tools like Auto Rig Pro may limit flexibility.\n\n\n\n\nAlternative approaches such as manual rigging or using different software were considered but ultimately deemed less efficient or effective.\n\n\n\nIn rare cases where highly specialized or technical requirements arise, additional human oversight may be necessary to ensure accuracy and appropriateness.\n\n\n\nThis proposal aligns with our core values of efficiency and professionalism and will be implemented by our team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nHuman Base Meshes bundle by Blender Studio CC0 Licensed - Human Base Meshes bundle by Blender Studio includes 17 separate meshes, including complete male and female figures, plus individual body parts like feet, hands, heads, jaws, and eyeballs.\nAuto Rig Pro\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240329-ready-to-go-kit-windows-11.html#the-infrequent-use-case",
-    "href": "decisions/20240329-ready-to-go-kit-windows-11.html#the-infrequent-use-case",
-    "title": "Proposed: V-Sekai Setup as a Ready-to-Go Kit",
+    "objectID": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#the-context",
+    "href": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#the-context",
+    "title": "Proposed: Convert Blender CC0 Base Mesh to Godot Engine T-Pose",
     "section": "",
-    "text": "Users who wish to customize their V-Sekai experience extensively may find the ready-to-go kit limiting. However, they still have the option to manually set up V-Sekai."
+    "text": "We would like to have several base meshes for testing and for skeleton merge clothing tests."
   },
   {
-    "objectID": "decisions/20240329-ready-to-go-kit-windows-11.html#in-core-and-done-by-us",
-    "href": "decisions/20240329-ready-to-go-kit-windows-11.html#in-core-and-done-by-us",
-    "title": "Proposed: V-Sekai Setup as a Ready-to-Go Kit",
+    "objectID": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#the-problem-statement",
+    "href": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#the-problem-statement",
+    "title": "Proposed: Convert Blender CC0 Base Mesh to Godot Engine T-Pose",
     "section": "",
-    "text": "This proposal will be implemented by the V-Sekai development team."
+    "text": "The current process of converting Blender CC0 base meshes to a format compatible with the Godot Engine is cumbersome and lacks a standardized approach. This proposal aims to streamline the conversion process, ensuring consistency and efficiency."
   },
   {
-    "objectID": "decisions/20240329-ready-to-go-kit-windows-11.html#status",
-    "href": "decisions/20240329-ready-to-go-kit-windows-11.html#status",
-    "title": "Proposed: V-Sekai Setup as a Ready-to-Go Kit",
+    "objectID": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Convert Blender CC0 Base Mesh to Godot Engine T-Pose",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "Install Blender 4.1.1\nDownload “Human Base Meshes bundle by Blender Studio CC0 Licensed”\nTest Auto Rig Pro version 3.70.38\nPick a category:\n\nA. Stylized\nB. Realistic\nC. Stylized Parts\nD. Realistic Parts\n\nWe’re picking realistic.\nPick feminine or masculine: We’re picking feminine.\nSelect all the meshes\nUse Auto-Rig Pro Smart: “Get Selected Objects”\nAdd armature: Human\n\nSet biped\nAdd additional: Twist\n\nClick on the body parts:\n\nNeck (This is the base of the neck)\nChin (This is the tip of the chin)\nShoulder (It’s in between the arm.)\nSpine root (Crotch area.)\nAnkles (Above the foot.)\n\nSet skeleton type to “UE5 Manny-Quinn”\nAdd facial\nRemember to set eyes (required)\nSet pelvis up to be enabled\nClick on the facial areas:\n\nEyebrows\nEyes\nMouth\n\nSet character name (it’s an option in misc tab) to body_feminine_realistic\nClick match to rig\nSelect all meshes, and the rig. Then go to the Skin tab\nSelect scale fix\nDo not enable preserve volume\nThen hit bind (Ensure the engine is heat map, voxel skinning gives poor results around the shoulder blades on base meshes.)\nGo to Rig\nDo not set pose to T-Pose. It is not reversible.\nSet the pose to “UE5 Manny-Quinn”\nTODO: Create a new animation action and name it “A-POSE”\nConfigure FBX exporter:\n\nUnity humanoid\nClick fix rig (again)\nSelect advanced\nFull facial\nExport root bone c_traj\nSet root motion\n\nEnsure that the multi-mesh GEO-body_female_realistic is set to render disabled\nExport as GLB\nOpen GLB in Godot Engine\nTODO: Instructions on the bone map\nTODO: Instructions on silhouette fixer:\n\nDisable list:\n\nLeftFoot\nRightFoot\nNeck\nHead\nUpperChest"
   },
   {
-    "objectID": "decisions/20240329-ready-to-go-kit-windows-11.html#decision-makers",
-    "href": "decisions/20240329-ready-to-go-kit-windows-11.html#decision-makers",
-    "title": "Proposed: V-Sekai Setup as a Ready-to-Go Kit",
+    "objectID": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#the-benefits",
+    "href": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#the-benefits",
+    "title": "Proposed: Convert Blender CC0 Base Mesh to Godot Engine T-Pose",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "Improved Efficiency: Streamlining the conversion process saves time and reduces manual effort.\nConsistency: Standardizing the approach ensures uniformity across different base meshes.\nEnhanced Compatibility: Ensures that the converted meshes are fully compatible with the Godot Engine."
   },
   {
-    "objectID": "decisions/20240329-ready-to-go-kit-windows-11.html#tags",
-    "href": "decisions/20240329-ready-to-go-kit-windows-11.html#tags",
-    "title": "Proposed: V-Sekai Setup as a Ready-to-Go Kit",
+    "objectID": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#the-downsides",
+    "href": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#the-downsides",
+    "title": "Proposed: Convert Blender CC0 Base Mesh to Godot Engine T-Pose",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Initial Learning Curve: Team members may need time to familiarize themselves with the new process.\nTool Dependency: Reliance on specific tools like Auto Rig Pro may limit flexibility."
   },
   {
-    "objectID": "decisions/20240329-ready-to-go-kit-windows-11.html#further-reading",
-    "href": "decisions/20240329-ready-to-go-kit-windows-11.html#further-reading",
-    "title": "Proposed: V-Sekai Setup as a Ready-to-Go Kit",
+    "objectID": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#the-road-not-taken",
+    "href": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#the-road-not-taken",
+    "title": "Proposed: Convert Blender CC0 Base Mesh to Godot Engine T-Pose",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
+    "text": "Alternative approaches such as manual rigging or using different software were considered but ultimately deemed less efficient or effective."
   },
   {
-    "objectID": "decisions/20230804-dokku.html",
-    "href": "decisions/20230804-dokku.html",
-    "title": "Proposed: Dokku for V-Sekai URO Backend Services Hosting and Development",
+    "objectID": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#the-infrequent-use-case",
+    "href": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#the-infrequent-use-case",
+    "title": "Proposed: Convert Blender CC0 Base Mesh to Godot Engine T-Pose",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, Dokku, Backend, Hosting, Development\n\n\n\n\nV-Sekai is exploring options to improve its backend services hosting and development. The goal is to find a system that can offer scalability, ease of deployment, and efficient resource management.\n\n\n\nOne potential solution could be Dokku, a Docker-powered mini-Heroku. Dokku provides a platform that could potentially meet our needs for building, deploying and managing applications effectively.\n\n\n\nIf Dokku were chosen, the implementation would involve setting up a Dokku server, migrating existing services, and training the team on how to use Dokku for development and deployment.\n# Install Dokku\nwget https://raw.githubusercontent.com/dokku/dokku/v0.21.4/bootstrap.sh;\nsudo DOKKU_TAG=v0.21.4 bash bootstrap.sh\n\n\n\n\nScalability: Dokku has features that could allow us to scale our applications based on demand.\nEase of Deployment: Dokku’s git-based deployment system might simplify the process of deploying new versions of our applications.\nResource Management: Dokku’s use of Docker containers could lead to more efficient use of system resources.\n\n\n\n\n\nThere might be a learning curve for the team members who are not familiar with Dokku or Docker.\nMigration of existing services to a new platform could require significant time and resources.\n\n\n\n\nOther options considered include traditional VM-based hosting and other PaaS solutions like Heroku or AWS Elastic Beanstalk. These options have their own sets of advantages and disadvantages that need to be weighed against those of Dokku.\n\n\n\nThis depends on the specific requirements of our backend services. If the enhancement is fundamental to the hosting and development of our backend services, it may not be possible to work around it with a few lines of script.\n\n\n\nThe choice of hosting and development environment is crucial for the efficiency and effectiveness of our operations. Whether Dokku or another solution is chosen, it will be important for us to maintain control over this aspect of our infrastructure.\n\n\n\n\nV-Sekai\nDokku Documentation"
+    "text": "In rare cases where highly specialized or technical requirements arise, additional human oversight may be necessary to ensure accuracy and appropriateness."
   },
   {
-    "objectID": "decisions/20230804-dokku.html#metadata",
-    "href": "decisions/20230804-dokku.html#metadata",
-    "title": "Proposed: Dokku for V-Sekai URO Backend Services Hosting and Development",
+    "objectID": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#in-core-and-done-by-us",
+    "href": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#in-core-and-done-by-us",
+    "title": "Proposed: Convert Blender CC0 Base Mesh to Godot Engine T-Pose",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, Dokku, Backend, Hosting, Development"
+    "text": "This proposal aligns with our core values of efficiency and professionalism and will be implemented by our team."
   },
   {
-    "objectID": "decisions/20230804-dokku.html#context-and-problem-statement",
-    "href": "decisions/20230804-dokku.html#context-and-problem-statement",
-    "title": "Proposed: Dokku for V-Sekai URO Backend Services Hosting and Development",
+    "objectID": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#status",
+    "href": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#status",
+    "title": "Proposed: Convert Blender CC0 Base Mesh to Godot Engine T-Pose",
     "section": "",
-    "text": "V-Sekai is exploring options to improve its backend services hosting and development. The goal is to find a system that can offer scalability, ease of deployment, and efficient resource management."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20230804-dokku.html#proposed-solution",
-    "href": "decisions/20230804-dokku.html#proposed-solution",
-    "title": "Proposed: Dokku for V-Sekai URO Backend Services Hosting and Development",
+    "objectID": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#decision-makers",
+    "href": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#decision-makers",
+    "title": "Proposed: Convert Blender CC0 Base Mesh to Godot Engine T-Pose",
     "section": "",
-    "text": "One potential solution could be Dokku, a Docker-powered mini-Heroku. Dokku provides a platform that could potentially meet our needs for building, deploying and managing applications effectively."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20230804-dokku.html#implementation",
-    "href": "decisions/20230804-dokku.html#implementation",
-    "title": "Proposed: Dokku for V-Sekai URO Backend Services Hosting and Development",
+    "objectID": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#tags",
+    "href": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#tags",
+    "title": "Proposed: Convert Blender CC0 Base Mesh to Godot Engine T-Pose",
     "section": "",
-    "text": "If Dokku were chosen, the implementation would involve setting up a Dokku server, migrating existing services, and training the team on how to use Dokku for development and deployment.\n# Install Dokku\nwget https://raw.githubusercontent.com/dokku/dokku/v0.21.4/bootstrap.sh;\nsudo DOKKU_TAG=v0.21.4 bash bootstrap.sh"
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20230804-dokku.html#potential-benefits",
-    "href": "decisions/20230804-dokku.html#potential-benefits",
-    "title": "Proposed: Dokku for V-Sekai URO Backend Services Hosting and Development",
+    "objectID": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#further-reading",
+    "href": "decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html#further-reading",
+    "title": "Proposed: Convert Blender CC0 Base Mesh to Godot Engine T-Pose",
     "section": "",
-    "text": "Scalability: Dokku has features that could allow us to scale our applications based on demand.\nEase of Deployment: Dokku’s git-based deployment system might simplify the process of deploying new versions of our applications.\nResource Management: Dokku’s use of Docker containers could lead to more efficient use of system resources."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nHuman Base Meshes bundle by Blender Studio CC0 Licensed - Human Base Meshes bundle by Blender Studio includes 17 separate meshes, including complete male and female figures, plus individual body parts like feet, hands, heads, jaws, and eyeballs.\nAuto Rig Pro\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20230804-dokku.html#potential-drawbacks",
-    "href": "decisions/20230804-dokku.html#potential-drawbacks",
-    "title": "Proposed: Dokku for V-Sekai URO Backend Services Hosting and Development",
+    "objectID": "decisions/20231225-mesh-transformer-clothing.html",
+    "href": "decisions/20231225-mesh-transformer-clothing.html",
+    "title": "Proposed: Mesh Transformer Clothing",
     "section": "",
-    "text": "There might be a learning curve for the team members who are not familiar with Dokku or Docker.\nMigration of existing services to a new platform could require significant time and resources."
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, second rank\n\n\n\n\nIn the realm of Virtual Reality (VR), personalization and style expression play a significant role in enhancing user experience. One way to achieve this is through customizable clothing for avatars, which can be made possible with the use of Mesh Transformers.\n\n\n\nThe challenge lies in enabling personalization and style expression in virtual environments by designing a wide array of clothing items optimized for VR. This involves generating meshes for different garments like jackets, shirts, pants, dresses, and more.\n\n\n\nThe strategy is to use Mesh Transformers to generate these clothing items. The goal is to create clothing that is visually appealing, stylistically diverse, and adaptable to different avatar bodies, while maintaining a low polygon count for optimal VR performance.\n\n\n\nThe upside is the creation of more immersive and engaging virtual environments, with avatars that can express their individuality and style through their clothing.\n\n\n\nThe downside could be the potential increase in complexity and computational requirements due to the addition of more detailed and diverse clothing items.\n\n\n\nAn alternative approach could have been to use simpler, less diverse clothing designs. However, this would limit the range of personal expression possible in VR environments.\n\n\n\nIn cases where VR environments are used for simple tasks or interactions, the need for highly diverse and customizable clothing may not be as high.\n\n\n\nYes, this proposal is core to our mission of enhancing VR experiences and will be implemented by our team.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20230804-dokku.html#option-graveyard",
-    "href": "decisions/20230804-dokku.html#option-graveyard",
-    "title": "Proposed: Dokku for V-Sekai URO Backend Services Hosting and Development",
+    "objectID": "decisions/20231225-mesh-transformer-clothing.html#metadata",
+    "href": "decisions/20231225-mesh-transformer-clothing.html#metadata",
+    "title": "Proposed: Mesh Transformer Clothing",
     "section": "",
-    "text": "Other options considered include traditional VM-based hosting and other PaaS solutions like Heroku or AWS Elastic Beanstalk. These options have their own sets of advantages and disadvantages that need to be weighed against those of Dokku."
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, second rank"
   },
   {
-    "objectID": "decisions/20230804-dokku.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230804-dokku.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Dokku for V-Sekai URO Backend Services Hosting and Development",
+    "objectID": "decisions/20231225-mesh-transformer-clothing.html#the-backdrop",
+    "href": "decisions/20231225-mesh-transformer-clothing.html#the-backdrop",
+    "title": "Proposed: Mesh Transformer Clothing",
     "section": "",
-    "text": "This depends on the specific requirements of our backend services. If the enhancement is fundamental to the hosting and development of our backend services, it may not be possible to work around it with a few lines of script."
+    "text": "In the realm of Virtual Reality (VR), personalization and style expression play a significant role in enhancing user experience. One way to achieve this is through customizable clothing for avatars, which can be made possible with the use of Mesh Transformers."
   },
   {
-    "objectID": "decisions/20230804-dokku.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230804-dokku.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Dokku for V-Sekai URO Backend Services Hosting and Development",
+    "objectID": "decisions/20231225-mesh-transformer-clothing.html#the-challenge",
+    "href": "decisions/20231225-mesh-transformer-clothing.html#the-challenge",
+    "title": "Proposed: Mesh Transformer Clothing",
     "section": "",
-    "text": "The choice of hosting and development environment is crucial for the efficiency and effectiveness of our operations. Whether Dokku or another solution is chosen, it will be important for us to maintain control over this aspect of our infrastructure."
+    "text": "The challenge lies in enabling personalization and style expression in virtual environments by designing a wide array of clothing items optimized for VR. This involves generating meshes for different garments like jackets, shirts, pants, dresses, and more."
   },
   {
-    "objectID": "decisions/20230804-dokku.html#references",
-    "href": "decisions/20230804-dokku.html#references",
-    "title": "Proposed: Dokku for V-Sekai URO Backend Services Hosting and Development",
+    "objectID": "decisions/20231225-mesh-transformer-clothing.html#the-strategy",
+    "href": "decisions/20231225-mesh-transformer-clothing.html#the-strategy",
+    "title": "Proposed: Mesh Transformer Clothing",
     "section": "",
-    "text": "V-Sekai\nDokku Documentation"
+    "text": "The strategy is to use Mesh Transformers to generate these clothing items. The goal is to create clothing that is visually appealing, stylistically diverse, and adaptable to different avatar bodies, while maintaining a low polygon count for optimal VR performance."
   },
   {
-    "objectID": "decisions/20211105-have-an-webxr-version-of-v-sekai.html",
-    "href": "decisions/20211105-have-an-webxr-version-of-v-sekai.html",
-    "title": "Rejected: Have an WebXR version of V-Sekai that is more accessible",
+    "objectID": "decisions/20231225-mesh-transformer-clothing.html#the-upside",
+    "href": "decisions/20231225-mesh-transformer-clothing.html#the-upside",
+    "title": "Proposed: Mesh Transformer Clothing",
     "section": "",
-    "text": "Status: rejected \nDeciders: V-Sekai,fire,\nTags: V-Sekai,\n\n\n\nIt’s hard to get access to V-Sekai.\n\n\n\nLet’s strip down our V-Sekai prototype and make it work for WebXR.\n\n\n\n\nUpgrade to 3.4 Godot Engine\n\n\n\n\n\n[e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]\n\n\n\n\n\nTook too much effort to verify.\n\n\n\n\n\nOption: \nRejection Reason: \n\n\n\n\nThis is not a few lines of code and is a V-Sekai core topic.\n\n\n\nWe maintain core V-Sekai.\n\n\n\n\nhttps://github.com/V-Sekai/groups-workspace-fire\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "The upside is the creation of more immersive and engaging virtual environments, with avatars that can express their individuality and style through their clothing."
   },
   {
-    "objectID": "decisions/20211105-have-an-webxr-version-of-v-sekai.html#context-and-problem-statement",
-    "href": "decisions/20211105-have-an-webxr-version-of-v-sekai.html#context-and-problem-statement",
-    "title": "Rejected: Have an WebXR version of V-Sekai that is more accessible",
+    "objectID": "decisions/20231225-mesh-transformer-clothing.html#the-downside",
+    "href": "decisions/20231225-mesh-transformer-clothing.html#the-downside",
+    "title": "Proposed: Mesh Transformer Clothing",
     "section": "",
-    "text": "It’s hard to get access to V-Sekai."
+    "text": "The downside could be the potential increase in complexity and computational requirements due to the addition of more detailed and diverse clothing items."
   },
   {
-    "objectID": "decisions/20211105-have-an-webxr-version-of-v-sekai.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20211105-have-an-webxr-version-of-v-sekai.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Rejected: Have an WebXR version of V-Sekai that is more accessible",
+    "objectID": "decisions/20231225-mesh-transformer-clothing.html#the-road-not-taken",
+    "href": "decisions/20231225-mesh-transformer-clothing.html#the-road-not-taken",
+    "title": "Proposed: Mesh Transformer Clothing",
     "section": "",
-    "text": "Let’s strip down our V-Sekai prototype and make it work for WebXR."
+    "text": "An alternative approach could have been to use simpler, less diverse clothing designs. However, this would limit the range of personal expression possible in VR environments."
   },
   {
-    "objectID": "decisions/20211105-have-an-webxr-version-of-v-sekai.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20211105-have-an-webxr-version-of-v-sekai.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Rejected: Have an WebXR version of V-Sekai that is more accessible",
+    "objectID": "decisions/20231225-mesh-transformer-clothing.html#the-infrequent-use-case",
+    "href": "decisions/20231225-mesh-transformer-clothing.html#the-infrequent-use-case",
+    "title": "Proposed: Mesh Transformer Clothing",
     "section": "",
-    "text": "Upgrade to 3.4 Godot Engine"
+    "text": "In cases where VR environments are used for simple tasks or interactions, the need for highly diverse and customizable clothing may not be as high."
   },
   {
-    "objectID": "decisions/20211105-have-an-webxr-version-of-v-sekai.html#positive-consequences",
-    "href": "decisions/20211105-have-an-webxr-version-of-v-sekai.html#positive-consequences",
-    "title": "Rejected: Have an WebXR version of V-Sekai that is more accessible",
+    "objectID": "decisions/20231225-mesh-transformer-clothing.html#in-core-and-done-by-us",
+    "href": "decisions/20231225-mesh-transformer-clothing.html#in-core-and-done-by-us",
+    "title": "Proposed: Mesh Transformer Clothing",
     "section": "",
-    "text": "[e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]"
+    "text": "Yes, this proposal is core to our mission of enhancing VR experiences and will be implemented by our team."
   },
   {
-    "objectID": "decisions/20211105-have-an-webxr-version-of-v-sekai.html#negative-consequences",
-    "href": "decisions/20211105-have-an-webxr-version-of-v-sekai.html#negative-consequences",
-    "title": "Rejected: Have an WebXR version of V-Sekai that is more accessible",
+    "objectID": "decisions/20231225-mesh-transformer-clothing.html#further-reading",
+    "href": "decisions/20231225-mesh-transformer-clothing.html#further-reading",
+    "title": "Proposed: Mesh Transformer Clothing",
     "section": "",
-    "text": "Took too much effort to verify."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20211105-have-an-webxr-version-of-v-sekai.html#option-graveyard",
-    "href": "decisions/20211105-have-an-webxr-version-of-v-sekai.html#option-graveyard",
-    "title": "Rejected: Have an WebXR version of V-Sekai that is more accessible",
+    "objectID": "decisions/20230123-ready-the-net-demo.html",
+    "href": "decisions/20230123-ready-the-net-demo.html",
+    "title": "Proposed: Ready net demo",
     "section": "",
-    "text": "Option: \nRejection Reason:"
+    "text": "Proposed: Ready net demo\n\nContext and Problem Statement\nGet the net demo ready for merge into V-Sekai\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nI want to get the net demo ready for presentation.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\n\njitter buffer window of 100ms\nbit packing with the godot engine core animation compression\nperfect prediction using ballistic trajectory https://github.com/fbsamples/oculus-networked-physics-sample/blob/f4242f317fc1c81348308bdd69774c637c3c0f91/Networked%20Physics/Assets/Scripts/Prediction.cs#L48\n\n\n\nPositive Consequences\nWe’ll have lag free VR network sync.\n\n\nNegative Consequences\nMay have cheating with this type of replication.\n\n\nOption graveyard\nOption: The status quo. Rejection Reason: This solves nothing.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot trivial.\n\n\nIs there a reason why this should be core and done by us?\nWe are doing this.\n\n\nReferences\n\nV-Sekai\n\n\n\nLicense of the contribution\nCopyright (c) 2019-latest V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20211105-have-an-webxr-version-of-v-sekai.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20211105-have-an-webxr-version-of-v-sekai.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Rejected: Have an WebXR version of V-Sekai that is more accessible",
+    "objectID": "decisions/20230131-meeting-at-gdc-2023.html",
+    "href": "decisions/20230131-meeting-at-gdc-2023.html",
+    "title": "Accepted: Meet at GDC SF 2023",
     "section": "",
-    "text": "This is not a few lines of code and is a V-Sekai core topic."
+    "text": "Accepted: Meet at GDC SF 2023\nCompleted.\n\nContext and Problem Statement\nWe would like to meet at the Gdeveloper conference San Francisco.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nWould like meet and try to ask for assistance.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\n\nPropose a meeting spot\nFly and ensure lodging\n\n\n\nPositive Consequences\nMeet and greet. &lt;3\n\n\nNegative Consequences\nAt what cost!\n\n\nOption graveyard\nNo response\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot coding related.\n\n\nIs there a reason why this should be core and done by us?\nWe would like to do this.\n\n\nReferences\n\nV-Sekai\n\n\n\nLicense of the contribution\nCopyright (c) 2022 K. S. Ernest (iFire) Lee contributors. Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20211105-have-an-webxr-version-of-v-sekai.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20211105-have-an-webxr-version-of-v-sekai.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Rejected: Have an WebXR version of V-Sekai that is more accessible",
+    "objectID": "decisions/20230508-novel-3d-views.html",
+    "href": "decisions/20230508-novel-3d-views.html",
+    "title": "Draft: Convert segmented front facing 3D Garment images to novel 3d views for 3d modeling",
     "section": "",
-    "text": "We maintain core V-Sekai."
+    "text": "Status: draft \nDeciders: V-Sekai, fire,\nTags: V-Sekai, ChatGPT-4\n\n\n\n\nWe want to create 3D models from a front-shot of the garment.\n\n\n\nUse Meta’s image segmentation model and zero123’s 3D reconstruction algorithm to generate novel 3D views of garments from a single front-shot image.\n\n\n\n\nPreprocess the input image: Resize and normalize the input image to meet the requirements of Meta’s image segmentation model.\nExtract the garment using Meta’s image segmentation model:\n\nLoad the pre-trained Meta’s image segmentation model.\nPass the preprocessed input image through the model to obtain the segmented garment image.\n\nPrepare the segmented garment for 3D reconstruction:\n\nLoad segmented garment image into zero123’s 3D novel view algorithm.\n\nApply zero123’s 3D reconstruction algorithm:\n\nLoad the pre-trained zero123’s 3D reconstruction model.\nPass the prepared segmented garment image through the model to generate novel 3d views of the garment.\n\nGenerate novel 3D views of the garment:\n\nRotate the 3D camera at intervals of 20 degrees around the garment to capture multiple 3D views.\n\nManually model the garment using views:\n\nUse a 3d design tool like Blender to create a mesh.\n\n\n\n\n\n\nEnhanced user experience with realistic 3D garment previews.\nImproved understanding of garment fit and style.\nIncreased creator satisfaction.\n\n\n\n\n\nPotential increase in computational resources required for processing.\nPossible limitations in accuracy and quality of generated 3D models.\n\n\n\n\n\nUsing multiple images for 3D reconstruction (discarded due to not enough aligned input images for 3D construction).\n\n\n\n\nNo, this enhancement requires integration of advanced image segmentation and 3D reconstruction algorithms, which cannot be achieved with a simple script.\n\n\n\nYes, implementing this feature as part of our core project will improve our opensource community of creators.\n\n\n\n\nV-Sekai"
   },
   {
-    "objectID": "decisions/20211105-have-an-webxr-version-of-v-sekai.html#references",
-    "href": "decisions/20211105-have-an-webxr-version-of-v-sekai.html#references",
-    "title": "Rejected: Have an WebXR version of V-Sekai that is more accessible",
+    "objectID": "decisions/20230508-novel-3d-views.html#metadata",
+    "href": "decisions/20230508-novel-3d-views.html#metadata",
+    "title": "Draft: Convert segmented front facing 3D Garment images to novel 3d views for 3d modeling",
     "section": "",
-    "text": "https://github.com/V-Sekai/groups-workspace-fire"
+    "text": "Status: draft \nDeciders: V-Sekai, fire,\nTags: V-Sekai, ChatGPT-4"
   },
   {
-    "objectID": "decisions/20211105-have-an-webxr-version-of-v-sekai.html#derivative-license",
-    "href": "decisions/20211105-have-an-webxr-version-of-v-sekai.html#derivative-license",
-    "title": "Rejected: Have an WebXR version of V-Sekai that is more accessible",
+    "objectID": "decisions/20230508-novel-3d-views.html#context-and-problem-statement",
+    "href": "decisions/20230508-novel-3d-views.html#context-and-problem-statement",
+    "title": "Draft: Convert segmented front facing 3D Garment images to novel 3d views for 3d modeling",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "We want to create 3D models from a front-shot of the garment."
   },
   {
-    "objectID": "decisions/20220820-bake alembic-anim-via-blender.html",
-    "href": "decisions/20220820-bake alembic-anim-via-blender.html",
-    "title": "Proposed: Bake alembic imports by running blender script.",
+    "objectID": "decisions/20230508-novel-3d-views.html#proposed-solution",
+    "href": "decisions/20230508-novel-3d-views.html#proposed-solution",
+    "title": "Draft: Convert segmented front facing 3D Garment images to novel 3d views for 3d modeling",
     "section": "",
-    "text": "Proposed: Bake alembic imports by running blender script.\n\nContext and Problem Statement\nWant to bake alembic imports to gltf blend shapes.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nWe run a python script in Blender to bake alembic inputs to gltf2.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\n# MIT LICENSE\n# Authored by iFire#6518 and alexfreyre#1663\n# This code ONLY apply to a mesh and simulations with ONLY the same vertex number\n\nimport bpy\n\n#Converts a MeshCache or Cloth modifiers to ShapeKeys\nframe = bpy.context.scene.frame_start\nfor frame in range(bpy.context.scene.frame_end + 1):\n    bpy.context.scene.frame_current = frame\n\n    # For alembic files converted to MDD and loaded as MeshCache.\n    bpy.ops.object.modifier_apply_as_shapekey(keep_modifier=True, modifier=\"MeshCache\")\n\n    # For cloth simulations inside blender using a Cloth modifier.\n    #bpy.ops.object.modifier_apply_as_shapekey(keep_modifier=True, modifier=\"Cloth\")\n\n# Loop through shapekeys and add as keyframe per frame.\n# https://blender.stackexchange.com/q/149045/87258\nframe = bpy.context.scene.frame_start\nfor frame in range(bpy.context.scene.frame_end + 1):\n    bpy.context.scene.frame_current = frame\n\n    for shapekey in bpy.data.shape_keys:\n        for i, keyblock in enumerate(shapekey.key_blocks):\n            if keyblock.name != \"Basis\":\n                curr = i - 1\n                if curr != frame:\n                    keyblock.value = 0\n                    keyblock.keyframe_insert(\"value\", frame=frame)\n                else:\n                    keyblock.value = 1\n                    keyblock.keyframe_insert(\"value\", frame=frame)\n\n# bpy.ops.object.modifier_remove(modifier=\"MeshCache\")\n# bpy.ops.object.modifier_remove(modifier=\"Cloth\")\nDo not use the pc2 vertex cache format because of mesh accuracy loss.\n\n\nPositive Consequences\nCan convert alembic to gltf2 for better interoperability.\n\n\nNegative Consequences\nBlend shapes are big.\n\n\nOption graveyard\nOption: Don’t convert.\nThis loses the animation.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot a few lines of script.\n\n\nIs there a reason why this should be core and done by us?\nWe already made a solution.\n\n\nReferences\n\nV-Sekai\n\n\n\nLicense of the contribution\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Use Meta’s image segmentation model and zero123’s 3D reconstruction algorithm to generate novel 3D views of garments from a single front-shot image."
   },
   {
-    "objectID": "decisions/20211005-improve-meshing-results-by-subdivision-in-godot-engine.html",
-    "href": "decisions/20211005-improve-meshing-results-by-subdivision-in-godot-engine.html",
-    "title": "Proposed: Improve Meshing Results by Subdivision in Godot Engine",
+    "objectID": "decisions/20230508-novel-3d-views.html#implementation",
+    "href": "decisions/20230508-novel-3d-views.html#implementation",
+    "title": "Draft: Convert segmented front facing 3D Garment images to novel 3d views for 3d modeling",
     "section": "",
-    "text": "For characters subdivision surfaces allow the ability to conserve authoring while also scaling polygons.\n\n\n\nUsing subdivision surfaces in Godot is useful.\n\n\n\n\nImplement subdivision\nIs the UI based on LOD multiples?\n\n\n\n\nNot a few lines of code.\n\n\n\nCan be done by other people.\n\n\n\n\nhttps://github.com/V-Sekai/godot/tree/subdivision\nhttps://github.com/godotengine/godot-proposals/issues/784\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Preprocess the input image: Resize and normalize the input image to meet the requirements of Meta’s image segmentation model.\nExtract the garment using Meta’s image segmentation model:\n\nLoad the pre-trained Meta’s image segmentation model.\nPass the preprocessed input image through the model to obtain the segmented garment image.\n\nPrepare the segmented garment for 3D reconstruction:\n\nLoad segmented garment image into zero123’s 3D novel view algorithm.\n\nApply zero123’s 3D reconstruction algorithm:\n\nLoad the pre-trained zero123’s 3D reconstruction model.\nPass the prepared segmented garment image through the model to generate novel 3d views of the garment.\n\nGenerate novel 3D views of the garment:\n\nRotate the 3D camera at intervals of 20 degrees around the garment to capture multiple 3D views.\n\nManually model the garment using views:\n\nUse a 3d design tool like Blender to create a mesh."
   },
   {
-    "objectID": "decisions/20211005-improve-meshing-results-by-subdivision-in-godot-engine.html#context-and-problem-statement",
-    "href": "decisions/20211005-improve-meshing-results-by-subdivision-in-godot-engine.html#context-and-problem-statement",
-    "title": "Proposed: Improve Meshing Results by Subdivision in Godot Engine",
+    "objectID": "decisions/20230508-novel-3d-views.html#positive-consequences",
+    "href": "decisions/20230508-novel-3d-views.html#positive-consequences",
+    "title": "Draft: Convert segmented front facing 3D Garment images to novel 3d views for 3d modeling",
     "section": "",
-    "text": "For characters subdivision surfaces allow the ability to conserve authoring while also scaling polygons."
+    "text": "Enhanced user experience with realistic 3D garment previews.\nImproved understanding of garment fit and style.\nIncreased creator satisfaction."
   },
   {
-    "objectID": "decisions/20211005-improve-meshing-results-by-subdivision-in-godot-engine.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20211005-improve-meshing-results-by-subdivision-in-godot-engine.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: Improve Meshing Results by Subdivision in Godot Engine",
+    "objectID": "decisions/20230508-novel-3d-views.html#negative-consequences",
+    "href": "decisions/20230508-novel-3d-views.html#negative-consequences",
+    "title": "Draft: Convert segmented front facing 3D Garment images to novel 3d views for 3d modeling",
     "section": "",
-    "text": "Using subdivision surfaces in Godot is useful."
+    "text": "Potential increase in computational resources required for processing.\nPossible limitations in accuracy and quality of generated 3D models."
   },
   {
-    "objectID": "decisions/20211005-improve-meshing-results-by-subdivision-in-godot-engine.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20211005-improve-meshing-results-by-subdivision-in-godot-engine.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Improve Meshing Results by Subdivision in Godot Engine",
+    "objectID": "decisions/20230508-novel-3d-views.html#option-graveyard",
+    "href": "decisions/20230508-novel-3d-views.html#option-graveyard",
+    "title": "Draft: Convert segmented front facing 3D Garment images to novel 3d views for 3d modeling",
     "section": "",
-    "text": "Implement subdivision\nIs the UI based on LOD multiples?"
+    "text": "Using multiple images for 3D reconstruction (discarded due to not enough aligned input images for 3D construction)."
   },
   {
-    "objectID": "decisions/20211005-improve-meshing-results-by-subdivision-in-godot-engine.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20211005-improve-meshing-results-by-subdivision-in-godot-engine.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Improve Meshing Results by Subdivision in Godot Engine",
+    "objectID": "decisions/20230508-novel-3d-views.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230508-novel-3d-views.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Draft: Convert segmented front facing 3D Garment images to novel 3d views for 3d modeling",
     "section": "",
-    "text": "Not a few lines of code."
+    "text": "No, this enhancement requires integration of advanced image segmentation and 3D reconstruction algorithms, which cannot be achieved with a simple script."
   },
   {
-    "objectID": "decisions/20211005-improve-meshing-results-by-subdivision-in-godot-engine.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20211005-improve-meshing-results-by-subdivision-in-godot-engine.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Improve Meshing Results by Subdivision in Godot Engine",
+    "objectID": "decisions/20230508-novel-3d-views.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230508-novel-3d-views.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Draft: Convert segmented front facing 3D Garment images to novel 3d views for 3d modeling",
     "section": "",
-    "text": "Can be done by other people."
+    "text": "Yes, implementing this feature as part of our core project will improve our opensource community of creators."
   },
   {
-    "objectID": "decisions/20211005-improve-meshing-results-by-subdivision-in-godot-engine.html#references",
-    "href": "decisions/20211005-improve-meshing-results-by-subdivision-in-godot-engine.html#references",
-    "title": "Proposed: Improve Meshing Results by Subdivision in Godot Engine",
+    "objectID": "decisions/20230508-novel-3d-views.html#references",
+    "href": "decisions/20230508-novel-3d-views.html#references",
+    "title": "Draft: Convert segmented front facing 3D Garment images to novel 3d views for 3d modeling",
     "section": "",
-    "text": "https://github.com/V-Sekai/godot/tree/subdivision\nhttps://github.com/godotengine/godot-proposals/issues/784"
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20211005-improve-meshing-results-by-subdivision-in-godot-engine.html#derivative-license",
-    "href": "decisions/20211005-improve-meshing-results-by-subdivision-in-godot-engine.html#derivative-license",
-    "title": "Proposed: Improve Meshing Results by Subdivision in Godot Engine",
+    "objectID": "decisions/20211031-godot-database-viewer-for-proposals.html",
+    "href": "decisions/20211031-godot-database-viewer-for-proposals.html",
+    "title": "Proposed: Godot Database viewer for proposals",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "[Describe the problem or limitation you are having in your project]\n[Describe the context and problem statement, e.g., in free form using two to three sentences. You may want to articulate the problem in the form of a question.]\n\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\n\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\n\n\n\n\n[e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]\n[…]\n\n\n\n\n\n[e.g., compromising quality attribute, follow-up decisions required, …]\n[…]\n\n[this section can be repeated for each option if more than one option is open for consideration]\n\n\n\n\nOption: \nRejection Reason: \n\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\n\n\n\nIs there a reason why this should be core and done by us?\n\n\n\n\nLink type \n… \n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240218-vrm-substance-editor.html",
-    "href": "decisions/20240218-vrm-substance-editor.html",
-    "title": "Proposed VRM mtoon in Substance Designer",
+    "objectID": "decisions/20211031-godot-database-viewer-for-proposals.html#context-and-problem-statement",
+    "href": "decisions/20211031-godot-database-viewer-for-proposals.html#context-and-problem-statement",
+    "title": "Proposed: Godot Database viewer for proposals",
     "section": "",
-    "text": "VRM is a file format for handling 3D humanoid avatars in VR applications. It’s designed to be a versatile and exchangeable format across various systems. mtoon is a toon shader used with VRM models to give them a distinct, stylized look that emulates 2D animation within a 3D space.\nSubstance Designer is a powerful node-based texturing tool essential for creating realistic textures for 3D models. By implementing mtoon support in Substance Designer, we can bridge the gap between high-quality texture design and VRM character customization.\n\n\n\nThe current workflow for applying toon shading to VRM models is disconnected from the process of designing textures, often requiring multiple tools and manual adjustments. We aim to simplify the workflow by integrating mtoon support directly into Substance Designer, allowing for a more cohesive and efficient design process.\n\n\n\nThe implementation would involve developing a custom Substance Designer node set or a template that encapsulates mtoon’s parameters and replicates its shading model within the Substance Designer environment. This would allow artists to preview and tweak the toon shader settings in real-time while crafting the textures.\nA mock-up interface would present these parameters within Substance Designer, where each one directly corresponds to a property in the VRM mtoon shader.\n\n\n\n\nStreamlined Workflow: Artists can create and adjust VRM textures and toon shaders all within Substance Designer.\nReal-time Previews: Immediate feedback on how changes to textures and shader parameters impact the final appearance.\nConsistency: Reduces discrepancies between the design phase and the final rendering in VR applications.\n\n\n\n\n\nDevelopment Time: Significant time investment required to develop and maintain the custom node set/template.\nComplexity: Adds an additional layer of complexity within Substance Designer, which could be overwhelming for new users.\nNiche Audience: The feature might only cater to a relatively small audience of VRM content creators.\n\n\n\n\nWe could have chosen to maintain the status quo, requiring VRM creators to switch between multiple tools to finalize their avatar’s appearance. However, this would prolong the existing inefficiencies in the production pipeline.\n\n\n\nWhile most VRM mtoon use cases involve common elements like lit colors and normal maps, less frequent use cases could involve highly custom properties such as UV animations or unique rim lighting effects.\n\n\n\nThe development of this feature would be in-house, ensuring deep integration with existing Substance Designer systems and full control over the implementation and updates.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team and community stakeholders.\n\n\n\n\n\nV-Sekai, Avatar Customization, AI, Facial Expressions\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article.\nBelow is a table of parameters for the proposed VRM mtoon Substance Designer node set/template:\n\n\n\n\n\n\n\n\n\n\n\nRank\nParameter\nType\nDescription\nImpact Level\nRange\n\n\n\n\n1\n_Color\nvec4\nLit Color, Alpha (Lit RGB, Alpha A)\nHigh\n[0, 1]\n\n\n2\n_MainTex\ntexture\nMain Texture (RGB)\nHigh\n[0, 1]\n\n\n3\n_ShadeColor\nvec4\nShade Color (Shade RGB)\nHigh\n[0, 1]\n\n\n4\n_ShadeTexture\ntexture\nShade Texture (RGB)\nHigh\n[0, 1]\n\n\n5\n_ShadeToony\nfloat\nShading Toony (0.0 is Lambert. Higher value get toony shading.)\nHigh\n[0.0, 1.0]\n\n\n6\n_RimColor\nvec4\nRim Color (RGB)\nHigh\n[0, 1]\n\n\n7\n_RimTexture\ntexture\nRim Texture (RGB)\nHigh\n[0, 1]\n\n\n8\n_EmissionColor\nvec4\nEmission Color (RGB)\nHigh\n[0, 1]\n\n\n9\n_EmissionMap\ntexture\nEmission Map (RGB)\nHigh\n[0, 1]\n\n\n10\n_Cutoff\nfloat\nAlpha Cutoff (Discard pixels below this value in Cutout mode)\nHigh\n[0.0, 1.0]\n\n\n11\n_AlphaCutoutEnable\nint\nRendering Type (TransparentWithZWrite mode can cause problems with rendering.)\nHigh\n{0, 1}\n\n\n12\n_MainTex_ST\nvec4\nUV Offset (UV Scale X,Y, UV Offset X,Y)\nHigh\n[0, 1]\n\n\n13\n_BumpScale\nvec2\nNormal Map and Multiplier for normals in tangent space\nHigh\n[0.0, 1.0]\n\n\n14\n_BumpMap\ntexture\nNormal Map (RGB)\nHigh\n[0, 1]\n\n\n15\n_OutlineWidth\nfloat\nWidth (Outline Width)\nHigh\n[0.01, ∞)\n\n\n16\n_OutlineWidthTexture\ntexture\nOutline Width Texture (R)\nHigh\n[0, 1]\n\n\n17\n_OutlineColor\nvec4\nOutline Color (RGB)\nHigh\n[0, 1]\n\n\n18\n_SphereAdd\ntexture\nMatCap Texture (RGB)\nSubtle\n[0, 1]\n\n\n19\n_ShadeShift\nfloat\nShading Shift (Zero is Default. Negative value increase lit area. Positive value increase shade area.)\nModerate\n[-1.0, ∞)\n\n\n20\n_ReceiveShadowRate\nfloat\nShadow Receive (Texture R * Rate. White is Default. Black attenuates shadows.)\nModerate\n[0.0, 1.0]\n\n\n21\n_ReceiveShadowTexture\ntexture\nReceive Shadow Texture (R)\nModerate\n[0, 1]\n\n\n22\n_ShadingGradeRate\nfloat\nShading Grade (Lit & Shade Mixing Multiplier: Texture R * Rate. Compatible with UTS2 ShadingGradeMap. White is Default. Black amplifies shade.)\nModerate\n[0.0, 1.0]\n\n\n23\n_ShadingGradeTexture\ntexture\nShading Grade Texture (R)\nModerate\n[0, 1]\n\n\n24\n_LightColorAttenuation\nfloat\nLight Color Attenuation\nModerate\n[0.0, ∞)\n\n\n25\n_IndirectLightIntensity\nfloat\nGI Intensity (Indirect Light Intensity)\nModerate\n[0.0, ∞)\n\n\n26\n_MatcapColor\nvec4\nMatCap Color (Color multiplied with Additive Sphere map / MatCap Texture RGB)\nSubtle\n[0, 1]\n\n\n27\n_RimLightingMix\nfloat\nRim Lighting Mix\nSubtle\n[0.0, 1.0]\n\n\n28\n_RimFresnelPower\nfloat\nFresnel Power (If you increase this value, you get sharper rim light.)\nSubtle\n[0.0, 100.0]\n\n\n29\n_RimLift\nfloat\nRim Lift (If you increase this value, you can lift rim light.)\nSubtle\n[0.0, ∞)\n\n\n30\n_OutlineWidthMode\nint\nMode (None = outline pass disabled; World = outline in world coordinates; Screen = screen pixel thickness)\nOutline-Specific\n{0, 1, 2}\n\n\n31\n_OutlineScaledMaxDistance\nfloat\nOutline Scaled Distance (Width Scaled Max Distance)\nOutline-Specific\n[1.0, 10.0]\n\n\n32\n_OutlineColorMode\nint\nColor Mode (FixedColor = unshaded; MixedLighting = match environment light (recommended))\nOutline-Specific\n{0, 1}\n\n\n33\n_OutlineLightingMix\nfloat\nOutline Mix (Outline Lighting Mix)\nOutline-Specific\n[0.0, 1.0]\n\n\n34\n_UvAnimMaskTexture\ntexture\nAuto Animation Mask Texture (R)\nUV Animation\n[0, 1]\n\n\n35\n_UvAnimScrollX\nfloat\nUV Scroll X (per second)\nUV Animation\n[-100.0, 100.0]\n\n\n36\n_UvAnimScrollY\nfloat\nUV Scroll Y (per second)\nUV Animation\n[-100.0, 100.0]\n\n\n37\n_UvAnimRotation\nfloat\nUV Rotation (per second)\nUV Animation\n[-100.0, 100.0]\n\n\n38\n_DebugMode\nint\nVisualize (Debugging Visualization: Normal or Lighting)\nDebugging\n{0, 1, 2}"
+    "text": "[Describe the problem or limitation you are having in your project]\n[Describe the context and problem statement, e.g., in free form using two to three sentences. You may want to articulate the problem in the form of a question.]"
   },
   {
-    "objectID": "decisions/20240218-vrm-substance-editor.html#the-context",
-    "href": "decisions/20240218-vrm-substance-editor.html#the-context",
-    "title": "Proposed VRM mtoon in Substance Designer",
+    "objectID": "decisions/20211031-godot-database-viewer-for-proposals.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20211031-godot-database-viewer-for-proposals.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: Godot Database viewer for proposals",
     "section": "",
-    "text": "VRM is a file format for handling 3D humanoid avatars in VR applications. It’s designed to be a versatile and exchangeable format across various systems. mtoon is a toon shader used with VRM models to give them a distinct, stylized look that emulates 2D animation within a 3D space.\nSubstance Designer is a powerful node-based texturing tool essential for creating realistic textures for 3D models. By implementing mtoon support in Substance Designer, we can bridge the gap between high-quality texture design and VRM character customization."
+    "text": "Describe the proposed option and how it helps to overcome the problem or limitation"
   },
   {
-    "objectID": "decisions/20240218-vrm-substance-editor.html#the-problem-statement",
-    "href": "decisions/20240218-vrm-substance-editor.html#the-problem-statement",
-    "title": "Proposed VRM mtoon in Substance Designer",
+    "objectID": "decisions/20211031-godot-database-viewer-for-proposals.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20211031-godot-database-viewer-for-proposals.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Godot Database viewer for proposals",
     "section": "",
-    "text": "The current workflow for applying toon shading to VRM models is disconnected from the process of designing textures, often requiring multiple tools and manual adjustments. We aim to simplify the workflow by integrating mtoon support directly into Substance Designer, allowing for a more cohesive and efficient design process."
+    "text": "Describe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams"
   },
   {
-    "objectID": "decisions/20240218-vrm-substance-editor.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240218-vrm-substance-editor.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed VRM mtoon in Substance Designer",
+    "objectID": "decisions/20211031-godot-database-viewer-for-proposals.html#positive-consequences",
+    "href": "decisions/20211031-godot-database-viewer-for-proposals.html#positive-consequences",
+    "title": "Proposed: Godot Database viewer for proposals",
     "section": "",
-    "text": "The implementation would involve developing a custom Substance Designer node set or a template that encapsulates mtoon’s parameters and replicates its shading model within the Substance Designer environment. This would allow artists to preview and tweak the toon shader settings in real-time while crafting the textures.\nA mock-up interface would present these parameters within Substance Designer, where each one directly corresponds to a property in the VRM mtoon shader."
+    "text": "[e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]\n[…]"
   },
   {
-    "objectID": "decisions/20240218-vrm-substance-editor.html#the-benefits",
-    "href": "decisions/20240218-vrm-substance-editor.html#the-benefits",
-    "title": "Proposed VRM mtoon in Substance Designer",
+    "objectID": "decisions/20211031-godot-database-viewer-for-proposals.html#negative-consequences",
+    "href": "decisions/20211031-godot-database-viewer-for-proposals.html#negative-consequences",
+    "title": "Proposed: Godot Database viewer for proposals",
     "section": "",
-    "text": "Streamlined Workflow: Artists can create and adjust VRM textures and toon shaders all within Substance Designer.\nReal-time Previews: Immediate feedback on how changes to textures and shader parameters impact the final appearance.\nConsistency: Reduces discrepancies between the design phase and the final rendering in VR applications."
+    "text": "[e.g., compromising quality attribute, follow-up decisions required, …]\n[…]\n\n[this section can be repeated for each option if more than one option is open for consideration]"
   },
   {
-    "objectID": "decisions/20240218-vrm-substance-editor.html#the-downsides",
-    "href": "decisions/20240218-vrm-substance-editor.html#the-downsides",
-    "title": "Proposed VRM mtoon in Substance Designer",
+    "objectID": "decisions/20211031-godot-database-viewer-for-proposals.html#option-graveyard",
+    "href": "decisions/20211031-godot-database-viewer-for-proposals.html#option-graveyard",
+    "title": "Proposed: Godot Database viewer for proposals",
     "section": "",
-    "text": "Development Time: Significant time investment required to develop and maintain the custom node set/template.\nComplexity: Adds an additional layer of complexity within Substance Designer, which could be overwhelming for new users.\nNiche Audience: The feature might only cater to a relatively small audience of VRM content creators."
+    "text": "Option: \nRejection Reason:"
   },
   {
-    "objectID": "decisions/20240218-vrm-substance-editor.html#the-road-not-taken",
-    "href": "decisions/20240218-vrm-substance-editor.html#the-road-not-taken",
-    "title": "Proposed VRM mtoon in Substance Designer",
+    "objectID": "decisions/20211031-godot-database-viewer-for-proposals.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20211031-godot-database-viewer-for-proposals.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Godot Database viewer for proposals",
     "section": "",
-    "text": "We could have chosen to maintain the status quo, requiring VRM creators to switch between multiple tools to finalize their avatar’s appearance. However, this would prolong the existing inefficiencies in the production pipeline."
+    "text": "If this enhancement will not be used often, can it be worked around with a few lines of script?"
   },
   {
-    "objectID": "decisions/20240218-vrm-substance-editor.html#the-infrequent-use-case",
-    "href": "decisions/20240218-vrm-substance-editor.html#the-infrequent-use-case",
-    "title": "Proposed VRM mtoon in Substance Designer",
+    "objectID": "decisions/20211031-godot-database-viewer-for-proposals.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20211031-godot-database-viewer-for-proposals.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Godot Database viewer for proposals",
     "section": "",
-    "text": "While most VRM mtoon use cases involve common elements like lit colors and normal maps, less frequent use cases could involve highly custom properties such as UV animations or unique rim lighting effects."
+    "text": "Is there a reason why this should be core and done by us?"
   },
   {
-    "objectID": "decisions/20240218-vrm-substance-editor.html#in-core-and-done-by-us",
-    "href": "decisions/20240218-vrm-substance-editor.html#in-core-and-done-by-us",
-    "title": "Proposed VRM mtoon in Substance Designer",
+    "objectID": "decisions/20211031-godot-database-viewer-for-proposals.html#references",
+    "href": "decisions/20211031-godot-database-viewer-for-proposals.html#references",
+    "title": "Proposed: Godot Database viewer for proposals",
     "section": "",
-    "text": "The development of this feature would be in-house, ensuring deep integration with existing Substance Designer systems and full control over the implementation and updates."
+    "text": "Link type \n…"
   },
   {
-    "objectID": "decisions/20240218-vrm-substance-editor.html#status",
-    "href": "decisions/20240218-vrm-substance-editor.html#status",
-    "title": "Proposed VRM mtoon in Substance Designer",
+    "objectID": "decisions/20211031-godot-database-viewer-for-proposals.html#derivative-license",
+    "href": "decisions/20211031-godot-database-viewer-for-proposals.html#derivative-license",
+    "title": "Proposed: Godot Database viewer for proposals",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240218-vrm-substance-editor.html#decision-makers",
-    "href": "decisions/20240218-vrm-substance-editor.html#decision-makers",
-    "title": "Proposed VRM mtoon in Substance Designer",
+    "objectID": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html",
+    "href": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html",
+    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Silverblue and #steam",
     "section": "",
-    "text": "V-Sekai development team and community stakeholders."
+    "text": "Status: rejected \nDeciders: V-Sekai,fire,\nTags: V-Sekai,\n\n\n\nI don’t have a #steam Deck since it was delayed til February 2022 to test V-Sekai.\n\n\n\nInstall Fedora Kinoite and Steam.\n\n\n\n\nInstall Ventoy on a USB Stick\nInstall iso of Fedora Silverblue onto the drive on Ventoy\nInstall Fedora Silverblue onto hardware proxy defined in another proposal.\nInstall #steam via RPMFusion\n\n\n\n\n\nAble to test builds from Windows?\n\n\n\n\n\nUnknown\n\n\n\n\n\nOption: Use Arch Manjaro\nRejection Reason: Unfamiliar with OS.\nOption: Use Arch Manjaro\nRejection Reason: Unfamiliar with OS.\n\n\n\n\nNot lines of code.\n\n\n\nQA testing needs to be inhouse.\n\n\n\n\nhttps://en.wikipedia.org/wiki/Steam_Deck\nhttps://download.fedoraproject.org/pub/fedora/linux/releases/35/Kinoite/x86_64/iso/Fedora-Kinoite-ostree-x86_64-35-1.2.iso\n\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240218-vrm-substance-editor.html#tags",
-    "href": "decisions/20240218-vrm-substance-editor.html#tags",
-    "title": "Proposed VRM mtoon in Substance Designer",
+    "objectID": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html#context-and-problem-statement",
+    "href": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html#context-and-problem-statement",
+    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Silverblue and #steam",
     "section": "",
-    "text": "V-Sekai, Avatar Customization, AI, Facial Expressions"
+    "text": "I don’t have a #steam Deck since it was delayed til February 2022 to test V-Sekai."
   },
   {
-    "objectID": "decisions/20240218-vrm-substance-editor.html#further-reading",
-    "href": "decisions/20240218-vrm-substance-editor.html#further-reading",
-    "title": "Proposed VRM mtoon in Substance Designer",
+    "objectID": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Silverblue and #steam",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article.\nBelow is a table of parameters for the proposed VRM mtoon Substance Designer node set/template:\n\n\n\n\n\n\n\n\n\n\n\nRank\nParameter\nType\nDescription\nImpact Level\nRange\n\n\n\n\n1\n_Color\nvec4\nLit Color, Alpha (Lit RGB, Alpha A)\nHigh\n[0, 1]\n\n\n2\n_MainTex\ntexture\nMain Texture (RGB)\nHigh\n[0, 1]\n\n\n3\n_ShadeColor\nvec4\nShade Color (Shade RGB)\nHigh\n[0, 1]\n\n\n4\n_ShadeTexture\ntexture\nShade Texture (RGB)\nHigh\n[0, 1]\n\n\n5\n_ShadeToony\nfloat\nShading Toony (0.0 is Lambert. Higher value get toony shading.)\nHigh\n[0.0, 1.0]\n\n\n6\n_RimColor\nvec4\nRim Color (RGB)\nHigh\n[0, 1]\n\n\n7\n_RimTexture\ntexture\nRim Texture (RGB)\nHigh\n[0, 1]\n\n\n8\n_EmissionColor\nvec4\nEmission Color (RGB)\nHigh\n[0, 1]\n\n\n9\n_EmissionMap\ntexture\nEmission Map (RGB)\nHigh\n[0, 1]\n\n\n10\n_Cutoff\nfloat\nAlpha Cutoff (Discard pixels below this value in Cutout mode)\nHigh\n[0.0, 1.0]\n\n\n11\n_AlphaCutoutEnable\nint\nRendering Type (TransparentWithZWrite mode can cause problems with rendering.)\nHigh\n{0, 1}\n\n\n12\n_MainTex_ST\nvec4\nUV Offset (UV Scale X,Y, UV Offset X,Y)\nHigh\n[0, 1]\n\n\n13\n_BumpScale\nvec2\nNormal Map and Multiplier for normals in tangent space\nHigh\n[0.0, 1.0]\n\n\n14\n_BumpMap\ntexture\nNormal Map (RGB)\nHigh\n[0, 1]\n\n\n15\n_OutlineWidth\nfloat\nWidth (Outline Width)\nHigh\n[0.01, ∞)\n\n\n16\n_OutlineWidthTexture\ntexture\nOutline Width Texture (R)\nHigh\n[0, 1]\n\n\n17\n_OutlineColor\nvec4\nOutline Color (RGB)\nHigh\n[0, 1]\n\n\n18\n_SphereAdd\ntexture\nMatCap Texture (RGB)\nSubtle\n[0, 1]\n\n\n19\n_ShadeShift\nfloat\nShading Shift (Zero is Default. Negative value increase lit area. Positive value increase shade area.)\nModerate\n[-1.0, ∞)\n\n\n20\n_ReceiveShadowRate\nfloat\nShadow Receive (Texture R * Rate. White is Default. Black attenuates shadows.)\nModerate\n[0.0, 1.0]\n\n\n21\n_ReceiveShadowTexture\ntexture\nReceive Shadow Texture (R)\nModerate\n[0, 1]\n\n\n22\n_ShadingGradeRate\nfloat\nShading Grade (Lit & Shade Mixing Multiplier: Texture R * Rate. Compatible with UTS2 ShadingGradeMap. White is Default. Black amplifies shade.)\nModerate\n[0.0, 1.0]\n\n\n23\n_ShadingGradeTexture\ntexture\nShading Grade Texture (R)\nModerate\n[0, 1]\n\n\n24\n_LightColorAttenuation\nfloat\nLight Color Attenuation\nModerate\n[0.0, ∞)\n\n\n25\n_IndirectLightIntensity\nfloat\nGI Intensity (Indirect Light Intensity)\nModerate\n[0.0, ∞)\n\n\n26\n_MatcapColor\nvec4\nMatCap Color (Color multiplied with Additive Sphere map / MatCap Texture RGB)\nSubtle\n[0, 1]\n\n\n27\n_RimLightingMix\nfloat\nRim Lighting Mix\nSubtle\n[0.0, 1.0]\n\n\n28\n_RimFresnelPower\nfloat\nFresnel Power (If you increase this value, you get sharper rim light.)\nSubtle\n[0.0, 100.0]\n\n\n29\n_RimLift\nfloat\nRim Lift (If you increase this value, you can lift rim light.)\nSubtle\n[0.0, ∞)\n\n\n30\n_OutlineWidthMode\nint\nMode (None = outline pass disabled; World = outline in world coordinates; Screen = screen pixel thickness)\nOutline-Specific\n{0, 1, 2}\n\n\n31\n_OutlineScaledMaxDistance\nfloat\nOutline Scaled Distance (Width Scaled Max Distance)\nOutline-Specific\n[1.0, 10.0]\n\n\n32\n_OutlineColorMode\nint\nColor Mode (FixedColor = unshaded; MixedLighting = match environment light (recommended))\nOutline-Specific\n{0, 1}\n\n\n33\n_OutlineLightingMix\nfloat\nOutline Mix (Outline Lighting Mix)\nOutline-Specific\n[0.0, 1.0]\n\n\n34\n_UvAnimMaskTexture\ntexture\nAuto Animation Mask Texture (R)\nUV Animation\n[0, 1]\n\n\n35\n_UvAnimScrollX\nfloat\nUV Scroll X (per second)\nUV Animation\n[-100.0, 100.0]\n\n\n36\n_UvAnimScrollY\nfloat\nUV Scroll Y (per second)\nUV Animation\n[-100.0, 100.0]\n\n\n37\n_UvAnimRotation\nfloat\nUV Rotation (per second)\nUV Animation\n[-100.0, 100.0]\n\n\n38\n_DebugMode\nint\nVisualize (Debugging Visualization: Normal or Lighting)\nDebugging\n{0, 1, 2}"
+    "text": "Install Fedora Kinoite and Steam."
   },
   {
-    "objectID": "decisions/20231105-pdf-embed-raster-svg-vr.html",
-    "href": "decisions/20231105-pdf-embed-raster-svg-vr.html",
-    "title": "Proposed: PDF to SVG Conversion for VR Books",
+    "objectID": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Silverblue and #steam",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nThe idea of converting PDFs to SVGs with raster image embeds for use in a VR book reader is an exciting project. However, dealing with PDF conversion can be challenging, especially when it comes to more complex tasks.\n\n\n\nThe main challenge lies in the conversion process from PDF to SVG while maintaining the quality and integrity of the original content. This includes handling raster embeds and ensuring they are correctly displayed in the Godot engine.\n\n\n\nThe proposed workflow involves taking a PDF page with potential raster embeds, running it through svgcleaner, and then using it in the Godot engine. The goal is to create a CBZ where the images are SVGs.\n\n\n\nThis approach allows for the creation of high-quality, interactive VR books. It also leverages the capabilities of the Godot engine, which supports SVG, PNG, and JPG embeds.\n\n\n\nThe complexity of the conversion process may present some challenges. Additionally, the quality of the final product will heavily depend on the quality of the original PDF and its embedded raster images.\n\n\n\nAn alternative approach could involve converting the PDF to another format that might be easier to work with. However, this would likely result in a loss of quality and may not support the desired interactivity.\n\n\n\nThis workflow may not be suitable for all types of PDFs, particularly those with complex layouts or numerous embedded images.\n\n\n\nThe implementation of this workflow would require a deep understanding of both the PDF and SVG formats, as well as the Godot engine. It would likely be a significant undertaking.\n\n\n\n\nV-Sekai\n\nThis article was assisted by AI."
+    "text": "Install Ventoy on a USB Stick\nInstall iso of Fedora Silverblue onto the drive on Ventoy\nInstall Fedora Silverblue onto hardware proxy defined in another proposal.\nInstall #steam via RPMFusion"
   },
   {
-    "objectID": "decisions/20231105-pdf-embed-raster-svg-vr.html#metadata",
-    "href": "decisions/20231105-pdf-embed-raster-svg-vr.html#metadata",
-    "title": "Proposed: PDF to SVG Conversion for VR Books",
+    "objectID": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html#positive-consequences",
+    "href": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html#positive-consequences",
+    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Silverblue and #steam",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai"
+    "text": "Able to test builds from Windows?"
   },
   {
-    "objectID": "decisions/20231105-pdf-embed-raster-svg-vr.html#the-backdrop",
-    "href": "decisions/20231105-pdf-embed-raster-svg-vr.html#the-backdrop",
-    "title": "Proposed: PDF to SVG Conversion for VR Books",
+    "objectID": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html#negative-consequences",
+    "href": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html#negative-consequences",
+    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Silverblue and #steam",
     "section": "",
-    "text": "The idea of converting PDFs to SVGs with raster image embeds for use in a VR book reader is an exciting project. However, dealing with PDF conversion can be challenging, especially when it comes to more complex tasks."
+    "text": "Unknown"
   },
   {
-    "objectID": "decisions/20231105-pdf-embed-raster-svg-vr.html#the-challenge",
-    "href": "decisions/20231105-pdf-embed-raster-svg-vr.html#the-challenge",
-    "title": "Proposed: PDF to SVG Conversion for VR Books",
+    "objectID": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html#option-graveyard",
+    "href": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html#option-graveyard",
+    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Silverblue and #steam",
     "section": "",
-    "text": "The main challenge lies in the conversion process from PDF to SVG while maintaining the quality and integrity of the original content. This includes handling raster embeds and ensuring they are correctly displayed in the Godot engine."
+    "text": "Option: Use Arch Manjaro\nRejection Reason: Unfamiliar with OS.\nOption: Use Arch Manjaro\nRejection Reason: Unfamiliar with OS."
   },
   {
-    "objectID": "decisions/20231105-pdf-embed-raster-svg-vr.html#the-strategy",
-    "href": "decisions/20231105-pdf-embed-raster-svg-vr.html#the-strategy",
-    "title": "Proposed: PDF to SVG Conversion for VR Books",
+    "objectID": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Silverblue and #steam",
     "section": "",
-    "text": "The proposed workflow involves taking a PDF page with potential raster embeds, running it through svgcleaner, and then using it in the Godot engine. The goal is to create a CBZ where the images are SVGs."
+    "text": "Not lines of code."
   },
   {
-    "objectID": "decisions/20231105-pdf-embed-raster-svg-vr.html#the-upside",
-    "href": "decisions/20231105-pdf-embed-raster-svg-vr.html#the-upside",
-    "title": "Proposed: PDF to SVG Conversion for VR Books",
+    "objectID": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Silverblue and #steam",
     "section": "",
-    "text": "This approach allows for the creation of high-quality, interactive VR books. It also leverages the capabilities of the Godot engine, which supports SVG, PNG, and JPG embeds."
+    "text": "QA testing needs to be inhouse."
   },
   {
-    "objectID": "decisions/20231105-pdf-embed-raster-svg-vr.html#the-downside",
-    "href": "decisions/20231105-pdf-embed-raster-svg-vr.html#the-downside",
-    "title": "Proposed: PDF to SVG Conversion for VR Books",
+    "objectID": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html#references",
+    "href": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html#references",
+    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Silverblue and #steam",
     "section": "",
-    "text": "The complexity of the conversion process may present some challenges. Additionally, the quality of the final product will heavily depend on the quality of the original PDF and its embedded raster images."
+    "text": "https://en.wikipedia.org/wiki/Steam_Deck\nhttps://download.fedoraproject.org/pub/fedora/linux/releases/35/Kinoite/x86_64/iso/Fedora-Kinoite-ostree-x86_64-35-1.2.iso"
   },
   {
-    "objectID": "decisions/20231105-pdf-embed-raster-svg-vr.html#the-road-not-taken",
-    "href": "decisions/20231105-pdf-embed-raster-svg-vr.html#the-road-not-taken",
-    "title": "Proposed: PDF to SVG Conversion for VR Books",
+    "objectID": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html#derivative-license",
+    "href": "decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html#derivative-license",
+    "title": "Rejected: Create Steamdeck hardware proxy by installing Fedora Silverblue and #steam",
     "section": "",
-    "text": "An alternative approach could involve converting the PDF to another format that might be easier to work with. However, this would likely result in a loss of quality and may not support the desired interactivity."
+    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20231105-pdf-embed-raster-svg-vr.html#the-infrequent-use-case",
-    "href": "decisions/20231105-pdf-embed-raster-svg-vr.html#the-infrequent-use-case",
-    "title": "Proposed: PDF to SVG Conversion for VR Books",
+    "objectID": "decisions/20211031-character-workshop.html",
+    "href": "decisions/20211031-character-workshop.html",
+    "title": "Proposed: Character workshop",
     "section": "",
-    "text": "This workflow may not be suitable for all types of PDFs, particularly those with complex layouts or numerous embedded images."
+    "text": "Proposed: Character workshop\n\nContext and Problem Statement\nCharacters are hard. Make it easier.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nMake a workshop for working with 3d characters.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nAuto rig a 3d obj.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNo idea.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nI can do this!\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20231105-pdf-embed-raster-svg-vr.html#in-core-and-done-by-us",
-    "href": "decisions/20231105-pdf-embed-raster-svg-vr.html#in-core-and-done-by-us",
-    "title": "Proposed: PDF to SVG Conversion for VR Books",
+    "objectID": "decisions/20231108-munich-godot-engine-conference.html",
+    "href": "decisions/20231108-munich-godot-engine-conference.html",
+    "title": "Proposed: Enhancing V-Sekai Through Effective Documentation",
     "section": "",
-    "text": "The implementation of this workflow would require a deep understanding of both the PDF and SVG formats, as well as the Godot engine. It would likely be a significant undertaking."
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nLyuma, a member of the V-Sekai team, recently attended the Godot Engine Munich 2023 conference. Three key takeaways from the event were the importance of friendship, Gemütlichkeit (a German term for a state of warmth, friendliness, and good cheer), and the critical role of documentation.\n\n\n\nOne of the challenges faced by V-Sekai is ensuring that all processes and systems are well-documented. This is crucial for maintaining consistency, facilitating knowledge transfer, and enabling efficient problem-solving.\n\n\n\nTo overcome this challenge, the strategy is to prioritize documentation in all projects. This involves creating comprehensive guides, manuals, and references that detail how different systems work and how to use them effectively.\n\n\n\nThe upside of this approach is that it can significantly improve the efficiency and effectiveness of the team. With proper documentation, team members can quickly understand and navigate different systems, reducing the time spent on troubleshooting and problem-solving.\n\n\n\nThe downside is that creating and maintaining documentation can be time-consuming. However, the benefits of having well-documented systems far outweigh the costs.\n\n\n\nAn alternative approach could have been to rely on informal knowledge transfer methods, such as one-on-one training or mentoring. However, this approach lacks the consistency and scalability of formal documentation.\n\n\n\nIn cases where systems or processes are rarely used or subject to frequent changes, maintaining up-to-date documentation might be challenging. In such scenarios, a combination of documentation and hands-on training might be more effective.\n\n\n\nThe decision to prioritize documentation is proposed by V-Sekai.\n\n\n\n\nV-Sekai\n\nThis article was assisted by Aria, an AI."
   },
   {
-    "objectID": "decisions/20231105-pdf-embed-raster-svg-vr.html#further-reading",
-    "href": "decisions/20231105-pdf-embed-raster-svg-vr.html#further-reading",
-    "title": "Proposed: PDF to SVG Conversion for VR Books",
+    "objectID": "decisions/20231108-munich-godot-engine-conference.html#metadata",
+    "href": "decisions/20231108-munich-godot-engine-conference.html#metadata",
+    "title": "Proposed: Enhancing V-Sekai Through Effective Documentation",
     "section": "",
-    "text": "V-Sekai\n\nThis article was assisted by AI."
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20231114-elixir-definition-of-godot-types.html",
-    "href": "decisions/20231114-elixir-definition-of-godot-types.html",
-    "title": "Proposed: Defining the List of Godot Types in Elixir Godot Parsers",
+    "objectID": "decisions/20231108-munich-godot-engine-conference.html#the-backdrop",
+    "href": "decisions/20231108-munich-godot-engine-conference.html#the-backdrop",
+    "title": "Proposed: Enhancing V-Sekai Through Effective Documentation",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai Development Team\nTags: Godot Engine, Elixir, Type Definitions, V-Sekai\n\n\n\n\nThe elixir_godot_parsers project under V-Sekai aims to enhance the integration and parsing capabilities between the Elixir programming language and the Godot Engine. A key component of this is understanding and effectively parsing various data types used in Godot.\n\n\n\nCurrently, there may be ambiguities or a lack of clear definition for all Godot types within the elixir_godot_parsers project. This can lead to inconsistencies in parsing and handling data, potentially affecting the efficiency and reliability of the integration.\n\n\n\nPropose the creation of a comprehensive, well-documented list of all Godot types. This list should be detailed and include specifications for each type, ensuring clarity and consistency in how Elixir handles and parses these types.\n\n\n\nDefining a clear list of Godot types will enhance the reliability and functionality of the Elixir-Godot integration. This will make the development process smoother, reduce bugs, and improve the overall efficiency of projects using both Elixir and Godot.\n\n\n\nCompiling and maintaining this list could be time-consuming. It may also require regular updates to stay in sync with any changes or updates in the Godot Engine.\n\n\n\nAn alternative approach could be to continue without a defined list, relying on ad-hoc solutions for each type as needed. However, this could lead to increased development time and potential errors.\n\n\n\nWhile this proposal primarily targets the Elixir-Godot integration, having a well-defined list of types could also be beneficial for other projects or integrations involving the Godot Engine.\n\n\n\nThis task involves direct contributions to the core functionality of the elixir_godot_parsers project under V-Sekai, aiming to enhance its core capabilities in terms of data handling and parsing.\n\n\n\n\nV-Sekai GitHub Repository - The official GitHub account for the V-Sekai development community, focusing on social VR functionality for the Godot Engine.\nElixir Godot Parsers Repository - The GitHub page for the elixir_godot_parsers project, part of V-Sekai’s efforts to integrate Elixir with the Godot Engine.\n\nThis proposal was created with the assistance of AI assistant Aria."
+    "text": "Lyuma, a member of the V-Sekai team, recently attended the Godot Engine Munich 2023 conference. Three key takeaways from the event were the importance of friendship, Gemütlichkeit (a German term for a state of warmth, friendliness, and good cheer), and the critical role of documentation."
   },
   {
-    "objectID": "decisions/20231114-elixir-definition-of-godot-types.html#metadata",
-    "href": "decisions/20231114-elixir-definition-of-godot-types.html#metadata",
-    "title": "Proposed: Defining the List of Godot Types in Elixir Godot Parsers",
+    "objectID": "decisions/20231108-munich-godot-engine-conference.html#the-challenge",
+    "href": "decisions/20231108-munich-godot-engine-conference.html#the-challenge",
+    "title": "Proposed: Enhancing V-Sekai Through Effective Documentation",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai Development Team\nTags: Godot Engine, Elixir, Type Definitions, V-Sekai"
+    "text": "One of the challenges faced by V-Sekai is ensuring that all processes and systems are well-documented. This is crucial for maintaining consistency, facilitating knowledge transfer, and enabling efficient problem-solving."
   },
   {
-    "objectID": "decisions/20231114-elixir-definition-of-godot-types.html#the-backdrop",
-    "href": "decisions/20231114-elixir-definition-of-godot-types.html#the-backdrop",
-    "title": "Proposed: Defining the List of Godot Types in Elixir Godot Parsers",
+    "objectID": "decisions/20231108-munich-godot-engine-conference.html#the-strategy",
+    "href": "decisions/20231108-munich-godot-engine-conference.html#the-strategy",
+    "title": "Proposed: Enhancing V-Sekai Through Effective Documentation",
     "section": "",
-    "text": "The elixir_godot_parsers project under V-Sekai aims to enhance the integration and parsing capabilities between the Elixir programming language and the Godot Engine. A key component of this is understanding and effectively parsing various data types used in Godot."
+    "text": "To overcome this challenge, the strategy is to prioritize documentation in all projects. This involves creating comprehensive guides, manuals, and references that detail how different systems work and how to use them effectively."
   },
   {
-    "objectID": "decisions/20231114-elixir-definition-of-godot-types.html#the-challenge",
-    "href": "decisions/20231114-elixir-definition-of-godot-types.html#the-challenge",
-    "title": "Proposed: Defining the List of Godot Types in Elixir Godot Parsers",
+    "objectID": "decisions/20231108-munich-godot-engine-conference.html#the-upside",
+    "href": "decisions/20231108-munich-godot-engine-conference.html#the-upside",
+    "title": "Proposed: Enhancing V-Sekai Through Effective Documentation",
     "section": "",
-    "text": "Currently, there may be ambiguities or a lack of clear definition for all Godot types within the elixir_godot_parsers project. This can lead to inconsistencies in parsing and handling data, potentially affecting the efficiency and reliability of the integration."
+    "text": "The upside of this approach is that it can significantly improve the efficiency and effectiveness of the team. With proper documentation, team members can quickly understand and navigate different systems, reducing the time spent on troubleshooting and problem-solving."
   },
   {
-    "objectID": "decisions/20231114-elixir-definition-of-godot-types.html#the-strategy",
-    "href": "decisions/20231114-elixir-definition-of-godot-types.html#the-strategy",
-    "title": "Proposed: Defining the List of Godot Types in Elixir Godot Parsers",
+    "objectID": "decisions/20231108-munich-godot-engine-conference.html#the-downside",
+    "href": "decisions/20231108-munich-godot-engine-conference.html#the-downside",
+    "title": "Proposed: Enhancing V-Sekai Through Effective Documentation",
     "section": "",
-    "text": "Propose the creation of a comprehensive, well-documented list of all Godot types. This list should be detailed and include specifications for each type, ensuring clarity and consistency in how Elixir handles and parses these types."
+    "text": "The downside is that creating and maintaining documentation can be time-consuming. However, the benefits of having well-documented systems far outweigh the costs."
   },
   {
-    "objectID": "decisions/20231114-elixir-definition-of-godot-types.html#the-upside",
-    "href": "decisions/20231114-elixir-definition-of-godot-types.html#the-upside",
-    "title": "Proposed: Defining the List of Godot Types in Elixir Godot Parsers",
+    "objectID": "decisions/20231108-munich-godot-engine-conference.html#the-road-not-taken",
+    "href": "decisions/20231108-munich-godot-engine-conference.html#the-road-not-taken",
+    "title": "Proposed: Enhancing V-Sekai Through Effective Documentation",
     "section": "",
-    "text": "Defining a clear list of Godot types will enhance the reliability and functionality of the Elixir-Godot integration. This will make the development process smoother, reduce bugs, and improve the overall efficiency of projects using both Elixir and Godot."
+    "text": "An alternative approach could have been to rely on informal knowledge transfer methods, such as one-on-one training or mentoring. However, this approach lacks the consistency and scalability of formal documentation."
   },
   {
-    "objectID": "decisions/20231114-elixir-definition-of-godot-types.html#the-downside",
-    "href": "decisions/20231114-elixir-definition-of-godot-types.html#the-downside",
-    "title": "Proposed: Defining the List of Godot Types in Elixir Godot Parsers",
+    "objectID": "decisions/20231108-munich-godot-engine-conference.html#the-infrequent-use-case",
+    "href": "decisions/20231108-munich-godot-engine-conference.html#the-infrequent-use-case",
+    "title": "Proposed: Enhancing V-Sekai Through Effective Documentation",
     "section": "",
-    "text": "Compiling and maintaining this list could be time-consuming. It may also require regular updates to stay in sync with any changes or updates in the Godot Engine."
+    "text": "In cases where systems or processes are rarely used or subject to frequent changes, maintaining up-to-date documentation might be challenging. In such scenarios, a combination of documentation and hands-on training might be more effective."
   },
   {
-    "objectID": "decisions/20231114-elixir-definition-of-godot-types.html#the-road-not-taken",
-    "href": "decisions/20231114-elixir-definition-of-godot-types.html#the-road-not-taken",
-    "title": "Proposed: Defining the List of Godot Types in Elixir Godot Parsers",
+    "objectID": "decisions/20231108-munich-godot-engine-conference.html#in-core-and-done-by-us",
+    "href": "decisions/20231108-munich-godot-engine-conference.html#in-core-and-done-by-us",
+    "title": "Proposed: Enhancing V-Sekai Through Effective Documentation",
     "section": "",
-    "text": "An alternative approach could be to continue without a defined list, relying on ad-hoc solutions for each type as needed. However, this could lead to increased development time and potential errors."
+    "text": "The decision to prioritize documentation is proposed by V-Sekai."
   },
   {
-    "objectID": "decisions/20231114-elixir-definition-of-godot-types.html#the-infrequent-use-case",
-    "href": "decisions/20231114-elixir-definition-of-godot-types.html#the-infrequent-use-case",
-    "title": "Proposed: Defining the List of Godot Types in Elixir Godot Parsers",
+    "objectID": "decisions/20231108-munich-godot-engine-conference.html#further-reading",
+    "href": "decisions/20231108-munich-godot-engine-conference.html#further-reading",
+    "title": "Proposed: Enhancing V-Sekai Through Effective Documentation",
     "section": "",
-    "text": "While this proposal primarily targets the Elixir-Godot integration, having a well-defined list of types could also be beneficial for other projects or integrations involving the Godot Engine."
+    "text": "V-Sekai\n\nThis article was assisted by Aria, an AI."
   },
   {
-    "objectID": "decisions/20231114-elixir-definition-of-godot-types.html#in-core-and-done-by-us",
-    "href": "decisions/20231114-elixir-definition-of-godot-types.html#in-core-and-done-by-us",
-    "title": "Proposed: Defining the List of Godot Types in Elixir Godot Parsers",
+    "objectID": "decisions/20231114-maintain-svgcleaner.html",
+    "href": "decisions/20231114-maintain-svgcleaner.html",
+    "title": "Proposed: Enhancing VR Book Reading through SVG Optimization",
     "section": "",
-    "text": "This task involves direct contributions to the core functionality of the elixir_godot_parsers project under V-Sekai, aiming to enhance its core capabilities in terms of data handling and parsing."
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: SVG Optimization, VR Book Reading, V-Sekai\n\n\n\n\nV-Sekai is dedicated to advancing the immersive experience in social VR. We can enhance VR book reading, a feature that demands high-quality visuals with efficient resource usage.\n\n\n\nIntegrating readable, high-quality SVG-based books into the VR environment presents a dual challenge of maintaining visual clarity while optimizing performance.\n\n\n\nUtilize the svgcleaner tool, particularly its Rust implementation, to optimize SVG files for VR book reading. This involves cleaning up SVG files from unnecessary data, thereby reducing file size without compromising visual integrity.\n\n\n\nOptimized SVGs lead to faster load times, smoother performance, and an overall enhanced user experience in VR book reading. This aligns with V-Sekai’s goal of creating a seamless and engaging VR environment.\n\n\n\nThe svgcleaner tool, particularly its Rust version, is currently archived and read-only, indicating a need for refresh or redevelopment.\n\n\n\nAlternative SVG optimization methods or tools might exist but could lack the specific features or efficiency provided by svgcleaner.\n\n\n\nWhile primarily aimed at VR book reading, this optimization could benefit other areas of V-Sekai where SVGs are used.\n\n\n\nThe task involves integrating an external tool (svgcleaner) into the core V-Sekai development process, possibly requiring custom adaptation for the specific VR context.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\nsvgcleaner on GitHub - The GitHub repository for svgcleaner, a tool to optimize SVG files.\n\nThis article was assisted by AI assistant Aria."
   },
   {
-    "objectID": "decisions/20231114-elixir-definition-of-godot-types.html#further-reading",
-    "href": "decisions/20231114-elixir-definition-of-godot-types.html#further-reading",
-    "title": "Proposed: Defining the List of Godot Types in Elixir Godot Parsers",
+    "objectID": "decisions/20231114-maintain-svgcleaner.html#metadata",
+    "href": "decisions/20231114-maintain-svgcleaner.html#metadata",
+    "title": "Proposed: Enhancing VR Book Reading through SVG Optimization",
     "section": "",
-    "text": "V-Sekai GitHub Repository - The official GitHub account for the V-Sekai development community, focusing on social VR functionality for the Godot Engine.\nElixir Godot Parsers Repository - The GitHub page for the elixir_godot_parsers project, part of V-Sekai’s efforts to integrate Elixir with the Godot Engine.\n\nThis proposal was created with the assistance of AI assistant Aria."
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: SVG Optimization, VR Book Reading, V-Sekai"
   },
   {
-    "objectID": "decisions/20240914-godot-engine-xr-elite-conference-setup.html",
-    "href": "decisions/20240914-godot-engine-xr-elite-conference-setup.html",
-    "title": "Accepted: Godot Engine XR Elite HMD Conference Setup",
+    "objectID": "decisions/20231114-maintain-svgcleaner.html#the-backdrop",
+    "href": "decisions/20231114-maintain-svgcleaner.html#the-backdrop",
+    "title": "Proposed: Enhancing VR Book Reading through SVG Optimization",
     "section": "",
-    "text": "Fire, an independent developer previously contracted with the Godot Foundation, plans to demonstrate the capabilities of the Godot Engine XR Team’s work on the VIVE headset at an upcoming conference. This setup is crucial for showcasing advanced VR features using the XR Elite Headset.\n\n\n\nSetting up a reliable and efficient demonstration environment for the XR Elite Headset at a conference can be challenging due to potential network issues and hardware integration complexities.\n\n\n\nThe proposed setup involves several components to ensure a stable and high-performance demonstration:\n\nHardware Connection:\n\nConnect the XR Elite Headset to a USB-C hub.\nAttach the Vive Ultimate Tracker dongle and a Belkin USB-C to Gigabit Ethernet Adapter to the hub.\n\nNetwork Configuration:\n\nUse a wired ethernet connection to avoid Wi-Fi instability common in conference venues.\nSet a fixed IP address for the VIVE Business Streaming server using the VBSIpSetting.exe tool.\n\nSoftware Setup:\n\nEnsure the business streaming server has a physical display connected to prevent the SteamVR overlay issue.\nRun SteamVR for VR demonstrations.\n\nAdditional Stability Measures:\n\nDisable Wi-Fi on the XR Elite Headset to rely solely on the wired connection.\nConsider using a gigabit travel router/switch to manage and shorten routing internally at the venue.\n\n\n\n\n\n\nReliability: Wired connections reduce the risk of connectivity issues during live demonstrations.\nPerformance: Direct network connections and optimized settings ensure smooth operation of VR applications.\nProfessional Presentation: A stable setup reflects well on the Godot Engine project and its capabilities in VR.\n\n\n\n\n\nComplexity: The setup requires careful configuration and might be daunting for less technical users.\nEquipment Dependency: Relies on specific hardware and software that may not be readily available at all venues.\n\n\n\n\nAlternative simpler setups were considered but rejected due to their reliance on less stable wireless connections which could compromise the demonstration’s effectiveness.\n\n\n\nIn cases where a direct internet connection is unavailable, additional configurations like mobile routers or other networking equipment might be necessary.\n\n\n\nThis proposal aligns with our core mission to showcase the best of Godot Engine’s VR capabilities and will be implemented by fire with support from the V-Sekai development team.\n\n\n\nStatus: Accepted \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "V-Sekai is dedicated to advancing the immersive experience in social VR. We can enhance VR book reading, a feature that demands high-quality visuals with efficient resource usage."
   },
   {
-    "objectID": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#the-context",
-    "href": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#the-context",
-    "title": "Accepted: Godot Engine XR Elite HMD Conference Setup",
+    "objectID": "decisions/20231114-maintain-svgcleaner.html#the-challenge",
+    "href": "decisions/20231114-maintain-svgcleaner.html#the-challenge",
+    "title": "Proposed: Enhancing VR Book Reading through SVG Optimization",
     "section": "",
-    "text": "Fire, an independent developer previously contracted with the Godot Foundation, plans to demonstrate the capabilities of the Godot Engine XR Team’s work on the VIVE headset at an upcoming conference. This setup is crucial for showcasing advanced VR features using the XR Elite Headset."
+    "text": "Integrating readable, high-quality SVG-based books into the VR environment presents a dual challenge of maintaining visual clarity while optimizing performance."
   },
   {
-    "objectID": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#the-problem-statement",
-    "href": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#the-problem-statement",
-    "title": "Accepted: Godot Engine XR Elite HMD Conference Setup",
+    "objectID": "decisions/20231114-maintain-svgcleaner.html#the-strategy",
+    "href": "decisions/20231114-maintain-svgcleaner.html#the-strategy",
+    "title": "Proposed: Enhancing VR Book Reading through SVG Optimization",
     "section": "",
-    "text": "Setting up a reliable and efficient demonstration environment for the XR Elite Headset at a conference can be challenging due to potential network issues and hardware integration complexities."
+    "text": "Utilize the svgcleaner tool, particularly its Rust implementation, to optimize SVG files for VR book reading. This involves cleaning up SVG files from unnecessary data, thereby reducing file size without compromising visual integrity."
   },
   {
-    "objectID": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Accepted: Godot Engine XR Elite HMD Conference Setup",
+    "objectID": "decisions/20231114-maintain-svgcleaner.html#the-upside",
+    "href": "decisions/20231114-maintain-svgcleaner.html#the-upside",
+    "title": "Proposed: Enhancing VR Book Reading through SVG Optimization",
     "section": "",
-    "text": "The proposed setup involves several components to ensure a stable and high-performance demonstration:\n\nHardware Connection:\n\nConnect the XR Elite Headset to a USB-C hub.\nAttach the Vive Ultimate Tracker dongle and a Belkin USB-C to Gigabit Ethernet Adapter to the hub.\n\nNetwork Configuration:\n\nUse a wired ethernet connection to avoid Wi-Fi instability common in conference venues.\nSet a fixed IP address for the VIVE Business Streaming server using the VBSIpSetting.exe tool.\n\nSoftware Setup:\n\nEnsure the business streaming server has a physical display connected to prevent the SteamVR overlay issue.\nRun SteamVR for VR demonstrations.\n\nAdditional Stability Measures:\n\nDisable Wi-Fi on the XR Elite Headset to rely solely on the wired connection.\nConsider using a gigabit travel router/switch to manage and shorten routing internally at the venue."
+    "text": "Optimized SVGs lead to faster load times, smoother performance, and an overall enhanced user experience in VR book reading. This aligns with V-Sekai’s goal of creating a seamless and engaging VR environment."
   },
   {
-    "objectID": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#the-benefits",
-    "href": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#the-benefits",
-    "title": "Accepted: Godot Engine XR Elite HMD Conference Setup",
+    "objectID": "decisions/20231114-maintain-svgcleaner.html#the-downside",
+    "href": "decisions/20231114-maintain-svgcleaner.html#the-downside",
+    "title": "Proposed: Enhancing VR Book Reading through SVG Optimization",
     "section": "",
-    "text": "Reliability: Wired connections reduce the risk of connectivity issues during live demonstrations.\nPerformance: Direct network connections and optimized settings ensure smooth operation of VR applications.\nProfessional Presentation: A stable setup reflects well on the Godot Engine project and its capabilities in VR."
+    "text": "The svgcleaner tool, particularly its Rust version, is currently archived and read-only, indicating a need for refresh or redevelopment."
   },
   {
-    "objectID": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#the-downsides",
-    "href": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#the-downsides",
-    "title": "Accepted: Godot Engine XR Elite HMD Conference Setup",
+    "objectID": "decisions/20231114-maintain-svgcleaner.html#the-road-not-taken",
+    "href": "decisions/20231114-maintain-svgcleaner.html#the-road-not-taken",
+    "title": "Proposed: Enhancing VR Book Reading through SVG Optimization",
     "section": "",
-    "text": "Complexity: The setup requires careful configuration and might be daunting for less technical users.\nEquipment Dependency: Relies on specific hardware and software that may not be readily available at all venues."
+    "text": "Alternative SVG optimization methods or tools might exist but could lack the specific features or efficiency provided by svgcleaner."
   },
   {
-    "objectID": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#the-road-not-taken",
-    "href": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#the-road-not-taken",
-    "title": "Accepted: Godot Engine XR Elite HMD Conference Setup",
+    "objectID": "decisions/20231114-maintain-svgcleaner.html#the-infrequent-use-case",
+    "href": "decisions/20231114-maintain-svgcleaner.html#the-infrequent-use-case",
+    "title": "Proposed: Enhancing VR Book Reading through SVG Optimization",
     "section": "",
-    "text": "Alternative simpler setups were considered but rejected due to their reliance on less stable wireless connections which could compromise the demonstration’s effectiveness."
+    "text": "While primarily aimed at VR book reading, this optimization could benefit other areas of V-Sekai where SVGs are used."
   },
   {
-    "objectID": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#the-infrequent-use-case",
-    "href": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#the-infrequent-use-case",
-    "title": "Accepted: Godot Engine XR Elite HMD Conference Setup",
+    "objectID": "decisions/20231114-maintain-svgcleaner.html#in-core-and-done-by-us",
+    "href": "decisions/20231114-maintain-svgcleaner.html#in-core-and-done-by-us",
+    "title": "Proposed: Enhancing VR Book Reading through SVG Optimization",
     "section": "",
-    "text": "In cases where a direct internet connection is unavailable, additional configurations like mobile routers or other networking equipment might be necessary."
+    "text": "The task involves integrating an external tool (svgcleaner) into the core V-Sekai development process, possibly requiring custom adaptation for the specific VR context."
   },
   {
-    "objectID": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#in-core-and-done-by-us",
-    "href": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#in-core-and-done-by-us",
-    "title": "Accepted: Godot Engine XR Elite HMD Conference Setup",
+    "objectID": "decisions/20231114-maintain-svgcleaner.html#further-reading",
+    "href": "decisions/20231114-maintain-svgcleaner.html#further-reading",
+    "title": "Proposed: Enhancing VR Book Reading through SVG Optimization",
     "section": "",
-    "text": "This proposal aligns with our core mission to showcase the best of Godot Engine’s VR capabilities and will be implemented by fire with support from the V-Sekai development team."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\nsvgcleaner on GitHub - The GitHub repository for svgcleaner, a tool to optimize SVG files.\n\nThis article was assisted by AI assistant Aria."
   },
   {
-    "objectID": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#status",
-    "href": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#status",
-    "title": "Accepted: Godot Engine XR Elite HMD Conference Setup",
+    "objectID": "decisions/20211031-use-our-custom-fullbody-ik.html",
+    "href": "decisions/20211031-use-our-custom-fullbody-ik.html",
+    "title": "Accepted: Use our custom fullbody IK",
     "section": "",
-    "text": "Status: Accepted"
+    "text": "Accepted: Use our custom fullbody IK\n\nContext and Problem Statement\nWe need to animater our characters in game using full body ik.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nEWBIK is a full body ik.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nEWBIK\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nCode is already complicated.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nI and Eron know.\n\n\nReferences\n\nEWBIK\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#decision-makers",
-    "href": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#decision-makers",
-    "title": "Accepted: Godot Engine XR Elite HMD Conference Setup",
+    "objectID": "decisions/20230913-V-Sekai-bugs.html",
+    "href": "decisions/20230913-V-Sekai-bugs.html",
+    "title": "Proposed: Challenges that need to be addressed in V-Sekai",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nIn our quest to expand our community, we are faced with several challenges that need to be addressed.\n\n\n\nOur game has been QA Engineered by Facade, which was a great help. However, there are still issues that need to be resolved.\n\n\n\nWe have identified several areas of concern and have charted them in the following flow diagram:\ngraph TD\n    Crash[\"V-Sekai crash on start on RADV, Ubuntu 22.04.2 LTS (Jammy Jellyfish) #115\"]\n    VR[\"VR doesn't work #228\"]\n    Avatar[\"Restore avatar upload #243\"]\n    Uploads[\"Restore world uploads #244\"]\n    Mirror[\"Restore mirror in the preview server #249\"]\n    Freeze[\"Pressing escape button while ingame freezes client #250\"]\n    Escape[\"Escape button in menu should go back, instead does nothing #251\"]\n    Text[\"UI dropdown text is invisible until hovered #252\"]\n    Sensitivity[\"Increase default mouse sensitivity #253\"]\n    Gestures[\"Restore gestures #254\"]\n    VOIP[\"Restore VOIP #255\"]\n    IK[\"IK errors ingame #256\"]\n\n    Crash--&gt;VR\n    VR--&gt;Avatar\n    Avatar--&gt;Uploads\n    Uploads--&gt;Mirror\n    Mirror--&gt;Freeze\n    Freeze--&gt;Escape\n    Escape--&gt;Text\n    Text--&gt;Sensitivity\n    Sensitivity--&gt;Gestures\n    Gestures--&gt;VOIP\n    VOIP--&gt;IK\n\n\n\nAddressing these issues will significantly improve the user experience, making our game more enjoyable and accessible. This could lead to an increase in our user base and community engagement.\n\n\n\nThe process of resolving these issues may require significant time and resources. It might also involve some trial and error, which could potentially introduce new bugs or problems.\n\n\n\nIgnoring these issues is not an option as it would negatively impact the user experience and could hinder the growth of our community.\n\n\n\nWhile some of these issues might only affect a small number of users or occur under specific circumstances, it’s important to address them to ensure a smooth and enjoyable experience for all users.\n\n\n\nYes, these issues are core to the functionality of our game and should be addressed by our team.\n\n\n\n\nV-Sekai\nThis article is assisted by AI."
   },
   {
-    "objectID": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#tags",
-    "href": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#tags",
-    "title": "Accepted: Godot Engine XR Elite HMD Conference Setup",
+    "objectID": "decisions/20230913-V-Sekai-bugs.html#metadata",
+    "href": "decisions/20230913-V-Sekai-bugs.html#metadata",
+    "title": "Proposed: Challenges that need to be addressed in V-Sekai",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#further-reading",
-    "href": "decisions/20240914-godot-engine-xr-elite-conference-setup.html#further-reading",
-    "title": "Accepted: Godot Engine XR Elite HMD Conference Setup",
+    "objectID": "decisions/20230913-V-Sekai-bugs.html#the-backdrop",
+    "href": "decisions/20230913-V-Sekai-bugs.html#the-backdrop",
+    "title": "Proposed: Challenges that need to be addressed in V-Sekai",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "In our quest to expand our community, we are faced with several challenges that need to be addressed."
   },
   {
-    "objectID": "decisions/20230531-godot-engine-ipad.html",
-    "href": "decisions/20230531-godot-engine-ipad.html",
-    "title": "Proposed: Build a Single-Instance MacOS Editor for the iPad",
+    "objectID": "decisions/20230913-V-Sekai-bugs.html#the-challenge",
+    "href": "decisions/20230913-V-Sekai-bugs.html#the-challenge",
+    "title": "Proposed: Challenges that need to be addressed in V-Sekai",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, GPT-4, MacOS, iPad\n\n\n\n\nWe have successfully tested a MacOS editor on the iPhone in February 2023. Now, we want to build a similar editor for the iPad so that people can upload game worlds and avatars from a tablet. However, due to iOS limitations, it’s impossible to run multiple instances of the app or restart the app on non-jailbroken devices. Therefore, we need to adapt the existing codebase to work within these constraints.\n\n\n\n\nAdapt the existing MacOS editor codebase for the iPad without relying on multi-process architecture.\nTest the application on various iPad models to ensure compatibility and performance.\n\n\n\n\n\nClone the existing iPhone Godot Engine editor repository.\nCreate a new branch for the iPad version.\nModify the codebase to avoid using multi-process architecture:\n\nChange almost all global states (probably except UIApplication and view controller) to thread-local.\nRun multiple Godot instances in threads instead of processes.\n\nImplement the editor, import project folder, and export PCK to the filesystem. Our project requires SCN uploads to a web CDN.\nTest the application on different iPad models and fix any issues found during testing.\n\nInstall Xcode.\nGenerate certificates.\nUpload the Godot Engine iPad build to the iPad.\n\nMerge the iPad branch back into the main branch once the application is stable and fully functional.\n\n\n\n\n\nExpanding the availability of the MacOS editor to iPad users.\nReusing the existing codebase, reducing development time and effort.\n\n\n\n\n\nAdditional development and testing efforts required to support another platform.\nPotential maintenance overhead due to supporting multiple platforms.\n\n\n\n\n\nDeveloping a separate iPad-only application from scratch.\nUsing web-based editor solutions instead of a native app.\nImplementing a remote desktop solution to access a MacOS editor on a different device.\nPorting the MacOS editor to a cross-platform framework, potentially sacrificing performance and native features.\n\n\n\n\nNo, this enhancement requires significant changes to the existing codebase to properly support the iPad.\n\n\n\nYes, as the maintainers of Godot Engine, we have the expertise and knowledge of the codebase to efficiently adapt it for the iPad.\n\n\n\n\nV-Sekai\niPad fork of of Godot Engine"
+    "text": "Our game has been QA Engineered by Facade, which was a great help. However, there are still issues that need to be resolved."
   },
   {
-    "objectID": "decisions/20230531-godot-engine-ipad.html#metadata",
-    "href": "decisions/20230531-godot-engine-ipad.html#metadata",
-    "title": "Proposed: Build a Single-Instance MacOS Editor for the iPad",
+    "objectID": "decisions/20230913-V-Sekai-bugs.html#the-strategy",
+    "href": "decisions/20230913-V-Sekai-bugs.html#the-strategy",
+    "title": "Proposed: Challenges that need to be addressed in V-Sekai",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, GPT-4, MacOS, iPad"
+    "text": "We have identified several areas of concern and have charted them in the following flow diagram:\ngraph TD\n    Crash[\"V-Sekai crash on start on RADV, Ubuntu 22.04.2 LTS (Jammy Jellyfish) #115\"]\n    VR[\"VR doesn't work #228\"]\n    Avatar[\"Restore avatar upload #243\"]\n    Uploads[\"Restore world uploads #244\"]\n    Mirror[\"Restore mirror in the preview server #249\"]\n    Freeze[\"Pressing escape button while ingame freezes client #250\"]\n    Escape[\"Escape button in menu should go back, instead does nothing #251\"]\n    Text[\"UI dropdown text is invisible until hovered #252\"]\n    Sensitivity[\"Increase default mouse sensitivity #253\"]\n    Gestures[\"Restore gestures #254\"]\n    VOIP[\"Restore VOIP #255\"]\n    IK[\"IK errors ingame #256\"]\n\n    Crash--&gt;VR\n    VR--&gt;Avatar\n    Avatar--&gt;Uploads\n    Uploads--&gt;Mirror\n    Mirror--&gt;Freeze\n    Freeze--&gt;Escape\n    Escape--&gt;Text\n    Text--&gt;Sensitivity\n    Sensitivity--&gt;Gestures\n    Gestures--&gt;VOIP\n    VOIP--&gt;IK"
   },
   {
-    "objectID": "decisions/20230531-godot-engine-ipad.html#context-and-problem-statement",
-    "href": "decisions/20230531-godot-engine-ipad.html#context-and-problem-statement",
-    "title": "Proposed: Build a Single-Instance MacOS Editor for the iPad",
+    "objectID": "decisions/20230913-V-Sekai-bugs.html#the-upside",
+    "href": "decisions/20230913-V-Sekai-bugs.html#the-upside",
+    "title": "Proposed: Challenges that need to be addressed in V-Sekai",
     "section": "",
-    "text": "We have successfully tested a MacOS editor on the iPhone in February 2023. Now, we want to build a similar editor for the iPad so that people can upload game worlds and avatars from a tablet. However, due to iOS limitations, it’s impossible to run multiple instances of the app or restart the app on non-jailbroken devices. Therefore, we need to adapt the existing codebase to work within these constraints."
+    "text": "Addressing these issues will significantly improve the user experience, making our game more enjoyable and accessible. This could lead to an increase in our user base and community engagement."
   },
   {
-    "objectID": "decisions/20230531-godot-engine-ipad.html#proposed-solution",
-    "href": "decisions/20230531-godot-engine-ipad.html#proposed-solution",
-    "title": "Proposed: Build a Single-Instance MacOS Editor for the iPad",
+    "objectID": "decisions/20230913-V-Sekai-bugs.html#the-downside",
+    "href": "decisions/20230913-V-Sekai-bugs.html#the-downside",
+    "title": "Proposed: Challenges that need to be addressed in V-Sekai",
     "section": "",
-    "text": "Adapt the existing MacOS editor codebase for the iPad without relying on multi-process architecture.\nTest the application on various iPad models to ensure compatibility and performance."
+    "text": "The process of resolving these issues may require significant time and resources. It might also involve some trial and error, which could potentially introduce new bugs or problems."
   },
   {
-    "objectID": "decisions/20230531-godot-engine-ipad.html#implementation",
-    "href": "decisions/20230531-godot-engine-ipad.html#implementation",
-    "title": "Proposed: Build a Single-Instance MacOS Editor for the iPad",
+    "objectID": "decisions/20230913-V-Sekai-bugs.html#the-road-not-taken",
+    "href": "decisions/20230913-V-Sekai-bugs.html#the-road-not-taken",
+    "title": "Proposed: Challenges that need to be addressed in V-Sekai",
     "section": "",
-    "text": "Clone the existing iPhone Godot Engine editor repository.\nCreate a new branch for the iPad version.\nModify the codebase to avoid using multi-process architecture:\n\nChange almost all global states (probably except UIApplication and view controller) to thread-local.\nRun multiple Godot instances in threads instead of processes.\n\nImplement the editor, import project folder, and export PCK to the filesystem. Our project requires SCN uploads to a web CDN.\nTest the application on different iPad models and fix any issues found during testing.\n\nInstall Xcode.\nGenerate certificates.\nUpload the Godot Engine iPad build to the iPad.\n\nMerge the iPad branch back into the main branch once the application is stable and fully functional."
+    "text": "Ignoring these issues is not an option as it would negatively impact the user experience and could hinder the growth of our community."
   },
   {
-    "objectID": "decisions/20230531-godot-engine-ipad.html#positive-consequences",
-    "href": "decisions/20230531-godot-engine-ipad.html#positive-consequences",
-    "title": "Proposed: Build a Single-Instance MacOS Editor for the iPad",
+    "objectID": "decisions/20230913-V-Sekai-bugs.html#the-infrequent-use-case",
+    "href": "decisions/20230913-V-Sekai-bugs.html#the-infrequent-use-case",
+    "title": "Proposed: Challenges that need to be addressed in V-Sekai",
     "section": "",
-    "text": "Expanding the availability of the MacOS editor to iPad users.\nReusing the existing codebase, reducing development time and effort."
+    "text": "While some of these issues might only affect a small number of users or occur under specific circumstances, it’s important to address them to ensure a smooth and enjoyable experience for all users."
   },
   {
-    "objectID": "decisions/20230531-godot-engine-ipad.html#negative-consequences",
-    "href": "decisions/20230531-godot-engine-ipad.html#negative-consequences",
-    "title": "Proposed: Build a Single-Instance MacOS Editor for the iPad",
+    "objectID": "decisions/20230913-V-Sekai-bugs.html#in-core-and-done-by-us",
+    "href": "decisions/20230913-V-Sekai-bugs.html#in-core-and-done-by-us",
+    "title": "Proposed: Challenges that need to be addressed in V-Sekai",
     "section": "",
-    "text": "Additional development and testing efforts required to support another platform.\nPotential maintenance overhead due to supporting multiple platforms."
+    "text": "Yes, these issues are core to the functionality of our game and should be addressed by our team."
   },
   {
-    "objectID": "decisions/20230531-godot-engine-ipad.html#option-graveyard",
-    "href": "decisions/20230531-godot-engine-ipad.html#option-graveyard",
-    "title": "Proposed: Build a Single-Instance MacOS Editor for the iPad",
+    "objectID": "decisions/20230913-V-Sekai-bugs.html#further-reading",
+    "href": "decisions/20230913-V-Sekai-bugs.html#further-reading",
+    "title": "Proposed: Challenges that need to be addressed in V-Sekai",
     "section": "",
-    "text": "Developing a separate iPad-only application from scratch.\nUsing web-based editor solutions instead of a native app.\nImplementing a remote desktop solution to access a MacOS editor on a different device.\nPorting the MacOS editor to a cross-platform framework, potentially sacrificing performance and native features."
+    "text": "V-Sekai\nThis article is assisted by AI."
   },
   {
-    "objectID": "decisions/20230531-godot-engine-ipad.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230531-godot-engine-ipad.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Build a Single-Instance MacOS Editor for the iPad",
+    "objectID": "decisions/20221018-v-sekai-game-update-procedure.html",
+    "href": "decisions/20221018-v-sekai-game-update-procedure.html",
+    "title": "Proposed: To remember how to update the engine and game write a procedure",
     "section": "",
-    "text": "No, this enhancement requires significant changes to the existing codebase to properly support the iPad."
+    "text": "Status: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\n\nGodot Engine and V-Sekai are fast moving projects.\n\n\n\nWrite down how to update the engine and the game.\n\n\n\n\nFirst step: change the update_vsekai_godot script to push to a staging branch.\nNext step (lazy and simple): it is your responsibility to build the engine, run groups project and make sure it works.\nOptionally: you should perform an export build and make sure that works too.\nNext step (less lazy): we add another set of CI pipelines for staging godot -&gt; staging templates -&gt; staging groups and then we test that\nMost issues aren’t export related, so I think engine build + open project and run project is probably sufficient for most things and we need a script to push staging -&gt; groups-4.x\nWhich means everyone gets the upgraded engine\n\n\n\n\nCreating a standard procedure means people know what to do.\n\n\n\nIt’s complicated.\n\n\n\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\n\nThis is a procedure and not code.\n\n\n\nWe know how to do this and others don’t.\n\n\n\n\nV-Sekai\n\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230531-godot-engine-ipad.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230531-godot-engine-ipad.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Build a Single-Instance MacOS Editor for the iPad",
+    "objectID": "decisions/20221018-v-sekai-game-update-procedure.html#context-and-problem-statement",
+    "href": "decisions/20221018-v-sekai-game-update-procedure.html#context-and-problem-statement",
+    "title": "Proposed: To remember how to update the engine and game write a procedure",
     "section": "",
-    "text": "Yes, as the maintainers of Godot Engine, we have the expertise and knowledge of the codebase to efficiently adapt it for the iPad."
+    "text": "Godot Engine and V-Sekai are fast moving projects."
   },
   {
-    "objectID": "decisions/20230531-godot-engine-ipad.html#references",
-    "href": "decisions/20230531-godot-engine-ipad.html#references",
-    "title": "Proposed: Build a Single-Instance MacOS Editor for the iPad",
+    "objectID": "decisions/20221018-v-sekai-game-update-procedure.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20221018-v-sekai-game-update-procedure.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: To remember how to update the engine and game write a procedure",
     "section": "",
-    "text": "V-Sekai\niPad fork of of Godot Engine"
+    "text": "Write down how to update the engine and the game."
   },
   {
-    "objectID": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html",
-    "href": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html",
-    "title": "Proposed: Replicate sync 100’000 entities using Godot Engine, mvsqlite and Foundationdb",
+    "objectID": "decisions/20221018-v-sekai-game-update-procedure.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20221018-v-sekai-game-update-procedure.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: To remember how to update the engine and game write a procedure",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai,fire,\nTags: V-Sekai,sync,view replication,\n\n\n\nSee replicate sync 100’000 entities using a solution.\n\n\n\nI propose we have groups of servers handling entities. Each server is synchronized with mvsqlite.\n\n\n\nWe assume we’re using Godot Engine 4 with float is doubles.\nThe servers do not share (independently access) the same memory or storage.\nWe can track the entity’s visibility and have a packed byte array per frame.\nUse mvsqlite in STRICT sql mode.\nUse the SQLite generated columns option STORED to optimize for reading and VIRTUAL to optimize for writing.\nCreate ECS style mvsqlite database for streaming and events (movement, health, avatar path and others).\nFor movement update the table once and only once per frame.\nFor avatar paths that change batch notify once per frame.\n\n\n\nimage\n\n\n\n\n\n\nThe code is using foundationdb’s share nothing architecture.\n\n\n\n\n\nWorried that latency will be above 20 milliseconds. It was shown in the graphs. May be a bug in mvsqlite with sequential key retries. Does the ownership / mastership of entities change often?\n\n\n\n\n\nOption: Current V-Sekai replication\nRejection Reason: Can’t link servers\n\n\n\n\nEntity replication is not trivial.\n\n\n\nWe’re doing the networking layer.\n\n\n\n\nfault-tolerance\ngodot-sqlite with mvsqlite\nnovus core\n\n\n\n\n[godot client alice] -&gt; [godot server alpha with mvsqlite |  [godot server alpha with mvsqlite| owns groups entities per tick\n  | have a way to track entities\n  | create, update and delete entity groups]]\n[godot client bob] -&gt; [godot server beta with mvsqlite |  [godot server beta with mvsqlite| owns groups entities per tick\n  | have a way to track entities\n  | create, update and delete entity groups]]\n[godot client carol] -&gt; [godot server gamma with mvsqlite |  [godot server gamma with mvsqlite| owns groups entities per tick\n  | have a way to track entities\n  | create, update and delete entity groups]]\n  [godot server alpha with mvsqlite] - [godot server beta with mvsqlite]\n  [godot server alpha with mvsqlite] - [godot server gamma with mvsqlite]\n  [godot server beta with mvsqlite] - [godot server gamma with mvsqlite]\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "First step: change the update_vsekai_godot script to push to a staging branch.\nNext step (lazy and simple): it is your responsibility to build the engine, run groups project and make sure it works.\nOptionally: you should perform an export build and make sure that works too.\nNext step (less lazy): we add another set of CI pipelines for staging godot -&gt; staging templates -&gt; staging groups and then we test that\nMost issues aren’t export related, so I think engine build + open project and run project is probably sufficient for most things and we need a script to push staging -&gt; groups-4.x\nWhich means everyone gets the upgraded engine"
   },
   {
-    "objectID": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#context-and-problem-statement",
-    "href": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#context-and-problem-statement",
-    "title": "Proposed: Replicate sync 100’000 entities using Godot Engine, mvsqlite and Foundationdb",
+    "objectID": "decisions/20221018-v-sekai-game-update-procedure.html#positive-consequences",
+    "href": "decisions/20221018-v-sekai-game-update-procedure.html#positive-consequences",
+    "title": "Proposed: To remember how to update the engine and game write a procedure",
     "section": "",
-    "text": "See replicate sync 100’000 entities using a solution."
+    "text": "Creating a standard procedure means people know what to do."
   },
   {
-    "objectID": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: Replicate sync 100’000 entities using Godot Engine, mvsqlite and Foundationdb",
+    "objectID": "decisions/20221018-v-sekai-game-update-procedure.html#negative-consequences",
+    "href": "decisions/20221018-v-sekai-game-update-procedure.html#negative-consequences",
+    "title": "Proposed: To remember how to update the engine and game write a procedure",
     "section": "",
-    "text": "I propose we have groups of servers handling entities. Each server is synchronized with mvsqlite."
+    "text": "It’s complicated."
   },
   {
-    "objectID": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Replicate sync 100’000 entities using Godot Engine, mvsqlite and Foundationdb",
+    "objectID": "decisions/20221018-v-sekai-game-update-procedure.html#option-graveyard",
+    "href": "decisions/20221018-v-sekai-game-update-procedure.html#option-graveyard",
+    "title": "Proposed: To remember how to update the engine and game write a procedure",
     "section": "",
-    "text": "We assume we’re using Godot Engine 4 with float is doubles.\nThe servers do not share (independently access) the same memory or storage.\nWe can track the entity’s visibility and have a packed byte array per frame.\nUse mvsqlite in STRICT sql mode.\nUse the SQLite generated columns option STORED to optimize for reading and VIRTUAL to optimize for writing.\nCreate ECS style mvsqlite database for streaming and events (movement, health, avatar path and others).\nFor movement update the table once and only once per frame.\nFor avatar paths that change batch notify once per frame.\n\n\n\nimage"
+    "text": "Option: The status quo. \nRejection Reason: This solves nothing."
   },
   {
-    "objectID": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#positive-consequences",
-    "href": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#positive-consequences",
-    "title": "Proposed: Replicate sync 100’000 entities using Godot Engine, mvsqlite and Foundationdb",
+    "objectID": "decisions/20221018-v-sekai-game-update-procedure.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20221018-v-sekai-game-update-procedure.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: To remember how to update the engine and game write a procedure",
     "section": "",
-    "text": "The code is using foundationdb’s share nothing architecture."
+    "text": "This is a procedure and not code."
   },
   {
-    "objectID": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#negative-consequences",
-    "href": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#negative-consequences",
-    "title": "Proposed: Replicate sync 100’000 entities using Godot Engine, mvsqlite and Foundationdb",
+    "objectID": "decisions/20221018-v-sekai-game-update-procedure.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20221018-v-sekai-game-update-procedure.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: To remember how to update the engine and game write a procedure",
     "section": "",
-    "text": "Worried that latency will be above 20 milliseconds. It was shown in the graphs. May be a bug in mvsqlite with sequential key retries. Does the ownership / mastership of entities change often?"
+    "text": "We know how to do this and others don’t."
   },
   {
-    "objectID": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#option-graveyard",
-    "href": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#option-graveyard",
-    "title": "Proposed: Replicate sync 100’000 entities using Godot Engine, mvsqlite and Foundationdb",
+    "objectID": "decisions/20221018-v-sekai-game-update-procedure.html#references",
+    "href": "decisions/20221018-v-sekai-game-update-procedure.html#references",
+    "title": "Proposed: To remember how to update the engine and game write a procedure",
     "section": "",
-    "text": "Option: Current V-Sekai replication\nRejection Reason: Can’t link servers"
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Replicate sync 100’000 entities using Godot Engine, mvsqlite and Foundationdb",
+    "objectID": "decisions/20221018-v-sekai-game-update-procedure.html#license-of-the-contribution",
+    "href": "decisions/20221018-v-sekai-game-update-procedure.html#license-of-the-contribution",
+    "title": "Proposed: To remember how to update the engine and game write a procedure",
     "section": "",
-    "text": "Entity replication is not trivial."
+    "text": "Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Replicate sync 100’000 entities using Godot Engine, mvsqlite and Foundationdb",
+    "objectID": "decisions/20231110-better-pipeline-tools.html",
+    "href": "decisions/20231110-better-pipeline-tools.html",
+    "title": "Proposed: Enhancing V-Sekai x Godot Engine x AYON for a Superior Workflow",
     "section": "",
-    "text": "We’re doing the networking layer."
+    "text": "Status: Proposed\nDeciders: V-Sekai, fire\nTags: V-Sekai, Godot Engine, Virtual Reality\n\n\n\n\nThe V-Sekai Project is an open-source initiative that aims to bring social VR/VRSNS/metaverse components to the Godot Engine.\n\n\n\nOne of the market leaders in VRSNS, the OMEGA project, is tied to a specific game engine and faces two key challenges in bundling their game engine:\n\nThe size of the bundle would be quite large.\nThey are separate entities that require commercial terms to bundle together.\nComponents are not commercial-friendly opensource.\n\nWe have the opportunity to enhance AYON to create a superior launcher for the Godot Engine and the Project, something many of our competitors cannot do due to similar constraints.\n\n\n\nOur strategy is to outperform OMEGA’s workflow by enhancing AYON through tooling and comprehensive documentation. By providing clear instructions and efficient tools for developers, we aim to streamline the development process and improve efficiency.\n\n\n\nThis approach could potentially lead to a more diverse range of social VR experiences and help grow the Godot Engine community.\n\n\n\nEnhancing AYON and creating comprehensive documentation is a time-consuming process and requires ongoing maintenance.\n\n\n\nAn alternative option would be to develop an individual plugin or extension. However, this requires significant resources and may not be feasible for an open-source project.\n\n\n\nWhile developing a plugin or extension provides out-of-the-box functionality, it may not cover all use cases and could limit the diversity of social VR experiences.\n\n\n\nBy focusing on enhancing AYON and creating comprehensive documentation, we are empowering developers to implement these features in their own unique ways.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nAYON - The platform hosting our tools and editor\n\n\nThis article was assisted by Aria, an AI assistant."
   },
   {
-    "objectID": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#references",
-    "href": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#references",
-    "title": "Proposed: Replicate sync 100’000 entities using Godot Engine, mvsqlite and Foundationdb",
+    "objectID": "decisions/20231110-better-pipeline-tools.html#metadata",
+    "href": "decisions/20231110-better-pipeline-tools.html#metadata",
+    "title": "Proposed: Enhancing V-Sekai x Godot Engine x AYON for a Superior Workflow",
     "section": "",
-    "text": "fault-tolerance\ngodot-sqlite with mvsqlite\nnovus core"
+    "text": "Status: Proposed\nDeciders: V-Sekai, fire\nTags: V-Sekai, Godot Engine, Virtual Reality"
   },
   {
-    "objectID": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#diagram-source",
-    "href": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#diagram-source",
-    "title": "Proposed: Replicate sync 100’000 entities using Godot Engine, mvsqlite and Foundationdb",
+    "objectID": "decisions/20231110-better-pipeline-tools.html#the-backdrop",
+    "href": "decisions/20231110-better-pipeline-tools.html#the-backdrop",
+    "title": "Proposed: Enhancing V-Sekai x Godot Engine x AYON for a Superior Workflow",
     "section": "",
-    "text": "[godot client alice] -&gt; [godot server alpha with mvsqlite |  [godot server alpha with mvsqlite| owns groups entities per tick\n  | have a way to track entities\n  | create, update and delete entity groups]]\n[godot client bob] -&gt; [godot server beta with mvsqlite |  [godot server beta with mvsqlite| owns groups entities per tick\n  | have a way to track entities\n  | create, update and delete entity groups]]\n[godot client carol] -&gt; [godot server gamma with mvsqlite |  [godot server gamma with mvsqlite| owns groups entities per tick\n  | have a way to track entities\n  | create, update and delete entity groups]]\n  [godot server alpha with mvsqlite] - [godot server beta with mvsqlite]\n  [godot server alpha with mvsqlite] - [godot server gamma with mvsqlite]\n  [godot server beta with mvsqlite] - [godot server gamma with mvsqlite]"
+    "text": "The V-Sekai Project is an open-source initiative that aims to bring social VR/VRSNS/metaverse components to the Godot Engine."
   },
   {
-    "objectID": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#derivative-license",
-    "href": "decisions/20221019-develop-a-replication-sync-for-100-000-entities.html#derivative-license",
-    "title": "Proposed: Replicate sync 100’000 entities using Godot Engine, mvsqlite and Foundationdb",
+    "objectID": "decisions/20231110-better-pipeline-tools.html#the-challenge",
+    "href": "decisions/20231110-better-pipeline-tools.html#the-challenge",
+    "title": "Proposed: Enhancing V-Sekai x Godot Engine x AYON for a Superior Workflow",
     "section": "",
-    "text": "Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "One of the market leaders in VRSNS, the OMEGA project, is tied to a specific game engine and faces two key challenges in bundling their game engine:\n\nThe size of the bundle would be quite large.\nThey are separate entities that require commercial terms to bundle together.\nComponents are not commercial-friendly opensource.\n\nWe have the opportunity to enhance AYON to create a superior launcher for the Godot Engine and the Project, something many of our competitors cannot do due to similar constraints."
   },
   {
-    "objectID": "decisions/20240623-what-is-uro-backend.html",
-    "href": "decisions/20240623-what-is-uro-backend.html",
-    "title": "Proposed: Why did we build “Uro”?",
+    "objectID": "decisions/20231110-better-pipeline-tools.html#the-strategy",
+    "href": "decisions/20231110-better-pipeline-tools.html#the-strategy",
+    "title": "Proposed: Enhancing V-Sekai x Godot Engine x AYON for a Superior Workflow",
     "section": "",
-    "text": "V-Sekai is an open-source project that brings social VR/VRSNS/metaverse components to the Godot Engine. It has a complex architecture involving multiple components, including a game client, a backend called “Uro”, and game servers.\n\n\n\nThere is a need to explain the architecture of V-Sekai, specifically the roles and interactions of the game client, the Uro backend, and the game servers.\n\n\n\nThe game client is the application that users interact with. It connects to both Uro, our backend service, and directly to game servers.\nThe game editor is a separate tool used by game designers. They use it to create and upload new worlds, props, and avatars to the Uro backend.\nUro is the backend service for our game. It handles requests from both the game client and game editor. It stores and serves game assets like worlds, props, and avatars.\nGame servers are responsible for running the game logic in real-time. They communicate with the game clients to keep the game state synchronized between all players.\n\n\n\nUnderstanding the architecture of V-Sekai can help developers contribute more effectively to the project. It can also help users troubleshoot issues and understand the capabilities and limitations of the system.\n\n\n\nThe complexity of the architecture may be daunting for some, and there may be a learning curve involved in understanding it.\n\n\n\n\nAn alternative approach could have been to implement a Peer-to-Peer (P2P) architecture. In this setup, each game client also acts as a mini-server, communicating directly with other clients.\nAnother alternative would be to use cloud-based game backends such as Microsoft’s PlayFab. These services can automatically scale up or down based on demand, ensuring that there’s always enough capacity for all players.\nNakama is an open-source distributed social and realtime server for games and apps. It has a rich feature set including user accounts, chat, social, matchmaker, realtime multiplayer, and much more.\n\n\n\n\nThe primary use case for the Uro server is to facilitate interactions between the game client and the game servers, there may be infrequent use cases where its functionality could be extended or used in different ways. For example, it is can be used to implement additional features such as leaderboards, achievements, or social networking features within the game. These use cases, while not common, should still be considered when designing and implementing the Uro server.\n\n\n\nThis proposal is core to the V-Sekai project and will be implemented by the V-Sekai development team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\nFire\nAries\n\n\n\n\n\nV-Sekai\nUro Backend\nGame Architecture\nOpen-source Project\nGodot Engine\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "Our strategy is to outperform OMEGA’s workflow by enhancing AYON through tooling and comprehensive documentation. By providing clear instructions and efficient tools for developers, we aim to streamline the development process and improve efficiency."
   },
   {
-    "objectID": "decisions/20240623-what-is-uro-backend.html#the-context",
-    "href": "decisions/20240623-what-is-uro-backend.html#the-context",
-    "title": "Proposed: Why did we build “Uro”?",
+    "objectID": "decisions/20231110-better-pipeline-tools.html#the-upside",
+    "href": "decisions/20231110-better-pipeline-tools.html#the-upside",
+    "title": "Proposed: Enhancing V-Sekai x Godot Engine x AYON for a Superior Workflow",
     "section": "",
-    "text": "V-Sekai is an open-source project that brings social VR/VRSNS/metaverse components to the Godot Engine. It has a complex architecture involving multiple components, including a game client, a backend called “Uro”, and game servers."
+    "text": "This approach could potentially lead to a more diverse range of social VR experiences and help grow the Godot Engine community."
   },
   {
-    "objectID": "decisions/20240623-what-is-uro-backend.html#the-problem-statement",
-    "href": "decisions/20240623-what-is-uro-backend.html#the-problem-statement",
-    "title": "Proposed: Why did we build “Uro”?",
+    "objectID": "decisions/20231110-better-pipeline-tools.html#the-downside",
+    "href": "decisions/20231110-better-pipeline-tools.html#the-downside",
+    "title": "Proposed: Enhancing V-Sekai x Godot Engine x AYON for a Superior Workflow",
     "section": "",
-    "text": "There is a need to explain the architecture of V-Sekai, specifically the roles and interactions of the game client, the Uro backend, and the game servers."
+    "text": "Enhancing AYON and creating comprehensive documentation is a time-consuming process and requires ongoing maintenance."
   },
   {
-    "objectID": "decisions/20240623-what-is-uro-backend.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240623-what-is-uro-backend.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Why did we build “Uro”?",
+    "objectID": "decisions/20231110-better-pipeline-tools.html#the-road-not-taken",
+    "href": "decisions/20231110-better-pipeline-tools.html#the-road-not-taken",
+    "title": "Proposed: Enhancing V-Sekai x Godot Engine x AYON for a Superior Workflow",
     "section": "",
-    "text": "The game client is the application that users interact with. It connects to both Uro, our backend service, and directly to game servers.\nThe game editor is a separate tool used by game designers. They use it to create and upload new worlds, props, and avatars to the Uro backend.\nUro is the backend service for our game. It handles requests from both the game client and game editor. It stores and serves game assets like worlds, props, and avatars.\nGame servers are responsible for running the game logic in real-time. They communicate with the game clients to keep the game state synchronized between all players."
+    "text": "An alternative option would be to develop an individual plugin or extension. However, this requires significant resources and may not be feasible for an open-source project."
   },
   {
-    "objectID": "decisions/20240623-what-is-uro-backend.html#the-benefits",
-    "href": "decisions/20240623-what-is-uro-backend.html#the-benefits",
-    "title": "Proposed: Why did we build “Uro”?",
+    "objectID": "decisions/20231110-better-pipeline-tools.html#the-infrequent-use-case",
+    "href": "decisions/20231110-better-pipeline-tools.html#the-infrequent-use-case",
+    "title": "Proposed: Enhancing V-Sekai x Godot Engine x AYON for a Superior Workflow",
     "section": "",
-    "text": "Understanding the architecture of V-Sekai can help developers contribute more effectively to the project. It can also help users troubleshoot issues and understand the capabilities and limitations of the system."
+    "text": "While developing a plugin or extension provides out-of-the-box functionality, it may not cover all use cases and could limit the diversity of social VR experiences."
   },
   {
-    "objectID": "decisions/20240623-what-is-uro-backend.html#the-downsides",
-    "href": "decisions/20240623-what-is-uro-backend.html#the-downsides",
-    "title": "Proposed: Why did we build “Uro”?",
+    "objectID": "decisions/20231110-better-pipeline-tools.html#in-core-and-done-by-us",
+    "href": "decisions/20231110-better-pipeline-tools.html#in-core-and-done-by-us",
+    "title": "Proposed: Enhancing V-Sekai x Godot Engine x AYON for a Superior Workflow",
     "section": "",
-    "text": "The complexity of the architecture may be daunting for some, and there may be a learning curve involved in understanding it."
+    "text": "By focusing on enhancing AYON and creating comprehensive documentation, we are empowering developers to implement these features in their own unique ways."
   },
   {
-    "objectID": "decisions/20240623-what-is-uro-backend.html#the-road-not-taken",
-    "href": "decisions/20240623-what-is-uro-backend.html#the-road-not-taken",
-    "title": "Proposed: Why did we build “Uro”?",
+    "objectID": "decisions/20231110-better-pipeline-tools.html#further-reading",
+    "href": "decisions/20231110-better-pipeline-tools.html#further-reading",
+    "title": "Proposed: Enhancing V-Sekai x Godot Engine x AYON for a Superior Workflow",
     "section": "",
-    "text": "An alternative approach could have been to implement a Peer-to-Peer (P2P) architecture. In this setup, each game client also acts as a mini-server, communicating directly with other clients.\nAnother alternative would be to use cloud-based game backends such as Microsoft’s PlayFab. These services can automatically scale up or down based on demand, ensuring that there’s always enough capacity for all players.\nNakama is an open-source distributed social and realtime server for games and apps. It has a rich feature set including user accounts, chat, social, matchmaker, realtime multiplayer, and much more."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nAYON - The platform hosting our tools and editor\n\n\nThis article was assisted by Aria, an AI assistant."
   },
   {
-    "objectID": "decisions/20240623-what-is-uro-backend.html#the-infrequent-use-case",
-    "href": "decisions/20240623-what-is-uro-backend.html#the-infrequent-use-case",
-    "title": "Proposed: Why did we build “Uro”?",
+    "objectID": "decisions/20240217-intended-effort-versioning.html",
+    "href": "decisions/20240217-intended-effort-versioning.html",
+    "title": "Proposed: Adoption of Intended Effort Versioning (EffVer) in V-Sekai",
     "section": "",
-    "text": "The primary use case for the Uro server is to facilitate interactions between the game client and the game servers, there may be infrequent use cases where its functionality could be extended or used in different ways. For example, it is can be used to implement additional features such as leaderboards, achievements, or social networking features within the game. These use cases, while not common, should still be considered when designing and implementing the Uro server."
+    "text": "V-Sekai currently does not adhere to any specific versioning scheme. This can lead to confusion and inefficiency when users try to adopt new versions of the software.\n\n\n\nWithout a clear versioning system, users may struggle to understand the effort required to adopt new versions of V-Sekai. This can result in wasted time and resources, and potentially deter users from updating to newer versions.\n\n\n\nWe propose adopting EffVer, short for Intended Effort Versioning. This versioning scheme categorizes version increments into Macro, Meso, and Micro, based on the effort needed for adoption—large, some, and little to no effort, respectively.\n# Example of EffVer in action\nversion = \"1.0.0\"  # Initial release\n\n# A micro update requiring little to no effort to adopt\nversion = \"1.0.1\"\n\n# A meso update requiring some effort to adopt\nversion = \"1.1.0\"\n\n# A macro update requiring large effort to adopt\nversion = \"2.0.0\"\n\n\n\nAdopting EffVer would provide clear communication to users about the expected effort required to adopt new versions of V-Sekai. This respects users’ time by quantifying and communicating the adoption effort upfront.\n\n\n\nThe main downside is that it requires the development team to accurately estimate the effort required for each update, which could be subjective and vary between users.\n\n\n\nAlternatives such as Semantic Versioning (SemVer) and Calendar Versioning (CalVer) were considered. However, these focus on technical orthogonality or time of release, rather than the intended impact of changes.\n\n\n\nEffVer may not be as effective for infrequent users who are less familiar with the software and may require more effort to adopt new versions regardless of the changes made.\n\n\n\nThe implementation of EffVer would be done by the V-Sekai development team and integrated into the core project.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team and community stakeholders.\n\n\n\n\n\nV-Sekai, Avatar Customization, AI, Facial Expressions\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nIntended Effort Versioning (EffVer)\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240623-what-is-uro-backend.html#in-core-and-done-by-us",
-    "href": "decisions/20240623-what-is-uro-backend.html#in-core-and-done-by-us",
-    "title": "Proposed: Why did we build “Uro”?",
+    "objectID": "decisions/20240217-intended-effort-versioning.html#the-context",
+    "href": "decisions/20240217-intended-effort-versioning.html#the-context",
+    "title": "Proposed: Adoption of Intended Effort Versioning (EffVer) in V-Sekai",
     "section": "",
-    "text": "This proposal is core to the V-Sekai project and will be implemented by the V-Sekai development team."
+    "text": "V-Sekai currently does not adhere to any specific versioning scheme. This can lead to confusion and inefficiency when users try to adopt new versions of the software."
   },
   {
-    "objectID": "decisions/20240623-what-is-uro-backend.html#status",
-    "href": "decisions/20240623-what-is-uro-backend.html#status",
-    "title": "Proposed: Why did we build “Uro”?",
+    "objectID": "decisions/20240217-intended-effort-versioning.html#the-problem-statement",
+    "href": "decisions/20240217-intended-effort-versioning.html#the-problem-statement",
+    "title": "Proposed: Adoption of Intended Effort Versioning (EffVer) in V-Sekai",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "Without a clear versioning system, users may struggle to understand the effort required to adopt new versions of V-Sekai. This can result in wasted time and resources, and potentially deter users from updating to newer versions."
   },
   {
-    "objectID": "decisions/20240623-what-is-uro-backend.html#decision-makers",
-    "href": "decisions/20240623-what-is-uro-backend.html#decision-makers",
-    "title": "Proposed: Why did we build “Uro”?",
+    "objectID": "decisions/20240217-intended-effort-versioning.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240217-intended-effort-versioning.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Adoption of Intended Effort Versioning (EffVer) in V-Sekai",
     "section": "",
-    "text": "V-Sekai development team\nFire\nAries"
+    "text": "We propose adopting EffVer, short for Intended Effort Versioning. This versioning scheme categorizes version increments into Macro, Meso, and Micro, based on the effort needed for adoption—large, some, and little to no effort, respectively.\n# Example of EffVer in action\nversion = \"1.0.0\"  # Initial release\n\n# A micro update requiring little to no effort to adopt\nversion = \"1.0.1\"\n\n# A meso update requiring some effort to adopt\nversion = \"1.1.0\"\n\n# A macro update requiring large effort to adopt\nversion = \"2.0.0\""
   },
   {
-    "objectID": "decisions/20240623-what-is-uro-backend.html#tags",
-    "href": "decisions/20240623-what-is-uro-backend.html#tags",
-    "title": "Proposed: Why did we build “Uro”?",
+    "objectID": "decisions/20240217-intended-effort-versioning.html#the-benefits",
+    "href": "decisions/20240217-intended-effort-versioning.html#the-benefits",
+    "title": "Proposed: Adoption of Intended Effort Versioning (EffVer) in V-Sekai",
     "section": "",
-    "text": "V-Sekai\nUro Backend\nGame Architecture\nOpen-source Project\nGodot Engine"
+    "text": "Adopting EffVer would provide clear communication to users about the expected effort required to adopt new versions of V-Sekai. This respects users’ time by quantifying and communicating the adoption effort upfront."
   },
   {
-    "objectID": "decisions/20240623-what-is-uro-backend.html#further-reading",
-    "href": "decisions/20240623-what-is-uro-backend.html#further-reading",
-    "title": "Proposed: Why did we build “Uro”?",
+    "objectID": "decisions/20240217-intended-effort-versioning.html#the-downsides",
+    "href": "decisions/20240217-intended-effort-versioning.html#the-downsides",
+    "title": "Proposed: Adoption of Intended Effort Versioning (EffVer) in V-Sekai",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "The main downside is that it requires the development team to accurately estimate the effort required for each update, which could be subjective and vary between users."
   },
   {
-    "objectID": "decisions/20220531-elixir-uro-dev.html",
-    "href": "decisions/20220531-elixir-uro-dev.html",
-    "title": "Accepted: How to start a development environment for cockroach and elixir?",
+    "objectID": "decisions/20240217-intended-effort-versioning.html#the-road-not-taken",
+    "href": "decisions/20240217-intended-effort-versioning.html#the-road-not-taken",
+    "title": "Proposed: Adoption of Intended Effort Versioning (EffVer) in V-Sekai",
     "section": "",
-    "text": "Accepted: How to start a development environment for cockroach and elixir?\n\nDescribe the status of the issue.\n\nproposed\ndraft\nrejected\naccepted\ndeprecated\nsuperseded by\n\n\n\nList the deciders of the issue.\nV-Sekai,lyuma,fire,\n\n\nDescribe the tags of the issue.\nV-Sekai,\n\n\nContext and Problem Statement\nHow do we start our uro backend?\nSee also 20230107-elixir-uro-dev-sqlite.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nWrite documentation how to update elixir.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nDownload the cockroach distribution and run this:\n./cockroach.exe start-single-node  --insecure --store=node1 --listen-addr=localhost:26257 --http-addr=localhost:8080\nYou can add --background to run in the background.\nNext, compile uro. You will need Elixir installed.\nI recommend getting the latest, but for these steps, I am using Elixir v1.13.3.\nDownload Uro from https://github.com/V-Sekai/uro\nWe are using the dev environment. It is the default, but you can also set MIX_ENV=dev.\nTo compile HTML/CSS webpack:\ncd assets\nnpm install\nnpm run deploy\ncd ..\nIf the compile gives issues, you can run it multiple times. To compile dependencies:\nmix do compile, phx.digest\nIf one of them gives an error due to nmake or not having a compiler, you can fix it by opening a x64 Native Tools command prompt from visual studio and run mix deps.compile bcrypt_elixir\nFinally, create and migrate the database and start the development server:\nmix ecto.create\nmix ecto.migrate\nmix phx.server\nThis will start uro at http://localhost:4000/\nGitHub - V-Sekai/uro: Server backend for V-Sekai written in Elixir …\nThe docker image docker-uro is compiled using GoCD, so after pushing, check that the pipeline ran.\nThen, go to DockerHub at https://hub.docker.com/r/groupsinfra/uro/tags and check the most recently pushed tag (it will not be the latest one, but instead a specific version).\nNow, edit the flux config at https://github.com/V-Sekai/flux-config/blob/flux2/workloads/uro-deployment.yaml and replace the uro image version with the tag from above.\nCheck that uro-deployment was updated.\n\n\nPositive Consequences\nWe’re able to update uro!\n\n\nNegative Consequences\nNo response\n\n\nOption graveyard\nNo response\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nIt’s arguably a few lines of script, but it’s our script!\n\n\nIs there a reason why this should be core and done by us?\nWe maintain the website.\n\n\nReferences\n\nV-Sekai\nUro\nhttps://github.com/V-Sekai/uro/issues/52\n\n\n\nLicense of the contribution\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Alternatives such as Semantic Versioning (SemVer) and Calendar Versioning (CalVer) were considered. However, these focus on technical orthogonality or time of release, rather than the intended impact of changes."
   },
   {
-    "objectID": "decisions/20231203-mesh-rwkv.html",
-    "href": "decisions/20231203-mesh-rwkv.html",
-    "title": "Proposed: Triangle Meshes Inferencing with MeshRWKV",
+    "objectID": "decisions/20240217-intended-effort-versioning.html#the-infrequent-use-case",
+    "href": "decisions/20240217-intended-effort-versioning.html#the-infrequent-use-case",
+    "title": "Proposed: Adoption of Intended Effort Versioning (EffVer) in V-Sekai",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nMeshGPT uses a transformer model trained on geometric vocabulary to generate triangle meshes, resulting in clean, coherent, and compact meshes.\n\n\n\nAdapting GPT-like generative models for the 3D domain is a challenge. Automated triangle mesh generation needs a robust solution.\n\n\n\nThe MeshRWKV model employs a sequence-based approach that autoregressively generates triangle meshes as sequences of triangles. The conversion process to RWKV4 can be broken down into two primary steps:\n\n\nThe initial step involves learning a vocabulary that can accurately represent triangle meshes from a large collection of 3D object meshes. This enables the encoding and decoding of triangles from this embedding.\nA graph convolution encoder, specifically a series of SAGE-Conv graph convolution layers, is utilized in this process. This encoder processes the mesh in the form of a face graph. For each graph node, input features include the positionally encoded 9 coordinates of the face triangle, its area, the angles between its edges, and the normal of the face.\nThese geometrically rich features capture the intricate details of 3D shapes and are quantized as embeddings of a codebook using residual quantization. This effectively reduces the sequence lengths of the mesh representation.\nThese embeddings are then sequenced and decoded by a 1D ResNet-34 network, which interprets the face features as a 1D sequence. It outputs logits corresponding to the 9 discrete coordinates of each face triangle. The size of the codebook C and the discretization space are determined based on the specific requirements and constraints of the model.\n\n\n\nThe next step is to train RWKV4, which leverages these quantized geometric embeddings. Given a sequence of geometric embeddings extracted from the triangles of a mesh, the transformer is trained to predict the codebook index of the next embedding in the sequence.\nOnce trained, the transformer can be auto-regressively sampled to predict sequences of embeddings. These embeddings can then be decoded to generate novel and diverse mesh structures that display efficient, irregular triangulations similar to human-crafted meshes.\n\n\n\nMeshGPT has made significant strides in the field of direct mesh generation, but it is not without its limitations. The autoregressive nature of the model results in slower sampling performance, with mesh generation times ranging from 30 to 90 seconds. The MeshGPT team’s learned tokenization approach has been successful in reducing sequence lengths for single object generation, but it may not be as effective when applied to scene-scale generation. This presents an opportunity for future enhancement.\nFurthermore, MeshGPT’s current computational resources restrict it to using the GPT2-medium transformer, which is less sophisticated than models like Llama2. Given that larger language models tend to benefit from increased data and computational power, expanding these resources could significantly enhance MeshGPT’s performance and capabilities.\nIt’s important to note that the RWKV (Receptance Weighted Key Value) model’s context size is significantly larger than that of GPT2. In machine learning, context size refers to the amount of information from previous steps that a model can consider while making predictions for the next step. It essentially determines how much ‘memory’ the model has about past data.\nThe larger context size of RWKV means that it can remember and utilize more past information while generating outputs. This feature potentially enables it to handle larger and more complex tasks, provided there are sufficient computational resources.\nHowever, a larger context size also implies higher computational demands. More processing power and memory are required to store and manage such large amounts of data. This could pose challenges in terms of hardware requirements and efficiency, particularly when dealing with very large datasets or complex tasks.\n\n\n\n\nOur approach produces compact meshes with sharp geometric details. It can suggest multiple shape completions for incomplete shapes.\n\n\n\nGiven that the MeshGPT model has already developed a process for converting mesh data into logits, this simplifies the task of applying the MeshRWKV model to skeletal animation.\nThe fundamental concept would involve representing a sequence of animation frames (from frame0 to frameN) as meshes. The recursive nature of RWKV could potentially offer significant advantages in this scenario. It might facilitate efficient encoding and decoding of sequential frames, which could lead to the generation of smooth and coherent animations.\nWith the mesh-to-logits conversion challenge addressed by MeshGPT, the primary focus can be on developing new training methodologies and loss functions tailored for animation data. This approach could significantly broaden the applicability of the MeshRWKV model, opening up exciting possibilities for future research and development in the field of 3D animation.\n\n\n\nTraining the model may require significant computational resources. Learning a vocabulary for triangle meshes could be complex.\n\n\n\nOther methods like neural field-based approaches exist but often miss geometric details or produce over-triangulated meshes.\n\n\n\nGenerating complex 3D shapes for niche applications might need additional model training or fine-tuning.\n\n\n\nYes, this proposal is core to our work at V-Sekai and will be implemented by us.\n\n\n\n\nV-Sekai · GitHub\nV-Sekai/v-sekai-game\nMeshGPT\nObjaverse-XL\nNous-Hermes-2-Vision\nMachine Learning in Elixir\nPyTorch Geometric SAGEConv\nInductive Representation Learning on Large Graphs\n\nAssisted by AI assistant Aria."
+    "text": "EffVer may not be as effective for infrequent users who are less familiar with the software and may require more effort to adopt new versions regardless of the changes made."
   },
   {
-    "objectID": "decisions/20231203-mesh-rwkv.html#metadata",
-    "href": "decisions/20231203-mesh-rwkv.html#metadata",
-    "title": "Proposed: Triangle Meshes Inferencing with MeshRWKV",
+    "objectID": "decisions/20240217-intended-effort-versioning.html#in-core-and-done-by-us",
+    "href": "decisions/20240217-intended-effort-versioning.html#in-core-and-done-by-us",
+    "title": "Proposed: Adoption of Intended Effort Versioning (EffVer) in V-Sekai",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai"
+    "text": "The implementation of EffVer would be done by the V-Sekai development team and integrated into the core project."
   },
   {
-    "objectID": "decisions/20231203-mesh-rwkv.html#background",
-    "href": "decisions/20231203-mesh-rwkv.html#background",
-    "title": "Proposed: Triangle Meshes Inferencing with MeshRWKV",
+    "objectID": "decisions/20240217-intended-effort-versioning.html#status",
+    "href": "decisions/20240217-intended-effort-versioning.html#status",
+    "title": "Proposed: Adoption of Intended Effort Versioning (EffVer) in V-Sekai",
     "section": "",
-    "text": "MeshGPT uses a transformer model trained on geometric vocabulary to generate triangle meshes, resulting in clean, coherent, and compact meshes."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20231203-mesh-rwkv.html#problem",
-    "href": "decisions/20231203-mesh-rwkv.html#problem",
-    "title": "Proposed: Triangle Meshes Inferencing with MeshRWKV",
+    "objectID": "decisions/20240217-intended-effort-versioning.html#decision-makers",
+    "href": "decisions/20240217-intended-effort-versioning.html#decision-makers",
+    "title": "Proposed: Adoption of Intended Effort Versioning (EffVer) in V-Sekai",
     "section": "",
-    "text": "Adapting GPT-like generative models for the 3D domain is a challenge. Automated triangle mesh generation needs a robust solution."
+    "text": "V-Sekai development team and community stakeholders."
   },
   {
-    "objectID": "decisions/20231203-mesh-rwkv.html#strategy",
-    "href": "decisions/20231203-mesh-rwkv.html#strategy",
-    "title": "Proposed: Triangle Meshes Inferencing with MeshRWKV",
+    "objectID": "decisions/20240217-intended-effort-versioning.html#tags",
+    "href": "decisions/20240217-intended-effort-versioning.html#tags",
+    "title": "Proposed: Adoption of Intended Effort Versioning (EffVer) in V-Sekai",
     "section": "",
-    "text": "The MeshRWKV model employs a sequence-based approach that autoregressively generates triangle meshes as sequences of triangles. The conversion process to RWKV4 can be broken down into two primary steps:\n\n\nThe initial step involves learning a vocabulary that can accurately represent triangle meshes from a large collection of 3D object meshes. This enables the encoding and decoding of triangles from this embedding.\nA graph convolution encoder, specifically a series of SAGE-Conv graph convolution layers, is utilized in this process. This encoder processes the mesh in the form of a face graph. For each graph node, input features include the positionally encoded 9 coordinates of the face triangle, its area, the angles between its edges, and the normal of the face.\nThese geometrically rich features capture the intricate details of 3D shapes and are quantized as embeddings of a codebook using residual quantization. This effectively reduces the sequence lengths of the mesh representation.\nThese embeddings are then sequenced and decoded by a 1D ResNet-34 network, which interprets the face features as a 1D sequence. It outputs logits corresponding to the 9 discrete coordinates of each face triangle. The size of the codebook C and the discretization space are determined based on the specific requirements and constraints of the model.\n\n\n\nThe next step is to train RWKV4, which leverages these quantized geometric embeddings. Given a sequence of geometric embeddings extracted from the triangles of a mesh, the transformer is trained to predict the codebook index of the next embedding in the sequence.\nOnce trained, the transformer can be auto-regressively sampled to predict sequences of embeddings. These embeddings can then be decoded to generate novel and diverse mesh structures that display efficient, irregular triangulations similar to human-crafted meshes.\n\n\n\nMeshGPT has made significant strides in the field of direct mesh generation, but it is not without its limitations. The autoregressive nature of the model results in slower sampling performance, with mesh generation times ranging from 30 to 90 seconds. The MeshGPT team’s learned tokenization approach has been successful in reducing sequence lengths for single object generation, but it may not be as effective when applied to scene-scale generation. This presents an opportunity for future enhancement.\nFurthermore, MeshGPT’s current computational resources restrict it to using the GPT2-medium transformer, which is less sophisticated than models like Llama2. Given that larger language models tend to benefit from increased data and computational power, expanding these resources could significantly enhance MeshGPT’s performance and capabilities.\nIt’s important to note that the RWKV (Receptance Weighted Key Value) model’s context size is significantly larger than that of GPT2. In machine learning, context size refers to the amount of information from previous steps that a model can consider while making predictions for the next step. It essentially determines how much ‘memory’ the model has about past data.\nThe larger context size of RWKV means that it can remember and utilize more past information while generating outputs. This feature potentially enables it to handle larger and more complex tasks, provided there are sufficient computational resources.\nHowever, a larger context size also implies higher computational demands. More processing power and memory are required to store and manage such large amounts of data. This could pose challenges in terms of hardware requirements and efficiency, particularly when dealing with very large datasets or complex tasks."
+    "text": "V-Sekai, Avatar Customization, AI, Facial Expressions"
   },
   {
-    "objectID": "decisions/20231203-mesh-rwkv.html#benefits",
-    "href": "decisions/20231203-mesh-rwkv.html#benefits",
-    "title": "Proposed: Triangle Meshes Inferencing with MeshRWKV",
+    "objectID": "decisions/20240217-intended-effort-versioning.html#further-reading",
+    "href": "decisions/20240217-intended-effort-versioning.html#further-reading",
+    "title": "Proposed: Adoption of Intended Effort Versioning (EffVer) in V-Sekai",
     "section": "",
-    "text": "Our approach produces compact meshes with sharp geometric details. It can suggest multiple shape completions for incomplete shapes."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nIntended Effort Versioning (EffVer)\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20231203-mesh-rwkv.html#future-work",
-    "href": "decisions/20231203-mesh-rwkv.html#future-work",
-    "title": "Proposed: Triangle Meshes Inferencing with MeshRWKV",
+    "objectID": "decisions/20230614-llm-statechart.html",
+    "href": "decisions/20230614-llm-statechart.html",
+    "title": "Proposed: Increase variety and quality with generated animation trees",
     "section": "",
-    "text": "Given that the MeshGPT model has already developed a process for converting mesh data into logits, this simplifies the task of applying the MeshRWKV model to skeletal animation.\nThe fundamental concept would involve representing a sequence of animation frames (from frame0 to frameN) as meshes. The recursive nature of RWKV could potentially offer significant advantages in this scenario. It might facilitate efficient encoding and decoding of sequential frames, which could lead to the generation of smooth and coherent animations.\nWith the mesh-to-logits conversion challenge addressed by MeshGPT, the primary focus can be on developing new training methodologies and loss functions tailored for animation data. This approach could significantly broaden the applicability of the MeshRWKV model, opening up exciting possibilities for future research and development in the field of 3D animation."
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, ai assisted\n\n\n\n\nGenerate an AnimationTrees with blend trees and nested state machines as a startchart json.\n\n\n\nCreate a script that generates a JSON file representing the AnimationTrees structure, including blend trees and nested state machines. This JSON file can then be used to create the corresponding AnimationTrees in the V-Sekai engine.\n\n\n\n\nDefine the JSON schema for the AnimationTrees structure.\nCreate a script that reads the existing AnimationTrees data and converts it into the defined JSON format.\nImplement a function in the V-Sekai engine that reads the generated JSON file and creates the corresponding AnimationTrees.\n\n\n\n\n\nEasier management and sharing of AnimationTrees structures.\nSimplified collaboration between developers working on the same project.\nPotential for automation and procedural generation of AnimationTrees.\n\n\n\n\n\nAdditional development time required to implement the JSON conversion script and the corresponding function in the V-Sekai engine.\nPossible performance overhead when reading and parsing the JSON file.\n\n\n\n\n\nManually creating and managing AnimationTrees structures without using a JSON representation.\n\n\n\n\nNo, this enhancement aims to simplify the management and sharing of complex AnimationTrees structures, which cannot be easily achieved with just a few lines of script.\n\n\n\nYes, implementing this feature as part of the core V-Sekai engine ensures consistency and compatibility across different projects and developers using the engine.\n\n\n\n\nV-Sekai\njsonformer\nintegrations/jsonformer_experimental"
   },
   {
-    "objectID": "decisions/20231203-mesh-rwkv.html#drawbacks",
-    "href": "decisions/20231203-mesh-rwkv.html#drawbacks",
-    "title": "Proposed: Triangle Meshes Inferencing with MeshRWKV",
+    "objectID": "decisions/20230614-llm-statechart.html#metadata",
+    "href": "decisions/20230614-llm-statechart.html#metadata",
+    "title": "Proposed: Increase variety and quality with generated animation trees",
     "section": "",
-    "text": "Training the model may require significant computational resources. Learning a vocabulary for triangle meshes could be complex."
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, ai assisted"
   },
   {
-    "objectID": "decisions/20231203-mesh-rwkv.html#alternatives",
-    "href": "decisions/20231203-mesh-rwkv.html#alternatives",
-    "title": "Proposed: Triangle Meshes Inferencing with MeshRWKV",
+    "objectID": "decisions/20230614-llm-statechart.html#context-and-problem-statement",
+    "href": "decisions/20230614-llm-statechart.html#context-and-problem-statement",
+    "title": "Proposed: Increase variety and quality with generated animation trees",
     "section": "",
-    "text": "Other methods like neural field-based approaches exist but often miss geometric details or produce over-triangulated meshes."
+    "text": "Generate an AnimationTrees with blend trees and nested state machines as a startchart json."
   },
   {
-    "objectID": "decisions/20231203-mesh-rwkv.html#special-use-case",
-    "href": "decisions/20231203-mesh-rwkv.html#special-use-case",
-    "title": "Proposed: Triangle Meshes Inferencing with MeshRWKV",
+    "objectID": "decisions/20230614-llm-statechart.html#proposed-solution",
+    "href": "decisions/20230614-llm-statechart.html#proposed-solution",
+    "title": "Proposed: Increase variety and quality with generated animation trees",
     "section": "",
-    "text": "Generating complex 3D shapes for niche applications might need additional model training or fine-tuning."
+    "text": "Create a script that generates a JSON file representing the AnimationTrees structure, including blend trees and nested state machines. This JSON file can then be used to create the corresponding AnimationTrees in the V-Sekai engine."
   },
   {
-    "objectID": "decisions/20231203-mesh-rwkv.html#core-implemented-by-us",
-    "href": "decisions/20231203-mesh-rwkv.html#core-implemented-by-us",
-    "title": "Proposed: Triangle Meshes Inferencing with MeshRWKV",
+    "objectID": "decisions/20230614-llm-statechart.html#implementation",
+    "href": "decisions/20230614-llm-statechart.html#implementation",
+    "title": "Proposed: Increase variety and quality with generated animation trees",
     "section": "",
-    "text": "Yes, this proposal is core to our work at V-Sekai and will be implemented by us."
+    "text": "Define the JSON schema for the AnimationTrees structure.\nCreate a script that reads the existing AnimationTrees data and converts it into the defined JSON format.\nImplement a function in the V-Sekai engine that reads the generated JSON file and creates the corresponding AnimationTrees."
   },
   {
-    "objectID": "decisions/20231203-mesh-rwkv.html#references",
-    "href": "decisions/20231203-mesh-rwkv.html#references",
-    "title": "Proposed: Triangle Meshes Inferencing with MeshRWKV",
+    "objectID": "decisions/20230614-llm-statechart.html#positive-consequences",
+    "href": "decisions/20230614-llm-statechart.html#positive-consequences",
+    "title": "Proposed: Increase variety and quality with generated animation trees",
     "section": "",
-    "text": "V-Sekai · GitHub\nV-Sekai/v-sekai-game\nMeshGPT\nObjaverse-XL\nNous-Hermes-2-Vision\nMachine Learning in Elixir\nPyTorch Geometric SAGEConv\nInductive Representation Learning on Large Graphs\n\nAssisted by AI assistant Aria."
+    "text": "Easier management and sharing of AnimationTrees structures.\nSimplified collaboration between developers working on the same project.\nPotential for automation and procedural generation of AnimationTrees."
   },
   {
-    "objectID": "decisions/20230123-use-easy-charts-for-observability.html",
-    "href": "decisions/20230123-use-easy-charts-for-observability.html",
-    "title": "Proposed: Use Easy Charts for observability",
+    "objectID": "decisions/20230614-llm-statechart.html#negative-consequences",
+    "href": "decisions/20230614-llm-statechart.html#negative-consequences",
+    "title": "Proposed: Increase variety and quality with generated animation trees",
     "section": "",
-    "text": "Proposed: Use Easy Charts for observability\n\nMetadata\n\nStatus: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nContext and Problem Statement\nWe would like to visualize metrics in-game.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nPort https://github.com/fenix-hub/godot-engine.easy-charts to v-sekai\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\n\nCreate a project in 4\nAdd easy charts as a addon\nUse the auto migrate in 4\nFix missing\n\n\n\nPositive Consequences\nWe are able to use V-Sekai easier to debug.\n\n\nNegative Consequences\nWe cannot get other features in.\n\n\nOption graveyard\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nEasy charts is not a few lines of script.\n\n\nIs there a reason why this should be core and done by us?\nToo low performance impacts usability.\n\n\nReferences\n\nV-Sekai\nhttps://github.com/fenix-hub/godot-engine.easy-charts"
+    "text": "Additional development time required to implement the JSON conversion script and the corresponding function in the V-Sekai engine.\nPossible performance overhead when reading and parsing the JSON file."
   },
   {
-    "objectID": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html",
-    "href": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html",
-    "title": "Proposed: Phase out groups in the branding to make it more recognizable",
+    "objectID": "decisions/20230614-llm-statechart.html#option-graveyard",
+    "href": "decisions/20230614-llm-statechart.html#option-graveyard",
+    "title": "Proposed: Increase variety and quality with generated animation trees",
     "section": "",
-    "text": "Need to find recognizable brands.\n\n\n\nPhase out the ‘groups’ terminology as much as possible because it was too generic and can easily get mixed up with other things.\n\n\n\nReplace vsk_default for the groups in the Godot project.\n\n\n\n\n[e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]\n[…]\n\n\n\n\n\n[e.g., compromising quality attribute, follow-up decisions required, …]\n[…]\n\n[this section can be repeated for each option if more than one option is open for consideration]\n\n\n\n\nOption: \nRejection Reason: \n\n\n\n\nNot a script.\n\n\n\nWe use the groups branding.\n\n\n\n\nLink type \n… \n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Manually creating and managing AnimationTrees structures without using a JSON representation."
   },
   {
-    "objectID": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html#context-and-problem-statement",
-    "href": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html#context-and-problem-statement",
-    "title": "Proposed: Phase out groups in the branding to make it more recognizable",
+    "objectID": "decisions/20230614-llm-statechart.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230614-llm-statechart.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Increase variety and quality with generated animation trees",
     "section": "",
-    "text": "Need to find recognizable brands."
+    "text": "No, this enhancement aims to simplify the management and sharing of complex AnimationTrees structures, which cannot be easily achieved with just a few lines of script."
   },
   {
-    "objectID": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: Phase out groups in the branding to make it more recognizable",
+    "objectID": "decisions/20230614-llm-statechart.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230614-llm-statechart.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Increase variety and quality with generated animation trees",
     "section": "",
-    "text": "Phase out the ‘groups’ terminology as much as possible because it was too generic and can easily get mixed up with other things."
+    "text": "Yes, implementing this feature as part of the core V-Sekai engine ensures consistency and compatibility across different projects and developers using the engine."
   },
   {
-    "objectID": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Phase out groups in the branding to make it more recognizable",
+    "objectID": "decisions/20230614-llm-statechart.html#references",
+    "href": "decisions/20230614-llm-statechart.html#references",
+    "title": "Proposed: Increase variety and quality with generated animation trees",
     "section": "",
-    "text": "Replace vsk_default for the groups in the Godot project."
+    "text": "V-Sekai\njsonformer\nintegrations/jsonformer_experimental"
   },
   {
-    "objectID": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html#positive-consequences",
-    "href": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html#positive-consequences",
-    "title": "Proposed: Phase out groups in the branding to make it more recognizable",
+    "objectID": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html",
+    "href": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html",
+    "title": "Proposed: Train quad-based Meshgpt within constraints",
     "section": "",
-    "text": "[e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]\n[…]"
+    "text": "The goal is to train a MeshGPT model for quad-based geometry with limited resources of one day using fixed Nvidia GPU hardware to evaluate its performance.\n\n\n\nDescribe a workflow for training Meshgpt with quad-based meshes to create a set of LODs (Level of Detail) within the given constraints.\n\n\n\n\nData Preparation: Collect a diverse dataset of quad-based meshes suitable for generating LODs. This involves cleaning and normalizing the data to ensure consistency and remove inconsistencies or errors. Categorizing the data based on complexity and size allows for targeted training and model performance evaluation across different mesh types. A requirement is to attribute every available source 3d model. Gather a dataset of quad-based meshes representing various objects within the distance range of interest.\nModel Architecture Selection: Choose an appropriate language model architecture to handle geometric data effectively. MeshGPT could be a good starting point due to its success in handling 3D mesh generation tasks.\nBatch Processing Technique: Implement a batch processing technique to optimize the use of GPU resources.\nHyperparameter Tuning: Fine-tune the hyperparameters, such as learning rate, batch size, and number of layers, to achieve optimal performance within the given time constraint. This may involve experimentation with different values and configurations to find the best setup for the chosen model architecture and dataset.\nTraining Process: Train the MeshGPT model using the prepared dataset with the chosen architecture, optimized batch processing technique, and fine-tuned hyperparameters for over one day. This involves monitoring the training process and making necessary adjustments to ensure optimal performance within the given timeframe.\nEvaluation: Evaluate the trained model’s performance by generating LODs for a diverse quad-based mesh and comparing them to ground truth data or existing LOD generation methods.\nResults Analysis: Analyze the results obtained from the evaluation stage, focusing on metrics such as accuracy, speed, and resource usage.\n\n\n\n\n\nEfficient utilization of Video RAM in training large language models for mesh generation tasks.\nAbility to train the MeshGPT model within a one-day timeframe.\nImproved LOD generation capabilities for quad-based meshes.\n\n\n\n\n\nLimited flexibility due to the constraint of Video RAM.\nTraining large language models can be computationally intensive and require significant processing power, potentially impacting system performance.\nRequires careful hyperparameter tuning for optimal results within the given timeframe.\n\n\n\n\n\nUsing less powerful hardware or smaller video RAM would result in longer training times or lower model capacity.\nOpting for a more complex model architecture without optimizations could lead to overfitting and poor performance on the LOD generation task.\n\n\n\n\nIn cases where more advanced GPU hardware is available, this workflow may not be necessary as it would allow for larger models or longer training times, potentially resulting in better performance. However, the proposed workflow can be a starting point for those with limited resources or time constraints.\n\n\n\n\nWorkflow design specifically tailored to train MeshGPT on quad-based meshes within one day using a fixed sized video RAM.\nHyperparameter tuning and optimization techniques are implemented to maximize performance under the given constraints.\n\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nRunpod\nMeshGPT with Quads\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html#negative-consequences",
-    "href": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html#negative-consequences",
-    "title": "Proposed: Phase out groups in the branding to make it more recognizable",
+    "objectID": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#the-context",
+    "href": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#the-context",
+    "title": "Proposed: Train quad-based Meshgpt within constraints",
     "section": "",
-    "text": "[e.g., compromising quality attribute, follow-up decisions required, …]\n[…]\n\n[this section can be repeated for each option if more than one option is open for consideration]"
+    "text": "The goal is to train a MeshGPT model for quad-based geometry with limited resources of one day using fixed Nvidia GPU hardware to evaluate its performance."
   },
   {
-    "objectID": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html#option-graveyard",
-    "href": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html#option-graveyard",
-    "title": "Proposed: Phase out groups in the branding to make it more recognizable",
+    "objectID": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#the-problem-statement",
+    "href": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#the-problem-statement",
+    "title": "Proposed: Train quad-based Meshgpt within constraints",
     "section": "",
-    "text": "Option: \nRejection Reason:"
+    "text": "Describe a workflow for training Meshgpt with quad-based meshes to create a set of LODs (Level of Detail) within the given constraints."
   },
   {
-    "objectID": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Phase out groups in the branding to make it more recognizable",
+    "objectID": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#proposed-workflow-with-data-selection-section",
+    "href": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#proposed-workflow-with-data-selection-section",
+    "title": "Proposed: Train quad-based Meshgpt within constraints",
     "section": "",
-    "text": "Not a script."
+    "text": "Data Preparation: Collect a diverse dataset of quad-based meshes suitable for generating LODs. This involves cleaning and normalizing the data to ensure consistency and remove inconsistencies or errors. Categorizing the data based on complexity and size allows for targeted training and model performance evaluation across different mesh types. A requirement is to attribute every available source 3d model. Gather a dataset of quad-based meshes representing various objects within the distance range of interest.\nModel Architecture Selection: Choose an appropriate language model architecture to handle geometric data effectively. MeshGPT could be a good starting point due to its success in handling 3D mesh generation tasks.\nBatch Processing Technique: Implement a batch processing technique to optimize the use of GPU resources.\nHyperparameter Tuning: Fine-tune the hyperparameters, such as learning rate, batch size, and number of layers, to achieve optimal performance within the given time constraint. This may involve experimentation with different values and configurations to find the best setup for the chosen model architecture and dataset.\nTraining Process: Train the MeshGPT model using the prepared dataset with the chosen architecture, optimized batch processing technique, and fine-tuned hyperparameters for over one day. This involves monitoring the training process and making necessary adjustments to ensure optimal performance within the given timeframe.\nEvaluation: Evaluate the trained model’s performance by generating LODs for a diverse quad-based mesh and comparing them to ground truth data or existing LOD generation methods.\nResults Analysis: Analyze the results obtained from the evaluation stage, focusing on metrics such as accuracy, speed, and resource usage."
   },
   {
-    "objectID": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Phase out groups in the branding to make it more recognizable",
+    "objectID": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#the-benefits",
+    "href": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#the-benefits",
+    "title": "Proposed: Train quad-based Meshgpt within constraints",
     "section": "",
-    "text": "We use the groups branding."
+    "text": "Efficient utilization of Video RAM in training large language models for mesh generation tasks.\nAbility to train the MeshGPT model within a one-day timeframe.\nImproved LOD generation capabilities for quad-based meshes."
   },
   {
-    "objectID": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html#references",
-    "href": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html#references",
-    "title": "Proposed: Phase out groups in the branding to make it more recognizable",
+    "objectID": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#the-downsides",
+    "href": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#the-downsides",
+    "title": "Proposed: Train quad-based Meshgpt within constraints",
     "section": "",
-    "text": "Link type \n…"
+    "text": "Limited flexibility due to the constraint of Video RAM.\nTraining large language models can be computationally intensive and require significant processing power, potentially impacting system performance.\nRequires careful hyperparameter tuning for optimal results within the given timeframe."
   },
   {
-    "objectID": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html#derivative-license",
-    "href": "decisions/20211031-phase-out-groups-terminology-for-vskdefault.html#derivative-license",
-    "title": "Proposed: Phase out groups in the branding to make it more recognizable",
+    "objectID": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#the-road-not-taken",
+    "href": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#the-road-not-taken",
+    "title": "Proposed: Train quad-based Meshgpt within constraints",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Using less powerful hardware or smaller video RAM would result in longer training times or lower model capacity.\nOpting for a more complex model architecture without optimizations could lead to overfitting and poor performance on the LOD generation task."
   },
   {
-    "objectID": "decisions/20240502-mesh-object-sync-benchmark.html",
-    "href": "decisions/20240502-mesh-object-sync-benchmark.html",
-    "title": "Proposed: Stress Testing Godot Engine’s Networking System",
+    "objectID": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#the-infrequent-use-case",
+    "href": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#the-infrequent-use-case",
+    "title": "Proposed: Train quad-based Meshgpt within constraints",
     "section": "",
-    "text": "The V-Sekai development team is working on a project that involves avatar, world, and prop collaboration workflow in the Godot engine. The team plans to use FoundationDB with SQLite to enhance the performance of this workflow.\n\n\n\nWe need to ensure that the networking system of the Godot engine can handle the increased load and perform optimally under stress.\n\n\n\nCreate in three stages:\n\nlocal client to local server\nlocal client to remote server\nremote client to remote server\n\nDoes not test infrastructure implementation.\nWe propose to conduct stress testing on the Godot engine’s networking system.\nThis will involve creating multiple virtual users and simulating high traffic scenarios to evaluate how the system performs under heavy load.\n# This is a single node example.\n# Assuming we have a list of props and a World instance\nvar props = [prop1, prop2, prop3]\nvar world = World.new()\n\nfor i in range(10): # Simulate 10 users\n    var user = User.new() # Create a new user\n    var selected_props = [] # List to store selected props\n\n    for _ in range(randi()%props.size()+1): # Randomly select props\n        var prop = props[randi()%props.size()]\n        selected_props.append(prop)\n\n    user.glue_props(selected_props) # Glue selected props together\n    world.merge(user.get_changed_world()) # Merge the changed world into the main world\n\n# Now, let's read back the changed world\nprint(world.get_state())\n# To be determined realistic multclient version.\nTest personal computer and digital ocean.\n\n\n\n\nIdentify potential bottlenecks in the system.\nEnsure the system can handle high traffic without compromising performance.\nImprove overall system reliability and user experience.\n\n\n\n\n\nRequires time and resources to set up and conduct the tests.\nPotential for false positives or negatives due to the simulated nature of the test.\n\n\n\n\nAn alternative would be to skip stress testing and directly implement the system. However, this could lead to unforeseen issues in a live environment, potentially affecting user experience.\n\n\n\nIn cases where the traffic is consistently low, stress testing may not provide significant benefits. However, it’s still important to prepare for potential spikes in usage.\n\n\n\nThe proposed stress testing will be conducted by the V-Sekai development team.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nStress testing Unity’s LLAPI, what are the limits?\nCrappy Contraption\n\nThis proposal was assisted by Aria, an AI assistant."
+    "text": "In cases where more advanced GPU hardware is available, this workflow may not be necessary as it would allow for larger models or longer training times, potentially resulting in better performance. However, the proposed workflow can be a starting point for those with limited resources or time constraints."
   },
   {
-    "objectID": "decisions/20240502-mesh-object-sync-benchmark.html#context",
-    "href": "decisions/20240502-mesh-object-sync-benchmark.html#context",
-    "title": "Proposed: Stress Testing Godot Engine’s Networking System",
+    "objectID": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#in-core-and-done-by-us",
+    "href": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#in-core-and-done-by-us",
+    "title": "Proposed: Train quad-based Meshgpt within constraints",
     "section": "",
-    "text": "The V-Sekai development team is working on a project that involves avatar, world, and prop collaboration workflow in the Godot engine. The team plans to use FoundationDB with SQLite to enhance the performance of this workflow."
+    "text": "Workflow design specifically tailored to train MeshGPT on quad-based meshes within one day using a fixed sized video RAM.\nHyperparameter tuning and optimization techniques are implemented to maximize performance under the given constraints."
   },
   {
-    "objectID": "decisions/20240502-mesh-object-sync-benchmark.html#problem-statement",
-    "href": "decisions/20240502-mesh-object-sync-benchmark.html#problem-statement",
-    "title": "Proposed: Stress Testing Godot Engine’s Networking System",
+    "objectID": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#status",
+    "href": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#status",
+    "title": "Proposed: Train quad-based Meshgpt within constraints",
     "section": "",
-    "text": "We need to ensure that the networking system of the Godot engine can handle the increased load and perform optimally under stress."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20240502-mesh-object-sync-benchmark.html#solution",
-    "href": "decisions/20240502-mesh-object-sync-benchmark.html#solution",
-    "title": "Proposed: Stress Testing Godot Engine’s Networking System",
+    "objectID": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#decision-makers",
+    "href": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#decision-makers",
+    "title": "Proposed: Train quad-based Meshgpt within constraints",
     "section": "",
-    "text": "Create in three stages:\n\nlocal client to local server\nlocal client to remote server\nremote client to remote server\n\nDoes not test infrastructure implementation.\nWe propose to conduct stress testing on the Godot engine’s networking system.\nThis will involve creating multiple virtual users and simulating high traffic scenarios to evaluate how the system performs under heavy load.\n# This is a single node example.\n# Assuming we have a list of props and a World instance\nvar props = [prop1, prop2, prop3]\nvar world = World.new()\n\nfor i in range(10): # Simulate 10 users\n    var user = User.new() # Create a new user\n    var selected_props = [] # List to store selected props\n\n    for _ in range(randi()%props.size()+1): # Randomly select props\n        var prop = props[randi()%props.size()]\n        selected_props.append(prop)\n\n    user.glue_props(selected_props) # Glue selected props together\n    world.merge(user.get_changed_world()) # Merge the changed world into the main world\n\n# Now, let's read back the changed world\nprint(world.get_state())\n# To be determined realistic multclient version.\nTest personal computer and digital ocean."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20240502-mesh-object-sync-benchmark.html#benefits",
-    "href": "decisions/20240502-mesh-object-sync-benchmark.html#benefits",
-    "title": "Proposed: Stress Testing Godot Engine’s Networking System",
+    "objectID": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#tags",
+    "href": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#tags",
+    "title": "Proposed: Train quad-based Meshgpt within constraints",
     "section": "",
-    "text": "Identify potential bottlenecks in the system.\nEnsure the system can handle high traffic without compromising performance.\nImprove overall system reliability and user experience."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20240502-mesh-object-sync-benchmark.html#downsides",
-    "href": "decisions/20240502-mesh-object-sync-benchmark.html#downsides",
-    "title": "Proposed: Stress Testing Godot Engine’s Networking System",
+    "objectID": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#further-reading",
+    "href": "decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html#further-reading",
+    "title": "Proposed: Train quad-based Meshgpt within constraints",
     "section": "",
-    "text": "Requires time and resources to set up and conduct the tests.\nPotential for false positives or negatives due to the simulated nature of the test."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nRunpod\nMeshGPT with Quads\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240502-mesh-object-sync-benchmark.html#the-road-not-taken",
-    "href": "decisions/20240502-mesh-object-sync-benchmark.html#the-road-not-taken",
-    "title": "Proposed: Stress Testing Godot Engine’s Networking System",
+    "objectID": "decisions/20230429-v-sekai-roadmap.html",
+    "href": "decisions/20230429-v-sekai-roadmap.html",
+    "title": "Superseded: V-Sekai Roadmap and Goals 2023-04-20",
     "section": "",
-    "text": "An alternative would be to skip stress testing and directly implement the system. However, this could lead to unforeseen issues in a live environment, potentially affecting user experience."
+    "text": "Superseded: V-Sekai Roadmap and Goals 2023-04-20\n\nMetadata\n\nStatus: superseded by 20230516-v-sekai-roadmap.md \nDeciders: V-Sekai,fire,lyuma,\nTags: V-Sekai,chatgpt4 summary,\n\n\n\nContext and Problem Statement\nWhat is the V-Sekai Roadmap and Goals?\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nThe roadmap presented here is divided into three stages: short-term, mid-term, and long-term goals. Each stage builds upon the previous one, gradually expanding the project’s scope and capabilities.\n\n\nDescribe how your proposal will work with code, pseudo-code, mock-ups, or diagrams\ngraph LR\n\n  subgraph Short Term\n    A[Avatar Loading] --&gt; B1[Simple Demo with VRM Avatar]\n    A --&gt; B2[VRM & Unity Import - Maintain and Improve]\n    A --&gt; B3[Network Code Reconciliation - Godot Network System]\n    A --&gt; B4[Jitter in Network Interpolation]\n    A --&gt; B5[Implement jitter and playback buffer for Voice]\n  end\n\n  subgraph Mid Term\n    B4 --&gt; C[Network]\n    C --&gt; D1[Entity System & Background Loading]\n    C --&gt; D2[Background Loading - Re-evaluate with Multithreaded Scene Tree]\n    C --&gt; D3[UI Work - Fix VR UI & Improve Interaction]\n    C --&gt; D4[Lightweight Relay Instance Server - Single Process, Multiple Instances]\n  end\n\n  subgraph Long Term\n    D4 --&gt; E[Scalable Instances]\n    E --&gt; F1[Network Topology Implementation]\n    E --&gt; F2[Streamlined Content Creation - Better Workflow]\n    E --&gt; F3[Zero Stutter when Loading Content - Address Bottlenecks]\n    E --&gt; F4[Social and Upload Features - Enhance User Experience]\n    E --&gt; F5[Video and Audio Work - Streaming Integration]\n    E --&gt; F6[Scripting Integrations - WASM-based Scripts]\n    E --&gt; F7[UX Work for Non-Technical Users - Accessible UI]\n    E --&gt; F8[Loading VRM Avatars - Streamlined Process]\n    E --&gt; F9[In-Editor Content Building UX - Non-Technical Users]\n  end\nThe discussion involves the development of V-Sekai, a project with short-term, mid-term, and long-term goals. In the short term, the focus is on avatar loading, simple demos, VRM & Unity import, network code reconciliation, adding network interpolation, and voice jitter buffer. Mid-term goals include working on the network, entity system, background loading, UI improvements, and developing a lightweight relay instance server. Finally, long-term goals involve scalable instances, network topology implementation, streamlined content creation, zero stutter loading, enhancing social and upload features, video and music playback and live streaming, scripting integrations, UX work for non-technical users, and in-editor content building UX.\nOne challenge the project faces is maintaining and improving the existing codebase, which includes outdated workarounds from Godot 3. Another setback was the change from OpenVR to OpenXR. Content is another hurdle: transferring a world from other platforms to V-Sekai is currently best accomplished by exporting source assets such as glTF or FBX. The project aims to cater to non-technical users, making it more accessible than other platforms. WASM-based scripting is being considered, but there are concerns about implementation challenges and security.\nIn addition, the V-Sekai project needs a project manager, and the team struggles to find collaborators who share their vision and can dedicate enough time to contribute significantly. Nevertheless, despite the long list of features needed for basic functionality, the team believes that V-Sekai is essential for the future of the Metaverse space, and that will draw collaborators to assist on our common vision.\nIt’s important that our roadmap and goals continue to be discussed and iterated on. Nothing should be seen as final, since technology changes so rapidly and consensus is important.\n\n\nPositive Consequences\nWe can create V-Sekai easier.\n\n\nNegative Consequences\nOverhead might be hard.\n\n\nOption graveyard\n\nRelying on informal communication and ad-hoc collaboration\nContinuing with the current approach without a structured process\n\n\n\nIf this enhancement will be used infrequently, can it be worked around with a few lines of script?\nNo. This is a process.\n\n\nIs there a reason why this should be core and done by us?\nThis is a core process for V-Sekai.\n\n\nReferences\n\nV-Sekai"
   },
   {
-    "objectID": "decisions/20240502-mesh-object-sync-benchmark.html#the-infrequent-use-case",
-    "href": "decisions/20240502-mesh-object-sync-benchmark.html#the-infrequent-use-case",
-    "title": "Proposed: Stress Testing Godot Engine’s Networking System",
+    "objectID": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html",
+    "href": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html",
+    "title": "Accepted: To make it easier to upload V-Sekai maps and Avatars use Godot Engine 4 script templates.",
     "section": "",
-    "text": "In cases where the traffic is consistently low, stress testing may not provide significant benefits. However, it’s still important to prepare for potential spikes in usage."
+    "text": "Status: accepted \nDeciders: V-Sekai,fire,saracen\nTags: V-Sekai,\n\n\n\nUploading V-Sekai maps and Avatars is complicated.\n\n\n\nUse the new Godot Engine feature of script templates to make it easier to upload.\n\n\n\n\nCreate a template for Avatars\nCreate a template for maps\n\n\n\n\n\nLess steps to upload.\n\n\n\n\n\nLoss of knowledge of how the tools work.\n\n\n\n\n\nOption: Status quo.\nRejection Reason: Too many steps are currently needed.\n\n\n\n\nNot a few lines of script.\n\n\n\nWe control the core application flow.\n\n\n\n\nhttps://github.com/godotengine/godot/pull/53957\n\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240502-mesh-object-sync-benchmark.html#in-core-and-done-by-us",
-    "href": "decisions/20240502-mesh-object-sync-benchmark.html#in-core-and-done-by-us",
-    "title": "Proposed: Stress Testing Godot Engine’s Networking System",
+    "objectID": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html#context-and-problem-statement",
+    "href": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html#context-and-problem-statement",
+    "title": "Accepted: To make it easier to upload V-Sekai maps and Avatars use Godot Engine 4 script templates.",
     "section": "",
-    "text": "The proposed stress testing will be conducted by the V-Sekai development team."
+    "text": "Uploading V-Sekai maps and Avatars is complicated."
   },
   {
-    "objectID": "decisions/20240502-mesh-object-sync-benchmark.html#status",
-    "href": "decisions/20240502-mesh-object-sync-benchmark.html#status",
-    "title": "Proposed: Stress Testing Godot Engine’s Networking System",
+    "objectID": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Accepted: To make it easier to upload V-Sekai maps and Avatars use Godot Engine 4 script templates.",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "Use the new Godot Engine feature of script templates to make it easier to upload."
   },
   {
-    "objectID": "decisions/20240502-mesh-object-sync-benchmark.html#decision-makers",
-    "href": "decisions/20240502-mesh-object-sync-benchmark.html#decision-makers",
-    "title": "Proposed: Stress Testing Godot Engine’s Networking System",
+    "objectID": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Accepted: To make it easier to upload V-Sekai maps and Avatars use Godot Engine 4 script templates.",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "Create a template for Avatars\nCreate a template for maps"
   },
   {
-    "objectID": "decisions/20240502-mesh-object-sync-benchmark.html#tags",
-    "href": "decisions/20240502-mesh-object-sync-benchmark.html#tags",
-    "title": "Proposed: Stress Testing Godot Engine’s Networking System",
+    "objectID": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html#positive-consequences",
+    "href": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html#positive-consequences",
+    "title": "Accepted: To make it easier to upload V-Sekai maps and Avatars use Godot Engine 4 script templates.",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Less steps to upload."
   },
   {
-    "objectID": "decisions/20240502-mesh-object-sync-benchmark.html#further-reading",
-    "href": "decisions/20240502-mesh-object-sync-benchmark.html#further-reading",
-    "title": "Proposed: Stress Testing Godot Engine’s Networking System",
+    "objectID": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html#negative-consequences",
+    "href": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html#negative-consequences",
+    "title": "Accepted: To make it easier to upload V-Sekai maps and Avatars use Godot Engine 4 script templates.",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nStress testing Unity’s LLAPI, what are the limits?\nCrappy Contraption\n\nThis proposal was assisted by Aria, an AI assistant."
+    "text": "Loss of knowledge of how the tools work."
   },
   {
-    "objectID": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html",
-    "href": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html",
-    "title": "Accepted: Avoid avatar breaking by following quality checklist",
+    "objectID": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html#option-graveyard",
+    "href": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html#option-graveyard",
+    "title": "Accepted: To make it easier to upload V-Sekai maps and Avatars use Godot Engine 4 script templates.",
     "section": "",
-    "text": "Status: accepted \nDeciders: V-Sekai,fire,\nTags: V-Sekai,\n\n\n\nAvoid avatar breaking which harmful to the person using the avatar.\n\n\n\nCreate a checklist to ensure quality.\n\n\n\nThis is defined for a VRM character.\n\nAdd a root bone\nAge height normalization to 1.59m for an Asian adult female.\nAuto generate spring bones via https://fujisunflower.booth.pm/items/2087178\nCheck eyes\nCheck Jaws\nAdjust spring bones limits\nCheck transparent glasses etc.\nRun mesh mush at 80 degrees twist on all vertices\nCheck culling locations\nMatch shade and base color in MTOON1\nThe relative angle between the Hips and the Thigh should something that works for inverse kinematics.\nCheck manifolds for skin breaking\n\nMove the feet to the origin of the scene\n\nCursor to world origin\nChange to origin\nMove to below feet\nMove object origin to origin\n\nCheck if environment lighting breaks the avatar\n\nChange sky temperature to the brightest\ntest 0.00001 light intensity\ntest 16 light intensity\n\nHow to make a Portrait of the head photo?\n\nE96E66 background color\n16 light intensity and camera set to realistic focal length for a portrait makes the photo look good.\n\n\n\n\n\nLess avatar breaking.\n\n\n\n\n\nWork\n\n\n\n\n\nOption: Do nothing.\nRejection Reason: This is unacceptable to the people who use the avatars.\n\n\n\n\nThis can be automated in the future.\n\n\n\nThis is a guideline and we are in the area.\n\n\n\n\nVRM - 3D Avatar File Format for VR \n\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Option: Status quo.\nRejection Reason: Too many steps are currently needed."
   },
   {
-    "objectID": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html#context-and-problem-statement",
-    "href": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html#context-and-problem-statement",
-    "title": "Accepted: Avoid avatar breaking by following quality checklist",
+    "objectID": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Accepted: To make it easier to upload V-Sekai maps and Avatars use Godot Engine 4 script templates.",
     "section": "",
-    "text": "Avoid avatar breaking which harmful to the person using the avatar."
+    "text": "Not a few lines of script."
   },
   {
-    "objectID": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Accepted: Avoid avatar breaking by following quality checklist",
+    "objectID": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Accepted: To make it easier to upload V-Sekai maps and Avatars use Godot Engine 4 script templates.",
     "section": "",
-    "text": "Create a checklist to ensure quality."
+    "text": "We control the core application flow."
   },
   {
-    "objectID": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Accepted: Avoid avatar breaking by following quality checklist",
+    "objectID": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html#references",
+    "href": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html#references",
+    "title": "Accepted: To make it easier to upload V-Sekai maps and Avatars use Godot Engine 4 script templates.",
     "section": "",
-    "text": "This is defined for a VRM character.\n\nAdd a root bone\nAge height normalization to 1.59m for an Asian adult female.\nAuto generate spring bones via https://fujisunflower.booth.pm/items/2087178\nCheck eyes\nCheck Jaws\nAdjust spring bones limits\nCheck transparent glasses etc.\nRun mesh mush at 80 degrees twist on all vertices\nCheck culling locations\nMatch shade and base color in MTOON1\nThe relative angle between the Hips and the Thigh should something that works for inverse kinematics.\nCheck manifolds for skin breaking\n\nMove the feet to the origin of the scene\n\nCursor to world origin\nChange to origin\nMove to below feet\nMove object origin to origin\n\nCheck if environment lighting breaks the avatar\n\nChange sky temperature to the brightest\ntest 0.00001 light intensity\ntest 16 light intensity\n\nHow to make a Portrait of the head photo?\n\nE96E66 background color\n16 light intensity and camera set to realistic focal length for a portrait makes the photo look good."
+    "text": "https://github.com/godotengine/godot/pull/53957"
   },
   {
-    "objectID": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html#positive-consequences",
-    "href": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html#positive-consequences",
-    "title": "Accepted: Avoid avatar breaking by following quality checklist",
+    "objectID": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html#derivative-license",
+    "href": "decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html#derivative-license",
+    "title": "Accepted: To make it easier to upload V-Sekai maps and Avatars use Godot Engine 4 script templates.",
     "section": "",
-    "text": "Less avatar breaking."
+    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html#negative-consequences",
-    "href": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html#negative-consequences",
-    "title": "Accepted: Avoid avatar breaking by following quality checklist",
+    "objectID": "decisions/20211103-use-platform-called-vfx-reference-platform.html",
+    "href": "decisions/20211103-use-platform-called-vfx-reference-platform.html",
+    "title": "Draft: Use a standard reference platform called VFX Reference platform",
     "section": "",
-    "text": "Work"
+    "text": "Status: draft \nDeciders: V-Sekai,fire,\nTags: V-Sekai,\n\n\n\n\n[A standard reference platform’s purpose is to] minimize incompatibilities between different software packages, ease the support burden for Linux-based pipelines and encourage further adoption of Linux by software vendors.\n\nHere are some problems:\n\nWe want to keep a consistent server configuration setup.\nWe want creators to have a consistent work environment.\n\n\n\n\n\nThe VFX Reference #platform is a set of tool and library versions to be used as a common target #platform for building software for the VFX industry. Its purpose is to minimize incompatibilities between different software packages, ease the support burden for Linux-based pipelines and encourage further adoption of Linux by software vendors. The Reference #platform is updated annually by a group of software vendors in collaboration with the Visual Effects Society Technology Committee.\n\n\n\n\n\nFind candidate centos-like platforms.\nA candidate is Rocky Linux.\n\n\n\n\n\nThe problems with #platform are informed by decisions of others in the industry.\n\n\n\n\n\nGoing outside the #platform is risky.\n\n\n\n\n\nOption: Use Rocky Linux directly\nRejection Reason: No collaboration\nOption: Use Fedora 35 directly\nRejection Reason: Unclear support lifetime.\n\n\n\n\nThis is a devops proposal, not a coding proposal.\n\n\n\nWe do have to choose a reference #platform even if we don’t think about it to upload to docker.\n\n\n\n\nhttps://vfxplatform.com/\nhttps://hub.docker.com/u/aswf\nhttps://hub.docker.com/r/aswf/ci-base\nhttps://github.com/AcademySoftwareFoundation/aswf-docker/tree/master/ci-base\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html#option-graveyard",
-    "href": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html#option-graveyard",
-    "title": "Accepted: Avoid avatar breaking by following quality checklist",
+    "objectID": "decisions/20211103-use-platform-called-vfx-reference-platform.html#context-and-problem-statement",
+    "href": "decisions/20211103-use-platform-called-vfx-reference-platform.html#context-and-problem-statement",
+    "title": "Draft: Use a standard reference platform called VFX Reference platform",
     "section": "",
-    "text": "Option: Do nothing.\nRejection Reason: This is unacceptable to the people who use the avatars."
+    "text": "[A standard reference platform’s purpose is to] minimize incompatibilities between different software packages, ease the support burden for Linux-based pipelines and encourage further adoption of Linux by software vendors.\n\nHere are some problems:\n\nWe want to keep a consistent server configuration setup.\nWe want creators to have a consistent work environment."
   },
   {
-    "objectID": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Accepted: Avoid avatar breaking by following quality checklist",
+    "objectID": "decisions/20211103-use-platform-called-vfx-reference-platform.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20211103-use-platform-called-vfx-reference-platform.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Draft: Use a standard reference platform called VFX Reference platform",
     "section": "",
-    "text": "This can be automated in the future."
+    "text": "The VFX Reference #platform is a set of tool and library versions to be used as a common target #platform for building software for the VFX industry. Its purpose is to minimize incompatibilities between different software packages, ease the support burden for Linux-based pipelines and encourage further adoption of Linux by software vendors. The Reference #platform is updated annually by a group of software vendors in collaboration with the Visual Effects Society Technology Committee."
   },
   {
-    "objectID": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Accepted: Avoid avatar breaking by following quality checklist",
+    "objectID": "decisions/20211103-use-platform-called-vfx-reference-platform.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20211103-use-platform-called-vfx-reference-platform.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Draft: Use a standard reference platform called VFX Reference platform",
     "section": "",
-    "text": "This is a guideline and we are in the area."
+    "text": "Find candidate centos-like platforms.\nA candidate is Rocky Linux."
   },
   {
-    "objectID": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html#references",
-    "href": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html#references",
-    "title": "Accepted: Avoid avatar breaking by following quality checklist",
+    "objectID": "decisions/20211103-use-platform-called-vfx-reference-platform.html#positive-consequences",
+    "href": "decisions/20211103-use-platform-called-vfx-reference-platform.html#positive-consequences",
+    "title": "Draft: Use a standard reference platform called VFX Reference platform",
     "section": "",
-    "text": "VRM - 3D Avatar File Format for VR"
+    "text": "The problems with #platform are informed by decisions of others in the industry."
   },
   {
-    "objectID": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html#derivative-license",
-    "href": "decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html#derivative-license",
-    "title": "Accepted: Avoid avatar breaking by following quality checklist",
+    "objectID": "decisions/20211103-use-platform-called-vfx-reference-platform.html#negative-consequences",
+    "href": "decisions/20211103-use-platform-called-vfx-reference-platform.html#negative-consequences",
+    "title": "Draft: Use a standard reference platform called VFX Reference platform",
     "section": "",
-    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Going outside the #platform is risky."
   },
   {
-    "objectID": "decisions/20211031-construct-the-virtual-world.html",
-    "href": "decisions/20211031-construct-the-virtual-world.html",
-    "title": "Proposed: Construct the virtual #world",
+    "objectID": "decisions/20211103-use-platform-called-vfx-reference-platform.html#option-graveyard",
+    "href": "decisions/20211103-use-platform-called-vfx-reference-platform.html#option-graveyard",
+    "title": "Draft: Use a standard reference platform called VFX Reference platform",
     "section": "",
-    "text": "Proposed: Construct the virtual #world\n\nContext and Problem Statement\nIt’s hard to create the virtual world.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nUse a way to create 3d in a virtual world.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n\npacked scenes\nblockmesh\ncassie\nSpark joy.\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot trivial.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nI know how to do this.\n\n\nReferences\n\nCASSIE\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Option: Use Rocky Linux directly\nRejection Reason: No collaboration\nOption: Use Fedora 35 directly\nRejection Reason: Unclear support lifetime."
   },
   {
-    "objectID": "decisions/20230911-xpr.exs.html",
-    "href": "decisions/20230911-xpr.exs.html",
-    "title": "Draft: XPR in Elixir",
+    "objectID": "decisions/20211103-use-platform-called-vfx-reference-platform.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20211103-use-platform-called-vfx-reference-platform.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Draft: Use a standard reference platform called VFX Reference platform",
     "section": "",
-    "text": "Draft: XPR in Elixir\ndefmodule AveragableLerpable do\n  @callback average(a :: any(), b :: any(), t :: number()) :: any()\n  @callback lerp(a :: any(), b :: any(), t :: number()) :: any()\n  @callback spherical_interpolate(a :: any(), b :: any(), t :: number()) :: any()\n  @callback spherical_cubic_interpolate(a :: any(), b :: any(), c :: any(), d :: any(), t1 :: number(), t2 :: number(), t3 :: number(), t4 :: number()) :: any()\n  @callback cubic_interpolate(a :: any(), b :: any(), c :: any(), d :: any(), t1 :: number(), t2 :: number(), t3 :: number(), t4 :: number()) :: any()\nend\n\ndefmodule Rotation6D do\n  @behavior AveragableLerpable\n\n  defstruct [:x1, :y1, :z1, :x2, :y2, :z2]\n\n  # Implement the required methods here\nend\n\ndefmodule Position3D do\n  @behavior AveragableLerpable\n\n  defstruct [:x, :y, :z]\n\n  # Implement the required methods here\nend\n\ndefmodule LightCone do\n  @type t :: %{\n          count: [AveragableLerpable.t()],\n          accumulate: [function()],\n          array: [AveragableLerpable.t()],\n          set: MapSet.t(any())\n        }\nend\n\n@type event ::\n        {:expand}\n        | {:superposition}\n        | {:spacetime_bubble}\n        | {:light_cone}\n        | {:collapse}\n        | {:avg_lerp}\n        | {:plus}\n        | {:union}\n\ndefmodule PropagateFilter do\n  use Membrane.Filter\n\n  @impl true\n  def handle_init(_) do\n    {:ok, %{}}\n  end\n\n  @impl true\n  def handle_demand(:output, size, :buffers, _ctx) do\n    {{:ok, demand: {:input, size}}, %{}}\n  end\n\n  @impl true\n  def handle_process(:input, buffer, _ctx) do\n    # Process the input data and generate the output data\n    output_data = process(buffer.payload)\n\n    # Create a new buffer with the output data\n    output_buffer = %Membrane.Buffer{payload: output_data}\n\n    {{:ok, buffer: {:output, output_buffer}}, %{}}\n  end\n\n  defp process(input_data) do\n    # Implement your processing logic here\n    # For example, if input_data is a list of numbers, you can calculate their sum:\n    Enum.reduce(input_data, 0, &(&1 + &2))\n  end\nend\n\n\ndefmodule XprPipeline do\n  use Membrane.Pipeline\n\n  alias Membrane.Element.Tee.Master\n  alias Membrane.Element.Funnel\n  alias Membrane.Element.Clock\n\n  @impl true\n  def handle_init(_) do\n    children = [\n      clock: Clock,\n      light_cone: LightConeElement,\n      expanding: ExpandingElement,\n      collapsing: CollapsingElement,\n      reduce: ReduceElement,\n      update: UpdateElement,\n      tee: Master,\n      funnel: Funnel,\n      propagate: PropagateFilter\n    ]\n\n    links = [\n      link(:clock)\n      |&gt; via_out(:tick, options: [interval: 1000]) # Adjust the interval as needed\n      |&gt; to(:tee)\n      |&gt; to(:expanding)\n      |&gt; to(:light_cone)\n      |&gt; to(:collapsing)\n      |&gt; to(:reduce)\n      |&gt; to(:propagate)\n      |&gt; to(:funnel)\n      |&gt; to(:update)\n    ]\n\n    {{:ok, %ParentSpec{children: children, links: links}}, %{}}\n  end\nend"
+    "text": "This is a devops proposal, not a coding proposal."
   },
   {
-    "objectID": "decisions/20240528-pipeline-godot-wasm-importer.html",
-    "href": "decisions/20240528-pipeline-godot-wasm-importer.html",
-    "title": "Proposed: Godot Engine as Wasm Importer",
+    "objectID": "decisions/20211103-use-platform-called-vfx-reference-platform.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20211103-use-platform-called-vfx-reference-platform.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Draft: Use a standard reference platform called VFX Reference platform",
     "section": "",
-    "text": "There are concerns regarding the security of gltf and fbx document code in Godot Engine.\n\n\n\nThe current implementation of gltf and fbx document code in Godot Engine may pose potential security risks.\n\n\n\nThe proposal is to compile Godot Engine as wasm and run the wasm workers in batch on the incoming files. This can be achieved without the need for node, using Rustler + wasmtime.\n1. Compile Godot Engine as wasm\n2. Run wasm workers on incoming files\n\n\n\n\nEnhanced security for gltf and fbx document code.\nEfficient handling of incoming files.\n\n\n\n\n\nPotential increase in complexity due to the introduction of wasm.\nPossible performance overhead from running wasm workers.\n\n\n\n\nAn additional layer of Godot Engine text scene and text resource to JSON could be implemented to avoid parsing errors.\n\n\n\nThis solution might not be beneficial for smaller projects or those that do not use gltf and fbx document code extensively.\n\n\n\nThis proposal involves core changes to the Godot Engine and will be implemented by the V-Sekai development team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team, Fire, Benbot\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nElixi Nodejs\norb-runtime to run wasm\n\nAI assistant Aria assisted with this article."
+    "text": "We do have to choose a reference #platform even if we don’t think about it to upload to docker."
   },
   {
-    "objectID": "decisions/20240528-pipeline-godot-wasm-importer.html#the-context",
-    "href": "decisions/20240528-pipeline-godot-wasm-importer.html#the-context",
-    "title": "Proposed: Godot Engine as Wasm Importer",
+    "objectID": "decisions/20211103-use-platform-called-vfx-reference-platform.html#references",
+    "href": "decisions/20211103-use-platform-called-vfx-reference-platform.html#references",
+    "title": "Draft: Use a standard reference platform called VFX Reference platform",
     "section": "",
-    "text": "There are concerns regarding the security of gltf and fbx document code in Godot Engine."
+    "text": "https://vfxplatform.com/\nhttps://hub.docker.com/u/aswf\nhttps://hub.docker.com/r/aswf/ci-base\nhttps://github.com/AcademySoftwareFoundation/aswf-docker/tree/master/ci-base"
   },
   {
-    "objectID": "decisions/20240528-pipeline-godot-wasm-importer.html#the-problem-statement",
-    "href": "decisions/20240528-pipeline-godot-wasm-importer.html#the-problem-statement",
-    "title": "Proposed: Godot Engine as Wasm Importer",
+    "objectID": "decisions/20211103-use-platform-called-vfx-reference-platform.html#derivative-license",
+    "href": "decisions/20211103-use-platform-called-vfx-reference-platform.html#derivative-license",
+    "title": "Draft: Use a standard reference platform called VFX Reference platform",
     "section": "",
-    "text": "The current implementation of gltf and fbx document code in Godot Engine may pose potential security risks."
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240528-pipeline-godot-wasm-importer.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240528-pipeline-godot-wasm-importer.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Godot Engine as Wasm Importer",
+    "objectID": "decisions/20240121-mac-setup.html",
+    "href": "decisions/20240121-mac-setup.html",
+    "title": "Proposed: Macos cicd setup.",
     "section": "",
-    "text": "The proposal is to compile Godot Engine as wasm and run the wasm workers in batch on the incoming files. This can be achieved without the need for node, using Rustler + wasmtime.\n1. Compile Godot Engine as wasm\n2. Run wasm workers on incoming files"
+    "text": "Status: Proposed\nDeciders: V-Sekai Core Team\nTags: Documentation, Automation, GoCD, Continuous Integration\n\n\n\n\nV-Sekai, a community-driven project aimed at developing social VR functionality for the Godot Engine, is experiencing growing pains due to increased contributions and complexity. There’s an apparent need to streamline development processes and ensure reliable automation in build and deployment workflows.\n\n\n\nThe current manual setup of development environments, especially continuous integration (CI) agents, is time-consuming and error-prone. The process lacks documentation, which creates barriers for new contributors and limits the scalability of the existing CI infrastructure.\n\n\n\nTo address these challenges, we propose to document the process thoroughly and automate the setup of GoCD agents, particularly for macOS environments, to facilitate smoother onboarding and reduce setup discrepancies.\n\n\nHere’s a step-by-step guide to setting up a GoCD agent service and configuring it to automatically start up on boot on a Mac.\n\n\n\nBoot your freshly reset or newly bought Mac.\nProceed with the initial setup, creating a user account as prompted by the macOS setup wizard.\n\n\n\n\ncd go-agent-20.5.0\nsudo xattr -d -r com.apple.quarantine .\n\n\n\n\nHandle Single Sign-On (SSO) if necessary.\n\n\n\n\n\nLog in with your Apple ID and download Xcode from the App Store.\n\n\n\n\n\nInstall Homebrew and the command line developer tools.\n/bin/bash -c \"$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh)\"\n\n\n\n\n\nInstall the GoCD agent via Homebrew or download from the GoCD website.\n\n\n\n\n\nEdit wrapper-properties.conf to configure your GoCD server URL and additional preferences.\n\n\n\n\n\nUpdate the server URL to https://ci.v-sekai.cloud/go.\n\n\n\n\n\nCreate a launch daemon for automatic startup on boot using the following commands:\nsudo tee /Library/LaunchDaemons/com.gocd.agent.plist &lt;&lt;EOF\n&lt;?xml version=\"1.0\" encoding=\"UTF-8\"?&gt;\n&lt;!DOCTYPE plist PUBLIC \"-//Apple//DTD PLIST 1.0//EN\" \"http://www.apple.com/DTDs/PropertyList-1.0.dtd\"&gt;\n&lt;plist version=\"1.0\"&gt;\n&lt;dict&gt;\n    &lt;key&gt;Label&lt;/key&gt;\n    &lt;string&gt;com.gocd.agent&lt;/string&gt;\n    &lt;key&gt;ProgramArguments&lt;/key&gt;\n    &lt;array&gt;\n        &lt;string&gt;/Users/fire/go-agent-23.5.0/bin/go-agent&lt;/string&gt;\n        &lt;string&gt;start&lt;/string&gt;\n    &lt;/array&gt;\n    &lt;key&gt;RunAtLoad&lt;/key&gt;\n    &lt;true/&gt;\n    &lt;key&gt;KeepAlive&lt;/key&gt;\n    &lt;true/&gt;\n&lt;/dict&gt;\n&lt;/plist&gt;\nEOF\nsudo launchctl load /Library/LaunchDaemons/com.gocd.agent.plist\nsudo launchctl list | grep com.gocd.agent\nReplace /Users/fire/go-agent-23.5.0 with the actual path where the binary resides.\nVerify that the agent starts upon boot.\n\nYour GoCD agent should now automatically start up whenever your Mac boots up.\n\n\n\n\n\nAutomating the setup of the GoCD agents substantially minimizes the potential for human error during configuration. It also speeds up the onboarding process for new developers and maintains consistency across multiple setups.\n\n\n\nThe main downside is the initial investment in time and resources required to document and test the automation scripts. Additionally, there is a reliance on macOS-specific services, which could alienate potential contributors who do not have access to a Mac.\n\n\n\nAlternatively, we considered using different CI services, like GitHub Actions or GitLab CI, but decided against it due to GoCD’s robustness and flexibility fitting V-Sekai’s needs more closely.\n\n\n\nWe recognize that not all contributors will require a local GoCD agent setup. However, for those involved in CI pipeline management or requiring a mirrored development environment, this will be invaluable.\n\n\n\nThis proposal suggests that the task be managed internally by the core V-Sekai team to maintain control over critical infrastructure components.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community.\nV-Sekai/v-sekai-game - GitHub repository for the V-Sekai game.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240528-pipeline-godot-wasm-importer.html#the-benefits",
-    "href": "decisions/20240528-pipeline-godot-wasm-importer.html#the-benefits",
-    "title": "Proposed: Godot Engine as Wasm Importer",
+    "objectID": "decisions/20240121-mac-setup.html#metadata",
+    "href": "decisions/20240121-mac-setup.html#metadata",
+    "title": "Proposed: Macos cicd setup.",
     "section": "",
-    "text": "Enhanced security for gltf and fbx document code.\nEfficient handling of incoming files."
+    "text": "Status: Proposed\nDeciders: V-Sekai Core Team\nTags: Documentation, Automation, GoCD, Continuous Integration"
   },
   {
-    "objectID": "decisions/20240528-pipeline-godot-wasm-importer.html#the-downsides",
-    "href": "decisions/20240528-pipeline-godot-wasm-importer.html#the-downsides",
-    "title": "Proposed: Godot Engine as Wasm Importer",
+    "objectID": "decisions/20240121-mac-setup.html#the-backdrop",
+    "href": "decisions/20240121-mac-setup.html#the-backdrop",
+    "title": "Proposed: Macos cicd setup.",
     "section": "",
-    "text": "Potential increase in complexity due to the introduction of wasm.\nPossible performance overhead from running wasm workers."
+    "text": "V-Sekai, a community-driven project aimed at developing social VR functionality for the Godot Engine, is experiencing growing pains due to increased contributions and complexity. There’s an apparent need to streamline development processes and ensure reliable automation in build and deployment workflows."
   },
   {
-    "objectID": "decisions/20240528-pipeline-godot-wasm-importer.html#the-road-not-taken",
-    "href": "decisions/20240528-pipeline-godot-wasm-importer.html#the-road-not-taken",
-    "title": "Proposed: Godot Engine as Wasm Importer",
+    "objectID": "decisions/20240121-mac-setup.html#the-challenge",
+    "href": "decisions/20240121-mac-setup.html#the-challenge",
+    "title": "Proposed: Macos cicd setup.",
     "section": "",
-    "text": "An additional layer of Godot Engine text scene and text resource to JSON could be implemented to avoid parsing errors."
+    "text": "The current manual setup of development environments, especially continuous integration (CI) agents, is time-consuming and error-prone. The process lacks documentation, which creates barriers for new contributors and limits the scalability of the existing CI infrastructure."
   },
   {
-    "objectID": "decisions/20240528-pipeline-godot-wasm-importer.html#the-infrequent-use-case",
-    "href": "decisions/20240528-pipeline-godot-wasm-importer.html#the-infrequent-use-case",
-    "title": "Proposed: Godot Engine as Wasm Importer",
+    "objectID": "decisions/20240121-mac-setup.html#the-strategy",
+    "href": "decisions/20240121-mac-setup.html#the-strategy",
+    "title": "Proposed: Macos cicd setup.",
     "section": "",
-    "text": "This solution might not be beneficial for smaller projects or those that do not use gltf and fbx document code extensively."
+    "text": "To address these challenges, we propose to document the process thoroughly and automate the setup of GoCD agents, particularly for macOS environments, to facilitate smoother onboarding and reduce setup discrepancies.\n\n\nHere’s a step-by-step guide to setting up a GoCD agent service and configuring it to automatically start up on boot on a Mac.\n\n\n\nBoot your freshly reset or newly bought Mac.\nProceed with the initial setup, creating a user account as prompted by the macOS setup wizard.\n\n\n\n\ncd go-agent-20.5.0\nsudo xattr -d -r com.apple.quarantine .\n\n\n\n\nHandle Single Sign-On (SSO) if necessary.\n\n\n\n\n\nLog in with your Apple ID and download Xcode from the App Store.\n\n\n\n\n\nInstall Homebrew and the command line developer tools.\n/bin/bash -c \"$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh)\"\n\n\n\n\n\nInstall the GoCD agent via Homebrew or download from the GoCD website.\n\n\n\n\n\nEdit wrapper-properties.conf to configure your GoCD server URL and additional preferences.\n\n\n\n\n\nUpdate the server URL to https://ci.v-sekai.cloud/go.\n\n\n\n\n\nCreate a launch daemon for automatic startup on boot using the following commands:\nsudo tee /Library/LaunchDaemons/com.gocd.agent.plist &lt;&lt;EOF\n&lt;?xml version=\"1.0\" encoding=\"UTF-8\"?&gt;\n&lt;!DOCTYPE plist PUBLIC \"-//Apple//DTD PLIST 1.0//EN\" \"http://www.apple.com/DTDs/PropertyList-1.0.dtd\"&gt;\n&lt;plist version=\"1.0\"&gt;\n&lt;dict&gt;\n    &lt;key&gt;Label&lt;/key&gt;\n    &lt;string&gt;com.gocd.agent&lt;/string&gt;\n    &lt;key&gt;ProgramArguments&lt;/key&gt;\n    &lt;array&gt;\n        &lt;string&gt;/Users/fire/go-agent-23.5.0/bin/go-agent&lt;/string&gt;\n        &lt;string&gt;start&lt;/string&gt;\n    &lt;/array&gt;\n    &lt;key&gt;RunAtLoad&lt;/key&gt;\n    &lt;true/&gt;\n    &lt;key&gt;KeepAlive&lt;/key&gt;\n    &lt;true/&gt;\n&lt;/dict&gt;\n&lt;/plist&gt;\nEOF\nsudo launchctl load /Library/LaunchDaemons/com.gocd.agent.plist\nsudo launchctl list | grep com.gocd.agent\nReplace /Users/fire/go-agent-23.5.0 with the actual path where the binary resides.\nVerify that the agent starts upon boot.\n\nYour GoCD agent should now automatically start up whenever your Mac boots up."
   },
   {
-    "objectID": "decisions/20240528-pipeline-godot-wasm-importer.html#in-core-and-done-by-us",
-    "href": "decisions/20240528-pipeline-godot-wasm-importer.html#in-core-and-done-by-us",
-    "title": "Proposed: Godot Engine as Wasm Importer",
+    "objectID": "decisions/20240121-mac-setup.html#the-upside",
+    "href": "decisions/20240121-mac-setup.html#the-upside",
+    "title": "Proposed: Macos cicd setup.",
     "section": "",
-    "text": "This proposal involves core changes to the Godot Engine and will be implemented by the V-Sekai development team."
+    "text": "Automating the setup of the GoCD agents substantially minimizes the potential for human error during configuration. It also speeds up the onboarding process for new developers and maintains consistency across multiple setups."
   },
   {
-    "objectID": "decisions/20240528-pipeline-godot-wasm-importer.html#status",
-    "href": "decisions/20240528-pipeline-godot-wasm-importer.html#status",
-    "title": "Proposed: Godot Engine as Wasm Importer",
+    "objectID": "decisions/20240121-mac-setup.html#the-downside",
+    "href": "decisions/20240121-mac-setup.html#the-downside",
+    "title": "Proposed: Macos cicd setup.",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "The main downside is the initial investment in time and resources required to document and test the automation scripts. Additionally, there is a reliance on macOS-specific services, which could alienate potential contributors who do not have access to a Mac."
   },
   {
-    "objectID": "decisions/20240528-pipeline-godot-wasm-importer.html#decision-makers",
-    "href": "decisions/20240528-pipeline-godot-wasm-importer.html#decision-makers",
-    "title": "Proposed: Godot Engine as Wasm Importer",
+    "objectID": "decisions/20240121-mac-setup.html#the-road-not-taken",
+    "href": "decisions/20240121-mac-setup.html#the-road-not-taken",
+    "title": "Proposed: Macos cicd setup.",
     "section": "",
-    "text": "V-Sekai development team, Fire, Benbot"
+    "text": "Alternatively, we considered using different CI services, like GitHub Actions or GitLab CI, but decided against it due to GoCD’s robustness and flexibility fitting V-Sekai’s needs more closely."
   },
   {
-    "objectID": "decisions/20240528-pipeline-godot-wasm-importer.html#tags",
-    "href": "decisions/20240528-pipeline-godot-wasm-importer.html#tags",
-    "title": "Proposed: Godot Engine as Wasm Importer",
+    "objectID": "decisions/20240121-mac-setup.html#the-infrequent-use-case",
+    "href": "decisions/20240121-mac-setup.html#the-infrequent-use-case",
+    "title": "Proposed: Macos cicd setup.",
     "section": "",
-    "text": "V-Sekai"
+    "text": "We recognize that not all contributors will require a local GoCD agent setup. However, for those involved in CI pipeline management or requiring a mirrored development environment, this will be invaluable."
   },
   {
-    "objectID": "decisions/20240528-pipeline-godot-wasm-importer.html#further-reading",
-    "href": "decisions/20240528-pipeline-godot-wasm-importer.html#further-reading",
-    "title": "Proposed: Godot Engine as Wasm Importer",
+    "objectID": "decisions/20240121-mac-setup.html#in-core-and-done-by-us",
+    "href": "decisions/20240121-mac-setup.html#in-core-and-done-by-us",
+    "title": "Proposed: Macos cicd setup.",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nElixi Nodejs\norb-runtime to run wasm\n\nAI assistant Aria assisted with this article."
+    "text": "This proposal suggests that the task be managed internally by the core V-Sekai team to maintain control over critical infrastructure components."
   },
   {
-    "objectID": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html",
-    "href": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html",
-    "title": "Accepted: Create an upstream pull request for all non-V-Sekai related patches",
+    "objectID": "decisions/20240121-mac-setup.html#further-reading",
+    "href": "decisions/20240121-mac-setup.html#further-reading",
+    "title": "Proposed: Macos cicd setup.",
     "section": "",
-    "text": "Status: accepted \nDeciders: V-Sekai,fire,lyuma,\nTags: V-Sekai,\n\n\n\nWe use a gitassembler script, but the list may diverge from Godot Engine master.\nThese critical changes need to be synced with Godot Engine organization.\n\n\n\nNon-V-Sekai related and upstreamable godot patches should be filed as upstream PRs.\nThis makes Godot Engine core and V-Sekai better because changes are synchronized.\n\n\n\nHere is an example .gitassembly:\nstage groups-web-4.x remotes/v-sekai-godot/master\nmerge groups-web-4.x remotes/lyuma/gltf_shapes_8bones\nmerge groups-web-4.x remotes/v-sekai-godot/ninja-ccache\nNeed to check every line in the list using a comparison link:\n\nhttps://github.com/godotengine/godot/compare/master…lyuma:gltf_shapes_8bones\nhttps://github.com/godotengine/godot/compare/master…v-sekai-godot:ninja-ccache\n\nMake a corresponding pull request on https://github.com/godotengine/godot/pulls if there isn’t one.\nIf not possible, or non-upstreamable (for example, V-Sekai related), leave a comment in the .gitassembly why one cannot create a Godot Engine organization pull request.\n\n\n\n\nsynced\neasier maintenance\n\n\n\n\n\nneed to pay cost of bureaucracy\n\n\n\n\n\nOption: do nothing\nRejection Reason: V-Sekai and Godot Engine organization diverge\n\n\n\n\nNot a few lines of code.\n\n\n\nGodot Engine code is core.\n\n\n\n\nhttps://github.com/godotengine/godot\nhttps://github.com/v-sekai/godot\nhttps://www.thregr.org/~wavexx/software/git-assembler/\n\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community.\nV-Sekai/v-sekai-game - GitHub repository for the V-Sekai game.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html#context-and-problem-statement",
-    "href": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html#context-and-problem-statement",
-    "title": "Accepted: Create an upstream pull request for all non-V-Sekai related patches",
+    "objectID": "decisions/20240710-platform-focus-on-pcvr-and-web.html",
+    "href": "decisions/20240710-platform-focus-on-pcvr-and-web.html",
+    "title": "Proposed: Focus on PCVR and the Web",
     "section": "",
-    "text": "We use a gitassembler script, but the list may diverge from Godot Engine master.\nThese critical changes need to be synced with Godot Engine organization."
+    "text": "In the development of virtual reality (VR) applications, focusing on both PC-based VR (PCVR) and web platforms can provide a broader reach and enhanced user experience.\nNote: When referring to “web” in this document, it specifically means web desktop platforms and not WebXR.\n\n\n\nBalancing the development efforts between PCVR and web platforms presents challenges in terms of resource allocation and maintaining consistent performance across different environments.\n\n\n\n\nUnified Codebase: Develop a unified codebase that supports both PCVR and web platforms to ensure consistency and reduce maintenance overhead.\nUnified Networking: A PCVR client can communicate with a web client.\nPlatform-Specific Optimizations: Implement platform-specific optimizations to leverage the strengths of each environment.\nResponsive Design: Ensure the user interface is responsive and adapts seamlessly to different devices and screen sizes.\nPerformance Monitoring: Continuously monitor performance metrics to identify and address any platform-specific issues promptly.\nMultithreaded Web: Opt for a multithreaded web approach instead of a single-threaded one to enhance performance and responsiveness on web platforms.\n\n\n\n\n\nBroader Reach: Supporting both PCVR and web platforms allows us to cater to a wider audience.\nEnhanced User Experience: Platform-specific optimizations ensure users have the best possible experience regardless of their device.\nConsistency: A unified codebase ensures consistent functionality and appearance across platforms.\n\n\n\n\n\nResource Allocation: Balancing development efforts between two platforms may require additional resources.\nComplexity: Managing a unified codebase with platform-specific optimizations can introduce complexity.\n\n\n\n\nFocusing exclusively on either PCVR or web platforms was considered but ultimately deemed less effective in reaching a broader audience.\n\n\n\nIn scenarios where the application is highly specialized for either PCVR or web, focusing on one platform might be more efficient.\n\n\n\nThis proposal aligns with our core values of inclusivity and innovation and will be implemented by our team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\nFire\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Accepted: Create an upstream pull request for all non-V-Sekai related patches",
+    "objectID": "decisions/20240710-platform-focus-on-pcvr-and-web.html#the-context",
+    "href": "decisions/20240710-platform-focus-on-pcvr-and-web.html#the-context",
+    "title": "Proposed: Focus on PCVR and the Web",
     "section": "",
-    "text": "Non-V-Sekai related and upstreamable godot patches should be filed as upstream PRs.\nThis makes Godot Engine core and V-Sekai better because changes are synchronized."
+    "text": "In the development of virtual reality (VR) applications, focusing on both PC-based VR (PCVR) and web platforms can provide a broader reach and enhanced user experience.\nNote: When referring to “web” in this document, it specifically means web desktop platforms and not WebXR."
   },
   {
-    "objectID": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Accepted: Create an upstream pull request for all non-V-Sekai related patches",
+    "objectID": "decisions/20240710-platform-focus-on-pcvr-and-web.html#the-problem-statement",
+    "href": "decisions/20240710-platform-focus-on-pcvr-and-web.html#the-problem-statement",
+    "title": "Proposed: Focus on PCVR and the Web",
     "section": "",
-    "text": "Here is an example .gitassembly:\nstage groups-web-4.x remotes/v-sekai-godot/master\nmerge groups-web-4.x remotes/lyuma/gltf_shapes_8bones\nmerge groups-web-4.x remotes/v-sekai-godot/ninja-ccache\nNeed to check every line in the list using a comparison link:\n\nhttps://github.com/godotengine/godot/compare/master…lyuma:gltf_shapes_8bones\nhttps://github.com/godotengine/godot/compare/master…v-sekai-godot:ninja-ccache\n\nMake a corresponding pull request on https://github.com/godotengine/godot/pulls if there isn’t one.\nIf not possible, or non-upstreamable (for example, V-Sekai related), leave a comment in the .gitassembly why one cannot create a Godot Engine organization pull request."
+    "text": "Balancing the development efforts between PCVR and web platforms presents challenges in terms of resource allocation and maintaining consistent performance across different environments."
   },
   {
-    "objectID": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html#positive-consequences",
-    "href": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html#positive-consequences",
-    "title": "Accepted: Create an upstream pull request for all non-V-Sekai related patches",
+    "objectID": "decisions/20240710-platform-focus-on-pcvr-and-web.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240710-platform-focus-on-pcvr-and-web.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Focus on PCVR and the Web",
     "section": "",
-    "text": "synced\neasier maintenance"
+    "text": "Unified Codebase: Develop a unified codebase that supports both PCVR and web platforms to ensure consistency and reduce maintenance overhead.\nUnified Networking: A PCVR client can communicate with a web client.\nPlatform-Specific Optimizations: Implement platform-specific optimizations to leverage the strengths of each environment.\nResponsive Design: Ensure the user interface is responsive and adapts seamlessly to different devices and screen sizes.\nPerformance Monitoring: Continuously monitor performance metrics to identify and address any platform-specific issues promptly.\nMultithreaded Web: Opt for a multithreaded web approach instead of a single-threaded one to enhance performance and responsiveness on web platforms."
   },
   {
-    "objectID": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html#negative-consequences",
-    "href": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html#negative-consequences",
-    "title": "Accepted: Create an upstream pull request for all non-V-Sekai related patches",
+    "objectID": "decisions/20240710-platform-focus-on-pcvr-and-web.html#the-benefits",
+    "href": "decisions/20240710-platform-focus-on-pcvr-and-web.html#the-benefits",
+    "title": "Proposed: Focus on PCVR and the Web",
     "section": "",
-    "text": "need to pay cost of bureaucracy"
+    "text": "Broader Reach: Supporting both PCVR and web platforms allows us to cater to a wider audience.\nEnhanced User Experience: Platform-specific optimizations ensure users have the best possible experience regardless of their device.\nConsistency: A unified codebase ensures consistent functionality and appearance across platforms."
   },
   {
-    "objectID": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html#option-graveyard",
-    "href": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html#option-graveyard",
-    "title": "Accepted: Create an upstream pull request for all non-V-Sekai related patches",
+    "objectID": "decisions/20240710-platform-focus-on-pcvr-and-web.html#the-downsides",
+    "href": "decisions/20240710-platform-focus-on-pcvr-and-web.html#the-downsides",
+    "title": "Proposed: Focus on PCVR and the Web",
     "section": "",
-    "text": "Option: do nothing\nRejection Reason: V-Sekai and Godot Engine organization diverge"
+    "text": "Resource Allocation: Balancing development efforts between two platforms may require additional resources.\nComplexity: Managing a unified codebase with platform-specific optimizations can introduce complexity."
   },
   {
-    "objectID": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Accepted: Create an upstream pull request for all non-V-Sekai related patches",
+    "objectID": "decisions/20240710-platform-focus-on-pcvr-and-web.html#the-road-not-taken",
+    "href": "decisions/20240710-platform-focus-on-pcvr-and-web.html#the-road-not-taken",
+    "title": "Proposed: Focus on PCVR and the Web",
     "section": "",
-    "text": "Not a few lines of code."
+    "text": "Focusing exclusively on either PCVR or web platforms was considered but ultimately deemed less effective in reaching a broader audience."
   },
   {
-    "objectID": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Accepted: Create an upstream pull request for all non-V-Sekai related patches",
+    "objectID": "decisions/20240710-platform-focus-on-pcvr-and-web.html#the-infrequent-use-case",
+    "href": "decisions/20240710-platform-focus-on-pcvr-and-web.html#the-infrequent-use-case",
+    "title": "Proposed: Focus on PCVR and the Web",
     "section": "",
-    "text": "Godot Engine code is core."
+    "text": "In scenarios where the application is highly specialized for either PCVR or web, focusing on one platform might be more efficient."
   },
   {
-    "objectID": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html#references",
-    "href": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html#references",
-    "title": "Accepted: Create an upstream pull request for all non-V-Sekai related patches",
+    "objectID": "decisions/20240710-platform-focus-on-pcvr-and-web.html#in-core-and-done-by-us",
+    "href": "decisions/20240710-platform-focus-on-pcvr-and-web.html#in-core-and-done-by-us",
+    "title": "Proposed: Focus on PCVR and the Web",
     "section": "",
-    "text": "https://github.com/godotengine/godot\nhttps://github.com/v-sekai/godot\nhttps://www.thregr.org/~wavexx/software/git-assembler/"
+    "text": "This proposal aligns with our core values of inclusivity and innovation and will be implemented by our team."
   },
   {
-    "objectID": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html#derivative-license",
-    "href": "decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html#derivative-license",
-    "title": "Accepted: Create an upstream pull request for all non-V-Sekai related patches",
+    "objectID": "decisions/20240710-platform-focus-on-pcvr-and-web.html#status",
+    "href": "decisions/20240710-platform-focus-on-pcvr-and-web.html#status",
+    "title": "Proposed: Focus on PCVR and the Web",
     "section": "",
-    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20231226-furniture-vs-organic.html",
-    "href": "decisions/20231226-furniture-vs-organic.html",
-    "title": "Proposed: Hardsurface vs Organic",
+    "objectID": "decisions/20240710-platform-focus-on-pcvr-and-web.html#decision-makers",
+    "href": "decisions/20240710-platform-focus-on-pcvr-and-web.html#decision-makers",
+    "title": "Proposed: Focus on PCVR and the Web",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai, fire, msstabby\nTags: V-Sekai, VR, Godot Engine, 3D Modeling, Performance Optimization\n\n\n\n\nV-Sekai is a vibrant platform for social VR experiences built on the Godot Engine. Its success hinges on the seamless integration of visually appealing 3D environments and characters that perform optimally across various VR hardware.\n\n\n\nThe challenge lies in striking a balance between hardsurface (static objects) and organic (characters) modeling within V-Sekai. The goal is to optimize both types of models, reducing geometric complexity without compromising on visual richness or functional requirements of rigging and animation.\n\n\n\nAdopt different strategies for hardsurface and organic modeling. For hardsurface models, focus on reducing the number of triangles, especially for non-moving geometry like furniture. For organic models, ensure even distribution of triangles to meet the unique requirements of rigging and deformation during animation.\n\n\n\nSuch optimization can lead to improved performance, reduced latency, and a more immersive VR experience for users.\n\n\n\nIt may require rethinking and overhauling existing modeling workflows, which could be resource-intensive.\n\n\n\nIgnoring the optimization could result in suboptimal performance, impacting the user experience and the scalability of V-Sekai projects.\n\n\n\nRare or unique objects and characters that require a departure from standard optimization practices to maintain their distinctiveness or functionality.\n\n\n\nThe proposal recommends integrating these optimization practices into the core development workflow of V-Sekai, handled by the internal team.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis proposal was assisted by Aria, an AI assistant."
+    "text": "V-Sekai development team\nFire"
   },
   {
-    "objectID": "decisions/20231226-furniture-vs-organic.html#metadata",
-    "href": "decisions/20231226-furniture-vs-organic.html#metadata",
-    "title": "Proposed: Hardsurface vs Organic",
+    "objectID": "decisions/20240710-platform-focus-on-pcvr-and-web.html#tags",
+    "href": "decisions/20240710-platform-focus-on-pcvr-and-web.html#tags",
+    "title": "Proposed: Focus on PCVR and the Web",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai, fire, msstabby\nTags: V-Sekai, VR, Godot Engine, 3D Modeling, Performance Optimization"
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20231226-furniture-vs-organic.html#context",
-    "href": "decisions/20231226-furniture-vs-organic.html#context",
-    "title": "Proposed: Hardsurface vs Organic",
+    "objectID": "decisions/20240710-platform-focus-on-pcvr-and-web.html#further-reading",
+    "href": "decisions/20240710-platform-focus-on-pcvr-and-web.html#further-reading",
+    "title": "Proposed: Focus on PCVR and the Web",
     "section": "",
-    "text": "V-Sekai is a vibrant platform for social VR experiences built on the Godot Engine. Its success hinges on the seamless integration of visually appealing 3D environments and characters that perform optimally across various VR hardware."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20231226-furniture-vs-organic.html#problem",
-    "href": "decisions/20231226-furniture-vs-organic.html#problem",
-    "title": "Proposed: Hardsurface vs Organic",
+    "objectID": "decisions/20240307-rabbitmq-ra.html",
+    "href": "decisions/20240307-rabbitmq-ra.html",
+    "title": "Proposed: Implement Ra in V-Sekai",
     "section": "",
-    "text": "The challenge lies in striking a balance between hardsurface (static objects) and organic (characters) modeling within V-Sekai. The goal is to optimize both types of models, reducing geometric complexity without compromising on visual richness or functional requirements of rigging and animation."
+    "text": "V-Sekai, a VR social network, needs reliable state machines for data persistence. Current system may struggle with data consistency and failure recovery.\n\n\n\nUser experience can be disrupted due to potential data inconsistencies and loss, leading to issues like lost interactions and inconsistent virtual states.\n\n\n\nImplement Ra, a Raft implementation by Team RabbitMQ, in any Erlang or Elixir project. Ra enables persistent, fault-tolerant, replicated state machines.\n\n\n\n\nFault Tolerance: Ra ensures data consistency via leader election and log replication.\nEfficiency: Supports log compaction and snapshot installation.\nScalability: Suitable for large-scale applications like V-Sekai.\n\n\n\n\n\nLearning Curve: Developers need to learn Ra and the Raft consensus algorithm.\nDependency: Ra could increase project complexity.\n\n\n\n\nOther solutions like CRDTs were considered but have major shortcomings.\n\n\n\nIn small distributed systems with rare failures, Ra’s benefits may not be fully realized.\n\n\n\nThe V-Sekai team will implement Ra.\n\n\n\nProposed\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\nRa\nErlang\nElixir\nDistributed Systems\n\n\n\n\n\nV-Sekai · GitHub\nV-Sekai/v-sekai-game\n\nAssisted by Aria, an AI assistant."
   },
   {
-    "objectID": "decisions/20231226-furniture-vs-organic.html#possible-solution",
-    "href": "decisions/20231226-furniture-vs-organic.html#possible-solution",
-    "title": "Proposed: Hardsurface vs Organic",
+    "objectID": "decisions/20240307-rabbitmq-ra.html#context",
+    "href": "decisions/20240307-rabbitmq-ra.html#context",
+    "title": "Proposed: Implement Ra in V-Sekai",
     "section": "",
-    "text": "Adopt different strategies for hardsurface and organic modeling. For hardsurface models, focus on reducing the number of triangles, especially for non-moving geometry like furniture. For organic models, ensure even distribution of triangles to meet the unique requirements of rigging and deformation during animation."
+    "text": "V-Sekai, a VR social network, needs reliable state machines for data persistence. Current system may struggle with data consistency and failure recovery."
   },
   {
-    "objectID": "decisions/20231226-furniture-vs-organic.html#pros",
-    "href": "decisions/20231226-furniture-vs-organic.html#pros",
-    "title": "Proposed: Hardsurface vs Organic",
+    "objectID": "decisions/20240307-rabbitmq-ra.html#problem",
+    "href": "decisions/20240307-rabbitmq-ra.html#problem",
+    "title": "Proposed: Implement Ra in V-Sekai",
     "section": "",
-    "text": "Such optimization can lead to improved performance, reduced latency, and a more immersive VR experience for users."
+    "text": "User experience can be disrupted due to potential data inconsistencies and loss, leading to issues like lost interactions and inconsistent virtual states."
   },
   {
-    "objectID": "decisions/20231226-furniture-vs-organic.html#cons",
-    "href": "decisions/20231226-furniture-vs-organic.html#cons",
-    "title": "Proposed: Hardsurface vs Organic",
+    "objectID": "decisions/20240307-rabbitmq-ra.html#solution",
+    "href": "decisions/20240307-rabbitmq-ra.html#solution",
+    "title": "Proposed: Implement Ra in V-Sekai",
     "section": "",
-    "text": "It may require rethinking and overhauling existing modeling workflows, which could be resource-intensive."
+    "text": "Implement Ra, a Raft implementation by Team RabbitMQ, in any Erlang or Elixir project. Ra enables persistent, fault-tolerant, replicated state machines."
   },
   {
-    "objectID": "decisions/20231226-furniture-vs-organic.html#alternatives",
-    "href": "decisions/20231226-furniture-vs-organic.html#alternatives",
-    "title": "Proposed: Hardsurface vs Organic",
+    "objectID": "decisions/20240307-rabbitmq-ra.html#benefits",
+    "href": "decisions/20240307-rabbitmq-ra.html#benefits",
+    "title": "Proposed: Implement Ra in V-Sekai",
     "section": "",
-    "text": "Ignoring the optimization could result in suboptimal performance, impacting the user experience and the scalability of V-Sekai projects."
+    "text": "Fault Tolerance: Ra ensures data consistency via leader election and log replication.\nEfficiency: Supports log compaction and snapshot installation.\nScalability: Suitable for large-scale applications like V-Sekai."
   },
   {
-    "objectID": "decisions/20231226-furniture-vs-organic.html#special-considerations",
-    "href": "decisions/20231226-furniture-vs-organic.html#special-considerations",
-    "title": "Proposed: Hardsurface vs Organic",
+    "objectID": "decisions/20240307-rabbitmq-ra.html#downsides",
+    "href": "decisions/20240307-rabbitmq-ra.html#downsides",
+    "title": "Proposed: Implement Ra in V-Sekai",
     "section": "",
-    "text": "Rare or unique objects and characters that require a departure from standard optimization practices to maintain their distinctiveness or functionality."
+    "text": "Learning Curve: Developers need to learn Ra and the Raft consensus algorithm.\nDependency: Ra could increase project complexity."
   },
   {
-    "objectID": "decisions/20231226-furniture-vs-organic.html#implementation",
-    "href": "decisions/20231226-furniture-vs-organic.html#implementation",
-    "title": "Proposed: Hardsurface vs Organic",
+    "objectID": "decisions/20240307-rabbitmq-ra.html#alternatives",
+    "href": "decisions/20240307-rabbitmq-ra.html#alternatives",
+    "title": "Proposed: Implement Ra in V-Sekai",
     "section": "",
-    "text": "The proposal recommends integrating these optimization practices into the core development workflow of V-Sekai, handled by the internal team."
+    "text": "Other solutions like CRDTs were considered but have major shortcomings."
   },
   {
-    "objectID": "decisions/20231226-furniture-vs-organic.html#references",
-    "href": "decisions/20231226-furniture-vs-organic.html#references",
-    "title": "Proposed: Hardsurface vs Organic",
+    "objectID": "decisions/20240307-rabbitmq-ra.html#infrequent-use-case",
+    "href": "decisions/20240307-rabbitmq-ra.html#infrequent-use-case",
+    "title": "Proposed: Implement Ra in V-Sekai",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis proposal was assisted by Aria, an AI assistant."
+    "text": "In small distributed systems with rare failures, Ra’s benefits may not be fully realized."
   },
   {
-    "objectID": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html",
-    "href": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html",
-    "title": "Proposed: Solve Renik directly rather than through many bone ik",
+    "objectID": "decisions/20240307-rabbitmq-ra.html#implementation",
+    "href": "decisions/20240307-rabbitmq-ra.html#implementation",
+    "title": "Proposed: Implement Ra in V-Sekai",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nWe want a robust character controller through V-Sekai renik, but we’re working on an abstract many bone ik and there wasn’t visible progress. The current approach is not yielding the desired results and is proving to be inefficient.\n\n\n\nPause many bone ik and update renik to use many bone ik technologies. This would involve refactoring the existing codebase to integrate the many bone ik technologies directly into the renik solution.\n\n\n\nTo be determined.\n\n\n\n\nMore efficient and direct solution for character control.\nBetter utilization of many bone ik technologies.\nPotential for improved performance and responsiveness in the final product.\n\n\n\n\n\nRequires significant refactoring of the existing codebase.\nPotential for introducing new bugs during the integration process.\nMay require additional resources and time to implement correctly.\n\n\n\n\nThis section is reserved for documenting past decisions and their outcomes.\n\n\n\nNo, this enhancement involves a fundamental change in how the character controller is implemented and cannot be achieved with a simple script workaround.\n\n\n\nYes, as the creators of the system, we have the best understanding of its architecture and potential improvements. Outsourcing or relying on external contributions may not align with our vision for the project.\n\n\n\n\nV-Sekai"
+    "text": "The V-Sekai team will implement Ra."
   },
   {
-    "objectID": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html#metadata",
-    "href": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html#metadata",
-    "title": "Proposed: Solve Renik directly rather than through many bone ik",
+    "objectID": "decisions/20240307-rabbitmq-ra.html#status",
+    "href": "decisions/20240307-rabbitmq-ra.html#status",
+    "title": "Proposed: Implement Ra in V-Sekai",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai"
+    "text": "Proposed"
   },
   {
-    "objectID": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html#context-and-problem-statement",
-    "href": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html#context-and-problem-statement",
-    "title": "Proposed: Solve Renik directly rather than through many bone ik",
+    "objectID": "decisions/20240307-rabbitmq-ra.html#decision-makers",
+    "href": "decisions/20240307-rabbitmq-ra.html#decision-makers",
+    "title": "Proposed: Implement Ra in V-Sekai",
     "section": "",
-    "text": "We want a robust character controller through V-Sekai renik, but we’re working on an abstract many bone ik and there wasn’t visible progress. The current approach is not yielding the desired results and is proving to be inefficient."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html#proposed-solution",
-    "href": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html#proposed-solution",
-    "title": "Proposed: Solve Renik directly rather than through many bone ik",
+    "objectID": "decisions/20240307-rabbitmq-ra.html#tags",
+    "href": "decisions/20240307-rabbitmq-ra.html#tags",
+    "title": "Proposed: Implement Ra in V-Sekai",
     "section": "",
-    "text": "Pause many bone ik and update renik to use many bone ik technologies. This would involve refactoring the existing codebase to integrate the many bone ik technologies directly into the renik solution."
+    "text": "V-Sekai\nRa\nErlang\nElixir\nDistributed Systems"
   },
   {
-    "objectID": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html#implementation",
-    "href": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html#implementation",
-    "title": "Proposed: Solve Renik directly rather than through many bone ik",
+    "objectID": "decisions/20240307-rabbitmq-ra.html#further-reading",
+    "href": "decisions/20240307-rabbitmq-ra.html#further-reading",
+    "title": "Proposed: Implement Ra in V-Sekai",
     "section": "",
-    "text": "To be determined."
+    "text": "V-Sekai · GitHub\nV-Sekai/v-sekai-game\n\nAssisted by Aria, an AI assistant."
   },
   {
-    "objectID": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html#positive-consequences",
-    "href": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html#positive-consequences",
-    "title": "Proposed: Solve Renik directly rather than through many bone ik",
+    "objectID": "decisions/20231203-graphsage-embedding-generation.html",
+    "href": "decisions/20231203-graphsage-embedding-generation.html",
+    "title": "Draft: GraphSAGE Embedding Algorithm Explanation",
     "section": "",
-    "text": "More efficient and direct solution for character control.\nBetter utilization of many bone ik technologies.\nPotential for improved performance and responsiveness in the final product."
+    "text": "Status: Draft\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nIn the world of graph-based machine learning, the GraphSAGE algorithm has emerged as a powerful tool for generating node embeddings. It’s an inductive method that learns to generate embeddings by leveraging node feature information and the graph structure.\n\n\n\nUnderstanding the GraphSAGE algorithm can be challenging due to its complex nature and the use of various mathematical concepts. This proposal aims to break down the algorithm into understandable components and explain how it works in a clear and concise manner.\n\n\n\n\n\n\nThe algorithm incrementally aggregates and updates the representations of each node by considering the information from its local neighbors at each depth.\nAs the depth K increases, nodes incorporate information from a wider neighborhood.\nThe choice of aggregator functions can vary and has a significant impact on the performance and the type of information aggregated.\n\n\n\n\n\nGraph G(V,E)G(V,E): The input graph with nodes VV and edges EE.\nInput Features {xv∀v∈V}{xv​∀v∈V}: The features for each node in the graph.\nDepth KK: The depth of the search or the number of iterations.\nWeight Matrices Wk∀k∈{1…K}Wk​∀k∈{1…K}: The weight matrices used for each depth kk.\nNon-linearity σσ: A non-linear activation function.\nAggregator Functions AGGREGATEk∀k∈{1…K}AGGREGATEk​∀k∈{1…K}: Functions that aggregate information from the node’s neighbors.\nNeighborhood Function NN: A function that returns the set of neighbors for a given node.\n\n\n\n\n\nVector Representations zv∀v∈Vzv​∀v∈V: The resulting vector representations for all nodes in the graph.\n\n\n\n\n\nInitialization: Each node’s feature vector xvxv​ is used as the initial representation hv0hv0​.\nIteration for Depth KK: For each depth level from 1 to KK:\n\nFor each node vv in the graph:\n\nAggregate the representations of the nodes in its neighborhood N(v)N(v) using the aggregator function AGGREGATEkAGGREGATEk​ for that depth. This results in a new vector hN(v)khN(v)k​.\nConcatenate this aggregated vector with the node’s current representation hvk−1hvk−1​, and apply the weight matrix WkWk​ followed by the non-linearity σσ. This results in the updated representation hvkhvk​.\nNormalize the updated representation.\n\n\nFinal Representations: After the final iteration KK, the output for each node vv, zvzv​, is set as its last representation hvKhvK​.\n\n\n\n\n\nThe algorithm incrementally aggregates and updates the representations of each node by considering the information from its local neighbors at each depth.\nAs the depth KK increases, nodes incorporate information from a wider neighborhood.\nThe choice of aggregator functions can vary and has a significant impact on the performance and the type of information aggregated.\n\n\n\n\n\nInductive Learning: Unlike traditional methods that require retraining for new nodes, this algorithm can generate embeddings for unseen nodes.\nFlexibility: The algorithm can be adapted to different types of graphs and feature sets.\nScalability: It’s designed to work efficiently on large graphs.\n\nUnderstanding this algorithm helps in applying it to real-world graph problems, such as social network analysis, recommendation systems, and more, where the structure and features of the graph can be leveraged to learn informative node embeddings.\n\n\n\n\nThe GraphSAGE algorithm provides a flexible and scalable solution for generating node embeddings in large graphs. It allows for inductive learning, which means it can handle unseen nodes without requiring retraining. This makes it particularly useful for dynamic graphs where nodes may be added or removed over time.\n\n\n\nThe algorithm’s performance heavily depends on the choice of aggregator functions and the quality of node features. Poorly chosen functions or low-quality features can lead to suboptimal embeddings. Additionally, the algorithm may not perform well on graphs with complex structures or those that lack sufficient node feature information.\n\n\n\nAlternative methods for generating node embeddings, such as transductive learning algorithms, could be considered. However, these methods typically require retraining when new nodes are added, making them less suitable for dynamic graphs.\n\n\n\nWhile GraphSAGE is highly effective for many graph-based machine learning tasks, it may not be the best choice for all scenarios. For instance, in cases where the graph structure is less important than node features, other methods like feature-based machine learning models might be more appropriate.\n\n\n\nYes, this explanation of the GraphSAGE algorithm has been developed by us, with assistance from AI assistant Aria.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nInductive Representation Learning on Large Graphs"
   },
   {
-    "objectID": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html#negative-consequences",
-    "href": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html#negative-consequences",
-    "title": "Proposed: Solve Renik directly rather than through many bone ik",
+    "objectID": "decisions/20231203-graphsage-embedding-generation.html#metadata",
+    "href": "decisions/20231203-graphsage-embedding-generation.html#metadata",
+    "title": "Draft: GraphSAGE Embedding Algorithm Explanation",
     "section": "",
-    "text": "Requires significant refactoring of the existing codebase.\nPotential for introducing new bugs during the integration process.\nMay require additional resources and time to implement correctly."
+    "text": "Status: Draft\nDeciders: V-Sekai\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html#option-graveyard",
-    "href": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html#option-graveyard",
-    "title": "Proposed: Solve Renik directly rather than through many bone ik",
+    "objectID": "decisions/20231203-graphsage-embedding-generation.html#the-backdrop",
+    "href": "decisions/20231203-graphsage-embedding-generation.html#the-backdrop",
+    "title": "Draft: GraphSAGE Embedding Algorithm Explanation",
     "section": "",
-    "text": "This section is reserved for documenting past decisions and their outcomes."
+    "text": "In the world of graph-based machine learning, the GraphSAGE algorithm has emerged as a powerful tool for generating node embeddings. It’s an inductive method that learns to generate embeddings by leveraging node feature information and the graph structure."
   },
   {
-    "objectID": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Solve Renik directly rather than through many bone ik",
+    "objectID": "decisions/20231203-graphsage-embedding-generation.html#the-challenge",
+    "href": "decisions/20231203-graphsage-embedding-generation.html#the-challenge",
+    "title": "Draft: GraphSAGE Embedding Algorithm Explanation",
     "section": "",
-    "text": "No, this enhancement involves a fundamental change in how the character controller is implemented and cannot be achieved with a simple script workaround."
+    "text": "Understanding the GraphSAGE algorithm can be challenging due to its complex nature and the use of various mathematical concepts. This proposal aims to break down the algorithm into understandable components and explain how it works in a clear and concise manner."
   },
   {
-    "objectID": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Solve Renik directly rather than through many bone ik",
+    "objectID": "decisions/20231203-graphsage-embedding-generation.html#the-strategy",
+    "href": "decisions/20231203-graphsage-embedding-generation.html#the-strategy",
+    "title": "Draft: GraphSAGE Embedding Algorithm Explanation",
     "section": "",
-    "text": "Yes, as the creators of the system, we have the best understanding of its architecture and potential improvements. Outsourcing or relying on external contributions may not align with our vision for the project."
+    "text": "The algorithm incrementally aggregates and updates the representations of each node by considering the information from its local neighbors at each depth.\nAs the depth K increases, nodes incorporate information from a wider neighborhood.\nThe choice of aggregator functions can vary and has a significant impact on the performance and the type of information aggregated.\n\n\n\n\n\nGraph G(V,E)G(V,E): The input graph with nodes VV and edges EE.\nInput Features {xv∀v∈V}{xv​∀v∈V}: The features for each node in the graph.\nDepth KK: The depth of the search or the number of iterations.\nWeight Matrices Wk∀k∈{1…K}Wk​∀k∈{1…K}: The weight matrices used for each depth kk.\nNon-linearity σσ: A non-linear activation function.\nAggregator Functions AGGREGATEk∀k∈{1…K}AGGREGATEk​∀k∈{1…K}: Functions that aggregate information from the node’s neighbors.\nNeighborhood Function NN: A function that returns the set of neighbors for a given node.\n\n\n\n\n\nVector Representations zv∀v∈Vzv​∀v∈V: The resulting vector representations for all nodes in the graph.\n\n\n\n\n\nInitialization: Each node’s feature vector xvxv​ is used as the initial representation hv0hv0​.\nIteration for Depth KK: For each depth level from 1 to KK:\n\nFor each node vv in the graph:\n\nAggregate the representations of the nodes in its neighborhood N(v)N(v) using the aggregator function AGGREGATEkAGGREGATEk​ for that depth. This results in a new vector hN(v)khN(v)k​.\nConcatenate this aggregated vector with the node’s current representation hvk−1hvk−1​, and apply the weight matrix WkWk​ followed by the non-linearity σσ. This results in the updated representation hvkhvk​.\nNormalize the updated representation.\n\n\nFinal Representations: After the final iteration KK, the output for each node vv, zvzv​, is set as its last representation hvKhvK​.\n\n\n\n\n\nThe algorithm incrementally aggregates and updates the representations of each node by considering the information from its local neighbors at each depth.\nAs the depth KK increases, nodes incorporate information from a wider neighborhood.\nThe choice of aggregator functions can vary and has a significant impact on the performance and the type of information aggregated.\n\n\n\n\n\nInductive Learning: Unlike traditional methods that require retraining for new nodes, this algorithm can generate embeddings for unseen nodes.\nFlexibility: The algorithm can be adapted to different types of graphs and feature sets.\nScalability: It’s designed to work efficiently on large graphs.\n\nUnderstanding this algorithm helps in applying it to real-world graph problems, such as social network analysis, recommendation systems, and more, where the structure and features of the graph can be leveraged to learn informative node embeddings."
   },
   {
-    "objectID": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html#references",
-    "href": "decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html#references",
-    "title": "Proposed: Solve Renik directly rather than through many bone ik",
+    "objectID": "decisions/20231203-graphsage-embedding-generation.html#the-upside",
+    "href": "decisions/20231203-graphsage-embedding-generation.html#the-upside",
+    "title": "Draft: GraphSAGE Embedding Algorithm Explanation",
     "section": "",
-    "text": "V-Sekai"
+    "text": "The GraphSAGE algorithm provides a flexible and scalable solution for generating node embeddings in large graphs. It allows for inductive learning, which means it can handle unseen nodes without requiring retraining. This makes it particularly useful for dynamic graphs where nodes may be added or removed over time."
   },
   {
-    "objectID": "decisions/20231201-xr-hands-animation-node.html",
-    "href": "decisions/20231201-xr-hands-animation-node.html",
-    "title": "Proposed: Seamless Integration of XR Tracking in Godot Engine",
+    "objectID": "decisions/20231203-graphsage-embedding-generation.html#the-downside",
+    "href": "decisions/20231203-graphsage-embedding-generation.html#the-downside",
+    "title": "Draft: GraphSAGE Embedding Algorithm Explanation",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai Project Maintainers\nTags: XR, Hand Tracking, Full Body Tracking, OpenXR, Godot Engine, Animation Retargeting\n\n\n\n\nThe document outlines the need for supporting hand and full body tracking in extended reality (XR) applications. As virtual and augmented reality technologies improve, developers seek methods to integrate external skeleton data, such as OpenXR hand tracking or “full body tracking” skeletons, with existing imported and skinned meshes within the Godot Engine.\n\n\n\nThe current implementation of OpenXR provides a bone structure model for hand tracking data, which is incorporated into the Godot Engine through an OpenXRHand helper node. This node transforms global position and orientation data into local space. However, this approach has compatibility issues due to the requirement that mesh structures strictly adhere to the OpenXR standard. Additionally, there’s a growing need to support solutions for vendor APIs offering “full body tracking” skeletons.\n\n\n\nTo address these limitations, we propose the introduction of an OpenXRSkeleton3D node. This new node will:\n\nConform to the OpenXR standard for consistency.\nInclude hardcoded rest poses based on open hands recorded using OpenXR to simplify development.\nApply tracked OpenXR data dynamically to generate pose animations.\n\nThis strategy enables advanced retargeting scenarios and improves the integration of partial tracking data to hand meshes, humanoid skeletons, and blending of tracked poses with static ones for specific interactions like object manipulation.\n\n\n\n\nIn AR, deforming the mesh to match the player’s actual hands and fingers can significantly enhance realism.\n\n\n\nIn VR, this strategy enables the representation of fixed-size avatar hands that do not vary with the player’s real hand size, similar to games like “Half-Life Alyx.”\n\n\n\n\n\nThe proposed solution will improve interoperability with other systems and standards, such as:\n\nApple’s Vision Pro: By implementing an AppleSkeleton3D node to accommodate format and skeleton definitions differences.\nWebXR: Potentially aligning with the OpenXR system.\nGodot Engine: Including additional metacarpal bones in the engine’s humanoid skeleton for accurate retargeting.\n\n\n\n\nThe system could also be beneficial for non-XR applications such as:\n\nAdjusting leg movement to avoid ground collision.\nSupporting procedural foot-planting techniques for realistic animation.\nTracking arms for dynamic motion capture.\nAllowing inverse kinematics setups similar to classic shooters like Doom (2016).\nProviding active ragdolls for lifelike physics responses, exemplified in Godot Engine Active Ragdolls.\n\n\n\n\n\nXR-Specific Node: This component extracts and refines hand-tracking data into a specialized Skeleton3D node.\nAnimation BlendTree Node: This node handles the complex task of retargeting data across different skeletons, enabling a mix-and-match approach to animation and physical interactions.\n\n\n\n\nA typical use case may involve two hand skeletons from different tracking sources being retargeted onto a third skeleton dedicated to visual representation within the Godot Engine environment or for physics-based interactions.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "The algorithm’s performance heavily depends on the choice of aggregator functions and the quality of node features. Poorly chosen functions or low-quality features can lead to suboptimal embeddings. Additionally, the algorithm may not perform well on graphs with complex structures or those that lack sufficient node feature information."
   },
   {
-    "objectID": "decisions/20231201-xr-hands-animation-node.html#metadata",
-    "href": "decisions/20231201-xr-hands-animation-node.html#metadata",
-    "title": "Proposed: Seamless Integration of XR Tracking in Godot Engine",
+    "objectID": "decisions/20231203-graphsage-embedding-generation.html#the-road-not-taken",
+    "href": "decisions/20231203-graphsage-embedding-generation.html#the-road-not-taken",
+    "title": "Draft: GraphSAGE Embedding Algorithm Explanation",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai Project Maintainers\nTags: XR, Hand Tracking, Full Body Tracking, OpenXR, Godot Engine, Animation Retargeting"
+    "text": "Alternative methods for generating node embeddings, such as transductive learning algorithms, could be considered. However, these methods typically require retraining when new nodes are added, making them less suitable for dynamic graphs."
   },
   {
-    "objectID": "decisions/20231201-xr-hands-animation-node.html#the-backdrop",
-    "href": "decisions/20231201-xr-hands-animation-node.html#the-backdrop",
-    "title": "Proposed: Seamless Integration of XR Tracking in Godot Engine",
+    "objectID": "decisions/20231203-graphsage-embedding-generation.html#the-infrequent-use-case",
+    "href": "decisions/20231203-graphsage-embedding-generation.html#the-infrequent-use-case",
+    "title": "Draft: GraphSAGE Embedding Algorithm Explanation",
     "section": "",
-    "text": "The document outlines the need for supporting hand and full body tracking in extended reality (XR) applications. As virtual and augmented reality technologies improve, developers seek methods to integrate external skeleton data, such as OpenXR hand tracking or “full body tracking” skeletons, with existing imported and skinned meshes within the Godot Engine."
+    "text": "While GraphSAGE is highly effective for many graph-based machine learning tasks, it may not be the best choice for all scenarios. For instance, in cases where the graph structure is less important than node features, other methods like feature-based machine learning models might be more appropriate."
   },
   {
-    "objectID": "decisions/20231201-xr-hands-animation-node.html#the-challenge",
-    "href": "decisions/20231201-xr-hands-animation-node.html#the-challenge",
-    "title": "Proposed: Seamless Integration of XR Tracking in Godot Engine",
+    "objectID": "decisions/20231203-graphsage-embedding-generation.html#in-core-and-done-by-us",
+    "href": "decisions/20231203-graphsage-embedding-generation.html#in-core-and-done-by-us",
+    "title": "Draft: GraphSAGE Embedding Algorithm Explanation",
     "section": "",
-    "text": "The current implementation of OpenXR provides a bone structure model for hand tracking data, which is incorporated into the Godot Engine through an OpenXRHand helper node. This node transforms global position and orientation data into local space. However, this approach has compatibility issues due to the requirement that mesh structures strictly adhere to the OpenXR standard. Additionally, there’s a growing need to support solutions for vendor APIs offering “full body tracking” skeletons."
+    "text": "Yes, this explanation of the GraphSAGE algorithm has been developed by us, with assistance from AI assistant Aria."
   },
   {
-    "objectID": "decisions/20231201-xr-hands-animation-node.html#the-strategy",
-    "href": "decisions/20231201-xr-hands-animation-node.html#the-strategy",
-    "title": "Proposed: Seamless Integration of XR Tracking in Godot Engine",
+    "objectID": "decisions/20231203-graphsage-embedding-generation.html#further-reading",
+    "href": "decisions/20231203-graphsage-embedding-generation.html#further-reading",
+    "title": "Draft: GraphSAGE Embedding Algorithm Explanation",
     "section": "",
-    "text": "To address these limitations, we propose the introduction of an OpenXRSkeleton3D node. This new node will:\n\nConform to the OpenXR standard for consistency.\nInclude hardcoded rest poses based on open hands recorded using OpenXR to simplify development.\nApply tracked OpenXR data dynamically to generate pose animations.\n\nThis strategy enables advanced retargeting scenarios and improves the integration of partial tracking data to hand meshes, humanoid skeletons, and blending of tracked poses with static ones for specific interactions like object manipulation.\n\n\n\n\nIn AR, deforming the mesh to match the player’s actual hands and fingers can significantly enhance realism.\n\n\n\nIn VR, this strategy enables the representation of fixed-size avatar hands that do not vary with the player’s real hand size, similar to games like “Half-Life Alyx.”"
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nInductive Representation Learning on Large Graphs"
   },
   {
-    "objectID": "decisions/20231201-xr-hands-animation-node.html#compatibility-with-other-systems",
-    "href": "decisions/20231201-xr-hands-animation-node.html#compatibility-with-other-systems",
-    "title": "Proposed: Seamless Integration of XR Tracking in Godot Engine",
+    "objectID": "decisions/20230806-music-gen.html",
+    "href": "decisions/20230806-music-gen.html",
+    "title": "Proposed: Sonic Symphony: Crafting Melodies with Machine Intelligence",
     "section": "",
-    "text": "The proposed solution will improve interoperability with other systems and standards, such as:\n\nApple’s Vision Pro: By implementing an AppleSkeleton3D node to accommodate format and skeleton definitions differences.\nWebXR: Potentially aligning with the OpenXR system.\nGodot Engine: Including additional metacarpal bones in the engine’s humanoid skeleton for accurate retargeting."
+    "text": "Status: proposed\nMasterminds: V-Sekai, fire\nKeywords: Music, AI, GPT-3, Python, Generation\n\n\n\n\nAs we navigate the 21st century, technology has become an inseparable part of our existence. It’s been making waves in the realm of music too. One such wave is the use of artificial intelligence (AI) to craft melodies. This blueprint proposes a method for creating music using computer algorithms.\n\n\n\nThe mission is to create music using computer programs.\n\n\n\nOne promising strategy is to employ .ABC files. These files have proven effective in generating outputs with AI models like GPT-3. The .ABC files carry data in the header section, such as the key signature, tempo, and time signature, which can be incorporated into the prompt.\nAlternatively, we could leverage AI models to script for us. For instance, we could ask for a Python script that composes the chromatic 7th intervals from C to B in eighth notes. The output format could be something user-friendly like Lilypond or MusicXML.\nHere’s a sneak peek at a Python script:\ndef generate_chromatic_seventh_intervals():\n    notes = ['C', 'C#', 'D', 'D#', 'E', 'F', 'F#', 'G', 'G#', 'A', 'A#', 'B']\n    intervals = []\n\n    for i in range(len(notes)):\n        seventh_interval = (i + 10) % len(notes)\n        intervals.append((notes[i], notes[seventh_interval]))\n\n    return intervals\n\nprint(generate_chromatic_seventh_intervals())\nAnother feasible strategy might be to use AI models to generate Lilypond syntax. Lilypond is a robust and adaptable tool for engraving tasks of all kinds, including sheet music, complex notation, vocal music, etc. Here is an example of a simple Lilypond syntax:\n\\relative c' {\n  c4 d e f |\n  g a b c |\n}\nThis code will compose a sequence of eighth notes from C to C.\n\n\n\nDuring the journey to find a solution, several paths were explored and abandoned for various reasons:\n\nUsing MIDI files: While MIDI files are a common choice for music creation, they were left behind due to their complexity and the challenge in crafting them programmatically.\nUsing MusicXML: Despite MusicXML being a comprehensive and widely supported format, it was abandoned due to its lengthy and intricate structure, which makes it tough to craft programmatically.\nUsing other music notation software: Other music notation software like Finale and Sibelius were considered but left behind due to their proprietary nature and lack of support for the programmatic generation of music.\n\n\n\n\n\nThis approach will pave the way for easier music creation.\nIt will sidestep the limitations posed by the intricate structure of MusicXML.\n\n\n\n\n\nThere may be some hurdles when using AI models to generate Lilypond syntax.\nTraining small transformers to output syntactically correct .ABC files might pose a challenge.\n\n\n\n\n\nSample .ABC files\nLilypond Notation Reference\nAsk HN: AI that produces sheet music for practice?"
   },
   {
-    "objectID": "decisions/20231201-xr-hands-animation-node.html#non-xr-use-cases-showcasing-broader-utility",
-    "href": "decisions/20231201-xr-hands-animation-node.html#non-xr-use-cases-showcasing-broader-utility",
-    "title": "Proposed: Seamless Integration of XR Tracking in Godot Engine",
+    "objectID": "decisions/20230806-music-gen.html#the-blueprint",
+    "href": "decisions/20230806-music-gen.html#the-blueprint",
+    "title": "Proposed: Sonic Symphony: Crafting Melodies with Machine Intelligence",
     "section": "",
-    "text": "The system could also be beneficial for non-XR applications such as:\n\nAdjusting leg movement to avoid ground collision.\nSupporting procedural foot-planting techniques for realistic animation.\nTracking arms for dynamic motion capture.\nAllowing inverse kinematics setups similar to classic shooters like Doom (2016).\nProviding active ragdolls for lifelike physics responses, exemplified in Godot Engine Active Ragdolls."
+    "text": "Status: proposed\nMasterminds: V-Sekai, fire\nKeywords: Music, AI, GPT-3, Python, Generation"
   },
   {
-    "objectID": "decisions/20231201-xr-hands-animation-node.html#core-components",
-    "href": "decisions/20231201-xr-hands-animation-node.html#core-components",
-    "title": "Proposed: Seamless Integration of XR Tracking in Godot Engine",
+    "objectID": "decisions/20230806-music-gen.html#the-backdrop",
+    "href": "decisions/20230806-music-gen.html#the-backdrop",
+    "title": "Proposed: Sonic Symphony: Crafting Melodies with Machine Intelligence",
     "section": "",
-    "text": "XR-Specific Node: This component extracts and refines hand-tracking data into a specialized Skeleton3D node.\nAnimation BlendTree Node: This node handles the complex task of retargeting data across different skeletons, enabling a mix-and-match approach to animation and physical interactions."
+    "text": "As we navigate the 21st century, technology has become an inseparable part of our existence. It’s been making waves in the realm of music too. One such wave is the use of artificial intelligence (AI) to craft melodies. This blueprint proposes a method for creating music using computer algorithms."
   },
   {
-    "objectID": "decisions/20231201-xr-hands-animation-node.html#application-scenarios",
-    "href": "decisions/20231201-xr-hands-animation-node.html#application-scenarios",
-    "title": "Proposed: Seamless Integration of XR Tracking in Godot Engine",
+    "objectID": "decisions/20230806-music-gen.html#the-challenge",
+    "href": "decisions/20230806-music-gen.html#the-challenge",
+    "title": "Proposed: Sonic Symphony: Crafting Melodies with Machine Intelligence",
     "section": "",
-    "text": "A typical use case may involve two hand skeletons from different tracking sources being retargeted onto a third skeleton dedicated to visual representation within the Godot Engine environment or for physics-based interactions."
+    "text": "The mission is to create music using computer programs."
   },
   {
-    "objectID": "decisions/20231201-xr-hands-animation-node.html#further-reading",
-    "href": "decisions/20231201-xr-hands-animation-node.html#further-reading",
-    "title": "Proposed: Seamless Integration of XR Tracking in Godot Engine",
+    "objectID": "decisions/20230806-music-gen.html#the-strategy",
+    "href": "decisions/20230806-music-gen.html#the-strategy",
+    "title": "Proposed: Sonic Symphony: Crafting Melodies with Machine Intelligence",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "One promising strategy is to employ .ABC files. These files have proven effective in generating outputs with AI models like GPT-3. The .ABC files carry data in the header section, such as the key signature, tempo, and time signature, which can be incorporated into the prompt.\nAlternatively, we could leverage AI models to script for us. For instance, we could ask for a Python script that composes the chromatic 7th intervals from C to B in eighth notes. The output format could be something user-friendly like Lilypond or MusicXML.\nHere’s a sneak peek at a Python script:\ndef generate_chromatic_seventh_intervals():\n    notes = ['C', 'C#', 'D', 'D#', 'E', 'F', 'F#', 'G', 'G#', 'A', 'A#', 'B']\n    intervals = []\n\n    for i in range(len(notes)):\n        seventh_interval = (i + 10) % len(notes)\n        intervals.append((notes[i], notes[seventh_interval]))\n\n    return intervals\n\nprint(generate_chromatic_seventh_intervals())\nAnother feasible strategy might be to use AI models to generate Lilypond syntax. Lilypond is a robust and adaptable tool for engraving tasks of all kinds, including sheet music, complex notation, vocal music, etc. Here is an example of a simple Lilypond syntax:\n\\relative c' {\n  c4 d e f |\n  g a b c |\n}\nThis code will compose a sequence of eighth notes from C to C."
   },
   {
-    "objectID": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html",
-    "href": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html",
-    "title": "Proposal: Stream a character from a webcam to the vmc protocol",
+    "objectID": "decisions/20230806-music-gen.html#the-road-not-taken",
+    "href": "decisions/20230806-music-gen.html#the-road-not-taken",
+    "title": "Proposed: Sonic Symphony: Crafting Melodies with Machine Intelligence",
     "section": "",
-    "text": "Status: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nStream a character from a webcam to the vmc protocol so it can be played in any VMC receiver.\n\n\n\nKalidokit packages mediapipe, opengl acceleration and tensorflow.\n\n\n\nUse kalidokit and have it output the vmc protocol using osc.js.\n\n\n\n\nOutput OSC.js which Godot Engine can use.\n\n\n\n\n\nUses the nodejs runtimes which is added complexity.\n\n\n\n\n\nOption: \nRejection Reason: \n\n\n\n\nNot a few lines of script.\n\n\n\nI joined the dots.\n\n\n\n\nhttps://github.com/infosia/vmc2bvh\nhttps://github.com/colinbdclark/osc.js/\n\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "During the journey to find a solution, several paths were explored and abandoned for various reasons:\n\nUsing MIDI files: While MIDI files are a common choice for music creation, they were left behind due to their complexity and the challenge in crafting them programmatically.\nUsing MusicXML: Despite MusicXML being a comprehensive and widely supported format, it was abandoned due to its lengthy and intricate structure, which makes it tough to craft programmatically.\nUsing other music notation software: Other music notation software like Finale and Sibelius were considered but left behind due to their proprietary nature and lack of support for the programmatic generation of music."
   },
   {
-    "objectID": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html#context-and-problem-statement",
-    "href": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html#context-and-problem-statement",
-    "title": "Proposal: Stream a character from a webcam to the vmc protocol",
+    "objectID": "decisions/20230806-music-gen.html#the-upside",
+    "href": "decisions/20230806-music-gen.html#the-upside",
+    "title": "Proposed: Sonic Symphony: Crafting Melodies with Machine Intelligence",
     "section": "",
-    "text": "Stream a character from a webcam to the vmc protocol so it can be played in any VMC receiver."
+    "text": "This approach will pave the way for easier music creation.\nIt will sidestep the limitations posed by the intricate structure of MusicXML."
   },
   {
-    "objectID": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposal: Stream a character from a webcam to the vmc protocol",
+    "objectID": "decisions/20230806-music-gen.html#the-downside",
+    "href": "decisions/20230806-music-gen.html#the-downside",
+    "title": "Proposed: Sonic Symphony: Crafting Melodies with Machine Intelligence",
     "section": "",
-    "text": "Kalidokit packages mediapipe, opengl acceleration and tensorflow."
+    "text": "There may be some hurdles when using AI models to generate Lilypond syntax.\nTraining small transformers to output syntactically correct .ABC files might pose a challenge."
   },
   {
-    "objectID": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposal: Stream a character from a webcam to the vmc protocol",
+    "objectID": "decisions/20230806-music-gen.html#further-reading",
+    "href": "decisions/20230806-music-gen.html#further-reading",
+    "title": "Proposed: Sonic Symphony: Crafting Melodies with Machine Intelligence",
     "section": "",
-    "text": "Use kalidokit and have it output the vmc protocol using osc.js."
+    "text": "Sample .ABC files\nLilypond Notation Reference\nAsk HN: AI that produces sheet music for practice?"
   },
   {
-    "objectID": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html#positive-consequences",
-    "href": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html#positive-consequences",
-    "title": "Proposal: Stream a character from a webcam to the vmc protocol",
+    "objectID": "decisions/20211031-bake-blend-shape-to-skeleton-animation.html",
+    "href": "decisions/20211031-bake-blend-shape-to-skeleton-animation.html",
+    "title": "Proposed: Bake blend shape to skeleton animation",
     "section": "",
-    "text": "Output OSC.js which Godot Engine can use."
+    "text": "Proposed: Bake blend shape to skeleton animation\n\nContext and Problem Statement\nBlend shapes are expensive and hard to interpolate\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nWant to bake blend shapes to animations.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n./DemBones -i=\"Face_Geom.fbx\" -a=\"Face_Anim.abc\" --bindUpdate=2 -o=\"Decomposition_20_grouped_face.fbx\" --nnz=8 -b=256\nNote that the corresponding fbx is 0.01 scale while the alembic is in meters.\nThe RMSE = 0.00433256 must be this low.\nDo not pass #dembones if the RMSE is like 3.5.\nNext step is to integrate an existing 3d skeleton.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot a few lines of script.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nWe control the default skeleton controller.\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html#negative-consequences",
-    "href": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html#negative-consequences",
-    "title": "Proposal: Stream a character from a webcam to the vmc protocol",
+    "objectID": "decisions/20220318-merge-retargeting-pr.html",
+    "href": "decisions/20220318-merge-retargeting-pr.html",
+    "title": "Proposed: Merge retargeting feature into Godot Engine master",
     "section": "",
-    "text": "Uses the nodejs runtimes which is added complexity."
+    "text": "Proposed: Merge retargeting feature into Godot Engine master\n\nDescribe the status of the issue.\nSuperseded by the https://github.com/V-Sekai/V-Sekai.github.io/issues/229 proposal.\n\n\nList the deciders of the issue.\nV-Sekai,tokage,fire,lyuma\n\n\nDescribe the tags of the issue.\nV-Sekai,animation,retargeting,\n\n\nContext and Problem Statement\nWe want to share animations among different skeletons.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nUse tokage’s animation retargeting.\n\nLyuma’s explanations\nFirst of all, Local (rest) and Absolute modes are not good enough for most of the common retargeting cases. As a test,. I transferred a local animation from one character to an Xbot model, and the animation was broken. See here: left is Global (GLO) which works well. Right is Local (LOC) which has arms and body backwards (image below).\nSo the question is: when is Global not good enough? Well, it is not well suited for finger bones. By its very nature, it does not know how finger bones work, since it is working on the “silhouette” of the model.\nThis means none of these retargeting modes are good enough on their own. So what can we do about it?\nPerhaps it is possible to create an importer which twists fingers in the Bone Rest matrix into a configuration suitable for Global retargeting? I can’t say whether or not this is possible, but if this could be solved, then maybe we can use Global mode for everything?\nIt could be declared that finger bones shall be local, and all other bones shall be global, and everyone making assets should agree on finger rotations. This might not always be possible, but this is my interpretation of reduz’s idea of storing the PlaybackMode in Node B in Tokage’s diagram.\nOr it could be left up to each animation artist / importer which to use, and then you’re going to have a mixture of modes. If so, I see two ways to deal with it:\nThe animations are stored in global along with skeleton and converted using the source skeleton. This sounds ok in principle if some conversion tool could be made, but I would be afraid to deal with converting animations on the fly at runtime.\nThe animations must point to the RetargetOption they were generated with (or a per-track retarget mode), so that these differently sourced animations can be mixed.\nfrom what I can understand, “2” is what Tokage is proposing. I don’t see many other solutions to this. Fundamentally, if it is the case that animations made from different models are needed to be mixed, I don’t see a viable solution other than the last one.\n\n\n\n158130997-7582d581-2b3c-45f5-b28f-deb26f2f6ffd\n\n\n\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\n\nSee pull request.\n\n\n\nPositive Consequences\n\nSharing animations will make Godot Engine better.\n\n\n\nNegative Consequences\n\nThe feature is hard to do.\n\n\n\nOption graveyard\n\nUse Blender and other types of retargeting\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\n\nNOT A FEW LINES OF SCRIPT!!!\n\n\n\nIs there a reason why this should be core and done by us?\n\nThis should be a core feature of Godot Engine.\n\n\n\nReferences\n\nV-Sekai\nhttps://github.com/godotengine/godot/pull/56902\n\n\n\nLicense of the contribution\nCopyright (c) 2022 V-Sekai contributors. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html#option-graveyard",
-    "href": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html#option-graveyard",
-    "title": "Proposal: Stream a character from a webcam to the vmc protocol",
+    "objectID": "decisions/20240110-magical-girls-college-novel.html",
+    "href": "decisions/20240110-magical-girls-college-novel.html",
+    "title": "Proposed: Magical Girls College Manager Simulator",
     "section": "",
-    "text": "Option: \nRejection Reason:"
+    "text": "Status: Proposed\nDeciders: V-Sekai, Cthulhoo, fire\nTags: V-Sekai\n\n\n\n\nA new game concept where players manage a college for magical girls has been proposed. Inspired by “Shadows of Doubt,” the game will focus on time management, relationship building, and academic success in a magical setting.\n\n\nShadows of Doubt on Steam\nA sandbox stealth game set in an alternate 1980s universe, blending detective work with gathering intelligence and solving cases.\n\n\n\n\nDevelop engaging planner scenarios for the player to navigate over the course of a week.\n\n\n\nUtilize VRM 3D chibis for character representation; initially limiting characters to five core members:\n\nThe Protagonist\nFour love interests\n\n\n\n\n\nStudents can earn study points by:\n\nAttending lectures\nCompleting homework\nStudying in the library\nEngaging in practical exercises\n\n\n\n\nCharacters can build relationships through activities:\n\nEating at the mess hall (easy, small benefit)\nGrabbing coffee together (small benefit)\nWatching movies at the cinema (moderate difficulty and benefit)\nHanging out at the pool (moderately challenging, moderate benefit)\nPicnicking in the park (challenging, moderate benefit)\nBeach trips (most challenging, high benefit)\n\n\n\n\nTo prevent burnout, students can:\n\nRead books\nPartake in hobbies\nParticipate in club activities\nEngage in chaste handholding\n\nSpecial considerations are given to individual preferences affecting decision outcomes, such as preferred or disliked activities impacting the willingness to participate.\n\n\n\n\n\n\nBurnout Management: A single meter may represent stamina and morale, balancing academic and social demands.\nPlanning Interface: Players plan weekly activities that unfold in real-time, adapting to emergent scenarios and random events.\nDuration: Each playthrough is one week long, split into weekdays and weekends, offering a chance to assess and strategize for the coming weeks.\n\n\n\n\nThis simulator offers a unique blend of time management, relationship simulation, and supernatural elements that appeal to various gaming audiences.\n\n\n\nComplex AI planning and character interaction mechanics could pose development challenges.\n\n\n\nThe decision to exclude a Pokemon-style battle system indicates a conscious move away from combat-oriented gameplay in favor of a simulation that emphasizes time management and social interactions within an academic setting. This choice differentiates the game from typical fantasy or RPG genres, focusing instead on daily life and relationship dynamics amongst magical girls.\nAlternative paths that were not taken might include:\n\nComplex combat systems with magical abilities.\nAn overarching narrative driven by external conflicts or villains.\nExpansion of the school’s supernatural elements beyond academic settings into broader world-saving quests.\n\nBy not pursuing these elements, the game remains intimate, allowing players to deeply explore the nuances of daily decisions and their impacts on personal growth and friendships.\n\n\n\nThough primary focus lies on managing relationships and academics within the college, rare use cases might involve:\n\nHandling exceptional magical crises that disrupt the normal flow of school life, requiring strategic changes to weekly planning.\nSpecial events such as magical tournaments or festivals, where characters must balance celebration with responsibilities.\nUnique narrative branches that only occur under specific conditions, adding replayability and depth to the character arcs.\n\nAddressing infrequent use cases can add layers of complexity and engagement for players, offering surprises and challenges that disrupt the routine management aspects of the game.\n\n\n\nThe V-Sekai team will decide core features and their implementation internally.\n\n\n\n\nV-Sekai GitHub Account\nV-Sekai Game Repository\n\nAI assistant Aria contributed to this proposal."
   },
   {
-    "objectID": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposal: Stream a character from a webcam to the vmc protocol",
+    "objectID": "decisions/20240110-magical-girls-college-novel.html#metadata",
+    "href": "decisions/20240110-magical-girls-college-novel.html#metadata",
+    "title": "Proposed: Magical Girls College Manager Simulator",
     "section": "",
-    "text": "Not a few lines of script."
+    "text": "Status: Proposed\nDeciders: V-Sekai, Cthulhoo, fire\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposal: Stream a character from a webcam to the vmc protocol",
+    "objectID": "decisions/20240110-magical-girls-college-novel.html#the-backdrop",
+    "href": "decisions/20240110-magical-girls-college-novel.html#the-backdrop",
+    "title": "Proposed: Magical Girls College Manager Simulator",
     "section": "",
-    "text": "I joined the dots."
+    "text": "A new game concept where players manage a college for magical girls has been proposed. Inspired by “Shadows of Doubt,” the game will focus on time management, relationship building, and academic success in a magical setting.\n\n\nShadows of Doubt on Steam\nA sandbox stealth game set in an alternate 1980s universe, blending detective work with gathering intelligence and solving cases."
   },
   {
-    "objectID": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html#references",
-    "href": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html#references",
-    "title": "Proposal: Stream a character from a webcam to the vmc protocol",
+    "objectID": "decisions/20240110-magical-girls-college-novel.html#the-challenge",
+    "href": "decisions/20240110-magical-girls-college-novel.html#the-challenge",
+    "title": "Proposed: Magical Girls College Manager Simulator",
     "section": "",
-    "text": "https://github.com/infosia/vmc2bvh\nhttps://github.com/colinbdclark/osc.js/"
+    "text": "Develop engaging planner scenarios for the player to navigate over the course of a week."
   },
   {
-    "objectID": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html#derivative-license",
-    "href": "decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html#derivative-license",
-    "title": "Proposal: Stream a character from a webcam to the vmc protocol",
+    "objectID": "decisions/20240110-magical-girls-college-novel.html#the-strategy",
+    "href": "decisions/20240110-magical-girls-college-novel.html#the-strategy",
+    "title": "Proposed: Magical Girls College Manager Simulator",
     "section": "",
-    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Utilize VRM 3D chibis for character representation; initially limiting characters to five core members:\n\nThe Protagonist\nFour love interests\n\n\n\n\n\nStudents can earn study points by:\n\nAttending lectures\nCompleting homework\nStudying in the library\nEngaging in practical exercises\n\n\n\n\nCharacters can build relationships through activities:\n\nEating at the mess hall (easy, small benefit)\nGrabbing coffee together (small benefit)\nWatching movies at the cinema (moderate difficulty and benefit)\nHanging out at the pool (moderately challenging, moderate benefit)\nPicnicking in the park (challenging, moderate benefit)\nBeach trips (most challenging, high benefit)\n\n\n\n\nTo prevent burnout, students can:\n\nRead books\nPartake in hobbies\nParticipate in club activities\nEngage in chaste handholding\n\nSpecial considerations are given to individual preferences affecting decision outcomes, such as preferred or disliked activities impacting the willingness to participate."
   },
   {
-    "objectID": "decisions/20230911-can-poly-green-coords-extend-to-3d.html",
-    "href": "decisions/20230911-can-poly-green-coords-extend-to-3d.html",
-    "title": "Draft: Can Poly Green Coords extend to 3d?",
+    "objectID": "decisions/20240110-magical-girls-college-novel.html#gameplay-mechanics",
+    "href": "decisions/20240110-magical-girls-college-novel.html#gameplay-mechanics",
+    "title": "Proposed: Magical Girls College Manager Simulator",
     "section": "",
-    "text": "Draft: Can Poly Green Coords extend to 3d?\nReminded by works by pixar: https://graphics.pixar.com/library/ProfileMover/\nHow applicable is this to 3d polygonal cages?\nYou may be interested by *[Green Coordinates for Triquad Cages in 3D](https://research.adobe.com/publication/green-coordinates-for-triquad-cages-in-3d/)* by Thiery and Boubekeur (SIGGRAPH Asia 2022). It is only for straight polygons though, the deformed cage cannot have Bézier arcs like this 2D version has, that's future work. ;) Profile curves are definitely a very nice and related work!\nOriginally posted by @eliemichel in https://github.com/eliemichel/PolyGreenCoords/issues/1#issuecomment-1683045650"
+    "text": "Burnout Management: A single meter may represent stamina and morale, balancing academic and social demands.\nPlanning Interface: Players plan weekly activities that unfold in real-time, adapting to emergent scenarios and random events.\nDuration: Each playthrough is one week long, split into weekdays and weekends, offering a chance to assess and strategize for the coming weeks."
   },
   {
-    "objectID": "decisions/20231218-mtlx-try-two.html",
-    "href": "decisions/20231218-mtlx-try-two.html",
-    "title": "Proposed: MaterialX try two.",
+    "objectID": "decisions/20240110-magical-girls-college-novel.html#the-upside",
+    "href": "decisions/20240110-magical-girls-college-novel.html#the-upside",
+    "title": "Proposed: Magical Girls College Manager Simulator",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nThe conversation revolves around the implementation of MaterialX in Blender nodes and its extension to glTF. The goal is to have an official KHR extension for MaterialX in glTF, which Blender should also support.\n\n\n\nThis proposal discusses implementing MaterialX in Blender nodes and extending it to glTF. The aim is to support an official KHR extension for MaterialX in glTF.\n\n\n\nThe plan is to first implement MaterialX in Blender nodes, then extend it to glTF. Once a KHR extension exists for MaterialX in glTF, Blender should add that.\n\n\n\nIf successful, this will allow for more efficient and effective use of MaterialX in Blender and its extensions. It will also pave the way for further developments and improvements in this area.\n\n\n\nThe downside is that this is a complex task that requires deep understanding and expertise in both Blender and MaterialX. There may also be unforeseen challenges and issues that could arise during the implementation process.\n\n\n\nSuccess will enhance MaterialX use in Blender and its extensions. However, this complex task requires deep expertise in both Blender and MaterialX and may face unforeseen challenges.\n\n\n\nAn alternative could be focusing on MaterialX’s functionality with OpenGL before its implementation in Blender nodes and glTF. Or using Material maker or Substance Designer.\n\n\n\nThis core proposal will be executed by the V-Sekai team.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
+    "text": "This simulator offers a unique blend of time management, relationship simulation, and supernatural elements that appeal to various gaming audiences."
   },
   {
-    "objectID": "decisions/20231218-mtlx-try-two.html#metadata",
-    "href": "decisions/20231218-mtlx-try-two.html#metadata",
-    "title": "Proposed: MaterialX try two.",
+    "objectID": "decisions/20240110-magical-girls-college-novel.html#the-downside",
+    "href": "decisions/20240110-magical-girls-college-novel.html#the-downside",
+    "title": "Proposed: Magical Girls College Manager Simulator",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai"
+    "text": "Complex AI planning and character interaction mechanics could pose development challenges."
   },
   {
-    "objectID": "decisions/20231218-mtlx-try-two.html#the-backdrop",
-    "href": "decisions/20231218-mtlx-try-two.html#the-backdrop",
-    "title": "Proposed: MaterialX try two.",
+    "objectID": "decisions/20240110-magical-girls-college-novel.html#the-road-not-taken",
+    "href": "decisions/20240110-magical-girls-college-novel.html#the-road-not-taken",
+    "title": "Proposed: Magical Girls College Manager Simulator",
     "section": "",
-    "text": "The conversation revolves around the implementation of MaterialX in Blender nodes and its extension to glTF. The goal is to have an official KHR extension for MaterialX in glTF, which Blender should also support."
+    "text": "The decision to exclude a Pokemon-style battle system indicates a conscious move away from combat-oriented gameplay in favor of a simulation that emphasizes time management and social interactions within an academic setting. This choice differentiates the game from typical fantasy or RPG genres, focusing instead on daily life and relationship dynamics amongst magical girls.\nAlternative paths that were not taken might include:\n\nComplex combat systems with magical abilities.\nAn overarching narrative driven by external conflicts or villains.\nExpansion of the school’s supernatural elements beyond academic settings into broader world-saving quests.\n\nBy not pursuing these elements, the game remains intimate, allowing players to deeply explore the nuances of daily decisions and their impacts on personal growth and friendships."
   },
   {
-    "objectID": "decisions/20231218-mtlx-try-two.html#the-challenge",
-    "href": "decisions/20231218-mtlx-try-two.html#the-challenge",
-    "title": "Proposed: MaterialX try two.",
+    "objectID": "decisions/20240110-magical-girls-college-novel.html#the-infrequent-use-case",
+    "href": "decisions/20240110-magical-girls-college-novel.html#the-infrequent-use-case",
+    "title": "Proposed: Magical Girls College Manager Simulator",
     "section": "",
-    "text": "This proposal discusses implementing MaterialX in Blender nodes and extending it to glTF. The aim is to support an official KHR extension for MaterialX in glTF."
+    "text": "Though primary focus lies on managing relationships and academics within the college, rare use cases might involve:\n\nHandling exceptional magical crises that disrupt the normal flow of school life, requiring strategic changes to weekly planning.\nSpecial events such as magical tournaments or festivals, where characters must balance celebration with responsibilities.\nUnique narrative branches that only occur under specific conditions, adding replayability and depth to the character arcs.\n\nAddressing infrequent use cases can add layers of complexity and engagement for players, offering surprises and challenges that disrupt the routine management aspects of the game."
   },
   {
-    "objectID": "decisions/20231218-mtlx-try-two.html#the-strategy",
-    "href": "decisions/20231218-mtlx-try-two.html#the-strategy",
-    "title": "Proposed: MaterialX try two.",
+    "objectID": "decisions/20240110-magical-girls-college-novel.html#in-core-and-done-by-us",
+    "href": "decisions/20240110-magical-girls-college-novel.html#in-core-and-done-by-us",
+    "title": "Proposed: Magical Girls College Manager Simulator",
     "section": "",
-    "text": "The plan is to first implement MaterialX in Blender nodes, then extend it to glTF. Once a KHR extension exists for MaterialX in glTF, Blender should add that."
+    "text": "The V-Sekai team will decide core features and their implementation internally."
   },
   {
-    "objectID": "decisions/20231218-mtlx-try-two.html#the-upside",
-    "href": "decisions/20231218-mtlx-try-two.html#the-upside",
-    "title": "Proposed: MaterialX try two.",
+    "objectID": "decisions/20240110-magical-girls-college-novel.html#further-reading",
+    "href": "decisions/20240110-magical-girls-college-novel.html#further-reading",
+    "title": "Proposed: Magical Girls College Manager Simulator",
     "section": "",
-    "text": "If successful, this will allow for more efficient and effective use of MaterialX in Blender and its extensions. It will also pave the way for further developments and improvements in this area."
+    "text": "V-Sekai GitHub Account\nV-Sekai Game Repository\n\nAI assistant Aria contributed to this proposal."
   },
   {
-    "objectID": "decisions/20231218-mtlx-try-two.html#the-downside",
-    "href": "decisions/20231218-mtlx-try-two.html#the-downside",
-    "title": "Proposed: MaterialX try two.",
+    "objectID": "decisions/20220624-webcam-to-posed-characters.html",
+    "href": "decisions/20220624-webcam-to-posed-characters.html",
+    "title": "Proposed: Connect Mediapipe to Blender",
     "section": "",
-    "text": "The downside is that this is a complex task that requires deep understanding and expertise in both Blender and MaterialX. There may also be unforeseen challenges and issues that could arise during the implementation process."
+    "text": "Proposed: Connect Mediapipe to Blender\n\nContext and Problem Statement\nWant to animate a blender file with mediapipe\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nBy writing a c++ executable on Linux, we can connect Mediapipe to Blender.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n\nCreate a wrapper for https://github.com/infosia/vmc2bvh/tree/master/osc\nInstall Blender addon https://github.com/maybites/blender.NodeOSC\nConvert python script to c++\nMake c++ buildable by bazel\nBuild executables on Github Actions\n\n\nDesign loop\n\nhttps://github.com/CLIUtils/CLI11 for command line parsing\nhttps://github.com/infosia/vmc2bvh/blob/master/code/Vmc2Bvh.cpp for example code\nFor each process send osc to node osc (Blender).\nCreate a structure for the messages\n\n\n\nNotes from Lox\nI looked at your mediapipe code.\nI can write pseudocode but since i don’t have a cpp toolchain, i can’t guarantee it’ll work\nYou might take a look at my code\nhttps://gitlab.com/-/snippets/2349711#LC70\nThe idea is quite simple:\ncompute hips and chest 3d position by averaging left+right hips and left+right shoulders 3d landmark.\ncompute hips and chest 2d position similarly using 2d landmark.\ncompute the spine length as the hips-chest distance for both 3d and 2d.\nthe 2d-to-3d scale factor is then the ratio of the two distances.\nhips world position will be hips 2d position scaled by the factor, with z=0\nhow do I get the 3d landmarks\nthat’s provided by API https://google.github.io/mediapipe/solutions/pose#pose_world_landmarks\nlox9973 — Today at 01:26\n2d landmarks: output.pose_landmarks\n3d landmarks: output.pose_world_landmarks\nthey are both 4d vectors\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nML and armature work is hard\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nIt’s needed for face tracking to work well.\n\n\nReferences\nFrom Kendrick\n\nmedia_pipe_demo.zip\nhttps://github.com/V-Sekai/game-tools-V-Sekai\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20231218-mtlx-try-two.html#the-road-not-taken",
-    "href": "decisions/20231218-mtlx-try-two.html#the-road-not-taken",
-    "title": "Proposed: MaterialX try two.",
+    "objectID": "decisions/20231112-archive-projects.html",
+    "href": "decisions/20231112-archive-projects.html",
+    "title": "Proposed: Effective V-Sekai project archival strategy",
     "section": "",
-    "text": "Success will enhance MaterialX use in Blender and its extensions. However, this complex task requires deep expertise in both Blender and MaterialX and may face unforeseen challenges."
+    "text": "Status: Proposed\nDeciders: V-Sekai, fire, arne\nTags: V-Sekai, Documentation, Project Archiving\n\n\n\n\nThe need for an effective project archival strategy has been highlighted by the experience of going through old projects without any structure or crucial data. This proposal aims to overcome this challenge in the context of V-Sekai projects.\n\n\n\nThe main challenge is to create a structured and comprehensive archive of V-Sekai projects that will allow easy access and understanding of each project even years after its completion.\n\n\n\nThe proposed strategy includes:\n\nMaintaining online projects: If a project is hosted online, doesn’t necessitate upkeep and isn’t financially burdensome, it’s best to keep it live for easy future reference.\nStructuring offline projects: For those projects that aren’t feasible to keep online, store them in your local file system. Establish a main folder with yearly subfolders for systematic organization.\nCapturing screenshots: Screenshots serve as a quick visual reference of your project without the need to set it up again.\nCreating screen recordings: For a more comprehensive record, consider creating a screen recording of your project—this not only captures the visual aspect but also records any audio commentary you might provide.\nIncorporating a README: Include a README file that outlines the purpose of the project, its creation and abandonment dates, contributors, and instructions to get it up and running again. This provides essential information about the project at a glance.\nSecuring the database: In cases where projects lack a database dump, all the actual content could be lost. Execute a sqldump or use the export functionality your database offers to create a backup alongside your files. This ensures data preservation.\nRetaining generated assets: When utilizing static site generators, include the directory containing the compiled HTML, CSS & JS in the archive. This allows you to easily browse the complete website by simply running a static file server.\nArchiving on the Internet Archive: If the platform hosting your content isn’t owned by you (for instance, you’re publishing to Discord or Github), consider saving your data to the Archive.org. This adds an extra level of security for preserving your projects.\n\n\n\n\nThis strategy will ensure that all V-Sekai projects are well-documented and easily accessible in the future. It will also help in preserving the history and evolution of V-Sekai projects over time.\n\n\n\nThe process might be time-consuming and require regular updates and maintenance.\n\n\n\nAn alternative could be to use a cloud-based storage service for archiving projects. However, this might not provide the same level of organization and accessibility as the proposed strategy.\n\n\n\nIn cases where a project was short-lived or did not have significant impact, it might be decided to not include it in the archive.\n\n\n\nYes, this strategy should be implemented by the V-Sekai team as it directly affects the organization and preservation of their projects.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\narne.me/articles/archive-your-old-projects\n\nThis article was assisted by AI assistant Aria."
   },
   {
-    "objectID": "decisions/20231218-mtlx-try-two.html#the-infrequent-use-case",
-    "href": "decisions/20231218-mtlx-try-two.html#the-infrequent-use-case",
-    "title": "Proposed: MaterialX try two.",
+    "objectID": "decisions/20231112-archive-projects.html#metadata",
+    "href": "decisions/20231112-archive-projects.html#metadata",
+    "title": "Proposed: Effective V-Sekai project archival strategy",
     "section": "",
-    "text": "An alternative could be focusing on MaterialX’s functionality with OpenGL before its implementation in Blender nodes and glTF. Or using Material maker or Substance Designer."
+    "text": "Status: Proposed\nDeciders: V-Sekai, fire, arne\nTags: V-Sekai, Documentation, Project Archiving"
   },
   {
-    "objectID": "decisions/20231218-mtlx-try-two.html#in-core-and-done-by-us",
-    "href": "decisions/20231218-mtlx-try-two.html#in-core-and-done-by-us",
-    "title": "Proposed: MaterialX try two.",
+    "objectID": "decisions/20231112-archive-projects.html#the-backdrop",
+    "href": "decisions/20231112-archive-projects.html#the-backdrop",
+    "title": "Proposed: Effective V-Sekai project archival strategy",
     "section": "",
-    "text": "This core proposal will be executed by the V-Sekai team."
+    "text": "The need for an effective project archival strategy has been highlighted by the experience of going through old projects without any structure or crucial data. This proposal aims to overcome this challenge in the context of V-Sekai projects."
   },
   {
-    "objectID": "decisions/20231218-mtlx-try-two.html#further-reading",
-    "href": "decisions/20231218-mtlx-try-two.html#further-reading",
-    "title": "Proposed: MaterialX try two.",
+    "objectID": "decisions/20231112-archive-projects.html#the-challenge",
+    "href": "decisions/20231112-archive-projects.html#the-challenge",
+    "title": "Proposed: Effective V-Sekai project archival strategy",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
+    "text": "The main challenge is to create a structured and comprehensive archive of V-Sekai projects that will allow easy access and understanding of each project even years after its completion."
   },
   {
-    "objectID": "decisions/20220118-convert-gltf-to-a-scene.html",
-    "href": "decisions/20220118-convert-gltf-to-a-scene.html",
-    "title": "Accepted: Convert gltf to a scene with AudioStreamPlayer3D, convert AudiostreamPlayer3D to gltf and expose usability.",
+    "objectID": "decisions/20231112-archive-projects.html#the-strategy",
+    "href": "decisions/20231112-archive-projects.html#the-strategy",
+    "title": "Proposed: Effective V-Sekai project archival strategy",
     "section": "",
-    "text": "Status: accepted \nDeciders: V-Sekai,fire,lyuma,\nTags: V-Sekai,\n\n\n\nWe want to import gltf audio emitters in Godot Engine.\n\n\n\nWe designed a gltf audio emitter extension with OMI.\n\n\n\n\nConvert gltf to a scene with AudioStreamPlayer3D\nconvert AudiostreamPlayer3D to gltf\nPublish to the Godot Engine 4.0 asset library\n\n\n\n\n\nAudio emitters.\n\n\n\n\n\nWork needs to be done to implement omi audio.\n\n\n\n\n\nOption: The current status.\nRejection Reason: Unable to load audio from artwork.\n\n\n\n\nNot a few lines of code.\n\n\n\nI proposed the idea and people at OMI are starting to move on.\n\n\n\n\nhttps://github.com/omigroup/gltf-extensions/pull/1\n\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "The proposed strategy includes:\n\nMaintaining online projects: If a project is hosted online, doesn’t necessitate upkeep and isn’t financially burdensome, it’s best to keep it live for easy future reference.\nStructuring offline projects: For those projects that aren’t feasible to keep online, store them in your local file system. Establish a main folder with yearly subfolders for systematic organization.\nCapturing screenshots: Screenshots serve as a quick visual reference of your project without the need to set it up again.\nCreating screen recordings: For a more comprehensive record, consider creating a screen recording of your project—this not only captures the visual aspect but also records any audio commentary you might provide.\nIncorporating a README: Include a README file that outlines the purpose of the project, its creation and abandonment dates, contributors, and instructions to get it up and running again. This provides essential information about the project at a glance.\nSecuring the database: In cases where projects lack a database dump, all the actual content could be lost. Execute a sqldump or use the export functionality your database offers to create a backup alongside your files. This ensures data preservation.\nRetaining generated assets: When utilizing static site generators, include the directory containing the compiled HTML, CSS & JS in the archive. This allows you to easily browse the complete website by simply running a static file server.\nArchiving on the Internet Archive: If the platform hosting your content isn’t owned by you (for instance, you’re publishing to Discord or Github), consider saving your data to the Archive.org. This adds an extra level of security for preserving your projects."
   },
   {
-    "objectID": "decisions/20220118-convert-gltf-to-a-scene.html#context-and-problem-statement",
-    "href": "decisions/20220118-convert-gltf-to-a-scene.html#context-and-problem-statement",
-    "title": "Accepted: Convert gltf to a scene with AudioStreamPlayer3D, convert AudiostreamPlayer3D to gltf and expose usability.",
+    "objectID": "decisions/20231112-archive-projects.html#the-upside",
+    "href": "decisions/20231112-archive-projects.html#the-upside",
+    "title": "Proposed: Effective V-Sekai project archival strategy",
     "section": "",
-    "text": "We want to import gltf audio emitters in Godot Engine."
+    "text": "This strategy will ensure that all V-Sekai projects are well-documented and easily accessible in the future. It will also help in preserving the history and evolution of V-Sekai projects over time."
   },
   {
-    "objectID": "decisions/20220118-convert-gltf-to-a-scene.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20220118-convert-gltf-to-a-scene.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Accepted: Convert gltf to a scene with AudioStreamPlayer3D, convert AudiostreamPlayer3D to gltf and expose usability.",
+    "objectID": "decisions/20231112-archive-projects.html#the-downside",
+    "href": "decisions/20231112-archive-projects.html#the-downside",
+    "title": "Proposed: Effective V-Sekai project archival strategy",
     "section": "",
-    "text": "We designed a gltf audio emitter extension with OMI."
+    "text": "The process might be time-consuming and require regular updates and maintenance."
   },
   {
-    "objectID": "decisions/20220118-convert-gltf-to-a-scene.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20220118-convert-gltf-to-a-scene.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Accepted: Convert gltf to a scene with AudioStreamPlayer3D, convert AudiostreamPlayer3D to gltf and expose usability.",
+    "objectID": "decisions/20231112-archive-projects.html#the-road-not-taken",
+    "href": "decisions/20231112-archive-projects.html#the-road-not-taken",
+    "title": "Proposed: Effective V-Sekai project archival strategy",
     "section": "",
-    "text": "Convert gltf to a scene with AudioStreamPlayer3D\nconvert AudiostreamPlayer3D to gltf\nPublish to the Godot Engine 4.0 asset library"
+    "text": "An alternative could be to use a cloud-based storage service for archiving projects. However, this might not provide the same level of organization and accessibility as the proposed strategy."
   },
   {
-    "objectID": "decisions/20220118-convert-gltf-to-a-scene.html#positive-consequences",
-    "href": "decisions/20220118-convert-gltf-to-a-scene.html#positive-consequences",
-    "title": "Accepted: Convert gltf to a scene with AudioStreamPlayer3D, convert AudiostreamPlayer3D to gltf and expose usability.",
+    "objectID": "decisions/20231112-archive-projects.html#the-infrequent-use-case",
+    "href": "decisions/20231112-archive-projects.html#the-infrequent-use-case",
+    "title": "Proposed: Effective V-Sekai project archival strategy",
     "section": "",
-    "text": "Audio emitters."
+    "text": "In cases where a project was short-lived or did not have significant impact, it might be decided to not include it in the archive."
   },
   {
-    "objectID": "decisions/20220118-convert-gltf-to-a-scene.html#negative-consequences",
-    "href": "decisions/20220118-convert-gltf-to-a-scene.html#negative-consequences",
-    "title": "Accepted: Convert gltf to a scene with AudioStreamPlayer3D, convert AudiostreamPlayer3D to gltf and expose usability.",
+    "objectID": "decisions/20231112-archive-projects.html#in-core-and-done-by-us",
+    "href": "decisions/20231112-archive-projects.html#in-core-and-done-by-us",
+    "title": "Proposed: Effective V-Sekai project archival strategy",
     "section": "",
-    "text": "Work needs to be done to implement omi audio."
+    "text": "Yes, this strategy should be implemented by the V-Sekai team as it directly affects the organization and preservation of their projects."
   },
   {
-    "objectID": "decisions/20220118-convert-gltf-to-a-scene.html#option-graveyard",
-    "href": "decisions/20220118-convert-gltf-to-a-scene.html#option-graveyard",
-    "title": "Accepted: Convert gltf to a scene with AudioStreamPlayer3D, convert AudiostreamPlayer3D to gltf and expose usability.",
+    "objectID": "decisions/20231112-archive-projects.html#further-reading",
+    "href": "decisions/20231112-archive-projects.html#further-reading",
+    "title": "Proposed: Effective V-Sekai project archival strategy",
     "section": "",
-    "text": "Option: The current status.\nRejection Reason: Unable to load audio from artwork."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\narne.me/articles/archive-your-old-projects\n\nThis article was assisted by AI assistant Aria."
   },
   {
-    "objectID": "decisions/20220118-convert-gltf-to-a-scene.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20220118-convert-gltf-to-a-scene.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Accepted: Convert gltf to a scene with AudioStreamPlayer3D, convert AudiostreamPlayer3D to gltf and expose usability.",
+    "objectID": "decisions/20230630-vsekai-goal-meeting.html",
+    "href": "decisions/20230630-vsekai-goal-meeting.html",
+    "title": "Accepted: V-Sekai Meeting - Friday, June 30, 2023",
     "section": "",
-    "text": "Not a few lines of code."
+    "text": "Original pad (90 day expiration): https://pad.sfconservancy.org/p/v-sekai-goals-meet-2023-06-30.md /timeslider#937\n\n\nMeeting goal: determine what we can feasibly build and what we can enable others to build.\n\n\n\n\nOptimally piggybacking on systems others have built / are maintaining.\nBuild things we would want to use\n\n\n\n\n\n\n\nScene loading support\nWorld hosting (network protocol)\nInstancing: Holepunching (users host?) and relay system and Multi-instance server system?\n\n\n\n\n\nAvatar support\nAvatar animation system\nVoIP (voice communication)\nIK synchronization and other player / avatar synchronization\nObject parenting support (chairs)\n\n\n\n\n\nInteractive elements\nGrabbable objects\nButtons\nPhysics\n\n\n\n\n\nDoodling (with a builtin script to save to a file)\nCameras (take a picture - screenshot?)\nMirrors + camera\nVideo player (static + playback of videos without a duration aka live) libvlc or ffmpeg\nLocal API (http OR jsonrpc OR local pipe OR OSC etc.) for Extending the Platform\n\nAllow users to write scripts and plugins for V-Sekai\nOr allow a local user to write custom GDScript into V-Sekai\nAPI to create an object.\nDetermine RPCs or functions to expose)\n\n\n\n\n\n\n\nNeeds API or scripting language.\n\n\n\n\n\nVRM import (avatars)\nGodot editor\nWorld creation\nUploading / sharing content items to an inventory.\n\n\n\n\n\nScreen sharing (OBS)\nModeling and 3D Creation (Blender)\n\n\n\n\n\nText chat\nCollaboration features / meeting spaces\n\nDoodling\n3D doodling/modeling tools sketch\nSaving and loading of content at runtime\n\nSupport for proprietary video hosting websites\n\n\n\n\n\nV-Sekai"
   },
   {
-    "objectID": "decisions/20220118-convert-gltf-to-a-scene.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20220118-convert-gltf-to-a-scene.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Accepted: Convert gltf to a scene with AudioStreamPlayer3D, convert AudiostreamPlayer3D to gltf and expose usability.",
+    "objectID": "decisions/20230630-vsekai-goal-meeting.html#context-and-problem-statement",
+    "href": "decisions/20230630-vsekai-goal-meeting.html#context-and-problem-statement",
+    "title": "Accepted: V-Sekai Meeting - Friday, June 30, 2023",
     "section": "",
-    "text": "I proposed the idea and people at OMI are starting to move on."
+    "text": "Meeting goal: determine what we can feasibly build and what we can enable others to build."
   },
   {
-    "objectID": "decisions/20220118-convert-gltf-to-a-scene.html#references",
-    "href": "decisions/20220118-convert-gltf-to-a-scene.html#references",
-    "title": "Accepted: Convert gltf to a scene with AudioStreamPlayer3D, convert AudiostreamPlayer3D to gltf and expose usability.",
+    "objectID": "decisions/20230630-vsekai-goal-meeting.html#principles",
+    "href": "decisions/20230630-vsekai-goal-meeting.html#principles",
+    "title": "Accepted: V-Sekai Meeting - Friday, June 30, 2023",
     "section": "",
-    "text": "https://github.com/omigroup/gltf-extensions/pull/1"
+    "text": "Optimally piggybacking on systems others have built / are maintaining.\nBuild things we would want to use"
   },
   {
-    "objectID": "decisions/20220118-convert-gltf-to-a-scene.html#derivative-license",
-    "href": "decisions/20220118-convert-gltf-to-a-scene.html#derivative-license",
-    "title": "Accepted: Convert gltf to a scene with AudioStreamPlayer3D, convert AudiostreamPlayer3D to gltf and expose usability.",
+    "objectID": "decisions/20230630-vsekai-goal-meeting.html#foundational-runtime-features-provided-by-the-platform",
+    "href": "decisions/20230630-vsekai-goal-meeting.html#foundational-runtime-features-provided-by-the-platform",
+    "title": "Accepted: V-Sekai Meeting - Friday, June 30, 2023",
     "section": "",
-    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Scene loading support\nWorld hosting (network protocol)\nInstancing: Holepunching (users host?) and relay system and Multi-instance server system?\n\n\n\n\n\nAvatar support\nAvatar animation system\nVoIP (voice communication)\nIK synchronization and other player / avatar synchronization\nObject parenting support (chairs)\n\n\n\n\n\nInteractive elements\nGrabbable objects\nButtons\nPhysics\n\n\n\n\n\nDoodling (with a builtin script to save to a file)\nCameras (take a picture - screenshot?)\nMirrors + camera\nVideo player (static + playback of videos without a duration aka live) libvlc or ffmpeg\nLocal API (http OR jsonrpc OR local pipe OR OSC etc.) for Extending the Platform\n\nAllow users to write scripts and plugins for V-Sekai\nOr allow a local user to write custom GDScript into V-Sekai\nAPI to create an object.\nDetermine RPCs or functions to expose)"
   },
   {
-    "objectID": "decisions/20231020-llama-cpp-mistral-npc.html",
-    "href": "decisions/20231020-llama-cpp-mistral-npc.html",
-    "title": "Proposed: Llama CPP AI Model NPC",
+    "objectID": "decisions/20230630-vsekai-goal-meeting.html#web-requests-http-or-websocket-to-servers",
+    "href": "decisions/20230630-vsekai-goal-meeting.html#web-requests-http-or-websocket-to-servers",
+    "title": "Accepted: V-Sekai Meeting - Friday, June 30, 2023",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, AI, NPC, Godot 4\n\n\n\n\nIn the realm of game development, creating engaging and dynamic Non-Player Characters (NPCs) is a challenging task. With advancements in AI, there’s an opportunity to leverage these technologies to enhance NPC interactions.\n\n\n\nThe challenge lies in effectively using various AI models to create the “brain” of an AI NPC in Godot 4. This involves generating realistic and contextually appropriate dialogs for the NPCs.\n\n\n\nThe strategy involves using a local GPT4All model for generating AI-based NPC dialog. The script includes several exported variables that can be set in the Godot editor, such as npc_background_directions, sample_npc_question_prompt, and sample_npc_prompt_response. These variables are used to configure the behavior of the AI dialog generation.\nKey functions include:\n\ncall_model(prompt): Calls the local model with a given prompt.\nset_model(new_model_name : String): Sets the model name.\n\n\n\n\nLeveraging AI for NPC dialog generation can lead to more dynamic and engaging gameplay. It allows for a wide range of responses and can adapt to different player inputs.\n\n\n\nAI models require significant computational resources and may not be suitable for all platforms. Additionally, ensuring the appropriateness and quality of generated dialogs can be challenging.\n\n\n\nTraditional methods of NPC dialog generation involve pre-scripted dialogs or simple decision trees. While these methods are less resource-intensive, they lack the dynamism and adaptability of AI-generated dialogs.\n\n\n\nIn games with minimal NPC interactions or where dialog is not a significant aspect of gameplay, the use of AI for dialog generation may not be necessary.\n\n\n\nYes, the implementation of this strategy is done by us in the core of our game development process.\n\n\n\n\nV-Sekai GitHub\nAI assists this article.\nAxolotl Mistral Example"
+    "text": "Needs API or scripting language."
   },
   {
-    "objectID": "decisions/20231020-llama-cpp-mistral-npc.html#metadata",
-    "href": "decisions/20231020-llama-cpp-mistral-npc.html#metadata",
-    "title": "Proposed: Llama CPP AI Model NPC",
+    "objectID": "decisions/20230630-vsekai-goal-meeting.html#foundational-static-content-creationsdk-features-in-the-editor",
+    "href": "decisions/20230630-vsekai-goal-meeting.html#foundational-static-content-creationsdk-features-in-the-editor",
+    "title": "Accepted: V-Sekai Meeting - Friday, June 30, 2023",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, AI, NPC, Godot 4"
+    "text": "VRM import (avatars)\nGodot editor\nWorld creation\nUploading / sharing content items to an inventory."
   },
   {
-    "objectID": "decisions/20231020-llama-cpp-mistral-npc.html#the-backdrop",
-    "href": "decisions/20231020-llama-cpp-mistral-npc.html#the-backdrop",
-    "title": "Proposed: Llama CPP AI Model NPC",
+    "objectID": "decisions/20230630-vsekai-goal-meeting.html#features-that-we-can-interface-with-third-parties",
+    "href": "decisions/20230630-vsekai-goal-meeting.html#features-that-we-can-interface-with-third-parties",
+    "title": "Accepted: V-Sekai Meeting - Friday, June 30, 2023",
     "section": "",
-    "text": "In the realm of game development, creating engaging and dynamic Non-Player Characters (NPCs) is a challenging task. With advancements in AI, there’s an opportunity to leverage these technologies to enhance NPC interactions."
+    "text": "Screen sharing (OBS)\nModeling and 3D Creation (Blender)"
   },
   {
-    "objectID": "decisions/20231020-llama-cpp-mistral-npc.html#the-challenge",
-    "href": "decisions/20231020-llama-cpp-mistral-npc.html#the-challenge",
-    "title": "Proposed: Llama CPP AI Model NPC",
+    "objectID": "decisions/20230630-vsekai-goal-meeting.html#features-that-we-can-enable-platform-developers-to-build",
+    "href": "decisions/20230630-vsekai-goal-meeting.html#features-that-we-can-enable-platform-developers-to-build",
+    "title": "Accepted: V-Sekai Meeting - Friday, June 30, 2023",
     "section": "",
-    "text": "The challenge lies in effectively using various AI models to create the “brain” of an AI NPC in Godot 4. This involves generating realistic and contextually appropriate dialogs for the NPCs."
+    "text": "Text chat\nCollaboration features / meeting spaces\n\nDoodling\n3D doodling/modeling tools sketch\nSaving and loading of content at runtime\n\nSupport for proprietary video hosting websites"
   },
   {
-    "objectID": "decisions/20231020-llama-cpp-mistral-npc.html#the-strategy",
-    "href": "decisions/20231020-llama-cpp-mistral-npc.html#the-strategy",
-    "title": "Proposed: Llama CPP AI Model NPC",
+    "objectID": "decisions/20230630-vsekai-goal-meeting.html#references",
+    "href": "decisions/20230630-vsekai-goal-meeting.html#references",
+    "title": "Accepted: V-Sekai Meeting - Friday, June 30, 2023",
     "section": "",
-    "text": "The strategy involves using a local GPT4All model for generating AI-based NPC dialog. The script includes several exported variables that can be set in the Godot editor, such as npc_background_directions, sample_npc_question_prompt, and sample_npc_prompt_response. These variables are used to configure the behavior of the AI dialog generation.\nKey functions include:\n\ncall_model(prompt): Calls the local model with a given prompt.\nset_model(new_model_name : String): Sets the model name."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20231020-llama-cpp-mistral-npc.html#the-upside",
-    "href": "decisions/20231020-llama-cpp-mistral-npc.html#the-upside",
-    "title": "Proposed: Llama CPP AI Model NPC",
+    "objectID": "decisions/20240424-reset-steamvr-controllers.html",
+    "href": "decisions/20240424-reset-steamvr-controllers.html",
+    "title": "Accepted: Prioritizing Valve Controllers Over Meta Quest 3 Controllers",
     "section": "",
-    "text": "Leveraging AI for NPC dialog generation can lead to more dynamic and engaging gameplay. It allows for a wide range of responses and can adapt to different player inputs."
+    "text": "We are considering the use of Quest 3 and Lighthouse tracked Valve Index controllers for our project when using playspace calibration.\n\n\n\nThe issue we face is that when a Meta Quest 3 is used, it takes over the controller priority. So we’re unable to open the steamvr menu.\n\n\n\nTo address this problem, we propose turning the SteamVR Index controller on and off. This action will prioritize the Valve controller over the Meta controller.\n\n\n\n\nEnsures optimal functionality of the Valve controller.\nPrevents interference from the Meta controller.\n\n\n\n\n\nMay need to be adjusted for different hardware configurations.\n\n\n\n\nWe could have chosen to let the Meta controller take priority, but this would not have been ideal for our specific needs.\n\n\n\nThis solution may not be necessary for users who do not use a Meta Quest 3.\n\n\n\nThis proposal has been developed and will be implemented by the V-Sekai development team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - The GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis proposal was assisted by AI assistant, Aria."
   },
   {
-    "objectID": "decisions/20231020-llama-cpp-mistral-npc.html#the-downside",
-    "href": "decisions/20231020-llama-cpp-mistral-npc.html#the-downside",
-    "title": "Proposed: Llama CPP AI Model NPC",
+    "objectID": "decisions/20240424-reset-steamvr-controllers.html#the-context",
+    "href": "decisions/20240424-reset-steamvr-controllers.html#the-context",
+    "title": "Accepted: Prioritizing Valve Controllers Over Meta Quest 3 Controllers",
     "section": "",
-    "text": "AI models require significant computational resources and may not be suitable for all platforms. Additionally, ensuring the appropriateness and quality of generated dialogs can be challenging."
+    "text": "We are considering the use of Quest 3 and Lighthouse tracked Valve Index controllers for our project when using playspace calibration."
   },
   {
-    "objectID": "decisions/20231020-llama-cpp-mistral-npc.html#the-road-not-taken",
-    "href": "decisions/20231020-llama-cpp-mistral-npc.html#the-road-not-taken",
-    "title": "Proposed: Llama CPP AI Model NPC",
+    "objectID": "decisions/20240424-reset-steamvr-controllers.html#the-problem-statement",
+    "href": "decisions/20240424-reset-steamvr-controllers.html#the-problem-statement",
+    "title": "Accepted: Prioritizing Valve Controllers Over Meta Quest 3 Controllers",
     "section": "",
-    "text": "Traditional methods of NPC dialog generation involve pre-scripted dialogs or simple decision trees. While these methods are less resource-intensive, they lack the dynamism and adaptability of AI-generated dialogs."
+    "text": "The issue we face is that when a Meta Quest 3 is used, it takes over the controller priority. So we’re unable to open the steamvr menu."
   },
   {
-    "objectID": "decisions/20231020-llama-cpp-mistral-npc.html#the-infrequent-use-case",
-    "href": "decisions/20231020-llama-cpp-mistral-npc.html#the-infrequent-use-case",
-    "title": "Proposed: Llama CPP AI Model NPC",
+    "objectID": "decisions/20240424-reset-steamvr-controllers.html#solution-proposal",
+    "href": "decisions/20240424-reset-steamvr-controllers.html#solution-proposal",
+    "title": "Accepted: Prioritizing Valve Controllers Over Meta Quest 3 Controllers",
     "section": "",
-    "text": "In games with minimal NPC interactions or where dialog is not a significant aspect of gameplay, the use of AI for dialog generation may not be necessary."
+    "text": "To address this problem, we propose turning the SteamVR Index controller on and off. This action will prioritize the Valve controller over the Meta controller."
   },
   {
-    "objectID": "decisions/20231020-llama-cpp-mistral-npc.html#in-core-and-done-by-us",
-    "href": "decisions/20231020-llama-cpp-mistral-npc.html#in-core-and-done-by-us",
-    "title": "Proposed: Llama CPP AI Model NPC",
+    "objectID": "decisions/20240424-reset-steamvr-controllers.html#the-benefits",
+    "href": "decisions/20240424-reset-steamvr-controllers.html#the-benefits",
+    "title": "Accepted: Prioritizing Valve Controllers Over Meta Quest 3 Controllers",
     "section": "",
-    "text": "Yes, the implementation of this strategy is done by us in the core of our game development process."
+    "text": "Ensures optimal functionality of the Valve controller.\nPrevents interference from the Meta controller."
   },
   {
-    "objectID": "decisions/20231020-llama-cpp-mistral-npc.html#further-reading",
-    "href": "decisions/20231020-llama-cpp-mistral-npc.html#further-reading",
-    "title": "Proposed: Llama CPP AI Model NPC",
+    "objectID": "decisions/20240424-reset-steamvr-controllers.html#the-downsides",
+    "href": "decisions/20240424-reset-steamvr-controllers.html#the-downsides",
+    "title": "Accepted: Prioritizing Valve Controllers Over Meta Quest 3 Controllers",
     "section": "",
-    "text": "V-Sekai GitHub\nAI assists this article.\nAxolotl Mistral Example"
+    "text": "May need to be adjusted for different hardware configurations."
   },
   {
-    "objectID": "decisions/20230521-audio-jitter-buffer-voip.html",
-    "href": "decisions/20230521-audio-jitter-buffer-voip.html",
-    "title": "Proposed: Improving Jitter-Buffer Implementation for Voice Chat in V-Sekai Projects",
+    "objectID": "decisions/20240424-reset-steamvr-controllers.html#the-road-not-taken",
+    "href": "decisions/20240424-reset-steamvr-controllers.html#the-road-not-taken",
+    "title": "Accepted: Prioritizing Valve Controllers Over Meta Quest 3 Controllers",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai, lyuma, Dreadpon,\nTags: V-Sekai, GPT-4, jitter-buffer, voice-chat, godot-speech, audio-quality, adaptive-jitter-buffer, Speex\n\n\n\n\nDreadpon is working on a voice chat solution inside Godot 3.5.2 and found the jitter-buffer implementation in godot-speech to be rudimentary. They are looking for an ideal jitter-buffer implementation that can handle both slowing down and speeding up played audio.\n\n\n\nUse the adaptive jitter buffer from the Speex source code as a starting point, with modifications to address its limitations:\n\nCapture packets as they are being dropped from the jitter buffer.\nEnsure all captured packets are played.\nImplement a playback buffer to speed up the audio when necessary.\n\n\n\n\n\nIntegrate the adaptive jitter buffer from the Speex source code into the godot-speech project.\nModify the jitter buffer to capture dropped packets and store them in a separate buffer.\nImplement a playback buffer that accelerates audio playback when more audio packets are available.\nTest the new implementation to ensure it handles jitter compensation effectively.\n\n\n\n\n\nImproved jitter compensation in the voice chat solution.\nBetter handling of packet drops and audio acceleration.\nEnhanced overall audio quality in the voice chat system.\n\n\n\n\n\nAdditional complexity in the godot-speech codebase.\nPotential performance impact due to the added buffering mechanism.\n\n\n\n\n\nContinue using the current rudimentary jitter-buffer implementation in godot-speech.\n\n\n\n\nNo, this enhancement is essential for a high-quality voice chat solution and cannot be easily worked around with a few lines of script.\n\n\n\nYes, improving the jitter-buffer implementation is crucial for providing a reliable and high-quality voice chat experience in V-Sekai projects.\n\n\n\n\nV-Sekai\ngodot-speech\nSpeex"
+    "text": "We could have chosen to let the Meta controller take priority, but this would not have been ideal for our specific needs."
   },
   {
-    "objectID": "decisions/20230521-audio-jitter-buffer-voip.html#metadata",
-    "href": "decisions/20230521-audio-jitter-buffer-voip.html#metadata",
-    "title": "Proposed: Improving Jitter-Buffer Implementation for Voice Chat in V-Sekai Projects",
+    "objectID": "decisions/20240424-reset-steamvr-controllers.html#the-infrequent-use-case",
+    "href": "decisions/20240424-reset-steamvr-controllers.html#the-infrequent-use-case",
+    "title": "Accepted: Prioritizing Valve Controllers Over Meta Quest 3 Controllers",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai, lyuma, Dreadpon,\nTags: V-Sekai, GPT-4, jitter-buffer, voice-chat, godot-speech, audio-quality, adaptive-jitter-buffer, Speex"
+    "text": "This solution may not be necessary for users who do not use a Meta Quest 3."
   },
   {
-    "objectID": "decisions/20230521-audio-jitter-buffer-voip.html#context-and-problem-statement",
-    "href": "decisions/20230521-audio-jitter-buffer-voip.html#context-and-problem-statement",
-    "title": "Proposed: Improving Jitter-Buffer Implementation for Voice Chat in V-Sekai Projects",
+    "objectID": "decisions/20240424-reset-steamvr-controllers.html#in-core-and-done-by-us",
+    "href": "decisions/20240424-reset-steamvr-controllers.html#in-core-and-done-by-us",
+    "title": "Accepted: Prioritizing Valve Controllers Over Meta Quest 3 Controllers",
     "section": "",
-    "text": "Dreadpon is working on a voice chat solution inside Godot 3.5.2 and found the jitter-buffer implementation in godot-speech to be rudimentary. They are looking for an ideal jitter-buffer implementation that can handle both slowing down and speeding up played audio."
+    "text": "This proposal has been developed and will be implemented by the V-Sekai development team."
   },
   {
-    "objectID": "decisions/20230521-audio-jitter-buffer-voip.html#proposed-solution",
-    "href": "decisions/20230521-audio-jitter-buffer-voip.html#proposed-solution",
-    "title": "Proposed: Improving Jitter-Buffer Implementation for Voice Chat in V-Sekai Projects",
+    "objectID": "decisions/20240424-reset-steamvr-controllers.html#status",
+    "href": "decisions/20240424-reset-steamvr-controllers.html#status",
+    "title": "Accepted: Prioritizing Valve Controllers Over Meta Quest 3 Controllers",
     "section": "",
-    "text": "Use the adaptive jitter buffer from the Speex source code as a starting point, with modifications to address its limitations:\n\nCapture packets as they are being dropped from the jitter buffer.\nEnsure all captured packets are played.\nImplement a playback buffer to speed up the audio when necessary."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20230521-audio-jitter-buffer-voip.html#implementation",
-    "href": "decisions/20230521-audio-jitter-buffer-voip.html#implementation",
-    "title": "Proposed: Improving Jitter-Buffer Implementation for Voice Chat in V-Sekai Projects",
+    "objectID": "decisions/20240424-reset-steamvr-controllers.html#decision-makers",
+    "href": "decisions/20240424-reset-steamvr-controllers.html#decision-makers",
+    "title": "Accepted: Prioritizing Valve Controllers Over Meta Quest 3 Controllers",
     "section": "",
-    "text": "Integrate the adaptive jitter buffer from the Speex source code into the godot-speech project.\nModify the jitter buffer to capture dropped packets and store them in a separate buffer.\nImplement a playback buffer that accelerates audio playback when more audio packets are available.\nTest the new implementation to ensure it handles jitter compensation effectively."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20230521-audio-jitter-buffer-voip.html#positive-consequences",
-    "href": "decisions/20230521-audio-jitter-buffer-voip.html#positive-consequences",
-    "title": "Proposed: Improving Jitter-Buffer Implementation for Voice Chat in V-Sekai Projects",
+    "objectID": "decisions/20240424-reset-steamvr-controllers.html#tags",
+    "href": "decisions/20240424-reset-steamvr-controllers.html#tags",
+    "title": "Accepted: Prioritizing Valve Controllers Over Meta Quest 3 Controllers",
     "section": "",
-    "text": "Improved jitter compensation in the voice chat solution.\nBetter handling of packet drops and audio acceleration.\nEnhanced overall audio quality in the voice chat system."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20230521-audio-jitter-buffer-voip.html#negative-consequences",
-    "href": "decisions/20230521-audio-jitter-buffer-voip.html#negative-consequences",
-    "title": "Proposed: Improving Jitter-Buffer Implementation for Voice Chat in V-Sekai Projects",
+    "objectID": "decisions/20240424-reset-steamvr-controllers.html#further-reading",
+    "href": "decisions/20240424-reset-steamvr-controllers.html#further-reading",
+    "title": "Accepted: Prioritizing Valve Controllers Over Meta Quest 3 Controllers",
     "section": "",
-    "text": "Additional complexity in the godot-speech codebase.\nPotential performance impact due to the added buffering mechanism."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - The GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis proposal was assisted by AI assistant, Aria."
   },
   {
-    "objectID": "decisions/20230521-audio-jitter-buffer-voip.html#option-graveyard",
-    "href": "decisions/20230521-audio-jitter-buffer-voip.html#option-graveyard",
-    "title": "Proposed: Improving Jitter-Buffer Implementation for Voice Chat in V-Sekai Projects",
+    "objectID": "decisions/20230719-pose-kusudama-constraints-in-vr.html",
+    "href": "decisions/20230719-pose-kusudama-constraints-in-vr.html",
+    "title": "Proposed: Enhancing the Many Bone IK Configuration",
     "section": "",
-    "text": "Continue using the current rudimentary jitter-buffer implementation in godot-speech."
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, VR, Game Development\n\n\n\n\nWe have identified a limitation in the V-Sekai platform where there are too many variables to pose the kusudama constraints on the desktop. We propose to overcome this limitation by introducing a VR mode.\n\n\n\nOur solution involves creating a VR mode specifically for posing Many Bone IK kusudama constraints. The steps for implementation are as follows:\n\nTake an off the shelf VR controller.\nTake an off the shelf multiplayer functionality.\nDevelop a tool selection ui. Collaborate with guillefix.\nAdjust the kusudama constraint attributes to match posing.\nSave attributes.\n\n\n\nImagine you have a ball. There are two ways you can move it:\n\nTwist: Like spinning a globe on its stand.\nSwing: Like moving your finger from one spot to another on the ball.\n\nThink of a Kusudama (a type of origami that forms a sphere) as an example for the swing movement. The pieces of paper move just like your finger would on the ball.\n\n\n\n\n\nInvestigate Saracen’s VR networking prototype.\nRebuild character posing without tracking the physical sensors\nApply Many Bone IK tracking\nRotation swing (10x Vector4)\nRotation twist (From and range)\nAdjust for quality\nComplete configuration\n\nAssigning physical sensors to IK points is non-goal.\n\n\n\n\nDesktop Mode Enhancement: Initially, we considered enhancing the desktop mode to handle the kusudama constraints better. However, this option was discarded due to the inherent limitations of the desktop interface for such complex interactions.\nUse of External Tools: Another option was to use external tools or plugins specifically designed for handling Many Bone IK kusudama constraints. This option was rejected because it would require users to learn and manage additional software, which could lead to a fragmented user experience.\nSimplified Kusudama Constraints: We also thought about simplifying the kusudama constraints to make them more manageable on the desktop. But this option was discarded as it would limit the capabilities and flexibility that our platform currently offers.\nAutomated Posing: An automated system for posing the kusudama constraints was also considered. However, this option was rejected because it would take away control from the users, potentially leading to less satisfactory results.\nTutorials and Guides: Providing extensive tutorials and guides to help users navigate the complexity of posing kusudama constraints on the desktop was another option. This was discarded because it doesn’t address the core issue - the difficulty of managing these constraints on a desktop interface.\n\n\n\n\n\nIncreased complexity in game development.\nPotential need for more resources (time, manpower, etc.) for implementation and testing.\n\n\n\n\nThis section is reserved for options considered but rejected.\n\n\n\nPosing the avatar is the first interaction a user has when entering our virtual world, V-Sekai. This underlines the necessity of investing in this enhancement to ensure a seamless and engaging user experience right from their first interaction with our platform.\n\n\n\nPose quality is crucial to us. As the creators of V-Sekai, we have an unparalleled understanding of our platform’s limitations and potential improvements. This insight puts us in a unique position to enhance the pose quality in a way that aligns with our users’ needs and expectations. Therefore, it is essential that we undertake this enhancement.\n\n\n\n\nV-Sekai"
   },
   {
-    "objectID": "decisions/20230521-audio-jitter-buffer-voip.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230521-audio-jitter-buffer-voip.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Improving Jitter-Buffer Implementation for Voice Chat in V-Sekai Projects",
+    "objectID": "decisions/20230719-pose-kusudama-constraints-in-vr.html#metadata",
+    "href": "decisions/20230719-pose-kusudama-constraints-in-vr.html#metadata",
+    "title": "Proposed: Enhancing the Many Bone IK Configuration",
     "section": "",
-    "text": "No, this enhancement is essential for a high-quality voice chat solution and cannot be easily worked around with a few lines of script."
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, VR, Game Development"
   },
   {
-    "objectID": "decisions/20230521-audio-jitter-buffer-voip.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230521-audio-jitter-buffer-voip.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Improving Jitter-Buffer Implementation for Voice Chat in V-Sekai Projects",
+    "objectID": "decisions/20230719-pose-kusudama-constraints-in-vr.html#context-and-problem-statement",
+    "href": "decisions/20230719-pose-kusudama-constraints-in-vr.html#context-and-problem-statement",
+    "title": "Proposed: Enhancing the Many Bone IK Configuration",
     "section": "",
-    "text": "Yes, improving the jitter-buffer implementation is crucial for providing a reliable and high-quality voice chat experience in V-Sekai projects."
+    "text": "We have identified a limitation in the V-Sekai platform where there are too many variables to pose the kusudama constraints on the desktop. We propose to overcome this limitation by introducing a VR mode."
   },
   {
-    "objectID": "decisions/20230521-audio-jitter-buffer-voip.html#references",
-    "href": "decisions/20230521-audio-jitter-buffer-voip.html#references",
-    "title": "Proposed: Improving Jitter-Buffer Implementation for Voice Chat in V-Sekai Projects",
+    "objectID": "decisions/20230719-pose-kusudama-constraints-in-vr.html#proposed-solution",
+    "href": "decisions/20230719-pose-kusudama-constraints-in-vr.html#proposed-solution",
+    "title": "Proposed: Enhancing the Many Bone IK Configuration",
     "section": "",
-    "text": "V-Sekai\ngodot-speech\nSpeex"
+    "text": "Our solution involves creating a VR mode specifically for posing Many Bone IK kusudama constraints. The steps for implementation are as follows:\n\nTake an off the shelf VR controller.\nTake an off the shelf multiplayer functionality.\nDevelop a tool selection ui. Collaborate with guillefix.\nAdjust the kusudama constraint attributes to match posing.\nSave attributes.\n\n\n\nImagine you have a ball. There are two ways you can move it:\n\nTwist: Like spinning a globe on its stand.\nSwing: Like moving your finger from one spot to another on the ball.\n\nThink of a Kusudama (a type of origami that forms a sphere) as an example for the swing movement. The pieces of paper move just like your finger would on the ball."
   },
   {
-    "objectID": "decisions/20220202-gltf-extensions-for-interoperability.html",
-    "href": "decisions/20220202-gltf-extensions-for-interoperability.html",
-    "title": "Accepted: Interoperability between platforms using gltf extensions",
+    "objectID": "decisions/20230719-pose-kusudama-constraints-in-vr.html#implementation",
+    "href": "decisions/20230719-pose-kusudama-constraints-in-vr.html#implementation",
+    "title": "Proposed: Enhancing the Many Bone IK Configuration",
     "section": "",
-    "text": "Status: accepted\nDeciders: V-Sekai,fire,lyuma,humbletim,codefloof,\nTags: V-Sekai,\n\n\n\nBuild Gltf extensions. Why build incomplete Gltf extensions with limited usefulness without the complete package? We should be making for creators, not ourselves.\n\n\n\nhumbletim, codefloof, iFire and lyuma debated the meaningfulness of building Gltf extensions.\niFire constructed an argument we are making a Gltf container for the metaverse. A metaverse container where each part is separated because of limited engineering bandwidth. We brought up the point Gltf isn’t unknown and is unknown.\nLyuma can’t entirely agree that Gltf extensions are “separated.” Gltf extensions are independent extensions that are good from an engineering perspective.\nLyuma reaffirmed his suspicions that OMI standards are not so valuable in isolation. Humbletim raised valid concerns that the Unity work had not progressed, and Mozilla Hubs had not merged the OMI audio emitter code. We may need Unity platforms and Mozilla Hubs to bootstrap the ecosystem, but tools like Gltf transform could sidestep it.\niFire also constructed a strawman of how operating inside a platform is seamless, and transferring between platforms is like pulling teeth. Still, a strawman isn’t something that helped facilitate the discussion so Lyuma may have misunderstood that part. iFire described the unity package vs others. Lyuma agrees that this is valid; other formats could be deemed “interoperable,” more expressive than Gltf.\nIn Lyuma’s mind, it’s a fair X point that already exists. So why work on Y? Why does Gltf 3d format if we have Fbx 3d format etc.?\nLyuma doesn’t think we need to assume that there must be only one standard.\nWe’re trying to see if we can do better by working together than taking some existing closed format and using it verbatim.\nOMI work is valid even if a unity package standard exists. We don’t need to be the only standard.\niFire didn’t exhaust all the details of the point, but we can make a Gltf transform for as many standards we can catalog.\n\n\n\nWe will generate github actions templates using the same jsonnet we use for GoCD.\n\n\n\n\nInteroperating between platforms.\n\n\n\n\n\nEasy to ignore users.\n\n\n\n\n\nOption: Keep the status quo, which is having separate platforms.\nRejection Reason: We want interoperability at OMI.\n\n\n\n\nIt is not only a few lines of code.\n\n\n\nWe want to maintain it to encourage developers and as the publisher of the platform it is our responsibility.\n\n\n\n\nhttps://omigroup.org/\n\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Investigate Saracen’s VR networking prototype.\nRebuild character posing without tracking the physical sensors\nApply Many Bone IK tracking\nRotation swing (10x Vector4)\nRotation twist (From and range)\nAdjust for quality\nComplete configuration\n\nAssigning physical sensors to IK points is non-goal."
   },
   {
-    "objectID": "decisions/20220202-gltf-extensions-for-interoperability.html#context-and-problem-statement",
-    "href": "decisions/20220202-gltf-extensions-for-interoperability.html#context-and-problem-statement",
-    "title": "Accepted: Interoperability between platforms using gltf extensions",
+    "objectID": "decisions/20230719-pose-kusudama-constraints-in-vr.html#option-graveyard",
+    "href": "decisions/20230719-pose-kusudama-constraints-in-vr.html#option-graveyard",
+    "title": "Proposed: Enhancing the Many Bone IK Configuration",
     "section": "",
-    "text": "Build Gltf extensions. Why build incomplete Gltf extensions with limited usefulness without the complete package? We should be making for creators, not ourselves."
+    "text": "Desktop Mode Enhancement: Initially, we considered enhancing the desktop mode to handle the kusudama constraints better. However, this option was discarded due to the inherent limitations of the desktop interface for such complex interactions.\nUse of External Tools: Another option was to use external tools or plugins specifically designed for handling Many Bone IK kusudama constraints. This option was rejected because it would require users to learn and manage additional software, which could lead to a fragmented user experience.\nSimplified Kusudama Constraints: We also thought about simplifying the kusudama constraints to make them more manageable on the desktop. But this option was discarded as it would limit the capabilities and flexibility that our platform currently offers.\nAutomated Posing: An automated system for posing the kusudama constraints was also considered. However, this option was rejected because it would take away control from the users, potentially leading to less satisfactory results.\nTutorials and Guides: Providing extensive tutorials and guides to help users navigate the complexity of posing kusudama constraints on the desktop was another option. This was discarded because it doesn’t address the core issue - the difficulty of managing these constraints on a desktop interface."
   },
   {
-    "objectID": "decisions/20220202-gltf-extensions-for-interoperability.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20220202-gltf-extensions-for-interoperability.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Accepted: Interoperability between platforms using gltf extensions",
+    "objectID": "decisions/20230719-pose-kusudama-constraints-in-vr.html#negative-consequences",
+    "href": "decisions/20230719-pose-kusudama-constraints-in-vr.html#negative-consequences",
+    "title": "Proposed: Enhancing the Many Bone IK Configuration",
     "section": "",
-    "text": "humbletim, codefloof, iFire and lyuma debated the meaningfulness of building Gltf extensions.\niFire constructed an argument we are making a Gltf container for the metaverse. A metaverse container where each part is separated because of limited engineering bandwidth. We brought up the point Gltf isn’t unknown and is unknown.\nLyuma can’t entirely agree that Gltf extensions are “separated.” Gltf extensions are independent extensions that are good from an engineering perspective.\nLyuma reaffirmed his suspicions that OMI standards are not so valuable in isolation. Humbletim raised valid concerns that the Unity work had not progressed, and Mozilla Hubs had not merged the OMI audio emitter code. We may need Unity platforms and Mozilla Hubs to bootstrap the ecosystem, but tools like Gltf transform could sidestep it.\niFire also constructed a strawman of how operating inside a platform is seamless, and transferring between platforms is like pulling teeth. Still, a strawman isn’t something that helped facilitate the discussion so Lyuma may have misunderstood that part. iFire described the unity package vs others. Lyuma agrees that this is valid; other formats could be deemed “interoperable,” more expressive than Gltf.\nIn Lyuma’s mind, it’s a fair X point that already exists. So why work on Y? Why does Gltf 3d format if we have Fbx 3d format etc.?\nLyuma doesn’t think we need to assume that there must be only one standard.\nWe’re trying to see if we can do better by working together than taking some existing closed format and using it verbatim.\nOMI work is valid even if a unity package standard exists. We don’t need to be the only standard.\niFire didn’t exhaust all the details of the point, but we can make a Gltf transform for as many standards we can catalog."
+    "text": "Increased complexity in game development.\nPotential need for more resources (time, manpower, etc.) for implementation and testing."
   },
   {
-    "objectID": "decisions/20220202-gltf-extensions-for-interoperability.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20220202-gltf-extensions-for-interoperability.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Accepted: Interoperability between platforms using gltf extensions",
+    "objectID": "decisions/20230719-pose-kusudama-constraints-in-vr.html#option-graveyard-1",
+    "href": "decisions/20230719-pose-kusudama-constraints-in-vr.html#option-graveyard-1",
+    "title": "Proposed: Enhancing the Many Bone IK Configuration",
     "section": "",
-    "text": "We will generate github actions templates using the same jsonnet we use for GoCD."
+    "text": "This section is reserved for options considered but rejected."
   },
   {
-    "objectID": "decisions/20220202-gltf-extensions-for-interoperability.html#positive-consequences",
-    "href": "decisions/20220202-gltf-extensions-for-interoperability.html#positive-consequences",
-    "title": "Accepted: Interoperability between platforms using gltf extensions",
+    "objectID": "decisions/20230719-pose-kusudama-constraints-in-vr.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230719-pose-kusudama-constraints-in-vr.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Enhancing the Many Bone IK Configuration",
     "section": "",
-    "text": "Interoperating between platforms."
+    "text": "Posing the avatar is the first interaction a user has when entering our virtual world, V-Sekai. This underlines the necessity of investing in this enhancement to ensure a seamless and engaging user experience right from their first interaction with our platform."
   },
   {
-    "objectID": "decisions/20220202-gltf-extensions-for-interoperability.html#negative-consequences",
-    "href": "decisions/20220202-gltf-extensions-for-interoperability.html#negative-consequences",
-    "title": "Accepted: Interoperability between platforms using gltf extensions",
+    "objectID": "decisions/20230719-pose-kusudama-constraints-in-vr.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230719-pose-kusudama-constraints-in-vr.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Enhancing the Many Bone IK Configuration",
     "section": "",
-    "text": "Easy to ignore users."
+    "text": "Pose quality is crucial to us. As the creators of V-Sekai, we have an unparalleled understanding of our platform’s limitations and potential improvements. This insight puts us in a unique position to enhance the pose quality in a way that aligns with our users’ needs and expectations. Therefore, it is essential that we undertake this enhancement."
   },
   {
-    "objectID": "decisions/20220202-gltf-extensions-for-interoperability.html#option-graveyard",
-    "href": "decisions/20220202-gltf-extensions-for-interoperability.html#option-graveyard",
-    "title": "Accepted: Interoperability between platforms using gltf extensions",
+    "objectID": "decisions/20230719-pose-kusudama-constraints-in-vr.html#references",
+    "href": "decisions/20230719-pose-kusudama-constraints-in-vr.html#references",
+    "title": "Proposed: Enhancing the Many Bone IK Configuration",
     "section": "",
-    "text": "Option: Keep the status quo, which is having separate platforms.\nRejection Reason: We want interoperability at OMI."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20220202-gltf-extensions-for-interoperability.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20220202-gltf-extensions-for-interoperability.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Accepted: Interoperability between platforms using gltf extensions",
+    "objectID": "decisions/20231027-drawing-concept-to-blockout.html",
+    "href": "decisions/20231027-drawing-concept-to-blockout.html",
+    "title": "Proposed: Drawing Concept to Blockout",
     "section": "",
-    "text": "It is not only a few lines of code."
+    "text": "Status: Proposed\nDeciders: V-Sekai, fire\nTags: V-Sekai\n\n\n\n\nThe goal is to add more finished vrms to V-Sekai.\n\n\n\nThe task at hand is to create some concept art for an existing VRoid character model.\n\n\n\nHere’s the proposed strategy:\n\nStart with grayscale outlines to focus on shapes rather than color.\nUse a off-white background, an outline color, a shadow color and a solid color.\nFocus on the overall shapes and silhouette first before adding details.\n\n\n\n\nThis process will help nail down the overall look and feel before getting distracted by details and color. Starting with outlines and simple shapes will make it easier to iterate quickly.\n\n\n\nThe downside could be that focusing too much on the overall shape might lead to neglecting the finer details which are also important in character design. Also, this approach may not work as effectively for complex designs.\n\n\n\nAn alternative approach could have been to start with detailed sketches instead of broad shapes. This would allow for more detail early on but could potentially slow down the iteration process.\n\n\n\nThis method might not be suitable if the character design is already well established and does not require significant changes to its overall shape and structure.\n\n\n\nYes, this is a core part of our design process and is done by us.\n\n\n\nFor more information, you can visit the following links:\n\nV-Sekai\nAI assists this article."
   },
   {
-    "objectID": "decisions/20220202-gltf-extensions-for-interoperability.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20220202-gltf-extensions-for-interoperability.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Accepted: Interoperability between platforms using gltf extensions",
+    "objectID": "decisions/20231027-drawing-concept-to-blockout.html#metadata",
+    "href": "decisions/20231027-drawing-concept-to-blockout.html#metadata",
+    "title": "Proposed: Drawing Concept to Blockout",
     "section": "",
-    "text": "We want to maintain it to encourage developers and as the publisher of the platform it is our responsibility."
+    "text": "Status: Proposed\nDeciders: V-Sekai, fire\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20220202-gltf-extensions-for-interoperability.html#references",
-    "href": "decisions/20220202-gltf-extensions-for-interoperability.html#references",
-    "title": "Accepted: Interoperability between platforms using gltf extensions",
+    "objectID": "decisions/20231027-drawing-concept-to-blockout.html#the-backdrop",
+    "href": "decisions/20231027-drawing-concept-to-blockout.html#the-backdrop",
+    "title": "Proposed: Drawing Concept to Blockout",
     "section": "",
-    "text": "https://omigroup.org/"
+    "text": "The goal is to add more finished vrms to V-Sekai."
   },
   {
-    "objectID": "decisions/20220202-gltf-extensions-for-interoperability.html#derivative-license",
-    "href": "decisions/20220202-gltf-extensions-for-interoperability.html#derivative-license",
-    "title": "Accepted: Interoperability between platforms using gltf extensions",
+    "objectID": "decisions/20231027-drawing-concept-to-blockout.html#the-challenge",
+    "href": "decisions/20231027-drawing-concept-to-blockout.html#the-challenge",
+    "title": "Proposed: Drawing Concept to Blockout",
     "section": "",
-    "text": "Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "The task at hand is to create some concept art for an existing VRoid character model."
   },
   {
-    "objectID": "decisions/attachments/pitch_general_02.html",
-    "href": "decisions/attachments/pitch_general_02.html",
-    "title": "V-Sekai’s main goals and features:",
+    "objectID": "decisions/20231027-drawing-concept-to-blockout.html#the-strategy",
+    "href": "decisions/20231027-drawing-concept-to-blockout.html#the-strategy",
+    "title": "Proposed: Drawing Concept to Blockout",
     "section": "",
-    "text": "V-Sekai’s main goals and features:\nV-Sekai wants to make virtual collaboration easy for everyone by focusing on bringing people together and enabling creation.\nWith open voice and text chat, you can hang out and talk to others freely. Customize your VRM 1.0 avatar to represent yourself and feel like you’re among friends no matter where they are.\nOur simple spaces provide locations for any activity. You can discuss ideas in a casual lounge, brainstorm on interactive whiteboards, design together in a 3D workshop, or build fully customized environments.\nIn V-Sekai, you can express yourself by sharing and creating things together. You can doodle and prototype on the digital whiteboard or with 3D modeling tools. Bring in images, videos, web content, anything - then combine them into new inventions. You can create alone or with friends to keep improving each other’s work.\nWe know that new platforms need good tutorials. That’s why we make collaborating in V-Sekai simple, with friendly walkthroughs and a helpful community. We built this platform for you, and we listen and update regularly based on what the community wants to create.\nAt V-Sekai, we believe in open access. We are developing ways for outside creators to build new tools, spaces, and features that expand V-Sekai’s potential. We follow our values of empowering users, spreading joy, and helping shape this open world!\nV-Sekai provides space, freedom, and fertile ground for relationships to flourish. The essentials for hanging out with friends in a virtual world are simple enough for everyone yet open for spontaneous interaction and creating together. We build the foundation, and you provide the imagination. Join us in building the future of social VR!\nTo summarize, V-Sekai’s main objectives are:\n• Enabling open communication through voice/text chat and VRM 1.0 avatars\n• Providing simple, flexible spaces for any activity or collaboration\n• Sharing media, tools, and abilities to create together\n• Educating and supporting the community\n• Providing open access for user and creator contributions\n• Fostering human relationships and co-creation in virtual reality\n• Keeping the platform accessible to all while being open-ended enough for creativity\n• Building a foundation for connection focused on user experience\n• Developing an ecosystem where people power imagination and potential."
+    "text": "Here’s the proposed strategy:\n\nStart with grayscale outlines to focus on shapes rather than color.\nUse a off-white background, an outline color, a shadow color and a solid color.\nFocus on the overall shapes and silhouette first before adding details."
   },
   {
-    "objectID": "decisions/attachments/virtual_pets/LICENSE.html",
-    "href": "decisions/attachments/virtual_pets/LICENSE.html",
-    "title": "V-Sekai - Manuals",
+    "objectID": "decisions/20231027-drawing-concept-to-blockout.html#the-upside",
+    "href": "decisions/20231027-drawing-concept-to-blockout.html#the-upside",
+    "title": "Proposed: Drawing Concept to Blockout",
     "section": "",
-    "text": "CC0 1.0 Universal\nStatement of Purpose\nThe laws of most jurisdictions throughout the world automatically confer exclusive Copyright and Related Rights (defined below) upon the creator and subsequent owner(s) (each and all, an “owner”) of an original work of authorship and/or a database (each, a “Work”).\nCertain owners wish to permanently relinquish those rights to a Work for the purpose of contributing to a commons of creative, cultural and scientific works (“Commons”) that the public can reliably and without fear of later claims of infringement build upon, modify, incorporate in other works, reuse and redistribute as freely as possible in any form whatsoever and for any purposes, including without limitation commercial purposes. These owners may contribute to the Commons to promote the ideal of a free culture and the further production of creative, cultural and scientific works, or to gain reputation or greater distribution for their Work in part through the use and efforts of others.\nFor these and/or other purposes and motivations, and without any expectation of additional consideration or compensation, the person associating CC0 with a Work (the “Affirmer”), to the extent that he or she is an owner of Copyright and Related Rights in the Work, voluntarily elects to apply CC0 to the Work and publicly distribute the Work under its terms, with knowledge of his or her Copyright and Related Rights in the Work and the meaning and intended legal effect of CC0 on those rights.\n\nCopyright and Related Rights. A Work made available under CC0 may be protected by copyright and related or neighboring rights (“Copyright and Related Rights”). Copyright and Related Rights include, but are not limited to, the following:\n\n\nthe right to reproduce, adapt, distribute, perform, display, communicate, and translate a Work;\nmoral rights retained by the original author(s) and/or performer(s);\npublicity and privacy rights pertaining to a person’s image or likeness depicted in a Work;\nrights protecting against unfair competition in regards to a Work, subject to the limitations in paragraph 4(a), below;\nrights protecting the extraction, dissemination, use and reuse of data in a Work;\ndatabase rights (such as those arising under Directive 96/9/EC of the European Parliament and of the Council of 11 March 1996 on the legal protection of databases, and under any national implementation thereof, including any amended or successor version of such directive); and\nother similar, equivalent or corresponding rights throughout the world based on applicable law or treaty, and any national implementations thereof.\n\n\nWaiver. To the greatest extent permitted by, but not in contravention of, applicable law, Affirmer hereby overtly, fully, permanently, irrevocably and unconditionally waives, abandons, and surrenders all of Affirmer’s Copyright and Related Rights and associated claims and causes of action, whether now known or unknown (including existing as well as future claims and causes of action), in the Work (i) in all territories worldwide, (ii) for the maximum duration provided by applicable law or treaty (including future time extensions), (iii) in any current or future medium and for any number of copies, and (iv) for any purpose whatsoever, including without limitation commercial, advertising or promotional purposes (the “Waiver”). Affirmer makes the Waiver for the benefit of each member of the public at large and to the detriment of Affirmer’s heirs and successors, fully intending that such Waiver shall not be subject to revocation, rescission, cancellation, termination, or any other legal or equitable action to disrupt the quiet enjoyment of the Work by the public as contemplated by Affirmer’s express Statement of Purpose.\nPublic License Fallback. Should any part of the Waiver for any reason be judged legally invalid or ineffective under applicable law, then the Waiver shall be preserved to the maximum extent permitted taking into account Affirmer’s express Statement of Purpose. In addition, to the extent the Waiver is so judged Affirmer hereby grants to each affected person a royalty-free, non transferable, non sublicensable, non exclusive, irrevocable and unconditional license to exercise Affirmer’s Copyright and Related Rights in the Work (i) in all territories worldwide, (ii) for the maximum duration provided by applicable law or treaty (including future time extensions), (iii) in any current or future medium and for any number of copies, and (iv) for any purpose whatsoever, including without limitation commercial, advertising or promotional purposes (the “License”). The License shall be deemed effective as of the date CC0 was applied by Affirmer to the Work. Should any part of the License for any reason be judged legally invalid or ineffective under applicable law, such partial invalidity or ineffectiveness shall not invalidate the remainder of the License, and in such case Affirmer hereby affirms that he or she will not (i) exercise any of his or her remaining Copyright and Related Rights in the Work or (ii) assert any associated claims and causes of action with respect to the Work, in either case contrary to Affirmer’s express Statement of Purpose.\nLimitations and Disclaimers.\n\n\nNo trademark or patent rights held by Affirmer are waived, abandoned, surrendered, licensed or otherwise affected by this document.\nAffirmer offers the Work as-is and makes no representations or warranties of any kind concerning the Work, express, implied, statutory or otherwise, including without limitation warranties of title, merchantability, fitness for a particular purpose, non infringement, or the absence of latent or other defects, accuracy, or the present or absence of errors, whether or not discoverable, all to the greatest extent permissible under applicable law.\nAffirmer disclaims responsibility for clearing rights of other persons that may apply to the Work or any use thereof, including without limitation any person’s Copyright and Related Rights in the Work. Further, Affirmer disclaims responsibility for obtaining any necessary consents, permissions or other rights required for any use of the Work.\nAffirmer understands and acknowledges that Creative Commons is not a party to this document and has no duty or obligation with respect to this CC0 or use of the Work.\n\nFor more information, please see http://creativecommons.org/publicdomain/zero/1.0/"
+    "text": "This process will help nail down the overall look and feel before getting distracted by details and color. Starting with outlines and simple shapes will make it easier to iterate quickly."
   },
   {
-    "objectID": "decisions/20230507-avatar-publishing-workflow-portability.html",
-    "href": "decisions/20230507-avatar-publishing-workflow-portability.html",
-    "title": "Draft: Describe a avatar publishing workflow for portability",
+    "objectID": "decisions/20231027-drawing-concept-to-blockout.html#the-downside",
+    "href": "decisions/20231027-drawing-concept-to-blockout.html#the-downside",
+    "title": "Proposed: Drawing Concept to Blockout",
     "section": "",
-    "text": "Status: draft \nDeciders: V-Sekai, fire\nTags: V-Sekai, ChatGPT-4, Avatar Publishing, Workflow, Portability, VRM Format, Silent’s Shader, Platform Compatibility, Sketchfab, Booth.pm\n\n\n\n\nWe want to create a workflow for publishing avatars in a portable format that can be easily used across different platforms. The goal is to streamline the process of converting and exporting avatars while maintaining compatibility with various platforms.\n\n\n\nThe proposed solution involves using the VRM portable avatar format, Silent’s shader, and platform-specific package bundles to create a seamless workflow for avatar publishing.\n\n\n\n\nImport avatar in VRM0 portable avatar format.\nInstall Silent’s shader 1.11.\nConvert VRM to compatible platform’s internal format.\n\nAvoid “Combine Mesh” option.\nThe Cutout Rendering Mode matches VRM’s usual transparency usage.\nUNRESOLVED: VRM Colliders cause greatly increased count of simulated physics objects\n\n\nTry switching to inside bounds instead of bone as spheres\n\nSwap the mtoon material for Silent’s shader’s crosstone material. Fire doesn’t use the light-ramp shader.\nMany bones need to be the first child for IK to work.\nFire prefers solid colour backgrounds for avatar photos\nExport as a compatible platform package bundle.\nBundle VRM and compatible platform package bundle and publish on Sketchfab and/or Booth.pm.\nThe compatible platform should display the avatar as poor rated.\n\n\n\n\n\nStreamlined avatar publishing process.\nIncreased portability and compatibility with different platforms.\nEasier sharing and distribution of avatars.\n\n\n\n\n\nPotential loss of some features or quality during conversion.\nMay require additional work to ensure compatibility with all desired platforms.\n\n\n\n\nN/A\n\n\n\nNo, this enhancement aims to create a comprehensive workflow for avatar publishing, which cannot be achieved with just a few lines of script.\n\n\n\nYes, creating a standardized workflow for avatar publishing ensures consistency and compatibility across platforms, making it easier for users to share and distribute their avatars.\n\n\n\n\nV-Sekai: V-Sekai\nSilent Cel Shading Shader: SCSS\nSilent Cel Shading Shader v1.11: Silent Cel Shading Shader v1.11\nBooth.pm: Booth.pm\nSketchfab: Sketchfab\nVRM converter for compatible platform: VRM converter\n\nAutomatically installs Univrm: Univrm"
+    "text": "The downside could be that focusing too much on the overall shape might lead to neglecting the finer details which are also important in character design. Also, this approach may not work as effectively for complex designs."
   },
   {
-    "objectID": "decisions/20230507-avatar-publishing-workflow-portability.html#metadata",
-    "href": "decisions/20230507-avatar-publishing-workflow-portability.html#metadata",
-    "title": "Draft: Describe a avatar publishing workflow for portability",
+    "objectID": "decisions/20231027-drawing-concept-to-blockout.html#the-road-not-taken",
+    "href": "decisions/20231027-drawing-concept-to-blockout.html#the-road-not-taken",
+    "title": "Proposed: Drawing Concept to Blockout",
     "section": "",
-    "text": "Status: draft \nDeciders: V-Sekai, fire\nTags: V-Sekai, ChatGPT-4, Avatar Publishing, Workflow, Portability, VRM Format, Silent’s Shader, Platform Compatibility, Sketchfab, Booth.pm"
+    "text": "An alternative approach could have been to start with detailed sketches instead of broad shapes. This would allow for more detail early on but could potentially slow down the iteration process."
   },
   {
-    "objectID": "decisions/20230507-avatar-publishing-workflow-portability.html#context-and-problem-statement",
-    "href": "decisions/20230507-avatar-publishing-workflow-portability.html#context-and-problem-statement",
-    "title": "Draft: Describe a avatar publishing workflow for portability",
+    "objectID": "decisions/20231027-drawing-concept-to-blockout.html#the-infrequent-use-case",
+    "href": "decisions/20231027-drawing-concept-to-blockout.html#the-infrequent-use-case",
+    "title": "Proposed: Drawing Concept to Blockout",
     "section": "",
-    "text": "We want to create a workflow for publishing avatars in a portable format that can be easily used across different platforms. The goal is to streamline the process of converting and exporting avatars while maintaining compatibility with various platforms."
+    "text": "This method might not be suitable if the character design is already well established and does not require significant changes to its overall shape and structure."
   },
   {
-    "objectID": "decisions/20230507-avatar-publishing-workflow-portability.html#proposed-solution",
-    "href": "decisions/20230507-avatar-publishing-workflow-portability.html#proposed-solution",
-    "title": "Draft: Describe a avatar publishing workflow for portability",
+    "objectID": "decisions/20231027-drawing-concept-to-blockout.html#in-core-and-done-by-us",
+    "href": "decisions/20231027-drawing-concept-to-blockout.html#in-core-and-done-by-us",
+    "title": "Proposed: Drawing Concept to Blockout",
     "section": "",
-    "text": "The proposed solution involves using the VRM portable avatar format, Silent’s shader, and platform-specific package bundles to create a seamless workflow for avatar publishing."
+    "text": "Yes, this is a core part of our design process and is done by us."
   },
   {
-    "objectID": "decisions/20230507-avatar-publishing-workflow-portability.html#implementation",
-    "href": "decisions/20230507-avatar-publishing-workflow-portability.html#implementation",
-    "title": "Draft: Describe a avatar publishing workflow for portability",
+    "objectID": "decisions/20231027-drawing-concept-to-blockout.html#further-reading",
+    "href": "decisions/20231027-drawing-concept-to-blockout.html#further-reading",
+    "title": "Proposed: Drawing Concept to Blockout",
     "section": "",
-    "text": "Import avatar in VRM0 portable avatar format.\nInstall Silent’s shader 1.11.\nConvert VRM to compatible platform’s internal format.\n\nAvoid “Combine Mesh” option.\nThe Cutout Rendering Mode matches VRM’s usual transparency usage.\nUNRESOLVED: VRM Colliders cause greatly increased count of simulated physics objects\n\n\nTry switching to inside bounds instead of bone as spheres\n\nSwap the mtoon material for Silent’s shader’s crosstone material. Fire doesn’t use the light-ramp shader.\nMany bones need to be the first child for IK to work.\nFire prefers solid colour backgrounds for avatar photos\nExport as a compatible platform package bundle.\nBundle VRM and compatible platform package bundle and publish on Sketchfab and/or Booth.pm.\nThe compatible platform should display the avatar as poor rated."
+    "text": "For more information, you can visit the following links:\n\nV-Sekai\nAI assists this article."
   },
   {
-    "objectID": "decisions/20230507-avatar-publishing-workflow-portability.html#positive-consequences",
-    "href": "decisions/20230507-avatar-publishing-workflow-portability.html#positive-consequences",
-    "title": "Draft: Describe a avatar publishing workflow for portability",
+    "objectID": "decisions/20231108-nier-automata-world-expansion.html",
+    "href": "decisions/20231108-nier-automata-world-expansion.html",
+    "title": "Proposed: “Freedom is in a future that you did not have in the past” - A Game Development Philosophy from NieR:Automata",
     "section": "",
-    "text": "Streamlined avatar publishing process.\nIncreased portability and compatibility with different platforms.\nEasier sharing and distribution of avatars."
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, Game Development, Open-world, Rich Content\n\n\n\n\nDuring GDC 2018, Yoko Taro and Takahisa Taura, key figures behind the creation of ‘NieR:Automata’, shared their insights on game development. Their panel was among the most attended, shedding light on the philosophy of game development and the intricacies of crafting an immersive world.\n\n\n\nThe primary challenge in game development lies in striking a balance between open-world freedom and rich content. While gamers often equate ultimate freedom with open-world games, many such titles lack depth. The goal should be to design the right gameplay mechanics while ensuring high player immersion.\n\n\n\n\n“Freedom is in a future that you did not have in the past” - Yoko Taro (40:40)\n\nYoko Taro emphasized the importance of incorporating freedom in a game while maintaining a balance between an open-world and rich content. He drew inspiration from The Legend of Zelda: Ocarina of Time when building the world of NieR. This strategy involves creating easy-to-learn gameplay without hindering the flow of the experience.\n\n\n\nThis approach fosters a more immersive gaming experience. By concentrating on the appropriate gameplay mechanics and balancing open-world freedom with rich content, developers can produce games that are both engaging and meaningful.\n\n\n\nThe downside to this approach is that it may necessitate more time and resources for development. Achieving a balance between open-world freedom and rich content can be a complex task, demanding meticulous planning and execution.\n\n\n\nAn alternative strategy could involve focusing exclusively on either open-world freedom or rich content. However, this could lead to a game that lacks depth or fails to fully captivate players.\n\n\n\nThis approach may not be suitable for all types of games. For instance, games that are heavily story-driven may not benefit from an open-world format.\n\n\n\nThis strategy is in line with our core philosophy of game development. We believe in crafting immersive experiences that balance freedom with rich content.\n\n\n\nFor more insights on this topic, consider the following resources:\n\nV-Sekai: The official GitHub page of V-Sekai, featuring various projects and initiatives related to game development.\nGDC 2018: A Fun Time in Which Some No-Good Game Developers May Discuss How We Made ‘NieR:Automata’: A comprehensive report on the GDC 2018 panel featuring Yoko Taro and Takahisa Taura discussing the creation process of ‘NieR:Automata’.\nGDC 2018 Video: A Fun Time in Which Some No-Good Game Developers May Discuss How We Made ‘NieR:Automata’\n\nThis article was assisted by AI."
   },
   {
-    "objectID": "decisions/20230507-avatar-publishing-workflow-portability.html#negative-consequences",
-    "href": "decisions/20230507-avatar-publishing-workflow-portability.html#negative-consequences",
-    "title": "Draft: Describe a avatar publishing workflow for portability",
+    "objectID": "decisions/20231108-nier-automata-world-expansion.html#metadata",
+    "href": "decisions/20231108-nier-automata-world-expansion.html#metadata",
+    "title": "Proposed: “Freedom is in a future that you did not have in the past” - A Game Development Philosophy from NieR:Automata",
     "section": "",
-    "text": "Potential loss of some features or quality during conversion.\nMay require additional work to ensure compatibility with all desired platforms."
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, Game Development, Open-world, Rich Content"
   },
   {
-    "objectID": "decisions/20230507-avatar-publishing-workflow-portability.html#option-graveyard",
-    "href": "decisions/20230507-avatar-publishing-workflow-portability.html#option-graveyard",
-    "title": "Draft: Describe a avatar publishing workflow for portability",
+    "objectID": "decisions/20231108-nier-automata-world-expansion.html#context",
+    "href": "decisions/20231108-nier-automata-world-expansion.html#context",
+    "title": "Proposed: “Freedom is in a future that you did not have in the past” - A Game Development Philosophy from NieR:Automata",
     "section": "",
-    "text": "N/A"
+    "text": "During GDC 2018, Yoko Taro and Takahisa Taura, key figures behind the creation of ‘NieR:Automata’, shared their insights on game development. Their panel was among the most attended, shedding light on the philosophy of game development and the intricacies of crafting an immersive world."
   },
   {
-    "objectID": "decisions/20230507-avatar-publishing-workflow-portability.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230507-avatar-publishing-workflow-portability.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Draft: Describe a avatar publishing workflow for portability",
+    "objectID": "decisions/20231108-nier-automata-world-expansion.html#problem",
+    "href": "decisions/20231108-nier-automata-world-expansion.html#problem",
+    "title": "Proposed: “Freedom is in a future that you did not have in the past” - A Game Development Philosophy from NieR:Automata",
     "section": "",
-    "text": "No, this enhancement aims to create a comprehensive workflow for avatar publishing, which cannot be achieved with just a few lines of script."
+    "text": "The primary challenge in game development lies in striking a balance between open-world freedom and rich content. While gamers often equate ultimate freedom with open-world games, many such titles lack depth. The goal should be to design the right gameplay mechanics while ensuring high player immersion."
   },
   {
-    "objectID": "decisions/20230507-avatar-publishing-workflow-portability.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230507-avatar-publishing-workflow-portability.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Draft: Describe a avatar publishing workflow for portability",
+    "objectID": "decisions/20231108-nier-automata-world-expansion.html#strategy",
+    "href": "decisions/20231108-nier-automata-world-expansion.html#strategy",
+    "title": "Proposed: “Freedom is in a future that you did not have in the past” - A Game Development Philosophy from NieR:Automata",
     "section": "",
-    "text": "Yes, creating a standardized workflow for avatar publishing ensures consistency and compatibility across platforms, making it easier for users to share and distribute their avatars."
+    "text": "“Freedom is in a future that you did not have in the past” - Yoko Taro (40:40)\n\nYoko Taro emphasized the importance of incorporating freedom in a game while maintaining a balance between an open-world and rich content. He drew inspiration from The Legend of Zelda: Ocarina of Time when building the world of NieR. This strategy involves creating easy-to-learn gameplay without hindering the flow of the experience."
   },
   {
-    "objectID": "decisions/20230507-avatar-publishing-workflow-portability.html#references",
-    "href": "decisions/20230507-avatar-publishing-workflow-portability.html#references",
-    "title": "Draft: Describe a avatar publishing workflow for portability",
+    "objectID": "decisions/20231108-nier-automata-world-expansion.html#pros",
+    "href": "decisions/20231108-nier-automata-world-expansion.html#pros",
+    "title": "Proposed: “Freedom is in a future that you did not have in the past” - A Game Development Philosophy from NieR:Automata",
     "section": "",
-    "text": "V-Sekai: V-Sekai\nSilent Cel Shading Shader: SCSS\nSilent Cel Shading Shader v1.11: Silent Cel Shading Shader v1.11\nBooth.pm: Booth.pm\nSketchfab: Sketchfab\nVRM converter for compatible platform: VRM converter\n\nAutomatically installs Univrm: Univrm"
+    "text": "This approach fosters a more immersive gaming experience. By concentrating on the appropriate gameplay mechanics and balancing open-world freedom with rich content, developers can produce games that are both engaging and meaningful."
   },
   {
-    "objectID": "decisions/20230131-default-test-plan.html",
-    "href": "decisions/20230131-default-test-plan.html",
-    "title": "Accepted: Default test plan for testing V-Sekai engine upgrades.",
+    "objectID": "decisions/20231108-nier-automata-world-expansion.html#cons",
+    "href": "decisions/20231108-nier-automata-world-expansion.html#cons",
+    "title": "Proposed: “Freedom is in a future that you did not have in the past” - A Game Development Philosophy from NieR:Automata",
     "section": "",
-    "text": "Status: accepted \nDeciders: V-Sekai,fire,\nTags: V-Sekai,\n\n\n\nWant to write down the default test plan for V-sekai on engine upgrades.\n\n\n\nWrite the default test plans.\n\n\n\n\nCheck if OpenXR godot works by joining a server.\nOn pancake desktop mode, check if two clients connect to a 1 server and see each other’s movements.\nCheck if you can export a map.\nWIP Check audio io\n\n\n\n\nThese are the default things that should work.\n\n\n\nWork.\n\n\n\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\n\nThis is a standard procedure.\n\n\n\nWe need to test our work.\n\n\n\n\nV-Sekai\n\n\n\n\nMIT License\n\nCopyright (c) 2019-2022 K. S. Ernest (iFire) Lee (fire)\nCopyright (c) 2022 V-Sekai Contributors\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
+    "text": "The downside to this approach is that it may necessitate more time and resources for development. Achieving a balance between open-world freedom and rich content can be a complex task, demanding meticulous planning and execution."
   },
   {
-    "objectID": "decisions/20230131-default-test-plan.html#context-and-problem-statement",
-    "href": "decisions/20230131-default-test-plan.html#context-and-problem-statement",
-    "title": "Accepted: Default test plan for testing V-Sekai engine upgrades.",
+    "objectID": "decisions/20231108-nier-automata-world-expansion.html#alternative-approach",
+    "href": "decisions/20231108-nier-automata-world-expansion.html#alternative-approach",
+    "title": "Proposed: “Freedom is in a future that you did not have in the past” - A Game Development Philosophy from NieR:Automata",
     "section": "",
-    "text": "Want to write down the default test plan for V-sekai on engine upgrades."
+    "text": "An alternative strategy could involve focusing exclusively on either open-world freedom or rich content. However, this could lead to a game that lacks depth or fails to fully captivate players."
   },
   {
-    "objectID": "decisions/20230131-default-test-plan.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20230131-default-test-plan.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Accepted: Default test plan for testing V-Sekai engine upgrades.",
+    "objectID": "decisions/20231108-nier-automata-world-expansion.html#limited-use-case",
+    "href": "decisions/20231108-nier-automata-world-expansion.html#limited-use-case",
+    "title": "Proposed: “Freedom is in a future that you did not have in the past” - A Game Development Philosophy from NieR:Automata",
     "section": "",
-    "text": "Write the default test plans."
+    "text": "This approach may not be suitable for all types of games. For instance, games that are heavily story-driven may not benefit from an open-world format."
   },
   {
-    "objectID": "decisions/20230131-default-test-plan.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20230131-default-test-plan.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Accepted: Default test plan for testing V-Sekai engine upgrades.",
+    "objectID": "decisions/20231108-nier-automata-world-expansion.html#alignment-with-our-core-philosophy",
+    "href": "decisions/20231108-nier-automata-world-expansion.html#alignment-with-our-core-philosophy",
+    "title": "Proposed: “Freedom is in a future that you did not have in the past” - A Game Development Philosophy from NieR:Automata",
     "section": "",
-    "text": "Check if OpenXR godot works by joining a server.\nOn pancake desktop mode, check if two clients connect to a 1 server and see each other’s movements.\nCheck if you can export a map.\nWIP Check audio io"
+    "text": "This strategy is in line with our core philosophy of game development. We believe in crafting immersive experiences that balance freedom with rich content."
   },
   {
-    "objectID": "decisions/20230131-default-test-plan.html#positive-consequences",
-    "href": "decisions/20230131-default-test-plan.html#positive-consequences",
-    "title": "Accepted: Default test plan for testing V-Sekai engine upgrades.",
+    "objectID": "decisions/20231108-nier-automata-world-expansion.html#additional-resources",
+    "href": "decisions/20231108-nier-automata-world-expansion.html#additional-resources",
+    "title": "Proposed: “Freedom is in a future that you did not have in the past” - A Game Development Philosophy from NieR:Automata",
     "section": "",
-    "text": "These are the default things that should work."
+    "text": "For more insights on this topic, consider the following resources:\n\nV-Sekai: The official GitHub page of V-Sekai, featuring various projects and initiatives related to game development.\nGDC 2018: A Fun Time in Which Some No-Good Game Developers May Discuss How We Made ‘NieR:Automata’: A comprehensive report on the GDC 2018 panel featuring Yoko Taro and Takahisa Taura discussing the creation process of ‘NieR:Automata’.\nGDC 2018 Video: A Fun Time in Which Some No-Good Game Developers May Discuss How We Made ‘NieR:Automata’\n\nThis article was assisted by AI."
   },
   {
-    "objectID": "decisions/20230131-default-test-plan.html#negative-consequences",
-    "href": "decisions/20230131-default-test-plan.html#negative-consequences",
-    "title": "Accepted: Default test plan for testing V-Sekai engine upgrades.",
+    "objectID": "decisions/20230516-additional-3d-import.html",
+    "href": "decisions/20230516-additional-3d-import.html",
+    "title": "Rejected: Additional 3D Import Functionality",
     "section": "",
-    "text": "Work."
+    "text": "Status: rejected \nDeciders: V-Sekai,fire,\nTags: V-Sekai,ChatGPT-4,AI_assistance\n\n\n\n\nImprove the 3D import functionality in Godot Engine for V-Sekai by enhancing the existing import process and adding support for more file formats.\nThis proposal is rejected because it doesn’t improve the 3D import functionality compared to its effort\n\n\n\n\nStatus: proposed\nDeciders: V-Sekai\nTags: V-Sekai, GPT-4\n\n\n\n\nV-Sekai has implemented .fbx and .gltf 3D import, and .obj is already part of Godot Engine. However, there is still room for improvement in the import process and support for additional file formats. The current Blender importer for Godot Engine 4.0 requires an additional installation and injects a Python script into Blender.\n\n\n\n\nDevelop an addon that can simultaneously export colliders, occluders, and LOD variants for a given mesh without requiring an additional Blender importer.\nEnhance the existing import process by providing better error handling, reporting, and automatic fixes for common issues.\nImprove the performance of the import process, especially for large and complex 3D models.\n\n\n\n\n\nCreate an addon that automatically searches for and sets Geometry Nodes input constants with relevant names (e.g., is_occluder, is_collider, and LOD) while exporting, giving modelers maximum flexibility on how different versions of a mesh should be exported. This addon should not require an additional Blender importer or Python script injection.\nUpdate the import pipeline to handle errors gracefully and provide helpful feedback to users.\nOptimize the import process by implementing caching, parallel processing, and other performance improvements.\n\n\n\n\n\nUsers will have more control over the export process, allowing them to easily manage colliders, occluders, and LOD variants without needing an additional Blender importer.\nThe improved import process will reduce the time spent on fixing import-related issues.\nFaster import times will lead to a smoother development experience.\n\n\n\n\n\nDeveloping an addon may require additional resources and maintenance.\nThere might be potential licensing issues with integrating third-party libraries.\n\n\n\n\n\nRelying solely on community plugins for additional import functionality.\nLimiting support to only a few popular file formats.\n\n\n\n\nNo, this enhancement addresses a core limitation in the engine and requires significant changes to the import pipeline.\n\n\n\nYes, improving the 3D import functionality is essential for providing a better user experience and supporting a wider range of 3D modeling tools. It also ensures that V-Sekai remains competitive with other game engines.\n\n\n\n\nV-Sekai"
   },
   {
-    "objectID": "decisions/20230131-default-test-plan.html#option-graveyard",
-    "href": "decisions/20230131-default-test-plan.html#option-graveyard",
-    "title": "Accepted: Default test plan for testing V-Sekai engine upgrades.",
+    "objectID": "decisions/20230516-additional-3d-import.html#metadata",
+    "href": "decisions/20230516-additional-3d-import.html#metadata",
+    "title": "Rejected: Additional 3D Import Functionality",
     "section": "",
-    "text": "Option: The status quo. \nRejection Reason: This solves nothing."
+    "text": "Status: rejected \nDeciders: V-Sekai,fire,\nTags: V-Sekai,ChatGPT-4,AI_assistance"
   },
   {
-    "objectID": "decisions/20230131-default-test-plan.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230131-default-test-plan.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Accepted: Default test plan for testing V-Sekai engine upgrades.",
+    "objectID": "decisions/20230516-additional-3d-import.html#propose-a-possible-solution-to-solve-a-v-sekai-limitation.-if-this-doesnt-look-right-choose-a-different-type.",
+    "href": "decisions/20230516-additional-3d-import.html#propose-a-possible-solution-to-solve-a-v-sekai-limitation.-if-this-doesnt-look-right-choose-a-different-type.",
+    "title": "Rejected: Additional 3D Import Functionality",
     "section": "",
-    "text": "This is a standard procedure."
+    "text": "Improve the 3D import functionality in Godot Engine for V-Sekai by enhancing the existing import process and adding support for more file formats.\nThis proposal is rejected because it doesn’t improve the 3D import functionality compared to its effort"
   },
   {
-    "objectID": "decisions/20230131-default-test-plan.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230131-default-test-plan.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Accepted: Default test plan for testing V-Sekai engine upgrades.",
+    "objectID": "decisions/20230516-additional-3d-import.html#metadata-1",
+    "href": "decisions/20230516-additional-3d-import.html#metadata-1",
+    "title": "Rejected: Additional 3D Import Functionality",
     "section": "",
-    "text": "We need to test our work."
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, GPT-4"
   },
   {
-    "objectID": "decisions/20230131-default-test-plan.html#references",
-    "href": "decisions/20230131-default-test-plan.html#references",
-    "title": "Accepted: Default test plan for testing V-Sekai engine upgrades.",
+    "objectID": "decisions/20230516-additional-3d-import.html#context-and-problem-statement",
+    "href": "decisions/20230516-additional-3d-import.html#context-and-problem-statement",
+    "title": "Rejected: Additional 3D Import Functionality",
     "section": "",
-    "text": "V-Sekai"
+    "text": "V-Sekai has implemented .fbx and .gltf 3D import, and .obj is already part of Godot Engine. However, there is still room for improvement in the import process and support for additional file formats. The current Blender importer for Godot Engine 4.0 requires an additional installation and injects a Python script into Blender."
   },
   {
-    "objectID": "decisions/20230131-default-test-plan.html#license-of-the-contribution",
-    "href": "decisions/20230131-default-test-plan.html#license-of-the-contribution",
-    "title": "Accepted: Default test plan for testing V-Sekai engine upgrades.",
+    "objectID": "decisions/20230516-additional-3d-import.html#proposed-solution",
+    "href": "decisions/20230516-additional-3d-import.html#proposed-solution",
+    "title": "Rejected: Additional 3D Import Functionality",
     "section": "",
-    "text": "MIT License\n\nCopyright (c) 2019-2022 K. S. Ernest (iFire) Lee (fire)\nCopyright (c) 2022 V-Sekai Contributors\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
+    "text": "Develop an addon that can simultaneously export colliders, occluders, and LOD variants for a given mesh without requiring an additional Blender importer.\nEnhance the existing import process by providing better error handling, reporting, and automatic fixes for common issues.\nImprove the performance of the import process, especially for large and complex 3D models."
   },
   {
-    "objectID": "decisions/20211031-benchmark-animation-playback.html",
-    "href": "decisions/20211031-benchmark-animation-playback.html",
-    "title": "Proposed: Benchmark #animation playback",
+    "objectID": "decisions/20230516-additional-3d-import.html#implementation",
+    "href": "decisions/20230516-additional-3d-import.html#implementation",
+    "title": "Rejected: Additional 3D Import Functionality",
     "section": "",
-    "text": "Proposed: Benchmark #animation playback\n\nContext and Problem Statement\nHow slow is #animation playback in a simulated player situation.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nNeed to see where we’re at.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n100, 500, 1’000, 50’000 avatars animating with 30fps and #animation compression on vs off.\nRandomize clips: idle, run, jump, walk (left, right, back, front)\nPut them into a 2d blend space and feed a random velocity.\nStart the #animation at different random offsets.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nCore code.\n\n\nPositive Consequences\n\nCan investigate compressed #animation player as a compute shader. The current architecture of the skinning and blend shapes #animation is like vertex #animation fed by buffers, but the keyframe playback is also problematic\n\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nI care about this more than other core contributors.\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Create an addon that automatically searches for and sets Geometry Nodes input constants with relevant names (e.g., is_occluder, is_collider, and LOD) while exporting, giving modelers maximum flexibility on how different versions of a mesh should be exported. This addon should not require an additional Blender importer or Python script injection.\nUpdate the import pipeline to handle errors gracefully and provide helpful feedback to users.\nOptimize the import process by implementing caching, parallel processing, and other performance improvements."
   },
   {
-    "objectID": "decisions/20221205-debug-linux-export.html",
-    "href": "decisions/20221205-debug-linux-export.html",
-    "title": "Proposed: Debug Linux Export",
+    "objectID": "decisions/20230516-additional-3d-import.html#positive-consequences",
+    "href": "decisions/20230516-additional-3d-import.html#positive-consequences",
+    "title": "Rejected: Additional 3D Import Functionality",
     "section": "",
-    "text": "Status: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nIt is hard to debug exports on Linux without using Linux as a desktop environment. There is a crash on export.\n\n\n\nPropose a workflow for debugging linux exports.\n\n\n\nUse wsl or a virtual machine.\n\nDownload the exact version of the editor that crashes on export.\nDownload the game templates.\nRun the export in a debugger\nFind the bug.\n\n\n\n\n\nWe can export again\nWriting down the workflow makes use be able to reuse processes.\n\n\n\n\nWe need to download the binaries manually for now.\n\n\n\n\nOption: The status quo. \nRejection Reason: This solves nothing. \nOption: Compile the package manually \nRejection Reason: This solves nothing because it is all manually and undocumented \n\n\n\n\nThis is a workflow document.\n\n\n\nWe have to build V-Sekai.\n\n\n\n\nV-Sekai\n\n\n\n\nMIT License\n\nCopyright (c) 2018-2022 SaracenOne\nCopyright (c) 2019-2022 K. S. Ernest (iFire) Lee (fire)\nCopyright (c) 2020-2022 Lyuma\nCopyright (c) 2020-2022 MMMaellon\nCopyright (c) 2022 V-Sekai Contributors\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
+    "text": "Users will have more control over the export process, allowing them to easily manage colliders, occluders, and LOD variants without needing an additional Blender importer.\nThe improved import process will reduce the time spent on fixing import-related issues.\nFaster import times will lead to a smoother development experience."
   },
   {
-    "objectID": "decisions/20221205-debug-linux-export.html#context-and-problem-statement",
-    "href": "decisions/20221205-debug-linux-export.html#context-and-problem-statement",
-    "title": "Proposed: Debug Linux Export",
+    "objectID": "decisions/20230516-additional-3d-import.html#negative-consequences",
+    "href": "decisions/20230516-additional-3d-import.html#negative-consequences",
+    "title": "Rejected: Additional 3D Import Functionality",
     "section": "",
-    "text": "It is hard to debug exports on Linux without using Linux as a desktop environment. There is a crash on export."
+    "text": "Developing an addon may require additional resources and maintenance.\nThere might be potential licensing issues with integrating third-party libraries."
   },
   {
-    "objectID": "decisions/20221205-debug-linux-export.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20221205-debug-linux-export.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: Debug Linux Export",
+    "objectID": "decisions/20230516-additional-3d-import.html#option-graveyard",
+    "href": "decisions/20230516-additional-3d-import.html#option-graveyard",
+    "title": "Rejected: Additional 3D Import Functionality",
     "section": "",
-    "text": "Propose a workflow for debugging linux exports."
+    "text": "Relying solely on community plugins for additional import functionality.\nLimiting support to only a few popular file formats."
   },
   {
-    "objectID": "decisions/20221205-debug-linux-export.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20221205-debug-linux-export.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Debug Linux Export",
+    "objectID": "decisions/20230516-additional-3d-import.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230516-additional-3d-import.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Rejected: Additional 3D Import Functionality",
     "section": "",
-    "text": "Use wsl or a virtual machine.\n\nDownload the exact version of the editor that crashes on export.\nDownload the game templates.\nRun the export in a debugger\nFind the bug."
+    "text": "No, this enhancement addresses a core limitation in the engine and requires significant changes to the import pipeline."
   },
   {
-    "objectID": "decisions/20221205-debug-linux-export.html#positive-consequences",
-    "href": "decisions/20221205-debug-linux-export.html#positive-consequences",
-    "title": "Proposed: Debug Linux Export",
+    "objectID": "decisions/20230516-additional-3d-import.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230516-additional-3d-import.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Rejected: Additional 3D Import Functionality",
     "section": "",
-    "text": "We can export again\nWriting down the workflow makes use be able to reuse processes."
+    "text": "Yes, improving the 3D import functionality is essential for providing a better user experience and supporting a wider range of 3D modeling tools. It also ensures that V-Sekai remains competitive with other game engines."
   },
   {
-    "objectID": "decisions/20221205-debug-linux-export.html#negative-consequences",
-    "href": "decisions/20221205-debug-linux-export.html#negative-consequences",
-    "title": "Proposed: Debug Linux Export",
+    "objectID": "decisions/20230516-additional-3d-import.html#references",
+    "href": "decisions/20230516-additional-3d-import.html#references",
+    "title": "Rejected: Additional 3D Import Functionality",
     "section": "",
-    "text": "We need to download the binaries manually for now."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20221205-debug-linux-export.html#option-graveyard",
-    "href": "decisions/20221205-debug-linux-export.html#option-graveyard",
-    "title": "Proposed: Debug Linux Export",
+    "objectID": "decisions/attachments/project_mirage.html",
+    "href": "decisions/attachments/project_mirage.html",
+    "title": "Project Mirage",
     "section": "",
-    "text": "Option: The status quo. \nRejection Reason: This solves nothing. \nOption: Compile the package manually \nRejection Reason: This solves nothing because it is all manually and undocumented"
+    "text": "Project Mirage\n\n\n\n\n\n\n\n\nStep\nDescription\nDependency\n\n\n\n\n1\nAn avatar’s face is created in a digital format, similar to drawing a portrait on a computer.\nNone\n\n\n2\nThe colors of the avatar are changed using Penpot, like using a digital paintbrush to change the color of a painting.\nCreated digital avatar\n\n\n3\nThe best looking avatars are chosen from a large group, like picking the best apples from a tree.\nChanged colors of the avatar\n\n\n4\nA body is added to the avatar using Blender’s CC0 base mesh, like adding a body to a mannequin head.\nChosen best looking avatars\n\n\n5\nAn attempt is made to create a 3D model of the back of the avatar (this wasn’t successful), like trying to sculpt the back of a statue but not getting it right.\nAdded body to the avatar\n\n\n6\nA tool is used to simplify any image, like using an eraser to remove details from a sketch.\nUnsuccessful attempt to create a 3D model of the back of the avatar\n\n\n7\nClothing and accessories are added to the avatar for Vroid Hub, like dressing up a doll.\nSimplified image\n\n\n8\nA 2D reference image is used in Blender, like using a photograph to help draw a picture.\nAdded clothing and accessories to the avatar\n\n\n9\nThe 2D image is placed in front of the 3D model, like placing a picture in front of a sculpture to use as a reference.\nUsed 2D reference image in Blender\n\n\n10\nAn image is captured from the camera’s point of view and sharpened, like taking a photo and then enhancing its clarity.\nPlaced 2D image in front of the 3D model\n\n\n11\nA tool is used that takes any image and generates a text caption, like writing a description for a photograph.\nCaptured and sharpened image from the camera’s point of view\n\n\n12\nThe color of the clothing is corrected and the pleated folds are ignored for the first try, like adjusting the colors in a painting and ignoring the small details for now.\nGenerated text caption from image\n\n\n13\nA complex structure involving sculpting and rigging is created, like building a skeleton for a clay model.\nCorrected color of the clothing\n\n\n14\nThe avatar is imported into Godot Engine and “Project Mirage”, like moving a digital file from one folder to another.\nCreated complex structure involving sculpting and rigging\n\n\n15\nThe imported avatar is refined in “Project Mirage”, like polishing a newly built machine.\nImported avatar into Godot Engine and “Project Mirage”\n\n\n16\nSpring bone “jiggle bones” are converted to phys bones and colliders, like changing the springs in a toy to make it more realistic.\nRefined the imported avatar in “Project Mirage”\n\n\n17\nPainting errors such as shirt seams and mesh clipping problems with the spine bone remain, like leaving some imperfections in a painting.\nConverted spring bone “jiggle bones” to phys bones and colliders\n\n\n18\nA choice is made between using the existing VRM MToon material in “Project Mirage” or using a friend’s custom SCSS shader, like choosing between two different types of paint for a painting.\nLeft painting errors unfixed\n\n\n19\nIssues with “Project Mirage”’s material counts and bones are dealt with, like solving problems in a complex puzzle.\nMade a choice between using the existing VRM MToon material in “Project Mirage” or using a friend’s custom SCSS shader\n\n\n20\nA process is established for moving files between “Project Mirage” and Godot Engine, like setting up a conveyor belt between two factories.\nDealt with issues with “Project Mirage”’s material counts and bones\n\n\n21\nVroid Hub’s hair painter and mesh generator are used, like using a special tool to add hair to a doll.\nEstablished process for moving files between “Project Mirage” and Godot Engine\n\n\n22\n“Perfect sync”, which are facial expressions for motion capture, is added, like giving a puppet the ability to show emotions.\nUsed Vroid Hub’s hair painter and mesh generator\n\n\n23\nMotion capture is set up using the Steam VR Lighthouse system, overcoming significant difficulties, like setting up a complex tracking system to record movements.\nAdded “perfect sync” facial expressions for motion capture"
   },
   {
-    "objectID": "decisions/20221205-debug-linux-export.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20221205-debug-linux-export.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Debug Linux Export",
+    "objectID": "decisions/attachments/thunderbolt_install_windows.html",
+    "href": "decisions/attachments/thunderbolt_install_windows.html",
+    "title": "Thunderbolt Driver Issue Solution",
     "section": "",
-    "text": "This is a workflow document."
+    "text": "Thunderbolt Driver Issue Solution\nTo all who end up in this thread, as I did. Welcome\nAnother user in this thread had a solution that worked for me, so I will repeat it with a more detailed explanation.\nCredit to “Johnatan” on page 3\nThe issue is that the new Thunderbolt drivers fail to remove and overwrite the old drivers. The problem can be resolved through the device manager.\nRight-click on “Start” (the Windows icon at the corner of your taskbar) and select “Device Manager.”\nWithin the device manager, open the category “System Devices.”\nScroll down to Thunderbolt(TM) Controller - (model number here)\n*Right-click on it, select “Uninstall Device,” and check the box “Delete the driver software for this device.”\nOnce removed, rerun the Thunderbolt installer or the update through the Dell Command Updater.\n*If you are worried about uninstalling the driver in the device manager, fret not. The driver will reinstall itself on reboot if you have an internet connection."
   },
   {
-    "objectID": "decisions/20221205-debug-linux-export.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20221205-debug-linux-export.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Debug Linux Export",
+    "objectID": "decisions/attachments/pitch_apple_vision_01.html",
+    "href": "decisions/attachments/pitch_apple_vision_01.html",
+    "title": "V-Sekai offer immersive experiences in various virtual environments.",
     "section": "",
-    "text": "We have to build V-Sekai."
+    "text": "V-Sekai, a proposed VR app for Apple Vision Pro, aims to offer immersive experiences in various virtual environments.\n\n\n\nSpatial Awareness: For interactive VR environments and enhancing 3D doodling and Virtual Avatar Performance.\nHigh Resolution Display: Utilizes Apple Vision Pro’s display for detailed VR rendering.\nVoice Communication: Allows user communication via voice chat.\n\n\n\n\n\nEye Tracking: Facilitates navigation and selection within the VR world.\nHand Gesture Recognition: Enables interaction with VR objects.\nProposed Machine Learning Technologies: Implements proposed speech-to-text and text-to-speech capabilities for real-time transcription and voice synthesis.\n\n\n\n\nV-Sekai offers exploration of pre-designed worlds or creation of custom ones. Users can manipulate VR objects, navigate menus with eye-tracking, and communicate via voice chat. Machine learning technologies enhance accessibility and interactivity. Spatial awareness adds depth to 3D doodling and Virtual Avatar Performance."
   },
   {
-    "objectID": "decisions/20221205-debug-linux-export.html#references",
-    "href": "decisions/20221205-debug-linux-export.html#references",
-    "title": "Proposed: Debug Linux Export",
+    "objectID": "decisions/attachments/pitch_apple_vision_01.html#key-features",
+    "href": "decisions/attachments/pitch_apple_vision_01.html#key-features",
+    "title": "V-Sekai offer immersive experiences in various virtual environments.",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Spatial Awareness: For interactive VR environments and enhancing 3D doodling and Virtual Avatar Performance.\nHigh Resolution Display: Utilizes Apple Vision Pro’s display for detailed VR rendering.\nVoice Communication: Allows user communication via voice chat."
   },
   {
-    "objectID": "decisions/20221205-debug-linux-export.html#license-of-the-contribution",
-    "href": "decisions/20221205-debug-linux-export.html#license-of-the-contribution",
-    "title": "Proposed: Debug Linux Export",
+    "objectID": "decisions/attachments/pitch_apple_vision_01.html#proposed-features",
+    "href": "decisions/attachments/pitch_apple_vision_01.html#proposed-features",
+    "title": "V-Sekai offer immersive experiences in various virtual environments.",
     "section": "",
-    "text": "MIT License\n\nCopyright (c) 2018-2022 SaracenOne\nCopyright (c) 2019-2022 K. S. Ernest (iFire) Lee (fire)\nCopyright (c) 2020-2022 Lyuma\nCopyright (c) 2020-2022 MMMaellon\nCopyright (c) 2022 V-Sekai Contributors\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
+    "text": "Eye Tracking: Facilitates navigation and selection within the VR world.\nHand Gesture Recognition: Enables interaction with VR objects.\nProposed Machine Learning Technologies: Implements proposed speech-to-text and text-to-speech capabilities for real-time transcription and voice synthesis."
   },
   {
-    "objectID": "decisions/20211005-create-sop-for-vrm-creation.html",
-    "href": "decisions/20211005-create-sop-for-vrm-creation.html",
-    "title": "Proposed: Create SOP for VRM #creation",
+    "objectID": "decisions/attachments/pitch_apple_vision_01.html#user-experience",
+    "href": "decisions/attachments/pitch_apple_vision_01.html#user-experience",
+    "title": "V-Sekai offer immersive experiences in various virtual environments.",
     "section": "",
-    "text": "Proposed: Create SOP for VRM #creation\n\nContext and Problem Statement\nCreate SOP for VRM #creation\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nHard to Get character #creation correct.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nList checkable prescriptions.\n\nSeparate Head from the body?\nMake sure every other mesh than the head mesh has no Head bone weights.\nDisable automatic mesh merging\nVertex weighting vs masking vs vrm spring bones\nSeparate leg weighting from each other with putting the character into the spread pose.\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nIs a workflow.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nNo one else is doing it.\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "V-Sekai offers exploration of pre-designed worlds or creation of custom ones. Users can manipulate VR objects, navigate menus with eye-tracking, and communicate via voice chat. Machine learning technologies enhance accessibility and interactivity. Spatial awareness adds depth to 3D doodling and Virtual Avatar Performance."
   },
   {
-    "objectID": "decisions/20220131-github-actions-support.html",
-    "href": "decisions/20220131-github-actions-support.html",
-    "title": "Accepted: To have an alternative CICD use Github Actions.",
+    "objectID": "decisions/20210523-simplfy-meshes-and-lods-better-with-quads.html",
+    "href": "decisions/20210523-simplfy-meshes-and-lods-better-with-quads.html",
+    "title": "Proposed: Simplify Meshes and LODs better with Quads",
     "section": "",
-    "text": "Status: accepted \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nGitHub actions is free and does not require running your own hardware for CI/CD. We understand some users may desire to use this route to build our system.\nHowever, we also want our system to be fully self hosted, so as a compromise, we may wish to offer first-party support for both types of continuous integration.\n\n\n\nWe will offer github actions files in our official Godot fork as well as our V-Sekai project.\n\n\n\nWe will generate github actions templates using the same jsonnet we use for GoCD.\n\n\n\n\nThe social network of GitHub is more accessible to most people.\nOffers more options for building our infrastructure and ways to get into Godot development, which is good.\nGitHub’s donated compute time may free up valuable compute resources for more critical operations.\n\n\n\n\n\nMaintaining more scripts requires our developer time\nMore codepaths means more QA or pieces that can break.\n\n\n\n\n\nOption: Keep the status quo, which is using GoCD or building manually on the command line.\nRejection Reason: Building manually on the command line is slow on Windows and not reproducible;\nRejection Reason: GoCD is inaccessible to most developers.\n\n\n\n\nIt can.\n\n\n\nWe want to maintain it to encourage developers and as the publisher of the platform it is our responsibility.\n\n\n\n\nhttps://jsonnet.org/\nhttps://docs.github.com/en/billing/managing-billing-for-github-actions/about-billing-for-github-actions\n\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Better mesh simplification and LODs that work on quads.\nCharacters that use subdivision look much better and be a difference between 18,000 quads and millions of quads.\n\n\n\nResearch a way to do subdivsion and decimation on quads.\n\n\nTo be determined.\n\n\n\n\nVisual Quality\nMaintainability\n\n\n\n\n\nTechnical complexity\n\n(this section can be repeated for each option, if more than one option is open for consideration\n\n\n\n\nList the proposed options no longer open for consideration.\nList the reasons for the rejection: (the Bad traits)\n\n\n\nNot trivial to do.\n\n\n\nWe want the source art to be in quads so we can post process it in the game.\n\n\n\n\nhttps://gdcvault.com/play/1026752/Quad-Mesh-Simplification-in\nhttps://github.com/godotengine/godot-proposals/issues/3861\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20220131-github-actions-support.html#context-and-problem-statement",
-    "href": "decisions/20220131-github-actions-support.html#context-and-problem-statement",
-    "title": "Accepted: To have an alternative CICD use Github Actions.",
+    "objectID": "decisions/20210523-simplfy-meshes-and-lods-better-with-quads.html#context-and-problem-statement",
+    "href": "decisions/20210523-simplfy-meshes-and-lods-better-with-quads.html#context-and-problem-statement",
+    "title": "Proposed: Simplify Meshes and LODs better with Quads",
     "section": "",
-    "text": "GitHub actions is free and does not require running your own hardware for CI/CD. We understand some users may desire to use this route to build our system.\nHowever, we also want our system to be fully self hosted, so as a compromise, we may wish to offer first-party support for both types of continuous integration."
+    "text": "Better mesh simplification and LODs that work on quads.\nCharacters that use subdivision look much better and be a difference between 18,000 quads and millions of quads."
   },
   {
-    "objectID": "decisions/20220131-github-actions-support.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20220131-github-actions-support.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Accepted: To have an alternative CICD use Github Actions.",
+    "objectID": "decisions/20210523-simplfy-meshes-and-lods-better-with-quads.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20210523-simplfy-meshes-and-lods-better-with-quads.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: Simplify Meshes and LODs better with Quads",
     "section": "",
-    "text": "We will offer github actions files in our official Godot fork as well as our V-Sekai project."
+    "text": "Research a way to do subdivsion and decimation on quads.\n\n\nTo be determined.\n\n\n\n\nVisual Quality\nMaintainability\n\n\n\n\n\nTechnical complexity\n\n(this section can be repeated for each option, if more than one option is open for consideration"
   },
   {
-    "objectID": "decisions/20220131-github-actions-support.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20220131-github-actions-support.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Accepted: To have an alternative CICD use Github Actions.",
+    "objectID": "decisions/20210523-simplfy-meshes-and-lods-better-with-quads.html#option-graveyard-tris",
+    "href": "decisions/20210523-simplfy-meshes-and-lods-better-with-quads.html#option-graveyard-tris",
+    "title": "Proposed: Simplify Meshes and LODs better with Quads",
     "section": "",
-    "text": "We will generate github actions templates using the same jsonnet we use for GoCD."
+    "text": "List the proposed options no longer open for consideration.\nList the reasons for the rejection: (the Bad traits)"
   },
   {
-    "objectID": "decisions/20220131-github-actions-support.html#positive-consequences",
-    "href": "decisions/20220131-github-actions-support.html#positive-consequences",
-    "title": "Accepted: To have an alternative CICD use Github Actions.",
+    "objectID": "decisions/20210523-simplfy-meshes-and-lods-better-with-quads.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20210523-simplfy-meshes-and-lods-better-with-quads.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Simplify Meshes and LODs better with Quads",
     "section": "",
-    "text": "The social network of GitHub is more accessible to most people.\nOffers more options for building our infrastructure and ways to get into Godot development, which is good.\nGitHub’s donated compute time may free up valuable compute resources for more critical operations."
+    "text": "Not trivial to do."
   },
   {
-    "objectID": "decisions/20220131-github-actions-support.html#negative-consequences",
-    "href": "decisions/20220131-github-actions-support.html#negative-consequences",
-    "title": "Accepted: To have an alternative CICD use Github Actions.",
+    "objectID": "decisions/20210523-simplfy-meshes-and-lods-better-with-quads.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20210523-simplfy-meshes-and-lods-better-with-quads.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Simplify Meshes and LODs better with Quads",
     "section": "",
-    "text": "Maintaining more scripts requires our developer time\nMore codepaths means more QA or pieces that can break."
+    "text": "We want the source art to be in quads so we can post process it in the game."
   },
   {
-    "objectID": "decisions/20220131-github-actions-support.html#option-graveyard",
-    "href": "decisions/20220131-github-actions-support.html#option-graveyard",
-    "title": "Accepted: To have an alternative CICD use Github Actions.",
+    "objectID": "decisions/20210523-simplfy-meshes-and-lods-better-with-quads.html#references",
+    "href": "decisions/20210523-simplfy-meshes-and-lods-better-with-quads.html#references",
+    "title": "Proposed: Simplify Meshes and LODs better with Quads",
     "section": "",
-    "text": "Option: Keep the status quo, which is using GoCD or building manually on the command line.\nRejection Reason: Building manually on the command line is slow on Windows and not reproducible;\nRejection Reason: GoCD is inaccessible to most developers."
+    "text": "https://gdcvault.com/play/1026752/Quad-Mesh-Simplification-in\nhttps://github.com/godotengine/godot-proposals/issues/3861"
   },
   {
-    "objectID": "decisions/20220131-github-actions-support.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20220131-github-actions-support.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Accepted: To have an alternative CICD use Github Actions.",
+    "objectID": "decisions/20210523-simplfy-meshes-and-lods-better-with-quads.html#derivative-license",
+    "href": "decisions/20210523-simplfy-meshes-and-lods-better-with-quads.html#derivative-license",
+    "title": "Proposed: Simplify Meshes and LODs better with Quads",
     "section": "",
-    "text": "It can."
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20220131-github-actions-support.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20220131-github-actions-support.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Accepted: To have an alternative CICD use Github Actions.",
+    "objectID": "decisions/20230525-animation-ik-node.html",
+    "href": "decisions/20230525-animation-ik-node.html",
+    "title": "Proposed: Convert IK solvers to be using the AnimationTree",
     "section": "",
-    "text": "We want to maintain it to encourage developers and as the publisher of the platform it is our responsibility."
+    "text": "Status: proposed\nDeciders: V-Sekai, fire,\nTags: V-Sekai, GPT-4\n\n\n\n\nAs part of the V-Sekai project we’re working on virtual worlds and avatars usable for all.\n\n\n\nThere is no robust, and production quality inverse kinematic solver for full body tracking virtual reality tracking and other inverse kinematic uses like foot planting and hand grabbing.\nIn addition to the limitations of the current IK system due to its implementation as a SkeletonIK3D node, the IK system can be improved by reimplementing it as an animation node. This can address these limitations and improve the overall functionality.\n\n\n\n\nReimplement the IK system as an animation node to gain better control over the processing order, ensure accurate pose states.\nReuse the track filtering code that exists in the AnimationTree system to enhance the new IK system’s capabilities.\n\n\n\n\nIn order to improve the Inverse Kinematics (IK) system, we will replace SkeletonIK3D with a new custom AnimationNode called IKAnimationNode. This new node will ensure accurate pose states and provide precise control over the IK system.\nTo enhance the blending between animations and handle IK more efficiently, we will reuse track filtering code from the existing AnimationTree. This will allow for smoother transitions and better performance.\nNext, we will implement the IK solver within the new IKAnimationNode. This solver will be responsible for calculating target positions and rotations for each bone in the skeleton.\nAfter implementing the IK solver, we will update the AnimationTree to use the new IKAnimationNode. This will involve adding an empty track, reading from the transform’s position, and blending between different animations to create seamless motion.\nAs we develop this new IK system, it is crucial to address potential issues such as filter usability, duplicate subtrees versus multiple outputs, and designing a reasonable full body setup. This includes handling jumping and foot IK interactions with the ground.\nFinally, we will test and optimize the new IK system to ensure correct functionality and optimal performance. This will result in a more robust and efficient IK solution for our animation needs.\n\n\n\n\nImproved control over the processing order of the IK system.\nAccurate pose states for better animation quality.\nPotential performance improvements by executing the animation tree outside of the main thread.\nEnhanced capabilities of the new IK system by reusing the track filtering code.\n\n\n\n\n\nIncreased complexity in the animation system.\nPossible compatibility issues with existing projects.\n\n\n\n\n\nKeeping the current SkeletonIK3D node and trying to improve its functionality.\nImplementing a custom IK solver without reusing the track filtering code from the AnimationTree system.\nUsing third-party IK solvers instead of developing an in-house solution.\n\n\n\n\nNo, the enhancement involves a significant change in the IK system’s implementation and cannot be easily worked around with a script.\n\n\n\nYes, addressing the limitations of the current IK system is crucial for improving V-Sekai’s functionality and providing a better experience for users.\n\n\n\n\nV-Sekai\nManyBoneIK3D (mentioned for reference purposes only)"
   },
   {
-    "objectID": "decisions/20220131-github-actions-support.html#references",
-    "href": "decisions/20220131-github-actions-support.html#references",
-    "title": "Accepted: To have an alternative CICD use Github Actions.",
+    "objectID": "decisions/20230525-animation-ik-node.html#metadata",
+    "href": "decisions/20230525-animation-ik-node.html#metadata",
+    "title": "Proposed: Convert IK solvers to be using the AnimationTree",
     "section": "",
-    "text": "https://jsonnet.org/\nhttps://docs.github.com/en/billing/managing-billing-for-github-actions/about-billing-for-github-actions"
+    "text": "Status: proposed\nDeciders: V-Sekai, fire,\nTags: V-Sekai, GPT-4"
   },
   {
-    "objectID": "decisions/20220131-github-actions-support.html#derivative-license",
-    "href": "decisions/20220131-github-actions-support.html#derivative-license",
-    "title": "Accepted: To have an alternative CICD use Github Actions.",
+    "objectID": "decisions/20230525-animation-ik-node.html#project",
+    "href": "decisions/20230525-animation-ik-node.html#project",
+    "title": "Proposed: Convert IK solvers to be using the AnimationTree",
     "section": "",
-    "text": "Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "As part of the V-Sekai project we’re working on virtual worlds and avatars usable for all."
   },
   {
-    "objectID": "decisions/20221203-target-10-minutes-cicd.html",
-    "href": "decisions/20221203-target-10-minutes-cicd.html",
-    "title": "Proposed: Target 10 minutes cicd builds to improve our iterations",
+    "objectID": "decisions/20230525-animation-ik-node.html#context-and-problem-statement",
+    "href": "decisions/20230525-animation-ik-node.html#context-and-problem-statement",
+    "title": "Proposed: Convert IK solvers to be using the AnimationTree",
     "section": "",
-    "text": "Status: proposed \nDeciders: V-Sekai,fire,\nTags: V-Sekai,\n\n\n\nCICD builds take too long to do.\n\n\n\nTry to aim for 10 minute builds and reduce stress.\n\n\n\nTry to aim for the godot cicd builds to finish in 10 minute.\n\n\n\nWe can see the results of our work.\n\n\n\nMight need to do special tricks.\n\n\n\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\n\nThis is a dev ops change.\n\n\n\nWe own the github repositories.\n\n\n\n\nV-Sekai\n\n\n\n\nCopyright (c) 2022 K. S. Ernest (iFire) Lee Copyright (c) 2022 V-Sekai contributors\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "There is no robust, and production quality inverse kinematic solver for full body tracking virtual reality tracking and other inverse kinematic uses like foot planting and hand grabbing.\nIn addition to the limitations of the current IK system due to its implementation as a SkeletonIK3D node, the IK system can be improved by reimplementing it as an animation node. This can address these limitations and improve the overall functionality."
   },
   {
-    "objectID": "decisions/20221203-target-10-minutes-cicd.html#context-and-problem-statement",
-    "href": "decisions/20221203-target-10-minutes-cicd.html#context-and-problem-statement",
-    "title": "Proposed: Target 10 minutes cicd builds to improve our iterations",
+    "objectID": "decisions/20230525-animation-ik-node.html#proposed-solution",
+    "href": "decisions/20230525-animation-ik-node.html#proposed-solution",
+    "title": "Proposed: Convert IK solvers to be using the AnimationTree",
     "section": "",
-    "text": "CICD builds take too long to do."
+    "text": "Reimplement the IK system as an animation node to gain better control over the processing order, ensure accurate pose states.\nReuse the track filtering code that exists in the AnimationTree system to enhance the new IK system’s capabilities."
   },
   {
-    "objectID": "decisions/20221203-target-10-minutes-cicd.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20221203-target-10-minutes-cicd.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: Target 10 minutes cicd builds to improve our iterations",
+    "objectID": "decisions/20230525-animation-ik-node.html#implementation",
+    "href": "decisions/20230525-animation-ik-node.html#implementation",
+    "title": "Proposed: Convert IK solvers to be using the AnimationTree",
     "section": "",
-    "text": "Try to aim for 10 minute builds and reduce stress."
+    "text": "In order to improve the Inverse Kinematics (IK) system, we will replace SkeletonIK3D with a new custom AnimationNode called IKAnimationNode. This new node will ensure accurate pose states and provide precise control over the IK system.\nTo enhance the blending between animations and handle IK more efficiently, we will reuse track filtering code from the existing AnimationTree. This will allow for smoother transitions and better performance.\nNext, we will implement the IK solver within the new IKAnimationNode. This solver will be responsible for calculating target positions and rotations for each bone in the skeleton.\nAfter implementing the IK solver, we will update the AnimationTree to use the new IKAnimationNode. This will involve adding an empty track, reading from the transform’s position, and blending between different animations to create seamless motion.\nAs we develop this new IK system, it is crucial to address potential issues such as filter usability, duplicate subtrees versus multiple outputs, and designing a reasonable full body setup. This includes handling jumping and foot IK interactions with the ground.\nFinally, we will test and optimize the new IK system to ensure correct functionality and optimal performance. This will result in a more robust and efficient IK solution for our animation needs."
   },
   {
-    "objectID": "decisions/20221203-target-10-minutes-cicd.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20221203-target-10-minutes-cicd.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Target 10 minutes cicd builds to improve our iterations",
+    "objectID": "decisions/20230525-animation-ik-node.html#positive-consequences",
+    "href": "decisions/20230525-animation-ik-node.html#positive-consequences",
+    "title": "Proposed: Convert IK solvers to be using the AnimationTree",
     "section": "",
-    "text": "Try to aim for the godot cicd builds to finish in 10 minute."
+    "text": "Improved control over the processing order of the IK system.\nAccurate pose states for better animation quality.\nPotential performance improvements by executing the animation tree outside of the main thread.\nEnhanced capabilities of the new IK system by reusing the track filtering code."
   },
   {
-    "objectID": "decisions/20221203-target-10-minutes-cicd.html#positive-consequences",
-    "href": "decisions/20221203-target-10-minutes-cicd.html#positive-consequences",
-    "title": "Proposed: Target 10 minutes cicd builds to improve our iterations",
+    "objectID": "decisions/20230525-animation-ik-node.html#negative-consequences",
+    "href": "decisions/20230525-animation-ik-node.html#negative-consequences",
+    "title": "Proposed: Convert IK solvers to be using the AnimationTree",
     "section": "",
-    "text": "We can see the results of our work."
+    "text": "Increased complexity in the animation system.\nPossible compatibility issues with existing projects."
   },
   {
-    "objectID": "decisions/20221203-target-10-minutes-cicd.html#negative-consequences",
-    "href": "decisions/20221203-target-10-minutes-cicd.html#negative-consequences",
-    "title": "Proposed: Target 10 minutes cicd builds to improve our iterations",
+    "objectID": "decisions/20230525-animation-ik-node.html#option-graveyard",
+    "href": "decisions/20230525-animation-ik-node.html#option-graveyard",
+    "title": "Proposed: Convert IK solvers to be using the AnimationTree",
     "section": "",
-    "text": "Might need to do special tricks."
+    "text": "Keeping the current SkeletonIK3D node and trying to improve its functionality.\nImplementing a custom IK solver without reusing the track filtering code from the AnimationTree system.\nUsing third-party IK solvers instead of developing an in-house solution."
   },
   {
-    "objectID": "decisions/20221203-target-10-minutes-cicd.html#option-graveyard",
-    "href": "decisions/20221203-target-10-minutes-cicd.html#option-graveyard",
-    "title": "Proposed: Target 10 minutes cicd builds to improve our iterations",
+    "objectID": "decisions/20230525-animation-ik-node.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230525-animation-ik-node.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Convert IK solvers to be using the AnimationTree",
     "section": "",
-    "text": "Option: The status quo. \nRejection Reason: This solves nothing."
+    "text": "No, the enhancement involves a significant change in the IK system’s implementation and cannot be easily worked around with a script."
   },
   {
-    "objectID": "decisions/20221203-target-10-minutes-cicd.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20221203-target-10-minutes-cicd.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Target 10 minutes cicd builds to improve our iterations",
+    "objectID": "decisions/20230525-animation-ik-node.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230525-animation-ik-node.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Convert IK solvers to be using the AnimationTree",
     "section": "",
-    "text": "This is a dev ops change."
+    "text": "Yes, addressing the limitations of the current IK system is crucial for improving V-Sekai’s functionality and providing a better experience for users."
   },
   {
-    "objectID": "decisions/20221203-target-10-minutes-cicd.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20221203-target-10-minutes-cicd.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Target 10 minutes cicd builds to improve our iterations",
+    "objectID": "decisions/20230525-animation-ik-node.html#references",
+    "href": "decisions/20230525-animation-ik-node.html#references",
+    "title": "Proposed: Convert IK solvers to be using the AnimationTree",
     "section": "",
-    "text": "We own the github repositories."
+    "text": "V-Sekai\nManyBoneIK3D (mentioned for reference purposes only)"
   },
   {
-    "objectID": "decisions/20221203-target-10-minutes-cicd.html#references",
-    "href": "decisions/20221203-target-10-minutes-cicd.html#references",
-    "title": "Proposed: Target 10 minutes cicd builds to improve our iterations",
+    "objectID": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html",
+    "href": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html",
+    "title": "Rejected: Rewriting Mixer Broadcaster Into Membrane Framework Pipelines",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Status: Rejected\nDeciders: V-Sekai\nTags: V-Sekai, Elixir, Membrane Framework, Multiplayer Blender\n\n\n\n\nUbisoft’s mixer broadcaster code has been the only available solution for handling multiplayer Blender. However, it has its limitations when it comes to scalability and real-time performance. This proposal aims to rewrite the code using Elixir and the Membrane Framework.\n\n\n\nThe main challenge is to translate the existing code into Elixir while maintaining the functionality and improving upon the limitations of the current system. This includes ensuring that the new code can handle larger volumes of users and provide real-time updates without lag or delay.\n\n\n\ngraph LR\n  A[Ubisoft's Mixer Broadcaster Code] --&gt; B[Elixir & Membrane Framework Code]\n  C[No Authentication] --&gt; D[GitHub OAuth 2.0 Login]\n  E[No Database] --&gt; F[Khepri Database Library]\nThis strategy leverages Elixir and the Membrane Framework’s unique features, uses the Khepri database library for data management, and implements GitHub login using OAuth 2.0 protocol for single sign-on.\nHere are the key steps:\n\nCodebase: Transition from Ubisoft’s Mixer Broadcaster Code to Elixir & Membrane Framework Code, tracked in a version control system.\nDependencies: Declare and isolate dependencies explicitly, avoiding reliance on system-wide packages.\nConfig: Store configuration (including GitHub OAuth 2.0 Login credentials) in the environment, not in the code.\nBacking Services: Replace in-memory data persistence with Khepri Database Library, attached as a backing service.\nBuild, Release, Run: Strictly separate these stages, facilitated by the Elixir & Membrane Framework Code.\nProcesses: Execute application as one or more stateless processes, storing needed state in the Khepri database.\nPort Binding: Export services via port binding, making the application self-contained.\nConcurrency: Scale out the application via the process model, allowing for handling increased load.\nDisposability: Aim for fast startup and graceful shutdown to maximize robustness.\nDev/Prod Parity: Keep development, staging, and production environments as similar as possible.\nLogs: Treat logs as event streams, handled by the executing environment.\nAdmin Processes: Run any needed one-off administrative tasks in an identical environment as the regular long-running processes of the app.\n\n\n\n\nBy rewriting the code in Elixir, using the Membrane Framework, and implementing the Khepri database library, we can expect improved scalability and real-time performance. This will allow for more users to use the system simultaneously without experiencing delays or lags. Additionally, the fault-tolerance feature of Elixir will ensure that the system remains operational even when errors occur.\n\n\n\nRewriting the code will require time and resources. There may also be a learning curve for developers who are not familiar with Elixir, the Membrane Framework, and the Khepri database library.\n\n\n\nAn alternative approach would have been to optimize the existing code instead of rewriting it. However, this would not have addressed the inherent limitations of the current system.\n\n\n\nIn cases where the number of users is low and real-time updates are not critical, the current system may still be sufficient. However, as the user base grows and the demand for real-time updates increases, the need for a more scalable and efficient system becomes apparent.\n\n\n\nYes, the rewriting of the code will indeed be done by us as we also maintain the uro backend services.\n\n\n\n\nV-Sekai\nElixir\nMembrane Framework\nKhepri Database Library\n\nThis article is assisted by AI."
   },
   {
-    "objectID": "decisions/20221203-target-10-minutes-cicd.html#license-of-the-contribution",
-    "href": "decisions/20221203-target-10-minutes-cicd.html#license-of-the-contribution",
-    "title": "Proposed: Target 10 minutes cicd builds to improve our iterations",
+    "objectID": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html#metadata",
+    "href": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html#metadata",
+    "title": "Rejected: Rewriting Mixer Broadcaster Into Membrane Framework Pipelines",
     "section": "",
-    "text": "Copyright (c) 2022 K. S. Ernest (iFire) Lee Copyright (c) 2022 V-Sekai contributors\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Status: Rejected\nDeciders: V-Sekai\nTags: V-Sekai, Elixir, Membrane Framework, Multiplayer Blender"
   },
   {
-    "objectID": "decisions/20211031-have-better-user-developer-experience.html",
-    "href": "decisions/20211031-have-better-user-developer-experience.html",
-    "title": "Proposed: Have better user developer experience",
+    "objectID": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html#the-backdrop",
+    "href": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html#the-backdrop",
+    "title": "Rejected: Rewriting Mixer Broadcaster Into Membrane Framework Pipelines",
     "section": "",
-    "text": "Proposed: Have better user developer experience\n\nContext and Problem Statement\nV-Sekai can aim to better at user developer experience.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nWe can measure and improve our experience.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n\nMeasure\nImprove\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot a few lines of code.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nWe need to do it.\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Ubisoft’s mixer broadcaster code has been the only available solution for handling multiplayer Blender. However, it has its limitations when it comes to scalability and real-time performance. This proposal aims to rewrite the code using Elixir and the Membrane Framework."
   },
   {
-    "objectID": "decisions/20211031-streaming-godot-to-opensoundcontrol.html",
-    "href": "decisions/20211031-streaming-godot-to-opensoundcontrol.html",
-    "title": "Proposed: Take a streaming godot game and streaming the VRM to OpenSoundControl",
+    "objectID": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html#the-challenge",
+    "href": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html#the-challenge",
+    "title": "Rejected: Rewriting Mixer Broadcaster Into Membrane Framework Pipelines",
     "section": "",
-    "text": "Proposed: Take a streaming godot game and streaming the VRM to OpenSoundControl\n\nContext and Problem Statement\nStreaming to Godot OSC to jsons.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nStream the animation player because we have no way to stream Godot as a autonomous program.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n\nTake animation player\nPut it in a animation tree\nAnimation node streams motions to osc\nTake osc to node.js\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot trivial\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nIt’s rare to know how to dothis.\n\n\nReferences\n\nto node js https://github.com/colinbdclark/osc.js js\nhttps://github.com/infosia/vmc2bvh\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "The main challenge is to translate the existing code into Elixir while maintaining the functionality and improving upon the limitations of the current system. This includes ensuring that the new code can handle larger volumes of users and provide real-time updates without lag or delay."
   },
   {
-    "objectID": "decisions/20220207-virtual-pets.html",
-    "href": "decisions/20220207-virtual-pets.html",
-    "title": "Accepted: To make a virtual pet game given Jeana’s designs",
+    "objectID": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html#strategy",
+    "href": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html#strategy",
+    "title": "Rejected: Rewriting Mixer Broadcaster Into Membrane Framework Pipelines",
     "section": "",
-    "text": "Status: accepted\nDeciders: V-Sekai,ifire,Jeana,lyuma,\nTags: V-Sekai,\n\n\n\nWe were chatting late night and the idea of a virtual pet game was challenged.\n\n\n\n\n\n\nVRM with spring bones\nreverse bone direction\nSimulate virtual pet behaviors\n\n\n\n\n\nspringbone/constraint/follower (will clip through geom)\nphysics\nnavmesh (bake at runtime?)\nraycast\n\n\n\n\n\nWanted to create a virtual reality pet game where the pet was a character that was beside you in game and networked. The virtual pet would be with you in the game.\n\n\n\n\nAble to backtrack ideas.\n\n\n\n\n\nWork\n\n\n\n\n\nOption: Forgetting decisions.\nRejection Reason: We won’t remember the original reasons why we did things.\n\n\n\n\nNot a small amount of scripting.\n\n\n\nWe are running the project.\n\n\n\n\nhttps://twitter.com/jordy_j_s/status/1489644934743396356?s=20&t=WWesEW8ksELrkJa__3mUIg\nhttps://github.com/V-Sekai/godot-tfd\nhttps://twitter.com/VSekaiOfficial\nhttps://itch.io/jam/virtual-pet-jam\n\n\n\n\n\n\nJeana virtual pet concept\n\n\n\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "graph LR\n  A[Ubisoft's Mixer Broadcaster Code] --&gt; B[Elixir & Membrane Framework Code]\n  C[No Authentication] --&gt; D[GitHub OAuth 2.0 Login]\n  E[No Database] --&gt; F[Khepri Database Library]\nThis strategy leverages Elixir and the Membrane Framework’s unique features, uses the Khepri database library for data management, and implements GitHub login using OAuth 2.0 protocol for single sign-on.\nHere are the key steps:\n\nCodebase: Transition from Ubisoft’s Mixer Broadcaster Code to Elixir & Membrane Framework Code, tracked in a version control system.\nDependencies: Declare and isolate dependencies explicitly, avoiding reliance on system-wide packages.\nConfig: Store configuration (including GitHub OAuth 2.0 Login credentials) in the environment, not in the code.\nBacking Services: Replace in-memory data persistence with Khepri Database Library, attached as a backing service.\nBuild, Release, Run: Strictly separate these stages, facilitated by the Elixir & Membrane Framework Code.\nProcesses: Execute application as one or more stateless processes, storing needed state in the Khepri database.\nPort Binding: Export services via port binding, making the application self-contained.\nConcurrency: Scale out the application via the process model, allowing for handling increased load.\nDisposability: Aim for fast startup and graceful shutdown to maximize robustness.\nDev/Prod Parity: Keep development, staging, and production environments as similar as possible.\nLogs: Treat logs as event streams, handled by the executing environment.\nAdmin Processes: Run any needed one-off administrative tasks in an identical environment as the regular long-running processes of the app."
   },
   {
-    "objectID": "decisions/20220207-virtual-pets.html#context-and-problem-statement",
-    "href": "decisions/20220207-virtual-pets.html#context-and-problem-statement",
-    "title": "Accepted: To make a virtual pet game given Jeana’s designs",
+    "objectID": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html#the-upside",
+    "href": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html#the-upside",
+    "title": "Rejected: Rewriting Mixer Broadcaster Into Membrane Framework Pipelines",
     "section": "",
-    "text": "We were chatting late night and the idea of a virtual pet game was challenged."
+    "text": "By rewriting the code in Elixir, using the Membrane Framework, and implementing the Khepri database library, we can expect improved scalability and real-time performance. This will allow for more users to use the system simultaneously without experiencing delays or lags. Additionally, the fault-tolerance feature of Elixir will ensure that the system remains operational even when errors occur."
   },
   {
-    "objectID": "decisions/20220207-virtual-pets.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20220207-virtual-pets.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Accepted: To make a virtual pet game given Jeana’s designs",
+    "objectID": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html#the-downside",
+    "href": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html#the-downside",
+    "title": "Rejected: Rewriting Mixer Broadcaster Into Membrane Framework Pipelines",
     "section": "",
-    "text": "VRM with spring bones\nreverse bone direction\nSimulate virtual pet behaviors\n\n\n\n\n\nspringbone/constraint/follower (will clip through geom)\nphysics\nnavmesh (bake at runtime?)\nraycast"
+    "text": "Rewriting the code will require time and resources. There may also be a learning curve for developers who are not familiar with Elixir, the Membrane Framework, and the Khepri database library."
   },
   {
-    "objectID": "decisions/20220207-virtual-pets.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20220207-virtual-pets.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Accepted: To make a virtual pet game given Jeana’s designs",
+    "objectID": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html#the-road-not-taken",
+    "href": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html#the-road-not-taken",
+    "title": "Rejected: Rewriting Mixer Broadcaster Into Membrane Framework Pipelines",
     "section": "",
-    "text": "Wanted to create a virtual reality pet game where the pet was a character that was beside you in game and networked. The virtual pet would be with you in the game."
+    "text": "An alternative approach would have been to optimize the existing code instead of rewriting it. However, this would not have addressed the inherent limitations of the current system."
   },
   {
-    "objectID": "decisions/20220207-virtual-pets.html#positive-consequences",
-    "href": "decisions/20220207-virtual-pets.html#positive-consequences",
-    "title": "Accepted: To make a virtual pet game given Jeana’s designs",
+    "objectID": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html#the-infrequent-use-case",
+    "href": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html#the-infrequent-use-case",
+    "title": "Rejected: Rewriting Mixer Broadcaster Into Membrane Framework Pipelines",
     "section": "",
-    "text": "Able to backtrack ideas."
+    "text": "In cases where the number of users is low and real-time updates are not critical, the current system may still be sufficient. However, as the user base grows and the demand for real-time updates increases, the need for a more scalable and efficient system becomes apparent."
   },
   {
-    "objectID": "decisions/20220207-virtual-pets.html#negative-consequences",
-    "href": "decisions/20220207-virtual-pets.html#negative-consequences",
-    "title": "Accepted: To make a virtual pet game given Jeana’s designs",
+    "objectID": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html#in-core-and-done-by-us",
+    "href": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html#in-core-and-done-by-us",
+    "title": "Rejected: Rewriting Mixer Broadcaster Into Membrane Framework Pipelines",
     "section": "",
-    "text": "Work"
+    "text": "Yes, the rewriting of the code will indeed be done by us as we also maintain the uro backend services."
   },
   {
-    "objectID": "decisions/20220207-virtual-pets.html#option-graveyard",
-    "href": "decisions/20220207-virtual-pets.html#option-graveyard",
-    "title": "Accepted: To make a virtual pet game given Jeana’s designs",
+    "objectID": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html#further-reading",
+    "href": "decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html#further-reading",
+    "title": "Rejected: Rewriting Mixer Broadcaster Into Membrane Framework Pipelines",
     "section": "",
-    "text": "Option: Forgetting decisions.\nRejection Reason: We won’t remember the original reasons why we did things."
+    "text": "V-Sekai\nElixir\nMembrane Framework\nKhepri Database Library\n\nThis article is assisted by AI."
   },
   {
-    "objectID": "decisions/20220207-virtual-pets.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20220207-virtual-pets.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Accepted: To make a virtual pet game given Jeana’s designs",
+    "objectID": "decisions/20211031-arc-radial-menu.html",
+    "href": "decisions/20211031-arc-radial-menu.html",
+    "title": "Proposed: ARC radial menu",
     "section": "",
-    "text": "Not a small amount of scripting."
+    "text": "Proposed: ARC radial menu\n\nContext and Problem Statement\nNeed to make user experience easy to use\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nMake an arc menu.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nTo be mocked up.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nSure. can be script.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nUIUX is our business.\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20220207-virtual-pets.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20220207-virtual-pets.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Accepted: To make a virtual pet game given Jeana’s designs",
+    "objectID": "decisions/20240127-urban-explorer-gdc-2024-sample.html",
+    "href": "decisions/20240127-urban-explorer-gdc-2024-sample.html",
+    "title": "Proposed: Urban Navigator: The City Unveiled",
     "section": "",
-    "text": "We are running the project."
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nThe aim is to present a demo at the Game Developer Conference 2024 that will showcase the capabilities of the Godot Engine animation and Godot Engine 3D pipelines.\n\n\n\nThe task at hand is to create a Godot Engine demo within a span of one week.\n\n\n\nThe proposed idea is “Urban Navigator: The City Unveiled”. Embark on an exploratory journey through the heart of a city. Unravel the secrets of a sprawling metropolis where every street corner has a story to tell. With the help of advanced motion matching technology, your gamepad inputs are transformed into lifelike movements, enabling seamless interaction with the city.\n\n\n\nThe project will demonstrate the power and flexibility of the Godot Engine, potentially attracting more developers to use it. It also provides an opportunity to innovate in the field of urban exploration games.\n\n\n\nThe tight timeline could lead to compromises in quality or scope. There’s also a risk that the final product may not fully meet the expectations set by the proposal.\n\n\n\nAn alternative approach could have been to focus on a different genre or type of game that might be less complex but still showcases the capabilities of the Godot Engine.\n\n\n\nWhile the primary use case is for the Game Developer Conference demo, the developed game could also be used as a benchmarking tool for testing hardware performance with the Godot Engine.\n\n\n\nYes, this project is core to our mission of showcasing the capabilities of the Godot Engine and can be done by our team.\n\n\n\n\nV-Sekai · GitHub - This is the official GitHub account for the V-Sekai development community which focuses on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - This is the GitHub page for the V-Sekai open-source project that brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis article was assisted by AI assistant Aria."
   },
   {
-    "objectID": "decisions/20220207-virtual-pets.html#references",
-    "href": "decisions/20220207-virtual-pets.html#references",
-    "title": "Accepted: To make a virtual pet game given Jeana’s designs",
+    "objectID": "decisions/20240127-urban-explorer-gdc-2024-sample.html#metadata",
+    "href": "decisions/20240127-urban-explorer-gdc-2024-sample.html#metadata",
+    "title": "Proposed: Urban Navigator: The City Unveiled",
     "section": "",
-    "text": "https://twitter.com/jordy_j_s/status/1489644934743396356?s=20&t=WWesEW8ksELrkJa__3mUIg\nhttps://github.com/V-Sekai/godot-tfd\nhttps://twitter.com/VSekaiOfficial\nhttps://itch.io/jam/virtual-pet-jam\n\n\n\n\n\n\nJeana virtual pet concept"
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20220207-virtual-pets.html#derivative-license",
-    "href": "decisions/20220207-virtual-pets.html#derivative-license",
-    "title": "Accepted: To make a virtual pet game given Jeana’s designs",
+    "objectID": "decisions/20240127-urban-explorer-gdc-2024-sample.html#the-backdrop",
+    "href": "decisions/20240127-urban-explorer-gdc-2024-sample.html#the-backdrop",
+    "title": "Proposed: Urban Navigator: The City Unveiled",
     "section": "",
-    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "The aim is to present a demo at the Game Developer Conference 2024 that will showcase the capabilities of the Godot Engine animation and Godot Engine 3D pipelines."
   },
   {
-    "objectID": "decisions/20230310-xml-based-tests.html",
-    "href": "decisions/20230310-xml-based-tests.html",
-    "title": "Proposed: Use junit xml based tests in github",
+    "objectID": "decisions/20240127-urban-explorer-gdc-2024-sample.html#the-challenge",
+    "href": "decisions/20240127-urban-explorer-gdc-2024-sample.html#the-challenge",
+    "title": "Proposed: Urban Navigator: The City Unveiled",
     "section": "",
-    "text": "Proposed: Use junit xml based tests in github\n\nMetadata\n\nStatus: proposed \nDeciders: V-Sekai,fire,\nTags: V-Sekai,\n\n\n\nContext and Problem Statement\nV-Sekai is not robust.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nI want to make V-Sekai more robust using best practices like unit tests.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nWhen CICD runs it will run gut and parse the junit xml that is outputted.\nWe will also need to use pending head git workflow techniques.\n\n\nPositive Consequences\nWe will be able to use unit tests for gdscript, not just for C++ to make v-sekai more robust.\n\n\nNegative Consequences\nWe cannot get other features in.\n\n\nOption graveyard\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nThis is a cicd change and is able scripting the github actions.\n\n\nIs there a reason why this should be core and done by us?\nWe manage cicd.\n\n\nReferences\n\nV-Sekai\nhttps://martinfowler.com/bliki/PendingHead.html"
+    "text": "The task at hand is to create a Godot Engine demo within a span of one week."
   },
   {
-    "objectID": "decisions/20240409-crud-godot-tiles.html",
-    "href": "decisions/20240409-crud-godot-tiles.html",
-    "title": "Accepted: “Sunny Park” Test Case for 3D Tile Sync",
+    "objectID": "decisions/20240127-urban-explorer-gdc-2024-sample.html#the-strategy",
+    "href": "decisions/20240127-urban-explorer-gdc-2024-sample.html#the-strategy",
+    "title": "Proposed: Urban Navigator: The City Unveiled",
     "section": "",
-    "text": "This test case aims to utilize a specific database technology, sqlite-fdb, to assess the efficiency and accuracy of syncing 3D tiles between Blender and Godot. The test will involve basic CRUD operations on a set of 3D tiles representing a park.\n\n\n\n\n3D Tiles: These include Grass, Pathway, Bench, Tree, Pond.\nTools: The tools used in this process are Blender (for creation/editing), Godot Engine (for scene assembly), and Database (for syncing).\n\n\n\n\n\nCreate (Blender): Design 5 different 3D park tiles and store their data in the database.\nRead (Godot): Import the tiles from the database into Godot and assemble the “Sunny Park.”\nUpdate (Blender): Modify a tile (e.g., change the color of the bench), update the database, and verify the update in Godot.\nDelete (Blender): Remove a tile (e.g., pond), delete it from the database, and confirm its removal in Godot.\n\n\n\n\n\nSynchronization Accuracy: Ensure that changes made in Blender are accurately reflected in Godot.\nPerformance: Measure the time taken for sync operations.\nEase of Use: Evaluate the complexity of the sync steps.\nError Handling: Check how the system responds to errors such as missing data."
+    "text": "The proposed idea is “Urban Navigator: The City Unveiled”. Embark on an exploratory journey through the heart of a city. Unravel the secrets of a sprawling metropolis where every street corner has a story to tell. With the help of advanced motion matching technology, your gamepad inputs are transformed into lifelike movements, enabling seamless interaction with the city."
   },
   {
-    "objectID": "decisions/20240409-crud-godot-tiles.html#objective",
-    "href": "decisions/20240409-crud-godot-tiles.html#objective",
-    "title": "Accepted: “Sunny Park” Test Case for 3D Tile Sync",
+    "objectID": "decisions/20240127-urban-explorer-gdc-2024-sample.html#the-upside",
+    "href": "decisions/20240127-urban-explorer-gdc-2024-sample.html#the-upside",
+    "title": "Proposed: Urban Navigator: The City Unveiled",
     "section": "",
-    "text": "This test case aims to utilize a specific database technology, sqlite-fdb, to assess the efficiency and accuracy of syncing 3D tiles between Blender and Godot. The test will involve basic CRUD operations on a set of 3D tiles representing a park."
+    "text": "The project will demonstrate the power and flexibility of the Godot Engine, potentially attracting more developers to use it. It also provides an opportunity to innovate in the field of urban exploration games."
   },
   {
-    "objectID": "decisions/20240409-crud-godot-tiles.html#components",
-    "href": "decisions/20240409-crud-godot-tiles.html#components",
-    "title": "Accepted: “Sunny Park” Test Case for 3D Tile Sync",
+    "objectID": "decisions/20240127-urban-explorer-gdc-2024-sample.html#the-downside",
+    "href": "decisions/20240127-urban-explorer-gdc-2024-sample.html#the-downside",
+    "title": "Proposed: Urban Navigator: The City Unveiled",
     "section": "",
-    "text": "3D Tiles: These include Grass, Pathway, Bench, Tree, Pond.\nTools: The tools used in this process are Blender (for creation/editing), Godot Engine (for scene assembly), and Database (for syncing)."
+    "text": "The tight timeline could lead to compromises in quality or scope. There’s also a risk that the final product may not fully meet the expectations set by the proposal."
   },
   {
-    "objectID": "decisions/20240409-crud-godot-tiles.html#steps",
-    "href": "decisions/20240409-crud-godot-tiles.html#steps",
-    "title": "Accepted: “Sunny Park” Test Case for 3D Tile Sync",
+    "objectID": "decisions/20240127-urban-explorer-gdc-2024-sample.html#the-road-not-taken",
+    "href": "decisions/20240127-urban-explorer-gdc-2024-sample.html#the-road-not-taken",
+    "title": "Proposed: Urban Navigator: The City Unveiled",
     "section": "",
-    "text": "Create (Blender): Design 5 different 3D park tiles and store their data in the database.\nRead (Godot): Import the tiles from the database into Godot and assemble the “Sunny Park.”\nUpdate (Blender): Modify a tile (e.g., change the color of the bench), update the database, and verify the update in Godot.\nDelete (Blender): Remove a tile (e.g., pond), delete it from the database, and confirm its removal in Godot."
+    "text": "An alternative approach could have been to focus on a different genre or type of game that might be less complex but still showcases the capabilities of the Godot Engine."
   },
   {
-    "objectID": "decisions/20240409-crud-godot-tiles.html#evaluation-criteria",
-    "href": "decisions/20240409-crud-godot-tiles.html#evaluation-criteria",
-    "title": "Accepted: “Sunny Park” Test Case for 3D Tile Sync",
+    "objectID": "decisions/20240127-urban-explorer-gdc-2024-sample.html#the-infrequent-use-case",
+    "href": "decisions/20240127-urban-explorer-gdc-2024-sample.html#the-infrequent-use-case",
+    "title": "Proposed: Urban Navigator: The City Unveiled",
     "section": "",
-    "text": "Synchronization Accuracy: Ensure that changes made in Blender are accurately reflected in Godot.\nPerformance: Measure the time taken for sync operations.\nEase of Use: Evaluate the complexity of the sync steps.\nError Handling: Check how the system responds to errors such as missing data."
+    "text": "While the primary use case is for the Game Developer Conference demo, the developed game could also be used as a benchmarking tool for testing hardware performance with the Godot Engine."
   },
   {
-    "objectID": "decisions/20240409-crud-godot-tiles.html#context",
-    "href": "decisions/20240409-crud-godot-tiles.html#context",
-    "title": "Accepted: “Sunny Park” Test Case for 3D Tile Sync",
-    "section": "Context",
-    "text": "Context\nThis proposal arises from the need for an efficient and accurate synchronization of 3D tiles between Blender and Godot Engine."
+    "objectID": "decisions/20240127-urban-explorer-gdc-2024-sample.html#in-core-and-done-by-us",
+    "href": "decisions/20240127-urban-explorer-gdc-2024-sample.html#in-core-and-done-by-us",
+    "title": "Proposed: Urban Navigator: The City Unveiled",
+    "section": "",
+    "text": "Yes, this project is core to our mission of showcasing the capabilities of the Godot Engine and can be done by our team."
   },
   {
-    "objectID": "decisions/20240409-crud-godot-tiles.html#problem-statement",
-    "href": "decisions/20240409-crud-godot-tiles.html#problem-statement",
-    "title": "Accepted: “Sunny Park” Test Case for 3D Tile Sync",
-    "section": "Problem Statement",
-    "text": "Problem Statement\nThe problem is determining whether SQLite-fdb would be faster for syncing 3D tiles from Blender to Godot engine compared to multi raft or cockroachdb."
+    "objectID": "decisions/20240127-urban-explorer-gdc-2024-sample.html#further-reading",
+    "href": "decisions/20240127-urban-explorer-gdc-2024-sample.html#further-reading",
+    "title": "Proposed: Urban Navigator: The City Unveiled",
+    "section": "",
+    "text": "V-Sekai · GitHub - This is the official GitHub account for the V-Sekai development community which focuses on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - This is the GitHub page for the V-Sekai open-source project that brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis article was assisted by AI assistant Aria."
   },
   {
-    "objectID": "decisions/20240409-crud-godot-tiles.html#benefits",
-    "href": "decisions/20240409-crud-godot-tiles.html#benefits",
-    "title": "Accepted: “Sunny Park” Test Case for 3D Tile Sync",
-    "section": "Benefits",
-    "text": "Benefits\nThe benefits of this proposal include improved performance, ease of use, and error handling in the synchronization process."
+    "objectID": "decisions/20230429-improve-collab.html",
+    "href": "decisions/20230429-improve-collab.html",
+    "title": "Proposed: Improve the collaboration process and attract more contributors to work on the project",
+    "section": "",
+    "text": "Proposed: Improve the collaboration process and attract more contributors to work on the project\n\nMetadata\n\nStatus: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,Roadmap,Collaboration,chatgpt4 summary,\n\n\n\nContext and Problem Statement\nThe V-Sekai project has an extensive roadmap with short-term, mid-term, and long-term goals, but it lacks a project manager and struggles to find collaborators who share the vision and can dedicate enough time to contribute. How can we improve the collaboration process and attract more contributors to work on the project more effectively?\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nThe proposed option to overcome the limitation of attracting more contributors and improving collaboration is to develop clear and concise project documentation, including a visual roadmap using mermaid.js, and establish a transparent contribution process. This will provide a structured environment for new and existing contributors to collaborate and understand the project’s goals and priorities.\n\nHow it helps to overcome the problem or limitation\n\nA well-organized project documentation and visual roadmap will help potential contributors understand the project’s scope and vision, allowing them to make informed decisions about contributing.\nA transparent contribution process will facilitate collaboration by providing guidelines, resources, and communication channels for contributors.\nOnboarding new contributors with tutorials and mentorship will help them quickly become productive and dedicated team members.\nRegular meetings and progress updates will keep the team motivated and focused on achieving milestones.\nRecognizing and rewarding contributors will foster a sense of community and commitment, making it more likely that they continue contributing to the project.\n\nWith these measures in place, the V-Sekai project will overcome its current limitations, making it easier for the team to work together and attract new contributors.\n\n\n\nDescribe how your proposal will work with code, pseudo-code, mock-ups, or diagrams\nDevelop a clear and concise project documentation that outlines the project’s goals, requirements, and milestones. Establish a transparent and structured contribution process, including:\n\nCreate a centralized repository for documentation, code, and assets, with clear guidelines for contributing.\nDevelop a project roadmap with prioritized tasks, deadlines, and assigned responsibilities.\nImplement an onboarding process for new contributors, including tutorials, resources, and mentorship.\nOrganize regular meetings and communication channels for updates, progress reports, and collaboration.\nRecognize and reward contributors for their work, fostering a sense of community and commitment.\n\n\n\nPositive Consequences\n\nImproved collaboration and communication among the team\nAttracting more contributors with diverse skill sets\nFaster progress towards project milestones\nClear understanding of project goals and priorities\n\n\n\nNegative Consequences\n\nIncreased management and coordination overhead\nPotential for disagreements on priorities and approaches\n\n\n\nOption graveyard\n\nRelying on informal communication and ad-hoc collaboration\nContinuing with the current approach without a structured process\n\n\n\nIf this enhancement will be used infrequently, can it be worked around with a few lines of script?\nWhile it may be possible to work around some aspects of the problem with a few lines of script, it would not address the underlying issues of attracting and retaining contributors or improving collaboration. The proposed solution aims to create a more sustainable and efficient environment for the V-Sekai project, which cannot be achieved with a temporary workaround or a simple script.\n\n\nIs there a reason why this should be core and done by us?\nAs the primary developers of the project, the V-Sekai team has the best understanding of the project’s goals, objectives, and priorities. Implementing this feature in-house will ensure that the solution aligns well with the project’s vision and addresses the specific needs of the project.\n\n\nReferences\n\nV-Sekai\nV-Sekai Roadmap and Goals\nV-Sekai Team Discussions and Updates\nMermaid.js"
   },
   {
-    "objectID": "decisions/20240409-crud-godot-tiles.html#downsides",
-    "href": "decisions/20240409-crud-godot-tiles.html#downsides",
-    "title": "Accepted: “Sunny Park” Test Case for 3D Tile Sync",
-    "section": "Downsides",
-    "text": "Downsides\nPotential downsides may include increased complexity and potential for errors during synchronization."
+    "objectID": "decisions/20211031-have-wires-in-3d.html",
+    "href": "decisions/20211031-have-wires-in-3d.html",
+    "title": "Proposed: Have wires in 3d",
+    "section": "",
+    "text": "Proposed: Have wires in 3d\n\nContext and Problem Statement\nHave wires in 3d to simulate connections\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nVertlet Rope wires\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nVertlet Rope wires project\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nIs a few hundred lines of gdscript\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nporting is easy by me\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240409-crud-godot-tiles.html#road-not-taken",
-    "href": "decisions/20240409-crud-godot-tiles.html#road-not-taken",
-    "title": "Accepted: “Sunny Park” Test Case for 3D Tile Sync",
-    "section": "Road Not Taken",
-    "text": "Road Not Taken\nThis proposal did not consider other database technologies that could be used for synchronization."
+    "objectID": "decisions/20240502-gltf-fbx-tscn-vrm.html",
+    "href": "decisions/20240502-gltf-fbx-tscn-vrm.html",
+    "title": "Proposed: Workflows for 3D Model Conversion",
+    "section": "",
+    "text": "In the realm of 3D modeling and animation, there are numerous file formats each with their own unique features and capabilities. However, not all software can support every format, leading to a need for conversion tools.\n\n\n\nThe challenge lies in creating a tool that can convert between different 3D model formats, specifically from glTF to FBX, while maintaining the integrity of the original model.\n\n\n\nWe propose to develop a workflow for 3D model conversion using the Elixir Membrane Framework.\nThe primary function of this tool would be to take a glTF file as input and export it as an FBX file. This tool could also potentially support other formats such as USD, Godot Engine tscn, and VRM.\nAdditionally, we propose a feature where the tool can take a post and return a result. This could be useful for batch processing or automated tasks.\nTo make these services accessible, we plan to expose them via a Tailscale funnel.\nFor many of the flows, we can use USD to glTF, then glTF to Godot Engine, and finally Godot Engine to VRM and back. This approach allows us to leverage existing conversion libraries and tools, reducing the amount of custom code we need to write.\ngraph LR\n    A[USD] --&gt; B[glTF]\n    B --&gt; C[Godot Engine]\n    C --&gt; D[VRM]\n    D --&gt; B\n\n\n\nThis tool would greatly simplify the process of converting 3D models between different formats, saving time and reducing potential errors.\n\n\n\nThere may be some loss of data or quality during the conversion process, depending on the complexity of the model and the capabilities of the target format.\n\n\n\nAlternative solutions could involve using existing conversion tools or plugins, but these may not offer the same level of control or flexibility as a custom-built tool.\n\n\n\nWhile the primary use case is for converting glTF to FBX, the tool could also be used for other less common conversions.\n\n\n\nThis tool would be developed in-house by the V-Sekai development team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240409-crud-godot-tiles.html#infrequent-use-case",
-    "href": "decisions/20240409-crud-godot-tiles.html#infrequent-use-case",
-    "title": "Accepted: “Sunny Park” Test Case for 3D Tile Sync",
-    "section": "Infrequent Use Case",
-    "text": "Infrequent Use Case\nThis proposal may not apply to projects that do not require frequent synchronization of 3D tiles between Blender and Godot Engine."
+    "objectID": "decisions/20240502-gltf-fbx-tscn-vrm.html#the-context",
+    "href": "decisions/20240502-gltf-fbx-tscn-vrm.html#the-context",
+    "title": "Proposed: Workflows for 3D Model Conversion",
+    "section": "",
+    "text": "In the realm of 3D modeling and animation, there are numerous file formats each with their own unique features and capabilities. However, not all software can support every format, leading to a need for conversion tools."
   },
   {
-    "objectID": "decisions/20240409-crud-godot-tiles.html#in-core-and-done-by-us",
-    "href": "decisions/20240409-crud-godot-tiles.html#in-core-and-done-by-us",
-    "title": "Accepted: “Sunny Park” Test Case for 3D Tile Sync",
-    "section": "In Core and Done by Us",
-    "text": "In Core and Done by Us\nThe V-Sekai development team will be responsible for implementing this proposal."
+    "objectID": "decisions/20240502-gltf-fbx-tscn-vrm.html#the-problem-statement",
+    "href": "decisions/20240502-gltf-fbx-tscn-vrm.html#the-problem-statement",
+    "title": "Proposed: Workflows for 3D Model Conversion",
+    "section": "",
+    "text": "The challenge lies in creating a tool that can convert between different 3D model formats, specifically from glTF to FBX, while maintaining the integrity of the original model."
   },
   {
-    "objectID": "decisions/20240409-crud-godot-tiles.html#status",
-    "href": "decisions/20240409-crud-godot-tiles.html#status",
-    "title": "Accepted: “Sunny Park” Test Case for 3D Tile Sync",
-    "section": "Status",
-    "text": "Status\nStatus: Accepted"
+    "objectID": "decisions/20240502-gltf-fbx-tscn-vrm.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240502-gltf-fbx-tscn-vrm.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Workflows for 3D Model Conversion",
+    "section": "",
+    "text": "We propose to develop a workflow for 3D model conversion using the Elixir Membrane Framework.\nThe primary function of this tool would be to take a glTF file as input and export it as an FBX file. This tool could also potentially support other formats such as USD, Godot Engine tscn, and VRM.\nAdditionally, we propose a feature where the tool can take a post and return a result. This could be useful for batch processing or automated tasks.\nTo make these services accessible, we plan to expose them via a Tailscale funnel.\nFor many of the flows, we can use USD to glTF, then glTF to Godot Engine, and finally Godot Engine to VRM and back. This approach allows us to leverage existing conversion libraries and tools, reducing the amount of custom code we need to write.\ngraph LR\n    A[USD] --&gt; B[glTF]\n    B --&gt; C[Godot Engine]\n    C --&gt; D[VRM]\n    D --&gt; B"
   },
   {
-    "objectID": "decisions/20240409-crud-godot-tiles.html#decision-makers",
-    "href": "decisions/20240409-crud-godot-tiles.html#decision-makers",
-    "title": "Accepted: “Sunny Park” Test Case for 3D Tile Sync",
-    "section": "Decision Makers",
-    "text": "Decision Makers\n\nV-Sekai development team"
+    "objectID": "decisions/20240502-gltf-fbx-tscn-vrm.html#the-benefits",
+    "href": "decisions/20240502-gltf-fbx-tscn-vrm.html#the-benefits",
+    "title": "Proposed: Workflows for 3D Model Conversion",
+    "section": "",
+    "text": "This tool would greatly simplify the process of converting 3D models between different formats, saving time and reducing potential errors."
   },
   {
-    "objectID": "decisions/20240409-crud-godot-tiles.html#tags",
-    "href": "decisions/20240409-crud-godot-tiles.html#tags",
-    "title": "Accepted: “Sunny Park” Test Case for 3D Tile Sync",
-    "section": "Tags",
-    "text": "Tags\n\nV-Sekai"
+    "objectID": "decisions/20240502-gltf-fbx-tscn-vrm.html#the-downsides",
+    "href": "decisions/20240502-gltf-fbx-tscn-vrm.html#the-downsides",
+    "title": "Proposed: Workflows for 3D Model Conversion",
+    "section": "",
+    "text": "There may be some loss of data or quality during the conversion process, depending on the complexity of the model and the capabilities of the target format."
   },
   {
-    "objectID": "decisions/20240409-crud-godot-tiles.html#further-reading",
-    "href": "decisions/20240409-crud-godot-tiles.html#further-reading",
-    "title": "Accepted: “Sunny Park” Test Case for 3D Tile Sync",
-    "section": "Further Reading",
-    "text": "Further Reading\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nEfficient_Methods_for_Improving_Scalability_and_Playability_of_Massively_Multiplayer_Online_Game_MMOG by Prasetya, Kusno\nlawnjelly’s spergler algorithm for splitting meshes\nlibgodot.\n\nAI assistant Aria assisted with this article."
+    "objectID": "decisions/20240502-gltf-fbx-tscn-vrm.html#the-road-not-taken",
+    "href": "decisions/20240502-gltf-fbx-tscn-vrm.html#the-road-not-taken",
+    "title": "Proposed: Workflows for 3D Model Conversion",
+    "section": "",
+    "text": "Alternative solutions could involve using existing conversion tools or plugins, but these may not offer the same level of control or flexibility as a custom-built tool."
   },
   {
-    "objectID": "decisions/20240705-rpg_town.html",
-    "href": "decisions/20240705-rpg_town.html",
-    "title": "Proposal: RPG Town in V-Sekai",
+    "objectID": "decisions/20240502-gltf-fbx-tscn-vrm.html#the-infrequent-use-case",
+    "href": "decisions/20240502-gltf-fbx-tscn-vrm.html#the-infrequent-use-case",
+    "title": "Proposed: Workflows for 3D Model Conversion",
     "section": "",
-    "text": "Researchers have been studying emergent AI behaviors in sandbox environments inspired by games like The Sims. This proposal aims to leverage these insights to enhance the V-Sekai game, which features 25 NPCs running goal-task hierarchical task network (GT-HTN).\n\n\n\nThe challenge is to create a dynamic and engaging environment where NPCs exhibit complex behaviors that can be streamed 24/7. The goal is to make the game interesting enough for Twitch streaming while ensuring the NPCs’ actions are meaningful and not just random clicks.\n\n\n\nFor HTN implementation, we will study the GOAP framework from Vinicius Gerevini’s GitHub and define tasks and goals for NPCs using predicate, subject-object triplet variables, or method calls. Networking and traffic simulation will involve implementing network traffic tests to ensure smooth operation and using tools like Microsoft’s GraphRAG for generating predicate and subject objects. For LLM integration, we will integrate Large Language Models (LLMs) to set goals for NPCs based on Twitch chat summaries, using LLMs to help plan but not directly control NPC actions.\n\n\nNPC Interaction Flow:\ngraph TD;\n    A[Start] --&gt; B[Define Goals];\n    B --&gt; C[Assign Tasks];\n    C --&gt; D[Execute Actions];\n    D --&gt; E[Monitor and Adjust];\n    E --&gt; F[Stream to Twitch];\nSystem Architecture:\ngraph LR;\n    A[User Input] --&gt; B[LLM];\n    B --&gt; C[Goal Setting];\n    C --&gt; D[GTHTN Engine];\n    D --&gt; E[NPC Actions];\n    E --&gt; F[Twitch Stream];\n\n\n\n\nCreating an interactive and dynamic environment suitable for Twitch streaming will result in engaging content. It allows for complex and unpredictable NPC interactions, fostering emergent behaviors. Additionally, it engages the community by summarizing Twitch chat to set NPC goals.\n\n\n\nImplementing and maintaining such a system can be challenging due to its complexity. It also requires significant computational resources for real-time processing and streaming.\n\n\n\nManually setting NPC goals and actions would be less dynamic and engaging. Using simpler AI models may not exhibit complex behaviors.\n\n\n\nRunning the game without Twitch integration, focusing solely on NPC interactions, represents an infrequent use case.\n\n\n\nWe will implement the GOAP framework within the V-Sekai game and integrate LLMs for goal setting based on community input.\n\n\n\nStatus: Proposed \n\n\n\nThe decision makers for this proposal are the V-Sekai development team.\n\n\n\nV-Sekai\n\n\n\nFor more information, you can visit the V-Sekai GitHub account, which focuses on social VR functionality for the Godot Engine. You can also check out the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nAI assistant Aria assisted with this article."
+    "text": "While the primary use case is for converting glTF to FBX, the tool could also be used for other less common conversions."
   },
   {
-    "objectID": "decisions/20240705-rpg_town.html#the-context",
-    "href": "decisions/20240705-rpg_town.html#the-context",
-    "title": "Proposal: RPG Town in V-Sekai",
+    "objectID": "decisions/20240502-gltf-fbx-tscn-vrm.html#in-core-and-done-by-us",
+    "href": "decisions/20240502-gltf-fbx-tscn-vrm.html#in-core-and-done-by-us",
+    "title": "Proposed: Workflows for 3D Model Conversion",
     "section": "",
-    "text": "Researchers have been studying emergent AI behaviors in sandbox environments inspired by games like The Sims. This proposal aims to leverage these insights to enhance the V-Sekai game, which features 25 NPCs running goal-task hierarchical task network (GT-HTN)."
+    "text": "This tool would be developed in-house by the V-Sekai development team."
   },
   {
-    "objectID": "decisions/20240705-rpg_town.html#the-problem-statement",
-    "href": "decisions/20240705-rpg_town.html#the-problem-statement",
-    "title": "Proposal: RPG Town in V-Sekai",
+    "objectID": "decisions/20240502-gltf-fbx-tscn-vrm.html#status",
+    "href": "decisions/20240502-gltf-fbx-tscn-vrm.html#status",
+    "title": "Proposed: Workflows for 3D Model Conversion",
     "section": "",
-    "text": "The challenge is to create a dynamic and engaging environment where NPCs exhibit complex behaviors that can be streamed 24/7. The goal is to make the game interesting enough for Twitch streaming while ensuring the NPCs’ actions are meaningful and not just random clicks."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20240705-rpg_town.html#describe-how-your-proposal-will-work",
-    "href": "decisions/20240705-rpg_town.html#describe-how-your-proposal-will-work",
-    "title": "Proposal: RPG Town in V-Sekai",
+    "objectID": "decisions/20240502-gltf-fbx-tscn-vrm.html#decision-makers",
+    "href": "decisions/20240502-gltf-fbx-tscn-vrm.html#decision-makers",
+    "title": "Proposed: Workflows for 3D Model Conversion",
     "section": "",
-    "text": "For HTN implementation, we will study the GOAP framework from Vinicius Gerevini’s GitHub and define tasks and goals for NPCs using predicate, subject-object triplet variables, or method calls. Networking and traffic simulation will involve implementing network traffic tests to ensure smooth operation and using tools like Microsoft’s GraphRAG for generating predicate and subject objects. For LLM integration, we will integrate Large Language Models (LLMs) to set goals for NPCs based on Twitch chat summaries, using LLMs to help plan but not directly control NPC actions.\n\n\nNPC Interaction Flow:\ngraph TD;\n    A[Start] --&gt; B[Define Goals];\n    B --&gt; C[Assign Tasks];\n    C --&gt; D[Execute Actions];\n    D --&gt; E[Monitor and Adjust];\n    E --&gt; F[Stream to Twitch];\nSystem Architecture:\ngraph LR;\n    A[User Input] --&gt; B[LLM];\n    B --&gt; C[Goal Setting];\n    C --&gt; D[GTHTN Engine];\n    D --&gt; E[NPC Actions];\n    E --&gt; F[Twitch Stream];"
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20240705-rpg_town.html#the-benefits",
-    "href": "decisions/20240705-rpg_town.html#the-benefits",
-    "title": "Proposal: RPG Town in V-Sekai",
+    "objectID": "decisions/20240502-gltf-fbx-tscn-vrm.html#tags",
+    "href": "decisions/20240502-gltf-fbx-tscn-vrm.html#tags",
+    "title": "Proposed: Workflows for 3D Model Conversion",
     "section": "",
-    "text": "Creating an interactive and dynamic environment suitable for Twitch streaming will result in engaging content. It allows for complex and unpredictable NPC interactions, fostering emergent behaviors. Additionally, it engages the community by summarizing Twitch chat to set NPC goals."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20240705-rpg_town.html#the-downsides",
-    "href": "decisions/20240705-rpg_town.html#the-downsides",
-    "title": "Proposal: RPG Town in V-Sekai",
+    "objectID": "decisions/20240502-gltf-fbx-tscn-vrm.html#further-reading",
+    "href": "decisions/20240502-gltf-fbx-tscn-vrm.html#further-reading",
+    "title": "Proposed: Workflows for 3D Model Conversion",
     "section": "",
-    "text": "Implementing and maintaining such a system can be challenging due to its complexity. It also requires significant computational resources for real-time processing and streaming."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240705-rpg_town.html#the-road-not-taken",
-    "href": "decisions/20240705-rpg_town.html#the-road-not-taken",
-    "title": "Proposal: RPG Town in V-Sekai",
+    "objectID": "decisions/20220531-truenas-scale.html",
+    "href": "decisions/20220531-truenas-scale.html",
+    "title": "Rejected: To create a deployment kit use truescale to host gocd agents for cicd.",
     "section": "",
-    "text": "Manually setting NPC goals and actions would be less dynamic and engaging. Using simpler AI models may not exhibit complex behaviors."
+    "text": "proposed\ndraft\nrejected\naccepted\ndeprecated\nsuperseded by\n\n\n\n\nV-Sekai,fire,\n\n\n\nV-Sekai,\n\n\n\nI want to run docker containers in a semi production way.\n\n\n\nUse truenas scale to host gocd agents for cicd.\n\n\n\nAdd a new storage node from hosts.\n\n\n\n\ninstall truenas scale\ninstall truenas charts\nLaunch docker image\nimage: groupsinfra/gocd-agent-centos-8-groups\ntag: v20.7.0-groups-0.5.3\nAdd environment variables\nGO_SERVER_URL=“https://ci.v-sekai.cloud/go/”\nAdd host volumes for\n/go\n/mnt/homego # On truenas\n\n\n\n\n\n??? Enable the agent\n??? Add the environment to the agent\n??? Add the agent to the environment.\n\n\n\nCan deploy this setup to digital ocean.\n\n\n\nNo response\n\n\n\nNo response\n\n\n\nNot a few lines script.\n\n\n\nI know how to do this and I don’t want to pay for it.\n\n\n\n\nV-Sekai\nagent_auto_register\n\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240705-rpg_town.html#the-infrequent-use-case",
-    "href": "decisions/20240705-rpg_town.html#the-infrequent-use-case",
-    "title": "Proposal: RPG Town in V-Sekai",
+    "objectID": "decisions/20220531-truenas-scale.html#truenas-scale",
+    "href": "decisions/20220531-truenas-scale.html#truenas-scale",
+    "title": "Rejected: To create a deployment kit use truescale to host gocd agents for cicd.",
     "section": "",
-    "text": "Running the game without Twitch integration, focusing solely on NPC interactions, represents an infrequent use case."
+    "text": "install truenas scale\ninstall truenas charts\nLaunch docker image\nimage: groupsinfra/gocd-agent-centos-8-groups\ntag: v20.7.0-groups-0.5.3\nAdd environment variables\nGO_SERVER_URL=“https://ci.v-sekai.cloud/go/”\nAdd host volumes for\n/go\n/mnt/homego # On truenas"
   },
   {
-    "objectID": "decisions/20240705-rpg_town.html#in-core-and-done-by-us",
-    "href": "decisions/20240705-rpg_town.html#in-core-and-done-by-us",
-    "title": "Proposal: RPG Town in V-Sekai",
+    "objectID": "decisions/20220531-truenas-scale.html#gocd-config",
+    "href": "decisions/20220531-truenas-scale.html#gocd-config",
+    "title": "Rejected: To create a deployment kit use truescale to host gocd agents for cicd.",
     "section": "",
-    "text": "We will implement the GOAP framework within the V-Sekai game and integrate LLMs for goal setting based on community input."
+    "text": "??? Enable the agent\n??? Add the environment to the agent\n??? Add the agent to the environment.\n\n\n\nCan deploy this setup to digital ocean.\n\n\n\nNo response\n\n\n\nNo response\n\n\n\nNot a few lines script.\n\n\n\nI know how to do this and I don’t want to pay for it.\n\n\n\n\nV-Sekai\nagent_auto_register\n\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240705-rpg_town.html#status",
-    "href": "decisions/20240705-rpg_town.html#status",
-    "title": "Proposal: RPG Town in V-Sekai",
+    "objectID": "decisions/20230505-polygon-mesh-based-sculpting-tools.html",
+    "href": "decisions/20230505-polygon-mesh-based-sculpting-tools.html",
+    "title": "Proposed: VR design application for V-Sekai",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "Status: proposed \nDeciders: V-Sekai,fire,\nTags: V-Sekai,ChatGPT-4,\n\n\n\n\nFind or create a VR design application offering a variety of powerful polygon mesh-based sculpting tools, suitable for both aspiring creatives and experienced 3D artists.\n\n\n\nCurrently, V-Sekai lacks a comprehensive VR design application that provides polygon mesh-based sculpting tools for users with varying levels of experience. How can we integrate such a tool to enhance the creative capabilities of our users?\n\n\n\nIntegrate a powerful VR design application, such as Gravity Sketch, which offers a wide range of polygon mesh-based sculpting tools. This will cater to both beginners and experienced 3D artists, allowing them to create intricate designs within the V-Sekai environment.\n\n\n\n\nResearch available VR design applications that meet the requirements.\nEvaluate the compatibility of the chosen application with V-Sekai.\nDevelop an integration plan, including necessary API calls and user interface adjustments.\nImplement the integration, ensuring seamless functionality within V-Sekai.\nTest the integrated application with various user profiles to ensure usability and performance.\n\n\n\n\n\nEnhanced creative capabilities for V-Sekai users.\nAttraction of a wider user base, including experienced 3D artists.\nImproved user satisfaction and engagement.\n\n\n\n\n\nPotential increase in system requirements for V-Sekai.\nAdditional development time and resources required for integration.\n\n\n\n\n\nDeveloping a custom VR design application from scratch (time-consuming and resource-intensive).\n\n\n\n\nNo, as the enhancement involves integrating a complex VR design application that cannot be achieved through a simple script workaround.\n\n\n\nYes, integrating a powerful VR design application will significantly enhance the creative capabilities of V-Sekai users, making it a core feature that directly impacts user experience and satisfaction.\n\n\n\n\nV-Sekai\nCassie on Github: https://github.com/V-Sekai/cassie\nShapelab by Leopoly on Steam\nGravity Sketch on Steam\nSubstance 3D Modeler 2023 on Steam: https://store.steampowered.com/app/1745780/Substance_3D_Modeler_2023/"
   },
   {
-    "objectID": "decisions/20240705-rpg_town.html#decision-makers",
-    "href": "decisions/20240705-rpg_town.html#decision-makers",
-    "title": "Proposal: RPG Town in V-Sekai",
+    "objectID": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#metadata",
+    "href": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#metadata",
+    "title": "Proposed: VR design application for V-Sekai",
     "section": "",
-    "text": "The decision makers for this proposal are the V-Sekai development team."
+    "text": "Status: proposed \nDeciders: V-Sekai,fire,\nTags: V-Sekai,ChatGPT-4,"
   },
   {
-    "objectID": "decisions/20240705-rpg_town.html#tags",
-    "href": "decisions/20240705-rpg_town.html#tags",
-    "title": "Proposal: RPG Town in V-Sekai",
+    "objectID": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#context-and-problem-statement",
+    "href": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#context-and-problem-statement",
+    "title": "Proposed: VR design application for V-Sekai",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Find or create a VR design application offering a variety of powerful polygon mesh-based sculpting tools, suitable for both aspiring creatives and experienced 3D artists."
   },
   {
-    "objectID": "decisions/20240705-rpg_town.html#further-reading",
-    "href": "decisions/20240705-rpg_town.html#further-reading",
-    "title": "Proposal: RPG Town in V-Sekai",
+    "objectID": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#describe-the-problem-or-limitation-you-have-in-your-project-e.g.-in-free-form-using-two-to-three-sentences.-consider-articulating-the-case-in-the-form-of-a-question.",
+    "href": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#describe-the-problem-or-limitation-you-have-in-your-project-e.g.-in-free-form-using-two-to-three-sentences.-consider-articulating-the-case-in-the-form-of-a-question.",
+    "title": "Proposed: VR design application for V-Sekai",
     "section": "",
-    "text": "For more information, you can visit the V-Sekai GitHub account, which focuses on social VR functionality for the Godot Engine. You can also check out the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nAI assistant Aria assisted with this article."
+    "text": "Currently, V-Sekai lacks a comprehensive VR design application that provides polygon mesh-based sculpting tools for users with varying levels of experience. How can we integrate such a tool to enhance the creative capabilities of our users?"
   },
   {
-    "objectID": "decisions/20240406-web-based-explore.html",
-    "href": "decisions/20240406-web-based-explore.html",
-    "title": "Proposed: Web-Based Exploration of V-Sekai",
+    "objectID": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: VR design application for V-Sekai",
     "section": "",
-    "text": "Recently, a discussion arose regarding the potential for creating a web version of V-Sekai. The concept involves utilizing WebAssembly (wasm) for this endeavor. Additionally, there is interest in integrating WebRTC with both native and web platforms.\n\n\n\nThe current iteration of V-Sekai lacks web accessibility, limiting its reach and usability. Furthermore, challenges exist concerning shared array buffer accessibility on Safari and access to ad networks, both of which are vital for online games.\n\n\n\nWe propose to construct a web version of V-Sekai using wasm. This process will necessitate overcoming the shared array buffer accessibility issue on Safari and ensuring access to ad networks.\n\n\n\n\nEnhanced accessibility and reach for V-Sekai.\nImproved user experience by allowing access from any device equipped with a web browser.\nPotential revenue increase through ad networks.\n\n\n\n\n\nPotential performance issues due to operation on a web platform.\nPossible compatibility issues across different browsers.\n\n\n\n\nAn alternative approach would be maintaining an exclusive focus on the native platform. However, this would restrict V-Sekai’s reach and potential for growth.\n\n\n\nThis proposal will significantly benefit users who prefer or only have access to the web platform.\n\n\n\nThe V-Sekai development team will undertake this project.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
+    "text": "Integrate a powerful VR design application, such as Gravity Sketch, which offers a wide range of polygon mesh-based sculpting tools. This will cater to both beginners and experienced 3D artists, allowing them to create intricate designs within the V-Sekai environment."
   },
   {
-    "objectID": "decisions/20240406-web-based-explore.html#context",
-    "href": "decisions/20240406-web-based-explore.html#context",
-    "title": "Proposed: Web-Based Exploration of V-Sekai",
+    "objectID": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: VR design application for V-Sekai",
     "section": "",
-    "text": "Recently, a discussion arose regarding the potential for creating a web version of V-Sekai. The concept involves utilizing WebAssembly (wasm) for this endeavor. Additionally, there is interest in integrating WebRTC with both native and web platforms."
+    "text": "Research available VR design applications that meet the requirements.\nEvaluate the compatibility of the chosen application with V-Sekai.\nDevelop an integration plan, including necessary API calls and user interface adjustments.\nImplement the integration, ensuring seamless functionality within V-Sekai.\nTest the integrated application with various user profiles to ensure usability and performance."
   },
   {
-    "objectID": "decisions/20240406-web-based-explore.html#problem-statement",
-    "href": "decisions/20240406-web-based-explore.html#problem-statement",
-    "title": "Proposed: Web-Based Exploration of V-Sekai",
+    "objectID": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#positive-consequences",
+    "href": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#positive-consequences",
+    "title": "Proposed: VR design application for V-Sekai",
     "section": "",
-    "text": "The current iteration of V-Sekai lacks web accessibility, limiting its reach and usability. Furthermore, challenges exist concerning shared array buffer accessibility on Safari and access to ad networks, both of which are vital for online games."
+    "text": "Enhanced creative capabilities for V-Sekai users.\nAttraction of a wider user base, including experienced 3D artists.\nImproved user satisfaction and engagement."
   },
   {
-    "objectID": "decisions/20240406-web-based-explore.html#proposal",
-    "href": "decisions/20240406-web-based-explore.html#proposal",
-    "title": "Proposed: Web-Based Exploration of V-Sekai",
+    "objectID": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#negative-consequences",
+    "href": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#negative-consequences",
+    "title": "Proposed: VR design application for V-Sekai",
     "section": "",
-    "text": "We propose to construct a web version of V-Sekai using wasm. This process will necessitate overcoming the shared array buffer accessibility issue on Safari and ensuring access to ad networks."
+    "text": "Potential increase in system requirements for V-Sekai.\nAdditional development time and resources required for integration."
   },
   {
-    "objectID": "decisions/20240406-web-based-explore.html#benefits",
-    "href": "decisions/20240406-web-based-explore.html#benefits",
-    "title": "Proposed: Web-Based Exploration of V-Sekai",
+    "objectID": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#option-graveyard",
+    "href": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#option-graveyard",
+    "title": "Proposed: VR design application for V-Sekai",
     "section": "",
-    "text": "Enhanced accessibility and reach for V-Sekai.\nImproved user experience by allowing access from any device equipped with a web browser.\nPotential revenue increase through ad networks."
+    "text": "Developing a custom VR design application from scratch (time-consuming and resource-intensive)."
   },
   {
-    "objectID": "decisions/20240406-web-based-explore.html#downsides",
-    "href": "decisions/20240406-web-based-explore.html#downsides",
-    "title": "Proposed: Web-Based Exploration of V-Sekai",
+    "objectID": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: VR design application for V-Sekai",
     "section": "",
-    "text": "Potential performance issues due to operation on a web platform.\nPossible compatibility issues across different browsers."
+    "text": "No, as the enhancement involves integrating a complex VR design application that cannot be achieved through a simple script workaround."
   },
   {
-    "objectID": "decisions/20240406-web-based-explore.html#alternative-path",
-    "href": "decisions/20240406-web-based-explore.html#alternative-path",
-    "title": "Proposed: Web-Based Exploration of V-Sekai",
+    "objectID": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: VR design application for V-Sekai",
     "section": "",
-    "text": "An alternative approach would be maintaining an exclusive focus on the native platform. However, this would restrict V-Sekai’s reach and potential for growth."
+    "text": "Yes, integrating a powerful VR design application will significantly enhance the creative capabilities of V-Sekai users, making it a core feature that directly impacts user experience and satisfaction."
   },
   {
-    "objectID": "decisions/20240406-web-based-explore.html#infrequent-use-case",
-    "href": "decisions/20240406-web-based-explore.html#infrequent-use-case",
-    "title": "Proposed: Web-Based Exploration of V-Sekai",
+    "objectID": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#references",
+    "href": "decisions/20230505-polygon-mesh-based-sculpting-tools.html#references",
+    "title": "Proposed: VR design application for V-Sekai",
     "section": "",
-    "text": "This proposal will significantly benefit users who prefer or only have access to the web platform."
+    "text": "V-Sekai\nCassie on Github: https://github.com/V-Sekai/cassie\nShapelab by Leopoly on Steam\nGravity Sketch on Steam\nSubstance 3D Modeler 2023 on Steam: https://store.steampowered.com/app/1745780/Substance_3D_Modeler_2023/"
   },
   {
-    "objectID": "decisions/20240406-web-based-explore.html#core-implementation-by-us",
-    "href": "decisions/20240406-web-based-explore.html#core-implementation-by-us",
-    "title": "Proposed: Web-Based Exploration of V-Sekai",
+    "objectID": "decisions/20230803-subrepo-addon-management.html",
+    "href": "decisions/20230803-subrepo-addon-management.html",
+    "title": "Accepted: Git Subrepo Addon Management",
     "section": "",
-    "text": "The V-Sekai development team will undertake this project."
+    "text": "We are currently managing separate repositories for each addon in the V-Sekai game. This has led to difficulties in synchronizing updates and maintaining consistency across different components of the project.\n\n\n\nWe propose to continue maintaining separate repositories for each addon, but use Git subrepo to merge them into the main V-Sekai game repository. This would result in the following structure:\nv-sekai-game\n│\n└───addons\n    │\n    ├───vrm (from godot-vrm/only-addon)\n    │\n    └───Godot-MToon-Shader (from Godot-MToon-Shader)\nThis way, all addons will be part of the main game repository but can still be managed independently.\n\n\n\nThe implementation will involve the following steps:\n\nChanges are made in the respective addon repositories.\nThese changes are then merged into the main V-Sekai game repository using Git subrepo.\n\nThis ensures that the addons remain up-to-date with their respective repositories.\n\n\n\n\nStreamlined workflow for managing addons.\nEasier synchronization of updates across different components of the project.\nReduced complexity in project management.\n\n\n\n\n\nInitial setup may require some time and effort.\nDevelopers will need to adapt to the new workflow.\n\n\n\n\nPreviously, we considered maintaining separate repositories for each addon without using Git subrepo. However, this approach was discarded due to the difficulties in synchronizing updates and maintaining consistency across different components of the project.\n\n\n\nNo, this enhancement is fundamental to the project structure and cannot be worked around with a few lines of script.\n\n\n\nYes, this change affects the core structure of our project and should therefore be implemented by us to ensure consistency and control over the project.\n\n\n\n\nV-Sekai"
   },
   {
-    "objectID": "decisions/20240406-web-based-explore.html#status",
-    "href": "decisions/20240406-web-based-explore.html#status",
-    "title": "Proposed: Web-Based Exploration of V-Sekai",
+    "objectID": "decisions/20230803-subrepo-addon-management.html#context-and-problem-statement",
+    "href": "decisions/20230803-subrepo-addon-management.html#context-and-problem-statement",
+    "title": "Accepted: Git Subrepo Addon Management",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "We are currently managing separate repositories for each addon in the V-Sekai game. This has led to difficulties in synchronizing updates and maintaining consistency across different components of the project."
   },
   {
-    "objectID": "decisions/20240406-web-based-explore.html#decision-makers",
-    "href": "decisions/20240406-web-based-explore.html#decision-makers",
-    "title": "Proposed: Web-Based Exploration of V-Sekai",
+    "objectID": "decisions/20230803-subrepo-addon-management.html#proposed-solution",
+    "href": "decisions/20230803-subrepo-addon-management.html#proposed-solution",
+    "title": "Accepted: Git Subrepo Addon Management",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "We propose to continue maintaining separate repositories for each addon, but use Git subrepo to merge them into the main V-Sekai game repository. This would result in the following structure:\nv-sekai-game\n│\n└───addons\n    │\n    ├───vrm (from godot-vrm/only-addon)\n    │\n    └───Godot-MToon-Shader (from Godot-MToon-Shader)\nThis way, all addons will be part of the main game repository but can still be managed independently."
   },
   {
-    "objectID": "decisions/20240406-web-based-explore.html#tags",
-    "href": "decisions/20240406-web-based-explore.html#tags",
-    "title": "Proposed: Web-Based Exploration of V-Sekai",
+    "objectID": "decisions/20230803-subrepo-addon-management.html#implementation",
+    "href": "decisions/20230803-subrepo-addon-management.html#implementation",
+    "title": "Accepted: Git Subrepo Addon Management",
     "section": "",
-    "text": "V-Sekai"
+    "text": "The implementation will involve the following steps:\n\nChanges are made in the respective addon repositories.\nThese changes are then merged into the main V-Sekai game repository using Git subrepo.\n\nThis ensures that the addons remain up-to-date with their respective repositories."
   },
   {
-    "objectID": "decisions/20240406-web-based-explore.html#further-reading",
-    "href": "decisions/20240406-web-based-explore.html#further-reading",
-    "title": "Proposed: Web-Based Exploration of V-Sekai",
+    "objectID": "decisions/20230803-subrepo-addon-management.html#positive-consequences",
+    "href": "decisions/20230803-subrepo-addon-management.html#positive-consequences",
+    "title": "Accepted: Git Subrepo Addon Management",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
+    "text": "Streamlined workflow for managing addons.\nEasier synchronization of updates across different components of the project.\nReduced complexity in project management."
   },
   {
-    "objectID": "decisions/20240325-table-avatar-embedded-xmp.html",
-    "href": "decisions/20240325-table-avatar-embedded-xmp.html",
-    "title": "Proposed: for 3d Asset Schema Design and Database Backend Selection",
+    "objectID": "decisions/20230803-subrepo-addon-management.html#negative-consequences",
+    "href": "decisions/20230803-subrepo-addon-management.html#negative-consequences",
+    "title": "Accepted: Git Subrepo Addon Management",
     "section": "",
-    "text": "The current project involves creating a schema for storing VRM license data, GLTF 3d assets, and other metadata. The data will be stored in a public.cbf_avatar table with fields such as created_at, gltf_embedded, id, and xmp.\n\n\n\nThe main challenge is deciding on the appropriate database backend and determining whether storing large files in a relational database is a good practice.\n\n\n\nCREATE TABLE public.cbf_avatar (\n    created_at timestamptz DEFAULT now() NOT NULL,\n    gltf_embedded jsonb DEFAULT '{}'::jsonb NOT NULL,\n    id uuid DEFAULT gen_random_uuid() NOT NULL,\n    xmp jsonb DEFAULT '{}'::jsonb NOT NULL,\n    CONSTRAINT cbf_avatar_pkey PRIMARY KEY (id)\n);\nThe proposed solution involves using either Supabase PostgreSQL or FoundationDB with SQLite as the database backend. The gltf_embedded field will store GLTF 3d asset data as JSON binary, while the xmp field will store VRM license data and other metadata.\n\n\n\n\nThe use of JSON binary allows for efficient storage and retrieval of GLTF 3d assets.\nThe chosen database backends are robust and reliable, ensuring data integrity and consistency.\n\n\n\n\n\nStoring large files in a relational database could potentially lead to disk thrashing and other performance issues.\nFields in databases generally have a size limit, which could pose problems if the data exceeds this limit.\n\n\n\n\nAn alternative approach would be to store the large files in a separate file system and only keep references to these files in the database. However, this might complicate the data management process.\n\n\n\nThis schema design and database backend selection may not be suitable for applications that require extremely high performance or have strict limitations on data size.\n\n\n\nThe schema design and database backend selection will be implemented by the V-Sekai development team.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nPostgres Storing Large Text - A 2020 article suggesting that larger file storage in a relational database is okay.\n\nThis proposal was assisted by Aria, an AI assistant."
+    "text": "Initial setup may require some time and effort.\nDevelopers will need to adapt to the new workflow."
   },
   {
-    "objectID": "decisions/20240325-table-avatar-embedded-xmp.html#context",
-    "href": "decisions/20240325-table-avatar-embedded-xmp.html#context",
-    "title": "Proposed: for 3d Asset Schema Design and Database Backend Selection",
+    "objectID": "decisions/20230803-subrepo-addon-management.html#option-graveyard",
+    "href": "decisions/20230803-subrepo-addon-management.html#option-graveyard",
+    "title": "Accepted: Git Subrepo Addon Management",
     "section": "",
-    "text": "The current project involves creating a schema for storing VRM license data, GLTF 3d assets, and other metadata. The data will be stored in a public.cbf_avatar table with fields such as created_at, gltf_embedded, id, and xmp."
+    "text": "Previously, we considered maintaining separate repositories for each addon without using Git subrepo. However, this approach was discarded due to the difficulties in synchronizing updates and maintaining consistency across different components of the project."
   },
   {
-    "objectID": "decisions/20240325-table-avatar-embedded-xmp.html#problem-statement",
-    "href": "decisions/20240325-table-avatar-embedded-xmp.html#problem-statement",
-    "title": "Proposed: for 3d Asset Schema Design and Database Backend Selection",
+    "objectID": "decisions/20230803-subrepo-addon-management.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230803-subrepo-addon-management.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Accepted: Git Subrepo Addon Management",
     "section": "",
-    "text": "The main challenge is deciding on the appropriate database backend and determining whether storing large files in a relational database is a good practice."
+    "text": "No, this enhancement is fundamental to the project structure and cannot be worked around with a few lines of script."
   },
   {
-    "objectID": "decisions/20240325-table-avatar-embedded-xmp.html#proposed-solution",
-    "href": "decisions/20240325-table-avatar-embedded-xmp.html#proposed-solution",
-    "title": "Proposed: for 3d Asset Schema Design and Database Backend Selection",
+    "objectID": "decisions/20230803-subrepo-addon-management.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230803-subrepo-addon-management.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Accepted: Git Subrepo Addon Management",
     "section": "",
-    "text": "CREATE TABLE public.cbf_avatar (\n    created_at timestamptz DEFAULT now() NOT NULL,\n    gltf_embedded jsonb DEFAULT '{}'::jsonb NOT NULL,\n    id uuid DEFAULT gen_random_uuid() NOT NULL,\n    xmp jsonb DEFAULT '{}'::jsonb NOT NULL,\n    CONSTRAINT cbf_avatar_pkey PRIMARY KEY (id)\n);\nThe proposed solution involves using either Supabase PostgreSQL or FoundationDB with SQLite as the database backend. The gltf_embedded field will store GLTF 3d asset data as JSON binary, while the xmp field will store VRM license data and other metadata."
+    "text": "Yes, this change affects the core structure of our project and should therefore be implemented by us to ensure consistency and control over the project."
   },
   {
-    "objectID": "decisions/20240325-table-avatar-embedded-xmp.html#benefits",
-    "href": "decisions/20240325-table-avatar-embedded-xmp.html#benefits",
-    "title": "Proposed: for 3d Asset Schema Design and Database Backend Selection",
+    "objectID": "decisions/20230803-subrepo-addon-management.html#references",
+    "href": "decisions/20230803-subrepo-addon-management.html#references",
+    "title": "Accepted: Git Subrepo Addon Management",
     "section": "",
-    "text": "The use of JSON binary allows for efficient storage and retrieval of GLTF 3d assets.\nThe chosen database backends are robust and reliable, ensuring data integrity and consistency."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20240325-table-avatar-embedded-xmp.html#downsides",
-    "href": "decisions/20240325-table-avatar-embedded-xmp.html#downsides",
-    "title": "Proposed: for 3d Asset Schema Design and Database Backend Selection",
+    "objectID": "decisions/20210622-shadermotion-to-godot-engine.html",
+    "href": "decisions/20210622-shadermotion-to-godot-engine.html",
+    "title": "Proposed: Convert #shadermotion to be played in Godot Engine",
     "section": "",
-    "text": "Storing large files in a relational database could potentially lead to disk thrashing and other performance issues.\nFields in databases generally have a size limit, which could pose problems if the data exceeds this limit."
+    "text": "We want a better way of importing animations to Godot Engine. Unfortunately, there is no standard way to exchange motion from other places to Godot and work interchangeably on different characters.\n\n\n\n#shadermotion files in video format provide an excellent way to record motion. However, we want the ability to play it back in Godot Engine onto a VRM character.\n\n\n\nInstall youtube-dl and ffmpeg with scoop\nscoop install youtube-dl ffmpeg\nConvert #shadermotion videos into WebM VP9.\nyoutube-dl https://www.youtube.com/playlist?list=PLmwqDOin_Zt4WCMWqoK6SdHlg0C_WeCP6 --audio-format wav --format webm --recode-video webm\nCrop the preview frame of the video for the left and the right side.\nffmpeg -i \"NNNN.webm\" \"-filter:v\" \"crop=in_w*(1-0.925):ih:0:0,fps=60,scale=24x180:flags=lanczos+full_chroma_inp\" shader_motion_character_00.webm\nffmpeg -i \"NNNN.webm\" \"-filter:v\" \"crop=in_w*(1-0.925):in_h:in_w:in_h,fps=60,scale=24x180:flags=lanczos+full_chroma_inp\" shader_motion_character_0\n\n\n\nBuild godot-cpp\ngodot.windows.opt.tools.64.exe --gdnative-generate-json-api api.json\ngodot.windows.opt.tools.64.exe --gdnative-generate-json-builtin-api builtin_api.json\n# copy to godot-cpp\n# compile godot-cpp\n# Use instructions for 4\n# https://github.com/GodotVR/godot_openvr/pull/123#issue-658898644\nscons p=windows target=release -j16 target=release generate_bindings=yes\n# compile gdnative-video-decoder\nscons platform=win64 target=release -j16\n\n\n\n\nCan interchange motions\n\n\n\n\n\nComplexity\n\n\n\n\nNot trivial.\n\n\n\nThe ability to give motion to 3d characters or NPCS is important.\nThe ability to interchange pose is important.\n\n\n\n\nhttps://motion.chibifire.com\nhttps://github.com/ytdl-org/youtube-dl\nhttps://github.com/FFmpeg/FFmpeg\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240325-table-avatar-embedded-xmp.html#the-road-not-taken",
-    "href": "decisions/20240325-table-avatar-embedded-xmp.html#the-road-not-taken",
-    "title": "Proposed: for 3d Asset Schema Design and Database Backend Selection",
+    "objectID": "decisions/20210622-shadermotion-to-godot-engine.html#context-and-problem-statement",
+    "href": "decisions/20210622-shadermotion-to-godot-engine.html#context-and-problem-statement",
+    "title": "Proposed: Convert #shadermotion to be played in Godot Engine",
     "section": "",
-    "text": "An alternative approach would be to store the large files in a separate file system and only keep references to these files in the database. However, this might complicate the data management process."
+    "text": "We want a better way of importing animations to Godot Engine. Unfortunately, there is no standard way to exchange motion from other places to Godot and work interchangeably on different characters."
   },
   {
-    "objectID": "decisions/20240325-table-avatar-embedded-xmp.html#infrequent-use-case",
-    "href": "decisions/20240325-table-avatar-embedded-xmp.html#infrequent-use-case",
-    "title": "Proposed: for 3d Asset Schema Design and Database Backend Selection",
+    "objectID": "decisions/20210622-shadermotion-to-godot-engine.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20210622-shadermotion-to-godot-engine.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: Convert #shadermotion to be played in Godot Engine",
     "section": "",
-    "text": "This schema design and database backend selection may not be suitable for applications that require extremely high performance or have strict limitations on data size."
+    "text": "#shadermotion files in video format provide an excellent way to record motion. However, we want the ability to play it back in Godot Engine onto a VRM character."
   },
   {
-    "objectID": "decisions/20240325-table-avatar-embedded-xmp.html#in-core-and-done-by-us",
-    "href": "decisions/20240325-table-avatar-embedded-xmp.html#in-core-and-done-by-us",
-    "title": "Proposed: for 3d Asset Schema Design and Database Backend Selection",
+    "objectID": "decisions/20210622-shadermotion-to-godot-engine.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20210622-shadermotion-to-godot-engine.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Convert #shadermotion to be played in Godot Engine",
     "section": "",
-    "text": "The schema design and database backend selection will be implemented by the V-Sekai development team."
+    "text": "Install youtube-dl and ffmpeg with scoop\nscoop install youtube-dl ffmpeg\nConvert #shadermotion videos into WebM VP9.\nyoutube-dl https://www.youtube.com/playlist?list=PLmwqDOin_Zt4WCMWqoK6SdHlg0C_WeCP6 --audio-format wav --format webm --recode-video webm\nCrop the preview frame of the video for the left and the right side.\nffmpeg -i \"NNNN.webm\" \"-filter:v\" \"crop=in_w*(1-0.925):ih:0:0,fps=60,scale=24x180:flags=lanczos+full_chroma_inp\" shader_motion_character_00.webm\nffmpeg -i \"NNNN.webm\" \"-filter:v\" \"crop=in_w*(1-0.925):in_h:in_w:in_h,fps=60,scale=24x180:flags=lanczos+full_chroma_inp\" shader_motion_character_0"
   },
   {
-    "objectID": "decisions/20240325-table-avatar-embedded-xmp.html#status",
-    "href": "decisions/20240325-table-avatar-embedded-xmp.html#status",
-    "title": "Proposed: for 3d Asset Schema Design and Database Backend Selection",
+    "objectID": "decisions/20210622-shadermotion-to-godot-engine.html#how-to-build-godot-video-decoder",
+    "href": "decisions/20210622-shadermotion-to-godot-engine.html#how-to-build-godot-video-decoder",
+    "title": "Proposed: Convert #shadermotion to be played in Godot Engine",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "Build godot-cpp\ngodot.windows.opt.tools.64.exe --gdnative-generate-json-api api.json\ngodot.windows.opt.tools.64.exe --gdnative-generate-json-builtin-api builtin_api.json\n# copy to godot-cpp\n# compile godot-cpp\n# Use instructions for 4\n# https://github.com/GodotVR/godot_openvr/pull/123#issue-658898644\nscons p=windows target=release -j16 target=release generate_bindings=yes\n# compile gdnative-video-decoder\nscons platform=win64 target=release -j16"
   },
   {
-    "objectID": "decisions/20240325-table-avatar-embedded-xmp.html#decision-makers",
-    "href": "decisions/20240325-table-avatar-embedded-xmp.html#decision-makers",
-    "title": "Proposed: for 3d Asset Schema Design and Database Backend Selection",
+    "objectID": "decisions/20210622-shadermotion-to-godot-engine.html#positive-consequences",
+    "href": "decisions/20210622-shadermotion-to-godot-engine.html#positive-consequences",
+    "title": "Proposed: Convert #shadermotion to be played in Godot Engine",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "Can interchange motions"
   },
   {
-    "objectID": "decisions/20240325-table-avatar-embedded-xmp.html#tags",
-    "href": "decisions/20240325-table-avatar-embedded-xmp.html#tags",
-    "title": "Proposed: for 3d Asset Schema Design and Database Backend Selection",
+    "objectID": "decisions/20210622-shadermotion-to-godot-engine.html#negative-consequences",
+    "href": "decisions/20210622-shadermotion-to-godot-engine.html#negative-consequences",
+    "title": "Proposed: Convert #shadermotion to be played in Godot Engine",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Complexity"
   },
   {
-    "objectID": "decisions/20240325-table-avatar-embedded-xmp.html#further-reading",
-    "href": "decisions/20240325-table-avatar-embedded-xmp.html#further-reading",
-    "title": "Proposed: for 3d Asset Schema Design and Database Backend Selection",
+    "objectID": "decisions/20210622-shadermotion-to-godot-engine.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20210622-shadermotion-to-godot-engine.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Convert #shadermotion to be played in Godot Engine",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\nPostgres Storing Large Text - A 2020 article suggesting that larger file storage in a relational database is okay.\n\nThis proposal was assisted by Aria, an AI assistant."
+    "text": "Not trivial."
   },
   {
-    "objectID": "decisions/20240623-talk-length-prototypes.html",
-    "href": "decisions/20240623-talk-length-prototypes.html",
-    "title": "Proposed: Talk Length Game Prototypes",
+    "objectID": "decisions/20210622-shadermotion-to-godot-engine.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20210622-shadermotion-to-godot-engine.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Convert #shadermotion to be played in Godot Engine",
     "section": "",
-    "text": "V-Sekai is a Virtual Reality Social Network Service (VRSNS).\n\n\n\nWhat length should a game demo be?\n\n\n\nOne suggestion is to make the game demo the length of a TED talk. A TED Talk is typically 18 minutes long. This duration is considered optimal for maintaining audience attention and conveying a powerful message, which is exactly what we aim to achieve with our game demo.\n\n\n\n\nAttention Span: An 18-minute demo aligns well with the average person’s attention span. It’s long enough to immerse the player in the game world and showcase its features, but not so long that it risks losing the player’s interest.\nDepth of Experience: This length allows us to provide a substantial preview of the game without overwhelming the player. We can introduce the main gameplay mechanics, narrative elements, and unique features within this timeframe.\nUnique Selling Point: Having a TED talk-length game demo could serve as a unique selling point, distinguishing V-Sekai from other VRSNS.\n\n\n\n\n\nNot One-Size-Fits-All: The length of a TED talk may not be suitable for all types of games. Some games might require longer playtimes to fully appreciate their depth and complexity.\nPlayer Preferences: Some players might prefer shorter or longer demos. We would need to ensure that our target audience is comfortable with this length.\n\n\n\n\nAlternative lengths for the game demo could be considered, such as the length of a typical movie or TV episode.\n\n\n\nThis proposal may not apply to games that are designed to be played in short bursts.\n\n\n\nThis proposal would be implemented by the V-Sekai development team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - The GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis proposal was assisted by AI assistant Aria."
+    "text": "The ability to give motion to 3d characters or NPCS is important.\nThe ability to interchange pose is important."
   },
   {
-    "objectID": "decisions/20240623-talk-length-prototypes.html#the-context",
-    "href": "decisions/20240623-talk-length-prototypes.html#the-context",
-    "title": "Proposed: Talk Length Game Prototypes",
+    "objectID": "decisions/20210622-shadermotion-to-godot-engine.html#references",
+    "href": "decisions/20210622-shadermotion-to-godot-engine.html#references",
+    "title": "Proposed: Convert #shadermotion to be played in Godot Engine",
     "section": "",
-    "text": "V-Sekai is a Virtual Reality Social Network Service (VRSNS)."
+    "text": "https://motion.chibifire.com\nhttps://github.com/ytdl-org/youtube-dl\nhttps://github.com/FFmpeg/FFmpeg"
   },
   {
-    "objectID": "decisions/20240623-talk-length-prototypes.html#the-problem-statement",
-    "href": "decisions/20240623-talk-length-prototypes.html#the-problem-statement",
-    "title": "Proposed: Talk Length Game Prototypes",
+    "objectID": "decisions/20210622-shadermotion-to-godot-engine.html#derivative-license",
+    "href": "decisions/20210622-shadermotion-to-godot-engine.html#derivative-license",
+    "title": "Proposed: Convert #shadermotion to be played in Godot Engine",
     "section": "",
-    "text": "What length should a game demo be?"
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20240623-talk-length-prototypes.html#proposal",
-    "href": "decisions/20240623-talk-length-prototypes.html#proposal",
-    "title": "Proposed: Talk Length Game Prototypes",
+    "objectID": "decisions/20241014-app-updater.html",
+    "href": "decisions/20241014-app-updater.html",
+    "title": "Proposed: Updater No-Op Implementation Using Velopack",
     "section": "",
-    "text": "One suggestion is to make the game demo the length of a TED talk. A TED Talk is typically 18 minutes long. This duration is considered optimal for maintaining audience attention and conveying a powerful message, which is exactly what we aim to achieve with our game demo."
+    "text": "V-Sekai needs frequent updates to improve and expand its VR features.\n\n\n\nIt’s essential to keep users informed during updates without distracting them with complex visuals.\n\n\n\n\n\nfunc update_application():\n    show_text(\"Updating V-Sekai... Please wait.\")\n    if Velopack.check_for_updates():\n        Velopack.perform_update()\n    hide_text()\n    notify(\"Update complete!\")\n\nfunc show_text(text):\n    var label = Label.new()\n    label.text = text\n    add_child(label)\n\nfunc hide_text():\n    get_node(\"Label\").queue_free()\n\nfunc notify(message):\n    show_message(message)\n\n\n\n\n\nSimplicity: Straightforward user communication.\nClarity: Clear update status messages.\nPerformance: Efficient use of resources through Velopack’s optimized update mechanisms.\n\n\n\n\n\nLack of Visual Appeal: Simple text might seem less professional.\nDependency on External Tool: Reliance on Velopack for update management.\n\n\n\n\nA full graphical interface was considered but deemed too distracting for this phase.\n\n\n\nUsers who rarely update might prefer more detailed visuals.\n\n\n\nHandled internally to ensure seamless integration with Velopack.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\nUpdater\nVelopack\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub repository.\nV-Sekai/v-sekai-game - Project page on GitHub.\nVelopack Documentation - Learn more about how Velopack manages application updates.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240623-talk-length-prototypes.html#the-benefits",
-    "href": "decisions/20240623-talk-length-prototypes.html#the-benefits",
-    "title": "Proposed: Talk Length Game Prototypes",
+    "objectID": "decisions/20241014-app-updater.html#the-context",
+    "href": "decisions/20241014-app-updater.html#the-context",
+    "title": "Proposed: Updater No-Op Implementation Using Velopack",
     "section": "",
-    "text": "Attention Span: An 18-minute demo aligns well with the average person’s attention span. It’s long enough to immerse the player in the game world and showcase its features, but not so long that it risks losing the player’s interest.\nDepth of Experience: This length allows us to provide a substantial preview of the game without overwhelming the player. We can introduce the main gameplay mechanics, narrative elements, and unique features within this timeframe.\nUnique Selling Point: Having a TED talk-length game demo could serve as a unique selling point, distinguishing V-Sekai from other VRSNS."
+    "text": "V-Sekai needs frequent updates to improve and expand its VR features."
   },
   {
-    "objectID": "decisions/20240623-talk-length-prototypes.html#the-downsides",
-    "href": "decisions/20240623-talk-length-prototypes.html#the-downsides",
-    "title": "Proposed: Talk Length Game Prototypes",
+    "objectID": "decisions/20241014-app-updater.html#the-problem-statement",
+    "href": "decisions/20241014-app-updater.html#the-problem-statement",
+    "title": "Proposed: Updater No-Op Implementation Using Velopack",
     "section": "",
-    "text": "Not One-Size-Fits-All: The length of a TED talk may not be suitable for all types of games. Some games might require longer playtimes to fully appreciate their depth and complexity.\nPlayer Preferences: Some players might prefer shorter or longer demos. We would need to ensure that our target audience is comfortable with this length."
+    "text": "It’s essential to keep users informed during updates without distracting them with complex visuals."
   },
   {
-    "objectID": "decisions/20240623-talk-length-prototypes.html#the-road-not-taken",
-    "href": "decisions/20240623-talk-length-prototypes.html#the-road-not-taken",
-    "title": "Proposed: Talk Length Game Prototypes",
+    "objectID": "decisions/20241014-app-updater.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20241014-app-updater.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Updater No-Op Implementation Using Velopack",
     "section": "",
-    "text": "Alternative lengths for the game demo could be considered, such as the length of a typical movie or TV episode."
+    "text": "func update_application():\n    show_text(\"Updating V-Sekai... Please wait.\")\n    if Velopack.check_for_updates():\n        Velopack.perform_update()\n    hide_text()\n    notify(\"Update complete!\")\n\nfunc show_text(text):\n    var label = Label.new()\n    label.text = text\n    add_child(label)\n\nfunc hide_text():\n    get_node(\"Label\").queue_free()\n\nfunc notify(message):\n    show_message(message)"
   },
   {
-    "objectID": "decisions/20240623-talk-length-prototypes.html#the-infrequent-use-case",
-    "href": "decisions/20240623-talk-length-prototypes.html#the-infrequent-use-case",
-    "title": "Proposed: Talk Length Game Prototypes",
+    "objectID": "decisions/20241014-app-updater.html#the-benefits",
+    "href": "decisions/20241014-app-updater.html#the-benefits",
+    "title": "Proposed: Updater No-Op Implementation Using Velopack",
     "section": "",
-    "text": "This proposal may not apply to games that are designed to be played in short bursts."
+    "text": "Simplicity: Straightforward user communication.\nClarity: Clear update status messages.\nPerformance: Efficient use of resources through Velopack’s optimized update mechanisms."
   },
   {
-    "objectID": "decisions/20240623-talk-length-prototypes.html#in-core-and-done-by-us",
-    "href": "decisions/20240623-talk-length-prototypes.html#in-core-and-done-by-us",
-    "title": "Proposed: Talk Length Game Prototypes",
+    "objectID": "decisions/20241014-app-updater.html#the-downsides",
+    "href": "decisions/20241014-app-updater.html#the-downsides",
+    "title": "Proposed: Updater No-Op Implementation Using Velopack",
     "section": "",
-    "text": "This proposal would be implemented by the V-Sekai development team."
+    "text": "Lack of Visual Appeal: Simple text might seem less professional.\nDependency on External Tool: Reliance on Velopack for update management."
   },
   {
-    "objectID": "decisions/20240623-talk-length-prototypes.html#status",
-    "href": "decisions/20240623-talk-length-prototypes.html#status",
-    "title": "Proposed: Talk Length Game Prototypes",
+    "objectID": "decisions/20241014-app-updater.html#the-road-not-taken",
+    "href": "decisions/20241014-app-updater.html#the-road-not-taken",
+    "title": "Proposed: Updater No-Op Implementation Using Velopack",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "A full graphical interface was considered but deemed too distracting for this phase."
   },
   {
-    "objectID": "decisions/20240623-talk-length-prototypes.html#decision-makers",
-    "href": "decisions/20240623-talk-length-prototypes.html#decision-makers",
-    "title": "Proposed: Talk Length Game Prototypes",
+    "objectID": "decisions/20241014-app-updater.html#the-infrequent-use-case",
+    "href": "decisions/20241014-app-updater.html#the-infrequent-use-case",
+    "title": "Proposed: Updater No-Op Implementation Using Velopack",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "Users who rarely update might prefer more detailed visuals."
   },
   {
-    "objectID": "decisions/20240623-talk-length-prototypes.html#tags",
-    "href": "decisions/20240623-talk-length-prototypes.html#tags",
-    "title": "Proposed: Talk Length Game Prototypes",
+    "objectID": "decisions/20241014-app-updater.html#in-core-and-done-by-us",
+    "href": "decisions/20241014-app-updater.html#in-core-and-done-by-us",
+    "title": "Proposed: Updater No-Op Implementation Using Velopack",
     "section": "",
-    "text": "V-Sekai"
+    "text": "Handled internally to ensure seamless integration with Velopack."
   },
   {
-    "objectID": "decisions/20240623-talk-length-prototypes.html#further-reading",
-    "href": "decisions/20240623-talk-length-prototypes.html#further-reading",
-    "title": "Proposed: Talk Length Game Prototypes",
+    "objectID": "decisions/20241014-app-updater.html#status",
+    "href": "decisions/20241014-app-updater.html#status",
+    "title": "Proposed: Updater No-Op Implementation Using Velopack",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - The GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nThis proposal was assisted by AI assistant Aria."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20211031-script-as-a-binary.html",
-    "href": "decisions/20211031-script-as-a-binary.html",
-    "title": "Proposed: To provide a performance and portable script use WasGo",
+    "objectID": "decisions/20241014-app-updater.html#decision-makers",
+    "href": "decisions/20241014-app-updater.html#decision-makers",
+    "title": "Proposed: Updater No-Op Implementation Using Velopack",
     "section": "",
-    "text": "Proposed: To provide a performance and portable script use WasGo\n\nContext and Problem Statement\nNeed a performant and portable script\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nUse wasgo for godot 4\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n\nport wasgo to 4\ndownload as binaries\n???\ngame\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNeed to collaborate with mmae\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nWe know how this works.\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20231108-neon-1-gb-scene-storage.html",
-    "href": "decisions/20231108-neon-1-gb-scene-storage.html",
-    "title": "Proposed: Adopting Neon’s Bottomless Storage with S3-Compatible Object Store for Edge CDN Data Management",
+    "objectID": "decisions/20241014-app-updater.html#tags",
+    "href": "decisions/20241014-app-updater.html#tags",
+    "title": "Proposed: Updater No-Op Implementation Using Velopack",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai, Fire\nTags: V-Sekai, Neon, Edge Hosting, Bottomless Storage, S3 Compatible, CDN, PostgreSQL, bytea\n\n\n\n\nV-Sekai operates an open-source platform and is in need of a scalable, high-performance solution for storing and managing CDN data for avatars and worlds at the edge.\n\n\n\nHow can V-Sekai effectively use Neon’s bottomless storage, which leverages PostgreSQL’s capabilities and an S3-compatible object store, for edge-hosted CDN data management?\n\n\n\nImplement an edge computing architecture with Neon’s PostgreSQL services, employing the bytea data type for binary data storage and Neon’s bottomless storage system for flushing PostgreSQL pages to an S3-compatible object store.\n\n\n\n\nEdge-hosted architecture for optimal performance and data sovereignty.\nS3-compatible storage enables cost-effective scaling and redundancy.\nThe use of PostgreSQL’s bytea accommodates efficient binary data management without special maintenance.\n\n\n\n\n\nbytea data type has a 1GB size limit and requires loading full data into memory for operations, which might affect performance with large objects.\nDependence on the reliability of S3-compatible services at the edge.\n\n\n\n\nCentralized or non-S3-compatible storage solutions that may not provide the latency and scalability benefits of an edge-hosted environment.\n\n\n\nCases where binary data exceeds the bytea size limit, necessitating additional strategies for data segmentation or alternative storage methods.\n\n\n\nYes, the edge-hosted Neon infrastructure with an S3-compatible object store is planned to be developed and maintained in-house as a core component of V-Sekai’s backend.\n\n\n\n\nV-Sekai on GitHub\nNeon’s Architecture and Bottomless Storage Details\nPostgreSQL bytea Performance Considerations\n\nThis article was assisted by AI."
+    "text": "V-Sekai\nUpdater\nVelopack"
   },
   {
-    "objectID": "decisions/20231108-neon-1-gb-scene-storage.html#metadata",
-    "href": "decisions/20231108-neon-1-gb-scene-storage.html#metadata",
-    "title": "Proposed: Adopting Neon’s Bottomless Storage with S3-Compatible Object Store for Edge CDN Data Management",
+    "objectID": "decisions/20241014-app-updater.html#further-reading",
+    "href": "decisions/20241014-app-updater.html#further-reading",
+    "title": "Proposed: Updater No-Op Implementation Using Velopack",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai, Fire\nTags: V-Sekai, Neon, Edge Hosting, Bottomless Storage, S3 Compatible, CDN, PostgreSQL, bytea"
+    "text": "V-Sekai · GitHub - Official GitHub repository.\nV-Sekai/v-sekai-game - Project page on GitHub.\nVelopack Documentation - Learn more about how Velopack manages application updates.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20231108-neon-1-gb-scene-storage.html#the-backdrop",
-    "href": "decisions/20231108-neon-1-gb-scene-storage.html#the-backdrop",
-    "title": "Proposed: Adopting Neon’s Bottomless Storage with S3-Compatible Object Store for Edge CDN Data Management",
+    "objectID": "decisions/20230602-pmx-module-integration.html",
+    "href": "decisions/20230602-pmx-module-integration.html",
+    "title": "Proposed: Pmx module integration",
     "section": "",
-    "text": "V-Sekai operates an open-source platform and is in need of a scalable, high-performance solution for storing and managing CDN data for avatars and worlds at the edge."
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, GPT-4\n\n\n\n\nState process for importing a godot engine module work and publish.\n\n\n\nIntegrate the Godot PMX module into the V-Sekai project by following the implementation steps below.\n\n\n\n\nGo to https://github.com/V-Sekai/godot\nMake sure the 4.0 branch is synced with https://github.com/godotengine/godot\nCreate a branch.\n\nLet’s use an example like vsk-pmx.\n\nSwitch to the branch.\nRun git subrepo clone https://github.com/V-Sekai/godot-pmx modules/pmx in the terminal or command prompt.\nCode the module.\nRun git subrepo pull modules/pmx in the terminal or command prompt to merge with upstream repo.\nCode the module.\nRun git subrepo push modules/pmx in the terminal or command prompt to publish.\nMake sure GitHub CI/CD tests pass.\n\n\n\n\n\nSeamless integration of the PMX module into the V-Sekai project\nImproved functionality and features for users\nEasier maintenance and updates for the module\n\n\n\n\n\nPotential increase in complexity and dependencies\nPossible performance impact if not optimized properly\n\n\n\n\n\nManual integration of the PMX module: Instead of using git subrepo, manually copy and integrate the PMX module into the V-Sekai project. This option is less efficient and harder to maintain, as it requires manual updates and synchronization with the original PMX repository.\nUsing Git Submodules: Use git submodule to include the PMX module in the V-Sekai project. While this approach allows for easier updates and maintenance, it can be more complex to set up and manage compared to git subrepo.\nCreating a separate plugin: Develop the PMX module as a standalone plugin that users can install and enable in their projects. This option reduces the complexity of the core V-Sekai project but may result in less seamless integration and increased setup effort for users.\nForking the Godot Engine: Fork the entire Godot Engine and directly modify its source code to include the PMX module. This option is not recommended, as it would make it difficult to keep the fork updated with upstream changes and could lead to compatibility issues.\n\n\n\n\nThis enhancement cannot be easily worked around with a few lines of script, as it involves integrating a new module into the core project.\n\n\n\nIntegrating the PMX module into the core project ensures that it is maintained and updated alongside the main project, providing a consistent and reliable experience for users.\n\n\n\n\nV-Sekai"
   },
   {
-    "objectID": "decisions/20231108-neon-1-gb-scene-storage.html#the-challenge",
-    "href": "decisions/20231108-neon-1-gb-scene-storage.html#the-challenge",
-    "title": "Proposed: Adopting Neon’s Bottomless Storage with S3-Compatible Object Store for Edge CDN Data Management",
+    "objectID": "decisions/20230602-pmx-module-integration.html#metadata",
+    "href": "decisions/20230602-pmx-module-integration.html#metadata",
+    "title": "Proposed: Pmx module integration",
     "section": "",
-    "text": "How can V-Sekai effectively use Neon’s bottomless storage, which leverages PostgreSQL’s capabilities and an S3-compatible object store, for edge-hosted CDN data management?"
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, GPT-4"
   },
   {
-    "objectID": "decisions/20231108-neon-1-gb-scene-storage.html#the-strategy",
-    "href": "decisions/20231108-neon-1-gb-scene-storage.html#the-strategy",
-    "title": "Proposed: Adopting Neon’s Bottomless Storage with S3-Compatible Object Store for Edge CDN Data Management",
+    "objectID": "decisions/20230602-pmx-module-integration.html#context-and-problem-statement",
+    "href": "decisions/20230602-pmx-module-integration.html#context-and-problem-statement",
+    "title": "Proposed: Pmx module integration",
     "section": "",
-    "text": "Implement an edge computing architecture with Neon’s PostgreSQL services, employing the bytea data type for binary data storage and Neon’s bottomless storage system for flushing PostgreSQL pages to an S3-compatible object store."
+    "text": "State process for importing a godot engine module work and publish."
   },
   {
-    "objectID": "decisions/20231108-neon-1-gb-scene-storage.html#the-upside",
-    "href": "decisions/20231108-neon-1-gb-scene-storage.html#the-upside",
-    "title": "Proposed: Adopting Neon’s Bottomless Storage with S3-Compatible Object Store for Edge CDN Data Management",
+    "objectID": "decisions/20230602-pmx-module-integration.html#proposed-solution",
+    "href": "decisions/20230602-pmx-module-integration.html#proposed-solution",
+    "title": "Proposed: Pmx module integration",
     "section": "",
-    "text": "Edge-hosted architecture for optimal performance and data sovereignty.\nS3-compatible storage enables cost-effective scaling and redundancy.\nThe use of PostgreSQL’s bytea accommodates efficient binary data management without special maintenance."
+    "text": "Integrate the Godot PMX module into the V-Sekai project by following the implementation steps below."
   },
   {
-    "objectID": "decisions/20231108-neon-1-gb-scene-storage.html#the-downside",
-    "href": "decisions/20231108-neon-1-gb-scene-storage.html#the-downside",
-    "title": "Proposed: Adopting Neon’s Bottomless Storage with S3-Compatible Object Store for Edge CDN Data Management",
+    "objectID": "decisions/20230602-pmx-module-integration.html#implementation",
+    "href": "decisions/20230602-pmx-module-integration.html#implementation",
+    "title": "Proposed: Pmx module integration",
     "section": "",
-    "text": "bytea data type has a 1GB size limit and requires loading full data into memory for operations, which might affect performance with large objects.\nDependence on the reliability of S3-compatible services at the edge."
+    "text": "Go to https://github.com/V-Sekai/godot\nMake sure the 4.0 branch is synced with https://github.com/godotengine/godot\nCreate a branch.\n\nLet’s use an example like vsk-pmx.\n\nSwitch to the branch.\nRun git subrepo clone https://github.com/V-Sekai/godot-pmx modules/pmx in the terminal or command prompt.\nCode the module.\nRun git subrepo pull modules/pmx in the terminal or command prompt to merge with upstream repo.\nCode the module.\nRun git subrepo push modules/pmx in the terminal or command prompt to publish.\nMake sure GitHub CI/CD tests pass."
   },
   {
-    "objectID": "decisions/20231108-neon-1-gb-scene-storage.html#the-road-not-taken",
-    "href": "decisions/20231108-neon-1-gb-scene-storage.html#the-road-not-taken",
-    "title": "Proposed: Adopting Neon’s Bottomless Storage with S3-Compatible Object Store for Edge CDN Data Management",
+    "objectID": "decisions/20230602-pmx-module-integration.html#positive-consequences",
+    "href": "decisions/20230602-pmx-module-integration.html#positive-consequences",
+    "title": "Proposed: Pmx module integration",
     "section": "",
-    "text": "Centralized or non-S3-compatible storage solutions that may not provide the latency and scalability benefits of an edge-hosted environment."
+    "text": "Seamless integration of the PMX module into the V-Sekai project\nImproved functionality and features for users\nEasier maintenance and updates for the module"
   },
   {
-    "objectID": "decisions/20231108-neon-1-gb-scene-storage.html#the-infrequent-use-case",
-    "href": "decisions/20231108-neon-1-gb-scene-storage.html#the-infrequent-use-case",
-    "title": "Proposed: Adopting Neon’s Bottomless Storage with S3-Compatible Object Store for Edge CDN Data Management",
+    "objectID": "decisions/20230602-pmx-module-integration.html#negative-consequences",
+    "href": "decisions/20230602-pmx-module-integration.html#negative-consequences",
+    "title": "Proposed: Pmx module integration",
     "section": "",
-    "text": "Cases where binary data exceeds the bytea size limit, necessitating additional strategies for data segmentation or alternative storage methods."
+    "text": "Potential increase in complexity and dependencies\nPossible performance impact if not optimized properly"
   },
   {
-    "objectID": "decisions/20231108-neon-1-gb-scene-storage.html#in-core-and-done-by-us",
-    "href": "decisions/20231108-neon-1-gb-scene-storage.html#in-core-and-done-by-us",
-    "title": "Proposed: Adopting Neon’s Bottomless Storage with S3-Compatible Object Store for Edge CDN Data Management",
+    "objectID": "decisions/20230602-pmx-module-integration.html#option-graveyard",
+    "href": "decisions/20230602-pmx-module-integration.html#option-graveyard",
+    "title": "Proposed: Pmx module integration",
     "section": "",
-    "text": "Yes, the edge-hosted Neon infrastructure with an S3-compatible object store is planned to be developed and maintained in-house as a core component of V-Sekai’s backend."
+    "text": "Manual integration of the PMX module: Instead of using git subrepo, manually copy and integrate the PMX module into the V-Sekai project. This option is less efficient and harder to maintain, as it requires manual updates and synchronization with the original PMX repository.\nUsing Git Submodules: Use git submodule to include the PMX module in the V-Sekai project. While this approach allows for easier updates and maintenance, it can be more complex to set up and manage compared to git subrepo.\nCreating a separate plugin: Develop the PMX module as a standalone plugin that users can install and enable in their projects. This option reduces the complexity of the core V-Sekai project but may result in less seamless integration and increased setup effort for users.\nForking the Godot Engine: Fork the entire Godot Engine and directly modify its source code to include the PMX module. This option is not recommended, as it would make it difficult to keep the fork updated with upstream changes and could lead to compatibility issues."
   },
   {
-    "objectID": "decisions/20231108-neon-1-gb-scene-storage.html#further-reading",
-    "href": "decisions/20231108-neon-1-gb-scene-storage.html#further-reading",
-    "title": "Proposed: Adopting Neon’s Bottomless Storage with S3-Compatible Object Store for Edge CDN Data Management",
+    "objectID": "decisions/20230602-pmx-module-integration.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230602-pmx-module-integration.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Pmx module integration",
     "section": "",
-    "text": "V-Sekai on GitHub\nNeon’s Architecture and Bottomless Storage Details\nPostgreSQL bytea Performance Considerations\n\nThis article was assisted by AI."
+    "text": "This enhancement cannot be easily worked around with a few lines of script, as it involves integrating a new module into the core project."
   },
   {
-    "objectID": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html",
-    "href": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html",
-    "title": "Accepted: Create an open metaverse by working on V-Sekai",
+    "objectID": "decisions/20230602-pmx-module-integration.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230602-pmx-module-integration.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Pmx module integration",
     "section": "",
-    "text": "Status: accepted \nDeciders: V-Sekai,lyuma,fire,MrMetaverse,\nTags: V-Sekai,\n\n\n\nV-Sekai is a VR virtual world platform.\n\n\n\nBuild V-Sekai.\n\nSpatialized audio and VOIP support\nA custom networking stack\nA security-focused sandboxed scripting environment backed by WASM\nCustomizable servers with their own individual game rules\nDependable for important presentations\n\nAs a 3d world builder, I want to upload a world to invite my friends to experience (Voice Communication, Reliability, Networked) with me.\n\nUninstalled: give a URL with a copy of the game.\nInstalled: url to uro that sends an url\n\nv-sekai://v-sekai.org/lyuma/home?key=asjdfhgdtg#68.4,1.4,0.34\nRegister windows protocol handler\n\n\nAs an explorer, I want to browse a selection of places to visit.\nAs a user, I want to pick up objects to hand them to my friend.\nAs a user, I want to bring my identity (my avatar) to interact with in V-Sekai.\nAs a developer, I need V-Sekai to understand my needs to have an excellent developer-user experience.\nAs a creative, I want to edit my V-Sekai virtual environment to better suit my requirements and preferences.\nAs a user developer, I want to remix V-Sekai to better suit my requirements and preferences.\nAs a person, I want to work with a group that shares my values.\nAs a person, I want to survive long enough to build V-Sekai.\n\n\n\nRegister protocol.\ndef register_protocol(proto, command):\n    import winreg\n    key = winreg.CreateKey(winreg.HKEY_CLASSES_ROOT, rf\"{proto}\")\n    winreg.SetValueEx(key, \"\", 0, winreg.REG_SZ, f\"URL:{proto} protocol\")\n    winreg.SetValueEx(key, \"URL Protocol\", 0, winreg.REG_SZ, \"\")\n    key = winreg.CreateKey(winreg.HKEY_CLASSES_ROOT, rf\"{proto}\\shell\\open\\command\")\n    winreg.SetValueEx(key, \"\", 0, winreg.REG_SZ, command)\n\n\n\n\nIt matters that we are here to create V-Sekai. I imagine a future where all the virtual world platforms are closed, with no space to create and remix.\nWe are making V-Sekai to serve people who want to create and be in the metaverse.\n\n\n\n\n\nWe are promoting Native VRM support so arbitrary 3d models aren’t on the golden path as of 2021-12-16.\nWe choose native code on the devices, so we can’t use the interoperability of the web as of 2021-12-16.\nWe choose Godot Engine which is an open source game engine to own our dependencies, so it is hard to use off the shelf commercial technologies.\nWe prefer de-facto or open standards for the most reach, so we may not be able to get the exact solution we want without effort.\n\n\n\n\n\nOption: Use dominant VR platforms.\nRejection Reason: At this moment. there is an opportunity to have a coalition of open metaverse.\n\n\n\n\nV-Sekai needs a strategy and not code.\n\n\n\nWe are V-Sekai and only we can be who we want to be.\n\n\n\n\nhttps://www.fortressofdoors.com/so-you-want-to-compete-with-roblox/\n\n\n\n\nYou should consider the following as mere table stakes: High-quality multiplayer support for user #creation out of the box High-performance servers with excellent reliability Powerful, user-friendly, and joyful creation tools\n\n\n\n\nhttps://martinfowler.com/bliki/MonolithFirst.html\nhttps://en.wikipedia.org/wiki/John_Gall_(author)\nhttps://github.com/ubisoft/mixer Has Blender and Unity Support 2021-12-14. It needs to be debugged for Blender 3.0.\n\n\n\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Integrating the PMX module into the core project ensures that it is maintained and updated alongside the main project, providing a consistent and reliable experience for users."
   },
   {
-    "objectID": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html#context-and-problem-statement",
-    "href": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html#context-and-problem-statement",
-    "title": "Accepted: Create an open metaverse by working on V-Sekai",
+    "objectID": "decisions/20230602-pmx-module-integration.html#references",
+    "href": "decisions/20230602-pmx-module-integration.html#references",
+    "title": "Proposed: Pmx module integration",
     "section": "",
-    "text": "V-Sekai is a VR virtual world platform."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Accepted: Create an open metaverse by working on V-Sekai",
+    "objectID": "decisions/20230507-distributed-sim.html",
+    "href": "decisions/20230507-distributed-sim.html",
+    "title": "Rejected: Distributed simulation",
     "section": "",
-    "text": "Build V-Sekai.\n\nSpatialized audio and VOIP support\nA custom networking stack\nA security-focused sandboxed scripting environment backed by WASM\nCustomizable servers with their own individual game rules\nDependable for important presentations\n\nAs a 3d world builder, I want to upload a world to invite my friends to experience (Voice Communication, Reliability, Networked) with me.\n\nUninstalled: give a URL with a copy of the game.\nInstalled: url to uro that sends an url\n\nv-sekai://v-sekai.org/lyuma/home?key=asjdfhgdtg#68.4,1.4,0.34\nRegister windows protocol handler\n\n\nAs an explorer, I want to browse a selection of places to visit.\nAs a user, I want to pick up objects to hand them to my friend.\nAs a user, I want to bring my identity (my avatar) to interact with in V-Sekai.\nAs a developer, I need V-Sekai to understand my needs to have an excellent developer-user experience.\nAs a creative, I want to edit my V-Sekai virtual environment to better suit my requirements and preferences.\nAs a user developer, I want to remix V-Sekai to better suit my requirements and preferences.\nAs a person, I want to work with a group that shares my values.\nAs a person, I want to survive long enough to build V-Sekai."
+    "text": "Status: rejected \nDeciders: V-Sekai,fire,\nTags: V-Sekai,networking,\n\n\n\n\nOur project involves a distributed simulation system where maintaining strong consistency and efficient workload distribution are important requirements. We are currently facing the challenge of how to handle authority transfer and state updates between simulation servers without incurring high network hop counts and latency.\nSomeone invited me to a popular VR platform and gave me a 20-minute tour, just enough to learn how to in desktop mode create a world, import an object, and inspector-edit it. So I imported our celebration map, and the map loaded in 20 seconds. I was able to change its transform. I’m still thinking about that experience.\n\n\n\nWe propose to use a metadata system with Khepri instances and Raft consensus algorithm to manage ownership and mastership information for game entity nodes. Homeservers will manage metadata using their own Khepri instances within a Raft cluster, while simulation servers, including player simulation servers, will maintain game entity nodes they have authority over using their own Khepri instances.\nAuthority transfer will be initiated through the metadata Raft cluster when players interact with game entities governed by different simulation servers. The homeserver Khepri’s nested path-to-value structure will be updated based on the ownership and mastership rules set by the Master. State updates will be exchanged between old and new authority simulation servers or synchronized using a separate mechanism during authority transfer.\nBy monitoring the load on homeservers and simulation servers, we can balance the system and ensure fault tolerance using Raft’s mechanisms. As the number of game entity nodes and players grows, adding more homeservers to the metadata Raft cluster and more simulation servers will ensure efficient workload distribution and enhance the overall gaming experience.\nWe believe that this approach will provide strong consistency guarantees, access control, and scalability while minimizing network hop counts and latency for authority transfer and state updates between simulation servers.\n\n\n\n\n\n\nHomeserver: A server responsible for managing metadata, including ownership and mastership information for game entity nodes.\nSimulation server: A server responsible for containing game entity nodes it has authority over, including player simulation servers.\nKhepri: A tree-like replicated on-disk database library for Erlang and Elixir, used for maintaining a nested path-to-value store.\nRaft cluster: A cluster of servers implementing the Raft consensus algorithm to ensure strong consistency and fault tolerance.\nOwnership: The player who has control over a game entity and can change its state.\nMastership: The authority that can change ownership rules and default ownership settings.\nAsk, Deny, Allow: Rules set by the Master for ownership transfer.\n\n\n\n\n\nEach type of server can only be Khepri members of the same type.\nEach server can only allow be Khepri members of the same logical instance.\nRaft is only active inside of each logical instance.\nHomeserver servers are REST + JSON and the cheap pattern.\nSimulation servers are using the nasty state transfer pattern\n\n\n\n\n\n\n\n\n\n\n\nStep\nAction\n\n\n\n\n1\nPlayer A’s simulation server sends a request to the home server to fetch the public key of Player B.\n\n\n2\nThe home server retrieves Player B’s public key from its database and sends it back to Player A’s simulation server.\n\n\n3\nPlayer A’s simulation server uses Player B’s public key to encrypt a message or binary data.\n\n\n4\nPlayer A’s simulation server signs the encrypted message or binary data using its own private key.\n\n\n5\nPlayer A’s simulation server sends the encrypted message or binary data along with the digital signature to Player B’s simulation server using the membrane_udp_plugin.\n\n\n6\nPlayer B’s simulation server receives the message and verifies the digital signature using Player A’s public key, which it retrieves from the home server.\n\n\n7\nIf the signature is valid, Player B’s simulation server uses its own private key to decrypt the message and obtain the original data sent by Player A’s simulation server.\n\n\n8\nIf the message is confidential, Player B’s simulation server may want to send a response back to Player A’s simulation server using a similar protocol, with Player A’s public key retrieved from the home server.\n\n\n\nThis table outlines the steps of the communication protocol between Player A and Player B’s simulation servers, which involves retrieving public keys from the home server’s database, encrypting and signing messages, and verifying digital signatures to ensure the authenticity of the messages. This protocol ensures secure and confidential communication between the two simulation servers, allowing for safe and reliable data exchange.\n# EC examples\nalice_private_jwk = JOSE.JWK.from_pem_file(\"ec-secp256r1-alice.pem\")\nalice_public_jwk  = JOSE.JWK.to_public(alice_private_jwk)\nbob_private_jwk   = JOSE.JWK.from_pem_file(\"ec-secp256r1-bob.pem\")\nbob_public_jwk    = JOSE.JWK.to_public(bob_private_jwk)\n\n## Encrypt and Decrypt (defaults to ECDH-ES with A128GCM)\n### Alice sends Bob a secret message using Bob's public key and Alice's private key\nalice_to_bob = \"For Bob's eyes only.\"\nencrypted = JOSE.JWK.box_encrypt(alice_to_bob, bob_public_jwk, alice_private_jwk)\n### Only Bob can decrypt the message using his private key (Alice's public key is embedded in the JWE header)\n{^alice_to_bob, _} = JOSE.JWK.box_decrypt(encrypted, bob_private_jwk)\n\n\n\nIn a distributed simulation system, maintaining separate roles for homeservers and simulation servers and using a metadata system with strong consistency guarantees is crucial. Homeservers are responsible for managing metadata, including ownership and mastership information for game entity nodes, using a Khepri instance within a Raft cluster. Simulation servers, including player simulation servers, maintain game entity nodes they have authority over using their own Khepri instances.\nAuthority transfer is initiated through the metadata Raft cluster when players interact with game entities governed by different simulation servers. The homeserver Khepri’s nested path-to-value structure is updated based on the ownership and mastership rules set by the Master. State updates are exchanged between old and new authority simulation servers or synchronized using a separate mechanism during authority transfer.\nMonitoring the load on homeservers and simulation servers allows for balancing the system and ensuring fault tolerance using Raft’s mechanisms. As the number of game entity nodes and players grows, adding more homeservers to the metadata Raft cluster and more simulation servers ensures efficient workload distribution and enhances the overall gaming experience.\n\n\n\n\nCase 1: Authority transfer from Player A to Player B on a different home server\n\n\n\n\n\n\n\n\nStep\nDescription\nHop Count\n\n\n\n\n1\nPlayer A’s simulation server sends a request to its homeserver (1 hop).\n1\n\n\n2\nPlayer A’s homeserver sends an authority request to Player B’s homeserver (H hops).\nH\n\n\n3\nPlayer B’s homeserver sends a response to Player A’s homeserver (H hops).\nH\n\n\n4\nPlayer A’s homeserver sends an authority response to Player A’s simulation server (1 hop).\n1\n\n\n5\nPlayer A’s simulation server sends an acknowledgment to Player B’s simulation server (1 hop).\n1\n\n\n\nSending an acknowledgment from Player A’s homeserver to Player A’s simulation server may not be necessary, as the authority request can be sent directly to Player B’s homeserver without waiting for confirmation.\nTotal hops: 3 + 2 * H\nCase 2: Authority transfer if Player A’s and Player B’s homeservers are exactly the same\n\n\n\n\n\n\n\n\nStep\nDescription\nHop Count\n\n\n\n\n1\nPlayer A’s simulation server sends a request to its homeserver (1 hop).\n1\n\n\n2\nPlayer A’s homeserver sends a response directly to Player B’s simulation server (1 hop).\n1\n\n\n3\nPlayer B’s simulation server sends an acknowledgment to Player A’s simulation server (1 hop).\n1\n\n\n\nTotal hops: 3\nIn this optimized process, we have removed sending an acknowledgment from Player A’s homeserver to Player A’s simulation server. This acknowledgment may not be necessary, as the response can be sent directly to Player B’s simulation server without waiting for confirmation. By removing this step, we reduce the total hop count by 1, potentially improving the efficiency of the authority transfer process when both players are on the same home server.\nCase 3: Direct communication between Player A and Player B’s simulation servers on the same home server.\n\n\n\n\n\n\n\n\nStep\nDescription\nHop Count\n\n\n\n\n1\nPlayer A’s simulation server sends an update directly to Player B’s simulation server using a hand-optimized binary layout and an asynchronous communication model.\n1\n\n\n2\nPlayer B’s simulation server sends an acknowledgment to Player A’s simulation server using credit-based flow control or another asynchronous technique.\n1\n\n\n\nIn this modified version of Case 3, both the update and acknowledgment steps employ the high-performance communication system’s features. This includes using hand-optimized binary layouts for data transfer and asynchronous communication techniques to minimize latency and maximize throughput. The total hop count remains the same at 2 hops.\n\n\n\nStrong consistency guarantees\nAccess control over Khepri instances\nScalability\nMinimized network hop counts and latency for authority transfer and state updates\n\n\n\n\n\nComplexity: The proposed system involves multiple components, such as homeservers, simulation servers, Khepri instances, and Raft clusters. Managing and maintaining these components can be complex and may require significant development effort.\nPerformance: The use of Raft consensus algorithm ensures strong consistency but may introduce performance overhead due to the need for communication between nodes in the cluster. This could impact the overall performance of the distributed simulation system.\nScalability: While the proposal aims to provide scalability, it is not clear how well the system will scale as the number of game entity nodes and players grows. Adding more homeservers and simulation servers might help, but there could still be bottlenecks or limitations that need to be addressed.\nSecurity: The proposed state transfer protocol relies on public key cryptography for secure communication between simulation servers. However, the security of the system depends on proper key management and protection against potential attacks, such as man-in-the-middle attacks or replay attacks.\nFault tolerance: Although the Raft consensus algorithm provides fault tolerance, the system’s resilience to failures (e.g., server crashes, network issues) needs to be carefully considered and tested to ensure smooth operation under various conditions.\nSynchronization: The proposal mentions that state updates are exchanged between old and new authority simulation servers or synchronized using a separate mechanism during authority transfer. However, it does not provide details on how this synchronization process works, which could be a critical aspect of the system’s functionality.\nLoad balancing: Monitoring the load on homeservers and simulation servers is essential for balancing the system. However, the proposal does not provide specific details on how load balancing will be achieved or what metrics will be used to determine when to add or remove servers from the system.\n\n\n\n\nWe considered using a client-server model for the distributed simulation system but found that it would not provide the strong consistency guarantees and access control we require, and it would also be more difficult to scale as the number of game entity nodes and players grows.\n\n\n\nThis is not a few lines of script.\n\n\n\nI am exploring alternatives for the current implementation of the client-server model.\n\n\n\n\nV-Sekai: https://v-sekai.org/\nKhepri documentation: https://github.com/rabbitmq/khepri\nRaft consensus algorithm: https://raft.github.io/\nNetworked Physics in Virtual Reality: https://gafferongames.com/post/networked_physics_in_virtual_reality/\nChapter 7 - Advanced Architecture using ZeroMQ: https://zguide.zeromq.org/docs/chapter7/"
   },
   {
-    "objectID": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Accepted: Create an open metaverse by working on V-Sekai",
+    "objectID": "decisions/20230507-distributed-sim.html#distributed-simulation-architecture",
+    "href": "decisions/20230507-distributed-sim.html#distributed-simulation-architecture",
+    "title": "Rejected: Distributed simulation",
     "section": "",
-    "text": "Register protocol.\ndef register_protocol(proto, command):\n    import winreg\n    key = winreg.CreateKey(winreg.HKEY_CLASSES_ROOT, rf\"{proto}\")\n    winreg.SetValueEx(key, \"\", 0, winreg.REG_SZ, f\"URL:{proto} protocol\")\n    winreg.SetValueEx(key, \"URL Protocol\", 0, winreg.REG_SZ, \"\")\n    key = winreg.CreateKey(winreg.HKEY_CLASSES_ROOT, rf\"{proto}\\shell\\open\\command\")\n    winreg.SetValueEx(key, \"\", 0, winreg.REG_SZ, command)"
+    "text": "Case 1: Authority transfer from Player A to Player B on a different home server\n\n\n\n\n\n\n\n\nStep\nDescription\nHop Count\n\n\n\n\n1\nPlayer A’s simulation server sends a request to its homeserver (1 hop).\n1\n\n\n2\nPlayer A’s homeserver sends an authority request to Player B’s homeserver (H hops).\nH\n\n\n3\nPlayer B’s homeserver sends a response to Player A’s homeserver (H hops).\nH\n\n\n4\nPlayer A’s homeserver sends an authority response to Player A’s simulation server (1 hop).\n1\n\n\n5\nPlayer A’s simulation server sends an acknowledgment to Player B’s simulation server (1 hop).\n1\n\n\n\nSending an acknowledgment from Player A’s homeserver to Player A’s simulation server may not be necessary, as the authority request can be sent directly to Player B’s homeserver without waiting for confirmation.\nTotal hops: 3 + 2 * H\nCase 2: Authority transfer if Player A’s and Player B’s homeservers are exactly the same\n\n\n\n\n\n\n\n\nStep\nDescription\nHop Count\n\n\n\n\n1\nPlayer A’s simulation server sends a request to its homeserver (1 hop).\n1\n\n\n2\nPlayer A’s homeserver sends a response directly to Player B’s simulation server (1 hop).\n1\n\n\n3\nPlayer B’s simulation server sends an acknowledgment to Player A’s simulation server (1 hop).\n1\n\n\n\nTotal hops: 3\nIn this optimized process, we have removed sending an acknowledgment from Player A’s homeserver to Player A’s simulation server. This acknowledgment may not be necessary, as the response can be sent directly to Player B’s simulation server without waiting for confirmation. By removing this step, we reduce the total hop count by 1, potentially improving the efficiency of the authority transfer process when both players are on the same home server.\nCase 3: Direct communication between Player A and Player B’s simulation servers on the same home server.\n\n\n\n\n\n\n\n\nStep\nDescription\nHop Count\n\n\n\n\n1\nPlayer A’s simulation server sends an update directly to Player B’s simulation server using a hand-optimized binary layout and an asynchronous communication model.\n1\n\n\n2\nPlayer B’s simulation server sends an acknowledgment to Player A’s simulation server using credit-based flow control or another asynchronous technique.\n1\n\n\n\nIn this modified version of Case 3, both the update and acknowledgment steps employ the high-performance communication system’s features. This includes using hand-optimized binary layouts for data transfer and asynchronous communication techniques to minimize latency and maximize throughput. The total hop count remains the same at 2 hops.\n\n\n\nStrong consistency guarantees\nAccess control over Khepri instances\nScalability\nMinimized network hop counts and latency for authority transfer and state updates\n\n\n\n\n\nComplexity: The proposed system involves multiple components, such as homeservers, simulation servers, Khepri instances, and Raft clusters. Managing and maintaining these components can be complex and may require significant development effort.\nPerformance: The use of Raft consensus algorithm ensures strong consistency but may introduce performance overhead due to the need for communication between nodes in the cluster. This could impact the overall performance of the distributed simulation system.\nScalability: While the proposal aims to provide scalability, it is not clear how well the system will scale as the number of game entity nodes and players grows. Adding more homeservers and simulation servers might help, but there could still be bottlenecks or limitations that need to be addressed.\nSecurity: The proposed state transfer protocol relies on public key cryptography for secure communication between simulation servers. However, the security of the system depends on proper key management and protection against potential attacks, such as man-in-the-middle attacks or replay attacks.\nFault tolerance: Although the Raft consensus algorithm provides fault tolerance, the system’s resilience to failures (e.g., server crashes, network issues) needs to be carefully considered and tested to ensure smooth operation under various conditions.\nSynchronization: The proposal mentions that state updates are exchanged between old and new authority simulation servers or synchronized using a separate mechanism during authority transfer. However, it does not provide details on how this synchronization process works, which could be a critical aspect of the system’s functionality.\nLoad balancing: Monitoring the load on homeservers and simulation servers is essential for balancing the system. However, the proposal does not provide specific details on how load balancing will be achieved or what metrics will be used to determine when to add or remove servers from the system.\n\n\n\n\nWe considered using a client-server model for the distributed simulation system but found that it would not provide the strong consistency guarantees and access control we require, and it would also be more difficult to scale as the number of game entity nodes and players grows.\n\n\n\nThis is not a few lines of script.\n\n\n\nI am exploring alternatives for the current implementation of the client-server model.\n\n\n\n\nV-Sekai: https://v-sekai.org/\nKhepri documentation: https://github.com/rabbitmq/khepri\nRaft consensus algorithm: https://raft.github.io/\nNetworked Physics in Virtual Reality: https://gafferongames.com/post/networked_physics_in_virtual_reality/\nChapter 7 - Advanced Architecture using ZeroMQ: https://zguide.zeromq.org/docs/chapter7/"
   },
   {
-    "objectID": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html#positive-consequences",
-    "href": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html#positive-consequences",
-    "title": "Accepted: Create an open metaverse by working on V-Sekai",
+    "objectID": "decisions/20241011-recovering-makehuman-parameters.html",
+    "href": "decisions/20241011-recovering-makehuman-parameters.html",
+    "title": "Proposed: Recovering MakeHuman Parameters Using Depth Map Comparison with Godot Engine",
     "section": "",
-    "text": "It matters that we are here to create V-Sekai. I imagine a future where all the virtual world platforms are closed, with no space to create and remix.\nWe are making V-Sekai to serve people who want to create and be in the metaverse."
+    "text": "In the realm of digital animation and character modeling, fitting an avatar to a specific image can enhance personalization and realism in various applications such as gaming and virtual reality.\n\n\n\nThe challenge lies in accurately estimating the parameters of a MakeHuman model from a given anime-style image to ensure the avatar closely resembles the original character.\n\n\n\n\n\nWe propose a system that utilizes depth map comparisons between rendered images from the Godot Engine and depth maps generated from anime images using Apple’s ML-Depth-Pro. This approach aims to optimize the MakeHuman parameters to recreate accurate 3D models of anime characters.\n\n\n\nDepth Map Generation: Generate depth maps from both anime images and Godot-rendered characters.\nOptimization: Employ machine learning techniques to minimize the differences between these depth maps, facilitating accurate parameter recovery.\nCost Efficiency: Leverage open-source tools to maintain budget-friendliness.\n\n\n\n\n\nInput Data: Anime images with manually labeled MakeHuman parameters for initial calibration.\nDepth Comparison: Analyze the discrepancies between the depth maps produced by Godot and those derived from anime images.\nOptimization Process: Utilize a search algorithm (e.g., genetic algorithm or bayesian optimization) to iteratively adjust and determine optimal MakeHuman parameters.\n\n\n\n\n\nData Collection:\n\nTask: Manually label a small set of images with MakeHuman parameters.\nOutcome: Create a baseline dataset for initial optimization efforts.\n\nGodot Integration:\n\nTask: Develop a script within Godot to render depth maps from configured MakeHuman models.\nOutcome: Prepare depth maps for subsequent comparison.\n\nOptimization Algorithm:\n\nTask: Implement a cost-effective optimization algorithm using a suitable loss function (e.g., L2, Chamfer distance).\nOutcome: Establish a mechanism to identify the best matching MakeHuman parameters.\n\nTesting and Refinement:\n\nTask: Systematically compare generated depth maps and refine the algorithm to improve accuracy.\nTimeline:\n\nData Collection: 1 week\nGodot Integration: 2 weeks\nOptimization Model: 3 weeks\nTesting & Refinement: 1 week\nTotal Duration: 7 weeks\n\n\n\n\n\n\n\n\nThis streamlined, budget-conscious methodology promises significant enhancements in personalization and realism in digital character modeling, making it ideal for applications in gaming and virtual reality where character authenticity is crucial.\n\n\n\n\nLimited Creativity: Strict adherence to replicating existing images may limit creative modifications.\nTechnical Complexity: The integration of multiple advanced technologies (depth sensing, machine learning, and 3D rendering) requires high technical expertise.\n\n\n\n\nAlternative methods such as direct 3D scanning of physical models or manual tweaking of parameters were considered but deemed less efficient and scalable compared to our proposed automated depth comparison method.\n\n\n\nIn cases where extremely high fidelity is required, such as in professional film production, additional manual adjustments by expert artists might still be necessary.\n\n\n\nThis project aligns with our core mission of enhancing digital interaction experiences and will be developed and maintained by our team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nDepthPro Demo with 3D Visualization\nHyper_parameter_optimization like bayensian optimization\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html#negative-consequences",
-    "href": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html#negative-consequences",
-    "title": "Accepted: Create an open metaverse by working on V-Sekai",
+    "objectID": "decisions/20241011-recovering-makehuman-parameters.html#the-context",
+    "href": "decisions/20241011-recovering-makehuman-parameters.html#the-context",
+    "title": "Proposed: Recovering MakeHuman Parameters Using Depth Map Comparison with Godot Engine",
     "section": "",
-    "text": "We are promoting Native VRM support so arbitrary 3d models aren’t on the golden path as of 2021-12-16.\nWe choose native code on the devices, so we can’t use the interoperability of the web as of 2021-12-16.\nWe choose Godot Engine which is an open source game engine to own our dependencies, so it is hard to use off the shelf commercial technologies.\nWe prefer de-facto or open standards for the most reach, so we may not be able to get the exact solution we want without effort."
+    "text": "In the realm of digital animation and character modeling, fitting an avatar to a specific image can enhance personalization and realism in various applications such as gaming and virtual reality."
   },
   {
-    "objectID": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html#option-graveyard",
-    "href": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html#option-graveyard",
-    "title": "Accepted: Create an open metaverse by working on V-Sekai",
+    "objectID": "decisions/20241011-recovering-makehuman-parameters.html#the-problem-statement",
+    "href": "decisions/20241011-recovering-makehuman-parameters.html#the-problem-statement",
+    "title": "Proposed: Recovering MakeHuman Parameters Using Depth Map Comparison with Godot Engine",
     "section": "",
-    "text": "Option: Use dominant VR platforms.\nRejection Reason: At this moment. there is an opportunity to have a coalition of open metaverse."
+    "text": "The challenge lies in accurately estimating the parameters of a MakeHuman model from a given anime-style image to ensure the avatar closely resembles the original character."
   },
   {
-    "objectID": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Accepted: Create an open metaverse by working on V-Sekai",
+    "objectID": "decisions/20241011-recovering-makehuman-parameters.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20241011-recovering-makehuman-parameters.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Recovering MakeHuman Parameters Using Depth Map Comparison with Godot Engine",
     "section": "",
-    "text": "V-Sekai needs a strategy and not code."
+    "text": "We propose a system that utilizes depth map comparisons between rendered images from the Godot Engine and depth maps generated from anime images using Apple’s ML-Depth-Pro. This approach aims to optimize the MakeHuman parameters to recreate accurate 3D models of anime characters.\n\n\n\nDepth Map Generation: Generate depth maps from both anime images and Godot-rendered characters.\nOptimization: Employ machine learning techniques to minimize the differences between these depth maps, facilitating accurate parameter recovery.\nCost Efficiency: Leverage open-source tools to maintain budget-friendliness.\n\n\n\n\n\nInput Data: Anime images with manually labeled MakeHuman parameters for initial calibration.\nDepth Comparison: Analyze the discrepancies between the depth maps produced by Godot and those derived from anime images.\nOptimization Process: Utilize a search algorithm (e.g., genetic algorithm or bayesian optimization) to iteratively adjust and determine optimal MakeHuman parameters.\n\n\n\n\n\nData Collection:\n\nTask: Manually label a small set of images with MakeHuman parameters.\nOutcome: Create a baseline dataset for initial optimization efforts.\n\nGodot Integration:\n\nTask: Develop a script within Godot to render depth maps from configured MakeHuman models.\nOutcome: Prepare depth maps for subsequent comparison.\n\nOptimization Algorithm:\n\nTask: Implement a cost-effective optimization algorithm using a suitable loss function (e.g., L2, Chamfer distance).\nOutcome: Establish a mechanism to identify the best matching MakeHuman parameters.\n\nTesting and Refinement:\n\nTask: Systematically compare generated depth maps and refine the algorithm to improve accuracy.\nTimeline:\n\nData Collection: 1 week\nGodot Integration: 2 weeks\nOptimization Model: 3 weeks\nTesting & Refinement: 1 week\nTotal Duration: 7 weeks"
   },
   {
-    "objectID": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Accepted: Create an open metaverse by working on V-Sekai",
+    "objectID": "decisions/20241011-recovering-makehuman-parameters.html#the-benefits",
+    "href": "decisions/20241011-recovering-makehuman-parameters.html#the-benefits",
+    "title": "Proposed: Recovering MakeHuman Parameters Using Depth Map Comparison with Godot Engine",
     "section": "",
-    "text": "We are V-Sekai and only we can be who we want to be."
+    "text": "This streamlined, budget-conscious methodology promises significant enhancements in personalization and realism in digital character modeling, making it ideal for applications in gaming and virtual reality where character authenticity is crucial."
   },
   {
-    "objectID": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html#references",
-    "href": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html#references",
-    "title": "Accepted: Create an open metaverse by working on V-Sekai",
+    "objectID": "decisions/20241011-recovering-makehuman-parameters.html#the-downsides",
+    "href": "decisions/20241011-recovering-makehuman-parameters.html#the-downsides",
+    "title": "Proposed: Recovering MakeHuman Parameters Using Depth Map Comparison with Godot Engine",
     "section": "",
-    "text": "https://www.fortressofdoors.com/so-you-want-to-compete-with-roblox/\n\n\n\n\nYou should consider the following as mere table stakes: High-quality multiplayer support for user #creation out of the box High-performance servers with excellent reliability Powerful, user-friendly, and joyful creation tools\n\n\n\n\nhttps://martinfowler.com/bliki/MonolithFirst.html\nhttps://en.wikipedia.org/wiki/John_Gall_(author)\nhttps://github.com/ubisoft/mixer Has Blender and Unity Support 2021-12-14. It needs to be debugged for Blender 3.0."
+    "text": "Limited Creativity: Strict adherence to replicating existing images may limit creative modifications.\nTechnical Complexity: The integration of multiple advanced technologies (depth sensing, machine learning, and 3D rendering) requires high technical expertise."
   },
   {
-    "objectID": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html#derivative-license",
-    "href": "decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html#derivative-license",
-    "title": "Accepted: Create an open metaverse by working on V-Sekai",
+    "objectID": "decisions/20241011-recovering-makehuman-parameters.html#the-road-not-taken",
+    "href": "decisions/20241011-recovering-makehuman-parameters.html#the-road-not-taken",
+    "title": "Proposed: Recovering MakeHuman Parameters Using Depth Map Comparison with Godot Engine",
     "section": "",
-    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Alternative methods such as direct 3D scanning of physical models or manual tweaking of parameters were considered but deemed less efficient and scalable compared to our proposed automated depth comparison method."
   },
   {
-    "objectID": "decisions/20230509-wasm-data-exchange.html",
-    "href": "decisions/20230509-wasm-data-exchange.html",
-    "title": "Draft: Exchange data between Godot Engine and WASM using handles",
+    "objectID": "decisions/20241011-recovering-makehuman-parameters.html#the-infrequent-use-case",
+    "href": "decisions/20241011-recovering-makehuman-parameters.html#the-infrequent-use-case",
+    "title": "Proposed: Recovering MakeHuman Parameters Using Depth Map Comparison with Godot Engine",
     "section": "",
-    "text": "Status: draft \nDeciders: V-Sekai, fire, lyuma, ashtonmeuser\nTags: V-Sekai, ChatGPT-4\n\n\n\n\nV-Sekai faces a limitation in sending complex data types between the Godot Engine and WebAssembly (WASM) modules. Simple Variant types can be marshaled or copied onto the stack, but arrays, dictionaries, and Object types require a more efficient approach.\n\n\n\nImplement a handle-based approach for managing complex data types. Allocate handles, possibly reference counted, allowing the WASM guest to pass integers around to all the Godot APIs. This will enable efficient communication between the host side and the WASM guest.\n\n\n\n\nDesign a handle-based system for managing complex data types.\nImplement reference counting for allocated handles.\nAdd Godot APIs to accept integer handles instead of direct object references.\nTest the new implementation with various data types and scenarios.\n\n\n\n\n\nEfficient communication between the host side and the WASM guest.\nImproved performance when dealing with complex data types.\nSimplified API usage for developers.\n\n\n\n\n\nAdditional complexity in the implementation.\nPotential overhead due to reference counting.\n\n\n\n\nN/A\n\n\n\nNo, this enhancement addresses a core limitation and requires changes to the underlying system.\n\n\n\nYes, this enhancement improves the efficiency and usability of the V-Sekai platform, making it more attractive to developers and users.\n\n\n\n\nV-Sekai\nGodot Engine StreamPeer\nGodot Engine Wasm\nGodot Engine WasGo"
+    "text": "In cases where extremely high fidelity is required, such as in professional film production, additional manual adjustments by expert artists might still be necessary."
   },
   {
-    "objectID": "decisions/20230509-wasm-data-exchange.html#metadata",
-    "href": "decisions/20230509-wasm-data-exchange.html#metadata",
-    "title": "Draft: Exchange data between Godot Engine and WASM using handles",
+    "objectID": "decisions/20241011-recovering-makehuman-parameters.html#in-core-and-done-by-us",
+    "href": "decisions/20241011-recovering-makehuman-parameters.html#in-core-and-done-by-us",
+    "title": "Proposed: Recovering MakeHuman Parameters Using Depth Map Comparison with Godot Engine",
     "section": "",
-    "text": "Status: draft \nDeciders: V-Sekai, fire, lyuma, ashtonmeuser\nTags: V-Sekai, ChatGPT-4"
+    "text": "This project aligns with our core mission of enhancing digital interaction experiences and will be developed and maintained by our team."
   },
   {
-    "objectID": "decisions/20230509-wasm-data-exchange.html#context-and-problem-statement",
-    "href": "decisions/20230509-wasm-data-exchange.html#context-and-problem-statement",
-    "title": "Draft: Exchange data between Godot Engine and WASM using handles",
+    "objectID": "decisions/20241011-recovering-makehuman-parameters.html#status",
+    "href": "decisions/20241011-recovering-makehuman-parameters.html#status",
+    "title": "Proposed: Recovering MakeHuman Parameters Using Depth Map Comparison with Godot Engine",
     "section": "",
-    "text": "V-Sekai faces a limitation in sending complex data types between the Godot Engine and WebAssembly (WASM) modules. Simple Variant types can be marshaled or copied onto the stack, but arrays, dictionaries, and Object types require a more efficient approach."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20230509-wasm-data-exchange.html#proposed-solution",
-    "href": "decisions/20230509-wasm-data-exchange.html#proposed-solution",
-    "title": "Draft: Exchange data between Godot Engine and WASM using handles",
+    "objectID": "decisions/20241011-recovering-makehuman-parameters.html#decision-makers",
+    "href": "decisions/20241011-recovering-makehuman-parameters.html#decision-makers",
+    "title": "Proposed: Recovering MakeHuman Parameters Using Depth Map Comparison with Godot Engine",
     "section": "",
-    "text": "Implement a handle-based approach for managing complex data types. Allocate handles, possibly reference counted, allowing the WASM guest to pass integers around to all the Godot APIs. This will enable efficient communication between the host side and the WASM guest."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20230509-wasm-data-exchange.html#implementation",
-    "href": "decisions/20230509-wasm-data-exchange.html#implementation",
-    "title": "Draft: Exchange data between Godot Engine and WASM using handles",
+    "objectID": "decisions/20241011-recovering-makehuman-parameters.html#tags",
+    "href": "decisions/20241011-recovering-makehuman-parameters.html#tags",
+    "title": "Proposed: Recovering MakeHuman Parameters Using Depth Map Comparison with Godot Engine",
     "section": "",
-    "text": "Design a handle-based system for managing complex data types.\nImplement reference counting for allocated handles.\nAdd Godot APIs to accept integer handles instead of direct object references.\nTest the new implementation with various data types and scenarios."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20230509-wasm-data-exchange.html#positive-consequences",
-    "href": "decisions/20230509-wasm-data-exchange.html#positive-consequences",
-    "title": "Draft: Exchange data between Godot Engine and WASM using handles",
+    "objectID": "decisions/20241011-recovering-makehuman-parameters.html#further-reading",
+    "href": "decisions/20241011-recovering-makehuman-parameters.html#further-reading",
+    "title": "Proposed: Recovering MakeHuman Parameters Using Depth Map Comparison with Godot Engine",
     "section": "",
-    "text": "Efficient communication between the host side and the WASM guest.\nImproved performance when dealing with complex data types.\nSimplified API usage for developers."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nDepthPro Demo with 3D Visualization\nHyper_parameter_optimization like bayensian optimization\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20230509-wasm-data-exchange.html#negative-consequences",
-    "href": "decisions/20230509-wasm-data-exchange.html#negative-consequences",
-    "title": "Draft: Exchange data between Godot Engine and WASM using handles",
+    "objectID": "decisions/20231108-postgres-bytea-optimizations.html",
+    "href": "decisions/20231108-postgres-bytea-optimizations.html",
+    "title": "Proposed: PostgreSQL bytea Storage Optimization for V-Sekai’s Edge CDN",
     "section": "",
-    "text": "Additional complexity in the implementation.\nPotential overhead due to reference counting."
+    "text": "Status: Proposed\nDeciders: V-Sekai, Fire\nTags: V-Sekai, PostgreSQL, Edge Hosting, CDN, bytea, TOAST, Optimization\n\n\n\n\nV-Sekai maintains an open-source CDN platform and seeks database optimizations for better performance and scalability.\n\n\n\nHow can V-Sekai enhance binary data storage and access by leveraging PostgreSQL’s bytea type with EXTERNAL storage, independent of Neon’s bottomless feature?\n\n\n\nOptimize the PostgreSQL database schema for CDN data by setting bytea columns to use EXTERNAL storage. This facilitates out-of-line and uncompressed storage of binary data, improving read performance and enabling streaming capabilities.\n\n\n\n\nReduced CPU usage by bypassing compression for binary data.\nEfficient access to specific data segments without loading entire objects, beneficial for streaming content.\n\n\n\n\n\nComplexity in managing custom TOAST configurations.\nNeed for precise database management to ensure performance gains.\n\n\n\n\nDefaulting to the EXTENDED storage type, which compresses bytea data but may not be as efficient for V-Sekai’s use case.\n\n\n\nScenarios requiring compressed storage for binary data, where the EXTENDED storage type might be more appropriate.\n\n\n\nThe PostgreSQL optimization will be implemented by V-Sekai’s team as a crucial part of our infrastructure enhancements.\n\n\n\n\nV-Sekai on GitHub\nBinary Data Performance in PostgreSQL - CYBERTEC​【oaicite:0】​\n\nThis article was assisted by AI."
   },
   {
-    "objectID": "decisions/20230509-wasm-data-exchange.html#option-graveyard",
-    "href": "decisions/20230509-wasm-data-exchange.html#option-graveyard",
-    "title": "Draft: Exchange data between Godot Engine and WASM using handles",
+    "objectID": "decisions/20231108-postgres-bytea-optimizations.html#metadata",
+    "href": "decisions/20231108-postgres-bytea-optimizations.html#metadata",
+    "title": "Proposed: PostgreSQL bytea Storage Optimization for V-Sekai’s Edge CDN",
     "section": "",
-    "text": "N/A"
+    "text": "Status: Proposed\nDeciders: V-Sekai, Fire\nTags: V-Sekai, PostgreSQL, Edge Hosting, CDN, bytea, TOAST, Optimization"
   },
   {
-    "objectID": "decisions/20230509-wasm-data-exchange.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230509-wasm-data-exchange.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Draft: Exchange data between Godot Engine and WASM using handles",
+    "objectID": "decisions/20231108-postgres-bytea-optimizations.html#the-backdrop",
+    "href": "decisions/20231108-postgres-bytea-optimizations.html#the-backdrop",
+    "title": "Proposed: PostgreSQL bytea Storage Optimization for V-Sekai’s Edge CDN",
     "section": "",
-    "text": "No, this enhancement addresses a core limitation and requires changes to the underlying system."
+    "text": "V-Sekai maintains an open-source CDN platform and seeks database optimizations for better performance and scalability."
   },
   {
-    "objectID": "decisions/20230509-wasm-data-exchange.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230509-wasm-data-exchange.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Draft: Exchange data between Godot Engine and WASM using handles",
+    "objectID": "decisions/20231108-postgres-bytea-optimizations.html#the-challenge",
+    "href": "decisions/20231108-postgres-bytea-optimizations.html#the-challenge",
+    "title": "Proposed: PostgreSQL bytea Storage Optimization for V-Sekai’s Edge CDN",
     "section": "",
-    "text": "Yes, this enhancement improves the efficiency and usability of the V-Sekai platform, making it more attractive to developers and users."
+    "text": "How can V-Sekai enhance binary data storage and access by leveraging PostgreSQL’s bytea type with EXTERNAL storage, independent of Neon’s bottomless feature?"
   },
   {
-    "objectID": "decisions/20230509-wasm-data-exchange.html#references",
-    "href": "decisions/20230509-wasm-data-exchange.html#references",
-    "title": "Draft: Exchange data between Godot Engine and WASM using handles",
+    "objectID": "decisions/20231108-postgres-bytea-optimizations.html#the-strategy",
+    "href": "decisions/20231108-postgres-bytea-optimizations.html#the-strategy",
+    "title": "Proposed: PostgreSQL bytea Storage Optimization for V-Sekai’s Edge CDN",
     "section": "",
-    "text": "V-Sekai\nGodot Engine StreamPeer\nGodot Engine Wasm\nGodot Engine WasGo"
+    "text": "Optimize the PostgreSQL database schema for CDN data by setting bytea columns to use EXTERNAL storage. This facilitates out-of-line and uncompressed storage of binary data, improving read performance and enabling streaming capabilities."
   },
   {
-    "objectID": "decisions/20230527-organization.html",
-    "href": "decisions/20230527-organization.html",
-    "title": "Draft: Finding ways to attract users, developers, and creators sustaining V-Sekai",
+    "objectID": "decisions/20231108-postgres-bytea-optimizations.html#the-upside",
+    "href": "decisions/20231108-postgres-bytea-optimizations.html#the-upside",
+    "title": "Proposed: PostgreSQL bytea Storage Optimization for V-Sekai’s Edge CDN",
     "section": "",
-    "text": "Status: draft\nDeciders: V-Sekai, Bioblaze Payne, fire\nTags: V-Sekai, GPT-4\n\n\n\n\nV-Sekai is a project aimed at creating an open-source, federated virtual world platform. The main challenge faced by the V-Sekai project is to compete with established platforms like Roblox, which has a massive user base and a market valuation of $41 billion. The problem lies in finding ways to attract users, developers, and creators while maintaining a sustainable economic model.\n\n\n\nTo address the limitations of V-Sekai and make it competitive with platforms like Roblox, the following solutions are proposed:\n\nImplement a V-Sekai currency system: Convert fiat currency into in-game currency.\nCharge a fee for adding money into the system: This will help generate revenue for the platform and maintain its sustainability.\nCreators are paid directly for their content from V-Sekai.\nPrevent abuse and ensure fair distribution of resources.\n\n\n\n\n\nIntegrate a payment gateway to charge fees for adding money into the system.\nImplement usage limits for players and creators to ensure fair resource allocation.\nOffer creators a reward for their work.\n\n\n\n\n\nAttracting more creators and users to the platform\nGenerating revenue to sustain the platform’s growth\nEnsuring fair distribution of resources among users and creators\nEncouraging creators to have a fair share in the platform.\n\n\n\n\n\nPotential backlash from users due to fees and usage limits\nLegal complexities in treating creators fairly.\nBalancing the currency system to prevent inflation or deflation\n\n\n\n\nImplementing a single currency system: This option was discarded due to the potential for abuse and difficulty in balancing the economy.\n\n\n\nNo, the proposed solution requires significant changes to the platform’s core architecture and cannot be achieved through simple scripting.\n\n\n\nYes, the proposed solution addresses fundamental limitations of the V-Sekai project and is essential for its success. It requires deep integration with the platform’s core systems and should be implemented by the core development team.\n\n\n\n\nV-Sekai"
+    "text": "Reduced CPU usage by bypassing compression for binary data.\nEfficient access to specific data segments without loading entire objects, beneficial for streaming content."
   },
   {
-    "objectID": "decisions/20230527-organization.html#metadata",
-    "href": "decisions/20230527-organization.html#metadata",
-    "title": "Draft: Finding ways to attract users, developers, and creators sustaining V-Sekai",
+    "objectID": "decisions/20231108-postgres-bytea-optimizations.html#the-downside",
+    "href": "decisions/20231108-postgres-bytea-optimizations.html#the-downside",
+    "title": "Proposed: PostgreSQL bytea Storage Optimization for V-Sekai’s Edge CDN",
     "section": "",
-    "text": "Status: draft\nDeciders: V-Sekai, Bioblaze Payne, fire\nTags: V-Sekai, GPT-4"
+    "text": "Complexity in managing custom TOAST configurations.\nNeed for precise database management to ensure performance gains."
   },
   {
-    "objectID": "decisions/20230527-organization.html#context-and-problem-statement",
-    "href": "decisions/20230527-organization.html#context-and-problem-statement",
-    "title": "Draft: Finding ways to attract users, developers, and creators sustaining V-Sekai",
+    "objectID": "decisions/20231108-postgres-bytea-optimizations.html#the-road-not-taken",
+    "href": "decisions/20231108-postgres-bytea-optimizations.html#the-road-not-taken",
+    "title": "Proposed: PostgreSQL bytea Storage Optimization for V-Sekai’s Edge CDN",
     "section": "",
-    "text": "V-Sekai is a project aimed at creating an open-source, federated virtual world platform. The main challenge faced by the V-Sekai project is to compete with established platforms like Roblox, which has a massive user base and a market valuation of $41 billion. The problem lies in finding ways to attract users, developers, and creators while maintaining a sustainable economic model."
+    "text": "Defaulting to the EXTENDED storage type, which compresses bytea data but may not be as efficient for V-Sekai’s use case."
   },
   {
-    "objectID": "decisions/20230527-organization.html#proposed-solution",
-    "href": "decisions/20230527-organization.html#proposed-solution",
-    "title": "Draft: Finding ways to attract users, developers, and creators sustaining V-Sekai",
+    "objectID": "decisions/20231108-postgres-bytea-optimizations.html#the-infrequent-use-case",
+    "href": "decisions/20231108-postgres-bytea-optimizations.html#the-infrequent-use-case",
+    "title": "Proposed: PostgreSQL bytea Storage Optimization for V-Sekai’s Edge CDN",
     "section": "",
-    "text": "To address the limitations of V-Sekai and make it competitive with platforms like Roblox, the following solutions are proposed:\n\nImplement a V-Sekai currency system: Convert fiat currency into in-game currency.\nCharge a fee for adding money into the system: This will help generate revenue for the platform and maintain its sustainability.\nCreators are paid directly for their content from V-Sekai.\nPrevent abuse and ensure fair distribution of resources."
+    "text": "Scenarios requiring compressed storage for binary data, where the EXTENDED storage type might be more appropriate."
   },
   {
-    "objectID": "decisions/20230527-organization.html#implementation",
-    "href": "decisions/20230527-organization.html#implementation",
-    "title": "Draft: Finding ways to attract users, developers, and creators sustaining V-Sekai",
+    "objectID": "decisions/20231108-postgres-bytea-optimizations.html#in-core-and-done-by-us",
+    "href": "decisions/20231108-postgres-bytea-optimizations.html#in-core-and-done-by-us",
+    "title": "Proposed: PostgreSQL bytea Storage Optimization for V-Sekai’s Edge CDN",
     "section": "",
-    "text": "Integrate a payment gateway to charge fees for adding money into the system.\nImplement usage limits for players and creators to ensure fair resource allocation.\nOffer creators a reward for their work."
+    "text": "The PostgreSQL optimization will be implemented by V-Sekai’s team as a crucial part of our infrastructure enhancements."
   },
   {
-    "objectID": "decisions/20230527-organization.html#positive-consequences",
-    "href": "decisions/20230527-organization.html#positive-consequences",
-    "title": "Draft: Finding ways to attract users, developers, and creators sustaining V-Sekai",
+    "objectID": "decisions/20231108-postgres-bytea-optimizations.html#further-reading",
+    "href": "decisions/20231108-postgres-bytea-optimizations.html#further-reading",
+    "title": "Proposed: PostgreSQL bytea Storage Optimization for V-Sekai’s Edge CDN",
     "section": "",
-    "text": "Attracting more creators and users to the platform\nGenerating revenue to sustain the platform’s growth\nEnsuring fair distribution of resources among users and creators\nEncouraging creators to have a fair share in the platform."
+    "text": "V-Sekai on GitHub\nBinary Data Performance in PostgreSQL - CYBERTEC​【oaicite:0】​\n\nThis article was assisted by AI."
   },
   {
-    "objectID": "decisions/20230527-organization.html#negative-consequences",
-    "href": "decisions/20230527-organization.html#negative-consequences",
-    "title": "Draft: Finding ways to attract users, developers, and creators sustaining V-Sekai",
+    "objectID": "decisions/20230429-git-subrepo-challenges.html",
+    "href": "decisions/20230429-git-subrepo-challenges.html",
+    "title": "Accepted: Challenges in managing and synchronizing multiple assets and libraries across different git repositories",
     "section": "",
-    "text": "Potential backlash from users due to fees and usage limits\nLegal complexities in treating creators fairly.\nBalancing the currency system to prevent inflation or deflation"
+    "text": "Accepted: Challenges in managing and synchronizing multiple assets and libraries across different git repositories\n\nMetadata\n\nStatus: accepted \nDeciders: V-Sekai,fire\nTags: V-Sekai,chatgpt4 summary,\n\n\n\nContext and Problem Statement\nV-Sekai projects currently face challenges in managing and synchronizing multiple assets and libraries across different branches. How can we improve the workflow to better maintain the project’s organization and compatibility?\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nImplement a Git subrepo management system to separate assets and libraries, enabling easier tracking and synchronization between branches. This solution streamlines the development process\n\n\nDescribe how your proposal will work with code, pseudo-code, mock-ups, or diagrams\nConfigure the Git subrepo to automatically update and synchronize with the main project.\nUse the Git subrepo in each branch to maintain consistent asset and library versions.\nAvoid storing godot and modules inside of the v-sekai-game.\n\n\nPositive Consequences\n\nImproved organization and compatibility of assets and libraries across branches.\nSimplified workflow for project updates and synchronization.\n\n\n\nNegative Consequences\n\nPotential learning curve for developers unfamiliar with Git subrepo management.\nPossible limitations in implementing other features.\n\n\n\nOption graveyard\nWorkarounds using scripts may be possible, but they are likely to be less efficient and more prone to errors compared to a Git subrepo management system.\n\n\nIf this enhancement will be used infrequently, can it be worked around with a few lines of script?\nNot a few lines of code. It is also devops.\n\n\nIs there a reason why this should be core and done by us?\nIntegrating a Git subrepo management system as a core feature ensures consistency and maintainability across the entire V-Sekai project. It promotes better collaboration among team members and streamlines the development process.\n\n\nReferences\n\nV-Sekai\nGit Subrepo Documentation"
   },
   {
-    "objectID": "decisions/20230527-organization.html#option-graveyard",
-    "href": "decisions/20230527-organization.html#option-graveyard",
-    "title": "Draft: Finding ways to attract users, developers, and creators sustaining V-Sekai",
+    "objectID": "decisions/20221006-rename-to-main.html",
+    "href": "decisions/20221006-rename-to-main.html",
+    "title": "Proposed: Rename master to godot3 and main to godot4",
     "section": "",
-    "text": "Implementing a single currency system: This option was discarded due to the potential for abuse and difficulty in balancing the economy."
+    "text": "Status: proposed \nDeciders: V-Sekai,lyuma,fire\nTags: V-Sekai,\n\n\n\nNot all the branches are released and are currently named godot4. They should be renamed to main.\n\n\n\nRename all godot4 branches to be main for v-sekai-game.\n\n\n\niFire (he, him) — Today at 16:11\nneed some consensus. I think that given v-sekai-game has only one branch it should be named\nLyuma — Today at 16:11\nI agree provided we do the same with the submodules\n\n\n\n\ncohersion\n\n\n\n\n\nchange\n\n\n\n\n\nDo nothing.\n\n\n\n\nCode organization.\n\n\n\nWe own the repos.\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230527-organization.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230527-organization.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Draft: Finding ways to attract users, developers, and creators sustaining V-Sekai",
+    "objectID": "decisions/20221006-rename-to-main.html#context-and-problem-statement",
+    "href": "decisions/20221006-rename-to-main.html#context-and-problem-statement",
+    "title": "Proposed: Rename master to godot3 and main to godot4",
     "section": "",
-    "text": "No, the proposed solution requires significant changes to the platform’s core architecture and cannot be achieved through simple scripting."
+    "text": "Not all the branches are released and are currently named godot4. They should be renamed to main."
   },
   {
-    "objectID": "decisions/20230527-organization.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230527-organization.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Draft: Finding ways to attract users, developers, and creators sustaining V-Sekai",
+    "objectID": "decisions/20221006-rename-to-main.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20221006-rename-to-main.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Proposed: Rename master to godot3 and main to godot4",
     "section": "",
-    "text": "Yes, the proposed solution addresses fundamental limitations of the V-Sekai project and is essential for its success. It requires deep integration with the platform’s core systems and should be implemented by the core development team."
+    "text": "Rename all godot4 branches to be main for v-sekai-game."
   },
   {
-    "objectID": "decisions/20230527-organization.html#references",
-    "href": "decisions/20230527-organization.html#references",
-    "title": "Draft: Finding ways to attract users, developers, and creators sustaining V-Sekai",
+    "objectID": "decisions/20221006-rename-to-main.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20221006-rename-to-main.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Rename master to godot3 and main to godot4",
     "section": "",
-    "text": "V-Sekai"
+    "text": "iFire (he, him) — Today at 16:11\nneed some consensus. I think that given v-sekai-game has only one branch it should be named\nLyuma — Today at 16:11\nI agree provided we do the same with the submodules"
   },
   {
-    "objectID": "decisions/20211005-create-add-spring-bones-to-vrm-models.html",
-    "href": "decisions/20211005-create-add-spring-bones-to-vrm-models.html",
-    "title": "Proposed: Create a standard procedure from adding spring bones to VRM models.",
+    "objectID": "decisions/20221006-rename-to-main.html#positive-consequences",
+    "href": "decisions/20221006-rename-to-main.html#positive-consequences",
+    "title": "Proposed: Rename master to godot3 and main to godot4",
     "section": "",
-    "text": "Create a standard operating procedure from adding spring bones to VRM models.\n\n\n\nBy adding spring bones the body doesn’t clip through clothing or hair.\n\n\n\nSecondary is a node under the root.\nUse VRM Spring Bone Collider Group to stop spring bones from clipping with the skeleton.\nAdd the root bones of the armature you want to animate.\nIs it possible to generate a humanoid collider groups?\n\n\n\nInstructions are needed, automation is work.\n\n\n\nNo response\n\n\n\nNo response\n\n\n\nI don’t know and it’s in my area so I need to know.\n\n\n\n\nLyuma has an upside down spring bone arrangement to avoid flipping.\nhttps://gist.github.com/emilianavt/51d8399987d67544fdebfe2ebd9a5149\nhttps://sator-imaging.booth.pm/items/2254383\nhttps://github.com/yuzu-unity/HumanoidCollider/raw/master/HumanoidCollider.unitypackage\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "cohersion"
   },
   {
-    "objectID": "decisions/20211005-create-add-spring-bones-to-vrm-models.html#context-and-problem-statement",
-    "href": "decisions/20211005-create-add-spring-bones-to-vrm-models.html#context-and-problem-statement",
-    "title": "Proposed: Create a standard procedure from adding spring bones to VRM models.",
+    "objectID": "decisions/20221006-rename-to-main.html#negative-consequences",
+    "href": "decisions/20221006-rename-to-main.html#negative-consequences",
+    "title": "Proposed: Rename master to godot3 and main to godot4",
     "section": "",
-    "text": "Create a standard operating procedure from adding spring bones to VRM models."
+    "text": "change"
   },
   {
-    "objectID": "decisions/20211005-create-add-spring-bones-to-vrm-models.html#describe-the-feature-enhancement-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20211005-create-add-spring-bones-to-vrm-models.html#describe-the-feature-enhancement-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: Create a standard procedure from adding spring bones to VRM models.",
+    "objectID": "decisions/20221006-rename-to-main.html#option-graveyard",
+    "href": "decisions/20221006-rename-to-main.html#option-graveyard",
+    "title": "Proposed: Rename master to godot3 and main to godot4",
     "section": "",
-    "text": "By adding spring bones the body doesn’t clip through clothing or hair."
+    "text": "Do nothing."
   },
   {
-    "objectID": "decisions/20211005-create-add-spring-bones-to-vrm-models.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-andor-diagrams",
-    "href": "decisions/20211005-create-add-spring-bones-to-vrm-models.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-andor-diagrams",
-    "title": "Proposed: Create a standard procedure from adding spring bones to VRM models.",
+    "objectID": "decisions/20221006-rename-to-main.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20221006-rename-to-main.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Rename master to godot3 and main to godot4",
     "section": "",
-    "text": "Secondary is a node under the root.\nUse VRM Spring Bone Collider Group to stop spring bones from clipping with the skeleton.\nAdd the root bones of the armature you want to animate.\nIs it possible to generate a humanoid collider groups?"
+    "text": "Code organization."
   },
   {
-    "objectID": "decisions/20211005-create-add-spring-bones-to-vrm-models.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20211005-create-add-spring-bones-to-vrm-models.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Create a standard procedure from adding spring bones to VRM models.",
+    "objectID": "decisions/20221006-rename-to-main.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20221006-rename-to-main.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Rename master to godot3 and main to godot4",
     "section": "",
-    "text": "Instructions are needed, automation is work."
+    "text": "We own the repos."
   },
   {
-    "objectID": "decisions/20211005-create-add-spring-bones-to-vrm-models.html#positive-consequences",
-    "href": "decisions/20211005-create-add-spring-bones-to-vrm-models.html#positive-consequences",
-    "title": "Proposed: Create a standard procedure from adding spring bones to VRM models.",
+    "objectID": "decisions/20221006-rename-to-main.html#derivative-license",
+    "href": "decisions/20221006-rename-to-main.html#derivative-license",
+    "title": "Proposed: Rename master to godot3 and main to godot4",
     "section": "",
-    "text": "No response"
+    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20211005-create-add-spring-bones-to-vrm-models.html#negative-consequences",
-    "href": "decisions/20211005-create-add-spring-bones-to-vrm-models.html#negative-consequences",
-    "title": "Proposed: Create a standard procedure from adding spring bones to VRM models.",
+    "objectID": "decisions/20240717-core-vsekai-scripting.html",
+    "href": "decisions/20240717-core-vsekai-scripting.html",
+    "title": "Proposal: Core V-Sekai Scripting with Wasm",
     "section": "",
-    "text": "No response"
+    "text": "The V-Sekai project aims to enhance the Godot Engine with social VR functionality. Currently, the project uses a forked version of the Godot Engine, which complicates development and maintenance due to frequent updates from the main Godot repository.\n\n\n\nThe V-Sekai team faces challenges with maintaining a forked version of the Godot Engine. Some team members prefer using the stock Godot Engine to avoid long compilation times and complex build processes. Additionally, there is a need for faster and more secure scripting capabilities than what GDScript offers.\n\n\n\nIf we move all core scripts to Wasm, we’ll need to make only one GDExtension, and then it will never change. So it will be one build that we can all share. We will only need to update when we want a new update from the main Godot Engine repository.\nIt might be hard, but encapsulating complex types is a bridge we’re going to have to cross no matter what.\nMMMaellon originally thought the reason why we want to move to Wasm is because the team doesn’t want to edit the C++ code. Perfectly matching the old API sounds really, really hard. But if we’re allowed to take shortcuts and figure out workarounds, MMMaellon thinks making a Wasm layer that allows us to do enough is doable. As long as the bar isn’t that it has to be an exact perfect replica of the old API.\nWe propose separating the core scripts into WebAssembly (Wasm) modules. This approach allows us to use the stock Godot Engine while leveraging the performance benefits of Wasm.\nThe core scripts will be loaded as Wasm modules, and a single GDExtension will handle the integration between Godot and the Wasm runtime.\n\n\n\nCore Scripts in Wasm: Move all core scripts to Wasm modules. These scripts will handle essential functionalities like security checks and editor tools.\nGDExtension for Wasm Integration: Develop a GDExtension that loads and executes the Wasm modules. This extension will act as a bridge between Godot and the Wasm runtime.\nSingle Binary Distribution: By using Wasm, we can distribute a single binary executable that includes the GDExtension and Wasm modules, simplifying the deployment process.\n\n\n\n\n\n\nPerformance: Wasm provides near-native performance, making it faster than GDScript.\nSecurity: Wasm’s sandboxed environment enhances security by isolating the execution of scripts.\nMaintainability: Using the stock Godot Engine reduces the burden of maintaining a forked version and simplifies updates.\nFlexibility: Developers can write core scripts in languages that compile to Wasm, such as C++ or Rust.\n\n\n\n\n\nComplexity: Developing and integrating Wasm modules adds complexity to the project.\nLearning Curve: Team members may need to learn new technologies and tools related to Wasm.\n\n\n\n\n\nSticking with Forked Godot: Continuing to use a forked version of Godot would require ongoing maintenance and could deter contributors.\nUsing Only GDExtension: While GDExtension provides native performance, it requires code signing and can be cumbersome to manage across multiple modules.\n\n\n\n\nIn scenarios where the performance and security benefits of Wasm are not critical, simpler scripting solutions like GDScript or native GDExtensions might suffice.\n\n\n\nThis proposal involves significant changes to the core architecture of the V-Sekai project. The development team will be responsible for implementing and maintaining the Wasm integration and GDExtension.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\nFire\nMMMaellon\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20211005-create-add-spring-bones-to-vrm-models.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20211005-create-add-spring-bones-to-vrm-models.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Create a standard procedure from adding spring bones to VRM models.",
+    "objectID": "decisions/20240717-core-vsekai-scripting.html#the-context",
+    "href": "decisions/20240717-core-vsekai-scripting.html#the-context",
+    "title": "Proposal: Core V-Sekai Scripting with Wasm",
     "section": "",
-    "text": "I don’t know and it’s in my area so I need to know."
+    "text": "The V-Sekai project aims to enhance the Godot Engine with social VR functionality. Currently, the project uses a forked version of the Godot Engine, which complicates development and maintenance due to frequent updates from the main Godot repository."
   },
   {
-    "objectID": "decisions/20211005-create-add-spring-bones-to-vrm-models.html#references",
-    "href": "decisions/20211005-create-add-spring-bones-to-vrm-models.html#references",
-    "title": "Proposed: Create a standard procedure from adding spring bones to VRM models.",
+    "objectID": "decisions/20240717-core-vsekai-scripting.html#the-problem-statement",
+    "href": "decisions/20240717-core-vsekai-scripting.html#the-problem-statement",
+    "title": "Proposal: Core V-Sekai Scripting with Wasm",
     "section": "",
-    "text": "Lyuma has an upside down spring bone arrangement to avoid flipping.\nhttps://gist.github.com/emilianavt/51d8399987d67544fdebfe2ebd9a5149\nhttps://sator-imaging.booth.pm/items/2254383\nhttps://github.com/yuzu-unity/HumanoidCollider/raw/master/HumanoidCollider.unitypackage"
+    "text": "The V-Sekai team faces challenges with maintaining a forked version of the Godot Engine. Some team members prefer using the stock Godot Engine to avoid long compilation times and complex build processes. Additionally, there is a need for faster and more secure scripting capabilities than what GDScript offers."
   },
   {
-    "objectID": "decisions/20211005-create-add-spring-bones-to-vrm-models.html#derivative-license",
-    "href": "decisions/20211005-create-add-spring-bones-to-vrm-models.html#derivative-license",
-    "title": "Proposed: Create a standard procedure from adding spring bones to VRM models.",
+    "objectID": "decisions/20240717-core-vsekai-scripting.html#proposed-solution",
+    "href": "decisions/20240717-core-vsekai-scripting.html#proposed-solution",
+    "title": "Proposal: Core V-Sekai Scripting with Wasm",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "If we move all core scripts to Wasm, we’ll need to make only one GDExtension, and then it will never change. So it will be one build that we can all share. We will only need to update when we want a new update from the main Godot Engine repository.\nIt might be hard, but encapsulating complex types is a bridge we’re going to have to cross no matter what.\nMMMaellon originally thought the reason why we want to move to Wasm is because the team doesn’t want to edit the C++ code. Perfectly matching the old API sounds really, really hard. But if we’re allowed to take shortcuts and figure out workarounds, MMMaellon thinks making a Wasm layer that allows us to do enough is doable. As long as the bar isn’t that it has to be an exact perfect replica of the old API.\nWe propose separating the core scripts into WebAssembly (Wasm) modules. This approach allows us to use the stock Godot Engine while leveraging the performance benefits of Wasm.\nThe core scripts will be loaded as Wasm modules, and a single GDExtension will handle the integration between Godot and the Wasm runtime.\n\n\n\nCore Scripts in Wasm: Move all core scripts to Wasm modules. These scripts will handle essential functionalities like security checks and editor tools.\nGDExtension for Wasm Integration: Develop a GDExtension that loads and executes the Wasm modules. This extension will act as a bridge between Godot and the Wasm runtime.\nSingle Binary Distribution: By using Wasm, we can distribute a single binary executable that includes the GDExtension and Wasm modules, simplifying the deployment process."
   },
   {
-    "objectID": "decisions/20230125-provide-metadata-to-match-compatibile-maps-and-avatars.html",
-    "href": "decisions/20230125-provide-metadata-to-match-compatibile-maps-and-avatars.html",
-    "title": "Proposed: Provide metadata to pre-check if maps and avatars are compatible to load",
+    "objectID": "decisions/20240717-core-vsekai-scripting.html#the-benefits",
+    "href": "decisions/20240717-core-vsekai-scripting.html#the-benefits",
+    "title": "Proposal: Core V-Sekai Scripting with Wasm",
     "section": "",
-    "text": "Proposed: Provide metadata to pre-check if maps and avatars are compatible to load\n\nMetadata\n\nStatus: proposed \nDeciders: V-Sekai,fire,lyuma\nTags: V-Sekai,\n\n\n\nContext and Problem Statement\nWe don’t know which are maps and avatars are compatible to load.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\n\nAdd date and version number to maps list\n\nCan also be add xmp metadata packets to each packed scene.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nWhen the user presses launches the game, there should be no unnecessary steps.\n\n\nPositive Consequences\nIt is easier to pick content that is loadable.\n\n\nNegative Consequences\nWe cannot get other features in.\n\n\nOption graveyard\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\n\nthis requires a server change\nthis requires a godot engine change\n\n\n\nIs there a reason why this should be core and done by us?\nUsability is a core feature.\n\n\nReferences\n\nV-Sekai\nKHR_xmp_json_ld"
+    "text": "Performance: Wasm provides near-native performance, making it faster than GDScript.\nSecurity: Wasm’s sandboxed environment enhances security by isolating the execution of scripts.\nMaintainability: Using the stock Godot Engine reduces the burden of maintaining a forked version and simplifies updates.\nFlexibility: Developers can write core scripts in languages that compile to Wasm, such as C++ or Rust."
   },
   {
-    "objectID": "decisions/20231104-flatbuffer_packed_scenes.html",
-    "href": "decisions/20231104-flatbuffer_packed_scenes.html",
-    "title": "Rejected: Merge Scene Tool for Godot Editor with FlatBuffer-based JSON Serialization",
+    "objectID": "decisions/20240717-core-vsekai-scripting.html#the-downsides",
+    "href": "decisions/20240717-core-vsekai-scripting.html#the-downsides",
+    "title": "Proposal: Core V-Sekai Scripting with Wasm",
     "section": "",
-    "text": "In collaborative projects, team members may edit the same scene in different ways. Version control systems (VCS) like Git can help manage these modifications through merging. However, merging scenes (TSCN format) can be challenging due to their complex semantics and potential for corruption.\n\n\n\nTo prevent scene corruption after merging, the Godot Editor should provide a merge scene window that allows users to merge TSCN files. This tool should:\n\nDetect Git merge conflict placeholders (&lt;&lt;&lt;&lt;&lt;&lt;&lt;, =======, &gt;&gt;&gt;&gt;&gt;&gt;&gt;)\nReconstruct local and remote scenes\nDisplay a merged scene tree with actions to accept or discard changes, or choose between local and remote versions\n\nThe merge tool should be intelligent enough to detect node movements, renaming, and other complex scene semantics. It should also allow users to edit the merged scene before saving it.\n\n\nTo ensure efficient serialization of the internal state of the merge tool at the start, in between, and at the end, FlatBuffer-based JSON should be used. This will allow for faster processing and better performance while maintaining human-readability.\n\n\n\n\nWhile this feature could be implemented as an add-on, a merge tool is a common feature in modern IDEs and should be fully integrated into the Godot Editor for a seamless user experience."
+    "text": "Complexity: Developing and integrating Wasm modules adds complexity to the project.\nLearning Curve: Team members may need to learn new technologies and tools related to Wasm."
   },
   {
-    "objectID": "decisions/20231104-flatbuffer_packed_scenes.html#problem-merging-scenes-in-collaborative-projects",
-    "href": "decisions/20231104-flatbuffer_packed_scenes.html#problem-merging-scenes-in-collaborative-projects",
-    "title": "Rejected: Merge Scene Tool for Godot Editor with FlatBuffer-based JSON Serialization",
+    "objectID": "decisions/20240717-core-vsekai-scripting.html#the-road-not-taken",
+    "href": "decisions/20240717-core-vsekai-scripting.html#the-road-not-taken",
+    "title": "Proposal: Core V-Sekai Scripting with Wasm",
     "section": "",
-    "text": "In collaborative projects, team members may edit the same scene in different ways. Version control systems (VCS) like Git can help manage these modifications through merging. However, merging scenes (TSCN format) can be challenging due to their complex semantics and potential for corruption."
+    "text": "Sticking with Forked Godot: Continuing to use a forked version of Godot would require ongoing maintenance and could deter contributors.\nUsing Only GDExtension: While GDExtension provides native performance, it requires code signing and can be cumbersome to manage across multiple modules."
   },
   {
-    "objectID": "decisions/20231104-flatbuffer_packed_scenes.html#solution-integrate-a-merge-scene-tool-in-godot-editor",
-    "href": "decisions/20231104-flatbuffer_packed_scenes.html#solution-integrate-a-merge-scene-tool-in-godot-editor",
-    "title": "Rejected: Merge Scene Tool for Godot Editor with FlatBuffer-based JSON Serialization",
+    "objectID": "decisions/20240717-core-vsekai-scripting.html#the-infrequent-use-case",
+    "href": "decisions/20240717-core-vsekai-scripting.html#the-infrequent-use-case",
+    "title": "Proposal: Core V-Sekai Scripting with Wasm",
     "section": "",
-    "text": "To prevent scene corruption after merging, the Godot Editor should provide a merge scene window that allows users to merge TSCN files. This tool should:\n\nDetect Git merge conflict placeholders (&lt;&lt;&lt;&lt;&lt;&lt;&lt;, =======, &gt;&gt;&gt;&gt;&gt;&gt;&gt;)\nReconstruct local and remote scenes\nDisplay a merged scene tree with actions to accept or discard changes, or choose between local and remote versions\n\nThe merge tool should be intelligent enough to detect node movements, renaming, and other complex scene semantics. It should also allow users to edit the merged scene before saving it.\n\n\nTo ensure efficient serialization of the internal state of the merge tool at the start, in between, and at the end, FlatBuffer-based JSON should be used. This will allow for faster processing and better performance while maintaining human-readability."
+    "text": "In scenarios where the performance and security benefits of Wasm are not critical, simpler scripting solutions like GDScript or native GDExtensions might suffice."
   },
   {
-    "objectID": "decisions/20231104-flatbuffer_packed_scenes.html#reason-for-core-integration",
-    "href": "decisions/20231104-flatbuffer_packed_scenes.html#reason-for-core-integration",
-    "title": "Rejected: Merge Scene Tool for Godot Editor with FlatBuffer-based JSON Serialization",
+    "objectID": "decisions/20240717-core-vsekai-scripting.html#in-core-and-done-by-us",
+    "href": "decisions/20240717-core-vsekai-scripting.html#in-core-and-done-by-us",
+    "title": "Proposal: Core V-Sekai Scripting with Wasm",
     "section": "",
-    "text": "While this feature could be implemented as an add-on, a merge tool is a common feature in modern IDEs and should be fully integrated into the Godot Editor for a seamless user experience."
+    "text": "This proposal involves significant changes to the core architecture of the V-Sekai project. The development team will be responsible for implementing and maintaining the Wasm integration and GDExtension."
   },
   {
-    "objectID": "decisions/20231104-flatbuffer_packed_scenes.html#problem-limited-scene-file-format-options",
-    "href": "decisions/20231104-flatbuffer_packed_scenes.html#problem-limited-scene-file-format-options",
-    "title": "Rejected: Merge Scene Tool for Godot Editor with FlatBuffer-based JSON Serialization",
-    "section": "Problem: Limited Scene File Format Options",
-    "text": "Problem: Limited Scene File Format Options\nWhen working on a project related to Godot, such as game development or add-ons, you may encounter limitations with the current scene file formats:\n\nescn: For scenes created by external tools (e.g., importing from Blender)\nscn: Binary format, small but not very useful when collaborating on a project\ntscn: Textual format, INI/TOML-like syntax, human-readable, and encouraged for use\n\nThe TSCN format is proprietary and not widely used, leading to issues such as difficulty editing scenes outside of the Godot Editor and a lack of supporting tools like linters or syntax checkers."
+    "objectID": "decisions/20240717-core-vsekai-scripting.html#status",
+    "href": "decisions/20240717-core-vsekai-scripting.html#status",
+    "title": "Proposal: Core V-Sekai Scripting with Wasm",
+    "section": "",
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20231104-flatbuffer_packed_scenes.html#solution-support-flatbuffer-based-json-as-an-alternative-human-readable-file-format",
-    "href": "decisions/20231104-flatbuffer_packed_scenes.html#solution-support-flatbuffer-based-json-as-an-alternative-human-readable-file-format",
-    "title": "Rejected: Merge Scene Tool for Godot Editor with FlatBuffer-based JSON Serialization",
-    "section": "Solution: Support FlatBuffer-based JSON as an Alternative Human-Readable File Format",
-    "text": "Solution: Support FlatBuffer-based JSON as an Alternative Human-Readable File Format\nTo overcome these limitations, it would be beneficial for Godot to support alternative human-readable file formats, such as FlatBuffer-based JSON. FlatBuffers provide a more efficient way to serialize and deserialize data compared to standard JSON while still being human-readable.\nThis feature should be part of the core engine to ensure official support and seamless integration.\nUse the extension FBJSCN."
+    "objectID": "decisions/20240717-core-vsekai-scripting.html#decision-makers",
+    "href": "decisions/20240717-core-vsekai-scripting.html#decision-makers",
+    "title": "Proposal: Core V-Sekai Scripting with Wasm",
+    "section": "",
+    "text": "V-Sekai development team\nFire\nMMMaellon"
   },
   {
-    "objectID": "decisions/20240626-update-python3-macos-certicates.html",
-    "href": "decisions/20240626-update-python3-macos-certicates.html",
-    "title": "Proposed: Update python3 macOS Certificates",
+    "objectID": "decisions/20240717-core-vsekai-scripting.html#tags",
+    "href": "decisions/20240717-core-vsekai-scripting.html#tags",
+    "title": "Proposal: Core V-Sekai Scripting with Wasm",
     "section": "",
-    "text": "In the current scenario, all Python network certificates are not functioning as expected. This is causing a significant hindrance in the smooth execution of network-related tasks and operations.\n\n\n\nAll python network certificates don’t work on the Macos.\n\n\n\nHere is a Python script that installs or updates a set of default Root Certificates for the SSL module using the certificates provided by the certifi package:\n# Install_Certificates.command\n# install_certifi.py\n#\n# sample script to install or update a set of default Root Certificates\n# for the ssl module.  Uses the certificates provided by the certifi package:\n#       https://pypi.python.org/pypi/certifi\n\nimport os\nimport os.path\nimport ssl\nimport stat\nimport subprocess\nimport sys\n\nSTAT_0o775 = ( stat.S_IRUSR | stat.S_IWUSR | stat.S_IXUSR\n             | stat.S_IRGRP | stat.S_IWGRP | stat.S_IXGRP\n             | stat.S_IROTH |                stat.S_IXOTH )\n\n\ndef main():\n    openssl_dir, openssl_cafile = os.path.split(\n        ssl.get_default_verify_paths().openssl_cafile)\n\n    print(\" -- pip install --upgrade certifi\")\n    subprocess.check_call([sys.executable,\n        \"-E\", \"-s\", \"-m\", \"pip\", \"install\", \"--upgrade\", \"certifi\"])\n\n    import certifi\n\n    # change working directory to the default SSL directory\n    os.chdir(openssl_dir)\n    relpath_to_certifi_cafile = os.path.relpath(certifi.where())\n    print(\" -- removing any existing file or link\")\n    try:\n        os.remove(openssl_cafile)\n    except FileNotFoundError:\n        pass\n    print(\" -- creating symlink to certifi certificate bundle\")\n    os.symlink(relpath_to_certifi_cafile, openssl_cafile)\n    print(\" -- setting permissions\")\n    os.chmod(openssl_cafile, STAT_0o775)\n    print(\" -- update complete\")\n\nif __name__ == '__main__':\n    main()\n\n\n\nThe proposed solution will ensure that the Python network certificates are updated and functioning correctly. This will facilitate smooth network operations and tasks.\n\n\n\nThere might be some initial downtime during the update process. Also, any issues with the certifi package could potentially affect the certificate update process.\n\n\n\nAn alternative approach could have been to manually update each certificate. However, this would have been a time-consuming and error-prone process.\n\n\n\nThis solution may not be applicable for systems that do not use Python or where network certificates are managed differently.\n\n\n\nThe proposed solution is core to our operations as it directly impacts the functionality of our network operations. The implementation will be done by us, the V-Sekai development team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20240626-update-python3-macos-certicates.html#the-context",
-    "href": "decisions/20240626-update-python3-macos-certicates.html#the-context",
-    "title": "Proposed: Update python3 macOS Certificates",
+    "objectID": "decisions/20240717-core-vsekai-scripting.html#further-reading",
+    "href": "decisions/20240717-core-vsekai-scripting.html#further-reading",
+    "title": "Proposal: Core V-Sekai Scripting with Wasm",
     "section": "",
-    "text": "In the current scenario, all Python network certificates are not functioning as expected. This is causing a significant hindrance in the smooth execution of network-related tasks and operations."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240626-update-python3-macos-certicates.html#the-problem-statement",
-    "href": "decisions/20240626-update-python3-macos-certicates.html#the-problem-statement",
-    "title": "Proposed: Update python3 macOS Certificates",
+    "objectID": "decisions/20230819-train-game.html",
+    "href": "decisions/20230819-train-game.html",
+    "title": "Proposed: Following Tracks: Enhancing VR Train Station Simulation in V-Sekai using Godot Engine",
     "section": "",
-    "text": "All python network certificates don’t work on the Macos."
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, Godot Engine, VR Development\n\n\n\n\nV-Sekai is a platform that specializes in VR development with the Godot engine. It’s currently facing challenges because there isn’t a test game available. The goal is to develop a minimal viable product for a train station simulator. This simulator will focus on avatar rendering, networking simulation, and parented objects in the train.\n\n\n\nThe main problems are the need for precise controls in VR and the ability to render and network large groups of people in VR. This also includes extensive NPC tests with skeletal animation in the Godot engine for VR.\n\n\n\nThe strategy involves adding new features to V-Sekai to address these challenges:\n\nNetworking Avatar Crowds: The aim here is to develop efficient methods for networking large groups of avatars in VR. This will involve creating a system that can handle the high data traffic required for real-time interaction between numerous avatars, while maintaining performance and stability. This could be achieved by implementing advanced networking protocols and optimization techniques to ensure smooth communication between avatars without overloading the network.\n\n\n\n\nIf this strategy is implemented successfully, it could enhance the user experience in VR games developed using the Godot engine. It could also enable the creation of more diverse and complex VR environments.\n\n\n\nThis process may require significant resources and time, and there might be technical limitations.\n\n\n\nAn alternative could have been to use a different game engine that already supports these features. However, this wouldn’t contribute to the improvement of the Godot engine.\n\n\n\nThese improvements might not benefit all types of games or developers. Their relevance depends on the specific needs and goals of each project.\n\n\n\nV-Sekai’s expertise in VR development and understanding of its challenges make it well-suited to lead these improvements. By doing so, V-Sekai can align with developer needs, contribute to the open-source Godot engine, and help build a stronger community around it.\nDespite requiring effort and resources, the potential benefits for both V-Sekai and the wider Godot engine community make it a worthwhile investment.\n\n\n\n\nV-Sekai\nGodot Engine Proposal Discussion\n\nThis article is assisted by AI."
   },
   {
-    "objectID": "decisions/20240626-update-python3-macos-certicates.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240626-update-python3-macos-certicates.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Update python3 macOS Certificates",
+    "objectID": "decisions/20230819-train-game.html#metadata",
+    "href": "decisions/20230819-train-game.html#metadata",
+    "title": "Proposed: Following Tracks: Enhancing VR Train Station Simulation in V-Sekai using Godot Engine",
     "section": "",
-    "text": "Here is a Python script that installs or updates a set of default Root Certificates for the SSL module using the certificates provided by the certifi package:\n# Install_Certificates.command\n# install_certifi.py\n#\n# sample script to install or update a set of default Root Certificates\n# for the ssl module.  Uses the certificates provided by the certifi package:\n#       https://pypi.python.org/pypi/certifi\n\nimport os\nimport os.path\nimport ssl\nimport stat\nimport subprocess\nimport sys\n\nSTAT_0o775 = ( stat.S_IRUSR | stat.S_IWUSR | stat.S_IXUSR\n             | stat.S_IRGRP | stat.S_IWGRP | stat.S_IXGRP\n             | stat.S_IROTH |                stat.S_IXOTH )\n\n\ndef main():\n    openssl_dir, openssl_cafile = os.path.split(\n        ssl.get_default_verify_paths().openssl_cafile)\n\n    print(\" -- pip install --upgrade certifi\")\n    subprocess.check_call([sys.executable,\n        \"-E\", \"-s\", \"-m\", \"pip\", \"install\", \"--upgrade\", \"certifi\"])\n\n    import certifi\n\n    # change working directory to the default SSL directory\n    os.chdir(openssl_dir)\n    relpath_to_certifi_cafile = os.path.relpath(certifi.where())\n    print(\" -- removing any existing file or link\")\n    try:\n        os.remove(openssl_cafile)\n    except FileNotFoundError:\n        pass\n    print(\" -- creating symlink to certifi certificate bundle\")\n    os.symlink(relpath_to_certifi_cafile, openssl_cafile)\n    print(\" -- setting permissions\")\n    os.chmod(openssl_cafile, STAT_0o775)\n    print(\" -- update complete\")\n\nif __name__ == '__main__':\n    main()"
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, Godot Engine, VR Development"
   },
   {
-    "objectID": "decisions/20240626-update-python3-macos-certicates.html#the-benefits",
-    "href": "decisions/20240626-update-python3-macos-certicates.html#the-benefits",
-    "title": "Proposed: Update python3 macOS Certificates",
+    "objectID": "decisions/20230819-train-game.html#the-backdrop",
+    "href": "decisions/20230819-train-game.html#the-backdrop",
+    "title": "Proposed: Following Tracks: Enhancing VR Train Station Simulation in V-Sekai using Godot Engine",
     "section": "",
-    "text": "The proposed solution will ensure that the Python network certificates are updated and functioning correctly. This will facilitate smooth network operations and tasks."
+    "text": "V-Sekai is a platform that specializes in VR development with the Godot engine. It’s currently facing challenges because there isn’t a test game available. The goal is to develop a minimal viable product for a train station simulator. This simulator will focus on avatar rendering, networking simulation, and parented objects in the train."
   },
   {
-    "objectID": "decisions/20240626-update-python3-macos-certicates.html#the-downsides",
-    "href": "decisions/20240626-update-python3-macos-certicates.html#the-downsides",
-    "title": "Proposed: Update python3 macOS Certificates",
+    "objectID": "decisions/20230819-train-game.html#the-challenge",
+    "href": "decisions/20230819-train-game.html#the-challenge",
+    "title": "Proposed: Following Tracks: Enhancing VR Train Station Simulation in V-Sekai using Godot Engine",
     "section": "",
-    "text": "There might be some initial downtime during the update process. Also, any issues with the certifi package could potentially affect the certificate update process."
+    "text": "The main problems are the need for precise controls in VR and the ability to render and network large groups of people in VR. This also includes extensive NPC tests with skeletal animation in the Godot engine for VR."
   },
   {
-    "objectID": "decisions/20240626-update-python3-macos-certicates.html#the-road-not-taken",
-    "href": "decisions/20240626-update-python3-macos-certicates.html#the-road-not-taken",
-    "title": "Proposed: Update python3 macOS Certificates",
+    "objectID": "decisions/20230819-train-game.html#the-strategy",
+    "href": "decisions/20230819-train-game.html#the-strategy",
+    "title": "Proposed: Following Tracks: Enhancing VR Train Station Simulation in V-Sekai using Godot Engine",
     "section": "",
-    "text": "An alternative approach could have been to manually update each certificate. However, this would have been a time-consuming and error-prone process."
+    "text": "The strategy involves adding new features to V-Sekai to address these challenges:\n\nNetworking Avatar Crowds: The aim here is to develop efficient methods for networking large groups of avatars in VR. This will involve creating a system that can handle the high data traffic required for real-time interaction between numerous avatars, while maintaining performance and stability. This could be achieved by implementing advanced networking protocols and optimization techniques to ensure smooth communication between avatars without overloading the network."
   },
   {
-    "objectID": "decisions/20240626-update-python3-macos-certicates.html#the-infrequent-use-case",
-    "href": "decisions/20240626-update-python3-macos-certicates.html#the-infrequent-use-case",
-    "title": "Proposed: Update python3 macOS Certificates",
+    "objectID": "decisions/20230819-train-game.html#the-upside",
+    "href": "decisions/20230819-train-game.html#the-upside",
+    "title": "Proposed: Following Tracks: Enhancing VR Train Station Simulation in V-Sekai using Godot Engine",
     "section": "",
-    "text": "This solution may not be applicable for systems that do not use Python or where network certificates are managed differently."
+    "text": "If this strategy is implemented successfully, it could enhance the user experience in VR games developed using the Godot engine. It could also enable the creation of more diverse and complex VR environments."
   },
   {
-    "objectID": "decisions/20240626-update-python3-macos-certicates.html#in-core-and-done-by-us",
-    "href": "decisions/20240626-update-python3-macos-certicates.html#in-core-and-done-by-us",
-    "title": "Proposed: Update python3 macOS Certificates",
+    "objectID": "decisions/20230819-train-game.html#the-downside",
+    "href": "decisions/20230819-train-game.html#the-downside",
+    "title": "Proposed: Following Tracks: Enhancing VR Train Station Simulation in V-Sekai using Godot Engine",
     "section": "",
-    "text": "The proposed solution is core to our operations as it directly impacts the functionality of our network operations. The implementation will be done by us, the V-Sekai development team."
+    "text": "This process may require significant resources and time, and there might be technical limitations."
   },
   {
-    "objectID": "decisions/20240626-update-python3-macos-certicates.html#status",
-    "href": "decisions/20240626-update-python3-macos-certicates.html#status",
-    "title": "Proposed: Update python3 macOS Certificates",
+    "objectID": "decisions/20230819-train-game.html#the-road-not-taken",
+    "href": "decisions/20230819-train-game.html#the-road-not-taken",
+    "title": "Proposed: Following Tracks: Enhancing VR Train Station Simulation in V-Sekai using Godot Engine",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "An alternative could have been to use a different game engine that already supports these features. However, this wouldn’t contribute to the improvement of the Godot engine."
   },
   {
-    "objectID": "decisions/20240626-update-python3-macos-certicates.html#decision-makers",
-    "href": "decisions/20240626-update-python3-macos-certicates.html#decision-makers",
-    "title": "Proposed: Update python3 macOS Certificates",
+    "objectID": "decisions/20230819-train-game.html#the-infrequent-use-case",
+    "href": "decisions/20230819-train-game.html#the-infrequent-use-case",
+    "title": "Proposed: Following Tracks: Enhancing VR Train Station Simulation in V-Sekai using Godot Engine",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "These improvements might not benefit all types of games or developers. Their relevance depends on the specific needs and goals of each project."
   },
   {
-    "objectID": "decisions/20240626-update-python3-macos-certicates.html#tags",
-    "href": "decisions/20240626-update-python3-macos-certicates.html#tags",
-    "title": "Proposed: Update python3 macOS Certificates",
+    "objectID": "decisions/20230819-train-game.html#in-core-and-done-by-us",
+    "href": "decisions/20230819-train-game.html#in-core-and-done-by-us",
+    "title": "Proposed: Following Tracks: Enhancing VR Train Station Simulation in V-Sekai using Godot Engine",
     "section": "",
-    "text": "V-Sekai"
+    "text": "V-Sekai’s expertise in VR development and understanding of its challenges make it well-suited to lead these improvements. By doing so, V-Sekai can align with developer needs, contribute to the open-source Godot engine, and help build a stronger community around it.\nDespite requiring effort and resources, the potential benefits for both V-Sekai and the wider Godot engine community make it a worthwhile investment."
   },
   {
-    "objectID": "decisions/20240626-update-python3-macos-certicates.html#further-reading",
-    "href": "decisions/20240626-update-python3-macos-certicates.html#further-reading",
-    "title": "Proposed: Update python3 macOS Certificates",
+    "objectID": "decisions/20230819-train-game.html#further-reading",
+    "href": "decisions/20230819-train-game.html#further-reading",
+    "title": "Proposed: Following Tracks: Enhancing VR Train Station Simulation in V-Sekai using Godot Engine",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "V-Sekai\nGodot Engine Proposal Discussion\n\nThis article is assisted by AI."
   },
   {
-    "objectID": "decisions/20240611-test-1x-and-4x.html",
-    "href": "decisions/20240611-test-1x-and-4x.html",
-    "title": "Proposed: Managing Multiple Training Runs in Separate Pods",
+    "objectID": "decisions/20240217-documentation-guidelines.html",
+    "href": "decisions/20240217-documentation-guidelines.html",
+    "title": "Proposed: Comprehensive Documentation for V-Sekai",
     "section": "",
-    "text": "We are working on training a model using multiple GPUs. We have encountered issues when trying to run two training runs in the same pod.\n\n\n\nThe problem is that we cannot run multiple GPU training runs in the same pod. This limits our ability to parallelize our training and make full use of our resources.\n\n\n\nBased on the discussion, the proposal is to manage the training runs in separate pods. Specifically:\n\nStart a pod with a single X1 4090 for stable training.\nStart another new pod with 4x 4090 to test the theory that you can only run the multi-GPU once per session.\n\n\n\n\n\nThis approach allows us to run multiple training runs simultaneously, making full use of our resources.\nIt also enables us to isolate the training runs, reducing the risk of one affecting the other.\n\n\n\n\n\nManaging multiple pods might be more complex than managing a single one.\nThere may be additional overhead associated with running multiple pods.\n\n\n\n\n\nWe could have continued trying to run multiple training runs in the same pod, but this was causing issues.\n\n\n\n\n\nThis approach may not be necessary if we only need to run a single training run at a time.\n\n\n\n\n\nThe decision on how to manage the pods and the training runs will be made by us, using our acquired resources and expertise.\n\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "V-Sekai is a project that brings social VR/VRSNS/metaverse components to the Godot Engine. It has numerous features and topics that need comprehensive documentation for both developers and users.\n\n\n\nThe current documentation lacks detailed information about significant features and topics, making it difficult for users and developers to understand and utilize V-Sekai’s full potential.\n\n\n\nWe propose creating dedicated pages for each feature with descriptive titles and bullet lists of essential points. For instance:\n\n\n\nExplanation of XR and Godot\nHow XR works in Godot and how V-Sekai utilizes it\nAchievements possible with this feature/knowledge\nLimitations of the technology affecting our product\n\nFor step-by-step instructions, we will use straightforward language and consistent verbs and phrasing. For example:\n\n\n\n\nOpen the Project -&gt; Project Settings… menu.\nNavigate to Display -&gt; Window in the left column.\nScroll down to the resolution setting.\nClick the numbers to change the resolution (values are in pixels).\n\n\n\n\n\nThis proposal will make it easier for users and developers to understand and use V-Sekai. It will also provide a foundation for further development and improvements.\n\n\n\nCreating comprehensive documentation requires time and resources. However, the benefits outweigh the costs.\n\n\n\nWithout comprehensive documentation, users and developers may struggle to understand and use V-Sekai effectively.\n\n\n\nEven infrequent or advanced features should be documented to ensure all users can fully utilize V-Sekai.\n\n\n\nThis proposal will be implemented by the V-Sekai development team and community stakeholders.\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team, community stakeholders, GDQuest, Fire\n\n\n\n\n\nV-Sekai, Avatar Customization, AI, Facial Expressions\n\n\n\n\n\nV-Sekai · GitHub\nV-Sekai/v-sekai-game\n\nAI assistant Aria assisted with this proposal."
   },
   {
-    "objectID": "decisions/20240611-test-1x-and-4x.html#the-context",
-    "href": "decisions/20240611-test-1x-and-4x.html#the-context",
-    "title": "Proposed: Managing Multiple Training Runs in Separate Pods",
+    "objectID": "decisions/20240217-documentation-guidelines.html#context",
+    "href": "decisions/20240217-documentation-guidelines.html#context",
+    "title": "Proposed: Comprehensive Documentation for V-Sekai",
     "section": "",
-    "text": "We are working on training a model using multiple GPUs. We have encountered issues when trying to run two training runs in the same pod."
+    "text": "V-Sekai is a project that brings social VR/VRSNS/metaverse components to the Godot Engine. It has numerous features and topics that need comprehensive documentation for both developers and users."
   },
   {
-    "objectID": "decisions/20240611-test-1x-and-4x.html#the-problem-statement",
-    "href": "decisions/20240611-test-1x-and-4x.html#the-problem-statement",
-    "title": "Proposed: Managing Multiple Training Runs in Separate Pods",
+    "objectID": "decisions/20240217-documentation-guidelines.html#problem-statement",
+    "href": "decisions/20240217-documentation-guidelines.html#problem-statement",
+    "title": "Proposed: Comprehensive Documentation for V-Sekai",
     "section": "",
-    "text": "The problem is that we cannot run multiple GPU training runs in the same pod. This limits our ability to parallelize our training and make full use of our resources."
+    "text": "The current documentation lacks detailed information about significant features and topics, making it difficult for users and developers to understand and utilize V-Sekai’s full potential."
   },
   {
-    "objectID": "decisions/20240611-test-1x-and-4x.html#proposal",
-    "href": "decisions/20240611-test-1x-and-4x.html#proposal",
-    "title": "Proposed: Managing Multiple Training Runs in Separate Pods",
+    "objectID": "decisions/20240217-documentation-guidelines.html#proposed-solution",
+    "href": "decisions/20240217-documentation-guidelines.html#proposed-solution",
+    "title": "Proposed: Comprehensive Documentation for V-Sekai",
     "section": "",
-    "text": "Based on the discussion, the proposal is to manage the training runs in separate pods. Specifically:\n\nStart a pod with a single X1 4090 for stable training.\nStart another new pod with 4x 4090 to test the theory that you can only run the multi-GPU once per session."
+    "text": "We propose creating dedicated pages for each feature with descriptive titles and bullet lists of essential points. For instance:\n\n\n\nExplanation of XR and Godot\nHow XR works in Godot and how V-Sekai utilizes it\nAchievements possible with this feature/knowledge\nLimitations of the technology affecting our product\n\nFor step-by-step instructions, we will use straightforward language and consistent verbs and phrasing. For example:\n\n\n\n\nOpen the Project -&gt; Project Settings… menu.\nNavigate to Display -&gt; Window in the left column.\nScroll down to the resolution setting.\nClick the numbers to change the resolution (values are in pixels)."
   },
   {
-    "objectID": "decisions/20240611-test-1x-and-4x.html#the-benefits",
-    "href": "decisions/20240611-test-1x-and-4x.html#the-benefits",
-    "title": "Proposed: Managing Multiple Training Runs in Separate Pods",
+    "objectID": "decisions/20240217-documentation-guidelines.html#benefits",
+    "href": "decisions/20240217-documentation-guidelines.html#benefits",
+    "title": "Proposed: Comprehensive Documentation for V-Sekai",
     "section": "",
-    "text": "This approach allows us to run multiple training runs simultaneously, making full use of our resources.\nIt also enables us to isolate the training runs, reducing the risk of one affecting the other."
+    "text": "This proposal will make it easier for users and developers to understand and use V-Sekai. It will also provide a foundation for further development and improvements."
   },
   {
-    "objectID": "decisions/20240611-test-1x-and-4x.html#the-downsides",
-    "href": "decisions/20240611-test-1x-and-4x.html#the-downsides",
-    "title": "Proposed: Managing Multiple Training Runs in Separate Pods",
+    "objectID": "decisions/20240217-documentation-guidelines.html#downsides",
+    "href": "decisions/20240217-documentation-guidelines.html#downsides",
+    "title": "Proposed: Comprehensive Documentation for V-Sekai",
     "section": "",
-    "text": "Managing multiple pods might be more complex than managing a single one.\nThere may be additional overhead associated with running multiple pods."
+    "text": "Creating comprehensive documentation requires time and resources. However, the benefits outweigh the costs."
   },
   {
-    "objectID": "decisions/20240611-test-1x-and-4x.html#the-road-not-taken",
-    "href": "decisions/20240611-test-1x-and-4x.html#the-road-not-taken",
-    "title": "Proposed: Managing Multiple Training Runs in Separate Pods",
+    "objectID": "decisions/20240217-documentation-guidelines.html#the-road-not-taken",
+    "href": "decisions/20240217-documentation-guidelines.html#the-road-not-taken",
+    "title": "Proposed: Comprehensive Documentation for V-Sekai",
     "section": "",
-    "text": "We could have continued trying to run multiple training runs in the same pod, but this was causing issues."
+    "text": "Without comprehensive documentation, users and developers may struggle to understand and use V-Sekai effectively."
   },
   {
-    "objectID": "decisions/20240611-test-1x-and-4x.html#the-infrequent-use-case",
-    "href": "decisions/20240611-test-1x-and-4x.html#the-infrequent-use-case",
-    "title": "Proposed: Managing Multiple Training Runs in Separate Pods",
+    "objectID": "decisions/20240217-documentation-guidelines.html#the-infrequent-use-case",
+    "href": "decisions/20240217-documentation-guidelines.html#the-infrequent-use-case",
+    "title": "Proposed: Comprehensive Documentation for V-Sekai",
     "section": "",
-    "text": "This approach may not be necessary if we only need to run a single training run at a time."
+    "text": "Even infrequent or advanced features should be documented to ensure all users can fully utilize V-Sekai."
   },
   {
-    "objectID": "decisions/20240611-test-1x-and-4x.html#in-core-and-done-by-us",
-    "href": "decisions/20240611-test-1x-and-4x.html#in-core-and-done-by-us",
-    "title": "Proposed: Managing Multiple Training Runs in Separate Pods",
+    "objectID": "decisions/20240217-documentation-guidelines.html#in-core-and-done-by-us",
+    "href": "decisions/20240217-documentation-guidelines.html#in-core-and-done-by-us",
+    "title": "Proposed: Comprehensive Documentation for V-Sekai",
     "section": "",
-    "text": "The decision on how to manage the pods and the training runs will be made by us, using our acquired resources and expertise."
+    "text": "This proposal will be implemented by the V-Sekai development team and community stakeholders."
   },
   {
-    "objectID": "decisions/20240611-test-1x-and-4x.html#status",
-    "href": "decisions/20240611-test-1x-and-4x.html#status",
-    "title": "Proposed: Managing Multiple Training Runs in Separate Pods",
+    "objectID": "decisions/20240217-documentation-guidelines.html#status",
+    "href": "decisions/20240217-documentation-guidelines.html#status",
+    "title": "Proposed: Comprehensive Documentation for V-Sekai",
     "section": "",
     "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20240611-test-1x-and-4x.html#decision-makers",
-    "href": "decisions/20240611-test-1x-and-4x.html#decision-makers",
-    "title": "Proposed: Managing Multiple Training Runs in Separate Pods",
+    "objectID": "decisions/20240217-documentation-guidelines.html#decision-makers",
+    "href": "decisions/20240217-documentation-guidelines.html#decision-makers",
+    "title": "Proposed: Comprehensive Documentation for V-Sekai",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "V-Sekai development team, community stakeholders, GDQuest, Fire"
   },
   {
-    "objectID": "decisions/20240611-test-1x-and-4x.html#tags",
-    "href": "decisions/20240611-test-1x-and-4x.html#tags",
-    "title": "Proposed: Managing Multiple Training Runs in Separate Pods",
+    "objectID": "decisions/20240217-documentation-guidelines.html#tags",
+    "href": "decisions/20240217-documentation-guidelines.html#tags",
+    "title": "Proposed: Comprehensive Documentation for V-Sekai",
     "section": "",
-    "text": "V-Sekai"
+    "text": "V-Sekai, Avatar Customization, AI, Facial Expressions"
   },
   {
-    "objectID": "decisions/20240611-test-1x-and-4x.html#further-reading",
-    "href": "decisions/20240611-test-1x-and-4x.html#further-reading",
-    "title": "Proposed: Managing Multiple Training Runs in Separate Pods",
+    "objectID": "decisions/20240217-documentation-guidelines.html#further-reading",
+    "href": "decisions/20240217-documentation-guidelines.html#further-reading",
+    "title": "Proposed: Comprehensive Documentation for V-Sekai",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "V-Sekai · GitHub\nV-Sekai/v-sekai-game\n\nAI assistant Aria assisted with this proposal."
   },
   {
-    "objectID": "decisions/20230719-dual-databases-cockroachdb-khepri.html",
-    "href": "decisions/20230719-dual-databases-cockroachdb-khepri.html",
-    "title": "Proposed: Game simulation server sidekick process",
+    "objectID": "decisions/20231201-headless-launcher-backend.html",
+    "href": "decisions/20231201-headless-launcher-backend.html",
+    "title": "Proposed: Headless Launcher Backend with Elixir and Server-Side CockroachDB",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, Godot Engine, khepri, elixir\n\n\n\n\nWe want to provide each game server a sidekick process that restarts Godot Engine on crash and acts as a local processor before upload to the source of truth backend database. This will ensure continuous gameplay and data integrity.\n\n\n\nWe propose to use khepri for sidekick server data with an elixir frontend.\nKhepri provides robustness and reliability while Elixir offers scalability and fault-tolerance.\n\n\n\n\nDevelop a sidekick process using khepri that monitors the Godot Engine.\nIn case of a crash, the sidekick process should be able to restart the Godot Engine.\nThe sidekick process should also act as a local processor for game data before it’s uploaded to the backend database.\nImplement an Elixir frontend to interact with the sidekick process.\n\n\n\n\n\nImproved game server stability.\nContinuous gameplay even in the event of a crash.\nEnsured data integrity before upload to the backend database.\n\n\n\n\n\nAdditional development time and resources required.\nPotential complexity in managing the sidekick process.\n\n\n\n\n\nUsing a simple watchdog script: A simple script that monitors the Godot Engine and restarts it in case of a crash. This was rejected due to its inability to act as a local processor for game data before upload.\nRelying on third-party services: There are several third-party services that offer process monitoring and automatic restarts. However, these were rejected due to potential issues with customization, cost, and data privacy.\nBuilding a custom solution from scratch: While this would give us the most control, it was deemed too resource-intensive and unnecessary given the existence of suitable tools like khepri and Elixir.\nDo nothing: The option to maintain the status quo was considered but ultimately rejected due to the negative impact on user experience and data integrity.\n\n\n\n\nNo, this enhancement is fundamental to the stability of the game servers and cannot be achieved with a simple script workaround.\n\n\n\nYes, as this directly impacts the user experience and the integrity of our game data, it is crucial that we have full control over its implementation and maintenance.\n\n\n\n\nV-Sekai"
+    "text": "Status: Proposed\nDeciders: V-Sekai Team\nTags: headless, backend, launcher, updater\n\n\n\n\nIntroduce a headless backend launcher to automate game updates for enhanced gaming experience.\n\n\n\nBuild an updater that is simple yet robust, handling automated game updates in the background.\n\n\n\nThe strategy for this proposal is to develop a headless backend launcher using Elixir and CockroachDB. The main components of the system will be:\nThe Headless CLI will implement desync for data synchronization and provide commands for displaying help information, version information, switching modes, checking current mode, listing all available modes, and updating according to semantic versioning.\nThe Updater Online Service will be a lightweight service that uses Elixir for handling web requests and CockroachDB for persistence. It will integrate the desync protocol and include error handling strategies for failed updates or data synchronization issues.\nThe GUI Launcher will be designed using the Godot Engine and will also integrate the desync protocol. It will feature a basic visual setup with V-Sekai branding.\nThe Game Sample will involve developing a basic visual sample with V-Sekai branding, planning for testing each component to ensure functionality, addressing security concerns including user data protection and secure updates, and discussing scalability potential with increasing users or larger game updates.\nEach table will have its own schema module representing different aspects of the application such as modes, versions, and update processes.\n\n\n\nThis system promotes seamless gaming with high performance and reliability from Elixir and CockroachDB.\n\n\n\nTechnology integration may lead to complex issues and compatibility challenges.\n\n\n\nExternal updaters and manual patches were dismissed for their demanding nature.\n\n\n\nDesign will allow manual update initiation for situations like limited bandwidth.\n\n\n\nThe V-Sekai team will develop and maintain this launcher backend. A detailed maintenance plan will be provided.\n\n\n\nA comprehensive documentation will be created for understanding the system and onboarding new team members.\n\n\n\n\nV-Sekai GitHub - Our efforts in VR using Godot Engine.\nV-Sekai Game Repo - Our open-source VR and social experiences project.\nDesync - Alternative casync implementation.\n\n\n\n\nstateDiagram-v2\n    [*] --&gt; Idle\n    Idle --&gt; CheckForUpdates : Update Triggered\n    CheckForUpdates --&gt; Updating\n    Updating --&gt; Idle : Update Successful\n\n    state CheckForUpdates {\n        [*] --&gt; Checking\n        Checking --&gt; NoUpdateFound\n        NoUpdateFound --&gt; [*]\n\n        Checking --&gt; UpdateAvailable\n        UpdateAvailable --&gt; PreparingUpdate\n        PreparingUpdate --&gt; DownloadingUpdate\n        DownloadingUpdate --&gt; ApplyingUpdate\n        ApplyingUpdate --&gt; FinalizingUpdate\n        FinalizingUpdate --&gt; UpdateSuccessful\n        UpdateSuccessful --&gt; [*]\n    }\n\n    Updating: Update in progress\n    Idle: Waiting for update trigger\nUse Elixir for concurrent services and CockroachDB on the server for data management:\n\nHeadless CLI\n\nImplement desync for data synchronization.\nDetail how desync will be integrated into the service and GUI.\n\n\n# Display help information\nvsekai --help\n\n# Display version information\nvsekai --version\n\n# Switch to a different mode. Modes allow different operations for the software.\nvsekai mode switch --mode_name stable\n\n# Check the current mode.\nvsekai mode current\n\n# List all available modes.\nvsekai mode list\n\n# Always updates according to semantic versioning to the mode.\n./headless-vsekai-v0.1.0.exe --update C:/v-sekai/launcher\n./headless-vsekai-v0.1.1.exe --update C:/v-sekai/launcher\n./headless-vsekai-v0.2.0.exe --update C:/v-sekai/launcher\n\n# Pseudo code for update process\ncheck_launcher_folder()\nvalidate_manifest_file_and_version()\nensure_correct_files_for_update()\ndownload_to_temp()\ndelete_old_and_move_over()\nsetup_registry_values()\n\nUpdater Online Service:\n\nCreate a lightweight updater service.\nUse Elixir for web requests handling.\nUtilize server-side CockroachDB for persistence.\nIntegrate desync protocol in the Service.\nInclude error handling strategy for failed updates or data synchronization issues.\n\nGUI Launcher Creation:\n\nDesign an intuitive Godot Engine GUI launcher.\nIntegrate desync protocol in the GUI.\nDetail the basic visual setup with V-Sekai branding.\n\nGame Setup Efforts:\n\nDevelop a basic visual setup with V-Sekai branding.\nInclude a plan for testing each component to ensure functionality.\nAddress security concerns, including user data protection and secure updates.\nDiscuss scalability potential with increasing users or larger game updates.\n\n\n\n\n\n\ndefmodule VSekaiNebula.Mode do\n  @moduledoc \"\"\"\n  This module represents the `modes` table in the application's database.\n\n  ## Fields\n\n  - `:name`: The name of the mode.\n  - `:is_active`: A boolean indicating whether the mode is active or not.\n  - `:update_to`: Updates to a different mode.\n  - `:id`: A unique identifier for each mode. It is autogenerated and serves as the primary key.\n  \"\"\"\n\n  use Ecto.Schema\n\n  schema \"modes\" do\n    field :name, :string\n    field :is_active, :bool\n    field :update_to, Ecto.UUID\n    field :id, Ecto.UUID, autogenerate: true, primary_key: true\n\n    timestamps()\n  end\n\n  # TODO changeset/2\nend\n\n\n\ndefmodule VSekaiNebula.Version do\n  @moduledoc \"\"\"\n  This module represents the `versions` table in the application's database.\n\n  ## Fields\n\n  - `:version`: The version number.\n  - `:skip_update`: A boolean indicating whether to skip the update or not.\n  - `:manifest_file_uri`: The URI of the manifest file. This is generated server-side to ensure integrity,\n    especially during CI/CD processes. It helps prevent issues such as network errors, mid-process failures,\n    or programming errors causing incorrect checksums or file locations.\n  - `:id`: A unique identifier for each version. It is autogenerated and serves as the primary key.\n\n  ## Associations\n\n  - belongs_to :mode, VSekaiNebula.Mode: Each version is associated with a mode.\n  \"\"\"\n\n  use Ecto.Schema\n\n  schema \"versions\" do\n    field :version, :string\n    field :skip_update, :bool\n    field :manifest_file_uri, :string\n    field :id, Ecto.UUID, autogenerate: true, primary_key: true\n\n    belongs_to :mode, VSekaiNebula.Mode\n\n    timestamps()\n  end\n\n  # TODO changeset/2\nend\n\n\n\ndefmodule VSekaiNebula.Files do\n  @moduledoc \"\"\"\n  This module represents the `files` table in the application's database.\n\n  ## Fields\n\n  - `:file_name`: The name of the file.\n  - `:file_uri`: The URI of the file.\n  - `:file_checksum_hash`: The checksum hash of the file.\n  - `:id`: A unique identifier for each file. It is autogenerated and serves as the primary key.\n\n  ## Associations\n\n  - belongs_to :version, VSekaiNebula.Version: Each file is associated with a version.\n\n  ## Reasoning\n\n  - Timestamps are removed as they are not necessary for this table. The files are static and do not change over time.\n  \"\"\"\n\n  use Ecto.Schema\n\n  schema \"files\" do\n    field :file_name, :string\n    field :file_uri, :string\n    field :file_checksum_hash, :string\n    field :id, Ecto.UUID, autogenerate: true, primary_key: true\n\n    belongs_to :version, VSekaiNebula.Version\n  end\n\n  # TODO changeset/2\nend\n\n\n\n\ndefmodule VSekaiNebula.CDN do\n  @moduledoc \"\"\"\n  This module represents the `cdn` table in the application's database.\n\n  ## Fields\n\n  - `:uid`: The unique identifier of the CDN.\n  - `:name`: The name of the CDN.\n  - `:uri`: The URI of the CDN.\n  - `:last_checked_on`: The date and time when the CDN was last checked. This field is necessary as the CDN details are checked regularly and we need to keep track of when they were last checked.\n  - `:region`: The region where the CDN is located.\n  - `:id`: A unique identifier for each CDN. It is autogenerated and serves as the primary key.\n\n  ## Reasoning\n\n  - Traditional timestamps (created_at, updated_at) are removed as they are not necessary for this table. The CDN details are static and do not change over time, except for the `:last_checked_on` field which is updated regularly.\n  \"\"\"\n\n  use Ecto.Schema\n\n  import Ecto.Changeset\n\n  schema \"cdn\" do\n    field :uid, :string\n    field :name, :string\n    field :uri, :string\n    field :last_checked_on, :utc_datetime\n    field :region, :string\n    field :id, Ecto.UUID, autogenerate: true, primary_key: true\n  end\n\n  # TODO changeset/2\nend"
   },
   {
-    "objectID": "decisions/20230719-dual-databases-cockroachdb-khepri.html#metadata",
-    "href": "decisions/20230719-dual-databases-cockroachdb-khepri.html#metadata",
-    "title": "Proposed: Game simulation server sidekick process",
+    "objectID": "decisions/20231201-headless-launcher-backend.html#metadata",
+    "href": "decisions/20231201-headless-launcher-backend.html#metadata",
+    "title": "Proposed: Headless Launcher Backend with Elixir and Server-Side CockroachDB",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai, Godot Engine, khepri, elixir"
+    "text": "Status: Proposed\nDeciders: V-Sekai Team\nTags: headless, backend, launcher, updater"
   },
   {
-    "objectID": "decisions/20230719-dual-databases-cockroachdb-khepri.html#context-and-problem-statement",
-    "href": "decisions/20230719-dual-databases-cockroachdb-khepri.html#context-and-problem-statement",
-    "title": "Proposed: Game simulation server sidekick process",
+    "objectID": "decisions/20231201-headless-launcher-backend.html#backdrop",
+    "href": "decisions/20231201-headless-launcher-backend.html#backdrop",
+    "title": "Proposed: Headless Launcher Backend with Elixir and Server-Side CockroachDB",
     "section": "",
-    "text": "We want to provide each game server a sidekick process that restarts Godot Engine on crash and acts as a local processor before upload to the source of truth backend database. This will ensure continuous gameplay and data integrity."
+    "text": "Introduce a headless backend launcher to automate game updates for enhanced gaming experience."
   },
   {
-    "objectID": "decisions/20230719-dual-databases-cockroachdb-khepri.html#proposed-solution",
-    "href": "decisions/20230719-dual-databases-cockroachdb-khepri.html#proposed-solution",
-    "title": "Proposed: Game simulation server sidekick process",
+    "objectID": "decisions/20231201-headless-launcher-backend.html#challenge",
+    "href": "decisions/20231201-headless-launcher-backend.html#challenge",
+    "title": "Proposed: Headless Launcher Backend with Elixir and Server-Side CockroachDB",
     "section": "",
-    "text": "We propose to use khepri for sidekick server data with an elixir frontend.\nKhepri provides robustness and reliability while Elixir offers scalability and fault-tolerance."
+    "text": "Build an updater that is simple yet robust, handling automated game updates in the background."
   },
   {
-    "objectID": "decisions/20230719-dual-databases-cockroachdb-khepri.html#implementation",
-    "href": "decisions/20230719-dual-databases-cockroachdb-khepri.html#implementation",
-    "title": "Proposed: Game simulation server sidekick process",
+    "objectID": "decisions/20231201-headless-launcher-backend.html#strategy",
+    "href": "decisions/20231201-headless-launcher-backend.html#strategy",
+    "title": "Proposed: Headless Launcher Backend with Elixir and Server-Side CockroachDB",
     "section": "",
-    "text": "Develop a sidekick process using khepri that monitors the Godot Engine.\nIn case of a crash, the sidekick process should be able to restart the Godot Engine.\nThe sidekick process should also act as a local processor for game data before it’s uploaded to the backend database.\nImplement an Elixir frontend to interact with the sidekick process."
+    "text": "The strategy for this proposal is to develop a headless backend launcher using Elixir and CockroachDB. The main components of the system will be:\nThe Headless CLI will implement desync for data synchronization and provide commands for displaying help information, version information, switching modes, checking current mode, listing all available modes, and updating according to semantic versioning.\nThe Updater Online Service will be a lightweight service that uses Elixir for handling web requests and CockroachDB for persistence. It will integrate the desync protocol and include error handling strategies for failed updates or data synchronization issues.\nThe GUI Launcher will be designed using the Godot Engine and will also integrate the desync protocol. It will feature a basic visual setup with V-Sekai branding.\nThe Game Sample will involve developing a basic visual sample with V-Sekai branding, planning for testing each component to ensure functionality, addressing security concerns including user data protection and secure updates, and discussing scalability potential with increasing users or larger game updates.\nEach table will have its own schema module representing different aspects of the application such as modes, versions, and update processes."
   },
   {
-    "objectID": "decisions/20230719-dual-databases-cockroachdb-khepri.html#positive-consequences",
-    "href": "decisions/20230719-dual-databases-cockroachdb-khepri.html#positive-consequences",
-    "title": "Proposed: Game simulation server sidekick process",
+    "objectID": "decisions/20231201-headless-launcher-backend.html#upside",
+    "href": "decisions/20231201-headless-launcher-backend.html#upside",
+    "title": "Proposed: Headless Launcher Backend with Elixir and Server-Side CockroachDB",
     "section": "",
-    "text": "Improved game server stability.\nContinuous gameplay even in the event of a crash.\nEnsured data integrity before upload to the backend database."
+    "text": "This system promotes seamless gaming with high performance and reliability from Elixir and CockroachDB."
   },
   {
-    "objectID": "decisions/20230719-dual-databases-cockroachdb-khepri.html#negative-consequences",
-    "href": "decisions/20230719-dual-databases-cockroachdb-khepri.html#negative-consequences",
-    "title": "Proposed: Game simulation server sidekick process",
+    "objectID": "decisions/20231201-headless-launcher-backend.html#downside",
+    "href": "decisions/20231201-headless-launcher-backend.html#downside",
+    "title": "Proposed: Headless Launcher Backend with Elixir and Server-Side CockroachDB",
     "section": "",
-    "text": "Additional development time and resources required.\nPotential complexity in managing the sidekick process."
+    "text": "Technology integration may lead to complex issues and compatibility challenges."
   },
   {
-    "objectID": "decisions/20230719-dual-databases-cockroachdb-khepri.html#option-graveyard",
-    "href": "decisions/20230719-dual-databases-cockroachdb-khepri.html#option-graveyard",
-    "title": "Proposed: Game simulation server sidekick process",
+    "objectID": "decisions/20231201-headless-launcher-backend.html#road-not-taken",
+    "href": "decisions/20231201-headless-launcher-backend.html#road-not-taken",
+    "title": "Proposed: Headless Launcher Backend with Elixir and Server-Side CockroachDB",
     "section": "",
-    "text": "Using a simple watchdog script: A simple script that monitors the Godot Engine and restarts it in case of a crash. This was rejected due to its inability to act as a local processor for game data before upload.\nRelying on third-party services: There are several third-party services that offer process monitoring and automatic restarts. However, these were rejected due to potential issues with customization, cost, and data privacy.\nBuilding a custom solution from scratch: While this would give us the most control, it was deemed too resource-intensive and unnecessary given the existence of suitable tools like khepri and Elixir.\nDo nothing: The option to maintain the status quo was considered but ultimately rejected due to the negative impact on user experience and data integrity."
+    "text": "External updaters and manual patches were dismissed for their demanding nature."
   },
   {
-    "objectID": "decisions/20230719-dual-databases-cockroachdb-khepri.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230719-dual-databases-cockroachdb-khepri.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Game simulation server sidekick process",
+    "objectID": "decisions/20231201-headless-launcher-backend.html#infrequent-use-case",
+    "href": "decisions/20231201-headless-launcher-backend.html#infrequent-use-case",
+    "title": "Proposed: Headless Launcher Backend with Elixir and Server-Side CockroachDB",
     "section": "",
-    "text": "No, this enhancement is fundamental to the stability of the game servers and cannot be achieved with a simple script workaround."
+    "text": "Design will allow manual update initiation for situations like limited bandwidth."
   },
   {
-    "objectID": "decisions/20230719-dual-databases-cockroachdb-khepri.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230719-dual-databases-cockroachdb-khepri.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Game simulation server sidekick process",
+    "objectID": "decisions/20231201-headless-launcher-backend.html#core-and-done-by-us",
+    "href": "decisions/20231201-headless-launcher-backend.html#core-and-done-by-us",
+    "title": "Proposed: Headless Launcher Backend with Elixir and Server-Side CockroachDB",
     "section": "",
-    "text": "Yes, as this directly impacts the user experience and the integrity of our game data, it is crucial that we have full control over its implementation and maintenance."
+    "text": "The V-Sekai team will develop and maintain this launcher backend. A detailed maintenance plan will be provided."
   },
   {
-    "objectID": "decisions/20230719-dual-databases-cockroachdb-khepri.html#references",
-    "href": "decisions/20230719-dual-databases-cockroachdb-khepri.html#references",
-    "title": "Proposed: Game simulation server sidekick process",
+    "objectID": "decisions/20231201-headless-launcher-backend.html#documentation",
+    "href": "decisions/20231201-headless-launcher-backend.html#documentation",
+    "title": "Proposed: Headless Launcher Backend with Elixir and Server-Side CockroachDB",
     "section": "",
-    "text": "V-Sekai"
+    "text": "A comprehensive documentation will be created for understanding the system and onboarding new team members."
   },
   {
-    "objectID": "decisions/20231108-neon-vercel-functions-toy-problem.html",
-    "href": "decisions/20231108-neon-vercel-functions-toy-problem.html",
-    "title": "Proposed: Development of a Community Polling Discord Bot Using Vercel and Neon PostgreSQL",
+    "objectID": "decisions/20231201-headless-launcher-backend.html#further-reading",
+    "href": "decisions/20231201-headless-launcher-backend.html#further-reading",
+    "title": "Proposed: Headless Launcher Backend with Elixir and Server-Side CockroachDB",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai Technical Team\nTags: Discord, Polling, Vercel, Serverless, PostgreSQL, Neon, Reactions, Community Engagement\n\n\n\n\nV-Sekai is aiming to boost community engagement by implementing interactive polling through Discord. The objective is to create a polling system where users can vote via reactions, and the results are managed in real-time.\n\n\n\nHow can V-Sekai develop a Discord bot that facilitates community polls using message reactions and records the results in a Neon-managed PostgreSQL database in a serverless environment?\n\n\n\n\nConstruct a Discord bot deployed on Vercel that can post poll messages with emoji reactions for voting.\nMonitor reaction additions and removals on these messages to count votes.\nIntegrate with Neon’s PostgreSQL database to store and update poll data, ensuring one vote per user.\nProvide real-time feedback and results tallying through the Discord bot.\n\n\n\n\n\nEngages the community in decision-making processes with interactive polls.\nGathers real-time data on community preferences and opinions.\nDemonstrates the real-time data handling capabilities of serverless functions and PostgreSQL databases.\n\n\n\n\n\nAdditional complexity in reaction event handling and vote deduplication.\nEnsuring database performance under high concurrency during active polls.\n\n\n\n\n\nUsing traditional polling methods without leveraging Discord’s interactive capabilities.\nReliance on external polling services that may not integrate seamlessly with Discord or offer real-time updates.\n\n\n\n\n\nDetailed analysis of voting patterns over time, which may require complex database queries.\n\n\n\n\n\nYes, the implementation of the Community Polling Discord bot using Neon’s PostgreSQL service will be developed and maintained internally as part of V-Sekai’s commitment to interactive community engagement.\n\n\n\n\n\nDiscord Bots: An Introduction\nVercel Serverless Functions\nNeon’s PostgreSQL Edge Capabilities\n\nThis strategy was formulated with AI assistance."
+    "text": "V-Sekai GitHub - Our efforts in VR using Godot Engine.\nV-Sekai Game Repo - Our open-source VR and social experiences project.\nDesync - Alternative casync implementation."
   },
   {
-    "objectID": "decisions/20231108-neon-vercel-functions-toy-problem.html#metadata",
-    "href": "decisions/20231108-neon-vercel-functions-toy-problem.html#metadata",
-    "title": "Proposed: Development of a Community Polling Discord Bot Using Vercel and Neon PostgreSQL",
+    "objectID": "decisions/20231201-headless-launcher-backend.html#code-snippets",
+    "href": "decisions/20231201-headless-launcher-backend.html#code-snippets",
+    "title": "Proposed: Headless Launcher Backend with Elixir and Server-Side CockroachDB",
     "section": "",
-    "text": "Status: Proposed\nDeciders: V-Sekai Technical Team\nTags: Discord, Polling, Vercel, Serverless, PostgreSQL, Neon, Reactions, Community Engagement"
+    "text": "stateDiagram-v2\n    [*] --&gt; Idle\n    Idle --&gt; CheckForUpdates : Update Triggered\n    CheckForUpdates --&gt; Updating\n    Updating --&gt; Idle : Update Successful\n\n    state CheckForUpdates {\n        [*] --&gt; Checking\n        Checking --&gt; NoUpdateFound\n        NoUpdateFound --&gt; [*]\n\n        Checking --&gt; UpdateAvailable\n        UpdateAvailable --&gt; PreparingUpdate\n        PreparingUpdate --&gt; DownloadingUpdate\n        DownloadingUpdate --&gt; ApplyingUpdate\n        ApplyingUpdate --&gt; FinalizingUpdate\n        FinalizingUpdate --&gt; UpdateSuccessful\n        UpdateSuccessful --&gt; [*]\n    }\n\n    Updating: Update in progress\n    Idle: Waiting for update trigger\nUse Elixir for concurrent services and CockroachDB on the server for data management:\n\nHeadless CLI\n\nImplement desync for data synchronization.\nDetail how desync will be integrated into the service and GUI.\n\n\n# Display help information\nvsekai --help\n\n# Display version information\nvsekai --version\n\n# Switch to a different mode. Modes allow different operations for the software.\nvsekai mode switch --mode_name stable\n\n# Check the current mode.\nvsekai mode current\n\n# List all available modes.\nvsekai mode list\n\n# Always updates according to semantic versioning to the mode.\n./headless-vsekai-v0.1.0.exe --update C:/v-sekai/launcher\n./headless-vsekai-v0.1.1.exe --update C:/v-sekai/launcher\n./headless-vsekai-v0.2.0.exe --update C:/v-sekai/launcher\n\n# Pseudo code for update process\ncheck_launcher_folder()\nvalidate_manifest_file_and_version()\nensure_correct_files_for_update()\ndownload_to_temp()\ndelete_old_and_move_over()\nsetup_registry_values()\n\nUpdater Online Service:\n\nCreate a lightweight updater service.\nUse Elixir for web requests handling.\nUtilize server-side CockroachDB for persistence.\nIntegrate desync protocol in the Service.\nInclude error handling strategy for failed updates or data synchronization issues.\n\nGUI Launcher Creation:\n\nDesign an intuitive Godot Engine GUI launcher.\nIntegrate desync protocol in the GUI.\nDetail the basic visual setup with V-Sekai branding.\n\nGame Setup Efforts:\n\nDevelop a basic visual setup with V-Sekai branding.\nInclude a plan for testing each component to ensure functionality.\nAddress security concerns, including user data protection and secure updates.\nDiscuss scalability potential with increasing users or larger game updates.\n\n\n\n\n\n\ndefmodule VSekaiNebula.Mode do\n  @moduledoc \"\"\"\n  This module represents the `modes` table in the application's database.\n\n  ## Fields\n\n  - `:name`: The name of the mode.\n  - `:is_active`: A boolean indicating whether the mode is active or not.\n  - `:update_to`: Updates to a different mode.\n  - `:id`: A unique identifier for each mode. It is autogenerated and serves as the primary key.\n  \"\"\"\n\n  use Ecto.Schema\n\n  schema \"modes\" do\n    field :name, :string\n    field :is_active, :bool\n    field :update_to, Ecto.UUID\n    field :id, Ecto.UUID, autogenerate: true, primary_key: true\n\n    timestamps()\n  end\n\n  # TODO changeset/2\nend\n\n\n\ndefmodule VSekaiNebula.Version do\n  @moduledoc \"\"\"\n  This module represents the `versions` table in the application's database.\n\n  ## Fields\n\n  - `:version`: The version number.\n  - `:skip_update`: A boolean indicating whether to skip the update or not.\n  - `:manifest_file_uri`: The URI of the manifest file. This is generated server-side to ensure integrity,\n    especially during CI/CD processes. It helps prevent issues such as network errors, mid-process failures,\n    or programming errors causing incorrect checksums or file locations.\n  - `:id`: A unique identifier for each version. It is autogenerated and serves as the primary key.\n\n  ## Associations\n\n  - belongs_to :mode, VSekaiNebula.Mode: Each version is associated with a mode.\n  \"\"\"\n\n  use Ecto.Schema\n\n  schema \"versions\" do\n    field :version, :string\n    field :skip_update, :bool\n    field :manifest_file_uri, :string\n    field :id, Ecto.UUID, autogenerate: true, primary_key: true\n\n    belongs_to :mode, VSekaiNebula.Mode\n\n    timestamps()\n  end\n\n  # TODO changeset/2\nend\n\n\n\ndefmodule VSekaiNebula.Files do\n  @moduledoc \"\"\"\n  This module represents the `files` table in the application's database.\n\n  ## Fields\n\n  - `:file_name`: The name of the file.\n  - `:file_uri`: The URI of the file.\n  - `:file_checksum_hash`: The checksum hash of the file.\n  - `:id`: A unique identifier for each file. It is autogenerated and serves as the primary key.\n\n  ## Associations\n\n  - belongs_to :version, VSekaiNebula.Version: Each file is associated with a version.\n\n  ## Reasoning\n\n  - Timestamps are removed as they are not necessary for this table. The files are static and do not change over time.\n  \"\"\"\n\n  use Ecto.Schema\n\n  schema \"files\" do\n    field :file_name, :string\n    field :file_uri, :string\n    field :file_checksum_hash, :string\n    field :id, Ecto.UUID, autogenerate: true, primary_key: true\n\n    belongs_to :version, VSekaiNebula.Version\n  end\n\n  # TODO changeset/2\nend\n\n\n\n\ndefmodule VSekaiNebula.CDN do\n  @moduledoc \"\"\"\n  This module represents the `cdn` table in the application's database.\n\n  ## Fields\n\n  - `:uid`: The unique identifier of the CDN.\n  - `:name`: The name of the CDN.\n  - `:uri`: The URI of the CDN.\n  - `:last_checked_on`: The date and time when the CDN was last checked. This field is necessary as the CDN details are checked regularly and we need to keep track of when they were last checked.\n  - `:region`: The region where the CDN is located.\n  - `:id`: A unique identifier for each CDN. It is autogenerated and serves as the primary key.\n\n  ## Reasoning\n\n  - Traditional timestamps (created_at, updated_at) are removed as they are not necessary for this table. The CDN details are static and do not change over time, except for the `:last_checked_on` field which is updated regularly.\n  \"\"\"\n\n  use Ecto.Schema\n\n  import Ecto.Changeset\n\n  schema \"cdn\" do\n    field :uid, :string\n    field :name, :string\n    field :uri, :string\n    field :last_checked_on, :utc_datetime\n    field :region, :string\n    field :id, Ecto.UUID, autogenerate: true, primary_key: true\n  end\n\n  # TODO changeset/2\nend"
   },
   {
-    "objectID": "decisions/20231108-neon-vercel-functions-toy-problem.html#the-backdrop",
-    "href": "decisions/20231108-neon-vercel-functions-toy-problem.html#the-backdrop",
-    "title": "Proposed: Development of a Community Polling Discord Bot Using Vercel and Neon PostgreSQL",
+    "objectID": "decisions/20211031-meeting-area.html",
+    "href": "decisions/20211031-meeting-area.html",
+    "title": "Proposed: Meeting area",
     "section": "",
-    "text": "V-Sekai is aiming to boost community engagement by implementing interactive polling through Discord. The objective is to create a polling system where users can vote via reactions, and the results are managed in real-time."
+    "text": "Proposed: Meeting area\n\nContext and Problem Statement\nNeed a virtual world to meet.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nNeed to be in VR more.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nHub world with a glass whiteboard to do meetings with some private alcoves.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nCore\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nI know how this worlds\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20231108-neon-vercel-functions-toy-problem.html#the-challenge",
-    "href": "decisions/20231108-neon-vercel-functions-toy-problem.html#the-challenge",
-    "title": "Proposed: Development of a Community Polling Discord Bot Using Vercel and Neon PostgreSQL",
+    "objectID": "decisions/20240708-vsekai-my-life-as-a-queen.html",
+    "href": "decisions/20240708-vsekai-my-life-as-a-queen.html",
+    "title": "Proposed: V-Sekai: My Life as a Princess",
     "section": "",
-    "text": "How can V-Sekai develop a Discord bot that facilitates community polls using message reactions and records the results in a Neon-managed PostgreSQL database in a serverless environment?"
+    "text": "The second Godot XR Game Jam is organized by the Godot XR Community and is occurring on July 8th, 2024. The jam theme is: Relaxation!\n\n\n\nCreate an Android XR game using the theme of “Relaxation” and utilizing Godot Engine 4.3 with our module for goal hierarchical task network planner and our portable avatar import format (VRM).\n\n\n\nIn “V-Sekai: My Life as a Princess,” players assume the role of a princess tasked with rebuilding and managing a kingdom. The game focuses on relaxation through planning, resource management, VR interactions, and adventurer tasking.\n\n\n\nLateral Thinking with Weathered Technology\nDesigned so both planning and people can do the same things\n\n\n\n\nvar memories: Dictionary = {\n    \"is_at\": {\"player\": \"cabin\"},\n    \"is_outside_of\": {\"cave entrance\": \"cabin\"},\n    \"contains\": {\"first_room\": \"treasure\"}\n}\n\nvar todo_list: Array = [\n    \"Explore the cabin\",\n    \"Find the cave entrance\",\n    \"Enter the cave\",\n    \"Reach the treasure room\"\n]\nYou start in a little cabin in the woods. You have a cave you can venture into, and at the end is treasure. This initial prototype serves as a simple introduction to the game’s mechanics and environment.\n\n\n\nvar princess_strategic_memories: Dictionary = {\n    \"is_at\": {\"princess\": \"royal cabin\"},\n    \"has_goal\": {\"princess\": \"retrieve treasure from the cave\"},\n    \"preparation_status\": {\"princess\": \"not_started\"}\n}\n\nvar princess_strategic_plan: Array = [\n    \"Set goal to retrieve treasure from the cave\",\n    \"Prepare for the journey\"\n]\n\nvar princess_tactical_memories: Dictionary = {\n    \"is_at\": {\"princess\": \"royal cabin\"},\n    \"knows_location\": {\"princess\": [\"royal cabin\", \"cave entrance\"]},\n    \"route_planned\": {\"princess\": false}\n}\n\nvar princess_tactical_plan: Array = [\n    \"Move to the royal cabin\",\n    \"Locate the cave entrance\",\n    \"Plan route through the cave to the treasure room\"\n]\n\nvar princess_operational_memories: Dictionary = {\n    \"is_at\": {\"princess\": \"royal cabin\"},\n    \"visited\": {\"princess\": []},\n    \"contains\": {\"first_room\": \"treasure\"}\n}\n\nvar princess_operational_plan: Array = [\n    \"Gather supplies for the journey\",\n    \"Travel to the cave entrance\",\n    \"Wait for the adventurer\",\n    \"Provide support from outside the cave\",\n    \"Receive the treasure from the adventurer\"\n]\n\nvar adventurer_tactical_memories: Dictionary = {\n    \"is_at\": {\"adventurer\": \"adventurer's cabin\"},\n    \"knows_location\": {\"adventurer\": [\"adventurer's cabin\", \"cave entrance\"]},\n    \"route_planned\": {\"adventurer\": false}\n}\n\nvar adventurer_tactical_plan: Array = [\n    \"Move to the adventurer's cabin\",\n    \"Locate the cave entrance\",\n    \"Plan route through the cave to the treasure room\"\n]\n\nvar adventurer_operational_memories: Dictionary = {\n    \"is_at\": {\"adventurer\": \"adventurer's cabin\"},\n    \"visited\": {\"adventurer\": []},\n    \"contains\": {\"first_room\": \"treasure\"}\n}\n\nvar adventurer_operational_plan: Array = [\n    \"Walk to the adventurer's cabin\",\n    \"Search for the cave entrance\",\n    \"Enter the cave\",\n    \"Navigate to the first room\",\n    \"Collect the treasure\",\n    \"Return to the cave entrance and hand over the treasure to the princess\"\n]\nIn the initial prototype, you explore the cave yourself. In “V-Sekai: My Life as a Princess,” you will reverse this concept by taking on the role of the princess who supplies adventurers with instructions to explore the cave and retrieve treasures. This shift from direct exploration to strategic management aligns with the relaxation theme.\n\n\n\n\n\nRelaxing Gameplay: Focuses on non-combat activities like building, gardening, organizing events, and sending adventurers on quests.\nImmersive Experience: Utilizes VRM technology for customizable avatars and Godot’s XR capabilities for an engaging experience.\nDynamic Task Management: The HTN planner ensures that tasks are generated based on player actions, providing a unique experience each time.\n\n\n\n\n\nLearning Curve: Players unfamiliar with resource management games may find it challenging initially.\nHardware Requirements: Requires a VR-capable device, which may limit accessibility.\n\n\n\n\n\nCombat Mechanics: Instead of focusing on relaxation, we could have included combat elements, but this would detract from the theme of relaxation.\nLinear Storyline: A fixed storyline could have been implemented, but dynamic task generation offers more replayability.\n\n\n\n\n\nSeasonal Events: While the game includes various activities, seasonal events such as festivals or special quests tied to real-world holidays are not included. These could add variety but would require additional development time and resources.\n\n\n\n\n\nCore Development: The V-Sekai development team will handle all core aspects of the game, including coding, art, and design.\nCommunity Contributions: Open to contributions from the Godot XR community for additional content and features.\n\n\n\n\nStatus: Proposed\n\n\n\n\nV-Sekai development team\niFire\nBrune\n\n\n\n\n\nV-Sekai\nGodot XR\nRelaxation\nVRM\nHTN Planner\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nFinal Fantasy Crystal Chronicles: My Life as a King - A Lost WiiWare Classic [REFFOID]\nGodot XR Game Jam July 2024\nGridmap usage in Cassette Beasts\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20231108-neon-vercel-functions-toy-problem.html#the-strategy",
-    "href": "decisions/20231108-neon-vercel-functions-toy-problem.html#the-strategy",
-    "title": "Proposed: Development of a Community Polling Discord Bot Using Vercel and Neon PostgreSQL",
+    "objectID": "decisions/20240708-vsekai-my-life-as-a-queen.html#the-context",
+    "href": "decisions/20240708-vsekai-my-life-as-a-queen.html#the-context",
+    "title": "Proposed: V-Sekai: My Life as a Princess",
     "section": "",
-    "text": "Construct a Discord bot deployed on Vercel that can post poll messages with emoji reactions for voting.\nMonitor reaction additions and removals on these messages to count votes.\nIntegrate with Neon’s PostgreSQL database to store and update poll data, ensuring one vote per user.\nProvide real-time feedback and results tallying through the Discord bot."
+    "text": "The second Godot XR Game Jam is organized by the Godot XR Community and is occurring on July 8th, 2024. The jam theme is: Relaxation!"
   },
   {
-    "objectID": "decisions/20231108-neon-vercel-functions-toy-problem.html#the-upside",
-    "href": "decisions/20231108-neon-vercel-functions-toy-problem.html#the-upside",
-    "title": "Proposed: Development of a Community Polling Discord Bot Using Vercel and Neon PostgreSQL",
+    "objectID": "decisions/20240708-vsekai-my-life-as-a-queen.html#the-problem-statement",
+    "href": "decisions/20240708-vsekai-my-life-as-a-queen.html#the-problem-statement",
+    "title": "Proposed: V-Sekai: My Life as a Princess",
     "section": "",
-    "text": "Engages the community in decision-making processes with interactive polls.\nGathers real-time data on community preferences and opinions.\nDemonstrates the real-time data handling capabilities of serverless functions and PostgreSQL databases."
+    "text": "Create an Android XR game using the theme of “Relaxation” and utilizing Godot Engine 4.3 with our module for goal hierarchical task network planner and our portable avatar import format (VRM)."
   },
   {
-    "objectID": "decisions/20231108-neon-vercel-functions-toy-problem.html#the-downside",
-    "href": "decisions/20231108-neon-vercel-functions-toy-problem.html#the-downside",
-    "title": "Proposed: Development of a Community Polling Discord Bot Using Vercel and Neon PostgreSQL",
+    "objectID": "decisions/20240708-vsekai-my-life-as-a-queen.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240708-vsekai-my-life-as-a-queen.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: V-Sekai: My Life as a Princess",
     "section": "",
-    "text": "Additional complexity in reaction event handling and vote deduplication.\nEnsuring database performance under high concurrency during active polls."
+    "text": "In “V-Sekai: My Life as a Princess,” players assume the role of a princess tasked with rebuilding and managing a kingdom. The game focuses on relaxation through planning, resource management, VR interactions, and adventurer tasking.\n\n\n\nLateral Thinking with Weathered Technology\nDesigned so both planning and people can do the same things\n\n\n\n\nvar memories: Dictionary = {\n    \"is_at\": {\"player\": \"cabin\"},\n    \"is_outside_of\": {\"cave entrance\": \"cabin\"},\n    \"contains\": {\"first_room\": \"treasure\"}\n}\n\nvar todo_list: Array = [\n    \"Explore the cabin\",\n    \"Find the cave entrance\",\n    \"Enter the cave\",\n    \"Reach the treasure room\"\n]\nYou start in a little cabin in the woods. You have a cave you can venture into, and at the end is treasure. This initial prototype serves as a simple introduction to the game’s mechanics and environment.\n\n\n\nvar princess_strategic_memories: Dictionary = {\n    \"is_at\": {\"princess\": \"royal cabin\"},\n    \"has_goal\": {\"princess\": \"retrieve treasure from the cave\"},\n    \"preparation_status\": {\"princess\": \"not_started\"}\n}\n\nvar princess_strategic_plan: Array = [\n    \"Set goal to retrieve treasure from the cave\",\n    \"Prepare for the journey\"\n]\n\nvar princess_tactical_memories: Dictionary = {\n    \"is_at\": {\"princess\": \"royal cabin\"},\n    \"knows_location\": {\"princess\": [\"royal cabin\", \"cave entrance\"]},\n    \"route_planned\": {\"princess\": false}\n}\n\nvar princess_tactical_plan: Array = [\n    \"Move to the royal cabin\",\n    \"Locate the cave entrance\",\n    \"Plan route through the cave to the treasure room\"\n]\n\nvar princess_operational_memories: Dictionary = {\n    \"is_at\": {\"princess\": \"royal cabin\"},\n    \"visited\": {\"princess\": []},\n    \"contains\": {\"first_room\": \"treasure\"}\n}\n\nvar princess_operational_plan: Array = [\n    \"Gather supplies for the journey\",\n    \"Travel to the cave entrance\",\n    \"Wait for the adventurer\",\n    \"Provide support from outside the cave\",\n    \"Receive the treasure from the adventurer\"\n]\n\nvar adventurer_tactical_memories: Dictionary = {\n    \"is_at\": {\"adventurer\": \"adventurer's cabin\"},\n    \"knows_location\": {\"adventurer\": [\"adventurer's cabin\", \"cave entrance\"]},\n    \"route_planned\": {\"adventurer\": false}\n}\n\nvar adventurer_tactical_plan: Array = [\n    \"Move to the adventurer's cabin\",\n    \"Locate the cave entrance\",\n    \"Plan route through the cave to the treasure room\"\n]\n\nvar adventurer_operational_memories: Dictionary = {\n    \"is_at\": {\"adventurer\": \"adventurer's cabin\"},\n    \"visited\": {\"adventurer\": []},\n    \"contains\": {\"first_room\": \"treasure\"}\n}\n\nvar adventurer_operational_plan: Array = [\n    \"Walk to the adventurer's cabin\",\n    \"Search for the cave entrance\",\n    \"Enter the cave\",\n    \"Navigate to the first room\",\n    \"Collect the treasure\",\n    \"Return to the cave entrance and hand over the treasure to the princess\"\n]\nIn the initial prototype, you explore the cave yourself. In “V-Sekai: My Life as a Princess,” you will reverse this concept by taking on the role of the princess who supplies adventurers with instructions to explore the cave and retrieve treasures. This shift from direct exploration to strategic management aligns with the relaxation theme."
   },
   {
-    "objectID": "decisions/20231108-neon-vercel-functions-toy-problem.html#the-road-not-taken",
-    "href": "decisions/20231108-neon-vercel-functions-toy-problem.html#the-road-not-taken",
-    "title": "Proposed: Development of a Community Polling Discord Bot Using Vercel and Neon PostgreSQL",
+    "objectID": "decisions/20240708-vsekai-my-life-as-a-queen.html#the-benefits",
+    "href": "decisions/20240708-vsekai-my-life-as-a-queen.html#the-benefits",
+    "title": "Proposed: V-Sekai: My Life as a Princess",
     "section": "",
-    "text": "Using traditional polling methods without leveraging Discord’s interactive capabilities.\nReliance on external polling services that may not integrate seamlessly with Discord or offer real-time updates."
+    "text": "Relaxing Gameplay: Focuses on non-combat activities like building, gardening, organizing events, and sending adventurers on quests.\nImmersive Experience: Utilizes VRM technology for customizable avatars and Godot’s XR capabilities for an engaging experience.\nDynamic Task Management: The HTN planner ensures that tasks are generated based on player actions, providing a unique experience each time."
   },
   {
-    "objectID": "decisions/20231108-neon-vercel-functions-toy-problem.html#the-infrequent-use-case",
-    "href": "decisions/20231108-neon-vercel-functions-toy-problem.html#the-infrequent-use-case",
-    "title": "Proposed: Development of a Community Polling Discord Bot Using Vercel and Neon PostgreSQL",
+    "objectID": "decisions/20240708-vsekai-my-life-as-a-queen.html#the-downsides",
+    "href": "decisions/20240708-vsekai-my-life-as-a-queen.html#the-downsides",
+    "title": "Proposed: V-Sekai: My Life as a Princess",
     "section": "",
-    "text": "Detailed analysis of voting patterns over time, which may require complex database queries."
+    "text": "Learning Curve: Players unfamiliar with resource management games may find it challenging initially.\nHardware Requirements: Requires a VR-capable device, which may limit accessibility."
   },
   {
-    "objectID": "decisions/20231108-neon-vercel-functions-toy-problem.html#in-core-and-done-by-us",
-    "href": "decisions/20231108-neon-vercel-functions-toy-problem.html#in-core-and-done-by-us",
-    "title": "Proposed: Development of a Community Polling Discord Bot Using Vercel and Neon PostgreSQL",
+    "objectID": "decisions/20240708-vsekai-my-life-as-a-queen.html#the-road-not-taken",
+    "href": "decisions/20240708-vsekai-my-life-as-a-queen.html#the-road-not-taken",
+    "title": "Proposed: V-Sekai: My Life as a Princess",
     "section": "",
-    "text": "Yes, the implementation of the Community Polling Discord bot using Neon’s PostgreSQL service will be developed and maintained internally as part of V-Sekai’s commitment to interactive community engagement."
+    "text": "Combat Mechanics: Instead of focusing on relaxation, we could have included combat elements, but this would detract from the theme of relaxation.\nLinear Storyline: A fixed storyline could have been implemented, but dynamic task generation offers more replayability."
   },
   {
-    "objectID": "decisions/20231108-neon-vercel-functions-toy-problem.html#further-reading",
-    "href": "decisions/20231108-neon-vercel-functions-toy-problem.html#further-reading",
-    "title": "Proposed: Development of a Community Polling Discord Bot Using Vercel and Neon PostgreSQL",
+    "objectID": "decisions/20240708-vsekai-my-life-as-a-queen.html#the-infrequent-use-case",
+    "href": "decisions/20240708-vsekai-my-life-as-a-queen.html#the-infrequent-use-case",
+    "title": "Proposed: V-Sekai: My Life as a Princess",
     "section": "",
-    "text": "Discord Bots: An Introduction\nVercel Serverless Functions\nNeon’s PostgreSQL Edge Capabilities\n\nThis strategy was formulated with AI assistance."
+    "text": "Seasonal Events: While the game includes various activities, seasonal events such as festivals or special quests tied to real-world holidays are not included. These could add variety but would require additional development time and resources."
   },
   {
-    "objectID": "decisions/20230716-enhancing-avatar-creation-process-01-regular.html",
-    "href": "decisions/20230716-enhancing-avatar-creation-process-01-regular.html",
-    "title": "Proposed: Enhancing Avatar Creation Process in V-Sekai Regular",
+    "objectID": "decisions/20240708-vsekai-my-life-as-a-queen.html#in-core-and-done-by-us",
+    "href": "decisions/20240708-vsekai-my-life-as-a-queen.html#in-core-and-done-by-us",
+    "title": "Proposed: V-Sekai: My Life as a Princess",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nV-Sekai currently has limitations when it comes to creating avatars with specific features and customizations. This can be a hindrance for users who want to have more control over the appearance of their avatars. To address this, we propose an enhancement that introduces various tools and techniques to overcome these limitations and provide a more comprehensive avatar creation process.\n\n\n\nHere is a list of raw processes to be broken down.\n\n\nTo implement the requested changes, here are the modified instructions:\n\nCreating the avatar face: Utilizes digital drawing techniques to design and create the facial features of the avatar.\n\nInput mime type: None\nOutput mime type: Digital drawing/image file (e.g., PNG, SVG)\n\nChanging colors: Utilizes a digital paintbrush tool like Penpot to modify and customize the colors of the avatar.\n\nInput mime type: Digital drawing/image file (e.g., PNG, SVG)\nOutput mime type: Digital drawing/image file (e.g., PNG, SVG)\n\nSelecting the best-looking avatars: Evaluates and chooses the most visually appealing avatars from a pool of options.\n\nInput mime type: Digital drawing/image file (e.g., PNG, SVG)\nOutput mime type: Digital drawing/image file (e.g., PNG, SVG)\n\nRemoving the background image: Removes the background image to make rework easier. May provide worse results with edge details.\n\nInput mime type: Digital drawing/image file (e.g., PNG, SVG)\nOutput mime type: Digital drawing/image file (e.g., PNG, SVG)\n\nAdding a body: Incorporates a body to the avatar using Blender’s CC0 base mesh or a similar tool.\n\nInput mime type: Digital drawing/image file (e.g., PNG, SVG)\nOutput mime type: Digital drawing/image file (e.g., PNG, SVG)\n\nCreating a 3D model of the back of the avatar: If feasible, attempts to create a 3D model of the back of the avatar for a more comprehensive representation.\n\nInput mime type: Digital drawing/image file (e.g., PNG, SVG)\nOutput mime type: Digital drawing/image file (e.g., PNG, SVG)\n\nSimplifying images: Uses a tool to simplify and refine the entire avatar image as a whole, removing any unnecessary image details or complexities.\n\nInput mime type: Digital drawing/image file (e.g., PNG, SVG)\nOutput mime type: Digital drawing/image file (e.g., PNG, SVG)\n\nAdding clothing and accessories: Enhances the avatar by adding clothing and accessories using tools like Vroid Hub.\n\nInput mime type: Digital drawing/image file (e.g., PNG, SVG)\nOutput mime type: Digital drawing/image file (e.g., PNG, SVG)\n\nPlacing the 2D image as a reference: Positions the 2D reference image in front of the 3D model to serve as a visual guide during customization.\n\nInput mime type: Digital drawing/image file (e.g., PNG, SVG), 3D model file (e.g., GLTF)\nOutput mime type: 3D model file (e.g., GLTF), Digital image file (e.g., PNG, SVG)\n\nCapturing and enhancing images: Captures images from various angles using a camera and enhances them to improve the overall quality.\n\n\nInput mime type: Digital drawing/image file (e.g., PNG, SVG)\nOutput mime type: Digital image file (e.g., PNG, SVG)\n\n\nGenerating text captions: Creates descriptive text captions for the captured images to provide additional context or information.\n\n\nInput mime type: Digital image file (e.g., PNG, SVG)\nOutput mime type: Text file (e.g., TXT)\n\n\nUsing a 2D reference image in Blender: Uses a 2D reference image within Blender to guide the customization process.\n\n\nInput mime type: Digital drawing/image file (e.g., PNG, SVG)\nOutput mime type: 3D model file (e.g., GLTF), Digital image file (e.g., PNG, SVG)\n\n\n\n\n\n\nUsers will be able to create highly customizable avatars with specific features.\nThe avatar creation process will be enhanced with a variety of tools and techniques.\nDetailed customization of colors, clothing, accessories, and facial expressions will be possible.\nMotion capture capabilities can be integrated for more realistic animations.\n\n\n\n\n\nThe implementation process is complex and may require advanced technical skills from users.\nSome steps, like creating a 3D model of the back of the avatar, may not always be successful.\nPainting errors and other imperfections may remain in the final avatar.\n\n\n\n\n\nExcessive complexity or technical requirements: We want the avatar creation process to be user-friendly and accessible to a wide range of users, so any options that require advanced technical skills or have excessively complex customization controls will not be included.\n\n\n\n\nNo, the proposed enhancement involves a multi-step process that cannot be easily replicated with just a few lines of script.\n\n\n\nThe proposed enhancement addresses the limitations in V-Sekai’s avatar creation process, providing users with a comprehensive solution for creating highly customizable avatars. By implementing these tools and techniques within the platform, V-Sekai can offer a more robust and user-friendly experience for its community.\n\n\n\n\nV-Sekai\nDetail Tweaker\nInstructBLIP: Towards General-purpose Vision-Language Models with Instruction Tuning\nPetals"
+    "text": "Core Development: The V-Sekai development team will handle all core aspects of the game, including coding, art, and design.\nCommunity Contributions: Open to contributions from the Godot XR community for additional content and features."
   },
   {
-    "objectID": "decisions/20230716-enhancing-avatar-creation-process-01-regular.html#metadata",
-    "href": "decisions/20230716-enhancing-avatar-creation-process-01-regular.html#metadata",
-    "title": "Proposed: Enhancing Avatar Creation Process in V-Sekai Regular",
+    "objectID": "decisions/20240708-vsekai-my-life-as-a-queen.html#status",
+    "href": "decisions/20240708-vsekai-my-life-as-a-queen.html#status",
+    "title": "Proposed: V-Sekai: My Life as a Princess",
     "section": "",
-    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai"
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20230716-enhancing-avatar-creation-process-01-regular.html#context-and-problem-statement",
-    "href": "decisions/20230716-enhancing-avatar-creation-process-01-regular.html#context-and-problem-statement",
-    "title": "Proposed: Enhancing Avatar Creation Process in V-Sekai Regular",
+    "objectID": "decisions/20240708-vsekai-my-life-as-a-queen.html#decision-makers",
+    "href": "decisions/20240708-vsekai-my-life-as-a-queen.html#decision-makers",
+    "title": "Proposed: V-Sekai: My Life as a Princess",
     "section": "",
-    "text": "V-Sekai currently has limitations when it comes to creating avatars with specific features and customizations. This can be a hindrance for users who want to have more control over the appearance of their avatars. To address this, we propose an enhancement that introduces various tools and techniques to overcome these limitations and provide a more comprehensive avatar creation process."
+    "text": "V-Sekai development team\niFire\nBrune"
   },
   {
-    "objectID": "decisions/20230716-enhancing-avatar-creation-process-01-regular.html#proposed-solution",
-    "href": "decisions/20230716-enhancing-avatar-creation-process-01-regular.html#proposed-solution",
-    "title": "Proposed: Enhancing Avatar Creation Process in V-Sekai Regular",
+    "objectID": "decisions/20240708-vsekai-my-life-as-a-queen.html#tags",
+    "href": "decisions/20240708-vsekai-my-life-as-a-queen.html#tags",
+    "title": "Proposed: V-Sekai: My Life as a Princess",
     "section": "",
-    "text": "Here is a list of raw processes to be broken down.\n\n\nTo implement the requested changes, here are the modified instructions:\n\nCreating the avatar face: Utilizes digital drawing techniques to design and create the facial features of the avatar.\n\nInput mime type: None\nOutput mime type: Digital drawing/image file (e.g., PNG, SVG)\n\nChanging colors: Utilizes a digital paintbrush tool like Penpot to modify and customize the colors of the avatar.\n\nInput mime type: Digital drawing/image file (e.g., PNG, SVG)\nOutput mime type: Digital drawing/image file (e.g., PNG, SVG)\n\nSelecting the best-looking avatars: Evaluates and chooses the most visually appealing avatars from a pool of options.\n\nInput mime type: Digital drawing/image file (e.g., PNG, SVG)\nOutput mime type: Digital drawing/image file (e.g., PNG, SVG)\n\nRemoving the background image: Removes the background image to make rework easier. May provide worse results with edge details.\n\nInput mime type: Digital drawing/image file (e.g., PNG, SVG)\nOutput mime type: Digital drawing/image file (e.g., PNG, SVG)\n\nAdding a body: Incorporates a body to the avatar using Blender’s CC0 base mesh or a similar tool.\n\nInput mime type: Digital drawing/image file (e.g., PNG, SVG)\nOutput mime type: Digital drawing/image file (e.g., PNG, SVG)\n\nCreating a 3D model of the back of the avatar: If feasible, attempts to create a 3D model of the back of the avatar for a more comprehensive representation.\n\nInput mime type: Digital drawing/image file (e.g., PNG, SVG)\nOutput mime type: Digital drawing/image file (e.g., PNG, SVG)\n\nSimplifying images: Uses a tool to simplify and refine the entire avatar image as a whole, removing any unnecessary image details or complexities.\n\nInput mime type: Digital drawing/image file (e.g., PNG, SVG)\nOutput mime type: Digital drawing/image file (e.g., PNG, SVG)\n\nAdding clothing and accessories: Enhances the avatar by adding clothing and accessories using tools like Vroid Hub.\n\nInput mime type: Digital drawing/image file (e.g., PNG, SVG)\nOutput mime type: Digital drawing/image file (e.g., PNG, SVG)\n\nPlacing the 2D image as a reference: Positions the 2D reference image in front of the 3D model to serve as a visual guide during customization.\n\nInput mime type: Digital drawing/image file (e.g., PNG, SVG), 3D model file (e.g., GLTF)\nOutput mime type: 3D model file (e.g., GLTF), Digital image file (e.g., PNG, SVG)\n\nCapturing and enhancing images: Captures images from various angles using a camera and enhances them to improve the overall quality.\n\n\nInput mime type: Digital drawing/image file (e.g., PNG, SVG)\nOutput mime type: Digital image file (e.g., PNG, SVG)\n\n\nGenerating text captions: Creates descriptive text captions for the captured images to provide additional context or information.\n\n\nInput mime type: Digital image file (e.g., PNG, SVG)\nOutput mime type: Text file (e.g., TXT)\n\n\nUsing a 2D reference image in Blender: Uses a 2D reference image within Blender to guide the customization process.\n\n\nInput mime type: Digital drawing/image file (e.g., PNG, SVG)\nOutput mime type: 3D model file (e.g., GLTF), Digital image file (e.g., PNG, SVG)"
+    "text": "V-Sekai\nGodot XR\nRelaxation\nVRM\nHTN Planner"
   },
   {
-    "objectID": "decisions/20230716-enhancing-avatar-creation-process-01-regular.html#positive-consequences",
-    "href": "decisions/20230716-enhancing-avatar-creation-process-01-regular.html#positive-consequences",
-    "title": "Proposed: Enhancing Avatar Creation Process in V-Sekai Regular",
+    "objectID": "decisions/20240708-vsekai-my-life-as-a-queen.html#further-reading",
+    "href": "decisions/20240708-vsekai-my-life-as-a-queen.html#further-reading",
+    "title": "Proposed: V-Sekai: My Life as a Princess",
     "section": "",
-    "text": "Users will be able to create highly customizable avatars with specific features.\nThe avatar creation process will be enhanced with a variety of tools and techniques.\nDetailed customization of colors, clothing, accessories, and facial expressions will be possible.\nMotion capture capabilities can be integrated for more realistic animations."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nFinal Fantasy Crystal Chronicles: My Life as a King - A Lost WiiWare Classic [REFFOID]\nGodot XR Game Jam July 2024\nGridmap usage in Cassette Beasts\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20230716-enhancing-avatar-creation-process-01-regular.html#negative-consequences",
-    "href": "decisions/20230716-enhancing-avatar-creation-process-01-regular.html#negative-consequences",
-    "title": "Proposed: Enhancing Avatar Creation Process in V-Sekai Regular",
+    "objectID": "decisions/20200602-manage-backend-with-k3s.html",
+    "href": "decisions/20200602-manage-backend-with-k3s.html",
+    "title": "Accepted: Manage backend resources on one or more physical machines with K3S",
     "section": "",
-    "text": "The implementation process is complex and may require advanced technical skills from users.\nSome steps, like creating a 3D model of the back of the avatar, may not always be successful.\nPainting errors and other imperfections may remain in the final avatar."
+    "text": "We want a way to manage backend resources on one or more physical machines.\n\n\n\nWe are using a lightweight Kubernetes implementation, k3s, to provide management of backend resources\n\n\n\n\n\nInstall Fedora 34 with a user account set as administrator.\nAdd authorized keys into ~/.ssh/authorized_keys\nOPTIONAL: customize SSH port: Set Port 2345 in /etc/ssh/sshd_config.\nsudo semanage port -a -t ssh_port_t -p tcp 2345\nsudo firewall-cmd --add-port=2345/tcp\nREQUIRED: set PasswordAuthentication no in /etc/ssh/sshd_config.\nOPTIONAL: Configure default DNS server:\n\n\n[main]\ndns=none\n[ipv4]\nmethod=auto\ndns=8.8.8.8;4.2.2.2;\nignore-auto-dns=true\n\n\n\nsearch localhost\nnameserver 1.0.0.1\nnameserver 1.1.1.1\n\n\n\nsudo service sshd restart\nsudo firewall-cmd --add-masquerade --permanent\nsudo systemctl restart firewalld\nsudo yum install redhat-lsb-core container-selinux selinux-policy-base podman\nsudo rpm -i https://github.com/rancher/k3s-selinux/releases/download/v0.1.1-rc1/k3s-selinux-0.1.1-rc1.el7.noarch.rpm\n# Validate that ssh logins work, then run:\nsudo service NetworkManager stop; sudo service NetworkManager start\nsudo grubby --update-kernel=ALL --args=\"systemd.unified_cgroup_hierarchy=0\"\nNow, reboot the system.\nFirst, create a new LVM Logical Volume named kubepvc XFS 100GB mounted at /kube. Add the following to /etc/fstab:\n\n\n\n# If created manually, run `sudo blkid` and add:\n# UUID=aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee /kube   auto  defaults   0 0\n/kube/rancher /var/lib/rancher    none bind 0 0`\n\n\n\nNow, setup the partition:\nsudo mkdir -p /kube\nsudo mount /kube\nsudo mkdir -p /kube/pvc /kube/rancher /var/lib/rancher /root/.kube\nsudo chcon -R -t container_file_t /kube/pvc\nsudo mount /var/lib/rancher\n\n\n\n\nIf your system uses SELinux, add the following SELinux module to allow dev-shm access. This will be necessary for python multiprocessing in containers, specifically usage of shm_lock, which is used by Emscripten.\n\n\nmodule dev-shm 1.0;\n\nrequire {\n        type container_runtime_tmpfs_t;\n        type container_t;\n        class dir { getattr relabelto unlink ioctl execute append read setattr write lock create rename link search rmdir remove_name reparent add_name open };\n        class file { map getattr relabelto unlink ioctl execute append read setattr write lock create rename relabelfrom link execute_no_trans entrypoint execmod open };\n        class shm { write destroy unix_write getattr create read setattr unix_read associate lock };\n        class sock_file { getattr relabelto unlink ioctl execute append read setattr write lock create rename relabelfrom link open };\n        class fifo_file { getattr relabelto unlink ioctl execute append read setattr write lock create rename relabelfrom link open };\n        class lnk_file { getattr relabelto unlink ioctl execute append read setattr write lock create rename relabelfrom link };\n}\n#============= container_t ==============\nallow container_t container_runtime_tmpfs_t:dir { getattr relabelto unlink ioctl execute append read setattr write lock create rename link search rmdir remove_name reparent add_name open };\n# domain_can_mmap_files\nallow container_t container_runtime_tmpfs_t:file { map getattr relabelto unlink ioctl execute append read setattr write lock create rename relabelfrom link execute_no_trans entrypoint execmod open };\nallow container_t container_runtime_tmpfs_t:shm { write destroy unix_write getattr create read setattr unix_read associate lock };\nallow container_t container_runtime_tmpfs_t:sock_file { getattr relabelto unlink ioctl execute append read setattr write lock create rename relabelfrom link open };\nallow container_t container_runtime_tmpfs_t:fifo_file { getattr relabelto unlink ioctl execute append read setattr write lock create rename relabelfrom link open };\nallow container_t container_runtime_tmpfs_t:lnk_file { getattr relabelto unlink ioctl execute append read setattr write lock create rename relabelfrom link };\nNow, install it with:\ncheckmodule -M -m dev-shm.te -o dev-shm.mod\nsemodule_package -m dev-shm.mod -o dev-shm.pp\nsudo semodule -i dev-shm.pp\n\n\n\n\ncurl -sfL https://raw.githubusercontent.com/rancher/k3s/master/install.sh | sh -s - server -o /root/.kube/config --default-local-storage-path /kube/pvc --disable=traefik --disable=servicelb --disable=flannel --disable=cni '--kubelet-arg=eviction-soft=memory.available&lt;0%,imagefs.available&lt;0%,nodefs.available&lt;0%' '--kubelet-arg=eviction-hard=memory.available&lt;0%,imagefs.available&lt;0%,nodefs.available&lt;0%'\nNow you will need to obtain the DNS IAM credentials. In this example, we are working with these Route53 hosted domains: vsekai.org,vsekai.net,vsekai.com,vsekai.cloud,v-sekai.org,v-sekai.net,v-sekai.com,v-sekai.cloud,vsek.ai,v-sek.ai\nInstall Helm services:\nACCESSKEY=AKIAABCDEFGHIJKLMNOP\nSECRETKEY=XXXXXXXXXXXXXXXXXXXX\n\nsudo helm repo add gocd https://gocd.github.io/helm-chart\nsudo helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx\nsudo helm repo add bitnami https://charts.bitnami.com/bitnami\nsudo helm repo add jetstack https://charts.jetstack.io\nsudo helm repo update\n\n# We are still using 3.2.3 - I have not figured out the upgrade process yet for external-dns\n\nsudo helm install external-dns --set provider=aws --set aws.zoneType=public --set registry=noop --set aws.credentials.accessKey=\"$ACCESSKEY\" --set domainFilters='{vsekai.org,vsekai.net,vsekai.com,vsekai.cloud,v-sekai.org,v-sekai.net,v-sekai.com,v-sekai.cloud,vsek.ai,v-sek.ai}' --set aws.credentials.secretKey=\"$SECRETKEY\"  bitnami/external-dns\n\n\n# NOTE: Some of these commands may be outdated:\n# They seem to refer to nginx-nginx-ingress but now it is nginx-ingress-nginx.\n# Take the following with a grain of salt:\n\nsudo kubectl create namespace ingress-nginx\nsudo helm install --namespace ingress-nginx nginx ingress-nginx/ingress-nginx --set controller.replicaCount=2\nsudo kubectl patch svc/nginx-nginx-ingress-controller -n kube-system --patch '{\"spec\":{\"externalTrafficPolicy\":\"Local\"}}'\nsudo kubectl patch deployments/nginx-nginx-ingress-controller --patch '{\"spec\":{\"template\":{\"spec\":{\"hostNetwork\":true}}}}' -n kube-system\n\nsudo kubectl get replicasets -n kube-system\n# Find the oldest nginx-nginx-ingress-controller one and delete with\nsudo kubectl delete replicasets -nginx-ingress-controller-abcdefg-whatever -n kube-system\n\n\n# Some weird stuff we changed. I don't think any of it is needed other than the above\n# externalTrafficPolicy and hostNetwork configuration changes.\n\ncat &gt; ingress-svc-edit.yaml\napiVersion: v1\nkind: Service\nmetadata:\n  annotations:\n    meta.helm.sh/release-name: nginx\n    meta.helm.sh/release-namespace: ingress-nginx\n    metallb.universe.tf/address-pool: default\n  creationTimestamp: \"2021-04-30T02:33:02Z\"\n  finalizers:\n  - service.kubernetes.io/load-balancer-cleanup\n  labels:\n    app.kubernetes.io/component: controller\n    app.kubernetes.io/instance: nginx\n    app.kubernetes.io/managed-by: Helm\n    app.kubernetes.io/name: ingress-nginx\n    app.kubernetes.io/version: 0.45.0\n    helm.sh/chart: ingress-nginx-3.29.0\n  name: nginx-ingress-nginx-controller\n  namespace: ingress-nginx\nspec:\n  clusterIP: 10.43.219.102\n  clusterIPs:\n  - 10.43.219.102\n  externalTrafficPolicy: Local\n  healthCheckNodePort: 32689\n  ipFamilies:\n  - IPv4\n  ipFamilyPolicy: SingleStack\n  ports:\n  - name: http\n    nodePort: 32595\n    port: 80\n    protocol: TCP\n    targetPort: http\n  - name: https\n    nodePort: 31937\n    port: 443\n    protocol: TCP\n    targetPort: https\n  selector:\n    app.kubernetes.io/component: controller\n    app.kubernetes.io/instance: nginx\n    app.kubernetes.io/name: ingress-nginx\n  sessionAffinity: None\n  type: LoadBalancer\nstatus:\n  loadBalancer:\n    ingress:\n    - ip: 999.999.999.999\n\nCtrl-D to save\n\nsudo kubectl apply -f ingress-svc-edit.yaml\n\nsudo kubectl patch -n ingress-nginx services/nginx-ingress-nginx-controller --patch '{\"metadata\":{\"annotations\":{\"metallb.universe.tf/address-pool\":\"default\"}},\"spec\":{\"externalTrafficPolicy\":\"Local\"}}\nsudo kubectl patch deployments/nginx-ingress-nginx-controller --patch '{\"spec\":{\"template\":{\"spec\":{\"hostNetwork\":true}}}}' -n ingress-nginx\n\n\n\n\n\nsudo kubectl create namespace cert-manager\n# Used --version v0.15.1 before; now v1.3.1\nsudo helm install cert-manager jetstack/cert-manager --namespace cert-manager --version v1.3.1 --set installCRDs=true\nsudo kubectl --namespace cert-manager create secret generic prod-route53-credentials-secret --from-literal=secret-access-key=\"$SECRETKEY\"\n\n\napiVersion: cert-manager.io/v1alpha2\nkind: ClusterIssuer\nmetadata:\n  name: letsencrypt-prod\n  namespace: cert-manager\nspec:\n  acme:\n    # The ACME server URL\n    server: https://acme-v02.api.letsencrypt.org/directory\n    # Email address used for ACME registration\n    email: example@example.com\n    # Name of a secret used to store the ACME account private key\n    privateKeySecretRef:\n      name: letsencrypt-prod\n    # Enable the HTTP-01 challenge provider\n    solvers:\n      - http01:\n          ingress:\n            class: nginx\n    #solvers:\n    #- dns01:\n    #   route53:\n    #     region: us-east-1\n    #     accessKeyID: AKIAABCDEFGHIJKLMNOP\n    #     secretAccessKeySecretRef:\n    #       name: prod-route53-credentials-secret\n    #       key: secret-access-key\n---\napiVersion: extensions/v1beta1\nkind: Ingress\nmetadata:\n  name: core-ingress\n  annotations:\n    kubernetes.io/ingress.class: \"nginx\"\n    cert-manager.io/cluster-issuer: \"letsencrypt-prod\"\n    nginx.ingress.kubernetes.io/hsts: \"false\"\n    # nginx.ingress.kubernetes.io/add-base-url: \"true\"\n    nginx.ingress.kubernetes.io/ssl-redirect: \"true\"\n    nginx.ingress.kubernetes.io/configuration-snippet: |\n      if ($host ~ ^(?!(ci))) {\n        more_clear_headers \"Strict-Transport-Security\";\n      }\n      if ($host ~ ^(.*\\.?)vsekai\\.([a-z]*)$ ) {\n          set $subd $1;\n          set $tld $2;\n          set $newdomain v-sekai.$tld;\n          rewrite ^/(.*)$ https://$subd$newdomain/$1;\n      }\nspec:\n  tls:\n    - hosts:\n        - vsekai.cloud\n        - v-sekai.cloud\n        - uro.vsekai.cloud\n        - uro.v-sekai.cloud\n        - radiance.v-sekai.cloud\n        - ci.radiance.v-sekai.cloud\n        - ci.v-sekai.cloud\n        - radiance.vsekai.cloud\n        - ci.radiance.vsekai.cloud\n        - ci.vsekai.cloud\n        - hls.vsek.ai\n      secretName: radiance-cert-secret1\n  rules:\n    - host: vsekai.cloud\n    - host: v-sekai.cloud\n    - host: uro.vsekai.cloud\n    - host: uro.v-sekai.cloud\n      http:\n        paths:\n          - path: /\n            backend:\n              serviceName: uro\n              servicePort: 4000\n    - host: hls.vsek.ai\n      http:\n        paths:\n          - path: /\n            backend:\n              serviceName: nginx-rtmp-service\n              servicePort: 80\n    - host: radiance.vsekai.cloud\n    - host: radiance.v-sekai.cloud\n      http:\n        paths:\n          - path: /debug_headers\n            backend:\n              serviceName: echo-service\n              servicePort: 8099\n          - path: /\n            backend:\n              serviceName: echo1\n              servicePort: 80\n    - host: ci.vsekai.cloud\n    - host: ci.v-sekai.cloud\n      http:\n        paths:\n          - path: /\n            backend:\n              serviceName: gocd-server\n              servicePort: 8153\n    - host: ci.radiance.vsekai.cloud\n    - host: ci.radiance.v-sekai.cloud\n      http:\n        paths:\n          - path: /\n            backend:\n              serviceName: gocd-server\n              servicePort: 8153\nThen:\nsudo kubectl apply -f ingress.yaml\n\n\n\n\n\n\napiVersion: v1\nkind: ConfigMap\nmetadata:\n  namespace: metallb-system\n  name: config\ndata:\n  config: |\n    address-pools:\n    - name: default\n      protocol: layer2\n      addresses:\n      - 108.85.109.49/32 # &lt;--- this is the external. HOST IP\nsudo kubectl create namespace metallb-system\nsudo kubectl create secret generic -n metallb-system memberlist --from-literal=secretkey=\"$(openssl rand -base64 128)\"\nsudo kubectl apply -f metalconfig.yml\nsudo kubectl apply -f https://raw.githubusercontent.com/metallb/metallb/v0.9.3/manifests/metallb.yaml\n\n\n\n\n(Optional in theory, but you have to remove enabled platforms in gocd):\nStart by grabbing a legitimate copy of MacOSX10.15.sdk.tar.xz from your local MacBook or Mac Mini.\nThen do the following to build:\ncd /opt\nsudo chown `whoami` .\ngit clone https://github.com/tpoechtrager/osxcross.git /opt/osxcross\nsudo chown root .\ncd /opt/osxcross\nmv MacOSX10.15.sdk.tar.xz /opt/osxcross/tarballs\nUNATTENDED=1 ./build.sh\n\n# In case host OS is newer than guest OS:\ncp -p /lib64/libstdc++.so.6 /opt/osxcross/target/bin/\nOn SELinux systems, you may need to give containers read permissions:\nsudo chcon -R unconfined_u:object_r:container_share_t:s0  /opt/osxcross\n\n\n\n\n\nagent:\n  image:\n    # agent.image.repository is the GoCD Agent image name\n    repository: \"groupsinfra/gocd-agent-centos-8-groups\" # agent.image.tag is the GoCD Agent image's tag\n    tag: v20.7.0-groups-0.5.3\n    # agent.image.pullPolicy is the GoCD Agent image's pull policy\n\n    pullPolicy: \"IfNotPresent\" # agent.replicaCount is the GoCD Agent replicas Count. Specify the number of GoCD agents to run\n  replicaCount: 6\n  security:\n    ssh:\n      enabled: true\n      secretName: gocd-ssh\nserver:\n  shouldPreconfigure: false\n  security:\n    ssh:\n      enabled: true\n      secretName: gocd-ssh\n  env:\n    extraEnvVars:\n      - name: GOCD_PLUGIN_INSTALL_gitlab-oauth-authorization-plugin\n        value: https://github.com/gocd-contrib/gitlab-oauth-authorization-plugin/releases/download/v2.0.1-52-exp/gitlab-oauth-authorization-plugin-2.0.1-52.jar\n\n\nssh-keygen -t rsa -b 4096 -C \"gocd-ssh-key\" -f gocd-ssh -P ''\n( ssh-keyscan gitlab.com ; ssh-keyscan github.com ) &gt; gocd_known_hosts\nsudo kubectl create secret generic gocd-ssh --from-file=id_rsa=gocd-ssh --from-file=id_rsa.pub=gocd-ssh.pub --from-file=known_hosts=gocd_known_hosts\n\n# Chart version 1.37.0 is gocd v21.2.0\nsudo helm install -f gocd_values.yaml gocd gocd/gocd --version 1.37.0\nsudo chcon -R -t container_file_t /kube/pvc\n# Installs a trash service on port 80 by default. Let's delete it:\nsudo kubectl delete ingress gocd-server\n# Instead of using \"kubectl scale\", scale agents by editing gocd_values.yaml\n# and do \"sudo helm upgrade -f ....\"\nsudo helm install -f gocd_values.yaml gocd gocd/gocd --version 1.37.0\n# Make sure to enable the agents in the web UI, and assign them to Resources and Environments.\n\n\n\n\n# Disable and Delete all agents in the AGENTS tab of gocd.\nEdit gocd_values.yaml and set agent version to latest (e.g. v21.2.0-groups-0.5.8)\nsudo helm upgrade -f gocd_values.yaml gocd gocd/gocd --version 1.37.0\nsudo kubectl delete ingress gocd-server\n# Upgrade gocd-agent-dind:\nsudo kubectl patch deployments/gocd-agent-dind --patch '{\"spec\":{\"template\":{\"spec\":{\"containers\":[{\"name\":\"gocd-agent-dind\",\"image\":\"gocd/gocd-agent-docker-dind:v21.2.0\"}]}}}}'\n# You can also use patch to upgrade gocd-agent and gocd-server instead of upgrading via helm chart. I sometimes do it that way.\n# Delete the old Agents on the web interface. Wait for the new agents to come up, and enable them and assign them as appropriate.\n\n\n\nCreate DockerHub permissions: Create an account if you do not have one. Visit https://hub.docker.com/settings/security and create an Access Token. Copy the token.\nsudo  kubectl create secret docker-registry regcred --docker-server=https://index.docker.io/v1/ --docker-username=dockerhubuser --docker-password=XXXX --docker-email=your.dockerhub.email@example.com\n\n\n\nFor osxcross (OSX cross compiling), make sure the OSX compiler SDK you created on mac os located at /opt/osxcross.\nIf you do not have osxcross (no access to Apple hardware), then you must create an empty directory at /opt/osxcross or remove the relevant volume mounts (and remove from enabled build targets in the gocd pipelines).\nNow create Docker-in-Docker, and apply this file with kubectl create -f dind.yaml or kubectl apply -f dind.yaml\n\n\n\napiVersion: apps/v1\nkind: Deployment\nmetadata:\n  labels:\n    app: gocd\n    component: agent-dind\n  name: gocd-agent-dind\n  namespace: default\nspec:\n  progressDeadlineSeconds: 600\n  replicas: 2\n  revisionHistoryLimit: 10\n  selector:\n    matchLabels:\n      app: gocd\n      component: agent-dind\n      release: gocd\n  strategy:\n    rollingUpdate:\n      maxSurge: 25%\n      maxUnavailable: 25%\n    type: RollingUpdate\n  template:\n    metadata:\n      creationTimestamp: null\n      labels:\n        app: gocd\n        component: agent-dind\n        release: gocd\n    spec:\n      containers:\n        - env:\n            - name: GO_SERVER_URL\n              value: http://gocd-server:8153/go\n          image: gocd/gocd-agent-docker-dind:v21.2.0\n          imagePullPolicy: IfNotPresent\n          name: gocd-agent-dind\n          resources: {}\n          securityContext:\n            privileged: true\n          terminationMessagePath: /dev/termination-log\n          terminationMessagePolicy: File\n          volumeMounts:\n            - mountPath: /root/.ssh\n              name: ssh-secrets\n              readOnly: true\n            - mountPath: /root/.docker\n              name: kaniko-secret\n            - mountPath: /opt/osxcross\n              name: opt-osxcross-volume\n              readOnly: true\n      dnsPolicy: ClusterFirst\n      restartPolicy: Always\n      schedulerName: default-scheduler\n      securityContext:\n        fsGroup: 0\n        runAsGroup: 0\n        runAsUser: 0\n      serviceAccount: default\n      serviceAccountName: default\n      terminationGracePeriodSeconds: 30\n      volumes:\n        - name: ssh-secrets\n          secret:\n            defaultMode: 256\n            secretName: gocd-ssh\n        - name: kaniko-secret\n          secret:\n            secretName: regcred\n            items:\n              - key: .dockerconfigjson\n                path: config.json\n        - name: opt-osxcross-volume\n          hostPath:\n            path: /opt/osxcross\n            type: Directory\n\n\n\n\nTo add osxcross support to the main agents, create the following patch:\ngocd-agent-patch.yaml\napiVersion: apps/v1\nkind: Deployment\nmetadata:\n  name: gocd-agent\nspec:\n  template:\n    spec:\n      containers:\n        - name: gocd-agent\n          volumeMounts:\n            - mountPath: /opt/osxcross\n              name: opt-osxcross-volume\n              readOnly: true\n      volumes:\n        - name: opt-osxcross-volume\n          hostPath:\n            path: /opt/osxcross\n            type: Directory\nand apply with:\nsudo kubectl patch deployments/gocd-agent -p \"$(cat gocd-agent-patch.yaml)\"\nMake sure to enable the Agents when they come up on the GoCD Dashboard. Add every server to the “development” environment. Also, assign linux servers to “mingw” and “linux”. Assign the dind agents to “dind”.\nFor GitLab, go to https://ci.v-sekai.cloud/go/admin/security/auth_configs and select Create new authorization configuration -&gt; gitlab-auth-config / GitLab Authentication plugin / follow documentation here: https://github.com/gocd-contrib/gitlab-oauth-authorization-plugin/blob/master/INSTALL.md - Do not check Allow only known users to login yet. If this works, you can skip the text auth step and corresponding passwd commands.\nCreate Guest login:\n\nGo to auth_configs, Create new authorization configuration -&gt; guest-login / Guest Login Plugin / Fill out Go server URL / Username view / Display name Guest.\nNow, go to Roles Management. Create role guest. Add Deny for all types and Resources * as desired.\nIn an Incognito window, visit the CI system and login as Guest. Close the incognito window.\nNow, go to Users Management. Select view / Guest and select Roles -&gt; guest\nAdmin -&gt; Pipelines. Select Pipeline Group beta, click + on the top right of the whole group, go to Roles, add guest, and only check View. Save this.\n\nAt this point, Guest should have permission to view pipelines, see logs, download artifacts but nothing else.\nFor text auth, go to https://ci.v-sekai.cloud/go/admin/security/auth_configs and select Create new authorization configuration -&gt; file-auth-config / Password File Authentication plugin / /godata/config/password.properties\nsudo kubectl exec gocd-server-6d77846995-5l244 -- touch /godata/config/password.properties\nsudo yum install httpd-tools\nhtpasswd -c -B passwd admin\ncat passwd | sudo kubectl exec gocd-server-6d77846995-5l244 -- sudo tee /kubepvc/pvc/*/godata/config/password.properties\nNow go to users page, edit your user and enable Global Admin.\nNow go to file-auth-config, edit configuration, enable Allow only known users to login\n\n\n\nGo to Admin -&gt; Config Repositories\n\nConfig #repository Name: groups-gocd-pipelines\nPlugin ID: JSON Configuration Plugin\nMaterial Type: Git\nURL: git@gitlab.com:godot-groups/groups-gocd-pipelines\nBranch: master\nGoCD pipeline files pattern: *.gopipeline.json\nGoCD environment files pattern: *.goenvironment.json\n\nRules\n\nAllow: Pipeline Group: beta\nAllow: Environment: development\n\n\n\n\ncurl -L https://github.com/fluxcd/flux2/releases/download/v0.24.1/flux_0.24.1_linux_amd64.tar.gz | tar -zxf - flux\nsudo cp flux /usr/local/bin/flux\nsudo chmod +x /usr/local/bin/flux\nsudo kubectl apply -f https://github.com/fluxcd/flux2/releases/download/v0.24.1/install.yaml\nFork the flux-config #repository from here https://github.com/V-Sekai/flux-config into your own github account, and set GHUSER=your github account.\nNow, in your fork of flux-config, go to project Settings -&gt; Deploy Keys and add the result of the above identity command. Make sure to check Allow write access.\nOnce you have done this, you can continue with the flux setup using your newly forked repository.\nexport GHUSER=\"xxxxxxxxx\"\nsudo flux install\nsudo flux create source git gitrepo --url=https://github.com/$GHUSER/flux-config  --branch=flux2\nsudo flux create kustomization workloads --source=GitRepository/gitrepo --path=\"./workloads/\"\nsudo flux get all\nFOR DEBUGGING ONLY: sudo setenforce permissive - this appears to have no effect, so there is a different problem.\n\n\n\n\n\nstatefulset:\n  resources:\n    limits:\n      memory: \"8Gi\"\n    requests:\n      memory: \"8Gi\"\nconf:\n  cache: \"2Gi\"\n  max-sql-memory: \"2Gi\"\ntls:\n  enabled: true\n\n\n\n\n# Helm version MAY be deprecated. We will switch to operator below.\n\n#sudo helm install cockroachdb --values cockroachdb.values.yaml cockroachdb/cockroachdb\n#sudo kubectl certificate approve default.node.cockroachdb-0\n#sudo kubectl certificate approve default.node.cockroachdb-1\n#sudo kubectl certificate approve default.node.cockroachdb-2\n#sudo kubectl certificate approve default.client.root\n\nwget https://raw.githubusercontent.com/cockroachdb/cockroach-operator/master/manifests/operator.yaml -O cockroach-operator.yaml\nsudo kubectl apply -f cockroach-operator.yaml\n\nwget https://raw.githubusercontent.com/cockroachdb/cockroach-operator/master/config/crd/bases/crdb.cockroachlabs.com_crdbclusters.yaml\nsudo kubectl apply -f crdb.yaml\n\ncat &gt; cockroachdb_extra_resource_certgen.yaml\napiVersion: v1\nkind: ServiceAccount\nmetadata:\n  name: cockroachdb\n  labels:\n    app: cockroachdb\n---\napiVersion: rbac.authorization.k8s.io/v1\nkind: Role\nmetadata:\n  name: cockroachdb\n  labels:\n    app: cockroachdb\nrules:\n- apiGroups:\n  - \"\"\n  resources:\n  - secrets\n  verbs:\n  - create\n  - get\n---\napiVersion: rbac.authorization.k8s.io/v1\nkind: ClusterRole\nmetadata:\n  name: cockroachdb\n  labels:\n    app: cockroachdb\nrules:\n- apiGroups:\n  - certificates.k8s.io\n  resources:\n  - certificatesigningrequests\n  verbs:\n  - create\n  - get\n  - watch\n---\napiVersion: rbac.authorization.k8s.io/v1\nkind: RoleBinding\nmetadata:\n  name: cockroachdb\n  labels:\n    app: cockroachdb\nroleRef:\n  apiGroup: rbac.authorization.k8s.io\n  kind: Role\n  name: cockroachdb\nsubjects:\n- kind: ServiceAccount\n  name: cockroachdb\n  namespace: default\n---\napiVersion: rbac.authorization.k8s.io/v1\nkind: ClusterRoleBinding\nmetadata:\n  name: cockroachdb\n  labels:\n    app: cockroachdb\nroleRef:\n  apiGroup: rbac.authorization.k8s.io\n  kind: ClusterRole\n  name: cockroachdb\nsubjects:\n- kind: ServiceAccount\n  name: cockroachdb\n  namespace: default\n\nCtrl-D\n\n\n# Note: may need to set up physicalVolume and physicalVolumeClaim objects for each cockraoch node.\n\n# The permissions may be set wrong if you are upgrading. Fix them with:\nsudo chown -R 1000581000 /kube/pvc/pvc-aaaaaaaaaaaaaaaaaa /kube/pvc/pvc-bbbbbbbbbbbbbbb /kube/pvc/pvc-cccccccccccccccccccccccccccccccc\n\n# OLD curl -o client-secure.yaml https://raw.githubusercontent.com/cockroachdb/cockroach/master/cloud/kubernetes/client-secure.yaml\n# OLD sudo kubectl apply -f client-secure.yaml\n\nwget https://raw.githubusercontent.com/cockroachdb/cockroach-operator/master/examples/client-secure-operator.yaml\nsudo kubectl apply -f client-secure-operator.yaml\n\nsudo kubectl certificate approve default.client.uro-prod\n\nsudo kubectl exec -it cockroachdb-client-secure -- ./cockroach sql --certs-dir=/cockroach-certs --host=cockroachdb-public\nIn SQL, write:\nCREATE DATABASE uro_prod;\nCREATE USER 'uro-prod' WITH PASSWORD 'blablablablaSOMEDATABASEPASSWORD';\nGRANT ALL ON DATABASE uro_prod to \"uro-prod\";\nTo make backups:\nsudo kubectl exec -it cockroachdb-client-secure -- ./cockroach dump --certs-dir=/cockroach-certs --host=cockroachdb-public uro_prod &gt; uro_prod_backup.txt\nApply secrets:\n(On dev machine) MIX_ENV=prod mix phx.gen.secret\n# Copy the output of above, and copy the database password from above:\nsudo kubectl create secret generic uro-prod --from-literal=secret-key-base='GENERATED_WITH_ABOVE_COMMAND' --from-literal=pass='blablablablaSOMEDATABASEPASSWORD'\n\nsudo kubectl apply -f https://raw.githubusercontent.com/V-Sekai/uro/master/kubernetes.yaml\n\n\n\n\n\n\nk3s set the default client cert for root to expire after a year or so. This leads to a problem where you can’t administer your own cluster because your root account’s cert is expired. So I had to figure out how to fix this.\nFor the most part, the process I came up with matches this more concise post here: https://github.com/k3s-io/k3s/issues/2342#issuecomment-713016341\nFirst approach, how to rotate kube client certificates: Because we need to modify /root/.kube/config, I ran sudo -i to login as a root shell.\n\nmkdir tls and create tls/config.txt with the following lines:\n\n# --------------------- tls/config.txt -----------\n[ req ]\ndistinguished_name                           = req_distinguished_name\nreq_extensions                                   = v3_req\nprompt = no\n[ req_distinguished_name ]\norganizationName       = system:masters\ncommonName             = system:admin\n[ v3_req ]\nbasicConstraints                                 = CA:FALSE\nkeyUsage                                           = critical, digitalSignature, keyEncipherment\nextendedKeyUsage                            = clientAuth\n# -------------------------------------------------\n\ncp /kube/rancher/k3s/server/tls/client-ca.crt tls/client-ca.crt\nopenssl ecparam -name prime256v1 -genkey -noout -out tls/new-key.pem\nopenssl req -new -key tls/new-key.pem -sha256 -nodes -out tls/new-req.csr -config tls/config.txt\nopenssl x509 -req -days 3000 -in tls/new-req.csr -CA tls/client-ca.crt -CAkey /kube/rancher/k3s/server/tls/client-ca.key -set_serial 4294742997922865905 -extensions v3_req -extfile tls/config.txt -out tls/new-client.crt\ncat tls/new-client.crt tls/client-ca.crt | base64 -w0; echo\ncat tls/new-key.pem | base64 -w0; echo\nedit .kube/config and update client-certificate-data: and client-key-data: respectively.\n\nHow to upgrade the rest of the certs.\nfind /var/lib/rancher/k3s/server/tls -name '*.crt' | while read fn; do echo $fn ===========; openssl x509 -text -in $fn | grep Not\\ After | grep '202[012]'; done\nHere is the script I ran:\n#!/bin/bash\nset -\nset -x\n[ -e \"$1.csr\" ] || openssl x509 -x509toreq -in \"$1.crt\" -out \"$1.csr\" -signkey \"$1.key\"\nmv -i \"$1.crt\" \"$1.crt.bak.$(date +%s)\"\nopenssl x509 -req -in \"$1.csr\" -CA \"client-ca.crt\" -CAkey \"client-ca.key\" -CAcreateserial -days 3650 -out \"$1.crt\"\ncat \"client-ca.crt\" &gt;&gt; \"$1.crt\"\nyou can use this process to update the client cert for /root/.kube/config\nNote that etcd/client.crt actually uses its own server-ca.key instead of client-ca within the etcd folder, so you need a slight modification of the script for this one. I don’t know what any of these certs do so I just did all of them\nFinally, client-k3s-controller.crt and client-kube-proxy.crt must be copied from /var/lib/rancher/k3s/server/tls to /var/lib/rancher/k3s/agent\n\n\n\nStart the upgrade process with:\nsudo dnf upgrade --refresh\nsudo dnf install dnf-plugin-system-upgrade\nsudo dnf system-upgrade download --releasever=34\nAnswer y to all prompts confirming list of packages and new GPG keys, if any. Once successful, it displays:\nDownload complete! Use 'dnf system-upgrade reboot' to start the upgrade.\nTo remove cached metadata and transaction use 'dnf system-upgrade clean'\nThe downloaded packages were saved in cache until the next successful transaction.\nYou can remove cached packages by executing 'dnf clean packages'.\nComplete the upgrade with:\nsudo dnf system-upgrade reboot\nThis will bring the system down for about an hour.\n\n\n\nsudo helm repo update\n# If the stable/nginx-ingress chart is still installed, make sure to helm uninstall nginx first.\nsudo helm upgrade --namespace ingress-nginx nginx ingress-nginx/ingress-nginx --set controller.replicaCount=2\nsudo helm upgrade cert-manager jetstack/cert-manager --namespace cert-manager --set installCRDs=true\n### I was not able to get external-dns to upgrade, but it is not user-facing so we keep running the old version.\n# sudo helm upgrade external-dns --reuse-values bitnami/external-dns\n\n\n\ncurl -sfL https://raw.githubusercontent.com/rancher/k3s/master/install.sh | sh -s - server -o /root/.kube/config --default-local-storage-path /kube/pvc --no-deploy=servicelb --disable=traefik --disable=servicelb\n\n\n\nRun the shell:\nsudo kubectl exec -it cockroachdb-client-secure -- ./cockroach sql --certs-dir=/cockroach-certs --host=cockroachdb-public\nAt the top of the shell prompt, it will say something like this. Copy the first two numbers from the CockroachDB CCL line. In this case, 20.2\n#\n# Welcome to the CockroachDB SQL shell.\n# All statements must be terminated by a semicolon.\n# To exit, type: \\q.\n#\n# Server version: CockroachDB CCL v20.2.2 (x86_64-unknown-linux-gnu\nReplace some.version in the following command with the value we found above:\nSET CLUSTER SETTING cluster.preserve_downgrade_option = 'some.version';\nFinally, perform the upgrade:\nsudo kubectl delete job cockroachdb-init\nsudo helm upgrade cockroachdb cockroachdb/cockroachdb --values cockroachdb.values.yaml\ncurl -o client-secure.yaml https://raw.githubusercontent.com/cockroachdb/cockroach/master/cloud/kubernetes/client-secure.yaml\nsudo kubectl delete pods/cockroachdb-client-secure\nsudo kubectl create -f client-secure.yaml\n\n\n\n\n\n\nKnowledge gains about service creation\nOperation experience\n\n\n\n\n\nConstant maintenance\n\n\n\n\n\nOption: Dedicated Servers\nOption: Virtual Machines\n\n\n\n\nYes, it is possible to deploy this system using docker or in the root system.\n\n\n\nHaving experience with kubernetes and maintaining discipline will make scaling or service upgrades smoother in the future.\n\n\n\n\nhttps://k3s.io/\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20230716-enhancing-avatar-creation-process-01-regular.html#option-graveyard",
-    "href": "decisions/20230716-enhancing-avatar-creation-process-01-regular.html#option-graveyard",
-    "title": "Proposed: Enhancing Avatar Creation Process in V-Sekai Regular",
+    "objectID": "decisions/20200602-manage-backend-with-k3s.html#context-and-problem-statement",
+    "href": "decisions/20200602-manage-backend-with-k3s.html#context-and-problem-statement",
+    "title": "Accepted: Manage backend resources on one or more physical machines with K3S",
     "section": "",
-    "text": "Excessive complexity or technical requirements: We want the avatar creation process to be user-friendly and accessible to a wide range of users, so any options that require advanced technical skills or have excessively complex customization controls will not be included."
+    "text": "We want a way to manage backend resources on one or more physical machines."
   },
   {
-    "objectID": "decisions/20230716-enhancing-avatar-creation-process-01-regular.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230716-enhancing-avatar-creation-process-01-regular.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Enhancing Avatar Creation Process in V-Sekai Regular",
+    "objectID": "decisions/20200602-manage-backend-with-k3s.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "href": "decisions/20200602-manage-backend-with-k3s.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
+    "title": "Accepted: Manage backend resources on one or more physical machines with K3S",
     "section": "",
-    "text": "No, the proposed enhancement involves a multi-step process that cannot be easily replicated with just a few lines of script."
+    "text": "We are using a lightweight Kubernetes implementation, k3s, to provide management of backend resources"
   },
   {
-    "objectID": "decisions/20230716-enhancing-avatar-creation-process-01-regular.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230716-enhancing-avatar-creation-process-01-regular.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Enhancing Avatar Creation Process in V-Sekai Regular",
+    "objectID": "decisions/20200602-manage-backend-with-k3s.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20200602-manage-backend-with-k3s.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Accepted: Manage backend resources on one or more physical machines with K3S",
     "section": "",
-    "text": "The proposed enhancement addresses the limitations in V-Sekai’s avatar creation process, providing users with a comprehensive solution for creating highly customizable avatars. By implementing these tools and techniques within the platform, V-Sekai can offer a more robust and user-friendly experience for its community."
+    "text": "Install Fedora 34 with a user account set as administrator.\nAdd authorized keys into ~/.ssh/authorized_keys\nOPTIONAL: customize SSH port: Set Port 2345 in /etc/ssh/sshd_config.\nsudo semanage port -a -t ssh_port_t -p tcp 2345\nsudo firewall-cmd --add-port=2345/tcp\nREQUIRED: set PasswordAuthentication no in /etc/ssh/sshd_config.\nOPTIONAL: Configure default DNS server:\n\n\n[main]\ndns=none\n[ipv4]\nmethod=auto\ndns=8.8.8.8;4.2.2.2;\nignore-auto-dns=true\n\n\n\nsearch localhost\nnameserver 1.0.0.1\nnameserver 1.1.1.1\n\n\n\nsudo service sshd restart\nsudo firewall-cmd --add-masquerade --permanent\nsudo systemctl restart firewalld\nsudo yum install redhat-lsb-core container-selinux selinux-policy-base podman\nsudo rpm -i https://github.com/rancher/k3s-selinux/releases/download/v0.1.1-rc1/k3s-selinux-0.1.1-rc1.el7.noarch.rpm\n# Validate that ssh logins work, then run:\nsudo service NetworkManager stop; sudo service NetworkManager start\nsudo grubby --update-kernel=ALL --args=\"systemd.unified_cgroup_hierarchy=0\"\nNow, reboot the system.\nFirst, create a new LVM Logical Volume named kubepvc XFS 100GB mounted at /kube. Add the following to /etc/fstab:\n\n\n\n# If created manually, run `sudo blkid` and add:\n# UUID=aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee /kube   auto  defaults   0 0\n/kube/rancher /var/lib/rancher    none bind 0 0`\n\n\n\nNow, setup the partition:\nsudo mkdir -p /kube\nsudo mount /kube\nsudo mkdir -p /kube/pvc /kube/rancher /var/lib/rancher /root/.kube\nsudo chcon -R -t container_file_t /kube/pvc\nsudo mount /var/lib/rancher\n\n\n\n\nIf your system uses SELinux, add the following SELinux module to allow dev-shm access. This will be necessary for python multiprocessing in containers, specifically usage of shm_lock, which is used by Emscripten.\n\n\nmodule dev-shm 1.0;\n\nrequire {\n        type container_runtime_tmpfs_t;\n        type container_t;\n        class dir { getattr relabelto unlink ioctl execute append read setattr write lock create rename link search rmdir remove_name reparent add_name open };\n        class file { map getattr relabelto unlink ioctl execute append read setattr write lock create rename relabelfrom link execute_no_trans entrypoint execmod open };\n        class shm { write destroy unix_write getattr create read setattr unix_read associate lock };\n        class sock_file { getattr relabelto unlink ioctl execute append read setattr write lock create rename relabelfrom link open };\n        class fifo_file { getattr relabelto unlink ioctl execute append read setattr write lock create rename relabelfrom link open };\n        class lnk_file { getattr relabelto unlink ioctl execute append read setattr write lock create rename relabelfrom link };\n}\n#============= container_t ==============\nallow container_t container_runtime_tmpfs_t:dir { getattr relabelto unlink ioctl execute append read setattr write lock create rename link search rmdir remove_name reparent add_name open };\n# domain_can_mmap_files\nallow container_t container_runtime_tmpfs_t:file { map getattr relabelto unlink ioctl execute append read setattr write lock create rename relabelfrom link execute_no_trans entrypoint execmod open };\nallow container_t container_runtime_tmpfs_t:shm { write destroy unix_write getattr create read setattr unix_read associate lock };\nallow container_t container_runtime_tmpfs_t:sock_file { getattr relabelto unlink ioctl execute append read setattr write lock create rename relabelfrom link open };\nallow container_t container_runtime_tmpfs_t:fifo_file { getattr relabelto unlink ioctl execute append read setattr write lock create rename relabelfrom link open };\nallow container_t container_runtime_tmpfs_t:lnk_file { getattr relabelto unlink ioctl execute append read setattr write lock create rename relabelfrom link };\nNow, install it with:\ncheckmodule -M -m dev-shm.te -o dev-shm.mod\nsemodule_package -m dev-shm.mod -o dev-shm.pp\nsudo semodule -i dev-shm.pp\n\n\n\n\ncurl -sfL https://raw.githubusercontent.com/rancher/k3s/master/install.sh | sh -s - server -o /root/.kube/config --default-local-storage-path /kube/pvc --disable=traefik --disable=servicelb --disable=flannel --disable=cni '--kubelet-arg=eviction-soft=memory.available&lt;0%,imagefs.available&lt;0%,nodefs.available&lt;0%' '--kubelet-arg=eviction-hard=memory.available&lt;0%,imagefs.available&lt;0%,nodefs.available&lt;0%'\nNow you will need to obtain the DNS IAM credentials. In this example, we are working with these Route53 hosted domains: vsekai.org,vsekai.net,vsekai.com,vsekai.cloud,v-sekai.org,v-sekai.net,v-sekai.com,v-sekai.cloud,vsek.ai,v-sek.ai\nInstall Helm services:\nACCESSKEY=AKIAABCDEFGHIJKLMNOP\nSECRETKEY=XXXXXXXXXXXXXXXXXXXX\n\nsudo helm repo add gocd https://gocd.github.io/helm-chart\nsudo helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx\nsudo helm repo add bitnami https://charts.bitnami.com/bitnami\nsudo helm repo add jetstack https://charts.jetstack.io\nsudo helm repo update\n\n# We are still using 3.2.3 - I have not figured out the upgrade process yet for external-dns\n\nsudo helm install external-dns --set provider=aws --set aws.zoneType=public --set registry=noop --set aws.credentials.accessKey=\"$ACCESSKEY\" --set domainFilters='{vsekai.org,vsekai.net,vsekai.com,vsekai.cloud,v-sekai.org,v-sekai.net,v-sekai.com,v-sekai.cloud,vsek.ai,v-sek.ai}' --set aws.credentials.secretKey=\"$SECRETKEY\"  bitnami/external-dns\n\n\n# NOTE: Some of these commands may be outdated:\n# They seem to refer to nginx-nginx-ingress but now it is nginx-ingress-nginx.\n# Take the following with a grain of salt:\n\nsudo kubectl create namespace ingress-nginx\nsudo helm install --namespace ingress-nginx nginx ingress-nginx/ingress-nginx --set controller.replicaCount=2\nsudo kubectl patch svc/nginx-nginx-ingress-controller -n kube-system --patch '{\"spec\":{\"externalTrafficPolicy\":\"Local\"}}'\nsudo kubectl patch deployments/nginx-nginx-ingress-controller --patch '{\"spec\":{\"template\":{\"spec\":{\"hostNetwork\":true}}}}' -n kube-system\n\nsudo kubectl get replicasets -n kube-system\n# Find the oldest nginx-nginx-ingress-controller one and delete with\nsudo kubectl delete replicasets -nginx-ingress-controller-abcdefg-whatever -n kube-system\n\n\n# Some weird stuff we changed. I don't think any of it is needed other than the above\n# externalTrafficPolicy and hostNetwork configuration changes.\n\ncat &gt; ingress-svc-edit.yaml\napiVersion: v1\nkind: Service\nmetadata:\n  annotations:\n    meta.helm.sh/release-name: nginx\n    meta.helm.sh/release-namespace: ingress-nginx\n    metallb.universe.tf/address-pool: default\n  creationTimestamp: \"2021-04-30T02:33:02Z\"\n  finalizers:\n  - service.kubernetes.io/load-balancer-cleanup\n  labels:\n    app.kubernetes.io/component: controller\n    app.kubernetes.io/instance: nginx\n    app.kubernetes.io/managed-by: Helm\n    app.kubernetes.io/name: ingress-nginx\n    app.kubernetes.io/version: 0.45.0\n    helm.sh/chart: ingress-nginx-3.29.0\n  name: nginx-ingress-nginx-controller\n  namespace: ingress-nginx\nspec:\n  clusterIP: 10.43.219.102\n  clusterIPs:\n  - 10.43.219.102\n  externalTrafficPolicy: Local\n  healthCheckNodePort: 32689\n  ipFamilies:\n  - IPv4\n  ipFamilyPolicy: SingleStack\n  ports:\n  - name: http\n    nodePort: 32595\n    port: 80\n    protocol: TCP\n    targetPort: http\n  - name: https\n    nodePort: 31937\n    port: 443\n    protocol: TCP\n    targetPort: https\n  selector:\n    app.kubernetes.io/component: controller\n    app.kubernetes.io/instance: nginx\n    app.kubernetes.io/name: ingress-nginx\n  sessionAffinity: None\n  type: LoadBalancer\nstatus:\n  loadBalancer:\n    ingress:\n    - ip: 999.999.999.999\n\nCtrl-D to save\n\nsudo kubectl apply -f ingress-svc-edit.yaml\n\nsudo kubectl patch -n ingress-nginx services/nginx-ingress-nginx-controller --patch '{\"metadata\":{\"annotations\":{\"metallb.universe.tf/address-pool\":\"default\"}},\"spec\":{\"externalTrafficPolicy\":\"Local\"}}\nsudo kubectl patch deployments/nginx-ingress-nginx-controller --patch '{\"spec\":{\"template\":{\"spec\":{\"hostNetwork\":true}}}}' -n ingress-nginx\n\n\n\n\n\nsudo kubectl create namespace cert-manager\n# Used --version v0.15.1 before; now v1.3.1\nsudo helm install cert-manager jetstack/cert-manager --namespace cert-manager --version v1.3.1 --set installCRDs=true\nsudo kubectl --namespace cert-manager create secret generic prod-route53-credentials-secret --from-literal=secret-access-key=\"$SECRETKEY\"\n\n\napiVersion: cert-manager.io/v1alpha2\nkind: ClusterIssuer\nmetadata:\n  name: letsencrypt-prod\n  namespace: cert-manager\nspec:\n  acme:\n    # The ACME server URL\n    server: https://acme-v02.api.letsencrypt.org/directory\n    # Email address used for ACME registration\n    email: example@example.com\n    # Name of a secret used to store the ACME account private key\n    privateKeySecretRef:\n      name: letsencrypt-prod\n    # Enable the HTTP-01 challenge provider\n    solvers:\n      - http01:\n          ingress:\n            class: nginx\n    #solvers:\n    #- dns01:\n    #   route53:\n    #     region: us-east-1\n    #     accessKeyID: AKIAABCDEFGHIJKLMNOP\n    #     secretAccessKeySecretRef:\n    #       name: prod-route53-credentials-secret\n    #       key: secret-access-key\n---\napiVersion: extensions/v1beta1\nkind: Ingress\nmetadata:\n  name: core-ingress\n  annotations:\n    kubernetes.io/ingress.class: \"nginx\"\n    cert-manager.io/cluster-issuer: \"letsencrypt-prod\"\n    nginx.ingress.kubernetes.io/hsts: \"false\"\n    # nginx.ingress.kubernetes.io/add-base-url: \"true\"\n    nginx.ingress.kubernetes.io/ssl-redirect: \"true\"\n    nginx.ingress.kubernetes.io/configuration-snippet: |\n      if ($host ~ ^(?!(ci))) {\n        more_clear_headers \"Strict-Transport-Security\";\n      }\n      if ($host ~ ^(.*\\.?)vsekai\\.([a-z]*)$ ) {\n          set $subd $1;\n          set $tld $2;\n          set $newdomain v-sekai.$tld;\n          rewrite ^/(.*)$ https://$subd$newdomain/$1;\n      }\nspec:\n  tls:\n    - hosts:\n        - vsekai.cloud\n        - v-sekai.cloud\n        - uro.vsekai.cloud\n        - uro.v-sekai.cloud\n        - radiance.v-sekai.cloud\n        - ci.radiance.v-sekai.cloud\n        - ci.v-sekai.cloud\n        - radiance.vsekai.cloud\n        - ci.radiance.vsekai.cloud\n        - ci.vsekai.cloud\n        - hls.vsek.ai\n      secretName: radiance-cert-secret1\n  rules:\n    - host: vsekai.cloud\n    - host: v-sekai.cloud\n    - host: uro.vsekai.cloud\n    - host: uro.v-sekai.cloud\n      http:\n        paths:\n          - path: /\n            backend:\n              serviceName: uro\n              servicePort: 4000\n    - host: hls.vsek.ai\n      http:\n        paths:\n          - path: /\n            backend:\n              serviceName: nginx-rtmp-service\n              servicePort: 80\n    - host: radiance.vsekai.cloud\n    - host: radiance.v-sekai.cloud\n      http:\n        paths:\n          - path: /debug_headers\n            backend:\n              serviceName: echo-service\n              servicePort: 8099\n          - path: /\n            backend:\n              serviceName: echo1\n              servicePort: 80\n    - host: ci.vsekai.cloud\n    - host: ci.v-sekai.cloud\n      http:\n        paths:\n          - path: /\n            backend:\n              serviceName: gocd-server\n              servicePort: 8153\n    - host: ci.radiance.vsekai.cloud\n    - host: ci.radiance.v-sekai.cloud\n      http:\n        paths:\n          - path: /\n            backend:\n              serviceName: gocd-server\n              servicePort: 8153\nThen:\nsudo kubectl apply -f ingress.yaml\n\n\n\n\n\n\napiVersion: v1\nkind: ConfigMap\nmetadata:\n  namespace: metallb-system\n  name: config\ndata:\n  config: |\n    address-pools:\n    - name: default\n      protocol: layer2\n      addresses:\n      - 108.85.109.49/32 # &lt;--- this is the external. HOST IP\nsudo kubectl create namespace metallb-system\nsudo kubectl create secret generic -n metallb-system memberlist --from-literal=secretkey=\"$(openssl rand -base64 128)\"\nsudo kubectl apply -f metalconfig.yml\nsudo kubectl apply -f https://raw.githubusercontent.com/metallb/metallb/v0.9.3/manifests/metallb.yaml\n\n\n\n\n(Optional in theory, but you have to remove enabled platforms in gocd):\nStart by grabbing a legitimate copy of MacOSX10.15.sdk.tar.xz from your local MacBook or Mac Mini.\nThen do the following to build:\ncd /opt\nsudo chown `whoami` .\ngit clone https://github.com/tpoechtrager/osxcross.git /opt/osxcross\nsudo chown root .\ncd /opt/osxcross\nmv MacOSX10.15.sdk.tar.xz /opt/osxcross/tarballs\nUNATTENDED=1 ./build.sh\n\n# In case host OS is newer than guest OS:\ncp -p /lib64/libstdc++.so.6 /opt/osxcross/target/bin/\nOn SELinux systems, you may need to give containers read permissions:\nsudo chcon -R unconfined_u:object_r:container_share_t:s0  /opt/osxcross\n\n\n\n\n\nagent:\n  image:\n    # agent.image.repository is the GoCD Agent image name\n    repository: \"groupsinfra/gocd-agent-centos-8-groups\" # agent.image.tag is the GoCD Agent image's tag\n    tag: v20.7.0-groups-0.5.3\n    # agent.image.pullPolicy is the GoCD Agent image's pull policy\n\n    pullPolicy: \"IfNotPresent\" # agent.replicaCount is the GoCD Agent replicas Count. Specify the number of GoCD agents to run\n  replicaCount: 6\n  security:\n    ssh:\n      enabled: true\n      secretName: gocd-ssh\nserver:\n  shouldPreconfigure: false\n  security:\n    ssh:\n      enabled: true\n      secretName: gocd-ssh\n  env:\n    extraEnvVars:\n      - name: GOCD_PLUGIN_INSTALL_gitlab-oauth-authorization-plugin\n        value: https://github.com/gocd-contrib/gitlab-oauth-authorization-plugin/releases/download/v2.0.1-52-exp/gitlab-oauth-authorization-plugin-2.0.1-52.jar\n\n\nssh-keygen -t rsa -b 4096 -C \"gocd-ssh-key\" -f gocd-ssh -P ''\n( ssh-keyscan gitlab.com ; ssh-keyscan github.com ) &gt; gocd_known_hosts\nsudo kubectl create secret generic gocd-ssh --from-file=id_rsa=gocd-ssh --from-file=id_rsa.pub=gocd-ssh.pub --from-file=known_hosts=gocd_known_hosts\n\n# Chart version 1.37.0 is gocd v21.2.0\nsudo helm install -f gocd_values.yaml gocd gocd/gocd --version 1.37.0\nsudo chcon -R -t container_file_t /kube/pvc\n# Installs a trash service on port 80 by default. Let's delete it:\nsudo kubectl delete ingress gocd-server\n# Instead of using \"kubectl scale\", scale agents by editing gocd_values.yaml\n# and do \"sudo helm upgrade -f ....\"\nsudo helm install -f gocd_values.yaml gocd gocd/gocd --version 1.37.0\n# Make sure to enable the agents in the web UI, and assign them to Resources and Environments.\n\n\n\n\n# Disable and Delete all agents in the AGENTS tab of gocd.\nEdit gocd_values.yaml and set agent version to latest (e.g. v21.2.0-groups-0.5.8)\nsudo helm upgrade -f gocd_values.yaml gocd gocd/gocd --version 1.37.0\nsudo kubectl delete ingress gocd-server\n# Upgrade gocd-agent-dind:\nsudo kubectl patch deployments/gocd-agent-dind --patch '{\"spec\":{\"template\":{\"spec\":{\"containers\":[{\"name\":\"gocd-agent-dind\",\"image\":\"gocd/gocd-agent-docker-dind:v21.2.0\"}]}}}}'\n# You can also use patch to upgrade gocd-agent and gocd-server instead of upgrading via helm chart. I sometimes do it that way.\n# Delete the old Agents on the web interface. Wait for the new agents to come up, and enable them and assign them as appropriate.\n\n\n\nCreate DockerHub permissions: Create an account if you do not have one. Visit https://hub.docker.com/settings/security and create an Access Token. Copy the token.\nsudo  kubectl create secret docker-registry regcred --docker-server=https://index.docker.io/v1/ --docker-username=dockerhubuser --docker-password=XXXX --docker-email=your.dockerhub.email@example.com\n\n\n\nFor osxcross (OSX cross compiling), make sure the OSX compiler SDK you created on mac os located at /opt/osxcross.\nIf you do not have osxcross (no access to Apple hardware), then you must create an empty directory at /opt/osxcross or remove the relevant volume mounts (and remove from enabled build targets in the gocd pipelines).\nNow create Docker-in-Docker, and apply this file with kubectl create -f dind.yaml or kubectl apply -f dind.yaml\n\n\n\napiVersion: apps/v1\nkind: Deployment\nmetadata:\n  labels:\n    app: gocd\n    component: agent-dind\n  name: gocd-agent-dind\n  namespace: default\nspec:\n  progressDeadlineSeconds: 600\n  replicas: 2\n  revisionHistoryLimit: 10\n  selector:\n    matchLabels:\n      app: gocd\n      component: agent-dind\n      release: gocd\n  strategy:\n    rollingUpdate:\n      maxSurge: 25%\n      maxUnavailable: 25%\n    type: RollingUpdate\n  template:\n    metadata:\n      creationTimestamp: null\n      labels:\n        app: gocd\n        component: agent-dind\n        release: gocd\n    spec:\n      containers:\n        - env:\n            - name: GO_SERVER_URL\n              value: http://gocd-server:8153/go\n          image: gocd/gocd-agent-docker-dind:v21.2.0\n          imagePullPolicy: IfNotPresent\n          name: gocd-agent-dind\n          resources: {}\n          securityContext:\n            privileged: true\n          terminationMessagePath: /dev/termination-log\n          terminationMessagePolicy: File\n          volumeMounts:\n            - mountPath: /root/.ssh\n              name: ssh-secrets\n              readOnly: true\n            - mountPath: /root/.docker\n              name: kaniko-secret\n            - mountPath: /opt/osxcross\n              name: opt-osxcross-volume\n              readOnly: true\n      dnsPolicy: ClusterFirst\n      restartPolicy: Always\n      schedulerName: default-scheduler\n      securityContext:\n        fsGroup: 0\n        runAsGroup: 0\n        runAsUser: 0\n      serviceAccount: default\n      serviceAccountName: default\n      terminationGracePeriodSeconds: 30\n      volumes:\n        - name: ssh-secrets\n          secret:\n            defaultMode: 256\n            secretName: gocd-ssh\n        - name: kaniko-secret\n          secret:\n            secretName: regcred\n            items:\n              - key: .dockerconfigjson\n                path: config.json\n        - name: opt-osxcross-volume\n          hostPath:\n            path: /opt/osxcross\n            type: Directory\n\n\n\n\nTo add osxcross support to the main agents, create the following patch:\ngocd-agent-patch.yaml\napiVersion: apps/v1\nkind: Deployment\nmetadata:\n  name: gocd-agent\nspec:\n  template:\n    spec:\n      containers:\n        - name: gocd-agent\n          volumeMounts:\n            - mountPath: /opt/osxcross\n              name: opt-osxcross-volume\n              readOnly: true\n      volumes:\n        - name: opt-osxcross-volume\n          hostPath:\n            path: /opt/osxcross\n            type: Directory\nand apply with:\nsudo kubectl patch deployments/gocd-agent -p \"$(cat gocd-agent-patch.yaml)\"\nMake sure to enable the Agents when they come up on the GoCD Dashboard. Add every server to the “development” environment. Also, assign linux servers to “mingw” and “linux”. Assign the dind agents to “dind”.\nFor GitLab, go to https://ci.v-sekai.cloud/go/admin/security/auth_configs and select Create new authorization configuration -&gt; gitlab-auth-config / GitLab Authentication plugin / follow documentation here: https://github.com/gocd-contrib/gitlab-oauth-authorization-plugin/blob/master/INSTALL.md - Do not check Allow only known users to login yet. If this works, you can skip the text auth step and corresponding passwd commands.\nCreate Guest login:\n\nGo to auth_configs, Create new authorization configuration -&gt; guest-login / Guest Login Plugin / Fill out Go server URL / Username view / Display name Guest.\nNow, go to Roles Management. Create role guest. Add Deny for all types and Resources * as desired.\nIn an Incognito window, visit the CI system and login as Guest. Close the incognito window.\nNow, go to Users Management. Select view / Guest and select Roles -&gt; guest\nAdmin -&gt; Pipelines. Select Pipeline Group beta, click + on the top right of the whole group, go to Roles, add guest, and only check View. Save this.\n\nAt this point, Guest should have permission to view pipelines, see logs, download artifacts but nothing else.\nFor text auth, go to https://ci.v-sekai.cloud/go/admin/security/auth_configs and select Create new authorization configuration -&gt; file-auth-config / Password File Authentication plugin / /godata/config/password.properties\nsudo kubectl exec gocd-server-6d77846995-5l244 -- touch /godata/config/password.properties\nsudo yum install httpd-tools\nhtpasswd -c -B passwd admin\ncat passwd | sudo kubectl exec gocd-server-6d77846995-5l244 -- sudo tee /kubepvc/pvc/*/godata/config/password.properties\nNow go to users page, edit your user and enable Global Admin.\nNow go to file-auth-config, edit configuration, enable Allow only known users to login\n\n\n\nGo to Admin -&gt; Config Repositories\n\nConfig #repository Name: groups-gocd-pipelines\nPlugin ID: JSON Configuration Plugin\nMaterial Type: Git\nURL: git@gitlab.com:godot-groups/groups-gocd-pipelines\nBranch: master\nGoCD pipeline files pattern: *.gopipeline.json\nGoCD environment files pattern: *.goenvironment.json\n\nRules\n\nAllow: Pipeline Group: beta\nAllow: Environment: development\n\n\n\n\ncurl -L https://github.com/fluxcd/flux2/releases/download/v0.24.1/flux_0.24.1_linux_amd64.tar.gz | tar -zxf - flux\nsudo cp flux /usr/local/bin/flux\nsudo chmod +x /usr/local/bin/flux\nsudo kubectl apply -f https://github.com/fluxcd/flux2/releases/download/v0.24.1/install.yaml\nFork the flux-config #repository from here https://github.com/V-Sekai/flux-config into your own github account, and set GHUSER=your github account.\nNow, in your fork of flux-config, go to project Settings -&gt; Deploy Keys and add the result of the above identity command. Make sure to check Allow write access.\nOnce you have done this, you can continue with the flux setup using your newly forked repository.\nexport GHUSER=\"xxxxxxxxx\"\nsudo flux install\nsudo flux create source git gitrepo --url=https://github.com/$GHUSER/flux-config  --branch=flux2\nsudo flux create kustomization workloads --source=GitRepository/gitrepo --path=\"./workloads/\"\nsudo flux get all\nFOR DEBUGGING ONLY: sudo setenforce permissive - this appears to have no effect, so there is a different problem.\n\n\n\n\n\nstatefulset:\n  resources:\n    limits:\n      memory: \"8Gi\"\n    requests:\n      memory: \"8Gi\"\nconf:\n  cache: \"2Gi\"\n  max-sql-memory: \"2Gi\"\ntls:\n  enabled: true\n\n\n\n\n# Helm version MAY be deprecated. We will switch to operator below.\n\n#sudo helm install cockroachdb --values cockroachdb.values.yaml cockroachdb/cockroachdb\n#sudo kubectl certificate approve default.node.cockroachdb-0\n#sudo kubectl certificate approve default.node.cockroachdb-1\n#sudo kubectl certificate approve default.node.cockroachdb-2\n#sudo kubectl certificate approve default.client.root\n\nwget https://raw.githubusercontent.com/cockroachdb/cockroach-operator/master/manifests/operator.yaml -O cockroach-operator.yaml\nsudo kubectl apply -f cockroach-operator.yaml\n\nwget https://raw.githubusercontent.com/cockroachdb/cockroach-operator/master/config/crd/bases/crdb.cockroachlabs.com_crdbclusters.yaml\nsudo kubectl apply -f crdb.yaml\n\ncat &gt; cockroachdb_extra_resource_certgen.yaml\napiVersion: v1\nkind: ServiceAccount\nmetadata:\n  name: cockroachdb\n  labels:\n    app: cockroachdb\n---\napiVersion: rbac.authorization.k8s.io/v1\nkind: Role\nmetadata:\n  name: cockroachdb\n  labels:\n    app: cockroachdb\nrules:\n- apiGroups:\n  - \"\"\n  resources:\n  - secrets\n  verbs:\n  - create\n  - get\n---\napiVersion: rbac.authorization.k8s.io/v1\nkind: ClusterRole\nmetadata:\n  name: cockroachdb\n  labels:\n    app: cockroachdb\nrules:\n- apiGroups:\n  - certificates.k8s.io\n  resources:\n  - certificatesigningrequests\n  verbs:\n  - create\n  - get\n  - watch\n---\napiVersion: rbac.authorization.k8s.io/v1\nkind: RoleBinding\nmetadata:\n  name: cockroachdb\n  labels:\n    app: cockroachdb\nroleRef:\n  apiGroup: rbac.authorization.k8s.io\n  kind: Role\n  name: cockroachdb\nsubjects:\n- kind: ServiceAccount\n  name: cockroachdb\n  namespace: default\n---\napiVersion: rbac.authorization.k8s.io/v1\nkind: ClusterRoleBinding\nmetadata:\n  name: cockroachdb\n  labels:\n    app: cockroachdb\nroleRef:\n  apiGroup: rbac.authorization.k8s.io\n  kind: ClusterRole\n  name: cockroachdb\nsubjects:\n- kind: ServiceAccount\n  name: cockroachdb\n  namespace: default\n\nCtrl-D\n\n\n# Note: may need to set up physicalVolume and physicalVolumeClaim objects for each cockraoch node.\n\n# The permissions may be set wrong if you are upgrading. Fix them with:\nsudo chown -R 1000581000 /kube/pvc/pvc-aaaaaaaaaaaaaaaaaa /kube/pvc/pvc-bbbbbbbbbbbbbbb /kube/pvc/pvc-cccccccccccccccccccccccccccccccc\n\n# OLD curl -o client-secure.yaml https://raw.githubusercontent.com/cockroachdb/cockroach/master/cloud/kubernetes/client-secure.yaml\n# OLD sudo kubectl apply -f client-secure.yaml\n\nwget https://raw.githubusercontent.com/cockroachdb/cockroach-operator/master/examples/client-secure-operator.yaml\nsudo kubectl apply -f client-secure-operator.yaml\n\nsudo kubectl certificate approve default.client.uro-prod\n\nsudo kubectl exec -it cockroachdb-client-secure -- ./cockroach sql --certs-dir=/cockroach-certs --host=cockroachdb-public\nIn SQL, write:\nCREATE DATABASE uro_prod;\nCREATE USER 'uro-prod' WITH PASSWORD 'blablablablaSOMEDATABASEPASSWORD';\nGRANT ALL ON DATABASE uro_prod to \"uro-prod\";\nTo make backups:\nsudo kubectl exec -it cockroachdb-client-secure -- ./cockroach dump --certs-dir=/cockroach-certs --host=cockroachdb-public uro_prod &gt; uro_prod_backup.txt\nApply secrets:\n(On dev machine) MIX_ENV=prod mix phx.gen.secret\n# Copy the output of above, and copy the database password from above:\nsudo kubectl create secret generic uro-prod --from-literal=secret-key-base='GENERATED_WITH_ABOVE_COMMAND' --from-literal=pass='blablablablaSOMEDATABASEPASSWORD'\n\nsudo kubectl apply -f https://raw.githubusercontent.com/V-Sekai/uro/master/kubernetes.yaml\n\n\n\n\n\n\nk3s set the default client cert for root to expire after a year or so. This leads to a problem where you can’t administer your own cluster because your root account’s cert is expired. So I had to figure out how to fix this.\nFor the most part, the process I came up with matches this more concise post here: https://github.com/k3s-io/k3s/issues/2342#issuecomment-713016341\nFirst approach, how to rotate kube client certificates: Because we need to modify /root/.kube/config, I ran sudo -i to login as a root shell.\n\nmkdir tls and create tls/config.txt with the following lines:\n\n# --------------------- tls/config.txt -----------\n[ req ]\ndistinguished_name                           = req_distinguished_name\nreq_extensions                                   = v3_req\nprompt = no\n[ req_distinguished_name ]\norganizationName       = system:masters\ncommonName             = system:admin\n[ v3_req ]\nbasicConstraints                                 = CA:FALSE\nkeyUsage                                           = critical, digitalSignature, keyEncipherment\nextendedKeyUsage                            = clientAuth\n# -------------------------------------------------\n\ncp /kube/rancher/k3s/server/tls/client-ca.crt tls/client-ca.crt\nopenssl ecparam -name prime256v1 -genkey -noout -out tls/new-key.pem\nopenssl req -new -key tls/new-key.pem -sha256 -nodes -out tls/new-req.csr -config tls/config.txt\nopenssl x509 -req -days 3000 -in tls/new-req.csr -CA tls/client-ca.crt -CAkey /kube/rancher/k3s/server/tls/client-ca.key -set_serial 4294742997922865905 -extensions v3_req -extfile tls/config.txt -out tls/new-client.crt\ncat tls/new-client.crt tls/client-ca.crt | base64 -w0; echo\ncat tls/new-key.pem | base64 -w0; echo\nedit .kube/config and update client-certificate-data: and client-key-data: respectively.\n\nHow to upgrade the rest of the certs.\nfind /var/lib/rancher/k3s/server/tls -name '*.crt' | while read fn; do echo $fn ===========; openssl x509 -text -in $fn | grep Not\\ After | grep '202[012]'; done\nHere is the script I ran:\n#!/bin/bash\nset -\nset -x\n[ -e \"$1.csr\" ] || openssl x509 -x509toreq -in \"$1.crt\" -out \"$1.csr\" -signkey \"$1.key\"\nmv -i \"$1.crt\" \"$1.crt.bak.$(date +%s)\"\nopenssl x509 -req -in \"$1.csr\" -CA \"client-ca.crt\" -CAkey \"client-ca.key\" -CAcreateserial -days 3650 -out \"$1.crt\"\ncat \"client-ca.crt\" &gt;&gt; \"$1.crt\"\nyou can use this process to update the client cert for /root/.kube/config\nNote that etcd/client.crt actually uses its own server-ca.key instead of client-ca within the etcd folder, so you need a slight modification of the script for this one. I don’t know what any of these certs do so I just did all of them\nFinally, client-k3s-controller.crt and client-kube-proxy.crt must be copied from /var/lib/rancher/k3s/server/tls to /var/lib/rancher/k3s/agent\n\n\n\nStart the upgrade process with:\nsudo dnf upgrade --refresh\nsudo dnf install dnf-plugin-system-upgrade\nsudo dnf system-upgrade download --releasever=34\nAnswer y to all prompts confirming list of packages and new GPG keys, if any. Once successful, it displays:\nDownload complete! Use 'dnf system-upgrade reboot' to start the upgrade.\nTo remove cached metadata and transaction use 'dnf system-upgrade clean'\nThe downloaded packages were saved in cache until the next successful transaction.\nYou can remove cached packages by executing 'dnf clean packages'.\nComplete the upgrade with:\nsudo dnf system-upgrade reboot\nThis will bring the system down for about an hour.\n\n\n\nsudo helm repo update\n# If the stable/nginx-ingress chart is still installed, make sure to helm uninstall nginx first.\nsudo helm upgrade --namespace ingress-nginx nginx ingress-nginx/ingress-nginx --set controller.replicaCount=2\nsudo helm upgrade cert-manager jetstack/cert-manager --namespace cert-manager --set installCRDs=true\n### I was not able to get external-dns to upgrade, but it is not user-facing so we keep running the old version.\n# sudo helm upgrade external-dns --reuse-values bitnami/external-dns\n\n\n\ncurl -sfL https://raw.githubusercontent.com/rancher/k3s/master/install.sh | sh -s - server -o /root/.kube/config --default-local-storage-path /kube/pvc --no-deploy=servicelb --disable=traefik --disable=servicelb\n\n\n\nRun the shell:\nsudo kubectl exec -it cockroachdb-client-secure -- ./cockroach sql --certs-dir=/cockroach-certs --host=cockroachdb-public\nAt the top of the shell prompt, it will say something like this. Copy the first two numbers from the CockroachDB CCL line. In this case, 20.2\n#\n# Welcome to the CockroachDB SQL shell.\n# All statements must be terminated by a semicolon.\n# To exit, type: \\q.\n#\n# Server version: CockroachDB CCL v20.2.2 (x86_64-unknown-linux-gnu\nReplace some.version in the following command with the value we found above:\nSET CLUSTER SETTING cluster.preserve_downgrade_option = 'some.version';\nFinally, perform the upgrade:\nsudo kubectl delete job cockroachdb-init\nsudo helm upgrade cockroachdb cockroachdb/cockroachdb --values cockroachdb.values.yaml\ncurl -o client-secure.yaml https://raw.githubusercontent.com/cockroachdb/cockroach/master/cloud/kubernetes/client-secure.yaml\nsudo kubectl delete pods/cockroachdb-client-secure\nsudo kubectl create -f client-secure.yaml"
   },
   {
-    "objectID": "decisions/20230716-enhancing-avatar-creation-process-01-regular.html#references",
-    "href": "decisions/20230716-enhancing-avatar-creation-process-01-regular.html#references",
-    "title": "Proposed: Enhancing Avatar Creation Process in V-Sekai Regular",
+    "objectID": "decisions/20200602-manage-backend-with-k3s.html#positive-consequences",
+    "href": "decisions/20200602-manage-backend-with-k3s.html#positive-consequences",
+    "title": "Accepted: Manage backend resources on one or more physical machines with K3S",
     "section": "",
-    "text": "V-Sekai\nDetail Tweaker\nInstructBLIP: Towards General-purpose Vision-Language Models with Instruction Tuning\nPetals"
+    "text": "Knowledge gains about service creation\nOperation experience"
   },
   {
-    "objectID": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html",
-    "href": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html",
-    "title": "Accepted: Take a list of 3D points that form a vaguely closed boundary in space and triangulate in Godot Engine",
+    "objectID": "decisions/20200602-manage-backend-with-k3s.html#negative-consequences",
+    "href": "decisions/20200602-manage-backend-with-k3s.html#negative-consequences",
+    "title": "Accepted: Manage backend resources on one or more physical machines with K3S",
     "section": "",
-    "text": "Status: accepted \nDeciders: V-Sekai,fire,em-yu\nTags: V-Sekai,\n\n\n\nCASSIE is a method for Curve And Surface Sketching in Immersive Environments.\nA core part of the CASSIE algorithm is to take a list of 3D points that form a vaguely closed boundary in space and triangulate.\n\n\n\nThis CASSIE triangulate operation needs to be done in Godot Engine so it can be use in V-Sekai.\n\n\n\n\nImplement “An Algorithm for Triangulating Multiple 3D Polygons”\nUse Godot’s delaunay tetrahedralize https://github.com/godotengine/godot/blob/96d7bc62af25b85b8b9cc091eeea1e7a784ba624/core/math/delaunay_3d.h#L145 static Vector&lt;OutputSimplex&gt; tetrahedralize(const Vector&lt;Vector3&gt; &p_points)\nEmilie Yu described a method for smoothing meshes.\n\nLibigl should be best for smoothing while pinning the boundaries. I see they have a solver that can take fixed boundary constraints https://libigl.github.io/tutorial/#quadratic-energy-minimization so that could allow you to pin the boundaries. So instead of this line it would be something like\nigl::min_quad_with_fixed_data mqwf;\nigl::min_quad_with_fixed_precompute(S, [flat vector of indices of boundary vertices size=(3 * N_boundary)], [zero matrix], true, mqwf);\nigl::min_quad_with_fixed_solve(mqwf, M * U, [flat vector of boundary vertices positions size=(3 * N_boundary)], [zero vector], Z);\nand the vector Z is a (3 * N) flat vector of the solution vertices (equivalent to the “U” of the other example).\n\n??? Add remeshing.\nExpose a function to Godot Engine called triangulate boundaries.\n\n\n\n\n\nJeana demonstrated the feel of CASSIE on 2021-11-05 to draw a cat.\n\n\n\n\n20211105 CASSIE Jeana\n\n\n\n\n\n\nAdding complexity and maybe time space explosions because of mesh processing.\nMay cause stuttering in VR.\n\n\n\n\n\nOption: Integrate drawing like OpenBrush. https://github.com/icosa-gallery/open-brush\nRejection Reason: The feel is not the same.\n\n\n\n\nNot a trivial gdscript and has performance gaps.\n\n\n\nIt is cool and I know how to approach implementing CASSIE in Godot Engine.\n\n\n\n\nhttps://www.cse.wustl.edu/~taoju/zoum/projects/TriMultPoly\nhttps://em-yu.github.io/\nhttps://ns.inria.fr/d3/CASSIE\nhttps://libigl.github.io/\nhttps://github.com/godotengine/\nhttps://www.blender.org/\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Constant maintenance"
   },
   {
-    "objectID": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html#context-and-problem-statement",
-    "href": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html#context-and-problem-statement",
-    "title": "Accepted: Take a list of 3D points that form a vaguely closed boundary in space and triangulate in Godot Engine",
+    "objectID": "decisions/20200602-manage-backend-with-k3s.html#option-graveyard",
+    "href": "decisions/20200602-manage-backend-with-k3s.html#option-graveyard",
+    "title": "Accepted: Manage backend resources on one or more physical machines with K3S",
     "section": "",
-    "text": "CASSIE is a method for Curve And Surface Sketching in Immersive Environments.\nA core part of the CASSIE algorithm is to take a list of 3D points that form a vaguely closed boundary in space and triangulate."
+    "text": "Option: Dedicated Servers\nOption: Virtual Machines"
   },
   {
-    "objectID": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Accepted: Take a list of 3D points that form a vaguely closed boundary in space and triangulate in Godot Engine",
+    "objectID": "decisions/20200602-manage-backend-with-k3s.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20200602-manage-backend-with-k3s.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Accepted: Manage backend resources on one or more physical machines with K3S",
     "section": "",
-    "text": "This CASSIE triangulate operation needs to be done in Godot Engine so it can be use in V-Sekai."
+    "text": "Yes, it is possible to deploy this system using docker or in the root system."
   },
   {
-    "objectID": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Accepted: Take a list of 3D points that form a vaguely closed boundary in space and triangulate in Godot Engine",
+    "objectID": "decisions/20200602-manage-backend-with-k3s.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20200602-manage-backend-with-k3s.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Accepted: Manage backend resources on one or more physical machines with K3S",
     "section": "",
-    "text": "Implement “An Algorithm for Triangulating Multiple 3D Polygons”\nUse Godot’s delaunay tetrahedralize https://github.com/godotengine/godot/blob/96d7bc62af25b85b8b9cc091eeea1e7a784ba624/core/math/delaunay_3d.h#L145 static Vector&lt;OutputSimplex&gt; tetrahedralize(const Vector&lt;Vector3&gt; &p_points)\nEmilie Yu described a method for smoothing meshes.\n\nLibigl should be best for smoothing while pinning the boundaries. I see they have a solver that can take fixed boundary constraints https://libigl.github.io/tutorial/#quadratic-energy-minimization so that could allow you to pin the boundaries. So instead of this line it would be something like\nigl::min_quad_with_fixed_data mqwf;\nigl::min_quad_with_fixed_precompute(S, [flat vector of indices of boundary vertices size=(3 * N_boundary)], [zero matrix], true, mqwf);\nigl::min_quad_with_fixed_solve(mqwf, M * U, [flat vector of boundary vertices positions size=(3 * N_boundary)], [zero vector], Z);\nand the vector Z is a (3 * N) flat vector of the solution vertices (equivalent to the “U” of the other example).\n\n??? Add remeshing.\nExpose a function to Godot Engine called triangulate boundaries."
+    "text": "Having experience with kubernetes and maintaining discipline will make scaling or service upgrades smoother in the future."
   },
   {
-    "objectID": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html#positive-consequences",
-    "href": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html#positive-consequences",
-    "title": "Accepted: Take a list of 3D points that form a vaguely closed boundary in space and triangulate in Godot Engine",
+    "objectID": "decisions/20200602-manage-backend-with-k3s.html#references",
+    "href": "decisions/20200602-manage-backend-with-k3s.html#references",
+    "title": "Accepted: Manage backend resources on one or more physical machines with K3S",
     "section": "",
-    "text": "Jeana demonstrated the feel of CASSIE on 2021-11-05 to draw a cat.\n\n\n\n\n20211105 CASSIE Jeana"
+    "text": "https://k3s.io/"
   },
   {
-    "objectID": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html#negative-consequences",
-    "href": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html#negative-consequences",
-    "title": "Accepted: Take a list of 3D points that form a vaguely closed boundary in space and triangulate in Godot Engine",
+    "objectID": "decisions/20200602-manage-backend-with-k3s.html#derivative-license",
+    "href": "decisions/20200602-manage-backend-with-k3s.html#derivative-license",
+    "title": "Accepted: Manage backend resources on one or more physical machines with K3S",
     "section": "",
-    "text": "Adding complexity and maybe time space explosions because of mesh processing.\nMay cause stuttering in VR."
+    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html#option-graveyard",
-    "href": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html#option-graveyard",
-    "title": "Accepted: Take a list of 3D points that form a vaguely closed boundary in space and triangulate in Godot Engine",
+    "objectID": "decisions/20230619-membrane-framework-for-mesh-processing.html",
+    "href": "decisions/20230619-membrane-framework-for-mesh-processing.html",
+    "title": "Proposed: Networked Procedural Generation as a Sidecar to the Godot Engine Server",
     "section": "",
-    "text": "Option: Integrate drawing like OpenBrush. https://github.com/icosa-gallery/open-brush\nRejection Reason: The feel is not the same."
+    "text": "Status: proposed\nDeciders: V-Sekai, fire\nTags: V-Sekai, Chatbot GPT4 assistance\n\n\n\n\nEnable creation of more dynamic and engaging environments within V-Sekai.\n\n\n\nV-Sekai, an open-source virtual reality platform, aims to deliver a user-friendly experience for the VR community. To boost its functionality and compatibility with other tools, we propose integrating networked procedural generation as a sidecar to the Godot engine server, allowing for more dynamic and immersive environments in V-Sekai.\nTo further address V-Sekai’s limitations, we suggest incorporating the Membrane Framework along with other relevant technologies such as Godot Engine, OpenMfx Support, Elixir Phoenix, and Elixir Nx. This comprehensive integration will not only enhance V-Sekai’s capabilities but also increase its versatility across various use cases.\nThe implementation involves connecting V-Sekai with the components mentioned in the Membrane Framework diagram below:\nsequenceDiagram\n  participant MembraneFramework\n  participant WebAndGodotEngineAndBlenderClient\n  participant ElixirNx\n  participant AIMLFramework\n  participant Yugabyte\n\n  rect rgb(240, 248, 255)\n    note over MembraneFramework, Yugabyte: Toggle Actions\n    MembraneFramework-&gt;&gt;WebAndGodotEngineAndBlenderClient: TOGGLE_GAME_ENGINE_AND_CLIENTS\n    MembraneFramework-&gt;&gt;ElixirNx: ACCELERATE_MEMBRANE_FRAMEWORK\n    MembraneFramework-&gt;&gt;AIMLFramework: TOGGLE_AIML_FRAMEWORK\n    MembraneFramework-&gt;&gt;Yugabyte: TOGGLE_YUGABYTE\n  end\n\n  box \"Source\" #CCFFCC\n    participant MembraneFramework\n    participant WebAndGodotEngineAndBlenderClient\n  end\n\n  box \"Filter\" #FFFFCC\n    participant ElixirNx\n    participant AIMLFramework\n  end\n\n  box \"Sink & Source of Data\" #FFCCCC\n    participant Yugabyte\n  end\n\n\nWe propose using read replicas for applications needing single-zone writes and multi-region reads. Benefits include:\n\nResilience: Zone-level resilience with primary cluster nodes across multiple zones.\nConsistency: Timeline consistency in replica clusters, better than eventual consistency.\nLatency: Quick reads from primary and replica clusters; write latency depends on client-primary cluster distance.\n\n\n\n\n\n\nImproved functionality and versatility of V-Sekai\nEnhanced compatibility with other tools and platforms\nGreater potential for collaboration and community involvement\n\n\n\n\n\nIncreased complexity in implementation and maintenance\nPotential performance overhead due to integration of multiple components\n\n\n\n\n\nStandalone procedural generation: Implementing procedural generation as a standalone feature without integrating it with the Godot Engine server. This option was discarded because it would not provide the same level of compatibility and versatility as the proposed solution.\nUsing pre-built assets: Relying on pre-built assets for creating environments instead of implementing networked procedural generation. This option was discarded due to the limited flexibility and potential for repetitive content, which could negatively impact user engagement.\nThird-party procedural generation tools: Integrating third-party procedural generation tools instead of developing a custom solution. This option was discarded because it may not offer the same level of control and customization required for V-Sekai’s specific needs.\nStatic environment design: Focusing on static environment design rather than dynamic, procedurally generated content. This option was discarded because it would not provide the desired level of immersion and interactivity for V-Sekai users.\n\n\n\n\nNo, the proposed solution involves integrating multiple technologies and cannot be achieved with a simple script workaround.\n\n\n\nYes, addressing the limitations of V-Sekai is crucial for its success and adoption within the VR community. By integrating the proposed technologies, we can ensure that V-Sekai remains competitive and relevant in the rapidly evolving VR landscape.\n\n\n\n\nV-Sekai"
   },
   {
-    "objectID": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Accepted: Take a list of 3D points that form a vaguely closed boundary in space and triangulate in Godot Engine",
+    "objectID": "decisions/20230619-membrane-framework-for-mesh-processing.html#metadata",
+    "href": "decisions/20230619-membrane-framework-for-mesh-processing.html#metadata",
+    "title": "Proposed: Networked Procedural Generation as a Sidecar to the Godot Engine Server",
     "section": "",
-    "text": "Not a trivial gdscript and has performance gaps."
+    "text": "Status: proposed\nDeciders: V-Sekai, fire\nTags: V-Sekai, Chatbot GPT4 assistance"
   },
   {
-    "objectID": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Accepted: Take a list of 3D points that form a vaguely closed boundary in space and triangulate in Godot Engine",
+    "objectID": "decisions/20230619-membrane-framework-for-mesh-processing.html#context-and-problem-statement",
+    "href": "decisions/20230619-membrane-framework-for-mesh-processing.html#context-and-problem-statement",
+    "title": "Proposed: Networked Procedural Generation as a Sidecar to the Godot Engine Server",
     "section": "",
-    "text": "It is cool and I know how to approach implementing CASSIE in Godot Engine."
+    "text": "Enable creation of more dynamic and engaging environments within V-Sekai."
   },
   {
-    "objectID": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html#references",
-    "href": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html#references",
-    "title": "Accepted: Take a list of 3D points that form a vaguely closed boundary in space and triangulate in Godot Engine",
+    "objectID": "decisions/20230619-membrane-framework-for-mesh-processing.html#proposed-solution",
+    "href": "decisions/20230619-membrane-framework-for-mesh-processing.html#proposed-solution",
+    "title": "Proposed: Networked Procedural Generation as a Sidecar to the Godot Engine Server",
     "section": "",
-    "text": "https://www.cse.wustl.edu/~taoju/zoum/projects/TriMultPoly\nhttps://em-yu.github.io/\nhttps://ns.inria.fr/d3/CASSIE\nhttps://libigl.github.io/\nhttps://github.com/godotengine/\nhttps://www.blender.org/"
+    "text": "V-Sekai, an open-source virtual reality platform, aims to deliver a user-friendly experience for the VR community. To boost its functionality and compatibility with other tools, we propose integrating networked procedural generation as a sidecar to the Godot engine server, allowing for more dynamic and immersive environments in V-Sekai.\nTo further address V-Sekai’s limitations, we suggest incorporating the Membrane Framework along with other relevant technologies such as Godot Engine, OpenMfx Support, Elixir Phoenix, and Elixir Nx. This comprehensive integration will not only enhance V-Sekai’s capabilities but also increase its versatility across various use cases.\nThe implementation involves connecting V-Sekai with the components mentioned in the Membrane Framework diagram below:\nsequenceDiagram\n  participant MembraneFramework\n  participant WebAndGodotEngineAndBlenderClient\n  participant ElixirNx\n  participant AIMLFramework\n  participant Yugabyte\n\n  rect rgb(240, 248, 255)\n    note over MembraneFramework, Yugabyte: Toggle Actions\n    MembraneFramework-&gt;&gt;WebAndGodotEngineAndBlenderClient: TOGGLE_GAME_ENGINE_AND_CLIENTS\n    MembraneFramework-&gt;&gt;ElixirNx: ACCELERATE_MEMBRANE_FRAMEWORK\n    MembraneFramework-&gt;&gt;AIMLFramework: TOGGLE_AIML_FRAMEWORK\n    MembraneFramework-&gt;&gt;Yugabyte: TOGGLE_YUGABYTE\n  end\n\n  box \"Source\" #CCFFCC\n    participant MembraneFramework\n    participant WebAndGodotEngineAndBlenderClient\n  end\n\n  box \"Filter\" #FFFFCC\n    participant ElixirNx\n    participant AIMLFramework\n  end\n\n  box \"Sink & Source of Data\" #FFCCCC\n    participant Yugabyte\n  end\n\n\nWe propose using read replicas for applications needing single-zone writes and multi-region reads. Benefits include:\n\nResilience: Zone-level resilience with primary cluster nodes across multiple zones.\nConsistency: Timeline consistency in replica clusters, better than eventual consistency.\nLatency: Quick reads from primary and replica clusters; write latency depends on client-primary cluster distance."
   },
   {
-    "objectID": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html#derivative-license",
-    "href": "decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html#derivative-license",
-    "title": "Accepted: Take a list of 3D points that form a vaguely closed boundary in space and triangulate in Godot Engine",
+    "objectID": "decisions/20230619-membrane-framework-for-mesh-processing.html#positive-consequences",
+    "href": "decisions/20230619-membrane-framework-for-mesh-processing.html#positive-consequences",
+    "title": "Proposed: Networked Procedural Generation as a Sidecar to the Godot Engine Server",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Improved functionality and versatility of V-Sekai\nEnhanced compatibility with other tools and platforms\nGreater potential for collaboration and community involvement"
   },
   {
-    "objectID": "decisions/20210523-basis-universal-import.html",
-    "href": "decisions/20210523-basis-universal-import.html",
-    "title": "Accepted: Support more flexible texture import via Basis Universal in Godot Engine",
+    "objectID": "decisions/20230619-membrane-framework-for-mesh-processing.html#negative-consequences",
+    "href": "decisions/20230619-membrane-framework-for-mesh-processing.html#negative-consequences",
+    "title": "Proposed: Networked Procedural Generation as a Sidecar to the Godot Engine Server",
     "section": "",
-    "text": "Support more flexible texture import via Basis Universal in Godot Engine. Adding Basis Universal allows more flexibility in the import. –&gt;\n\n\n\n\nBasis Universal\n\n\n\n\nChosen option: Basis Universal\n\n\n\nMore flexibility between mobile and desktop\n\n\n\n\n\nDramatically slower import\nTexture limits?\n\n\n\n\n\n\n\nAdd basis universal to Godot Engine via glTF\n\nGood, because Basis Universal isn’t fully supported in the import pipeline\nGood, because it bridges Web, Desktop and Mobile\nBad, because makes importing slower\n\n\n\n\n\n\nhttps://github.com/KhronosGroup/glTF/blob/master/extensions/2.0/Khronos/KHR_texture_basisu/README.md\n\n\n\n\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Increased complexity in implementation and maintenance\nPotential performance overhead due to integration of multiple components"
   },
   {
-    "objectID": "decisions/20210523-basis-universal-import.html#context-and-problem-statement",
-    "href": "decisions/20210523-basis-universal-import.html#context-and-problem-statement",
-    "title": "Accepted: Support more flexible texture import via Basis Universal in Godot Engine",
+    "objectID": "decisions/20230619-membrane-framework-for-mesh-processing.html#option-graveyard",
+    "href": "decisions/20230619-membrane-framework-for-mesh-processing.html#option-graveyard",
+    "title": "Proposed: Networked Procedural Generation as a Sidecar to the Godot Engine Server",
     "section": "",
-    "text": "Support more flexible texture import via Basis Universal in Godot Engine. Adding Basis Universal allows more flexibility in the import. –&gt;"
+    "text": "Standalone procedural generation: Implementing procedural generation as a standalone feature without integrating it with the Godot Engine server. This option was discarded because it would not provide the same level of compatibility and versatility as the proposed solution.\nUsing pre-built assets: Relying on pre-built assets for creating environments instead of implementing networked procedural generation. This option was discarded due to the limited flexibility and potential for repetitive content, which could negatively impact user engagement.\nThird-party procedural generation tools: Integrating third-party procedural generation tools instead of developing a custom solution. This option was discarded because it may not offer the same level of control and customization required for V-Sekai’s specific needs.\nStatic environment design: Focusing on static environment design rather than dynamic, procedurally generated content. This option was discarded because it would not provide the desired level of immersion and interactivity for V-Sekai users."
   },
   {
-    "objectID": "decisions/20210523-basis-universal-import.html#considered-options",
-    "href": "decisions/20210523-basis-universal-import.html#considered-options",
-    "title": "Accepted: Support more flexible texture import via Basis Universal in Godot Engine",
+    "objectID": "decisions/20230619-membrane-framework-for-mesh-processing.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230619-membrane-framework-for-mesh-processing.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Networked Procedural Generation as a Sidecar to the Godot Engine Server",
     "section": "",
-    "text": "Basis Universal"
+    "text": "No, the proposed solution involves integrating multiple technologies and cannot be achieved with a simple script workaround."
   },
   {
-    "objectID": "decisions/20210523-basis-universal-import.html#decision-outcome",
-    "href": "decisions/20210523-basis-universal-import.html#decision-outcome",
-    "title": "Accepted: Support more flexible texture import via Basis Universal in Godot Engine",
+    "objectID": "decisions/20230619-membrane-framework-for-mesh-processing.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230619-membrane-framework-for-mesh-processing.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Networked Procedural Generation as a Sidecar to the Godot Engine Server",
     "section": "",
-    "text": "Chosen option: Basis Universal\n\n\n\nMore flexibility between mobile and desktop\n\n\n\n\n\nDramatically slower import\nTexture limits?"
+    "text": "Yes, addressing the limitations of V-Sekai is crucial for its success and adoption within the VR community. By integrating the proposed technologies, we can ensure that V-Sekai remains competitive and relevant in the rapidly evolving VR landscape."
   },
   {
-    "objectID": "decisions/20210523-basis-universal-import.html#pros-and-cons-of-the-options",
-    "href": "decisions/20210523-basis-universal-import.html#pros-and-cons-of-the-options",
-    "title": "Accepted: Support more flexible texture import via Basis Universal in Godot Engine",
+    "objectID": "decisions/20230619-membrane-framework-for-mesh-processing.html#references",
+    "href": "decisions/20230619-membrane-framework-for-mesh-processing.html#references",
+    "title": "Proposed: Networked Procedural Generation as a Sidecar to the Godot Engine Server",
     "section": "",
-    "text": "Add basis universal to Godot Engine via glTF\n\nGood, because Basis Universal isn’t fully supported in the import pipeline\nGood, because it bridges Web, Desktop and Mobile\nBad, because makes importing slower"
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20210523-basis-universal-import.html#references",
-    "href": "decisions/20210523-basis-universal-import.html#references",
-    "title": "Accepted: Support more flexible texture import via Basis Universal in Godot Engine",
+    "objectID": "decisions/20210811-godot-transparency.html",
+    "href": "decisions/20210811-godot-transparency.html",
+    "title": "Accepted: OIT in Godot Engine",
     "section": "",
-    "text": "https://github.com/KhronosGroup/glTF/blob/master/extensions/2.0/Khronos/KHR_texture_basisu/README.md"
+    "text": "Accepted: OIT in Godot Engine\n\nContext and Problem Statement\nRender hair well.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nUse “Shortcut” or “PPLL” to render OIT transparency.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\n\nShortcut takes 4 passes but is faster.\n\nTressFX technology uses order independent transparency.\n\n(OIT). There are two variants. One uses a per-pixel linked list (PPLL), and the other uses a multi-pass method referred to as Shortcut.\n\n\nThe main decision to make is whether to use per-pixel linked lists or Shortcut. The Shortcut method can be generally faster, with an easier memory bound, but at the expense of some quality. The TressFX 4.1/Unreal 4.22 Engine integration uses Shortcut (although the shader for PPLL may still be present in the branch, it was/is unmodified/untested/unused). TressFX 4.1/Cauldron uses both Shortcut and PPLL.\n\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nAvatars are a strength of V-Sekai.\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nCode complexity.\n\n\nIs there a reason why this should be core and done by us?\nReduz isn’t interested in OIT.\n\n\nReferences\n\nhttps://raw.githubusercontent.com/GPUOpen-Effects/TressFX/master/doc/TressFX4xDeveloperGuide.pdf\nhttps://github.com/GPUOpen-Effects/TressFX/blob/master/src/Shaders/TressFXPPLL.hlsl\nhttps://github.com/GPUOpen-Effects/TressFX/blob/master/src/Shaders/TressFXShortCut.hlsl\nhttps://blog.icare3d.org/2010/07/opengl-40-abuffer-v20-linked-lists-of.html\nhttps://github.com/SaschaWillems/Vulkan/blob/master/examples/oit/oit.cpp\n\n\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
   },
   {
-    "objectID": "decisions/20210523-basis-universal-import.html#derivative-license",
-    "href": "decisions/20210523-basis-universal-import.html#derivative-license",
-    "title": "Accepted: Support more flexible texture import via Basis Universal in Godot Engine",
+    "objectID": "decisions/20230620-t5-jsonformer-xstate.html",
+    "href": "decisions/20230620-t5-jsonformer-xstate.html",
+    "title": "Proposed: Large language model t5 generating xstate json reliabily for digital beings",
     "section": "",
-    "text": "Copyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nV-Sekai is facing a limitation that requires a solution to convert natural language text into XState JSON format for executing behavior statecharts for digital beings. This can be achieved by using the T5 (Text-to-Text Transfer Transformer) model with JSON-former for XState in Godot Engine 4.0.\n\n\n\nThe proposed solution involves using the T5 model to generate text based on input text and then converting the generated text into XState JSON format, all within the Godot Engine 4.0 environment.\n\n\n\nTo use T5 (Text-to-Text Transfer Transformer) with JSON-former for XState in Godot Engine 4.0, you’ll need to follow these steps:\n\nLoad the necessary libraries\n\nvar transformers = preload(\"res://path/to/transformers.gd\")\nvar torch = preload(\"res://path/to/torch.gd\")\n\nLoad the T5 model and tokenizer\n\nvar model_name = \"t5-small\"\nvar tokenizer = transformers.load_T5Tokenizer(model_name)\nvar model = transformers.load_T5ForConditionalGeneration(model_name)\n\nCreate a function to generate text using T5\n\nfunc generate_text(input_text: String) -&gt; String:\n    var input_ids = tokenizer.encode(input_text)\n    var outputs = model.generate(input_ids)\n    var generated_text = tokenizer.decode(outputs[0])\n    return generated_text\n\nCreate a function to replace placeholders in T5 output\n\nfunc replace_placeholders(text: String) -&gt; String:\n    var formatted_text = text.replace(\"&lt;extra_id_0&gt;\", \"event\").replace(\"&lt;extra_id_1&gt;\", \"state\")\n    return formatted_text\n\nCreate a function to parse JSON from formatted text\n\nfunc parse_JSON(formatted_text: String) -&gt; Dictionary:\n    var json_object = JSON.parse(formatted_text).result\n    return json_object\n\nCreate a function to convert T5 output to XState JSON format\n\nfunc t5_to_jsonformer_xstate(text: String) -&gt; Dictionary:\n    var formatted_text = replace_placeholders(text)\n    var json_object = parse_JSON(formatted_text)\n    return json_object\n\nUse the functions to generate XState JSON\n\nfunc _ready():\n    var input_text = \"your input text here\"\n    var t5_output = generate_text(input_text)\n    var xstate_json = t5_to_jsonformer_xstate(t5_output)\n    print(xstate_json)\nThis will give you the XState JSON format for the given input text. Note that the T5 model might need to be fine-tuned on a dataset specific to your use case to generate accurate XState JSON representations.\n\n\n\n\nAutomates the process of converting natural language text into XState JSON format within the Godot Engine 4.0 environment.\nReduces manual effort and potential errors in creating XState JSON representations.\n\n\n\n\n\nThe T5 model may require fine-tuning on a specific dataset to generate accurate XState JSON representations.\nThere might be limitations in understanding complex or ambiguous input text.\n\n\n\n\nHere are some option graveyard items for the proposal:\n\nUsing rule-based natural language processing (NLP) techniques\n\nPros:\n\nEasier to implement and understand.\nNo need for training data or fine-tuning.\n\nCons:\n\nLimited in handling complex or ambiguous input text.\nRequires manual updates to rules as new use cases emerge.\n\n\nUsing other pre-trained NLP models (e.g., GPT-3, BERT)\n\nPros:\n\nCan leverage existing state-of-the-art NLP models.\nMay provide better performance on certain tasks.\n\nCons:\n\nMay require additional fine-tuning or adaptation for the specific task.\nSome models may have higher computational requirements or costs.\n\n\nCreating a custom NLP model from scratch\n\nPros:\n\nTailored specifically for the task of converting natural language text into XState JSON format.\nPotential for better performance if designed well.\n\nCons:\n\nRequires significant time and effort to develop, train, and maintain.\nMay not perform as well as existing state-of-the-art models.\n\n\nUsing an external API or service for natural language understanding\n\nPros:\n\nOffloads the complexity of NLP to an external service.\nCan potentially leverage more advanced NLP techniques.\n\nCons:\n\nIntroduces dependency on an external service.\nMay incur additional costs or usage limitations.\n\n\n\nThese options were considered but ultimately discarded in favor of using the T5 model with JSON-former for XState in Godot Engine 4.0 due to its balance of performance, ease of implementation, and adaptability to the specific task.\n\n\n\nThe proposed solution requires more than a few lines of script and involves using a pre-trained model (T5) to generate the desired output within the Godot Engine 4.0 environment.\n\n\n\nImplementing this solution as part of the core functionality can help V-Sekai users automate the process of generating XState JSON representations from natural language text within the Godot Engine 4.0 environment, improving efficiency and reducing manual effort.\n\n\n\n\nV-Sekai\nGodot Engine\nGDScript documentation\nT5 (Text-to-Text Transfer Transformer)\nTransformers library\nXState documentation"
   },
   {
-    "objectID": "decisions/20240425-recharge-cycle.html",
-    "href": "decisions/20240425-recharge-cycle.html",
-    "title": "Proposed: Stuck / Recharge Cycle",
+    "objectID": "decisions/20230620-t5-jsonformer-xstate.html#metadata",
+    "href": "decisions/20230620-t5-jsonformer-xstate.html#metadata",
+    "title": "Proposed: Large language model t5 generating xstate json reliabily for digital beings",
     "section": "",
-    "text": "In the realm of software development, it’s common for developers to hit a wall or get “stuck” on a particular problem. This can lead to frustration and decreased productivity.\n\n\n\nDevelopers often find themselves stuck on a problem, unable to make progress. This can be due to a variety of reasons such as lack of understanding, complexity of the problem, or simply mental fatigue.\n\n\n\nThe proposed solution is a “Stuck/Recharge” cycle. When a developer finds themselves stuck on a problem, they switch to working on someone else’s problem. This change in perspective can help recharge their mental energy and when they return to their original problem, they may find that they are able to approach it with a fresh mindset.\nif (developer.isStuck()) {\n    developer.switchTask();\n    developer.recharge();\n    developer.returnToOriginalTask();\n}\n\n\n\nThis approach can help prevent burnout and increase overall productivity. It also promotes collaboration and knowledge sharing among the team.\n\n\n\nThere could be potential downsides such as context switching overhead and disruption of flow. However, these can be mitigated with proper task management and communication within the team.\n\n\n\nAn alternative approach could be to have dedicated “unsticking” sessions where developers come together to brainstorm solutions for stuck problems. However, this requires coordination and may not be as flexible as the proposed solution.\n\n\n\nThis proposal may not be beneficial for simple tasks or for developers who rarely get stuck.\n\n\n\nThis proposal is applicable to our core development process and can be implemented by us.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "Status: proposed\nDeciders: V-Sekai\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20240425-recharge-cycle.html#the-context",
-    "href": "decisions/20240425-recharge-cycle.html#the-context",
-    "title": "Proposed: Stuck / Recharge Cycle",
+    "objectID": "decisions/20230620-t5-jsonformer-xstate.html#context-and-problem-statement",
+    "href": "decisions/20230620-t5-jsonformer-xstate.html#context-and-problem-statement",
+    "title": "Proposed: Large language model t5 generating xstate json reliabily for digital beings",
     "section": "",
-    "text": "In the realm of software development, it’s common for developers to hit a wall or get “stuck” on a particular problem. This can lead to frustration and decreased productivity."
+    "text": "V-Sekai is facing a limitation that requires a solution to convert natural language text into XState JSON format for executing behavior statecharts for digital beings. This can be achieved by using the T5 (Text-to-Text Transfer Transformer) model with JSON-former for XState in Godot Engine 4.0."
   },
   {
-    "objectID": "decisions/20240425-recharge-cycle.html#the-problem-statement",
-    "href": "decisions/20240425-recharge-cycle.html#the-problem-statement",
-    "title": "Proposed: Stuck / Recharge Cycle",
+    "objectID": "decisions/20230620-t5-jsonformer-xstate.html#proposed-solution",
+    "href": "decisions/20230620-t5-jsonformer-xstate.html#proposed-solution",
+    "title": "Proposed: Large language model t5 generating xstate json reliabily for digital beings",
     "section": "",
-    "text": "Developers often find themselves stuck on a problem, unable to make progress. This can be due to a variety of reasons such as lack of understanding, complexity of the problem, or simply mental fatigue."
+    "text": "The proposed solution involves using the T5 model to generate text based on input text and then converting the generated text into XState JSON format, all within the Godot Engine 4.0 environment."
   },
   {
-    "objectID": "decisions/20240425-recharge-cycle.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20240425-recharge-cycle.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Stuck / Recharge Cycle",
+    "objectID": "decisions/20230620-t5-jsonformer-xstate.html#implementation",
+    "href": "decisions/20230620-t5-jsonformer-xstate.html#implementation",
+    "title": "Proposed: Large language model t5 generating xstate json reliabily for digital beings",
     "section": "",
-    "text": "The proposed solution is a “Stuck/Recharge” cycle. When a developer finds themselves stuck on a problem, they switch to working on someone else’s problem. This change in perspective can help recharge their mental energy and when they return to their original problem, they may find that they are able to approach it with a fresh mindset.\nif (developer.isStuck()) {\n    developer.switchTask();\n    developer.recharge();\n    developer.returnToOriginalTask();\n}"
+    "text": "To use T5 (Text-to-Text Transfer Transformer) with JSON-former for XState in Godot Engine 4.0, you’ll need to follow these steps:\n\nLoad the necessary libraries\n\nvar transformers = preload(\"res://path/to/transformers.gd\")\nvar torch = preload(\"res://path/to/torch.gd\")\n\nLoad the T5 model and tokenizer\n\nvar model_name = \"t5-small\"\nvar tokenizer = transformers.load_T5Tokenizer(model_name)\nvar model = transformers.load_T5ForConditionalGeneration(model_name)\n\nCreate a function to generate text using T5\n\nfunc generate_text(input_text: String) -&gt; String:\n    var input_ids = tokenizer.encode(input_text)\n    var outputs = model.generate(input_ids)\n    var generated_text = tokenizer.decode(outputs[0])\n    return generated_text\n\nCreate a function to replace placeholders in T5 output\n\nfunc replace_placeholders(text: String) -&gt; String:\n    var formatted_text = text.replace(\"&lt;extra_id_0&gt;\", \"event\").replace(\"&lt;extra_id_1&gt;\", \"state\")\n    return formatted_text\n\nCreate a function to parse JSON from formatted text\n\nfunc parse_JSON(formatted_text: String) -&gt; Dictionary:\n    var json_object = JSON.parse(formatted_text).result\n    return json_object\n\nCreate a function to convert T5 output to XState JSON format\n\nfunc t5_to_jsonformer_xstate(text: String) -&gt; Dictionary:\n    var formatted_text = replace_placeholders(text)\n    var json_object = parse_JSON(formatted_text)\n    return json_object\n\nUse the functions to generate XState JSON\n\nfunc _ready():\n    var input_text = \"your input text here\"\n    var t5_output = generate_text(input_text)\n    var xstate_json = t5_to_jsonformer_xstate(t5_output)\n    print(xstate_json)\nThis will give you the XState JSON format for the given input text. Note that the T5 model might need to be fine-tuned on a dataset specific to your use case to generate accurate XState JSON representations."
   },
   {
-    "objectID": "decisions/20240425-recharge-cycle.html#the-benefits",
-    "href": "decisions/20240425-recharge-cycle.html#the-benefits",
-    "title": "Proposed: Stuck / Recharge Cycle",
+    "objectID": "decisions/20230620-t5-jsonformer-xstate.html#positive-consequences",
+    "href": "decisions/20230620-t5-jsonformer-xstate.html#positive-consequences",
+    "title": "Proposed: Large language model t5 generating xstate json reliabily for digital beings",
     "section": "",
-    "text": "This approach can help prevent burnout and increase overall productivity. It also promotes collaboration and knowledge sharing among the team."
+    "text": "Automates the process of converting natural language text into XState JSON format within the Godot Engine 4.0 environment.\nReduces manual effort and potential errors in creating XState JSON representations."
   },
   {
-    "objectID": "decisions/20240425-recharge-cycle.html#the-downsides",
-    "href": "decisions/20240425-recharge-cycle.html#the-downsides",
-    "title": "Proposed: Stuck / Recharge Cycle",
+    "objectID": "decisions/20230620-t5-jsonformer-xstate.html#negative-consequences",
+    "href": "decisions/20230620-t5-jsonformer-xstate.html#negative-consequences",
+    "title": "Proposed: Large language model t5 generating xstate json reliabily for digital beings",
     "section": "",
-    "text": "There could be potential downsides such as context switching overhead and disruption of flow. However, these can be mitigated with proper task management and communication within the team."
+    "text": "The T5 model may require fine-tuning on a specific dataset to generate accurate XState JSON representations.\nThere might be limitations in understanding complex or ambiguous input text."
   },
   {
-    "objectID": "decisions/20240425-recharge-cycle.html#the-road-not-taken",
-    "href": "decisions/20240425-recharge-cycle.html#the-road-not-taken",
-    "title": "Proposed: Stuck / Recharge Cycle",
+    "objectID": "decisions/20230620-t5-jsonformer-xstate.html#option-graveyard",
+    "href": "decisions/20230620-t5-jsonformer-xstate.html#option-graveyard",
+    "title": "Proposed: Large language model t5 generating xstate json reliabily for digital beings",
     "section": "",
-    "text": "An alternative approach could be to have dedicated “unsticking” sessions where developers come together to brainstorm solutions for stuck problems. However, this requires coordination and may not be as flexible as the proposed solution."
+    "text": "Here are some option graveyard items for the proposal:\n\nUsing rule-based natural language processing (NLP) techniques\n\nPros:\n\nEasier to implement and understand.\nNo need for training data or fine-tuning.\n\nCons:\n\nLimited in handling complex or ambiguous input text.\nRequires manual updates to rules as new use cases emerge.\n\n\nUsing other pre-trained NLP models (e.g., GPT-3, BERT)\n\nPros:\n\nCan leverage existing state-of-the-art NLP models.\nMay provide better performance on certain tasks.\n\nCons:\n\nMay require additional fine-tuning or adaptation for the specific task.\nSome models may have higher computational requirements or costs.\n\n\nCreating a custom NLP model from scratch\n\nPros:\n\nTailored specifically for the task of converting natural language text into XState JSON format.\nPotential for better performance if designed well.\n\nCons:\n\nRequires significant time and effort to develop, train, and maintain.\nMay not perform as well as existing state-of-the-art models.\n\n\nUsing an external API or service for natural language understanding\n\nPros:\n\nOffloads the complexity of NLP to an external service.\nCan potentially leverage more advanced NLP techniques.\n\nCons:\n\nIntroduces dependency on an external service.\nMay incur additional costs or usage limitations.\n\n\n\nThese options were considered but ultimately discarded in favor of using the T5 model with JSON-former for XState in Godot Engine 4.0 due to its balance of performance, ease of implementation, and adaptability to the specific task."
   },
   {
-    "objectID": "decisions/20240425-recharge-cycle.html#the-infrequent-use-case",
-    "href": "decisions/20240425-recharge-cycle.html#the-infrequent-use-case",
-    "title": "Proposed: Stuck / Recharge Cycle",
+    "objectID": "decisions/20230620-t5-jsonformer-xstate.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "href": "decisions/20230620-t5-jsonformer-xstate.html#if-this-enhancement-will-be-used-infrequently-can-it-be-worked-around-with-a-few-lines-of-script",
+    "title": "Proposed: Large language model t5 generating xstate json reliabily for digital beings",
     "section": "",
-    "text": "This proposal may not be beneficial for simple tasks or for developers who rarely get stuck."
+    "text": "The proposed solution requires more than a few lines of script and involves using a pre-trained model (T5) to generate the desired output within the Godot Engine 4.0 environment."
   },
   {
-    "objectID": "decisions/20240425-recharge-cycle.html#in-core-and-done-by-us",
-    "href": "decisions/20240425-recharge-cycle.html#in-core-and-done-by-us",
-    "title": "Proposed: Stuck / Recharge Cycle",
+    "objectID": "decisions/20230620-t5-jsonformer-xstate.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "href": "decisions/20230620-t5-jsonformer-xstate.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
+    "title": "Proposed: Large language model t5 generating xstate json reliabily for digital beings",
     "section": "",
-    "text": "This proposal is applicable to our core development process and can be implemented by us."
+    "text": "Implementing this solution as part of the core functionality can help V-Sekai users automate the process of generating XState JSON representations from natural language text within the Godot Engine 4.0 environment, improving efficiency and reducing manual effort."
   },
   {
-    "objectID": "decisions/20240425-recharge-cycle.html#status",
-    "href": "decisions/20240425-recharge-cycle.html#status",
-    "title": "Proposed: Stuck / Recharge Cycle",
+    "objectID": "decisions/20230620-t5-jsonformer-xstate.html#references",
+    "href": "decisions/20230620-t5-jsonformer-xstate.html#references",
+    "title": "Proposed: Large language model t5 generating xstate json reliabily for digital beings",
     "section": "",
-    "text": "Status: Proposed"
+    "text": "V-Sekai\nGodot Engine\nGDScript documentation\nT5 (Text-to-Text Transfer Transformer)\nTransformers library\nXState documentation"
   },
   {
-    "objectID": "decisions/20240425-recharge-cycle.html#decision-makers",
-    "href": "decisions/20240425-recharge-cycle.html#decision-makers",
-    "title": "Proposed: Stuck / Recharge Cycle",
+    "objectID": "decisions/20240710-use-webrtc-to-native-interop.html",
+    "href": "decisions/20240710-use-webrtc-to-native-interop.html",
+    "title": "Proposed: Use WebRTC to Native to Interop with Godot Engine",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "In the realm of game development, particularly with the Godot Engine, enabling seamless communication between native clients and web clients is crucial. This proposal aims to address this need by leveraging WebRTC for interoperability.\n\n\n\nWe cannot connect between native clients and web clients for our Godot Engine game. This limitation hinders the user experience and restricts the game’s accessibility across different platforms.\n\n\n\nImplement WebRTC in both native and web clients to facilitate real-time communication.\nSet up a signaling server to manage the initial connection setup between clients.\nUtilize WebRTC data channels for efficient data transfer between clients.\nIntegrate WebRTC functionalities within the Godot Engine to ensure smooth operation.\n\n\n\n\nImproved Connectivity: Enables seamless communication between native and web clients.\nEnhanced User Experience: Provides a consistent gaming experience across different platforms.\nScalability: Facilitates the addition of new features that require real-time communication.\n\n\n\n\n\nComplexity: Implementing WebRTC can be complex and may require significant development effort.\nPerformance Overhead: Real-time communication may introduce performance overhead, especially on lower-end devices.\n\n\n\n\nAlternative approaches such as using traditional client-server models or other communication protocols were considered but ultimately deemed less efficient or effective for real-time communication needs.\n\n\n\nIn scenarios where highly specialized or technical language is required, additional human oversight may be necessary to ensure accuracy and appropriateness.\n\n\n\nThis proposal aligns with our core values of efficiency and professionalism and will be implemented by our team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240425-recharge-cycle.html#tags",
-    "href": "decisions/20240425-recharge-cycle.html#tags",
-    "title": "Proposed: Stuck / Recharge Cycle",
+    "objectID": "decisions/20240710-use-webrtc-to-native-interop.html#the-context",
+    "href": "decisions/20240710-use-webrtc-to-native-interop.html#the-context",
+    "title": "Proposed: Use WebRTC to Native to Interop with Godot Engine",
     "section": "",
-    "text": "V-Sekai"
+    "text": "In the realm of game development, particularly with the Godot Engine, enabling seamless communication between native clients and web clients is crucial. This proposal aims to address this need by leveraging WebRTC for interoperability."
   },
   {
-    "objectID": "decisions/20240425-recharge-cycle.html#further-reading",
-    "href": "decisions/20240425-recharge-cycle.html#further-reading",
-    "title": "Proposed: Stuck / Recharge Cycle",
+    "objectID": "decisions/20240710-use-webrtc-to-native-interop.html#the-problem-statement",
+    "href": "decisions/20240710-use-webrtc-to-native-interop.html#the-problem-statement",
+    "title": "Proposed: Use WebRTC to Native to Interop with Godot Engine",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
+    "text": "We cannot connect between native clients and web clients for our Godot Engine game. This limitation hinders the user experience and restricts the game’s accessibility across different platforms."
   },
   {
-    "objectID": "decisions/20230123-publish-godot-vrm-4.html",
-    "href": "decisions/20230123-publish-godot-vrm-4.html",
-    "title": "Proposed: Publish Godot VRM for Godot 4 for production use",
+    "objectID": "decisions/20240710-use-webrtc-to-native-interop.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240710-use-webrtc-to-native-interop.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Use WebRTC to Native to Interop with Godot Engine",
     "section": "",
-    "text": "Status: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nI want to be able to download the godot vrm addon from the asset library in 4.\n\n\n\nBy publishing we will have reviewed the bugs and decide it is ready to be use.\n\n\n\nSubmit godot vrm to the godot 4 asset library lyuma\nStarted because of discussion with https://twitter.com/AlfredBaudisch/status/1586999148171198465?s=20&t=nUHLXskgrxnTbPFN9WzZxQ about mtoon outlines\n\n\n\nWe’ll prepare for release.\n\n\n\nOld bugs might not be fixed.\n\n\n\n\nOption: The status quo. \nRejection Reason: This solves nothing. \n\n\n\n\nGodot VRM is a few gdscripts.\n\n\n\nGodot VRM is a core feature.\n\n\n\n\nV-Sekai\n\n\n\n\nMIT License\n\nCopyright (c) 2018-present SaracenOne\nCopyright (c) 2019-present K. S. Ernest (iFire) Lee (fire)\nCopyright (c) 2020-present Lyuma\nCopyright (c) 2020-present MMMaellon\nCopyright (c) 2022-present V-Sekai Contributors\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
+    "text": "Implement WebRTC in both native and web clients to facilitate real-time communication.\nSet up a signaling server to manage the initial connection setup between clients.\nUtilize WebRTC data channels for efficient data transfer between clients.\nIntegrate WebRTC functionalities within the Godot Engine to ensure smooth operation."
   },
   {
-    "objectID": "decisions/20230123-publish-godot-vrm-4.html#context-and-problem-statement",
-    "href": "decisions/20230123-publish-godot-vrm-4.html#context-and-problem-statement",
-    "title": "Proposed: Publish Godot VRM for Godot 4 for production use",
+    "objectID": "decisions/20240710-use-webrtc-to-native-interop.html#the-benefits",
+    "href": "decisions/20240710-use-webrtc-to-native-interop.html#the-benefits",
+    "title": "Proposed: Use WebRTC to Native to Interop with Godot Engine",
     "section": "",
-    "text": "I want to be able to download the godot vrm addon from the asset library in 4."
+    "text": "Improved Connectivity: Enables seamless communication between native and web clients.\nEnhanced User Experience: Provides a consistent gaming experience across different platforms.\nScalability: Facilitates the addition of new features that require real-time communication."
   },
   {
-    "objectID": "decisions/20230123-publish-godot-vrm-4.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20230123-publish-godot-vrm-4.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Proposed: Publish Godot VRM for Godot 4 for production use",
+    "objectID": "decisions/20240710-use-webrtc-to-native-interop.html#the-downsides",
+    "href": "decisions/20240710-use-webrtc-to-native-interop.html#the-downsides",
+    "title": "Proposed: Use WebRTC to Native to Interop with Godot Engine",
     "section": "",
-    "text": "By publishing we will have reviewed the bugs and decide it is ready to be use."
+    "text": "Complexity: Implementing WebRTC can be complex and may require significant development effort.\nPerformance Overhead: Real-time communication may introduce performance overhead, especially on lower-end devices."
   },
   {
-    "objectID": "decisions/20230123-publish-godot-vrm-4.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20230123-publish-godot-vrm-4.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Proposed: Publish Godot VRM for Godot 4 for production use",
+    "objectID": "decisions/20240710-use-webrtc-to-native-interop.html#the-road-not-taken",
+    "href": "decisions/20240710-use-webrtc-to-native-interop.html#the-road-not-taken",
+    "title": "Proposed: Use WebRTC to Native to Interop with Godot Engine",
     "section": "",
-    "text": "Submit godot vrm to the godot 4 asset library lyuma\nStarted because of discussion with https://twitter.com/AlfredBaudisch/status/1586999148171198465?s=20&t=nUHLXskgrxnTbPFN9WzZxQ about mtoon outlines"
+    "text": "Alternative approaches such as using traditional client-server models or other communication protocols were considered but ultimately deemed less efficient or effective for real-time communication needs."
   },
   {
-    "objectID": "decisions/20230123-publish-godot-vrm-4.html#positive-consequences",
-    "href": "decisions/20230123-publish-godot-vrm-4.html#positive-consequences",
-    "title": "Proposed: Publish Godot VRM for Godot 4 for production use",
+    "objectID": "decisions/20240710-use-webrtc-to-native-interop.html#the-infrequent-use-case",
+    "href": "decisions/20240710-use-webrtc-to-native-interop.html#the-infrequent-use-case",
+    "title": "Proposed: Use WebRTC to Native to Interop with Godot Engine",
     "section": "",
-    "text": "We’ll prepare for release."
+    "text": "In scenarios where highly specialized or technical language is required, additional human oversight may be necessary to ensure accuracy and appropriateness."
   },
   {
-    "objectID": "decisions/20230123-publish-godot-vrm-4.html#negative-consequences",
-    "href": "decisions/20230123-publish-godot-vrm-4.html#negative-consequences",
-    "title": "Proposed: Publish Godot VRM for Godot 4 for production use",
+    "objectID": "decisions/20240710-use-webrtc-to-native-interop.html#in-core-and-done-by-us",
+    "href": "decisions/20240710-use-webrtc-to-native-interop.html#in-core-and-done-by-us",
+    "title": "Proposed: Use WebRTC to Native to Interop with Godot Engine",
     "section": "",
-    "text": "Old bugs might not be fixed."
+    "text": "This proposal aligns with our core values of efficiency and professionalism and will be implemented by our team."
   },
   {
-    "objectID": "decisions/20230123-publish-godot-vrm-4.html#option-graveyard",
-    "href": "decisions/20230123-publish-godot-vrm-4.html#option-graveyard",
-    "title": "Proposed: Publish Godot VRM for Godot 4 for production use",
+    "objectID": "decisions/20240710-use-webrtc-to-native-interop.html#status",
+    "href": "decisions/20240710-use-webrtc-to-native-interop.html#status",
+    "title": "Proposed: Use WebRTC to Native to Interop with Godot Engine",
     "section": "",
-    "text": "Option: The status quo. \nRejection Reason: This solves nothing."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20230123-publish-godot-vrm-4.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20230123-publish-godot-vrm-4.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Proposed: Publish Godot VRM for Godot 4 for production use",
+    "objectID": "decisions/20240710-use-webrtc-to-native-interop.html#decision-makers",
+    "href": "decisions/20240710-use-webrtc-to-native-interop.html#decision-makers",
+    "title": "Proposed: Use WebRTC to Native to Interop with Godot Engine",
     "section": "",
-    "text": "Godot VRM is a few gdscripts."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20230123-publish-godot-vrm-4.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20230123-publish-godot-vrm-4.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Proposed: Publish Godot VRM for Godot 4 for production use",
+    "objectID": "decisions/20240710-use-webrtc-to-native-interop.html#tags",
+    "href": "decisions/20240710-use-webrtc-to-native-interop.html#tags",
+    "title": "Proposed: Use WebRTC to Native to Interop with Godot Engine",
     "section": "",
-    "text": "Godot VRM is a core feature."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20230123-publish-godot-vrm-4.html#references",
-    "href": "decisions/20230123-publish-godot-vrm-4.html#references",
-    "title": "Proposed: Publish Godot VRM for Godot 4 for production use",
+    "objectID": "decisions/20240710-use-webrtc-to-native-interop.html#further-reading",
+    "href": "decisions/20240710-use-webrtc-to-native-interop.html#further-reading",
+    "title": "Proposed: Use WebRTC to Native to Interop with Godot Engine",
     "section": "",
-    "text": "V-Sekai"
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20230123-publish-godot-vrm-4.html#license-of-the-contribution",
-    "href": "decisions/20230123-publish-godot-vrm-4.html#license-of-the-contribution",
-    "title": "Proposed: Publish Godot VRM for Godot 4 for production use",
+    "objectID": "decisions/20240710-art-direction-in-vsekai.html",
+    "href": "decisions/20240710-art-direction-in-vsekai.html",
+    "title": "Proposed: Art Direction in V-Sekai Process",
     "section": "",
-    "text": "MIT License\n\nCopyright (c) 2018-present SaracenOne\nCopyright (c) 2019-present K. S. Ernest (iFire) Lee (fire)\nCopyright (c) 2020-present Lyuma\nCopyright (c) 2020-present MMMaellon\nCopyright (c) 2022-present V-Sekai Contributors\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."
+    "text": "We visited a VRChat world for “Zenless Zone Zero” and discussed how cool the urban maze was created. Lyuma mentioned that he prefers wild open places. We also noted how Mihoyo has three distinct settings:\n\nMedieval (Genshin Impact)\nUrban Asia (Zenless Zone Zero)\nInterstellar (Star Rail)\n\n\n\n\nWe need an art direction in V-Sekai for our work. Without a defined art direction, we risk inconsistency and lack of cohesion in our visual presentation.\n\n\n\n\nConcept Art Creation: Develop initial concept art to explore different themes and styles.\nCommunity Feedback: Share concept art with the community for feedback and suggestions.\nStyle Guide Development: Create a comprehensive style guide based on the chosen art direction.\nImplementation: Apply the style guide across all assets and environments within V-Sekai.\n\n\n\n\n\nVisual Cohesion: A unified art direction ensures a consistent and professional appearance.\nEnhanced User Experience: A well-defined aesthetic can make the virtual environment more immersive and enjoyable.\nBrand Identity: Establishing a unique visual style helps in building a recognizable brand.\n\n\n\n\n\nLimited Creativity: Strict adherence to a specific art direction may limit creative expression.\nInitial Setup Time: Developing and implementing an art direction requires an initial investment of time and resources.\n\n\n\n\nAlternative approaches such as allowing individual artists complete freedom or using multiple art styles were considered but ultimately deemed less effective for maintaining visual consistency.\n\n\n\nIn scenarios where highly specialized or technical visual elements are required, additional oversight may be necessary to ensure they align with the overall art direction.\n\n\n\nThis proposal aligns with our core values of efficiency and professionalism and will be implemented by our team.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20211031-gltf-importer-should-bind-animation-players-to-the-closest-root-node.html",
-    "href": "decisions/20211031-gltf-importer-should-bind-animation-players-to-the-closest-root-node.html",
-    "title": "Proposed: glTF - importer should bind animation players to the closest root node",
+    "objectID": "decisions/20240710-art-direction-in-vsekai.html#the-context",
+    "href": "decisions/20240710-art-direction-in-vsekai.html#the-context",
+    "title": "Proposed: Art Direction in V-Sekai Process",
     "section": "",
-    "text": "Proposed: glTF - importer should bind animation players to the closest root node\n\nContext and Problem Statement\nGodot currently creates one massive animation per scene. It is hard to organize.\n\n\nDescribe the feature / enhancement and how it helps to overcome the problem or limitation\nSplit the monolithic animation player.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams\nMove the animations on to different subbranches.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nCan be an addon\n\n\nPositive Consequences\nNo response\n\n\nNegative Consequences\nNo response\n\n\nIs there a reason why this should be core and done by us?\nDoesn’t need to be done.\n\n\nReferences\nNo response\n\n\nDerivative License\nCopyright (c) 2020-2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "We visited a VRChat world for “Zenless Zone Zero” and discussed how cool the urban maze was created. Lyuma mentioned that he prefers wild open places. We also noted how Mihoyo has three distinct settings:\n\nMedieval (Genshin Impact)\nUrban Asia (Zenless Zone Zero)\nInterstellar (Star Rail)"
   },
   {
-    "objectID": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html",
-    "href": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html",
-    "title": "Accepted: Use the Humanoid Profile for Character Motion Mirroring",
+    "objectID": "decisions/20240710-art-direction-in-vsekai.html#the-problem-statement",
+    "href": "decisions/20240710-art-direction-in-vsekai.html#the-problem-statement",
+    "title": "Proposed: Art Direction in V-Sekai Process",
     "section": "",
-    "text": "Daniel Snd was looking for a simple way to mirror right-sided walking keyframes on a character avatar motion.\n\n\n\nDaniel Snd did not utilize the Godot Engine humanoid profile.\n\n\n\nThe solution is to use the Godot Engine humanoid profile.\n\n\nIn Godot Engine, the animation humanoid profile is essential for managing bone rolls in incoming humanoid skeletons. This is because these skeletons often have arbitrary bone rolls that need to be standardized for consistent animation behavior.\n\n\nBone roll refers to the rotation around the bone’s longitudinal axis. In 3D modeling and animation, it’s important to correctly set up bone rolls as they determine the axes of rotation for the bones during animation.\n\n\n\nThe SkeletonProfileHumanoid in Godot 4.0 adopts a practical rule for managing bone rolls:\n\nThe +Y axis should point from the parent joint to the child joint. This is considered as the roll axis.\nThe +X rotation should bend the joints towards the body’s inside (almost the direction of muscle contraction).\n\n\n\n\nIf you mirror animations, the bone rolls and names may need to be corrected. This is because the orientation of the bones can get flipped during the mirroring process. The Godot Humanoid Profile applies a Bone Rule to the bone rolls.\n\n\n\nThe Godot Humanoid Profile standardizes the bone names consistently, it allows one to reuse animations across different characters. For example, if one has a walking animation for one character and one wants to apply it to another character, having the same bone names will allow one to do this without any additional work.\n\n\n\nIn 3D animation, the T-Pose is a standard pose where the character stands upright with their arms extended straight out to the sides. This pose is often used as the default pose for rigging and animating characters because it provides a clear view of all parts of the character. However, not all models are initially in a T-Pose. If you have a model in any other pose (let’s say it’s an A-Pose), you might need to convert it to a T-Pose before you can use it effectively in Godot.\n\n\n\n\nThe engine can ensure that all humanoid animations behave consistently, regardless of the original orientation or roll of the bones in the imported skeleton by following the Bone Rule. This makes it easier to create and manage humanoid animations, especially when working with different humanoids that may have been rigged differently.\n\n\n\n\nUsing the Godot Humanoid Profile will allow for consistent behavior across all humanoid animations, making it easier to create and manage these animations. It also allows for reusability of animations across different characters, saving time and effort in animation creation.\n\n\n\nThere may be a learning curve associated with understanding and implementing the Godot Humanoid Profile. Additionally, this solution assumes that all incoming humanoid skeletons will be compatible with the Godot Humanoid Profile, which may not always be the case.\n\n\n\nAn alternative could have been to manually adjust the bone rolls and names for each individual animation. However, this would be a time-consuming process and would not guarantee consistent results across different animations.\n\n\n\nThis proposal may not be beneficial for non-humanoid animations or for projects that do not require motion mirroring.\n\n\n\nThis proposal involves using an existing feature of the Godot Engine the V-Sekai team implemented in Godot Engine 4.0, so no additional development work would be required from our team.\n\n\n\nStatus: Accepted\n\n\n\n\nV-Sekai development team\n\n\n\n\n\nGodot Engine\nHumanoid Profile\nAnimation Mirroring\nBone Rolls\nCharacter Avatar Motion\n3D Modeling\nT-Pose Conversion\nAnimation Reusability\nV-Sekai\nVR Animation\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nFire\n\nAI assistant Aria assisted with this article.\n\n\n\n## SPDX-License-Identifier: CC0-1.0\n##\n## Author: Daniel Snd\n\n@export var left_name:String = \"Left\"\n@export var right_name:String = \"Right\"\n\nfunc do_mirror():\n    var parenteless_ids :PackedInt32Array = get_parentless_bones()\n    for p in get_parentless_bones():\n        attempt_mirror_recursive(p)\n\nfunc attempt_mirror_recursive(bone_id:int):\n    for i in get_bone_children(bone_id):\n        var bone_name = get_bone_name(i)\n        if bone_name.contains(right_name):\n            mirror_pose(bone_name)\n        elif bone_name.contains(left_name):\n            pass\n        else:\n            mirror_single_bone(i)\n        attempt_mirror_recursive(i)\n\nfunc mirror_single_bone(bone_idx):\n    var mirrored_rot = get_bone_pose(bone_idx).basis.get_rotation_quaternion()\n    mirrored_rot.x *= -1\n    mirrored_rot.w *= -1\n    set_bone_pose_rotation(bone_idx, mirrored_rot)\n\n# Function to mirror pose\nfunc mirror_pose(bone_name):\n    var bone_idx = find_bone(bone_name)\n    if bone_idx == -1:\n        print(\"Bone does not exist in Skeleton\")\n        return\n\n    var mirrored_bone_idx = find_bone(bone_name.replace(right_name, left_name) if bone_name.contains(right_name) else bone_name.replace(left_name, right_name))\n    if mirrored_bone_idx == -1:\n        print(\"Mirrored bone does not exist in Skeleton\")\n        return\n\n    var tr :Transform3D = get_bone_pose(bone_idx)\n    var opposite_tr :Transform3D = get_bone_pose(mirrored_bone_idx)\n    var mirrored_rot = tr.basis.get_rotation_quaternion()\n    mirrored_rot.x *= -1\n    mirrored_rot.w *= -1\n\n    var opposite_mirrored_rot = opposite_tr.basis.get_rotation_quaternion()\n    opposite_mirrored_rot.x *= -1\n    opposite_mirrored_rot.w *= -1\n\n    set_bone_pose_rotation(mirrored_bone_idx, mirrored_rot)\n    set_bone_pose_rotation(bone_idx, opposite_mirrored_rot)"
+    "text": "We need an art direction in V-Sekai for our work. Without a defined art direction, we risk inconsistency and lack of cohesion in our visual presentation."
   },
   {
-    "objectID": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#context",
-    "href": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#context",
-    "title": "Accepted: Use the Humanoid Profile for Character Motion Mirroring",
+    "objectID": "decisions/20240710-art-direction-in-vsekai.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "href": "decisions/20240710-art-direction-in-vsekai.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
+    "title": "Proposed: Art Direction in V-Sekai Process",
     "section": "",
-    "text": "Daniel Snd was looking for a simple way to mirror right-sided walking keyframes on a character avatar motion."
+    "text": "Concept Art Creation: Develop initial concept art to explore different themes and styles.\nCommunity Feedback: Share concept art with the community for feedback and suggestions.\nStyle Guide Development: Create a comprehensive style guide based on the chosen art direction.\nImplementation: Apply the style guide across all assets and environments within V-Sekai."
   },
   {
-    "objectID": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#problem-statement",
-    "href": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#problem-statement",
-    "title": "Accepted: Use the Humanoid Profile for Character Motion Mirroring",
+    "objectID": "decisions/20240710-art-direction-in-vsekai.html#the-benefits",
+    "href": "decisions/20240710-art-direction-in-vsekai.html#the-benefits",
+    "title": "Proposed: Art Direction in V-Sekai Process",
     "section": "",
-    "text": "Daniel Snd did not utilize the Godot Engine humanoid profile."
+    "text": "Visual Cohesion: A unified art direction ensures a consistent and professional appearance.\nEnhanced User Experience: A well-defined aesthetic can make the virtual environment more immersive and enjoyable.\nBrand Identity: Establishing a unique visual style helps in building a recognizable brand."
   },
   {
-    "objectID": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#solution-description",
-    "href": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#solution-description",
-    "title": "Accepted: Use the Humanoid Profile for Character Motion Mirroring",
+    "objectID": "decisions/20240710-art-direction-in-vsekai.html#the-downsides",
+    "href": "decisions/20240710-art-direction-in-vsekai.html#the-downsides",
+    "title": "Proposed: Art Direction in V-Sekai Process",
     "section": "",
-    "text": "The solution is to use the Godot Engine humanoid profile.\n\n\nIn Godot Engine, the animation humanoid profile is essential for managing bone rolls in incoming humanoid skeletons. This is because these skeletons often have arbitrary bone rolls that need to be standardized for consistent animation behavior.\n\n\nBone roll refers to the rotation around the bone’s longitudinal axis. In 3D modeling and animation, it’s important to correctly set up bone rolls as they determine the axes of rotation for the bones during animation.\n\n\n\nThe SkeletonProfileHumanoid in Godot 4.0 adopts a practical rule for managing bone rolls:\n\nThe +Y axis should point from the parent joint to the child joint. This is considered as the roll axis.\nThe +X rotation should bend the joints towards the body’s inside (almost the direction of muscle contraction).\n\n\n\n\nIf you mirror animations, the bone rolls and names may need to be corrected. This is because the orientation of the bones can get flipped during the mirroring process. The Godot Humanoid Profile applies a Bone Rule to the bone rolls.\n\n\n\nThe Godot Humanoid Profile standardizes the bone names consistently, it allows one to reuse animations across different characters. For example, if one has a walking animation for one character and one wants to apply it to another character, having the same bone names will allow one to do this without any additional work.\n\n\n\nIn 3D animation, the T-Pose is a standard pose where the character stands upright with their arms extended straight out to the sides. This pose is often used as the default pose for rigging and animating characters because it provides a clear view of all parts of the character. However, not all models are initially in a T-Pose. If you have a model in any other pose (let’s say it’s an A-Pose), you might need to convert it to a T-Pose before you can use it effectively in Godot.\n\n\n\n\nThe engine can ensure that all humanoid animations behave consistently, regardless of the original orientation or roll of the bones in the imported skeleton by following the Bone Rule. This makes it easier to create and manage humanoid animations, especially when working with different humanoids that may have been rigged differently."
+    "text": "Limited Creativity: Strict adherence to a specific art direction may limit creative expression.\nInitial Setup Time: Developing and implementing an art direction requires an initial investment of time and resources."
   },
   {
-    "objectID": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#benefits",
-    "href": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#benefits",
-    "title": "Accepted: Use the Humanoid Profile for Character Motion Mirroring",
+    "objectID": "decisions/20240710-art-direction-in-vsekai.html#the-road-not-taken",
+    "href": "decisions/20240710-art-direction-in-vsekai.html#the-road-not-taken",
+    "title": "Proposed: Art Direction in V-Sekai Process",
     "section": "",
-    "text": "Using the Godot Humanoid Profile will allow for consistent behavior across all humanoid animations, making it easier to create and manage these animations. It also allows for reusability of animations across different characters, saving time and effort in animation creation."
+    "text": "Alternative approaches such as allowing individual artists complete freedom or using multiple art styles were considered but ultimately deemed less effective for maintaining visual consistency."
   },
   {
-    "objectID": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#downsides",
-    "href": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#downsides",
-    "title": "Accepted: Use the Humanoid Profile for Character Motion Mirroring",
+    "objectID": "decisions/20240710-art-direction-in-vsekai.html#the-infrequent-use-case",
+    "href": "decisions/20240710-art-direction-in-vsekai.html#the-infrequent-use-case",
+    "title": "Proposed: Art Direction in V-Sekai Process",
     "section": "",
-    "text": "There may be a learning curve associated with understanding and implementing the Godot Humanoid Profile. Additionally, this solution assumes that all incoming humanoid skeletons will be compatible with the Godot Humanoid Profile, which may not always be the case."
+    "text": "In scenarios where highly specialized or technical visual elements are required, additional oversight may be necessary to ensure they align with the overall art direction."
   },
   {
-    "objectID": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#the-road-not-taken",
-    "href": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#the-road-not-taken",
-    "title": "Accepted: Use the Humanoid Profile for Character Motion Mirroring",
+    "objectID": "decisions/20240710-art-direction-in-vsekai.html#in-core-and-done-by-us",
+    "href": "decisions/20240710-art-direction-in-vsekai.html#in-core-and-done-by-us",
+    "title": "Proposed: Art Direction in V-Sekai Process",
     "section": "",
-    "text": "An alternative could have been to manually adjust the bone rolls and names for each individual animation. However, this would be a time-consuming process and would not guarantee consistent results across different animations."
+    "text": "This proposal aligns with our core values of efficiency and professionalism and will be implemented by our team."
   },
   {
-    "objectID": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#the-infrequent-use-case",
-    "href": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#the-infrequent-use-case",
-    "title": "Accepted: Use the Humanoid Profile for Character Motion Mirroring",
+    "objectID": "decisions/20240710-art-direction-in-vsekai.html#status",
+    "href": "decisions/20240710-art-direction-in-vsekai.html#status",
+    "title": "Proposed: Art Direction in V-Sekai Process",
     "section": "",
-    "text": "This proposal may not be beneficial for non-humanoid animations or for projects that do not require motion mirroring."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#in-core-and-done-by-us",
-    "href": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#in-core-and-done-by-us",
-    "title": "Accepted: Use the Humanoid Profile for Character Motion Mirroring",
+    "objectID": "decisions/20240710-art-direction-in-vsekai.html#decision-makers",
+    "href": "decisions/20240710-art-direction-in-vsekai.html#decision-makers",
+    "title": "Proposed: Art Direction in V-Sekai Process",
     "section": "",
-    "text": "This proposal involves using an existing feature of the Godot Engine the V-Sekai team implemented in Godot Engine 4.0, so no additional development work would be required from our team."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#status",
-    "href": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#status",
-    "title": "Accepted: Use the Humanoid Profile for Character Motion Mirroring",
+    "objectID": "decisions/20240710-art-direction-in-vsekai.html#tags",
+    "href": "decisions/20240710-art-direction-in-vsekai.html#tags",
+    "title": "Proposed: Art Direction in V-Sekai Process",
     "section": "",
-    "text": "Status: Accepted"
+    "text": "V-Sekai"
   },
   {
-    "objectID": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#decision-makers",
-    "href": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#decision-makers",
-    "title": "Accepted: Use the Humanoid Profile for Character Motion Mirroring",
+    "objectID": "decisions/20240710-art-direction-in-vsekai.html#further-reading",
+    "href": "decisions/20240710-art-direction-in-vsekai.html#further-reading",
+    "title": "Proposed: Art Direction in V-Sekai Process",
     "section": "",
-    "text": "V-Sekai development team"
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#tags",
-    "href": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#tags",
-    "title": "Accepted: Use the Humanoid Profile for Character Motion Mirroring",
+    "objectID": "decisions/20230408-v-sekai-launcher.html",
+    "href": "decisions/20230408-v-sekai-launcher.html",
+    "title": "Proposed: Provide v-sekai-game in a launcher to make it easier to use v-sekai",
     "section": "",
-    "text": "Godot Engine\nHumanoid Profile\nAnimation Mirroring\nBone Rolls\nCharacter Avatar Motion\n3D Modeling\nT-Pose Conversion\nAnimation Reusability\nV-Sekai\nVR Animation"
+    "text": "Proposed: Provide v-sekai-game in a launcher to make it easier to use v-sekai\n\nMetadata\n\nStatus: proposed \nDeciders: V-Sekai,\nTags: V-Sekai,\n\n\n\nContext and Problem Statement\nProvide v-sekai-game in a launcher.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nMake a graphical launcher that runs scoop.\nRun scoop bucket add v-sekai-central https://github.com/v-sekai/v-sekai-central.\nTo install, do scoop install v-sekai-game.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\n\nCreate a scoop bucket at https://github.com/V-Sekai/v-sekai-central\nStore game builds in git repos using desync to put separate the files into chunks.\nIn the manifest decompress the desync files.\n\n\n\nPositive Consequences\nWe are able to use V-Sekai easier.\n\n\nNegative Consequences\nWe cannot get other features in.\n\n\nOption graveyard\nDo nothing.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nThis is a json manifest which is a bit more than a few lines of script.\n\n\nIs there a reason why this should be core and done by us?\nWant to make it easier to use v-sekai.\n\n\nReferences\n\nV-Sekai"
   },
   {
-    "objectID": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#further-reading",
-    "href": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#further-reading",
-    "title": "Accepted: Use the Humanoid Profile for Character Motion Mirroring",
+    "objectID": "decisions/20230831-fixing-upload-limits.html",
+    "href": "decisions/20230831-fixing-upload-limits.html",
+    "title": "Accepted: Enhancing Map Uploads",
     "section": "",
-    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.\nV-Sekai/v-sekai-game is the GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.\nFire\n\nAI assistant Aria assisted with this article."
+    "text": "Status: accepted\nDeciders: V-Sekai, fire, Scipi\nTags: V-Sekai\n\n\n\n\nV-Sekai is facing limitations in its Elixir uro backend when uploading maps, specifically related to the Godot Engine scenes. These limitations are believed to be caused by a restriction in the Waffles library.\n\n\n\nThe challenge at hand is to address the arbitrary limitations imposed by the Waffles library on the Godot Engine scenes during map uploads in the Elixir uro backend of V-Sekai.\n\n\n\nTo overcome this challenge, we propose patching the Waffles library in collaboration with our new contributor.\n\n\n\nBy patching the Waffles library, we can effectively remove the limitations on the Godot Engine scenes and improve the functionality of map uploads in V-Sekai.\n\n\n\nIt is important to consider any potential downsides or risks associated with patching the Waffles library. Further analysis and testing may be required to ensure compatibility and stability.\n\n\n\nAlternative solutions to address the limitations have been explored, but patching the Waffles library appears to be the most viable option.\n\n\n\nThis limitation impacts the specific use case of map uploads in the Elixir uro backend, and may not affect other functionalities in V-Sekai.\n\n\n\nAs a core functionality of V-Sekai, addressing the limitations in the Godot Engine scenes during map uploads is a task that should be done by our team.\n\n\n\n\nV-Sekai\nThis article is assisted by AI.\nhttps://github.com/V-Sekai/v-sekai-game/issues/68"
   },
   {
-    "objectID": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#mirroring-script",
-    "href": "decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html#mirroring-script",
-    "title": "Accepted: Use the Humanoid Profile for Character Motion Mirroring",
+    "objectID": "decisions/20230831-fixing-upload-limits.html#metadata",
+    "href": "decisions/20230831-fixing-upload-limits.html#metadata",
+    "title": "Accepted: Enhancing Map Uploads",
     "section": "",
-    "text": "## SPDX-License-Identifier: CC0-1.0\n##\n## Author: Daniel Snd\n\n@export var left_name:String = \"Left\"\n@export var right_name:String = \"Right\"\n\nfunc do_mirror():\n    var parenteless_ids :PackedInt32Array = get_parentless_bones()\n    for p in get_parentless_bones():\n        attempt_mirror_recursive(p)\n\nfunc attempt_mirror_recursive(bone_id:int):\n    for i in get_bone_children(bone_id):\n        var bone_name = get_bone_name(i)\n        if bone_name.contains(right_name):\n            mirror_pose(bone_name)\n        elif bone_name.contains(left_name):\n            pass\n        else:\n            mirror_single_bone(i)\n        attempt_mirror_recursive(i)\n\nfunc mirror_single_bone(bone_idx):\n    var mirrored_rot = get_bone_pose(bone_idx).basis.get_rotation_quaternion()\n    mirrored_rot.x *= -1\n    mirrored_rot.w *= -1\n    set_bone_pose_rotation(bone_idx, mirrored_rot)\n\n# Function to mirror pose\nfunc mirror_pose(bone_name):\n    var bone_idx = find_bone(bone_name)\n    if bone_idx == -1:\n        print(\"Bone does not exist in Skeleton\")\n        return\n\n    var mirrored_bone_idx = find_bone(bone_name.replace(right_name, left_name) if bone_name.contains(right_name) else bone_name.replace(left_name, right_name))\n    if mirrored_bone_idx == -1:\n        print(\"Mirrored bone does not exist in Skeleton\")\n        return\n\n    var tr :Transform3D = get_bone_pose(bone_idx)\n    var opposite_tr :Transform3D = get_bone_pose(mirrored_bone_idx)\n    var mirrored_rot = tr.basis.get_rotation_quaternion()\n    mirrored_rot.x *= -1\n    mirrored_rot.w *= -1\n\n    var opposite_mirrored_rot = opposite_tr.basis.get_rotation_quaternion()\n    opposite_mirrored_rot.x *= -1\n    opposite_mirrored_rot.w *= -1\n\n    set_bone_pose_rotation(mirrored_bone_idx, mirrored_rot)\n    set_bone_pose_rotation(bone_idx, opposite_mirrored_rot)"
+    "text": "Status: accepted\nDeciders: V-Sekai, fire, Scipi\nTags: V-Sekai"
   },
   {
-    "objectID": "decisions/20211229-run-meetings-using-lean-coffee.html",
-    "href": "decisions/20211229-run-meetings-using-lean-coffee.html",
-    "title": "Accepted: Run meetings using Lean Coffee",
+    "objectID": "decisions/20230831-fixing-upload-limits.html#the-backdrop",
+    "href": "decisions/20230831-fixing-upload-limits.html#the-backdrop",
+    "title": "Accepted: Enhancing Map Uploads",
     "section": "",
-    "text": "Status: accepted \nDeciders: V-Sekai,Mr. Metaverse,fire,\nTags: V-Sekai,\n\n\n\nMeetings need to be ran better than randomly.\n\n\n\nLean coffee can improve on meetings.\n\n\n\nThree column kanban board. To discuss, discussing, and discussed.\nHave everyone add cards for topics they want to discuss. It may take 2-3 min for people to get into the Trello board. Once in take 2-3 min to add topics to the left column.\nThen have everyone vote, each person gets 2-3 votes. To vote, they should click the card of a topic to discuss and in the comments type “+”. Be sure nobody else adds any other comments until we begin discussing the cards.\nLast, sort the cards by number of comments (most amount of + go to top) and then one by one drag in the top card to “discussing”. Set a timer for 5 minutes. After 5 minutes the group votes to keep discussing or to move on. While discussing the group can add comments or links to the card while discussing.\n\n\n\n\nOrganized meetings are better\n\n\n\n\n\nCan be strange to use because it’s not common.\n\n\n\n\n\nOption: Gather for one hour randomly.\nRejection Reason: We can do better.\n\n\n\n\nNot code.\n\n\n\nWe need to run better meetings.\n\n\n\n\nhttps://leanchange.org/resources/leancoffee\n\n\n\n\nCopyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "V-Sekai is facing limitations in its Elixir uro backend when uploading maps, specifically related to the Godot Engine scenes. These limitations are believed to be caused by a restriction in the Waffles library."
   },
   {
-    "objectID": "decisions/20211229-run-meetings-using-lean-coffee.html#context-and-problem-statement",
-    "href": "decisions/20211229-run-meetings-using-lean-coffee.html#context-and-problem-statement",
-    "title": "Accepted: Run meetings using Lean Coffee",
+    "objectID": "decisions/20230831-fixing-upload-limits.html#the-challenge",
+    "href": "decisions/20230831-fixing-upload-limits.html#the-challenge",
+    "title": "Accepted: Enhancing Map Uploads",
     "section": "",
-    "text": "Meetings need to be ran better than randomly."
+    "text": "The challenge at hand is to address the arbitrary limitations imposed by the Waffles library on the Godot Engine scenes during map uploads in the Elixir uro backend of V-Sekai."
   },
   {
-    "objectID": "decisions/20211229-run-meetings-using-lean-coffee.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20211229-run-meetings-using-lean-coffee.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Accepted: Run meetings using Lean Coffee",
+    "objectID": "decisions/20230831-fixing-upload-limits.html#the-strategy",
+    "href": "decisions/20230831-fixing-upload-limits.html#the-strategy",
+    "title": "Accepted: Enhancing Map Uploads",
     "section": "",
-    "text": "Lean coffee can improve on meetings."
+    "text": "To overcome this challenge, we propose patching the Waffles library in collaboration with our new contributor."
   },
   {
-    "objectID": "decisions/20211229-run-meetings-using-lean-coffee.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20211229-run-meetings-using-lean-coffee.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Accepted: Run meetings using Lean Coffee",
+    "objectID": "decisions/20230831-fixing-upload-limits.html#the-upside",
+    "href": "decisions/20230831-fixing-upload-limits.html#the-upside",
+    "title": "Accepted: Enhancing Map Uploads",
     "section": "",
-    "text": "Three column kanban board. To discuss, discussing, and discussed.\nHave everyone add cards for topics they want to discuss. It may take 2-3 min for people to get into the Trello board. Once in take 2-3 min to add topics to the left column.\nThen have everyone vote, each person gets 2-3 votes. To vote, they should click the card of a topic to discuss and in the comments type “+”. Be sure nobody else adds any other comments until we begin discussing the cards.\nLast, sort the cards by number of comments (most amount of + go to top) and then one by one drag in the top card to “discussing”. Set a timer for 5 minutes. After 5 minutes the group votes to keep discussing or to move on. While discussing the group can add comments or links to the card while discussing."
+    "text": "By patching the Waffles library, we can effectively remove the limitations on the Godot Engine scenes and improve the functionality of map uploads in V-Sekai."
   },
   {
-    "objectID": "decisions/20211229-run-meetings-using-lean-coffee.html#positive-consequences",
-    "href": "decisions/20211229-run-meetings-using-lean-coffee.html#positive-consequences",
-    "title": "Accepted: Run meetings using Lean Coffee",
+    "objectID": "decisions/20230831-fixing-upload-limits.html#the-downside",
+    "href": "decisions/20230831-fixing-upload-limits.html#the-downside",
+    "title": "Accepted: Enhancing Map Uploads",
     "section": "",
-    "text": "Organized meetings are better"
+    "text": "It is important to consider any potential downsides or risks associated with patching the Waffles library. Further analysis and testing may be required to ensure compatibility and stability."
   },
   {
-    "objectID": "decisions/20211229-run-meetings-using-lean-coffee.html#negative-consequences",
-    "href": "decisions/20211229-run-meetings-using-lean-coffee.html#negative-consequences",
-    "title": "Accepted: Run meetings using Lean Coffee",
+    "objectID": "decisions/20230831-fixing-upload-limits.html#the-road-not-taken",
+    "href": "decisions/20230831-fixing-upload-limits.html#the-road-not-taken",
+    "title": "Accepted: Enhancing Map Uploads",
     "section": "",
-    "text": "Can be strange to use because it’s not common."
+    "text": "Alternative solutions to address the limitations have been explored, but patching the Waffles library appears to be the most viable option."
   },
   {
-    "objectID": "decisions/20211229-run-meetings-using-lean-coffee.html#option-graveyard",
-    "href": "decisions/20211229-run-meetings-using-lean-coffee.html#option-graveyard",
-    "title": "Accepted: Run meetings using Lean Coffee",
+    "objectID": "decisions/20230831-fixing-upload-limits.html#the-infrequent-use-case",
+    "href": "decisions/20230831-fixing-upload-limits.html#the-infrequent-use-case",
+    "title": "Accepted: Enhancing Map Uploads",
     "section": "",
-    "text": "Option: Gather for one hour randomly.\nRejection Reason: We can do better."
+    "text": "This limitation impacts the specific use case of map uploads in the Elixir uro backend, and may not affect other functionalities in V-Sekai."
   },
   {
-    "objectID": "decisions/20211229-run-meetings-using-lean-coffee.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20211229-run-meetings-using-lean-coffee.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Accepted: Run meetings using Lean Coffee",
+    "objectID": "decisions/20230831-fixing-upload-limits.html#in-core-and-done-by-us",
+    "href": "decisions/20230831-fixing-upload-limits.html#in-core-and-done-by-us",
+    "title": "Accepted: Enhancing Map Uploads",
     "section": "",
-    "text": "Not code."
+    "text": "As a core functionality of V-Sekai, addressing the limitations in the Godot Engine scenes during map uploads is a task that should be done by our team."
   },
   {
-    "objectID": "decisions/20211229-run-meetings-using-lean-coffee.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20211229-run-meetings-using-lean-coffee.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Accepted: Run meetings using Lean Coffee",
+    "objectID": "decisions/20230831-fixing-upload-limits.html#further-reading",
+    "href": "decisions/20230831-fixing-upload-limits.html#further-reading",
+    "title": "Accepted: Enhancing Map Uploads",
     "section": "",
-    "text": "We need to run better meetings."
+    "text": "V-Sekai\nThis article is assisted by AI.\nhttps://github.com/V-Sekai/v-sekai-game/issues/68"
   },
   {
-    "objectID": "decisions/20211229-run-meetings-using-lean-coffee.html#references",
-    "href": "decisions/20211229-run-meetings-using-lean-coffee.html#references",
-    "title": "Accepted: Run meetings using Lean Coffee",
+    "objectID": "decisions/20230922-spacetime-shadow-shards-sync.html",
+    "href": "decisions/20230922-spacetime-shadow-shards-sync.html",
+    "title": "Proposed: Streamlining V-Sekai Performance",
     "section": "",
-    "text": "https://leanchange.org/resources/leancoffee"
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, Godot, Networking\n\n\n\n\nV-Sekai, leveraging the Godot client-server model, aspires to support 1000-2000 clients. The objective is to deliver uninterrupted gameplay and a comprehensive gaming experience.\n\n\n\nKey challenges encompass managing single-shard overload, administering shadow shards, and implementing state synchronization and game state transitions. These tasks necessitate precise planning, execution, and monitoring for peak performance.\n\n\n\nA simple gameplay session will be initiated where an art seller can upload artwork. The game environment will be a flat surface with a boundary, allowing mathematical movement calculations without a navigation mesh.\nThe number of clients connecting to the server will gradually increase, starting small and eventually reaching 2,000. This will test the server’s capacity to handle multiple connections. During testing, system resources will be monitored to estimate the cost and resources required to support 2000 players. Gameplay sessions will be recorded for the trade show, and load testing will be conducted to ensure our server can manage the maximum number of players without crashing or significant slowdowns.\n\nServer Configuration: Set up a Godot server that listens on a designated port.\nClient Development: Build a Godot client that connects to our server using High-Level Networking.\nShadow Shard Administration: Generate shadow copies of the original shard, serialize them for network transmission, and synchronize their state periodically.\nState Synchronization: Develop Ref&lt;Animation&gt; data structures symbolizing different parts of the model and outline their interactions.\nGame State Transitions: Preserve, the current game state, pinpoint the target state, transition to it, and validate the transition using an orphan AnimationTree.\n\n\n\n\nThis strategy allows us to accommodate numerous clients simultaneously without sacrificing performance or user experience. It also provides a systematic method to monitor and enhance gaming sessions.\n\n\n\nThis approach requires substantial resources and expertise in server configuration, networking, and game development. Unexpected challenges may surface during implementation and testing.\n\n\n\nA potential alternative could have been adopting a different game engine or networking model. However, this would demand a complete revamp of our existing setup, possibly compromising performance and flexibility.\n\n\n\nControversial plans are essential to minimize gameplay disruption in unexpected traffic surges or server outages.\n\n\n\nAll tasks outlined are integral to our operations and will be undertaken by us.\n\n\n\n\n[V-Sekai]\nAI assists this article."
   },
   {
-    "objectID": "decisions/20211229-run-meetings-using-lean-coffee.html#derivative-license",
-    "href": "decisions/20211229-run-meetings-using-lean-coffee.html#derivative-license",
-    "title": "Accepted: Run meetings using Lean Coffee",
+    "objectID": "decisions/20230922-spacetime-shadow-shards-sync.html#metadata",
+    "href": "decisions/20230922-spacetime-shadow-shards-sync.html#metadata",
+    "title": "Proposed: Streamlining V-Sekai Performance",
     "section": "",
-    "text": "Copyright (c) 2021 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "Status: Proposed\nDeciders: V-Sekai\nTags: V-Sekai, Godot, Networking"
   },
   {
-    "objectID": "decisions/20221016-v-sekai-view-replication.html",
-    "href": "decisions/20221016-v-sekai-view-replication.html",
-    "title": "Rejected: Use view replication algorithm for multiplayer multirelay sync",
+    "objectID": "decisions/20230922-spacetime-shadow-shards-sync.html#background",
+    "href": "decisions/20230922-spacetime-shadow-shards-sync.html#background",
+    "title": "Proposed: Streamlining V-Sekai Performance",
     "section": "",
-    "text": "Status: rejected\nDeciders: V-Sekai,fire,\nTags: V-Sekai,sync,view replication,\n\n\n\nSee replicate sync 100’000 entities using a solution.\n\n\n\nV-Sekai could use viewstamp replication in the context of game entity interpolation of past and current state.\nThe key insight is everything is a keyframed animation that is nearest, linear or cubic interpolated.\n\n\n\nWe assume we’re using Godot Engine 4 with float is doubles.\n\nReplicate pending property changes safely to a quorum of distributed replicas, then\ninterpolate property changes to the in-memory state.\n\nIgnore p_time too far in the future or the past as the viewstamp limit.\nT Animation::_interpolate(const Vector&lt;TKey&lt;T&gt;&gt; &p_keys, double p_time, InterpolationType p_interp, bool p_loop_wrap, bool *p_ok, bool p_backward) const\n\nACK to the client.\n\nSee also Linux io_uring (replacement for epoll).\nEverything is an interpolation event or a property state. Want to fit datastructures into 128 bytes (2 CPU cache lines).\nWe reuse the create_property data structure as the state.\n\n\nReferencing https://github.com/tigerbeetledb/tigerbeetle/blob/main/docs/DESIGN.md#data-structures.\nSee Variant bytes_to_var_with_objects (PackedByteArray bytes) and PackedByteArray var_to_bytes_with_objects (Variant variable).\n\n\ncreate_property_interpolate {\n           id: 16 bytes (128-bit)\n   past_entity_id: 16 bytes (128-bit)\ncurrent_entity_id: 16 bytes (128-bit) [to allow interpolation between different entities]\n    user_data: 16 bytes (128-bit) [optional, e.g. opaque third-party identifier to link\n        this transfer (many-to-one) to an external entity]\n     reserved: 16 bytes (128-bit) [reserved, for accounting policy primitives]\n       pending_id: 16 bytes (128-bit) [optional, required to post or void an existing but pending transfer]\n      timeout:  8 bytes (64-bit) [optional, required only for a pending transfer, a quantity of time,\n        i.e. an offset in nanoseconds from timestamp]\n        shard:  4 bytes (32-bit) [required, to enforce isolation by ensuring that all transfers\n        are between entities of the same shard]\n         code:  2 bytes (16-bit) [required, an opaque entity code describing the type\n        of the interpolation, e.g. player, map, prop]\n        flags:  2 bytes (16-bit) [optional, to modify the usage of the reserved field and for future feature expansion.]\n        value:  n bytes (n-bit) [required, variant of the past property and current property,\n        which must be the same for both properties. Uses var_to_bytes_with_objects.]\n    timestamp:  8 bytes (64-bit) [reserved, assigned by the leader before journaling]\n} = n bytes (n CPU cache lines)\n\n\n\n   create_property {\n          id: 16 bytes (128-bit)\n       user_data: 16 bytes (128-bit) [optional, opaque third-party identifier to link this account\n        (many-to-one) to an external entity]\n    reserved: 48 bytes (384-bit) [reserved for future accounting policy primitives]\n       shard:  4 bytes (32-bit) [required, to enforce isolation by ensuring that all transfers\n        are between accounts of the same ledger]\n        code:  2 bytes (16-bit) [required, an opaque entity code describing the type\n        of the interpolation, e.g. player, map, prop]\n       flags:  2 bytes (16-bit) [optional, net balance limits:\n        e.g. debits_must_not_exceed_credits or credits_must_not_exceed_debits]\n     past_interpolations_pending: n bytes (n-bit variant. Uses var_to_bytes_with_objects.)\n      past_interpolations_posted: n bytes (n-bit variant. Uses var_to_bytes_with_objects.)\n  current_interpolations_pending: n bytes (n-bit variant. Uses var_to_bytes_with_objects.)\n   current_interpolations_posted: n bytes (n-bit variant. Uses var_to_bytes_with_objects.)\n               timestamp: 8 bytes ( 64-bit) [reserved]\n} = n bytes (n CPU cache lines)\n\n\n\n\n\n\nThe code is based on robust view replication consensus algorithm theory.\nThe playback of the state machine is deterministic.\n\n\n\n\n\nMinimum of three relays.\n\n\n\n\n\nOption: Current V-Sekai replication\nRejection Reason: Can’t link servers\n\n\n\n\nEntity replication is not trivial.\n\n\n\nWe’re doing the networking layer.\n\n\n\n\nAdd a multiplayer interface and visual nodes for SceneTree replication\nLMAX Exchange Architecture\n\nLMAX (quote):\n\n\njournal incoming events safely to disk, and\nreplicate to backup nodes, then\napply these events to the in-memory state, then\nACK to the client\n\n\n\nTigerbeetle design\n\nTigerbeetle uses viewstamp replication in the context of bank ledger credit and debit.\nTigerbeetle (quote):\n\n\nreplicate incoming events safely to a quorum of distributed replicas, then\napply these events to the in-memory state, then\nACK to the client\n\n\n\nviewstamped-replication-made-famous\nvr-revisited.pdf\nTigerBeetle Discord server\nCubic interpolation\n\n\n\n\nNote that this handles both nearest interpolation and cubic (with time) interpolation.\ntemplate &lt;class T&gt;\nT Animation::_interpolate(const Vector&lt;TKey&lt;T&gt;&gt; &p_keys, double p_time, InterpolationType p_interp, bool p_loop_wrap, bool *p_ok, bool p_backward) const {\n    int len = _find(p_keys, length) + 1; // try to find last key (there may be more past the end)\n\n    if (len &lt;= 0) {\n        // (-1 or -2 returned originally) (plus one above)\n        // meaning no keys, or only key time is larger than length\n        if (p_ok) {\n            *p_ok = false;\n        }\n        return T();\n    } else if (len == 1) { // one key found (0+1), return it\n\n        if (p_ok) {\n            *p_ok = true;\n        }\n        return p_keys[0].value;\n    }\n\n    int idx = _find(p_keys, p_time, p_backward);\n\n    ERR_FAIL_COND_V(idx == -2, T());\n\n    bool result = true;\n    int next = 0;\n    real_t c = 0.0;\n    // prepare for all cases of interpolation\n\n    if (loop_mode == LOOP_LINEAR && p_loop_wrap) {\n        // loop\n        if (!p_backward) {\n            // no backward\n            if (idx &gt;= 0) {\n                if (idx &lt; len - 1) {\n                    next = idx + 1;\n                    real_t delta = p_keys[next].time - p_keys[idx].time;\n                    real_t from = p_time - p_keys[idx].time;\n\n                    if (Math::is_zero_approx(delta)) {\n                        c = 0;\n                    } else {\n                        c = from / delta;\n                    }\n                } else {\n                    next = 0;\n                    real_t delta = (length - p_keys[idx].time) + p_keys[next].time;\n                    real_t from = p_time - p_keys[idx].time;\n\n                    if (Math::is_zero_approx(delta)) {\n                        c = 0;\n                    } else {\n                        c = from / delta;\n                    }\n                }\n            } else {\n                // on loop, behind first key\n                idx = len - 1;\n                next = 0;\n                real_t endtime = (length - p_keys[idx].time);\n                if (endtime &lt; 0) { // may be keys past the end\n                    endtime = 0;\n                }\n                real_t delta = endtime + p_keys[next].time;\n                real_t from = endtime + p_time;\n\n                if (Math::is_zero_approx(delta)) {\n                    c = 0;\n                } else {\n                    c = from / delta;\n                }\n            }\n        } else {\n            // backward\n            if (idx &lt;= len - 1) {\n                if (idx &gt; 0) {\n                    next = idx - 1;\n                    real_t delta = (length - p_keys[next].time) - (length - p_keys[idx].time);\n                    real_t from = (length - p_time) - (length - p_keys[idx].time);\n\n                    if (Math::is_zero_approx(delta)) {\n                        c = 0;\n                    } else {\n                        c = from / delta;\n                    }\n                } else {\n                    next = len - 1;\n                    real_t delta = p_keys[idx].time + (length - p_keys[next].time);\n                    real_t from = (length - p_time) - (length - p_keys[idx].time);\n\n                    if (Math::is_zero_approx(delta)) {\n                        c = 0;\n                    } else {\n                        c = from / delta;\n                    }\n                }\n            } else {\n                // on loop, in front of last key\n                idx = 0;\n                next = len - 1;\n                real_t endtime = p_keys[idx].time;\n                if (endtime &gt; length) { // may be keys past the end\n                    endtime = length;\n                }\n                real_t delta = p_keys[next].time - endtime;\n                real_t from = p_time - endtime;\n\n                if (Math::is_zero_approx(delta)) {\n                    c = 0;\n                } else {\n                    c = from / delta;\n                }\n            }\n        }\n    } else { // no loop\n        if (!p_backward) {\n            if (idx &gt;= 0) {\n                if (idx &lt; len - 1) {\n                    next = idx + 1;\n                    real_t delta = p_keys[next].time - p_keys[idx].time;\n                    real_t from = p_time - p_keys[idx].time;\n\n                    if (Math::is_zero_approx(delta)) {\n                        c = 0;\n                    } else {\n                        c = from / delta;\n                    }\n                } else {\n                    next = idx;\n                }\n            } else {\n                idx = next = 0;\n            }\n        } else {\n            if (idx &lt;= len - 1) {\n                if (idx &gt; 0) {\n                    next = idx - 1;\n                    real_t delta = (length - p_keys[next].time) - (length - p_keys[idx].time);\n                    real_t from = (length - p_time) - (length - p_keys[idx].time);\n\n                    if (Math::is_zero_approx(delta)) {\n                        c = 0;\n                    } else {\n                        c = from / delta;\n                    }\n\n                } else {\n                    next = idx;\n                }\n            } else {\n                idx = next = len - 1;\n            }\n        }\n    }\n\n    if (p_ok) {\n        *p_ok = result;\n    }\n    if (!result) {\n        return T();\n    }\n\n    real_t tr = p_keys[idx].transition;\n\n    if (tr == 0 || idx == next) {\n        // don't interpolate if not needed\n        return p_keys[idx].value;\n    }\n\n    if (tr != 1.0) {\n        c = Math::ease(c, tr);\n    }\n\n    switch (p_interp) {\n        case INTERPOLATION_NEAREST: {\n            return p_keys[idx].value;\n        } break;\n        case INTERPOLATION_LINEAR: {\n            return _interpolate(p_keys[idx].value, p_keys[next].value, c);\n        } break;\n        case INTERPOLATION_LINEAR_ANGLE: {\n            return _interpolate_angle(p_keys[idx].value, p_keys[next].value, c);\n        } break;\n        case INTERPOLATION_CUBIC:\n        case INTERPOLATION_CUBIC_ANGLE: {\n            int pre = 0;\n            int post = 0;\n            if (!p_backward) {\n                pre = idx - 1;\n                if (pre &lt; 0) {\n                    if (loop_mode == LOOP_LINEAR && p_loop_wrap) {\n                        pre = len - 1;\n                    } else {\n                        pre = 0;\n                    }\n                }\n                post = next + 1;\n                if (post &gt;= len) {\n                    if (loop_mode == LOOP_LINEAR && p_loop_wrap) {\n                        post = 0;\n                    } else {\n                        post = next;\n                    }\n                }\n            } else {\n                pre = idx + 1;\n                if (pre &gt;= len) {\n                    if (loop_mode == LOOP_LINEAR && p_loop_wrap) {\n                        pre = 0;\n                    } else {\n                        pre = idx;\n                    }\n                }\n                post = next - 1;\n                if (post &lt; 0) {\n                    if (loop_mode == LOOP_LINEAR && p_loop_wrap) {\n                        post = len - 1;\n                    } else {\n                        post = 0;\n                    }\n                }\n            }\n\n            real_t pre_t = 0.0;\n            real_t to_t = 0.0;\n            real_t post_t = 0.0;\n            if (loop_mode == LOOP_LINEAR && p_loop_wrap) {\n                pre_t = pre &gt; idx ? -length + p_keys[pre].time - p_keys[idx].time : p_keys[pre].time - p_keys[idx].time;\n                to_t = next &lt; idx ? length + p_keys[next].time - p_keys[idx].time : p_keys[next].time - p_keys[idx].time;\n                post_t = next &lt; idx || post &lt;= idx ? length + p_keys[post].time - p_keys[idx].time : p_keys[post].time - p_keys[idx].time;\n            } else {\n                pre_t = p_keys[pre].time - p_keys[idx].time;\n                to_t = p_keys[next].time - p_keys[idx].time;\n                post_t = p_keys[post].time - p_keys[idx].time;\n            }\n\n            if (p_interp == INTERPOLATION_CUBIC_ANGLE) {\n                return _cubic_interpolate_angle_in_time(\n                        p_keys[pre].value, p_keys[idx].value, p_keys[next].value, p_keys[post].value, c,\n                        pre_t, to_t, post_t);\n            }\n            return _cubic_interpolate_in_time(\n                    p_keys[pre].value, p_keys[idx].value, p_keys[next].value, p_keys[post].value, c,\n                    pre_t, to_t, post_t);\n        } break;\n        default:\n            return p_keys[idx].value;\n    }\n\n    // do a barrel roll\n}\n\n\n\nCopyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "V-Sekai, leveraging the Godot client-server model, aspires to support 1000-2000 clients. The objective is to deliver uninterrupted gameplay and a comprehensive gaming experience."
   },
   {
-    "objectID": "decisions/20221016-v-sekai-view-replication.html#context-and-problem-statement",
-    "href": "decisions/20221016-v-sekai-view-replication.html#context-and-problem-statement",
-    "title": "Rejected: Use view replication algorithm for multiplayer multirelay sync",
+    "objectID": "decisions/20230922-spacetime-shadow-shards-sync.html#challenges",
+    "href": "decisions/20230922-spacetime-shadow-shards-sync.html#challenges",
+    "title": "Proposed: Streamlining V-Sekai Performance",
     "section": "",
-    "text": "See replicate sync 100’000 entities using a solution."
+    "text": "Key challenges encompass managing single-shard overload, administering shadow shards, and implementing state synchronization and game state transitions. These tasks necessitate precise planning, execution, and monitoring for peak performance."
   },
   {
-    "objectID": "decisions/20221016-v-sekai-view-replication.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "href": "decisions/20221016-v-sekai-view-replication.html#describe-the-proposed-option-and-how-it-helps-to-overcome-the-problem-or-limitation",
-    "title": "Rejected: Use view replication algorithm for multiplayer multirelay sync",
+    "objectID": "decisions/20230922-spacetime-shadow-shards-sync.html#approach",
+    "href": "decisions/20230922-spacetime-shadow-shards-sync.html#approach",
+    "title": "Proposed: Streamlining V-Sekai Performance",
     "section": "",
-    "text": "V-Sekai could use viewstamp replication in the context of game entity interpolation of past and current state.\nThe key insight is everything is a keyframed animation that is nearest, linear or cubic interpolated."
+    "text": "A simple gameplay session will be initiated where an art seller can upload artwork. The game environment will be a flat surface with a boundary, allowing mathematical movement calculations without a navigation mesh.\nThe number of clients connecting to the server will gradually increase, starting small and eventually reaching 2,000. This will test the server’s capacity to handle multiple connections. During testing, system resources will be monitored to estimate the cost and resources required to support 2000 players. Gameplay sessions will be recorded for the trade show, and load testing will be conducted to ensure our server can manage the maximum number of players without crashing or significant slowdowns.\n\nServer Configuration: Set up a Godot server that listens on a designated port.\nClient Development: Build a Godot client that connects to our server using High-Level Networking.\nShadow Shard Administration: Generate shadow copies of the original shard, serialize them for network transmission, and synchronize their state periodically.\nState Synchronization: Develop Ref&lt;Animation&gt; data structures symbolizing different parts of the model and outline their interactions.\nGame State Transitions: Preserve, the current game state, pinpoint the target state, transition to it, and validate the transition using an orphan AnimationTree."
   },
   {
-    "objectID": "decisions/20221016-v-sekai-view-replication.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "href": "decisions/20221016-v-sekai-view-replication.html#describe-how-your-proposal-will-work-with-code-pseudo-code-mock-ups-or-diagrams",
-    "title": "Rejected: Use view replication algorithm for multiplayer multirelay sync",
+    "objectID": "decisions/20230922-spacetime-shadow-shards-sync.html#advantages",
+    "href": "decisions/20230922-spacetime-shadow-shards-sync.html#advantages",
+    "title": "Proposed: Streamlining V-Sekai Performance",
     "section": "",
-    "text": "We assume we’re using Godot Engine 4 with float is doubles.\n\nReplicate pending property changes safely to a quorum of distributed replicas, then\ninterpolate property changes to the in-memory state.\n\nIgnore p_time too far in the future or the past as the viewstamp limit.\nT Animation::_interpolate(const Vector&lt;TKey&lt;T&gt;&gt; &p_keys, double p_time, InterpolationType p_interp, bool p_loop_wrap, bool *p_ok, bool p_backward) const\n\nACK to the client.\n\nSee also Linux io_uring (replacement for epoll).\nEverything is an interpolation event or a property state. Want to fit datastructures into 128 bytes (2 CPU cache lines).\nWe reuse the create_property data structure as the state.\n\n\nReferencing https://github.com/tigerbeetledb/tigerbeetle/blob/main/docs/DESIGN.md#data-structures.\nSee Variant bytes_to_var_with_objects (PackedByteArray bytes) and PackedByteArray var_to_bytes_with_objects (Variant variable).\n\n\ncreate_property_interpolate {\n           id: 16 bytes (128-bit)\n   past_entity_id: 16 bytes (128-bit)\ncurrent_entity_id: 16 bytes (128-bit) [to allow interpolation between different entities]\n    user_data: 16 bytes (128-bit) [optional, e.g. opaque third-party identifier to link\n        this transfer (many-to-one) to an external entity]\n     reserved: 16 bytes (128-bit) [reserved, for accounting policy primitives]\n       pending_id: 16 bytes (128-bit) [optional, required to post or void an existing but pending transfer]\n      timeout:  8 bytes (64-bit) [optional, required only for a pending transfer, a quantity of time,\n        i.e. an offset in nanoseconds from timestamp]\n        shard:  4 bytes (32-bit) [required, to enforce isolation by ensuring that all transfers\n        are between entities of the same shard]\n         code:  2 bytes (16-bit) [required, an opaque entity code describing the type\n        of the interpolation, e.g. player, map, prop]\n        flags:  2 bytes (16-bit) [optional, to modify the usage of the reserved field and for future feature expansion.]\n        value:  n bytes (n-bit) [required, variant of the past property and current property,\n        which must be the same for both properties. Uses var_to_bytes_with_objects.]\n    timestamp:  8 bytes (64-bit) [reserved, assigned by the leader before journaling]\n} = n bytes (n CPU cache lines)\n\n\n\n   create_property {\n          id: 16 bytes (128-bit)\n       user_data: 16 bytes (128-bit) [optional, opaque third-party identifier to link this account\n        (many-to-one) to an external entity]\n    reserved: 48 bytes (384-bit) [reserved for future accounting policy primitives]\n       shard:  4 bytes (32-bit) [required, to enforce isolation by ensuring that all transfers\n        are between accounts of the same ledger]\n        code:  2 bytes (16-bit) [required, an opaque entity code describing the type\n        of the interpolation, e.g. player, map, prop]\n       flags:  2 bytes (16-bit) [optional, net balance limits:\n        e.g. debits_must_not_exceed_credits or credits_must_not_exceed_debits]\n     past_interpolations_pending: n bytes (n-bit variant. Uses var_to_bytes_with_objects.)\n      past_interpolations_posted: n bytes (n-bit variant. Uses var_to_bytes_with_objects.)\n  current_interpolations_pending: n bytes (n-bit variant. Uses var_to_bytes_with_objects.)\n   current_interpolations_posted: n bytes (n-bit variant. Uses var_to_bytes_with_objects.)\n               timestamp: 8 bytes ( 64-bit) [reserved]\n} = n bytes (n CPU cache lines)"
+    "text": "This strategy allows us to accommodate numerous clients simultaneously without sacrificing performance or user experience. It also provides a systematic method to monitor and enhance gaming sessions."
   },
   {
-    "objectID": "decisions/20221016-v-sekai-view-replication.html#positive-consequences",
-    "href": "decisions/20221016-v-sekai-view-replication.html#positive-consequences",
-    "title": "Rejected: Use view replication algorithm for multiplayer multirelay sync",
+    "objectID": "decisions/20230922-spacetime-shadow-shards-sync.html#limitations",
+    "href": "decisions/20230922-spacetime-shadow-shards-sync.html#limitations",
+    "title": "Proposed: Streamlining V-Sekai Performance",
     "section": "",
-    "text": "The code is based on robust view replication consensus algorithm theory.\nThe playback of the state machine is deterministic."
+    "text": "This approach requires substantial resources and expertise in server configuration, networking, and game development. Unexpected challenges may surface during implementation and testing."
   },
   {
-    "objectID": "decisions/20221016-v-sekai-view-replication.html#negative-consequences",
-    "href": "decisions/20221016-v-sekai-view-replication.html#negative-consequences",
-    "title": "Rejected: Use view replication algorithm for multiplayer multirelay sync",
+    "objectID": "decisions/20230922-spacetime-shadow-shards-sync.html#alternatives",
+    "href": "decisions/20230922-spacetime-shadow-shards-sync.html#alternatives",
+    "title": "Proposed: Streamlining V-Sekai Performance",
     "section": "",
-    "text": "Minimum of three relays."
+    "text": "A potential alternative could have been adopting a different game engine or networking model. However, this would demand a complete revamp of our existing setup, possibly compromising performance and flexibility."
   },
   {
-    "objectID": "decisions/20221016-v-sekai-view-replication.html#option-graveyard",
-    "href": "decisions/20221016-v-sekai-view-replication.html#option-graveyard",
-    "title": "Rejected: Use view replication algorithm for multiplayer multirelay sync",
+    "objectID": "decisions/20230922-spacetime-shadow-shards-sync.html#exceptional-scenarios",
+    "href": "decisions/20230922-spacetime-shadow-shards-sync.html#exceptional-scenarios",
+    "title": "Proposed: Streamlining V-Sekai Performance",
     "section": "",
-    "text": "Option: Current V-Sekai replication\nRejection Reason: Can’t link servers"
+    "text": "Controversial plans are essential to minimize gameplay disruption in unexpected traffic surges or server outages."
   },
   {
-    "objectID": "decisions/20221016-v-sekai-view-replication.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "href": "decisions/20221016-v-sekai-view-replication.html#if-this-enhancement-will-not-be-used-often-can-it-be-worked-around-with-a-few-lines-of-script",
-    "title": "Rejected: Use view replication algorithm for multiplayer multirelay sync",
+    "objectID": "decisions/20230922-spacetime-shadow-shards-sync.html#responsibility",
+    "href": "decisions/20230922-spacetime-shadow-shards-sync.html#responsibility",
+    "title": "Proposed: Streamlining V-Sekai Performance",
     "section": "",
-    "text": "Entity replication is not trivial."
+    "text": "All tasks outlined are integral to our operations and will be undertaken by us."
   },
   {
-    "objectID": "decisions/20221016-v-sekai-view-replication.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "href": "decisions/20221016-v-sekai-view-replication.html#is-there-a-reason-why-this-should-be-core-and-done-by-us",
-    "title": "Rejected: Use view replication algorithm for multiplayer multirelay sync",
+    "objectID": "decisions/20230922-spacetime-shadow-shards-sync.html#additional-resources",
+    "href": "decisions/20230922-spacetime-shadow-shards-sync.html#additional-resources",
+    "title": "Proposed: Streamlining V-Sekai Performance",
     "section": "",
-    "text": "We’re doing the networking layer."
+    "text": "[V-Sekai]\nAI assists this article."
   },
   {
-    "objectID": "decisions/20221016-v-sekai-view-replication.html#references",
-    "href": "decisions/20221016-v-sekai-view-replication.html#references",
-    "title": "Rejected: Use view replication algorithm for multiplayer multirelay sync",
+    "objectID": "decisions/20230310-IREE-backend-for-machine-learning-computations.html",
+    "href": "decisions/20230310-IREE-backend-for-machine-learning-computations.html",
+    "title": "Superseded: Creating a Godot Engine C++ module with IREE backend for machine learning computations using Vulkan and CUDA",
     "section": "",
-    "text": "Add a multiplayer interface and visual nodes for SceneTree replication\nLMAX Exchange Architecture\n\nLMAX (quote):\n\n\njournal incoming events safely to disk, and\nreplicate to backup nodes, then\napply these events to the in-memory state, then\nACK to the client\n\n\n\nTigerbeetle design\n\nTigerbeetle uses viewstamp replication in the context of bank ledger credit and debit.\nTigerbeetle (quote):\n\n\nreplicate incoming events safely to a quorum of distributed replicas, then\napply these events to the in-memory state, then\nACK to the client\n\n\n\nviewstamped-replication-made-famous\nvr-revisited.pdf\nTigerBeetle Discord server\nCubic interpolation"
+    "text": "Superseded: Creating a Godot Engine C++ module with IREE backend for machine learning computations using Vulkan and CUDA\n\nMetadata\n\nStatus: superseded by 20230502-add-iree-to-godot-engine-for-image-superresolution \nDeciders: V-Sekai,fire,\nTags: V-Sekai, IREE, Godot Engine, Image Superresolution, Vulkan Backend,chatgpt 4,Google,\n\n\n\nContext and Problem Statement\nI want to have a starting place for testing ai algorithms.\n\n\nDescribe the proposed option and how it helps to overcome the problem or limitation\nCreate a Godot Engine C++ module with a machine learning computation backend.\nFind a interesting test case.\nWant to run the machine learning technology on the player’s computer, the cpu-only server that hosts the game, and the gpu cloud.\nTo summarize, if you’re looking for a sample that demonstrates loading a model at runtime for CPU, Vulkan, and CUDA in C++, you can check out the IREE samples. In particular, the dynamic_shapes and simple_embedding samples showcase how to run on your choice of target. The input program may have a signature in the stablehlo dialect, and you can use IREE or XLA depending on your preferred tech stack or runtime requirements. The Vulkan stack in IREE is relatively stable and offers good performance, with nod.ai’s SHARK offering extra tuning and APIs on top. However, there may be differences in optimization depending on the workload and potential driver bugs and pitfalls.\n\n\nDescribe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams\nProvide IREE to godot engine.\nUses the Vulkan back end.\n\ninput_count\ninput/0/data (TypedArray)\noutput_count\noutput/0/data (TypedArray)\n\n\n\nPositive Consequences\nHave a playground for testing.\n\n\nNegative Consequences\nNo response\n\n\nOption graveyard\nDon’t use onnx because it doesn’t have vulkan support which limits reach.\n\n\nIf this enhancement will not be used often, can it be worked around with a few lines of script?\nNot a small number of gdscript lines.\n\n\nIs there a reason why this should be core and done by us?\nI know how, and no one else is doing it.\n\n\nReferences\n\nV-Sekai\nSHARK\nIREE in-tree samples: https://github.com/openxla/iree/tree/main/samples\nIREE extra/more complex samples: https://github.com/iree-org/iree-samples\nIREE dynamic shapes sample: https://github.com/openxla/iree/tree/main/samples/dynamic_shapes\nIREE CPU/Vulkan/CUDA sample: https://github.com/openxla/iree/tree/main/samples/simple_embedding\nXLA axpy example: https://github.com/openxla/xla/tree/main/xla/examples/axpy\nnod.ai SHARK: https://github.com/nod-ai/SHARK\nnod.ai SHARK results on AMD GPUs using Vulkan: https://nod.ai/sd-rdna3-ces2023/"
   },
   {
-    "objectID": "decisions/20221016-v-sekai-view-replication.html#interpolation-function-from-godot-engine-4",
-    "href": "decisions/20221016-v-sekai-view-replication.html#interpolation-function-from-godot-engine-4",
-    "title": "Rejected: Use view replication algorithm for multiplayer multirelay sync",
+    "objectID": "decisions/20240330-cicd-gitlab.html",
+    "href": "decisions/20240330-cicd-gitlab.html",
+    "title": "Proposed: CI/CD Setup with Docker and Other Platforms",
     "section": "",
-    "text": "Note that this handles both nearest interpolation and cubic (with time) interpolation.\ntemplate &lt;class T&gt;\nT Animation::_interpolate(const Vector&lt;TKey&lt;T&gt;&gt; &p_keys, double p_time, InterpolationType p_interp, bool p_loop_wrap, bool *p_ok, bool p_backward) const {\n    int len = _find(p_keys, length) + 1; // try to find last key (there may be more past the end)\n\n    if (len &lt;= 0) {\n        // (-1 or -2 returned originally) (plus one above)\n        // meaning no keys, or only key time is larger than length\n        if (p_ok) {\n            *p_ok = false;\n        }\n        return T();\n    } else if (len == 1) { // one key found (0+1), return it\n\n        if (p_ok) {\n            *p_ok = true;\n        }\n        return p_keys[0].value;\n    }\n\n    int idx = _find(p_keys, p_time, p_backward);\n\n    ERR_FAIL_COND_V(idx == -2, T());\n\n    bool result = true;\n    int next = 0;\n    real_t c = 0.0;\n    // prepare for all cases of interpolation\n\n    if (loop_mode == LOOP_LINEAR && p_loop_wrap) {\n        // loop\n        if (!p_backward) {\n            // no backward\n            if (idx &gt;= 0) {\n                if (idx &lt; len - 1) {\n                    next = idx + 1;\n                    real_t delta = p_keys[next].time - p_keys[idx].time;\n                    real_t from = p_time - p_keys[idx].time;\n\n                    if (Math::is_zero_approx(delta)) {\n                        c = 0;\n                    } else {\n                        c = from / delta;\n                    }\n                } else {\n                    next = 0;\n                    real_t delta = (length - p_keys[idx].time) + p_keys[next].time;\n                    real_t from = p_time - p_keys[idx].time;\n\n                    if (Math::is_zero_approx(delta)) {\n                        c = 0;\n                    } else {\n                        c = from / delta;\n                    }\n                }\n            } else {\n                // on loop, behind first key\n                idx = len - 1;\n                next = 0;\n                real_t endtime = (length - p_keys[idx].time);\n                if (endtime &lt; 0) { // may be keys past the end\n                    endtime = 0;\n                }\n                real_t delta = endtime + p_keys[next].time;\n                real_t from = endtime + p_time;\n\n                if (Math::is_zero_approx(delta)) {\n                    c = 0;\n                } else {\n                    c = from / delta;\n                }\n            }\n        } else {\n            // backward\n            if (idx &lt;= len - 1) {\n                if (idx &gt; 0) {\n                    next = idx - 1;\n                    real_t delta = (length - p_keys[next].time) - (length - p_keys[idx].time);\n                    real_t from = (length - p_time) - (length - p_keys[idx].time);\n\n                    if (Math::is_zero_approx(delta)) {\n                        c = 0;\n                    } else {\n                        c = from / delta;\n                    }\n                } else {\n                    next = len - 1;\n                    real_t delta = p_keys[idx].time + (length - p_keys[next].time);\n                    real_t from = (length - p_time) - (length - p_keys[idx].time);\n\n                    if (Math::is_zero_approx(delta)) {\n                        c = 0;\n                    } else {\n                        c = from / delta;\n                    }\n                }\n            } else {\n                // on loop, in front of last key\n                idx = 0;\n                next = len - 1;\n                real_t endtime = p_keys[idx].time;\n                if (endtime &gt; length) { // may be keys past the end\n                    endtime = length;\n                }\n                real_t delta = p_keys[next].time - endtime;\n                real_t from = p_time - endtime;\n\n                if (Math::is_zero_approx(delta)) {\n                    c = 0;\n                } else {\n                    c = from / delta;\n                }\n            }\n        }\n    } else { // no loop\n        if (!p_backward) {\n            if (idx &gt;= 0) {\n                if (idx &lt; len - 1) {\n                    next = idx + 1;\n                    real_t delta = p_keys[next].time - p_keys[idx].time;\n                    real_t from = p_time - p_keys[idx].time;\n\n                    if (Math::is_zero_approx(delta)) {\n                        c = 0;\n                    } else {\n                        c = from / delta;\n                    }\n                } else {\n                    next = idx;\n                }\n            } else {\n                idx = next = 0;\n            }\n        } else {\n            if (idx &lt;= len - 1) {\n                if (idx &gt; 0) {\n                    next = idx - 1;\n                    real_t delta = (length - p_keys[next].time) - (length - p_keys[idx].time);\n                    real_t from = (length - p_time) - (length - p_keys[idx].time);\n\n                    if (Math::is_zero_approx(delta)) {\n                        c = 0;\n                    } else {\n                        c = from / delta;\n                    }\n\n                } else {\n                    next = idx;\n                }\n            } else {\n                idx = next = len - 1;\n            }\n        }\n    }\n\n    if (p_ok) {\n        *p_ok = result;\n    }\n    if (!result) {\n        return T();\n    }\n\n    real_t tr = p_keys[idx].transition;\n\n    if (tr == 0 || idx == next) {\n        // don't interpolate if not needed\n        return p_keys[idx].value;\n    }\n\n    if (tr != 1.0) {\n        c = Math::ease(c, tr);\n    }\n\n    switch (p_interp) {\n        case INTERPOLATION_NEAREST: {\n            return p_keys[idx].value;\n        } break;\n        case INTERPOLATION_LINEAR: {\n            return _interpolate(p_keys[idx].value, p_keys[next].value, c);\n        } break;\n        case INTERPOLATION_LINEAR_ANGLE: {\n            return _interpolate_angle(p_keys[idx].value, p_keys[next].value, c);\n        } break;\n        case INTERPOLATION_CUBIC:\n        case INTERPOLATION_CUBIC_ANGLE: {\n            int pre = 0;\n            int post = 0;\n            if (!p_backward) {\n                pre = idx - 1;\n                if (pre &lt; 0) {\n                    if (loop_mode == LOOP_LINEAR && p_loop_wrap) {\n                        pre = len - 1;\n                    } else {\n                        pre = 0;\n                    }\n                }\n                post = next + 1;\n                if (post &gt;= len) {\n                    if (loop_mode == LOOP_LINEAR && p_loop_wrap) {\n                        post = 0;\n                    } else {\n                        post = next;\n                    }\n                }\n            } else {\n                pre = idx + 1;\n                if (pre &gt;= len) {\n                    if (loop_mode == LOOP_LINEAR && p_loop_wrap) {\n                        pre = 0;\n                    } else {\n                        pre = idx;\n                    }\n                }\n                post = next - 1;\n                if (post &lt; 0) {\n                    if (loop_mode == LOOP_LINEAR && p_loop_wrap) {\n                        post = len - 1;\n                    } else {\n                        post = 0;\n                    }\n                }\n            }\n\n            real_t pre_t = 0.0;\n            real_t to_t = 0.0;\n            real_t post_t = 0.0;\n            if (loop_mode == LOOP_LINEAR && p_loop_wrap) {\n                pre_t = pre &gt; idx ? -length + p_keys[pre].time - p_keys[idx].time : p_keys[pre].time - p_keys[idx].time;\n                to_t = next &lt; idx ? length + p_keys[next].time - p_keys[idx].time : p_keys[next].time - p_keys[idx].time;\n                post_t = next &lt; idx || post &lt;= idx ? length + p_keys[post].time - p_keys[idx].time : p_keys[post].time - p_keys[idx].time;\n            } else {\n                pre_t = p_keys[pre].time - p_keys[idx].time;\n                to_t = p_keys[next].time - p_keys[idx].time;\n                post_t = p_keys[post].time - p_keys[idx].time;\n            }\n\n            if (p_interp == INTERPOLATION_CUBIC_ANGLE) {\n                return _cubic_interpolate_angle_in_time(\n                        p_keys[pre].value, p_keys[idx].value, p_keys[next].value, p_keys[post].value, c,\n                        pre_t, to_t, post_t);\n            }\n            return _cubic_interpolate_in_time(\n                    p_keys[pre].value, p_keys[idx].value, p_keys[next].value, p_keys[post].value, c,\n                    pre_t, to_t, post_t);\n        } break;\n        default:\n            return p_keys[idx].value;\n    }\n\n    // do a barrel roll\n}"
+    "text": "The V-Sekai project is focused on enhancing the Godot Engine by introducing social VR capabilities. To ensure a seamless development process across various environments, we need a robust CI/CD setup. This setup should cater to the diverse platforms our developers and contributors use, including Linux, macOS, Windows, Docker, and Kubernetes clusters.\n\n\n\nOur current CI/CD setup does not efficiently cover all operating systems and environments our developers use. This leads to inconsistent build and test results across different platforms. This inconsistency hinders our ability to rapidly develop and deploy features for the V-Sekai project.\n\n\n\nTo address this, we propose registering GitLab Runners for Linux, macOS, Windows, Docker, and Kubernetes. Each runner will be configured to handle builds and tests specific to its platform. Here’s a simplified view of how each runner would be set up:\nFor Linux, macOS, and Windows Runners:\n\nInstall GitLab Runner on the respective OS.\nUse the gitlab-runner register command with the platform-specific registration token.\nConfigure the runner to use an executor appropriate for the OS (e.g., shell for Linux/macOS, PowerShell for Windows).\n\nFor Docker Runner:\n\nInstall Docker on the host machine.\nPull the GitLab Runner Docker image.\nRun the GitLab Runner container with the Docker executor.\n\nFor Kubernetes Runner:\n\nDeploy the GitLab Runner Helm chart to the Kubernetes cluster.\nConfigure the runner to use the Kubernetes executor.\nUse a registration token from the GitLab instance to link the Kubernetes runner.\n\n\n\n\n\nConsistency Across Platforms: Ensures builds and tests are consistent across all supported platforms.\nIncreased Development Speed: Faster feedback loops for developers working on different platforms.\nScalability: Kubernetes runners can dynamically scale to handle increased loads, improving CI/CD pipeline performance.\n\n\n\n\n\nMaintenance Overhead: Requires initial setup and ongoing maintenance of runners across multiple platforms.\nComplexity: Adds complexity to the CI/CD setup, especially managing different executors and environments.\n\n\n\n\n\nRelying solely on cloud-based CI/CD services. While simpler, this would not provide the level of control and customization needed for our specific development needs.\n\n\n\n\n\nHandling builds or tests that require very specific environment configurations not commonly used by the development team. These cases might still need bespoke solutions outside the standard CI/CD pipeline.\n\n\n\n\nThis initiative is core to our mission of enhancing the Godot Engine with social VR capabilities. It will be executed by the V-Sekai development team, ensuring alignment with our project’s goals and technical standards.\n\n\n\nStatus: Proposed \n\n\n\n\nV-Sekai development team\n\n\n\n\n\nV-Sekai\n\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAssisted by Aria, your AI assistant."
   },
   {
-    "objectID": "decisions/20221016-v-sekai-view-replication.html#derivative-license",
-    "href": "decisions/20221016-v-sekai-view-replication.html#derivative-license",
-    "title": "Rejected: Use view replication algorithm for multiplayer multirelay sync",
+    "objectID": "decisions/20240330-cicd-gitlab.html#context",
+    "href": "decisions/20240330-cicd-gitlab.html#context",
+    "title": "Proposed: CI/CD Setup with Docker and Other Platforms",
     "section": "",
-    "text": "Copyright (c) 2022 V-Sekai contributors.\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\nTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
+    "text": "The V-Sekai project is focused on enhancing the Godot Engine by introducing social VR capabilities. To ensure a seamless development process across various environments, we need a robust CI/CD setup. This setup should cater to the diverse platforms our developers and contributors use, including Linux, macOS, Windows, Docker, and Kubernetes clusters."
   },
   {
-    "objectID": "changelog/2024/20240603-changelog.html",
-    "href": "changelog/2024/20240603-changelog.html",
-    "title": "V-Sekai Changelog - June 2024",
+    "objectID": "decisions/20240330-cicd-gitlab.html#problem-statement",
+    "href": "decisions/20240330-cicd-gitlab.html#problem-statement",
+    "title": "Proposed: CI/CD Setup with Docker and Other Platforms",
     "section": "",
-    "text": "Not applicable for this month.\n\n\n\n\n\n\n\nWorked on a pull request for motion blur, which included:\n\nPushing updates to the vsk-motion-blur-4.3-beta1 branch in the Godot repository.\n\nInitiated and updated a paint mixer spectral.js project in the world:main branch\nPushed an update to the mirror script at V-Sekai/avatar_vr_demo so it works in desktop mode as well as XR, and works at arbitrary aspect ratios. Thanks iFire for rubber duckying and encouraging me. Note that if you want square pixels and wish to use the screenspace mode, you need this commit V-Sekai/godot. However, it also supports using Godot’s builtin Frustum camera in non-screenspace mode where the pixels will be aligned along the plane of the mirror. See if you can spot the differences. (the skybox shader doesn’t fully support frustum mode)\nIntegrated OpenTelemetry into the codebase for enhanced debugging capabilities. This will allow developers to trace and monitor application performance in real-time, helping to identify and resolve issues more efficiently.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nBumped github/codeql-action from 3.25.6 to 3.25.7 for security best practices.\n\nThis project does not adhere to Semantic Versioning.\n\n\n\n\n\nNot applicable for this month."
+    "text": "Our current CI/CD setup does not efficiently cover all operating systems and environments our developers use. This leads to inconsistent build and test results across different platforms. This inconsistency hinders our ability to rapidly develop and deploy features for the V-Sekai project."
   },
   {
-    "objectID": "changelog/2024/20240603-changelog.html#released",
-    "href": "changelog/2024/20240603-changelog.html#released",
-    "title": "V-Sekai Changelog - June 2024",
+    "objectID": "decisions/20240330-cicd-gitlab.html#proposed-solution",
+    "href": "decisions/20240330-cicd-gitlab.html#proposed-solution",
+    "title": "Proposed: CI/CD Setup with Docker and Other Platforms",
     "section": "",
-    "text": "Not applicable for this month."
+    "text": "To address this, we propose registering GitLab Runners for Linux, macOS, Windows, Docker, and Kubernetes. Each runner will be configured to handle builds and tests specific to its platform. Here’s a simplified view of how each runner would be set up:\nFor Linux, macOS, and Windows Runners:\n\nInstall GitLab Runner on the respective OS.\nUse the gitlab-runner register command with the platform-specific registration token.\nConfigure the runner to use an executor appropriate for the OS (e.g., shell for Linux/macOS, PowerShell for Windows).\n\nFor Docker Runner:\n\nInstall Docker on the host machine.\nPull the GitLab Runner Docker image.\nRun the GitLab Runner container with the Docker executor.\n\nFor Kubernetes Runner:\n\nDeploy the GitLab Runner Helm chart to the Kubernetes cluster.\nConfigure the runner to use the Kubernetes executor.\nUse a registration token from the GitLab instance to link the Kubernetes runner."
   },
   {
-    "objectID": "changelog/2024/20240603-changelog.html#unreleased",
-    "href": "changelog/2024/20240603-changelog.html#unreleased",
-    "title": "V-Sekai Changelog - June 2024",
+    "objectID": "decisions/20240330-cicd-gitlab.html#benefits",
+    "href": "decisions/20240330-cicd-gitlab.html#benefits",
+    "title": "Proposed: CI/CD Setup with Docker and Other Platforms",
     "section": "",
-    "text": "Worked on a pull request for motion blur, which included:\n\nPushing updates to the vsk-motion-blur-4.3-beta1 branch in the Godot repository.\n\nInitiated and updated a paint mixer spectral.js project in the world:main branch\nPushed an update to the mirror script at V-Sekai/avatar_vr_demo so it works in desktop mode as well as XR, and works at arbitrary aspect ratios. Thanks iFire for rubber duckying and encouraging me. Note that if you want square pixels and wish to use the screenspace mode, you need this commit V-Sekai/godot. However, it also supports using Godot’s builtin Frustum camera in non-screenspace mode where the pixels will be aligned along the plane of the mirror. See if you can spot the differences. (the skybox shader doesn’t fully support frustum mode)\nIntegrated OpenTelemetry into the codebase for enhanced debugging capabilities. This will allow developers to trace and monitor application performance in real-time, helping to identify and resolve issues more efficiently.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nBumped github/codeql-action from 3.25.6 to 3.25.7 for security best practices.\n\nThis project does not adhere to Semantic Versioning."
+    "text": "Consistency Across Platforms: Ensures builds and tests are consistent across all supported platforms.\nIncreased Development Speed: Faster feedback loops for developers working on different platforms.\nScalability: Kubernetes runners can dynamically scale to handle increased loads, improving CI/CD pipeline performance."
   },
   {
-    "objectID": "changelog/2024/20240603-changelog.html#previous-releases",
-    "href": "changelog/2024/20240603-changelog.html#previous-releases",
-    "title": "V-Sekai Changelog - June 2024",
+    "objectID": "decisions/20240330-cicd-gitlab.html#downsides",
+    "href": "decisions/20240330-cicd-gitlab.html#downsides",
+    "title": "Proposed: CI/CD Setup with Docker and Other Platforms",
     "section": "",
-    "text": "Not applicable for this month."
+    "text": "Maintenance Overhead: Requires initial setup and ongoing maintenance of runners across multiple platforms.\nComplexity: Adds complexity to the CI/CD setup, especially managing different executors and environments."
   },
   {
-    "objectID": "changelog/2024/20240505-changelog.html",
-    "href": "changelog/2024/20240505-changelog.html",
-    "title": "V-Sekai Changelog - May 2024",
+    "objectID": "decisions/20240330-cicd-gitlab.html#alternatives-not-chosen",
+    "href": "decisions/20240330-cicd-gitlab.html#alternatives-not-chosen",
+    "title": "Proposed: CI/CD Setup with Docker and Other Platforms",
     "section": "",
-    "text": "Not applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\nWebRTC: Worked on browser and native webrtc interop. https://ifiregames.itch.io/webrtc-native-web-interoperability\nlibgodot: Worked on embedding libgodot to where it doesn’t belong.\ncsg: Update csg in Godot Engine to use Manifold.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nSecurity Best Practices:\n\nThis project does not adhere to Semantic Versioning.\n\n\n\n\n\nNot applicable for this month."
+    "text": "Relying solely on cloud-based CI/CD services. While simpler, this would not provide the level of control and customization needed for our specific development needs."
   },
   {
-    "objectID": "changelog/2024/20240505-changelog.html#released",
-    "href": "changelog/2024/20240505-changelog.html#released",
-    "title": "V-Sekai Changelog - May 2024",
+    "objectID": "decisions/20240330-cicd-gitlab.html#infrequent-use-case",
+    "href": "decisions/20240330-cicd-gitlab.html#infrequent-use-case",
+    "title": "Proposed: CI/CD Setup with Docker and Other Platforms",
     "section": "",
-    "text": "Not applicable for this month."
+    "text": "Handling builds or tests that require very specific environment configurations not commonly used by the development team. These cases might still need bespoke solutions outside the standard CI/CD pipeline."
   },
   {
-    "objectID": "changelog/2024/20240505-changelog.html#unreleased",
-    "href": "changelog/2024/20240505-changelog.html#unreleased",
-    "title": "V-Sekai Changelog - May 2024",
+    "objectID": "decisions/20240330-cicd-gitlab.html#in-core-and-done-by-us",
+    "href": "decisions/20240330-cicd-gitlab.html#in-core-and-done-by-us",
+    "title": "Proposed: CI/CD Setup with Docker and Other Platforms",
     "section": "",
-    "text": "Not applicable for this month.\n\n\n\n\nWebRTC: Worked on browser and native webrtc interop. https://ifiregames.itch.io/webrtc-native-web-interoperability\nlibgodot: Worked on embedding libgodot to where it doesn’t belong.\ncsg: Update csg in Godot Engine to use Manifold.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nSecurity Best Practices:\n\nThis project does not adhere to Semantic Versioning."
+    "text": "This initiative is core to our mission of enhancing the Godot Engine with social VR capabilities. It will be executed by the V-Sekai development team, ensuring alignment with our project’s goals and technical standards."
   },
   {
-    "objectID": "changelog/2024/20240505-changelog.html#previous-releases",
-    "href": "changelog/2024/20240505-changelog.html#previous-releases",
-    "title": "V-Sekai Changelog - May 2024",
+    "objectID": "decisions/20240330-cicd-gitlab.html#status",
+    "href": "decisions/20240330-cicd-gitlab.html#status",
+    "title": "Proposed: CI/CD Setup with Docker and Other Platforms",
     "section": "",
-    "text": "Not applicable for this month."
+    "text": "Status: Proposed"
   },
   {
-    "objectID": "changelog/2024/20240330-changelog.html",
-    "href": "changelog/2024/20240330-changelog.html",
-    "title": "V-Sekai Changelog - March 2024",
+    "objectID": "decisions/20240330-cicd-gitlab.html#decision-makers",
+    "href": "decisions/20240330-cicd-gitlab.html#decision-makers",
+    "title": "Proposed: CI/CD Setup with Docker and Other Platforms",
     "section": "",
-    "text": "Not applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\nGDC Demo: We attended the Game Developers Conference (GDC) in San Francisco, California, USA. We demonstrated the capabilities of the Godot Engine on an Android tablet.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nSecurity Best Practices:\n\nThis project does not adhere to Semantic Versioning.\n\n\n\n\n\nNot applicable for this month."
+    "text": "V-Sekai development team"
   },
   {
-    "objectID": "changelog/2024/20240330-changelog.html#released",
-    "href": "changelog/2024/20240330-changelog.html#released",
-    "title": "V-Sekai Changelog - March 2024",
+    "objectID": "decisions/20240330-cicd-gitlab.html#tags",
+    "href": "decisions/20240330-cicd-gitlab.html#tags",
+    "title": "Proposed: CI/CD Setup with Docker and Other Platforms",
     "section": "",
-    "text": "Not applicable for this month."
+    "text": "V-Sekai"
   },
   {
-    "objectID": "changelog/2024/20240330-changelog.html#unreleased",
-    "href": "changelog/2024/20240330-changelog.html#unreleased",
-    "title": "V-Sekai Changelog - March 2024",
+    "objectID": "decisions/20240330-cicd-gitlab.html#further-reading",
+    "href": "decisions/20240330-cicd-gitlab.html#further-reading",
+    "title": "Proposed: CI/CD Setup with Docker and Other Platforms",
     "section": "",
-    "text": "Not applicable for this month.\n\n\n\n\nGDC Demo: We attended the Game Developers Conference (GDC) in San Francisco, California, USA. We demonstrated the capabilities of the Godot Engine on an Android tablet.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nSecurity Best Practices:\n\nThis project does not adhere to Semantic Versioning."
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAssisted by Aria, your AI assistant."
   },
   {
-    "objectID": "changelog/2024/20240330-changelog.html#previous-releases",
-    "href": "changelog/2024/20240330-changelog.html#previous-releases",
-    "title": "V-Sekai Changelog - March 2024",
+    "objectID": "decisions/20231229-byobu.html",
+    "href": "decisions/20231229-byobu.html",
+    "title": "Proposed: Byobu terminal multiplexer",
     "section": "",
-    "text": "Not applicable for this month."
+    "text": "Status: Proposed \nDeciders: V-Sekai\nTags: V-Sekai\n\n\n\n\nIn the world of software development, having a robust and user-friendly terminal environment is crucial. Developers often need to manage multiple terminal sessions at once, which can be challenging without the right tools.\n\n\n\nThe challenge is to find a usable terminal multiplexer that can handle multiple terminal sessions efficiently and effectively.\n\n\n\nOur strategy is to use Byobu, a GPLv3 open source text-based window manager and terminal multiplexer. It was chosen for its ease of use and robust feature set.\n\n\n\nBy using Byobu, developers can easily manage multiple terminal sessions from a single interface. This can greatly improve productivity and efficiency.\n\n\n\nAs with any tool, there may be a learning curve associated with Byobu. However, its benefits far outweigh this minor inconvenience.\n\n\n\nOther options like Screen and tmux were considered but found not as user friendly. Tmux, in particular, didn’t correctly scroll and did not advertise the option to start on terminal.\n\n\n\nWhile Byobu is an excellent tool for managing multiple terminal sessions, it may not be necessary for developers who only occasionally need to work with multiple terminals.\n\n\n\nThis decision to use Byobu is part of our core strategy to provide the best tools and environment for our developers.\n\n\n\n\nV-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "changelog/2024/20240202-changelog.html",
-    "href": "changelog/2024/20240202-changelog.html",
-    "title": "V-Sekai Changelog - February 2024",
+    "objectID": "decisions/20231229-byobu.html#metadata",
+    "href": "decisions/20231229-byobu.html#metadata",
+    "title": "Proposed: Byobu terminal multiplexer",
     "section": "",
-    "text": "Not applicable for this month.\n\n\n\n\n\n\n\nUFBX Importer: Merged into Godot Engine master for version 4.3.\nUnidot Spring Bones: Spring bones now import with Unidot Importer! It’s compatible with various popular formats and supports all features of the vrm spring bone script. Currently no advanced features like axis locks or inside colliders. While the vrm script supports curves, Unity curve sampling has not been implemented yet, so each bone in the chain imports with a constant value.\ngodot-vrm: An update to godot-vrm on git has been pushed to make it easier and more straightforward to edit spring bones in the inspector.\nUnidot: A lot of bugfixes have been made to the VRM import/export, unidot import pipeline, and springbone support. It’s becoming a lot easier to import a set of assets from unitypackage including booth outfits, attach them, and then export a VRM with functional spring bones!\nGodot FBX Importer: ArchVizPro volume 6 imported with ufbx. The importer is exceptionally good, and during testing it appears to perfectly replicate the result obtained in the autodesk SDK. This means Unidot in Godot 4.3 will be able to import directly to fbx out of the box without having to go through gltf!\ngodot-whisper: Added support for real-time audio transcription within the Godot Engine, which includes enhanced compatibility for the Metal API on Apple devices and improved threading performance. (Commit: 2d85a0e update)\ngodot-steamaudio: Updated the Steam Audio integration by refactoring the build configuration and audio stream handling process. (Commit: 8f15de1 Refactor build configuration)\n\n\n\n\n\nRemove a V-Sekai-game github release and point to https://saracenone.itch.io/groups-4x\n\n\n\n\n\n2024-02-07: There was a nasty bug involving the springbone gizmo, a node rename, and a Godot bug that would corrupt the node if replace_by was called on an internal node (such as a gizmo) that was leading random meshes to disappear in godot vrm during import. Should be fixed now!\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nSecurity Best Practices:\nThis project does not adhere to Semantic Versioning.\n\n\n\n\n\n\nNot applicable for this month."
+    "text": "Status: Proposed \nDeciders: V-Sekai\nTags: V-Sekai"
   },
   {
-    "objectID": "changelog/2024/20240202-changelog.html#released",
-    "href": "changelog/2024/20240202-changelog.html#released",
-    "title": "V-Sekai Changelog - February 2024",
+    "objectID": "decisions/20231229-byobu.html#the-backdrop",
+    "href": "decisions/20231229-byobu.html#the-backdrop",
+    "title": "Proposed: Byobu terminal multiplexer",
     "section": "",
-    "text": "Not applicable for this month."
+    "text": "In the world of software development, having a robust and user-friendly terminal environment is crucial. Developers often need to manage multiple terminal sessions at once, which can be challenging without the right tools."
   },
   {
-    "objectID": "changelog/2024/20240202-changelog.html#unreleased",
-    "href": "changelog/2024/20240202-changelog.html#unreleased",
-    "title": "V-Sekai Changelog - February 2024",
+    "objectID": "decisions/20231229-byobu.html#the-challenge",
+    "href": "decisions/20231229-byobu.html#the-challenge",
+    "title": "Proposed: Byobu terminal multiplexer",
     "section": "",
-    "text": "UFBX Importer: Merged into Godot Engine master for version 4.3.\nUnidot Spring Bones: Spring bones now import with Unidot Importer! It’s compatible with various popular formats and supports all features of the vrm spring bone script. Currently no advanced features like axis locks or inside colliders. While the vrm script supports curves, Unity curve sampling has not been implemented yet, so each bone in the chain imports with a constant value.\ngodot-vrm: An update to godot-vrm on git has been pushed to make it easier and more straightforward to edit spring bones in the inspector.\nUnidot: A lot of bugfixes have been made to the VRM import/export, unidot import pipeline, and springbone support. It’s becoming a lot easier to import a set of assets from unitypackage including booth outfits, attach them, and then export a VRM with functional spring bones!\nGodot FBX Importer: ArchVizPro volume 6 imported with ufbx. The importer is exceptionally good, and during testing it appears to perfectly replicate the result obtained in the autodesk SDK. This means Unidot in Godot 4.3 will be able to import directly to fbx out of the box without having to go through gltf!\ngodot-whisper: Added support for real-time audio transcription within the Godot Engine, which includes enhanced compatibility for the Metal API on Apple devices and improved threading performance. (Commit: 2d85a0e update)\ngodot-steamaudio: Updated the Steam Audio integration by refactoring the build configuration and audio stream handling process. (Commit: 8f15de1 Refactor build configuration)\n\n\n\n\n\nRemove a V-Sekai-game github release and point to https://saracenone.itch.io/groups-4x\n\n\n\n\n\n2024-02-07: There was a nasty bug involving the springbone gizmo, a node rename, and a Godot bug that would corrupt the node if replace_by was called on an internal node (such as a gizmo) that was leading random meshes to disappear in godot vrm during import. Should be fixed now!\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nSecurity Best Practices:\nThis project does not adhere to Semantic Versioning."
+    "text": "The challenge is to find a usable terminal multiplexer that can handle multiple terminal sessions efficiently and effectively."
   },
   {
-    "objectID": "changelog/2024/20240202-changelog.html#previous-releases",
-    "href": "changelog/2024/20240202-changelog.html#previous-releases",
-    "title": "V-Sekai Changelog - February 2024",
+    "objectID": "decisions/20231229-byobu.html#the-strategy",
+    "href": "decisions/20231229-byobu.html#the-strategy",
+    "title": "Proposed: Byobu terminal multiplexer",
     "section": "",
-    "text": "Not applicable for this month."
+    "text": "Our strategy is to use Byobu, a GPLv3 open source text-based window manager and terminal multiplexer. It was chosen for its ease of use and robust feature set."
   },
   {
-    "objectID": "changelog/2024/20241003-changelog.html",
-    "href": "changelog/2024/20241003-changelog.html",
-    "title": "V-Sekai Changelog - October 2024",
+    "objectID": "decisions/20231229-byobu.html#the-upside",
+    "href": "decisions/20231229-byobu.html#the-upside",
+    "title": "Proposed: Byobu terminal multiplexer",
     "section": "",
-    "text": "Experimental (🧪): This stage is for features that are still being tested and may not be stable.\nFeature complete (🎯): This stage is for features that have all planned functionality implemented.\nBeta (🚧): This stage is for features that are largely complete but may still have bugs.\nGeneral release (🚀): This stage is for features that have been fully tested and are now released.\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\n\n\n🎯 https://gonzerelli.itch.io/demo - fwsgonzo decided to embed LuaJIT to Godot Sandbox as a proof-of-concept. Touching the first coin will open up a Lua “console” which redirects print() to a TextEdit\n🎯 https://gonzerelli.itch.io/demo - We enabled binary translation for LuaJIT on Godot Sandbox.\n🚀 Installed Discord on the Meta Quest 3 and was able to stream Godot Engine and ecosystem applications.\n🎯 Added a double build of steam audio\n🎯 Steam Audio now works without a custom Godot Engine fork.\n🧪 The VRM Consortium, Inc., the creator and advocate of the VRM 3D avatar file format, which is based on the glTF™ 2.0 open standard, has announced a collaboration with The Khronos Group, the developer of glTF, to advance the international standardization of VRM.\n🚀 Submitted IREE.gd to Awesome-Godot-Scientific\n🧪 Collaboration with GuilhermeGSousa/godot-motion-matching\n🚀 Found opensource animation assets. Useful bases for retargeting and also stylizing motions. O3DE MotionMatching Animation Assets\n🧪 Collaboration with maiself/godot-python-extension\n🧪 Split V-Sekai world into world_editor and world_game\n\n\n\n\n\n🚧 Try to release iree-gd for godot engine 4.3 stable. https://github.com/iree-gd/iree.gd/pull/87\n🧪 Cleanup 3d cage for porting to python. https://github.com/V-Sekai-fire/godot_cage_deformer\n🚧 Updated manifold to remove GLM - https://github.com/godotengine/godot/pull/94321\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nSecurity Best Practices:\n\nThis project does not adhere to Semantic Versioning.\n\n\n\n\n\nNot applicable for this month."
+    "text": "By using Byobu, developers can easily manage multiple terminal sessions from a single interface. This can greatly improve productivity and efficiency."
   },
   {
-    "objectID": "changelog/2024/20241003-changelog.html#released",
-    "href": "changelog/2024/20241003-changelog.html#released",
-    "title": "V-Sekai Changelog - October 2024",
+    "objectID": "decisions/20231229-byobu.html#the-downside",
+    "href": "decisions/20231229-byobu.html#the-downside",
+    "title": "Proposed: Byobu terminal multiplexer",
     "section": "",
-    "text": "Not applicable for this month."
+    "text": "As with any tool, there may be a learning curve associated with Byobu. However, its benefits far outweigh this minor inconvenience."
   },
   {
-    "objectID": "changelog/2024/20241003-changelog.html#unreleased",
-    "href": "changelog/2024/20241003-changelog.html#unreleased",
-    "title": "V-Sekai Changelog - October 2024",
+    "objectID": "decisions/20231229-byobu.html#the-road-not-taken",
+    "href": "decisions/20231229-byobu.html#the-road-not-taken",
+    "title": "Proposed: Byobu terminal multiplexer",
     "section": "",
-    "text": "🎯 https://gonzerelli.itch.io/demo - fwsgonzo decided to embed LuaJIT to Godot Sandbox as a proof-of-concept. Touching the first coin will open up a Lua “console” which redirects print() to a TextEdit\n🎯 https://gonzerelli.itch.io/demo - We enabled binary translation for LuaJIT on Godot Sandbox.\n🚀 Installed Discord on the Meta Quest 3 and was able to stream Godot Engine and ecosystem applications.\n🎯 Added a double build of steam audio\n🎯 Steam Audio now works without a custom Godot Engine fork.\n🧪 The VRM Consortium, Inc., the creator and advocate of the VRM 3D avatar file format, which is based on the glTF™ 2.0 open standard, has announced a collaboration with The Khronos Group, the developer of glTF, to advance the international standardization of VRM.\n🚀 Submitted IREE.gd to Awesome-Godot-Scientific\n🧪 Collaboration with GuilhermeGSousa/godot-motion-matching\n🚀 Found opensource animation assets. Useful bases for retargeting and also stylizing motions. O3DE MotionMatching Animation Assets\n🧪 Collaboration with maiself/godot-python-extension\n🧪 Split V-Sekai world into world_editor and world_game\n\n\n\n\n\n🚧 Try to release iree-gd for godot engine 4.3 stable. https://github.com/iree-gd/iree.gd/pull/87\n🧪 Cleanup 3d cage for porting to python. https://github.com/V-Sekai-fire/godot_cage_deformer\n🚧 Updated manifold to remove GLM - https://github.com/godotengine/godot/pull/94321\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nSecurity Best Practices:\n\nThis project does not adhere to Semantic Versioning."
+    "text": "Other options like Screen and tmux were considered but found not as user friendly. Tmux, in particular, didn’t correctly scroll and did not advertise the option to start on terminal."
   },
   {
-    "objectID": "changelog/2024/20241003-changelog.html#previous-releases",
-    "href": "changelog/2024/20241003-changelog.html#previous-releases",
-    "title": "V-Sekai Changelog - October 2024",
+    "objectID": "decisions/20231229-byobu.html#the-infrequent-use-case",
+    "href": "decisions/20231229-byobu.html#the-infrequent-use-case",
+    "title": "Proposed: Byobu terminal multiplexer",
     "section": "",
-    "text": "Not applicable for this month."
+    "text": "While Byobu is an excellent tool for managing multiple terminal sessions, it may not be necessary for developers who only occasionally need to work with multiple terminals."
   },
   {
-    "objectID": "changelog/2021/20210901-changelog.html",
-    "href": "changelog/2021/20210901-changelog.html",
-    "title": "V-Sekai Changelog - 2021-09",
+    "objectID": "decisions/20231229-byobu.html#in-core-and-done-by-us",
+    "href": "decisions/20231229-byobu.html#in-core-and-done-by-us",
+    "title": "Proposed: Byobu terminal multiplexer",
     "section": "",
-    "text": "V-Sekai Changelog - 2021-09\n\n2021-09-30 18:33:19Z fire: Saracen https://github.com/godotengine/godot/pull/52210 https://cdn.discordapp.com/attachments/836651615532482611/893203877367779408/unknown.png\n2021-09-30 01:28:33Z fire: https://www.youtube.com/watch?v=Dp42lQYVzwo&t=47s\n2021-09-29 22:12:20Z fire: Holoplay initial commit https://github.com/CaptainProton42/GodotHoloPlayExtension\n2021-09-29 22:08:01Z fire: “Fales 12:31 PM Okay peeps, I got the WebRTC plugin for 4.0 to build on all platforms (and most architectures): https://github.com/Faless/webrtc-native/actions/runs/1288153747 .” 👍 (1)\n2021-09-29 21:39:33Z fire: Closed 6 bugs related to 53114\n2021-09-29 21:03:56Z fire: https://github.com/godotengine/godot/pull/53114 Merged\n2021-09-29 20:23:20Z lyuma: “Posted the glTF export bugfix for review. Fixes blend shapes, skeletons and nested bone attachment hierarchies: https://github.com/godotengine/godot/pull/53114”\n2021-09-29 10:10:12Z lyuma: Successfully exported a glTF model with multiple surfaces and blend shapes: https://cdn.discordapp.com/attachments/836651615532482611/892714872012406794/unknown.png kickass (2)\n2021-09-28 22:34:20Z fire:  has entered the discussion\n2021-09-28 22:33:40Z fire: Spent some time at OMIGROUP discussing OMI-WASM-ECS\n2021-09-28 16:33:48Z fire: https://twitter.com/mux213/status/1442820373322420224?s=20 😎 (2)\n2021-09-28 16:25:34Z fire: Updated https://github.com/V-Sekai/godot/tree/export_skin_fixes to master\n2021-09-27 21:24:18Z fire: &gt; From reduz all would you be up for an animation meeting tomorrow?\n2021-09-27 19:30:01Z fire: point to child and point to global as a skeleton modifier. just dreamed this. Per frame 😱\n2021-09-27 17:03:16Z fire: https://github.com/GodotVR/godot_xr_reference\n2021-09-27 15:31:37Z lyuma: “Nice blog post by Mux about GDExtension! A good read: https://godotengine.org/article/introducing-gd-extensions Maybe we can try making one of these for VRM springbone” 👍 (2)\n2021-09-27 14:32:29Z fire: Wrote down a bake miku miku motion workflow. With a rebased 3.x (not 3.3) we can export the baked scene with a manual step to delete the face / blendshapes. Remember to copy both the reset and the transferred anim. Then in 4.0 import and put it on the original vrm. Enable RESET bake.\n2021-09-27 14:26:53Z fire: Reviewed godot-tests pr and had some comments. Added a comment to fix export of skeletons and skins. Tested the export more. Noted a weird issue where if the blend was animated it would cause the blend shape to be exported wrong. Like a shape mouth blend set to 1.0 and looking in blender\n2021-09-27 14:25:36Z fire: Approved gltf2 making light activate again. Discussed IK with Eron and on VRM rests.\n2021-09-27 12:51:50Z fire: I exported the scene from your pr. Testing it with joy set to 1. https://cdn.discordapp.com/attachments/836651615532482611/892030776210780210/unknown.png\n2021-09-27 07:18:36Z fire: godot-tests? ✅ (1)\n2021-09-27 07:18:31Z fire: Lyuma want to add cursed hat to the models repo?\n2021-09-27 07:01:50Z lyuma: Pushed pull request https://github.com/godotengine/godot/pull/53114 to address gltf skin and skeleton objects being generated at the wrong time during the export process. Still in draft state because it needs more testing.\n2021-09-26 11:28:12Z Saracen: https://github.com/godotengine/godot/pull/53086 🐱 (2)\n2021-09-24 18:21:54Z fire: Ellenhp discussion about HRTF audio in the audio channel in chat.godotengine.org.\n2021-09-24 14:59:37Z fire: Good news everyone. https://twitter.com/yunayuna64/status/1441288908659048453\n2021-09-23 22:43:33Z lyuma: “Just resolved yet another server downtime. It was down overnight because I was unavailable to investigate due to an appointment. Cause for failure: Fedora (without NetworkManager?) defaults to non-daemonized dhclient and allowed the dhcp lease to expire.\n\nTo prevent future disruption, I have implemented both mitigations outlined in this helpful ServerFault answer! https://serverfault.com/a/291202 regrets_for_not_using_ubuntu++;”\n\n2021-09-23 21:28:31Z fire: https://github.com/V-Sekai/godot-vrm/issues/23 👍 (1)\n2021-09-23 09:02:30Z lyuma: in terms of ui, is VisualScript good?\n2021-09-23 09:02:13Z lyuma: “co-opting this channel to discuss the AnimationTree draft proposal &gt; https://docs.google.com/document/d/1mkGjnj8VzCJmZS2x6l6qMVvemylGR2OPYq4hF-sTPRI/edit?usp=sharing\n\nI think the overall design is great. we are wondering how to configure the variables”\n\n2021-09-22 19:42:40Z fire: VMD to VRM Dance https://cdn.discordapp.com/attachments/836651615532482611/890322222042976286/2021-09-22_12-03-13.mp4 👍 (3)\n2021-09-21 01:25:13Z fire: First draft of new updated extensions api. https://github.com/godotengine/godot/pull/52802 Lyuma\n2021-09-20 23:21:50Z lyuma: Cool\n2021-09-20 23:19:13Z fire: Chatted with Robert. Proposed design to do the import_node and import_scene APIs as a first pass for the OMI_audio_emitter extension. Can fallback to post hook.\n2021-09-20 22:44:46Z lyuma: ImporterMeshInstance3D. Nice that is moving out of the Editor namespace, and less typing\n2021-09-20 22:44:11Z fire: https://cdn.discordapp.com/attachments/836651615532482611/889643129525907546/unknown.png\n2021-09-20 19:50:39Z fire: gltfdocument extensions works I think. next steps 1) review 2) merge 3) update godot-vrm. for now. khajit needs food\n2021-09-20 19:31:58Z fire: false success &gt;.&gt;\n2021-09-20 16:57:12Z fire: &gt; reduz: it should only check whether its the same for vertex, normal and tangent\n2021-09-20 12:26:23Z fire: openvr\n2021-09-20 12:26:06Z fire: and after you compile it make sure you create a new extensions_api.json and copy the gdnative_extensions.h file into the godot-cpp of the plugin\n2021-09-20 12:25:53Z fire: https://github.com/BastiaanOlij/godot/tree/xr_extension_return_buffers\n2021-09-19 04:43:53Z fire: Contacted moody he wanted to get scons ninja and scons shared libraries done. there are new prs needing review\n2021-09-19 04:33:10Z fire: Lots of headless crash bugs\n2021-09-19 04:13:07Z fire: https://cdn.discordapp.com/attachments/836651615532482611/889001129877340160/unknown.png 😩 (1)\n2021-09-19 03:23:59Z fire: Next up. rebuild GDExtension Openvr\n2021-09-19 03:18:41Z fire: Spending some time checking CICD still works. Updated misc. See logs on pipeline https://github.com/V-Sekai/groups-gocd-pipelines/\n2021-09-18 19:32:11Z lyuma: “Updated cluster install directions to account for the recent changes seeing remote ip; cockroachdb not from helm; and disabling eviction: https://github.com/V-Sekai/v-sekai-proposals/blob/master/docs/decisions/20200602-manage-backend-with-k3s.md”\n2021-09-18 18:48:46Z lyuma: “Our server was down for 4 hours due to a kubernetes misconfiguration (one of the options was reverted to default by mistake when changing the network metallb options):\n\nTo correct, I edited /etc/systemd/system/k3s.service and changed the ExecStart lines to:\nExecStart=/usr/local/bin/k3s \\\n    server \\\n        '-o' \\\n        '/root/.kube/config' \\\n        '--default-local-storage-path' \\\n        '/kube/pvc' \\\n        '--disable=traefik' \\\n        '--disable=servicelb' \\\n        '--disable=flannel' \\\n        '--disable=cni' \\\n        '--kubelet-arg=eviction-soft=memory.available&lt;0%,imagefs.available&lt;0%,nodefs.available&lt;0%' \\\n        '--kubelet-arg=eviction-hard=memory.available&lt;0%,imagefs.available&lt;0%,nodefs.available&lt;0%' \\\n\n2021-09-18 12:41:48Z fire: “&gt; WOW…. workarounds galore and its not pretty, and it crashes badly when you exit Godot, but OpenVR is breathing life and renders to the headset now. That means that the system at its core is working and we’re now at a stage of fixing bugs (well I still need to finish the changes to controllers).\n\n\nFor OpenXR there is far more work to do because there currently isn’t any support for rendering to texture chains supplied by the plugin and I’m only about halfway through converting all the code. I plan to do more on that conversion tomorrow as I wait for things to be fixed in Godot before I can take the next steps with OpenVR.”\n\n\n2021-09-18 12:41:23Z fire: &gt; mux\n2021-09-18 03:58:34Z fire: https://github.com/godotengine/godot/pull/52802\n2021-09-18 01:04:23Z fire: https://cdn.discordapp.com/attachments/836651615532482611/888591247835541584/unknown.png\n2021-09-18 01:04:19Z fire: first draft design of GLT2DocumentExtensionEditor\n2021-09-17 07:07:15Z fire: https://twitter.com/VR_Rosie/status/1438600868245426180?s=20\n2021-09-16 16:24:13Z fire: Added https://github.com/godotengine/godot-proposals/issues/3305 and updated https://github.com/godotengine/godot-proposals/issues/3273\n2021-09-16 06:28:45Z fire: “Lyuma Saracen When I wake up tomorrow I’m going to be hyped and implement https://hackmd.io/37S0FGw7TruwjiLIspl8vQ. I think the proposal is ready to go. Please read and comment.”\n2021-09-15 15:58:29Z fire: https://twitter.com/bjornornorn/status/1435607551031357443?s=20 🆗 (1)\n2021-09-15 15:57:26Z fire: “Having fun with shaders, but gotta go do errands. Trying to make the circle fit the box. Might need some help https://github.com/V-Sekai/godot/tree/ok_color”\n2021-09-15 15:57:09Z fire: https://cdn.discordapp.com/attachments/836651615532482611/887728757702537247/unknown.png\n2021-09-15 00:43:01Z fire: Devise a workflow for https://github.com/godotengine/godot/pull/49775#issuecomment-919608377\n2021-09-14 18:23:20Z fire: https://hackmd.io/37S0FGw7TruwjiLIspl8vQ\n2021-09-14 17:18:20Z fire: &gt; Discussion this morning with Reduz to unify the Ref&lt;GLTFDocument&gt; api. &gt; &gt; - load_file(), load_buffer() that just generates the internal state, and save_file and save_buffer functions that save back the files. &gt; - parse_scene(Node*) generates the internal state from a Node* scene. And Node* write_scene() writes it out &gt; &gt; Expose a Vector&lt;Ref&lt;GLTFDocumentExtension&gt;&gt;”\n2021-09-14 17:17:39Z fire: https://github.com/godotengine/godot/pull/52541#issuecomment-919353368 Lyuma, Saracen, MMMaellon, Silent. Feedback requested on GLTFDocument api.\n2021-09-14 07:23:22Z fire: Four Godot 4 prs on my list – 1) libcurl complete the pr and not be at 98% 2) core based gltf i/o 3) svg 4) cvtt\n2021-09-13 22:44:02Z fire: https://cdn.discordapp.com/attachments/836651615532482611/887106377716224000/2021-09-13_15-42-22.mp4 👏 (4)\n2021-09-13 22:33:29Z fire: https://github.com/TwistedTwigleg/Godot_GSOC_2020_Project/tree/IK_Modification_Fix Updated Skeleton Modifier example code Saracen\n2021-09-13 19:07:30Z fire: Put https://github.com/godotengine/godot/pull/52541 for review again.\n2021-09-13 19:07:11Z fire: Godot Meson updates https://github.com/godotengine/godot/pull/52311#issuecomment-918474496\n2021-09-13 11:08:54Z fire: “Contacted Eron and sent demo materials. https://ifiregames.itch.io/chibifire-godot-4-custom-engine https://github.com/V-Sekai/godot-ik-tests”\n2021-09-13 11:08:14Z fire: Can’t sleep so updated the skeleton modification demo https://github.com/godotengine/godot-demo-projects/issues/649\n2021-09-11 17:59:00Z fire: Eron was interested in ewbik on sunday\n2021-09-11 16:37:08Z fire: https://github.com/V-Sekai/godot-vrm/issues/22\n2021-09-11 16:32:05Z fire: Lyuma I updated godot engine to remove PackedSceneGLTF. The changes will be posted in a bit for godot-vrm\n2021-09-09 17:50:45Z fire: 👀 https://www.vrfocus.com/2021/09/ray-ban-stories-is-facebooks-299-entry-into-the-smart-glasses-market/\n2021-09-08 17:24:52Z fire: Lyuma Saracen from reduz &gt; fire it looks good. We got quite a lot of demand to make the GLTF importer part of core, given it is needed for VR and other stuff, so I have the feeling we should optimize it for performance (which we should do anyway) and have an option to load actual meshes instead of EditorImporterMesh.. so that means we would need to provide a function to parse the mesh node into a scene node and the editor supplies, otherwise it uses Mesh as a default\n2021-09-07 18:32:54Z fire: Miku Base Textures https://cdn.discordapp.com/attachments/836651615532482611/884868837978288178/unknown.png\n2021-09-07 18:02:00Z fire: Miku Miku Dance now split into materials. https://cdn.discordapp.com/attachments/836651615532482611/884861074648760380/unknown.png 👍 (2)\n2021-09-07 16:39:33Z トカゲ: “fixed skinning https://github.com/godotengine/godot/pull/52462”\n2021-09-07 05:53:14Z fire: https://cdn.discordapp.com/attachments/836651615532482611/884677671563460639/unknown.png\n2021-09-07 02:10:09Z fire: Trying to write down steps to make a V-Sekai/godot update\n2021-09-06 00:25:10Z fire: https://cdn.discordapp.com/attachments/836651615532482611/884232728839606284/kaitai_mmd_pmx.zip\n2021-09-06 00:24:45Z fire: https://github.com/kaitai-io/kaitai_struct_formats/pull/446 Lyuma Thanks to Hakanai I can now generate mmd_pmx c++/stl via & 'C:\\Program Files (x86)\\kaitai-struct-compiler\\bin\\kaitai-struct-compiler.bat' --cpp-standard=11 --target=cpp_stl .\\3d\\mmd_pmx.ksy -I=. --cpp-namespace kaitai_mmd_pmx Also glb binary has a parser for read and write too. Can also do fbx!?!!!! Also tscn, scn, tres and res mikuleek (3)\n2021-09-06 00:09:07Z トカゲ: “Child class of EditorProperty’s read_only property has been implemented correctly https://github.com/godotengine/godot/pull/51722” https://cdn.discordapp.com/attachments/836651615532482611/884228687992594482/2021-09-06_9.07.35-1.mov 👍 (2)\n2021-09-04 02:10:44Z fire: GLTF Skeletons\n2021-09-04 01:30:12Z lyuma: We found an infinite recursion bug in the godot gltf exporter caused by the construction of gltf node objects from skeletons and skins. I believe the issue is treating skeletons as special objects, and if we expand skeleton bones to nodes initially that should simplify things greatly and prevent this type of bug.\n2021-09-03 22:23:17Z fire: use vnen’s fix to replace saracen’s auto load fix\n2021-09-03 15:36:00Z fire: If you were crashing Godot Engine when opening vrms, it’s a Nvidia driver bug. Please update.\n2021-09-03 08:10:01Z lyuma: This was all imported using Unidot on godot 4.x (with progress bar patch :-p)\n2021-09-03 08:09:11Z lyuma: https://cdn.discordapp.com/attachments/836651615532482611/883262336243216424/rin_himeji_lineup.png FeaturingDanteFromTheDevilMayCry (1)\n2021-09-03 08:09:06Z lyuma: Fixed material searching logic for legacy materials. There are some issues with material ordering, but most scenes now import with the correct materials! https://cdn.discordapp.com/attachments/836651615532482611/883262312969011250/rin_himeji_diorama2.png\n2021-09-03 08:08:15Z lyuma: https://cdn.discordapp.com/attachments/836651615532482611/883262098942079026/archery_sample.png\n2021-09-02 03:56:26Z lyuma: “Progress on Unidot Importer: I made some major fixes on binary asset deserialization: I finally figured out how padding works (short answer: flag 0x4000 adds padding after a byte or short), and fixed a crash by implementing support for Unity 4.x and earlier assets, since you never know where they will show up.\n\nNext up is parsing the texture filename mapping from FBX files to assist in material discovery, since Unity legacy materials default to lookup by texture filename rather than material name or texture name. Since Godot has no means for preserving the original filename on import when the files are not present, doing a fix to the FBX2glTF tool won’t quite cover my necessary usecase, so I think extracting the map in the tooling is easiest. Will probably revisit this decision later.” 👍 (4)\n\n2021-09-02 01:27:40Z fire: https://twitter.com/babylonjs/status/1433216048036122629?s=20 webgpu\n2021-09-01 21:26:59Z fire: \n2021-09-01 15:39:17Z fire: Tried to get additional screenshots to work https://github.com/godotengine/godot/pull/52316\n2021-09-01 14:53:33Z fire: Worked with ellenhp on a proposal on import, to extract all the vorbis packets and just decode vorbis so the imported file gets rid of the ogg container. This is to remove stb_vorbis because of its documented crashing nature. Has preapproval from reduz."
+    "text": "This decision to use Byobu is part of our core strategy to provide the best tools and environment for our developers."
   },
   {
-    "objectID": "changelog/2021/20210601-changelog.html",
-    "href": "changelog/2021/20210601-changelog.html",
-    "title": "V-Sekai Changelog - 2021-06",
+    "objectID": "decisions/20231229-byobu.html#further-reading",
+    "href": "decisions/20231229-byobu.html#further-reading",
+    "title": "Proposed: Byobu terminal multiplexer",
     "section": "",
-    "text": "V-Sekai Changelog - 2021-06\n\n2021-06-30 17:31:02Z lyuma: Updated the GDScript migration script: https://github.com/V-Sekai/gd3to4/commit/bad3998a69273ba3b1172cead10363b7fda706cd\n2021-06-30 17:29:12Z lyuma: “Posted the MToon shader on the Godot Shaders page: https://godotshaders.com/shader/mtoon-shader-for-godot/”\n2021-06-30 09:27:28Z fire: Shaved some yaks to get the point of gltf2 export. Made 5 prs.\n2021-06-29 15:13:05Z fire: “Today I will work on:\nExpedite the SVG PR https://github.com/godotengine/godot/pull/49645\nInvestigate gltf2 export https://github.com/godotengine/godot/pull/48947 and https://github.com/fire/godot/tree/gltf-export-02\nInvestigate VOIP in Godot Engine outside of Godot Engine org tree”\n2021-06-28 03:02:32Z fire: Sent saracen an animation test\n2021-06-27 20:35:13Z fire: I wrote a 20 step instruction on how to save any pose as the rest pose. https://github.com/V-Sekai/blue-tin-fox-models/blob/master/characters/blender-save-pose-as-rest-pose.md\n2021-06-27 04:34:09Z fire: Invited a few new people this week. Say hi to LillyByte from Godot Engine Discord and mrmetaverse from OMI Group\n2021-06-24 22:57:41Z fire: https://hubs.mozilla.com/spoke/projects/new?sceneId=Rpt8DJS\n2021-06-24 22:40:50Z fire: https://github.com/MozillaReality/hubs-blender-exporter https://github.com/KhronosGroup/glTF/pull/1400 Lyuma\n2021-06-24 21:34:56Z fire: Talked with Robert from OMI about the useful of a spatial audio emitter extension. There’s also a microsoft and a mozilla hub implementation for spatial audio node in wav?, mp3? or ogg? . He had unfinished business with the extension namespace of hubs and wanted to split it.\n2021-06-23 00:19:33Z lyuma: “https://github.com/V-Sekai-godot-hop-spin-dance Don’t get your hopes up quite yet: A lot of the lower level dependencies for scene packing and t-posing are not converted yet, but the tool scripts work now, so it’s a start :-p” 🔥 (1)\n2021-06-23 00:19:07Z lyuma: Worked with fire to get the avatar conversion tool updated, using the high level vsk_avatar vsk_vrm_avatar_tool modules: https://cdn.discordapp.com/attachments/836651615532482611/857052116593803284/unknown.png\n2021-06-22 23:48:06Z lyuma: mux says they also keep hitting this issue. they also made the connection to set_name() interestingly\n2021-06-22 23:47:51Z lyuma: after a day of debugging, Saracen got a reproduction project here: https://github.com/godotengine/godot/issues/49843\n2021-06-22 23:22:17Z fire: Another day. Implement vrm quaternion format from lox9973 from ShaderMotion to move godot VRMs\n2021-06-22 21:00:23Z fire: We ported the avatar T-Poser to the point the menu popup shows and checkpointed, then concluded for lunch. Multiple modules were ported.\n2021-06-22 20:56:35Z fire: https://github.com/godotengine/godot-proposals/issues/2903 Lyuma wrote a proposal\n2021-06-22 17:33:46Z fire: “Did a 5 minute design for libcurl in Godot Engine. Use https://github.com/OpenAPITools/openapi-generator/tree/master/modules/openapi-generator/src/main/resources/C-libcurl as a template.”\n2021-06-22 17:22:01Z fire: Defined a mantra for groups: Presence with custom avatars and custom worlds.\n2021-06-22 15:55:37Z fire: Updated https://github.com/godotengine/godot/pull/49645 CICD Passes https://cdn.discordapp.com/attachments/836651615532482611/856925406166515722/unknown.png\n2021-06-21 13:24:31Z fire: Did I do this wrong? A vs B cs C https://imgsli.com/NTgzMDk/1/2\n2021-06-21 12:40:26Z fire: Good news, the gd_util, math_util and vsk_avatar plugin enables. Now to test it.\n2021-06-21 03:30:21Z fire: Updated godot-vrm to latest master. https://github.com/V-Sekai/godot-vrm/tree/master 👍 (1)\n2021-06-20 23:44:26Z Saracen: More fixes to be compatible with the latest master branch. Also making more bug reports for serious issues I encounter 🐛 (1),👍 (1)\n2021-06-20 20:29:37Z fire: It’s pretty slow like 7 seconds\n2021-06-20 20:29:23Z fire: &gt; RGBA Max error: 77 RMSE: 1.55 PSNR 44.34 dB\n2021-06-20 20:29:22Z fire: # bc7_enc_rdo\n2021-06-20 20:29:01Z Saracen: Wow, the existing one is already pretty fast. Good job!\n2021-06-20 20:28:33Z fire: “# Current (1 thread) RGBA Max error: 57 RMSE: 0.85 PSNR 49.57 dB CVTT 1024x1024 total time: 1.55 secs # Previous (1 thread) RGBA Max error: 28 RMSE: 0.43 PSNR 55.53 dB CVTT 1024x1024 total time: 35.68 secs”\n2021-06-20 20:28:32Z fire: https://github.com/fire/godot/tree/faster-cvtt Lyuma Saracen Faster BPTC compression.\n2021-06-19 22:42:58Z Saracen: I think I managed to fix the performance issue. It was a badly ported coroutine calling a heavy function continually. Still some issues with pathfinding and abilities not executing, but it’s at least actually functioning now.\n2021-06-19 19:22:18Z Saracen: Further fixes, there’s workarounds now for the tool I wrote to extract root motion. Two of the notable bugs I’ve discovered are ConfigFile.load returning random values and the fact that there doesn’t seem to be implicit casting between String and StringName. Want to create some example projects for this. It’s also worth noting that while Amethyst is close to being functional now, it’s running OBSCENELY slow at the moment. 🦥 (1)\n2021-06-19 18:01:49Z Saracen: Some more progress on the Amethyst port\n2021-06-19 07:45:39Z fire: Can now export blends to gltf2 and save as an artifact. Also installs vrm plugin.\n2021-06-19 07:45:30Z fire: https://github.com/V-Sekai/blue-tin-fox-models\n2021-06-19 00:16:57Z fire: Discussed with Saracen and Acquaintances to add a female mannequin to add colored characters.\n2021-06-18 21:01:16Z fire: https://github.com/godotengine/godot/pull/49717\n2021-06-18 20:15:22Z lyuma: That’s a bug with shadow mesh actually\n2021-06-18 20:14:42Z fire: https://github.com/godotengine/godot/issues/49706\n2021-06-18 10:29:49Z lyuma: https://cdn.discordapp.com/attachments/836651615532482611/855393862876790804/avp_living.jpg\n2021-06-18 10:28:07Z lyuma: There are still things missing, of course: for example, some materials like the walls use a custom shader with nonstandard property names… but the overall scene structure does get imported! 👏 (3)\n2021-06-18 10:27:51Z lyuma: I’m proud to announce that Unidot Importer was finally able to import the “Vol. 6” AirBnB House without any major errors! https://cdn.discordapp.com/attachments/836651615532482611/855393367545085983/unknown.png\n2021-06-17 22:53:22Z fire: 2 visual script godot engine prs merged\n2021-06-17 17:01:09Z fire: !!!\n2021-06-17 16:59:42Z Saracen: I pushed an experimental branch of Amethyst designed to work in 4.0 upstream to a new branch. The behavior tree is still broken though.\n2021-06-16 23:24:26Z fire: https://github.com/fire/godot/tree/bc7enc_rdo Updated\n2021-06-16 23:23:49Z fire: https://github.com/godotengine/godot/pull/49669 Lyuma not sure if it’s the crash\n2021-06-16 17:55:57Z fire: OMI meeting notes.\n2021-06-16 17:54:58Z fire: https://cdn.discordapp.com/attachments/836651615532482611/854781112055234561/June_16th_2021_OMI_Meeting.pdf\n2021-06-16 17:52:52Z fire: ThorVG made bugfixes to my failure code.\n2021-06-16 07:18:45Z fire: Got very sidetracked. Also implemented ThorVG to compare.\n2021-06-14 16:30:44Z fire: Code review from Blender for faster baking performance\n2021-06-14 16:30:09Z fire: https://github.com/godotengine/godot/pull/49601 PR for SVG module.\n2021-06-13 02:50:12Z fire: Woke up with a dream. openseeface as a body tracker. https://github.com/you-win/openseeface-gd/issues/16\n2021-06-13 02:44:32Z fire: Related to the comic book reader idea for vr\n2021-06-13 02:39:39Z fire: I wrote a SVG module for godot engine https://github.com/sammycage/lunasvg/issues/47\n2021-06-12 22:26:57Z fire: I think I’m breaking lyuma’s server\n2021-06-12 22:26:21Z fire: Godot Engine 4 and Groups 4.x builds have been flowing for the last day or so on itchio\n2021-06-12 22:16:36Z fire: Chatted with youwin with Lyuma and did work on gdopenseeface, gltf and godot-vrm\n2021-06-12 22:16:09Z fire: Chatted with https://twitter.com/CaptainProton42 and joined a few repositories\n2021-06-11 22:07:17Z fire: https://github.com/Tom94/tev !\n2021-06-11 03:46:06Z lyuma: Updated the @export fix for a third time. It’s amazing how many different ways there are to fix bit operations on a single line of code\n2021-06-11 03:45:26Z lyuma: Updated shader_improvements_meta_3.x branch for latest 3.x godot so someone could try SCSS (I want to keep it for historical purposes). I’m not going to update 4.x because it’s in flux and too much churn with renames to keep anything working\n2021-06-11 03:44:54Z lyuma: Found a bug in MToon, related to a line of code that flips the normal if it’s pointing backwards from the view direction (you can see this if you look at an MToon face with custom normals from a sharp direction).\n2021-06-10 22:56:30Z fire: Restoring the CICD builds for godot 4. I did the changes, but currently verifying that it builds on Groups 4.x and then I’ll try github.com/godotengine@master\n2021-06-10 03:11:20Z fire: https://cdn.discordapp.com/attachments/845777129605300255/852383622606094346/unknown.png https://cdn.discordapp.com/attachments/845777129605300255/852383560882323487/unknown.png I tested compute graphs earlier. This is is the important part. I can now start a github action, start a kubernetes server, start a argo server, start an alpine linux image, have a whale message a hello world and then save it as a file and have it be download as a github artifact\n2021-06-09 20:50:29Z lyuma: “I tried baking lighting in the”“AirBNB”” and ran into this error: &gt; WARNING: Inconsistency found in triangulation while building BSP, probe interpolation quality may degrade a bit. &gt; at: LightmapGI::_compute_bsp_tree (scene\\3d_gi.cpp:460) &gt; &gt; Jfons informed me it is an issue with separating tetrahedrons. The scene has 2641 light probes so there’s probably something suspect there. I’ll have to look into it further. I think I have an idea: we have to make sure there are probes above and below to form a complete tetrahedron”\n2021-06-09 20:49:09Z lyuma: “Summary about lightmap UV problem: Mesh scale & import scale matters when dealing with lightmaps. There were bugs reading the scale, but now that is fixed and the issue with losing polygons will only happen on triangles with 1e-7 edge length in world space.\n\nThe issue with removing mesh edges still exists, in theory, but in practice it seems unlikely so let’s wait and see if it shows up in the wild and then we can take another look”\n\n2021-06-09 18:09:18Z lyuma: https://cdn.discordapp.com/attachments/836651615532482611/852248004215570432/unknown.png\n2021-06-09 18:07:18Z lyuma: Due to a glitch in Godot’s etcpak implementation, I had to use BPTC texture compression. It took 3-4 hours to compress all the textures :-p (I can’t use uncompressed textures because VRAM isn’t free and I don’t own a 3090) godette (1)\n2021-06-09 18:06:25Z lyuma: so it’s bound to improve further. it’s pretty fun seeing this place come together\n2021-06-09 18:06:04Z lyuma: A lot of objects are missing material assignments due to naming rules (for example ” - ” or ” #” in filenames\n2021-06-09 18:05:39Z lyuma: I know it’s not the v-sekai 4.x port but I took a break from it to work a bit more on fixing import issues: https://cdn.discordapp.com/attachments/836651615532482611/852247085931298896/unknown.png\n2021-06-09 13:44:28Z fire: https://github.com/godotengine/godot/pull/49458#event-4864988341 Lyuma\n2021-06-08 16:57:57Z fire: Blank screen\n2021-06-08 16:57:53Z fire:\n\nOpenVR: initializing OpenVR context Application in scene (normal) mode. Main OpenVR interface has been initialized Main render models interface has been initialized. Exec path: C:/Users/XXXX/Desktop/groups-4.x/godot/bin\n\n2021-06-08 16:04:42Z fire: Fell asleep doing Quat and Transform3D renames\n2021-06-08 12:25:39Z fire: “Need to build godot, then copy the generated files for GDNative. --gdnative-generate-json-api api.json --gdnative-generate-json-builtin-api builtin_api.json”\n2021-06-08 10:22:22Z fire: Lyuma Openvr godot 4\n2021-06-08 10:21:49Z fire: fire build godot using:\n\ngodot#49301\nThen build the plugin with:\ngodot_openvr#123\nMake sure to use vnens godot-cpp and copy all the gdnative headers and stuff into place from your godot build”\n\n2021-06-08 02:36:48Z fire: Lyuma Saracen MMMaellon https://cdn.discordapp.com/attachments/836651615532482611/851650948467916810/unknown.png 👍 (1),VRDude (2)\n2021-06-07 19:44:27Z fire: https://github.com/godotengine/godot/pull/49401 PR\n2021-06-07 07:02:52Z fire: Made a release of FBX2glTF https://github.com/V-Sekai/FBX2glTF/releases/tag/v2021-06-07T06_5500_00\n2021-06-06 16:20:36Z fire: ✨ Silent’s Birthday Party. Cake, Shrine and 15 fps. Someone mentioned there was a guest list of a hundred.\n2021-06-04 14:59:40Z fire: My first Blender pr. ✨ https://developer.blender.org/D11502/new/ 👍 (1)\n2021-06-03 22:27:31Z fire: Lyuma lots of things changed today. Including Transform -&gt; Transform3D\n2021-06-03 14:55:15Z fire: Meeting done.\n2021-06-03 12:59:57Z fire: “Lyuma Saracen MMMaellon PR review meeting on https://meet.jit.si/godot-pr-review in 5 min, everyone welcome. We’ll bikeshed about”“breaks compat”” PRs for 4.0 (mostly renaming stuff in the API, etc.)”\n2021-06-03 04:47:29Z fire: ”\ndiff --git a/source/blender/io/collada/AnimationExporter.cpp b/source/blender/io/collada/AnimationExporter.cpp\nindex 73952b06bc9..3679dd090b4 100644\n--- a/source/blender/io/collada/AnimationExporter.cpp\n+++ b/source/blender/io/collada/AnimationExporter.cpp\n@@ -100,6 +100,10 @@ bool AnimationExporter::exportAnimations()\n    openLibrary();\n\n    BCObjectSet::iterator it;\n+\n+#ifdef WITH_OMP\n+#pragma omp parallel for\n+#endif\n    for (it = animated_subset.begin(); it != animated_subset.end(); ++it) {\n        Object *ob = *it;\n        exportAnimation(ob, animation_sampler);``` 15 minutes to 5 minutes gltf2 anim export.\n2021-06-02 20:39:33Z fire: Lyuma Any thoughts on making Mousse a VRM? I’m stuck. Meshes are not exporting from Blender. Compiling Blender 2.93 (LTS) for debugging.\n2021-06-02 20:19:18Z fire: Wasm GDNative and Godot Engine will be evaluated in future releases https://twitter.com/nonunknown3/status/1400090487005011970?s=20\n2021-06-02 20:14:14Z fire: / Blender 2.93 is out https://www.blender.org/download/releases/2-93/ https://twitter.com/i/status/1373384489146142720\n2021-06-02 19:03:14Z fire: Worked with Lyuma with posting a comment about small and bigger than [-1, 1] weights on blend shapes. Will send it off to the rendering team and we’re punting it.\n2021-06-02 15:08:21Z fire: Spent an hour debugging gltf2 blend shapes. 💤 Conclusion, blender export bug in 2.91 (stable is 2.92)\n2021-06-01 15:03:23Z fire: lottie -&gt; zstd compressed packaged scene (online)\n2021-06-01 15:03:08Z fire: inkscape -&gt; lottie -&gt; saved in an ordered list container with zstd (all offline). .cb7l\n2021-06-01 14:41:05Z fire: Investigating a path where we do pdf -&gt; svg (vectors and raster images) -&gt; lottie (vectors and raster images)\n2021-06-01 13:43:29Z fire: Finding libraries that does pdf https://github.com/reMarkable/pdfium-binaries https://pdfium.googlesource.com/pdfium/+/HEAD/docs/getting-started.md pdfium page as_image\n2021-06-01 06:25:26Z lyuma: https://twitter.com/VSekaiOfficial/status/1399608449101484032"
+    "text": "V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine\nV-Sekai/v-sekai-game - GitHub page for the V-Sekai open-source project bringing social VR/VRSNS/metaverse components to the Godot Engine\n\nAI assistant Aria assisted with this article."
   },
   {
-    "objectID": "changelog/2021/20210501-changelog.html",
-    "href": "changelog/2021/20210501-changelog.html",
-    "title": "V-Sekai Changelog - 2021-05",
+    "objectID": "changelog/2024/20240701-changelog.html",
+    "href": "changelog/2024/20240701-changelog.html",
+    "title": "V-Sekai Changelog - July 2024",
     "section": "",
-    "text": "V-Sekai Changelog - 2021-05\n\n\nChangelog\n\n2021-05-31\n\n21:30:03Z fire: Godot4OVRTest and godot-fire\n21:29:42Z fire: Context. Porting OpenXR to run on Godot Engine 4\n21:29:29Z fire: haagch’s input on VkPhysicalDevices and VkInstances\n21:28:46Z fire: haagch’s suggestion for handling VkInstance in OpenXR plugin and engine\n21:25:54Z lyuma: Yayay\n21:11:03Z fire: 🎆 🎆 🎆\n21:10:49Z fire: 🎉\n21:10:45Z fire: Lyuma Merged PR #49120 👏 (2)\n\n\n\n2021-05-30\n\n12:58:28Z fire: V-Sekai VRM addon release\n10:58:12Z lyuma: “Submitted the asset”“VRM Importer and MToon Shader”” - it will be at asset/3693 once approved.\n\nIssue comment\nVideo demo\n\n00:57:51Z fire: Merged LOD fix PR #49197\n\n\n\n2021-05-29\n\n22:08:49Z fire: Found a bug in LOD on integer locations. Asked someone to handle it for me.\n17:52:04Z fire: Lyuma May need an ubuntu version too. Not sure how the test matrix works. I want fedora and ubuntu LTS (the oldest one)\n17:13:00Z lyuma: Progress on godot-cpp, Godette-Chan model port to VRM, and other updates\n17:09:27Z lyuma: Debugging an issue causing the outlines to look too bright in MixedLight mode, then I’ll demonstrate exporting a default character from vroid studio as well.\n\n\n\n2021-05-29\n\n17:06:50Z lyuma: Godette-Chan model in VRM format\n16:59:06Z lyuma: Godette-Chan model port result 👏 (1)\n\n\n\n2021-05-28\n\n22:45:48Z fire: Spent the afternoon on organizing work on the CMValley Godot Demo\n21:53:32Z lyuma: Updated godot-cpp; fixed SConstruct lines and resolved errors with clang and the gltf GDNative plugin\n21:15:35Z fire: Investigating the Godot Engine open content map “CMValley_to_Godot_Demo” (Ask me for the doc if you want it)\n20:46:13Z fire: Given .net assemblies 1. visualize 2. given pdbs associate symbols 3. graph!\n20:45:48Z fire: Lyuma Synergiance SourcetrailDotnetIndexer\n06:24:04Z fire: Code review gltf the entire afternoon\n\n\n\n2021-05-27\n\n18:45:25Z fire: Spent time summoning peers about making a realistically lit 3d game level environment in Godot Engine. Official Godot Engine business. -_-\n\n\n\n2021-05-26\n\n21:43:14Z lyuma: Filed bugs and pull requests\n21:17:25Z fire: Tokage improved the Skeleton Gizmos with better color choices and bugfix for a shadow problem with depth\n17:43:36Z fire: We contributed to the drafting of them.\n17:43:22Z fire: Values from OMI\n10:38:49Z lyuma: Twitter post\n\n\n\n2021-05-26\n\n09:26:03Z lyuma: For now anyway, the VRM module is only for import.\n09:25:40Z lyuma: there’s a lot of untested code related to export, since there are still bugs, but I expect to be able to incorporate any bugfixes made to export\n09:25:09Z lyuma: After finishing the backport of the Fire’s latest gltf module to 3.x as a module / draft PR, I had success in porting the gltf module to GDNative: The VRM module now runs in Godot 3.3-stable: Screenshot\n\n\n\n2021-05-24\n\n18:13:44Z fire: Evaluating curve fitter from Maya2glTF. Reducer-fire branch Screenshot\n18:08:49Z Saracen: Progress on asset validation layer and remaining issues\n15:37:50Z fire: (blender)\n15:37:37Z fire: Screenshot 👍 (2)\n15:37:09Z fire: Worked with hutty to transfer gltf export tech to his voxel drawing tool\n00:56:09Z fire: Also, pitching usdz after 4.0\n00:55:22Z fire: “Trying to pitch a list of features for funding. - Full glTF2 / VRM import and export pipeline in Godot Engine\nGeneral purpose retargeting system for VRM type models + encoding in BVH (3d pose format)\nGodot Engine support for basis universal in glTF2\nQuads in glTF2\nAfter quads in glTF2, better mesh simplification and LODs that work on quads”\n\n\n\n2021-05-22\n\n16:23:18Z fire: PR #47764 Lod Merge! 👏 (4)\n03:41:06Z lyuma: is it GLES2 or GLES3?\n03:12:33Z fire: humbletim Screenshot\n02:30:08Z fire: Investigating V-Sekai compiled for javascript\n\n\n\n2021-05-21\n\n23:38:30Z fire: Screenshot\n23:32:27Z fire: What do I do, Victoria Day on Monday. How is the Queen!?\n23:31:24Z fire: Discussed 15 frames encoding into a QR / DataMatrix code ShaderMotion Writing a obs script in python to read data.\n\n\n\n2021-05-21\n\n15:37:50Z fire: (blender)\n15:37:37Z fire: Screenshot 👍 (2)\n15:37:09Z fire: Worked with hutty to transfer gltf export tech to his voxel drawing tool\n00:56:09Z fire: Also, pitching usdz after 4.0\n00:55:22Z fire: “Trying to pitch a list of features for funding. - Full glTF2 / VRM import and export pipeline in Godot Engine\nGeneral purpose retargeting system for VRM type models + encoding in BVH (3d pose format)\nGodot Engine support for basis universal in glTF2\nQuads in glTF2\nAfter quads in glTF2, better mesh simplification and LODs that work on quads”\n2021-05-21 22:51:16Z lyuma: “I worked with fire on debugging glTF. I think we’re going to possibly need two different approaches for solving glTF skeletons.\n\nRadical change to glTF parser to treat all subtree nodes as part of a single skeleton recursively. (What we were just testing) I believe this would be unacceptable in 3.x because it is almost guaranteed to break compatibility with all content, but it may be desirable in 4.x.\nAdd BoneAttachments to skeletons directly parented to skeletons. (We tried this). This may be required in 3.x.\nWhile in _determine_skeletons, detect the specific case in which two skeletons would be directly parented and add them to the disjoint set in this case (look at the parent objects at the end). Do not actually add the parent bone to the disjoint set: only do it if this would hit the problem case. Issue: this may require doing another iteration of the _determine_skeletons code? Is this possible without causing more bugs? This could be a compromise if it is possible.\n\nBugs:\n\nAnimations must not animate SkinnedMesh objects\nWe ran into weird issues with fake_joints. Can these issues be reproduced without the radical change above? I think they can by making a single gltf file which has a skin also referencing a mesh. This issue leads animation targeting mesh-bones to fail to create a bone track correctly.\nMeshSkinnedToItselfAndOthersV3 is missing a whole mesh node after import. It shows up in the popup but not in the final scene. Owner issue?? Is it related to the fake_joints? The glb here should have a spinning diamond and two spinning skinned cubes:” https://cdn.discordapp.com/attachments/836651615532482611/845433592888557568/MeshSkinnedToItselfAndOthersV3.glb\n\n2021-05-21 22:29:43Z fire: We also gain the ability to post more twitter tweets.\n2021-05-21 22:29:23Z fire: Had a discussion with Lyuma and Saracen about V-Sekai for wider testing and how it was blocked by scene validation feature.\n2021-05-21 15:27:33Z fire: Multiple PRs from fire and Lyuma were merged for gltf problems\n2021-05-20 15:28:19Z fire: トカゲ https://github.com/godot-extended-libraries/godot-fire/commits/features/skeleton-gizmos I did some cleanup, rebased on the modification stack and changed the color for selected bones to be a darker orange\n2021-05-20 15:26:43Z fire: Lyuma IK and Modification stack are now a stacked branch.\n2021-05-20 04:21:06Z fire: Work with Lyuma on 3 glTF bug fixes. 1. instead of failing all the meshes only fail once 2. the skins duplication removal code has a bug and it needs to check skin bind bone, skin bind name and pose transform. 3. the skin bind code was removed 4. gltf 4.0 modules was backported to 3.2\n2021-05-19 19:20:41Z fire: Lyuma and I summarized our concerns about the ease of implementation and the inability to use off the shelf code.\n2021-05-19 19:20:00Z fire: OMI Week 3. Stayed for the talk at 9am and then stayed with Robert Long to talk about OMI Identity and misc things like there is no opensource OpenXR mobile client. https://github.com/omigroup/OMI/issues/36#issuecomment-844392614\n2021-05-19 14:37:19Z fire: After sleeping on the Linux RPM database problem, I was able to get WSL working again. Lyuma I needed to switch WSL to version 2.\n2021-05-18 18:32:58Z fire:\n\ngroups-4.x branch in the Groups Godot Engine Repo\n\n1. VRM patches required\n2. Importing patches for the editor\n3. Gltf and other UV1-8 channel requirements\n4. (stacked branch) bone modification + bone gizmos\n5. fix normals being broken in mesh optimizer\nPush on merge extended-fire-master remotes/fire/cubic-interpolation\nPush on merge extended-fire-master remotes/fire/gltf-bone-skinning-normalization\n6. remotes/bruvzg/msdf_fonts\n7. push gltf export (fire)\n8. feature/spatial-audio\n9. rewrite compressed audio for voip\nPush on SIMDE for avx support\nPunt crash / reliability problem on Godot Engine crashing\n\nmerge-script-4.x is the branch name for the groups_merge_script Repo\n\n2021-05-18 17:41:55Z fire: “Coordination problems:\nname of the ““merge script”” for v-sekai 4.x\nname of the V-Sekai/godot branch for v-sekai 4.x\nwhich branches should be in the initial set of patches applied to godotengine master branch”\n2021-05-18 14:46:44Z fire: GSOC 2021 started on Monday. Will be mentoring Theoway and on the topic of Visual Script node visual organization\n2021-05-18 14:43:56Z fire: Posted my last revision of runtime export https://github.com/godot-extended-libraries/godot-fire/tree/extended-fire-master-runtime-gltf\n2021-05-18 14:01:58Z fire: Lyuma Please see xr channel in godot about runtime gltf. May be too politically diffficult to get merged, so will fix gltf export bugs\n2021-05-18 03:48:49Z fire: “Worked with Lyuma and Tim on MotionShader to glTF2 https://hackmd.io/@tI5OkracQhuas5Kjh-kG0g/S1uzKIgt_/edit”\n2021-05-17 00:07:58Z Saracen: A few more fixes to the XR switching + you can now alter your real-world height at runtime heart (2)\n2021-05-16 23:01:38Z fire: I have as animation as I want 😮 https://cdn.discordapp.com/attachments/836651615532482611/843624264958738462/2021-05-16_15-59-25.mp4 👍 (2)\n2021-05-16 23:01:17Z fire: https://cdn.discordapp.com/attachments/835369558541467668/843623340965888040/godot_girl_stealth_JohnnyRouddro_mit_lic_No_Logic_David_cc_by.glb\n2021-05-16 22:58:19Z Saracen: Added further bug fixes to runtime switching of VR mode and flat mode. Fixes the few minor remaining issues with the avatar poses getting messed up, and the VR controllers being stuck on screen. With that, I’m satisfied with marking this feature as done in the tracker.\n2021-05-16 22:22:05Z fire: Work around found. Import into godot and then export it as glb again.\n2021-05-16 22:17:37Z fire: Submitted a blender gltf bug report. https://github.com/KhronosGroup/glTF-Blender-IO/issues/1392 😮 (1)\n2021-05-16 21:19:32Z fire: We are a go for big frame counts. I’m able to get a massive dataset thanks to lox9973 https://cdn.discordapp.com/attachments/836651615532482611/843598569851846707/unknown.png\n2021-05-16 21:15:45Z lyuma: “I hope the code I wrote will help others as a template for making nice-looking inspectors.\n\nI am considering submitting Godot-MToon-Shader to the asset library, separately from VRM.”\n\n2021-05-16 21:15:12Z lyuma: Using much the same cursed techniques that many Unity inspectors use, I was able to create bold headings, and “single-line” texture+image property pickers.\n2021-05-16 21:13:39Z lyuma: In some ways, it’s a bit more clunky than the get_property_list(), and a bit less versatile in terms of what you can do… but I decided to think outside the VBoxContainer a little bit, and I came up with a reasonable inspector, I think.\n2021-05-16 21:11:54Z lyuma: Spent most of the day learning how to make a custom shader inspector using EditorInspectorPlugin. I’m pretty happy with how it turned out https://cdn.discordapp.com/attachments/836651615532482611/843596648855896084/mtoon_shader_inspector.png\n2021-05-16 16:15:16Z fire: Thanks lox9973 for linking me to enough training data for my pose motion transfer tests. https://www.youtube.com/playlist?list=PLmwqDOin_Zt4WCMWqoK6SdHlg0C_WeCP6 (cc-by)\n2021-05-16 15:11:34Z fire: Brainstorming an intermediate format that isn’t exact per bone joint orientation but general across characters\n2021-05-16 05:53:14Z fire: Investigating ShaderMotion. Now that I can go from some anims to Unity Mechanism / UE4 / VRM skeletons, I want to investigate writing a shader motion player.\n2021-05-16 01:16:04Z lyuma: https://github.com/V-Sekai/godot-vrm godot3 branch (Godot 3.3): Runtime support requires no patches. Editor requires gltf module. master branch: Runtime support requires no patches. Editor requires two small engine fixes.\n2021-05-16 01:13:55Z lyuma: Getting very close to a releasable fully featured (Import-only) VRM addon for Godot. Let me know what you think in #pipeline https://cdn.discordapp.com/attachments/836651615532482611/843295167603015700/godot_vrm_1.0.0_beta.mp4\n2021-05-15 23:15:29Z fire: VRM from jin. Motion from Perfume dance webgl demo from 2013 in bvh format\n2021-05-15 23:15:13Z fire: Testing animation retargeting software from the Blender ecosystem. https://cdn.discordapp.com/attachments/842452265296986134/843264562430214164/2021-05-15_16-10-49.mp4\n2021-05-15 14:36:56Z lyuma: wiping history on V-Sekai/godot-vrm will be necessary because some large binary files were pushed in the past, and I want to ensure this addon is lightweight and easy to clone.\n2021-05-15 14:33:39Z lyuma: “Pushed an update to Godot-VRM for godot 3.x: https://github.com/V-Sekai/godot-vrm/tree/gd3 It’s not finalized yet and I will do a bit more testing and bugfixing before rebasing/wiping all of history pushing it to godot3, its final resting place.”\n2021-05-14 15:00:58Z Saracen: Fixed some bugs to improve support for switching between VR and flat modes at runtime. Very ugly hack to fix one of the bugs though, strange issue. Some slight remaining avatar issues, but it’s mostly working now it seems.\n2021-05-14 02:17:44Z fire: Added three pictures and a video.\n2021-05-14 01:33:44Z fire: VOX to VRM fun. (Autorigging investigation for any static humanoid mesh!)\n2021-05-13 21:38:00Z lyuma: but yeah! It’s really exciting to get this much imported with just a couple clicks and about 30 seconds of waiting\n2021-05-13 21:37:01Z lyuma: it’s a bit of random chance that it looks so similar: the skydome and some objects like flowers have completely custom shaders, so those will have to be ported manually\n2021-05-13 21:36:32Z Saracen: This is actually starting to look like the original now\n2021-05-13 21:36:27Z Saracen: Woah!\n2021-05-13 21:36:04Z lyuma: Unidot Importer: Got lighting and basic environment settings importing. In squiddingme’s Traveler’s Rift, I’m now able to bake lighting immediately after importing. (You can see the probes are baking as black, so there are still some issues to be worked out.) - Also added support for audio, cameras and reflection probes: https://cdn.discordapp.com/attachments/836651615532482611/842515566413873172/unknown.png\n2021-05-13 18:14:28Z fire: https://github.com/V-Sekai/vox-to-vrm\n2021-05-13 18:12:49Z lyuma: Oh, jin is re-rigging it\n2021-05-13 18:12:28Z lyuma: Jin’s proposal does not make sense\n2021-05-13 18:12:21Z lyuma: Vrm is an avatar format which requires a rigged humanoid model. Obj does not support rigging\n2021-05-13 17:48:43Z fire: Lyuma https://cdn.discordapp.com/attachments/836651615532482611/842458354202181642/unknown.png\n2021-05-13 06:35:51Z Saracen: Tweaked the way wristspan is calculated since it came out wrong on some avatars where the arms weren’t perfectly aligned. Should result in more accurate VR proportions.\n2021-05-13 04:26:05Z fire: Rebased my godot 4.0 stack so I can go back to my vrm viewer thing\n2021-05-13 03:14:34Z Saracen: One more patch just to allow direct assignment of upper and lower bones by ID, but it seems to be working now. Good job! It’s now possible to use avatars with in-between bones.\n2021-05-13 03:00:37Z Saracen: Basically, the new code to automatically assign the next bone in the chain assumed the skeleton was assigned, even though it can be null.\n2021-05-13 02:55:04Z MMMaellon#2053 whoa wait why was it crashing\n2021-05-13 02:47:41Z Saracen: Fixed RenIK crashing.\n2021-05-13 00:48:18Z fire: Reviewed https://github.com/godotengine/godot/pull/46568. Basis universal version update.\n2021-05-12 23:34:42Z fire: OMI meeting today. OKR Review. Progress was difficult.\n2021-05-11 15:38:53Z fire: Vive con starts in 20 minutes Voice Notifications. Any interesting talks?\n2021-05-11 15:38:00Z fire: Anything from Vive Con?\n2021-05-11 13:49:22Z lyuma: Fixed an issue in EWBIK that was bothering me – namely, that the result of the algorithm appeared to depend on the root bone having an identity transform. It seems that all that was needed was to transform the “tip” and “target” headings of an IKBoneChain by the inverse transform of the root. https://cdn.discordapp.com/attachments/836651615532482611/841673340740829234/unknown.png 🌅 (1)\n2021-05-11 03:32:10Z fire: Whoo debugged EWBIK the entire day, and removed the hacks to reveal the broken core to be rebuilt! Thanks Eron!\n2021-05-10 17:21:03Z fire: Evaluated EWBIK with Motion Retargeting. Suggestions included adding a position indication (with scale) as a child of the correction node that is a child of the bone attachment and olving only one frame at a time. No conclusions yet, because ewbik is too broken.\n2021-05-10 02:48:21Z fire: Working with Eron on ewbik. Next meeting at 9am or later.\n2021-05-09 22:31:35Z fire: Working out a system where we create targets from the other skeletal animation using bone attachments and then a corresponding correction node underneath it. The ik solver then uses those correction node targets as the target.\n2021-05-09 17:22:13Z Saracen: Support for ordered grid super sampling and camera position-based bill-boarding added thanks to help from Silent and Lyuma\n2021-05-09 16:08:30Z fire: Many patches from トカゲ were merged today /. Thanks\n2021-05-09 14:34:42Z fire: Saracen / Lyuma suggested a hint_string where a skeleton bone attachment gets a filtering tree popup for selecting bones\n2021-05-08 15:47:13Z Saracen: https://github.com/SaracenOne/godot/tree/collada_semantic_fix_4_0\n2021-05-08 15:46:07Z Saracen: https://github.com/SaracenOne/godot/tree/collada_semantics_fix_3\n2021-05-08 15:45:11Z Saracen: Fixed some bugs with the Collada importer\n2021-05-08 15:44:33Z Saracen: https://cdn.discordapp.com/attachments/836651615532482611/840615163937816585/screenshot_2021_05_08_164031.png\n2021-05-08 10:48:29Z lyuma: Just to see how close I could get, I manually added a WorldEnvironment and did a few tweaks to light attenuation curves: https://cdn.discordapp.com/attachments/836651615532482611/840540658241634304/unknown.png\n2021-05-08 10:43:35Z lyuma: (Though, I also have not yet implemented world environment. Also, you can see it fails to port custom shaders like the skybox.)\n2021-05-08 10:42:42Z lyuma: squiddingme helped provide me with source files to their beautiful Traveler’s Rift, and I am finally able to import it using Unidot. This part was all automated, and includes collision meshes for all of the separate pickup objects, as well as light sources. https://cdn.discordapp.com/attachments/836651615532482611/840539201987936306/TravelersRift.jpg 👍 (1)\n2021-05-08 06:55:06Z fire: Chatted with humbletim about importing an existing armature into EWBIK Java\n2021-05-08 06:30:40Z MMMaellon#2053 You were talking about it the other day, but all that I got was that it was difficult to set up. idk what it actually did\n2021-05-08 06:30:13Z MMMaellon#2053 what does matrix server giv us?\n2021-05-08 06:28:45Z lyuma: “1. We set up a matrix server in 5 hours (a few hours wasted due to firewall).\n\n\nWe set up federation to the matrix server in an SRV record Next steps?\nTry godot-matrix to see if we can use the matrix server for interop. (Are there similar bindings for other languages?)\nSee if we can boil everything down to be easy to set up.\nWhat is matrix actually useful for? Identity? Establishing E2E messages? Sending invites? How does federation help?”\n\n\n2021-05-07 13:51:55Z fire: EWBIK bone dampening is implemented.\n2021-05-07 11:09:14Z fire: &gt; You won’t need stabilization before you’ve implemented constraints.\n2021-05-07 11:08:49Z fire: “Ewbik todo. dampening is about getting a natural pose, stabilization is about preventing wobbling when a lot of constraints are being violated.”\n2021-05-06 15:45:06Z fire: Got a reply from glitchtip. Require use cases generation.\n2021-05-05 21:29:14Z fire: Added better ui for creating the effectors (targets and pins) in ewbik\n2021-05-05 18:28:53Z fire: Lyuma When you’re around, wanted to show you the EWBIK changes. It’s working for some small cases.\n2021-05-05 12:53:56Z lyuma: anyway aside from this PR and one other two-line workaround to the @export gdscript bug, Godot VRM master branch is now up-to-date and works on godot master (4.x). Currently working on getting the reins on 3.x and backporting some of the bugfixes\n2021-05-05 12:52:45Z lyuma: Akien uses a stupid reason to argue against https://github.com/godotengine/godot/pull/48014\n2021-05-04 22:02:14Z fire: Oops stupid, I didn’t enable parent to child for EWBIK\n2021-05-04 16:34:46Z fire: The idea is to run scripts on the os using ebpf to probe an active system. EBpf is similar to Sun DTrace and made by the same people.\n2021-05-04 16:34:15Z fire: Discovered: https://pixielabs.ai/ Apache 2 CNCF project. Access metrics, events, traces and logs in seconds without changing code via dynamic eBPF probes and ingestors.\n2021-05-04 16:15:03Z fire: Debugged with Eron EWBIK. No conclusions.\n2021-05-04 14:52:02Z fire: “Next steps on EWBIK: The stiffness constraint of a bone determines how much the IK solver should prefer to avoid rotating it if it can. The kusudama constraint limits rotation and twist.”\n2021-05-04 13:01:11Z fire: https://github.com/godotengine/godot/pull/47389#issuecomment-830588813 Saracen Please respond to wave importer review\n2021-05-04 12:59:10Z fire: “Still working on getting tokage’s prs merged (ping pong) https://github.com/godotengine/godot/pull/48332 (discrete carry) https://github.com/godotengine/godot/pull/48375”\n2021-05-04 12:55:38Z fire: Porting https://github.com/fire/godot/tree/2d-ik but need to ask pouley something\n2021-05-04 05:30:19Z lyuma: music?\n2021-05-04 05:28:37Z fire: V-Sekai music discussion.\n2021-05-04 01:29:11Z fire: rafallus EWBIK meeting time. Meeting done. Discussed the instability when the target is close and with multiple targets. Investigated future implementation of Kusudama constraints. Described a way to turn off ewbik constraints in the Java demo.\n2021-05-03 21:25:19Z fire: Godot Vulkan now runs a software renderer (for now SwiftShader) on cicd. Thanks qarmin.\n2021-05-03 21:24:38Z fire: https://github.com/godotengine/godot/pull/48410\n2021-05-03 21:23:55Z fire: PSA - We run godot –doctool in the Linux build, so if you modify the public API but fail to update the documentation, it will throw an error: So remember to run –doctool.\n2021-05-03 21:20:13Z fire: Fetching 2d IK PR for tomorrow.\n2021-05-03 21:19:37Z fire: Updated lottie to use zstd packedscene compression because vram compression is bad.\n2021-05-03 20:28:02Z fire: Trying to see if power of two resize will solve a crash on etcpak compressing for Lottie. It does.\n2021-05-03 20:19:20Z fire: Updated lottie https://github.com/godot-extended-libraries/lottie/tree/next to use texture compression (1GB to 10MB) and change skipping frames which was cursed to a interpolation scheme where the input is frame rate and not skipped frames.\n2021-05-03 19:10:40Z fire: Discussed with Lyuma about so many Godot Engine bugs to fix. gdparty (1)\n2021-05-03 16:06:57Z lyuma: Implemented support for unity binary asset format into Unidot Importer (such as LightingData.asset) - note that the actual data in this file isn’t used yet, but now we can parse these files.\n2021-05-03 12:09:06Z fire: Scheduled a meeting with rafallus about ewibik and working on gltf2 normalization pr.\n2021-05-02 21:09:57Z fire: &gt; wasm2c: Convert wasm files to C source and header\n2021-05-02 21:01:10Z fire: There’s an discussion about OMI and WASM again.\n2021-05-02 21:00:18Z fire: Discussed with Tylo#4997 in the OMI server, apparently we’re GLTF2 buddies. He worked on glTF2 furniture arrangements with 3d product models.\n2021-05-02 19:48:53Z fire: Reviewed https://github.com/godotengine/godot/issues/41028 with tokage “Blendspace2D BLEND_MODE_DISCRETE_CARRY freezes or doesn’t carry #41028”\n2021-05-02 15:10:07Z fire: https://github.com/fire/godot/tree/bc7enc_rdo and https://github.com/simd-everywhere/simde Godot Simd proposal\n2021-05-02 01:35:12Z fire: Working on nested bone attachments that also have a skeleton\n2021-05-02 01:27:57Z fire: Lyuma We got bone attachments! 🍖 (1)\n2021-05-01 22:34:48Z fire: Add a pr. Needs review\n2021-05-01 18:59:03Z fire: Trying to deal with the case where the weights is [2, 2, 2, 2] [0.7, 0.3, 0.0, 0.0] &gt;.&lt;\n2021-05-01 16:42:28Z fire: Clamping Nans, -Inf, +Inf in gltf exporter in Godot Engine."
+    "text": "Experimental (🧪): This stage is for features that are still being tested and may not be stable.\nFeature complete (🎯): This stage is for features that have all planned functionality implemented.\nBeta (🚧): This stage is for features that are largely complete but may still have bugs.\nGeneral release (🚀): This stage is for features that have been fully tested and are now released.\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nReplaced fabrik ik solver in renik ik character controler with qcp ik solver.\nManifold for Godot Engine CSG ready for review\nWorked on Wasgo for WASM32-CPUs for tooling and runtime user generated code.\nWorked on libriscv loading and executing a hello world function call with a shared object.\nWorked on godot-llama trying to get the new PHI-3 model working. https://github.com/V-Sekai/godot-llama\nWorked on ServerBackend🚫\nWorked on TrollVsGoatTrafficSimulator\nWorked on elaish/manifold for Constructive Solid Geometry\nWorked on Vahera/godot-orchestrator for riscv and a merge for node formatting\nWorked with fwsGonzo/libriscv for riscv. V8 now works.\nWorked on 3D Mesh\n\nTokenized into Sequence of Tokens\nInputted into Transformer Model\nGenerates New Meshes\nModifies Existing Meshes\n\nExperimental Mirrors: Engine Patch 🧪\nExperimental Mirrors: Screenspace 🧪\nMaintained Resource Whitelister 🎯\nMaintained VRM 🎯\nRobust Weight Painting (Experimental 🧪) (iFire)\n\nRelies on Lyuma’s Skeleton Merging Tool\n\nUpdate to Godot Engien 4.3-beta3\n\n\n\n\nUnified Godot Humanoid Skeleton 🚀\nUnidot Unity Package Importer\nFBX 🚧\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nSecurity Best Practices:\n\nThis project does not adhere to Semantic Versioning.\n\n\n\n\n\nNot applicable for this month."
   },
   {
-    "objectID": "changelog/2021/20210401-changelog.html",
-    "href": "changelog/2021/20210401-changelog.html",
-    "title": "V-Sekai Changelog - 2021-04",
+    "objectID": "changelog/2024/20240701-changelog.html#released",
+    "href": "changelog/2024/20240701-changelog.html#released",
+    "title": "V-Sekai Changelog - July 2024",
     "section": "",
-    "text": "V-Sekai Changelog - 2021-04\nIn April 2021, various developments and discussions took place in the Godot community. Key highlights include proposal designs for MaterialX integration, audio system improvements, and updates to the TPS demo for Godot 4.0. Additionally, there were investigations into edcurve support, normal seam problems, and soft body creation usability.\n\n2021-04-30\n\nProposal design of MaterialX Principled BSDF to Blender Principled BSDF to Blender surface.\nLyuma — MaterialX in glTF would allow for a generalization of “KHR_materials_variants” extension.\nMade a proposal for GLTF2 to include MaterialX in three stages.\nMade a prototype that exposes HTC Facial tracker to Godot Engine as a GDNative plugin for 3.x. Link\n\n\n\n2021-04-29\n\nDesign Approved; Needs Proposal from Juan: Play scheduled notes/metronome Link\nPostponed Discussion: Modular audio system (like JACK) godot#35613\nInterest: Integrate interactive music PR godot#32769\nInterest: Discuss audio stream graph\nApproved: Onboarding for newcomers to the audio side of Godot development\nInterest: Godot Audio Graph\n\n\n\n2021-04-28\n\nArguing in OMI about materialx, usdz and wasm\nFiled issue Link\nInvestigate Link for edcurve support now\nFiled issue Link\nFire filed issue Link about the rendering server custom format issue with a reproduction project.\nReduz is personally updating the TPS demo for 4.0\nGodot Engine developers’ next Live Q&A on YouTube this Thursday, 29 April 2021 at 18:00 UTC. Link\nLyuma Topics: Normal seam problem\nLyuma Topics: Create a proposals for better usability of soft body creation.\nLyuma Topics: Using n-gon encoding for glTF / VRM.\n\n\n\n2021-04-27\n\nMade a small video and ported the Godot IPFS demo to Windows. Link\nUpdated Scheduled play branch and the demo. Link and Link\nWaiting for a 3d print of Link so I can try the HTC Facial tracker with Link.\nMade a decision yesterday to close GIF / APNG import in Godot due to consensus. Link\nReviewing WebP as the default lossless compression algo for the core Godot Engine. Link\nReceived an update to the Holo display delivery. It’ll be in May - https://www.kickstarter.com/projects/lookingglass/looking-glass-portrait/posts\nReviewing Play Scheduled proposal - Link\nUse the IPFS Go language binary to make Godot an IPFS server Link\nWorked on debugging SVG import for the UI made for the hop spin dance display. Link"
+    "text": "Not applicable for this month."
   },
   {
-    "objectID": "changelog/2022/20220201-changelog.html",
-    "href": "changelog/2022/20220201-changelog.html",
-    "title": "V-Sekai Changelog - 2022-02",
+    "objectID": "changelog/2024/20240701-changelog.html#unreleased",
+    "href": "changelog/2024/20240701-changelog.html#unreleased",
+    "title": "V-Sekai Changelog - July 2024",
     "section": "",
-    "text": "iFire — Today at 07:38 Openxr is merged into Godot Engine master!\nLyuma — Today at 16:13\nOVR Advanced Settings 5.4.0 is released with OpenXR playspace moving support (for devices connected via SteamVR):\nhttps://user-images.githubusercontent.com/32321/155451982-8d21ca07-0178-4314-a4f2-8de56c275fa3.png\n\n\n\nトカゲ — 10:28 We discussed with reduz implementation of retargeting for about 8 hours\nLyuma — 14:02 if anyone’s interested, you can read RocketChat from a browser: https://chat.godotengine.org/channel/animation?msg=JYqzF7xviTbh5zbmm\n\n\n\nFire moved multiple projects issues to https://github.com/V-Sekai/V-Sekai/issues.\n\n\n\nLyuma changed RenIK to use set_bone_local_pose_override, and “hacked” skeleton’s transform to keep it centered on the hips, fixing the avatar disappearing when far from origin.\n\n\n\nWe made a lot of progress yesterday: getting closer to OpenXR integration; fixed some issues with avatar uploading; and progress with WasGo, including the ability to create a Godot Callable which directly represents a WASM function\n\n\n\nMoved fire’s project notes to V-Sekai/V-sekai issues.\nCurl has been postponed.\nCvtt bc6, bc7 texture compression speedup by reducing quality has been merged. Updating groups.\n\n\n\nWasgo go! Restored wasgo wasm execution."
+    "text": "Replaced fabrik ik solver in renik ik character controler with qcp ik solver.\nManifold for Godot Engine CSG ready for review\nWorked on Wasgo for WASM32-CPUs for tooling and runtime user generated code.\nWorked on libriscv loading and executing a hello world function call with a shared object.\nWorked on godot-llama trying to get the new PHI-3 model working. https://github.com/V-Sekai/godot-llama\nWorked on ServerBackend🚫\nWorked on TrollVsGoatTrafficSimulator\nWorked on elaish/manifold for Constructive Solid Geometry\nWorked on Vahera/godot-orchestrator for riscv and a merge for node formatting\nWorked with fwsGonzo/libriscv for riscv. V8 now works.\nWorked on 3D Mesh\n\nTokenized into Sequence of Tokens\nInputted into Transformer Model\nGenerates New Meshes\nModifies Existing Meshes\n\nExperimental Mirrors: Engine Patch 🧪\nExperimental Mirrors: Screenspace 🧪\nMaintained Resource Whitelister 🎯\nMaintained VRM 🎯\nRobust Weight Painting (Experimental 🧪) (iFire)\n\nRelies on Lyuma’s Skeleton Merging Tool\n\nUpdate to Godot Engien 4.3-beta3\n\n\n\n\nUnified Godot Humanoid Skeleton 🚀\nUnidot Unity Package Importer\nFBX 🚧\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nSecurity Best Practices:\n\nThis project does not adhere to Semantic Versioning."
   },
   {
-    "objectID": "changelog/2022/20220201-changelog.html#section",
-    "href": "changelog/2022/20220201-changelog.html#section",
-    "title": "V-Sekai Changelog - 2022-02",
+    "objectID": "changelog/2024/20240701-changelog.html#previous-releases",
+    "href": "changelog/2024/20240701-changelog.html#previous-releases",
+    "title": "V-Sekai Changelog - July 2024",
     "section": "",
-    "text": "iFire — Today at 07:38 Openxr is merged into Godot Engine master!\nLyuma — Today at 16:13\nOVR Advanced Settings 5.4.0 is released with OpenXR playspace moving support (for devices connected via SteamVR):\nhttps://user-images.githubusercontent.com/32321/155451982-8d21ca07-0178-4314-a4f2-8de56c275fa3.png"
+    "text": "Not applicable for this month."
   },
   {
-    "objectID": "changelog/2022/20220201-changelog.html#section-1",
-    "href": "changelog/2022/20220201-changelog.html#section-1",
-    "title": "V-Sekai Changelog - 2022-02",
+    "objectID": "changelog/2024/20240625-changelog.html",
+    "href": "changelog/2024/20240625-changelog.html",
+    "title": "Special Notice: V-Sekai 2023-2024",
     "section": "",
-    "text": "トカゲ — 10:28 We discussed with reduz implementation of retargeting for about 8 hours\nLyuma — 14:02 if anyone’s interested, you can read RocketChat from a browser: https://chat.godotengine.org/channel/animation?msg=JYqzF7xviTbh5zbmm"
+    "text": "Focused on Unidot and VRM (import pipeline).\nGodot 4.0 bugfixes and animation. Lots of engine dev.\nJuly–Aug spent time working on new CDN downloader and starting to rethink avatar controller.\n\n\n\n\n\nNew networking system committed to v-sekai-game and to a demo repository. It is missing basic features like support for pickup items so we haven’t enabled it yet.\n\n\n\n\n\nJan–Mar focused on FBX support and GDC.\nApr–May focused on updating Unidot to support FBX.\n\n\n\n\n\n\nSince early June, Lyuma started to revisit the incomplete code from 10 months ago. Lyuma is currently working on tracker binding / skeleton calibration (e.g. full body).\n4.3 release was delayed. Lyuma wants to release 4.3-compatible updates to Unidot and VRM.\nLyuma had some difficulties with API integration.\nSome Godot 4.3 bugs are still on Lyuma’s plate.\n\n\n\n\n\nNew in-game UI update. A draft was committed a couple weeks ago but saracen has been away on vacation.\nSaracen has also been working some more on physics sync.\nAPI/backend redesign.\n\n\n\n\n\nIntegration of UI code into game.\nNetwork syncing support of props/objects using the new system.\nIntegration of other game features between avatar_vr_demo (player controller) and v-sekai-game (legacy codebase).\nNew backend so we can reenable registration.\nSome OpenAPI wrapper so we can talk to the new backend.\n\nLyuma thinks we should put more focus on getting something lightweight we can run and play levels in. Lyuma is of half a mind to put more focus into making avatar demo runnable with custom content rather than fully integrating network syncing just so we can get off the ground more easily with content creation."
   },
   {
-    "objectID": "changelog/2022/20220201-changelog.html#section-2",
-    "href": "changelog/2022/20220201-changelog.html#section-2",
-    "title": "V-Sekai Changelog - 2022-02",
+    "objectID": "changelog/2024/20240625-changelog.html#stuff-we-did-over-the-past-year",
+    "href": "changelog/2024/20240625-changelog.html#stuff-we-did-over-the-past-year",
+    "title": "Special Notice: V-Sekai 2023-2024",
     "section": "",
-    "text": "Fire moved multiple projects issues to https://github.com/V-Sekai/V-Sekai/issues."
+    "text": "Focused on Unidot and VRM (import pipeline).\nGodot 4.0 bugfixes and animation. Lots of engine dev.\nJuly–Aug spent time working on new CDN downloader and starting to rethink avatar controller.\n\n\n\n\n\nNew networking system committed to v-sekai-game and to a demo repository. It is missing basic features like support for pickup items so we haven’t enabled it yet.\n\n\n\n\n\nJan–Mar focused on FBX support and GDC.\nApr–May focused on updating Unidot to support FBX."
   },
   {
-    "objectID": "changelog/2022/20220201-changelog.html#section-3",
-    "href": "changelog/2022/20220201-changelog.html#section-3",
-    "title": "V-Sekai Changelog - 2022-02",
+    "objectID": "changelog/2024/20240625-changelog.html#current-work",
+    "href": "changelog/2024/20240625-changelog.html#current-work",
+    "title": "Special Notice: V-Sekai 2023-2024",
     "section": "",
-    "text": "Lyuma changed RenIK to use set_bone_local_pose_override, and “hacked” skeleton’s transform to keep it centered on the hips, fixing the avatar disappearing when far from origin."
+    "text": "Since early June, Lyuma started to revisit the incomplete code from 10 months ago. Lyuma is currently working on tracker binding / skeleton calibration (e.g. full body).\n4.3 release was delayed. Lyuma wants to release 4.3-compatible updates to Unidot and VRM.\nLyuma had some difficulties with API integration.\nSome Godot 4.3 bugs are still on Lyuma’s plate."
   },
   {
-    "objectID": "changelog/2022/20220201-changelog.html#section-4",
-    "href": "changelog/2022/20220201-changelog.html#section-4",
-    "title": "V-Sekai Changelog - 2022-02",
+    "objectID": "changelog/2024/20240625-changelog.html#other-projects-in-progress",
+    "href": "changelog/2024/20240625-changelog.html#other-projects-in-progress",
+    "title": "Special Notice: V-Sekai 2023-2024",
     "section": "",
-    "text": "We made a lot of progress yesterday: getting closer to OpenXR integration; fixed some issues with avatar uploading; and progress with WasGo, including the ability to create a Godot Callable which directly represents a WASM function"
+    "text": "New in-game UI update. A draft was committed a couple weeks ago but saracen has been away on vacation.\nSaracen has also been working some more on physics sync.\nAPI/backend redesign."
   },
   {
-    "objectID": "changelog/2022/20220201-changelog.html#section-5",
-    "href": "changelog/2022/20220201-changelog.html#section-5",
-    "title": "V-Sekai Changelog - 2022-02",
+    "objectID": "changelog/2024/20240625-changelog.html#wtfawry-what-do-we-need-to-get-v-sekai-game-working-with-the-new-architecture",
+    "href": "changelog/2024/20240625-changelog.html#wtfawry-what-do-we-need-to-get-v-sekai-game-working-with-the-new-architecture",
+    "title": "Special Notice: V-Sekai 2023-2024",
     "section": "",
-    "text": "Moved fire’s project notes to V-Sekai/V-sekai issues.\nCurl has been postponed.\nCvtt bc6, bc7 texture compression speedup by reducing quality has been merged. Updating groups."
+    "text": "Integration of UI code into game.\nNetwork syncing support of props/objects using the new system.\nIntegration of other game features between avatar_vr_demo (player controller) and v-sekai-game (legacy codebase).\nNew backend so we can reenable registration.\nSome OpenAPI wrapper so we can talk to the new backend.\n\nLyuma thinks we should put more focus on getting something lightweight we can run and play levels in. Lyuma is of half a mind to put more focus into making avatar demo runnable with custom content rather than fully integrating network syncing just so we can get off the ground more easily with content creation."
   },
   {
-    "objectID": "changelog/2022/20220201-changelog.html#section-6",
-    "href": "changelog/2022/20220201-changelog.html#section-6",
-    "title": "V-Sekai Changelog - 2022-02",
+    "objectID": "changelog/2024/20240101-changelog.html",
+    "href": "changelog/2024/20240101-changelog.html",
+    "title": "V-Sekai Changelog - January 2024",
     "section": "",
-    "text": "Wasgo go! Restored wasgo wasm execution."
+    "text": "Not applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nSecurity Best Practices: Applied security best practices as recommended by StepSecurity. (Commit: d641001)\n\nThis project does not adhere to Semantic Versioning.\n\n\n\n\n\nNot applicable for this month."
   },
   {
-    "objectID": "changelog/2022/20220501-changelog.html",
-    "href": "changelog/2022/20220501-changelog.html",
-    "title": "V-Sekai Changelog - 2022-05",
+    "objectID": "changelog/2024/20240101-changelog.html#released",
+    "href": "changelog/2024/20240101-changelog.html#released",
+    "title": "V-Sekai Changelog - January 2024",
     "section": "",
-    "text": "https://github.com/V-Sekai/godot-seurat is dependent on being able to fetch 16 bit float buffers https://github.com/godotengine/godot/issues/54122#issuecomment-1140414946.\n\n\n\n\nInvestigated technical art via breaking apart the cafe\nInvestigated DagAmendment for brush based refinement of csg shapes.\n\n\n\n\n\nCharacters now load but the pose is incorrect.\nMaps load from a new sdk uploader.\nThe content picker is bad and ugly but usable to pick maps to host and choose avatars.\nThe server sees all clients but the clients only see the server and not each other.\nThe vr pose is incorrect but you can see the error so it hasn’t catastrophically exploded.\n\n\n\n\nimage\n\n\n\n\n\nCompleted a first stage EWBIK inverse kinematics solver to the stage one which solves but doesn’t have constraints."
+    "text": "Not applicable for this month."
   },
   {
-    "objectID": "changelog/2022/20220501-changelog.html#section",
-    "href": "changelog/2022/20220501-changelog.html#section",
-    "title": "V-Sekai Changelog - 2022-05",
+    "objectID": "changelog/2024/20240101-changelog.html#unreleased",
+    "href": "changelog/2024/20240101-changelog.html#unreleased",
+    "title": "V-Sekai Changelog - January 2024",
     "section": "",
-    "text": "https://github.com/V-Sekai/godot-seurat is dependent on being able to fetch 16 bit float buffers https://github.com/godotengine/godot/issues/54122#issuecomment-1140414946."
+    "text": "Not applicable for this month.\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nSecurity Best Practices: Applied security best practices as recommended by StepSecurity. (Commit: d641001)\n\nThis project does not adhere to Semantic Versioning."
   },
   {
-    "objectID": "changelog/2022/20220501-changelog.html#section-1",
-    "href": "changelog/2022/20220501-changelog.html#section-1",
-    "title": "V-Sekai Changelog - 2022-05",
+    "objectID": "changelog/2024/20240101-changelog.html#previous-releases",
+    "href": "changelog/2024/20240101-changelog.html#previous-releases",
+    "title": "V-Sekai Changelog - January 2024",
     "section": "",
-    "text": "Investigated technical art via breaking apart the cafe\nInvestigated DagAmendment for brush based refinement of csg shapes."
+    "text": "Not applicable for this month."
   },
   {
-    "objectID": "changelog/2022/20220501-changelog.html#section-2",
-    "href": "changelog/2022/20220501-changelog.html#section-2",
-    "title": "V-Sekai Changelog - 2022-05",
+    "objectID": "changelog/2024/20240901-changelog.html",
+    "href": "changelog/2024/20240901-changelog.html",
+    "title": "V-Sekai Changelog - September 2024",
     "section": "",
-    "text": "Characters now load but the pose is incorrect.\nMaps load from a new sdk uploader.\nThe content picker is bad and ugly but usable to pick maps to host and choose avatars.\nThe server sees all clients but the clients only see the server and not each other.\nThe vr pose is incorrect but you can see the error so it hasn’t catastrophically exploded.\n\n\n\n\nimage"
+    "text": "Experimental (🧪): This stage is for features that are still being tested and may not be stable.\nFeature complete (🎯): This stage is for features that have all planned functionality implemented.\nBeta (🚧): This stage is for features that are largely complete but may still have bugs.\nGeneral release (🚀): This stage is for features that have been fully tested and are now released.\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\n\n\nWork in progress with humanoid muscle encoding to/from quaternion. We can use this in the future for more efficient network serialization (similar to ShaderMotion’s format, or networked IK)\nSome progress on CDN code to make it a bit more reliable and engineered. It supports both gltf and godot scene format.\nfire and fwsGonzo have been working hard on godot-sandbox, a scripting system which allows you to write C++ code which acts like GDScript, via a sandboxed risc-v VM\nIn terms of engine features, typed dictionaries are in! https://godotengine.org/article/dev-snapshot-godot-4-4-dev-2/ That said, code which uses typed dictionaries will be incompatible with Godot 4.3 and earlier.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nSecurity Best Practices:\n\nThis project does not adhere to Semantic Versioning.\n\n\n\n\n\nNot applicable for this month."
   },
   {
-    "objectID": "changelog/2022/20220501-changelog.html#section-3",
-    "href": "changelog/2022/20220501-changelog.html#section-3",
-    "title": "V-Sekai Changelog - 2022-05",
+    "objectID": "changelog/2024/20240901-changelog.html#released",
+    "href": "changelog/2024/20240901-changelog.html#released",
+    "title": "V-Sekai Changelog - September 2024",
     "section": "",
-    "text": "Completed a first stage EWBIK inverse kinematics solver to the stage one which solves but doesn’t have constraints."
+    "text": "Not applicable for this month."
   },
   {
-    "objectID": "changelog/2022/20221101-changelog.html",
-    "href": "changelog/2022/20221101-changelog.html",
-    "title": "V-Sekai Changelog - 2022-11",
+    "objectID": "changelog/2024/20240901-changelog.html#unreleased",
+    "href": "changelog/2024/20240901-changelog.html#unreleased",
+    "title": "V-Sekai Changelog - September 2024",
     "section": "",
-    "text": "v-sekai-game-bug\n\n\n\n\n\nopenxr_showing\n\n\nRestored V-Sekai-Game home.\nWorked on EWBIK as a git branch.\n\n\n\nGame releases are working again.\n\n\n\nV-Sekai-game Player spawning should be working again (see their name tag at least). There’s an issue with the default sky_celebration map caused by “TestEntity” which has scene_file_path==“” and that breaks the validation logic, preventing the player from spawning, and most default maps don’t work. You need to use Mobile Dragon Shop (very dark) or Tokyo Map\nNote that avatars are currently not working. I think I’m getting closer to identifying where the validation is causing trouble.\n\n\nWe are working on a v2 of the network architecture based on Godot’s network spawn & sync system, so a lot of the code I’m editing right now is kind of legacy at this point. The new network implementation should drastically simplify the code and eliminate dozens of complex GDScript files from being needed. I still want to get this demo stable, since we will still be using the player controller and avatar loader from it\n\n\n\nVSK Tokyo Map\n\n\nThe new v2 network demo can be found at https://github.com/V-Sekai/net_demo if you’re curious. There’s no VR support planned for net_demo, but it should serve as a strong foundation going forward.\nAvatars should show up again. There was some code mistake that triggered only when the default “mirror” was disabled and caused avatars not to instantiate, but I didn’t notice because I had turned it on in my checkout\nI also fixed the default sky celebration map\nAvatar bone rotations are currently broken with this setup. Seems like the head always faces a certain direction:\n\n\n\nAvatar bone rotations are broken"
+    "text": "Work in progress with humanoid muscle encoding to/from quaternion. We can use this in the future for more efficient network serialization (similar to ShaderMotion’s format, or networked IK)\nSome progress on CDN code to make it a bit more reliable and engineered. It supports both gltf and godot scene format.\nfire and fwsGonzo have been working hard on godot-sandbox, a scripting system which allows you to write C++ code which acts like GDScript, via a sandboxed risc-v VM\nIn terms of engine features, typed dictionaries are in! https://godotengine.org/article/dev-snapshot-godot-4-4-dev-2/ That said, code which uses typed dictionaries will be incompatible with Godot 4.3 and earlier.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nSecurity Best Practices:\n\nThis project does not adhere to Semantic Versioning."
   },
   {
-    "objectID": "changelog/2022/20221101-changelog.html#section",
-    "href": "changelog/2022/20221101-changelog.html#section",
-    "title": "V-Sekai Changelog - 2022-11",
+    "objectID": "changelog/2024/20240901-changelog.html#previous-releases",
+    "href": "changelog/2024/20240901-changelog.html#previous-releases",
+    "title": "V-Sekai Changelog - September 2024",
     "section": "",
-    "text": "v-sekai-game-bug\n\n\n\n\n\nopenxr_showing\n\n\nRestored V-Sekai-Game home.\nWorked on EWBIK as a git branch."
+    "text": "Not applicable for this month."
   },
   {
-    "objectID": "changelog/2022/20221101-changelog.html#section-1",
-    "href": "changelog/2022/20221101-changelog.html#section-1",
-    "title": "V-Sekai Changelog - 2022-11",
+    "objectID": "changelog/2021/20211001-changelog.html",
+    "href": "changelog/2021/20211001-changelog.html",
+    "title": "V-Sekai Changelog - 2021-10",
     "section": "",
-    "text": "Game releases are working again."
+    "text": "V-Sekai Changelog - 2021-10\n\n2021-10-31 19:30:30Z fire: https://twitter.com/reduzio/status/1454867881771024391?s=20\n2021-10-31 17:12:51Z fire: Instruction unclear. Hair stuck in gentle breeze. https://github.com/fire/TressFX-OpenGL See releases for a zip. https://cdn.discordapp.com/attachments/836651615532482611/904417650510295060/2021-10-31_10-09-56.mp4\n2021-10-31 04:08:23Z fire: Confirmed fixed my screenshots system.\n2021-10-30 18:18:28Z fire: :danceblob:\n2021-10-30 18:17:58Z fire: aha. yes. https://github.com/godotengine/godot/pull/54427\n2021-10-30 17:59:04Z fire: Restored theme generator for groups. [reverted to editor theme] Needs time to debug.\n2021-10-30 06:03:59Z fire: Early builds are testable\n2021-10-30 02:20:34Z lyuma: “The VRM avatar converter has been updated at https://github.com/V-Sekai/vsk_vrm_avatar_tool and made to work with the new rotation/scale/blend_shape tracks. (generated scenes duplicate all resources, so make sure to not save as”“.tscn”“)” https://cdn.discordapp.com/attachments/836651615532482611/903830713009311754/unknown.png\n2021-10-29 23:28:11Z fire: Character translation movement now works. [WASD]\n2021-10-29 20:59:18Z fire:  HungryProton pushed the beginning of the 4.0 port to the refactoring-4.0 branch\n2021-10-29 16:02:35Z fire: From Mux and related to Godot XR This is so much fun: https://youtu.be/UxZj8OOCgY4\n2021-10-29 01:42:32Z lyuma: Here’s a video showing multiple players moving around over the network! and made it right side up by not calling set_vflip(true)! https://cdn.discordapp.com/attachments/836651615532482611/903458754262089728/vsekaimultiplayer_2021-10-28.mp4 🎉 (1)\n2021-10-29 01:26:17Z lyuma: “We might all be in error avatars, and the world might be upside down….. But. We have networking!!! (This is the first time we’ve successfully made a multiplayer connection on Godot 4 pre-alpha with Vulkan!)” https://cdn.discordapp.com/attachments/836651615532482611/903454660243894352/unknown.png\n2021-10-28 09:40:10Z lyuma: https://media.discordapp.net/attachments/659137056991346708/903093451560714280/unknown.png\n2021-10-27 19:54:44Z fire: Checked material settings Lyuma. Pushed the updates.\n2021-10-27 18:22:01Z fire: Lyuma ninja and ccache oh my. https://github.com/V-Sekai/godot/tree/ninja-ccache Based on work by dmoody256\n2021-10-27 16:31:59Z fire: Great work humbletim https://github.com/omigroup/omi-blender-gltf/pull/1\n2021-10-27 01:47:49Z fire: I un-archived HungryProton’s work, made a build and duplicated some trash cans. https://cdn.discordapp.com/attachments/836651615532482611/902735304228737094/unknown.png\n2021-10-25 19:59:28Z fire: Rotation mode pr merged. https://github.com/godotengine/godot/pull/54222 Lod added 🦎 (1)\n2021-10-25 12:23:37Z fire: Openvr update from mux\n2021-10-25 06:39:34Z lyuma: Updated some more scripts to work with the latest engine. the groups demo is still pink with looping physics sounds, though moving the mouse appears to pan the audio, so there’s something moving somewhere\n2021-10-24 01:37:02Z fire: “followed up on a design for duplicated blendshapes Lyuma korewaChino EIREXE https://github.com/godotengine/godot/issues/54062”\n2021-10-24 01:21:56Z fire: Tested animation compress. was a bit slow\n2021-10-24 01:12:26Z fire: Moved key-frame reduce to 4.0 but it still has fiddly test cases. Don’t want to debug, but leaving it here. https://github.com/V-Sekai/godot/commits/keyframe-reduce Dropping it.\n2021-10-23 15:25:29Z fire: https://twitter.com/smallseasonsbot/status/1451929853565890563?s=20\n2021-10-23 08:08:18Z fire: https://cdn.discordapp.com/attachments/836651615532482611/901381505526415360/unknown.png\n2021-10-23 06:18:32Z fire: sync with samsung thorvg team need pr review about paint replacement through iteration for color replacement\n2021-10-23 01:48:51Z fire: Got godot speech C++ module to compile. At some point in the future need to try uncompressed audio after the api changes. There’s a test project. 🗣️ (2)\n2021-10-23 00:36:32Z fire: Extracting godot-speech into a C++ module\n2021-10-23 00:25:44Z fire: Lyuma told me about this tool. So cleaned it a bit https://github.com/V-Sekai/V-Sekai-Blender-tools/tree/main/addons/ApplyModifierForObjectWithShapeKeys\n2021-10-21 03:27:13Z lyuma: fire made a lot of progress debugging the frame lag and random hangs. we have mitigations for some issues, but might not be fully correct\n2021-10-20 07:26:46Z fire: VERY POOR 1 FRAME STUTTER Got the sample working with our own build of the openvr gdextension. https://github.com/V-Sekai/v-sekai-openvr-sample/releases/tag/v0.2 Includes the godot 4 editor.\n2021-10-18 16:33:47Z fire: https://deepmind.com/blog/announcements/mujoco\n2021-10-18 13:59:41Z fire: mux offers to send his working openvr as an archive. He found some bugs with exporting gdextensions\n2021-10-18 05:26:43Z fire: cyberpunkmermaid#6171 interested in clothing for avatars at omigroup\n2021-10-17 01:02:32Z fire: https://github.com/ubisoft/mixer/pull/27\n2021-10-17 01:01:54Z fire: Debugged why mixer crashes on 2.93 did not fix but worked around\n2021-10-16 02:52:17Z fire: I am satisfied. Found the bug. https://github.com/godotengine/godot/pull/53865\n2021-10-16 00:33:27Z fire: What can we do to speed up our processes? https://scattered-thoughts.net/writing/speed-matters/\n2021-10-16 00:22:51Z lyuma: Updated Unidot Importer to work with latest master. Godot has gotten quite a lot faster it feels like\n2021-10-15 23:05:50Z fire: https://github.com/godotengine/godot/pull/53821#issuecomment-944785300\n2021-10-15 22:29:11Z fire: “https://github.com/V-Sekai/godot-4-animation-vrm-sample\n\nCurrently the root motion is on the hips and not on the root bone so it’s a bit funny”\n\n2021-10-15 22:22:01Z lyuma: “Rumors of a Godot 4 alpha are beginning to emerge. From Akien: &gt; New 4.0 build which is not alpha yet hohoho https://downloads.tuxfamily.org/godotengine/testing/4.0/4.0-dev.20211015/\n\nSome hints that it could be ““a few days more to mature”” beyond ““this week”” so there’s a chance of next week even!”\n\n2021-10-15 14:10:43Z fire: https://github.com/godotengine/godot/pull/53833 📽️ (1),🎞️ (1),🧹 (1)\n2021-10-15 01:33:14Z fire: https://github.com/godotengine/godot/issues/53823 Saracen PREVIEWS ARE FIXED 🔥 👍 (2)\n2021-10-14 15:08:32Z fire: Watching https://vive.com event.\n2021-10-14 14:12:59Z fire: Typed a plan for EWBIK work https://github.com/godot-extended-libraries/ewbik/issues/6\n2021-10-13 11:49:07Z fire: Worked on トカゲ VRM-like rotational rest pose baking https://github.com/V-Sekai/godot/tree/bake-rests\n2021-10-13 11:03:55Z fire: Skeleton split transform 3d merged from reduz\n2021-10-13 09:20:44Z fire: Updated Lyuma https://github.com/V-Sekai/godot/tree/groups-4.x-remove-separate-gltf-bake\n2021-10-13 04:57:28Z fire: Updated https://github.com/V-Sekai/godot/tree/rot-interpolate\n2021-10-12 10:54:44Z fire: Akien mentioned libacktrace\n2021-10-11 18:46:53Z lyuma: “Spent all day researching nonunknown’s negative scale issue: https://github.com/godotengine/godot/pull/53642#issuecomment-940357171 I think I have a pretty good understanding of why it breaks in Godot (except cull_back meshes) and what solutions are possible/feasible.”\n2021-10-11 15:57:30Z fire: https://cdn.discordapp.com/attachments/836651615532482611/897150929911021619/unknown.png\n2021-10-11 15:03:44Z fire: Updated blockmesh models https://github.com/V-Sekai/art-blue-tin-fox-models/releases/tag/latest. Edited: Incorrect export. Exported again.\n2021-10-11 13:24:24Z fire: Restored compilation of lasso.\n2021-10-11 12:56:20Z fire: Today’s Godot Engine build tag https://github.com/V-Sekai/godot/releases/tag/groups-4.x.2021-10-11T123723Z\n2021-10-10 22:50:47Z fire: https://cdn.discordapp.com/attachments/836651615532482611/896892548528889896/unknown.png\n2021-10-10 22:48:25Z fire: Trialing windows 11 and WSL for CUDA on windows. It works\n2021-10-10 22:48:09Z fire: Silent Sure, at least the permission to use them and if it’s not too much effort.\n2021-10-10 10:18:21Z Silent#0264 Do you want the source text?\n2021-10-09 23:24:05Z fire: Lyuma EIREXE https://www.kickstarter.com/projects/lookingglass/looking-glass-portrait with https://github.com/CaptainProton42/GodotHoloPlay https://cdn.discordapp.com/attachments/836651615532482611/896538541402783774/unknown.png\n2021-10-09 18:21:42Z fire: Silent Trying to create your list of CC0, CC-BY avatars https://cdn.discordapp.com/attachments/836651615532482611/896462441221877790/unknown.png\n2021-10-09 18:20:55Z fire: Creating a list of VRM checking conditions. https://cdn.discordapp.com/attachments/836651615532482611/896462244378996756/unknown.png\n2021-10-08 17:31:13Z fire: https://twitter.com/smallseasonsbot/status/1446491101490081802?s=20\n2021-10-08 17:01:37Z fire: Does not support blend shapes in bake, but does in player.\n2021-10-08 17:00:47Z fire: See addons/miku_motion_bake/readme.md for instructions\n2021-10-08 17:00:26Z fire: Been working on baking from VMD to VRM. Promising. https://github.com/V-Sekai/MikuMotionVSekai\n2021-10-07 07:42:12Z fire: “youwin — Yesterday at 21:03 started work on an obs &lt;-&gt; godot integration using obs-websocket. Might be useful for tutorial makers or recording short demo clips of your game without requiring too much editing https://github.com/you-win/obs-websocket-gd” 👀 (3),👍 (1)\n2021-10-06 20:26:41Z fire: Notes from GDC - Genshin Impact: Building a Scalable AI System humbletim https://hackmd.io/SPqekctOQYS5vQ7w7glJ5A\n2021-10-06 20:10:50Z fire: https://github.com/godotengine/godot-proposals/issues/3394 reduz wrote a proposal for ellenhp\n2021-10-06 20:07:47Z fire: Decreasing GLB (probably VRM) sizes https://forum.playcanvas.com/t/tricks-to-decrease-morph-target-sizes/18628/9?u=chris\n2021-10-06 19:51:03Z fire: Trialing https://v-sekai.budibase.app Lyuma\n2021-10-06 19:34:12Z fire: Discussed with Ob5vr about blend shape baking. TODO: Get some GDC courses from The Last of Us Part 2 on SSD techniques.\n2021-10-06 19:21:20Z トカゲ: “Marged Skeleton Gizmo 🎉 https://github.com/godotengine/godot/pull/45699” gdhearteyes (1),PartyParrot (2),mikuleek (1),SkellyDance (1)\n2021-10-06 19:17:15Z fire: https://github.com/godotengine/godot/pull/53298\n2021-10-06 19:05:46Z fire: Also to bake blend shapes.\n2021-10-06 19:05:37Z fire: The goal is to remove the dem bones repo is remove FBX and ABC dependencies\n2021-10-06 19:04:50Z fire: https://github.com/V-Sekai/godot-dem-bones/tree/godot working on it for a few hours\n2021-10-06 19:01:30Z fire: Still working on a summary of UIUX proposals. https://hackmd.io/26BUnwWOSYuMFIvvpoLa5Q\n2021-10-06 13:18:17Z fire: https://github.com/godotengine/godot/pull/53473 Lyuma トカゲ 🆗 (1)\n2021-10-05 07:01:01Z fire: https://cdn.discordapp.com/attachments/836651615532482611/894841592505069599/unknown.png pog (2),😍 (2)\n2021-10-05 06:50:22Z lyuma: we can chat more about this in #server-backend\n2021-10-05 06:44:14Z fire: https://twitter.com/JenMsft/status/1445065715698962442?s=20\n2021-10-05 04:55:21Z fire: Donmcurdy chat about materialx in omigroup’s gltf extensions discord for a few hours ❤️ (2),👏 (2)\n2021-10-04 17:03:45Z fire: GLTF2 Document merged.\n2021-10-04 08:21:47Z lyuma: トカゲ let’s move this to #animation … but basically there are three different proposals from Reduz.\n2021-10-04 08:21:42Z トカゲ: So it should not support A pose -&gt; T pose\n2021-10-04 08:21:02Z トカゲ: If I understand correctly from my discussion with reduz, this implementation is pretty similar to the global transform in MMD\n2021-10-04 08:18:08Z lyuma: I believe this proposal is sort of a generalization of the retargeting system you might find in Unity, without going into specifics on the implementation of the retargeting: what Reduz calls a “Retargeter” is what you would call an “Avatar” in Unity.\n2021-10-04 08:15:31Z lyuma: “Reduz made a new proposal related to Animations: https://github.com/godotengine/godot-proposals/issues/3379”\n2021-10-04 05:35:48Z fire: https://github.com/godotengine/godot/pull/50964 Updated libcurl. Ready for merging.\n2021-10-04 01:59:46Z fire: Branch created https://github.com/V-Sekai/godot/tree/remove-skeleton-ik-3d\n2021-10-03 19:51:15Z fire: https://www.campaign.viveport.com/step-into-catart\n2021-10-03 19:49:11Z fire: https://autodesk-forks.github.io/MaterialX/ materialx web viewer\n2021-10-03 19:48:47Z fire: https://cdn.discordapp.com/attachments/836651615532482611/894310029715464262/unknown.png\n2021-10-03 05:35:20Z lyuma: This isn’t really a discussion channel so I’ll continue in #server-backend\n2021-10-03 04:37:57Z fire: v-sekai.org’s ssl cert will expire in 2 days\n2021-10-02 19:26:59Z fire: https://github.com/godotengine/godot/pull/53337 merged\n2021-10-02 16:51:51Z fire: Need to a tech limits design. The Last of Us Part II Abby has a total joint count of 1075 Animated - 520 (includes face) and 555 procedural.\n2021-10-02 16:34:45Z fire: “Everything is back to working. Yesterday everything broke ref: meshes disappeared and crash with skeleton because minimum verts. Fixes from Lyuma. Also tested occlusion culling”\n2021-10-02 14:35:34Z fire: Lyuma The platform creator of Tokyo Game Show 2021 liked my post. https://cdn.discordapp.com/attachments/836651615532482611/893868818038915132/unknown.png\n2021-10-02 12:52:57Z Saracen: Cool, I’ll read through it later today\n2021-10-02 12:48:43Z lyuma: “Saracen fire New proposal by reduz for animation import without bone rest pose: https://github.com/godotengine/godot-proposals/issues/3377”\n2021-10-02 02:32:49Z fire: https://github.com/godotengine/godot-proposals/issues/3375\n2021-10-01 07:54:55Z Saracen: Neat!"
   },
   {
-    "objectID": "changelog/2022/20221101-changelog.html#lyuma",
-    "href": "changelog/2022/20221101-changelog.html#lyuma",
-    "title": "V-Sekai Changelog - 2022-11",
+    "objectID": "changelog/2021/20210801-changelog.html",
+    "href": "changelog/2021/20210801-changelog.html",
+    "title": "V-Sekai Changelog - 2021-08",
     "section": "",
-    "text": "V-Sekai-game Player spawning should be working again (see their name tag at least). There’s an issue with the default sky_celebration map caused by “TestEntity” which has scene_file_path==“” and that breaks the validation logic, preventing the player from spawning, and most default maps don’t work. You need to use Mobile Dragon Shop (very dark) or Tokyo Map\nNote that avatars are currently not working. I think I’m getting closer to identifying where the validation is causing trouble.\n\n\nWe are working on a v2 of the network architecture based on Godot’s network spawn & sync system, so a lot of the code I’m editing right now is kind of legacy at this point. The new network implementation should drastically simplify the code and eliminate dozens of complex GDScript files from being needed. I still want to get this demo stable, since we will still be using the player controller and avatar loader from it\n\n\n\nVSK Tokyo Map\n\n\nThe new v2 network demo can be found at https://github.com/V-Sekai/net_demo if you’re curious. There’s no VR support planned for net_demo, but it should serve as a strong foundation going forward.\nAvatars should show up again. There was some code mistake that triggered only when the default “mirror” was disabled and caused avatars not to instantiate, but I didn’t notice because I had turned it on in my checkout\nI also fixed the default sky celebration map\nAvatar bone rotations are currently broken with this setup. Seems like the head always faces a certain direction:\n\n\n\nAvatar bone rotations are broken"
+    "text": "V-Sekai Changelog - 2021-08\n\n2021-08-31 23:04:24Z fire: Did a few hours of work learning Blender with Cleam last night. Did some testing of Tokage’s skeleton gizmo.\n2021-08-30 17:09:35Z MMMaellon#2053 nice\n2021-08-30 16:13:28Z Saracen: Got MMMaellon’s RenIK system compiling for 4.x now. It’s also worth noting that the new SkeletonModifierStack is now mainlined in 4.0, so my next task with this will be to port RenIK to using this system. The final step will be porting it to the new GDExtension system as that becomes more viable\n2021-08-30 02:31:12Z fire: updated our engine + AUTHORITY changes + libcurl\n2021-08-28 22:01:33Z fire: Left is blend shape / right is bones. https://cdn.discordapp.com/attachments/836651615532482611/881297479033827388/2021-08-28_15-00-45.mp4\n2021-08-28 21:52:02Z fire: I got dembones working. ./DemBones -i=\"Face_Geom.fbx\" -a=\"Face_Anim.abc\" --bindUpdate=2 -o=\"Decomposition_20_grouped_face.fbx\" --nnz=8 -b=256 Note that the corresponding fbx is 0.01 scale while the alembic is in meters. The RMSE = 0.00433256 must be this low. Especially do not pass DemBones if the RMSE is like 3.5. Next thing is to integrate an existing 3d skeleton.\n2021-08-28 21:28:03Z fire: Jonbonazza said he resolved the ipv6 dns problem and the last remaining steps are to get to build for all platforms. Details for a future iFire.\n2021-08-28 06:24:28Z fire: https://twitter.com/mux213/status/1431474082885734403?s=20 🥽 (2)\n2021-08-27 23:20:23Z fire: troubles\n2021-08-27 23:20:17Z fire: Restoring spatial audio after ellenhp’s pr\n2021-08-27 14:15:31Z fire: https://cdn.discordapp.com/attachments/836651615532482611/880817809737805824/image0.jpg\n2021-08-27 09:17:32Z fire: https://cdn.discordapp.com/attachments/836651615532482611/880742820812562432/unknown.png\n2021-08-27 09:10:49Z fire: https://github.com/godotengine/godot/pull/51985\n2021-08-27 08:26:02Z lyuma: hosting seems to kind of work but plays constant physics sounds, so it’s likely that scenes are loading, but I can’t see anything.\n2021-08-27 08:23:56Z lyuma: Made some further progress: https://cdn.discordapp.com/attachments/836651615532482611/880729330035077120/unknown.png pink (2)\n2021-08-27 05:35:53Z lyuma: we do things because they are crazy\n2021-08-27 05:35:15Z fire: https://pbs.twimg.com/media/E3OC-r7WQAUvy5l.jpg ⬆️ (1)\n2021-08-27 05:26:19Z lyuma: https://cdn.discordapp.com/attachments/836651615532482611/880684632553705482/unknown.png\n2021-08-27 01:43:10Z fire: https://github.com/ValveSoftware/openvr/tree/master/samples/helloworldoverlay steam overlay\n2021-08-26 20:20:03Z fire: https://thume.ca/2017/06/17/tree-diffing/ useful comparing two visual script trees or two godot engine scenes or maybe skeletons!?s\n2021-08-26 19:21:48Z lyuma: Quilkin thread\n2021-08-26 16:01:57Z fire: https://medium.com/embarkstudios/say-hi-to-quilkin-an-open-source-udp-proxy-88577c795204\n2021-08-26 14:36:54Z fire: https://cdn.discordapp.com/attachments/836651615532482611/880460804351205386/image0.jpg\n2021-08-26 11:44:22Z lyuma: With the Autoload ordering fix applied, groups client now gets to the loading bar and is able to fade out after loading some plugins, but ends up at a black screen without showing the menu screen.\n2021-08-26 10:07:46Z lyuma: “Write PR to fix Autoload sort order (e.g. at runtime) https://github.com/godotengine/godot/pull/52122”\n2021-08-26 01:30:05Z fire: Got together with CLEAM and got a schedule to work on Blender artwork. First thing is teach ourselves how to make a Virtual Market quality character. https://cdn.discordapp.com/attachments/836651615532482611/880262796661624912/Artboard-11.png 👍🏿 (2)\n2021-08-24 16:56:46Z Saracen: https://github.com/godotengine/godot/pull/52071 gddab (3)\n2021-08-24 16:56:45Z Saracen: GDScript 2.0 bug fixes\n2021-08-24 16:10:48Z fire: https://cdn.discordapp.com/attachments/836651615532482611/879759658393403402/unknown.png\n2021-08-24 16:07:44Z fire: MaterialX gltf2 bake with https://github.com/fire/MaterialX/tree/standalone-gltf https://cdn.discordapp.com/attachments/836651615532482611/879758889032253501/unknown.png\n2021-08-24 15:47:33Z fire: draft of materialx spec written https://github.com/fire/glTF/tree/materialx and draft of stand alone baker https://github.com/fire/MaterialX/tree/standalone\n2021-08-23 16:44:55Z fire: Spent some time trying to bake the animations of the face going from 0 to 1 for Angry face on three_girl vrm and dem bones could not work. Bake blend shapes to skeletal animation. Did not succeed.\n2021-08-22 07:59:23Z fire: remotes/bruvzg/msdf_fonts2\n2021-08-20 19:09:33Z fire: https://github.com/godotengine/godot/pull/44399\n2021-08-20 19:08:25Z fire: https://github.com/vnen/godot-cpp/tree/gdnative-extensions\n2021-08-20 08:30:17Z fire: https://github.com/godotengine/godot/pull/51908 new MSDF Branch\n2021-08-19 15:58:27Z fire: https://cdn.discordapp.com/attachments/836651615532482611/877944612508008468/2021-08-19_08-57-17.mp4\n2021-08-19 15:37:58Z fire: https://user-images.githubusercontent.com/7645683/109620721-debe3f00-7b42-11eb-870b-c2207812a03f.mov\n2021-08-19 15:33:20Z fire: Testing MSDF branch 2 https://github.com/bruvzg/godot/tree/msdf_fonts2.\n2021-08-16 15:03:26Z fire: Nikumaru font: https://cdn.discordapp.com/attachments/836651615532482611/876843603413069884/unknown.png\n2021-08-16 14:36:27Z lyuma: Including 3d modifier?? ⭐ (2),gdbee (2),🍦 (2),🔥 (2)\n2021-08-16 14:04:39Z fire: ik 3d is merged!!!!!\n2021-08-14 00:04:31Z fire: Updated https://github.com/fire/looking-glass/ Godot Engine demo. The fix was making the app fullscreen\n2021-08-14 00:00:04Z fire: Connected with Emili Yu https://ns.inria.fr/d3/CASSIE/\n2021-08-13 23:59:33Z fire: Connected with FreeMocap https://twitter.com/JonMatthis\n2021-08-13 06:07:51Z lyuma: “&gt; It’s coming! The Virtual Market 6 will commence in 18 hours! &gt; The opening ceremony will be held on JST 9:30 am, UTC 0:30 am, Eastern 8:30 pm. &gt; https://www.youtube.com/watch?v=XrTj_-Yg7AA”\n2021-08-13 04:21:30Z fire: https://twitter.com/Lyuma2d/status/1426005291573813249?s=20\n2021-08-11 22:48:18Z fire: https://twitch.tv/freemocap Jon’s gonna stream tomorrow, Thursday from roughly 4-6pm (Eastern US time)\n2021-08-11 15:37:36Z fire: For cloud and edge computing, made an iso that’ll automatically install k3s with proper keying if we reboot once manually to remove the iso. https://github.com/V-Sekai/k3s-auto-start-gitops\n2021-08-10 22:56:35Z Saracen: Looking into this right now (https://github.com/godotengine/godot/issues/47885), discussion will be on RocketChat #scripting\n2021-08-10 19:47:41Z lyuma: Congrats!!\n2021-08-10 19:47:30Z fire: https://github.com/godotengine/godot/pull/49343/files merged 👏 (2)\n2021-08-05 06:51:43Z MMMaellon#2053 that’s very exciting hype (3),gdhollidays (2)\n2021-08-05 06:31:39Z lyuma: but this is a huge milestone for us: we can now open the project cleanly and fix stuff\n2021-08-05 06:31:02Z lyuma: Groups project now opens on Godot 4 without errors! We’re still getting a few script errors here and there while exporting, and we see some issues related to loading openvr; and a godot bug related to extending a “res://” url might be affecting exports\n2021-08-05 02:16:43Z lyuma: We’re still missing ports of GDNative code: godot speech and open?r\n2021-08-05 02:16:04Z lyuma: Finished with the majority of the port of 430 gdscript files. We have builds running, though godot4 has bugs in export builds with preload() of tscn files so I’ll try changing those to regular load()\n2021-08-05 01:14:44Z lyuma: V-Sekai in godot 4 is getting my avatars! https://cdn.discordapp.com/attachments/836651615532482611/872648788672647208/unknown.png vrcExclaim (1)\n2021-08-04 18:52:42Z fire: Wasm emulation of fedora 33 via RISCV64. Related to Stellar Mesh discussion. https://cdn.discordapp.com/attachments/836651615532482611/872552648182751252/unknown.png\n2021-08-04 13:19:32Z fire: Trialing new github actions for all of our modules\n2021-08-02 22:17:37Z fire: Next year Siggraph is in Vancouver 🇨🇦\n2021-08-02 20:45:24Z fire: https://cdn.discordapp.com/attachments/836651615532482611/871856235098562621/unknown.png\n2021-08-02 20:14:08Z lyuma: Siggraph 2021 is the week of August 9 - August 13\n2021-08-02 19:48:01Z fire: Siggraph 2021! invited to discord\n2021-08-02 05:49:11Z fire: Worked on gltf2 export in Godot Engine master\n2021-08-02 05:48:57Z fire: Worked with Nikitalita on visual regression testing of vulkan"
   },
   {
-    "objectID": "changelog/2022/20220801-changelog.html",
-    "href": "changelog/2022/20220801-changelog.html",
-    "title": "V-Sekai Changelog - 2022-08",
+    "objectID": "changelog/2021/20211101-changelog.html",
+    "href": "changelog/2021/20211101-changelog.html",
+    "title": "V-Sekai Changelog - 2021-11",
     "section": "",
-    "text": "Migrated vsk_avatar and vsk_vrm_avatar_tool to import retargeter. There is still pending work to apply the 180 degree rotation during VRM import but we’re pretty close. Newly uploaded avatars should work, but after we fix the z-forward issue we may want to upload again.\n\n\n\nNothing to see here, got godot 4 engine updated to the latest master.\n\n\n\nMany changes to the Godot Engine 4 master retargeting and animation system were added."
+    "text": "iFire: Added https://github.com/V-Sekai/v-sekai-proposals/blob/master/CHANGELOG.md\niFire: Update FBX2glTF to create packaged release tags.\niFire: Wild goose chased godot 3.4 webxr. the goose flew away this time.\niFire: Evaluating Godot 4 for the web. 2D only. Builds in a bit from itch and cicd\niFire: I’ll be arranging the OMI gltf2 group meeting tomorrow. It’s currently wednesday. Need figure out what people are doing and reflect that.\niFire: https://github.com/godotengine/godot/pull/54886 Lyuma pr for blend i/o. Pending pr proposal. Discussed with the Godot Discord community and with Reduz.\nLyuma: the above is in reference to the .blend, .bvh (via bleneer) and .usdz (via blender) importers for Godor 4 and 3.3+\niFire: Ported and split the blender assisted addons into 6 branches and 3 repos\ntheoway: Visual script updates. https://github.com/godotengine/godot-proposals/issues/3548\niFire: Ventured into MaterialX slack channel and asked for answers. Answers were found.\nLyuma: Wrote a simple .bvh importer for Godot using @iFire [He/Him]’s blender importer as a base (importing using blender).\niFire: Onboarded a few people onto Godot 4 Groups from older versions\niFire: Finishing touches on blend import for Godot Engine\nLyuma: reworked scene export\n\n\n\niFire: Builds of fbx2gltf from github cicd are now at https://github.com/V-Sekai/FBX2glTF/releases\niFire: Updated the godot branch. There was some some difficult with the blend-io branch so I merged it with other branch import something\nMMMaellon: Didn’t we use to have an IK channel? Anyway here’s some of my ideas on how I plan to revamp RenIK. I’m still hoping that EWBIK takes over RENIK’s IK solving one day, so I’m focusing on improving the walk cycle and leaving IK solving alone https://mmmaellon.notion.site/Semi-Deterministic-Walk-Cycles-dbe1dcaa307e4fb9b85dd6ee920de20c\niFire — 07/11/2021: Groups update to the latest Godot. 1. intersect rays api changed. 2. misc crash if precondition fails return Oops forgot to upload a few branches.\niFire — 08/11/2021: https://github.com/V-Sekai/godot-blender Now works on my Linux. Need some testing for Windows and Mac. Save a blend file into the godot project and it’ll be openable as scene through tricks.\niFire — 08/11/2021: Will be around in voice call for an 30m to 1 hour.\niFire — 09/11/2021: Cleared some godot engine github backlog. Wheeee\niFire: Mixer bug fixes have been merged https://github.com/ubisoft/mixer\n\n\n\n\n\n\nAdded a change log\n2021-11-03 21:01:24Z fire: iFire Reviewed Visual Script work prs https://github.com/godotengine/godot/pull/54564 https://github.com/godotengine/godot/pull/52218"
   },
   {
-    "objectID": "changelog/2022/20220801-changelog.html#lyuma-04082022",
-    "href": "changelog/2022/20220801-changelog.html#lyuma-04082022",
-    "title": "V-Sekai Changelog - 2022-08",
+    "objectID": "changelog/2021/20211101-changelog.html#z",
+    "href": "changelog/2021/20211101-changelog.html#z",
+    "title": "V-Sekai Changelog - 2021-11",
     "section": "",
-    "text": "Migrated vsk_avatar and vsk_vrm_avatar_tool to import retargeter. There is still pending work to apply the 180 degree rotation during VRM import but we’re pretty close. Newly uploaded avatars should work, but after we fix the z-forward issue we may want to upload again."
+    "text": "Added a change log\n2021-11-03 21:01:24Z fire: iFire Reviewed Visual Script work prs https://github.com/godotengine/godot/pull/54564 https://github.com/godotengine/godot/pull/52218"
   },
   {
-    "objectID": "changelog/2022/20220801-changelog.html#ifire-he-him-26082022",
-    "href": "changelog/2022/20220801-changelog.html#ifire-he-him-26082022",
-    "title": "V-Sekai Changelog - 2022-08",
+    "objectID": "changelog/2021/20210701-changelog.html",
+    "href": "changelog/2021/20210701-changelog.html",
+    "title": "V-Sekai Changelog - 2021-07",
     "section": "",
-    "text": "Nothing to see here, got godot 4 engine updated to the latest master."
+    "text": "V-Sekai Changelog - 2021-07\n\n2021-07-30 23:27:44Z fire: Update https://github.com/V-Sekai/FBX2glTF/releases/tag/v2021-06-20T0053%2B0000 with a godot 4 project\n2021-07-30 23:27:32Z fire: Merged 3/5 prs related to gltf, colliders and RESET animation\n2021-07-28 23:15:15Z fire: https://github.com/godotengine/godot/pull/50964 Libcurl work from the net team\n2021-07-27 15:10:18Z fire: / https://cdn.discordapp.com/attachments/836651615532482611/869597574481449001/unknown.png\n2021-07-27 14:15:21Z fire: Working on CICD for https://github.com/V-Sekai/godot-hop-spin-dance as a preview for v-sekai 4\n2021-07-26 00:39:45Z fire: https://tenor.com/view/fun-lies-imlovingit-portal-itwouldbefuntheysaid-gif-4842907\n2021-07-26 00:22:35Z lyuma: ugly, but we do what we must\n2021-07-26 00:22:31Z lyuma: I was able to resolve autoload cycles by passing references by loading them in the right order, and passing in the out-of-order (cyclic) references as constructor arguments, referencing them with a prefix instead of the autoload name\n2021-07-26 00:21:40Z lyuma: There are still quite a few addons left, and then comes debugging\n2021-07-26 00:21:32Z lyuma: Made good progress on porting GDScript. I have most VSK* and sar1_ classes ported: https://cdn.discordapp.com/attachments/836651615532482611/869011521290764298/unknown.png\n2021-07-25 20:06:18Z fire: Worked with OMI to add OMI https://github.com/M3-org/awesome-metaverse/pull/4 to the list.\n2021-07-25 18:05:02Z Saracen: Nice!\n2021-07-25 18:00:45Z fire: Saracen Bugfix for _File. I’m able to open vrms again\n2021-07-23 20:10:25Z fire: https://cdn.discordapp.com/attachments/836651615532482611/868223549469511740/unknown.png\n2021-07-23 16:56:54Z fire: https://cdn.discordapp.com/attachments/836651615532482611/868174850005561374/unknown.png\n2021-07-23 16:56:33Z fire: https://twitter.com/MampelSkyliner Lyuma Trying to connect.\n2021-07-22 19:59:57Z fire: https://youtu.be/WBGkyqYEdTU From Mark Mandel\n2021-07-22 19:28:43Z fire: &gt; gizmo improvements are (finally) up for review 🙂 #50748\n2021-07-22 18:17:32Z fire: Did some research on ai planners. https://gist.github.com/fire/e5fd4fd3a943b76f3f1e4e76c305af0b\n2021-07-22 16:51:42Z fire: started moz hubs importer in godot engine master\n2021-07-22 16:42:11Z fire: collaborated with jonb on libcurl in Godot\n2021-07-22 00:05:41Z fire: OMI Meeting today. Debates are ongoing. No consensus.\n2021-07-20 18:29:32Z fire: Reduz wants to merge the real_t is double PRs soon. 🎆 🎆\n2021-07-20 00:01:16Z fire: Connected with https://twitter.com/lorenc_dan\n2021-07-19 23:21:35Z fire: https://github.com/KhronosGroup/glTF/pull/1955\n2021-07-19 23:01:08Z MMMaellon#2053 Have you guys messed with this engine before? Heard about it at work because Amazon made it https://o3de.org/ 👀 (1)\n2021-07-19 19:23:28Z fire: “&gt; iFire and I broke the ice, but feel this would be best served as a series of workshops together. We created this issue in the omigroup/gltf-extensions repo to track progress. https://github.com/omigroup/gltf-extensions/issues/3”\n2021-07-18 19:45:09Z Saracen: Put the Vket6 repo on GitLab. Right now, it’s just a straight port of the original, mostly making it work with Udon scripting, but I will explore changes which could be made for VKet6. https://gitlab.com/SaracenOne/vket6-vsk-booth/\n2021-07-16 17:41:08Z fire: Godot Networking meeting Saracen\n2021-07-15 23:45:34Z fire: Worked on glTF2 OMI_audio_emitter with humbletim\n2021-07-15 06:47:10Z Saracen: https://github.com/godotengine/godot/issues/50471\n2021-07-15 06:47:09Z Saracen: Logged this issue. Considering this one pretty crucial for V-Sekai’s 4.x port since the codebase heavily relies on dependent singletons\n2021-07-14 19:22:42Z fire: W3C - OMI GLTF extension working group created\n2021-07-14 19:22:23Z fire: https://cdn.discordapp.com/attachments/823417508417110026/864919725301432360/unknown.png\n2021-07-14 19:21:56Z fire: materialx pr merged\n2021-07-14 05:46:19Z fire: / /o/  ❤️ ❤️ ❤️ https://cdn.discordapp.com/attachments/836651615532482611/864744601017516042/unknown.png\n2021-07-14 03:32:32Z fire: https://cdn.discordapp.com/attachments/836651615532482611/864710936211750942/unknown.png\n2021-07-14 03:32:20Z fire: Saracen Lyuma We will be at this roundtable? https://cdn.discordapp.com/attachments/836651615532482611/864710886093619240/unknown.png\n2021-07-14 00:40:41Z fire: https://github.com/omigroup/OMI/issues/64 gltf2 proposal\n2021-07-13 21:05:10Z fire: Proposal for a materialx bsdf that works for gltf bsdf https://github.com/materialx/MaterialX/issues/653#issuecomment-879321877\n2021-07-13 12:18:26Z lyuma: Beware: autoload cycles are a problem: two files cannot reference each other without breaking the cycle in some way. Currently, I have about 7 references to EntityManager commented out from the network_manager addon, or else Godot hard crashes when loading the project.\n2021-07-13 12:16:42Z lyuma: “Pushed https://github.com/V-Sekai/godot-hop-spin-dance groups_test_project branch. The following addons now compile:\n\nentity_manager\ngd_util\ninput_manager\nmath_util\nmesh_combiner\nmodel_format\nnetwork_manager\nquentincaffeino-console\nsar1_log_manager\nstate_machine\nstatic_baker\nvsk_avatar (50% commented, must redo later)\nvsk_vrm_avatar_tool” ✨ (1)\n\n2021-07-13 02:01:04Z fire: Got static!\n2021-07-13 01:39:09Z fire: Can’t connect yet, but there’s less errors running\n2021-07-13 01:38:21Z fire: Worked on https://github.com/V-Sekai/godot_voip_experimental\n2021-07-11 21:54:33Z fire: https://github.com/V-Sekai/v-sekai-proposals/issues/34 Lyuma Wrote how to evaluate neural blendshapes\n2021-07-10 20:31:09Z fire: For next week I’m going to get a build of groupx-4.x to cicd and then start iterating on “Two person floating name tags in a networked Groups 4.x with the ability to pass beachballs”. I asked my friend gameplay programmer and we determined that waiting for all the things to port to Godot Engine 4 has a high latency. I’m trying a new approach of growing the code base feature by feature as it was done originally for 3.x.\n2021-07-10 20:22:34Z fire: Polishing https://github.com/godotengine/godot/pull/49645 for merge\n2021-07-09 21:04:20Z fire: Morning Meeting done with Reduz, Catania and Lyuma about Pose in 3d\n2021-07-07 18:40:06Z fire: Updated https://hackmd.io/C0oIi_vlRs6V8qa9ZCjxaw with the guessing “Blender edit” https://github.com/KhronosGroup/glTF-Blender-IO/pull/941\n2021-07-07 18:39:23Z fire: We talked about how “godot pose matcher” is an ok name for the tool\n2021-07-07 18:38:51Z Saracen: I’m going to try and build a test case for another bug in GodotPhysics and also start refactoring the avatar bone fixer from vsk_avatar into its own standalone addon with minimal dependencies.\n2021-07-07 18:38:31Z fire: Worked with tokage on bone rolls https://docs.google.com/spreadsheets/d/1j6Sq7-Iy_P3esTILySrqVQ91Hlq4MsEiI35X_R-NaiI/edit#gid=0\n2021-07-07 06:21:14Z fire: Merge pull request #50229 from reduz/fix-textures-not-updating Saracen Lyuma 👏 (2),pink (2)\n2021-07-07 06:01:10Z fire: https://cdn.discordapp.com/attachments/836651615532482611/862211623782711306/unknown.png\n2021-07-07 06:00:30Z fire: https://cdn.discordapp.com/attachments/598003845657788438/862209880990547968/fox_default_run.glb Fox is holding a leg.\n2021-07-07 05:59:29Z fire: https://github.com/godot-extended-libraries/godot-fire/tree/feature/bake-reset-anim Lyuma Saracen QA testing the RESET pose baker\n2021-07-06 18:11:18Z fire: Saracen was interested in my Hydro module.\n2021-07-06 18:11:02Z fire: Saracen and I were interested in GridMate interest management techniques\n2021-07-06 18:10:34Z fire: Evaluated o3de 1. GridMate as a college class !!!! 2. OIT (Transparency) 3. TressFX ??? 4. animation sync 5. behavior tree\n2021-07-05 21:07:53Z fire: “Did some work on physics collision bugs but didn’t complete. Sent to saracen. https://github.com/V-Sekai/godot/commit/99a9f79e25f7760cb5a0990e67545d78e9dd0423”\n2021-07-05 15:29:30Z fire: “I figured out the bug with the ewbik ui. need to separate the concept of the stored”“serialisable”” data vs the internal runtime data because the serialisable data can’t access the skeleton.”\n2021-07-03 23:41:32Z fire: worked with eron and also separately got the ik to not reset every solve on ewbik\n2021-07-02 07:14:33Z fire: https://github.com/materialx/MaterialX/pull/651 Standalone material baker\n2021-07-01 19:13:21Z fire: Vket6 booth summoning of discord here?!\n2021-07-01 15:35:11Z fire: Poked https://github.com/SigNoz/signoz/issues/193\n2021-07-01 14:48:52Z fire: Discussed with HumbleTim the concept of a source glb we run again as many individual solvers for the input data, if the input is solved and it passes QA, that is one that is the outputted.\n2021-07-01 14:22:16Z fire: https://github.com/materialx/MaterialX/issues/650#issuecomment-871921261\n2021-07-01 14:21:54Z fire: ThorVG now supports images! in svg"
   },
   {
-    "objectID": "changelog/2022/20220801-changelog.html#トカゲ",
-    "href": "changelog/2022/20220801-changelog.html#トカゲ",
-    "title": "V-Sekai Changelog - 2022-08",
+    "objectID": "changelog/2022/20220601-changelog.html",
+    "href": "changelog/2022/20220601-changelog.html",
+    "title": "V-Sekai Changelog - 2022-06",
     "section": "",
-    "text": "Many changes to the Godot Engine 4 master retargeting and animation system were added."
+    "text": "Updated this v-sekai.github.io website.\n\n\n\n\nHad a meeting with Lyuma, Fire, Sarcen, Silent and MMMaellon about the V-Sekai project.\nResolved apply style patches to 3d-audio.\nMake V-Sekai film tests with the new Godot Engine movie maker feature.\n\n\n\n\n\n\nFire collaborated on godot-snappy for object snapping https://github.com/jgillich/godot-snappy\nTry to integrate manifold again.\n\n\n\n\nhttps://gitlab.com/bramw/baserow/-/issues/998 Spent some documenting the baserow io system on Digital Ocean used to store in-progress art assets, data from research and 3d galleries.\nDonated research on avatar generation to the MIT-licensed project at https://github.com/AtlasFoundation/OpenCharacterCreator As part of: lightweight-quality-avatars\n\n\n\n\nLyuma uncommented some code in vsk_avatar/ik_space.gd to create IK tracking points on the server, to enable IK sync via server. TL;DR (Other peers can see other peers while connected to a server.)\nServer sync issue removed from todo list.\n\n\n\n\n\n\n\n\n\n\nid\nName\nNotes\nActive\n\n\n\n\n24\nVR smooth locomotion.\n\nTrue\n\n\n24\nVR smooth locomotion with blackout.\n\nTrue\n\n\n5\nGrab an object.\n\nTrue\n\n\n17\nSupport large uploads to the content distribution network.\n\nTrue\n\n\n19\nMake a video of entering the world and grabbing objects.\n\nTrue\n\n\n\nTrialing a fix for issue of SDFGI on VR. Was poor. Had to backout branch."
   },
   {
-    "objectID": "changelog/2022/20221001-changelog.html",
-    "href": "changelog/2022/20221001-changelog.html",
-    "title": "V-Sekai Changelog - 2022-10",
+    "objectID": "changelog/2022/20220601-changelog.html#section",
+    "href": "changelog/2022/20220601-changelog.html#section",
+    "title": "V-Sekai Changelog - 2022-06",
     "section": "",
-    "text": "Lyuma — 01/10/2022 I have pushed internal and external resource whitelisting at the ResrouceLoader (ResourceFormatLoaderBinary) level as a Godot engine patch.\n\nHere’s an example of what gets printed when the above script with OS.alert() attempts to be loaded\nERROR: user://asset_cache/81dd12d03686\n0a08faba06a1b47a3a29.scn:Resource of unrecognized type in file: GDScript.\n   at: load (core/io/resource_format_binary.cpp:789)\nERROR: Failed loading resource: user://asset_cache/81dd12d036860a08faba06a1b47a3a29.scn. Make sure resources have been imported by opening the project in the editor at least once.\nNote that I was forced to rebase to the latest build which includes the new build system (target=editor) most of the code I changed is in the private gitlab repo. once things stabilize and we get the build system up and running again, next step is to publish the remainder of the code on github\n\ngroups-4.x (and staging) were updated to latest. I attempted to update GoCD, but it’s a bit of a yolo merge, since a few pieces all had to be updated at once due to new scons target=editor argument we need to follow https://ci.v-sekai.cloud/ (log in as guest) and test the release builds\n\n\nexport builds are being created again with the new scons naming scheme. They seem to work on linux (steam deck) at least. Don’t have access to a windows machine right now\n\n\n\n\nhttps://github.com/v-sekai/v-sekai-game is released as fully opensource.\n\n\n\n\niFire (he, him) — Today at 16:33 https://github.com/V-Sekai/v-sekai-game/pull/5 added caching to reduce doing nothing builds from 2 hours to 10 minutes ish\n\nNew contributors this week:\n@Malek Awesome for being around 🐱. Contributed to designs and cheering us when we succeed. Fixed the issue with the ci/cd with the recurse submodules. Too much to list!\n@gamethecupdog Helped us figured out some problems with AMD vr and V-sekai. We debugged the AMD VR launch issues and talked about fixing the vignette settings in the ui https://github.com/V-Sekai/V-Sekai.github.io/issues/378\n@meowses For supporting us and watching our presentation.\n@Kosyne For starting a topic about onboarding and our short term and long term planning.\n@! [P1-D3] Samuel Martin @Mr_Squarepeg Thanks for hanging out on Sunday, we chatted about V-Sekai and played a bit of ZeroK.\n\n\n\niFire (he, him) — Today at 12:34 Turned off the mesh mirror mode for avatars because of playtesting confusion.\nLyuma — Today at 13:04 makes sense. at some point we can add a mirror, and we need a map aligned at the right place, or a script added to maps which define where the ““mirrors”” are (there can be more than one since it’s just duplicating meshes which is cool)\niFire (he, him) — Today at 14:47 I added https://github.com/TokageItLab/realtime_retarget to V-Sekai’s godot engine c++ modules. Please test, @トカゲ is looking for feedback.\ntefusion’s gdextension addon https://github.com/tefusion/godot-subdiv is now published. https://godotengine.org/asset-library/asset/1488\niFire reorganized the development documentation site.\niFire is working on a bullet train kinetic novel https://github.com/V-Sekai-fire/INK_bullet_train world.\n\n\n\nUpdated this website to remove the left sidebar. Added headers to decisions and the changelog.\n\n\n\nGodot Engine proposal meeting rejected setting float=64 as default. However official 64 bit builds have interest.\n\n\n\nEarly morning discussion with guillefix, lyuma and fire.\nFeature requests from the community:\n\ndesktop capture\navatar ik\nquest support\n3d node graph system\nin-game content creation\nwasm for game scripting\n\n\n\n\nMeeting between betalars, fire, lyuma, jeana and others about usability in 3d games, convention application and V-Sekai.\n\n\n\n\n\n\nbetalars is working on making Chaos Computer Club more accessible.\nThere has been development to create an online-platform for Chaos Communication Congress using Godot\nIt is planned to be deployed in browser, limiting it to Godot 3 for now\nRealistically, the Congress Experience software will not be production-ready before Godot4, so starting with Godot 3 only sets us up for tech-debt and also makes cooperation with V-sekai impossible, so it was the wrong decision originally and is now being reverted.\nBased on limited contributors and also limited time, a Prototype in Godot 3 has been scrapped and betalars reached out to the V-Sekai team for some collaboration and humble contributions\n\n\n\n\n\nMilas needs to write a masters thesis on accessibility-driven Game-Development\nAt the end of December of each year, CCC holds a big conference, this year it is going to be a decentralized bunch of small-scale events due to the pandemic\niFire wants to be able to present meaningful progress by march 2023\n\n\n\n\n\nPretty much all goals align …\n\nMake it FOSS\nAllow for player interaction and expression in an online space\nMake 3D-level building accessible for players\nUse Godot Engine\nEncourage for tinkering and hacking (of the white-hat variety of course)\n\n… except for the fact, that online-chaos was developed for desktop browsers and not VR-Devices\nV-Sekai is engineering-driven and lacks in UX and Design, which betalars has more knowledge in, so there is potential for synergy\nIf this collaboration is successful, it would introduce the project into a big community of developers, some of which will be happy to contribute further code\n\n\n\n\n\nGetting distracted by shiny things\nThere’s currently limited interest in the chaos community at large and Betalars is still pretty junior in experience despite leading the effort of building an online-world\n\n\n\n\n\nAccessibility\n\nV-Sekai is interested in this subject, there’s an argument to be had, that XR has great potential for people with disabilities\n\nNot having to leave their flat for social interaction is a plus\nBeing able to choose to be stealth with a bodily disability\nMore intuitive controls with tracking\nHand tracking can be used for signing.\n\nEven for for visually impaired people, there are options to interact\nButtons\n\nRumble\nSound Feedback\nThere’s a lot of potential for work and research here, that would also benefit the godot-community by add-on development\n\n… and maybe by politely asking for some vital accessibility features to be pushed upstream\nConcrete Projects are:\n\nSubtitles\nIntroducing a Layer for alternate text / screen-reader Label3D\n\n\nLevel Generation\n\nCurrently there is a lot of interest in the community on this subject, as NeosVR, a project with great level-building UX, has been frozen\nGodot has a solid 3D-Level generator, that can be used by “power-users” to create 3D-Scenes\nExpanding its feature set could benefit the Godot Engine Community at large\nThere’s the need for intuitive tools for the average user to create cool stuff in 3D\n\nVoxel-Editors are a great first step, as they are an intuitive tool for blocking out 3D-shapes\nVoxel Editors can be extended with\n“Smart Voxel objects”, that can generate stuff like staircases, roofs, fences etc, that are a pain to block out within the voxel grid (and expanding the voxel grid)\n\n3D-Generators, that based on the existing mesh can build plants for instance\nConvenient Prop-Placement\n\n\n\nLevel Generation References\n\nEverQuest Next Landmark - Detail building tools\nCloud Gardens, a relaxing level building game\nDreams\ncrocotile3d.com\nMinecraft\n\nAI-Assisted Level Generation will probably also be a thing soon\nDesigning fun player-interaction Concepts\n\nBetalars would like to work on it, but it is hard\n\nMaking pretty Characters\n\nBetalars has been working on a sims-style character generator\nCurrent state can be found on gitlab\n\nHopefully will also benefit Godot Engine community\n\n\nDeveloping a Tablet-Mode for V-Sekai\n\nThere has been effort put into creating a Non-VR interaction mode\nCurrently it is pretty janky and not thought through\nBetalars would like to improve this\n\nFire’s V-Sekai priorities:\n\na better setting to be in\ncommunications between at least two people\nbetter character motion via constraints, spring bones, and animations\nbetter character models (betalars has a character creation system that they already developed as possible collaboration points)\n\n\n\n\n\ngithub.com/omigroup/ux-research\nThis is the new repo for the recently formed UX Research group in OMI. Check back weekly for updates on this repo and how to get involved. - GitHub - omigroup/ux-research: This is a new working group for OMIGroup\n\n\n\n\nMmmaellon’s work requires him to build an XR app using AWS Services. He wants to use that opportunity to make something that allows players to build maps collaboratively.\n\n\n\nASTC work for mobile gpu textures work."
+    "text": "Updated this v-sekai.github.io website.\n\n\n\n\nHad a meeting with Lyuma, Fire, Sarcen, Silent and MMMaellon about the V-Sekai project.\nResolved apply style patches to 3d-audio.\nMake V-Sekai film tests with the new Godot Engine movie maker feature."
   },
   {
-    "objectID": "changelog/2022/20221001-changelog.html#section",
-    "href": "changelog/2022/20221001-changelog.html#section",
-    "title": "V-Sekai Changelog - 2022-10",
+    "objectID": "changelog/2022/20220601-changelog.html#section-1",
+    "href": "changelog/2022/20220601-changelog.html#section-1",
+    "title": "V-Sekai Changelog - 2022-06",
     "section": "",
-    "text": "Lyuma — 01/10/2022 I have pushed internal and external resource whitelisting at the ResrouceLoader (ResourceFormatLoaderBinary) level as a Godot engine patch.\n\nHere’s an example of what gets printed when the above script with OS.alert() attempts to be loaded\nERROR: user://asset_cache/81dd12d03686\n0a08faba06a1b47a3a29.scn:Resource of unrecognized type in file: GDScript.\n   at: load (core/io/resource_format_binary.cpp:789)\nERROR: Failed loading resource: user://asset_cache/81dd12d036860a08faba06a1b47a3a29.scn. Make sure resources have been imported by opening the project in the editor at least once.\nNote that I was forced to rebase to the latest build which includes the new build system (target=editor) most of the code I changed is in the private gitlab repo. once things stabilize and we get the build system up and running again, next step is to publish the remainder of the code on github\n\ngroups-4.x (and staging) were updated to latest. I attempted to update GoCD, but it’s a bit of a yolo merge, since a few pieces all had to be updated at once due to new scons target=editor argument we need to follow https://ci.v-sekai.cloud/ (log in as guest) and test the release builds\n\n\nexport builds are being created again with the new scons naming scheme. They seem to work on linux (steam deck) at least. Don’t have access to a windows machine right now"
+    "text": "Fire collaborated on godot-snappy for object snapping https://github.com/jgillich/godot-snappy\nTry to integrate manifold again."
   },
   {
-    "objectID": "changelog/2022/20221001-changelog.html#section-1",
-    "href": "changelog/2022/20221001-changelog.html#section-1",
-    "title": "V-Sekai Changelog - 2022-10",
+    "objectID": "changelog/2022/20220601-changelog.html#section-2",
+    "href": "changelog/2022/20220601-changelog.html#section-2",
+    "title": "V-Sekai Changelog - 2022-06",
     "section": "",
-    "text": "https://github.com/v-sekai/v-sekai-game is released as fully opensource."
+    "text": "https://gitlab.com/bramw/baserow/-/issues/998 Spent some documenting the baserow io system on Digital Ocean used to store in-progress art assets, data from research and 3d galleries.\nDonated research on avatar generation to the MIT-licensed project at https://github.com/AtlasFoundation/OpenCharacterCreator As part of: lightweight-quality-avatars"
   },
   {
-    "objectID": "changelog/2022/20221001-changelog.html#section-2",
-    "href": "changelog/2022/20221001-changelog.html#section-2",
-    "title": "V-Sekai Changelog - 2022-10",
+    "objectID": "changelog/2022/20220601-changelog.html#section-3",
+    "href": "changelog/2022/20220601-changelog.html#section-3",
+    "title": "V-Sekai Changelog - 2022-06",
     "section": "",
-    "text": "iFire (he, him) — Today at 16:33 https://github.com/V-Sekai/v-sekai-game/pull/5 added caching to reduce doing nothing builds from 2 hours to 10 minutes ish\n\nNew contributors this week:\n@Malek Awesome for being around 🐱. Contributed to designs and cheering us when we succeed. Fixed the issue with the ci/cd with the recurse submodules. Too much to list!\n@gamethecupdog Helped us figured out some problems with AMD vr and V-sekai. We debugged the AMD VR launch issues and talked about fixing the vignette settings in the ui https://github.com/V-Sekai/V-Sekai.github.io/issues/378\n@meowses For supporting us and watching our presentation.\n@Kosyne For starting a topic about onboarding and our short term and long term planning.\n@! [P1-D3] Samuel Martin @Mr_Squarepeg Thanks for hanging out on Sunday, we chatted about V-Sekai and played a bit of ZeroK."
+    "text": "Lyuma uncommented some code in vsk_avatar/ik_space.gd to create IK tracking points on the server, to enable IK sync via server. TL;DR (Other peers can see other peers while connected to a server.)\nServer sync issue removed from todo list.\n\n\n\n\n\n\n\n\n\n\nid\nName\nNotes\nActive\n\n\n\n\n24\nVR smooth locomotion.\n\nTrue\n\n\n24\nVR smooth locomotion with blackout.\n\nTrue\n\n\n5\nGrab an object.\n\nTrue\n\n\n17\nSupport large uploads to the content distribution network.\n\nTrue\n\n\n19\nMake a video of entering the world and grabbing objects.\n\nTrue\n\n\n\nTrialing a fix for issue of SDFGI on VR. Was poor. Had to backout branch."
   },
   {
-    "objectID": "changelog/2022/20221001-changelog.html#section-3",
-    "href": "changelog/2022/20221001-changelog.html#section-3",
-    "title": "V-Sekai Changelog - 2022-10",
+    "objectID": "changelog/2022/20220301-changelog.html",
+    "href": "changelog/2022/20220301-changelog.html",
+    "title": "V-Sekai Changelog - 2022-03",
     "section": "",
-    "text": "iFire (he, him) — Today at 12:34 Turned off the mesh mirror mode for avatars because of playtesting confusion.\nLyuma — Today at 13:04 makes sense. at some point we can add a mirror, and we need a map aligned at the right place, or a script added to maps which define where the ““mirrors”” are (there can be more than one since it’s just duplicating meshes which is cool)\niFire (he, him) — Today at 14:47 I added https://github.com/TokageItLab/realtime_retarget to V-Sekai’s godot engine c++ modules. Please test, @トカゲ is looking for feedback.\ntefusion’s gdextension addon https://github.com/tefusion/godot-subdiv is now published. https://godotengine.org/asset-library/asset/1488\niFire reorganized the development documentation site.\niFire is working on a bullet train kinetic novel https://github.com/V-Sekai-fire/INK_bullet_train world."
+    "text": "Steamdeck test with V-Sekai.\nRestored image grid in V-Sekai content picking.\nWorking with the animation team to approve the skeleton animation retargeter.\nhttps://github.com/fire/geodesiac-path-on-mesh https://mindsdb.com/ https://github.com/godotengine/godot/pull/56902 https://github.com/KhronosGroup/glTF-Blender-IO/pull/1582.\nRestored wasd in V-Sekai build.\nAlso the last line also reduced the warning from 700 to around 8-30\nLast week improved openxr support but not yet locomotion.\nHand actions and triggers still bugged\nCollaboration with Khronos and Lucasfilm has added gltf principled pbr to materialx\nA static materialx baking importer has been added to a Godot Engine c++ master module\nAbandoned the work on webview because it required too much mingw hacking of windows calls. Should have worked in msvc still https://github.com/AcademySoftwareFoundation/MaterialX/issues/874\nWant to propose gltf specular and gltf volumetric to the godot engine rendering team\nWorked on an idea with Krsytof https://github.com/godotengine/godot-proposals/discussions/4226 to pin inspectors.\nFire collaborated with Tokage and Lyuma on the UIUX of a skeletal retargeting importer\nStarted a discussion on a train station stress test. https://github.com/godotengine/godot-proposals/discussions/4233\n\n\nOpenXR mode works!!!\nMade a skeleton retargeting demo.\n\n\n\n\n\nAdded a new audio effect to down-mix stereo audio to mono progressively. https://github.com/godotengine/godot/pull/58823\n\n\n\n\nAllow automatic lod when importing 3D scenes with Static Lightmaps https://github.com/godotengine/godot/pull/58548\nproductionize a clothing band / bracelet maker on 3d manifold-only meshes https://github.com/fire/geodesiac-path-on-mesh\nplay with a auto-ml thing that guesses floats, guesses classes and forecasts https://mindsdb.com/\nworking with the animation team to approve the skeleton animation retargeter. https://github.com/godotengine/godot/pull/56902\nconvinced the gltf blender maintainer it’s super easy to export pure 3d animations as gltf. https://github.com/KhronosGroup/glTF-Blender-IO/pull/1582"
   },
   {
-    "objectID": "changelog/2022/20221001-changelog.html#section-4",
-    "href": "changelog/2022/20221001-changelog.html#section-4",
-    "title": "V-Sekai Changelog - 2022-10",
+    "objectID": "changelog/2022/20220301-changelog.html#section",
+    "href": "changelog/2022/20220301-changelog.html#section",
+    "title": "V-Sekai Changelog - 2022-03",
     "section": "",
-    "text": "Updated this website to remove the left sidebar. Added headers to decisions and the changelog."
+    "text": "OpenXR mode works!!!\nMade a skeleton retargeting demo."
   },
   {
-    "objectID": "changelog/2022/20221001-changelog.html#section-5",
-    "href": "changelog/2022/20221001-changelog.html#section-5",
-    "title": "V-Sekai Changelog - 2022-10",
+    "objectID": "changelog/2022/20220301-changelog.html#section-1",
+    "href": "changelog/2022/20220301-changelog.html#section-1",
+    "title": "V-Sekai Changelog - 2022-03",
     "section": "",
-    "text": "Godot Engine proposal meeting rejected setting float=64 as default. However official 64 bit builds have interest."
+    "text": "Added a new audio effect to down-mix stereo audio to mono progressively. https://github.com/godotengine/godot/pull/58823\n\n\n\n\nAllow automatic lod when importing 3D scenes with Static Lightmaps https://github.com/godotengine/godot/pull/58548\nproductionize a clothing band / bracelet maker on 3d manifold-only meshes https://github.com/fire/geodesiac-path-on-mesh\nplay with a auto-ml thing that guesses floats, guesses classes and forecasts https://mindsdb.com/\nworking with the animation team to approve the skeleton animation retargeter. https://github.com/godotengine/godot/pull/56902\nconvinced the gltf blender maintainer it’s super easy to export pure 3d animations as gltf. https://github.com/KhronosGroup/glTF-Blender-IO/pull/1582"
   },
   {
-    "objectID": "changelog/2022/20221001-changelog.html#section-6",
-    "href": "changelog/2022/20221001-changelog.html#section-6",
-    "title": "V-Sekai Changelog - 2022-10",
+    "objectID": "changelog/2022/20220901-changelog.html",
+    "href": "changelog/2022/20220901-changelog.html",
+    "title": "V-Sekai Changelog - 2022-09",
     "section": "",
-    "text": "Early morning discussion with guillefix, lyuma and fire.\nFeature requests from the community:\n\ndesktop capture\navatar ik\nquest support\n3d node graph system\nin-game content creation\nwasm for game scripting"
+    "text": "V-Sekai Changelog - 2022-09\n\n\n2022-09-05\ntefusion took iFire’s previous Godot Engine 3 branch and forward ported quad subdivision to an gdextension addon https://github.com/tefusion/godot-subdiv\nWe discuss with Reduz, Calinou and Lyuma about astc and limiting astc block size to 4x4, 8x8, and 12x12 block sizes. 4x4 was agreed on. Others have not yet.\n\n\n2022-09-06\nRestored Lillybyte’s https://github.com/godotengine/godot/pull/59675 Show the 3D transform gizmo in the center when otherwise offscreen work.\nGodot Engine astc block size agreed to be 4x4 and 8x8.\nSaracen’s Make auto-advance flag a requirement for conditional/expression evaluation with design amendments approved. https://github.com/godotengine/godot/pull/65312\nhttps://twitter.com/KenneyNL made a V-Sekai logo for us. https://twitter.com/KenneyNL/status/1567077172866596868?s=20&t=RIGyiux3A_KNX_HCLCVKvg\n\n\n2022-09-09\nhttps://github.com/Geequlim/ECMAScript/issues/131#issuecomment-1241570998 Javascript update.\nhttps://github.com/fire/ewbik Collaborated with Eron and Lyuma. Worked on the design of EWBIK bone weights and bone priority. Worked on the different bone rolls vs silhouette problem in regular 3d formats versus VRM which has a identity bone roll. (Use the original bone and then parent the change to be in ewbik bone roll.) Made the EWBIK solve less jello. Also discussion using kusudama constraints in Godot Engine core."
   },
   {
-    "objectID": "changelog/2022/20221001-changelog.html#section-7",
-    "href": "changelog/2022/20221001-changelog.html#section-7",
-    "title": "V-Sekai Changelog - 2022-10",
+    "objectID": "changelog/2022/20221201-changelog.html",
+    "href": "changelog/2022/20221201-changelog.html",
+    "title": "V-Sekai Changelog - 2022-12",
     "section": "",
-    "text": "Meeting between betalars, fire, lyuma, jeana and others about usability in 3d games, convention application and V-Sekai."
+    "text": "V-Sekai Changelog - 2022-12\nThis is the changelog for December 2022.\n\n\n2022-12-05\nRestored AEC3 to speech for echo cancellation.\n\n\n2022-12-06\nSome reorganization of the the V-Sekai-game issues and the proposal repository to move bugs to V-Sekai-game and enhancements to the proposal repository. Organized the issues and put some videos for some of them. The Japanese tokyo world bug with the 30 second lag between load was funny.\nMoved enhancements to https://github.com/V-Sekai/V-Sekai.github.io and bugs to https://github.com/V-Sekai/v-sekai-game/issues.\nGodot Speech now includes echo cancellation using WebRTC AEC3. Thanks iFire for adding it and getting it building. (some of the builds had issues but they should be resolved) .\n\n\n2022-12-12\nMMMaellon updated the V-Sekai game fov to 70.\nLyuma — Today at 00:34\nWe had an animation meeting with people in the Godot rocketchat.\nWe went through the issues in this list: https://docs.google.com/spreadsheets/d/16Al_PUHAUJE0S3XXtBpmA6MQIA_9sx57BXEisW1EAB0/edit#gid=0 Google Docs (Saracen / Lyuma / Fire / Tokage) A list of open issues/bugs/PRs th…\nPretty excited about some of these changes if they can get merged, especially the ability to extend and override AnimationNode classes, such as from a GDExtension plugin\nWe agreed to punt SkeletonModificationStack3D until 4.1. I think we will remove it from 4.0 because it is very buggy in its present state and there is not enough time to develop a good system for IK\n\n\n2022-12-15\n\n\n\noblique clipping plane for screenspace mirrors\n\n\n&lt;Lyuma&gt; Engine patch: https://github.com/V-Sekai/godot/tree/override_projection VR Demo branch based on Saracen’s code: https://github.com/V-Sekai/avatar_vr_demo/tree/screenspace_mirror It’s missing some of the newer changes but anyway that’s what I have."
   },
   {
-    "objectID": "changelog/2022/20221001-changelog.html#humble-contributions-and-places-to-start",
-    "href": "changelog/2022/20221001-changelog.html#humble-contributions-and-places-to-start",
-    "title": "V-Sekai Changelog - 2022-10",
+    "objectID": "changelog/2022/20220101-changelog.html",
+    "href": "changelog/2022/20220101-changelog.html",
+    "title": "V-Sekai Changelog - 2022-01",
     "section": "",
-    "text": "betalars is working on making Chaos Computer Club more accessible.\nThere has been development to create an online-platform for Chaos Communication Congress using Godot\nIt is planned to be deployed in browser, limiting it to Godot 3 for now\nRealistically, the Congress Experience software will not be production-ready before Godot4, so starting with Godot 3 only sets us up for tech-debt and also makes cooperation with V-sekai impossible, so it was the wrong decision originally and is now being reverted.\nBased on limited contributors and also limited time, a Prototype in Godot 3 has been scrapped and betalars reached out to the V-Sekai team for some collaboration and humble contributions\n\n\n\n\n\nMilas needs to write a masters thesis on accessibility-driven Game-Development\nAt the end of December of each year, CCC holds a big conference, this year it is going to be a decentralized bunch of small-scale events due to the pandemic\niFire wants to be able to present meaningful progress by march 2023\n\n\n\n\n\nPretty much all goals align …\n\nMake it FOSS\nAllow for player interaction and expression in an online space\nMake 3D-level building accessible for players\nUse Godot Engine\nEncourage for tinkering and hacking (of the white-hat variety of course)\n\n… except for the fact, that online-chaos was developed for desktop browsers and not VR-Devices\nV-Sekai is engineering-driven and lacks in UX and Design, which betalars has more knowledge in, so there is potential for synergy\nIf this collaboration is successful, it would introduce the project into a big community of developers, some of which will be happy to contribute further code\n\n\n\n\n\nGetting distracted by shiny things\nThere’s currently limited interest in the chaos community at large and Betalars is still pretty junior in experience despite leading the effort of building an online-world\n\n\n\n\n\nAccessibility\n\nV-Sekai is interested in this subject, there’s an argument to be had, that XR has great potential for people with disabilities\n\nNot having to leave their flat for social interaction is a plus\nBeing able to choose to be stealth with a bodily disability\nMore intuitive controls with tracking\nHand tracking can be used for signing.\n\nEven for for visually impaired people, there are options to interact\nButtons\n\nRumble\nSound Feedback\nThere’s a lot of potential for work and research here, that would also benefit the godot-community by add-on development\n\n… and maybe by politely asking for some vital accessibility features to be pushed upstream\nConcrete Projects are:\n\nSubtitles\nIntroducing a Layer for alternate text / screen-reader Label3D\n\n\nLevel Generation\n\nCurrently there is a lot of interest in the community on this subject, as NeosVR, a project with great level-building UX, has been frozen\nGodot has a solid 3D-Level generator, that can be used by “power-users” to create 3D-Scenes\nExpanding its feature set could benefit the Godot Engine Community at large\nThere’s the need for intuitive tools for the average user to create cool stuff in 3D\n\nVoxel-Editors are a great first step, as they are an intuitive tool for blocking out 3D-shapes\nVoxel Editors can be extended with\n“Smart Voxel objects”, that can generate stuff like staircases, roofs, fences etc, that are a pain to block out within the voxel grid (and expanding the voxel grid)\n\n3D-Generators, that based on the existing mesh can build plants for instance\nConvenient Prop-Placement\n\n\n\nLevel Generation References\n\nEverQuest Next Landmark - Detail building tools\nCloud Gardens, a relaxing level building game\nDreams\ncrocotile3d.com\nMinecraft\n\nAI-Assisted Level Generation will probably also be a thing soon\nDesigning fun player-interaction Concepts\n\nBetalars would like to work on it, but it is hard\n\nMaking pretty Characters\n\nBetalars has been working on a sims-style character generator\nCurrent state can be found on gitlab\n\nHopefully will also benefit Godot Engine community\n\n\nDeveloping a Tablet-Mode for V-Sekai\n\nThere has been effort put into creating a Non-VR interaction mode\nCurrently it is pretty janky and not thought through\nBetalars would like to improve this\n\nFire’s V-Sekai priorities:\n\na better setting to be in\ncommunications between at least two people\nbetter character motion via constraints, spring bones, and animations\nbetter character models (betalars has a character creation system that they already developed as possible collaboration points)\n\n\n\n\n\ngithub.com/omigroup/ux-research\nThis is the new repo for the recently formed UX Research group in OMI. Check back weekly for updates on this repo and how to get involved. - GitHub - omigroup/ux-research: This is a new working group for OMIGroup"
+    "text": "iFire wrote with Lyuma some proposals:\n\nCICD as a TrueNas Scale system\nProposal for Github CICD actions.\n\nBastiaanOlij updated the OpenXR pull request so it now uses OpenXR 1.0.22 and it has that DISABLE_STD_FILESYSTEM switch in there.\n\n\nSwitch proposal website to use https://quarto.org/.\nUpdated nomnoml diagrams.\n\n\n\n&lt;Lyuma&gt; Merged VR support (including OpenXR and the ability to create OpenVR as a plugin) into our godot engine build.\n\n\n\nMaterial Maker was patched so that OpenEXR export don’t shift color channels in generated EXR file."
   },
   {
-    "objectID": "changelog/2022/20221001-changelog.html#section-8",
-    "href": "changelog/2022/20221001-changelog.html#section-8",
-    "title": "V-Sekai Changelog - 2022-10",
+    "objectID": "changelog/2022/20220101-changelog.html#section",
+    "href": "changelog/2022/20220101-changelog.html#section",
+    "title": "V-Sekai Changelog - 2022-01",
     "section": "",
-    "text": "Mmmaellon’s work requires him to build an XR app using AWS Services. He wants to use that opportunity to make something that allows players to build maps collaboratively."
+    "text": "Switch proposal website to use https://quarto.org/.\nUpdated nomnoml diagrams."
   },
   {
-    "objectID": "changelog/2022/20221001-changelog.html#section-9",
-    "href": "changelog/2022/20221001-changelog.html#section-9",
-    "title": "V-Sekai Changelog - 2022-10",
+    "objectID": "changelog/2022/20220101-changelog.html#section-1",
+    "href": "changelog/2022/20220101-changelog.html#section-1",
+    "title": "V-Sekai Changelog - 2022-01",
     "section": "",
-    "text": "ASTC work for mobile gpu textures work."
+    "text": "&lt;Lyuma&gt; Merged VR support (including OpenXR and the ability to create OpenVR as a plugin) into our godot engine build."
   },
   {
-    "objectID": "changelog/2023/20230901-changelog.html",
-    "href": "changelog/2023/20230901-changelog.html",
-    "title": "V-Sekai Changelog - September 2023",
+    "objectID": "changelog/2022/20220101-changelog.html#section-2",
+    "href": "changelog/2022/20220101-changelog.html#section-2",
+    "title": "V-Sekai Changelog - 2022-01",
     "section": "",
-    "text": "Ported RenIK to GDScript, providing a reference implementation and allowing for separation of RenIKPlacement from RenIK as two distinct nodes. This change enables reuse of the foot placement implementation on any other IK system or swapping out the foot placement system for another animation system and then running the IK algorithm independently. The port was challenging due to differences in the Basis APIs between C++ and GDScript. The GDScript code is available at https://github.com/V-Sekai/renik/tree/gdscript and can be used instead of the original C++ version at https://github.com/V-Sekai/renik. It includes a test scene for use in projects.\n\n\n\n\n\n\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\n\n\n\nNot applicable for this month.\n\nThis project does not adhere to Semantic Versioning.\n\n\n\n\n\nNot applicable for this month.\n\nNote: This changelog has been compiled based on the updates provided. For more detailed information, please refer to the specific issues or pull requests in the respective repositories.\n\n\n\ncommit dc4754b - (main) Merge pull request #242 from V-Sekai/move-utility Move the utility folder.\ncommit f854698 - (main) Merge pull request #241 from V-Sekai/better-svgs Improve the logos.\ncommit 5928dee - (main) Merge pull request #239 from V-Sekai/remove-unused-01 Remove unnecessary files and configurations for Mac development in vs code.\ncommit 8c34654 - (remove-unused-math-utils) Remove unused math utils.\ncommit 9860967 - (main) Merge pull request #245 from V-Sekai/xr-on Make xr mode on.\ncommit 6147202 - (xr-on) Make xr mode on.\ncommit dc4754b - (main) Merge pull request #242 from V-Sekai/move-utility Move the utility folder.\ncommit 83b4490 - (move-utility) Move the utility folder.\ncommit f854698 - (main) Merge pull request #241 from V-Sekai/better-svgs Improve the logos.\ncommit 6519cce - (better-svgs) Improve the logos.\nWrite a constraint minimizer https://github.com/V-Sekai/v-sekai-game/blob/constraint-minimizer/new_script.gd\nWrite a github action for godot engine so I can push releases\nUpdate github actions for tagged release. Use the 0.1.0-alpha1 tag.\nInvestigate https://about.signpath.io/product/open-source for part 2\nLauncher https://gist.github.com/fire/e5a16d3e738e8575b8ce7f527c245d27\nPeople are asking about 3d ik so I need to increase the code quality of https://github.com/V-Sekai/renik"
+    "text": "Material Maker was patched so that OpenEXR export don’t shift color channels in generated EXR file."
   },
   {
-    "objectID": "changelog/2023/20230901-changelog.html#unreleased",
-    "href": "changelog/2023/20230901-changelog.html#unreleased",
-    "title": "V-Sekai Changelog - September 2023",
+    "objectID": "changelog/2022/20220401-changelog.html",
+    "href": "changelog/2022/20220401-changelog.html",
+    "title": "V-Sekai Changelog - 2022-04",
     "section": "",
-    "text": "Ported RenIK to GDScript, providing a reference implementation and allowing for separation of RenIKPlacement from RenIK as two distinct nodes. This change enables reuse of the foot placement implementation on any other IK system or swapping out the foot placement system for another animation system and then running the IK algorithm independently. The port was challenging due to differences in the Basis APIs between C++ and GDScript. The GDScript code is available at https://github.com/V-Sekai/renik/tree/gdscript and can be used instead of the original C++ version at https://github.com/V-Sekai/renik. It includes a test scene for use in projects."
+    "text": "Moved issues into the tracker.\n\n\nWorked with manifold csg library author and was able to remove the boost dependency. https://github.com/elalish/manifold/pull/92\nAlso published a first draft on a Godot Engine master branch. See the issue for details.\n\n\n\nLyuma\nMade a lot of progress towards animation import in Unidot. Godot’s node system means that some paths become different: for example, meshes have to be reparented to skeletons; or extra levels in the hierarchy to keep track of physics bodies.\nTo this end, it is now keeping a lookup dictionary from path and component to fileID (which can be mapped to Godot node) which means animation support should be close.\n(Also, they made a major change to the import system in 2019 which affects id numbering. Still working on it)\nPushed a major update to Unidot, mostly in the post_import script. It should now generate paths much more accurately to the original file, and implemented the hashing algorithm used by Unity 2019 for file ID generation, for example generating ids like 919132149155446097 for the root object.\nThis has fixed some assets exported from Unity 2019 like below, which used to fail to resolve the fileIDs for meshes! @iFire\nMade some progress with terrain import in Unidot. It will import textures, normalmaps and splatmaps (creating an appropriate ShaderMaterial). My plan is to implement trees and grass using MultimeshInstance objects. With this I also now support texture assets. Texture Arrays seem to fail internally. Hard to tell if I did something wrong or something isn’t implemented on Godot’s end, but we’ll get there…\nperformance-wise, I think it’s now acceptable to just pipe all 2+ million polygons (for 1025x1025 terrain) to the GPU. I’m using tristrips so it’s mostly just 1 index per triangle. It might be better to use a more dedicated terrain system for this, so this is just a stopgap while Godot 4 is in development since the terrain systems in the asset library are not keeping up with the rapid pace of development. (if you’re interested in this subject, feel free to start a thread or reply on godot-general)\nTerrain trees, splatmaps and materials are implemented in Unidot, converting to a single conventional terrain mesh + multimesh. I have not implemented holes yet, but if someone has an example and there is demand, I could work on it.\nI also chose not to implement detail (grasses), because I don’t understand how detail patches are implemented, and they tend to not look that great in VR, so I’d rather work on something else.\n\n\n\n\nRestore fix-save-as-binary so we can export projects\nRestore elixir shared branch so we can run godot in elixir\nPoked ludwig about diffusion net for machine learning training.\n\n\n\n\nFBX2GLTF and Blender importers are merged.\n\n\n\niFire\n\nMade a bug report for Blender exported animation to gltf with @RockyMadio https://github.com/KhronosGroup/glTF-Blender-IO/issues/1613 GitHub"
   },
   {
-    "objectID": "changelog/2023/20230901-changelog.html#changed",
-    "href": "changelog/2023/20230901-changelog.html#changed",
-    "title": "V-Sekai Changelog - September 2023",
+    "objectID": "changelog/2022/20220401-changelog.html#section",
+    "href": "changelog/2022/20220401-changelog.html#section",
+    "title": "V-Sekai Changelog - 2022-04",
     "section": "",
-    "text": "Not applicable for this month.\n\n\n\n\n\n\n\n\nNot applicable for this month.\n\nThis project does not adhere to Semantic Versioning."
+    "text": "Worked with manifold csg library author and was able to remove the boost dependency. https://github.com/elalish/manifold/pull/92\nAlso published a first draft on a Godot Engine master branch. See the issue for details."
   },
   {
-    "objectID": "changelog/2023/20230901-changelog.html#previous-releases",
-    "href": "changelog/2023/20230901-changelog.html#previous-releases",
-    "title": "V-Sekai Changelog - September 2023",
+    "objectID": "changelog/2022/20220401-changelog.html#section-1",
+    "href": "changelog/2022/20220401-changelog.html#section-1",
+    "title": "V-Sekai Changelog - 2022-04",
     "section": "",
-    "text": "Not applicable for this month.\n\nNote: This changelog has been compiled based on the updates provided. For more detailed information, please refer to the specific issues or pull requests in the respective repositories."
+    "text": "Lyuma\nMade a lot of progress towards animation import in Unidot. Godot’s node system means that some paths become different: for example, meshes have to be reparented to skeletons; or extra levels in the hierarchy to keep track of physics bodies.\nTo this end, it is now keeping a lookup dictionary from path and component to fileID (which can be mapped to Godot node) which means animation support should be close.\n(Also, they made a major change to the import system in 2019 which affects id numbering. Still working on it)\nPushed a major update to Unidot, mostly in the post_import script. It should now generate paths much more accurately to the original file, and implemented the hashing algorithm used by Unity 2019 for file ID generation, for example generating ids like 919132149155446097 for the root object.\nThis has fixed some assets exported from Unity 2019 like below, which used to fail to resolve the fileIDs for meshes! @iFire\nMade some progress with terrain import in Unidot. It will import textures, normalmaps and splatmaps (creating an appropriate ShaderMaterial). My plan is to implement trees and grass using MultimeshInstance objects. With this I also now support texture assets. Texture Arrays seem to fail internally. Hard to tell if I did something wrong or something isn’t implemented on Godot’s end, but we’ll get there…\nperformance-wise, I think it’s now acceptable to just pipe all 2+ million polygons (for 1025x1025 terrain) to the GPU. I’m using tristrips so it’s mostly just 1 index per triangle. It might be better to use a more dedicated terrain system for this, so this is just a stopgap while Godot 4 is in development since the terrain systems in the asset library are not keeping up with the rapid pace of development. (if you’re interested in this subject, feel free to start a thread or reply on godot-general)\nTerrain trees, splatmaps and materials are implemented in Unidot, converting to a single conventional terrain mesh + multimesh. I have not implemented holes yet, but if someone has an example and there is demand, I could work on it.\nI also chose not to implement detail (grasses), because I don’t understand how detail patches are implemented, and they tend to not look that great in VR, so I’d rather work on something else."
   },
   {
-    "objectID": "changelog/2023/20230901-changelog.html#work-in-progress",
-    "href": "changelog/2023/20230901-changelog.html#work-in-progress",
-    "title": "V-Sekai Changelog - September 2023",
+    "objectID": "changelog/2022/20220401-changelog.html#section-2",
+    "href": "changelog/2022/20220401-changelog.html#section-2",
+    "title": "V-Sekai Changelog - 2022-04",
     "section": "",
-    "text": "commit dc4754b - (main) Merge pull request #242 from V-Sekai/move-utility Move the utility folder.\ncommit f854698 - (main) Merge pull request #241 from V-Sekai/better-svgs Improve the logos.\ncommit 5928dee - (main) Merge pull request #239 from V-Sekai/remove-unused-01 Remove unnecessary files and configurations for Mac development in vs code.\ncommit 8c34654 - (remove-unused-math-utils) Remove unused math utils.\ncommit 9860967 - (main) Merge pull request #245 from V-Sekai/xr-on Make xr mode on.\ncommit 6147202 - (xr-on) Make xr mode on.\ncommit dc4754b - (main) Merge pull request #242 from V-Sekai/move-utility Move the utility folder.\ncommit 83b4490 - (move-utility) Move the utility folder.\ncommit f854698 - (main) Merge pull request #241 from V-Sekai/better-svgs Improve the logos.\ncommit 6519cce - (better-svgs) Improve the logos.\nWrite a constraint minimizer https://github.com/V-Sekai/v-sekai-game/blob/constraint-minimizer/new_script.gd\nWrite a github action for godot engine so I can push releases\nUpdate github actions for tagged release. Use the 0.1.0-alpha1 tag.\nInvestigate https://about.signpath.io/product/open-source for part 2\nLauncher https://gist.github.com/fire/e5a16d3e738e8575b8ce7f527c245d27\nPeople are asking about 3d ik so I need to increase the code quality of https://github.com/V-Sekai/renik"
+    "text": "Restore fix-save-as-binary so we can export projects\nRestore elixir shared branch so we can run godot in elixir\nPoked ludwig about diffusion net for machine learning training."
   },
   {
-    "objectID": "changelog/2023/20230801-changelog.html",
-    "href": "changelog/2023/20230801-changelog.html",
-    "title": "V-Sekai Changelog - August 2023",
+    "objectID": "changelog/2022/20220401-changelog.html#section-3",
+    "href": "changelog/2022/20220401-changelog.html#section-3",
+    "title": "V-Sekai Changelog - 2022-04",
     "section": "",
-    "text": "Basisu (ktx2) for gltf was merged to allow compressing the textures to KTX2, which is GPU compatible and has a very small size. Our project also deals with hundreds and thousands of models placed in one scene, making the file size of each model crucial.\nRechieKho Integrated the iree.gd library with Godot game engine and allows Godot projects to leverage IREE for machine learning workflows.\n\nAddition of Godot image &lt;-&gt; IREE buffer view conversion utilities\nExposure of IREE workflow\nAddition of Godot demos showing IREE integration\n\nRecreated Architext demo for testing apartment blueprint generation.\nGodot VRM has been submitted to the asset library for 4.x by Lyuma on 2023-08-03. It’s now usable and most bugs have been fixed. One known issue is that node constraints have some issues on models which were retargeted (needed bone rotation). If anyone wants to play with godot-vrm, feel free to clone it from github: it’s the same as the version that will be available in the Godot Asset Library. Readme is updated. Feel free to check it out and give feedback. Github Link\nNew commits to godot_uro:main by Lyuma and Fire.\nNew commits to v-sekai-game:main by Lyuma and Fire.\nNew commits to godot:groups-staging-4.2 by Fire.\nNew commits to godot:vsk-many-bone-ik-4.2 by Fire.\nNew commits to v-sekai-game:update-translations by Fire.\nNew commits to v-sekai-game:update-godot by Fire.\nNew commits to godot-vrm:only-addon by Lyuma.\nNew commits to godot-vrm:master by Lyuma.\nNew commits to godot:vsk-flac-4.2 by Fire.\nNew commits to godot:vsk-subdiv-4-0 branch.\nForce-pushed updates to godot branches: vsk-subdiv-4-0, groups-staging-4.2, scene-import-fixes, faster-generate-lod.\nDeletion of branches in V-Sekai/v-sekai-game: migrate-authors, all-contributors/add-lyuma, all-contributors/add-EnthWyrr.\nCreation of new branches in V-Sekai/v-sekai-game: gh-readonly-queue/main/pr-213-d5fbc97d5854516d4305eb94fb6a81307256c978, all-contributors/- add-s-ilent, gh-readonly-queue/main/pr-215-e72f9297674c4c2f82dcc59ba8af18a03fd86fcc, gh-readonly-queue/main/pr-215-d5fbc97d5854516d4305eb94fb6a81307256c978, gh-readonly-queue/main/pr-213-2a174801a0b88ccdfc9c3671230911f6978477bd.\nNew commits to godot:groups-staging-4.2 branch.\nCreation of new branches in V-Sekai/godot: groups-staging-lbfgs, vsk-lbfgs-4.2.\nBump of github/codeql-action from 2.21.4 to 2.21.5 in V-Sekai/v-sekai-game.\nCreation of new branch in V-Sekai/v-sekai-game: dependabot/github_actions/github/codeql-action-2.21.5.\nPull requests #213 and #215 in V-Sekai/v-sekai-game.\nPull request #216 (Bump github/codeql-action from 2.21.4 to 2.21.5) in V-Sekai/v-sekai-game.\n\n\n\n\n\nUpdated localization files for VR manager and menu strings by Fire.\nUpdated the ref value for the v-sekai-game repository to groups-4.2.2023-08-01T161313Z by Fire.\nUpdated godot-deps action.yml by Fire.\nUpdated icons path in FLAC config module by Fire.\nUpdates to README.md and .all-contributorsrc in V-Sekai/v-sekai-game.\nRefactoring and updates in godot:groups-staging-4.2 and godot:vsk-lbfgs-4.2 branches.\n\n\n\n\n\nFix theme of export dialog by Lyuma.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nMany Bone IK has been removed temporarily to ensure the engine builds and passes tests.\nDeletion of branches in V-Sekai/v-sekai-game: gh-readonly-queue/main/pr-213-d5fbc97d5854516d4305eb94fb6a81307256c978, gh-readonly-queue/main/pr-215-e72f9297674c4c2f82dcc59ba8af18a03fd86fcc, gh-readonly-queue/main/pr-215-d5fbc97d5854516d4305eb94fb6a81307256c978, gh-readonly-queue/main/pr-213-2a174801a0b88ccdfc9c3671230911f6978477bd, groups-4.2-latest, dependabot/github_actions/github/codeql-action-2.21.5. MMD PMX scene importer in godot:groups-staging-4.2 branch.\n\n\n\n\n\nNot applicable for this month.\n\nThis project does not adhere to Semantic Versioning.\n\n\n\n\n\nNot applicable for this month.\n\nNote: This changelog has been compiled based on the updates provided. For more detailed information, please refer to the specific issues or pull requests in the respective repositories."
+    "text": "FBX2GLTF and Blender importers are merged."
   },
   {
-    "objectID": "changelog/2023/20230801-changelog.html#unreleased",
-    "href": "changelog/2023/20230801-changelog.html#unreleased",
-    "title": "V-Sekai Changelog - August 2023",
+    "objectID": "changelog/2022/20220401-changelog.html#section-4",
+    "href": "changelog/2022/20220401-changelog.html#section-4",
+    "title": "V-Sekai Changelog - 2022-04",
     "section": "",
-    "text": "Basisu (ktx2) for gltf was merged to allow compressing the textures to KTX2, which is GPU compatible and has a very small size. Our project also deals with hundreds and thousands of models placed in one scene, making the file size of each model crucial.\nRechieKho Integrated the iree.gd library with Godot game engine and allows Godot projects to leverage IREE for machine learning workflows.\n\nAddition of Godot image &lt;-&gt; IREE buffer view conversion utilities\nExposure of IREE workflow\nAddition of Godot demos showing IREE integration\n\nRecreated Architext demo for testing apartment blueprint generation.\nGodot VRM has been submitted to the asset library for 4.x by Lyuma on 2023-08-03. It’s now usable and most bugs have been fixed. One known issue is that node constraints have some issues on models which were retargeted (needed bone rotation). If anyone wants to play with godot-vrm, feel free to clone it from github: it’s the same as the version that will be available in the Godot Asset Library. Readme is updated. Feel free to check it out and give feedback. Github Link\nNew commits to godot_uro:main by Lyuma and Fire.\nNew commits to v-sekai-game:main by Lyuma and Fire.\nNew commits to godot:groups-staging-4.2 by Fire.\nNew commits to godot:vsk-many-bone-ik-4.2 by Fire.\nNew commits to v-sekai-game:update-translations by Fire.\nNew commits to v-sekai-game:update-godot by Fire.\nNew commits to godot-vrm:only-addon by Lyuma.\nNew commits to godot-vrm:master by Lyuma.\nNew commits to godot:vsk-flac-4.2 by Fire.\nNew commits to godot:vsk-subdiv-4-0 branch.\nForce-pushed updates to godot branches: vsk-subdiv-4-0, groups-staging-4.2, scene-import-fixes, faster-generate-lod.\nDeletion of branches in V-Sekai/v-sekai-game: migrate-authors, all-contributors/add-lyuma, all-contributors/add-EnthWyrr.\nCreation of new branches in V-Sekai/v-sekai-game: gh-readonly-queue/main/pr-213-d5fbc97d5854516d4305eb94fb6a81307256c978, all-contributors/- add-s-ilent, gh-readonly-queue/main/pr-215-e72f9297674c4c2f82dcc59ba8af18a03fd86fcc, gh-readonly-queue/main/pr-215-d5fbc97d5854516d4305eb94fb6a81307256c978, gh-readonly-queue/main/pr-213-2a174801a0b88ccdfc9c3671230911f6978477bd.\nNew commits to godot:groups-staging-4.2 branch.\nCreation of new branches in V-Sekai/godot: groups-staging-lbfgs, vsk-lbfgs-4.2.\nBump of github/codeql-action from 2.21.4 to 2.21.5 in V-Sekai/v-sekai-game.\nCreation of new branch in V-Sekai/v-sekai-game: dependabot/github_actions/github/codeql-action-2.21.5.\nPull requests #213 and #215 in V-Sekai/v-sekai-game.\nPull request #216 (Bump github/codeql-action from 2.21.4 to 2.21.5) in V-Sekai/v-sekai-game.\n\n\n\n\n\nUpdated localization files for VR manager and menu strings by Fire.\nUpdated the ref value for the v-sekai-game repository to groups-4.2.2023-08-01T161313Z by Fire.\nUpdated godot-deps action.yml by Fire.\nUpdated icons path in FLAC config module by Fire.\nUpdates to README.md and .all-contributorsrc in V-Sekai/v-sekai-game.\nRefactoring and updates in godot:groups-staging-4.2 and godot:vsk-lbfgs-4.2 branches.\n\n\n\n\n\nFix theme of export dialog by Lyuma.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nMany Bone IK has been removed temporarily to ensure the engine builds and passes tests.\nDeletion of branches in V-Sekai/v-sekai-game: gh-readonly-queue/main/pr-213-d5fbc97d5854516d4305eb94fb6a81307256c978, gh-readonly-queue/main/pr-215-e72f9297674c4c2f82dcc59ba8af18a03fd86fcc, gh-readonly-queue/main/pr-215-d5fbc97d5854516d4305eb94fb6a81307256c978, gh-readonly-queue/main/pr-213-2a174801a0b88ccdfc9c3671230911f6978477bd, groups-4.2-latest, dependabot/github_actions/github/codeql-action-2.21.5. MMD PMX scene importer in godot:groups-staging-4.2 branch.\n\n\n\n\n\nNot applicable for this month.\n\nThis project does not adhere to Semantic Versioning."
+    "text": "iFire\n\nMade a bug report for Blender exported animation to gltf with @RockyMadio https://github.com/KhronosGroup/glTF-Blender-IO/issues/1613 GitHub"
   },
   {
-    "objectID": "changelog/2023/20230801-changelog.html#previous-releases",
-    "href": "changelog/2023/20230801-changelog.html#previous-releases",
-    "title": "V-Sekai Changelog - August 2023",
+    "objectID": "changelog/2023/20231109-changelog.html",
+    "href": "changelog/2023/20231109-changelog.html",
+    "title": "V-Sekai Changelog - November 2023",
     "section": "",
-    "text": "Not applicable for this month.\n\nNote: This changelog has been compiled based on the updates provided. For more detailed information, please refer to the specific issues or pull requests in the respective repositories."
+    "text": "V-Sekai.xr-grid is a VR interaction tool.\n\nFirst release\nRelease Version: 0.1.0-rc1\nChanges: The game name environment variable has been updated in the build workflow. A new commit was also made to set the draft flag to false for the release.\nRelease Link\n\n\n\n\nV-Sekai Model Explorer is a 3D model viewer built with Godot 4. It supports various model formats like VRM and glTF 2.0. With this tool, you can dive deep into the components of a 3D model - inspecting meshes, materials, textures, and animations.\n\nFirst release\nRelease Version: v0.2.0-rc2\nChanges: The GAMENAME environment variable value has been changed to “vsekai_model_explorer”. The macos_editor_macos_deploy job from builds.yml has been removed. A README.md for GitHub actions has been added and the warning has been moved to the top of the file.\nRelease Link\n\n\n\n\n\n\n\n\nMacOS Editor Builds: MacOS editor builds have been added to the project. (Commit: df041f0)\nExport Mac Game: The game can now be exported for Mac. Pending code-signing and App support.\nGolang Installation: Golang has been installed in the project. (Commit: c25456b)\nUnidot Dependency Removal: The dependency on the post-import script by Unidot has been removed after conversion is complete. This means the converted assets will work standalone without the Unidot importer, with one exception*.\nSupported Asset Types: Supported asset types are listed in the readme. It should support many types of meshes, animations, Standard shader materials, scenes/prefabs and physics objects.\nOptimization for Generating Tangents in Mikktspace: An optimization has been added for generating tangents in mikktspace. (Pull Request #83648)\n\n\n\n\n\nGame Name Variable: A game name variable has been implemented on Github Actions. (Commit: 08d87db)\nGodot Engine Repository Update: The Godot engine repository and reference in build workflows have been updated. (Commit: f7f609d)\nImports Update: Imports in the project have been updated. (Commit: 896cb7c)\nUnidot Beta Release: Unidot is now in a beta / early RC for the first release.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nSecurity Best Practices: Applied security best practices as recommended by StepSecurity. (Commit: d641001)\n\nThis project does not adhere to Semantic Versioning.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nLyuma, a member of the V-Sekai team, recently attended the Godot Engine Munich 2023 conference.\nShaders or MonoBehaviors/scripts are not currently supported. This will not be part of the initial release. The goal for now is scene / character / animation conversion.\nAnimationTree uses the standalone runtime/anim_tree.gd script as a blackboard system to simulate unity parameters. This file should remain.\nUnidot Importer Github Link\nA wild spooky dev snapshot appears! 👻 🎃 Contributors are making great progress on solving regressions in Godot 4.2! This new 4.2 beta 4 should be significantly more stable and reliable to upgrade 4.1 projects (not perfect yet though!). Godot Engine Dev snapshot: Godot 4.2 beta 4 We continue iterating quickly on beta snapshots for Godot 4.2 to ensure that we can solve regressions before the stable release."
   },
   {
-    "objectID": "changelog/2023/20231207-changelog.html",
-    "href": "changelog/2023/20231207-changelog.html",
-    "title": "V-Sekai Changelog - December 2023",
+    "objectID": "changelog/2023/20231109-changelog.html#released",
+    "href": "changelog/2023/20231109-changelog.html#released",
+    "title": "V-Sekai Changelog - November 2023",
     "section": "",
-    "text": "2023-12-11 20:10: Unidot Importer | Unidot Importer. Unidot is a .unitypackage asset interoperability tool to bring assets designed for other engines into Godot Engine. Check it out here.\n2023-12-12 04:19: Unidot was submitted to the asset library! We have a separate discord server for Unidot Importer: Join us on Discord. It’s kind of a companion for V-Sekai, but I expect a lot of general game developers joining who have little interest in VR or social virtual worlds, so I think it’s good to have a separate community.\n\n\n\n\nInitial commit on TOOL_game_start:main branch.\nNew commits to godot:master adding various features and fixes.\nUnify tangents in obj on godot:unify-tangents-obj branch.\nUpdates to manuals:main branch.\nAddition of mtlx on godot:godot-mtlx-4.2 branch.\nUpdates to godot-usd:main branch\nUpdated https://saracenone.itch.io/groups-4x on godot engine master (4.3). DX12 is not enabled.\n\n\n\n\n\nForce-pushed changes to various branches in the godot repository.\nMerged pull requests on V-Sekai.xr-grid:main branch.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nRemoval of git submodules on godot-mtlx:godot-rebase branch.\n\n\n\n\n\nSecurity Best Practices: Applied security best practices as recommended by StepSecurity.\n\nThis project does not adhere to Semantic Versioning.\n\n\n\n\n\nNot applicable for this month."
+    "text": "V-Sekai.xr-grid is a VR interaction tool.\n\nFirst release\nRelease Version: 0.1.0-rc1\nChanges: The game name environment variable has been updated in the build workflow. A new commit was also made to set the draft flag to false for the release.\nRelease Link\n\n\n\n\nV-Sekai Model Explorer is a 3D model viewer built with Godot 4. It supports various model formats like VRM and glTF 2.0. With this tool, you can dive deep into the components of a 3D model - inspecting meshes, materials, textures, and animations.\n\nFirst release\nRelease Version: v0.2.0-rc2\nChanges: The GAMENAME environment variable value has been changed to “vsekai_model_explorer”. The macos_editor_macos_deploy job from builds.yml has been removed. A README.md for GitHub actions has been added and the warning has been moved to the top of the file.\nRelease Link"
   },
   {
-    "objectID": "changelog/2023/20231207-changelog.html#released",
-    "href": "changelog/2023/20231207-changelog.html#released",
-    "title": "V-Sekai Changelog - December 2023",
+    "objectID": "changelog/2023/20231109-changelog.html#unreleased",
+    "href": "changelog/2023/20231109-changelog.html#unreleased",
+    "title": "V-Sekai Changelog - November 2023",
     "section": "",
-    "text": "2023-12-11 20:10: Unidot Importer | Unidot Importer. Unidot is a .unitypackage asset interoperability tool to bring assets designed for other engines into Godot Engine. Check it out here.\n2023-12-12 04:19: Unidot was submitted to the asset library! We have a separate discord server for Unidot Importer: Join us on Discord. It’s kind of a companion for V-Sekai, but I expect a lot of general game developers joining who have little interest in VR or social virtual worlds, so I think it’s good to have a separate community.\n\n\n\n\nInitial commit on TOOL_game_start:main branch.\nNew commits to godot:master adding various features and fixes.\nUnify tangents in obj on godot:unify-tangents-obj branch.\nUpdates to manuals:main branch.\nAddition of mtlx on godot:godot-mtlx-4.2 branch.\nUpdates to godot-usd:main branch\nUpdated https://saracenone.itch.io/groups-4x on godot engine master (4.3). DX12 is not enabled.\n\n\n\n\n\nForce-pushed changes to various branches in the godot repository.\nMerged pull requests on V-Sekai.xr-grid:main branch.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nRemoval of git submodules on godot-mtlx:godot-rebase branch.\n\n\n\n\n\nSecurity Best Practices: Applied security best practices as recommended by StepSecurity.\n\nThis project does not adhere to Semantic Versioning."
+    "text": "MacOS Editor Builds: MacOS editor builds have been added to the project. (Commit: df041f0)\nExport Mac Game: The game can now be exported for Mac. Pending code-signing and App support.\nGolang Installation: Golang has been installed in the project. (Commit: c25456b)\nUnidot Dependency Removal: The dependency on the post-import script by Unidot has been removed after conversion is complete. This means the converted assets will work standalone without the Unidot importer, with one exception*.\nSupported Asset Types: Supported asset types are listed in the readme. It should support many types of meshes, animations, Standard shader materials, scenes/prefabs and physics objects.\nOptimization for Generating Tangents in Mikktspace: An optimization has been added for generating tangents in mikktspace. (Pull Request #83648)\n\n\n\n\n\nGame Name Variable: A game name variable has been implemented on Github Actions. (Commit: 08d87db)\nGodot Engine Repository Update: The Godot engine repository and reference in build workflows have been updated. (Commit: f7f609d)\nImports Update: Imports in the project have been updated. (Commit: 896cb7c)\nUnidot Beta Release: Unidot is now in a beta / early RC for the first release.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nSecurity Best Practices: Applied security best practices as recommended by StepSecurity. (Commit: d641001)\n\nThis project does not adhere to Semantic Versioning."
   },
   {
-    "objectID": "changelog/2023/20231207-changelog.html#previous-releases",
-    "href": "changelog/2023/20231207-changelog.html#previous-releases",
-    "title": "V-Sekai Changelog - December 2023",
+    "objectID": "changelog/2023/20231109-changelog.html#previous-releases",
+    "href": "changelog/2023/20231109-changelog.html#previous-releases",
+    "title": "V-Sekai Changelog - November 2023",
     "section": "",
     "text": "Not applicable for this month."
   },
   {
-    "objectID": "changelog/2023/20230301-changelog.html",
-    "href": "changelog/2023/20230301-changelog.html",
-    "title": "V-Sekai Changelog - 2023-03",
+    "objectID": "changelog/2023/20231109-changelog.html#misc",
+    "href": "changelog/2023/20231109-changelog.html#misc",
+    "title": "V-Sekai Changelog - November 2023",
     "section": "",
-    "text": "This is the changelog for March 2023.\nGodot Engine 4.0 launched on March 1st. 🎉\n\n\nUpgrade the documentation to point to github actions.\nPosted changes to https://github.com/godotengine/tps-demo/pull/167 to improve Github Actions export\nWorking on https://github.com/V-Sekai/blender-art-blue-tin-fox-models to get a list of prototype models.\nTuned the vr vingette usability feature to be more black.\nCreate an Awesome V-sekai page https://github.com/V-Sekai/awesome-v-sekai.\nMigrate the manual page to https://v-sekai.github.io/manuals\nInvestigated SHARK and IREE. Provides vulkan for machine learning.\nWrote a proposal for libfbx. https://github.com/godotengine/godot-proposals/issues/6453\nDid some removal of non essential code towards being in vr, loading maps and being in an avatar.\nRestore the brightness defaults in physical lighting.\nTrial variable rate shading.\nUpdate VSK_model_explorer to stable Godot Engine 4.0.\nHelped HungryProton add an automated build system for his ProtonGraph application. https://github.com/protongraph/protongraph\nTrying to get Godot Engine V-Sekai builds to pass. There was a breaking change in Scons.\nLibgodot doesn’t pass unit testing.\nUpdated https://github.com/V-Sekai/godot-task-goal-planner ’s gut addon and remove vsk versioning.\nReleased embedding search example with Marqo. https://github.com/fire/soriee-search\n\n\n\n\n\n\n\n\n\nSequence\nPose\n\n\n\n\n0\nT-pose\n\n\n1\nA-Pose\n\n\n2\nHands beside the upper leg, palms inwards at “At Ease”.\n\n\n3\nLift left leg\n\n\n4\nPut hands next to the face in a claw position palms facing outwards\n\n\n5\nHands at “At Ease”\n\n\n6\nLift left arm from “At Ease” to pointing straight upwards\n\n\n7\nLift left arm from “At Ease” to pointing upwards and wave off to a side\n\n\n8\nPoint left index finger\n\n\n9\nHands at “At Ease”\n\n\n10\nBicycle pose\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nOrganization\nDescription\ndate\n\n\n\n\nGodot Engine Foundation & V-Sekai\nCSG Fire Chatted about CSG with reduz First Meeting\n2023-03-30 00:00:00\n\n\nV-Sekai\nPhysics Colliders Fire CoACD https://github.com/SarahWeiii/CoACD/issues/9\n2023-03-30 00:00:00\n\n\nV-Sekai & Thorvg\nFire Fire Review thorvg PR https://github.com/godotengine/godot/pull/75508\n2023-03-30 00:00:00\n\n\nV-Sekai\nFire Fire Play a horror game First Meeting\n2023-03-30 00:00:00\n\n\nV-Sekai & Zylann\nFire Fire Asked zylann to review double precision pr\n2023-03-30 00:00:00\n\n\nV-Sekai\nFire Fire Restore github cicd First Meeting\n2023-03-30 00:00:00\n\n\nV-Sekai\nFire Fire Animation iks as node first draft posted. First draft\n2023-03-30 00:00:00\n\n\nV-Sekai\nFire Fire Propose a animation node pr First Meeting\n2023-03-30 00:00:00"
+    "text": "Lyuma, a member of the V-Sekai team, recently attended the Godot Engine Munich 2023 conference.\nShaders or MonoBehaviors/scripts are not currently supported. This will not be part of the initial release. The goal for now is scene / character / animation conversion.\nAnimationTree uses the standalone runtime/anim_tree.gd script as a blackboard system to simulate unity parameters. This file should remain.\nUnidot Importer Github Link\nA wild spooky dev snapshot appears! 👻 🎃 Contributors are making great progress on solving regressions in Godot 4.2! This new 4.2 beta 4 should be significantly more stable and reliable to upgrade 4.1 projects (not perfect yet though!). Godot Engine Dev snapshot: Godot 4.2 beta 4 We continue iterating quickly on beta snapshots for Godot 4.2 to ensure that we can solve regressions before the stable release."
   },
   {
-    "objectID": "changelog/2023/20230301-changelog.html#fire",
-    "href": "changelog/2023/20230301-changelog.html#fire",
-    "title": "V-Sekai Changelog - 2023-03",
+    "objectID": "changelog/2023/20230501-changelog.html",
+    "href": "changelog/2023/20230501-changelog.html",
+    "title": "V-Sekai Changelog - 2023-05",
     "section": "",
-    "text": "Upgrade the documentation to point to github actions.\nPosted changes to https://github.com/godotengine/tps-demo/pull/167 to improve Github Actions export\nWorking on https://github.com/V-Sekai/blender-art-blue-tin-fox-models to get a list of prototype models.\nTuned the vr vingette usability feature to be more black.\nCreate an Awesome V-sekai page https://github.com/V-Sekai/awesome-v-sekai.\nMigrate the manual page to https://v-sekai.github.io/manuals\nInvestigated SHARK and IREE. Provides vulkan for machine learning.\nWrote a proposal for libfbx. https://github.com/godotengine/godot-proposals/issues/6453\nDid some removal of non essential code towards being in vr, loading maps and being in an avatar.\nRestore the brightness defaults in physical lighting.\nTrial variable rate shading.\nUpdate VSK_model_explorer to stable Godot Engine 4.0.\nHelped HungryProton add an automated build system for his ProtonGraph application. https://github.com/protongraph/protongraph\nTrying to get Godot Engine V-Sekai builds to pass. There was a breaking change in Scons.\nLibgodot doesn’t pass unit testing.\nUpdated https://github.com/V-Sekai/godot-task-goal-planner ’s gut addon and remove vsk versioning.\nReleased embedding search example with Marqo. https://github.com/fire/soriee-search\n\n\n\n\n\n\n\n\n\nSequence\nPose\n\n\n\n\n0\nT-pose\n\n\n1\nA-Pose\n\n\n2\nHands beside the upper leg, palms inwards at “At Ease”.\n\n\n3\nLift left leg\n\n\n4\nPut hands next to the face in a claw position palms facing outwards\n\n\n5\nHands at “At Ease”\n\n\n6\nLift left arm from “At Ease” to pointing straight upwards\n\n\n7\nLift left arm from “At Ease” to pointing upwards and wave off to a side\n\n\n8\nPoint left index finger\n\n\n9\nHands at “At Ease”\n\n\n10\nBicycle pose\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nOrganization\nDescription\ndate\n\n\n\n\nGodot Engine Foundation & V-Sekai\nCSG Fire Chatted about CSG with reduz First Meeting\n2023-03-30 00:00:00\n\n\nV-Sekai\nPhysics Colliders Fire CoACD https://github.com/SarahWeiii/CoACD/issues/9\n2023-03-30 00:00:00\n\n\nV-Sekai & Thorvg\nFire Fire Review thorvg PR https://github.com/godotengine/godot/pull/75508\n2023-03-30 00:00:00\n\n\nV-Sekai\nFire Fire Play a horror game First Meeting\n2023-03-30 00:00:00\n\n\nV-Sekai & Zylann\nFire Fire Asked zylann to review double precision pr\n2023-03-30 00:00:00\n\n\nV-Sekai\nFire Fire Restore github cicd First Meeting\n2023-03-30 00:00:00\n\n\nV-Sekai\nFire Fire Animation iks as node first draft posted. First draft\n2023-03-30 00:00:00\n\n\nV-Sekai\nFire Fire Propose a animation node pr First Meeting\n2023-03-30 00:00:00"
+    "text": "In May 2023, significant progress was made in the Godot community and V-Sekai project. Key developments include the implementation of WebAssembly modules for Godot Engine 4, improvements to the V-Sekai Godot Engine fork, and advancements in Unidot’s FBX humanoid support. Additionally, there were updates to the manual site, suggestions for Blender VRM drag-and-drop support, and bug fixes related to LODs.\n\nhttps://github.com/ashtonmeuser/godot-wasm/tree/godot-4 Implements wasm modules for Godot Engine 4.\nFire has chatgpt4 api access.\nMerged godot-wasm into V-Sekai Godot Engine fork for experimenting with user generated scripting and optimization of computation.\nvsk_speech branch of V-Sekai Godot Engine passes cicd again!!\nRevised and optimized the manual site.\nSuggested that .VRM drag and drop support is added to Blender. https://github.com/mika-f/blender-drag-and-drop/issues/34#issuecomment-1539429579\nUse a better representation of feminine and masculine avatars\nFixing bugs with lods\n\n\n\nLyuma has been working on implementing imported humanoid FBX support in Unidot, including bone guessing. The current implementation supports FBX source models and performs bone name guessing when humanDescription is empty. However, it does not yet support humanoid .anim clips, and there are known issues applying Animator components to already-imported models.\nAfter fixing a typo in Fix Silhouette, Lyuma reported that FBX humanoid animation import in Unidot seems much closer. They also implemented support for “Copy from other Avatar” to handle conversion of Maya FBX files with the first frame posed like the animation. This allows using the T-pose of another model as the rest pose.\nLyuma shared their progress on Twitter, showcasing the effectiveness of Unidot-Importer by VSekaiOfficial and Godot 4.0’s new humanoid retargeter system. The Godot Engine community also discovered the team’s GLTF work, as seen in a tweet by Bramwell.\nGamefromscratch covered Godot -&gt; Unity migration in a YouTube video, highlighting the use of barcoderdev’s version of FBX2glTF with Unidot, which might solve the pivot issue encountered earlier."
   },
   {
-    "objectID": "changelog/2023/20230701-changelog.html",
-    "href": "changelog/2023/20230701-changelog.html",
-    "title": "V-Sekai Changelog - July 2023",
+    "objectID": "changelog/2023/20230501-changelog.html#unidot-update-summary",
+    "href": "changelog/2023/20230501-changelog.html#unidot-update-summary",
+    "title": "V-Sekai Changelog - 2023-05",
     "section": "",
-    "text": "VRM 1.0 export work by Lyuma.\nImplemented VRM 1 spring bones in the vrm1-wip branch by Lyuma.\nRefactored XML class definitions in all external vsk-modules by iFire.\nAdded “painfulness” to the many bone IK solver by iFire.\n\n\n\n\n\nPushed a bunch of the code for VRM 1 to godot-vrm by Lyuma.\nMore changes to vrm1-wip specifically changing how head hiding works by Lyuma.\nRestoring editor upload of avatars and worlds by iFire.\n\n\n\n\n\nPosted a fix for the magenta viewport copy of xr bug by iFire.\n\n\n\n\n\nVRM 0 models are upgraded to VRM 1 format during import, so only VRM 1 can be exported, and it will use VRM 1 style naming for everything by Lyuma.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\nThis project does not adheres to Semantic Versioning.\n\n\n\n\n\nNot applicable for this month.\n\nNote: This changelog has been compiled based on the updates provided. For more detailed information, please refer to the specific issues or pull requests in the respective repositories."
+    "text": "Lyuma has been working on implementing imported humanoid FBX support in Unidot, including bone guessing. The current implementation supports FBX source models and performs bone name guessing when humanDescription is empty. However, it does not yet support humanoid .anim clips, and there are known issues applying Animator components to already-imported models.\nAfter fixing a typo in Fix Silhouette, Lyuma reported that FBX humanoid animation import in Unidot seems much closer. They also implemented support for “Copy from other Avatar” to handle conversion of Maya FBX files with the first frame posed like the animation. This allows using the T-pose of another model as the rest pose.\nLyuma shared their progress on Twitter, showcasing the effectiveness of Unidot-Importer by VSekaiOfficial and Godot 4.0’s new humanoid retargeter system. The Godot Engine community also discovered the team’s GLTF work, as seen in a tweet by Bramwell.\nGamefromscratch covered Godot -&gt; Unity migration in a YouTube video, highlighting the use of barcoderdev’s version of FBX2glTF with Unidot, which might solve the pivot issue encountered earlier."
   },
   {
-    "objectID": "changelog/2023/20230701-changelog.html#unreleased",
-    "href": "changelog/2023/20230701-changelog.html#unreleased",
-    "title": "V-Sekai Changelog - July 2023",
+    "objectID": "changelog/2023/20230101-changelog.html",
+    "href": "changelog/2023/20230101-changelog.html",
+    "title": "V-Sekai Changelog - 2023-01",
     "section": "",
-    "text": "VRM 1.0 export work by Lyuma.\nImplemented VRM 1 spring bones in the vrm1-wip branch by Lyuma.\nRefactored XML class definitions in all external vsk-modules by iFire.\nAdded “painfulness” to the many bone IK solver by iFire.\n\n\n\n\n\nPushed a bunch of the code for VRM 1 to godot-vrm by Lyuma.\nMore changes to vrm1-wip specifically changing how head hiding works by Lyuma.\nRestoring editor upload of avatars and worlds by iFire.\n\n\n\n\n\nPosted a fix for the magenta viewport copy of xr bug by iFire.\n\n\n\n\n\nVRM 0 models are upgraded to VRM 1 format during import, so only VRM 1 can be exported, and it will use VRM 1 style naming for everything by Lyuma.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\nThis project does not adheres to Semantic Versioning."
+    "text": "V-Sekai Changelog - 2023-01\nThis is the changelog for January 2023."
   },
   {
-    "objectID": "changelog/2023/20230701-changelog.html#previous-releases",
-    "href": "changelog/2023/20230701-changelog.html#previous-releases",
-    "title": "V-Sekai Changelog - July 2023",
+    "objectID": "changelog/2023/20230201-changelog.html",
+    "href": "changelog/2023/20230201-changelog.html",
+    "title": "V-Sekai Changelog - 2023-02",
     "section": "",
-    "text": "Not applicable for this month.\n\nNote: This changelog has been compiled based on the updates provided. For more detailed information, please refer to the specific issues or pull requests in the respective repositories."
+    "text": "This is the changelog for February 2023.\nThe sdk has the entire v-sekai-game project, all the builds and git .\nThe game builds can be smaller but they currently have the shared_library, the executable and the gdextension interface files. It also can launch v-sekai with openxr.\nThe builds are ranging to 10 minutes for a partially cached build on average. Engine builds take longer.\nhttps://nightly.link/V-Sekai/v-sekai-game/workflows/vsk_linux_builds/main\n\n\n\nSomeone wanted me to help out on voip so I assisted\nA v-tuber, expiredpopsicle, is using godot-vrm! and contributed.\nFaolan is a Godot contributor. Fire gifted libgodot code to him and now he’s able to run his vr platform on the Meta Quest with dotnet.\n\n\n\n\nI reduced iteration times on the V-Sekai cicd from 1.5 hours to 2-10 minutes.\nI also stopped merging incomplete work. Every merge commit should stand on its own."
   },
   {
-    "objectID": "changelog/2023/20230601-changelog.html",
-    "href": "changelog/2023/20230601-changelog.html",
-    "title": "V-Sekai Changelog - 2023-06",
+    "objectID": "changelog/2023/20230201-changelog.html#people",
+    "href": "changelog/2023/20230201-changelog.html#people",
+    "title": "V-Sekai Changelog - 2023-02",
     "section": "",
-    "text": "In June 2023, various developments and discussions took place in the Godot community, particularly within the V-Sekai project. Key highlights include updates to the godot-vrm repository, security improvements in the v-sekai-game repository, and progress on animation retargeting and PMX character structure. Additionally, a fix was implemented for Skeleton3D’s rest_dirty reset issue.\n\nFork created: aaronfranke/godot-vrm (01/06/2023)\nNew commits in V-Sekai/godot-vrm repository, including updates to load_at_runtime_scene for 4.x and adding files_dropped functionality (02/06/2023)\nPR 130 closed, bumping github/codeql-action from 2.3.5 to 2.3.6 in V-Sekai/v-sekai-game (02/06/2023)\nPR 129 closed, bumping actions/setup-dotnet from 3.1.0 to 3.2.0 in V-Sekai/v-sekai-game (02/06/2023)\nStepSecurity bot opened PR 131 to apply security best practices in V-Sekai/v-sekai-game (02/06/2023)\nNew commit in v-sekai-game:main to avoid the empty avatar crash (02/06/2023)\nNew commits in v-sekai-game:main, including changes to assert and early return print _error (02/06/2023)\nNew tag created in V-Sekai/godot: groups-4.x.2023-06-03T034215Z (02/06/2023)\nPR 131 closed, applying security best practices in V-Sekai/v-sekai-game (02/06/2023)\nNew commit in v-sekai-game:main to make joining a server less crashy (02/06/2023)\nNew commit in v-sekai-game:main to remove debug points (02/06/2023)\nNew branch created in V-Sekai/v-sekai-game: codeql (02/06/2023)\nPR 132 opened, creating codeql.yml in V-Sekai/v-sekai-game (02/06/2023)\nNew comment on issue #25 in V-Sekai/godot-vrm discussing how to make a VRM model pose using GDScript (02/06/2023)\nNew commits in v-sekai-game:main, including changes to assert and early return print _error part 3, avoiding runtime errors, and removing gut (02/06/2023 - 03/06/2023)\nPR 132 closed, creating codeql.yml in V-Sekai/v-sekai-game (03/06/2023)\nPR 133 opened, hardening GitHub Actions in V-Sekai/v-sekai-game (03/06/2023)\nNew comments on issue #25 in V-Sekai/godot-vrm discussing animation retargeting and PMX character structure (03/06/2023)\nNew commits in v-sekai-game:main, including removing hardcoded gravity and gravity direction, inverting state machine condition, and setting up work in progress state chart (03/06/2023)\nNew branch created in V-Sekai/v-sekai-game: state-chart (03/06/2023)\nSkeleton3D now correctly resets rest_dirty only after all bone transforms have been updated (PR 78025 by lyuma). This also resolves the SkeletonGizmo display issue when there is more than one bone root.\n\n\n\nThe team has introduced a feature that allows for easy setup with just a single click. Additionally, they’re now utilizing an advanced system known as the Many Bones’ solver.\n\n\n\nThere were some concerns about how much time the GPU was spending on processing the shader - think of the shader like a set of instructions telling the GPU how to draw each pixel. The frame times, or the speed at which frames are processed, seemed to be slower than expected. However, it was clarified that these tests were being run in a mode designed for finding errors (debug mode), not for optimal performance.\n\n\n\nThe team discussed how their system’s performance stacks up against other virtual reality social platforms. They used different types of hardware for these comparisons, similar to comparing the performance of different cars using various types of roads and conditions.\n\n\n\nThe team also talked about how to best optimize their system for different devices. This is akin to tuning a car’s engine differently depending on whether it’s going to be driven in the city or on a racetrack.\n\n\n\nThere were discussions about the challenges of rendering avatars, especially when there are multiple avatars on the screen at once. It’s like trying to paint multiple portraits at the same time - the more you have, the harder it gets. The team discussed the need for guidelines to help avatar creators optimize their designs for less powerful hardware.\n\n\n\nLooking ahead, the team plans to conduct more tests, particularly focusing on how well their system handles complex 3D models on Android devices. They also aim to create a benchmark scenario where they expect good performance across most platforms, much like setting a standard track to test different cars’ performances."
+    "text": "Someone wanted me to help out on voip so I assisted\nA v-tuber, expiredpopsicle, is using godot-vrm! and contributed.\nFaolan is a Godot contributor. Fire gifted libgodot code to him and now he’s able to run his vr platform on the Meta Quest with dotnet."
   },
   {
-    "objectID": "changelog/2023/20230601-changelog.html#simplified-setup-and-advanced-solver-system",
-    "href": "changelog/2023/20230601-changelog.html#simplified-setup-and-advanced-solver-system",
-    "title": "V-Sekai Changelog - 2023-06",
+    "objectID": "changelog/2023/20230201-changelog.html#fire",
+    "href": "changelog/2023/20230201-changelog.html#fire",
+    "title": "V-Sekai Changelog - 2023-02",
     "section": "",
-    "text": "The team has introduced a feature that allows for easy setup with just a single click. Additionally, they’re now utilizing an advanced system known as the Many Bones’ solver."
+    "text": "I reduced iteration times on the V-Sekai cicd from 1.5 hours to 2-10 minutes.\nI also stopped merging incomplete work. Every merge commit should stand on its own."
   },
   {
-    "objectID": "changelog/2023/20230601-changelog.html#graphics-processing-unit-gpu-performance",
-    "href": "changelog/2023/20230601-changelog.html#graphics-processing-unit-gpu-performance",
-    "title": "V-Sekai Changelog - 2023-06",
+    "objectID": "changelog/2023/20231001-changelog.html",
+    "href": "changelog/2023/20231001-changelog.html",
+    "title": "V-Sekai Changelog - October 2023",
     "section": "",
-    "text": "There were some concerns about how much time the GPU was spending on processing the shader - think of the shader like a set of instructions telling the GPU how to draw each pixel. The frame times, or the speed at which frames are processed, seemed to be slower than expected. However, it was clarified that these tests were being run in a mode designed for finding errors (debug mode), not for optimal performance."
+    "text": "Lyuma has pushed support to GodotEngine Unidot-Importer for humanoid unity .anim import including lox9973’s center of mass correction for hips. #gamedev\nHumanoid anim support is complete, including arm/leg twist! Import of standalone Avatar assets is now functional (such as converted VRM files).\nUnpacked avatar prefabs are now extracted into their own scenes.\n\n\n\n\n\nUpdated casync for v-sekai-game. This is still using the old version binaries.\n\ngit clone https://github.com/V-Sekai/casync-v-sekai-game.git\ncd casync-v-sekai-game\n./extract.sh\n\n\n\n\nFixed an issue with GLTF images being referenced directly instead of going through the GLTFState.textures mapping. This was causing texture mis-matches on some VRMs when loaded. The fix involved passing the GLTF state into a few more functions, replacing the image list, so we could also access the textures mapping directly alongside them. (#82)\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\nThis project does not adhere to Semantic Versioning.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nConvinced PolygonJS to change their license to the MIT license.\nReviewed a character generator with OMI and JIN\nDiscussed svg in gltf at OMI\nProposed feature request to add an extractor to save 3d assets, gltf files, CAD files, shapefiles, STLs, etc to ArchiveBox. Issue #668\nDiscovered a method of json document sync. JsonJoy\n\n\n\n\n\n“The term logbook originated with the ship’s log, a maritime record of important events in the management, operation, and navigation of a ship. The captain was responsible for keeping a log, as a minimum, of navigational wind, speed, direction and position.” - Wikipedia"
   },
   {
-    "objectID": "changelog/2023/20230601-changelog.html#comparing-performance-across-platforms",
-    "href": "changelog/2023/20230601-changelog.html#comparing-performance-across-platforms",
-    "title": "V-Sekai Changelog - 2023-06",
+    "objectID": "changelog/2023/20231001-changelog.html#unreleased",
+    "href": "changelog/2023/20231001-changelog.html#unreleased",
+    "title": "V-Sekai Changelog - October 2023",
     "section": "",
-    "text": "The team discussed how their system’s performance stacks up against other virtual reality social platforms. They used different types of hardware for these comparisons, similar to comparing the performance of different cars using various types of roads and conditions."
+    "text": "Lyuma has pushed support to GodotEngine Unidot-Importer for humanoid unity .anim import including lox9973’s center of mass correction for hips. #gamedev\nHumanoid anim support is complete, including arm/leg twist! Import of standalone Avatar assets is now functional (such as converted VRM files).\nUnpacked avatar prefabs are now extracted into their own scenes.\n\n\n\n\n\nUpdated casync for v-sekai-game. This is still using the old version binaries.\n\ngit clone https://github.com/V-Sekai/casync-v-sekai-game.git\ncd casync-v-sekai-game\n./extract.sh\n\n\n\n\nFixed an issue with GLTF images being referenced directly instead of going through the GLTFState.textures mapping. This was causing texture mis-matches on some VRMs when loaded. The fix involved passing the GLTF state into a few more functions, replacing the image list, so we could also access the textures mapping directly alongside them. (#82)\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\n\n\n\n\nNot applicable for this month.\n\nThis project does not adhere to Semantic Versioning."
   },
   {
-    "objectID": "changelog/2023/20230601-changelog.html#tailoring-performance-for-different-devices",
-    "href": "changelog/2023/20230601-changelog.html#tailoring-performance-for-different-devices",
-    "title": "V-Sekai Changelog - 2023-06",
+    "objectID": "changelog/2023/20231001-changelog.html#previous-releases",
+    "href": "changelog/2023/20231001-changelog.html#previous-releases",
+    "title": "V-Sekai Changelog - October 2023",
     "section": "",
-    "text": "The team also talked about how to best optimize their system for different devices. This is akin to tuning a car’s engine differently depending on whether it’s going to be driven in the city or on a racetrack."
+    "text": "Not applicable for this month."
   },
   {
-    "objectID": "changelog/2023/20230601-changelog.html#rendering-avatars",
-    "href": "changelog/2023/20230601-changelog.html#rendering-avatars",
-    "title": "V-Sekai Changelog - 2023-06",
+    "objectID": "changelog/2023/20231001-changelog.html#misc",
+    "href": "changelog/2023/20231001-changelog.html#misc",
+    "title": "V-Sekai Changelog - October 2023",
     "section": "",
-    "text": "There were discussions about the challenges of rendering avatars, especially when there are multiple avatars on the screen at once. It’s like trying to paint multiple portraits at the same time - the more you have, the harder it gets. The team discussed the need for guidelines to help avatar creators optimize their designs for less powerful hardware."
+    "text": "Convinced PolygonJS to change their license to the MIT license.\nReviewed a character generator with OMI and JIN\nDiscussed svg in gltf at OMI\nProposed feature request to add an extractor to save 3d assets, gltf files, CAD files, shapefiles, STLs, etc to ArchiveBox. Issue #668\nDiscovered a method of json document sync. JsonJoy"
   },
   {
-    "objectID": "changelog/2023/20230601-changelog.html#future-plans",
-    "href": "changelog/2023/20230601-changelog.html#future-plans",
-    "title": "V-Sekai Changelog - 2023-06",
+    "objectID": "changelog/2023/20231001-changelog.html#quotes-of-the-month",
+    "href": "changelog/2023/20231001-changelog.html#quotes-of-the-month",
+    "title": "V-Sekai Changelog - October 2023",
     "section": "",
-    "text": "Looking ahead, the team plans to conduct more tests, particularly focusing on how well their system handles complex 3D models on Android devices. They also aim to create a benchmark scenario where they expect good performance across most platforms, much like setting a standard track to test different cars’ performances."
+    "text": "“The term logbook originated with the ship’s log, a maritime record of important events in the management, operation, and navigation of a ship. The captain was responsible for keeping a log, as a minimum, of navigational wind, speed, direction and position.” - Wikipedia"
   }
 ]
\ No newline at end of file
diff --git a/docs/sitemap.xml b/docs/sitemap.xml
index ee7f4bc48d..fff5698764 100644
--- a/docs/sitemap.xml
+++ b/docs/sitemap.xml
@@ -1,2039 +1,2039 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
   <url>
-    <loc>https://v-sekai.github.io/manuals/plan.html</loc>
-    <lastmod>2024-11-02T08:18:10.238Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/changelog/2023/20230601-changelog.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/changelog/2023/20231001-changelog.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/changelog/2023/20230701-changelog.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/changelog/2023/20230201-changelog.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/changelog/2023/20230301-changelog.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/changelog/2023/20230101-changelog.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/changelog/2023/20231207-changelog.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/changelog/2023/20230501-changelog.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/changelog/2023/20230801-changelog.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/changelog/2023/20231109-changelog.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/changelog/2023/20230901-changelog.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/changelog/2022/20220401-changelog.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/changelog/2022/20221001-changelog.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/changelog/2022/20220101-changelog.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/changelog/2022/20220801-changelog.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/changelog/2022/20221201-changelog.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/changelog/2022/20221101-changelog.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/changelog/2022/20220901-changelog.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/changelog/2022/20220501-changelog.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/changelog/2022/20220301-changelog.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/changelog/2022/20220201-changelog.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/changelog/2022/20220601-changelog.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/changelog/2021/20210401-changelog.html</loc>
+    <lastmod>2024-11-02T14:50:23.662Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/changelog/2021/20210701-changelog.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/changelog/2021/20210501-changelog.html</loc>
+    <lastmod>2024-11-02T14:50:23.662Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/changelog/2021/20211101-changelog.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/changelog/2021/20210601-changelog.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/changelog/2021/20210801-changelog.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/changelog/2021/20210901-changelog.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/changelog/2021/20211001-changelog.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/changelog/2024/20241003-changelog.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/changelog/2024/20240901-changelog.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/changelog/2024/20240202-changelog.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/changelog/2024/20240101-changelog.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/changelog/2024/20240330-changelog.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/changelog/2024/20240625-changelog.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/changelog/2024/20240505-changelog.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/changelog/2024/20240701-changelog.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/changelog/2024/20240603-changelog.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231229-byobu.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20221016-v-sekai-view-replication.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240330-cicd-gitlab.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211229-run-meetings-using-lean-coffee.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230310-IREE-backend-for-machine-learning-computations.html</loc>
-    <lastmod>2024-11-02T08:18:10.026Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230922-spacetime-shadow-shards-sync.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211031-gltf-importer-should-bind-animation-players-to-the-closest-root-node.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230831-fixing-upload-limits.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230123-publish-godot-vrm-4.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230408-v-sekai-launcher.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240425-recharge-cycle.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240710-art-direction-in-vsekai.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20210523-basis-universal-import.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240710-use-webrtc-to-native-interop.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230620-t5-jsonformer-xstate.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230716-enhancing-avatar-creation-process-01-regular.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20210811-godot-transparency.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231108-neon-vercel-functions-toy-problem.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230619-membrane-framework-for-mesh-processing.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230719-dual-databases-cockroachdb-khepri.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20200602-manage-backend-with-k3s.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240611-test-1x-and-4x.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240708-vsekai-my-life-as-a-queen.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240626-update-python3-macos-certicates.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211031-meeting-area.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231104-flatbuffer_packed_scenes.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231201-headless-launcher-backend.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230125-provide-metadata-to-match-compatibile-maps-and-avatars.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240217-documentation-guidelines.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211005-create-add-spring-bones-to-vrm-models.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230819-train-game.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230527-organization.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240717-core-vsekai-scripting.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230509-wasm-data-exchange.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20221006-rename-to-main.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230429-git-subrepo-challenges.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231108-neon-1-gb-scene-storage.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231108-postgres-bytea-optimizations.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211031-script-as-a-binary.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20241011-recovering-makehuman-parameters.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240623-talk-length-prototypes.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230507-distributed-sim.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240325-table-avatar-embedded-xmp.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230602-pmx-module-integration.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240406-web-based-explore.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20241014-app-updater.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240705-rpg_town.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20210622-shadermotion-to-godot-engine.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240409-crud-godot-tiles.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230803-subrepo-addon-management.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230310-xml-based-tests.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230505-polygon-mesh-based-sculpting-tools.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20220207-virtual-pets.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20220531-truenas-scale.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211031-streaming-godot-to-opensoundcontrol.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240502-gltf-fbx-tscn-vrm.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211031-have-better-user-developer-experience.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211031-have-wires-in-3d.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20221203-target-10-minutes-cicd.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230429-improve-collab.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20220131-github-actions-support.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240127-urban-explorer-gdc-2024-sample.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211005-create-sop-for-vrm-creation.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211031-arc-radial-menu.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20221205-debug-linux-export.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211031-benchmark-animation-playback.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230525-animation-ik-node.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230131-default-test-plan.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20210523-simplfy-meshes-and-lods-better-with-quads.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230507-avatar-publishing-workflow-portability.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/attachments/pitch_apple_vision_01.html</loc>
-    <lastmod>2024-11-02T08:18:10.170Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/attachments/virtual_pets/LICENSE.html</loc>
+    <lastmod>2024-11-02T14:50:23.874Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/attachments/thunderbolt_install_windows.html</loc>
-    <lastmod>2024-11-02T08:18:10.222Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/attachments/pitch_general_02.html</loc>
+    <lastmod>2024-11-02T14:50:23.810Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/attachments/project_mirage.html</loc>
-    <lastmod>2024-11-02T08:18:10.170Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20220202-gltf-extensions-for-interoperability.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230516-additional-3d-import.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230521-audio-jitter-buffer-voip.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231108-nier-automata-world-expansion.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231020-llama-cpp-mistral-npc.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231027-drawing-concept-to-blockout.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20220118-convert-gltf-to-a-scene.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230719-pose-kusudama-constraints-in-vr.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231218-mtlx-try-two.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240424-reset-steamvr-controllers.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230911-can-poly-green-coords-extend-to-3d.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230630-vsekai-goal-meeting.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231112-archive-projects.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231201-xr-hands-animation-node.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20220624-webcam-to-posed-characters.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240110-magical-girls-college-novel.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231226-furniture-vs-organic.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20220318-merge-retargeting-pr.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211031-bake-blend-shape-to-skeleton-animation.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240528-pipeline-godot-wasm-importer.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230806-music-gen.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230911-xpr.exs.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231203-graphsage-embedding-generation.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211031-construct-the-virtual-world.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240307-rabbitmq-ra.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240710-platform-focus-on-pcvr-and-web.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240502-mesh-object-sync-benchmark.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240121-mac-setup.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211031-phase-out-groups-terminology-for-vskdefault.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211103-use-platform-called-vfx-reference-platform.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230123-use-easy-charts-for-observability.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231203-mesh-rwkv.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230429-v-sekai-roadmap.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20220531-elixir-uro-dev.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240623-what-is-uro-backend.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230614-llm-statechart.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20221019-develop-a-replication-sync-for-100-000-entities.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240217-intended-effort-versioning.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230531-godot-engine-ipad.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231110-better-pipeline-tools.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240914-godot-engine-xr-elite-conference-setup.html</loc>
+    <lastmod>2024-11-02T14:50:23.690Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20221018-v-sekai-game-update-procedure.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231114-elixir-definition-of-godot-types.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230913-V-Sekai-bugs.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231105-pdf-embed-raster-svg-vr.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211031-use-our-custom-fullbody-ik.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240218-vrm-substance-editor.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231114-maintain-svgcleaner.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211005-improve-meshing-results-by-subdivision-in-godot-engine.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231108-munich-godot-engine-conference.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20220820-bake alembic-anim-via-blender.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211031-character-workshop.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211105-have-an-webxr-version-of-v-sekai.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230804-dokku.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211031-godot-database-viewer-for-proposals.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240329-ready-to-go-kit-windows-11.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230508-novel-3d-views.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230125-without-viz-we-cannot-compare-the-interpolation.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230131-meeting-at-gdc-2023.html</loc>
-    <lastmod>2024-11-02T08:18:10.026Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230519-add-vrm-omi-personality-gltf-extension.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230123-ready-the-net-demo.html</loc>
-    <lastmod>2024-11-02T08:18:10.026Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230519-v-sekai-roadmap.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231225-mesh-transformer-clothing.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231229-mRemoteNG.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20210811-omi-glb.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20221006-unidot-is-optional.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20220130-to-record-decisions-write-a-proposal.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231227-blue-green-shadows.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240411-elixir-libgodot-zig.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230824-subdiv-for-lods.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240217-container-2-wasm.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230831-fixing-menus.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230626-godot-vrm1-addon.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240407-pcvr-vs-standalone.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20220222-rank-skeleton-bone-names-with-catboost.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230803-idle-rpg-home.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231108-v-sekai-chat-bot.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230620-doi-github.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211104-research-mesh-tooling-with-kaolin.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240709-anwave-set-nvidia-watt-limit.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20220916-too-many-branches-on-v-sekai-godot.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230123-face-helmet-capture.html</loc>
-    <lastmod>2024-11-02T08:18:10.026Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231027-dreamcraft3d-workflow.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240613-1k-quad-limit.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230106-walking-controller-renik.html</loc>
-    <lastmod>2024-11-02T08:18:10.026Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230527-v-sekai-roadmap.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230415-load-collaborate.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240621-proposal-template copy.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230123-integrate-blender-with-gltf-extensions-and-godot.html</loc>
-    <lastmod>2024-11-02T08:18:10.026Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230616-pmx-to-vrm.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240616-request-for-quad-mesh-dataset.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231027-write-a-list-of-github-pull-requests.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230602-v-sekai-roadmap.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231027-apartment-building-vr.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230812-gocd-agent-setup.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211031-create-a-demo-viewer-gallery.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230419-package-godot-for-pkgin.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240618-4-player-test-vsekai.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211005-bridge-music-to-xr.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240715-vrchat-networking-mental-model.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230310-don&#39;t-merge-incomplete-work.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230701-vsekai-broken-down-goals.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20220605-gocd-pipeline-reset.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20210811-game-workflow-membrane.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20221014-networking-overhaul-proposal.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211031-face-motion-tracking-requires-standard-shapes.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240622-process-for-testing-vsekai.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230912-target-most-popular-resolution.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230527-server-performance-test.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20221206-export-godot-vrm-to-the-asset-library.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20210212-use-markdown-architectural-decision-records.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211031-extract-proposals-into-proposals.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20210715-portable-world-content.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230823-speech-to-blendshapes.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240121-livebook-fedora-install.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240613-training-dataset.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20220901-mirror-extend-asset-library-packages.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240305-v-sekai-launcher.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240627-every-commit-push-pass-cicd.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231112-validation-service.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240314-live-collab.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240121-install-tailscale.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240331-vrc-vrm-compatibility.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240522-discord-bot.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240611-lower-learning-rate.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211220-network-the-ubisoft-mixer-server.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231227-punchline-reports.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211031-verification-tools.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240120-vr-armature-system.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20241014-basic-realtime-interaction.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20210707-transfer-animations-by-baking-reset.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211031-update-uro-for-godot-4.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20221019-networking-100000-entities-ownership.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230903-replicate-vrm-transform.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20210811-min-spec-v-sekai.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20210529-performance-profiling.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211005-we-want-to-proxy-udp-datagrams-at-production-quality-of-service.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230811-punchline-reports.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231109-discord-polygonjs-generator.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231225-mesh-transformer-facial-features.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230830-generating-v-sekai-worlds.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240710-use-godot-engine-web-threaded.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240613-modifying-the-mesh-transformer-for-quads.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230803-jolt-gextension-to-module.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20210811-disconnected-ipfs.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240121-easy-diffusion-fedora-install.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240522-shader-motion-to-bvh.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240105-1-meter-128-quantize.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240630-use-motion-transformers-for-prediction.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240511-review-80-vr.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211031-openvr-for-godot-engine.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230415-rgbaf-to-store-integers.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230125-cover-80-95-percent-of-the-userbase.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230920-godot-project-search.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211031-use-bpr-to-rank-skeleton-bone-names.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240215-avatar-customization-with-ai-facial-expressions.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240416-previewer-upload-gltf-to-glb.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211031-tire-model-car-sim.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20220131-elixir-desktop-uro.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230624-v-sekai-roadmap.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211031-1000-player-servers.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230618-v-sekai-roadmap.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230830-better-object-pick.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20210710-verify-pr-workflow.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230527-server-side-content-validation.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230123-recording-demo-checklist.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20220222-rank-bone-skeletons-with-xgboost.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230619-move-cockroachdb-to-yugabyte.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231026-blender-steam-beta-version.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240111-fit-clothing-on-humans-without-tearing.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20221205-moving-fast-philosophy-development.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211031-membrane-framework-streaming-mixer.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20220830-godot-pdf-workflow.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230608-v-sekai-roadmap.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231209-appium-testing-win11.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20210212-use-log4brains-to-manage-the-adrs.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240406-itch-github-actions.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240217-workload-benchmarking.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240622-build-for-many-platforms.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230813-blender-runner-into-membrane-framework.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230125-possible-futures.html</loc>
-    <lastmod>2024-11-02T08:18:10.026Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211031-how-to-make-a-v-sekaigodot-update.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240111-fspy.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240502-membrane-framework-identity-post.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231125-v-sekai-report.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211031-plausable-npc-behaviour.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20241006-restore-onedrive-shortcut-overrides.html</loc>
+    <lastmod>2024-11-02T14:50:23.690Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240413-calling-opensource-llm-with-aria.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240425-proposal-prompt-system.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240522-discord-inworld-portal.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211031-client-and-mast.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211031-stream-shader-motion.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240905-revised-tracker-configuration-and-constraints.html</loc>
+    <lastmod>2024-11-02T14:50:23.690Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211031-cicd-export-v-sekai.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231024-finetuning-workflow.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230522-JOKE-fictional-blood-combat.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240330-gitlab-helm.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20220113-change-transform-by-crdt.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20220222-rank-bone-names-with-transformer.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230125-grow-the-community-with-a-reactive-discord-bot.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230908-bendable-screen-generative-assistant-ggml.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230125-two-groups-battle-demo.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211031-vmd-on-vrm-animationtree-node.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230415-procedural-variations-props-envs-avatars.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230829-omifest-2023.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230502-add-iree-to-godot-engine-for-image-superresolution.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211031-bake-a-materialx-into-a-custom-godot-standardmaterial3d.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211108-integrate-with-blender.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20220317-use-spec-rough-metal.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230108-wmf-video-playback.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20200608-vsekai-charter.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20220108-bake-blend-shapes-to-skeletons-for-performance.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20221021-make-it-easier-propose-and-post-bugs.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211005-want-to-use-the-same-cluster-for-the-same-web-and-native.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20210523-retarget-motion-for-vrm-type-models.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20221214-powershell-autocomplete-use-right-arrow.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20220224-v-sekai-version-two-plan.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20210528-trial-install-of-gravity-for-kubernetes.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231209-appium-testing-fbx-to-gltf.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230516-v-sekai-roadmap.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230505-consistent-v-sekai-naming.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240401-shader-graphic.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230812-constraint-all-bones.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240217-essential-typle-normalization-form.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230123-player-scripting.html</loc>
-    <lastmod>2024-11-02T08:18:10.026Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231110-blender-manual-t-pose.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211005-use-materialx-for-asset-interchange.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240411-elixir-libgodot-bundlex.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240324-v-sekai-as-slc.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230611-wasm-in-v-sekai.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20220317-protect-minumum-spec-steam-deck.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20220820-cloth-sim.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240810-steamvr-dongles-separate.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231110-efficient-llm-training.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20220228-v-sekai-version-three-plan.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231127-performance-test.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240423-building-metaverse-with-glue-mechanic.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240117-pivot-painting.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230125-create-an-in-game-tablet-interface-we-can-activate.html</loc>
-    <lastmod>2024-11-02T08:18:10.026Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240613-training-dataset-creation-with-csg.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230803-publish-vrm-to-assetlibrary.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20241028-use-data-tables-for-godot-constraints.html</loc>
+    <lastmod>2024-11-02T14:50:23.690Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20220515-profile-using-perf.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231230-spatiallabs-openvr.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240330-k8s-harvester-hci.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20220222-know-where-we-re-going-by-planning-vsekai.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211005-solve-mocap-by-connecting-mediapipe-to-blender.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211031-standard-backup-procedures.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20210523-distribute-trusted-clients-with-notary.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html</loc>
+    <lastmod>2024-11-02T14:50:23.690Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240627-gdextension-as-libriscv.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211005-want-to-summon-friends-and-acquaintances-via-presence.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230505-cross-platform-artwork-distribution.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240615-what-is-mesh-transformers.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230131-adopt-best-product-development-practices.html</loc>
-    <lastmod>2024-11-02T08:18:10.026Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20220317-baserow.io-truenas.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240830-use-dokku-to-host-vsk-backend.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20220820-market-booth-tutorial.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211104-research-mesh-tooling-with-nglod.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240218-vrm-acronym-correction.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240623-do-cdn-for-launcher.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230505-v-sekai-ai-completion.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231022-hover-to-ocean-game.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20210811-minecraft-voxel.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20210811-neural-blend-shape-rigging.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230527-server-sidecar.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20241014-xr-interface-for-rigging.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20220217-omi-chan-oni-chan.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230523-marketing-cycle.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20210212-add-build-notifications.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240623-only-save-tools-in-our-cdn.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230806-v-sekai-ipad-projection-compatibility.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20220131-run-own-infrastructure.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230911-xr-grid-with-drawing.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231024-training-simulators.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/present-proposal-template.html</loc>
+    <lastmod>2024-11-02T14:50:23.878Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230107-elixir-uro-dev-sqlite.html</loc>
-    <lastmod>2024-11-02T08:18:10.026Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231126-v-sekai-report.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240330-hyperv-harvester-test.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230830-better-backend-services.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240522-webrtc-relay-test.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231108-ansible-new-server-provisioning.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20220601-lightweight-quality-avatars.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230527-godot-test-game.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/ai-assisted-proposal-style-guide.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230123-no-traversal-loading-screen.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240411-multiplayer-movement-with-parented-obejcts.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211031-play-preprocessed-animations-on-any-vrm-model.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230419-limited-tracker-placement.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20210612-flow-avatar-asset-pipeline.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20210811-glb-in-video.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20221203-block-direct-pushes-to-main.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231110-v-sekai-dependencies.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20220130-optimize-cicd.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230507-supabase.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230623-fdn-reverb-solution.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230505-automated-avatar-garment-rigging.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240326-verifying-and-finetuning-plans.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240618-schedule-as-binary-tree.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20241016-instantiating-v-sekai-content.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20220223-store-source-VSK_map-files-via-DVC.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240511-wasm-cache-incident.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20220605-host-internal-baserow.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240824-ffmpeg-wav-mic-speaker-play.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240622-gocd-agent-docker-image-update.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230812-vsekai-update-process.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240706-motion-capture-bill-of-materials.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240418-college-quest.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240621-caption-photos-for-cicd.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211005-use-kvm-to-test-our-amd-apu-test-computer-via-barrier.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240330-bitnami-rancher-helm-catalog.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211031-thorvg.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230716-enhancing-avatar-creation-process-02-advanced.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20200729-entity-networking.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231111-ayon-evaluation.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20220206-logging-notifications-from-discord.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230527-server-cdn-session-url.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240608-skin-weight-transfer-skeleton-merge.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211005-test-google-mediapipe.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240502-where-can-I-use-gltf.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231228-v-sekai-slogan.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231114-upload-creative-commons-fbx-test-files.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20220215-uro-deployment-process.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240502-install-windows-on-older-computers.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231203-mesh-rwkv-test-metrics.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231019-quest3-mocap-steam-lighthouse.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html</loc>
+    <lastmod>2024-11-02T14:50:23.690Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211031-voip.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230108-bolster-creating-the-metaverse.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240410-data-storage-elixir.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240325-fdb-sqlite-blender-godot.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20210601-store-presentation-and-book-content-via-lottie-2.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230125-user-generated-scripting-with-libsql-and-wasm.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240529-improve-godot-import-ecosystem.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20221022-have-larger-worlds-by-server-state-migration.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230602-limited-tracker-placement.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240710-web-and-pcvr-networking.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20221212-world-and-character-tools.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20221205-port-renik-to-many-bone-ik.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240218-blender-to-godot.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20210724-Spreadsheet-animation-preview.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20241001-small-game-tools.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240502-mvsqlite-launchd.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211031-make-a-place-to-record.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20221019-replicate-sync-100-000-entities.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230911-first-alpha-tag.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20210811-soiree-party.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20220203-create-default-animation-set.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231110-ai-based-outlier-detection.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211031-export-import-testing-via-robot-framework-and-swiftshader.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211031-keep-a-changelog.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240709-wired-first.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230531-godot-engine-learning.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20210715-Material-Addon-Blender.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20210811-spoke-to-v-sekai.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240326-heartstrings-vr.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240409-elixir-raft-vs-sqlite-fdb.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231108-neon-postgresql.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/index.html</loc>
+    <lastmod>2024-11-02T14:50:23.878Z</lastmod>
   </url>
   <url>
     <loc>https://v-sekai.github.io/manuals/authors.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <lastmod>2024-11-02T14:50:23.662Z</lastmod>
   </url>
   <url>
     <loc>https://v-sekai.github.io/manuals/changelog.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <lastmod>2024-11-02T14:50:23.662Z</lastmod>
   </url>
   <url>
     <loc>https://v-sekai.github.io/manuals/decisions.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/index.html</loc>
-    <lastmod>2024-11-02T08:18:10.238Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/plans.html</loc>
+    <lastmod>2024-11-02T14:50:23.878Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240409-elixir-raft-vs-sqlite-fdb.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231108-neon-postgresql.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240326-heartstrings-vr.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211031-run-the-maintance-scripts-from-windows-in-unix-mode-with-msys2.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20210715-Material-Addon-Blender.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20210811-spoke-to-v-sekai.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240709-wired-first.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230531-godot-engine-learning.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211031-export-import-testing-via-robot-framework-and-swiftshader.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211031-keep-a-changelog.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231110-ai-based-outlier-detection.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211113-learn-how-to-scale-v-sekai-using-bots-and-multipliers.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20210811-soiree-party.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20220203-create-default-animation-set.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20221019-replicate-sync-100-000-entities.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230911-first-alpha-tag.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240502-mvsqlite-launchd.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211031-make-a-place-to-record.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20210724-Spreadsheet-animation-preview.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20241001-small-game-tools.html</loc>
+    <lastmod>2024-11-02T14:50:23.690Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20221205-port-renik-to-many-bone-ik.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240218-blender-to-godot.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240710-web-and-pcvr-networking.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20221212-world-and-character-tools.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20221022-have-larger-worlds-by-server-state-migration.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230602-limited-tracker-placement.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230125-user-generated-scripting-with-libsql-and-wasm.html</loc>
-    <lastmod>2024-11-02T08:18:10.026Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240529-improve-godot-import-ecosystem.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240325-fdb-sqlite-blender-godot.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20210601-store-presentation-and-book-content-via-lottie-2.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230108-bolster-creating-the-metaverse.html</loc>
-    <lastmod>2024-11-02T08:18:10.026Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240410-data-storage-elixir.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240712-use-shrinkwrap-blender-modiifer-to-fit.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211031-voip.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20220205-cicd-to-pass by-fixing-spatial-audio-branch.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231019-quest3-mocap-steam-lighthouse.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240502-install-windows-on-older-computers.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231203-mesh-rwkv-test-metrics.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231114-upload-creative-commons-fbx-test-files.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20220215-uro-deployment-process.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240502-where-can-I-use-gltf.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231228-v-sekai-slogan.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240608-skin-weight-transfer-skeleton-merge.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211005-test-google-mediapipe.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230527-server-cdn-session-url.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20241019-reduce-size-difference-between-capsules-and-mesh-volume.html</loc>
+    <lastmod>2024-11-02T14:50:23.690Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231111-ayon-evaluation.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20220206-logging-notifications-from-discord.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230716-enhancing-avatar-creation-process-02-advanced.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20200729-entity-networking.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240330-bitnami-rancher-helm-catalog.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211031-thorvg.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240621-caption-photos-for-cicd.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211005-use-kvm-to-test-our-amd-apu-test-computer-via-barrier.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240706-motion-capture-bill-of-materials.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240418-college-quest.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240622-gocd-agent-docker-image-update.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230812-vsekai-update-process.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20220605-host-internal-baserow.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240824-ffmpeg-wav-mic-speaker-play.html</loc>
+    <lastmod>2024-11-02T14:50:23.690Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20220223-store-source-VSK_map-files-via-DVC.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240511-wasm-cache-incident.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240618-schedule-as-binary-tree.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20241016-instantiating-v-sekai-content.html</loc>
+    <lastmod>2024-11-02T14:50:23.690Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230505-automated-avatar-garment-rigging.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240326-verifying-and-finetuning-plans.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211113-file-or-attestation-for-virtual-worlds-using-ssh-signatures.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230623-fdn-reverb-solution.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20220130-optimize-cicd.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230507-supabase.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20221203-block-direct-pushes-to-main.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231110-v-sekai-dependencies.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20210612-flow-avatar-asset-pipeline.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20210811-glb-in-video.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211031-play-preprocessed-animations-on-any-vrm-model.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230419-limited-tracker-placement.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230123-no-traversal-loading-screen.html</loc>
-    <lastmod>2024-11-02T08:18:10.026Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240411-multiplayer-movement-with-parented-obejcts.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230527-godot-test-game.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/ai-assisted-proposal-style-guide.html</loc>
+    <lastmod>2024-11-02T14:50:23.690Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231108-ansible-new-server-provisioning.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20220601-lightweight-quality-avatars.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230830-better-backend-services.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240522-webrtc-relay-test.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231126-v-sekai-report.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240330-hyperv-harvester-test.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/present-proposal-template.html</loc>
-    <lastmod>2024-11-02T08:18:10.238Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230107-elixir-uro-dev-sqlite.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230911-xr-grid-with-drawing.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231024-training-simulators.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230806-v-sekai-ipad-projection-compatibility.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20220131-run-own-infrastructure.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20210212-add-build-notifications.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240623-only-save-tools-in-our-cdn.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20220217-omi-chan-oni-chan.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230523-marketing-cycle.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230527-server-sidecar.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20241014-xr-interface-for-rigging.html</loc>
+    <lastmod>2024-11-02T14:50:23.690Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20210523-complete-gltf2-vrm-import-and-export-pipeline-in-godot-engine.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20210811-neural-blend-shape-rigging.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231022-hover-to-ocean-game.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20210811-minecraft-voxel.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240623-do-cdn-for-launcher.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230505-v-sekai-ai-completion.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211104-research-mesh-tooling-with-nglod.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240218-vrm-acronym-correction.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240605-sustainable-version-management-for-godot-engine-in-v-sekai.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20220820-market-booth-tutorial.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20220317-baserow.io-truenas.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240830-use-dokku-to-host-vsk-backend.html</loc>
+    <lastmod>2024-11-02T14:50:23.690Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240615-what-is-mesh-transformers.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230131-adopt-best-product-development-practices.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211005-want-to-summon-friends-and-acquaintances-via-presence.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230505-cross-platform-artwork-distribution.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240830-pcie-lane-depletion-thunderbolt-4-issues.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240627-gdextension-as-libriscv.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211031-standard-backup-procedures.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20210523-distribute-trusted-clients-with-notary.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20220222-know-where-we-re-going-by-planning-vsekai.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211005-solve-mocap-by-connecting-mediapipe-to-blender.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231230-spatiallabs-openvr.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240330-k8s-harvester-hci.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20241028-use-data-tables-for-godot-constraints.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20220515-profile-using-perf.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240613-training-dataset-creation-with-csg.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230803-publish-vrm-to-assetlibrary.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240117-pivot-painting.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230125-create-an-in-game-tablet-interface-we-can-activate.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231127-performance-test.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240423-building-metaverse-with-glue-mechanic.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231110-efficient-llm-training.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20220228-v-sekai-version-three-plan.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20220820-cloth-sim.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240810-steamvr-dongles-separate.html</loc>
+    <lastmod>2024-11-02T14:50:23.690Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211211-create-steamdeck-hardware-proxy-by-fedora-kinoite.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20220317-protect-minumum-spec-steam-deck.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240324-v-sekai-as-slc.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230611-wasm-in-v-sekai.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240411-elixir-libgodot-bundlex.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211108-invisible-meshes-appear-via-the-use-of-the-exporter.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231110-blender-manual-t-pose.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211005-use-materialx-for-asset-interchange.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240217-essential-typle-normalization-form.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230123-player-scripting.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240401-shader-graphic.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230812-constraint-all-bones.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230516-v-sekai-roadmap.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230505-consistent-v-sekai-naming.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20210528-trial-install-of-gravity-for-kubernetes.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231209-appium-testing-fbx-to-gltf.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20221214-powershell-autocomplete-use-right-arrow.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20220224-v-sekai-version-two-plan.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20210523-retarget-motion-for-vrm-type-models.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230812-unmerge-and-merge-procedure-source-code-tree.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20221021-make-it-easier-propose-and-post-bugs.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211005-want-to-use-the-same-cluster-for-the-same-web-and-native.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211105-iterate-faster-on-wasgo-prototype-by-using-godot-34.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20220108-bake-blend-shapes-to-skeletons-for-performance.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230108-wmf-video-playback.html</loc>
-    <lastmod>2024-11-02T08:18:10.026Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20200608-vsekai-charter.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211108-integrate-with-blender.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20220317-use-spec-rough-metal.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230502-add-iree-to-godot-engine-for-image-superresolution.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211031-bake-a-materialx-into-a-custom-godot-standardmaterial3d.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230415-procedural-variations-props-envs-avatars.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230829-omifest-2023.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230125-two-groups-battle-demo.html</loc>
-    <lastmod>2024-11-02T08:18:10.026Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211031-vmd-on-vrm-animationtree-node.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230125-grow-the-community-with-a-reactive-discord-bot.html</loc>
-    <lastmod>2024-11-02T08:18:10.026Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230908-bendable-screen-generative-assistant-ggml.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20220113-change-transform-by-crdt.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20220222-rank-bone-names-with-transformer.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240330-gitlab-helm.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230516-create-an-aquarium-nightclub-booth-for-virtual-market.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231024-finetuning-workflow.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230522-JOKE-fictional-blood-combat.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240905-revised-tracker-configuration-and-constraints.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211031-cicd-export-v-sekai.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211031-client-and-mast.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211031-stream-shader-motion.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240425-proposal-prompt-system.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240522-discord-inworld-portal.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20241006-restore-onedrive-shortcut-overrides.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240413-calling-opensource-llm-with-aria.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231125-v-sekai-report.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211031-plausable-npc-behaviour.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240111-fspy.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240502-membrane-framework-identity-post.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211112-degrade-v-sekais-networking-model-to-work-in-2d-and-with-webrtc.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211031-how-to-make-a-v-sekaigodot-update.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230813-blender-runner-into-membrane-framework.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230125-possible-futures.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240217-workload-benchmarking.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240622-build-for-many-platforms.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20210212-use-log4brains-to-manage-the-adrs.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240406-itch-github-actions.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230608-v-sekai-roadmap.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231209-appium-testing-win11.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211031-membrane-framework-streaming-mixer.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20220830-godot-pdf-workflow.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240111-fit-clothing-on-humans-without-tearing.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20221205-moving-fast-philosophy-development.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230619-move-cockroachdb-to-yugabyte.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231026-blender-steam-beta-version.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230123-recording-demo-checklist.html</loc>
-    <lastmod>2024-11-02T08:18:10.026Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20220222-rank-bone-skeletons-with-xgboost.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20210710-verify-pr-workflow.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230527-server-side-content-validation.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230618-v-sekai-roadmap.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230830-better-object-pick.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230624-v-sekai-roadmap.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211031-1000-player-servers.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211031-tire-model-car-sim.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20220131-elixir-desktop-uro.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240215-avatar-customization-with-ai-facial-expressions.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240416-previewer-upload-gltf-to-glb.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211117-allow-godot-asset-library-browser-to-use-alternative-sources.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211031-use-bpr-to-rank-skeleton-bone-names.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230125-cover-80-95-percent-of-the-userbase.html</loc>
-    <lastmod>2024-11-02T08:18:10.026Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230920-godot-project-search.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211031-openvr-for-godot-engine.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230415-rgbaf-to-store-integers.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240630-use-motion-transformers-for-prediction.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240511-review-80-vr.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240522-shader-motion-to-bvh.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240105-1-meter-128-quantize.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20210811-disconnected-ipfs.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240121-easy-diffusion-fedora-install.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240613-modifying-the-mesh-transformer-for-quads.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230803-jolt-gextension-to-module.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230830-generating-v-sekai-worlds.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240710-use-godot-engine-web-threaded.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231109-discord-polygonjs-generator.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231225-mesh-transformer-facial-features.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211005-we-want-to-proxy-udp-datagrams-at-production-quality-of-service.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230811-punchline-reports.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20210811-min-spec-v-sekai.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20210529-performance-profiling.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20221019-networking-100000-entities-ownership.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230903-replicate-vrm-transform.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20210707-transfer-animations-by-baking-reset.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211031-update-uro-for-godot-4.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240120-vr-armature-system.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20241014-basic-realtime-interaction.html</loc>
+    <lastmod>2024-11-02T14:50:23.690Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231227-punchline-reports.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211031-verification-tools.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240611-lower-learning-rate.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211220-network-the-ubisoft-mixer-server.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240331-vrc-vrm-compatibility.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240522-discord-bot.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240314-live-collab.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240121-install-tailscale.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240627-every-commit-push-pass-cicd.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231112-validation-service.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240305-v-sekai-launcher.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211105-use-single-player-webxr-in-godot-engine-to-prototype-cassie.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240613-training-dataset.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20220901-mirror-extend-asset-library-packages.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230823-speech-to-blendshapes.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240121-livebook-fedora-install.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211031-extract-proposals-into-proposals.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20210715-portable-world-content.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20221206-export-godot-vrm-to-the-asset-library.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20210212-use-markdown-architectural-decision-records.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230912-target-most-popular-resolution.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230527-server-performance-test.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240622-process-for-testing-vsekai.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211128-stabilize-godot-engine-updates-by-delaying-to-2-week-cycles.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20221014-networking-overhaul-proposal.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211031-face-motion-tracking-requires-standard-shapes.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20220605-gocd-pipeline-reset.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20210811-game-workflow-membrane.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230310-don&#39;t-merge-incomplete-work.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230701-vsekai-broken-down-goals.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211005-bridge-music-to-xr.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240715-vrchat-networking-mental-model.html</loc>
+    <lastmod>2024-11-02T14:50:23.690Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230419-package-godot-for-pkgin.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240618-4-player-test-vsekai.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230812-gocd-agent-setup.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211031-create-a-demo-viewer-gallery.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230602-v-sekai-roadmap.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231027-apartment-building-vr.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240616-request-for-quad-mesh-dataset.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231027-write-a-list-of-github-pull-requests.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230616-pmx-to-vrm.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211207-for-godot-engine-changes-use-a-decision-flowchart.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240621-proposal-template copy.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230123-integrate-blender-with-gltf-extensions-and-godot.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230527-v-sekai-roadmap.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230415-load-collaborate.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240613-1k-quad-limit.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230106-walking-controller-renik.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211129-create-a-godot-engine-asset-store-service-on-elixir-and-on-sqlite.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231027-dreamcraft3d-workflow.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20220916-too-many-branches-on-v-sekai-godot.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230123-face-helmet-capture.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211104-research-mesh-tooling-with-kaolin.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240709-anwave-set-nvidia-watt-limit.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231108-v-sekai-chat-bot.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230620-doi-github.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20220222-rank-skeleton-bone-names-with-catboost.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230803-idle-rpg-home.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230626-godot-vrm1-addon.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240407-pcvr-vs-standalone.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240217-container-2-wasm.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230831-fixing-menus.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230824-subdiv-for-lods.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211106-preview-materialx-materials-on-the-web-in-godot-engine-2.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231227-blue-green-shadows.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240411-elixir-libgodot-zig.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211109-create-a-vrm-character-by-experimenting-with-written-workflows.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20220130-to-record-decisions-write-a-proposal.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20210811-omi-glb.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20221006-unidot-is-optional.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231229-mRemoteNG.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240710-convert-blender-cc0-base-mesh-to-godot-engine-t-pose.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230519-v-sekai-roadmap.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231225-mesh-transformer-clothing.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230519-add-vrm-omi-personality-gltf-extension.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230123-ready-the-net-demo.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230125-without-viz-we-cannot-compare-the-interpolation.html</loc>
-    <lastmod>2024-11-02T08:18:10.026Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230131-meeting-at-gdc-2023.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240329-ready-to-go-kit-windows-11.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230508-novel-3d-views.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230804-dokku.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211031-godot-database-viewer-for-proposals.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211105-have-an-webxr-version-of-v-sekai.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211212-create-steamdeck-hardware-proxy-by-fedora-silverblue.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20220820-bake alembic-anim-via-blender.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211031-character-workshop.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211005-improve-meshing-results-by-subdivision-in-godot-engine.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231108-munich-godot-engine-conference.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240218-vrm-substance-editor.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231114-maintain-svgcleaner.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231105-pdf-embed-raster-svg-vr.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211031-use-our-custom-fullbody-ik.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231114-elixir-definition-of-godot-types.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230913-V-Sekai-bugs.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240914-godot-engine-xr-elite-conference-setup.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20221018-v-sekai-game-update-procedure.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230531-godot-engine-ipad.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231110-better-pipeline-tools.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20221019-develop-a-replication-sync-for-100-000-entities.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240217-intended-effort-versioning.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240623-what-is-uro-backend.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230614-llm-statechart.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20220531-elixir-uro-dev.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240413-training-quad-based-meshgpt-with-40gb-vram.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231203-mesh-rwkv.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230429-v-sekai-roadmap.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230123-use-easy-charts-for-observability.html</loc>
-    <lastmod>2024-11-02T08:18:10.026Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20220118-to-make-it-easier-to-upload-maps-and-avatars-templates.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211031-phase-out-groups-terminology-for-vskdefault.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211103-use-platform-called-vfx-reference-platform.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240502-mesh-object-sync-benchmark.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240121-mac-setup.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211130-avoid-avatar-breaking-by-following-quality-checklist.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240710-platform-focus-on-pcvr-and-web.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211031-construct-the-virtual-world.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240307-rabbitmq-ra.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230911-xpr.exs.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231203-graphsage-embedding-generation.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240528-pipeline-godot-wasm-importer.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230806-music-gen.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211130-fix-critical-bugs-by-creating-an-upstream-pull-request.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211031-bake-blend-shape-to-skeleton-animation.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231226-furniture-vs-organic.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20220318-merge-retargeting-pr.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230726-solve-renik-directly-rather-than-many-bone-ik.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240110-magical-girls-college-novel.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231201-xr-hands-animation-node.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20220624-webcam-to-posed-characters.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211229-stream-a-character-from-a-webcam-to-the-vmc-protocol.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231112-archive-projects.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230911-can-poly-green-coords-extend-to-3d.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230630-vsekai-goal-meeting.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231218-mtlx-try-two.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240424-reset-steamvr-controllers.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20220118-convert-gltf-to-a-scene.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230719-pose-kusudama-constraints-in-vr.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231020-llama-cpp-mistral-npc.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231027-drawing-concept-to-blockout.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230521-audio-jitter-buffer-voip.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231108-nier-automata-world-expansion.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20220202-gltf-extensions-for-interoperability.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230516-additional-3d-import.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/attachments/pitch_general_02.html</loc>
-    <lastmod>2024-11-02T08:18:10.170Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/attachments/project_mirage.html</loc>
+    <lastmod>2024-11-02T14:50:23.810Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/attachments/virtual_pets/LICENSE.html</loc>
-    <lastmod>2024-11-02T08:18:10.238Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/attachments/thunderbolt_install_windows.html</loc>
+    <lastmod>2024-11-02T14:50:23.862Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230507-avatar-publishing-workflow-portability.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/attachments/pitch_apple_vision_01.html</loc>
+    <lastmod>2024-11-02T14:50:23.810Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230131-default-test-plan.html</loc>
-    <lastmod>2024-11-02T08:18:10.026Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20210523-simplfy-meshes-and-lods-better-with-quads.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211031-benchmark-animation-playback.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230525-animation-ik-node.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20221205-debug-linux-export.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230813-mixer-broadcaster-into-membrane-framework copy.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211005-create-sop-for-vrm-creation.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211031-arc-radial-menu.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20220131-github-actions-support.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240127-urban-explorer-gdc-2024-sample.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20221203-target-10-minutes-cicd.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230429-improve-collab.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211031-have-better-user-developer-experience.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211031-have-wires-in-3d.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211031-streaming-godot-to-opensoundcontrol.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240502-gltf-fbx-tscn-vrm.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20220207-virtual-pets.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20220531-truenas-scale.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230310-xml-based-tests.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230505-polygon-mesh-based-sculpting-tools.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240409-crud-godot-tiles.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230803-subrepo-addon-management.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240705-rpg_town.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20210622-shadermotion-to-godot-engine.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240406-web-based-explore.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20241014-app-updater.html</loc>
+    <lastmod>2024-11-02T14:50:23.690Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240325-table-avatar-embedded-xmp.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230602-pmx-module-integration.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240623-talk-length-prototypes.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230507-distributed-sim.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211031-script-as-a-binary.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20241011-recovering-makehuman-parameters.html</loc>
+    <lastmod>2024-11-02T14:50:23.690Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231108-neon-1-gb-scene-storage.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231108-postgres-bytea-optimizations.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211214-create-an-open-metaverse-by-working-on-v-sekai.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230429-git-subrepo-challenges.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230509-wasm-data-exchange.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20221006-rename-to-main.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230527-organization.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240717-core-vsekai-scripting.html</loc>
+    <lastmod>2024-11-02T14:50:23.690Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211005-create-add-spring-bones-to-vrm-models.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230819-train-game.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230125-provide-metadata-to-match-compatibile-maps-and-avatars.html</loc>
-    <lastmod>2024-11-02T08:18:10.026Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240217-documentation-guidelines.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231104-flatbuffer_packed_scenes.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231201-headless-launcher-backend.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240626-update-python3-macos-certicates.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20211031-meeting-area.html</loc>
+    <lastmod>2024-11-02T14:50:23.670Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240611-test-1x-and-4x.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240708-vsekai-my-life-as-a-queen.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230719-dual-databases-cockroachdb-khepri.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20200602-manage-backend-with-k3s.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20231108-neon-vercel-functions-toy-problem.html</loc>
-    <lastmod>2024-11-02T08:18:10.034Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230619-membrane-framework-for-mesh-processing.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230716-enhancing-avatar-creation-process-01-regular.html</loc>
-    <lastmod>2024-11-02T08:18:10.030Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20210811-godot-transparency.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211105-take-a-list-of-3d-points-to-triangulate-in-godot-engine.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230620-t5-jsonformer-xstate.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20210523-basis-universal-import.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240710-use-webrtc-to-native-interop.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240425-recharge-cycle.html</loc>
-    <lastmod>2024-11-02T08:18:10.038Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240710-art-direction-in-vsekai.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20230123-publish-godot-vrm-4.html</loc>
-    <lastmod>2024-11-02T08:18:10.026Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230408-v-sekai-launcher.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211031-gltf-importer-should-bind-animation-players-to-the-closest-root-node.html</loc>
-    <lastmod>2024-11-02T08:18:10.018Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230831-fixing-upload-limits.html</loc>
+    <lastmod>2024-11-02T14:50:23.678Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20240608-for-skeleton-mirroring-use-the-godot-humanoid.html</loc>
-    <lastmod>2024-11-02T08:18:10.042Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230922-spacetime-shadow-shards-sync.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20211229-run-meetings-using-lean-coffee.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20230310-IREE-backend-for-machine-learning-computations.html</loc>
+    <lastmod>2024-11-02T14:50:23.674Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/decisions/20221016-v-sekai-view-replication.html</loc>
-    <lastmod>2024-11-02T08:18:10.022Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20240330-cicd-gitlab.html</loc>
+    <lastmod>2024-11-02T14:50:23.686Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/changelog/2024/20240603-changelog.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/decisions/20231229-byobu.html</loc>
+    <lastmod>2024-11-02T14:50:23.682Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/changelog/2024/20240505-changelog.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/changelog/2024/20240701-changelog.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/changelog/2024/20240330-changelog.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/changelog/2024/20240625-changelog.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/changelog/2024/20240202-changelog.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/changelog/2024/20240101-changelog.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/changelog/2024/20241003-changelog.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/changelog/2024/20240901-changelog.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/changelog/2021/20210901-changelog.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/changelog/2021/20211001-changelog.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/changelog/2021/20210601-changelog.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/changelog/2021/20210801-changelog.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/changelog/2021/20210501-changelog.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/changelog/2021/20211101-changelog.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/changelog/2021/20210401-changelog.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/changelog/2021/20210701-changelog.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/changelog/2022/20220201-changelog.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/changelog/2022/20220601-changelog.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/changelog/2022/20220501-changelog.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/changelog/2022/20220301-changelog.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/changelog/2022/20221101-changelog.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/changelog/2022/20220901-changelog.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/changelog/2022/20220801-changelog.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/changelog/2022/20221201-changelog.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/changelog/2022/20221001-changelog.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/changelog/2022/20220101-changelog.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/changelog/2023/20230901-changelog.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/changelog/2022/20220401-changelog.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/changelog/2023/20230801-changelog.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/changelog/2023/20231109-changelog.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/changelog/2023/20231207-changelog.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/changelog/2023/20230501-changelog.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/changelog/2023/20230301-changelog.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/changelog/2023/20230101-changelog.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/changelog/2023/20230701-changelog.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/changelog/2023/20230201-changelog.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
   <url>
-    <loc>https://v-sekai.github.io/manuals/changelog/2023/20230601-changelog.html</loc>
-    <lastmod>2024-11-02T08:18:10.014Z</lastmod>
+    <loc>https://v-sekai.github.io/manuals/changelog/2023/20231001-changelog.html</loc>
+    <lastmod>2024-11-02T14:50:23.666Z</lastmod>
   </url>
 </urlset>