#(fixed) playtesting death delay

51 messages · Page 1 of 1 (latest)

minor comet
#

Desc: when i am trying to playtest my level when i die it pauses then dies but when i exit out and go back in it works well for like 5 attempts then starts doing the delay again a thing i noticed is that when i played an attempt and died the level scroll bar at the top got abnormally long reaching so far that it wont scroll any further that point is around the 13 minute mark but my level is only 3 minutes also it was not laging durring lay creation only after i started adding triggers and stuff

attempted fixes: i thought it was one of the triggers since i was useing item persist particals camera triggers shaders area moves and a freecam section so i started going trough them and nothing was changing i did have a block that followed player x along the bottom so i made it stop at the end of the level but it did nothing. soi am here for help i dont know if this is triggers bug or something else.

heady juniperBOT
#
`Triggers` FAQ

Having trouble getting a trigger to work? Make sure to follow these instructions.

  1. You know how to use the trigger that you're having trouble with (Otherwise, see Triggers 1).
  2. Your trigger isn't accidentally Touch/Spawn Triggered, Stopped, or Toggled Off, it is set to the correct channel, has the correct order, and targets the correct Item ID/Group.
  3. Your trigger's settings are modified from the default values so it can actually do something.
  4. If you're using one of these triggers Move (Target/Direction) GradientTrigger RotateTrigger FollowTrigger ScaleTrigger FollowPlayerYTrigger AdvancedFollow AreaMoveTrigger (ANY Area Trigger) CamStaticTrigger CamEdgeTrigger SongTrigger SFXTrigger (Proximity Modes), your Center Group ID only has one object assigned to it or has one object as a Parent Group.
  5. If you're using one of these triggers to activate other triggers SpawnTrigger OnDeathTrigger TouchTrigger CollisionTrigger InstantCollision CountTrigger InstantCount RandomTrigger AdvancedRandom EndLevelTrigger SpawnParticleTrigger , you've assigned other triggers to the right groups and/or marked those triggers as Spawn Triggered.
  6. If you're using one of these triggers CollisionTrigger InstantCollision CountTrigger InstantCount ItemEditTrigger ResetCollectibleTrigger SpawnParticleTrigger, the additional inputs (Collision Blocks, Pickup Triggers, Item IDs, etc.) exist and are working properly. Double-check that at least one Collision block is Dynamic.
If none of these options work, please let us know.
minor comet
#

-request

heady juniperBOT
#

<@&1422239416323412098>

Help Request

@minor comet is requesting additional help - please see their original request [here](#1500326881172652132 message).

distant trout
#

Oh that’s weird

#

Never seen that before

olive scroll
minor comet
#

ok i can try rmoveing mods

distant trout
#

Does it occur without start pos?

#

You can negate start pos bugs by using a teleport trigger instead

minor comet
#

not really but it dose not happen twords the begining of the level

distant trout
#

Hmm

#

Idk

#

Try mod thing first

minor comet
#

ok

#

1 moment i am looking trough my mods

#

ok i removed all my mods for editing add its still laging i have like 40 levesl in my editer not big ones but is that it

distant trout
#

I don’t think this is a trigger issue at least

#

The only thing I can think of is that your level is 3 mins long, and it might be due to something floating point error

#

But I don’t really know

minor comet
#

the item presist is used for a custom attempt counter is that it?

#

also whats a floting point error

gentle sierra
#

not floating point error

junior basin
# minor comet also whats a floting point error

Floating point errors refer to errors that involve the game's way of handling numbers. There's a limit to the amount of data it can store (some huge number). When you somehow overshoot that limit, the game starts storing data as duplicates. That shouldn't be the case though considering the level's only a layout with triggers so far. Item persist could be the case but that doesn't explain the editor issue

gentle sierra
#

you're explaining number limits

#

floating point error is that decimal (x.x) numbers stored on computers have limited precision

junior basin
#

Really? I must've heard some misinformation somewhere cus this was something explained to me that way. Or maybe I mixed up the two

gentle sierra
junior basin
#

Yeah. Prolly cus of the infinite chess video

gentle sierra
#

its especially confusing because floating point numbers also suffer from overflow errors

junior basin
#

Code is weird

gentle sierra
#

tell me about it

junior basin
#

Honestly, with how this bug looks, I'd try to make it consistent across attempts to make it an intended feature

#

Hey @minor comet

#

Try sending the level to a friend and watching how they experience the bug

#

If it's the same, it's an issue with the level

#

If there's slight differences, then it might be geode

#

If it's non existent, it's a system issue

minor comet
#

ok i will have to try tomorrow so i will see

minor comet
#

update i tryed and when they tryed to play it crashed thire game

final crescent
#

I want to try it out

minor comet
#

ok i can

final crescent
#

You can drop the ID here

minor comet
#

ok gimmi a sec

#

i sent you a privet dm

final crescent
#

Nice

#

I still think this is some trigger problems

minor comet
#

ok it is fixed it was the area moves i did not put and area stop after they where supost to be done