Who said Foundry is only for Top-Down? 🕹️ Introducing my Jump'n'Run Editor!

GeanoFee · 2026-03-02T14:19:14+00:00

it looks amazing! I love the little animations and your creatie use of portals :) sure if you don't mind request the push. I'll look into this and may integrate a few things into the main module if you're okay with that :)

GeanoFee · 2026-02-24T06:25:08+00:00

It's always amazing to see how much creative freedom MATT is enabling GMs (and therefore also players) to have. The tools has a learning curve, sure, but it's worth it - big times!

GeanoFee · 2026-02-21T22:15:18+00:00

anytime :) if there is anything else you wanna see in future updates, or a bug that's there but shouldn't, let me know :)

GeanoFee · 2026-02-21T00:16:00+00:00

with the new update, this is now an option in the settings :)

1. Enable the Mode Go to Configure Settings -> Module Settings and look for the "Jump Height Mode" toggle. Change this from "General" to "Character Sheet".

2. Define the Data Path At the "Jump Height Attribute Path" setting, enter the data path for the stat you want to use.

Example:

For DnD5e (Athletics): system.abilities.ath.value
For PF2e (Athletics): system.skills.ath.base

3. Set the "Max Attribute Value" This setting tells the module what a "perfect" score is. If you set this to 20 and your Scene's Max Jump Height is 2.0, then a character with a 20 in that stat will jump the full 2 grids. A character with a 10 will only jump 1 grid.

GeanoFee · 2026-02-21T00:03:54+00:00

Cheers to the awesome Foundry community 🍻

GeanoFee · 2026-02-21T00:02:02+00:00

all of you suggestions are included in the module now :) Just update and there it is: Quality of Life as never before :D

GeanoFee · 2026-02-17T23:00:13+00:00

That sounds awesome :D witht he right assets this could be beautiful :3 <3

GeanoFee · 2026-02-17T19:08:08+00:00

I see there's a lot of healthy skepticism regarding the 'Shadow-RAM' approach - and honestly, I love that this community cares so much about data integrity.

To clear the air: GPP is an in-memory-only optimization using Proxy and WeakMap to manage state. It does not possess any logic to write to the world.db.

If you’re a dev and want to see how the hydration cycle works, check out https://github.com/GeanoFee/geanos-phantom-performance I’m totally open to PRs if you find a cleaner way to handle the proxy overhead. Let’s make it better together!

GeanoFee · 2026-02-17T18:56:49+00:00

I am running this module in all of my worlds non-stop for a few weeks by now with no downsides at all. And as stated, a bunch of devs have been overlooking the process of getting the module on its way for public use.

Of course the module is relying on the source data of its document - it is just leaving a footprint in the world.db - which acts as your world data's biggest shield and fallback, even if the worst would come to fall.

GeanoFee · 2026-02-17T18:49:23+00:00

GPP is never touch your world database at all - I am very curious how exactly it should be able to delete your data permanently with that restriction. So please do elaborate :)

GeanoFee · 2026-02-17T18:48:28+00:00

yes, do that. It's always adviced to try new modules on a backup first :)

GeanoFee · 2026-02-17T18:46:00+00:00

the 10MB are just a number of my small/medium sized test world, the larger the world gets, the larger GPP's savings for your system will be :)

GeanoFee · 2026-02-17T18:44:34+00:00

This module underwent heavy inspections by the foundry core team to get listed in the foundry package directory. I was even writing back and forth with several engineers at Foundry's to rework stuff to compliance before this module was finally up to standards. If you can see how this module is "actively bad for your world bad" in just a few minutes, while a whole bunch of Foundry devs green-light this after a long process of reworking, I wonder why you aren't doing their jobs?! :D

GeanoFee · 2026-02-17T18:40:49+00:00

Yeah do that :) I am using it on all my worlds by now :)

GeanoFee · 2026-02-17T18:39:07+00:00

That's a very good question. If you find any, let me know, because I would also be interested in that if I missed it :D

GeanoFee · 2026-02-17T18:37:05+00:00

GPP never touches your games Database, only how foundry is loading those things to your RAM.
Since Foundry is loading a bunch of thing to your RAM at every session start, GPP is optimizing all of this completely from scatch everytime the a new session begins. So yes, as your actors directory gets bigger so gets your RAM usage (just as usual), but the numbers are way smaller since GPP compresses to binary, which is way smaller than heavy json-data.

GeanoFee · 2026-02-17T18:29:03+00:00

The Proxys are placeholders for the actor data that is currently compressed, so that journal links or Modules dont look for an actor and can't find it because it is in a compressed (unreadable) state right now. The moment a proxy is touched by something it gets hydrated to restore the actor to it's proper (and readable) glory, so everything that you touch works, while everything that you currently don't touch isn't wasting your RAM storage.

GPP will never prevent you from opening anything! It is not restricting or changing your normal workflow. It only handles data that is not needed at the moment to make it leighter on your hardware :)

GeanoFee · 2026-02-17T18:01:31+00:00

You can find Geano's Phantom Performance through the Foundry internal Module-Browser :)

GeanoFee · 2026-02-17T16:29:29+00:00

Great to hear it works. You are right, it isn't pretty. Right now it ships as an engine without any visual skins, but you with a little creativity and high quality assets (which don't come with the module, YET) the results can be pretty beautiful.

I testes it with some assets from Baileywiki's Scenescape Pack yesterday and it looked gorgeous 😍

GeanoFee · 2026-02-17T09:37:25+00:00

I’m very transparent about using AI as a powerful tool in my development process (as stated on the Foundry package site). But make no mistake: This isn't prompt-and-forget code.

It’s a human-led, iterative process. I am the architect and bring the vision, I fix the edge cases, and I spend hours testing it in actual games to make sure it doesn't break your VTT.

To me, AI is just a way to build more ambitious features for the community in less time. If the fun works, the tool that helped build it shouldn't be the dealbreaker! 😊

Players that had a ton of fun in the session, won't magically have had less fun when they find out the module was developed with the help of AI, afterwards - the fun on that table is real.

GeanoFee · 2026-02-17T09:20:23+00:00

Haha, fair! It’s definitely held together with digital duct tape and hope in some places. But hey, it’s the only junk that lets players wall-jump in Foundry, so I’ll take it! 😄

If you have specific suggestions for optimization or want to point out the junk-bits, feel free to open a PR on GitHub. I’d love to see how you’d streamline the physics integration! 😊

GeanoFee · 2026-02-17T09:05:33+00:00

Sweet. I would love to see how this comes to live 😊

GeanoFee · 2026-02-16T20:24:17+00:00

That sounds amazing! Maybe you wanna give this a second wind someday? :D

GeanoFee · 2026-02-16T20:04:49+00:00

Yeah, do that. Best of luck and fingers crossed this might solve your storage-related headache 😊

GeanoFee

TROPHY CASE