Skip to content

Playtesting bug fix ideas (Physics, Corrupting File) #94

Description

@FrankieIzzy

Tinker Suggestion

  • I verify that this suggestion isn't already a feature in Tinker and that I have looked over the settings and mod description.

Feature description

Hello, Cool mod, I have an idea, as an impossible level maker(source im making one i guess), these (few) suggestions would help i thjnk

Any fix to editor physics in general,
Biggest ones are (besides the d block wave, which is already in) cube acting like h blocks and the physics being inconsistant and also inconsistantly (sometimes normal) inconsistant (sometimes the weirdest thign ever), Usually the bug where the cube acts like an H block isn't bad for playtesting (since you are probably going to go on the right path anyways) but if you hit a breakable block it bugs out, I cannot find the real source of this bug, but what i assume is happening (from my mediocre coding understanding) is that something is messing with the cube in a way that it is always registered as valid step-up, and when you hit a block from the bottom, it steps to the closest block hitbox ending, so it is just resetting velocity, not like an actual H block. my ideas are these

Anything that will fix more of the editor bugginess (good luck) mostly with step ups, but here are some suggestions that would be reasonable to try to do,

Editor playtest cube force bugged ( cant think of a name)
Info:, Makes the cube forced to clip downwards when hitting a solids bottom, like the bugged cube physics, similar to h blocks.

Area Scale (biggest opp)
Playtesting too many times in a row, already bugs stuff out, which is annoying but then you can literally be screwed without a backup mod, I think this is because floating point (root of all evil) but idk man, I can't easily replicate this because the editor is buggy, but a solution i can think of is making it so the editor cannot be changed while playtesting until pause, but im not a coder,
If im pushing my luck then what if
Preview move (considering area scale issues when playtesting, this is probably a bad idea and will ruin preformance so no)
but anyways, TLDR, Option to fix editor inconsistancy in any way, and fix area scale sometimes corrupting stuff
Thanks, frankieizzy i guess

Media

No response

Metadata

Metadata

Assignees

Labels

suggestionFeatures you want to see in Tinker

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions